ProMinent Aegis II User Manual
ADDENDUM: Aegis II Communication Driver Card
Industrial Communication Driver Card
“Com Module”
Aegis II
Communication Driver Card Part Number: 734593
This document contains general information regarding the implementation of the ProMinent Industrial
Communication Card, “Com Module” into the Aegis II Controllers.
Revision D Part Number 1079218
Page 1 of 30
1. Description
2. Layman’s Glossary of terms
3. Multiple Protocols
4. Com Module Installation
5. Pyxis Sensor
6. The RTU Slave Connection
7. Gateway Settings
8. The Inputs and Outputs
9. Gateway Enclosure kits
10. Replacement Parts
1 Description
The ProMinent Industrial Communication Driver card (Com Module) provides the Aegis II with the ability to
interface with most industrial communication protocols thus providing the customer with live I/O values.
The Com Module includes:
o Two 4-20mA outputs, assigned as I/O points I and J
o One Modbus RTU (RS-485 serial) Master port for a Modbus Pyxis Fluorometer which will be assigned
point M. Any previous use of M will be removed. See section 5.
o Modbus RTU (RS-485 serial) Slave communication ports for use with a Modbus RTU network or any
Modbus RTU gateway.
o Can be ordered separately or with a power supply and terminal strip mounted in an enclosure. See
section 9.
Optionally, a dual 4-20mA input driver card can be added to this module. Currently, this is the only driver that can
be added. These inputs are assigned letters K and L in the controller program. If K and L were previously in use,
those programs are removed.
The Modbus connection is Read only. This connection will not allow any user to edit or modify any part of the
program. Only live I/O data is available. See a complete list of the controller I/O in section 8.
The Slave port can be directly connected to any Modbus RTU Master. RTU Masters includes various SCADA
systems as well as Gateways which convert the data to other Protocols.
Once the Com Module Slave port is connected to a Master, the second Com Module Slave port can be used to
‘Daisy Chain’ other Modbus RTU Slave devices to the same Master. See Daisy Chain example on page 10.
Note: A Master port can monitor multiple Slave devices. A Slave device must obey one and only one Master.
ProMinent has optional Gateway devices to convert this serial connection to Modbus TCP-IP (Ethernet), BACnet
MS/TP (RS 485-Serial) and BACnet IP (Ethernet). Each gateway can be chosen with or without UL certification.
Page 2 of 30
2 Layman’s Glossary of terms
PFC
Part #
Description
Link to Gateway manual
1092940
Modbus TCP Slave / Modbus Master – Converter UL Certified (RTA brand)
http://www.rtaautomation.com/userguides/BFR3000-NNA1_Userguide.pdf
1092941
Modbus TCP Slave / Modbus Master – Converter (ADFweb brand)
http://www.adfweb.com/download/filefold/modbus_TCP_Server_RTU_Master_MN67507_ENG.pdf
1092942
BACnet IP Slave / Modbus Master – Converter UL Certified (RTA brand)
http://www.rtaautomation.com/userguides/460MMBS-NNA1_Userguide.pdf
1092943
BACnet IP Slave / Modbus Master – Converter (ADFweb brand)
http://www.adfweb.com/download/filefold/mn67671_eng.pdf
1092964
BACnet MSTP Slave / Modbus Master – Converter UL Certified (RTA brand)
http://www.rtaautomation.com/userguides/460MMBMS-NNA4_Userguide.pdf
1092965
BACnet MSTP Slave / Modbus Master – Converter (ADFweb brand)
http://www.adfweb.com/download/filefold/mn67671_eng.pdf
TCP and IP indicate Ethernet type connections. MSTP and RTU indicates a serial connection.
In the chart below, the first gateway has the description “Modbus TCP Slave/Modbus Master”. This describes the
gateway as being a slave to the customers Modbus TCP(Ethernet) and passing through to our driver via the serial
port as a Master to our driver card slave connection. Therefore, in each of these descriptions, ‘Modbus Master’
refers to the serial connection between the Gateway and our communication driver.
3 Multiple Protocols
The following chart list Gateways available through ProMinent. A link is provided in the event you need a Gateway
manual.
Other Gateways are available from electronics vendors. These gateway part numbers do not include complete
kits. See section 9.
Any gateway that can convert from the user’s protocol to Modbus RTU can be used with the Com Module.
RTA gateways are UL certified. ADFweb brands are not.
An example of Gateways from RTA is shown below.
Allen Bradley PCL ASCII BACnet/IP Client
BACnet/IP Server BACnet MS/TP Initiator BACnet MS/TP Responder
DeviceNet Master DeviceNet Slave DF1 Devices
Ethernet/IP Adapter Ethernet/IP Scanner Modbus RTU Slave
Modbus TCP/IP Client Modbus TCP/IP Server Profibus Master
Profinet Controller Ethernet TCP/IP USB
Page 3 of 30
Dual 4-20mA Input
Driver
4 Com Module Installation
Com Module installed in expansion slot 3
From the factory, the Com Module will be installed in expansion slot 3. This card will not operate in expansion
slots 1 or 2. A plastic screw secures the card in place. The Com module may or may not have an optional driver
card attached. This optional driver is supplied with a plastic support screw as well. See optional driver card below.
Never install nor remove any driver or Com Module with power applied to the controller.
Instructions for installation, operation and maintenance of the 4-20mA input driver are in the controller operation
manuals.
The dual 4-20mA input driver can be installed in any expansion slot, Module 1, Module 2, Module 3 or in the feed
through slot on the communication driver card. See next page.
Page 4 of 30
Driver card installed on Com module
Component
Function
Description
Connection
XT1
Modbus RTU Master to ext. Slave
(For Pyxis)
resistor jumpers
Def: Failsafe
1 3 5
2 4 6
1 3 5
2 4 6
1 3 5
2 4 6
Failsafe termination
Standard termination
or SW control
No termination
(park position)
XT2
Modbus RTU Slave to ext. Master
For Gateways and direct connection
resistor jumpers
Default: Standard?
XA1
mA output Channel 1
Pin 1 = (-)
Pin 2 = (+)
XA2
mA output Channel 2
Pin 1 = (-)
Pin 2 = (+)
XB11
Modbus RTU Master to ext. Slave
Pin 1 = (A)
Pin 2 = (B)
Pin 3 = (GND)
XB12
Modbus RTU Master to ext. Slave
Pin 1 = (shield)
Pin 2 = (+24)
XB21
Modbus RTU Slave to ext. Master
Pin 1 = (A)
Pin 2 = (B)
Pin 3 = (GND)
Pin 4 = (shield)
XB22
Modbus RTU Slave to ext. Master
For Daisy chain
XE1
mA input Channel 1
(optional driver)
Pin 1 = (GND)
Pin 2 = (mA input)
Pin 3 = (+23)
XE2
mA input Channel 2
(optional driver)
Pin 1 = (GND)
Pin 2 = (mA input)
Pin 3 = (+23)
When a Com Module is added to expansion slot #3, the dual 4-20mA
outputs acquire the identification letters I and J. These are the letter
assignments for any card installed in this slot.
If the dual 4-20mA input driver is installed onto the Com Module, it is
represented by the letters K and L.
The Dual 4-20mA input driver card is the only card that can be added
to the Com Module.
The Wiring Terminal Table shows all connections to the Com Module
Wiring Terminal Table:
Page 5 of 30
5 Pyxis Sensor
Optional plug in 4-20mA input Module
Com Module
Pyxis sensor connection:
- XB11:01 -> Blue
- XB11:02 -> Yellow
Modbus RTU RS-485 Slave
Pyxis connection to Modbus Master RTU
Modbus RTU RS-485 Master
The Com card was constructed to accept a Modbus RTU version Pyxis Fluorometer. Connect the sensor as shown
below. This is currently the only input to the Master Modbus RTU terminals.
The fluorometer on input M can be monitored, used for control, show diagnostics and be calibrated through the
keypad or via a network connection using the Ethernet port or WiFi.
Consult the Aegis II and Pyxis manuals for programming instructions.
The Modbus RTU slave connections allow other entities to monitor this controller. The users can see the I/O
values but cannot edit them.
6 The RTU Slave Connection
Connect up to 120 communication driver card slaves to one master. The master can be the plant Modbus RTU
network or any number of Gateways. Currently, ProMinent has six gateways in stock that provide conversion to 3
protocols; Modbus TCP (Ethernet), BACnet IP (Ethernet) and BACnet MSTP (Serial). These gateways are available
with or without UL approval. The RTA brands are UL approved. The ADFweb brands are not UL approved and are
therefore available at a lesser price. See also section 9 for complete enclosure kits.
- XB11:03 -> Black
- XB12:01 (Blank)
- XB12:02 -> Red
Page 6 of 30
Gateway devices require a separate DC power supply. See instructions accompanying the Gateway.
Controller Modbus RTU Comm Module
Gateway Slave to
TCP Master
External Power
Max 24V
V DC: Min 12V
Max 5V
The next few illustrations depict ADFweb brand, non-UL approved gateways which convert the Com Module
Modbus RTU Slave to another Protocol. The connection to the Com card is via the Modbus Master serial port on
the Gateway. The Gateway Slave port connects to the plant network Master. This port can be serial or Ethernet as
you choose.
ADFweb Modbus TCP (Ethernet) Slave to Modbus Master. Not UL approved.
(Description explanation: ‘Modbus TCP Slave’ is the Gateway’s connection to the plant master via Ethernet.
‘Modbus Master’ describes the Gateway’s serial master to the communication card slave.)
Wiring the gateway terminal to Com card:
A+ to XB21 pin 1 (A), B - to pin 2 (B), Common (S) to pin 3 (Shown as a dash).
To load Configuration please refers to manufacture instruction manual MN67507_ENG section “UPDATE VIA
UDP:”
Gateway Part number:
1092941
Complete Kit part number:
1094286
See page 22 for kit
information.
Supply
V AC: Min 8V;
Customer Modbus-
Page 7 of 30
ADFweb BACnet IP (Ethernet) Slave to Modbus Master. Not UL approved.
Gateway Slave to
IP Master
External Power
Max 35V
Controller Modbus RTU Comm Module
(Description explanation: ‘BACnet IP Slave’ is the Gateway’s connection to the plant master via Ethernet. ‘Modbus
Master’ describes the Gateway’s serial master to the communication card slave.)
Gateway terminal to Com card: A+ to XB21 pin 1 (A), B - to pin 2 (B), Common (S) to pin 3 (Shown as a dash).
To load Configuration please refers to manufacture instruction manual MN67671_ENG section
“UPDATE DEVICE:”
Gateway Part number:
1092943
Complete kit part number:
1094287
See page 23 for kit
information.
Supply
V AC: Min 8V;
Max 24V
V DC: Min 12V
Customer BACnet
Page 8 of 30
ADFweb BACnet MSTP (Serial) Slave to Modbus Master. Not UL approved.
External Power
Max 35V
To Customer BACnet
MSTP Master
Controller Modbus RTU Comm Module
(Description explanation: ‘BACnet MSTP Slave’ is the Gateway’s connection to the plant master via Serial wiring.
‘Modbus Master’ describes the Gateway’s serial master to the communication card slave.)
Gateway terminal to Com card: A+ to XB21 pin 1 (A), B - to pin 2 (B), Common (S) to pin 3 (Shown as a dash).
To load Configuration please refers to manufacture instruction manual MN67671_ENG section
“UPDATE DEVICE:”
Gateway Part number:
1092945
Complete Kit part number:
1094290
See page 21 for kit
information.
Supply
V AC: Min 8V;
Max 24V
V DC: Min 12V
Page 9 of 30
Loading...