Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Constant loading of the monitor with the message TWAI RX: ESP_ERR_TIMEOUT #5

Open
TouchOnBob opened this issue Apr 15, 2024 · 3 comments
Assignees

Comments

@TouchOnBob
Copy link

TouchOnBob commented Apr 15, 2024

Greetings! Many thanks for this wonderful work!

I'm using ESP32 Wrover and sn65hvd230dr and i have this problem: I'm trying to use the esp32can_receive.ino example and it works as expected. But at the same time, when there is no data exchange on the bus, the message TWAI RX: ESP_ERR_TIMEOUT constantly appears in the serial monitor. At the same time, the example itself seems to work fine.

I tried compiling the code using Arduino Release v2.0.15 based on ESP-IDF v4.4.7, as well as Arduino Release v3.0.0 RC1 based on ESP-IDF v5.1, but the problem remains.
Perhaps this is not a problem, but due to the constant loading of the monitor, I do not have time to see the diagnostic messages that I myself send to the serial monitor...

Please help me correct the situation...

@TouchOnBob
Copy link
Author

In search of at least some solution, I commented out line 147 in the ESP32CAN.cpp file
After this, life became easier.
I understand this is not a solution.
Therefore, I expect a correct and correct solution from the creator of the library...

@JackDaviesDesign
Copy link

I am also encountering this issue. Would be great to get a solution!

@sdp8483
Copy link
Owner

sdp8483 commented Oct 15, 2024

My intention was that #define ESP32CAN_DEBUG on line 9 of ESP32CAN.h would be commented out so that debug messages would not be sent over serial in the final code. I enabled the printing of errors so that I would know what state the functions were in when debugging examples but don't intend for them to always show up. They don't hurt anything, just clutter up the serial monitor.

I am sure there is a better way to do this, but I didn't look too much into it. If anyone else comes up with something that lets the user easily disable debug messages submit a pull request and I will include it into the main branch. Otherwise, if I ever get around to implementing the filter and other TODO features I will fix this issue too.

@sdp8483 sdp8483 self-assigned this Oct 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants