Tom, Err flags 0x2040. The 0x20 part is the error interrupt. The 0x40 part is "RX0OVR: Receive Buffer 0 Overflow Flag bit”. Where the number on ‘can can2 status’ moving at all? Or completely stuck? Seems different than the fault Greg and I are seeing. This one likely to be interrupt flag, or buffer overflow, not being cleared correctly. I’m guessing the overflow because that just doesn’t seem correct in mcp2515::RxCallback(). I’ll focus on that and have a look. Regards, Mark.
On 6 Jul 2018, at 5:51 PM, Tom Parker <tom@carrott.org> wrote:
My situation is somewhat different. Can2 is sick, but Rx err is 0:
OVMS# can can2 status CAN: can2 Mode: Active Speed: 500000 Interrupts: 6945528 Rx pkt: 7012397 Rx err: 0 Rx ovrflw: 2483 Tx pkt: 6801 Tx delays: 0 Tx err: 0 Tx ovrflw: 0 Err flags: 0x2040
If I power cycle the can bus then things start to work again.
OVMS# power can2 off Power mode of can2 is now off OVMS# can can2 start active 500000 Can bus can2 started in mode active at speed 500000bps OVMS# can can2 status CAN: can2 Mode: Active Speed: 500000 Interrupts: 10263 Rx pkt: 10340 Rx err: 0 Rx ovrflw: 6 Tx pkt: 0 Tx delays: 0 Tx err: 0 Tx ovrflw: 0 Err flags: 0x2040
My experience is that can2 only lasts a few minutes to perhaps an hour of driving before stopping. I'll see what it looks like next time it stops. _______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev