Vcds?
61 - 80 of 123 Posts
Joined
·
108 Posts
Roger if you look under the "video on motion" menu, at that page, there is a code generator so you can access the locked menus
Joined
·
2,485 Posts
I have the lock codes for several channels, but if they are NOT permitted to be changed, the codes won't help. There just seem to be a few things Audi doesn't want messed with. I have similar security and personalization codes for my S5 BCM2 and when changing channel adaptations there to make my E-Code tailights work correctly (which I WAS able to change) still threw a DTC for the controller that the "Dataset is implausible" which then led Audi to want to replace the controller - it was/is fine, but the changed data is in conflict with other data for my VIN on that car.
I live with that because it serves my purposes, but I'm not sure many others might want to explain this kind of code changes to their cars under a new car warranty. The code changes I've so far made to my Q3 do NOT throw such DTCs since I've only made changes that are "accepted" by VCDS. When I see a channel value that contains an 'Error *** N/A to Change', that leads me anyway, to stay a bit clear of trying to do so ...
I live with that because it serves my purposes, but I'm not sure many others might want to explain this kind of code changes to their cars under a new car warranty. The code changes I've so far made to my Q3 do NOT throw such DTCs since I've only made changes that are "accepted" by VCDS. When I see a channel value that contains an 'Error *** N/A to Change', that leads me anyway, to stay a bit clear of trying to do so ...
Joined
·
108 Posts
I see, so if I change the setting to allow Video while driving, since it is a locked option, I will get a DTC?
Joined
·
2,485 Posts
That's not necessarily what I said. I was speaking generically with a specific reference. Some coding actions are normal in one market and not in another - those are easily changed and usually do not affect local laws (but sometimes do) and/or operational safety or alignment with other CAN-systems. Other changes CAN affect safety or integration/cooperation with other CAN-systems (controllers) that can deteriorate operational driveability or safety.
All my changes (to my Q3) show current Fault-Free scans - and were accepted by the change request, but VCDS is not the only way to make such changes. Frankly, I do not know what would happen if you change your video in motion to be active - I think laws are different for this, but Audi (and others too) takes a position of vehicle operation safety for themselves, which may make this change throw a code regardless (so that anyone - including themselves - that scans the car, will see it). Or, it may just NOT allow VCDS to make the change regardless security or personalization access.
I'm just saying that while most changes to coding MAY/WILL be fine, care must be exercised when doing so - and that if I see a channel or byte/bit that hints at not wanting to be changed (and then some are just NOT accepted or outside a predetermined range set by Audi), or requires security first, personalization second, I'd be VERY careful in going in there !!
VCDS is a very powerful utility, but it is NOT a complete CAN-BUS re-programming tool that allows you to do any/everything you want to to the code. You have to be a very gutsy hacker for that (and there are some out there) - and you take your chances...
All my changes (to my Q3) show current Fault-Free scans - and were accepted by the change request, but VCDS is not the only way to make such changes. Frankly, I do not know what would happen if you change your video in motion to be active - I think laws are different for this, but Audi (and others too) takes a position of vehicle operation safety for themselves, which may make this change throw a code regardless (so that anyone - including themselves - that scans the car, will see it). Or, it may just NOT allow VCDS to make the change regardless security or personalization access.
I'm just saying that while most changes to coding MAY/WILL be fine, care must be exercised when doing so - and that if I see a channel or byte/bit that hints at not wanting to be changed (and then some are just NOT accepted or outside a predetermined range set by Audi), or requires security first, personalization second, I'd be VERY careful in going in there !!
VCDS is a very powerful utility, but it is NOT a complete CAN-BUS re-programming tool that allows you to do any/everything you want to to the code. You have to be a very gutsy hacker for that (and there are some out there) - and you take your chances...
I checked this tonight, I do indeed having parking lights.
Turn ignition off and then move the indicator stalk, side light is then on.
Joined
·
2,485 Posts
...then I need to look thru your coding a bit more carefully to see where this is coded - as I would like to have it, and the above reference does NOT work.
Thanks -
Joined
·
2,485 Posts
Go to Open Controller - FF-Body Other, Long Coding Helper, byte 99, bit 17, change 0 to 1, Do It! and have a drink while waiting for the Auto-Scan to update...
Very excited about getting my RT cable today. Made some of the mods Roger identified earlier in this thread. They were very easy to do. Thank you Roger for the precise instructions. I am attaching my original scan prior to any changes. I am concerned about the fault code I am getting for 5F Address. Also label "redir fail" for Address 56 & 6D. Has anyone seen these? Any suggestions on a fix?
Joined
·
2,485 Posts
The DTC (fault code) is prolly from something you may have unplugged and replugged - as in many of these controllers, they notice that - even if power is off. When I changed my MMI bin, the CANBUS noticed the MMI unit was unplugged and threw a code. If you DIDN'T do that, you may have a REAL intermittent issue to deal with.
As for the "Redir fail" it's about the same as either NOT having a label file for the controller or it was unavailable to connect or reference to. You could try another AutoScan and it might pick up again. This happens from time to time, as some controllers "fail to respond" also. I notice that much more often with HEX-NET than HEX+CAN anyway...
As for the "Redir fail" it's about the same as either NOT having a label file for the controller or it was unavailable to connect or reference to. You could try another AutoScan and it might pick up again. This happens from time to time, as some controllers "fail to respond" also. I notice that much more often with HEX-NET than HEX+CAN anyway...
Thanks for the info. Yes, when I was playing around in the truck to change the lights, I looked at all of the wiring and disconnected the wire above the tire going to a Bose subwooffer.I reconnected and put everything back in place. This must have been it. I suppose I should clear it, right?
Joined
·
2,485 Posts
I think you can clear these DTCs and just watch it. I scan about once a week just for grins, plus I'm in there nosing around still as RT gets more label files for the Q3. Apparently, since they're in the U.S., they hadn't focused on it much since it came out, and are only now beginning to prioritize to fully document.
Sounds about right, ignore the RoW. It's only been out in Europe, India, Australia etc for 3yrs!
61 - 80 of 123 Posts
