I connect my Real Dash panel to EDC17CV44 and can’t connect, that’s what the program writes:
atpc
OK
atsp9
OK
atdpn
9
0100
410098380007AA
0900
STOPPED
OK
"
+“:”
can you help me…
Vehicle info (0900) responds “Stopped”. That is an indication that car will not allow you to read identification info, probably needs a specific header to be set before reading.
I found the problem. My ECU operates according to the ISO15765-4 CAN protocol (29 bit ID, 250Kbaub), there is no such protocol in the list, but when the ECU protocol is automatically detected in the CAN monitor, it is detected and it can be applied, why is it not in the list when selecting protocol settings? In the list of program protocols there is only ISO15765-4 CAN (29 bit ID, 500Kbaub)
Automatic detection is not perfect, it only finds the first protocol that seems to respond to 0100 PID.
How do I choose the protocol that is defined in the OBD monitor from the list? If he’s not there. Use an OBD monitor every time?
You can test if your adapter can auto detect the protocol:
ATSP0
0100
ATDPN
If ATDPN returns your protocol number, adapter does auto detect properly.
Alternatively you can make your custom OBD2 XML file that uses ATSP# in ‘init’ section.