Mike Dunston

Let me see what I can find, I agree this is a sub-optimal behavior. I'm not seeing anything specific in the ESP-IDF driver that would handle this differently.

Perhaps, but there may be other conditions masked by doing that. Perhaps the WD task could disable/enable the interrupt when it wakes every ~10sec if the TX/RX count has changed...

from the S3 datasheet, it looks like the bus-error interrupt flag can be isolated but there are some usages of this bit in ESP-IDF ([ref](https://github.com/espressif/esp-idf/blob/3640dc86bb4b007da0c53500d90e318f0b7543ef/components/hal/twai_hal_iram.c#L112)). It also appears that `TWAI_HAL_EVENT_BUS_ERR`...

It may also make sense to implement handlers for the following events which are currently ignored: * `TWAI_HAL_EVENT_ABOVE_EWL` * `TWAI_HAL_EVENT_BELOW_EWL` * `TWAI_HAL_EVENT_ERROR_PASSIVE` * `TWAI_HAL_EVENT_ERROR_ACTIVE` These are currently being set by...

I've dug through the TWAI code and this bus-error count increasing is occurring *AFTER* the driver enters error-passive state. It also does not ever appear to transition to the bus-off...

> Is the ArduinoBuild / Build ESP32 examples build failure check holding it up? that can be ignored as it is trying to use the latest arduino-esp32 that isn't supported...

@balazsracz I observed one odd crash with this hub implementation while using a UWT-50, any ideas? ``` 02:26:35.202: CanDatagramWriteFlow: No datagram response arrived from destination 090099020126. 02:26:35.203: MemoryConfig: Failed to...

What motor shield are you using?

That looks correct from what I can tell. Check the serial console output for any clues.

I haven't used more than one display in any of my projects. But you should have some options on implementation. - if the displays all need to be identical you...