When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
Hmm interesting. Never had issue with panic braking. The collision warning thing works quite well too. I am pretty sure I am running the latest firmware on the modules. Did some major updates after I got the car. I should try cruise control see if I run into the same issues. Not a big cruise control fan.
just coz it came up in the journalist loan car reviews section of Oct 2021 issue of CAR magazine...
Brand new VW GOLF GTI 2.0 TSI DSG
The climate control doesn't work (sometimes)
The touch screen has 3 or 4 second lag (sometimes)
The speedo reading bears no relation to the road speed showing 110 at 70mph (sometimes) And the active cruise control slows for old people in Honda Jazzes in other lanes (sometimes)
its going back for a software update and some fettling
Thank You very much, I've just done my S class 2008, took me about 3-4 minutes, worked perfectly first time. Used DVD rom as I didn't have CD, burned with Imgburn. Enough read topic and go follow instructions.
Now wonder how to update whole NTG 3.0 to latest version
Again thank You
Thank You very much, I've just done my S class 2008, took me about 3-4 minutes, worked perfectly first time. Used DVD rom as I didn't have CD, burned with Imgburn. Enough read topic and go follow instructions.
Now wonder how to update whole NTG 3.0 to latest version
Again thank You
Polar Bear did a great job with this update. Mine just flipped round with daylight saving as it should :-)
Here is a link to the update and instructions for use in a .ZIP file to update your COMAND NTG 3.0 to fix the ongoing date/time issue and setting of the analog clock.
This is my contribution to the W221 community and is the work of several people to get the NTG 3.0 clock and date bug fixed again.
I had a detailed reply typed out but my stupid work computer ate it so I'll be brief. Note: My car is a December 2006 build.
I've had this car for like 4 days now and a few days ago I noticed the date was 2003. I'm like "that's odd." Then I found this thread. Funny thing is, I had this exact same problem on another car, a 2005 Cadillac STS, which also has a nav system made by Denso (I presume NTG3 is also Denso, based solely on the sound the CD changer makes, and I guess also this issue). Unlike my STS where I had to follow a thread for months after the epoch rollover and some poor Denso engineer was able to crank out a fix, the fix is already available for this car.
There was only one concern: do I have bird's eye? I checked and thankfully I do have it so I guess my telematics is suitably updated. Bird's eye confirmed
What I then did was this:
Fired up my 2006 Sony VAIO that still runs Win 10 because it's the only CD burner I have access to. Downloaded zip, unzipped, right click, burn image. Verify. Worked perfect. My super old VAIO burning the ISO with no problems.
Went out to car. Eject all changer media. Insert firmware CD into slot 1. Enter engineering mode by pressing COMAND wheel right, massage/lumbar and mute. I did this all with my right hand and did not need to press * as reported by others. Don't make this harder than it needs to be.
Select update. It took all of 5 seconds and then seemed to finish with no errors. It did NOT, however, reboot COMAND. So I tried it again. Same thing, finished fast, no reboot. I decided to shut all the systems off and then go for a short drive. I did that, came back, and date was now correct. That was easy. I admit there are multiple stages where you can get tripped up but it seems like a very easy process to me. Just posting this to give others confidence.
Various S/W versions. Select update.... Date is now correct!
Dang. That's what I get for being cocky. I am still on release 422. And the date is back to 2003 (actually shows 2002 in the GPS menu). WTF? I tried it a third time and it flashed for like a few seconds and then said completed successfully. But no reboot and the version number is the same. What gives?
Scrolling up it looks like I am having the same exact issue as elmerfud. And the conclusion was.....needed to update his Telematics? Even though mine does have Bird's eye?
been at it for more than a year - not sure what drives it - in one later thread, Polar Bear did mention it might be something about older not fully up to date cars don't load the update.
With it running to keep volts at grown up level would be a good idea - as would a DVD drive that NEVER saw anything other than update discs for telematics and mapping - wearing out something critical for something irrelevant doesn't seem a good trade off to me - did you follow the whole thing about inserting the disc before going in ENG menu and getting the corrected failed message before trying...
I did it running and not. That doesn't matter unless the battery is trash. I don't think there is anything wrong with my drive. Plays CDs and loaded this thing with no issue. It even said the update was successful. This is not a mechanical issue. I don't know what's with all the superstition about the instructions. Yes I checked the MD5, too. Matches. You insert the CD, go to eng menu, select update. That's it. But it didn't work on my car and is EXACTLY what elmerfud experienced if you go up and read his. It didn't say update not found. It didn't say update error. It didn't say update not successful. It clearly read the CD.
you are speaking as if you understand a w221 - these things are magic and do whatever they want as they want - 2003 cutting edge technology that's now nearly 20 years old
and YES 10 mins on battery alone is enough to keel over and fail (and yes I did read you did it running), I started with my reply - a bloke in UK has been trying for more than a year …..
Merc programming is designed to be reliable at 14.2 v not 12.5 v
Right but given the older SW on my car, isn't the current/best hypothesis that I need some kind of telematics update to even accept this GPS fix? If so, why are we talking about the battery, and CD drives, and Windows CD burning and everything else? I mean those are technically things that can impact anyone but my situation is my situation.
Plus elmerfud had the exact issue and went through the ringer with all of these same suggestions with no improvement, so.....it's probably not us.
Right but given the older SW on my car, isn't the current/best hypothesis that I need some kind of telematics update to even accept this GPS fix? If so, why are we talking about the battery, and CD drives, and Windows CD burning and everything else?
as you now become only the 3rd person where it doesn't want load (that I know if) trying to ensure the best starting point for other's to try
1) only put the update file on the disc (not the pdf as well)
2) use a CD-R (normal high quality old style disc - some trendy purple trash isn't read by the old / out of date firmware of disc material's it's drive accepts)
don't use a RW
don't use a DVD of any description (the car looks for a Mercedes update CD)
3) keep the volts up (as its likely to work better - you are programming an old computer that was designed to only load updates if volts above 14.2v)
4) don't expect a tired merc drive to cope - they are built for 3 mins use not everyday for 15 years
5) its never a good idea to trust Microsoft to write a cd that functions, (in the last 15 years all the experts left and its now only compiled junk by 3 year old's with a desire to make your life a misery)
6) follow the odd ball instructions to load - it took 16 years before anyone found the Eng menu on the w221 - who knows if merc ever expected it to function - every other update was done in session with dealer diagnostics tools
the only way to know if its caused by old software is to apply the last update and if they still didn't add the clock update - try it after - its just as likely a tired drive or nasty cd
When I updated my 2005 Cadillac STS for this exact issue, I made an image the same way with the same old laptop using the same media (CD-R). Insert into map DVD drive. It reads it, does the update and it's done. Again believe it is also a Denso system. Not saying people haven't burned coasters, or have crap batteries, don't have the dexterity to get into the engineering menu, or whatever other problems ail. Just looking for closure on MY issue that this is beyond action I can take without a Star system or visiting the dealer. And not because of process of elimination. I was hoping for a smoking gun. Like, if this version date is older than this, update telematics.
Here is a link to the update and instructions for use in a .ZIP file to update your COMAND NTG 3.0 to fix the ongoing date/time issue and setting of the analog clock.
This is my contribution to the W221 community and is the work of several people to get the NTG 3.0 clock and date bug fixed again.
If you decide to install this fix, I would be interested in hearing the outcome. I am hoping for 100%!
Hi
Is there an idiots guide to doing the clock fix on the w221? just bought a 2008 s500 model and the only thing that annoys me is the clock not being correctable as there is no other clock on view in the car. I'm not great with IT stuff and I tried to access the link you put on here (https://resources.mbdx.us/files/tele...E_TIME_FIX.zip) (I'm based in UK) but it just keeps timing out. If there's an A to B idiots guide/video on how to do this, I'd be eternally grateful. Thanks again.
download it
then open
then check file hash to prove u got what u thought u downloaded
then write JUST the update .iso thing to a quality CD
then read the instructions
do as it says with the engine idling
10mins later the date and the clock should correct themselves - if its outside
Can you guys do us a favor and post your software dates? I want to establish correlation (and ideally causation) that my seemingly older SW is not allowing this update to take.
Can you guys do us a favor and post your software dates? I want to establish correlation (and ideally causation) that my seemingly older SW is not allowing this update to take.
it doesn't work like this, what you have is hardware build date not software - you also have the WRONG colour background on you hardware dates how come ??? it should look the same beige menus not blue.... Blue was the NTG3.5 set up and yet lots of your stuff is old kit ???
the only thing I know of it to print the gibberish out from STAR - it can tell you if it needs an update too... (when its been online to germany) but its usually lies, as it is very easy to get muddled with other minor faults making it say there's an update, but if you fix the unrelated fault, it can say its happy - which again doesn't make sense unless
merc forgot to adopted the clock fix on their systems (likely)
but was then clever enough over Chrimbo and New Year LY to update their systems and then spot my car was now correct