Skip to content

serial port malfunctioning after receiving noise that should normally be rejected as a frame error #786

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

Closed
nkostis opened this issue Oct 29, 2017 · 1 comment

Comments

@nkostis
Copy link

nkostis commented Oct 29, 2017

we have a project where esp32 serial0 is connected to a 3rd party MCU (unknown, black box to us) via transceivers (to convert RS232 voltage levels to TTL ones).

When the transceiver of the 3rd party system -i assume- initializes (while serial0 has already began) it produces noise that is definitely not a valid byte for the configured 9600/8N1
However the available() and read() functions in arduino-esp32 both hit and give us 'normal' input. While the IDF serial api provides info on framing errors, Arduino apis seem to not carry this information.

In addition, all subsequent transactions (until a reset on esp32) now carry corrupt or extra bytes interleaved with the normal ones.

This may be related to #476 which while closed, has a final comment by @me-no-dev as "I hope all issue will be fixed once I change the driver with the IDF one."

is this something that is known and/or has a timeline for fixing?

@nkostis
Copy link
Author

nkostis commented Nov 2, 2017

closing as this appears to have happened.

@nkostis nkostis closed this as completed Nov 2, 2017
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

1 participant