Mike Dunston

This creates a pins variant but doesn't define any board to use it. Please update boards.txt to have a reference to this new board.

Most likely this is due to the bus not being in a compatible state for transmit and further as a result receive will fail for the same reason. Add these...

@thankthemaker TWAI is working perfectly fine in any of the 2.0.x releases of arduino-esp32. Note that this is based on ESP-IDF v4.4.x and not IDF v5.x. IDF v5.x is *NOT*...

@thankthemaker You will need to share some code for review as the above usually indicates that the bus encountered an error and you did not initiate recover from it.

Also note that https://github.com/espressif/arduino-esp32/tree/master/libraries/ESP32/examples/TWAI both appear to work

From your output above: ``` Failed to queue message for transmission alert 0x3380, status 0x103 ESP_ERR_INVALID_STATE ``` The alert bits are set as follows: - TWAI_ALERT_ARB_LOST - somewhat normal and...

@thankthemaker can you do your test with IDF v4.4.3 (what is currently picked up)? I'm suspecting something was fixed *AFTER* IDF v4.4.3 and may be picked up by a currently...

I'm curious how this might have happened, I saw something similar in one of my tests (it wasn't throttle related) but found that my node-id wasn't initializing correctly (it was...

Interesting, I wonder then if OpenMRN should discard the 0x000 alias frames or reply with an error to the caller (though with an invalid alias it may raise other issues).

That breaks existing user code that expects WiFi scan to work when operating in AP mode. It's not as simple as changing the mode since that would attempt to start...