TMC VCDS not working(?) 2016 Comfortline

[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/au...1911c.xROW2.7z

3G0919866BF 0821 MRM2 2017/18, appears to be the latest that are compatible
http://vw.download.navigation.com/au...-1245.xROW2.7z

Incompatible maps:
5NA919866AD 1310 MRM3 2020
http://vw-mapscdn.tdd.adacorcdn.com/...M3_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/au...1911c.xROW2.7z

3G0919866BF 0821 MRM2 2017/18, appears to be the latest that are compatible
http://vw.download.navigation.com/au...-1245.xROW2.7z

Incompatible maps:
5NA919866AD 1310 MRM3 2020
http://vw-mapscdn.tdd.adacorcdn.com/...M3_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.

[gh172]

Same for me, I have a incompatible map also. Pain in the Butt!!

Sent from my Pixel 2 XL using Tapatalk