|
|
Post by tachyonic on Aug 1, 2024 9:12:41 GMT
I lost the only key I was given for my audi s3 2022 8y. The worst part is my car is 4 hours away from me at a audi dealer cause I lost it on vacation and now its stuck out there. I purchased a new key from audi and they can’t program it cause they said they were getting an error on one of the modules. Come to find out they are blaming me for changing the rear tail light animation with obd11 to the rs3 one and so I sent them the obd11 to revert the coding. They said they can’t get the car fully into accessory mode and to connect to the app even though the dashboard and lights come on and I tried hitting up support via live chat and clicked on speak to agent but they aren’t responding in a timely manner and this is pretty urgent! I just don’t know what to do like it will cost a ton to get it towed and they said I would be out of pocket if they replace the faulty module…. Does anyone know how to get the car into accessory mode so I can revert the coding and get a key programmed to my car?
|
|
|
|
Post by whataboutthis on Aug 1, 2024 14:20:29 GMT
I dont know the answer but support normal responce time line is 6 - 24 hours so you will be very lucky to get a quick response I am afraid.
Are the Audi Garage actually using your OBD11 Dongle to try and use OBD11 (vag app) or are they trying to use VAG/AUDI Software to reprogramme
If they are using OBD11 Then if it connects to the car (obviously Bonnet open) then it will give you error messages if it cant connect.
If it can connect do the actually know how to revert the changes using OBD11
|
|
|
|
Post by tachyonic on Aug 1, 2024 16:43:28 GMT
I dont know the answer but support normal responce time line is 6 - 24 hours so you will be very lucky to get a quick response I am afraid. Are the Audi Garage actually using your OBD11 Dongle to try and use OBD11 (vag app) or are they trying to use VAG/AUDI Software to reprogramme If they are using OBD11 Then if it connects to the car (obviously Bonnet open) then it will give you error messages if it cant connect. If it can connect do the actually know how to revert the changes using OBD11 . Yes I let the dealership know how to use the obd11 and sent them my obd11 device to use. Dealer says they can’t revert the changes I made with their devices and so I sent them my obd11 to try and revert it but they are having issues with it going into accessory mode fully but I told them to send me a screenshot of the actual error which they should send me today. Also I messaged support 24+ hours ago and no response still. |
|
|
|
Post by whataboutthis on Aug 1, 2024 16:55:05 GMT
Afraid with support you just have to keep pushing, i also find if connecting via a laptop that when I closw firefox then I loose the chat I was having and have to start again. Not the same issue when using phone.
Cant say I understand what Accessory mode is because from what I have read this is just when the ignition is turned on but you have not started the engine.
If for some reason they are having an issue they could always turn the engine on and then try coding changes with obd11 dongle
|
|
|
|
Post by tachyonic on Aug 1, 2024 18:58:11 GMT
Car is not able to be started as there is no key programmed to it.
|
|
|
|
Post by whataboutthis on Aug 1, 2024 21:25:45 GMT
Sorry brain in gear now.
Hopefully the Audi Dealership will be able to get OBD11 Working on ignition only.
I have also raised an issue directly with support pointing at this thread and saying you have already raised this request via the help system, fingers crossed they get there act together for you.
|
|
|
|
Post by tachyonic on Aug 2, 2024 0:03:59 GMT
Thanks! the dealer is saying they are now having trouble unlocking sfd to get into adaptations. Does that sound like the accessory ignition is working then? Do they need to do the changes through garage? I saw a new vehicle when I logged in on the obd11 to take the screenshots. Do I need to remove the obd11 device from my phone for them to be able to connect to it? Should they do a soft or hard reset or does that not actually change the coding back to normal? I activated the pro plan a week ago for email I had them log into.
|
|
|
|
Post by whataboutthis on Aug 2, 2024 9:19:02 GMT
No you dont need to remove the app from your phone.
I have the app on multiple phones and have no issues.
When you set your app up did you make it so it automatically connects to SFD or do you have to do it manually.
I would not do a reset (but I am not an expert) because from memory that will revert to factory (part factory not how the car came to you).
Are they able to connect to the car and see the control unit and when they go into the control unit if they try and recode what error message do they get
|
|
|
|
Post by tachyonic on Aug 2, 2024 17:21:48 GMT
"I am able to gain access and change/perform adaptations for any other module except the central electronics module. I did a screen recording but the file is too large to send . I am going to edit the video to reduce the file size. The central electronics module is requiring the ignition to come on." The audi dealer just sent me this so some progress!!! They were using the wrong app lol!! So I asked them to make sure all doors are unlocked and to have a door open as well before they try it and I hope it works but any other thoughts? I'm pretty sure the ignition didn't need to be on for any coding I ever did to the central electronics. They just sent me an update "All the doors are unlocked and the drivers door is open. It is still requiring the ignition on(accessory mode on) All other modules are ok. I am pretty sure there is a problem/fault with the central locks module."
|
|
|
|
Post by tachyonic on Aug 2, 2024 18:06:16 GMT
|
|
|
|
Post by whataboutthis on Aug 2, 2024 18:45:52 GMT
The picture is of control unit 17 (dashboard) do you have any faults on Central Electrics (09), if possible can you clear them and see if that helps.
I thought all you did was touch the start button and that took you into accessory mode and then you could code.
Support have been hopeless no feedback did they get in touch with you.
You are saying you cant code the central electronics, what error message do you get and I presume the bonnet is unlocked otherwise no SFD Coding.
|
|
|
|
Post by tachyonic on Aug 2, 2024 18:58:39 GMT
There is two image links there sorry about that! The first one is the central electronics 09 which is giving them an error before they can even get to the options for selecting adaptations or reset or clear. Support responded told me to make sure I’m using the vag app and that was an issue the dealer was using the bmw app but now that they are using the correct vag obd11 app they can get access to all the modules except the central electronics which is the only one I need to revert!
|
|
|
|
Post by tachyonic on Aug 2, 2024 19:32:53 GMT
|
|
|
|
Post by whataboutthis on Aug 2, 2024 21:43:36 GMT
Well good news that support came back but as its the weekend they wont be back online till monday I am afraid. From the video it shows the control unit 09 in red which means there is a fault but it probably just the one you get with SFD (B184C00) There appear to be lots and lots of errors on the car have they run a scan to see if there is anything that could cause this issue. Afraid this is beyond my knowledge but maybe dv52 (Australia) may have some idea's to get the dealership to look at. |
|
|
|
Post by tachyonic on Aug 2, 2024 22:13:34 GMT
"I have sent you the videos and have shown you that I am able to access and perform adaptations to other modules on those videos. The hood has remained unlatched. The doors cannot be locked so they have been open the whole time, I believe I have shown you the sfd is unlocked on the video and have done what you have asked. Now the only thing new you mention is the seat belt clicked. Is there anything else that needs to be done when connecting. I do not think the seat belt makes a difference, but I can do that. Again, I am pretty sure there is something damaged internally on that module. I was able to access the module and it looks like it had several logs with attempts to do some modifications or coding. I will try with seat belt clicked." Audi dealer
I'm positive nothing is damaged with the module I need this figured out so these guys don't try and install a module and charge me over 1,000$ cause it's not under warranty since I modified the coding with obd11.
|
|
|
|
Post by dv52 (Australia) on Aug 2, 2024 23:11:00 GMT
tachyonic : Hi Let's start at the beginning - meaning that we need to understand how this car was built and we need to see EXACTLY how the modules are behaving. First activate Freeze frame data on your account - see HEREThen post-up a copy of the SCAN reports. To do this follow the steps below
- Fire-up OBD11 software on your mobile-phone/tablet
- Select Garage tab in the Home screen (lower left-side)
- If you have registered multiple cars on you account - select the the correct vehicle
- Scroll-down and select History
- Follow the screen instructions below:
 - On the 2nd screen above - deselect ALL entries except Full scan
- After you receive the Email that you sent to yourself (last screenshot) - add the SCANs file as an Attachment to a new post.
Don
|
|
|
|
Post by tachyonic on Aug 3, 2024 2:07:18 GMT
Thanks so much Dv here is the log file history! Attachments:OBDeleven_Log.txt (11.95 KB)
|
|
|
|
Post by dv52 (Australia) on Aug 3, 2024 8:23:11 GMT
tachyonic : So, here's the thing - I always have problems with SCANs from 5WA chassis vehicles like this because MQB-evo platform cars invariably have lots of errors even though they operate OK.
There are a number of Technical Service Bulletins (TSB) / Technical Product Information (TPI) from Audi/VW that instruct that these errors should be ignored. I've no doubt that some of the errors on this SCAN are in this category.
Given the foibles of 5WA chassis vehicles, I guess the way to look at this SCAN is to use the date/time stamp on each error as a guide to which are NOT related to the problem in this thread.
If you are not aware, the date/time stamp is when the error was first registered in the module's fault memory. The other relevant Freeze-frame data-point is Malfunction frequency counter. This metric indicates how many times the error has re-occurred in a "drive cycle" since being registered. A "drive cycle" is a defined OBD term- but it's ostensibly a reasonable distance traveled in an ignition cycle.
Calculate the period between the error date/time stamp and the date of the SCAN. This determines the period in which the Malfunction frequency counter should be evaluated. If this car is used to travel a reasonable distance each day, then the Malfunction frequency count should be about the same as the period of days since the error date/time stamp. If the malfunction frequency count is much lower than the number of days since the error date, then likely the error is what I call an "aged fault" - and not relevant to this problem.
Also, you don't say when this problem first happened - look at the date/time stamps for each error with respect to the date that this problem started
OK - so the particularly interesting error in this SCAN (for me at least) is U042200 - Invalid Data Received From Body Control Module (BCM) in the Engine Control Module (let's call this the ECU), The BCM is what OBD11 calls the central electrics module that lives at address 09 on the CAN network
The fact that the BCM is NOT reporting an error indicates that as far as the 09 module is concerned, it is operating as coded. However, according to the ECU, clearly there is a mismatch in the data that it is expecting from the BCM. The error is reported as "intermittent" - which means that the "invalid data" happens only when a particular function in the ECU is operating. I guess the restricted function could be related to the CAN message from the immobilizer (which lives in the Dashboard module) - but descriptor in the error-code is too general to be certain.
I'm not sure what could be causing this error - I can't see how coding the "rear tail light animation with obd11 to the rs3 one" could be implicated in the U042200 error - but then I don't know what coding changes were actually made (no offense intended)!
So, let's find-out what coding changes were actually made to this car using OBD11!! I suggest that you post-up a copy of the History records for the coding changes against your OBD11 account. To do this, use my same instructions as per my previous post. However in Step VI. deselect everything but: - App
- Adaptations
- Coding
- Coding II
- Long coding
- Gateway coding
- Basic settings
- Diagnostic session
After you receive the Email that you sent to yourself (last screenshot) - add the History file again as an Attachment to a new post.
Don |
|
|
|
Post by tachyonic on Aug 3, 2024 14:07:07 GMT
So I live 4 hours from the dealer other wise I would go and try and get this to work myself and the dealer won't be back till Monday to try and work on it again so I've been giving you the history that the obd11 shows for me I'm not sure it will show everything but it was all in working order up until I lost my key. Attachments:OBDeleven_Log 2.txt (2.32 KB)
|
|
|
|
Post by dv52 (Australia) on Aug 3, 2024 22:30:26 GMT
tachyonic : hmm......... you don't say when this problem first happened - look at the date/time stamps for each error with respect to the date that this problem started So, " when did this problem first happen"?
As for the coding history for this car - I can see the changes that you made to "the rear tail light animation with obd11 to the rs3 one". I doubt that this tweak is implicated in this problem.
BUT - this is NOT the only change that has been made to this car!!!
For example, in respect to the U042200 - Invalid Data Received From Body Control Module error on the ECU (from your SCAN), this is what happened when you altered the long-code string on the Engine module:
Old value New value
Byte Hex Binary Hex Binary
00 0A 00001010 0A 00001010
01 25 00100101 25 00100101
02 00 00000000 00 00000000
03 32 00110010 32 00110010
04 24 00100100 24 00100100
05 66 01100110 66 01100110
06 01 00000001 01 00000001
07 0E 00001110 0E 00001110
08 30 00110000 30 00110000
09 04 00000100 00 00000000
10 00 00000000 00 00000000
11 00 00000000 00 00000000
12 00 00000000 00 00000000
13 00 00000000 00 00000000
14 00 00000000 00 00000000
15 00 00000000 00 00000000
16 00 00000000 00 00000000
17 00 00000000 00 00000000
18 00 00000000 00 00000000
19 00 00000000 00 00000000
20 00 00000000 00 00000000
21 00 00000000 00 00000000
22 00 00000000 00 00000000
23 00 00000000 00 00000000
As you can clearly see - your tweak reset Byte 04, Bit 2. According to my information, this software switch has NO descriptor - so I have no idea what effect this change had on the engine module. What was your intention in making this change?
Also, the immobilizer on this car lives in the Dashboard module and the immobilizer is intimately linked to the car's keying system. You appear to have made a number of changes to the coding on the Dashboard module.
I'm not sure how (or, if) these changes will affect the dealer's attempt to re-key the car - but there are imobilizer error(s) in the SCAN report. And as an example, by changing the Dashboard module derivative, you are telling the module that this car is a different model Audi!
So, bottom line = ALL (I've used capital letters for emphasis) of the changes that are listed in your History records should be revered back to the "old value".
Given that the car is 4 hours away from where you live, I suggest that you send the history records to the dealer and get them to revert the changes - then, try clearing the error codes and start again
Don
|
|
|
|
Post by tachyonic on Aug 3, 2024 22:53:19 GMT
Hi Don they can't get access to the control module 9 to revert those specific changes. They can access all other modules so my best bet is to try and have them reset the dashboard and other modules and see if that will program the key. I will ask them to revert the dashboard module and the other modules I coded. I never once made any changes to the engine module so it's weird you're saying I made a code change to it. Also how do I go about reverting the engine module coding back to how it was? I looked at the history for engine module and see a long number that has a change in it but I never did that and have no clue how to change that back I've only ever done changes to things in the adaptations options. Also it was done in diagnostic mode does that not make in difference? I think I figured out how to make the change back.
|
|
|
|
Post by dv52 (Australia) on Aug 3, 2024 23:26:40 GMT
OK - Of course I can't comment on your memory regarding the long-code change to the engine module.
All that I can say is that the amendment appears in your History records and the date/time of the change was 2023-06-14 at 17:09:49 hrs. So, about 12 months ago and about the same time that you made the other coding changes to the Dashboard module!!
Don
|
|
|
|
Post by tachyonic on Aug 3, 2024 23:31:50 GMT
Yeah just cause we don't remember doesn't mean we didn't haha. I attached what looks to me the way to change it back obd11 made it nice and had the number I modified highlighted in green and when you change it back to the original numbers it goes to grey which was super helpful. Thanks a ton Don fingers crossed this works for them on Monday |
|
|
|
Post by dv52 (Australia) on Aug 4, 2024 0:34:47 GMT
hmm.... I would have thought that any master-tech working for a dealer and with even basic coding skills could make these changes using the dealer tool ODIS (this ain't rocket science)!
The video ONLY deals with the long-code change to the Engine module - what about the other changes (I'm not sure what part of "ALL (I've used capital letters for emphasis) of the changes that are listed in your History records should be revered back to the old value" was confusing?
Again, I would have expected that the ONLY information required would be a copy of the OBD11 history records - so the dealer knows what changes to revert back to factory settings!! Don |
|
|
|
Post by tachyonic on Aug 4, 2024 16:18:55 GMT
I know how to make all the changes on all the other modules so I didn't include those. I sent the dealer how to make every change back to normal from the dashboard module there was only two changes as one of the adaptations I did change back to it's original value last time I used obd, engine module this was a change I made to have the exaughst flaps open always, and sound bourne structure module from 0 back to 100. I've talked to the dealer a bunch of times about why they can't just reflash the faulty module and upload the correct coding and they said that they can't do that and it would just have to be replaced entirely had my dad call them and talk to them for an hour on why they can't do it for all I know they are full of shit.
|
|
|
|
Post by tachyonic on Aug 6, 2024 18:18:33 GMT
|
|
|
|
Post by dv52 (Australia) on Aug 6, 2024 22:12:23 GMT
hmm......... I'm really not sure what you are expecting as a response (your last post contains 6 x words and a 2.5 minute video)!
Remember that I'm here on an island which is situated a little North of Antarctica, reading about a mysterious car on an unknown part of this lonely blue planet (I assume in the Northern hemisphere).
My understanding of the strange problems with this car is extremely limited and from a diagnostic perspective - a forum discussion is about the worst possible medium for information exchange! Plus, in this case, the already terrible diagnostic environment is further complicated because you are using a third-party agent (i.e. the dealer) for information provision!
So, i have NO idea whats happening in the video - but I make the following (very ill-informed) observations!
1. I can see that the Dashboard module on this car has a Component Protection (CP) error. Normally CP errors arise in at least 2 x modules: the problematic module AND in the CP master-module (i.e. the Gateway module). Is there a second CP error on this car? Also, normally when the Dashboard module has a CP error, a flashing error message "CP Safe" appears on the dashboard display. Does this happen on this car?
CP is ostensibly a hardware protection function - this means that at least in theory, I'm NOT aware how OBD11 (of itself) can create CP errors! However, OBD11 can NOT be used to clear CP errors
CP is designed by the deities on the VAG mother-ship to combat the black-market trade in stolen parts! So, CP errors normally arise when a new module that is included in the "CP constellation" is retrofitted in the car. And ONLY the dealer tool ODIS and a remote connection to VAG's central server (FAZIT) is able to clear CP errors.
I assume that the Dashboard module in the video is the original unit that was factory fitted to this car. This means that from a CP perceptive - the identity of the Dashboard module should have been registered with the CP master module when the car was built.
Once more, OBD11 can NOT change this registration - ONLY a different Dashboard module which is retrofitted into this car should create a CP error.
Again, NO context has been provided in the video for the CP error - however, since CP is reported on the original physical module, I can only assume that somehow the software identity of the Dashboard module that the CP process uses for validation has been changed. This identity is encrypted - so it's not possible for a third party tool like OBD11 to be involved in either the creation, or deletion of the error
I have no idea why the Dashboard module on this car has a CP error - but it's a basic error that will fundamentally affect the operation of the module's functions (including keying and immobilizer activities - I suspect).
2. I can see that the dealer is not able to access the long-code string on the Engine module. Again, without knowing a whole lot more about how the dealer's OBD11 account is set-up, I'm not able to make comment. My suggestion is that the dealer should try accessing the engine module long-code on another car to confirm whether this problem is peculiar to this car, or if it's a problem with the dealer's PRO account
3. From the Control Units screens in the video and because the CP error is new - it's clear that there is a big difference between the SCAN report that you posted-up previously and the current error status of this car! If you want to continue to participate with the dealer arrangement, I suggest that you get a fresh SCAN
Don
|
|
|
|
Post by ghostrider72 on Aug 11, 2024 20:47:37 GMT
To make it short and understandable…
If you lost ALL keys on MQBEvo platform car you need to replace BCM with brand new one, and new keys. Both need to be supplied by dealer and coded online with odis.
This applies to A3 8Y, Golf MK8, Octavia MK4 etc. It is because BCM shut itself and its not possible to code new key, even if supplied by main dealer. In fact… there is TPI for it so dealer should know about it.
|
|
