[Ovmsdev] Not processing canbus frames anymore
dexter at expeedo.de
Fri Apr 15 16:24:50 HKT 2022
This doesn't match my thought:
> Tx fails: 840
That means there actually were TX failures or TX aborts from a bus error
That should manifest in the logs as well, with possibly more detail.
Am 15.04.22 um 09:15 schrieb Michael Balzer:
> That looks like RX was working normally, but all TX was just queued.
> Just a thought: is it possible the ESP32CAN TX buffer is sometimes
> unavailable on the first frame transmission (or appears to be), not
> due to an actual frame blocking the buffer, but due to some kind of
> init race condition?
> That would lead to esp32can::WriteFrame() returning FAIL causing the
> frame to be queued in m_txqueue, but as there is no real TX going on
> at that moment, there never will be a TX callback, so the m_txqueue
> will grow indefinitely from there on.
> Am 14.04.22 um 00:51 schrieb Craig Leres:
>> Here is can bus status for my Corvette after 4 run cycles in which it
>> was never able to transmit frames on can1.
>> OVMS# can can1 status
>> CAN: can1
>> Mode: Active
>> Speed: 500000
>> DBC: none
>> Interrupts: 5115225
>> Rx pkt: 4236787
>> Rx ovrflw: 0
>> Tx pkt: 0
>> Tx delays: 30
>> Tx ovrflw: 28916
>> Tx fails: 840
>> Err flags: 0x00000000
>> Rx err: 0
>> Tx err: 0
>> Rx invalid: 0
>> Wdg Resets: 0
>> Wdg Timer: 3 sec(s)
>> Err Resets: 0
> OvmsDev mailing list
> OvmsDev at lists.openvehicles.com
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 203 bytes
Desc: OpenPGP digital signature
More information about the OvmsDev