cmy
New Member
Posts: 6
|
Post by cmy on Apr 22, 2022 11:15:14 GMT
Hi - I have a Golf eTsi 1.5 model 21, built Week 42/2020 (SOP1 pre week 28/20) with all features included Side Assist with blind Spot Warning. Software ist 1896. I tried now to code 3C (Side Assist) to activate the Exit Warning function ASW with Byte 0 - Bit 2 off and Bit 3 on (advice newty in Motortalk) Unfortunately the change was rejected with "error at writing...". Can anybody help me? What means the other point "no ASW-HMI-modules"? (I tried to change it, but it was rejected too). Thanks for your help.
|
|
|
Post by newty on Apr 22, 2022 12:17:49 GMT
When you cannot code anything, this looks like another problem. Did you open the hood before?
Can you please tell us you software version of 3C? From my own research, I can definitely tell you that with Softwareversion 0284 this works.
ASW-HMI is not needed and not supported by the Golf (this will enable electric child locks to close with the ASW or to actuate some - in my opinion never seen - vibrations motors)
|
|
cmy
New Member
Posts: 6
|
Post by cmy on Apr 22, 2022 13:58:10 GMT
Hi newty , I can code other things with my new OBDeleven Nexgen: I did not open the hood (Motorhaube) during or before coding. Here the details of the software of the 3C: 0284 Thanks again in advance for your help.
|
|
|
Post by newty on Apr 22, 2022 14:05:32 GMT
Generally, there is the diagnosis firewall active in gateway, which should supress all writing datagrams from the OBD port. Obviously, this does not apply to all communication relations.
You can disable the firewall by opening up the hood. So for coding any MBQw, please at least pop up the hood (just popping it open is fine) and turn on the ignition.
The software of your side assist looks good to go, so I would not see any unresolveable issue here.
|
|
cmy
New Member
Posts: 6
|
Post by cmy on Apr 22, 2022 16:09:56 GMT
Have immediately tried with open hood - unfortunately does not work (neither with bits change nor with direct change in the longcoding menu) - too bad. In the meantime I searched in the forum and found the thread here with the statement of Don: forum.obdeleven.com/thread/14431/audi-a3-exit-warning-codingdinksy : hmm.... Yes, I understand how exit warning on the side mirror works when the car is stationary. What I'm not sure about is- does the software in your 2 x rear-facing radars support this function (not all modules support the function)? Could there be something to it? Thanks
|
|
|
Post by newty on Apr 23, 2022 17:04:10 GMT
Signatur beachten! Actually the exit warning was the first thing I coded on my G8
My car was shipped with the same software version on the side assist as yours, so at least enabling it in the 3C should work.
Either you are facing a bug there or something else is wrong. I would suggest deleting all data from OBD11 and try again.
Of course, the ASW should be supported by the Gateway and the Infotainment. But since you are having 1896 and therefore either the Post KW48/20 SOP or the the TPI for earlier cars, I see no problem there
|
|
cmy
New Member
Posts: 6
|
Post by cmy on Apr 23, 2022 22:12:12 GMT
Thanks again newty I will try that tomorrow. Btw I have a Pre KW48/20 SOP1 and got the TPI Update to 1896 a month ago. I tried the OBD11 app with android and apple handy: Both reject the ASW coding with "Fehler beim Schreiben der langen Codierung". Other question: What means "Produktionsmodus/Deaktivierung Spurwechselassistent und Ausstiegswarnung" in the OBD11 app? You can set to aktiv or nicht-aktiv.
|
|
cmy
New Member
Posts: 6
|
Post by cmy on Apr 24, 2022 9:46:41 GMT
Hi newtyThank you very much - deleting and reinstallation of the OBD11 app, a new scan, hood open, security access 20103 and longcoding the ASW as you recommendet helped: ASW is up and running. I am really surprised of the design and the possibilities of OBDeleven NexGen. Helpful and not expensive.
|
|
|
Post by newty on Apr 24, 2022 10:41:14 GMT
Good to hear! So there is still a problem with cached data and reinstalling the app or wiping data is still a good approach when something just feels plain odd.
Production modes will disable some features which are not wanted or even harmful for mid production / engineering testing. The control unit then reacts as is coded otherwise, but does not actually work. These are undocumented mostly, as they are either used automatically during production or meant for specific smoke or box tests
|
|
dwj22
New Member
Posts: 43
|
Post by dwj22 on Apr 25, 2022 17:27:39 GMT
Sorry to jump in. I want to activate this on my mk8 R. Can someone tell me exactly how to do this and where to go in the app? Thank you
|
|
|
Post by newty on Apr 26, 2022 5:29:27 GMT
Before starting: Open Hood
Control Module 3C Long Coding Set Exit Warning to with_ASW Apply
Done. If you are unsure about those steps, watch a few tutorials for the overall handling of the app.
|
|
dwj22
New Member
Posts: 43
|
Post by dwj22 on Apr 27, 2022 21:19:10 GMT
Thank you. Where is the what place to watch? YouTube?
|
|
OwnerTR
Junior Member
Seat Ateca FR
Posts: 90
|
Post by OwnerTR on Aug 22, 2022 15:31:04 GMT
It gave the same "31 function not available" error with OBD2 Pro for my Caddy 5 vehicle. But I activated it with VCDS and it works.
|
|
|
Post by jesse93 on May 17, 2024 22:39:17 GMT
I tried several times to code this for the Octavia NX. It has the same software and hardware information as stated above. On iOS it sometimes just keeps "writing" and never stops. Only solution is to hardclose the app. If i'm not getting the constant "writing" message, i'm getting "function not available". On android the same message "function not available".
I have also tried deleting and reinstalling the app, but still the same message. Approach is as follows: Open the hood, connect OBD11, Scan, fill in security access code (20103) and try to long code to Exit warning to with_ASW. Am I doing anything wrong? Am I using the wrong security code?
|
|
|
Post by blizzard60 on May 21, 2024 3:42:24 GMT
I tried several times to code this for the Octavia NX. It has the same software and hardware information as stated above. On iOS it sometimes just keeps "writing" and never stops. Only solution is to hardclose the app. If i'm not getting the constant "writing" message, i'm getting "function not available". On android the same message "function not available". I have also tried deleting and reinstalling the app, but still the same message. Approach is as follows: Open the hood, connect OBD11, Scan, fill in security access code (20103) and try to long code to Exit warning to with_ASW. Am I doing anything wrong? Am I using the wrong security code? My OBDEleven was the same with this coding. ODIS worked fine though. I never tried deleting the app though. Maybe some sort of bug with this coding?
|
|
|
Post by brkica on May 21, 2024 12:56:00 GMT
I noticed that for some work especially in the SFD protected units, you need to use the next gen OBD11 device. The first gen simply fails to execute some coding changes.
|
|