Data Loading...

EasyIO Adv 01 - Modbus Master and Slave Flipbook PDF

EasyIO 30P Modbus Master and Slave Configurations Hardware configurations Image below shows the hardware configurations


191 Views
149 Downloads
FLIP PDF 808.14KB

DOWNLOAD FLIP

REPORT DMCA

EasyIO 30P Modbus Master and Slave Configurations

EasyIO 30P Modbus Master and Slave

EasyIO 30P Modbus Master and Slave Configurations

Document Change Log

28th October 2011 Document created. 30th March 2012 Hardware configuration added.

EasyIO 30P Modbus Master and Slave Configurations

Contents Introduction ............................................................................................................................................ 4 Hardware configurations ........................................................................................................................ 5 EasyioModbusSlave ................................................................................................................................ 6 ModbusSlaveAsyncNetwork ............................................................................................................... 6 ModbusSlaveDevice .......................................................................................................................... 10 ModbusPointCoil............................................................................................................................... 12 ModbusPointDiscrete ....................................................................................................................... 13 ModbusPointHoldingFloat ................................................................................................................ 14 ModbusPointHoldingLong ................................................................................................................ 15 ModbusPointHoldingWord ............................................................................................................... 16 ModbusPointInputFloat .................................................................................................................... 17 ModbusPointInputLong .................................................................................................................... 18 ModbusPointInputWord ................................................................................................................... 20 Configuring the Modbus Slave Network ............................................................................................... 21

EasyIO 30P Modbus Master and Slave Configurations

Introduction Every EasyIO 30P comes with a feature called Modbus Master. The EasyIO 30P can be a modbus master and slave devices can be connected to the RS 485 port on board. This feature only applicable for Modbus Async devices. BACnet MS/TP devices is not supported for with this feature.

This feature enable users to hooked up directly to a Variable Speed Drive (VSD) , Digital Power Meters (DPM) and other modbus Async devices. However there is a limitation to max devices per EasyIO 30P. Each 30P is recommended up to 4 nos MAX of slave devices.

EasyIO 30P Modbus Master and Slave Configurations

Hardware configurations Image below shows the hardware configurations for the Modbus Master and Slave feature. Integration between EasyIO 30P and NCU is either SOX protocol , Tcom (by Infocon) , Bacnet IP or Modbus TCP.

Below is the wrong perception of customers. EasyIO 30P cannot do BACnet MS/TP to BACnet IP. EasyIO 30P cannot convert MS/TP devices points to become BACnet IP points. It is not a BACnet Gateway.

EasyIO 30P Modbus Master and Slave Configurations

EasyioModbusSlave kit Components This kit contains 10 objects. All the objects are to be used for Modbus Master Slave configuration only. Modbus Master and Slave configuration is a unique configuration where , the EasyIO 30P Sedona controller as a Modbus Master Controller and Modbus Slave controller connecting to the Rs-485 com port. To use these objects just drag and drop into the wire sheet.

ModbusSlaveAsyncNetwork ModbusSlaveAsyncNetwork uses the EasyIO-30P built-in Modbus RTU master driver to connect to Modbus Slave devices.

The serial port has to be disabled first before changing parameter. Do not attempt to change the parameters via web browser. The serial port setting will automatically changed from Modbus to Modbus Master whenever you change the parameter in this object. **Note: ModbusSlaveAsyncNetwork can be in a new folder or in default EasyIO folder Example below show the ModbusSlaveAsyncNetwork is in a new folder created with the name Slave

EasyIO 30P Modbus Master and Slave Configurations

ModbusSlaveAsyncNetwork is under a new folder named Slave.

Typical Modbus Master Slave Configuration.

EasyIO 30P Modbus Master and Slave Configurations The property sheet of the object is shown below

♦ Status Network status. Readonly >0 = OK 0 = Not connected. -1 = port not available -2 = invalid baudrate -3 = invalid databit -4 = invalid stopbit -5 = invalid parity Normally the value should be “1” ♦ Port Serial port, COM1 = 1, COM2 = 2 and etc By default the Com port is = “1” ♦ Baudrate Serial port baudrate, 1200 – 115200 Default baud rate set is at 19.2K EasyIO30P default baud rate is at 19.2K ♦ Databit Serial port data bit, 7 or 8 ♦ Stopbit Serial port stop bit, 1 or 2

♦ Parity

EasyIO 30P Modbus Master and Slave Configurations Serial port parity. 0 = None 1 = Odd 2 = Even

♦ Turn Around Turnaround is the time delay in milliseconds between a message can be sent out by driver after it receive the last message.

♦ Time Out Modbus Slave device time out in milliseconds. ♦ Enable Enable Serial port ♦ Write On Up Perform a write whenever the COM/Device is up. ♦ Write On Start Perform a write whenever the COM/Device is up.

EasyIO 30P Modbus Master and Slave Configurations

ModbusSlaveDevice ModbusSlaveDevice must be child of Modbus Slave Network.It cannot be anywhere else. **Note: ModbusSlaveDevice can only be a child of ModbusSlaveNetwork Example below show the ModbusSlaveDevice is in a child oof the network.

ModbusSlaveDevicek is a child of ModbusSlaveNetwork. The property sheet of the object is shown below

♦ Fault Fault status. Readonly False = No fault True = Fault ♦ Status Current status. Readonly Alive = Slave Device Alive Down = Slave Device Down

EasyIO 30P Modbus Master and Slave Configurations

♦ Enable Enable device. ♦ Address Device Address in decimal ♦ Long Byte Order3210 Long type data (32-bit) byte order. True = 3210F False = 1032 ♦ Float Byte Order3210 Floating point type data byte order True = 3210 False = 1032 ♦ Use Preset Multiple Register True = support Modbus function 16 ♦ Use Force Multiple Coil True = support Modbus function 15 ♦ Action Version 1.0.43.21 offers device ping. Right mouse button at the device to do a force ping.

EasyIO 30P Modbus Master and Slave Configurations

ModbusPointCoil ModbusPointCoil is Modbus Coil Output Point **Note: ModbusPointCoil can only be a child of ModbusSlaveDevice The property sheet of the object is shown below

♦ Fault Status of the Modbus register. false = Valid true =Invalid ♦ Status Status of the point OK = Online Down = Offline ♦ Address Modbus register address. Note that only Decimal format is supported. If the Modbus device register is in HEX , need to convert to DEC. ♦ Out Current Coil Output state. Readonly ♦ In Local input value.

EasyIO 30P Modbus Master and Slave Configurations

ModbusSlaveDevice register example.

ModbusPointDiscrete ModbusPointDiscrete is Modbus Discrete Input point **Note: ModbusPointDiscrete can only be a child of ModbusSlaveDevice The property sheet of the object is shown below

♦ Fault Status of the Modbus register. false = Valid true =Invalid ♦ Status Status of the point OK = Online Down = Offline ♦ Address Modbus register address. Note that only Decimal format is supported. If the Modbus device register is in HEX , need to convert to DEC.

EasyIO 30P Modbus Master and Slave Configurations ♦ Out Current Coil Output state. Readonly

ModbusSlaveDevice register example.

ModbusPointHoldingFloat ModbusPointHoldingFloat is Modbus Holding Float point **Note: ModbusPointHoldingFloat can only be a child of ModbusSlaveDevice The property sheet of the object is shown below

♦ Fault Status of the Modbus register. false = Valid true =Invalid ♦ Status Status of the point OK = Online Down = Offline

EasyIO 30P Modbus Master and Slave Configurations ♦ Address Modbus register address. Note that only Decimal format is supported. If the Modbus device register is in HEX , need to convert to DEC. ♦ Out Current Coil Output state. Readonly ♦ In Local input value.

ModbusSlaveDevice register example.

ModbusPointHoldingLong ModbusPointHoldingLong is Modbus Holding Long point **Note: ModbusPointHoldingLong can only be a child of ModbusSlaveDevice The property sheet of the object is shown below

♦ Fault Status of the Modbus register. false = Valid true =Invalid

EasyIO 30P Modbus Master and Slave Configurations ♦ Status Status of the point OK = Online Down = Offline ♦ Address Modbus register address. Note that only Decimal format is supported. If the Modbus device register is in HEX , need to convert to DEC.

♦ Out Current Coil Output state. Readonly ♦ In Local input value.

ModbusSlaveDevice register example.

ModbusPointHoldingWord ModbusPointHoldingWord is Modbus Holding Word point **Note: ModbusPointHoldingWord can only be a child of ModbusSlaveDevice The property sheet of the object is shown below

EasyIO 30P Modbus Master and Slave Configurations ♦ Fault Status of the Modbus register. false = Valid true =Invalid ♦ Status Status of the point OK = Online Down = Offline ♦ Address Modbus register address. Note that only Decimal format is supported. If the Modbus device register is in HEX , need to convert to DEC. ♦ Out Current Coil Output state. Readonly ♦ In Local input value.

ModbusSlaveDevice register example.

ModbusPointInputFloat ModbusPointInputFloat is Modbus Input Float point **Note: ModbusPointInputFloat can only be a child of ModbusSlaveDevice The property sheet of the object is shown below

EasyIO 30P Modbus Master and Slave Configurations

♦ Fault Status of the Modbus register. false = Valid true =Invalid ♦ Status Status of the point OK = Online Down = Offline

♦ Address Modbus register address. Note that only Decimal format is supported. If the Modbus device register is in HEX , need to convert to DEC. ♦ Out Current Coil Output state. Readonly

ModbusSlaveDevice register example.

ModbusPointInputLong ModbusPointInputLong is Modbus Input Long point **Note: ModbusPointInputLong can only be a child of ModbusSlaveDevice

EasyIO 30P Modbus Master and Slave Configurations

The property sheet of the object is shown below

♦ Fault Status of the Modbus register. false = Valid true =Invalid ♦ Status Status of the point OK = Online Down = Offline ♦ Address Modbus register address. Note that only Decimal format is supported. If the Modbus device register is in HEX , need to convert to DEC. ♦ Out Current Coil Output state. Readonly

ModbusSlaveDevice register example.

EasyIO 30P Modbus Master and Slave Configurations

ModbusPointInputWord ModbusPointInputWord is Modbus Input Word point **Note: ModbusPointInputWord can only be a child of ModbusSlaveDevice The property sheet of the object is shown below

♦ Fault Status of the Modbus register. false = Valid true =Invalid ♦ Status Status of the point OK = Online Down = Offline ♦ Address Modbus register address. Note that only Decimal format is supported. If the Modbus device register is in HEX , need to convert to DEC. ♦ Out Current Coil Output state. Readonly

ModbusSlaveDevice register example.

EasyIO 30P Modbus Master and Slave Configurations

Configuring the Modbus Slave Network Step 1 Connect to the controller with Sedona Workbench. Default login credentials are as below; IP address : 192.168.10.10 Username : admin Password : Manage kits to install easyioModbusSlave into your controller

Make sure you install the easyio kit to 1.0.45.10 as well. You need to have the easyio.kit 1.0.45.10 in order to proceed.

EasyIO 30P Modbus Master and Slave Configurations Step 2: - Choose easyioModbusSlave from Sedona Palette -

Step 3: -

Drag & drop the ModbusSlaveNetwork into your App . The object can be anywhere in the EasyIO folder. The object can be placed in a new folder as well. In this case , the object is drop into a new folder named Modbus. The object cannot be drop into the service folder

Double click the object to get into the property sheet. You will need to configure the serial configurations according to the slave device. Enable the network. Any changes made, user need to disable and re-enable the network again.

EasyIO 30P Modbus Master and Slave Configurations Step 4: - Drop the ModbusSlaveDevice object under the Network object. - Slave device must be a child of the Network object. Renaming the object is possible. -

-

Open the property sheet of the device and configure the serial address for the device. For this example the device address = 110.

Step 5: - Now user can drop the modbus register point under the device, modbus register has to be a child of the device. - Referring to the Modbus Register document of the Modbus Slave device that is connecting to the EasyIO 30P, drop the respective point into it. - An example that we are using here is the Schneider ION 6200, modbus RTU protocol. Below is the modbus register document. - The register that describe in this document is the Frequency, Modbus address = 40115, Register type = Holding register, Data type = Integer16, scale = 100.

EasyIO 30P Modbus Master and Slave Configurations

-

Point type that should be use from the ModbusSlave kit is ModbusPointHoldingWord.

Step 6: - Configure the register address. Referring to the document, Frequency register address is modbus = 40115 or decimal = 114. - The register address may vary depending on manufacturer (zero based or one based). - EasyIO sedona will only accept decimal format for the modbus register.

-

The value shown = 4994 , multiplier according to the document = 100. In order to get the correct value , 4994 / 100 = 49.94Hz.

Step 7: - Continue Step 5 and Step 6 for other points.