Modbus server tcp serial serial#
Modbus server tcp serial driver#
Modbus server tcp serial code#

Device ID will be the Modbus Slave Node ID assigned to the meter (keep this at 1 if you are unsure what this should be). Here you will also keep most of the default settings. Change this from 'COM Port' to 'Ethernet Encapsulation'.ģ. Keep most of the default settings for the Channel until you see the Physical Medium.

Modbus server tcp serial serial#

In KEPServerEX (Industrial Connectivity), create a new Channel, and select the Modbus RTU Serial driver.Ģ. Modbus RTU is the original Modbus protocol, and even with the TCP header, it is slightly different from the Modbus TCP (Modbus Ethernet) protocol.įollow these steps to connect with this device:ġ. This header is removed/added as it passes to/from the Serial/Ethernet gateway. Ethernet encapsulation adds a TCP header to the serial-based Modbus RTU protocol.

Modbus server tcp serial driver#

It should be possible to use the KEPServerEX Modbus RTU Serial driver with Ethernet Encapsulation to interface with this level meter device. I can't tell, how do you extrapolate the units from what the Device has sent? It appears the units might be a setting put in place on this Device that will be universal for all values. While you will not be able to embed the units with the raw value in the same tag, It may be possible to create a separate tag that contains a String value representing the units. By creating a Derived Tag within Advanced Tags, you could apply arithmetic operations to a value to produce a new value that will be read by a Client or ThingWorx (for example, to multiple the value by 1000).

There is an internal Client Plug-in available called Advanced Tags. To multiply the value, you will need use a Client application, or ThingWorx. Simply Modbus is also an excellent resource for understanding this protocol:įor the second part of your question, is it important to note KEPServerEX is bringing the raw values from the Device and converting them into whichever Data Type you have specified. Are you seeing the value you expect? You may need to Disable the 'Modbus Byte Order' in the Device Properties > Settings property group.įor more information on Modbus addressing, here is a link to the 'Modbus Addressing' section of the KEPServerEX Modbus RTU driver help manual: Launch the Quick Client and locate your tag. This is the default 16-bit (2 byte) Modbus Holding Register data type.Ĥ. For the Data Type, keep this as Default, or manually set it to Word. 0000 is 40001, 0001 is 40002, etc) or you can disable this setting in the Device Properties, within the Settings property group (i.e. You can shift all of your address by 1 (i.e. Per the Modbus Spec, the default setting for 'Zero-based addressing' is Enabled.

Modbus server tcp serial code#

Since the address is an 'Analog Output', being read by Function Code 3, this tells us it is an Analog Output Holding Register in KEPServerEX, which is addressed as '4xxxx'. Name it '0000', to align with the documentation you have for the device.Ģ. To read the '0000' register, here are the steps you will want to follow:ġ.

Thanks for sharing the device documentation, that gives us some key insight.