[Ovmsdev] OBD/UDS error 31

sharkcow sharkcow at gmx.de
Sat Oct 3 20:59:15 HKT 2020


I'm having trouble getting a multiline OBD message to be read by OVMS.
What exactly does error code 31 mean?

In the OVMS log I see:

D (806212) vehicle: PollerSend(0): send [bus=1, type=22, pid=1821],
expecting 713/77d-77d
D (806222) vehicle: PollerReceive[77D]: process OBD/UDS error 22(1821)
code=31

The only messages with header 713 and 77D in the CAN log are:

1601729078.788373 1T11 713 03 22 18 21 00 00 00 00
1601729078.801032 1R11 77D 03 7f 22 31 aa aa aa aa

However, when I log with OVMS what happens when a working third-party
OBD-adapter issues the command, I see:

1601721047.201952 1R11 713 03 22 18 21 55 55 55 55
1601721047.210050 1R11 77D 10 2f 62 18 21 01 fe 00
1601721047.210695 1R11 713 30 ff 01 55 55 55 55 55
1601721047.214801 1R11 77D 21 00 16 15 00 00 02 20
1601721047.219865 1R11 77D 22 00 00 00 04 00 00 00
1601721047.224808 1R11 77D 23 00 00 00 15 91 00 00
1601721047.230282 1R11 77D 24 01 66 00 00 00 00 00
1601721047.235039 1R11 77D 25 00 00 00 00 fe c9 c9
1601721047.240117 1R11 77D 26 c9 c9 ff fe ff ff aa

Does OVMS even support multiline OBD messages? Are there any settings I
should adjust? Any clues? :)

I'm guessing the intermediate "713 30 ff 01" an acknowledge for the
multiline response, does/can OVMS send that?

Thanks for any hints!

sharkcow



More information about the OvmsDev mailing list