Legal Removal Request

Post: Try slowing down the baud rate to 9600 and see if that makes any difference. It is possible that the clock on the ESP32 does not generate a serial clock of exactly 115200 so if the Raspberry Pi clock does not match the ESP32 clock exactly it would not understand the data it is receiving. Another possible cause may be the Raspberry Pi is starting the readline() before the transmit buffer has finished sending so it could be picking up parts of the transmitted data. In the Arduino example, the TX and RX pins were connected on separate wires so the communication was full-duplex. The RS485 Pi is half-duplex so it can't transmit and receive at the same time. You may need to add in some extra code to make sure the transmit buffer is empty before you start listening for any received data. The [url=https://pyserial.readthedocs.io/en/latest/pyserial_api.html]pyserial library[/url] has an out_waiting function which gets the number of bytes in the output buffer. You should be able to use this function to wait until the number of bytes reaches 0 before calling the readline() function. Do you have an oscilloscope or logic analyser you could use to monitor the TX and RX pins on the Raspberry Pi? This would allow you to see what is being sent and received and help in finding the cause of the problem.