Replies: 1 comment
-
Update: The reason for which it says "Protocol not supported" is revealed in the console, it's because it can't retrieve the functional address, for some reason. The same file is usable in pyRen DDT mode, without complaints (actually same file name, since pyRen uses XML and DDT4ALL uses JSON). I wouldn't say this issue/discussion is finished, because I believe DDT4ALL should support it... |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi. I wanted to use this tool to enable "Extended grip" in the ABS (and Navigation) module in order to get "Expert" mode for traction control.
I am using an ELM327 through bluetooth. Selecting the model "Renault New Captur (C1A)" and scanning ECUs, it does find a few, but an ABS module is not included. Trying a random module from the "ABS-VDC_29b" section yields a "Protocol not supported", but perhaps this is because it tries to use some strange protocol like DoIP, I don't know. Other older module versions give a KWP request out of range error when trying to enter screens.
I am aware the Captur II has writing protection imposed by the gateway. For coding the Navigation, I was planning to bypass the gateway at the navigation unit's connector. Is it possible that I need to bypass the gateway just so I am able to connect to ABS?
I have been able to apparently access the ABS module using the same ELM327 with an Android app. Unfortunately, all it's able to tell me regarding identification is
Diag. ver.: 04
. When I try to read fault codes, the ABS warning light starts flashing in the dash, so it's definitely doing something.So how could I possibly convince DDT4ALL to connect to the ABS module?
Beta Was this translation helpful? Give feedback.
All reactions