EPDCX145 - Serial Interface Module Implementation Guide
EPDCX145 - Serial Interface Module Implementation Guide
While this information is presented in good faith and believed to be accurate, Honeywell disclaims
the implied warranties of merchantability and fitness for a particular purpose and makes no
express warranties except as may be stated in its written agreement with and for its customers.
In no event is Honeywell liable to anyone for any indirect, special or consequential damages. The
information and specifications in this document are subject to change without notice.
Honeywell International
Process Solutions
2500 West Union Hills
Phoenix, AZ 85027
1-800 343-0228
Release Information
Document Name Document ID Release Publication
Number Date
References
The following list identifies all documents that may be sources of reference for material discussed
in this publication.
Document Title
Contacts
World Wide Web
The following Honeywell web sites may be of interest to Process Solutions customers.
Corporate http://www.honeywell.com
Telephone
Contact us by telephone at the numbers listed below.
Symbol Definitions
The following table lists those symbols used in this document to denote certain conditions.
Symbol Definition
Symbol Definition
SIM MAINTENANCE.............................................................................57
Periodic Checks ....................................................................................................... 57
Recommended Spare Parts .................................................................................... 57
SIM Removal and Installation Under Power.......................................................... 58
Replacing Failed SIM TC- or TK-MUX021 .............................................................. 58
Prerequisites ........................................................................................................................58
Considerations .....................................................................................................................58
To replace a failed SIM ........................................................................................................59
Replacing Failed Power Adapter TC-/TK-SMPD01 or TC-/TK-SMPC01 .............. 60
Prerequisites ........................................................................................................................60
Considerations .....................................................................................................................60
To replace SIM power adapter .............................................................................................60
Replacing Failed Serial Interface FTA ................................................................... 61
Tables
Table 1 Start index ranges for limited range FTA....................................................... 109
Table 2 Start index ranges for extended range FTA .................................................. 110
Figures
Figure 1 Typical SIM topology with C200 Controller.......................................................2
Figure 2 Typical SIM topology with C300 Controller.......................................................3
Figure 3 Signal Path between Serial Field Device and Serial Interface Array Channel
Function Block. .........................................................................................................5
Figure 4 Typical Modbus Serial Interface connections .................................................21
Figure 5 Power Adapter to Serial Interface FTA Wiring................................................23
Figure 6 Pins common to RS-232 25-pin connector and FTA J2, DB-25 type connector.
................................................................................................................................24
Figure 7 Modbus FTA EIA-422/485 connections. .........................................................26
Figure 8 Typical connection of Allen-Bradley devices to the SIM.................................27
Figure 9 Typical Allen-Bradley Serial Interface connections. .......................................28
Figure 10 SIM front panel display and indicators..........................................................51
Figure 3 Signal Path between Serial Field Device and Serial Interface Array
Channel Function Block.
R310.2 Experion Serial Interface Module Implementation Guide 5
3/08 Honeywell
Serial Interface Module Purpose
SIM processing characteristics
Numerics 8
Flags 16
8-Character Strings 8
16-Character Strings 4
32-Character Strings 2
64-Character Strings 1
Writes to the Channel blocks can also be rejected because the SIM is not keeping up with
the writes being sent by the SIM. The SIM uses a write sequence number on a per
channel basis for each write command to the SIM. Upon receipt of the write command,
the SIM echoes back the last write sequence number processed. When the sequence
numbers get too far apart, the Channel block rejects further writes.
Note that writes can degrade read performance to as little as one array update per second.
Actual performance depends on Baud Rate and Device Protocol as well as
responsiveness of the field device. You can check read/write performance and overrun
statistics by viewing SIM details through the Network Tools (NTOOLS) application
provided with Experion Engineering Tools. See the Using NetworkTools to view SIM
statistic data section for more information.
The SIM block non-alarming parameters FTAAOVRNFL and FTABOVRNFL indicate
write overruns. You can monitor these parameters through the SIM Detail display in
Station. To alarm on the overrun condition, connect the overrun parameter to a FLAG
block, which can generate an OffNormal alarm.
33 cm (1 ft) MU-KLAM01
66 cm (2 ft) MU-KLAM02
External Cable
• Every four SI Array Channel blocks associated with a given SIM block are
equivalent to using one traditional analog/discrete IOM. A single rack-mounted SIM
can represent from 1 to 8 traditional IOMs, in terms of the maximum IOM capacity,
based on a ratio of four Array Channel blocks equal one traditional IOM.
• The 32 Array Channel blocks associated with a SIM block are allocated to the two
FTAs as follows.
− Channels 0 to 15 to FTA "A"
− Channels 16 to 31 to FTA "B"
• When only one FTA is used, it must be configured as FTA "A" and channels 0 to 3
must be used for at least one connection.
• For the most efficient use of Controller I/O connections, assign channels
consecutively starting from channel 0. If high throughput is required, especially high
write throughput, assign fewer arrays to each I/O connection.
• An FTA serial port operates at a data rate of up to 19.2 kilobaud.
• Communication between the SIM and the FTA operates at 38.4 kilobaud.
• The FTA to Power Adapter cable can be up to 300 meters (1000 feet) long.
• The Power Adapter to SIM cable can be up to 10 meters (32 feet) long.
• Be sure the 24Vdc power supply that is used to power the TC/TK-SMPD01 SIM
FTA Power Adapter is dedicated to powering only that Power Adapter and is not
used to power any other equipment. The power supply must also be a floating power
source, such as a DIN rail-mounted Phoenix Contact (MCR-PS-24DC/24DC/200)
power supply with floating 24Vdc output.
ESD HAZARD
Electrostatic discharge can damage integrated circuits or semiconductors if
you touch connector pins or tracks on a printed wiring board. Follow these
guidelines when you handle any electronic component:
WARNING
Unless the location is known to be non-hazardous, do not:
Considerations
You have reviewed the previous SIM implementation considerations and restrictions
section in this document.
Step Action
1 Position the module at the planned chassis slot location. For example, slots 3
and 4.
(Remember that slot numbering is zero-based and the left most slot is
number "0".)
Step Action
2 Align the module's circuit board with the top and bottom chassis guides.
Printed circuit
board
Bottom chassis
guide alignment
3 Slide the module into the chassis until the module tabs "click: into position.
Step Action
Be sure the 24Vdc power supply that you use to power the TC/TK-
CAUTION SMPD01 SIM FTA Power Adapter is dedicated to powering only that
Power Adapter and is not used to power any other equipment. The
power supply must also be a floating power source, such as a DIN rail-
mounted Phoenix Contact (MCR-PS-24DC/24DC/200) power supply
with floating 24Vdc output. Otherwise, voltage transients on the user-
supplied 24Vdc to the Power Adapter may damage the associated
TC/TK-MUX021 SIM in the chassis. You can also use the ac-powered
TC/TK-SIMPC01 SIM FTA Power Adapter instead of the dc-powered
version, as an alternative.
Considerations
• You have a Philips screwdriver and a drill, if you are mounting the power adapter on
a flat surface.
• If you are mounting the power adapter on a flat surface, observe the following
precautions:
• If the Power Adapter does not lay flat before the screws are
tightened, use additional washers as shims. This will ensure that
the circuit board is not warped or cracked by tightening the screws.
Warping a Power Adapter could cause a malfunction and prevent
proper operation.
• If you are mounting the power adapter on a DIN rail, you are responsible for
supplying and installing the DIN rails.
Step Action
Step Action
2 Remove the Power Adapter and drill tap holes at the marked locations.
3 Using the screws provided, mount the Power Adapter to the surface.
Step Action
B
Power Adapter
A to FTA Ports
SIM to Power
Adapter Cable
Port
5 • For Vdc model, connect leads from 24 Vdc power supply to J5 terminals
on the adapter, observing polarity.
• For Vac model, connect leads from 120/240 Vac line to J4 terminals L1,
L2, and GND.
AC Power
Connector
B
DC Power
Connector
Prerequisites
You have the applicable Modbus FTA and associated cables on hand.
• Limited-Range Modbus FTA model MU-TSIM12, or
• Extended-Range Modbus FTA model MU/MC-TSIM13
Considerations
• You can mount the Modbus FTA on a standard FTA Mounting Channel, DIN rail
(35 x 7.5 mm top hat rail), or flat surface.
• Do not expose the FTA to the weather. It is designed for mounting in a cabinet or a
controlled environment.
• Be sure the FTA is grounded either directly or through the mounting means.
Step Action
1 Is the Modbus FTA mounted in a cabinet with the Power Adapter?
• If the answer is Yes, be sure you have the appropriate number and length
of Honeywell internal cable MU-KLAMxx on hand. Go to the next Step.
• If the answer is No, be sure you have the appropriate number and length
of Honeywell external cable MU-KSXxxx on hand. Go to the next Step.
(Note that the cable must have two individually shielded, twisted pairs.)
Step Action
2 On one twisted pair mark one lead P- and the other P+ at both ends of the
cable. On the other twisted pair mark one lead S- and the other S+ at both
ends of the cable. Repeat this for other cables, as applicable.
3 Locate the J2 (CHANNEL A), 6-pin connector on the Power Adapter.
Observing polarity, connect the cable lead marked P- to pin 1 - PWR CUR and
lead marked P+ to pin 2 + PWR CUR. Connect the shield wire for this pair to
pin 3 SHD. Observing polarity, connect the cable lead marked S- to pin 4 -
SER and lead marked S+ to pin 5 + SER. Connect the shield wire for this pair
to pin 6 SHD. See the connection diagram in the following Figure for
reference.
(Note that the shield wires are connected to ground at the Power Adapter end
only.)
4 Locate the J1, 4-pin connector on the FTA "A". Observing polarity, connect the
cable lead marked P- to pin 1 - PWR CUR and lead marked P+ to pin 2 +
PWR CUR. Trim the shield wire for this pair close to the cable insulation.
Observing polarity, connect the cable lead marked S- to pin 3 - SER and lead
marked S+ to pin 4 + SER. Trim the shield wire for this pair close to the cable
insulation. See the connection diagram in the following Figure for reference.
5 Do you have a second FTA to be connected to the Power Adapter?
• If the answer is Yes, continue with Step 6.
• If the answer is No, exit this procedure and go to the next section Wiring
Modbus FTA to Modbus devices.
6 Locate the J3 (CHANNEL B), 6-pin connector on the Power Adapter.
Observing polarity, connect the cable lead marked P- to pin 1 - PWR CUR and
lead marked P+ to pin 2 + PWR CUR. Connect the shield wire for this pair to
pin 3 SHD. Observing polarity, connect the cable lead marked S- to pin 4 -
SER and lead marked S+ to pin 5 + SER. Connect the shield wire for this pair
to pin 6 SHD. See the connection diagram in the following Figure for
reference.
(Note that the shield wires are connected to ground at the Power Adapter end
only.)
7 Locate the J1, 4-pin connector on the FTA "B". Observing polarity, connect the
cable lead marked P- to pin 1 - PWR CUR and lead marked P+ to pin 2 +
PWR CUR. Trim the shield wire for this pair close to the cable insulation.
Observing polarity, connect the cable lead marked S- to pin 3 - SER and lead
marked S+ to pin 4 + SER. Trim the shield wire for this pair close to the cable
insulation. See the connection diagram in the following Figure for reference.
Step Action
8 Go to the next section Wiring Modbus FTA to Modbus devices.
GND L2 L1
+ J4
J1
J5
SIM Vac
Vdc
Power Adapter
PWR PWR
CUR SHD SER SHD CUR SHD SER SHD
1- 2+ 3 4- 5+ 6 1- 2+ 3 4- 5+ 6
J2 J3
CHANNEL A CHANNEL B
MU-KLAMxx Internal Cable
or
MU-KSXxx External Cable
Trim shield (300 m/1000 ft maximum)
Trim shield
close close
J3 J1 J3 J1
1- 2+ 3- 4+ 1- 2+ 3- 4+
PWR SER PWR SER
CUR CUR
J2 J2
FTA A FTA B
Common
FTA RS-232
25-pin 25-pin
Chassis Ground (FG) Chassis Ground (FG)
1 1
2 Transmit Data (TD) Transmit Data (TD) 2
3 Receive Data (RD) Receive Data (RD) 3
4 Request To Send (RTS) Request To Send (RTS)
4
Clear To Send (CTS) Clear To Send (CTS)
5 5
6 Data Set Ready (DSR) Data Set Ready (DSR) 6
8 Data Carrier Detect (DCD) Data Carrier Detect (DCD) 8
9 Reserved Reserved 9
Data Terminal Ready (DTR) Data Terminal Ready (DTR)
20 20
Figure 6 Pins common to RS-232 25-pin connector and FTA J2, DB-25 type
connector.
Data +
Data -
Notes:
1. Connect the shield wires together with a crimp
connector, Honeywell part number 30755381-001.
Ground the cable shield at only one end by
connecting the shield wire to J3, pin 3 on the FTA as
shown. Insulate the exposed ends of the shield wire.
2. Do not route the cables in the same conduit or tray as
AC power.
3. J3, pin 1 is connected to pin 2 and pin 4 is
connected to pin 5 internally on the FTA.
4. Up to 15 units can be connected to the EIA-422/485
Last Unit on Link interface. System performance is dependent on several
variables, such as the number of peripherals, the baud
Data + rate, the number of transactions, and the FTA Device
Data - Driver firmware.
120 ohm
ATTENTION
Connections and options are subject to change by Allen-Bradley without
notice to or from Honeywell. Please Contact Allen-Bradley for the latest
interface.
The following figures show the typical component connections associated with an Allen-
Bradley FTA installation for reference.
Controller Chassis
SIM SIM
3 m/10 ft 3 m/10 ft
Power Power
Adapter Adapter
Honeywell
Equipment RS-232 19.2 kbaud RS-232
Asynchronous Links 19.2 kbaud
Allen-Bradley
Equipment CIM CIM
A-B SLC 500
DH (57.6 kbaud) DH+ (57.6 kbaud)
Communications
See A-B Manuals for
Adapter connection options
DH+
A-B PLC-2 A-B PLC-3 A-B PLC-5 A-B PLC-5
CIM
Prerequisites
You have the Allen-Bradley FTA and associated cables on hand.
Considerations
• You can mount the Allen-Bradley FTA on a standard FTA Mounting Channel, DIN
rail (35 x 7.5 mm top hat rail), or flat surface.
• Do not expose the FTA to the weather. It is designed for mounting in a cabinet or a
controlled environment.
• Be sure the FTA is grounded either directly or through the mounting means.
Step Action
1 Is the A-B FTA mounted in a cabinet with the Power Adapter?
• If the answer is Yes, be sure you have the appropriate number and length
of Honeywell internal cable MU-KLAMxx on hand. Go to the next Step.
• If the answer is No, be sure you have the appropriate number and length
of Honeywell external cable MU-KSXxxx on hand. Go to the next Step.
(Note that the cable must have two individually shielded, twisted pairs.)
2 On one twisted pair mark one lead P- and the other P+ at both ends of the
cable. On the other twisted pair mark one lead S- and the other S+ at both
ends of the cable. Repeat this for other cables, as applicable.
3 Locate the J2 (CHANNEL A), 6-pin connector on the Power Adapter.
Observing polarity, connect the cable lead marked P- to pin 1 - PWR CUR and
lead marked P+ to pin 2 + PWR CUR. Connect the shield wire for this pair to
pin 3 SHD. Observing polarity, connect the cable lead marked S- to pin 4 -
SER and lead marked S+ to pin 5 + SER. Connect the shield wire for this pair
to pin 6 SHD. See the connection diagram in the previous Power Adapter to
Serial Interface FTA Wiring Figure for reference.
(Note that the shield wires are connected to ground at the Power Adapter end
only.)
4 Locate the J1, 4-pin connector on the FTA "A". Observing polarity, connect the
cable lead marked P- to pin 1 - PWR CUR and lead marked P+ to pin 2 +
PWR CUR. Trim the shield wire for this pair close to the cable insulation.
Observing polarity, connect the cable lead marked S- to pin 3 - SER and lead
marked S+ to pin 4 + SER. Trim the shield wire for this pair close to the cable
insulation. See the connection diagram in the previous Power Adapter to
Step Action
Serial Interface FTA Wiring Figure for reference.
5 Do you have a second A-B FTA to be connected to the Power Adapter?
• If the answer is Yes, continue with Step 6.
• If the answer is No, exit this procedure and go to the next section Wiring A-
B FTA to Allen-Bradley devices.
6 Locate the J3 (CHANNEL B), 6-pin connector on the Power Adapter.
Observing polarity, connect the cable lead marked P- to pin 1 - PWR CUR and
lead marked P+ to pin 2 + PWR CUR. Connect the shield wire for this pair to
pin 3 SHD. Observing polarity, connect the cable lead marked S- to pin 4 -
SER and lead marked S+ to pin 5 + SER. Connect the shield wire for this pair
to pin 6 SHD. See the connection diagram in the previous Power Adapter to
Serial Interface FTA Wiring Figure for reference.
(Note that the shield wires are connected to ground at the Power Adapter end
only.)
7 Locate the J1, 4-pin connector on the FTA "B". Observing polarity, connect the
cable lead marked P- to pin 1 - PWR CUR and lead marked P+ to pin 2 +
PWR CUR. Trim the shield wire for this pair close to the cable insulation.
Observing polarity, connect the cable lead marked S- to pin 3 - SER and lead
marked S+ to pin 4 + SER. Trim the shield wire for this pair close to the cable
insulation. See the connection diagram in the previous Power Adapter to
Serial Interface FTA Wiring Figure for reference.
8 Go to the next section Wiring A-B FTA to Allen-Bradley devices.
Prerequisites
• You are running Control Builder version R301.1 or greater.
• The existing Programmable Logic Controller is capable of larger addresses and had
been used to access lower address (<9,999) registers through a limited range FTA.
• You have logged on with sufficient security level to make changes in a control
strategy in Control Builder.
Considerations
Need to provide SIM flag point access to the read/write bit flag value at an extended
address (for example 33, 000) in an existing Programmable Logic Controller.
ATTENTION
If you are running pre R301.1 Experion software, the Control Execution
Environment (CEE) will not accept loads of array blocks with STARTINDEX
values above 99,999.
CAUTION
We recommend that you proceed with extreme caution whenever replacing
any component in a control system. Be sure the system is offline or in a safe
operating mode.
Step Action
1 Replace limited range Modbus FTA model MU-TSIM12 with extended range
Modbus FTA model MU-TSIM13 or MC-TSIM13. See the previous Installing
MODBUS FTA section for more information.
Step Action
2 In Project tree in Control Builder, reconfigure all existing serial interface I/O
channel blocks assigned to the SIM channels associated with the replaced
limited range Modbus FTA to change the most significant digit of the Starting
Element Address (STARTINDEX) so it agrees with the extended address
format. And, reconfigure the AUXDATA [5] parameter entry to 65535.0 to
enable the extended addressing mode on the extended range Modbus FTA.
3 Re-load modified control strategies in Project to the Controller.
4 This completes the procedure. Resume normal operation.
Considerations
• You can only view SIM (TC_MUX021) blocks in the Project tab set for
Assignment view. The Assignment view shows the relationship among all blocks
while the Containment view only shows templates that contain other templates or
Control Modules (CM), Sequential Control Modules (SCM), and basic blocks. To
toggle the view, right-click in an open area of the tab window and select Assignment
View or Containment View from the list, as applicable.
• Each TC_MUX021 block is automatically assigned a unique default tag name when
it is created. If your system will include multiple SIM blocks, you may want to adopt
a more structured syntax for naming them.
• The block tag or module name can be up to 16 characters long and must contain at
least on letter (A-Z). It must not contain an embedded space or leading space, and
dots are allowed in parameter naming only.
• The item name can be up to 40 characters long and must contain at least one letter
(A-Z). It is a name by which an entity is known within the context of the enterprise
model. The Item name must be unique among children of the same containment
parent in the Enterprise Model Builder hierarchy and should conform to the standard
convention names within the system.
• The module description text can be up to 132 characters long and appears on both
detail and group displays.
Step Action
1 On the File menu, click New>I/O Modules>IOMODULE>TC-MUX021 -
Step Action
Serial Interface, 32 ch. Calls up the TC_MUX021 Block parameters
configuration form Main tab with cursor in the Item Name field, as shown in
the following sample illustration.
2 If you want to change the default module name, double-click the Module
Name box to highlight it and key in the desired module name. Click the cursor
in the Item Name box. Otherwise, go to Step 3.
3 With cursor in the Item Name box, Key in the name of the item this object will
be associated with in the Enterprise Model Builder hierarchy.
4 Click the Module Description box and key in the desired descriptive text to
be used on displays.
5 Double-click the IOM Slot Number box and key in the number of the first slot
the SIM occupies in the chassis.
Step Action
6 • If the SIM is installed in a remote Series A I/O chassis, double-click the
Remote IO Chassis MAC Address box and key in the MAC address of
the uplink ControlNet Interface (CNI) module installed in the remote
chassis.
• If the SIM is installed in a C200 Controller chassis, you can skip this step.
7 • If the SIM is installed in a remote Series A I/O chassis, double click the
ControlNet Module Slot Number (connected to IO Chassis) box and
key in the number of the slot the downlink CNI module occupies in the
C200 Controller chassis.
• If the SIM is installed in a C200 Controller chassis, you can skip this step.
Considerations
• The following procedure adds a Serial Interface Numeric Array channel block to a
CM and assigns a channel to a SIM for example purposes only. You can easily adapt
this procedure to apply to another Serial Interface Array channel block.
• Each IOCHANNEL block is automatically assigned a unique default tag name when
it is created. If your system will include multiple IOCHANNEL blocks, you may
want to adopt a more structured syntax for naming them.
• The channel name can be up to 16 characters long and must contain at least on letter
(A-Z). It must not contain an embedded space or leading space, and dots are allowed
in parameter naming only.
• All illustrations used in the following procedure are for example purposes only.
Step Action
1 In the Project tab, double-click the icon for the Control Module that is to
include a serial interface I/O channel block to open it in the Control Drawing
pane, as shown in the following sample illustration.
Step Action
2 In the Library tab, scroll to the IOCHANNEL icon and click the plus sign to
expand the tree.
3 Click and drag the icon for the SINUMARRCH block to the open CM in the
Control Drawing to add the block to the CM, as shown in the following sample
illustration.
Step Action
Step Action
Step Action
8 In the Channel Number list box, click the desired FTA channel number this
channel block is to be assigned to. Channel 0 is the default selection.
9 Click the Assign Channel Block button to assign this channel to the
selected FTA channel number. The Channel Name field and the Assigned to
… fields are automatically updated, as shown in the following sample
illustration.
Step Action
11 Click the down arrow in the Access Lock box and select who can change the
block's value or state based on signon privileges. Press the Tab key to move
the cursor to the Serial Link Device Address box.
13 Key in the address that identifies the serial link device connected to this FTA
channel. Press the Tab key to move the cursor to the Starting Element
Index box.
14 Key in the value to identify the start of the contiguous array in the serial
device. See the Allen-Bradley Interface Reference or MODBUS Interface
Reference section, depending on the communications interface protocol
being used, for more information. Press the Tab key to move the cursor to
Step Action
the Number of Numeric Values box.
15 Key in the number that represents the number of numeric values in the array
of data from the serial device.
16 Click the down arrow in the Write Option box and select how the Array
Channel block will handle writes to its "data" parameter.
17 Double-click the 0 row in the Auxiliary Config Data list box. Key in value to
define communications interface for Allen-Bradley Interface or MODBUS
Interface. The default value is NaN (Not a Number) if parameters are not
being used with a specified interface. See the Allen-Bradley Interface
Reference or MODBUS Interface Reference section, depending on the
communications interface protocol being used, for more information
18 Repeat Step 17 for the other (1 to 7) rows in the Auxiliary Config Data list
box, as applicable.
19 Click the Identification tab to display it
20 Use this tab to configure parameters associated with the licensed template
option. See the Control Building Guide and/or the online help for more
information.
21 Click the Block Pins tab to display it.
22 Use this tab to configure the pins you want to expose for this block. See the
Control Building Guide and/or the online help for more information.
23 Click the Configuration Parameters tab to display it.
24 Use this tab to configure the parameters to be displayed on the block in the
Project mode. See the Control Building Guide and/or the online help for more
information.
25 Click the Monitoring Parameters tab to display it.
26 Use this tab to configure the parameters to be displayed on the block in the
Monitoring mode. See the Control Building Guide and/or the online help for
more information.
27 Click the Block Preferences tab to display it.
28 Use this tab to configure the viewing preferences for the block. See the
Control Building Guide and/or the online help for more information.
29 If you have a template license, click the Template Defining tab to display it.
Step Action
30 Use this tab to select which parameters are to be template defining. See the
Control Building Guide and/or the online help for more information.
31 When you completed entering configuration data, click the OK button to close
the configuration form and save the data.
32 This completes the procedure. Go to the next section.
Considerations
• If you assign a SIM to a CEEC300 block, you must configure the name of the FTE
Bridge block that represents the FTEB mounted in the Series A I/O chassis to
identify the communications path to the SIM on its configuration form. The
following illustration shows an excerpt of the FTE Bridge Name field that appears
on the TC_MUX021 Block configuration form when the SIM is assigned to a
CEEC300 block.
• All illustrations used in the following procedure are for example purposes only.
Step Action
1 On the Edit menu, click Execution Environment Assignment; or click the
2 If the IOMs tab is not on display in the Available modules list box, click the
tab to display it.
Step Action
block.
5 Check that the SIM block now appears in the Assigned Modules list box for
the given CEE block, as shown in the sample illustration below.
Note that the equal symbol prefix means that the block has been assigned
and the down arrow symbol prefix means that the block has been loaded
to the Controller.
6 Click the Close button to exit the dialog and save the assignments.
7 This completes the procedure. Go to the next section.
Considerations
• The following procedure is based on doing an initial load of a block from the
Project tab. You can also initiate a re-load of a block from the Monitoring tab.
• All the illustrations used in the procedure are for example purposes only.
The load operation is still an offline function. The Load Dialog box
provides the ability to automatically inactivate a component during a
load and then return the component to its active state. Do not use
this automatic inactivate/activate function, if your process cannot
tolerate the load disruption and consequent delay in activation. In
this case, you must manually toggle the component state through
the Monitoring tab in Control Builder.
Step Action
1 In the Project tab, click the plus signs to expand the tree hierarchy for the
Controller, CEE, and I/O icons, as required.
Step Action
2 Right-click the SIM icon and select Load from the menu to call up the Load
dialog.
Step Action
• Click the down arrow in the Post Load State column to select another
state.
• Check the check box at the bottom of the dialog to automatically change
the state of the SIM to the selected Post Load State after the load is
completed.
4 Click the OK button to initiate the load and track progress through the Load
Monitor dialog.
5 After load completes, check that the SIM icon now appears in the Monitoring
tab tree hierarchy.
6 This completes the procedure. Go to the next section.
Tnnn SIM is in its self-test mode and nnn equals the current
test sequence number.
Brief Green Flash every FTA is not present or not communicating - a retry is
0.5 second performed every 0.5 second.
Flashing Red All I/O connections are lost, or fail state, running under
software control.
Prerequisites
• You have logged on with sufficient privileges to make changes in a control strategy.
• You have loaded a control strategy to the Controller and can view the SIM through
the Monitoring tab of Control Builder.
Considerations
• Activating a SIM generates a state event change and resumes the module's normal
periodic processing.
• Inactivating a SIM generates a state event change; blocks channel access to flag,
numeric, and string data from the SIM; and sets channel data to NaN, Off, and "", as
well as setting associated statuses to Bad.
Step Action
1 • Right-click the SIM icon (green) and click Inactivate>Selected Item(s) on
the menu.
Or,
• Right click the SIM icon (blue) and click the Activate>Selected Item(s) on
the menu.
2 Click the Yes button to confirm the action in the Change State dialog.
3 • Wait for SIM icon to turn blue/inactive.
Or,
• Wait for SIM icon to turn green/active.
Project Tab
(gray)
Monitoring Tab
(gray)
(blue)
(green)
(red/black
exclamation)
(red/red
exclamation)
REFERENCE - INTERNAL
Please refer to the Control Building Guide sections in On-Line Monitoring
Using Control Builder for detailed information:
That all segments of the 4-character If segment or LED is not lit or has
display and the light emitting diodes dimmed, you must replace the SIM, since
(LED) on SIM are working. front-panel indicators and LEDs are not
field replaceable.
Power Adapter TC- or TK-SMPD01 24 Vdc SIM FTA Power Adapter 1/2
WARNING
Unless the location is known to be non-hazardous, do not:
CAUTION
We recommend that you proceed with extreme caution whenever replacing
any component in a control system. Be sure the system is offline or in a safe
operating mode.
Prerequisites
You have logged onto Control Builder with sufficient security level to make control
strategy changes.
The SIM icon is red with red exclamation point in the Monitoring tab of Control
Builder.
Considerations
• Be sure the system is offline or in a safe operating mode and power is removed from
the chassis.
• Be sure you take ESD hazard precautions when handling the SIM. See the
Installation Declarations section for more information.
Step Action
1 Unplug the SIM to Power Adapter cable assembly from the SIM.
2 Push in the top and bottom locking tabs on the SIM.
Prerequisites
• You have reviewed the previous CAUTION note.
• You have logged onto Control Builder with sufficient security level to
activate/inactivate components.
Considerations
• You have inactivated the SIM through the Monitoring tab in Control Builder.
• Be sure you take ESD hazard precautions when handling the SIM power adapter.
See the Installation Declarations section for more information.
Step Action
1 Turn Off the power source.
2 Remove power cable leads from ac or dc power connector.
3 Disconnect the SIM-to-Power Adapter, and the Power Adapter-to-FTA
cables.
4 • Remove the screws that hold the Power Adapter to the surface. Be sure
you are holding the Power Adapter when you remove the last screw.
Or
• Grasp both rail mount adapters on the tapered side and pull forward
slightly to pop the Power Adapter off the DIN rail. Be sure you hold onto
the Power Adapter, so it does not fall on the floor.
5 Reverse Steps 2 to 4 to mount the replacement power adapter.
6 Turn On the power source
7 This completes the procedure. Activate the SIM and resume normal
operation.
Fault Classifications
The following table lists some possible ways for classifying faults along with some
identifying characteristics.
The failure scenarios are as listed in the row above for the
Hard Failure.
Initial Checks
This section offers some checks that you can make to help isolate the problem. The
checks are arranged in no particular order.
In this syntax, the error code is the last four digits in the message or 3326.
Please refer to the Control Builder Error Codes Reference book for applicable error code
information.
REFERENCE - INTERNAL
Please refer to the Viewing SIM statistics in NetworkTools section in the
Control Hardware Troubleshooting and Maintenance Guide for more
information.
The Network Tools (NTools) application lets you view additional SIM diagnostic
information by selecting the SIM Module in its chassis view and making the appropriate
Device menu selection. Keep the following considerations in mind.
• An informational string is returned by the FTA to help diagnose the cause of soft
failures. See the Allen-Bradley Interface Error messages or MODBUS interface
Error messages for more information.
• The statistics are a continuously updating display of the one-second-sampled, 15-
second running average statistics, collected by the SIM.
• When Control Module Array Channel block communication has failed and all the
failed devices have been set inactive, the NTools SIM status display will show the
FTA revision and the FTA communication settings.
If every Control Module Array Channel block connected to an FTA is set inactive, the
NTools SIM status display will show the FTA revision and the text 'No Array Points are
configured to this FTA'.
REFERENCE - INTERNAL
Please refer to the Capturing chassis information using NetworkTools section
in the Control Hardware Troubleshooting and Maintenance Guide for more
information.
T001 CPU Type and Wrong CPU chip This test is done before the ROM
Version Check installed tests, because a wrong CPU could
appear to work, but might fail
timing tests. The CPU version is
also displayed as E40+ or E41+
for 630e Rev 4.0 or 4.1, 100 MHz.
Or, R for 603r, 150 MHz.
T010 Flash ROM Parity Flash chip For each ROM line (8 bytes) of the
Scan 1 MB boot image area, the data is
read and the expected parity is
T011 Flash ROM Parity Instruction Cache, The time needed to perform the
Scan Time MEM PLD wait above test is checked for
states reasonability. This test detects 603
Instruction Cache failure and/or
ROM wait state problems.
T013 Flash ROM Loader Flash chip The checksum of the boot
Checksum personality's Flash ROM loader is
computed and verified.
T015 XILINX DRAM Hardware Status This bit is asserted if the XILINX
Controller ASIC Register chips, did not power up properly.
Ready Check XILINX
T017 XILINX DRAM Hardware Status This bit is asserted if the XILINX
Controller ASIC Register chips, did not configure properly.
Error Check XILINX, MEM PLD
T018 XILINX DRAM XILINX, MEM PLD The XILINX configuration file is
Controller ASIC read back 32 bits at a time, and
Read-Back Verify compared to the image in ROM. A
read-back mask is used to
determine which bits of the stream
are not to be compared for one
reason or another.
T021 RAM Parity Path RAM, XILINX, Writes two 8-byte patterns and
buffers, MEM PLD verifies that parity byte was set
T022 RAM Word Access RAM, XILINX, Verifies that word patterns can be
buffers, MEM PLD written and read including three
cases of miss-aligned transfer.
T023 RAM Byte Access RAM, XILINX, Verifies that writing a string of 8
buffers, MEM PLD bytes can be read back as two
correct words, and as 8 bytes.
T024 RAM Half Access RAM, XILINX, Verifies that half words can be
buffers, MEM PLD read.
T025 RAM Byte Write RAM, XILINX, Verifies that bytes can be written
buffers, MEM PLD correctly.
T026 RAM Half Write RAM, XILINX, Verifies that half words can be
buffers, MEM PLD written correctly.
T027 RAM Half Align RAM, XILINX, Verifies that half-words can be
buffers, MEM PLD written and ready when miss-
aligned.
T028 RAM Word Align RAM, XILINX, Verifies that words can be written
buffers, MEM PLD and ready when miss-aligned.
T029 RAM Double RAM, XILINX, Verifies that the floating point unit
Access buffers, MEM PLD can write and read a double-word
value, and the same value is
correctly stored as two words.
T030 EDAC Correction RAM, XILINX, Verifies that any single-bit error
buffers, MEM PLD can both be detected and
corrected, in data or check bits, in
high or low word. One bit at a time
is changed and walked through
one line of RAM.
T031 EDAC Error Test RAM, XILINX, Verifies that a double-bit error can
buffers, MEM PLD be detected, in both high and low
word.
interrupt is expected.
T033 Data Parity Parity buffers, Verify that the data parity error
Interrupt parity circuit detection is working by enabling
data parity checking and the
machine check exception, then
walking through an area of ROM
which has been programmed with
bad parity. There are eight 8-byte
lines, each with a parity error in a
different byte, such that all byte
lanes are covered.
T034 RAM Parity Sweep Destructive RAM The RAM is read two words at a
Test time until end or until a multiple-bit
error is detected. Single bit errors
are counted, and written back for
correction. Parity errors (SRAM) or
Multi-bit Errors (DRAM) force
destructive testing in RAM.
T036 RAM Parity Sweep Instruction Cache, The time needed to perform the
Time MEM PLD wait above test is checked for
states reasonability, using the PPC 630
decremented. This test detects
603 Instruction Cache failure
and/or RAM wait-state problems.
Note that the time is not measured
(zero) if a parity error / Multi-bit
Error is detected and memory is
flushed.
T037 EDAC Interrupt XILINX chip, Verifies that a double-bit error will
Hardware Status generate the correct machine
Register chips, check exception.
MEM PLD, CPU
PLD
T040 RAM Memory Battery low The magic numbers are checked
Retention Test to see if the data in RAM may still
be valid. In the absence of parity
T041 RAM Destructive XILINX, RAM chip, Checks address and data lines by
Pattern Test MEM PLD writing a non-repeating pattern
over the whole memory, then
verifying it. Runs with data parity
enabled and fatal. Two starting
patterns are used for better
coverage.
T042 Flush RAM Data XILINX, RAM chip, Write zeros to all locations and
Zeros MEM PLD verify. Data parity is enabled
during this test. Runs with data
parity enabled and fatal.
T043 Flush RAM Parity RAM chip, XILINX, Verify that Flush RAM Data Zeros
Ones Parity/check bit test forced parity byte to ones
buffers (check bits to correct value). Data
parity disabled during this test, but
enabled permanently after the test
completes. Runs with data parity
disabled. Sets magic number to
show memory is initialized.
T060 Hardware Status Hardware Status Verifies that the Hardware Status
Register Access Register chips, Register appears to be readable
Test CPU PLD without generating a machine
check exception.
T065 Hardware Status Dev Card DUART, Verifies that the DEV_INT
Register DEV_INT Dev Card PLD, (Interrupt from development
Test CPU PLD board) status is not asserted.
T066 Hardware Status XILINX, MEM PLD Verifies that the MEM_INT
Register MEM_INT (interrupt from memory board)
Test status is not asserted.
T067 Hardware Status CUP PLD, Verifies that the SYS_FAIL status
Register SYS_FAIL backplane, other is not asserted for longer than a
Test modules specified period, to accommodate
other module's tests.
T068 Hardware Status PLD, WDT chip Verifies that the WDT_PENDING
Watchdog Timer status is not asserted.
Timeout Pending
Test
T070 Hardware Status ICP ASIC Verifies that the ICP-FAULT status
Register is not asserted. This would
ICP_FAULT Test indicate that the IC PASIC had
failed to come out of reset.
T073 Watchdog Timer CPU PLD, WDT Verifies that the WDT does not
Test chip, ICP ASIC, expire when hit for 500 msec,
ICP Oscillator based on Hardware Status
Register and interrupt. Uses the
WDT Test mode to show that the
WDT will time out and generate an
SMI interrupt in more than 195
msec but less than 210 msec. The
interrupt routine disables WDT
Test Mode to clear the interrupt.
Disables WDT after test.
T080 FTA DUART CPU PLD Verifies that the DUART can be
Register Access initialized.
Test
T081 FTA DUART Clock DUART Crystal Check the DUART clock against
Compare Test the CPU timebase register to
make sure they are running at the
same relative rates. The test is run
for 2048 DUART ticks (8.8888
msec) which corresponds to
55555 CPU ticks +/- 54.
T082 FTA DUART CPU PLD Verifies that the DUART can
Interrupt Test generate an interrupt. The counter
which had expired from the
previous test is used. The interrupt
is verified in the DUART ISR, then
enabled through the DUART IMR
and verified in the Hardware
Status Register; finally exceptions
are enabled to make sure that the
interrupt occurs.
T100 ICP Shared RAM Shared RAM chip, Checks address and data lines by
Destructive Pattern buffers, arbitration writing a non-repeating pattern
Test over the whole memory, then
verifying it. Runs with data parity
enabled and fatal. Two starting
patterns are used for better
coverage.
T101 ICP Shared RAM Shared RAM chip, Verify that 603 data parity error did
Destructive Pattern buffers, arbitration not occur during previous test.
Parity Interrupt Runs with data parity enabled and
Check fatal.
T102 ICP Shared RAM Shared RAM chip, Verified. This must be done before
Initialization to buffers, arbitration writing to the ASIC control
Force Correct Odd registers. Runs with data parity
Parity enabled and fatal.
T111 ICP ASIC Register ICP ASIC, ASIC- The hardware setup parameters
Access Test RAM I/F having been written to the ASIC
some time earlier, access to the
ICP ASIC registers is verified, and
the error register is verified as
zero. The ECHO_REV operation
is used to make the ASIC write its
version register to a designated
T112 IC PASIC Unique IC PASIC, ASIC- Correct access to the ICP shared
Address Echo Test RAM I/F RAM from the ASIC is verified
through the Echo Test, by asking
the ASIC to write each location's
address at that address. This test
is performed once for the address
and once for the complement of
the address. Coverage is not
100% because only the 17 LS
address bits are supported by
ASIC.
T113 ICP Bus Lock Test Bus lock or Verify that the IC PASIC can be
arbitration circuit locked out of its Shared RAM by
(CPU PLD) ICP the 603. This is accomplished with
ASIC the ASIC Echo_REV Test by:
locking the bus, telling the ASIC to
write to a specified address,
looking at the address, unlocking
the bus, and looking at the
address to see that it changed and
the correct data was written.
T114 ICP Clock Run Test IC PASIC Verifies that ICP clock is running. `
Oscillator
T115 ICP Clock Compare 603 Oscillator, ICP Check the ASIC clock against the
Test ASIC Oscillator 603 clock to make sure they are
running at the same relative rates.
The IC PASIC read timer
command is used to write the
Internal Timer to shared RAM
where it is read by the 603. The
test is run for 20 msec and +/-
0.016 msec error is allowed at this
time.
T116 ICP ASIC Interrupt Hardware Status The IC PASIC timer interrupt is
Test Register chips, enabled, along with the CPU
external interrupt, to see if the
T131 Personality Area Bad flash chip If the previous test indicated a
Erase parity error, the 3 MB personality
are is erased and verified.
Loss of power
The power supply has failed or the main power source has been shut down or is
experiencing a brownout or blackout condition.
Diagnostic Check • The 4-character display and LEDs on the SIM are off.
Cause 1 Main power source has been disconnected or shut down either manually
or temporarily by brownout or blackout condition.
Solution Re-connect the main power source or turn it On or wait for temporary
brownout or blackout condition to pass.
Cause 2 The 24 Vdc or 120/240 Vac chassis power supply failed or power cable
has been disconnected or failed.
Diagnostic Check A self-test diagnostic code remains on display and the poweron selftest
does not continue.
Cause The SIM poweron selftest has detected a failure that does not allow
operation to continue.
Solution Try cycling power to the SIM. Replace the SIM, if fault persists. See
Replacing Failed SIM TC- or TK-MUX021 for details.
Cause The SIM software has detected a failure that does not allow operation to
continue. There can be many causes for a failure including hardware,
use the NetworkTools function to capture a crash block for the device to
determine the possible cause before proceeding.
Solution Try cycling power to the SIM. If error persists, replace the SIM. See
Replacing Failed SIM TC- or TK-MUX021 for details.
Check the Trace log for breadcrumbs that occurred prior to the event.
See Viewing trace log and Using NetworkTools to capture chassis
information for more information. Provide the results of the trace log to
our Technical Assistance Center (TAC) for analysis.
Cause The SIM software has detected a background diagnostic failure that
does not allow operation to continue.
Solution Try cycling power to the SIM. If error persists, replace the SIM. See
Replacing Failed SIM TC- or TK-MUX021 for details.
Check the Trace log for breadcrumbs that occurred prior to the event.
See Viewing trace log and Using NetworkTools to capture chassis
information for more information. Provide the results of the trace log to
our Technical Assistance Center (TAC) for analysis.
Document/Section Comments
Experion Rxxx > Reference > Control Builder Describes error codes generated from within
Error Codes Reference Control Builder.
Experion Rxxx > Troubleshooting and The main repository for troubleshooting,
Maintenance > Control Hardware maintenance and repair of Process Controllers.
Troubleshooting and Maintenance Guide
Experion Rxxx > Configuration > DeviceNet Describes error codes generated from
Implementation Guide > Troubleshooting DeviceNet Interface Board.
DeviceNet Status Failures
Experion Rxxx > Installation and Upgrades > Troubleshooting FTE bridges.
Fault Tolerant Ethernet Bridge Implementation
Guide > Service > Troubleshooting
Experion Rxxx > Installation and Upgrades > Troubleshooting FTE nodes.
Fault Tolerant Ethernet Installation and Service
Guide > Troubleshooting FTE Nodes
Experion Rxxx> Reference > Honeywell TDC Troubleshooting TDC 3000 Hiway problems.
3000 Data Hiway Interface Reference > TDC
error codes and Troubleshooting
Experion Rxxx > Operations > SafeView User's Describes the meaning of SafeView
Guide > Appendix D - SafeView Error configuration errors.
Messages
Experion Rxxx > Reference > Server Scripting Describes the meaning of error messages in
Reference > Server scripting error messages the server log specific to server scripting.
Experion Rxxx > Reference > System Describes the meaning of System
Management Configuration Guide > Management Configuration errors.
Troubleshooting System Management
Experion Rxxx > Reference > System Describes the meaning of SES Configuration
Document/Section Comments
Management Configuration Guide > errors.
Troubleshooting SES
Experion Rxxx > Reference > System Describes the meaning of SPS Configuration
Management Configuration Guide > errors.
Troubleshooting SPS
Experion Rxxx > Planning and Design > Troubleshooting workstation nodes used in
Planning, Installation, and Service for WS360 Experion and TPN.
ATTENTION
When the AUXDATA[0…7] parameters are not being used with a Allen-
Bradley interface, they should be set to the default value of NaN (Not a
Number).
AUXDATA[4] Specifies the Allen- Use the following setting for a given PLC type.
Bradley PLC family
type. • 2.0 for PLC-2 type
• 3.0 for PLC-3 type
• 5.0 for PLC-5 type
AUXDATA[5] Specifies the Allen- Use the following setting for a given PLC type.
Bradley PLC file
number. • NaN for PLC-2 type
• 0 to 999 for PLC-3 or PLC-5 type
For diagnostic related Array Channel blocks, you
must set the AUXDATA[5] parameter to "-1" for a
Computer Interface Module or PLC type, or "-3"
for a loopback test. See the following section
Diagnostic data configuration for details.
AUXDATA[6] Specifies the data See the paragraph following this table for details
type for Allen-Bradley about making AUXDATA[6] settings for a given
PLC -2 or PLC-5 type PLC type.
or the section ID for a
PLC-3 type. Different settings are required for diagnostic
related Array Channel blocks. See the following
section Diagnostic data configuration for details.
AUXDATA[7] Specifies the Allen- Each Array Channel block can have a different
Bradley PLC scan scan rate. The Allen-Bradley interface supports
rate. either polling or Report by Exception (RBE)
independent of the scan rate. Use the following
setting for a given scan rate.
• 0 to scan the channel as fast as possible
• 1 to 255 to scan the channel once every 1 to
255 seconds
• 256 to scan the channel once after
configuration or after link or device failure
recovery (then only Report by Exception)
Notes:
a) Use higher priority scanning for time-critical
data, and slower scanning or RBE for lower
priority channels where data changes
infrequently.
b) If all channels are set for very fast scan (0 to
2 seconds), actual performance may be less
than one update per second, especially
when writes are used.
c) A setting greater than 256 causes a POL
FREQ error.
d) If more than one Array Channel block is
configured to map the same PLC memory
area, only one of the blocks will be updated
with RBE data.
e) After the first scan is completed with a
setting of 256, Array data is updated when
RBE data is received for that channel or
after any communication error (but not after
configuration errors).
f) The RBE feature is independent of the scan
rate. See the section Report by Exception
requirements for details.
WARNING
An unexpected write may take place when changing AuxData[6] (data type)
online, in the following scenario:
1. Data Type was 4 or 5 (read only unsigned).
2. An online value change was attempted. The change is ignored.
3. Data Type is changed to other writable numeric type.
Data Type AUXDATA[6] Array Channel Function Data Range Max. No.
Setting Block Elem.
Note: The PLC-2 controller only recognizes status or integer data types. The interface handles
other data types by requesting single or multiple elements for integer data according to the
AUXDATA[6] setting. The SIM does not support the VAX F format.
Data Type AUXDATA[6] Array Channel Function Data Range Max. No.
Setting Block Elem.
Notes:
1. The setting for AUXDATA[6] corresponds to the PLC-3 controller Section Identifier.
2. The PLC-3 controller does not support these data types: timers, counters, decimal, high
order (two word) integers, and pointers.
Data Type AUXDATA[6] Array Channel Function Data Range Max. No.
Setting Block Elem.
These Allen-Bradley file types are read only and writes to them are ignored.
Notes:
1. The setting for AUXDATA[6] corresponds to the PLC-5 controller file type, except 9 is
assigned for string data. Configure the PLC-5 file to use data type 'A' (ASCII), not data type
'ST' (string).
2. Timers/counters require three words per timer/counter. Presets and accumulated values
are read only. They can only be modified in ladder logic.
The PLC-3 Context and External Data Tables are only supported to the extent that
Context is fixed equals 1 (current context) and the External Data Table is always
equal to E3.
• PLC-5 Type: Use the file start index depending on the type of data (Flag, Numeric,
String).
For flag data, the start index setting represents the word address within the file. If the
AUXDATA[6] setting is 0 (Output) or 1 (Input), enter the start index for a Flag
Array Channel block as an octal number in the range of 0008 to 1778. A non-octal
digit or an out-of-range value causes a STARTIDX error.
Specify all other start index settings as integers, including flag array data except as
noted above for input or output data type. The SIM does not check file size.
Data Read by SIM Basic Command Set: Specific command Specific command
from PLC "Unprotected Read" "Word Range Read" "Word Range
Read"
(All Data Types) CMD: 01 CMD:0F
FNC: N/A FNC: 01 CMD:0F
FNC: 01
Data Write by SIM Basic Command Set: Specific command Specific command
to PLC "Unprotected Bit "Bit Write" "Read-Modify-
Write" Write"
(Flag Data Type) CMD:0F
CMD: 05 FNC: 02 CMD:0F
FNC: N/A FNC: 26
Data Write by SIM Basic Command Set: Specific command Specific command
to PLC "Unprotected Write" "Word Range Write" "Word Range
Write"
(Other Data Types) CMD: 08 CMD:0F
FNC: N/A FNC: 00 CMD:0F
FNC: 00
Data Write by PLC Basic Command Set: Specific command Specific command
to SIM (RBE) "Unprotected Write" "Word Range Write" "Typed Write"
These functions must use the Logical Binary Addressing format or the RBE message is
rejected by the SIM. Other formats including PLC-3 Symbolic and PLC-5 Logical ASCII will be
rejected.
Performance considerations
ATTENTION
• Since the Serial Interface I/O Module (SIM) bandwidth is limited, the
Array Channel blocks only process writes which change the current
process value. This eliminates unnecessary repeated writes.
An active SIM function block processes the following actions once per its publication
period of 250 milliseconds. The publication rate is the same whether the SIM block is
assigned to a 5ms-CEE or a 50ms-CEE type.
• Load Serial Interface Array Channel block configurations to the SIM.
• Send Array Channel block write requests to the SIM.
• Monitor status of the SIM, and report diagnostics, as applicable.
Of course, these actions are not performed when the SIM block is inactive. When the
SIM block is inactive, the Array Channel blocks set their data to applicable default
values.
The SIM block collects the writes for each array channel and sends them to the SIM
every 250ms. The following table lists the maximum number writes a SIM block
supports per channel in every 250ms cycle. If the SIM block's write list becomes full, it
rejects a write to the array channel block.
SINUMARRCH 8
SIFLAGARRCH 16
SITEXTARRCH (STRLEN = 8) 8
Writes to Array Channel Blocks can also be rejected because the SIM is not keeping up
with the writes being sent by the SIM block. Write overruns are indicated by the SIM
block FTAAOVRNFL and FTABOVRNFL parameters. To provide an overrun condition
alarm, connect the overrun parameters to a FLAG function block configured to generate
an OffNormal alarm.
For an Allen-Bradley interface, all configured Array Channel blocks scan the PLC
devices in a circular sequence at the specified scan rate with the read data requests. A
write data request preempts the read requests (and/or response to any RBE requests). The
number of consecutive write data requests is limited to eight (8), after which a Report by
Exception request or scan read request is serviced. If outputs, RBE requests, and scan
read requests are stacked continuously, the RBE requests and scan read requests are
alternately serviced after every eight outputs. This slows data acquisition considerably.
Channels with a scan frequency of 3 to 255 seconds are scanned once upon block
activation and then at the configured scan rate. RBE messages reset the scan interval
timer, therefore frequent RBE messages can prevent unnecessary scanning.
There is a limit to the number of write requests per second that can be serviced before
read response is significantly affected. Because of the time ladder logic takes to execute
the maximum number of write requests per second to a PLC running ladder logic should
be limited even further. Your Honeywell representative can provide test data and reports
on PLC modules certified to date.
CAUTION
It may take a few seconds after the Array Channel block is activated for the
configuration to be loaded to the SIM/FTA and good data to be imaged from
the device to the Array Channel block. During this time, short duration
BADPV alarms may occur on blocks that are accessing the channel's array
data.
The following actions are taken to prevent delay in communications to Arrary Channel
blocks that are active and communicating without error due to an inactive Array Channel
block with communication errors, requests, retries, or timeouts to a bad or out-of-service
device in the FTA.
When the CEE state is set to IDLE or when the When the CEE state is set to IDLE or when the
EXECSTATE of the Array Channel block is set EXECSTATE of the Array Channel block is set
to inactive, the Array Channel block to inactive, the CEE sends a NULL array
clears/disables SIM/FTA communications. database for the associated Array Channel
block to the SIM and FTA to stop the
When the CEE state transitions from IDLE to associated communication requests. However,
RUN and when the Array Channel block is all the Controller to SIM connections will be
active, the channel block initializes/enables maintained.
SIM/FTA communications.
When the CEE is set to IDLE or all Array
Channel blocks to a device are set inactive, the
FTA foreign device communications stops.
Once all the Control Module Array Channel
blocks communicating to a particular failed
device are set to inactive, the communication
to that device is stopped by both the SIM and
FTA(s). Communication to other error-free
device adresses will no longer be delayed for
requests, retries, or timeouts to the bad or out-
of-service device in the FTA
When the EXECSTATE of the Array channel When the EXECSTATE of at least one Control
block transitions from inactive to active and if Module Array Channel block configured for a
the CEE is in RUN, the Array Channel block particular device is set active, the configuration
initializes/enables SIM/FTA communications. will be downloaded to the FTA and the
communication gets established again, if the
device is healthy.
ATTENTION
We recommend using a read-back check to verify that a write is successful
in reaching the external device. A read-back check reads the parameter just
written and compares it to the value written. When the compared values are
equal, it guarantees that the write was successful all the way to the serial
device. The feedback time varies based on SIM, FTA, and device
performance.
interpret the diagnostic data returned. The software automatically reformats data from
diagnostic counters for easier interpretation.
You can cause a Diagnostic Counters Reset by executing a write to any element of the
diagnostic array counters. Note that a write to any one diagnostic counter resets all the
diagnostic counters in the module.
Use the settings in the following table to configure a Numeric Array Channel block to
acquire diagnostic information from an Allen-Bradley KE/KF Computer Interface
Module (CIM). Numeric data is used for diagnostic counters.
You must know which CIM is used because each model can have different
meanings for its offset values.
Use the settings in the following table to configure a Numeric Array Channel block to
acquire diagnostic information from an Allen-Bradley PLC. Numeric data is used for
diagnostic counters.
You must know which PLC model is used because each model can have different
meanings for its offset values.
Use the settings in the following table to configure a Text Array Channel block to set up
a diagnostic loop. A repetitive diagnostic loop can be set up to check the integrity of
transmissions over the communications link. It works by transmitting a message of a
certain length from the FTA which causes the A-B device to reply by transmitting the
same data back to the FTA. String data is used for this purpose.
AUXDATA[4] NaN
AUXDATA[5] -3
AUXDATA[6] NaN
STARTINDEX 1
STRLEN 64 characters
NSTRING 1
Counters check the attempted/successful transactions and when the block is active,
monitor data block.str[1] should contain the message:
Loopback Test: Attempted - xxxxx Pass - xxxxx
Where xxxxx is a pass/failure count.
Any communication errors are displayed, but the BADPVFL is not set for a diagnostic
loop.
Note that the loopback test can run along with other Array Channel block scans, but
doing so adversely affects performance.
Error messages
The following table lists some possible Serial Interface and Allen-Bradley
communication errors for reference. You may also need to refer to the Allen-Bradley
documentation for error messages specific to the PLC.
ERRCODE Description
String
# ELEMNT Number of elements is out of range for the given Array Channel
block.
ARR INIT Array Channel block is configured, but no valid data has been
received.
CEE Idle The CEE is Idle, so the function blocks are executing.
CFG_WAIT The SIM is waiting for valid communications from the FTA before
attempting to send the slot configuration.
CONFIG Can not load configuration to the SIM. Check all configuration data
carefully.
DataType Array Channel block is not supported or out of range for this
device.
ERRCODE Description
String
Md Inctv The SIM function block is inactive, so the Array Channel block can
not get new array data.
No Conn The Array Channel block can not get data because a proper
connection does not exist between the CPM and the SIM.
No SIMFB Array Channel block can not locate its assigned SIM block. Be
sure the SIM block is loaded to the CEE.
STR LEN Illegal string length for diagnostic loop channel type.
ERRCODE Description
String
MSGTMOUT Timed out waiting for the Allen-Bradley device to reply to the last
request.
OK_POLL No errors exist against the Array Channel block whose poll rate is
within 0 to 255.
OK_RBE No errors exist against the Array Channel block whose poll rate is
256.
RBE_FULL RBE buffer full due to too many Report by Exception requests
from the PLC devices.
FTA KE/KF
25-Pin 15-Pin
(male) (male)
TX 2 2 TX
RX 3 3 RX
RTS 4 4 RTS
CTS 5 5 CTS
DCD 8 11 DTR
DSR 6 6 DSR
DTR 20 8 DSR
GND 7 7 GND
13 GND
FTA PLC-5
25-Pin 15-Pin
(male) (male)
GND 7 7 GND
TX 2 3 RX
RX 3 2 TX
DTR 20 8 DCD
DSR 6 6 DSR
DCD 8 20 DCD
RTS 4 4 RTS
CTS 5 5 CTS
Reference Specifications
The following table lists some general specifications relevant to the Serial Interface
function.
Function Description
Model Numbers
SIM TC-MUX021
SIM FTA Power Adapter TC-SMPD01 (24 Vdc, 18-36 Vdc, 0.4A
maximum)
TC-SMPC01 (85 to 265 Vac, 47-63 Hz, 12W
maximum)
Function Description
General
EIA-RS232-D Support
Allen-Bradley Specific
Parity Even
Function Description
ATTENTION
When the AUXDATA[0…7] parameters are not being used with a Generic
Modbus interface, they should be set to the default value of NaN (Not a
Number).
AUXDATA[0] Specifies the Keep Alive This parameter tells the Modbus system that
Address for a Modbus the Experion subsystem is functioning. It can
coil. be configured separately on each array
channel block, but no two array channel
blocks should write to the same coil. The coil
address must be within the range 00001 to
09999 for limited range FTA or 000001 to
099999 for extended range FTA.
AUXDATA[1] Specifies the time If a valid response is not received after three
interval in seconds to tries (original plus two retires), a MSGTMOUT
wait before attempting a error results. The range is 0.25 to 5 seconds
message retry. on NaN. If NaN is specified, the default
timeout is 1.5 seconds. A timeout value can
be configured separately for each array
channel block.
AUXDATA[2] Specifies the signaling The first valid array channel block loaded to
protocol and modem the Controller with values in AUXDATA[2] and
control in an AUXDATA[3] sets the mode and baud rate for
integer/decimal format: the FTA communications. This means that
AUXDATA[2] AUXDATA[3] must contain the
mmm.n same value for all array blocks configured
through the same FTA. If array blocks loaded
Where mmm is the
later to that FTA have different
signaling protocol and n
AUXDATA[2]/[3] values, an AUXMATCH
is the modem control (0
error results.
= OFF and 1 = ON).
The modem control feature switches the
For example, 232.1
following signals: RTS, CTS, DSR, DTR, and
indicates EIA-232 with
DCD. When AUXDATA[2] is NaN, the
modem control ON. The
protocol is EIA-232 and modem control is
other choices are 232.0
OFF.
and 485.0. EIA-232
permits use of an
external modem.
AUXDATA[3] Specifies the baud rate The legal baud rates are 19200, 9600, 4800,
in an integer/decimal 2400, and 1200. NaN (dashes) results in a
format: default value of 19200 baud with odd parity.
bbbbb.n
TIP
The maximum extended range address of 99,999 more than supports the
maximum Modbus address of 65,535. The address range of 65,536 to 99,999
will not be usable by the Modbus standard protocol.
Preset Multiple 16
2 Read/Write
Registers
Performance considerations
ATTENTION
• Since the Serial Interface I/O Module (SIM) bandwidth is limited, the
Array Channel blocks only process writes which change the current
process value. This eliminates unnecessary repeated writes.
• In Experion systems with redundant Controller configurations, the
writes are not guaranteed during a failover. The store attempt may
occur in the Primary Controller, but it may not reach the SIM before the
failover occurs. The Secondary Controller does not attempt to resend
the data.
An active SIM function block processes the following actions once per its publication
period of 250 milliseconds. The publication rate is the same whether the SIM block is
assigned to a 5ms-CEE or a 50ms-CEE type.
• Load Serial Interface Array Channel block configurations to the SIM.
• Send Array Channel block write requests to the SIM.
• Monitor status of the SIM, and report diagnostics, as applicable.
Of course, these actions are not performed when the SIM block is inactive. When the
SIM block is inactive, the Array Channel blocks set their data to applicable default
values.
The SIM block collects the writes for each array channel and sends them to the SIM
every 250ms. The following table lists the maximum number writes a SIM block
supports per channel in every 250ms cycle. If the SIM block's write list becomes full, it
rejects a write to the array channel block.
SINUMARRCH 8
SIFLAGARRCH 16
SITEXTARRCH (STRLEN = 8) 8
Writes to Array Channel Blocks can also be rejected because the SIM is not keeping up
with the writes being sent by the SIM block. Write overruns are indicated by the SIM
block FTAAOVRNFL and FTABOVRNFL parameters. To provide an overrun condition
alarm, connect the overrun parameters to a FLAG function block configured to generate
an OffNormal alarm.
CAUTION
It may take a few seconds after the Array Channel block is activated for the
configuration to be loaded to the SIM/FTA and good data to be imaged from
the device to the Array Channel block. During this time, short duration
BADPV alarms may occur on blocks that are accessing the channel's array
data.
The following actions are taken to prevent delay in communications to Arrary Channel
blocks that are active and communicating without error due to an inactive Array Channel
block with communication errors, requests, retries, or timeouts to a bad or out-of-service
device in the FTA.
When the CEE state is set to IDLE or when the When the CEE state is set to IDLE or when the
EXECSTATE of the Array Channel block is set EXECSTATE of the Array Channel block is set
to inactive, the Array Channel block to inactive, the CEE sends a NULL array
clears/disables SIM/FTA communications. database for the associated Array Channel
block to the SIM and FTA to stop the
When the CEE state transitions from IDLE to associated communication requests. However,
RUN and when the Array Channel block is all the Controller to SIM connections will be
active, the channel block initializes/enables maintained.
SIM/FTA communications.
When the CEE is set to IDLE or all Array
Channel blocks to a device are set inactive, the
FTA foreign device communications stops.
Once all the Control Module Array Channel
blocks communicating to a particular failed
device are set to inactive, the communication
to that device is stopped by both the SIM and
FTA(s). Communication to other error-free
device adresses will no longer be delayed for
requests, retries, or timeouts to the bad or out-
of-service device in the FTA
When the EXECSTATE of the Array channel When the EXECSTATE of at least one Control
block transitions from inactive to active and if Module Array Channel block configured for a
the CEE is in RUN, the Array Channel block particular device is set active, the configuration
initializes/enables SIM/FTA communications. will be downloaded to the FTA and the
communication gets established again, if the
device is healthy.
ATTENTION
We recommend using a read-back check to verify that a write is successful
in reaching the external device. A read-back check reads the parameter just
written and compares it to the value written. When the compared values are
equal, it guarantees that the write was successful all the way to the serial
device. The feedback time varies based on SIM, FTA, and device
performance.
Error messages
The following table lists some possible Serial Interface and Modbus communication
errors for reference. You may also need to refer to the Modbus documentation for error
messages specific to the serial device.
ERRCODE Description
String
# ELEMNT Number of elements is out of range for the given Array Channel
block.
ARR INIT Array Channel block is configured, but no valid data has been
received.
CEE Idle The CEE is Idle, so the function blocks are executing.
CFG_WAIT The SIM is waiting for valid communications from the FTA before
attempting to send the slot configuration.
CONFIG Can not load configuration to the SIM. Check all configuration data
carefully.
DataCond Array Channel block does not understand Data Conditioner (internal
value) sent by the FTA.
DataType Array Channel block is not supported or out of range for this device.
(Most significant digit of STARTINDEX does not match the array
channel point. Extended Modbus addressing has a larger address
range.)
ERRCODE Description
String
EXT ADDR Value for AUXDATA[5] is not NaN or 65535.0. Defines whether
extended range addressing is enabled (65535.0) or not (NaN). This
defines how the user STARTINDEX parameter is interpreted on this
array point slot. FTA slots must have a STARTINDEX value that
matches the AUXDATA[5] setting or DATATYPE/STARTIDX errors
may occur.
IO Comm There is an I/O communications problem between the CPM and the
SIM.
Md Inctv The SIM function block is inactive, so the Array Channel block can
not get new array data.
No Conn The Array Channel block can not get data because a proper
connection does not exist between the CPM and the SIM.
No Data Transient condition that occurs when the Control Module containing
the Array Channel block is activated. Condition clears once ERRFL
is set OFF or ON.
No SIMFB Array Channel block can not locate its assigned SIM block. Be sure
the SIM block is loaded to the CEE.
ERRCODE Description
String
Startidx The STARTINDEX address is out of range. The address portion has
a maximum of 9,999 for limited range addressing or 65,535 for
extended range addressing.
STR LEN Illegal string length for diagnostic loop channel type.
NO CTS Modem did not respond with Clear To Send within the message
timeout time.
Task/Information Action/Reference
Task/Information Action/Reference
Configuration • In each Master and Slave Array Channel pair, configure the
identical settings for the device address (DEVADDR) and
start index (STARTINDEX) parameters.
• Configure identical, non-overlapping data areas in Master
and Slave Array Channel pairs. For example, if Array 1 is 32
integers with a STARTINDEX of 90001, then Array 2 must
have a STARTINDEX of 00033. If Array 1 is 512 Booleans
with a STARTINDEX of 00000 and Array 2 is 16 floating
points, then Array 2 must have a STARTINDEX of 70513 and
Array 3 must have a STARTINDEX of x00001 + 512 +16 =
529.
• In all Slave Array Channels, set AUXDATA[4] parameter to a
non-zero value (1.0) to enable the Remote Terminal Unit
(RTU) protocol.
• In all Master Array Channels, set AUXDATA[1] parameter to
recommended 3.0 second timeout.
• In all Master and Slave Array Channel pairs, configure the
identical settings for AUXDATA[2] and AUXDATA[3]
parameters.
− For short distances, the default is RS-232 direct
connection with NaN settings for both AUXDATA[2] and
AUXDATA[3] parameters.
− For long distance, use RS485 connection with a 485.0
setting for the AUXDATA[2] parameter and a 19200.1
setting for the AUXDATA[3] parameter.
Common Errors • If the Master accesses a device address that does not match
an existing Slave Array configuration, the Slave responds
with an Ex-2 error and freezes. After the Master address is
corrected, you must restart or reconfigure the Slave.
• If the Slave Array is configured with overlapping data areas
between arrays, it returns the STRTINDX error code.
• If the Slave Array is configured with a conflicting device
address, it returns the DEV ADDR error code.
• If the Slave is configured for a STARTINDEX address of
8xxxx, it causes an Ex-2 error code in the Master. The 8xxxx
address (IEEE Float at address -1) is not supported.
Reference Specifications
The following table lists some general specifications relevant to the Serial Interface
function.
Function Description
Model Numbers
SIM TC-MUX021
SIM FTA Power Adapter TC-SMPD01 (24 Vdc, 18-36 Vdc, 0.4A
Function Description
maximum)
TC-SMPC01 (85 to 265 Vac, 47-63 Hz, 12W
maximum)
General
Protocol Modbus
Serial Data Format 8 data bits with programmable ninth bit (parity)
EIA-RS232-D Support
Function Description
EIA-485 Support