[Ovmsdev] Problems with IncomingFrameCan when registering two can buses.
Geir Øyvind Vælidalo
geir at validalo.net
Sun Dec 31 08:00:46 HKT 2017
I did a test where I created three counters.
One went into MCP2515_isr and counts every interrupt.
One was added as the first code line in mcp2515::RxCallback.
And the third one was added to RxCallBack, but right before we read the CAN frame via SPI that will end up in IncomingFrame. I.e. should be a count of every CAN frame.
This is what I got:
OVMS > can can2 status
Rx pkt: 82
Rx err: 0
Tx pkt: 0
Tx err: 0
Err flags: 0x2040
These numbers puzzles me. Shouldn’t RxCallback1 and RxCallback2 be less or equal to MCP2515_isr? Where does these extra 81 calls come from? I’m missing something here...
Also, RxCallback2 is much bigger than Rx pkt, which means not all frames are sent to IncomingFrame. I Believe the reason is this code in can.cpp CAN_rxtask:
Is this correct? Wouldn’t it skip calling IncomingFrame it there are only one interrupt?
I would think this is would be more appropriate:
keepOn = msg.body.bus->RxCallback(&msg.body.frame);
Do you agree?
But, the interrupts still stops :-( What does the 0x2040 means? And where do that number comes from?
> 30. des. 2017 kl. 21:24 skrev Michael Balzer <dexter at expeedo.de>:
> MCP2515 Arduino
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OvmsDev