Quote:
|
Originally Posted by KiwiJochen
No, because if the car was ordered with SES, or if a dealer enabled SES officially, then the SES option would be coded in the SA coding (SA = Special Accessories) of the car, which is stored in the instrument cluster. NavCoder cannot, unfortunately, change the SA code. So when NavCoder enables SES, it is a change that will always be overridden by a dealer if the dealer recodes the ULF.
The recording is in the GM and SA coding for the car, which is stored in the car itself.
|
Ah, now that explains it. Pity that you can't code the SA area though..
Quote:
|
Originally Posted by KiwiJochen
This is interesting - it may be a part number format that NavCoder cannot handle, hence it displays the raw hex. Please send me a private email with a copy of the log file form when you read the telephone identification data. I can then check how NavCoder deals with the data from your car, and correct any bugs etc.
I need the raw hex showing NavCoder asking for the data, and the data being sent from the TEL to NavCoder
And I also need to know what version NavCoder you are using - current version is v2.3.1
Regards, Jochen
|
I'll have to connect to the car again tomorrow, as I didn't have a logfile saved. I just saved a list of visible devices. I'll send you that too, as BODY, EWS, PDC, 66, RAD, TEL and TV are all showing a hex part no.
What sort of log do you want? A log of the device scan?
Mark.