0% found this document useful (0 votes)

20 views51 pages

Modbus Integration Guide

The Modbus Integration Guide provides detailed instructions for integrating Automated Logic® controllers with Modbus devices, covering scenarios where the controller acts as a master, slave, client, or server. It includes a checklist for prerequisites, steps for creating control programs, and wiring specifications, as well as troubleshooting tips. The document emphasizes the importance of correct address formatting and communication settings to ensure successful integration.

Uploaded by

C. Scot Lewis

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

20 views51 pages

Modbus Integration Guide

Uploaded by

C. Scot Lewis

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

Modbus Integration Guide

For an LGR line, ME-LGR line, or ME812u-LGR controller

Rev. 6/28/2012

Verify that you have the most current version of this document. Go to [Link] then select Support >
Download > Third-party Interfaces > Third-party Integration Guides.
Contents
Overview .................................................................................................................................. 1
Controller as a master device on EIA-232/485 ............................................................................ 2
Before-you-begin checklist ........................................................................................... 2
The integration process ................................................................................................ 3
1 Create a control program in EIKON® LogicBuilder ..................................................... 3
Formatting a Modbus address ....................................................................... 3
Editing a microblock address ......................................................................... 5
2 Download the Modbus driver and control programs ................................................... 6
3 Connect the Automated Logic® controller to the third-party device ............................ 6
Wiring specifications ..................................................................................... 6
To wire a third-party device ............................................................................ 6
4 Set up the Modbus Combo driver properties .............................................................. 8
5 Verify the controller is set up correctly ....................................................................... 8
To capture communication using PuTTY ........................................................ 10
Controller as a slave device on EIA-232/485............................................................................. 12
Before-you-begin checklist ......................................................................................... 12
The integration process .............................................................................................. 13
1 Create a control program in EIKON® LogicBuilder ................................................... 13
Formatting a Modbus address ..................................................................... 13
Editing a microblock address ....................................................................... 15
2 Download the Modbus driver and control programs ................................................. 15
3 Connect the Automated Logic® controller to the third-party device .......................... 15
Wiring specifications ................................................................................... 15
To wire a third-party device .......................................................................... 16
4 Set up the Modbus Combo driver properties ............................................................ 17
5 Verify the controller is set up correctly ..................................................................... 17
To capture communication using PuTTY ........................................................ 19
Controller as a client device on Ethernet.................................................................................... 21
Before-you-begin checklist ......................................................................................... 21
The integration process .............................................................................................. 22
1 Create a control program in EIKON® LogicBuilder ................................................... 22
Formatting a Modbus address ..................................................................... 22
Editing a microblock address ....................................................................... 24
2 Download the Modbus driver and control programs ................................................. 25
3 Connect the Automated Logic® controller to the third-party device .......................... 25
4 Set up the Modbus Combo driver properties ............................................................ 25
5 Verify the controller is set up correctly ..................................................................... 26
To capture communication using Wireshark ................................................. 27
To capture communication using PuTTY ........................................................ 28
Controller as a server device on Ethernet ................................................................................... 30
Before-you-begin checklist ......................................................................................... 30
The integration process .............................................................................................. 30
1 Create a control program in EIKON® LogicBuilder ................................................... 31
Formatting a Modbus address ..................................................................... 31
Editing a microblock address ....................................................................... 32
2 Download the Modbus driver and control programs ................................................. 33
3 Connect the Automated Logic® controller to the third-party device .......................... 33
4 Set up the Modbus Combo driver properties ............................................................ 33
5 Verify the controller is set up correctly ..................................................................... 34
To capture communication using Wireshark ................................................. 35
To capture communication using PuTTY ........................................................ 36

© 2012 Automated Logic Corporation. All rights reserved throughout the world. Automated Logic, WebCTRL, EIKON, and BACview are
registered trademarks, and EnergyReports, Environmental Index, and Eco-Screen are trademarks of Automated Logic Corporation. BACnet
is a registered trademark of ASHRAE. All other brand and product names are trademarked by their respective companies.
Modbus Troubleshooting ......................................................................................................... 38
If the Automated Logic® controller is a Serial Master or Ethernet Client ....................... 38
Register addresses ...................................................................................... 38
Errors .......................................................................................................... 39
If the Automated Logic® controller is a Serial Slave or Ethernet Server ........................ 43
Register addresses ...................................................................................... 43
Errors .......................................................................................................... 43
Appendix A - Upgrading an existing Modbus driver ..................................................................... 44
Appendix B - Modbus Protocol Conformance Statement ............................................................. 46
Overview
You can use an Automated Logic® controller to integrate Modbus device(s) with a
WebCTRL® system. The controller can serve as a master or slave on a serial network, or a
client or server on a TCP/IP network.
This document is divided into 4 sections that provide integration instructions for the 4
scenarios listed in the first two columns below. Determine how your Automated Logic®
controller will be used, then go to the appropriate page for the instructions.

If the Automated ...on this ...you can use See...

Logic® controller is to media type... this controller
be a Modbus... port...
Master EIA-485, 4 wire S1 Controller as a master
EIA-485, 2 wire S1 or S2 device on EIA-232/485
EIA-232 S1 or S2 (page 2)
Slave EIA-485, 4 wire S1 Controller as a slave
EIA-485, 2 wire S1 or S2 device on EIA-232/485
EIA-232 S1 or S2 (page 12)
Client Ethernet E1 Controller as a client
device on Ethernet
(page 21)
Server Ethernet E1 Controller as a server
device on Ethernet
(page 30)

NOTES
• The Modbus Combo driver supports Modbus devices connected to ports S1, S2, and
E1 simultaneously on the Automated Logic® controller. The third-party point count for
the controller is the total of the 3 ports.
• The 3 ports can simultaneously have different functionality. For example, Port S1
could be a serial master, Port S2 could be a serial slave, and Port E1 an ethernet
client.

CAUTION If you want to upgrade a system to the Modbus Combo driver, carefully
review Appendix A - Upgrading an existing Modbus driver (page 44) to determine if you
should upgrade the driver.

Modbus Integration Guide • Rev. 6/28/2012 1 © 2012 Automated Logic Corporation

Controller as a master device on EIA-232/485
NOTE Modbus supports a single master on each network.

Automated Logic®
Controllers LGR25 ME-LGR25
LGR250 ME-LGR200
LGR1000 ME812u-LGR
Driver Modbus Combo:
drv_melgr_mb_combo_<latest version>.driver
Read/write capability Can read from and write to the third-party equipment
Third party
Supported equipment Any device that supports the Modbus (Modicon)
protocol
Network media type EIA-232, EIA-485
Quantity of Modbus slave For EIA-232: 1 Modbus slave
devices you can physically
connect to Port S1 or Port S2 on For EIA-485: Up to 254 Modbus slaves
the Automated Logic® master NOTE You may reach the point
controller limitation of the Automated
Logic® controller before
connecting 254 Modbus slaves.

Before-you-begin You need the following items, information, and skills for the integration process:
checklist
 A points list for each Modbus device that includes register addresses and read/write
capabilities. Points lists are usually available from the third-party manufacturer’s
representative or website.
 The addresses of the Modbus devices
 The network media type required by the Modbus device: EIA-232 or EIA-485
 A port pinout/configuration of the Modbus device. Pinouts are usually available from
the third-party manufacturer’s representative or website.
 The Modbus network’s baud rate, data bits, parity, and stop bits
 Verification that all communication properties have been set on the Modbus devices
 Verification of communications through the port that the Automated Logic®
controller will connect to
 Experience creating control programs in the EIKON® LogicBuilder application
 Experience installing, wiring, setting up, and downloading to the Automated Logic®
controller

Modbus Integration Guide • Rev. 6/28/2012 2 © 2012 Automated Logic Corporation

The integration Follow the steps in this section to integrate one or more third-party Modbus devices into a
process WebCTRL® system using an Automated Logic® controller. To install and network the
Automated Logic® controller, see the controller's Technical Instructions.

1 Create a When you create your control program, use a Network I/O microblock for each third-party
control program point.
in EIKON® TIP Verify the third-party manufacturer’s register addressing pattern by establishing
LogicBuilder communication with a few points whose values you can physically manipulate before you
spend time addressing the remaining integration points.

Formatting a Modbus address

Use the information below to format a valid address in each microblock that you use to
read or write to a third-party point.

CAUTION!
When integrating third-party devices into a WebCTRL® system, most communication
problems are caused by incorrect data or typing errors in the microblock's Address field.

Address format: protocol://register type/modbus register address/device address

See Defined by Provided in third- Set on third-party

Protocol ALC. See party points list. device (1-254).
below. Register type/ See Register type/ See NOTE below.
Register address Register address
on next page. on next page.

Example: modbus2://UINT/40128/26

NOTE To send a broadcast to all Modbus devices on the port specified by the protocol
signature, use 0 for the device address in a network output microblock.

Protocol

If the point is in a Modbus device connected Use the following protocol

to the Automated Logic® controller's port... signature *
S1 modbus1://

S2 modbus2://
* You can also use modbus:// for points on one of the ports, but not both ports.

Modbus Integration Guide • Rev. 6/28/2012 3 © 2012 Automated Logic Corporation

To... this kind of use this with this and a Modbus

value... microblock... register type... register address in
this range... 1
Read 0 to 65,535 ANI Uint (not Unit) 300001–365535
Unsigned 16-bit integer
Input register (3XXXXX)
0 to 65,535 ANI Uint (not Unit) 400001–465535
Unsigned 16-bit integer
Holding register (4XXXXX)
0 to 4,294,967,296 ANI Uint32 300001–365535
Unsigned, 32-bit (long) integer
Input register (3XXXXX)
0 to 4,294,967,296 ANI Uint32 400001–465535
Unsigned, 32-bit (long) integer
Holding register (4XXXXX)
–32,768 to +32,767 ANI Sint 300001–365535
Signed 16-bit integer
Input register (3XXXXX)
–32,768 to +32,767 ANI Sint 400001–465535
Signed 16-bit integer
Holding register (4XXXXX)
-2,147,483,648 to ANI Sint32 300001–365535
2,147,483,647
Signed, 32-bit (long) integer
Input register (3XXXXX)
-2,147,483,648 to ANI Sint32 400001–465535
2,147,483,647
Signed, 32-bit (long) integer
Holding register (4XXXXX)
Value with decimal point ANI Float 300001–365535 2
Input register (3XXXXX)
Value with decimal point ANI Float 400001–465535 2
Holding register (4XXXXX)
0 or 1 BNI Do 1–65535
Coil / Discrete (binary) output (or ANI)
0 or 1 BNI Di 100001–165535
Discrete (binary) input (1XXXXX) (or ANI)
0 or 1 BNI BITn (where n is a 300001–365535
Input register (3XXXXX) value 0-15 defined
in points list)
0 or 1 BNI BITn (where n is a 400001–465535
Holding register (4XXXXX) value 0-15 defined
in points list)

Modbus Integration Guide • Rev. 6/28/2012 4 © 2012 Automated Logic Corporation

To... this kind of use this with this and a Modbus
value... microblock... register type... register address in
this range... 1
Write 0 to 65,535 ANO Uint (not Unit) 400001–465535
Unsigned 16-bit integer
Holding register (4XXXXX)
–32,768 to +32,767 ANO Sint 400001–465535
Signed 16-bit integer
Holding register (4XXXXX)
Value with decimal point ANO Float 400001–465535 2
Holding register (4XXXXX)
0 or 1 BNO Do 1–65535
Coil (or ANO)
Discrete (binary) output
0 or 1 BNO BITn (where n is a 400001–465535
Holding register (4XXXXX) (or ANO) value 0-15 defined
in points list)

1 The Modbus register address (sometimes called register, address, code, or parameter) must be a decimal value. If the
register addresses in the points list include the letters A-F, use a scientific calculator to convert these hexadecimal
values to decimal values.
If the register addresses in the points list are 5-digit numbers in the range #0001-#9999 (where # = the prefix 1, 3, or
4), you may use the addresses as they are, or change them to fit the formats in the table above by shifting the prefix
one digit to the left. For example, if you see the address 38129, you can also use 308129.

2 Each Float uses 2 consecutive Modbus register addresses. Use the lower number in the microblock address.

See Modbus Troubleshooting (page 38) for more information on register addresses.

Editing a microblock address

You can edit a microblock address in the following places:
• In the EIKON® LogicBuilder Property Editor
• In the WebCTRL® interface on the microblock's Properties page > Details tab
• In the WebCTRL® interface on the control program's Properties page > Network
Points tab

Modbus Integration Guide • Rev. 6/28/2012 5 © 2012 Automated Logic Corporation

2 Download the 1 Go to the website [Link] then select
Modbus driver Third-party Interfaces > Drivers > Third-party interface (ME-LGR & LGR) > Modbus
Combo.
and control
2 Download the driver, saving it in WebCTRLx.x\webroot\<system_name>\drivers.
programs
3 On SiteBuilder's Network tree, double-click the Automated Logic® controller.
4 Select the Automated Logic® controller in the Device Definition drop-down list, then
click OK.
5 On the Network tree, expand the controller, then double-click Driver.
6 Select drv_melgr_mb_combo_<latest version> in the Driver drop-down list, then click
OK.
7 Assign the equipment to the controller by dragging the equipment from the
Geographic tree and dropping it on the controller in the Network tree.

8 Click .
9 In WebCTRL®, download the driver and control programs to the Automated Logic®
controller.

3 Connect the Wiring specifications

Automated
For... Use...
Logic® controller
to the third-party EIA-232 18-28 AWG shielded cable, 50 feet maximum length
device EIA-485 1 • 24 AWG twisted, shielded pair cable for up to 200 feet (60.96 meters) 2
or
• 22 AWG twisted, shielded pair cable for up to 2000 feet (609.6 meters)
See ARC156 Wiring Technical Instructions
([Link] for details.
1 Use an EIA-485, 2-wire connection unless the connected device specifies EIA-485, 4-wire or does
not support EIA-485, 2 wire.
2 Shielding provides noise immunity in an electrically noisy environment. Acceptable wiring types, in
order of greatest to least noise immunity, are:
• two pair, each pair individually shielded
• two pair, single overall cable shield
• four wire, single overall cable shield

To wire a third-party device

1 Turn off the Automated Logic® controller's power.
2 Check the communications wiring for shorts and grounds.
3 Set jumpers and DIP switches on the Automated Logic® controller. See table below.
4 Wire the Automated Logic® controller to the third-party device. See table and notes
below.
5 Turn on the Automated Logic® controller's power.

Modbus Integration Guide • Rev. 6/28/2012 6 © 2012 Automated Logic Corporation

For... Use Wire ...to Set the port's Set DIP switches
Automated Automated third-party jumper(s) on on Automated
Logic® Logic® device Automated Logic®
controller terminal... terminal Logic® controller
port... controller
EIA-232 S1 or S2* TX Rx EIA-232 Turn off or
Rx Tx disable PTP,
MSTP, or
Signal Ground Gnd
Enhanced
EIA-485, S1 or S2* Net+ + EIA-485 Access if it
2-wire Net- - 485-2w (Port applies to the
S1 only) port you are
This is called using.
Half on some
controllers.
EIA-485, S1 Tx+ Rx+ EIA-485
4-wire Tx- Rx- 485-4w
(EIA-422) This is called
Rx+ Tx+
Full on some
Rx- Tx-
controllers.
* The ME812u-LGR does not have Port S2.

NOTES
• If you cannot determine the media type or connections of the third-party device,
contact your third-party representative.
• Use the same polarity throughout the network segment.
• Repeaters are required for more than 32 devices on an EAI-485 network. See your
third-party device manufacturer's recommendations.
• Configure an EIA-485, 4-wire (EIA-422) network as a linear bus with daisy-chained
connections. Star topologies are not recommended.
• To reduce communication and data errors, terminate each end of an EIA-485 network
with a resistor whose value equals the network's characteristic impedance. Some
third-party manufacturers provide a built-in resistor that you enable or disable with a
jumper. Make sure that only devices at the end of a network have termination
enabled.
EXAMPLE If an EIA-485 4-wire network's characteristic impedance is 120 Ohms,
terminate both pairs of wires at each end of the network with a 120 Ohm resistor (4
resistors total). Each end of the network will then have one resistor across the Rx+
and Rx- and one across the Tx+ and Tx-.
• A solid receive light on the Automated Logic® controller indicates a wiring or polarity
problem.

Modbus Integration Guide • Rev. 6/28/2012 7 © 2012 Automated Logic Corporation

4 Set up the 1 On the WebCTRL® NET tree, expand the Automated Logic® controller's driver.
Modbus Combo 2 Expand Protocols, then select Modbus.
driver properties 3 Under Port Configuration, enable the port(s) on the controller that third-party
device(s) are connected to.
4 For each port that you enabled, select one of the following in the Supported
Microblock Signature field:

Select... If the Modbus point addresses

on the port use...
modbus#:// Only this signature
modbus:// & modbus#:// Both types of signatures

5 Set the remaining fields under Port Configuration to match the third-party device.
6 Under Protocol Configuration, verify that Is this device a Master is set to Yes.
7 Set the remaining fields using information from the third-party manufacturer's
representative. Select the Details checkbox for help.
8 On the NET tree, select Protocols.
9 In the Protocol Status table, verify the following for the port you enabled:
○ Modbus 1 shows Running on Port S1
○ Modbus 2 shows Running on Port S2
If the status shows Not Running or the wrong port, verify that:
○ You selected the correct port in step 3 above.
○ You set the controller's DIP switches correctly.
○ The control program has at least one valid Modbus address. The driver must
detect at least one valid address to initiate Modbus communications.

5 Verify the 1 On the WebCTRL® GEO tree, select the control program for the Automated Logic®
controller is set controller.
up correctly 2 Select the Properties page > Network Points tab.

If... Then...
You see the point value you You have successfully established communication with
expect with no errors in the the third-party device.
Error column
All points show question The WebCTRL® application is not communicating with
marks instead of values the Automated Logic® controller or the control program.
Troubleshoot the controller's communications. See the
controller's Technical Instructions.

Modbus Integration Guide • Rev. 6/28/2012 8 © 2012 Automated Logic Corporation

If... Then...
Some points show question You may have exceeded the third-party points available
marks instead of values in the controller. If so, do one of the following:
• Use a controller that provides more third-party
points.
• Split the points between two control programs used
in separate controllers.
To determine the number of third-party points used in a
controller: On the WebCTRL® NET tree, click on the
controller's Driver, then scroll to the bottom of the page.
Number of integration points requested and Number of
integration points active show how many third-party
Network I/O microblocks the controller is using. These
counts will differ if you exceed the controller's
integration point limit. For example, if your LGR25's
control program includes 27 third-party points, your
Integration points requested will be 27 and your
Integration points active will be 25.
The point name is red Look in the Error column for one of the following error
codes and descriptions.
• 1 - Communications Disabled for this Microblock
Enable the microblock's Communications Enabled
field on the Network Points tab, on the microblock's
Properties page > Details tab, or in the EIKON®
LogicBuilder application.
• 3 - Address Error - Unknown Protocol Specified
Select the correct port on the Modbus driver page,
verify that Address in the microblock is correct, or
set the DIP switches correctly on the controller.
• All other errors
On the WebCTRL® NET tree, expand the Automated
Logic® controller's driver, then select Protocols >
Modbus > Modbus Error Definitions. Find the error
and its possible solution.
A value is incorrect Verify that:
• The Address in the microblock is correct.
• The retrieved value is scaled properly, if necessary.
For example, scaled from Celsius to Fahrenheit.
Refer to the third-party manufacturer's
documentation or the controller's Technical
Instructions for scaling information.

If the above solutions do not resolve the problem, gather the following information for
technical support:
• A diagnostic capture. See next topic.
• A screenshot of the Driver > Protocols > Properties page and the Driver > Protocols >
Modbus > Properties page
• A screenshot of the Properties page > Network Points tab showing addresses and
errors
• Technical instructions for the third-party device, if available

Modbus Integration Guide • Rev. 6/28/2012 9 © 2012 Automated Logic Corporation

To capture communication using PuTTY
Use PuTTY, a free open source terminal emulation program that works with all Windows
operating systems, to capture communication between the controller and the Modbus
device into a text file.

PREREQUISITES
• Download and install PuTTY from the PuTTY website
([Link]
• Get the Automated Logic® controller's IP address.
• Get the longest microblock refresh time in the control program that has the error you
are troubleshooting. In WebCTRL®, view the control program's Properties page >
Network Points tab to see all the refresh times.

1 Connect your computer's Ethernet port to the controller's Ethernet port using one of
the following:
○ A CAT5 or higher Ethernet crossover cable
○ A hub and a CAT5 or higher Ethernet straight-through cable
2 Ping the Automated Logic® controller to verify communications between the
controller and the computer you are using to get this capture.
3 On the WebCTRL® NET tree, expand the Automated Logic® controller's driver, then
select Protocols.
4 Click Properties, select Enable Telnet diagnostics, then click OK.
5 Start PuTTY.
6 Enter the controller's IP address.
7 Select Telnet as the Connection Type.
8 Click the Logging option in the upper left corner of the left pane.
9 Select Printable output.
10 Select a location for the capture text file.
11 Click Open to start the session.
12 After Login:>, type: diagport
Press Enter.
13 To capture data receipts, after diagport>, do one of the following:
○ For Modbus on Port S1, type: modbus1 rx
○ For Modbus on Port S2, type: modbus2 rx
Press Enter.
14 To capture data transmissions, after diagport>, do one of the following:
○ For Modbus on Port S1, type: modbus1 tx
○ For Modbus on Port S2, type: modbus2 tx
Press Enter.
15 To capture more detailed diagnostic messages, after diagport>, do one of the
following:
○ For Modbus on Port S1, type: modbus1 vmsg
○ For Modbus on Port S2, type: modbus2 vmsg
Press Enter.

Modbus Integration Guide • Rev. 6/28/2012 10 © 2012 Automated Logic Corporation

16 To capture error messages, after diagport>, do one of the following:
○ For Modbus on Port S1, type: modbus1 emsg
○ For Modbus on Port S2, type: modbus2 emsg
Press Enter.
17 Verify the displayed text shows:
modbus reporting level status:
rx on
tx on
flush off
fc1 off
fc2 off
vmsg on
emsg on
off
If rx, tx, vmsg, or emsg show off, repeat the appropriate step (13, 14, 15, or 16)
to turn on capture of that item.
18 After diagport>, type: go
Press Enter.
19 Run the capture for one of the following periods of time:
○ If all microblock refresh times are one minute or less, run the capture for 5
minutes.
○ If any microblock refresh time is longer than 1 minute, run the capture for 5 times
the longest microblock refresh time.
20 Type: stop
Press Enter. Verify that you see diagport> before doing the next step.
21 After diagport>, type: logout
Press Enter.
22 To end the PuTTY session, click the X in the upper right corner.
23 In WebCTRL®, clear the Enable Telnet diagnostics checkbox (see steps 3 and 4),
then click OK.
24 Open the text file from the location you selected in step 11, and then verify that it
legibly shows the same information that PuTTY displayed.

Modbus Integration Guide • Rev. 6/28/2012 11 © 2012 Automated Logic Corporation

Controller as a slave device on EIA-232/485
You can integrate an Automated Logic® controller acting as a slave device into a
third-party Modbus system.

Automated Logic®
Controllers LGR25 ME-LGR25
LGR250 ME-LGR200
LGR1000 ME812u-LGR
Driver Modbus Combo:
drv_melgr_mb_combo_<latest version>.driver
Capability Can be read from and written to
Third party
Supported equipment A master device that supports the Modbus (Modicon)
protocol
Network media type EIA-232, EIA-485
Quantity of devices you can 1 Modbus master
physically connect to Port S1 or
Port S2 on the Automated
Logic® controller

Before-you-begin You need the following items, information, and skills for the integration process:
checklist
 A list of the points in the Automated Logic controller that the Modbus device will
read or write to.
 The Automated Logic® controller's address on the Modbus network.
 The network media type required by the Modbus device: EIA-232 or EIA-485
 A port pinout/configuration of the Modbus device. Pinouts are usually available from
the third-party manufacturer’s representative or website.
 The Modbus network’s baud rate, data bits, parity, and stop bits
 Verification that all communication properties have been set on the Modbus devices
 Verification of communications through the port that the Automated Logic®
controller will connect to
 Experience creating control programs in the EIKON® LogicBuilder application
 Experience installing, wiring, setting up, and downloading to the Automated Logic®
controller

Modbus Integration Guide • Rev. 6/28/2012 12 © 2012 Automated Logic Corporation

The integration Follow the steps in this section to integrate an Automated Logic® controller into a
process Modbus system. To install and network the Automated Logic® controller, see the
controller's Technical Instructions.

1 Create a When you create your control program, use a Network I/O microblock for each value that
control program you want to expose to the Modbus master.
in EIKON®
LogicBuilder
Formatting a Modbus address
Use the information below to format a valid address in each microblock that you want to
expose to the Modbus master.

CAUTION!
When integrating third-party devices into a WebCTRL® system, most communication
problems are caused by incorrect data or typing errors in the microblock's Address field.

Address format: protocol://register type/modbus register address

See Defined by Assigned by you.

Protocol ALC. See See Register type/
below. Register type/ Register address
Register address on next page.
on next page.

Example: modbus2://UINT/40128

Protocol

If the Modbus master is connected Use this protocol signature

to the controller's port...
S1 modbus1://
S2 modbus2://

NOTE You can also use the modbus:// signature for points on one of the ports, but not
both ports.

Register type/Register address

When the Automated Logic controller is a slave device, you must expose its points so that
they can be read or written to by a third-party master device.

Modbus Integration Guide • Rev. 6/28/2012 13 © 2012 Automated Logic Corporation

For a this kind of exposed value in use this with this and a Modbus
third-party the Automated Logic® microblock... register type... register address in
device to... controller... this range...
Write 0 to 65,535 ANI Uint (not Unit) 400001–465535
Unsigned 16-bit integer
Holding register (4XXXXX)
–32,768 to +32,767 ANI Sint 400001–465535
Signed 16-bit integer
Holding register (4XXXXX)
Value with decimal point ANI Float 400001–465535
Holding register (4XXXXX)
0 or 1 BNI Do 1–65535
Coil
Discrete (binary) output
Read 0 to 65,535 ANO Uint (not Unit) 300001–365535
Unsigned 16-bit integer
Input register (3XXXXX)
0 to 65,535 ANO Uint (not Unit) 400001–465535
Unsigned 16-bit integer
Holding register (4XXXXX)
–32,768 to +32,767 ANO Sint 300001–365535
Signed 16-bit integer
Input register (3XXXXX)
–32,768 to +32,767 ANO Sint 400001–465535
Signed 16-bit integer
Holding register (4XXXXX)
Value with decimal point ANO Float 300001–365535
Input register (3XXXXX)
Value with decimal point ANO Float 400001–465535
Holding register (4XXXXX)
0 or 1 BNO Do 1–65535
Coil
Discrete (binary) output
0 or 1 BNO Di 100001–165535
Discrete (binary) input
(1XXXXX)

1 If the register addresses in the points list are 5-digit numbers in the range #0001-#9999 (where # = the prefix 1, 3,
or 4), you may use the addresses as they are, or change them to fit the formats in the table above by shifting the
prefix one digit to the left. For example, if you see the address 38129, you can also use 308129.

2 Each Float uses 2 consecutive Modbus register addresses. Use the lower number in the microblock address.

See Modbus Troubleshooting (page 38) for more information on register addresses.

Modbus Integration Guide • Rev. 6/28/2012 14 © 2012 Automated Logic Corporation

Editing a microblock address
You can edit a microblock address in the following places:
• In the EIKON® LogicBuilder Property Editor
• In the WebCTRL® interface on the microblock's Properties page > Details tab
• In the WebCTRL® interface on the control program's Properties page > Network
Points tab

2 Download the 1 Go to the website [Link] then select

Modbus driver Third-party Interfaces > Drivers > Third-party interface (ME-LGR & LGR) > Modbus
Combo.
and control
2 Download the driver, saving it in WebCTRLx.x\webroot\<system_name>\drivers.
programs
3 On SiteBuilder's Network tree, double-click the Automated Logic® controller.
4 Select the Automated Logic® controller in the Device Definition drop-down list, then
click OK.
5 On the Network tree, expand the controller, then double-click Driver.
6 Select drv_melgr_mb_combo_<latest version> in the Driver drop-down list, then click
OK.
7 Assign the equipment to the controller by dragging the equipment from the
Geographic tree and dropping it on the controller in the Network tree.

8 Click .
9 In WebCTRL®, download the driver and control programs to the Automated Logic®
controller.

3 Connect the Wiring specifications

Modbus Integration Guide • Rev. 6/28/2012 15 © 2012 Automated Logic Corporation

To wire a third-party device
1 Turn off the Automated Logic® controller's power.
2 Check the communications wiring for shorts and grounds.
3 Set jumpers and DIP switches on the Automated Logic® controller. See table below.
4 Wire the Automated Logic® controller to the third-party device. See table and notes
below.
5 Turn on the Automated Logic® controller's power.

Modbus Integration Guide • Rev. 6/28/2012 16 © 2012 Automated Logic Corporation

4 Set up the 1 On the WebCTRL® NET tree, expand the Automated Logic® controller's driver.
Modbus Combo 2 Expand Protocols, then select Modbus.
driver properties 3 Under Port Configuration, enable the port(s) on the controller that connects to the
Modbus Master.
4 For each port that you enabled, select one of the following in the Supported
Microblock Signature field:

Select... If the Modbus point addresses

on the port use...
modbus#:// Only this signature
modbus:// & modbus#:// Both types of signatures

5 Under Port Configuration, select the controller port that connects the third-party
network.
6 Under Protocol Configuration, set Is this device a Master to No for the port you are
using.
7 In the Modbus Slave Address for this port is field, type the address of the Automated
Logic® controller on the third-party network.
8 On the NET tree, select Protocols.
9 In the Protocol Status table, verify the following for the port you enabled:
○ Modbus 1 shows Running on Port S1
○ Modbus 2 shows Running on Port S2
If the status shows Not Running or the wrong port, verify that:
○ You selected the correct port in step 3 above.
○ You set the controller's DIP switches correctly.
○ The control program has at least one valid Modbus address. The driver must
detect at least one valid address to initiate Modbus communications.

5 Verify the 1 On the WebCTRL® GEO tree, select the control program for the Automated Logic®
controller is set controller.
up correctly 2 Select the Properties page > Network Points tab.

If... Then...
You see the point value you You have successfully exposed the Automated Logic®
expect and the Error column controller's value to the third-party device.
shows Initializing
All points show question The WebCTRL® application is not communicating with
marks instead of values the Automated Logic® controller or the control program.
Troubleshoot the controller's communications. See the
controller's Technical Instructions.

Modbus Integration Guide • Rev. 6/28/2012 17 © 2012 Automated Logic Corporation

If... Then...
Some points show question You may have exceeded the third-party points available
marks instead of values in the controller. If so, do one of the following:
• Use a controller that provides more third-party
points.
• Split the points between two control programs used
in separate controllers.
To determine the number of third-party points used in a
controller: On the WebCTRL® NET tree, click on the
controller's Driver, then scroll to the bottom of the page.
Number of integration points requested and Number of
integration points active show how many third-party
Network I/O microblocks the controller is using. These
counts will differ if you exceed the controller's
integration point limit. For example, if your LGR25's
control program includes 27 third-party points, your
Integration points requested will be 27 and your
Integration points active will be 25.
The point name is red Look in the Error column for one of the following error
codes and descriptions.
• 1 - Communications Disabled for this Microblock
Enable the microblock's Communications Enabled
field on the Network Points tab, on the microblock's
Properties page > Details tab, or in EIKON®
LogicBuilder.
• 3 - Address Error - Unknown Protocol Specified
Select the correct port on the Modbus driver page in
WebCTRL®, verify that Address in the microblock is
correct, or set the DIP switches correctly on the
controller.
• All other errors
On the WebCTRL® NET tree, expand the Automated
Logic® controller's driver, then select Protocols >
Modbus > Modbus Error Definitions. Find the error
and its possible solution.
A value is incorrect Verify that the Address in the microblock is correct.

Modbus Integration Guide • Rev. 6/28/2012 18 © 2012 Automated Logic Corporation

Modbus Integration Guide • Rev. 6/28/2012 19 © 2012 Automated Logic Corporation

Modbus Integration Guide • Rev. 6/28/2012 20 © 2012 Automated Logic Corporation

Controller as a client device on Ethernet
You can integrate Modbus devices into a WebCTRL® system with an Automated Logic®
controller acting as an IP client in either of the following scenarios:
• The client controller reads and writes to points in a Modbus server.
• The client controller communicates with a Modbus gateway server to read and write
to points in Modbus server devices.

Automated Logic®
Controllers LGR25 ME-LGR25
LGR250 ME-LGR200
LGR1000 ME812u-LGR
Driver Modbus Combo:
drv_melgr_mb_combo_<latest version>.driver
Read/write capability Can read from and write to the third-party equipment
Third party
Supported equipment Any device that supports the Modbus (Modicon)
protocol
Network media type Ethernet
Quantity of devices you can Up to 30 Modbus TCP/IP connections.*
connect to the Automated
Logic® client controller
* You may be able to connect more devices (256 maximum) if you consider the
following:
• The lower the point count per device, the more devices you can connect.
• The more devices, the slower the communication between the
Automated Logic® controller and the Modbus devices.
A practical limit in most systems is approximately 100 devices. To connect more
than 30 devices, change the Close socket after each completed transaction setting
in the driver.

Before-you-begin You need the following items, information, and skills for the integration process:
checklist
 The IP addresses of the Modbus server
 The Unit ID of each Modbus device that contains points that the Automated Logic®
controller will read and write to, and a points list for each device that includes point
register addresses and read/write capabilities. Points lists are usually available from
the third-party manufacturer’s representative or website.
 Verification that all communication properties have been set on the Modbus devices
 Verification of Ethernet communication with each server that the Automated Logic®
controller will connect to
 Experience creating control programs in the EIKON® LogicBuilder application
 Experience installing, wiring, setting up, and downloading to the Automated Logic®
controller

Modbus Integration Guide • Rev. 6/28/2012 21 © 2012 Automated Logic Corporation

Formatting a Modbus address

Use the information below to format a valid address in each microblock that you use to
read or write to a third-party point.

CAUTION!
When integrating third-party devices into a WebCTRL® system, most communication
problems are caused by incorrect data or typing errors in the microblock's Address field.

Address format:

mtcpip://register type/modbus register address/unit ID/IP address

Defined by Provided in third- Set on the IP address of

ALC. See party points list. third-party the Modbus
Register type/ See Register type/ device that server
Register address Register address contains
on next page. on next page. the point.
See Unit ID
below.

Example: mtcpip://UINT/40128/3/[Link]

Unit ID

If the register address is in... the Unit ID is...

The Modbus server 0 or 255
A device on the Modbus server's serial network 1–254

Modbus Integration Guide • Rev. 6/28/2012 22 © 2012 Automated Logic Corporation

To... this kind of use this with this and a Modbus

value... microblock... register type... register address in
this range... 1
Read 0 to 65,535 ANI Uint (not Unit) 300001–365535
Unsigned 16-bit integer
Input register (3XXXXX)
0 to 65,535 ANI Uint (not Unit) 400001–465535
Unsigned 16-bit integer
Holding register (4XXXXX)
0 to 4,294,967,296 ANI Uint32 300001–365535
Unsigned, 32-bit (long) integer
Input register (3XXXXX)
0 to 4,294,967,296 ANI Uint32 400001–465535
Unsigned, 32-bit (long) integer
Holding register (4XXXXX)
–32,768 to +32,767 ANI Sint 300001–365535
Signed 16-bit integer
Input register (3XXXXX)
–32,768 to +32,767 ANI Sint 400001–465535
Signed 16-bit integer
Holding register (4XXXXX)
-2,147,483,648 to ANI Sint32 300001–365535
2,147,483,647
Signed, 32-bit (long) integer
Input register (3XXXXX)
-2,147,483,648 to ANI Sint32 400001–465535
2,147,483,647
Signed, 32-bit (long) integer
Holding register (4XXXXX)
Value with decimal point ANI Float 300001–365535 2
Input register (3XXXXX)
Value with decimal point ANI Float 400001–465535 2
Holding register (4XXXXX)
0 or 1 BNI Do 1–65535
Coil / Discrete (binary) output (or ANI)
0 or 1 BNI Di 100001–165535
Discrete (binary) input (1XXXXX) (or ANI)
0 or 1 BNI BITn (where n is 300001–365535
Input register (3XXXXX) a value 0-15
defined in points
list)
0 or 1 BNI BITn (where n is 400001–465535
Holding register (4XXXXX) a value 0-15
defined in points
list)

Modbus Integration Guide • Rev. 6/28/2012 23 © 2012 Automated Logic Corporation

1 The Modbus register address (sometimes called register, address, code, or parameter) must be a decimal value. If
the register addresses in the points list include the letters A-F, use a scientific calculator to convert these
hexadecimal values to decimal values.
If the register addresses in the points list are 5-digit numbers in the range #0001-#9999 (where # = the prefix 1, 3,
or 4), you may use the addresses as they are, or change them to fit the formats in the table above by shifting the
prefix one digit to the left. For example, if you see the address 38129, you can also use 308129.

2 Each Float uses 2 consecutive Modbus register addresses. Use the lower number in the microblock address.

See Modbus Troubleshooting (page 38) for more information on register addresses.

Editing a microblock address

Modbus Integration Guide • Rev. 6/28/2012 24 © 2012 Automated Logic Corporation

2 Download the 1 Go to the website [Link] then select
Modbus driver Third-party Interfaces > Drivers > Third-party interface (ME-LGR & LGR) > Modbus
Combo.
and control
programs 2 Download the driver, saving it in WebCTRLx.x\webroot\<system_name>\drivers.
3 On SiteBuilder's Network tree, double-click the Automated Logic® controller.
4 Select the Automated Logic® controller in the Device Definition drop-down list, then
click OK.
5 On the Network tree, expand the controller, then double-click Driver.
6 Select drv_melgr_mb_combo_<latest version> in the Driver drop-down list, then click
OK.
7 Assign the equipment to the controller by dragging the equipment from the
Geographic tree and dropping it on the controller in the Network tree.

8 Click .
9 In WebCTRL®, download the driver and control programs to the Automated Logic®
controller.

3 Connect the Use one of the following CAT5 or higher Ethernet cables:
Automated • A cross-over cable to connect the Automated Logic® controller directly to the
Logic® controller third-party Modbus device
to the third-party • A straight-through cable to connect the controller to a hub or switch, and a second
device straight-through cable to connect the hub or switch to the third-party Modbus device
Maximum cable length: 328 feet (100 meters)

1 Turn off the Automated Logic® controller's power.

2 Check the communications wiring for shorts and grounds.
3 Wire the Automated Logic® controller's Port E1 to the third-party device.
NOTE Port E1 will still be capable of BACnet communication.
4 Turn on the Automated Logic® controller's power.

4 Set up the 1 On the WebCTRL® NET tree, expand the Automated Logic® controller's driver.
Modbus Combo 2 Expand Protocols, then select Modbus TCP/IP.
driver properties 3 Under Port Configuration, select TCP/IP as the Communication Type.
4 The standard Modbus TCP Port is 502. If a different port is to be used, type the port
number. Select the Details checkbox for help.
5 Under Modbus Protocol Configuration, set This device is a Client to Yes.
6 Set the remaining fields under Modbus Protocol Configuration using information from
the third-party manufacturer's representative. Select the Details checkbox for help.
7 If the Automated Logic® controller has more than 30 TCP/IP connections, under
TCP/IP Protocol Configuration, change Close socket after each completed
transaction to Yes.
NOTE If you connect more than 30 devices (256 maximum), consider the following:
• The lower the point count per device, the more devices you can connect.
• The more devices, the slower the communication between the Automated Logic®
controller and the Modbus devices.
A practical limit in most systems is approximately 100 devices.

Modbus Integration Guide • Rev. 6/28/2012 25 © 2012 Automated Logic Corporation

8 On the NET tree, select Protocols.
9 In the Protocol Status table, verify that the mtcpip protocol shows Running on Port
E1.

5 Verify the 1 On the WebCTRL® GEO tree, select the control program for the Automated Logic®
controller is set controller.
up correctly 2 Select the Properties page > Network Points tab.

If... Then...
You see the point value You have successfully established communication with the
you expect with no errors third-party device.
in the Error column
All points show question The WebCTRL® application is not communicating with the
marks instead of values Automated Logic® controller or the control program.
Troubleshoot the controller's communications. See the
controller's Technical Instructions.
Some points show You may have exceeded the third-party points available in
question marks instead of the controller. If so, do one of the following:
values • Use a controller that provides more third-party points.
• Split the points between two control programs used in
separate controllers.
To determine the number of third-party points used in a
controller: On the WebCTRL® NET tree, click on the
controller's Driver, then scroll to the bottom of the page.
Number of integration points requested and Number of
integration points active show how many third-party
Network I/O microblocks the controller is using. These
counts will differ if you exceed the controller's integration
point limit. For example, if your LGR25's control program
includes 27 third-party points, your Integration points
requested will be 27 and your Integration points active will
be 25.
The point name is red Look in the Error column for one of the following error
codes and descriptions.
• 1 - Communications Disabled for this Microblock
Enable the microblock's Communications Enabled field
on the Network Points tab, on the microblock's
Properties page > Details tab, or in EIKON®
LogicBuilder.
• 3 - Address Error - Unknown Protocol Specified
Select the correct port on the Modbus driver page in
WebCTRL®, verify that Address in the microblock is
correct, or set the DIP switches correctly on the
controller.
• All other errors
On the WebCTRL® NET tree, expand the Automated
Logic® controller's driver, then select Protocols >
Modbus > Modbus Error Definitions. Find the error and
its possible solution.

Modbus Integration Guide • Rev. 6/28/2012 26 © 2012 Automated Logic Corporation

If... Then...
A value is incorrect Verify that:
• The Address in the microblock is correct.
• The retrieved value is scaled properly, if necessary. For
example, scaled from Celsius to Fahrenheit. Refer to
the third-party manufacturer's documentation or the
controller's Technical Instructions for scaling
information.

If the above solutions do not resolve the problem, gather the following information for
technical support:
• A diagnostic capture using Wireshark. See the following section for Wireshark
instructions.
NOTE If directed by Tech Support, you can use PuTTY to get a diagnostic capture.
PuTTY instructions are after the Wireshark instructions.
• A screenshot of the driver's Protocols and Modbus TCP/IP pages.
• A screenshot of the Properties page > Network Points tab showing addresses and
errors
• All information from a Modstat copied into a text file.
Right-click the Modstat, then select Select All. Press Ctrl+C to copy the information,
then open Notepad and paste the information into a text file.
• Technical instructions for the third-party device, if available

To capture communication using Wireshark

Use Wireshark, a network analysis tool, to capture the Ethernet communication between
the Automated Logic® controller and the Modbus device.

PREREQUISITE Provide an Ethernet hub (not a switch) so that Wireshark can capture all
Ethernet communication, not just broadcasts.

1 Download the latest version of Wireshark from the Wireshark website

([Link]
2 Run the Wireshark install program, accepting all defaults. Include WinPcap in the
installation.
3 Disconnect the network cable from the Automated Logic® controller's Ethernet port,
then plug the cable into the hub's Uplink port.
4 Use a separate Ethernet cable to connect the controller's Ethernet port to the hub.
5 Connect the Modbus device's Ethernet cable to the hub.
6 Connect the Ethernet port of the computer running Wireshark to the hub.
7 On the computer, click Start > All Programs > Wireshark.

Modbus Integration Guide • Rev. 6/28/2012 27 © 2012 Automated Logic Corporation

8 From the menu bar, select Capture > Interfaces.

9 Click the Start button next to the adapter that is connected to the network. This starts
the IP capture.

TIP Choose the adapter that shows the Packets value changing.
10 Allow the capture to run long enough to ensure that there is sufficient data to allow a
technician to review the problem.
11 On the menu bar, select Capture > Stop to stop the data capture.
12 Select File > Save and save the capture to a convenient location. Leave the Save as
type default set to Wireshark/tcpdump/… - libpcap (*.pcap, *.cap).
13 Send the file to Automated Logic® Technical Support for analysis.

TIP You can color code the information in the Wireshark capture file based on
user-defined criteria. See Wireshark's Help for instructions on setting up Coloring Rules.

To capture communication using PuTTY

Use PuTTY, a free open source terminal emulation program that works with all Windows
operating systems, to capture communication between the controller and the Modbus
device into a text file.

Modbus Integration Guide • Rev. 6/28/2012 28 © 2012 Automated Logic Corporation

5 Start PuTTY.
6 Enter the controller's IP address.
7 Select Telnet as the Connection Type.
8 Click the Logging option in the upper left corner of the left pane.
9 Select Printable output.
10 Select a location for the capture text file.
11 Click Open to start the session.
12 After Login:>, type: diagport
Press Enter.
13 To capture data receipts, after diagport>, type: mtcpip rx
Press Enter.
14 To capture data transmissions, after diagport>, type: mtcpip tx
Press Enter.
15 To capture more detailed diagnostic messages, after diagport>, type: mtcpip
vmsg
Press Enter.
16 To capture error messages, after diagport>, type: mtcpip emsg
Press Enter.
17 Verify the displayed text shows:
modbus reporting level status:
rx on
tx on
flush off
fc1 off
fc2 off
vmsg on
emsg on
off
If rx, tx, vmsg, or emsg show off, repeat the appropriate step (13, 14, 15, or 16)
to turn on capture of that item.
18 After diagport>, type: go
Press Enter.
19 Run the capture for one of the following periods of time:
○ If all microblock refresh times are one minute or less, run the capture for 5
minutes.
○ If any microblock refresh time is longer than 1 minute, run the capture for 5 times
the longest microblock refresh time.
20 Type: stop
Press Enter. Verify that you see diagport> before doing the next step.
21 After diagport>, type: logout
Press Enter.
22 To end the PuTTY session, click the X in the upper right corner.
23 In WebCTRL®, clear the Enable Telnet diagnostics checkbox (see steps 3 and 4),
then click OK.
24 Open the text file from the location you selected in step 11, and then verify that it
legibly shows the same information that PuTTY displayed.

Modbus Integration Guide • Rev. 6/28/2012 29 © 2012 Automated Logic Corporation

Controller as a server device on Ethernet

Before-you-begin You need the following items, information, and skills for the integration process:
checklist
 A list of the points in the Automated Logic® controller that the Modbus client will
read or write to.
 Verification that all communication properties have been set on the Modbus devices
 Verification of Ethernet communication with each Modbus client that the Automated
Logic® controller will connect to
 Experience creating control programs in the EIKON® LogicBuilder application
 Experience installing, wiring, setting up, and downloading to the Automated Logic®
controller

Modbus Integration Guide • Rev. 6/28/2012 30 © 2012 Automated Logic Corporation

1 Create a When you create your control program, use a Network I/O microblock for each value that
control program you want to expose to the Modbus client.
in EIKON®
LogicBuilder

Formatting a Modbus address

Use the information below to format a valid address for each value that you want to
expose to the Modbus client.

CAUTION!
When integrating third-party devices into a WebCTRL® system, most communication
problems are caused by incorrect data or typing errors in the microblock's Address field.

Address format:
mtcpip://register type/modbus register address

Defined by Provided in third-

ALC. See party points list.
Register type/ See Register type/
Register address Register address
on next page. on next page.

Example: mtcpip://UINT/40128

Register type/Register address

When the Automated Logic controller is a server device, you must expose its points so
that they can be read or written to by a third-party client device.

For a this kind of exposed value in use this with this and a Modbus
third-party the Automated Logic® microblock... register type... register address in
device to... controller... this range...
Read 0 to 65,535 ANO Uint (not Unit) 300001–365535
Unsigned 16-bit integer
Input register (3XXXXX)
0 to 65,535 ANO Uint (not Unit) 400001–465535
Unsigned 16-bit integer
Holding register (4XXXXX)
–32,768 to +32,767 ANO Sint 300001–365535
Signed 16-bit integer
Input register (3XXXXX)
–32,768 to +32,767 ANO Sint 400001–465535
Signed 16-bit integer
Holding register (4XXXXX)
Value with decimal point ANO Float 300001–365535
Input register (3XXXXX)
Value with decimal point ANO Float 400001–465535
Holding register (4XXXXX)
0 or 1 BNO Do 1–65535
Coil
Discrete (binary) output
0 or 1 BNO Di 100001–165535
Discrete (binary) input
(1XXXXX)

2 Each Float uses 2 consecutive Modbus register addresses. Use the lower number in the microblock address.

See Modbus Troubleshooting (page 38) for more information on register addresses.

Editing a microblock address

8 Click .
9 In WebCTRL®, download the driver and control programs to the Automated Logic®
controller.

1 Turn off the Automated Logic® controller's power.

5 Verify the 1 On the WebCTRL® GEO tree, select the control program for the Automated Logic®
controller is set controller.
up correctly 2 Select the Properties page > Network Points tab.

If... Then...
You see the point value You have successfully exposed the Automated Logic®
you expect and the Error controller's value to the third-party device.
column shows Initializing
All points show question The WebCTRL® application is not communicating with the
marks instead of values Automated Logic® controller or the control program.
Troubleshoot the controller's communications. See the
controller's Technical Instructions.
Some points show You may have exceeded the third-party points available in
question marks instead of the controller. If so, do one of the following:
values • Use a controller that provides more third-party points.
• Split the points between two control programs used in
separate controllers.
To determine the number of third-party points used in a
controller: On the WebCTRL® NET tree, click on the
controller's Driver, then scroll to the bottom of the page.
Number of integration points requested and Number of
integration points active show how many third-party
Network I/O microblocks the controller is using. These
counts will differ if you exceed the controller's integration
point limit. For example, if your LGR25's control program
includes 27 third-party points, your Integration points
requested will be 27 and your Integration points active will
be 25.
The point name is red Look in the Error column for one of the following error
codes and descriptions.
• 1 - Communications Disabled for this Microblock
Enable the microblock's Communications Enabled field
on the Network Points tab, on the microblock's
Properties page > Details tab, or in EIKON®
LogicBuilder.
• 3 - Address Error - Unknown Protocol Specified
Select the correct port on the Modbus driver page in
WebCTRL®, verify that Address in the microblock is
correct, or set the DIP switches correctly on the
controller.
• All other errors
On the WebCTRL® NET tree, expand the Automated
Logic® controller's driver, then select Protocols >
Modbus > Modbus Error Definitions. Find the error and
its possible solution.
A value is incorrect Verify that the Address in the microblock is correct.

To capture communication using Wireshark

Use Wireshark, a network analysis tool, to capture the Ethernet communication between
the Automated Logic® controller and the Modbus device.

PREREQUISITE Provide an Ethernet hub (not a switch) so that Wireshark can capture all
Ethernet communication, not just broadcasts.

1 Download the latest version of Wireshark from the Wireshark website

9 Click the Start button next to the adapter that is connected to the network. This starts
the IP capture.

TIP Choose the adapter that shows the Packets value changing.
10 Allow the capture to run long enough to ensure that there is sufficient data to allow a
technician to review the problem.

11 On the menu bar, select Capture > Stop to stop the data capture.
12 Select File > Save and save the capture to a convenient location. Leave the Save as
type default set to Wireshark/tcpdump/… - libpcap (*.pcap, *.cap).
13 Send the file to Automated Logic® Technical Support for analysis.

TIP You can color code the information in the Wireshark capture file based on
user-defined criteria. See Wireshark's Help for instructions on setting up Coloring Rules.

To capture communication using PuTTY

Use PuTTY, a free open source terminal emulation program that works with all Windows
operating systems, to capture communication between the controller and the Modbus
device into a text file.

1 Connect your computer's Ethernet port to the controller's Ethernet port using one of
the following:
○ A CAT5 or higher Ethernet crossover cable
○ A hub and a CAT5 or higher Ethernet straight-through cable
2 Ping the Automated Logic® controller to verify communications between the
controller and the computer you are using to get this capture.
3 On the WebCTRL® NET tree, expand the Automated Logic® controller's driver, then
select Protocols.
4 Click Properties, select Enable Telnet diagnostics, then click OK.
5 Start PuTTY.
6 Enter the controller's IP address.
7 Select Telnet as the Connection Type.
8 Click the Logging option in the upper left corner of the left pane.
9 Select Printable output.
10 Select a location for the capture text file.
11 Click Open to start the session.
12 After Login:>, type: diagport
Press Enter.
13 To capture data receipts, after diagport>, type: mtcpip rx
Press Enter.
14 To capture data transmissions, after diagport>, type: mtcpip tx
Press Enter.

15 To capture more detailed diagnostic messages, after diagport>, type: mtcpip
vmsg
Press Enter.
16 To capture error messages, after diagport>, type: mtcpip emsg
Press Enter.
17 Verify the displayed text shows:
modbus reporting level status:
rx on
tx on
flush off
fc1 off
fc2 off
vmsg on
emsg on
off
If rx, tx, vmsg, or emsg show off, repeat the appropriate step (13, 14, 15, or 16)
to turn on capture of that item.
18 After diagport>, type: go
Press Enter.
19 Run the capture for one of the following periods of time:
○ If all microblock refresh times are one minute or less, run the capture for 5
minutes.
○ If any microblock refresh time is longer than 1 minute, run the capture for 5 times
the longest microblock refresh time.
20 Type: stop
Press Enter. Verify that you see diagport> before doing the next step.
21 After diagport>, type: logout
Press Enter.
22 To end the PuTTY session, click the X in the upper right corner.
23 In WebCTRL®, clear the Enable Telnet diagnostics checkbox (see steps 3 and 4),
then click OK.
24 Open the text file from the location you selected in step 11, and then verify that it
legibly shows the same information that PuTTY displayed.

Modbus Troubleshooting
The following troubleshooting information depends on whether your Automated Logic
controller is a master/client or a slave/server.
In most cases, a diagnostic capture can help determine the problem. See To capture
communication using … in the appropriate section of this document.

If the Automated Register addresses

Logic® controller Because Modbus register address formats differ from one manufacturer to another, the
is a Serial Master most common problems in a Modbus integration are caused by a microblock address
or Ethernet Client having an incorrect register address.
If the Automated Logic controller is a serial master or ethernet client, the register address
that you include in a microblock address is the register address that you want to read
from/write to in the slave/server. Microblocks support Modbus register addresses that
consist of a base register address (1–65535) and a one digit prefix (except coils) that
defines the type of value.

This type of value... Has the prefix... Example of register address

Discrete input 1 103459 or 13459
Input register 3 304564 or 34564
Holding register 4 401563 or 41563
Coil No prefix

Base address
Most manufacturers begin counting register addresses at 1; some begin at 0. Other than
contacting the manufacturer to get clarification, you can look at the register address list to
see if the addressing in any table starts at 0. If any table's addressing begins at 0, you
need to add 1 to each register address in order to read the right register. For example, if
you are given a register address of 40100, you must enter the address as 40101 to read
the correct register.

Prefix
Some manufacturers include the prefix in their register address. If you add another prefix,
you will have an invalid register address. For example, if the third-party manufacturer
shows a holding register address is 40123 and you add the prefix 4, your register address
will be 440123, which is an invalid address.

Errors
If the Properties page > Network Points tab shows errors, look for the error in the table
below. To see a more extensive list, go to the NET tree > the controller > Driver >
Protocols > Modbus Error Definitions.

Error code/message Possible solution(s)

Error ## - Modbus Where:
Exception Code - XXXX ## = a number from 51 to 61, and
XXXX = the exception code description
A server/slave device returns a Modbus Exception Code when
it cannot respond to the master/client. The most common are:
• ILLEGAL FUNCTION: The master/client sends an
unsupported function code to the slave/server. For
example, the master/client tries to query with function
code 16, which is not supported by the slave/server.
NOTE Some manufacturers do not support:
Function Code 15—Write Multiple Coils, or
Function Code 16—Write Multiple Registers
To resolve this, go to the NET tree > the controller > Driver
> Protocols > Modbus TCP/IP. Set Restrict coil and
register commands to Yes.
• ILLEGAL DATA ADDRESS: The master/client sends an
invalid register address to the slave/server. For example,
the master/client tries to read register 500, but the highest
register address is 100. To resolve this error, correct the
register address.
• ILLEGAL DATA VALUE: The master/client sends an invalid
value to the slave/server. For example, the master/client
tries to write a decimal value 150 to a Modbus Coil. To
resolve this error, change the value you are writing to a
value the register can accept.
Error 94 - Response Err Although rare, the Exception Code returned by the Modbus
– Invalid Exception slave/server device may be incorrect. Valid Exception Code
Code range is 1 to 11 (except 9). Use a diagnostic capture to
determine the invalid exception code. Then contact the
third-party manufacturer for a resolution.
Error 72 – Addr Err – See Register Addresses (page 38).
Invalid Register Number
Prefix

Error 73 – Addr Err –

Invalid Register Number
Range
Error 78 – Addr Err – You cannot have multiple ANO/BNO microblocks in the same
Invalid Duplicates controller write to the same address. If you have duplicates,
Found only one will be processed. Remove all duplicates, and then
download memory.
NOTE You can have multiple ANI/BNI microblocks read from
the same address.

Error code/message Possible solution(s)
Error 79 – Addr Err – This error indicates registers that share a common address.
Possible Overlapped For example:
Register Modbus://FLOAT/401000/58
Modbus://UINT/401001/58
In this example, the FLOAT register type uses two register
addresses, 1000 and 1001. So, the UINT's register address
overlaps the FLOAT's 1001 address. The last microblock
processed will get an error. To find the issue, the application
programmer should check the previous and next sequential
microblock register addresses.
Error 11 – Unable to Although rare, you may see this error if you have a large
allocate packet number of network points (more than 250) and most
microblocks have a Refresh Time of 10 seconds or less. To
resolve this, increase the Refresh Time on non-critical points.
Critical points can still be updated more frequently.
As described below, you can use diagnostic captures to
fine-tune your system to make the most of the available
bandwidth. See To capture communication using … in the
appropriate section of this document. Only turn on the vmsg
(verbose message) to see how the points are queried.
Serial Master
By looking at the capture, the engineer can follow how efficient
the query may be. Look at the bolded packets below. The
Master reads from device 58, Function Code 3 (Read Holding
Reg) and register address 1 through 3, for the total of 3
registers. This packet is repeated twice in sequence, which
may not be desirable. To resolve this, change the refresh time
of microblocks with register address 2 and 3 to 10 minutes (or
larger). Register addresses 2 and 3 will be read and updated
when register address 1 is read and will only trigger an update
if register address 1 is removed from the application. Observe
the capture and make sure that the repetition is resolved.
MODBUS<VM>READ Dev:58 - FC:3 - Reg:601 -> 603 - Qty:3
MODBUS<VM>READ Dev:58 - FC:3 - Reg:1 -> 3 - Qty:3
MODBUS<VM>READ Dev:58 - FC:3 - Reg:1 -> 3 - Qty:3
MODBUS<VM>READ Dev:58 - FC:3 - Reg:601 -> 603 - Qty:3
MODBUS<VM>READ Dev:58 - FC:3 - Reg:1 -> 3 - Qty:3
MODBUS<VM>READ Dev:58 - FC:3 - Reg:401 -> 406 - Qty:6
MODBUS<VM>READ Dev:58 - FC:4 - Reg:2001 -> 2009 - Qty:9
MODBUS<VM>READ Dev:58 - FC:4 - Reg:1001 -> 1009 - Qty:9
MODBUS<VM>READ Dev:58 - FC:4 - Reg:601 -> 603 - Qty:3
MODBUS<VM>READ Dev:58 - FC:4 - Reg:301 -> 306 - Qty:6
MODBUS<VM>READ Dev:58 - FC:4 - Reg:201 -> 206 - Qty:6
MODBUS<VM>READ Dev:58 - FC:4 - Reg:101 -> 103 - Qty:3
MODBUS<VM>READ Dev:58 - FC:4 - Reg:1 -> 3 - Qty:3

Error code/message Possible solution(s)
IP Client
Use the same techniques described above for the Serial
Master. Look at the bolded packets below. The client reads
from Device IP [Link] with device address 0. It
reads register 65532 through 65535 twice sequentially. To
resolve this, change the refresh time to 10 minutes (or larger)
for each microblock in the group except for the first microblock
with register address 65532. Register addresses 65533
through 65535 will be read and updated when register
address 65532 is read, and will only trigger an update if
register address 65532 is removed from the application.
MTCPIP<VM>Rx response ID:44
MTCPIP<VM>Rx response ID:45
MTCPIP<VM>READ Dev IP:[Link] - Addr:0 - FC:3 -
Reg:40009 -> 40016 - Qty:8 - ID:55
MTCPIP<VM>READ Dev IP:[Link] - Addr:0 - FC:3 -
Reg:40000 -> 40007 - Qty:8 - ID:56
MTCPIP<VM>READ Dev IP:[Link] - Addr:0 - FC:3 -
Reg:1 -> 12 - Qty:12 - ID:57
MTCPIP<VM>Rx response ID:46
MTCPIP<VM>Rx response ID:47
MTCPIP<VM>READ Dev IP:[Link] - Addr:0 - FC:2 -
Reg:65532 -> 65535 - Qty:4 - ID:58
MTCPIP<VM>READ Dev IP:[Link] - Addr:0 - FC:1 -
Reg:65532 -> 65535 - Qty:4 - ID:59
MTCPIP<VM>READ Dev IP:[Link] - Addr:0 - FC:1 -
Reg:65532 -> 65535 - Qty:4 - ID:60
MTCPIP<VM>Rx response ID:48
MTCPIP<VM>Rx response ID:49
Error 86 – Unable to The microblock value is not updating.
update point value Serial Master
In rare cases, the master may receive a valid response but
cannot match it to any microblock. The only way to determine
this is to review a diagnostic capture. To resolve, go to the
WebCTRL® NET tree > controller > Driver > Protocols >
Modbus page, and increase the Interpacket Delay. This
solution is not desirable if the controller's point count is high.
IP Client
Because Modbus TC/IP does not have a timeout defined, this
error may occur when the client communicates with a very slow
server. If a client microblock with a low refresh time (1 second)
sends a query every second but the server requires more than
2 seconds to respond, this error will be set on the microblocks
after a few cycles of queries. Get a diagnostic capture using
Wireshark to see the timing between query and response.
Increase the refresh time to allow the server to respond before
a new request is sent. This solution will slow communication
between the server and client controllers.

Error code/message Possible solution(s)
Error 40 – No response Serial Master
If the error is persistent, check the wiring, communication
baud rate, and device address.
If it is intermittent, go to the WebCTRL® NET tree > controller >
Driver > Protocols > Modbus page, and try changing the
following settings:
• Increase the Interpacket Delay in increments of 10 ms.
Maximum recommended is 100 ms, depending on the size
of control program. The bigger the control program is, the
smaller this setting should be.
• If the query reads multiple registers, try reducing the size of
Maximum Registers to Request. Use the diagnostics
capture to determine where the issue is most likely to
occur. If you need to reduce multiple registers, set the
Maximum Registers to Request and/or Maximum
Coils/DIs to Request to 1. You can optimize later if
needed.
• If the query writes to multiple registers, you may want to
inhibit multiple write altogether. Use the diagnostics
capture to determine where the issue is most likely to
occur. In most cases, the slave device is more susceptible
to multiple writes. To inhibit multiple registers writes, set
Restrict coil and register commands to Yes.
IP Client
TCP/IP communication is successful, but the Modbus packet
never gets a response from the Modbus server. Talk to the
third-party vendor to determine the reason the server is not
responding.
No microblock error, but FLOAT register types use 2 register addresses. The order in
a float value is not which they are processed differs from one manufacturer to
correct another. If you see incorrect float values, go to the NET tree >
the controller > Driver > Protocols > Modbus TCP/IP. Change
the value of the Reverse Float/32 Bit Integer field.
CAUTION This setting is applied globally for all float values in
the controller. If you have some float registers that are to be
processed one way and others that are to be processed the
other way, you must use separate master/client devices to talk
to them.

If the Automated Register addresses
Logic® controller If the Automated Logic controller is a slave/server, register addresses are 1-based, not
is a Serial Slave 0-based, and do not require any adjustment as long as the serial master or ethernet client
or Ethernet adheres to the Modbus protocol implementation described on the Modbus website
Server ([Link]).
If the Automated Logic controller is a slave/server, the register address that you include in
a microblock address is the register address that you want to expose to master/client.
Microblocks support Modbus register addresses that consist of a base register address
(1–65535) and a one digit prefix (except coils) that defines the type of value.

This type of value... Has the prefix... Example of register address

Discrete input 1 103459 or 13459
Input register 3 304564 or 34564
Holding register 4 401563 or 41563
Coil No prefix

Error code/message Possible solution(s)

Error 72 – Addr Err – Invalid See Register Addresses (page 43).
Register Number Prefix

Error 73 – Addr Err – Invalid

Register Number Range
Error 78 – Addr Err – Invalid Ensure all addresses are unique.
Duplicates Found
No microblock error, but the FLOAT register types use 2 register addresses. The order
value displayed at the in which they are processed differs from one
master/client is not correct manufacturer to another. If you see incorrect float
values, go to the NET tree > the controller > Driver >
Protocols > Modbus TCP/IP. Change the value of the
Reverse Float/32 Bit Integer field.

Appendix A - Upgrading an existing Modbus driver

CAUTION If you want to upgrade a system to the Modbus Combo driver, carefully
read the section below to determine if you should upgrade the driver.

Before you upgrade an existing Modbus driver

The Modbus Combo driver differs from previous Modbus drivers in the ways described in
the table below.
DO NOT UPGRADE an existing driver if you cannot do the following.

If your existing integration You must…

control program…
Uses abbreviated register Change the abbreviated (invalid) addresses to
addresses complete addresses. For example, change
modbus://UINT/123/1 to
modbus://UINT/40123/1.
Has multiple network output Reconfigure the control program. The Modbus
microblocks in the same controller Combo driver does not allow this situation.
writing to the same address
Uses the driver's IP Address Index table Replace the index number with the actual IP
for TCP/IP addresses address in the microblock addresses.
TIP Use Search/Replace on the Properties
page > Network Points tab to quickly modify
the microblock address.
Has hundreds of microblocks with Increase the refresh time for non-critical
the same refresh time in sequentially points. For more information, see Error 11 in
addressed registers the "Troubleshooting" section of the Modbus
Integration Guide.
Uses register addresses in the 1–9999 Do nothing. The Modbus Combo driver
range supports a wider range of addresses
(1–65535) but still supports the older address
format. As long as the register address
prefixes are correct (1 for discrete inputs, 3 for
input registers, or 4 for holding registers), the
driver will read the registers correctly.

To upgrade the Modbus driver

1 Back up your system.
2 Put the Modbus Combo driver in the
C:\WebCTRLx.x\webroot\<system_name>\drivers folder.
3 Select the Modbus Combo driver for your controller in the SiteBuilder or WebCTRL®
application.
4 Leave driver parameters at their default settings. You can adjust later if needed.

5 If your Automated Logic® controller is communicating Modbus TCP/IP through the
Ethernet port, go to the driver’s Modbus TCP/IP > Properties page and then choose
None Selected in the Communication Type field to properly close out the TCP/IP
connection for other Modbus devices.

6 Download memory to the controller.

7 On the WebCTRL NET tree > Properties page, see if any microblocks have an error.
These will typically be address errors. See "Troubleshooting" in the Modbus
Integration Guide to resolve address issues.
8 If your controller is communicating Modbus TCP/IP through the Ethernet port, do the
following:
a) On the driver’s Modbus TCP/IP > Properties page, select TCP/IP to start
communication.

b) Go back to the WebCTRL NET tree > Properties page and check for other errors.
Again, see "Troubleshooting" in the Modbus Integration Guide to resolve errors.

Appendix B - Modbus Protocol Conformance Statement
The following Modbus features and commands are supported by the Automated Logic®
Modbus drivers. See the Modbus website ([Link] for complete Modbus
protocol information.

Serial connection:

Modes RTU1
ASCII
Media type EIA-232
EIA-485, 2-wire1
EIA-485, 4-wire
Baud rate 1200 96001
2400 192001
4800 384001
Data bits 7
81
Parity None1
Odd
Even
Stop bits 11
2
1 Most commonly used value(s)

Ethernet connection:

Communication Type TCP/IP

Media Type Ethernet
Baud rate 10 Mbps/100 Mbps
Maximum TCP/IP 30 2
Connections
2 You may be able to connect more devices (256 maximum) if you consider the following:
• The lower the point count per device, the more devices you can connect.
• The more devices, the slower the communication between the Automated Logic® controller
and the Modbus devices.
A practical limit is approximately 100 devices. To connect more than 30 devices, change the
Close socket after each completed transaction setting in the driver.

Serial or Ethernet:

Function codes - command Register address range

01 - Read coils 1-65535
02 - Read discrete inputs 100001-165535
03 - Read holding registers 400001-465535
04 - Read input registers 300001-365535
05 - Write single coil
06 - Write single register
15 - Write multiple coils
16 - Write multiple registers

DIAG485 Technical Instructions
No ratings yet
DIAG485 Technical Instructions
10 pages
EIKON LogicBuilder v4 User Guide
No ratings yet
EIKON LogicBuilder v4 User Guide
36 pages
MultiCube M-Bus Communication Guide
No ratings yet
MultiCube M-Bus Communication Guide
27 pages
Interoperability of The WAGO IEC60870-5-101 and - 104 Protocol Library
No ratings yet
Interoperability of The WAGO IEC60870-5-101 and - 104 Protocol Library
18 pages
MR50-S3 Installation and Wiring Guide
No ratings yet
MR50-S3 Installation and Wiring Guide
6 pages
Eikon 3.02 Microblock Reference
No ratings yet
Eikon 3.02 Microblock Reference
372 pages
DAP III Modbus Integration Guide
No ratings yet
DAP III Modbus Integration Guide
12 pages
Diag 485
No ratings yet
Diag 485
7 pages
InteliGen 500 G2 Modbus Overview
No ratings yet
InteliGen 500 G2 Modbus Overview
12 pages
EIKON v8.0 User Manual Overview
No ratings yet
EIKON v8.0 User Manual Overview
42 pages
C6/C6M Modbus Controller Manual
No ratings yet
C6/C6M Modbus Controller Manual
32 pages
EIKON v7.0 User Manual Guide
No ratings yet
EIKON v7.0 User Manual Guide
46 pages
OptiFlex OFHI CS
No ratings yet
OptiFlex OFHI CS
2 pages
FAN 410 Rev 4.6
No ratings yet
FAN 410 Rev 4.6
366 pages
PowerFlex 750-Series - Accessing Parameters Over Modbus RTU
No ratings yet
PowerFlex 750-Series - Accessing Parameters Over Modbus RTU
3 pages
FRENIC MEGA Servo Function Codes
100% (1)
FRENIC MEGA Servo Function Codes
19 pages
WebCTRL License Upgrade Overview
No ratings yet
WebCTRL License Upgrade Overview
6 pages
MT LevelSensing Control-7.21 PDF
No ratings yet
MT LevelSensing Control-7.21 PDF
12 pages
EBO External Log Storage Installer Guide
No ratings yet
EBO External Log Storage Installer Guide
13 pages
Setpointps Configuration Software: Programming Manual
No ratings yet
Setpointps Configuration Software: Programming Manual
98 pages
Danfoss FC102 Modbus Register Overview
No ratings yet
Danfoss FC102 Modbus Register Overview
89 pages
RTU560 23BE40 Connections Guide
No ratings yet
RTU560 23BE40 Connections Guide
9 pages
BMS Upgrade Tool User Manual V1.0.0
No ratings yet
BMS Upgrade Tool User Manual V1.0.0
5 pages
Scadapack 4203 DR
No ratings yet
Scadapack 4203 DR
92 pages
EIKON LogicBuilder v5 User Manual
No ratings yet
EIKON LogicBuilder v5 User Manual
44 pages
User Archives Control V 7
No ratings yet
User Archives Control V 7
38 pages
ME812u Controller Series: Power Ful, Multi-Equipment Controllers
No ratings yet
ME812u Controller Series: Power Ful, Multi-Equipment Controllers
2 pages
IQL Controller Setup via 3xtend Guide
100% (1)
IQL Controller Setup via 3xtend Guide
9 pages
Modbus Address Mapping for Mk5 Controller
No ratings yet
Modbus Address Mapping for Mk5 Controller
7 pages
852-303 Wago User Manual
No ratings yet
852-303 Wago User Manual
338 pages
ION Setup Device Configuration Guide 70002-0293-03
No ratings yet
ION Setup Device Configuration Guide 70002-0293-03
68 pages
SE8000 Firmware Upgrade Guide
No ratings yet
SE8000 Firmware Upgrade Guide
4 pages
BCSoft Software Installation Guide
No ratings yet
BCSoft Software Installation Guide
31 pages
SCADAPack 4000 Series Transmitters
No ratings yet
SCADAPack 4000 Series Transmitters
106 pages
CXproHD Training Completion Certificate
No ratings yet
CXproHD Training Completion Certificate
1 page
RSPRO
No ratings yet
RSPRO
14 pages
Concept XXMIT - RTXMIT Transmit (Receive) Function Block
No ratings yet
Concept XXMIT - RTXMIT Transmit (Receive) Function Block
110 pages
ME812u Controller: Technical Instructions
0% (1)
ME812u Controller: Technical Instructions
39 pages
1769-If4I Analog Input Module
No ratings yet
1769-If4I Analog Input Module
24 pages
GDP 300 Operation and Configuration Manual
No ratings yet
GDP 300 Operation and Configuration Manual
146 pages
Hirolink SMM Service Manual Overview
No ratings yet
Hirolink SMM Service Manual Overview
17 pages
FMBT-21 Modbus/TCP User Manual
No ratings yet
FMBT-21 Modbus/TCP User Manual
110 pages
Lgr25, Lgr250, & Lgr1000: High-Speed Bacnet Routing & Integration
No ratings yet
Lgr25, Lgr250, & Lgr1000: High-Speed Bacnet Routing & Integration
2 pages
Aermec Modbus Communication Guide
100% (1)
Aermec Modbus Communication Guide
10 pages
First Configuration Guide for ClearSCADA
No ratings yet
First Configuration Guide for ClearSCADA
38 pages
Modbus RTU Protocol for Modu_Control Board
No ratings yet
Modbus RTU Protocol for Modu_Control Board
14 pages
Model RFT9712
No ratings yet
Model RFT9712
57 pages
SIMATIC IPC 477E 15" Touch Data Sheet
No ratings yet
SIMATIC IPC 477E 15" Touch Data Sheet
3 pages
Modbus RTU Protocol Installation Guide
No ratings yet
Modbus RTU Protocol Installation Guide
18 pages
InteliGen 1000 Controller Datasheet
No ratings yet
InteliGen 1000 Controller Datasheet
6 pages
C3FT30 Eng
No ratings yet
C3FT30 Eng
373 pages
SDMO APM802 Modbus User Manual
No ratings yet
SDMO APM802 Modbus User Manual
36 pages
Trane Tracer Graphics Editor
No ratings yet
Trane Tracer Graphics Editor
140 pages
STT04 Abb Manual PDF
No ratings yet
STT04 Abb Manual PDF
285 pages
Modbus RTU Register Variables Table
No ratings yet
Modbus RTU Register Variables Table
7 pages
CPU 313C-2DP Communication Setup Guide
No ratings yet
CPU 313C-2DP Communication Setup Guide
4 pages
Modbus Integration Guide
100% (1)
Modbus Integration Guide
51 pages
25TRGEXT000054 Introduction To Interfaces v5
No ratings yet
25TRGEXT000054 Introduction To Interfaces v5
25 pages
DMSView User Guide From 2.3. General Availability - 120206
No ratings yet
DMSView User Guide From 2.3. General Availability - 120206
687 pages
PowerStoreOS 2.1.1.2 Release Notes
No ratings yet
PowerStoreOS 2.1.1.2 Release Notes
21 pages
I2C and SPI in IoT Systems
100% (1)
I2C and SPI in IoT Systems
17 pages
Managing Congestion: Qos Congestion Management and Avoidance
No ratings yet
Managing Congestion: Qos Congestion Management and Avoidance
27 pages
Overview of Routing Information Protocol
No ratings yet
Overview of Routing Information Protocol
1 page
Cyber Security Training Essentials
No ratings yet
Cyber Security Training Essentials
9 pages
Mobile Originated SMS Call Flow
No ratings yet
Mobile Originated SMS Call Flow
3 pages
Diseño Lógico de Red con Switches y Routers
No ratings yet
Diseño Lógico de Red con Switches y Routers
3 pages
BGP Attributes and Path Selection Guide
No ratings yet
BGP Attributes and Path Selection Guide
63 pages
IP Addressing Scheme for 400 Devices
No ratings yet
IP Addressing Scheme for 400 Devices
2 pages
Unit 2 WSN
No ratings yet
Unit 2 WSN
12 pages
Transitioning from OpenBGPD to BIRD
No ratings yet
Transitioning from OpenBGPD to BIRD
24 pages
DROPS: Secure Cloud Data Management
No ratings yet
DROPS: Secure Cloud Data Management
5 pages
SNMPv2 Overview and Key Features
No ratings yet
SNMPv2 Overview and Key Features
35 pages
IoT Fundamentals and Applications
No ratings yet
IoT Fundamentals and Applications
115 pages
Orion IP SLA Manager
No ratings yet
Orion IP SLA Manager
3 pages
Cloud Computing: Benefits, Models & Challenges
No ratings yet
Cloud Computing: Benefits, Models & Challenges
10 pages
Information Security Goals and Attacks
No ratings yet
Information Security Goals and Attacks
48 pages
TANGRAM GT41W IP Processing Module
No ratings yet
TANGRAM GT41W IP Processing Module
2 pages
Proxy Server Project Overview
No ratings yet
Proxy Server Project Overview
163 pages
Introduction to Cyber Security Concepts
No ratings yet
Introduction to Cyber Security Concepts
272 pages
Xirrus Wi-Fi Inspector User Guide
No ratings yet
Xirrus Wi-Fi Inspector User Guide
8 pages
Nokia Small Cell Portfolio Update 2023
100% (1)
Nokia Small Cell Portfolio Update 2023
47 pages
Flytec Computers Price List 01/13
No ratings yet
Flytec Computers Price List 01/13
65 pages
S1104309GC10 AA Lab09
No ratings yet
S1104309GC10 AA Lab09
18 pages
Installing Openfiler on CentOS 6.5
No ratings yet
Installing Openfiler on CentOS 6.5
12 pages
CCNP/CCIE DCCOR 350-601 Training Guide
No ratings yet
CCNP/CCIE DCCOR 350-601 Training Guide
80 pages
Cloud Computing Exam Questions Guide
No ratings yet
Cloud Computing Exam Questions Guide
2 pages
AAA Concepts and Quiz Questions
No ratings yet
AAA Concepts and Quiz Questions
3 pages

Modbus Integration Guide

Uploaded by

Modbus Integration Guide

Uploaded by

Modbus Integration Guide

For an LGR line, ME-LGR line, or ME812u-LGR controller

If the Automated ...on this ...you can use See...

Modbus Integration Guide • Rev. 6/28/2012 1 © 2012 Automated Logic Corporation

Modbus Integration Guide • Rev. 6/28/2012 2 © 2012 Automated Logic Corporation

Formatting a Modbus address

Address format: protocol://register type/modbus register address/device address

See Defined by Provided in third- Set on third-party

If the point is in a Modbus device connected Use the following protocol

Modbus Integration Guide • Rev. 6/28/2012 3 © 2012 Automated Logic Corporation

To... this kind of use this with this and a Modbus

Modbus Integration Guide • Rev. 6/28/2012 4 © 2012 Automated Logic Corporation

Editing a microblock address

Modbus Integration Guide • Rev. 6/28/2012 5 © 2012 Automated Logic Corporation

3 Connect the Wiring specifications

To wire a third-party device

Modbus Integration Guide • Rev. 6/28/2012 6 © 2012 Automated Logic Corporation

Modbus Integration Guide • Rev. 6/28/2012 7 © 2012 Automated Logic Corporation

Select... If the Modbus point addresses

Modbus Integration Guide • Rev. 6/28/2012 8 © 2012 Automated Logic Corporation

Modbus Integration Guide • Rev. 6/28/2012 9 © 2012 Automated Logic Corporation

Modbus Integration Guide • Rev. 6/28/2012 10 © 2012 Automated Logic Corporation

Modbus Integration Guide • Rev. 6/28/2012 11 © 2012 Automated Logic Corporation

Modbus Integration Guide • Rev. 6/28/2012 12 © 2012 Automated Logic Corporation

Address format: protocol://register type/modbus register address

See Defined by Assigned by you.

If the Modbus master is connected Use this protocol signature

Register type/Register address

Modbus Integration Guide • Rev. 6/28/2012 13 © 2012 Automated Logic Corporation

Modbus Integration Guide • Rev. 6/28/2012 14 © 2012 Automated Logic Corporation

2 Download the 1 Go to the website [Link] then select

3 Connect the Wiring specifications

Modbus Integration Guide • Rev. 6/28/2012 15 © 2012 Automated Logic Corporation

Modbus Integration Guide • Rev. 6/28/2012 16 © 2012 Automated Logic Corporation

Select... If the Modbus point addresses

Modbus Integration Guide • Rev. 6/28/2012 17 © 2012 Automated Logic Corporation

Modbus Integration Guide • Rev. 6/28/2012 18 © 2012 Automated Logic Corporation

Modbus Integration Guide • Rev. 6/28/2012 19 © 2012 Automated Logic Corporation

Modbus Integration Guide • Rev. 6/28/2012 20 © 2012 Automated Logic Corporation

Modbus Integration Guide • Rev. 6/28/2012 21 © 2012 Automated Logic Corporation

Formatting a Modbus address

mtcpip://register type/modbus register address/unit ID/IP address

Defined by Provided in third- Set on the IP address of

If the register address is in... the Unit ID is...

Modbus Integration Guide • Rev. 6/28/2012 22 © 2012 Automated Logic Corporation

To... this kind of use this with this and a Modbus

Modbus Integration Guide • Rev. 6/28/2012 23 © 2012 Automated Logic Corporation

Editing a microblock address

Modbus Integration Guide • Rev. 6/28/2012 24 © 2012 Automated Logic Corporation

1 Turn off the Automated Logic® controller's power.

Modbus Integration Guide • Rev. 6/28/2012 25 © 2012 Automated Logic Corporation

Modbus Integration Guide • Rev. 6/28/2012 26 © 2012 Automated Logic Corporation

To capture communication using Wireshark

1 Download the latest version of Wireshark from the Wireshark website

Modbus Integration Guide • Rev. 6/28/2012 27 © 2012 Automated Logic Corporation

To capture communication using PuTTY

Modbus Integration Guide • Rev. 6/28/2012 28 © 2012 Automated Logic Corporation

Modbus Integration Guide • Rev. 6/28/2012 29 © 2012 Automated Logic Corporation

Modbus Integration Guide • Rev. 6/28/2012 30 © 2012 Automated Logic Corporation

Formatting a Modbus address

Defined by Provided in third-

Register type/Register address

Modbus Integration Guide • Rev. 6/28/2012 31 © 2012 Automated Logic Corporation

Editing a microblock address

Modbus Integration Guide • Rev. 6/28/2012 32 © 2012 Automated Logic Corporation

1 Turn off the Automated Logic® controller's power.

Modbus Integration Guide • Rev. 6/28/2012 33 © 2012 Automated Logic Corporation

Modbus Integration Guide • Rev. 6/28/2012 34 © 2012 Automated Logic Corporation

To capture communication using Wireshark

1 Download the latest version of Wireshark from the Wireshark website

Modbus Integration Guide • Rev. 6/28/2012 35 © 2012 Automated Logic Corporation

To capture communication using PuTTY

Modbus Integration Guide • Rev. 6/28/2012 36 © 2012 Automated Logic Corporation

Modbus Integration Guide • Rev. 6/28/2012 37 © 2012 Automated Logic Corporation

If the Automated Register addresses

This type of value... Has the prefix... Example of register address