Wild thought, but perhaps the issue could be that the bus isn't properly terminated, so the transmitter is constantly deferring to what appears to be a busy bus?

Greg

Michael Balzer wrote:

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.

Regards,
Michael

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.

        Craig

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@lists.openvehicles.com
http://lists.openvehicles.com/mailman/listinfo/ovmsdev