dave
New Member
Posts: 7 
|
Post by dave on Mar 30, 2017 17:39:03 GMT
Hi, I try my OBd device for the first time to detect which of my parking sensor was faulty. I made a Scan and get the only error on the park system module and get info that my front right sensor is faulty. I then try to look coding possibilities and, as I change my License plate from bulb to LED, I try to code by changing from 'Bulb' to 'LED'. Once done, just few seconds after, I get an error on my panel regarding a faulty "starting car (Key) device". So I run a scan and appears some more error (which was not there before my coding  ) Here are some pictures (in french, sorry     Despite this "alert", car is starting normally. - I already check all the fuses and none is faulty. - I also disconnect my battery for 10 minutes, reconnect, new scan and errors still there Any advice to remove these errors codes?? |
|
|
|
Post by stifens on Apr 1, 2017 5:01:06 GMT
+1 I have gotten the same errors in My A5 after doing what you did as well. Any help would be much appreciated.
|
|
|
|
Post by stifens on Apr 3, 2017 12:07:47 GMT
My A5 now wont start at all. Cannot put the ignition on either. The car is going to the local audi dealer. I also checked with Vag-com. It seems like the Control module (central electrics 46) is defective due to a internal cpu error and needs to be replaced. It was absolutely fine before.
|
|
dave
New Member
Posts: 7
|
Post by dave on Apr 3, 2017 16:10:01 GMT
Oh Sh*t..not a good news |
|
|
|
Post by Matthew on Apr 6, 2017 3:35:13 GMT
My A5 now wont start at all. Cannot put the ignition on either. The car is going to the local audi dealer. I also checked with Vag-com. It seems like the Control module (central electrics 46) is defective due to a internal cpu error and needs to be replaced. It was absolutely fine before. OBDeleven stores the car's HISTORY of changes. It sounds like you may have changed the famous byte18 to a value it can't revert to. I need to look back at what this value should be in VCDS. Also, when you restore the original coding, you may have to switch off the ignition for about 30 seconds. The issue with using the APPs option is that it doesn't show you the bits & bytes before and after changes. I HOPE you e-mailed yourself a copy of the ORIGINAL coding for ALL modules before you made any changes. Buying a new central electrics module is not necessary. Everything is "undoable" except for changes made to the immobilizer module, airbag module, and top speed limiter set for the car. Don't be tricked into thinking that your #46 module is bricked. If you play around with the output of your airbag module, than your car will not start. If you do the wrong changes for your immobilizer, your car won't start either. |
|
|
|
Post by stifens on Apr 6, 2017 4:52:01 GMT
Thanks for answering. Maybe OP's car is fixable but mine is toast. I have a friend who works at the local audi dealer. They tried updating the module with new software and coding it again. It's not working. They also checked all the coding. Everything seems normal, but for some reason the module failed. So It will need replacing. Nope  no backups of modules... but as I said. The coding was fine. We double checked everything. The error came right after I had used the obdeleven for the first time. I just switched on engineering menu of the MMI' emergency brake lights, mirror dip, and LED licence plate lights. All was done with the apps. Then the car started but with errors. A week later it wouldn't start. |
|
|
|
Post by stifens on Apr 6, 2017 5:09:43 GMT
As far as I understand the immobilizer and keyless is integrated into the comfort module, so that's why it wont work.
|
|
|
|
Post by Matthew on Apr 6, 2017 11:05:53 GMT
As far as I understand the immobilizer and keyless is integrated into the comfort module, so that's why it wont work. OOH, Ouch. I forgot that they started merging these roles in these models. My MK5 Golf has the immobilizer as a separate module. |
|
dave
New Member
Posts: 7
|
Post by dave on Apr 6, 2017 19:28:54 GMT
My A5 now wont start at all. Cannot put the ignition on either. The car is going to the local audi dealer. I also checked with Vag-com. It seems like the Control module (central electrics 46) is defective due to a internal cpu error and needs to be replaced. It was absolutely fine before. OBDeleven stores the car's HISTORY of changes. It sounds like you may have changed the famous byte18 to a value it can't revert to. I need to look back at what this value should be in VCDS. Also, when you restore the original coding, you may have to switch off the ignition for about 30 seconds. The issue with using the APPs option is that it doesn't show you the bits & bytes before and after changes. I HOPE you e-mailed yourself a copy of the ORIGINAL coding for ALL modules before you made any changes. Buying a new central electrics module is not necessary. Everything is "undoable" except for changes made to the immobilizer module, airbag module, and top speed limiter set for the car. Don't be tricked into thinking that your #46 module is bricked. If you play around with the output of your airbag module, than your car will not start. If you do the wrong changes for your immobilizer, your car won't start either. ...so it mean that I should do or verify what exactly? The last coding I get from last 'OK VCDs Scan': ...and actual coding for my mmodul 46:  So actual coding is same as the one I get "when everything was ok" |
|
|
|
Post by Matthew on Apr 6, 2017 20:29:23 GMT
I see what you mean. I'll need about half-a-day to do some reading online in this regard.
|
|
dave
New Member
Posts: 7
|
Post by dave on Apr 8, 2017 19:18:41 GMT
I see what you mean. I'll need about half-a-day to do some reading online in this regard. so?? any news...? |
|
|
|
Post by Matthew on Apr 9, 2017 15:01:01 GMT
No. No news as yet. I'm playing around with VCDS on my MK5 to give you the results Ross-Tech's page doesn't seem to have anything for your configuration either wiki.ross-tech.com/wiki/index.php/Audi_A4/S4/RS4_(8K)I'm still working on your issue. I'm looking for a similar vehicle here in Jamaica to get some screenshots to help you. |
|
|
|
Post by Matthew on Apr 9, 2017 15:03:35 GMT
My A5 now wont start at all. Cannot put the ignition on either. The car is going to the local audi dealer. I also checked with Vag-com. It seems like the Control module (central electrics 46) is defective due to a internal cpu error and needs to be replaced. It was absolutely fine before. Did you make the mistake of resetting to factory as stated below? wiki.ross-tech.com/wiki/index.php/Audi_A4_(8K)_Comfort_System |
|
|
|
Post by stifens on Apr 9, 2017 16:10:30 GMT
No, I did not |
|
|
|
Post by Matthew on Apr 9, 2017 16:47:31 GMT
Whatever you do, don't allow your dealer to sell you a new module. It may be the quickest way for them to fix the issue, but it is going to be expensive for you. ....then they slap you with huge (labor) fees for having to code that new module.
|
|
|
|
Post by stifens on Apr 9, 2017 18:08:52 GMT
I bought a used and tested module. A friend of mine works at the local dealer, so he checked the old module for me. I promise, it's toast. He'll code the new module for me when it gets here.
|
|
|
|
Post by Matthew on Apr 9, 2017 22:23:27 GMT
The mere thought of toasting a module with a simple coding change is scary to me. I wonder how much worse it could have been if you used a more powerful tool like VCDS. I'm happy you are getting it resolved though.
|
|
|
|
Post by stifens on Apr 10, 2017 22:57:22 GMT
Yeah, scary stuff. I'm guessing the coding for the LED taillights messes with something that makes the keyless/immobilizer angry. Since it is in the same module. But exactly what I'm not sure of, since the coding itself seems fine.
|
|
|
|
Post by Matthew on Apr 10, 2017 23:15:59 GMT
I'm sure if this was done-over with VCDS, the car will start.
I suspect the issue is with the Work Shop code / number. I can't see the value that OBDeleven uses. I suspect they use the existing one stored in the module already.
|
|
dave
New Member
Posts: 7
|
Post by dave on Apr 11, 2017 18:03:57 GMT
I'm sure if this was done-over with VCDS, the car will start. I suspect the issue is with the Work Shop code / number. I can't see the value that OBDeleven uses. I suspect they use the existing one stored in the module already. I contact OBDeleven support and answer is: "Sorry, I don't have this information." It's quite incredible...they are not able to say what this shi*y buitin coding is changing!!!!!!! |
|
|
|
Post by Dadeyen1 on Apr 11, 2017 20:20:08 GMT
I also got this problem. Changed the plate light to led and I got a key error or something. Restarted the car some times and it got better. But I don't know if it'll come back again soon. The error is surely there if I scan the car.. 01330 is the code.
|
|
|
|
Post by Dadeyen12345 on Apr 11, 2017 20:21:18 GMT
I also got this problem. Changed the plate light to led and I got a key error or something. Restarted the car some times and it got better. But I don't know if it'll come back again soon. The error is surely there if I scan the car.. 01330 is the code.
|
|
|
|
Post by Matthew on Apr 11, 2017 21:42:18 GMT
This is what Ross-Tech's page says about the error wiki.ross-tech.com/wiki/index.php/01330"Control module faulty" seems like the most likely option due to bad coding. It is very important to remember that there are several variations of the same module. The OBDeleven developers can't support them all. The issue when you use an APPs option to change a module that has a different revision / firmware from the one that the OBDeleven team has been testing with will cause these issues. You wouldn't have this issue if you were using VCDS because the label files would prevent you from selecting the WRONG options (in terms of bits and bytes) during the long coding process. |
|
|
|
Post by dadeyen123 on Apr 12, 2017 4:36:57 GMT
So what can I do? Everytime I start my car from now on the little key with an X over it is showing in the screen. Why make apps available if it's not fully supported for my vehicle?
|
|
|
|
Post by Matthew on Apr 12, 2017 4:53:13 GMT
I don't have an answer for you at this time Why make apps available if it's not fully supported for my vehicle? They aren't specifically for "your" vehicle. They are for modules (not chassis code) for a specific range of part numbers. I'll post an example below: In the above example 1K0-907-115 is a part number for the module, but the revision "R" might not be supported, or have different internal firmware or addressing scheme. The OBDeleven team is helping you out by scripting these automated APPs, however, they can't possibly be expected to support every possible variation of a module that is created. It is always a gamble, hence I advise against using APPs, and recommend coding your modules manually so that you can see what is being changed. With APPs, you can't see what's happening in the background. |
|
|
|
Post by dadeyen123 on Apr 12, 2017 5:13:10 GMT
I got some other faults as well 16349 and 16366
|
|
|
|
Post by dadeyen123 on Apr 12, 2017 5:16:25 GMT
So can I revert the coding or is the only option now to swap out the whole module? I switched back to bulb instead of led but it didn't get any better.
|
|
|
|
Post by Matthew on Apr 12, 2017 5:31:58 GMT
Reverting the coding, only does the coding, but NOT the adaptation channels. The issue is that we have no idea what setting changes were made with the APPs option you selected. The OBDeleven team would have to answer that question.
|
|
matt
Closed beta tester
Posts: 48
|
Post by matt on Apr 12, 2017 12:05:19 GMT
I don't have an answer for you at this time Why make apps available if it's not fully supported for my vehicle? They aren't specifically for "your" vehicle. They are for modules (not chassis code) for a specific range of part numbers. I'll post an example below: In the above example 1K0-907-115 is a part number for the module, but the revision "R" might not be supported, or have different internal firmware or addressing scheme. The OBDeleven team is helping you out by scripting these automated APPs, however, they can't possibly be expected to support every possible variation of a module that is created. It is always a gamble, hence I advise against using APPs, and recommend coding your modules manually so that you can see what is being changed. With APPs, you can't see what's happening in the background. I make software for a living, if you are going to make apps like this they must support 100% of cars 100% of the time or you (the people who made them) are financially responsible for the consequences. Having apps that take down a car is not only illegal its absolutely awful coding and testing..... |
|
|
|
Post by Matthew on Apr 12, 2017 15:23:00 GMT
[if you are going to make apps like this they must support 100% of cars 100% of the time I hear you. However, the fact is: If you wanted 100% support for ALL VAG cars, one would have bought a genuine VCDS cable where that is included. There is a reason for Ross-Tech's high(er) price tag. One can't expect to pay a few dollars for an OBDeleven dongle and an Android app, and expect the same quality of service from a dealer-level cable like Ross-Tech. What I really mean to say is: "we get (the value of) what we pay for". I was in your shoe too. I then bought a VCDS cable and learnt what the differences were. I'm here to give back to the community by being a good Samaritan and assisting others with their coding issues. |
|
)
no backups of modules... but as I said. The coding was fine. We double checked everything.