Edge. Modbus Serial Node. No Parity and Stop Bits?

Hello Alexander,

If you have a Debug Node after your Modbus: Read Node, what error did you get in the Debug Panel when it did not work?

I am going to try and answer all of your questions below. Let me know if I miss anything or if you have additional questions.

  1. We currently have a ticket generated to add this feature to allow the user to configure the parity, stop bits, and data bits. We are actively working on this feature now. I will add your name and request to this ticket.
  2. The Modbus: Read Node for a RTU connection is using the following values: data bits: 8, stop bits: 1, and parity: none.
  3. The port name is the same name presented in the Docker container. You get the Modbus serial data from your Edge Compute device into the Losant Edge Agent docker container following the steps listed in this post. It sounds like you have this working since an indicator light flashes on your device when your Modbus: Read Node executes.

Do you know if your Modbus network is using 8 data bits, 1 stop bit, and none for parity? If it is using these parameters then the Modbus: Read node should work for you. I cannot see the rest of your Modbus: Read Node configuration but I am assuming that you entered a register to read.

Let me know how I can continue to help or if you have more information you can provide based off of the information above. Also, let me know if there are any additional configurations besides data bits, stop bits, and parity that you would expect in a Modbus: Read Node for a RTU connection.

Thank you Alexander,
Kevin

1 Like