Controlinc Network Master
Model M124 Version 3.1
Installation and Operations Manual
VCIOM-17039-EN Rev. 0
April 2022
Notes
April 2022
Installation and Operations Manual
VCIOM-17039-EN Rev. 0
This page intentionally left blank
Installation and Operations Manual
VCIOM-17039-EN Rev. 0
Table of Contents
Section 1: Introduction
1.1 Reference Documents ................................................................................... 1
1.2 System Conguration ................................................................................... 2
1.3 General System Specications ....................................................................... 4
1.3.1 Environmental .................................................................................... 4
1.3.2 Electrical ............................................................................................ 4
1.3.3 LCD Touch Panel Specications ........................................................... 4
1.3.4 M124 PLC Port 2 Setup for Database Exchange Link (DxL) ................... 5
1.4 Parts List ....................................................................................................... 7
Section 2: Installation
2.1 Mounting ...................................................................................................... 8
2.1.1 Rack Mount ...................................................................................... 10
2.2 Power Input ................................................................................................ 11
2.3 Field Network Wiring .................................................................................. 11
2.3.1 Network Grounding ......................................................................... 12
2.3.2 Network Termination ....................................................................... 13
2.4 Modbus Host Cables ................................................................................... 13
Table of Contents
April 2022
Section 3: Conguring the System
3.1 System Protection and Software Versions ................................................... 14
3.1.1 Password Protection ......................................................................... 14
3.1.2 CoProcessor Software Protection ..................................................... 14
3.1.3 Software Version Identication ........................................................14
3.2 Selecting Diagnostic/Programming Mode ................................................... 15
3.3 Chassis Identication and Hot Standby ........................................................ 15
3.4 Conguring Modbus Host Port Interface(s) ................................................. 15
3.5 Conguring the Field Network .................................................................... 15
3.5.1 Conguring the Number of Slaves .................................................... 15
3.5.2 Conguring Field Network Baud Rate ............................................... 15
3.5.3 Conguring Network Master Receiver Time-Out ............................... 16
3.5.4 Conguring Report-By-Exception (RBE) ............................................ 16
3.6 Conguring Network Address Sequence ..................................................... 16
3.7 Conguring Device Types ............................................................................ 17
Table of Contents
i
Table of Contents
April 2022
Section 4: Modbus Register Maps
Installation and Operations Manual
VCIOM-17039-EN Rev. 0
4.1 Valve Status and Command Registers per Modbus Function Code ............... 18
4.2 Valve Status Bit Data for Each Valve ............................................................. 19
4.2.1 Multiple Valve Status Locations Using Function Code 02 ................... 20
4.2.2 Multiple Valve Status Data Using Modbus Function Code 03 ............. 20
4.2.3 Multiple Valve Status Data Using Modbus Function Code 04 ............. 21
4.3 Reading Valve Position and Setpoint ............................................................ 21
4.4 Writing Analog Valve Position Setpoint (Function Codes 06 and 16) ............ 22
4.5 Writing Discrete Commands to Valve Actuators .......................................... 22
4.6 Reading Auxiliary Analog Inputs Using Function Code 03 ............................ 23
4.6.1 Reading Torque Analog Input Using Function Code 03 ...................... 23
4.7 Reading and Writing Auxiliary Analog Outputs ............................................ 23
4.8 Reading User Discrete Inputs ....................................................................... 23
4.9 Writing User Relay Outputs (MRTU Support) ............................................... 24
4.10 System Status Word .................................................................................... 25
4.11 Combined System Alarms ........................................................................... 26
4.12 Network Fault Location ............................................................................... 26
4.13 M124 Global Database and Modbus Holding Register Map .......................... 26
Section 5: Theory of Operation
5.1 Valve Actuator Network Connections .......................................................... 30
5.2 Power-up Initialization ................................................................................. 30
5.3 Hot Standby Fail-Over ................................................................................. 31
5.3.1 Modbus Host Link and Fail-Over ........................................................ 31
5.4 Network Fault Detection ............................................................................. 32
5.5 Polling Process ............................................................................................ 32
5.6 Report-by-Exception ................................................................................... 32
5.7 Priority Scan ................................................................................................ 33
5.8 Writing Discrete Commands to Valve Actuators .......................................... 33
5.9 Writing Position Setpoint ............................................................................ 33
5.10 Writing Analog Outputs .............................................................................. 33
5.11 Writing User Relay Outputs ......................................................................... 34
5.12 Writing ESD Command ............................................................................... 34
Section 6: Software Source Code
6.1 Host Database Conguration Aid ................................................................ 35
Section 7: LCD Touch Panel Backup
Terminal Operation
7.1 Home Screen ..............................................................................................36
7.1.1 Alarm Display ................................................................................... 37
7.1.2 Security Codes Screen ...................................................................... 37
7.1.3 ESD Screen ....................................................................................... 38
7.1.4 Switch Active Master to Standby Screen ...........................................39
7.2 Valve Control and Status Display ................................................................. 40
7.2.1 Valve Control .................................................................................... 41
7.2.2 Navigation Buttons ...........................................................................41
ii
Table of Contents
Installation and Operations Manual
VCIOM-17039-EN Rev. 0 April 2022
Section 1: Introduction
Section 1: Introduction
Emerson Controlinc Network Masters are the master of Emerson Controlinc valve actuator networks
with Modbus RTU protocol. The system provides network management, data concentration, and
protocol conversion, off-loading the host system of these tasks. This enhances overall system
performance and minimizes software development and system conguration tasks by the system
integrator. The Network Master serves as the master of a master/slave network. It manages the
network by keeping an orderly cycle of data transfers to and from the slave devices (valve actuators).
It handles error detection, alarming, and network recovery. The Network Master serves as a data
concentrator for the host by providing a common database for all slave devices. The host is required
to communicate with only one slave device (network master) for all data transfers to and from the
eld. Data can be transferred between the network master and host in large blocks at a much higher
communications rate than would be possible if the host communicated with each slave device
(valve actuator) on the eld network. The Network Master acquires data from the valve actuators
by polling or scanning each device in a sequence of slave address from a table called a scan list.
Polling is a process of the Network Master sending to each slave address, a command to return
its status information, including alarms, discrete and analog inputs and outputs. When control
commands (valve open, stop, close, position setpoint, etc.) are generated by a host system up-line
of the Network Master, it then sends the appropriate commands over the network to the addressed
slave device. A more detailed functional description of operation is provided in the Theory of
Operation section of this manual.
1.1 Reference Documents
In addition to this Controlinc Network Master Operations Manual, the following references are
required for proper installation, conguration, and operation of the Network Master. All reference
documents are supplied with the system. Paragraph numbers, as listed below, are used for reference
to these documents in this manual.
1. EIM TEC2000 Installation and Operations Manual E2K-405-0703
2. Bettis XTE3000 Electric Actuator IOM
3. FACTS Engineering 205 Basic CoProcessor User’s Manual
4. FACTS Extended BASIC Reference Manual
5. Direct Logic DL205 User Manual
All manuals and software are provided in electronic format with the system on CD.
Introduction
1
Section 1: Introduction
April 2022
1.2 System Conguration
Controlinc Network Master Model M124 contains redundant valve actuator network masters in a
single enclosure. M124 supports one Controlinc E>Net ring network with up to 124 valve actuators.
The system uses standard RS485 and Modbus RTU protocol.
Redundant systems consist of two identical chassis with identical software. One is the primary master
and the other a hot standby master. The two chassis may switch roles of primary and hot standby at
any time. Figure 1 shows the specic system conguration of the supplied system. Version 1.0 and
later communicate with DCM 320B valve actuators with Version 1.0 or later rmware that control
both block valves (Open, Stop, Close) and modulating or positioner type valves. The system consists
of two six-slot chassis with each chassis having a central processor located in Slot 0, which provides a
global database for the CoProcessors installed the chassis. The central processor also performs such
functions as watchdog timers and system alarm generation for the CoProcessors. It also provides
interrupt control for fast data transfers between processor modules.
Each chassis consists of two Modbus Slave modules located in Slots 3 and 4. These slave modules
communicate with a redundant Modbus host systems up line. The CoProcessor installed in Slot 1 is
the Controlinc Network Master to a ring eld network. Two ports of the Network Master module are
connected to Network Interface Module (NIM) Model M124I with redundant, isolated ports. Each
NIM has connections to the redundant Network Master modules of the redundant chassis. Any one
of the four ports may acquire data from and control all actuators in the eld in either direction
around the network. Multiple M124 systems may be networked from a single host or redundant
hosts to automate any size system form a few valves to thousands of valves covering a large
network area. Ten (10) independent processors ensure full redundancy of all functions in a single
unit. All components except display are redundant with double-redundant host links to redundant
hosts and automatic processor hot swapping. Host equipment is not required to implement any
fail-over logic. Full-time redundant Modbus host links are standard. Plug-in modular construction
and DIN-rail mounting of components ensure minimum MTR, minimizing down time. LCD screen
and keypad provide valve actuator monitor and control of all valves in case redundant host links fail.
All valve status and alarms may be displayed by the LCD terminal for maintenance purposes.
The LCD terminal is a valuable troubleshooting tool during system commissioning. A more detailed
description of operation is provided in the Theory of Operation section of this manual.
Installation and Operations Manual
VCIOM-17039-EN Rev. 0
2
Introduction
Installation and Operations Manual
VCIOM-17039-EN Rev. 0 April 2022
Figure 1 Model M124 Valve Control System
Section 1: Introduction
HOST 1
HOST 2
Host 1 NIM TCP Host 2
M124
Primary
Master
M124
Secondary
Master
A NIM 124I B
Controlinc
E>Net Ring
Network
Modbus TCP/IP Ethernet
Links 10/100 BaseT
RS232 Modbus RTU
Links at 115.2K baud
NEMA Enclosure
with LCD Touch Panel
124
Actuators
per Network
Introduction
3
Section 1: Introduction
April 2022
Installation and Operations Manual
1.3 General System Specications
1.3.1 Environmental
Storage temperature: -20 °C to 70 °C
Ambient operating temperature: 0 °C to 55 °C
Ambient humidity: 5 to 95% (non-condensing)
Vibration resistance: MIL STD 810C, Method 514.2
Shock resistance: MIL STD 810C, Method 516.2
1.3.2 Electrical
Standard input voltage: 117 V AC at 50/60 Hz (100 - 240 V AC)
(other options available)
Total current at nominal voltage: 0.65 A (includes LCD panel)
Maximum inrush current: 60 A
Total power consumption: 25 VA nominal (includes LCD)
Isolation resistance: >10 MΩ at 500 V DC
Dielectric withstand voltage: 1500 V AC at 1 min.
VCIOM-17039-EN Rev. 0
1.3.3 LCD Touch Panel Specications
Display type: 5.7 in. diagonal color TFT
Enclosure: NEMA 4 (IP65)
Input voltage: 12 - 24 V DC
Power consumption: 16.0 W, 1.30 A at 12 V DC, 0.66 A at 24 V DC
Operating temp: 0 °C to 50 °C
4
Introduction
Installation and Operations Manual
VCIOM-17039-EN Rev. 0 April 2022
Section 1: Introduction
1.3.4 M124 PLC Port 2 Setup for Database Exchange Link (DxL)
Primary Master Secondary Master
DirectNet DirectNet
Base Timeout x 1 Base Timeout x 1
RTS/CTS 0 mS, 0 mS RTS/CTS 0 mS, 0 mS
Station Address 2 Station Address 1
38400, 1, Odd, Hex 38400, 1, Odd, Hex
PLC to PLC cable is RS232, 3-wire, rolled, with 15-pin D connectors
Primary Secondary
Pin/Wire Pin/Wire
2 Red 3 Red
3 Wht 2 Wht
7 Grn 7 Grn
8 Blk 8 Blk
Introduction
5
Section 1: Introduction
April 2022
Figure 2 M124 Internal Wiring
Installation and Operations Manual
VCIOM-17039-EN Rev. 0
Actuator
RS485
Network
Port A
Actuator
RS485
Network
Port B
6
Introduction
Installation and Operations Manual
Section 1: Introduction
VCIOM-17039-EN Rev. 0 April 2022
1.4 Parts List
Figure 3 is a list of materials supplied within each Network Master enclosure. This may be used as a
spare parts list.
Figure 3
Actuator
RS485
Network
Port A
Actuator
RS485
Network
Port A
Item Qty Model
Emerson Part
Number
Description
1 1 EA9-T6CL-R VA001-667-58 Color graphics LCD touch panel
2 1 2938730 VA2001803004 Power Supply, 24 V DC, 3 A
3 1 NIM124I VA84713 Network Interface Module, Iso. RS485
4 2 D2-06B-1 VA2001805050 Base, 6-slot with 110/220 V AC P/S
5 2 D2-250-1 VA2001805052 CPU, DL205-250
6 8 - VA37586-1 Cable, CoProcessor to NIM, 6x6, 11"
7 8 F2-CP128 VA2001805051 CoProcessor, Overdrive
8 1 NIM-TCP VA87065 Network Interface Module, Ethernet
9 1 - VA37587 Cable, CPU to CPU DxL
10 3 BK/MDA-1 VA7019900428 Fuse, 1 A, 250 V, Time Lag, CRM MDA
11 2 - VA37586-2 Cable, CoProcessor to LCD, 6x6, 46"
12 1 - VA84725 LCD com adapter
Introduction
7
Section 2: Installation
April 2022
Section 2: Installation
If the system is supplied from the factory in an NEMA enclosure, no internal wiring is required except
for connecting power and eld network wiring. The next three Sections 2.1, 2.2 and 2.3 discuss
mounting, power input and eld network wire connections to the NIM.
2.1 Mounting
The enclosure is rated for NEMA 4/12 and IP65/IP55. Dimensions of the enclosure are shown
in Figure 4. Mounting dimensions are shown in Figure 5. The enclosure may be bulkhead
mounted using the internal mounting holes. External mounting brackets may be used if desired.
When mounting using the internal mounting holes, caution must be used to ensure the holes are
sealed to maintain the NEMA/IP rating. The enclosure is supplied with ve 1/2" compression type
cable entry hubs. These may be tted with conduit type ttings if desired. If the system includes
backup LCD keypad terminal, some planning is required to allow for proper height above the oor to
view the display and properly operate the keypad.
Installation and Operations Manual
VCIOM-17039-EN Rev. 0
Figure 4
(5) Cable entries are provided for:
(1) Power Cable
(2) Field RS485 Network Cables
(2) Host RS485 Network Cables
NOTE
Allow 1 in. clearance on left side for ventilation and room for the door to swing open to left.
8
Installation
Installation and Operations Manual
VCIOM-17039-EN Rev. 0 April 2022
Section 2: Installation
Figure 5 NEMA Box Mounting
Installation
9
Section 2: Installation
April 2022
2.1.1 Rack Mount
The enclosure is designed for standard EIA 19" DIN rail rack mounting. Dimensions of the
enclosure are shown in Figure 6. The enclosure conforms to EIA RS310, IEC 297-1, and DIN 41
494, Part 1 standards. The rack in which the enclosure(s) are mounted must allow a minimum of
20" (508 mm) depth, allowing space for cable connections. If the system includes backup LCD keypad
terminals, some planning is required to allow for proper height above the oor to view the display
and operate the keypad properly.
Figure 6
Installation and Operations Manual
VCIOM-17039-EN Rev. 0
Enclosure Depth = 15.0" (381 mm)
Allow a total depth of 20" (508 mm)
for rear panel cable connections.
Figure 7 Rear Panel View
PORT A PORT B PORT C PORT D HOST 1 HOST 2
10
Installation
Installation and Operations Manual
VCIOM-17039-EN Rev. 0 April 2022
Section 2: Installation
2.2 Power Input
The system operates from 120 V AC or 220 V AC, 50/60 Hz single-phase power with internal
three-wire power terminals. Ensure that a good safety ground is provided to the electrical supply to
which the power input is connected. The system contains three main fuses (6.3x32 mm, 1 A) in the
DIN-rail mounted fuse blocks. Each chassis and the LCD terminal are independently fused. Each NIM
is powered from redundant 24 V DC power supplies from the two chassis power supplies. The LCD
terminal is powered from an independent 24 V DC power supply. All other modules within the unit
are powered over the base back plane from the associated main chassis power supply.
2.3 Field Network Wiring
The eld network is wired in a ring conguration from Port A around a loop to Port B of the
network master. Beginning at Port A, the network is wired to Port A of the rst actuator and then
from Port B of the rst actuator to Port A of the second actuator and so on until the network returns
from Port B of the last actuator to Port B of the network master. Networks may have parallel wired
(BUS wired) actuators between series wired actuators. Always wire parallel actuators to Port A
and remove termination and bias. Do not connect more than 15 actuators in parallel between any
two series connected actuators. Networks are polarized with (+) and (-) symbols on all drawings.
Proper operation requires that polarity be observed at all connections. Connect the eld networks
to the Port A and B connectors on the NIM in the network master as shown in Figure 8. The networks
must be connected to Port A and Port B of the valve actuators as shown in the wiring diagram
of the DCM 320B manual, and XTE manual. DCM 320B with Controlinc supports many different
network topologies. This manual supports only a single ring E>Net network topology that allows a
combination of parallel (BUS) and series E>Net connections on the same network.
Installation
11
Section 2: Installation
April 2022
Figure 8 320B E>Net Ring Network Wiring (Typical)
Installation and Operations Manual
VCIOM-17039-EN Rev. 0
2.3.1 Network Grounding
The shield or drain wire of the network must be earth grounded at only one point per
network segment. This single ground point may be at any location in the system where a good
earth ground can be obtained. This may be Port B of each actuator if desired. If the network shield
is connected to the internal ground or the chassis of the valve actuator, then the actuator housing
must have a good earth ground. The NIM connection is normally the building/vessel hull equipment
ground grid. A jumper may be installed between terminals 22 and 23 on the TBM of each actuator
to carry the ground throughout the loop. Do not connect the network cable shields to a power
line ground cable. Power lines can conduct lightning and other transients into the network. Do not
connect both ends of the network shield to earth ground at the network master. This can cause a
ground loop, making the transient protection system ineffective.
12
Installation
Installation and Operations Manual
VCIOM-17039-EN Rev. 0 April 2022
Section 2: Installation
2.3.2 Network Termination
The network requires termination and bias to be asserted at every network segment in
the E>Net ring. Parallel (BUS) connected actuators must have termination and bias turned off.
Setting DIP switches S1 and S2 on the NIM to the ON position terminates the Network Master (NIM).
Figure 9 TEC2000 Controlinc E>Net Ring Network Wiring (Typical)
2.4 Modbus Host Cables
It is necessary for the user to connect cables between the Modbus Host computer and the
Modbus slave NIM. If RS232 is used, components of the cable kit (F2-CBLKIT) may be used during
system integration and test but should be replaced by a quality shielded cable when the system
is put in service. Two cables are required if redundant Modbus slave modules are installed.
The system may be congured for communications at baud rates from 1200 to 115, 200 baud.
Default conguration of all slave modules is 9600 baud, 8-bit data, no parity and one stop bit.
The Modbus communications link may be congured for RS232, RS422 (4-wire), or RS485 (2-wire).
The system is normally congured at the factory to the customer-specied settings. The supplied
system is congured for RS232 and the ports are converted to isolated RS485, 2-wire by the supplied
NIM124I module.
Installation
13
Section 3: Conguring the System
April 2022
Installation and Operations Manual
Section 3: Conguring the System
The user should read this entire section before attempting to congure the system. It may also be
helpful to read Theory of Operation in Section 5 of this manual for a better understanding of the
system before attempting system conguration. Conguration data and associated Modbus registers
are shown in Table 12 in Section 4 of this manual. The system is congured from any Modbus host
capable of reading and writing up to 290 conguration registers in the range of 41325 through
41614 shown in Table 12. It is recommended that Emerson’s TECLINC be used for conguring
the system. The system is congured at the factory per the customer specications. If the user
changes the total number of actuators on the eld network or other operational parameters,
then the system conguration must be changed. If the actuators are not addressed in sequence
around the loop, then the user must enter the actuator address sequence in the Network Address
Scan List. Other parameters such as Modbus port baud rate, network master receiver time-out,
and enabling/disabling diagnostic mode may be required during system integration and start-up.
Refer to the following paragraphs of this section for location and value of conguration parameters to
be edited.
NOTICE
VCIOM-17039-EN Rev. 0
When conguration changes are made, the affected module will automatically reset and reinitialize
with the new conguration parameters. Caution must be used when conguring the Modbus
slave module to which the conguration computer is connected. The communication port of the
conguration computer must match the conguration written to the connected slave module.
Both primary and secondary chassis are congured at the same time regardless of which Module slave
port is used to congure the system.
3.1 System Protection and Software Versions
3.1.1 Password Protection
Unlike previous network master systems supplied by Emerson, the software development
environment is not required to congure the system. All software is protected by password available
only to the programmer. The software development package is not supplied with the system.
Source code is supplied only for backup and must not be modied by the user. Should a development
software package be acquired, the software on the system is password protected. This means
the user may not edit the software without the password. This does not limit the user’s ability to
congure any part of the system via the Modbus host communication ports.
3.1.2 CoProcessor Software Protection
Access to all application software in the CoProcessor modules is disabled unless each module is put
into diagnostic mode. The user must access the Modbus register containing the Diagnostic Mode
register by one of the Host communication links.
3.1.3 Software Version Identication
Software version number of each module may be obtained by reading the associated “Software
Version” Modbus register shown in Table 12. Software versions are reported as a three-digit number
with an implied decimal point between the rst as second most signicant digits. Software version
numbers are displayed by the TECLINC.
14
Conguring the System
Installation and Operations Manual
VCIOM-17039-EN Rev. 0 April 2022
Section 3: Conguring the System
3.2 Selecting Diagnostic/Programming Mode
Each module may be independently congured for Diagnostic/Programming mode by writing a
non-zero value to the “Diagnostic Mode” register. When Diagnostic Mode is selected, network
communication messages are output (printed) in ASCII format to Port 3 of the module. While in
Diagnostic Mode, the module may be interrupted and allow user to gain access to the program.
Programs may be uploaded and downloaded via Port 1 of modules in Slots 1 and 2 and Port 2 of
Modbus Slave modules in Slots 3 and 4. You must write zero to the Diagnostic Mode register to return
the module to the Normal Run Mode.
3.3 Chassis Identication and Hot Standby
The chassis near the bottom of the enclosure is the Primary chassis. The chassis near the top of the
enclosure is the Secondary chassis. Each chassis identies itself by setting the appropriate bit in the
“System Status Word”, Modbus Register 40254 as shown in Table 10 in Section 4.10 of this manual.
If Bit 8 is set then the chassis with which you are communicating is the Primary Network Master.
If Bit 9 is set then the chassis with which you are communicating is the Secondary Network Master.
Either chassis may be in Hot Standby mode. Bits 4 and 5 of register 40254 identify the chassis that is
in hot standby. The two chassis may swap roles of active and hot standby at any time a fault condition
of one chassis exists. The two chassis may be forced to swap roles of active and hot standby mode
by writing a non-zero value to Modbus Register 40249. This register will be reset to zero after mode
swap is executed.
3.4 Conguring Modbus Host Port Interface(s)
The host port may be congured for RS232 full duplex or RS422/RS485 with either 4-wire or 2-wire
half duplex by writing to the Port Hardware Mode register as shown in Table 12. The module must
be congured for RS232 if a NIIM is used for connecting the Host RS485 networks. Modbus slave
address, baud rate, and parity may be congured by writing to the associated conguration register
shown in Table 12.
3.5 Conguring the Field Network
Editing the values loaded to Modbus registers 41577 through 41580 as shown in Table 12
congure the eld network ports and network master functions. Each parameter is discussed in the
following paragraphs.
3.5.1 Conguring the Number of Slaves
The number of slaves (valve actuators) on the eld network is congured by editing the constant
loaded to “Number of Field Network Devices” in Modbus register 41577.
3.5.2 Conguring Field Network Baud Rate
Editing the constant written to Modbus register 41578 as shown in Table 12 change network baud
rate of the Network Master. If the number written to this register is not a valid baud rate, the system
will default to 9600 baud. The baud rate must match the baud rate of the valve actuators connected
to the network. The default baud of all devices and all ports of the Network Master is 9600.
Conguring the System
15
Section 3: Conguring the System
April 2022
Installation and Operations Manual
VCIOM-17039-EN Rev. 0
3.5.3 Conguring Network Master Receiver Time-Out
Editing the constant loaded to Modbus register 41579 may change receiver time-out of the network
masters. Receiver time-out is the amount of time the network master will wait for a response from
a slave device before moving on to the next device. If this time is too short (less than 10 mS) it could
cause collisions on the network, degrading communications throughput. If this time is too long, it
will cause time to be wasted while the master is trying to put unconnected devices on the network.
The default setting is 50 mS.
3.5.4 Conguring Report-By-Exception (RBE)
Loading a zero to Modbus register 41580 will disable RBE. Writing a non-zero value to register 41580
enables RBE, the default setting.
3.6 Conguring Network Address Sequence
The network master must know the sequence of slave addresses around the network ring in order
to properly perform network fault location. Unless otherwise specied, all systems are shipped with
a scan list in contiguous sequence starting at address #1 at Port A and ending with the last address
at Port B. To change the sequence of addresses in the scan list, it is necessary to edit the scan list
located in Modbus registers 41325 through 41448 or the number of registers equal to the number of
actuators on the network. If the system reloads default settings, the contiguous sequence of 1 to 124
will be loaded to this list.
16
Conguring the System
Installation and Operations Manual
VCIOM-17039-EN Rev. 0 April 2022
Section 3: Conguring the System
3.7 Conguring Device Types
The network master must know the type of slave device connected to the network corresponding
to each network address in order to acquire the desired data. There are ve different device types
that may be selected for each unit connected to the network. All device types return valve status
(inputs 16 - 31). Remaining data acquired is listed below.
Device Data Acquired
Type 0 Valve position (0 - 100% in 1% increments)
Type 1 Valve position (0 - 100% in 1% increments)
Coils (0 - 15)
Inputs (0 - 15)
Type 2 Valve position (0 - 4095)
Position setpoint (0 - 4095)
Analog output (0 - 4095)
Type 3 Valve position (0 - 4095)
Position setpoint (0 - 4095)
Analog output (0 - 4095)
Coils (0 - 15)
Inputs (0 - 15)
Type 4 Valve position (0 - 4095)
Position setpoint (0 - 4095)
Analog output (0 - 4095)
Valve torque (0 - 4095)
User analog input #1 (0 - 4095)
User analog input #2 (0 - 4095)
Type 5 Valve position (0 - 4095)
Position setpoint (0 - 4095)
Analog output (0 - 4095)
Valve torque (0 - 4095)
User analog input #1 (0 - 4095)
User analog input #2 (0 - 4095)
Coils (0 - 15)
Inputs (0 - 15)
Type 7 XTE3000 actuator
Conguring the System
Unless otherwise specied, all systems are shipped with all devices congured as Type 2. To change
the device type for any one or all devices, it is necessary to edit the device type list located in Modbus
registers 41449 through 41572 or the number of registers equal to the number of devices on the
network. If the system reload default settings, all devices will be set as Device Type 2.
17
Section 4: Modbus Register Maps
April 2022
Installation and Operations Manual
VCIOM-17039-EN Rev. 0
Section 4: Modbus Register Maps
4.1 Valve Status and Command Registers per
Modbus Function Code
Controlinc Network Masters communicate with host computer equipment using Modbus RTU
protocol. Valve actuator status and alarms data may be acquired from the Network Master using
any one of four Modbus Function Codes (01 thru 04). Data is returned as either discrete (bit) type
using Function Code 01 and 02 or as 16-bit unsigned integers using Function Code 03 and 04.
Command outputs to the valves may be written to the Network Master using four Function Codes
(05, 15, 06, and 16). Table 1 is the address map for valve actuators up to a maximum of 124. Status of
each valve is stored as 16 discrete inputs and as 16 coils. Discrete commands to each valve consist of
eight bits (coils) per valve and are stored as coils in one 16-bit register per actuator. Position setpoint
is an analog word (0 - 4095) value written to the valve actuator using the 06 or 16 function codes.
All registers are unsigned 16-bit integers.
NOTE
Modbus addressing shown in the tables of this section is the normal conguration addressing
method used by most SCADA and DCS systems. If you are building Modbus messages at the
communication driver level, keep in mind that HEX-starting addresses in the Modbus message
are offset by one. You must subtract one from the address in the tables when building a Modbus
message. For example, to read the rst valve status bits as coils using Function Code 01, the starting
address of 1025 shown in Table 1 would be 400 Hex (1024 decimal) in the Modbus message. If valve
status of the rst valve is read using Function Code 02, the starting address of 10001 shown in Table 1
would be 00 Hex in the Modbus message. If valve status of the rst valve is read using Function
Code 03, the starting address of 40001 shown in Table 1 would be 00 Hex in the Modbus message.
Table 1. Memory Map of Valve Data and Commands by Function Code
Function Code and
Valve Data/Command
01 Discrete valve status Read Coils (discrete) 01985 03968 1984
01 Discrete Outputs (0 - 15) Read Coils (discrete) 03969 05952 1984
02 Discrete valve status Read Inputs (discrete) 10001 11984 1984
02 Discrete Inputs (raw 0 - 15) Read Inputs (discrete) 11985 12108 1984
03 Valve status word Read Holding Register 40001 40124 124
03 Valve position feedback Read Holding Register 40256 40379 124
03 Raw torque analog input Read Holding Register 40401 40524 124
03 Valve position setpoint Read Holding Register 40576 40699 124
03 Aux. analog input #1 Read Holding Register 40701 40824 124
03 Aux. Analog input #2 Read Holding Resister 40825 40948 124
03 Aux. Analog output Read Holding Register 40951 41074 124
03 Discrete Inputs (raw 0 - 15) Read Holding Register 41075 41198 124
03 Discrete Outputs (0 - 15) Read Holding Register 41201 41324 124
04 Valve status word Read Input Register 30001 30124 124
04 Discrete Inputs (raw 0 - 15) Read Input Register 31075 31198 124
05 Discrete valve commands Write Coils (discrete) 00001 01984 1984
Command Data Type Begin Reg Ending Reg Max Number
18
Modbus Register Maps
Installation and Operations Manual
VCIOM-17039-EN Rev. 0 April 2022
Section 4: Modbus Register Maps
Function Code and
Valve Data/Command
05 Discrete Outputs (0 - 15) Write Coils (user relays) 03969 05952 1984
15 Discrete valve commands Write Multiple Coils 00001 01984 1984
15 Discrete Outputs (0 - 15) Write Multiple Coils 03969 05952 1984
06 Discrete valve commands Write Holding Register 40125 40248 124
06 Valve position setpoint Write Holding Register 40576 40699 124
06 Aux. analog output Write Holding Register 40951 41074 124
06 Discrete Outputs (0 - 15) Write Holding Register 41201 41324 124
16 Discrete valve commands Write Multiple Registers 40125 40248 124
16 Valve position setpoint Write Multiple Registers 40576 40699 124
16 Aux. Analog output Write Multiple Registers 40951 41074 124
16 Discrete Outputs (0 - 15) Write Multiple Registers 41201 41324 124
NOTE:
User Relays #1 and #2 may be controlled by writing to the valve command registers. See Table 7 in Section 4.4.
These relays may also be controlled by writing to Discrete Outputs 04 and 05. See Section 4.9.
Command Data Type Begin Reg Ending Reg Max Number
4.2 Valve Status Bit Data for Each Valve
Valve status information is stored in contiguous registers in sequence with the valve actuator
network address. Table 2 shows the valve status for valve address #1 when using Modbus Function
Code 02.
Table 2. Valve Status Information for Valve at Network Address #1 for
Controlinc Model 320B
Modbus Address Valve Status Description
10001 Open Limit Switch Valve Fully Open
10002 Close Limit Switch Valve Fully Closed
10003 Transition Opening Valve is Moving Open
10004 Transition Closing Valve is Moving Close
10005 Manual Mode Selector Swt in Local
10006 Auto Mode Selector Swt in Remote
10007 Open Torque Alarm Open Torque Swt Tripped
10008 Close Torque Alarm Close Torque Swt Tripped
10009 Valve Stall Alarm Valve is Not Moving
10010 Power Monitor Alarm Loss of Control Voltage
10011 Motor Overload Alarm Overload Relay Tripped
10012 Phase Monitor Alarm 3-Phase power reversed
10013 Local ESD Alarm Local ESD input activated
10014 Actuator Fail Alarm Failed self-diagnostics
10015 Com No-Response Alarm Com Failure on both lines
10016 Unit Alarm Set when any alarm bit set
NOTE:
Unit alarm bit (10016) is set if any one or more alarm bits 7 through 13 are set.
Modbus Register Maps
19
Section 4: Modbus Register Maps
April 2022
Installation and Operations Manual
VCIOM-17039-EN Rev. 0
4.2.1 Multiple Valve Status Locations Using Function Code 02
Valve status information shown in Table 2 is repeated for each actuator on the network in sequence of
network address. Data for valve at network address number 2 is located at Modbus addresses 10017
through 10032. Data for valve at network address 3 is located at 10033 through 10048 and so on for
up to 124 valves on the network as shown in Table 3.
Table 3. Using Modbus Function Code 02
Valve Actuator Network Address Modbus Addresses for Valve Status
001 10001 thru 10016
002 10017 thru 10032
003 10033 thru 10048
004 10049 thru 10064
005 10065 thru 10080
thru thru
122 11937 thru 11952
123 11953 thru 11968
124 11969 thru 11984
4.2.2 Multiple Valve Status Data Using Modbus Function Code 03
The same valve status data can be accessed by the Host using Function Code 03 by reading unsigned
16-bit integers from holding registers beginning at Modbus Address 40001 as shown in Table 4.
The 16 bits of valve status for each valve actuator is the same as that shown in Table 2.
Table 4. Using Modbus Function Code 03
Valve Actuator Network Address Modbus Address
001 40001
002 40002
003 40003
004 40004
005 40005
thru thru
122 40122
123 40123
124 40124
20
Modbus Register Maps
Installation and Operations Manual
VCIOM-17039-EN Rev. 0 April 2022
Section 4: Modbus Register Maps
4.2.3 Multiple Valve Status Data Using Modbus Function Code 04
The same valve status data can be accessed by the Host using Function Code 04 by reading unsigned
16-bit integers from input registers beginning at Modbus Address 30001 as shown in Table 5.
The 16 bits of valve status for each valve actuator is the same as that shown in Table 2.
Table 5. Using Modbus Function Code 04
Valve Actuator Network Address Modbus Address
001 30001
002 30002
003 30003
004 30004
005 30005
thru thru
122 30122
123 30123
124 30124
4.3 Reading Valve Position and Setpoint
Valve position feedback is accessed by the Host using Modbus Function Code 03 to read holding
registers beginning at Modbus address 40256. Position setpoint of each valve may be read in
sequence with valve address starting at Modbus address 40576. Device types 0 and 1 return valve
position as 0 - 100% in 1% increments. All other device types return analog data representing analog
position and setpoint of each valve as unsigned 16-bit integer with a 12-bit value of 0 to 4095.
Each valve’s analog position and setpoint are located in holding registers in sequence of network
address as shown in Table 6.
Table 6. Valve Position Feedback and Setpoint using Modbus Function Code 03
Valve Actuator Network Address
001 40256 40576
002 40257 40577
003 40258 40578
004 40259 40579
005 40260 40580
thru thru
122 40278 40697
123 40279 40698
124 40380 40699
Position Setpoint
Modbus Addresses
Modbus Register Maps
21
Section 4: Modbus Register Maps
April 2022
Installation and Operations Manual
VCIOM-17039-EN Rev. 0
4.4 Writing Discrete Commands to Valve Actuators
Discrete commands are written to a single valve actuator as coils (bit) data using Modbus Function
Code 05 or to multiple valve actuators using Function Code 15. Commands may also be written to
valve actuators by writing holding registers using Function Code 06 or to multiple holding registers
using Function Code 16. Emergency Shut Down to all valve actuators (ESD) is accomplished by
writing seven (7) to Modbus Register 40250. This will cause ESD to be broadcast to all valve actuator
addresses. Writing a zero to register 40250 ends the ESD function. Regardless of “Device Type”,
each valve actuator will respond to eight commands as shown in Table 7. The four LSBs of each word
control the valve actuator. The next higher four bits of each word control the two User Relays. When
writing to holding registers, one register is written per valve in sequence of valve addresses. Writing
zeros to any location has no affect on operation. Each command is a positive one (set coil) and the coil
is automatically reset to zero when the command is executed. Only one coil per valve may be written
for valve control at any one time. Writing multiple coils to control a single valve will cause no action,
i.e. it is treated as a no-op. Writing two mutually exclusive coils will have no affect on operation.
Table 7. Writing Commands to Valves using Function Code 05 or 15
Modbus Address Comman and Valve Network Address
0001 Open - Valve at address 001
0002 Stop - Valve at address 001
0003 Close - Valve at address 001
0004 ESD - Valve at address 001
0005 Turn ON User Relay #1 for valve address 001
0006 Turn OFF User Relay #1 for valve address 001
0007 Turn ON User Relay #2 for valve address 001
0008 Turn OFF User Relay #2 for valve address 001
0009 Reserved
00010 Reserved
00011 Reserved
00012 Reserved
00013 Reserved
00014 Reserved
00015 Reserved
00016 Reserved
Discrete command holding registers contain four commands per valve and four bits for User Relay
output control per register. A single register may be written to command one valve by using Modbus
Function Code 06. Multiple registers may be written to control multiple valves by using Function
Code 16. Command holding registers begin at Modbus address 40125. A total of 124 registers
are used for the command coils. Writing a seven (7) to Modbus Register 40250 will cause an ESD
command to be sent to all actuators on the network. Each actuator is congured to respond to the
ESD command in one of three ways: go closed, go open, or stay put. Each actuator can also control an
ESD relay, that may be wired to control the actuator, external equipment or to override some internal
function. See instructions on setting valve actuator ESD functions in the document EIM TEC2000
Installation and Operations Manual E2K-405-0703 listed in Section 1.1.
4.5 Writing Analog Valve Position Setpoint
(Function Codes 06 and 16)
If the valve is a modulating or positioning unit (except device types 0 and 1), the position setpoint
may be written to the valve as an unsigned 16-bit integer from 0 to 4095 using Modbus Function
Codes 06 or 16. Setpoint of each valve is in sequence with network address. Any DCM 320B actuator,
except device types 0 and 1, may be a positioner or modulating unit. The actuator depending on the
command issued by the master automatically sets the operating mode.
22
Modbus Register Maps
Installation and Operations Manual
VCIOM-17039-EN Rev. 0 April 2022
Section 4: Modbus Register Maps
4.6 Reading Auxiliary Analog Inputs Using
Function Code 03
Device types 4 and 5 have two auxiliary analog inputs for data acquisition of other equipment such
as pressure or temperature transducers. The two inputs for each actuator are identied as AIN2
and AIN3. The analog data is returned as unscaled 12-bit unsigned integers with a value between 0
and 4095. The host is required to scale the values to engineering units for display to the Man Machine
Interface (MMI). The values are scaled by (real time value/4095*full scale engineering units). Data for
auxiliary analog inputs AIN2 is in sequence with network address starting at Modbus register 40701.
Up to 124 values may be acquired. The last register for the 124th unit is 40824. Data for auxiliary
analog inputs AIN3 is in sequence with network address starting at address 40825. Up to 124 values
may be acquired. The last register for the 124th unit is 40928.
4.6.1 Reading Torque Analog Input Using Function Code 03
Device types 4 and 5 may have an optional analog input for relative torque measurement. The
torque data is scaled as 0 - 4095 for 0 - 100% of the analog value read from register 15 labeled
AIN#1. The user must provide scaling at the host for conversion to actual torque based on the
actuator model and spring pack. Torque data range is provided on the data sheet supplied with
each actuator. Torque data may be used for detection of valve problems by measuring and storing
an initial maximum opening torque and then comparing the current reading to the stored initial
maximum torque reading. If the current reading exceeds the initial maximum torque reading by
a predetermined amount (limit), then a valve maintenance alarm or message may be generated.
The analog torque reading is in sequence with network address starting at Modbus register 40401.
Up to 124 values may be acquired. The last register for the 124th unit is 40524.
4.7 Reading and Writing Auxiliary Analog Outputs
All device types, except type 0 and 1, have an option to add one 4 - 20 mA analog output. The host
may write to the output by writing to a Modbus register in sequence with network address starting
at register 40951. Up to 124 analog outputs may be written. The last register for the 124th unit
is 41074. Data must be written to the actuators as 12-bit analog data with a range of 0 to 4095
corresponding to 4 - 20 mA. The data is written to the actuators using Modbus Function Code 06
or 16. The analog output may be read back from the actuator using Function Code 03.
4.8 Reading User Discrete Inputs
Each 320B has two isolated discrete inputs available to the User. These are Inputs 13 (User Input #1)
and 14 (User Input #2) in the 320B discrete input memory map. Inputs 0 - 15 of the 320B are the
raw hardware discrete inputs and are de-bounced by software. None of the inputs are software
generated. The Network Master reads all discrete inputs (0 - 15) of device types 1, 3, and 5 and
places these into contiguous data base locations corresponding to network address of the actuator.
Inputs of each actuator are shown in Table 8. The host, using Function Codes 02, 03, and 04, may
access these inputs. When using Function Code 02, the inputs are addressed from 11985 to 13968
with 16 inputs per actuator as shown in Table 8 for up to 124 actuators. When using Function
Code 03, the discrete inputs are addressed from register 41075 (valve #1) to 41198 (valve #124).
When using Function Code 04, the discrete inputs are addressed from register 31075 (valve #1) to
31198 (valve #124). Inputs (bits) of each valve actuator within the 40000 and 30000 registers are in
the same sequence as shown in Table 8.
Modbus Register Maps
23
Section 4: Modbus Register Maps
April 2022
Table 8. Discrete Inputs for Valve at Network Address #1 Using Function Code 02
for Controlinc Model 320B
Modbus Address Valve Status Description
14001 Open Limit Switch Valve Fully Open
14002 Close Limit Switch Valve Fully Closed
14003 Auxiliary Open Contact Aux. contact of starter
14004 Auxiliary Close Contact Aux. contact of starter
14005 Manual Mode Selector Swt in Local
14006 Auto Mode Selector Swt in Remote
14007 Open Torque Alarm Open Torque Swt Tripped
14008 Close Torque Alarm Close Torque Swt Tripped
14009 Power Monitor Alarm Loss of Control Voltage
14010 Motor Overload Alarm Overload Relay Tripped
14011 Phase Monitor Alarm 3-Phase power reversed
14012 Local ESD Alarm Local ESD input activated
14013 VFC Fault Alarm VFC alarm input activated
14014 User Discrete Input #1 Isolated user wired input
14015 User Discrete Input #2 Isolated user wired input
14016 On-Board Execute Button Used by 320A or B only
Installation and Operations Manual
VCIOM-17039-EN Rev. 0
4.9 Writing User Relay Outputs (MRTU Support)
Device types 1, 3, and 5 allow four relays to be controlled by the host. The outputs are Coils 00
(Close Relay), 01 (Open Relay), 04 (User Relay #1) and 05 (User Relay #2) in the 320B Coil Map (0 - 15).
The Network Master may read and write all 16 coils but masks all coils except 00, 01, 04 and 05. If the
user attempts to write to any other coils, the command will be ignored. The user should not write to
coils 00 (close) or 01 (open) if the device is a valve actuator. Write these coils only if the device is a
Micro Remote Terminal Unit (MRTU).
The database of the Network Master is congured for 16 coils per actuator for 124 actuators in
sequence with valve address. The User Relays may be controlled using Function Codes 05, 15, 06,
or 16. If Function Codes 05 or 15 are used the coils are addressed from coil 03969 to 05952 with
16 coils per actuator. For example, writing to the relays of valve number one, write to coil 03972 for
User Relay #1 and 03973 for User Relay #2. User Relays of each consecutive valve are offset by 16.
For example, User Relay #1 of valve number two would be coil 03989 (3973+16). Coils 00 (close)
and 01 (open) are masked by the network master when the selector switch is in “Remote” mode.
This prevents the host from overwriting these coils in the valve actuator when under control by
the Controlinc card in the actuator. The host may control On/Off state of User Relay#1 and User
Relay#2 regardless of device type by writing to the discrete command registers as shown in Table 7 as
explained in Section 4.4.
24
Modbus Register Maps
Installation and Operations Manual
VCIOM-17039-EN Rev. 0 April 2022
Section 4: Modbus Register Maps
4.10 System Status Word
The system status word is the status of the Network Master. This word is located in Modbus
register 40254. The system status word may be read using Modbus Function Code 02 or 03 in the
same manor as reading valve status. Bit locations for Function Code 02 are shown in Table 9. Only the
rst least signicant twelve bits are dened.
The four most signicant bits are reserved for future functions and are set to zeros. If Bit 8 is set (true)
then the chassis is the primary network master. If Bit 9 is set (true) then the chassis is the secondary
network master. Bit assignments are shown in Table 9.
Table 9. System Status Word Bit Map
Bit Status Denition Note CR FC02
0 Primary Watchdog Timer Alarm - 20 14049
1 Secondary Watchdog Timer Alarm - 21 14050
2 Primary Failed Write Command Alarm C (FW) 22 14051
3 Secondary Failed Write Command Alarm C (FW) 23 14052
4 Primary Master in Hot Standby Mode C (HM) 24 14053
5 Secondary Master in Hot Standby Mode C (HM) 25 14054
6 Primary Network Fault Alarm C (NF) 26 14055
7 Secondary Network Fault Alarm C (NF) 27 14056
8 Primary Network Master Active C (AM) 30 14057
9 Secondary Network Master Active C (AM) 31 14058
10 Primary Host Link Failed Alarm - 32 14059
11 Secondary Host Link Failed Alarm - 33 14060
12 DXL Grant primary master access to network - 34 14061
13 DXL Grant secondary master access to network - 35 14062
14 DXL Fail Alarm - 36 14063
15 Switch Active Master to Hot Standby and Standby to Active - 37 14064
Primary and Secondary Host Link Failed alarms shown in Table 9 are determined by queries received
from the Modbus host computer (DCS) using function codes 01, 02, 03, 04 or 08. If a query is
not received from the host in about ve to six seconds, then this alarm is set. Host link alarms are
exchanged between the primary and secondary network masters. These alarms are also used to help
determine which master takes control of the network.
The host communication status and associated network fail-over is discussed in the Theory of
Operation Section of this manual. The host(s) must repeatedly transmit queries to both primary
and secondary masters within ve seconds between transmissions to prevent the masters from
detecting a faulty link from the host(s). The network master will not respond to any queries while in
hot standby.
Modbus Register Maps
25
Section 4: Modbus Register Maps
April 2022
4.11 Combined System Alarms
In addition to the system alarms located in the system status word at Modbus register 40254, there
are four combined system alarms located at Modbus register 40251 as shown in Table 10. The system
is in alarm when this register is non-zero and the alarm is cleared when this register in zero. Bit 0 is
a combined alarm for bits 1 - 3 in register 40251, meaning this bit is set when any one of the other
system alarms is set. Bit 1 is set when any valve actuator on the loop is in alarm. This is a combination
of all actuator Unit alarms. Bit 2 is set when the Primary master is in alarm. This is a combination of
Bits 0, 2, 6 and 14 of the system status word shown in Table 9. This alarm is also set when the Primary
master is powered down. Bit 3 is set when the Secondary master is in alarm. This is a combination
of Bits 1, 3, 7 and 14 of the system status word shown in Table 9. This alarm is also set when the
Secondary master is powered down.
Table 10. Combined System Alarms (Modbus Register 40251)
Bit Alarm Denition
0 System Alarm (Combined system alarm, set when any one of Bits 1, 2, or 3 is set)
1 Actuator Unit Alarm (Set when any valve actuator unit alarm is set)
2 Primary Master Alarm (Set when any primary master alarm is set)
3 Secondary Master Alarm (Set when any secondary master alarm is set)
4-15 Reserved for future enhancements
Installation and Operations Manual
VCIOM-17039-EN Rev. 0
4.12 Network Fault Location
If the eld network is connected in a ring conguration, the Network Master automatically
detects and locates a single line fault. Location of the fault may be displayed by the LCD terminal
or the MMI as two network addresses. The two network addresses between which the fault is
located is available in Modbus register 40252 (Network Fault Low Address) and register 40253
(Network Fault High Address).
By reading these two locations, the SCADA or DCS host may display to the MMI the location of the
fault when a Network Fault system alarm bit is set. It is important for the address scan list be properly
congured as described under system conguration, Section 3.6 of this manual, in order for fault
location to function properly.
4.13 M124 Global Database and Modbus
Holding Register Map
Table 11 is supplied for the benet of the software engineer and is not required for system
conguration. The system automatically allocates memory for the database as shown.
All communication modules, masters and slaves, located in Slots 1 - 5 of the I/O rack share the same
database located in the memory of the main processor. Table 12 is supplied for system conguration.
For more detail on system conguration, see Section 3 of this manual. All communication modules
may be congured from any one of the Modbus slave ports normally connected to a host.
Emerson TECLINC Version 117 may be used to congure the network masters. The TECLINC software
is include in a CD that ship with the Network Master or can be obtained by Sale Representative.
Any other Third-Party Modbus host device can also be used to do the congurations by using our Map
Table 12.
26
Modbus Register Maps
Installation and Operations Manual
VCIOM-17039-EN Rev. 0 April 2022
Section 4: Modbus Register Maps
Table 11. M124 Global Database and Modus Register Assignments for Valve Data
(All Actuator Data is in sequence with Valve Actuator Network Address)
Parameter Octal Decimal Hex Modbus
Valve Status and Alarms (124 words)
Discrete Valve Commands (124 words)
Swap Primary and Hot Standby - 1770 1016 3F8 40249 R/W
ESD to all Valve Actuators - 1771 1017 3F9 40250 R/W
System Alarm - 1772 1018 3FA 40251 RO
Network Fault Low Address - 1773 1019 3FB 40252 RO
Network Fault High Address - 1774 1020 3FC 40253 RO
System Status Word (1 word) - 1775 1021 3FD 40254 RO
System ID, High byte = Char. E,
69 decimal, Low byte = Loop #
Valve Position Feedback (124 words)
Valve Torque (raw analog) (124 words)
Valve Position Setpoint (124 words)
User Analog Input #1 (124 words)
User Analog Input #2 (124 words)
Analog Output (124 words)
User Discrete Inputs
(valve inputs 0 - 15) (124 words)
User Discrete Outputs
(valve outputs 0 - 15) (124 words)
Begin 1400 0768 300 40001
End 1573 0891 37B 40124
Begin 1574 0892 37C 40125
End 1767 1015 3F7 40248
- 1776 1022 3FE 40255 RO
Begin 1777 1023 3FF 40256
End 2172 1146 47A 40379
Begin 2220 1168 490 40401
End 2413 1291 50B 40524
Begin 2477 1343 53F 40576
End 2672 1466 5BA 40699
Begin 2674 1468 5BC 40701
End 3067 1591 637 40824
Begin 3070 1592 638 40825
End 3263 1715 6B3 40948
Begin 3266 1718 6B6 40951
End 3461 1841 731 41074
Begin 3462 1842 732 41075
End 3655 1965 7AD 41198
Begin 3660 1968 7B0 41201
End 4053 2091 82B 41324
RO
R/W
RO
RO
R/W
RO
RO
R/W
RO
RO
Modbus Register Maps
WARNING
!
Writing 7 to Register 40250 will cause all actuators to execute ESD.
Writing zero to Register 40250 will disable (end) ESD.
27
Section 4: Modbus Register Maps
April 2022
Table 12. M124 Network Master Conguration (Writing to RO Registers is
allowed but will be over-written by the controller)
(All Registers are 16-bit Unsigned Integers)
Installation and Operations Manual
VCIOM-17039-EN Rev. 0
Conguration
Slot/Parameter
Network Address
Scan List
(124 words)
Device Type List
(124 words)
Main CPU
S/W Version
System Reset
Slot 1
(Net Master)
Software Version
Diagnostic Mode
Number of Field
Network Devices
Baud rate of Valve
Actuator Network
Receiver Time-Out Enter time in milliseconds [50 mS] 7017 E0F 42832 R/W
Enable/Disable
Report-By-Exception
Reserved Data written ignored. 7021 E11 42834 R/W
Enable Program Mode
Reload Default Scan
List and Device Types
Slot 2
(LCD Terminal)
Software Version
Diagnostic Mode
LCD Control Passcode
Reserved for Future
Expansion
Conguration Options, Default
settings shown in [brackets]
Physical sequence of
Actuators on Network
Type of each Slave Device on Valve
Actuator Network
Software Version Number of RLL. Data
written to this register will be over-written
by the CPU on power-up
Writing non-zero value will cause the
system to reset. This register is zeroed
after reset.
Valve Actuator Network Master
Module S/W Version Number
Written by Module in Slot 1
[0=Normal Run Mode]
Non-Zero=Diagnostic Mode
[124] Total number of slave devices
connected to network
Enter whole number/100.
Example: 48, 96, 192, 384. [96]
0=Disable report by exception (RBE)
[Non-Zero=Enable RBE]
Writing a non-zero value to this register
allows the module to be programmed
from Port 1.
Writing zero to this register reloads
sequential scan list from 1 to 124 and all
device types as 2. Do not write a non-zero
value. The master writes 0x5A5A to this
register after defaults are loaded.
LCD Panel and Control Passcode
Module S/W Version Number
Written by Module in Slot 2
[0=Normal Run Mode]
Non-Zero=Diagnostic Mode
[0=Passcode Disabled]. Write integer
between 125 and 998.
Data written to these registers
are ignored.
Begin 6025 C15 42326
End 6416 D0B 42575
Begin 6417 D0F 42576
End 7010 E08 42825
Begin 4463 933 41588
End 4471 938 41594
PLC
Octal
7011 E09 42826 RO
7012 E0A 42827 R/W
7013 E0B 42828 RO
7014 E0C 42829 R/W
7015 E0D 42830 R/W
7016 E0E 42831 R/W
7020 E10 42833 R/W
7023 E13 42836 R/W
7024 E14 42837 R/W
4460 930 41585 RO
4461 931 41586 R/W
4462 932 41587 R/W
PLC
Hex
Modbus
Register
R/W
R/W
R/W
28
Modbus Register Maps
Installation and Operations Manual
VCIOM-17039-EN Rev. 0 April 2022
Section 4: Modbus Register Maps
Conguration
Slot/Parameter
Slot 3
(Host Port 1)
Software Version
Diagnostic Mode
Modbus Slave Address
Modbus Slave Baud Rate
Modbus Slave Parity [0=None], 1=Odd, 2=Even 4476 93E 41599 R/W
Port Hardware Mode [0=RS232], Non-Zero=RS422/485 4477 93F 41600 R/W
Reserved for Future
Expansion
Slot 4
(Host Port 2)
Software Version
Diagnostic Mode
Modbus Slave Address
Modbus Slave Baud Rate
Modbus Slave Parity [0=None], 1=Odd, 2=Even 4510 948 41609 R/W
Port Hardware Mode [0=RS232], Non-Zero=RS422/485 4511 949 41610 R/W
Reserved for Future
Expansion
Conguration Options, Default
settings shown in [brackets]
Modbus Slave Conguration
Module S/W Version Number
Written by Module in Slot 3
[0=Normal Run Mode]
Non-Zero=Diagnostic Mode
Enter whole number from 1 to 254.
[Default=5]
Enter whole number. Example:
4800, 9600, 19200, etc. [9600]
Data written to these registers
are ignored.
Modbus Slave Conguration
Module S/W Version Number
Written by Module in Slot 4
[0=Normal Run Mode]
Non-Zero=Diagnostic Mode
Enter whole number from 1 to 254.
[Default=5]
Enter whole number. Example:
4800, 9600, 19200, etc. [9600]
Data written to these registers
are ignored.
PLC
Octal
4472 93A 41595 RO
4473 93B 41596 R/W
4474 93C 41597 R/W
4475 93D 41598 R/W
Begin 4500 940 41601
End 4503 943 41604
4504 944 41605 RO
4505 945 41606 R/W
4506 946 41607 R/W
4507 947 41608 R/W
Begin 4512 94A 41611
End 4515 94D 41614
PLC
Hex
Modbus
Register
R/W
R/W
NOTES:
▪ Network Address Scan List defaults to addresses 1 to 124 in sequence.
▪ Device Type List defaults to all type 2.
▪ All communication ports default to RS232, 9600, N, 8, 1.
▪ All host ports (Modbus slaves) default to address 1.
▪ All modules default to Normal Run Mode.
Modbus Register Maps
29
Section 5: Theory of Operation
April 2022
Installation and Operations Manual
Section 5: Theory of Operation
This section describes systems with redundant network masters. If your system does not have
redundant masters, references to redundant chassis or modules do not apply. The system normally
has two Network Master chassis running identical software. System conguration and the Network
Master’s ability to access the eld network determine mode of operation of each chassis. Either of the
network masters may take control of the eld network. The following paragraphs explain how the
system functions from an application software point of view. This will provide a better understanding
of how the system functions. The Network Masters may be referred to as modules.
5.1 Valve Actuator Network Connections
In order to better understand how the Network Masters operate, the user needs to understand
what goes on at the network and actuator level. Each 320B valve actuator has a network Port A
and Port B connection. When a message is received on either port, it is conditioned by hardware
and transmitted at the other port. If a message is received on Port A, it is transmitted at Port B. If a
message is received at Port B, it is transmitted at Port A.
Messages on the network are conditioned and transmitted in both directions without intervention
of microprocessor software. As the message passes through the actuator, it is received by the
microprocessor of the valve actuator. If the message address matches the actuator address, the
command is processed, and the valve actuator responds to the host command. When the actuator
responds, it transmits on both Ports A and B. Thus, both communication channels of the network
master receive messages returned from the eld. Both redundant Network Masters receive all
messages from the network from both ends of a ring.
VCIOM-17039-EN Rev. 0
5.2 Power-up Initialization
The M124 system supports one Network Master module per chassis but may support a variable
number of slave modules. At power-up, the Network Master module congures itself based on
information read from the global database as written to the system via Modbus registers 41574
through 41584. Each communication module in the rack reads the number of slaves congured for
the network from memory location 0x927 (Modbus register 41577).
The master module uses the number of slaves to allocate memory and build a scan list obtained from
a master scan list starting at memory location 0x82B, Modbus register 41325. The module then reads
the device type list starting at memory location 0x8A7 (Modbus register 41449). The module reads
its network baud rate from memory location 0x928 (Modbus register 41578). This is the baud rate for
network Ports 1 and 2 of the module. The module reads its receiver time out from memory location
0x929 (Modbus register 41579). This is the amount of time in milliseconds it will wait for a response
from a slave before agging the slave response as bad and going on to the next slave address.
The module reads the RBE enable from memory location 0x92A, Modbus register 41580. If the value
in this location is greater then zero, then the master will use Report-By-Exception (RBE) in the polling
process. If the value is zero then RBE is disabled.
The module reads the Diagnostic Mode from memory location 0x926 (Modbus register 41576).
If the value in this register is greater than zero, the module transmits ASCII debug messages to Port 3
at 9600, N, 8, 1. Transmitting these debug messages signicantly slows down the normal process.
It is advisable to always write a zero to this register to enable normal run mode after diagnostics
is complete. While in diagnostic mode, the module will transmit to Port 3 selected Modbus messages
sent to and received from the network ports. It will also transmit other useful diagnostic messages
to Port 3, such as error messages. The module reads the Program Mode from memory location
0x92D (Modbus register 41583). If the value in this register is greater than zero, the module will
enable Port 1 as the programming port, disable “LOCKOUT”, and enable entry of Control C at Port 1.
This mode allows the processor to be halted by entering Control C. The program may be edited
online or a new program downloaded at Port 1.
30
Theory of Operation
Installation and Operations Manual
VCIOM-17039-EN Rev. 0 April 2022
One of the two redundant chassis is congured at the factory as the “primary” chassis and the
other is congured as the “secondary” chassis. The secondary chassis normally powers up in the
Hot Standby mode. The secondary master module/chassis delays two seconds after power-up to
allow the primary module/chassis to take control of the network. If the system is installed with a
Hot Standby system, this forces the Hot Standby unit (secondary module/chassis) to remain in the
Hot Standby mode so long as the primary master is communicating on the same network to which
it is connected.
Section 5: Theory of Operation
5.3 Hot Standby Fail-Over
After power-up, both masters listen to the network to which they are connected for 500 mS. If no
activity is detected (quiet line), the module checks status of the host links to both chassis. If the
other chassis is not present, then the rst chassis will proceed to take control of its network if it has
a good host link. If network activity is detected during this process, the timer is reset to 200 mS
and the whole process begins again. If a master transmission is detected while listening to the line,
the message is discarded, and the listening process is restarted. If at any time during the listening
process, a master module detects a quiet line, it will begin the polling process and thus take over
the network but only if a good host link is detected. In the case of redundant host links, if all host
links are bad, it checks the status of the host links to the other chassis. If the other chassis has a
good host link then the listen mode will be repeated, allowing the other chassis with a good host
link to take control. During the polling process, if another master’s message is received, the module
will go into Hot Standby mode and begin listening to the network again.
This process requires less than 1 s, where the normal listening process takes up to two seconds
to fail-over. If the master detects all host links have failed, it checks the status of the host link
of the other chassis. If the other chassis has a good host link, then listen mode will be entered,
else the polling process will continue. Each module resets its own watchdog timer when valid
data is received from the network. On every poll cycle, each module checks the status of its own
watchdog timer. If the watchdog timer times out, the module goes to the listen mode and turns
the network over to the Hot Standby chassis. Each module counts the number of no responses from
the slave units. If the number of no responses exceeds the number of connected devices plus ten,
without receiving good data, then the module goes into listen mode and releases the network to
the Hot Standby chassis. Normal failover time is 800 mS for problems other than host link failures.
Fail-over time for host link failures is up to 6 s from the time the host stops polling the master.
5.3.1 Modbus Host Link and Fail-Over
Each time the host transmits a query to the network master using function code 01, 02, 03, 04,
or 08, the host link timer is reset. If a host query is not received within 5 to 6 s, the master sets the
Host Link Failed Alarm in the system status word. Both chassis monitor status of redundant host
links to both chassis. If the redundant links to the master that has control of the network fails, then
the system will fail-over to the chassis that has a good host link. If either of the two modules goes
into Hot Standby mode, Modbus communication transmissions to the host system are inhibited.
This ensures that the host is acquiring data from the system that has control of the network. If both
chassis have good host links or if both chassis have bad host links, then the master that has control of
the network will retain control.
Theory of Operation
31
Section 5: Theory of Operation
April 2022
5.4 Network Fault Detection
If the module gains access to the network, it then performs a network test. It transmits a message
from Port A and veries that the message is received through the network at Port B. It then transmits
a message from Port B and veries that the message is received through the network at Port A. If the
message is not received on either port after three attempts, it then sets the network fault alarm.
It then polls form Port A around the ring in the order of slave addresses from the scan list for the total
number of actuators congured. The module records the last address that responded as the fault
location low address. The module polls the network from Port B by polling from the last congured
address in the scan list and decrements to the rst address in the scan list. The module records the
last address to respond as the location of the network fault high address.
The network fault is located between the low address and high address. These addresses are available
to the host in Modbus registers 40252 and 40253. If a module gains access to the network but does
not receive any valid data from the connected slaves, it also sets a network fault alarm. Each time
the module nishes 5 complete poll cycles of all network addresses, it repeats the network fault test
described above. Network fault conditions reported in the system status word and the location of
the fault should be alarmed to the system operator MMI (HMI) so that the fault can be corrected. If a
network fault is detected, the module polls the accessible addresses around the ring in one direction
from Port A and then polls around the ring in the opposite direction from Port B. This allows the
master to access all actuators on both sides of the network fault. Under network fault conditions, the
module polls one address from the scan list greater than the last address to respond, i.e., it polls one
address past the fault location. If the address beyond the fault responds, the network fault alarm is
reset, and the normal polling process resumes.
Installation and Operations Manual
VCIOM-17039-EN Rev. 0
5.5 Polling Process
The module gets slave addresses from a scan list located in the global data starting at memory
location 0x82B and progress upward for the next slave to poll. The scan list is actually loaded into
the network master module form the database at power-up. If a valid address is the next address
in the poll sequence, the slave is polled and received data stored in the global database by address
sequence, not scan list sequence. If a slave does not return data for three poll cycles, the module sets
the COM alarm bit for that slave address.
Valve actuator status includes one COM alarm bit (14th bit). This com alarm bit is set only when both
network paths have failed, meaning both Port A and Port B of the module lost access to the actuator.
The COM alarm bit is reset when either port gains access to the actuator.
5.6 Report-by-Exception
The system uses Modbus Function Code 07 for report-by-exception (RBE). The module normally
polls all devices with Function Code 07. If the valve actuator did not have any status, alarms, or
analog valve changes since the last master’s request it returns zero in the Function 07-processor
status eld. If data changed since the last poll, the valve actuator responses with a 0xFF in the
processor status eld. The valve actuator is actually performing the RBE process, distributing the
RBE processing time among the salve devices. If zero is returned, the master module has no data to
process into the database.
It simply goes on to the next slave address in the scan list. If 0xFF is returned, indicating an exception,
the module polls the actuator using Function Code 03. All data is requested in one block and
processed into the database when received. This RBE process speeds up the system throughput by
a factor of four to six times due to the small amount of data being transferred over the network.
Throughput is also increased due to the fact that no data is processed into the database (the most
time consuming event) until data has changed. To ensure the host system always has an accurate
database, the valve actuators force an exception every 200 poll cycles.
32
Theory of Operation
Installation and Operations Manual
VCIOM-17039-EN Rev. 0 April 2022
Section 5: Theory of Operation
5.7 Priority Scan
When a master module receives a command from the host and commands an actuator to move, the
actuator’s address is put in priority scan. If a valve transition opening or closing status is received
from an actuator, its address is put in priority scan. The module polls the valves in priority scan rst
and then polls the next slave in the master scan list. It continues this pattern of interlace scanning of
moving valves between non-moving valves.
The interlace-scanning process insures fast update of moving valves to the host system. An unlimited
number of slave addresses may be in priority scan at any one time. Slave addresses are removed
from priority scan as soon as their opening or closing transition bit is cleared or if they go into
communications alarm.
5.8 Writing Discrete Commands to Valve Actuators
The host system writes discrete valve commands to the Modbus slave module that in turn stores
the commands in the global database and sets an interrupt to the central CPU. The CPU writes the
commands to the Network Master module.
The CPU write to the master module generates an interrupt to the module. The interrupt causes
immediate processing of the commands. If a module does not accept the data written by the CPU
within two seconds, a Write Command Alarm bit is set in the system status word for the faulty
module. Each module decodes the commands and determines which slave address is to receive the
command. If the slave address is not in the scan list, the module ignores the command.
If the slave is in the scan list the command is transmitted to the slave and the module waits for an
acknowledgment. If an acknowledgment is not received within the receiver time-out period, the
command is retransmitted up to three times on Port A and three times on Port B. If the slave does
not return an acknowledgment after three transmission attempts on both Ports A and B, its COM
alarm bit is set. The host may write commands for multiple valves at the same time. The module
will decode each command in the order of the slave address and transmit each in turn. After each
command is transmitted to an actuator, the module zeros the discrete command in the global
database. Database values stored for analog setpoint, analog output, and user discrete outputs are
not zeroed.
The host may read back these types of output data at any time. Each time a new command is written,
the commanded actuator’s address is put in priority scan.
5.9 Writing Position Setpoint
When the host writes a valve position setpoint to the master, the module compares the new setpoint
with the setpoint returned by the valve actuator. If a difference is detected, the new setpoint is
transmitted to the valve actuator. The module requires an acknowledgment from the actuator. If an
acknowledgment is not received after three attempts on both Ports A and B, the COM alarm bit
for the actuator is set. Each time a new setpoint is written to a valve actuator, the address is put in
priority scan. If the address is congured as device type 0 or 1, then the master will not attempt to
write valve position setpoint.
5.10 Writing Analog Outputs
When the host writes an analog output to an actuator, the module compares the command output
to the received analog output form the actuator. If a difference is detected, it writes the new analog
value to the actuator. Like all writes, the module will attempt three times on both Ports A and B if an
acknowledgment is not received. If the address is congured as device type 0 or 1, then the master
will not attempt to write the analog output.
Theory of Operation
33
Section 5: Theory of Operation
April 2022
5.11 Writing User Relay Outputs
When the host writes to a coil corresponding to either User Relay #1 or User Relay #2 or both, the
module compares the status of the coils received from the actuator. If a difference is detected, the
module writes the new coil output (on or off) to the actuator. The module will make three attempts
to write a coil to the actuator on both Ports A and B if an acknowledgment is not received.
The module only will write discrete outputs to device types 1, 3 and 5.
5.12 Writing ESD Command
When the host writes an Emergency Shut Down (ESD) command to the system by writing a 7 to
register 40250, an ESD command is immediately transmitted to all valve actuators that are currently
active on the network. A broadcast address is not used because the module requires conrmation
that each actuator received the ESD command. It will retransmit the ESD command to any one device
up to three times. This insures that all actuators receive the ESD command; if not received, an alarm
bit is set for the actuators that do not acknowledge the command.
Installation and Operations Manual
VCIOM-17039-EN Rev. 0
34
Theory of Operation
Installation and Operations Manual
VCIOM-17039-EN Rev. 0 April 2022
Section 6: Software Source Code
Section 6: Software Source Code
Source code for the main CPU, LCD Panel, Modbus slaves and Network Master module is supplied
with the system on CD ROM. The software is supplied as a backup copy and should not be copied.
Emerson reserves all rights in accordance with copyright laws.
Thus, it must not be printed or copied. The software les may be used only for downloading to a
replacement module.
6.1 Host Database Conguration Aid
An excel spreadsheet is also supplied on the CD ROM under “Memory Maps” directory. This
spreadsheet is an aid used for conguring the host database. Load the excel le to a computer
with windows then open the spreadsheet. To use the spreadsheet, simply enter the valve actuator
network address in the designated “address” box and then hit the enter key. Locate the parameter to
be read or written by the host.
The corresponding Modbus address according to desired function code is listed for the specied
valve or MRTU under the Network Master column.
Software Source Code
35
Section 7: LCD Touch Panel Backup Terminal Operation
April 2022
Installation and Operations Manual
Section 7: LCD Touch Panel Backup
Terminal Operation
Touch Panel display may be used to monitor system and actuators health and for valve control.
7.1 Home Screen
Refer to Figure 10 for a view of the Home Screen Information.
Figure 10
VCIOM-17039-EN Rev. 0
M124 Model Master
M124 Network Master
Job# 8888888 Emerson
Primary Network Master Active
Alarms
02/08 Valve 101 - Unit Alarm
ESD
Switch to
STBY
Job Number and Job ID
Next
36
Alarms button take to
Alarms page and show
lists of alarms
Alarm Indication bar
ESD button take to ESD
page, security code required
Switch to Standby button take
Show which Master Active
Next button takes to
Valve page. Security
code required
Switch to Standby page.
Security code required
LCD Touch Panel Backup Terminal Operation
Installation and Operations Manual
VCIOM-17039-EN Rev. 0 April 2022
Section 7: LCD Touch Panel Backup Terminal Operation
7.1.1 Alarm Display
The alarm display page will display lists of alarms that valve currently has an alarm, including
system alarms.
Refer to Figure 11.
Figure 11
Alarm Summary Total of 1 Alarms
No
System Alarm - DXL Failed
Message
System and
Actuator alarms
Page Up Line DownLine Up
Page Down
Home
01/01 System Alarm - DXL Failed
7.1.2 Security Codes Screen
Refer to Figure 12 to view a Security Code Screen. This is where Password Protection screen will
prompt when it requires a security code.
Figure 12
Enter Security Code
Take back to
Home Screen
Alarm bar
Enter Password
LCD Touch Panel Backup Terminal Operation
Escape or Cancel
Back Space
Clear Contents
Enter
37
Section 7: LCD Touch Panel Backup Terminal Operation
April 2022
7.1.3 ESD Screen
Emergency Shut Down (ESD) may be sent to all valve by writing 7 cause all actuators to execute ESD.
Writing 0 (zero) will disable (end) ESD.
Refer to Figure 13.
Figure 13
EMERGENCY SHUTDOWN TO
ALL VALVES
ENTER 7 TO COMPLETE OR 0 TO
CLEAR EMERGENCY SHUTDOWN
TO ALL VALVES
Installation and Operations Manual
VCIOM-17039-EN Rev. 0
Home
Home Screen Click to enter value 0 or 7
38
LCD Touch Panel Backup Terminal Operation
Installation and Operations Manual
VCIOM-17039-EN Rev. 0 April 2022
Section 7: LCD Touch Panel Backup Terminal Operation
7.1.4 Switch Active Master to Standby Screen
Switching to Hot Standby will cause the active chassis/master to go to hot standby and allow the
chassis currently on standby to switch to the active role. This allows the two masters to be toggled
between active and standby modes. To switch the active master to hot standby mode, press the
“Switch to STBY”. Entering a non-zero value from 1 - 999 will switch the currently active master to hot
standby and allow the master in standby to become active.
Refer to Figure 14.
Figure 14
Entering the non-zero value will
switch the currently active master to
hot standby and allow the master in
standby to become active. Entering a
zero will not switch the mode
Switch to STBY
Home
Click to enter non-zero
value from 1 - 999
LCD Touch Panel Backup Terminal Operation
39
Section 7: LCD Touch Panel Backup Terminal Operation
April 2022
Installation and Operations Manual
7.2 Valve Control and Status Display
Valve status and control is displayed by the LCD touch panel. Select the valve tag number by pressing
the Next Button or Go To Button. When the desired station address or valve tag number is displayed,
the current status of the valve is displayed. The valve status display the FULL CLOSE (valve closed),
STOPPED (valve stopped in mid-travel), or FULL OPEN (valve open). If the valve is in transition,
the CLOSING will ash while the valve is closing or the OPEN will ash while the valve is opening.
Valve position is updated on the LCD display while the valve is moving. If any alarms occur in the
system or actuator alarm, it will be displayed on the bottom.
Refer to Figure 15.
Figure 15
Valve Address
Valve Position Valve Tag Name
VCIOM-17039-EN Rev. 0
Valve Control
(Command) Buttoon
Tag #
Command
Open
Open
Torq
Close
Torq
Motor
Over
FULL OPEN
Home
Screen
Home
Valve Alarms
and Status
Back
01/01 System Alarm - DXL Failed
Stop
Valve
Stall
Ph
Mon
REMOTE
Go To...
Go To Valve, jump to
any valve on the list
Local
ESD
Close
Pow
Mon
No
Com
Act.
Fail
40
Back to the valve that before or
decrementing by 1 valve
Next Valve or
incrementing by one valve
LCD Touch Panel Backup Terminal Operation
Installation and Operations Manual
VCIOM-17039-EN Rev. 0 April 2022
Section 7: LCD Touch Panel Backup Terminal Operation
7.2.1 Valve Control
Status of the desired valve must be displayed before attempting to control the valve. Select the
valve by clicking the Next or Go To Button to desired valve address or tag number is displayed.
CLOSE, STOP, OPEN valve control button may then be used to control the valve.
Refer to Figure 15.
7.2.2 Navigation Buttons
Back Button – This button will allow to go back to one screen (Valve).
Home Button – This button will take back to Home Screen from anywhere on the screen when there
is a Home Button presence.
Go To Button – This button will allow to jump to any selected valve from the list.
Refer to Figure 16.
Figure 16
Valve 1
Valve Address
Valve 2
Valve 3
Valve 4
Scroll Up and Down for
Alarms
Valve 5
more Valve
01/01 System Alarm - DXL Failed
Alarms Button – This button will take to Alarms List Screen.
NOTE
Alarms List Screen only display the Unit Alarm of each Valve when there is an actual Valve Alarm.
To view the Valve alarms, please go to Valve Control and Status Screen. System alarm can also be
viewed on the Alarms List Screen if there is System Alarms. The above information can also be seen
on the Alarm Bars on the bottom of any screen.
Next Button – This button will allow to go to Next Valve.
LCD Touch Panel Backup Terminal Operation
41
Section 7: LCD Touch Panel Backup Terminal Operation
April 2022
Network Fault Screen - To access the Network FLT Address screen.
With the Go To Button available in the Valve Control and Status screen, select Network Fault Screen.
Refer to Figure 17.
Figure 17
Network FLT Lo
Installation and Operations Manual
VCIOM-17039-EN Rev. 0
Network FLT Hi
Home
42
LCD Touch Panel Backup Terminal Operation
Installation and Operations Manual
VCIOM-17039-EN Rev. 0
Notes
April 2022
This page intentionally left blank
World Area Conguration Centers (WACC) offer sales support, service,
inventory and commissioning to our global customers.
Choose the WACC or sales ofce nearest you:
NORTH & SOUTH AMERICA
19200 Northwest Freeway
Houston TX 77065
USA
T +1 281 477 4100
Av. Hollingsworth
325 Iporanga Sorocaba
SP 18087-105
Brazil
T +55 15 3413 8888
ASIA PACIFIC
No. 9 Gul Road
#01-02 Singapore 629361
T +65 6777 8211
No. 1 Lai Yuan Road
Wuqing Development Area
Tianjin 301700
P. R. China
T +86 22 8212 3300
For complete list of sales and manufacturing sites, please visit
www.emerson.com/actuationtechnologieslocations or contact us at
info.actuationtechnologies@emerson.com
MIDDLE EAST & AFRICA
P. O. Box 17033
Jebel Ali Free Zone
Dubai
T +971 4 811 8100
P. O. Box 10305
Jubail 31961
Saudi Arabia
T +966 3 340 8650
24 Angus Crescent
Longmeadow Business Estate East
P.O. Box 6908 Greenstone
1616 Modderfontein Extension 5
South Africa
T +27 11 451 3700
EUROPE
Holland Fasor 6
Székesfehérvár 8000
Hungary
T +36 22 53 09 50
Strada Biffi 165
29017 Fiorenzuola d’Arda (PC)
Italy
T +39 0523 944 411
www.emerson.com
VCIOM-17039-EN ©2022 Emerson. All rights reserved.
The Emerson logo is a trademark and service mark of Emerson Electric Co.
All other marks are property of their respective owners.
The contents of this publication are presented for information purposes
only, and while every effort has been made to ensure their accuracy, they
are not to be construed as warranties or guarantees, express or implied,
regarding the products or services described herein or their use or
applicability. All sales are governed by our terms and conditions, which are
available on request. We reserve the right to modify or improve the designs
or specifications of our products at any time without notice.
Loading...