<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
sharkcow,<br>
<br>
I would assume…<br>
<br>
<blockquote type="cite">or which
attempts to access a dataIdentifier/routineIdentifer that is not
supported or <b>not supported
in active session</b>.
</blockquote>
<br>
…you need to login with a diagnostic session first. Look for
VEHICLE_POLL_TYPE_OBDIISESSION (0x10) requests.<br>
<br>
Regards,<br>
Michael<br>
<br>
<br>
<div class="moz-cite-prefix">Am 03.10.20 um 20:23 schrieb sharkcow:<br>
</div>
<blockquote type="cite"
cite="mid:8694852c-999a-2c08-e446-11ec44114ff5@gmx.de">Michael,
<br>
<br>
thanks for the explanation.
<br>
<br>
Still I'm wondering why the same command works when issued from
the
<br>
third-party OBD adapter... are there any setup commands I could
look out
<br>
for?
<br>
<br>
sharkcow
<br>
<br>
<br>
Am 03.10.20 um 20:08 schrieb Michael Balzer:
<br>
<blockquote type="cite">sharkcow,
<br>
<br>
0x22 is VEHICLE_POLL_TYPE_OBDIIEXTENDED and well supported, see
vehicle
<br>
module.
<br>
<br>
See the PDF I just sent you on page 252:
<br>
<br>
Error code 0x31: requestOutOfRange
<br>
<br>
<blockquote type="cite">This response code indicates that the
requested action will not be
<br>
taken because the
<br>
server has detected that the request message contains a
parameter
<br>
which attempts
<br>
to substitute a value beyond its range of authority (e.g.
attempting
<br>
to substitute a
<br>
data byte of 111 when the data is only defined to 100), or
which
<br>
attempts to access a
<br>
dataIdentifier/routineIdentifer that is not supported or not
supported
<br>
in active session.
<br>
This response code shall be implemented for all services which
allow
<br>
the client to
<br>
read data, write data or adjust functions by data in the
server.
<br>
</blockquote>
<br>
Regards,
<br>
Michael
<br>
<br>
<br>
Am 03.10.20 um 14:59 schrieb sharkcow:
<br>
<blockquote type="cite">I'm having trouble getting a multiline
OBD message to be read by OVMS.
<br>
What exactly does error code 31 mean?
<br>
<br>
In the OVMS log I see:
<br>
<br>
D (806212) vehicle: PollerSend(0): send [bus=1, type=22,
pid=1821],
<br>
expecting 713/77d-77d
<br>
D (806222) vehicle: PollerReceive[77D]: process OBD/UDS error
22(1821)
<br>
code=31
<br>
<br>
The only messages with header 713 and 77D in the CAN log are:
<br>
<br>
1601729078.788373 1T11 713 03 22 18 21 00 00 00 00
<br>
1601729078.801032 1R11 77D 03 7f 22 31 aa aa aa aa
<br>
<br>
However, when I log with OVMS what happens when a working
third-party
<br>
OBD-adapter issues the command, I see:
<br>
<br>
1601721047.201952 1R11 713 03 22 18 21 55 55 55 55
<br>
1601721047.210050 1R11 77D 10 2f 62 18 21 01 fe 00
<br>
1601721047.210695 1R11 713 30 ff 01 55 55 55 55 55
<br>
1601721047.214801 1R11 77D 21 00 16 15 00 00 02 20
<br>
1601721047.219865 1R11 77D 22 00 00 00 04 00 00 00
<br>
1601721047.224808 1R11 77D 23 00 00 00 15 91 00 00
<br>
1601721047.230282 1R11 77D 24 01 66 00 00 00 00 00
<br>
1601721047.235039 1R11 77D 25 00 00 00 00 fe c9 c9
<br>
1601721047.240117 1R11 77D 26 c9 c9 ff fe ff ff aa
<br>
<br>
Does OVMS even support multiline OBD messages? Are there any
settings I
<br>
should adjust? Any clues? :)
<br>
<br>
I'm guessing the intermediate "713 30 ff 01" an acknowledge
for the
<br>
multiline response, does/can OVMS send that?
<br>
<br>
Thanks for any hints!
<br>
<br>
sharkcow
<br>
_______________________________________________
<br>
OvmsDev mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:OvmsDev@lists.openvehicles.com">OvmsDev@lists.openvehicles.com</a>
<br>
<a class="moz-txt-link-freetext" href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a>
<br>
</blockquote>
<br>
</blockquote>
_______________________________________________
<br>
OvmsDev mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:OvmsDev@lists.openvehicles.com">OvmsDev@lists.openvehicles.com</a>
<br>
<a class="moz-txt-link-freetext" href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a>
<br>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26</pre>
</body>
</html>