[Ovmsdev] RE tool for OBDII

[Mark Webb-Johnson]

RE tool for OBDII:

OVMS > re start

OVMS > re obdii standard 7df 7df
Set OBDII standard ID range 7df-7df

OVMS > obdii ecu start can3
OBDII ECU has been started

I (38897) events: Signal(power.can3.on)
I (38997) obd2ecu: Using custom scripting for pid#99

OVMS > power ext12v on
Power mode of ext12v is now on
I (44127) ext12v: Powering on external 12V devices

(Wait a bit …)

OVMS > re list
key                     records     ms last
can3/7df:O2Qm1:0              2  11500 02 01 00 00 00 00 00 00
can3/7df:O2Qm1:12            18   1277 02 01 0c 00 00 00 00 00
can3/7df:O2Qm1:13            14   1642 02 01 0d 00 00 00 00 00
can3/7df:O2Qm1:16            14   1642 02 01 10 00 00 00 00 00
can3/7df:O2Qm1:32             1  23000 02 01 20 00 00 00 00 00
can3/7df:O2Qm1:47            13   1769 02 01 2f 00 00 00 00 00
can3/7df:O2Qm1:5             14   1642 02 01 05 00 00 00 00 00
can3/7df:O2Qm1:64             1  23000 02 01 40 00 00 00 00 00

You start the RE tool, and give it the ID range to monitor for standard frames OBDII. You can also optionally give ‘re obdii extended …’ for extended frames as well. The RE tool will then treat messages on those IDs as OBDII requests/responses and key appropriately. The keys are O2Q for query, and O2P for reply. The “m1” is mode #1. The final digits (after the “:”) is the PID requested/replied. This should work for both OBDII requests and replies (although only standard mode requests tested so far).

At the moment, I’m monitoring frames inbound (can rx) only. We could monitor tx as well, without too much difficulty.

Here is what a O2 vehicle module on the box, talking to an external OBDII ECU simulator, looks like:

OVMS > re obdii standard 7df 7ef
Set OBDII standard ID range 7df-7ef

OVMS > vehicle module O2
I (593927) v-obdii: Generic OBDII vehicle module
I (593927) events: Signal(power.can1.on)

OVMS > re list
key                     records     ms last
can1/7e8                      3  19666 22 37 32 35 32 33 36 37
can1/7e8:O2Pm1:12             6   9833 04 41 0c 3c 13 00 00 00
can1/7e8:O2Pm1:13             5  11800 03 41 0d 5b 00 00 00 00
can1/7e8:O2Pm1:15             2  29500 03 41 0f 41 00 00 00 00
can1/7e8:O2Pm1:47             2  29500 03 41 2f 80 00 00 00 00
can1/7e8:O2Pm1:5              2  29500 03 41 05 40 00 00 00 00
can1/7e8:O2Pm1:70             2  29500 03 41 46 3c 00 00 00 00
can1/7e9:O2Pm1:12             6   9833 04 41 0c 3c 13 00 00 00
can1/7e9:O2Pm1:13             5  11800 03 41 0d 5b 00 00 00 00
can1/7e9:O2Pm1:5              2  29500 03 41 05 40 00 00 00 00
can1/7ea:O2Pm1:13             5  11800 03 41 0d 5b 00 00 00 00

Committed, and pushed.

Regards, Mark.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20171101/0aa0d09d/attachment.htm>