|
Post by s2artfraser on Mar 30, 2022 8:34:34 GMT
Hi I am trying to modify light sensor EINSCHALTGRENZE_CHO_LHO and the value is 600lx.however OBD will only let me enter a value between 0-255. Can you please let me know how to modify it. Thank you Stu
|
|
|
Post by dv52 (Australia) on Mar 30, 2022 21:59:49 GMT
s2artfraser : hmm.......... this is the same question that you posted in the Audi A3 forum - please don't multiple-post the same question (see the forum rules)
So, it's a programming problem with the way that OBD11 reports this adaptation channel. The message that OBD11 displays is meant for channels that use a hexadecimal number for their value.
The number 255 in decimal = FF in hexadecimal (it's the largest value possible for a 2 x digit hex number) = 1111 1111 in Binary. There are lots of adaptation channels that use hexadecimal numbers.
However, the channel EINSCHALTGRENZE_CHO_LHO does not use hexadecimal numbers - the message that OBD11 displays is clearly wrong because the default factory value for this channel is 600!
Just ignore the 0-255 limitation and enter a decimal number - it should be accepted with the security code 31347
Don
|
|
|
Post by s2artfraser on Mar 31, 2022 8:59:28 GMT
Hi Don
applogies for listing this twice in the A3 forum
Thankyou for getting back to me, i will let you know how i get on
I was trying convert 600 into binary however i wasnt sure what the maxiumum value would be and couldnt work it out, ive sent a message to OBD to change it to max 65535
Thanks Stuart
|
|
|
Post by dv52 (Australia) on Apr 1, 2022 1:48:13 GMT
hmmm.........OK -maybe this channel does use hexadecimal (because 655345 = hexFFFF)?
|
|
|
Post by s2artfraser on Apr 1, 2022 9:45:54 GMT
Hi Don,
It wouldn't let me put in the security access code, 31347 - Am i missing any zeros 000031347 or putting it in incorrectly or these there another code?
Thanks Stu
|
|
|
Post by dv52 (Australia) on Apr 1, 2022 19:36:13 GMT
s2artfraser : The venerable 31347 has been the correct code for the hex09 module for many years on MQB platform cars - so it most definitely is correct. And no, security codes for these module types are a 5 x digit number only. So, here's the thing - UDS/ODX protocol modules (like those in your Audi) are very temperamental where security codes are concerned. They lock-out for a period of time after just a few attempts to enter an incorrect code. I suspect that this is what's happened in your case. Once the module is "locked-out", the count-down timer is only active with the ignition turned-on (it's called a "T15" voltage). The lock-out time varies, but nominally 5-10 minutes.
You can tell if the module is locked-out using the instructions below (the Android version is very similar): Notes:
- The number circled in the last screenshot should be less than, or equal-to 3 (preferably zero) for the module to accept the correct security code.
- If the module is locked-out, the number will automatically return to zero when the count-down timer resets.
- The lock-out timer will count-down only with the ignition turned-on (i.e. T15 voltage must be active)
- You can manually reset the number back to zero by exiting out-of the module and then selecting it again - but this manual reset method only works if the module is NOT locked-out (else the time-out period must elapse for the number to automatically reset)
Don
|
|
|
Post by s2artfraser on Apr 2, 2022 10:37:28 GMT
Hi Don thank you for getting back to me I couldn't find "security" does not appear to be in the list. Should I have it in developer mode when trying to change the settings on the original post as it says 31 function not available when I am trying to modify light sensor EINSCHALTGRENZE_CHO_LHO
Thanks Stuart
|
|
|
Post by dv52 (Australia) on Apr 2, 2022 21:12:57 GMT
@2artfraser: Because you first posted in the Audi A3 8V part of the forum- I have been assuming that your car is built on a MQB platform. But it seems that your car is the newer S3 8Y model
This being the case, your car is likely to use the newer SFD access protocols rather than the older security codes. This explains your observations
To allow access to the module, you will need to use an entirely different method - read the SFD instructions HERE
Don
|
|
|
Post by s2artfraser on Apr 3, 2022 22:32:26 GMT
Hi Don thank you for getting back to me I followed the link and unlocked SFD however it still came up with 31 function not available when I am trying to modify light sensor EINSCHALTGRENZE_CHO_LHO
Thanks Stuart
|
|
|
Post by dv52 (Australia) on Apr 4, 2022 7:42:10 GMT
Stuart- bummer!! I tried changing this channel on my "virtual MQB car" (my test-bench - see below) and it worked OK - but this is a non SFD platform
Don
|
|
|
Post by denzel on Nov 23, 2023 17:37:37 GMT
hi don i have a 2007 audi a4 b7 cvt transmission i wanna do calibration and adaptation am using obdelevn pro pack its asking for channel 0-255 would you assist thank you
|
|
|
Post by dv52 (Australia) on Nov 23, 2023 19:29:24 GMT
denzel :Hi. OK - there is a huge difference between OP's car when this thread was started and your MY07 Audi A4 B7. Your car has a PL46 chassis and OP's car has a MQB-evo platform - so very different!! The modules on your car do NOT use the newer style UDS/ODX protocols - which means that they do NOT use alphabetic names. Instead, the A4 modules use numbers for the channel identifiers (hence the request for 0-255). I'm not familiar with these older style modules - I suggest that you ask your question in the appropriate part of the forum Don
|
|