-
Notifications
You must be signed in to change notification settings - Fork 7.5k
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
UART Loopback doesn't work on 2.0.2 #6126
Comments
Yes, i found the PR right after posting the link. |
I'd like to also complain about hitting this issue. Manually applying #6133 does fix it. My problem was a Tesla Model S module sketch. The modules speak serial at 612.5k and you send on TX to the bank of modules which send from one to the other then loop all the way back to RX. I would not call this loopback. Loopback tends to suggest that TX is directly connected to RX by a wire with nothing in between or the hardware is directly doing this. No, this is more like token ring where the signal flows from device to device and ends up back where it started. But, really, the issue is one of full duplex. No matter what anyone says, the offending code in V2.02 most certainly puts the hardware into half duplex and this doesn't work if you have both wires active at once whether that's because the signal from TX is looping back or whether it is because you otherwise have full duplex for some other reason. So, the issue is fixed but that doesn't do normal users any good since there has not been another release. So, hopefully my verbose complaint helps anyone else searching for answers. |
Thank you for the comment. We will release 2.0.3 in a week or two and it will have the fix #6133 and others more new features. Please stay tuned! |
Related Information
#5549 (comment)
Board
ESP32, ESP32-S2 and ESP32-C3
Hardware Configuration
ESP32 - loopback on UART2 : TX2 <--> RX2
ESP32-S2 and ESP32-C3 - loopback on UART1 : TX1 <--> RX1
Description
When trying to send data in a UART loopback configuration, it fails and nothing is read.
Using Arduino Core 2.0.0 and 2.0.1 - it works fine. The issue is with v2.0.2
Most problably something related to last change on support to MODBUS #6026
Sketch
Debug Message
but with v2.0.2 there is no output after the message
Serial Port 0 - Testing
I have checked existing issues, online documentation and the Troubleshooting Guide
The text was updated successfully, but these errors were encountered: