|
||||||||
| Xoutpost server transfer and maintenance is occurring.... |
| Xoutpost is currently undergoing a planned server migration.... stay tuned for new developments.... sincerely, the management |
![]() |
|
|
LinkBack | Thread Tools | Display Modes |
|
|
|
#1
|
|||
|
|||
|
Anyone else get service done but the iDrive info is never updated?
This has happened twice so far and I think it's happened again with my front brakes.
First time it was the state inspection date (but I changed it myself after the fact), then it was the brake fluid (which is telling me I need service but just had it flushed a month ago) and now my front brakes say they're due to expire in 2000 miles but they seem fine. Also, I had them look at the brakes last month and they said they will not replace them under the maintenance plan yet because there's too much pad life left. I recall only seeing the rear brakes done on the service history when I bought the truck in January and that is reset and shows 28k miles left of life in iDrive. My maintenance ends 8/15/11 so I've been trying to be harder on the brakes to wear them down to sneak in one last free change before it expires. Any insight is appreciated. |
|
#2
|
||||
|
||||
|
There are different types of triggers for iDrive warnings.
The state inspection and the brake fluid are simple date reminders. The vehicle doesn't know the work was done. When you complete the work, you just reset the date for another year or two years. If the tech didn't do it, you can do it. There are condition-based warnings, such as oil service. Those depend on driving history, oil condition, etc. The brake pad warning is a combination. There are two trigger points in the pads for both front and rear, one at midlife and one just prior to wear out. In between those trigger points, the vehicle calculates likely pad depth remaining but it isn't particularly accurate, so when a hard trigger point is reached it corrects the readout. That is what causes a jump, showing as reduced pad life remaining. A physical inspection will confirm the actual pad life remaining. My service advisor does it with a hand held tool in the drive-through bay, reaching through the wheel. It takes about 15 seconds.
__________________
2007 X3 3.0si, 6 MT, Premium, White Retired: 2008 535i, 6 MT, M Sport, Premium, Space Grey 2003 X5 3.0 Steptronic, Premium, Titanium Silver 2002 325xi 5 MT, Steel Grey 2004 Z4 3.0 Premium, Sport, SMG, Maldives Blue |
|
#3
|
|||
|
|||
|
Quote:
Howse that? Familiar with the wear sensor, but not the midlife one.... A |
|
#4
|
||||
|
||||
|
The E53 had a single trigger when the pads were worn out. The E70 uses a multi-stage trigger. It is combined with the CBS brake pad wear calculation based on number and severity of stops. You can see inconsistent estimates when it can't figure out what is happening. My E60 got new (dustless) pads at 500 km. It showed 60,000 km remaining on the fronts. It still showed 60,000 km remaining after 3 years (the pads were still good, but it should have moved somewhat). When the sensor eventually wore through the first loop, it would have jumped.
More details: https://wiki.bentleypublishers.com/d...W+5+Series+E60 My experience is with the E60, but the E70 is on the same platform. BMW changed the sensor design when they went to iDrive. I think it is a safe assumption that the E70 is the same as the E60, but if not I stand to be corrected.
__________________
2007 X3 3.0si, 6 MT, Premium, White Retired: 2008 535i, 6 MT, M Sport, Premium, Space Grey 2003 X5 3.0 Steptronic, Premium, Titanium Silver 2002 325xi 5 MT, Steel Grey 2004 Z4 3.0 Premium, Sport, SMG, Maldives Blue |
![]() |
| Bookmarks |
|
|
|
|