RTP 3000/06 User manual

Technical Manual
3000/06
Node Processor

2
© 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: [phone]
Internet: http://www.rtpcorp.com
Last Updated: 4/4/2018

3
TABLE OF CONTENTS
INTRODUCTION........................................................................................4
SPECIFICATIONS.....................................................................................6
FAILURE RATES IN ACCORDANCE TO IEC 61508 ...............................8
HARDWARE CONFIGURATION...............................................................9
Switches........................................................................................................9
Cabling ..........................................................................................................9
SOFTWARE CONFIGURATION..............................................................12
Editing the Configuration File.......................................................................12
Configuration Parameters............................................................................14
ipaddress, ipaddress_b, ipaddress_c, ipaddress_d................................14
Subnetmask...........................................................................................15
Scan cycle..............................................................................................15
Nodenum...............................................................................................15
Maxconn ................................................................................................15
Peer alltime............................................................................................16
Ip route...................................................................................................16
Maxpgm.................................................................................................16
Udl mem.................................................................................................17
Host activity max....................................................................................17
Tcp min rt timeout ..................................................................................17
Dsvc max points.....................................................................................17
Id_a, id_b, id_c, id_d..............................................................................17
redundant...............................................................................................17
Firmware Upgrades .....................................................................................18
Firmware Upgrade Order .......................................................................18
Firmware Upgrade Procedure................................................................18
NetArrays Configuration...............................................................................19
I/O Configuration....................................................................................19
Diagnostic Information............................................................................23
Device Status Window.................................................................................26
COMPLIANCE WITH CE MARK .............................................................28
ENVIRONMENTAL CONDITIONS...........................................................30
REFERENCED COMPANIES..................................................................31
DEFINITIONS........................................................................................... 31

4
Introduction
The 3000/06 Node Processor card is the Main Processing Unit (MPU), which solves user application logic,
communicates with the 3000/01 Chassis Processor cards and also host applications. It can be configured
single, dual redundant, triple redundant or quad redundant.
Two indicator LEDs are located near the top of the front panel. The left LED indicator displays the overall
health status of the card. If this LED is on, the card is functioning normally; if it is off, the card has detected
an error or is offline. The right indicator LED indicates the node processor status as shown below:
On If left LED is On - Primary without errors
If left LED is Off - WWDT/WDT expires, Board/CPU temperature is > 90
degrees Celsius, or expiration of 2-0 Tolerance Time
1 Blink Primary with chassis/card error or forced read-only variable
2 Blinks Redundant without errors
3 Blinks Redundant with chassis/card error or forced read-only variable
4 Blinks Bootloader mode
6 Blinks Offline (Insufficient I/O communication links)
Off No valid program loaded
If the left LED on the top is off and the right LED on the top is on, then the windowed watchdog timer on
the node processor is expired due to an error (node is running faster or slower than it is configured in
WWDT) or Board/CPU temperature was higher than temperature defined in node processor shutdown
object or 2-0 Tolerance Time, defined in node processor shutdown object, is expired. 2-0 Tolerance time
should be configured only when you operate the SIS with redundant Node Processors. Setting a non-zero
value (between 0.01 seconds and 327.67 seconds) enables the SIS to start the Elapsed timer; when it is
Latched true in redundant mode (more than one node processor had come on line and operational) and
only one Node Processor is left online and operational. If successful redundant Node Processor operation
is not established within the 2-0 Tolerance Time, the remaining Node Processor CPU is turned off,

5
effectively de-energizing all outputs and putting the SIS into a safe state. It is necessary to de-energize
node processor card to put card in normal function again.
Each Ethernet port on the card has two LED’s: The top LED turns on whenever there is transmit / receive
activity. The bottom LED on the Ethernet port indicates the link status: If the link is functioning normally, it
will turn on.
Power
ON Power on and within limits
OFF Power off or error
Transmit/Receive
ON Message transmit/receive
OFF No link activity
Link Status
ON Link is functioning normally
OFF Link error
Node Processor Status
ON Primary, no errors (If Power
LED is ON)
If Power LED is OFF and NP
Status LED is ON it indicates
that Node is in Reset because
WWDT/WDT is expired or
board/CPU temperature was
too high or 2-0 Tolerance Time
is expired
1 Blink Primary, chassis/card error or
forced read-only variable
2 Blinks Redundant, no errors
3 Blinks Redundant, chassis/card error
or forced read-only variable
4 Blinks Bootloader mode
6 Blinks Node Processor Offline
OFF No valid Program loaded
Figure 1: 3000/06 Node Processor Front Panel
Host Network A
I/O Network B or
Host Network B
I/O Network C
I/O Network D
Transmit/Receive
Link Status
Transmit/Receive
Link Status
Transmit/Receive
Link Status
Transmit/Receive
Link Status
Node
Power Processor
Status
3000/06

6
Specifications
Module Safety Integrity Level: SIL-2 (SIL-3 in redundant configuration)
Card Address: Determined by software configuration
Watchdog Timers:
Fixed: 600 ms maximum
Windowed: 3 ms minimum, 80 ms maximum
Host Network Compatibility: 1 GB TX full-duplex with auto-negotiation
I/O Network Compatibility: 1 GB TX full-duplex with auto-negotiation
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
Program Memory: Up to 4096512 bytes for PGM files
Up to 1500000 bytes for UDL files
Data Memory Type: SDRAM
Program Memory Type: IDE Disk Chip
Power Requirements: +5 VDC @ 1.75 Amps
Battery: Processor contains a lithium battery (see Figure 2) that powers the
time-of-day clock whenever power to chassis is turned off. The
expected life span of this battery is five (5) years. Replace this
battery (see Figure 2) only with an agency-approved battery of the
same voltage and capacity (3V, 180 mAh). Two recommended
replacements are:
Panasonic part number BR 2032
Varta part number CR 2032
WARNING! If you replace the battery with an incorrect type, it may
explode.
Do not dispose of batteries in the trash. Dispose of batteries
according to local regulations.
Please recycle according to local regulations.
Programming Tools: NetArrays Developer Studio
Programming Languages: Flow Charts, Objects, Structured Text, C/C++, Fuzzy Logic
Processor Utilization: Processor can be configured for cyclic execution: 5 ms, 10 ms, 15 ms,
20 ms or 25 ms. Processor utilization is measured via Node Info
Object, which reports the reserve time in each execution cycle.
Minimum 1 ms reserve time is recommended.
Processing of I/O: The 3000/06 Node Processor communicates each scan cycle with
3000/01 Chassis Processor. Inputs from the modules are acquired by
the 3000/01 Chassis Processor, transferred to the 3000/06 Node
Processor and are processed in the user application program after
two scan cycles. Computational results of the user application
program are sent back to the 3000/01 Chassis Processor to activate
the output modules.

7
Self-Tests and Diagnostics: Processor performs a Power-On-Self-Test (POST) upon cold startup
or if instructed by the Node Shutdown object. POST includes
comprehensive memory tests and verification of the onboard
peripherals. Runtime diagnostics tests CPU, registers and allocated
memory.

8
Failure Rates in Accordance to IEC 61508
The following table summarizes the failure rates of the modules, which were calculated from Failure Mode
and Diagnostic Effects in accordance to standard IEC 61508. The information can be used in calculating
probability of dangerous failures using Reliability Block Modeling or Markov Modeling. Such modeling
should consider redundant node processors in a 1oo2, 2oo3 or 3oo4 configuration.
Model
3000/06 Atom NP
Safety Integrity Level
2
Safe Failure Fraction:
99.71%
Diagnostic Coverage:
99.48%
Failure Rates In Common Circuitry:
Safe Detected
4.3012E-07
Safe Undetected
4.3447E-09
Dangerous Detected
8.7354E-07
Dangerous Undetected
4.5318E-09
Don't Care
6.6874E-07
Failure Rates In Per Channel Circuitry:
Safe Detected
2.7041E-07
Safe Undetected
2.7314E-09
Dangerous Detected
2.5215E-07
Dangerous Undetected
2.0830E-10
Don't Care
1.3170E-07
Average Frequency of a Dangerous Failure per Hour (1oo1D):
4.7401E-09
Average Frequency of a Dangerous Failure per Hour (1oo2D):
2.8012E-10
Average Frequency of a Dangerous Failure per Hour (2oo3D):
6.5874E-11
Average Frequency of a Dangerous Failure per Hour (3oo4D):
3.5238E-11
Mean Time to Restoration for 1oo2D (SIL-3) configurations:
≤ 9 days
Mean Time to Restoration for all other configurations:
No restriction
In dual redundant configurations, the users must exchange the card within Mean Time to Restore (MTTR ≤
9 days) in order to remain within SIL 3 requirements. Otherwise the card will continue to operate in
degraded SIL 2 mode.

9
Hardware Configuration
Switches
Figure 2: Node Processor Configuration Switch Settings
For normal run mode all DIP switches on SW2 must be in the OFF position.
Bootloader mode - set DIP switch SW2-1 or SW2-3 to the on position.
Cabling
The top port of the Node Processor is dedicated to host communications.
Redundant host communication ports of Node Processors can be connected to one or more Ethernet
networks (shown in Figure 3 with Switch 1and Switch 2 respectively).
Non-Redundant node processor configurations use port B for redundant host communications.
Redundant node processors use port B for inter-processor and I/O communications (as needed if
redundant chassis processors are configured) as shown in Figure 3 with Switch B. If redundant chassis
processors are not used, the port still should be connected to I/O Switch B.
The C and D ports of the node processor are always dedicated to I/O communications.
The node processor uses the I/O ports to communicate with I/O ports on the chassis processor, in effect
creating I/O Path B, I/O Path C and I/O Path D (shown in Figure 3 with Switch B, Switch C and Switch D
respectively).
Refer to Table 1 for a summary of Ethernet cabling.
Battery

10
Figure 3: 3000-T Node with Four Chassis and Host with two Ethernet networks

11
Table 1: Ethernet Cabling Matrix
Description
Redundant ID
Ethernet
Port
Host
Switch
A
I/O
Switch
B
I/O
Switch
C
I/O
Switch
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

12
Software Configuration
Editing the Configuration File
The 3000/06 Node Processor must be configured correctly, before the user application program is fully
deployed. The 3000/06 Node Processor is shipped either with a default IP address (89.89.89.89) or as
marked on the chassis.
1. Ensure that redundant Node Processors are turned off.
2. Use the Project Tag Database Manager (PTDBM.exe) and configure the default IP or the factory
configured IP address(es).
3. Ensure that the PC’s network interface is configured in the same IP domain as the 3000/06 Node
Processor. Issue a ping command from the PC to the configured IP address to verify connectivity.
If there is no response from the controller, set DIP SW2-1 (or DIP SW2-3) on the Node Processor
card (see Figure 2) in the ON position; remove Ethernet cables on ports J2, J3 and J4; and turn on
the Node Processor. This will put the 3000/06 Node Processor into Bootloader mode, which stops
executing any user application logic and communicates for configuration changes over the default
IP address 89.89.89.89.
4. Run the Node Configuration program (RTPNC.exe) and select the device created in step 1.
5. Right click on the file name VIK2K1.CFG and select Upload from the pull-down menu. (Uploads
and downloads are password protected, so you will need the download password to upload the
configuration file. The default password is “rtp”.):
6. Configure the Node Processor parameters and click the Download button to write the configuration
to the Node Processor. Enter the password when prompted (Uploads and downloads are
password protected, so you will need the download password to download the configuration file.
The default password is “rtp”.).

13
7. Reconnect all Ethernet cables and set DIP SW2-1 (or DIP SW2-3) on the Node Processor card
(see Figure 2) back to its OFF position (if changed in step 3) and power-cycle the 3000/06 Node
Processor.
8. Download the user application program (with the correct I/O Configuration) from NetArrays.
From the Device Status window, verify that the user application program is running.
9. For redundant configurations reconnect the Ethernet cables and turn the power on at the “B”, “C”
and “D” Node Processors. The configuration parameters will be transferred to the redundant
processors.
10. For redundant configurations, use again PTDBM application to configure IP addresses for all Node
Processors of the device.

14
Configuration Parameters
Use the Device Configuration Editor to change the configuration parameters from their default settings. To
change an entry, move the mouse pointer to the parameter, select it, and type the newvalue. When
finished, click on the Download button to write the configuration file to the target device. The VIK2K1.CFG
configuration file parameters are:
ipaddress, ipaddress_b, ipaddress_c, ipaddress_d
These IP address parameters specify the Ethernet IP address used to communicate with the node
processor card(s). The format of an IP address is nnn.nnn.nnn.nnn, where nnn can be any
number from 0 to 255. The Ethernet IP address must match the IP address assigned to the device
in the NetArrays Project Tag Database Manager (Default address: 89.89.89.89). Enter the IP
address specified in the device configuration for the target node, otherwise leave default value
0.0.0.0. Please note that the IP address cannot contain leading zeros: e.g. 089.089.089.120 is not
a valid IP address.
These entries define up to four IP addresses:

15
For RTP3000S and RTP3000D systems:
Configure ipaddress and ipaddress_b. Note! It is recommended to configure ipaddress
and ipaddress_b to be on different networks.
Note! For RTP3000S system, use PTDBM application and configure node as Single and
define IP Address and IP Address2 for redundant host communication.
For RTP3000T systems:
Configure ipaddress for node processor A, ipaddress_b for node processor B and
ipaddress_c for node processor C.
For RTP3000Q systems:
Configure ipaddress for node processor A, ipaddress_b for node processor B, ipaddress_c
for node processor C and ipaddress_d for node processor D.
If the IP address parameter for a node processor is not configured, and this node processor is
inserted into the RTP3000 system, then the following display status message will be printed:
Node Processor %s –Requires Configuration File IPAddress
where %s is the newly inserted new node processor B, C or D, which is not configured in the
configuration file. Likewise, if the user application program has less node processors configured
than what is physically configured then the following display status message will be generated:
Node Processor %s –Requires I/O Configuration Node Update
where %s is the newly inserted new node processor B, C or D, which is not configured in the
NetArrays user application program file’s IOC page.
Subnetmask
The subnetmask parameter specifies the subnet mask to the processor card. The format of the
subnet mask is nnn.nnn.nnn.nnn, where nnn can be any number from 0 to 255 (Default value is
255.0.0.0, which is suitable for an internal or private network).
Scan cycle
If the configuration file is deleted, the default scan_cycle entry is set to 250, which equates a fixed
scan rate of 25 milliseconds or 40 passes per second. For RTP3000S, RTP3000D, RTP3000T
and RTP3000Q systems, this parameter may be changed to a scan_cycle of
50, for a fixed scan rate of 5 milliseconds or 200 passes per second or
100, for a fixed scan rate of 10 milliseconds or 100 passes per second or
150, for a fixed scan rate of 15 milliseconds or 67 passes per second or
200, for a fixed scan rate of 20 milliseconds or 50 passes per second or
250, for a fixed scan rate of 25 milliseconds or 40 passes per second.
Nodenum
A node number is required for Peer-to-Peer communications in a multiple-node configuration.
Node numbers can range from 0 to 99. Each peer node must have a unique node number from 1
to 99. A node number of 0 (zero) disables Peer-to-Peer communications for the node (Default
value is 0). The assigned node numbers are then used for the creation of peer variables in the
NetArrays project program.
Maxconn
The maxconn parameter specifies the maximum number of TCP/IP network connections (sockets)
allowed. The maximum value is 215 (Default value is 50).
For example, each host that connects to this node consumes one connection, each peer node that
receives data from this node consumes one connection, and each peer node that sends data to
this node consumes one connection. The total number of all these connections must not exceed
the value entered for this parameter.

16
Peer alltime
To reduce network traffic during normal peer-to-peer operation, only those peer variables that
changed are sent to the other nodes. However, the processor periodically sends all of its peer
variables to the other nodes. The peer_alltime parameter specifies how often these “all peer
variable” transfers occur (Valid range: 0 to 2147483647 in 10-millisecond increments –Default
value: 6000 every 60 seconds).
Ip route
The IP route parameter is required if the node must respond to communications from a
host located on another network. If all the nodes and hosts reside on the same network, this
parameter is not required and should be left at its default value.
The format of an IP route is composed of three elements, each separated by a space as follows:
destination mask gateway. The format of each of the three elements is
nnn.nnn.nnn.nnn, where nnn is a number from 0 to 255. Up to five IP routes may be entered in
this parameter, each separated from the other by a space. There are three types of IP routes that
may be added in this parameter: host routes, network routes, and a default route. The routes
specify networks (destination AND mask) that must be different than the one containing the RTP
target node as specified in the ipaddress parameter. Be careful not to enter the ipaddress into the
ip route parameter
The default route is the simplest means to access a host on another network. It takes the
form: 0.0.0.0 0.0.0.0 gateway, where gateway is IP address of the gateway computer, or
router, that connects the target node’s network to the network where the host resides.
(The destination and mask must be 0.0.0.0.) Note that only one default route is allowed in the IP
route parameter. Example: 0.0.0.0 0.0.0.0 10.100.100.65 triplet entry in the ip route parameter to
reach all other networks. In this example, the gateway 10.100.100.65 is in the same network as
the RTP target node, as specified in ipaddress parameter (e.g. 10.10.10.64).
A host route defines one specific host on another network. It takes the form: destination
255.255.255.255 gateway, where destination is the IP address of the host and gateway is the IP
address of the gateway computer connecting the two networks. (The mask must be
255.255.255.255.)
A network route specifies a route to a subnet of hosts which is a route that will match multiple IP
addresses. It takes the form: destination mask gateway, where destination is the IP address of the
host, mask is a subnet mask that masks all but the intended range of addresses, and gateway is
the IP address of the gateway computer connecting the two networks. For example, the network
route 192.200.100.0 255.255.255.0 gateway would provide valid routes to all hosts with IP
addresses between 192.200.100.1 and
192.200.100.255 on the network connected by the gateway, or router, defined by gateway.
The gateway, or router, must have an IP address (gateway) that is within the same network as
specified in the ipaddress configuration parameter.
Note: Do not change the ip_route parameter for communications in Safety Instrumented Systems.
Safety-critical communication messages (e.g. peer-to-peer messages) should not be routed.
Maxpgm
The maxpgm parameter specifies the maximum amount of memory (in bytes) allocated for the
project program. The default value is 1,843,712 bytes (Valid range: 307,712 to 4,096,512). In
RTP3000M and RTP3100M, the default value is 1,048,576 bytes (Valid range: 307,712 to
1,048,576). You must allocate sufficient memory for the project program. If the project program
is too large, an error message is generated during the attempted download.

17
Udl mem
The udl_mem parameter specifies the amount of memory (in kilobytes) allocated for the UDL files
(file extension .UDL) included with the project program in the node processor. The value specified
must be as large as, or larger than the actual UDLs (Default value: 512 kilobytes –Valid range: 0
to 1500 kilobytes). The 3000/01-0YZ Counter Cards and 3000/01-0YZ Servo Controller Cards
have 512 kilobytes of fixed memory allocated for the UDL files (file extension .UDF).
Output Disable Type (RTP3100S or 3100D only)
This entry, if exists, determines the action taken by a non-safety I/O node if its Chassis Processor
stops receiving valid output messages from the processor card. Valid entries are 0 and 1. If set to
0, the Chassis Processor will disable all I/O card outputs (zero / OFF / de-energize). If set to 1, it
will use the “default” parameter of the programmed I/O card output channel. The default value is 0.
Host activity max
This entry sets the threshold in recognizing a flood condition on the host network. The default
setting is 300 interrupts per scan cycle and is based on 25 ms scan cycle setting. This parameter
is scaled automatically with the scan cycle setting, for example: If the scan cycle is at 10
milliseconds, then this parameter is scaled internally to 240 and if the scan cycle setting is 5
milliseconds, then this parameter is scaled to 180 internally. Setting this parameter to a large
number (e.g. 1000), disables checking of flood on the host network.
Tcp min rt timeout
This parameter specifies the TCP/IP reply timeout period. Do not modify and leave this parameter
to its default configuration: 300 milliseconds.
Dsvc max points
The maximum number of points that can be serviced to host applications (excluding NetArrays).
Default value is 10000. This parameter should not be modified.
Id_a, id_b, id_c, id_d
These parameters designate, which processor will be designated as A, B, C or D processor.
These parameters are automatically programmed by the firmware. Modification of these
parameters is not required.
redundant
Modify this parameter based on the type of system.
For non-redundant systems (RTP3000S), this parameter should to be set to 0 (zero).
For redundant systems (RTP3000D, RTP3000T, RTP3000Q) this parameter should be set to 1
(one).

18
Firmware Upgrades
Firmware updates are required when you upgrade to a new version of NetSuite. The required files are
included in the NetSuite distribution CD. You must follow this procedure in the order presented to
successfully update the firmware.
Firmware Upgrade Order
When upgrading firmware, the following order should be followed:
1. Upgrade 3019 MODBUS Serial card firmware and PLD.
2. Upgrade 3018 HART card firmware and PLD.
3. Upgrade 3000/01-0YZ Counter card firmware and PLD.
4. Upgrade 3000/01-0YZ Servo card firmware and PLD.
5. Upgrade 3000/01 Chassis Processor firmware and PLD.
6. Upgrade 3000/06 Node Processor firmware.
7. Lastly, power cycle in order for the new firmware and PLD to take effect.
If the order is not followed, then you might not be able to communicate to the cards intermittently as a
result of firmware incompatibilities. In this case, the firmware of any card can still be updated by means of
setting it into Bootloader mode.
Firmware Upgrade Procedure
1. Ensure that all redundant node processors are powered up and running.
2. Copy the Node Processor firmware from the distribution CD into a temporary folder (Located under the
Firmware 4000 Directory).
3. Launch NetArrays and open the Device Status window for the Node to be upgraded. Leave the
window open.
4. If no communication can be established in step 3, ensure that the PC’s network interface is configured
in the same IP domain as the 3000/06 Node Processor. Issue a ping command from the PC to the
configured IP address to verify connectivity. If there is no response from the node, set DIP SW2-1 on
one Node Processor card (see Figure 2) in the ON position; remove Ethernet cables on ports J2, J3
and J4; and turn on the Node Processor. This will put the 3000/06 Node Processor into Bootloader
mode, which stops executing any user application logic and communicates for configuration changes
over the default IP address 89.89.89.89. You will need to configure this default IP address in the
Project Tag Database Manager also. Please note that Device Status window is not available when the
processor is in Bootloader mode.
5. Launch RTPNC.
6. From the left Devices tree-view, select the node that needs firmware upgrade. If the Node Processor
was put into Bootloader mode, select the node with the default IP address.
7. From the File menu, select Download File…
8. Select the vik4k.bin file, which was copied in step 2.
9. Enter the password when prompted (Uploads and downloads are password protected, so you will
need the download password to download the firmware. The default password is “rtp”.).
10. In NetArrays Device Status window, ensure that all redundant Node Processors report receiving the
file vik4k.bin. Please note that Device Status window is not available when the processor is in
Bootloader mode.
11. Reconnect all Ethernet cables and set DIP SW2-1 (or DIP SW2-3) on the Node Processor card (see
Figure 2) back to its OFF position (if changed in step 4) and power-cycle the 3000/06 Node Processor.
Repeat steps 4 through 11 for the remaining 3000/06 Node Processors, if the Bootloader mode is
used to upgrade each Node Processor.
12. In NetArrays Device Status window, ensure that the Node Processor firmware version is reported
correctly. Please note that redundant Node Processors will not report a version, if the firmware is
same as the primary Node Processor.

19
NetArrays Configuration
I/O Configuration
Node Processor configuration is included as part of the Node and Chassis configuration. You must
configure the correct Node to match the correct redundancy of the Node Processors. To do so, you can
1. Use the File -> New menu item and select the matching hardware configuration.
2. Open the I/O Configuration page and drag & drop the matching configuration.
a. Use Table 2 to match the hardware configuration
Example:

20
Table 2
RTP3000 Safety System Configuration Specifications
SIL (*)
3000 Series
CPU Nodes
Number of
Chassis
Number of Node
Processors in
Each Chassis
Number of
Chassis
Processors in
Each Chassis
Chassis
Power
Supply
Type
Number of
Available Slots for
I/O Cards in Each
Chassis
SIL-2
3000S/00-1
1
1
1
Single
17
3000S/00-1D
1
1
1
Dual
13
SIL-3
3000D/00-2
1
2
1
Single
16
3000D/00-2D
1
2
1
Dual
12
3000D/00-3
2
1
1
Single
17
3000D/00-3D
2
1
1
Dual
13
3000D/00-7
1
2
2
Single
15
3000D/00-7D
1
2
2
Dual
11
3000D/00-8
2
1
2
Single
16
3000D/00-8D
2
1
2
Dual
12
3000T/00-4
1
3
1
Single
15
3000T/00-4D
1
3
1
Dual
11
3000T/00-5
3
1
1
Single
17
3000T/00-5D
3
1
1
Dual
13
3000T/00-9
1
3
2
Single
14
3000T/00-9D
1
3
2
Dual
10
3000T/00-10
3
1
2
Single
16
3000T/00-10D
3
1
2
Dual
12
3000Q/00-11
1
4
1
Single
14
3000Q/00-11D
1
4
1
Dual
10
3000Q/00-12
4
1
1
Single
17
3000Q/00-12D
4
1
1
Dual
13
3000Q/00-13
1
4
2
Single
13
3000Q/00-13D
1
4
2
Dual
9
3000Q/00-14
4
1
2
Single
16
3000Q/00-14D
4
1
2
Dual
12
SIL (*)
3000 Micro
Series CPU
Nodes
Number of
Chassis
Number of Micro
Processors in
Each Chassis
Number of
Chassis
Processors in
Each Chassis
Chassis
Power
Supply
Type
Number of
Available Slots for
I/O Cards in Each
Chassis
SIL-2
3000M/00-15
1
1
0
Single
5
3000M/00-16
1
1
0
Dual
14
3000M/00-17
1
1
0
Single
18