Technical Manual

3000/02-004
MODBUS TCP/IP
Communications Card
© 2002 - 2018 RTP Corporation
Specifications, information and graphics are subject to change without notice. Contact
RTP’s corporate office for specifics regarding any changes.
Not for reproduction in any printed or electronic media without express written consent
from RTP Corp.
All information, data, graphics and statements in this document are proprietary
intellectual property of RTP Corp. unless otherwise indicated and are to be considered
RTP Corp. confidential. This intellectual property is made available solely for the direct
use of potential or licensed RTP Corp. customers in their application of RTP Corp.
products, and any other use or distribution is expressly prohibited. If you have received
this publication in error, immediately delete, discard or return all copies to RTP Corp.

RTP Corporation
2832 Center Port Circle
Pompano Beach, FL 33064
Phone: (954) 597-5333
Internet: http://www.rtpcorp.com

Last Updated: 4/4/2018

TABLE OF CONTENTS

INTRODUCTION ........................................................................................ 4
SPECIFICATIONS ..................................................................................... 4
CABLING.................................................................................................... 5
FAILURE RATES IN ACCORDANCE TO IEC 61508 ............................... 7
REDUNDANT I/O CARDS PLACEMENT .................................................. 8
3000 Series System with I/O Cards................................................................ 8
3100 Series System with I/O Cards................................................................ 8
SOFTWARE CONFIGURATION ............................................................... 9
Firmware Upgrade ......................................................................................... 9
NetArrays Configuration ............................................................................... 10
Integer Error Detection ........................................................................... 11
Integer Status......................................................................................... 12
CPU Temp ............................................................................................. 12
Board Temp ........................................................................................... 12
Redundant Card ID ................................................................................ 12
MODBUS TCP Master Port .................................................................... 12
IP ........................................................................................................... 13
Subnet Mask .......................................................................................... 13
Node ...................................................................................................... 13
Response Timeout (ms) ......................................................................... 13
IP ........................................................................................................... 13
Unit ID .................................................................................................... 13
MODBUS TCP Slave Port ...................................................................... 14
Node ...................................................................................................... 14
Bool Input and Bool Output Point Groups ............................................... 15
Integer Input and Integer Output Point Groups ....................................... 17
Analog Input and Analog Output Point Groups ....................................... 19
COMPLIANCE WITH CE MARK ............................................................. 21
ENVIRONMENTAL CONDITIONS .......................................................... 23
REFERENCED COMPANIES .................................................................. 24
DEFINITIONS............................................................................................24
Introduction

The 3000/02-004 MODBUS TCP Communications Cards provides two 100 MHz Ethernet links for
TCP/IP communications with MODBUS-compatible controllers. It supports integration of an RTP
control system with equipment using the MODBUS TCP/IP protocol. Two front-panel mounted
RJ-45 connectors that accept standard Ethernet cables provide convenient connections to the
Ethernet ports. Cable lengths of up to 328 feet (100 meters) are supported.
The 3000/02-004 MODBUS TCP/IP Communications Card manages all aspects of the protocol
and data exchange including message translating and formatting, message checking and CRC
generation and checking, responding to MODBUS controllers with proper acknowledgements and
error or success codes, and protocol data byte ordering. This built-in intelligence unburdens the
RTP controller’s processor from the responsibility of managing the MODBUS protocol.
During each output transfer, the MODBUS card performs a MooN output validation test on the
data received from the node processor across the redundant I/O communications network
through its bottom two Ethernet ports. This insures the integrity of the communications channels.

Specifications
Card Address: Determined by onboard switch settings
Isolation: 500 VAC/DC Channel to RTP System
Standards Supported: MODBUS TCP Protocol (client mode or server mode)
Number of Ports: 2 TCP/IP
User Connectors: RJ-45
TCP Network Compatibility: 100/10Base-T
Ethernet Cable Length: 328 feet (100 meters) maximum, card to switch or card to
card
Ethernet Cable Type: STP Category 5 (EIA 568B, Cat 5) shielded Ethernet cables
with 4 twisted-pair wires and RJ-45 tips
Power Requirements: 5 VDC at 2.3 A
Supported Functions:
Code Function Supported Port
Master Slave
1 Read Coils  
2 Read Discrete Inputs  
3 Read Holding Registers  
4 Read Input Registers  
5 Write Single Coil 
6 Write Single Register 
15 Force Multiple Coils  
16 Preset Multiple Register  

Cabling
The MAC address used for raw Ethernet communication with the MODBUS TCP card is
determined by an assigned “chassis number”. This value is determined by DIP switch settings on
the card. Table 1 indicates the switch settings, and Figure 1 shows the location of these
switches:
Table 1: Chassis Address Selection Switch Positions
Chassis Number SW3 SW4 SW5 SW6
32 OFF OFF OFF OFF
33 ON OFF OFF OFF
34 OFF ON OFF OFF
35 ON ON OFF OFF
36 OFF OFF ON OFF
37 ON OFF ON OFF
38 OFF ON ON OFF
39 ON ON ON OFF
40 OFF OFF OFF ON
41 ON OFF OFF ON
42 OFF ON OFF ON
43 ON ON OFF ON
44 OFF OFF ON ON
45 ON OFF ON ON
46 OFF ON ON ON
47 ON ON ON ON
All other switches on DIP switches must be in OFF position during runtime.
Figure 1: 3000/02-004 MODBUS TCP Communications Card showing address 33.

Transmit or Receive MODBUS TCP/IP Master or

Slave Port A
Link Status

Transmit or Receive MODBUS TCP/IP Master or

Slave Port B
Link Status

Transmit or Receive
I/O Ethernet Connector A
Link Status

Transmit or Receive
I/O Ethernet Connector B
Link Status
 Table 2: Ethernet Cabling Matrix

Host I/O I/O I/O

Ethernet Switch Switch Switch Switch
Description Redundant ID Port A B C D
Node Processor Single (Non-redundant) J1 X
J2 X
J3 X
J4 X
A J1 X
J2 X
J3 X
J4 X
B J1 X
J2 X
J3 X
J4 X
C J1 X
J2 X
J3 X
J4 X
D J1 X
J2 X
J3 X
J4 X
Chassis Processor Main (00-15) J1 X
J2 X
Redundant (00R - 15R) J1 X
J2 X
MODBUS TCP/IP Main (32-47) J3 X
J4 X
Redundant (32-47) J3 X
J4 X
2-Channel Servo Main (32-63) J1 X
J2 X
Redundant (32-63) J1 X
J2 X
8-Channel Counter Main (32-63) J1 X
J2 X
Redundant (32-63) J1 X
J2 X

Failure Rates in Accordance to IEC 61508

The 3000/02-004 MODBUS TCP card cannot be used for safety-critical functions because the
MODBUS protocol itself is not a safety-certified communication protocol. However, the module is
non-interfering with other safety-critical modules and therefore can be used for non-safety related
functions.
Redundant I/O Cards Placement
3000 Series System with I/O Cards
Redundant I/O cards may be located in any chassis; there are no restrictions.

3100 Series System with I/O Cards

Redundant I/O cards in non-safety 3100 systems have the following chassis placement
restrictions. All Redundant I/O Cards may be located in the same chassis or in a single other
redundant chassis.
There can be multiple pairs of redundant chassis, but all redundant I/O cards must stay within the
same chassis pair as the other cards in the chassis pair.

This is an example of a good redundant configuration. All Redundant I/O cards are within two
chassis only:
Rack0 Slot0 is redundant with Rack0 Slot1 (OK-Redundant cards in same Rack)
Rack0 Slot2 is redundant with Rack1 Slot5 (OK-Redundant cards in first Rack and second Rack)
Rack0 Slot3 is redundant with Rack1 Slot10 (OK-Redundant cards in first Rack and second Rack)

This is an example of a bad redundant configuration. The redundant cards are distributed over
three chassis:
Rack0 Slot0 is redundant with Rack0 Slot1 (OK-Redundant cards in same Rack)
Rack0 Slot2 is redundant with Rack1 Slot5 (OK-Redundant cards in first Rack and second Rack)
Rack0 Slot3 is redundant with Rack2 Slot5 (Not OK-Redundant cards in first Rack and third Rack)

8
Software Configuration
Firmware Upgrade
In case where a new version of the 3000/02-004 MODBUS TCP/IP Card is required to be
installed, follow these steps:
1. Turn the power ON at all chassis within the target node.
2. From the Windows StartPrograms menu, launch the RTPNC utility.
3. In the Devices pane of the RTPNC utility window, select the node that corresponds to the
target node you are updating.
4. In the Files menu, select Download Card File…
5. Navigate to the NetSuite distribution CD and open the Firmware folder.
6. Open the 3000 MODBUS TCP Card folder.
7. Open the appropriate revision level folder, select the binary engine file (MODBUS.bin),
and click on the Open button. You will need to enter the download password to perform
the operation. The engine is downloaded to all 3000/04-000 MODBUS TCP/IP Cards.

Note: In the Device Status window, verify that all chassis received the
downloaded engine (MODBUS.bin) file.

8. Turn the chassis power supply to OFF.

9. Turn the chassis power supply to ON.
Alternatively, the MODBUS TCP Card can be configured in bootloader mode by setting switch 1
(SW1) to ON position (See Figure 1). Please note that in normal operation this switch should be
in OFF position:

1. Turn the chassis power supply to OFF (0).

2. Remove the 3000/04 MODBUS TCP/IP Card from the chassis.
3. Place the 3000/04 MODBUS TCP/IP Card in Boot Loader FTP Mode by moving SW1 to
the ON position.
4. Replace the 3000/04 MODBUS TCP/IP Card in the chassis.
5. Connect the J1 port, MODBUS TCP Port A to the Host network switch.
6. Turn the chassis power supply to ON (1).
7. To communicate with the 3000/04 MODBUS TCP/IP Card at its default address, run the
Project Tag Database Manager program and configure a device node with the IP address
89.89.89.89.
8. Run the configuration program RTPNC.
9. Select the device created in Step 7.
10. In the Files menu, select Download File…
11. Navigate to the NetSuite distribution CD and open the Firmware folder.
12. Open the 3000 MODBUS TCP Card folder.

9
 13. Open the appropriate revision level folder, select the binary engine file (MODBUS.bin),
and click on the Open button. The engine is downloaded to the 3000/04-000 MODBUS
TCP/IP Cards.
14. Turn the chassis power supply to OFF (0).
15. Remove the 3000/04 MODBUS TCP/IP Card from the chassis.
16. Place the 3000/04 MODBUS TCP/IP Card into the Normal Operating Mode. Make sure
that switch 1 (SW1) is in the OFF position (see Figure 1).
17. Replace the 3000/04 MODBUS TCP/IP Card in the chassis.
18. Connect the I/O Ethernet A into I/O network switch A and I/O Ethernet B into I/O network
switch B.
19. Turn the chassis power supply to ON (1).

NetArrays Configuration
The MODBUS TCP Card provides two MODBUS TCP protocol Ethernet ports. It acts as an
interface between the RTP target node and several controller nodes that may contain digital and
analog I/O points.

The MODBUS Serial Card supports the following functions:

Code Function Supported Port

Master Slave
1 Read Coils  
2 Read Discrete Inputs  
3 Read Holding Registers  
4 Read Input Registers  
5 Write Single Coil 
6 Write Single Register 
15 Force Multiple Coils  
16 Preset Multiple Register  

Card Properties

10
Integer Error Detection
The Error Detection input is an Int Variable that provides I/O card status information within the
user application program. The format of this variable is common to all RTP I/O cards. A Card
Timeout Error (Bit 0) will set the Error Latch bit (Bit14), which will remain set until this bit is
cleared to zero by an operator. While the Error Latch is set, the card will be offline and the target
node will not attempt to communicate with it. Note that most cards do not use all the status bits
shown. Any unused bits will always equal zero.

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
ERR DATA DATA CARD CARD CBL TIME
LTCH ERR INV ID ERR ERR OUT

Bit 14 Card Error Latch

Bit 9 Backplane Bus Data Error
Bit 8 Data Invalid
Bit 7 Card ID Does Not Match I/O Configuration
Bit 6 Card Setup Error
Bit 5 Cable Detect Error
Bit 0 Card Timeout Error

Bit 14 Card Error Latch

This status bit indicates that a Card Timeout Error occurred on the I/O card, and that it
has been taken offline. The card will not be initialized or placed online until this bit is
cleared in the project program or operator intervention.
Note: If this bit is set, it must be cleared to return the card to operation. The correct way
to clear this bit is to select the card’s icon in the I/O configuration Form while NetArrays is
operating in Debug mode and answer “Yes” to the prompt. See I/O Card Status and
Control. (It is also possible to change the value of this variable by forcing an Integer Bit
Variable object, with Bit 14 selected in the object's properties, to zero. Do not clear the
entire Error Detection Integer Variable to zero.)
Bit 9 Backplane Bus Data Error
This status bit is applicable only to I/O cards with Backplane Bus data checking
capability. It indicates that a data error was detected in a data or command transfer to or
from an I/O card.
Bit 8 Data Invalid
For a 3000 system, this status bit indicates that the I/O card is not ready to send valid
data.
Bit 7 Card ID Does Not Match I/O Configuration
This bit indicates that the ID code read from the I/O card does not match the card type
specified in the NetArrays I/O configuration.
Bit 6 Card Setup Error
Bit 5 Cable Detect Error
This bit indicates that one or more of the cables are not connected to the I/O card or
between the I/O card and the termination block.
Bit 0 Card Timeout Error
This bit indicates that there was no response from the I/O card. The card is not returning
a ready test signal, is offline, or has been removed from the chassis. This bit sets the
Card Error Latch (Bit 14).

11
Integer Status
This status word provides additional information on errors and configuration status of the card. It
has the following meaning:

11 Invalid configuration
13 Illegal message from Serial ModBus Card
14 Point Groups for Redundant Cards not the same

CPU Temp
This integer variable will hold the measurement of the card’s CPU Temperature. A rise in
temperature could indicate a fan failure; a temperature of 90º C or more indicates a critical error
condition.

Board Temp
This integer variable will hold the measurement of the card’s Temperature. A rise in temperature
could indicate a fan failure; a temperature of 90º C or more indicates a critical error condition.

Redundant Card ID
If the inputs of two of these cards are connected in a redundant configuration, a unique
Redundant Card ID must be assigned to the cards to identify them as being part of the same
parallel redundant group. ModBus TCP cards are considered to be connected in a redundant
configuration if the ports are connected to the same network. Assigning them to a redundant
group allows one card at a time to be active on the network.

The Redundant Card ID number assigned to one group must not be assigned to any other group
of redundant cards. If the cards are not connected in a redundant configuration, the Redundant
Card ID must be 0.

MODBUS TCP Master Port

The MODBUS TCP card has two Ethernet ports. Each of them can be configured either as
Master TCP Port or Slave TCP Port. It acts as an interface between the RTP target node and
several controller nodes that may contain digital and analog I/O points.

12
IP
This is the Ethernet IP address used by the MODBUS Master controller to communicate with the
Port. The format of an IP address is nnn.nnn.nnn.nnn, where nnn can be any number from 0 to
255. The default address is 89.89.89.89. Enter an IP address according to the format specified
for your network.

Note: The MODBUS TCP card has two ports. The IP address on these ports
must belong to two separate networks. E.g. they can be assigned 89.0.0.1 and
90.0.0.1 with subnet masks 255.0.0.0.

Subnet Mask
This field is the subnet mask to the Port. The format of the subnet mask is nnn.nnn.nnn.nnn,
where nnn can be any number from 0 to 255. The default mask is 255.0.0.0, which is suitable for
an internal or private network.

Node
This represents the target Slave MODBUS Node information that the RTP Master TCP controller
will be communicating with. The RTP Master TCP controller can communicate with several other
MODBUS Slave TCP controllers, therefore users can enter multiple MODBUS TCP nodes under
the MODBUS TCP Master Port. It provides the physical Ethernet connection between Port and a
number of Point Groups. Initially, there are no Nodes connected to the Port. Nodes are
configured by dragging a MODBUS TCP Node icon from the I/O Configuration toolbox to a
Node=Empty cell.

Response Timeout (ms)

Enter a response timeout, in milliseconds, that will determine the time period between retries. Its
value depends on the characteristics of the attached MODBUS devices. The timeout specified
for a node must be long enough to account for the longest delay between the node receiving a
command and sending a complete reply.

IP
This is the Ethernet IP address used by the MODBUS Slave TCP card to communicate with the
MODBUS controller. The format of an IP address is nnn.nnn.nnn.nnn, where nnn can be any
number from 0 to 255. The default address is 89.89.89.89. Enter an IP address according to the
format specified for your network.

Unit ID
This is the Unit ID number determined by the MODBUS slave device. This number will usually be
zero.

13
MODBUS TCP Slave Port
The MODBUS TCP card has two Ethernet ports. Each of them can be configured either as
Master TCP Port or Slave TCP Port. A slave port acts as a slave device on the MODBUS
network. It supports internal data arrays which are defined and accessed by the RTP system.

IP
This is the Ethernet IP address used by the MODBUS controller to communicate with the Port.
The format of an IP address is nnn.nnn.nnn.nnn, where nnn can be any number from 0 to 255.
The default address is 89.89.89.89. Enter an IP address according to the format specified for
your network.

Note: The MODBUS TCP card has two ports. The IP address on these ports
must belong to two separate networks. E.g. they can be assigned 89.0.0.1 and
90.0.0.1 with subnet masks 255.0.0.0.

Subnet Mask
This field is the subnet mask to the Port. The format of the subnet mask is nnn.nnn.nnn.nnn,
where nnn can be any number from 0 to 255. The default mask is 255.0.0.0, which is suitable for
an internal or private network.

Node
This provides the physical Ethernet connection between Port and a number of Point Groups.
There is only one Node connected to the MODBUS Slave TCP Port.

I/O Timeout (ms)

The I/O timeout parameter specifies a maximum time, in milliseconds, between I/O commands
from the Node Processor Card. The MODBUS Slave card will not respond to an inquiry from a
MODBUS master if there have been no data updates within this specified time. If the timeout
value is zero, this feature is disabled.

14
Bool Input and Bool Output Point Groups

Note: The total number of point groups configured in each MODBUS card must
be less or equal to 64.

Point Group
Adding a Bool Input Point Group or Bool Output Point Group to the node creates 16 Bool I/O
points.

Start Address
A start address for the Point Group must be entered here to create a contiguous MODBUS
message exchange within the controller node.

Inter Scan Delay (ms)

The Inter Scan Delay defines the scan rate, in terms of a minimum delay between accesses in
milliseconds. For example, if the delay is 100, the point group will not be scanned until 100
milliseconds have elapsed since the last time it was scanned.

Register Type
For Bool Point Groups only, this entry selects the source of the data. Select “Input” for MODBUS
Discrete Inputs data, or “Coil” for MODBUS Coils data. A master port cannot have an output
point group of type “Input”.

15
Integer Status
The Point Group Integer Status input is an Int Variable that supplies operating information for the
Point Group. Its meaning is as follows:
0 Normal
1 Exception status from MODBUS response message
256 Slave Point Group or Offline. Used for Signal Validation.

You can enable or disable Integer Status variable by clicking on Type column and select "Int" or
"Disable".

Bool Send Request

If this variable is configured in MODBUS TCP Master mode, then the values of the configured
MODBUS variables in the point group will be transferred, whenever the value of this Boolean
variable transitions from FALSE to TRUE. The variable is ignored in all other MODBUS
configurations.
You can enable or disable Bool Send Request variable by clicking on Type column and select
"Bool" or "Disable".

Channel
Up to 16 Bool input or output points can be configured for each Point Group. Initially, all I/O
points are enabled (Bool). To access a Bool input or output point, you must enable it (Bool).
Disabled points will not be scanned. The first point in a group should always be enabled,
disabled points within a group are allowed.

I/O Tag
Each Bool input or output channel is accessed by a Bool Variable object. NetArrays assigns a
Tag to each channel when the channel is enabled. Reconfigure the I/O Tag as required to match
the Module Form Bool Variable object that is used to access the channel.
Note! All unused un-terminated I/O points must be disabled in IO Configuration.

16
Integer Input and Integer Output Point Groups

Note: The total number of point groups configured in each MODBUS card
must be less or equal to 64.

Point Group
Adding an Integer Input Point Group or Integer Output Point Group to the node creates 16 Integer
Raw Count I/O points.

Start Address
A start address for the Point Group must be entered here to create a contiguous MODBUS
message exchange within the controller node.

Inter Scan Delay (ms)

The Inter Scan Delay defines the scan rate, in terms of a minimum delay between accesses in
milliseconds. For example, if the delay is 100, the point group will not be scanned until 100
milliseconds have elapsed since the last time it was scanned.

17
Register Type
For Int Point Groups only, this entry selects the source of the data. Select “Input Register” for
MODBUS Input Registers data or “Holding Register” for MODBUS Holding Register output data.
A master port cannot have an output group of type “Input”.

Integer Status
The Point Group Integer Status input is an Int Variable that supplies operating information for the
Point Group. Its meaning is as follows:

0 Normal
1 Exception status from MODBUS response message
256 Slave Point Group or Offline. Used for Signal Validation.

You can enable or disable Integer Status variable by clicking on Type column and select "Int" or
"Disable".

Bool Send Request

If this variable is configured in MODBUS TCP Master mode, then the values of the configured
MODBUS variables in the point group will be transferred, whenever the value of this Boolean
variable transitions from FALSE to TRUE. The variable is ignored in all other MODBUS
configurations.
You can enable or disable Bool Send Request variable by clicking on Type column and select
"Bool" or "Disable".

Channel
Up to 16 Integer input or output points can be configured for each Point Group. Initially, all I/O
points are enabled (Integer). To access an Integer input or output point, you must enable it
(Integer). Disabled points will not be scanned. The first point in a group should always be
enabled, disabled points within a group are allowed. The float selection is not applicable.

I/O Tag
Each Integer input or output channel is accessed by an Int Variable object. NetArrays assigns a
Tag to each channel when the channel is enabled. Reconfigure the I/O Tag as required to match
the Module Form Int Variable object that is used to access the channel.
Note! All unused un-terminated I/O points must be disabled in IO Configuration.

18
Analog Input and Analog Output Point Groups

Note: The total number of point groups configured in each MODBUS card
must be less or equal to 64.

Point Group
Adding an Analog Input Point Group or Analog Output Point Group to the node creates 16
floating-point engineering units I/O points.

Start Address
A start address for the Point Group must be entered here to create a contiguous MODBUS
message exchange within the controller node.

Inter Scan Delay (ms)

The Inter Scan Delay defines the scan rate, in terms of a minimum delay between accesses in
milliseconds. For example, if the delay is 100, the point group will not be scanned until 100
milliseconds have elapsed since the last time it was scanned.

19
Register Type
For Float Point Groups only, this entry selects the source of the data. Select “Input Register” for
MODBUS Input Register or “Holding Register” for MODBUS Holding Register output data. A
master port cannot have an output group of type “Input Register”.

Integer Status
The Point Group Integer Status input is an Int Variable that supplies operating information for the
Point Group. Its meaning is as follows:
0 Normal
1 Exception status from MODBUS response message
256 Slave Point Group or Offline. Used for Signal Validation.

You can enable or disable Integer Status variable by clicking on Type column and select "Int" or
"Disable".

Bool Send Request

If this variable is configured in MODBUS TCP Master mode, then the values of the configured
MODBUS variables in the point group will be transferred, whenever the value of this Boolean
variable transitions from FALSE to TRUE. The variable is ignored in all other MODBUS
configurations.

You can enable or disable Bool Send Request variable by clicking on Type column and select
"Bool" or "Disable".

Channel
Up to 16 Float input or output points can be configured for each Point Group. Initially, all I/O
points are enabled (Float). To access a Float input or output point, you must enable it (Float).
Disabled points will not be scanned. The first point in a group should always be enabled,
disabled points within a group are allowed. The Integer selection is not applicable.

I/O Tag
Each Float input or output channel is accessed by a Float Variable object. NetArrays assigns a
Tag to each channel when the channel is enabled. Reconfigure the I/O Tag as required to match
the Module Form Float Variable object that is used to access the channel.
Note! All unused un-terminated I/O points must be disabled in IO Configuration.

20
Compliance with CE Mark
This section describes how to install and operate RTP equipment for use in the European Union
(EU) to comply with the requirements of the CE Mark and its referenced standards. The
procedures in this section apply also to other environments where provisions of the EU’s EMC
and Low Voltage Directives are either required or desirable.
RTP Corporation has successfully tested and reviewed its products to the stringent requirements
of the European Union’s EMC Directives (2004/108/EC) and Low Voltage Directive (2006/95/EC).
In order for the equipment to meet the requirements of these directives, the equipment
must be installed and operated in accordance with these instructions.
These tests and reviews are in accordance to EN 61131-2:2007 as listed in the next section.
Information on the tests performed and the standards involved is available from RTP Corporation.
To comply with the requirements of the CE Mark and its referenced standards, the system
integrator, installer, and end user must store, integrate, install, and operate this equipment in
accordance with the following guidelines.
1. Compliance with all product specific instructions (including but not limited to storage
instructions, installation instructions, operating instructions, maintenance instructions,
disposal instructions, and specifications) is required.
2. RTP equipment is rated for use in Installation Category (Overvoltage Category) II and
Pollution Degree 2 environments in accordance with standard IEC 664.
3. To assure that an Operator is not exposed to electrical hazards, all equipment capable of
electrical hazards must be housed in a grounded enclosure (equipment cabinet/rack) that
limits access to the equipment only to Service Personnel. Limited access may include
enclosure doors and side panels, which are locked or require a tool to open. To assure
compliance with the EMC requirements, the equipment must be housed in an enclosure
(equipment cabinet/rack) that provides EMC shielding. Compliance testing was
performed in a shielded equipment rack provided by Hoffman Concept® Wall Mounted
Enclosure model number CSD242420. To assure compliance, the equipment must be
installed in this style cabinet, or one with similar or greater RF attenuation characteristics.
The cabinet should be outfitted with continuous copper finger gasketing and copper foil
along all seams and joints.
4. The Service Personnel must be trained to operate the equipment and must be aware of
the potential of electrical hazards of the equipment and of the field I/O signals connected
to the equipment.
5. Hazardous voltage warning labels must be applied to the enclosure doors adjacent to the
locking mechanisms to warn the Service Personnel that hazardous voltages are
contained within the enclosure, if modules carrying 120 V and above are used.
6. Hazardous voltage warning labels also must be applied to the termination modules
(which carry 120 V and above), adjacent to the external connectors, to warn the Service
Personnel that hazardous voltages are present at the module's terminal blocks.
7. To assure compliance with the EMC requirements, the equipment must have all
communications, power, and field signal cabling exiting the enclosure enclosed in metal
conduits or shielded wireways. These conduits must provide EMI/RFI shielding and must
be terminated at the enclosure shell. There must be no uncovered openings in the
cabinet. Connections between the cabinet and conduit must be made with conduit
connectors making good (low impedance) electrical contact to the enclosure. Input
mains power to the enclosure and mains power fed to switching digital output I/O cards
and modules must be filtered by AC mains filters with attenuation characteristics of

21
 Corcom VR series filters or with similar filters with equal or greater attenuation
characteristics.
8. DC input mains power to the enclosure and mains power must be filtered by a DC mains
filters with attenuation characteristics of Corcom 6EH1 series filters or with similar filters
with equal or greater attenuation characteristics.
9. Insulation strip length of 0.26 inches (6.5 mm) is required on all field wirings to the I/O
card termination modules.
10. The disposal of any electronic products must be in accordance with local regulations (e.g.
Directive 2002/96/EC of the European Parliament and of the Council on waste electrical
and electronic equipment). Some RTP Corporation products contain materials that may
be detrimental to the environment. These materials may include, but are not limited to
lead (in solder) and lithium (in batteries).
11. Prior to storage or shipping, the equipment must be packaged in accordance with the
following guidelines:
● Inventory all items and inspect all components for damage.
● Verify that all fasteners are properly tightened and that the chassis I/O module
retaining bar is properly installed.
● Wrap the chassis assembly in plastic bubble wrap.
● Select a suitable shipping box that provides at least 1½ inches of space between the
equipment and all sides of the box. This space shall be tightly packed with packing
peanuts or bubble wrap to protect the equipment during storage or shipping.
● Close and secure the box with suitable packing tape.
● Do not stack boxes more than three high. Store the boxes in a protected, dry
environment. Do not expose the boxes to rain or environmental conditions beyond
the ranges specified for the equipment in this document.

22
Environmental Conditions
The modules are rated for the following environmental conditions:

Specification Type Recommended Range Test Specification

IEC 60068-2-30, Db
Operating Temperature -20 ºC to 60 ºC
RTP Type Testing
Operating Temperature Change 10 ºC/minute IEC 60068-2-14 Test Nb
Operating Humidity 10% to 95% non-condensing IEC 60068-2-30, Db
IEC 60068-2-1 Tests Ab, Ad
Storage Temperature -40 ºC to 85 ºC IEC 60068-2-2 Tests Bb, Bd
RTP Type Testing
Storage Temperature Change 10 ºC/minute IEC 60068-2-14 Test Na
Storage Humidity 0% to 100% condensing IEC 60068-2-30, Db
Vibration 9 Hz to 150 Hz at 1 g IEC 60068-2-6, Fc
Mechanical Shock 15 g for 11 milliseconds IEC 60068-2-27, Ea
Electrostatic Discharge Immunity ±6 kV contact IEC 61000-4-2
80 MHz to 1 GHz at 20 V/m
1 GHz to 2.1 GHz at 10 V/m
Radiated E-Field Immunity IEC 61000-4-3
2.1 GHz to 2.5 GHz at 5 V/m
2.5 GHz to 2.7 GHz at 1 V/m
Ethernet Line Burst Immunity ±2 kV IEC 61000-4-4
Ethernet Line Surge Immunity ±2 kV IEC 61000-4-5
Ethernet Line Conducted RF
150 kHz to 80 MHz at 10 V IEC 61000-4-6
Immunity
Pulsed Magnetic Field 300 A/m IEC 61000-4-9

Modules can be ordered with optional HumiSeal© conformal coating. In this case, the modules
can be installed in G3 harsh environmental conditions as defined in standard ISA–S71.04–1985.

This equipment has been tested and found to comply with the limits for a Class A digital device,
pursuant to Part 15 of FCC Rules. These limits are designed to provide reasonable protection
against harmful interference when the equipment is operated in a commercial environment. This
equipment generates, uses, and can radiate radio frequency energy and, if not installed and used
in accordance with the instruction manual, may cause harmful interference to radio
communications. Operation of this equipment in a residential area is likely to cause interference
in which case the user will be required to correct the interference at his own expense.

This Class A digital apparatus complies with Canadian ICES-003.

Cet appareil numérique de la Classe A est conforme à la norme NMB-003 du Canada.

23
Referenced Companies
Corcom Inc.; Libertyville, Illinois, USA; 708-680-7400
Hoffman; Anoka, Minnesota, USA; 763-422-2178

Definitions
OPERATOR is any personnel other than SERVICE PERSONNEL. Requirements
assume that the OPERATOR is oblivious to electrical hazards, but does not act
intentionally in creating a hazard.
SERVICE PERSONNEL are assumed reasonably careful in dealing with obvious
hazards.
CE Conformité Européenne
EMC Electro-Magnetic Compatibility
EMI Electro-Magnetic Interference
EC European Community
EN European Norm
ESD Electro-Static Discharge
EU European Union
IEC International Electrotechnical Commission
MPU Main Processing Unit
PLD Programmable Logic Device
RF Radio Frequency
RFI Radio Frequency Interference
SOE Sequence of Events

24