Quote:
|
Originally Posted by trapdoor
What if the car had been ordered with SES active (and the customer had paid for it)? Would that coding still have been deleted?
What if this change had been done by a dealer (and evidently some dealers can and do activate X3's SES)? Would the coding be deleted?
|
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.
Quote:
|
Originally Posted by trapdoor
I wonder how BMW record and act on 'legitimate' coding of options against 3rd party coding of options? For example, when I had Nav retrofitted by the dealer in my E46, they printed out a vehicle options sheet which had the Nav and Bluetooth SA numbers added to the option list. So when THEY do a coding (retrofit), they do record it somewhere.
|
The recording is in the GM and SA coding for the car, which is stored in the car itself.
Quote:
|
Originally Posted by trapdoor
PS. Why are some 'Part Numbers' displayed by the NavCoder scan in Hex, for example the Tel module is :
TEL Telephone:
Part number 01D5321, version HW 09, SW 66, made by Visteon on 32/04 (August 2004)
Diagnostic index 15, Bus index 13, Encoding index 03
|
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