[Ovmsdev] Help me get my first data item on the I3

Steve Davies steve at telviva.co.za
Sun Dec 13 21:55:49 HKT 2020


On Sun, 13 Dec 2020 at 15:38, Steve Davies <steve at telviva.co.za> wrote:

>
>
> On Sun, 13 Dec 2020 at 12:34, Michael Balzer <dexter at expeedo.de> wrote:
>
>> But it shouldn't be hard to add support for this, as it basically just
>> fills the first frame byte from the lower 8 bits of the TX and RX IDs,
>> reduces the payload size by one byte and shifts the offsets by one.
>> PollerSend() and PollerReceive() need to be extended for this, and
>> poll_pid_t needs to be extended by an addressing scheme tag.
>>
>
> I don't think that the extra byte is included in the replies.  (Would help
> if I could get a reply...):
>
>
I suddenly got a whole lot of warning logged:

W (3516211) vehicle: PollerReceive[607]: ignoring unknown/invalid ISO TP
frame: f1 03 7f 22 78 00 00 00 | ..."x...
W (3516261) vehicle: PollerReceive[607]: ignoring unknown/invalid ISO TP
frame: f1 10 09 62 dd bc 02 ea | ...b....
W (3518201) vehicle: PollerReceive[607]: ignoring unknown/invalid ISO TP
frame: f1 03 7f 22 78 00 00 00 | ..."x...
W (3518261) vehicle: PollerReceive[607]: ignoring unknown/invalid ISO TP
frame: f1 05 62 dd 68 93 85 00 | ..b.h...
W (3530211) vehicle: PollerReceive[607]: ignoring unknown/invalid ISO TP
frame: f1 03 7f 22 78 00 00 00 | ..."x...
W (3530261) vehicle: PollerReceive[607]: ignoring unknown/invalid ISO TP
frame: f1 10 09 62 dd bc 02 eb | ...b....
W (3532211) vehicle: PollerReceive[607]: ignoring unknown/invalid ISO TP
frame: f1 03 7f 22 78 00 00 00 | ..."x...
W (3532261) vehicle: PollerReceive[607]: ignoring unknown/invalid ISO TP
frame: f1 05 62 dd 68 93 86 00 | ..b.h...
W (3544211) vehicle: PollerReceive[607]: ignoring unknown/invalid ISO TP
frame: f1 03 7f 22 78 00 00 00 | ..."x...
W (3544261) vehicle: PollerReceive[607]: ignoring unknown/invalid ISO TP
frame: f1 10 09 62 dd bc 02 eb | ...b....
W (3546201) vehicle: PollerReceive[607]: ignoring unknown/invalid ISO TP
frame: f1 03 7f 22 78 00 00 00 | ..."x...
W (3546261) vehicle: PollerReceive[607]: ignoring unknown/invalid ISO TP
frame: f1 05 62 dd 68 93 87 00 | ..b.h...
W (3558211) vehicle: PollerReceive[607]: ignoring unknown/invalid ISO TP
frame: f1 03 7f 22 78 00 00 00 | ..."x...
W (3558261) vehicle: PollerReceive[607]: ignoring unknown/invalid ISO TP
frame: f1 10 09 62 dd bc 02 eb | ...b....
W (3560201) vehicle: PollerReceive[607]: ignoring unknown/invalid ISO TP
frame: f1 03 7f 22 78 00 00 00 | ..."x...
W (3560261) vehicle: PollerReceive[607]: ignoring unknown/invalid ISO TP
frame: f1 05 62 dd 68 93 88 00 | ..b.h...


In there I can see "f1 10 09 62 dd bc 02 eb"   0x02eb = 747 = 74.7% - so
there is the SOC. :-)
and "f1 05 62 dd 68 93 88 00" 0x9388 = 37768 = 377.68 volts - so there is
the battery voltage.

So it looks like the receivepacket does need to be adjusted too - that f1 I
guess is OUR "extended address".
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20201213/f83a5133/attachment-0003.htm>


More information about the OvmsDev mailing list