Python Forum
Raspberry + RS485 shield | pySerial
Thread Rating:
  • 3 Vote(s) - 2.67 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Raspberry + RS485 shield | pySerial
#5
Sorry for the awol. I've been meddling with other stuff. Thanks for the additional insight.

About the baud rate I'm pretty sure it is the same at both ends of the connection. I have some basic information, a document, about the serial communication used by the device, including the baud rate and I am using that for my python serial port configuration.
Unfortunately, I don't have any tools to measure it.

Regarding the integrity of the message I send from my RPI to the device, I tried to see what actually reaches the equipment by doing the following setup ( I think you will need to click on the image to enlarge it)
[Image: l6JKU4R.png]
I sent my message from the RPI to Device 1 and with the sniffer on PC (that was connected through serial with Device2 | Device 2 was connected to Device 1 | No link from RPI to PC) I saw on the PC the exact message sent without any noticeable distortion.
That made me believe, that a theoretically correct code, reaches Device 1.
That's the best I could do for now and with the tools I had.

More tests are coming with different settings. Will post any worthy failures and/or breakthroughs.

Thanks again !
Reply


Messages In This Thread
Raspberry + RS485 shield | pySerial - by Coada - Feb-24-2017, 12:04 PM
RE: Raspberry + RS485 shield | pySerial - by Coada - Mar-01-2017, 07:54 AM
RE: Raspberry + RS485 shield | pySerial - by Coada - Apr-13-2017, 01:55 PM

Possibly Related Threads…
Thread Author Replies Views Last Post
  help with code for USB-RS485 korenron 3 3,685 Nov-17-2022, 09:04 AM
Last Post: wiseweezer
  Help reading data from serial RS485 korenron 8 14,050 Nov-14-2021, 06:49 AM
Last Post: korenron
Photo Raspberry PI writing to RS485 driver, DIR pin not holding state zazas321 2 2,139 Oct-30-2020, 06:23 AM
Last Post: zazas321

Forum Jump:

User Panel Messages

Announcements
Announcement #1 8/1/2020
Announcement #2 8/2/2020
Announcement #3 8/6/2020