ADAM Modbus Device
ADAM Modbus Device
ADAM Modbus Device
Table of Contents
1. Introduction 3
1.1 Overview............................................................................................................... 3
1.1.1 Modbus Protocol ......................................................................................... 3
1.1.2 ADAM Modbus Device Driver................................................................... 3
1.2 Support List........................................................................................................... 4
1.3 Requirements......................................................................................................... 5
1.3.1 ADAM Utility ............................................................................................. 5
1.3.2 Wiring and Cabling..................................................................................... 5
1.3.3 Reference Manual ....................................................................................... 6
2. Hardware Configuration 7
2.1 ADAM-5000/485 Series ....................................................................................... 7
2.2 ADAM-5000/TCP Series ...................................................................................... 8
2.3 ADAM-5510 Series ............................................................................................ 13
2.3.1 Run Modbus RTU..................................................................................... 14
2.3.2 Run Modbus Ethernet ............................................................................... 16
2.4 ADAM-6000 Series ............................................................................................ 20
3. Software Configuration 21
3.1 ADAM-5000/485 Series ..................................................................................... 21
3.2 ADAM-5000/TCP Series .................................................................................... 22
3.3 ADAM-5510 Series ............................................................................................ 22
3.4 ADAM-6000 Series ............................................................................................ 23
4. Example 24
1. Introduction
1.1 Overview
Modbus is a "De-facto" standard for communications especially for connection of SCADA and
HMI systems to intelligent operator panels, PLCs and controllers.
Modbus is an "open" communications protocol designed for industrial control and monitoring
applications.
Many Automation Control Devices support the Modbus protocol in both Serial Modbus
RTU/ASCII and Modbus Ethernet.
Via these protocols, PLC, Single Loop and Multi-Loop Controllers, RTU, DCS, computers, shop
floor operator panels and other devices can communicate throughout plants and substations.
Advantech WebAccess SCADA Node provides a Modbus master interface using Modbus RTU or
Modbus Ethernet protocol for communicating with Modbus slave devices. With ADAMModbus
Device Driver, many Advantech ADAM modules can connect with Advantech WebAccess
conveniently.
Modbus ASCII
In Modbus ASCII, each byte(8-bit) in a message is sent as two ASCII characters. The main
advantage is that it allows up to one second time interval between characters without causing an
error.
Modbus RTU
This is the default protocol of the Advantech WebAccess ADAM Modbus serial device driver. In
Modbus RTU, each byte(8-bit) in a message, contains two 4-bit hexadecimal characters. The main
advantage of Modbus RTU is its greater character density allows better data throughput than
Modbus ASCII at the same baud rate.
Advantech WebAccess can scan every 100 milliseconds over serial connections limited only by
the PLC, Controller or RTU and the connection.
Most modern Modbus serial devices use Modbus RTU, including Advantech ADAM modules.
Modbus Ethernet
Modbus Ethernet network is a single master, multi-drop network, which supports up to 247 slave
devices.
The preferred physical layer for the Modbus Ethernet network is TCP/IP over Ethernet, although
any TCP/IP network connection is supported including the Internet, WANs and LANs.
A single IP address can support up to 255 devices. Serial communications can be "encapsulated"
into TCP/IP packets using Modbus Serial-to-Ethernet gateways.
You can use ADAM Modbus Device Driver when connect ADAM modules and Advantech
WebAccess software by serial or Ethernet. But not all ADAM modules support Modbus Protocol
especially the early ones. You can get the support list from Advantech Application Engineer or log
onto Advantech website for more information. Part of the support list is available in the following
chapter.
Note: Modbus ASCII is not supported by most ADAM modules at present, Modbus RTU is
the default for serial device.
1.3 Requirements
Some ADAM utilities can be used to configure ADAM modules in Advantech WebAccess
software. Log onto Advantech website at http://www.advantech.com.cn/Support/index-1.asp to get
these utilities.
The Modbus protocol allows standard RS-232 and RS-485 communication formats.
The cable type is device and application-specific. Refer to the hardware manuals for proper
cabling requirement.
Under most circumstances, you can use RS-232 straight-through cable to connect ADAM modules
and computer. But when configure ADAM5510KW series modules with ADAM-4000-5000 utility,
please use RS232 cross-over cable. When connect PC and ADAM modules with RS-485, please
use RS-232 straight-through cable to connect PC and ADAM-4520(RS232 to RS422/RS-485
converter).
1 1
2 2
3 3
4 4
5 5
6 6
7 7
8 8
The following manuals provide information on configuration of ADAM modules and Advantech
WebAccess via Modbus Protocol:
z ADAM 5000-485 7.1th.pdf
z ADAM 5000TCP 3rd.pdf
z ADAM-5510KW Series Manual Ed-1.1.pdf
z ADAM-6000 series Manual pdf file (Depend on which module you need)
Log onto our website at http://www.advantech.com.cn/Support/index-1.asp for download
2. Hardware Configuration
2.1 ADAM-5000/485 Series
COM Port
Straight-through cable
RS-232
Before searching the ADAM module with ADAM-4000-5000 utility, please initialize the settings,
set switches No.1-NO.7 in Node ID to OFF, and NO.8 to ON as follows:
Then, you can set the ADAM module Address from 1 to 255 by setting Node ID switches
NO.1-NO.7 and keep NO.8 to OFF, search ADAM modules again, you will see as follows, and
you can test the modules in each slot.
When apply ADAM-5000/TCP Series modules in Advantech WebAccess, you can use a
cross-over Ethernet cable to initialize device with ADAM-5000TCP/6000 utility.
Note:
1. Close host PC windows Firewall before using ADAM-5000TCP/6000 utility, or set
ADAM-5000TCP/6000 utility as the exception in the Firewall.
2. Set your host PC to static IP address.
When you apply ADAM-5510 Series modules in Advantech WebAccess, use a cross-over RS-232
cable to test device with ADAM-4000-5000 utility.
Before testing ADAM-5510 modules, please set NODE ID at first: SW1, SW6, SW7, and SW8 to
ON, others to OFF. Be sure to use ADAM 5510 module's COM1 Port with RS-232.
In this utility, ADAM-5510 module will be shown as 5000/E module, as follows (use
ADAM-5510EKW/TP for example):
ADAM-5510 Series modules run Modbus RTU by serial port should be configured as follows
(please refer to relative manuals for information on how to build ADAM-5510 project in KW
MULTIPROG ). Here, you should set NODE ID as: SW1 to ON, others to OFF. Use a cross-over
RS-232 cable to connect ADAM-5510 module COM1 port with host PC.
Then, you can configure Advantech WebAccess with Modbus RTU protocol.
ADAM-5510 modules, such as ADAM-5510EKW/TP module have Ethernet Port support Modbus
Ethernet, you can configure these devices as follows.
Firstly, configure TCP/IP protocol by ADAM-5510 Series Utility. Use a straight-through RS-232
cable to connect host PC and ADAM-5510 module COM3 port. Set NODE ID as: SW1 to ON,
others to OFF.
You can configure ADAM-6000 Series the same with ADAM-5000/TCP, with the same
ADAM-5000TCP/6000 Utility, but when you connect ADAM-6500/6501 modules which run
WinCE OS, you should use uScope Utility to configure them. For details, please refer to
ADAM-6000 Series manual.
3. Software Configuration
The main problem of setting ADAM modules with Advantech WebAccess is the communication
settings; we will show details in the following chapters. For ADAM AI/AO module, it is necessary
to change Modbus data to real data. The calculation formula is as follows:
1. ADAM AI module
Modbus data precision in ADAM AI module is 65536(2^16), so if you select the AI input range as
±10V, the conversion of data is as follows:
Real =Modbus Data/65535*(Max. value- Min. value)+ Min.
Note: all these values are signed value
2. ADAM AO module
Modbus data precision in ADAM AO module is 4096(2^12), so if you select the AO output range
as 0~10V, the conversion of data is as follows,
Real =Modbus Data/4095*(Max. value- Min. value)+ Min.
Note: all these values are signed value
There is nothing special about ADAM-5000/485 Series module communication settings, you can
just set it as normal, make sure the serial port is corresponding to real COM port in host PC, and
the ADAM device ID is correctly set, the NODE ID should be set as (if the device ID is set as 1):
Only SW1 to ON, others to OFF.
There is nothing special about ADAM-5000/485 Series module communication settings, you can
just set it as normal, and you can set any communication port as TCP/IP interface which isn't
relative with TCP/IP real port, just as we can set any communication port to run TCP/IP. Be sure
the device property is correctly set and the default Modbus Ethernet communication port is set to
"502". About NODE ID settings, please refer to ADAM-5000/485 series.
ADAM-5510 series Modbus RTU and Modbus Ethernet settings are different from ADAM-5000
series, especially for ADAM-5510KW/EKW/TP. When configure ADAM-5510 series with
Advantech WebAccess, you should specially set Node ID as follows:
SW1-SW5 set as Device ID, setting SW1 to ON to represent Device No.1, setting SW6 to ON,
SW7-SW8 to OFF to represent using ADAM-5510 module COM1 port with a baud rate of 9600
bps. Please refer to user manual for details.
About the device and TCP/IP setting, please refer to ADAM-5000 series.
You can set ADAM-6000 Series as the ADAM-5000/TCP, please refer to that chapter.
4. Example
Here we take ADAM-5000/TCP as example to show the whole configuration process.
Step 1, set a new project in project Node as follows,
Fig. 4.8 Change Tag value of some ADAM module by its utility
Following the above example, you can set up an Advantech WebAccess project running ADAM
modules easily and conveniently!