Archive for January, 2009

2008 BMW 335XI – Fuel Delivery Lemon Story

Posted on January 24, 2009. Filed under: Car Tangents |

By: Brenton Blawat

Part 1 – Lemon Law Over / Issue Logs

Part 2 – Contacting the Dealer / Manufacturer – UPDATED!!

 

SANY0902

Friday, January 23rd, 2009 – Yes, this is my car. Yes that is a construction cone in front of it (a perverted joke my associate was playing on me). Probably not as surprising as the dunce code my associate found on his vehicle after I left the Hotel (shown below; yes that is me hiding behind the car!).

SANY0903

Perhaps my associate’s joke provided certitude to the troubles that I was going to have with my new 2008 BMW 335XI?

Let me be frank about my car. I LOVE IT! It’s fast, sporty, handles like a dream, and is everything I would want in a vehicle. It came fully loaded from the dealership and has every little gadget that makes this geek completely satisfied for the lease term. I have no regrets on purchasing this vehicle and up to this point, I’ve been extremely impressed by BMW’s responsiveness to my issues.

I am writing this to allow the community to follow me through my journey to claiming my vehicle through the Wisconsin Lemon Laws. I will be updating this article throughout this process. It will be interesting to see the progression of my frustration (hopefully lack there of) and have my experience serve as a guide for others.

Lemon Law Statutes

According to the Wisconsin Lemon Laws the following must be satisfied:

X You bought or leased a new vehicle. New Lease on May 3, 2008
X The vehicle is a car, truck, motorcycle or motor home. Vehicle is a Car
X The vehicle developed a defect or defects during its first year and before the warranty expired. See Service Details Below. All in First Year.
  One of the following happened during the vehicle’s first year and before the warranty expired: One of the following did happen:
X The dealer failed four times to fix the same defect; Car has been at the dealer 5 times since the purchase date for Fuel Delivery Issues.
  OR  
18 The vehicle was out of service for 30 days or more due to defects. Only has been in the shop for 18 Days.

 

It’s a Lemon What’s Next?

According to the department of transportation for Wisconsin they strongly suggest completing the Formal Wisconsin Paperwork for the issues.

http://www.dot.wisconsin.gov/safety/consumer/forms/llfrm700.pdf

Completed Paperwork: Friday, January 23rd, 2008

Filed Paperwork: (To Be Determined)

They also suggest reporting the Lemon through pre-established programs in the state of Wisconsin (AKA WisDot Certified Program).

BBB Auto Line

(Certified for: Audi, Ford, Lincoln, Mercury, Hyundai, Isuzu, Kia, Mazda, Volkswagen)
(Non-certified for: Acura, AM General, General Motors (including Saturn and Saab), Geo, Honda, Infiniti, Nissan, Subaru)

National Center for Dispute Settlement

(Certified for: Porsche)
(Non-certified for: Lexus, Toyota, Mitsubishi, Suzuki)

 

Do you see my problem yet? There are no WisDOT Certified (or non Certified) Programs for BMW owners to dispute their vehicles. This might be an interesting bottleneck.

Verbiage in the Owner Manual – Lemon Law

Book: Service and Warranty Information

Information:

©2007 BMW of North America, LLC

Woodcliff Lake, New Jersey 07677

Printed: Printed in U.S.A. 07/07

Quote:

Customer Assistance – Notification

During a specific period (for example, the earlier of 12 months or 12,000 miles, though this period varies by state), some states require us or our authorized BMW center, to repair in a reasonable number of attempts, any defect or condition which substantially impairs the use, value, or safety of a new vehicle sold, leased or registered in that state.

A reasonable number of attempts is generally defined as (i) four or more attempts to repair the same defect (the number of attempts vary by state) or (ii) the vehicle is out of service by reason of one or more repair(s) for more than a cumulative total of 30 days (this period varies by state), except for delays created by conditions beyond our control.

If we are unable to correct a defect or condition covered by these statutes in a reasonable number of attempts, we may be obligated either to replace the vehicle or reimburse the owner/lessee in an amount equal to the purchase price or lease payments paid by the owner/lessee, less the amount direct attributable to use of the vehicle by the owner/lessee.

You should send written notification directly to BMW of North America, LLC of the existence of an alleged defect. Send written communication to the Customer Relations and Services Department address listed below.

BMW of North America, LLC

Customer Relations and Services Department

P.O. Box 1227

Westwood, New Jersey 07675-1117

Telephone: 1 800 831-1117 “

— OK so first problem. The State of Wisconsin mentions it is a good idea to send the Lemon form via certified mail. In the United States you cannot send certified mail to a P.O. Box. Tricky BMW. After a little research:

http://www.bmwusa.com/Standard/Content/CompanyInformation/

BMW of North America, LLC
300 Chestnut Ridge Road
Woodcliff Lake, NJ 07675

 

The Birth Of  A New Baby BMW – AKA The Problem Child

n691181521_1293914_760

January 2, 2008 – My BMW was created.

May 3rd, 2008 –

I became a proud owner of a 2008 BMW 335XI. I purchased this vehicle from International Autos located at 2400 South 108th St., Milwaukee, WI 53227. If you are looking for a new BMW, Audi, Mini, or Mercedes, I strongly suggest talking with Jay Sheik. While I had a bad experience with this car, Jay has made this experience worth while. You can read my review of my experience with Mr. Sheik at his linked in profile. Its definitely not his fault that my car was a Lemon.

1. June 9th, 2008 – 1,175 Miles

Symptoms: Car was having problems starting in my garage. The car would not drive nicely from the line in ‘D’ and was running rough. I also received the Engine Malfunction, Reduced Power Message. The crank time on the car was anywhere from 5 – 10 seconds. Problem started just after the vehicle turned 1,000.

Loaners: Car was delivered to International Auto’s BMW Service Center and received an 2008 BMW 328XI loaner vehicle.

Results (verbatim): FUEL PUMP FAILURE 6199000 3 0000555 2 133159 4 1351517 17 TROUBLESHOOTING USING GT-1, VERIFY FAULT STORED IN DME (2FBF-FUEL PRESSURE RELEASE LOW), PERFORM DIAGNOSIS USING GT-1 TEST B1214_DI6KHDR AND B1214_DI6KNDR (CHECKIGN LOW AND HIGH PRESSURE TESTS RESPECTFULLY) FOUND HIGH PRESSURE FUEL PUMP FAULTY. REMOVE INTAKE MANIFOED AND ASSOC PARTS, REPALCE FUEL PUMP, RE-INSTALL AND RECHECK FOR FAULTS (0) RECHECK OK. CLEAR FAULTS AND RESET IDLE ADAPTATIONS. PRIOR TO DIAG, PER SIB#12-55-06, HOOK UP TO SSS AND VERIFY SOFTWARE STATUS BY STARTING PROGMAN(VERSION OF DATA UPDATED OK) CHARGE BATTERY.

Final Verdict: Fuel Delivery System

Return Date: June 13th, 2008

Days: 4 Days

2. June 18th, 2008 – 2,588 Miles

Symptoms: Car was having problems starting in my garage. The car would not drive nicely from the line in ‘D’ and was running rough. I also received the Engine Malfunction, Reduced Power Message. Vehicle would die while idle or slow which posed a safety hazard in intersections.

Loaners: Car was delivered to International Auto’s BMW Service Center and did not receive a loaner vehicle.

Results (verbatim): 2588 FAULTY PRESSURE PUMP 0000005 4 1351518 17 CHECKED FAULTS FOUND FCS FOR TOO LOW FUEL PRESURE RAN TESTPANS PER SI_125506. TEST PLAN PROMPTED FOR REPLACEMENT OF HIGH PRESSURE PUMP REPLACED PUMP.

Final Verdict: Fuel Delivery System

Return Date: June 20th, 2008

Days: 2 Days

3. January 10, 2009 – 18,025 Miles

Symptoms: My car felt like I was dragging thousands of pounds of weight behind the vehicle. The car would not idle nicely, and eventually died when at idle. It also felt as if the transmission was going to blow up when driving.

Loaners: Car was delivered to International Auto’s BMW Service Center and received an 2009 BMW X3 loaner vehicle.

Results (verbatim): 18025 FUEL RAIL PRESURE READING WRONG 0000005 .40 1331529 .40 1353596 .40 CHECK FOR FAULT CODES FOUND 4 FAULTS FOR FUEL PRESURE PERFORMED PRESURE TEST ON SYSTEM PER TEST PLAN FOR FAULTS FOUND FUEL RAIL SENSOR READING LOW REPLACED SENSOR CLEARED CODES

Final Verdict: Fuel Delivery System

Return Date: January 14, 2009

Days:  4 Days

 4. January 20, 2009 – 18,696 Miles

Beauty(When I was bored waiting for the Tow I decided to take a picture of my dash before the car died) 

Symptoms: (again) My car felt like I was dragging thousands of pounds of weight behind the vehicle. The car would not idle nicely, and eventually died when at idle. It also felt as if the transmission was going to blow up when driving. Vehicle would die while idle or slow which posed a safety hazard in intersections.

I also received the Engine Malfunction, Reduced power message. Also saw the above picture full of colorful lights on my dash. (But not merely as colorful as the words going through my head at the time.)

Loaners: Car was delivered to Patrick BMW Service Center and received an 2009 Jeep Wrangler loaner vehicle.

Results (verbatim): 18705 HIGH PRESSURE FUEL PUMP ENGINE BARELY RUNNING AND RUNNING ROUGH PERFORM SHORT TEST. FOUND MULTPLOE FAULTS SOTRED FOR FUEL PUMP SYSTEMS, CYLINDER INJECTION CUTOUT, AND MISFIRE DETECTION. DW TIME PUCNHED FOR CONTINUED DIAGNOSIS. PROCEED WITH TEST MODULE AND CHECK LOW PUMP PRESSURE AND SENSOR AT 6 BAR OK. NO FAULT FOUND IN LOW PSI SYSTEM DIAGCODE: D1330_B0000000_05_901. PROCEED AND CHECK HIGH PRESSURE FUEL SYSTEM CHECK PRESSURE OF RAIL PRESSURE SENSOR OK CHEKC PRESSUR AT IDLES PEED AT RAIL PRESSURE SENSEOR ACTUAL PRESSURE 147.2 BAR TARGET PRESSURE 50BAR. CHECKED PRESSURE AGAIN AND PRESSURE WAS OK. INTERNAL PUMP FAILURE. REPLACE HIGH PRESSURE FUEL PUMP

DIAGCODE: d1350_0000000_02_001. CLEAR FAULT MEMORY AND ADAPTATIONS THEN TEST DRIVE. CAR STARING AND DRIVING AS DESIGNED. CHECK ENGINE LIGHT OFF. CUSTOMER TO MONITOR. PRINTOUTS INCLUDED ON FILE.

Final Verdict: Fuel Delivery System

Return Date: January 21st, 2009

Days:  1 Days

5. January 22, 2009 – 18738 Miles

Symptoms: (again.. yes again) My car felt like I was dragging thousands of pounds of weight behind the vehicle. The car would not idle nicely, and eventually died when at idle. It also felt as if the transmission was going to blow up when driving. Vehicle would die while idle or slow which posed a safety hazard in intersections.

Loaners: Car was delivered to Patrick BMW Service Center and received an 2009 Jeep Wrangler loaner vehicle. They switched me to a 2009 Toyota Corolla for the week as I put on major miles on the weekends driving between Wisconsin and Chicago.

Results (verbatim): A OWNER REPORTS WHILE DRIVING LAST NIGHT THE ENGINE HAD REDUCED POWER AND SEEMED TO MISFIRE

CAUSE: .

5199000 OPEN TIME Job time without allowance for / body equipment

235 WAR

1 13-53-7-545-725 INLET PIPE:135040

Final Verdict: Fuel Delivery System (fuel rail sensor)

Return Date: January 28, 2009

Days:  7 Days

GRAND TOTAL SERVICES: 5

GRAND TOTAL DAYS: 17 Days

 

UPDATED 6. June 1, 2009 – 30766 Miles 

IMG00419-20090601-1509 IMG00420-20090601-1510

(BMW 335XI Engine malfunction! Reduced power.)

Symptoms: (again.. yes again) My car felt like I was dragging thousands of pounds of weight behind the vehicle. The car would not idle nicely, and eventually died when at idle. It also felt as if the transmission was going to blow up when driving. Vehicle would die while idle or slow which posed a safety hazard in intersections.

Results (verbatim): Issue was Reported to BMW… Please view Part 2 – Contracting the Dealer / BMW of North America

Final Verdict: Proceed to Part 2 – Contacting the Dealer / BMW of North America

Read Full Post | Make a Comment ( 25 so far )

Wavelink Enabler Issues – A story of the Subpar Enablers

Posted on January 23, 2009. Filed under: Software Tangents |

By: Brenton Blawat

Yet again we hit a frustrating snag with the Wavelink Enabler and I have taken it upon myself to add a new section to my blog for Wavelink Enabler Bugs. It’s not that I am frustrated with Wavelink support personnel. They have been more than attentive to my issues and have responded to my calls almost immediately.

The frustration comes with the core of the issue. I am having the same problems in the PPT-8846 Enabler (Released December 2006) as I am having in the MC-55 Beta Enabler (Beta Release this 2009). To Wavelink’s immediate defense, the MC-55 “Beta” Enabler is a “Beta” for a reason. But having an Enabler that has been revised more than once since the release of the 3.50-56 Enabler with the same fundamental issues? – hmmm.

Known Issues:

Issue: Handheld Desktop Displays ; No Method to Get Back to the Wavelink Enabler.

 

Above is an image of my case and point for my frustration. The above graphic displays the exact same issue on both Windows Mobile 6.1 (left) and Pocket PC 2003 (right). Same problem 3 years later?

 

configscreen2 configscreen3

Enabler Config MC-55

Enabler Config PPT-8846

When configuring the Enabler you have the ability to Manage the Taskbar and effectively lock access to the background of the Enabler. While this works most of the time I’ve noticed multiple instances of the Enabler allowing access to the desktop. Additionally, there is no way for the Wavelink Enabler to be accessed again. This is troublesome especially when the Enabler is responsible for Launching Applications (like in my client’s case).

Come on Wavelink; you can do better than this. – I have faith!

Work Around: The only work around for this issue is to restart the handheld. (aka warm boot/soft reset)

Known Versions: 3.50-56, 4-06-13 beta

Bug Status: Reported to Wavelink

 

Issue: Handheld Freezes in the Locked Full Screen Window; No Method to Get Back to Wavelink Enabler.

GetAttachment2

IMG00040-20090113-1517 *
Motorola MC-55
(Agent Not Found)
Symbol PPT-8846
(Update Complete)

 

Both of the devices are frozen at the Update Window Screen. While the PPT-8846 is at a hard lock, the MC-55 will return to the Enabler if touched. * The right image was modified to remove application specific information and agent addresses.

 

The Wavelink Enabler is having issues with the Full Screen Control and Update Window. As shown in the above screens, the Update Windows should be “Hidden” as it’s normal state. For some reason, the Update Window Remains locked and will not automatically unlock itself. The end result is the Enabler is frozen in an Update State. The subsequent updates will not affect the screen locked out state.

Work Around: The only work around for this issue is to restart the handheld or not lock the screen during updates. (aka warm boot/soft reset)

Known Versions: 3.50-56, 4-06-13 beta

Bug Status: Reported to Wavelink

Issue: Software which monitors for state changes of Wireless WILL lock handheld device or cause TCP/IP stack corruption.

 IMG00047-20090113-1522

IMG00046-20090113-1521
Symbol PPT-8846
(Corrupt TCP/IP Stack)
Symbol PPT-8846
(Idle Application Locked)

* The images have been blurred to remove any client specific information.

On the left you will see a corrupt TCP/IP Stack. You also will see that the wireless status indicator is changed to “no connectivity”. In this instance, the application which was sharing the call to the API for the wireless status lost the battle.

On the right, you will see the application (which previously lost the race) is frozen. The wireless feud seems to have caused the login credential boxes (the blank space above the numbers) to disappear.  The handheld is locked and unusable. Please note that the wireless status indicator (next to the battery) is missing from the screen.

Work Around: The only work around for this issue is to restart the handheld (aka warm boot/soft reset)

Known Versions: 3.50-56

Bug Status: Reported to Wavelink

For More Free Training by BIT Tangents: Go to Wavelink Training (Click Here)

Info on Author: Brenton Blawat is a Wavelink Consultant who has worked closely with the Avalanche product for over 5 years. He has integrated Wavelink AMC (and variants) into a multitude of corporations including but not limited to: Seneca Foods Corporation, American Eagle Outfitters, and Alexian Brothers Health System.

** BIT Tangents nor any of its contributors are liable for damages as a result of following these instructions. These instructions are intended as guidelines for best practices and are to be used at the executioners own risk! All re-productions / digital copies of this content must be approved in writing by an authorized representative of BIT Tangents. **

Read Full Post | Make a Comment ( None so far )

    About

    Business and Information Technology Tangents is dedicated to providing quality content while informing the world about technology.

    RSS

    Subscribe Via RSS

    • Subscribe with Bloglines
    • Add your feed to Newsburst from CNET News.com
    • Subscribe in Google Reader
    • Add to My Yahoo!
    • Subscribe in NewsGator Online
    • The latest comments to all posts in RSS

    Meta

Liked it here?
Why not try sites on the blogroll...