Author Topic: Read Modbus RTU 16bits  (Read 672 times)

mourazo

  • Newbie
  • *
  • Posts: 31
    • View Profile
Read Modbus RTU 16bits
« on: November 18, 2019, 04:17:55 PM »
I am trying to read data from a device that transmits in modbus RTU 16 bit, without existing, I obtaining a baud rate exception  when the parameter is correct, i can't read with easyModbus library, I obtain a parse int error but i can read with modbus poll program.  What is the correct way to read it?
« Last Edit: November 18, 2019, 04:26:20 PM by mourazo »

Godra

  • Hero Member
  • *****
  • Posts: 1438
    • View Profile
Re: Read Modbus RTU 16bits
« Reply #1 on: November 18, 2019, 06:05:33 PM »
In AHMI, the correct way to read it is to add ModbusRTUCom driver to the form, set COM port parameters correctly, add a BasicLabel to the form and input a PLC register address in the PLCAddressValue field. Run the program and see what that BasicLabel will show.
« Last Edit: November 18, 2019, 06:43:47 PM by Godra »

mourazo

  • Newbie
  • *
  • Posts: 31
    • View Profile
Re: Read Modbus RTU 16bits
« Reply #2 on: November 19, 2019, 02:15:03 AM »
When I execute I obtain a baudrate exception, different when I execute with a modbus 32 bits equipments, i cant find The correct configuration in a modbusRTUcom driver. Thanks

Godra

  • Hero Member
  • *****
  • Posts: 1438
    • View Profile
Re: Read Modbus RTU 16bits
« Reply #3 on: November 19, 2019, 02:40:26 AM »
You need to provide far more details like what is the model of the device you are using, what COM port parameters are you using and any other info.

Godra

  • Hero Member
  • *****
  • Posts: 1438
    • View Profile
Re: Read Modbus RTU 16bits
« Reply #4 on: November 19, 2019, 04:52:08 PM »
As a test, see if you can connect to your device with Modbus Master app from this post:

https://www.advancedhmi.com/forum/index.php?topic=765.msg15223#new

mourazo

  • Newbie
  • *
  • Posts: 31
    • View Profile
Re: Read Modbus RTU 16bits
« Reply #5 on: December 03, 2019, 12:05:40 PM »
thank you, it´s solved, it was a problem of the equipment