Modbus Utility Manual

Modbus Utility User Manual

April 2014

Version 1.0.2

Table of Contents

Contents ...................................................................................................... 2

1.

1.1

1.2

Introduction ............................................................................. 5

Instruction to the User Manual ................................................................. 5

Modbus Protocol ....................................................................................... 6

1.3

1.4

Default Firmware Features ....................................................................... 7

Typical Applications .................................................................................. 9

2.

2.1

2.2

Starting the Modbus Utility ................................................... 13

Instruction to the Working Area ............................................................. 15

Updating the Firmware ........................................................................... 17

2.2.1. Updating via the Ethernet ....................................................................... 17

2.2.2. Updating via a Serial Port ........................................................................ 20

2.3 Network Settings ..................................................................................... 23

2.3.1. Method 1: Under Running Firmware Mode ........................................... 23

2.4

2.3.2. Method 2: Under Initial Mode ................................................................ 26

Net ID (Station number) Setting ............................................................. 28

2.5 Connecting to the Controller .................................................................. 29

2.5.1. Connect via the Ethernet (Modbus/TCP) ................................................ 29

2.5.2. Connect via a Serial port (Modbus/RTU) ................................................ 30

2.6

2.5.3. Refresh Configuration after Connecting ................................................. 31

Address Table (Mapping Table) .............................................................. 32

2.7

2.8

Library Version ........................................................................................ 33

Range Code and Offset Settings.............................................................. 34

2.8.1. Range Code ............................................................................................. 34

Copyright © 2013 ICP DAS Co., Ltd. All Rights Reserved. E-mail: [email protected]

2

2.9

2.8.2. Offset Settings ......................................................................................... 35

Digital Output Power-on and Safe Values .............................................. 36

2.9.1. Digital Output Power-on Value ............................................................... 36

2.9.2. Digital Output Safe Value ........................................................................ 37

2.10 Analog Output Power-on and Safe Values.............................................. 39

2.11

2.12

2.10.1.

2.10.2.

Analog Output Power-on value ....................................................... 39

Analog Output Safe Value ............................................................... 40

87K Digital Input Counter ........................................................................ 42

COM Port Settings ................................................................................... 44

2.12.1.

2.13

COM Port Enable Modes ................................................................. 45

Watchdog Timer (WDT) Settings ............................................................ 47

2.14 Monitoring .............................................................................................. 49

2.15

2.16

2.17

2.18

2.19

Trend ....................................................................................................... 52

Data Log .................................................................................................. 56

Save and Load the Configuration Settings .............................................. 58

Modbus RTU Master Tool ....................................................................... 59

Modbus TCP Client Tool .......................................................................... 62

3.

3.1

Linking to SCADA Software via Modbus ....................................... 65

Vijeo Citect .............................................................................................. 66

3.1.1. Creating a New Project, an I/O Server and an I/O Device ...................... 66

3.2

3.1.2. Designing the Layout and Acquiring the Data ........................................ 74

DASYLab .................................................................................................. 94

3.2.1. Adding an Analog Input Channel ............................................................ 94

3.2.2. Adding an Analog Output Channel ......................................................... 99

3.2.3. Adding a Digital Input Channel ............................................................. 104

3.3

3.2.4. Adding a Digital Output Channel .......................................................... 108

EZ Data Logger ...................................................................................... 112


3

3.3.1. Adding the I/O Modules to the Workgroup .......................................... 112

3.3.2. Designing the Layout and Acquiring the Data ...................................... 124

Appendix A: Backing Up and Recovering the EEPROM Settings ................ 128

1. Backing up the Settings ......................................................................... 129

2. Recovering the Settings ........................................................................ 132

Appendix B: Function Codes (FC) ............................................................. 135

1. Read DO (0xxxx) .................................................................................... 136

6.

7.

8.

4.

5.

2.

3.

Read DI (1xxxx) ...................................................................................... 137

Read AO (4xxxx) .................................................................................... 138

Read AI (3xxxx) ...................................................................................... 139

Write Single DO (0xxxx) ......................................................................... 140

Write Single AO (4xxxx) ......................................................................... 141

Write DO (0xxxx) ................................................................................... 142

Write AO (4xxxx) ................................................................................... 143

Appendix C: Supported Modules ............................................................. 144

Appendix D: Range Codes for Analog Modules ........................................ 145

1. 87K Analog Modules ............................................................................. 146

1.1. Current and Voltage Type Definitions .................................................. 146

1.2. Thermocouple Type Definitions ............................................................ 151

1.3. RTD (Resistance Temperature Detector) Type Definitions ........................ 153

2.

1.4. Thermistor Type Definitions ................................................................. 157

8K Modules ........................................................................................... 160


4

1. Introduction

1.1 Instruction to the User Manual

Modbus is a very popular protocol used in the industrial manufacturing and environment monitoring fields. The Modbus Utility provided by ICP DAS can be used to communicate with the Host controller to retrieve data from remote modules.

This manual describes how to use the Modbus Utility in conjunction with controllers that support the Modbus protocol. Also included are instructions for linking SCADA (Supervisor Control and Data Acquisition) software Modbus devices

.

This manual applies to following controllers and modules.

Model

I/O

Slots

CPU SRAM Flash

Memory

Expansion

Ethernet

RS-232

/485

I-8431-MTCP

I-8331-MTCP

I-8431-80-MTCP 4

I-8831-80-MTCP 8

I-8KE4-MTCP-G 4

I-8KE8-MTCP-G

IP-8441-MTCP

4 40

8

MHz

8

4

80

MHz

IP-8841-MTCP 8

ET-87P4-MTCP 4

-

512

KB

768

KB

-

512

KB

-

-

Micro SD

-

1

(10BASE-

T)

2

(10/100

BASE-Tx)

3

1

4

1

ET-87P8-MTCP 8

I-7188EX(D)-MT

CP

I-7188E2(D)-MT

CP

-

-

40

MHz

512

KB

384

KB

512

KB

-

-

1

(10BASE-

T)

2

μPAC-7186EX(D)

-MTCP

-

80

MHz

512

KB

-

1

(10/100

BASE-Tx)


5

1.2 Modbus Protocol

1.2.1. What is the Modbus protocol?

Modbus is a communication protocol originally developed for Modicon controllers by Modicon Inc. in 1979. Modbus is a standard, truly open protocol and is the most widely used network communication protocol in industrial automation field. SCADA

(Supervisor Control and Data Acquisition) and HMI (Human-Machine Interface) software can be used to easily integrate serial devices via the Modbus protocol.

1.2.2. What is the Modbus/TCP protocol?

The Modbus/TCP protocol is a variant of original Modbus protocol that was developed in 1999 to allow access to Ethernet devices by the Internet community.

1.2.3. What software supports the Modbus and Modbus/TCP protocol?

Most SCADA and HMI software packages include support for the Modbus protocol.

For example: ControlMaestro, DASYLab ,

EZ Data Logger , GENESIS 32/64, iFIX,

InduSoft Web Studio, LabView, Trace Mode, Vijeo Citect , Wonderware Intouch, etc.

1.2.4. What are the benefits of using Modbus and Modbus/TCP?

A.

Open source, no license fees.

B.

Widely supported by SCADA and HMI software

C.

Easy to use

D.

Easily integrated with a variety of devices

E.

Low development cost

F.

Wide knowledge base

1.2.5. Modbus Resources

A.

http://www.modbus.org

A community for Modbus users.

B.

http://www.modbustools.com/modbus_activex.asp

An ActiveX control to communicate with a Modbus slave device via Modbus

(RTU/ASCII) or Modbus/TCP.


6

1.3 Default Firmware Features

When purchased, the IP-8000-MTCP/I-8000-MTCP controller, already has the default Modbus firmware in Flash memory, and includes the following features.

1.3.1. Support for the Modbus/TCP communication protocol that allows access

to I/O devices that are inserted in the I/O slots.

The default firmware allows user to connect to the controller by Ethernet, and send Modbus commands in Modbus/TCP protocol form.

1.3.2. Support for the VxComm technique for all COM ports on connected

controllers.

Even if a serial device doesn't support the Modbus/RTU protocol, it can still be accessed via Ethernet. However, the VxComm driver will first need to be installed on the host PC and COM ports assigned in order to link to the controller’s COM ports. Once installed, the serial clients will then be able to access these remote serial devices via Ethernet using the standard RS-232 functions. Here’s the link of the VxComm driver for PC. http://ftp.icpdas.com/pub/cd/8000cd/napdos/driver/vxcomm_driver/2k/

1.3.3. Automatic I/O module scanning.

When a connection created, the default firmware will scan all slots and then put modules information into the “Summary” table.

1.3.4. Automatic assignment of a register address for the I/O modules.

An I/O module can be inserted into any slot and the Modbus firmware will automatically scan all slots and assign the I/O channels to register in a continuous range. The register mapping for all the I/O channels can be retrieved by connecting to the controller using the Modbus Utility.

1.3.5. Allows simultaneous access by multiple clients (or masters).

Different controllers support a different number of connections to a client. For more details, refer to the FAQ on ICPDAS web site.


7

http://www.icpdas.com/faq/7188e/hardware/003.htm

1.3.6. Online configuration via Ethernet using the Modbus Utility

1.3.7. Supports I-8000 and I-87000 series I/O modules

1.3.8. Updateable and programmable firmware

The Modbus SDK provided by ICP DAS allows users to develop custom Modbus firmware. The link for IP-8000-MTCP shows as below. http://ftp.icpdas.com/pub/cd/8000cd/napdos/modbus/ip8000/demo/bc/


8

1.4 Typical Applications

1.4.1. Basic Application 1: Modbus TCP I/O Device

An I-8000-MTCP running the default firmware operates as a Modbus/TCP slave I/O device. Simply use the Modbus Utility to configure the device and then create a connection between the SCADA/HMI software and the

I-8000-MTCP.


9

1.4.2. Basic Application 2: Modbus/RTU to Modbus/TCP Converter

After setting the COM Port to gateway mode via the Modbus Utility, the

Modbus/RTU device can be linked to the I-8000-MTCP using the Modbus/TCP protocol. The SCADA/HMI software can then be configured to convert the

Modbus/RTU device to a Modbus/TCP device.


10

1.4.3. Basic Application 3: Modbus/TCP I/O Device using the VxComm

Technique

An I-8000-MTCP is also able to link serial devices that are connected to the

COM ports on the I-8000-MTCP device. To use this function, the VxComm driver first needs to be installed on the Host PC. After the driver is installed, the remote COM ports can be accessed via the standard serial driver.


11

1.4.4. Advanced Application 1: User-defined Modbus/TCP Controller

Using the Modbus SDK, custom firmware can be developed that allows access to additional functions, together with integration of serial devices with

Modbus/TCP kernel, making the I-8000-MTCP a powerful controller. The link for I-8000-MTCP shows as below. http://ftp.icpdas.com/pub/cd/8000cd/napdos/modbus/8000e/demo/bc/

1.4.5. Advanced Application 2: Modbus/TCP Controller using the VxComm

technique

If an I-8000-MTCP is used to link same hardware devices as described in

Advanced Application 1 above, and if any of devices connected to specific COM ports are not integrated into the custom firmware, the COM ports can still be accessed using the standard serial driver. However, in order to do this, the

VxComm driver must first be installed on the Host PC.


12

2. Starting the Modbus Utility

Follow the instructions described below to establish a connection between the controller and the Modbus Utility, then retrieve and set the I/O value.

Install the Modbus Utility and update the firmware of controller to the latest version

Configure the Network Settings

Configure the Net ID Setting

Connect

Confirm Information

Configure the Module

COM Port Settings

Address Table

(Mapping Table)

Library Version

Range Code & Offset

Power-on &

Safe Values

87K DI Counter

Set the Watch Dog Timer

Start Acquiring Data

Monitor

Tren Log file

Save and Load

Configuration Settings


13

The Modbus Utility executable file can be downloaded from http://ftp.icpdas.com/pub/cd/8000cd/napdos/modbus/modbus_utility/


14

2.1 Instruction to the Working Area

The following is an illustration of the main working area of the Modbus Utility.

A

B

C D

E

F

A.

Menu Bar

B.

Tool Bar

C.

Connection panel

D.

Power-on value, safe value ,offset and DI Counter settings panel

E.

Controller Panel and Module Panel

Left-hand side: COM ports and Watchdog Timer (WDT) settings

Right-hand side: Module setting panel.

F.

Address table (mapping table)


15

Note: If the warning message shown below is displayed after executing the Modbus

Utility, reboot the program by right-clicking on the shortcut and clicking "Run

As Administrator" to open the application with Administrator privileges.

Right-click on the shortcut


16

2.2 Updating the Firmware

This function is used to update the firmware to the latest version. The firmware can be updated using either a COM port or a UDP connection. However, ensure that the LAN1 or COM1 ports are connected to the network or the computer before attempting to update the firmware.

2.2.1. Updating via the Ethernet

Step 1: Reboot the controller in INIT mode.

For I-8000 modules, short the INIT* and INIT*COM pins.

For IP-8000 and ET-87PN modules, move the DIP switch to the “Init” position.

For 7188E devices, short the INIT* and GND pins.

Step 2: Execute the Modbus Utility and select the Modbus/TCP mode.

Step 3: Select the “Update Firmware” option from the “Client Tools” menu to connect to the controller.


17

Select UDP option from the drop-down menu. If IP address is known, enter the details in the text field and then click the “Connect” button. Alternatively, click the

“Search IP” button to search for available controllers on the LAN port and then double-click IP address to establish a connection.

Method 1

Search for available controllers and then double-click the IP address to connect.

Method 2

Enter the IP address here and then click “Connect”.

After connecting, the firmware file for the controller will be listed in the “Update

Firmware” tab, as shown in the diagram below.


18

Step 4: Before updating the firmware, all existing files must be deleted. Click the

“Erase Disk” button to delete all files currently existing on the controller.

Step 5: Select the new firmware file and then click the “Upload >>” button. After the update process is completed, the new file will be displayed in the file list. If it is not displayed, click the “Refresh file list” button to display the latest files.


19

2.2.2. Updating via a Serial Port








20

Select the required COM port from the drop-down menu and click the "Connect" button. After connecting, the firmware file for the controller will be listed in the

"Update Firmware" tab, as shown in the diagram below.

Note: The default COM port settings are "115200, N, 8, 1”.

Step 4: Before updating the firmware, all existing files must be deleted. Click the

“Erase Disk” button to delete all files currently existing on the controller.


21

Step 5: Select the new firmware file and then click “Upload >>” button. After the update process is completed, the new file will be displayed in the file list. If it is not displayed, click the “Refresh file list” button to display the latest files.


22

2.3 Network Settings

Before starting the configuration process, ensure that LAN1 or LAN2 are connected to your network. There are two methods of configuring the network using a UDP connection.

2.3.1. Method 1: Under Running Firmware Mode

Step 1: Make the controller under the running firmware mode.


Step 3: Select the “UDP Search” option from the “Client Tools” menu to open the eSearch Utility.


23

Step 4: Click the “Search Servers” button to search for the controllers on the LAN.

Step 5: Select the controller that is to be configured and then click the

“Configuration (UDP)” button.


24

Enter the required details in the IP, Mask, Gateway, Alias and DHCP fields, and then click the “OK” button to save the settings.


25

2.3.2. Method 2: Under Initial Mode






Step 3: Select the “Update Firmware” option from the “Client tools” menu.


26

Step 4: Select the UDP option from the drop-down menu, and click the "Search IP" button to search for available controllers. When the search is completed, select an IP address and click the “Connect” button to establish a connection.

Step 5: Select the “Network Settings” tab and then click the “Get Settings” button.

The current network settings will be displayed in the LAN 1 text fields. Edit the settings as required and then click the "Save Settings" button to save the new settings.

After setting the new network, the Modus Utility will connect to new IP address automatically.


27

2.4 Net ID (Station number) Setting

The Net ID can be from 01 to FF and must be unique in the network. Set Net ID by following the procedure described below.

Step 1: The Net ID is set using the 8-bit DIP switch located on the right-hand side of the controller. To set the Net ID, move the DIP switch for the required bit to the ON position. The following figure shows the Net ID for the controller. Bits 1 and 2 are in the ON position and the others are set to OFF, meaning that the

Net ID for the controller is 3.

Step 2: Reboot the controller to set the new Net ID

Step 3: After connecting to the controller, the Net ID for the controller will be

displayed in the connection panel as described in Instruction to the Working

Area

index C.


28

2.5 Connecting to the Controller

Before performing the following operation, set the controller to "Run Firmware" mode, insert the modules, and then turn on the power.

2.5.1. Connect via the Ethernet (Modbus/TCP)


Step 2: Enter the IP address for your controller, and then click the “Connect” button.

If a connection is successfully established, the status will be displayed in the text filed indicated in the diagram below.


29

2.5.2. Connect via a Serial port (Modbus/RTU)

Step 1: Execute the Modbus Utility and select the Modbus/RTU mode.

Step 2: Select the COM port and click “Connect” on the connect panel.

Step 3: Click the “Search” button to search for any available device. After locating the required device, click the “Stop” button to stop searching.


30

Step 4: Select the Net ID from the list, and then click the “Connect to selected ID” button to establish a connection.

If COM port is successfully opened, the status will be displayed in the text filed indicated in the diagram below.

2.5.3. Refresh Configuration after Connecting

If the current configurations for the modules on the controller do not match the setting stored in the EEPROM, click the “Refresh” button to save the current configuration to the EEPROM.


31

2.6 Address Table (Mapping Table)

After connecting to the module, use the Summary tab on the address table to check the information related to the module, including the slot number for the module and address of the I/O channels (points).

Note: The I/O addresses here are Base 0.


32

2.7 Library Version

The version of the library depends on the version of the firmware. The latest version of the firmware can be obtained from the following addresses.

For 7188E: http://ftp.icpdas.com/pub/cd/8000cd/napdos/modbus/7188e/firmware/

For ET-87PN: http://ftp.icpdas.com/pub/cd/8000cd/napdos/modbus/et87pn/firmware/

For I-8000-MTCP: http://ftp.icpdas.com/pub/cd/8000cd/napdos/modbus/8000e/firmware/

For IP-8000-MTCP: http://ftp.icpdas.com/pub/cd/8000cd/napdos/modbus/ip8000/firmware/

Check the version information for the library using the following procedure:

Step 1: Select the “About” option from the “Help” menu.

Step 2: The version information will be displayed in the Modbus Utility “About” dialog box. The Modbus library and the I/O scan library are related to the firmware name. The format of the version information is as follows.


33

2.8 Range Code and Offset Settings

To change the range code and offset settings, click the module that is to be configured to open the Settings panel.

The image here shows the I-87028U module as an example.

2.8.1. Range Code

Range code is used to set the maximum and minimum input/output range for the module and only signals within this range can be legally transmitted.

Configure the Range Code setting in the Settings panel, and then click the “Set All” button to apply the new settings.

The range code types and definitions for modules are shown in Appendix D: Range

Codes for Analog Modules .


34

2.8.2. Offset Settings

An offset value can be set to compensate for any inaccuracies that exist in the module. Enter an offset value in the text field for the relevant channel, and then click the “Set All” button to apply the new settings


35

2.9 Digital Output Power-on and Safe Values

To change the Digital Output Power-on and Safe values, click the module that is to be configured to open the Settings panel.

The image here shows the I-87061 module as an example.

2.9.1. Digital Output Power-on Value

The Power-on value is the Digital Output value that will be set for the module when the controller is powered on every time.

Step 1: In the “DO Power-on” tab of the DIO Settings dialog box, check the checkbox(es) for the channel(s) to be set, and then click the “Set DO Power-on

Value” button to apply the Power-on value.


36

Step 2: The controller should be rebooted if the new Power-on settings would like to be applied. After rebooting, the Power-on value will be displayed in the DO

Mapping tab in monitoring mode, or check the output LED.

After rebooting the controller, the values for channel 0 to 2 display the Power-on values.

2.9.2. Digital Output Safe Value

If Modbus communication with the controller is lost for longer than the defined timer period, the Watchdog will be triggered and all modules will be set to a preset

Safe Value.

In the “DO Safe Value” tab of the DIO Settings dialog box, check the checkbox(es) for the channel(s) to be set, and then click the “Set DO Safe Value” button to apply the

Safe value.


37

After the Watchdog has been reset the modules, the DO value will be set to the Safe value.

After the Watchdog reset, the values for channel 13 to 15 display the Safe values.


38

2.10 Analog Output Power-on and Safe Values

To change the Analog Output Power-on and Safe values, click the module that is to be configured to open the Settings panel.

The image here shows the I-87028C module as an example.

2.10.1. Analog Output Power-on value

The Power-on value is the Analog Output value that will be set for the module when the controller is powered on every time.

Step 1: In the Range Code dialog box, enter a Power-on value in the text box(es) for the relevant channel(s), then click the “Set All” button to apply the Power-on value(s).


39

Step 2: The controller should be rebooted if the new Power-on settings would like to be applied. After rebooting, the Power-on value will be displayed for the channel in the AO Mapping tab in monitoring mode, or use a monitoring tool to detect the value.

After rebooting the controller, the value for channel 0 displays the Power-on value.

2.10.2. Analog Output Safe Value

If Modbus communication with the controller is lost for longer than the defined timer period, the Watchdog will be triggered and all modules will be set to a preset

Safe Value.

In the Range Code dialog box, enter a Safe value in the text box(es) for the relevant channel(s), then click the “Set All” button to apply the new Safe value(s).


40

After the Watchdog has been reset the modules, the DO value will be set to the Safe value.

After the Watchdog reset, the value for channel 7 displays the Safe value.


41

2.11 87K Digital Input Counter

For 87K series modules, the DI channels can also be used as a Low-speed (<100Hz) counter. Click the module that is to be configured to open the Settings panel.

The image here shows the I-87046 module as an example.

Step 1: In the “DI Counter” tab of the DIO Settings dialog box, check the checkbox(es) for the channel(s) to be set, and then click the “Set DI Counter” button to apply the new settings.

The channel set to be a DI counter will be displayed in the AI Mapping tab.


42

Step 2: After the counter(s) for the DI channel(s) have been set, click the AI

Mapping tab to display the channels that have associated counters, together with the current values for the counter.

Note: To get the current counter values needs to enable the

Monitoring function

first.

Step 3: To clear counter value, click the DO Mapping tab and then double-click the relevant channel. The counter value for the channel will then be set to 0.

Double-click the Value column for channel 0.

The counter value for the channel 0 becomes zero.


43

2.12 COM Port Settings

Step 1: To adjust the configuration for the COM ports, click the COM port icon to display the “COM port settings” panel.

Step 2: Select the port to be configured from the drop-down menu, and then select the enable mode, Modbus timeout and the other setting. There are seven modes can be selected for the COM port. When all the settings are done, click the “Set” button to apply for new settings.


44

The new settings will be displayed in the “System Settings” panel immediately.

2.12.1. COM Port Enable Modes

Seven modes can be selected for the COM port, each of which are described below.

A.

VxComm: This option creates virtual COM ports and maps them to the Ethernet ports on the serial modules.

B.

Modbus/RTU Gateway: This option allows the COM port to connect to up to 255

RTU slaves (stations). Enter the number of devices connected to the RTU gateway in the “Stations per COM Port” text field and then click the “Set” button. The Modbus Utility will automatically assign the Slave ID if more than one port is set to the RTU gateway mode.

C.

Modbus/RTU Slave: This option is used to set the device to operate as a

Modbus/RTU Slave.

D.

Modbus/ASCII Slave: This option is used to set the device to operate as a

Modbus/ASCII Slave.

E.

Programming: This option is used for programming only and will not automatically detect Modbus request.

F.

Debug: This option is used to display debug messages relating to Modbus requests, or communication messages, etc. while communicating with a


45

Modbus master or Modbus clients.

G.

Console: This option is used to perform configuration for file uploads, or updating the firmware for the device.


46

C

D

A

B

2.13 Watchdog Timer (WDT) Settings

Every controller has the Watchdog that will be activated when crashed or hanged happened to the controller. The Watchdog Timer is to count down when the controller lost the Modbus communication for a specified period. When the

Watchdog Timer counts to zero, the Watchdog will be activated and all analog/digital output modules will be set to their preset Safe values and the L3 LED on the panel will flash to indicate that an error has occurred.

Click the Watchdog icon to open the setting panel.

A.

CPU Reset Status: Indicates whether the current status was set during a normal power-on or if it was reset by the CPU Watchdog.

By Power on: This status message will be displayed if the controller was started normally.

By CPU WDT: This status message will be displayed if the controller encountered an error that caused the CPU Watchdog to reboot the controller.

B.

CPU Reset Event: Indicates the number of times the controller has been reset due to CPU and power-on events. Clicking the “Clear” button will reset the counter to 0.


47

C.

Watchdog Timer: Indicates the count-down duration of the Watchdog Timer. To enable the Watchdog Timer, the duration has to be set more than 5 seconds and the “Set” button has to be clicked for applying the duration.

D.

WDT Event Counts: Indicates the number of times the controller has been reset due to Watchdog Timer events. Clicking the “Clear” button will reset the counter to 0.


48

2.14 Monitoring

The Monitor function is used to retrieve I/O values immediately and also set the output values.

Step 1: In the monitor drop-down menu, click “Timer interval” to set timer scan interval.

Step 2: Click the “Monitor” button in the tool bar to begin scanning. After the monitoring process begins, the "Monitor" icon will show an active icon as below. To stop monitoring process, click the “Monitor” button again.

The I/O values in the mapping table will be refreshed periodically, but the update frequency depends on the value set for the timer interval.


49

Step 3: The display mode for analog modules can be changed to either Value,

Decimal or Hexadecimal format. Click the “Scale” button and select the desired option from the drop-down list.

Value Decimal Hexadecimal

Step 4: This step is to set the output values for analog output modules. To change the output values for a specific channel, double-click the row to relevant channel in the AO Mapping table to open the “Channel” dialog box. Enter the value and then click the “OK” button. The value to the channel will be changed.

Double-click the row.


50

Step 5: This step is to set the output values for digital output modules. To change the output values for a specific channel, double-click the row to relevant channel in the DO Mapping table. The value to the channel will be changed immediately.

Double-click the row of channel 0.

Note: The Modbus Utility also has an alert system that warns when an 87K module is off line. If the module is off line, the image for the unit will be displayed in red and the value in the DI Mapping table will be shown as 0. Both the image and the value will return to normal once the module is online.


51

A

B

2.15 Trend

In addition to retrieving data values from the address table, the Trend function can be used to monitor data and display it as a trend chart. The following illustration is the working area of the Trend function.

C

A.

Setting and control area: In this area can set condition to add an address, and to start or stop monitoring, and change the scope range.

B.

List of trend chart area: In this area can display the addresses that were added to Track area, and adjust the settings for respective address, and set the output values to the addresses of DO/AO.

C.

Track area: The Trend function has four areas to monitor and display the data, and these four areas are named as Track 1, Track 2, Track 3 and Track 4. Track

1 can only display analog module trend lines, and Track 2 to 4 can display digital module trend lines.

The following procedures indicate the setting to retrieve data.


52

Step 1: Click the “Trend” button on the main menu to open the “Scope” dialog box.

Step 2: To record I/O data on the trend chart, select the I/O type and address from the respective drop-down menus. Select a color for the chart line and assign a track number, and then click the “Add” button to add the record to the Track area.

After adding the address to the Track area, the address can be set visible or not on the Track area by clicking the checkbox or change line color by clicking the color column.

Step 3: To set the output values for the DO addresses, click the address column and then the “Channel Information” dialog box will show. Click the “On” button to set the value of DO address to on and click the “Off” button to set the value to off, and click the “Inverse” button to set the value contrary to current value.

Click the address column.


53

Step 4: To set the output values for the AO addresses, click the address column and then the “Channel Information” dialog box will show. Enter the output value and then click the “Set” button to apply the setting.

Click the address column.


54

Step 5: To change the scope range, click the “Axis” button to open the “Change

Scope Range” dialog box. Adjust the settings as necessary and then click the

“Set” button. The details shown in the “Change Scope Range” dialog box can also be fine-tuned by dragging either of the scale arrows illustrated in the image below.

fine-tuning


55

2.16 Data Log

The data log function can be used to record the configuration of the modules, together with the current values, and then save the information as a text file.

Note: The Monitoring function must be active before the Data Log function can be activated.

Step 1: First, set a name for the log file by clicking the “Log File” option from the

“Log” drop-down menu in the “Settings” menu. If a name is not set for the log file, the default file name "yyyymmdd.txt" will be used and stored in the "log" subdirectory.

Step 2: Click the “Log” icon to begin recording log data. Once recording begins, the

Log icon will show an active icon as below.


56

Step 3: To open the data log file, click the “Log” icon to stop recording first and then click the “Open Log” option in the drop-down menu of “Log” icon to open the data log. The I/O data will be display in the data log text file.


57

2.17 Save and Load the Configuration Settings

The Modbus Utility allows the configuration of the module to be saved for future use, meaning that it can be loaded the next time the Modbus Utility is used without needing to set the configuration again.

After clicking the “Save” icon, the Modbus Utility will generate two files. The default file names are Modbus_8E.ini and Modbus_8E.txt.

Two methods can be used to review the settings of both a specific controller and each module that is inserted in it.

A.

Using the Modbus Utility: Click the “Load” icon to load the .ini file to the Modbus

Utility.

Load “ModBus_8E.ini” to the Modbus Utility.

B.

Using a text editor (such as Notepad): Open the .txt file in the text editor to view the details.

Open “ModBus_8E.txt” in the Notepad.


58

2.18 Modbus RTU Master Tool

The Modbus RTU (MRTU) Master Tool can be used to send Modbus message to read or write I/O values via the COM port. The following image provides an overview of the MRTU Master Tool interface.

A B

C

D

E

A.

COM Status: Connect to the controller is related to the “Open” button and disconnect to the controller is related to the “Close” button.

B.

Protocol Description: This section provides a description of the request and the

response. For more detailed information regarding this section, see Appendix

B: Function Codes (FC)

C.

Polling Mode: The waiting period to this mode will not be more than the timeout. The next command will be sent immediately once receive the response. This mode is used to perform the transmitting time and the timeout is set to be the maximum waiting period. Click the “Start” button to activate

Polling Mode and click the “Stop” button to cancel it.


59

Timer Mode: Enter a value that must elapse before a command is sent in the

"Interval" textbox. Click the “Start” button to activate Timer Mode and click the

“Stop” button to cancel it.

D.

Command: This section is used to enter commands. Click the “Send Command” button to transmit to commands.

E.

Command/Response: Commands sent to the controller will be displayed in the left-hand text field, and the related response will be displayed on the right.

Use the following procedure to send a Modbus command.

Step 1: Set the COM Port mode to Modbus RTU Slave. For more details of the

procedure, see Section 2.12 COM Port Settings .

Step 2: Click the “Modbus/RTU Client” option from the “Clients tools” menu.

Step 3: In the COM Status section, select COM Port and Baud Rate from the respective drop-down menus and then click the "Open" button to establish a connection to the COM Port.

Step 4: In the Command section, enter a command and click the "Send Command" button to transmit the command. Ensure that the "Include CRC" option is checked to automatically add a Checksum to the end of the command.


60

Step 5: The command will be displayed on the left-hand side of the

Command/Response window, and the response will be shown on the right-hand side. Note that the last two bytes are the CRC.

Responses Commands


61

2.19 Modbus TCP Client Tool

The Modbus TCP (MTCP) Client Tool can be used to send Modbus message to read or write I/O values via the Ethernet. The following image provides an overview of the MTCP Master Tool interface.

A B

C

D

E

A.

Modbus TCP: Click the “Connect” button to connect the controller using the selected IP address and Port number. Click the “Disconnect” button to end the connection.

B.

Protocol Description: This section provides a description of the request and the response. Note that a 6-byte prefix must be used for the Modbus TCP protocol.

For more detailed information regarding this section, see Appendix B:

Function Codes (FC) .

C.

Polling Mode: This mode is used to perform the transmitting time. The next command will be sent immediately once receive the response. Click the “Start” button to activate Polling Mode and click the “Stop” button to cancel it.


62

Timer Mode: Enter a value that must elapse before a command is sent in the

"Interval" textbox and then click the "Set" button. Click the "Start" button to activate Timer Mode and click the "Stop" button to cancel it

D.

Command: This section is used to enter commands. Enter the command, including the 6-byte Modbus TCP prefix, and then click the “Send Command” button to transmit the command.

E.

Command/Response: Commands sent to the controller will be displayed in the left-hand text field, and the related response will be displayed on the right.

Use the following procedure to send a Modbus command.

Step 1: Click the "Modbus/TCP Client" option from the "Clients tools" menu.

Step 2: In the Modbus TCP section, enter the IP address and the Port number in the respective textboxes and then click the "Connect" button to establish a connection. If you also wish to create a data log, click the "Data Log" checkbox.

Step 3: In the Command section, enter a command and click the "Send Command" button to transmit the command.


63

Step 4: The command will be displayed on the left-hand side of the

Command/Response window, and the response will be shown on the right-hand side.

Commands Responses


64

3. Linking to SCADA Software via Modbus

This chapter provides a description of how to connect SCADA (Supervisor Control and Data Acquisition) applications to Modbus in order to retrieve I/O values via

Modbus/TCP protocol. The SCADA will be described in this chapter are:



Vijeo Citect



DASYLab



EZ Data Logger


65

3.1 Vijeo Citect

In this section, a detailed description of the procedure for connecting the Vijeo

Citect solution to controller via the Modbus/TCP protocol is presented. In this example Vijeo Citect version 7.40 is used.

3.1.1. Creating a New Project, an I/O Server and an I/O Device

Step 1: Open the Vijeo Citect Explorer Software from the Startup Menu.

Step 2: In the “Citect Explorer” window, click the “New” icon to create a new project.


66

Step 3: In the “New Project” dialog box, enter a name for this project. The name

“Modbus Demo” is used in this example. Leave all other parameters at their default values, and then click the “OK” button to continue.


67

Step 4: In the Project List panel, expand the “Modbus Demo” folder, and then double-click the “Express I/O Device Setup” icon in the “Communications” folder to create a new I/O Server and I/O Device.

Step 5: Once the “Express Communications Wizard” screen is displayed, click the

“Next >” button to continue.


68

Step 6: Click the “Create a new I/O Server” radio button, and enter

“ModbusServer” as the name of I/O Server in the Name field, and then click the “Next >” button to continue.

Step 7: Click the “Create a new I/O Device” radio button, and enter “Dev_8000” as the name of I/O Device in the Name field, and then click the “Next >” button to continue.


69

Step 8: Click the “External I/O Device” radio button to select the I/O Device type, and then click the “Next >” button to continue.

Step 9: Select the communication protocol by expanding the “Modicon” item, and then expand “Quantum” item and then click the “Modbus/TCP (Ethernet)” option. Click the “Next >” button to continue.


70

Step 10: Determine the IP address by checking the LED on the left-hand side of the controller, and enter it in the “IP address” field. In this example, the IP address

“192.168.2.199” is used. Enter the Port number, “502” in this example, in the

“Port” field and then click the “Next >” button to continue.

Step 11: There is no need to select any options on the following screen, so click the

“Next >” button to continue.


71

Step 12: Verify that the details for the new I/O Server are correct, and then click the "Finish" button to complete the configuration.

Step 13: Double-click the “I/O Servers” icon to open the “I/O Server [Modbus

Demo]” dialog box in the “Citect Project Editor” window.


72

Step 14: Roll the scroll to find the Server named “ModbusServer” that was created in previous step. Enter the port number “502” in the “Port” text field and then click the “Replace” button to complete the I/O Server configuration.


73

3.1.2. Designing the Layout and Acquiring the Data

Step 1: Switch the screen to the “Citect Project Editor” window, and then select the

“I/O Devices” option from the Communication menu in order to modify the

parameters for the I/O device that was created in Section 3.1.1

.

Step 2: Once the “I/O Device [Modbus Demo]” dialog box is displayed, roll the scroll

to find the device named “Dev_8000” that was created in Section 3.1.1

.

Determine the station number by checking the DIP switch on the right-hand side of the controller, and enter the value in the "Address" field. In this example, the station number "1" is used. To prevent the “Number” was the same with the exist Server Number, enter “2” in the “Number” field. When all settings are finished, click the "Replace" button to complete the configuration.


74

Step 3: Switch the screen to the “Citect Explorer” window, expand the “Modbus

Demo” folder in the Project List panel. Double-click the “Variable Tags” icon in the Tags folder to create a new variable tags.

Step 4: Switch the screen to the “Citect Project Editor” window, enter a name for the tag in the “Tag Name” field in the “Variable Tags [Modbus Demo]” dialog box. Then select the device from the “I/O Device” drop-down menu, enter the correct address in the "Address" field, and select the appropriate "Data Type" from the drop-down menu. After the details for the first tag have been entered, click the "Add" button to save it, and then repeat the procedure to create the next tag. The parameters for all tags used in this example are shown in the table below.

Tag Name I/O Device Name Data Type Address Eng Scale

DO_0

DI_0

AO_0

AI_0

Dev_8000

Dev_8000

Dev_8000

Dev_8000

DIGITAL 00001 X

DIGITAL 10001

INT 40001

X

0~10

INT 30001 0~10


75


76

Notes



When using the Modbus protocol, the Address Type must be set to “0xxxx” for

Digital Output, “1xxxx” for Digital Input, “3xxxx” for Analog Input, and “4xxxx” for Analog Output.



The Digital Input and Digital Output are declared as Boolean data, and the Analog

Input and Analog Output are declared as unsigned integer data.



The “Starting Address” begins at “0001”. Thus, to use the 5th Digital Output, the

“Address” filed must be se to “10005”, and the Data Type must be set to

“DIGITAL”. To use the 15th Analog Input, enter “30015” in the “Address” field, and set the Data Type to “INT”.

Step 5: Switch the screen to the “Citect Graphics Builder” window, click “New…” from the “File” menu to create a new page.


77

Step 6: In the "New" dialog box, click the "Page" button to create a new page using a pre-defined template.

Step 7: In the "Template" dialog box, click the "normal" option to select the template to be used for the page, and then click the "OK" button to continue.


78

Step 8: Click and hold the "New Button" icon and then drag-and-drop it onto the blank page to add a new button to the page.


79

Step 9: Once release the cursor, the “Button Properties” dialog box will be displayed.

Click the "Appearance" tab and click the "Text" radio button and enter "DO

Button" in the "Text" field. This will be the label displayed on the button. Click the "Input" tab and check the "Up" checkbox then enter "Toggle(DO_0)" in the

"UP Command" text field. Click the "OK" button to save the changes.


80

Step 10: Click and hold the "LED Object" icon and then drag-and-drop it onto the page to add a new LED object to the page.


81

Step 11: Once release the cursor, the “Symbol Set Properties” dialog box will be displayed. Click the "Appearance" tab and click the "On/Off" radio button in the

"Type" section, then enter "DO_0" in the "ON symbol when" text field. Click the

"OK" button to save the changes.


82

Step 12: Repeat Steps 10 and 11 to create a second LED object. Use the parameters shown in the image below for this LED object.

DI_0


83

Step 13: Click the "Text" icon and then move the cursor onto the page above the left-hand LED object, and enter “DO LED” to the text field.


84

Step 14: Once finishing entering the Text, click the text again and the “Text

Properties” dialog box will be displayed. Verify the words in the “Text” field, and then click the “OK” button to save the settings.

Step 15: Follow the Steps 13 and 14 to create three more Text objects and place them in the appropriate locations. Use the parameters shown in the image below for these Text objects.


85

Step 16: The layout of the page at this stage is shown in the image below. Click and hold the "Number" icon and then move it onto the page below the "AO Value" text object to create a new number object.


86

Step 17: Once release the cursor, the “Text Properties” dialog box will be displayed.

Click the "Appearance" tab, and click the "Numeric" radio button in the "Type" section, and then enter "AO_0" in the "Numeric expression" field, and set the

"Format" to "##.##". Click the "Input" tab and enter "#####ENTER" in the

"Key sequence" field box. Enter "AO_0=arg1;" in the "Command" field, and then click the "OK" button to save the changes.


87

Step 18: Repeat Step 16 to create another new number object and place it below the "AI Value" text object. When the "Text Properties" dialog box is opened for the new Number object, click the "Appearance" tab. Click the "Numeric" radio button in the "Type" section, then enter "AI_0" in the "Numeric expression" field, and set the "Format" to "##.##". In this case, there is no need to set the

Input parameters, so click the "OK" button to save the changes.

Step 19: The layout for the finished page is shown below. Click the "Save" button to save the page.


88

Step 20: In the "Page" field, enter "page1" as the name of the page and then click the “OK” button.

Step 21: Switch the screen to the “Citect Explorer” window, Click the "Computer

Setup Wizard" button to open the "Computer Setup Wizard".


89

Step 22: Click the "Express Setup" radio button and then click the "Next >" button to continue.

Step 23: Select "Modbus Demo" from the "Project Name" drop-down menu and then click the "Next >" button to continue.


90

Step 24: Click the "Server and Control Client" radio button, and click the "Next >" button to continue.

Step 25: Click the “Stand alone (no other SCADA computers)” radio button and click the “Next >” button to continue.


91

Step 26: Enter the password in the “Password” text field and “Confirm Password” field to set the password for the server, and click the “Next >” button to continue.

Step 27: Click the "Finish" button to complete the computer setup.


92

Step 28: Press F5 to execute the project. Verify that clicking the "DO Button" button or clicking the Analog Output "Number object" to enter a value will change the value for the Digital Output and the Analog Output.


93

3.2 DASYLab

In this section, a detailed description of the procedure for connecting the DASYLab solution to the I-8000-MTCP/ IP-8000-MTCP controller via the Modbus/TCP protocol is presented. In this example, DASYLab version 12 is used. This solution can also be used to request data from external devices such as the ET-7000,

I-7188-MTCP, or WISE-7000 using the Modbus protocol.

Before using DASYLab, the controller should be correctly configured using the

Modbus Utility. The Net ID is set using the DIP switch located on the right-hand side

of the controller (see Section 2.4 Net ID (Station number) Setting for more

information).

3.2.1. Adding an Analog Input Channel

Step 1: Open the DASYLab software.

Step 2: In the “Modules” folder, expand the “Inputs/Outputs” folder and then expand the “ModBus” folder. Drag a Modbus Analog Input module to the worksheet.


94

Step 3: Right-click the module icon and click the “Module Properties” option.


95

Step 4: Configure the module properties in the Modbus Analog Input dialog box.

A.

In the “Interfaces” section, set the Interface to TCP/IP and enter the IP address.

B.

In the “Device” section, set the Address, which is the Net ID of the controller.

C.

Check the “Register starts at 0: checkbox.

D.

Enter the register address, which can be found from the address mapping table in the Modbus Utility. Select 30 for Analog Input channels. In this demo, the register is set to 30000.

E.

Set the Data Type, which is a signed 16-bit integer in this demo.

F.

In the “Data range” section, enable Scaling by checking the “Scaling” checkbox, and set the minimum and maximum values, which are -10 to 10V in this demo.

A

C

B

E

D

F


96

Step 5: Click the “Test” button to verify the settings and then click the “OK” button to save the configuration. The data can also be checked on the “AI Mapping” using the Modbus Utility.


97

Step 6: In the “Modules” folder, expand the “Display” folder. Drag an Analog Meter or a List to the worksheet. Click the “run” triangle button to connect to the module and acquire data.

Analog Meter

List


98

3.2.2. Adding an Analog Output Channel

Step 1: In the “Modules” folder, expand the “Inputs/Outputs” folder and then expand the “ModBus” folder. Drag a Modbus Analog Output module to the worksheet.



99

Step 3: Configure the module properties in the Modbus Analog Output dialog box.

A.

In the “Interfaces” section, set the Interface to TCP/IP and enter the IP address.

B.

In the “Device” section, set the Address, which is the Net ID of the controller.

C.

Check the “Register starts at 0: checkbox.

D.

Enter the register address, which can be found from the address mapping table in the Modbus Utility.

E.

Set the Data Type, which is a Word unsigned 16-bit integer in this demo.

F.

In the “Data range” section, enable Scaling by checking the “Scaling” checkbox, and set the minimum and maximum values, which are -10 to 10V in this demo.

A

C

B

E

D

F


100

Step 4: In the “Modules” folder, expand the “Control” folder and then drag a Slider

Control to the worksheet.

Step 5: Right-click the Slider Control icon and click the “Module Properties” option.


101

Step 6: Click the “Scale” button and set the Begin and End values in the “Display area” section. In this demo, -10 to +10 are used. Click the “OK” button to continue.


102

Step 7: Drag a line from the “Slider00” icon to the “ModBus Ana00” icon to establish a connection between the Slider Control and the Analog Output module. Click the “run” triangle button to start exporting value by dragging the

Slider Control. The value can also be using the Modbus Utility.


103

3.2.3. Adding a Digital Input Channel

Step 1: In the “Modules” folder, expand the “Inputs/Outputs” folder and then expand the “ModBus” folder. Drag a Modbus Digital Input module to the worksheet.



104

Step 3: Configure the module properties in the Modbus Digital Input dialog box.

A.

In the “Device settings” section, set the Interface to TCP/IP and enter the IP address.

B.

In the “Device settings” section, set the Address, which is the Net ID of the controller.

C.

Enter the Start byte, which can be found from the address mapping in the

Modbus Utility.

A

B C


105

Step 4: In the “Modules” folder, expand the “Display” folder and then drag a Status

Display object to the worksheet.


106

Step 5: Drag a line from the “Status Dis00” icon to the ”Modbus Dig00” icon to establish a connection between the Status Display object and the Digital Input module. Click the “run” triangle button to start acquiring data. The data can also be checked on the “DI Mapping” using the Modbus Utility.


107

3.2.4. Adding a Digital Output Channel

Step 1: In the “Modules” folder, expand the “Inputs/Outputs” folder and then expand the “ModBus” folder. Drag a Modbus Digital Output module to the worksheet.



108

Step 3: Configure the module properties in the Modbus Digital- Output dialog box.

A.

In the “Device settings” section, set the Interface to TCP/IP and enter the IP address.

B.

In the “Device settings” section, set the Address, which is the Net ID of the controller.

C.

Enter the Start byte, which can be found from the address mapping in the

Modbus Utility.

A

B C


109

Step 4: In the “Modules” folder, expand the “Control” folder and then drag a Switch

Control to the worksheet.


110

Step 5: Drag a line from the “Switch00” icon to the “Modbus Dig00” icon to establish a connection between the Switch Control and the Digital Output module. Click the “run” triangle button to exporting value by clicking the

Switch00. The value can also be set on the “DO Mapping” using the Modbus

Utility.


111

3.3 EZ Data Logger

In this section, a detailed description of the procedure for connecting the EZ Data

Logger solution to the controllers via the Modbus/TCP protocol is presented. In this example, EZ Data Logger version 4.5.7 is used.

Before you using the EZ Data Logger, the controller should be correctly configured using the Modbus Utility. The Net ID is set using the 8-bit DIP switch located on the

right-hand side of the controller (see Section 2.4 Net ID (Station number) Setting for

more information).

The EZ Data Logger can be downloaded from the following website: http://ftp.icpdas.com/pub/cd/8000cd/napdos/driver/ez_data_logger/

3.3.1. Adding the I/O Modules to the Workgroup

Step 1: Open the EZ Data Logger software and the main page will be displayed. The

EZ Data Logger will load a default project named “MyProject”.


112

To create a new project, click “New Project” in the “Project” menu.

Step 2: Enter a name for the project and click the “Save” button.


113

Step 3: Click the “Group Setup” button on the main toolbar to open the

“Workgroup Setting” dialog box, and begin to add the controller and the I/O channels to the workgroup list.


114

Step 4: Click the “Install” button in the “Driver List” numbered 1section to display the “Driver” dialog box.


115

Step 5: Select “Modbus TCP” from the “Driver Mode” drop-down menu, and enter the controller IP address in the “Host” text field and then click the “Install”.

The new driver will be added to the Driver List, as shown below.


116

Step 6: Click the “+Device” button in the “Driver” dialog box to display the “Device” dialog box.


117

Step 7: In the “Select Driver” drop-down menu, select the “MTCP” driver that was added earlier and select “Enter numbers by yourself” from the “Module” drop-down menu.

Enter the name of the AI module, 87017W in this example, in the “Nickname” text field of Nickname and set the “Slave ID” to “1”.

Check the “AI” checkbox and enter the channel numbers 0 to 7 then select

“Integer” as the type.

Click the “Add” button to add the new module configuration to the Device List section and Channel List section.

Once the new device has been configured, the new channels will be displayed in the

“Channel List” section, as shown in the following figure.


118

Step 8: As the “Device” dialog box remaining on the screen, using the images below as a guide, repeat the procedure described in Step 6 to add the details for AO, DI and DO to the Channel List.


119

Step 9: The output style and alarm for an AI channel can be edited by double-clicking the name of the channel in the Channel List to open the

“Modify Channel” dialog box. The example illustrated below uses AI channel 0.

AO, DI and DO channel can be edited in the same way.

C

B

A

D

Configure the channel properties in the “Modify Channel” dialog box.

A.

Set the Gain and Offset values by entering the AI value in the “Scaling” section.

B.

In the “Alarm” section, set the high and low alarm values to notify of any abnormal events if the “MailNotifier” driver was set earlier. The procedures to set “MailNotifier” can be gotten from below download link: http://ftp.icpdas.com/pub/cd/8000cd/napdos/driver/ez_data_logger/faq_en/ ezdl1-003-03_how_to_set_alarm_notifies_by_sending_email_en.pdf

C.

In the “Component Style” section, select the desired style for AI channel 0.

D.

Click the “Modify” button to save the configurations.


120

Step 10: Click” Workgroup1” to be a selected status from the “Work Group” section, and the I/O channels will be added to the channel list of the “Workgroup1” in the later procedures.

Step 11: Click the “AI List” button in the “Channel List” section to display the AI channels that configured earlier. Select all AI channels and click the “Add>>” button.


121

After clicking the “Add>>” button, the selected channels will be added to the channel list panel of the Workgroup1, as shown in the following figure. These channels will be used for monitoring purpose later.

The AI Channels that were added earlier in the Workgroup1.


122

Step 12: Repeat the procedure described in Step 10 to add the other I/O channels to the channel list of Workgroup1. After all channels have been added, click the

“Home” button to return to the main page.


123

3.3.2. Designing the Layout and Acquiring the Data

After setting up in the section3.3.1, the layout can be designed and the data can be acquired in the main page.

Step 1: The layout style can be adjusted in the “Workgroup1 Ver 4.5.7” dialog box by clicking “Layout” button on “Workgroup1” in the main page.


124

Step 2: The interface can be arranged by dragging the relevant I/O objects, adding a background by clicking the “Back Picture” from the “Picture” menu, or changing the font color by clicking the “Font Color” menu.


125

Step 3: After the interface design is complete, click the “Hide” button in the menu to close the dialog box.

Step 4: Click the “Start” button on the main toolbar to begin connecting to the controller and acquiring the values. If the connection has been correctly established, the device state indicators will be switched to ON and the connected messages will be printed in the yellow text filed.


126

Step 5: To acquire the I/O values, the “Gauge” button, the” Trend” button or the”

Layout” button can be clicked. The “Layout” button is clicked in the following figures. The”Workgroup1 Ver 4.5.7” dialog box will be displayed, and the values from the relevant modules also be displayed in the dialog box.


127

Appendix A: Backing Up and

Recovering the EEPROM Settings

The EERPOM is a memory component that is used to store network, system, COM port and module configuration information .The Back Up/Recover functions are used to duplicate EEPROM data from one controller to another.

The size of the EEPROM is different in every controller and each block in the

EEPROM stores different types of data. The following table givens an overview of the writable blocks and the reserved blocks. The writable blocks include library version, COM port configuration, watchdog timer, module settings, and the reserved blocks include IP address, Mask, Gateway and MAC address.

Controller Writable Block Reserved Block Number of Blocks

I-8000 1-7 0 8 (blocks 0-7)

IP-8000

7188E

8-14

1-7

0-7

0

64 (blocks 0-63)

8 (blocks 0-7)

Note 1: Before attempting to read or write EEPROM data, ensure that the I/O Scan

Library is version 1.6.0 or later.

Note 2: This function only supports connections via the COM port. Before attempting to perform this function, ensure that controller’s COM1 is connected to the computer.


128

1. Backing up the Settings



For IP-8000 modules, move the DIP switch to the “Init” position.





129

Select the COM port from the drop-down menu and then click the “Connect” button.

Once a connection is established, the “Back up Settings” and “Recover Settings” buttons will be displayed.

Step 4: Click the “Back up Settings” button and the “Back up EEPROM file” dialog box will be displayed. Click the "Save" button to save the current configuration of the controller to the default root folder named “backup_setting”. A status message "Downloading. Please Wait..." will be displayed while the file is saved.


130

Once the download is complete, a message will be displayed to notify that the file was saved successfully. Click the "OK" button to continue.


131

2. Recovering the Settings



For IP-8000 modules, move the DIP switch to the “Init” position.





132

Select the COM port from the drop-down menu and then click the “Connect” button.

Once a connection is established, the “Back up Settings” and “Recover Settings” buttons will be displayed.

Step 4: To configure a controller to the same settings as another, click the “Recover

Settings” button and the "Select an EEPROM file to write" dialog box will be displayed. Click the name of the file that contains the configuration to be uploaded, and then select the blocks to be duplicated from the "Write Block" drop-down menus, then click the "Write 1/multi-block" button.


133

A status message "Writing. Please Wait..." will be displayed while the configuration is duplicated.

Once the duplication process is complete, a message will be displayed to notify that the file was written successfully. Click the "OK" button to continue.


134

Appendix B: Function Codes (FC)

All data addresses in a Modbus message start at zero and are transmitted in

hexadecimal format. For example:

A.

Input register 30001 is addressed as 0 in the data address field of the Modbus message.

B.

Coil 24 (decimal) in an I/O module is addressed as coil 0017 (hexadecimal) in the Modbus message (Equivalent to 23 in decimal.).

As the function code already specifies whether the operation is DO, DI, AO or AI, the references ‘0xxxx, 1xxxx, 4xxxx, 3xxxx’ are implicit. Function codes are used in both the Modbus RTU Master Tool and the Modbus TCP Client Tool.


135

1. Read DO (0xxxx)

Function Code 01=Read Coil Status

Byte

Request

0 1 2 3 4 5

Net ID FC=01 Starting Address Bit Count

11 0 D Example: Net ID = 20

Read coils 18-30

Byte

(*2)

0

(*1)

, Hex

1

14

2

Net ID FC=01 Byte Count

1 0

Command 14 1 0 11 0 D

Response

3 ~Byte Count+2

Bits Value

Response

Binary

14 01 2

(*3)

5C (coils 25-18) 1B (coils 30-26)

0101 1100

(*4)

0001 1011

(*5)

*1: Net ID decimal 20 = hexadecimal 14.

*2: Coils 18-30 are addressed as 17-29 (decimal), with a total of 13 coils.

*3: If the number of coils returned isn’t a multiple of 8, the remaining bits in the last byte will be filled with 0.

*4: 5C= 0101 1100 refers to coils 18 to 25 (from right to left). The status values are:

OFF (25), ON (24), OFF (23), ON (22), ON (21), ON (20), OFF (19), OFF (18).

*5: 1B= 0001 1011, refers to coils 26 to 30 (from right to left). The status values are:

ON (30), ON (29), OFF (28), ON (27), ON (26).


136

2. Read DI (1xxxx)

Function Code 02=Read Input Status

Byte

Request

0 1 2 3 4 5

Net ID FC=02 Starting Address Bit Count

0 0 0 8 Example: Net ID = 1, Read the input status 1-8

Byte

(*1)

0

Hex

1

1

2


2

Command 1 2 0 0 0 8

Response

3 ~Byte Count+2

Bits Value

Response

Binary

1 2 1 FF (coils 8-1)

1111 1111

(*2)

*1: Inputs 1-8 are addressed as 0-7 (decimal), there are a total of 8 inputs.

*2: FF=1111 1111, refers to coils 8 to 1 (from right to left), and the status of each coil is set ON.


137

3. Read AO (4xxxx)

Function Code 03=Read Holding Registers

Byte

Example: Net ID = 25,

Read registers

40027-40028

(*1)

Byte

Response

Register

Hex

0

Request

1 2

Net ID FC=03 Starting Address Word Count

19

Command

3 0

19 3 0 1A 0 2

0 1

Response

2


19 3 4 2

3

4

~Byte Count+2

Register Values

17

40027

(*2)

3

1A

0

0

40028

C8

(*2)

5

2

*1: Holding registers 40027-40028 are addressed as 26-27 in Modbus.

*2: The value of register 40027 is shown as a 2-byte value: 02 17 (hexadecimal) =

535 (decimal), the value of register 40028 is 00 C8 (hexadecimal) = 200 (decimal).

To convert value to float format, see Appendix D: Range Codes for Analog

Modules .


138

4. Read AI (3xxxx)

Function Code 04=Read Input Registers

Byte

Example: Net ID = 2,

Read registers

30001-30002

(*1)

Hex

3 4

Net ID FC=04 Starting Address Word Count

Command

0

2

Request

1

4

2 4 0 0 0 2

Byte

Response

Register

0 1

Response

2


2 4 4

2

0

3

0 0

~Byte Count+2

Register Values

0 0

30001

(*2)

0

30002

64

(*2)

5

2

*1: Input registers 30001-30002 are addressed as 0-1 in Modbus.

*2: The value of register 30001 is shown as a 2-byte value: 00 00 (hexadecimal) = 0

(decimal), the value of register 30002 is 00 64 (hexadecimal) = 100 (decimal).

To convert value to float format, see Appendix D: Range Codes for Analog

Modules .


139

5. Write Single DO (0xxxx)

Function Code 05=Write Single Coil

Byte 0

Request

1 2 3

Net ID FC=05 Write Address

4 5

FF 00=ON,

00 00=OFF

FF 0 Example: Net ID = 1, set coil 5 to ON

(*1)

Hex 1 5 0

Command 1 5 0 4 FF 0

Response

4

Byte 0 1

Net ID FC=05

2 3

Write Address

4 5

FF 00=ON, 00 00=OFF

Response 1 5 0 4 FF 0

If the request is successful, the function will return an echo of the request.

*1: Coil 5 is addressed as 4.

A value of FF 00 sets the coil to ON, and a value of 00 00 sets it to OFF. All other values are treated as an invalid command.


140

6. Write Single AO (4xxxx)

Function Code 06= Write Single Register

Byte

Example: Net ID =

1, set register

40003

(*1)

to 155

(*2)

Hex

0

Command

Request

1

1 6 0 2 0 9B

2 3 4 5

Net ID FC=06 Write Address Register Value

1 6 0 2 0 9B

Byte 0 1

Net ID FC=06

Response

2 3

Write Address

4 5

Register Value

Response 1 6 0 4 0 9B

If the request is successful, the function will return an echo of the request.

*1: Register 40003 is addressed as 2 in Modbus.

*2: Register value 155 = 9B (hexadecimal).


141

7. Write DO (0xxxx)

Function Code 15=Write Multiple Coils

Byte

Hex

0 1 2 3

Request

4 5 6 7 ~Byte Count+6

Net ID FC=15 Write Address Bit Count Byte Count Data to be Written

1 F

Example: Net ID = 1, write coils 1 to 12

(*1)

0 0 0 C 2 FE

(*2)

1111

1110

05

(*2)

0000

0101

Command

Byte

Response

0

1 F 0 0 0 C 2 FE 5

Net ID FC=15

1

1

F

Response

2 3

Write Address

0 0

4

0

Bit Count

5

C

*1: Coils 1-12 are addressed as 0-11, there are a total of 12(hexadecimal 0C) coils.

*2: The data is 2-byte value. FE 05 (hexadecimal) = 1111 1110 0000 0101 (binary)

Bit 1 1 1 1 1 1 1 0 0 0 0 0 0 1 0 1

Coil 8 7 6 5 4 3 2 1 - - - - 12 11 10 9


142

8. Write AO (4xxxx)

Function Code 16= Write Multiple Registers

Byte 0 1 2 3

Request

4 5 6 7 ~Byte Count+6

Net ID FC=16 Write Address Word Count Byte Count Register Values

Hex 1 10 0

Example: Net ID = 1, write register 40001-40002

(*1)

0 0 2 4 0 19 0 64

Command 1 10 0 0 0 2 4 0 19 0 64

Byte 0 1

Net ID FC=16

Response

2 3

Write Address

4

Word Count

5

Response 1 10 0 0 0 2

*1: Register 40001-40002 are addressed as 0-1 in Modbus.

The register values are 40001:25 (hexadecimal 19), 40002:100 (hexadecimal

64).


143

Appendix C: Supported Modules

For details of which I/O modules are supported by the different controllers, go to http://ftp.icpdas.com/pub/cd/8000cd/napdos/modbus/8000e/document/mbt8_s upport_modules.htm


144

Appendix D: Range Codes for

Analog Modules

The Modbus Utility can be used to convert the input or output value to float format

or other formats. The operation can see Step 3 of 2.14Monitoring

.

The formula shown below provides details of the conversion process.

𝒴

Max

Max. Input/Output Range

(Data

𝒳

, FValue

𝒴

)

𝒳

Min. Value

(-32768)

Offset

(0, 0)

𝒳

Max. Value

(+32767)

𝒴

Min

Min. Input/Output Range

Float Value 𝒴 = (Gain * Data 𝒳) + Offset

Gain = the Slope for this Range Code type.

Data = the input or output value.

Offset = the offset value to compensate for an inaccuracy in the module.

The following tables provide the maximum and minimum values, Gain, and Offset for each range code type.



87K Analog Modules



Current and Voltage Type Definitions



Thermocouple Type Definitions



RTD (Resistance Temperature Detector) Type Definitions



Thermistor Type Definitions



8K Modules


145

1. 87K Analog Modules

1.1. Current and Voltage Type Definitions

Type Type

Code Definitions

Data Format Max. Value Min. Value Gain Offset

00

-15 mV to

+15 mV

01

-50 mV to

+50 mV

02

-100 mV to

+100 mV

03

-500 mV to

+500 mV

04 -1 V to +1V

05

-2.5 V to

+2.5 V

06

*1

-20 mA to

+20 mA


146

Type Type

Code Definitions

(With 125 ohms resistor)

Data Format

2's Complement

Hexadecimal Units

07

*2

08

09

0A -1 V to +1V

0B

0C

0D

*3

+4 mA to

+20 mA

-10 V to

+10 V

-5 V to

+5 V

-500 mV to

+500 mV

-150 mV to

+150 mV

-20 mA to

+20 mA

(with 125 ohms resistor)

Input Range

Decimal Units

2's Complement

Hexadecimal Units

Input Range

Decimal Units

2's Complement

Hexadecimal Units

Input Range

Decimal Units

2's Complement

Hexadecimal Units

Input Range

Decimal Units

2's Complement

Hexadecimal Units

Input Range

Decimal Units

2's Complement

Hexadecimal Units

Input Range

Decimal Units

2's Complement

Hexadecimal Units

Input Range

Decimal Units

2's Complement

Hexadecimal Units

Max. Value Min. Value

7FFF 8000

Gain Offset

+20.0 mA +4.0 mA 0.000488296 +4

+65535

FFFF

+10.0 V

+32767

7FFF

+5.0 V

+32767

7FFF

+1.0 V

+32767

7FFF

+500.0 mV -500.0 mV 0.015259022 0

+32767 -32768

7FFF

+150.0 mV -150.0 mV 0.004577706 0

+32767 -32768

7FFF

+0

0000

-10.0 V 0.00030518

-32768

8000

-5.0 V

-32768

8000

0.00015259

0

0

-1.0 V 0.000030518 0

-32768

8000

8000

8000

+20.0 mA -20.0 mA 0.00061036

+32767

7FFF

-32768

8000

0


147

Type Type

Code Definitions

1A

*2

1B

1C


+0 mA to

+20 mA

-150 V to

+150 V

Input Range

Decimal Units

2's Complement

Hexadecimal Units

Input Range

Decimal Units

2's Complement

Hexadecimal Units

+20.0 mA +0.0 mA 0.00030518

+65535

FFFF

+0

0000

+150.0 V -150.0 V 0.0045777

+32767

7FFF

-32768

8000

0

0

-50 V to

+50 V

Input Range

Decimal Units

2's Complement

Hexadecimal Units

+50.0 V -50.0 V 0.0015259 0

+32767

7FFF

-32768

8000

Digital Input/Output, Counter, Frequency, Encoder Modules

40

50

51

54

Digital

Input/

Output

Counter

Mode

Frequency

Mode

Up/Down

Counter

Mode

55 Pulse Mode

56

AB Phase

Mode

N/A

N/A

N/A

N/A

N/A

N/A

N/A

N/A

N/A

N/A

N/A

N/A

N/A

N/A

N/A

N/A

N/A

N/A

N/A

N/A

N/A

N/A

N/A

N/A

N/A

N/A

N/A

N/A

N/A

N/A

0, 30

+0 mA to

+20 mA

Analog Output Modules

Output Range

Decimal Units

2's Complement

Hexadecimal Units

+20.0 mA +0.0 mA 0.00061037 0

+32767 +0

7FFF 0000


148

Type Type

Code Definitions


1, 31

2, 32

3, 33

4, 34

5, 35

6, 36

+4 mA to

+20 mA

+0 V to

+10 V

-10 V to

+10 V

+0 V to

+5 V

-5 V to

+5 V

+0 V to

+20 V

Output Range

Decimal Units

2's Complement

Hexadecimal Units

Gain

-1

= 1638.35

+20.0 mA +4.0 mA 0.000488296 +4

+32767 +0

7FFF 0000

Output Range

Decimal Units

2's Complement

Hexadecimal Units

Gain

-1

= 2047.9375

+10.0 V +0.0 V 0.000305185 0

+32767 +0

7FFF 0000

Output Range

Decimal Units

2's Complement

Hexadecimal Units

Gain

-1

= 3276.7

+10.0 V -10.0 V 0.00030518 0

+32767 -32768

7FFF 8000

Output Range

Decimal Units

2's Complement

Hexadecimal Units

Gain

-1

= 3276.75

+5.0 V +0.0 V 0.00015259 0

+32767 0

7FFF 0000

Output Range

Decimal Units

2's Complement

Hexadecimal Units

Gain

-1

= 6553.4

+5.0 V -5.0 V 0.00015259 0

+32767 -32768

7FFF 8000

Output Range

Decimal Units

2's Complement

Hexadecimal Units

Gain

-1

= 6553.4

+20.0 V +0.0 V 0.00061037 0

+32767 0

7FFF 0000


149

Type Type

Code Definitions


Gain

-1

= 1638.35

Notes

*1: When I-87018 and I-87018R are connecting to a current source set to the 06 type code, an optional external 125 Ohms resistor is required.

*2: I-87017RC has built-in 125 Ohms resistors for each channel. When connecting to a current source, no add any external resistors required.

*3: When I-87017 and I-87017R are connecting to a current source set to 0D type code, an optional external 125 Ohms resistor is required. On the other hand,

I-87017RC has built-in 125 Ohms resistors for each channel, so require no external resistors.


150

1.2. Thermocouple Type Definitions

Type

Code

Thermocouple

Type

0E

0F

10

J Type

K Type

T Type

Data Format

Max.

Value

Min.

Value

Gain Offset

Input Range

(Celsius)

+760.0 -210.0 0.023194089

Decimal Units +32767 -9054

0

2's Complement

Hexadecimal Units

Input Range

(Celsius)

7FFF DCA2

+1372.0 -270.0 0.0418717327 0

Engineer Unit +32767 -6448

2's Complement

HEX

Input Range

(Celsius)

7FFF E6D0

+400.0 -270.0 0.0122073426 0


11

12

13

E Type

R Type

S Type

2's Complement

Hexadecimal Units

Input Range

(Celsius)

7FFF A99A

+1000.0 -270.0 0.030518575


0

2's Complement

Hexadecimal Units

Input Range

(Celsius)

7FFF DD71

+1768.0 +0.0 0.0539567247 0

Decimal Units +32767 +0

2's Complement

Hexadecimal Units

Input Range

(Celsius)

7FFF 0000

+1768.0 +0.0 0.0539567247 0


2's Complement

Hexadecimal Units

7FFF 0000


151

Type

Code

Thermocouple

Type

14

15

16

B Type

N Type

C Type

Data Format

Max.

Value

Min.

Value

Gain Offset

Input Range

(Celsius)

+1820.0 +0.0 0.0555436872 0


2's Complement

Hexadecimal Units

Input Range

(Celsius)

7FFF 0000

+1300.0 -270.0 0.0396745173 0


2's Complement

Hexadecimal Units

Input Range

(Celsius)

7FFF E56B

+2320.0 +0.0 0.0708029419 0


17

18

19

L Type

M Type

L Type

DIN43710

2's Complement

Hexadecimal Units

Input Range

(Celsius)

7FFF 0000

+800.0 -200.0 0.0244146585 0


2's Complement

Hexadecimal Units

Input Range

(Celsius)

7FFF E000

+100.0 -200.0 0.0061035156 0


2's Complement

Hexadecimal Units

Input Range

(Celsius)

4000 8000

+900.0 -200.0 0.0274670395 0


2's Complement

Hexadecimal Units

7FFF E38F


152

1.3. RTD (Resistance Temperature Detector) Type Definitions

Type

Code

RTD Type

20

21

22

23

24

Platinum

100 a =

0.00385

-100℃ to

100℃

Platinum

100 a =

0.00385

0℃ to

100℃

Platinum

100 a =

0.00385

0℃ to

200℃

Platinum

100 a =

0.00385

0℃ to

600℃

Platinum

100 a =

0.003916

-100℃ to

100℃

Data Format

Max.

Value

Min.

Value

Gain

Input Range

(Celsius)

+100.0 -100.0 0.0030518043


2's Complement

Hexadecimal Units

Ohm

7FFF 8000

+138.5 +60.25

Input Range

(Celsius)

+100.0 +0.0 0.0030518509


2's Complement

Hexadecimal Units

Ohm

7FFF 0000

+138.5 +100.0

Input Range

(Celsius)

+200.0 +0.0 0.0061037018


2's Complement

Hexadecimal Units

Ohm

7FFF 0000

+175.84 +100.0

Input Range

(Celsius)

+600.0 +0.0 0.0183111056


2's Complement

Hexadecimal Units

Ohm

7FFF 0000

+313.59 +100.0

Input Range

(Celsius)

+100.0 -100.0 0.0030518043


2's Complement

Hexadecimal Units

Ohm

7FFF 8000

+139.16 +59.58

Offset

0

0

0

0

0


153

Type

Code

25

26

27

28

29

RTD Type

Platinum

100 a =

0.003916

0℃ to

100℃

Platinum

100 a =

0.003916

0℃ to

200℃

Platinum

100 a =

0.003916

0℃ to

600℃

Nickel 120

-80℃ to

100℃

Nickel 120

0℃ to

100℃

2A Platinum

Data Format

Max.

Value

Min.

Value

Gain

Input Range

(Celsius)

+100.0 +0.0 0.0030518509


2's Complement

Hexadecimal Units

Ohm

7FFF 0000

+139.16 +100.0

Input Range

(Celsius)

+200.0 +0.0 0.0061037018


Offset

0

0

2's Complement

Hexadecimal Units

Ohm

7FFF 0000

+177.13 +100.0

Input Range

(Celsius)

+600.0 +0.0 0.01831110568


0

2's Complement

Hexadecimal Units

Ohm

7FFF 0000

+317.28 +100.0

Input Range

(Celsius)

+100.0 -80.0 0.0030518302


2's Complement

Hexadecimal Units

Ohm

7FFF 999A

+200.64 +120.6

Input Range

(Celsius)

+100.0 +0.0 0.0030518509


2's Complement

Hexadecimal Units

Ohm

Input Range

7FFF 0000

+200.64 +120.6

+600.0 -200.0 0.0183112453

0

0

0


154

Type

Code

2B

2C

2D

2E

2F

*1

*1

*1

*2

*2

RTD Type

1000 a

=0.00385

-200℃ to

600℃

Cu 100 a

=0.00421

-20℃ to

150℃

Cu 100 a

=0.00421

0℃ to

200℃

Cu 1000 a

=0.00421

-20℃ to

150℃

Pt 100 a

=0.00385

-200℃ to

200℃

Pt 100 a

Data Format

Max.

Value

Min.

Value

(Celsius)


Gain

2's Complement

Hexadecimal Units

Ohm

7FFF D556

+3137.1 +185.2

Input Range

(Celsius)

+150.0 -20.0


0.0045777

2's Complement

Hexadecimal Units

Ohm

7FFF EEEF

+163.17 +91.56

Input Range

(Celsius)

+200.0 +0.0


0.0061037

2's Complement

Hexadecimal Units

Ohm

7FFF 0000

+167.75 +90.34

Input Range

(Celsius)

+150.0 -20.0


0.0045777

2's Complement

Hexadecimal Units

Ohm

7FFF EEEF

+1631.7 +915.6

Input Range

(Celsius)

+200.0 -200.0


0.0061036

2's Complement

Hexadecimal Units

Ohm

Input Range

(Celsius)

7FFF 8000

+175.84 +18.49

+200.0 -200.0 0.0061036

Offset

0

0

0

0

0


155

Type

Code

80

*2

RTD Type

=0.003916

-200℃ to

200℃

Pt 100 a

=0.00385

-200℃ to

600℃

81

*2

Pt 100 a

=0.003916

-200℃ to

600℃

Data Format

Max.

Value

Min.

Value


2's Complement

Hexadecimal Units

Ohm

7FFF 8000

+177.14 +17.14

Gain

Input Range

(Celsius)

+600.0 -200.0


0.018311

2's Complement

Hexadecimal Units

Ohm

7FFF D556

+313.59 +18.49

Input Range

(Celsius)

+600.0 -200.0


0.018311

2's Complement

Hexadecimal Units

Ohm

7FFF D556

+317.28 +17.14

Notes

Offset

0

0

*1: Type code 2B, 2C and 2D are only available with I-87015.

*2: Type code 2E, 2F, 80 and 81 are only available with the I-87015 firmware version A1.10 and later, I-87013 firmware version B1.3 and later.


156

1.4. Thermistor Type Definitions

Type

Code

Thermistor

Type

60

Data Format

Precon

ST-A3

-30 to 240 degree

Fahrenheit

Input Range

(Fahrenheit)

Decimal Units

2's Complement

Hexadecimal Units

Ohm


+240.0

+32767

7FFF

-30.0

-4096

F000

+539.4 +173600.0

61

Type U

Fenwell

-50 to 150 degree

Celsius

Input Range

(Celsius)

Decimal Units

2's Complement

Hexadecimal Units

Ohm

+150.0

+32767

7FFF

+37.2

-50.0

-10922

D556

+134020.0

62

63

64

Type U

Fenwell

0 to 150 degree

Celsius

YSI L Mix

100

YSI L Mix

300

Input Range

(Celsius)

Decimal Units

2's Complement

Hexadecimal Units

Ohm

Input Range

(Celsius)

Decimal Units

2's Complement

Hexadecimal Units

Ohm

Input Range

Decimal Units

2's Complement

Hexadecimal Units

Ohm

+150.0

+32767

7FFF

+37.2

+100.0

+32767

7FFF

+14.3

+100.0

+32767

7FFF

+35.8

+0.0

+0

0000

+6530.0

-80.0

-26214

999A

+14470.0

-80.0

-26214

999A

+67660.0

Gain

0.0073244

0.004577

0.004577

0.0030518

0.0030518

Offset

0

0

0

0

0


157

Type

Code

Thermistor

Type

65

66

67

68

69

YSI L Mix

1000

YSI B Mix

2252

YSI B Mix

3000

YSI B Mix

5000

YSI B Mix

6000

6A YSI B Mix

Data Format

Input Range

(Celsius)

Decimal Units

2's Complement

Hexadecimal Units

Ohm

Input Range

(Celsius)

Decimal Units

2's Complement

Hexadecimal Units

Ohm

Input Range

(Celsius)

Decimal Units

2's Complement

Hexadecimal Units

Ohm

Input Range

(Celsius)

Decimal Units

2's Complement

Hexadecimal Units

Ohm

Input Range

(Celsius)

Decimal Units

2's Complement

Hexadecimal Units

Ohm

Input Range


+100.0

+32767

7FFF

-70.0

-22937

A667

+106.4 +132600.0

+150.0

+32767

7FFF

+41.8

+150.0

+32767

7FFF

+55.6

+150.0

+32767

7FFF

+92.7

+150.0

+32767

7FFF

-50.0

-10922

D556

+151000.0

-40.0

-8738

DDDE

+101000.0

-40.0

-8738

DDDE

+168300.0

-30.0

-6553

E667

+111.5 +106200.0

+150.0 -30.0

Gain

0.004577

0.004577

0.00305

0.004577

0.004577

0.004577

Offset

0

0

0

0

0

0


158

Type

Code

Thermistor

Type

10K

Data Format

(Celsius)

Decimal Units

2's Complement

Hexadecimal Units

Ohm


+32767

7FFF

-6553

E667

+185.9 +177000.0

6B

YSI H Mix

10K

Input Range

(Celsius)

Decimal Units

2's Complement

Hexadecimal Units

Ohm

+150.0

+32767

7FFF

-30.0

-6553

E667

+237.0 +135200.0

6C

70-

77

YSI H Mix

30K

User- defined

-50 to 150 degree

Celsius

Input Range

(Celsius)

Decimal Units

2's Complement

Hexadecimal Units

Ohm

Input Range

(Celsius)

Decimal Units

2's Complement

Hexadecimal Units

Ohm

+200.0

+32767

7FFF

-10.0

-1638

F99A

+186.7 +158000.0

+150.0

+32767

7FFF

+0.0

-50.0

-10922

D556

+0.0

Gain

0.004577

0.004577

0.0061037

Offset

0

0

0


159

2. 8K Modules

Type

Code

Type

Definitions

Data Format

05

06

07

08

30

-2.5 V to

+2.5 V

-20 mV to

+20 mV

-1.25 V to

+1.25 V

-10 V to

+10 V

09 -5 V to +5 V

+0 mA to

+20 mA

Input Range

Decimal Units

2's Complement

Hexadecimal Units

Input Range

Decimal Units

2's Complement

Hexadecimal Units

Input Range

Decimal Units

2's Complement

Hexadecimal Units

Input Range

Decimal Units

2's Complement

Hexadecimal Units

Input Range

Decimal Units

2's Complement

Hexadecimal Units

Output Range

Decimal Units

2's Complement

Hexadecimal Units


+2.5 V

+32767

7FFF

+32767

7FFF

+1.25 V

+32767

7FFF

+10.0 V

+32767

7FFF

+5.0 V

+32767

7FFF

7FFF

Offset

-2.5 V 0.000076295 0

-32768

8000

+20.0 mV -20.0 mV 0.00061036

-32768

8000

0

-1.25 V 0.000038147 0

-32768

8000

-10.0 V 0.00030518

-32768

8000

-5.0 V

-32768

8000

Gain

0.00015259

+20.0 mA +0.0 mA 0.00061037

+32767 +0

0000

0

0

0

33

-10 V to

+10 V

Output Range

Decimal Units

2's Complement

Gain

-1

= 1638.35

+10.0 V -10.0 V 0.00030518 0

+32767 -32768

7FFF 8000


160

Type

Code

Type

Definitions

80

Data Format Max. Value Min. Value

Mode 0:

Pulse/

Direction

Counter

Mode 1:

Up/Down

Counter

Mode 2:

Frequency

Mode 3: Up

Counter

Hexadecimal Units

Decimal Units

Decimal Units

Gain

-1

= 3276.75

+2147483

647

-2147483

648

2's Complement

Hexadecimal Units

7FFFFFFF 80000000

+2147483

647

-2147483

648

2's Complement

Hexadecimal Units

Decimal Units

2's Complement

Hexadecimal Units

7FFFFFFF 80000000

450000 0

6DDD0 00000000

Decimal Units

+4294967

295

0

2's Complement

Hexadecimal Units

FFFFFFFF 00000000

Gain Offset

1

1

1

1

0

0

0

0


161

Modbus Utility Manual

Modbus Utility User Manual

Table of Contents

1. Introduction

1.2.1. What is the Modbus protocol?

1.2.2. What is the Modbus/TCP protocol?

1.2.3. What software supports the Modbus and Modbus/TCP protocol?

1.2.4. What are the benefits of using Modbus and Modbus/TCP?

1.2.5. Modbus Resources

1.3.1. Support for the Modbus/TCP communication protocol that allows access

to I/O devices that are inserted in the I/O slots.

1.3.2. Support for the VxComm technique for all COM ports on connected

controllers.

1.3.3. Automatic I/O module scanning.

1.3.4. Automatic assignment of a register address for the I/O modules.

1.3.5. Allows simultaneous access by multiple clients (or masters).

1.3.6. Online configuration via Ethernet using the Modbus Utility

1.3.7. Supports I-8000 and I-87000 series I/O modules

1.3.8. Updateable and programmable firmware

1.4.1. Basic Application 1: Modbus TCP I/O Device

1.4.2. Basic Application 2: Modbus/RTU to Modbus/TCP Converter

1.4.3. Basic Application 3: Modbus/TCP I/O Device using the VxComm

Technique

1.4.4. Advanced Application 1: User-defined Modbus/TCP Controller

1.4.5. Advanced Application 2: Modbus/TCP Controller using the VxComm

technique

2. Starting the Modbus Utility

3. Linking to SCADA Software via Modbus

Appendix A: Backing Up and

Recovering the EEPROM Settings

Appendix B: Function Codes (FC)

Function Code 01=Read Coil Status

Function Code 02=Read Input Status

Function Code 03=Read Holding Registers

Function Code 04=Read Input Registers

Function Code 05=Write Single Coil

Function Code 06= Write Single Register

Function Code 15=Write Multiple Coils

Function Code 16= Write Multiple Registers

Appendix C: Supported Modules

Appendix D: Range Codes for

Analog Modules

(Data

𝒳

, FValue

𝒴

)

Min. Value

(-32768)

Offset

(0, 0)

Max. Value

(+32767)

Related manuals

ICP DAS USA

ET-87P4-MTCP

ICP

PPDS-755D-MTCP

ICP

ET-8KP8-MTCP

ICP

PDS-5105D-MTCP

ICP

PPDSM-734D-MTCP

ICP DAS USA

ET-87P4

ICP DAS USA

WP-8441

ICP DAS USA

ET-87P4

ICP

PPDS-782-MTCP

ICP

IP-8411-MRTU

ICP

iBPC-4081