Yes, they are all correct. Well, the adaptation is right - I can't tell you about the long-coding though.long code =
Long coding: 02730008FF00000051510001000928001F0100D601200100C7
adaption code is 1024 is this correct for aust?
@KFiddy: yep looks OK - I've had other conversations with Aussies that have your MIB2 and that have had problems with activating TMC using 1024. ALL I can suggest is to try other codes (32787 has been used in Australia on Audi MMI units - worth a try)long code =
Long coding: 02730008FF00000051510001000928001F0100D601200100C7
adaption code is 1024 is this correct for aust?
VW MD reading your email: There's countries other than England?Would you believe, The Scottish Government have been more than helpful on this? I'm as shocked as you are - someone actually had time to look into something other than Independence...
The wonders never cease!
Unfortunately, it's not good news... If what they said in their letter to me is to be believed, Transport Scotland actually took my question to INRIX themselves, who confirmed the following:
View attachment 220882
So...it looks like...VW don't actually make use of this? Which would make sense, the unit doesn't have to be capable of decoding the data from INRIX to be able to display them as a service provider in the GEM of the unit, when in an applicable area.
This is, however, considerably poor show on VW's part. As TrafficMaster do not cover beyond Perth, they've left an entire part of the country without access to this -whether it's basic, if I was someone who had paid for a MIB to be installed (particularly a MIB1, with no Car-Net) from factory, I would be really pissed off that I'd paid for functionality in a car that I'd never have.
But why list them as a provider without making use of their service? There is always the chance that Traffic Scotland got the wrong information -
I imagine this comes as no surprise - I'm not 100% sure I'm overly surprised myself, but I'm going to pose the question VW and see what they say. I'm sure this will be highly entertaining and not at all scripted. But I've found the email address for VW UK's MD, so if I get a crock-shit response from them, I'll on-pass to him and see what he has to say for it.
I mean, just how much excess carbon are they willing to pump into the atmosphere, exactly? The confirmed the sale of Bugatti to Rimac in May this year, they're not exactly in a position to handle another law-suit for a carbon-copy of the one they've already got...
Aye, he'll be very swiftly reminded we're the one his lot couldn't conquer, all those times they triedVW MD reading your email: There's countries other than England?
I've been on a mission here in New Zealand to try and get my TMC working... and this might be helpful in the UK as well..
A little bit of background, like Australia, NZ is served by two TMC providers... SUNA (intelematics) and HereTraffic.
I would occasionally get an update on my unit from SUNA, but it would be in weird locations and only appear for a short while before disappearing again.
In order to check if there was a config issue or it was just really shit reception I used my SDR (Software defined radio) and using a couple of tools RDSpy and redsea to check what messages were been sent over the FM radio in my area, the location data was encrypted but I could decode what type of message it was e.g. road works, accident etc.
What I discovered was that SUNA is really shit, they broadcast really infrequently, I'll get some messages during rush hour, but they disappear soon afterwards, where as HereTraffic broadcast throughout the day and a lot more messages compared to SUNA, i would say close to 20:1
You have probably come across the Drive.ru pages when searching for TMC info, They managed to figure out the encryption setup for russian cities, so I spent some time decoding what they did and using the Green engineering menu I was able to create my own PayTmc.json and PayTmc_aus.json with the required definitions for hereTraffic.. basically I need the Station ID, Extended Country Codes, and an encryption index key, the rest of the info is the same as what was in the SUNA config. (This is for the Discover Pro units, not Discover Media Nav)
the SID and ECC was easy to find via GEM (also via the SDR), the encryption key I did not know, but I learnt from a drive.ru post that there is only 8 possible keys...
So I sat in the car with my laptop, started with encryption key index 1 and loaded the new files onto the media unit, tested, increased the index, re copy... rinse and repeat till I found the right index. I am going to release the setup on github after I make a trip up north to Auckland, to make sure the values don't change between major centres in NZ... if SUNA config is anything to go by they should stay the same in NZ, but Australia for example the settings changes per state.
I also have a VW/Delphi Discover Media Nav unit on my test bench, so I am starting to have a look at the config files, if the TMCprovider files on the SD card are anything to go by, there isn't any mention of a SUNA (1024) config on the map card... so hopefully there is something in the base firmware, I have seen messages referring to SUNA in the serial debug output so hopefully the config is there somewhere.