moonstone
Tyre Kicker
it says function not available
Where?
Welcome to Deutschespeed.com the newly launched community for German Performance car lovers. The site is in it's launch phase at the moment and so content and membership is small (but growing). Soon we'll have competition prizes and and a live ad campaign to help build the community. If you'd like to be apart of what's going on, sign up and join in!
it says function not available
Finally, got it to work great green P on dash and button all working as it should and I find it very useful.
Have checked over wiring and all is correct and snug fitted in abs module , Would I be thinking this coding is different for a manual gear box . As I have been following the guide which I believe is for a DSG box here which I think one of the coding lines is set for a autoCheck your connections. They’re either not right or not fully engaged.
Have checked over wiring and all is correct and snug fitted in abs module , Would I be thinking this coding is different for a manual gear box . As I have been following the guide which I believe is for a DSG box here which I think one of the coding lines is set for a auto
Cheers
question about Security access codes
Two that work for me are 20103 which I use and 01138. I can code the car with the above bytes 15 ,16,25,26 all fine and then the warning lights come on in dash saying auto hold unavailable . I reset the ignition go into the app to remove the fault which is open circuit on lamp on the button, this lead me to believe it was a wiring issue which I will take another look today . It won’t allow me to clear the fault as I have seen other vids on YouTube saying it’s normal for this to happen after coding and will require it to be cleared before working correctly . Do you know if the app based coding on odb11 for auto hold function require security access codes. As it’s meant to be a one click option
Thanks for taking time to reply to meThe fault you describe is definitely a wiring issue. You’re getting this fault because the car has been successfully coded and is now reporting a wiring fault. If your coding had been unsuccessful then you wouldnt have a fault at all (as the car wouldn’t be looking for hold assist).
This is exactly the same issue I had and it turned out that I had one of the pins in the ABS connector I’m the wrong slot.
Also the grey plugs in the connector have a habit of breaking in half. Half you ensured that there’s nothing left in those slots that mate be stopping the wiring connection from happening?
I wasn’t aware that there was a one-click app for hold assist. In terms of coding, you’ll know if it fails because it’ll tell you. Based on everything you’re saying I’d be amazed if it wasn’t a wiring issue.
Oh and to answer your earlier question that I missed the first time around. OBDeleven will let you code pretty much anything regardless if it’s present on the car or not so how it behaves has nothing to do with whether or not your physical install has been successful.
I’d agree with the grey pin issue. I had an issue getting mine out so maybe there is a bit in one or both ports 32,23. I’d have to get the connector off again but I think I’ll struggle with that now tilOk. So what you're doing sounds correct. If the coding failed in OBDeleven then either you would get a message on the app saying "coding not accepted" or your bit & bytes would have reverted back to original when you went back into check after changing them.
The Kufatec dongle that came with mine only changed two bytes when I checked it afterwards with OBDeleven.
The reason why I'm saying its a wiring issue, rather than a coding issue is because of what's coming up on the dash. You've now told the car that it has Autohold. So now, the car is including Auto-hold in its function list, is seeing that there's a problem with it and is displaying the error. If your coding hadn't worked, you wouldn't get the error on the dash.
Forget get about Hex. Hex is just an alphanumberic number made up of bytes and another way to describe long coding.
In a previous post your wrote:
"I reset the ignition go into the app to remove the fault which is open circuit on lamp on the button, this lead me to believe it was a wiring issue which I will take another look today . It won’t allow me to clear the fault as I have seen other vids on YouTube saying it’s normal for this to happen after coding and will require it to be cleared before working correctly . "
Open circuit on the lamp means that the wiring from the lamp to the ABS connector is incorrect. Clearing the error wont fix it and it's NOT normal for this to happen after coding.
So everything points to this being a wiring issue rather than a coding issue. Two of us had the same symptoms as you and it was a wiring problem. I was also convinced it must be coding until I eventually realised I had one of the wires in the wrong pin on the ABS connector. Before that, on my first attempt, it turned out that part of the grey plug in the pin location was still wedged in the slot and was stopping the new pin from connecting.
We really need photos of your connections to help you further.
I get a new locking mech.I’d agree with the grey pin issue. I had an issue getting mine out so maybe there is a bit in one or both ports 32,23. I’d have to get the connector off again but I think I’ll struggle with that now til