[Ovmsdev] V3 CAN frames missing last four data bytes
Mark Webb-Johnson
mark at webb-johnson.net
Tue Oct 24 07:36:22 HKT 2017
My bad. I broke it the other day (when changing the CAN framework message queue framework).
OVMS > can can3 tx standard 100 01 02 03 04 05 06 07 08
CAN tx origin can3 id 100 (len:8) 01 02 03 04 05 06 07 08........
CAN rx origin can1 id 100 (len:8) 01 02 03 04 00 00 00 00........
Fixed now:
- m_rxqueue = xQueueCreate(20,sizeof(CAN_frame_t));
+ m_rxqueue = xQueueCreate(20,sizeof(CAN_msg_t));
OVMS > can can3 tx standard 100 01 02 03 04 05 06 07 08
CAN tx origin can3 id 100 (len:8) 01 02 03 04 05 06 07 08........
CAN rx origin can1 id 100 (len:8) 01 02 03 04 05 06 07 08........
Regards, Mark.
> On 24 Oct 2017, at 4:50 AM, Michael Balzer <dexter at expeedo.de> wrote:
>
> Is this a known problem?
>
> In all of my can1 frames bytes 5-8 are zero:
>
> OVMS > metrics list can
> d.can1.f.080
> d.can1.f.155 07 97 cf 54 00 00 00 00
> d.can1.f.196 00 ff e7 7f 00 00 00 00
> d.can1.f.19f ff ff 7d 0f 00 00 00 00
> d.can1.f.423 03 33 ff ff 00 00 00 00
> d.can1.f.424 11 40 10 23 00 00 00 00
> d.can1.f.425 2a 21 44 ff 00 00 00 00
> d.can1.f.426 00 78 01 00 00 00 00
> d.can1.f.436 00 07 7e d8 00 00
> d.can1.f.554 36 36 36 36 00 00 00 00
> d.can1.f.556 31 23 11 31 00 00 00 00
> d.can1.f.557 31 03 10 31 00 00 00 00
> d.can1.f.55e 31 23 12 31 00 00 00 00
> d.can1.f.55f ff ff 73 00 00 00 00 00
> d.can1.f.597 00 95 08 41 00 00 00 00
> d.can1.f.599 00 00 b7 b2 00 00 00 00
> d.can1.f.59b 20 00 64 00 00 00 00 00
> d.can1.f.59e 00 00 0c 8d 00 00 00 00
> d.can1.f.5d7 00 00 04 7c 00 00 00
> d.can1.f.627 00 00 00
> d.can1.f.628 00 00 00
> d.can1.f.629 00 00 00
> d.can1.f.659 ff ff ff ff
> d.can1.f.69f f0 82 87 37
> d.can1.f.701 05
>
> Trace mode:
>
> …
> CAN rx origin can1 id 080 (len:0)
> CAN rx origin can1 id 196 (len:8) 00 ff e7 7f 00 00 00 00........
> CAN rx origin can1 id 155 (len:8) 07 97 ce 54 00 00 00 00...T....
> CAN rx origin can1 id 19f (len:8) ff ff 7d 0f 00 00 00 00..}.....
> CAN rx origin can1 id 196 (len:8) 00 ff e7 7f 00 00 00 00........
> CAN rx origin can1 id 155 (len:8) 07 97 ce 54 00 00 00 00...T....
> CAN rx origin can1 id 5d7 (len:7) 00 00 04 7c 00 00 00 ...|...
> CAN rx origin can1 id 19f (len:8) ff ff 7d 0f 00 00 00 00..}.....
> CAN rx origin can1 id 080 (len:0)
> CAN rx origin can1 id 196 (len:8) 00 ff e7 7f 00 00 00 00........
> CAN rx origin can1 id 599 (len:8) 00 00 b7 b2 00 00 00 00........
> CAN rx origin can1 id 436 (len:6) 00 07 7e f2 00 00 ..~...
> CAN rx origin can1 id 155 (len:8) 07 97 ce 54 00 00 00 00...T....
> CAN rx origin can1 id 69f (len:4) f0 82 87 37 ...7
> CAN rx origin can1 id 19f (len:8) ff ff 7d 0f 00 00 00 00..}.....
> CAN rx origin can1 id 196 (len:8) 00 ff e7 7f 00 00 00 00........
> CAN rx origin can1 id 423 (len:8) 03 33 ff ff 00 00 00 00.3......
> CAN rx origin can1 id 426 (len:7) 00 78 01 00 00 00 00 .x.....
> …
>
>
>
> --
> Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
> Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
>
> _______________________________________________
> OvmsDev mailing list
> OvmsDev at lists.teslaclub.hk
> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20171024/77f94ee7/attachment.htm>
More information about the OvmsDev
mailing list