Experion PKS

Troubleshooting and Notifications

Reference
Doc. No.: EP-DCX111
Release: 100
Last Revision Date: 1/03

Volume 1 of 2


ii Experion PKS

Troubleshooting and Notifications Reference Release 100

Honeywell 1/03

Notices and Trademarks

Copyright 2003 by Honeywell, Inc.
Release 100 January 2003

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, and TotalPlant are U.S. registered trademarks.
Other brand or product names are trademarks of their respective owners.










Honeywell
ACS Industry Solutions
2500 West Union Hills Dr.
Phoenix, AZ 85027
800-343-0228



Release 100 Experion PKS

Troubleshooting and Notifications Reference iii

1/03 Honeywell
About This Document
Contacts
Wide Web
The following lists Honeywells World Wide Web sites that will be of interest to our
industrial automation and control customers.

Honeywell Organization WWW Address (URL)
Corporate http://www.honeywell.com
ACS Industry Solutions http://www.acs.honeywell.com

Telephone
Contact us by telephone at the numbers listed below.

Organization Phone Number
United States
and Canada
Honeywell
ACS Industry
Solutions
1-800-343-0228 Solution Support Center
1-800-525-7439 On-Site Service Information
1-800-852-3211 Training Registrar
Experion PKS Support Program Information:
1-800-288-7491
Asia Pacific Honeywell Asia Pacific
Hong Kong
(852) 28298298
Pacific Honeywell Limited
Australia
(612) 9353 7000
Korea Honeywell
Seoul, Korea
82-2-799-6318
China Honeywell
China
86-10-65610371
Europe Honeywell PACE
Brussels, Belgium
[32-2] 728-2111
Latin America Honeywell
Sunrise, Florida U.S.A.
(954) 845-2600
About This Document
iv Experion PKS

Troubleshooting and Notifications Reference Release 100

Honeywell 1/03

About This Document
Release 100 Experion PKS

Troubleshooting and Notifications Reference v

1/03 Honeywell
Symbol definitions
The following table lists those symbols used in this document to denote certain
conditions.

Symbol Definition

ATTENTION
Used to identify information that requires special consideration.

TIP
Used to identify information that can not be classified as requiring
special consideration, but as "nice-to-know."

REFERENCE - INTERNAL
Used to identify an information reference source internal to the
document set.

REFERENCE - EXTERNAL
Used to identify an information reference source external to the
document set.



CAUTION
Refers to the Product Manual for additional information.



WARNING
Refers the to the Product Manual for additional information.



SHOCK HAZARD
WARNING: risk of electrical shock. This symbol warns the user of a
potential shock hazard where HAZARDOUS LIVE voltages greater
than 30 Vrms, 42.4 Vpeak, or 60 VDC may be accessible.



ESD HAZARD
Electrostatic Discharge (ESD) hazards. Observe precautions for
handling electrostatic sensitive devices




Protective Earth (PE) terminal. Provided for connection of the
protective earth (green or green/yellow) supply system conductor.

vi Experion PKS

Troubleshooting and Notifications Reference Release 100

Honeywell 1/03
Symbol Definition




Functional earth terminal. Used for non-safety purposes such as
noise immunity improvement. NOTE: This connection shall be
bonded to protective earth at the source of supply in accordance
with national local electrical code requirements.




Earth Ground. Functional earth connection. NOTE: This connection
shall be bonded to Protectiveearth at the source of supply in
accordance with national and local electrical code requirements.




Chassis Ground. Identifies a connection to the chassis or frame of
the equipment shall be bonded to Protective Earth at the source of
supply in accordance with national and local electrical code
requirements.



Release 100 Experion PKS

Troubleshooting and Notifications Reference vii

1/03 Honeywell
Contents

Part I Experion PKS Troubleshooting Guide
Isolating Faults........................................................................................ 1
Introduction...................................................................................................................1
To Learn More..............................................................................................................2
Fault Isolation ...............................................................................................................7
Start....................................................................................................................................... 7
Module Fault.......................................................................................................................... 7
BEM Fault Isolation ......................................................................................................8
Fault Isolation Table .............................................................................................................. 8
Background ........................................................................................................................... 8
Out-Of-The-Box Assembly Required..................................................................................... 9
Out-Of-The-Box Capacity...................................................................................................... 9
CNI Fault Isolation......................................................................................................10
CNI Not Compatible............................................................................................................. 10
Incorrect Keeper Values...................................................................................................... 11
NetworkTools Related Questions ........................................................................................ 11
General CNI Questions ....................................................................................................... 12
CPM Fault Isolation....................................................................................................13
Flash ROM Programming Errors ......................................................................................... 13
Fault Isolation Table ............................................................................................................ 13
PM IOP Fault Isolation ...............................................................................................14
IOP Box Soft failure error codes.......................................................................................... 15
IOP Slot Soft failure error codes.......................................................................................... 22
RM Fault Isolation ......................................................................................................24
STI and STI_MV IOP Fault Isolation ..........................................................................25
Process Variable Reliability ................................................................................................. 25
Error Detection .................................................................................................................... 26
Field Device Status.............................................................................................................. 26
Information Redundancy ..................................................................................................... 26
Standardized tests............................................................................................................... 27
Noise Immunity.................................................................................................................... 27
Noise Rejection ................................................................................................................... 28
Contents
viii Experion PKS

Troubleshooting and Notifications Reference Release 100

Honeywell 1/03
Smart Transmitter Error Codes............................................................................................ 28
Smart Transmitter IOP Messages........................................................................................ 30
Front Panel Indicators ........................................................................... 33
BEM ........................................................................................................................... 33
OK LED ............................................................................................................................... 33
CNI ............................................................................................................................. 34
Normal Runtime Displays .................................................................................................... 34
Abnormal Displays............................................................................................................... 36
Controller Redundancy Specific Displays............................................................................ 38
Common questions.............................................................................................................. 40
CPM........................................................................................................................... 41
OK LED ............................................................................................................................... 41
Battery LED......................................................................................................................... 43
4-Character Display............................................................................................................. 44
Input Modules ............................................................................................................ 49
Output Modules.......................................................................................................... 50
Serial Interface Modules ............................................................................................ 51
4-Character Display............................................................................................................. 51
Display of Runtime Information............................................................................................ 52
Display of Failure Information.............................................................................................. 53
Health Indicator.................................................................................................................... 54
Channel Activity Indicators .................................................................................................. 54
RM.............................................................................................................................. 55
OK LED ............................................................................................................................... 55
PRI LED............................................................................................................................... 55
COM LED............................................................................................................................ 56
4-Character Display............................................................................................................. 57
IOLIM ......................................................................................................................... 61
LINK Status LEDs................................................................................................................ 62
Fault Codes........................................................................................... 63
CNI Fault Codes ........................................................................................................ 63
CPM Fault Codes....................................................................................................... 64
Background ......................................................................................................................... 64
0x0000................................................................................................................................. 64
0x0002................................................................................................................................. 64
0x0003................................................................................................................................. 64
0x0004................................................................................................................................. 65
0x0006................................................................................................................................. 65
Contents
Release 100 Experion PKS

Troubleshooting and Notifications Reference ix

1/03 Honeywell
0x0007................................................................................................................................. 65
0x0008................................................................................................................................. 65
0x000D................................................................................................................................ 66
0x0013................................................................................................................................. 66
0x0014................................................................................................................................. 66
0x0401................................................................................................................................. 66
0x0402................................................................................................................................. 67
0x0403................................................................................................................................. 67
0x0404................................................................................................................................. 67
0x0405................................................................................................................................. 67
0x0406................................................................................................................................. 68
0x0407................................................................................................................................. 68
0x0408................................................................................................................................. 68
0x0409................................................................................................................................. 68
0x040A ................................................................................................................................ 69
0x040B ................................................................................................................................ 69
0x040C................................................................................................................................ 69
0x040D................................................................................................................................ 69
0x040E ................................................................................................................................ 70
0x040F ................................................................................................................................ 70
0x0410................................................................................................................................. 70
0x0411................................................................................................................................. 70
0x0412................................................................................................................................. 71
0x0413................................................................................................................................. 71
0x0414................................................................................................................................. 71
0x0415................................................................................................................................. 71
0x0416................................................................................................................................. 72
0x0417................................................................................................................................. 72
0x0418................................................................................................................................. 72
0x0419................................................................................................................................. 72
0x041A ................................................................................................................................ 73
0x041B ................................................................................................................................ 73
0x041C................................................................................................................................ 73
0x041D................................................................................................................................ 73
0x041E ................................................................................................................................ 74
0x041F ................................................................................................................................ 74
0x0420................................................................................................................................. 74
0x0421................................................................................................................................. 74
0x0422................................................................................................................................. 75
0x0423................................................................................................................................. 75
0x0424................................................................................................................................. 75
0x0425................................................................................................................................. 75
0x0426................................................................................................................................. 76
0x0427................................................................................................................................. 76
0x0428................................................................................................................................. 76
0x0429................................................................................................................................. 76
0x042A ................................................................................................................................ 77
0x042B ................................................................................................................................ 77
0x042C................................................................................................................................ 77
Contents
x Experion PKS

Troubleshooting and Notifications Reference Release 100

Honeywell 1/03
0x042D................................................................................................................................ 77
0x042E ................................................................................................................................ 78
0x042F................................................................................................................................. 78
0x0430................................................................................................................................. 78
0x0431................................................................................................................................. 78
Exchange Block ERRCODE Fault Codes.................................................................. 78
Description........................................................................................................................... 79
1........................................................................................................................................... 79
2........................................................................................................................................... 79
3........................................................................................................................................... 80
4........................................................................................................................................... 80
5........................................................................................................................................... 81
8........................................................................................................................................... 81
12......................................................................................................................................... 81
14......................................................................................................................................... 81
15......................................................................................................................................... 82
17......................................................................................................................................... 82
19......................................................................................................................................... 82
21......................................................................................................................................... 82
31......................................................................................................................................... 83
34......................................................................................................................................... 83
255....................................................................................................................................... 83
512....................................................................................................................................... 83
768....................................................................................................................................... 84
1024..................................................................................................................................... 84
1280..................................................................................................................................... 84
1536..................................................................................................................................... 84
1792..................................................................................................................................... 84
2010..................................................................................................................................... 85
2047..................................................................................................................................... 85
2048..................................................................................................................................... 85
2089..................................................................................................................................... 85
2304..................................................................................................................................... 86
2560..................................................................................................................................... 86
4096..................................................................................................................................... 86
8192..................................................................................................................................... 86
12288................................................................................................................................... 87
16384................................................................................................................................... 87
20480................................................................................................................................... 87
24576................................................................................................................................... 87
28672................................................................................................................................... 87
32768................................................................................................................................... 88
36864................................................................................................................................... 88
45056................................................................................................................................... 88
49152................................................................................................................................... 88
53248................................................................................................................................... 88
61441................................................................................................................................... 89
61442................................................................................................................................... 89
Contents
Release 100 Experion PKS

Troubleshooting and Notifications Reference xi

1/03 Honeywell
61443 .................................................................................................................................. 89
61444 .................................................................................................................................. 90
61445 .................................................................................................................................. 90
61446 .................................................................................................................................. 90
61447 .................................................................................................................................. 91
61448 .................................................................................................................................. 91
61449 .................................................................................................................................. 91
61450 .................................................................................................................................. 91
61451 .................................................................................................................................. 92
61452 .................................................................................................................................. 92
61453 .................................................................................................................................. 92
61454 .................................................................................................................................. 92
61455 .................................................................................................................................. 92
61456 .................................................................................................................................. 93
61457 .................................................................................................................................. 93
61458 .................................................................................................................................. 93
61459 .................................................................................................................................. 93
61460 .................................................................................................................................. 93
61461 .................................................................................................................................. 94
61462 .................................................................................................................................. 94
61463 .................................................................................................................................. 94
61464 .................................................................................................................................. 94
61465 .................................................................................................................................. 95
61466 .................................................................................................................................. 95
61467 .................................................................................................................................. 95
61468 .................................................................................................................................. 95
61469 .................................................................................................................................. 95
61470 .................................................................................................................................. 96
61471 .................................................................................................................................. 96
I/O Fault Codes ..........................................................................................................97
TC-ODX081 Discrete AC Output Module ............................................................................ 97
RM Fault Codes..........................................................................................................98
About fault code format ....................................................................................................... 98
E000.................................................................................................................................... 99
E001.................................................................................................................................... 99
E010.................................................................................................................................. 100
E020.................................................................................................................................. 100
E021.................................................................................................................................. 100
E022.................................................................................................................................. 100
E023.................................................................................................................................. 101
E024.................................................................................................................................. 101
E025.................................................................................................................................. 101
E026.................................................................................................................................. 101
E027.................................................................................................................................. 102
E028.................................................................................................................................. 102
E029.................................................................................................................................. 102
E02A.................................................................................................................................. 102
Contents
xii Experion PKS

Troubleshooting and Notifications Reference Release 100

Honeywell 1/03
E02B.................................................................................................................................. 103
E02C.................................................................................................................................. 103
E02D.................................................................................................................................. 103
E030 .................................................................................................................................. 103
E031 .................................................................................................................................. 104
E032 .................................................................................................................................. 104
E033 .................................................................................................................................. 104
E034 .................................................................................................................................. 104
E035 .................................................................................................................................. 105
E036 .................................................................................................................................. 105
E037 .................................................................................................................................. 105
E038 .................................................................................................................................. 105
E039 .................................................................................................................................. 106
E03A.................................................................................................................................. 106
E03a .................................................................................................................................. 106
E03B.................................................................................................................................. 106
E03b .................................................................................................................................. 107
E03C.................................................................................................................................. 107
E03D.................................................................................................................................. 107
E03E.................................................................................................................................. 107
E03F.................................................................................................................................. 108
E03G ................................................................................................................................. 108
E03H.................................................................................................................................. 108
E03I ................................................................................................................................... 108
E03J .................................................................................................................................. 109
E03K.................................................................................................................................. 109
E03L .................................................................................................................................. 109
E03M................................................................................................................................. 109
E03N.................................................................................................................................. 110
E03P.................................................................................................................................. 110
E03Q ................................................................................................................................. 110
E03R.................................................................................................................................. 110
E03T.................................................................................................................................. 111
E03U.................................................................................................................................. 111
E03V.................................................................................................................................. 111
E03W................................................................................................................................. 111
E03X.................................................................................................................................. 112
E03Y.................................................................................................................................. 112
E03Z.................................................................................................................................. 112
E040 .................................................................................................................................. 112
E041 .................................................................................................................................. 113
E042 .................................................................................................................................. 113
E043 .................................................................................................................................. 113
E044 .................................................................................................................................. 113
E045 .................................................................................................................................. 114
E046 .................................................................................................................................. 114
E047 .................................................................................................................................. 114
E048 .................................................................................................................................. 114
E049 .................................................................................................................................. 115
Contents
Release 100 Experion PKS

Troubleshooting and Notifications Reference xiii

1/03 Honeywell
E04A.................................................................................................................................. 115
E04B.................................................................................................................................. 115
E04C ................................................................................................................................. 115
E04D ................................................................................................................................. 116
E050.................................................................................................................................. 116
E051.................................................................................................................................. 116
E052.................................................................................................................................. 116
E053.................................................................................................................................. 117
E054.................................................................................................................................. 117
E060.................................................................................................................................. 118
E07A.................................................................................................................................. 118
E070.................................................................................................................................. 118
E071.................................................................................................................................. 118
E072.................................................................................................................................. 118
E073.................................................................................................................................. 119
E074.................................................................................................................................. 119
E075.................................................................................................................................. 119
E076.................................................................................................................................. 119
E077.................................................................................................................................. 119
E078.................................................................................................................................. 120
E079.................................................................................................................................. 120
E080.................................................................................................................................. 120
E090.................................................................................................................................. 120
E091.................................................................................................................................. 121
E092.................................................................................................................................. 121
E093.................................................................................................................................. 121
E0A0.................................................................................................................................. 121
E0A1.................................................................................................................................. 122
E0A2.................................................................................................................................. 122
E0A3.................................................................................................................................. 122
E0A4.................................................................................................................................. 122
E0A5.................................................................................................................................. 123
E0A6.................................................................................................................................. 123
E0A7.................................................................................................................................. 123
E0A8.................................................................................................................................. 123
E0B0.................................................................................................................................. 124
E0B1.................................................................................................................................. 124
E0B2.................................................................................................................................. 124
E0C0 ................................................................................................................................. 124
E0C1 ................................................................................................................................. 125
E0C2 ................................................................................................................................. 125
E0C3 ................................................................................................................................. 125
E0C4 ................................................................................................................................. 126
E0C5 ................................................................................................................................. 126
E0D0 ................................................................................................................................. 126
E0D1 ................................................................................................................................. 126
E0D2 ................................................................................................................................. 127
E0D3 ................................................................................................................................. 127
E0D4 ................................................................................................................................. 127
Contents
xiv Experion PKS

Troubleshooting and Notifications Reference Release 100

Honeywell 1/03
E0D5.................................................................................................................................. 127
E0D6.................................................................................................................................. 127
E0D7.................................................................................................................................. 128
E0D8.................................................................................................................................. 128
E0D9.................................................................................................................................. 128
E0DA................................................................................................................................. 128
E0DB................................................................................................................................. 128
E0DC................................................................................................................................. 129
E0E0.................................................................................................................................. 129
E0E1.................................................................................................................................. 129
E0E2.................................................................................................................................. 129
E0F0.................................................................................................................................. 130
E0G0 ................................................................................................................................. 130
E0H0.................................................................................................................................. 130
E0I0 ................................................................................................................................... 130
E0I1 ................................................................................................................................... 131
E0I2 ................................................................................................................................... 131
E0I3 ................................................................................................................................... 131
E0I4 ................................................................................................................................... 131
E0I5 ................................................................................................................................... 132
E0I6 ................................................................................................................................... 132
E0I7 ................................................................................................................................... 132
E0I8 ................................................................................................................................... 132
E0I9 ................................................................................................................................... 133
E0IA................................................................................................................................... 133
E0IB................................................................................................................................... 133
E0IC................................................................................................................................... 133
E0ID................................................................................................................................... 134
E0IE................................................................................................................................... 134
E0IF................................................................................................................................... 134
E0IG .................................................................................................................................. 134
E0J0 .................................................................................................................................. 135
E101 .................................................................................................................................. 135
E102 .................................................................................................................................. 135
E103 .................................................................................................................................. 135
E104 .................................................................................................................................. 136
E105 .................................................................................................................................. 136
E106 .................................................................................................................................. 136
E107 .................................................................................................................................. 136
E108 .................................................................................................................................. 136
E109 .................................................................................................................................. 137
E10A.................................................................................................................................. 137
E10B.................................................................................................................................. 137
E10C.................................................................................................................................. 137
E10D.................................................................................................................................. 137
E10E.................................................................................................................................. 138
E10F.................................................................................................................................. 138
E10G ................................................................................................................................. 138
E10H.................................................................................................................................. 138
Contents
Release 100 Experion PKS

Troubleshooting and Notifications Reference xv

1/03 Honeywell
E10I ................................................................................................................................... 138
E10J .................................................................................................................................. 139
E10K.................................................................................................................................. 139
E10L.................................................................................................................................. 139
E10M................................................................................................................................. 139
E10N ................................................................................................................................. 139
E10P.................................................................................................................................. 140
E201.................................................................................................................................. 140
E202.................................................................................................................................. 140
E203.................................................................................................................................. 140
E204.................................................................................................................................. 141
E205.................................................................................................................................. 141
E206.................................................................................................................................. 141
E207.................................................................................................................................. 141
E208.................................................................................................................................. 141
E209.................................................................................................................................. 142
E20A.................................................................................................................................. 142
E20B.................................................................................................................................. 142
E20C ................................................................................................................................. 142
E20D ................................................................................................................................. 143
E20E.................................................................................................................................. 143
E20F.................................................................................................................................. 143
E20G................................................................................................................................. 143
E20H ................................................................................................................................. 144
E20I ................................................................................................................................... 144
E20J .................................................................................................................................. 144
E20K.................................................................................................................................. 144
E20L.................................................................................................................................. 145
E20M................................................................................................................................. 145
E210.................................................................................................................................. 145
E211.................................................................................................................................. 145
E230.................................................................................................................................. 146
E235.................................................................................................................................. 146
E236.................................................................................................................................. 146
E237.................................................................................................................................. 146
E239.................................................................................................................................. 147
E23B.................................................................................................................................. 147
E250.................................................................................................................................. 147
E251.................................................................................................................................. 147
E252.................................................................................................................................. 148
E253.................................................................................................................................. 148
E254.................................................................................................................................. 148
E255.................................................................................................................................. 148
E256.................................................................................................................................. 148
E257.................................................................................................................................. 149
E258.................................................................................................................................. 149
E259.................................................................................................................................. 149
E25A.................................................................................................................................. 149
E25B.................................................................................................................................. 149
Contents
xvi Experion PKS

Troubleshooting and Notifications Reference Release 100

Honeywell 1/03
E25C.................................................................................................................................. 150
E25D.................................................................................................................................. 150
E25E.................................................................................................................................. 150
E25F.................................................................................................................................. 150
E25G ................................................................................................................................. 150
E25H.................................................................................................................................. 151
E25I ................................................................................................................................... 151
E25J .................................................................................................................................. 151
E260 .................................................................................................................................. 151
E261 .................................................................................................................................. 152
E262 .................................................................................................................................. 152
E263 .................................................................................................................................. 152
E264 .................................................................................................................................. 152
E265 .................................................................................................................................. 153
E266 .................................................................................................................................. 153
E267 .................................................................................................................................. 153
E268 .................................................................................................................................. 153
E269 .................................................................................................................................. 154
E26A.................................................................................................................................. 154
E26B.................................................................................................................................. 154
E270 .................................................................................................................................. 154
E271 .................................................................................................................................. 155
E280 .................................................................................................................................. 155
E281 .................................................................................................................................. 155
E282 .................................................................................................................................. 155
E283 .................................................................................................................................. 156
E284 .................................................................................................................................. 156
E285 .................................................................................................................................. 156
E288 .................................................................................................................................. 156
E289 .................................................................................................................................. 157
E28A.................................................................................................................................. 157
E28B.................................................................................................................................. 157
E28C.................................................................................................................................. 157
E28D.................................................................................................................................. 158
E290 .................................................................................................................................. 158
E291 .................................................................................................................................. 158
E292 .................................................................................................................................. 158
E293 .................................................................................................................................. 159
E294 .................................................................................................................................. 159
E295 .................................................................................................................................. 159
E296 .................................................................................................................................. 159
E297 .................................................................................................................................. 160
E298 .................................................................................................................................. 160
E299 .................................................................................................................................. 160
E2B0.................................................................................................................................. 160
E2B1.................................................................................................................................. 161
E2B2.................................................................................................................................. 161
E2B3.................................................................................................................................. 161
E2B4.................................................................................................................................. 161
Contents
Release 100 Experion PKS

Troubleshooting and Notifications Reference xvii

1/03 Honeywell
E2B5.................................................................................................................................. 161
E2B6.................................................................................................................................. 162
E2B7.................................................................................................................................. 162
E2B8.................................................................................................................................. 162
E2B9.................................................................................................................................. 162
E2BA................................................................................................................................. 163
E2BB................................................................................................................................. 163
E2BC................................................................................................................................. 163
E2BD................................................................................................................................. 163
E2BE................................................................................................................................. 163
E2BF ................................................................................................................................. 164
E2BG................................................................................................................................. 164
E2BH................................................................................................................................. 164
E2BI................................................................................................................................... 164
E2BJ.................................................................................................................................. 165
E2BK................................................................................................................................. 165
E2BL.................................................................................................................................. 165
E2C0 ................................................................................................................................. 165
E2C1 ................................................................................................................................. 165
E2C2 ................................................................................................................................. 166
E2C3 ................................................................................................................................. 166
E2C4 ................................................................................................................................. 166
E2C5 ................................................................................................................................. 166
E2C6 ................................................................................................................................. 166
E2C7 ................................................................................................................................. 167
E2C8 ................................................................................................................................. 167
E2C9 ................................................................................................................................. 167
E2CA................................................................................................................................. 167
E2CB................................................................................................................................. 168
E2CC................................................................................................................................. 168
E2CD................................................................................................................................. 168
E2CE................................................................................................................................. 168
E2CF ................................................................................................................................. 169
E2CG................................................................................................................................. 169
E2CH................................................................................................................................. 169
E2CI .................................................................................................................................. 169
E2CJ.................................................................................................................................. 170
E2CK................................................................................................................................. 170
E2CL ................................................................................................................................. 170
E2D0 ................................................................................................................................. 170
E2E0.................................................................................................................................. 170
E2E1.................................................................................................................................. 171
E2E2.................................................................................................................................. 171
E2E3.................................................................................................................................. 171
E2E4.................................................................................................................................. 171
E2E5.................................................................................................................................. 172
E2E6.................................................................................................................................. 172
E2E7.................................................................................................................................. 172
E2E8.................................................................................................................................. 172
Contents
xviii Experion PKS

Troubleshooting and Notifications Reference Release 100

Honeywell 1/03
E2E9.................................................................................................................................. 173
E2EA ................................................................................................................................. 173
E2EB ................................................................................................................................. 173
E2EC................................................................................................................................. 173
E2ED................................................................................................................................. 174
E2EE ................................................................................................................................. 174
E2EF.................................................................................................................................. 174
E2EG................................................................................................................................. 174
E2EH................................................................................................................................. 175
E2F0.................................................................................................................................. 175
E2F1.................................................................................................................................. 175
E2F2.................................................................................................................................. 175
E2F3.................................................................................................................................. 176
E2F4.................................................................................................................................. 176
E2F5.................................................................................................................................. 176
E2F6.................................................................................................................................. 176
E2F7.................................................................................................................................. 177
E2F8.................................................................................................................................. 177
E2F9.................................................................................................................................. 177
E2FA.................................................................................................................................. 177
E2FB.................................................................................................................................. 178
E2FC ................................................................................................................................. 178
E2FD ................................................................................................................................. 178
E2FE.................................................................................................................................. 178
E2FF.................................................................................................................................. 179
E2G0 ................................................................................................................................. 179
E2G1 ................................................................................................................................. 179
E2H0.................................................................................................................................. 179
E2H1.................................................................................................................................. 180
E2J0 .................................................................................................................................. 180
E2J1 .................................................................................................................................. 180
E2J2 .................................................................................................................................. 180
E2J3 .................................................................................................................................. 181
E2J4 .................................................................................................................................. 181
E2J5 .................................................................................................................................. 181
E2J6 .................................................................................................................................. 181
E2J7 .................................................................................................................................. 182
E2J8 .................................................................................................................................. 182
E2J9 .................................................................................................................................. 182
E2K0.................................................................................................................................. 182
E2L0 .................................................................................................................................. 183
E2L1 .................................................................................................................................. 183
E2M0 ................................................................................................................................. 183
E2M1 ................................................................................................................................. 183
E2N0.................................................................................................................................. 184
E2P0.................................................................................................................................. 184
E2Q0 ................................................................................................................................. 184
E2Q1 ................................................................................................................................. 184
E2Q2 ................................................................................................................................. 185
Contents
Release 100 Experion PKS

Troubleshooting and Notifications Reference xix

1/03 Honeywell
E2Q3 ................................................................................................................................. 185
E2Q4 ................................................................................................................................. 185
E2Q5 ................................................................................................................................. 185
E2Q6 ................................................................................................................................. 186
E2Q7 ................................................................................................................................. 186
E2Q8 ................................................................................................................................. 186
E2Q9 ................................................................................................................................. 186
E2QA................................................................................................................................. 187
E2QB................................................................................................................................. 187
E2QC................................................................................................................................. 187
E2QD................................................................................................................................. 187
E2QE................................................................................................................................. 188
E2QF................................................................................................................................. 188
E300.................................................................................................................................. 188
E301.................................................................................................................................. 188
E400.................................................................................................................................. 189
E401.................................................................................................................................. 189
E402.................................................................................................................................. 189
E404.................................................................................................................................. 189
E405.................................................................................................................................. 189
E406.................................................................................................................................. 190
E407.................................................................................................................................. 190
E408.................................................................................................................................. 190
E409.................................................................................................................................. 190
E40A.................................................................................................................................. 191
E410.................................................................................................................................. 191
E420.................................................................................................................................. 191
E430.................................................................................................................................. 191
E440.................................................................................................................................. 192
E450.................................................................................................................................. 192
E451.................................................................................................................................. 192
E460.................................................................................................................................. 192
E470.................................................................................................................................. 192
E480.................................................................................................................................. 193
E481.................................................................................................................................. 193
E490.................................................................................................................................. 193
E4A0.................................................................................................................................. 193
E4B0.................................................................................................................................. 193
E4C0 ................................................................................................................................. 194
E4D0 ................................................................................................................................. 194
E4E0.................................................................................................................................. 194
E4F0.................................................................................................................................. 194
E4G0 ................................................................................................................................. 194
E4H0 ................................................................................................................................. 195
E4I0................................................................................................................................... 195
E4J0 .................................................................................................................................. 195
E4K0.................................................................................................................................. 195
E4L0.................................................................................................................................. 195
E4L1.................................................................................................................................. 196
Contents
xx Experion PKS

Troubleshooting and Notifications Reference Release 100

Honeywell 1/03
E4L2 .................................................................................................................................. 196
E4M0 ................................................................................................................................. 196
E4N0.................................................................................................................................. 196
E4N1.................................................................................................................................. 196
E4P0.................................................................................................................................. 197
E4P1.................................................................................................................................. 197
E4P2.................................................................................................................................. 197
E4P3.................................................................................................................................. 197
E4P4.................................................................................................................................. 198
E4Q0 ................................................................................................................................. 198
E4R0.................................................................................................................................. 198
E4T0.................................................................................................................................. 198
E4U0.................................................................................................................................. 198
E4U1.................................................................................................................................. 199
E4U2.................................................................................................................................. 199
E4U3.................................................................................................................................. 199
E4V0.................................................................................................................................. 199
E4V3.................................................................................................................................. 199
E4V4.................................................................................................................................. 200
E4V5.................................................................................................................................. 200
E4V6.................................................................................................................................. 200
E4V7.................................................................................................................................. 200
E4V8.................................................................................................................................. 201
E4V9.................................................................................................................................. 201
E4VA ................................................................................................................................. 201
E4VB ................................................................................................................................. 201
E4VC................................................................................................................................. 202
E4VD................................................................................................................................. 202
E4VE ................................................................................................................................. 202
E4VF.................................................................................................................................. 202
E4VG................................................................................................................................. 202
E4VH................................................................................................................................. 203
E4VI................................................................................................................................... 203
E4W0................................................................................................................................. 203
E4X0.................................................................................................................................. 203
E4X1.................................................................................................................................. 204
E4X2.................................................................................................................................. 204
E500 .................................................................................................................................. 204
E600 .................................................................................................................................. 204
E601 .................................................................................................................................. 205
E602 .................................................................................................................................. 205
E603 .................................................................................................................................. 205
E604 .................................................................................................................................. 205
E605 .................................................................................................................................. 206
E606 .................................................................................................................................. 206
E607 .................................................................................................................................. 206
E608 .................................................................................................................................. 206
E609 .................................................................................................................................. 207
E610 .................................................................................................................................. 207
Contents
Release 100 Experion PKS

Troubleshooting and Notifications Reference xxi

1/03 Honeywell
E611.................................................................................................................................. 207
E612.................................................................................................................................. 207
E614.................................................................................................................................. 208
E615.................................................................................................................................. 208
E631.................................................................................................................................. 208
E640.................................................................................................................................. 208
E641.................................................................................................................................. 209
E642.................................................................................................................................. 209
E643.................................................................................................................................. 209
E644.................................................................................................................................. 209
E645.................................................................................................................................. 210
E646.................................................................................................................................. 210
E647.................................................................................................................................. 210
E648.................................................................................................................................. 210
E649.................................................................................................................................. 211
E650.................................................................................................................................. 211
E651.................................................................................................................................. 211
E652.................................................................................................................................. 211
E653.................................................................................................................................. 212
E654.................................................................................................................................. 212
E655.................................................................................................................................. 212
E656.................................................................................................................................. 212
E660.................................................................................................................................. 213
E670.................................................................................................................................. 213
E671.................................................................................................................................. 213
E672.................................................................................................................................. 213
E673.................................................................................................................................. 214
E680.................................................................................................................................. 214
E690.................................................................................................................................. 214
E6A0.................................................................................................................................. 214
E6B0.................................................................................................................................. 215
E6C0 ................................................................................................................................. 215
E6C1 ................................................................................................................................. 215
E6C2 ................................................................................................................................. 215
E6C3 ................................................................................................................................. 216
E6C4 ................................................................................................................................. 216
E6C5 ................................................................................................................................. 216
E6C6 ................................................................................................................................. 216
E6C7 ................................................................................................................................. 217
E6C8 ................................................................................................................................. 217
E6C9 ................................................................................................................................. 217
E6CA................................................................................................................................. 217
E6CB................................................................................................................................. 218
E6CC................................................................................................................................. 218
E6CD................................................................................................................................. 218
E6D0 ................................................................................................................................. 218
E6D1 ................................................................................................................................. 219
E6D2 ................................................................................................................................. 219
E6D3 ................................................................................................................................. 219
Contents
xxii Experion PKS

Troubleshooting and Notifications Reference Release 100

Honeywell 1/03
E6D4.................................................................................................................................. 219
E6E0.................................................................................................................................. 220
E6F0.................................................................................................................................. 220
E700 .................................................................................................................................. 220
E701 .................................................................................................................................. 220
E702 .................................................................................................................................. 221
E703 .................................................................................................................................. 221
E704 .................................................................................................................................. 221
E70E.................................................................................................................................. 221
E70G ................................................................................................................................. 222
E70H.................................................................................................................................. 222
E70L .................................................................................................................................. 222
E70N.................................................................................................................................. 222
E70Q ................................................................................................................................. 223
E70T.................................................................................................................................. 223
E70U.................................................................................................................................. 223
E70V.................................................................................................................................. 223
E70W................................................................................................................................. 224
E710 .................................................................................................................................. 224
E711 .................................................................................................................................. 224
E712 .................................................................................................................................. 224
E713 .................................................................................................................................. 225
E714 .................................................................................................................................. 225
E715 .................................................................................................................................. 225
E716 .................................................................................................................................. 225
E717 .................................................................................................................................. 226
E718 .................................................................................................................................. 226
E719 .................................................................................................................................. 226
E71A.................................................................................................................................. 226
E71B.................................................................................................................................. 227
E71C.................................................................................................................................. 227
E71D.................................................................................................................................. 227
E71E.................................................................................................................................. 227
E71F.................................................................................................................................. 228
E71G ................................................................................................................................. 228
E71H.................................................................................................................................. 228
E71I ................................................................................................................................... 228
E71J .................................................................................................................................. 228
E720 .................................................................................................................................. 229
E721 .................................................................................................................................. 229
E722 .................................................................................................................................. 229
E723 .................................................................................................................................. 229
E724 .................................................................................................................................. 230
E725 .................................................................................................................................. 230
E726 .................................................................................................................................. 230
E727 .................................................................................................................................. 230
E728 .................................................................................................................................. 231
E729 .................................................................................................................................. 231
E72A.................................................................................................................................. 231
Contents
Release 100 Experion PKS

Troubleshooting and Notifications Reference xxiii

1/03 Honeywell
E72B.................................................................................................................................. 231
E72C ................................................................................................................................. 231
E72D ................................................................................................................................. 232
E730.................................................................................................................................. 232
E731.................................................................................................................................. 232
E732.................................................................................................................................. 232
E733.................................................................................................................................. 232
E734.................................................................................................................................. 233
E735.................................................................................................................................. 233
E736.................................................................................................................................. 233
E737.................................................................................................................................. 234
E738.................................................................................................................................. 234
E739.................................................................................................................................. 234
E73A.................................................................................................................................. 234
E73C ................................................................................................................................. 235
E73D ................................................................................................................................. 235
E73F.................................................................................................................................. 235
E73G................................................................................................................................. 235
E73H ................................................................................................................................. 236
E73I ................................................................................................................................... 236
E740.................................................................................................................................. 236
E741.................................................................................................................................. 236
E742.................................................................................................................................. 237
E752.................................................................................................................................. 237
E753.................................................................................................................................. 237
E754.................................................................................................................................. 237
E755.................................................................................................................................. 238
E756.................................................................................................................................. 238
E757.................................................................................................................................. 238
E75A.................................................................................................................................. 238
E75B.................................................................................................................................. 239
E75C ................................................................................................................................. 239
E75D ................................................................................................................................. 239
E75E.................................................................................................................................. 239
E75F.................................................................................................................................. 240
E75G................................................................................................................................. 240
E75I ................................................................................................................................... 240
E75J .................................................................................................................................. 240
E75K.................................................................................................................................. 241
E75L.................................................................................................................................. 241
E75M................................................................................................................................. 241
E760.................................................................................................................................. 241
E762.................................................................................................................................. 242
E763.................................................................................................................................. 242
E764.................................................................................................................................. 242
E766.................................................................................................................................. 242
E767.................................................................................................................................. 243
E768.................................................................................................................................. 243
E769.................................................................................................................................. 243
Contents
xxiv Experion PKS

Troubleshooting and Notifications Reference Release 100

Honeywell 1/03
E76A.................................................................................................................................. 243
E76C.................................................................................................................................. 244
E76D.................................................................................................................................. 244
E76E.................................................................................................................................. 244
E76F.................................................................................................................................. 244
E770 .................................................................................................................................. 245
E771 .................................................................................................................................. 245
E772 .................................................................................................................................. 245
E774 .................................................................................................................................. 245
E777 .................................................................................................................................. 246
E778 .................................................................................................................................. 246
E779 .................................................................................................................................. 246
E77A.................................................................................................................................. 246
E77C.................................................................................................................................. 247
E77E.................................................................................................................................. 247
E77H.................................................................................................................................. 247
E77I ................................................................................................................................... 247
E77J .................................................................................................................................. 248
E77K.................................................................................................................................. 248
E790 .................................................................................................................................. 248
E791 .................................................................................................................................. 248
E792 .................................................................................................................................. 249
E7B1.................................................................................................................................. 249
E7B2.................................................................................................................................. 249
E7B3.................................................................................................................................. 249
E7B4.................................................................................................................................. 250
E7B6.................................................................................................................................. 250
E7B7.................................................................................................................................. 250
E7B8.................................................................................................................................. 250
E7B9.................................................................................................................................. 251
E7BA ................................................................................................................................. 251
E7BB ................................................................................................................................. 251
E7BC................................................................................................................................. 251
E7BD................................................................................................................................. 252
E7BE ................................................................................................................................. 252
E7BF.................................................................................................................................. 252
E7BG................................................................................................................................. 252
E7BH................................................................................................................................. 253
E7BI................................................................................................................................... 253
E7BJ.................................................................................................................................. 253
E7BL.................................................................................................................................. 253
E7BM................................................................................................................................. 254
E7BN................................................................................................................................. 254
E7BQ................................................................................................................................. 254
E7BT.................................................................................................................................. 254
E7BU................................................................................................................................. 255
E800 .................................................................................................................................. 255
E801 .................................................................................................................................. 255
E810 .................................................................................................................................. 255
Contents
Release 100 Experion PKS

Troubleshooting and Notifications Reference xxv

1/03 Honeywell
E811.................................................................................................................................. 256
E812.................................................................................................................................. 256
E813.................................................................................................................................. 256
E814.................................................................................................................................. 256
E815.................................................................................................................................. 257
E816.................................................................................................................................. 257
E817.................................................................................................................................. 257
E818.................................................................................................................................. 257
E819.................................................................................................................................. 258
E81A.................................................................................................................................. 258
E81B.................................................................................................................................. 258
E81C ................................................................................................................................. 258
E81D ................................................................................................................................. 259
E81E.................................................................................................................................. 259
E820.................................................................................................................................. 259
E821.................................................................................................................................. 259
E830.................................................................................................................................. 260
E831.................................................................................................................................. 260
E832.................................................................................................................................. 260
E833.................................................................................................................................. 260
E834.................................................................................................................................. 260
E835.................................................................................................................................. 261
E836.................................................................................................................................. 261
E840.................................................................................................................................. 261
E841.................................................................................................................................. 261
E850.................................................................................................................................. 262
E851.................................................................................................................................. 262
E852.................................................................................................................................. 262
E860.................................................................................................................................. 262
E861.................................................................................................................................. 262
E862.................................................................................................................................. 263
E870.................................................................................................................................. 263
E871.................................................................................................................................. 263
E872.................................................................................................................................. 263
E873.................................................................................................................................. 263
E876.................................................................................................................................. 264
E880.................................................................................................................................. 264
E881.................................................................................................................................. 264
E882.................................................................................................................................. 264
E883.................................................................................................................................. 264
E884.................................................................................................................................. 265
E885.................................................................................................................................. 265
E886.................................................................................................................................. 265
E887.................................................................................................................................. 265
E888.................................................................................................................................. 266
E889.................................................................................................................................. 266
E88A.................................................................................................................................. 266
E88B.................................................................................................................................. 266
E88C ................................................................................................................................. 267
Contents
xxvi Experion PKS

Troubleshooting and Notifications Reference Release 100

Honeywell 1/03
E88D.................................................................................................................................. 267
E88E.................................................................................................................................. 267
E891 .................................................................................................................................. 267
E892 .................................................................................................................................. 268
E893 .................................................................................................................................. 268
E894 .................................................................................................................................. 268
E895 .................................................................................................................................. 268
E896 .................................................................................................................................. 269
E8A0.................................................................................................................................. 269
E8A1.................................................................................................................................. 269
E8A2.................................................................................................................................. 269
E8A3.................................................................................................................................. 270
E8A4.................................................................................................................................. 270
E8A5.................................................................................................................................. 270
E8B0.................................................................................................................................. 270
EA00.................................................................................................................................. 270
EA01.................................................................................................................................. 271
EA02.................................................................................................................................. 271
EA03.................................................................................................................................. 271
EA04.................................................................................................................................. 271
EA05.................................................................................................................................. 271
EA10.................................................................................................................................. 272
EA11.................................................................................................................................. 272
EA12.................................................................................................................................. 272
EA13.................................................................................................................................. 272
EA14.................................................................................................................................. 272
EA15.................................................................................................................................. 273
EA16.................................................................................................................................. 273
EA17.................................................................................................................................. 273
EA18.................................................................................................................................. 273
EA19.................................................................................................................................. 273
EA1B ................................................................................................................................. 274
EA1C................................................................................................................................. 274
EA1D................................................................................................................................. 274
EA1E ................................................................................................................................. 274
EA1F.................................................................................................................................. 274
EA1G................................................................................................................................. 275
EA1H................................................................................................................................. 275
EA1I................................................................................................................................... 275
EA1J.................................................................................................................................. 275
EA1K ................................................................................................................................. 275
EA1L.................................................................................................................................. 276
EA1M................................................................................................................................. 276
EA1N................................................................................................................................. 276
EA1P ................................................................................................................................. 276
EA1Q................................................................................................................................. 276
EA1R................................................................................................................................. 277
EA1T.................................................................................................................................. 277
EA1U................................................................................................................................. 277
Contents
Release 100 Experion PKS

Troubleshooting and Notifications Reference xxvii

1/03 Honeywell
EA1V................................................................................................................................. 277
EA1W ................................................................................................................................ 278
EA20.................................................................................................................................. 278
EA21.................................................................................................................................. 278
EA22.................................................................................................................................. 278
EA23.................................................................................................................................. 279
EA24.................................................................................................................................. 279
EA25.................................................................................................................................. 279
EA26.................................................................................................................................. 279
EA27.................................................................................................................................. 279
EA28.................................................................................................................................. 280
EA29.................................................................................................................................. 280
EA2A................................................................................................................................. 280
EA2B................................................................................................................................. 280
EA2C................................................................................................................................. 281
EA2E................................................................................................................................. 281
EA2F ................................................................................................................................. 281
EA2G................................................................................................................................. 281
EA2H................................................................................................................................. 282
EA2I................................................................................................................................... 282
EA2J.................................................................................................................................. 282
EA2K................................................................................................................................. 282
EA2L.................................................................................................................................. 283
EA2M................................................................................................................................. 283
EA30.................................................................................................................................. 283
EA31.................................................................................................................................. 283
EA32.................................................................................................................................. 283
EA33.................................................................................................................................. 284
EA34.................................................................................................................................. 284
EA35.................................................................................................................................. 284
EA36.................................................................................................................................. 284
EA37.................................................................................................................................. 285
EA38.................................................................................................................................. 285
EA39.................................................................................................................................. 285
EA3A................................................................................................................................. 285
EA3B................................................................................................................................. 285
EA3C................................................................................................................................. 286
EA3D................................................................................................................................. 286
EA3E................................................................................................................................. 286
EA3F ................................................................................................................................. 286
EA3G................................................................................................................................. 286
EA3H................................................................................................................................. 287
EA3I................................................................................................................................... 287
EA3J.................................................................................................................................. 287
EA3K................................................................................................................................. 287
EA3L.................................................................................................................................. 288
EA3N................................................................................................................................. 288
EA3P................................................................................................................................. 288
EA3Q................................................................................................................................. 288
Contents
xxviii Experion PKS

Troubleshooting and Notifications Reference Release 100

Honeywell 1/03
EA3R................................................................................................................................. 289
EA3T.................................................................................................................................. 289
EA3U................................................................................................................................. 289
EA3V ................................................................................................................................. 289
EA40.................................................................................................................................. 289
EA41.................................................................................................................................. 290
EA42.................................................................................................................................. 290
EA43.................................................................................................................................. 290
EA44.................................................................................................................................. 290
EA45.................................................................................................................................. 290
EA46.................................................................................................................................. 291
EA47.................................................................................................................................. 291
EA48.................................................................................................................................. 291
EA49.................................................................................................................................. 291
EA4A ................................................................................................................................. 291
EA4B ................................................................................................................................. 292
EA4C................................................................................................................................. 292
EA4E ................................................................................................................................. 292
EA4F.................................................................................................................................. 292
EA4G................................................................................................................................. 293
EA4H................................................................................................................................. 293
EA4I................................................................................................................................... 293
EA4J.................................................................................................................................. 293
EA4K ................................................................................................................................. 293
EA4L.................................................................................................................................. 294
EA4M................................................................................................................................. 294
EA50.................................................................................................................................. 294
EA51.................................................................................................................................. 294
EA52.................................................................................................................................. 294
EA53.................................................................................................................................. 295
EA54.................................................................................................................................. 295
EA55.................................................................................................................................. 295
EA56.................................................................................................................................. 295
EA57.................................................................................................................................. 295
EA58.................................................................................................................................. 296
EA59.................................................................................................................................. 296
EA5A ................................................................................................................................. 296
EA5B ................................................................................................................................. 296
EA5D................................................................................................................................. 297
EA5E ................................................................................................................................. 297
EA5F.................................................................................................................................. 297
EA5G................................................................................................................................. 297
EA5H................................................................................................................................. 297
EA5I................................................................................................................................... 298
EA5J.................................................................................................................................. 298
EA5K ................................................................................................................................. 298
EA80.................................................................................................................................. 298
EA81.................................................................................................................................. 298
EA82.................................................................................................................................. 299
Contents
Release 100 Experion PKS

Troubleshooting and Notifications Reference xxix

1/03 Honeywell
EA83.................................................................................................................................. 299
EA84.................................................................................................................................. 299
EA85.................................................................................................................................. 299
EA86.................................................................................................................................. 299
EA87.................................................................................................................................. 300
EA88.................................................................................................................................. 300
EA89.................................................................................................................................. 300
EA8A................................................................................................................................. 300
EA8B................................................................................................................................. 301
EA8C................................................................................................................................. 301
EA90.................................................................................................................................. 301
EA91.................................................................................................................................. 301
EA92.................................................................................................................................. 302
EA93.................................................................................................................................. 302
EA94.................................................................................................................................. 302
EA95.................................................................................................................................. 302
EA96.................................................................................................................................. 302
EA97.................................................................................................................................. 303
EA98.................................................................................................................................. 303
EA99.................................................................................................................................. 303
EA9A................................................................................................................................. 303
EA9B................................................................................................................................. 304
EAA0 ................................................................................................................................. 304
EAA1 ................................................................................................................................. 304
EAA2 ................................................................................................................................. 304
EAA3 ................................................................................................................................. 304
EAA4 ................................................................................................................................. 305
EAA5 ................................................................................................................................. 305
EAA6 ................................................................................................................................. 305
EAA7 ................................................................................................................................. 305
EAA8 ................................................................................................................................. 305
EAA9 ................................................................................................................................. 306
EAAA................................................................................................................................. 306
EAAB................................................................................................................................. 306
EAAC................................................................................................................................. 306
EAAD................................................................................................................................. 307
EAAF................................................................................................................................. 307
EAAG ................................................................................................................................ 307
EAAH................................................................................................................................. 307
EAAI .................................................................................................................................. 307
EAAJ ................................................................................................................................. 308
EAAK................................................................................................................................. 308
EAAL ................................................................................................................................. 308
EAAM................................................................................................................................ 308
EAAN................................................................................................................................. 308
EAB0 ................................................................................................................................. 309
EAB1 ................................................................................................................................. 309
EAB2 ................................................................................................................................. 309
EAB3 ................................................................................................................................. 309
Contents
xxx Experion PKS

Troubleshooting and Notifications Reference Release 100

Honeywell 1/03
EAB4 ................................................................................................................................. 309
EAB5 ................................................................................................................................. 310
EAB6 ................................................................................................................................. 310
EAB7 ................................................................................................................................. 310
EAB8 ................................................................................................................................. 310
EAB9 ................................................................................................................................. 311
EABA................................................................................................................................. 311
EABB................................................................................................................................. 311
EABC................................................................................................................................. 311
EAC0 ................................................................................................................................. 311
EAC1 ................................................................................................................................. 312
EAC2 ................................................................................................................................. 312
EAC3 ................................................................................................................................. 312
EAC4 ................................................................................................................................. 312
EADO ................................................................................................................................ 312
EAD1 ................................................................................................................................. 313
EAD2 ................................................................................................................................. 313
EAD3 ................................................................................................................................. 313
EAD4 ................................................................................................................................. 313
EAD5 ................................................................................................................................. 313
EAD6 ................................................................................................................................. 314
EAD7 ................................................................................................................................. 314
EAD8 ................................................................................................................................. 314
EAD9 ................................................................................................................................. 314
EADA................................................................................................................................. 314
EADB................................................................................................................................. 315
EADC................................................................................................................................. 315
EADD................................................................................................................................. 315
EADE................................................................................................................................. 315
EADF................................................................................................................................. 315
EADG ................................................................................................................................ 316
EAE0 ................................................................................................................................. 316
EAE1 ................................................................................................................................. 316
EAE2 ................................................................................................................................. 316
EAE3 ................................................................................................................................. 317
EAE4 ................................................................................................................................. 317
EAE5 ................................................................................................................................. 317
EAE6 ................................................................................................................................. 317
EAE7 ................................................................................................................................. 318
EAE8 ................................................................................................................................. 318
EAE9 ................................................................................................................................. 318
EAEA................................................................................................................................. 318
EAEB................................................................................................................................. 319
EAEC................................................................................................................................. 319
EAF0.................................................................................................................................. 319
EAF1.................................................................................................................................. 319
EAF2.................................................................................................................................. 320
EAF3.................................................................................................................................. 320
EAF4.................................................................................................................................. 320
Contents
Release 100 Experion PKS

Troubleshooting and Notifications Reference xxxi

1/03 Honeywell
EAF5 ................................................................................................................................. 320
EAG0................................................................................................................................. 321
EAG1................................................................................................................................. 321
EAG2................................................................................................................................. 321
EAG3................................................................................................................................. 321
EAH0................................................................................................................................. 321
EAH1................................................................................................................................. 322
EAH2................................................................................................................................. 322
EAH3................................................................................................................................. 322
EAI0................................................................................................................................... 322
EAI1................................................................................................................................... 322
EAJ0.................................................................................................................................. 323
EAJ1.................................................................................................................................. 323
EB00.................................................................................................................................. 323
EB01.................................................................................................................................. 323
EB02.................................................................................................................................. 324
EB03.................................................................................................................................. 324
EB05.................................................................................................................................. 324
EB06.................................................................................................................................. 324
EB10.................................................................................................................................. 325
EB11.................................................................................................................................. 325
EB12.................................................................................................................................. 325
EB13.................................................................................................................................. 325
EB14.................................................................................................................................. 325
EB15.................................................................................................................................. 326
EB16.................................................................................................................................. 326
EC00 ................................................................................................................................. 326
EC01 ................................................................................................................................. 326
EC02 ................................................................................................................................. 327
EC03 ................................................................................................................................. 327
EC04 ................................................................................................................................. 327
EC05 ................................................................................................................................. 327
EC06 ................................................................................................................................. 327
EC07 ................................................................................................................................. 328
ED00 ................................................................................................................................. 328
ED10 ................................................................................................................................. 328
ED11 ................................................................................................................................. 328
ED12 ................................................................................................................................. 329
ED13 ................................................................................................................................. 329
ED14 ................................................................................................................................. 329
ED20 ................................................................................................................................. 329
ED21 ................................................................................................................................. 330
ED22 ................................................................................................................................. 330
ED23 ................................................................................................................................. 330
ED30 ................................................................................................................................. 330
ED31 ................................................................................................................................. 331
EE00.................................................................................................................................. 331
EF00.................................................................................................................................. 331
EF10.................................................................................................................................. 331
Contents
xxxii Experion PKS

Troubleshooting and Notifications Reference Release 100

Honeywell 1/03
EF11.................................................................................................................................. 332
EF20.................................................................................................................................. 332
EF21.................................................................................................................................. 332
EF22.................................................................................................................................. 332
EF23.................................................................................................................................. 332
EF24.................................................................................................................................. 333
EF30.................................................................................................................................. 333
EG02 ................................................................................................................................. 333
EG10 ................................................................................................................................. 333
EG11 ................................................................................................................................. 334
EH01.................................................................................................................................. 334
EH02.................................................................................................................................. 334
EH03.................................................................................................................................. 334
EH04.................................................................................................................................. 335
EH05.................................................................................................................................. 335
EH06.................................................................................................................................. 335
EH07.................................................................................................................................. 335
EH0A................................................................................................................................. 336
EH10.................................................................................................................................. 336
EH11.................................................................................................................................. 336
EH12.................................................................................................................................. 336
EH20.................................................................................................................................. 337
EH21.................................................................................................................................. 337
EH22.................................................................................................................................. 337
EH23.................................................................................................................................. 337
EH24.................................................................................................................................. 338
EH25.................................................................................................................................. 338
EH26.................................................................................................................................. 338
EH27.................................................................................................................................. 338
EH28.................................................................................................................................. 339
EH29.................................................................................................................................. 339
EH2A................................................................................................................................. 339
EH2B................................................................................................................................. 339
EH30.................................................................................................................................. 340
EH3A................................................................................................................................. 340
EH31.................................................................................................................................. 340
EH32.................................................................................................................................. 340
EH33.................................................................................................................................. 341
EH34.................................................................................................................................. 341
EH35.................................................................................................................................. 341
EH36.................................................................................................................................. 341
EH37.................................................................................................................................. 342
EH38.................................................................................................................................. 342
EH39.................................................................................................................................. 342
EH40.................................................................................................................................. 342
EH41.................................................................................................................................. 343
EH42.................................................................................................................................. 343
EH43.................................................................................................................................. 343
EH44.................................................................................................................................. 343
Contents
Release 100 Experion PKS

Troubleshooting and Notifications Reference xxxiii

1/03 Honeywell
EH45 ................................................................................................................................. 344
EH46 ................................................................................................................................. 344
EH47 ................................................................................................................................. 344
EH48 ................................................................................................................................. 344
EH49 ................................................................................................................................. 345
EH4A................................................................................................................................. 345
EH50 ................................................................................................................................. 345
EH5A................................................................................................................................. 345
EH51 ................................................................................................................................. 346
EH52 ................................................................................................................................. 346
EH53 ................................................................................................................................. 346
EH60 ................................................................................................................................. 346
EH70 ................................................................................................................................. 347
EH71 ................................................................................................................................. 347
EH72 ................................................................................................................................. 347
EH73 ................................................................................................................................. 347
EH74 ................................................................................................................................. 348
EH75 ................................................................................................................................. 348
EH76 ................................................................................................................................. 348
EH77 ................................................................................................................................. 348
EH78 ................................................................................................................................. 349
EH79 ................................................................................................................................. 349
EH7A................................................................................................................................. 349
EH7B................................................................................................................................. 349
EH7C................................................................................................................................. 350
EH7D................................................................................................................................. 350
EHA1................................................................................................................................. 350
EHA2................................................................................................................................. 350
EHA3................................................................................................................................. 351
EHA4................................................................................................................................. 351
EHA5................................................................................................................................. 351
EHA6................................................................................................................................. 351
EHA7................................................................................................................................. 352
EHA8................................................................................................................................. 352
EHA9................................................................................................................................. 352
EHAA................................................................................................................................. 352
EHAB................................................................................................................................. 353
EHAC ................................................................................................................................ 353
EHAD ................................................................................................................................ 353
EHAE................................................................................................................................. 353
EHAF................................................................................................................................. 354
EHAG................................................................................................................................ 354
EHAH ................................................................................................................................ 354
EHAJ ................................................................................................................................. 354
EHAK................................................................................................................................. 355
EHAL................................................................................................................................. 355
EHAM................................................................................................................................ 355
EHAN ................................................................................................................................ 355
EHAP................................................................................................................................. 356
Contents
xxxiv Experion PKS

Troubleshooting and Notifications Reference Release 100

Honeywell 1/03
EHAR................................................................................................................................. 356
EHAT................................................................................................................................. 356
EHAV................................................................................................................................. 356
EI00 ................................................................................................................................... 357
EI01 ................................................................................................................................... 357
EI02 ................................................................................................................................... 357
EI03 ................................................................................................................................... 357
EI10 ................................................................................................................................... 358
EI40 ................................................................................................................................... 358
EI50 ................................................................................................................................... 358
EI51 ................................................................................................................................... 358
EI52 ................................................................................................................................... 359
EI53 ................................................................................................................................... 359
EI60 ................................................................................................................................... 359
EI61 ................................................................................................................................... 359
EI62 ................................................................................................................................... 360
EI63 ................................................................................................................................... 360
EI64 ................................................................................................................................... 360
EI70 ................................................................................................................................... 360
EI71 ................................................................................................................................... 361
EI72 ................................................................................................................................... 361
EI73 ................................................................................................................................... 361
EI74 ................................................................................................................................... 361
EI75 ................................................................................................................................... 362
EI80 ................................................................................................................................... 362
EI81 ................................................................................................................................... 362
EI90 ................................................................................................................................... 362
EIZ0................................................................................................................................... 363
EJ00 .................................................................................................................................. 363
EJ01 .................................................................................................................................. 363
EJ02 .................................................................................................................................. 363
EJ10 .................................................................................................................................. 364
EJ11 .................................................................................................................................. 364
EJ12 .................................................................................................................................. 364
EJ13 .................................................................................................................................. 364
EJ20 .................................................................................................................................. 364
EK10.................................................................................................................................. 365
EK21.................................................................................................................................. 365
EK22.................................................................................................................................. 365
EK23.................................................................................................................................. 365
EK24.................................................................................................................................. 366
EK25.................................................................................................................................. 366
EK26.................................................................................................................................. 366
EK27.................................................................................................................................. 367
EK28.................................................................................................................................. 367
EK29.................................................................................................................................. 367
EK2A ................................................................................................................................. 368
EK2B ................................................................................................................................. 368
EK2C................................................................................................................................. 368
Contents
Release 100 Experion PKS

Troubleshooting and Notifications Reference xxxv

1/03 Honeywell
EK40.................................................................................................................................. 368
EK70.................................................................................................................................. 369
EKA0 ................................................................................................................................. 369
EKC0................................................................................................................................. 369
EKD0................................................................................................................................. 369
EKE0 ................................................................................................................................. 370
EKF0 ................................................................................................................................. 370
EKG0................................................................................................................................. 370
EKT1 ................................................................................................................................. 370
EKU0................................................................................................................................. 371
Experion PKS Notifications ................................................................. 373
CPM FB Generated Notifications .............................................................................373
Backup State..................................................................................................................... 373
Battery Not OK .................................................................................................................. 373
Not Synchronized .............................................................................................................. 373
RAM Sweep Error(s) ......................................................................................................... 374
RAM Scrub Errors ............................................................................................................. 374
REDUN Chassis ID Unknown............................................................................................ 374
REDUN Chassis ID A........................................................................................................ 374
REDUN Chassis ID B........................................................................................................ 375
Switchover ......................................................................................................................... 375
Sync Checksum Fail .......................................................................................................... 375
Sync HW Failure................................................................................................................ 376
NDM Generated Notifications...................................................................................377
Overview ........................................................................................................................... 377
BOOTP Enabled................................................................................................................ 380
Cable Failure..................................................................................................................... 380
Card Added ....................................................................................................................... 380
Card Failure....................................................................................................................... 380
Card Removed .................................................................................................................. 381
Comm Failure.................................................................................................................... 381
Driver Added...................................................................................................................... 381
Driver Removed................................................................................................................. 382
Intermittent Comm Failure................................................................................................. 382
Invalid Keeper.................................................................................................................... 383
KTC Failure ....................................................................................................................... 383
KTC Normal....................................................................................................................... 383
Missing Keeper.................................................................................................................. 384
PCIC Failure...................................................................................................................... 384
PCIC Normal ..................................................................................................................... 384
RSLinx Initialization Failure ............................................................................................... 385
RSLinx Initialized............................................................................................................... 385
RSLinx Failure................................................................................................................... 385
RSLinx Normal .................................................................................................................. 385
UMAX Exceeded ............................................................................................................... 386
Contents
xxxvi Experion PKS

Troubleshooting and Notifications Reference Release 100

Honeywell 1/03
RM Events........................................................................................... 387
Overview.................................................................................................................. 387
CNI Generated RM Events ...................................................................................... 388
ControlNet Lonely.............................................................................................................. 388
ControlNet Not Lonely ....................................................................................................... 388
NetWork Entity Gone......................................................................................................... 388
MacID Switches Changed to Bad...................................................................................... 389
MacID Switches Changed to OK ....................................................................................... 389
Bad CNet Ping for Sec Connection.................................................................................... 389
ControlNet Duplicate Node................................................................................................ 390
ControlNet Unduplicate Node............................................................................................ 390
Revision Not Compatible ................................................................................................... 390
Node Number Not Identical ............................................................................................... 391
Partner Not Scanner .......................................................................................................... 391
Not Recognized Vendor..................................................................................................... 391
Not Compatible Vendor ..................................................................................................... 392
Unrecognized Product Code.............................................................................................. 392
False ControlNet Partner ................................................................................................... 392
Keeper Info Not Identical ................................................................................................... 393
Incompatible Product Code ............................................................................................... 393
ControlNet Ping Transmit Problem.................................................................................... 393
ControlNet Ping Transmit Success.................................................................................... 394
ICP debug - NoIcpCbFree ................................................................................................. 394
ICP debug - BadIcpFreeCbId ............................................................................................ 394
ICP debug - IcpCbFree0.................................................................................................... 395
Smac Spontaneous ListenOnly_Mute................................................................................ 395
Keeper Write...................................................................................................................... 395
Partner Detected................................................................................................................ 396
Smac Fail........................................................................................................................... 396
Illegal Partner Compat. Status........................................................................................... 396
Partner In Wrong Module State ......................................................................................... 397
Partner Not Changed - Qualifying...................................................................................... 397
Qualifying Notification Not Sent ......................................................................................... 397
Not Compatible.................................................................................................................. 398
Xload Unsuccessful ........................................................................................................... 398
Partner Not Changed to Qualified...................................................................................... 398
Qualified Notification Not Sent........................................................................................... 399
Qual Phase2 Req Out Of Sequence.................................................................................. 399
Qual Phase3 Req Out Of Sequence.................................................................................. 399
Qual Phase4 Req Out Of Sequence.................................................................................. 400
ICP ASIC Still timing.......................................................................................................... 400
ICP ASIC Recovered......................................................................................................... 400
Qualify Fail Due to DISQ_EVENT...................................................................................... 401
Spurious Buffer Pointer Error............................................................................................. 401
Keeper Error ...................................................................................................................... 401
Combuf Pool ID Invalid...................................................................................................... 402
Module Cmpt Disq Detected #2......................................................................................... 402
Contents
Release 100 Experion PKS

Troubleshooting and Notifications Reference xxxvii

1/03 Honeywell
Partner Offline And Not Lonely.......................................................................................... 402
Bad UMAX......................................................................................................................... 402
Good UMAX ...................................................................................................................... 403
Keeper Info Updated ......................................................................................................... 403
Process Disqualification .................................................................................................... 403
Partner Connection Closed ............................................................................................... 403
Partner Connection Exists ................................................................................................. 404
Failed To Create Partner Conn.......................................................................................... 404
Create Partner Conn Retry................................................................................................ 404
Qualifying Disq-Detected #2.............................................................................................. 404
Retry Partner SMAC Not Stable ........................................................................................ 405
Module Not Cmpt............................................................................................................... 405
Retry Xmit Failure.............................................................................................................. 405
Entered Qual Phase1 ........................................................................................................ 405
Qualified Disq-Detected #2................................................................................................ 406
Partner Not Set To Qualifying............................................................................................ 406
Qualifying Not Sent To Partner.......................................................................................... 406
Qual Phase1 OutOfSequence Error .................................................................................. 406
Entered Qual Phase2 ........................................................................................................ 407
Qual Phase2 OutOfSequence Error .................................................................................. 407
Entered Qual Phase3 ........................................................................................................ 407
Partner Not Set To Qualified.............................................................................................. 407
Qualified Not Sent To Partner............................................................................................ 408
Qual Phase3 OutOfSequence Error .................................................................................. 408
Entered Qual Phase4 ........................................................................................................ 408
Qual Phase4 OutOfSequence Error .................................................................................. 408
Qualifying Cant Xmit.......................................................................................................... 409
Reply To RSN disqualification........................................................................................... 409
Module Cmpt No Partner Conn ......................................................................................... 409
Module Cmpt XmitBuff Unavailable................................................................................... 409
Module Cmpt No Response............................................................................................... 410
Module Cmpt Disq Detected #1......................................................................................... 410
Module Cmpt Cant Xmit .................................................................................................... 410
Qualified Cant Xmit............................................................................................................ 410
Qualifying Disq-Detected #1.............................................................................................. 411
Qualified Disq-Detected #1................................................................................................ 411
Qualifying No Response.................................................................................................... 411
Qualified No Response...................................................................................................... 411
Qualifying Xmit Buff Unavailable ....................................................................................... 412
Qualified Xmit Buff Unavailable ......................................................................................... 412
Qualifying No Partner Conn............................................................................................... 412
Qualified No Partner Conn ................................................................................................ 412
CPM Generated RM Events.....................................................................................413
LOS_CLEANPOINT_BUFFER_OVERFLOW.................................................................... 413
LOS_CLEANPOINT_FIFO_OVERFLOW.......................................................................... 413
LOS_CLEANPOINT_IDLE_TIMEOUT .............................................................................. 414
LOS_CLEANPOINT_RX_FAILURE .................................................................................. 414
LOS_CLEANPOINT_TX_FAILURE................................................................................... 415
Contents
xxxviii Experion PKS

Troubleshooting and Notifications Reference Release 100

Honeywell 1/03
LOS_CPM_CONFIG_LOAD_IN_PROGRESS.................................................................. 415
SYN_CPM_CONFIG_LOAD_END.................................................................................... 416
LOS_CROSSLOAD_ERROR............................................................................................ 416
LOS_EDIT_RESOURCE_LOCKED .................................................................................. 416
LOS_EXEC_SYNC_TIMEOUT.......................................................................................... 417
LOS_IOMGR_PURGE_INPROG....................................................................................... 417
LOS_ISR_BUFFER_OVERFLOW..................................................................................... 418
LOS_ISR_FIFO_OVERFLOW........................................................................................... 418
LOS_ISR_RX_FAILURE ................................................................................................... 419
LOS_ISR_TX_FAILURE.................................................................................................... 419
LOS_KEEP_ALIVE_BUFFER_OVERFLOW..................................................................... 420
LOS_KEEP_ALIVE_FIFO_OVERFLOW........................................................................... 420
LOS_KEEP_ALIVE_RX_FAILURE.................................................................................... 421
LOS_KEEP_ALIVE_TX_FAILURE.................................................................................... 421
LOS_PARTNER_ABSENT................................................................................................ 422
LOS_PARTNER_INCOMPATIBLE.................................................................................... 423
LOS_PARTNER_STARTUP_INCOMPLETE .................................................................... 424
LOS_MOVE_BUFFER_OVERFLOW................................................................................ 424
LOS_MOVE_FIFO_OVERFLOW ...................................................................................... 425
LOS_MOVE_RX_FAILURE............................................................................................... 425
LOS_MOVE_TX_FAILURE ............................................................................................... 426
LOS_RM_CONNECTION_TIMEOUT................................................................................ 426
LOS_SD_IDLE_TIMEOUT ................................................................................................ 427
LOS_SEC_CLEANPOINT_SEQ_ERROR......................................................................... 427
LOS_SEC_SD_SEQ_ERROR........................................................................................... 428
LOS_SEC_TD_ACCUMULATE_FORMAT_ERROR......................................................... 429
LOS_SEC_TD_ACCUMULATE_OVERRUN..................................................................... 430
LOS_SEC_TD_COMMIT_FORMAT_ERROR................................................................... 431
LOS_SEC_TD_SEQ_ERROR........................................................................................... 431
LOS_SEC_TD_UNPACK_FORMAT_ERROR .................................................................. 432
LOS_SWITCHOVER_TEST.............................................................................................. 432
LOS_SYNC_CHECKSUM_FAILURE................................................................................ 433
LOS_SYNC_HW_FAILURE_PRIMARY............................................................................ 434
LOS_SYNC_HW_FAILURE_SECONDARY...................................................................... 435
LOS_TD_BUFFER_TIMEOUT .......................................................................................... 436
LOS_TD_PENDING_RX_FAILURE .................................................................................. 436
LOS_TD_PENDING_TX_FAILURE................................................................................... 437
SYN_IOMGR_PURGE_COMPLETE................................................................................. 437
SYN_PARTNER_STARTUP_COMPLETE........................................................................ 438
DBG_PSEUDO_DATABASE_WRITES............................................................................. 438
LOS_SD_CONN_OPEN_FAILURE................................................................................... 438
LOS_SD_CONN_RX_FAILURE........................................................................................ 439
LOS_SD_CONN_TX_FAILURE ........................................................................................ 439
LOS_TD_CONN_OPEN_FAILURE................................................................................... 440
LOS_TD_CONN_RX_FAILURE........................................................................................ 440
LOS_SEC_CLEANPOINT_COMMIT_TIMEOUT............................................................... 441
LOS_EDIT_RESOURCE_CLEAR_INPROG..................................................................... 441
SYN_EDIT_RESOURCE_CLEAR_COMPLETE ............................................................... 442
LOS_UNKNOWN_SECONDARY_LOS............................................................................. 442
Contents
Release 100 Experion PKS

Troubleshooting and Notifications Reference xxxix

1/03 Honeywell
RM Generated Events..............................................................................................443
Communication resource error .......................................................................................... 443
Operating system error...................................................................................................... 443
Port1 Communication resource err.................................................................................... 444
Port2 Communication resource err.................................................................................... 444
Watchdog time-out ............................................................................................................ 444
Hardware failure ................................................................................................................ 445
Firmware error ................................................................................................................... 445
Configuration log error....................................................................................................... 445
Dup. RM, This one not in control ....................................................................................... 446
RM Power Down................................................................................................................ 446
Port1 Communication Error ............................................................................................... 446
Port2 Communication Error ............................................................................................... 447
Communication Error......................................................................................................... 447
Event Log Error ................................................................................................................. 448
Autoqual. Option Always ................................................................................................... 448
Autoqual. Option Never ..................................................................................................... 449
Autoqual. Option Conditional ............................................................................................. 449
Program Red. Ini. Cmd Disabled....................................................................................... 450
Program Red. Ini. Cmd Enabled........................................................................................ 450
Password Scope Neither ................................................................................................... 451
Password Scope Only Red. Cfg. ....................................................................................... 451
Password Scope Only User Cmd. ..................................................................................... 452
Password Scope Both ....................................................................................................... 452
Chassis redundancy state PwNS ...................................................................................... 453
Chassis redundancy state PwDS ...................................................................................... 453
Chassis redundancy state PwQS...................................................................................... 453
Chassis redundancy state PwSS....................................................................................... 454
Chassis redundancy state DSwNP.................................................................................... 454
Chassis redundancy state DSwP ...................................................................................... 454
Chassis redundancy state QSwP...................................................................................... 455
Chassis redundancy state SSwP....................................................................................... 455
RM Power Up .................................................................................................................... 455
Modules Chassis State Rule.............................................................................................. 456
Failed Modules Rule.......................................................................................................... 456
Disqualified Secondaries Rule........................................................................................... 457
Blank Memories Rule ........................................................................................................ 457
Standby Secondaries Rule................................................................................................ 458
NRC Modules Rule............................................................................................................ 458
Powerdown Time Rule ...................................................................................................... 459
Chassis Modules Rule....................................................................................................... 459
RM Serial Number Rule..................................................................................................... 460
Module Insertion................................................................................................................ 460
Module Removal................................................................................................................ 461
Autoqual. Trigger ............................................................................................................... 461
Qualification Attempted ..................................................................................................... 462
Qualification Complete ...................................................................................................... 462
Qualification Abort ............................................................................................................. 463
Contents
xl Experion PKS

Troubleshooting and Notifications Reference Release 100

Honeywell 1/03
Switchover Attempted........................................................................................................ 463
Switchover Complete......................................................................................................... 464
Autoqual. State Change..................................................................................................... 465
Ini. Qual. Cmd. Accepted................................................................................................... 466
Ini. Qual. Cmd. Rejected.................................................................................................... 466
Ini. Switchover Cmd Accepted........................................................................................... 466
Ini. Switchover Cmd Rejected............................................................................................ 467
Become Primary Cmd Accepted........................................................................................ 467
Become Primary Cmd Rejected ........................................................................................ 467
Disq. Secondary Cmd Accepted........................................................................................ 468
Disq. Secondary Cmd Rejected......................................................................................... 468
Enter Standby Cmd Accepted ........................................................................................... 468
Enter Standby Cmd Rejected ............................................................................................ 469
Swap Control Cmd Accepted............................................................................................. 469
Swap Control Cmd Rejected ............................................................................................. 469
Swap To Standby Cmd Accepted...................................................................................... 470
Swap To Standby Cmd Rejected....................................................................................... 470
Firmware Upgrade............................................................................................................. 470
Partner Chassis Connected............................................................................................... 471
Partner Chassis Disconnected .......................................................................................... 471
User Initiated Time Change............................................................................................... 471
SYS_FAIL_L Active........................................................................................................... 472
SYS_FAIL_L Inactive......................................................................................................... 472
Scream Detected............................................................................................................... 472
Backup Communication Data Errors.................................................................................. 473
Task Failed It's Status Check ............................................................................................ 473
Powerup Startup Time Changed........................................................................................ 474
WCT set to default ............................................................................................................. 474
WCT set to last event timestamp....................................................................................... 475
WCT time change ( > 1 second) ........................................................................................ 475
Rule Failed ........................................................................................................................ 475
Rule Interrupted by Ext. Event ........................................................................................... 476
Module Rejected a State Change...................................................................................... 476
Module Rejected a Sw. Phase........................................................................................... 477
RM Serial Numbers are the same...................................................................................... 477
RM application fw has changed......................................................................................... 477
DEBUG:: Jabba State Change .......................................................................................... 478
A partner RM has been connected.................................................................................... 478
The partner RM has been disconn..................................................................................... 478
The partner RM screamed................................................................................................. 479
The Health LED maybe incorrect....................................................................................... 479
Closed Prim. Connection at Sw. ........................................................................................ 480
Closed Sec. Connection at Sw. ......................................................................................... 480
Opened Prim. Connection at Sw........................................................................................ 481
Closed Sec. Connection at Disq. ....................................................................................... 481
Module Rejected Qualification........................................................................................... 482
Module State Change Response Bad................................................................................ 482
Module Qual Response Bad.............................................................................................. 482
Module Switchover Response Bad.................................................................................... 483
Contents
Release 100 Experion PKS

Troubleshooting and Notifications Reference xli

1/03 Honeywell
The State Change Timed Out............................................................................................ 483
Executing Prim. capability check ....................................................................................... 484
Pri. capability check failed ................................................................................................. 484
Pri. capability check successful ......................................................................................... 485
Changed vendor ID ........................................................................................................... 485
Changed serial number ..................................................................................................... 486
Test Sequence Numbers .................................................................... 487
CPM..........................................................................................................................487
Table of CPM Test Sequence Numbers............................................................................ 487
RM............................................................................................................................493
Corrective Actions ............................................................................................................. 493
Test Sequence Numbers................................................................................................... 493
SIM...........................................................................................................................500
Table of SIM Test Sequence Numbers.............................................................................. 500
Corrective Actions............................................................................... 511
General .....................................................................................................................511
GEN_CA01........................................................................................................................ 511
GEN_CA02........................................................................................................................ 511
BEM..........................................................................................................................512
BEM_CA01........................................................................................................................ 512
BEM_CA02........................................................................................................................ 512
CNI ...........................................................................................................................513
CNI_CA01 ......................................................................................................................... 513
CNI_CA02 ......................................................................................................................... 514
CPM..........................................................................................................................515
CPM_CA01........................................................................................................................ 515
CPM_CA02........................................................................................................................ 515
CPM_CA03........................................................................................................................ 515
CPM_CA04........................................................................................................................ 516
CPM_CA05........................................................................................................................ 516
CPM_CA06........................................................................................................................ 517
CPM_CA07........................................................................................................................ 517
CPM_CA08........................................................................................................................ 518
CPM_CA09........................................................................................................................ 518
CPM_CA10........................................................................................................................ 518
CPM_CA11........................................................................................................................ 518
CPM_CA12........................................................................................................................ 518
CPM_CA13........................................................................................................................ 519
CPM_CA14........................................................................................................................ 519
CPM_CA15........................................................................................................................ 520
Contents
xlii Experion PKS

Troubleshooting and Notifications Reference Release 100

Honeywell 1/03
CPM_CA16........................................................................................................................ 520
CPM_CA17........................................................................................................................ 520
CPM_CA18........................................................................................................................ 521
CPM_CA19........................................................................................................................ 521
CPM_CA20........................................................................................................................ 521
I/O Modules.............................................................................................................. 522
IO_CA01............................................................................................................................ 522
IO_CA02............................................................................................................................ 522
IO_CA03............................................................................................................................ 522
Network.................................................................................................................... 523
NET_CA01 ........................................................................................................................ 523
NET_CA02 ........................................................................................................................ 523
NET_CA03 ........................................................................................................................ 523
NET_CA04 ........................................................................................................................ 523
NET_CA05 ........................................................................................................................ 523
NET_CA06 ........................................................................................................................ 523
Rack and Supply...................................................................................................... 524
CH_CA01 .......................................................................................................................... 524
CH_CA02 .......................................................................................................................... 525
RM............................................................................................................................ 526
RM_CA01.......................................................................................................................... 526
RM_CA02.......................................................................................................................... 527
RM_CA03.......................................................................................................................... 528
Network Configurations ....................................................................... 529
Overview.................................................................................................................. 529
Addressing......................................................................................................................... 529
Complying with minimum redundant controller system requirements ..................... 531
Rules for Conjoined Networks ........................................................................................... 531
Rules for Independent Networks ....................................................................................... 533
Invalid Configuration ................................................................................................ 535
Example............................................................................................................................. 535
Checklists................................................................................................................. 536
Guidelines for assigning MAC ID/ControlNet addresses ................................................... 536
Confirming redundant controller system requirements ...................................................... 537
RM (Workstation) Displays.................................................................. 539
Introduction .............................................................................................................. 539
Overview............................................................................................................................ 539
Redundancy Terminology........................................................................................ 540
Contents
Release 100 Experion PKS

Troubleshooting and Notifications Reference xliii

1/03 Honeywell
Definitions.......................................................................................................................... 540
Accessing RM Displays............................................................................................541
Control Builder RM Displays.............................................................................................. 541
Station RM Displays .......................................................................................................... 541
Summary (CB) or Main (Stn) Panes ........................................................................542
Purpose............................................................................................................................. 542
Diagnostic Features........................................................................................................... 542
RM Profiles (CB and Stn) Panes..............................................................................543
Purpose............................................................................................................................. 543
Diagnostic Features........................................................................................................... 543
Configuration (CB and Stn) Panes...........................................................................545
Purpose............................................................................................................................. 545
Diagnostic Features........................................................................................................... 545
Synchronization (CB) and Synch (Stn) Panes .........................................................546
Purpose............................................................................................................................. 546
Diagnostic Features........................................................................................................... 546
Chassis Profiles (CB and Stn) Panes ......................................................................548
Purpose............................................................................................................................. 548
Diagnostic Features........................................................................................................... 548
Display (CB) Pane....................................................................................................549
Purpose............................................................................................................................. 549
Server Parameters (CB) Pane .................................................................................549
Purpose............................................................................................................................. 549
Tools and Utilities................................................................................ 551
CPM Tools................................................................................................................551
Introduction........................................................................................................................ 551
d - Display Module State ................................................................................................... 552
v - Display Module Version................................................................................................ 552
b - Display Module Startup Information ............................................................................. 553
f - Display SIM FTA Information......................................................................................... 554
r - Recover Failed Module ................................................................................................. 554
s - Start Module ................................................................................................................. 555
c - Module Crash Analysis................................................................................................. 556
l - Load Module Program Image ........................................................................................ 557
p - Select New Module Path.............................................................................................. 558
t - Force Shutdown Of Module........................................................................................... 559
x - Exit Program................................................................................................................. 559
Using DBADMIN.............................................................................................560
Introduction ................................................................................................................. 560
Contents
xliv Experion PKS

Troubleshooting and Notifications Reference Release 100

Honeywell 1/03
Description................................................................................................................... 561
Some Terms ............................................................................................................... 562
Installation.................................................................................................................... 562
Startup........................................................................................................................... 563
Menu or tree pane functions.............................................................................................. 566
Selecting a Remote Server Node ...................................................................................... 576
Viewing Server information................................................................................................ 578
Changing lock display filter ................................................................................................ 580
Clearing current locks........................................................................................................ 582
Making a Backup database ............................................................................................... 584
Restoring a backup database............................................................................................ 587
Restoring clean database................................................................................................ 589
Detaching database........................................................................................................... 591
Expanding database.......................................................................................................... 593
Recovering Primary database ........................................................................................... 594
Recovering Secondary database....................................................................................... 597
Enabling replication ........................................................................................................... 600
Disabling replication........................................................................................................... 602
I/O Maintenance Tool............................................................................................... 603
Overview............................................................................................................................ 603
Navigator Tab.................................................................................................................... 603
Calibration Tab .................................................................................................................. 611
Analog Input (Rack I/O) Module Calibration ...................................................................... 612
Analog Input (Rack I/O) Calibration Value Table............................................................... 613
Analog Output (Rack I/O) Module Calibration.................................................................... 614
Analog Output (Rack I/O) Calibration Value Table ............................................................ 615
Current Input (Rail I/O) Module Calibration........................................................................ 615
Current Output (Rail I/O) Module Calibration..................................................................... 617
Temperature Input (Rail I/O) Module Calibration #1.......................................................... 619
Temperature Input (Rail I/O) Calibration #1 Value Tables................................................. 621
Temperature Input (Rail I/O) Module Calibration #2.......................................................... 622
RTD Input (Rail I/O) Module Calibration ............................................................................ 623
RTD Input (Rail I/O) Calibration Value Table..................................................................... 624
Utilities Tab........................................................................................................................ 625
NetworkTools ........................................................................................................... 626
Overview............................................................................................................................ 626
Cautions ............................................................................................................................ 626
Command Line options...................................................................................................... 627
Launching NetworkTools ................................................................................................... 628
Display Regions (panes).................................................................................................... 631
Using the Detail Pane........................................................................................................ 631
Device Identity Dialog Box................................................................................................. 632
CNI ControlNet Stats Dialog Box....................................................................................... 632
ENET TCP/IP Configuration .............................................................................................. 632
Reset Error Counter Dialog Box ........................................................................................ 633
Status Bar.......................................................................................................................... 633
Contents
Release 100 Experion PKS

Troubleshooting and Notifications Reference xlv

1/03 Honeywell
ControlNet Parameters...................................................................................................... 634
ControlNet Unique ID ........................................................................................................ 635
Viewing SIM statistics........................................................................................................ 636
Getting RM Events ............................................................................................................ 636
Getting CPM Breadcrumbs................................................................................................ 637
Firmware Upgrades........................................................................................................... 637
ENET Browser Information.......................................................................................639
Main Screen ...................................................................................................................... 639
Main Screen - Module Information..................................................................................... 640
Main Screen - TCP/IP Configuration ................................................................................. 641
TCP/IP Configuration - IP Address.................................................................................... 641
TCP/IP Configuration - Subnet Mask................................................................................. 642
TCP/IP Configuration - Gateway Mask.............................................................................. 643
TCP/IP Configuration - Name Server and Secondary Name Server ................................. 643
TCP/IP Configuration - BOOTP......................................................................................... 644
Main Screen - Diagnostic Information................................................................................ 644
Diagnostic Information - Network Statistics ....................................................................... 645
Network Statistics - Ethernet Statistics.............................................................................. 645
Network Statistics - ICMP Statistics................................................................................... 646
Network Statistics - IGMP Statistics .................................................................................. 646
Network Statistics - IP Statistics ........................................................................................ 647
Network Statistics - UDP Statistics.................................................................................... 647
Network Statistics - TCP Statistics .................................................................................... 648
Network Statistics - TCP Extended Statistics .................................................................... 648
Network Statistics - Network Memory Statistics................................................................. 649
Network Statistics - Mbuf Statistics.................................................................................... 649
Diagnostic Information - Miscellaneous............................................................................. 650
Miscellaneous - Crash Display .......................................................................................... 650
Miscellaneous - General Memory Statistics....................................................................... 650
Miscellaneous - TGFT Task Statistics ............................................................................... 651
TGFT Task Statistics - CIP (TCP/IP ) Statistics................................................................. 651
TGFT Task Statistics - CIP (IP) Statistics.......................................................................... 652
TGFT Task Statistics - Encapsulation Protocol Stats ........................................................ 652
TGFT Task Statistics - TGFT (CIP) Statistics.................................................................... 653
Main Screen - Chassis Who.............................................................................................. 653
Effective Trouble Reporting................................................................. 655
What Makes A PAR Effective...................................................................................655
PM I/O Component Description .......................................................... 657
Introduction...............................................................................................................657
Component part numbers.................................................................................................. 657
Power System Controls............................................................................................658
IOP Card Power Interrupt Switches................................................................................... 658
Contents
xlvi Experion PKS

Troubleshooting and Notifications Reference Release 100

Honeywell 1/03
PM I/O Subsystem Overview................................................................................... 660
Major assemblies............................................................................................................... 660
Card file types.................................................................................................................... 662
Total number of card files .................................................................................................. 662
Remote card file installation............................................................................................... 662
Total number of IOPs......................................................................................................... 662
15-Slot IOP card file........................................................................................................... 663
Types of Input/Output Processors (IOPs) .......................................................................... 664
Redundant IOPs ................................................................................................................ 664
Redundant AO IOPs.......................................................................................................... 665
Low Level Multiplexer IOP (LLMux) ................................................................................... 666
Field Termination Assemblies for IOPs ................................................................... 668
Two types of FTAs............................................................................................................. 668
Power Adapter................................................................................................................... 668
Remote Hardened Low Level Multiplexer IOP (RHMUX) .................................................. 669
RHMUX Thermocouple FTA.............................................................................................. 671
FTA and Power Adapter installation .................................................................................. 671
I/O Link Extender (Fiber Optic Link) ........................................................................ 672
Features and guidelines .................................................................................................... 672
Front panel indicators ........................................................................................................ 673
Status indicator operation.................................................................................................. 673
Field Termination Assemblies (FTAs)...................................................................... 674
FTAs types ........................................................................................................................ 674
Detailed descriptions ......................................................................................................... 674
Galvanically isolated FTAs ................................................................................................ 676
Three physical sizes .......................................................................................................... 676
FTA Mounting.................................................................................................................... 678
Vertical orientation............................................................................................................. 678
FTA Mounting Channels .......................................................................................... 679
Vertical FTA Mounting Channels ....................................................................................... 679
Horizontal FTA Mounting Channels................................................................................... 679
Typical cabinet installation................................................................................................. 680
FTA Wiring Connection Types................................................................................. 682
Compression or screw terminals available ........................................................................ 682
FTA compression-type terminal connector ........................................................................ 683
FTA fixed screw terminal connector................................................................................... 684
FTA removable screw-type connector ............................................................................... 685
Galvanic Isolation Module connectors ............................................................................... 685
Crimp pin-type terminal connector ..................................................................................... 686
Compression-type terminal connector ............................................................................... 687
Power Systems........................................................................................................ 688
Standard Power System.................................................................................................... 688
48 volt battery backup time duration.................................................................................. 688
CMOS backup time duration.............................................................................................. 689
Contents
Release 100 Experion PKS

Troubleshooting and Notifications Reference xlvii

1/03 Honeywell
Standard Power System.................................................................................................... 689
AC Only Power System..................................................................................................... 690
Power Distribution ....................................................................................................692
AC Only Power System ac power...................................................................................... 692
Battery Backup Module ..................................................................................................... 693
48 Volt Battery switch........................................................................................................ 693
No battery backup (Standard Power System)................................................................... 693
CMOS Battery Backup ...................................................................................................... 694
AC Only Power System..................................................................................................... 695
24 Vdc Power Distribution........................................................................................696
Dual power distribution cables........................................................................................... 696
Standard Power System.................................................................................................... 696
AC Only Power System..................................................................................................... 696
Typical cabinet power distribution...................................................................................... 696
Cabinet Fan Assembly .............................................................................................698
Optional Cabinet Fan assembly......................................................................................... 698
LLAI Line Frequency Clock Voltage.........................................................................699
Standard Power System.................................................................................................... 699
AC Only Power System..................................................................................................... 699
24 Vdc Fuse Protection............................................................................................700
Card file fusing................................................................................................................... 700
Fuse removal..................................................................................................................... 700
Fuse extraction.................................................................................................................. 700
Fuse insertion.................................................................................................................... 701
Left 7-Slot Card File Fuse Protection................................................................................. 701
Left 7-Slot IOP card file 24 Vdc distribution....................................................................... 702
Left 7-Slot card file backpanel fuse locations .................................................................... 703
Right 7-Slot Card File Backpanel Fuse Protection............................................................. 704
Right 7-Slot IOP card file 24 Vdc distribution..................................................................... 705
Right 7-Slot card file backpanel fuse locations .................................................................. 706
15-Slot Card File Backpanel Fuse Protection.................................................................... 706
15-Slot IOP card file 24 Vdc distribution............................................................................ 707
15 Slot card file backpanel fuse locations.......................................................................... 709
FTA fuse protection ........................................................................................................... 710
Cabinet Fan assembly fuse protection .............................................................................. 710
IOP Card File Power Cabling ...................................................................................711
Power Distribution assemblies........................................................................................... 711
Power System power connectors ...................................................................................... 711
Power cables for IOP......................................................................................................... 711
Fifteen-Slot IOP Card File Backpanel Connections........................................................... 713
Power cables for power distribution assemblies................................................................ 713
Power distribution examples.............................................................................................. 713
Power distribution methods ............................................................................................... 714
15-Slot Card File with Power Distribution Assemblies....................................................... 715
Contents
xlviii Experion PKS

Troubleshooting and Notifications Reference Release 100

Honeywell 1/03
Two 15-Slot Card Files with Power Distribution Assemblies.............................................. 716
Three 15-Slot Card Files.................................................................................................... 717
Three 15-Slot Card Files with Power Distribution Assemblies........................................... 718
Power Distribution Assemblies for redundant cabling........................................................ 720
Installing I/O Interface cable .................................................................................... 722
Cabling Requirements ....................................................................................................... 722
Power surge protection for the I/O link interface................................................................ 723
New and upgraded subsystems only................................................................................. 723
I/O Link interface cables in adjacent cabinets.................................................................... 723
I/O Link interface cable installation.................................................................................... 724
Typical I/O Link and power cable connection .................................................................... 724
I/O Link Interface cable shield grounding........................................................................... 726
IOP to FTA Cabling.................................................................................................. 727
Standard FTAs................................................................................................................... 727
Galvanically Isolated FTAs ................................................................................................ 727
External cabinet installation............................................................................................... 727
Typical cable routing.......................................................................................................... 728
Power Adapter Cabling............................................................................................ 729
LLMux interconnections..................................................................................................... 729
I/O Link Address Pinning ......................................................................................... 731
IOP card file addressing .................................................................................................... 731
One method only ............................................................................................................... 733
Jumper method example ................................................................................................... 733
Zero-ohm resistor jumper pinning example ....................................................................... 734
Removal and Replacement of PM I/O Components............................ 737
ESD Guidelines........................................................................................................ 737
Static discharge effects...................................................................................................... 737
Building a static discharge probe....................................................................................... 737
ESD prevention rules......................................................................................................... 738
IOP Cards ................................................................................................................ 739
Replacing IOP cards.......................................................................................................... 739
Standby Manual Devices ......................................................................................... 740
About devices .................................................................................................................... 740
No external power source option....................................................................................... 740
Standby Manual device connections ................................................................................. 740
Device interchangeability................................................................................................... 742
DIN to phone connector adaptor cable.............................................................................. 742
Board revision level ........................................................................................................... 742
AO Standby Manual Device Operation.................................................................... 743
Two models ....................................................................................................................... 743
Original Analog Output Standby Manual device ................................................................ 743
Contents
Release 100 Experion PKS

Troubleshooting and Notifications Reference xlix

1/03 Honeywell
Control of FTA outputs ...................................................................................................... 744
FTA connection ................................................................................................................. 744
Standby Manual device control procedure ........................................................................ 745
Normal IOP control procedure........................................................................................... 745
Compact Analog Output Standby Manual device.............................................................. 746
Compact device features................................................................................................... 747
Compact ASOM device control procedure ........................................................................ 748
Return to Normal IOP control procedure ........................................................................... 749
DO Standby Manual Device Operation....................................................................750
About the DOSM device.................................................................................................... 750
Secondary function............................................................................................................ 750
Mounting locations............................................................................................................. 750
DOSM connection ............................................................................................................. 751
Output control switches disablement ................................................................................. 751
Switch activation................................................................................................................ 752
DOSM to normal IOP control procedure............................................................................ 754
IOP Card Case Replacement...................................................................................755
Handling and installing IOP components........................................................................... 755
Replacing plastic case....................................................................................................... 755
IOP to FTA Cable Replacement...............................................................................758
Nonredundant IOP cable replacement .............................................................................. 758
Redundant IOP cable replacement.................................................................................... 758
FTA Replacement.............................................................................................................. 759
FTA Module and Relay Replacement ......................................................................760
Replacing FTA Module or Relay........................................................................................ 760
LLAI Module replacement.................................................................................................. 760
AO redundancy switching module replacement................................................................. 760
Galvanic isolation module replacement ............................................................................. 761
Card File Replacement.............................................................................................762
Card File Replacement.............................................................................................762
Replacing card file............................................................................................................. 762
Power System ..........................................................................................................763
About the power system.................................................................................................... 763
CMOS Battery Replacement ....................................................................................764
NiCad batteries.................................................................................................................. 764
48 V Backup Battery Replacement ..........................................................................765
Battery operational and service life.................................................................................... 765
Battery performance.......................................................................................................... 765
48 V Battery Pack end-of-life............................................................................................. 765
48 V Battery Pack service life............................................................................................ 767
End of Battery Pack life check........................................................................................... 768
Battery pack removal ......................................................................................................... 769
Contents
l Experion PKS

Troubleshooting and Notifications Reference Release 100

Honeywell 1/03
Battery Pack installation .................................................................................................... 770
Power Supply Module Replacement........................................................................ 771
Replacing power supply module........................................................................................ 771
CMOS Backup Assembly Replacement .................................................................. 773
About CMOS Backup Assembly ........................................................................................ 773
Replacing CMOS Backup Assembly.................................................................................. 774
Cabinet..................................................................................................................... 775
Removing Markhon cabinet side panels............................................................................ 775
Removing Rittal cabinet side panels.................................................................................. 775
I/O Link Extender Optical Coupler Module Replacement ........................................ 776
Replacement procedures................................................................................................... 776
Replacing coupler in Non-CE Compliant card file.............................................................. 776
IOP Calibration Procedures................................................................. 779
Overview.................................................................................................................. 779
Introduction........................................................................................................................ 779
No manual adjustments..................................................................................................... 779
LLAI, HLAI, and AO IOP Calibration........................................................................ 780
Introduction to common calibration procedures................................................................. 780
IOP or FTA substitution ..................................................................................................... 780
Precision Test Equipment Requirements........................................................................... 780
LLAI IOP Calibration Procedure .............................................................................. 781
Seven ranges .................................................................................................................... 781
Calibration affects eight slots............................................................................................. 781
Range type selection......................................................................................................... 781
Select RTD or TC calibration............................................................................................. 782
Procedure.......................................................................................................................... 782
Nonredundant HLAI IOP Calibration Procedure...................................................... 791
About HALI procedure ....................................................................................................... 791
Galvanic isolation FTA connection points.......................................................................... 791
Calibration terminals.......................................................................................................... 792
HLAI calibration procedure ................................................................................................ 792
Redundant HLAI IOP Calibration Procedure ........................................................... 796
Simultaneous HLAI IOP calibration.................................................................................... 796
Nonredundant AO IOP Calibration Procedure......................................................... 797
About AO procedure.......................................................................................................... 797
AO calibration procedure................................................................................................... 797
Redundant AO IOP Calibration Procedure.............................................................. 801
Simultaneous AO IOP calibration ...................................................................................... 801
Contents
Release 100 Experion PKS

Troubleshooting and Notifications Reference li

1/03 Honeywell
LLMux IOP Calibration Procedure............................................................................802
About LLMUX calibration................................................................................................... 802
LLMUX calibration procedure............................................................................................ 802
RHMUX IOP Calibration Procedure .........................................................................804
About RHMUX calibration.................................................................................................. 804
RHMUX calibration method............................................................................................... 804
Field calibration overview.................................................................................................. 805
RHMUX calibration procedure........................................................................................... 805
RHMUX calibration failure ................................................................................................. 806
Thermocouple Input Accuracy Verification...............................................................807
About thermocouple verification ........................................................................................ 807
Thermocouple verification procedure ................................................................................ 807
Periodic IOP Redundancy Tests......................................................... 809
Overview...................................................................................................................809
About redundancy tests..................................................................................................... 809
Monitor displays................................................................................................................. 809
Testing IOP Redundancy .........................................................................................811
IOP redundancy terminology ............................................................................................. 811
Test procedure .................................................................................................................. 812
Redundant 8-Channel Analog Output IOPs .............................................................813
About redundancy bias...................................................................................................... 813
Hardware identification...................................................................................................... 813
Status check...................................................................................................................... 813
Power Cable Redundancy........................................................................................816
Testing power cable redundancy....................................................................................... 816
Power Supply Module Redundancy .........................................................................817
About power system redundancy ...................................................................................... 817
Testing power system redundancy procedure................................................................... 817
System Performance and Tuning Considerations............................... 819
System Performance Features.................................................................................819
Operating System Tuning.........................................................................................821
Service/Kernel Tuning ....................................................................................................... 821
Disk Management.............................................................................................................. 826
Memory and Swapfile........................................................................................................ 831
Network Optimization ........................................................................................................ 835
Video Settings ................................................................................................................... 838
System Usage ..........................................................................................................839
Contents
lii Experion PKS

Troubleshooting and Notifications Reference Release 100

Honeywell 1/03
Topology related settings......................................................................................... 840
Physical location of the Systems ....................................................................................... 840
Physical location of the Components................................................................................. 840
Service Integration............................................................................................................. 840
Network Integration............................................................................................................ 840
System Monitoring/Assessing the need for hardware upgrades ............................. 841
Opening Performance Monitor........................................................................................... 843
Interpreting the Performance Counter Values: .................................................................. 845
Spare Parts ......................................................................................... 849
CNI Parts.................................................................................................................. 849
General Notes ................................................................................................................... 849
TC-CCN011....................................................................................................................... 849
TC-CCR011....................................................................................................................... 850
TC-CCN012....................................................................................................................... 850
TC-CCR012....................................................................................................................... 851
TC-CCN013....................................................................................................................... 851
TC-CCR013....................................................................................................................... 852
Periodic Maintenance Parts for PM I/O ................................................................... 853
Periodic maintenance parts list .......................................................................................... 853
Batteries ............................................................................................................................ 853
Fuses................................................................................................................................. 853
Filters................................................................................................................................. 855
Optimum Replaceable Unit (ORU) Parts for PM I/O ............................................... 856
ORU parts List ................................................................................................................... 856
Cables ............................................................................................................................... 856
Power system components - non-conformally coated ....................................................... 862
Power system components - conformally coated .............................................................. 863
IOP cards - non-conformally coated .................................................................................. 864
IOP cards - conformally coated ......................................................................................... 865
I/O LINK Extender components - non-conformally coated................................................. 866
I/O LINK Extender components - conformally coated........................................................ 867
Standard FTA components - non-conformally coated........................................................ 867
Standard FTA components - conformally coated............................................................... 874
Galvanically Isolated FTA components - non-conformally coated ..................................... 881
Galvanically Isolated FTA components - conformally coated ............................................ 884
Miscellaneous components - non-conformally coated....................................................... 887
Miscellaneous components - conformally coated .............................................................. 890



Release 100 Experion PKS

Troubleshooting and Notifications Reference liii

1/03 Honeywell
Figures
Part I PlantScape Troubleshooting Guide
Figure 1 MMC hosts DBADMIN Tool with common Windows type interface. ............561
Figure 2 Vertical FTA Mounting Channel Installation Single Access Cabinet ..........680
Figure 3 Typical Vertical FTA Mounting Channel Layout ............................................681
Figure 4 AC Only Power System.................................................................................691
Figure 5 Power Distribution..........................................................................................692
Figure 6 Standard Power System Backpanel ..............................................................694
Figure 7 CMOS Battery Backup Assembly (Standard Power System) .......................695
Figure 8 Typical Cabinet 24 Vdc Power Distribution ...................................................697
Figure 9 Power Cable with I/O Link Protectors............................................................712
Figure 10 Fifteen-Slot IOP Card File Backpanel Connections ....................................713
Figure 11 15-Slot Card File with Power Distribution Assemblies ................................715
Figure 12 Two 15-Slot Card Files with Power Distribution Assemblies.......................716
Figure 13 Three 15-Slot Card Files..............................................................................717
Figure 14 Three 15-Slot Card Files with Power Distribution Assemblies ....................719
Figure 15 Power Distribution Assemblies for redundant cabling.................................721
Figure 16 Typical Cabinet I/O Link Interface Cable Connections................................725
Figure 17 IOP to FTA Cabinet Cabling........................................................................728
Figure 18 Power Adapter Interconnections LLMux Application................................730

Figures
liv Experion PKS

Troubleshooting and Notifications Reference Release 100

Honeywell 1/03

Part I
Experion PKS Troubleshooting
Guide
Release 100 Experion PKS Troubleshooting and Notifications Reference 1
1/03 Honeywell Part I
Isolating Faults
Introduction
This document focuses on the process of Hybrid Controller Fault Isolation.
To support this process, this section includes descriptions of diagnostic tools and
definitions of various fault indicators. It then assists the user with fault isolation through
a series of questions and hyperlinks that eventually take the user to fault definitions and
corresponding recovery recommendations.
The reader may use this information to either address a specific fault or to better
understand Hybrid Controller diagnostic tools and fault symptoms.
This manual focuses on the Hybrid Controller, which includes any component within a
Controller or remote I/O chassis, as well as the interconnecting networks and I/O devices.
Isolating Faults
To Learn More
2 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
To Learn More

About Then go to
Why my system faulted Fault Isolation
Module Fault
Fault Indicators Front Panel Indicators:
BEM
CNI
CPM
Input Modules
Output Modules
IOLIM
Serial Interface Modules
RM
Fault Codes
CNI Fault Codes
CPM Fault Codes
Exchange Block ERRCODE Fault Codes
I/O Fault Codes
PM IOP Fault Codes
RM Fault Codes
STI and STI_MV IOP Maintenace
Experion PKS Notifications
CPM FB Generated Notifications
NDM Generated Notifications
RM Events
Overview
Isolating Faults
To Learn More
Release 100 Experion PKS Troubleshooting and Notifications Reference 3
1/03 Honeywell Part I
About Then go to
CNI Generated RM Events
CPM Generated RM Events
RM Generated Events
Test Sequence Numbers
CPM
RM
SIM
Corrective Actions General
BEM
CNI
CPM
I/O Modules
PM I/O Processors
Network
Rack and Supply
RM
Diagnostic Tools &
Utilities
CPM Tools
Using DBADMIN
I/O Maintenance Tool
NetworkTools
ENET Browser Information
RM (Workstation) Displays
Introduction
Redundancy Terminology
Accessing RM Displays
Isolating Faults
To Learn More
4 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
About Then go to
Summary (CB) or Main (Stn) Panes
RM Profiles (CB and Stn) Panes
Configuration (CB and Stn) Panes
Synchronization (CB) and Synch (Stn) Panes
Chassis Profiles (CB and Stn) Panes
Display (CB) Pane
Server Parameters (CB) Pane
Reporting a problem Effective Trouble Reporting
PM I/O Equipment
Overview
PM I/O Subsystem Overview
Cabinet Fan Assembly
Field Termination Assemblies (FTAs)
Field Termination Assemblies for IOPs
FTA Mounting Channels
FTA Wiring Comnection Types
I/O Link Extender (Fiber Optic Link)
I/O Link Interface Address Pinning
I/O Link Interface Cabling
IOP to FTA Cabling
IOP/FTA 24 Vdc Fuse Protection
IOP Card File Power Cabling
LLAI Line Frequency Clock Voltage
Power Adapter Cabling
Power Distribution
Power Systems
Power System Controls
Isolating Faults
To Learn More
Release 100 Experion PKS Troubleshooting and Notifications Reference 5
1/03 Honeywell Part I
About Then go to
Maintenance
Procedures
Periodic IOP Redundancy Tests
Testing IOP Redundancy
Redundant 8-Channel Analog Output IOPs
Power Cable Redundancy
Power Supply Module Redundancy
Removal/Replacement
Procedures
Removal and Replacement of PM I/O
Components
ESD Guidelines
IOP Cards
Standby Manual Devices
AO Standby Manual Device Operation
DO Standby Manual Device Operation
IOP Card Case Replacement
IOP to FTA Cable Replacement
FTA Module and Relay Replacement
Card File Replacement
IOP/FTA 24 Vdc Fuse Replacement
Power System
CMOS Battery Replacement
48 V Backup Battery Replacement
Power Supply Module Replacement
CMOS Backup Assembly Replacement
Cabinet
I/O Link Extender Optical Coupler Module
Replacement
Spare Parts Spare Parts
Isolating Faults
To Learn More
6 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
About Then go to
CNI Parts

Isolating Faults
Fault Isolation
Release 100 Experion PKS Troubleshooting and Notifications Reference 7
1/03 Honeywell Part I
Fault Isolation
Start

If Then go to
A specific module has faulted, Module Fault

I want to know more about a diagnostic
tool or fault indicator,
To Learn More


Module Fault

Go to the appropriate module Fault Isolation
BEM Fault Isolation
CNI Fault Isolation
CPM Fault Isolation
RM Fault Isolation
PM IOP Fault Isolation
STI and STI_MV IOP Fault Isolation

Isolating Faults
BEM Fault Isolation
8 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03

BEM Fault Isolation
Fault Isolation Table

If then
the BEM OK LED is off, Ensure chassis power is applied and/or BEM is
fully inserted into the chassis.
If the BEM OK LED remains off, then go to BEM
Corrective Action BEM_CA01.
the BEM OK LED is solid red, Go to BEM Corrective Action BEM_CA02.
If the BEM OK LED is solid green, No action is required.
The BEM is operating normally.

Background
The BEM is a separate, singlewide module that plugs into the Controller chassis. It
incorporates the standard ICP plastic module cover and front door. Connection to the
chassis backplane is though the standard ICP connector.
The Battery Extension Module (BEM) provides battery backup power for volatile
memory ICs contained within chassis modules, such as the Control Processor Module
(CPM). The battery backup is useful for maintaining memory contents, such as
configuration databases, during temporary power outages and weekend shutdowns.
Three (3) series-connected, sub-C size, nickel-cadmium cells constitute the battery pack.
Its sourcing capacity is rated at 1200mAh. In terms of what is required by the CPM, this
means it can provide 10 milliamps of DC current at 3.6 volts for a period of 120 hours on
a full charge. This figure represents the worst-case scenario for CPM operation. The
CPM typically draws 5 milliamps at reference temperature conditions and with nominal
components.
There is self-test circuitry on the BEM that periodically tests for battery pack presence
and the battery-pack under load. These tests are performed only when chassis power is
present.
Isolating Faults
BEM Fault Isolation
Release 100 Experion PKS Troubleshooting and Notifications Reference 9
1/03 Honeywell Part I
A front panel LED shows the state (health) of the battery system. An integral status
contact supports a user supplied annunciatior circuit for external/remote alarming in the
event of battery deterioration or failure. The normally-open relay contact remains closed
(and the normally-closed contact remains open) when the BEM is able to provide 3.0 to
3.6 Vdc battery backup power. The normally-open relay contact opens (and the
normally-closed contact closes) when the BEM is not able to provide at least 3.0 Vdc
battery backup power.
Out-Of-The-Box Assembly Required
The BEM module is shipped from the factory without the battery pack installed. Please
refer to the Control Hardware Installation Guide for battery pack installation details.
Out-Of-The-Box Capacity
Since Ni-Cd batteries have a high self-discharge rate, we recommend that users let the
BEM module installed in a powered chassis for 24 hours prior to use. Technically, it
takes 30 to 32 hours to fully charge a set of completely discharged batteries. However,
from a practical standpoint, completely discharged batteries can never be charged. What
typically happens is that a user receives a BEM module with a battery pack charged from
60% to 80% capacity available.
Isolating Faults
CNI Fault Isolation
10 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03

CNI Fault Isolation
CNI Not Compatible

Symptoms: On the RM Detail display (either Summary pane or Synchronization
pane) the large list shows the Compatibility (4th column) for the CNI
as INCOMPATIBLE?
When I look at the 4 character display of the CNI I see "!CPT".
Cause: CNIs are not compatible. Incompatibility may occur for several
reasons:
1) Mismatch between hardware revisions.
2) Mismatch between firmware version.
3) Mismatch between configured ControlNet parameters.
Corrective
Action:
Launch NetworkTools with the appropriate switch, select a suspect
CNI and click the toolbar button that looks like a blue wrench.
Go to the Present Keeper Tab.
You may need to reprogram you CNI's network parameters.
If that
doesn't
work:
Select the suspect CNI in NetworkTools and click on the toolbar
button that has the letters "ID".
Record the Product Type and Product Code values.
Do the same on the partner CNI. If the two do not match. Replace
the one that is not Type "c" and Code "8".

Isolating Faults
CNI Fault Isolation
Release 100 Experion PKS Troubleshooting and Notifications Reference 11
1/03 Honeywell Part I
Incorrect Keeper Values

Symptoms: My CNI show the words KPR ERR.
NetworkTools just popped up a dialog box indicating bad Network
values.
My Monitoring pane has started to show red for many items.
Cause: Bad network parameters.
Corrective
Action:
Launch NetworkTools with the appropriate switch, select a suspect
CNI and click the toolbar button that looks like a blue wrench.
Go to the Present Keeper Tab.
You may need to reprogram you CNI's network parameters.
If that
doesn't
work:
Cycle power to the CNI.

NetworkTools Related Questions

Symptoms: I have a large system and NetworkTools CNI Stats display shows
many non-concurrences.
Is there a way to diagnose ControlNet parameters?
I am planning an upgrade and know my ControlNet parameters
should change. Do I need to do this to all CNIs?
Cause: ControlNet paramters may need to change.
Corrective
Action:
Launch NetworkTools with the appropriate switch, select a suspect
CNI and click the toolbar button that looks like a blue wrench.
Go to the Present Keeper Tab.
You may need to reprogram you CNI's network parameters.
If you are creating a network with parameters other than those in the
previous discussion, you must reprogram all CNIs on that network
(and potential spares).
Isolating Faults
CNI Fault Isolation
12 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
You can diagnose the parameters by using the first toolbar button in
NetworkTools. Go the to Options tab. Check the box called Enable
ControlNet Parameter Checking. NetworkTools will perform a
diagnostic each time it is launched, if the checkbox is clicked ON or
after a change of network parameters. This check only uses the
standard Experion PKS values (it is no utility for non-standard
network parameteres).
If that
doesn't
work:
Refer to the Installation manual and the Planning manual.

General CNI Questions

Symptoms: In a pinch can I use a CCR012 in a remote I/O chassis?
In a pinch can I use a CCN01x as a buddy node in a redundant
media system?
Cause: Spares/emergencies questions.
Corrective
Action:
At this time a CCN011 cannot be used as a buddy node in a
redundant media system.
A CCR012 can be used in a remote I/O chassis.
If that
doesn't
work:
Call TAC


Isolating Faults
CPM Fault Isolation
Release 100 Experion PKS Troubleshooting and Notifications Reference 13
1/03 Honeywell Part I

CPM Fault Isolation
Flash ROM Programming Errors
Errors and faults encountered in the process of programming CPM Application and/or
Boot firmware are not addressed in this document. In general, an error programming the
Application personality shall permit repeated attempts, while an error programming the
Boot personality may require returning the module to the factory.
Fault Isolation Table

If the . . . Then See . . .
CPM is stuck displaying the same
Test Sequence Number for more than
30 seconds,
Table of CPM Test Sequence Numbers
CPM is in the Fail State, CPM Fault Codes
CPM Health LED is solid red, CPM_CA05
problem persists, CPM_CA06
CPM Battery LED is solid red, CPM_CA07
CPM is being used in a redundant
configuration and unable to
synchronize,
CPM_CA03

Isolating Faults
PM IOP Fault Isolation
14 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03

PM IOP Fault Isolation
The IOP reports device soft failures to Experion PKS Server. These soft failures are also
located on the Control Builder configuration forms under the Softfailures tab as shown in
Figure 1.



Figure 1 Softfailures Flag Tab
Isolating Faults
PM IOP Fault Isolation
Release 100 Experion PKS Troubleshooting and Notifications Reference 15
1/03 Honeywell Part I
IOP Box Soft failure error codes
The IOP Box Soft failure codes are defined in the following table. Also, the corrective
actions are identified in the table.
Table 1 IOP Box Soft Failure Error Codes

Error
Code
Description Corrective Action
00 Null Soft failure. No failure None.
01 Sample time clock overrun
greater than 2 x period.
Investigate a possible I/O Link problem. Data access to
the IOP cards may not be operating properly. Check the
High-Performance I/O Link card, the I/O Link cable, and
the IOP cards.
02 IOP task request overflow
excessive IOL activity.
Call TAC for assistance.
03 IOP executive resumed a
nonwaiting task software
bug indicated
Call TAC for assistance.
04 Diagnostics not run in at
least 5 seconds indicates a
processing overload.
Investigate control point mix/strategy for an excessive
load. Otherwise, a possible I/O Link problem exists.
Check the High-Performance I/O Link card, the I/O Link
cable, and the IOP cards.
05 Entire diagnostic cycle
overran the 2-minute
allocated time in which
diagnostics have to run to
completion.
Same as error code 04.
06 The FTA is missing, or if
LLMUX, power adapter
missing.
Install the FTA. If an FTA is present, replace the FTA or
check the FTA cable. (Note: For the LLMux or RHMUX,
this code refers to the Power Adapter assembly. RTD and
TC FTAs are diagnosed by error codes 50 and 51.)
07 EEPROM (used to hold
calibration information in
Analog Output IOPs)
checksum failure. It
usually means an Analog
Output IOP is not
calibrated properly.
Calibrate the Analog Output IOP card (refer to the IOP
Calibration Procedures section for the procedure). If the
error persists, replace the HLAI, or the AO IOP card, or
the FTA.
Isolating Faults
PM IOP Fault Isolation
16 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Error
Code
Description Corrective Action
08 EEPROM counter error.
The number of writes to
EEPROM has exceeded
the safe number (10,000).
This could indicate the IOP
has not been calibrated
because a virgin EEPROM
will fail this test.
Same as error code 07.
09 EEPROM flag error -
incomplete write or
uncalibrated IOP.
Same as error code 07.
10 No longer used. Switched
signal error possible FTA
problem
No action required.
11 ADP (Analog to Digital
Processor) private RAM
contents error LLAI only
no conversion
Replace the appropriate IOP card because the ADP has
failed.
12 ADP private RAM address
error LLAI only no
conversion
Replace the IOP card.
13 LLAI shared ROM
contents failure LLAI
only no AI conversion
Replace the IOP card.
14 LLAI shared ROM address
error LLAI only no AI
conversion
Replace the IOP card.
15 LLAI shared ROM
checksum error LLAI
only no AI conversion
Replace the IOP card.
16 ADP ROM checksum
failure LLAI only no AI
conversion
Replace the IOP card.
Isolating Faults
PM IOP Fault Isolation
Release 100 Experion PKS Troubleshooting and Notifications Reference 17
1/03 Honeywell Part I
Error
Code
Description Corrective Action
17 ADP has failed in
communications with IOLP
recoverable-
Application processor
(LLAI or STI) has a
communication failure with
the High-Performance I/O
Link card.
If the error persists, replace the IOP card.
18 ADP (LLAI only) failed on
IOP startup it will not
recover
Replace the IOP card.
19 Input module scan
overrun excessive IOL
activity to this IOP. Inputs
have been lost.
Check for a "chattering" DI point. Another possible cause
would be intermittently bad I/O link hardware.
20 Input module scan
overrun.
No longer used. No action required.
21 Not used. Not applicable.
22 DOM secondary regulator
is not working.
Replace the DO IOP card.
23 Not used. Not applicable.
24 8051stack usage is
dangerously close to its
limit.
Call TAC for assistance.
25 Spare N/A
26 Input/Output loopback
failure.
Replace the appropriate IOP card.
27 No IOLP acess to shared
RAM. Input conversion
will be prohibited.
Replace the IOP card.
28 No external AC line in the
LLAI input conversions
continue.
Check optical coupler and associated fuse on the
backpanel. Check that the primary (left side)Power
Supply Module in the Power System is installed and
functional.
Isolating Faults
PM IOP Fault Isolation
18 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Error
Code
Description Corrective Action
29 Not used. Not applicable.
30 Test voltage Reference
>5% out of range
PVAUTO to MAN. The PV
is set to NAN by the IOP.
Replace the IOP card.
31 Not used. Not applicable.
32 Zero Reference voltage
out of range. The PV is set
to NAN by the IOP.
Replace the IOP card.
33 LLAI Reference junction
value is bad.
Check that the reference junction wire or jumper (P1) is
correctly implemented on the FTA.
34 LLAI bad ADP branch
taken software bug.
Replace the LLAI IOP card for the LLAI FTA.
35 Not used. Not applicable.
36 LLMux or RHMUX: FTA #1
has a Soft failure.
LLMux or RHMUX: Check FTA 1.
SI: Correct the error condition at the device connected to
FTA 1.
37 LLMux or RHMUX: FTA #2
has a Soft failure.
LLMux or RHMUX: Check FTA 2.
SI: Correct the error condition at the device connected to
FTA 2.
38 Calibration of a module
has been aborted due to a
failure.
Check the precision voltage/resistance source for
accuracy. Also, make sure that the correct calibration
procedure is being followed
39 Calibration voltage out of
range.
Replace the HLAI.
40 EEPROM store failed
calibration data may be
lost..
If an HLAI or AO, replace the IOP. If an LLAI, replace the
affected plug-in module.
41 LLMUX FTA reference
voltage out of range
If the problem persists replace the FTA
42 Not used. Not applicable.
Isolating Faults
PM IOP Fault Isolation
Release 100 Experion PKS Troubleshooting and Notifications Reference 19
1/03 Honeywell Part I
Error
Code
Description Corrective Action
43 HLAI A/D is out of
calibration by more than
3%.
(refer to the IOP
Calibration Procedures
section).
Calibrate or replace the IOP card (refer to the IOP
Calibration Procedures section).
44 AO module failure
selection register is bad.
Replace the AO IOP card.
45 Secondary latch failure. Replace the IOP. Use a Standby Manual device if
nonredundant.
46 Output disable buffer
failure.
Replace IOP. Use Standby Manual device if
nonredundant.
47 Calibration reference
voltage out of range.
Replace the IOP or recalibrate.
48 LLMux: FTA 1 is not
calibrated.
SI: FTA 1 write buffer
overflow.
LLMux or RHMUX: Calibrate FTA 1.
SI: Reduce the number of writes to the FTA.
49 LLMux: FTA 2 is not
calibrated.
SI: FTA 2 write buffer
overflow.
LLMux or RHMUX: Calibrate FTA 2.
SI: Reduce the number of writes to the FTA.
50 FTA 1 communication
failure.
Check the connection from the Power Adapter to FTA 1. If
the FTA is missing, install the FTA. If the FTA is present,
replace the FTA.
51 FTA 2 communication
failure.
Check the connection from the Power Adapter to FTA 2. If
the FTA is missing, install the FTA. If the FTA is present,
replace the FTA.
52 FTA 1 identification failure. Verify/correct the FTA pinning.
53 FTA 2 identification failure. Verify/correct the FTA pinning.
54 FTA 1 reference voltage
failure.
Replace the FTA.
55 FTA 2 reference voltage
failure.
Replace the FTA.
Isolating Faults
PM IOP Fault Isolation
20 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Error
Code
Description Corrective Action
56 FTA 1 calibration failure. Recalibrate the FTA.
57 FTA 2 calibration failure. Recalibrate the FTA.
58 IOP lost synchronization
with its primary.
If the primary IOP is in OK, resynch with the START
command. If the primary IOP is in IDLE, resynch with the
IDLE command.
59 AO or DO write enable
protection failure.
Replace the IOP at the earliest convenience. IOP failure
can result in indeterminate outputs.
60 Multiple input failure
detected.
Replace the IOP.
61 Redundancy hardware
diagnostic failure.
If an AO, replace the FTAs plug-in module
after forcing IOP A to be the primary.
If an HLAI, replace the IOPs one at a time following
database synchronization.
62 Data bus failure.
63 IO redundancy configured
on non-supportive
hardware rev.
Replace the IOP with an IOP that supports redundancy
(proper hardware revision).
64 Hardware FIFO diagnostic
failed. PVs set BAD
replace IOP.
Replace the IOP.
65 Private RAM diagnostic
failed. PVs set BAD
replace IOP.
Replace the IOP.
66 The SOE clock failed. PVs
set BAD replace IOP.
Replace the IOP.
67 PV validation diagnostic
failed. PVs set BAD
replace IOP.
Replace the IOP.
68 SOE counter diagnostic
failed. PVs set BAD
replace IOP.
Replace the IOP.
69 Data path failure. Replace the FTA when convenient.
70 Data path failure. Replace the FTA when convenient.
Isolating Faults
PM IOP Fault Isolation
Release 100 Experion PKS Troubleshooting and Notifications Reference 21
1/03 Honeywell Part I
Error
Code
Description Corrective Action
71 State machine diagnostic
failed. PVs set BAD
replace IOP.
Recalibrate the FTA.
72 Bad personality image. - Reload personality image?
73 Bad BS and/or PS image
in Flash ROM.
-
74 Bad CRC for PS Flash
ROM image.
-
75 Bad AS image in Flash
ROM.
-
76
to
255
Not used. Not applicable.

Isolating Faults
PM IOP Fault Isolation
22 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
IOP Slot Soft failure error codes
The IOP block reports diagnostic alarms in the event of an IOP hardware failure or a
change in the IOP redundancy state. Specifically, the following diagnostic alarm codes
are presented for the IOP block and are described in the table. The recommended
corrective actions are included in the table.
Table 2 IOP Slot Soft Failure Error Codes

Error
Code
Description Corrective Action
00 No error
01
to
06
Not used. N/A
07 LLAI EEPROM checksum
error or IOP not
calibrated.
Replace the FTA plug-in module or recalibrate.
08 LLAI EEPROM counter
error too many writes or
unformatted EEPROM.
Replace the FTA plug-in module or recalibrate.
09
to
20
Not used. N/A
21 Input point failed
diagnostic.
Replace the IOP or check the FTA wiring.
22 Not used. N/A
23 Failure in output circuitry
detected by AO or DO
Check the output connection at the FTA. If it is good, try
replacing the FTA and/or the appropriate IOP card.
24
to
28
Not used. N/A
29 Bad input or bad FTA
plug-in module
Test that the slot is wired correctly. If it is, replace the
FTA plug-in module.
30 Not used. N/A
31 FTA type mismatch with
slot configuration.
Reconfigure or replace the FTA.
Isolating Faults
PM IOP Fault Isolation
Release 100 Experion PKS Troubleshooting and Notifications Reference 23
1/03 Honeywell Part I
Error
Code
Description Corrective Action
32
to
34
Not used. N/A
35 Illegal internal zero
configuration attempted
on this channel.
Check for an open thermocouple, fuse, or replace the
IOP.
36

Spare failure indicator. N/A
37 Spare failure indicator. N/A
38 Calibration of this slot has
aborted.
Check the precision voltage source for accuracy.
39
to
41
Not used. N/A
42
to
80
A/D slot conversion on
AIM slot underflowed min
allowed count (HLAI only).
Check the input wiring at the FTA; possible open contact.
Otherwise, replace the IOP card and/or the FTA.
81
to
255
Not used. N/A


Isolating Faults
RM Fault Isolation
24 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03

RM Fault Isolation

If then
THxy on stalled RM front panel
display.
(xy represents any 2 alphanumeric
characters)
The RM has failed a startup test.
Go to RM Test Sequence Numbers

Exyz error code on RM front panel
display.
(xyz represents any 3 alphanumeric
characters)
The RM has encountered a run-time error.
Go to the corresponding code at RM Fault
Codes

OK LED solid red on RM front
panel.
(with no Exyz error code displayed).
The RM has encountered a severe run-time
error.
First, take RM Corrective Action RM_CA02.
If the problem persists, take RM Corrective
Action RM_CA01.
And if it still persists, take General Corrective
Action GEN_CA01


Isolating Faults
STI and STI_MV IOP Fault Isolation
Release 100 Experion PKS Troubleshooting and Notifications Reference 25
1/03 Honeywell Part I

STI and STI_MV IOP Fault Isolation
This section discusses transmitter error and diagnostic messages associated with Smart
Transmitter Interface (STI) or Smart Transmitter Interface Multivariable (STI_MV) IOP
operation which may be sent to the Operator Station or SFC. Error codes for various
smart transmitters are listed along with suggested corrective actions.
Process Variable Reliability
The replacement of an analog PV signal with a digital PV signal can represent an
increase in process value security if all the proper measures discussed below are
implemented. The DE protocol provides the means necessary for accurate secured
communication of process signals between field devices and their controllers. When
used in conjunction with a Smart Transmitter IOP board, increased knowledge of the
field device is provided along with the signal processing required for the digital PV to
attain its high level of performance.
The analog version of the PV contains no checks and balances of any form to indicate to
the control system the instantaneous validity of the PV signal. Also, the analog PV
signal is not impervious to noise and the control system has no means of recovering lost
or corrupted analog PV signals.
It should be noted that the control system, in a DE protocol environment, functions as a
passive listener only and is incapable of polling field sensors. As a result, lost or
corrupted digital PV data cannot be retransmitted by request. In fact, if that were
possible, more PVs would be lost due to the increased communication activity.
Since the DE protocol requires that the field device continuously broadcast PVs, loss of
one sample is immediately followed by another sample. As a result, the control system
(Smart Transmitter IOP) need only determine whether a given sample is good or bad.
This analysis serves to establish the rate at which the controller can be expected to miss
PVs due to a corrupted digital communication channel, and also to establish a rate at
which the Smart Transmitter IOP can be expected to detect that corruption.
The analysis falls into three categories:
Error detection
Noise immunity
Noise rejection
Isolating Faults
STI and STI_MV IOP Fault Isolation
26 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Error Detection
The Digital Enhanced (DE) protocol incorporates two means of enhancing error
detection:
Field Device Status
Information Redundancy
Field Device Status
The original analog version of the PV has no way of indicating field device failures to the
control system, instantly. Many field devices use a burnout technique to indicate device
failuresthis is usually not instantaneous, and the controller may have already begun
control on a signal being driven towards burnout. Consequently, there is no effective
means to indicate to the control system the validity of an analog PV signal.
The DE protocol, however, requires that an indication of the field device status be
transmitted with every digital PV value. As a result, a controller is never controlling a
PV from a known bad field device.
Information Redundancy
Redundancy is the addition of noninformation carrying bits so that particular
mathematical calculations can be made at the receive end to determine whether the group
of bits, including the redundant bits, are the same as those transmitted. This process
ensures that the original information was correctly received while allowing the capability
to detect bad message blocks and have them rejected by the system. The DE protocol
contains Byte parity (VRC) redundant bits in the message block.
The digital PV value is contained in bytes 2 through 4 of the message block. As a further
means of screening potentially bad PV data, all consecutive byte parities (for bytes 1
through 4) must be good before a new digital PV value is accepted by the Smart
Transmitter IOP.
Isolating Faults
STI and STI_MV IOP Fault Isolation
Release 100 Experion PKS Troubleshooting and Notifications Reference 27
1/03 Honeywell Part I
Standardized tests
The following tests were performed on the actual hardware with the results focused on
the PV validity. Test reports are available from Honeywell by special request.
Temperature
Voltage Margin
Power Cycling
ANSI Surge
RFI
ESD
Fault Insertion
Noise Immunity
In DE protocol, increased noise immunity is gained by using a digital communication
baud rate that is low in frequency relative to its environmental noise. The DE protocol
transmits at a rate of 218 baud. The advantages of this are
1. High frequency noise can be easily filtered out with simple RC filters (on the Smart
Transmitter IOP board).
2. It is less likely that burst noise will last long enough or contain enough energy to
interfere with the signal.
Noise immunity is also gained by selecting significantly large and different
voltage/current levels to represent a logical 1 and 0. For the DE protocol, these levels are
4 mA/1 volt and 20 mA/5 volts.
Isolating Faults
STI and STI_MV IOP Fault Isolation
28 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Noise Rejection
The term noise rejection indicates that the digital PV signal is communicating through
twisted pair wire in floating point numbers.
Since noise rejection assumes that noise has already corrupted the signal, all noise
rejection techniques, in DE protocol, are only applicable to the Smart Transmitter IOP.
The Smart Transmitter IOP has the capability of rejecting noise using four techniques:
1. Digital Input Filteringthe IOP contains a simple RC input filter to eliminate high
frequency noise. The 3db point is set at 482 Hz.
2. Samples per BitThe IOP software UART will take five samples per bit and use a
voting technique before declaring a given logic level. Four of the five bit samples
must agree for data to be considered good.
3. Floating Point Value CheckThe IOP software verifies that the received floating
point value is of a valid form. All floating point values that do not conform are
rejected.
4. Digital Noise FilteringThe IOP software treats the received good digital PV as a
real signal by not allowing unusually large instantaneous transitions to occur. This is
accomplished by comparing the received digital PV sample with the previous sample.
If the new sample differs by greater than 30% of the working range, the new value is
discarded and the old value is used for control. The next digital PV value is always
used. This technique allows the IOP to reject multibit errors which might pass
undetected and corrupt the digital PV. Its limitations are that it can only reject one
noise sample and it causes a temporary lag in the process.
Smart Transmitter Error Codes
The following tables list error codes that appear on the STI_MV point detail display at
the station as IOP diagnostics for ST3000, STT3000, and MagneW3000 Smartline
Transmitters.
Error codes for multivariable field devices are described in the user manual for the
specific field device.
Isolating Faults
STI and STI_MV IOP Fault Isolation
Release 100 Experion PKS Troubleshooting and Notifications Reference 29
1/03 Honeywell Part I
ST 3000 Pressure Transmitter Error Codes

Critical Error Codes Noncritical Error Codes
Char PROM Fault
Suspect Input
Electronic Fault

Sensor Over Temp
Excess Zero Corr.
Excess Span Corr.
In Output Mode
Meter Body Overload
or Meter Body Fault
Corrects Reset
1


STT 3000 Temperature Transmitter Error Codes

Critical Error Codes Noncritical Error Codes
Self-Test Fail
ISO Comm Fail
Input Open
Inval. Cal Data
Inval User Data
NVM Write Fail

Amb. Temp HI/LO
Uncertain Reading
I/P out of Spec.
Uncertain CJC
Excess Zero Corr.
In Output Mode
User Corr. Active


MagneW 3000 Flowmeter Transmitter Error Codes

Critical Error Codes Noncritical Error Codes Noncritical Error Codes
Excit. Coil Fail.
A.C. Power Loss
NVM Fault
RAM Fault
A/D Fault
Bad Config. Data
Local Mode
DO Output Mode
Fixed Pulse Mode
Output Mode
In Cal. Mode
Corrects Reset
1
Excit. Check Mode
Empty Pipe
Ext. Zero Active
Type/Dia Error
Hi<Lo Alarm Error
Span>Range
Pulse Weight Error
Pulse>70%
Hysteresis Error

1
Corrects Reset This error message on an Smartline 3000 Pressure or MagneW
transmitter means that someone has sent a Reset Correct (Rst Cor) command to the
transmitter from the SFC or the US. This command sets the calibration values to those
set into the transmitters nonvolatile memory during the characterization phase of the
transmitters manufacture.
Isolating Faults
STI and STI_MV IOP Fault Isolation
30 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
To remove the Corrects Reset message, calibrate the transmitter using a lab standard. If
you do not want to recalibrate, make sure that LRV is zero, vent the transmitter to zero
inches, send a Correct LRV command, then switch transmitter power off and on.
Smart Transmitter IOP Messages
The following messages appear on the operator station in the Transmitter Status field of
the Detail display.
Smart Transmitter IOP Status Messages on US

Message Problem Corrective Action
XMTR DATABASE IS
NOT YET AVAIL
SYSTEM ACQUIRING
DATABASE ...WAIT
(R230 or later)
Power-up. No action required. Wait
for system to acquire
database.
XMTR DATABASE NOT
AVAILABLE XMTR
FAILED OR
IN ANALOG MODE
(R230 or later)
No DE data on a slot. Attempt to switch
transmitter to 6-byte DE
mode. If you cannot do
this, replace the
transmitter.
XMTR DATABASE NOT
AVAILABLE XMTR IN
PV MODE
W/O DB ACCESS
(R230 or later)
STI IOP is in 4-byte DE
mode.
No action required. If you
want database, switch to
PV_DB or PV_SV_DB, 6-
byte mode.
SFC MODIFIED XMTR
DATABASE SYSTEM
ACQUIRING DATABASE
...WAIT
(R230 or later)
SFC activity has modified
the transmitter database.
6-byte mode column:
upload or download if
required; or wait for
message to disappear. 4-
byte mode column: R230,
download; R300 or later,
upload or download.
COMMAND FAILURE
UNSUCCESSFUL
COMMUNICATIONS
(R300 or later)
Failed download or
calibrate command from
transmitter.
Try again; if command
fails, investigate for
problem in the transmitter
or diagnostic procedure
on the communication
link.
Isolating Faults
STI and STI_MV IOP Fault Isolation
Release 100 Experion PKS Troubleshooting and Notifications Reference 31
1/03 Honeywell Part I
Message Problem Corrective Action
COMMAND FAILURE
INVALID REQUEST
(R300 or later)
Failed download or
calibrate command from
transmitter.
Verify that the correct
function has been
requested.
COMMAND FAILURE
LOCAL MODE
(R300 or later, MagneW
only)
Failed download or
calibrate command from
transmitter.
Refer to MagneW 3000
Magnetic Flowmeter
Users Guide, 36-KI-25-
01.
COMMAND FAILURE
FIELD DEVICE IS
WRITE PROTECTED
(R300 or later, MagneW
or ST only)
Failed download or
calibrate command from
transmitter.
Remove the write protect
from the transmitter.
Refer to MagneW 3000
Magnetic Flowmeter
Users Guide, 36-KI-25-01
or ST 3000 Smart
Transmitter Users
Manual, 34-ST-32-02B.
COMMAND FAILURE
NVM BAD
(R300 or later)
Failed download or
calibrate command from
transmitter.
Replace transmitter.
COMMAND ALLOWED
ONLY ON FIRST SLOT
OF MULTIPLE PV
XMTRS
Attempted to download
database with DECONF
change from slot 2, 3, or
4.
Call up slot 1 Detail
display for PV1 and retry
database download
command.
COMMAND FAILURE
. . . BUSY
Command could not be
executed because
transmitter is busy
Retry command.
CONFIGURATION
MISMATCH MULTIPLE
DEVICES ASSIGNED
TO SLOT
Another transmitter is
physically connected to a
logical slot for a
multivariable transmitter.
Disconnect offending
transmitter or reconfigure
the number of PVs for the
SMV 3000 transmitter.
TRANSMITTER IS
BROADCASTING A
SUBSTITUTE VALUE
PV
Transmitter is in output
mode or input mode.
Use SCT 3000 to remove
transmitter from output
mode or input mode.

Isolating Faults
STI and STI_MV IOP Fault Isolation
32 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03

Release 100 Experion PKS Troubleshooting and Notifications Reference 33
1/03 Honeywell Part I
Front Panel Indicators
BEM
The only BEM front panel indicator is the OK LED.
OK LED

This Display: Means: Corrective Action:
Off No Power. See BEM_CA01.
Toggling
Red/Green
N/A N/A
Flashing
Green
N/A N/A
Flashing Red N/A N/A
Solid Green The battery voltage is within spec (3.0V to
4.6V), and a simple hardware diagnostic
passes.
N/A
Solid Red The battery voltage is out of spec and/or
something is wrong with the module
See BEM_CA02.

Front Panel Indicators
CNI
34 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
CNI
Normal Runtime Displays
A ControlNet interface module in either a standalone or redundant configuration
normally displays the following messages. Note that the messages are listed in the
sequence in which they are displayed.

4 Character Display
Message
Description of Cause
(A,#,x,x) Address indication where xx indicates the ControlNet Mac ID.
( ,O,K, ,) CNI is operating normally
Redundancy
State
Refer to Controller Redundancy Specific Displays if CNI resides in a
redundant chassis.
(%,C,x,x) Percentage of CPU usage where xx is in the range 00 - 99%.
Because of display limitations, the maximum value displayed will be
99% even if CPU usage reaches 100%.
(K,p,x,x) Module's keeper state, where xx can be one of the following
abbreviations:
Ov - the keeper is powering up or off line with valid keeper information
that may or may not match the network keeper signature.
Oi - the keeper is powering up or off line with invalid keeper
information.
Av - the keeper is the active network keeper, with valid keeper
information, whose keeper signature defines the network keeper
signature.
Iv - the keeper is an inactive network keeper with valid keeper
information that matches the network keeper signature.
Ai - the keeper is the active network keeper either with invalid keeper
information or with a keeper signature that does not match the
network keeper signature.
Ii - the keeper is an inactive network keeper either with invalid keeper
information or with a keeper signature that does not match the
network keeper signature.
(n,C,x,x) Number of open connections used by the CNI, where xx is in the rage
of 00 to 64 connections.
Front Panel Indicators
CNI
Release 100 Experion PKS Troubleshooting and Notifications Reference 35
1/03 Honeywell Part I
4 Character Display
Message
Description of Cause
(n,U,x,x) Number of unconnected buffers used by the CNI, where xx is in the
range of 00 to 20 buffers.
(B,x,n,n) Number of bandwidth exceeded occurrences since the last power
cycle or module reset, where nn is in the range of 00 to 99
occurrences after which the display rolls over to 00 and continues
counting.
A bandwidth exceeded error occurs whenever module has all its
receive buffers in use at the same time and an additional buffer is
needed. At that point, the module clears all of the received buffers
thus destroying their contents, in an effort to recover from the
resource overload.
A bandwidth exceeded error might also occur when the module
firmware is flash updated. In this case, clearing of the buffers is
necessary to begin the flash update process. This error is
automatically cleared after the flash process by way of the module
reset after the flash update.
The bandwidth exceeded count display is disabled until the first
bandwidth exceeded event is detected. Once one has occurred, the
display will remain activated and be a part of the display sequence.
The count and display is cleared whenever the module is reset or
power cycled.

Front Panel Indicators
CNI
36 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Abnormal Displays
A ControlNet interface module in either a standalone or redundant configuration can
display the following messages.

OK
Status
Light
4 Character Display
Message
Description of Cause Corrective Action
GREEN (I,N,I,T,) CNI is performing post powerup
initialization.
Wait
GREEN ( ,O,K, ,) CNI is operating normally None needed
FL.RED (R,O,M, ,U,P,D,T) flash loading from application is
in progress
Wait
GREEN ( ,S,W, ,E,R,R, ) Mac ID Switch changed after
powerup or when in a redundant
secondary, Mac ID not set the
same as primary.
Adjust switch
settings
FL.GRN (C,N,F,G,E,R,R, ) ControlNet Config error Call SSC
RED (A,D,D,R,E,R,R, ) Two node 1's, or node set to 00
or node 99 if redundant
Adjust switch
settings
RED (R,A,C,K,E,R,R, ) Cannot read backplane EPROM
or rack/slot address incorrect
Call SSC
RED (D,U,P,L,N,O,D,E) There is another node on the
network at the same address
(May be a temporary condition
during redundant switchover)
Adjust switch
settings (unless
temporary
condition during
switchover)
FL.GRN (N,E,T, ,E,R,R, ) CNI cannot find network
connection
Check that all drop
cables are
attached, check
for faulty drop,
check cabling in
general
RED (C,N,I,C,E,R,R, ) Cnet ASIC Error Call SSC
RED (B,P,I,C,E,R,R, ) Backplane ASIC error Call SSC
RED (B,P,R,X,E,R,R, ) Backplane receiver error Call SSC
Front Panel Indicators
CNI
Release 100 Experion PKS Troubleshooting and Notifications Reference 37
1/03 Honeywell Part I
OK
Status
Light
4 Character Display
Message
Description of Cause Corrective Action
RED (B,P,A,#,E,R,R, ) Backplane address # (slot
number) error
Call SSC
GREEN ( ,B,W, ,>,M,A,X) Bandwidth exceeded, temporary
Cnet scheduling problem
wait
RED (S,T,O,P,) CNI commanded to stop
functioning by the Redundancy
Module (Occurs when a non
redundancy compliant CNI is
placed into a redundant
secondary chassis)
Check that the
stopped CNI is
redundancy
capable (TC-
CCx012 or TC-
CCx013 where x
equals N or R)

Front Panel Indicators
CNI
38 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Controller Redundancy Specific Displays
A redundant compliant ControlNet interface module in only a redundant configuration
can display the following messages.

OK
Status
Light
4 Character Display
Message
Description of Cause Corrective Action
RED (W,A,I,T, ,R,M, ) CNI waiting for the Redundancy
Module to complete powerup
wait
GREEN (P,w,D,S) CNI is primary with a
disqualified secondary partner
Synchronize
Secondary
GREEN (P,w,Q,g) CNI is primary with a qualifying
secondary partner
wait
GREEN (P,w,Q,S) CNI is primary with a qualified
secondary partner
None needed
GREEN (P,w,N,S) CNI is primary with a no
secondary partner
Inspect secondary
GREEN (Q,U,A,L) Primary CNI is qualified with its
partner
wait
GREEN (C,M,P,T) Secondary CNI is compatible
with its partner
wait
GREEN (D,I,S,Q) Secondary CNI is disqualified Synchronize
Secondary
GREEN (Q,f,n,g) Secondary CNI is qualifying wait
GREEN ( ,Q,S, ) Secondary CNI is qualified None needed
GREEN (D,S,N,P) Secondary CNI is disqualified
with no partner
Inspect partner
and RMs

Front Panel Indicators
CNI
Release 100 Experion PKS Troubleshooting and Notifications Reference 39
1/03 Honeywell Part I
The following messages would be displayed only if the CNI module failed during
transition from one phase to another and are provided as diagnostic tools.

OK Status
Light
4 Character Display
Message
Description of Cause Corrective Action
GRN/off (S,O, ,1) Old primary switchover phase 1
in progress

GRN/off (S,O, ,2) Old primary switchover phase 2
in progress

GRN/off (S,O, ,3) Old primary switchover phase 3
in progress

GRN/off (S,N, ,1) New primary switchover phase
1 in progress

GRN/off (S,N, ,2) New primary switchover phase
2 in progress

GRN/off (S,N, ,3) New primary switchover phase
3 in progress

GRN/off (s,e,t,C) CNI set to be compatible with its
partner

GRN/off (s,e,t,!) CNI set to not be compatible
with its partner

GRN/off (?,C,p,t) CNI has not determined if it is
compatible

GRN/off (!,C,p,t) CNI has determined that it is not
compatible
See CNI Not
Compatible

Front Panel Indicators
CNI
40 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Common questions

Question Answer
1. My CNI shows the word !CPT.
Is this an error?
A display of !CPT is not normal and needs corrective
action. Hyperlink to PSTS_08.

2. My CNI shows the word FAULT or
ASSERT scrolling across it.
Is this an error?
If the CNI is displaying FAULT or ASSERT or the
health LED is solid Red, copy down the exact
sequence of symbols being shwon on the 4 character
display. Collect (hyperlink to the NetworkTools
writeup on this) CPM BreadCrumbs and RM Events
from the Primary and Seconday if this is a Redundant
C200. Cycle power to the chassis.

Front Panel Indicators
CPM
Release 100 Experion PKS Troubleshooting and Notifications Reference 41
1/03 Honeywell Part I
CPM
The CPM front panel indicators include two LEDs and the Alphanumeric Display.
OK LED
The OK LED, on the right, indicates the overall health of the CPM.

This
Display:
Means: Corrective
Action:
Off No Power. Check the
CPM_CA01.
Toggling
Red/Green
N/A N/A
Flashing
Green
While in the CPM Alive, Ready or Loading States
(i.e. executing CPM Boot firmware), the flashing
green Health LED serves as a heartbeat indication
that the module is functioning properly. However,
the module is not capable of performing control.
Load CPM
firmware
CPM_CA02.
While in the CPM Backup State (i.e. executing
CPM Application FW), the flashing green Health
LED serves as a heartbeat indication that the
module is functioning properly. However,
synchronization with the primary redundant partner
has not yet been achieved.
Isolate reason
for loss of
synchronizatio
n CPM_CA03.
Flashing
Red
Indicates that the CPM is currently in the Fail State
(i.e. executing CPM Boot firmware).
Recover from
CPM Fail State
CPM_CA04.
Solid Green The Health LED is only ever solid green when
executing CPM Application firmware. While the
Alphanumeric Display indicates that the CPM is in
one of the NotLoaded, NoCEE, Idle, Run or Backup
States, a solid green Health LED indicates the
module is operating as expeted. Furthermore,
while in the CPM Backup State, a solid green LED
indicates that the secondary CPM is synchronized
with its primary partner.
N/A
Solid Red Upon initial CPM startup, the Health LED is solid
red until the CPM successfully completes startup
diagnostics and settles in the Application or Boot
personality.
N/A
Front Panel Indicators
CPM
42 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
This
Display:
Means: Corrective
Action:
If after CPM startup has completed or CPM startup
halted (i.e. Alphanumeric Display indicating the
same test sequence number for more than 30
seconds) a major fault has occurred. The CPM
must be restarted and/or replaced.
Restart the
CPM
CPM_CA05.

Front Panel Indicators
CPM
Release 100 Experion PKS Troubleshooting and Notifications Reference 43
1/03 Honeywell Part I
Battery LED
The Battery LED, on the left, indicates whether the CPM is capable of retaining any
loaded control strategy after AC power loss.

This
Display:
Means: Corrective
Action:
Off No Power. Check the
CPM
CPM_CA01.
Toggling
Red/Green
N/A N/A
Flashing
Green
N/A N/A
Flashing
Red
N/A N/A
Solid Green Upon initial CPM startup, the Battery LED is solid
green until the completion of the Alphanumeric
Display test so that all LED colors can be checked
by the factory test technician.
N/A
After the CPM settles in the Application or Boot
personality, a solid green Battery LED indicates
that the startup diagnostics have been successfully
completed, and that one, and only one, battery is
present and of proper voltage.
N/A
Solid Red During CPM startup, the Battery LED is solid red
until the completion of the startup diagnostics.
N/A
After the CPM settles in the Application or Boot
personality, a solid red Battery LED indicates the
battery is defective/missing or an invalid battery
configuration exists.
Replace
defective
battery or
correct invalid
battery
configuration
CPM_CA07.

Front Panel Indicators
CPM
44 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
4-Character Display
The purpose of the Alphanumeric Display is to provide a local view of the status of the
CPM only; it is not meant to provide any definitive information about other modules
residing in the same chassis.

This
display:
Means: Take this
action:
ALIV The startup diagnostics have successfully
completed but no Application firmware exists. ICP
Communication is enabled and the CPM remains in
the CPM Alive State until the user commands
Application firmware download which results in the
transition to the CPM Loading State.
Load CPM
firmware
CPM_CA02.
BKUP The CPM startup diagnostics have successfully
completed and the CPM is executing the
Application personality. Furthermore, the CPM is in
the secondary redundancy role. Note that whether
the secondary CPM has achieved synchronization
with its primary partner or not is indicated by the
Health LED.
N/A
BOOT Upon completing the CPM startup diagnostics, the
CPM enters the transient Booting State during
which the operating system is started. Prior to
starting the operating system within the Application
FW, the Alphanumeric Display is updated to display
BOOT. The CPM normally transitions to the
NotLoaded, NoCEE, Idle, Run, or Backup State
within 30 seconds. Initially, ICP Communication is
not active, but it is enabled prior to completion of
the Booting State.
N/A
An abnormal condition exists if the CPM remains in
the Booting State for more than 30 seconds. Note
that if a RM is present in the chassis, the CPM
remains in the Booting State while the RM performs
its startup diagnostics.
Check the RM
CPM_CA08.
FAIL A fault condition was encountered which results in
the termination of any control activity. A transition
to the CPM Fail State may occur from any CPM
State. ICP communication is enabled in an attempt
to remain visible so that error information may be
queried from the failed module.
Recover from
CPM Fail State
CPM_CA04.
Front Panel Indicators
CPM
Release 100 Experion PKS Troubleshooting and Notifications Reference 45
1/03 Honeywell Part I
This
display:
Means: Take this
action:
IDLE The CPM is executing the Application personality
firmware in the Idle State. Although a control
strategy is loaded, the control strategy in inactive.
Note that if the CPM was in the Run State prior to a
Retention Startup, the CPM State is forced to Idle
so that the user may judge whether it is safe to
immediately go on control (e.g. based upon the
length of the power down).
Activate CPM
control strategy
CPM_CA09 .
IISC One or more unrecognized command errors have
occurred.
No Qsend errors have occurred.
A copy of the control block that caused the last
PCmnd error is stored in memory. See the
implementation details for more information.
N/A
IISQ One or more Qsend errors have occurred.
No unrecognized command errors have occurred.
N/A
IISR Both types of errors have occurred at least one
time.
A copy of the control block that caused the last
PCmnd error is stored in memory. See the
implementation details for more information.
N/A
LOAD Upon commencing Application or Boot personality
firmware download (user commanded action), the
CPM transitions from the CPM Alive/Ready/Fail
State to the CPM PI Loading State. The CPM
remains in the transient CPM PI Loading State
throughout the firmware download operation.
N/A
Upon encountering an error programming the CPM
Application or Boot personality, reattempt the
firmware download operation. Note that an error
programming the Boot personality may require the
CPM to be returned to the factory to be
reprogrammed.
Reload CPM
firmware
CPM_CA02.
Front Panel Indicators
CPM
46 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
This
display:
Means: Take this
action:
NODB The CPM is executing the Application personality
firmware in the NotLoaded State. This implies that
no control strategy exists. Note that the CPM State
remains NotLoaded until the first load of the CPM
FB. If power is lost before the load of the CPM FB,
the CPM State settles back into the NotLoaded
State after powerup.
Create/Load
CPM control
strategy
CPM_CA10.
If the CPM was in the Idle or Run State prior to
loosing power, Retention Startup may not have
been possible due to a very long power down or a
marginal battery.
Replace
defective
battery or
correct invalid
battery
configuration
CPM_CA07.
NOEE The CPM is executing the Application personality
firmware in the NoCEE State. The transient
NoCEE State is visible between the load of the
CPM FB and the CEE FB. Since the user initiated
load of the CPM FB automatically loads the CEE
FB, the CPM normally transitions to the Idle State.
N/A
An abnormal condition exits if the CPM remains in
the NoCEE State. This implies that the CPM FB
was loaded but the CEE FB has not been loaded.
Reload the
CPM FB
CPM_CA11.
PASS Upon completing the CPM startup diagnostics, the
CPM enters the transient Booting State during
which the operating system is started. Prior to
starting the operating system within the Boot FW,
the Alphanumeric Display is updated to display
PASS. The CPM normally transitions to the Alive,
Ready, or Fail State within 30 seconds. Initially,
ICP Communication is not active, but it is enabled
prior to completion of the Booting State.
N/A
An abnormal condition exists if the CPM remains in
the Booting State for more than 30 seconds. Note
that if a RM is present in the chassis, the CPM
remains in the Booting State while the RM performs
its startup diagnostics.
Check the RM
CPM_CA08.
Front Panel Indicators
CPM
Release 100 Experion PKS Troubleshooting and Notifications Reference 47
1/03 Honeywell Part I
This
display:
Means: Take this
action:
RDY The CPM is executing the Boot personality
firmware in the Ready State. A valid Application
personality exists. ICP Communication is enabled.
The CPM remains in the CPM Ready State until the
user either commands Application FW download or
issues the Start command. The CPM transitions to
the CPM Loading State in the former case or
reboots into the Run, Idle, NoCEE, NotLoaded or
Backup State in the latter case, respectively.
Restart the
CPM
CPM_CA05.
RUN The CPM is executing the Application personality
firmware in the Run State. This implies a control
strategy is loaded and the control strategy in active.
N/A
Txxx Upon being released from reset, the CPM enters
the transient Testing State during which the CPM
executes startup diagnostics. Prior to executing
each diagnostic, a test sequence number, Txxx, is
posted to the Alphanumeric Display so that if a test
fails or hangs, the Alphanumeric Display indicates
the test that was in progress at the time of failure.
The test of longest duration takes much less than
30 seconds to complete.
N/A
An abnormal condition exists if the CPM remains
displaying the same Test Sequence Number for
more than 30 seconds.
Interpret the
CPM Test
Sequence
Number Table
of CPM Test
Sequence
Numbers.
wait Once the new Application or Boot firmware is
loaded, the CPM disappears from the ICP
backplane while the personality is programmed into
flash ROM. The CPM reboots within 30 seconds.
N/A
An abnormal condition exists if the CPM remains
displaying wait for more than 30 seconds.
Restart the
CPM
CPM_CA05.
Front Panel Indicators
CPM
48 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
This
display:
Means: Take this
action:
WDT Indicates the CPM Watchdog Timer has timed-out. Recover from
CPM
Watchdog
Timer Timeout
CPM_CA13.

Front Panel Indicators
Input Modules
Release 100 Experion PKS Troubleshooting and Notifications Reference 49
1/03 Honeywell Part I
Input Modules

Display: LED: Means: Take this action:
OK Steady green light The inputs are being multicast
and in normal operating state.
None.
OK Flashing green light The module has passed internal
diagnostics but is not multicasting
inputs or it is inhibited
None.
OK Flashing red light Previously established
communication has timed out.
Check controller and
chassis
communication.
OK Steady red light The module must be replaced. Replace the module.
I/O State Yellow The input is active. None.
I/O Fault Red A fault has occurred for this point. Check this point at the
controller.

Front Panel Indicators
Output Modules
50 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Output Modules

Display: LED: Means: Take this action:
OK Steady green light The outputs are actively
controlled by a system processor.
None.
OK Flashing green light The module passed internal
diagnostics, but is not actively
controlled, or is inhibited.
None.
OK Flashing red light Previously established
communication has timed out.
Check controller and
chassis
communication.
OK Steady Red light The module must be replaced. Replace the module.
I/O State Yellow The output is active. None.
I/O Fuse Red A short overload fault has
occurred for this point.
Check wiring for short
overload.
I/O Fault Red A fault has occurred for this point. Check this point at the
controller.

Front Panel Indicators
Serial Interface Modules
Release 100 Experion PKS Troubleshooting and Notifications Reference 51
1/03 Honeywell Part I
Serial Interface Modules
4-Character Display
Startup/Selftest Mode

This
Display:
Means: Corrective Action:
Tnnn Selftest Current Test Sequence Number. If the SIM stalls
with one of these
numbers
displayed, replace
the SIM.
TEST Factory Test Mode. Entered on command or
because the backplane test signal was
asserted.
Can be loaded.
PASS Completed Selftest. Attempting to execute
Boot.
None.
ALIV Running in Boot; no personality is present. Can be loaded.
WDT (LED Green/Red)
Factory Test Mode Commanded WDT test
waiting for timeout interrupt. Health LED will
turn from GREEN to RED upon WDT timeout.
None.

Front Panel Indicators
Serial Interface Modules
52 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Post-Startup and Firmware Load Information

This
Display:
Means: Corrective Action:
ALIV Running in Boot; no personality is present. Can be loaded.
RDY Running in Boot; personality is present but shut
down.
Can be loaded or
started.
LOAD Running in Boot with an open loader
connection.
None.
BOOT Completed Selftest. Attempting to execute
personality.
None.
wait Attempting to program Flash ROM.
(Health LED is RED during actual programming)
None.
stop Shutting down (transitional) None.
WDT Watchdog Timer Fault. A power cycle is
required to recover the module.
If the problem
persists, call SSC.

Display of Runtime Information
The SIM will alternately display module status and status of channels A and B.

This
Display:
Means: Corrective
Action:
OK Running in personality alternates with display of
channel states.
None.
A ok
B ok
Channel is operating normally, communicating with
FTA, and FTA is communicating with attached
device.

Aerr
Berr
Channel cannot communicate with FTA
A st
B st
Channel can communicate with FTA but FTA is
reporting a soft failure. Information about the error
can be obtained through pcmana or NTools.

Acfg
Bcfg
Channel is being configured. This is normally a
transient display. A bad configuration will make it
appear permanent.


Front Panel Indicators
Serial Interface Modules
Release 100 Experion PKS Troubleshooting and Notifications Reference 53
1/03 Honeywell Part I
Display of Failure Information
When the CPM is in the Fail state, the alphanumeric display will alternate the numeric
fail code and FAIL.

This
Display:
Means: Corrective Action:
FAIL
alternating
with nnnn
Software error nnnn has occured. Running in
Boot. Can be loaded, recovered or restarted.
A power cycle is
required to recover
the module.
If the problem
persists, contact
SSC.
WDT Watchdog Timer Fault. A power cycle is
required to recover
the module.
If the problem
persists, contact
SSC.
WDT (Let from Green to Red)
Factory Test Mode Commanded WDT test
waiting for timeout interrupt.
Health LED will turn from GREEN to RED
upon WDT timeout.
None

Front Panel Indicators
Serial Interface Modules
54 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Health Indicator
The Health LED is used to indicate the general state of the module.

This Display: Means: Corrective Action:
OFF No power; significant fault. None
Solid RED During load it means programming the Flash
ROM.
Selftest in progress or failed accompanied
by a test number in Alphanumeric display;
Hardware Fault, unrecoverable WDT
Timeout.
A power cycle is
required to recover
the module. If the
problem persists,
contact SSC.
Flashing RED Fail State, running under software control.
Alternating
RED/GREEN
Factory Test Mode.
Solid GREEN OK At leasst one I/O data connection
active.

Flashing
GREEN
During load it means getting ready to program
Flash ROM.
During run, it means no active I/O connection.


Channel Activity Indicators
There is a status/activity indicator for each channel of A and B.

This Display: Means: Corrective
Action:
OFF No activity Alive
Flashing
GREEN
Transmit or Receive in progress, but not normal
continuous communications.

Brief GREEN
flash every
0.5 sec
FTA is not present or not communicating a
retry is performed every 0.5 second.

Solid GREEN Normal communications with FTA produces
continuous illumination.



Front Panel Indicators
RM
Release 100 Experion PKS Troubleshooting and Notifications Reference 55
1/03 Honeywell Part I
RM
OK LED

This
Display:
Means: Corrective
Action:
Off No Power
Toggling
Red/Green
Powerup LED Self Test Wait
Flashing
Green
Module OK, but not communicating with other
chassis modules

Flashing
Red
Configured Improperly or
Non-Critical Failure or
NVS Update

Solid Green OK
Solid Red Critical module Failure or
RM Powerup Self Test
--
Wait

PRI LED

This
Display:
Means: Corrective
Action:
Off No Power or
RM Powerup Self Test or
Redundancy State = SECONDARY or
RM Failed

Toggling
Red/Green
Powerup LED Self Test
Flashing
Green
N/A --
Flashing
Red
N/A --
Solid Green Redundancy State = PRIMARY
Solid Red N/A --

Front Panel Indicators
RM
56 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
COM LED

This
Display:
Means: Corrective
Action:
Off No Power or
RM Powerup Self Test

Toggling
Red/Green
Powerup LED Self Test

Flashing
Green
No (or intermittent) partner connections.
Flashing
Red
N/A --
Solid Green Normal partner communications.
Solid Red Partner connection occurred.

Front Panel Indicators
RM
Release 100 Experion PKS Troubleshooting and Notifications Reference 57
1/03 Honeywell Part I
4-Character Display
Startup/Selftest Mode

This
Display:
Means: Corrective
Action:
(all pixels
on)
Visual test. The display will flash twice to allow the
user to quickly check the condition of the display.

THnx RM startup self test, Phase I.
T - designates a startup test.
H - designates the Self Test subsystem.
n x Numeric Subtest ID.
The n signifies a number. When this character is
a number, the RM is executing test code out of its
flash ROM. Most of the tests are against the RMs
RAM.
The Subtest ID is presented at the start of a test
and held only for the duration of a test. Most tests
execute too quickly for the operator to read the
code. However, should a test fail, the RM will tend
to hold the display so the user can identify the
failed test.

TH** RM self test decompressing its executive code into
RAM, after which the RM will begin executing out of
RAM.

Front Panel Indicators
RM
58 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
This
Display:
Means: Corrective
Action:
THax RM startup self test, Phase II.
T - designates a startup test.
H - designates the Self Test subsystem.
a x Alphabetic Subtest ID.
The a signifies a letter. When this character is a
letter, the RM is executing test code out of its RAM.
Most of the tests are against non-RAM subsystems,
and require the use of RAM-based functions such
as the stack and exception handlers.
The Subtest ID is presented at the start of a test
and held only for the duration of a test. Most tests
execute too quickly for the operator to read the
code. However, should a test fail, the RM will tend
to hold the display so the user can identify the
failed test.

???? RM resolving its initial Redundancy State. During
this time, the RM will wait for other modules to
complete startup, then it will gather information and
work its way through a series of tests to ascertain
its position in the Primary/Secondary relationship.


Front Panel Indicators
RM
Release 100 Experion PKS Troubleshooting and Notifications Reference 59
1/03 Honeywell Part I
Normal/Operational Mode

This
Display:
Means: Corrective
Action:
PRIM Primary - This RM and its chassis modules are
responsible for the chassis Assigned Functions.

DISQ Disqualified Secondary - The RM and its chassis
modules are a backup to the Primary, but are not
able to carryout the Primary chassis Assigned
Functions.
The other chassis modules may either be
Disqualified or Synchronizing when then RM is in
the Disqualified state.

SYNC Synchronized Secondary - The RM and its chassis
modules are a backup to the Primary, in a
Synchronized state, and able to carry out the
Primary chassis Assigned Functions, should a
switchover occur.


Fault/Failure Mode

This
Display:
Means: Corrective
Action:
Exxx Indicates a major fault (Error) situation, where xxx
represents an error code.

(Error Brief) An Error Brief summarizes the cause.
(Recovery
Message)
A Recovery Message summarizes the
recommended user action.

(Pause) A 1 second pause to delimit the Exxx - Error Brief -
Recovery Message sequence.


Front Panel Indicators
RM
60 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Firmware Upgrade Mode

This
Display:
Means: Corrective
Action:
BOOT Boot mode - awaiting further instructions
ERAS Boot mode - erasing firmware
PROG Boot mode - loading new firmware

Front Panel Indicators
IOLIM
Release 100 Experion PKS Troubleshooting and Notifications Reference 61
1/03 Honeywell Part I
IOLIM

The IOLIM has one four-character display and three two-color LEDs on its front
panel. The LEDs provide Link 1 status, Link 2 status, and module health status
(OK). The following table summarizes some typical indications for reference.


OK LED is . . . And, 4-Character
Display shows . .
Then, IOLIM is . . .
Solid Red TEST Factory test mode
T### Executing hardware diagnostic tests
(display shows T###, where ### is
the test number)
Solid Green BOOT Booting firmware
Flashing Green/off ALIV No application loaded
RDY Ready for firmware upgrade
LOAD Loading firmware
Solid Red PROG Downloaded firmware is being
programmed into Flash ROM
FAIL Failed
Solid Green if
secondary is
synchronized.
Flashing green if
secondary is not
synchronized.
BKUP Secondary IOLIM
Solid Green if there
are CDA connections
to the module.
Flashing green if no
CDA.
NODB No database
NOEE IOLIM block loaded, IOLINK block
not loaded.
OK IOLIM block loaded and running.
Front Panel Indicators
IOLIM
62 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
OK LED is . . . And, 4-Character
Display shows . .
Then, IOLIM is . . .
OK SF
(display alternates OK
and SF)
IOLINK detects a soft failure.

LINK Status LEDs
Two LEDs indicate the status of Link A and Link B. The following table describes
possible conditions.

If CHANNEL A or B
LED is . . .
Condition
Solid Red IOLIM self test
Flashing Red Channel communications error
Solid Green Channel communications OK
Flashing Green Channel communications warning


Release 100 Experion PKS Troubleshooting and Notifications Reference 63
1/03 Honeywell Part I
Fault Codes
CNI Fault Codes
The CNI utilizes a fault reporting protocol that pinpoints the location in CNI firmware
where an illegal condition occurs.
The fault is reported via a 3 part message shifted across the CNI front panel display. The
3 message parts include:

Fault Type ASSERT or FAULT
(Note: The difference between these two terms is
inconsequencial.)

Source file name e.g., smacisr.c

Line number (within file) e.g., 0733

In the event a CNI enters such a faulted (a.k.a. Asserted) state, reset the CNI via
CNI_CA02.
go to GEN_CA01.
Fault Codes
CPM Fault Codes
64 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
CPM Fault Codes
Background
Upon detection of a hard fault or critical failure, the CPM reboots into the Fail State.
Hardware permitting, ICP communications to the module is enabled. An error block is
generated (at the time of failure) to store information useful in diagnosis following the
occurrence of a fault. The error block survives power cycles as long as no RAM
parity/edac errors are introduced (i.e. single battery of proper voltage is present).
Each discernible type of detectable fault is assigned a unique faultcode. If the CPM
generated fault code is not defined in one of the following subsections, perform the
following general corrective action. First, recover from the CPM Fail State CPM_CA04.
If the problem persists, replace the CPM CPM_CA06.
0x0000

Description: The CPM faulted without generation of a fault code.
Cause: Software defect or memory corruption.
Corrective
Action:
First, recover from the CPM Fail State CPM_CA04. If the problem
persists, replace the CPM CPM_CA06.

0x0002

Description: The CPM encountered an unexpected Machine Check fatal
exception.
Cause: Memory corruption.
Corrective
Action:
First, recover from the CPM Fail State CPM_CA04. If the problem
persists, replace the CPM CPM_CA06.

0x0003

Description: The CPM encountered an unexpected Data Access fatal exception.
Cause: Memory corruption.
Corrective
Action:
First, recover from the CPM Fail State CPM_CA04. If the problem
persists, replace the CPM CPM_CA06.

Fault Codes
CPM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 65
1/03 Honeywell Part I
0x0004

Description: The CPM encountered an unexpected Instruction Access fatal
exception.
Cause: Unable to access ROM and/or memory corruption.
Corrective
Action:
First, recover from the CPM Fail State CPM_CA04. If the problem
persists, replace the CPM CPM_CA06.

0x0006

Description: The CPM encountered an unexpected Alignment fatal exception.
Cause: Memory corruption.
Corrective
Action:
First, recover from the CPM Fail State CPM_CA04. If the problem
persists, replace the CPM CPM_CA06.

0x0007

Description: The CPM encountered an unexpected Program fatal exception.
Cause: Memory corruption.
Corrective
Action:
First, recover from the CPM Fail State CPM_CA04. If the problem
persists, replace the CPM CPM_CA06.

0x0008

Description: The CPM encountered an unexpected Floating Point Unavailable
fatal exception.
Cause: Memory corruption.
Corrective
Action:
First, recover from the CPM Fail State CPM_CA04. If the problem
persists, replace the CPM CPM_CA06.

Fault Codes
CPM Fault Codes
66 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
0x000D

Description: The CPM encountered an unexpected Trace fatal exception.
Cause: Defective CPU (since this feature is only enabled in a development
scenario).
Corrective
Action:
Replace the CPM CPM_CA06.

0x0013

Description: The CPM encountered an unexpected Instruction Address
Breakpoint fatal exception.
Cause: Defective CPU (since this feature is only enabled in a development
scenario).
Corrective
Action:
Replace the CPM CPM_CA06.

0x0014

Description: The CPM encountered an unexpected System Management
Interrupt fatal exception.
Cause: {1} Watchdog Timer timeout.
{2} ICP ASIC Fault signal asserted.
Corrective
Action:
First, recover from the CPM Fail State CPM_CA04. If the problem
persists, replace the CPM CPM_CA06.

0x0401

Description:
PLTCLLSInvalidCrashCodeRange
Cause: Software defect (i.e. impossible condition that should never occur).
Corrective
Action:


Fault Codes
CPM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 67
1/03 Honeywell Part I
0x0402

Description:
PLTCLLSCantReserveCEEDB
Cause:
Corrective
Action:


0x0403

Description:
PLTCLLSCantReleaseCEEDB
Cause:
Corrective
Action:


0x0404

Description:
CEEUBTCantGetIdForStartUpTask
Cause:
Corrective
Action:


0x0405

Description:
CEEUBTCantSendCompleteToStartUpTask
Cause:
Corrective
Action:


Fault Codes
CPM Fault Codes
68 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
0x0406

Description:
CEEUBTErrorOnWaitForStartUpTask
Cause:
Corrective
Action:


0x0407

Description:
CEEUBTCantGetIdForCEEUBTask
Cause:
Corrective
Action:


0x0408

Description:
CEEUBTCantGetPriorityForCEEUBTask
Cause:
Corrective
Action:


0x0409

Description:
CEEBTCantGetIdForStartUpTask
Cause:
Corrective
Action:


Fault Codes
CPM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 69
1/03 Honeywell Part I
0x040A

Description:
CEEBTCantSendCompleteToStartUpTask
Cause:
Corrective
Action:


0x040B

Description:
CEEBTErrorOnWaitForStartUpTask
Cause:
Corrective
Action:


0x040C

Description:
CEEBTCantSetUpCycleTimingEvent
Cause:
Corrective
Action:


0x040D

Description:
CEEBTErrorOnWaitForFirstCycleTimingEvent
Cause:
Corrective
Action:


Fault Codes
CPM Fault Codes
70 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
0x040E

Description:
CEEBTErrorOnWaitForNthCycleTimingEvent
Cause:
Corrective
Action:


0x040F

Description:
CEEBTCantGetIdForCEEBTask
Cause:
Corrective
Action:


0x0410

Description:
CEEBTCantGetPriorityForCEEBTask
Cause:
Corrective
Action:


0x0411

Description:
CEEBTCantCreateCEEFB
Cause:
Corrective
Action:


Fault Codes
CPM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 71
1/03 Honeywell Part I
0x0412

Description:
CEEBTCantCreatePCMFB
Cause:
Corrective
Action:


0x0413

Description:
CFCMFBMAssignXferInstSize
Cause:
Corrective
Action:


0x0414

Description:
CFCMFBExecuteDFLOX
Cause:
Corrective
Action:


0x0415

Description:
CFCMFBUnBindBlocks
Cause:
Corrective
Action:


Fault Codes
CPM Fault Codes
72 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
0x0416

Description:
CEEBTCantAllocateSchedulerMemory
Cause:
Corrective
Action:


0x0417

Description:
CEEBTCantAllocateBlockManagerMemory
Cause:
Corrective
Action:


0x0418

Description:
CEEBTCantAllocateConnectionManagerMemory
Cause:
Corrective
Action:


0x0419

Description:
CEEBTCantCreatePhysicalPool
Cause:
Corrective
Action:


Fault Codes
CPM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 73
1/03 Honeywell Part I
0x041A

Description:
CEEBTCantCreateMemoryManager
Cause:
Corrective
Action:


0x041B

Description:
BMCantAccessRCOAMemory
Cause:
Corrective
Action:


0x041C

Description:
CCLITCantGetIdForStartUpTask
Cause:
Corrective
Action:


0x041D

Description:
CCLITCantSendCompleteToStartUpTask
Cause:
Corrective
Action:


Fault Codes
CPM Fault Codes
74 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
0x041E

Description:
CCLITErrorOnWaitForStartUpTask
Cause:
Corrective
Action:


0x041F

Description:
CCLMBindCallOutWasCalled
Cause:
Corrective
Action:


0x0420

Description:
CCLITMinorVersionChangeFailed
Cause:
Corrective
Action:


0x0421

Description:
CEEBTCantAllocateBlockTypeManagerMemory
Cause:
Corrective
Action:


Fault Codes
CPM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 75
1/03 Honeywell Part I
0x0422

Description:
CEEBTCantAllocateCCLManagerMemory
Cause:
Corrective
Action:


0x0423

Description:
CCLITAcquireLibrariesFailed
Cause:
Corrective
Action:


0x0424

Description:
CCLITCantGetIdForCEEBTask
Cause:
Corrective
Action:


0x0425

Description:
CEEBTCantGetIdForCCLITask
Cause:
Corrective
Action:


Fault Codes
CPM Fault Codes
76 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
0x0426

Description:
CEEBTCantSendInitEventToCCLITask
Cause:
Corrective
Action:


0x0427

Description:
CEEBTErrorOnWaitForCCLITask
Cause:
Corrective
Action:


0x0428

Description:
CCLITUnloadLibrariesFailed
Cause:
Corrective
Action:


0x0429

Description:
CEEBTCantSendEventToCCLITask
Cause:
Corrective
Action:


Fault Codes
CPM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 77
1/03 Honeywell Part I
0x042A

Description:
CCLITCantGetIdForCEEUTask
Cause:
Corrective
Action:


0x042B

Description:
CFCMFBCfInitialize
Cause:
Corrective
Action:


0x042C

Description:
CEEUBTInvalidTaskIDForGuaranteedStore
Cause:
Corrective
Action:


0x042D

Description:
ROLETCantGetROLETaskPriority
Cause:
Corrective
Action:


Fault Codes
Exchange Block ERRCODE Fault Codes
78 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
0x042E

Description:
ROLETCantSetCCLITaskPriority
Cause:
Corrective
Action:


0x042F

Description:
ROLETCantGetIdForCCLITask
Cause:
Corrective
Action:


0x0430

Description:
ROLETCantSendEventToCCLITask
Cause:
Corrective
Action:


0x0431

Description:
CEEUBTSharedRamDecodeFailure
Cause:
Corrective
Action:


Exchange Block ERRCODE Fault Codes
Fault Codes
Exchange Block ERRCODE Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 79
1/03 Honeywell Part I
Description
Communication errors and errors reported by the target device are stored without being
modified in the ERRCODE parameter of request type Exchange function blocks. All of
the PCCC errors and some of the other errors are generated by the target device. Please
refer to the Allen-Bradley documentation for additional information about these errors.
The fault codes for some common errors are listed below for convenient reference.
1

Name: CONNECTION_FAILED
Cause: A connection could not be established from the CPM to the target
device. Possible reasons for this error include:
An invalid relative path was specified.
A ControlNet cable on the path between the CPM and the
target is broken or has been disconnected.
The target device or an intermediate CNI on the path between
the CPM and the target is powered off.
The specified maximum number of target devices has been
exceeded.
Corrective
Action:


2

Name: INSUFFICIENT RESOURCE
Cause: There are insufficient resources in the CPM for this array block.
Corrective
Action:
Make sure that the specified maximum number of request array
blocks in the CPM has not been exceeded. Delete other array
blocks that are no longer being used to free resources in the CPM.

Fault Codes
Exchange Block ERRCODE Fault Codes
80 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
3

Name: INVALID VALUE
Cause: An invalid value has been specified for one or more elements in the
array.
This error is generated when the Numeric Array block has been
configured as a Write block and one or more values of PV fall
outside the limits imposed by the TGTDATATYPE.
For example, if TGTDATATYPE is specified as SIGNEDINT16 and
one or more values of PV in the array fall outside the integer range
of 16-bit Signed Integers (-32768 to +32767) or are NaNs, this error
will be generated.
The entire Write operation will fail (even for PV values that are in
range).
Corrective
Action:
Make sure that the values of PV fall within the appropriate range
before attempting the Write operation.

4

Name: IOI SYNTAX
Cause: An invalid tag name has been specified as the FILENAME for a CIP
Read or Write operation.
If this error occurs for a PCCC Read or Write, this error indicates
that communication is not supported between the CPM and the
target device or the specified version of the DHRIO module.
Corrective
Action:


Fault Codes
Exchange Block ERRCODE Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 81
1/03 Honeywell Part I
5

Name: UNKNOWN DESTINATION ADDRESS
Cause: An invalid tag name (or tag name index) has been specified as the
FILENAME for a CIP Read or Write operation.
If this error occurs for a PCCC Read or Write, this error indicates
that communication is not supported between the CPM and the
target device or the specified version of the DHRIO module.
Corrective
Action:


8

Name: SERVICE UNSUPPORTED
Cause: The specified operation is not supported by the target device.
Corrective
Action:


12

Name: OBJECT IN WRONG STATE
Cause: The current state of the target device prevents the execution of the
specified operation.
Corrective
Action:


14

Name: ATTRIBUTE CANNOT BE SET
Cause: The write operation cannot be completed because the value being
modified cannot currently be set.
Corrective
Action:


Fault Codes
Exchange Block ERRCODE Fault Codes
82 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
15

Name: PERMISSION DENIED
Cause: Permission is denied to carry out the specified operation.
Corrective
Action:


17

Name: REPLY WONT FIT
Cause: The response message is corrupt or is larger than expected and so
cannot be processed.
Corrective
Action:


19

Name: NOT ENOUGH DATA
Cause: The data received in the response is smaller than expected.
Corrective
Action:


21

Name: TOO MUCH DATA
Cause: The data received in the response is larger than expected.
Corrective
Action:


Fault Codes
Exchange Block ERRCODE Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 83
1/03 Honeywell Part I
31

Name: CONNECTION RELATED FAILURE
Cause: There is a connection-related failure due to communication
problems in the path between the CPM and the target device.
Corrective
Action:


34

Name: INVALID REPLY
Cause: The data size or data type of the response is incompatible with the
type of array block being used for CIP access. Note that the Flag
Array Block can only access Binary (BOOL) files, the Numeric Array
block can only access Integer (SINT, INT, DINT) and Single
Precision Floating Point (REAL) files, and the Text Array block can
only access ASCII files.
Corrective
Action:


255

Name: Wrong Data
Cause: There is something wrong in your data that you are writing.
Corrective
Action:
Chedk for NaN.

512

Name: PCCC Error
Cause: Cannot guarantee delivery, link layer timed out or received a NAK.
Corrective
Action:


Fault Codes
Exchange Block ERRCODE Fault Codes
84 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
768

Name: PCCC Error.
Cause: Duplicate token holder detected by link layer
Corrective
Action:


1024

Name: PCCC Error
Cause: Local port is disconnected.
Corrective
Action:


1280

Name: PCCC Error
Cause: Application layer timed out waiting for a response.
Corrective
Action:


1536

Name: PCCC Error
Cause: Duplicate node detected.
Corrective
Action:


1792

Name: PCCC Error
Cause: Node is off-line.
Corrective
Action:


Fault Codes
Exchange Block ERRCODE Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 85
1/03 Honeywell Part I
2010

Name: Peer Connection Error
Cause: Internal error or resource constraint in the CEE's processing of a
peer connection.
Corrective
Action:
Be sure system resources are not being exceeded. The maximum
number of Exchange blocks per CPM is 32. Contact technical
assistance.

2047

Name: PCCC Error
Cause: User initialy configured large number of Number Of Values and
made them visible. Then, user changed Number Of Values to a
smaller number than the visible pins.
Corrective
Action:
User must re-configure original large number of Number Of Values
and remove any extra pins.

2048

Name: PCCC Error
Cause: Hardware Fault.
Corrective
Action:


2089

Name: PCCC Error
Cause: User has tried to configure more than the maximum number of
parameter connectors on this Control Module (CM). The maximum
number is 1000 per CM.
Corrective
Action:
Reduce number of parameter connectors per CM.

Fault Codes
Exchange Block ERRCODE Fault Codes
86 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
2304

Name: PCCC Error
Cause: Cant find address in routing table.
Corrective
Action:


2560

Name: PCCC Error
Cause: Illegal LSAP value.
Corrective
Action:


4096

Name: PCCC Error
Cause: Illegal command or format.
For example, addressing file 13 that does not exist, will generate this
error. Or, addressing a file as N7:0 but the file is a Bit file, will
genterate this error..
Corrective
Action:
Change command or format.

8192

Name: PCCC Error
Cause: Node has a problem and will not communicate.
Corrective
Action:


Fault Codes
Exchange Block ERRCODE Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 87
1/03 Honeywell Part I
12288

Name: PCCC Error
Cause: Remote node is not there, disconnected or shutdown.
Corrective
Action:


16384

Name: PCCC Error
Cause: Node could not complete function due to hardware fault.
Corrective
Action:


20480

Name: PCCC Error
Cause: Addressing problem or memory protect rungs.
Corrective
Action:


24576

Name: PCCC Error
Cause: Function disallowed due to command protection selection.
Corrective
Action:


28672

Name: PCCC Error
Cause: Processor is in program mode.
Corrective
Action:


Fault Codes
Exchange Block ERRCODE Fault Codes
88 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
32768

Name: PCCC Error
Cause: Compatibility mode file missing or communication zone problem.
Corrective
Action:


36864

Name: PCCC Error
Cause: Remote node cannot buffer command.
Corrective
Action:


45056

Name: PCCC Error
Cause: Remote node problem, due to download.
Corrective
Action:


49152

Name: PCCC Error
Cause: Cannot execute command, due to active IPBs.
Corrective
Action:


53248

Name: PCCC Error
Cause: Cannot route request.
Corrective
Action:


Fault Codes
Exchange Block ERRCODE Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 89
1/03 Honeywell Part I
61441

Name: PCCC Error
Cause: Illegal Data Table Address Format. A field has an illegal value.
Corrective
Action:
Check the FILENAME parameter to see if it is a valid PLC-5 Data
Table Address and that it refers to a valid location in the target
device. The end address (which is determined using the PLC-5 Data
Table Address in FILENAME and the number of elements to
read/write) must not be beyond the end of the file. Also verify that
the array block is not being used to access a file of an unsupported
type.

61442

Name: PCCC Error
Cause: Illegal Data Table Address Format. Not enough fields specified.
Corrective
Action:
Check the FILENAME parameter to see if it is a valid PLC-5 Data
Table Address and that it refers to a valid location in the target
device. The end address (which is determined using the PLC-5 Data
Table Address in FILENAME and the number of elements to
read/write) must not be beyond the end of the file. Also verify that
the array block is not being used to access a file of an unsupported
type.

61443

Name: PCCC Error
Cause: Illegal Data Table Address Format. Too many fields specified.
Corrective
Action:
Check the FILENAME parameter to see if it is a valid PLC-5 Data
Table Address and that it refers to a valid location in the target
device. The end address (which is determined using the PLC-5 Data
Table Address in FILENAME and the number of elements to
read/write) must not be beyond the end of the file. Also verify that
the array block is not being used to access a file of an unsupported
type.

Fault Codes
Exchange Block ERRCODE Fault Codes
90 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
61444

Name: PCCC Error
Cause: Illegal Data Table Address Format. Symbol not found.
Corrective
Action:
Check type.

61445

Name: PCCC Error
Cause: Illegal Data Table Address Format. Symbol is zero or greater than
the number of characters supported by the target device.
Corrective
Action:
Check the FILENAME parameter to see if it is a valid PLC-5 Data
Table Address and that it refers to a valid location in the target
device. The end address (which is determined using the PLC-5 Data
Table Address in FILENAME and the number of elements to
read/write) must not be beyond the end of the file. Also verify that
the array block is not being used to access a file of an unsupported
type.

61446

Name: PCCC Error
Cause: Illegal Address. Address does not exist, or does not point to
something usable by this command.
Corrective
Action:
Check the FILENAME parameter to see if it is a valid PLC-5 Data
Table Address and that it refers to a valid location in the target
device. The end address (which is determined using the PLC-5 Data
Table Address in FILENAME and the number of elements to
read/write) must not be beyond the end of the file. Also verify that
the array block is not being used to access a file of an unsupported
type.

Fault Codes
Exchange Block ERRCODE Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 91
1/03 Honeywell Part I
61447

Name: PCCC Error:
Cause: Illegal size. File is wrong size. Address is past end of file.
Corrective
Action:
Check the FILENAME parameter to see if it is a valid PLC-5 Data
Table Address and that it refers to a valid location in the target
device. The end address (which is determined using the PLC-5 Data
Table Address in FILENAME and the number of elements to
read/write) must not be beyond the end of the file. Also verify that
the array block is not being used to access a file of an unsupported
type.

61448

Name: PCCC Error
Cause: Cannot complete request.Situation changed (file size, for example)
during operation.
Corrective
Action:


61449

Name: PCCC Error:
Cause: Data or file too large. Memory is unavailable.
Corrective
Action:


61450

Name: PCCC Error:
Cause: Request is too large. Transaction size plus word address is too
large.
Corrective
Action:


Fault Codes
Exchange Block ERRCODE Fault Codes
92 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
61451

Name: PCCC Error
Cause: Access is denied, privilege violation.
Corrective
Action:


61452

Name: PCCC Error
Cause: Resource is not available. Condition cannot be generated.
Corrective
Action:


61453

Name: PCCC Error
Cause: Resource is already available. Condition already exists.
Corrective
Action:


61454

Name: PCCC Error
Cause: Command cannot be executed.
Corrective
Action:


61455

Name: PCCC Error:
Cause: Overflow. Histogram overflow.
Corrective
Action:


Fault Codes
Exchange Block ERRCODE Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 93
1/03 Honeywell Part I
61456

Name: PCCC Error
Cause: No access.
Corrective
Action:


61457

Name: PCCC Error
Cause: Illegal data type information.
Corrective
Action:
Verify that the array block is not being used to access a file of an
unsupported type.

61458

Name: PCCC Error:
Cause: Invalid parameter. Invalid data in search or command block.
Corrective
Action:


61459

Name: PCCC Error
Cause: Address reference exists to deleted area.
Corrective
Action:


61460

Name: PCCC Error
Cause: Command execution failure for unknown reason.
Corrective
Action:


Fault Codes
Exchange Block ERRCODE Fault Codes
94 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
61461

Name: PCCC Error
Cause: Data conversion error.
Corrective
Action:


61462

Name: PCCC Error
Cause: The scanner is not able to communicate with a 1771 rack adapter.
Corrective
Action:
This could be due to the scanner not scanning, the selected adapter
not being scanned, the adapter not responding, or an invalid
request.

61463

Name: PCCC Error
Cause: The adapter is not able to communicate with the module.
Corrective
Action:


61464

Name: PCCC Error
Cause: The 1771 module response was not valid (size, checksum, etc.).
Corrective
Action:


Fault Codes
Exchange Block ERRCODE Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 95
1/03 Honeywell Part I
61465

Name: PCCC Error
Cause: Duplicated Label.
Corrective
Action:


61466

Name: PCCC Error
Cause: File is open another node owns it.
Corrective
Action:


61467

Name: PCCC Error
Cause: Another node is the program owner.
Corrective
Action:


61468

Name: PCCC Error
Cause: Disk file is write protected or otherwise inaccessible.
Corrective
Action:


61469

Name: PCCC Error
Cause: Disk file is being used by another application, update not performed.
Corrective
Action:


Fault Codes
Exchange Block ERRCODE Fault Codes
96 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
61470

Name: PCCC Error
Cause: Data Table Element Protection violation.
Corrective
Action:


61471

Name: PCCC Error
Cause: Unable to execute command due to a temporary internal condition in
the target device.
Corrective
Action:


Fault Codes
I/O Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 97
1/03 Honeywell Part I
I/O Fault Codes
TC-ODX081 Discrete AC Output Module
As indicated in the following table, the TC-ODX081 Discrete AC Output Module
provides enhanced output diagnostics for each output channel (Fault Conditions), and
channel fault indication on the module front panel and on Station displays (Fault
Indications)

Faults Description
Fault Conditions
Short Circuit
Protection/Overload
Protects the device from damage by sensing when current draw for
a given channel is above the limit.
Loss of Field Power Senses lack of power for a channel, if zero crossing on the ac-line
power is not detected which causes the output state to change.
No Load Detected Senses when the output current draw falls below the threshold or
when a hardware output failure occurs (No load is detected on this
channel).
NOTE: Detection only works when the output is in the OFF state.
Output Verification Verifies if the actual output state matches the commanded output
state for field side verification.
NOTE: Verification only works when the output is in the ON state.
Pulse Test Periodically checks the output to verify that it still has the ability to
change states without causing the load to transition.
NOTE: This function only operates in systems with software version
R120 or greater.
Fault Indications
I/O Module front panel A red number will indicate the channel(s) with the fault condition. To
determine the actual fault, call up the Station Detail display for the
I/O Module.
Station Alarm
Summary display
The Alarm Summary display will indicate the fault condition type and
time that the fault occurred.
NOTE: To determine the actual fault, call up the Station Detail
display for the I/O Module.
Station Detail display The Detail will show the status of each output Channel.
Fault Codes
RM Fault Codes
98 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03

RM Fault Codes
About fault code format
The fault code is a 4 character alphanumeric string. Valid characters are [0-9,A-Z],
except [S, O]. The first character is always E. The second character indicates the
subsystem in which the error was detected. The third character indicates the subsystem
function or group of functions in which the error was detected. The fourth character
enumerates the specific error.
Each subsystem within the RM is assigned a range of fault codes as listed in the
following table.

Range Object Firmware Directory
E 0 _ _ Backup Control Object /bcoObj
E 1 _ _ OS Board Support Package /bsp1.1
E 2 _ _ Chassis Profile Object /chpObj
E 3 _ _ Coordinated System Time Object /cstObj
E 4 _ _ Device Object /devObj
E 5 _ _ Extended Device Object /edoObj
E 6 _ _ Event Log Object /eloObj
E 7 _ _ Backup Communications Object /iSBMcomm
E 8 _ _ ICP toolkit /icptk
E 9 _ _ Indicator Device Driver /ind
E A _ _ RM State Machine (JABBA) /jabba
E B _ _ Event Log Device Driver /ogDrv
E C _ _ Object Communications /objComm
E D _ _ Wall Clock Time Object /wctObj
E E _ _ Non-Maskable Interrupt Service Routine /nmiIsr
E F _ _ Non-Volatile Storage Object /nvsObj
Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 99
1/03 Honeywell Part I
Range Object Firmware Directory
E G _ _ RM Fault Handler /rmFault
E H _ _ Self Test Object /stObj
E I _ _ Workstation Display Object /wdObj
E J _ _ Industrial Control Platform Object /icpObj
E K _ _ RM Watchdog Manager /dog

A solid red OK LED on any module is a sign of total shutdown/failure (or in process or
faulted startup self testing). A RM displaying an Exxx code is a sign of an RM failure,
including a sign of an RM's inability to resolve a chassis condition without user
intervention. For example, an E054 code is a signal that the RM has lost contact with
another chassis module, but the RM still sees that module as present in the chassis
through other back plane signals.
E000

Description: Unable to initialize attributes from the configuration log.
Cause: An errno value returned from bcoUpdateAttributes.
Corrective
Action:
Reset RM (RM_CA02). If error persists, replace RM (RM_CA01).

E001

Description: Unable to register class with ICP Toolkit.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
100 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E010

Description: Unable to post event to message queue.
Cause: An errno value returned from msgQSend.
An event which was to be posted.
Corrective
Action:
Reset the RM, go to RM_CA02.

E020

Description: Unable to read from incoming event message queue.
Cause: An errno value returned from msgQReceive.
Corrective
Action:
Reset the RM, go to RM_CA02.

E021

Description: RM is in invalid state to perform a chassis state change with the
partner going first
Cause: A new state requested.
Corrective
Action:
Reset the RM, go to RM_CA02.

E022

Description: Invalid value for state change coordination order.
Cause: State change coordination order.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 101
1/03 Honeywell Part I
E023

Description: Unable to start watchdog timer used to wait for switchover phasing
to complete.
Cause: An errno value returned from wdStart.
Corrective
Action:
Reset the RM, go to RM_CA02.

E024

Description: Invalid event sent to the backup control object.
Cause: Event type.
Corrective
Action:
Reset the RM, go to RM_CA02.

E025

Description: Unable to update attributes from the configuration log.
Cause: An errno value returned from bcoUpdateAttributes.
Corrective
Action:
Reset (RM_CA02) or replace (RM_CA01) RM when convenient.

E026

Description: Unable to write display position to configuration log.
Cause: An errno value returned from cfgWriteDisplayPosition.
Corrective
Action:
Reset (RM_CA02) or replace (RM_CA01) RM when convenient.

Fault Codes
RM Fault Codes
102 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E027

Description: Invalid service state parameter for coordinated state change (last
chassis).
Cause: Service state parameter.
Corrective
Action:
Reset the RM, go to RM_CA02.

E028

Description: Invalid service state parameter for coordinated state change (first
chassis).
Cause: Service state parameter.
Corrective
Action:
Reset the RM, go to RM_CA02.

E029

Description: Invalid coordinated state change state.
Cause: Coordinated state change state.
Corrective
Action:
Reset the RM, go to RM_CA02.

E02A

Description: Invalid multicast service state parameter.
Cause: State parameter.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 103
1/03 Honeywell Part I
E02B

Description: Invalid coordinated state change state reached.
Cause: State of coordinated state change.
Corrective
Action:
Reset the RM, go to RM_CA02.

E02C

Description: Invalid multicast service state parameter.
Cause: State parameter.
Corrective
Action:
Reset the RM, go to RM_CA02.

E02D

Description: Unable to start watchdog timer used to time the chassis state
change.
Cause: An errno value returned from wdStart.
Corrective
Action:
Reset the RM, go to RM_CA02.

E030

Description: Unable to update attributes from the configuration log.
Cause: An errno value returned from bcoUpdateAttributes.
Corrective
Action:
Reset (RM_CA02) or replace (RM_CA01) RM when convenient.

Fault Codes
RM Fault Codes
104 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E031

Description: Unable to open module to RM portion of multicast connection.
Cause:
Corrective
Action:
None.

E032

Description: The slot number value for a module opening module to RM portion
of multicast connection exceeds largest possible slot number.
Cause:
Corrective
Action:
None.

E033

Description: Unable to open module to RM portion of multicast connection.
Cause:
Corrective
Action:
None.

E034

Description: The slot number value for a module opening module to RM portion
of multicast connection exceeds largest possible slot number.
Cause:
Corrective
Action:
None.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 105
1/03 Honeywell Part I
E035

Description: Unable to open connection made to the backup control object from
another module (not the multicast connection).
Cause:
Corrective
Action:
None.

E036

Description: Unable to close connection made to the backup control object from
another module.
Cause: An errno value returned from objCommTargClose.
Corrective
Action:
None.

E037

Description: Unable to send message to the backup control object event handler
message queue.
Cause: An errno value returned from msgQSend.
Corrective
Action:
Reset the RM, go to RM_CA02.

E038

Description: Unknown state change request from partner RM.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
106 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E039

Description: Unable to allocate a response buffer for a state change request
service.
Cause:
Corrective
Action:
None.

E03A

Description: The response routine was NULL for the state change request
service.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E03a

Description: Buffer could not be allocated for Fwd_Close_Reply on multicast
connection.
Cause:
Corrective
Action:
None.

E03B

Description: Unable to prepare response buffer for initiate qualification service
request.
Cause:
Corrective
Action:
None.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 107
1/03 Honeywell Part I
E03b

Description: There is no specified response routine to which to forward the
Fwd_Close_Reply buffer.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E03C

Description: The response routine was NULL for the initiate qualification service
request.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E03D

Description: Unable to prepare response buffer for the initiate switchover service
request.
Cause:
Corrective
Action:
None.

E03E

Description: The response routine was NULL for the initiate switchover service
request.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
108 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E03F

Description: Unable to start watchdog timer used to delay switchover request.
Cause: An errno value returned from wdStart.
Corrective
Action:
Reset the RM, go to RM_CA02.

E03G

Description: Unable to prepare response buffer for the coordinated switchover
service request.
Cause:
Corrective
Action:
None.

E03H

Description: The response routine was NULL for the coordinated switchover
service request.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E03I

Description: Unable to prepare response buffer for the report event service
request.
Cause:
Corrective
Action:
None.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 109
1/03 Honeywell Part I
E03J

Description: The response routine was NULL for the report event service
request.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E03K

Description: Unable to prepare response buffer for the become primary service
request.
Cause:
Corrective
Action:
None.

E03L

Description: The response routine was NULL for the become primary service
request.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E03M

Description: Unable to start watchdog timer used to delay become primary
request.
Cause: An errno value returned from wdStart.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
110 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E03N

Description: Unable to prepare response buffer for the disqualify secondary
service request.
Cause:
Corrective
Action:
None.

E03P

Description: Unable to send message to the backup control object event handler
message queue.
Cause: An errno value returned from msgQSend.
Corrective
Action:
Reset the RM, go to RM_CA02.

E03Q

Description: Unable to send message to the delayed service request handler
message queue.
Cause: An errno value returned from msgQSend.
Corrective
Action:
None.

E03R

Description: Unable to send message to the delayed service request handler
message queue.
Cause: An errno value returned from msgQSend.
Corrective
Action:
None.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 111
1/03 Honeywell Part I
E03T

Description: Unable to send message to the backup control object event handler
message queue.
Cause: An errno value returned from msgQSend.
Corrective
Action:
Reset the RM, go to RM_CA02.

E03U

Description: The response routine was NULL for the disqualify secondary service
request
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E03V

Description: Unable to send message to the delayed service request handler
message queue.
Cause: An errno value returned from msgQSend.
Corrective
Action:
None.

E03W

Description: The appTable indicates that connection being closed uses non-ICP
(Industrial Control Platform) Port.
Cause: bcoObjTargAppHandle.
appTable[bcoObjTargAppHandle].port
Corrective
Action:
None.

Fault Codes
RM Fault Codes
112 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E03X

Description: The bcoLinkConsumerTable indicates that connection has already
been closed
Cause: UcmmReceiveSlotNum (slot in which module closing
connection resides).
bcoLinkConsumerTable[ucmmReceiveSlotNum].
Corrective
Action:
None.

E03Y

Description: Link consumer could not be freed (does not exist)
Cause: UcmmReceiveSlotNum (slot in which module closing
connection resides).
bcoLinkConsumerTable[ucmmReceiveSlotNum].
Corrective
Action:
None.

E03Z

Description: Transport could not be restarted following removal of link consumer.
Cause:
Corrective
Action:
None.

E040

Description: Unable to write autoqualification state to the configuration log.
Cause:
Corrective
Action:
Reset ( RM_CA02) or replace the RM (RM_CA01).

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 113
1/03 Honeywell Part I
E041

Description: Unable to write autoqualification option to the configuration log.
Cause:
Corrective
Action:
Reset ( RM_CA02) or replace the RM (RM_CA01).

E042

Description: Unable to prepare response buffer for set single attribute service
request (autoqualification option attribute).
Cause:
Corrective
Action:
None.

E043

Description: The response routine was NULL for set single attribute service
request (autoqualification option attribute).
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E044

Description: Unable to write program command recognition attribute to the
configuration log.
Cause:
Corrective
Action:
Reset ( RM_CA02) or replace the RM (RM_CA01)..

Fault Codes
RM Fault Codes
114 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E045

Description: Unable to prepare response buffer for set single attribute service
request (program command recognition attribute).
Cause:
Corrective
Action:
None.

E046

Description: The response routine was NULL for set single attribute service
request (program command recognition attribute).
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E047

Description: Unable to prepare response buffer for set single attribute service
request (password scope attribute).
Cause:
Corrective
Action:
None.

E048

Description: The response routine was NULL for set single attribute service
request (password scope attribute).
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 115
1/03 Honeywell Part I
E049

Description: Unable to write display position attribute to the configuration log.
Cause:
Corrective
Action:
Reset ( RM_CA02) or replace the RM (RM_CA01).

E04A

Description: Unable to prepare response buffer for set single attribute service
request (display position attribute).
Cause:
Corrective
Action:
None.

E04B

Description: The response routine was NULL for set single attribute service
request (display position attribute).
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E04C

Description: Unable to write autoqualification state to the configuration log.
Cause:
Corrective
Action:
Reset ( RM_CA02) or replace the RM (RM_CA01).

Fault Codes
RM Fault Codes
116 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E04D

Description: Unable to write autoqualification state to the configuration log.
Cause:
Corrective
Action:
Reset ( RM_CA02) or replace the RM (RM_CA01).

E050

Description: An invalid port number has been associated with the multicast
connection.
Cause:
Corrective
Action:
None.

E051

Description: Attempting to delete a link consumer which has already been
deleted (or never allocated).
Cause:
Corrective
Action:
None.

E052

Description: Unable to delete link consumer.
Cause:
Corrective
Action:
None.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 117
1/03 Honeywell Part I
E053

Description: Unable to restart server transport for multicast connection after one
of the link consumers timed-out.
Cause:
Corrective
Action:
None.

E054

Description: Unable to restart server transport for multicast connection after one
of the link consumers timed-out.
The RM requires operator assistance. It has encountered a situation
where another chassis module is not responding to Redundancy
status queries but is still responding to low level backplane queries.
This error can occur anytime after the RM completes Startup Self
Test.
If this RM was hosting a Primary with a Synchronized Secondary, a
switchover will occur.
If this RM was hosting a Synchronized Secondary, all other
functional chassis modules will enter a Disqualified Secondary state.
Cause: Bitmap of redundancy compliant modules in chassis
(determined by pinging).
Slot number of module not responding, but the module is still
responding to low level backplane interface queries
("pings").
Corrective
Action:
Reset offending module and the RM.
If the identity of the other module is not obvious from displays or
chassis indicators, see the RM Event Log, where and E054 fault
should be recorded. The Data 2 field of that event record will specify
the slot number of the module that triggered the fault.
Go to RM_CA02.

Fault Codes
RM Fault Codes
118 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E060

Description: Invalid event received on connection.
Cause: Event received.
Corrective
Action:
None.

E07A

Description: Invalid multicast service state parameter.
Cause: State parameter.
Corrective
Action:
Reset the RM, go to RM_CA02.

E070

Description: Invalid multicast service state parameter.
Cause: State parameter.
Corrective
Action:
Reset the RM, go to RM_CA02.

E071

Description: Invalid coordinated state change state reached.
Cause: State parameter.
Corrective
Action:
Reset the RM, go to RM_CA02.

E072

Description: Invalid multicast service state parameter.
Cause: State parameter.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 119
1/03 Honeywell Part I
E073

Description: Unknown error code received.
Cause: Error code.
Corrective
Action:
None.

E074

Description: Unknown extended error code received.
Cause: Extended error code.
Corrective
Action:
None.

E075

Description: Invalid extended error size.
Cause: Extended error size.
Corrective
Action:
None.

E076

Description: Unknown error code received..
Cause: Error code.
Corrective
Action:
None.

E077

Description: Invalid service response code received.
Cause: Service response code.
Corrective
Action:
None.

Fault Codes
RM Fault Codes
120 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E078

Description: Invalid multicast service state parameter.
Cause: State parameter.
Corrective
Action:
Reset the RM, go to RM_CA02.

E079

Description: Invalid coordinated state change state reached.
Cause: State of coordinated state change.
Corrective
Action:
Reset the RM, go to RM_CA02.

E080

Description: Invalid service parameter for qualifcation service response.
Cause: Service parameter.
Corrective
Action:
None.

E090

Description: Invalid service state parameter for coordinated state change (last
chassis).
Cause: Service state parameter.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 121
1/03 Honeywell Part I
E091

Description: Invalid service state parameter for coordinated state change (first
chassis).
Cause: Service state parameter.
Corrective
Action:
Reset the RM, go to RM_CA02.

E092

Description: Invalid coordinated state change state.
Cause: Coordinated state change state.
Corrective
Action:
Reset the RM, go to RM_CA02.

E093

Description: Invalid multicast service state.
Cause: Multicast service state.
Corrective
Action:
Reset the RM, go to RM_CA02.

E0A0

Description: New state is invalid.
Cause: New state.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
122 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E0A1

Description: New state is invalid (for last chassis coordinated state change state).
Cause: New state.
Corrective
Action:
Reset the RM, go to RM_CA02.

E0A2

Description: New state is invalid (for first chassis coordinated state change
state).
Cause: New state.
Corrective
Action:
Reset the RM, go to RM_CA02.

E0A3

Description: Invalid coordinated state change state.
Cause: Coordinated state change state.
Corrective
Action:
Reset the RM, go to RM_CA02.

E0A4

Description: New state is invalid (for last chassis coordinated state change state).
Cause: New state.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 123
1/03 Honeywell Part I
E0A5

Description: New state is invalid (for first chassis coordinated state change
state).
Cause: New state.
Corrective
Action:
Reset the RM, go to RM_CA02.

E0A6

Description: Invalid coordinated state change state.
Cause: Coordinated state change state.
Corrective
Action:
Reset the RM, go to RM_CA02.

E0A7

Description: Status of multicast connection makes it impossible to send state
notification.
Cause: Status of multicast connection.
Corrective
Action:
Reset the RM, go to RM_CA02.

E0A8

Description: Unable to start watchdog timer used to time the chassis state
change.
Cause: An errno value returned from wdStart.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
124 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E0B0

Description: Invalid qualification trigger value.
Cause: Trigger value.
Corrective
Action:
Reset the RM, go to RM_CA02.

E0B1

Description: Invalid new phase value.
Cause: New phase value.
Corrective
Action:
None.

E0B2

Description: Status of multicast connection makes it impossible to send
qualification request.
Cause: Status of multicast connection.
Corrective
Action:
Reset the RM, go to RM_CA02.

E0C0

Description: Unable to close unconnected message manager resource (after
unsuccessful send).
Cause: Service request being made.
First service request parameter.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 125
1/03 Honeywell Part I
E0C1

Description: Unable to close unconnected message manager resource (after
successful send and response).
Cause: Service request being made.
First service request parameter.
Corrective
Action:
Reset the RM, go to RM_CA02.

E0C2

Description: Unable to close unconnected message manager resource (after
maximum retries reached).
Cause: Service request being made.
First service request parameter.
Corrective
Action:
Reset the RM, go to RM_CA02.

E0C3

Description: Unable to close unconnected message manager resource (after
unsuccessful send and unsuccessful attempt to recycle the resource
for a retry).
Cause: Service request being made.
First service request parameter.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
126 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E0C4

Description: Unable to close unconnected message manager resource (after an
invalid internal state has been reached).
Cause: Service request being made.
First service request parameter.
Corrective
Action:
Reset the RM, go to RM_CA02.

E0C5

Description: Unable to take semaphore for sending partner service request.
Cause: An errno value returned from semTake.
Corrective
Action:
Reset the RM, go to RM_CA02.

E0D0

Description: Unsuccessful response status received. RM's Backup Control
Object experienced a timeout of an unconnected message to its
partner RM.
Cause: Response handle.
Response status.
Real or apparent Redundancy Cable disconnection.
Corrective
Action:
None.

E0D1

Description: Invalid response data size for get single attribute request.
Cause: Data size received.
Corrective
Action:
None

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 127
1/03 Honeywell Part I
E0D2

Description: Invalid response service for get single attribute request.
Cause: Response service code.
Corrective
Action:
None

E0D3

Description: Get single attribute request was unsuccessful.
Cause: Response general status code.
Corrective
Action:
None

E0D4

Description: Invalid partner state returned in get single attribute request.
Cause: Partner state.
Corrective
Action:
Reset the RM, go to RM_CA02.

E0D5

Description: Invalid response data size for coordinated state change request.
Cause: Data size received.
Corrective
Action:
None.

E0D6

Description: Invalid response service for coordinated state change request.
Cause: Response service code.
Corrective
Action:
None.

Fault Codes
RM Fault Codes
128 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E0D7

Description: Coordinated state change request was unsuccessful.
Cause: Response general status code.
Corrective
Action:
None.

E0D8

Description: Invalid response data size for coordinated switchover request.
Cause: Data size received.
Corrective
Action:
None.

E0D9

Description: Invalid response service for coordinated switchover request.
Cause: Response service code.
Corrective
Action:
None.

E0DA

Description: Coordinated switchover request was unsuccessful.
Cause: Response general status code.
Corrective
Action:
None.

E0DB

Description: An invalid coordinated switchover state has been reached.
Cause: Coordinated switchover state.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 129
1/03 Honeywell Part I
E0DC

Description: Invalid service request response receieved.
Cause: Response handle.
Corrective
Action:
Reset the RM, go to RM_CA02.

E0E0

Description: New switchover phase is invalid.
Cause: New switchover phase.
Corrective
Action:
Reset the RM, go to RM_CA02.

E0E1

Description: Status of multicast connection makes it impossible to send
switchover request.
Cause: Status of multicast connection.
Corrective
Action:
Reset the RM, go to RM_CA02.

E0E2

Description: The ICP ASIC timer interrupt is not working properly.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
130 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E0F0

Description: Invalid parameter for service request being delayed.
Cause: Service request being delayed.
Corrective
Action:
Reset the RM, go to RM_CA02.

E0G0

Description: Invalid new state requested.
Cause: New state value.
Corrective
Action:
Reset the RM, go to RM_CA02.

E0H0

Description: Unable to update attributes from configuration log.
Cause: An errno value returned by bcoUpdateAttributes.
Corrective
Action:
Reset ( RM_CA02) or replace the RM (RM_CA01).

E0I0

Description: Tried to send more than one request at a time to the partner RM.
Cause: Service request number of offending service.
First service parameter.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 131
1/03 Honeywell Part I
E0I1

Description: Out of necessary resources to send partner request.
Cause: Service request number.
First service parameter
Corrective
Action:
Reset the RM, go to RM_CA02.

E0I2

Description: Invalid service request.
Cause: Service request number.
First service parameter
Corrective
Action:
Reset the RM, go to RM_CA02.

E0I3

Description: Invalid response state during request.
Cause: Service request number.
First service parameter
Corrective
Action:
Reset the RM, go to RM_CA02.

E0I4

Description: No client resources available to send request.
Cause: Service request number.
First service parameter
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
132 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E0I5

Description: No receive descriptor available for the response.
Cause: Service request number.
First service parameter
Corrective
Action:
Reset the RM, go to RM_CA02.

E0I6

Description: No transmit descriptor available for the request.
Cause: Service request number.
First service parameter
Corrective
Action:
Reset the RM, go to RM_CA02.

E0I7

Description: No combuf available for the response.
Cause: Service request number.
First service parameter
Corrective
Action:
Reset the RM, go to RM_CA02.

E0I8

Description: A bad unconnected message manager handle was used.
Cause: Service request number.
First service parameter
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 133
1/03 Honeywell Part I
E0I9

Description: A transmit was already in progress for the unconnected message
manager..
Cause: Service request number.
First service parameter
Corrective
Action:
Reset the RM, go to RM_CA02.

E0IA

Description: An operating system error occured.
Cause: Service request number.
First service parameter
Corrective
Action:
Reset the RM, go to RM_CA02.

E0IB

Description: No longer connected to the partner RM.
Cause: Service request number.
First service parameter
Corrective
Action:
None.

E0IC

Description: An invalid service request was made.
Cause: Service request number.
First service parameter
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
134 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E0ID

Description: Maximum retries exceeded.
Cause: Service request number.
First service parameter
Real or apparent Redundancy cable disconnection.
Corrective
Action:
Reset the RM, go to RM_CA02.

E0IE

Description: The private link transmit queue is full.
Cause: Service request number.
First service parameter
Corrective
Action:
Reset the RM, go to RM_CA02.

E0IF

Description: The unconnected message manager being used was receiving data
unexpectedly.
Cause: Service request number.
First service parameter
Corrective
Action:
Reset the RM, go to RM_CA02.

E0IG

Description: An undefined errno value was encountered.
Cause: An errno value.
Service request number.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 135
1/03 Honeywell Part I
E0J0

Description: Error taking a semaphore for access to data structures for
forwarding report events services to the partner RM.
Cause: An errno value.
Service request number.
Corrective
Action:
Reset the RM, go to RM_CA02.

E101

Description: Unable to initialize indicator device driver.
Cause: An errno value returned from indDrv.
Corrective
Action:
Reset the RM, go to RM_CA02.

E102

Description: Unable to create /display device (4 character display).
Cause: An errno value returned from indDevCreate.
Corrective
Action:
Reset the RM, go to RM_CA02.

E103

Description: Unable to create /commLed device.
Cause: An errno value returned from indDevCreate.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
136 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E104

Description: Unable to create /healthLed device.
Cause: An errno value returned from indDevCreate.
Corrective
Action:
Reset the RM, go to RM_CA02.

E105

Description: Unable to create /priLed device.
Cause: An errno value returned from indDevCreate.
Corrective
Action:
Reset the RM, go to RM_CA02.

E106

Description: Unable to create /secLed device.
Cause: An errno value returned from indDevCreate.
Corrective
Action:
Reset the RM, go to RM_CA02.

E107

Description: Unable to create /relay device.
Cause: An errno value returned from indDevCreate.
Corrective
Action:
Reset the RM, go to RM_CA02.

E108

Description: Unable to initialize event log object.
Cause: An errno value returned from eloInit.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 137
1/03 Honeywell Part I
E109

Description: Unable to initialize coordinated system time object.
Cause: An errno value returned from cstInit.
Corrective
Action:
Reset the RM, go to RM_CA02.

E10A

Description: Unable to initialize wall clock time object.
Cause: An errno value returned from wctInit.
Corrective
Action:
Reset the RM, go to RM_CA02.

E10B

Description: Unable to initialize backup control object.
Cause: An errno value returned from bcoInit.
Corrective
Action:
Reset the RM, go to RM_CA02.

E10C

Description: Unable to initialize chassis profile object.
Cause: An errno value returned from chpInit.
Corrective
Action:
Reset the RM, go to RM_CA02.

E10D

Description: Unable to initialize device object.
Cause: An errno value returned from devInit.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
138 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E10E

Description: Unable to initialize extended device object.
Cause: An errno value returned from edoInit.
Corrective
Action:
Reset the RM, go to RM_CA02.

E10F

Description: Unable to initialize RM State machine.
Cause: An errno value returned from jbaInit.
Corrective
Action:
Reset the RM, go to RM_CA02.

E10G

Description: Unable to initialize backup communications object.
Cause: An errno value returned from bcInit.
Corrective
Action:
v

E10H

Description: Unable to initialize non-volatile storage object.
Cause: An errno value returned from nvsInit.
Corrective
Action:
Reset the RM, go to RM_CA02.

E10I

Description: Unable to initialize DF_FAIL event handler.
Cause: An errno value returned from nmiInit.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 139
1/03 Honeywell Part I
E10J

Description: Unable to initialize workstation display object.
Cause: An errno value returned from wdoInit.
Corrective
Action:
Reset the RM, go to RM_CA02.

E10K

Description: Unable to initialize self test object.
Cause: An errno value returned from stoInit.
Corrective
Action:
Reset the RM, go to RM_CA02.

E10L

Description: Unable to initialize watchdog manager.
Cause: An errno value returned from dogInit.
Corrective
Action:
Reset the RM, go to RM_CA02.

E10M

Description: Unable to initialize display task.
Cause: Unable to initialize display task.
Corrective
Action:
Reset the RM, go to RM_CA02.

E10N

Description: Unable to initialize ICP object.
Cause: An errno value returned from icpObjInit.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
140 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E10P

Description: Unable to post event to device object for displaying BOOT when
running in boot mode.
Cause: An errno value returned from devEventPost.
Corrective
Action:
Reset the RM, go to RM_CA02.

E201

Description: Error collecting redundancy attribute data from all existing modules.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E202

Description: Error collected device attribute data from all existing modules.
Cause:
Corrective
Action:
None.

E203

Description: Error collecting redundancy attribute data from all existing modules.
Cause:
Corrective
Action:
None.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 141
1/03 Honeywell Part I
E204

Description: Error collected device attribute data from all existing modules.
Cause:
Corrective
Action:
None.

E205

Description: Unable to start watchdog timer for collecting module data.
Cause: An errno value returned from wdStart.
Corrective
Action:
Reset the RM, go to RM_CA02.

E206

Description: Error collecting redundancy attribute data from all existing modules.
Cause:
Corrective
Action:
None.

E207

Description: Error collected device attribute data from all existing modules.
Cause:
Corrective
Action:
None.

E208

Description: Unable to start watchdog timer for collecting module data.
Cause: An errno value returned from wdStart.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
142 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E209

Description: Received a startup time value from a module which is greater than 3
minutes.
Cause: Startup time value received
Slot number from which the value was received
Corrective
Action:
Reset the RM, go to RM_CA02.

E20A

Description: Unable to update the chassis ID in all redundancy compliant
modules.
Cause:
Corrective
Action:
None.

E20B

Description: Unable to send partner present attribute to a specific module.
Cause: Slot number of module.
Corrective
Action:
None.

E20C

Description: Unable to get partner redundancy map when checking for a partner
module.
Cause: Slot number of module for which a partner is being checked.
Corrective
Action:
None.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 143
1/03 Honeywell Part I
E20D

Description: Unable to send partner present service to all redundancy compliant
modules that have a partner.
Cause:
Corrective
Action:
None.

E20E

Description: Unable to collect redundancy attribute data for a newly inserted
module.
Cause:
Corrective
Action:
None.

E20F

Description: Unable to collect device object attribute data for a newly inserted
module.
Cause:
Corrective
Action:
None.

E20G

Description: Unable to read the display position from the configuration log.
Cause:
Corrective
Action:
Reset ( RM_CA02) or replace the RM (RM_CA01).

Fault Codes
RM Fault Codes
144 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E20H

Description: Unable to notify newly inserted module of current chassis ID.
Cause:
Corrective
Action:
None.

E20I

Description: Unable to start watchdog timer to monitor for SYS_FAIL_L
deassertion.
Cause: An errno value returned from wdStart
Corrective
Action:
Reset the RM, go to RM_CA02.

E20J

Description: Unable to update the chassis ID in all redundancy compliant
modules.
Cause:
Corrective
Action:
None.

E20K

Description: Invalid event sent to the chassis profile object.
Cause: Invalid event number.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 145
1/03 Honeywell Part I
E20L

Description: Error reading message from message queue.
Cause: An errno value returned from msgQReceive.
Corrective
Action:
Reset the RM, go to RM_CA02.

E20M

Description: Error in stop service processing.
Cause: Stop service resulting state.
The slot number where stop service processing stopped.
Corrective
Action:
Non-redundant modules at the slot number or past the slot number
may have not been stopped.

E210

Description: Unable to allocate a response combuf.
Cause:
Corrective
Action:
None.

E211

Description: Response routine pointer is NULL.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
146 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E230

Description: Unable to close an unconnected message manager resource.
Cause: Service request.
First service request parameter.
Corrective
Action:
Reset the RM, go to RM_CA02.

E235

Description: Unable to close an unconnected message manager resource.
Cause: Service request.
First service request parameter.
Corrective
Action:
Reset the RM, go to RM_CA02.

E236

Description: Unable to close an unconnected message manager resource.
Cause: Service request.
First service request parameter.
Corrective
Action:
Reset the RM, go to RM_CA02.

E237

Description: Unable to close an unconnected message manager resource.
Cause: Service request.
First service request parameter.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 147
1/03 Honeywell Part I
E239

Description: Unable to close an unconnected message manager resource.
Cause: Service request.
First service request parameter.
Corrective
Action:
Reset the RM, go to RM_CA02.

E23B

Description: Unable to close an unconnected message manager resource.
Cause: Service request.
First service request parameter.
Corrective
Action:
Reset the RM, go to RM_CA02.

E250

Description: Unable to allocate combuf
Cause: Service request.
First service request parameter.
Corrective
Action:
None.

E251

Description: Unable to allocate unconnected message manager resource.
Cause:
Corrective
Action:
None.

Fault Codes
RM Fault Codes
148 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E252

Description: Unable to send unconnected request.
Cause:
Corrective
Action:
None.

E253

Description: Unable to close unconnected message manager resource.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E254

Description: Unable to close unconnected message manager resource.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E255

Description: Unable to close unconnected message manager resource.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E256

Description: Unable to close unconnected message manager resource.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 149
1/03 Honeywell Part I
E257

Description: Unable to close unconnected message manager resource.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E258

Description: Unable to close unconnected message manager resource.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E259

Description: Unable to close unconnected message manager resource.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E25A

Description: Unable to allocate combuf.
Cause:
Corrective
Action:
None.

E25B

Description: Unable to allocate unconnected message manager resource.
Cause:
Corrective
Action:
None.

Fault Codes
RM Fault Codes
150 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E25C

Description: Unable to send unconnected request.
Cause:
Corrective
Action:
None.

E25D

Description: Unable to close unconnected message manager resource.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E25E

Description: Unable to close unconnected message manager resource.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E25F

Description: Unable to close unconnected message manager resource.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E25G

Description: Unable to close unconnected message manager resource.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 151
1/03 Honeywell Part I
E25H

Description: Unable to close unconnected message manager resource.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E25I

Description: Unable to close unconnected message manager resource.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E25J

Description: Unable to close unconnected message manager resource.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E260

Description: Unable to allocate combuf.
Cause: Destination slot number.
Corrective
Action:
None.

Fault Codes
RM Fault Codes
152 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E261

Description: Unable to allocate unconnected message manager resource.
Cause: UCMM Handle.
Destination slot number.
Corrective
Action:
None.

E262

Description: Unable to send unconnected request.
Cause: UCMM Handle.
Destination slot number.
Corrective
Action:
None.

E263

Description: Unable to close unconnected message manager resource.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E264

Description: Unable to close unconnected message manager resource.
Cause: UCMM Handle.
Destination slot number.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 153
1/03 Honeywell Part I
E265

Description: Unable to close unconnected message manager resource.
Cause: UCMM Handle.
Destination slot number.
Corrective
Action:
Reset the RM, go to RM_CA02.

E266

Description: Retries exceeded trying to do primary capability check with module.
Cause: Destination slot number.
Corrective
Action:
None.

E267

Description: Unable to close unconnected message manager resource.
Cause: UCMM Handle.
Destination slot number.
Corrective
Action:
Reset the RM, go to RM_CA02.

E268

Description: Unable to close unconnected message manager resource.
Cause: UCMM Handle.
Destination slot number.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
154 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E269

Description: Unable to close unconnected message manager resource.
Cause: UCMM Handle.
Destination slot number.
Corrective
Action:
Reset the RM, go to RM_CA02.

E26A

Description: Invalid internal state reached.
Cause: Invalid state number.
Destination slot number.
Corrective
Action:
Reset the RM, go to RM_CA02.

E26B

Description: Unable to close unconnected message manager resource.
Cause: UCMM Handle.
Destination slot number.
Corrective
Action:
Reset the RM, go to RM_CA02.

E270

Description: Unable to collect redundancy attribute data.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 155
1/03 Honeywell Part I
E271

Description: Unable to collect device object attribute data.
Cause:
Corrective
Action:
None

E280

Description: Unable to allocate combuf.
Cause:
Corrective
Action:
None

E281

Description: Unable to allocate unconnected message manager resource.
Cause: UCMM Handle.
Destination slot number.
Corrective
Action:
None

E282

Description: Unable to send unconnected request.
Cause: UCMM Handle.
Destination slot number.
Corrective
Action:
None

Fault Codes
RM Fault Codes
156 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E283

Description: Unable to close unconnected message manager resource.
Cause: UCMM Handle.
Destination slot number.
Corrective
Action:
Reset the RM, go to RM_CA02.

E284

Description: Unable to close unconnected message manager resource.
Cause: UCMM Handle.
Destination slot number.
Corrective
Action:
Reset the RM, go to RM_CA02.

E285

Description: Unable to close unconnected message manager resource.
Cause: UCMM Handle.
Destination slot number.
Corrective
Action:
Reset the RM, go to RM_CA02.

E288

Description: Unable to close unconnected message manager resource.
Cause: UCMM Handle.
Destination slot number.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 157
1/03 Honeywell Part I
E289

Description: Unable to close unconnected message manager resource.
Cause: UCMM Handle.
Destination slot number.
Corrective
Action:
Reset the RM, go to RM_CA02.

E28A

Description: Unable to close unconnected message manager resource.
Cause: UCMM Handle.
Destination slot number.
Corrective
Action:
Reset the RM, go to RM_CA02.

E28B

Description: Retry to a module not communicating.
Cause: Destination slot number.
Corrective
Action:
None.

E28C

Description: Unable to close unconnected message manager resource.
Cause: UCMM Handle.
Destination slot number.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
158 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E28D

Description: Bad stop service state number.
Cause: Stop service state number.
Destination slot number.
Corrective
Action:
Reset the RM, go to RM_CA02.

E290

Description: Unable to allocate combuf.
Cause: Destination slot number.
Corrective
Action:
None.

E291

Description: Unable to allocate unconnected message manager resource.
Cause: UCMM Handle.
Destination slot number.
Corrective
Action:
None

E292

Description: Unable to send unconnected request.
Cause: UCMM Handle.
Destination slot number.
Corrective
Action:
None

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 159
1/03 Honeywell Part I
E293

Description: Unable to close unconnected message manager resource.
Cause: UCMM Handle.
Destination slot number.
Corrective
Action:
Reset the RM, go to RM_CA02.

E294

Description: Unable to close unconnected message manager resource.
Cause: UCMM Handle.
Destination slot number.
Corrective
Action:
Reset the RM, go to RM_CA02.

E295

Description: Unable to close unconnected message manager resource.
Cause: UCMM Handle.
Destination slot number.
Corrective
Action:
Reset the RM, go to RM_CA02.

E296

Description: Retries exceeded trying to send partner present service to module.
Cause: Destination slot number.
Corrective
Action:
None.

Fault Codes
RM Fault Codes
160 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E297

Description: Unable to close unconnected message manager resource.
Cause: UCMM Handle.
Destination slot number.
Corrective
Action:
Reset the RM, go to RM_CA02.

E298

Description: Unable to send partner present service to module.
Cause: Partner present state number.
Destination slot number.
Corrective
Action:
Reset the RM, go to RM_CA02.

E299

Description: Unable to close unconnected message manager resource.
Cause: UCMM Handle.
Destination slot number.
Corrective
Action:
Reset the RM, go to RM_CA02.

E2B0

Description: Unable to allocate combuf.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 161
1/03 Honeywell Part I
E2B1

Description: Not connected to partner RM.
Cause:
Corrective
Action:
None.

E2B2

Description: Resources not available for partner unconnected request.
Cause: An errno value returned from bcUcmmOpen.
Corrective
Action:
Reset the RM, go to RM_CA02.

E2B3

Description: Combuf not available for unconnected response.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E2B4

Description: Unknown errno value returned from bcUcmmOpen.
Cause: An errno value returned from bcUcmmOpen.
Corrective
Action:
Reset the RM, go to RM_CA02.

E2B5

Description: A bad handle was used for partner unconnected request.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
162 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E2B6

Description: Not connected to partner RM.
Cause:
Corrective
Action:
None.

E2B7

Description: An unconnected request for the unconnected resource is already in
progress.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E2B8

Description: An operating resource error occurred while trying to send unconnect
request.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E2B9

Description: The transmit queue is full for private link communications.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 163
1/03 Honeywell Part I
E2BA

Description: Unknown errno value returned from bcUcmmOpen.
Cause: An errno value returned from bcUcmmOpen.
Corrective
Action:
Reset the RM, go to RM_CA02.

E2BB

Description: Unable to close unconnected message manager resource.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E2BC

Description: Unable to close unconnected message manager resource.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E2BD

Description: Unable to close unconnected message manager resource.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E2BE

Description: Partner RM became disconnected during request.
Cause:
Corrective
Action:
None.

Fault Codes
RM Fault Codes
164 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E2BF

Description: Bad handle used when recycling unconnected message manager
resource.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E2BG

Description: Tried to recycle unconnected resource in the process of receiving a
response.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E2BH

Description: Not connected to partner RM while trying to recycle unconnected
resource.
Cause:
Corrective
Action:
None.

E2BI

Description: Unknown errno value returned from bcUcmmRecycle.
Cause: An errno value returned from bcUcmmRecycle.
Corrective
Action:
None.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 165
1/03 Honeywell Part I
E2BJ

Description: Unable to close unconnected message manager resource.
Cause: Handle of unconnected message manager resource.
Corrective
Action:
Reset the RM, go to RM_CA02.

E2BK

Description: Invalid internal state reached.
Cause: Invalid state value.
Corrective
Action:
Reset the RM, go to RM_CA02.

E2BL

Description: Unable to close unconnected message manager resource.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E2C0

Description: Unable to allocate combuf.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E2C1

Description: Not connected to partner RM.
Cause:
Corrective
Action:
None.

Fault Codes
RM Fault Codes
166 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E2C2

Description: Resources not available for partner unconnected request.
Cause: An errno value returned from bcUcmmOpen.
Corrective
Action:
Reset the RM, go to RM_CA02.

E2C3

Description: Combuf not available for unconnected response.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E2C4

Description: Unknown errno value returned from bcUcmmOpen.
Cause: An errno value returned from bcUcmmOpen.
Corrective
Action:
Reset the RM, go to RM_CA02.

E2C5

Description: A bad handle was used for partner unconnected request.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E2C6

Description: Not connected to partner RM.
Cause:
Corrective
Action:
None.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 167
1/03 Honeywell Part I
E2C7

Description: An unconnected request for the unconnected resource is already in
progress.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E2C8

Description: An operating resource error occurred while trying to send unconnect
request.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E2C9

Description: The transmit queue is full for private link communications.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E2CA

Description: Unknown errno value returned from bcUcmmOpen.
Cause: An errno value returned from bcUcmmOpen.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
168 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E2CB

Description: Unable to close unconnected message manager resource.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E2CC

Description: Unable to close unconnected message manager resource.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E2CD

Description: Unable to close unconnected message manager resource.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E2CE

Description: Partner RM became disconnected during request.
Cause:
Corrective
Action:
None.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 169
1/03 Honeywell Part I
E2CF

Description: Bad handle used when recycling unconnected message manager
resource.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E2CG

Description: Tried to recycle unconnected resource in the process of receiving a
response.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E2CH

Description: Not connected to partner RM while trying to recycle unconnected
resource.
Cause:
Corrective
Action:
None.

E2CI

Description: Unknown errno value returned from bcUcmmRecycle.
Cause: An errno value returned from bcUcmmRecycle.
Corrective
Action:
None.

Fault Codes
RM Fault Codes
170 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E2CJ

Description: Unable to close unconnected message manager resource.
Cause: Handle of unconnected message manager resource.
Corrective
Action:
Reset the RM, go to RM_CA02.

E2CK

Description: Invalid internal state reached.
Cause: Invalid state value.
Corrective
Action:
Reset the RM, go to RM_CA02.

E2CL

Description: Unable to close unconnected message manager resource.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E2D0

Description: Unable to start watchdog timer for monitoring.
Cause: An errno value returned from wdStart.
Corrective
Action:
Reset the RM, go to RM_CA02.

E2E0

Description: Unable to allocate combuf.
Cause: Slot number of module to be queried.
Corrective
Action:
None.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 171
1/03 Honeywell Part I
E2E1

Description: Unable to allocate unconnected message manager resource.
Cause: Slot number of module to be queried.
Corrective
Action:
None.

E2E2

Description: Unable to take semaphore for collecting redundancy attributes.
Cause: An errno value returned from semTake.
Corrective
Action:
Reset the RM, go to RM_CA02.

E2E3

Description: Unable to close unconnected message manager resource.
Cause: Slot number of module to be queried.
UCMM Handle.
Corrective
Action:
Reset the RM, go to RM_CA02.

E2E4

Description: Unable to take semphore used to verify a switchover is not in
progress.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
172 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E2E5

Description: Unable to close unconnected message manager resource.
Cause: Slot number of module to be queried.
UCMM Handle.
Corrective
Action:
Reset the RM, go to RM_CA02.

E2E6

Description: Unable to send unconnected request..
Cause: Slot number of module to be queried.
UCMM Handle.
Corrective
Action:
None.

E2E7

Description: Unable to close unconnected message manager resource.
Cause: Slot number of module to be queried.
UCMM Handle.
Corrective
Action:
Reset the RM, go to RM_CA02.

E2E8

Description: Too much data returned by module being queried.
Cause: Slot number of module to be queried.
Number of bytes returned.
Corrective
Action:
None.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 173
1/03 Honeywell Part I
E2E9

Description: Unable to send unconnected request.
Cause: Slot number of module to be queried.
UCMM Handle.
Corrective
Action:
None.

E2EA

Description: Unable to send unconnected request.
Cause: Slot number of module to be queried.
UCMM Handle.
Corrective
Action:
None.

E2EB

Description: Unable to send unconnected request.
Cause: Slot number of module to be queried.
UCMM Handle.
Corrective
Action:
None.

E2EC

Description: Unable to send unconnected request.
Cause: Slot number of module to be queried.
UCMM Handle.
Corrective
Action:
None.

Fault Codes
RM Fault Codes
174 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E2ED

Description: Unable to collect data from module.
Cause: Slot number of module to be queried.
UCMM Handle.
Corrective
Action:
None.

E2EE

Description: Unable to close unconnected message manager resource.
Cause: Slot number of module to be queried.
UCMM Handle.
Corrective
Action:
Reset the RM, go to RM_CA02.

E2EF

Description: Unable to close unconnected message manager resource.
Cause: Slot number of module to be queried.
UCMM Handle.
Corrective
Action:
Reset the RM, go to RM_CA02.

E2EG

Description: Unable to collect data from module.
Cause: Slot number of module to be queried.
UCMM Handle.
Corrective
Action:
None.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 175
1/03 Honeywell Part I
E2EH

Description: Unable to close unconnected message manager resource.
Cause: Slot number of module to be queried.
UCMM Handle.
Corrective
Action:
Reset the RM, go to RM_CA02.

E2F0

Description: Unable to allocate combuf.
Cause: Slot number of module to be queried.
Corrective
Action:
None.

E2F1

Description: Unable to allocate unconnected message manager resource.
Cause: Slot number of module to be queried.
Corrective
Action:
None.

E2F2

Description: Unable to send unconnected request.
Cause: Slot number of module to be queried.
UCMM Handle.
Corrective
Action:
None.

Fault Codes
RM Fault Codes
176 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E2F3

Description: Unable to close unconnected message manager resource.
Cause: Slot number of module to be queried.
UCMM Handle.
Corrective
Action:
Reset the RM, go to RM_CA02.

E2F4

Description: Unable to close unconnected message manager resource.
Cause: Slot number of module to be queried.
UCMM Handle.
Corrective
Action:
Reset the RM, go to RM_CA02.

E2F5

Description: Unable to close unconnected message manager resource.
Cause: Slot number of module to be queried.
UCMM Handle.
Corrective
Action:
Reset the RM, go to RM_CA02.

E2F6

Description: Unable to close unconnected message manager resource.
Cause: Slot number of module to be queried.
UCMM Handle.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 177
1/03 Honeywell Part I
E2F7

Description: Unable to collect data from module, maximum retries exceeded.
Cause: Slot number of module to be queried.
UCMM Handle.
Corrective
Action:
None.

E2F8

Description: Unable to close unconnected message manager resource.
Cause: Slot number of module to be queried.
UCMM Handle.
Corrective
Action:
Reset the RM, go to RM_CA02.

E2F9

Description: Unable to collect module data.
Cause: Slot number of module to be queried.
UCMM Handle.
Corrective
Action:
None.

E2FA

Description: Unable to close unconnected message manager resource.
Cause: Slot number of module to be queried.
UCMM Handle.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
178 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E2FB

Description: Unable to take semaphore for collecting device object attributes.
Cause: An errno value returned from semTake.
Corrective
Action:
Reset the RM, go to RM_CA02.

E2FC

Description: Unable to take semphore used to verify a switchover is not in
progress.
Cause: An errno value returned from semTake.
Corrective
Action:
Reset the RM, go to RM_CA02.

E2FD

Description: Unable to close unconnected message manager resource.
Cause: Slot number of module to be queried.
UCMM Handle.
Corrective
Action:
Reset the RM, go to RM_CA02.

E2FE

Description: Unable to close unconnected message manager resource.
Cause: Slot number of module to be queried.
UCMM Handle.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 179
1/03 Honeywell Part I
E2FF

Description: Unable to close unconnected message manager resource.
Cause: Slot number of module to be queried.
UCMM Handle.
Corrective
Action:
Reset the RM, go to RM_CA02.

E2G0

Description: Unable to give semaphore to begin collection.
Cause: An errno value returned from semGive.
Corrective
Action:
Reset the RM, go to RM_CA02.

E2G1

Description: Unable to restart watchdog timer for data collection.
Cause: An errno value returned from wdStart.
Corrective
Action:
Reset the RM, go to RM_CA02.

E2H0

Description: Unable to take semaphore to begin collection.
Cause: An errno value returned from semTake.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
180 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E2H1

Description: Received a startup time value from a module which is greater than 3
minutes.
Cause: Startup time value received.
Slot number from which the value was received.
Corrective
Action:
Reset the RM, go to RM_CA02.

E2J0

Description: Unable to allocate combuf.
Cause: Slot number of module to be queried.
Corrective
Action:
None.

E2J1

Description: Unable to allocate unconnected message manager resource.
Cause: Slot number of module to be queried.
Corrective
Action:
None.

E2J2

Description: Unable to send unconnected request.
Cause: Slot number of module to be queried.
UCMM Handle.
Corrective
Action:
None.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 181
1/03 Honeywell Part I
E2J3

Description: Unable to close unconnected message manager.
Cause: Slot number of module to be queried.
UCMM Handle.
Corrective
Action:
Reset the RM, go to RM_CA02.

E2J4

Description: Unable to close unconnected message manager.
Cause: Slot number of module to be queried.
UCMM Handle.
Corrective
Action:
Reset the RM, go to RM_CA02.

E2J5

Description: Unable to close unconnected message manager.
Cause: Slot number of module to be queried.
UCMM Handle.
Corrective
Action:
Reset the RM, go to RM_CA02.

E2J6

Description: Unable to communicate chassis ID to module, maximum retries
timed out.
Cause: Destination slot number.
Corrective
Action:
None.

Fault Codes
RM Fault Codes
182 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E2J7

Description: Unable to close unconnected message manager.
Cause: Slot number of module to be queried.
UCMM Handle.
Corrective
Action:
Reset the RM, go to RM_CA02.

E2J8

Description: Unable to communicate chassis ID to module.
Cause: Set chassis ID state number.
Destination slot number.
Corrective
Action:
Reset the RM, go to RM_CA02.

E2J9

Description: Unable to close unconnected message manager.
Cause: Destination slot number.
UCMM Handle.
Corrective
Action:
Reset the RM, go to RM_CA02.

E2K0

Description: Unable to create watchdog timer used for module pinging.
Cause: An errno value returned from wdCreate.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 183
1/03 Honeywell Part I
E2L0

Description: Unable to restart watchdog timer used for module pinging.
Cause: An errno value returned from wdStart.
Corrective
Action:
Reset the RM, go to RM_CA02.

E2L1

Description: Unable to restart watchdog timer used for module pinging.
Cause: An errno value returned from wdStart.
Corrective
Action:
Reset the RM, go to RM_CA02.

E2M0

Description: Unsuccesful status returned from partner request.
Cause: Response handle.
Status returned.
Real or apparent Redundancy cable disconnection.
Corrective
Action:
None.

E2M1

Description: Unexpected response received.
Cause: Response handle.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
184 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E2N0

Description: Unable to take semaphore which allows module data collection.
Cause: An errno value returned from semTake.
Corrective
Action:
Reset the RM, go to RM_CA02.

E2P0

Description: Unable to send event to message queue.
Cause: An errno value returned from msgQSend.
An event to be sent.
Corrective
Action:
Reset the RM, go to RM_CA02.

E2Q0

Description: Tried to send more than one request at a time to the partner RM.
Cause: Service request number of offending service.
First service parameter.
Corrective
Action:
Reset the RM, go to RM_CA02.

E2Q1

Description: Out of necessary resources to send partner request.
Cause: Service request number.
First service parameter.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 185
1/03 Honeywell Part I
E2Q2

Description: Invalid service request.
Cause: Service request number.
First service parameter.
Corrective
Action:
Reset the RM, go to RM_CA02.

E2Q3

Description: Invalid response state during request.
Cause: Service request number.
First service parameter.
Corrective
Action:
Reset the RM, go to RM_CA02.

E2Q4

Description: No client resources available to send request.
Cause: Service request number.
First service parameter.
Corrective
Action:
Reset the RM, go to RM_CA02.

E2Q5

Description: No receive descriptor available for the response.
Cause: Service request number.
First service parameter.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
186 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E2Q6

Description: No transmit descriptor available for the request.
Cause: Service request number.
First service parameter.
Corrective
Action:
Reset the RM, go to RM_CA02.

E2Q7

Description: No combuf available for the response.
Cause: Service request number.
First service parameter.
Corrective
Action:
Reset the RM, go to RM_CA02.

E2Q8

Description: A bad unconnected message manager handle was used.
Cause: Service request number.
First service parameter.
Corrective
Action:
Reset the RM, go to RM_CA02.

E2Q9

Description: A transmit was already in progress for the unconnected message
manager.
Cause: Service request number.
First service parameter.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 187
1/03 Honeywell Part I
E2QA

Description: An operating system error occurred.
Cause: Service request number.
First service parameter.
Corrective
Action:
Reset the RM, go to RM_CA02.

E2QB

Description: No longer connected to the partner RM.
Cause: Service request number.
First service parameter.
Corrective
Action:
None.

E2QC

Description: Maximum retries exceeded.
Cause: Service request number.
First service parameter.
Real or apparent Redundancy cable disconnection.
Corrective
Action:
Reset the RM, go to RM_CA02.

E2QD

Description: The private link transmit queue is full.
Cause: Service request number.
First service parameter.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
188 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E2QE

Description: The unconnected message manager being used was receiving data
unexpectedly.
Cause: Service request number.
First service parameter.
Corrective
Action:
Reset the RM, go to RM_CA02.

E2QF

Description: An undefined errno value was encountered.
Cause: Service request number.
An errno value.
Corrective
Action:
Reset the RM, go to RM_CA02.

E300

Description: Unable to prepare a buffer for response to a CST time maintenance
update request.
Cause:
Corrective
Action:
None.

E301

Description: Response routine to a request is NULL.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 189
1/03 Honeywell Part I
E400

Description: Error reading configuration log for vendor id.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E401

Description: Error reading configuration log for product type.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E402

Description: Error reading configuration log for product code.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E404

Description: Error reading configuration log for configured bit.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E405

Description: Error reading configuration log for serial number.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
190 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E406

Description: Error reading configuration log for product name.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E407

Description: Error creating semaphore for reset service.
Cause: An errno value returned from semBCreate.
Corrective
Action:
Reset the RM, go to RM_CA02.

E408

Description: Error creating watchdog for delay before servicing reset.
Cause: An errno value returned from wdCreate.
Corrective
Action:
Reset the RM, go to RM_CA02.

E409

Description: Error registering the device object class with the toolkit.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 191
1/03 Honeywell Part I
E40A

Description: Error setting the initial device object general status to unkeyed,
awaiting connection.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E410

Description: Unknown instance number.
Cause:
Corrective
Action:
None. Defaults to instance one.

E420

Description: Unknown instance number.
Cause:
Corrective
Action:
None. Defaults to instance one.

E430

Description: Unknown instance number.
Cause:
Corrective
Action:
None. Defaults to instance one.

Fault Codes
RM Fault Codes
192 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E440

Description: Unknown instance number.
Cause:
Corrective
Action:
None. Defaults to instance one.

E450

Description: Unknown instance number.
Cause:
Corrective
Action:
None. Defaults to instance one.

E451

Description: Error updating attributes.
Cause: An errno value returned from devUpdateAttributes.
Corrective
Action:
None. Defaults to instance one.

E460

Description: Unknown instance number.
Cause:
Corrective
Action:
None. Defaults to instance one.

E470

Description: Unknown instance number.
Cause:
Corrective
Action:
None. Defaults to instance one.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 193
1/03 Honeywell Part I
E480

Description: Unknown instance number.
Cause:
Corrective
Action:
None. Defaults to instance one.

E481

Description: Error updating attributes.
Cause: An errno value returned from devUpdateAttributes.
Corrective
Action:
None. Defaults to instance one.

E490

Description: Unknown instance number.
Cause:
Corrective
Action:
None. Defaults to instance one.

E4A0

Description: Unknown instance number.
Cause:
Corrective
Action:
None. Defaults to instance one.

E4B0

Description: Unknown instance number.
Cause:
Corrective
Action:
None. Defaults to instance one.

Fault Codes
RM Fault Codes
194 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E4C0

Description: Unknown instance number.
Cause:
Corrective
Action:
None. Defaults to instance one.

E4D0

Description: Unknown instance number.
Cause:
Corrective
Action:
None. Defaults to instance one.

E4E0

Description: Unknown instance number.
Cause:
Corrective
Action:
None. Defaults to instance one.

E4F0

Description: Unknown instance number.
Cause:
Corrective
Action:
None. Defaults to instance one.

E4G0

Description: Unknown instance number.
Cause:
Corrective
Action:
None. Defaults to instance one.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 195
1/03 Honeywell Part I
E4H0

Description: Unknown instance number.
Cause:
Corrective
Action:
None. Defaults to instance one.

E4I0

Description: Unknown instance number.
Cause:
Corrective
Action:
None. Defaults to instance one.

E4J0

Description: Unknown instance number.
Cause:
Corrective
Action:
None. Defaults to instance one.

E4K0

Description: Unknown instance number.
Cause:
Corrective
Action:
None. Defaults to instance one.

E4L0

Description: Unknown instance number.
Cause:
Corrective
Action:
None. Defaults to instance one.

Fault Codes
RM Fault Codes
196 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E4L1

Description: In major fault state, but no fault bits are set.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E4L2

Description: Unknown general state.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E4M0

Description: Unknown instance number.
Cause:
Corrective
Action:
None. Defaults to instance one.

E4N0

Description: Unknown instance number.
Cause:
Corrective
Action:
None. Defaults to instance one.

E4N1

Description: Error updating attributes.
Cause:
Corrective
Action:
None. Defaults to instance one.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 197
1/03 Honeywell Part I
E4P0

Description: Error updating attributes
Cause: An errno value returned from devUpdateAttributes.
Corrective
Action:
None. Defaults to instance one.

E4P1

Description: Error preparing success status response buffer for reset service
request.
Cause:
Corrective
Action:
None. Defaults to instance one.

E4P2

Description: Response routine pointer used to send reply to reset request is
corrupted (had value of NULL).
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E4P3

Description: Error taking semaphore to wait for event log to finish before resetting
RM.
Cause: An errno value returned from semTake.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
198 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E4P4

Description: Error starting watchdog to perform reset.
Cause: An errno value returned from wdStart.
Corrective
Action:
Reset the RM, go to RM_CA02.

E4Q0

Description: Error sending event to fault information queue.
Cause: An errno value returned from msgQSend.
Corrective
Action:
Reset the RM, go to RM_CA02.

E4R0

Description: Error sending event to display control queue.
Cause: An errno value returned from msgQSend.
Corrective
Action:
Reset the RM, go to RM_CA02.

E4T0

Description: Unknown control display event.
Cause: Control display event.
Corrective
Action:
None.

E4U0

Description: Error opening display.
Cause: An errno value returned from open.
Corrective
Action:
None.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 199
1/03 Honeywell Part I
E4U1

Description: Error commanding display to turn shifting off.
Cause: An errno value returned from ioctl.
Corrective
Action:
None.

E4U2

Description: Error writing to display.
Cause: An errno value returned from write.
Corrective
Action:
None.

E4U3

Description: Error closing display.
Cause: An errno value returned from close.
Corrective
Action:
None.

E4V0

Description: Error reading event from display control queue.
Cause: An errno value returned from msgQReceive.
Corrective
Action:
None.

E4V3

Description: Unknown redundancy state for display.
Cause: Redundancy state.
Corrective
Action:
None.

Fault Codes
RM Fault Codes
200 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E4V4

Description: Unknown non-redundancy state for display.
Cause: Non-Redundancy state.
Corrective
Action:
None.

E4V5

Description: Error starting watchdog to display fault message next.
Cause: An errno value returned from wdStart.
Corrective
Action:
None.

E4V6

Description: Error starting watchdog to display recovery message next.
Cause: An errno value returned from wdStart.
Corrective
Action:
None.

E4V7

Description: Error starting watchdog to display blank next.
Cause: An errno value returned from wdStart.
Corrective
Action:
None.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 201
1/03 Honeywell Part I
E4V8

Description: Error starting watchdog to display the next field in the fault message
next.
Cause: An errno value returned from wdStart.
Corrective
Action:
None.

E4V9

Description: Error starting watchdog to display recovery message next.
Cause: An errno value returned from wdStart.
Corrective
Action:
None.

E4VA

Description: Error starting watchdog to display blank next.
Cause: An errno value returned from wdStart.
Corrective
Action:
None.

E4VB

Description: Error starting watchdog to display the next field in the recovery
message next.
Cause: An errno value returned from wdStart.
Corrective
Action:
None.

Fault Codes
RM Fault Codes
202 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E4VC

Description: Error starting watchdog to display blank next.
Cause: An errno value returned from wdStart.
Corrective
Action:
None.

E4VD

Description: Error starting watchdog to display fault code next.
Cause: An errno value returned from wdStart.
Corrective
Action:
None.

E4VE

Description: Error starting watchdog to display new fault code next.
Cause: An errno value returned from wdStart.
Corrective
Action:
None.

E4VF

Description: Unknown event for display control.
Cause: Event.
Corrective
Action:
None.

E4VG

Description: Error reading event from fault information queue.
Cause: An errno value returned from msgReceive.
Corrective
Action:
None.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 203
1/03 Honeywell Part I
E4VH

Description: Error starting watchdog to clear minor recoverable fault in one
minute.
Cause: An errno value returned from wdStart.
Corrective
Action:
None.

E4VI

Description: Error starting watchdog to change display intensity (heartbeat).
Cause: An errno value returned from wdStart.
Corrective
Action:
None.

E4W0

Description: Unknown instance number.
Cause:
Corrective
Action:
None. Defaults to instance one.

E4X0

Description: Error starting watchdog to change display intensity (heartbeat).
Cause: An errno value returned from wdStart.
Corrective
Action:
None.

Fault Codes
RM Fault Codes
204 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E4X1

Description: Error starting watchdog to change display intensity (heartbeat).
Cause: An errno value returned from wdStart.
Corrective
Action:
None.

E4X2

Description: Error starting watchdog to change display intensity (heartbeat).
Cause: An errno value returned from wdStart.
Corrective
Action:
None.

E500

Description: Error registering the device object class with the toolkit.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E600

Description: Message queue send from service routine to event log task failed
when handling absolute or relative event log read.
Cause:
Corrective
Action:
None.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 205
1/03 Honeywell Part I
E601

Description: Failed to properly prepare buffer to send reply to get powerdown
state service request.
Cause:
Corrective
Action:
None.

E602

Description: Response routine pointer used to send reply to get powerdown state
service request is corrupted (had value of NULL).
Cause:
Corrective
Action:
None.

E603

Description: Failed to properly prepare buffer to send reply to get powerdown
time service request.
Cause:
Corrective
Action:
None.

E604

Description: Response routine pointer used to send reply to get powerdown time
service request is corrupted (had value of NULL).
Cause:
Corrective
Action:
None.

Fault Codes
RM Fault Codes
206 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E605

Description: Message queue send from service routine to event log task failed
when handling absolute or relative event log read.
Cause: An errno value returned from msgQSend.
Corrective
Action:
None.

E606

Description: Unable to get semaphore for configuration log shadow resource
when handling configuration log update service.
Cause: An errno value returned from semTake.
Corrective
Action:
None.

E607

Description: The function cfgReadAllData failed when handling configuration log
update service.
Cause:
Corrective
Action:
None.

E608

Description: The function cfgNcWriteNewData failed when handling configuration
log update service.
Cause:
Corrective
Action:
None.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 207
1/03 Honeywell Part I
E609

Description: Preparing response buffer failed when handling configuration log
update service.
Cause:
Corrective
Action:
None.

E610

Description: Unable to wdStart failed to start timer at beginning of task.
Cause: An errno value returned from wdStart.
Corrective
Action:
Reset the RM, go to RM_CA02.

E611

Description: Unable to wdStart failed to start timer in task loop.
Cause: An errno value returned from wdStart.
Corrective
Action:
Reset the RM, go to RM_CA02.

E612

Description: The function cfgReadAllData failed when handling event from Jabba
to indicating RM state is now primary with secondary.
Cause:
Corrective
Action:
None.

Fault Codes
RM Fault Codes
208 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E614

Description: Received a bad event in the tasks event queue (the events type
wasnt expected).
Cause: The event type that was sent to the eventlog.
Corrective
Action:
Reset the RM, go to RM_CA02.

E615

Description: The function msgQReceive failed when trying to receive on the
event log objects event queue.
Cause: An errno from msgQReceive.
Corrective
Action:
Reset the RM, go to RM_CA02.

E631

Description: Powerup rule received an unrecognized response handle.
Cause: Response handle that wasnt recognized.
Corrective
Action:
Reset the RM, go to RM_CA02.

E640

Description: Open function call for either partner or local event log failed.
Cause: An errno from open.
Corrective
Action:
None.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 209
1/03 Honeywell Part I
E641

Description: Could not prepare buffer for response to event log read service
request.
Cause:
Corrective
Action:
None.

E642

Description: Ioctl function call for either partner or local event log failed read
relative service.
Cause: An errno from ioctl.
Corrective
Action:
None.

E643

Description: Ioctl function call for either partner or local event log failed for read
absolute service.
Cause: An errno from ioctl.
Corrective
Action:
None.

E644

Description: Ioctl function call for either partner or local event log failed for read
absolute service.
Cause: An errno from ioctl.
Corrective
Action:
None.

Fault Codes
RM Fault Codes
210 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E645

Description: Read function call for read of event log failed with errno
S_logDrv_BAD_DEVICE_TYPE or S_logDrv_SEM_UNAVAILABLE.
Cause: An errno from read.
Corrective
Action:
Reset the RM, go to RM_CA02.

E646

Description: In read absolute or read relative service request, read system call
failed with errno S_logDrv_BAD_DEVICE_TYPE or
S_logDrv_SEM_UNAVAILABLE.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E647

Description: Open function call for local event log failed in update partner service
request.
Cause: An errno from read.
Corrective
Action:
None.

E648

Description: Could not prepare buffer for response to event log update partner
service request.
Cause:
Corrective
Action:
None.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 211
1/03 Honeywell Part I
E649

Description: Response routine pointer corrupted (NULL) in update partner
service.
Cause:
Corrective
Action:
None.

E650

Description: Could not allocate application connection resource for event log
connection to partner.
Cause:
Corrective
Action:
None.

E651

Description: Failure to initiate connection opening to partners event log object.
Cause:
Corrective
Action:
None.

E652

Description: Time required to open connection to partners event log object is
too long.
Cause:
Corrective
Action:
None.

Fault Codes
RM Fault Codes
212 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E653

Description: Failed to get pointer to buffer when attempting communications to
partners event log.
Cause:
Corrective
Action:
None.

E654

Description: Failed attempting to send message to partners event log.
Cause:
Corrective
Action:
None.

E655

Description: Time required to receive response from partner when querying its
event log is too long.
Cause:
Corrective
Action:
None.

E656

Description: Time required to receive response from partner when querying its
event log is too long.
Cause:
Corrective
Action:
None.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 213
1/03 Honeywell Part I
E660

Description: Reply to open failed.
Cause:
Corrective
Action:
None.

E670

Description: Response from partner to request timed-out.
Cause: Real or apparent Redundancy cable disconnection.
Corrective
Action:
None.

E671

Description: Write failed when attempting to write to local (shadow) copy of
partners event log.
Cause: An errno value returned from write.
Corrective
Action:
None.

E672

Description: Ioctl failed when attempting to configure local (shadow) copy of
partners event log.
Cause: An errno value returned from ioctl.
Corrective
Action:
None.

Fault Codes
RM Fault Codes
214 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E673

Description: Open failed when attempting for local (shadow) copy of partners
event log.
Cause: An errno value returned from open.
Corrective
Action:
None.

E680

Description: Data indication function received unrecognized event.
Cause: Unrecognized event.
Corrective
Action:
None.

E690

Description: Unable to get semaphore for configuration log shadow resource.
Cause: An errno value returned from semTake.
Corrective
Action:
Reset the RM, go to RM_CA02.

E6A0

Description: Unable to get semaphore for configuration log shadow resource.
Cause: An errno value returned from semTake.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 215
1/03 Honeywell Part I
E6B0

Description: Unable to get semaphore for configuration log shadow resource.
Cause: An errno value returned from semTake.
Corrective
Action:
Reset the RM, go to RM_CA02.

E6C0

Description: Unable to get semaphore for configuration log shadow resource
while writing vendor ID.
Cause: An errno value returned from semTake.
Corrective
Action:
Reset the RM, go to RM_CA02.

E6C1

Description: Unable to get semaphore for configuration log shadow resource
while writing product type.
Cause: An errno value returned from semTake.
Corrective
Action:
Reset the RM, go to RM_CA02.

E6C2

Description: Unable to get semaphore for configuration log shadow resource
while writing product code.
Cause: An errno value returned from semTake.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
216 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E6C3

Description: Unable to get semaphore for configuration log shadow resource
while writing revision number.
Cause: An errno value returned from semTake.
Corrective
Action:
Reset the RM, go to RM_CA02.

E6C4

Description: Unable to get semaphore for configuration log shadow resource
while writing serial number.
Cause: An errno value returned from semTake.
Corrective
Action:
Reset the RM, go to RM_CA02.

E6C5

Description: Unable to get semaphore for configuration log shadow resource
while writing product name.
Cause: An errno value returned from semTake.
Corrective
Action:
Reset the RM, go to RM_CA02.

E6C6

Description: Unable to get semaphore for configuration log shadow resource
while writing autoqualification option.
Cause: An errno value returned from semTake.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 217
1/03 Honeywell Part I
E6C7

Description: Unable to get semaphore for configuration log shadow resource
while writing program command recognition option.
Cause: An errno value returned from semTake.
Corrective
Action:
Reset the RM, go to RM_CA02.

E6C8

Description: Unable to get semaphore for configuration log shadow resource
while writing maximum power-up time.
Cause: An errno value returned from semTake.
Corrective
Action:
Reset the RM, go to RM_CA02.

E6C9

Description: Unable to get semaphore for configuration log shadow resource
while writing configured bit.
Cause: An errno value returned from semTake.
Corrective
Action:
Reset the RM, go to RM_CA02.

E6CA

Description: Unable to get semaphore for configuration log shadow resource
while writing workstation display position value.
Cause: An errno value returned from semTake.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
218 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E6CB

Description: Unable to get semaphore for configuration log shadow resource
while writing autoqualification state.
Cause: An errno value returned from semTake.
Corrective
Action:
Reset the RM, go to RM_CA02.

E6CC

Description: Unable to get semaphore for configuration log shadow resource
while writing autoqualification option and autoqualification state.
Cause: An errno value returned from semTake.
Corrective
Action:
Reset the RM, go to RM_CA02.

E6CD

Description: Unable to get semaphore for configuration log shadow resource
while writing application revision.
Cause: An errno value returned from semTake.
Corrective
Action:
Reset the RM, go to RM_CA02.

E6D0

Description: Unable to allocate combuf when copying event log to partner.
Cause:
Corrective
Action:
None.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 219
1/03 Honeywell Part I
E6D1

Description: Opening unconnected resource to partner to copy event log failed.
Cause:
Corrective
Action:
None.

E6D2

Description: Unable to send UCMM request to partner.
Cause:
Corrective
Action:
None.

E6D3

Description: Getting semaphore that waits for partner send response failed (but
this was not due to a message timeout).
Cause:
Corrective
Action:
None.

E6D4

Description: Copy of event log to partner failed.
Cause: Value of cfgCopyStatus.
Corrective
Action:
None.

Fault Codes
RM Fault Codes
220 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E6E0

Description: Unable to get semaphore for configuration log shadow resource
while reseting RM configuration log to factory defaults.
Cause: An errno value returned from semTake.
Corrective
Action:
Reset the RM, go to RM_CA02.

E6F0

Description: Message Queue Send function failed when another subsystem tried
to post an event to the event log object.
Cause: An errno value returned from msgQSend.
Corrective
Action:
Reset the RM, go to RM_CA02.

E700

Description: Unable to post to message queue for the backup communications
object.
Cause: An errno value returned from msgQSend.
Event number
Corrective
Action:
Reset the RM, go to RM_CA02.

E701

Description: Unable to start watchdog used to keep the partner communication
LED red for greater than 1 second at powerup.
Cause: An errno value returned from wdStart.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 221
1/03 Honeywell Part I
E702

Description: Unable to open the /commLed device used for controlling the
partner communication LED.
Cause: An errno value returned from open.
Corrective
Action:
Reset the RM, go to RM_CA02.

E703

Description: Unable to perform ioctl command to /commLed device used for
controlling the partner communication LED.
Cause: An errno value returned from ioctl.
Corrective
Action:
Reset the RM, go to RM_CA02.

E704

Description: Unable to perform write to /commLed device used for controlling the
partner communication LED.
Cause: An errno value returned from write.
Corrective
Action:
Reset the RM, go to RM_CA02.

E70E

Description: Unexpected event while in the INIT state.
Cause: Current Backup Communications object state.
Event type received.
Corrective
Action:
None.

Fault Codes
RM Fault Codes
222 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E70G

Description: Unexpected event while in the DISCONNECTED state.
Cause: Current Backup Communications object state.
Event type received.
Corrective
Action:
None.

E70H

Description: Unexpected event while in the DISCONNECTED_S state.
Cause: Current Backup Communications object state.
Event type received.
Corrective
Action:
None.

E70L

Description: Unable to allocate memory for table of available UCMM targets on
the partner RM.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E70N

Description: Unable to start watchdog used for collecting private link statistics.
Cause: An errno value returned from wdStart.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 223
1/03 Honeywell Part I
E70Q

Description: Received an ACK to an unexpected command transmission while in
the CONNECTING state.
Cause: Current Backup Communications object state.
Command code transmitted.
Corrective
Action:
None.

E70T

Description: Unable to start watchdog used for RM to RM pinging.
Cause: An errno value returned from wdStart.
Corrective
Action:
Reset the RM, go to RM_CA02.

E70U

Description: Unable to start watchdog used to control partner to partner pinging.
Cause: An errno value returned from wdStart.
Corrective
Action:
Reset the RM, go to RM_CA02.

E70V

Description: Received an unexpected command from partner RM while in the
CONNECTING state.
Cause: Current Backup Communications object state.
Command code received from partner RM.
Corrective
Action:
None.

Fault Codes
RM Fault Codes
224 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E70W

Description: Unexpected event while in the CONNECTING state.
Cause: Current Backup Communications object state.
Event type received.
Corrective
Action:
None.

E710

Description: The transmit packet count register rolled over before it could be read
by firmware.
Cause:
Corrective
Action:
None.

E711

Description: The transmit retry count register rolled over before it could be read
by firmware.
Cause:
Corrective
Action:
None.

E712

Description: The transmit word count register rolled over before it could be read
by firmware.
Cause:
Corrective
Action:
None.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 225
1/03 Honeywell Part I
E713

Description: The receive packet count register rolled over before it could be read
by firmware.
Cause:
Corrective
Action:
None.

E714

Description: The receive valid packet count register rolled over before it could be
read by firmware.
Cause:
Corrective
Action:
None.

E715

Description: The receive CRC error count register rolled over before it could be
read by firmware.
Cause:
Corrective
Action:
None.

E716

Description: The receive framing error count register rolled over before it could
be read by firmware.
Cause:
Corrective
Action:
None.

Fault Codes
RM Fault Codes
226 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E717

Description: The receive word count register rolled over before it could be read
by firmware.
Cause:
Corrective
Action:
None.

E718

Description: Unable to start watchdog used for collecting private link statistics.
Cause: An errno value returned from wdStart.
Corrective
Action:
Reset the RM, go to RM_CA02.

E719

Description: Received BC_CMD_START from partner RM while in the
CONNECTED state.
Cause:
Corrective
Action:
None.

E71A

Description: Received unexpected command from partner RM while in the
CONNECTED state.
Cause: Command code received from partner RM.
Corrective
Action:
None.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 227
1/03 Honeywell Part I
E71B

Description: Unexpected event while in the CONNECTED state.
Cause: Current Backup Communications object state.
Command code received from partner RM.
Corrective
Action:
None.

E71C

Description: Unexpected event while in the DISABLED_S state.
Cause: Current Backup Communications object state.
Command code received from partner RM.
Corrective
Action:
None.

E71D

Description: Unexpected event while in the DISABLED_E state.
Cause: Current Backup Communications object state.
Command code received from partner RM.
Corrective
Action:
None.

E71E

Description: Backup communications object is in an invalid state.
Cause: Current state value of backup communications object.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
228 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E71F

Description: Error reading message from message queue.
Cause: An errno value returned from msgQReceive.
Corrective
Action:
Reset the RM, go to RM_CA02.

E71G

Description: Unable to cancel watchdog used for collecting private link statistics.
Cause: An errno value returned from wdCancel.
Corrective
Action:
Reset the RM, go to RM_CA02.

E71H

Description: Unable to cancel watchdog used for collecting private link statistics.
Cause: An errno value returned from wdCancel.
Corrective
Action:
Reset the RM, go to RM_CA02.

E71I

Description: Unable to cancel watchdog used for collecting private link statistics.
Cause: An errno value returned from wdCancel.
Corrective
Action:
Reset the RM, go to RM_CA02.

E71J

Description: Unable to cancel watchdog used for collecting private link statistics.
Cause: An errno value returned from wdCancel.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 229
1/03 Honeywell Part I
E720

Description: Unable to post message to link producer task.
Cause: An errno value returned from msgQSend.
Corrective
Action:
None.

E721

Description: Unable to post message to unconnected message manager task.
Cause: An errno value returned from msgQSend.
Corrective
Action:
None.

E722

Description: Unknown command in transmit descriptor being recovered.
Cause: Descriptor id.
Command character.
Corrective
Action:
None.

E723

Description: Unable to post message to link producer task.
Cause: An errno value returned from msgQSend.
Corrective
Action:
None.

Fault Codes
RM Fault Codes
230 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E724

Description: Unable to post message to unconnected message manager task.
Cause: An errno value returned from msgQSend.
Corrective
Action:
None.

E725

Description: Unknown command in transmit descriptor being recovered.
Cause: Descriptor id.
Command character.
Corrective
Action:
None.

E726

Description: The transmit packet count register rolled over before it could be read
by firmware.
Cause:
Corrective
Action:
None.

E727

Description: The transmit retry count register rolled over before it could be read
by firmware.
Cause:
Corrective
Action:
None.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 231
1/03 Honeywell Part I
E728

Description: The transmit word count register rolled over before it could be read
by firmware.
Cause:
Corrective
Action:
None.

E729

Description: The receive packet count register rolled over before it could be read
by firmware.
Cause:
Corrective
Action:
None.

E72A

Description: The receive valid packet count register rolled over before it could be
read by firmware.
Cause:
Corrective
Action:
None.

E72B

Description: The receive CRC error count register rolled over before it could be
read by firmware.
Cause:
Corrective
Action:
None.

E72C

Description: The receive framing error count register rolled over before it could
be read by firmware.
Fault Codes
RM Fault Codes
232 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Cause:
Corrective
Action:
None.

E72D

Description: The receive word count register rolled over before it could be read
by firmware.
Cause:
Corrective
Action:
None.

E730

Description: Unable to get semaphore for allocating a new bridging transport.
Cause: An errno value returned from semTake.
Corrective
Action:
Reset the RM, go to RM_CA02.

E731

Description: State conflict occured when deleting a link consumer.
Cause: Link consumer handle.
Corrective
Action:
None.

E732

Description: State conflict occured when deleting a link producer.
Cause: Link producer handle.
Corrective
Action:
None.

E733

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 233
1/03 Honeywell Part I
Description: State conflict occured when deleting a link consumer.
Cause: Link consumer handle.
Corrective
Action:
None.

E734

Description: State conflict occured when deleting a link producer.
Cause: Link producer handle.
Corrective
Action:
None.

E735

Description: Time-out on bridged connection, originator to target direction.
Cause: Bridge record handle.
Corrective
Action:
None.

E736

Description: Error occured while swapping in-port and out-port buffers, originator
to target direction.
Cause: Bridge record handle.
Status returned from bcBridgeSwap.
Corrective
Action:
None.

Fault Codes
RM Fault Codes
234 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E737

Description: Error occured while forwarding a message to the target.
Cause: Bridge record handle.
Status returned from Link Producer send routine.
Corrective
Action:
None.

E738

Description: Time-out on bridged connection, target to originator direction.
Cause: Bridge record handle.
Corrective
Action:
None.

E739

Description: Error occured while swapping in-port and out-port buffers, target to
originator direction.
Cause: Bridge record handle.
Status returned from bcBridgeSwap.
Corrective
Action:
None.

E73A

Description: Error occured while forwarding a message to the originator.
Cause: Bridge record handle.
Status returned from Link Producer send routine.
Corrective
Action:
None.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 235
1/03 Honeywell Part I
E73C

Description: Error occured while swapping in-port and out-port buffers, originator
to target direction.
Cause: Bridge record handle.
Status returned from bcBridgeSwap.
Corrective
Action:
None.

E73D

Description: Error occured while forwarding a message to the target.
Cause: Bridge record handle.
Status returned from Link Producer send routine.
Corrective
Action:
None.

E73F

Description: Error occured while swapping in-port and out-port buffers, target to
originator direction.
Cause: Bridge record handle.
Status returned from bcBridgeSwap.
Corrective
Action:
None.

E73G

Description: Error occured while forwarding a message to the originator.
Cause: Bridge record handle.
Status returned from Link Producer send routine.
Corrective
Action:
None.

Fault Codes
RM Fault Codes
236 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E73H

Description: Unexpected event received from link producer in transmit done
routine.
Cause: Bridge record handle.
Event received from link producer.
Corrective
Action:
Reset the RM, go to RM_CA02.

E73I

Description: Unexpected event received from link producer in transmit done
routine.
Cause: Bridge record handle.
Event received from link producer.
Corrective
Action:
Reset the RM, go to RM_CA02.

E740

Description: Unable to get semaphore for allocating a receive descriptor.
Cause: An errno value returned from semTake.
Corrective
Action:
Reset the RM, go to RM_CA02.

E741

Description: Unable to get semaphore for allocating a transmit descriptor.
Cause: An errno value returned from semTake.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 237
1/03 Honeywell Part I
E742

Description: Unable to get semaphore for allocating a descriptor ID.
Cause: An errno value returned from semTake.
Corrective
Action:
Reset the RM, go to RM_CA02.

E752

Description: Descriptor ID read from transmit channel is 0.
Cause:
Corrective
Action:
None.

E753

Description: The transmit channel returned a transmit error.
Cause: Transmit descriptor ID causing the error.
Corrective
Action:
Reset the RM, go to RM_CA02.

E754

Description: Unknown transmit status returned by the transmit channel.
Cause: Transmit descriptor ID containing invalid status.
Invalid status value
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
238 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E755

Description: Unable to send message to the link producer task.
Cause: An errno value returned by msgQSend.
Corrective
Action:
None.

E756

Description: Unable to send message to the unconnected message manager
task.
Cause: An errno value returned by msgQSend.
Corrective
Action:
None.

E757

Description: Unknown command code in transmit descriptor.
Cause: Transmit descriptor ID.
Invalid command code
Corrective
Action:
None.

E75A

Description: Descriptor ID read from receive channel is 0.
Cause:
Corrective
Action:
None.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 239
1/03 Honeywell Part I
E75B

Description: The receive channel returned a memory access error.
Cause: Receive descriptor ID.
Corrective
Action:
Reset the RM, go to RM_CA02.

E75C

Description: The receive channel returned an invalid destination error.
Cause: Receive descriptor ID.
Corrective
Action:
None.

E75D

Description: Unknown received status returned by the receive channel.
Cause: Receive descriptor ID containing the invalid status.
Invalid status value
Corrective
Action:
Reset the RM, go to RM_CA02.

E75E

Description: Unable to send to the link consumer task.
Cause: An errno value returned by msgQSend.
Corrective
Action:
None.

Fault Codes
RM Fault Codes
240 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E75F

Description: Unable to send to the unconnected message manager task.
Cause: An errno value returned by msgQSend.
Corrective
Action:
None.

E75G

Description: Unknown command code in receive descriptor.
Cause: Receive descriptor ID.
Invalid command code.
Corrective
Action:
None.

E75I

Description: A double bit memory error has occured in local RAM.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E75J

Description: A shared RAM parity error occred.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 241
1/03 Honeywell Part I
E75K

Description: Error occured while invalidating the data cache for a transmit
descriptor.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E75L

Description: Error occured while invalidating the data cache for a receive
descriptor.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E75M

Description: An error occurred while trying to start a watchdog timer to unmask
the signal detect interrupt.
Cause: An errno value returned by wdStart.
Corrective
Action:
Reset the RM, go to RM_CA02.

E760

Description: The bcLcFreeReceiveBuffer was called with a NULL buffer pointer.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
242 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E762

Description: Receive descriptor in use by hardware layer. Not expected unless
buffer overwriting is enabled.
Cause: Receive descriptor number.
Corrective
Action:
None.

E763

Description: Receive descriptor in use by hardware layer. Not expected unless
buffer overwriting is enabled.
Cause: Receive descriptor number.
Corrective
Action:
None.

E764

Description: Unable to get semaphore for allocating a link consumer.
Cause: An errno value returned from semTake.
Corrective
Action:
Reset the RM, go to RM_CA02.

E766

Description: Unexpected message received by the link consumer task.
Cause: Message type received.
Corrective
Action:
None.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 243
1/03 Honeywell Part I
E767

Description: Error reading message from link consumer message queue.
Cause: An errno value returned from msgQReceive.
Corrective
Action:
Reset the RM, go to RM_CA02.

E768

Description: An invalid descriptor ID was received.
Cause: Receive descriptor ID.
Corrective
Action:
None.

E769

Description: Status of received descriptor is not OK.
Cause: Receive descriptor ID.
Status of receive descriptor.
Corrective
Action:
None.

E76A

Description: Link consumer received a message but is no longer running.
Cause: Link consumer handle.
Link consumer state.
Corrective
Action:
None.

Fault Codes
RM Fault Codes
244 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E76C

Description: Receive descriptor in use by hardware layer. Not expected unless
buffer overwriting is enabled.
Cause: Receive descriptor ID.
Corrective
Action:
None.

E76D

Description: Double buffering is enabled but the second buffer is not available.
Cause: Receive descriptor ID.
Corrective
Action:
None.

E76E

Description: Receive descriptor in use by hardware layer. Not expected unless
buffer overwriting is enabled.
Cause: Receive descriptor ID.
Corrective
Action:
None.

E76F

Description: Double buffering is enabled but the second buffer is not available.
Cause: Receive descriptor ID.
Corrective
Action:
None.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 245
1/03 Honeywell Part I
E770

Description: The selected buffer was not available for the transport layer, the
second buffer is being used.
Cause: Transmit descriptor number.
Corrective
Action:
None.

E771

Description: The selected buffer was not available for the transport layer, the
second buffer is being used.
Cause: Transmit descriptor number.
Corrective
Action:
None.

E772

Description: Unable to get semaphore for allocating a link producer.
Cause: An errno value returned from semTake.
Corrective
Action:
Reset the RM, go to RM_CA02.

E774

Description: A message existed on the pending queue. This means that the
hardware is not transmitting messages as fast as they are being
submitted by firmware.
Cause:
Corrective
Action:
None.

Fault Codes
RM Fault Codes
246 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E777

Description: Error reading message from link producer message queue.
Cause: An errno value returned from msgQReceive.
Corrective
Action:
Reset the RM, go to RM_CA02.

E778

Description: The bcLpSend was called with a NULL buffer pointer.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E779

Description: Descriptor being written to the transmit queue has nothing to be
transmitted.
Cause: Transmit descriptor number.
Corrective
Action:
None.

E77A

Description: Descriptor being written to the transmit queue has nothing to be
transmitted.
Cause: Transmit descriptor number.
Corrective
Action:
None.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 247
1/03 Honeywell Part I
E77C

Description: The hardware transmit queue is full. Message to be sent will be
queued by firmware.
Cause: Transmit descriptor number.
Corrective
Action:
None.

E77E

Description: A message existed on the pending queue. This means that the
hardware is not transmitting messages as fast as they are being
submitted by firmware.
Cause:
Corrective
Action:
None.

E77H

Description: Unable to post message to link producer message queue.
Cause: An errno value returned from msgQSend.
Corrective
Action:
None.

E77I

Description: An invalid transmit descriptor was given back by the hardware
transmit channel.
Cause: Transmit descriptor ID
Corrective
Action:
None.

Fault Codes
RM Fault Codes
248 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E77J

Description: A transmission has finished for a link producer which is no longer
running.
Cause: Link producer handle.
Link producer state.
Corrective
Action:
None.

E77K

Description: Unable to write transmit descriptor to hardware transmit queue or
internal firmware transmission queue.
Cause:
Corrective
Action:
None.

E790

Description: Unable to start watchdog used for communication timers.
Cause: An errno value returned from wdStart.
Corrective
Action:
Reset the RM, go to RM_CA02.

E791

Description: Unable to send time-out message to link consumer task.
Cause: An errno value returned from msgQSend.
Corrective
Action:
None.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 249
1/03 Honeywell Part I
E792

Description: Unable to send time-out message to link consumer task.
Cause: An errno value returned from msgQSend.
Corrective
Action:
None

E7B1

Description: Unable to get semaphore for allocating a client UCMM resource.
Cause: An errno value returned from semTake.
Corrective
Action:
Reset the RM, go to RM_CA02.

E7B2

Description: Unable to get semaphore for allocating a server UCMM resource.
Cause: An errno value returned from semTake.
Corrective
Action:
Reset the RM, go to RM_CA02.

E7B3

Description: Unable to get semaphore when selecting a target resource for
sending an unconnected command.
Cause: An errno value returned from semTake.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
250 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E7B4

Description: Unable to get semaphore when selecting a target resource for
sending an unconnected request.
Cause: An errno value returned from semTake.
Corrective
Action:
Reset the RM, go to RM_CA02.

E7B6

Description: Unable to get semaphore when marking a target resource available.
Cause: An errno value returned from semTake.
Corrective
Action:
Reset the RM, go to RM_CA02.

E7B7

Description: An invalid descriptor ID was received.
Cause: Received descriptor ID.
Corrective
Action:
None.

E7B8

Description: Status of received descriptor is not OK.
Cause: Received descriptor ID.
Status of receive descriptor.
Corrective
Action:
None.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 251
1/03 Honeywell Part I
E7B9

Description: Unable to allocate an UCMM server resource when receiving a
request.
Cause:
Corrective
Action:
None.

E7BA

Description: Unable to allocate a transmit descriptor when receiving a request.
Cause:
Corrective
Action:
None.

E7BB

Description: Status of received descriptor is not OK.
Cause: Received descriptor ID.
Status of receive descriptor.
Corrective
Action:
None.

E7BC

Description: The message router request to process a received command failed.
Cause:
Corrective
Action:
None.

Fault Codes
RM Fault Codes
252 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E7BD

Description: Unable to get semaphore when marking a target resource available.
Cause: An errno value returned from semTake.
Corrective
Action:
Reset the RM, go to RM_CA02.

E7BE

Description: Received a response for an UCMM that is not running.
Cause: UCMM handle.
Corrective
Action:
None.

E7BF

Description: Unable to get semaphore when marking a target resource available.
Cause: An errno value returned from semTake.
Corrective
Action:
Reset the RM, go to RM_CA02.

E7BG

Description: Unable to get semaphore when marking a target resource available.
Cause: An errno value returned from semTake.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 253
1/03 Honeywell Part I
E7BH

Description: Unexpected command character in receive descriptor.
Cause: Receive descriptor ID.
Command character.
Corrective
Action:
None.

E7BI

Description: An invalid descriptor ID was received.
Cause: Receive descriptor ID.
Corrective
Action:
None.

E7BJ

Description: Unable to get semaphore when marking a target resource available.
Cause: An errno value returned from semTake.
Corrective
Action:
Reset the RM, go to RM_CA02.

E7BL

Description: Unable to get semaphore when marking a target resource available.
Cause: An errno value returned from semTake.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
254 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E7BM

Description: Unable to get semaphore when marking a target resource available.
Cause: An errno value returned from semTake.
Corrective
Action:
Reset the RM, go to RM_CA02.

E7BN

Description: Unable to get semaphore when marking a target resource available.
Cause: An errno value returned from semTake.
Corrective
Action:
Reset the RM, go to RM_CA02.

E7BQ

Description: A message existed on the pending queue. This means that the
hardware is not transmitting messages as fast as they are being
submitted by firmware.
Cause:
Corrective
Action:
None.

E7BT

Description: Error reading message from unconnected message manager queue.
Cause: An errno value returned from msgQReceive.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 255
1/03 Honeywell Part I
E7BU

Description: Unexpected command character in transmit descriptor.
Cause: Transmit descriptor ID.
Command character.
Corrective
Action:
None.

E800

Description: Attempted to free a combuf which was already free.
Cause: Combuf pointer.
Corrective
Action:
None.

E801

Description: Tries to free a NULL combuf pointer.
Cause:
Corrective
Action:
None.

E810

Description: The ICP ASIC fault line did not go inactive within expected time limit.
Cause:
Corrective
Action:
Reset ( RM_CA02) or replace the RM (RM_CA01).

Fault Codes
RM Fault Codes
256 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E811

Description: The ICP ASIC loop back test failed and a supervisor control could
not be submitted to the ASIC to turn off the receiver circuitry.
Cause:
Corrective
Action:
Reset ( RM_CA02) or replace the RM (RM_CA01).

E812

Description: The ICP ASIC loop back test failed.
Cause:
Corrective
Action:
Reset ( RM_CA02) or replace the RM (RM_CA01).

E813

Description: An invalid control block pointer is trying to be passed to the ICP
ASIC.
Cause: Invalid control block pointer.
Corrective
Action:
Reset the RM, go to RM_CA02.

E814

Description: An invalid control block pointer came from the control block host free
list.
Cause: Invalid control block pointer.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 257
1/03 Honeywell Part I
E815

Description: An invalid control block pointer is trying to be put onto the control
block host free list.
Cause: Invalid control block pointer.
Corrective
Action:
Reset the RM, go to RM_CA02.

E816

Description: An invalid control block pointer is trying to be passed to the ICP
ASIC (for a flow controlled connection).
Cause: Invalid control block pointer.
Corrective
Action:
Reset the RM, go to RM_CA02.

E817

Description: An invalid control block pointer is trying to be passed to the ICP
ASIC (for a supervisory request).
Cause: Invalid control block pointer.
Corrective
Action:
Reset the RM, go to RM_CA02.

E818

Description: A control block pointer is trying to be passed to the ICP ASIC, but
the ICP ASIC queing link is already non-zero.
Cause: Invalid control block pointer.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
258 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E819

Description: An invalid control block pointer is trying to be passed to the ICP
ASIC (for a notify CB).
Cause: Control block pointer.
Corrective
Action:
None.

E81A

Description: A control block is going onto the host free list with a non-zero value
in the ICP ASIC queing link.
Cause: Control block pointer.
Corrective
Action:
None.

E81B

Description: A control block came from the host free list with a non-zero value in
the ICP ASIC queing link.
Cause: Control block pointer.
Corrective
Action:
None.

E81C

Description: A control block is trying to be passed to the ICP ASIC, but the ICP
ASIC queing link is already non-zero (for a flow controlled
connection).
Cause: Control block pointer.
Corrective
Action:
None.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 259
1/03 Honeywell Part I
E81D

Description: A control block is trying to be passed to the ICP ASIC, but the ICP
ASIC queing link is already non-zero (for a supervisory request).
Cause: Control block pointer.
Corrective
Action:
None.

E81E

Description: A control block is trying to be passed to the ICP ASIC, but the ICP
ASIC queing link is already non-zero (for a notify CB).
Secondary RM encounters a minor recoverable fault during
powerup. The E81E fault code indicates that the RM encountered a
communication failure. Note that as a consequence of this defect,
modules within the secondary chassis may not have transitioned to
the secondary redundancy role (for example,. CNIs in DUPL node,
CPM not in BKUP state). However, this does not affect primary
controller chassis operation.
Cause: Control block pointer.
Corrective
Action:
Cycle power to the secondary chassis.

E820

Description: The dynamic class registration table could not be initialized.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E821

Description: Part of the general initialization failed.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
260 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E830

Description: Unable to create semaphore for the UCMM Resource table.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E831

Description: Unable to take semaphore for the UCMM Resource table.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E832

Description: Unable to take semaphore for the UCMM Resource table.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E833

Description: Unable to take semaphore for the UCMM Resource table.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E834

Description: Unable to take semaphore for the UCMM Resource table.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 261
1/03 Honeywell Part I
E835

Description: Unable to take semaphore for the UCMM Resource table.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E836

Description: Unable to take semaphore for the UCMM Resource table.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E840

Description: Unable to initialize semaphore for the server transport resource
table.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E841

Description: Unable to initialize semaphore for the client transport resource table.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
262 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E850

Description: Unable to take semaphore for the server transport resource table.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E851

Description: Unable to give semaphore for the server transport resource table.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E852

Description: Unable to give semaphore for the server transport resource table.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E860

Description: Unable to take semaphore for the client transport resource table.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E861

Description: Unable to give semaphore for the client transport resource table.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 263
1/03 Honeywell Part I
E862

Description: Unable to give semaphore for the client transport resource table.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E870

Description: Unable to initialize semaphore for the link consumer resource table.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E871

Description: Unable to take semaphore for the link consumer resource table.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E872

Description: Unable to give semaphore for the link consumer resource table.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E873

Description: Unable to give semaphore for the link consumer resource table.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
264 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E876

Description: Tried to free a NULL link consumer receive buffer.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E880

Description: Unable to initialize semaphore for the link producer resource table.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E881

Description: Unable to take semaphore for the link producer resource table.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E882

Description: Unable to give semaphore for the link producer resource table.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E883

Description: Unable to give semaphore for the link producer resource table.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 265
1/03 Honeywell Part I
E884

Description: Unable to create buffer used for queing link producers which need to
be resent.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E885

Description: Unable to create watchdog timer for monitoring queue of link
producers which need to be resent.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E886

Description: Unable to start the watchdog timer used for monitoring queue of link
producers which need to be resent.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E887

Description: Unable to restart the watchdog timer used for monitoring queue of
link producers which need to be resent.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
266 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E888

Description: Tried to do a link producer send with a NULL transmit buffer.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E889

Description: Unable to create buffer used for queing link producers which need to
be resent.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E88A

Description: A link producer CB is being processed on return from the ICP ASIC
and a new send is already pending. This is unexpected.
Cause: Pointer to control block allocated by link producer.
State of control block.
Corrective
Action:
None.

E88B

Description: Double buffering code is running unexpectedly on a link producer
send.
Cause: Link producer handle.
Pointer to control block allocated by link producer.
Corrective
Action:
None.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 267
1/03 Honeywell Part I
E88C

Description: Trying a new send when the previous send is still pending in the ICP
ASIC.
Cause: Link producer handle.
Pointer to control block allocated by link producer.
Corrective
Action:
None.

E88D

Description: A control block was returned by the ICP ASIC in the CB_STS_INIT
state.
Cause: State of control block.
Pointer to control block allocated by link producer.
Corrective
Action:
None.

E88E

Description: A control block was returned by the ICP ASIC in an error state.
Cause: State of control block.
Pointer to control block allocated by link producer.
Corrective
Action:
None.

E891

Description: Unable to take semaphore for the connection manager resource
table.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
268 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E892

Description: Unable to give semaphore for the connection manager resource
table.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E893

Description: Unable to give semaphore for the connection manager resource
table.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E894

Description: Unable to create semaphore for the connection manager resource
table.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

E895

Description: Unable to set device state to CONNECTED_ACTIVE when the first
connection is created.
Cause: An errno value returned from devSetState().
Corrective
Action:
None.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 269
1/03 Honeywell Part I
E896

Description: Unable to set device state to
UNKEYED_AWAITING_CONNECTION when last connection is
closed.
Cause: An errno value returned from devSetState().
Corrective
Action:
None.

E8A0

Description: Received Fault interrupt from ICP ASIC.
Cause:
Corrective
Action:
None.

E8A1

Description: Received bad data on loop back test.
Cause: Data received.
Data expected.
Corrective
Action:
Reset ( RM_CA02) or replace the RM (RM_CA01).

E8A2

Description: Received a control block from the ICP ASIC with the queing value
still non-zero.
Cause: Control block pointer.
Corrective
Action:
None.

Fault Codes
RM Fault Codes
270 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
E8A3

Description: ICP ASIC reported a watchdog error.
Cause: Error register value read from ICP ASIC.
Corrective
Action:
Reset the RM, go to RM_CA02.

E8A4

Description: ICP ASIC reported a shared RAM parity error.
Cause: Error register value read from ICP ASIC.
Corrective
Action:
Reset the RM, go to RM_CA02.

E8A5

Description: ICP ASIC reported a host parity error.
Cause: Error register value read from ICP ASIC.
Corrective
Action:
Reset the RM, go to RM_CA02.

E8B0

Description: Unable to allocate combuf for error response.
Cause: Error register value read from ICP ASIC.
Corrective
Action:
Reset the RM, go to RM_CA02.

EA00

Description: Error opening LED.
Cause: An errno value returned from open.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 271
1/03 Honeywell Part I
EA01

Description: Error opening relay.
Cause: An errno value returned from open.
Corrective
Action:
Reset the RM, go to RM_CA02.

EA02

Description: Duplicate RM.
Cause:
Corrective
Action:
Remove the RM.

EA03

Description: Error starting timer for starting state determination.
Cause: An errno value returned from wdStart.
Corrective
Action:
None.

EA04

Description: Unknown redundancy state handle.
Cause: Redundancy state handle.
Corrective
Action:
Reset the RM, go to RM_CA02.

EA05

Description: Error reading message from main queue.
Cause: An errno value returned from msgQReceive.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
272 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
EA10

Description: Event received in wrong state.
Cause: State.
Corrective
Action:
Reset the RM, go to RM_CA02.

EA11

Description: Event received in wrong state.
Cause: State.
Corrective
Action:
Reset the RM, go to RM_CA02.

EA12

Description: Event received in wrong state.
Cause: State.
Corrective
Action:
Reset the RM, go to RM_CA02.

EA13

Description: Event received in wrong state.
Cause: State.
Corrective
Action:
Reset the RM, go to RM_CA02.

EA14

Description: Error entering event into transition queue.
Cause: An errno value returned from msgQSend.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 273
1/03 Honeywell Part I
EA15

Description: Event received in wrong state.
Cause: State.
Corrective
Action:
Reset the RM, go to RM_CA02.

EA16

Description: Error entering event into transition queue.
Cause: An errno value returned from msgQSend.
Corrective
Action:
Reset the RM, go to RM_CA02.

EA17

Description: Event received in wrong state.
Cause: State.
Corrective
Action:
Reset the RM, go to RM_CA02.

EA18

Description: Error entering event into transition queue.
Cause: An errno value returned from msgQSend.
Corrective
Action:
Reset the RM, go to RM_CA02.

EA19

Description: Unexpected redundancy state from partner.
Cause: Redundancy state.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
274 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
EA1B

Description: Unexpected redundancy state.
Cause: Redundancy state.
Corrective
Action:
Reset the RM, go to RM_CA02.

EA1C

Description: Error completing the state change.
Cause: An errno returned from jbaStateChangeComplete.
Corrective
Action:
Reset the RM, go to RM_CA02.

EA1D

Description: Event received in wrong state.
Cause: State.
Corrective
Action:
Reset the RM, go to RM_CA02.

EA1E

Description: Unexpected event for powerup.
Cause: Event.
Corrective
Action:
Reset the RM, go to RM_CA02.

EA1F

Description: Event received in wrong state.
Cause: State
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 275
1/03 Honeywell Part I
EA1G

Description: Event received in wrong state.
Cause: State
Corrective
Action:
Reset the RM, go to RM_CA02.

EA1H

Description: Event received in wrong state.
Cause: State
Corrective
Action:
Reset the RM, go to RM_CA02.

EA1I

Description: Event received in wrong state.
Cause: State
Corrective
Action:
Reset the RM, go to RM_CA02.

EA1J

Description: Event received in wrong state.
Cause: State
Corrective
Action:
Reset the RM, go to RM_CA02.

EA1K

Description: Event received in wrong state.
Cause: State
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
276 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
EA1L

Description: Event received in wrong state.
Cause: State
Corrective
Action:
Reset the RM, go to RM_CA02.

EA1M

Description: Event received in wrong state.
Cause: State
Corrective
Action:
Reset the RM, go to RM_CA02.

EA1N

Description: Event received in wrong state.
Cause: State
Corrective
Action:
Reset the RM, go to RM_CA02.

EA1P

Description: Event received in wrong state.
Cause: State
Corrective
Action:
Reset the RM, go to RM_CA02.

EA1Q

Description: Event received in wrong state.
Cause: State
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 277
1/03 Honeywell Part I
EA1R

Description: Switchover complete event with wrong switchover phase.
Cause: Switchover phase.
State.
Corrective
Action:
Reset the RM, go to RM_CA02.

EA1T

Description: Event received in wrong state.
Cause: State
Corrective
Action:
Reset the RM, go to RM_CA02.

EA1U

Description: Event received in wrong state.
Cause: State
Corrective
Action:
Reset the RM, go to RM_CA02.

EA1V

Description: Primary capability checks with a module that is not communicating
has maxed out the number of retries. The state cannot be
determined without primary capability results.
Cause: State
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
278 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
EA1W

Description: Primary capability checks with a module is not working. The state
cannot be determined without primary capability results.
Cause: State.
Error or undefined status from primary capability checks.
Corrective
Action:
Reset the RM, go to RM_CA02.

EA20

Description: Error entering event into transition queue.
Cause: An errno value returned from msgQSend.
Corrective
Action:
Reset the RM, go to RM_CA02.

EA21

Description: Event received in wrong state.
Cause: State
Corrective
Action:
Reset the RM, go to RM_CA02.

EA22

Description: Error entering event into transition queue.
Cause: An errno value returned from msgQSend.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 279
1/03 Honeywell Part I
EA23

Description: Error entering event into transition queue.
Cause: An errno value returned from msgQSend.
Corrective
Action:
Reset the RM, go to RM_CA02.

EA24

Description: Error entering event into transition queue.
Cause: An errno value returned from msgQSend.
Corrective
Action:
Reset the RM, go to RM_CA02.

EA25

Description: Event received in wrong state.
Cause: State
Corrective
Action:
Reset the RM, go to RM_CA02.

EA26

Description: Event received in wrong state.
Cause: State
Corrective
Action:
Reset the RM, go to RM_CA02.

EA27

Description: Event received in wrong state.
Cause: State
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
280 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
EA28

Description: Event received in wrong state.
Cause: State
Corrective
Action:
Reset the RM, go to RM_CA02.

EA29

Description: Event received in wrong state.
Cause: State
Corrective
Action:
Reset the RM, go to RM_CA02.

EA2A

Description: Event received in wrong state.
Cause: State
Corrective
Action:
Reset the RM, go to RM_CA02.

EA2B

Description: Event received in wrong state.
Cause: State
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 281
1/03 Honeywell Part I
EA2C

Description: Switchover complete event with wrong switchover phase.
Cause: Switchover phase.
State.
Corrective
Action:
Reset the RM, go to RM_CA02.

EA2E

Description: Unexpected redundancy state.
Cause: Redundancy state.
Corrective
Action:
Reset the RM, go to RM_CA02.

EA2F

Description: Error completing the state change.
Cause: An errno returned from jbaStateChangeComplete.
Corrective
Action:
Reset the RM, go to RM_CA02.

EA2G

Description: Event received in wrong state.
Cause: State
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
282 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
EA2H

Description: Event received in wrong state.
Cause: State.
Redundancy state stored.
Corrective
Action:
Reset the RM, go to RM_CA02.

EA2I

Description: Unexpected event for primary with qualified secondary.
Cause: Event.
Corrective
Action:
Reset the RM, go to RM_CA02.

EA2J

Description: Error entering event into transition queue.
Cause: An errno value returned from msgQSend.
Corrective
Action:
Reset the RM, go to RM_CA02.

EA2K

Description: Event received in wrong state.
Cause: State
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 283
1/03 Honeywell Part I
EA2L

Description: Error entering event into transition queue.
Cause: An errno value returned from msgQSend.
Corrective
Action:
Reset the RM, go to RM_CA02.

EA2M

Description: Error entering event into transition queue.
Cause: An errno value returned from msgQSend.
Corrective
Action:
Reset the RM, go to RM_CA02.

EA30

Description: Event received in wrong state.
Cause: State
Corrective
Action:
Reset the RM, go to RM_CA02.

EA31

Description: Event received in wrong state.
Cause: State
Corrective
Action:
Reset the RM, go to RM_CA02.

EA32

Description: Event received in wrong state.
Cause: State
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
284 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
EA33

Description: Event received in wrong state.
Cause: State
Corrective
Action:
Reset the RM, go to RM_CA02.

EA34

Description: Event received in wrong state.
Cause: State
Corrective
Action:
Reset the RM, go to RM_CA02.

EA35

Description: Qualification complete event with wrong qualification phase.
Cause: Qualification phase.
State.
Corrective
Action:
Reset the RM, go to RM_CA02.

EA36

Description: Unknown extended error for module requested qualification abort.
Cause: Extended error.
Module slot number.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 285
1/03 Honeywell Part I
EA37

Description: Error entering event into transition queue.
Cause: An errno value returned from msgQSend.
Corrective
Action:
Reset the RM, go to RM_CA02.

EA38

Description: Event received in wrong state.
Cause: State
Corrective
Action:
Reset the RM, go to RM_CA02.

EA39

Description: Error entering event into transition queue.
Cause: An errno value returned from msgQSend.
Corrective
Action:
Reset the RM, go to RM_CA02.

EA3A

Description: Error entering event into transition queue.
Cause: An errno value returned from msgQSend.
Corrective
Action:
Reset the RM, go to RM_CA02.

EA3B

Description: Error entering event into transition queue.
Cause: An errno value returned from msgQSend.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
286 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
EA3C

Description: Error entering event into transition queue.
Cause: An errno value returned from msgQSend.
Corrective
Action:
Reset the RM, go to RM_CA02.

EA3D

Description: Error entering event into transition queue.
Cause: An errno value returned from msgQSend.
Corrective
Action:
Reset the RM, go to RM_CA02.

EA3E

Description: Error entering event into transition queue.
Cause: An errno value returned from msgQSend.
Corrective
Action:
Reset the RM, go to RM_CA02.

EA3F

Description: Error entering event into transition queue.
Cause: An errno value returned from msgQSend.
Corrective
Action:
Reset the RM, go to RM_CA02.

EA3G

Description: Error entering event into transition queue.
Cause: An errno value returned from msgQSend.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 287
1/03 Honeywell Part I
EA3H

Description: Event received in wrong state.
Cause: State
Corrective
Action:
Reset the RM, go to RM_CA02.

EA3I

Description: Event received in wrong state.
Cause: State
Corrective
Action:
Reset the RM, go to RM_CA02.

EA3J

Description: Event received in wrong state.
Cause: State
Corrective
Action:
Reset the RM, go to RM_CA02.

EA3K

Description: Event received in wrong state.
Cause: State
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
288 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
EA3L

Description: Switchover complete event with wrong switchover phase.
Cause: Switchover phase.
State.
Corrective
Action:
Reset the RM, go to RM_CA02.

EA3N

Description: Unexpected redundancy state.
Cause: Redundancy state.
Corrective
Action:
Reset the RM, go to RM_CA02.

EA3P

Description: Event received in wrong state. Primary RM encounters a major
unrecoverable fault during (power-cycle) switchover.
Cause: State
Corrective
Action:
Reset the RM, go to RM_CA02.

EA3Q

Description: Event received in wrong state.
Cause: State.
Redundancy state stored.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 289
1/03 Honeywell Part I
EA3R

Description: Unexpected event for primary with disqualified secondary..
Cause: Event
Corrective
Action:
Reset the RM, go to RM_CA02.

EA3T

Description: Error entering event into transition queue.
Cause: An errno value returned from msgQSend.
Corrective
Action:
Reset the RM, go to RM_CA02.

EA3U

Description: Event received in wrong state.
Cause: State
Corrective
Action:
Reset the RM, go to RM_CA02.

EA3V

Description: Error completing the state change.
Cause: An errno returned from jbaStateChangeComplete.
Corrective
Action:
Reset the RM, go to RM_CA02.

EA40

Description: Event received in wrong state.
Cause: State
Corrective
Action:
None. Disconnect and connect the redundancy cable.

Fault Codes
RM Fault Codes
290 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
EA41

Description: Event received in wrong state.
Cause: State
Corrective
Action:
None. Disconnect and connect the redundancy cable.

EA42

Description: Event received in wrong state.
Cause: State
Corrective
Action:
None. Disconnect and connect the redundancy cable.

EA43

Description: Event received in wrong state.
Cause: State
Corrective
Action:
Reset the RM, go to RM_CA02.

EA44

Description: Event received in wrong state.
Cause: State
Corrective
Action:
Reset the RM, go to RM_CA02.

EA45

Description: Error entering event into transition queue.
Cause: An errno value returned from msgQSend.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 291
1/03 Honeywell Part I
EA46

Description: Event received in wrong state.
Cause: State
Corrective
Action:
Reset the RM, go to RM_CA02.

EA47

Description: Event received in wrong state.
Cause: State
Corrective
Action:
Reset the RM, go to RM_CA02.

EA48

Description: Event received in wrong state.
Cause: State
Corrective
Action:
Reset the RM, go to RM_CA02.

EA49

Description: Event received in wrong state.
Cause: State
Corrective
Action:
Reset the RM, go to RM_CA02.

EA4A

Description: Event received in wrong state.
Cause: State
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
292 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
EA4B

Description: Switchover complete event with wrong switchover phase.
Cause: Switchover phase.
State.
Corrective
Action:
Reset the RM, go to RM_CA02.

EA4C

Description: Unexpected redundancy state from partner.
Cause: Redundancy state.
Corrective
Action:
Reset the RM, go to RM_CA02.

EA4E

Description: Unexpected redundancy state.
Cause: Redundancy state.
Corrective
Action:
Reset the RM, go to RM_CA02.

EA4F

Description: Error completing the state change.
Cause: An errno value returned jbaStateChangeComplete.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 293
1/03 Honeywell Part I
EA4G

Description: Event received in wrong state.
Cause: State
Corrective
Action:
Reset the RM, go to RM_CA02.

EA4H

Description: Unexpected event for primary with no secondary.
Cause: Event
Corrective
Action:
Reset the RM, go to RM_CA02.

EA4I

Description: Error entering event into transition queue.
Cause: An errno value returned from msgQSend.
Corrective
Action:
Reset the RM, go to RM_CA02.

EA4J

Description: Error completing the state change.
Cause: An errno value returned jbaStateChangeComplete.
Corrective
Action:
Reset the RM, go to RM_CA02.

EA4K

Description: Error completing the state change.
Cause: An errno value returned jbaStateChangeComplete.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
294 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
EA4L

Description: Error completing the state change.
Cause: An errno value returned jbaStateChangeComplete.
Corrective
Action:
Reset the RM, go to RM_CA02.

EA4M

Description: Error completing the state change.
Cause: An errno value returned jbaStateChangeComplete.
Corrective
Action:
Reset the RM, go to RM_CA02.

EA50

Description: Error entering event into transition queue.
Cause: An errno value returned from msgQSend.
Corrective
Action:
Reset the RM, go to RM_CA02.

EA51

Description: Event received in wrong state.
Cause: State
Corrective
Action:
Reset the RM, go to RM_CA02.

EA52

Description: Error entering event into transition queue.
Cause: An errno value returned from msgQSend.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 295
1/03 Honeywell Part I
EA53

Description: Error entering event into transition queue.
Cause: An errno value returned from msgQSend.
Corrective
Action:
Reset the RM, go to RM_CA02.

EA54

Description: Error entering event into transition queue.
Cause: An errno value returned from msgQSend.
Corrective
Action:
Reset the RM, go to RM_CA02.

EA55

Description: Event received in wrong state.
Cause: State
Corrective
Action:
Reset the RM, go to RM_CA02.

EA56

Description: Event received in wrong state.
Cause: State
Corrective
Action:
Reset the RM, go to RM_CA02.

EA57

Description: Event received in wrong state.
Cause: State
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
296 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
EA58

Description: Event received in wrong state.
Cause: State
Corrective
Action:
Reset the RM, go to RM_CA02.

EA59

Description: Event received in wrong state.
Cause: State
Corrective
Action:
Reset the RM, go to RM_CA02.

EA5A

Description: Event received in wrong state.
Cause: State
Corrective
Action:
Reset the RM, go to RM_CA02.

EA5B

Description: Switchover complete event with wrong switchover phase.
Cause: Switchover phase.
State.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 297
1/03 Honeywell Part I
EA5D

Description: Unexpected redundancy state.
Cause: Redundancy state.
Corrective
Action:
Reset the RM, go to RM_CA02.

EA5E

Description: Error completing the state change.
Cause: An errno returned from jbaStateChangeComplete.
Corrective
Action:
Reset the RM, go to RM_CA02.

EA5F

Description: Event received in wrong state.
Cause: State
Corrective
Action:
Reset the RM, go to RM_CA02.

EA5G

Description: Unexpected event for primary with standby secondary.
Cause: Event
Corrective
Action:
Reset the RM, go to RM_CA02.

EA5H

Description: Error entering event into transition queue.
Cause: An errno value returned from msgQSend.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
298 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
EA5I

Description: Event received in wrong state.
Cause: State
Corrective
Action:
Reset the RM, go to RM_CA02.

EA5J

Description: Error entering event into transition queue.
Cause: An errno value returned from msgQSend.
Corrective
Action:
Reset the RM, go to RM_CA02.

EA5K

Description: Error entering event into transition queue.
Cause: An errno value returned from msgQSend.
Corrective
Action:
Reset the RM, go to RM_CA02.

EA80

Description: Error entering event into transition queue.
Cause: An errno value returned from msgQSend.
Corrective
Action:
Reset the RM, go to RM_CA02.

EA81

Description: Event received in wrong state.
Cause: State
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 299
1/03 Honeywell Part I
EA82

Description: Error entering event into transition queue.
Cause: An errno value returned from msgQSend.
Corrective
Action:
Reset the RM, go to RM_CA02.

EA83

Description: Error entering event into transition queue.
Cause: An errno value returned from msgQSend.
Corrective
Action:
Reset the RM, go to RM_CA02.

EA84

Description: Event received in wrong state.
Cause: State
Corrective
Action:
Reset the RM, go to RM_CA02.

EA85

Description: Event received in wrong state.
Cause: State
Corrective
Action:
Reset the RM, go to RM_CA02.

EA86

Description: Event received in wrong state.
Cause: State
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
300 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
EA87

Description: Event received in wrong state.
Cause: State
Corrective
Action:
Reset the RM, go to RM_CA02.

EA88

Description: Switchover complete event with wrong switchover phase.
Cause: Switchover phase.
State.
Corrective
Action:
Reset the RM, go to RM_CA02.

EA89

Description: Unexpected redundancy state.
Cause: Redundancy state.
Corrective
Action:
Reset the RM, go to RM_CA02.

EA8A

Description: Error completing the state change.
Cause: An errno value returned from jbaStateChangeComplete.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 301
1/03 Honeywell Part I
EA8B

Description: Unexpected event for qualified secondary with primary.
Cause: Event
Corrective
Action:
Reset the RM, go to RM_CA02.

EA8C

Description: Error entering event into transition queue.
Cause: An errno value returned from msgQSend.
Corrective
Action:
Reset the RM, go to RM_CA02.

EA90

Description: Error entering event into transition queue.
Cause: An errno value returned from msgQSend.
Corrective
Action:
Reset the RM, go to RM_CA02.

EA91

Description: Event received in wrong state. Secondary RM encounters a major
unrecoverable fault during initial synchronization.
Cause: State
Corrective
Action:
Reset the RM (RM_CA02) or cycle power to the secondary chassis.

Fault Codes
RM Fault Codes
302 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
EA92

Description: Error entering event into transition queue.
Cause: An errno value returned from msgQSend.
Corrective
Action:
Reset the RM, go to RM_CA02.

EA93

Description: Error entering event into transition queue.
Cause: An errno value returned from msgQSend.
Corrective
Action:
Reset the RM, go to RM_CA02.

EA94

Description: Event received in wrong state.
Cause: State
Corrective
Action:
Reset the RM, go to RM_CA02.

EA95

Description: Event received in wrong state.
Cause: State
Corrective
Action:
Reset the RM, go to RM_CA02.

EA96

Description: Event received in wrong state.
Cause: State
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 303
1/03 Honeywell Part I
EA97

Description: Switchover complete event with wrong switchover phase.
Cause: Switchover phase.
State.
Corrective
Action:
Reset the RM, go to RM_CA02.

EA98

Description: Unexpected redundancy state.
Cause: Redundancy state.
Corrective
Action:
Reset the RM, go to RM_CA02.

EA99

Description: Error completing the state change.
Cause: An errno value returned from jbaStateChangeComplete.
Corrective
Action:
Reset the RM, go to RM_CA02.

EA9A

Description: Unexpected event for primary with standby secondary.
Cause: Event.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
304 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
EA9B

Description: Error entering event into transition queue.
Cause: An errno value returned from msgQSend.
Corrective
Action:
Reset the RM, go to RM_CA02.

EAA0

Description: Event received in wrong state.
Cause: State
Corrective
Action:
None. Disconnect and connect the redundancy cable.

EAA1

Description: Event received in wrong state.
Cause: State
Corrective
Action:
None. Disconnect and connect the redundancy cable.

EAA2

Description: Event received in wrong state.
Cause: State
Corrective
Action:
Reset the RM, go to RM_CA02.

EAA3

Description: Event received in wrong state.
Cause: State
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 305
1/03 Honeywell Part I
EAA4

Description: Error entering event into transition queue.
Cause: An errno value returned from msgQSend.
Corrective
Action:
Reset the RM, go to RM_CA02.

EAA5

Description: Error entering event into transition queue.
Cause: An errno value returned from msgQSend.
Corrective
Action:
Reset the RM, go to RM_CA02.

EAA6

Description: Event received in wrong state.
Cause: State
Corrective
Action:
Reset the RM, go to RM_CA02.

EAA7

Description: Event received in wrong state.
Cause: State
Corrective
Action:
Reset the RM, go to RM_CA02.

EAA8

Description: Event received in wrong state.
Cause: State
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
306 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
EAA9

Description: Event received in wrong state.
Cause: State
Corrective
Action:
Reset the RM, go to RM_CA02.

EAAA

Description: Event received in wrong state.
Cause: State
Corrective
Action:
Reset the RM, go to RM_CA02.

EAAB

Description: Event received in wrong state.
Cause: State
Corrective
Action:
Reset the RM, go to RM_CA02.

EAAC

Description: Switchover complete event with wrong switchover phase.
Cause: Switchover phase.
State.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 307
1/03 Honeywell Part I
EAAD

Description: Unexpected redundancy state from partner.
Cause: Redundancy state.
Corrective
Action:
Reset the RM, go to RM_CA02.

EAAF

Description: Unexpected redundancy state.
Cause: Redundancy state.
Corrective
Action:
Reset the RM, go to RM_CA02.

EAAG

Description: Error completing the state change.
Cause: An errno value returned from jbaStateChangeComplete.
Corrective
Action:
Reset the RM, go to RM_CA02.

EAAH

Description: Event received in wrong state.
Cause: State
Corrective
Action:
Reset the RM, go to RM_CA02.

EAAI

Description: Unexpected event for disqualified secondary with no primary.
Cause: Event
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
308 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
EAAJ

Description: Error entering event into transition queue.
Cause: An errno value returned from msgQSend.
Corrective
Action:
Reset the RM, go to RM_CA02.

EAAK

Description: Error completing the state change.
Cause: An errno value returned from jbaStateChangeComplete.
Corrective
Action:
Reset the RM, go to RM_CA02.

EAAL

Description: Error completing the state change.
Cause: An errno value returned from jbaStateChangeComplete.
Corrective
Action:
Reset the RM, go to RM_CA02.

EAAM

Description: Error completing the state change.
Cause: An errno value returned from jbaStateChangeComplete.
Corrective
Action:
Reset the RM, go to RM_CA02.

EAAN

Description: Error completing the state change.
Cause: An errno value returned from jbaStateChangeComplete.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 309
1/03 Honeywell Part I
EAB0

Description: Error entering event into transition queue.
Cause: An errno value returned from msgQSend.
Corrective
Action:
Reset the RM, go to RM_CA02.

EAB1

Description: Event received in wrong state.
Cause: State
Corrective
Action:
Reset the RM, go to RM_CA02.

EAB2

Description: Error entering event into transition queue.
Cause: An errno value returned from msgQSend.
Corrective
Action:
Reset the RM, go to RM_CA02.

EAB3

Description: Error entering event into transition queue.
Cause: An errno value returned from msgQSend.
Corrective
Action:
Reset the RM, go to RM_CA02.

EAB4

Description: Event received in wrong state.
Cause: State
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
310 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
EAB5

Description: Event received in wrong state.
Cause: State
Corrective
Action:
Reset the RM, go to RM_CA02.

EAB6

Description: Event received in wrong state.
Cause: State
Corrective
Action:
Reset the RM, go to RM_CA02.

EAB7

Description: Event received in wrong state.
Cause: State
Corrective
Action:
Reset the RM, go to RM_CA02.

EAB8

Description: Switchover complete event with wrong switchover phase.
Cause: Switchover phase.
State.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 311
1/03 Honeywell Part I
EAB9

Description: Unexpected redundancy state.
Cause: Redundancy state.
Corrective
Action:
Reset the RM, go to RM_CA02.

EABA

Description: Error completing the state change.
Cause: An errno value returned from jbaStateChangeComplete.
Corrective
Action:
Reset the RM, go to RM_CA02.

EABB

Description: Unexpected event for standby secondary with primary.
Cause: Event
Corrective
Action:
Reset the RM, go to RM_CA02.

EABC

Description: Error entering event into transition queue.
Cause: An errno value returned from msgQSend.
Corrective
Action:
Reset the RM, go to RM_CA02.

EAC0

Description: Error posting event.
Cause: An errno value.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
312 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
EAC1

Description: Error posting urgent event priority.
Cause: An errno value.
Corrective
Action:
Reset the RM, go to RM_CA02.

EAC2

Description: Error posting undefined event priority.
Cause: An errno value.
Corrective
Action:
Reset the RM, go to RM_CA02.

EAC3

Description: Error posting event.
Cause: An errno value.
Corrective
Action:
Reset the RM, go to RM_CA02.

EAC4

Description: Error entering event into main queue.
Cause: An errno value returned from msgQSend.
Corrective
Action:
Reset the RM, go to RM_CA02.

EADO

Description: Error writing to relay.
Cause: An errno value returned from write.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 313
1/03 Honeywell Part I
EAD1

Description: Error writing to LED.
Cause: An errno value returned from write.
Corrective
Action:
Reset the RM, go to RM_CA02.

EAD2

Description: Error writing to relay.
Cause: An errno value returned from write.
Corrective
Action:
Reset the RM, go to RM_CA02.

EAD3

Description: Error writing to LED.
Cause: An errno value returned from write.
Corrective
Action:
Reset the RM, go to RM_CA02.

EAD4

Description: Error writing to relay.
Cause: An errno value returned from write.
Corrective
Action:
Reset the RM, go to RM_CA02.

EAD5

Description: Error writing to LED.
Cause: An errno value returned from write.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
314 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
EAD6

Description: Error writing to relay.
Cause: An errno value returned from write.
Corrective
Action:
Reset the RM, go to RM_CA02.

EAD7

Description: Error writing to LED.
Cause: An errno value returned from write.
Corrective
Action:
Reset the RM, go to RM_CA02.

EAD8

Description: Error writing to relay.
Cause: An errno value returned from write.
Corrective
Action:
Reset the RM, go to RM_CA02.

EAD9

Description: Error writing to LED.
Cause: An errno value returned from write.
Corrective
Action:
Reset the RM, go to RM_CA02.

EADA

Description: Error writing to relay.
Cause: An errno value returned from write.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 315
1/03 Honeywell Part I
EADB

Description: Error writing to LED.
Cause: An errno value returned from write.
Corrective
Action:
Reset the RM, go to RM_CA02.

EADC

Description: Error writing to relay.
Cause: An errno value returned from write.
Corrective
Action:
Reset the RM, go to RM_CA02.

EADD

Description: Error writing to LED.
Cause: An errno value returned from write.
Corrective
Action:
Reset the RM, go to RM_CA02.

EADE

Description: Error writing to relay.
Cause: An errno value returned from write.
Corrective
Action:
Reset the RM, go to RM_CA02.

EADF

Description: Error writing to LED.
Cause: An errno value returned from write.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
316 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
EADG

Description: Unknown redundancy state handle.
Cause: Redundancy state handle.
Corrective
Action:
Reset the RM, go to RM_CA02.

EAE0

Description: RMs have the same serial number. The state cannot be
determined.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

EAE1

Description: RMs have the same serial number. The state cannot be
determined.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

EAE2

Description: RMs have the same serial number. The state cannot be
determined.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 317
1/03 Honeywell Part I
EAE3

Description: Unknown redundancy state handle.
Cause: Redundancy state handle.
Corrective
Action:
Reset the RM, go to RM_CA02.

EAE4

Description: Unexpected event for rules.
Cause: Event.
Corrective
Action:
Reset the RM, go to RM_CA02.

EAE5

Description: Primary capability checks with a module that is not communicating
has maxed out the number of retries. The state cannot be
determined without primary capability results.
Cause: State.
Corrective
Action:
Reset the RM, go to RM_CA02.

EAE6

Description: Primary capability checks with a module that is not communicating
has maxed out the number of retries. The state cannot be
determined without primary capability results.
Cause: State.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
318 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
EAE7

Description: Primary capability checks with a module that is not communicating
has maxed out the number of retries. The state cannot be
determined without primary capability results.
Cause: State.
Corrective
Action:
Reset the RM, go to RM_CA02.

EAE8

Description: Primary capability checks with a module that is not communicating
has maxed out the number of retries. The state cannot be
determined without primary capability results.
Cause: State.
Corrective
Action:
Reset the RM, go to RM_CA02.

EAE9

Description: Primary capability checks with a module is not working. The state
cannot be determined without primary capability results.
Cause: State.
Corrective
Action:
Reset the RM, go to RM_CA02.

EAEA

Description: Primary capability checks with a module is not working. The state
cannot be determined without primary capability results.
Cause: State.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 319
1/03 Honeywell Part I
EAEB

Description: Primary capability checks with a module is not working. The state
cannot be determined without primary capability results.
Cause: State.
Corrective
Action:
Reset the RM, go to RM_CA02.

EAEC

Description: Primary capability checks with a module is not working. The state
cannot be determined without primary capability results.
Cause: State.
Corrective
Action:
Reset the RM, go to RM_CA02.

EAF0

Description: Unknown redundancy state handle.
Cause: Redundancy state handle.
Corrective
Action:
Reset the RM, go to RM_CA02.

EAF1

Description: Unknown rule interruption reason.
Cause: Rule interruption reason.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
320 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
EAF2

Description: Unknown rule interruption reason.
Cause: Rule interruption reason.
Corrective
Action:
Reset the RM, go to RM_CA02.

EAF3

Description: Unknown rule interruption reason.
Cause: Rule interruption reason.
Corrective
Action:
Reset the RM, go to RM_CA02.

EAF4

Description: Unknown redundancy state handle.
Cause: Redundancy state handle.
Corrective
Action:
Reset the RM, go to RM_CA02.

EAF5

Description: Rule failed to complete. At Startup, the RM encountered a
Redundancy state resolution rule failure.
Cause: State.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 321
1/03 Honeywell Part I
EAG0

Description: Unknown rule determined state.
Cause: Rule determined state.
Corrective
Action:
Reset the RM, go to RM_CA02.

EAG1

Description: Unknown rule determined state.
Cause: Rule determined state.
Corrective
Action:
Reset the RM, go to RM_CA02.

EAG2

Description: Unknown rule determined state.
Cause: Rule determined state.
Corrective
Action:
Reset the RM, go to RM_CA02.

EAG3

Description: Unknown redundancy state handle.
Cause: Redundancy state handle.
Corrective
Action:
Reset the RM, go to RM_CA02.

EAH0

Description: Unknown rule determined state.
Cause: Rule determined state.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
322 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
EAH1

Description: Unknown rule determined state.
Cause: Rule determined state.
Corrective
Action:
Reset the RM, go to RM_CA02.

EAH2

Description: Unknown rule determined state.
Cause: Rule determined state.
Corrective
Action:
Reset the RM, go to RM_CA02.

EAH3

Description: Unknown redundancy state handle.
Cause: Redundancy state handle.
Corrective
Action:
Reset the RM, go to RM_CA02.

EAI0

Description: Unknown rule determined state.
Cause: Rule determined state.
Corrective
Action:
Reset the RM, go to RM_CA02.

EAI1

Description: Unknown redundancy state handle.
Cause: Redundancy state handle.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 323
1/03 Honeywell Part I
EAJ0

Description: Error writing to relay.
Cause: An errno value returned from write.
Corrective
Action:
Reset the RM, go to RM_CA02.

EAJ1

Description: Error writing to LED.
Cause: An errno value returned from write.
Corrective
Action:
Reset the RM, go to RM_CA02.

EB00

Description: The configuration log is empty (and ICP_TEST_L is NOT asserted).
Cause:
Corrective
Action:
Assert ICP_TEST_L and reset the RM in order to have the RM auto-
program the configuration log with default values.

EB01

Description: The last entry in the configuration log was corrupt, and the previous
two entries could also not be read.
Cause:
Corrective
Action:
Assert ICP_TEST_L and reset the RM in order to have the RM auto-
program the configuration log with default values.

Fault Codes
RM Fault Codes
324 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
EB02

Description: The last entry in the configuration log was corrupt, and the previous
two entries could also not be read.
Cause:
Corrective
Action:
Assert ICP_TEST_L and reset the RM in order to have the RM auto-
program the configuration log with default values.

EB03

Description: The last entry in the configuration log was corrupt, and the previous
two entries could also not be read.
Cause:
Corrective
Action:
Assert ICP_TEST_L and reset the RM in order to have the RM auto-
program the configuration log with default values.

EB05

Description: Problems recovering a corrupted configuration log (trying to erase
corrupted log).
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

EB06

Description: Problems recovering a corrupted configuration log (trying to write
valid entry to replace corrupted log).
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 325
1/03 Honeywell Part I
EB10

Description: Unable to take semaphore for the FLASH device.
Cause: An errno value returned from semTake.
Corrective
Action:
Reset the RM, go to RM_CA02.

EB11

Description: Unable to take semaphore for event log.
Cause: An errno value returned from semTake.
Corrective
Action:
Reset the RM, go to RM_CA02.

EB12

Description: Unable to take semaphore for configuration log.
Cause: An errno value returned from semTake.
Corrective
Action:
Reset the RM, go to RM_CA02.

EB13

Description: Unable to take semaphore for event log.
Cause: An errno value returned from semTake.
Corrective
Action:
Reset the RM, go to RM_CA02.

EB14

Description: Unable to take semaphore for configuration log.
Cause: An errno value returned from semTake.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
326 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
EB15

Description: Unable to write new entry to configuration log.
Cause:
Corrective
Action:
Try to write a new configuration entry (by making a configuration
change), or assert ICP_TEST_L and reset the RM (RM_CA02).
Replacing the RM (RM_CA01) may be necessary.

EB16

Description: Unable to erase the next sector for the configuration log.
Cause:
Corrective
Action:
Try to write a new configuration entry (by making a configuration
change), or assert ICP_TEST_L and reset the RM (RM_CA02).
Replacing the RM (RM_CA01) may be necessary.

EC00

Description: Unable to create semaphore for application resource table.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

EC01

Description: Unable to create semaphore for the request forwarding array.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 327
1/03 Honeywell Part I
EC02

Description: Unable to take semaphore for the application resource table.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

EC03

Description: Unable to give semaphore for the application resource table.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

EC04

Description: Unable to give semaphore for the application resource table.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

EC05

Description: A send was requested for an invalid port.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

EC06

Description: Unable to take semaphore for the request forwarding array.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
328 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
EC07

Description: Unable to create link consumer for the multicast connection.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

ED00

Description: Unable to start watchdog used for updating the partners current
time.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

ED10

Description: Unable to allocate a combuf for sending new offset from CST.
Cause:
Corrective
Action:
None.

ED11

Description: Unable to allocate an UCMM resource for sending time update to
partner.
Cause:
Corrective
Action:
None.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 329
1/03 Honeywell Part I
ED12

Description: Invalid response handle received.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

ED13

Description: Unable to start watchdog used for updating the partners current
time.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

ED14

Description: Unable to allocate a combuf for sending new time to partner WCT
object.
Cause:
Corrective
Action:
None.

ED20

Description: Unable to take semaphore used synchronize the wall clock time
task.
Cause: An errno value returned from semTake.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
330 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
ED21

Description: Unable to allocate combuf for sending GET_ATTRIBUTES_ALL
request to partner WCT object.
Cause: An errno value returned from semTake.
Corrective
Action:
None.

ED22

Description: Unable to allocate an UCMM resource for sending
GET_ATTRIBUTES_ALL request to partner WCT object.
Cause:
Corrective
Action:
None.

ED23

Description: Unable to start watchdog used for updating the partners current
time.
Cause: An errno value returned from wdStart.
Corrective
Action:
Reset the RM, go to RM_CA02.

ED30

Description: Unable to read application revision from configuration log.
Cause: An errno value returned from cfgReadAppRevision.
Corrective
Action:
None.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 331
1/03 Honeywell Part I
ED31

Description: Unable to write application revision to configuration log.
Cause: An errno value returned from cfgWriteAppRevision.
Corrective
Action:
None.

EE00

Description: DC_FAIL Interrupt has occured.
Cause: Value of the hardware watchdog timer register.
RM watchdog count value.
Corrective
Action:
If the chassis did not actually power down, reset the RM. Go to
RM_CA02.

EF00

Description: Unable to post event to the NVS Object.
Cause: An errno value returned from msgQSend.
Corrective
Action:
Reset the RM, go to RM_CA02.

EF10

Description: Received unhandled event.
Cause: Event type received.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
332 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
EF11

Description: Error when receiving messages from message queue.
Cause: An errno value returned from msgQReceive.
Corrective
Action:
Reset the RM, go to RM_CA02.

EF20

Description: Unable to read message from NVS Task message queue.
Cause: An errno value returned from msgQReceive.
Corrective
Action:
Reset the RM, go to RM_CA02.

EF21

Description: Unable to prepare response buffer for an update service request.
Cause:
Corrective
Action:
None.

EF22

Description: The pointer to the response routine was NULL.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

EF23

Description: Unable to prepare response buffer for a transfer service request.
Cause:
Corrective
Action:
None.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 333
1/03 Honeywell Part I
EF24

Description: The pointer to the response routine was NULL. Unable to send
response to transfer service request.
Cause:
Corrective
Action:
None.

EF30

Description: Received unknown event.
Cause: Event received.
Corrective
Action:
None.

EG02

Description: A second major unrecoverable fault has been declared.
Cause: Fault code of second major fault declared.
First argument of second major fault declared.
Corrective
Action:
Follow the action of the first major fault declared (probably reset the
RM).

EG10

Description: The default exception handler was called by the OS.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
334 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
EG11

Description: The reboot handler was called by the OS.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

EH01

Description: Unable to create a message queue for Self Test Object events.
Cause: An errno value returned from msgQCreate.
Corrective
Action:
Reset the RM, go to RM_CA02.

EH02

Description: Unable to spawn the Self Test Object event handling task.
Cause: An errno value returned from taskSpawn.
Corrective
Action:
Reset the RM, go to RM_CA02.

EH03

Description: Unable to create a watchdog timer for use in timing Self Test Object
operations.
Cause: An errno value returned from wdCreate.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 335
1/03 Honeywell Part I
EH04

Description: Unable to create a semaphore for use in Self Test Object
scheduling.
Cause: An errno value returned from semBCreate.
Corrective
Action:
Reset the RM, go to RM_CA02.

EH05

Description: Unable to create a semaphore for use in coordinating Self Test
Object operations with Switchovers.
Cause: An errno value returned from semBCreate.
Corrective
Action:
Reset the RM, go to RM_CA02.

EH06

Description: Unable to spawn the Self Test Object test scheduling task.
Cause: An errno value returned from taskSpawn.
Corrective
Action:
Reset the RM, go to RM_CA02.

EH07

Description: Unable to register the Self Test Object with the ICP Toolkit
(Backplane comm).
Cause: An errno value returned from classRegister.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
336 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
EH0A

Description: A failure occurred in a Self Test Object attempt to take a semaphore
which blocks self tests during a switchover.
Cause: An errno value returned from semTake.
Corrective
Action:
Reset the RM, go to RM_CA02.

EH10

Description: Error occurred in reception of an event message.
Cause: An errno value returned from msgQReceive.
Corrective
Action:
Reset the RM, go to RM_CA02.

EH11

Description: Failed in attempt to forward events to partner RM.
Cause: Status (no zero) value returned from stoForwardFaultEvent.
Corrective
Action:
Reset the RM, go to RM_CA02.

EH12

Description: An invalid event type accompanied a request to forward an event to
the partner RM.
Cause: Event type which accompanied request.
Current errno value.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 337
1/03 Honeywell Part I
EH20

Description: Failed attempt to allocate a comm buffer.
Cause: An errno value returned from ComBuf_Malloc.
Corrective
Action:
None.

EH21

Description: Failed attempt to open a connection to the partner RM.
Cause: An errno value returned from bcUcmmOpen.
Corrective
Action:
None.

EH22

Description: Failed attempt to send a request to the partner RM.
Cause: An errno value returned from bcUcmmSendRequest.
Corrective
Action:
None.

EH23

Description: Failed (BAD HANDLE) attempt to close connection with the partner
RM.
Cause: An errno value returned from bcUcmmClose.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
338 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
EH24

Description: Failed (BAD HANDLE) attempt to close connection with the partner
RM.
Cause: An errno value returned from bcUcmmClose.
Corrective
Action:
Reset the RM, go to RM_CA02.

EH25

Description: Failed (BAD HANDLE) attempt to close connection with the partner
RM.
Cause: An errno value returned from bcUcmmClose.
Corrective
Action:
Reset the RM, go to RM_CA02.

EH26

Description: Failed attempt to recycle connection with the partner RM.
Cause: An errno value returned from bcUcmmRecycle.
Corrective
Action:
Reset the RM, go to RM_CA02.

EH27

Description: Failed (BAD HANDLE) attempt to close connection with the partner
RM.
Cause: An errno value returned from bcUcmmClose.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 339
1/03 Honeywell Part I
EH28

Description: Invalid or false Secondary Device Status collection state
encountered while awaiting response from the partner RM.
Cause: State enumeration.
Corrective
Action:
None.

EH29

Description: Failed (BAD HANDLE) attempt to close connection with the partner
RM.
Cause: An errno value returned from bcUcmmClose.
Corrective
Action:
Reset the RM, go to RM_CA02.

EH2A

Description: A failure occurred in a Self Test Objects preliminary attempt to take
a semaphore which blocks this function during a switchover.
Cause: An errno value returned from semTake.
Corrective
Action:
Reset the RM, go to RM_CA02.

EH2B

Description: A failure occurred in a Self Test Objects final (just prior to sending a
request message) attempt to take a semaphore which blocks this
function during a switchover.
Cause: An errno value returned from semTake.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
340 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
EH30

Description: Failed attempt to allocate a comm buffer.
Cause: An errno value returned from ComBuf_Malloc.
Corrective
Action:
None.

EH3A

Description: A failure occurred in a Self Test Objects preliminary attempt to take
a semaphore which blocks this function during a switchover.
Cause: An errno value returned from semTake.
Corrective
Action:
Reset the RM, go to RM_CA02.

EH31

Description: Failed attempt to open a connection to the partner RM.
Cause: An errno value returned from bcUcmmOpen.
Corrective
Action:
None.

EH32

Description: Failed attempt to send a request to the partner RM.
Cause: An errno value returned from bcUcmmSendRequest.
Corrective
Action:
None.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 341
1/03 Honeywell Part I
EH33

Description: Failed (BAD HANDLE) attempt to close connection with the partner
RM.
Cause: An errno value returned from bcUcmmClose.
Corrective
Action:
Reset the RM, go to RM_CA02.

EH34

Description: Failed (BAD HANDLE) attempt to close connection with the partner
RM.
Cause: An errno value returned from bcUcmmClose.
Corrective
Action:
Reset the RM, go to RM_CA02.

EH35

Description: Failed (BAD HANDLE) attempt to close connection with the partner
RM.
Cause: An errno value returned from bcUcmmClose.
Corrective
Action:
Reset the RM, go to RM_CA02.

EH36

Description: Failed attempt to recycle connection with the partner RM.
Cause: An errno value returned from bcUcmmRecycle.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
342 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
EH37

Description: Failed (BAD HANDLE) attempt to close connection with the partner
RM.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

EH38

Description: Invalid or false Secondary SYS_FAIL_L Subsystem Status collection
state encountered while awaiting response from the partner RM.
Cause: State enumeration.
Corrective
Action:
None.

EH39

Description: Failed (BAD HANDLE) attempt to close connection with the partner
RM.
Cause: An errno value returned from bcUcmmClose.
Corrective
Action:
Reset the RM, go to RM_CA02.

EH40

Description: Failed attempt to allocate a comm buffer.
Cause: An errno value returned from ComBuf_Malloc.
Corrective
Action:
None.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 343
1/03 Honeywell Part I
EH41

Description: Failed attempt to open a connection to the partner RM.
Cause: An errno value returned from bcUcmmOpen.
Corrective
Action:
None.

EH42

Description: Failed attempt to send a request to the partner RM.
Cause: An errno value returned from bcUcmmSendRequest.
Corrective
Action:
None.

EH43

Description: Failed (BAD HANDLE) attempt to close connection with the partner
RM.
Cause: An errno value returned from bcUcmmClose.
Corrective
Action:
Reset the RM, go to RM_CA02.

EH44

Description: Failed (BAD HANDLE) attempt to close connection with the partner
RM.
Cause: An errno value returned from bcUcmmClose.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
344 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
EH45

Description: Failed (BAD HANDLE) attempt to close connection with the partner
RM.
Cause: An errno value returned from bcUcmmClose.
Corrective
Action:
Reset the RM, go to RM_CA02.

EH46

Description: Failed attempt to recycle connection with the partner RM.
Cause: An errno value returned from bcUcmmClose.
Corrective
Action:
Reset the RM, go to RM_CA02.

EH47

Description: Failed (BAD HANDLE) attempt to close connection with the partner
RM.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

EH48

Description: Invalid or false Forward Fault Event collection state encountered
while awaiting response from the partner RM.
Cause: State enumeration.
Corrective
Action:
None.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 345
1/03 Honeywell Part I
EH49

Description: Failed (BAD HANDLE) attempt to close connection with the partner
RM.
Cause: An errno value returned from bcUcmmClose.
Corrective
Action:
Reset the RM, go to RM_CA02.

EH4A

Description: A failure occurred in a Self Test Objects preliminary attempt to take
a semaphore which blocks this function during a switchover.
Cause: An errno value returned from semTake.
Corrective
Action:
Reset the RM, go to RM_CA02.

EH50

Description: Failed attempt to allocate a comm buffer.
Cause: An errno value returned from ComBuf_Malloc.
Corrective
Action:
None.

EH5A

Description: A failure occurred in a Self Test Objects preliminary attempt to take
a semaphore which blocks this function during a switchover.
Cause: An errno value returned from semTake.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
346 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
EH51

Description: Failed attempt to open a connection to the partner RM.
Cause: Status value returned from bcUcmmOpen.
An errno value returned from bcUcmmOpen.
Corrective
Action:
None.

EH52

Description: Failed attempt to send a request to the partner RM.
Cause: Status value returned from bcUcmmSendRequest.
An errno value returned from bcUcmmSendRequest.
Corrective
Action:
None.

EH53

Description: Status of test response not SUCCESS.
Cause: Status value returned.
An errno value returned.
Corrective
Action:
None.

EH60

Description: Failed attempt to post an event in the Self Test Object Event Queue.
Cause: Event type.
An errno value returned from msgQSend.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 347
1/03 Honeywell Part I
EH70

Description: Device Status Read - Problem encountered in preparing a response
buffer.
Cause:
Corrective
Action:
None.

EH71

Description: Device Status Read - Routine handling a prepared response
encountered a fault.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

EH72

Description: SYS_FAIL Results Read - Problem encountered in preparing a
response buffer
Cause:
Corrective
Action:
None.

EH73

Description: SYS_FAIL Results Read - Routine handling a prepared response
encountered a fault.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
348 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
EH74

Description: Reset Test Stats - Problem encountered in preparing a response
buffer.
Cause:
Corrective
Action:
None.

EH75

Description: Reset Test Stats - Routine handling a prepared response
encountered a fault
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

EH76

Description: Set User Relay - Problem encountered in preparing a response
buffer
Cause:
Corrective
Action:
None.

EH77

Description: Set User Relay - Routine handling a prepared response
encountered a fault.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 349
1/03 Honeywell Part I
EH78

Description: STO Loopback Test - Problem encountered in preparing a response
buffer.
Cause:
Corrective
Action:
None.

EH79

Description: STO Loopback Test - Routine handling a prepared response
encountered a fault.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

EH7A

Description: Forward Partner Fault - Problem encountered in preparing a
response buffer.
Cause:
Corrective
Action:
None.

EH7B

Description: Forward Partner Fault - Invalid event type.
Cause: Event type.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
350 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
EH7C

Description: Forward partner Fault - Routine handling a prepared response
encountered a fault.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

EH7D

Description: A failure occurred in a outsdie processs attempt to take a
semaphore that would block testing during a switchover.
Cause: An errno value returned from semTake.
Corrective
Action:
Reset the RM, go to RM_CA02.

EHA1

Description: Invalid test pulse state returned after an attempted SYS_FAIL_L
test.
Cause: Test pulse state enumeration.
Corrective
Action:
Reset the RM, go to RM_CA02.

EHA2

Description: Failed attempt to allocate a comm buffer for use in sending a
SYS_FAIL_L test request to another module.
Cause: An errno value returned from ComBuf_Malloc.
Corrective
Action:
None.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 351
1/03 Honeywell Part I
EHA3

Description: Failed attempt to open a connection to another module for the sake
of sending a test request.
Cause:
Corrective
Action:
None.

EHA4

Description: Failed attempt to send a test request to another module.
Cause: An errno value returned from UCMM_SendRequest.
Corrective
Action:
None.

EHA5

Description: Failed attempt to close a connection following the unsuccessful
sending of a test request to another module.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

EHA6

Description: Failed attempt to close a connection following a NOT READY
response to a test request to another module.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
352 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
EHA7

Description: Failed attempt to close a connection following a READY response to
a test request to another module.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

EHA8

Description: Failed attempt to close a connection following a COMMS ERROR or
NEEDS RETRY response to a test request to another module.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

EHA9

Description: Invalid test status response state encountered regarding a test
request to another module.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

EHAA

Description: Failed attempt to allocate a comm buffer for use in sending a
SYS_FAIL_L test status request to another module.
Cause:
Corrective
Action:
None.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 353
1/03 Honeywell Part I
EHAB

Description: Failed attempt to open a connection to another module for the sake
of sending a test status request.
Cause:
Corrective
Action:
None.

EHAC

Description: Failed attempt to send a test status request to another module.
Cause:
Corrective
Action:
None.

EHAD

Description: Failed attempt to close a connection following the unsuccessful
sending of a test status request to another module.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

EHAE

Description: Failed attempt to close a connection following an UNSUPPORTED,
BUSY, or COMPLETE response to a test request to another
module.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
354 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
EHAF

Description: Failed attempt to close a connection following an NEEDS RETRY,
WAIT, or COMM ERR, or unrecognized response to a test request
to another module.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

EHAG

Description: Local SYS_FAIL_L input circuitry has failed local loopback test.
Specifics on cause are unknown.
Cause:
Corrective
Action:
Replace RM (RM_CA01) at earliest opportunity. This RM will not
support Synchronization if in a Secondary.

EHAH

Description: Local SYS_FAIL_L input circuitry has failed local loopback test.
Interrupt portion was found to be faulty.
Cause:
Corrective
Action:
Replace RM (RM_CA01) at earliest opportunity. This RM will not
support Synchronization if in a Secondary.

EHAJ

Description: Local SYS_FAIL_L input circuitry has failed local loopback test.
Status read portion was found to be faulty.
Cause:
Corrective
Action:
Replace RM (RM_CA01) at earliest opportunity. This RM will not
support Synchronization if in a Secondary.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 355
1/03 Honeywell Part I
EHAK

Description: Local SYS_FAIL_L input circuitry has failed local loopback test.
Local driver portion was found to be faulty.
Cause:
Corrective
Action:
Replace RM (RM_CA01) at earliest opportunity. This RM will not
support Synchronization if in a Secondary.

EHAL

Description: Local SYS_FAIL_L input circuitry has failed local loopback test.
Status read portion was found to be faulty.
Cause:
Corrective
Action:
Replace RM (RM_CA01) at earliest opportunity. This RM will not
support Synchronization if in a Secondary.

EHAM

Description: Local SYS_FAIL_L input circuitry has failed local loopback test.
Status read occurred, but interrupt did not.
Cause:
Corrective
Action:
Replace RM (RM_CA01) at earliest opportunity. This RM will not
support Synchronization if in a Secondary.

EHAN

Description: Local SYS_FAIL_L input circuitry has failed local loopback test.
Invalid test results.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02. If error persists, contact Honeywell
TAC.

Fault Codes
RM Fault Codes
356 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
EHAP

Description: A failure occurred in a Self Test Objects attempt to take a
semaphore which would block scanning for new modules during a
switchover.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

EHAR

Description: A failure occurred in a Self Test Objects attempt to take a
semaphore which would block SYS_FAIL_L assertion testing during
a switchover.
Cause: An errno value returned from semTake.
Corrective
Action:
Reset the RM, go to RM_CA02.

EHAT

Description: A failure occurred in a Self Test Objects preliminary attempt to take
a semaphore which blocks the sending of a test status request to
another module during a switchover.
Cause: An errno value returned from semTake.
Corrective
Action:
Reset the RM, go to RM_CA02.

EHAV

Description: A failure occurred in a Self Test Objects attempt to take a
semaphore which would block sending a test request to another
module during a switchover.
Cause: An errno value returned from semTake.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 357
1/03 Honeywell Part I
EI00

Description: During a shutdown, a fault occurred while attempting to unregister
Workstation Display Object with backplance communications
subsystem.
Cause:
Corrective
Action:
None. A shutdown situation.

EI01

Description: During a shutdown, a fault occurred while attempting to delete the
Workstation Display Object task.
Cause: An errno value returned from taskDelete.
Corrective
Action:
None. A shutdown situation.

EI02

Description: During a shutdown, a fault occurred while attempting to delete a
Workstation Display Object semaphore.
Cause: An errno value returned from semDelete.
Corrective
Action:
None. A shutdown situation.

EI03

Description: During a shutdown, a fault occurred while attempting to delete a
Workstation Display Object watchdog timer.
Cause: An errno value returned from wdDelete.
Corrective
Action:
None. A shutdown situation.

Fault Codes
RM Fault Codes
358 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
EI10

Description: A failure occurred in a Workstation Display Object attempt to start a
scheduling (watchdog) semaphore.
Cause: An errno value returned from wdStart.
Corrective
Action:
Reset the RM, go to RM_CA02.

EI40

Description: A failure occurred in a Workstation Display Object attempt to start a
scheduling (watchdog) semaphore.
Cause: An errno value returned from wdStart.
Corrective
Action:
Reset the RM, go to RM_CA02.

EI50

Description: A failure occurred in a Workstation Display Object attempt to read all
RM Configuration Data (via cfgReadAllData).
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

EI51

Description: A failure occurred in a Workstation Display Object attempt to write
all RM Configuration Data (via cfgWriteNewData).
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 359
1/03 Honeywell Part I
EI52

Description: A failure occurred in a Workstation Display Object attempt to
prepare a response buffer.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

EI53

Description: A failure occurred in a Workstation Display Object call to the
response handling routine.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

EI60

Description: A failure occurred in a Workstation Display Object attempt to
initialize its attributes.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

EI61

Description: A failure occurred in a Workstation Display Object attempt to create
a scheduling watchdog timer.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
360 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
EI62

Description: A failure occurred in a Workstation Display Object attempt to create
a scheduling semaphore.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

EI63

Description: A failure occurred in a Workstation Display Object attempt to spawn
itself.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

EI64

Description: A failure occurred in a Workstation Display Object attempt to register
with the comm ports.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

EI70

Description: A failure occurred in a Workstation Display Object attempt to start a
scheduling watchdog timer.
Cause: An errno value returned from wdStart.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 361
1/03 Honeywell Part I
EI71

Description: A failure occurred in a Workstation Display Object attempt to take a
scheduling semaphore.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

EI72

Description: A failure occurred in a Workstation Display Object request to other
RM objects to refresh their stale data.
Cause: An errno value returned from semTake.
Corrective
Action:
Reset the RM, go to RM_CA02.

EI73

Description: A failure occurred in a Workstation Display Object attempt to
determine its next refresh delay.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

EI74

Description: A failure occurred in a Workstation Display Object attempt to start a
scheduling watchdog timer.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
362 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
EI75

Description: A failure occurred in a Workstation Display Object attempt to take a
scheduling semaphore.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

EI80

Description: A failure occurred in a Workstation Display Object request to BCO to
updates stale attributes.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

EI81

Description: A failure occurred in a Workstation Display Object request to Devce
Object to updates stale attributes.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

EI90

Description: A failure occurred in a Workstation Display Object attempt to read
RM Revision (cfgReadRevision).
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 363
1/03 Honeywell Part I
EIZ0

Description: A failure occurred in a Workstation Display Object attempt to take a
scheduling (watchdog) semaphore.
Cause: An errno value returned from wdCreate.
Corrective
Action:
Reset the RM, go to RM_CA02.

EJ00

Description: Unable to read serial number from configuration log.
Cause:
Corrective
Action:
Reset ( RM_CA02) or replace the RM (RM_CA01).

EJ01

Description: Unable to read the vendor ID from the configuration log.
Cause:
Corrective
Action:
Reset ( RM_CA02) or replace the RM (RM_CA01).

EJ02

Description: Unable to register the ICP Object with the ICP Toolkit.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
364 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
EJ10

Description: Unable to register the ICP Object with the ICP Toolkit.
Cause:
Corrective
Action:
None.

EJ11

Description: Response routine for the SET_ATTRIBUTES_ALL request is NULL.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

EJ12

Description: Unable to prepare a response buffer for a RESET request.
Cause:
Corrective
Action:
None.

EJ13

Description: Response routine for the RESET request is NULL.
Cause:
Corrective
Action:
None.

EJ20

Description: A supervisory request to the ICP ASIC failed.
Cause: State of supervisory control block.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 365
1/03 Honeywell Part I
EK10

Description: Error sending event to main watchdog manager queue.
Cause: An errno value returned from msgQSend.
Corrective
Action:
Reset the RM, go to RM_CA02.

EK21

Description: RM hardware watchdog timer test failed. The watchdog timer was
disabled after being enabled.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

EK22

Description: RM hardware watchdog timer test failed. The watchdog timer was
not counting.
Cause:
Corrective
Action:
Reset the RM, go to RM_CA02.

EK23

Description: Error receiving event from main watchdog manager queue.
Cause: An errno value returned from msgQReceive.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
366 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
EK24

Description: All of the asynchronous tasks being checked did not report to the
watchdog manager on time.
Cause: Task number (upper 16 bits); number of watchdog kicks (lower
16 bits).
Asynchronous tasks reporting.
Corrective
Action:
Reset the RM, go to RM_CA02.

EK25

Description: The timer clock task did not report to the watchdog manager on
time.
Cause: Task number (upper 16 bits); number of watchdog kicks (lower
16 bits).
Synchronous tasks reporting.
Corrective
Action:
Reset the RM, go to RM_CA02.

EK26

Description: The self-test object task did not report to the watchdog manager on
time.
Cause: Task number (upper 16 bits); number of watchdog kicks (lower
16 bits).
Synchronous tasks reporting.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 367
1/03 Honeywell Part I
EK27

Description: The collect attributes task did not report to the watchdog manager
on time.
Cause: Task number (upper 16 bits); number of watchdog kicks (lower
16 bits).
Synchronous tasks reporting.
Corrective
Action:
Reset the RM, go to RM_CA02.

EK28

Description: The wall clock time object task did not report to the watchdog
manager on time.
Cause: Task number (upper 16 bits); number of watchdog kicks (lower
16 bits).
Asynchronous tasks reporting.
Corrective
Action:
Reset the RM, go to RM_CA02.

EK29

Description: The workstation display object task did not report to the watchdog
manager on time.
Cause: Task number (upper 16 bits); number of watchdog kicks (lower
16 bits).
Asynchronous tasks reporting.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
368 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
EK2A

Description: Unknown task index.
Cause: Task index.
Corrective
Action:
Reset the RM, go to RM_CA02.

EK2B

Description: Unknown event for watchdog manager to process.
Cause: Event.
Corrective
Action:
Reset the RM, go to RM_CA02.

EK2C

Description: The event log object task did not report to the watchdog manager on
time. Primary RM encounters a major shutdown fault during (power-
cycle) switchover.
Cause: Task number (upper 16 bits); number of watchdog kicks (lower
16 bits).
Asynchronous tasks reporting.
Corrective
Action:
Reset the RM, go to RM_CA02. If problem persists, go to
GEN_CA01.

EK40

Description: Error starting the watchdog for checking tasks.
Cause: An errno value returned from wdStart.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 369
1/03 Honeywell Part I
EK70

Description: Error starting the watchdog for kicking the hardware watchdog.
Cause: An errno value returned from wdStart.
Corrective
Action:
Reset the RM, go to RM_CA02.

EKA0

Description: Error sending watchdog report in event to backup communications
unconnected message manager receive task.
Cause: An errno value returned from msgQSend.
Corrective
Action:
Reset the RM, go to RM_CA02.

EKC0

Description: Error sending watchdog report in event to backup communications
link producer receive task.
Cause: An errno value returned from msgQSend.
Corrective
Action:
Reset the RM, go to RM_CA02.

EKD0

Description: Error sending watchdog report in event to ICP link producer receive
task.
Cause: An errno value returned from msgQSend.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
370 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
EKE0

Description: Error sending watchdog report in event to ICP link consummer
receive task.
Cause: An errno value returned from msgQSend.
Corrective
Action:
Reset the RM, go to RM_CA02.

EKF0

Description: Error sending watchdog report in event to ICP link consummer
receive task.
Cause: An errno value returned from msgQSend.
Corrective
Action:
Reset the RM, go to RM_CA02.

EKG0

Description: Error sending watchdog report in event to ICP unconnected
message manager receive task.
Cause: An errno value returned from msgQSend.
Corrective
Action:
Reset the RM, go to RM_CA02.

EKT1

Description: Unknown task index.
Cause: Task index.
Corrective
Action:
Reset the RM, go to RM_CA02.

Fault Codes
RM Fault Codes
Release 100 Experion PKS Troubleshooting and Notifications Reference 371
1/03 Honeywell Part I
EKU0

Description: Unknown task index.
Cause: Task index.
Corrective
Action:
Reset the RM, go to RM_CA02.


Fault Codes
RM Fault Codes
372 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03

Release 100 Experion PKS Troubleshooting and Notifications Reference 373
1/03 Honeywell Part I
Experion PKS Notifications
CPM FB Generated Notifications
Backup State

Description: State Change Event generated by the secondary CPM to indicate
the CPM is executing in the secondary redundancy role.
Cause: Startup or role change (e.g. switchover) into the secondary
redundancy role.
Corrective
Action:
N/A

Battery Not OK

Description: There are two types of batteries used for CPM memory retention: {1}
the lithium battery in the front of the CPM and {2} the Ni-Cad Battery
Extension Module (BEM) residing in the chassis. This Diagnostic
Alarm indicates either that {1} neither type of battery is present nor
of proper voltage or {2} both batteries are present and of proper
voltage. Note that having two batteries (of proper voltage) present is
a minor fault condition.
Cause: Defective battery or invalid battery configuration.
Corrective
Action:
Replace defective battery or correct invalid battery configuration
CPM_CA07.

Not Synchronized

Description: The primary and/or secondary CPM generates the Not
Synchronized Diagnostic Alarm notification either upon redundancy
startup (i.e. detection of RM) or detection of loss-of-synchronization.
The primary and secondary CPM generates the Not Synchronized
return-to-normal notification once synchronization is achieved.
Cause: Many causes that are scrutinized within the corrective action.
Corrective
Action:
Isolate reason for loss-of-synchronization CPM_CA03.

Experion PKS Notifications
CPM FB Generated Notifications
374 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
RAM Sweep Error(s)

Description: Diagnostic Alarm to indicate that a CPM run-time diagnostic was
unable to correct a DRAM single bit error.
Cause: Defective CPM memory.
Corrective
Action:
Restart the CPM CPM_CA05.If problem persists, replace the CPM
CPM_CA06.

RAM Scrub Errors

Description: Diagnostic Alarm to indicate that the CPM encountered more than
10 single bit errors in one pass of the entire DRAM.
Cause: Defective CPM memory and/or high temperatures.
Corrective
Action:
Restart the CPM CPM_CA05.If problem persists, replace the CPM
CPM_CA06.

REDUN Chassis ID Unknown

Description: System Info Event to inform the user that the RM has not yet notified
the CPM in which physical chassis it resides.
Cause: This CPM generation of this notification indicates {1} a transient
condition during RM startup or {2} an abnormal condition whereby
the RM was visible to the CPM but has failed to broadcast its
physical chassis ID setting.
Corrective
Action:
Check the RM resident in the CPM chassis CPM_CA08.

REDUN Chassis ID A

Description: System Info Event to inform the user that the CPM resides in
redundancy chassis A.
Cause: The RM broadcasts its physical chassis ID setting to the CPM either
{1} upon completion of startup or {2} when the user changes the
physical chassis ID designation.
Corrective
Action:
N/A

Experion PKS Notifications
CPM FB Generated Notifications
Release 100 Experion PKS Troubleshooting and Notifications Reference 375
1/03 Honeywell Part I
REDUN Chassis ID B

Description: System Info Event to inform the user that the CPM resides in
redundancy chassis B.
Cause: The RM broadcasts its physical chassis ID setting to the CPM either
{1} upon completion of startup or {2} when the user changes the
physical chassis ID designation.
Corrective
Action:
N/A

Switchover

Description: System Info Event to indicate a redundancy switchover role change
operation has occurred. Since the Not Synchronized alarm
notification is also generated as a consequence of the switchover
operation, it is sufficient for the Switchover notification to only be a
System Info Event (i.e. detail as to the cause of loss-of-
synchronization).
Cause: Redundancy role change due to a fault in the primary chassis or the
receipt of the Switchover command.
Corrective
Action:
N/A

Sync Checksum Fail

Description: Diagnostic Alarm to indicate the secondary CPM has detected
Synchronization Checksum comparison failure. The
Synchronization Checksum is a synchronization maintenance
integrity verification whereby the synchronized secondary CPM
computes a local database checksum for verification with one
calculated on the primary CPM. This represents a specific cause for
persistent loss-of-synchronization which requires the secondary
CPM to be restarted and/or replaced.
Cause: Data corruption during transmission from primary to secondary CPM
(across redundancy cable) or Secondary CPM memory corruption.
Corrective
Action:
Restart the CPM CPM_CA05.If problem persists, replace the CPM
CPM_CA06.

Experion PKS Notifications
CPM FB Generated Notifications
376 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Sync HW Failure

Description: Diagnostic Alarm to indicate that the primary CPM or secondary
CPM has detected synchronization hardware failure. Moreover,
problem detected either due to use of the synchronization hardware
or during execution of the run-time synchronization hardware
diagnostic. The corrective action for this persistent loss-of-
synchronization depends on the CPM redundancy role as follows.
Cause: Synchronization hardware (i.e. Tracker mechanism) failure.
Corrective
Action:
If the CPM is being used in a non-redundant configuration, replace
the CPM CPM_CA06 at the users earliest convenience.
If the CPM is currently in the primary redundancy role, attempt
switchover to better primary CPM_CA15. Note that commanded
initial synchronization causes the CPM to internally reset this failure
condition, and if the synchronization hardware failure occurs
infrequently, this provides the user a potential avenue from which to
replace bad CPM HW that is currently in the primary role without
loss of control.
If the CPM is currently in the secondary redundancy role, first restart
the CPM CPM_CA05. If problem persists, replace the CPM
CPM_CA06.

Experion PKS Notifications
NDM Generated Notifications
Release 100 Experion PKS Troubleshooting and Notifications Reference 377
1/03 Honeywell Part I
NDM Generated Notifications
Overview
The Network Diagnostic Manager (NDM) monitors the devices physically present that
are not explicitly configured as part of the users control strategy. As a consequence,
NDM uses an auto-identification scheme that generates unique names for each device
based on the path used to communicate with the device. First, the list of devices of
interest to NDM is as follows:

CNI ControlNet Interface module
ENET Ethernet Interface module
KTC (ISA Bus) PC to ControlNet interface card.
PCIC (PCI Bus) PC to ControlNet interface card.
GW ControlNet Gateway for either Non-Hazardous Rail I/O or
Hazardous Rail I/O.
LD Fieldbus Linking Device
PLC Family of programmable logic controllers
CL Control Logix 5550 controller
RM Redundancy Module
FIM Fieldbus Interface Module

Furthermore, the NDM only cares about the following RSLinx driver types:

CNETDRVR RSLinx ControlNet Driver
ENETDRVR RSLinx Ethernet Driver

One of the following formatted segments is concatenated to the device/driver base names
in the above tables to form the overall device/driver notification Point ID. Note that each
lower case letter-pair below represents a numeric value with the range 00 - 99.

Experion PKS Notifications
NDM Generated Notifications
378 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
dd RSLinx Driver ID (dd). This format is used to uniquely identify the
RSLinx driver in the event that more than one driver of the same
type exists. The numerical value is derived from the zero-based
offset into the RSLinx configured driver list (i.e. not related to the
user-configured driver name string). Furthermore, this format is also
used to identify a device residing on the supervisory Ethernet
segment.
For example, if ENETDRVR05 is the NDM generated name for a
RSLinx Ethernet driver, then ENET05 is the name of the
Supervisory Ethernet Interface module, associated with
ENETDRVR05, against which the event/alarm is reported.
ddss RSLinx Ethernet Driver ID (dd) + Chassis Slot (ss). This format is
used to identify a device residing in the same chassis as an Ethernet
Interface module attached to the supervisory Ethernet segment.
More specifically, (dd) identifies the RSLinx Ethernet driver used by
NDM to communicate with the device residing in slot (ss) of the
same chassis as the Ethernet interface module associated with
driver (dd).
For example, if ENETDRVR05 is the NDM generated name for a
RSLinx Ethernet driver, then CNI0503 is the CNI downlink in a
controller chassis attached to the Supervisory Ethernet via ENET05
which resides in the same chassis. Note that CNI0503 forms the
head of an IO subnet against which the event/alarm is reported.
ddssmm RSLinx Ethernet Driver ID (dd) + Chassis Slot (ss) + ControlNet
Subnet Mac ID (mm). This format is used to identify a device
residing on a ControlNet subnet that is reached by traversing a
chassis attached to the supervisory Ethernet. More specifically, (dd)
identifies the RSLinx Ethernet driver used by NDM to communicate
with the chassis containing both an Ethernet interface module
associated with the RSLinx driver (dd) and a CNI downlink in slot
(ss) attached to the ControlNet subnet node at MAC ID (mm).
For example, if ENETDRVR05 is the NDM generated name for a
RSLinx Ethernet driver and CNI0503 is the CNI downlink in a
controller chassis attached to the Supervisory Ethernet via ENET05,
then LD050302 is a Fieldbus Linking Device residing on the
ControlNet subnet against which the event/alarm is reported.
ddmm RSLinx ControlNet Driver ID (dd) + Supervisory Mac ID (mm). This
format is used to identify a device residing on the supervisory
ControlNet segment. More specifically, (dd) identifies the RSLinx
ControlNet Driver ID used by NDM to communicate with the device
residing at MAC ID (mm).
Experion PKS Notifications
NDM Generated Notifications
Release 100 Experion PKS Troubleshooting and Notifications Reference 379
1/03 Honeywell Part I
For example, if CNETDRVR00 is the NDM generated name for a
RSLinx ControlNet driver then PCIC0020 is the name assigned to
the PC to ControlNet interface card, configured for MAC ID 20 &
associated with CNETDRVR00, against which the event/alarm is
reported.
ddmmss RSLinx ControlNet Driver ID (dd) + Supervisory Mac ID (mm) +
Chassis Slot (ss). This format is used to identify a device residing in
the same chassis as a ControlNet Interface module attached to the
supervisory ControlNet segment. More specifically, (dd) identifies
the RSLinx ControlNet driver used by NDM to communicate with the
device residing at MAC ID (mm) in chassis slot (ss).
For example, if CNETDRVR00 is the NDM generated name for a
RSLinx ControlNet driver, then CNI000103 is the CNI downlink in a
controller chassis attached to the Supervisory ControlNet via
CNI0001 which resides in the same chassis. Note that CNI000103
forms the head of an IO subnet against which the event/alarm is
reported.
ddmmsscc RSLinx ControlNet Driver ID (dd) + Supervisory Mac ID (mm) +
Chassis Slot (ss) + ControlNet Subnet Mac ID (cc). This format is
used to identify a device residing on a ControlNet subnet that is
reached by traversing a chassis attached to the supervisory
ControlNet. More specifically, (dd) identifies the RSLinx ControlNet
driver used by NDM to communicate with the chassis containing
both a CNI attached to the Supervisory ControlNet segment at MAC
ID (mm) and a CNI downlink in slot (ss) attached to the ControlNet
subnet node at MAC ID (cc).
For example, if CNETDRVR00 is the NDM generated name for a
RSLinx ControlNet driver and CNI000103 is the CNI downlink in a
controller chassis attached to the Supervisory Ethernet via CNI0001,
then LD00010302 is a Fieldbus Linking Device residing on the
ControlNet subnet against which the event/alarm is reported.

Note that for all of the device and driver notifications, the actual user-configured RSLinx
driver name string is embedded as a prefix of the notification description to provide
explicit association to the RSLinx driver ID. The following subsections describe all
possible notification descriptions generated by the NDM.
Experion PKS Notifications
NDM Generated Notifications
380 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
BOOTP Enabled

Description: Diagnostic Alarm to indicate that the BootP setting of the specified
ENET module is enabled.
Cause: User forgot to disable BootP after updating the ENET modules IP
address.
Corrective
Action:
Utilize the Network Tools application to disable the BootP setting of
the specified ENET module.

Cable Failure

Description: Diagnostic Alarm to indicate ControlNet cable failure. Note that the
faulted cable (i.e. Cable A or Cable B) is specified to remove
ambiguity in dual media systems.
Cause: ControlNet cable disconnected and/or defective.
Corrective
Action:
Use the NDM generated Point ID (e.g. CNI0007) with the specified
cable as the starting point to begin network fault isolation.

Card Added

Description: System Info Event to indicate that the NDM detected the presence
of a device of interest.
Cause: Module inserted in the chassis while power still applied (IUP), power
applied to the chassis, or redundant controller chassis switchover
has occurred.
Corrective
Action:
N/A

Card Failure

Description: Diagnostic Alarm to indicate that the specified device has explicitly
returned a not healthy status.
Cause: Module faulted.
Corrective
Action:
Restart and/or replace module based on fault code.

Experion PKS Notifications
NDM Generated Notifications
Release 100 Experion PKS Troubleshooting and Notifications Reference 381
1/03 Honeywell Part I
Card Removed

Description: System Info Event to indicate that the NDM detected the absence of
the specified device which was previously present.
Cause: Module removed in the chassis while power still applied (RUP),
power removed to the chassis, or redundant controller chassis
switchover has occurred.
Corrective
Action:
N/A

Comm Failure

Description: System Info Event to indicate that the NDM was not able to
communicate with the specified device.
Cause: NDM is not able to communicate to the specified device because
either {1} the specified device is removed or {2} as a consequence
of an intermittent communication problem. The former may occur as
a consequence of redundant controller chassis switchover. The
latter may be due to diminished unconnected communication
bandwidth somewhere in between the PC (i.e. on which the NDM
runs) and the specified device.
Corrective
Action:
N/A if this notification precedes device removal. Otherwise, use the
Network Tools application to investigate diminished communication
bandwidth between the PC and the specified device.

Driver Added

Description: System Info Event to indicate that the NDM detected the presence
of a new ControlNet or Ethernet RSLinx driver.
Cause: New RSLinx driver configured.
Corrective
Action:
N/A

Experion PKS Notifications
NDM Generated Notifications
382 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Driver Removed

Description: System Info Event to indicate that the NDM detected the absence of
a previously configured ControlNet or Ethernet RSLinx driver.
Cause: RSLinx driver deleted.
Corrective
Action:
N/A

Intermittent Comm Failure

Description: The NDM executes as a continuous loop performing two phases of
operation: {1} single topology scan to find any new devices and/or
drivers, and {2} multiple iterations of querying status from the list of
known devices. This generic Diagnostic Alarm indicates that the
NDM was not able to communicate with one or more devices in two
consecutive device-query iterations.
Cause: NDM is not able to communicate to one or more devices because
either {1} the specified device is removed or {2} as a consequence
of an intermittent communication problem. The former may occur as
a consequence of redundant controller chassis switchover. The
latter may be due to diminished unconnected communication
bandwidth somewhere in between the PC (i.e. on which the NDM
runs) and the device(s).
Corrective
Action:
Refer to the Event Journal in search of any recent Comm Failure
and/or Card Removed System Info Events to determine what
specific device(s) with which the NDM has trouble communicating.
Be aware that removal of a device (e.g. PCIC) required for
communication with other downstream devices results in NDM
reporting communication errors against the other downstream
devices. Repair/replace any device that was unexpectedly
removed, and/or use the Network Tools application to investigate
communication bandwidth between the PC and the specified
device(s).

Experion PKS Notifications
NDM Generated Notifications
Release 100 Experion PKS Troubleshooting and Notifications Reference 383
1/03 Honeywell Part I
Invalid Keeper

Description: Diagnostic Alarm to indicate that a Keeper capable ControlNet
resident device does not indicate the Master Keeper Status or
Backup Keeper Status.
Cause: Either {1} there is no Master Keeper on the affected ControlNet
segment or {2} the specified devices programmed ControlNet
parameters disagree with the ControlNet parameters being asserted
by the Master Keeper.
Corrective
Action:
Utilize the Network Tools application to reprogram the ControlNet
parameters for the either {1} the entire ControlNet segment or {2}
just the specified device.

KTC Failure

Description: Either as part of NDM startup initialization or as a consequence of
being unable to communicate with any devices during a portion of
the topology scan, the NDM searches the NT Event Log in search of
KTC related events. This Diagnostic Alarm indicates that the most
recent encountered KTC related event was a KTC tombstone
event (as opposed to a KTC started successfully event).
Cause: The presence of a KTC tombstone event implicitly indicates KTC
card failure.
Corrective
Action:
Restart RSLinx, which indirectly resets the KTC.

KTC Normal

Description: Diagnostic Alarm return-to-normal to indicate either KTC card failure
recovery or that the KTC is healthy as part of NDM startup
initialization. More specifically, the NDM searches the NT Event Log
in search of KTC related events and encounters the started
successfully event.
Cause: KTC device started successfully.
Corrective
Action:
N/A

Experion PKS Notifications
NDM Generated Notifications
384 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Missing Keeper

Description: Diagnostic Alarm to indicate that a ControlNet segment does not
have a Master Keeper.
Cause: Either {1} all Keeper capable devices are in a Keeper Status other
than Master or Backup (e.g. Faulted Keeper Status) or {2} there are
no Keeper capable devices present on the affected ControlNet
segment.
Corrective
Action:
Either {1} Utilize the Network Tools application to reprogram the
ControlNet parameters for the affected ControlNet segment to
appropriate values (e.g. NUT 10000, UMAX 20, and SMAX 1) or {2}
add a Keeper capable device to the affected ControlNet segment.

PCIC Failure

Description: Either as part of NDM startup initialization or as a consequence of
being unable to communicate with any devices during a portion of
the topology scan, the NDM searches the NT Event Log in search of
PCIC related events. This Diagnostic Alarm indicates that the most
recent encountered PCIC related event was a PCIC tombstone
event (as opposed to a PCIC started successfully event).
Cause: The presence of a PCIC tombstone event implicitly indicates PCIC
card failure.
Corrective
Action:
Restart RSLinx, which indirectly resets the PCIC.

PCIC Normal

Description: Diagnostic Alarm return-to-normal to indicate either PCIC card
failure recovery or that the PCIC is healthy as part of NDM startup
initialization. More specifically, the NDM searches the NT Event Log
in search of PCIC related events and encounters the started
successfully event.
Cause: PCIC device started successfully.
Corrective
Action:
N/A

Experion PKS Notifications
NDM Generated Notifications
Release 100 Experion PKS Troubleshooting and Notifications Reference 385
1/03 Honeywell Part I
RSLinx Initialization Failure

Description: Diagnostic Alarm to indicate that the NDM is unable to initialize a
RSLinx session.
Cause: Either {1} incompatible version of RSLinx software or {2} RSLinx not
running.
Corrective
Action:
{1} Verify that the appropriate version of RSLinx software is installed
for the specific software release in use or {2} restart the RSLinx
service.

RSLinx Initialized

Description: Diagnostic Alarm return-to-normal to indicate that the NDM
successfully initialized a RSLinx session.
Cause: N/A
Corrective
Action:
N/A

RSLinx Failure

Description: Diagnostic Alarm to indicate RSLinx service failure.
Cause: RSLinx service failure.
Corrective
Action:
Restart RSLinx service.

RSLinx Normal

Description: Diagnostic Alarm return-to-normal to indicate RSLinx service failure
recovery.
Cause: N/A
Corrective
Action:
N/A

Experion PKS Notifications
NDM Generated Notifications
386 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
UMAX Exceeded

Description: Diagnostic Alarm to indicate that a ControlNet segment has strayed
from the expected UMAX ControlNet network parameter.
Cause: Either {1} there is no Master Keeper on the affected ControlNet
segment or {2} the ControlNet parameters being asserted by the
Master Keeper are not valid.
Corrective
Action:
Utilize the Network Tools application to reprogram the ControlNet
parameters for the affected ControlNet segment to appropriate
values (e.g. NUT 10000, UMAX 20, and SMAX 1).


Release 100 Experion PKS Troubleshooting and Notifications Reference 387
1/03 Honeywell Part I
RM Events
Overview
An individual RM log entry specifies the following information:

This Field: Means:
Entry Number Sequential number, unique to each entry.
Module Type of module that submitted the event based on its Product
Type and Product Code attributes.
Slot Number Slot number of module that submitted the event.
Serial Number Serial Number of module that submitted the event.
Source In addition to viewing the RMs log the Network Tools utility
allows the user to the RMs copy of its partner RMs log. To
distinguish which RM log is being displayed the Network Tools
utility specifies the RM log source as T or O for This RM or
the Other RM respectively.
Event Class Represents the event classification.
Event ID Module-specific event.
Extended Event
Info.
Module-specific extended event data.
Event Time-stamp Time that event was observed on module that submitted the
event.
Logging Time-
stamp
RM time that event was stored into the event log.

RM Events
CNI Generated RM Events
388 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
CNI Generated RM Events
ControlNet Lonely

Number: 0x0000
Description: CNI is lonely on ControlNet.
Cause: Cable disconnected or network related problem.
Corrective
Action:
Connect the appropriate ControlNet cables so that the CNI may join
the intended network and/or apply power to other nodes on the
network.

ControlNet Not Lonely

Number: 0x0001
Description: CNI recovered from ControlNet lonely condition.
Cause: ControlNet cables attached, or recovery from network problem.
Corrective
Action:
N/A.

NetWork Entity Gone

Number: 0x0002
Description: The primary CNI lost the connection with its redundant partner
across the RM private-path (i.e. the redundancy cable).
Cause: Secondary CNI faulted/removed, one or both of the RMs
faulted/removed or the redundancy cable is faulted/disconnected.
Corrective
Action:
If the secondary CNI or secondary RM is faulted, power-cycle the
secondary chassis.
If the primary RM is faulted, remove and reinsert the primary RM
with chassis-power applied (or power-cycle the primary chassis if
not performing control).
Reattach the redundancy cable if it is disconnected.

RM Events
CNI Generated RM Events
Release 100 Experion PKS Troubleshooting and Notifications Reference 389
1/03 Honeywell Part I
MacID Switches Changed to Bad

Number: 0x0003
Description: MAC switches changed from setting captured during CNI powerup
state.
Cause: Deficient CNI hardware or user inadvertently changed the MAC
switches with power applied to the CNI.
Corrective
Action:
If the user was not changing the CNI MAC switch setting, replace
the CNI. Otherwise, if the user was changing the CNI MAC switch
setting, restore to original value or power-cycle the CNI for the new
value to take effect.

MacID Switches Changed to OK

Number: 0x0004
Description: MAC switches returned to setting captured during CNI powerup
state.
Cause: User restored the MAC switches to original setting.
Corrective
Action:
If the user was not changing the CNI MAC switch setting, replace
the CNI.

Bad CNet Ping for Sec Connection

Number: 0x0005
Description: The primary CNI encountered a ping error response while
attempting to communicate with its redundant partner across the
ControlNet path.
Cause: Obvious problems include secondary CNI lonely, faulted, or missing.
Obscure problems include the case where the ControlNet trunk
cable is broken in between the primary and secondary CNI but each
CNI is not lonely.
Corrective
Action:
If one of the CNIs is lonely, connect the appropriate ControlNet
cables so that the CNI may join the intended network.
Use the Network Tools utility to verify that the CNI redundant pair is
visible on the same ControlNet subnet.

RM Events
CNI Generated RM Events
390 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
ControlNet Duplicate Node

Number: 0x0006
Description: CNI encountered Duplicate Node condition.
Cause: CNI with duplicate MAC switch settings exists on the same
ControlNet subnet.
Corrective
Action:
User must determine which CNI has the improperly configured MAC
switch settings and reconfigure it with the appropriate (i.e. not in use
MAC ID) setting. Affected CNIs must be power-cycled to go to
proper MAC ID settings.

ControlNet Unduplicate Node

Number: 0x0007
Description: CNI recovered from Duplicate Node condition.
Cause: CNI with duplicate MAC switch settings removed from the network.
Corrective
Action:
N/A

Revision Not Compatible

Number: 0x0008
Description: The primary CNI module compatibility test failed because the
redundant partner has incompatible firmware.
Cause: The secondary CNI has incompatible firmware.
Corrective
Action:
Update the CNI firmware.

RM Events
CNI Generated RM Events
Release 100 Experion PKS Troubleshooting and Notifications Reference 391
1/03 Honeywell Part I
Node Number Not Identical

Number: 0x0009
Description: The primary CNI module compatibility test failed because the
redundant partner CNI MAC Switch setting is not identical to that of
the primary CNI.
Cause: Incorrect redundant CNI installation or attempt to use spare-CNI
without setting the appropriate MAC ID.
Corrective
Action:
Adjust secondary CNI MAC Switch setting to be identical to that of
the primary partner CNI.

Partner Not Scanner

Number: 0x000A
Description: The primary CNI has detected that the redundancy compliant
partner in the same slot of the secondary chassis is not a CNI.
Cause: Incorrect module type in the same slot number of the secondary
chassis.
Corrective
Action:
Replace module in same slot of the secondary chassis with a
redundancy compliant CNI (with the same single/dual media
capability and same MAC ID switch setting as the primary CNI).

Not Recognized Vendor

Number: 0x000B
Description: The primary CNI has detected that the redundancy compliant
partner in the same slot of the secondary chassis is not a compatible
CNI.
Cause: Incorrect module type in the same slot number of the secondary
chassis.
Corrective
Action:
Replace module in same slot of the secondary chassis with a
redundancy compliant CNI (with the same single/dual media
capability and same MAC ID switch setting as the primary CNI).

RM Events
CNI Generated RM Events
392 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Not Compatible Vendor

Number: 0x000C
Description: The primary CNI has detected that the redundancy compliant
partner in the same slot of the secondary chassis is not a compatible
CNI.
Cause: One CNI specifies AB as the vendor and the other CNI specifies
Honeywell as the vendor.
Corrective
Action:
Replace one of the CNIs such that the resulting redundant CNI pair
specifies the same vendor.

Unrecognized Product Code

Number: 0x000D
Description: The primary CNI has detected that the redundancy compliant
partner in the same slot of the secondary chassis is not a CNI.
Cause: Incorrect module type in the same slot number of the secondary
chassis.
Corrective
Action:
Replace module in same slot of the secondary chassis with a
redundancy compliant CNI (with the same single/dual media
capability and same MAC ID switch setting as the primary CNI).

False ControlNet Partner

Number: 0x000E
Description: The primary CNI does not reside on the same ControlNet subnet, as
does the secondary CNI.
Cause: ControlNet trunk broken in between the redundant pair of CNIs or
invalid installation.
Corrective
Action:
The redundant CNI pair must reside on the same ControlNet subnet.
Perform network fault isolation to ensure this requirement is
satisfied.

RM Events
CNI Generated RM Events
Release 100 Experion PKS Troubleshooting and Notifications Reference 393
1/03 Honeywell Part I
Keeper Info Not Identical

Number: 0x000F
Description: The primary CNI keeper information not identical to the secondary
CNI.
Cause: Incorrect CNI installation or attempt to use spare-CNI (previously
programmed with different keeper parameters).
Corrective
Action:
Use the Network Tools utility to correct whichever CNI does not
specify either the Honeywell default or the user network specific
keeper parameters.

Incompatible Product Code

Number: 0x0010
Description: The primary CNI has detected that the redundancy compliant
partner in the same slot of the secondary chassis is not a compatible
CNI.
Cause: One CNI is dual media and the other CNI is single media.
Corrective
Action:
Replace CNI that does not agree with the intended single or dual
network configuration.

ControlNet Ping Transmit Problem

Number: 0x0011
Description: The CNI (primary or secondary) encountered a problem sending
ControlNet ping to the secondary partner.
Cause: ControlNet trunk broken in between the redundant pair of CNIs or
invalid installation.
Corrective
Action:
The redundant CNI pair must reside on the same ControlNet subnet.
Perform network fault isolation to ensure this requirement is
satisfied.

RM Events
CNI Generated RM Events
394 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
ControlNet Ping Transmit Success

Number: 0x0012
Description: The CNI (primary or secondary) recovered from inability to send
ControlNet ping to the secondary partner.
Cause: The redundant CNI pair now resides on the same ControlNet
subnet.
Corrective
Action:
N/A

ICP debug - NoIcpCbFree

Number: 0x0013
Description: Event used during CNI development to indicate no free ICP CBs.
This event is generated prior to the CNI entering the faulted state.
Cause: Software defect or defective CNI hardware.
Corrective
Action:
If a secondary CNI is faulted, power-cycle the secondary chassis.
If a primary CNI is faulted, remove and reinsert the CNI with
chassis-power applied (or power-cycle the primary chassis if not
performing control).
If the problem persists, replace the CNI.

ICP debug - BadIcpFreeCbId

Number: 0x0014
Description: Event used during CNI development to indicate invalid ICP CB ID.
This event is generated prior to the CNI entering the faulted state.
Cause: N/A
Corrective
Action:
If a secondary CNI is faulted, power-cycle the secondary chassis.
If a primary CNI is faulted, remove and reinsert the CNI with
chassis-power applied (or power-cycle the primary chassis if not
performing control).
If the problem persists, replace the CNI.

RM Events
CNI Generated RM Events
Release 100 Experion PKS Troubleshooting and Notifications Reference 395
1/03 Honeywell Part I
ICP debug - IcpCbFree0

Number: 0x0015
Description: Event used during CNI development to indicate down to last free
ICP CB. This event is generated prior to the CNI entering the
faulted state.
Cause: N/A
Corrective
Action:
If a secondary CNI is faulted, power-cycle the secondary chassis.
If a primary CNI is faulted, remove and reinsert the CNI with
chassis-power applied (or power-cycle the primary chassis if not
performing control).
If the problem persists, replace the CNI.

Smac Spontaneous ListenOnly_Mute

Number: 0x0016
Description: The CNIs ControlNet interface (SMAC) chip can no longer transmit.
Code has been added to prevent this from happening during
redundancy role change (e.g. switchover). However, it can still
happen at powerup. The CNI restarts its SMAC chip as a
consequence.
Cause: N/A
Corrective
Action:
N/A

Keeper Write

Number: 0x0017
Description: The CNI that posted this event has determined that its Keeper
parameters have been corrupted.
Cause: Defective flash ROM.
Corrective
Action:
Attempt to reprogram the Keeper parameters using the Network
Tools utility.
If that doesnt work, replace the CNI.

RM Events
CNI Generated RM Events
396 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Partner Detected

Number: 0x0018
Description: The primary CNI has attempted to trigger initial synchronization due
to successful attempt to connect to secondary partner after prior
attempts failed.
Cause: Secondary CNI insertion with chassis power applied.
Corrective
Action:
N/A

Smac Fail

Number: 0x0019
Description: The CNI has detected that its ControlNet interface (SMAC) chip has
failed its powerup or run-time diagnostics. This event is generated
prior to the CNI entering the faulted state.
Cause: CNI SMAC chip diagnostic failure.
Corrective
Action:
If a secondary CNI is faulted, power-cycle the secondary chassis.
If a primary CNI is faulted, remove and reinsert the CNI with
chassis-power applied (or power-cycle the primary chassis if not
performing control).
If the problem persists, replace the CNI.

Illegal Partner Compat. Status

Number: 0x001A
Description: The primary CNI has aborted an initial synchronization attempt due
to wrong partner compatibility status.
Cause: Incorrect secondary CNI compatibility status.
Corrective
Action:
Power-cycle the secondary chassis or disconnect-and-reconnect the
redundancy cable.

RM Events
CNI Generated RM Events
Release 100 Experion PKS Troubleshooting and Notifications Reference 397
1/03 Honeywell Part I
Partner In Wrong Module State

Number: 0x001B
Description: The primary CNI has aborted an initial synchronization attempt due
to wrong partner module state.
Cause: Incorrect secondary CNI state.
Corrective
Action:
Power-cycle the secondary chassis or disconnect-and-reconnect the
redundancy cable.

Partner Not Changed - Qualifying

Number: 0x001C
Description: The primary CNI has aborted an initial synchronization attempt
because partner CNI failed to transition to the internal Qualifying
Redundancy State.
Cause: Secondary CNI failed to transition to the internal Qualifying
Redundancy State.
Corrective
Action:
Power-cycle the secondary chassis or disconnect-and-reconnect the
redundancy cable.

Qualifying Notification Not Sent

Number: 0x001D
Description: The primary CNI has aborted an initial synchronization attempt
because it was unable to issue the Qualifying Notification service to
its partner CNI.
Cause: Primary CNI unable to issue the Qualifying Notification service.
Corrective
Action:
Power-cycle the secondary chassis or disconnect-and-reconnect the
redundancy cable.

RM Events
CNI Generated RM Events
398 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Not Compatible

Number: 0x001E
Description: The primary CNI has aborted an initial synchronization attempt
because it unexpectedly received the Qualification service with
phase 1 parameter (from the RM) before its partner compatibility
status permits initial synchronization.
Cause: Race condition whereby the RM commences initial synchronization
before the secondary CNI is ready.
Corrective
Action:
None. The primary CNI remembers the rejected attempt to
commence initial-synchronization and triggers initial-synchronization
after the secondary CNI completes its partner compatibility analysis.

Xload Unsuccessful

Number: 0x001F
Description: The primary CNI has aborted an initial synchronization attempt
because it was unable to successfully crossload connection
information to its secondary partner.
Cause: Secondary CNI faulted/removed, one or both of the RMs
faulted/removed, the redundancy cable is faulted/disconnected, or
redundant connection could not be established.
Corrective
Action:
Power-cycle the secondary chassis or disconnect-and-reconnect the
redundancy cable.

Partner Not Changed to Qualified

Number: 0x0020
Description: The primary CNI has aborted an initial synchronization attempt
because partner CNI failed to transition to the internal Qualified
Redundancy State.
Cause: Secondary CNI failed to transition to the internal Qualified
Redundancy State.
Corrective
Action:
Power-cycle the secondary chassis or disconnect-and-reconnect the
redundancy cable.

RM Events
CNI Generated RM Events
Release 100 Experion PKS Troubleshooting and Notifications Reference 399
1/03 Honeywell Part I
Qualified Notification Not Sent

Number: 0x0021
Description: The primary CNI has aborted an initial synchronization attempt
because it was unable to issue the Qualified Notification service to
its partner CNI.
Cause: Primary CNI unable to issue the Qualified Notification service.
Corrective
Action:
Power-cycle the secondary chassis or disconnect-and-reconnect the
redundancy cable.

Qual Phase2 Req Out Of Sequence

Number: 0x0022
Description: The primary CNI has aborted an initial synchronization attempt
because it unexpectedly received the Qualification service with
phase 2 parameter (from the RM).
Cause: Primary CNI received Qualification service out of sequence.
Corrective
Action:
Power-cycle the secondary chassis or disconnect-and-reconnect the
redundancy cable.

Qual Phase3 Req Out Of Sequence

Number: 0x0023
Description: The primary CNI has aborted an initial synchronization attempt
because it unexpectedly received the Qualification service with
phase 3 parameter (from the RM).
Cause: Primary CNI received Qualification service out of sequence.
Corrective
Action:
Power-cycle the secondary chassis or disconnect-and-reconnect the
redundancy cable.

RM Events
CNI Generated RM Events
400 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Qual Phase4 Req Out Of Sequence

Number: 0x0024
Description: The primary CNI has aborted an initial synchronization attempt
because it unexpectedly received the Qualification service with
phase 4 parameter (from the RM).
Cause: Primary CNI received Qualification service out of sequence.
Corrective
Action:
Power-cycle the secondary chassis or disconnect-and-reconnect the
redundancy cable.

ICP ASIC Still timing

Number: 0x0025
Description: CNI encountered condition whereby the ICP Midrange ASIC is still
processing data even though it didn't process a request in time.
Cause: N/A
Corrective
Action:
N/A

ICP ASIC Recovered

Number: 0x0026
Description: CNI encountered condition whereby the ICP Midrange ASIC
completed a request but not within the expected time frame.
Cause: N/A
Corrective
Action:
N/A

RM Events
CNI Generated RM Events
Release 100 Experion PKS Troubleshooting and Notifications Reference 401
1/03 Honeywell Part I
Qualify Fail Due to DISQ_EVENT

Number: 0x0027
Description: The primary CNI has aborted an initial synchronization attempt
because it unexpectedly received the Qualification service (from
the RM) while a disqualification was still in progress.
Cause: Primary CNI received Qualification service out of sequence.
Corrective
Action:
Power-cycle the secondary chassis or disconnect-and-reconnect
the redundancy cable.

Spurious Buffer Pointer Error

Number: 0x0028
Description: Event used during CNI development to indicate a buffer pointer
corruption problem.
Cause: A pointer to a connection buffer was corrupted.
Corrective
Action:
If a secondary CNI is faulted, power-cycle the secondary chassis.
If a primary CNI is faulted, remove and reinsert the CNI with
chassis-power applied (or power-cycle the primary chassis if not
performing control).
If the problem persists, replace the CNI.

Keeper Error

Number: 0x0029
Description: Under Construction.
Cause:
Corrective
Action:


RM Events
CNI Generated RM Events
402 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Combuf Pool ID Invalid

Number: 0x002A
Description: Under Construction.
Cause:
Corrective
Action:


Module Cmpt Disq Detected #2

Number: 0x002B
Description: Under Construction.
Cause:
Corrective
Action:


Partner Offline And Not Lonely

Number: 0x002C
Description: Under Construction.
Cause:
Corrective
Action:


Bad UMAX

Number: 0x002D
Description: Under Construction.
Cause:
Corrective
Action:


RM Events
CNI Generated RM Events
Release 100 Experion PKS Troubleshooting and Notifications Reference 403
1/03 Honeywell Part I
Good UMAX

Number: 0x002E
Description: Under Construction.
Cause:
Corrective
Action:


Keeper Info Updated

Number: 0x002F
Description: Under Construction.
Cause:
Corrective
Action:


Process Disqualification

Number: 0x0030
Description: Under Construction.
Cause:
Corrective
Action:


Partner Connection Closed

Number: 0x0031
Description: Under Construction.
Cause:
Corrective
Action:


RM Events
CNI Generated RM Events
404 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Partner Connection Exists

Number: 0x0032
Description: Under Construction.
Cause:
Corrective
Action:


Failed To Create Partner Conn

Number: 0x0033
Description: Under Construction.
Cause:
Corrective
Action:


Create Partner Conn Retry

Number: 0x0034
Description: Under Construction.
Cause:
Corrective
Action:


Qualifying Disq-Detected #2

Number: 0x0035
Description: Under Construction.
Cause:
Corrective
Action:


RM Events
CNI Generated RM Events
Release 100 Experion PKS Troubleshooting and Notifications Reference 405
1/03 Honeywell Part I
Retry Partner SMAC Not Stable

Number: 0x0036
Description: Under Construction.
Cause:
Corrective
Action:


Module Not Cmpt

Number: 0x0037
Description: Under Construction.
Cause:
Corrective
Action:


Retry Xmit Failure

Number: 0x0038
Description: Under Construction.
Cause:
Corrective
Action:


Entered Qual Phase1

Number: 0x0039
Description: Under Construction.
Cause:
Corrective
Action:


RM Events
CNI Generated RM Events
406 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Qualified Disq-Detected #2

Number: 0x003A
Description: Under Construction.
Cause:
Corrective
Action:


Partner Not Set To Qualifying

Number: 0x003B
Description: Under Construction.
Cause:
Corrective
Action:


Qualifying Not Sent To Partner

Number: 0x003C
Description: Under Construction.
Cause:
Corrective
Action:


Qual Phase1 OutOfSequence Error

Number: 0x003D
Description: Under Construction.
Cause:
Corrective
Action:


RM Events
CNI Generated RM Events
Release 100 Experion PKS Troubleshooting and Notifications Reference 407
1/03 Honeywell Part I
Entered Qual Phase2

Number: 0x003E
Description: Under Construction.
Cause:
Corrective
Action:


Qual Phase2 OutOfSequence Error

Number: 0x003F
Description: Under Construction.
Cause:
Corrective
Action:


Entered Qual Phase3

Number: 0x0046
Description: Under Construction.
Cause:
Corrective
Action:


Partner Not Set To Qualified

Number: 0x0047
Description: Under Construction.
Cause:
Corrective
Action:


RM Events
CNI Generated RM Events
408 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Qualified Not Sent To Partner

Number: 0x0048
Description: Under Construction.
Cause:
Corrective
Action:


Qual Phase3 OutOfSequence Error

Number: 0x0049
Description: Under Construction.
Cause:
Corrective
Action:


Entered Qual Phase4

Number: 0x004A
Description: Under Construction.
Cause:
Corrective
Action:


Qual Phase4 OutOfSequence Error

Number: 0x004B
Description: Under Construction.
Cause:
Corrective
Action:


RM Events
CNI Generated RM Events
Release 100 Experion PKS Troubleshooting and Notifications Reference 409
1/03 Honeywell Part I
Qualifying Cant Xmit

Number: 0x004C
Description: Under Construction.
Cause:
Corrective
Action:


Reply To RSN disqualification

Number: 0x004D
Description: Under Construction.
Cause:
Corrective
Action:


Module Cmpt No Partner Conn

Number: 0x004E
Description: Under Construction.
Cause:
Corrective
Action:


Module Cmpt XmitBuff Unavailable

Number: 0x004F
Description: Under Construction.
Cause:
Corrective
Action:


RM Events
CNI Generated RM Events
410 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Module Cmpt No Response

Number: 0x0050
Description: Under Construction.
Cause:
Corrective
Action:


Module Cmpt Disq Detected #1

Number: 0x0051
Description: Under Construction.
Cause:
Corrective
Action:


Module Cmpt Cant Xmit

Number: 0x0052
Description: Under Construction.
Cause:
Corrective
Action:


Qualified Cant Xmit

Number: 0x0053
Description: Under Construction.
Cause:
Corrective
Action:


RM Events
CNI Generated RM Events
Release 100 Experion PKS Troubleshooting and Notifications Reference 411
1/03 Honeywell Part I
Qualifying Disq-Detected #1

Number: 0x0054
Description: Under Construction.
Cause:
Corrective
Action:


Qualified Disq-Detected #1

Number: 0x0055
Description: Under Construction.
Cause:
Corrective
Action:


Qualifying No Response

Number: 0x0056
Description: Under Construction.
Cause:
Corrective
Action:


Qualified No Response

Number: 0x0057
Description: Under Construction.
Cause:
Corrective
Action:


RM Events
CNI Generated RM Events
412 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Qualifying Xmit Buff Unavailable

Number: 0x0058
Description: Under Construction.
Cause:
Corrective
Action:


Qualified Xmit Buff Unavailable

Number: 0x0059
Description: Under Construction.
Cause:
Corrective
Action:


Qualifying No Partner Conn

Number: 0x005A
Description: Under Construction.
Cause:
Corrective
Action:


Qualified No Partner Conn

Number: 0x005B
Description: Under Construction.
Cause:
Corrective
Action:


RM Events
CPM Generated RM Events
Release 100 Experion PKS Troubleshooting and Notifications Reference 413
1/03 Honeywell Part I
CPM Generated RM Events
The CPM reports the following redundancy related events to the chassis resident RM.
The Network Tools utility can be used to view the RM event log.
LOS_CLEANPOINT_BUFFER_OVERFLOW

Number: 0x0001
Description: Loss-of-synchronization occurred due to primary CPM detection of
buffer-overflow condition while creating cleanpoint notification
message for the secondary CPM.
Extended
Data:
(UINT32) Number of data bytes.
Cause: Pointer corruption occurred due to possible memory error.
Corrective
Action:
Attempt switchover to better primary CPM_CA15.

LOS_CLEANPOINT_FIFO_OVERFLOW

Number: 0x0002
Description: Loss-of-synchronization occurred due to primary CPM detection of
Tracker-FIFO-overflow condition while creating cleanpoint
notification message for the secondary CPM. Note that the Sync
HW Failure Experion PKS Notification is also generated upon
detecting this condition.
Extended
Data:
(UINT16) Partner Connections state machine step
(UINT16) Sync state machine step
(UINT32) Edit Resources vector
(UINT32) Tracker Status register
Cause: Tracker-FIFO-overflow is only possible due to either incorrect
revision of Boot firmware or Tracker hardware failure.
Corrective
Action:
First, check Boot firmware revision CPM_CA16.
If using valid CPM Boot firmware, attempt switchover to better
primary CPM_CA15.

RM Events
CPM Generated RM Events
414 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
LOS_CLEANPOINT_IDLE_TIMEOUT

Number: 0x0003
Description: Loss-of-synchronization occurred due to primary CPM timeout
while waiting for the secondary CPM to acknowledge a cleanpoint
notification message.
Extended
Data:
(UINT32) Elapsed time
(UINT16) tx/rx/seq
(UINT16) tx/rx/seq

Cause: Secondary CPM has failed or has been removed. Otherwise, if
secondary CPM is present and healthy, CPM to CPM
communication fault occurred across the RM redundancy cable.
Corrective
Action:
Isolate communication fault with secondary CPM_CA17.

LOS_CLEANPOINT_RX_FAILURE

Number: 0x0004
Description: Loss-of-synchronization occurred due to primary CPM loss of view
to the secondary CPM across the RM redundancy cable. More
specifically, encountered the track-data connection unexpectedly
busy or timed-out. The loss of view was detected prior to the
transmission of a cleanpoint notification message.
Extended
Data:
None.
Cause: Secondary CPM has failed or has been removed. Otherwise, if
secondary CPM is present and healthy, CPM to CPM
communication fault occurred across the RM redundancy cable.
Corrective
Action:
Isolate communication fault with secondary CPM_CA17.

RM Events
CPM Generated RM Events
Release 100 Experion PKS Troubleshooting and Notifications Reference 415
1/03 Honeywell Part I
LOS_CLEANPOINT_TX_FAILURE

Number: 0x0005
Description: Loss-of-synchronization occurred due to primary CPM inability to
transmit on the partner track-data connection.
Extended
Data:
None.
Cause: Secondary CPM has failed or has been removed. Otherwise, if
secondary CPM is present and healthy, CPM to CPM
communication fault occurred across the RM redundancy cable.
Corrective
Action:
Isolate communication fault with secondary CPM_CA17.

LOS_CPM_CONFIG_LOAD_IN_PROGRESS

Number: 0x0006
Description: Synchronization aborted/blocked due to CPM FB creation/deletion
or CCL download.
Extended
Data:
(UINT16) Partner Connections state machine step
(UINT16) Sync state machine step
(UINT32) Edit Resources vector
(UINT16) Qualification status.
Cause: CPM FB creation/deletion or CCL download.
Corrective
Action:
N/A

RM Events
CPM Generated RM Events
416 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
SYN_CPM_CONFIG_LOAD_END

Number: 0x0007
Description: The CPM has attempted to trigger initial synchronization due to
completion of CPM FB creation/deletion or CCL download.
Extended
Data:
None.
Cause: CPM FB creation/deletion or CCL download completion.
Corrective
Action:
N/A

LOS_CROSSLOAD_ERROR

Number: 0x0008
Description: In the current implementation of CPM redundancy, this event is not
used.
Extended
Data:
None.
Cause: N/A
Corrective
Action:
This is an unexpected RM Event log entry; call TAC.

LOS_EDIT_RESOURCE_LOCKED

Number: 0x0009
Description: Loss-of-synchronization due to primary CPM detection of the
presence of an undefined edit-resource being locked.
Extended
Data:
(UINT16) Partner Connections state machine step
(UINT16) Sync state machine step
(UINT32) Edit Resources vector
Cause: Primary CPM detection of the presence of an undefined edit
resource being locked.
Corrective
Action:
This is an unexpected RM Event log entry; call TAC.
RM Events
CPM Generated RM Events
Release 100 Experion PKS Troubleshooting and Notifications Reference 417
1/03 Honeywell Part I

LOS_EXEC_SYNC_TIMEOUT

Number: 0x000A
Description: Loss-of-synchronization due to primary CPM timeout waiting for the
secondary CPMs I/O Manager subsystem to complete forming
redundant I/O connections. More specifically, initial
synchronization is aborted if the secondary CPM is unable to
redundantly form at least the same number of I/O connections (per
CNI) already established in the primary within some finite amount
of time (e.g. 12 seconds).
Extended
Data:
(UINT32) Elapsed time
(UINT24) slot/actual/expected (x4 for the primary CPM).
(UINT24) slot/actual/expected (x4 for the secondary CPM).
Cause: Secondary CNI faulted and/or lonely.
Corrective
Action:
Isolate secondary I/O CNI ControlNet communication fault
CPM_CA18.

LOS_IOMGR_PURGE_INPROG

Number: 0x000B
Description: Indicates that the primary CPM aborted an initial synchronization
attempt because the secondary CPMs I/O Manager subsystem is
purging the I/O Map Table. Note that the secondary CPMs I/O
Map Table purge is necessary to ensure that the disqualified
secondary CPM has no I/O configuration for the I/O Manager to act
upon as a consequence of a disqualify-secondary operation.
Extended
Data:
(UINT16) Partner Connections state machine step
(UINT16) Sync state machine step
(UINT32) Edit Resources vector
Cause: Abort initial synchronization or synchronization maintenance.
Corrective
Action:
None. The primary CPM remembers the rejected attempt to
commence initial-synchronization and triggers initial-sync after the
secondary I/O Manager completes its I/O Map Table purge.

RM Events
CPM Generated RM Events
418 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
LOS_ISR_BUFFER_OVERFLOW

Number: 0x000C
Description: Loss-of-synchronization occurred due to primary CPM detection of
buffer-overflow condition while creating redundancy-data message
for the secondary CPM.
Extended
Data:
(UINT32) Number of data bytes.
Cause: Pointer corruption occurred due to possible memory error.
Corrective
Action:
Attempt switchover to better primary CPM_CA15.

LOS_ISR_FIFO_OVERFLOW

Number: 0x000D
Description: Loss-of-synchronization occurred due to primary CPM detection of
Tracker-FIFO-overflow condition while creating redundancy-data
message for the secondary CPM. Note that the Sync HW Failure
Experion PKS Notification is also generated upon detecting this
condition.
Extended
Data:
(UINT16) Partner Connections state machine step
(UINT16) Sync state machine step
(UINT32) Edit Resources vector
(UINT32) Tracker Status register
Cause: Tracker-FIFO-overflow is only possible due to either incorrect
revision of Boot firmware or Tracker hardware failure.
Corrective
Action:
First, check Boot firmware revision CPM_CA16.
If using valid CPM Boot firmware, attempt switchover to better
primary CPM_CA15.

RM Events
CPM Generated RM Events
Release 100 Experion PKS Troubleshooting and Notifications Reference 419
1/03 Honeywell Part I
LOS_ISR_RX_FAILURE

Number: 0x000E
Description: Loss-of-synchronization occurred due to primary CPM loss of view
to the secondary CPM across the RM redundancy cable. More
specifically, encountered the track-data connection unexpectedly
busy or timed-out.
Extended
Data:
None.
Cause: Secondary CPM has failed or has been removed. Otherwise, if
secondary CPM is present and healthy, CPM to CPM
communication fault occurred across the RM redundancy cable.
Corrective
Action:
Isolate communication fault with secondary CPM_CA17.

LOS_ISR_TX_FAILURE

Number: 0x000F
Description: Loss-of-synchronization occurred due to primary CPM inability to
transmit on the partner track-data connection.
Extended
Data:
None.
Cause: Secondary CPM has failed or has been removed. Otherwise, if
secondary CPM is present and healthy, CPM to CPM
communication fault occurred across the RM redundancy cable.
Corrective
Action:
Isolate communication fault with secondary CPM_CA17.

RM Events
CPM Generated RM Events
420 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
LOS_KEEP_ALIVE_BUFFER_OVERFLOW

Number: 0x0010
Description: Loss-of-synchronization occurred due to primary CPM detection of
buffer overflow condition while creating connection-keep-alive
message for the secondary CPM.
Extended
Data:
(UINT32) Number of data bytes.
Cause: Pointer corruption occurred due to possible memory error.
Corrective
Action:
Attempt switchover to better primary CPM_CA15.

LOS_KEEP_ALIVE_FIFO_OVERFLOW

Number: 0x0011
Description: Loss-of-synchronization occurred due to primary CPM detection of
Tracker-FIFO-overflow condition while creating connection-keep-
alive message for the secondary CPM. Note that the Sync HW
Failure Experion PKS Notification is also generated upon detecting
this condition.
Extended
Data:
(UINT16) Partner Connections state machine step
(UINT16) Sync state machine step
(UINT32) Edit Resources vector
(UINT32) Tracker Status register
Cause: Tracker-FIFO-overflow is only possible due to either incorrect
revision of Boot firmware or Tracker hardware failure.
Corrective
Action:
First, check Boot firmware revision CPM_CA16.
If using valid CPM Boot firmware, attempt switchover to better
primary CPM_CA15.

RM Events
CPM Generated RM Events
Release 100 Experion PKS Troubleshooting and Notifications Reference 421
1/03 Honeywell Part I
LOS_KEEP_ALIVE_RX_FAILURE

Number: 0x0012
Description: Loss-of-synchronization occurred due to primary CPM loss of view
to the secondary CPM across the RM redundancy cable. More
specifically, encountered the track-data connection unexpectedly
busy or timed-out.
Extended
Data:
None.
Cause: Secondary CPM has failed or has been removed. Otherwise, if
secondary CPM is present and healthy, CPM to CPM
communication fault occurred across the RM redundancy cable.
Corrective
Action:
Isolate communication fault with secondary CPM_CA17.

LOS_KEEP_ALIVE_TX_FAILURE

Number: 0x0013
Description: Loss-of-synchronization occurred due to primary CPM inability to
transmit on the partner track-data connection.
Extended
Data:
None.
Cause: Secondary CPM has failed or has been removed. Otherwise, if
secondary CPM is present and healthy, CPM to CPM
communication fault occurred across the RM redundancy cable.
Corrective
Action:
Isolate communication fault with secondary CPM_CA17.

RM Events
CPM Generated RM Events
422 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
LOS_PARTNER_ABSENT

Number: 0x0014
Description: In the current implementation of CPM redundancy, this event is not
used.
Extended
Data:
None.
Cause: N/A
Corrective
Action:
This is an unexpected RM Event log entry; call TAC.

RM Events
CPM Generated RM Events
Release 100 Experion PKS Troubleshooting and Notifications Reference 423
1/03 Honeywell Part I
LOS_PARTNER_INCOMPATIBLE

Number: 0x0015
Description: Indicates that the primary CPM has ascertained that the
redundancy compliant partner module is not compatible.
Extended
Data:
(UINT16) Partner Connections state machine step
(UINT16) Sync state machine step
(UINT32) Reason:
0x00000000 = Null
0x00000001 = Message size
0x00000002 = Vendor ID
0x00000003 = Product Type
0x00000004 = Product Code
0x00000005 = Major Revision
0x00000006 = Minor Revision
0x00000007 = I/O Manager DFV Position
0x00000008 = I/O Manager DFV Size
0x00000009 = Debug LSM Address
0x0000000A = Debug LSM Size
0x0000000B = Debug LSM Revision
0x0000000C = I/O Manager LSM Address
0x0000000D = I/O Manager LSM Size
0x0000000E = I/O Manager LSM Revision
0x0000000F = CEE LSM Address
0x00000010 = CEE LSM Size
0x00000011 = CEE LSM Revision
0x00000012 = CDA LSM Address
0x00000013 = CDA LSM Size
0x00000014 = CDA LSM Revision
0x00000015 = Build ID
Cause: 1) The secondary CPM has incompatible firmware (i.e. reasons
0x00000005 through 0x00000015).
2) Incorrect module type in the same slot number of the secondary
chassis (i.e. reasons 0x00000001 through 0x00000004).
Corrective
Action:
First, check CPM Application firmware compatibility CPM_CA19.
If using compatible CPM Application firmware, check CPM
hardware compatibility CPM_CA20.

RM Events
CPM Generated RM Events
424 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
LOS_PARTNER_STARTUP_INCOMPLETE

Number: 0x0016
Description: Indicates that the primary CPM aborted an initial synchronization
attempt because the secondary CPM has not completed system
startup initialization.
Extended
Data:
(UINT16) Partner Connections state machine step
(UINT16) Sync state machine step
(UINT32) Edit Resources vector
Cause: Secondary CPM startup or reboot (as a consequence of
switchover).
Corrective
Action:
None. The primary CPM remembers the rejected attempt to
commence initial-synchronization and triggers initial-sync after the
secondary CPM completes system startup initialization.

LOS_MOVE_BUFFER_OVERFLOW

Number: 0x0017
Description: Loss-of-synchronization occurred due to primary CPM detection of
buffer-overflow condition while creating redundancy-data message
for the secondary CPM.
Extended
Data:
(UINT32) Number of data bytes.
Cause: Pointer corruption occurred due to possible memory error.
Corrective
Action:
Attempt switchover to better primary CPM_CA15.

RM Events
CPM Generated RM Events
Release 100 Experion PKS Troubleshooting and Notifications Reference 425
1/03 Honeywell Part I
LOS_MOVE_FIFO_OVERFLOW

Number: 0x0018
Description: Loss-of-synchronization occurred due to primary CPM detection of
Tracker-FIFO-overflow condition while creating redundancy-data
message for the secondary CPM. Note that the Sync HW Failure
Experion PKS Notification is also generated upon detecting this
condition.
Extended
Data:
(UINT16) Partner Connections state machine step
(UINT16) Sync state machine step
(UINT32) Edit Resources vector
(UINT32) Tracker Status register
Cause: Tracker-FIFO-overflow is only possible due to either incorrect
revision of Boot firmware or Tracker hardware failure.
Corrective
Action:
First, check Boot firmware revision CPM_CA16.
If using valid CPM Boot firmware, attempt switchover to better
primary CPM_CA15.

LOS_MOVE_RX_FAILURE

Number: 0x0019
Description: Loss-of-synchronization occurred due to primary CPM loss of view
to the secondary CPM across the RM redundancy cable. More
specifically, encountered the track-data connection unexpectedly
busy or timed-out.
Extended
Data:
None.
Cause: Secondary CPM has failed or has been removed. Otherwise, if
secondary CPM is present and healthy, CPM to CPM
communication fault occurred across the RM redundancy cable.
Corrective
Action:
Isolate communication fault with secondary CPM_CA17.

RM Events
CPM Generated RM Events
426 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
LOS_MOVE_TX_FAILURE

Number: 0x001A
Description: Loss-of-synchronization occurred due to primary CPM inability to
transmit on the partner track-data connection.
Extended
Data:
None.
Cause: Secondary CPM has failed or has been removed. Otherwise, if
secondary CPM is present and healthy, CPM to CPM
communication fault occurred across the RM redundancy cable.
Corrective
Action:
Isolate communication fault with secondary CPM_CA17.

LOS_RM_CONNECTION_TIMEOUT

Number: 0x001B
Description: The CPM has requested either a switchover operation (on the
primary) or a disqualify-secondary operation (on the secondary) as
a consequence to the detection of RM removal.
Extended
Data:
None.
Cause: RM fault.
Corrective
Action:
Check the RM resident in the same chassis as the CPM
CPM_CA08.

RM Events
CPM Generated RM Events
Release 100 Experion PKS Troubleshooting and Notifications Reference 427
1/03 Honeywell Part I
LOS_SD_IDLE_TIMEOUT

Number: 0x001C
Description: Loss-of-synchronization occurred due to primary CPM timeout
while waiting for the secondary CPM to acknowledge an initial
sync-data message.
Extended
Data:
(UINT32) Elapsed time
(UINT16) tx/rx/seq
(UINT16) tx/rx/seq

Cause: Secondary CPM has failed or has been removed. Otherwise, if
secondary CPM is present and healthy, CPM to CPM
communication fault occurred across the RM redundancy cable.
Corrective
Action:
Isolate communication fault with secondary CPM_CA17.

LOS_SEC_CLEANPOINT_SEQ_ERROR

Number: 0x001D
Description: Loss-of-synchronization occurred due to secondary CPM out-of-
sequence receipt of redundancy related information on the track-
data connection. More specifically, a cleanpoint notification was
received out-of-sequence.
Extended
Data:
(UINT16) Actual sequence number
(UINT16) Expected sequence number
Cause: Data corruption, on the primary CPM, during transfer across the
RM private-path (i.e. redundancy cable), or on the secondary CPM.
Corrective
Action:
First, restart the secondary CPM CPM_CA05.
Second, if the problem persists, replace the secondary CPM
CPM_CA06.
Third, if the problem still persists, attempt switchover to better
primary CPM CPM_CA15.

RM Events
CPM Generated RM Events
428 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
LOS_SEC_SD_SEQ_ERROR

Number: 0x001E
Description: Loss-of-synchronization occurred due to secondary CPM out-of-
sequence receipt of redundancy related information on the sync-
data connection. More specifically, initial synchronization data or a
synchronization status query was received out-of-sequence.
Extended
Data:
(UINT16) Actual sequence number
(UINT16) Expected sequence number
Cause: Data corruption, on the primary CPM, during transfer across the
RM private-path (i.e. redundancy cable), or on the secondary CPM.
Corrective
Action:
First, restart the secondary CPM CPM_CA05.
Second, if the problem persists, replace the secondary CPM
CPM_CA06.
Third, if the problem still persists, attempt switchover to better
primary CPM CPM_CA15.

RM Events
CPM Generated RM Events
Release 100 Experion PKS Troubleshooting and Notifications Reference 429
1/03 Honeywell Part I
LOS_SEC_TD_ACCUMULATE_FORMAT_ERROR

Number: 0x001F
Description: Loss-of-synchronization occurred due to secondary CPM detection
of data corruption within redundancy related information received
from the primary CPM. Note that the data corruption was detected
during synchronization maintenance.
Extended
Data:
(UINT32) Unsupported tracker format
(UINT32) address
(UINT32) data #1
(UINT32) data #2
Cause: Data corruption, on the primary CPM, during transfer across the
RM private-path (i.e. redundancy cable), or on the secondary CPM.
Corrective
Action:
First, restart the secondary CPM CPM_CA05.
Second, if the problem persists, replace the secondary CPM
CPM_CA06.
Third, if the problem still persists, attempt switchover to better
primary CPM CPM_CA15.

RM Events
CPM Generated RM Events
430 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
LOS_SEC_TD_ACCUMULATE_OVERRUN

Number: 0x0020
Description: Loss-of-synchronization occurred due to secondary CPM internal
circular list overrun. This private resource accumulates
redundancy-related information from the primary CPM until a
cleanpoint notification is received.
Extended
Data:
(UINT16) Partner Connections state machine step
(UINT16) Sync state machine step
(UINT32) Edit Resources vector
(UINT32) pCommitBeg
(UINT32) pAccumulate
(UINT32) pCommitEnd
Cause: Secondary CPM memory corruption, or redundancy load exceeds
internal secondary CPM resource (i.e. primary control strategy
exceeds redundancy capacity). Realistically, control cycle
overruns occur before the later case.
Corrective
Action:
First, restart the secondary CPM CPM_CA05.
Second, if the problem persists, replace the secondary CPM
CPM_CA06.
Third, if the problem still persists, attempt switchover to better
primary CPM CPM_CA15.

RM Events
CPM Generated RM Events
Release 100 Experion PKS Troubleshooting and Notifications Reference 431
1/03 Honeywell Part I
LOS_SEC_TD_COMMIT_FORMAT_ERROR

Number: 0x0021
Description: Loss-of-synchronization occurred due to secondary CPM detection
of data corruption within redundancy related information already
preprocessed by the secondary CPM. Note that the data
corruption was detected during synchronization maintenance.
Extended
Data:
(UINT32) Unsupported tracker format
(UINT32) address
(UINT32) data #1
(UINT32) data #2
Cause: Data corruption on the secondary CPM.
Corrective
Action:
First, restart the secondary CPM CPM_CA05.
Second, if the problem persists, replace the secondary CPM
CPM_CA06.

LOS_SEC_TD_SEQ_ERROR

Number: 0x0022
Description: Loss-of-synchronization occurred due to secondary CPM out-of-
sequence receipt of redundancy related information on the track-
data connection.
Extended
Data:
(UINT16) Actual sequence number
(UINT16) Expected sequence number
Cause: Data corruption, on the primary CPM, during transfer across the
RM private-path (i.e. redundancy cable), or on the secondary CPM.
Corrective
Action:
First, restart the secondary CPM CPM_CA05.
Second, if the problem persists, replace the secondary CPM
CPM_CA06.
Third, if the problem still persists, attempt switchover to better
primary CPM CPM_CA15.

RM Events
CPM Generated RM Events
432 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
LOS_SEC_TD_UNPACK_FORMAT_ERROR

Number: 0x0023
Description: Loss-of-synchronization occurred due to secondary CPM detection
of data corruption within redundancy related information received
from the primary CPM. Note that the data corruption was detected
during initial synchronization.
Extended
Data:
(UINT32) Unsupported tracker format
(UINT32) address
(UINT32) data #1
(UINT32) data #2
Cause: Data corruption, on the primary CPM, during transfer across the
RM private-path (i.e. redundancy cable), or on the secondary CPM.
Corrective
Action:
First, restart the secondary CPM CPM_CA05.
Second, if the problem persists, replace the secondary CPM
CPM_CA06.
Third, if the problem still persists, attempt switchover to better
primary CPM CPM_CA15.

LOS_SWITCHOVER_TEST

Number: 0x0024
Description: Event posted in a development environment when the CPM
requests a switchover role change for testing purposes.
Extended
Data:
None.
Cause: Development testing.
Corrective
Action:
This is an unexpected RM Event log entry; call TAC.

RM Events
CPM Generated RM Events
Release 100 Experion PKS Troubleshooting and Notifications Reference 433
1/03 Honeywell Part I
LOS_SYNC_CHECKSUM_FAILURE

Number: 0x0025
Description: The secondary CPM has detected Synchronization Checksum
comparison failure. The Synchronization Checksum is a
synchronization maintenance integrity verification whereby the
synchronized secondary CPM computes a local database
checksum for verification with one calculated on the primary CPM.
This represents a specific cause for persistent loss-of-
synchronization which requires the secondary CPM to be restarted
and/or replaced. Note that the Sync Checksum Fail Experion PKS
Notification is also generated by the secondary CPM upon
detecting this condition.
Extended
Data:
(UINT16) Partner Connections state machine step
(UINT16) Sync state machine step
(UINT32) Edit Resources vector
(UINT32) pMemCurrent
Cause: Data corruption during transmission from primary to secondary
CPM (across redundancy cable) or Secondary CPM memory
corruption.
Corrective
Action:
Restart the secondary CPM CPM_CA05.
If the problem persists, replace the secondary CPM CPM_CA06.

RM Events
CPM Generated RM Events
434 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
LOS_SYNC_HW_FAILURE_PRIMARY

Number: 0x0026
Description: The primary CPM posts this RM Event to indicate that it has
detected synchronization hardware failure during execution of the
run-time synchronization hardware diagnostic. Note that the
primary CPM also generates the Sync HW Failure Experion PKS
Notification upon detecting this condition.
Extended
Data:
(UINT16) Partner Connections state machine step
(UINT16) Sync state machine step
(UINT32) Edit Resources vector
(UINT32) Hardware status
(UINT32) Hardware address
(UINT32) Tracker Status register
(UINT32) Caller ID
Cause: Primary CPM synchronization hardware (i.e. Tracker mechanism)
failure.
Corrective
Action:
Attempt switchover to better primary CPM CPM_CA15.

RM Events
CPM Generated RM Events
Release 100 Experion PKS Troubleshooting and Notifications Reference 435
1/03 Honeywell Part I
LOS_SYNC_HW_FAILURE_SECONDARY

Number: 0x0027
Description: The primary and secondary CPM posts this RM Event to indicate
that the secondary CPM has detected synchronization hardware
failure during execution of the run-time synchronization hardware
diagnostic. Note that the Sync HW Failure Experion PKS
Notification is also generated by the secondary CPM upon
detecting this condition.
Extended
Data:
(UINT16) Partner Connections state machine step
(UINT16) Sync state machine step
(UINT32) Edit Resources vector
(UINT32) Hardware status
(UINT32) Hardware address
(UINT32) Tracker Status register
(UINT32) Caller ID
Cause: Secondary CPM synchronization hardware (i.e. Tracker
mechanism) failure.
Corrective
Action:
Restart the secondary CPM CPM_CA05.
If the problem persists, replace the secondary CPM CPM_CA06.

RM Events
CPM Generated RM Events
436 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
LOS_TD_BUFFER_TIMEOUT

Number: 0x0028
Description: Timeout occurred while waiting for a track-data buffer to become
available for use.
Extended
Data:
(UINT32) Elapsed time
(UINT16) tx/rx/seq
(UINT16) tx/rx/seq

Cause: Secondary CPM has failed or has been removed. Otherwise, if
secondary CPM is present and healthy, CPM to CPM
communication fault occurred across the RM redundancy cable.
Corrective
Action:
Isolate communication fault with secondary CPM_CA17.

LOS_TD_PENDING_RX_FAILURE

Number: 0x0029
Description: Loss-of-synchronization occurred due to primary CPM loss of view
to the secondary CPM across the RM redundancy cable. More
specifically, encountered the track-data connection unexpectedly
busy or timed-out.
Extended
Data:
None.
Cause: Secondary CPM has failed or has been removed. Otherwise, if
secondary CPM is present and healthy, CPM to CPM
communication fault occurred across the RM redundancy cable.
Corrective
Action:
Isolate communication fault with secondary CPM_CA17.

RM Events
CPM Generated RM Events
Release 100 Experion PKS Troubleshooting and Notifications Reference 437
1/03 Honeywell Part I
LOS_TD_PENDING_TX_FAILURE

Number: 0x002A
Description: Loss-of-synchronization occurred due to primary CPM inability to
transmit on the partner track-data connection.
Extended
Data:
None.
Cause: Secondary CPM has failed or has been removed. Otherwise, if
secondary CPM is present and healthy, CPM to CPM
communication fault occurred across the RM redundancy cable.
Corrective
Action:
Isolate communication fault with secondary CPM_CA17.

SYN_IOMGR_PURGE_COMPLETE

Number: 0x002B
Description: The primary CPM has attempted to trigger initial synchronization
due to completion of the secondary CPM I/O Manager subsystem
I/O Map Table purge operation (that occurs as a consequence of
the disqualify secondary operation).
Extended
Data:
None.
Cause: Secondary CPM I/O Map Table purge completion.
Corrective
Action:
N/A

RM Events
CPM Generated RM Events
438 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
SYN_PARTNER_STARTUP_COMPLETE

Number: 0x002C
Description: The CPM has attempted to trigger initial synchronization due to
completion of the secondary CPM system startup.
Extended
Data:
None.
Cause: Secondary CPM system startup completion.
Corrective
Action:
N/A

DBG_PSEUDO_DATABASE_WRITES

Number: 0x002D
Description: Developer event to declare that a pseudo database-write
redundancy load is configured.
Extended
Data:
(UINT16) pseudo database-write load
Cause: CPM memory corruption or development testing.
Corrective
Action:
This is an unexpected RM Event log entry; .

LOS_SD_CONN_OPEN_FAILURE

Number: 0x002E
Description: The primary CPM was unable to open the partner sync-data
connection.
Extended
Data:
None.
Cause: Secondary CPM missing, faulted, or rebooting (as a consequence
of switchover).
Corrective
Action:
If the secondary CPM is not rebooting as a consequence of
switchover, isolate communication fault with secondary
CPM_CA17.

RM Events
CPM Generated RM Events
Release 100 Experion PKS Troubleshooting and Notifications Reference 439
1/03 Honeywell Part I
LOS_SD_CONN_RX_FAILURE

Number: 0x002F
Description: Loss-of-synchronization occurred due to primary CPM loss of view
to the secondary CPM across the RM redundancy cable. More
specifically, encountered the sync-data connection unexpectedly
busy or timed-out.
Extended
Data:
(UINT16) Partner Connections state machine step
(UINT16) Sync state machine step
Cause: Secondary CPM has failed or has been removed. Otherwise, if
secondary CPM is present and healthy, CPM to CPM
communication fault occurred across the RM redundancy cable.
Corrective
Action:
Isolate communication fault with secondary CPM_CA17.

LOS_SD_CONN_TX_FAILURE

Number: 0x0030
Description: Loss-of-synchronization occurred due to primary CPM inability to
transmit on the partner sync-data connection.
Extended
Data:
(UINT16) Partner Connections state machine step
(UINT16) Sync state machine step
Cause: Secondary CPM has failed or has been removed. Otherwise, if
secondary CPM is present and healthy, CPM to CPM
communication fault occurred across the RM redundancy cable.
Corrective
Action:
Isolate communication fault with secondary CPM_CA17.

RM Events
CPM Generated RM Events
440 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
LOS_TD_CONN_OPEN_FAILURE

Number: 0x0031
Description: The primary CPM was unable to open the partner track-data
connection.
Extended
Data:
None.
Cause: Secondary CPM has failed or has been removed. Otherwise, if
secondary CPM is present and healthy, CPM to CPM
communication fault occurred across the RM redundancy cable.
Corrective
Action:
Isolate communication fault with secondary CPM_CA17.

LOS_TD_CONN_RX_FAILURE

Number: 0x0032
Description: Loss-of-synchronization occurred due to primary CPM loss of view
to the secondary CPM across the RM redundancy cable. More
specifically, encountered the track-data connection unexpectedly
busy or timed-out.
Extended
Data:
None.
Cause: Secondary CPM has failed or has been removed. Otherwise, if
secondary CPM is present and healthy, CPM to CPM
communication fault occurred across the RM redundancy cable.
Corrective
Action:
Isolate communication fault with secondary CPM_CA17.

RM Events
CPM Generated RM Events
Release 100 Experion PKS Troubleshooting and Notifications Reference 441
1/03 Honeywell Part I
LOS_SEC_CLEANPOINT_COMMIT_TIMEOUT

Number: 0x0033
Description: Loss-of-synchronization occurred due to secondary CPM timeout
during commit to memory operation (as a consequence of
cleanpoint notification).
Extended
Data:
(UINT16) Actual sequence number
(UINT16) Expected sequence number
(UINT32) Elapsed time
Cause: Secondary CPM memory corruption, or redundancy load exceeds
internal secondary CPM resource (i.e. primary control strategy
exceeds redundancy capacity). Realistically, control cycle
overruns occur before the later case.
Corrective
Action:
First, restart the secondary CPM CPM_CA05.
Second, if the problem persists, replace the secondary CPM
CPM_CA06.
Third, if the problem still persists, must reduce the primary CPM
capacity consumed by the current control strategy.

LOS_EDIT_RESOURCE_CLEAR_INPROG

Number: 0x0034
Description: Upon issuing the Sync Secondary command, the primary CPM
requests that the secondary CPM clear any persistent redundancy
faults (internally known as edit resources) so that initial
synchronization may be re-attempted.
Extended
Data:
(UINT16) Partner Connections state machine step
(UINT16) Sync state machine step
(UINT32) Edit Resources vector
Cause: The primary CPM posts this RM Event when the secondary CPM
has redundancy faults that need to be cleared prior to commencing
initial synchronization.
Corrective
Action:
None. The primary CPM remembers the rejected attempt to
commence initial-synchronization and triggers initial-sync after the
secondary CPM completes edit resource initialization.
RM Events
CPM Generated RM Events
442 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03

SYN_EDIT_RESOURCE_CLEAR_COMPLETE

Number: 0x0035
Description: The primary CPM has attempted to trigger initial synchronization
due to completion of the secondary CPM initialization of all
persistent redundancy faults, (which occurs upon receipt of the
Sync Secondary command).
Extended
Data:
None.
Cause: Secondary CPM cleared all persistent redundancy faults.
Corrective
Action:
N/A

LOS_UNKNOWN_SECONDARY_LOS

Number: 0x0036
Description: Loss-of-synchronization due to primary CPM receipt of feedback
from its secondary partner. A more specific event is not used
because the primary CPM is unable to interpret the reason to drop
synchronization specified by the secondary CPM.
Extended
Data:
(UINT16) Partner Connections state machine step
(UINT16) Sync state machine step
(UINT32) Edit Resources vector
Cause: Primary CPM receipt of an undefined reason to drop
synchronization from its secondary partner.
Corrective
Action:
This is an unexpected RM Event log entry; call TAC.

RM Events
RM Generated Events
Release 100 Experion PKS Troubleshooting and Notifications Reference 443
1/03 Honeywell Part I
RM Generated Events
Communication resource error

Number: 0x0001
Description: A communication resource error occurred on the RM. The port
was not or could not be determined.
Extended
Data:
Fault Information
Cause: Communication resource errors could be due to inadequate
resources or problems accessing resources.
Corrective
Action:


Operating system error

Number: 0x0002
Description: An operating system error occurred on the RM.
Extended
Data:
Fault Information
Cause: Operation on operating system resource (queues, semaphores)
fails.
Corrective
Action:


RM Events
RM Generated Events
444 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Port1 Communication resource err

Number: 0x0003
Description: A communication resource error occurred on the RM ICP port.
Extended
Data:
Fault Information
Cause: Communication resource errors could be due to inadequate
resources or problems accessing resources.
Corrective
Action:


Port2 Communication resource err

Number: 0x0004
Description: A communication resource error occurred on the RM inter-RM port.
Extended
Data:
Fault Information
Cause: Communication resource errors could be due to inadequate
resources or problems accessing resources.
Corrective
Action:


Watchdog time-out

Number: 0x0005
Description: N/A
Extended
Data:
Fault Information
Cause: N/A
Corrective
Action:
This is an unexpected RM Event log entry.
Go to GEN_CA01.

RM Events
RM Generated Events
Release 100 Experion PKS Troubleshooting and Notifications Reference 445
1/03 Honeywell Part I
Hardware failure

Number: 0x0006
Description: An unexpected condition or event occurred and the RM has
determined the defect to exist in hardware.
Extended
Data:
Fault Information
Cause: Hardware failure.
Corrective
Action:
Go to RM_CA01.

Firmware error

Number: 0x0007
Description: An unexpected condition or event occurred and the RM has
determined the defect to exist in firmware.
Extended
Data:
Fault Information
Cause: Firmware defect.
Corrective
Action:


Configuration log error

Number: 0x0008
Description: An error occurred in reading or writing to the RM configuration log.
Extended
Data:
Fault Information
Cause: Configuration log corrupt.
Corrective
Action:


RM Events
RM Generated Events
446 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Dup. RM, This one not in control

Number: 0x0009
Description: Another RM has been detected and that RM is or will be in control
of the chassis.
Extended
Data:
Fault Information
Cause: Multiple RM modules in a single chassis.
Corrective
Action:


RM Power Down

Number: 0x000A
Description: The RM is powering down.
Extended
Data:
Fault information
Cause: RM removed from chassis or chassis lost power.
Corrective
Action:
None. Event posted for information purposes only.

Port1 Communication Error

Number: 0x000B
Description: A communication error occurred on the RM ICP port.
Extended
Data:
Fault Information
Cause: Communication errors could be due to many causes. The RM may
not be seated properly in the chassis. The redundancy cable may
not be properly attached. A module may be taking too long to
process a request thus causing timeouts.
Corrective
Action:


RM Events
RM Generated Events
Release 100 Experion PKS Troubleshooting and Notifications Reference 447
1/03 Honeywell Part I
Port2 Communication Error

Number: 0x000C
Description: A communication error occurred on the RM inter-RM port.
Extended
Data:
Fault Information
Cause: Communication errors could be due to many causes. The RM may
not be seated properly in the chassis. The redundancy cable may
not be properly attached. A module may be taking too long to
process a request thus causing timeouts.
Corrective
Action:


Communication Error

Number: 0x000D
Description: A communication error occurred on the RM. The port was not or
could not be determined.
Extended
Data:
Fault Information
Cause: Communication errors could be due to many causes. The RM may
not be seated properly in the chassis. The redundancy cable may
not be properly attached. A module may be taking too long to
process a request thus causing timeouts.
Corrective
Action:


RM Events
RM Generated Events
448 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Event Log Error

Number: 0x000E
Description: An event log error occurred. The error was a read failure,
connection failure, or a resource failure.
Extended
Data:
Fault Information
Cause: Event log corrupt or event log partner connection lost due to
redundancy cable break or removal.
Corrective
Action:


Autoqual. Option Always

Number: 0x000F
Description: The autoqualification option has been set to always autoqualify.
This configures the RM to always attempt qualification when an
autoqualification trigger occurs in a disqualified state.
Extended
Data:
None
Cause: The RM received a request to change the autoqualification option
to always.
Corrective
Action:
None. Event posted for information purposes only.

RM Events
RM Generated Events
Release 100 Experion PKS Troubleshooting and Notifications Reference 449
1/03 Honeywell Part I
Autoqual. Option Never

Number: 0x0010
Description: The autoqualification option has been set to never autoqualify.
This configures the RM to never attempt qualification when an
autoqualification trigger occurs in a disqualified state.
Extended
Data:
None
Cause: The RM received a request to change the autoqualification option
to never.
Corrective
Action:
None. Event posted for information purposes only.

Autoqual. Option Conditional

Number: 0x0011
Description: The autoqualification option has been set to conditional autoqualify.
This configures the RM to conditionally attempt qualification when
an autoqualification trigger occurs in a disqualified state. The
autoqualification state is used as the conditional expression.
Qualification is attempted when the autoqualification state is
enabled and qualification is not attempted when the
autoqualification state is disabled.
Extended
Data:
None
Cause: The RM received a request to change the autoqualification option
to conditional.
Corrective
Action:
None. Event posted for information purposes only.

RM Events
RM Generated Events
450 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Program Red. Ini. Cmd Disabled

Number: 0x0012
Description: Program-initiated redundancy commands have been disabled.
This configures the RM to not accept redundancy commands from
user programs.
Extended
Data:
None
Cause: The RM received a request to change the program-initiated
redundancy commands option to disabled.
Corrective
Action:
None. Event posted for information purposes only.

Program Red. Ini. Cmd Enabled

Number: 0x0013
Description: Program-initiated redundancy commands have been enabled. This
configures the RM to accept redundancy commands from user
programs.
Extended
Data:
None
Cause: The RM received a request to change the program-initiated
redundancy commands option to enabled.
Corrective
Action:
None. Event posted for information purposes only.

RM Events
RM Generated Events
Release 100 Experion PKS Troubleshooting and Notifications Reference 451
1/03 Honeywell Part I
Password Scope Neither

Number: 0x0014
Description: The password scope has been set to neither. This configures the
RM to require neither a password for access to redundancy
configuration parameters or redundancy user commands.
Extended
Data:
None
Cause: The RM received a request to change the password scope to
neither.
Corrective
Action:
None. Event posted for information purposes only.

Password Scope Only Red. Cfg.

Number: 0x0015
Description: The password scope has been set to only redundancy
configuration. This configures the RM to require a password for
access to redundancy configuration parameters only.
Extended
Data:
None
Cause: The RM received a request to change the password scope to only
require a password for redundancy configuration access.
Corrective
Action:
None. Event posted for information purposes only.

RM Events
RM Generated Events
452 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Password Scope Only User Cmd.

Number: 0x0016
Description: The password scope has been set to only redundancy user
commands. This configures the RM to require a password for
access to redundancy user commands only.
Extended
Data:
None
Cause: The RM received a request to change the password scope to only
require a password for redundancy user command access.
Corrective
Action:
None. Event posted for information purposes only.

Password Scope Both

Number: 0x0017
Description: The password scope has been set to both. This configures the RM
to require a password for access to redundancy configuration
parameters and redundancy user commands.
Extended
Data:
None
Cause: The RM received a request to change the password scope to
require a password for redundancy configuration parameters and
redundancy user commands.
Corrective
Action:
None. Event posted for information purposes only.

RM Events
RM Generated Events
Release 100 Experion PKS Troubleshooting and Notifications Reference 453
1/03 Honeywell Part I
Chassis redundancy state PwNS

Number: 0x0018
Description: The chassis redundancy state for this chassis is primary with no
secondary.
Extended
Data:
None
Cause: The RM either entered this state from powerup, disconnection with
a secondary, or commanded to become primary.
Corrective
Action:
None. Event posted for information purposes only.

Chassis redundancy state PwDS

Number: 0x0019
Description: The chassis redundancy state for this chassis is primary with
disqualified secondary.
Extended
Data:
None
Cause: The RM either entered this state from powerup, disqualification, or
commanded to disqualify.
Corrective
Action:
None. Event posted for information purposes only.

Chassis redundancy state PwQS

Number: 0x001A
Description: The chassis redundancy state for this chassis is primary with
qualified secondary.
Extended
Data:
None
Cause: The RM either entered this state from qualification due to an
autoqualification trigger or a command.
Corrective
Action:
None. Event posted for information purposes only.

RM Events
RM Generated Events
454 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Chassis redundancy state PwSS

Number: 0x001B
Description: The chassis redundancy state for this chassis is primary with
standby secondary.
Extended
Data:
None
Cause: The RM entered this state from a command.
Corrective
Action:
None. Event posted for information purposes only.

Chassis redundancy state DSwNP

Number: 0x001C
Description: The chassis redundancy state for this chassis is disqualified
secondary with no primary.
Extended
Data:
None
Cause: The RM either entered this state from powerup or disconnection
with a primary.
Corrective
Action:
None. Event posted for information purposes only.

Chassis redundancy state DSwP

Number: 0x001D
Description: The chassis redundancy state for this chassis is disqualified
secondary with primary.
Extended
Data:
None
Cause: The RM either entered this state from powerup, disqualification, or
commanded to disqualify.
Corrective
Action:
None. Event posted for information purposes only.

RM Events
RM Generated Events
Release 100 Experion PKS Troubleshooting and Notifications Reference 455
1/03 Honeywell Part I
Chassis redundancy state QSwP

Number: 0x001E
Description: The chassis redundancy state for this chassis is qualified
secondary with primary.
Extended
Data:
None
Cause: The RM either entered this state from qualification due to an
autoqualification trigger or a command.
Corrective
Action:
None. Event posted for information purposes only.

Chassis redundancy state SSwP

Number: 0x001F
Description: The chassis redundancy state for this chassis is standby secondary
with primary.
Extended
Data:
None
Cause: The RM entered this state from a command.
Corrective
Action:
None. Event posted for information purposes only.

RM Power Up

Number: 0x0020
Description: The RM has been powered on and is in the process or complete
with initialization. The RM was previously powered off.
Extended
Data:
None
Cause: Power supplied to the chassis with the RM.
Corrective
Action:
None. Event posted for information purposes only.

RM Events
RM Generated Events
456 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Modules Chassis State Rule

Number: 0x0021
Description: The RM pair has entered rules for determining primary/secondary
chassis redundancy state. This RM has finished its result of the
modules chassis state rule. The result is found in the extended
event info field.
Extended
Data:
Rule Result
e.g. [0x02] Rule Tie
Cause: A RM pair powered up at the same time, two primary RM's are
connected, or two secondary RM's are connected.
Corrective
Action:
None. Event posted for information purposes only.

Failed Modules Rule

Number: 0x0022
Description: The RM pair is continuing to process rules for determining
primary/secondary chassis redundancy state. This RM has
finished its result of the failed modules rule. The result is found in
the extended event info field.
Extended
Data:
Rule Result
e.g. [0x01] Rule Loser
Cause: The RM pair progressed to this Rule check after encountering a tie
for the Modules Chassis State Rule.
Corrective
Action:
None. Event posted for information purposes only.

RM Events
RM Generated Events
Release 100 Experion PKS Troubleshooting and Notifications Reference 457
1/03 Honeywell Part I
Disqualified Secondaries Rule

Number: 0x0023
Description: The RM pair is continuing to process rules for determining
primary/secondary chassis redundancy state. This RM has
finished its result of the disqualified secondaries rule. The result is
found in the extended event info field.
Extended
Data:
Rule Result
e.g. [0x00] Rule Winner
Cause: The RM pair progressed to this Rule check after encountering a tie
for the Failed Modules Rule.
Corrective
Action:
None. Event posted for information purposes only.

Blank Memories Rule

Number: 0x0024
Description: The RM pair is continuing to process rules for determining
primary/secondary chassis redundancy state. This RM has
finished its result of the blank memories rule. The result is found in
the extended event info field.
Extended
Data:
Rule Result
e.g. [0x02] Rule Tie
Cause: The RM pair progressed to this Rule check after encountering a tie
for the Disqualified Secondaries Rule.
Corrective
Action:
None. Event posted for information purposes only.

RM Events
RM Generated Events
458 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Standby Secondaries Rule

Number: 0x0025
Description: The RM pair is continuing to process rules for determining
primary/secondary chassis redundancy state. This RM has
finished its result of the standby secondaries rule. The result is
found in the extended event info field.
Extended
Data:
Rule Result
e.g. [0x02] Rule Tie
Cause: The RM pair progressed to this Rule check after encountering a tie
for the Blank Memories Rule.
Corrective
Action:
None. Event posted for information purposes only.

NRC Modules Rule

Number: 0x0026
Description: The RM pair is continuing to process rules for determining
primary/secondary chassis redundancy state. This RM has
finished its result of the NRC (non-redundancy compliant) modules
rule. The result is found in the extended event info field.
Extended
Data:
Rule Result
e.g. [0x02] Rule Tie
Cause: The RM pair progressed to this Rule check after encountering a tie
for the Standby Secondaries Rule.
Corrective
Action:
None. Event posted for information purposes only.

RM Events
RM Generated Events
Release 100 Experion PKS Troubleshooting and Notifications Reference 459
1/03 Honeywell Part I
Powerdown Time Rule

Number: 0x0027
Description: The RM pair is continuing to process rules for determining
primary/secondary chassis redundancy state. This RM has
finished its result of the powerdown time rule. The result is found in
the extended event info field.
Extended
Data:
Rule Result
e.g. [0x02] Rule Tie
Cause: The RM pair progressed to this Rule check after encountering a tie
for the NRC Modules Rule.
Corrective
Action:
None. Event posted for information purposes only.

Chassis Modules Rule

Number: 0x0028
Description: The RM pair is continuing to process rules for determining
primary/secondary chassis redundancy state. This RM has
finished its result of the chassis modules rule. The result is found
in the extended event info field.
Extended
Data:
Rule Result
e.g. [0x02] Rule Tie
Cause: The RM pair progressed to this Rule check after encountering a tie
for the Powerdown Time Rule.
Corrective
Action:
None. Event posted for information purposes only.

RM Events
RM Generated Events
460 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
RM Serial Number Rule

Number: 0x0029
Description: The RM pair is continuing to process rules for determining
primary/secondary chassis redundancy state. This RM has
finished its result of the RM serial number rule. The result is found
in the extended event info field.
Extended
Data:
Rule Result
e.g. [0x02] Rule Tie
Cause: The RM pair progressed to this Rule check after encountering a tie
for the RM Serial Number Rule.
Corrective
Action:
None. Event posted for information purposes only.

Module Insertion

Number: 0x002A
Description: The RM has detected a module inserted in the chassis. The slot
number and redundancy compliance of the inserted module is
found in the extended event info field.
Extended
Data:
Slot Number, Redundancy Compliance
e.g. Slot 0x05, Fully Compatible
Cause: Module inserted in chassis or module found during powerup of RM.
Corrective
Action:
None. Event posted for information purposes only.

RM Events
RM Generated Events
Release 100 Experion PKS Troubleshooting and Notifications Reference 461
1/03 Honeywell Part I
Module Removal

Number: 0x002B
Description: The RM has detected a module removed from the chassis. The
slot number and redundancy compliance of the removed module is
found in the extended event info field.
Extended
Data:
Slot Number, Redundancy Compliance
e.g. Slot 0x05, Fully Compatible
Cause: Module removed from chassis.
Corrective
Action:
None. Event posted for information purposes only.

Autoqual. Trigger

Number: 0x002C
Description: The RM has detected an autoqualification trigger. The trigger is
found in the extended event info field.
Extended
Data:
Trigger
e.g. [0x01] Module Request
Cause: Autoqualification trigger detected. Triggers are listed in extended
data.
Corrective
Action:
None. Event posted for information purposes only.

RM Events
RM Generated Events
462 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Qualification Attempted

Number: 0x002D
Description: The RM has made an attempt to initiate qualification for the
redundant chassis pair. The reason for the qualification attempt is
found in the extended event info field.
Extended
Data:
Qualification Attempt Reason
e.g. [0x01] Commanded Trigger
Cause: The RM either received a command to initiate qualification or an
autoqualification trigger was accepted to initiate qualification.
Corrective
Action:
None. Event posted for information purposes only.

Qualification Complete

Number: 0x002E
Description: The chassis pair has finished qualification.
Extended
Data:
None
Cause: All modules including the RM finished all of the qualification phases
without any errors that would cause qualification to abort.
Corrective
Action:
None. Event posted for information purposes only.

RM Events
RM Generated Events
Release 100 Experion PKS Troubleshooting and Notifications Reference 463
1/03 Honeywell Part I
Qualification Abort

Number: 0x002F
Description: The chassis pair has aborted qualification. The reason for the
qualification abort is found in the extended event info field.
Extended
Data:
(optional) Slot Number, Qualification Abort Reason
e.g. [0x0C00] Sec Failed Module Exists
e.g. [0x0103] Slot 0x03, Module Configuration Error
Cause: A pre-qualification check failed or an error occurred during
qualification. Qualification abort reasons are listed in extended
data.
Corrective
Action:


Switchover Attempted

Number: 0x0030
Description: The RM has made an attempt to initiate switchover. The reason for
the switchover attempt is found in the extended event info field.
Extended
Data:
Switchover Attempt Reason
e.g. [0x07] Switchover Command
Cause: The RM either received a command to initiate switchover or an
event or failure triggered the switchover. Switchover attempt
reasons are listed in the extended data.
Corrective
Action:
None. Event posted for information purposes only.

RM Events
RM Generated Events
464 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Switchover Complete

Number: 0x0031
Description: The chassis has finished switchover.
Extended
Data:
None
Cause: All modules including the RM finished all of the switchover phases.
Corrective
Action:
None. Event posted for information purposes only.

RM Events
RM Generated Events
Release 100 Experion PKS Troubleshooting and Notifications Reference 465
1/03 Honeywell Part I
Autoqual. State Change

Number: 0x0032
Description: The autoqualification state has changed. The new autoqualification
state and the reason for the change are found in the extended data
info field.
Extended
Data:
Two values.
First value: Autoqualification State (2 hexadecimal digits)
0x00 = Disabled
0x01 = Enabled
Second value: Autoqualification State Change Reason (2
hexadecimal digits)
0x01 = Autoqualification Option Changed to Never
0x02 = Autoqualification Option Change to Always
0x03 = Initiate Qualification Command
0x04 = Disqualify Secondary Command
0x05 = Partner RM's Decision
Cause: The RM or partner RM received and accepted a command to
initiate qualification with the autoqualification option set to
conditional.
The RM or partner RM received and accepted a command to
disqualify secondary with the autoqualification option set to
conditional.
The RM or partner RM received and accepted a request to change
the autoqualification option to never with the autoqualification state
enabled.
The RM or partner RM received and accepted a request to change
the autoqualification option to always with the autoqualification
state disabled.
The partner RM requested the change due to a configuration
mismatch at powerup.
Corrective
Action:
None. Event posted for information purposes only.

RM Events
RM Generated Events
466 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Ini. Qual. Cmd. Accepted

Number: 0x0033
Description: The RM accepted a command to initiate qualification.
Extended
Data:
None
Cause: The RM received a command to initiate qualification.
Corrective
Action:
None. Event posted for information purposes only.

Ini. Qual. Cmd. Rejected

Number: 0x0034
Description: The RM rejected a command to initiate qualification. The reason
for the rejection is found in the extended data info field.
Extended
Data:
CIP General Status
e.g. [0x0b] GS_ALREADY_IN_REQUESTED_MODE
Cause: The RM received a command to initiate qualification.
Corrective
Action:


Ini. Switchover Cmd Accepted

Number: 0x0035
Description: The RM accepted a command to initiate switchover.
Extended
Data:
None
Cause: The RM received a command to initiate switchover.
Corrective
Action:
None. Event posted for information purposes only.

RM Events
RM Generated Events
Release 100 Experion PKS Troubleshooting and Notifications Reference 467
1/03 Honeywell Part I
Ini. Switchover Cmd Rejected

Number: 0x0036
Description: The RM rejected a command to initiate switchover. The reason for
the rejection is found in the extended data info field.
Extended
Data:
CIP General Status
e.g. [0x0b] GS_ALREADY_IN_REQUESTED_MODE
Cause: The RM received a command to initiate switchover.
Corrective
Action:


Become Primary Cmd Accepted

Number: 0x0037
Description: The RM accepted a command to become primary.
Extended
Data:
None
Cause: The RM received a command to become primary.
Corrective
Action:
None. Event posted for information purposes only.

Become Primary Cmd Rejected

Number: 0x0038
Description: The RM rejected a command to become primary. The reason for
the rejection is found in the extended data info field.
Extended
Data:
CIP General Status
e.g. [0x0b] GS_ALREADY_IN_REQUESTED_MODE
Cause: The RM received a command to become primary.
Corrective
Action:


RM Events
RM Generated Events
468 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Disq. Secondary Cmd Accepted

Number: 0x0039
Description: The RM accepted a command to disqualify secondary.
Extended
Data:
None
Cause: The RM received a command to disqualify secondary.
Corrective
Action:
None. Event posted for information purposes only.

Disq. Secondary Cmd Rejected

Number: 0x003A
Description: The RM rejected a command to disqualify secondary. The reason
for the rejection is found in the extended data info field.
Extended
Data:
CIP General Status
e.g. [0x0b] GS_ALREADY_IN_REQUESTED_MODE
Cause: The RM received a command to disqualify secondary.
Corrective
Action:


Enter Standby Cmd Accepted

Number: 0x003B
Description: N/A
Extended
Data:
None
Cause: N/A
Corrective
Action:
This is an unexpected RM Event log entry.
Go to GEN_CA01.

RM Events
RM Generated Events
Release 100 Experion PKS Troubleshooting and Notifications Reference 469
1/03 Honeywell Part I
Enter Standby Cmd Rejected

Number: 0x003C
Description: N/A
Extended
Data:
CIP General Status
e.g. [0x0b] GS_ALREADY_IN_REQUESTED_MODE
Cause: N/A
Corrective
Action:
This is an unexpected RM Event log entry.
Go to GEN_CA01.

Swap Control Cmd Accepted

Number: 0x003D
Description: N/A
Extended
Data:
None
Cause: N/A
Corrective
Action:
This is an unexpected RM Event log entry.
Go to GEN_CA01.

Swap Control Cmd Rejected

Number: 0x003E
Description: N/A
Extended
Data:
CIP General Status
e.g. [0x0b] GS_ALREADY_IN_REQUESTED_MODE
Cause: N/A
Corrective
Action:
This is an unexpected RM Event log entry.
Go to GEN_CA01.

RM Events
RM Generated Events
470 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Swap To Standby Cmd Accepted

Number: 0x003F
Description: N/A
Extended
Data:
None
Cause: N/A
Corrective
Action:
This is an unexpected RM Event log entry.
Go to GEN_CA01.

Swap To Standby Cmd Rejected

Number: 0x0040
Description: N/A
Extended
Data:
CIP General Status
e.g. [0x0b] GS_ALREADY_IN_REQUESTED_MODE
Cause: N/A
Corrective
Action:
This is an unexpected RM Event log entry.
Go to GEN_CA01.

Firmware Upgrade

Number: 0x0041
Description: N/A
Extended
Data:
None
Cause: N/A
Corrective
Action:
This is an unexpected RM Event log entry.
Go to GEN_CA01.

RM Events
RM Generated Events
Release 100 Experion PKS Troubleshooting and Notifications Reference 471
1/03 Honeywell Part I
Partner Chassis Connected

Number: 0x0042
Description: N/A
Extended
Data:
None
Cause: N/A
Corrective
Action:
This is an unexpected RM Event log entry.
Go to GEN_CA01.

Partner Chassis Disconnected

Number: 0x0043
Description: N/A
Extended
Data:
None
Cause: N/A
Corrective
Action:
This is an unexpected RM Event log entry.
Go to GEN_CA01.

User Initiated Time Change

Number: 0x0044
Description: N/A
Extended
Data:
None
Cause: N/A
Corrective
Action:
This is an unexpected RM Event log entry.
Go to GEN_CA01.

RM Events
RM Generated Events
472 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
SYS_FAIL_L Active

Number: 0x0045
Description: The RM has detected the SYS_FAIL_L signal transition to the
active state.
Extended
Data:
None
Cause: A module in the chassis failed.
Corrective
Action:


SYS_FAIL_L Inactive

Number: 0x0046
Description: The RM has detected the SYS_FAIL_L signal transition to the
inactive state.
Extended
Data:
None
Cause: A failed module was removed from the chassis.
Corrective
Action:
None. Event posted for information purposes only.

Scream Detected

Number: 0x0047
Description: N/A
Extended
Data:
None
Cause: N/A
Corrective
Action:
This is an unexpected RM Event log entry.
Go to GEN_CA01.

RM Events
RM Generated Events
Release 100 Experion PKS Troubleshooting and Notifications Reference 473
1/03 Honeywell Part I
Backup Communication Data Errors

Number: 0x0048
Description: An overflow in transmit or receive statistic counters of backup
communication data.
Extended
Data:
Fault Information
Cause: Excessive backup communication data.
Corrective
Action:


Task Failed It's Status Check

Number: 0x0049
Description: The RM watchdog manager has detected a task that has stopped
responding.
Extended
Data:
Fault Information
Cause: An RM task is not operating properly.
Corrective
Action:


RM Events
RM Generated Events
474 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Powerup Startup Time Changed

Number: 0x004A
Description: The RM has changed its stored powerup startup time for the
chassis. This powerup time is used to make sure that all modules
are given a chance to finish powerup before the RM begins
primary/secondary determination.
Extended
Data:
Four values.
First value: Slot Number (2 hexadecimal digits)
0x## = Slot Number
Second value: Module Product Code (4 hexadecimal digits)
0x#### = Module Product Code
Third value: Module Product Type (4 hexadecimal digits)
0x#### = Module Product Type
Fourth value: Startup Time (4 hexadecimal digits)
0x#### = Startup Time
Cause: A module increases its powerup startup time such that the value is
greater than the stored RM powerup startup time for the chassis.
The RM has finished powerup and has detected a change in the
largest powerup startup time for the chassis (a change here
meaning greater or lesser than the stored powerup startup time for
the chassis).
Corrective
Action:
None. Event posted for information purposes only.

WCT set to default

Number: 0x004B
Description: The initial wall clock time value was set to the default value.
Extended
Data:
None
Cause: The last time stamp was invalid and the RM is initializing wall clock
time object data.
Corrective
Action:
None. Event posted for information purposes only.

RM Events
RM Generated Events
Release 100 Experion PKS Troubleshooting and Notifications Reference 475
1/03 Honeywell Part I
WCT set to last event timestamp

Number: 0x004C
Description: The initial wall clock time value was set to the last time stamp.
Extended
Data:
None
Cause: The last time stamp was valid and the RM is initializing wall clock
time object data.
Corrective
Action:
None. Event posted for information purposes only.

WCT time change ( > 1 second)

Number: 0x004D
Description: The time changed greater than one second.
Extended
Data:
None
Cause: The RM received a request to change the time. The request could
come from a user or the partner RM when becoming connected.
Corrective
Action:
None. Event posted for information purposes only.

Rule Failed

Number: 0x004E
Description: The RM encountered a problem with processing a rule. A major
non-recoverable fault will occur and give more details concerning
the rule failure.
Extended
Data:
None
Cause: Most causes are due to invalid internal RM states during rule
processing.
Corrective
Action:


RM Events
RM Generated Events
476 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Rule Interrupted by Ext. Event

Number: 0x004F
Description: The RM received an event that has stopped rule processing. Rule
processing will either restart or stop because the event has taken
precedence over the processing of rules.
Extended
Data:
None
Cause: The RM pair was disconnected or the partner RM has finished the
rules before this RM and has requested this RM to switchover or
enter the primary/secondary chassis redundancy state.
Corrective
Action:


Module Rejected a State Change

Number: 0x0050
Description: A module rejected the chassis redundancy state requested by the
RM.
Extended
Data:
Module Slot Number, Rejected Phase
e.g. Slot 0x01, phase/state = 0x0001
Cause: A module in the chassis rejected the redundancy state requested
by the RM.
Corrective
Action:
The RM automatically aborts the state change if the redundancy
state was primary with qualified secondary, qualified secondary,
primary with standby secondary, or standby secondary. Otherwise,
the RM automatically forces the state change.

RM Events
RM Generated Events
Release 100 Experion PKS Troubleshooting and Notifications Reference 477
1/03 Honeywell Part I
Module Rejected a Sw. Phase

Number: 0x0051
Description: A module rejected the switchover phase requested by the RM.
Extended
Data:
Module Slot Number, Rejected Phase
e.g. Slot 0x01, phase/state = 0x0001
Cause: A module in the chassis rejected the switchover phase requested
by the RM.
Corrective
Action:
The RM automatically forces the switchover phase.

RM Serial Numbers are the same

Number: 0x0052
Description: The RM pair has the exact same serial number.
Extended
Data:
Fault Information
Cause: RM's were programmed with the same serial number and the RM
pair rule result for the last rule, RM serial number rule, was a tie.
Corrective
Action:
One of the two RMs must be replaced.
Pick one, then go to RM_CA01.

RM application fw has changed

Number: 0x0053
Description: The RM has detected a change in the application firmware revision.
This indicates that newer or older application firmware has been
loaded into the RM and this is the first time that newer or older
application firmware has run.
Extended
Data:
None
Cause: The RM was updated with newer or older application firmware.
Corrective
Action:
None. Event posted for information purposes only.
RM Events
RM Generated Events
478 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03

DEBUG:: Jabba State Change

Number: 0x0054
Description: Developer event that indicates the RM state machine has
transitioned to a new state.
Extended
Data:
State (4 hexadecimal digits)
0x#### = State
Cause: N/A
Corrective
Action:
This is an unexpected RM Event log entry.
Go to GEN_CA01.

A partner RM has been connected

Number: 0x0055
Description: RM has established connection to partner RM.
Extended
Data:
None
Cause: Redundancy cable connecting RM pair was added or partner RM is
powering up.
Corrective
Action:
None. Event posted for information purposes only.

The partner RM has been disconn.

Number: 0x0056
Description: RM has lost connection to partner RM.
Extended
Data:
Disconnection Reason
e.g. [0x01] PINGING_LOST
Cause: Redundancy cable connecting RM pair was removed.
Corrective
Action:


RM Events
RM Generated Events
Release 100 Experion PKS Troubleshooting and Notifications Reference 479
1/03 Honeywell Part I
The partner RM screamed.

Number: 0x0057
Description: RM has detected the partner RM screaming. The partner RM has
failed or lost power.
Extended
Data:
None
Cause: The partner RM failed or was removed or the chassis power supply
failed.
Corrective
Action:


The Health LED maybe incorrect.

Number: 0x0058
Description: The RM Health LED maybe indicating an incorrect state. The
Health LED maybe indicating a connection (solid green) when
there is no connection (flash green) or indicating no connection
(flash green) when there is a connection (solid green).
Extended
Data:
Fault Information
Cause: The RM had a problem setting the device object state attribute.
The RM was setting the state to the connected state or the waiting
for connections state.
Corrective
Action:


RM Events
RM Generated Events
480 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Closed Prim. Connection at Sw.

Number: 0x0059
Description: Developer event indicating closure of a primary connection at
switchover.
Extended
Data:
Application Connection Table Index
e.g. 0x0103
Cause: Switchover.
Corrective
Action:
This is an unexpected RM Event log entry.
Go to GEN_CA01.

Closed Sec. Connection at Sw.

Number: 0x005A
Description: Developer event indicating closure of a secondary connection at
switchover.
Extended
Data:
Application Connection Table Index
e.g. 0x0103
Cause: Switchover.
Corrective
Action:
This is an unexpected RM Event log entry.
Go to GEN_CA01.

RM Events
RM Generated Events
Release 100 Experion PKS Troubleshooting and Notifications Reference 481
1/03 Honeywell Part I
Opened Prim. Connection at Sw.

Number: 0x005B
Description: Developer event indicating opening a primary connection at
switchover.
Extended
Data:
Application Connection Table Index
e.g. 0x0103
Cause: Switchover.
Corrective
Action:
This is an unexpected RM Event log entry.
Go to GEN_CA01.

Closed Sec. Connection at Disq.

Number: 0x005C
Description: Developer event indicating closure of a secondary connection at
disqualification.
Extended
Data:
Application Connection Table Index
e.g. 0x0103
Cause: Disqualification
Corrective
Action:
This is an unexpected RM Event log entry.
Go to GEN_CA01.

RM Events
RM Generated Events
482 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Module Rejected Qualification

Number: 0x005D
Description: Module rejected the qualification phase requested by the RM.
Extended
Data:
Module Slot Number, Rejected Phase
e.g. Slot 0x01, phase/state = 0x0001
Cause: A module in the chassis rejected the qualification phase requested
by the RM.
Corrective
Action:
The RM automatically aborts qualification.

Module State Change Response Bad

Number: 0x005E
Description: Module responded with an invalid chassis redundancy state.
Extended
Data:
Module Slot Number, Module Phase Response
e.g. Slot 0x01, Invalid Response Parameter = 0x0001
Cause: A module in the chassis responded with an incorrect response to
the redundancy state requested by the RM.
Corrective
Action:


Module Qual Response Bad

Number: 0x005F
Description: Module responded with an invalid qualification phase.
Extended
Data:
Module Slot Number, Module Phase Response
e.g. Slot 0x01, Invalid Response Parameter = 0x0001
Cause: A module in the chassis responded with an incorrect response to
the qualification phase requested by the RM.
Corrective
Action:


RM Events
RM Generated Events
Release 100 Experion PKS Troubleshooting and Notifications Reference 483
1/03 Honeywell Part I
Module Switchover Response Bad

Number: 0x0060
Description: Module responded with an invalid switchover phase.
Extended
Data:
Module Slot Number, Module Phase Response
e.g. Slot 0x01, Invalid Response Parameter = 0x0001
Cause: A module in the chassis responded with an incorrect response to
the qualification phase requested by the RM.
Corrective
Action:


The State Change Timed Out

Number: 0x0061
Description: At least one of the chassis resident modules failed to respond to
the RMs last broadcast of the chassis redundancy state.
Extended
Data:
[(UINT24) Slot Mask (UINT24) Slot Vector]
Redundancy State
Slots that failed to respond to the RSN
e.g. [0x4F0909 0x00002A] DSwP Slots: 01 03 05
Cause: At least one of the chassis resident modules failed to respond to
the RMs last broadcast of the chassis redundancy state.
Corrective
Action:


RM Events
RM Generated Events
484 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Executing Prim. capability check

Number: 0x0062
Description: Indicates that the RM has begun an attempt to transition the
disqualified secondary chassis into the primary redundancy role.
Extended
Data:
None.
Cause: Either {1} RM insertion under power to a chassis with at least one
module in the secondary state, or {2} receipt of the Become
Primary command.
Corrective
Action:
None. Event posted for information purposes only.

Pri. capability check failed

Number: 0x0063
Description: Indicates that the RM was unsuccessful in its attempt to transition
the disqualified secondary chassis into the primary redundancy
role.
Extended
Data:
None.
Cause: At least one (chassis resident) modules responded to the RM with
an indication of its inability to transition into the primary redundancy
role.
Corrective
Action:


RM Events
RM Generated Events
Release 100 Experion PKS Troubleshooting and Notifications Reference 485
1/03 Honeywell Part I
Pri. capability check successful

Number: 0x0064
Description: Indicates that the RM was successful in its attempt to transition the
disqualified secondary chassis into the primary redundancy role.
Extended
Data:
None.
Cause: All (chassis resident) modules responded to the RM with an
indication of their ability to transition into the primary redundancy
role.
Corrective
Action:
None. Event posted for information purposes only.

Changed vendor ID

Number: 0x0065
Description: Indicates that the RM has manipulated the specified manufacturing
information to compensate for an obsolete Vendor ID. Note that
this does not save the modified Vendor ID into non-volatile memory
(i.e. this event shall be regenerated upon every RM release from
reset).
Extended
Data:
None.
Cause: RM is one of a batch that was assigned an obsolete Vendor ID
Corrective
Action:
None. Event posted for information purposes only.

RM Events
RM Generated Events
486 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Changed serial number

Number: 0x0066
Description: Indicates that the RM has manipulated the specified manufacturing
information to compensate for an incorrectly formatted serial
number. Note that this does not save the modified serial number
into non-volatile memory (i.e. this event shall be regenerated upon
every RM release from reset).
Extended
Data:
None.
Cause: RM is one of a batch that was assigned an incorrectly formatted
serial number.
Corrective
Action:
None. Event posted for information purposes only.


Release 100 Experion PKS Troubleshooting and Notifications Reference 487
1/03 Honeywell Part I
Test Sequence Numbers
CPM
The following table indicates the major tests performed during CPM startup, their test
sequence numbers and their order of execution. These tests are basically a linear
sequence, which uses very few subroutines and no stack. On any failure, the test loops at
that location so the problem can be easily diagnosed. Note that an abnormal condition
exists if the CPM remains in a particular test for more than 30 seconds at which time the
specified corrective action should be performed.
Table of CPM Test Sequence Numbers

TSN Description Corrective
Action
0 Alphanumeric Display Test. The alphanumeric display
is a write-only device. As such, it is very difficult to test
automatically. However, diagnostics scroll vertical and
horizontal lines and vary brightness when all segments
are lit. In this way an interested user can ascertain
whether the display as a whole or any particular
segment are functioning properly. Note that this test
sequence number is not actually displayed. The
firmware version is briefly displayed after this test (e.g.
FW E).
Replace the CPM
CPM_CA06.
1 CPU Type & Version Check. This test is used to detect
a bad, obsolete, or unexpected new CPU. The CPU
chip version is briefly displayed after this test (e.g.
E40+).
Replace the CPM
CPM_CA06.
10 Flash ROM parity scan. For each ROM line (8 bytes) of
the 1MB Boot Image area, the data is read and the
expected parity is computed and compared with the
actual parity. The test is timed.
Replace the CPM
CPM_CA06.
11 Flash ROM parity scan time. The time needed to
perform the above test is checked for reasonability.
This test detects CPU Instruction Cache failure and/or
ROM wait state problems.
Replace the CPM
CPM_CA06.
12 The checksum of the Boot personality is computed and
verified.
Replace the CPM
CPM_CA06.
13 The checksum of the Boot personality Flash ROM
loader is computed and verified.
Replace the CPM
CPM_CA06.
15 Verify the DRAM Controller ASIC powered up properly. Replace the
CPM
CPM_CA06.
Test Sequence Numbers
CPM
488 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
TSN Description Corrective
Action
16 Load the DRAM Controller ASIC configuration file. Replace the CPM
CPM_CA06.
17 Verify the DRAM Controller ASIC configuration was
accepted.
Replace the CPM
CPM_CA06.
18 Read back the DRAM Controller ASIC configuration and
compare with the image embedded in Boot personality.
Replace the CPM
CPM_CA06.
20 Verify that RAM can be read/written as 32-bit words.
This is the first and simplest way to access RAM. It is
also the only way to know if the DRAM Controller ASIC
was configured properly.
Replace the CPM
CPM_CA06.
21 Verify that the RAM parity/checkbit path is working. Replace the CPM
CPM_CA06.
22 Verify RAM word read/write access. Replace the CPM
CPM_CA06.
23 Verify RAM byte read access. Replace the CPM
CPM_CA06.
24 Verify RAM half-word read access. Replace the CPM
CPM_CA06.
25 Verify RAM byte read/write access. Replace the CPM
CPM_CA06.
26 Verify RAM half-word read/write access. Replace the CPM
CPM_CA06.
27 Verify RAM half-word missaligned read/write access. Replace the CPM
CPM_CA06.
28 Verify RAM word misaligned read/write access. Replace the CPM
CPM_CA06.
29 Verify RAM double-word read/write access. Replace the CPM
CPM_CA06.
30 EDAC Correction test to verify that any single-bit error
can both be detected and corrected irrespective of
whether it occurs in the data or check bits.
Replace the CPM
CPM_CA06.
31 EDAC Error Test to verify that a double-bit error can be
detected.
Replace the CPM
CPM_CA06.
Test Sequence Numbers
CPM
Release 100 Experion PKS Troubleshooting and Notifications Reference 489
1/03 Honeywell Part I
TSN Description Corrective
Action
32 After verifying that no machine check interrupt source is
active, the exception is unmasked. No interrupt is
expected.
Replace the CPM
CPM_CA06.
33 Data Parity Interrupt test to verify that the data parity
error detection is working by enabling data parity
checking and the machine check exception, then
walking through an area of ROM which has been
intentionally programmed with bad parity.
Replace the CPM
CPM_CA06.
34 RAM parity/edac sweep to ensure no multiple-bit errors
exists. Single bit errors are counted, and written back
for correction. On detection of an error, the memory
retention magic number is cleared to force the
destructive memory test.
Replace the CPM
CPM_CA06.
35 RAM Single-bit Error Threshold Test. If more than 2
single-bit errors occurred in the previous test, force the
destructive memory test. High temperatures may cause
a number of single-bit errors, so this test is skipped
when factory test mode is enabled.
Replace the CPM
CPM_CA06.
36 The time required to perform the above RAM
parity/edac sweep test is checked for reasonability.
This test detects CPU Instruction Cache failure and/or
RAM wait state problems. Note that this test is only
applicable if a Multi-bit Error was not detected.
Replace the CPM
CPM_CA06.
37 Verify that a EDAC double-bit error generates the
correct machine check exception.
Replace the CPM
CPM_CA06.
40 RAM Memory Retention Test. The magic numbers are
checked to determine if the data in RAM may still be
valid. In the absence of parity/edac errors, skip RAM
destructive test and flush (i.e. skip to test #55).
Replace the CPM
CPM_CA06.
41 RAM Destructive Pattern Test. Check address and data
lines by writing a non-repeating pattern over the whole
memory, then verifying it. Data parity is enabled during
this test.
Replace the CPM
CPM_CA06.
42 Flush RAM Data Zero. Write zeros to all locations and
verify. Data parity is enabled during this test.
Replace the CPM
CPM_CA06.
Test Sequence Numbers
CPM
490 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
TSN Description Corrective
Action
43 Verifies that checkbits were correct after DRAM flushed
to all zeros. Sets magic number to show memory is
initialized.
Replace the CPM
CPM_CA06.
55 Enable the Data Cache and execute a RAM write/verify
loop. Verify that it runs faster than it would if the cache
were broken or disabled. Flush/disable cache and
verify that the data was written to RAM correctly. Only
uses the memory test area, so just shows that the data
cache is enabled and at least partially functional.
Replace the CPM
CPM_CA06.
56 Recompute the Boot personality checksum with Data
Cache enabled. The test is timed. If either the
checksum is incorrect or the test takes too long, the
data cache is not working properly.
Replace the CPM
CPM_CA06.
60 Verify that Hardware Status Register can be accessed
without error.
Replace the CPM
CPM_CA06.
61 Verify that Battery Load Applied changes state per the
Battery Load Apply/Remove controls. This test is
performed early because it is the only test with
feedback.
Replace the CPM
CPM_CA06.
62 Verify that the DC_FAIL/SRESET status is not asserted. Replace the CPM
CPM_CA06.
63 Verify that the AC_FAIL/BP_LINE_FAIL status is not
asserted.
Replace the CPM
CPM_CA06.
64 Verify that the ICP ASIC interrupt is not asserted. Replace the CPM
CPM_CA06.
65 Verify that the interrupt from development board is not
asserted.
Replace the CPM
CPM_CA06.
66 Verify that the interrupt from memory board is not
asserted.
Replace the CPM
CPM_CA06.
67 If factory test mode is enabled, verify that the SYS_FAIL
status is not asserted for longer than a finite period, to
account for other modules tests.
Replace the CPM
CPM_CA06.
68 Verify that Watchdog Timer Timeout status is not
asserted.
Replace the CPM
CPM_CA06.
Test Sequence Numbers
CPM
Release 100 Experion PKS Troubleshooting and Notifications Reference 491
1/03 Honeywell Part I
TSN Description Corrective
Action
70 Verify that the ICP_FAULT status is not asserted. This
would indicate that the ICP ASIC had failed to come out
of reset.
Replace the CPM
CPM_CA06.
71 ICP ASIC Release and Stuck Interrupt Test. Enables
interrupts to make sure that there is no interrupt stuck in
the asserted state.
Replace the CPM
CPM_CA06.
72 If factory test mode is enabled, verify that system
controls assert and deassert the SYSFAIL_L condition.
Uses timeouts to prevent conflicts with other modules
under test on the same backplane. No SYSFAIL_L
interrupt test. This test fails if another module leaves
SYSFAIL_L asserted.
Replace the CPM
CPM_CA06.
73 Watchdog Timer Test. Verify that the WDT does not
expire when refreshed over a period of 500 msec. Uses
the WDT Test mode to verify that the WDT is capable of
interrupt generation on timeout within a fininte expected
time range.
Replace the CPM
CPM_CA06.
100 ICP Shared RAM Destructive Pattern Test. Check
address and data lines by writing a non-repeating
pattern over the whole memory, then verifying it.
Replace the CPM
CPM_CA06.
102 ICP Shared RAM Initialization. Replace the CPM
CPM_CA06.
111 ICP ASIC Register Access Test. Replace the CPM
CPM_CA06.
112 ICP ASIC Unique Address Echo Test. Correct access
to the ICP Shared RAM from the ICP ASIC is verified
through the Echo Test, by asking the ASIC to write each
locations address at that address. This test is
performed once for the address and once for the
complement of the address.
Replace the CPM
CPM_CA06.
113 Verify that the ICP ASIC can be locked out of ICP
Shared RAM.
Replace the CPM
CPM_CA06.
114 ICP Clock test to compare the ICP ASIC clock against
the CPU clock to make sure they are running at the
same relative rates.
Replace the CPM
CPM_CA06.
Test Sequence Numbers
CPM
492 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
TSN Description Corrective
Action
116 ICP ASIC Interrupt Test. Replace the CPM
CPM_CA06.
120 Synchronization Hardware (i.e. Tracker mechanism)
test to ensure the controller redundancy specific
hardware works as expected.
Replace the CPM
CPM_CA06.
130 Perform Application personality parity/edac scan. Replace the CPM
CPM_CA06.
131 Erase the Application personality if the previous test
indicated a parity/edac error.
Replace the CPM
CPM_CA06.
132 Perform parity/edac scan on the Application personality
area, which has been erased.
Replace the CPM
CPM_CA06.
133 Compute CPM Application personality checksum and
compare with embedded value. A key is written in RAM
to indicate whether the personality is invalid or valid
depending on whether a checksum error was detected
or not respectively. In other words, checksum error
detection forces the CPM to execute its Boot
personality.
N/A
255 The CPM has completed startup diagnostics. The
Alphanumeric Display is updated to display either PASS
when starting the operating system in the Boot firmware
or BOOT when starting the operating system in the
Application firmware.
Replace the CPM
CPM_CA06.

Test Sequence Numbers
RM
Release 100 Experion PKS Troubleshooting and Notifications Reference 493
1/03 Honeywell Part I
RM
The following table indicates the major tests performed during RM startup, their test
sequence numbers and their order of execution.
On any failure, the test loops at that location so the problem can be easily diagnosed.
If the RM displays any THxy code (where xy is any 2 alphanumeric characters) for
more than 30 seconds, then a fault has occurred.
Corrective Actions
First, take RM Corrective Action RM_CA02.
If the problem persists, take RM Corrective Action RM_CA01.
And if it still persists, take the General Corrective Action GEN_CA01.
Test Sequence Numbers
The list of THxy codes below are offered for reference purposes only. The corrective
action above is the same for all codes listed.

TH00 - Startup Self Test, Phase 1 Initialization. Phase 1 focuses on CPU and
Memory testing, and executes out of RM Flash memory.
TH01 - Arbalest Registers Default Value Test.
TH02 - Arbalest Internal RAM (via Arbalest BIST)
TH05 - Hardware Control/Status Register Verification Test
TH10 - LED and 4-Char Display Verification Test
TH40 - Local RAM, Walking Data Bit Test, Lower half
TH41 - Local RAM, Walking Data Bit Test, Upper half
TH42 - Local RAM, Walking Address Bit Test, Lower half
TH43 - Local RAM, Walking Address Bit Test, Upper half
TH44 - Local RAM, Bus Access Test, Lower half
TH45 - Local RAM, Bus Access Test, Upper half
TH46 - Local RAM, Data Storage Test, Lower half
TH47 - Local RAM, Data Storage Test, Upper half
Test Sequence Numbers
RM
494 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
TH50 - ECC RAM, Walking Data Bit Test, Lower half
TH51 - ECC RAM, Walking Data Bit Test, Upper half
TH52 - ECC RAM, Walking Address Bit Test, Lower half
TH53 - ECC RAM, Walking Address Bit Test, Upper half
TH56 - ECC RAM, Data Storage Test, Lower half
TH57 - ECC RAM, Data Storage Test, Upper half
TH61 - EDAC Code Generation Test
TH62 - EDAC Single Bit Detection/Correction Test
TH63 - EDAC Double Bit Detection Test
TH70 - Shared Bus I/F, Arbitration vs. Wait States
TH71 - Shared Bus I/F, Access vs. Wait States
TH72 - Shared Bus I/F, Parity Checking vs. Wait States
TH73 - Shared Bus I/F, Comm Controller Access vs. Wait States (including a simple
Tx to Rx Transfer)
TH80 - Shared RAM, Walking Data Bit Test
TH82 - Shared RAM, Walking Address Bit Test
TH84 - Shared RAM, Bus Access Test
TH86 - Shared RAM, Data Storage Test
TH91 - Parity RAM, Parity Generation and Storage Test
TH99 - Startup Self Test, Phase 1 Termination
TH** - During this time, the RM is transferring its application firmware from
Flash to RAM, after which it begins execution from RAM.
THA0 - Startup Self Test, Phase 2 Initialization. Phase 2 testing focuses on RM
peripheral testing, and executes out of RAM.
THB0 - Exception Handler Verification Test Initialization
THBE - Arbalest Fault Interrupt (Parity) Test
THBS - SYS_FAIL_L Interrupt Test
THC0 - Arbalest Transmit Comm, Test Initialization
Test Sequence Numbers
RM
Release 100 Experion PKS Troubleshooting and Notifications Reference 495
1/03 Honeywell Part I
THCA - Arbalest Transmit Comm, Tx Queue Pattern Test
THCB - Arbalest Transmit Comm, Tx Queue Index/Count Test
THCC - Arbalest Transmit Comm, Tx Descriptor ID Port Test
THCH - Arbalest Transmit Comm, Receive ID Queue Test
THCJ - Arbalest Transmit Comm, Rx Queue Index/Count Test
THCK - Arbalest Transmit Comm, Rx Descriptor ID Port Test
THDA - Arbalest Transmit Comm, Local RAM TX Descriptor Processing Test
THDB - Arbalest Transmit Comm, Illegal Descriptor ID Test
THDC - Arbalest Transmit Comm, Bogus Descriptor Address Test
THDD - Arbalest Transmit Comm, Invalid Descriptor Type Test
THDE - Arbalest Transmit Comm, Invalid Destination ID Test
THDF - Arbalest Transmit Comm, Bogus Buffer Address Test
THDG - Arbalest Transmit Comm, Lookup Table Double-Bit Error Test
THDH - Arbalest Transmit Comm, Tx Descriptor Double-Bit Error Test
THDJ - Arbalest Transmit Comm, Tx Lookup Table/Descriptor Single-Bit Error Tests
THDK - Arbalest Transmit Comm, Word and Packet Count Verification
THEA - Arbalest Transmit Comm, Tx Shared Bus Descriptor Tests, Initialization
THEB - Arbalest Transmit Comm, SB Tx Descriptor Processing Tests
THEC - Arbalest Transmit Comm, Bogus Descriptor Address Test
THED - Arbalest Transmit Comm, Invalid Descriptor Type Test
THEE - Arbalest Transmit Comm, Invalid Destination Id Test
THEF - Arbalest Transmit Comm, Bogus Buffer Address Test
THEG - Arbalest Transmit Comm, Lookup Table Parity Error Test
THEH - Arbalest Transmit Comm, Tx Descriptor Parity Error Test
THEJ - Arbalest Transmit Comm, Tx Descriptor Shared Bus Access Test
THEK - Arbalest Transmit Comm, Word And Packet Count Verification Test
THFA - Arbalest Transmit Comm, Local Bus Buffer Access Tests, Initialization
Test Sequence Numbers
RM
496 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
THFB - Arbalest Transmit Comm, Burst = 4, Buffer Size = 1
THFC - Arbalest Transmit Comm, Burst = 4, Buffer Size = 3
THFD - Arbalest Transmit Comm, Burst = 4, Buffer Size = 4
THFE - Arbalest Transmit Comm, Burst = 4, Buffer Size = 5
THFF - Arbalest Transmit Comm, Burst = 4, Buffer Size = 20
THFG - Arbalest Transmit Comm, Burst = 8, Buffer Size = 7
THFH - Arbalest Transmit Comm, Burst = 8, Buffer Size = 8
THFJ - Arbalest Transmit Comm, Burst = 8, Buffer Size = 9
THFK - Arbalest Transmit Comm, Burst = 16, Buffer Size = 15
THFL - Arbalest Transmit Comm, Burst = 16, Buffer Size = 16
THFM - Arbalest Transmit Comm, Burst = 16, Buffer Size = 17
THFN - Arbalest Transmit Comm, Burst = 16, Buffer Size = 20
THFP - Arbalest Transmit Comm, Burst = 16, Buffer Size = 0x8000 (Word Count
Rolldown)
THGA - Arbalest Transmit Comm, Shared Bus Buffer Access Tests, Initialization
THGB - Arbalest Transmit Comm, Burst = 4, Buffer Size = 1
THGC - Arbalest Transmit Comm, Burst = 4, Buffer Size = 3
THGD - Arbalest Transmit Comm, Burst = 4, Buffer Size = 4
THGE - Arbalest Transmit Comm, Burst = 4, Buffer Size = 5
THGF - Arbalest Transmit Comm, Burst = 4, Buffer Size = 20
THGG - Arbalest Transmit Comm, Burst = 8, Buffer Size = 7
THGH - Arbalest Transmit Comm, Burst = 8, Buffer Size = 8
THGJ - Arbalest Transmit Comm, Burst = 8, Buffer Size = 9
THGK - Arbalest Transmit Comm, Burst = 16, Buffer Size = 15
THGL - Arbalest Transmit Comm, Burst = 16, Buffer Size = 16
THGM - Arbalest Transmit Comm, Burst = 16, Buffer Size = 17
THGN - Arbalest Transmit Comm, Burst = 16, Buffer Size = 20
Test Sequence Numbers
RM
Release 100 Experion PKS Troubleshooting and Notifications Reference 497
1/03 Honeywell Part I
THGP - Arbalest Transmit Comm, Burst = HF/4, Buffer Size = 30
THGQ - Arbalest Transmit Comm, Burst = HF/8, Buffer Size = 30
THGR - Arbalest Transmit Comm, Burst = HF/16, Buffer Size = 30
THGS - Arbalest Transmit Comm, Burst = F, Buffer Size = 33
THHA - Arbalest Transmit Comm, Transmit Channel Operational Test, Initialization
THHB - Arbalest Transmit Comm, Transmit Channel Enable/Disable/Busy Tests
THHC - Arbalest Transmit Comm, Enable/Impact Verification Test
THHD - Arbalest Transmit Comm, Transmit Channel Reset/Abort Tests
THHE - Arbalest Transmit Comm, Send ACK When Tx Disabled Test
THHF - Arbalest Transmit Comm, Send ACK When Acknowledge Enabled Test
THHG - Arbalest Transmit Comm, Send ACK When Tx Enabled Test
THHH - Arbalest Transmit Comm, Send ACK With Tx Buffer Full Test
THHJ - Arbalest Transmit Comm, Send ACK With Tx Buffer Full And Tx Channel
Enabled Test
THHK - Arbalest Transmit Comm, Tx Descriptor Processing With Tx Buffer Full
THHL - Arbalest Transmit Comm, Tx Buffer Content Validation
THJA - Arbalest Transmit Comm, Tx Acknowledge Tests, Initialization
THJB - Arbalest Transmit Comm, Tx Acknowledge Enable Test
THJC - Arbalest Transmit Comm, Tx ACK/ACK Enabled/Invalid ACK Tests
THJD - Arbalest Transmit Comm, ACK Timer/ACK Enable/TX Disable Test
THJE - Arbalest Transmit Comm, Acknowledge Turn-Off/Turn-On Test
THJF - Arbalest Transmit Comm, ACK Word Error Tests
THJG - Arbalest Transmit Comm, Tx Acknowledge/Tx Enabled Tests - No Rollback
THJH - Arbalest Transmit Comm, Tx Acknowlegde/Tx Enabled - Rollback Test
THJJ - Arbalest Transmit Comm, Tx Acknowledge Timeout Test
THJK - Arbalest Transmit Comm, Tx Acknowledge Tests - Same Slot - Success
THJL - Arbalest Transmit Comm, Tx Acknowledge Tests - Same Slot - No Rollback
Test Sequence Numbers
RM
498 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
THJZ - Arbalest Transmit Comm, Testing Cleanup
THK0 - Arbalest Receive Comm, Test Initialization
THKA - Arbalest Receive Comm, Packet with No Errors Test
THKB - Arbalest Receive Comm, Header with Bad Buffer Address Test
THKC - Arbalest Receive Comm, Header with Bad Descriptor Address Test
THKD - Arbalest Receive Comm, Header with Bad Descriptor Type Test
THKE - Arbalest Receive Comm, Header with Unavailable Descriptor Test
THKF - Arbalest Receive Comm, Packet with Data Block Too Big Test
THKG - Arbalest Receive Comm, Packet Duplicate Test
THLA - Arbalest Receive Comm, Header with No Error Overwrite Available Test
THLB - Arbalest Receive Comm, Header with Overwrite Unavailable Test
THLC - Arbalest Receive Comm, Header with NoError With Noise Test
THLD - Arbalest Receive Comm, Header with Admin2 Walk Parity Errors Test
THLE - Arbalest Receive Comm, Header with Various Parity Errors Test
THLF - Arbalest Receive Comm, Header with Various Special Codes Test
THLG - Arbalest Receive Comm, Header with Sliding EOF Test
THLH - Arbalest Receive Comm, Header with Sliding Packets Test
THLJ - Arbalest Receive Comm, Header with CRC Error Test
THMB - Arbalest Receive Comm, Packet with Sliding EOF Burst Length Test
THMC - Arbalest Receive Comm, Packet with Early SOF Test
THMD - Arbalest Receive Comm, Packet with CRC Error Test
THME - Arbalest Receive Comm, Packet with Parity Errors Test
THMF - Arbalest Receive Comm, Packet with Context Errors Test
THMG - Arbalest Receive Comm, Packet with Ack Word Test
THMJ - Arbalest Receive Comm, Packet with Abort Test
THMM - Arbalest Receive Comm, Packet with No Errors (Again) Test
THMP - Arbalest Receive Comm, Packet with SB Burst Length Wait States Test
Test Sequence Numbers
RM
Release 100 Experion PKS Troubleshooting and Notifications Reference 499
1/03 Honeywell Part I
THMZ - Arbalest Receive Comm, Testing Cleanup
THP0 - Arbalest HotLink I/F, Tx Bfr Test, Test Initialization
THPA - Arbalest HotLink I/F, Tx Bfr Test, Empty Flag Test
THPB - Arbalest HotLink I/F, Tx Bfr Test, Half-Full Flag Test
THPC - Arbalest HotLink I/F, Tx Bfr Test, Full Flag Test
THPD - Arbalest HotLink I/F, Tx Bfr Test, Walking Ones/Zeros Test
THQA - Arbalest HotLink I/F, Rx Bfr Test, Empty Flag Test
THQB - Arbalest HotLink I/F, Rx Bfr Test, Half-Full Flag Test
THQC - Arbalest HotLink I/F, Rx Bfr Test, Full Flag Test
THQD - Arbalest HotLink I/F, Rx Bfr Test, Walking Ones/Zeros Test
THRA - Arbalest HotLink I/F, Tx/Rx Test, Transmit Buffer Clear Tes
THRB - Arbalest HotLink I/F, Tx/Rx Test, Receive Buffer Clear Test
THRC - Arbalest HotLink I/F, Tx/Rx Test, Transmit Interface Enable/Disable Test
THRE - Arbalest HotLink I/F, Tx/Rx Test, Receive Interface Enable/Disable Test
THRF - Arbalest HotLink I/F, Tx/Rx Test, Transmit/Receive Data Transfer Test
THSA - Arbalest HotLink I/F, HOTLink BIST
THSZ - Arbalest HotLink I/F, Testing Cleanup
THZZ - Phase 2 Cleanup. End of RM Startup Self Testing.

Test Sequence Numbers
SIM
500 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
SIM
The following table indicates the major tests performed during SIM startup diagnostics,
their test sequence numbers and their order of execution.



ATTENTION
This information is offered for reference purposes only. Should the user find
that the SIM has failed one of these startup tests, the module should be
replaced.

These tests are linear sequence, which uses very few subroutines and no stack. On any
failure, the test loops at that location so the problem can be easily diagnosed. Note that
an abnormal condition exists if the CPM remains in a particular test for more than 30
seconds at which time the specified corrective action should be performed.
In order that all LED colors can be checked by the factory test technician:
The Health LED (right-hand) will be turned RED to start. It will be turned GREEN upon
successful completion of selftest.
The Channel Activity LEDs will be turned RED until completion of the Alphanumeric
Display Test. They will be turned GREEN until completion of the ROM test.
Test Sequence Numbers are output first to the Factory Test Port and then to the
Alphanumeric Display.
Table of SIM Test Sequence Numbers

TSN Description Probable
Cause for
Error
Action
on Error
0 Alphanumeric Display and LED Test -- This test walks
horizontal/vertical bars, then flashes all segments of the
display through stages of brightness. The technician
who places the boards in the test fixture needs to see
this test operate before closing the chamber. This test
number will be output only to the Test Port, not to the
Display. For this test to work, CPU, Flash ROM,
address bus, data bus and some of the hardware
control logic must be working.
The firmware version is briefly displayed after this test.
Hardware
control
registers are
not writable,
CPU PLD.
FAULT
Test Sequence Numbers
SIM
Release 100 Experion PKS Troubleshooting and Notifications Reference 501
1/03 Honeywell Part I
TSN Description Probable
Cause for
Error
Action
on Error
1 CPU Type & Version Check. This test is done before
the ROM tests because a wrong CPU could appear to
succeed but might fail timing tests. The CPU version is
also displayed as E40+ or E41+ for 603e Rev 4.0 or
4.1, 100 MHz.
Wrong CPU
chip installed.
FAULT
10 Flash ROM parity scan -- For each ROM line (8 bytes)
of the 1MB Boot Image area, the data is read and the
expected parity is computed and compared with the
actual parity. The test is timed.
Flash chip. FAULT
11 Flash ROM parity scan time -- the time needed to
perform the above test is checked for reasonability. This
test detects 603 Instruction Cache failure and/or ROM
wait state problems.
Instruction
Cache, MEM
PLD wait
states.
FAULT
12 Flash ROM checksum The checksum of the boot
personality in ROM is computed and verified.
Flash chip. FAULT
13 Flash ROM Loader checksum The checksum of the
boot personalitys Flash ROM loader is computed and
verified.
Flash chip. FAULT
15 XILINX DRAM Controller ASIC Ready check (Hardware
Status Register [MEM_STATUS]). This bit is asserted if
the XILINX did not power up properly.
Hardware
Status Register
chips, XILINX
FAULT
16 XILINX DRAM Controller ASIC Load -- The XILINX
configuration file is written one bit at a time to the chip.
MEM PLD FAULT
17 XILINX DRAM Controller ASIC Error Check (Hardware
Status Register [MEM_STATUS]). This bit is asserted if
the XILINX did not configure properly.
Hardware
Status Register
chips, XILINX,
MEM PLD
FAULT
18 XILINX DRAM Controller ASIC read-back verify -- The
XILINX configuration file is read back 32 bits at a time,
and 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.
XILINX, MEM
PLD
FAULT
20-
3x
Various RAM/Parity/Interrupt Tests For all: RAM,
XILINX,
buffers, MEM
PLD.

Test Sequence Numbers
SIM
502 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
TSN Description Probable
Cause for
Error
Action
on Error
20 RAM path verifies that RAM can be read/written as
32-bit words. This is the first and simplest way to access
RAM. It is also the only way to know if the XILINX was
configured properly.
FAULT
21 RAM parity path -- writes two 8-byte patterns and
verifies that parity byte was set correctly, even and odd.
FAULT
22 RAM word access verifies that word patterns can be
written and read, including three cases of miss-aligned
transfer.
FAULT
23 RAM byte access verifies that writing a string of 8
bytes can be read back as 2 correct words, and as 8
bytes.
FAULT
24 RAM half access verifies that half words can be read. FAULT
25 RAM byte write verifies that bytes can be written
correctly.
FAULT
26 RAM half write verifies that half-words can be written
correctly.
FAULT
27 RAM half align verifies that half-words can be written
and ready when miss-aligned.
FAULT
28 RAM word align verifies that words can be written and
ready when miss-aligned.
FAULT
29 RAM double access verifies that the floating point unit
can write and read a double-word value, and the same
value is correctly stored as two words.
FAULT
30 EDAC Correction Verifies that any single-bit error 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.
FAULT
31 EDAC Error Test verifies that a double-bit error can be
detected, in both high and low word.
FAULT
Test Sequence Numbers
SIM
Release 100 Experion PKS Troubleshooting and Notifications Reference 503
1/03 Honeywell Part I
TSN Description Probable
Cause for
Error
Action
on Error
32 Stuck Machine Check interrupt after verifying that no
machine check source is active in the Hardware Status
Register, unmasks the exception. No interrupt is
expected.
Hardware
Status Register
chips, CPU
PLD, MEM
PLD
FAULT
33 Data Parity Interrupt -- verify that the data parity error
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 8, 8-byte lines, each with a parity error
in a different byte, such that all byte lanes are covered.
Parity buffers,
parity circuit
(CPU PLD?)
FAULT
34 RAM parity sweep The RAM is read 2 words at a 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 of RAM.
Stress Screen can log the time for this test for profiling.
On an error, the memory retention magic number is
cleared to force the destructive memory test.
Destruc-
tive
RAM
Test
35 RAM Single-bit Error Threshold test -- The number of
single-bit errors is compared against a threshold. High
temperatures may cause a number of single-bit errors,
so this test is skipped in Factory Test.
RAM self-
refresh control,
very high temp.
FAULT
36 RAM parity sweep time the time needed to perform
the above test is checked for reasonability, using the
PPC 603 decrementer. 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.
Instruction
Cache, MEM
PLD wait
states
FAULT
37 EDAC Interrupt verifies that a double-bit error will
generate the correct machine check exception.
XILINX chip,
Hardware
Status Register
chips, MEM
PLD, CPU PLD
FAULT
Test Sequence Numbers
SIM
504 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
TSN Description Probable
Cause for
Error
Action
on Error
40 RAM Memory Retention Test The magic numbers are
checked to see if the data in RAM may still be valid. In
the absence of parity errors, RAM is considered valid at
the boot level. If passes test, bumps power cycle
counter and skips destructive test and flush.
Battery low Fall into
Destruc-
tive
Test.
41 RAM Destructive Pattern Test. Checks address and
data lines by 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.
XILINX, RAM
chip, MEM
PLD
FAULT
42 Flush RAM Data Zeros Write zeros to all locations and
verify. Data parity is enabled during this test. Runs with
data parity enabled and fatal.
XILINX, RAM
chip, MEM
PLD
FAULT
43 Flush RAM Parity Ones verify that Flush RAM Data
Zeros test forced parity byte to ones (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.
RAM chip,
XILINX,
Parity/check bit
buffers
FAULT



ATTENTION
Note that after the RAM tests, data parity detection is disabled.

50 CPU I-Cache Active Test Compare how many times a
loop runs in one clock tick with I-Cache disabled and
enabled.
May not need to do this test because ROM timing test
may show whether I-Cache is working or not.
FAULT
5x Other I-Chache Tests. FAULT
55 CPU D-Cache Active Test Enable cache and execute
a RAM write/verify loop. Verify that it runs faster than it
would if the cache were broken or disabled.
Flush/disable cache and verify that the data was written
to RAM correctly. Only uses the memory test area, so
just shows that the data cache is enabled and at least
partially functional.
CPU FAULT
Test Sequence Numbers
SIM
Release 100 Experion PKS Troubleshooting and Notifications Reference 505
1/03 Honeywell Part I
5 CPU D-Cache Function Test The checksum of the
boot code is repeated with Data Cache enabled. The
test is timed. If the data cache is not working properly,
the checksum will fail or the test will take too long.
CPU FAULT
5x Other D-Cache Tests. FAULT
60-
7x
Hardware Status Register and System Controls Tests.
Until these status checks are made, interrupts (SMI,
INT, DEC) cannot be enabled. Machine Check is
enabled and checked separately. Data parity is disabled
for each hardware status register read operation.
For all:
Hardware
Status Register
chips, CPU
PLD

60 Hardware Status Register Access Test Verifies that
the Hardware Status Register appears to be readable
without generating a machine check exception.
FAULT
61 Hardware Status Register Battery Load Test Verifies
that Battery Load Applied changes state per the Battery
Load Apply/Remove controls. This test is performed
early because it is the only test with feedback.
FAULT
62 Hardware Status Register DC_FAIL Test Verifies that
the DC_FAIL/SRESET status is not asserted.
Backplane, P/S FAULT
63 Hardware Status Register FTA_INT Test Verifies that
the FTA DUART interrupt status is not asserted.
CPU card
DUART
FAULT
64 Hardware Status Register ICP_INT Test Verifies that
the ICP_INT status is not asserted.
ICP ASIC FAULT
65 Hardware Status Register DEV_INT Test Verifies that
the DEV_INT (interrupt from development board) status
is not asserted.
Dev Card
DUART.Dev
Card PLD.CPU
PLD.
FAULT
66 Hardware Status Register MEM_INT Test Verifies that
the MEM_INT (interrupt from memory board) status is
not asserted.
XILINX, MEM
PLD
FAULT
67 Hardware Status Register SYS_FAIL Test Verifies
that the SYS_FAIL status is not asserted for longer than
a TBD period, to accommodate other modules tests.
CPU PLD,
backplane,
other modules.
FAULT
68 Hardware Status Watchdog Timer Timeout Pending
Test Verifies that the WDT_PENDING status is not
asserted.
PLD, WDT
Chip
FAULT
Test Sequence Numbers
SIM
506 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
69 Hardware Status DUART Interrupt Pending Test
Verifies that the DUART_INT status is not asserted.
DUART FAULT
70 Hardware Status Register ICP_FAULT Test Verifies
that the ICP_FAULT status is not asserted. This would
indicate that the ICP ASIC had failed to come out of
reset.
ICP ASIC FAULT
71 ICP ASIC Release and Stuck Interrupt Test Enables
interrupts to make sure that there is no interrupt stuck in
the asserted state. Because the Hardware Status
Register has been tested for potential interrupt sources,
no interrupt is expected.
Interrupts are disabled after this test. If any interrupt
source is stuck, this test will fail to return from the
interrupt level.
Writes hardware setup parameters (such as odd parity,
one wait-state) to the ICP ASIC. The ASIC firmware
reinitializes.
ICP ASIC FAULT
72 SYS_FAIL Assert Test Verifies that SYS_FAIL system
controls assert and deassert the SYS_FAIL condition.
Uses timeouts to prevent conflicts with other modules
under test on the same backplane. No SYS_FAIL
interrupt test. This test will fail if another module leaves
STS_FAIL asserted.
Only execute when in Factory Test mode.
CPU PLD,
backplane,
other modules
FAULT
73 Watchdog Timer Test Verifies that the WDT does not
expire when hit for 500 msec, 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.
CPU PLD,
WDT Chip, ICP
ASIC, ICP
Oscillator
FAULT
80-
89
FTA DUART Tests For all: CPU
card DUART

80 FTA DUART Register Access Test Verifies that the
DUART can be initialized.
CPU PLD FAULT
Test Sequence Numbers
SIM
Release 100 Experion PKS Troubleshooting and Notifications Reference 507
1/03 Honeywell Part I
81 FTA DUART Clock Compare Test -- Check the DUART
clock against 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.
DUART Crystal FAULT
82 FTA DUART Interrupt Test Verifies that the DUART
can 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.
CPU PLD FAULT
83 FTA DUART Channel A Transceiver and Loopback Test
verifies that data cannot be transmitted or received if
either transceiver is disabled, but data can be
transmitted and received when both are enabled.
Transceivers FAULT
84 FTA DUART Channel B Transceiver and Loopback Test
verifies that data cannot be transmitted or received if
either transceiver is disabled, but data can be
transmitted and received when both are enabled.
Transceivers FAULT
100
-1xx
ICP Shared RAM Tests For all: RAMs,
buffers, CPU
PLD, ICP ASIC
FAULT
100 ICP Shared RAM Destructive Pattern Test. Checks
address and data lines by 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.
Shared RAM
chip, buffers,
arbitration
FAULT
101 ICP Shared RAM Destructive Pattern Parity Interrupt
Check verify that 603 data parity error did not occur
during previous test. Runs with data parity enabled and
fatal.
Shared RAM
chip, buffers,
arbitration
FAULT
102 ICP Shared RAM Initialization to force correct odd
parity. Verified. This must be done before writing to the
ASIC control registers. Runs with data parity enabled
and fatal.
Shared RAM
chip, buffers,
arbitration
FAULT
110
-
119
ICP ASIC Tests
Test Sequence Numbers
SIM
508 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
110 N/A
111 ICP ASIC Register Access Test The hardware setup
parameters 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 location in Shared RAM. This
value is saved in RAM. The rest of Shared RAM is
verified to make sure that only the designated location
was written.
ICP ASIC,
ASIC-RAM I/F
FAULT
112 ICP ASIC Unique Address Echo Test Correct access
to the ICP shared RAM from the ASIC is verified
through the Echo Test, by asking the ASIC to write each
locations 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
the ASIC.
ICP ASIC,
ASIC-RAM I/F
FAULT
113 ICP Bus Lock Test Verify that the ICP ASIC can be
locked out of it Shared RAM by the 603. This is
accomplished with the ASIC Echo_REV Test by: 1)
locking the bus 2) telling the ASIC to write to a specified
address, 3) looking at the address, 4) unlocking the bus,
5) looking at the address to see that it changed and the
correct data was written.
Bus lock or
arbitration
circuit (CPU
PLD) ICP
ASIC.
FAULT
114 ICP Clock Compare Test Check the ASIC clock
against the 603 clock to make sure they are running at
the same relative rates. The ICP ASIC 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.
603 Oscillator,
ICP ASIC
Oscillator
FAULT
115 ICP ASIC Interrupt Test The ICP ASIC timer interrupt
is enabled, along with the CPU external interrupt, to see
if the interrupt generation and recognition works and the
Hardware Status Register ICP_INT is asserted. The
ASIC timer is disabled, and the CPU interrupt inhibited,
after the test.
Hardware
Status Register
chips, ICP
ASIC
FAULT
130 Personality Parity Check A parity interrupt scan is
performed of the 3MB personality area.
No personality,
bad personality
load
Persona
l-ity is
erased.
Test Sequence Numbers
SIM
Release 100 Experion PKS Troubleshooting and Notifications Reference 509
1/03 Honeywell Part I
131 Personality Area Erase If the previous test indicated a
parity error, the 3MB personality area is erased and
verified.
Bad flash chip FAULT
132 Personality checksum -- If the previous test indicated no
parity error, and a personality is present, the personality
checksum is verified. If no errors, a key is written in
RAM to indicate that the personality is valid.
Bad personality
load
Persona
l-ity is
ignored.
255 PCM Signals end of selftest. The HEALTH LED is made
GREEN. Depending on various state flags and whether
RAM was flushed, selftest will exit to the Alive/Fail
executive or start the personality. Displays BOOT when
starting the personality and PASS when starting the
Alive executive.
N/A N/A

Test Sequence Numbers
SIM
510 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03

Release 100 Experion PKS Troubleshooting and Notifications Reference 511
1/03 Honeywell Part I
Corrective Actions
General
GEN_CA01
Call TAC for assistance.
GEN_CA02
Cycle power to the chassis.

Corrective Actions
BEM
512 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
BEM
BEM_CA01
Check the BEM.

If ... Then ...
If the BEM front panel indicator
is off,
Ensure chassis power is applied and/or BEM is
fully inserted into the chassis.
If that doesnt work, Replace the BEM.

BEM_CA02
Recharge the BEM.

If ... Then ...
If the BEM OK
LED is solid red,
1. Verify that the battery-pack has been inserted into the BEM
(usually done at time of installation).
2. Otherwise, if the battery-pack is present, then its capacity is
not within spec. Replace the BEM to reinstate the battery-
backed protection of the CPM control strategy and perform
the following steps to attempt to repair the deficient BEM.
Allow the BEM to recharge the battery-pack in a powered
chassis for 24 hours. The battery-pack may have originally
been drained after the chassis has been powered down for
an extended period of time.
If the battery pack fails to charge after sitting in a powered
chassis for 24 hours, replace the battery-pack.
If the BEM LED is not solid green with a new battery-pack,
then the BEM circuitry and/or ICP connector is defective.
Note that the battery-pack may still be salvaged by
recharging (for 24 hours in a powered chassis) using another
BEM.

Corrective Actions
CNI
Release 100 Experion PKS Troubleshooting and Notifications Reference 513
1/03 Honeywell Part I
CNI
CNI_CA01
To replace a CNI,

If Then
the CNI resides in an
On-Control PRIMARY,
remove SECONDARY chassis power,
then replace the PRIMARY CNI,
then wait for the PRIMARY CNI to successfully
complete startup,
then return SECONDARY chassis power.

the CNI resides in an
Off-Control PRIMARY,
remove SECONDARY chassis power,
then a few seconds later remove PRIMARY chassis
power,
then replace the PRIMARY CNI,
then return PRIMARY chassis power,
then wait for the PRIMARY to successfully
complete startup,
then return SECONDARY chassis power.

the CNI resides in a
SECONDARY,
remove SECONDARY chassis power,
then replace the SECONDARY CNI,
then return SECONDARY chassis power.

Corrective Actions
CNI
514 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
CNI_CA02
To reset a CNI,

If Then
the CNI resides in an
On-Control PRIMARY,
remove SECONDARY chassis power,
then remove and re-insert the PRIMARY CNI,
then wait for the PRIMARY CNI to successfully
complete startup,
then return SECONDARY chassis power.

the CNI resides in an
Off-Control PRIMARY,
remove SECONDARY chassis power,
then a few seconds later remove PRIMARY chassis
power,
then return PRIMARY chassis power,
then wait for the PRIMARY to successfully
complete startup,
then return SECONDARY chassis power.

the CNI resides in a
SECONDARY,
remove SECONDARY chassis power,
then return SECONDARY chassis power.


Corrective Actions
CPM
Release 100 Experion PKS Troubleshooting and Notifications Reference 515
1/03 Honeywell Part I
CPM
CPM_CA01
Check the CPM.

If ... Then ...
If all the CPM front panel
indicators are off,
Ensure chassis power is applied and/or CPM is fully
inserted into the chassis.
If that doesnt work, Replace the CPM CPM_CA06.

CPM_CA02
Load the CPM firmware.

If ... Then ...
If the CPM is in the
Alive or Ready
State,
Utilize NetworkTools utility to load the CPM Boot and/or
Application personality firmware.
If the CPM is in the
Loading State,
Await CPM Application or Boot personality-download
completion. Otherwise, if the current firmware download
session terminated abnormally:
Ensure downloading the correct personality for the
module type.
Attempt to reload the CPM personality firmware using
the NetworkTools utility.
If repeated attempts to load CPM personality firmware
are unsuccessful, replace the CPM CPM_CA06.

CPM_CA03
Isolate reason for loss-of-synchronization.

If ... Then ...
If RM COM LED is
off,
Ensure redundancy cable is present and attached to both the
primary and secondary RM.

Corrective Actions
CPM
516 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
CPM_CA04
Recover from CPM Fail State.

Step Action
1 Acquire the CPM crash block using either the NetworkTools or the CPMTools
utility. This information is necessary for the generation of an effective defect
report.
2 Interpret the CPM Fault Codes and perform any additional corrective action
specific to the individual CPM Fault Code extracted from the crash block in
step #1 or the CPM Alphanumeric Display.
3 Issue the Recover command to the CPM in the Fail State using either the
NetworkTools or CPMTools utilities. If the CPM does not reboot into the Alive
or Ready States either {1} interpret the new CPM Fault Codes or {2} replace
the CPM CPM_CA06, if the same Fault Code persists.
4 Once the CPM transitions into the Ready State issue the Start command using
either the NetworkTools or CPMTools utilities. If the CPM does not reboot into
the NotLoaded or Backup States either {1} interpret the new CPM Fault Codes
or {2} replace the CPM CPM_CA06, if the same Fault Code persists.
5 If the CPM is in the Alive State, load the CPM Boot and/or Application
personality firmware using the NetworkTools utility.

CPM_CA05
Restart the CPM.

If ... Then ...
If the CPM is in the secondary chassis, Power-cycle the secondary chassis.
If the CPM is the only control agent (e.g.
no other controller or I/O) within the
chassis,
Power-cycle the primary/non-redundant
chassis.
Otherwise, if other control agents are
present in the primary/non-redundant
chassis,
Remove-and-insert the CPM under power.
However, take into consideration that the
chassis backplane can only support a
finite number of module removals and
insertions while power is applied.

If restarting the CPM does not resolve the problem replace the CPM CPM_CA06.
Corrective Actions
CPM
Release 100 Experion PKS Troubleshooting and Notifications Reference 517
1/03 Honeywell Part I
CPM_CA06
Replace the CPM.

If ... Then ...
If the CPM is the only control agent (e.g.
no other controller or I/O) within the
chassis,
Perform CPM replacement with chassis
power removed.
Otherwise, if other control agents are
present in the chassis,
Replace the CPM without removing
chassis power. However, take into
consideration that the chassis backplane
can only support a finite number of module
removals and insertions while power is
applied.

CPM_CA07
Replace defective battery or correct invalid battery configuration. There are two types of
batteries used for CPM memory retention:
5. The lithium battery in the front of the CPM
6. The Ni-Cad Battery Extention Module (BEM) residing in the chassis.

If ... Then ...
If no batteries are present, Equip the CPM with one type of battery.
If only one battery is present, Replace the battery because it is drained and/or
damaged.
If two batteries of proper voltage
are present,
Remove one of the batteries. Note that having
two batteries (of proper voltage) present is a minor
fault condition.

Corrective Actions
CPM
518 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
CPM_CA08
Check the RM resident in the CPM chassis.

If ... Then ...
If the RM faulted, Interpret the RM fault code.
Otherwise if the RM appears
healthy,
Either power-cycle the chassis or remove-and-
replace the RM with power applied depending
whether the RM is in the secondary or primary
redundancy role respectively.
If that doesnt work, Restart the CPM CPM_CA05.

CPM_CA09
Activate the CPM control strategy using Control Builder or the appropriate SCAN
display.
CPM_CA10
If necessary, create/modify control strategy using Control Builder. Load new/existing
control strategy using the Control Builder.
CPM_CA11
Reload the CEE FB manually.
CPM_CA12
Interpret the CPM Test Sequence Number displayed on the Alphanumeric Display.
Corrective Actions
CPM
Release 100 Experion PKS Troubleshooting and Notifications Reference 519
1/03 Honeywell Part I
CPM_CA13
Recover from CPM Watchdog Timer timeout. The following recovery procedure
assumes the CPM is the only control agent within the chassis. If this is not the case and
the CPM must be immediately recovered (i.e. without gathering defect information),
simply restart the CPM

Step Action
1 Ensure a battery is present and power-cycle the CPM.
2 The CPM reboots into the Fail State displaying FAIL 0014.
3 Acquire the CPM crash block using either the NetworkTools or the CPMTools
utility.
4 Issue the Recover command to the Failed CPM using either the NetworkTools
or CPMTools utilities.
5 The CPM reboots into the Ready State.
6 Issue the Start command to the Ready CPM using either the NetworkTools or
CPMTools utilities.
7 The CPM reboots into the NotLoaded or Backup State.
8 Replace the CPM if the Watchdog Timer timeout condition reoccurs.

CPM_CA14
Isolate cause of ControlNet communication fault.

Step Action
1 Search the Experion PKS SCAN Alarm Summary display for any revealing
indications as to which communication module and/or cable are in distress.
2 Repair CNI slot x (where x is the slot number embedded in the Experion PKS
Notification text descriptor) communication fault between primary and
secondary chassis.

Corrective Actions
CPM
520 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
CPM_CA15
Attempt switchover to better primary CPM. The goal of the following procedure is to
remove the marginally defective CPM hardware that is currently executing in the primary
redundancy role without loss of control. If unable to achieve synchronization, the
primary CPM must be replaced, CPM_CA06; however, if the user is comfortable
controlling without redundancy for the time being, primary CPM replacement can wait
until a more convenient time.

Step Action
1 Initiate initial synchronization using the Control Builder RM configuration form
or the appropriate SCAN display.
2 When initial synchronization is complete, issue the Initiate Switchover
command to change redundancy roles.
3 Power down the secondary chassis and replace the marginally defective
(original primary) CPM.

CPM_CA16
Check Boot FW revision.

Step Action
1 Using either the NetworkTools or the CPMTools utility verify that the proper
Boot firmware is loaded to the CPM.
2 Reload the CPM Boot firmware using the NetworkTools utility if an older Boot
firmware exists.

CPM_CA17
Isolate communication fault with secondary CPM. Primary CPM aborted initial
synchronization or synchronization maintenance due to communication error with the
secondary CPM (across the RM redundancy cable).

Step Action
1 If the secondary CPM is missing and/or faulted
2 Otherwise, if secondary CPM is present and appears healthy, power cycle the
secondary chassis, and verify auto-synchronization commences if configured
to do so.

Corrective Actions
CPM
Release 100 Experion PKS Troubleshooting and Notifications Reference 521
1/03 Honeywell Part I
CPM_CA18
Recover from secondary I/O CNI ControlNet communication fault.

Step Action
1 If a secondary CNI is faulted, power-cycle the secondary chassis.
2 If a primary CNI is faulted, remove and reinsert the CNI with chassis-power
applied (or power-cycle the primary chassis if not performing control).

CPM_CA19
Check CPM Application firmware compatibility.




CPM_CA20
Check CPM hardware compatibility.




Corrective Actions
I/O Modules
522 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
I/O Modules
IO_CA01
With chassis power removed, replace the I/O module.
IO_CA02
Without removing chassis power, replace the I/O module.
IO_CA03
Without removing chassis power, remove and re-insert the I/O module.

Corrective Actions
Network
Release 100 Experion PKS Troubleshooting and Notifications Reference 523
1/03 Honeywell Part I
Network
NET_CA01
Check the ControlNet cables.
NET_CA02
Check the CNI MAC ID settings.
NET_CA03

NET_CA04

NET_CA05

NET_CA06

Corrective Actions
Rack and Supply
524 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Rack and Supply
CH_CA01
To replace a chassis power supply.

If Then
the supply resides in an On-
Control PRIMARY,
take the controller Off Control,
then remove SECONDARY chassis power,
then a few seconds later remove PRIMARY
chassis power,
then replace the PRIMARY supply,
then repower the PRIMARY and wait for
startup to successfully complete,
then return SECONDARY chassis power.

the supply resides in an Off-
Control PRIMARY,
remove SECONDARY chassis power,
then a few seconds later remove PRIMARY
chassis power,
then replace the PRIMARY supply,
then repower the PRIMARY and wait for
startup to successfully complete,
then return SECONDARY chassis power.

the supply resides in a
SECONDARY,
remove SECONDARY chassis power,
then replace the SECONDARY supply,
then return SECONDARY chassis power.

the supply resides in a non-
redundant controller or in an
I/O rack,
remove chassis power,
then replace the supply,
then return chassis power.
Corrective Actions
Rack and Supply
Release 100 Experion PKS Troubleshooting and Notifications Reference 525
1/03 Honeywell Part I

CH_CA02
To replace the chassis backplane,

If Then
the backplane resides in an
On-Control PRIMARY,
take the controller Off Control,
then remove SECONDARY chassis power,
then a few seconds later remove PRIMARY
chassis power,
then replace the PRIMARY backplane,
then repower the PRIMARY and wait for
startup to successfully complete,
then return SECONDARY chassis power.
the backplane resides in an
Off-Control PRIMARY,
remove SECONDARY chassis power,
then a few seconds later remove PRIMARY
chassis power,
then replace the PRIMARY backplane,
then repower the PRIMARY and wait for
startup to successfully complete,
then return SECONDARY chassis power.
the backplane resides in a
SECONDARY,
remove SECONDARY chassis power,
then replace the SECONDARY backplane,
then return SECONDARY chassis power.
the backplane resides in a
non-redundant controller or in
an I/O rack,
remove chassis power,
then replace the backplane,
then return chassis power.

Corrective Actions
RM
526 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
RM
RM_CA01
To replace an RM,

If Then
the RM resides in an On-
Control PRIMARY,
remove SECONDARY chassis power,
then replace the PRIMARY RM,
then wait for the PRIMARY RM to successfully
complete startup,
then return SECONDARY chassis power.

the RM resides in an Off-
Control PRIMARY,
remove SECONDARY chassis power,
then a few seconds later remove PRIMARY
chassis power,
then replace the PRIMARY RM,
then return PRIMARY chassis power,
then wait for the PRIMARY to successfully
complete startup,
then return SECONDARY chassis power.

the RM resides in a
SECONDARY,
remove SECONDARY chassis power,
then replace the SECONDARY RM,
then return SECONDARY chassis power.


Corrective Actions
RM
Release 100 Experion PKS Troubleshooting and Notifications Reference 527
1/03 Honeywell Part I
RM_CA02
To reset an RM,

If Then
the RM resides in an On-
Control PRIMARY,
remove SECONDARY chassis power,
then remove and re-insert the PRIMARY RM,
then wait for the PRIMARY RM to successfully
complete startup,
then return SECONDARY chassis power.

the RM resides in an Off-
Control PRIMARY,
remove SECONDARY chassis power,
then a few seconds later remove PRIMARY
chassis power,
then return PRIMARY chassis power,
then wait for the PRIMARY to successfully
complete startup,
then return SECONDARY chassis power.

the RM resides in a
SECONDARY,
remove SECONDARY chassis power,
then return SECONDARY chassis power.

Corrective Actions
RM
528 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
RM_CA03
To check and/or replace a Redundancy Cable,
remove SECONDARY chassis power,
then detach the Redundancy Cable,
then verify the ends are clean and polished to the naked eye,
then verify the cable has no sign of kinks or breaks,
replacing the cable if suspect,
checking its replacement in the same manner,
then return SECONDARY chassis power.
Note: Optical cable is sensitive to mishandling, particularly with regard to a tight bend
radius.


Release 100 Experion PKS Troubleshooting and Notifications Reference 529
1/03 Honeywell Part I
Network Configurations
Overview
Addressing
You set the MAC ID (ControlNet address) switches on the partner CNI modules in an
RCP to the same ID (address). The software automatically assigns the switch set address
to the Primary Controller and increments the set address by one for the Secondary
Controller. For example, if you set the switches on the partner CNI modules to 1 for the
Supervisory ControlNet, the address of the Primary Controller is always 1 and the
address for the Secondary Controller is always 2. You must always allocate two
consecutive addresses for partner CNI modules in an RCP.

Network Configurations
Overview
530 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Remote I/O Modules
B A B A B A B A
Redundancy Cable (GN-KRR011)
CNI (TC-CCR011, MAC Setting = 3)
B A
I/O
Chassis
I/O (Field Devices)
I/O ControlNet
To
Server
Redundant
Chassis
Pair
CNI (TC-CCR012, MAC Setting = 1)
C200 CPM (TC-PRS021)
CNI (TC-CCR012,
MAC Setting = 1)
RM (TC-PRR021)
CNI (TC-CCR012, MAC Setting = 1)
C200 CPM (TC-PRS021)
CNI (TC-CCR012,
MAC Setting = 1)
RM (TC-PRR021)


Network Configurations
Complying with minimum redundant controller system requirements
Release 100 Experion PKS Troubleshooting and Notifications Reference 531
1/03 Honeywell Part I
Complying with minimum redundant controller system
requirements
Rules for Conjoined Networks
You must comply with the following system configuration rule, when your Experion
PKS system supports controller redundancy.
Any ControlNet segment that connects to an RCP must have at least two other nodes.
A node can be a CNI in another chasssis, KTC, PCIC, Linking Device, Series A/H
Gateway, etc.
The following sample system configurations show how you can adapt a given small
system architecture to meet minimum redundant controller system requirements.
If your system only consists of a non-redundant Server or redundant Servers, one
RCP, and one I/O chassis, you must link the Supervisory ControlNet with the I/O
ControlNet though a trunk cable to form a common ControlNet as shown in the figure
below. In this case, the default addresses are as follows.
Default address for CNI in slot 0 is 1.
Default address for CNI in slot 3 is 5.
Note that the default address for the I/O Chassis CNI in slot 0 is 3.

Network Configurations
Complying with minimum redundant controller system requirements
532 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Optional
Redundant
Server
Remote I/O Modules
Operator
Station
Ethernet
Non- Redundant
Server
B A B A
CNI
C200 CPM
CNI RM
B A B A B A B A
Redundancy Cable
Redundant
Chassis
Pair
CNI
B A
I/O
Chassis
I/O (Field Devices)
Common
ControlNet
CNI
C200 CPM
CNI RM


Network Configurations
Complying with minimum redundant controller system requirements
Release 100 Experion PKS Troubleshooting and Notifications Reference 533
1/03 Honeywell Part I
Rules for Independent Networks
You must comply with the following system configuration rule, when your Experion
PKS system supports controller redundancy.
If your system only consists of a non-redundant Server or redundant Servers, two
RCPs, and one I/O chassis per RCP, you can add another CNI in the I/O chassis to
increase the nodes in the I/O ControlNet to a given RCP as shown in the figure below.
In this case, the default MAC ID addresses for CNIs are as follows. (Note that
addresses must be incremented accordingly in the other RCP. The default addresses
are shown for example purposes only. You are free to set the addresses you want
within the constraints of the ControlNet addressing rules.)
Default address for CNI in slot 0 is 1.
Default address for CNI in slot 3 is 1.
Note that the default address for the I/O Chassis CNI in slot 0 is 3.
Note that the default address for the I/O Chassis CNI in slot 4 is 4. (Note that the
slot 4 location was chosen for example purposes only.)

Network Configurations
Complying with minimum redundant controller system requirements
534 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Optional
Redundant
Server
Remote I/O Modules
Operator
Station
Ethernet
Non- Redundant
Server
B A B A
CNI
C200 CPM
CNI RM
B A B A B A B A
Redundancy Cable
Redundant
Chassis
Pair
B A
I/O
Chassis
I/O (Field Devices)
CNI CNI
CNI
C200 CPM
CNI RM
Supervisory
ControlNet
To
Other
RCP
I/O ControlNet
B A


Network Configurations
Invalid Configuration
Release 100 Experion PKS Troubleshooting and Notifications Reference 535
1/03 Honeywell Part I
Invalid Configuration
Example
The figure below shows an invalid redundant controller system configuration for
reference only. Do not add additional CNIs to an RCP as the means to increase the
number of nodes in a ControlNet segment to a single I/O chassis. This does not meet the
requirement of having at least two nodes in any ControlNet segment that connects to an
RCP.

Optional
Redundant
Server
Remote I/O Modules
Operator
Station
Ethernet
Non- Redundant
Server
B A B A
CNI
C200 CPM
CNI RM
B A B A B A B A B A B A
Redundancy Cable
Redundant
Chassis
Pair
CNI
B A
I/O
Chassis
I/O (Field Devices)
CNI CNI
CNI
C200 CPM
CNI RM
Supervisory
ControlNet
I/O ControlNet


Network Configurations
Checklists
536 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Checklists
Guidelines for assigning MAC ID/ControlNet addresses
Be sure your MAC ID assignments conform to these general guidelines.
Valid Supervisory ControlNet address range is between 1 to 24.
Valid I/O ControlNet address range is between 1 to 20.
Assign 23 as the address for the Server. This reserves address 24 for an optional
redundant partner Server.



CAUTION
When reconfiguring the Server MAC ID from 19/20 to 23/24 for the first time,
you must first change the Supervisory ControlNet UMAX parameter to 24.
Otherwise, a loss of view occurs.

ControlNet address 1 is now optional (even though the documentation assumes that it
is always present). The CNI node with the lowest MAC ID controls the NUT timing
for the CNET segment it is in.
When you assign the lowest MAC ID to an operating CNI in an RCP, do not assign
the next higher used address above lowest MAC ID + 1 (in the same physical
network) to another CNI in that RCP. You must assign the next higher used address
above lowest MAC ID + 1 to a CNI in another Controller chassis, a CNI in a remote
I/O chassis, or the PCIC card in the Server in the same physical network. (Note that
the examples shown in Figures 2, 3, and 4 comply with this rule.)
Only assign odd numbered addresses to accommodate the logical assignment of
odd/even address pairs for RCP applications.
Assign same odd numbered address to CNI partners in an RCP.
Refer to the Experion PKS Planning Guide, Supervisory ControlNet Addressing for more
address guidelines.
Network Configurations
Checklists
Release 100 Experion PKS Troubleshooting and Notifications Reference 537
1/03 Honeywell Part I
Confirming redundant controller system requirements
Be sure your redundant controller system architecture includes:
At least four nodes. This means that there must be at least two other nodes in any
ControlNet segment that connects to an RCP.
Redundant-compliant C200 CPMs and CNIs in RCP.
CPMs, CNIs, and RMs located in matching slots in RCP.
Partner CNIs in RCP have same odd numbered address.
Partner CNIs in RCP have same ControlNet parameter settings.
RMs connected by a redundancy cable for each RCP.
No local I/O in any RCP.
RCP that includes a CNI with the lowest MAC ID of the ControlNet segment does
not also include a CNI with the next higher used address above lowest MAC ID +
1 in the same physical network.
Network Configurations
Checklists
538 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03

Release 100 Experion PKS Troubleshooting and Notifications Reference 539
1/03 Honeywell Part I
RM (Workstation) Displays
Introduction
Overview
Experion PKS offers RM Displays from both Control Builder and Station. The data
which feeds these displays is the same. The presentations are similar. References (in tis
document) to these displays apply in general to both the CB and Station versions.
The RM Displays provide not only a view to the RMs themselves, but also a means to
monitor and control Redundancy within a given redundant chassis pair (RCP).
The displays offer an indication of the general Redundancy state of each chassis of an
RCP along with several tabs/categories of detailed Redundancy related data and
command features.
This section will discuss these displays with the emphasis on their use as diagnostic tools
RM (Workstation) Displays
Redundancy Terminology
540 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Redundancy Terminology
Definitions
These definitions are listed in order of complexity, and are given in the context of
process and machine control.
Device (Chassis)
Assigned Functions
On-Line vs. Off-Line
Availability
Redundancy
Dual Redundancy
RCP (supported at the chassis level only)
Redundancy State
Primary
Secondary
Secondary Readiness
Switchover
Chassis ID
RM (Workstation) Displays
Accessing RM Displays
Release 100 Experion PKS Troubleshooting and Notifications Reference 541
1/03 Honeywell Part I
Accessing RM Displays
Control Builder RM Displays
In Control Builder, under the Monitor tab, double click on the icon of the target RM, e.g.,
RM0103.
Once the dialog box appears, select the tab (pane) of interest.
Note the data from both chassis appears on one display.
Station RM Displays
In Station, enter the target RM identifier (e.g., RM0103) on the tool bar and hit F12.
Once in the display, select the display of interest using the buttons along the upper edge
of the display.
Note that data from only one chassis appears. To see the partner data, hit the Show
Secondary or Show Primary button in the lower left corner.
RM (Workstation) Displays
Summary (CB) or Main (Stn) Panes
542 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Summary (CB) or Main (Stn) Panes
Purpose
These displays serve as a summary. In many instances, this summary is sufficient for
operator interaction.
Diagnostic Features

Feature Diagnostics
(Visibility) Is data being retrieved from the target RMs?
Redundancy State Are states opposing (one PRIMARY, the other
SECONDARY)?
Are states as expected?
Secondary Readiness Is this state as expected (DISQUALIFIED,
SYNCHRONIZING, SYNCHRONIZED)?
Module Are modules present and placed as expected?
Compatibility Do modules consider themselves compatible with their
partners?
ATTENTION: The RM always displays UNDEFINED.
% Complete If Secondary Readiness is DISQUALIFIED, is this value 0?
Otherwise, is this value approaching (or at) 100% as the
modules approach (or reach) Synchronization?
ATTENTION: The RM will always report 0.

RM (Workstation) Displays
RM Profiles (CB and Stn) Panes
Release 100 Experion PKS Troubleshooting and Notifications Reference 543
1/03 Honeywell Part I
RM Profiles (CB and Stn) Panes
Purpose
A view to check and compare identity, revisions, and states of the RMs.
Diagnostic Features

Feature Diagnostics
(Visibility) Is data being retrieved from the target RMs?
Redundancy State Are states opposing (one PRIMARY, the other
SECONDARY)?
Are states as expected?
Secondary Readiness Is this state as expected (DISQUALIFIED,
SYNCHRONIZING, SYNCHRONIZED)?
Compatibility Are module version and revisions compatible (i.e., have the
same ver./rev/ numbers?
Are Product Types 112 and Product Codes 1?
Do vendor codes match?
Are Serial Numbers different?
Are Chassis IDs opposing (one CHASSIS_A, the other
CHASSIS_B)?
ATTENTION: Mismatches may be allowed. Refer to
release documentation.
General State Are both RMs OK?
Auto-Sync Option,
Auto-Sync State,
Program Command
Recognition
Do these 3 items match?
Error Code Is this field blank ()?
If not, does the code remain after 1 minute?
RM (Workstation) Displays
RM Profiles (CB and Stn) Panes
544 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Feature Diagnostics
Fault Bits Are any Major fault bits set?
ATTENTION: Minor fault bits should not hinder normal
operations.

RM (Workstation) Displays
Configuration (CB and Stn) Panes
Release 100 Experion PKS Troubleshooting and Notifications Reference 545
1/03 Honeywell Part I
Configuration (CB and Stn) Panes
Purpose
Purpose is self-explanatory
Diagnostic Features

Feature Diagnostics
(Visibility) Is data being retrieved from the target RMs?
Redundancy State Are states opposing (one PRIMARY, the other
SECONDARY)?
Are states as expected?
Secondary Readiness Is this state as expected (DISQUALIFIED,
SYNCHRONIZING, SYNCHRONIZED)?
Chassis ID Are Serial Numbers different?
Are Chassis IDs opposing (one CHASSIS_A, the other
CHASSIS_B)?
(Command writes) Toggling the Chassis ID is a way to test the abiity to issue a
command to the RM without impacting the Redundancy
State or Secondary Readiness.
Do the Serial Number/Chassis A vs. B relationships swap
as the Chassis ID is toggled?

RM (Workstation) Displays
Synchronization (CB) and Synch (Stn) Panes
546 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Synchronization (CB) and Synch (Stn) Panes
Purpose
This display offers the user the broadest set of features related to controlling and
monitoring RCP Synchronization.
Diagnostic Features

Feature Diagnostics
(Visibility) Is data being retrieved from the target RMs?
Redundancy State Are states opposing (one PRIMARY, the other
SECONDARY)?
Are states as expected?
Secondary Readiness Is this state as expected (DISQUALIFIED,
SYNCHRONIZING, SYNCHRONIZED)?
Auto-Synchronization
State
Does this state track the Auto-Sychronization Option as it
should?
e.g.,
IF Auto-Synchroniation Option = ALWAYS,
Then Auto-Synchronization State should be ENABLED.
ELSE IF Auto-Synchroniation Option = NEVER,
Then Auto-Synchronization State should be DISABLED.
ELSE Auto-Synchroniation Option = CONDITION,
Then Auto-Synchronization State can be ENABLED or
DISABLED.
Module Are modules present and placed as expected?
Compatibility Do modules consider themselves compatible with their
partners?
ATTENTION: The RM always displays UNDEFINED.
RM (Workstation) Displays
Synchronization (CB) and Synch (Stn) Panes
Release 100 Experion PKS Troubleshooting and Notifications Reference 547
1/03 Honeywell Part I
Feature Diagnostics
% Complete If Secondary Readiness is DISQUALIFIED, is this value 0?
Otherwise, is this value approaching (or at) 100% as the
modules approach (or reach) Synchronization?
ATTENTION: The RM will always report 0.

RM (Workstation) Displays
Chassis Profiles (CB and Stn) Panes
548 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Chassis Profiles (CB and Stn) Panes
Purpose
These displays offer the user the broadest set of feature for diagnosing a problem RCP.
The objective of these displays is to pinpoint the problem slot or module. From there, the
user must refer to module specific displays and documentation to further isolate the
problem.
Diagnostic Features

Feature Diagnostics
(Visibility) Is data being retrieved from the target RMs?
Redundancy State Are states opposing (one PRIMARY, the other
SECONDARY)?
Are states as expected?
Secondary Readiness Is this state as expected (DISQUALIFIED,
SYNCHRONIZING, SYNCHRONIZED)?
Module Are modules present and placed as expected?
Does every module have a partner?
General State Are both existing modules OK?
Compatibility Do modules consider themselves compatible with their
partners?
ATTENTION: The RM always displays UNDEFINED.
% Complete If Secondary Readiness is DISQUALIFIED, is this value 0?
Otherwise, is this value approaching (or at) 100% as the
modules approach (or reach) Synchronization?
ATTENTION: The RM will always report 0.
Secondary Readiness
(module-specific)
Is this state as expected (DISQUALIFIED,
SYNCHRONIZING, SYNCHRONIZED)?

RM (Workstation) Displays
Display (CB) Pane
Release 100 Experion PKS Troubleshooting and Notifications Reference 549
1/03 Honeywell Part I
Display (CB) Pane
Purpose
This display offers no significant diagnostic usefulness.
Server Parameters (CB) Pane
Purpose
This display offers no significant diagnostic usefulness.
RM (Workstation) Displays
Server Parameters (CB) Pane
550 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03

Release 100 Experion PKS Troubleshooting and Notifications Reference 551
1/03 Honeywell Part I
Tools and Utilities
CPM Tools
Introduction
CPM Tools is a command line (pcmana.exe), diagnostic application intended for internal
Experion PKS Engineering usage. Certain situations, however, merit its usage by
customers.
This utility supports both Ethernet and ControlNet networks. With the posibility of
having multiple RSLinx drivers, the user must first select the driver needed to
communicate with the module under investigation. A list of currently configured drivers
is presented to the user that the user can select from. Once a driver is selected, the main
menu is presented to the user. Note that all of the functionality offered on the main menu
can be obtained by using the NetworkTools application.



Tools and Utilities
CPM Tools
552 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
d - Display Module State
Selecting d from the Main Menu displays the modules current state.



v - Display Module Version
Selecting v from the Main Menu displays the modules Boot and Application firmware
version.



Tools and Utilities
CPM Tools
Release 100 Experion PKS Troubleshooting and Notifications Reference 553
1/03 Honeywell Part I
b - Display Module Startup Information
Selecting b from the Main Menu displays the modules reasoning for vetoing a
Retention Startup. The first non-false reason encountered in the list indicates why
Retention Startup was not possible. More specifically, the list of reasons, from top-to-
bottom, is ordered in the sequence that the controller performs the test on the individual
items.
For example, the following illustrates the Startup Information for a controller that did not
perform Retention Startup because it was rebooted as a consequence of Application
firmware upgrade:



As another example, the following illustrates the Startup Information for a controller that
did perform Retention Startup:



Tools and Utilities
CPM Tools
554 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
f - Display SIM FTA Information
Selecting f from the Main Menu displays the SIMs FTA(s) information.



r - Recover Failed Module
Selecting r from the Main Menu attempts to recover the module from the faulted state.



Tools and Utilities
CPM Tools
Release 100 Experion PKS Troubleshooting and Notifications Reference 555
1/03 Honeywell Part I
s - Start Module
Selecting s from the Main Menu reboots the module from execution in the Boot
firmware (e.g. the Alive or Ready states) into the application firmware (e.g. No Database
or Ok states).



Tools and Utilities
CPM Tools
556 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
c - Module Crash Analysis
Selecting c from the Main Menu displays the modules crash block.



Tools and Utilities
CPM Tools
Release 100 Experion PKS Troubleshooting and Notifications Reference 557
1/03 Honeywell Part I
l - Load Module Program Image
Selecting l from the Main Menu allows the user to update the modules Boot or
Application firmware.



Tools and Utilities
CPM Tools
558 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
p - Select New Module Path
Selecting p from the Main Menu allows the user to change the communication path to
the module under investigation.



Tools and Utilities
CPM Tools
Release 100 Experion PKS Troubleshooting and Notifications Reference 559
1/03 Honeywell Part I
t - Force Shutdown Of Module
Selecting t from the Main Menu forces the module to transition to the Ready State.
This option is useful when performing module firmware update.



CAUTION
Use extreme caution when forcing shutdown and double check that the path
is properly specified because execution of this option results in an immediate
loss-of-control.



x - Exit Program
Selecting x from the Main Menu exits the CPM Tools application.
Tools and Utilities
Using DBADMIN
560 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Using DBADMIN
Introduction
The Database Administration (DBADMIN) tool is a utility for maintaining the
Engineering Repository Database (ERDB) used by the Experion PKS system to create
and maintain the control strategies. It enables users to initiate the following database
maintenance tasks:
Display and clear locks left in the ERDB after abnormal termination of the Control
Builder.
Restore the clean database in the primary ERDB.
Detach and copy the primary ERDB to specified location.
Check the consistency of the ERDB.
Re-organize data and index pages, and update statistics of the ERDB.
Expand the size of the ERDB database.
Create a backup of the current database.
Restore a backup database in the primary ERDB.
And, for redundant Servers only:
Recover a Primary or Secondary ERDB.
Synchronize ERDBs to start and stop replication.
Tools and Utilities
Using DBADMIN
Release 100 Experion PKS Troubleshooting and Notifications Reference 561
1/03 Honeywell Part I
Description
The Microsoft Management Console hosts the DBADMIN tool with a typical Windows
type interface. The interface includes dropdown menus, directory tree pane and a view
pane as shown in the following figure.

Microsoft
Management
Console
Tree
Pane
View
Pane
Status
Bar
Dropdown
Menus


Figure 1 MMC hosts DBADMIN Tool with common Windows type interface.
Tools and Utilities
Using DBADMIN
562 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Some Terms

Term Definition
ERDB
The Experion PKS Engineering Repository relational
database.
Master
Also referred to as Design Master or Primary ERDB.
The primary copy of a redundant ERDB.
ODBC (Open Database Connectivity) - A protocol for
accessing databases that is used by Experion PKS
applications.
Replica A secondary or backup copy of the ERDB that is
maintained in sync with the design master.
Replicated An ERDB that has been ] synchronized copies for
ERDB redundancy purposes.
SQL (Structured Query Language) - A database
sublanguage used in querying, updating, and
managing relational databases. Used by Experion
PKS applications to access the ERDB.
Synchronize The process of copying database information
between master and replica to bring both copies up
to date.

Installation
The DBADMIN tool (dbadmin.msc) executable resides in this Experion PKS directory
Program Files\Honeywell\Experion PKS\Engineering Tools\system\bin. It is installed
as part of the Experion PKS process software installation procedure for Engineering
Tools.
Tools and Utilities
Using DBADMIN
Release 100 Experion PKS Troubleshooting and Notifications Reference 563
1/03 Honeywell Part I
Startup
Use the following procedure to launch the DBADMIN tool.

Step Action Result
1 Click the Start button on the taskbar.
Click Programs->Experion PKS
Engineering Tools->DBADMIN.
Launches the DBADMIN utility.




Tools and Utilities
Using DBADMIN
564 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03

2 Click the DbAdmin folder icon. Calls up Login Information dialog box.




Tools and Utilities
Using DBADMIN
Release 100 Experion PKS Troubleshooting and Notifications Reference 565
1/03 Honeywell Part I
3 The default User Name is >mngr<
and it is case sensitive. Please key
in your assigned user name, if
applicable.
Click and key in your login
password in the Password field.
Please check with your system
administrator to get your assigned
password, if required. The password
is tied to the operator security for the
Station application. The default
password is >mngr1<, and it is case
sensitive.
The Server Name field lists the
Server that contains the Engineering
Repository Database (ERDB) to be
accessed. The name shown is used
for example purposes only. It is the
default name (localhost) for a non-
redundant Server.
Click the OK button.



Can now initiate DBADMIN functions.
4 Please go to the next section Menu or
tree pane functions for a list of the
functions you can initiate using this utility.


Tools and Utilities
Using DBADMIN
566 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Menu or tree pane functions
The following table summarizes the functions you can initiate through a given menu or
tree pane selection for reference. If you are familiar with working in a Windows type
environment, you should be able to intuitively interact with all the functions provided
through DBADMIN tool menu selections. Please note that the selections available in a
given menu will vary depending on the current active function.

Click This Menu
Selection . . .
To Initiate This Function . . .
Action->New Window
from Here
Opens new console root window.
Action->New Taskpad
View
Open New Taskpad View Wizard to create another
taskpad view.
Action->Export List Opens Save as dialog box to save data as text file to
specified location.



Action->Help Calls up Microsoft Management Console help.
Tools and Utilities
Using DBADMIN
Release 100 Experion PKS Troubleshooting and Notifications Reference 567
1/03 Honeywell Part I
Click This Menu
Selection . . .
To Initiate This Function . . .
View->Choose Columns Calls up Modify Columns dialog box. Use buttons
provided to move, remove, or add columns as applicable.



View->Large Icons Changes view to use Large Icons style.



View->Small Icons Changes view to use Small Icons style.



Tools and Utilities
Using DBADMIN
568 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Click This Menu
Selection . . .
To Initiate This Function . . .
View->List Changes view to use List style.



View->Detail Changes view to use Detail style.



Tools and Utilities
Using DBADMIN
Release 100 Experion PKS Troubleshooting and Notifications Reference 569
1/03 Honeywell Part I
Click This Menu
Selection . . .
To Initiate This Function . . .
View->Customize Calls up Customize View dialog box. Use checkbox
selections to view or hide the listed items.



Tools and Utilities
Using DBADMIN
570 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Click This Menu
Selection . . .
To Initiate This Function . . .
Favorites->Add Favorites Calls up Add to Favorites dialog box. Lets you add views
to favorites tab. Favorite is also added to the Favorites
dropdown menu.



Favorites->Organize
Favorites
Opens Organize Favorites dialog box. Lets you create
folders and move items into folders.



Tools and Utilities
Using DBADMIN
Release 100 Experion PKS Troubleshooting and Notifications Reference 571
1/03 Honeywell Part I
Click This Menu
Selection . . .
To Initiate This Function . . .
Tools->Change Node Opens the Login Information dialog box. Lets you
connect to the specified system node in a multi-server
environment. Just enter your password and Server
Name, and click the OK button.



Tools->Refresh Status Refresh data in View pane. (Only active for selected
directory tree functions.)
Tools->User Filter Opens the Set the User ID for Lock Filtering dialog box.
Lets you restrict lock access to the specified user for the
selected node. The value entered is saved in the
Windows Registry and becomes the default for the next
session. The user ID includes the machine name and the
login name for the user whose locks are to be cleared.
The default selection is All Users, which defeats the by
user filtering mechanism. (Only active for selected
directory tree functions.)



Tools and Utilities
Using DBADMIN
572 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Click This Menu
Selection . . .
To Initiate This Function . . .
Tools->Refresh Locks Refreshes the View pane to show the most current lock
information in the ERDB. (Only active for selected
directory tree functions.)
Tools->Clear Locks Clears all the current locks in the ERDB. The current
User Filter setting is applied, when clearing the list of
associated locks. (Only active for selected directory tree
functions.)


Click this Tree Pane
Selection . . .
To Initiate This Function . . .
DbAdmin Access Experion PKS Node folder.



Experion PKS Node Access ERDB Host Information, Active Locks, and Admin
Tasks folders.



Tools and Utilities
Using DBADMIN
Release 100 Experion PKS Troubleshooting and Notifications Reference 573
1/03 Honeywell Part I
Click this Tree Pane
Selection . . .
To Initiate This Function . . .
ERDB Host Information Display host name, type, and status in the View pane.




ATTENTION
Before clearing locks or performing database operations at a remote
server node, insure that tasks such as Control Builder and
Import/Export are shut down at that node.
Active Lock Display active locks in the View pane. (Click Tools-
>Clear Locks or right-click in open area of view pane and
select Clear Locks from pop-up menu to clear current
locks from the database.)



Admin Tasks Display the following Admin Tasks as Icons in the View
pane. There are additional tasks available for redundant
Servers.

Tools and Utilities
Using DBADMIN
574 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Click this Tree Pane
Selection . . .
To Initiate This Function . . .


Initialize Database Restores the Clean database
(ps_erdb_clean.bak) in the Primary ERDB.
Detach Database Shutdowns the database
services, detaches the Primary ERDB, copies and
attaches database to the c:\Temp directory location,
re-attaches Primary ERDB and restarts database
services.
Database Consistency Checks the consistency of
the database and rebuilds indexes using the SQL
Server.
Update Statistics Runs the DBCC REINDEX to
reorganize data and index pages followed by update
statistics.
Expand Database Expands the size of the
database
Backup Database Creates a backup copy of the
current database as a ".bak" file under the user
specified name and in the user selected directory
location on a local drive through the Back To dialog
box. A common directory location is c:\Program
Files\honeywell\Experion PKS\Engineering
Tools\ER.
Restore Database Restores the user selected
backup database (*.bak) in the primary ERDB
through the Restore From dialog box. The default
directory is c:\Program Files\honeywell\Experion
PKS\Engineering Tools\ER.

Tools and Utilities
Using DBADMIN
Release 100 Experion PKS Troubleshooting and Notifications Reference 575
1/03 Honeywell Part I
Click this Tree Pane
Selection . . .
To Initiate This Function . . .
The following tasks are only available for Redundant
Servers.



Recover Primary Database Recovers Primary
database from secondary database. If a valid
Primary (master) ERDB exists, it merely resets the
mastership ID so that the primary database is the
Design Master. If the master ERDB no longer exists,
the utility first makes the secondary database (at
SERVERA) the master temporarily. Then it
replicates this database to the primary (SERVERB).
Finally, it switches mastership back to the new copy
at SERVERB.
Recover Secondary Database Recovers
Secondary database from Primary database. It
creates a new replica from the Design Master, which
is assumed to be located at the path set by data
source `ps_erdb'. It creates the new replica at the
server node previously specified during installation
as the secondary ERDB server.
Enable Replication Starts replication of the ERDB
from the Primary to the Secondary. This enables
replication from scratch.
Disable Replication Stops the replication function
completely. This is not a temporary interruption of
the replication function.
Tools and Utilities
Using DBADMIN
576 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03

Selecting a Remote Server Node
Use the following procedure to select another Server in a multiple server environment.
This means you not have to be physically located at the Server where DBADMIN
functions need to be done. This procedure assumes that you have started the DBADMIN
utility as outlined in the previous Startup section.


ATTENTION
Be sure applications such as Control Builder and Import/Export are shut
down at the remote Server node before initiating any DBADMIN operations.


Step Action Result
1 Click the DbAdmin folder. Selects the folder and adds the Tools
menu to the toolbar.



2 Click Tools-Change Node. Calls up the Login dialog box.



Tools and Utilities
Using DBADMIN
Release 100 Experion PKS Troubleshooting and Notifications Reference 577
1/03 Honeywell Part I
Step Action Result
3 The default User Name is
>mngr<, and it is case sensitive.
Please key in your assigned
user name for the selected
Server, if applicable.
Click and key in your login
password in the Password field.
The default password is
>mngr1<, and it is case
sensitive.
Key in the name of the remote
Server or click the button
and select it from the drop-down
menu. The following illustration
is for example purposes only.


Connects to the identified Server. The
Experion PKS Node folder with the name
of the Server in parenthesis appears in the
view pane.



4 This completes the procedure. Just
repeat Steps 2 and 3 to return to the
localhost where you are located.

5 Go the next procedure Viewing
Server information to view ERDB
host information.


Tools and Utilities
Using DBADMIN
578 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Viewing Server information
Use the following procedure to view the information about the logged on Server. This
procedure assumes that you have started the DBADMIN utility as outlined in the
previous Startup section.

Step Action Result
1 Click the sign for the DbAdmin and
Experion PKS Node (servername)
folders.
Expands the directory tree.



2 Click ERDB Host Information folder. General information about the logged on
Server appears in the view pane. The
following illustration shows a typical view
for a non-redundant Server.



For Redundant Servers, information for
both the Primary and Secondary Servers
is shown.



3 Click Tools->Refresh Status. Updates Host information in the display
to reflect current data.
Tools and Utilities
Using DBADMIN
Release 100 Experion PKS Troubleshooting and Notifications Reference 579
1/03 Honeywell Part I
Step Action Result
4 This completes the procedure. Go to
the next procedure Changing lock
display filter or return to normal
operation.
Click Console->Exit to close dbadmin
window and return to normal operation.

Tools and Utilities
Using DBADMIN
580 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Changing lock display filter
Use the following procedure to change the User Filter to filter the lock display by user or
bypass the filter by enabling All Users. This procedure assumes that you have started the
DBADMIN utility as outlined in the previous Startup section.

Step Action Result
1 Click the sign for the DbAdmin and
Experion PKS Node (servername)
folders.
Expands the directory tree.



2 Click the Active Locks folder. Selects the folder and activates lock
menu selections.
3 Click Tools->User Filter. Calls up the Set the User ID for Lock
Filtering dialog box.



Tools and Utilities
Using DBADMIN
Release 100 Experion PKS Troubleshooting and Notifications Reference 581
1/03 Honeywell Part I
Step Action Result
4 Click All Users checkbox. Removes checkmark and disables the All
Users function, and activates the User ID
field.



5 Key in desired Server name and/or
user name for by user lock display
access. Click OK.
Closes the dialog box and enables lock
display filter for specified user.
6 Repeat Steps 3 and 4. Adds checkmark and enables the All
Users (default) function and disables the
filter mechanism.
7 Click OK. Closes the dialog box and refreshes the
lock display for all users.
8 This completes the procedure. Go to
the next procedure Clearing current
locks or return to normal operation.
Click Console->Exit to close dbadmin
window and return to normal operation.

Tools and Utilities
Using DBADMIN
582 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Clearing current locks
Use the following procedure to clear current locks in the database. This procedure
assumes that you have started the DBADMIN utility as outlined in the previous Startup
section and set the desired lock display filter as outlined in the prior procedure.

Step Action Result
1 Click the sign for the DbAdmin and
Experion PKS Node (servername)
folders.
Expands the directory tree.



2 Click the Active Locks folder. Selects the folder, activates lock menu
selections, and displays current locks in
the view pane


.
3 Click Tools->Refresh Locks. Updates the display to make sure the
view is current.

TIP
You can also right-click the cursor in an open area in the view pane and select
Refresh Locks or Clear Locks from the pop-up menu.
Tools and Utilities
Using DBADMIN
Release 100 Experion PKS Troubleshooting and Notifications Reference 583
1/03 Honeywell Part I
Step Action Result
4 Click Tools->Clear Locks. Clears current locks from the database
and the view pane.
5 This completes the procedure. Go to
the next procedure Making a backup
database or return to normal operation.
Click Console->Exit to close dbadmin
window and return to normal operation.

Tools and Utilities
Using DBADMIN
584 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Making a Backup database
Use the following procedure to make a backup copy of the current database. This
procedure assumes that you have started the DBADMIN utility as outlined in the
previous Startup section.


ATTENTION
It is a good idea to close the Control Builder application while running the
DBADMIN utility.


Step Action Result
1 Click the sign for the DbAdmin and
Experion PKS Node (servername)
folders.
Expands the directory tree.



2 Click the Admin Tasks folder. Calls up Admin Tasks in the view pane.
3 Are you using a redundant Server? If the answer is Yes, go to the next Step.
If the answer is No, go to Step 6.
4 Be sure you are logged onto the Server
with the Primary database.
Want to Backup the Design Master
(Primary) database.
5 Click the Disable Replication icon. Stops the replication function.
Tools and Utilities
Using DBADMIN
Release 100 Experion PKS Troubleshooting and Notifications Reference 585
1/03 Honeywell Part I
Step Action Result
6 Click the Backup Database icon. Calls up the Backup To dialog box.



7
Click button in the Save in
field and select the desired
directory location on a local drive
from the drop-down menu.
Common directory location is
c:\Program
Files\honeywell\Experion
PKS\Engineering Tools\ER.
Key in desired file name in the File
name field. For example,
>ps_erdb_1.bak<.
Defines backup to location and backup
database name. The following illustration
is for example purposes only.



8 Click the Save button. Imitates the backup function.
9 Wait for message prompt to announce
the successful completion of the
backup. Click the OK button.


Acknowledges prompt.
Tools and Utilities
Using DBADMIN
586 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Step Action Result
10 This completes the procedure. Go to
the next procedure Restoring a backup
database or return to normal operation.
Click Console->Exit to close dbadmin
window and return to normal operation.

Tools and Utilities
Using DBADMIN
Release 100 Experion PKS Troubleshooting and Notifications Reference 587
1/03 Honeywell Part I
Restoring a backup database
Use the following procedure to restore a backup database. This procedure assumes that
you have started the DBADMIN utility as outlined in the previous Startup section and
you have created a backup database as outlined in the prior procedure.


ATTENTION
Disconnect all clients before initiating a database restore function.


Step Action Result
1 Click the sign for the DbAdmin and
Experion PKS Node (servername)
folders.
Expands the directory tree.



2 Click the Admin Tasks folder. Calls up Admin Tasks in the view pane.
3 Are you using a redundant Server? If the answer is Yes, go to the next Step.
If the answer is No, go to Step 6.
4 Be sure you are logged onto the Server
with Primary database.
Want to restore the backup as the Design
Master (Primary) database.
5 Click the Disable Replication icon. Stops the replication function.
6 Click the Restore Database icon. Prompt asks if replication is disabled and
if you want to continue.



Tools and Utilities
Using DBADMIN
588 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Step Action Result
7 Click the OK button. Calls up the Restore From dialog box.



8
Click button in the Look in field
and select the desired directory
location from the drop-down menu.
Common directory location is
c:\Program
Files\honeywell\Experion
PKS\Engineering Tools\ER.
Select the desired backup
database (*.bak) in the list box, so
it appears in the File name field.
For example, >ps_erdb_1.bak<.
Selects the backup database to be
restored.



9 Wait for message prompt to announce
the successful completion of the
restore. Click the OK button.


Acknowledges prompt.
10 This completes the procedure. Go to
the next procedure Restoring a clean
database or return to normal operation.
Click Console->Exit to close dbadmin
window and return to normal operation.

Tools and Utilities
Using DBADMIN
Release 100 Experion PKS Troubleshooting and Notifications Reference 589
1/03 Honeywell Part I
Restoring clean database
Use the following procedure to restore the clean database that is provided with the
Experion PKS Engineering Tools software. This procedure assumes that you have started
the DBADMIN utility as outlined in the previous Startup section.


ATTENTION
Disconnect all clients before initiating a database restore function.


Step Action Result
1 Click the sign for the DbAdmin and
Experion PKS Node (servername)
folders.
Expands the directory tree.



2 Click the Admin Tasks folder. Calls up Admin Tasks in the view pane.
3 Are you using a redundant Server? If the answer is Yes, go to the next Step.
If the answer is No, go to Step 6.
4 Be sure you are logged onto the Server
with the Primary database.
Want to restore the clean database as
the Design Master (Primary) database.
5 Click the Disable Replication icon. Stops the replication function.
6 Click the Initialize Database icon. Prompt asks if replication is disabled and
if you want to continue.



7 Click the Yes button. Initiates the initialization function.
Tools and Utilities
Using DBADMIN
590 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Step Action Result
8 Wait for message prompt to announce
the successful completion of the
initialization. Click the OK button.


Acknowledges prompt.
9 Did you initialize the Primary database
on a redundant Server?
If the answer is Yes, go to the next Step.
If the answer is No, go to Step 12.
10 Click the Recover Secondary Database
icon.
Initializes the secondary database.
11 Wait for message prompt to announce
the successful completion of the
initialization. Click the OK button.
Acknowledges prompt.
12 This completes the procedure. Go to
the next procedure Detaching database
or return to normal operation.
Click Console->Exit to close dbadmin
window and return to normal operation.

Tools and Utilities
Using DBADMIN
Release 100 Experion PKS Troubleshooting and Notifications Reference 591
1/03 Honeywell Part I
Detaching database
Use the following procedure to detach and copy the database file to a specified location.
This procedure assumes that you have started the DBADMIN utility as outlined in the
previous Startup section.


ATTENTION
Disconnect all clients before detaching a database.


Step Action Result
1 Click the sign for the DbAdmin and
Experion PKS Node (servername)
folders.
Expands the directory tree.



2 Click the Admin Tasks folder. Calls up Admin Tasks in the view pane.
3 Click the Detach Database icon. Prompt asks if you want to continue.



4 Click the Yes button. Initiates the function that stops database
services, detaches the database, copies
files ps_erdb.mdf and ps_erdb_log.idf to
the c:\Temp directory, re-attaches the
database, and starts database services.
Tools and Utilities
Using DBADMIN
592 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Step Action Result
5 Wait for prompt to announce successful
completion of the operation. Click the
OK button.


Acknowledges prompt.
6 This completes the procedure. Go to
the next procedure Expanding
database or return to normal operation.
Click Console->Exit to close dbadmin
window and return to normal operation.

Tools and Utilities
Using DBADMIN
Release 100 Experion PKS Troubleshooting and Notifications Reference 593
1/03 Honeywell Part I
Expanding database
Use the following procedure to expand the database if more than 75% of the allocated
hard-disk space is in use. This procedure assumes that you have started the DBADMIN
utility as outlined in the previous Startup section.

Step Action Result
1 Click the sign for the DbAdmin and
Experion PKS Node (servername)
folders.
Expands the directory tree.



2 Click the Admin Tasks folder. Calls up Admin Tasks in the view pane.
3 Click the Expand Database icon. Prompt asks you to confirm the action.



4 Click the Yes button. Initiates the function.
5 Wait for prompt to announce the
successful completion of the expansion.
Click the OK button.
Acknowledges prompt.
6 This completes the procedure. Go to
the next procedure Recovering Primary
database or return to normal operation.
Click Console->Exit to close dbadmin
window and return to normal operation.

Tools and Utilities
Using DBADMIN
594 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Recovering Primary database
Use the following procedure to recover a Primary database in a redundant Server
application only. This procedure assumes that you have started the DBADMIN utility as
outlined in the previous Startup section on the redundant Server running the Primary
database.


ATTENTION
Disconnect all clients before initiating a database recovery function.


Step Action Result
1 Click the Start button in the taskbar.
Click Settings->Control Panel
Opens Control Panel window.
2 Double-click Administrative Tools folder
.
Opens Administrative Tools window
3
Double-click Services icon .
Opens Services window.
4 Scroll the list box to find the Experion
PKS System Repository service.
Double-click this service.
Opens the Experion PKS System
Repository Properties dialog box.



5 Click the Stop button. Initiates service shutdown.
Tools and Utilities
Using DBADMIN
Release 100 Experion PKS Troubleshooting and Notifications Reference 595
1/03 Honeywell Part I
Step Action Result
6 Wait for service status to change to
stopped. Click the OK button.
Closes the dialog box.
7 Repeat Steps 4, 5, and 6 to stop these
other Experion PKS services:
Experion PKS Control Data
Access Server
Experion PKS ER Server
Stops Experion PKS database services.
8 Close the Services, Administrative
Tools, and Control Panel windows.
Completes tasks.
9 In dbadmin window, click the sign for
the DbAdmin and Experion PKS Node
(servername) folders.
Expands the directory tree.



10 Click the Admin Tasks folder. Calls up Admin Tasks in the view pane.
11 Click the Recover Primary Database
icon.
Prompt asks if you want to continue.
12 Click the Yes button. Initiates function to backup the
Secondary database and use it to restore
the Primary database.
13 Wait for prompt to announce the
successful completion of the action.
Click the OK button.
Acknowledges prompt.
14 Repeat Steps 1 to 8, modifying Step 5
to click the Start button.
Starts Experion PKS database services.
Tools and Utilities
Using DBADMIN
596 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Step Action Result
15 This completes the procedure. Go to
the next procedure Recovering
Secondary database or return to normal
operation.
Click Console->Exit to close dbadmin
window and return to normal operation.

Tools and Utilities
Using DBADMIN
Release 100 Experion PKS Troubleshooting and Notifications Reference 597
1/03 Honeywell Part I
Recovering Secondary database
Use the following procedure to recover a Primary database in a redundant Server
application only. This procedure assumes that you have started the DBADMIN utility as
outlined in the previous Startup section on the redundant Server running the Primary
database.


ATTENTION
Disconnect all clients before initiating a database recovery function.


Step Action Result
1 Click the Start button in the taskbar.
Click Settings->Control Panel
Opens Control Panel window.
2 Double-click Administrative Tools folder
.
Opens Administrative Tools window
3
Double-click Services icon .
Opens Services window.
4 Scroll the list box to find the Experion
PKS System Repository service.
Double-click this service.
Opens the Experion PKS System
Repository Properties dialog box.



5 Click the Stop button. Initiates service shutdown.
Tools and Utilities
Using DBADMIN
598 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Step Action Result
6 Wait for service status to change to
stopped. Click the OK button.
Closes the dialog box.
7 Repeat Steps 4, 5, and 6 to stop these
other Experion PKS services:
Experion PKS Control Data
Access Server
Experion PKS ER Server
Stops Experion PKS database services.
8 Close the Services, Administrative
Tools, and Control Panel windows.
Completes tasks.
9 In dbadmin window, click the sign for
the DbAdmin and Experion PKS Node
(servername) folders.
Expands the directory tree.



10 Click the Admin Tasks folder. Calls up Admin Tasks in the view pane.
11 Click the Recover Secondary Database
icon.
Prompt asks if you want to continue.
12 Click the Yes button. Initiates function to backup the Primary
database and use it to restore the
Secondary database.
13 Wait for prompt to announce the
successful completion of the action.
Click the OK button.
Acknowledges prompt.
14 Repeat Steps 1 to 8, modifying Step 5
to click the Start button.
Starts Experion PKS database services.
Tools and Utilities
Using DBADMIN
Release 100 Experion PKS Troubleshooting and Notifications Reference 599
1/03 Honeywell Part I
Step Action Result
15 This completes the procedure. Go to
the next procedure Enabling replication
or return to normal operation.
Click Console->Exit to close dbadmin
window and return to normal operation.

Tools and Utilities
Using DBADMIN
600 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Enabling replication
Use the following procedure to initiate the replication function in a redundant Server
application only. This procedure assumes that you have started the DBADMIN utility as
outlined in the previous Startup section on the redundant Server running the Primary
database.

Step Action Result
1 Click the sign for the DbAdmin and
Experion PKS Node (servername)
folders.
Expands the directory tree.



2 Click the Admin Tasks folder. Calls up Admin Tasks in the view pane.
3 Click the Recover Secondary Database
icon.
Prompt asks if you want to continue.
4 Click the Yes button. Initiates function to backup the Primary
database and use it to restore the
Secondary database. This action
synchronizes the databases in
preparation for replication.
5 Wait for prompt to announce the
successful completion of the action.
Click the OK button.
Acknowledges prompt.
6 Click the Enable Replication icon. Initiates replication of the database from
the Primary to the Secondary. It sets up
and starts the SQL server jobs to do the
replication.
7 Wait for prompt to announce the
successful completion of this operation.
Click the OK button.
Acknowledges prompt.
Tools and Utilities
Using DBADMIN
Release 100 Experion PKS Troubleshooting and Notifications Reference 601
1/03 Honeywell Part I
Step Action Result
8 This completes the procedure. Go to
the next procedure Disabling replication
or return to normal operation.
Click Console->Exit to close dbadmin
window and return to normal operation.

Tools and Utilities
Using DBADMIN
602 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Disabling replication
Use the following procedure to stop the replication function and delete the configured
replication setup. This procedure assumes that you have started the DBADMIN utility as
outlined in the previous Startup section on the redundant Server running the Primary
database.

Step Action Result
1 Click the sign for the DbAdmin and
Experion PKS Node (servername)
folders.
Expands the directory tree.



2 Click the Admin Tasks folder. Calls up Admin Tasks in the view pane.
3 Click the Disable Replication icon. Prompt asks if you want to continue.
4 Click the Yes button. Stops the replication jobs and deletes the
configured replication setup.
5 Wait for prompt to announce the
successful completion of the action.
Click the OK button.
Acknowledges prompt.
6 This completes the procedure. Go to
another procedure or return to normal
operation.
Click Console->Exit to close dbadmin
window and return to normal operation.

Tools and Utilities
I/O Maintenance Tool
Release 100 Experion PKS Troubleshooting and Notifications Reference 603
1/03 Honeywell Part I
I/O Maintenance Tool
Overview
The I/O Maintenance Tool allows the user to {1} navigate to a single I/O Module and
display Module Information and Status, {2} perform calibration for various Analog
Modules, and {3} reset Short/Overload Faults on Diagnostic Output Modules. These
operations are separated into 3 tabs on the main I/O Maintenance Tool display:
Navigator, Calibration, and Utilities respectively. The Calibration and Utilities tabs are
not accessible until the user specifies the appropriate target I/O Module type on the
Navigator tab.
Navigator Tab
The Navigator Tab is used to specify the location of the I/O Module that requires
maintenance. The target I/O module can be either a Rack or Rail mount module, and the
destination Rack/Rail can reside on either a Local or Remote network.

Select Driver Used to select an appropriate driver to communicate with the
target I/O Module. The IO Maintenance Tool supports the
maintenance of IO Modules via both Ethernet and
ControlNet networks. With the possibility of having multiple
RSLinx drivers, the user must explicitly select the driver
needed to communicate with the target I/O module. At
startup, the IO Maintenance Tool populates this combo box
with a list of configured RSLinx drivers. Please note that
RSLinx drivers must be configured before using the IO
Maintenance Tool.
Enable Remote If the target I/O Module resides on a remote network (i.e. not
directly connected to the PC), check this Box to expose the
Remote Network fields.
Rail I/O If selecting a Rail I/O Module, check this box to expose the
Gateway and Device Information fields. Selecting this box
also changes the final SLOT' field to 'MODULE #', because
Rail I/O modules are referred to by their number position on
the Rail vs. Rack I/O modules that are referenced by the slot
location in the Rack.
Local Network If the Enable Remote check box is selected, the Local
Network information specifies the communication hub used
to reach the remote network. Otherwise, if the Enable
Remote check box is not selected, the Local Network
information specifies the target Rail/Rack I/O module.
Tools and Utilities
I/O Maintenance Tool
604 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Local Network information is comprised of up to 2 fields:
MAC ID and SLOT. The MAC ID field specifies the
ControlNet address directly connected to this PC. Note that
this selection is not required and hence not available when
an Ethernet driver has been selected.
The SLOT field specifies the Rack position of either the I/O
Module (i.e. no remote network) or the communication
interface module (i.e. I/O Module on remote network). Note
that if the I/O Module resides on the local network and it is a
Rail I/O Module (i.e. Enable Remote is not selected and
Rail I/O is selected), the SLOT field is renamed to
MODULE #.
Remote Network The Remote Network entry fields are only exposed when the
Enable Remote check box is selected. Remote Network
information is comprised of 2 fields: {1} MAC ID and {2}
either SLOT in the case of Rack I/O or 'MODULE #' in the
case of Rail I/O. The MAC ID field specifies the ControlNet
address of the remote Rack/Rail. The SLOT / MODULE #
field specifies the Rack / Rail position of the I/O Module.
Note that the SLOT field is only renamed to MODULE # if
the I/O Module is a Rail I/O Module (i.e. Rail I/O is
selected).

Tools and Utilities
I/O Maintenance Tool
Release 100 Experion PKS Troubleshooting and Notifications Reference 605
1/03 Honeywell Part I
The following illustration depicts the Navigator Tab configuration for a Rack I/O Module
residing on a local ControlNet network.



Tools and Utilities
I/O Maintenance Tool
606 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
The following illustration depicts the Navigator Tab configuration for a Rack I/O Module
residing on a local Ethernet network.



Tools and Utilities
I/O Maintenance Tool
Release 100 Experion PKS Troubleshooting and Notifications Reference 607
1/03 Honeywell Part I
The following illustration depicts the Navigator Tab configuration for a Rail I/O Module
residing on a local ControlNet network. Note that although the equivalent selections for
a local Ethernet network are allowed by the I/O Maintenance Tool, this is currently a
non-supported topology.



Tools and Utilities
I/O Maintenance Tool
608 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
The following illustration depicts the Navigator Tab configuration for a Rack I/O Module
residing on a remote ControlNet network with a Supervisory ControlNet network.



Tools and Utilities
I/O Maintenance Tool
Release 100 Experion PKS Troubleshooting and Notifications Reference 609
1/03 Honeywell Part I
The following illustration depicts the Navigator Tab configuration for a Rail I/O Module
residing on a remote ControlNet network with a Supervisory Ethernet network.



Selection of the 'GET MODULE DATA' Button causes the I/O Maintenance Tool to
acquire information & status for the targeted I/O Module. For Rack I/O, the requested
I/O Module information is displayed in the Device Information field. For Rail I/O, the
requested I/O Module information is displayed in the ControlNet Gateway Information
and Device Information fields.
Tools and Utilities
I/O Maintenance Tool
610 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
For Rack I/O:

Device Information
Name The Catalog name of the I/O Module.
Type The type of I/O Module.
FW Version The version number of the I/O Module
firmware currently loaded.
Serial Num The I/O Module's serial number.
LEDs The I/O Module Operation and Fault Status is
displayed by the round "LED" symbols.

For Rail I/O:

ControlNet Gateway Information:
Name The Catalog name of the ControlNet Gateway.
Type The type of ControlNet Gateway.
FW Version The version number of the ControlNet
Gateway firmware currently loaded.
Serial Num The ControlNet Gateway's serial number.
LEDs The ControlNet Gateway Operation and Fault
Status is displayed by the round "LED"
symbols.
Device Information:
Name The Catalog name of the I/O Module.
Type The type of I/O Module.

If this data reflects the desired I/O Module, proceed to the Calibration or Utilities Tabs.
NOTES:
1. Selection of an Analog Module enables the Calibration Tab.
2. Selection of a Diagnostic Output Module enables the Utilities Tab.
3. If 'GET MODULE DATA' fails, some of the fields display '???' and a STATUS
message is displayed at the bottom of the Navigator Tab.
Tools and Utilities
I/O Maintenance Tool
Release 100 Experion PKS Troubleshooting and Notifications Reference 611
1/03 Honeywell Part I
4. Possible Messages:
"Get Module Data Succeeded"
"Get Module Data Failed"
"Bad MAC ID for the Remote CNI"
"Bad SLOT # for the Local Rack CNI"
"Selected Analog Module is READY to Calibrate"
"Selected Analog Module is RUNNING. You MUST INACTIVATE and DELETE
this Module from the Control Builder Monitoring TAB before Calibrating."
"The ControlNet Gateway is Connected to one or more Rail I/O Devices. You
MUST INACTIVATE and DELETE any such Device(s) from the Control Builder
Monitoring TAB before Calibrating."
Calibration Tab
The Calibration Tab is enabled once the Navigator Tab specifies an Analog Module. The
following are procedures for performing a Calibration sequence for various Analog
Modules. Substitute calibration values from the procedure-subordinate tables based on
the particular I/O Module type.
Tools and Utilities
I/O Maintenance Tool
612 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Analog Input (Rack I/O) Module Calibration



ATTENTION
This calibration procedure only applies to the following Rack I/O Modules:
TC-IAH061, TC-IAH161, TC-IXL061, and TC-IXR061.

1. Select the Channel or Channels to be calibrated with the "Select" check boxes next to
each Channel. For TC-IAH161, the "Select Channel Group Box" is also used to
navigate between the four (4) four-channel groups.
2. Select the 'Optional Cal Range' if the calibration range is 1~20mA for TC-IAH061, or
-14~30mV for TC-IXL061. Do not check for the other Analog Input module types.
3. Press 'Start Calibration Mode' Button. Calibration is prohibited if the I/O Module is in
RUN Mode. Please inactivate and unload (delete) the I/O Module from the Controller
before proceeding with Calibration.
4. Input exactly the Low Cal Value to the screw terminals of the channel(s).
5. Press 'Perform Low Cal' Button. The input is then sampled and the 'L' LED transitions
to Yellow. If the Input is out of range the LED transitions to Red and the calibration is
unsuccessful. Verify that the input is exactly the Low Cal Value and press 'Perform
Low Cal' again.
6. Once the 'L' LED is Yellow, input exactly the High Cal Value to the screw terminals
of the channel(s).
7. Press 'Perform High Cal' Button. The input is then sampled and the 'H' LED should
transition to Yellow. If the Input is out of range the LED transitions to Red and the
calibration is unsuccessful. Verify that the input is exactly the High Cal Value and
press 'Perform High Cal' again.
8. Now that the Low signal and High signal are sampled, the calibration should finish
and the 'H' and 'L' LEDs transition to Green. The Calibration Status LED on the left
also transitions to Green. If either the low or high signal is not sampled correctly, the
calibration is unsuccessful. In that case you can stop the calibration by pressing the
'Stop Calibration Mode' button. Note that the Calibration Status LED transitions to
Red.
9. When the calibration has succeeded, the calibration mode stops automatically. You do
not need to press 'Stop Calibration Mode' button. If you need to continue the
calibration for other channels, repeat from step 1) until all channels are calibrated
correctly.
Tools and Utilities
I/O Maintenance Tool
Release 100 Experion PKS Troubleshooting and Notifications Reference 613
1/03 Honeywell Part I
Analog Input (Rack I/O) Calibration Value Table

Module Low Value Low Tolerance High Value High Tolerance
TC-IAH061 0V +/-0.68mV +10V +/-0.6V
(Optional range) 1mA 20mA

TC-IAH161 0V +/-0.11V +10.25 -0.07~0.18V

TC-IXL061 -12mV -0.89~0.84mV +78mV -3.7~4.0mV
(Optional range) -14.22mV +30.78mV

TC-IXR061 1 Ohm +/-0.8 Ohm 487 Ohm +/-17 Ohm

Notes:
TC-IXL061 and TC-IAH061 have two types of Calibration values depending on the
configuration.
The type is selected by the "Optional Cal Range" check box.
The tolerance for -14~30mV type is half of the -12~78 type.
The tolerance means allowable difference counts from the Nominal Counts before the
value is rejected with an error.
The counts are converted to physical value based on the High Cal Nominal counts.
The accuracy of the devices are typically 0.005%.
Tools and Utilities
I/O Maintenance Tool
614 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Analog Output (Rack I/O) Module Calibration



ATTENTION
This calibration procedure only applies to the following Rack I/O Modules:
TC-OAV061, TC-OAH061, and TC-OAV081.

1. Select the Channel or Channels to be calibrated with the "select" check boxes next to
each Channel. For TC-OAV061, the "Select Channel Group Box" is also used to
navigate between the two (2) four-channel groups.
2. For TC-OAV081, the "optional cal range" selection enables the channel(s) selected to
output mA values to the current output pins, for Current Mode calibration.
3. Press 'Start Calibration Mode' Button
4. Press 'Perform Low Cal' Button. The AO module outputs the Low Value. The 'L'
LED transitions to Yellow.
5. Measure the value of the screw, and enter the value into the left 'Measurements' text
box.
6. Press 'Perform High Cal' Button. The AO module outputs the High Value, and the 'H'
LED transitions to Yellow.
7. Measure the value of the screw, and enter the value into the right 'Measurements' text
box. The value should be near the High Value.
8. Press 'Finish Calibration' Button. The calibration should finish. If the entered values
are out of range, the calibration is unsuccessful. In that case you can stop the
calibration by pressing the 'Stop Calibration Mode' button. Note that the Calibration
Status LED transitions to Red.
9. When the calibration has succeeded, the calibration mode stops automatically. You do
not need to press 'Stop Calibration Mode' button. If you need to continue the
calibration for other channels, repeat from step 1).
Tools and Utilities
I/O Maintenance Tool
Release 100 Experion PKS Troubleshooting and Notifications Reference 615
1/03 Honeywell Part I
Analog Output (Rack I/O) Calibration Value Table

Module Low Value Low Tolerance High Value High Tolerance
TC-OAV061 0.0 V +/-18 mV 10.0 V +/-251 mV

TC-OAH061 4.0 mA +/-0.15 mA 20.0 mA +/-0.67 mA

TC-OAV081 0.0 V +/-18 mV 10.0 V +/-251 mV
(Optional
current range)
4.0 mA +/-0.15 mA 20.0 mA +/-0.67 mA

Notes:
When the calibration has finished, the 'Last Cal Date' in the module is updated to
Today's date.
Current Input (Rail I/O) Module Calibration



ATTENTION
This procedure only applies to TC-PIA082. The TC-FIAH81 does not allow
calibration.

1. Select a Channel to be calibrated with the "Select" check boxes next to the Channel
Number. You can also select 'Sel All' to calibrate all channels at the same time.
2. Press 'Start Calibration Mode' Button. Calibration is prohibited if the Module is in
RUN Mode. Please inactivate and unload (delete) the Module from the Controller
before proceeding with Calibration. If the calibration can proceed, the 'Cal Active'
LED on the top left corner transitions to Green.
3. Create an open circuit between the 'sig' (+) terminal and '-' (-) terminal(s) of selected
channel(s).
Tools and Utilities
I/O Maintenance Tool
616 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
4. Press 'Offset Cal' Button. The Input is then sampled and the 'Offset' LED(s) should
transition to Green. If the Input is out of range, the LED(s) transition to Red. In this
case the calibration did not succeed. Verify that there is an open circuit between 'sig'
(+) terminal and '-' (-) terminal(s) of selected channel(s) and press 'Offset Cal' again.
5. Once the 'Offset' LED(s) transition to Green, input exactly the Gain Calibration Value
of 20.000 mA to the screw terminals of the channel(s).
6. Press 'Gain Cal' Button. The Input is then sampled and the 'Gain' LED(s) should
transition to Green. If the Input is out of range the LED(s) transition to Red. In this
case the calibration did not succeed. Verify that the current source connection is
correct and that the input is exactly the Gain Calibration Value and press 'Gain Cal'
again.
7. Once the Offset and Gain signals are sampled, the calibration should finish and the
'Offset' and 'Gain' LEDs should be Green.
8. If you need to continue the calibration for other channels, repeat from step 1) until all
channels are calibrated correctly.
9. When the calibration has succeeded, press 'Stop Calibration Mode' button. All LEDs
transition to White and the Navigator Tab is enabled.
Notes:
The accuracy of current source should be 0.01% or better.
Current Input Channels should not be connected in parallel to one source. Individual
current sources must be used or channels must be calibrated on at a time.

Tools and Utilities
I/O Maintenance Tool
Release 100 Experion PKS Troubleshooting and Notifications Reference 617
1/03 Honeywell Part I
Current Output (Rail I/O) Module Calibration



ATTENTION
This procedure only applies to TC-POA082. The TC-FOA041 does not allow
calibration.

1. Select a Channel to be calibrated with the "Select" check box next to the Channel
Number. You can also select 'Sel All' to calibrate all channels at the same time.
2. Press 'Start Calibration Mode' Button. Calibration is prohibited if the Module is in
RUN Mode. Please inactivate and unload (delete) the Module from the Controller
before proceeding with Calibration. If the calibration can proceed, the 'Cal Active'
LED on the top left corner transitions to Green.
3. Press 'Min Scale Cal' Button. The AO module outputs the Min Scale Cal Ref value of
1.000 mA. The 'Min' LED transitions to Yellow.
4. Connect the '+' lead(s) of the current meter(s) to the '+' terminal(s) of selected
Channel(s). Connect the '-' lead(s) of the current meter(s) to 250 Ohm resistor(s).
Connect the other end(s) of the 250 Ohm resistor(s) to the '-' terminal(s) of selected
Channel(s).
5. Measure the value(s) at the screw(s), and enter the value(s) into the left
'Measurements' text box to a precision of 0.001 mA.
6. Press 'Finish Calibration' Button. The Minimum Scale calibration should finish and
the 'Min' Calibration Status LED(s) transition to Green. If the entered value(s) are out
of range, the calibration is unsuccessful and the 'Min' Calibration Status LED(s)
transition to Red. Verify that the current meter(s) are properly connected and press
'Min Scale Cal' Button again.
7. Press 'Max Scale Cal' Button. The AO module outputs the Max Scale Cal Ref value of
21.000 mA. The 'Max' LED transitions to Yellow.
8. Connect the '+' lead(s) of the current meter(s) to the '+' terminal(s) of selected
Channel(s). Connect the '-' lead(s) of the current meter(s) to 250 Ohm resistor(s).
Connect the other end(s) of the 250 Ohm resistor(s) to the '-' terminal(s) of selected
Channel(s).
9. Measure the value(s) of the screw(s), and enter the value(s) into the left
'Measurements' text box to a precision of 0.001 mA.
Tools and Utilities
I/O Maintenance Tool
618 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
10. Press 'Finish Calibration' Button. The Maximum Scale calibration should finish
and the 'Max' Calibration Status LED(s) transition to Green. If the entered value(s) are
out of range, the calibration is unsuccessful and the 'Max' Calibration Status LED(s)
transition to Red. Verify that the current meter(s) are properly connected and press
'MaxScale Cal' Button again.
11. If you need to continue the calibration for other channels, repeat from step 1)
until all channels are calibrated correctly.
12. When the calibration has succeeded, press 'Stop Calibration Mode' button.
Notes:
The accuracy of current source should be 0.01% or better.
Tools and Utilities
I/O Maintenance Tool
Release 100 Experion PKS Troubleshooting and Notifications Reference 619
1/03 Honeywell Part I
Temperature Input (Rail I/O) Module Calibration #1



ATTENTION
There are two Temperature Input (Rail I/O) Module calibration procedures.
This procedure only applies to TC-PIL081. There is a separate procedure
(following this one) for TC-FIL081.

1. Select a Channel to be calibrated with the "Select" check box next to the Channel
Number. You can also select 'Sel All' to calibrate all channels at the same time.
2. Press 'Start Calibration Mode' Button. Calibration is prohibited if the Module is in
RUN Mode. Please inactivate and unload (delete) the Module from the Controller
before proceeding with Calibration. If the calibration can proceed, the 'Cal Active'
LED on the top left corner transitions to Green.
3. Press 'Offset Cal' Button. This enables Offset calibration for ALL Programmable Gain
Amplifier (PGA) Selections.
4. Connect the voltage source to the millivolt-input terminals of the selected Channel(s).
5. To the screw terminals of the selected channel(s), input exactly the Offset Calibration
Value for a particular PGA Selection for which a button is currently Enabled. (Note:
Refer to the table below for Offset Calibration Values corresponding to each PGA
Selection). Press the Enabled PGA Selection Button. The Input is then sampled and
the 'Offset' LED(s) should transition to Green. If the Input is out of range, the LED(s)
transition to Red. In this case the calibration did not succeed. Verify that the voltage
source connection is correct and that the input is exactly the specified Offset
Calibration Value and press Enabled PGA Selection Button again. Repeat this step for
all PGA Selections.
6. Press 'Gain Cal' Button. This enables Gain calibration for ALL PGA Selections.
7. To the screw terminals of the selected channel(s), input exactly the Gain Calibration
Value for a particular PGA Selection for which a button is currently Enabled. (Note:
Refer to the table below for Gain Calibration Values corresponding to each PGA
Selection). Press the Enabled PGA Selection Button. The Input is then sampled and
the 'Gain' LED(s) should transition to Green. If the Input is out of range, the LED(s)
transition to Red. In this case the calibration did not succeed. Verify that the voltage
source connection is correct and that the input is exactly the specified Gain Calibration
Value and press Enabled PGA Selection Button again. Repeat this step for all PGA
Selections.
Tools and Utilities
I/O Maintenance Tool
620 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
8. Connect 383 Ohm resistor(s) to the selected channel(s) in a 4 wire configuration
(resistor is connected to '+' and '' terminals, and sense wire is connected to 'L' and 'H'
terminals).
9. Press '383 Ohm Current Cal' Button. The Input is then sampled and the '383 ' LED(s)
should transition to Green. If the resistor value is wrong or the connection is not
correct, the LED(s) transition to Red. In this case the calibration did not succeed.
Verify that the resistor value is exactly the specified value and is properly connected in
a 4-wire configuration and press '383 Ohm Current Cal' Button again.
10. Connect 100 Ohm resistor(s) to the selected channel(s) in a 4 wire
configuration.
11. Press '100 Ohm Current Cal' Button. The Input is then sampled and the '100 '
LED(s) should transition to Green. If the resistor value is wrong or the connection is
not correct, the LED(s) transition to Red. In this case the calibration did not succeed.
Verify that the resistor value is exactly the specified value and is properly connected in
a 4-wire configuration and press '100 Ohm Current Cal' Button again.
12. Select Thermistor(s) for Cold Junction Compensation calibration. Replace the
selected cold junction compensation thermistor(s) by a 10K Ohm resistor(s).
13. Press 'Cold Junction Compensation Calibration' Button. The LED(s) next to the
selected thermistor(s) should transition to Green. If the resistor(s) value is wrong, the
LED(s) transition to Red. In this case the calibration did not succeed. Verify that the
resistor value is exactly the specified value and it is properly connected in a 4-wire
configuration and press 'Cold Junction Compensation Calibration' Button again.
14. If you need to continue the calibration for other channels or thermistors, repeat
from step 1) until all channels and thermistors are calibrated correctly.
15. When the calibration has succeeded, press 'Stop Calibration Mode' button. All
LEDs transition to White and the Navigator Tab becomes enabled.
Tools and Utilities
I/O Maintenance Tool
Release 100 Experion PKS Troubleshooting and Notifications Reference 621
1/03 Honeywell Part I
Temperature Input (Rail I/O) Calibration #1 Value Tables

Programmable
Gain Amplifier
Selection
Offset Value Offset
Tolerance
Gain Value Gain Tolerance
Gain = 1 0.000 mV +/-13.2 mV 330.000 mV +/-13.2 mV
Gain = 2 -30.000 mV +/-6.6 mV 100.000 mV +/-6.6 mV
Gain = 4 -10.000 mV +/-3.3 mV 77.000 mV +/-3.3 mV
Gain = 8 -5.000 mV +/-1.1 mV 48.000 mV +/-1.1 mV
Gain = 16 -1.000 mV +/-1.6 mV 22.000 mV +/-1.6 mV


Current Nominal Resistance Accepted Values
100 Ohms 90 Ohms - 175 Ohms
383 Ohms 373 Ohms - 458 ohms

CJC Nominal Resistance Accepted Values
10k Ohms 9.2k Ohms - 11.9k Ohms

Notes:
The accuracy of voltage source should be 0.01% or better.
Offset and Gain calibration should be done before other parameters are calibrated.
Cold Junction calibration should be done after the Offset and Gain calibration of
Channel 0.
100 Ohm Current Calibration should be done after 383 Ohm Current Calibration.
Loop Resistance Compensation is not part of calibration, it is a tuning procedure that
calculates automatically RTD loop resistance offset and is used if during configuration
of the module, the RTD loop resistance offset was selected to be 'Determined'. To
compensate for loop resistance, either {1} determine cable resistance by measurement
and place a resistor of the same value across terminals or {2} short the cable as close
to RTD as possible.
Tools and Utilities
I/O Maintenance Tool
622 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Temperature Input (Rail I/O) Module Calibration #2



ATTENTION
There are two Temperature Input (Rail I/O) Module calibration procedures.
This procedure only applies to TC-FIL081. The previous procedure applies to
TC-PIL081.

1. Select a Channel to be calibrated with the "Select" check box next to the Channel
Number. You can also select 'Sel All' to calibrate all channels at the same time.
2. Press 'Start Calibration Mode' Button. Calibration is prohibited if the Module is in
RUN Mode. Please inactivate and unload (delete) the Module from the Controller
before proceeding with Calibration. If the calibration can proceed, the 'Cal Active'
LED on the top left corner transitions to Green.
3. Connect 0.000mV across each input channel. Connect all high signal terminals
together and attach to the positive lead from the precision voltage source. Connect all
low signal terminals together and attach to the negative lead. The Offset Calibration
Value is 0.000mV.
4. Press 'Offset Cal' Button. This enables Offset calibration for the selected channel(s).
5. The Input is then sampled and the 'Offset' LED(s) should transition to Green. If the
Input is out of range, the LED(s) transition to Red. In this case the calibration did not
succeed. Verify that the voltage source connection is correct and that the input is
exactly the specified Offset Calibration Value.
6. If the Offset Calibration was successful, then proceed to the Gain Calibration.
Connect exactly 75.000mV (the Gain Calibration Value) across each input channel.
7. Press 'Gain Cal' Button. This enables Gain calibration for the selected channel(s).
8. The Input is then sampled and the 'Gain' LED(s) should transition to Green. If the
Input is out of range, the LED(s) transition to Red. In this case the calibration did not
succeed. Verify that the voltage source connection is correct and that the input is
exactly the specified Gain Calibration Value.
9. If you need to continue the calibration for other channels, repeat from step 1) until all
channels are calibrated correctly.
10. When the calibration has succeeded, press 'Stop Calibration Mode' button. All
LEDs transition to White and the Navigator Tab becomes enabled.
Tools and Utilities
I/O Maintenance Tool
Release 100 Experion PKS Troubleshooting and Notifications Reference 623
1/03 Honeywell Part I
RTD Input (Rail I/O) Module Calibration



ATTENTION
This procedure only applies to TC-FIR081.

1. Select a Channel to be calibrated with the "Select" check box next to the Channel
Number. You can also select 'Sel All' to calibrate all channels at the same time.
2. Press 'Start Calibration Mode' Button. Calibration is prohibited if the Module is in
RUN Mode. Please inactivate and unload (delete) the Module from the Controller
before proceeding with calibration. If the calibration can proceed, the 'Cal Active'
LED on the top left corner transitions to Green.
3. Connect 1.00 ohm resistors across each input channel. Connect the low signal side to
24Vdc common. If using a decade box, connect all high signal terminals together and
attach to one lead from the decade box. Connect all low signal terminals together and
attach to the other lead and to 24V dc common. Set the decade box for 1.00 ohm. The
Offset Calibration Value is 1.00 ohm.
4. Press 'Offset Cal' Button. This enables Offset calibration for the selected channel(s).
5. The Input is then sampled and the 'Offset' LED(s) should transition to Green. If the
Input is out of range, the LED(s) transition to Red. In this case the calibration did not
succeed. Verify that the voltage source connection is correct and that the input is
exactly the specified Offset Calibration Value.
6. If the Offset Calibration was successful, then proceed to Selecting the RTD type for
the Gain Calibration. Use the table below to determine the Gain Calibration.
7. Connect the correct resistors across each input channel. Connect the low signal side to
24V dc common. Resistor values are shown in the table below. If using a decade box,
connect all high signal terminals together and attach to one lead from the decade box.
Connect all low signal terminals together and attach to the other lead and to 24V dc
common. Set the decade box for the value shown in the table below.
8. Press 'Gain Cal' Button. This enables Gain calibration for the selected channel(s).
9. The Input is then sampled and the 'Gain' LED(s) should transition to Green. If the
Input is out of range, the LED(s) transition to Red. In this case the calibration did not
succeed. Verify that the voltage source connection is correct and that the input is
exactly the specified Gain Calibration Value.
10. If you need to continue the calibration for other channels, repeat from step 1)
until all channels are calibrated correctly.
Tools and Utilities
I/O Maintenance Tool
624 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
11. When the calibration has succeeded, press 'Stop Calibration Mode' button. All
LEDs transition to White and the Navigator Tab becomes enabled.
RTD Input (Rail I/O) Calibration Value Table

Type of RTD Offset Calibration Value Gain Calibration Value
100 ohm Pt.
(alpha = 0.00385)
1 ohm, 0.1%, 5ppm/deg C
100 ohm Pt.
(alpha = 0.003916)
1 ohm, 0.1%, 5ppm/deg C 432ohm, 0.01%, 5ppm/deg C
120 ohm Nickel
(alpha = 0.00672)
1 ohm, 0.1%, 5ppm/deg C 432ohm, 0.01%, 5ppm/deg C
100 ohm Nickel
(alpha = 0.00618)
1 ohm, 0.1%, 5ppm/deg C 432ohm, 0.01%, 5ppm/deg C
10 ohm Copper
(alpha = 0.00427)
1 ohm, 0.1%, 5ppm/deg C 432ohm, 0.01%, 5ppm/deg C

200 ohm Pt.
(alpha = 0.00385)
1 ohm, 0.1%, 5ppm/deg C 864 ohm, 0.01%, 5ppm/deg C
200 ohm Nickel
(alpha = 0.00618)
1 ohm, 0.1%, 5ppm/deg C 864 ohm, 0.01%, 5ppm/deg C

500 ohm Pt.
(alpha = 0.00385)
1 ohm, 0.1%, 5ppm/deg C 1728 ohm, 0.01%, 5ppm/deg C
500 ohm Nickel
(alpha = 0.00618)
1 ohm, 0.1%, 5ppm/deg C

Tools and Utilities
I/O Maintenance Tool
Release 100 Experion PKS Troubleshooting and Notifications Reference 625
1/03 Honeywell Part I
Utilities Tab
The Utilities Tab is enabled once a Diagnostic Output Module is selected in the
Navigator Tab. The Utilities Tab is used to reset Diagnostic Output Module SHORT /
THERMAL OVERLOAD Faults as follows:
1. Be sure that the condition, which caused the Short/Overload, has been corrected.
2. Enable the Channel or Channels to be reset with the 'Enable Reset' check boxes.



CAUTION
Only Shorted Channels should be Enabled. Resetting Outputs that are "ON"
and NOT shorted will cause transition to the "OFF" (Unpowered) State.

3. Press the RESET COMMAND Button.
4. A RESET COMMAND WARNING Message Box will appear. This reminds the User
to confirm that Only Shorted Channels should be Enabled.
5. Press 'YES' if ready to Send the Command or 'NO' if you wish to change any Reset
Enable selections before sending the Command.
6. When the Command is sent, the Fault condition should be cleared for the Channel(s)
selected as indicated by {1} the I/O Module Detail Display on STATION, {2} the I/O
Channel Function Block in Control Builder, or {3} the LED status on the front of the
I/O Module.
Tools and Utilities
NetworkTools
626 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
NetworkTools
Overview
NetworkTools automatically starts up by scanning all nodes on the ControlNet/Ethernet
supervisory network segment connected to your computer. Information is presented in
three panes - the Tree pane (on the upper left), the List pane (on the upper right) and,
below them, the Detail pane. The List pane shows ControlNet message error counters
maintained by NetworkTools. Consult the Help file for NetworkTools (from the
applications menu bar or hit F1) for on-line Help.
Cautions



CAUTION
Honeywell makes the following recommendation:
NetworkTools is a utility. Under abnormal network conditions, this utility may
negatively impact network performance.
Do not use NetworkTools while connecting nodes to the network.
Do not use NetworkTools when monitoring an Analog I/O Module.
Do not use NetworkTools to monitor an Analog I/O ControlNet.
Do not use NetworkTools while On Control.

Consider running NetworkTools with the Pause / Resume mode of operation or using
Ping mode if you plan to engage in any of the above activities. This way you can let
NetworkTools remain launched while performing such activities.
Tools and Utilities
NetworkTools
Release 100 Experion PKS Troubleshooting and Notifications Reference 627
1/03 Honeywell Part I
Command Line options
NetworkTools supports several command-line options. Start NetworkTools at the
command prompt with the command-line options as follows:

Option Behavior
ntools -c Starts the NetworkTools application in the ControlNet mode. This
means NetworkTools scans for MAC IDs on a supervisory
ControlNet segment through the ControlNet Driver. If there is more
than one ControlNet Driver installed, the NetworkTools application
uses the first available driver. NetworkTools displays the MAC IDs
present in the tree pane.
ntools -e Starts the NetworkTools application in the Ethernet mode. This
means NetworkTools scans for the Ethernet drivers on the
supervisory Ethernet segment. There should be one Ethernet Driver
corresponding to each Ethernet module. NetworkTools displays the
driver names in the tree pane.
ntools -l NetworkTools executes in "Log" mode. This mode creates an ASCII
text file called log.txt in the same directory in which NetworkTools
lives. This contains a textual record of what modules were found on
the last scan.
Note: this option causes the log.txt file to be written every scan - this
may be more hard drive activity than some users want. Suggestion:
only use this when running NetworkTools in ping mode.
ntools -nl Used if you do not want to get warning messages (dialog boxed) for
Lonely CNIs. This is discouraged in normal practice but this
warning may become a nuisance in certain commissioning
situations.
ntools -u Allows the NetworkTools application to update the device firmware.
See the Update Firmware from File topic for more information.
Updating device firmware should not be done on-process.

Tools and Utilities
NetworkTools
628 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Launching NetworkTools
Use the following procedure to call up the NetworkTools (NTOOLS) utility.

Step Action
1 Click the Start button in the taskbar. Click Programs->Engineering Tools-
>NTOOLS to launch the application.
2 Click OK to acknowledge the warning about monitoring through Control
Builder.




3
Click the Resume button to begin the network scan.
4
If this is the initial launch of NTOOLS, click the Settings button to open
the Setting dialog box. Select the desired scanning options. The defaults are:
2 second delay between scans
Periodic (automatic) - selected
Enable mode version/revision checking checked
Enable ControlNet Parameter checking checked
Click OK to close the dialog box.
Tools and Utilities
NetworkTools
Release 100 Experion PKS Troubleshooting and Notifications Reference 629
1/03 Honeywell Part I
Step Action
5 For the initial NTOOLS launch, you must specify some details about your
particular network configuration. Click the first CNI/ENET icon under the
Desktop tree. Fill in the appropriate data in the Settings dialog box for the
Local and Remote chassis configurations in your network associated with the
given CNI/ENET. This only applies for the initial use of NTOOLS. Repeat this
step for the other CNI/ENET icons.




6 Once the graphic representation of the chassis appears in the Detail pane,
individual modules can be selected which results in the applicable menu
options becomming enabled.

Tools and Utilities
NetworkTools
630 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Step Action






Tools and Utilities
NetworkTools
Release 100 Experion PKS Troubleshooting and Notifications Reference 631
1/03 Honeywell Part I

Display Regions (panes)
NetworkTools automatically starts up by scanning all nodes on the Supervisory network
segment connected to your computer. Information is presented in three panes - the Tree
pane (on the upper left), the List pane (on the upper right) and, below them, the Detail
pane. The List pane shows ControlNet/Ethernet related statistics maintained by
NetworkTools.
Using the Detail Pane
Select one item (either the MAC ID of a CNI or the driver name for an Ethernet module)
from the Tree pane to populate the Detail pane with a Experion PKS controller. You may
be asked to provide the details on the controller. If so, fill in the details requested by the
Settings dialog boxs pages - use the check boxes if you have any remote chassis. Note
that you must provide the MAC IDs for the CNIs in any Remote chassis and you must
provide chassis slot positions for DownLink CNIs in your Local Chassis.
You can display one Local chassis and up to four Remote chassis at a time. Use the
NetworkTools > Settings menu pick for adjustments at any time. Your settings are saved
across sessions.
NetworkTools scans per your settings and report results in a visual manner on each
module discovered. NetworkTools can be run in Periodic (automatic)" mode or " Ping "
mode. If Periodic mode is chosen, you can specify a number between 1 and 60 that is the
time, in seconds, that NetworkTools "sleeps" between consecutive scans. Adjust this on
the Settings dialog. You can pause and resume Periodic scanning.
The text in the cyan boxes is the string provided in the Device Identity Object - typically,
the Model number (the TC- portion of the strings are suppressed to ease readability).
The green text in the black box is the human-readable version of the state information
acquired from the module during the scan. The Device Identity Object state is used for all
modules except the CPM for which the Extended Device Object state is used.
The V string is the Major (version) and Minor (revision) release identifiers for the
module.
The A and B text at the bottom of CNI modules indicates what ControlNet cable they
were using when last scanned. The Cable Redundancy Warning is indicated by a "W"
(this may appear if your system is only using a single ControlNet cable).
Tools and Utilities
NetworkTools
632 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Device Identity Dialog Box
Click on a modules face - it should get a red highlight rectangle around it. Now you can
use the Device > Show Details menu pick (or its "I.D" toolbar button) to reveal the
contents of the modules Device Identity Object dialog box. Double clicking on the
module will launch the dialog, too.
CNI ControlNet Stats Dialog Box
When you have clicked a CNI, you can use the Device > Show CNI Stats menu pick (or
its toolbar button showing a network) to show three pages of ControlNet statistics for the
selected CNI. The first page is static data; the second and third are dynamic. When this
dialog is showing, the normal scanning is suspended and the scanning for the statistics on
the second or third page occurs every one-half second.
ENET TCP/IP Configuration
When you have clicked an ENET, you can use the Device > TCP/IP Configuration menu
pick (or the right mouse button) to show the TCP/IP configuration for the selected ENET.
This dialog is only activated if NTOOLS is started with the -U command line option
and an Ethernet module is selected. When this dialog is showing, the normal scanning is
suspended and the scanning for the statistics on the second or third page occurs every
one-half second. This dialog contains the following:

IP Address The IP Address for the Ethernet module
Subnet Mask The Subnet Mask for the IP Address of the Ethernet module
Gateway
Address
The Gateway Address for the Ethernet module
BOOTP
Enable/Disable
flag
On Checking this check box, the BOOTP flag in the module is
enabled and on unchecking this, it is disabled.
If the BOOTP flag is enabled, the module expects a BOOTP
server on the Ethernet segment to provide it an IP Address, a
Subnet Mask and a Gateway Address after the next power up.
The module remains with all these three settings with all 0s until a
BOOTP Server replies to the module and successfully gives it an
IP Address, Subnet Mask and Gateway Address.
Tools and Utilities
NetworkTools
Release 100 Experion PKS Troubleshooting and Notifications Reference 633
1/03 Honeywell Part I
If the BOOTP flag is disabled, the module remembers its
configuration and uses it on next powerup. However, the module
also remembers the slot number and chassis where it was
configured. Thus, it is currently not possible to set an IP Address
in a slot and then shift the module to another slot. In this case,
the module enables BOOTP and all other settings are initialized
with 0s.

A screenshot of this dialog is shown:



Reset Error Counter Dialog Box
Use the Network > Reset Error Counters menu to reset Channel A and B error counters
(maintained by NetworkTools) for individual nodes on the Supervisory ControlNet
segment.
Status Bar
The progress of a scan is reflected in message on the right side of the status bar.
Tools and Utilities
NetworkTools
634 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
ControlNet Parameters
This section discusses the Keeper Values dialog box and its operation. This powerful
feature should only be used by those with a thorough understanding of the operation of
ControlNet. This function can only be used if you launched NetworkTools with the
appropriate command line option.
The reason this is under the "Device" menu is that one must select a keeper capable
module for NetworkTools to effect the network changes operation - CNIs have the
Keeper Object that orchestrates the distribution of new network parameters to all
segment nodes.
Depending on which keeper capable module is selected, all modules on the
corresponding ControlNet segment can be updated (i.e. the Supervisory network or
subsidiary I/O networks).
The ControlNet parameters that are presently in use that are viewable in the
ControlNetStats1 dialog, i.e., doubleclick on any CNI in the network
The ControlNet parameters that are stored in the Keeper Object any specific CNI are
viewable in the Present Keeper tab of the Keeper Values dialog. These parameters may
not represent the parameters in current use in the network, but would be impressed on the
network if this CNI became the Keeper node and found that network needed to have
ControlNet parameters impressed upon it.
The parameters in the Future Keeper tab of the Keeper Values dialog for any specific
CNI are just a calculation based on the values shown in the Changes tab of the Keeper
Values dialog. These will be the parameters stored in this CNI's Keeper Object when
you click OK..This is an operation that takes about 10 seconds at the end you are told
of the success and shown the Unique ID value that was impressed on the CNI (discussed
below).
Tools and Utilities
NetworkTools
Release 100 Experion PKS Troubleshooting and Notifications Reference 635
1/03 Honeywell Part I
ControlNet Unique ID
The Unique ID shown on the Present Keeper tab of the Keeper Values dialog box is
important for redundant chassis operation. It is strongly recommended that all CNIs at a
site be programmed for the same ControlNet parameters. Each time a CNI is
programmed for ControlNet parameters a shorthand code is calculated the Unique ID
and it too is stored to the CNI. The Experion PKS default values are as follows:

Supervisory
Network
I/O Network
NUT 10000 10000
SMAX 1 1
UMAX 24 20
Repeaters 0 0
Cable Length 1000 1000
Channel Usage A+B A+B
Fiber Optics No No

Unique ID 0xa0b3b298 0x4687418c

If your site needs to be different than the values above (e.g. you use fiber optics) then a
different Unique ID will result. Again, it is strongly recommended that all CNIs at a site
be programmed for the same ControlNet parameters.
If CNIs show !CPT in their four character display it could be because of a Unique ID
mis-match. To recover, update the ControlNet parameter settings for the secondary CNI
and then power-cycle the secondary chassis (so that the CNIs reattempt their partner
compatibility checks).
Flash Upgrades to CNI firmware do not affect the previously-stored ControlNet
parameter settings.
Tools and Utilities
NetworkTools
636 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Viewing SIM statistics
Use the following procedure to view SIM statistics in the open NTOOLS window.

Step Action
1 Click the CNI icon under the Desktop tree for the chassis that contains a SIM.
2 In the Detail pane, click the graphic representation of the SIM in the chassis
to select it.
3
Click Device->View SIM Details to call up the dialog box. Click the Pause
button to stop the network scan, if desired.
4 View the following statistics to determine if the rate of writes needs tuning.
Updates/sec: Shows the number of arrays transferred from the FTA to
the SIM per second. Divide this number by the number of arrays to find
the per array update rate.
Stores/sec: Shows the number of individual parameter writes per
second.
Overruns/sec: Shows the number of parameter writes that were not
accepted per second. A non-zero value is signaled as an overrun.
5 Click OK to close the dialog box.
6 Click NetworkTools->Exit to close the application.

Getting RM Events
The RMs History is stored as Events. Select (click) the RM and choose the Device >
Show History menu pick (or tool bar button).
Use this dialog to display the RMs Event Log and set the social time of the RM. You
cannot destroy the events - only view them. Use the Refresh button to re-fetch the most
recent events (this is useful if you think some new events have occurred since you
launched the dialog). The Set Time affects only the RM (not the other modules in the
controller chassis).
RMs contain their own Event Log and a small copy of their partners Log. Use the
checkbox to select which you want. Note the column called Src the letter T means
this RM (the one you clicked on before launching the dialog box; the letter O means
the other RM (the partner) is the source for the displayed events.
Tools and Utilities
NetworkTools
Release 100 Experion PKS Troubleshooting and Notifications Reference 637
1/03 Honeywell Part I
Getting CPM Breadcrumbs
The CPMs History is stored as Breadcrumbs. Select (click) the CPM and choose the
Device > Show History menu pick (or tool bar button). This menu pick can only be used
if you launched NetworkTools with the appropriate command line option.
Use this dialog to display the CPMs Bread Crumbs. You cannot destroy the Bread
Crumbs - only view them.
Note that retrieving Bread Crumbs occurs at a priority higher than executing control
this my adversely affect the control mission.
Use the Refresh button to re-fetch the most recent Bread Crumbs (this is useful if you
think some new Bread Crumbs have occurred since you launched the dialog.
Firmware Upgrades
Updating device firmware should not be done on-process. The Update Firmware from
file menu pick can only be used if you launched NetworkTools with the -u command
line option.



TIP
Read the Software Installation and Upgrades Guide for its discussion of
this topic.
Remove from the chassis all modules except the one you are about to
upgrade. While this is not necessary, it removes distractions and module
interaction that could cause failure of the upgrade.
Read the dialog boxes you are presented with very carefully. If you are
ever confronted with a dialog which is titled Warning: Use Extreme Care
be very certain before you click OK. If the text in that dialog says The NVS
file you have chosen does not contain a reference to the module you
selected you may have selected an inappropriate image to Flash to the
target module.

Tools and Utilities
NetworkTools
638 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03

CNI: Select (click) the CNI in the Detail Pane and choose the Device :> Update
Firmware from file dialog.
CPM: Select (click) the CPM in the Detail Pane and choose the Device :> Update
Firmware from file dialog. If you asked to change the state of the CPM,
select OK but realize that this causes the CPM to re-boot. If you proceed
too quickle to the actual Flashing operation (firmware upgrade) the
operation will fail (but in a graceful, recoverable way). The lesson: in this
case wait until the CPM has fully rebooted.
In some situations the Flashing operation starts but goes on and on until a
failure is finally declared. This is a graceful, recoverable failure. But it if
happens more than once, you are advised to shut down the CDA service
and try again. (If you do this, remember to restart the CDA service).
ENET Select (click) the ENET in the Detail Pane and choose the Device :> Update
Firmware from file dialog.
I/O: Select (click) the I/O in the Detail Pane and choose the Device :> Update
Firmware from file dialog. No special instructions apply.
PCIC: Select (click) the PCIC in the Tree Pane and choose the Device :> Update
Firmware from file dialog. It is suggested that CDA Service be shut down
before starting this operation.
RM: Select (click) the RM in the Detail Pane and choose the Device :> Update
Firmware from file dialog. The redundantYou cannot upgrade a RM that is
showing E054 or some other failure code on its 4 character display.

Tools and Utilities
ENET Browser Information
Release 100 Experion PKS Troubleshooting and Notifications Reference 639
1/03 Honeywell Part I
ENET Browser Information
The TC-CEN011 provides extensive diagnostic to be used in troubleshooting Ethernet
related problems on an Ethernet network. These diagnostics are best used by a trained
network technician who can use these diagnostic and performance monitoring tools to
isolate networking problems. The user can access all the diagnostic information about
the TC-CEN011 Ethernet Module using Microsoft Internet Explorer. To access the main
screen, enter the IP address of the module into the Address block of MS Internet
Explorer.
Main Screen
The user can select any of the four sub-screens once the main screen is displayed.



Tools and Utilities
ENET Browser Information
640 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Main Screen - Module Information
There is no user configurable or usable information on this screen. This screen is useful
for advanced diagnostics and provides useful information for troubleshooting
technicians.



Tools and Utilities
ENET Browser Information
Release 100 Experion PKS Troubleshooting and Notifications Reference 641
1/03 Honeywell Part I
Main Screen - TCP/IP Configuration



TCP/IP Configuration - IP Address
The IP address identifies each node on the IP network (or system of connected networks).
Each TCP/IP node on a network (including the Ethernet module) must have a unique IP
address.
The IP address is 32 bits long and has a net ID part and a host ID part. Each network is a
Class A, Class B, or Class C network. The class of a network determines how an IP
address is formatted.
Each node on the same physical network must have an IP address of the same class and
must have the same net ID. Each node on the same network must have a different host ID
thus giving it a unique IP address.
IP addresses are written as four decimal integers (0-255) separated by periods where each
integer gives the value of one byte of the IP address. For example, the 32-bit IP address:
00000011 00000000 00000000 00000001 is written as 3.0.0.1.
Tools and Utilities
ENET Browser Information
642 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
You can distinguish the class of an IP address from the first integer in its dotted-decimal
IP address as follows:

Range of first
integer
Class Range of first integer Class
0 127 A 192 223 C
128 191 B 224 255 Other

Contact your network administrator or the Network Information Center for a unique IP
address to assign to your module.
TCP/IP Configuration - Subnet Mask
Subnet addressing is an extension of the IP address scheme that allows a site to use a
single net ID for multiple physical networks. Routing outside of the site continues by
dividing the IP address into a net ID and a host ID via the class. Inside a site, the subnet
mask is used to redivide the IP address into a custom net ID portion and host ID portion.
Take Network 2 (a Class B network) in the previous example and add another physical
network. Selecting the following subnet mask would add two additional net ID bits
allowing for four physical networks:
Example:
11111111 11111111 11000000 00000000 = 255.255.192.0
Two bits of the Class B host ID have been used to extend the net ID. Each unique
combination of bits in the part of the host ID where subnet mask bits are 1 specifies a
different physical network.
Tools and Utilities
ENET Browser Information
Release 100 Experion PKS Troubleshooting and Notifications Reference 643
1/03 Honeywell Part I
TCP/IP Configuration - Gateway Mask
A gateway connects individual physical networks into a system of networks. When a
node needs to communicate with a node on another network, a gateway transfers the data
between the two networks. The following figure shows gateway G connecting Network 1
with Network 2.
When host B with IP address 128.2.0.1 communicates with host C, it knows from Cs IP
address that C is on the same network. In an Ethernet environment, B can then resolve
Cs IP address to a MAC address (via ARP) and communicate with C directly.
When host B communicates with host A, it knows from As IP address that A is on
another network (the net IDs are different). In order to send data to A, B must have the IP
address of the gateway connecting the two networks. In this example, the gateways IP
address on Network 2 is 128.2.0.3.
The gateway has two IP addresses (128.1.0.2 and 128.2.0.3). The first must be used by
hosts on Network 1 and the second must be used by hosts on Network 2. To be usable, a
hosts gateway must be addressed using a net ID matching its own.
TCP/IP Configuration - Name Server and Secondary Name Server
In Internet terminology, computers referred to as name servers provide services that
maintain name-to-IP address mappings. These DNS name servers provide this
information to client computers and programs that need to connect to other computers on
a network. Name servers provide a look-up service. Please refer to the network
administrator for more information regarding name servers.
Tools and Utilities
ENET Browser Information
644 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
TCP/IP Configuration - BOOTP
BOOTP (Bootstrap protocol) is a low-level protocol that provides configurations to other
nodes on a TCP/IP network with DOS, Microsoft Windows, Windows NT, Windows 95,
VMS and HP-UNIX platforms. BOOTP configuration files let you automatically assign
IP addresses to the Ethernet module. You can also obtain subnet masks and gateway
addresses from BOOTP. The Ethernet module factory default is BOOTP enabled. Upon
powerup, the module sends a message to the BOOTP server on the network with its
hardware address. The server is a computer that has BOOTP server software installed.
The server compares that hardware address to those in its look-up table in the
configuration file and sends a message back to the module with the appropriate IP
address.
With all hardware and IP addresses in one location, you can easily change IP addresses in
the BOOTP configuration file if your network needs to be changed.
If BOOTP is disabled (or there is no BOOTP server on the network), you can use the
Experion PKS Control Data Access Server to configure the TC-CEN011 Ethernet
module.
Main Screen - Diagnostic Information



Tools and Utilities
ENET Browser Information
Release 100 Experion PKS Troubleshooting and Notifications Reference 645
1/03 Honeywell Part I
Diagnostic Information - Network Statistics
The Network Statistics define statistics that are industry standards and are defined in the
Management Information Base for Network Management of TCP/IP-based internets
Request For Comments RFC 1156. No additional detail will be provided here. These
statistics are used by Network Administrators to monitor the health of a TCP/IP network.
They are provided here for reference only.
Network Statistics - Ethernet Statistics



Tools and Utilities
ENET Browser Information
646 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Network Statistics - ICMP Statistics



Network Statistics - IGMP Statistics



Tools and Utilities
ENET Browser Information
Release 100 Experion PKS Troubleshooting and Notifications Reference 647
1/03 Honeywell Part I
Network Statistics - IP Statistics



Network Statistics - UDP Statistics



Tools and Utilities
ENET Browser Information
648 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Network Statistics - TCP Statistics



Network Statistics - TCP Extended Statistics



Tools and Utilities
ENET Browser Information
Release 100 Experion PKS Troubleshooting and Notifications Reference 649
1/03 Honeywell Part I
Network Statistics - Network Memory Statistics



Network Statistics - Mbuf Statistics



Tools and Utilities
ENET Browser Information
650 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Diagnostic Information - Miscellaneous
The following three sections have no user configurable or usable information on this
screen. This screen is useful for advanced diagnostics and provides useful information
for troubleshooting technicians.
Miscellaneous - Crash Display



Miscellaneous - General Memory Statistics



Tools and Utilities
ENET Browser Information
Release 100 Experion PKS Troubleshooting and Notifications Reference 651
1/03 Honeywell Part I
Miscellaneous - TGFT Task Statistics
CIP (TCP/IP) Statistics
CIP (IP) Statistics
Encapsulation Protocol Stats
TGFT (CIP) Statistics

TGFT Task Statistics - CIP (TCP/IP ) Statistics



Tools and Utilities
ENET Browser Information
652 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
TGFT Task Statistics - CIP (IP) Statistics



TGFT Task Statistics - Encapsulation Protocol Stats



Tools and Utilities
ENET Browser Information
Release 100 Experion PKS Troubleshooting and Notifications Reference 653
1/03 Honeywell Part I
TGFT Task Statistics - TGFT (CIP) Statistics



Main Screen - Chassis Who
The Chassis Who utility allows a user to graphically see what hardware is currently in the
chassis. The user can then select any module and retrieve more diagnostic information
about the particular module.
Tools and Utilities
ENET Browser Information
654 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03

Release 100 Experion PKS Troubleshooting and Notifications Reference 655
1/03 Honeywell Part I
Effective Trouble Reporting
What Makes A PAR Effective
A PAR (Product Anomoly Report) is the formal means by which problems are
documented, from identification to eventual resolution, fix verification, and closure.
The life cycle of a PAR is very much dependent on a thorough description of the
problem. When filing a PAR, the following guidelines will help enhance the
effectiveness of the report:

Clue Value
Component Version
& Revision
Problems are many times unique to a release or set of
releases. Code inspections and problem reproducability are
dependent on this information.
Always provide the Experion PKS release number, e.g.,
PS120.0-26.1.
Where a problem has been localized to a module or modules,
go to NetworkTools and get the version/revision numbers for
those modules. To reinforce the Experion PKS release
number, it is also helpful to record RSLinx, KTC and CNI
release numbers.
TAC will contact the user if specific version/revision
information is needed.
Topology A general description of the system topology is usually
important.
e.g., Redundant server, dual media ControlNet, 1 RCP with 2
downlinks, 1 RCP with 1 downlink, and 1 non-redundant
controller with 2 downlinks, single I/O rack with all downlinks.
If the problem is thought to be topology oriented, then a more
detailed description/drawing is appropriate, including MAC ID
assignments.
Symptoms What about system operation is abnormal?
What CNI, CPM, RM, CB, and/or SCAN error/fault indicators
(LED states or error codes) are present?
What alarms surround the abnormal condition?
Effective Trouble Reporting
What Makes A PAR Effective
656 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Clue Value
Preceding Events &
Actions
What lead up to this situation?
Where actions were being taken prior to the event?
What was the state of the system prior to the event?
It is important that this information be recorded while it is still
fresh in the Users mind.
Logs
(see the respective
Tool sections for
details on log
retrieval procedures)
What recorded events surround the abnormal condition?
This question is best handled by printing/saving pertinent log
content and attaching the printouts/files to the report. Error
on the side of too many (vs. too few) events.
The following logs should be considered for storage and
attachment:
SCAN Logs (both if redundant)
CB Logs
CPM Breadcrumbs (both if redundant) (see
NetworkTools)
RM Event Logs (both) (see NetworkTools)
Recovery
procedures
What recovery procedures where taken? Many times this
information is extremely helpful in pinpointing the states of the
components prior to recovery.
NOTE: Controller Redundancy is designed to maintain
control through a very large percentage of fault and recovery
situations. It is very important that prescribed recovery
procedures be followed.
Repeatability If a problem is persistent, how persistent? This information is
helpful in determining how the problem reproduction is
approached.


PM I/O Component Description
Introduction
Release 100 Experion PKS Troubleshooting and Notifications Reference 657
1/03 Honeywell Part I
PM I/O Component Description
Introduction
This section provides a quick reference to various topics related to Process Manager I/O
assemblies and components that may be helpful in troubleshooting PM I/O subsystem
faults.
Component part numbers
The Honeywell part numbers for all components described in this section are listed in
Spare Parts
PM I/O Component Description
Power System Controls
658 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Power System Controls
Control of ac power to the Power Supply Modules is provided by two methods when the
control cabinet contains the normal Standard Power System components.
AC power control
All ac power to the control cabinet, which includes any cabinet fan assemblies, is
controlled by a dedicated circuit breaker that is supplied by the user for each power
supply module in the power system. Additional ac power supply module control is
provided by a power switch that is mounted at the front of each module.
DC power control
Since the standard power system can contain redundant power supply modules, placing a
modules power switch in the off position does not necessarily remove power from the
controller chassis, IOP card files and Field Termination Assemblies (FTAs) in the cabinet
because the second module will continue to supply power unless its Power switch is in
the off position.
If the standard power system contains a battery backup module, 24 Vdc power will
continue to be supplied to the controller chassis, card files and FTAs unless the
BATTERY switch is placed in the off position, or the battery backup module is
discharged. All three switches must be in the off position to completely remove power
from the equipment.
AC Only Power System
In a cabinet that contains an AC Only Power System, no battery backup module exists to
provide 24 Vdc power to the equipment, so control of dc power to the controller chassis,
card files and FTAs is provided exclusively by user supplied ac circuit breakers. When
redundant power supply modules exist, each module has its own circuit breaker that is
provided by the user. There is no on-off switch at the front of the power supply module.
IOP Card Power Interrupt Switches
The PM I/O Link cards, and each IOP card have a 24 Vdc power interrupt switch that is
activated by unlocking and lifting the upper card extractor/insertion lever. Activating an
IOP card power interrupt switch removes power only from that IOP card. Power is
removed only while the switch is activated.

PM I/O Component Description
Power System Controls
Release 100 Experion PKS Troubleshooting and Notifications Reference 659
1/03 Honeywell Part I

WARNING
The loss of power to an analog or digital output IOP causes the loss of the
IOPs outputs to the field connections. Analog output IOP outputs drop to a
nonpowered state (-6.9%), and the digital output IOP outputs are set to their
off state.
The nonpowered state of the output IOPs should result in a safe condition for
personnel, the plant, and the process under control.

PM I/O Component Description
PM I/O Subsystem Overview
660 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
PM I/O Subsystem Overview
Major assemblies
The Process Manager I/O (PM I/O) subsystem is comprised of the major assemblies that
are described in the following subsections. The following figure is a view of a single
cabinet containing nonredundant IOP card files and identifies some of PM I/O
assemblies. The PM I/O major assemblies are:
Left 7-Slot IOPCard File (Slots 1 through 7)
Right 7-Slot IOP Card File (Slots 9 through 15)
15-Slot IOPCard File
Input/Output Processor Cards (IOPs)
Field Termination Assemblies (FTAs)
Power Systems

PM I/O Component Description
PM I/O Subsystem Overview
Release 100 Experion PKS Troubleshooting and Notifications Reference 661
1/03 Honeywell Part I


Single Control Cabinet with PM I/O

PM I/O Component Description
PM I/O Subsystem Overview
662 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Card file types
Three types of card files can accommodate Input/Output Processor (IOP) cards. The Left
7-Slot (Slots 1 through 7), Right 7-Slot Card File (Slots 9 through 15) and 15-Slot card
files.
IOP Card File Models

Card File Description CE Compliant Non-CE Compliant
Left 7-Slot MU-HPFI03 MU-HPFH01
Right 7-Slot MU-HPFI13 MU-HPFH11
15-Slot MU-HPFI23 MU-HPFX02

Total number of card files
The number of card files that can exist in a single PM I/O subsystem is dependent upon
the mix of 7-Slot and 15-Slot card files. Eight I/O Link addresses are available for use in
the PM I/O subsystem. Each card file must be assigned a unique I/O Link Interface
address. Two 7-Slot card files can share the same I/O Link address if one is a Left card
file (slots 1-7) and the other a Right card file (slots 9-15). The 15-Slot card file cannot
share its I/O Link address with another card file. It is conceivable that sixteen 7-Slot card
files can exist in a PM I/O subsystem (eight Left 7-Slot and eight Right 7-Slot card files).
Remote card file installation
IOP card files can be installed at remote locations through the use of I/O Link Extender
cards that are installed in the card files. I/O Link Extender cards provide the
communications link between the local control cabinet or cabinet complex and the
remote location card files.
Total number of IOPs
Depending upon the configuration of IOP types, up to 40 primary IOPs, 40 secondary
(redundant) IOPs, and 3 I/O Link Extenders (a maximum of 8 I/O Link Extender cards)
can exist in a single PM I/O subsystem.
PM I/O Component Description
PM I/O Subsystem Overview
Release 100 Experion PKS Troubleshooting and Notifications Reference 663
1/03 Honeywell Part I
15-Slot IOP card file
The following figure illustrates a 15-slot IOP card file.



15-Slot IOP Card File
PM I/O Component Description
PM I/O Subsystem Overview
664 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Types of Input/Output Processors (IOPs)
There are various types of IOP card assemblies. Some IOP card types interface with
more than one type of Field Termination Assembly (FTA). The functional types of IOPs
are:
High Level Analog Input (HLAI)
Low Level Analog Input (LLAI)
Low Level Analog Multiplexer (LLMux)
Remote Hardened Low Level Analog Multiplexer (RHMUX)
Digital Input (DI)
Analog Output (AO)
Digital Output (DO)
Smart Transmitter Interface (STI)
Smart Transmitter Interface Multivariable (STIM)
Digital Input Sequence of Events (DISOE)
Some of the functional types of IOPs support only certain associated Field Termination
Assemblies (FTAs) models because the number of channels (Points) differ. Examples
are the Analog Output (8 and 16 channels) and Digital Output (16 and 32 channels) IOPs.
Redundant IOPs
IOPs can be connected in a redundant configuration with both IOPs connected by
separate cables to the same FTA. Some models of the following types of IOPs support
redundancy.
Smart Transmitter Interface (STI)
High Level Analog Input (HLAI)
Digital Input (DI)
Digital Output (DO)
The following figure illustrates an HLAI FTA that interfaces with a pair of HLAI IOPs
that are installed in separate 7-Slot card files.

PM I/O Component Description
PM I/O Subsystem Overview
Release 100 Experion PKS Troubleshooting and Notifications Reference 665
1/03 Honeywell Part I


HLAI FTA with Redundant HLAI IOPs
Redundant AO IOPs
When an Analog Output FTA interfaces with two IOPs through separate cables, and an
automatic selector switch on the FTA selects which IOPs output drives the field wiring
terminal connectors on the FTA.
PM I/O Component Description
PM I/O Subsystem Overview
666 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Low Level Multiplexer IOP (LLMux)
A Low Level Analog Input Multiplexer (LLMux) IOP processes up to 32 inputs from
two 16 input FTAs.
The following figure illustrates LLMux FTA interconnections for non-CE Compliant
FTA models. CE Compliant FTA models are similar. See Process Manager I/O
Installation and Wiringin the Control Hardware Installation Guide for detailed
information.

PM I/O Component Description
PM I/O Subsystem Overview
Release 100 Experion PKS Troubleshooting and Notifications Reference 667
1/03 Honeywell Part I


Low Level Multiplexer Interconnections
PM I/O Component Description
Field Termination Assemblies for IOPs
668 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Field Termination Assemblies for IOPs
Two types of FTAs
There are two types of FTAs, Thermocouple (TC) and Resistive Temperature Device
(RTD), that are connected to the IOP through a Power Adapter assembly as shown in in
the previous figure. One TC and one RTD FTA, or two of the same type FTAs can be
connected to one IOP through the Power Adapter. See Planning for Low Level
Multiplexer IOP in the Planning Guide for detailed information.
Power Adapter
The Power Adapter provides power to the FTA(s) from the IOP and can be installed on
an FTA mounting channel.
The Power Adapter assembly has two LEDs, one for each cable that indicates a grounded
or shorted cable. Each FTA has an LED that indicates the FTA is receiving power
IOP to Power Adapter connection
The IOP to Power Adapter connection is made using the standard model MU-KFTAxx
(the suffix xx in the model number represents the length of the cable in meters) IOP to
FTA cable. The maximum allowable length is 50 meters (164 feet).
For CE Compliance applications, the model MU-KFTSxx IOP to FTA cable must be
used.
Power Adapter to FTA connection
The Power Adapter connects to either FTA type with a model MU-KLAMxx (internal
cabinet use) or model MU-KLXxxx (external cabinet use) cable (one per FTA) as shown
in the previous figure. The cable is limited to a maximum length of 305 meters (1000
feet).
The model MU-KLAMxx cable has two individually shielded, twisted pair wires. The
shield must be connected to ground at the Power Adapter end of the cable only.
The model MU-KLXxxx external cabinet cable has four wires with a single braided
shield. The braided shield must be connected to ground at both the Power Adapter and
FTA ends of the cable.
For CE Compliance applications, Belden model 83654 braided shield cable must be used.
PM I/O Component Description
Field Termination Assemblies for IOPs
Release 100 Experion PKS Troubleshooting and Notifications Reference 669
1/03 Honeywell Part I
Remote Hardened Low Level Multiplexer IOP (RHMUX)
The Remote Hardened Low Level Analog Input Multiplexer (RHMUX) IOP can process
up to 32 inputs from two 16-input FTAs. The following figure illustrates the RHMUX
IOP, Power Adapter, and Thermocouple FTA interconnections for a CE Compliant
application.

PM I/O Component Description
Field Termination Assemblies for IOPs
670 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03


Remote Hardened Low Level Multiplexer Interconnections
PM I/O Component Description
Field Termination Assemblies for IOPs
Release 100 Experion PKS Troubleshooting and Notifications Reference 671
1/03 Honeywell Part I
RHMUX Thermocouple FTA
One or two Thermocouple (TC) type RHMUX FTAs can be connected to a RHMUX
IOP through either an Intrinsically Safe (IS) or Non-Incendive (NI) Power Adapter
assembly.
FTA and Power Adapter installation
The Power Adapter provides power to the FTA(s) from the IOP. Both types of Power
Adapters can be installed on an FTA mounting channel. The FTAs dimensions (size)
are non-standard and prevent installing the FTA on a standard FTA mounting channel.
The Power Adapter assembly has two LEDs, one for each cable, that indicate a grounded
or shorted cable. Each FTA has an LED that indicates the FTA is receiving power.
IOP to Power Adapter connection
The IOP to Power Adapter connection is made using the standard model MU-KFTAxx
(the suffix xx in the model number represents the length of the cable in meters) IOP to
FTA cable. The maximum allowable length is 50 meters (164 feet).
For CE Compliance applications, the model MU-KFTSxx IOP to FTA cable must be
used.
Power Adapter to FTA connection
The Power Adapter connects to the FTA through a model MU-KLXxxx (internal cabinet
use) or model MU-KLO305 (external cabinet use) cable (one per FTA). The model MU-
KLXxxx cable is limited to a maximum length of 305 meters (1000 feet), while the
model MU-KLO305 cable is 305 meters in length, the cable type (Belden YC41926) can
be used in lengths of up to 2000 meters (6560 feet).
Both types of cables have four conductors in a single-twist with a single braided shield.
The shield must be connected to ground at both the Power Adapter and FTA ends of the
cable.
PM I/O Component Description
I/O Link Extender (Fiber Optic Link)
672 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
I/O Link Extender (Fiber Optic Link)
The I/O Link Extender provides the ability to locate 7-Slot and 15-Slot IOP card files and
associated FTAs up to 8 kilometers (5 miles) from the IOLIM. Two types of I/O Link
extenders and their associated fiber optical coupler modules are available, the Standard
I/O Link extender which provides up to a 1.3 kilometers (4000 feet) link, and the Long
Distance I/O Link extender which provides up to an 8 kilometers (5 miles) link. The
connection is made using a pair of fiber optic transmission cables, driven and terminated
by a fiber optical coupler module that mates with the connector located directly below
the card file slot in which the I/O Link extender card is installed.
Features and guidelines
Each I/O Link extender consists of two I/O Link extender cards, one for Link A
and one for Link B, which occupy two slots in the IOP card file.
Each Standard I/O Link extender card has an associated fiber optical coupler
module that can drive up to three pair of fiber optic cables. Each cable pair is
terminated by a fiber optical coupler module that terminates one fiber optic pair.
Each long distance I/O Link extender card has an associated fiber coupler that
drives a single pair of fiber optic cables. Each cable pair is terminated by a fiber
optical coupler module that terminates one fiber optic pair.
Every remote card file, or complex of IOP card files, requires two I/O Link
extender cards and two fiber optical coupler modules, one for Link A and one
for Link B. The Standard I/O Link extender card will drive and terminate Link
A or Link B, depending upon the card file number and card file slot number. If
the card file number and card files slot number are both odd or both even, the
card will drive Link A. If the card file number and card files slot number are
not both odd or both even, the card will drive Link B. The Link A or Link B
selection for the long distance I/O Link extender is determined by a jumper on
the card.
Two Standard I/O Link Extender cards, connecting up to six remote card files,
can be installed in an IOP card file, but the maximum number of other primary
IOPs is still 40 (plus 40 redundant IOPs).
The maximum fiber optic cable length is dependent upon the number of splices
and quality of the cable (dB loss per meter of cable). This maximum can be
between 0.98 and 1.3 kilometers for the Standard I/O Link Extender and 8
kilometers for the Long Distance I/O Link Extender. See the Signal Loss
Budget calcaulationin the Planning Guide.
PM I/O Component Description
I/O Link Extender (Fiber Optic Link)
Release 100 Experion PKS Troubleshooting and Notifications Reference 673
1/03 Honeywell Part I
Front panel indicators
Two visual front panel indicators are provided on the I/O Link Extender card that are
consistent with the display of IOP card indicators. The upper indicator is illuminated if
the fused +24 Vdc is present on the card (the input voltage is acceptable). The lower
indicator denotes status.
Status indicator operation
In normal operation, the lower indicator is illuminated when messages are being
transmitted from the fiber optic cable. The indicator should be fully lit or slightly
flickering, depending on system loading. Abnormal operation will result in the anti-
jabber circuit locking up the transmitter circuit when the transmission period has been too
long. The indicator will then be off. If the fiber optical coupler module is improperly
installed, the indicator will blink at a 50% duty cycle. The anti-jabber circuit can be reset
by cycling the upper extractor/insertion lever power switch on the I/O Link extender
card. For the long distance I/O Link extender, cycling power resets both ends of the link.
The standard I/O Link extender must be manually reset at both ends of the link. The long
distance I/O Link extender can be reset by cycling power at one end of the link.
For more detailed information on I/O Link Extender installation and system components,
refer to Installing Remote I/O in the Control Hardware Installation Guide.
PM I/O Component Description
Field Termination Assemblies (FTAs)
674 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Field Termination Assemblies (FTAs)
Terminal connectors on FTAs provide the connection points for the process control
wiring to sense, condition, or operate the connected device. Depending upon the type of
FTA, fuses, relays, and resistors protect the FTA circuitry. The FTA communicates with
an associated IOP, which in turn communicates with the IOLIM.
FTAs types
Standard types of FTAs, as described in the following table, interface the field wiring and
provide communication with an associated IOP. They are categorized as standard
because types of galvanically isolated FTAs are also available as described below.
The model and part numbers for available individual FTAs of each type can be found in
the Spare Parts.
Detailed descriptions
Refer to the Process Manager I/O Installation and Wiringin the Control Hardware
Installation Guide for a more detailed description and installation information of each
FTA.
Standard Field Termination Assembly Types

FTA Type Description
High Level Analog
Input/Smart Transmitter
Interface (HLAI/STI)
Accepts high level analog inputs. The inputs are configurable as
single-ended or differential in relation to logic common. This FTA is
also used to interface a Smart Transmitter device.
High Level Analog Input
(HLAI)
Accepts high level analog inputs. The inputs are configurable as
single-ended or differential in relation to logic common.
Smart Transmitter
Interface (STI)
Interfaces with Smart Transmitter devices. The interface is
referenced to logic ground. The Smart Transmitter provides field
isolation.
Low Level Analog Input
(LLAI)
Can be configured to accept low-level or high-level analog inputs.
Low-level analog inputs include Thermocouples (TC), Resistance
Temperature Detectors (RTDs), or millivolt sources. High-level
inputs such as voltage sources (0-5 V) and 4-20 milliamp current
loop devices are acceptable.The inputs are isolated from each other
and the IOLIM, but share a common bus for field wire shields.
PM I/O Component Description
Field Termination Assemblies (FTAs)
Release 100 Experion PKS Troubleshooting and Notifications Reference 675
1/03 Honeywell Part I
FTA Type Description
Low Level Analog Input
Multiplexer (LLMux)
or Remote Hardened
Low Level Analog
Multiplexer (RHMUX)
The FTA accepts one set of low-level analog inputs, such as
thermocouples (TC) or Resistance Temperature Detectors (RTDs).
The set of inputs must be either thermocouples or RTDs. The inputs
are sequentially multiplexed. One or two FTAs of either type can be
connected to one Power Adapter assembly and its IOP.
Analog Output (AO) Provides 4-20 mA analog outputs to proportioning loads such as
valves.
Analog Output (AO)
HART
Provides 4-20 mA outputs, and incorporates circuitry to allow HART
field devices to be connected to the FTA without using external
filters. These FTAs also provide a connector for an external HART
multiplexer.
120 Vac Digital Input
(DI)
Accepts ac digital inputs. All inputs are isolated from each other.
Two versions of the FTA are available, with and without pluggable
input modules.
240 Vac Digital Input
(DI)
Similar to the 120 Vac DI FTA, except it has a higher operating
voltage and a lower sense current. The inputs are in four groups of
eight circuits with a common return for each group. Groups are
isolated from each other.
24 Vdc Digital Input (DI) Accepts contacts grouped with an isolated common return. Two
versions of the FTA are available, with and without pluggable input
modules.
120/240 Vac Solid-State
Digital Output (DO)
Provides solid-state ac digital outputs that are isolated from each
other and the IOLIM.
3-30 Vdc Solid-State
Digital Output (DO)
Provides dc power digital outputs that are isolated from each other
and the IOLIM.
31-200 Vdc Solid-State
Digital Output (DO)
Provides dc power digital outputs that are isolated from each other
and the IOLIM.
24 Vdc Nonisolated
Digital Output (DO)
Provides nonisolated digital outputs to loads such as lamps and
relays. The signals are referenced to logic common.
24 Vdc Isolated Digital
Output (DO)
Provides isolated digital outputs to loads such as lamps and relays.
The signals are not referenced to logic common.
120 Vac/125 Vdc Relay
Digital Output (DO)
Provides independent electromechanical relays for ac or dc digital
outputs.
240 Vac/125 Vdc Relay
Digital Output (DO)
Provides independent electromechanical relays for ac or dc digital
outputs.

PM I/O Component Description
Field Termination Assemblies (FTAs)
676 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Galvanically isolated FTAs
Galvanically isolated FTA types are listed in following table.
Galvanically Isolated Field Termination Assembly Types

FTA Type Description
High Level Analog Input
(HLAI/STI)
The HLAI/STI FTA accepts high level analog inputs. Some FTA
models also interface with Smart Transmitter devices. All inputs are
isolated from ground and each other.
24 Vdc Digital Input (DI) The 24 Vdc DI FTA accepts contact inputs. All inputs are isolated
from each other.
Analog Output (AO) The AO FTA provides isolated 4-20 mA outputs to proportioning
loads such as valves.
Analog Output (AO)
HART
Provides 4-20 mA outputs, and incorporates circuitry to allow HART
field devices to be connected to the FTA without using external filters.
These FTAs also provide a connector for an external HART
multiplexer.
24 Vdc Digital Output
(DO)
The 24 Vdc DO FTA provides isolated digital outputs to loads such as
solenoid valves or lamps.

Three physical sizes
The standard FTAs have three physical sizes as illustrated in the following figure. The
Galvanically isolated FTAs are one size only, B-size.

PM I/O Component Description
Field Termination Assemblies (FTAs)
Release 100 Experion PKS Troubleshooting and Notifications Reference 677
1/03 Honeywell Part I
C
Size
FTA
Hole Size = 3.96
.156
A
B
C
152.4/6.00
307.3/12.10
462.3/18.20
120.7/4.75
120.7/4.75
120.7/4.75
W
B
Size
FTA
L
10.8
.425
A
Size
FTA
L
Length L Width W Size
L
5.7
0.225
104.2
4.10
5.1
0.20
All measurements are in:
millimeters
inches
Note:

The center of the mounting holes is a constant distance from the edge of the
assembly board for all three FTA sizes as shown for size B.

Sizes B and C, depending on the type of FTA, can have additional mounting holes
along the length (sides) of the FTA. The additional mounting holes all fall on a grid
established for mounting adjacent A-size FTAs.
297.2
11.70
142.2
5.60
17.8
452.1


Field Termination Assembly (FTA) Sizes
PM I/O Component Description
Field Termination Assemblies (FTAs)
678 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
FTA Mounting
The FTAs are installed at the rear or front of a dual access cabinet on one or more FTA
mounting channels. In a single access cabinet, the FTAs are mounted on FTA mounting
channels at the front of the cabinet. The FTA mounting channels also function as cable
and wiring channels, or troughs. The standard and galvanically isolated FTAs must not
be mounted on the same FTA mounting channel. Mounting both types of FTAs on the
same FTA mounting channel is an intrinsic safety violation because their field wiring
will be routed together. See Installing Standard FTAsin the Control Hardware
Installation Guide for additional information on FTA insallation.
Vertical orientation
Standard and galvanically isolated FTAs are mounted on vertically oriented 3-foot long
FTA mounting channel segments; however, Standard and galvanically isolated FTAs
must not be mounted on the same FTA mounting channels.
Galvanically isolated FTAs can be mounted on an FTA mounting channel that is above
or below an FTA mounting channel that has standard FTAs mounted on it, but the field
wiring must never be routed in the standard FTAs channel.
PM I/O Component Description
FTA Mounting Channels
Release 100 Experion PKS Troubleshooting and Notifications Reference 679
1/03 Honeywell Part I
FTA Mounting Channels
FTA mounting channels are used to mount the FTAs and to organize and separate the
field wiring and IOP to FTA cables.
The FTAs are installed on FTA mounting channels that are located in the front of a single
access control cabinet, and in the rear or front of a dual access cabinet.
The number of FTA mounting channels that can be accommodated in a control cabinet is
dependent upon whether the cabinet is single access or dual access, and whether standard
or wide vertically orientated FTA mounting channels are installed.
Optionally, galvanically isolated FTAs can be mounted on horizontally oriented FTA
mounting channels.
Vertical FTA Mounting Channels
Vertical FTA mounting channels are available in two sizes, standard and wide, to better
accommodate the amount of process control wiring that connects to the FTAs. The FTA
mounting channels provide both a mounting surface for the FTAs and dual channels
(troughs) to route the IOP to FTA cabling, and the process control wiring.
When standard FTAs are mounted on the FTA mounting channel, the IOP to FTA or
Power Distribution Assembly cabling is routed in the right channel and the process
control wiring is routed in the left channel. The opposite is true when galvanically
isolated FTAs are mounted on the FTA mounting channel because the vertical orientation
of the FTA mounting channel is reversed.
Horizontal FTA Mounting Channels
Horizontal FTA mounting channels can be installed when galvanically isolated FTAs are
mounted in the cabinet. Only galvanically isolated FTAs are mounted on the horizontal
FTA mounting channels. They are approximately 61 centimeters (24 inches) long and up
to eight horizontal FTA mounting channels can be accommodated on one side of the
cabinet.
The IOP to FTA, Power Distribution Assembly, or Marshalling Panel cabling is routed in
the upper channel to the left side of the cabinet, and the process control wiring is routed
in the lower channel to the right side of the cabinet.
PM I/O Component Description
FTA Mounting Channels
680 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Typical cabinet installation
Single vertical FTA mounting channels, mounted adjacently, can be used to accept FTAs
installed in the front lower area of a single access cabinet below an IOP card file and
power system as shown in Figure 2.
A typical cabinet layout of FTA mounting channels and standard FTAs in the rear of a
dual access controller cabinet is shown in Figure 3.




Figure 2 Vertical FTA Mounting Channel Installation Single Access
Cabinet

PM I/O Component Description
FTA Mounting Channels
Release 100 Experion PKS Troubleshooting and Notifications Reference 681
1/03 Honeywell Part I


Figure 3 Typical Vertical FTA Mounting Channel Layout
PM I/O Component Description
FTA Wiring Connection Types
682 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
FTA Wiring Connection Types
Compression or screw terminals available
Most standard FTA types are available with either compression-type or screw-type
terminal connectors. Some exceptions are the 6-inch Analog Output (AO), 6-inch High
Level Analog Input (HLAI), 6-inch Low Level Analog Input Multiplexer (LLMux), and
the 6-inch Digital Input Power Distribution Assembly, which are available with
compression-type terminal connectors only. The Remote Hardened Low Level Analog
Input Multiplexer (RHMUX) is available only with screw-type terminal connectors. The
number of terminals for both the compression-type and screw-type terminal connector
can vary depending on the type of standard FTA.
All galvanically isolated FTAs are available with both crimp pin-type and compression-
type terminal connectors. The Marshalling Panel and Combiner Panel are available only
with screw-type terminals.
PM I/O Component Description
FTA Wiring Connection Types
Release 100 Experion PKS Troubleshooting and Notifications Reference 683
1/03 Honeywell Part I
FTA compression-type terminal connector
The following figure is an illustration of a typical compression-type terminal connector
connection to a standard FTA.



Typical FTA Compression Terminal Connector
PM I/O Component Description
FTA Wiring Connection Types
684 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
FTA fixed screw terminal connector
The following figure illustrates a typical fixed screw-type terminal connector as it would
appear on a standard FTA.



Typical FTA Fixed Screw Terminal Connector
PM I/O Component Description
FTA Wiring Connection Types
Release 100 Experion PKS Troubleshooting and Notifications Reference 685
1/03 Honeywell Part I
FTA removable screw-type connector
The following figure illustrates a typical removable screw-type terminal connector.



Typical FTA Removable Screw Terminal Connector
Galvanic Isolation Module connectors
Crimp pin-type and compression-type terminal connectors are available for the
galvanically isolated FTAs. Terminal connectors on the Galvanic Isolation Modules
have six terminals. Depending on the type of terminal connector, the terminals accept
size 0.3 to 3.5 mm
2
(12 to 22 AWG) wiring.
PM I/O Component Description
FTA Wiring Connection Types
686 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Crimp pin-type terminal connector
The following figure illustrates the crimp pin-type Galvanic Isolation Module terminal
connector.



Crimp-Type Galvanic Isolation Module Terminal Connector
PM I/O Component Description
FTA Wiring Connection Types
Release 100 Experion PKS Troubleshooting and Notifications Reference 687
1/03 Honeywell Part I
Compression-type terminal connector
The following figure illustrates the compression-type Galvanic Isolation Module terminal
connector.



Compression-Type Galvanic Isolation Module Terminal Connector
PM I/O Component Description
Power Systems
688 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Power Systems
The Power Systems for PM I/O provide 24 Vdc power for operation of all controller
chassis, IOP cards, FTAs, a nominal 3.6 Vdc battery output for backup of the IOP
memory circuits, and a nominal 0.25 ampere, 6 Vac output for operation of a LLAI line
frequency noise cancellation clock circuit. There are two types of power systems. They
are listed below.

Power System Type Description
Standard Power System
(Model MU/MC-PSSX04)
Power system with optional redundant
power supply module and battery backup
module.
AC Only Power System (optional)

This power system is intended for use
with an uninterruptible ac power source.
It does not provide a battery backup
option for continuous operation in the
event of a primary power loss.

Standard Power System
The standard power system has many versatile attributes that include:
An optional redundant Power Supply Module (model MU-PSRX04)
Either 120 Vac or 240 Vac input power. A single or dual source of input power
can be connected when the optional redundant power supply module option is
implemented
Single and redundant power supply module failure detection
CMOS memory NiCad battery backup (3.6 Vdc) with failure detection
An optional 48 Vdc Battery Backup Module (model MU-PSRB04) with a
disconnect connector that provides continuous equipment in the event of a
primary power loss
Provides fused ac power for 4 cabinet fan assemblies
48 volt battery backup time duration
The 48 volt battery backup time duration for a redundant control cabinet containing 40
IOPs (40 nonredundant or 20 redundant pairs) is approximately 20 minutes for a fully
charged battery.
PM I/O Component Description
Power Systems
Release 100 Experion PKS Troubleshooting and Notifications Reference 689
1/03 Honeywell Part I
CMOS backup time duration
The following CMOS backup durations are defined for a redundant control cabinet
containing 40 IOPs (40 nonredundant or 20 redundant pairs). The time duration depends
on which type of power system exists in the specific control cabinet.
Standard Power System = 45 hours (uses three C size NiCad batteries)
AC Only power system = 55 hours, with new batteries (use three alkaline batteries)
The current draw of each IOP is almost negligible.
Standard Power System
The following figure illustrates the standard power system configuration. The power
systems connectors, terminal strips, battery and fuse holders are an integral part of the
power system backpanel.
There are twelve 24 Vdc power distribution output connectors, four cabinet fan assembly
power connectors with associated fuse holders, and a NiCad battery holder on the
backpanel. Sets of terminals provide alarm signals (for external alarm mechanisms) from
each power supply module and the CMOS battery backup. The alarm signals are
normally wired in series to a 24 Vdc Digital Input FTA to notify the system when a
power supply module fails.

PM I/O Component Description
Power Systems
690 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03


Standard Power System
AC Only Power System
The AC Only power system offers optional 8- or 16-ampere redundant power supply
modules, but does not offer the optional 48 Vdc battery backup module feature and
rechargeable NiCad CMOS memory backup power. Nonrechargeable alkaline battery
CMOS memory backup power is provided instead.
The following figure illustrates the AC Only power system. The AC Only power system
has eight power distribution output connectors and four fused Cabinet Fan Assembly
power connectors. There are two sets of normally open alarm contacts, each set operated
by a relay, that signal a power supply module failure. The alarm signals are normally
wired in series to a 24 Vdc Digital Input FTA to notify the system when a power supply
PM I/O Component Description
Power Systems
Release 100 Experion PKS Troubleshooting and Notifications Reference 691
1/03 Honeywell Part I
module fails. Two LED indicators, mounted on the AC Only AC/DC Distribution
Assembly, offer a visual indication of a power supply module failure when the LED is
extinguished.



Figure 4 AC Only Power System
PM I/O Component Description
Power Distribution
692 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Power Distribution
Power distribution is illustrated in Figure 5.
AC input power connections are located on the lower left side of the backpanel, behind
the left power supply module, in the standard power system. Primary and redundant
terminals can be wired in parallel from a single power line source, or wired separately
from two power line sources. See Figure 6.



Figure 5 Power Distribution
AC Only Power System ac power
AC input power connections to the AC Only power system are made to the AC Input
terminal strips at the left side of the AC/DC Distribution board as shown in Figure 4.
The upper AC Input terminal strip powers the optional redundant power supply module,
and the lower AC Input terminal strip powers the primary power supply module. The
primary and redundant terminals can be wired in parallel from a single power line source,
or wired separately from two power line sources.
PM I/O Component Description
Power Distribution
Release 100 Experion PKS Troubleshooting and Notifications Reference 693
1/03 Honeywell Part I
Battery Backup Module
The Battery Backup Module used to power the 24 Vdc power supply modules is a 48
Vdc lead acid battery that provides backup power for approximately 25 minutes with a
full charge. The charging circuit is active in both power supply modules whenever ac
power is available to the power supply module(s). At least one power supply module
must be present to allow the battery to supply power to the card files.
48 Volt Battery switch
A 48 Volt Battery switch that is located at the left side of the standard power system
chassis provides a means of preventing the power supply modules from discharging the
battery backup module when ac power is removed from one or both power supply
modules. Placing the switch in the off position disconnects the battery to power supply
module paths.
No battery backup (Standard Power System)
When there is no battery backup, a battery backup failure is reported unless the zero-ohm
resistor jumpers, W1 and W2, located next to the power supply module connectors, are
cut. This is done at the factory before shipping. If a battery backup is later installed, the
connections must be restored. Figure 6 is a view of the standard power system
backpanel.

PM I/O Component Description
Power Distribution
694 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03


Figure 6 Standard Power System Backpanel
CMOS Battery Backup
Depending on the power system configuration, three rechargeable NiCad or three
nonrechargeable alkaline batteries provide a nominal 3.6 Vdc for CMOS memory backup
power. The batteries support all the memory circuits in the IOPs. NiCad batteries are
long-lived, and they are automatically tested periodically. Every 8 seconds the batteries'
output voltage is tested for the proper level, and every 2 hours a load is applied to the
batteries and the voltage level is again tested.
The standard power system uses 3 C size NiCad batteries which provide approximately
45 hours of backup.
PM I/O Component Description
Power Distribution
Release 100 Experion PKS Troubleshooting and Notifications Reference 695
1/03 Honeywell Part I
Standard Power System
Refer to Figure 6 for the location of the CMOS battery backup assembly mating
connector on the backpanel.
The standard power system configuration has NiCad batteries located at the upper left of
the power system chassis backpanel, and the supporting CMOS battery backup assembly
is inserted into a connector at the lower right-hand side of the backpanel. The right
power supply module must be removed to view the assembly. The assembly provides
both charging circuitry and a monitoring circuitry for failure alarm reporting. See Figure
7 for an illustration of the latest version of CMOS battery backup assembly.



Figure 7 CMOS Battery Backup Assembly (Standard Power System)


ATTENTION
A bad batteries alarm occurs when the CMOS batteries are discharged.

AC Only Power System
The AC Only power system uses alkaline batteries which must be replaced frequently.
The three alkaline batteries are located at the center of the AC/DC Distribution Assembly
as shown in Figure 4. No charging circuitry or monitoring circuitry for failure alarm
reporting exists. A new set of batteries will provide approximately 55 hours of backup
time.
PM I/O Component Description
24 Vdc Power Distribution
696 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
24 Vdc Power Distribution
Dual power distribution cables
To improve reliability, redundant 24 Vdc distribution to the card files is always provided
by two power distribution cables.
Standard Power System
The standard power system provides twelve 6-pin connectors located on its backpanel.
This allows a greater flexibility in providing power to IOP card files, Digital Input Power
Distribution Assemblies and Galvanic Isolation Power Distribution Assemblies.
AC Only Power System
The AC Only power system provides eight 6-pin connectors located on the AC/DC
Distribution Assembly that will redundantly power three card files and a Digital Input
Power Distribution Assembly or Galvanic Isolation Power Distribution Assembly.
Typical cabinet power distribution
Figure 8 illustrates the typical 24 Vdc cabinet power distribution to the card files, Digital
Input Power Distribution Assembly, and Galvanic Isolation Power Distribution
Assembly for the various power system configurations.

PM I/O Component Description
24 Vdc Power Distribution
Release 100 Experion PKS Troubleshooting and Notifications Reference 697
1/03 Honeywell Part I


Figure 8 Typical Cabinet 24 Vdc Power Distribution
PM I/O Component Description
Cabinet Fan Assembly
698 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Cabinet Fan Assembly
Fused 0.5 A 120 Vac or 240 Vac power is provided by the power system for cabinet fan
assembly operation.
Up to four cabinet fan assemblies can be powered by the 120 Vac or 240 Vac provided
by the four 3-pin connectors of the standard or AC Only power system configurations.
The connectors and fuses are located at the left side of the standard power system
backpanel (as shown in Figure 6) and at the bottom of the AC Only power system
AC/DC Distribution assembly. See Figure 4.
Optional Cabinet Fan assembly
An optional cabinet fan assembly has an LED indicator that indicates normal operation of
both fans, and an alarm signal, represented by normally open contacts, is available at a
terminal strip, TB1. The contacts are closed when the cabinet fan assembly is operating
normally. The operation of the cabinet fan assembly can be monitored by a 24 Vdc
Digital Input FTA, by providing the alarm 24 Vdc signal source from the FTA and
returning it to the FTA through the alarm contacts.
PM I/O Component Description
LLAI Line Frequency Clock Voltage
Release 100 Experion PKS Troubleshooting and Notifications Reference 699
1/03 Honeywell Part I
LLAI Line Frequency Clock Voltage
The power system provides a nominal 6 Vac half-wave rectified phase reference signal to
the IOP card file assemblies through the power cable. A pluggable solid-state optical
coupler module, U1, on each type of card file backpanel generates this line frequency
phase reference signal. It is located at the bottom right of a 7-slot card file backpanel and
in a similar position on the 15 slot card file. Its 6 Vac output is routed to the Low Level
Analog Input (LLAI) IOPs through power cables and card file backpanels. The signal is
used by the IOPs to improve the common and normal mode noise rejection ratio.
Standard Power System
In the standard power system configuration, the power supply module located at the left
side of the assembly is the source of the line frequency phase reference signal. If the left
power supply module is removed, the LLAI IOPs in the same cabinet will report a Soft
failure and continue to operate, but at lesser degree of accuracy.
AC Only Power System
The line frequency phase reference signal in the AC Only power system configuration is
not dependent upon the presence of the left or right side power supply modules, since a
constant voltage is supplied by the AC/DC Distribution Assembly.
PM I/O Component Description
24 Vdc Fuse Protection
700 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
24 Vdc Fuse Protection
Card file fusing
Fuse protection is provided for the IOP card files. The following protection philosophy
applies for both the 7-Slot and 15-Slot IOP card files.
The individual IOP card and an associated standard FTA are protected by a
common fast-action fuse that is located on the backpanel. The fuse has a 2 A
rating.
In addition to the 2 A protection, each individual IOP card has fast-action 0.5 A
fuse protection that is located on the card. The fast-action 0.5 A fuse is soldered
in place and is not field replaceable. You must replace the IOP card.
A fast-action 2.0 A fuse protects the LLAI optical coupler module on backpanel
U1. It generates the line frequency phase reference signal that is used by LLAI
IOPs.
Fuse removal
A Honeywell designed fusepuller is generally needed for extracting and inserting fuses in
the IOP backpanels because of the restricted space between components. The Honeywell
part number is 51190586-100.
The fusepuller is comprised of three parts; an inner barrel that grasps the fuse, an end cap
that is attached one end of the inner barrel, and an outer barrel in which the inner barrel
moves.
The following extraction and insertion procedures should aid in the use of the fusepuller.
Fuse extraction

Step Action
1 Hold the outer barrel of the fusepuller with the fingers of one hand and
depress the fusepullers end cap with your other hand.
2 Place the protruding end of the inner barrel around the fuse. The fusepuller
must be perpendicular to the backpanel.
3 Release the end cap while still holding the outer barrel.
4 Move the outer barrel towards the backpanel. The greater the movement, the
greater the gripping force will be on the fuse.

PM I/O Component Description
24 Vdc Fuse Protection
Release 100 Experion PKS Troubleshooting and Notifications Reference 701
1/03 Honeywell Part I
Fuse insertion

Step Action
1 Hold the outer barrel of the fusepuller with the fingers of one hand and
depress the the fusepullers end cap with the thumb.
2 Hold the fuse in position with the fingers of your other hand and place the
protruding end of the fusepullers inner barrel around the fuse.
3 Release the end cap while still holding the outer barrel and the fuse.
4 Move the outer barrel towards the fuse. The greater the movement, the
greater the gripping force will be on the fuse.
5 Insert the fuse in its backpanel position by vertically moving the fusepuller
towards from the backpanel. Depress the end cap to release the fuse.

Left 7-Slot Card File Fuse Protection
The following table lists the individual backpanel fuses and their application for the Left
7-Slot card file. The fuse rating is 2 A for fuse locations F1 through F8.
Left 7-Slot Card File Fuse Protection

Fuse Rating Protection Application
F1 2 A fast-action Slot 1 IOP card and associated FTA
F2 2 A fast-action Slot 2 IOP card and associated FTA
F3 2 A fast-action Slot 3 IOP card and associated FTA
F4 2 A fast-action Slot 4 IOP card and associated FTA
F5 2 A fast-action Slot 5 IOP card and associated FTA
F6 2 A fast-action Slot 6 IOP card and associated FTA
F7 2 A fast-action Slot 7 IOP card and associated FTA
F8 2 A fast-action HLAI Optical Coupler Module, U1

PM I/O Component Description
24 Vdc Fuse Protection
702 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Left 7-Slot IOP card file 24 Vdc distribution
The following figure illustrates the 24 Vdc power distribution on the Left 7-Slot IOP card
file backpanel.



Left 7-Slot IOP Card File Backpanel 24 Vdc Distribution
PM I/O Component Description
24 Vdc Fuse Protection
Release 100 Experion PKS Troubleshooting and Notifications Reference 703
1/03 Honeywell Part I
Left 7-Slot card file backpanel fuse locations
The following figure illustrates the locations of the individual fuses on the Left 7-Slot
card file backpanel.



Left 7-Slot Card File Backpanel Fuse Locations
PM I/O Component Description
24 Vdc Fuse Protection
704 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Right 7-Slot Card File Backpanel Fuse Protection
The following table lists the individual backpanel fuses and their application for the
Right 7-Slot card file. The fuse rating is 2 A for fuse locations F1 through F8.
Right 7-Slot Card File Backpanel Fuse Protection

Fuse Rating Protection Application
F1 2 A fast-action Slot 9 IOP card and associated FTA
F2 2 A fast-action Slot 10 IOP card and associated FTA
F3 2 A fast-action Slot 11 IOP card and associated FTA
F4 2 A fast-action Slot 12 IOP card and associated FTA
F5 2 A fast-action Slot 13 IOP card and associated FTA
F6 2 A fast-action Slot 14 IOP card and associated FTA
F7 2 A fast-action Slot 15 IOP card and associated FTA
F8 2 A fast-action HLAI Optical Coupler Module, U1

PM I/O Component Description
24 Vdc Fuse Protection
Release 100 Experion PKS Troubleshooting and Notifications Reference 705
1/03 Honeywell Part I
Right 7-Slot IOP card file 24 Vdc distribution
The following figure illustrates the 24 Vdc power distribution on the Right 7-Slot IOP
card file backpanel.



Right 7-Slot IOP Card File Backpanel 24 Vdc Distribution
PM I/O Component Description
24 Vdc Fuse Protection
706 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Right 7-Slot card file backpanel fuse locations
The following figure illustrates the locations of the individual fuses on the Right 7-Slot
card file backpanel.



Right 7-Slot Card File Backpanel Fuse Locations


15-Slot Card File Backpanel Fuse Protection
Backpanel assembly 51401129, revision B, or later have time-delay 3 A fuse protection
for the IOP card and its associated standard FTA. Assembly 51401406 and 51402599
backpanels, all revisions, have fast-action 2 A fuse card and FTA protection. All card
file backpanel assemblies provide a fast-action 0.5 A fuse for the LLAI optical coupler
module on the backpanel, U1.
The following table lists the individual backpanel fuses and their application for the 15-
Slot card file. The fuse rating is 2 A for fuse locations F1 through F15.
PM I/O Component Description
24 Vdc Fuse Protection
Release 100 Experion PKS Troubleshooting and Notifications Reference 707
1/03 Honeywell Part I
15-Slot Card File Fuse Protection

Fuse Rating Protection Application
F1 2 A fast-action/3 A time-delay Slot 1 IOP card and associated FTA
F2 2 A fast-action/3 A time-delay Slot 2 IOP card and associated FTA
F3 2 A fast-action/3 A time-delay Slot 3 IOP card and associated FTA
F4 2 A fast-action/3 A time-delay Slot 4 IOP card and associated FTA
F5 2 A fast-action/3 A time-delay Slot 5 IOP card and associated FTA
F6 2 A fast-action/3 A time-delay Slot 6 IOP card and associated FTA
F7 2 A fast-action/3 A time-delay Slot 7 IOP card and associated FTA
F8 2 A fast-action/3 A time-delay Slot 8 IOP card and associated FTA
F9 2 A fast-action/3 A time-delay Slot 9 IOP card and associated FTA
F10 2 A fast-action/3 A time-delay Slot 10 IOP card and associated FTA
F11 2 A fast-action/3 A time-delay Slot 11 IOP card and associated FTA
F12 2 A fast-action/3 A time-delay Slot 12 IOP card and associated FTA
F13 2 A fast-action/3 A time-delay Slot 13 IOP card and associated FTA
F14 2 A fast-action/3 A time-delay Slot 14 IOP card and associated FTA
F15 2 A fast-action/3 A time-delay Slot 15 IOP card and associated FTA
F16 0.5 A fast-action LLAI Optical Coupler Module, U1

15-Slot IOP card file 24 Vdc distribution
The following figure illustrates the 24 Vdc power distribution on the 15 slot card file
backpanel.

PM I/O Component Description
24 Vdc Fuse Protection
708 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03


15-Slot Card File Backpanel 24 Vdc Power Distribution
PM I/O Component Description
24 Vdc Fuse Protection
Release 100 Experion PKS Troubleshooting and Notifications Reference 709
1/03 Honeywell Part I
15 Slot card file backpanel fuse locations
The following figure illustrates the locations of the individual fuses on the 15 slot card
file backpanel.



15-Slot Card File Backpanel Fuse Locations
PM I/O Component Description
24 Vdc Fuse Protection
710 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
FTA fuse protection
Some individual FTAs may have fuse protection on the assembly. In general, output
type FTAs are fused, but not exclusively. Fuse information for the individual FTAs can
be found in Appendixes C and D in the Control Hardware Installation Guide.
Cabinet Fan assembly fuse protection
Each Cabinet Fan Assembly is protected by fast-action 0.5 A fuse located on the power
system backpanel assembly. A control cabinet can contain two individually fused Fan
Assemblies. Both the Standard, and AC Only power system configurations provide
fused circuits for four fan assemblies. Refer to Figure 4 for the locations of the Fan
Assembly fuses.
PM I/O Component Description
IOP Card File Power Cabling
Release 100 Experion PKS Troubleshooting and Notifications Reference 711
1/03 Honeywell Part I
IOP Card File Power Cabling
Each IOP card file receives power (24 Vdc, 3.6 Vdc, and 6 Vac) from the power system
through dual cables that connect to the power system. The POWER connectors on the
IOP card file backpanel are listed in the following table.
Card File Power Cabling

Card File Type Dual Power Connectors
7-Slot J20 and J21
15-Slot J46 and J47

Power Distribution assemblies
Digital Input Power Distribution assemblies and Galvanic Isolation Power Distribution
assemblies require 24 Vdc power and require the same type of power cable as the card
files.
Power System power connectors
The standard power system has 12 power output connectors, labeled OUTPUT 1 through
OUTPUT 12. Connectors are not assigned to any particular card file or Power
Distribution assembly. The power output connectors are located at the upper right side of
the backpanel of the standard power system. The AC Only power system power
connectors are located at the right side of its AC/DC Distribution assembly as shown in
Figure 4.
Power cables for IOP
The power cables that are available for use in a PM I/O subsystem have an integrated
surge protection network as part of the cable. The network protects the I/O link
transceivers from power surges when each I/O link interface cable is routed through a
protection network at the card file. For this feature to be effective, all card files in the
subsystem (for example, a subsystem being all the IOP card files that are connected to
the IOLIM through the metallic I/O link interface cable) must have the surge protection
network feature installed. The following figure shows a pair of power cables with the
power surge protection network.

PM I/O Component Description
IOP Card File Power Cabling
712 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03


Figure 9 Power Cable with I/O Link Protectors
PM I/O Component Description
IOP Card File Power Cabling
Release 100 Experion PKS Troubleshooting and Notifications Reference 713
1/03 Honeywell Part I
Fifteen-Slot IOP Card File Backpanel Connections

32772
R7 R9 R11 R13
R12 R10 R8
F6
2 A
F5
2 A
F4
2 A
F3
2 A
F2
2 A
SLOT 1 SLOT 2 SLOT 3 SLOT 4 SLOT 5 SLOT 6 SLOT 7
REDUNDANCY
STATUS OUT
POWER A POWER B
LLAI OPTO
+
_
RESTART IN
J38
F16
2 A
U1
J42 J43
J44 J45
LINK A LINK B
J40
J41
P
R14
P
P 32 16 8 4 2 1 NET
FILE P 2 4 1 +
_
R17
R16
R15
R1
R2
1
2
4
B
A
A B
SHIELD
1
J39
J47 J46
F7
2 A
F1
2 A


Figure 10 Fifteen-Slot IOP Card File Backpanel Connections
Power cables for power distribution assemblies
A pair of power cables supply 24 Vdc from the power system to both Digital Input Power
Distribution Assemblies and Galvanically Isolated Power Distribution Assemblies.
These power cables do not have surge protection. If cables are routed from a cabinet to
an external destination, use the shielded model of the cable. Check your site
documentation for cable models, or see Power cables for IOPs in the Planning Guide for
power cable part numbers for CE compliant and CE non-compliant installations.
Power distribution examples
Figure 11, Figure 12, Figure 13, and Figure 14 illustrate typical power cabling of various
combinations of card files and Power Distribution assemblies using the standard power
system. The AC Only power system cabling would be similar.
PM I/O Component Description
IOP Card File Power Cabling
714 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Power distribution methods
The AC Only power system are limited to eight power output connectors. The eight
connectors provide power for various combinations, depending upon power requirements
of card files, Digital Input Power Distribution assemblies, and Galvanic Isolation Power
Distribution assemblies. Redundant power cabling to each assembly is recommended.
However, an exception must be made when three card files, a Digital Input Power
Distribution assembly, and a Galvanic Isolation Power Distribution assembly are present
in the cabinet, since only eight power output connectors are available. The power cables
are then daisy-chained. See Figure 15.
The standard power system provides 12 power output connectors which eliminates the
need to daisy-chain power from one file to file.
PM I/O Component Description
IOP Card File Power Cabling
Release 100 Experion PKS Troubleshooting and Notifications Reference 715
1/03 Honeywell Part I
15-Slot Card File with Power Distribution Assemblies
The following figure illustrates power cabling for a typical PM I/O configuration of a
single 15-Slot card file and Power Distribution assemblies.



Figure 11 15-Slot Card File with Power Distribution Assemblies
PM I/O Component Description
IOP Card File Power Cabling
716 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Two 15-Slot Card Files with Power Distribution Assemblies
The following figure illustrates power cabling for a typical PM I/O configuration of two
15-Slot card files and two Power Distribution assemblies.



Figure 12 Two 15-Slot Card Files with Power Distribution Assemblies
PM I/O Component Description
IOP Card File Power Cabling
Release 100 Experion PKS Troubleshooting and Notifications Reference 717
1/03 Honeywell Part I
Three 15-Slot Card Files
The following figure illustrates power cabling for a typical PM I/O configuration of three
15-Slot card files.



Figure 13 Three 15-Slot Card Files
PM I/O Component Description
IOP Card File Power Cabling
718 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Three 15-Slot Card Files with Power Distribution Assemblies
The following figure illustrates power cabling for a typical PM I/O configuration of three
15-Slot card files and two Power Distribution assemblies.

PM I/O Component Description
IOP Card File Power Cabling
Release 100 Experion PKS Troubleshooting and Notifications Reference 719
1/03 Honeywell Part I


Figure 14 Three 15-Slot Card Files with Power Distribution Assemblies
PM I/O Component Description
IOP Card File Power Cabling
720 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Power Distribution Assemblies for redundant cabling
AC Only Power Systems are limited to eight power output connectors. The following
figure illustrates how power is distributed when the number of available connectors does
not meet the total need for redundant cabling.

PM I/O Component Description
IOP Card File Power Cabling
Release 100 Experion PKS Troubleshooting and Notifications Reference 721
1/03 Honeywell Part I


Figure 15 Power Distribution Assemblies for redundant cabling
PM I/O Component Description
Installing I/O Interface cable
722 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Installing I/O Interface cable
The I/O Link Interface is a dual serial communications link between IOP card files that
are connected to a common IOLIM. If there is more than one card file, I/O link interface
cables are daisy-chained to all IOP card files associated with the IOLIM. In a redundant
installation, both primary and secondary IOP card files are connected to the IOLIM using
I/O link interface cables. When installing remote I/O, all IOP card files at the local site,
including both primary and secondary IOP card files in a redundant installation, are
connected the IOLIM using the interface cables.
Cabling Requirements
The metallic I/O link interface cable is a three-conductor shielded cable. Up to six IOP
card files and IOLIMs can be connected to one I/O link interface. Since the files are
daisy-chained, the cable should contain the appropriate number of drops (connectors) for
the number of IOP card files and IOLIMs to be connected. See Spare Parts for available
I/O link interface cable types and part numbers. Two cables are provided when ordered
by the part number.
Power cables should be installed first, before the I/O Link interface cabling.
I/O link interface cables are to be no longer than 10 m (33 feet) in total length
and are not to leave the cabinet or cabinet complex.
Two cables are required because the I/O link interface is redundant for
reliability. One cable is designated Link A and the other Link B.
The I/O link interface cabling does not involve external terminators and
therefore an empty I/O link interface connector on the backpanel is an
acceptable situation.



Use caution when connecting the I/O Link Interface cables because
of the differences between the 7-slot and 15-slot IOP card files. All
card files have two I/O link interface connectors marked LINKA and
LINKB.

The following table identifies the I/O link interface connectors on the 7-Slot, 15-Slot,
IOP card file backpanels.
PM I/O Component Description
Installing I/O Interface cable
Release 100 Experion PKS Troubleshooting and Notifications Reference 723
1/03 Honeywell Part I
IOP Card File Connector Assignments for I/O Interface Cables

Card File Type I/O Link A Connector I/O Link B Connector
7-Slot J23 J24
15-Slot J42 J43

Power surge protection for the I/O link interface
An induced power surge of 10 amperes or greater can originate through an FTAs field
connections as a result of a lighting strike and elevate the card file(s) above the common
mode range of the I/O link interface transceivers and cause transceiver failure.
To prevent this occurrence, a power cable was developed with a surge protection network
that filters the power surge on the I/O link interface to the power cables ground before
the I/O link interface connects to the card file.
Figure 9 illustrates a pair of surge protection network power cables and identifying the
connections for both Link A and Link B.
The I/O Link Interface connects to the surge protection network that is an integral part of
the power cable, passes through the filter, and then connects to the card file. The method
of implementing the surge protection is illustrated in Figure 16.
New and upgraded subsystems only
The surge protection network power cable is presently used in new production and newly
upgraded hardware only. However, older hardware can and should be upgraded by the
use of a set of power cable I/O link protector adapters, Honeywell part number
51204127-100. See Spare Parts for available I/O link interface cable types and part
numbers.
I/O Link interface cables in adjacent cabinets
The I/O link interface cable daisy chain can be extended to include additional
intermediate drops. Longer daisy chain runs from card file to card file in one cabinet can
also include card files in an adjacent cabinet. I/O link interface cables with the
appropriate number of drops must be ordered to satisfy your PM I/O subsystem
configuration (number of card files). Refer to Spare Parts for a listing of available cables
types and part numbers.
PM I/O Component Description
Installing I/O Interface cable
724 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
I/O Link interface cable installation
Follow the procedure to install the I/O interface cables IOP card files.
Note that example describes I/O link interface cable installation to 15-slot IOP card files.

Step Action
1 Consult site documentation to locate all IOP card files, both primary and
secondary in a redundant installation, associated with an IOLIM.
2 Connect one end of an I/O interface cable to the surge protection network
connected to LINK A of the IOLIM in the controller chassis.
3 Connect the next I/O interface cable drop (connector) to the surge protection
network connected to J42 (LINK A) of the first IOP card file. The first IOP card
file is usually located closest to the IOLIM or power system. See Figure 16.
4 Connect the I/O interface cable to all other associated IOP card files by
connecting the cable to the surge protection network that is connected to the
LINK A connection of the IOP card file backpanel.
5 Repeat steps 2 through 4 to install the I/O Link interface cable to LINK B of
the IOLIM and all associated IOP card files.
6 Repeat steps 1 through 5 for all remaining IOLIMs and associated IOP card
files in the system.

Typical I/O Link and power cable connection
The following figure illustrates typical surge protection network power cable and I/O
Link Interface cable connections to the Power System and card files in a cabinet.

PM I/O Component Description
Installing I/O Interface cable
Release 100 Experion PKS Troubleshooting and Notifications Reference 725
1/03 Honeywell Part I


Figure 16 Typical Cabinet I/O Link Interface Cable Connections
PM I/O Component Description
Installing I/O Interface cable
726 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
I/O Link Interface cable shield grounding


ATTENTION
The IOLIM in the controller chassis contains jumpers that set I/O interface
cable shield ground. These jumpers are labeled B Shield and A Shield on the
IOLIM daughterboard and should be set accordingly.

For non-CE compliant applications, the cable shield for the I/O link interface cable
should be grounded at only one point along the cable daisy chain. This is normally done
on the backpanel of the first IOP card file (file position 1) in the first control cabinet
(using jumpers on the backpanel).
On a 7-Slot card file, J29 and J22 are located between the I/O link interface
cable connectors. Both the A and B I/O link interface cables have their own
jumper for grounding the cable shield. J29 is for the Link A cable shield and
J22 is for the Link B cable shield. The cable shield is grounded if the jumper is
bridged across both pins.
On the 15-Slot card file, J44 and J45 are located between the I/O link interface
cable connectors and accomplish the same function.
For CE Compliant applications, the I/O link interface cable shield must be grounded
to the card file chassis (Safety Ground) at each connector. This is accomplished with
shield wire that attaches to a FASTON terminal on the card file's backpanel ground
plate. Only cables with a part number of 51204042-xxx can be used.
See Spare Parts for available I/O link interface cable types and part numbers.


ATTENTION
The I/O Link Interface cable shield grounding must be carefully adhered to
when installing a PM I/O subsystem. Failure to follow the above guidelines
can result in unwanted ground loops and abnormal system sensitivity to RFI
and ESD influence from the surrounding environment.

PM I/O Component Description
IOP to FTA Cabling
Release 100 Experion PKS Troubleshooting and Notifications Reference 727
1/03 Honeywell Part I
IOP to FTA Cabling
Each IOP has a cable that connects it to its associated FTA.
Standard FTAs
The cables for standard FTAs leave the FTAs at the top or center, travel up or down the
right side of the vertical FTA mounting channel, go over or under the center divider, and
then connect to the associated IOP card file connector on the 7-Slot or 15-Slot card file
backpanel.
Galvanically Isolated FTAs
When mounted on a horizontal FTA mounting channel, the cables for galvanically
isolated FTAs leave the top side of the FTAs, travel up or down the left side of the
horizontal FTA mounting channel, go over or under the center divider, and then connect
to the associated IOP connector on the 7-Slot or 15-Slot card file backpanel.
Galvanically isolated FTAs can also be mounted on vertical FTA mounting channels.
When they are, the reverse of the cabling rules that apply for the standard FTAs apply for
galvanically isolated FTAs because the vertical orientation of the FTA mounting channel
is reversed.
External cabinet installation
The FTAs can also be installed on a panel that is external to the cabinet, up to 50 meters
(164 feet) cable length from the IOP. Shielded FTA cables must be used whenever the
FTA is located outside of the control cabinet complex. See Remote FTA installation in
the Control Hardware Installation Guide for additional information.
PM I/O Component Description
IOP to FTA Cabling
728 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Typical cable routing
The following figure illustrates typical cable routing for a standard FTA in a cabinet or
cabinet complex.



Figure 17 IOP to FTA Cabinet Cabling
PM I/O Component Description
Power Adapter Cabling
Release 100 Experion PKS Troubleshooting and Notifications Reference 729
1/03 Honeywell Part I
Power Adapter Cabling
Using a standard FTA cable, the model MU-TLPA02 Power Adapter can be located up to
50 meters (164 feet) distance from the card file containing the associated IOP card. The
Power Adapter connects to one or two FTAs that can be installed at a remote location up
to 305 meters (1000 feet) from the Power Adapter. Figure 18 illustrates its application
with a Low Level Multiplexer Analog Input FTA.
LLMux interconnections
The following figure illustrates the Power Adapter interconnections for a Low Level
Multiplexer application.

PM I/O Component Description
Power Adapter Cabling
730 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03


Figure 18 Power Adapter Interconnections LLMux Application
PM I/O Component Description
I/O Link Address Pinning
Release 100 Experion PKS Troubleshooting and Notifications Reference 731
1/03 Honeywell Part I
I/O Link Address Pinning
IOP card file addressing
All IOP card files must be hardware configured (pinned) for an address on the I/O Link
Interface. I/O Link address selection is implemented (pinned) in one of two ways:
Two-pin hardware jumpers, or
Zero-ohm resistors located on each card file backpanel. Zero-ohm resistors that are
used in place of jumpers are soldered in at the factory only by special request
The IOP card file I/O Link addresses must be configured (pinned) consecutively, starting
at I/O Link address 0 (zero). See the following figure for the location of the jumpers on
the 7-Slot IOP card file.



Left 7-Slot Card File I/O Link Address Pinning
PM I/O Component Description
I/O Link Address Pinning
732 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Any I/O card files in the PM I/O subsystem must be addressed consecutively, starting at
I/O Link address 0 (zero). See the following figure for the location of the jumpers on the
15-Slot card file.



15-Slot Card File I/O Link Address Pinning


ATTENTION
The numerical I/O link address displayed on the workstation displays is
numbered one higher (+1) than the actual pinned I/O link address. The I/O
link address of 0 is displayed as a numerical address of 1 on the system
displays. (i.e. pinned value of 0 = card file 1, pinned value of 1 = card file 2,
etc.).

PM I/O Component Description
I/O Link Address Pinning
Release 100 Experion PKS Troubleshooting and Notifications Reference 733
1/03 Honeywell Part I
One method only
Use only one of the two methods to set the I/O link interface address for the IOP card
files. Either remove all jumpers and use the zero-ohm resistors to set the address, or clip
out the zero-ohm resistors and use the jumpers. The jumper method (without the
resistors) is the most common method.


ATTENTION
Whichever method you use, please note that there are four address positions
labeled 1, 2, 4 and P. The "P" position is for parity. It is used so that all I/O
link addresses are set using an odd number of jumpers, (or resistors). See
examples below.

Jumper method example
I/O Link address configuration using plug jumpers is demonstrated with the following
example. Refer to the following figure to locate the 7-slot card file pinning area (J26) for
the following procedure.

Step Action
1 Assume an IOP card file is to be configured for an I/O Link hardware address
of 4.
(The workstation will display this card files I/O Link address as 5.)
2 Take diagonal cutters and remove all the zero-ohm resistors.
3 Install a plug jumper to bridge both pins at position 4.
NOTE: Because this single jumper constitutes an odd number of jumpers,
remove the P (parity) plug jumper as well as all others.

Even though the J-number (J26 in this case) differs between the 7-Slot and 15-Slot card
files, the method of pinning the card file address remains the same.

PM I/O Component Description
I/O Link Address Pinning
734 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03


Left 7-Slot Card File I/O Link Address Pinning with Plug Jumpers
Zero-ohm resistor jumper pinning example
I/O Link address configuration using zero-ohm resistor jumpers is demonstrated with the
following example. Refer to the following figure to locate the 7-slot card file resistor
jumper area for the following procedure.

Step Action
1 Assume an I/O card file is to be configured for an I/O Link hardware address
of 3. (The workstation will display this card files address as 4.)
2 Remove all the plug jumpers and set them aside.
3 Leave the zero-ohm resistors at positions 1 and 2 (1 + 2 = 3), and leave the P
(parity) zero-ohm resistor because an odd number of jumpers is required.
(A logic one is created by leaving the zero-ohm resistor in place and a zero is
created by removing the zero-ohm resistor. )
4 Remove all other zero-ohm resistors with diagonal cutters.

Even though the jack number (J26 in this case) differs between the 7 and 15-Slot card
files, the method of pinning the card file address remains the same.

PM I/O Component Description
I/O Link Address Pinning
Release 100 Experion PKS Troubleshooting and Notifications Reference 735
1/03 Honeywell Part I


Left 7-Slot Card File I/O Link Address Pinning with Zero-Ohm Resistors



If a zero-ohm resistor jumper is incorrectly removed, do not attempt
to correct the problem by resoldering the jumper. The backpanel
can be easily damaged. Instead, remove all the zero-ohm resistor
jumpers and configure the card files I/O Link Interface address with
the plug jumpers

PM I/O Component Description
I/O Link Address Pinning
736 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03

Release 100 Experion PKS Troubleshooting and Notifications Reference 737
1/03 Honeywell Part I
Removal and Replacement of PM I/O Components
ESD Guidelines


ESD HAZARD
It is extremely important that you wear a properly connected Electrostatic
Discharge (ESD) wriststrap while removing, handling, and installing these
Process Manager I/O components. Slip the strap on your wrist like a
wristwatch and connect its clip to the ground bus located inside the left front
side of the cabinet. There is no danger of personnel receiving shocks from
wearing an approved wrist strap. Be sure to place the component in a static-
safe carrying pouch, if appropriate, immediately after its removal.

Static discharge effects
When inserting an IOP card into a card file and following normal ESD procedures, other
cards in the card file can go OFFNET because of electrostatic discharge. It does not
result in damage to any of the components on the card when an ESD wriststrap is worn,
but does affect subsystem integrity. A procedure has been developed to discharge the
card using a 10 megaohms Static Discharge Probe.
ESD kit
Honeywell has available an ESD kit, part number 30185H, that contains the following
components.
10 megaohm static discharge probe
Static discharge wriststrap (AESOPS Inc. Model 31531)
Static discharge cord, 15 feet (AESOPS Inc. Model 30204)
Static discharge cord, 6 feet (AESOPS Inc. Model 30205)
Antistatic work surface with bag
Building a static discharge probe
A static discharge probe can be built by placing a 10 megaohm resistor in series with any
available probe or clip lead.
Removal and Replacement of PM I/O Components
ESD Guidelines
738 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
ESD prevention rules
When installing a firmware upgrade, or replacing or adding a card, adhere to the
following rules to prevent ESD from affecting the IOP cards.
Ground the antistatic work surface to the card file chassis.
Ground the wriststrap that is to be worn when removing or inserting card to the card
file chassis.
Ground the wriststrap that is to be worn when upgrading card firmware to the
antistatic work surface.
When removing or inserting a card, handle only the card frame. Do not touch the
circuit board or the components
The 10 megaohm static discharge probe must be grounded to the card file chassis.
When inserting a card, insert the card 3/4 of the way into the slot and then discharge
the card with the 10 megaohm static discharge probe by touching the lower lead of the
upper LED, or if there is a daughter board, touch the minus/lower lead of the bypass
capacitor labeled C1 or C2.
Removal and Replacement of PM I/O Components
IOP Cards
Release 100 Experion PKS Troubleshooting and Notifications Reference 739
1/03 Honeywell Part I
IOP Cards



Cycling power or removing nonredundant Analog or Digital Output
IOPs results in their outputs going to the nonpowered state
regardless of the FAILOPT selection configured. Follow the Analog
or Digital Standby Manual device instructions in this section.

Replacing IOP cards
Use the following procedure to remove and replace an IOP card.

Step Action
1 Connect your ESD wriststrap to the cabinets ground bar.
2 Before removing an analog or digital output IOP from a card file, system
operational requirements may require that a Standby Manual device be
connected to the FTA to control operations while the IOP is removed.
3 Any IOP card can be removed by simultaneously pulling on the upper and
lower extractor levers. When the upper extractor is first moved, power is
disconnected from the card. Further operation of both extractors moves the
card away from its backpanel connector.
4 After the card is free from the connector, carefully slide it out on the card rails
and into your hands. Immediately place the card in a static-safe pouch for
transport.
5 With your ESD wriststrap still attached, remove the replacement card from its
pouch.
6 Carefully slide the card onto the card rails, checking to be sure that the card
is inserted in both rails.
7 Slide the card into the card file until it has made contact with the backpanel
connectors. Then firmly press on the front of the card with the heel of your
hand. Do not use excessive force! If the card doesn't slip easily into its
connectors, remove the card and locate the source of the obstruction. Check
for bent contacts at the backpanel connectors.

Removal and Replacement of PM I/O Components
Standby Manual Devices
740 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Standby Manual Devices
About devices
A Standby Manual device provides the capability to maintain output signals from an
Analog Output or 24 Vdc Digital Output FTA while its nonredundant IOP is replaced.
An Analog Output IOP to FTA cable can be replaced if an external power source is
connected directly to the Standby Manual device, since the cable is the FTAs normal 24
Vdc source. The IOP switching module on the Analog Output FTA can also be replaced.
No external power source option
The Digital Output Standby Manual device does not have an external power source
option.
Standby Manual device connections
The connection of the Analog Output Standby Manual device and the Digital Output
Standby Manual device to the FTA differs. The Analog Output Standby Manual device
connects by cable to a unique connector on the FTA that is labeled STANDBY
MANUAL. The Digital Output Standby Manual device connects to one of the two IOP
interface connectors as shown in the following figure for a model MU-TDON12 24 Vdc
Digital Output FTA.

Removal and Replacement of PM I/O Components
Standby Manual Devices
Release 100 Experion PKS Troubleshooting and Notifications Reference 741
1/03 Honeywell Part I


Removal and Replacement of PM I/O Components
Standby Manual Devices
742 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Device interchangeability
There is an interchangeability problem with the Digital Output Standby Manual devices.
The software Release 300, or later, model of the Digital Output Standby Manual device
is not compatible with a Release 230, or earlier Digital Output FTA, nor is the Release
230, or earlier, Digital Output Standby Manual device compatible with a software
Release 300, or later, FTA. Software Release 300, or later, devices are identified by
having phone-type cable connectors, while software Release 230, or earlier, devices have
DIN-type cable connectors.
DIN to phone connector adaptor cable
A DIN to phone connector adaptor cable, Honeywell part number 51201561-xxx, where
the suffix xxx is the length of the cable in meters, can be used to interconnect an
incompatible Digital Output Standby Manual device to an FTA, provided the circuit
board inside the Digital Output Standby Manual device is the proper revision as follows.
Digital Standby Manual device with phone connectorPWB 51304451-100, Revision B
Digital Standby Manual device with DIN connectorPWB 51304076-100, Revision C
Board revision level
The 24 Vdc required by the Digital Output Standby Manual device will be missing if the
devices circuit board is not at the listed revision level. The R230 and R300 Analog
Output Standby Manual devices do not have the same problem.
Removal and Replacement of PM I/O Components
AO Standby Manual Device Operation
Release 100 Experion PKS Troubleshooting and Notifications Reference 743
1/03 Honeywell Part I
AO Standby Manual Device Operation
About AOSM device
There are two models of the Analog Output Standby Manual (AOSM) device. Both
models provide the same primary function, which is to control the loads connected to an
Analog Output FTA while its associated Analog Output IOP can be removed from
service and replaced. The Analog Output Standby Manual device connects to the Analog
Output FTA and provides control of any or all eight of the outputs that are normally
controlled by the IOP.
Two models
The original Analog Output Standby Manual device model is not as convenient to use as
the newer compact Analog Output Standby Manual device model which also offers more
features. A description and the use of both models is discussed in the information that
follows.
Original Analog Output Standby Manual device
The original model MU-SMAC01/MU-SMAC02 Analog Output Standby Manual
(AOSM) device, as shown in the following figure, monitors the outputs of an Analog
Output (AO) IOP by displaying its output values on meters as a percentage of the range.
The following figure illustrates one of the two Analog Output Standby Manual device
assemblies that comprise the Analog Output Standby Manual device. When you press
one of the BAL switches on the Analog Output Standby Manual device, the
corresponding meter indicates the IOPs output value. Using the VALVE knob, you
adjust the Analog Output Standby Manual device's output to match the output of the IOP.
Then, you switch control of the FTA output to the Standby Manual device by moving the
mode switch to the MAN position.

Removal and Replacement of PM I/O Components
AO Standby Manual Device Operation
744 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03


Control of FTA outputs
To use an Analog Output Standby Manual device to control the FTA outputs to the field
while an Analog Output IOP or the IOP switching module on a redundant Analog Output
FTA is being replaced, place all of the mode switches on the Standby Manual device to
the position opposite the MAN position after you have duplicated the IOPs outputs.
FTA connection
Connect the Standby Manual device to the STANDBY MANUAL connector on the FTA
with its cable.


ATTENTION
If the FTA cable to be connected to the Standby Manual device has a phone-
type connector, use the adapter cable, Honeywell part number 51201561-xxx
(The suffix xxx represents the length of the cable in meters), to make the
connection.

Removal and Replacement of PM I/O Components
AO Standby Manual Device Operation
Release 100 Experion PKS Troubleshooting and Notifications Reference 745
1/03 Honeywell Part I
Standby Manual device control procedure
Use the following procedure as a typical guide to provide Standby Manual device control
of the FTA field devices.

Step Action
1 In Monitor tab of Control Builder, click Tools->Upload and click Continue to
upload IOP data from the Controller to the Monitor database.
2 Click Tools->Update to Project and click Continue to update IOP data in
Project.
3 For the first output, press the BAL switch and note the IOPs output value.
4 Release the BAL switch and adjust the VALVE knob to make the output of
the AnalogOutput Standby Manual device equal to the output of the IOP.
5 Place the mode switch for this output in the MAN position.
6 Repeat Steps 3 through 5 for all remaining outputs from the IOP.
7 Remove and replace the IOP or switching module, as appropriate, and
proceed to the Normal IOP Control procedure.

Normal IOP control procedure
Use the following procedure to return to normal IOP control of the FTA field devices.

Step Action
1 In Project tab of Control Builder, click applicable IOP icon and click Tools-
>Load to call up the Load Dialog. Click OK to reload the IOP data from
Project.
2 In Monitor tab, open the Control Module containing the strategy that is
controlling the first output channel for the IOP. Put this point in Manual mode.
3 Manually set the output of the first IOP channel to match that of the Analog
Output Standby Manual device.
4 On the Analog Output Standby Manual device, change the mode switch for
this output to the position opposite the MAN position.
5 Return the point controlling the output to its Normal mode and close the
Control Module.
6 Repeat Steps 2 through 5 for all remaining outputs from the IOP.
Removal and Replacement of PM I/O Components
AO Standby Manual Device Operation
746 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Step Action
7 Disconnect the Analog Output Standby Manual device cable from the
STANDBY MANUAL connector on the FTA, if desired.

Compact Analog Output Standby Manual device
The compact Analog Output Standby Manual (AOSM) device display panel, as shown in
the following figure, monitors the outputs of an Analog Output (AO) IOP as well as the
AOSM itself, presenting their output values on the display panel as a percentage of the
range. It can be ordered by Honeywell part number 51401926-100.



Removal and Replacement of PM I/O Components
AO Standby Manual Device Operation
Release 100 Experion PKS Troubleshooting and Notifications Reference 747
1/03 Honeywell Part I
Compact device features
The Analog Output Standby Manual device has the following features.
The Analog Output Standby Manual device will accept the standard IOP to FTA
cables with either DIN or phone type connectors.
The Analog Output Standby Manual device can be powered by any of two methods.
The IOP card file backpanel through its connection to the STANDBY MANUAL
connector on the FTA.
By applying 110 or 220 Vac to connector at the side of the AOSM. The universal
power supply in the AOSM will accept 100 to 240 Vac, 50/60 Hz.
The panel display shows the 4-20 milliamp current levels in a 0% to 100% scale for all
eight IOP outputs as well as the level of all eight AOSM outputs.
The toggle switches are a tamper-proof style that require the operator to lift up on
the bat handle before changing the switch position.
The compact AOSMs output current and the its OUTPUT SOURCE SELECT
switches are disabled when the device is first connected to the FTA, the STANDBY
ENABLE indicator is extinguished, or the cable to the FTA is disconnected.
When the AOSM is enabled by depressing the STANDBY ENABLE switch, the
STANDBY ENABLE indicator is illuminated and the OUTPUT SOURCE
SELECT switch settings are active.
The balancing of the AOSM output values to equal the IOP output values is performed
automatically, either continuously, or by single snapshot action. Balancing in the other
direction, IOP to AOSM, is an operator function.
A DIR/REV switch for each channel flips the display and reverses the INC/DEC
action relative to the actual current level. In the DIR position, 4 mA equals 0% and 20
mA equals 100%. The INC position of the INC/DEC switch will increase current and
the DEC position will decrease current. With the DIR/REV switch in the REV
position, 20 mA equals 0% and 4 mA equals 100%. The INC position of the
INC/DEC switch will decrease current and the DEC position will increase current.
Removal and Replacement of PM I/O Components
AO Standby Manual Device Operation
748 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Compact ASOM device control procedure
Use the procedure in the following table to provide Standby Manual device control of the
FTA field devices.

Step Action
1 In Monitor tab of Control Builder, click Tools->Upload and click Continue to
upload IOP data from the Controller to the Monitor database.
2 Click Tools->Update to Project and click Continue to update IOP data in
Project.
3 Be sure all the OUTPUT SOURCE SELECT switches are in the PM position.
4 Place the DIR/REV switches in the correct position for all eight channels.
5 Connect a standard IOP to FTA cable between the STANDBY MANUAL
connector on the FTA and the AOSM.
6 Verify that all OUTPUT SOURCE SELECT switches are in the PM position.
7 The BALANCE switch has three positions, left (CONT), center (inactive), and
right (PUSH TO BALANCE). Select the left or right position.
CONT Position
In the CONTinuous (left) position, the switch remains toggled and all the
channels with their OUTPUT SOURCE SELECT switch in the PM position will
automatically have their Standby Manual device output level continuously set
equal to the IOP level. Manual INCrement and DECrement control for a
channel is not possible when a channel is in the PM position while the
BALANCE switch is in the CONT position.
PM Position
In the PUSH TO BALANCE (right) position, the position is momentary and all
channels with their OUTPUT SOURCE SELECT switch in the PM position will
automatically have their Standby Manual device output level set equal to the
IOP output level. However, this balance method is a single event and the
switch returns to the center position when it is released. Any subsequent
change in the IOPs output level will not be transferred to the Standby
Manual, but the INCrement and DECrement control for a channel can alter
the Standby Manual devices current level.
8 The STANDBY ENABLE switch can now be pressed. The green LED
illuminates to indicate that the FTA is now ready for control by the Standby
Manual device.
Removal and Replacement of PM I/O Components
AO Standby Manual Device Operation
Release 100 Experion PKS Troubleshooting and Notifications Reference 749
1/03 Honeywell Part I
Step Action
9 Placing any or all of the OUTPUT SOURCE SELECT switches in the MANual
position will automatically place all eight IOP channels in the Standby Manual
mode.
10 When all eight OUTPUT SOURCE SELECT switches are in their MANual
position, the Analog Output IOP can be placed in the Idle state and removed.
11 Replace the IOP and proceed to the Return to normal IOP control procedure.

Return to Normal IOP control procedure
Use the procedure in the following table to return to normal IOP control of the FTA field
devices.

Step Action
1 In Project tab of Control Builder, click applicable IOP icon and click Tools-
>Load to call up the Load Dialog. Click OK to reload the IOP data from
Project.
2 In Monitor tab, open the Control Module containing the strategy that is
controlling the first output channel for the IOP. Put this point in Manual mode.
3 Manually set the output of the first IOP channel to match that of the Analog
Output Standby Manual device.
4 When the output level for first channel matches the output level of the Analog
Output Standby Manual device, place the OUTPUT SOURCE SELECT
switch for the channel in the PM position. The IOP will now be controlling the
channel.
5 Return the point controlling the output to its Normal mode and close the
Control Module.
6 Repeat Steps 2 through 5 for IOP channels 2 through 8.
7 Disconnect the Analog Output Standby Manual device cable from the
STANDBY MANUAL connector on the FTA, if desired.

Removal and Replacement of PM I/O Components
DO Standby Manual Device Operation
750 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
DO Standby Manual Device Operation
About the DOSM device
The primary function of the model MU-SMDC02 or model MU-SMDX02 Digital Output
Standby Manual (DOSM) device is to control Digital Output FTAs while the associated
Digital Output IOP card is serviced. Except in the case of the +24 Vdc nonisolated FTA
which has no relays, the FTAs relays are controlled, not their loads.
Secondary function
A secondary function of the Digital Output Standby Manual device is to indicate the state
of each IOP output (LED on = output on). The LEDs indicate the output state of the IOP
as soon as the connection is made.
Mounting locations
The model MU-SMDX02 Digital Output Standby Manual device can be mounted in an
HPM cabinet on an FTA Mounting Channel. The model MU-SMDC02 Digital Output
Standby Manual device is mounted in a carrying case for portable applications.
Removal and Replacement of PM I/O Components
DO Standby Manual Device Operation
Release 100 Experion PKS Troubleshooting and Notifications Reference 751
1/03 Honeywell Part I
DOSM connection
Connection of the Digital Output Standby Manual device to the FTA Standby connector
is made with a standard IOP to FTA cable. A 3-meter cable is included with the model
MU-SMDC02 Digital Output Standby Manual device that is shown in the following
figure.



Output control switches disablement
The Digital Output Standby Manual devices output control switches are disabled when
the DOSM is first connected to the FTA, or whenever the ENABLE STANDBY switch
on the DOSM is in the OFF position.
Removal and Replacement of PM I/O Components
DO Standby Manual Device Operation
752 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Switch activation
When the ENABLE STANDBY switch is in the ON position, momentary operation of
the ACTIVATE STANDBY switch latches the manual mode of the Digital Output
Standby Manual device and activates the 16 output switches to control the FTA as
discussed below.


ATTENTION
The IOP to FTA cable, from the card file backpanel to the FTA, must be
connected to carry the +24 Vdc and the common from the IOP backpanel to
the FTA and the Digital Output Standby Manual device. Also, the Digital
Output Standby Manual device cannot be used with the 24 Vdc nonisolated
Digital Output FTA if the FTA load voltage for any output is other than +24
Vdc.

DOSM device control procedure
Use the Tools menu commands Upload and Update to Project for the IOP(s) in Monitor
tab of Control Builder, if desired, and then use the following procedure to provide
Standby Manual device control of the FTA field devices.

Step Action
1 Place ENABLE STANDBY switch on the Digital Output Standby Manual
device in the OFF position.
2 Connect the Digital Output Standby Manual device cable to the FTA CABLE
B connector, J2, on the Digital Output FTA.
3 When the Digital Output Standby Manual device is connected to the
connector on the Digital Output FTA, all "on" IOP outputs light their
corresponding indicator on the Digital Output Standby Manual device. The
following figure shows a model MU-SMDX02 Digital Output Standby Manual
device panel. If you only want to display outputs, stop at this Step.
Removal and Replacement of PM I/O Components
DO Standby Manual Device Operation
Release 100 Experion PKS Troubleshooting and Notifications Reference 753
1/03 Honeywell Part I
Step Action



4 If you want to use the Digital Output Standby Manual device to hold the
current FTA output states while servicing the associated Digital Output IOP,
set the 16 output switches equal to the output state that is displayed by the
LEDs on the Digital Output Standby Manual device and perform Steps 5
through 7 below. You can also set any of the 16 output switches to an
alternate state, if desired.
5 Place the ENABLE STANDBY switch on the Digital Output Standby Manual
device in the ON position.
6 Toggle the momentary ACTIVE STANDBY switch on the Digital Output
StandbyManual device. The STANDBY ACTIVATED LED should illuminate.
This allows the Digital Output Standby Manual devices switch settings to
control the Digital Output FTA and also send a status signal to the IOP to
indicate that the connected Digital Output Standby Manual device is armed
and possibly controlling FTA outputs.
Removal and Replacement of PM I/O Components
DO Standby Manual Device Operation
754 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Step Action
7 While the Digital Output Standby Manual device is controlling outputs, the
IOP can be placed in the idle mode or removed/replaced for servicing, and
the FTA outputs will be held by the Digital Output Standby Manual device.
After servicing the IOP, proceed to the DOSM to normal IOP control
procedure to restart the IOP.

DOSM to normal IOP control procedure
After using the Digital Output Standby Manual device to maintain FTA digital output
states while servicing the associated Digital Output IOP, use the following procedure to
return FTA output control to the IOP

Step Action
1 In Project tab of Control Builder, click applicable IOP icon and click Tools-
>Load to call up the Load Dialog. Click OK to reload the IOP data from
Project.
2 In Monitor tab, open the Control Module containing the strategy that is
controlling the first status output (SO) channel for the IOP.
3 Manually set the output of the first SO to match that of the Digital Output
Standby Manual device.
4 Repeat Steps 2 and 3 for the remaining IOP channels.
5 Set the ENABLE STANDBY switch on the Digital Output Standby Manual
device to the OFF position. The STANDBY ACTIVATED LED should be off,
indicating that the Digital Output Standby Manual device is no longer
controlling the FTA digital outputs. Control has been returned exclusively to
the IOP.
6 Remove the Digital Output Standby Manual device connection to the FTA, if
desired.



ATTENTION
When a digital output point indicates Standby Manual mode (STDBYMAN) on
an operating display, such as Group or Detail, the output cannot be changed
using that display. To set the point output to match the Digital Output Standby
Manual device setting, the output point must be set through the applicable
control drawing in Control Builder.

Removal and Replacement of PM I/O Components
IOP Card Case Replacement
Release 100 Experion PKS Troubleshooting and Notifications Reference 755
1/03 Honeywell Part I
IOP Card Case Replacement
Handling and installing IOP components


ESD HAZARD
It is extremely important that you wear a properly connected Electrostatic
Discharge (ESD) wrist strap while removing, handling, and installing these
IOP components.

Replacing plastic case
Use the following procedure to replace the plastic case on a card assembly.

Step Action
1 Remove the card assembly from the card file. Place the card on a static free
work surface.
2 Remove the two screws at the corners near the connector edge of the card
as illustrated in the following figure.

Removal and Replacement of PM I/O Components
IOP Card Case Replacement
756 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Step Action


3 Lift the connector end of the card to approximate 30 degree angle with the
case.
4 Lift the card from the plastic pins at the front left corners of the circuit board. If
the card has a daughter board attached, the plastic pins are hidden under the
daughter circuit board.
Removal and Replacement of PM I/O Components
IOP Card Case Replacement
Release 100 Experion PKS Troubleshooting and Notifications Reference 757
1/03 Honeywell Part I
Step Action
5 To insert the card in the new case, place the front of the card on the plastic
pins while holding the card at approximately a 30 degree angle. If a daughter
board is attached, the two alignment studs at the front edge of the case must
fit between the two circuit boards. See the figure above after Step 2.
6 Lay the card flat on the work surface and replace the two screws removed in
Step 2.
7 Check the alignment of the LEDs with the openings in the front of the plastic
case for visibility.
8 Reinstall the card in the card file.

Removal and Replacement of PM I/O Components
IOP to FTA Cable Replacement
758 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
IOP to FTA Cable Replacement
Nonredundant IOP cable replacement
All outputs or inputs carried by the IOP to FTA cable, as well as 24 Vdc from the IOP
that powers the FTA, will be disconnected when the cable is removed. The use of an
Analog Output or Digital Output Standby Manual device may be appropriate to maintain
the present outputs of an output type FTA. See one of these previous sections for more
information.
AO Standby Manual Device Operation
DO Standby Manual Device Operation
Redundant IOP cable replacement
Before removing an IOP to FTA cable from a redundant IOP configuration, be sure that
the FTA cable to be removed is not controlling analog output field terminals on the FTA
or providing inputs. When the green DS1 LED on an AO redundancy FTA is illuminated,
the B FTA cable can be removed, since the A FTA cable is controlling the FTA
output field terminals. When the green DS1 LED on an AO redundancy FTA is not
illuminated, the A FTA cable can be removed, since the B FTA cable is controlling
the FTA output field terminals. The IOP forms in the Monitor tab can also be used to
determine whether the A or B FTA cable is controlling the FTA output field
terminals.
For critical analog outputs, it is recommended that the A AO IOP be removed before
the A FTA cable is removed. It is also recommended that the B AO IOP be removed
before the B FTA cable is removed.
When removing FTA cables from High Level Analog Input (HLAI) IOPs, use the IOP
configuration forms in Monitor mode to determine whether or not the cable being
removed is being used to provide subsystem inputs.
Removal and Replacement of PM I/O Components
IOP to FTA Cable Replacement
Release 100 Experion PKS Troubleshooting and Notifications Reference 759
1/03 Honeywell Part I
FTA Replacement
Use the following procedure to replace an FTA.


ATTENTION
Remove power from the FTA by unplugging the IOP to FTA cable before
disconnecting the process wiring.


Step Action
1 Unplug the cable(s) from the associated IOP card connector to the FTA at the
FTA. Remove the field power serving the FTA to be replaced. Unplug the
field wiring terminal-strip from the FTA. It is not necessary to unscrew the
field wiring if compression terminals are used.
2 Remove the screws that hold the FTA to the mounting channel. Carefully
remove the FTA.
3 Compare the replacement FTA with the removed FTA. Be sure any 250 ohm
or zero-ohm resistors that have been clipped on the removed FTA are also
clipped on the replacement FTA. Be sure all fuses are in place and jumpers
are properly positioned.
4 Install the replacement FTA with the screws that were removed in step 2.
Rotate them counterclockwise until they fall into the original threads, then
tighten them clockwise. Reconnect the field wiring terminal connector and
the cable from the associated IOP card(s).

Removal and Replacement of PM I/O Components
FTA Module and Relay Replacement
760 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
FTA Module and Relay Replacement
Replacing FTA Module or Relay
Modules and relays plug into the FTA circuit boards and are held in place by a retaining
screw(s). Usethe following procedure to replace a module or relay.


SHOCK HAZARD
Risk of electric shock exists, whem removing and replacing a FTA module or
relay.


Step Action
1 Remove the screw(s) holding the module or relay to the circuit board and
then firmly lift it straight away until it is free.
2 Align the replacement module or relay with the holes and connector on the
FTA circuit board before inserting it. Replace the retaining screw(s).

LLAI Module replacement
The LLAI plug-in module can be replaced while power is applied to the FTA. After
replacement, power initialize the LLAI IOP. The initialization will initiate a background
diagnostics. Allow at least two (2) minutes for it to complete before analyzing the results.
AO redundancy switching module replacement
Before removing the Analog Output (AO) Redundancy Switching Module from an AO
Redundancy FTA for testing or replacement, be sure that the associated A AO IOP is
controlling the FTA outputs. When the green DS1 LED on the FTA is illuminated, the
associated A AO IOP is controlling the FTAs output. The HPM Status display at the
Universal Station also can also be used to determine if the A AO IOP is controlling the
FTA output.
For critical analog outputs, it is recommended that the B AO IOP be removed, or an
Analog Output Standby Manual device be connected before removing the Analog Output
Redundancy Switching Module.
Removal and Replacement of PM I/O Components
Card File Replacement
Release 100 Experion PKS Troubleshooting and Notifications Reference 761
1/03 Honeywell Part I
Galvanic isolation module replacement
If the field device, controlled by a Galvanic Isolation Module that must be replaced, is an
output device, be sure the loss of control is acceptable. Also, when the environment is
Division 2, be sure the atmosphere is nonhazardous. The module can be removed and
replaced while power is applied to the FTA. Remove the modules pluggable field
connector. Loosen the screws that retain the module. Lift the module from its connector
on the FTA and replace it. Reinstall the pluggable field connector.

Removal and Replacement of PM I/O Components
Card File Replacement
762 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Card File Replacement
Replacing card file
Use the following procedure to replace a card file.

Step Action
1 Disconnect all cables attached to the card file.
2 Remove the side plates connecting the card file to the card file above and/or
below by first removing the two screws at the inside of the panel.
3 Loosen, but do not remove, the four screws holding the card file to its
supports.
4 Grasp the card file firmly and lift it about 1 cm (1/2 inch) to release the card
file into your hands.
5 Install the replacement card file in a reverse manner, making sure it is
engaged by all four mounting screws. Tighten the screws when the card file is
in place. Reconnect the cables that were disconnected in Step 1.

Removal and Replacement of PM I/O Components
Power System
Release 100 Experion PKS Troubleshooting and Notifications Reference 763
1/03 Honeywell Part I
Power System
About the power system
The sections that follow describe the removal and replacement of major assemblies in the
PowerSystem.
If all options are installed, most of the major assemblies in the Power System can be
removed and replaced while the HPM remains in operation because of Power Supply
Module redundancy and battery backup power. Observe all precautions mentioned in this
text when replacing the Power System components.


CAUTION
Batteries may contain toxic materials that are not biodegradable. Batteries
should be disposed of safely in accordance with local laws and regulations.

Removal and Replacement of PM I/O Components
CMOS Battery Replacement
764 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
CMOS Battery Replacement
NiCad batteries
The three NiCad batteries that are installed in the Standard Power System to provide
standby power for the CMOS memory have a tendency to age over a period of time.
Aging occurs even if the batteries have been regularly recharged throughout their
lifetime. For this reason, the NiCad batteries should be replaced after every two years of
operation.
Replacing NiCad batteries
Use the following procedure to replace the NICad batteries.

Step Action
1 Remove the old batteries from the battery holder and replace them with fresh
ones. It is not necessary to remove power from the batteries while they are
being replaced.
2 Observe and match the polarity marked on the case of each battery and the
holder. After all the batteries are in place, rotate each one slightly with your
finger to assure it makes good contact with the holder.

Alkaline batteries
The alkaline batteries that are installed in the AC Only Power System are not
rechargeable and, therefore, must be replaced more often. A six month replacement cycle
is suggested, unless an equipment power failure has occurred for a prolonged period.
Then, the batteries should be replaced.
Removal and Replacement of PM I/O Components
48 V Backup Battery Replacement
Release 100 Experion PKS Troubleshooting and Notifications Reference 765
1/03 Honeywell Part I
48 V Backup Battery Replacement
Battery operational and service life
The lead acid batteries provide 20 minutes of standby power for the HPM Power System
and have a normal stand-by service life of 4 to 5 years. However, usage and high
environmental temperatures will reduce the service life. For this reason, environmental
temperature, battery storage time, and battery usage should be monitored and recorded.
In the absence of this attention, it is recommended the battery performance be checked on
a yearly basis, or be replaced every 3 years to insure proper performance.
Battery performance
All batteries of the same capacity, rating, and specifications, do not provide equivalent
performance or reliability. For optimum system backup realization, use only Honeywell
recommended and approved batteries.
48 V Battery Pack end-of-life
The battery end-of-life is defined as the time when the battery capacity, meaning its
ability to accept and hold a charge, has decayed to 60% of the original capacity. There
are several factors that determine useful service life. The standby service life is reduced
by events other than a continual 20 degrees C standby condition and are defined as
follows.
Standby (float) service life means that the batteries are connected to a charger and only
occasionally discharged. Honeywell 48-volt batteries are designed to operate in
standby (float) service for 4 to 5 years at 20 degrees C. The service life of a battery can
be shortened by an improper charging voltage. The charging voltage from the Power
Supplies should be checked every 6 months for the proper voltage level. See the
following Power Supply Module section for the recommended procedure.
As shipped from Honeywell, the batteries are fully charged. However, if a system is
stored in a nonpowered state, the batteries will self-discharge and can become
unusable. The time required for this to happen is a function of storage temperature.
Removal and Replacement of PM I/O Components
48 V Backup Battery Replacement
766 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03

If Storage Temperature is . . . Then, Self-Discharge Time is . . .
0 degrees to 20 degrees C
(32 degrees to 68 degrees F)
12 months
21 degrees to 30 degreesC
(69 degrees to 86 degrees F)
9 months
31 degrees to 40 degreesC
(87 degrees to 104 degrees F)
5 months
41 degrees to 50 degreesC
105 degrees to 122 degrees F)
2.5 months

Batteries should not be left in a discharged condition for extended periods of time, as
this strongly affects the ability of the battery to accept a charge thereafter. The
batteries should be charged periodically if they are stored or in an nonpowered system.
The IOP provides proper charging current to the batteries while the subsystem is
powered up and running. Whenever ac power is removed from the subsystem, the
Power System automatically draws power from the batteries to maintain the
subsystems 24 Vdc power. Anytime the system is intentionally shutdown and left
nonpowered, the BATTERY switch at the front of the Power System assembly should
be placed in the OFF position to prevent discharge of the batteries.
Service life is directly reduced by high ambient temperature. Heat destroys batteries.
While the operating temperature range is -15 degrees C to 50 degrees C (5 degrees to
122 degrees F), maximum service life will be realized when the batteries are operated
in an ambient of 20 degrees C (68 degrees F). Brief usage, that is, a few days, at higher
temperatures will have no adverse effect on the service life. However, if such usage is
over extended periods of time or occurs repetitively (such as a environment that is not
air-conditioned), the service life will be reduced. This reduction may be as much as
20% of service life (1 year) for each 10 degrees C above the reference ambient of 20
degrees C (68 degrees F).
Removal and Replacement of PM I/O Components
48 V Backup Battery Replacement
Release 100 Experion PKS Troubleshooting and Notifications Reference 767
1/03 Honeywell Part I
48 V Battery Pack service life
Service life is reduced by the number of discharges and the depth of each discharge.
The batteries can provide 200 cycles at 100% depth of discharge, 550 cycles at 50%
depth of discharge, 1200 cycles at 30% depth of discharge, or 2000 cycles at 10%
depth of discharge. This effect is superimposed on the standby aging effect stated
above.
With an expected 5 year life, 200 cycles would represent one power outage
approximately every 9 days, or approximately 2000 ampere-hours of 24 Vdc
subsystem backup.
Battery charge voltage check procedure
Use the following procedure to verify that the output voltage to the 48 Volt Battery Pack
is proper.

Step Action
1 Locate the test points marked "COMMON" (-) and "BATTERY" (+) at the
front of the primary Power Supply Module and connect a dc voltmeter with an
accuracy of +/- 0.05 volts across the test points.
2 The voltage should read between 54.0 volts minimum to 55.2 volts maximum
at 20 degrees C. For each degree the battery enclosure temperature deviates
from 20 degrees C, the following adjustments in Power Supply Modules
battery charge output voltage are applicable.
Above 20 degrees C, the battery charge voltage limits are decreased by 72
mv/deg C.
Below 20 degrees C, the battery charge voltage limits are increased by 72
mv/deg C.
If the charge voltage is outside of these limits, replace the module.

ATTENTION
Step 3 and step 5 should be performed during plant shutdowns, since it
requires disconnecting the battery pack and placing the redundant Power
Supply Modules power switch in the OFF position.
3 Disconnect the battery pack. With the voltmeter connected to the primary
Power Supply Modules battery test points, place the redundant Power
Supply Modules power switch in the OFF position. The voltage should not fall
below the minimum voltage specified in Step 2. If it does, replace the
redundant Power Supply Module.
Removal and Replacement of PM I/O Components
48 V Backup Battery Replacement
768 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Step Action
4 Place the redundant Power Supply Modules power switch in the ON position.
Move the test leads to the battery test points on the redundant Power Supply
Module and place the primary Power Supply Modules power switch in the
OFF position. The voltage should not fall below the minimum voltage
specified in step 3. If it does, replace the redundant Power Supply Module.
5 Reconnect the battery pack to the Power System.

End of Battery Pack life check
The battery pack can be checked for the end of its life by using the procedure in the
following table.

Step Action
1 Set the BATTERY switch on the power system control panel in the OFF
position. Remove the Power Systems lower cover. You can use either a
screwdriver or a coin to remove the two screws holding it in place.
2 Release the Power System cord connector at the battery.
3 Disconnect the battery pack from the subsystem.
4 Attach two pairs of leads to the battery pack terminals. One pair of leads are
for attaching a load resistor and must be a minimum of 1.0 mm 2 (18 AWG)
wire. The second pair are for attaching a voltmeter and can be a smaller
gauge.
5 Select a voltmeter range of 60 Vdc for monitoring the battery voltage. Attach
the voltmeter to the smaller gauge leads.
6 The battery load for the test must be 5 ohms and rated at 500 watts. Five 1-
ohm, 100-watt resistors placed in series is recommended.
7 Attach the resistors to the larger test leads. Note the time of attachment.
8 The battery voltage must remain above 40 Vdc for a minimum of 20 minutes.
If the battery voltage is not maintained, the battery is considered at the end of
its life and must be replaced.
9 All batteries of the same capacity, rating, and specifications, do not provide
equivalent performance or reliability. For optimum battery backup
performance, use only Honeywell recommended and approved batteries.

Removal and Replacement of PM I/O Components
48 V Backup Battery Replacement
Release 100 Experion PKS Troubleshooting and Notifications Reference 769
1/03 Honeywell Part I
Battery pack removal
Use the procedure in the following table to remove the battery pack.


ATTENTION
Using the following procedure will cause alarms to go off, so be sure to notify
Plant Operations in advance that alarms will occur.


Step Action
1 Set the BATTERY switch on the power system control panel to the OFF
position. Remove the Power Systems lower cover. You can use either a
screwdriver or a coin to remove the two screws holding it in place.
2 Release the Power System cord connector at the battery.
3 Remove two screws holding the front lip of the battery pack to the base of the
Power system chassis.
4 Move the Power System cord out of the way so it will not be damaged when
the battery pack is removed.
5 Slowly slide the battery pack out into your hands, but be careful, the pack is
heavy. Go to the next section Battery Pack installation.

Removal and Replacement of PM I/O Components
48 V Backup Battery Replacement
770 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Battery Pack installation
Use the procedure in the following table to install a Battery Pack.

Step Action
1 Slide the new battery pack into the Power System chassis, being careful not
to damage the battery pack connector cord within the compartment.
2 Secure the pack by replacing the two screws through the front lip of the pack
into the base of the chassis.
3 Connect the pack to the system by inserting the polarized battery pack plug
into the polarized connector cord in the compartment. Carefully dress the
cord and connectors to prevent damage.
4 Replace the metal cover.
5 Apply power to the battery by switching the BATTERY switch to the on
position. Unless it is already in a charged condition, the battery pack may
need to be initially charged for 16 hours before it will be capable of sustaining
power to the system.

Removal and Replacement of PM I/O Components
Power Supply Module Replacement
Release 100 Experion PKS Troubleshooting and Notifications Reference 771
1/03 Honeywell Part I
Power Supply Module Replacement
Replacing power supply module
Use the procedure in the following table to replace a Power Supply Module. The
procedure assumes that redundant Power Supply Modules are in use.



If the system is operational, do not remove both Power Supply
Modules at the same time. The batteries will not power the system
unless at least one Power Supply Module is present. If one of the
Power Supply Modules fails, the batteries will not be drained.



ATTENTION
Provided the optional redundant Power Supply Module is installed, the
HPM will remain in operation while replacing a Power Supply Module. Be
sure to notify Plant Operations that you will cause alarms during the
replacement process.
If the primary (left side) Power Supply Module is removed from the system
or turned off, the 6 Vac is not provided to the card files because the
redundant Power Supply Module does not provide 6 Vac. This can cause a
Soft Failure Alarm Notification for any LLAI card that is present.


Step Action
1 If the Power Supply Modules have ac present (AC In LED on), the BATTERY
switch can be placed in the OFF position. Place the BATTERY switch in the
OFF position before removing the Power Supply Module. Set the recessed
toggle switch on one, and only one, Power Supply Module in the down (OFF)
position. Remove two screws at the bottom of the module that hold it to the
shelf of the Power System chassis.
2 Pull the Power Supply Module straight out of the housing.
3 Before installing the replacement Power Supply Module, be sure the
recessed toggle switch is in the OFF position.
4 Carefully slide the replacement module into the Power System chassis. Dont
slam it into its housing. Be careful and be sure that the contacts at the back of
the module mate properly with the fixed contacts at the back of the Power
System backpanel.
Removal and Replacement of PM I/O Components
Power Supply Module Replacement
772 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Step Action
5 Secure the replacement module with two screws at the bottom of the module,
then set the recessed toggle switch to the ON position. Check that the green
indicators on the supply are operating satisfactorily and that alarms can be
reset.
6 Place the BATTERY switch in the ON position.

Removal and Replacement of PM I/O Components
CMOS Backup Assembly Replacement
Release 100 Experion PKS Troubleshooting and Notifications Reference 773
1/03 Honeywell Part I
CMOS Backup Assembly Replacement
About CMOS Backup Assembly
Replacement of the CMOS Backup Assembly requires the removal of the redundant
(right side) Power Supply Module. See the previous section for removal of the Power
Supply Module.
The following figure shows the CMOS Battery Backup assembly.



Removal and Replacement of PM I/O Components
CMOS Backup Assembly Replacement
774 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
The following figure shows the layout of the Standard Power System backpanel with the
location of the CMOS Battery Backup assembly connector.



Replacing CMOS Backup Assembly
Use the procedure in the following table to replace the CMOS Backup assembly.

Step Action
1 Remove the screw located at the front middle of the CMOS Backup
Assembly.
2 Extract the circuit board from the Power System backpanel assembly.
3 Insert the replacement circuit board in the connector on the Power System
backpanel assembly and fasten the screw.

Removal and Replacement of PM I/O Components
Cabinet
Release 100 Experion PKS Troubleshooting and Notifications Reference 775
1/03 Honeywell Part I
Cabinet
Removing Markhon cabinet side panels
To remove the cabinet side panels, either for cabinet complexing or for service
requirements, remove the two external Phillips screws, lift up on the side panel
approximately 1 to 2 inches, and pull the panel outwardly. If the panel does not release,
additional lifting of the panel may be required.
Removing Rittal cabinet side panels
To remove the cabinet side panels, either for cabinet complexing or for service
requirements, remove the six internal Phillips screws, lift up on the side panel
approximately 1 to 2 inches, and pull the panel outwardly. If the panel does not release,
additional lifting of the panel may be required.
Removal and Replacement of PM I/O Components
I/O Link Extender Optical Coupler Module Replacement
776 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
I/O Link Extender Optical Coupler Module Replacement
Replacement procedures
There are two replacement procedures. They depend upon whether the Fiber Optic
Coupler module is mounted in a non-CE Compliant card file or a CE Compliant card file.
The CE Compliant card file requires an adapter kit because of the IOP connector ground
plate.
Select the appropriate procedure from the two procedures that follow.


ATTENTION
Before removing a defective fiber Optical Coupler module, it is necessary to
remove its associated I/O Link Extender card to prevent the transmission of
erroneous signals on the I/O Link..

Replacing coupler in Non-CE Compliant card file
Use the procedure in the following table to replace the I/O Link Extender Coupler when
it is installed in a non-CE Compliant card file.

Step Action
1 Grasp the upper and lower extractors on the I/O Link Extender card and pull
them outward in unison. Move the card toward you until the card is
disengaged from the card file backpanel connector. It is not necessary to
remove the card from the card file.
2 Disconnect the fiber optic cables from the Fiber Optic Coupler module. Be
sure the cables are properly labeled.
3 Using a screwdriver with a small blade, loosen the two screws that secure the
Fiber Optic Coupler module to the backpanel connector. Grasp the module
firmly in your hand and pull it towards you. Place the module on an antistatic
surface or in an antistatic container.
4 Replace the defective module by reversing Step 3.
5 Reconnect the fiber optic cables to the module.
6 Reinstall the I/O Link Extender card by reversing Step 1.
Removal and Replacement of PM I/O Components
I/O Link Extender Optical Coupler Module Replacement
Release 100 Experion PKS Troubleshooting and Notifications Reference 777
1/03 Honeywell Part I
Step Action
7 When you replace a Standard I/O Link Extender Fiber Optic Coupler module,
you must initialize both ends of the link(s) by manually resetting the I/O Link
Extender cards using the upper card extractor on the card. When a Long
Distance I/O Link Extender Fiber Optic Coupler module is replaced,
reinstalling either I/O Link Extender card produces initialization at both ends
of the link.

Replacing coupler in CE Compliant card file
Use the procedure in the following table to replace the Fiber Optic Coupler module when
the coupler is installed in a CE Compliant card file.

Step Action
1 Grasp the upper and lower extractors on the I/O Link Extender card and pull
them outward in unison. Move the card toward you until the card is
disengaged from the card file backpanel connector. It is not necessary to
remove the card from the card file.
2 Disconnect the fiber optic cables from the Fiber Optic Coupler module. Be
sure the cables are properly labeled.
3 Using a screwdriver with a small blade, loosen the two screws that
secure the fiber optic coupler to the backpanel connector. Grasp the
module firmly in your hand and pull it towards you.
The adapter connector that is between the Fiber Optic Coupler module
and the backpanel connector may remain in place in the backpanel
connector or disengage with the module. See the following figure for an
illustration of the Fiber Optic Coupler module components.
Remove the adapter connector from the module and place the module
on an antistatic surface or in an antistatic container.
Removal and Replacement of PM I/O Components
I/O Link Extender Optical Coupler Module Replacement
778 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Step Action



4 Replace the defective module by reversing Step 3.
5 Reconnect the fiber optic cables to the module.
6 Reinstall the I/O Link Extender card by reversing Step 1.
7 When you replace a Standard I/O Link Extender Fiber Optic Coupler module,
you must initialize both ends of the link(s) by manually resetting the I/O Link
Extender cards using the upper card extractor on the card. When a Long
Distance I/O Link Extender Fiber Optic Coupler module is replaced,
reinstalling either I/O Link Extender card produces initialization at both ends
of the link.


Release 100 Experion PKS Troubleshooting and Notifications Reference 779
1/03 Honeywell Part I
IOP Calibration Procedures
Overview
Introduction
This section describes the calibration procedures used to calibrate the Process Manager
I/O Input/Output Processors (IOPs).


SHOCK HAZARD
Calibration may require access to hazardous live circuits and should only be
performed by a qualified service person. More than one switch may be
required to deenergize units before calibration.

No manual adjustments
There are no manual adjustments, such as Power Supply Module settings in the IOP
cabinet. However, there are some semiautomatic calibration procedures for the Low
Level Analog Input (LLAI), High Level Analog Input (HLAI), and Analog Output (AO)
subsystems that may be required periodically.



Do not attempt recalibration without the proper equipment and a
working knowledge of the equipment.

IOP Calibration Procedures
LLAI, HLAI, and AO IOP Calibration
780 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
LLAI, HLAI, and AO IOP Calibration
Introduction to common calibration procedures
Each LLAI, AO, and HLAI subsystem maintains on-board calibration constants for each
analog channel that is stored in nonvolatile memory. Field calibration can probably be an
annual event or more often during a plant or unit shutdown, if necessary.
IOP or FTA substitution
If you suspect that an IOP or FTA is out of calibration, we recommend substitution of the
component instead of recalibrating the IOP or FTA with an on-line Controller.
Precision Test Equipment Requirements
You will need precision equipment to accurately recalibrate these subsystems. The
following table lists typical precision test equipment that you can use.

Item Tolerance Vendor Model
Programmable Voltage
Source: (with 10 V and 100
mV range)
(For precision simulation of
thermocouple inputs)
(0.002% setting
+.0005% range +3 V )

Electronic
Development Co.
11 Hamlin Street
Boston, MA 02127
501 J1
(with option
D)
Precision Resistors:
100 ohm
500 ohm
2000 ohm
(For precision simulation of
RTD inputs)

0.005%
0.005%
0.005%
C. T. Gamble605
Perkins Lane
Delanco, NJ 08075
1608AL or
1608PC for
each
Digital Multimeter with 10 V
range (1 V/count) and 100
mV range (0.1 V/count)
(For accurate calibration
value measurements)
0.0025 reading + 40
counts

John Fluke Mfg. Co.,
Inc.
PO Box C9090
Everett, WA 98206
8505A

IOP Calibration Procedures
LLAI IOP Calibration Procedure
Release 100 Experion PKS Troubleshooting and Notifications Reference 781
1/03 Honeywell Part I
LLAI IOP Calibration Procedure


SHOCK HAZARD
Calibration may require access to hazardous live circuits and should only be
performed by a qualified service person. More than one switch may be
required to deenergize units before calibration.

Seven ranges
The Low Level Analog Input has seven different ranges that require calibration on a per
slot basis, and a special range type for its reference junction calibration. At any one time,
only one of the given gain ranges is being used by a given slot. Each range usage is
independent from another slots usage (for example, performing a calibration for one
range does not affect the calibration constants of another range).
Calibration affects eight slots
Although the LLAI performs calibration on an individual slot basis, only calibration
affecting all eight slots can be performed.
Range type selection
Calibration of a slot assumes that the range type selected is applied to the slot. The range
type is internally derived from the slots current configuration of sensor type
(SENSRTYP), PV character (PVCHAR), and thermocouple range option (TCRNGOPT
for a thermocouple input).


ATTENTION
The user is responsible for reconfiguration of the slots so that the input
voltage or resistor applied to each channel is appropriate for the
configuration. Any violation, due to a configuration mismatch during
calibration, will result in calibration abort errors.




Although mixed ranges of calibration are allowed, never configure
slot 1 as an RTD input if there is at least one slot configured for a
thermocouple. This is because the reference junction for a
thermocouple input is connected to slot 1.

IOP Calibration Procedures
LLAI IOP Calibration Procedure
782 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Select RTD or TC calibration
When performing RTD calibration, all eight points must be configured as RTD. The
same is true when performing thermocouple calibration. All eight points must be
configured as thermocouple.



When performing the following calibration sequences, be sure to use
only high-quality solid copper wire for all the wire jumpers and
voltage source wires to the FTAs inputs. Failure to use high-quality
solid copper wire can result in calibration errors and reduced
accuracy.
An excellent source of high-quality solid copper wire is the copper
wire conductor of type-T thermocouple wire (usually color-coded
blue).

Procedure
Use the following procedure as a guide for calibrating a Low Level Analog Input IOP.


ATTENTION
Each LLAI IOP card and FTA has been calibrated at the factory for all input
types. If recalibration must be performed in the field, power must be applied
to the LLAI for at least 30 minutes for temperature stabilization before starting
the calibration. The calibration procedure calibrates all channels on one FTA
simultaneously, rather than each channel singularly.


Step Action
1 Put the IOP card in its IDLE state through the Execution State command on
its configuration form in the Monitor tab of Control Builder or the Station Detail
display.
2 If the FTA has screw terminal strips, temporarily remove the plastic cover.
Remove the field wiring from the FTA and substitute "zero input" sources for
all channels. These inputs are short copper wire jumpers across the input
terminals. Use the appropriate figure that follows for reference.
IOP Calibration Procedures
LLAI IOP Calibration Procedure
Release 100 Experion PKS Troubleshooting and Notifications Reference 783
1/03 Honeywell Part I
Step Action






IOP Calibration Procedures
LLAI IOP Calibration Procedure
784 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Step Action






3 Select the ENABLE CALIBRATION (or ENABLE RJ CALIBRATION if an RJ
calibration is being performed) target through the Calibartion Status field on
the Calibration tab of the configuration form for the LLAI in the Monitor tab of
Control Builder or on the Station Detail display.
4 Momentarily short the two square calibrate pads in the upper-left corner of
the FTA under test, as shown in the following figure. Now check the STATUS
indicator (DS1) on the associated LLAI FTA. You will find it extinguishes
immediately, then comes back on in approximately 30 seconds. During this
time, the IOP card has performed its "zero input" calibration.
IOP Calibration Procedures
LLAI IOP Calibration Procedure
Release 100 Experion PKS Troubleshooting and Notifications Reference 785
1/03 Honeywell Part I
Step Action



5 Remove the "zero inputs" and replace them with full-scale signals. Refer to
the appropriate figure that follows for the full scale input value and the
connection to the screw or compression terminals.
IOP Calibration Procedures
LLAI IOP Calibration Procedure
786 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Step Action



IOP Calibration Procedures
LLAI IOP Calibration Procedure
Release 100 Experion PKS Troubleshooting and Notifications Reference 787
1/03 Honeywell Part I
Step Action



6 Again, momentarily short the calibration pads at the upper-left corner of the
FTA under test, then check the STATUS indicator (DS1) on the LLAI. The
STATUS indicator remains extinguished for approximately 30 seconds while
the IOP card performs its "full-scale" calibration.
7 If a thermocouple input is connected to the LLAI subsystem, it is
recommended that you recalibrate the Reference Junction (RJ) input each
time the thermocouple is recalibrated. Only channel 1 requires a zero ohm
jumper connected to it.
Connect a zero-ohm jumper to channel 1 as shown in the following figure.
Repeat Steps 3 and 4.
IOP Calibration Procedures
LLAI IOP Calibration Procedure
788 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Step Action



8 Connect a 2000 ohm resistor jumper to channel 1 as shown in the following
figure. Repeat Step 6.
IOP Calibration Procedures
LLAI IOP Calibration Procedure
Release 100 Experion PKS Troubleshooting and Notifications Reference 789
1/03 Honeywell Part I
Step Action



9 Be sure the target through the Calibartion Status field on the Calibration tab
of the configuration form for the LLAI in the Monitor tab of Control Builder or
on the Station Detail display has returned to ENABLE CALIBRATION,
indicating that the zero and span calibration process has completed.
10 Check the LLAI IOP card for Soft failures. If a Soft failure occurred, find the
source of the failure, correct it, and repeat the calibration procedure. If none
occurred, remove the test equipment from the FTA and reconnect the field
wiring. If the FTA has screw terminal strips, replace the plastic cover over the
strips.
IOP Calibration Procedures
LLAI IOP Calibration Procedure
790 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Step Action
11 Inform the operator that the LLAI subsystem can be returned to on-line
operation.

IOP Calibration Procedures
Nonredundant HLAI IOP Calibration Procedure
Release 100 Experion PKS Troubleshooting and Notifications Reference 791
1/03 Honeywell Part I
Nonredundant HLAI IOP Calibration Procedure
About HALI procedure
The following calibration procedure is written for the nonredundant model MU-TAIH02
or MU-TAIH03 HLAI FTA, but the procedure can also be used for the redundant model
MU-TAIH12, MU-TAIH13, MU-TAIH22, MU-TAIH23, MU-TAIH52, MU-TAIH53,
MU-TAIH62, MU-GAIH12/82, MU-GAIH13/83, MU-GAIH14/84, and MU-GAIH22/92
FTAs.


SHOCK HAZARD
Calibration may require access to hazardous live circuits and should only be
performed by a qualified service person. More than one switch may be
required to deenergize units before calibration.

Galvanic isolation FTA connection points
The connection points for the calibration voltage source and the shorting location that
starts the calibration differs for the model MU-GAIH12/82, MU-GAIH13/83, and MU-
GAIH14/84 Galvanically Isolated FTAs. Because of circuit density on the FTA board
assembly, IOP calibration terminals, similar to those on a standard FTA, could not be
added to the assembly. Instead, unused pins in the FTAs 50-pin auxiliary connector, J19,
provide a calibration interface for the Galvanic Isolation HLAI Calibration tool,
Honeywell part number 51201450-100. The following table lists the voltage input pins
and calibration start pins and the following figure is an illustration of the tool..

Description Pins
Primary IOP Voltage Source 19 (+) and 44 (-)
Secondary IOP Voltage Source 20 (+) and 45 (-)
Calibration Start (Short together) 21 and 46


IOP Calibration Procedures
Nonredundant HLAI IOP Calibration Procedure
792 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03


Calibration terminals
The signals required for calibration of the HLAI IOP are provided at the screw terminals
at the end of the tools cable when the cable is connected to the auxiliary connector on
the HLAI FTA. The calibration procedure is the same procedure used for the standard
HLAI FTA.
HLAI calibration procedure
Use the following procedure to calibrate a nonredundant HLAI IOP.


ATTENTION
This calibration procedure calibrates all channels simultaneously, rather than
each channel singularly.


Step Action
1 Put the IOP card in its IDLE state through the Execution State command on
its configuration form in the Monitor tab of Control Builder or the Station Detail
display.
2 Select the ENABLE CALIBRATION target through the Calibartion Status field
on the Calibration tab of the configuration form for the HLAI in the Monitor tab
of Control Builder or on the Station Detail display.
3 If the voltage source is connected before idling the IOP and enabling
calibration, the HLAI will report a Soft failure. Connect the calibration voltage
source to the FTA and adjust the voltage to 5 Vdc (4.9995 5.0005 Vdc).
See the following figures for the assembly layout of the nonredundant model
MU-TAIH02 FTA and the redundant model MU-TAIH12 FTA, respectively.
The assembly layouts of all the HLAI FTAs are illustrated in the Control
Hardware Installation Guide in Knowledge Builder.
IOP Calibration Procedures
Nonredundant HLAI IOP Calibration Procedure
Release 100 Experion PKS Troubleshooting and Notifications Reference 793
1/03 Honeywell Part I
Step Action



IOP Calibration Procedures
Nonredundant HLAI IOP Calibration Procedure
794 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Step Action



IOP Calibration Procedures
Nonredundant HLAI IOP Calibration Procedure
Release 100 Experion PKS Troubleshooting and Notifications Reference 795
1/03 Honeywell Part I
Step Action
4 Short the two calibration pads at the upper-left corner of the HLAI FTA to start
the calibration. For the Galvanically Isolated FTAs, two pins in the
Marshalling Panel connector are shorted together.
5 Be sure the calibration target on the form in Monitor tab of Control Builder or
Station Detail display has changed back to ENABLE CALIBRATION,
indicating that thezero and span calibration process has completed. Check
for the Soft failure CALIB ABORT, which indicates bad calibration.
6 Disconnect the calibration voltage source wiring.
7 Inform the operator that the HLAI can be returned to on-line operation.

IOP Calibration Procedures
Redundant HLAI IOP Calibration Procedure
796 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Redundant HLAI IOP Calibration Procedure
Simultaneous HLAI IOP calibration
Recalibrate each HLAI IOP separately with an off-line Controller or follow the previous
procedure for nonredundant High Level Analog Input FTA to simultaneously calibrate
both IOPs. The calibration voltage source must be connected to both sets of calibration
terminals on the redundant model FTA simultaneously with parallel wiring as shown in
the figure in the previous procedure for the model MU-TAIH12 FTA.


SHOCK HAZARD
Calibration may require access to hazardous live circuits and should only be
performed by a qualified service person. More than one switch may be
required to deenergize units before calibration.

IOP Calibration Procedures
Nonredundant AO IOP Calibration Procedure
Release 100 Experion PKS Troubleshooting and Notifications Reference 797
1/03 Honeywell Part I
Nonredundant AO IOP Calibration Procedure
About AO procedure
This calibration procedure is written with the nonredundant model MU-TAOX02 as an
example, but the procedure can also be used for the nonredundant model MU-GAOX02,
and MU-GAOX72 FTAs, and the redundant model MU-TAOX12, MU-TAOX52, MU-
GAOX12, and MU-GAOX82 FTAs.
AO calibration procedure
Use the following procedure to calibrate an Analog Output IOP.

Step Action
1 Isolate the AO IOP outputs. Use an Analog Standby Manual device to control
the devices connected to the FTA. The Analog Standby Manual device
provides isolation from the IOP outputs.
2 Put the IOP card in its IDLE state through the Execution State command on
its configuration form in the Monitor tab of Control Builder or the Station Detail
display.
3 Select the ENABLE CALIBRATION target through the Calibartion Status field
on the Calibration tab of the configuration form for the HLAI in the Monitor tab
of Control Builder or on the Station Detail display.
4 Connect an adjustable floating voltage source to the FTA output terminals as
shown in the following figures for the nonredundant model MU-TAOX02 FTA
or redundant model MU-TA0X12, respectively. Adjust the voltage source to
between 4.9995 and 5.0005 Vdc. The AO IOP uses this precision voltage
reference to do an accurate short term calibration of the internal loopback
ADC. The circuitry is then used to calibrate each output channel.
(See the Control Hardware Installation Guide for layouts of other model AO
FTAs.)
IOP Calibration Procedures
Nonredundant AO IOP Calibration Procedure
798 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Step Action



IOP Calibration Procedures
Nonredundant AO IOP Calibration Procedure
Release 100 Experion PKS Troubleshooting and Notifications Reference 799
1/03 Honeywell Part I
Step Action



5 Short together the calibration pads at the upper-left corner of the FTA. The
procedure takes approximately 5 seconds.
6 Disconnect the calibration source.
IOP Calibration Procedures
Nonredundant AO IOP Calibration Procedure
800 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Step Action
7 Inform the operator that the AO IOP can be placed in control.

IOP Calibration Procedures
Redundant AO IOP Calibration Procedure
Release 100 Experion PKS Troubleshooting and Notifications Reference 801
1/03 Honeywell Part I
Redundant AO IOP Calibration Procedure
Simultaneous AO IOP calibration
Follow the previous nonredundant Analog Output FTA calibration procedure to
simultaneously calibrate both IOPs. The calibration voltage source must be connected to
both sets of calibration terminals on the redundant model FTA simultaneously with
parallel wiring as shown in the redundant AO calibration connections figure in the
previous procedure.
IOP Calibration Procedures
LLMux IOP Calibration Procedure
802 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
LLMux IOP Calibration Procedure
About LLMUX calibration
The LLMux FTA daughter board can only be calibrated when it is mounted on a
Thermocouple (TC) FTA. After calibration, the daughter board can be moved to any
LLMux FTA and maintain the calibration. However, a TC daughter board is not
interchangeable with an RTD daughter board.
LLMUX calibration procedure
Use the following procedure to calibrate a LLMux IOP.

Step Action
1 Connect a precision voltage source to point zero, terminals T1A and T1B of
terminal strip J1 as shown in the following figure, and set the voltage to 100
millivolts (99.995 - 100.005 millivolts).



2 Remove the two jumpers, JRA and JRB, located between J2 and J3.
IOP Calibration Procedures
LLMux IOP Calibration Procedure
Release 100 Experion PKS Troubleshooting and Notifications Reference 803
1/03 Honeywell Part I
Step Action
3 Connect the precision resistor (three lead 100 ohm .005 ohm) to the remote
CJR terminals, J5. Apply power for 5 minutes.
4 Calibration is initiated by a single command for each FTA. Put the IOP card in
its IDLE state through the Execution State command on its configuration form
in the Monitor tab of Control Builder or the Station Detail display.
5 Select the ENABLE CALIBRATION target through the Calibartion Status field
on the Calibration tab of the configuration form for the LLMUX in the Monitor
tab of Control Builder or on the Station Detail display. The calibration
procedure is automatic and completes in less than one second.
6 Remove the voltage source. Disconnect the precision resistor from J5 and
reconnect the jumpers removed from JRA and JRB in Step 2.

IOP Calibration Procedures
RHMUX IOP Calibration Procedure
804 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
RHMUX IOP Calibration Procedure
About RHMUX calibration
The main calibration constants for the Remote Hardened Low Level Multiplexer
(RHMUX) IOP are determined during factory calibration and are used to calibrate the
gain block error and the A/D reference.
A subsequent field calibration calibrates only the A/D reference and is done only for the
100 mV range which results in the field calibration factor being set to a ratio of the
original factory calibration gain to the field calibration gain. This factor is then used to
modify the original factory calibration constants such that the original factory calibration
gain constants still exist.
RHMUX calibration method
The input to the RHMUX IOP is calibrated by using two input voltages for each scale,
one at 20% of full range, and on at 80% of full scale. The RHMUX IOP will check to see
if the voltage that is present is within 20% of what is expected for each step in the
calibration procedure.
If the input voltage is out of the expected voltage range, a signal with the led and in the
case of automated factory calibration is generated. When the input voltage isdigitized, the
firmware will take 34 readings, eliminate the highest and lowest readings, and average
the remaining readings. The gain can then be computed from the factor: Delta
Input/Delta Expected. The resultant gain constants are stored in nonvolatile memory
within the RHMUX IOP microprocessor. The field calibration factor is also set to 1.
If field calibration is performed at 50 hertz, rather than 60 hertz, the calibration
coefficients have a ratio of 545/655 prior to storage. This figure is not the exact ratio of
50 hertz to 60 hertz because of a peculiarity in the A/D converter in the RHMUX IOP.
Since calibration coefficients are stored just for 60 hertz, the firmware compensates
accordingly when 50 hertz operation for the RHMUX IOP is selected.
In all cases, millivolts are computed as:
(A/D Counts - ZERO Counts) x GAIN.
GAIN is determined at calibration time as:
Factory mV/Count) x (Field Calibration Factor) x (50 Hz/60 Hz Factor)
IOP Calibration Procedures
RHMUX IOP Calibration Procedure
Release 100 Experion PKS Troubleshooting and Notifications Reference 805
1/03 Honeywell Part I
Field calibration overview
The field calibration procedure is designed with the assumption that the RHMUX FTA
may be some distance from the control room and the console when calibration is
performed. Therefore, the procedure provides for all the interaction between the person
performing the calibration and the RHMUX FTA when the initial calibration command is
executed at the console and the tasks that must be performed locally at the RHMUX
FTA.
In addition, the RHMUX IOP will not exit the calibration sequence if it is unsuccessful,
but rather remains at the failed step in the calibration sequence in order to allow it to be
repeated. This means that in order to use the RHMUX IOP again, or restart the
calibration sequence, power to the RHMUX IOP must be cycled off and then on again.
RHMUX calibration procedure
Use the following procedure to calibrate an RHMUX IOP.

Step Action
1 Put the IOP card in its IDLE state through the Execution State command on
its configuration form in the Monitor tab of Control Builder or the Station Detail
display.
2 Verify on the RHMUX configuration form in the Monitor tab of Control builder
that the IOP is configured for the correct frequency.
3 Disconnect any field wires from channels 1 and 16.
4 Select the ENABLE CALIBRATION target through the Calibartion Status field
on the Calibration tab of the configuration form for the RHMUX in the Monitor
tab of Control Builder or on the Station Detail display.
5 At the RHMUX FTA, verify that the voltage at the factory calibration pin is a
logic one which indicates that field calibration is in process.
Verify that the FTAs Status LED is off and not blinking randomly.
6 Connect the calibration device to the channel 1 input terminals. Set the
voltage to 100 mV, +/- 5 microvolts.
7 Short the channel 16 input terminals for a minimum of 0.1 of a second and
then remove the short. The firmware uses burnout to read the state of the
channel 16 input. The multiplexer digitizes the input in about 4 seconds, turns
on the Status LED for 0.2 seconds, and turns the Status LED off if the voltage
is within 20% of the expected voltage. If not, the Status LED will blink twice.
IOP Calibration Procedures
RHMUX IOP Calibration Procedure
806 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Step Action
8 Set the calibration voltage to 20 mV, +/- 5 uV. Short the channel 16 terminals
again for a minimum of 0.1 of a second and then remove the short. The
RHMUX IOP will do another conversion. The firmware extracts a new slope
coefficient for the reference diode and overwrites the field the previous field
calibration factor.
9 If the calibration is successful and complete, the Status LED returns to the
normal blinking cycle. The RHMUX IOP will respond to a Status command
with an OK status. If the calibration was not successful, the response will be
CALIBRATION FAILURE.

RHMUX calibration failure
If during the calibration procedure, the RHMUX IOP senses that the calibration voltage
is off by more than 20%, the Status LED will blink twice (0.2 of a second on, 0.2 of a
second off) to indicate a failure. This requires that the calibration voltage be checked and
reset to the proper value. Again, the channel 16 input terminals must be shorted for a
minimum of 0.1 of a second and then opened to cause the RHMUX IOP to retry the
voltage. If the calibration sequence can not be successfully completed, power must be
cycled off and then on again to exit the calibration sequence.
IOP Calibration Procedures
Thermocouple Input Accuracy Verification
Release 100 Experion PKS Troubleshooting and Notifications Reference 807
1/03 Honeywell Part I
Thermocouple Input Accuracy Verification
About thermocouple verification
It is necessary to verify the accuracy of a thermocouple input. Verification is
accomplished with the use of a precision Thermocouple Simulator, the instruments
operating procedure, and the procedure steps that follow.
Thermocouple verification procedure
Perform the following steps to verify the accuracy of the thermocouple.

Step Action
1 Be sure the equipment is properly installed in the cabinet.
2 Connect a reference grade thermocouple wire between the Thermocouple
Simulator and one input of the process control system.
3 Install all equipment covers and close the cabinet doors.
4 Using the applicable configuration form in the Montior tab of Control Builder,
disable the Open Thermocouple Detection mode for the control point.
5 Allow the equipment to operate normally for 2 hours while temperature
gradients stabilize.
6 Verify the accuracy of the thermocouple using the Thermocouple Simulator
and following its operating procedure.
7 Move the thermocouple reference wire to another thermocouple input from
the process control system and repeat the above procedures, starting at Step
3.

IOP Calibration Procedures
Thermocouple Input Accuracy Verification
808 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03

Release 100 Experion PKS Troubleshooting and Notifications Reference 809
1/03 Honeywell Part I
Periodic IOP Redundancy Tests
Overview
About redundancy tests
This section describes the recommended periodic verification of the equipments
redundancy where applicable.
At an appropriate time, such as during a annual period of scheduled plant maintenance,
the Process Manager I/O subsystems availability can be improved by performing
specific tests on various hardware parts of the Process Manager I/O subsystem. During
the tests, personnel should be prepared for either proper operation or improper operation
of the hardware. The preparation for improper operation of the hardware during the tests
yields the lowest Mean Time to Repair (MTR), which is important when maximizing
subsystem availability.
Even though fault coverage is high in the process control system during normal
operation, periodic redundancy testing provides additional fault coverage by exercising
any hardware that is not in use during normal operation.
Monitor displays
You can monitor and interact with a redundant Input/Output Processor (IOP) through its
configuration form in the Monitor tab of Control Builder or its Station Detail display.
The following figure shows the main tab of the configuration form for an Analog Output
IOP in the Monitor tab of Control Builder. The figure is for example purposes only does
not represent actual indications.

Periodic IOP Redundancy Tests
Overview
810 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03


Periodic IOP Redundancy Tests
Testing IOP Redundancy
Release 100 Experion PKS Troubleshooting and Notifications Reference 811
1/03 Honeywell Part I
Testing IOP Redundancy
IOP redundancy terminology

Term Description
IOP A IOP A is the physical primary IOP. It is the IOPthat is physically
connected by cable to the A cable connector on a redundant
FTA.
IOP B IOP B is the physical primary IOP. It is the IOP that is physically
connected by cable to the B cable connector on a redundant
FTA.
Primary IOP IOP B is the physical primary IOP. It is the IOP that is physically
connected by cable to the B cable connector on a redundant
FTA.
Secondary IOP The secondary IOP is the logical secondary IOP. It can be
either IOP A or IOP B that is not controlling the FTAs field
terminals or providing the process variable.
IOP Swap An IOP swap reverses the status of the physical IOPs, A and B.
The present primary IOP becomes the secondary IOP, and the
present secondary IOP becomes the primary IOP.
IOP Bias For the 8-channel Analog Output IOP only, operation with the
IOP A as the primary IOP and IOP B as the secondary IOP is
with the basis, the preferred condition. Operation with the IOP B
as the primary IOP and IOP A as the secondary IOP is against
the basis, the nonpreferred condition.

Periodic IOP Redundancy Tests
Testing IOP Redundancy
812 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Test procedure
Use the following procedure to test each redundant IOP configuration.

Step Action
1 In Monitor tab of Control Builder, double-click applicable IOP icon to open its
configuration form.
2 On the Main tab, check the current status of IOP Partner A and IOP Partner
B.
3 Click the Swap Primary IOP button.
Check that the status of IOP Partner A and IOP Parnter B is switched
accordingly.
4 Click the Swap Primary IOP button again to restore the status noted in Step
2.
5 Repeat this procedure for other redundant pairs of IOPs.

Periodic IOP Redundancy Tests
Redundant 8-Channel Analog Output IOPs
Release 100 Experion PKS Troubleshooting and Notifications Reference 813
1/03 Honeywell Part I
Redundant 8-Channel Analog Output IOPs
About redundancy bias
Redundancy for the 8-channel Analog Output IOPs is biased toward the IOP A to
maximize reliability. Hardware bias is preferred because IOP B (the physical secondary)
is connected to the Analog Output FTA through a switching module on the FTA, while
IOP A (the physical primary) is connected directly to the FTA circuitry that interfaces the
FTAs field wiring output terminals. Use of the procedure in this subsection tests a
redundant pair of Analog Output IOPs for proper operation.
Hardware identification
Locate the following components.
Analog Output IOP A
Analog Output IOP B
The redundant Analog Output FTA
An Analog Output Standby Manual device
Devices that are being controlled by the analog output of the FTA
Control algorithms that are driving the analog outputs
Status check
Using the IOP configuration form in the Monitor tab of Control Builder, check that the
IOPs are currently operating normally, as indicated by a status of OK/BKP. In addition,
be sure the following is true.
The outputs are being controlled by IOP A
IOP A and IOP B are synchronized
IOP A is operating normally without Soft failures
IOP B is operating normally without Soft failures
Periodic IOP Redundancy Tests
Redundant 8-Channel Analog Output IOPs
814 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
8-channel AO test procedure
Use the following procedure to test for proper 8-channel AO IOP redundancy operation.

Step Action
1 Begin the test at a convenient time. Disrupt power to IOP B by toggling the
IOPs upper extractor. The status of the IOPs on the Main tab of the
configuration form in Control Builder should indicate a status of OK/NR [S]
briefly, and then return to a status of OK/BKP for the IOPs. Confirm that the
field devices are operating properly by observing the operation of the
process, or measure the output currents reaching the devices.
2 Disconnect the cable to IOP B. The AO Main tab should indicate a status of
OK/BSF for the IOPs. Confirm that the field devices are operating properly by
observing the operation of the process, or measure the output currents
reaching the devices.
3 Reconnect the cable to IOP B. The AO Main tab should return to an OK/BKP
status for the IOPs.
4 Click the Swap Primary IOP button so that IOP B has control of the FTAs
outputs. The AO Main tab should indicate a BKP/OK status for the IOPs.
Check that the Main tab continues to indicate BKP/OK status for a period of
at least two minutes to allow the Redundancy Diagnostics to complete with
IOP B now controlling theFTA outputs. Confirm that the output devices are
operating properly by observing the operation of the process, or measuring
the output currents reaching the field devices before and after executing the
swap command.
5 Disrupt power to IOP A by toggling the IOPs upper extractor. The AO Main
tab should indicate a [S] NR/OK status briefly, then return to BKP/OK.
Confirm that the output devices are operating properly by observing the
operation of the process, or measuring the output currents reaching the field
devices.
6 Disconnect IOP As FTA cable. The AO Main tab should indicate a status of
BSF/OK for the IOPs. Confirm that the output devices are operating properly
by observing the operation of the process, or measuring the output currents
to the field devices.
7 Connect IOP As FTA cable. The AO Main tab should return to a BKP/OK
status for the IOPs.
Periodic IOP Redundancy Tests
Redundant 8-Channel Analog Output IOPs
Release 100 Experion PKS Troubleshooting and Notifications Reference 815
1/03 Honeywell Part I
Step Action
8 Allow the subsystem to operate against the bias with IOP B controlling the
outputs for a period of time, such as 4 hours. During this period of time, the
AO Main tab should continue to indicate a BKP/OK status for the IOPs.
Ensure that no Soft failures are logged into the Station Event Journal.
Continue to monitor that the output devices are operating properly by
observing the operation of the process, or measuring the output currents
reaching the field devices
9 Execute a Swap Primary IOP command so that IOP A has control of the
FTAs outputs. The AO Main tab should indicate an OK/BKP status for the
IOPs. Continue to monitor operation of the output devices with the bias for a
period of time, such as 2 hours.

Periodic IOP Redundancy Tests
Power Cable Redundancy
816 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Power Cable Redundancy
About power cables
The IOP Card files, the Digital Input Power Distribution assembly, and the Galvanic
Isolation Power Distribution assembly are provided with redundant power cables to
enhance power distribution reliability within the Process Manager I/O subsystem. You
should be able to disconnect either end of one of the two power cables providing power
to the card file, Digital Input Power Distribution assembly, or Galvanic Isolation Power
Distribution assembly without affecting equipment operation.



Power cable redundancy testing should be performed during a plant
shutdown.

Testing power cable redundancy
Perform the following steps for each IOPcard file, Digital Input Power Distribution
assembly, and Galvanic Isolation Power Distribution assembly.

Step Action
1 Disconnect one of the pair of power cables for a card file, Digital Input Power
Distribution assembly, or Galvanic Isolation Power Distribution assembly at
either the Power System connection or the other end of the cable. Determine
if the operation of the equipment is impaired by observing the operation of the
affected IOP cards.
2 Replace the cable connection and then disconnect the other cable in the pair.
Determine if the operation of the equipment is impaired.
3 Repeat Steps 1 and 2 for all card files, Digital Input Power Distribution
assemblies, and Galvanic Isolation Power Distribution assemblies.

Periodic IOP Redundancy Tests
Power Supply Module Redundancy
Release 100 Experion PKS Troubleshooting and Notifications Reference 817
1/03 Honeywell Part I
Power Supply Module Redundancy
About power system redundancy
A Power System with redundant Power Supply Modules should continue to provide
power to the High-Performance Process Manager without interruption when one of the
Power Supply Modules fails or looses ac power.



Power system redundancy testing should be performed during a
plant shutdown.

Testing power system redundancy procedure
Perform the following steps to test the Power Systems redundancy power capability.

Step Action
1 With the both Power Supply Modules of a redundant Power System
operating, place the ON/OFF switch of the right Power Supply Module in the
OFF position. Observe that the IOP cards continue to operate normally (their
Status and Power indicators are illuminated). Return the ON/OFF switch to
the ON position, if operation continues normally. Should the IOP cards not
continue to operate normally, check cables and/or replace the Power Supply
Module.

ATTENTION
When the left Power Supply Modules ON/OFF switch is placed in the OFF
position, all Low Level Analog Input IOPs should report a Soft failure, but they
will continue to operate normally.
2 With the both Power Supply Modules of a redundant Power System
operating, place the ON/OFF switch of the left Power Supply Module in the
OFF position. Observe that the IOP cards continue to operate normally (their
Status and Power indicators are illuminated). Return the ON/OFF switch to
the ON position, if operation continues normally. Should the IOP cards not
continue to operate normally, check cables and/or replace the Power Supply
Module.

Periodic IOP Redundancy Tests
Power Supply Module Redundancy
818 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03

Release 100 Experion PKS Troubleshooting and Notifications Reference 819
1/03 Honeywell Part I
System Performance and Tuning Considerations
System Performance Features
Some of these features are controlled by system configuration and licensing. Others are
only automatically applicable when the system is ordered with the Installation Services
Option. Without this option, some features require customer care and intervention.

PC Qualification/
Installation
Services
The ability to Attain system Performance, Availability, and
Reliability, starts at the ground level with PC Platform.
Honeywell works with Dell to build PCs to specifications to
meet the needs of Process Control Systems. Although
based on systems available to the General Public, these
systems will typically include such items as Error Correcting
Memory, internal hardware sensors, management
applications, and other features that differentiate them from
the typical household or business PC. Once built, these
systems are then brought in for evaluation and testing.
Honeywell then tests these platforms to verify that they meet
certain Environmental and regulatory standards. This is
necessary to verify that the PC will work in all types of
Process Control scenarios.
Qualification continues with the Operating System
installation. How the system performs is very dependent on
the OS software configuration, which includes the device
drivers that interact with the hardware. Many performance
characteristics are derived from this interaction, while also
working towards optimizing the user experience.
Offered via the Honeywell Installation Services option, the
data from the qualification effort is included in the Operating
System installation CDs, called NT5Plus. If you have not
ordered the system with NT5Plus, then you should apply the
qualified driver set for your PC platform.
The information on hardware drivers and versions is
published in the Software Change Notice (SCN) for the
Release. If you are unable to attain the specified driver
versions, call the Honeywell Technical Assistance Center.
Redundant
Networking
A configuration option, it protects the system from network
faults. The system monitors the network status and will
automatically fail over when the system detects a fault.
System Performance and Tuning Considerations
System Performance Features
820 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Server Redundancy This allows the system to continue operating even when a
PC fails which was hosting the Experion PKS Server. All
systems in the configuration will shift to the backup system if
the primary node has failed.
Fast Failover: Some processes need to be more
tolerant to total system failure. This option includes
more stringent monitoring of the two servers and a faster
switch-over time.
Redundant Engineering Repository (Process Systems):
When the Redundant Server option is chosen on
Process Systems, you automatically get redundant
Engineering Repositories. This is a database of Control
information and configuration items which are critical in
operation on these type of systems.
Multi-User/Location
Control Builder
(Process Systems)
An application to define process configurations and monitor
status, the system supports up to 4 of these applications
running on separate nodes in the system.
Multiple
Clients/Stations
The system supports up to 20 Stations for Process and 40
for SCADA systems.
Integrated Security An integrated security model limits on who can change
parameters that effect the control environment.
Fast Recovery/Re-
Installation
(NT5Plus)
Should a PC hardware failure occur and the system was
purchased with Installation Services, the NT5Plus installation
CD can be used to reinstall the systems configuration in a
short period of time.

System Performance and Tuning Considerations
Operating System Tuning
Release 100 Experion PKS Troubleshooting and Notifications Reference 821
1/03 Honeywell Part I
Operating System Tuning
Systems ordered with Installation Services (NT5Plus) already have these settings applied
for the Operational Phase. NT5Plus installed systems will benefit from the settings
mentioned below only during the Configuration Phase of the system. Those systems
which have not had any of the settings applied will benefit from the settings described
below given the systems intended usage and Phase. All settings must be applied with a
User Account logged in that has Administrative Privileges on the system being tuned.
Service/Kernel Tuning
Windows 2000 Professional
Three types of systems are supported on Windows 2000 Professional; Server,
Engineering Workstation, and Client. Server can be comprised of the Experion PKS
Server Components or the Engineering Repository/SQL (Process Systems only)
components. Engineering Workstation (Process Systems only) is comprised of Control
Builder and Engineering Repository/SQL components. Clients are systems running
Station and/or Control Builder (Process Systems Only).
Kernel Tuning changes the way the Operating System assigns tasking priorities. Two
main areas exist on Professional, Applications or Background Services. The ability to
change this setting is accessed by performing the following steps:

Step Action
1 Locate the My Computer Icon on the Desktop.
2 Right-click the icon and choose properties.
3 On the System Properties Window that appears, choose the Advanced Tab.
4 In the Performance Section, Click the Performance Options Button.


System Performance and Tuning Considerations
Operating System Tuning
822 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03


Tuning this parameter changes the overall effect of the foreground Application response.
On Clients, the intended use is Applications. Engineering Workstation are balanced
between Application and Background Services. Servers need more response for the
Background Services. When tuned for Background Services, foreground application
receive lower priority thereby allowing the background services more.
For Clients and Engineering Workstations, the selection should be Optimize performance
for Applications.
For Experion PKS and/or Engineering Repository Servers, the selection should be
Optimize performance for Background Services.
System Performance and Tuning Considerations
Operating System Tuning
Release 100 Experion PKS Troubleshooting and Notifications Reference 823
1/03 Honeywell Part I
Windows 2000 Server
Only two types of systems are supported on Windows 2000 Server; Server and
Engineering Repository/SQL Server. Server can be comprised of the Experion PKS
Server Components and/or the Engineering Repository/SQL (Process Systems only)
components. Although Clients can run on the Server itself, they will receive poor
performance. (See the Topologies section of this document for more information.)
Kernel Tuning changes the way the Operating System assigns tasking priorities. Server
allows more tuning options and is actually a two-step process. Step one involves setting
the Application Response. Step two involves tuning the Server Service.

Step Action
1 Application Response:
Adjust the application response. First decide whether or not you will run
applications on your Server. (Control Builder, Station, Excel, etc.) The
recommendation is that you do NOT run applications and configure the
system as what is called a Headless server. (See the Topologies section of
this document for more information.)
3. Locate the My Computer Icon on the Desktop.
4. Right Click the icon and choose properties.
5. On the System Properties Window that appears, choose the Advanced
Tab.
6. In the Performance Section, Click the Performance Options Button.



Tuning this parameter changes the overall effect of the foreground
System Performance and Tuning Considerations
Operating System Tuning
824 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Step Action
Application response. For Servers, the recommended setting (Headless
Node) is to have the parameter set to Background Services. When tuned for
Background Services, foreground applications receive lower priority thereby
allowing the background services more.
Important Notes: During the Configuration phase of the system, running
applications on the Server will be effected by this parameter setting.
Therefore, this setting can be set to Applications during the configuration
phase and then changed to Background Services for the Operational Phase.
Users intending to run applications on their Server during the Operational
Phase, should set this option to Applications.
2 Server Service Tuning:
Adjust the application response. First decide whether or not you will run
applications on your Server. (Control Builder, Station, Excel, etc.) The
recommendation is that you do NOT run applications and configure the
system as what is called a Headless server. (See the Topologies section of
this document for more information.)
7. Locate the My Network Places Icon on the Desktop.
8. Right Click the icon and choose properties.



9. Choose one of the defined networks. (It does not matter which one is
chosen.) One of the labeled items on the right hand side with the
System Performance and Tuning Considerations
Operating System Tuning
Release 100 Experion PKS Troubleshooting and Notifications Reference 825
1/03 Honeywell Part I
Step Action
following icon associated with it:

10. Right Click it and choose Properities.
11. Highlight (Click On) the File and Printer Sharing for Microsoft Networks
and click the Properties button.



Tuning this parameter changes the overall effect of how the system handles
Services. For Servers, the recommended setting (Headless Node) is to have
the parameter set to Maximize data throughput for network applications.
Important Notes: During the Configuration phase of the system, running
applications on the Server will be effected by this parameter setting. Based
on System Configuration, the following rules can be applied:
On Small Systems and Medium to Large system without the integrated
System Performance and Tuning Considerations
Operating System Tuning
826 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Step Action
Engineering Repository (it is on a separate node), this setting can be set to
Minimize memory used on small systems during the configuration phase and
then changed to Maximize data throughput for network applications for the
Operational Phase.
Medium to Large System configurations with the Integrated Engineering
Repository should set it to Balance during the configuration phase and then
changed to Maximize data throughput for network applications for the
Operational Phase.
On nodes dedicated to running only the Engineering Repository (SQL), this
setting should always be Maximize data throughput for network applications.

Disk Management
Disk performance, or the capability of the system to access and store files on the hard
disk, can greatly affect the overall performance of the system. Other than Disk failures,
two types of File System (the format of storage on the disk) issues affect the system: File
System Errors and Fragmentation.
File System Errors
These can occur frequently during the following events:
Power Outages
Improper Shutdown
Disk Hardware malfunction.
In order to fix the errors, the system must first be set, and then rebooted. (It is
recommended that this operation not be done with the system On-Control.)
Perform the following tasks:
System Performance and Tuning Considerations
Operating System Tuning
Release 100 Experion PKS Troubleshooting and Notifications Reference 827
1/03 Honeywell Part I

Step Action
1 Locate and Open the My Computer icon on the desktop by double clicking
the icon.


2 Click or highlight the drive you wish to check. Right click it and choose
properties.
3 Selecting the Tools tab will present the following screen:

System Performance and Tuning Considerations
Operating System Tuning
828 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Step Action

4 Click the Check Now button in the Error-Checking section.


5 After making sure the Automatically fix files system errors box is checked,
click the Start button Unless a prior check revealed bad sectors do not
System Performance and Tuning Considerations
Operating System Tuning
Release 100 Experion PKS Troubleshooting and Notifications Reference 829
1/03 Honeywell Part I
Step Action
click the Start button. Unless a prior check revealed bad sectors, do not
check the Scan for and attempt recovery of bad sectors.


6 Due to file system locking the drive (NTFS), the system cannot perform this
option at this time. Click the Yes button to schedule the operation to occur
the next time the system is started.
7 Shutdown and Restart the system. (The check will occur during the Startup.)

After the system returns to the logon prompt, you should log in and check the disk report
in the Systems Event Viewer. If the report contains that it had found bad sectors, then
the operation should be re-run and the option to Scan for and attempt recovery of bad
sectors should be checked. Drives which continually report bad sectors should be
scheduled for replacement. It usually indicates that the drive is experiencing hardware
malfunctions.
File System Defragmentation
Although the NTFS File system attempts to minimize this problem, it is often the most
frequent occurring performance issue to occur during normal operation. Basically,
fragmentation is the process of when a file or piece of data is written to disk, and it is not
written contiguously. This causes the system to perform multiple read and lookups every
time the file is accessed. The process of Defragmentation optimizes the file system by
making each file on the disk occur contiguously. Also, commonly accessed files, such as
operating system or frequently accessed files, are moved to the first sectors on the disk.
This enables these files to be found and accessed faster.
Fragmentation will occur frequently and affect performance on Experion PKS Systems.
Since the performance of the system is severely degraded during the running of the tasks
to fix this performance problem, it should not be done with the system On-Control.
Administrators of the system should add this maintenance task to the Plant Maintenance
schedule, so that it occurs during Control Shutdowns.
System Performance and Tuning Considerations
Operating System Tuning
830 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Fragmentation will also occur naturally during the Configuration Phase of the system. It
is highly suggested that when the configuration phase of system is completed and before
the operation phase, that the system be defragmented.
Steps to Defragment the Disk:

Step Action
1 Locate and Open the My Computer icon on the desktop by double clicking
the icon.
2 Click or highlight the drive you wish to defragment. Right click it and choose
properties.
3 Selecting the Tools tab, click the Defragment now button in the
Defragmentation Section.


4 After Highlighting the drive you wish to defragment, click the Analyze button.
This will assess the fragmentation level of the drive. (Lots of Red, like the
example, means the system if fragmented. Large areas shaded in Blue
means the system is mostly contiguous.)
System Performance and Tuning Considerations
Operating System Tuning
Release 100 Experion PKS Troubleshooting and Notifications Reference 831
1/03 Honeywell Part I
Step Action
5 After analysis, you should then defragment the drive either by choosing
Defragment now on the recommendation screen, or by reselecting and
clicking the Defragment button. Depending on the level of fragmentation and
usage, the task may take some time to complete.



ATTENTION
The default fragmentation utility included in Windows 2000 can be upgraded
to the full version. Executive Softwares Diskeeper includes a scheduler and
the ability to defragment directories and page files at boot time. The
defragmentation tasks will effect the Control System if set to run automatically
via the Scheduler. Care should be taken when scheduling these events.


Memory and Swapfile
Two types of memory exist in the system; Physical RAM and the Swapfile. Frequently,
Multi-tasking operating systems such as Windows 2000, have the ability to take memory
space occupied by data in physical RAM and swap it into a file. This frees up the
physical RAM for other processes. If the process again requires the data that was
swapped out, a page fault occurs and the page is swapped back from the file into physical
RAM before operation continues. This type of management is called Paging. (And the
associated swapfile is called the page file.)
In Windows 2000 using Task Manager, looking at the Total Limit in the Commit Charge
section of the Performance tab, the Total value is the amount of Physical RAM and
Swapfile combined. The Physical Memory section shows how much of the Physical
memory is available for use.
Page file settings include a lower and upper limit. The lower limit is typically the
amount of physical RAM plus management space. This is almost always 1.5 times the
amount of physical RAM. The system typically suggests that the upper limit be set to
around 3 times the amount of physical RAM. Windows 2000, in normal operation, will
only use the lower limit size, and hence only the value of the lower limit (Initial Size) is
pre-allocated. If the usage exceeds this limit, the system will then continue to allocate
additional space until the upper limit (Maximum Size) is reached or the system runs out
of disk space. If this occurs, it usually means that an application/process is leaking
memory.
Some paging of memory for systems is normal. Excessive paging will hurt performance
as there is a hit taken during the swapping and allocation phases. Memory performance
can be degraded during some operations as long as they are not prolonged or part of
System Performance and Tuning Considerations
Operating System Tuning
832 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
normal system operations. The goal is to produce perfectly balanced systems. Ones
which have enough physical RAM for normal operations and the ability to Page when an
abnormal event is required. Systems who perform paging operations frequently during
normal operations will receive great performance benefits by adding more physical
RAM.
Honeywell attempts to specify default memory configurations (as published in the SCN
of the Release) to minimize paging during normal operations of the system. Scaled via
Small, Medium, and Large Systems, and then broken up by Operating System, you
should use these tables as a starting point. You should then monitor the Pagefile usage to
determine whether or not your system could benefit from added physical RAM. (See
Section 6.)
At any time memory is added or removed from the PC, the operating system should be
adjusted based on the system type described below.
Client/Station Memory Settings
Based on the Operating System and application usage, this system should not be affected
by paging operations as long as the memory is at the specified amount of 128 MB. If
adjustments are needed (Section 3.3.4), you should follow the default rules of the
Operating System suggestion:
(Example for a 128 MB System)
Initial Size: 192 MB (or default Operating System suggestion.)
Maximum Size: 384 MB (or default Operating System suggestion.)
Servers with 128 MB of Physical RAM or Less.
Based on the Operating System and application usage, this system can be severely
affected by paging because the amount is less than required. Smaller systems may be
able to take this performance hit, but medium to large systems will not be able to
adequately perform. Adjustments for this type of system are required for operation.
(Section 3.3.4) The settings suggested below should allow the system to run, but a
memory upgrade is highly suggested:
Initial Size: 300 MB
Maximum Size: 450 MB
System Performance and Tuning Considerations
Operating System Tuning
Release 100 Experion PKS Troubleshooting and Notifications Reference 833
1/03 Honeywell Part I
Servers with 256 MB of Physical RAM or More.
Based on the Operating System and application usage, this system should not be effected
by paging as long as the memory specifications are followed for the system size and
usage. If adjustments are needed (Section 3.3.4), you should follow the default rules of
the Operating System suggestion:
(Example for a 256 MB System)
Initial Size: 1.5 times physical or default Operating System suggestion. (Eg. 384 MB)
Maximum Size: 3 times physical or default Operating System suggestion. (Eg. 768 MB)
Adjusting Swapfile Size on Windows 2000
Steps to change the Swapfile/Pagefile on Windows 2000 (Professional and Server):
1. 1. Locate the My Computer Icon on the Desktop.
2. 2. Right Click the icon and choose properties.
3. 3. On the System Properties Window that appears, choose the Advanced Tab.
4. 4. In the Performance Section, Click the Performance Options Button.



System Performance and Tuning Considerations
Operating System Tuning
834 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
5. In the Virtual Memory Section, click the Change button



6. After verifying the correct drive is selected in Drive Section, add the appropriate
values in the Paging file size for selected drive and click the Set Button.
7. Changing these values will require the system to be rebooted for them to take effect.
As you answer OK to subsequent screens, you will be asked to restart the system.

System Performance and Tuning Considerations
Operating System Tuning
Release 100 Experion PKS Troubleshooting and Notifications Reference 835
1/03 Honeywell Part I
Network Optimization
Few steps in the Operating System itself can optimize the Network. Utilizing and
managing the traffic on the network with your networking equipment will yield more
gains.
Service/Kernel Tuning affects the ability of the system to respond to network traffic. If
you have not applied these settings, you should perform them now.
The order in which the systems access the network is important. The Bindings should be
adjusted so that each system accesses the network in the same order. If your system has
more than 1 network card, then you should verify that the bindings for each system is in
the correct order.
Management of Traffic
If your control system uses an Ethernet Network for its Control Network, then you can
benefit by restricting the type of traffic that occurs on this network.

High Alarm
Low Alarm
Comm.
Err.
High Alarm
Low Alarm
Comm.
Err.
PlantScape
Servers
Controller
1
2
3


Microsoft, by default, will use all network cards defined in a system for communication
with other systems as long as the network are common between the initiator and target.
From the example above, you can see that all 3 Ethernet Networks are common between
the 2 Experion PKS Servers. Effective management for Server to Server communication
would be to direct all Server to Server traffic across networks 1 and 2; thereby reserving
network 3 for Control traffic only. Server to Server or Windows 2000 Networking
System Performance and Tuning Considerations
Operating System Tuning
836 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
traffic, mostly occurs through the utilization of the NetBIOS transport protocol. If we
disable this protocol from use on Network 3, then we restrict this type of communication.
Steps to Adjust Bindings and Disabling Protocols from the Ethernet based Control
Network:

Step Action
1 Locate the My Network Places Icon on the Desktop.
2 Right Click the icon and choose properties.


3 Click on Advanced, then choose Advanced Settings.

System Performance and Tuning Considerations
Operating System Tuning
Release 100 Experion PKS Troubleshooting and Notifications Reference 837
1/03 Honeywell Part I
Step Action


4 In the Connections Section, the order should be the following:
1. Primary Plant Information Network
2. Backup Plant Information Network (If you have redundant networks.)
3. Supervisory Control Network (If you are doing control over Ethernet.)
Important Note: Your network names may not be the ones used in the
example provided. (These are only assigned if the system had the
Installation Services option.) In this case, you will have to determine which
network card is handling which task in the system before making
adjustments.
Use the Up and Down arrows provided on the right to make any necessary
adjustments.
5 If the system has the Supervisory Control Network. Click to highlight the
network in the Connections section.
6 Verify that there is no Check mark for the File and Printer Sharing for
Microsoft Networks option in the Bindings section.
System Performance and Tuning Considerations
Operating System Tuning
838 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Step Action
7 Click OK to apply the setting.

Benefits from other Network Services
You can reduce the number of Broadcasts a system performs, and hence increase
network performance, by using other services to provide directory and resolution
information. (Active Directory, WINS, DNS, Domains, etc.) However, this will make
some functions of the Control System dependent on these services for operation. In order
to integrate these types of services into the system, extreme care and planning needs to
occur.
Video Settings
There are no great performance gains to be made through adjustments made to Video
Settings. The system applications and displays have been optimized to be displayed at a
resolution of 1024 by 768 with 65K (High Color 16 bit) colors. Utilizing any other
setting that this will produce anomalies in some displays.
In order to receive the best performance from the PC perspective, we highly suggest that
the Video Card utilized be for the AGP bus. This frees up the PCI bus and gives the
video processor a more direct line to the CPU and memory resources.
System Performance and Tuning Considerations
System Usage
Release 100 Experion PKS Troubleshooting and Notifications Reference 839
1/03 Honeywell Part I
System Usage
The system usage itself will have an impact on the performance of the system. Most
memory and CPU recommendations are based on what we consider average use of the
system. Although highly interpretative, depending on how the system is used and/or
configured may require your system to utilize more memory, higher speed or multiple
CPUs, larger disks, faster networking, etc.
These type of adjustments can only occur over time as you gain experience with your
usage of the system. Here are some features in the system, which will affect the
performance of the Supervisory Systems:
1. Number of Stations
The Display update rate.
Shared vs. local displays
Chart Visualization
The number of Parameters viewed (across all Stations) and their frequency of
change.
2. Frequency of Report Generation.
3. Frequency of performed maintenance; ie defragmentation of the disk.
4. Number of Servers participating in a DSA Architecture and the number of parameters
shared.
5. History Collection.
6. Event Archiving.
7. Server Synchronization with File Backup.
8. Size of the system. (Also the size of ERDB for Process Systems.)
As you system is adjusted over time and customized to your Control environment, you
should utilize the techniques outlined in System Monitoring/Assessing the need for
hardware upgrades to evaluate how your systems are performing and make adjustments
accordingly.
System Performance and Tuning Considerations
Topology related settings
840 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Topology related settings
The types of configurations in discussed in this section are not factored in to the
published performance specifications for the system. Adjustments would have to be
made accordingly.
Physical location of the Systems
The location and distance between each node becomes a factor in the performance.
Experion PKS Servers are designed to be within the same Network. If hops are
introduced, then timing parameters need to be adjusted due to the increased time to
perform such things as synchronization. As tasks take longer to complete, they affect the
other running tasks on the system. Station performance will also be affected if it is
running remotely. Consult the Server Documentation for setting up the Server to support
these types of architectures. Monitor the Server Performance and adjust accordingly.
Physical location of the Components
During the operational phase of the system, client response will be better when the
application is not run on the Server itself.
For Process Systems, if the processor on the server is being overwhelmed, you may want
to change the configuration and move the ERDB to its own dedicated node. Depending
on System Usage, this can have a dramatic impact on your system performance.
Service Integration
Adding Services, such as Active Directory, to the Experion PKS Server will have an
impact on the Servers CPU and memory usage. This should be taken into consideration
when planning the hardware purchase for your Server. Consult the Network Planning
Guide for more information.
Network Integration
Integrating the Plant Networks with the Companies Business Network can also impact
the performance of the System. If Active Directories are going to be integrated, you
must plan to be able to support the whole Business Network Infrastructure. Depending
on the size of the company, this can have a large impact on the Servers CPU and memory
usage. If considering this type of integration, you should plan this into your hardware
purchase for your Server. Consult the Network Planning Guide for more information.
System Performance and Tuning Considerations
System Monitoring/Assessing the need for hardware upgrades
Release 100 Experion PKS Troubleshooting and Notifications Reference 841
1/03 Honeywell Part I
System Monitoring/Assessing the need for hardware
upgrades
Most monitoring of the system should be done during the Operational Phase of the
system. Frequently, during the configuration phase, some components of the system are
maximized to reduce the amount of time to perform the task.
When the system is ordered with Installation Services (NT5Plus), a pre-canned
monitoring tool is included in the Start\Programs\Experion PKS PC Monitoring Tools
folder. Simply click to open the PC Performance Tool.
If your system was not ordered with this option, go to Opening Performance Monitor.



Double Click on the Icon for System Performance.

System Performance and Tuning Considerations
System Monitoring/Assessing the need for hardware upgrades
842 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03


System Performance and Tuning Considerations
System Monitoring/Assessing the need for hardware upgrades
Release 100 Experion PKS Troubleshooting and Notifications Reference 843
1/03 Honeywell Part I
Opening Performance Monitor
On Windows 2000 Professional systems without the pre-built console, follow the steps
outlined below:

Step Action
1 On the Explorer Toolbar, click Start/Settings/Control Panel.
2 Locate the Administrative Tools Icon and Double Click.
3 Double Click the Performance Icon.

4 Click the + sign on the Toolbar on the Right Pane of the console to bring up
the Add Counters window.

System Performance and Tuning Considerations
System Monitoring/Assessing the need for hardware upgrades
844 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Step Action

Add the Following Counters:
Ref
Number
Performance
Object
Counter Instance
1 Paging File % Usage \\??\C:\Pagefile.sys
2 System Processor Queue
Length

3 System Context
Switches/Sec

4 Processor % Processor Time _Total
5 Processor % Interrupt Time _Total
6 Server Work
Queues
Queue Length 0
7 Server Work
Queues
Bytes
Transferred/Sec
0
5
8 TCP Segments/Sec

System Performance and Tuning Considerations
System Monitoring/Assessing the need for hardware upgrades
Release 100 Experion PKS Troubleshooting and Notifications Reference 845
1/03 Honeywell Part I
Interpreting the Performance Counter Values:
Paging File Usage
(Reference Number 1.)
Evaluating the Paging File Usage counter will tell you whether or not your system has
enough physical RAM. The counter itself tells you how often the system is using the
Paging File. Average values approaching 40% or higher are a strong indication that the
system is running without enough memory.
Recommendation: Add more Physical RAM.
Processor Speed and quantity
In order to evaluate whether or not your system has adequate processing power, you must
look a several counters:
System/Processor Queue Length
System/Context Switches/Sec
Processor/% Processor Time
Processor/% Interrupt Time
Server Work Queues/Queue Length
(Reference Numbers 2-6)
The Processor Queue Length indicates how many threads are waiting for CPU time.
Evaluating the Average will give you an idea of how well the system is supporting the
configuration. Generally, numbers averaging from 2 to 15 indicate the system could
receive a benefit by moving to a faster CPU. Numbers averaging above 15 indicate the
system could receive a benefit by moving to a Multiple CPU system. (Microsoft states
that systems with average queue lengths above 2 indicate processor congestion.)
Evaluating the Context Switches/Sec will give you an idea of how busy the system is.
The counter measures the number of times a thread voluntarily relinquishes the
processor, is preempted by a higher priority ready thread, or switches between user-mode
and privileged (kernel) mode to use an Executive or subsystem service.
The Percent Processor Time indicates the utilization of the processor measured in a
percentage. Average percentages higher than 50% usually indicate that the system could
benefit from an upgrade to a faster processor or multiple CPU system.
System Performance and Tuning Considerations
System Monitoring/Assessing the need for hardware upgrades
846 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
The Percent Interrupt Time indicates how often the system is handling hardware
related tasks. In the Process Control System, this will indicate where CPU congestion
might exist. Whether it is coming from the Control configuration or the process of
servicing clients. Evaluating this counter may assist you in customizing your system
configuration and usage to gain the best performance.
The Server Work Queue Length indicates the workload the server is performing. A
sustained queue length greater than four might indicate processor congestion.
You should evaluate all these counters before considering an upgrade for the CPU.
Faster Speed Processors will not always solve CPU performance problems. Some
systems will require the use of Multiple CPUs. If you are unsure of the CPU
requirements of your system, then you should purchase a system capable of supporting
Multiple CPUs. This leaves you the option of going to higher speed CPUs as well as the
ability to add a second.
Networking
Network utilization is best measured using third party tools to evaluate the Network
Hardware itself. However, you can gain knowledge by how a particular Server node is
performing by looking at the following counters:
Server Work Queues/Bytes Transferred/Sec
TCP/Segments/Sec
With these counters, you should also evaluate the network using the pre-installed
network diagnostic tools provided with the Network Drivers. Two exist depending on
Platform and Configuration:

3Com Diagnostic Tool: For use with 3Com Cards on the
following platforms: GX1, GX200,
PE300/500 Note 1, and PE1400/1500
Note 1.
Accessed by running Start, Programs,
3Com NIC Utilities, 3Com NIC Doctor.
Intel Pro Set: For use with Intel Pro Cards on following
platforms: PE300/500 and
PE1400/1500.
Accessed by running Start, Settings,
Control Panel and double clicking the
Intel ProSet Icon.

System Performance and Tuning Considerations
System Monitoring/Assessing the need for hardware upgrades
Release 100 Experion PKS Troubleshooting and Notifications Reference 847
1/03 Honeywell Part I
Experion PKS Clients utilize two types of methods to communicate with the Server. To
adequately evaluate the performance of this mechanism, it requires viewing both
counters at the server to determine how busy the network/server is performing these
tasks.
The Bytes Transferred/Sec shows how busy the Server is servicing network clients.
This is the rate at which the Server is sending and receiving bytes with the clients.
The TCP/Segments/Sec shows the amount of TCP traffic sent or received by the Server.


TIP
3Com cards are included if additional networking cards are specified in the
configuration on these platforms.


System Performance and Tuning Considerations
System Monitoring/Assessing the need for hardware upgrades
848 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Release 100 Experion PKS Troubleshooting and Notifications Reference 849
1/03 Honeywell Part I
Spare Parts
CNI Parts
General Notes



ATTENTION
Upon redundant controller switchover, the CNIs within the Redundant
Chassis Pair (RCP) are temporarily not visible on their respective ControlNet
segments. To ensure that the network is maintained, a minimum of two other
ControlNet Nodes must remain on the ControlNet segment during the
switchover operation. A method to avoid a single ControlNet node from going
lonely during RCP switchover is to add another CNI module, or another
Series A/H Rail Gateway module, or another Foundation Fieldbus Linking
Device to the same ControlNet segment. This additional ControlNet device is
commonly known as a Buddy Node.




ATTENTION
Note that after reprogramming the Secondary CNIs ControlNet parameters to
match that of the Primary CNI, the Secondary CNI must be power-cycled so
that redundant partner compatibility checks are re-attempted.

TC-CCN011

Description Single Media Series A ControlNet Interface Card.
FW Location \Program Files\Honeywell\Experion PKS\Engineering
Tools\System\Firmware\CNI\SeriesA\
Controller
Redundancy
Not supported. This implies that this CNI cannot be present in a
RCP. However, this CNI can be used in a remote I/O chassis or
as a Buddy Node.




CAUTION
At this time a TC-CCN011 cannot be used as a Buddy Node in a redundant
media system.

Spare Parts
CNI Parts
850 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
TC-CCR011

Description Redundant Media Series A ControlNet Interface Card.
FW Location \Program Files\Honeywell\Experion PKS\Engineering
Tools\System\Firmware\CNI\SeriesA\
Controller
Redundancy
Not supported. This implies that this CNI cannot be present in a
RCP. However, this CNI can be used in a remote I/O chassis or
as a Buddy Node.

TC-CCN012

Description Single Media Series C ControlNet Interface Card.
FW Location \Program Files\Honeywell\Experion PKS\Engineering
Tools\System\Firmware\CNI\SeriesC\
Controller
Redundancy
Supported.
Redundancy
Compatibility
The TC-CCN012 is compatible with another TC-CCN012 that has
the same ControlNet parameter configuration and firmware
revision.
Furthermore, the TC-CCN012 is compatible with the TC-CCN013
that has the same ControlNet parameter configuration with one
limitation: the TC-CCN012 must be in the primary redundancy
role. The intent of this design enhancement is to allow a customer
to migrate to the TC-CCN013 while on process. For example, if
the customer only has TC-CCN013 spares and a TC-CCN012
fails in a RCP, the customer {1} replaces the faulted TC-CCN012
in the secondary chassis with a TC-CCN013 (the RCP
synchronizes), {2} commands a switchover, and {3} replaces the
good TC-CCN012 in the secondary chassis with a TC-CCN013.
Upon switchover to the primary role, the TC-CCN013 is not
compatible with the TC-CCN012 because the TC-CCN013 has
more resources (e.g. memory) than the TC-CCN012.
Note that the ability to synchronize with a primary TC-CCN012
and secondary TC-CCN013 is only available starting in c4.20 and
d5.20 firmware revisions respectively.

Spare Parts
CNI Parts
Release 100 Experion PKS Troubleshooting and Notifications Reference 851
1/03 Honeywell Part I
TC-CCR012

Description Redundant Media Series C ControlNet Interface Card.
FW Location \Program Files\Honeywell\Experion PKS\Engineering
Tools\System\Firmware\CNI\SeriesC\
Controller
Redundancy
Supported.
Redundancy
Compatibility
The TC-CCR012 is compatible with another TC-CCR012 that has
the same ControlNet parameter configuration and firmware
revision.
Furthermore, the TC-CCR012 is compatible with the TC-CCR013
that has the same ControlNet parameter configuration with one
limitation: the TC-CCR012 must be in the primary redundancy
role. The intent of this design enhancement is to allow a customer
to migrate to the TC-CCR013 while on process. For example, if
the customer only has TC-CCR013 spares and a TC-CCR012
fails in a RCP, the customer {1} replaces the faulted TC-CCR012
in the secondary chassis with a TC-CCR013 (the RCP
synchronizes), {2} commands a switchover, and {3} replaces the
good TC-CCR012 in the secondary chassis with a TC-CCR013.
Upon switchover to the primary role, the TC-CCR013 is not
compatible with the TC-CCR012 because the TC-CCR013 has
more resources (e.g. memory) than the TC-CCR012.
Note that the ability to synchronize with a primary TC-CCR012
and secondary TC-CCR013 is only available starting in c4.20 and
d5.20 firmware revisions respectively.

TC-CCN013

Description Single Media Series D ControlNet Interface Card.
FW Location \Program Files\Honeywell\Experion PKS\Engineering
Tools\System\Firmware\CNI\SeriesD\
Controller
Redundancy
Supported.
Redundancy
Compatibility
The TC-CCN013 is compatible with another TC-CCN013 that has
the same ControlNet parameter configuration and firmware
revision.

Spare Parts
CNI Parts
852 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
TC-CCR013

Description Redundant Media Series D ControlNet Interface Card.
FW Location \Program Files\Honeywell\Experion PKS\Engineering
Tools\System\Firmware\CNI\SeriesD\
Controller
Redundancy
Supported.
Redundancy
Compatibility
The TC-CCR013 is compatible with another TC-CCR013 that has
the same ControlNet parameter configuration and firmware
revision.

Spare Parts
Periodic Maintenance Parts for PM I/O
Release 100 Experion PKS Troubleshooting and Notifications Reference 853
1/03 Honeywell Part I
Periodic Maintenance Parts for PM I/O
Periodic maintenance parts list
The following tables list items that may be required for maintenance during the life of the
Process Manager I/O components.
Batteries

Name Description Part Number
Set of 3 AA-size NiCad batteries 51190422-100 NiCad Rechargeable
Batteries
Set of 3 C-size NiCad batteries 51192060-100
Alkaline Batteries Set of 3 AA-size Alkaline batteries 51190467-100

Fuses

Name Description Qty Part Number
Assembly
Left 7-Slot Card File
(51401626)

2.0 A Subminiature fuse (F1-8)

8

30754661-021
Right 7-Slot Card File
(51401629)
2.0 A Subminiature fuse (F1-8)

8 30754661-021
15-Slot Card File
(51401629)
2.0 A Subminiature fuse (F1-16) 16 30754661-021
IOP Card File
(51402599)
2.0 A Subminiature fuse (F1-15)
0.5 A Subminiature fuse (F16)
15
1
30754661-021
30754661-014
3-30 Vdc SS DO FTA
(51304423)
5.0 A Time-delay fuse 5 x 20 mm 16 51190584-250
3-30 Vdc SS DO FTA
(51304650, 51309153)
2.5 A Time-delay fuse 5 x 20 mm 16 51190584-225
31-200 Vdc SS DO FTA
(51304428, 51309154)
1.0 A Time-delay fuse 5 x 20 mm 16 51190584-210
Spare Parts
Periodic Maintenance Parts for PM I/O
854 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
24-240 Vac SS DO FTA
(51304408)
3.0 A Time-delay fuse 5 x 20 mm 16 51190584-230
120/240 Vac SS DO
FTA (51304648)
2.5 A Time-delay fuse 5 x 20 mm 16 51190584-225
120 Vac Relay DO FTA
(51304443, 51309148)
6.0 A Time-delay fuse 5 x 20 mm 16 51190584-260
240 Vac Relay DO FTA
(51304427, 51309150)
3.0 A Time-delay fuse 5 x 20 mm 16 51190584-230
24 Vdc Nonisolated DO
FTA (51304446)
0.2 A Fast-action fuse 5 x 20 mm (F1-
16)
2.0 A Fast-action fuse 5 x 20 mm
(F17)
16
1
51190582-120
51190582-220
24 Vdc Isolated DO FTA
(80364013)
1.6 A Fast-action fuse MP16 (F1-4) 4 83957061-004
24 Vdc Isolated DO FTA
(80366183)
1.6 A Fast-action fuse MP16 (F1-16) 16 83957061-004
LLAI FTA (51304437,
51309202)
0.5 A Subminiature fuse (F1-4) 4 30754661-014
DI FTA (80364010,
80366180)
0.5 A Fast-action fuse MP05 (F1, F3) 2 83957061-002
DI FTA (80364010,
80366180)
1.0 A Fast-action fuse MP10 (F2) 1 83957061-003
DI Power Distribution
Assy (51304425)
1.0 A Fast-action fuse 5 x 20 mm (F1-
12)
12 51190582-210
Nonredundant AO FTA
(51304476)
1.0 A Fast-action fuse 5 x 20 mm (F1-
12
12 51190582-210
Redundant AO FTA
(51304335)
1.0 A Fast-action fuse 5 x 20 mm (F1-
3)
3 51190582-210
Redundant AO FTA
(80364007, 80366177,
80366481, 80366484)
1.0 A Fast-action fuse MP10 (F1) 1 83957061-003
Pulse Input FTA
(51304084)
0.25 A Fast-action fuse 5 x 20 mm
(F1-8)
8 51190582-125
Spare Parts
Periodic Maintenance Parts for PM I/O
Release 100 Experion PKS Troubleshooting and Notifications Reference 855
1/03 Honeywell Part I
Galvanic AO FTA
(51304638)
1.0 A Subminiature fuse (F1-3) 3 30754661-019
GI Power Distribution
Assy (51304644)
4.0 A Fast-action fuse 5 x 20 mm (F1-
8)
8 51190582-240
I/O Link Card 3.0 A Fast-action fuse (F1) 1 30754661-022
Fuseholder Puller Fuseholder extractor 51190586-100

Filters

Name Description Part Number
Filter Kit (Rittal cabinet) Louvered cover and filter, 20 /8 x 20 /8
(cm/in.)
51109488-100
Filter (Rittal cabinet) Replacement filter only, 20 /8 x 20 /8
(cm/in.)

51109488-200
Filter (Markhon cabinet) Replacement filter only, 39 /15.5 x 61 /24
(cm/in.)
51109541-100

Spare Parts
Optimum Replaceable Unit (ORU) Parts for PM I/O
856 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Optimum Replaceable Unit (ORU) Parts for PM I/O
ORU parts List
This subsection identifies the assemblies that may be required during the life of the
Process Manager I/O components.
Cables

Name Description Part Number
Power System to card file cable (Set
of two when ordered by model
number)

MU-KDPR01 1 meter 51201397-001
MU-KDPR02 1.5 meters 51201397-915
2 meters 51201397-002
3 meters 51201397-003
MU-KDPR04 4 meters 51201397-004
MU-KDPR05 5 meters 51201397-005
6 meters 51201397-006
8 meters 51201397-008
MU-KDPR10 10 meters 51201397-010
MU-KDPR15 15 meters 51201397-015
MU-KDPR20 20 meters 51201397-020
MU-KDPR25 25 meters 51201397-025
MU-KDPR30 30 meters 51201397-030
MU-KDPR35 35 meters 51201397-035
MU-KDPR40 40 meters 51201397-040
MU-KDPR45 45 meters 51201397-045
Power Cable
Nonshielded (For
internal cabinet use)
MU-KDPR50 50 meters 51201397-050
Spare Parts
Optimum Replaceable Unit (ORU) Parts for PM I/O
Release 100 Experion PKS Troubleshooting and Notifications Reference 857
1/03 Honeywell Part I
Name Description Part Number
Power System to card file cable Set
of two (With surge protection network
for I/O Link cable)

1.0 meter 51204126-001
1.5 meters 51204126-915
2 meters 51204126-002
3 meters 51204126-003
4 meters 51204126-004
5 meters 51204126-005
Power Cable
Nonshielded (internal
cabinet use)
6 meters 51204126-006
Power Cable Adapter
Cable Nonshield
(internal cabinet use)
Power cable I/O Link protector
adapter Set of two (Provides I/O
Link protector for 51201397-xxx cable)
51204127-100
Combination power and I/O link
interface cable used to connect the
I/O Link Interface Module to the IOP
card file and the IOP power system
(The cable includes leads for
connecting 24 Vdc power to the
Process Controller chassis power
supply.)

TC-KIOL02 2 meters 51202306-100
TC-KIOL05 5 meters 51202306-200
Power and I/O Link
Interface Cable
TC-KIOL10 10 meters 51202306-300
Power System to Power Distribution
Assembly cable (Set of two when
ordered by model number)

MU-KSPR05 5 meters 51204037-005
MU-KSPR10 10 meters 51204037-010
MU-KSPR15 15 meters 51204037-015
Power Cable Shielded
(For external cabinet
use)
MU-KSPR20 20 meters 51204037-020
Spare Parts
Optimum Replaceable Unit (ORU) Parts for PM I/O
858 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Name Description Part Number
MU-KSPR25 25 meters
MU-KSPR30 30 meters 51204037-030
MU-KSPR35 35 meters
MU-KSPR40 40 meters 51204037-040

MU-KSPR50 50 meters 51204037-050
Power System to card file cable Set
of two (With surge protection network
for I/O Link cable)

1.0 meter 51204138-001
1.5 meters 51204138-915
2 meters 51204138-002
3 meters 51204138-003
4 meters 51204138-004
5 meters 51204138-005
Power Cable Shielded
(For external cabinet
use)
6 meters 51204138-006
Power cable I/O Link protector
adapter Set of two (Provides I/O
Link protector for 51204037-xxx cable)
GI Power Distribution assembly to
FTA cable
51204140-100
0.50 meter 51109620-020
0.75 meter 51109620-030
1.00 meter 51109620-040
1.25 meters 51109620-050
2.00 meters 51109620-080
3.00 meters 51109620-120
4.00 meters 51109620-160
Galv Isolation FTA
Power Cable (For
internal cabinet use)
MU-KGPR05 5.00 meters 51109620-195
Spare Parts
Optimum Replaceable Unit (ORU) Parts for PM I/O
Release 100 Experion PKS Troubleshooting and Notifications Reference 859
1/03 Honeywell Part I
Name Description Part Number

MU-KGPR10 10.00 meters 51109620-390
Bridge cable for model MU/MC-
TDOY23 and MU/MC-TDOY63 FTAs

1.0 meter 80366198-100
Bridge Cable
2.0 meters 80366198-200
Power Adapter to LLMux/SDI/SI FTA
cable (External to the cabinet for
LLMux/SDI/SI)

Special order 51190696-xxx
76 meters 51190696-076
152 meters 51190696-152
Power Adapter Cable
(Non-CE Comply
Applications)
305 meters 51190696-305
Power Adapter to
LLMux/RHMUX/SDI/SI FTA cable
(External to the cabinet for
LLMux/SDI/SI) (Internal to the cabinet
for RHMUX)

Special order 51192139-104
MU-KLX076 76 meters 51192139-114
MU-KLX152 152 meters 51192139-124
Power Adapter Cable
(CE Compliant
Applications)

MU-KLX305 305 meters 51192139-134
RHMUX Power Adapter to RHMUX
FTA cable (External to the cabinet)

Special order 51197597-100
RHMUX Power Adapter
Cable (CE Compliant
Applications)
MU-KLO305 305 meters 51197597-305
Power Adapter to LLMux/SDI/SI FTA
cable (Internal to the cabinet)

MU-KLAM01 30 centimeters 51304465-100
Power Adapter Cable
(Non-CE Comply
Applications)
MU-KLAM02 66 centimeters 51304465-200
Spare Parts
Optimum Replaceable Unit (ORU) Parts for PM I/O
860 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Name Description Part Number
MU-KLAM03 100 centimeters 51304465-300
MU-KLAM06 200 centimeters 51304465-400

MU-KLAM09 300 centimeters 51304465-500
IOP card file communication cable
Two drop in cabinet 51195479-100
Three drop in cabinet 51195479-200
Four drop in cabinet 51195479-300
Five drop in cabinet 51195479-400
I/O Link Interface Cable
(Set of two)
Six drop in cabinet 51195479-500
IOP card file communication cable
Two drop in cabinet 51204042-100
Three drop in cabinet 51204042-200
Four drop in cabinet 51204042-300
Five drop in cabinet 51204042-400
I/O Link Interface Cable
(Set of two, shielded
for use in Europe)
Six drop in cabinet 51204042-500
IOP to FTA cable
1 meter 51201420-001
1.5 meters 51201420-915
MU-KFTA02 2.0 meters 51201420-002
MU-KFTA03 3.0 meters 51201420-003
MU-KFTA04 4.0 meters 51201420-004
MU-KFTA05 5.0 meters 51201420-005
6.0 meters 51201420-006
MU-KFTA08 8.0 meters 51201420-008
IOP to FTA
Cable
MU-KFTA10 10.0 meters 51201420-010
Spare Parts
Optimum Replaceable Unit (ORU) Parts for PM I/O
Release 100 Experion PKS Troubleshooting and Notifications Reference 861
1/03 Honeywell Part I
Name Description Part Number
MU-KFTA15 15.0 meters 51201420-015
MU-KFTA20 20.0 meters 51201420-020
MU-KFTA25 25.0 meters 51201420-025
MU-KFTA30 30.0 meters 51201420-030
MU-KFTA35 35.0 meters 51201420-035
MU-KFTA40 40.0 meters 51201420-040
MU-KFTA45 45.0 meters 51201420-045

MU-KFTA50 50.0 meters 51201420-050
IOP to FTA cable
1 meter 51204033-001
1.5 meters 51204033-915
MU-KFTS02 2.0 meters 51204033-002
MU-KFTS03 3.0 meters 51204033-003
MU-KFTS04 4.0 meters 51204033-004
MU-KFTS05 5.0 meters 51204033-005
6.0 meters 51204033-006
MU-KFTS08 8.0 meters 51204033-008
MU-KFTS10 10.0 meters 51204033-010
MU-KFTS15 15.0 meters 51204033-015
MU-KFTS20 20.0 meters 51204033-020
MU-KFTS25 25.0 meters 51204033-025
MU-KFTS30 30.0 meters 51204033-030
MU-KFTS35 35.0 meters 51204033-035
MU-KFTS40 40.0 meters 51204033-040
IOP to FTA
Cable (Shielded
for external
cabinet use)
MU-KFTS45 45.0 meters 51204033-045
Spare Parts
Optimum Replaceable Unit (ORU) Parts for PM I/O
862 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Name Description Part Number
MU-KFTS50 50.0 meters 51204033-050

Power system components - non-conformally coated

Name Description Part Number
Power Supply Module Standard 20 A Power Supply Module 51109456-200
Power Supply Module AC Only 8 A Power Supply Module 51190465-100
Power Supply Module AC Only 16 A Power Supply Module 51190465-200
48 V Battery Backup 48 V Battery Pack assembly 51303948-100
AC/DC Distribution
Assembly
AC Only power control and distribution
board 115 Vac dual PSMs
51401135-100
AC/DC Distribution
Assembly
AC Only power control and distribution
board 115 Vac single PSM
51401135-200
AC/DC Distribution
Assembly
AC Only power control and distribution
board 230 Vac dual PSMs
51401135-300
AC/DC Distribution
Assembly
AC Only power control and distribution
board 230 Vac single PSM
51401135-400
CMOS Battery Backup
Assembly
PS Charger/monitor for CMOS
memory
51309206-100
Power System
Backpanel Assy
Power System backpanel 51404172-100

Spare Parts
Optimum Replaceable Unit (ORU) Parts for PM I/O
Release 100 Experion PKS Troubleshooting and Notifications Reference 863
1/03 Honeywell Part I
Power system components - conformally coated

Name Description Part Number
Power Supply Module Standard 20 A Power Supply
Module
51109456-200
Power Supply Module AC Only 8 A Power Supply
Module
51190465-150
Power Supply Module AC Only 16 A Power Supply
Module
51190465-250
48 V Battery Backup 48 V Battery Pack assembly 51303948-100
AC/DC Distribution
Assembly
AC Only power control and
distribution board 115 Vac dual
PSMs
51401135-150
AC/DC Distribution
Assembly
AC Only power control and
distribution board 115 Vac single
PSM
51401135-250
AC/DC Distribution
Assembly
AC Only power control and
distribution board 230 Vac dual
PSMs
51401135-350
AC/DC Distribution
Assembly
AC Only power control and
distribution board 230 Vac single
PSM
51401135-450
CMOS Battery Backup
Assembly
PS Charger/monitor for CMOS
memory
51309206-150
Power System
Backpanel Assy
Power System backpanel 51404172-150



Spare Parts
Optimum Replaceable Unit (ORU) Parts for PM I/O
864 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
IOP cards - non-conformally coated

Name Description Part Number
HLAI IOP (MU-PAIH02) High Level Analog Input card
(Replaced by 51304754-100)
51304489-100
HLAI IOP (MU-PAIH03) High Level Analog Input card 51304754-100
LLAI IOP (MU-PAIL02) Low Level Analog Input card 51304481-100
LLMux IOP (MU-
PLAM02)
Low Level Multiplexer card 51304362-100
RHMUX(MU-PRHM01) Remote Hardened Low Level
Multiplexer card
51404109-125
DI IOP (MU-PDIX02) Digital Input card 51304485-100
DI IOP (MU-PDIY22) Digital Input card 80363972-100
AO IOP (MU-PAOX02) Analog Output 51304483-100
AO IOP (MU-PAOX03) Analog Output card (Replaced by
51309152-175)
51304672-100
AO IOP (MU-PAOX03) Analog Output card (Conformally
Coated)
51309152-175
AO IOP (MU-PAOY22) Analog Output card 80363969-100
DO IOP (MU-PDOX02) Digital Output card 51304487-100
DO IOP (MU-PDOY22) Digital Output card 80363975-100
STI IOP (MU-PSTX02) Smart Transmitter Interface card
(Replaced by 51304516-200)
51304516-100
STI_MV (MU-PSTX03) Smart Transmitter Interface
Multivariable
51304516-200
DISOE IOP (MU-
PDIS11)
Digital Input Sequence Of Events
card (Replaced by 51402625-125)
51304690-100
DISOE IOP (MU-
PDIS12)
Digital Input Sequence Of Events
card
51402625-125
Slot Filler Empty IOP slot filler card 51304260-200

Spare Parts
Optimum Replaceable Unit (ORU) Parts for PM I/O
Release 100 Experion PKS Troubleshooting and Notifications Reference 865
1/03 Honeywell Part I
IOP cards - conformally coated

Name Description Part Number
HLAI IOP (MC-PAIH02) High Level Analog Input card 51304489-150
HLAI IOP (MC-PAIH03) High Level Analog Input card 51304754-150
LLAI IOP (MC-PAIL02) Low Level Analog Input card 51304481-150
LLMux IOP (MC-
PLAM02)
Low Level Multiplexer card 51304362-150
RHMUX(MC-PRHM01) Remote Hardened Low Level
Multiplexer card
51404109-175
DI IOP (MC-PDIX02) Digital Input card 51304485-150
DI IOP (MC-PDIY22) Digital Input card 80363972-150
AO IOP (MC-PAOX02) Analog Output 51304483-150
AO IOP (MC-PAOX03) Analog Output card (Replaced by
51309152-175)
51304672-150
AO IOP (MC-PAOX03) Analog Output card 51309152-175
AO IOP (MC-PAOY22) Analog Output card 80363969-150
DO IOP (MC-PDOX02) Digital Output card 51304487-150
DO IOP (MC-PDOY22) Digital Output card 80363975-150
STI IOP (MC-PSTX02) Smart Transmitter Interface card
(Replaced by 51304516-200)
51304516-150
STI_MV IOP (MC-
PSTX03)
Smart Transmitter Interface
Multivariable
51304516-250
DISOE IOP (MC-
PDIS11)
Digital Input Sequence Of Events
card (Replaced by 51402625-125)
51304690-150
DISOE IOP (MC-
PDIS12)
Digital Input Sequence Of Events
card
51402625-175
Slot Filler Empty IOP slot filler card 51304260-250

Spare Parts
Optimum Replaceable Unit (ORU) Parts for PM I/O
866 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
I/O LINK Extender components - non-conformally coated

Name Description Part Number
Standard I/O Link Extender card 51304419-100
Standard fiber optic Tx/Rx coupler
(1)
51201557-100
Standard I/O Link
Extender (MU-IOLM02)
Standard fiber optic Tx/Rx coupler
(3)
51201557-300
Long Distance I/O Link Extender
card
51304532-100 Long Distance I/O Link
Extender (MU-ILDX02
Replaced by MU-
ILDX03)
Long Distance fiber optic Tx/Rx
coupler (1)
51201616-100
Long Distance I/O Link Extender
card
51304532-100 Long Distance I/O Link
Extender (MU-ILDX03)
Long Distance fiber optic Tx/Rx
coupler (1)
51309208-100
I/O Link Extender
Adapter Kit (MU-
ILES01)
I/O Link Extender Adapter kit 51204043-100

Spare Parts
Optimum Replaceable Unit (ORU) Parts for PM I/O
Release 100 Experion PKS Troubleshooting and Notifications Reference 867
1/03 Honeywell Part I
I/O LINK Extender components - conformally coated

Name Description Part Number
Standard I/O Link Extender card 51304419-150
Standard fiber optic Tx/Rx coupler
(1)
51201557-150
Standard I/O Link
Extender (MC-IOLM02)
Standard fiber optic Tx/Rx coupler
(3)
51201557-350
Long Distance I/O Link Extender
card
51304532-150 Long Distance I/O Link
Extender (MC-ILDX02
Replaced by MC-
ILDX03)
Long Distance fiber optic Tx/Rx
coupler (1)
51201616-150
Long Distance I/O Link Extender
card
51304532-150 Long Distance I/O Link
Extender (MC-ILDX03)
Long Distance fiber optic Tx/Rx
coupler (1)
51309208-150

Standard FTA components - non-conformally coated

Name Description Part Number
HLAI/STI FTA
(MU-TAIH02)
HLAI/STI with compression
terminals
51304453-100
HLAI/STI FTA
(MU-TAIH12)
HLAI/STI with compression
terminals
51304337-100
HLAI/STI with compression
terminals
80366195-100 HLAI/STI FTA
(MU-TAIH22)
AI Adapter Module for the above
FTA
80367163-001
HLAI/STI FTA
(MU-TAIH52)
HLAI/STI with screw terminals 51304337-200
HLAI/STI with screw terminals 80366192-100 HLAI/STI FTA
(MU-TAIH62)
AI Adapter Module for the above
FTA
80360713-001
Spare Parts
Optimum Replaceable Unit (ORU) Parts for PM I/O
868 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Name Description Part Number
HLAI FTA
(MU-TAIH03)
HLAI with compression terminals 51309136-125
HLAI FTA
(MU-TAIH13)
HLAI with compression terminals 51309138-125
HLAI with compression terminals 80369165-125 HLAI FTA
(MU-TAIH23)
AI Adapter Module for the above
FTA
80367163-001
HLAI FTA
(MU-TAIH53)
HLAI with screw terminals 51309138-225
STI FTA (MU-TSTX03) STI with compression terminals 51309140-125
STI FTA (MU-TSTX13) STI with compression terminals 51309142-125
STI FTA (MU-TSTX53) STI with screw terminals 51309142-225
LLAI FTA with compression
terminals (Replaced by MU-
TAIL03)
51304437-100 LLAI FTA (MU-TAIL02)
Daughter module for above FTA
(Replaced by 51309280-100)
51304085-100
LLAI FTA with compression
terminals
51309202-125 LLAI FTA (MU-TAIL03)
Daughter module for above FTA 51309280-100
LLMux local TC with compression
terminals (Replaced by MU-
TAMT03)
51401491-100 LLMux FTA
(MU-TAMT02)
LLMux Analog board for above
FTA
51401564-100
LLMux FTA
(MU-TAMT03)
LLMux local TC with compression
terminals
51409223-125
LLMux remote TC with
compression terminals (Replaced
by MU-TAMT13)
51401573-100 LLMux FTA
(MU-TAMT12)
LLMux Analog board for above
FTA
51401564-100
Spare Parts
Optimum Replaceable Unit (ORU) Parts for PM I/O
Release 100 Experion PKS Troubleshooting and Notifications Reference 869
1/03 Honeywell Part I
Name Description Part Number
LLMux remote sensor board for
above FTA
51304589-100
LLMux FTA
(MU-TAMT13)
LLMux remote TC with
compression terminals
51409213-125
LLMux RTD with compression
terminals (Replaced by MU-
TAMR03)
51304477-100 LLMux FTA
(MU-TAMR02)
LLMux daughter board for above
FTA
51401364-100
LLMux FTA
(MU-TAMR03)
LLMux RTD with compression
terminals
51309218-125
RHMUX GI/IS Power
Adapter (MU-GRPA01)
RHMUXGI/IS Power Adapter with
compression terminals
51304724-125
RHMUX GI/NI Power
Adapter (MU-TRPA01)
RHMUX GI/NI Power Adapter with
compression terminals
51304722-125
AO FTA (MU-THAO11) Analog Output with HART and
comp. terminals
51309542-125
AO FTA (MU-TAOX02) Analog Output with compression
terminals
51304476-125
AO FTA (MU-TAOX12) Analog Output with compression
terminals
51304335-125
Analog Output with screw
terminals
51304335-225 AO FTA (MU-TAOX52)
Plug-in module for above FTAs 51304338-100
AO FTA (MU-TAOY22) Analog Output with comp term,
Stdby Manual
80366481-125
AO FTA (MU-TAOY23) Analog Output with comp term, no
Stdby Manual
80366177-200
AO FTA (MU-TAOY52) Analog Output with screw term,
Stdby Manual
80366484-125
DI 120 Vac FTA
(MU-TDIA12)
Digital Input 120 Vac with
compression terminals
51304439-125
Spare Parts
Optimum Replaceable Unit (ORU) Parts for PM I/O
870 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Name Description Part Number
Digital Input 120 Vac with fixed-
screw terminals
51304439-225 DI 120 Vac FTA
(MU-TDIA52)
Plug-in module for above FTAs 51190523-225
DI 120 Vac FTA
(MU-TDIA72)
Digital Input 120 Vac with
removable screw term
51303930-100
DI 240 Vac FTA
(MU-TDIA22)
Digital Input 240 Vac with
compression terminals
51304431-125
Digital Input 240 Vac with fixed-
screw terminals
51304431-225 DI 240 Vac FTA
(MU-TDIA62)
Plug-in module for above FTAs 51190523-325
DI 24 Vdc FTA
(MU-TDID12)
Digital Input 24 Vdc with
compression terminals
51304441-125
Digital Input 24 Vdc with fixed-
screw terminals
51304441-225 DI 24 Vdc FTA
(MU-TDID52)
Plug-in module for above FTAs 51190523-125
DI 24 Vdc FTA
(MU-TDID72)
Digital Input 24 Vdc with
removable screw term
51303928-100
DI 24 Vdc FTA
(MU-TDIY22)
Digital Input 24 Vdc with
compression terminals
80366180-125
DI 24 Vdc FTA
(MU-TDIY62)
Digital Input 24 Vdc with screw
terminals
80364010-125
DO 120/240 Vac FTA
(MU-TDOA12)
Digital Output 120/240 Vac SS
with fixed-comp term (Replaced
by MU-TDOA13)
51304408-100
Digital Output 120/240 Vac SS
with fixed-screw term (Replaced
by MU-TDOA53)
51304408-200 DO 120/240 Vac FTA
(MU-TDOA52)
Solid-state relay plug-in module
for above FTAs
51190516-325
DO 120/240 Vac FTA
(MU-TDOA13)
Digital Output 24-240 Vac SS with
removable compression terminals.
51304648-125
Spare Parts
Optimum Replaceable Unit (ORU) Parts for PM I/O
Release 100 Experion PKS Troubleshooting and Notifications Reference 871
1/03 Honeywell Part I
Name Description Part Number
Digital Output 24-240 Vac SS with
removable screw terminals
51304648-225 DO 120/240 Vac FTA
(MU-TDOA53)
Solid-state relay plug-in module
for above FTAs
51190516-332
DO 3-30 Vdc FTA
(MU-TDOD12)
Digital Output 3-30 Vdc SS with
fixed-comp term (Replaced by
MU-TDOD13)
51304423-100
Digital Output 3-30 Vdc SS with
fixed-screw term (Replaced by
MU-TDOD53)
51304423-200 DO 3-30 Vdc FTA
(MU-TDOD52)
Solid-state relay plug-in module
for above FTAs
51190516-122
DO 3-30 Vdc FTA
(MU-TDOD13)
Digital Output 3-30 Vdc SS with
removable compression terminals
51304650-100
Digital Output 3-30 Vdc SS with
removable screw terminals
51304650-200 DO 3-30 Vdc FTA
(MU-TDOD53)
Solid-state relay plug-in module
for above FTAs
51190516-132
DO 3-30 Vdc FTA
(MU-TDOD14)
Digital Output 3-30 Vdc SS with
fixed-compression terminals
51309153-125
Digital Output 3-30 Vdc SS with
fixed-screw terminals
51309153-225 DO 3-30 Vdc FTA
(MU-TDOD54)
Solid-state relay plug-in module
for above FTAs
51190516-134
DO 31-200 Vac FTA
(MU-TDOD22)
Digital Output 31-200 Vdc SS with
compression terminals
51304428-100
Digital Output 31-200 Vdc SS with
screw terminals
51304428-200 DO 31-200 Vac FTA
(MU-TDOD62)
Solid-state relay plug-in module
for above FTAs
51190516-402
DO 31-200 Vac FTA
(MU-TDOD23)
Digital Output 31-200 Vdc SS with
compression terminals
51309154-125
Spare Parts
Optimum Replaceable Unit (ORU) Parts for PM I/O
872 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Name Description Part Number
Digital Output 31-200 Vdc SS with
screw terminals
51309154-225 DO 31-200 Vac FTA
(MU-TDOD63)
Solid-state relay plug-in module
for above FTAs
51190516-404
DO 24 Vdc FTA
(MU-TDON12)
Digital Output 24 Vdc nonisolated
with comp term
51304446-100
DO 24 Vdc FTA
(MU-TDON52)
Digital Output 24 Vdc nonisolated
with screw term
51304446-200
DO 24 Vdc FTA
(MU-TDOY22)
Digital Output 24 Vdc isolated with
comp term
80366183-125
DO 24 Vdc FTA
(MU-TDOY62)
Digital Output 24 Vdc isolated with
screw terminals
80364013-125
DO 120 Vac Relay
(MU-TDOR12)
DO 120 Vac/125 Vdc with
compression terminals (Replaced
by 51309148-125)
51304443-150
DO 120 Vac/125 Vdc with screw
terminals (Replaced by
51309148-225)
51304443-250 DO 120 Vac Relay
(MU-TDOR52)
Relay plug-in module for above
assemblies
51191945-100
DO 120 Vac Relay
(MU-TDOR12)
DO 120 Vac/125 Vdc with
compression terminals
51309148-125
DO 120 Vac Relay
(MU-TDOR52)
DO 120 Vac/125 Vdc with screw
terminals
51309148-225
DO 240 Vac Relay
(MU-TDOR22)
DO 240 Vac/125 Vdc with
compression terminals (Replaced
by 51309150-125)
51304427-100
DO 240 Vac/125 Vdc with screw
terminals (Replaced by
51309150-225)
51304427-200 DO 240 Vac Relay
(MU-TDOR62)
Relay plug-in module for above
assemblies
51191945-100
Spare Parts
Optimum Replaceable Unit (ORU) Parts for PM I/O
Release 100 Experion PKS Troubleshooting and Notifications Reference 873
1/03 Honeywell Part I
Name Description Part Number
DO 240 Vac Relay
(MU-TDOR22)
DO 240 Vac/125 Vdc with
compression terminals
51309150-125
DO 240 Vac/125 Vdc with screw
terminals
51309150-225 DO 240 Vac Relay
(MU-TDOR62)
Relay plug-in module for above
assemblies
51191945-100
DO 240 Vac Relay
(MU-TDOY23)
DO 240 Vac/125 Vdc with
compression terminals
80366189-125
DO 240 Vac/125 Vdc with screw
terminals
80366186-125
Relay (NT1) for above assemblies 83970001-110
DO 240 Vac Relay
(MU-TDOY63)
Jumper for above assemblies 51190610-101
DI Power Dist Assy
(MU-TDPR02)
Digital Input Power Distribution
Assembly
51304425-125
DO Standby Manual
(MU-SMDC02)
Digital Output Standby Manual
Device with case
51304526-100
DO Standby Manual
(MU-SMDX02)
Digital Output Standby Manual
Device with case and cable
51304527-100
AO Standby Manual
(MU-SMAC02)
Analog Output Standby Manual
Device Assy with cable
51401277-100
Manual/Auto Station
(MU-MASX02)
Honeywell Manual/Auto Station
(part number PC6001-U-2MO-40-
A0)


Spare Parts
Optimum Replaceable Unit (ORU) Parts for PM I/O
874 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Standard FTA components - conformally coated

Name Description Part Number
HLAI/STI FTA
(MC-TAIH02)
HLAI/STI with compression
terminals
51304453-150
HLAI/STI FTA
(MC-TAIH12)
HLAI/STI with compression
terminals
51304337-150
HLAI/STI with compression
terminals
80366195-150 HLAI/STI FTA
(MC-TAIH22)
AI Adapter Module for the above
FTA
80367163-001
HLAI/STI FTA
(MC-TAIH52)
HLAI/STI with screw terminals 51304337-250
HLAI/STI with screw terminals 80366192-150 HLAI/STI FTA
(MC-TAIH62)
AI Adapter Module for the above
FTA
80360713-001
HLAI FTA
(MC-TAIH03)
HLAI with compression terminals 51309136-175
HLAI FTA
(MC-TAIH13)
HLAI with compression terminals 51309138-175
HLAI with compression terminals 80369165-175 HLAI FTA
(MC-TAIH23)
AI Adapter Module for the above
FTA
80367163-001
HLAI FTA
(MC-TAIH53)
HLAI with screw terminals 51309138-275
STI FTA (MC-TSTX03) STI with compression terminals 51309140-175
STI FTA (MC-TSTX13) STI with compression terminals 51309142-175
STI FTA (MC-TSTX53) STI with screw terminals 51309142-275
LLAI FTA with compression
terminals (Replaced by MC-
TAIL03)
51304437-150 LLAI FTA (MC-TAIL02)
Daughter module for above FTA
(Replaced by 51309280-100)
51304085-150
Spare Parts
Optimum Replaceable Unit (ORU) Parts for PM I/O
Release 100 Experion PKS Troubleshooting and Notifications Reference 875
1/03 Honeywell Part I
Name Description Part Number
LLAI FTA with compression
terminals
51309202-175 LLAI FTA (MC-TAIL03)
Daughter module for above FTA 51309280-100
LLMux local TC with compression
terminals (Replaced by MC-
TAMT03)
51401491-150 LLMux FTA
(MC-TAMT02)
LLMux Analog board for above
FTA
51401564-150
LLMux FTA
(MC-TAMT03)
LLMux local TC with compression
terminals
51409223-175
LLMux remote TC with
compression terminals (Replaced
by MC-TAMT13)
51401573-150
LLMux Analog board for above
FTA
51401564-150
LLMux FTA
(MC-TAMT12)
LLMux remote sensor board for
above FTA
51304589-150
LLMux FTA
(MC-TAMT13)
LLMux remote TC with
compression terminals
51409213-175
LLMux RTD with compression
terminals (Replaced by MC-
TAMR03)
51304477-150 LLMux FTA
(MC-TAMR02)
LLMux daughter board for above
FTA
51401364-100
LLMux FTA
(MC-TAMR03)
LLMux RTD with compression
terminals
51309218-125
RHMUX FTA
(MC-GRMT01)
RHMUX TC with screw terminals 51404106-175
RHMUX GI/IS Power
Adapter (MC-GRPA01)
RHMUXGI/IS Power Adapter with
compression terminals
51304724-175
RHMUX GI/NI Power
Adapter (MC-TRPA01)
RHMUX GI/NI Power Adapter with
compression terminals
51304722-175
Spare Parts
Optimum Replaceable Unit (ORU) Parts for PM I/O
876 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Name Description Part Number
AO FTA (MC-THAO11) Analog Output with HART and
comp. terminals
51309542-175
AO FTA (MC-TAOX02) Analog Output with compression
terminals
51304476-175
AO FTA (MC-TAOX12) Analog Output with compression
terminals
51304335-175
Analog Output with screw
terminals
51304335-275 AO FTA (MC-TAOX52)
Plug-in module for above FTAs 51304338-150
AO FTA (MC-TAOY22) Analog Output with comp term,
Stdby Manual
80366481-175
AO FTA (MC-TAOY23) Analog Output with comp term, no
Stdby Manual
80366177-250
AO FTA (MC-TAOY52) Analog Output with screw term,
Stdby Manual
80366484-175
AO FTA (MC-TAOY53) Analog Output with screw term,
no Stdby Manual
80364007-250
DI 120 Vac FTA
(MC-TDIA12)
Digital Input 120 Vac with
compression terminals
51304439-175
Digital Input 120 Vac with fixed-
screw terminals
51304439-275 DI 120 Vac FTA
(MC-TDIA52)
Plug-in module for above FTAs 51190523-225
DI 120 Vac FTA
(MC-TDIA72)
Digital Input 120 Vac with
removable screw term
51303930-150
DI 240 Vac FTA
(MC-TDIA22)
Digital Input 240 Vac with
compression terminals
51304431-175
Digital Input 240 Vac with fixed-
screw terminals
51304431-275 DI 240 Vac FTA
(MC-TDIA62)
Plug-in module for above FTAs 51190523-325
DI 24 Vdc FTA
(MC-TDID12)
Digital Input 24 Vdc with
compression terminals
51304441-175
Spare Parts
Optimum Replaceable Unit (ORU) Parts for PM I/O
Release 100 Experion PKS Troubleshooting and Notifications Reference 877
1/03 Honeywell Part I
Name Description Part Number
Digital Input 24 Vdc with fixed-
screw terminals
51304441-275 DI 24 Vdc FTA
(MC-TDID52)
Plug-in module for above FTAs 51190523-125
DI 24 Vdc FTA
(MC-TDID72)
Digital Input 24 Vdc with
removable screw term
51303928-150
DI 24 Vdc FTA
(MC-TDIY22)
Digital Input 24 Vdc with
compression terminals
80366180-175
DI 24 Vdc FTA
(MC-TDIY62)
Digital Input 24 Vdc with screw
terminals
80364010-175
DO 120/240 Vac FTA
(MC-TDOA12)
Digital Output 120/240 Vac SS
with fixed-comp term (Replaced
by MC-TDOA13)
51304408-150
Digital Output 120/240 Vac SS
with fixed-screw term (Replaced
by MC-TDOA53)
51304408-250 DO 120/240 Vac FTA
(MC-TDOA52)
Solid-state relay plug-in module
for above FTAs
51190516-325
DO 120/240 Vac FTA
(MC-TDOA13)
Digital Output 24-240 Vac SS with
removable compression terminals.
51304648-175
Digital Output 24-240 Vac SS with
removable screw terminals
51304648-275 DO 120/240 Vac FTA
(MC-TDOA53)
Solid-state relay plug-in module
for above FTAs
51190516-332
DO 3-30 Vdc FTA
(MC-TDOD12)
Digital Output 3-30 Vdc SS with
fixed-comp term (Replaced by
MC-TDOD13)
51304423-150
Digital Output 3-30 Vdc SS with
fixed-screw term (Replaced by
MC-TDOD53)
51304423-250 DO 3-30 Vdc FTA
(MC-TDOD52)
Solid-state relay plug-in module
for above FTAs
51190516-122
DO 3-30 Vdc FTA
(MC-TDOD13)
Digital Output 3-30 Vdc SS with
removable compression terminals
51304650-150
Spare Parts
Optimum Replaceable Unit (ORU) Parts for PM I/O
878 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Name Description Part Number
Digital Output 3-30 Vdc SS with
removable screw terminals
51304650-250 DO 3-30 Vdc FTA
(MC-TDOD53)
Solid-state relay plug-in module
for above FTAs
51190516-132
DO 3-30 Vdc FTA
(MC-TDOD14)
Digital Output 3-30 Vdc SS with
fixed-compression terminals
51309153-175
Digital Output 3-30 Vdc SS with
fixed-screw terminals
51309153-275 DO 3-30 Vdc FTA
(MC-TDOD54)
Solid-state relay plug-in module
for above FTAs
51190516-134
DO 31-200 Vac FTA
(MC-TDOD22)
Digital Output 31-200 Vdc SS with
compression terminals
51304428-150
Digital Output 31-200 Vdc SS with
screw terminals
51304428-250 DO 31-200 Vac FTA
(MC-TDOD62)
Solid-state relay plug-in module
for above FTAs
51190516-402
DO 31-200 Vac FTA
(MC-TDOD23)
Digital Output 31-200 Vdc SS with
compression terminals
51309154-175
Digital Output 31-200 Vdc SS with
screw terminals
51309154-275 DO 31-200 Vac FTA
(MC-TDOD63)
Solid-state relay plug-in module
for above FTAs
51190516-404
DO 24 Vdc FTA
(MC-TDON12)
Digital Output 24 Vdc nonisolated
with comp term
51304446-150
DO 24 Vdc FTA
(MC-TDON52)
Digital Output 24 Vdc nonisolated
with screw term
51304446-250
DO 24 Vdc FTA
(MC-TDOY22)
Digital Output 24 Vdc isolated with
comp term
80366183-175
DO 24 Vdc FTA
(MC-TDOY62)
Digital Output 24 Vdc isolated with
screw terminals
80364013-175
DO 120 Vac Relay
(MC-TDOR12)
DO 120 Vac/125 Vdc with
compression terminals (Replaced
by 51309148-175)
51304443-150
Spare Parts
Optimum Replaceable Unit (ORU) Parts for PM I/O
Release 100 Experion PKS Troubleshooting and Notifications Reference 879
1/03 Honeywell Part I
Name Description Part Number
DO 120 Vac/125 Vdc with screw
terminals (Replaced by
51309148-275)
51304443-250 DO 120 Vac Relay
(MC-TDOR52)
Relay plug-in module for above
assemblies
51191945-100
DO 120 Vac Relay
(MC-TDOR12)
DO 120 Vac/125 Vdc with
compression terminals
51309148-175
DO 120 Vac Relay
(MC-TDOR52)
DO 120 Vac/125 Vdc with screw
terminals
51309148-275
Relay plug-in module for above
assemblies
51191945-100
DO 240 Vac Relay
(MC-TDOR22)
DO 240 Vac/125 Vdc with
compression terminals (Replaced
by 51309150-125)
51304427-150
DO 240 Vac/125 Vdc with screw
terminals (Replaced by
51309150-225)
51304427-250 DO 240 Vac Relay
(MC-TDOR62)
Relay plug-in module for above
assemblies
51191945-100
DO 240 Vac Relay
(MC-TDOR22)
DO 240 Vac/125 Vdc with
compression terminals
51309150-175
DO 240 Vac/125 Vdc with screw
terminals
51309150-275 DO 240 Vac Relay
(MC-TDOR62)
Relay plug-in module for above
assemblies
51191945-150
DO 240 Vac Relay
(MC-TDOY23)
DO 240 Vac/125 Vdc with
compression terminals
80366189-175
DO 240 Vac/125 Vdc with screw
terminals
80366185-175
Relay (NT1) for above assemblies 83970001-110
DO 240 Vac Relay
(MC-TDOY63)
Jumper for above assemblies 51190610-101
Power Adapter
(MC-TLPA02)
Power Adapter (Used with LLMux) 51309204-175
Spare Parts
Optimum Replaceable Unit (ORU) Parts for PM I/O
880 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Name Description Part Number
DI Power Dist Assy
(MC-TDPR02)
Digital Input Power Distribution
Assembly
51304425-175
DO Standby Manual
(MC-SMDC02)
Digital Output Standby Manual
Device with case
51304526-150
DO Standby Manual
(MC-SMDX02)
Digital Output Standby Manual
Device with case and cable
51304527-150
AO Standby Manual
(MC-SMAC02)
Analog Output Standby Manual
Device Assy with cable
51401277-150

Spare Parts
Optimum Replaceable Unit (ORU) Parts for PM I/O
Release 100 Experion PKS Troubleshooting and Notifications Reference 881
1/03 Honeywell Part I
Galvanically Isolated FTA components - non-conformally coated

Name Description Part Number
HLAI FTA
(MU-GAIH12)
HLAI FTA with GI Modules
(Compress terminals) (Replaced
by MU-GAIH13 51304718-125)
51304636-100
HLAI FTA with GI Modules (Crimp
terminals) (Replaced by MU-
GAIH83 51304718-325)
51304636-300 HLAI FTA
(MU-GAIH82)
HLAI Galvanic Isolation Module
(MTL4041)
51191697-100
HLAI FTA
(MU-GAIH13)
HLAI FTA with GI Modules
(Compress terminals)
51304718-125
HLAI FTA with GI Modules (Crimp
terminals)
51304718-325 HLAI FTA
(MU-GAIH83)
HLAI Galvanic Isolation Module
(MTL4041B)
51191697-200
HLAI FTA
(MU-GAIH14)
HLAI FTA with GI Modules
(Compress terminals)
51304730-125
HLAI FTA with GI Modules (Crimp
terminals)
51304730-325 HLAI FTA
(MU-GAIH84)
HLAI Galvanic Isolation Module
MTL4041P)
51191928-100
HLAI FTA
(MU-GAIH22)
HLAI FTA with GI Modules
(Compress terminals)
51304748-125
HLAI FTA with GI Modules (Crimp
terminals)
51304748-325 HLAI FTA
(MU-GAIH92)
HLAI Galvanic Isolation Module
(MTL4041B)
51191697-200
HLAI Calibration Tool HLAI calibration tool 51201450-100
24 Vdc DI FTA
(MU-GDID12)
24 Vdc DI FTA with GI Modules
(Compress Term)
51304640-125
24 Vdc DI FTA
(MU-GDID82)
24 Vdc DI FTA with GI Modules
(Crimp Terminals)
51304640-325
Spare Parts
Optimum Replaceable Unit (ORU) Parts for PM I/O
882 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Name Description Part Number
24 Vdc DI Galvanic Isolation
Module (MTL4016)
51191699-100
24 Vdc DI FTA
(MU-GDID13)
24 Vdc DI FTA with GI Modules
(Compress Term)
51304728-125
24 Vdc DI FTA with GI Modules
(Crimp Terminals)
51304728-325 24 Vdc DI FTA
(MU-GDID83)
24 Vdc DI Galvanic Isolation
Module (MTL4013)
51191926-100
AO FTA
(MU-GHAO11)
AO nonredun FTA with HART and
Comp Term
51309540-125
AO FTA
(MU-GAOX02)
AO nonredun FTA with GI
Modules (Comp Term)
51304638-125
AO FTA
(MU-GAOX72)
AO nonredun FTA with GI
Modules (Crimp Term)
51304638-325
AO FTA
(MU-GAOX12)
AO redundant FTA with GI
Modules (Comp Term)
51304638-525
AO redundant FTA with GI
Modules (Crimp Term)
51304638-725
AO Galvanic Isolation Module
(MTL4045C)
51192097-200
AO Galvanic Isolation Module
(MTL4046P)
51192565-100
AO FTA
(MU-GAOX82)
Redundancy Module for FTA 51304338-100
DO FTA
(MU-GDOD12)
DO FTA with GI Modules
(Compression Terminals)
51304642-125
DO FTA with GI Modules (Crimp
Terminals)
51304642-325 DO FTA
(MU-GDOD82)
DO Galvanic Isolation Module
(MTL4021)
51191698-100
DO FTA
(MU-GDOL12)
DO FTA with GI Modules
(Compression Terminals)
51304736-125
Spare Parts
Optimum Replaceable Unit (ORU) Parts for PM I/O
Release 100 Experion PKS Troubleshooting and Notifications Reference 883
1/03 Honeywell Part I
Name Description Part Number
DO FTA with GI Modules (Crimp
Terminals)
51304736-325 DO FTA
(MU-GDOL82)
DO Galvanic Isolation Module
(MTL4023)
51191927-100
LFD Combiner Panel
(MU-GLFD02)
Line Fault Detection Combiner
Panel
51304732-125
Power Distribution
Assembly
(MU-GPRD02)
Galvanic Isolation Power
Distribution Assembly
51304644-125
Marshalling Panel
(MU-GMAR52)
Marshalling Panel 51309156-125
Comp-type terminal connector for
GI Modules
51191738-100
Crimp-type terminal connector for
GI Modules
51191737-100
GI Module Connector
14-20 AWG wire crimp pins for
above connector
51191737-201

Spare Parts
Optimum Replaceable Unit (ORU) Parts for PM I/O
884 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Galvanically Isolated FTA components - conformally coated

Name Description Part Number
HLAI FTA
(MC-GAIH12)
HLAI FTA with GI Modules
(Compress terminals) (Replaced
by MU-GAIH13 51304718-125)
51304636-150
HLAI FTA with GI Modules (Crimp
terminals) (Replaced by MU-
GAIH83 51304718-325)
51304636-350 HLAI FTA
(MC-GAIH82)
HLAI Galvanic Isolation Module
(MTL4041)
51191697-100
HLAI FTA
(MC-GAIH13)
HLAI FTA with GI Modules
(Compress terminals)
51304718-175
HLAI FTA with GI Modules (Crimp
terminals)
51304718-375 HLAI FTA
(MC-GAIH83)
HLAI Galvanic Isolation Module
(MTL4041B)
51191697-200
HLAI FTA
(MC-GAIH14)
HLAI FTA with GI Modules
(Compress terminals)
51304730-175
HLAI FTA with GI Modules (Crimp
terminals)
51304730-375 HLAI FTA
(MC-GAIH84)
HLAI Galvanic Isolation Module
MTL4041P)
51191928-100
HLAI FTA
(MC-GAIH22)
HLAI FTA with GI Modules
(Compress terminals)
51304748-175
HLAI FTA with GI Modules (Crimp
terminals)
51304748-375 HLAI FTA
(MC-GAIH92)
HLAI Galvanic Isolation Module
(MTL4041B)
51191697-200
HLAI Calibration Tool HLAI calibration tool 51201450-100
24 Vdc DI FTA
(MC-GDID12)
24 Vdc DI FTA with GI Modules
(Compress Term)
51304640-175
24 Vdc DI FTA
(MC-GDID82)
24 Vdc DI FTA with GI Modules
(Crimp Terminals)
51304640-375
Spare Parts
Optimum Replaceable Unit (ORU) Parts for PM I/O
Release 100 Experion PKS Troubleshooting and Notifications Reference 885
1/03 Honeywell Part I
Name Description Part Number
24 Vdc DI Galvanic Isolation
Module (MTL4016)
51191699-100
24 Vdc DI FTA
(MC-GDID13)
24 Vdc DI FTA with GI Modules
(Compress Term)
51304728-175
24 Vdc DI FTA with GI Modules
(Crimp Terminals)
51304728-375 24 Vdc DI FTA
(MC-GDID83)
24 Vdc DI Galvanic Isolation
Module (MTL4013)
51191926-100
AO FTA
(MC-GHAO11)
AO nonredun FTA with HART and
Comp Term
51309540-175
AO FTA
(MC-GAOX02)
AO nonredun FTA with GI
Modules (Comp Term)
51304638-175
AO FTA
(MC-GAOX72)
AO nonredun FTA with GI
Modules (Crimp Term)
51304638-375
AO FTA
(MC-GAOX12)
AO redundant FTA with GI
Modules (Comp Term)
51304638-575
AO redundant FTA with GI
Modules (Crimp Term)
51304638-775
AO Galvanic Isolation Module
(MTL4045C)
51192097-200
AO Galvanic Isolation Module
(MTL4046P)
51192565-100
AO FTA
(MC-GAOX82)
Redundancy Module for FTA 51304338-100
DO FTA
(MC-GDOD12)
DO FTA with GI Modules
(Compression Terminals)
51304642-175
DO FTA with GI Modules (Crimp
Terminals)
51304642-375 DO FTA
(MC-GDOD82)
DO Galvanic Isolation Module
(MTL4021)
51191698-100
DO FTA
(MC-GDOL12)
DO FTA with GI Modules
(Compression Terminals)
51304736-175
Spare Parts
Optimum Replaceable Unit (ORU) Parts for PM I/O
886 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Name Description Part Number
DO FTA with GI Modules (Crimp
Terminals)
51304736-375 DO FTA
(MC-GDOL82)
DO Galvanic Isolation Module
(MTL4023)
51191927-100
LFD Combiner Panel
(MC-GLFD02)
Line Fault Detection Combiner
Panel
51304732-175
Power Distribution
Assembly
(MC-GPRD02)
Galvanic Isolation Power
Distribution Assembly
51304644-175
Marshalling Panel
(MC-GMAR52)
Marshalling Panel 51309156-175
Comp-type terminal connector for
GI Modules
51191738-100
Crimp-type terminal connector for
GI Modules
51191737-100
GI Module Connector
14-20 AWG wire crimp pins for
above connector
51191737-201

Spare Parts
Optimum Replaceable Unit (ORU) Parts for PM I/O
Release 100 Experion PKS Troubleshooting and Notifications Reference 887
1/03 Honeywell Part I
Miscellaneous components - non-conformally coated

Name Description Part Number
Card Case Plastic case for IOP cards 51304072-100
Label - Plain blue for IOP filler
card
51109474-100
Label for Low Level Analog Input
IOP
51109475-100
Label for High Level Analog Input
IOP
51109476-100
Label for Analog Output IOP 51109477-100
Label for Digital Input IOP 51109478-100
Label for Digital Output IOP 51109479-100
Label for I/O Link Extender 51109480-100
Label for Low Level Multiplexer
IOP
51109486-100
Card Label
Label for Smart Transmitter
Interface IOP
51109494-100
8 Point terminal block 51190694-108
12 Point terminal block 51190694-112
8 Point terminal block, labeled 1-
8, gold contacts, for LLAI
51190787-408
8 Point terminal block, labeled 9-
16, gold contacts, for LLAI
51190787-508
FTA Plug-in Terminal
Block
11 Point terminal block, labeled 9-
19, gold contacts, for LLAI
51190787-411
Terminal Block Cover Cover for terminals on 8-channel
LLAI FTA
51201569-100
Cabinet fan assembly, 115 Vac
without alarm
51304074-100 Cabinet Fan Assembly
Cabinet fan assembly, 230 Vac
without alarm
51304074-200
Spare Parts
Optimum Replaceable Unit (ORU) Parts for PM I/O
888 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Name Description Part Number
Fan, 115 Vac (replacement for
51304074-100)
68A8976P1 Cabinet Fan
Fan, 230 Vac (replacement for
51304074-200)
68A8976P2
Cabinet fan assembly, 115 Vac
with alarm
51303940-100 Cabinet Fan Assembly
Cabinet fan assembly, 230 Vac
with alarm
51303940-200
PWB, 115 Vac (replacement for
51303940-100)
51201475-100 Cabinet Fan Assembly
PWB
PWB, 230 Vac (replacement for
51303940-200)
51201475-200
Left 7- Slot Card File
(MU-HPFH01)
Left 7-Slot IOPcard file assy (slots
1-7)
51404125-100
Left 7- Slot Card File
(MU-HPFI03)
Left 7-Slot IOP card file assy
(slots 1-7)
51404191-225
Left 7- Slot Card File
Backpanel
Left 7-Slot card file backpanel
assy (slots 1-7)
51401626-100
Right 7- Slot Card File
(MU-HPFH11)
Right 7- Slot IOP card file assy (9-
15)
51404126-100
Right 7- Slot Card File
(MU-HPFI13)
Right 7- Slot IOP card file assy
(slots 9-15)
51404192-225
Right 7- Slot Card File
Backpanel
Right 7- Slot card file backpanel
assy (slots 9-15)
51401629-100
IOP Only Card File
(MU-IOFX02)
15 IOP Only card file assembly 51401546-100
IOP Only Card File
Backpanel
15 IOP Only card file backpanel
assembly
51402599-100
IOP Only Card File
(MU-IOFX03)
15 IOP Only card file assembly 51404210-125
IOP Only Card File
Backpanel
15 IOP Only card file backpanel
assembly
51402599-125
Spare Parts
Optimum Replaceable Unit (ORU) Parts for PM I/O
Release 100 Experion PKS Troubleshooting and Notifications Reference 889
1/03 Honeywell Part I
Name Description Part Number
Filler Plate Filler plate between 7-Slot card
files
51304720-100
Opto-Isolator Solid-state opto-isolator for card
files
51190516-202
Fuse Holder/Puller Fuse holder/puller (15 IOP card
file)
51190586-100
100 ohm range resistor 51190102-100 Range Resistor
250 ohm range resistor 51190102-200
Zero Ohm Resistor Zero ohm resistor for Power
System backpanel when adding
Battery Pack assembly
51190101-100

Spare Parts
Optimum Replaceable Unit (ORU) Parts for PM I/O
890 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03
Miscellaneous components - conformally coated

Name Description Part Number
Cabinet fan assembly, 115 Vac
without alarm
51304074-150 Cabinet Fan Assembly
Cabinet fan assembly, 230 Vac
without alarm
51304074-250
Fan, 115 Vac (replacement for
51304074-100)
68A8976P1 Cabinet Fan
Fan, 230 Vac (replacement for
51304074-200)
68A8976P2
Cabinet fan assembly, 115 Vac
with alarm
51303940-150 Cabinet Fan Assembly
Cabinet fan assembly, 230 Vac
with alarm
51303940-250
PWB, 115 Vac (replacement for
51303940-100)
51201475-150 Cabinet Fan Assembly
PWB
PWB, 230 Vac (replacement for
51303940-200)
51201475-250
Left 7- Slot Card File
(MC-HPFH01)
Left 7-Slot IOPcard file assy (slots
1-7)
51404125-150
Left 7- Slot Card File
(MC-HPFI03)
Left 7-Slot IOP card file assy
(slots 1-7)
51404191-275
Left 7- Slot Card File
Backpanel
Left 7-Slot card file backpanel
assy (slots 1-7)
51401626-150
Right 7- Slot Card File
(MC-HPFH11)
Right 7- Slot IOP card file assy (9-
15)
51404126-150
Right 7- Slot Card File
(MC-HPFI13)
Right 7- Slot IOP card file assy
(slots 9-15)
51404192-275
Right 7- Slot Card File
Backpanel
Right 7- Slot card file backpanel
assy (slots 9-15)
51401629-150
IOP Only Card File
(MC-IOFX02)
15 IOP Only card file assembly 51401546-150
Spare Parts
Optimum Replaceable Unit (ORU) Parts for PM I/O
Release 100 Experion PKS Troubleshooting and Notifications Reference 891
1/03 Honeywell Part I
Name Description Part Number
IOP Only Card File
Backpanel
15 IOP Only card file backpanel
assembly
51402599-150
IOP Only Card File
(MC-IOFX03)
15 IOP Only card file assembly 51404210-175
IOP Only Card File
Backpanel
15 IOP Only card file backpanel
assembly
51402599-175
Filler Plate Filler plate between 7-Slot card
files
51304720-150

Spare Parts
Optimum Replaceable Unit (ORU) Parts for PM I/O
892 Experion PKS Troubleshooting and Notifications Reference Release 100
Part I Honeywell 1/03




Fax Transmittall Fax No.: (602) 313-3293
Reader Comments Ftw
To: Solution Support Center
From: Name Date:
Title:
Company:
Address:
City: State: Zip:
Telephone: Fax:
Experion PKS

Troubleshooting and Notifications Reference, Release 100, 1/03
Comments:










You may also call the Solution Support Center at 800-343-0228,
Email SSC at tac-response@honeywell.com, or write to:
Solution Support Center
Honeywell
MS-P13
2500 West Union Hills Drive
Phoenix, AZ 85027

Experion PKS

Knowledge Building Tools




Honeywell
ACS Industry Solutions
1100 Virginia Drive
Fort Washington, PA 19034