TMC VCDS not working(?) 2016 Comfortline

[aim54x]

I have had two attempts to get TMC to enable on my Comfortline using the standard "1024" code, checking that both TP and RDS are enabled in the radio setup.

Any suggestions? Am I missing something? A friend has a VCDS cable so I will be able to try again if anyone has suggestions. Is it worth trying the other codes suggested in the link below (thinking VWTMCProMIB2 32768 )

VCDS/OBDeleven Tweaks: VW Golf MK7

I also could only get the first two changes of the three changes for enabling "off-road mode" .

[DreamensioN]

Did you hard reset your head unit after you did the change?

[HPRS230]

Hard Rest is needed, also is the car out in GPS view? ie not parked in a shed/under ground car park

[aim54x]

Hard reset as in press+hold the power until.it comes back on? Then yes.

I have done this then driven the car around for up to an hour, then continued to use the car as per normal for over 2 weeks. It's almost always on GPS view.

[aim54x]

I currently have a VCDS HEX-CAN cable and double checked the coding last night. I won't get a chance for a decent drive until at least tonight.

Also turned off off-road mode

[DV52]

aim54x: Thanks for the PM. Not really sure what's causing your problem but my hunch is that the HEX+CAN cable is too old for the protocols in the newer style module @ address hex5F (which I assume is OBDII - V2.0, or higher). It should be remembered that the HEX+CAN cable is over 25 years old in it's design and whilst Ross - Tech has supported its continuance, there must come a time when the old technology can no longer support the ever changing newer protocols. My suspicion is that you have found that time!!


As for the specifics of your problem, I've included below the pertinent "yellow" long coding helper screen for Byte 13 of the hex5F module:



Unless you have one of the newer Hex-Net/V2 cable/dongles, you won't be able to access this screen. Nevertheless, the 2 x important Bits to get TMC operational are Bit0 and Bit3. I guess the other way of implementing the TMC tweak is to try to force-enter Btye 13 = hex09 using the old fashion cut-and-paste method (assuming that the current value of Byte13 is hex00).

And, for TMC to work, "TP" and "RDS" need to be activated in the set-up menu for the radio

Don

[aim54x]

Thanks for the reply DV52. I dont have the yellow long code screen...only the blue one, and I cannot see the BIT0, but I did copy the binary for byte 13 which turned to BIT code to 09. Still no love after a hard reset and triple checking the TP and RDS are activated in the radio setup.

Could it be the map version? I am currently running 0915 MRM2 2018, and have seen some chatter on the Tiguan section that TMC stopped working when they upgraded past the 2017 map.

It might be time to invest in a system (the HEX-CAN is borrowed from a good friend)....would you recommend OBD11 as a more cost effective solution compared to a new ROSS-TECH?

I do have to thank you for the incandescent tail light mods!

[DV52]

aim54X: As I said, I'm bewildered as to why TMC is so problematic on your car.

if you have force-fed hex09 into Byte 13 and if it was accepted by the hex5F module, and if the RDS and TP options have been activated, and if you are in a place where the SUNA facility can be received (which is really the Capital Cities) then I'm at a loss to suggest anything else - my apology for not being able to help.

If all the "ifs" above are true, I wouldn't have thought that buying another type of diagnostic tool would solve your problem. However, as to your question about choosing between OBD11 dongle, or a Ross-Tech tool, while the question itself is simple, the answer is far more complex - I believe.

Because I have had a long interest (entirely as a amateur) in the reasoning why folk make different purchasing decisions and as I have a passing acquaintance with diagnostic tools - I've happily participated in quite a few discussions regarding VCDS versus OBD11 (and occasionally, with the inclusion of VCP). My singular conclusion in debating this on different forums with various, invariably very intelligent folk is that its not a one-size-fits-all issue. And, if the potential buyer is completely honest about the reasoning for his/her ultimate choice, its probably not even a purely logical decision - and frankly a logical decision isn't necessary (read my post about what you want versus what you need).

So - my suggestion is to look through the New Kid on the Block thread (latter part) - or simply acknowledge that world is replete with purchasers who are ultimately driven by their own prejudges (I'm one of these) and let your heart guide your decision!!!

Here endeth a gratuitous explanation of my hypothesis on buyer purchasing mechanisms for OBD diagnostic cables!!

Don

[aim54x]

aim54X: As I said, I'm bewildered as to why TMC is so problematic on your car.

if you have force-fed hex09 into Byte 13 and if it was accepted by the hex5F module, and if the RDS and TP options have been activated, and if you are in a place where the SUNA facility can be received (which is really the Capital Cities) then I'm at a loss to suggest anything else - my apology for not being able to help.

If all the "ifs" above are true, I wouldn't have thought that buying another type of diagnostic tool would solve your problem. However, as to your question about choosing between OBD11 dongle, or a Ross-Tech tool, while the question itself is simple, the answer is far more complex - I believe.

Thanks Don, I will continue to drive around in the said vehicle and see if SUNA eventually connects. I am based in Sydney and will be using the car a lot more over the weekend, so hopefully it will eventually decide to do its thing now that hex09 is in Byte 13. I suspect that buying another tools will not solve this issue, but it will give me more freedom to play with other settings.

If I decide to look for, and downgrade my maps to see if that allows for TMC I will keep this thread informed. In the mean time I may continue to ignore that “TRAFFIC” button on the dash.

Because I have had a long interest (entirely as a amateur) in the reasoning why folk make different purchasing decisions and as I have a passing acquaintance with diagnostic tools - I've happily participated in quite a few discussions regarding VCDS versus OBD11 (and occasionally, with the inclusion of VCP). My singular conclusion in debating this on different forums with various, invariably very intelligent folk is that its not a one-size-fits-all issue. And, if the potential buyer is completely honest about the reasoning for his/her ultimate choice, its probably not even a purely logical decision - and frankly a logical decision isn't necessary (read my post about what you want versus what you need).

So - my suggestion is to look through the New Kid on the Block thread (latter part) - or simply acknowledge that world is replete with purchasers who are ultimately driven by their own prejudges (I'm one of these) and let your heart guide your decision!!!

Here endeth a gratuitous explanation of my hypothesis on buyer purchasing mechanisms for OBD diagnostic cables!!

I do agree with you that there are many reasons for our decisions as buyers, and I will sit down later to have a proper read of that linked thread. Thank you for all your help and advice.

[Flipper Dog]

aim54x - been quietly reading your experience. I am in the same boat with trying to reactivate TMC after loading 1010 MRM2 2018/19 maps.
I had had no problem with 0821 MRM2 2017/18 maps and when 0915 MRM2 2018 came out the problems started. What I did was revert back to 0821.
I have the OBD11 and have checked, rechecked and rechecked the settings as you have gone through to no avail.
I have removed the TMC data from the 0821 version and loaded this onto the 1010 version on the SD card - no luck.
I have reloaded version 0821 back with only the map file (country.fcf from file 22/sds/au/en) from version 1010 onto the SD card and still no TMC.
Loaded the original 0821 version back to the SD card and it works in about 2 minutes parked in a garage. So there is something with the country.fcf file that has to be the issue.

End of the day I have just plugged in my phone and google earth maps with traffic via android auto gives better information. Still this is only a band aid fix, as I also don't like having a useless traffic button now.

Also re Ross Tech verses OBD11 - have a Mirco-CAN cable from Ross Tech, support is still there and works great but after using the OBD11 - I am hooked. So much easier and convenient to operate.

[ryan]

Hey all,

I'm some trouble getting TMC to work on my 2017 Mk7.0 GTI w/ MIB2. I'm coding with an OBDeleven, and this is the only tweak that hasn't worked as expected.

Process so far:
- Enable RDS, TP
- Module 5F adaptation "Fee Based Traffic Information (TMC)" 65535 -> 1024
- (drive around)
- Upgrade maps from factory 3G0919866AA 0635 MRM2 2016/17 -> latest 1310 MRM3 2020 from DiscoverMedia2_MRM3_1310_V11.7z
- (drive around)
- Module 5F long coding byte_13_RDS deactivated -> not_deactivated (00001000 -> 00001001)
- Downgrade maps from dd image backup
- Quadruple check RDS, TP enabled
- Reset MIB2 by long pressing power button
- (write this post)

It could well be that I'm impatient and setting byte_13_RDS to not_deactivated will have done the trick by the time I hit the road tomorrow, however I thought it may be worthwhile checking in with the gurus here before wasting any more time. If it does come good then I'll update this post with the procedure that worked.

As an aside, thank you 1000 times DV52 for your fantastic tweaking index and guides.

[dArK5HaD0w]

Hey all,

I'm some trouble getting TMC to work on my 2017 Mk7.0 GTI w/ MIB2. I'm coding with an OBDeleven, and this is the only tweak that hasn't worked as expected.

Process so far:
- Enable RDS, TP
- Module 5F adaptation "Fee Based Traffic Information (TMC)" 65535 -> 1024
- (drive around)
- Upgrade maps from factory 3G0919866AA 0635 MRM2 2016/17 -> latest 1310 MRM3 2020 from DiscoverMedia2_MRM3_1310_V11.7z
- (drive around)
- Module 5F long coding byte_13_RDS deactivated -> not_deactivated (00001000 -> 00001001)
- Downgrade maps from dd image backup
- Quadruple check RDS, TP enabled
- Reset MIB2 by long pressing power button
- (write this post)

It could well be that I'm impatient and setting byte_13_RDS to not_deactivated will have done the trick by the time I hit the road tomorrow, however I thought it may be worthwhile checking in with the gurus here before wasting any more time. If it does come good then I'll update this post with the procedure that worked.

As an aside, thank you 1000 times DV52 for your fantastic tweaking index and guides.

Holy smokes.....that is going way overboard for enabling TMC!!!

It's a simple 2 step process.
1. Change value to 1024
2. Wait about 30 mins for TMC info to start showing.

[DV52]

ryan: I've now done this tweak on many MQB platform vehicles (mk7, Tiggy, A3 etc) - but always here in Melbourne.

Since the early days when I first wrote-up the instructions, I've found on very few occasions that some cars don't like the byte 13 change (I have no idea why, but it does seem to be more prevalent in later model MIB units).

So, given your tenacity in getting TMC to work and if you are still having problems - try reverting the Byte 13, Bit 0 change to 0 (just a guess).

Don
PS: Many thanks for your kind words!

[ryan]

Thanks all, I've been able to solve the mystery. My main issue was rushing to update my maps to the latest version, which evidently lack the required location codes / other metadata to support TMC. (my home address is still wrong in the new maps anyway...)

My secondary issue was impatience after initially setting 1024 with the factory maps, and again last night after restoring the factory maps. With no changes since my earlier post, TMC data started flowing at some point today. Byte 13 turned out to be irrelevant, I've reverted this to the original 00001000.

TMC compatible maps:
3G0919866AA 0635 MRM2 2016/17, factory in my case

http://vw.download.navigation.com/automotive/VW/MIB2/MIB_Standard2_Single_File_MRM2/0635_V05_1911c.xROW2.7z

3G0919866BF 0821 MRM2 2017/18, appears to be the latest that are compatible

http://vw.download.navigation.com/automotive/VW/MIB2/MIB_Standard2_Single_File_MRM2/0821_MP163-1245.xROW2.7z

Incompatible maps:
5NA919866AD 1310 MRM3 2020

http://vw-mapscdn.tdd.adacorcdn.com/DiscoverMedia2_MRM3_1310_V11.7z

So my advice to others with MIB2 Discovery Media is:
- Follow DV52's guide to set module 5F adaptation "Fee Based Traffic Information (TMC)" 65535 -> 1024
- Download 0635_V05_1911c.xROW2.7z from the link above
- Re-format the 8GB navigation SD card as FAT32 with 4KiB clusters (mine was needlessly formatted with 32KiB clusters and couldn't accommodate the slightly larger updated maps)
- Exract the "maps" directory to the card
- Reset the MIB2 by holding the power button
- Be within SUNA coverage: Coverage | Suna Traffic
- Be patient, and occasionally check for TMC events

[turbojetta83]

Thanks all, I've been able to solve the mystery. My main issue was rushing to update my maps to the latest version, which evidently lack the required location codes / other metadata to support TMC. (my home address is still wrong in the new maps anyway...)

My secondary issue was impatience after initially setting 1024 with the factory maps, and again last night after restoring the factory maps. With no changes since my earlier post, TMC data started flowing at some point today. Byte 13 turned out to be irrelevant, I've reverted this to the original 00001000.

TMC compatible maps:
3G0919866AA 0635 MRM2 2016/17, factory in my case

http://vw.download.navigation.com/automotive/VW/MIB2/MIB_Standard2_Single_File_MRM2/0635_V05_1911c.xROW2.7z

3G0919866BF 0821 MRM2 2017/18, appears to be the latest that are compatible

http://vw.download.navigation.com/automotive/VW/MIB2/MIB_Standard2_Single_File_MRM2/0821_MP163-1245.xROW2.7z

Incompatible maps:
5NA919866AD 1310 MRM3 2020

http://vw-mapscdn.tdd.adacorcdn.com/DiscoverMedia2_MRM3_1310_V11.7z

So my advice to others with MIB2 Discovery Media is:
- Follow DV52's guide to set module 5F adaptation "Fee Based Traffic Information (TMC)" 65535 -> 1024
- Download 0635_V05_1911c.xROW2.7z from the link above
- Re-format the 8GB navigation SD card as FAT32 with 4KiB clusters (mine was needlessly formatted with 32KiB clusters and couldn't accommodate the slightly larger updated maps)
- Exract the "maps" directory to the card
- Reset the MIB2 by holding the power button
- Be within SUNA coverage: Coverage | Suna Traffic
- Be patient, and occasionally check for TMC events

Hi Ryan,

I think you may have just saved me a bunch of time - thank you! I've been racking my brain trying to get this to work in my Tiguan - but the link I've found here is, I've got the '5NA919866AD 1310 MRM3 2020' mapping installed, which you've now confirmed isn't TMC compatible!

I will attempt to revert the mapping to the older '3G0919866BF 0821 MRM2 2017/18' mapping and see if it TMC works.