Software Diagnostic Output

and Error Messages

ACE3600 System Tools

Suite (STS)
AB
Version 21.60

ACE1000
Version 5.00

6802979C20-T

MOTOROLA, MOTO, MOTOROLA SOLUTIONS and the Stylized

M Logo are trademarks or registered trademarks of Motorola
Trademark Holdings, LLC and are used under license. All other
product or service names are the property of their respective
owners.

Copyright © 2018 All rights reserved

Copyrights
The Motorola Solutions products described in this document may include copyrighted Motorola
Solutions computer programs. Laws in the United States and other countries preserve for Motorola
Solutions certain exclusive rights for copyrighted computer programs. Accordingly, any copyrighted
Motorola Solutions computer programs contained in the Motorola Solutions products described in this
document may not be copied or reproduced in any manner without the express written permission of
Motorola Solutions.
© 2018 Motorola Solutions, Inc. All Rights Reserved

No part of this document may be reproduced, transmitted, stored in a retrieval system, or translated
into any language or computer language, in any form or by any means, without the prior written
permission of Motorola Solutions, Inc.
Furthermore, the purchase of Motorola Solutions products shall not be deemed to grant either directly
or by implication, estoppel or otherwise, any license under the copyrights, patents or patent
applications of Motorola Solutions, except for the normal non-exclusive, royalty-free license to use that
arises by operation of law in the sale of a product.

Disclaimer
Please note that certain features, facilities, and capabilities described in this document may not be
applicable to or licensed for use on a particular system, or may be dependent upon the characteristics
of a particular mobile subscriber unit or configuration of certain parameters. Please refer to your
Motorola Solutions contact for further information.

Trademarks
MOTOROLA, MOTO, MOTOROLA SOLUTIONS, and the Stylized M Logo are trademarks or
registered trademarks of Motorola Trademark Holdings, LLC and are used under license. All other
trademarks are the property of their respective owners.

European Union (EU) Waste of Electrical and Electronic Equipment (WEEE)

directive

The European Union's WEEE directive requires that products sold into EU countries must have
the crossed out trash bin label on the product (or the package in some cases).
As defined by the WEEE directive, this cross-out trash bin label means that customers and end-users
in EU countries should not dispose of electronic and electrical equipment or accessories in household
waste.
Customers or end-users in EU countries should contact their local equipment supplier representative or
service centre for information about the waste collection system in their country.

Send Feedback
Contact Us
Motorola Solution Support Center
The Solution Support Center (SSC) is the primary Motorola Solutions support contact. Call:
• Before any software reload.
• To confirm troubleshooting results and analysis before removing and replacing a Field Replaceable
Unit (FRU) and Field Replaceable Entity (FRE) to repair the system.

For... Phone
United States Calls 800-221-7144
International Calls 302-444-9800

North America Parts Organization

For assistance in ordering replacement parts or identifying a part number, contact the Motorola Parts
organization. Your first response when troubleshooting your system is to call the Motorola SSC.

For... Phone
Phone Orders 800-422-4210 (US and Canada Orders)
For help identifying an item or part number, select
choice 3 from the menu.

302-444-9842 (International Orders)

Includes help for identifying an item or part number and
for translation as needed.

Fax Orders 800-622-6210 (US and Canada Orders)

Comments
Send questions and comments regarding user documentation to
[email protected].
Provide the following information when reporting a documentation error:
• The document title and part number
• The page number with the error
• A description of the error
We welcome your feedback on this and other Motorola manuals. To take a short, confidential survey
on Motorola Customer Documentation, go to docsurvey.motorolasolutions.com or scan the following
QR code with your mobile device to access the survey.

Send Feedback
Contents
SOFTWARE DIAGNOSTICS OUTPUT ........................................................................................................... 4
Overview ............................................................................................................................................... 4
TRANSPORT MUX DEVICE = TRNINT .......................................................................................... 11
TMRHEAP DEVICE = HP_F_TX, HP_F_RX, HP_UF_A, HP_UF_U, HOM2L (ACE3600)........ 17
HEAP DEVICE = HP_F_TX, HP_F_RX, HP_UF_A, HP_UF_U (IRRInet-M) ............................. 17
ADAPTOR DEVICE = COM1A, RTU1A, LIN1A,…RTU:A ............................................................ 19
TRANSPORT DEVICE = TRANS1, TRANS2,..., MTRAN1, MTRAN2,… ........................................ 21
MTE .................................................................................................................................................... 23
LINK LAYER DEVICE = COM1L, RTU:L, … ................................................................................. 39
NETWORK STOCK (NSTOCK) ....................................................................................................... 42
USERROM (USRROM)..................................................................................................................... 45
NETWORK (NETWRK)...................................................................................................................... 50
MINISESSION (WIDE, EVNT, STCL, ASCLI, ASSER, FEPRTU) .................................................. 51
GAPRATIO (GPRTIO) ................................................................................................................... 56
HDLC/RADIO (RAD1P, RAD2P,...) ................................................................................................. 57
UART .................................................................................................................................................. 65
RADIO CHANNEL (RAD1C , RAD2C,…) .......................................................................................... 78
TRUNK CHANNEL ............................................................................................................................. 82
RS232 CHANNEL ............................................................................................................................... 86
MODEM CHANNEL ........................................................................................................................... 90
TIMERS (10__MS , 100_MS , 1__SEC , 1__MIN) ........................................................................... 95
TIME-TAG (ACE_TM_)..................................................................................................................... 95
SESSION DEVICE = SESS1, SESS2,..., MSESS1, MSESS2… ........................................................ 96
DI ........................................................................................................................................................ 97
I/O MODULES (R0M1 , R0M2 ,...) ................................................................................................... 97
8DO ..................................................................................................................................................... 97
MIX ................................................................................................................................................... 100
DSP (AC ANALYZER) ...................................................................................................................... 101
RS485 ................................................................................................................................................ 104
FLASH MEMORY (FLASHDB, FLSEXT1) ..................................................................................... 109
FFILES.............................................................................................................................................. 110
MFFS ................................................................................................................................................ 111
LDIALER (DIL2D , DIL 3D) .......................................................................................................... 113
(ML_DL) ........................................................................................................................................... 114
TOPLC (PLC1L, PLC2L, PLC3L) .................................................................................................... 115
TOSCADA (PLC1L, PLC2L, PLC3L) .............................................................................................. 116
SWITCHR/SWITCHER ..................................................................................................................... 117
FRM_USR/FRAME SEQUENCE ..................................................................................................... 118
BURST - SEQ .................................................................................................................................... 119
PHONE BOOK LEVEL = 0 PHNBK ............................................................................................ 119
ACE_TMR/TIMER EVENT ............................................................................................................... 120
STBLA ............................................................................................................................................... 122
POOLMNGR ..................................................................................................................................... 123
OCOMM LEVEL = 0 ..................................................................................................................... 124
FSKADP (OCOMC).......................................................................................................................... 129
GPS ................................................................................................................................................... 135
CAPPL (IRRInet-M/MOSCAD-M) .................................................................................................... 138

1
 Software Diagnostics Output

C APPLICATION TIMERS DEVICE = CD_10, CD_100 ............................................................. 140

SFLASH (CPU 400 and above only) ................................................................................................ 140
GAUART DEVICE = COMxA, RTUxA, LINxA ............................................................................. 142
SITTBL .............................................................................................................................................. 145
PTRMNG........................................................................................................................................... 146
DCFi (for ‘C’ applications only) ...................................................................................................... 146
IPLINK LINxL .............................................................................................................................. 147
SLIP LINxSlp ............................................................................................................................... 156
I2PHYS.............................................................................................................................................. 164
IPLINK LINxL, LINxLAN, LINxPL .............................................................................................. 165
NTP ................................................................................................................................................... 184
DUART.............................................................................................................................................. 190
DRS485 ............................................................................................................................................. 195
DHDLC ............................................................................................................................................. 197
DRADIO ............................................................................................................................................ 201
LOGFLAS ......................................................................................................................................... 206
ACE_LED ......................................................................................................................................... 208
ERRLOG ........................................................................................................................................... 209
I2C .................................................................................................................................................... 211
RS485 ................................................................................................................................................ 214
UART ................................................................................................................................................ 216
RS232 ................................................................................................................................................ 222
RADIO CHANNEL (RAD1C , RAD2C,…) ........................................................................................ 223
SFLEVL ............................................................................................................................................. 226
SFLLDR ............................................................................................................................................ 228
SOCKETF ......................................................................................................................................... 229
SPI ..................................................................................................................................................... 230
IPPORTS ........................................................................................................................................... 235
E2_INTR ........................................................................................................................................... 236
IOSWITCH ........................................................................................................................................ 237
VXWDMNG....................................................................................................................................... 238
F_EVNT ............................................................................................................................................ 240
DHCPCL ........................................................................................................................................... 243
DNSCLI ............................................................................................................................................. 244
DFLTCNF ......................................................................................................................................... 244
CONFIG ............................................................................................................................................ 245
FIREWL ............................................................................................................................................ 246
PS (POWER SUPPLY) ...................................................................................................................... 247
IOMNGR ........................................................................................................................................... 253
IOFPGA ............................................................................................................................................ 254
RxMy ................................................................................................................................................. 254
IOMNGR ........................................................................................................................................... 258
SFM ................................................................................................................................................... 259
RTC ................................................................................................................................................... 259
PWR_MNG ....................................................................................................................................... 260
HW_TST ............................................................................................................................................ 261
PB...................................................................................................................................................... 262
TIMESYN .......................................................................................................................................... 263
REQMNG (ACE IP Gateway Only) .................................................................................................. 268
HELTHCH (ACE IP Gateway Only) ................................................................................................ 270

2
 Software Diagnostics Output

LNKHNDL (ACE IP Gateway Only) ................................................................................................ 272

DCF6 (IRRIV Application for IRRInet-M and IRRInet-ACE) .......................................................... 272
IPCNTBL........................................................................................................................................... 278
VXNETPOOL .................................................................................................................................... 279
VXPPP .............................................................................................................................................. 280
VXROUTE ......................................................................................................................................... 285
CAPPL (ACE3600) ........................................................................................................................... 288
PLCxIP (where x = the PLCx Link name) ........................................................................................ 290
PLCIPAC .......................................................................................................................................... 293
TMSEQSY ......................................................................................................................................... 295
MI (MAPIMAGE).............................................................................................................................. 297
EMI ................................................................................................................................................... 300
MNTR ................................................................................................................................................ 300
IOEMNGR......................................................................................................................................... 302
IOEMCLI .......................................................................................................................................... 309
RDNDNCY ........................................................................................................................................ 313
RDNDSRV ......................................................................................................................................... 315
USBCONF......................................................................................................................................... 317
LINxRND........................................................................................................................................... 322
PORTMNG ........................................................................................................................................ 326
SECLOG ........................................................................................................................................... 327
SECKEYS .......................................................................................................................................... 328
SECPRVD ......................................................................................................................................... 328
SECPOL ............................................................................................................................................ 329
ENCRYP............................................................................................................................................ 332
AUTCORE......................................................................................................................................... 332
AUTHSRV ......................................................................................................................................... 333
SECMNGR ........................................................................................................................................ 334
WHITELS .......................................................................................................................................... 335
SELFTST ........................................................................................................................................... 335
DBBKUP ........................................................................................................................................... 336
MODBUS (ACE100) ......................................................................................................................... 340
RTU (ACE1000) ................................................................................................................................ 346
DNP3 Master .................................................................................................................................... 349
DNP3 Slave ....................................................................................................................................... 355
LTRAPPL (ACE1000) ....................................................................................................................... 365
RTU1P (ACE1000) ........................................................................................................................... 367
SYSTEM (ACE1000) ......................................................................................................................... 368
IRM, IRMSRV ................................................................................................................................... 371
LOGIx, MLOGIx, MINIx, FRMSQx, BRSSQx, UTIL, MDLCSRV (ACE1000) ................................. 376
LOGIx, MLOGIx, MINIx, FRMSQx, BRSSQx, UTIL (MDLCSRV) (ACE1000) ............................... 376
LOGIx, MLOGIx, MINIx, FRMSQx, BRSSQx, UTIL, MDLCSRV (ACE1000) ................................. 377
MDLCSRV (ACE1000) ..................................................................................................................... 377
LOGIx, MLOGIx, MINIx, FRMSQx, BRSSQx, UTIL (MDLCSRV) (ACE1000) ............................... 378
MDLCSRV (ACE1000) ..................................................................................................................... 378
ERROR MESSAGES ................................................................................................................................. 380
Error Logger Messages .................................................................................................................... 380
Compiler Error List .......................................................................................................................... 470
Corrupted Database Errors .............................................................................................................. 476
Warning List...................................................................................................................................... 476

3
 Software Diagnostics Output

Software Diagnostics Output

The STS Software Diagnostics utility allows access to each of the devices in the RTU according to their
logical names. For details on retrieving software diagnostic messages, see the “Operation” chapter of the
ACE3600 RTU User Guide or the ACE1000 Easy Configurator User Guide.

Overview

Communication System Statistics

The communication system implements the seven layers of OSI (Open Systems Interconnection) model.
In each layer, one or more devices are created to handle that specific layer. Each of the devices (in
addition to its functions) performs statistical follow-up that may be used to analyze the status of the
communication system. The following figure describes the devices (objects) of the communication
system:

4
 Software Diagnostics Output

EVENT LOGGING
ERROR LOGGING
SOFTWARE DIAGNOSTICS
DOWNLOADING & MONITORING
APPLICATION LADDER and DATA BASE
LAYER DATA BASE MAPPING

PRESENTATION ....
LAYER PRESS1 PRESSn

SESSION
EVNT STCL WIDE ....
LAYER
Event Broadcast RTU-to-RTU SESS1 SESSn
Transmission Reception Communication
n
Session Logical
Channels
MiniSession
....
Logical TRANS1 TRANSn
Channels
TRANSPORT
LAYER

TRANSPORT MULTIPLEX

NETWORK
NETWRK
LAYER

LINK
LAYER COM1L LIN1L RAD1L

COM1A LIN1A
PHYSICAL
LAYER

COM1P LIN1P RAD1P

HARDWARE UART UART RADIO PORT

PORT 1 PORT 2 PORT 3

COMPUTER EXTERNAL RADIO
PORT MODEM

A typical ACE3600 RTU is depicted with three physical ports marked Port 1-3, where Port 1 is defined as
a Local Computer port, Port 2 is defined as External Modem, and Port 3 is defined as Radio. The
physical ports are supported by the Link and Physical layers.

5
 Software Diagnostics Output

It also shows n Session Logical Channels used by various applications. In addition, three Minisession
Logical Channels support event & burst transmission, broadcast reception, and RTU-to-RTU
communication.

The names of the devices of the Link and Physical layers are taken from the logical names of the links, as
defined by the user in the site configuration. There is no connection between the number that is part of the
device name and the port number.

For example, the device of the link of port 2 is named LIN1L, since the link name is LINE1 and L
indicates a link device.

The MDLC communication supports two modes of transmission:

• Synchronous mode (may be used in the plug-in ports of the CPU module)

• Asynchronous mode, UART (may be used in the on-board or plug-in ports of the CPU
module)

A plug-in port is used in the Synchronous mode of transmission, when:

1. A radio of any type is connected.

2. A modem is connected and synchronous communication is defined in the Site Configuration

program (except dial-up mode that allows only asynchronous mode of operation).

3. An RS232 Synchronous piggyback is connected to port 3.

When the communication is synchronous (bit oriented), the physical channel consists of the Link device
and Physical device. The transmitted frame is composed of a stream of bits that starts and ends with flags
that indicate the frame limits.

When the communication is asynchronous (byte oriented), the frame is broken down and encoded into a
series of bytes, transmitted and received by a UART. This type of communication is handled by the
Adaptor device.

To get the statistics of a specific device, define the device name, the Site ID, and also the Level of
request. All devices in the system have a level of request, starting from Level 0.

Level 10 and Level 11 should be used to get communication statistics.

The following table provides the device names that respond to Level 10 and Level 11.

Layer Name Device Notes

Name
Mini-Session EVNT for Event application
STCL for Group-Control application
WIDE for RTU-to-RTU application
Transport TRANSx x – logical channel
Network NETWRK –

6
 Software Diagnostics Output

Layer Name Device Notes

Name
Link DILxL For DIAL link
COMxL for COMPUTER link
RTUxL for RSlink
RADxL for RADIO link
LINxL for LINE link
LINxRND for LINE link (Remote NDIS)
TSxL for terminal server link*
x – logical number (ACE) and
– No.of terminal server port
(ACE IP Gateway)
UART-Physical DILxA For DIAL link
(Adaptor)
COMxA for COMPUTER link
RTUxA for RSlink link
RADxA for RADIO link
LINxA for LINE link via ext. modem
TSxA x – logical number (ACE) and
– No.of terminal server port
(ACE IP Gateway)
Physical DILxP For DIAL link
COMxP for COMPUTER link
RTUxP for RSlink link
RADxP for RADIO link
LINxP for LINE link via ext. modem
TSxP x – logical number (ACE) and
– No.of terminal server port
(ACE IP Gateway)

Link ID Link Adaptor Physical Layer

For dial DIL1L DIL1A DIL1P

Line 1- Line 9 LIN1L-LIN9L LIN1A-LIN9A LIN1P-LIN9P

Line 10 LIN:L LIN:A LIN:P

Line 11 LIN;L LIN;A LIN;P

Line 12 LIN<L LIN<A LIN<P

Line 13 LIN=L LIN=A LIN=P

Line 14 LIN>L LIN>A LIN>P

7
 Software Diagnostics Output

Link ID Link Adaptor Physical Layer

Line 15 LIN?L LIN?A LIN?P

Line 16 LIN@L LIN@A LIN@P

Line 17-Line 29 LINAL LINAA-LINMA LINAP-LINMP

Line 30-Line 99 L030L-L099L L030A-L099A L030P-L099P

Line 100-Line 200 L100L-L200L L100A-L200A L100P-L200P

Rslink 1-Rslink9 RTU1L-RTU9L RTU1A-RTU9A RTU1P-RTU9P

Rslink 10 RTU:L RTU:A RTU:P

Rslink 11 RTU;L RTU;A RTU;P

Rslink 12 RTU<L RTU<A RTU<P

Rslink 13 RTU=L RTU=A RTU=P

Rslink 14 RTU>L RTU>A RTU>P

Rslink 15 RTU?L RTU?A RTU?P

Rslink 16 RTU@L RTU@A RTU@P

Rslink 17-Rslink 19 RTUAL-RTUCL RTUAA-RTUCA RTUAP-RTUCP

Rslink 20-Rslink 99 S020L-S099L S020A-S099A S020P-S099P

Rslink 100-Rslink 200 S100L-S200L S100A-S200A S100P-S200P

Radio 1-Radio 9 RAD1L-RAD9L RAD1A-RAD9A RAD1P-RAD9P

Radio 10-Radio 99 R010L-R099L R010A-R099A R010P-R099P

Radio 100-Radio 200 R100L-R200L R100A-R200A R100P-R200P

Computer 1-Computer 9 COM1L-COM9L COM1A-COM9A COM1P-COM9P

For the ACE1000 RTU, the following devices exist for MDLC driver channels:

Type Device Notes

Name
Session Slave LOG1 Requests coming from UI or
STS regarding Error Logger,
LOG2 Date & Time, installation, etc.
LOG3
LOG4
LOG5

8
 Software Diagnostics Output

Type Device Notes

Name
Session Master MLOG6 All UI operations such as Error
Logger, Date & Time,
MLOG7 Diagnostics, etc.
MLOG8
MLOG9
MLOG10
Minisession MINI1 MOSCAD_SndFrm,
MOSCAD_Txfrm,
MINI2 MOSCAD_AnsFrm
MINI3 MOSCAD_tx_burst, FEP-RTU
application etc.)
MINI4
MINI5
MINI6
Frame FRMSQ1 MOSCAD_MDLC_txframe,
Sequence MOSCAD_MDLC_rxframe
FRMSQ2
Burst Sequence BRSSQ3 MOSCAD_tx_burstseq
BRSSQ4
Sync and other UTIL Sending sync not supported
internal usage

Reading Diagnostics Information

The structure of the statistical data is described below for each device name.

COMxA (Adaptor device of Computer X)

Jun 30 14:49:10 Site: LOCAL Device: COM1A Level: 11
# of Transmitted Frames : 6
# of Re-transmitted Frames : 0
# of Received Frames : 6
# of Received Frames (With Error): 0

The # of Received Frames includes only correct frames (including acknowledgment frames).

The # of Re-transmitted Frames represents only frames rejected by the physical layer (do not use this
number; use the # of Re-transmitted Frames in the Link device).

RADxL (Link device of Radio X)

Jun 30 14:50:10 Site: LOCAL Device: RAD1L Level: 11
# of Transmitted Frames : 0
# of Re-transmitted Frames : 0
# of Received Frames : 0
# of Received Frames (With Error): 0

The # of Transmitted Frames does not include retransmission and acknowledgment frames. The # of
Received Frames includes only correct frames.

COMxL (Link device of Computer X)

Jun 30 14:55:26 Site: LOCAL Device: COM1L Level: 11

9
 Software Diagnostics Output

# of Transmitted Frames : 17
# of Re-transmitted Frames : 0
# of Received Frames : 35
# of Received Frames (With Error): 0

The # of Transmitted Frames does not include retransmission and acknowledgment frames. The # of
Received Frames includes only correct frames.

NETWRK (Network device)

Jun 30 14:56:20 Site: LOCAL Device: NETWRK Level: 11
# of Transmitted Frames : 21
# of Received Frames : 43
# of Received Frames (With Error): 0

WIDE
Jun 30 15:02:00 Site: LOCAL Device: WIDE Level: 11
# of transmitted frames as ORIGINATE: 0
# of transmitted frames as GROUPCALL: 0
# of transmitted frames as ANSWER : 0
# of transmitted frames as MESSAGE : 0
# of re-transmitted frames : 0
# of received frames as ORIGINATE : 0
# of received frames as GROUPCALL : 0
# of received frames as ANSWER : 0
# of received frames as MESSAGE : 0
# of received frames (with error) : 0

STCL
Jun 30 15:09:25 Site: LOCAL Device: STCL Level: 11
# of transmitted frames as ORIGINATE: 0
# of transmitted frames as GROUPCALL: 0
# of transmitted frames as ANSWER : 0
# of transmitted frames as MESSAGE : 0
# of re-transmitted frames : 0
# of received frames as ORIGINATE : 0
# of received frames as GROUPCALL : 0
# of received frames as ANSWER : 0
# of received frames as MESSAGE : 0
# of received frames (with error) : 0

TRANSx
Jun 30 15:12:38 Site: LOCAL Device: TRANS1 Level: 11
# of Transmitted Frames : 25
# of Received Frames : 26
# of Re-transmitted Frames : 0
# of Received Frames (With Error) : 0
# of Frames in TX queue : 0
# of Frames in RX queue : 0
# of Frames in TX queue (hold by LINK layer): 0
# of Frames in TX queue (hold by PHYSICAL layer): 0

Software Diagnostics Terminology

The section below lists the diagnostics which are available for the various ACE3600 RTU devices. The
messages are listed as they appear on the screen, with %% signs in the text to represent the device’s
current alphanumeric values.

The description which follows the diagnostics messages, provides an explanation for the variables.

Terms that are used frequently in diagnostics are described below:

10
 Software Diagnostics Output

Term Explanation

Device An ACE3600 software module.

Instance (of a device) A device may appear more than once in
ACE3600, each carrying a unique name.
Level A group of diagnostic checks. Up to 100 (0
through 99) levels can be custom-defined for
each device.
PIN table A pointer which allows “cabling” between
two devices during run time.
Address Numeric sum of Site ID and System Address.
Tick Time measurement unit, equal to 10 ms.

TRANSPORT MUX DEVICE = TRNINT

## 16 LEVEL = 0
Mini Session Channels : %% 1
Master Channels : %% 2
Slave Channels : %% 3

1. Number of logical mini-sessions that serve the RTU applications. A mini-session is an API layer that
serves the RTU-to-RTU communications, event bursts, and setcall.

2. The number of logical channels above the Presentation layer from which the RTU can initiate
communications. In an RTU there are no such logical channels as there is no application that can
initiate a call. Control centers (e.g. MCP-M) do have such applications such as schedulers and
command dispatchers.

3. The number of logical channels above the Presentation layer through which the RTU reacts to calls
simultaneously (such as error logger, diagnostics, D.B. monitor, process monitor, date and time,
download). The RTU does not need more than 2-4 channels for regular and orderly activity.

## 17 LEVEL = 1
Minisession Channels
--------------------
Minisession Key Application ID
--------------- -----------------

This is the applications table that uses the mini-session API for communication purposes. For each
application this table records the key for the instance of the mini-session, and the application ID.

11
 Software Diagnostics Output

## 18 LEVEL = 2
Master Channels
-------------------
Transport Key Slave: Site Port Link
------------- ---- ---- ----

This table defines the logical channels located above the Presentation layer, and capable of initiating
communications. For each channel the table records the call destination. The destination address consists
of the site ID, the port ID, and the link ID.

## 19 LEVEL = 3
Slave Channels
--------------
Transport Key Master: Site Port Link Channel Id Is Session Secured
------------- ---- ---- ---- ---------- ------------------

This table defines the active logical channels that can react to communications from ToolBox, the control
center, MCP-M or IP Gateway. For each logical channel, the table records information about the SRC that
initiated the call, namely, the site ID, link ID, Port ID and the identification number of the logical channel
that was used for the call. The 'Is Session Secured' column reflects if the RTU communicates with the
master in a nonsecured communication session.

## 20 LEVEL = 4
Frame Sequence Channels
-----------------------
Frame Seq Key Application Id
------------- --------------
The Frame Seq Key field holds the key of the application that should receive the frames originating from
the corresponding application on the transmitting side, specified in the Application ID field.

## 21 LEVEL = 5
Exp Send L_dup State T_reset T_dup T_hole B_reset B_ack

Exp The expected sequence number.

Send The sequence number of the next frame sent.

L_dup The last sequence number that can be accepted as the sequence of a duplicated frame.

State The status registered in the internal status engine.

T_reset The amount of time a unit waits after having acknowledged repeated reset requests, before
sending its own reset frame.

T_dup The amount of time a unit, which has received frames with identical numbers, considers
them as duplicates instead of new transmissions.

T_hole The amount of time a unit, which has received frames with holes in the sequence numbers,
still expects to receiving the missing frames.

B_reset 1 means that the frame contains a reset bit.

12
 Software Diagnostics Output

B_ack 1 means that the frame contains a reset ACK bit.

## 23
Curr Since Last Diagnostic: Max # # Max #
Waiting Waiting Range Time Hole Resets
Buffers Buffers Holes Holes Len

Current Waiting Buffers Number of frames held in Waiting Queue.

Max Waiting Buffers Maximum number of frames in Waiting Queue.

# Range Holes The number of range “holes” found since the last diagnostic.

# Time Holes The number of time “holes” found since the last diagnostic.

Max Hole Len The maximum length of time “holes.”

# Resets The number of resets/rejects since the last diagnostic.

## 25 LEVEL = 6
Pointer to encryption keys list : %%1
Encryption keys list ID : %%2
# of encryption keys : %%3
Duration (100Ms) to swich Encryption keys preset : %%4
Dual encryption keys Rx duration (100Ms) preset : %%5
Is encryption keys switch in process : %%6
Current encryption key index : %%7
Next encryption key index to activate : %%8
Timeout to Tx with current key : %%9
Timeout to Rx with both current and next keys : %%10
# of Session Tx rejects : %%11
# of MiniSession Tx rejects : %%12
# of FrameSeq Tx rejects : %%13
# of Session Rx rejects : %%14
# of MiniSession Rx rejects : %%15
# of FrameSeq Rx rejects : %%16

This diagnostic is relevant only in firmware <V16.00 for LEGACY encryption. For firmware ≥ 16.00
and above, see ## 27 LEVEL = 6.

1. Pointer to the list of encryption keys.

2. The ID of the encryption keys list.

3. The number of encryption keys.

4. The interval, in seconds, required for the new key to become active.

5. The interval, in seconds, during which two keys are acceptable- the old key which is being changed
and the new key which is becoming active.

6. Whether a switch of keys is in progress.

13
 Software Diagnostics Output

7. The index to the keys file (0-9) which is the current key.

8. The next key index to be activated.

9. The number of seconds remaining to transmit using the current key.

10. The number of seconds remaining to transmit using the both the current and next key.

11. The number of user data transmissions of Session type communication which were rejected.

12. The number of user data transmissions of MiniSession type communication which were rejected.

13. The number of user data transmissions of FrameSeq type communication which were rejected.

14. The number of user data receptions of Session type communication which were rejected.

15. The number of user data receptions of MiniSession type communication which were rejected.

16. The number of user data receptions of FrameSeq type communication which were rejected.

14
 Software Diagnostics Output

## 27 LEVEL = 6
Encryption Mode : %% %%1
Encryption Policy : %%2
Encryption Package : %%3
Encryption Algorithm Type : %%4
Send NAK upon decryption failure : %%5
Encryption Block Size : %%6
Indicate 'RSTLOAD' control fully executed : %%7

Last Site of Tx Session rejects : %%8

Last Site of Tx MiniSession rejects : %%9
Last Site of Tx FrameSeq rejects : %%10

Last Site of Rx Session rejects : %%11

Last Site of Rx MiniSession rejects : %%12
Last Site of Rx FrameSeq rejects : %%13

Number of Tx Session rejects : %%14

Number of Tx MiniSession rejects : %%15
Number of Tx FrameSeq rejects : %%16

Number of Rx Session rejects : %%17

Number of Rx MiniSession rejects : %%18
Number of Rx FrameSeq rejects : %%19

Last Tx Encryption Error : %%20

Last Rx Decryption Error : %%21

Last Tx Encryption padding length : %%22

Last Rx Decryption padding length : %%23

Self Test Pass Counter : %%24

Self Test Fail Counter : %%25

Session Tx Retry Counter : %%26

MiniSession Tx Retry Counter : %%27
FrameSeq Tx Busy Counter : %%28
Last Site of RX Illegal Second Control : %%29
Number of RX Illegal Second Control : %%30

This diagnostic is relevant only in ≥ 16.00 and above . For firmware <V16.00 for LEGACY encryption,
see ## 25 LEVEL = 6.

1. Encryption mode. Can be one of: No encryption/Legacy encryption (TEA)/New encryption (AES).

2. Whether MDLC payload encryption is enabled in the policy. Can be one of: ON/OFF.

3. OPENSSL.

4. The encryption algorithm type. Can be one of: AES, TEA.

5. Whether the RTU should send a NAK when decryption fails. If 0, do not reply with the decrypted
failed message back to the sender to avoid overloading the sender with NAKs. If 1-255 Reply with the
decrypted failed message (as received with error bit set) back to the sender with an error.

6. If 0, no block size is required; the encryption software accepts any buffer size. Otherwise, the
encryption software needs to prepare the buffer with integer multiples of the block size.

15
 Software Diagnostics Output

7. 'RSTLOAD' control was fully executed.

8. The site ID that rejected the last Session communication type transmission from this unit.

9. The site ID that rejected the last MiniSession communication type transmission from this unit.

10. The site ID that rejected the last FrameSeq communication type transmission from this unit.

11. The site that sent the last Session frame that was rejected.

12. The site that sent the last MiniSession frame that was rejected.

13. The site that sent the last FrameSeq frame that was rejected.

14. The number of user data transmissions of Session type communication which were rejected.

15. The number of user data transmissions of MiniSession type communication which were rejected.

16. The number of user data transmissions of FrameSeq type communication which were rejected.

17. The number of user data receptions of Session type communication which were rejected.

18. The number of user data receptions of MiniSession type communication which were rejected.

19. The number of user data receptions of FrameSeq type communication which were rejected.

20. The last specific encryption error on transmit.

21. The last specific encryption error on receive.

22. The last padding size added to a transmitted encrypted frame.

23. The last padding size retrieved from received encrypted frame.

24. Not used.

25. Not used.

26. The counter for Session frame retries that are decrypted and re-encrypted.

27. The counter for MiniSession frame retries that are decrypted and re-encrypted.

28. The counter for FrameSeq frame retries that are decrypted and re-encrypted.

29. Received an illegal frame (bad control part) from this site.

30. Number of received illegal frames (bad control part).

16
 Software Diagnostics Output

## 26 LEVEL = 12, 13
Is RTU secured? : %%1
Security policy password length : %%2
# of successfully transmitted secured frames : %%3
# of non-successful transmitted secured frames: %%4
# of successfully received secured frames : %%5
# of non-successfull received secured frames : %%6
Is RTU secured by message life time? : %%
Message life time window : %%
# of successfully transmitted secured message life time frames : %%
# of non-successfull transmitted secured message life time frames: %%
# of successfully received secured message life time frames : %%
# of non-successfull received secured message life time frames : %%

1. Does the RTU use MDLC authentication?

2. The password length embedded in the outbound frame's secured credentials.

3. The number of outbound frames with secured credentials transmitted successfully.

4. The number of outbound frames with secured credentials transmitted unsuccessfully.

5. The number of inbound frames with secured credentials received and authenticated successfully.

6. The number of inbound frames with secured credentials received and authenticated unsuccessfully.

7. Is the message life time security feature enabled?

8. The duration in seconds for message life time validity.

9. The number of outbound frames with message life time data transmitted successfully.

10. The number of outbound frames with message life time data transmitted unsuccessfully.

11. The number of inbound frames with message life time data received and authenticated successfully.

12. The number of inbound frames with message life time data received and authenticated
unsuccessfully.

Note: Level 12 displays the values and resets the last 4 rows of this diagnostic.

TMRHEAP DEVICE = HP_F_TX, HP_F_RX, HP_UF_A,

HP_UF_U, HOM2L (ACE3600)

HEAP DEVICE = HP_F_TX, HP_F_RX, HP_UF_A, HP_UF_U

(IRRInet-M)

17
 Software Diagnostics Output

HP_F_TX, HP_F_RX MDLC Formatted

HP_UF_A MDLC adaptor (unformatted)
HP_UF_U USER Port

## 32 LEVEL = 0
# of buffers in heap : %% 1
# of buffers left in heap : %% 2
The minimum # of buffers left
in heap from last diagnostic : %% 3
# of times the heap was empty
since last diagnostic : %% 4
Size of one buffer in bytes : %% 5
During init flag : %% 6
Bad heap flag : %% 7
Unit time for freeing by force : %% 8
Pointer to start chain : %% 9
Pointer to current chain : %% 10
Pointer to end chain : %% 11
Timeout to Restart if Heap Empty (minutes) : %% 12
Time left to Restart if Heap Empty (minutes) : %% 13
Actual size allocated for each buffer in bytes : %% 14

1. Number of buffers in heap instance

2. Number of free buffers in heap.

3. Minimum number of free buffers left in heap since the last diagnostic. This information reflects the
extent to which the heap is capable of meeting RTU needs under heavy traffic.

4. The number of times, since the last diagnostic, the RTU software detected an empty heap. A large
number of times points to incorrect allocation of memory resources.

5. Size of buffer including the overhead for managing a single buffer.

6. The flag that indicates that the RTU is in startup stage.

7. The flag that points to memory overwrite in the memory area allocated to the heap.

8. Unit of time to be measure how long a buffer is out of the heap (used by other parts of the system).

9. The beginning of the heap. The heap consists of a chain of joined buffers. For chain management
purposes, a key holds pointers to the beginning of the chain, the end of the chain, and to the next
buffer that will be taken from the chain. The P_current_chain value must be (numerically) between
the start and end values.

10. The current value of the chain. See 9. above.

11. The end of the chain. See 9. above.

12. The number of minutes to wait before restarting when the heap is empty.

13. The number of minutes remaining before restarting when the heap is empty.

14. The number of bytes allocated for each buffer.

18
 Software Diagnostics Output

## 32 LEVEL = 1
Buf Key Next Cntr #FF
--------------------------------------

Buf Address of the buffer in the memory.

Key Handle (identifier) of the heap. (If =0, buffer is in heap. Otherwise buffer is in use by system.)

Next Next buffer in heap to be allocated. (Meaningful only if key=0.)

Cntr Counts intervals of time that the buffer is out of the heap. (Meaningful only if key ≠ 0)

#FF Forced free. (Meaningful only if key ≠ 0.) Indicates the total number of units that the buffer was
in use out of the heap. Set back to zero when heap is returned to heap. If this value is greater
than 3, there may be a memory leak problem. Please consult product group.

ADAPTOR DEVICE = COM1A, RTU1A, LIN1A,…RTU:A

## 48 LEVEL = 0
Physical device key : %% 1
Physical PIN’s table : %% 2
Heap key, to be used by the receive function : %% 3
Heap key, to be used by the transmit function : %% 4
Mask address (ignore addresses or not) : %% 5
System address : %% 6
Specific logical address (site id) : %% 7
Extra address 1 : %% 8
Extra address 2 : %% 9
Mode of operation : %% 10
TimeAuth device key (HEX) : %% 11
TimeAuth handle : %% 12
Authentication stamp offset : %% 13

General - The adaptor is the layer which coordinates the transmission / reception of the MDLC frame
above Asynchronous Port.

1. The physical asynchronous key.

2. PIN Table - A pointer which allows “cabling” during run time to the physical asynchronous layer
selected in Site Configuration.

3. The Rx Heap key - This is the key to the formatted buffer Heap HP_F_RX to be used to collect the
stream of bytes which is received in the Asynchronous Port in the MDLC Frame.

4. The Tx Heap key - This is the key to the unformatted buffer Heap HP_UF_A to be used to convert
the MDLC frame into a stream of bytes for transmitting through the Asynchronous Port.

5. 0XFFFF - means receiving every MDLC frame regardless of its address. (used for the Protocol
Analyzer)

6. The System address - In the local port (not above radio) the value is zero , even if the user chooses a
different value.

19
 Software Diagnostics Output

7. The Site ID.

8. Used for transmissions in the local address (-2).

9. Used as a default router address

10. Whether or not to allow reception of SYNC frames.

11. TimeAuth device key in Hexadecimal form.

12. TimeAuth identifier.

13. Offset of Authentication stamp within the buffer for authenticated SYNC frames only.

## 49 LEVEL = 10,11
# of transmitted frames : %% 1
# of transmission fails : %% 2
# of received frames : %% 3
# of received frames (with error) : %% 4
Mask of errors (receive) : %% 5
Number of non-properly authenticated SYNC frames : %% 6

1. The number of unformatted frames that have been transmitted.

2. The number of unformatted frames that have been transmitted and for which the physical layer
returned a fail signal.

3. The number of received frames includes only correct frames (including acknowledgment frames).

4. The number of unformatted frames that have been received with some error.

5. The following figure illustrates the mask:

6. Number of synchronization frames which were not properly authenticated.

b15 . . . . . . . . . . b8 b7 b6 b5 b4 b3 b2 b1 b0

unformatted buffer heap is empty

Reserved

inverse byte, end of frame

empty frame received
invalid destination
frame, more than 200 bytes
inverse byte, inverse byte
invalid byte after inverse byte
CRC error
Recovery of UF heap

20
 Software Diagnostics Output

TRANSPORT DEVICE = TRANS1, TRANS2,..., MTRAN1,

MTRAN2,…

## 64 LEVEL = 0
Logical channel no. : %% 1
Timeout between Tx retries : %% 2
Timeout between channel busy retries : %% 3
Timeout between Rx frames : %% 4
Timeout of Rx wait (till session chk) : %% 5
Current timeout between Tx retries : %% 6
Current timeout between channel busy retries : %% 7
Current timeout between Rx frames : %% 8
Current timeout of Rx waiting : %% 9
No. of Tx retries : %% 10
No. of channel busy retries : %% 11
Current no. of Tx retries : %% 12
Current no. of channel busy retries : %% 13
Sequence of master session : %% 14
No. of frames in burst : %% 15
No. of frames in current burst : %% 16
Size of Tx queue : %% 17
Index in Tx queue of first buffer : %% 18
Index in Tx queue of next free place for buffer : %% 19
Sequence of first frame in Tx queue : %% 20
Sequence of last frame in Tx queue : %% 20
Size of Rx queue : %% 21
Index in Rx queue of first frame : %% 22
Sequence of first frame in Rx queue : %% 23
Sequence of first expected frame : %% 24
Index in Rx queue of for expected frame : %% 25
Size of temp queue : %% 26
Index in temp queue of first frame : %% 26
Index in temp queue of next free place for frame : %% 26
(flag) should start session frames to be expected : %% 27
(flag) is ack required ? : %% 28
(flag) is sync ack arrived ? : %% 29
(flag) was sync ack sent ? : %% 30
(flag) has new data arrived ? : %% 30
(flag) is it a master device ? : %% 31
(flag) is device in Tx state ? : %% 32
(flag) has reset by master occurred ? : %% 33
(flag) was session aborted ? : %% 34
(flag) first ack with burst in msg ? : %% 35
(flag) is it first Tx burst in session ? : %% 36
In_retry : %% 37

1. The logical channel number.

2. The number of seconds between transmission attempts when ACK is not received at the Transport
layer.
3. The number of seconds between transmission attempts when a Busy ACK is received. (not enough
logical channels on the answering site).
4. The preset time that the site will wait until it issues its ACK to a partial reception.
5. The preset time that the site will wait for the first time until it asks the other site “is session on?”

21
 Software Diagnostics Output

6. The current number of seconds between transmission attempts.

7. The current number of seconds between transmission attempts in case of Busy ACK.

8. The actual time that the site waits until it issues its ACK to a partial reception.

9. The actual time that the site will wait for the first time until it asks the other site “is session on?”

10. Number of transmission attempts.

11. Number of transmission attempts in case of Busy ACK.

12. The current number of transmission attempts.

13. The current number of transmission attempts in case of Busy ACK.

14. The sequence number of the master session at the initiator’s site.

15. The current number of frames in a single transmission while waiting for ACK on the receiving site.

16. The total number of frames in a single transmission while waiting for ACK on the receiving site.

17. The size of the Tx queue until the Transport layer suspends the application.

18. The index of the next buffer to be transmitted. (beginning of queue).

19. The index of the next buffer to be added to the queue. (end of queue).

20. The sequence number of the first frame and last frame in the queue.

21. The size of the Rx queue.

22. The next frame to be received by the Rx queue.

23. The sequence number of the frame to be received.

24. The expected sequence number of the next frame to be received.

25. The location of the next frame to be received in the Rx queue.

26. A temporary queue in case of holes in reception (the receiving sequence number is different from
expected). The data is similar to the Rx queue

27. Does Transport expect start session in the next frame to be received?

28. Is Sync ACK required?

29. Has Sync ACK arrived?

30. Was Sync ACK transmitted? Have new frames been received?

31. Is this Instance master or slave?

32. Is this Instance in Tx state?

33. Has a Reset been sent from the Master?

34. Has the current session been aborted?

22
 Software Diagnostics Output

35. Send ACK in next transmission?

36. Is this the first burst in the current transmission for sending Start Session?

37. Is the Transport layer retrying?

## 65 LEVEL = 1
no. of buffers in Tx queue : %%
no. of buffers in Rx queue : %%
no. of buffers in temp queue : %%

The number of MDLC frames in each queue in this instance of the Transport layer.

## 66 LEVEL = 10, 11
# of transmitted frames : %% 1
# of received frames : %% 2
# of re-transmitted frames : %% 3
# of received frames (with error) : %%
# of frames in Tx queue : %%
# of frames in Rx queue : %%
# of frames in Tx queue (held by link layer) : %%
# of frames in Tx queue (held by physical layer) : %%

1. The # of Transmitted Frames (does not include retransmission and acknowledgment frames.)

2. The # of Received Frames (includes only correct frames.)

3. The # of Re-transmitted Frames represents only frames rejected by the physical layer (do not use this
number; use the # of Re-transmitted Frames in the Link device).

MTE

## 80 LEVEL = 0
Unused RAM memory : %% 1
Total RAM handled by MTE : %% 2
Number of created tasks : %% 3
Number of created devices : %% 4
Spare stack for each task stack : %% 5
Spare stack for sup. stack : %% 5
Length of sup. stack (without spare) : %% 6
Unused sup. stack (without spare) : %% 7
Length of 1 task control block (tcb) : %% 8
Length of 1 device control block (dcb) : %% 8
Address of mt_curtaskid : %% 9
Address of mt_curprio : %% 9
Maximum allowed value for low task watchdog : %% 10
Maximum allowed value for high task watchdog : %% 10
Maximum reached value of low task watchdog : %% 11
Maximum reached value of high task watchdog : %% 11

1. The amount of unused memory in bytes.

23
 Software Diagnostics Output

2. The amount of memory that the MTE (the operating system) received at startup and distributed
among all of the instances that were created in the system.

3. The number of tasks (infinite threads) that were created according to the site configuration.

4. The total number of instances created by the MTE according to the site configuration.

5. The number of extra bytes for each stack. These bytes are designed to detect memory corruption.

6. The length in bytes of the supervisor stack.

7. The amount of unused bytes in the supervisor stack.

8. The length in bytes in the MTE structures — TCB (Task Control Block) and DCB (Device Control
Block).

9. Data on the current task (the task ID and the task priority).

10. The RTU tasks are wrapped by two inner tasks (high, low) which are to be reached by the CPU every
so and so ticks (the numbers are defined).

11. These two numbers are the maximum reached by the two tasks above.

## 81 LEVEL = 1
The list of all of the instances created, the key of each one of them and its address in memory.

## 82 LEVEL = 2
The list of all of the tasks created in the system, the stack address of each one of them, and the current
number of unused bytes.

24
 Software Diagnostics Output

## 84 LEVEL = 100
This media, software or hardware ("Product") obtained from Motorola
Solutions, Inc. ("Motorola Solutions") may include Motorola Solutions’
Software, Third Party Software (defined below), and/or Open Source Software
(defined below).

The object code or source code (collectively, the "Software") included

with the Product is the exclusive property of Motorola Solutions or its
licensors, and any use is subject to the terms and conditions of one or
more agreements in force between the purchaser of the Motorola Solutions
Product or licensee of the Motorola Solutions Software and Motorola
Solutions. SOFTWARE IS PROTECTED BY U.S. COPYRIGHT LAWS AND INTERNATIONAL
LAWS AND TREATIES. UNAUTHORIZED COPYING, DISTRIBUTION OR OTHER USE OF
THIS PRODUCT IS STRICTLY PROHIBITED. ANY DISTRIBUTION OR USE NOT
SPECIFICALLY APPROVED BY MOTOROLA SOLUTIONS IS STRICTLY PROHIBITED.

Motorola Solutions’ Software is subject to the commercial terms and

conditions entered into with Motorola Solutions, any other use is strictly
prohibited. Commercial Software licensed for redistribution by Motorola
Solutions ("Third Party Software") is subject to the terms and conditions
in force between Motorola Solutions and the licensor of the Third party
Software. The terms and conditions governing the usage of Third Party
Software may be part of the agreement entered into by the purchaser of
the Product with Motorola Solutions or separate Third Party Software
license agreement(s) included with the Product.

Software provided by Motorola Solutions which is covered by a publicly

available license governed solely under Copyright law, whereas the complete
terms and obligations of such license attach to a licensee solely through
the act of copying, using and/or distribution of the licensed Software, such
obligations often include one or more of attribution obligations, distribution
obligations, copyleft obligations, and intellectual property encumbrances is
referred to herein as "Open Source Software". The use of any Open Source
Software is subject to the licenses, terms and conditions of the commercial
agreement in force between the purchaser of the Product and Motorola Solutions
as well as the terms and conditions of the corresponding license of each
Open Source Software package. If there is a conflict between the terms and
conditions of any commercial agreement and the terms and conditions of the
Open Source Software license, the applicable Open Source Software license will
take precedence. Copies of the licenses for the included Open Source Software
as well as their attributions, acknowledgements, and software information
details, are listed below. Motorola Solutions is required to reproduce
the software licenses, acknowledgments and copyright notices as provided by
the authors and owners, thus, all such information is provided in its native
language form, without modification or translation.

For instructions on how to obtain a copy of any source code made publicly
available by Motorola Solutions related to Open Source Software distributed
by Motorola Solutions, you may send your request in writing to:

Motorola Solutions, Inc.

Open Source Software Management
1301 E. Algonquin Road
Schaumburg, IL 60196 USA.

In your request, please include the Motorola Solutions Product name and
version, along with the Open Source Software specifics, such as the Open
Source Software name and version.

25
 Software Diagnostics Output

Note: the source code for the Open Source Software included by Motorola
Solutions may be resident on the Product’s installation media provided with
the Product or on supplemental Product media. Please reference and review
the entire Motorola Solutions Open Source Software "Legal Notices" and any
corresponding "End User License Agreement" provided with the Product or the
commercial agreement under which the Product was purchased for details on
the availability, location and method for obtaining source code. Further,
depending on the license terms of the specific Open Source Software, source
code may not be provided. Please reference and review the entire Motorola
Solutions Open Source Software "Legal Notices" and "End User License
Agreement"
to identify which Open Source Software packages have source code provided
or available.

To view information regarding licenses, acknowledgments and required copyright

notices for Open Source Software used in this Product, please select "Legal
Notices"
from the graphical user interface of the Software (if applicable) or as
specified in the "Legal Notices" or End User License Agreement File/README
associated with the Product. Use of any Software is subject to acceptance of
the corresponding terms associated with the Software and by using the Software
you agree you have reviewed the terms and agreed to be bound by said terms.

MOTOROLA, MOTOROLA SOLUTIONS and the Stylized M Logo are trademarks or

registered trademarks of Motorola Trademark Holdings, LLC and are used under
license. All other trademarks are the property of Motorola Solutions, Inc. or
their respective owners. All rights reserved.

===========================================================================
PUBLICLY AVAILABLE SOFTWARE LIST
===========================================================================

===========================================================================

Name: CMU-SNMP

Version: 1.14

Description: Linux CMU-SNMP is a GNU/Linux port of the CMU SNMP system.

Motorola Solutions has modified the software.

Software Site: ftp://ftp.andrew.cmu.edu/pub/net/snmp/

Source Code: The Source Packages for CMU-SNMP are available from the
original Software Site, or may be acquired from Motorola
Solutions.
To obtain the Software from Motorola Solutions, please contact
Motorola Solutions using the methods described in the preamble
of
this Legal Notices Document.

License:

26
 Software Diagnostics Output

**********************************************************************
*
* Copyright 1998 by Carnegie Mellon University
*
* All Rights Reserved
*
* Permission to use, copy, modify, and distribute this software and its
* documentation for any purpose and without fee is hereby granted,
* provided that the above copyright notice appear in all copies and that
* both that copyright notice and this permission notice appear in
* supporting documentation, and that the name of CMU not be
* used in advertising or publicity pertaining to distribution of the
* software without specific, written prior permission.
*
* CMU DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING
* ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL
* CMU BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR
* ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS,
* WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION,
* ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS
* SOFTWARE.
*
* $Id: asn1.h,v 1.9 1998/08/07 20:18:46 ryan Exp $
* $Id: mibii.h,v 1.5 1998/05/06 04:07:03 ryan Exp $
* $Id: snmp_pdu.h,v 1.16 1998/05/06 04:07:47 ryan Exp $
* $Id: snmp-internal.h,v 1.8 1998/05/06 04:07:11 ryan Exp $
* $Id: snmp_vars.h,v 1.12 1998/05/06 04:07:52 ryan Exp $
* $Id: snmp_msg.h,v 1.6 1998/05/06 04:07:44 ryan Exp $
* $Id: snmp_error.h,v 1.11 1998/05/06 04:07:36 ryan Exp $
* $Id: snmp_compat.h,v 1.4 1998/05/06 04:07:30 ryan Exp $
* $Id: snmp_api_error.h,v 1.6 1998/09/01 03:05:19 ryan Exp $
*
**********************************************************************

Credits: N/A

===========================================================================

Name: NTP

Version: 4.2.0a

Description: NTP is a protocol designed to synchronize the clocks of

computers over a network.
Motorola Solutions has modified the software.

Software Site: http://www.ntp.org

Source Code: The Source Packages for NTP are available from the
original Software Site, or may be acquired from Motorola
Solutions.
To obtain the Software from Motorola Solutions, please contact
Motorola Solutions using the methods described in the preamble
of
this Legal Notices Document.

License:

27
 Software Diagnostics Output

***********************************************************************
* *
* Copyright (c) David L. Mills 1992-2003 *
* *
* Permission to use, copy, modify, and distribute this software and *
* its documentation for any purpose and without fee is hereby *
* granted, provided that the above copyright notice appears in all *
* copies and that both the copyright notice and this permission *
* notice appear in supporting documentation, and that the name *
* University of Delaware not be used in advertising or publicity *
* pertaining to distribution of the software without specific, *
* written prior permission. The University of Delaware makes no *
* representations about the suitability this software for any *
* purpose. It is provided "as is" without express or implied *
* warranty. *
* *
***********************************************************************

Credits:

The following individuals contributed in part to the Network Time Protocol

Distribution
Version 4 and are acknowledged as authors of this work.

Mark Andrews <[email protected]> Leitch atomic clock controller

Bernd Altmeier <[email protected]> hopf Elektronik serial line and PCI-
bus devices
Viraj Bais <[email protected]> and Clayton Kirkwood
<[email protected]>
port to WindowsNT 3.5
Michael Barone <michael,[email protected]> GPSVME fixes
Jean-Francois Boudreault <[email protected]>IPv6
support
Karl Berry <[email protected]> syslog to file option
Greg Brackley <[email protected]> Major rework of WINNT port. Clean
up recvbuf and
iosignal code into separate modules.
Marc Brett <[email protected]> Magnavox GPS clock driver
Piete Brooks <[email protected]> MSF clock driver, Trimble PARSE
support
Reg Clemens <[email protected]> Oncore driver (Current maintainer)
Steve Clift <[email protected]> OMEGA clock driver
Casey Crellin <[email protected]> vxWorks (Tornado) port and help with target
configuration
Sven Dietrich <[email protected]> Palisade reference clock driver,
NT adj. residuals,
integrated Greg's Winnt port.
John A. Dundas III <[email protected]> Apple A/UX port
Torsten Duwe <[email protected]> Linux port
Dennis Ferguson <[email protected]> foundation code for NTP Version 2
as specified in
RFC-1119
John Hay <jhay@@icomtek.csir.co.za> IPv6 support and testing
Glenn Hollinger <[email protected]> GOES clock driver
Mike Iglesias <[email protected]> DEC Alpha port
Jim Jagielski <[email protected]> A/UX port
Jeff Johnson <[email protected]> massive prototyping overhaul
Hans Lambermont <[email protected]> or
<[email protected]> ntpsweep
Poul-Henning Kamp <[email protected]> Oncore driver (Original author)

28
 Software Diagnostics Output

Frank Kardel <[email protected]> PARSE <GENERIC>

driver (14 reference
clocks), STREAMS modules for PARSE, support scripts, syslog cleanup William
L. Jones
<[email protected]> RS/6000 AIX modifications, HPUX
modifications
Dave Katz <[email protected]> RS/6000 AIX port
Craig Leres <[email protected]> 4.4BSD port, ppsclock, Magnavox GPS clock
driver
George Lindholm <[email protected]> SunOS 5.1 port
Louis A. Mamakos <[email protected]> MD5-based authentication
Lars H. Mathiesen <[email protected]> adaptation of foundation code for
Version 3 as specified
in RFC-1305
Danny Mayer <[email protected]>Network I/O, Windows Port, Code Maintenance
David L. Mills <[email protected]> Version 4 foundation: clock discipline,
authentication,
precision kernel; clock drivers: Spectracom, Austron, Arbiter, Heath, ATOM,
ACTS,
KSI/Odetics; audio clock drivers: CHU, WWV/H, IRIG
Wolfgang Moeller <[email protected]> VMS port
Jeffrey Mogul <[email protected]> ntptrace utility
Tom Moore <[email protected]> i386 svr4 port
Kamal A Mostafa <[email protected]> SCO OpenServer port
Derek Mulcahy <[email protected]> and Damon Hart-Davis <[email protected]>
ARCRON MSF clock
driver
Rainer Pruy <[email protected]> monitoring/trap
scripts, statistics file
handling
Dirce Richards <[email protected]> Digital UNIX V4.0 port
Wilfredo S?nchez <[email protected]> added support for NetInfo
Nick Sayer <[email protected]> SunOS streams modules
Jack Sasportas <[email protected]> Saved a Lot of space on the
stuff in the
html/pic/ subdirectory
Ray Schnitzler <[email protected]> Unixware1 port
Michael Shields <[email protected]> USNO clock driver
Jeff Steinman <[email protected]> Datum PTS clock driver
Harlan Stenn <[email protected]> GNU automake/autoconfigure makeover, various
other bits (see
the ChangeLog)
Kenneth Stone <[email protected]> HP-UX port
Ajit Thyagarajan <[email protected]>IP multicast/anycast support
Tomoaki TSURUOKA <[email protected]>TRAK clock driver
Paul A Vixie <[email protected]> TrueTime GPS driver, generic TrueTime clock
driver
Ulrich Windl <[email protected]> corrected and validated
HTML documents
according to the HTML DTD

===========================================================================

Name: ZLIB

Version: 1.2.3, July 18th, 2005

Description: zlib is a general purpose compression library.

29
 Software Diagnostics Output

Software Site: http://www.zlib.net/

Source Code: The Source Packages for ZLIB can be found at \OSS\ZLIB
in the Motorola Solutions Product Media. You may also acquire
the Source
Packages from Motorola Solutions using the request methods
described in the
preamble of this Legal Notices Document.

License:

zlib general purpose compression library

version 1.2.3, July 18th, 2005

Copyright (C) 1995-2005 Jean-loup Gailly and Mark Adler

This software is provided 'as-is', without any express or implied

warranty. In no event will the authors be held liable for any damages
arising from the use of this software.

Permission is granted to anyone to use this software for any purpose,

including commercial applications, and to alter it and redistribute it
freely, subject to the following restrictions:

1. The origin of this software must not be misrepresented; you must not
claim that you wrote the original software. If you use this software
in a product, an acknowledgment in the product documentation would be
appreciated but is not required.
2. Altered source versions must be plainly marked as such, and must not be
misrepresented as being the original software.
3. This notice may not be removed or altered from any source distribution.

Jean-loup Gailly [email protected]

Mark Adler [email protected]

Credits: See above.

===========================================================================

Name: ZLIB

Version: 1.1.3, July 9th, 1998

Description: zlib is a general purpose compression library.

Software Site: http://www.zlib.net/

Source Code: The Source Packages for ZLIB are available from the
original Software Site, or may be acquired from Motorola Solutions.
To obtain the Software from Motorola Solutions, please contact
Motorola Solutions using the methods described in the preamble of
this Legal Notices Document.

License:

version 1.1.3, July 9th, 1998

30
 Software Diagnostics Output

Copyright (C) 1995-1998 Jean-loup Gailly and Mark Adler

This software is provided 'as-is', without any express or implied

warranty. In no event will the authors be held liable for any damages
arising from the use of this software.

Permission is granted to anyone to use this software for any purpose,

including commercial applications, and to alter it and redistribute it
freely, subject to the following restrictions:

1. The origin of this software must not be misrepresented; you must not
claim that you wrote the original software. If you use this software
in a product, an acknowledgment in the product documentation would be
appreciated but is not required.
2. Altered source versions must be plainly marked as such, and must not be
misrepresented as being the original software.
3. This notice may not be removed or altered from any source distribution.

Jean-loup Gailly Mark Adler

[email protected] [email protected]

Credits: See above.

===========================================================================
Open source notice is continued by diagnostics of device=MTE Level=101
===========================================================================

The licenses for all open source software used in the firmware.

31
 Software Diagnostics Output

## 85 LEVEL = 101

Open source notice continued:

===========================================================================

Name: libxml2

Version: 2.7.6

Description: Parsing XML and making queries by Xpath.

Motorola Solutions has modified the software.

Software Site: http://xmlsoft.org/index.html

Source Code: The Source Packages for libxml2 can be found at \OSS\libxml2
in the Motorola Solutions Product Media. You may also acquire the Source
Packages from Motorola Solutions using the request methods described in the
preamble of this Legal Notices Document.

License: Except where

otherwise noted in the source code (e.g. the files hash.c,
list.c and the trio files, which are covered by a similar licence but
with different Copyright notices) all the files are:

Copyright (C) 1998-2003 Daniel Veillard. All Rights Reserved.

Permission is hereby granted, free of charge, to any person obtaining a

copy
of this software and associated documentation files (the "Software"), to
deal
in the Software without restriction, including without limitation the
rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is fur-
nished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FIT-
NESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
DANIEL VEILLARD BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
WHETHER
IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
CON-
NECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Except as contained in this notice, the name of Daniel Veillard shall not
be used in advertising or otherwise to promote the sale, use or other deal-
ings in this Software without prior written authorization from him.
hash.c: chained hash tables
* Reference: Your favorite introductory book on algorithms
* Copyright (C) 2000 Bjorn Reese and Daniel Veillard.
* Permission to use, copy, modify, and distribute this software for any
* purpose with or without fee is hereby granted, provided that the above
* copyright notice and this permission notice appear in all copies.

32
 Software Diagnostics Output

* THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR IMPLIED
* WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF
* MERCHANTIBILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE AUTHORS AND
* CONTRIBUTORS ACCEPT NO RESPONSIBILITY IN ANY CONCEIVABLE MANNER.
* Author: [email protected]

list.c: lists handling implementation

* Copyright (C) 2000 Gary Pennington and Daniel Veillard.
* Permission to use, copy, modify, and distribute this software for any
* purpose with or without fee is hereby granted, provided that the above
* copyright notice and this permission notice appear in all copies.
* THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR IMPLIED
* WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF
* MERCHANTIBILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE AUTHORS AND
* CONTRIBUTORS ACCEPT NO RESPONSIBILITY IN ANY CONCEIVABLE MANNER.
* Author: [email protected]

Trio.c
Copyright (C) 1998 Bjorn Reese and Daniel Stenberg.
* Permission to use, copy, modify, and distribute this software for any
* purpose with or without fee is hereby granted, provided that the above
* copyright notice and this permission notice appear in all copies.
* THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR IMPLIED
* WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF
* MERCHANTIBILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE AUTHORS AND
* CONTRIBUTORS ACCEPT NO RESPONSIBILITY IN ANY CONCEIVABLE MANNER.

Credits: Additional copyrights:

Copyright (C) 1991 Massachusetts Institute of Technology
Copyright (C) 1992-2009 Free Software Foundation, Inc.
Copyright (C) 1998-1999 W3C (MIT, INRIA, Keio),
Copyright (C) 1998-2003 Daniel Veillard. All Rights Reserved.
Copyright (C) 1998, 2000 Bjorn Reese and Daniel Stenberg.
Copyright (C) 1999 Microsoft Corporation
Copyright (C) 1999 Netscape Communications
Copyright (C) 2000 International Press Telecommunications Council (IPTC)
Copyright (C) 2001 OASIS
Copyright (C) 2000 Bjorn Reese and Daniel Veillard.
Copyright (C) 2000 Gary Pennington and Daniel Veillard.
Copyright (C) 2001 Bjorn Reese <[email protected]>
Copyright (C) 2001 Bjorn Reese and Daniel Stenberg.
Copyright (C) 2002, 2003 John Fleck
Copyright (C) 2003 Daniel Veillard.

AUTHORS
Daniel Veillard <[email protected]>
Bjorn Reese <[email protected]>
William Brack <[email protected]>
Igor Zlatkovic <[email protected]> for the Windows port
Aleksey Sanin <[email protected]>

===========================================================================

Name: OpenSSL

Version: 1.0.0e

Description: Encryption / Network utiltities/libraries.

33
 Software Diagnostics Output

Motorola Solutions has modified the software.

Software Site: http://www.openssl.org/

Source Code: The Source Packages for OpenSSL can be found at \OSS\OpenSSL
in the Motorola Solutions Product Media. You may also acquire the Source
Packages from Motorola Solutions using the request methods described in the
preamble of this Legal Notices Document.

License:

LICENSE ISSUES
==============

The OpenSSL toolkit stays under a dual license, i.e. both the conditions
of
the OpenSSL License and the original SSLeay license apply to the toolkit.
See below for the actual license texts. Actually both licenses are BSD-
style
Open Source licenses. In case of any license issues related to OpenSSL
please contact [email protected].

OpenSSL License
---------------

====================================================================
* Copyright (c) 1998-2011 The OpenSSL Project. All rights reserved.
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
* are met:
*
* 1. Redistributions of source code must retain the above copyright
* notice, this list of conditions and the following disclaimer.
*
* 2. Redistributions in binary form must reproduce the above copyright
* notice, this list of conditions and the following disclaimer in
* the documentation and/or other materials provided with the
* distribution.
*
* 3. All advertising materials mentioning features or use of this
* software must display the following acknowledgment:
* "This product includes software developed by the OpenSSL Project
* for use in the OpenSSL Toolkit. (http://www.openssl.org/)"
*
* 4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to
* endorse or promote products derived from this software without
* prior written permission. For written permission, please contact
* [email protected].
*
* 5. Products derived from this software may not be called "OpenSSL"
* nor may "OpenSSL" appear in their names without prior written
* permission of the OpenSSL Project.
*
* 6. Redistributions of any form whatsoever must retain the following
* acknowledgment:
* "This product includes software developed by the OpenSSL Project
* for use in the OpenSSL Toolkit (http://www.openssl.org/)"
*
* THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY

34
 Software Diagnostics Output

* EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE

* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
* PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR
* ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
* SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
* NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
* LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
* STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
* ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
* OF THE POSSIBILITY OF SUCH DAMAGE.
* ====================================================================
*
* This product includes cryptographic software written by Eric Young
* ([email protected]). This product includes software written by Tim
* Hudson ([email protected]).
*
*/

Original SSLeay License

-----------------------

/* Copyright (C) 1995-1998 Eric Young ([email protected])

* All rights reserved.
*
* This package is an SSL implementation written
* by Eric Young ([email protected]).
* The implementation was written so as to conform with Netscapes SSL.
*
* This library is free for commercial and non-commercial use as long as
* the following conditions are aheared to. The following conditions
* apply to all code found in this distribution, be it the RC4, RSA,
* lhash, DES, etc., code; not just the SSL code. The SSL documentation
* included with this distribution is covered by the same copyright terms
* except that the holder is Tim Hudson ([email protected]).
*
* Copyright remains Eric Young's, and as such any Copyright notices in
* the code are not to be removed.
* If this package is used in a product, Eric Young should be given
attribution
* as the author of the parts of the library used.
* This can be in the form of a textual message at program startup or
* in documentation (online or textual) provided with the package.
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
* are met:
* 1. Redistributions of source code must retain the copyright
* notice, this list of conditions and the following disclaimer.
* 2. Redistributions in binary form must reproduce the above copyright
* notice, this list of conditions and the following disclaimer in the
* documentation and/or other materials provided with the distribution.
* 3. All advertising materials mentioning features or use of this software
* must display the following acknowledgement:
* "This product includes cryptographic software written by
* Eric Young ([email protected])"
* The word 'cryptographic' can be left out if the rouines from the
library
* being used are not cryptographic related :-).

35
 Software Diagnostics Output

* 4. If you include any Windows specific code (or a derivative thereof)

from
* the apps directory (application code) you must include an
acknowledgement:
* "This product includes software written by Tim Hudson
([email protected])"
*
* THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS'' AND
* ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE
* ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
* FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL
* DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
* OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
STRICT
* LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
* OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
* SUCH DAMAGE.
*
* The licence and distribution terms for any publically available version
or
* derivative of this code cannot be changed. i.e. this code cannot simply
be
* copied and put under another distribution licence
* [including the GNU Public Licence.]
*/

Credits: Additional copyrights:

Copyright (C) 1986, 2002 Sun Microsystems, Inc.
Copyright (C) 1993 Microsoft Corp.
Copyright (C) 1995 Patrick Powell
Copyright (C) 1995-1998 Eric A. Young
Copyright (C) 1995-1998 Eric A. Young, Tim J. Hudson
Copyright (C) 1998-2000 nCipher Corporation Limited
Copyright (C) 1998-2011 The OpenSSL Project
Copyright (C) 1999 Bodo Moeller
Copyright (C) 2000 Broadcom Corporation
Copyright (C) 2001 Baltimore Technologies Ltd.
Copyright (C) 2001 International Business Machines Corp.
Copyright (C) 2002 Bob Beck <[email protected]>
Copyright (C) 2002 Markus Friedl
Copyright (C) 2002 The OpenTSA Project
Copyright (C) 2002 Theo de Raadt
Copyright (C) 2004 Kungliga Tekniska Hogskolan
Copyright (C) 2004 Richard Levitte <[email protected]>
Copyright (C) 2005 Hewlett-Packard Development Company, L.P.
Copyright (C) 2005 Nokia
Copyright (C) 2005-2006 Cryptocom LTD
Copyright (C) 2006 NTT (Nippon Telegraph and Telephone Corporation)
Copyright (C) 2007 KISA(Korea Information Security Agency)
Copyright (C) 2008 Andy Polyakov <[email protected]>

ACKNOWLEDGEMENTS
The OpenSSL project depends on volunteer efforts and financial support
from
the end user community. That support comes in the form of donations and
paid

36
 Software Diagnostics Output

sponsorships, software support contracts, paid consulting services

and commissioned software development.

Since all these activities support the continued development and

improvement
of OpenSSL we consider all these clients and customers as sponsors of the
OpenSSL project.

We would like to identify and thank the following such sponsors for their
past
or current significant support of the OpenSSL project:

Very significant support:

OpenGear: www.opengear.com

Significant support:

PSW Group: www.psw.net

Please note that we ask permission to identify sponsors and that some
sponsors
we consider eligible for inclusion here have requested to remain
anonymous.

Additional sponsorship or financial support is always welcome: for more

information please contact the OpenSSL Software Foundation.

===========================================================================

Name: sha2

Version: February 2, 2007

Description: Hashing Algorithm.

Software Site: http://www.ouah.org/ogay/sha2/

Source Code: The Source Packages for sha2 can be found at \OSS\sha2
in the Motorola Solutions Product Media. You may also acquire the Source
Packages from Motorola Solutions using the request methods described in the
preamble of this Legal Notices Document.

License:
From source files:
* Copyright (C) 2005, 2007 Olivier Gay <[email protected]>
* All rights reserved.
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
* are met:
* 1. Redistributions of source code must retain the above copyright
* notice, this list of conditions and the following disclaimer.
* 2. Redistributions in binary form must reproduce the above copyright
* notice, this list of conditions and the following disclaimer in the
* documentation and/or other materials provided with the distribution.
* 3. Neither the name of the project nor the names of its contributors
* may be used to endorse or promote products derived from this software

37
 Software Diagnostics Output

* without specific prior written permission.

*
* THIS SOFTWARE IS PROVIDED BY THE PROJECT AND CONTRIBUTORS ``AS IS'' AND
* ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE
* ARE DISCLAIMED. IN NO EVENT SHALL THE PROJECT OR CONTRIBUTORS BE LIABLE
* FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL
* DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
* OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
STRICT
* LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
* OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
* SUCH DAMAGE.

Credits: See above

The continuation of licenses for all open source software used in the firmware.

38
 Software Diagnostics Output

LINK LAYER DEVICE = COM1L, RTU:L, …

## 112 LEVEL = 0
Number of boxes in table (size of Tx queue) : %% 1
Number of ack buffers to alloc : %% 2
Sequence (most + least - up to 13 bits) : %% 3
Number of retries until positive ack received : %% 4
Number of retries for negative ack (busy) : %% 5
Interval until next retry in case of busy : %% 6
Number of retries for setcall frame : %% 7
Simultaneous (4 channel priority) : %% 8
Specific logical address : %% 9
System address : %% 10
Number of holds : %% 11
Interval between holds : %% 12
All RTU range response : %% 13
Stop using AUTH TX state (flag, 1=YES) : %% 14
Start using AUTH TX state (flag, 1=YES) : %% 14
Stop using AUTH RX state (flag, 1=YES) : %% 15
Start using AUTH RX state (flag, 1=YES) : %% 15
Stop obeying AUTH TX (flag, 1=YES) : %% 18
Start obeying AUTH TX (flag, 1=YES) : %% 19
Stop obeying AUTH RX (flag, 1=YES) : %% 10
Start obeying AUTH RX (flag, 1=YES) : %% 11
Is AUTH active TX (flag, 1=YES) : %% 12
Is AUTH active RX (flag, 1=YES) : %% 13
Obeying AUTH TX (flag, 1=YES) : %% 14
Obeying AUTH RX (flag, 1=YES) : %% 15
TimeAuth handle: : %% 16
TimeAuth device key (HEX): : %% 17

1. The number of MDLC frames that the Link layer can handle simultaneously.

2. The number of ACK frames that are available to the instance Link for transmitting ACK for the
receiving MDLC frames.

3. The number of bits reserved for the sequence number in the Link layer protocol of the MDLC Frame.

4. The number of times the MDLC frame was retried without receiving ACK.

5. The number of MDLC frame retries that received Busy ACK. (The receiving site does not have
enough room to handle it because of overload).

6. The number of seconds between transmission attempts in case of Busy ACK.

7. The number of times the broadcast frame was retried.

8. The number of different addresses the Link will transmit to simultaneously.

9. The RTU Site ID.

10. The RTU System address.

39
 Software Diagnostics Output

11. The time that the Link layer waits when the Physical layer returns Busy to the transmission attempts
of the Link layer in “private conversation”, until it retries.

12. The number of times the Link layer will try to transmit to the Physical layer, if the latter returns Busy
in “private conversation”.

13. The Link layer is capable of answering a range of addresses. This number is the upper bound that the
RTU reacts to, whereas the lower bound is the Site ID.

14. Flag which indicates AUTH TX state (1=YES, 0=NO)

15. Flag which indicates AUTH RX state (1=YES, 0=NO)

16. Flag which indicates Stop obeying AUTH TX (1=YES, 0=NO)

17. Flag which indicates Start obeying AUTH TX (1=YES, 0=NO)

18. Flag which indicates Stop obeying AUTH RX (1=YES, 0=NO)

19. Flag which indicates Start obeying AUTH RX (1=YES, 0=NO)

20. Flag which indicates that AUTH is active for TX (1=YES, 0=NO)

21. Flag which indicates that AUTH is active for RX (1=YES, 0=NO)

22. Flag which indicates Obeying AUTH TX (1=YES, 0=NO)

23. Flag which indicates Obeying AUTH RX (1=YES, 0=NO)

24. TimeAuth identifier

25. TimeAuth device key (HEX)

## 113 LEVEL = 1
Address 0 to transmit in same snapshot : %% 1
Address 1 to transmit in same snapshot : %% 1
Address 2 to transmit in same snapshot : %% 1
Address 3 to transmit in same snapshot : %% 1
Network device key : %% 2
Physical device key : %% 3
Physical pin’s table : %% 3
Last reported station in fail : %% 4
Port fail flag : %% 5
‘one to one’ flag : %% 6
Full duplex flag : %% 7
# of frames in Tx queue : %% 8
# of frames in ‘wait for ack’ queue : %% 9
# of frames in ‘busy & setcall’ queue : %% 10
# of frames in ‘busy & finish’ queue : %% 11
‘private conversation’ flag : %% 12

1. The Link layer is capable of sending to up to four different addresses simultaneously. These fields
contain the last four target addresses transmitted in the same transmission.

2. The Network layer key.

40
 Software Diagnostics Output

3. The pins table and key of the Physical layer below link. The Link layer is capable of connecting to
any of the different physical media.

4. The last unit that has been reported to be in fail state.

5. The physical port in fail.

6. Mark if the link answers to the local address.

7. Mark if the link is full duplex.

8. The number of frames currently in the Tx queue.

9. The number of frames currently in the Wait for ACK queue .

10. The number of frames currently in the Busy and Broadcast queue that are waiting for the timeout
between retries.

11. The number of frames waiting for the timeout between retries to be over and to be transmitted before
new data frames waiting in the Tx queue.

12. Whether link functions in the private conversation mode (not in use in RTU).

## 114 LEVEL = 2
PosACK Busy-STCALL IsFree Slice-Len Authenticate AUTH-Offset

PosACK Number of retries until positive ACK is received.

Busy-STCALL Number of retries for negative ACK or SETCALL.

IsFree Whether the box is free: 1 - box is free, 0 - box is occupied.

slice_len Length in bytes of the Link's slice.

Authenticate Whether the frame should be authenticated: 1 - Authenticate this frame,

0 - do nothing

AUTH-Offset The offset in the Link's protocol of the authentication stamp.

41
 Software Diagnostics Output

## 115 LEVEL = 10, 11

# of transmitted frames : %% 1
# of re-transmitted frames : %% 2
# of received frames : %% 3
# of received frames (with error) : %%
# of times that link was enabled : %%
# of times that link was disabled : %%

Ignored frame(s) with unexpected source site ID:

-since source site ID was equal to self site ID (1=Yes,0=No): %%4
-since source site ID was LOCAL (1=Yes,0=No): %%
-since source site ID was SETCALL (1=Yes,0=No): %%5

1. The # of Transmitted Frames does not include retransmission and acknowledgment frames.

2. The # of Re-transmitted Frames represents only frames rejected by the physical layer (do not use this
number; use the # of Re-transmitted Frames in the Link device).

3. The # of Received Frames includes only correct frames.

4. The number of frame(s) that were ignored because their source site ID is equal to the self site ID. This
generally indicates that there are two or more sites with the same site ID.

5. The Number of frame(s) that were ignored because their source site ID is equal to SETCALL. This
generally indicates that there is a site ID equal to the System Address.

NETWORK STOCK (NSTOCK)

## 144 LEVEL = 0
RAM stock size : %% 1
RAM stock length : %% 2
Network configuration size : %% 3
Was network configuration downloaded ? : %% 4
Used site id for download : %% 5
Used link id for download : %% 6
Is it a node ? : %% 7
Does alternative path to local link exist ? : %% 8
# of entries in Remote Failed Links table : %% 9
Size of Remote Failed Links table : %% 10
Remote Failed Links table entry timeout : %% 11

1. The bank size of learned paths by the Network program.

2. The number of learned paths currently in the bank.

3. The number of paths in the network loaded by the RTU.

4. Whether the Network configuration was loaded to the flash memory.

5. The Site ID which was used for loading the network (must be the same as the self site ID).

6. The Link ID which was used for loading the network (must be one of the RTU links).

7. Whether the RTU is a node in the network.

42
 Software Diagnostics Output

8. Does the network file downloaded to the RTU have the 'alternative path to local link' feature on?
(YES=1; NO=0)

9. The number of entries in the Remote Failed Links Table used to identify failed links.

10. The maximum size of Remote Failed Links table.

11. The number of minutes that an entry will remain in the Remote Failed Links table before being
erased. This prevents an entry from remaining in the table forever if the link restoration message is
lost.

## 145 LEVEL = 1
Nothing in stock *

Marked with * if no path was learned, otherwise a table of the learned paths appears:
Dest Link Via Site Thru Link

## 146 LEVEL = 2
Nothing in scf *

Marked with * if no network was downloaded, otherwise as in ## 145.

## 147 LEVEL = 3
Nothing in direct link scf *

Marked with * if no multiple direct link exists, otherwise as in ## 145.

## 148 LEVEL = 11
# of times remote failed links table was full : %% 1
# of time tried to add data to remote failed links
table while it was disabled : %% 2

1. The number of times the Remote Failed Links table was full.

2. The number of times an attempt was made to add data to the Remote Failed Links table while it was
disabled.

## 151 LEVEL = 4
Pointer to authentication information header : %% 1

1. Points to the header of the authentication information.

43
 Software Diagnostics Output

## 153 LEVEL = 5
Remote Failed Link - Table :
Table dest dest fail report is me report via via fail
index link site link site orig? back? link site counter
%%1 %%2 %%3 %%4 %%5 %%6 %%7 %%8 %%9 %%10

1. Index into the Remote Failed Link table diagnostic display.

2. The Link ID of the link which leads to the destination RTU, i.e. the last link in the routing path.

3. The Site ID of the RTU to which the frame is to be transmitted, i.e. the frame destination site.

4. The Link ID of the failed link.

5. The Site ID of the site reporting the failed link.

6. Is the RTU the originator of the frame? (1=YES; 0=NO)

7. When the failed link is restored, should this node transmit a "restored link" frame or just delete the
entry from the table? (1=YES; 0=NO)

8. The Link ID of the link used by the failed frame to access its neighbor site (via site) when trying to
reach the destination site.

9. The Site ID of the neighbor site used by the failed frame when trying to reach the destination site.

10. The amount of time that has passed since the failure was discovered.

Note: The Remote Failed Links table is dynamic, so entries may move from one location to another,
without changing the table meaning and information. (See Table index in #1 above.)

If the Remote Failed Links table is empty, the diagnostic will be:
Nothing in Remote Failed Link Table

If the Remote Failed Links table cannot be accessed, the diagnostic will be:
Unable to lock semaphore for table. Can not list data.

## 155 LEVEL = 255

Stock device levels information:
level 0 - Get STOCK parameters
level 1 - Get Stock Table
level 2 - Get SCF Table
level 3 - Get Directs Link Table
level 4 - Get Authentication header
level 5 - Get Remote Failed Link Table
level 10 - Get & reset statistics
level 11 - Get statistics

This lists all diagnostics provided for the device at all its supported levels.

44
 Software Diagnostics Output

USERROM (USRROM)

## 160 LEVEL = 0
Does ladder application exist ? : %% 1
Is ladder application running ? : %% 2
Ladder application (ROM) address : %% 3
Start of rungs code (ROM) address : %% 4
User RAM base address : %% 5
Allocated user RAM length : %% 6
Diffs. down address : %% 7
Diffs. up address : %% 8

1. Whether the application ladder is loaded in flash memory.

2. Whether the application ladder runs in flash memory.

3. The memory start address reserved for ladder application.

4. The number of bytes reserved for the ladder application.

5. The memory start address reserved the user RAM.

6. The number of bytes reserved for user RAM.

7. The address of the beginning of differentiators down area in memory.

8. The address of the beginning of differentiators up area in memory.

## 161 LEVEL = 1
status = U_STOP => 161 1
U_NONE => 162 2
U_RUN => 163 3

1. Application exists but is stopped.

2. There is no application.

3. Application exists and running.

USERROM application status.

## 162 LEVEL = 1
Application code does not exist.

The system was unable to access the PPH (pulses per hour) database of the ladder application. This
indicates some database corruption. Please reload the application. If the message appears again, please
consult product group.

45
 Software Diagnostics Output

## 163 LEVEL = 1
Flow input scan rate: %% * 10msec. 1
Minimum calculation period in scans: %% (100 / %% percent accuracy) 2
Number of pph columns: %% 3
Total number of pph elements: %% 4

1. Time period in units of 10msec between two successive scans of each digital input for which PPH is
being performed.

2. Minimum time period between two PPH calculations (the time is in scan units as described above).

3. The number of PPH type columns.

4. The total number of PPH elements.

## 165 LEVEL = 1
Flash sets
----------
Type Operation Start End Burn_adr Source length Erased_len

Type The type of flash: (2=user application flash, 3=logging flash).

Operation The type of operation to be performed on the specified flash (0=Erase, 1=Program,
0xFFFE=Abort, 0xFFFF=no operation (default)).

Start The starting address of the flash memory.

End The ending address of the flash memory.

Burn_adr The address of the flash memory which is to be programmed.

Source The source address of the information to be written to the flash.

length The size of the information to be written to the flash.

Erased_len The size of the memory that was actually erased.

## 166 LEVEL = 2
%%1
CURR operation on FLASH memory: %%2
Last file ID manipulated in FLASH memory: %%3
Length of data burned to FLASH memory: %%4
Return code of last operation on FLASH memory: %%5
File name manipulated in FLASH memory: %%6

The indicators above are used by the 'burn/erase' task when handling a certain file.

1. File type- either Application files or Logging files.

2. The CURRent operation being performed on the flash memory. May be one of:
- erasing a file from flash memory
46
 Software Diagnostics Output

- creating a new/overwriting an existing file in flash memory

- appending to an existing file in flash memory

3. The ID of the last file to be manipulated in the flash memory.

4. The length of the data burned to the flash memory in bytes.

5. The return code of the last operation performed on the flash memory.

6. The name of the last file to be manipulated in the flash memory, e.g. conf.30, where conf is the name
and 30 is the internal file type suffix.

## 167 LEVEL = 10, 11

%% 1
# Time 'write' failed %%2

1. File type- either Application files or Logging files.

2. Logs the number of times the writing/appending of data to a flash file failed.

## 168 LEVEL = 3
Ucalls:
Name Related function address
----------------------------------------------

This table lists all ucalls (name and related function address) used in the RTU's ladder application.

Note: If the related function does not exist in RTU's run-time code, the related function address of this
ucall will be the address of 'Unresolved Ucall function' whose address is specified in this diagnostic.

## 169 LEVEL = 255

Level 0 - Application state
Level 1 - PPH
Level 2 - Flash
Level 3 - C Application
Level 4 - Expansion Frames
Level 5 - Redundancy Tb2Cpy CALL
Level 10 - Statistics - view and clear
Level 11 - Statistics - view
Level 255 - This list

This lists all diagnostics provided for the device at all its supported levels.

47
 Software Diagnostics Output

## 170 LEVEL = 4
Expansion Frames errors:
-----------------------

get Frame Id - no table - %%

set Frame Id - no table - %%
get Frame Id - invalid - %%
set Frame Id - invalid - %%
set Frame Id - failed to get a reserved flag - %%
set Frame Id - failed to get a reserved value - %%
set Frame Id - no Expansions Reserved Flags table - %%
set Aux Id - no PS1 or PS2 table - %%

The expansion frame errors above will appear in the RTU’s error logger one time. This diagnostic
displays the actual number of time each error occurred.

## 171 LEVEL = 5
Redundancy Tb2Cpy CALL diagnostics:
-----------------------------------
Is Cpu Active? %%1
Registered in rdndsrv module for copy services? %%2
Copy processed locked by a previous copy? %%3
Size of the allocated memory %%4
Maximum size of allocated memory %%5
Maximum size of each block in the copy process %%6
Allocated memory address %%7

1. In a redundant system, whether the CPU is the active or standby CPU.

2. Yes (=1) if redundancy is supported. No (=0) if redundancy is not supported OR if we failed to register
in the rdndsrv service.

3. If redundancy is supported:

4. Current size of the memory allocated for the Tb2Cpy CALL process. Used to keep the copied tables
information.

5. Maximum size (Configuration parameter) of the memory allocated for the Tb2Cpy CALL process, to
keep the copied tables information.

6. Internal use only.

48
 Software Diagnostics Output

## 172 LEVEL = 100

CPU diagnostics:
-------------------------------
Unit type :%%1
System version :%%2-%%-%%
Boot strap version :%%3-%%-%%
Site ID :%%4
System Address :%%5
FPGA version :%%6.%%.%%
System serial number :%%7
Configuration version :%%8
Configuration CRC (IO CRC) :%%9
System (Image) CRC :%%10
Security Signature :%%11
Security Firmware :%%12
CPU serial number :%%13

1. The RTU type. Can be one of: 52 (ACE3680), 54 (ACE3610), 55 (ACE3640), 57 (ACE IO
expansion), 58 (ACE4600 IP GW).

2. System version information: Version – Type – Build Number. Type can be one of: Release,
Alpha, Beta, Development, Bootstrap, Expansion loader, Boot line.

3. Boot strap version information: Version – Type – Build Number. Type can be one of: Release,
Alpha, Beta, Development, Bootstrap, Expansion loader, Boot line.

4. Site ID as defined in the site configuration.

5. System address as defined in the site configuration.

6. FPGA version: Version- Sub version – Sub version (Number-Number-Number).

7. The RTU serial number from factory, unique for each RTU.

8. Site configuration version, according to the STS version.

9. I/O Configuration CRC, according to the I/O modules type in the configuration.

10. System CRC, according to the system burned in the unit.

11. 1= CPU has a security signature burned on the board, 0= CPU does not have a security signature.

12. 1= CPU has secured firmware burned in the RTU. 0= CPU does not have secured firmware.

13. The CPU serial number from factory, unique for each CPU.

49
 Software Diagnostics Output

NETWORK (NETWRK)

## 180 LEVEL = 0
# of links actually connected to network layer : %% 1
Transport interface key : %% 2
Formatted buffers heap key 1 : %% 3
Formatted buffers heap key 2 : %% 3
Network stock key : %% 4
Default central link key : %% 5
Default central via link-id : %% 6
Default central thru site-id : %% 7
The unit site-id : %% 8
The default central flag : %% 9
The network transparent flag : %% 10
Response up to : %% 11
Time To Live Counter preset value : %% 12
Is Remote Fail Link detection enabled? : %% 13
Re-route returned frames? : %% 14
Current communication links : %% 15

1. The number of links registered on the network layer, when each zone is considered a separate link.

2. The Transport Multiplex layer key.

3. Heap keys. Identifier of heap from which to take buffers for the Network to transmit Default central
location, and also to duplicate MDLC frame, if needed.

4. The network bank key.

5. The link key through which MDLC frames should be channeled in case of Dest = default central.

6. The link ID of the Default control path in the unit.

7. The site ID where the MDLC frame is directed towards the Default Central.

8. The unit site ID.

9. This parameter determines whether this site is the Default Central.

10. Is the Network “transparent,” i.e. is there only a single path for transmission?

11. The sum of the unit Site ID and the advanced network layer parameter from the site configuration
named Addr. range response for 'All RTU simulation'.

12. The preset value for the Time To Live counter, which is inserted into each frame by the frame
originator. 0 means Time To Live Counter feature is not activated. The value must be greater than
the longest path in the network (maximum numbers of nodes in the entire longest path). All units in
the system must support this feature or frames will be discarded.

13. Flag that indicates whether the Remote Fail Links Detection mechanism is enabled or disabled.

14. When the Remote Failed Links Table feature is enabled, this parameter determines whether a returned
frame from a remote failed link is dropped or rerouted to the destination using another available link.

15. A list of links currently available to the node.

50
 Software Diagnostics Output

## 181 LEVEL = 10, 11

# of transmitted frames : %% 1
# of received frames : %% 2
# of received frames (with error) : %% 3
# of received frames (with protocol not supported) : %% 4
# of frames discarded due to Time To Live counter : %% 5
Minimum value of Time To Live counter via this node : %% 6
Source of last frame discarded due to TTL expiration : %% 7

1. The # of transmitted frames does not include retransmission and acknowledgment frames.

2. The # of received frames includes only correct frames.

3. The # of received error frames.

4. The # of received whose protocol is not supported.

5. The # of frames which were discarded because the Time to Live counter expired.

6. The value of the Time to Live (TTL) counter from frames passing through this site. The value is
updated in the RTU diagnostic only if the TTL of the current passing frame is lower than the current
diagnostic stored in RTU. (The field will contain the minimum of TTL value of frames passed
through this site since the last time the diagnostic was cleared - level 10).

7. The source RTU of the last frame which was discarded due to Time To Live counter expiration.

## 183 LEVEL = 1
Enable remote STS connection : %%

Whether communication with remote STS is enabled or disabled.

## 185 LEVEL = 255

Network device levels information:
level 0 - Get Network parameters
level 10 - Get & reset statistics
level 11 - Get statistics

This lists all diagnostics provided for the device at all its supported levels.

MINISESSION (WIDE, EVNT, STCL, ASCLI, ASSER,

FEPRTU)
WIDE RTU-to-RTU communication device
EVNT Event & Burst device
STCL Broadcast reception device
ASCLI Authentication client (RTU)
ASSER Authentication server
FEPRTU ACE1000 FEP/RTU

51
 Software Diagnostics Output

## 200 LEVEL = 0
Application id : %% 1
No. of boxes in device : %% 2
No. of retries : %% 3
Interval between retries : %% 4
Time till flushing rcv frames : %% 5
Protocol flags : %% 6
Does task exist ? : %% 7
Is flushing needed ? : %% 8
Heap key : %% 9
Index of first box in free queue : %% 10
Index of first box in “wait for answ” queue : %% 11
Index of first box in “answers from outside” queue : %% 12
Index of first box in “request to applic” queue : %% 13
Index of first box in “waiting for applic answer” queue : %% 14
Index of first box in “originate from applic” queue : %% 15
Index of first box in “setcall from applic” queue : %% 16
Index of first box in “answers from applic” queue : %% 17

1. The application ID.

2. The number of frames to be managed simultaneously in the device instance.

3. The number of Tx retries.

4. Timeout in seconds between TX retries.

5. The time in seconds until the system discards the MDLC frames not solicited by the Application layer
(Ladder or “C” application)

6. Instance internal signals.

7. Whether the instance functions with task.

8. Mark if queues should be cleared.

9. Heap key used for transmission.

10. The next index of free boxes.

11. The next index of frames awaiting answer.

12. The next index of slave answer.

13. The next index of incoming frames.

14. The next index of incoming “originate” frames.

15. The next index of outbound “originate” frames.

16. The next index of broadcast frames to be issued.

17. The next index of answer frames to be issued.

52
 Software Diagnostics Output

## 201 LEVEL = 1
Boxes_nr : %% 1
Boxes in free queue : %% 2
Boxes in wait_for_outside_answr queue : %% 3
Boxes in outside_answrs queue : %% 4
Boxes in requests_from_applic queue : %% 5
Boxes in wait_for_applic_answr queue : %% 6
Boxes in originate queue : %% 7
Boxes in setcall queue : %% 8
Boxes in answer queue : %% 9

1. Total number of boxes to be handled by this instance. Each box handles one MDLC frame.

2. Current number of free boxes.

3. Current number of boxes waiting for answer.

4. Current number of boxes that are slave-answers.

5. Current number of frame boxes that arrived.

6. Number of originate boxes that arrived.

7. Number of originate boxes to be sent.

8. Number of broadcast boxes to be sent.

9. Number of answer boxes to be sent.

## 202 LEVEL = 2
“waiting for outside answer queue”
------------------------------------------
buf site port link retries ret_time indx p_indx _indx q_nr
---------------------------------------------------------------------
%% %% %% %% %% %% %% %% %% %%
1 2 3 4 5 6 7 8 9 10

1. Frame address.

2. Destination site ID.

3. Destination port ID.

4. Destination link ID.

5. Number of retries left.

6. Amount of time left until the next retry.

7. Box index.

8. Previous box index.

9. Next box index.

10. The internal queue ID.

53
 Software Diagnostics Output

## 203 LEVEL = 3
“outside answers queue”
-------------------------------
buf site port link retries ret_time indx p_indx _indx q_nr
---------------------------------------------------------------------
%% %% %% %% %% %% %% %% %% %%
1 2 3 4 5 6 7 8 9 10

See #202 above.

## 204 LEVEL = 4
“requests from application queue”
-----------------------------------------
buf site port link retries ret_time indx p_indx _indx q_nr
---------------------------------------------------------------------
%% %% %% %% %% %% %% %% %% %%
1 2 3 4 5 6 7 8 9 10

See #202 above.

## 205 LEVEL = 5
“waiting for application queue”
--------------------------------------
buf site port link retries ret_time indx p_indx _indx q_nr
---------------------------------------------------------------------
%% %% %% %% %% %% %% %% %% %%
1 2 3 4 5 6 7 8 9 10

## 206 LEVEL = 6
“originate queue”
---------------------
buf site port link retries ret_time indx p_indx _indx q_nr
---------------------------------------------------------------------
%% %% %% %% %% %% %% %% %% %%
1 2 3 4 5 6 7 8 9 10

## 207 LEVEL = 7
“setcall queue”
------------------
buf site port link retries ret_time indx p_indx _indx q_nr
---------------------------------------------------------------------
%% %% %% %% %% %% %% %% %% %%
1 2 3 4 5 6 7 8 9 10

See #202 above.

## 208 LEVEL = 8
“answers queue”
--------------------
buf site port link retries ret_time indx p_indx _indx q_nr

54
 Software Diagnostics Output

---------------------------------------------------------------------
%% %% %% %% %% %% %% %% %% %%
1 2 3 4 5 6 7 8 9 10

See #202 above.

## 209 LEVEL = 9
“free queue”
---------------
buf site port link retries ret_time indx p_indx _indx q_nr
---------------------------------------------------------------------
%% %% %% %% %% %% %% %% %% %%
1 2 3 4 5 6 7 8 9 10

See #202 above.

## 210 LEVEL = 10, 11

# of transmitted frames as originate : %%
# of transmitted frames as groupcall : %%
# of transmitted frames as answer : %%
# of transmitted frames as message : %%
# of re-transmitted frames originate : %%
# of received frames as originate : %%
# of received frames as groupcall : %%
# of received frames as answer : %%
# of received frames as message : %%
# of received frames (with error) : %%

See Reading Diagnostics Information above.

## 211 LEVEL = 12, 13

# Is RTU secured? : %%1
# Security policy password length : %%2
# of successfully transmitted secured frames : %%3
# of non-successful transmitted secured frames: %%4
# of successfully received secured frames : %%5
# of non-successfull received secured frames : %%6

1. Does the RTU use MDLC authentication?

2. The password length embedded in the outbound frame's secured credentials.

3. The number of outbound frames with secured credentials transmitted successfully.

4. The number of outbound frames with secured credentials transmitted unsuccessfully.

5. The number of inbound frames with secured credentials received and authenticated successfully.

6. The number of inbound frames with secured credentials received and authenticated unsuccessfully.

Note: Level 12 displays the values and resets the last 4 rows of this diagnostic.

55
 Software Diagnostics Output

## 212 LEVEL = 12, 13

Incoming authentication requests message queue information:

The authentication queue structure administrated by VxWorks for the MiniSession frames waiting in the
authentication queue.

##213 LEVEL = 255

Level 0 - Device key info
Level 1 - Boxes data
Level 2 - “Waiting for outside answer queue"
Level 3 - “Outside answers queue”
Level 4 - “Requests from application queue”
Level 5 - “Waiting for application queue”
Level 6 - “Originate queue”
Level 7 - “Setcall queue”
Level 8 - “Answers queue”
Level 9 - “Free queue”
levels 10/11- Transmit / receive statistics
levels 12/13- Authentication & Authorization data
Level 14 - Authentication & Authorization message queue information
Level 255 - Diagnostics information

This lists all diagnostics provided for the device at all its supported levels.

GAPRATIO (GPRTIO)

## 220 LEVEL = 0
The main process CPU usage in percent : %% 1
The other system tasks usage in percent : %% 2
The main process flag (hplcin) : %% 3
The main process key : %% 4

1. The percent of the CPU reserved for the ladder application and the tasks above it ( the 10ms and the
Rxlink tasks).
2. The percent of the CPU reserved for the rest of the tasks under the ladder application.
3. A flag for three different states:
a. Whether the ladder application is running at the moment.
b. Whether the ladder application is not running at the moment.
c. Whether the ladder application has been running for 1.2 seconds continuously.
4. The main process key.

56
 Software Diagnostics Output

HDLC/RADIO (RAD1P, RAD2P,...)

## 240 LEVEL = 0
HDLC hardware/software brief status :-
-------------------------------------

HDLC-logical software key (DEV_KEY) : %%1

Communication port (HDLC_PORT) : %%-> %%2
Reception lock (RXBD_LOCK) : %%3
Transmission lock (TXBD_LOCK) : %%4
Reception bd head index (RXBD_HEAD) : %%5
Reception current bd index (CUR_RX) : %%6
Transmission current bd index (CUR_TX) : %%7
Transmission bd tail (TXBD_TAIL) : %%8
Communication signals (HDLC_SIGNAL): %%9

Communication buffers (HDLC_TYPE) : %% %%10

Rx buffer descriptors base : %%11

Tx buffer descriptors base : %%12
Rx current buffer descriptors address : %%13
Tx current buffer descriptors address : %%14

Current reception empty buffers : %%15

Current reception ready buffers : %%16
Current transmission empty buffers : %%17
Current transmission ready buffers : %%18

1. Device key address.

2. The port number.
3. Semaphore of the reception function.
4. Semaphore of the transmission function.
5. Offset in RX_QUEUE (descriptors) for the entry of the new frame that has been received in port.
6. Offset in RX_QUEUE for moving the next frame to upper layers.
7. Offset in TX_QUEUE for moving a new frame to transmission, by upper layers.
8. Offset in TX_QUEUE from where this device takes the next frame for transmission.
9. MTE signal of events that took place.
10. Whether the frame is formatted/unformatted.
11. The base of the receive buffer descriptor.
12. The base of the transmit buffer descriptor.
13. The address of the current receive buffer descriptor.
14. The address of the current transmit buffer descriptor.
15. The number of empty frames ready to be received.
16. The number of frames received.
17. The number of frames transmitted.

57
 Software Diagnostics Output

18. The number of empty frames directed to transmission.

58
 Software Diagnostics Output

## 241 LEVEL = 1
HDLC hardware control and status :-
----------------------------------

HDLC-Physical SCC software key (DATA): %%1

HDLC-Physical SCC registers address : %%2
HDLC-Physical SCC parameters address : %%3
HDLC-Physical SCC protocol params addr: %%4

Baud rate generator in use : %%5

Clock control register (CMXSCR): %%6
Baud rate generator value (BRGC) : %%7

SCC registers:8
GSMR_L : %%
GSMR_H : %%
PSMR : %%
TODR : %%
DSR : %%
SCCE : %%
SCCM : %%
SCCS : %%

SCC parameters:9
RBASE : %%
TBASE : %%
RFCR : %%
TFCR : %%
MRBLR : %%
RSTATE : %%
RPTR : %%
RBPTR : %%
RCOUNT : %%
RTEMP : %%
TSTATE : %%
TPTR : %%
TBPTR : %%
TCOUNT : %%
TTEMP : %%
RCRC : %%
TCRC : %%

SCC HDLC protocol parameters:10

C_MASK : %%
C_PRES : %%
DISFC : %%
CRCEC : %%
ABTSC : %%
NMARC : %%
RETRC : %%
MFLR : %%
MAX_CNT : %%
RFTHR : %%
RFCNT : %%
HMASK : %%
HADDR[0] : %%
HADDR[1] : %%
HADDR[2] : %%
HADDR[3] : %%

59
 Software Diagnostics Output

TMP : %%
TMP_MB : %%

FPGA communication registers:11

General purpose register 1 : %% %%
General purpose register 2 : %% %%
General purpose register 3 : %% %%
General purpose register 4 : %% %%
General purpose register 5

1. Device key address.

2. Address of HW registers.

3. Address of HW parameters.

4. Address of protocol parameters

5. Whether a baud rate generator is in use.

6. Clock control register address.

7. Value of the baud rate generator.

8. The SCC registers.

9. The SCC parameters.

10. The SCC HDLC protocols parameters.

11. The FPGA communication registers.

60
 Software Diagnostics Output

## 242 LEVEL = 2
HDLC buffers descriptors information :-
--------------------------------------

Status Len Buffer

Receive buffer descriptor 0 (RXBD0): %% %% %%1
Receive buffer descriptor 1 (RXBD1): %% %% %%2
Receive buffer descriptor 2 (RXBD2): %% %% %%3
Receive buffer descriptor 3 (RXBD3): %% %% %%4
Receive buffer descriptor 4 (RXBD4): %% %% %%5
Receive buffer descriptor 5 (RXBD5): %% %% %%6
Receive buffer descriptor 6 (RXBD6): %% %% %%7
Receive buffer descriptor 7 (RXBD7): %% %% %%8

Transmit buffer descriptor 0 (TXBD0): %% %% %%9

Transmit buffer descriptor 1 (TXBD1): %% %% %%10
Transmit buffer descriptor 2 (TXBD2): %% %% %%11
Transmit buffer descriptor 3 (TXBD3): %% %% %%12
Transmit buffer descriptor 4 (TXBD4): %% %% %%13
Transmit buffer descriptor 5 (TXBD5): %% %% %%14
Transmit buffer descriptor 6 (TXBD6): %% %% %%15
Transmit buffer descriptor 7 (TXBD7): %% %% %%16

1. Address of frame in descriptor RX 0.

2. Address of frame in descriptor RX 1.

3. Address of frame in descriptor RX 2.

4. Address of frame in descriptor RX 3.

5. Address of frame in descriptor RX 4.

6. Address of frame in descriptor RX 5.

7. Address of frame in descriptor RX 6.

8. Address of frame in descriptor RX 7.

9. Address of frame for transmission in descriptor 0.

10. Address of frame for transmission in descriptor 1.

11. Address of frame for transmission in descriptor 2.

12. Address of frame for transmission in descriptor 3.

13. Address of frame for transmission in descriptor 4.

14. Address of frame for transmission in descriptor 5.

15. Address of frame for transmission in descriptor 6.

16. Address of frame for transmission in descriptor 7.

61
 Software Diagnostics Output

## 243 LEVEL = 3
HDLC-Logical device key info :-
------------------------------------
HDLC-logical software key (DATA) : %%1
Current mode parameters (MODE) : %%2
Current rate parameters (RATE) : %%3
Current sync parameters (SYNC) : %%4
Address mask parameters (MASK) : %%5
Address data parameters (ADRS) : %%6
HDLC-physical SCC device key address : %%7
HDLC-physical SCC pin table address : %%8
Current channel name (CHAN) : %%9
Current channel data (CHAN_DATA) : %%10
Current channel code (CHAN_CODE) : %%11
Current heap data (HEAP_DATA) : %%12
Communication port (HDLC_PORT) : %%13
Communication type (HDLC_TYPE) : %%14
Max tx empty wait : %%15
Is RTS in auto mode (RTS_MODE) : %%16
Is CTS in auto mode (CTS_AUTO) : %%17
Is CD ignored (IGNORE_CD) : %%18
Sync delay (SYNC_DELAY) : %%19
CRC size (CRC_SIZE) : %%20
Number of flags (NUM_OF_FLAGS): %%21
Is driver alloated : %%22
Number of Tx descriptors (TX_DESC_SIZE): %%23
Number of Rx descriptors (RX_DESC_SIZE): %%24
Is port used for MDLC ? (MDLC_PORT) : %%25
Is_snooping_enabled? : %%26
Reception data lock (RXBD_LOCK) : %%27
Transmission data lock (TXBD_LOCK) : %%28
Reception next free (RXBD_FREE) : %%29
Reception data header(RXBD_HEAD) : %%30
Transmission data tail (TXBD_TAIL) : %%31
Communication signals (HDLC_SIGNAL) : %%32
Communication time lock (TIME_LOCK) : %%33
Communication time data (TIME_DATA) : %%34
Communication status (NOISY) : %%35
(QUIET) : %%36
Communication preset/timers (GRANT) : %% %%37
(QUIET) : %% %%38

1. Logical device key address.

2. Working mode of the channel (synchronous, asynchronous, DTE, DCE).

3. Communication baud rate.

4. Not relevant.

5. Not relevant.

6. The addresses to which this site will respond through this port.

7. SCC device key address.

8. SCC pin table address.

62
 Software Diagnostics Output

9. The channel access name.

10. The channel access device key.

11. Channel access pin table.

12. The heap pin table.

13. The Port number.

14. Whether the frame is formatted or unformatted.

15. When all transmission buffers are full, the maximum time to wait for at least one transmission buffer
to become empty and available in order to transmit the next frame. If no buffer is emptied and the
transmission is not completed within that time, the transmission is considered as failed.

16. Is RTS in auto mode?

17. Is CTS in auto mode?

18. Is CD in auto mode?

19. The sync delay.

20. The size of the CRC.

21. The number of flags.

22. Is a driver allocated?

23. Number of Tx descriptors.

24. Number of Rx descriptors.

25. Is port used for MDLC?

26. Is snooping enabled?

27. Semaphore of the reception function.

28. Semaphore of the transmission function.

29. Offset in Rx descriptors to the next free descriptor.

30. Offset for Rx descriptors for receiving frame.

31. Offset for Tx descriptors for transmitting frame.

32. MTE signal of conditions that were met.

33. Not in use.

34. Coded time stamp of last received frame (in ticks).

35. Current counter of noise.

36. Current counter of quiet.

63
 Software Diagnostics Output

37. GRANT-TIME for channel access: The time the site will wait to obtain a transmission channel until it
decides that a channel is not available.

38. QUIET-TIME after transmission: The time to wait before a retry.

## 244 LEVEL = 4
HDLC-physical device key info :-
--------------------------------------
CPM base address (pIMMR) : %%
SCC registers address (scc_regs) : %%
SCC parameters (scc_params) : %%
SCC interrupt number (INUM_value) : %%
Is snooping enabled ? : %%
Command register sub block (scc_sub_block): %%
SCC in use (hdlc_phys_scc): %%
Port in use (port_number) : %%
Tx clock direction (txclock_dir) : %%
Rx clock direction (rxclock_dir) : %%
Receive buffer descriptor base (p_rbase) : %%
Transmit buffer descriptor base (p_tbase) : %%
Baud rate generator number (brg_in_use) : %%
Address of Baud rate generator (p_brg_in_use) : %%
Baud rate generator frequency (brg_freq) : %%
Is RTS in auto mode (rts_auto) : %%
Is CTS in auto mode (cts_auto) : %%
Is CD ignored (ignore_cd) : %%
Is Modem enabled? (modem_enable) : %%
Modem type (modem_type) : %%
Radio interface board value (radio_int_brd): %%

HDLC-physical device key info.

## 246 LEVEL = 10, 11

HDLC physical error counters info :-
--------------------------------------
Discard frame counter (DISFC) : %% 1
CRC error counter (CRCEC) : %% 2
Abort sequence counter (ABTSC) : %% 3
Non matching address counter (NMARK) : %% 4
Frame retransmit counter (RETRC) : %% 5

1. The number of discarded frames.

2. The number of CRC-error frames.

3. The number of abort-sequence frames.

4. The number of nonmatching address frames.

5. The number of retransmitted frames.

64
 Software Diagnostics Output

## 247 LEVEL = 255

HDLC list of diagnostic levels :-
--------------------------------------
0 - Get HDLC hardware/software brief status
1 - Get HDLC hardware control and status
2 - Get HDLC buffers descriptors information
3 - Get HDLC-Logical device key info
4 - Get HDLC-physical device key info
5 - Get Authentication info
10 - Clear HDLC physical error counters
11 - Get HDLC physical error counters info

UART

## 280
UART hardware/software last status :-
Internal software data (key) (DATA) : %% 1
Internal hardware registers (IREG) : %% 2
Internal hardware parameters (IRAM) : %% 3
Current channel port (UART_PORT) : %% 4
Reception data lock (RXBD_LOCK) : %% 5
Transmission data lock (TXBD_LOCK) : %% 6
Reception data header (RXBD_HEAD) : %% 7
Reception data tail (RXBD_TAIL) : %% 8
Transmission data header (TXBD_HEAD) : %% 9
Transmission data tail (TXBD_TAIL) : %% 10
Communication signals (UART_SIGNAL): %% 11
Communication buffers (UART_TYPE) : %% 12
Idle characters counter (IDLC) : %% 13
Parity error counter (PAREC) : %% 14
Framing error counter (FRMEC) : %% 15
Noise error counter (NOSEC) : %% 16
Break error counter (BRKEC) : %% 17
Current reception empty buffer : %% 18
Current reception ready buffers : %% 19
Current transmission ready buffers : %% 20
Current transmission empty buffers : %% 21

1. Device key address.

2. H-W registers address.

3. H-W parameters address.

4. The Port number.

5. Semaphore of the reception function.

6. Semaphore of the transmission function.

7. Offset for Rx descriptors for receiving frame.

8. Offset in RX_QUEUE for moving the next frame to upper layers.

65
 Software Diagnostics Output

9. Offset in TX_QUEUE for moving a new frame to transmission, by upper layers.

10. Offset in TX_QUEUE from where this device takes the next frame for transmission.

11. MTE signal of events that took place.

12. Whether the frame is formatted/unformatted.

13. The actual counter that counts the number of idles since the last character was received. For example,
the time that a character takes to arrive (corresponds to idle) at 9600 baud is 1 msec.

14. The number of times the parity error occurred during the reception of a single byte.

15. The number of times the framing error occurred during the reception of a single byte.

16. The number of times the noise error occurred during the reception of a single byte.

17. The number of times a break signal (end of reception) was received at the port.

18. The number of empty frames ready to be received.

19. The number of frames received.

20. The number of frames transmitted.

21. The number of empty frames directed to transmission.

## 281
UART hardware control and status :-
Internal software data (key) (DATA) : %% 1
Internal hardware registers (IREG) : %% 2
Internal hardware parameters (IRAM) : %% 3
Scc configuration register (SCON) : %% 4
Scc mode register (SCM) : %% 5
Scc data sync. register (DSR) : %% 6
Scc event register (SCCE) : %% 7
Scc mask register (SCCM) : %% 8
Scc status register (SCCS) : %% 9
Idle characters maximum (MAX_IDL) : %% 10
Idle characters counter (IDLC) : %% 11
Break characters register (BRKCR) : %% 12
Parity error counter (PAREC) : %% 13
Framing error counter (FRMEC) : %% 14
Noise error counter (NOSEC) : %% 15
Break error counter (BRKEC) : %% 16
User defined UART addresses (UADDRX) : %% %% 17
Control character register (RCCR) : %% 18
Control character table (CHARACTERX) : %% %% %% %% 19
: %% %% %% %%

1. Device key address.

2. H-W registers address.

3. H-W parameters address.

4. Determines the clock direction (Rx or Tx) and the baud rate
66
 Software Diagnostics Output

5. Determines the work mode — HDLC or UART.

6. Determines the HDLC flags.

7. The events that generate the interrupt.

8. Mask to block the interrupt.

9. The CM (Channel Monitor) and TD (Tone Detect) statuses.

10. How many idles to wait before declaring that the transmission has ended.

11. The actual counter that counts the number of idles since the last character was received. For example,
the time that a character takes to arrive (corresponds to idle) at 9600 baud is 1 msec.

12. Break register.

13. The number of times the parity error occurred during the reception of a single byte.

14. The number of times the framing error occurred during the reception of a single byte.

15. The number of times the noise error occurred during the reception of a single byte.

16. The number of times a break signal (end of reception) was received at the port.

17. Not in use.

18. Control character register.

19. The characters that are used to close a frame.

67
 Software Diagnostics Output

## 282
UART hardware data buffers status :-
Internal software data (key) (DATA) : %% 1
Internal hardware registers (IREG) : %% 2
Internal hardware parameters (IRAM) : %% 3
Receive buffer descriptor 0 (RXBD0) : %% %% %% %% 4
Receive buffer descriptor 1 (RXBD1) : %% %% %% %% 5
Receive buffer descriptor 2 (RXBD2) : %% %% %% %% 6
Receive buffer descriptor 3 (RXBD3) : %% %% %% %% 7
Receive buffer descriptor 4 (RXBD4) : %% %% %% %% 8
Receive buffer descriptor 5 (RXBD5) : %% %% %% %% 9
Receive buffer descriptor 6 (RXBD6) : %% %% %% %% 10
Receive buffer descriptor 7 (RXBD7) : %% %% %% %% 11
Transmit buffer descriptor 0 (TXBD0) : %% %% %% %% 12
Transmit buffer descriptor 1 (TXBD1) : %% %% %% %% 13
Transmit buffer descriptor 2 (TXBD2) : %% %% %% %% 14
Transmit buffer descriptor 3 (TXBD3) : %% %% %% %% 15
Transmit buffer descriptor 4 (TXBD4) : %% %% %% %% 16
Transmit buffer descriptor 5 (TXBD5) : %% %% %% %% 17
Transmit buffer descriptor 6 (TXBD6) : %% %% %% %% 18
Transmit buffer descriptor 7 (TXBD7) : %% %% %% %% 19
Rxd/Txd function code (R/TFCR): %% 20
Maximum receive buffer length (MRBLR) : %% 21
Current receive buffer status : %% 22
Current receive buffer offset (RBD#) : %% 23
Current receive data pointer : %% %% 24
Current receive byte counter : %% 24
Current receive temp memory : %% 24
Current transmit buffer status : %% 25
Current transmit buffer offset (TBD#) : %% 26
Current transmit data pointer : %% %% 27
Current transmit byte counter : %% 27
Current transmit temp memory : %% 27

1. Device key address.

2. H-W registers address.

3. H-W parameters address.

4. Address of frame in descriptor RX 0.

5. Address of frame in descriptor RX 1.

6. Address of frame in descriptor RX 2.

7. Address of frame in descriptor RX 3.

8. Address of frame in descriptor RX 4.

9. Address of frame in descriptor RX 5.

10. Address of frame in descriptor RX 6.

11. Address of frame in descriptor RX 7.

12. Address of frame for transmission in descriptor 0.

68
 Software Diagnostics Output

13. Address of frame for transmission in descriptor 1.

14. Address of frame for transmission in descriptor 2.

15. Address of frame for transmission in descriptor 3.

16. Address of frame for transmission in descriptor 4.

17. Address of frame for transmission in descriptor 5.

18. Address of frame for transmission in descriptor 6.

19. Address of frame for transmission in descriptor 7.

20. Rx and Tx function code.

21. Maximum received frame length.

22. The reception status of the last received frame.

23. The offset value in the descriptors of the last received frame.

24. Internal variable of 68302.

25. The status of the last transmitted frame.

26. The offset value in the descriptors of the last transmitted frame.

27. Internal variable of 68302.

69
 Software Diagnostics Output

## 283
UART software control and status :-
Internal software data (key) (DATA) : %% 1
Internal hardware registers (IREG) : %% 2
Internal hardware parameters (IRAM) : %% 3
Current mode parameters (MODE_BACKUP): %% 4
Current rate parameters (RATE_BACKUP): %% 5
Current sync parameters (SYNC_BACKUP): %% 6
Address mask parameters (MASK_BACKUP): %% 7
Address data parameters (ADRS_BACKUP): %% %% %% %% 8
Current channel name (CHAN_BACKUP): %% 9
Current channel data (CHAN_DATA) : %% 10
Current channel code (CHAN_CODE) : %% 11
Current heap name (HEAP_BACKUP): %% 12
Current heap name (HEAP_DATA) : %% 13
Current heap data (HEAP_CODE) : %% 14
Current channel port (UART_PORT) : %% 15
Reception data lock (RXBD_LOCK) : %% 16
Transmission data lock (TXBD_LOCK) : %% 17
Reception next free (RXBD_FREE) : %% 18
Transmission next free (TXBD_FREE) : %% 19
Reception data header (RXBD_HEAD) : %% 20
Transmission data tail (TXBD_TAIL) : %% 21
Communication signals (UART_SIGNAL): %% 22
Communication buffer (UART_TYPE) : %% 23
Communication HDLC lock (UART_LOCK) : %% 24
Communication time lock (TIME_LOCK) : %% 25
Communication time data (TIME_DATA) : %% 26
Communication status (NOISY) : %% 27
(QUIET) : %% 28
Communication preset/timers (GRANT) : %% %% 29
(QUIET) : %% %% 30

1. Device key address.

2. H-W registers address.

3. H-W parameters address.

4. Working mode of the channel (synchronous, asynchronous, DTE, DCE).

5. Communication baud rate.

6. Not relevant.

7. Not relevant.

8. The addresses to which this site will respond through this port.

9. The channel access name.

10. The channel access device key.

11. Channel access pin table.

12. The heap name (HP_F_RX).

13. The heap device key.

70
 Software Diagnostics Output

14. The heap pin table.

15. The Port number.

16. Semaphore of the reception function.

17. Semaphore of the transmission function.

18. Offset in Rx descriptors to the next free descriptor.

19. Offset in Tx descriptors to the next free descriptor.

20. Offset for Rx descriptors for receiving frame.

21. Offset for Tx descriptors for transmitting frame.

22. MTE signal of conditions that were met.

23. Whether the frame is formatted or unformatted.

24. Device semaphore.

25. Not in use.

26. Coded time stamp of last received frame (in ticks).

27. Current counter of noise.

28. Current counter of quiet.

29. GRANT-TIME for channel access: The time the site will wait to obtain a transmission channel until it
decides that a channel is not available.

30. QUIET-TIME after transmission: The time to wait before a retry.

71
 Software Diagnostics Output

## 285
UART hardware/software last status :-
Internal software data (key) (DATA) : %% 1
Internal hardware registers (IREG) : %% 2
Internal hardware parameters (IRAM) : %% 3
Current channel port (UART_PORT) : %% 4
Reception data lock (RXBD_LOCK) : %% 5
Transmission data lock (TXBD_LOCK) : %% 6
Reception data header (RXBD_HEAD) : %% 7
Reception data tail (RXBD_TAIL) : %% 8
Transmission data header (TXBD_HEAD) : %% 9
Transmission data tail (TXBD_TAIL) : %% 10
Communication signals (UART_SIGNAL): %% 11
Communication buffers (UART_TYPE) : %% %% 12
Idle characters counter (IDLC) : %% 13
Parity error counter (PAREC) : %% 14
Framing error counter (FRMEC) : %% 15
Noise error counter (NOSEC) : %% 16
Break error counter (BRKEC) : %% 17
Current reception empty buffers : %% 18
Current reception ready buffers : %% 19
Current transmission ready buffers : %% 20
Current transmission empty buffers : %% 21

1. Device key address.

2. H-W registers address.

3. H-W parameters address.

4. The Port number.

5. Semaphore of the reception function.

6. Semaphore of the transmission function.

7. Offset for Rx descriptors for receiving frame.

8. Offset in RX_QUEUE for moving the next frame to upper layers.

9. Offset in TX_QUEUE for moving a new frame to transmission, by upper layers.

10. Offset in TX_QUEUE from where this device takes the next frame for transmission.

11. MTE signal of events that took place.

12. Whether the frame is formatted/unformatted.

13. The actual counter that counts the number of idles since the last character was received. For example,
the time that a character takes to arrive (corresponds to idle) at 9600 baud is 1 msec.

14. The number of times the parity error occurred during the reception of a single byte.

15. The number of times the framing error occurred during the reception of a single byte.

16. The number of times the noise error occurred during the reception of a single byte.

17. The number of times a break signal (end of reception) was received at the port.

72
 Software Diagnostics Output

18. The number of empty frames ready to be received.

19. The number of frames received.

20. The number of frames transmitted.

21. The number of empty frames directed to transmission.

## 286
UART hardware control and status :-
Internal software data (key) (DATA) : %% 1
Internal hardware registers (IREG) : %% 2
Internal hardware parameters (IRAM) : %% 3
Scc configuration register (SCON) : %% 4
Scc mode register (SCM) : %% 5
Scc data sync. register (DSR) : %% 6
Scc event register (SCCE) : %% 7
Reserved register (RES2) : %% 8
Scc mask register (SCCM) : %% 9
Reserved register (RES3) : %% 10
Scc status register (SCCS) : %% 11
Idle characters maximum (MAX_IDL) : %% 12
Idle characters counter (IDLC) : %% 13
Break characters register (BRKCR) : %% 14
Parity error counter (PAREC) : %% 15
Framing error counter (FRMEC) : %% 16
Noise error counter (NOSEC) : %% 17
Break error counter (BRKEC) : %% 18
User defined UART addresses (UADDRX) : %% %% 19
Control character register (RCCR) : %% 20
Control character table (CHARACTERX) : %% %% %% %% 21
: %% %% %% %%

1. Device key address.

2. H-W registers address.

3. H-W parameters address.

4. Determines the clock direction (Rx or Tx) and the baud rate

5. Determines the work mode — HDLC or UART.

6. Determines the HDLC flags.

7. The events that generate the interrupt.

8. Reserved.

9. Mask to block the interrupt.

10. Reserved.

11. The CM (Channel Monitor) and TD (Tone Detect) statuses.

12. How many idles to wait before declaring that the transmission has ended.

73
 Software Diagnostics Output

13. The actual counter that counts the number of idles since the last character was received. For example,
the time that a character takes to arrive (corresponds to idle) at 9600 baud is 1 msec.

14. Break register.

15. The number of times the parity error occurred during the reception of a single byte.

16. The number of times the framing error occurred during the reception of a single byte.

17. The number of times the noise error occurred during the reception of a single byte.

18. The number of times a break signal (end of reception) was received at the port.

19. Not in use.

20. Control character register

21. The characters that are used to close a frame.

## 287
UART hardware data buffers status :-
Internal software data (key) (DATA) : %% 1
Internal hardware registers (IREG) : %% 2
Internal hardware parameters (IRAM) : %% 3
Receive buffer descriptor 0 (RXBD0) : %% %% %% %% 4
Receive buffer descriptor 1 (RXBD1) : %% %% %% %% 5
Receive buffer descriptor 2 (RXBD2) : %% %% %% %% 6
Receive buffer descriptor 3 (RXBD3) : %% %% %% %% 7
Receive buffer descriptor 4 (RXBD4) : %% %% %% %% 8
Receive buffer descriptor 5 (RXBD5) : %% %% %% %% 9
Receive buffer descriptor 6 (RXBD6) : %% %% %% %% 10
Receive buffer descriptor 7 (RXBD7) : %% %% %% %% 11
Transmit buffer descriptor 0 (TXBD0) : %% %% %% %% 12
Transmit buffer descriptor 1 (TXBD1) : %% %% %% %% 13
Transmit buffer descriptor 2 (TXBD2) : %% %% %% %% 14
Transmit buffer descriptor 3 (TXBD3) : %% %% %% %% 15
Transmit buffer descriptor 4 (TXBD4) : %% %% %% %% 16
Transmit buffer descriptor 5 (TXBD5) : %% %% %% %% 17
Transmit buffer descriptor 6 (TXBD6) : %% %% %% %% 18
Transmit buffer descriptor 7 (TXBD7) : %% %% %% %% 19
Rxd/Txd function code (R/TFCR): %% 20
Maximum receive buffer length (MRBLR) : %% 21
Current receive buffer status : %% 22
Current receive buffer offset (RBD#) : %% 23
Current receive data pointer : %% %% 24
Current receive byte counter : %% 24
Current receive temp memory : %% 24
Current transmit buffer status : %% 25
Current transmit buffer offset (TBD#) : %% 26
Current transmit data pointer : %% %% 27
Current transmit byte counter : %% 27
Current transmit temp memory : %% 27

1. Device key address.

2. H-W registers address.

74
 Software Diagnostics Output

3. H-W parameters address.

4. Address of frame in descriptor RX 0.

5. Address of frame in descriptor RX 1.

6. Address of frame in descriptor RX 2.

7. Address of frame in descriptor RX 3.

8. Address of frame in descriptor RX 4.

9. Address of frame in descriptor RX 5.

10. Address of frame in descriptor RX 6.

11. Address of frame in descriptor RX 7.

12. Address of frame for transmission in descriptor 0.

13. Address of frame for transmission in descriptor 1.

14. Address of frame for transmission in descriptor 2.

15. Address of frame for transmission in descriptor 3.

16. Address of frame for transmission in descriptor 4.

17. Address of frame for transmission in descriptor 5.

18. Address of frame for transmission in descriptor 6.

19. Address of frame for transmission in descriptor 7.

20. Rx and Tx function code.

21. Maximum received frame length.

22. The reception status of the last received frame.

23. The offset value in the descriptors of the last received frame.

24. Internal variable of 68302.

25. The status of the last transmitted frame.

26. The offset value in the descriptors of the last transmitted frame.

27. Internal variable of 68302.

75
 Software Diagnostics Output

## 288
UART software control and status :-
Internal software data (key) (DATA) : %% 1
Internal hardware registers (IREG) : %% 2
Internal hardware parameters (IRAM) : %% 3
Current mode parameters (MODE_BACKUP): %% 4
Current rate parameters (RATE_BACKUP): %% 5
Current sync parameters (SYNC_BACKUP): %% 6
Address mask parameters (MASK_BACKUP): %% 7
Address data parameters (ADRS_BACKUP): %% %% %% %% 8
Current heap name (HEAP_KEY) : %% 9
Current channel port (DART_PORT) : %% 10
Reception data lock (RXBD_LOCK) : %% 11
Transmission data lock (TXBD_LOCK) : %% 12
Reception next free (RXBD_FREE) : %% 13
Transmission next free (TXBD_FREE) : %% 14
Reception data header (RXBD_HEAD) : %% 15
Transmission data tail (TXBD_TAIL) : %% 16
Communication signals (UART_SIGNAL): %% 17
Communication buffer (DART_TYPE) : %% %% 18
Communication UART lock (DART_LOCK) : %% 19
Communication time lock (TIME_LOCK) : %% 20
Communication time data (TIME_DATA) : %% 21
Communication status (NOISY) : %% 22
(QUIET) : %% 23
Communication preset/timers (GRANT) : %% %% 24
(QUIET) : %% %% 25
Incoming Call flag : %% 26
Second counter : %% 27

1. Device key address.

2. H-W registers address.

3. H-W parameters address.

4. Working mode of the channel (synchronous, asynchronous, DTE, DCE).

5. Communication baud rate.

6. Not relevant.

7. Not relevant.

8. The addresses to which this site will respond through this port.

9. The heap device key.

10. The Port number.

11. Semaphore of the reception function.

12. Semaphore of the transmission function.

13. Offset in Rx descriptors to the next free descriptor.

14. Offset in Tx descriptors to the next free descriptor.

76
 Software Diagnostics Output

15. Offset for Rx descriptors for receiving frame.

16. Offset for Tx descriptors for transmitting frame.

17. MTE signal of conditions that were met.

18. Whether the frame is formatted or unformatted.

19. Internal variable that represents the device status.

20. Not in use.

21. Coded time stamp of last received frame (in ticks).

22. Current counter of noise.

23. Current counter of quiet.

24. GRANT-TIME for channel access: The time the site will wait to obtain a transmission channel until it
decides that a channel is not available.

25. QUIET-TIME after transmission: The time to wait before a retry.

26. Internal device variable.

27. Internal device variable.

## 290
UART hardware/software last status :-
Parity error counter (PAREC) : %% 1
Framing error counter (FRMEC) : %% 2
Noise error counter (NOSEC) : %% 3
Break error counter (BRKEC) : %% 4

1. The number of times the parity error occurred during the reception of a single byte.

2. The number of times the framing error occurred during the reception of a single byte.

3. The number of times the noise error occurred during the reception of a single byte.

4. The number of times a break signal (end of reception) was received at the port.

## 291
UART hardware/software last status :-
Parity error counter (PAREC) : %% 1
Framing error counter (FRMEC) : %% 2
Noise error counter (NOSEC) : %% 3
Break error counter (BRKEC) : %% 4

1. The number of times the parity error occurred during the reception of a single byte.

2. The number of times the framing error occurred during the reception of a single byte.

3. The number of times the noise error occurred during the reception of a single byte.

77
 Software Diagnostics Output

4. The number of times a break signal (end of reception) was received at the port.

RADIO CHANNEL (RAD1C , RAD2C,…)

## 300 LEVEL = 0
Radio hardware/software last status :-
Internal software data (key) (DATA) : %% 1
Internal hardware registers (IREG) : %% 2
Internal hardware parameters (IRAM) : %% 3
Current channel port (CHAN_PORT) : %% 4
Channel status mode (CHAN_MODE) : %% 5
Channel driver lock (CHAN_LOCK) : %% 6
Channel signals (CHAN_SIGNAL): %% 7
Channel access type (CHAN_ACCESS): %%
Channel driver type (CHAN_TYPE) : %% 8
Channel control register (PBCNT) : %% 9
Channel direction register (PBDDR) : %% 10
Channel data register (PBDAT) : %% 11
Current reception empty buffers : %% 12
Current reception ready buffer : %% 13
Current transmission ready buffers : %% 14
Current transmission empty buffers : %% 15

1. Device-key address.

2. H-W registers address.

3. H-W parameters address.

4. Port number.

5. Configuration mode.

6. Channel access semaphore.

7. MTE signal on events that took place.

8. Whether FSK, DPSK or FSK.

9. Defines the functionality of port B in 68xxx (68000 family).

10. Determines whether the pin is for input or output.

11. Defines the value of the pin (previous parameter).

12. Number of empty Rx descriptors.

13. Number of busy Rx descriptors.

14. Number of busy Tx descriptors.

15. Number of empty Tx descriptors.

78
 Software Diagnostics Output

## 301
Radio hardware control and status :-
Internal software data (key) (DATA) : %% 1
Internal hardware registers (IREG) : %% 2
Internal hardware parameters (IRAM) : %% 3
Scc configuration register (SCON) : %% 4
Scc mode register (SCM) : %% 5
Scc data sync. register (DSR) : %% 6
Scc event register (SCCE) : %% 7
Scc mask register (SCCM) : %% 8
Scc status register (SCCS) : %% 9
Channel control register (PBCNT) : %% 10
Channel direction register (PRDDR) : %% 11
Channel data register (PBDAT) : %% 12

1. Device-key address.

2. H-W registers address.

3. H-W parameters address.

4. Determines the clock direction (Rx or Tx) and the baud rate

5. Determines the work mode — HDLC or UART.

6. Determines the HDLC flags.

7. The events that generate the interrupt.

8. Mask to block the interrupt.

9. The CM (Channel Monitor) and TD (Tone Detect) statuses.

10. Defines the functionality of port B in 68.

11. Determines whether the pin is for input or output.

12. Defines the value of the pin (previous parameter).

## 302 LEVEL = 2
Radio hardware data buffers status :-
Internal software data (key) (DATA) : %% 1
Internal hardware registers (IREG) : %% 2
Internal hardware parameters (IRAM) : %% 3
Receive buffer descriptor 0 (RXBD0) : %% %% %% %% 4
Receive buffer descriptor 1 (RXBD1) : %% %% %% %% 5
Receive buffer descriptor 2 (RXBD2) : %% %% %% %% 6
Receive buffer descriptor 3 (RXBD3) : %% %% %% %% 7
Receive buffer descriptor 4 (RXBD4) : %% %% %% %% 8
Receive buffer descriptor 5 (RXBD5) : %% %% %% %% 9
Receive buffer descriptor 6 (RXBD6) : %% %% %% %% 10
Receive buffer descriptor 7 (RXBD7) : %% %% %% %% 11
Transmit buffer descriptor 0 (TXBD0) : %% %% %% %% 12
Transmit buffer descriptor 1 (TXBD1) : %% %% %% %% 13
Transmit buffer descriptor 2 (TXBD2) : %% %% %% %% 14
Transmit buffer descriptor 3 (TXBD3) : %% %% %% %% 15
Transmit buffer descriptor 4 (TXBD4) : %% %% %% %% 16

79
 Software Diagnostics Output

Transmit buffer descriptor 5 (TXBD5) : %% %% %% %% 17

Transmit buffer descriptor 6 (TXBD6) : %% %% %% %% 18
Transmit buffer descriptor 7 (TXBD7) : %% %% %% %% 19
Rxd/Txd function code (R/TFCR): %% 20
Maximum receive buffer length (MRBLR) : %% 21
Current receive buffer status : %% 22
Current receive buffer offset (RBD#) : %% 23
Current receive data pointer : %% %% 24
Current receive byte counter : %% 24
Current receive temp memory : %% 24
Current transmit buffer status : %% 25
Current transmit buffer offset (TBD#) : %% 26
Current transmit data pointer : %% %% 27
Current transmit byte counter : %% 27
Current transmit temp memory : %% 27

1. Device-key address.

2. H-W registers address.

3. H-W parameters address.

4. Address of frame in descriptor RX 0.

5. Address of frame in descriptor RX 1.

6. Address of frame in descriptor RX 2.

7. Address of frame in descriptor RX 3.

8. Address of frame in descriptor RX 4.

9. Address of frame in descriptor RX 5.

10. Address of frame in descriptor RX 6.

11. Address of frame in descriptor RX 7.

12. Address of frame for transmission in descriptor 0.

13. Address of frame for transmission in descriptor 1.

14. Address of frame for transmission in descriptor 2.

15. Address of frame for transmission in descriptor 3.

16. Address of frame for transmission in descriptor 4.

17. Address of frame for transmission in descriptor 5.

18. Address of frame for transmission in descriptor 6.

19. Address of frame for transmission in descriptor 7.

20. Rx and Tx function code.

21. Maximum received frame length.

80
 Software Diagnostics Output

22. The reception status of the last received frame.

23. The offset value in the descriptors of the last received frame.

24. Internal variable of 68302.

25. The status of the last transmitted frame.

26. The offset value in the descriptors of the last transmitted frame.

27. Internal variable of 68302.

## 303 LEVEL = 3
Radio software control and status :-
Internal software data (key) (DATA) : %% 1
Internal hardware registers (IREG) : %% 2
Internal hardware parameters (IRAM) : %% 3
Current mode parameters (MODE_BACKUP) : %% 4
Current rate parameters (RATE_BACKUP) : %% 5
Current sync parameters (SYNC_BACKUP) : %% 6
Current channel port (CHAN_PORT) : %% 7
Channel status mode (CHAN_MODE) : %% %% 8
Channel driver lock (CHAN_LOCK) : %% 9
Channel signals (CHAN_SIGNAL) : %% 10
Channel access type (CHAN_ACCESS) : %%
Channel driver type (CHAN_TYPE) : %% 11
Channel addresses (CHAN/NEXT/MASK) : %% %% %% 12
Channel status (NOISY) : %% 13
(QUIET) : %%
Channel preset/timers (OVERRIDE) : %% %% 14
(RESOLUTE/QUIET) : %% %%
(SHUTUP) : %% %%
(GRANT) : %% %%
(WARMUP) : %% %%
(TRANSMIT) : %% %%
(HOLDUP) : %% %%
(RESPOND) : %% %%

1. Device-key address.

2. H-W registers address.

3. H-W parameters address.

4. Working mode of the channel (synchronous, asynchronous, DTE, DCE).

5. Communication baud rate.

6. Not relevant.

7. Port number.

8. Configuration mode.

9. Channel access semaphore.

10. MTE signal on events that took place.

81
 Software Diagnostics Output

11. Whether FSK, DPSK or FSK.

12. The address to which this site will respond through this port.

13. Actual channel access timers.

14. Preset timers for fields defined in the advanced parameters of Port 3.

TRUNK CHANNEL

## 320
Trunk radio hardware/software last status :-
Internal software data (key) (DATA) : %% 1
Internal hardware registers (IREG) : %% 2
Internal hardware parameters (IRAM) : %% 3
Current channel port (CHAN_PORT) : %% 4
Channel status mode (CHAN_MODE) : %% 5
Channel driver lock (CHAN_LOCK) : %% 6
Channel signals (CHAN_SIGNAL): %% 7
Channel access type (CHAN_ACCESS): %%
Channel driver type (CHAN_TYPE) : %% 8
Channel control register (PBCNT) : %% 9
Channel direction register (PBDDR) : %% 10
Channel data register (PBDAT) : %% 11
Current reception empty buffers : %% 12
Current reception ready buffers : %% 13
Current transmission ready buffers : %% 14
Current transmission empty buffers : %% 15

1. Device-key address.

2. H-W registers address.

3. H-W parameters address.

4. Port number.

5. Configuration mode.

6. Channel access semaphore.

7. MTE signal on events that took place.

8. Whether FSK, DPSK or FSK.

9. Defines the functionality of port B in 68.

10. Determines whether the pin is for input or output.

11. Defines the value of the pin (previous parameter).

12. Number of empty Rx descriptors.

13. Number of busy Rx descriptors.

82
 Software Diagnostics Output

14. Number of busy Tx descriptors.

15. Number of empty Tx descriptors.

## 321
Trunk radio hardware control and status :-
Internal software data (key) (DATA) : %% 1
Internal hardware registers (IREG) : %% 2
Internal hardware parameters (IRAM) : %% 3
Scc configuration register (SCON) : %% 4
Scc mode register (SCM) : %% 5
Scc data sync. register (DSR) : %% 6
Scc event register (SCCE) : %% 7
Scc mask register (SCCM) : %% 8
Scc status register (SCCS) : %% 9
Channel control register (PBCNT): %% 10
Channel direction register (PRDDR): %% 11
Channel data register (PBDAT): %% 12

1. Device-key address.

2. H-W registers address.

3. H-W parameters address.

4. Determines the clock direction (Rx or Tx) and the baud rate

5. Determines the work mode — HDLC or UART.

6. Determines the HDLC flags.

7. The events that generate the interrupt.

8. Mask to block the interrupt.

9. The CM (Channel Monitor) and TD (Tone Detect) statuses.

10. Defines the functionality of port B in 68.

11. Determines whether the pin is for input or output.

12. Defines the value of the pin (previous parameter).

## 322
Trunk radio hardware data buffers status :-
Internal software data (key) (DATA) : %% 1
Internal hardware registers (IREG) : %% 2
Internal hardware parameters (IRAM) : %% 3
Receive buffer descriptor 0 (RXBD0) : %% %% %% %% 4
Receive buffer descriptor 1 (RXBD1) : %% %% %% %% 5
Receive buffer descriptor 2 (RXBD2) : %% %% %% %% 6
Receive buffer descriptor 3 (RXBD3) : %% %% %% %% 7
Receive buffer descriptor 4 (RXBD4) : %% %% %% %% 8
Receive buffer descriptor 5 (RXBD5) : %% %% %% %% 9
Receive buffer descriptor 6 (RXBD6) : %% %% %% %% 10

83
 Software Diagnostics Output

Receive buffer descriptor 7 (RXBD7) : %% %% %% %% 11

Transmit buffer descriptor 0 (TXBD0) : %% %% %% %% 12
Transmit buffer descriptor 1 (TXBD1) : %% %% %% %% 13
Transmit buffer descriptor 2 (TXBD2) : %% %% %% %% 14
Transmit buffer descriptor 3 (TXBD3) : %% %% %% %% 15
Transmit buffer descriptor 4 (TXBD4) : %% %% %% %% 16
Transmit buffer descriptor 5 (TXBD5) : %% %% %% %% 17
Transmit buffer descriptor 6 (TXBD6) : %% %% %% %% 18
Transmit buffer descriptor 7 (TXBD7) : %% %% %% %% 19
Rxd/Txd function code (R/TFCR): %% 20
Maximum receive buffer length (MRBLR) : %% 21
Current receive buffer status : %% 22
Current receive buffer offset (RBD#) : %% 23
Current receive data pointer : %% %% 24
Current receive byte counter : %% 24
Current receive temp memory : %% 24
Current transmit buffer status : %% 25
Current transmit buffer offset (TBD#) : %% 26
Current transmit data pointer : %% %% 27
Current transmit byte counter : %% 27
Current transmit temp memory : %% 27

1. Device-key address.
2. H-W registers address.
3. H-W parameters address.
4. Address of frame in descriptor RX 0.
5. Address of frame in descriptor RX 1.
6. Address of frame in descriptor RX 2.
7. Address of frame in descriptor RX 3.
8. Address of frame in descriptor RX 4.
9. Address of frame in descriptor RX 5.
10. Address of frame in descriptor RX 6.
11. Address of frame in descriptor RX 7.
12. Address of frame for transmission in descriptor 0.
13. Address of frame for transmission in descriptor 1.
14. Address of frame for transmission in descriptor 2.
15. Address of frame for transmission in descriptor 3.
16. Address of frame for transmission in descriptor 4.
17. Address of frame for transmission in descriptor 5.
18. Address of frame for transmission in descriptor 6.
19. Address of frame for transmission in descriptor 7.
20. Rx and Tx function code.
21. Maximum received frame length.
22. The reception status of the last received frame.

84
 Software Diagnostics Output

23. The offset value in the descriptors of the last received frame.
24. Internal variable of 68302.
25. The status of the last transmitted frame.
26. The offset value in the descriptors of the last transmitted frame.
27. Internal variable of 68302.

## 323
Trunk radio software control and status :-
Internal software data (key) (DATA) : %% 1
Internal hardware registers (IREG) : %% 2
Internal hardware parameters (IRAM) : %% 3
Current mode parameters (MODE_BACKUP) : %% 4
Current rate parameters (RATE_BACKUP) : %% 5
Current sync parameters (SYNC_BACKUP) : %% 6
Current channel port (CHAN_PORT) : %% 7
Channel status mode (CHAN_MODE) : %% %% 8
Channel driver lock (CHAN_LOCK) : %% 9
Channel signals (CHAN_SIGNAL) : %% 10
Channel access type (CHAN_ACCESS) : %%
Channel driver type (CHAN_TYPE) : %% 11
Channel addresses (CHAN/NEXT/MASK) : %% %% %% 12
Channel acks (ACK_SLOT) : %% 13
Channel random (RANDOM_REGISTER) : %% 14
Channel status (NOISY) : %% 15
(QUIET) : %% 15
(LATCH) : %% 15
(GRANT) : %% 15
(ACTIVE) : %% 15
(NOACTIVE) : %% 15
Channel preset/timers (OVERRIDE) : %% %% 16
(RESOLUTE/QUIET) : %% %% 16
(SHUTUP) : %% %% 16
(GRANT) : %% %% 16
(WARMUP) : %% %% 16
(TRANSMIT) : %% %% 16
(HOLDUP) : %% %% 16
(RESPOND) : %% %% 16
(RELEASE) : %% %% 16
(RECEIVE/CHECK) : %% %% 16
(REQUEST) : %% %% 16
(SHORT_WARMUP) : %% 16
(SMART_MIN) : %% 16
(SMART_LONG) : %% 16
(SMART_WARM) : %% 16
(OFF_SLOT) : %% 16

1. Device-key address.

2. H-W registers address.

3. H-W parameters address.

4. Working mode of the channel (synchronous, asynchronous, DTE, DCE).

5. Communication baud rate.

85
 Software Diagnostics Output

6. Not relevant.

7. Port number.

8. Configuration mode.

9. Channel access semaphore.

10. MTE signal on events that took place.

11. Whether FSK, DPSK or FSK.

12. The address to which this site will respond through this port.

13. The ACK transmission slot.

14. Random value to obtain a channel during a retry.

15. Actual channel access timers.

16. Preset timers for fields defined in the advanced parameters of Port 3.

RS232 CHANNEL

## 340
Rs232 hardware/software last status :-
Internal software data (key) (DATA) : %% 1
Internal hardware registers (IREG) : %% 2
Internal hardware parameters (IRAM) : %% 3
Current channel port (CHAN_PORT) : %% 4
Channel status mode (CHAN_MODE) : %% 5
Channel driver lock (CHAN_LOCK) : %% 6
Channel signals (CHAN_SIGNAL): %% 7
Channel access type (CHAN_ACCESS): %%
Channel driver type (CHAN_TYPE) : %% 8
Channel control register (PBCNT) : %% 9
Channel direction register (PBDDR) : %% 10
Channel data register (PBDAT) : %% 11
Current reception empty buffers : %% 12
Current reception ready buffers : %% 13
Current transmission ready buffers : %% 14
Current transmission empty buffers : %% 15

1. Device-key address.

2. H-W registers address.

3. H-W parameters address.

4. Port number.

5. Configuration mode.

6. Channel access semaphore.

86
 Software Diagnostics Output

7. MTE signal on events that took place.

8. Whether FSK, DPSK or FSK.

9. Defines the functionality of port B in 68.

10. Determines whether the pin is for input or output.

11. Defines the value of the pin (previous parameter).

12. Number of empty Rx descriptors.

13. Number of busy Rx descriptors.

14. Number of busy Tx descriptors.

15. Number of empty Tx descriptors.

## 341
Rs232 hardware control and status :-
Internal software data (key) (DATA) : %% 1
Internal hardware registers (IREG) : %% 2
Internal hardware parameters (IRAM) : %% 3
Scc configuration register (SCON) : %% 4
Scc mode register (SCM) : %% 5
Scc data sync. register (DSR) : %% 6
Scc event register (SCCE) : %% 7
Scc mask register (SCCM) : %% 8
Scc status register (SCCS) : %% 9
Channel control register (PBCNT) : %% 10
Channel direction register (PRDDR) : %% 11
Channel data register (PBDAT) : %% 12

1. Device-key address.

2. H-W registers address.

3. H-W parameters address.

4. Determines the clock direction (Rx or Tx) and the baud rate

5. Determines the work mode — HDLC or UART.

6. Determines the HDLC flags.

7. The events that generate the interrupt.

8. Mask to block the interrupt.

9. The CM (Channel Monitor) and TD (Tone Detect) statuses.

10. Defines the functionality of port B in 68.

11. Determines whether the pin is for input or output.

12. Defines the value of the pin (previous parameter).

87
 Software Diagnostics Output

## 342
Rs232 hardware data buffers status :-
Internal software data (key) (DATA) : %% 1
Internal hardware registers (IREG) : %% 2
Internal hardware parameters (IRAM) : %% 3
Receive buffer descriptor 0 (RXBD0) : %% %% %% %% 4
Receive buffer descriptor 1 (RXBD1) : %% %% %% %% 5
Receive buffer descriptor 2 (RXBD2) : %% %% %% %% 6
Receive buffer descriptor 3 (RXBD3) : %% %% %% %% 7
Receive buffer descriptor 4 (RXBD4) : %% %% %% %% 8
Receive buffer descriptor 5 (RXBD5) : %% %% %% %% 9
Receive buffer descriptor 6 (RXBD6) : %% %% %% %% 10
Receive buffer descriptor 7 (RXBD7) : %% %% %% %% 11
Transmit buffer descriptor 0 (TXBD0) : %% %% %% %% 12
Transmit buffer descriptor 1 (TXBD1) : %% %% %% %% 13
Transmit buffer descriptor 2 (TXBD2) : %% %% %% %% 14
Transmit buffer descriptor 3 (TXBD3) : %% %% %% %% 15
Transmit buffer descriptor 4 (TXBD4) : %% %% %% %% 16
Transmit buffer descriptor 5 (TXBD5) : %% %% %% %% 17
Transmit buffer descriptor 6 (TXBD6) : %% %% %% %% 18
Transmit buffer descriptor 7 (TXBD7) : %% %% %% %% 19
Rxd/Txd function code (R/TFCR): %% 20
Maximum receive buffer length (MRBLR) : %% 21
Current receive buffer status : %% 22
Current receive buffer offset (RBD#) : %% 23
Current receive data pointer : %% %% 24
Current receive byte counter : %% 24
Current receive temp memory : %% 24
Current transmit buffer status : %% 25
Current transmit buffer offset (TBD#) : %% 26
Current transmit data pointer : %% %% 27
Current transmit byte counter : %% 27
Current transmit temp memory : %% 27

1. Device-key address.

2. H-W registers address.

3. H-W parameters address.

4. Address of frame in descriptor RX 0.

5. Address of frame in descriptor RX 1.

6. Address of frame in descriptor RX 2.

7. Address of frame in descriptor RX 3.

8. Address of frame in descriptor RX 4.

9. Address of frame in descriptor RX 5.

10. Address of frame in descriptor RX 6.

11. Address of frame in descriptor RX 7.

12. Address of frame for transmission in descriptor 0.

88
 Software Diagnostics Output

13. Address of frame for transmission in descriptor 1.

14. Address of frame for transmission in descriptor 2.

15. Address of frame for transmission in descriptor 3.

16. Address of frame for transmission in descriptor 4.

17. Address of frame for transmission in descriptor 5.

18. Address of frame for transmission in descriptor 6.

19. Address of frame for transmission in descriptor 7.

20. Rx and Tx function code.

21. Maximum received frame length.

22. The reception status of the last received frame.

23. The offset value in the descriptors of the last received frame.

24. Internal variable of 68302.

25. The status of the last transmitted frame.

26. The offset value in the descriptors of the last transmitted frame.

27. Internal variable of 68302.

## 343
Rs232 software control and status :-
Internal software data (key) (DATA) : %% 1
Internal hardware registers (IREG) : %% 2
Internal hardware parameters (IRAM) : %% 3
Current mode parameters (MODE_BACKUP) : %% 4
Current rate parameters (RATE_BACKUP) : %% 5
Current sync parameters (SYNC_BACKUP) : %% 6
Current channel port (CHAN_PORT) : %% 7
Channel status mode (CHAN_MODE) : %% %% 8
Channel driver lock (CHAN_LOCK) : %% 9
Channel signals (CHAN_SIGNAL) : %% 10
Channel access type (CHAN_ACCESS) : %%
Channel driver type (CHAN_TYPE) : %% 11
Channel addresses (CHAN/NEXT/MASK) : %% %% %% 12
Channel status (NOISY) : %% 13
(QUIET) : %% 13
Channel preset/timers (OVERRIDE) : %% %% 14
(RESOLUTE/QUIET) : %% %% 14
(SHUTUP) : %% %% 14
(GRANT) : %% %% 14
(WARMUP) : %% %% 14
(TRANSMIT) : %% %% 14
(HOLDUP) : %% %% 14
(RESPOND) : %% %% 14
1. Device-key address.

89
 Software Diagnostics Output

2. H-W registers address.

3. H-W parameters address.

4. Working mode of the channel (synchronous, asynchronous, DTE, DCE).

5. Communication baud rate.

6. Not relevant.

7. Port number.

8. Configuration mode.

9. Channel access semaphore.

10. MTE signal on events that took place.

11. Whether FSK, DPSK or FSK.

12. The address to which this site will respond through this port.

13. Actual channel access timers.

14. Preset timers for fields defined in the advanced parameters of Port 3.

MODEM CHANNEL

## 360
Modem hardware/software last status :-
Internal software data (key) (DATA) : %% 1
Internal hardware registers (IREG) : %% 2
Internal hardware parameters (IRAM) : %% 3
Current channel port (CHAN_PORT) : %% 4
Channel status mode (CHAN_MODE) : %% 5
Channel driver lock (CHAN_LOCK) : %% 6
Channel signals (CHAN_SIGNAL): %% 7
Channel access type (CHAN_ACCESS): %%
Channel driver type (CHAN_TYPE) : %% 8
Channel control register (PBCNT) : %% 9
Channel direction register (PBDDR) : %% 10
Channel data register (PBDAT) : %% 11
Current reception empty buffers : %% 12
Current reception ready buffers : %% 13
Current transmission ready buffers : %% 14
Current transmission empty buffers : %% 15

1. Device-key address.

2. H-W registers address.

3. H-W parameters address.

4. Port number.

90
 Software Diagnostics Output

5. Configuration mode.

6. Channel access semaphore.

7. MTE signal on events that took place.

8. Whether FSK, DPSK or FSK.

9. Defines the functionality of port B in 68.

10. Determines whether the pin is for input or output.

11. Defines the value of the pin (previous parameter).

12. Number of empty Rx descriptors.

13. Number of busy Rx descriptors.

14. Number of busy Tx descriptors.

15. Number of empty Tx descriptors.

## 361
Modem hardware control and status :-
Internal software data (key) (DATA) : %% 1
Internal hardware registers (IREG) : %% 2
Internal hardware parameters (IRAM) : %% 3
Scc configuration register (SCON) : %% 4
Scc mode register (SCM) : %% 5
Scc data sync. register (DSR) : %% 6
Scc event register (SCCE) : %% 7
Scc mask register (SCCM) : %% 8
Scc status register (SCCS) : %% 9
Channel control register (PBCNT): %% 10
Channel direction register (PRDDR): %% 11
Channel data register (PBDAT): %% 12

1. Device-key address.

2. H-W registers address.

3. H-W parameters address.

4. Determines the clock direction (Rx or Tx) and the baud rate.

5. Determines the work mode — HDLC or UART.

6. Determines the HDLC flags.

7. The events that generate the interrupt.

8. Mask to block the interrupt.

9. The CM (Channel Monitor) and TD (Tone Detect) statuses.

91
 Software Diagnostics Output

10. Defines the functionality of port B in 68.

11. Determines whether the pin is for input or output.

12. Defines the value of the pin (previous parameter).

## 362
Modem hardware data buffers status :-
Internal software data (key) (DATA) : %% 1
Internal hardware registers (IREG) : %% 2
Internal hardware parameters (IRAM) : %% 3
Receive buffer descriptor 0 (RXBD0) : %% %% %% %% 4
Receive buffer descriptor 1 (RXBD1) : %% %% %% %% 5
Receive buffer descriptor 2 (RXBD2) : %% %% %% %% 6
Receive buffer descriptor 3 (RXBD3) : %% %% %% %% 7
Receive buffer descriptor 4 (RXBD4) : %% %% %% %% 8
Receive buffer descriptor 5 (RXBD5) : %% %% %% %% 9
Receive buffer descriptor 6 (RXBD6) : %% %% %% %% 10
Receive buffer descriptor 7 (RXBD7) : %% %% %% %% 11
Transmit buffer descriptor 0 (TXBD0) : %% %% %% %% 12
Transmit buffer descriptor 1 (TXBD1) : %% %% %% %% 13
Transmit buffer descriptor 2 (TXBD2) : %% %% %% %% 14
Transmit buffer descriptor 3 (TXBD3) : %% %% %% %% 15
Transmit buffer descriptor 4 (TXBD4) : %% %% %% %% 16
Transmit buffer descriptor 5 (TXBD5) : %% %% %% %% 17
Transmit buffer descriptor 6 (TXBD6) : %% %% %% %% 18
Transmit buffer descriptor 7 (TXBD7) : %% %% %% %% 19
Rxd/Txd function code (R/TFCR): %% 20
Maximum receive buffer length (MRBLR) : %% 21
Current receive buffer status : %% 22
Current receive buffer offset (RBD#) : %% 23
Current receive data pointer : %% %% 24
Current receive byte counter : %% 24
Current receive temp memory : %% 24
Current transmit buffer status : %% 25
Current transmit buffer offset (TBD#) : %% 26
Current transmit data pointer : %% %% 27
Current transmit byte counter : %% 27
Current transmit temp memory : %% 27

1. Device-key address.

2. H-W registers address.

3. H-W parameters address.

4. Address of frame in descriptor RX 0.

5. Address of frame in descriptor RX 1.

6. Address of frame in descriptor RX 2.

7. Address of frame in descriptor RX 3.

8. Address of frame in descriptor RX 4.

9. Address of frame in descriptor RX 5.

92
 Software Diagnostics Output

10. Address of frame in descriptor RX 6.

11. Address of frame in descriptor RX 7.

12. Address of frame for transmission in descriptor 0.

13. Address of frame for transmission in descriptor 1.

14. Address of frame for transmission in descriptor 2.

15. Address of frame for transmission in descriptor 3.

16. Address of frame for transmission in descriptor 4.

17. Address of frame for transmission in descriptor 5.

18. Address of frame for transmission in descriptor 6.

19. Address of frame for transmission in descriptor 7.

20. Rx and Tx function code.

21. Maximum received frame length.

22. The reception status of the last received frame.

23. The offset value in the descriptors of the last received frame.

24. Internal variable of 68302.

25. The status of the last transmitted frame.

26. The offset value in the descriptors of the last transmitted frame.

27. Internal variable of 68302.

93
 Software Diagnostics Output

## 363
Modem software control and status :-
Internal software data (key) (DATA) : %% 1
Internal hardware registers (IREG) : %% 2
Internal hardware parameters (IRAM) : %% 3
Current mode parameters (MODE_BACKUP) : %% %% %% %% %% %% %% %% 4
: %% %% %% %% %% %% %% %%
Current rate parameters (RATE_BACKUP) : %% 5
Current sync parameters (SYNC_BACKUP) : %% 6
Current channel port (CHAN_PORT) : %% 7
Channel status mode (CHAN_MODE) : %% %% 8
Channel driver lock (CHAN_LOCK) : %% 9
Channel signals (CHAN_SIGNAL) : %% 10
Channel access type (CHAN_ACCESS) : %%
Channel driver type (CHAN_TYPE) : %% 11
Channel addresses (CHAN/NEXT/MASK) : %% %% %% 12
Channel status (NOISY) : %% 13
(QUIET) : %% 13
Channel preset/timers (OVERRIDE) : %% %% 14
(RESOLUTE/QUIET) : %% %% 14
(SHUTUP) : %% %% 14
(GRANT) : %% %% 14
(WARMUP) : %% %% 14
(TRANSMIT) : %% %% 14
(HOLDUP) : %% %% 14
(RESPOND) : %% %% 14

1. Device-key address.

2. H-W registers address.

3. H-W parameters address.

4. Working mode of the channel (synchronous, asynchronous, DTE, DCE).

5. Communication baud rate.

6. Not relevant.

7. Port number.

8. Configuration mode.

9. Channel access semaphore.

10. MTE signal on events that took place.

11. Whether FSK, DPSK or FSK.

12. The address to which this site will respond through this port.

13. Actual channel access timers.

14. Preset timers for fields defined in the advanced parameters of Port 3.

94
 Software Diagnostics Output

TIMERS (10__MS , 100_MS , 1__SEC , 1__MIN)

## 380 LEVEL = 0
# of entries in the service table (actual) : %% 1
Maximum # of entries in the service table : %% 2
# of time units passed from last task running : %% 3
The limit # of time units passed without activating task : %% 4

1. The number of timer services (in the specific Instance) currently in use.

2. The maximum number of timer services that can be used.

3. The number of time units (depending on the timer resolution) that have elapsed since the last
execution.

4. The maximum number of time units that will elapse without activating the instance, until an error
message reports instance timer delay.

TIME-TAG (ACE_TM_)

## 400 LEVEL = 0
time_tag
The start pointer in queue : %% 1
The writer pointer in queue : %% 2
The read pointer in queue : %% 3
The end pointer in queue : %% 4
# of free bytes in queue : %% 5
The last event in queue is an i/o event : %% 6
There is at least 1 i/o event in queue : %% 7
Queue was full at least one time : %% 8
Queue is locked : %% 9

1. Pointer to the time-tag queue.

2. Pointer to the next write.

3. Pointer to the next read.

4. Pointer to the end of the queue.

5. Number of free bytes in the queue.

6. Whether the last element in the queue is COS (Change of State) of I/O.

7. Whether there is COS (Change of State) of any I/O.

8. Whether the queue was ever full.

9. Lock for down load purposes.

95
 Software Diagnostics Output

SESSION DEVICE = SESS1, SESS2,..., MSESS1, MSESS2…

Layer Name Device Notes
Name
Session SESS The slave (RTU)
MSESS The master (generally for ‘C’ application

## 460 LEVEL = 1
# Is RTU secured? : %%1
# Security policy password length : %%2
# Session's peer site : %%3
# Is LEGACY comm. with peer site allowed? : %%4
# User role on start session : %%5
# Is session authenticated? : %%6
# Is part of session is LEGACY session? : %%7
# Is session authorization failed? : %%8

1. Does the RTU use MDLC authentication?

2. The password length embedded in the outbound frame's secured credentials.

3. The site ID of this RTU's peer in the last communication session.

4. This RTU's peer in the last session communication does not use authentication. Can this RTU
commnucate with it?

5. The role of the user that initiated the session.

6. Whether the session was successfully authenticated.

7. Whether one side of the SESSION does not support authentication..

8. Whether the session was successfully authenticated but not authorized.

## 461 LEVEL = 12
# of successfully transmitted secured frames : %%1
# of non-successful transmitted secured frames: %%2
# of successfully received secured frames : %%3
# of non-successfull received secured frames : %%4

1. The number of outbound frames with secured credentials transmitted successfully.

2. The number of outbound frames with secured credentials transmitted unsuccessfully.

3. The number of inbound frames with secured credentials received and authenticated successfully.

4. The number of inbound frames with secured credentials received and authenticated unsuccessfully.

96
 Software Diagnostics Output

## 462 LEVEL = 255

level 1 - get secured communication general information",
level 12 - get secured transmission accumulative data and clear the
accumulated values",
level 13 - get secured transmission accumulative data",

This lists all diagnostics provided for the device at all its supported levels.

DI

I/O MODULES (R0M1 , R0M2 ,...)

## 500 LEVEL = 1
Di : priority=%% , eirq=%% , test=%% , di_pol=%% , cntr=%% , sr=%%
1 2 3 4 5 6

1. Interrupt priority level : 1 - 254 (0 - no interrupts)

2. EIRQ line : 0 - disabled, 1, 2 or 3

3. DI loop test on : YES/NO

4. Reverse polarity : YES/NO

5. Counter rate : 0 = 30 KHZ , 1 = 3.75 KHZ

6. Serial rate : Approximate values

0 38 msec
1 19
2 9.5
3 4.75
4 2.4
5 1.2
6 0.6

8DO

## 501 LEVEL = 1
Do : init=%% 1 , one submodule: sub_module=%%: 2
mode2.refresh=%% 3 , sub_priority=%% 4 , sub_test=%% 5
mode0 : irq_en=%% 6 , no_clk1=%% 7 , sr=%% 8
mode1 : no_clk=%% 9 , wdt_sel=%% 10 , bi_int=%% 11 , ext_int=%% 12
ref_sel=%% 13 , ocs=%% 14

1. Init state : 1 = CREATE , 2 = POWER UP , 3 = DONE

2. Submodule 0 or 1

97
 Software Diagnostics Output

3. Refresh trigger

4. Interrupt priority level : 1-254 (0 - no interrupts)

5. DI loop test on : YES/NO

6. IRQ Enable : YES/NO

7. “NO CLOCK” WDT Enable : YES/NO

8. Sr - Serial rate : Approximate values

0 38 msec
1 19
2 9.5
3 4.75
4 2.4
5 1.2
6 0.6

9. “NO CLOCK” WDT Enable : YES/NO

10. WDT SELECT : 0 - 4 secs , 1 - 1 sec

11. Relay Readback : 0 - Actual , 1 - Desired

12. Led display of RO: 0 - Actual , 1 - Desired

13. Refresh start : 0 - no refresh of DO , 1 - 1.1 sec refresh, 2 - 4.5 sec refresh, 3 - 18 sec refresh

14. Pulse width for ML Relays : 0 - no clock , 1 - 8 msec, 2 - 16 msec, 3 - 32 msec

## 502
Do : init=%% 1 , two submodules: sub_module=%%: 2
mode2.refresh=%% 3 , sub_priority=%% 4 , sub_test=%% 5
mode0 : irq_en=%% 6 , no_clk1=%% 7 , sr=%% 8
mode1 : no_clk=%% 9 , wdt_sel=%% 10 , bi_int=%% 11 , ext_int=%% 12
ref_sel=%% 13 , ocs=%% 14

sub_module=%%:
mode2.refresh=%% , sub_priority=%% , sub_test=%%
mode0 : irq_en=%% , no_clk1=%% , sr=%%
mode1 : no_clk=%% , wdt_sel=%% , bi_int=%% , ext_int=%%
ref_sel=%% , ocs=%%

1. Init state : 1 = CREATE , 2 = POWER UP , 3 = DONE

2. Submodule 0 or 1

3. Refresh trigger

4. Interrupt priority level : 1-254 (0 - no interrupts)

5. DI loop test on : YES/NO

98
 Software Diagnostics Output

6. IRQ Enable : YES/NO

7. “NO CLOCK” WDT Enable : YES/NO

8. Sr - Serial rate : Approximate values

0 38 msec
1 19
2 9.5
3 4.75
4 2.4
5 1.2
6 0.6

9. “NO CLOCK” WDT Enable : YES/NO

10. WDT SELECT : 0 - 4 secs , 1 - 1 sec

11. Relay Readback : 0 - Actual , 1 - Desired

12. Led display of RO: 0 - Actual , 1 - Desired

13. Refresh start : 0 - no refresh of DO , 1 - 1.1 sec refresh, 2 - 4.5 sec refresh, 3 - 18 sec refresh

14. Pulse width for ML Relays : 0 - no clock , 1 - 8 msec, 2 - 16 msec, 3 - 32 msec

## 503 LEVEL = 1
Ai : priority=%% 1 , irq_ctrl=%% 2 , eom_fifo=%% 3 , tx_fifo=%% 4
filter_rank=%% 5

1. Interrupt priority level : 1-254 (0 - no interrupts)

2. IRQ line : 0 - disabled, 1m, 2, or 3

3. End of message FIFO : Y/N

4. Num bytes in TX FIFO : 0 - 8

5. Filter Rank : 1 , 2 , 4 or 8

## 504 LEVEL = 1
Ao : ao_swap=%% 1 , ao_rate=%% 2 , ao_ref_sel 3 , ao_refresh=%% 4
irq_priority=%% 5 , eirq=%% 6 , ai_irq_en=%% 7 ,
di_irq_en=%% 8
spi_control=%% 9 , spi_cs_control=%% 10
smc_byte=%% 11 , wamst=%% 12

1. Swap order of AO bits : Y/N

2. AO transfer time : 0 - 3/4 msec , 1 - 3 msec

3. AO refresh select : 0 (no refresh) , 1 - 1/4 sec , 2 - 1 sec , 3 - 4 sec

99
 Software Diagnostics Output

4. AO refresh enable : 1 bit per channel : Y/N

5. Interrupt priority level : 1-254 (0 - no interrupts)

6. IRQ Line : 0 - disabled , 1, 2, or 3

7. AI IRQ Enable : Y/N

8. DI IRQ Enable : Y/N

9. SPI Control byte

10. SPI CS force : Y/N

11. SMC byte

12. WAMST byte

MIX

## 505 LEVEL = 1
Mixed i/o : ro_wdt=%% 1 , ro_ck=%% 2 , ro_ref=%% 3
di_fc_en=%% 4 , di_cos_en=%% 5 , di_sr=%% 6
di_enc=%% 7 , ai_rate=%% 8 , ai_make_delay=%% 9 ,
ai_start_delay=%% 10
ai_filter_rank=%% 11
irq_priority=%% 12, eirq=%% 13, ai_irq_en 14 ,
di_irq_en=%% 15 spi_control=%% 16 , spi_cs_control=%% 17
smc_byte=%% 18 , wamst=%% 19

1. RO WDT select : 0 - 4 secs , 1 - 16 secs

2. RO pulse width (ML) : 0 - 8 msec , 1 - 17 msec , 2 - 35 msec, 3 - 128 msec

3. RO refresh rate : 0 -1 sec , 1 - 4 sec, 2 - 9 sec, 3 - 18 sec

4. DI Fast Capture En : 1 bit for each input : Y/N

5. DI Cos Enable En : 1 bit for each input : Y/N

6. DI Serial rate : Approximate values

0 38 msec
1 19
2 9.5
3 4.75
4 2.4
5 1.2
6 0.6

7. AI channel select is encoded : Y/N

8. AI rate : 0 - 8 micro on , 24 off ; 1 - 17 micro on , 48 off

100
 Software Diagnostics Output

9. AI make delay : 0 - 70 micro , 1 - 140 micro, 2 - 280 micro, 3 - 560 micro

10. AI start delay : 0 - 140 micro , 1 - 280 , 2 - 0.5 msec , 3 - 1 msec

11. AI filter rank : 1 , 2 , 4 , 8

12. Interrupt priority level : 1-254 (0 - no interrupts)

13. IRQ Line : 0 - disabled , 1, 2, or 3

14. AI IRQ Enable : Y/N

15. DI IRQ Enable : Y/N

16. SPI Control byte

17. SPI CS force : Y/N

18. SMC byte

19. WAMST byte

## 506 (MIX , LEVEL = 2)

Mixed i/o : ai error count=%%

Count of AI fail or loss of synchronization (Information only: the problem is corrected by software).

DSP (AC ANALYZER)

## 507 LEVEL = 1
Dsp : di_pol=%% 1 , cb_pol=%% 2 , di_fc_en=%% 3 , di_cos_en=%% 4
ga_eirq=%% 5 , ga_eirq_with_irq=%% 6 , ga_eirq_without_irq=%% 7
sr=%% 8 , sr_with_irq=%% 9 , sr_without_irq=%% 10
ga_prior=%% 11 , di_irq_en=%% 12
dsp_prior=%% 13 , dsp_eirq=%% 14 , dsp_irq_en=%% 15
ro_ref_rate=%% 16 , ro_duration=%% 17 , ro_type=%% 18
div_en=%% 19 , div_ratio=%% 20
dsp_mode=%% 21 , host_mode=%% 22
dsp_wd_rate=%% 23 , dsp_wd_irq_en=%% 24 , dsp_wd_en=%% 25

1. DI polarity reversed : Y/N

2. Checkback polarity reversed : Y/N

3. DI Fast Capture Enable : 1 bit for each input : Y/N

4. DI Cos Enable : 1 bit for each input: Y/N

5. GA IRQ Line : 0 - disabled, 1, 2, or 3

6. Default GA IRQ Line when using IRQ

7. Default GA IRQ Line when not using IRQ

101
 Software Diagnostics Output

8. DI Serial rate : Approximate values

0 38 msec
1 19
2 9.5
3 4.75
4 2.4
5 1.2
6 0.6

9. DI serial rate when using interrupts

10. DI serial rate when not using interrupts

11. GA Interrupt priority : 0 - disabled , 1 - 254

12. DI IRQ Enable : Y/N

13. DSP Interrupt priority : 0 - disable , 1 - 254

14. DSP IRQ Line : 0 - disabled, 1, 2, or 3

15. DSP IRQ Enable : Y/N

16. RO refresh rate : 0 - 1 sec , 1-4 sec , 2-9 sec, 3-18 sec

17. RO pulse duration (ML) : 0 - 17 msec , 1-35 msec, 2-128 msec, 3-500 msec

18. RO Type : 1 bit for each RO - 0 - EE , 1 - ML

19. Enable Divider :Y/N

20. Divider ratio “n” : divide by 2 (n + 1)

21. DSP DMA mode : 0 - Host Read IRQ , 1 - Host Write IRQ , 2 - Read - Write IRQ , 3 - Read 8 bit
DMA , 4 - Read 16 bit DMA , 5 - Write 8 bit DMA , 6 - Write 16 bit DMA

22. GA Mode : 0 - IRQ , 1 - DMA

23. DSP WDT rate : 0-64 msec, 1-250 msec, 2-1 sec , 3-4 secs

24. DSP WDT IRQ Enable : Y/N

25. DSP WDT Enable : Y/N

102
 Software Diagnostics Output

## 508 (SC , LEVEL = 1)

Single cable : rx_task_priority=%% 1 , tx_task_priority=%% 2 ,
eirq=%% 3 , cosirq_en=%% 4 , rxirq_en=%% 5 ,
txirq_en=%% 6 , after_reset=%% 7 ,
slave_handshake=%% 7 , activity_state=%% 7
sensitive_40v=%% 7 , line1_rtu_fail=%% 8 ,
line2_rtu_fail=%% 9
sgc_software_ver_num=%% 10 , init=%% 11

1. Task priority of Rx task.

2. Task priority of Tx task.

3. EIRQ line : 0 - disabled, 1, 2 or 3

4. COS IRQ Enabled: Y/N

5. RX IRQ Enabled: Y/N

6. TX IRQ Enabled: Y/N

7. Inn er flags in the module to be called through the application.

8. RTU warning - failure on line 1.

9. RTU warning - failure on line 2.

10. Inner program version of module.

11. Whether the module state is init or regular.

## 510
Dsp: Loadable Code - address=%% 1, length=%% 2
P MEM: Code - address=%% 3, length=%% 4
X MEM: Data - address=%% 5, length=%% 6

1. Address of DSP Loadable Code.

2. Length of DSP Loadable Code.

3. Address of DSP P Mem Code.

4. Length of DSP P Mem Code.

5. Address of DSP X Mem Data..

6. Length of DSP X Mem Data.

## 511
Dsp: AO Image: Number of AO locations in use=%% 1
Location Value

1. Number of AO locations in use.

103
 Software Diagnostics Output

Table of AO locations and their values.

## 513
Dsp: Num error calls to dsp_init()=%% 1

1. Number of error calls to the dsp_init function.

## 518
Auto IO Recognition: %% 1

1. Automatic I/O Configuration bit in Site Configuration is Enabled/Disabled.

## 519
Number of IO Modules: %% 1
List of All IO Module Types: 2

1. Number of modules found in unit.

2. List of all I/O Module Types defined in unit.

RS485

## 520
Rs485 hardware/software last status :-
Internal software data (key) (DATA) : %% 1
Internal hardware registers (IREG) : %% 2
Internal hardware parameters (IRAM) : %% 3
Current channel port (CHAN_PORT) : %% 4
Channel status mode (CHAN_MODE) : %% 5
Channel driver lock (CHAN_LOCK) : %% 6
Channel signals (CHAN_SIGNAL): %% 7
Channel access type (CHAN_ACCESS): %%
Channel driver type (CHAN_TYPE) : %% 8
Channel control register (PBCNT) : %% 9
Channel direction register (PBDDR) : %% 10
Channel data register (PBDAT) : %% 11
Current reception empty buffers : %% 12
Current reception ready buffers : %% 13
Current transmission ready buffers : %% 14
Current transmission empty buffers : %% 15

1. Device-key address.

2. H-W registers address.

3. H-W parameters address.

4. Port number.

104
 Software Diagnostics Output

5. Configuration mode.

6. Channel access semaphore.

7. MTE signal on events that took place.

8. Whether FSK, DPSK or FSK.

9. Defines the functionality of port B in 68.

10. Determines whether the pin is for input or output.

11. Defines the value of the pin (previous parameter).

12. Number of empty Rx descriptors.

13. Number of busy Rx descriptors.

14. Number of busy Tx descriptors.

15. Number of empty Tx descriptors.

## 521
Rs485 hardware control and status :-
Internal software data (key) (DATA) : %% 1
Internal hardware registers (IREG) : %% 2
Internal hardware parameters (IRAM) : %% 3
Scc configuration register (SCON) : %% 4
Scc mode register (SCM) : %% 5
Scc data sync. register (DSR) : %% 6
Scc event register (SCCE) : %% 7
Scc mask register (SCCM) : %% 8
Scc status register (SCCS) : %% 9
Channel control register (PBCNT) : %% 10
Channel direction register (PRDDR) : %% 11
Channel data register (PBDAT) : %% 12

1. Device-key address.

2. H-W registers address.

3. H-W parameters address.

4. Determines the clock direction (Rx or Tx) and the baud rate.

5. Determines the work mode — HDLC or UART.

6. Determines the HDLC flags.

7. The events that generate the interrupt.

8. Mask to block the interrupt.

9. The CM (Channel Monitor) and TD (Tone Detect) statuses.

10. Defines the functionality of port B in 68.

105
 Software Diagnostics Output

11. Determines whether the pin is for input or output.

12. Defines the value of the pin (previous parameter).

## 522
Rs485 hardware data buffers status :-
Internal software data (key) (DATA) : %% 1
Internal hardware registers (IREG) : %% 2
Internal hardware parameters (IRAM) : %% 3
Receive buffer descriptor 0 (RXBD0) : %% %% %% %% 4
Receive buffer descriptor 1 (RXBD1) : %% %% %% %% 5
Receive buffer descriptor 2 (RXBD2) : %% %% %% %% 6
Receive buffer descriptor 3 (RXBD3) : %% %% %% %% 7
Receive buffer descriptor 4 (RXBD4) : %% %% %% %% 8
Receive buffer descriptor 5 (RXBD5) : %% %% %% %% 9
Receive buffer descriptor 6 (RXBD6) : %% %% %% %% 10
Receive buffer descriptor 7 (RXBD7) : %% %% %% %% 11
Transmit buffer descriptor 0 (TXBD0) : %% %% %% %% 12
Transmit buffer descriptor 1 (TXBD1) : %% %% %% %% 13
Transmit buffer descriptor 2 (TXBD2) : %% %% %% %% 14
Transmit buffer descriptor 3 (TXBD3) : %% %% %% %% 15
Transmit buffer descriptor 4 (TXBD4) : %% %% %% %% 16
Transmit buffer descriptor 5 (TXBD5) : %% %% %% %% 17
Transmit buffer descriptor 6 (TXBD6) : %% %% %% %% 18
Transmit buffer descriptor 7 (TXBD7) : %% %% %% %% 19
Rxd/Txd function code (R/TFCR): %% 20
Maximum receive buffer length (MRBLR) : %% 21
Current receive buffer status : %% 22
Current receive buffer offset (RBD#) : %% 23
Current receive data pointer : %% %% 24
Current receive byte counter : %% 24
Current receive temp memory : %% 24
Current transmit buffer status : %% 25
Current transmit buffer offset (TBD#) : %% 26
Current transmit data pointer : %% %% 27
Current transmit byte counter : %% 27
Current transmit temp memory : %% 27

1. Device-key address.

2. H-W registers address.

3. H-W parameters address.

4. Address of frame in descriptor RX 0.

5. Address of frame in descriptor RX 1.

6. Address of frame in descriptor RX 2.

7. Address of frame in descriptor RX 3.

8. Address of frame in descriptor RX 4.

9. Address of frame in descriptor RX 5.

10. Address of frame in descriptor RX 6.

106
 Software Diagnostics Output

11. Address of frame in descriptor RX 7.

12. Address of frame for transmission in descriptor 0.

13. Address of frame for transmission in descriptor 1.

14. Address of frame for transmission in descriptor 2.

15. Address of frame for transmission in descriptor 3.

16. Address of frame for transmission in descriptor 4.

17. Address of frame for transmission in descriptor 5.

18. Address of frame for transmission in descriptor 6.

19. Address of frame for transmission in descriptor 7.

20. Rx and Tx function code.

21. Maximum received frame length.

22. The reception status of the last received frame.

23. The offset value in the descriptors of the last received frame.

24. Internal variable of 68302.

25. The status of the last transmitted frame.

26. The offset value in the descriptors of the last transmitted frame.

27. Internal variable of 68302.

107
 Software Diagnostics Output

## 523
Rs485 software control and status :-
Internal software data (key) (DATA) : %% 1
Internal hardware registers (IREG) : %% 2
Internal hardware parameters (IRAM) : %% 3
Current mode parameters (MODE_BACKUP) : %% 4
Current rate parameters (RATE_BACKUP) : %% 5
Current sync parameters (SYNC_BACKUP) : %% 6
Current channel port (CHAN_PORT) : %% 7
Channel status mode (CHAN_MODE) : %% %% 8
Channel driver lock (CHAN_LOCK) : %% 9
Channel signals (CHAN_SIGNAL) : %% 10
Channel access type (CHAN_ACCESS) : %%
Channel driver type (CHAN_TYPE) : %% 11
Channel addresses (CHAN/NEXT/MASK) : %% %% %% 12
Channel status (NOISY) : %% 13
(QUIET) : %% 13
Channel preset/timers (OVERRIDE) : %% %% 14
(RESOLUTE/QUIET) : %% %% 14
(SHUTUP) : %% %% 14
(GRANT) : %% %% 14
(WARMUP) : %% %% 14
(TRANSMIT) : %% %% 14
(HOLDUP) : %% %% 14
(RESPOND) : %% %% 14

1. Device-key address.

2. H-W registers address.

3. H-W parameters address.

4. Working mode of the channel (synchronous, asynchronous, DTE, DCE).

5. Communication baud rate.

6. Not relevant.

7. Port number.

8. Configuration mode.

9. Channel access semaphore.

10. MTE signal on events that took place.

11. Whether FSK, DPSK or FSK.

12. The address to which this site will respond through this port.

13. Actual channel access timers.

14. Preset timers for fields defined in the advanced parameters of Port 3.

108
 Software Diagnostics Output

FLASH MEMORY (FLASHDB, FLSEXT1)

## 600 LEVEL = 0
Pointer to entries : %% 1
Number of entries : %% 2
Flash start address : %% 3
Flash end address : %% 4
Flash length : %% 5
Flash number of burns: %% 6

1. Pointer to block IDs address list.

2. Maximum number of different types of block ID.

3. The starting address of the flash memory.

4. The end of the flash memory.

5. The size of the flash memory in bytes.

6. The number of times the flash memory has been burned.

LEVEL = 2
Disabled blocks for type- %%1
Block- 0 : %%2
Block- 1 : %%2

1. The block type (block id). For the FLASHDB device (application flash), there can be up to 50 blocks
. For FLSEXT1 (logging flash), the user can define up to five blocks (0-4).

2. The status of the blocks in the application or logging flash can be one of: 0 (block enabled) or 1
(block disabled).

## 601 LEVEL = 1, 20 , 21 , ... , 39

Pointer to version : %% 1
Pointer to data : %% 2
Length of data : %% 3
File Name : %% 4
Block Description : %% 5

1. Pointer to block’s header.

2. Pointer to block’s data.

3. Length of block’s data.

4. Name of file in block (downloaded blocks only)

5. Description of block (download blocks only)

109
 Software Diagnostics Output

• Supported only by versions < 3.70. Previous versions support 20 types of blocks.
In order to receive diagnostics on block number 0 , use LEVEL = 20.
In order to receive diagnostics on block number 5 , use LEVEL = 25.

• From versions ≥ V3.70 on, at LEVEL = 1 the system displays a table that includes all of this data for
all block IDs.

FFILES

## 610 LEVEL = 0
File name Ram address Size loaded to RAM
------------------------------------------------------------------------

Lists all the file names that were burned to flash an d loaded to RAM.

File Name The name of the file, e.g. conf.30, where conf is the file name and
30 is the file type suffix.

Ram address The address of the file in RAM, e.g. 6909060H .

Size loaded to RAM The size in bytes of the file in RAM, e.g. 2872 .

## 611 LEVEL = 255

level 0 - List of application files loaded from FLASH memory to RAM memory.
Level 1 - List of application files loaded to RAM memory (not in FLASH
memory).
Level 255- This list

## 620
Low byte : %%
Message : %%
‘send message’ : %%
‘comm established’ flag : %%
‘message exist’ flag : %%
Warmup not done : %%
Dial number : %%
Physical key : %%
Mini - session key : %%
Unformatted heap key : %%

110
 Software Diagnostics Output

MFFS

MFFS LEVEL = 0
FDV files names - list:
name=<%%>, size=(%%), time=<%%>, date=<%%>
Total size=%%=%% Bytes

This level lists the user files (File ID the form of <filename.file type>, e.g. conf.51.) and their size. The
'time' and 'date' have no meaningful data.

MFFS LEVEL = 1
DAV files names - list:
name=<%%>, Type=<%%>, addr=%%, size=%%

This level lists file information in the system area.

MFFS LEVEL = 2
FDI General diagnostic info - flash Using parameters:
Flash start address.= %%

DAV start address...= %%

DAV number of blocks= %%
DAV block size......= %%

FDV start address...= %%

FDV number of blocks= %%
FDV block size......= %%

This diagnostic lists FLASH block information. FDV is the user area and DAV is the system area.

111
 Software Diagnostics Output

MFFS LEVEL = 3
FDI space and size info:
FDV larges avaliable object,
until File and Data is going full = %% (%%) Bytes

FDV available File and Data space statistics:

Free_space.=%% (%%) Bytes
Dirty_space=%% (%%) Bytes

DAV Max space:

Total size (Bytes).................................= %% (%%)
Managed size (exclude ReservedReclaim size) (Bytes)= %% (%%)
Blocks size (Bytes)................................= %% (%%)
Page size (Bytes)..................................= %%
Blocks reserved for reclaim........................= %%
Blocks reserved for system code....................= %%
Threshold level for triggering reclaim.............= %%
Padding to align data..............................= %%

This diagnostic lists FLASH blocks information.

FDV is the user area and DAV is the system area.

Dirty_space is area containing deleted data but not yet ready for writing. Note that actual total of all file
sizes may yield different values than this diagnostic shows, due to file system overhead.

MFFS LEVEL = 255

List diag. levels:
0 - FDV files names - list:
1 - DAV files names - list:
2 - FDI General diagnostic info - flash Using parameters:
3 - FDI space and size info:
4 - FDI space in details:
5 - FDI internal state:
6 – Flash Blocks Lock Status:
255 - This list.

This lists all diagnostics provided for the device at all its supported levels.

MFFS LEVEL = 6
Flash Blocks Lock Status:
Flash Read Identifier Codes:
Device code: %%
Manufacturer code: %%
Flash Blocks Lock Status:
Block start address Is block locked?
%% %%

This diagnostic lists the blocks of the flash which are locked (cannot be written to).

112
 Software Diagnostics Output

LDIALER (DIL2D , DIL 3D)

## 640 LEVEL = 0
Physical device key : %% 1
Physical pin’s table : %% 2
Async dial physical device key : %% 3
Async dial physical pin’s table : %% 4
Interval between phone call retries (sec) : %% 5
# of phone call retries : %% 6
# of times to call the physical_receive
before hanging up (indicator) : %% 7
# of times to call the physical_receive
before hanging up (responser) : %% 8
‘wait for call’ interval in (milli - sec) : %% 9

1. Adaptor layer device key.

2. Adaptor pin table.
3. Dial (DART) device key.
4. Dial (DART) PIN table.
5. Interval between two dialing attempts.
6. Number of phone call retries.
7. Quiet time, in seconds, before hanging up on the initiating site.
8. Quiet time, in seconds, before hanging up on the responding site.
9. Inner program waiting time for a new incoming call.

## 641 LEVEL = 1
Ldialer current state : : %% 1
Current hang up counter : %% 2
Last / current dialed phone number : %% 3
Previous dialed phone number : %% 4
Last / current partner site id : %% 5
Is initiator : %% 6

1. Ldialer state: 0 - wait for new call, 1- communication established

2. Time counter until disconnection.

3. Last or current dialed number.

4. Previous number dialed.

5. Last site ID connected.

6. Whether initiator or responder.

113
 Software Diagnostics Output

(ML_DL)

## 645 LEVEL = 0
# of dial links (preset) : %% 1
Network key : %% 2
Pointer to links table : %% 3

1. Number of dialing channels.

2. Network layer device key.

3. Pointer to Dial-type channels table

114
 Software Diagnostics Output

## 646 LEVEL = 1
# of dial links (current) : %% 1
Last failed link used : %% 2
Port status partner link_key ldialer_key
------------------------------------------------------
3 4 5 6 7

1. Number of dialing channels.

2. The last failed channel used.

3. The dialing line.

4. The call status.

5. The initiator site ID.

6. The Link layer device key.

7. The Ldialer layer device key.

TOPLC (PLC1L, PLC2L, PLC3L)

## 660 LEVEL = 0
Port name : %% 1
Connection to : %% 2
Appl. code area : %% 3
Appl. code length : %% 4
Appl RAM area : %% 5
Appl. RAM len : %% 6
Number of retries : %% 7
Number of polls : %% 8
No response timeout : %% 9
# of idles timeout : %% 10
# of diag errors : %% 11
Load module vers : %% 12
Load module rev : %% 13
Load module name : %% 14
Load module diag : %% 15

Diagnostics for third party protocol port defined as connected ‘TO PLC’.

1. PLC1 / PLC2 / PLC3

2. PLC (slave)
3. Address where the FLS file was downloaded.
4. Length of the code that was downloaded.
5. Start of RAM - used for the PLC PORT software.
6. Length of RAM - used for the PLC PORT software.
7. Maximum number of retries.
8. Maximum number of pollings.
115
 Software Diagnostics Output

9. Maximum amount of time to announce no response.

10. Number of idles to announce end of RX.
11. Number of errors.
12. Downloadable module version.
13. Downloadable module revision.
14. Name of the downloadable module.
15. Diagnostic string given by the downloadable module.

## 661 LEVEL = 1
Parm 1 : %%
Parm 2 : %%
Parm 3 : %%
Parm 4 : %%
Parm 5 : %%
Parm 6 : %%
Parm 7 : %%
Parm 8 : %%
Parm 9 : %%
Parm 10 : %%

• Diagnostics for driver specific parameters for port connected ‘TO PLC’

• These parameters are actually the driver specific parameters (‘TO PLC’ port). The parameters can be
defined in the PLC expert parameter screen. Currently these parameters are not in use.

TOSCADA (PLC1L, PLC2L, PLC3L)

## 670 LEVEL = 0
Port name : %% 1
Connection to : %% 2
Appl. code area : %% 3
Appl. code len : %% 4
Appl RAM area : %% 5
Appl. RAM len : %% 6
# of diag errors : %% 7
Local plc reply timeout : %% 8
Remote reply timeout : %% 9
Mode of translation : %% 10
No response timeout : %% 11
#of idles timeout : %% 12
Load module vers : %% 12
Load module rev : %% 13
Load module name : %% 14
Load module diag : %% 15

1. PLC1 / PLC2 / PLC3

2. Master computer.

3. Address of downloaded FLS file.

116
 Software Diagnostics Output

4. Length of downloaded FLS file.

5. Start of RAM - used for the PLC PORT software.

6. Length of RAM for the PLC PORT software.

7. Number of errors.

8. Reply timeout in seconds from PLC (locally connected).

9. Reply timeout in seconds from PLC (remotely connected).

10. Modbus Reg # to (z , y , x) mode of translation.

11. Maximum time to announce no response.

12. Maximum number of idles to announce end of Rx.

13. The downloadable module version.

14. The downloadable module revision.

15. The downloadable module name.

16. The downloadable module diagnostic string.

## 671 LEVEL = 1
Parm 1 : %%
Parm 2 : %%
Parm 3 : %%
Parm 4 : %%
Parm 5 : %%
Parm 6 : %%
Parm 7 : %%
Parm 8 : %%
Parm 9 : %%
Parm 10 : %%

• Diagnostics for driver specific parameters for port connected ‘TO MASTER’

• These parameters are actually the driver specific parameters (‘TO MASTER’ port). The parameters
can be defined in the PLC expert parameter screen. Currently these parameters are not in use.

SWITCHR/SWITCHER

## 680 LEVEL = 0
Maximum number of plc ports : %% 1
Actual number of plc ports : %% 2

• Third party protocol switcher (network) diagnostics.

1. Maximum number of third party protocol ports allowed.

117
 Software Diagnostics Output

2. Number of defined third party protocol ports.

## 681 LEVEL = 1
Plc port connected to link device name
1 2 3

• The third party protocol port list.

1. Port 1 / 2 / 3 for PLC1 / PLC2 / PLC3

2. SLAVE / MASTER

3. Physical layer device name

## 682 LEVEL = 2
Number of switcher_push_reply calls : %% 1
Number of switcher_push_control calls : %% 1
Number of switcher_push_frame calls : %% 1
Number of switcher_send_control calls : %% 1
Number of userrom_push_reply calls : %% 1
Number of userrom_push_control calls : %% 1
Number of tmuxsend_frame calls : %% 1
Number of plcs_s2m_send_reply calls : %% 1
Number of plcs_m2s_send_control calls : %% 1
Number of errors : %% 2

1. Internal counters that count the number of times activated.

2. Number of times an error has occurred.

FRM_USR/FRAME SEQUENCE

## 700
application identity : %%1
maximum buffers in ready queue : %%2
Number of buffers in list : %%3
maximum errors in ready queue : %%4
Number of errors in list : %%5
maximum indications in ready queue : %%6
Number of indications in list : %%7
Time (in sec) to flush rx frames : %%8
# rx frames thrown under flush : %%9

1. Application ID number.

2. Maximum number of frames allowed to be accumulated.

3. Number of frames currently waiting in the queue.

4. Maximum number of error frames allowed to be accumulated.

118
 Software Diagnostics Output

5. Number of error frames currently in list.

6. Maximum number of indication frames allowed to be accumulated.

7. Number of indication frames currently in list.

8. The amount of time required to flush received frames.

9. The number of frames which were flushed from the received queue.

BURST - SEQ

## 710
application identity : %% 1
maximum buffers in ready queue : %% 2
Number of buffers in list : %% 3

1. Application ID number.

2. Maximum number of frames allowed to be accumulated.

3. Number of frames currently waiting in the queue.

PHONE BOOK LEVEL = 0 PHNBK

## 940
Start at flash : %% 1
Number of entries : %% 2

1. The phone book address in the flash.

2. The number of entries in the phone book.

## 941
Site Id Phone Numbers:

• The contents of phone book in the flash is provided.

119
 Software Diagnostics Output

ACE_TMR/TIMER EVENT

## 960 LEVEL = 0
Timers max. value (in 10msc units) : %% 1
Max. number of events / timers in buffer : %% 2
Current number of events / timers in buffer : %% 3
# of heap_aloc_buf failed : %% 4

1. The maximum number of timers that can be set by SetTmr to a specific event.

2. The maximum number of events and timers that can be managed simultaneously by the timer event
device. (They are managed by the heap.)

3. The number of events and timers currently in the heap.

4. The number of failed attempts to allocate buffers from the events’ and timers’ heap. (Its size as in 2.)

## 961 LEVEL = 1
Is Device running ? : %%1
Events enabled ? : %%2
Heap device key : %%3
Last written heap buffer : %%4
Current 10ms index : %%5
Last read index : %%6
----------------------------------
Is device busy? : %%7
Was there overflow? : %%8
Sync Day : %%9
Sync Year : %%10
pp_tm_index : %%11

1. Whether the device is running. (Does not run during load and reset load.)

2. Whether the events are enabled.

3. The key to the heap from where event buffers are taken.

4. The last event buf that was written.

5. The time index of the current time.

6. The time index of the last read event.

7. GtEvnt is/isn’t busy.

8. 1 if events weren't processed for the max event time value (default of 15 seconds).

9. Day in year of the last time synchronization.

10. Year of time of the last synchronization

11. Pointer to the time events array.

120
 Software Diagnostics Output

• The above indexes are in a cyclic array that return a pointer per 10 msec. Every such pointer points to
the list of events that were received in those last 10 msec.

## 962 LEVEL = 2
Current Read index data
Header data:
Header address: : %%1
p_next : %%2
type : %%3
msec : %%4
number of records : %%5
current record : %%6

records data:

COS_bits_MSWORD COS_bits_LSWORD DIR_bits_MSWORD DIR_bits_LSWORD RM

------------------------------------------------------------------------------
------------
7%% 8%% 9%% 10%% 11%% 12%%

Level 2 message when there are events (in the events buffer) to read which were not read yet:

Entries 1-6 show information on the data structure that represents all first events to be read, that were
generated on the same 10 milliseconds time slice.

The next clauses illustrate the data of these events:

7. Change of state bits / Most significant word / Bit for each DI while 1=COS and 0=No COS

8. Change of state bits / Least significant word / Bit for each DI while 1=COS and 0=No COS

9. Change of state direction / Most segnificant word / Bit for each DI while 1=COS 0->1 and 0=COS 1-
>0

10. Change of state direction / Least segnificant word / Bit for each DI while 1=COS 0->1 and 0=COS 1-
>0

11. and 12. Most significant nibble - Rack, Least significant nibble - Module

## 963 LEVEL = 2
No Events to read( "read" index is NULL ).

Level 2 message when there is no event (in the events buffer) to read.

## 964 LEVEL = 255

Timer Event Diagnostic Level 255
==============================
Diagnostics level 0: Timers info and allocation problems info
Diagnostics level 1: Device key info
Diagnostics level 10: Overflow and failed allocations - view and delete.
Diagnostics level 11: Overflow and failed allocations - view.

This lists all diagnostics provided for the device at all its supported levels.

121
 Software Diagnostics Output

## 966 LEVEL = 10, 11

# of heap_aloc_buf failed : %%
Should log on heap_aloc_buf failed? : %%
Was there overflow? : %%
# of failed ack from main i/o : %%

Overflow, failed allocations, and failed communication of timer events.

STBLA

## 1020 LEVEL = 0
Version of Site-Table Downloader : %%1
The Target Unit (1-VRM-100, 5-IPGateway, 7-Moscad-M): %%2
Size of Downloaded Site Table : %%3
Size of Learning Site Table : %%4

1. The version of the site table file.

2. The target unit. (1=VRM-100 (obsolete), 5=ACE IP Gateway, 7=Moscad-M RTU)

3. The size of the Site Table downloaded from the STS to the ACE IP Gateway and used for specifying
the peers in the system.

4. The size of the learning Site Table, created during run-time and used for specifying the peers in the
system.

## 1021 LEVEL = 1
Learning Site-Table:
Site-ID Link-ID ComFal
======== ======= ======
%% %% %%

The learning Site Table, created during run-time and used for specifying the peers in the system. Includes
Site ID, Link ID, and status of the ComFal bit.

## 1022 LEVEL = 2
Downloaded Site-Table:
Site Retr Time Link Link SecLink SecLink
-ID ries out -ID -Validity -ID -Validity
==== ==== ==== ==== ========= ======= =========
%%1 %%2 %%3 %%4 %%5 %%6 %%7

The Site Table downloaded from the STS to the ACE IP Gateway and used for specifying the peers in the
system. Includes:

1. The added Site ID

2.- The number of attempts to be made to communicate with a non responding site

122
 Software Diagnostics Output

3. The time to wait between communication retries,

4.- The primary link through which the site is connected to the network,

5.- The the ACE IP Gateway tests communication with the sites on a regular basis.

If a site has not responded for a specific time interval, the primary link is considered unreachable.

6.- The secondary ((other than the Primary) link through which the site is connected to the network,

7.- The the ACE IP Gateway tests communication with the sites on a regular basis.

If a site has not responded for a specific time interval, the secondary link is considered unreachable.

POOLMNGR

## 1130
Pool address : %% 1
Pool size (in bytes) : %% 2
Pool end address : %% 3
First free chunk address : %% 4
Largest free chunk address : %% 5
Sum of all free memory : %% 6
# of times that allocation
failed (from last diag) : %% 7
Was enough space for 2 aloc : %% 8

1. The pool address.

2. The size of the whole pool.
3. Pointer to the first byte after the pool.
4. Pointer to the first free chunk. Updated only by check validity function, thus might not be free.
5. Pointer to the largest free chunk. Updated only by check validity function, thus might not be free nor
the largest one.
6. The sum size of all the free chunks.
7. The number of times that allocate failed.
8. The number of times that the function poolmngr_2_allocs_ok returned NO.

## 1131
Chunk address Chunk size Is free?
------------- ---------- --------
1 2 3

• A table of all of the chunks that were allocated in the pool (some were freed and therefore marked
free).

1. The chunk address.

2. The chunk size.
3. Whether the chunk is occupied or free.

123
 Software Diagnostics Output

## 1132
Is Check- Check-
Chunk addr Chunk size free? Bits Word
---------- ---------- ----- ----- -----
1 2 3 4 5

• A table of all of the chunks that were allocated in the pool manager (some were freed and therefore
marked free).

1. The chunk address.

2. The chunk size.
3. Whether the chunk is occupied or free.
4. Status of Check-Bits - check chunk boundaries to see if part of this chunk is overlapped by another
chunk.
5. Status of Check-Words - check chunk boundaries to see if part of this chunk is overlapped by another
chunk.

## 1140
Is pool clobbered? : %% 1

1. If Check-Bits or Check-Words are set, the validity check will report if one chunk in the pool has
overlapped another’s boundaries.

OCOMM LEVEL = 0

## 1400
ocomm key variables
--------------------------
Heap device key : %% 1
Physical device key : %% 2
Rtu to RTU station address : %% 3
Rtu to RTU system address : %% 4
Rtu to RTU Rxlo : %% 5
Rtu to RTU Rxhi : %% 5
INTRAC Rxlo : %% 6
INTRAC Rxhi : %% 6
Maximum time units for a frame to be in reception queue [sec]: %% 7
Repeater mode (Yes / No): %% 8
Control opcode to execute by transmit thread : %% 9
Answer of execution from receive thread : %% 9
Pointer to plug-in diagnostic buffer : %% 10

General: Ocomm is the module in charge of transmission and reception of wide MEIC MDLC and
INTRAC frames.

Type “OCOMM” in device name for general diagnostic.

Type “OCOMH” in device name for diagnostic of transmission heap.

124
 Software Diagnostics Output

Type “OCOMC” in device name for diagnostic of Channel Access.

1. The key to the heap from where buffers are taken for transmission.

2. The key to the physical layer that is used for transmission/reception (Adapter).

3. The Station Address of the unit in the wide MEIC MDLC network.

4. The System Address of the unit in the wide MEIC MDLC network.

5. The address range for wide MEIC MDLC frame reception.

6. The address range for INTRAC frame reception.

7. The amount of time a received frame (INTRAC or wide MEIC MDLC) can wait in the reception
queue. If the Ladder or C application does not retrieve it from there (by RxIntr function or by
RxWdth) the frame will be erased at the end of this time.

8. If Yes, then frames received by radio are transmitted to the line and vise versa.

9. The transmitting/receiving code to Piggyback used for configuration or diagnostics.

10. A pointer to the buffer received from Piggyback after being diagnosed (levels 41, 40 , 20).

## 1401 LEVEL = 1
ocomm key variables (continue)
---------------------------------------
Radio transmit queue pointer : %% 1
Radio transmit queue size [frames] : %% 2
Line transmit queue pointer : %% 3
Line transmit queue size [frames] : %% 4
Rtu to RTU reception queue pointer : %% 5
Rtu to RTU reception queue size [frames] : %% 6
INTRAC reception queue pointer : %% 7
INTRAC reception queue size [frames] : %% 8
Was RTU to RTU reception queue pulled ? (Yes / No): %% 9
Was INTRAC reception queue pulled ? (Yes / No): %% 10
Transmission state : %% 11
Will radio transmit queue be first ?(Yes / No) : %% 12
Is transmit thread at physical_transmit ( ) ? : %% 13
Is transmit thread at physical_wait ( ) ? : %% 13
Is transmit thread waiting for ack ? : %% 13
Was trunk radio configured : %% 14
Is trunk channel being warmed up with high priority ? : %% 15

1. The memory address of the radio transmission queue.

2. The number of frames in the radio transmission queue.

3. The memory address of the line transmission queue.

4. The number of frames in the line transmission queue.

5. The memory address of the wide MEIC MDLC frame reception queue.

6. The number of frames in the wide MEIC MDLC frame reception queue.

125
 Software Diagnostics Output

7. The memory address of the INTRAC frame reception queue.

8. The number of frames in the INTRAC frame reception queue.

9. Yes - The application called the RxWdth (in Ladder language)

10. Yes - The application called the RxIntr/UpIntr (in Ladder language).

11. The transmission state (to line, radio, piggyback or not at all).

12. Yes - The next time transmission will be to radio.

No - The next time transmission will be to line.

13. Waiting during transmission :

- During the transmission itself.
- Waiting for the end of transmission.
- Waiting for ACK from piggyback (while executing diagnostics or configuration)

14. If Yes, then working with trunk radio.

15. If working with trunk radio, Yes means access to trunk channel in high priority, if Low access to
trunk channel in low priority.

## 1410
The number of times the following operations were executed
LEVEL : 10 (zeros the counters after diagnostics)
LEVEL : 11 (does not zero the counters)

ocomm key error counters

--------------------------------
How many times did getting buffer fail ? : %% 1
How many times was a frame transmitted ? : %% 2
How many times did transmission fail ? : %% 3
How many times did warmup fail ? : %% 4
How many times was control frame received ? : %% 5
How many times was a frame received ? : %% 6
How many times was invalid frame received ? : %% 7
How many times was a frame with error status byte received : %% 8
How many times was a frame with invalid crc received ? : %% 9
How many times was a frame with irrelevant address received? : %% 10
How many times was received frames ignored ? : %% 11
How many times was received frames flushed ? : %% 12
How many times was transmit frame as a repeater failed : %% 13

1. The transmission was not carried out because there were no buffers in the transmission heap.

2. The number of times the frame was transmitted (to line/radio or piggyback).

3. The number of times the transmission failed.

4. The number of times warmup failed.

5. The number of times ACK (configuration/diagnostics) message or error was received from
piggyback.

6. The number of times frame was received from radio/line.

126
 Software Diagnostics Output

7. The number of times invalid frame was received from radio/line.

8. The number of received frames with hardware error.

9. The number of received frames without hardware error but with invalid CRC.

10. The number of received invalid frames with addresses out of range (which were erased).

11. The number of received frames with valid addresses that were erased, because the application did not
try to receive before that time.

12. The number of received frames with valid addresses, but were erased after timeout because the
application did not try to receive during this time.

13. The number of times the transmission of a received frame (in repeater mode) failed because the heap
was empty.

## 1420 LEVEL = 20
plug - in modem config. parameters
Pre - emphasize enable : %% 1
De - emphasize enable : %% 2
Radio channel monitor or txen polarity : %% 3
Radio indication or Rxen polarity : %% 4
Radio reception condition : %% 5
Radio gain level : %% 6
Line gain level : %% 7
Maximum received frame size : %% 8
A.g.c enable : %% 9

• FSK INTRAC Piggyback parameters :

1. Yes - Execute pre-emphasis in transmission.

2. Yes - Execute de-emphasis in reception.

3. Comm. radio - The Channel Monitor polarity; Trunk - The TxEn polarity.

4. Comm. radio - The RIND polarity; Trunk - The RxEn polarity.

5. Reception conditions :
Channel Monitor : Begin reception when C.M. active.
Tone Detect : Begin reception when there is a tone from the radio.
Channel Monitor and Tone Detect : Begin reception when both of the above occur.
(in use for regular radio).
RxEn and Tone Detect : Begin reception when there is an active RxEn and tone.
(in use for Trunk radio only)

6. Radio transmission level 0..7 (7 is maximum).

7. Line transmission level 0..7 (7 is maximum, 0 means disconnect).

8. The maximum length of a received frame. Longer frames are errors.

9. Yes - Operate AGC in reception from line.

127
 Software Diagnostics Output

## 1430
Failed to communicate with plug-in modem

A ToolBox message shown when piggyback (level 41, 40, 20) diagnostics fail. The message means that
communications with piggyback failed.

## 1431
Previous diagnostic operation to plug-in modem was not terminated - try again

A ToolBox message shown when piggyback diagnostics fail. The meaning of the message is that the
diagnostics failed (levels 20, 40, 41) because of current transmission (or access) to channel, radio or line.
Diagnostics will be allowed at the end of the current transmission.

## 1440
plug-in modem statistical information
Number of spikes received at last reception : %% 1
Total number of spikes received : %% 2
Number of illegal received frames (till 225) : %% 3

• Piggyback hardware statistics

LEVEL : 40 - Execute statistics and zero counters.
LEVEL : 41 - Execute statistics but do not zero counters.

1. The number of spikes received the last time reception was operated.

2. The total number of spikes received.

3. From piggyback version 1.2 and on, the size of the maximum transmission buffer of piggyback (up to
32 bits).

FSKADP : Channel Access to INTRAC FSK Piggyback. (The transmission of lateral

MDLC INTRAC frames to radio / line). The module is executed as a
result of transmission from OCOMM module and is found under UART.

Diagnostic operation : Operated by DEVICE NAME : OCOMM

LEVEL : 0 , 1 , 2 , 3 , 4 , 10 , 11

128
 Software Diagnostics Output

FSKADP (OCOMC)

## 1500 LEVEL = 0
Line Configuration parameters :
Override Time on busy line-channel mS : %% 1
Quiet Time on free line-channel mS : %% 2
Wait for Channel-Access Timeout Sec : %% 3
Line-channel warmup Time mS : %% 4
Transmission Timeout Sec : %% 5
Wait for Holdup Timeout Sec : %% 6
Line-channel Holdup Time mS : %% 7
Line-channel Shutup Time mS : %% 8
Current status of line :
Line-channel quiet time mS : %% 9
Line-channel busy time mS : %% 10

Line channel access parameters:

1. During transmission, if “Channel busy” is detected, this parameter will determine the waiting time (in
msec) before forcing transmission onto a channel (even if the channel is still busy). Setting this
parameter to "0", will terminate the option.
2. Quiet channel period (in msec) before transmission. Setting this parameter to "0", will terminate the
waiting time and transmission will start immediately after the "free channel" detection.
3. Maximum waiting time (in msec) for available channel for transmission. If at the end of this period,
the channel is not available, the system provides a failure notice and the transmission attempts will be
terminated.
4. Transmits a constant tone during this period (in msec), before data transmission starts.
5. The maximum time frame (in seconds) for data transmission. Transmission over this time will be
terminated, and a failure will be declared. The transmission always ends (normally or forced) with a
constant tone for holdup time.
6. During this period (in msec), the system allows the plug-in modem to transmit the contents of its
internal buffer, after the MOSCAD RTU has finished data transmission. It is not recommended to
change this parameter.
7. The amount of time (in msec) a constant tone transmission is continued after the end of transmission.
8. The minimum waiting time (in msec) between one frame transmission and the next. It is measured
from the end of the constant tone of the last transmission.
• The receiving line status:
9. The amount of quiet time on the line (msec).
10. The amount of busy time on the line, meaning Line Tone Detect is active.

129
 Software Diagnostics Output

## 1501 LEVEL = 1
Radio Configuration parameters :
Override Time on busy radio-channel mS : %% 1
Quiet Time on free radio-channel mS : %% 2
Wait for radio-channel-access Timeout Sec : %% 3
Radio-channel warmup time mS : %% 4
Transmission timeout Sec : %% 5
Wait for Holdup timeout Sec : %% 6
Radio-channel Holdup Time mS : %% 7
Radio-channel Shutup Time mS : %% 8
Radio-channel is kept busy by : %% 9
Current status of radio :
Radio-channel quiet time mS : %% 10
Radio-channel busy time mS : %% 11

• Regular radio channel access parameters:

1. During transmission, if “Channel busy” is detected, this parameter will determine the waiting time (in
msec) before forcing transmission onto a channel (even if the channel is still busy). Setting this
parameter to "0", will terminate the option.

2. Quiet channel period (in msec) before transmission. Setting this parameter to "0", will terminate the
waiting time and transmission will start immediately after the "free channel" detection.

3. Maximum waiting time (in msec) for available channel for transmission. If at the end of this period,
the channel is not available, the system provides a failure notice and the transmission attempts will be
terminated.

4. Transmits a constant tone during this period (in msec), before data transmission starts.

5. The maximum time frame (in seconds) for data transmission. Transmission over this time will be
terminated, and a failure will be declared. The transmission always ends (normally or forced) with a
constant tone for holdup time.

6. During this period (in msec), the system allows the plug-in modem to transmit the contents of its
internal buffer, after the MOSCAD RTU has finished data transmission. It is not recommended to
change this parameter.

7. The amount of time (in msec) a constant tone transmission is continued after the end of transmission.

8. The minimum waiting time (in msec) between one frame transmission and the next. It is measured
from the end of the constant tone of the last transmission.

9. To detect a busy channel:

Channel Monitor - The channel is busy when C.M. is active.
Tone Detect - The channel is busy when there is tone on the channel.

10. The amount of quiet time on the radio (msec).

11. The amount of busy time on the radio, meaning Radio Tone Detect is active.

130
 Software Diagnostics Output

## 1502 LEVEL = 2
Trunk Radio Configuration parameters :
Is trunk radio configured ? : %% 1
No trunk-channel time before requesting TxEn (Low) : %% 2
No trunk-channel time before requesting TxEn (High) : %% 3
Quiet Trunk-channel time before requesting TxEn (High) : %% 4
TxEn-request PTT active time mS : %% 5
TxEn-request PTT non-active time mS : %% 5
Wait for trunk-channel-access timeout Sec : %% 6
Warmup trunk-channel time mS : %% 7
Transmission timeout Sec : %% 8
Wait for holdup timeout Sec : %% 9
Trunk-channel holdup time mS : %% 10
Trunk-channel shutup time mS : %% 11
Current status of trunk :
Trunk-channel quiet time mS : %% 12
Trunk-channel busy time mS : %% 13
Channel does not exist time mS : %% 14
Is txen active ? : %% 15
Is PTT pressed and txen requested ? : %% 16
Time remaining for PTT pressing or reset mS : %% 17

1. YES - Trunk has been defined in configuration. Radio transmissions are via trunk.
NO - Trunk not used (regular radio transmission).

2. When the channel does not exist, this parameter determines the allotted time (in msec), to ask for
TxEn (transmit enable). This parameter is relevant if one of the functions, TxWdth or TxIntr was
called with Tx_Lnk=1 (Tx_Lnk=LoTrnk or Radio).

3. When the channel does not exist, this parameter determines the allotted time (in msec), to ask for
TxEn (transmit enable). This parameter is relevant if one of the functions, TxIntr or TxWdth was
called with Tx_Lnk=11.

4. When the channel exists and is quiet, this parameter determines the time (in msec) until asking for
TxEn (transmit enable). This parameter is relevant if one of the functions, TxWdth or TxIntr has been
called with Tx_Lnk=11 (Tx_Lnk=HiTrnk).

5. These two parameters, are used to determine the PTT active time (pressed) and PTT release time after
the transmit enable TxEn request (both in msec).

6. Maximum waiting time (in msec) for available channel for transmission. If at the end of this period,
the channel is not available, the system provides a failure notice and the transmission attempts will be
terminated.

7. Transmits a constant tone during this period (in msec), before data transmission starts.

8. The maximum time frame (in seconds) for data transmission. Transmission over this time will be
terminated, and a failure will be declared. The transmission always ends (normally or forced) with a
constant tone for holdup time.

9. During this period (in msec), the system allows the plug-in modem to transmit the contents of its
internal buffer, after the MOSCAD RTU has finished data transmission. It is not recommended to
change this parameter.

10. The amount of time (in msec) a constant tone transmission is continued after the end of transmission.

131
 Software Diagnostics Output

11. The minimum waiting time (in msec) between one frame transmission and the next. It is measured
from the end of the constant tone of the last transmission.

12. Period (in msec) during which the trunk channel was quiet (RxEn but no tone),

13. Period (in msec) during which a transmission took place in trunk (both tone and RxEn).

14. Period (msec) during which a trunk channel was not available (no RxEn).

15. Whether the CPU is pressing TxEn now.

16. Whether PTT is pressed now and TxEn requested.

17. If TxEn is requested: The time (in msec) remaining for re-pressing/releasing the PTT. If TxEn was
not requested, the value is 0.

The access to trunk channel:

• In order to begin transmission, the user should request TxEn from central unit. This is done by
pressing PTT for 4 msec. and releasing it for 5 msec. If someone else is transmitting, this request
interrupts the transmission, and therefore should be avoided.

• Access to channel is available in low priority and then the waiting time is 1 msec during which there
is no channel (RxEn is not active and no one is transmitting) until requesting TxEn (for transmitting).
If during this time someone receives permission to transmit, RxEn will become active and again the
user should wait for it to become inactive.

• Access to channel is also available in high priority and then the waiting time is either 2 msec, as
before, during which RxEn is not active until requesting TxEn, or 3 msec during which RxEn is active
and the channel is quiet (there is no Tone) before requesting TxEn.

## 1503 LEVEL = 3
Control channel Configuration parameters:
Wait for control - channel - access timeout Sec : %% 1
Warmup control - channel time mS : %% 1
Transmission timeout Sec : %% 1
Wait for holdup timeout Sec : %% 1
Holdup control - channel time mS : %% 1
Shutup control - channel time mS : %% 1
Current status of control channel : 2
Is transmission enabled : %% : %% 2

1. The piggyback control channel access parameters used for its diagnostics and configuration. The
meaning of the parameters is the same as in Line, Radio or Trunk.

The piggyback control channel current status:

2. Yes - Transmitting to the control channel is enabled.

132
 Software Diagnostics Output

## 1504 LEVEL = 4
fskadp device - current state variables
Did plug - in modem fail test ? - %% 1
Is trunk radio configured ? - %% 2
Is channel monitor LED on ? - %% 3
Is driver waiting for CTS at grant state ? - %% 4
Is task suspended on Tx_start_1 ? - %% 5
Is task suspended on Tx_start_2 ? - %% 6
Is task suspended on hc11_end_of_Tx ? - %% 7
Current module state : %% 8
Time remaining for current state mS : %% 9
Current transmitted channel : %% 10
Current accessed channel : %% 11
Current channel quiet time mS : %% 12
Current channel busy time mS : %% 13
Trunk channel status :
How long does channel not exist mS : %% 14
Is transmission enabled ? (Is TxEn Active) : %% 15
Is PTT pressed when asking for TxEn : %% 16
How much time remains for PTT pressing or reset mS : %% 17
Next warmup will be performed on channel : %% 18
Next warmup will be performed with priority : %% 19

• General parameters of FSKADP (or DEVICE OCOM) module state. Notice that parameters related to
trunking are relavant if “ Is trunk radio configured” is set to “Yes”. :

1. Yes: Piggyback failed on first test; therefore cannot be transmitted to.

2. Yes: Radio trunk was defined in configuration.

3. Yes: LED, CM3 are on. (There is reception from one of the channels).

4. Yes: Waiting for CTS from piggyback, after completing Channel Access process, in order to begin
transmitting.

5. Yes: OCOMM module is waiting in transmission until descriptor is available (TxBD).

6. Yes: OCOMM module is waiting in transmission until current transmission is over.

7. Yes: OCOMM module is waiting for end of current piggyback transmission. (UART of CPU has
finished transmitting).

8. Transmission state: Init, Grant (executing Channel Access), Warmup (transmitting Tone) and so on.

9. The amount of timeout left for current state.

10. The name of the channel that is currently being transmitted to.

11. Current channel access priority.

12. The amount of time the current channel was quiet before transmission or channel access.

13. The amount of time the current channel was busy before transmission or channel access.

14. Period (msec) during which a trunk channel was not available (no RxEn).

15. Whether the CPU is pressing TxEn now.

133
 Software Diagnostics Output

16. Whether PTT is pressed now and TxEn requested.

17. If TxEn is requested: The time (in msec) remaining for re-pressing/releasing the PTT. If TxEn was not
requested, the value is 0.

18. Next warmup will be performed on this channel.

19. Access priority of the channel that will execute Channel Access the next time. When executing
Channel Access the channel has priority. That is because the access to trunk channel can be in high or
low priority. Therefore when accessing other channels the following priorities are available: Conv.
Radio, Line , Sci (internal). When not accessing channel, this field shows “No Channel Access”.

## 1510
Transmission failure error counters
Number of times CTS signal was stuck : %% 1
Number of times channel was busy and could not be accessed : %% 2
Number of times transmission timeout occurred : %% 3
Number of times ‘Wait for Holdup’ timeout occured : %% 4

• The transmission failure statistics:

LEVEL : 10 - zero counters after diagnostics.
LEVEL : 11 - do not zero counters.

1. The number of times a channel was available for transmission (Channel Access ended successfully),
but piggyback did not enable the beginning of transmission (did not execute CTS). This can occur
because of hardware difficulties or because the transmission buffer was full for too long.

2. The number of times transmission failed because the channel was busy (Channel Access failed).

3. The number of times the transmission was stopped because it was too long.

4. The number of times the waiting for the end of piggyback modem transmission was stopped because
it took too long.

134
 Software Diagnostics Output

GPS

## 1600
GPS module parameters
Heap key : %% 1
UART key : %% 2
Update System flags function pointer : %% 3
Read Ladder time offset function pointer : %% 4
Period to Get time from GPS [sec] : %% 5
Local offset to UTS time : %% mSec.%%:%%:%%6
Local offset time at Reserved Values Table : %% mSec 7
Last PPS occurred at : %% mSec.%%:%%:%% 8
Last PPS (before GPS - frame) occurred at : %% mSec.%%:%%:%%9
Time sent from GPS : %% mSec.%%:%%:%% 10
Date sent from GPS : %%...%%:%%:%% 11
Elapsed time from last PPS when saving it : %% mSec... %%:%%:%% 12
Time that GPS frame was encoded : %% mSec... %%:%%:%% 13
Current calculated local time : %% mSec... %%:%%:%% 14
Current calculated local date : %% :%%:%% 15
Is GPS connected to MOSCAD CPU ? : %% 16
Is GPS time valid ? : %% 17
Has GPS recovered from warm - restart : %% 18

The GPS module works with the GPS receiver, configures it, receives its satellite timings and updates the
DATE & TIME table accordingly. Works above UART.

For general diagnostics : Type GPS2 in name device.

For Heap diagnostics : Type GPS2H in name device.

For Uart diagnostics : Type GPS2P in name device.

1. Pointer to the Heap key for transmission and reception.

2. Pointer to the UART key that transmits and receives with GPS.

3. Pointer to the function that updates the System Flags table.

4. Pointer to the function that returns time offset from System Values.

5. Frequency (seconds) at which GPS time is received.

6. Satellite time offset from configuration.

7. Time offset from System Values table.

8. The MOSCAD time when there is an event 1pps (every second) from GPS.

9. When a frame is received, saves the last of the 1pps event time (what was in 8).

10. The time received from GPS.

11. The date received from GPS.

12. The amount of time that passed between frame receiving event to 9 (less than a second).

135
 Software Diagnostics Output

13. When the GPS frame was encoded and calculated in local time. Because it is correct for 9, 10 is to be
added.

14. The time calculated via GPS + offset.

15. The date calculated via GPS + offset.

16. Yes : GPS is connected to MOSCAD(always defaults to no).

17. Whether the time from GPS is valid.

18. Yes : Execute Warm Restart , meaning reconfigure GPS.

## 1601 LEVEL = 1
Current RTU Time
-----------------
Time in TICKS register : %% : %% : %% 1
Date in TICKS register : %% : %% : %% 2
Time in Real time Clock : %% : %% : %% 3
Date in Real time Clock : %% : %% : %% 4
Time in GPS receiver : %% : %% : %% 5
Date in GPS receiver : %% : %% : %% 6
Is GPS connected to MOSCAD CPU ? : %% 7
Is GPS time valid ? : %% 8
Number of visible sattelites (M12 only) : %%9
Number of tracked sattelites (M12 only) : %%10
Last GPS status read : %%11
Time that GPS has invalid status [seconds]: %%12
PPS Low pulse interval in micorsec : %%13
PPS high pulse interval in micorsec : %%14
Max PPS low pulse interval in micorsec : %%15
Max PPS high pulse interval in micorsec : %%16
Last NMEA0183 frame recevied : %%17

• The current GPS and MOSCAD times:

1. The MOSCAD time (updated only if clocks have been updated or the update is from GPS).

2. The MOSCAD date.

3. The time in RTC (updated from ToolBox , GPS).

4. The date in RTC.

5. Time that was received from GPS.

6. Date that was received from GPS.

7. Yes : GPS is connected to MOSCAD (See 9)

This is the flag that is set to YES whenever there is a 1pps interrupt from GPS. Subsequently
MOSCAD changes it to NO in order to diagnose whether GPS disconnected. If receiving reception
timeout of 2 sec and this flag is NO, the system knows that the GPS has been disconnected and will
wait for reconnection, and then it will reconfigure it. If a timeout occurred and the flag is set to YES,
GPS is connected and therefore will try to receive again. Therefore this flag varies according to
system needs and does not really indicate whether GPS is connected or not.

136
 Software Diagnostics Output

8. Whether GPS time is valid.

9. The number of satellites the M12 GPS receiver can see.

10. The number of satellites the M12 GPS receiver is tracking.

11. The last status read from the GPS receiver.

12. The number of seconds that the GPS receiver had an invalid status.

13. -14. The current low/high intervals of PPS signals in microseconds.

15-16. The maximum low/high intervals of PPS signals in microseconds.

17. The last frame/string received when GPS port is configured for an NMEA 0183 GPS receiver (such as
Garmin 16X). and user specify GPS connection to "NMEA0183" in port user screen. If empty, GPS
receiver is not connected, or not powered on, or the baud rate setting is wrong.

## 1602 LEVEL = 2
%%1

1. GPS Receiver ID

## 1610
GPS statistical information
How many 2 seconds timeout occurred during reception ? : %% 1
How many valid frames were received : %% 2
Number of invalid frames received (total) : %% 3
Number of received frames that got timeout in the middle : %% 4
Number of received frames with size less than 4 chars : %% 5
Number of received frames that got invalid 2 prefix bytes : %% 6
Number of received frames that got invalid 2 opcode bytes : %% 7
Number of received frames with length more than required : %% 8
Number of received frames that got invalid 2 suffix bytes : %% 9
Number of received frames that got invalid checksum : %% 10
Number of frames that were handled long time after pps : %% 11
How many valid frames were received with error status byte ? : %% 12

• The GPS module statistics:

LEVEL : 10 - zeroes counters after statistics
LEVEL : 11 -does not zero counters

1. The number of two second timeouts during which no frame was received from GPS.
2. The number of times a valid frame was received from GPS.
3. The number of times an invalid frame was received from GPS.
4. The number of times a timeout was received during reception of a frame.
5. The number of times the frame was too short.
6. The number of times the frame had an invalid prefix.

137
 Software Diagnostics Output

7. The number of frames that had an invalid opcode.

8. The number of frames that were too long.
9. The number of frames that had an invalid suffix.
10. The number of frames that had an invalid checksum.
11. The number of frames that were received after their 1pps time (more than a second).
12. The number of frames that were supposedly valid, but their status determined that they were not
satellite times.

## 1611 LEVEL = 255

GPS levels:
-----------
0- Get parameters
1- Get state
2- Get GPS receiver ID
10-Get & clear statistics
11-Get statistics

This lists all diagnostics provided for the device at all its supported levels.

CAPPL (IRRInet-M/MOSCAD-M)

## 1650 LEVEL = 0
The ‘C’ application Block ID : %% 1
The address of our jump-table to access the aplic : %% 2
Number of ‘C’ blocks in the flash (chain) : %% 3
Number of relevant ‘C’ blocks : %% 4
Number of expected ‘C’ functions : %% 5
Number of found ‘C’ functions : %% 6

1. The block number that is designed for programming the ‘C’ application, in this case 10. For every
type of item that is programmed into the site there is a set block ID.
2. The address of the Jumptable that coordinates between the ‘C’ application and the system services in
the RTU. The purpose of the Jumptable is to enable linkage during Runtime.
3. The number of ‘C’ blocks currently found in the flash.
4. The number of active ‘C’ blocks currently found in the flash.
5. The number of functions expected by the Ladder.
6. The number of functions that are currently found and with them linkage was executed in Runtime.

138
 Software Diagnostics Output

## 1651 LEVEL = 1
Expected Functions.
Func Func
Index Name
------ -----

• The list of functions expected by the Ladder and their names, as they appear in the flash after
download of the Ladder and/or C block.

## 1652 LEVEL = 2
List of the relevant blocks (starting from 1)
Block Num RAM Address
---------- ------------

• The list of the active blocks in the flash and their RAM addresses (all globals and statics).

## 1653 LEVEL = 3
Func Block Block Block Func
Addr RAM RAM Size Number Name
----- ----- -------- ------ -----

• The list of functions, their address in flash, the Block RAM beginning address, its size in RAM, the
block number and their names.

• In case the function is not found then it points to an empty function address in the system and is
marked block = 0. These values are useful when debugging the application.

## 1654 LEVEL = 4
Block Block Block Block Block User RAM RAM Lib
Cntr Ver Status Address len JT Size Address JT
----- ----- ------ ------- ----- ---- ---- ------- ---

• The list of all the blocks in flash (either active or not), the version of the block, the status of block
(active or not), the address of the block, and length of the block, (the size of the whole block without
the header). the address of the user’s Jumptable, and the amount of RAM needed by the block, address
of RAM needed and address of the library (system) Jumptable.

## 1655 LEVEL = 5
Func Block Func
Addr RAM Name
----- ------ ----

• The list of all of the functions expected by the Ladder including the memory address and the RAM
beginning address for each function. The global static variables are relative to the RAM beginning
address.

139
 Software Diagnostics Output

C APPLICATION TIMERS DEVICE = CD_10, CD_100

## 1680 LEVEL = 0
Index Value Alloc? Run?
----- ----- ------ -----

Displays all of the ‘C’ application 10/100 millisecond timers available to the user.

Value The current value of the timer in the units of the timer

Alloc Whether the timer is allocated.

Run Whether the timer is in use (started).

This information relates to the STS C Application Advanced Parameters Number of ’10 ms’ timers for
‘C’ applications and Number of ’100 ms’ timers for ‘C’ applications.

SFLASH (CPU 400 and above only)

## 1730 LEVEL = 0
Start of SFlash : %% 1
Last Flash address : %% 2
Num of segments : %% 3
Num of regions : %% 4
Max Prog Wait (mics) : %% 5
Max Erase Wait (mics) : %% 6
Max Suspend Time (mics): %% 7
Max Erase Time Secs : %% 8
Max Prog Time (mics) : %% 9

1. Start address of flash memory (CPU 400 - system and user, CPU420 User only).

2. Last address of Sflash.

3. Number of Segments.

4. Number of Regions.

5. Maximum time (# of microseconds) to wait until the flash memory is programmed.

6. Maximum time (# of microseconds) to wait until the flash memory is erased.

7. Maximum time (# of microseconds) to suspend the task which programs the flash memory.

8. Maximum time (# of seconds) required to erase the flash memory.

9. Maximum time (# of microseconds) required to program the flash memory.

140
 Software Diagnostics Output

## 1731 LEVEL = 1
Num of segments: %%
Start_Seg End_Seg Region Boot?

For all segments:

• Beginning address of the segment.

• End of segment (last address)

• In what region is the segment? (System region is 0 and User region is 1 - MOSCAD only).

• Is segment used for boot purposes or not?

## 1732 LEVEL = 2
Num of Regions: %% Chip Information
Num_ Chip_ Elt_ ID_ ID_
Chips Width Size Manu Dvc

For system software developers only.

## 1733 LEVEL = 3
Num of regions: %% Routines in RAM:
Erase Program Read_ID Busy_Wait_Micro

For system software developers only.

141
 Software Diagnostics Output

GAUART DEVICE = COMxA, RTUxA, LINxA

## 2020 LEVEL = 0
GAUart 's Hardware Internal Registers :-
------------------------------------------
Internal software data (key) (DATA) : %% 1
General Status Register (GSR) : %% 2
General reset Register (GRR) : %% 3
Events Register (ER) : %% 4
Events Mask Register (EMR) : %% 5
Max idles Register (MX_IDL) : %% 6
Close Character : %% 7
baud rate read register low (BRR_L) : %% 8
baud rate read regiaster high (BRR_H) : %% 9
Mode register (MR) : %% 10
control 1 register (CC1) : %% 11
control 2 register (CC2) : %% 12
external pins register : %% 13
Receive Ready control Register(RR_x) : %% 14
Receive Status control Registe(RS_x) : %% 15
transmit control register (TC_x) : %% 16
Receive Ready control Register(RR_x) : %% 17
Receive Status control Registe(RS_x) : %% 18
transmit control register (TC_x) : %% 19

1. Device key.

2. General Status Register.

3. General reset Register.

4. Events Register.

5. Events Mask Register.

6. Max idles Register.

7. Close Character

8. Read register containing baud rate (low byte)

9. Read register containing baud rate (high byte)

10. Mode register.

11. Control 1 register.

12. Control 2 register.

13. External pins register.

14. Receive Ready control Register (1st buffer).

15. Receive Status control Register (1st buffer).

16. Transmit control bits (1st buffer).

142
 Software Diagnostics Output

17. Receive Ready control Register (2nd buffer).

18. Receive Status control Register (2nd buffer).

19. Transmit control bits (2nd buffer).

## 2021 LEVEL = 1
GAUART's Software descriptors :-
--------------------------------------
Head (offset) software receive descriptor: %% 1
tail (offset) software receive descriptor: %% 2
Head (offset) software transmit descriptor: %% 3
tail (offset) software transmit descriptor: %% 4
empty software receive descriptor: %% 5
ready software receive descriptor: %% 6
empty software transmit descriptor: %% 7
ready software transmit descriptor: %% 8

1. Where the processor will leave the next received data.

2. Where the software will take the next received data.

3. Where the software will leave the next data to be transmitted.

4. Where the processor will take the next data to be transmitted.

5. Number of empty software receive descriptors

6. Number of full software receive descriptors ready to be emptied.

7. Number of empty software transmit descriptors

8. Number of full software transmit descriptors ready to be emptied.

143
 Software Diagnostics Output

## 2022 LEVEL = 2
GAUART's Internal RAM data-Device Key :-
------------------------------------------
Current mode parameters (MODE_BACKUP): %% 1
Current rate parameters (RATE_BACKUP): %% 2
Current sync parameters (SYNC_BACKUP): %% 3
Address mask parameters (MASK_BACKUP): %% 4
Address data parameters (ADRS_BACKUP): %% %% %% %% 5
Current channel's name (CHAN_BACKUP): %% 6
Current channel's data (CHAN_DATA) : %% 7
Current channel's code (CHAN_CODE) : %% 8
Current heap's name (HEAP_BACKUP): %% 9
Current heap's name (HEAP_DATA) : %% 10
Current heap's data (HEAP_CODE) : %% 11
Current channel's port (GAUART_PORT): %% 12
Reception data lock (RXBD_LOCK) : %% 13
Transmission data lock (TXBD_LOCK) : %% 14
Reception data head (RXBD_HEAD) : %% 15
Transmission data tail (TXBD_TAIL) : %% 16
Communication signals (GAUART_SIGNAL): %% 17
Communication buffers (GAUART_TYPE) : %% %% 18
Communication uart lock (GAUART_LOCK) : %% 19
Communication time lock (TIME_LOCK) : %% 20
Communication time data (TIME_DATA) : %% 21
Communication status (NOISY): %% 22
(QUIET): %% 23
Communication preset/timers (GRANT): %% %% 24
(QUIET): %% %% 25

1. Current working mode of the channel (synchronous, asynchronous, DTE, DCE).

2. Communication baud rate.

3. Current synchronization character.

4. Not relevant.

5. The addresses to which this site will respond through this port.

6. Channel access name.

7. Current channel's device.

8. Current channel's pin table.

9. Heap name.

10. Heap device key.

11. Heap pin table.

12. The port number.

13. Semaphore of the reception function.

14. Semaphore of the transmission function.

15. Offset for Rx descriptors for receiving frame.

144
 Software Diagnostics Output

16. Offset for Tx descriptors for transmitting frame .

17. MTE signal of conditions that were met.

18. Whether the frame is formatted or unformatted.

19. Device semaphore.

20. Not in use.

21. Coded time stamp of last received frame (in ticks)

22. Current counter of noise.

23. Current counter of quiet.

24. GRANT-TIME for channel access: The time the site will wait to obtain a transmission channel until it
decides that a channel is not available.

25. QUIET-TIME after transmission: The time to wait before a retry.

## 2040 LEVEL = 0
Index Name Pointer
----- ----- -------

All saved names and pointers to blocks used until now. The names are created with the function
MOSCAD_bind_name()and pointers are created with MOSCAD_get_named_ptr() for the purpose of
keeping historical data on the block.

SITTBL

## 2060 LEVEL = 0
Dynamic Site-Table :
Index ID Link ComFal
----- ---- ---- ------

The Dynamic Site Table as determined by C functions such as init_site_table(), new_site_table(), and
Set_site_table(). Includes Site ID, Link ID, and status of the ComFal bit.

## 2061 LEVEL = 1
Static Site-Table :
Index ID Link ComFal
----- ---- ---- ------

The Site Table as defined in the Ladder of the Application Programmer. Includes Site ID, Link ID, and
status of the ComFal bit.

145
 Software Diagnostics Output

PTRMNG

## 2080 LEVEL = 0
Index Set In-Use In-Process Pointer
----- ---- ------ ---------- -------

Details for each of the master channels the following information:

Set Is this channel set in channels table

In-Use Is this channel in use

In-Process Is communication/process in progress

Pointer The channel device key in RAM

DCFi (for ‘C’ applications only)

## 2100 LEVEL = 0
Number of entries in the function table: %% 1

Address

1. The number of entries in the function table corresponds to the number of functions allocated for
this DCF device. This corresponds to the advanced parameter set in the Site Configuration (e.g.
Number of diagnostics functions for ‘C’ application for DCF6.)

Address The starting address of this DCF function table.

For each DCFi device used (where i = 1-9), a separate function table exists.

## 2101 LEVEL = 1
Index Func RAM Ptr Pres-Key ID Lock In-Use Stop
----- ---- --- --- -------- -- ---- ------ ----

Index The index into the function table.

Func The function address.

RAM The RAM address of the block to which the function is linked.

Ptr The user pointer.

Pres-Key The Presentation Device key (internal system structure.)

ID The function ID.

Lock An indication if this Table Entry has been locked for use or modification.

In-Use Is this entry in the function table in use?

146
 Software Diagnostics Output

Stop Use Indication: If this entry is to be removed, then stop calling the function. If the function
is not going to be removed, then it can continue be called (concerning the MOSCAD_set...
and MOSCAD_unset... for each of the DCF's functions.)

This table contains an entry for each function allocated for the DCFi device (where i = 1-9).

If the user application calls MOSCAD_set_diag_func(), user defined diagnostics can be viewed for the
DCF6 device, generally at Levels 20-50. For more information, see the “Calling User Functions from the
MOSCAD Family System” chapter of the ‘C’ Toolkit for MOSCAD Family RTUs User Guide.

IPLINK LINxL

## 2200 LEVEL = 0
Iplink device key
--------------------
Heap key : %% 1
Network key : %% 2
Network pin table : %% 3
Site ID : %% 4
Link ID : %% 5
IP port number : %% 6
IP address : %% 7
Enable RCP : %% 8
Port is in Fail : %% 9
Group IP address : %% 10
All RTU Simulation: %% 11
Enable IPModem : %% 12
Learn IP Address : %% 13
Check failed sites : %%14
Max echoes to send : %%15
Max sec between echoes: %%16
Max sec to check alive: %%17
Is GetSiteName exist : %%18
Enable time sync6 : %%19
Enable check sites : %%20
Ignore broadcasts : %%21
Parent Site ID : %%22
Enable Route : %% 23
Enable Multi-Link : %% 24
Interface name : %% 25
Is Get host by name enabled : %% 26
Notify my IP adddress : %% 27
Notify private site IDs : %% 28

When Port is defined as MDLC Over IP (Astro, iDEN,Tetra, Terminal server or Standard Modem).

1. General Heap key for transmission and reception.

2. Network layer in the unit.

3. A pointer which allows “cabling” between two devices during run time.
147
 Software Diagnostics Output

4. Site ID.

5. Link ID.

6. Number of the IP Port as defined in Site Configuration.

7. IP Address as defined in Site Configuration.

8. Enable RCP- Yes or No

9. Status of Link.

10. IP address used for Group Call as defined in Site Configuration.

11. YES if the Addr. range response for 'All RTU simulation' (Network Layer Advanced Parameter) was
set to non zero.

12. YES if connected to iDEN.

13. YES if the port’s IP address will be retrieved during run time, e.g. from the iDEN modem.

14. YES if the sites that are failed will be checked before transmitting to them. If the site does not reply,
transmissions will be routed to an alternative path (if such exists.) A site is considered failed when
transmission to it results in an ICMP:Dest Unreach error message, or when the ‘check alive’ test fails.
Use of this parameter makes MLDC over IP more reliable when transmitting to failed sites.

15. If ‘Check failed sites’ is YES, this specifies the number of retries of the ‘check alive’ test to the failed
site, before the message is routed to an alternative path (if such exists) and asserting that it is still
failed.

16. If ‘Check failed sites’ is YES, this specifies the timeout in seconds between retries of the ‘check
alive’ test.

17. If ‘Check failed sites’ is YES, this specifies the timeout in seconds in which no message was received
from a site before declaring it as unknown. Any new transmission to the site will first cause a ‘check
alive’ test as explained above. This parameter is extends the ‘check alive’ test to sites which are not
failed, but have been idle for some time. If this parameter is set to 0, no ‘check alive’ test will be
performed for idle sites.

18. Not relevant.

19. Not relevant.

20. YES if sites paging enabled.

21. If YES, incoming broadcasts will be ignored.

22. Relevant for IP Interface. If not 0, it is the parent RTU's Site ID.

23. If YES, enables routing on MDLC over IP port. This parameter if enabled from Advanced link
parameter of port can route back messages if destined to a different site that appears in ip conversion
table. Useful with ASTRO IV&D or RTUs with dynamic addresses that require RTU to RTU
communication via a fixed address RTU.

24. If YES, provides multiplexing of several MDLC link IDs via one physical IP address.

148
 Software Diagnostics Output

25. Name of port/interface in RTU. Unlike MOSCAD where only one IP port is used, this can help
identify on which port these link IDs operate.

26. YES, if for the specified link ID the user enabled ‘get host by name’, i.e. support for domain names in
the IP conversion table. This can be enabled in advanced link parameters of the port configuration.

27. If YES, notifies my IP address when power up, download an IP conversion table, change IP address,
or when RTU becomes active. The message is sent with my public (common) site ID. but no IP
address, as the IP layer specifies the IP address.

28. If YES, and the Addr. range response for 'All RTU simulation' advanced Network parameter is non 0
(one or more private site IDs exist), then when sending the IP address notification, send along my
private site IDs. For example, if Addr. range response for 'All RTU simulation' = 2, then notify my
site ID + 1 and my site ID +2. Up to 5 private site IDs can be sent.

## 2201 LEVEL = 1
Iplink socket status
---------------------
Socket number : %%
Socket state : %%
Socket timeout : %%
Socket open latest result : %%
Socket send latest result : %%
Socket recv latest result : %%

Status of the socket on the link. For system software developers only.

## 2202 LEVEL = 2
Iplink status
--------------------------
Queue size : %%1
Is transmission thread waits for new buffer : %%2
If transmission thread waits for socket to be opened : %%3
Is transmission thread waits for socket to transmit data : %%4
Is reception thread waits for socket to received new data : %%5
Last transmitted site ID : %%6
Last transmitted IP address : %%7
Last received site ID : %%8
Last received IP address : %%9
Last site ID used when calling getsitename() : %%10
Last site name retreived from getsitename() : %%11
Last IP Address retrieved when calling gethostname() : %%12
Is Conversion Table locked : %%13
Task name locking conversion table : %%14
Last transmitted IP Port : %%15
Last received IP Port : %%16
Last dest link ID transmitted to : %%17
Last source link ID received from : %%18
Is CPU in standby mode ? : %%19

1. Number of frames awaiting transmission.

2. Not relevant.

149
 Software Diagnostics Output

3. Not relevant.

4. Not relevant.

5. Not relevant.

6. Last Site ID to which the RTU transmitted.

7. Last IP address (and the UDP port number for ACE) to which the RTU transmitted.

8. Last Site ID from which the RTU received transmission.

9. Last IP address (and the UDP port number for ACE) from which the RTU received transmission.

10. Not relevant.

11. Not relevant.

12. Not relevant.

13. Not relevant.

14. Not relevant.

15. With firmware ≥ V9.24, the UDP port number can be learned upon reception from each site. In
earlier versions only the IP Address is learned. This diagnostic shows the last transmitted site ID
(field 6) IP address (field 7) and its UDP port number (this field).

16. With firmware ≥ V9.24, the UDP port number can be learned upon reception from each site. In
earlier versions only the IP Address is learned. This diagnostic shows the last received site ID (field
8) IP address (field 9) and its UDP port number (this field). When the RTU replies to this site, it will
use this IP Address and UDP port number.

17. ACE can support multiple link IDs on the same physical port. This shows the last Link ID
transmitted.

18. ACE can support multiple link IDs on the same physical port. This shows the last Link ID received.

19. YES if the CPU is inactive (standby). Only a CPU 3680 can be inactive, and only if the peer CPU is
active.
Also YES if the user clears the DisCom bit in Reserved Flags table. In this mode, the CPU is able to
reply only to its private site ID (if specified in response upto), and ignore frames destined for its
public/common site ID. Note that if Addr. range response for 'All RTU simulation' = 0), then it cannot
communicate.

150
 Software Diagnostics Output

## 2203 LEVEL = 3
Iplink conversion table for ALL Link IDs
--------------------------------
Maximum entries allowed : 200
Number of actual entries : 2
Internal pointer of Table Header : 0x1976b40
Internal pointer of Table Entries : 0x1976bb0

Num. Echo Echo Ave Fail Check UDP

Site Link ID IP-address Status Fail Sent Rply Delay [Sec] Hint in [Sec] Port Name
---- ------- ------------ ------ ---- ---- ---- ----- ----- ---- -------- ---- ----
550 21 145.9.199.26 Ok 0 0 0 0 0 44H 0 27 -- --
65534 21 10.108.3.11 -- 0 0 0 0 0 40H 0 0 2002 --

Iplink conversion table

------------------------
Maximum entries allowed : %%1
Number of actual entries : %%2
Next entry for setcall : %%3
I was inactive when last notified my IP : %%4
Notify IP address changes on other link IDs: %%5

Num Echo Echo Ave Fail Check UDP

Site Link-ID IP-address Status Fail Sent Rply Delay [sec] Hint In [Sec] Port Name
---- ---- ---------- ------ ---- ---- ----- ------ ----- ---- -------- ---- ----

1. Maximum number of entries allowed in IP Conversion Table.

2. Actual number of entries in IP Conversion Table.

3. Not relevant.

4. YES if CPU became inactive, when last notified IP address. If ‘Notify My IP address’ is YES,
response up to is non 0, and the CPU was inactive when sending out ‘Notify my IP’ it will send out
with my private sites. If response upto is 0 then no message is sent during power up, address change,
or download of IP conversion Table.

5. (V15.50 or higher) This reflects whether to notify of IP address changes from other links (ports). The
notification is sent as a setcall. See the ACE3600 STS Advanced Features manual for more on
setcalls.

The contents of the IP Conversion Table is provided:

• Site ID

• Link ID – In ACE3600 RTUs, each entry in the IP conversion table has a link id designating its
physical port. There can be several link IDs per RTU, with different IP addresses, or with the same IP
address.

• IP Address

• Site Status OK/Fail/-- (Unknown) OK means the site is OK. Fail means that either a site
page failed or a transmission failed. -- means unknown.

• Number Failed Number of times site has become failed (either from OK or Unknown state).

• Echo Send Number of polls sent to site during check alive test or page.

151
 Software Diagnostics Output

• Reply Received Number of polls (pages) replied to by the site.

• Average Delay Average delay when transmitting to a site. Each poll bears the site timestamp.
When the site replies, an average delay is recalculated. The average depends on how many echoes
were sent.

• Failed Time[sec] Time in seconds from which the site was first declared as failed.

• Hint Not relevant.

• Check In If in the middle of paging, specifies how many echoes are left to check and when the next
one will be sent in seconds.

• UDP Port Shows the UDP Port number for the site. If -- it is the configured MDLC UDP port number
as in## 2200.

• Name – Displays the site full host name as specified in the IP conversion table (appears only if the
“get host by name” parameter was enabled for the specified link in advanced link configuration.)

In MOSCAD >= V9.24, level 30 for this diagnostic clears the statistics information display in the IPLink
Conversion Table (level 3.)

## 2204 LEVEL = 3
Displays the contents of each row in## 2203.

152
 Software Diagnostics Output

## 2210 LEVEL = 10, 11

Iplink statistics
------------------
Number of times re-opened socket : %%1
Number of times transmitted successfully : %%2
Number of times failed transmission : %%3
Number of times failed get IP address before transmitting : %%4
Number of times failed set IP address after receiving : %%5
Number of times failed get buffer from heap : %%6
Number of times received a frame successfully : %%7
Number of times failed reception : %%8
Number of times received irrelevant frame : %%9
Number of times failed handle received control frame : %%10
Number of times failed handled received data frame : %%11
Number of times port has become failed : %%12
Number of times port has recovered : %%13
Error when failed pushing received datagram to network : %%14
Number of times tried a loop transmission : %%15
Number of ICMP:Host Unreach messages received : %%16
Last destination Site ID that caused ICMP:Host Unreachable: %%17
Number of unknown frames received from peer MOSCAD sites : %%18
Last MOSCAD site ID that sent an unknown frame : %%19
Number of times failed transmission because of full queue : %%20
Number of times transmitted sync frame : %%21
Number of times received sync frame : %%22
Number of times transmitted to non OK sites : %%23
Number of bytes transmitted : %%24
Number of bytes received : %%25
Number of echo rqst frames sent to other peer MOSCAD sites : %%26
Last MOSCAD site ID that sent an echo request to : %%27
Number of echo rply frames received from peer MOSCAD sites : %%28
Last MOSCAD site ID that sent an echo reply frame : %%29
Number of times failed obtain gethostbyname : %%30
Number of times got setip frame : %%31
Number of times got getip request : %%32
Number of times failed reply to getip request : %%33
Number of times sent setip frame : %%34
Number of times replied to sync frames : %%35
Number of times sent control frame : %%36
Number of times received control frame : %%37
Number of times sent routed frame : %%38
Number of times received routed frame : %%39
Number of times failed socket transmit : %%40
Last MOSCAD site and link ID that failed socket transmit : %%41
Last destination IP address that failed socket transmit : %%42
Number of times sent a frame to a site with an expired IP : %%43
Last expired MOSCAD site and link ID that transmitted : %%44
Last IP address of expired MOSCAD that transmitted : %%45
Number of received frames ignored because being inactive : %%46
Number of transmission ignored because being inactive : %%47
Number of times became inactive : %%48
Number of times became active : %%49

1. Not relevant.

2. Number of successful transmissions.

3. Number of failed transmissions.

153
 Software Diagnostics Output

4. Not relevant.

5. Not relevant.

6. Not relevant.

7. Not relevant.

8. Number of time reception failed – invalid MDLC file.

9. Not relevant.

10. Number of times that a radio control frame could not be processed (Astro Spectra only).

11. Number of times that a radio data frame could not be sent to the network, usually because the network
is busy (Astro Spectra only).

12. Number of times the port went into failed mode.

13. Number of times the port recovered from failed mode.

14. Reason for failure to push received radio data frame to network (as in 11 above.)

15. Number of times transmission was attempted to a destination site with the same IP address as the
RTU. As a result, transmission failed.

16. Number of times an ICMP:Host Unreachable message was received after transmission. As a result,
destination site has become failed.

17. Last Site ID to become failed because of an ICMP:Host Unreachable message.

18. Number of valid MDLC frames received from peer MOSCAD sites that could not be processed by the
RTU. This is because of an MDLC version mismatch. The message has been reported back to the
peer site.

19. Last peer Site ID to have sent a message that could not be processed. The message has been reported
back to the peer site.

20. The number of times that transmission failed because the queue was full. This prevents over-
consuming MDLC heap resources when transmitting large blocks of data.

21. The number of times that synchronization was transmitted to all sites.

22. The number of times that synchronization was received.

23. The number of times that data was transmitted to a site which is either failed or its status is currently
unknown. Usually a site like this is polled before transmitting, but in order to free heap resources,
data was transmitted to it and may have been lost. (relevant only when Check failed sites is set to
YES in #2200 parameter 17)

24. Number of bytes transmitted. (includes both 2 and 26)

25. Number of bytes received. (includes both 7 and 28)

26. Number of polls sent to other sites. (includes both 2 and 24)

154
 Software Diagnostics Output

27. Site ID of the last MOSCAD that was polled.

28. Number of replies received. (includes both 7 and 25)

29. Site ID of the last MOSCAD that replied to a poll request.

30. Not relevant.

31. The number of times a SETIP control frame was received.

32. Not relevant.

33. Not relevant.

34. Number of times sent SETIP control frame. This is issued when RTU notifies all sites in the IP
Conversion Table of the IP address for the modem/radio.

35. Not relevant.

36. Number of control frames (such as SETIP, Echo request and Reply) that were sent.

37. Number of control frames received.

38. Number of routed frames sent.

39. Number of routed frames received.

40. Number of failed socket transmits.

41. The last RTU site ID and link ID whose socket transmit failed.

42. The last destination IP address whose socket transmit failed.

43. The number of times a frame was sent to a site whose IP has expired.

44. The site ID and link ID of last RTU whose IP has expired that transmitted.

45. The IP address of the last RTU whose IP has expired that transmitted.

46. The number of frames received on this port that were destined to this site ID, but were ignored
because this CPU was inactive.

47. The number of transmissions that were not sent because they originated from the public/common site
ID, and this CPU is inactive.

48. The number of times the RTU became inactive. The RTU becomes inactive when there is dual CPU
and the peer CPU is active, or when the user clears the DisCom bit in reserved flags table.

49. The number of times the RTU became active. The RTU inactive state is cleared when there is dual
CPU and the peer CPU is inactive, or when the user sets the DisCom bit in reserved flags table.

155
 Software Diagnostics Output

SLIP LINxSlp

## 2300 LEVEL = 0
Slip/ppp port parameters
---------------------
formater key : %%1
port mode : %%2
port rate : %%3
port from : %%4
port flow control : %%5
Is device down : %%6
Is char being received : %%7
Is driver wait during transmission: %%8
Char that is being received : %%9
Has device went up ? : %% 10
Is driver being stopped ? : %% 11
Is reception from port being held? : %% 12
Is driver PPP ? : %%13
Maximal no reception time to declare disconnect [sec]: %%14
Time elapsed since last Slip/PPP reception [sec] : %%15
Is driver being stopped : %%16
Is driver being started/connected : %%17
Last error when started driver (HEX) : %%18
Is disconnected driver on ? : %%19
Was AT response been received when driver was up ? : %%20
Send optional String : %%21
Is slip/ppp freezed ? : %%22

1. Not relevant.

2. Not relevant.

3. Baud rate of port, as defined in Site Configuration.

4. Not relevant.

5. Type of flow control (DTR/CTS) as defined in Site Configuration.

6. Not relevant.

7. Not relevant.

8. Not relevant.

9. Not relevant.

10. Has the SLIP device been activated?

11. Is transmission of IP datagrams through SLIP device currently paused?

12. Is reception of IP datagrams through SLIP device currently paused?

Note: 11 and 12 are YES when initializing modem (e.g. iDEN) using AT commands.

13. YES if driver is PPP; NO if it is SLIP.

156
 Software Diagnostics Output

14. Timeout in seconds in which no data was received and disconnecting/reactivating SLIP/PPP.

15. Time elapsed in seconds since the last received SLIP/PPP data from port.

16. Is PPP/SLIP driver in the process of being disconnected?

17. Is PPP/SLIP driver in the process of being connected?

18. Not relevant.

19. Not relevant.

20. Was an AT response noted when receiving data in SLIP/PPP mode? An AT response can be
ERROR, +CME ERROR, AT, ATH, etc. It indicates that the modem has moved to command mode
and therefore the driver needs to be disconnected.

21. Not relevant.

22. Not relevant.

## 2301 LEVEL = 1
PPP Status
---------------
LCP Layer Status: %%1
IPCP Layer Status: %%2
PAP Layer Status: %%3
CHAP Layer Status: %%4

PPP State
---------------
LCP Layer State: %%5
IPCP Layer State: %%6
PAP Layer State: %%7
CHAP Layer State: %%8

Terminate Configure Failure

--------- --------- -------
LCP Layer Retry: %%9 %%9 %%9
IPCP Layer Retry: %%10 %%10 %%10
PAP Layer Retry: %%11 %%11 %%11
CHAP Layer Retry: %%12 %%12 %%12

PPP Configuration My Their Negotiated

----------------- ------------ -------------- ----------
Asyncctl : %%13
Magic : %%14
Maxmtu : %%15
Auth protocol: %%16
Quality protocol: %%17
Protocol comp. : %%18
Address comp. : %%19
IP Address : %%20
Tcp Compressio : %%21
Tcp Comp Max slot: %%22
Tcp Comp slot : %%23

1. Status of LCP layer (up or down).

157
 Software Diagnostics Output

2. Status of IPCP layer (up or down).

3. Status of PAP layer (up or down).

4. Status of CHAP layer (up or down).

5. Not relevant.

6. Not relevant.

7. Not relevant.

8. Not relevant.

9. Number of retries to terminate or configure the LCP layer.

10. Number of retries to terminate or configure the IPCP layer.

11. Number of retries to terminate or configure the PAP layer.

12. Number of retries to terminate or configure the CHAP layer.

13. PPP Async option of myself/peer and negotiated one.

14. PPP Magic option of myself/peer and negotiated one.

15. PPP Authentication protocol option of myself/peer and negotiated one.

16. PPP Protocol compression option of myself/peer and negotiated one. 1 if this is required.

17. PPP Address compression option of myself/peer and negotiated one. 1 if this is required.

18. IP Address option of myself, peer, and negotiated one.

19. TCP header compression protocol of myself, peer and negotiated one.

20. TCP header compression maximal slot of myself, peer and negotiated one.

21. TCP header compression slot of myself, peer and negotiated one.

158
 Software Diagnostics Output

## 2302 LEVEL = 2
PPP log information
-------------------
Last protocol received : %%1
LCP protocol received : %%2
LCP code received : %%3
LCP id received : %%4
LCP message length : %%5
LCP message received : %%6
Time received last LCP : %%7
Number of Nak received : %%8
Number of Rej received : %%9

IPCP protocol received : %%10

IPCP protocol received : %%11
IPCP code received : %%12
IPCP id received : %%13
IPCP message length : %%14
IPCP message received : %%15
Time received last IPCP: %%16
Number of Nak received : %%17

PAP protocol received : %%18

PAP code received : %%19
PAP id received : %%20
PAP message length : %%21
PAP message received : %%22
Time received last PAP: %%23

CHAP protocol received : %%24

CHAP code received : %%25
CHAP id received : %%26
CHAP message length : %%27
CHAP message received : %%28
Time received last CHAP: %%29
Number of 'Success' code : %%30
Number of 'Fail' code : %%31

Last protocol transmitted: %%32

LCP protocol transmitted : %%33
LCP code transmitted : %%34
LCP id transmitted : %%35
LCP message length : %%36
LCP message transmitted : %%37
Time transmitted last LCP: %%38
Number of Nak transmitted: %%39
Number of Rej transmitted: %%40

IPCP protocol transmitted : %%41

IPCP code transmitted : %%42
IPCP id transmitted : %%43
IPCP message length : %%44
IPCP message transmitted : %%45
Time transmitted last IPCP: %%46
Number of Nak transmitted : %%47
Number of Rej transmitted : %%48

PAP protocol transmitted : %%49

PAP code transmitted : %%50

159
 Software Diagnostics Output

PAP id transmitted : %%51

PAP message length : %%52
PAP message transmitted : %%53
Time transmitted last PAP: %%54

CHAP protocol transmitted : %%55

CHAP code transmitted : %%56
CHAP id transmitted : %%57
CHAP message length : %%58
CHAP message transmitted : %%59
Time transmitted last CHAP: %%60
Number of 'Success' codes : %%61
Number of 'Fail' codes : %%62

1. Last protocol received.

2. Not relevant.

3. Last LCP code received.

4. Last LCP id received.

5. Last LCP/IP message received.

6. Last LCP/IP message length in bytes.

7. Time the message was received.

8. Number of Nacks received for LCP.

9. Number of Rejects received for LCP.

10. Not relevant.

11. Last IPCP code received.

12. Last IPCP id received.

13. Last IPCP message received.

14. Last IPCP message length in bytes.

15. Time the message was received.

16. Number of Nacks received for IPCP.

17. Number of Rejects received for IPCP.

18. Not relevant.

19. PAP code received.

20. PAP id received.

21. PAP message length in bytes received.

22. Last PAP message length in bytes.

160
 Software Diagnostics Output

23. Time the message was received.

24. Not relevant.

25. CHAP code received.

26. CHAP id received.

27. Length of CHAP message received in bytes.

28. CHAP message received.

29. Time the CHAP message was received.

30. Number of ‘Success’ CHAP messages received.

31. Number of ‘Fail’ CHAP messages received.

32. Not relevant.

33. Not relevant.

34. Last LCP code transmitted.

35. Last LCP id transmitted.

36. Last LCP/IP message length in bytes.

37. Last LCP/IP message transmitted.

38. Time the last LCP/IP message was transmitted.

39. Number of Nacks transmitted to LCP.

40. Number of Rejects transmitted to LCP.

41. IPCP protocol transmitted.

42. IPCP code transmitted.

43. IPCP id transmitted.

44. Length in bytes of the last IPCP message transmitted.

45. Last IPCP message transmitted.

46. The last time an IPCP message was transmitted.

47. Number of Nacks transmitted for IPCP.

48. Number of Rejects transmitted for IPCP.

49. Not relevant.

50. PAP code transmitted.

51. PAP id transmitted.

161
 Software Diagnostics Output

52. Length in bytes of the last PAP message transmitted.

53. Last PAP message transmitted.

54. The last time an PAP message was transmitted.

55. Not relevant.

56. CHAP code transmitted.

57. CHAP id transmitted.

58. Length in bytes of the last CHAP message transmitted.

59. Last CHAP message transmitted.

60. The last time an CHAP message was transmitted.

61. Number of ‘Success’ CHAP messages transmitted.

62. Number of ‘Fail’ CHAP messages transmitted.

## 2310 LEVEL = 10, 11

Slip port statistics
---------------------
Number of succefull transmissions : %%1
Number of failed transmissions : %%2
Number of successfull bytes received : %%3
Number of times failed receiving byte: %%4
Number of pulled bytes by Fusion : %%5
Size of last transmitted frame : %%6
Number of transmitted rejected frames: %%7
Number of times driver was stopped : %%8
Number of times failed stop driver : %%9
Number of times got AT response during Slip/PPP session: %%10
Number of times disconnected by force : %%11
Number of timeouts when bringing device up : %%12
Number of timeouts when bringing device down : %%13
Number of times failed alloc LCP msg : %%14
Number of times failed alloc IPCP msg : %%15
Number of times got bad PPP frame with invalid size : %%16
Number of times got bad PPP frame with invalid frame : %%17
Number of times PPP failed authentication phase : %%18
Number of times PPP failed obtain IP address : %%19
Number of times got invalid ICMP message : %%20
Number of times bytes available in FUSION heap : %%21

Last Time received msg : %%22

Last msg received len : %%23
Last msg received : %%24
Last Time transmit msg : %%25
Last msg transmitted len: %%26
Last msg transmitted : %%27

1. Number of frames successfully sent from the RTU to the Radio/Link over SLIP line.

162
 Software Diagnostics Output

2. Number of frames unsuccessfully sent from the RTU to the Radio/Link over SLIP line.

3. Number of bytes received.

4. Number of bytes received by the RTU which could not be processed.

5. Not relevant.

6. Size in bytes of the last transmitted datagram.

7. Number of rejected transmissions of datagrams when the driver was paused. The driver is paused
when initializing modem (e.g. iDEN) using AT commands.

8. Number of times the driver was paused.

9. Number of times failed to pause the driver.

10. Number of times got AT response (such as ERROR, +CME ERROR, AT, ATH) when Slip/PPP was
connected. This denotes a modem error, which forces RTU to disconnect Slip/PPP.

11. Number of times disconnected by force (for example when CD drops.)

12. Number of times timeout expired when trying to connect Slip/PPP.

13. Number of times timeout expired when trying to disconnect Slip/PPP.

14. Number of times failed alloc LCP message. Denotes lack of internal resources.

15. Number of times failed alloc IPCP message. Denotes lack of internal resources.

16. Number of bad PPP with invalid size received.

17. Number of times bad PPP frames with invalid CRC received.

18. Number of times failed authenticate PPP when connecting.

19. Number of times failed to obtain an IP Address from the modem when connecting.

20. Number of times got bad ICMP message from the modem (with source IP Address 0). (Tetra bug)

21. Number of bytes currently available in internal heap for TCP/IP stack (sockets/PPP, etc.)

22. Last time received Slip/PPP message from port. Relevant when driver is connected or trying to
connect.

23. Length of last Slip/PPP message received.

24. Last Slip/PPP message received.

25. Last time transmitted Slip/PPP message from port. Relevant when driver is connected or trying to
connect.

26. Length of last Slip/PPP message transmitted.

27. Last Slip/PPP message transmitted.

163
 Software Diagnostics Output

## 2398
PPP is not created on this port

User has tried issue level 1 or 2 for SLIP port (## 2301 or ## 2302). Port is not PPP.

## 2399
PPP was not initialized yet try again later

User has tried issue level 1 or 2 for PPP port (## 2301 or ## 2302). Port is still initializing and cannot
provide data. Try again later.

I2PHYS

## 2400 LEVEL = 0
Physical layer device key : %%
Link layer device key : %%
TX queue head : %%
RX queue head : %%
offset of next byte to be pushed to 3'rd party driver : %% : %%
Sync frame was sent (0 - never sent) : %%
Time stamps queue : %%

I2Phys device get key.

## 2401 LEVEL = 1
# of received buffers (from physical layer) : %%
Index to next empty time stamp in time stamps queue : %%
Index to next occupied time stamp in time stamps queue : %%
Heap type (formatted = 1, unformatted = 2) : %%
Protocol type (MDLC = 0, DNP = 1, ... ) : %%
Next byte to be read by 3'rd party driver : %%
3'rd party driver instance : %%
Port baud rate : %%
Is 3'rd party driver hooked (0 - No, 1 - Yes) ? : %%
Link layer transmission task is running : %%
Quiet reported by 3'rd party driver : %%
Quiet by MDLc is allowed (0 - No, 1 - Yes) : %%
is MDLC Synchronizing mode allowed ? : %%
is USER's Application Disabled ? : %%
Time (in sec) to flush rx frames : %%
# rx frames avoided : %%
# rx frames thrown under flush : %%

I2Phys queue parameters.

164
 Software Diagnostics Output

IPLINK LINxL, LINxLAN, LINxPL

## 2500 LEVEL = 100

RCP user parameters
--------------------
Radio IP address : %%1
RCP IP port : %%2
RTU sets radio in encrypted mode : %%3
Time to wait while diagnosing radio [millisec] : %%4

1. IP address of ASTRO 3.xx radio.

2. Should always be 469.

3. If radio is encrypted, this parameter will be Yes. If radio is in clear, this parameter will be No.

4. Radio diagnose reply timeout, as defined in Site Configuration.

## 2501 LEVEL = 101

Status of RCP
--------------
Is radio being configured : %%1
Has configuration of radio failed : %%2
RCP request of which configuration failed : %%3
Last request SDU tag number : %%4
Last request sent to radio : %%5
Is radio registered in infrastructure : %%6
Is data service not available : %%7
Is ICMP:Network unreachble received : %%8
Has radio failed transmission due to encryption problem : %%9
Last report received from radio : %%10
Is port in 'Fail' mode : %%11

1. If RTU is configuring ASTRO 3.xx radio (radio startup, RTU startup or when making connection),
this will be yes. In this case, the data will remain pending until it can be transmitted.

2. Whether the configuration of the radio has failed. If so, data cannot be transmitted by way of the
link/radio.

3. Describes which configuration message failed.

4. Sequential number of configuration message last sent to radio.

5. Indicates last type of operation.

6. Indicates whether radio succeeded in registering in the infrastructure.

7. Whether data service is unavailable (This might be the reason for failure to register in infrastructure.)

8. Whether network is unreachable (This might be the reason for failure to register in infrastructure.)

9. Not relevant.

10. The string which the radio returns (RF ACK).

165
 Software Diagnostics Output

11. Indicates whether port is in failed mode. (as in ## 2200)

## 2502 LEVEL = 102

RCP socket status
--------------------
Socket number : %%
Socket state : %%
Socket timeout : %%
Socket open latest result : %%
Socket send latest result : %%
Socket recv latest result : %%

Not relevant. (ASTRO 3.xx)

## 2503 LEVEL = 103

Radio configuration
--------------------
Encryption mode: %%

Indicates whether radio is in Encryption mode or not. (ASTRO 3.xx)

## 2504 LEVEL = 104

Radio information
-------------------
Radio's software version : %%
Radio's manufacturer : %%
Radio's current CAI logic link ID : %%
Radio's maximum transfer unit : %%
Radio's serial number : %%
Radio's registeration status : %%
Radio's channel quality : %%
Radio's signal strength : %%
Radio's battery level : %%

Basic information from radio. (ASTRO 3.xx)

## 2505 LEVEL = 105

Encryption failue info:
-----------------------
%%
RTU sets radio in encrypted mode: %%
Encryption mode of radio : %%

Indicates if there is a contradiction between the radio’s actual encryption mode and the encryption mode
according to the RTU. (ASTRO 3.xx)

166
 Software Diagnostics Output

## 2510 LEVEL = 110, 111

RCP statistics in RTU
----------------------
Number of requests issued to radio : %%1
Number of requests aborted by RTU : %%2
Number of relevant replies received from radio : %%3
Number of irrelevant replies received from radio : %%4
Number of reports received from radio : %%5
Number of irrelevant reports received from radio : %%6
Number of 'power up' reports received from radio : %%7
Number of 'not registered' reports received from radio : %%8
Number of 'data service' reports received from radio : %%9
Number of 'encryption state' reports received from radio : %%10
Number of 'encryption failed' reports received from radio: %%11
Number of invalid reports/replies received from radio : %%12
Number of ICMP Netowrk unreachable received from radio : %%13
Number of ACK reports received from the radio : %%14
Last Destination IP Address that received ACK for : %%15

1. Number of requests sent from the RTU to the ASTRO 3.xx radio.

2. Number of times the RTU aborted transmission of a request due to timeout.

3. Number of replies from the radio (should match the number of requests.)

4. Number of replies from the radio which were discarded.

5. Number of reports from the radio.

6. Number of reports from the radio which cannot be deciphered by the RTU.

7. Number of reports from the radio of type “data service”.

8. Number of reports from the radio of type “not registered”.

9. Number of reports from the radio of type “encryption state”.

10. Number of reports from the radio of type “encryption failed”.

11. Number of reports from the radio of type “encryption failed”.

12. Number of reports/replies received from radio which were illegal.

13. Number of messages received from radio that ICMP Network is unreachable.

14. Number of Acknowledgements from the infrastructure on message that were sent.

15. Last Destination IP Address for which an acknowledgement was received.

167
 Software Diagnostics Output

## 2520 LEVEL = 100

IPMODM user parameters
----------------------
Learn IP address from modem : %% 1
RTU IP address : %% 2
RTU's gateway IP address : %% 3
RTU Subnet mask : %% 4
DTE IP Address in modem : %% 5
DTE Subnet mask in modem : %% 6
Home Agent in modem : %% 7
Modem IP Address : %% 8
Modem version : %% 9
Getting "OK" timeout from modem [millisec]: %% 10
Time to wait for ATD to succeed [millisec]: %% 11
Time to wait for modem to be configured [millisec]: %% 12
Optional string to send before dialing : %% 13
Radio Sampling time for RALP prototol [millisec] : %% 14
Connect to : %%15
Disconnect on ICMP:Network Unreachable reception? : %%16
Is Abort Sequence supported in the modem ? : %%17
Ignore CD Signal ? : %%18
Maximal Rx Idle time to disconnect [seconds ] : %%19
Modem address (if exist) : %%20
Registration life time to disconnect [seconds] : %%21

Parameters for packet data modem (e.g. iDEN).

1. YES if the port’s IP address is to be retrieved during run time, e.g. from iDEN modem.

2. Current RTU’s IP address.

3. Current RTU’s default gateway.

4. Current RTU’s subnet mask.

5. The IP address of the modem’s configured RTU as stored in the modem.

6. The subnet mask address of the modem’s configured RTU as stored in the modem.

7. The home agent configured for the modem (to be used as the RTU’s default IP address.)

8. The IP address of the modem.

9. The OEM version of the modem (should be R35.01.00 or later).

10. Timeout in milliseconds for getting an OK response when sending an AT command.

11. Timeout in milliseconds to wait for the modem to succeed in registration (if needed) and go online.

12. Timeout in milliseconds to wait for the modem to be configured. To be used when transmitting while
the modem is being configured. If this time elapses, transmission will fail. Refer to Modem
configuration timeout parameter in the Site Configuration Advanced Link Layer.

13. Optional AT command string to send to modem before dialing. Used by the RTU to override default
settings in the modem. Refer to technical support if needed.

168
 Software Diagnostics Output

14. Radio sampling time in milliseconds that RALP will poll the radio registration status. Relevant only if
RALP is enabled.

15. Device to which the RTU is connected (iDEN,Tetra, Standard Modem, or Null Modem).

16. YES, if the RTU should disconnect Slip/PPP when getting an ICMP:Destination Unreach message.

17. YES, if the modem supports abort sequence. An abort sequence is +++ issued after a pause of 1
second and followed by another pause of 1second. If YES, the modem should switch to command
mode when this sequence is issued by the RTU. The modem may or may not disconnect from PD
channel. Tetra or Novatell (CDPD) for example do not support it, but most modems do (for example
iDEN or G18).

18. Never, if CD is being polled constantly. This includes the time while Slip/PPP is being connected and
when the connection is established. When CD drops, the modem will be disconnected by the RTU.
Always, if CD is never checked. It is assumed that it is active all the time, so its state does not denote
Slip/PPP state.
When connecting, if CD is ignored during Slip/PPP connection but polled when connection is
established.

19. Maximal Rx idle time to disconnect in seconds. If no data is received from the port for this period of
time, Slip/PPP will be disconnected. If this parameter is 0, it will never be checked.

20. The address of the modem which is read from the modem using an AT command during
configuration. (i.e. IMEI in iDEN, ISSI in TETRA, IMSI in GPRS, WUID in ASTRO IV&D)

21. Timeout in seconds to disconnect after registration life time expires. If 0 it is not relevant. This
parameter can be set by the user in the modem configuration file, or in the site configuration. For
iDEN, this parameter is automatically retrieved from the modem during connection.

## 2521 LEVEL = 101

IPMODM state
------------
Is modem being configured ? : %% 1
State of configuration task : %% 2
Is CD active ? : %% 3
Has modem configuration been aborted ? : %% 4
Is Modem registered in the system ? : %% 5
Cause for configuration failure : %% 6
Last command that was sent to Modem : %% 7
Response received from modem that caused failure : %% 8
Time it took to configure modem [millisec] : %% 9
Is port being locked ? : %%10
Last time started configure modem : %%11
Command sent to modem that caused failure : %%12
Is in transparent mode : %%13
Task that is locking port : %%14
Time to wait to begin modem configuration [milli]: %%15
Time it took to connect modem [millisec] : %%16
Maximal idle timeout to disconnect [millisec] : %%17
Registration life time to disconnect [millisec] : %%18 (%%19)

1. YES if modem is in the process of being configured. In this case, it operates in command mode, and it
cannot transmit data.

169
 Software Diagnostics Output

2. Connected and Registered should be displayed if the modem is online. In online mode, the modem
can transmit data.

3. YES if the CD pin is active. If YES, the modem is connected and is in online mode.

4. Internal use only.

5. YES if the packet data modem is registered in the system.

6. If last modem configuration failed, display the reason for the failure.

7. The last AT command which was sent to the modem when configuring it.

8. If modem configuration has failed, display the last response from the modem that caused this failure
(No Response if there was none).

9. Time in milliseconds that it took to configure the modem last time. Relevant only if modem
configuration has succeeded. Note that it does not denote the actual time the modem has been in
command mode, just the last cycle.

10. Should be YES when configuring the modem.

11. Marks the time that last started to configure the modem. Along with 9, this denotes the time Slip/PPP
has been reconnected.

12. The last command sent to the modem causing it to fail and issue parameter 6.

13. Transparent mode can be set by the application locking the port.

14. Internal use.

15. Time to wait before starting to configure modem. Usually when configuring it remotely, this is set to
5000 milliseconds.

16. The time it took to actually connect/register modem.

17. Configuration - Maximal idle timeout to disconnect modem. The RTU will monitor reception from
modem/radio, and if not received within that time it will disconnect and connect it again. As a result
the modem/radio will reconnect with the infrastructure. If set to 0, this parameter is ignored.

18. Timeout in milliseconds to disconnect after registration life time expires. If 0 it is not relevant. This
parameter can be set by the user in the modem configuration file, or in the site configuration. For
iDEN, this parameter is automatically retrieved from the modem during connection.

19. The number of milliseconds which have passed since the 'Registration life time to disconnect' timeout
started.

170
 Software Diagnostics Output

## 2522 LEVEL = 102

RALP State
----------
Diagnostic timeout : %% 1
IP Port Number : %% 2
IP Address : %% 3
Was RALP initiated : %% 4
Is Communication Enabled in Radio : %% 5
Is request being executed : %% 6
Current exectued group : %% 7
Current executed opcode : %% 8
Current expected opcode : %% 9
Pointer of response buffer : %% 10

Relevant for iDEN only.

1. Time in milliseconds to wait for a response from the iDEN modem to a RALP command. Refer to
Modem diagnose reply timeout parameter in the Site Configuration Advanced Link Layer.

2. IP port number of the RALP protocol.

3. IP Address of the modem for the RALP protocol.

4. YES if a RALP session has been initiated with the modem.

5. YES if the modem has enabled RALP communication with the RTU.

6. YES if the RTU expects a RALP response from the modem.

7. Currently executed RALP command group

8. Currently executed RALP opcode.

9. Currently executed RALP opcode.

10. Internal use only.

## 2523 LEVEL = 103

iDEN Radio Status:
------------------
Radio status : %% 1
Radio substatus : %% 2
Radio services : %% 3
Radio mobile IP : %% 4

1. Modem status.

2. Modem substatus (Packet data registered).

3. Modem supported services (e.g. packet data).

4. Accept if modem is mobile IP capable.

171
 Software Diagnostics Output

## 2524 LEVEL = 104

iDEN Phone Information:
-----------------------
Ralp version : %% 1
Model type : %% 2
Model number : %% 3
Serial number : %% 4
IMEI number : %% 5
Codeplug version : %% 6
DSP ROM version : %% 7
RCE ROM version : %% 8
Software Type : %% 9

This information is obtained via RALP from the modem.

1. RALP version in the modem.

2. Modem type.

3. Modem model number.

4. Modem serial number.

5. Modem electronic number (IMEI).

6. Modem codeplug version.

7. Modem software version.

8. Modem software version.

9. Modem software type.

172
 Software Diagnostics Output

## 2525 LEVEL = 105

LAPi related statistics in iDEN modem:
--------------------------------------
Number of PRAP message expirations : %% 1
Number of Inbound I PDUs sent (not including retries) : %% 2
Number of Inbound All Block Retry I PDUs sent : %% 3
Number of Inbound Retry I PDUs sent : %% 4
Number of Outbound I PDUs received (not including retries) : %% 5
Number of Outbound Retry I PDUs received : %% 6
Number of PDUs lost when the LLC receives a Local Release : %% 7
Number of PDUs lost due to an error or connection loss : %% 8
Number of Inbound user bytes requested to be transmitted : %% 9
Number of Outbound user bytes received : %%10
Number of half duplex collisions detected by the LAPi LLC : %%11
Number of SABME received because of N(R) or timeout in peer : %%12
Number of unexpected UAs received : %%13
Number of unexpected DMs received : %%14
Number of retransmissions exhausted while connect/disconnect: %%15
Number of retransmissions exhausted while transmitting I PDU: %%16
Number of N(R)s received out of valid range : %%17
Number of N(S)s received out of valid range : %%18
Number of Retry I PDUs received without Original I PDU : %%19
Number of reliable datagrams from client too big to send : %%20
Number of unreliable datagrams from client too big to send : %%21
Number of PDUs received in a state when they were invalid : %%22
The number of invalid PDUs received from FNE : %%23
The number of multiple block I PDUs with an LLC FCS error : %%24

The parameters are obtained via RALP from modem. Only the important parameters are described below:

2. Number of messages sent over the air towards the MDG/iDEN system. Not including the number of
retries in #3 and 4.

3,4. Number of retries for messages sent over the air towards the MDG.

5. Number of messages received from the MDG. Not including the number of retries in #6.

6. Number of retries received from the MDG.

9. Number of bytes transmitted over the air towards the MDG.

10. Number of bytes received over the air from the MDG.

All other parameters denote communication problems over the air. Contact system
administrator/technical support if not 0.

Note: After executing diagnostics, these parameters are reset in the modem.

Refer to iDEN documentation such as iDEN Protocol Manual 68P81129E10-B for an explanation of the
LAPi protocol and meaning of parameters.

173
 Software Diagnostics Output

## 2526 LEVEL = 106

IP Related Statistics in iDEN modem:
------------------------------------
Total number of IP Datagrams received from DTE : %% 1
Total number of Total IP Datagrams received from FNE : %% 2
Number of Valid IP Datagrams received from DTE : %% 3
Number of Valid IP Datagrams received from FNE : %% 4
Number of IP Datagrams sent to DTE : %% 5
Largest IP Datagram sent to DTE (bytes) : %% 6
Largest IP Datagram sent to FNE (bytes) : %% 7
Number of ICMP Error Messages Sent : %% 8
Number of Valid UDP Datagrams received : %% 9
Number of received UDP datagrams discarded by the MS : %%10
Number of UDP Datagrams Sent : %%11
Number of successful MIP registrations by the MS : %%12
Number of rejected MIP registrations by the MS : %%13
Number of retries MIP Registrations Requests sent by the MS: %%14

1. Number of datagrams transmitted by the RTU to the modem including RALP/diagnostics of the
modem as well as over the air data.

2. Number of datagrams transmitted by the modem to the RTU as a response, including

RALP/diagnostics of the modem as well as over the air data.

3. Number of valid datagrams received over the air from the MDG.

4. Number of valid datagrams transmitted by the RTU to the modem including RALP/diagnostics of
modem as well as over the air data.

5. Number of datagrams sent over the air to the MDG.

6. Size of largest datagram sent to the RTU. Datagram may be either MDLC data or RALP diagnostics.

7. Size of largest datagram sent over the air to the MDG/iDEN system. (data only)

8. Number of ICMP errors sent to the RTU.

9. Number of valid UDP datagrams received in the modem from the RTU or from the MDG. This does
not include the RTU’s over the air data.

10. Number of valid UDP datagrams discarded by the modem. This does not include the RTU’s over the
air data.

11. Number of UDP datagrans sent by the modem (usually RALP) towards the RTU. This does not
include the RTU’s over the air data.

12,13,14. Number of times succeeded, denied, and retried mobile IP registration with the MDG.

Note: After executing diagnostics, these parameters are reset in the modem.

174
 Software Diagnostics Output

## 2527 LEVEL = 107

iDEN modem server description
-----------------------------
Normalized battery level : %% 1
Color code : %% 2
Carrier : %% 3
Carrier RSSI (dbm) : %% 4
Carrier SQE (db) : %% 5
Battery level : %% of %% 6
Signal strength : %% of %% 7

Obtained via RALP from modem.

1. Battery level 0 to 60.

2. Color code.

3. Carrier code.

4. RSSI, received signal strength, should be more than –100 dbm.

5. SQE, received signal strength in db.

6. Battery level from 1 to 6 (highest).

7. Signal strength from 1 to 6 (highest).

## 2530 LEVEL = 110,111

IPModem statistics:
--------------------
Number of times CD has dropped : %% 1
Number of times RTU powered up : %% 2
Number of times Registration failed : %% 3
Number of times configuration timeout occured : %% 4
Number of times modem configuration has succeeded : %% 5
Number of times modem configuration has failed : %% 6
Number of times detetected that modem is not packet data : %% 7
Number of times link failed because of registration : %% 8
Number of times re-registered modem : %% 9
Number of times restarted modem : %%10
Last reason for link failure : %%11
Number of times received icmpnetunreachable : %%12
Number of times lost connection with modem (PPP) : %%13
Number of times disconnect because there was no response : %%14
Number of times failed dialup : %%15
Number of times failed hangup : %%16
Number of times failed start slip/ppp : %%17
Number of times disconnect because of idle timeout : %%18
Number of times failed set PPP parameter : %%19
Number of times disconnect because of registration timeout: %%20

1. Number of times CD became inactive, e.g. the modem was disconnected or went offline (command
mode).

2. Number of times the RTU powered up (cold or warm restart).

175
 Software Diagnostics Output

3. Number of times the modem was online and got deregistered from the infrastructure.

4. Number of times the configuration timeout elapsed. This may happen when configuration takes
longer than the time specified by the user in the Modem configuration timeout parameter in the Site
Configuration Advanced Link Layer. If data was transmitted while the modem was being configured,
that data may have been lost.

5. Number of times that configuration succeeded.

6. Number of times that configuration failed. When failed, the RTU keeps reconfiguring the modem in
cycles until it succeeds. This number denote how many configuration cycles have failed.

7. Number of times the RTU failed to register the modem because it is not data packet capable. (The
modem is probably not registered in the infrastructure database.)

8. Not relevant (future use).

9. Number of times the RTU deregistered and reregistered the modem by force.

10. Number of times the RTU restarted the modem (usually because of registration problems).

11. Last event that caused the port to be failed: Modem configuration failed, or modem became
deregistered from the infrastructure.

12. Number of ICMP:Destination unreach messages received of type Network unreachable.

13. Number of times the PPP connection was dropped.

14. Number of times the Slip/PPP connection was disconnected because it failed to respond for RALP
requests. Relevant for iDEN.

15. Number of times failed to issue ATD (dialup) command to modem.

16. Number of times failed to issue ATH (disconnect) command to modem (there was no response).

17. Number of times failed to connect Slip/PPP.

18. Number of times the connection was disconnected because the idle timeout expired with no data
coming in from the modem/radio. This is relevant if (17) in @2521 (level 101) is not 0.

19. Number of times failed to set the PPP parameters.

20. Number of times the connection was disconnected because of the Registration life time parameter.

Note: Activating this message with level 110 will reset these parameters.

176
 Software Diagnostics Output

## 2531 LEVEL = 102

PDS Mib state
---------------
Wait for Context Timeout : %% 1
SNMP IP Port : %% 2
Trap IP Port : %% 3
MIB Name : %% 4
Is PDS Mib initiated ? : %% 5
Radio Context state : %% 6
Radio Registration state : %% 7
Is SNMP Session locked : %% 8
SNMP session locking Task name : %% 9
SNMP session state : %%10

Relevant for ASTRO IV&D only.

1. Configuration parameter in milliseconds. How long to wait until the ASTRO IV&D radio gets context
activated. If this time expires, the radio will be reconnected by the RTU. Sometimes it will even be
restarted (via AT command).

2. Configuration parameter - IP (UDP) Port for SNMP poll communication issued by RTU, when
reading radio state.

3. Configuration parameter - IP (UDP) Port for SNMP trap communication issued by radio to RTU,
when changing radio context activation state.

4. OID of MIB used to read the radio's context activation state. This is referred to as PDS (Packet Data
System) MIB.

5. If Yes, the MIB was initialized.

6. Internal RTU's state – Whether or not it is waiting for context to be activated.

7. Radio context activation state.

8. Not relevant.

9. Not relevant.

10. Shows the RTU's state in relation to reading radio status.

## 2532 LEVEL = 103

PDS Mib table
---------------
Table MIB OID: : %% 1

Last Last
Set Get Number Number Number
Subid Type Value Description Error Error Set Get Trap
---- ---- ----- ----------- ----- ----- --------- -------- ------

Relevant for ASTRO IV&D only.

177
 Software Diagnostics Output

1. OID of MIB used to read the radio's context activation state. This is referred to as PDS (Packet Data
System) MIB.

Each row in the PDS MIB table represents a MIB variable.

Subid MIB Variable sub ID.

Type 2 – Integer.

Value This field depends upon the variable.

Description This field depends upon the variable.

The important variables are in row 2 and 4:

-In row 2 (subid 2.1.2) pdsDataregsts - should be 1.

Indicates whether the subscriber is registered on the packet data system (i.e. context activated).
If 1 it is context activated. If 2, a previous attempt to register failed.

-In row 4 (subid 2.1.4) pdsDataActivitySts - should be 1.

Indicates whether the subscriber is on the packet data channel or not. This variable is set to 1
(active) when the subscriber switches to the packet data channel and to 0 (inactive) when it is no
longer on the packet data channel.

Other variables are as follows:

In row 1 (subid 2.1.1) unitId - always 0.

In row 3 (subid 2.1.3) pdsDataRegRequest – The RTU sets it to 1 when it wishes to make a data
registration request (or context activation) on the packet data system. After it
has been completed this variable is set to 0 by the radio.

In row 5 (subid 2.1.5) pdsPPPLinkSts - Always 0.

Last Set error Shows the error code after fail to set a variable to the radio, usually 0.

Last Get error Shows the error code after fail to get a variable from the radio, usually 0.

Number Set Number of times set a variable in the radio in the form XX/YY.
XX - shows number of times succeed set a variable.
YY - shows number of times failed set a variable.

Number Get Number of times got a variable from the radio in the form XX/YY.
XX - shows number of times succeed get a variable.
YY - shows number of times failed set a variable.

Number Trap Number of times received traps from the radio for that variable

178
 Software Diagnostics Output

## 2533 LEVEL = 104

PDS SNMP State
---------------
Number of free PDUs : %% 1
Maximal number of free PDUs : %% 2
Number of free Vars : %% 3
Maximal number of Vars : %% 4
Last request ID sent : %% 5
Number of ASN1 parse errors : %% 6
Number of bad SNMP packets received : %% 7
Last error with SNMP operation : %% 8

Relevant for ASTRO IV&D only.

1. Current number of free PDUs (packet data units) used for communication over SNMP with the radio.

2. Configuration parameter for number of PDUs (Packet data units) used for communication over
SNMP with the radio.

3. Current number of free entities used to represent SNMP MIB variables.

4. Configuration parameter for maximum number of free entities used to represent SNMP MIB
variables.

5. Last SNMP request ID sent to the radio.

6. Number of errors when parsing received frames in SNMP protocol (ASN1) from the radio.

7. Number of illegal SNMP frames received from the radio.

8. Last error code when doing a set/get SNMP operation with the radio.

## 2534 LEVEL = 210, 211

PDS MIB Statistics
-------------------
Number of times activate context sent : %% 1
Number of times activate context timeout : %% 2
Number of times activate context failed : %% 3
Number of times check registered : %% 4
Number of times check registered failed : %% 5
Number of times gained register : %% 6
Number of times lost register : %% 7
Number of times trap ignored : %% 8
Number of times received pdsmib trap : %% 9
Number of times ignored unexpected variable in trap : %% 10
Number of times ignored varibale in pdsmib trap : %% 11
Number of times got pdsmib variables through a trap : %% 12

Relevant for ASTRO IV&D only.

1. Number of times RTU sent context activate request to the radio via SNMP.

2. Number of times RTU got timeout when trying to context activate the radio.

3. Number of times RTU failed to context activate the radio.

179
 Software Diagnostics Output

4. Number of times RTU checked if radio is still context activated.

5. Number of times RTU failed check radio state.

6. Number of times radio got context activated.

7. Number of times radio lost registration (became context deactivated).

8. Number of times RTU received a trap from the radio and ignored it.

9. Number of times RTU received a trap from the radio.

10. Number of variables RTU ignored when receiving a trap from the radio. This includes variables
which are legal, but are not supported.

11. Number of variables RTU ignored when receiving a trap from the radio. Unlike previous item, this
counts variables which are illegal.

12. Number of variables RTU received from the radio via traps.

## 2540 LEVEL = 210,211

RALP statistics:
----------------
Number of times failed lock RALP : %% 1
Number of times posted a request : %% 2
Number of times aborted request : %% 3
Number of times got response for requests : %% 4
Number of times got unsolicited alarms : %% 5
Group of last response received from radio : %% 6
Opcode of last response received from radio : %% 7
Last alarm received from radio : %% 8
Number of software alarms received from radio : %% 9
Last software alarm error : %%10
Last software alarm task name : %%11
Number of registration alarms received from radio : %%12
Last registration alarm code : %%13
Last registration alarm roaming : %%14
Last registration alarm domain : %%15
Number of times have got invalid alarm : %%16
Number of times have got invalid reponse (not alarms) : %%17
Number of times ignored responses : %%18
Number of times ignored alarms : %%19
Number of times got 'Failed execute' alarm : %%20

Relevant only if RALP is enabled. (iDEN)

1. Internal use only.

2. Number of times a RALP request was sent to the modem.

3. Number of times aborted RALP when waiting for a reply from the modem.

4. Number of times a response was received for RALP requests from the modem.

5. Number of times unsolicited alarms weres received from the modem (registration/software etc).

6. Group of last RALP response received from the modem.

180
 Software Diagnostics Output

7. Opcode of last RALP response received from the modem.

8. Code of last alarm received from the modem.

9,10,11- Number of software alarms received from the modem, and specific parameters of the last one
received.

12,13,14,15. Number of registration alarms received from the modem, and specific parameters of the last
one received.

16. Number of times an alarm was received denoting that a RALP request was invalid.

17. Number of times invalid messages were received via RALP socket from the modem.

18. Number of times that responses which were received from the modem were ignored.

19. Number of times that alarms which were received from the modem were ignored.

20. Number of times the modem failed to execute a RALP request sent from the RTU.

## 2541 LEVEL = 220

Standard Modem state
--------------------
Block ID of file : %% 1
Has file been downloaded : %% 2
Number of seconds to wait for OK : %% 3
Number of seconds to wait while dialing : %% 4
Number of seconds to wait while diagnosing : %% 5
Number of seconds to wait before unset RTS : %% 6
Number of seconds to wait after unset RTS : %% 7
Last error when sending command to modem : %% 8
Number of times Toggled RTS : %% 9
Last error from modem : %% 10
Last command that transmitted to modem : %% 11
Last command that caused modem error : %% 12
Ignore CD ? : %% 13
Is abort sequence supported in modem ? : %% 14
Has last transmission to modem been aborted? : %% 15
Need to toggle RTS when entering command mode ? : %% 16
Has new file need to be initialized ? : %% 17
Standard modem name : %% 18
Number of milli seconds to Wait for quiet : %% 19
File version : %% 20
File features bit mask in hexa : %% 21
File current processed line : %% 22
Last AT response from modem : %% 23

1. In MOSCAD, Port 1 is block id 42; Port 2 is block id 43; Port 3 is block id 44.
In ACE3600 port PI1 is block id 42, SI1 is block id 43, SI2 is block id 44, and PI2 is block id 45.

2. Has the modem configuration file been downloaded?

3. When sending an AT command to the modem, the time to wait for its reply.

4. Time to wait while dialing.

181
 Software Diagnostics Output

5. Time to wait while diagnosing the modem via AT command.

6. Time to wait before resetting RTS (turning off modem if applicable).

7. Time to wait after resetting RTS (turning on modem if applicable).

8. Internal use.

9. The number of times tried to reset modem because failed to configure it.

10. Internal use.

11. The last AT command that was sent to the modem.

12. The last AT command that failed.

13. Should the modem CD (DCD) signal be ignored when connecting?

14. Is the abort sequence (+++) supported by the modem? If YES, the modem supports the abort
sequence (+++) when moving from data to command mode.

15. Internal use.

16. Do we need to toggle RTS when entering command mode? If YES, each time move from data to
command mode, RTS will be turned off and on.

17. Internal use.

18. The name of the modem according to the modem configuration file.

19. Timeout (in milliseconds) to wait when expecting an AT response after getting a partial answer
(something received which is not the expected response.)

20. The modem configuration file version.

21. Internal use.

22. Current line processed in file.

23. Last AT response replied by modem.

## 2542 LEVEL = 102

Standard modem File variables
-----------------------------
Variable Value
-------- -----

When a Standard Modem is used, this level shows obtained variables as set in the downloadable IP
Modem file.

The Variable column shows the variable name, according to the file. The Value column shows its
contents, either initialized in the file or read from the modem.

182
 Software Diagnostics Output

## 2543 LEVEL = 103

%% times toggled RTS : %% 1

1. The number of times toggled RTS (tried to restart modem) because configuration failed.

## 2544 LEVEL = 104

Standard Modem %% : %% 1

1. The modem diagnostics according to the [Diag0] - [Diag7] sections in the modem configuration file.

## 2545 LEVEL = 105

Standard Modem File : %% 1

1. The modem configuration file that was downloaded and used when configuring the modem by the
system.

## 2560 LEVEL = 100

User parameters of LAN connection
----------------------------------
Port name : %%
Interface name : %%
Wait for connect timeout [millisec]: %%
Sample time interval [millisec] : %%

Gets the user parameters of LAN CONTROL.

## 2561 LEVEL = 101

Status of Lan connection
------------------------------
Is Connected : %%
Time that is connected [sec] : %%
Is Config Failed : %%
Time that is disconnected [sec] : %%

Gets the status of LAN CONTROL.

## 2568 LEVEL = 110

Statistics of LAN connection
-----------------------------
Number of times wait for config failed: %%
Number of times config succeed : %%
Number of times config failed : %%

Gets the statistics of LAN CONTROL.

183
 Software Diagnostics Output

## 2569 LEVEL = 255

Diagnostics levels for LAN Control
----------------------------------
Level 0 - Get user parameters of LAN Connection
Level 1 - Get status of LAN Connection
Level 10 - Get statistics of LAN Connection and reset
Level 11 - Get statistics of LAN Connection
Level 255 - This list

This lists all diagnostics provided for the device at all its supported levels.

## 2597
Section %% not found in file

The Diag[n] section number related to the level does not appear in the modem configuration file.

## 2598
Failed communicate with radio

Indication that communication with radio has failed. (Occurs when response from the radio times out.)

## 2599
Communication with radio already in progress - please try again

Occurs when configuring modem, and it cannot be diagnosed using RALP over SLIP (SLIP has not been
initiated).

NTP

## 3200 LEVEL = 0
NTP state
----------
Does NTP configuration block exist : %%1
Is NTP clock disipline enabled : %%2
Is clock synchronized : %%3
Has clock been slewed (adjusted) or stepped : %%4
Is NTP being initialized : %%5
Is NTP task stopped because of fatal error : %%6
Does task hang up because of insuffient memory : %%7
Number of peer associations : %%8
Maximum allocated memory block size in bytes : %%9
Last allocated memory block size in bytes : %%10
Number of current memory allocated blocks : %%11
Max sync offset to declare an error in seconds : %%12
NTP default option : %%13
Time sync lost before declare 'No Sync' [sec] : %%14
Notify error logger when when losing sync ? : %%15

NTP parameters:

184
 Software Diagnostics Output

1. YES if the NTP file was downloaded (not relevant for ACE).

2. YES if NTP controls the clock. The user can configure servers without modifying the clock for
diagnostic/tests purposes.

3. YES if the clock is considered as synchronized.

4. YES if the clock has been modified.

5. YES if the NTP process is in the middle of being initialized.

6. YES if the NTP process was halted because of a fatal error and cannot control the clock. It does not
affect other aspects of the firmware, but denotes a problem that requires restarting the RTU to regain
control on the clock.

7. Internal use.

8. Number of peers configured.

9. Size of memory allocated (internal use).

10. Last memory size that was allocated (internal use).

11. Number of memory blocks allocated (internal use).

12. This is the advanced NTP parameter configured in the site configuration ‘Max sync offset in
milliseconds’. The maximum permitted offset of the RTU clock from its NTP server(s). If the offset
exceeds the value set in this parameter, the NTP servers will be polled frequently to correct the offset,
possibly causing a heavy communication load. When set to 0, the offset is not checked. It is
recommended to leave this parameter set to 0. If 0 a default of 0.5 second difference between clocks
will log an error.

13. The set of parameters in NTP standard RFC1305 language (www.ntp.org) which are used to
designate how the peer clock is obtained. For example burst iburst version 3 minpoll 1 maxpoll 10.

14. The number of seconds to wait before declaring ‘no sync’, when no reply is received from the NTP
server after a poll.

15. Whether notification should be sent to the error logger when declaring ‘no sync’.

185
 Software Diagnostics Output

## 3201 LEVEL = 1
NTP Clock state
-----------------
Clock state : %%1
Last offset adjusted to host clock : %%2
Drift in frequency : %%3
Latest frequency adjustment per seconds : %%4
Distance to current sync source : %%5
Dispersion of system clock : %%6
Stratum of system : %%7
Ticks time and date : %%8
Prefered peer (server) : %%9
Prefered peer offset in seconds : %%10
Prefered peer delay in seconds : %%11
Prefered peer dispersion : %%12
Is clock synchronized : %%13
Time took to gain synchron. [sec] : %%14
Time took to lose synchron. [sec] : %%15
Sec since synchron. state has change : %%16
Sec. aince not being in sync : %%17

1. Whether the NTP clock is synchronized.

2. Last adjustment to clock (phase) in seconds.

3. Drift in frequency from sync source in seconds.

4. Last adjustment to system clock per second in seconds.

5. Distance in seconds to sync source (the root stratum 1).

6. The maximum error of the local clock relative to the system reference clock.

7. Startum of the site. 1 is the root, 2 is the one connected to it.

8. Clock system (time and date) e.g. Sun May 14 15:06:32:812 2000

9. Prefered IP Address if system peer (server)

10. Clock offset in seconds compared to the system peer's clock (not root).

11. Delay in milliseconds to system peer.

12. The maximum error of the local clock relative to the peer clock.

13. YES if the clock is considered as synchronized.

14. The time in seconds that it took to achieve the last synchronization.

15. How long system was synchronized before it lost synchronization (in seconds).

16. If the system is synchronized - how long (in seconds) has it been synchronized.

17. If the system is notsynchronized - how long (in seconds) has it not been synchronized.

186
 Software Diagnostics Output

## 3202 LEVEL = 2
Fail Prev Next
Peer address port assoc Strat test Flags poll poll delay offset disper. maxrxtime
------------ ---- ----- ----- ---- ---- ---- ----- ------ ------- ------- ---------

This is the list of servers that NTP polls.

1st column * means this is the system peer, + is a candidate, - or x is bad server.

Peer Address The peer IP address.

Failed test Usually ‘—’; otherwise a number from 1 to 10 which represents these tests failed
when checking upon latest results from peer. For a list of failed tests, contact product support or
www.ntp.org.

Flag A hexadecimal number that denotes the attribute of the peer according to www.ntp.org.

Prev poll/Next poll how many seconds ago the peer was polled, and how long until it will be
polled again.

Delay How much delay in milliseconds to each peer.

Offset The time offset in milliseconds between the system clock and the peer.

Dispersion How stable the clock is. (the less it is the better is the result. maxrxtime is for internal use
and denote in microseconds how much time since the frame received from server until it was processes.

## 3203 LEVEL = 3
NTP local time:
---------------
Ticks time and date : %%1
Is Unit Time Zone aware (Global or Local): %%2
Current local time zone : %%3
Is daylight saving in effect : %%4

The current timezone. This diagnostic can be used regardless of NTP.

1. The local time of RTU (Ticks is local time),

2. YES if the unit is time zone aware, as defined in the site configuration Time Zone advanced paramter.
By default it is not. If user use NTP with no time zone aware, there are two choices: If the server if
another MOSCAD ACE which is not connected to a real NTP server, or to a GPS, the time will show the
same as it was set in the server. If the server is a real NTP server, GPS, or another MOSCAD ACE which
is connected to any one of them (directly or indirectly), the time will be a UTC time (Universal Time
Clock), but the RTU will not be aware of that. When reading the time via STS Time & Date for example,
it may be shown with an offset. Extended time sync sent from this RTU will have no time zone as well so
all RTUs synced will operate with UTC time too.

3. The time zone in minutes as configured by the user in the advanced site configuration.

4. Whether daylight savings time is in effect. In order for this to be YES, the user must set the time
zone in the advanced site configuration and the current time must be between the start and end dates

187
 Software Diagnostics Output

defined in the ACE application database Daylight Saving Dates system table. If YES, an extra hour is
added to local time zone of RTU.

## 3204 LEVEL = 4
Resolve Retry Interface Num Num Last
Peer address port assoc peer address time Time Active Resolv Failed Error
------------ ----- --- -------------- ------- ----- -------- ------ ------ -----

The list of NTP resolved servers. When using NTP it is possible to configure NTP name servers instead
of numeric addresses. This is accomplished only if the user specified DNS servers. This list NTP
Diagnostic level 4, shows these servers, on which port they were configured, and their numeric addresses.
The rest columns are for internal use. Note that when an NTP server name is resolved, its address is
updated in the list of polled servers in NTP Diagnostic Level 2, and it participates in the NTP process.
(Not supported in TETRA and ASTRO IV&D ports.)

## 3210 LEVEL = 10, 11

NTP Statistics
-----------------
Number of times failed allocate memory : %%1
Number of times freed memory blocks : %%2
Number of times transmitted packets : %%3
Number of times failed transmission : %%4
Number of times received packets : %%5
Number of times dropped packets : %%6
Number of times ignored packets : %%7
Number of times gained/changed syncronization : %%8
Number of times lost syncronization : %%9
Number of times stepped clock : %%10
Number of times adjusted clock : %%11
Number of times reset NTP clock/peers by force : %%12
Maximal time spent in input_handler : %%13
Maximal elapsed time of timer handler[millisec] : %%14
Maximal time offset from system peer [seconds] : %%15
Number of times reset peer poll time to minimum : %%16
Last dest address of packet not sent : %%17
Last ifname of packet not sent : %%18
Max elapsed time since got a frame till process [micro]: %%19
Max elapsed time spent when transmt a frame [micro] : %%20

NTP statistics.

1. The number of times the NTP process failed to allocate memory.

2. The times memory blocks were freed (poolmngr).

3. The number of NTP packets which were transmitted.

4. The number of times transmission failed.

5. The number of NTP packets received.

6. The number of packets that were received and dropped.

7. The number of packets that were received and ignored.

188
 Software Diagnostics Output

8. The number of times the site gained synchronization or changed system peer.

9. The number of times the site lost synchronization (1 or 2 is typical at startup).

10. The number of times a new time was set in the system clock.

11. The number of times changes were made to the system clock (frequency.)

12. The number of times the clock was been tampered (e.g. SnmpIntr). NTP resets its peers and internal
variables once diagnosing this situation and polls them from the beginning (after 15-20 minutes of active
sync.)

13. Maximal time spent by NTP handler in milliseconds.

14. Maximal elapsed time between NTP timer (1 second timer) and when it was actually processed. NTP
transmits to the peers during processing.

15. Maximal time offset from the system peer.

16. When losing sync with an NTP server, or when a PPP port is disconnected and connected again, the
NTP process decreases the poll time to a minimum, in order to expedite the time it takes to re-sync. In this
case, all servers will be polled frequently. This shows how many times this situation occurred.

17. The address of the server which had a network problem sending an NTP packet, if such an unlikely
event occurs. Internal use.

18. The port which had a network problem sending an NTP packet, if such an unlikely event occurs.
Internal use.

19. Maximal time in microseconds between getting a frame and the time it was processed. Internal use.

20. Maximal time in microseconds which until the frame is sent. This may affect accuracy. Internal use.

## 3229 LEVEL = 255

NTP levels:
-----------
Level 0 - NTP Parameters
Level 1 - NTP state
Level 2 - NTP servers
Level 3 - Current time zone
Level 4 - NTP resolved servers
Level 10- Get & clear statistics
Level 11- Get statistics
Level 255- This list

This lists all diagnostics provided for the device at all its supported levels.

189
 Software Diagnostics Output

DUART

## 3230 LEVEL = 0
Duart 's Hardware Internal Registers :-
------------------------------------------
Internal software data (key) (DATA) : %%1
DTR Register pointer (DTR) : %%2
DTR Mask (DTR Mask) : %%3
RTS Register pointer (RTS) : %%4
RTS Mask (RTS Mask) : %%5
CONTROL Register pointer (CONTROL) : %%6
RX Register pointer (RX) : %%7
TX Register pointer (TX) : %%8
MRBLR - Max RX Length (MRBLR) : %%9
CONTROL Register Data (*CONTROL) : %%10
DTR Register Data (*DTR) : %%11
RTS Register Data (*RTS) : %%12
RX Register Data (*RX) : %%13
TX Register Data (*TX) : %%14
Close Char (Close Char): %%15
Max idles Counter (MX_IDL) : %%16

1. Pointer to the UART Device key.

2. The address of DTR in the Hardware.

3. The Mask of DTR.

4. The address of RTS in the Hardware.

5. The Mask of RTS.

6. The address of the CONTROL REGISTER in the Hardware.

7. The address of RX REGISTER in the Hardware.

8. The address of TX REGISTER in the Hardware.

9. Maximum Receive Length.

10. The Data in the Control Register.

11. The Data in DTR Register

12. The Data in RTS Register

13. The Data in RX Register

14. The Data in TX Register

15. Close Character to close received buffer.

16. Maximum idle in msec units to close received frame.

190
 Software Diagnostics Output

## 3231 LEVEL = 1
Duart's Software descriptors :-
--------------------------------------
Head (offset) software receive descriptor: %%1
tail (offset) software receive descriptor: %%2
Head (offset) software transmit descriptor: %%3
tail (offset) software transmit descriptor: %%4
empty software receive descriptor: %%5
ready software receive descriptor: %%6
empty software transmit descriptor: %%7
ready software transmit descriptor: %%8
RX Descriptor[0].flag : %%9
RX Descriptor[0].p_buffer : %%10
RX Descriptor[0].offset : %%11
RX Descriptor[1].flag : %%12
RX Descriptor[1].p_buffer : %%13
RX Descriptor[1].offset : %%14
RX Descriptor[2].flag : %%15
RX Descriptor[2].p_buffer : %%16
RX Descriptor[2].offset : %%17
RX Descriptor[3].flag : %%18
RX Descriptor[3].p_buffer : %%19
RX Descriptor[3].offset : %%20
RX Descriptor[4].flag : %%21
RX Descriptor[4].p_buffer : %%22
RX Descriptor[4].offset : %%23
RX Descriptor[5].flag : %%24
RX Descriptor[5].p_buffer : %%25
RX Descriptor[5].offset : %%26
RX Descriptor[6].flag : %%27
RX Descriptor[6].p_buffer : %%28
RX Descriptor[6].offset : %%29
RX Descriptor[7].flag : %%30
RX Descriptor[7].p_buffer : %%31
RX Descriptor[7].offset : %%32
Tx Descriptor[0].length : %%33
Tx Descriptor[0].p_buffer : %%34
Tx Descriptor[0].offset : %%35
Tx Descriptor[1].length : %%36
Tx Descriptor[1].p_buffer : %%37
Tx Descriptor[1].offset : %%38
Tx Descriptor[2].length : %%39
Tx Descriptor[2].p_buffer : %%40
Tx Descriptor[2].offset : %%41
Tx Descriptor[3].length : %%42
Tx Descriptor[3].p_buffer : %%43
Tx Descriptor[3].offset : %%44
Tx Descriptor[4].length : %%45
Tx Descriptor[4].p_buffer : %%46
Tx Descriptor[4].offset : %%47
Tx Descriptor[5].length : %%48
Tx Descriptor[5].p_buffer : %%49
Tx Descriptor[5].offset : %%50
Tx Descriptor[6].length : %%51
Tx Descriptor[6].p_buffer : %%52
Tx Descriptor[6].offset : %%53
Tx Descriptor[7].length : %%54
Tx Descriptor[7].p_buffer : %%55
Tx Descriptor[7].offset : %%56

191
 Software Diagnostics Output

1. The next buffer to be handled by the Driver for received data.

2. The next buffer to be handled by the System for received data.

3. The next buffer to be handled by the Driver to transmit data.

4. The next buffer to be handled by the System to transmit data.

5. #9-#32 For each Receive buffer (0-7), a flag indicating if the buffer is in use, empty or has errors, a
pointer to the buffer, and the number of bytes that were received.

6. #33-#56 For each Transmit buffer (0-7) the number of bytes to be transmitted, a pointer to the buffer,
and the number of bytes that were transmitted by the driver so far.

## 3232 LEVEL = 2
Duart's Internal RAM data-Device Key :-
------------------------------------------
Current mode parameters (MODE_BACKUP): %%1
Current rate parameters (RATE_BACKUP): %%2
Current sync parameters (SYNC_BACKUP): %%3
Address mask parameters (MASK_BACKUP): %%4
Address data parameters (ADRS_BACKUP): %% %% %% %%5
Current channel's name (CHAN_BACKUP): %%6
Current channel's data (CHAN_DATA) : %%7
Current channel's code (CHAN_CODE) : %%8
Current heap's name (HEAP_BACKUP): %%9
Current heap's name (HEAP_DATA) : %%10
Current heap's data (HEAP_CODE) : %%11
Current channel's port (DUART_PORT) : %%12
Reception data head (RXBD_HEAD) : %%13
Transmission data tail (TXBD_TAIL) : %%14
Communication signals (DUART_SIGNAL): %%15
Communication buffers (DUART_TYPE) : %% %%16
Communication status (NOISY): %% 17
(QUIET): %% 18
Communication preset/timers (GRANT): %% %%19
(QUIET): %% %%20

1. The Uart's mode.

2. The Baud rate.

3. Contains the idle time to close received buffer.

4. Not relevant.

5. All the Legal addresses.

6. Pointer to Channel name.

7. Pointer to Channel device key.

8. Pointer to Channel Pin-Table.

9. Pointer to heap name.

10. Pointer to Heap device key.

192
 Software Diagnostics Output

11. Pointer to Heap Pin-Table.

12. The current port (1-3).

13. Next Reception data (0-7).

14. Communication Signal to identify TXD_END.

15. Next Transmit data (0-7).

16. Sign if formatted or unformatted buffer.

17. Not relevant.

18. Not relevant.

19. Time to occupy channel (preset, current).

20. Timer for Quiet (preset, quiet).

## 3233 LEVEL = 3
Duart's external dialup modem parameters :-
------------------------------------------
Functional Mode (FUNCTIONAL) : %%1
Reception Data lock (RXBD_LOCK) : %%2
Transmission Data lock (TXBD_LOCK) : %%3
Modem Command Lock (COMMAND_LOCK) : %%4
Incoming call Status (INCOMING_CALL) : %%5
Incoming call Counter (SECOND_COUNTER) : %%6
Get line lock Status (GET_LINE_LOCK) : %%7
Connection Status (LINE_LOCK) : %%8

1. The current functional mode (e.g. External modem).

2. Not in use.

3. Not in use.

4. Semaphore while modem is in command mode.

5. Flag for status of incoming call.

6. Counter while trying to dial.

7. Semaphore between dialing and receiving call.

8. Whether line is connected or not.

193
 Software Diagnostics Output

## 3234 LEVEL = 10
Duart's Diagnostic's Transmit/Receive :-
------------------------------------------
No. of Transmitted Frames : %%
No. of Received Frames : %%
No. of Received Frames with errors : %%
Mask of Error in the received frames : %%

1. The number of frames transmitted.

2. The number of frames received.

3. The number of frames received that had errors.

4. The mask of the errors.

All counters are reset after this diagnostic is read.

## 3235 LEVEL = 11
Duart's Diagnostic's Transmit/Receive :-
------------------------------------------
No. of Transmitted Frames : %%
No. of Received Frames : %%
No. of Received Frames with errors : %%
Mask of Error in the received frames : %%

1. The number of frames transmitted.

2. The number of frames received.

3. The number of frames received that had errors.

4. The mask of the errors.

The counters are not reset after reading this diagnostic.

194
 Software Diagnostics Output

DRS485

## 3245 LEVEL = 0
Rs485 hardware/software last status :-
--------------------------------------
Internal software data (key) : %%1
Current mode parameters (MODE_BACKUP): %%2
Current rate parameters (RATE_BACKUP): %%3
Current sync parameters (SYNC_BACKUP): %%4
Current channel port (CHAN_PORT) : %%5
Channel status mode (CHAN_MODE) : %%6
Channel driver lock (CHAN_LOCK) : %%7
Channel signals (CHAN_SIGNAL): %%8
Channel access type (CHAN_ACCESS): %%9
Physical tx_descriptorsize : %%10
DNP Min Random : %%11
DNP Max Random : %%12
DNP Master Bit : %%13
Channel driver type (CHAN_TYPE) : %%14
DNP random register : %%15
Channel Phys Key : %%16
Channel I2Phys Key : %%17
Time Driver Key : %%18

1. Pointer to the Device key of RS485.

2. The RS485's mode BACKUP.

3. Baud rate BACKUP.

4. Bit mask for staggering BACKUP.

5. The current port of RS485.

6. The RS485's mode.

7. Channel is busy.

8. Signals for MTE.

9. Channel access type.

10. Number of descriptors.

11. For DNP.

12. For DNP.

13. For DNP.

14. DATA Type.

15. For DNP.

16. Pointer to UART Device.

195
 Software Diagnostics Output

17. Pointer to i2phys device.

18. Pointer to Timer device key(10 ms).

## 3246 LEVEL = 1
Rs485 hardware control and status :-
--------------------------------------
PORT D Direction : %%
PORT D Data : %%
PORT D Pull up : %%
PORT D Select : %%
PORT F Data : %%
RTS Register : %%
Control Register : %%
RTS Data Register : %%
Control Data Register : %%

ALL are HARDWARE Registers.

## 3247 LEVEL = 2
Rs485 software control and status :-
--------------------------------------
Channel addresses (BASE/CHAN/NEXT/MASK) : %% %% %% %%1
Channel Ack Slot : %%2
Channel status (NOISY): %%3
(QUIET): %%3
Channel preset/timers (OVERRIDE): %% %%4
(RESOLUTE/QUIET): %% %%5
(SHUTUP): %% %%6
(GRANT): %% %%7
(WARMUP): %% %%8
(TRANSMIT): %% %%9
(HOLDUP): %% %%10
(RESPOND): %% %%11

1. All the legal addresses of the RTU.

2. Number of Slots for channel access.

3. Number of msecs that the channel identified quiet/noise.

4. Preset/Current timer to do override.

5. Time resolution of the channel.

6. Timer for Shutup.

7. Max Timer to try to occupy the Channel.

8. Preset/Current time for Warmup.

9. Preset/Current time channel is transmitted.

10. Preset/Current time for Holdup.

196
 Software Diagnostics Output

11. Preset/Current time for Respond.

DHDLC

## 3300 LEVEL = 0
Dhdlc 's Hardware Internal Registers :-
------------------------------------------
Internal software data (key) (DATA) : %%1
RTS Register pointer (RTS) : %%2
Interrupt Register pointer (INTP) : %%3
Receive Register pointer (RX) : %%4
Transmit Register pointer (TX) : %%5
Test Register pointer (TEST> : %%6
Control Register pointer (CONTROL) : %%7
Sample Register pointer (SAMPLE) : %%8
RTS Mask (RTS Mask) : %%9
Current mode parameters (MODE_BACKUP) : %%10
Current rate parameters (RATE_BACKUP) : %%11
Current sync parameters (SYNC_BACKUP) : %%12
Address mask parameters (MASK_BACKUP) : %%13
Address data parameters (ADRS_BACKUP) : %% %% %% %%14
Current channel's data (CHAN_DATA) : %%15
Current heap's name (HEAP_DATA) : %%16
Current channel's port (DHDLC_PORT) : %%17
RTS Register Data (RTS) : %%18

1. Pointer to the HDLC Device key.

2. The address of RTS in the Hardware.

3. The address of the INTERRUPT REGISTER in the Hardware.

4. The address of the RX REGISTER in the Hardware.

5. The address of the TX REGISTER in the Hardware.

6. The address of the TEST REGISTER in the Hardware.

7. The address of the CONTROL REGISTER in the Hardware.

8. The address of the SAMPLE REGISTER in the Hardware.

9. The mask of the RTS.

10. The HDLC Mode.

11. The Baud Rate.

12. Not relevant.

13. Not relevant.

14. The addresses to which this site will respond through this port.

15. Pointer to the Channel device key.

197
 Software Diagnostics Output

16. Pointer to the Heap name.

17. The current port (1-3).

18. . The Data in RTS Register.

198
 Software Diagnostics Output

## 3301 LEVEL = 1
Dhdlc's Software descriptors :-
--------------------------------------
Head (offset) software receive descriptor: %%1
tail (offset) software receive descriptor: %%2
Head (offset) software transmit descriptor: %%3
tail (offset) software transmit descriptor: %%4
empty software receive descriptor: %%5
ready software receive descriptor: %%6
empty software transmit descriptor: %%7
ready software transmit descriptor: %%8
RX Descriptor[0].flag : %%9
RX Descriptor[0].p_buffer : %%10
RX Descriptor[0].offset : %%11
RX Descriptor[1].flag : %%12
RX Descriptor[1].p_buffer : %%13
RX Descriptor[1].offset : %%14
RX Descriptor[2].flag : %%15
RX Descriptor[2].p_buffer : %%16
RX Descriptor[2].offset : %%17
RX Descriptor[3].flag : %%18
RX Descriptor[3].p_buffer : %%19
RX Descriptor[3].offset : %%20
RX Descriptor[4].flag : %%21
RX Descriptor[4].p_buffer : %%22
RX Descriptor[4].offset : %%23
RX Descriptor[5].flag : %%24
RX Descriptor[5].p_buffer : %%25
RX Descriptor[5].offset : %%26
RX Descriptor[6].flag : %%27
RX Descriptor[6].p_buffer : %%28
RX Descriptor[6].offset : %%29
RX Descriptor[7].flag : %%30
RX Descriptor[7].p_buffer : %%31
RX Descriptor[7].offset : %%32
Tx Descriptor[0].length : %%33
Tx Descriptor[0].p_buffer : %%34
Tx Descriptor[0].offset : %%35
Tx Descriptor[1].length : %%36
Tx Descriptor[1].p_buffer : %%37
Tx Descriptor[1].offset : %%38
Tx Descriptor[2].length : %%39
Tx Descriptor[2].p_buffer : %%40
Tx Descriptor[2].offset : %%41
Tx Descriptor[3].length : %%42
Tx Descriptor[3].p_buffer : %%43
Tx Descriptor[3].offset : %%44
Tx Descriptor[4].length : %%45
Tx Descriptor[4].p_buffer : %%46
Tx Descriptor[4].offset : %%47
Tx Descriptor[5].length : %%48
Tx Descriptor[5].p_buffer : %%49
Tx Descriptor[5].offset : %%50
Tx Descriptor[6].length : %%51
Tx Descriptor[6].p_buffer : %%52
Tx Descriptor[6].offset : %%53
Tx Descriptor[7].length : %%54
Tx Descriptor[7].p_buffer : %%55
Tx Descriptor[7].offset : %%56

199
 Software Diagnostics Output

1. The next buffer to be handled by the Driver for received data.

2. The next buffer to be handled by the System for received data.

3. The next buffer to be handled by the Driver to transmit data.

4. The next buffer to be handled by the System to transmit data.

5. Number of empty receive buffers.

6. Number of receive buffers in use.

7. Number of empty transmit buffers.

8. Number of transmit buffers in use.

9. #9-#32 For each Receive buffer (0-7), a flag indicating if the buffer is in use, empty or has errors, a
pointer to the buffer, and the number of bytes that were received.

10. #33-#56 For each Transmit buffer (0-7) the number of bytes to be transmitted, a pointer to the buffer,
and the number of bytes that were transmitted by the driver so far.

## 3302 LEVEL = 10
Dhdlc's Diagnostic's Transmit/Receive :-
------------------------------------------
No. of Transmitted Frames : %%1
No. of Received Frames : %%2
No. of Received Frames with errors : %%3
Mask of Error in the received frames : %%4

5. The number of frames transmitted.

6. The number of frames received.

7. The number of frames received that had errors.

8. The mask of the errors.

All counters are reset after this diagnostic is read.

## 3303 LEVEL = 11
Dhdlc's Diagnostic's Transmit/Receive :-
------------------------------------------
No. of Transmitted Frames : %%
No. of Received Frames : %%
No. of Received Frames with errors : %%
Mask of Error in the received frames : %%

1. The number of frames transmitted.

2. The number of frames received.

3. The number of frames received that had errors.

4. The mask of the errors.

200
 Software Diagnostics Output

The counters are not reset after this diagnostic is read.

DRADIO

## 3310 LEVEL = 0
Dradio Channel Parameters :-
--------------------------------------
Internal software data (key) : %%1
Current mode parameters (MODE_BACKUP): %%2
Current rate parameters (RATE_BACKUP): %%3
Current sync parameters (SYNC_BACKUP): %%4
Current channel port (CHAN_PORT) : %%5
Channel driver lock (CHAN_LOCK) : %%6
Channel signals (CHAN_SIGNAL): %%7
Channel access type (CHAN_ACCESS): %%8

1. Pointer to the Device key of DRADIO.

2. The RS485's mode BACKUP.

3. Baud rate BACKUP.

4. Bit mask for staggering BACKUP.

5. The current communication port of the RTU (1-3).

6. Channel is busy.

7. Signals for MTE.

8. Channel access type.

201
 Software Diagnostics Output

## 3311 LEVEL = 1
Dradio hardware control and status :-
--------------------------------------
RTS Register : %%1
Control Register : %%2
Interrupt Register : %%3
Modem Control0 Register : %%4
Modem Control1 Register : %%5
RTS Mask : %%6
Modem Control0 Mask : %%7
Modem Control1 Mask : %%8
Warmup type0 : %%9
Warmup type1 : %%10
Preamble type0 : %%11
Preamble type1 : %%12
Radio Default Channel : %%13
Modem type : %%14
Radio type : %%15
Is Internal : %%16
Cm_rssi : %%17
Tx_level : %%18
Is_Agc_on : %%19
Rxa_rssi : %%20
Tx_float : %%21
Diff_ptt_Tx : %%22
Diff_ptt_Rx : %%23
Rssi_level : %%24
Cm_polarity : %%25

1. Pointer to the RTS Hardware's Register.

2. Pointer to the Control Hardware's Register.

3. Pointer to the Interrupt Hardware's Register.

4. Contents of the register which contains Modem Control0 status. Modem Control0 is one of the
lines from the microprocessor (pin PK4) which control the output data from the FPGA's modem
to the radio.

5. Contents of the register which contains Modem Control1 status. Modem Control1 is one of the
lines from the microprocessor (pin PK3) which control the output data from the FPGA's modem
to the radio.

Each set of register values corresponds to a given status, as follows:

Status CTRL1\ CTRL0\ Notes

PK4 PK3
Transmitted 0 0
data
Automatic/ 0 1 Automatic mode - The FPGA performs a full channel
pseudo data access when the RTS line is reset from the
microprocessor . That means : 30mSec DC 10mSec
Sinus and at least 10mSec pseudo data after that it
transmits the data received from the processor or if
no data (all zeros) it continues transmitting pseudo
202
 Software Diagnostics Output

data.
Stop at DC 1 0 When the RTS line is asserted, the FPGA transmits
DC until the status of the control lines is changed.
Stop at sinus 1 1 When the RTS line is asserted the FPGA transmits
DC for 30mSec. Then it starts transmitting a sinus
wave until the RTS line is lowered.
6. The mask of the RTS.

7. Mask of Modem Control0.

8. Mask of Modem Control0.

9. Selects the transmit mode of Modem control 0, when performing warmup in channel access in
port 3.

10. Selects the transmit mode of Modem control 1, when performing warmup in channel access in
port 3.

11. Selects the transmit mode of Modem control 0, when performing preamble in channel access in
port 3.

12. Selects the transmit mode of Modem control 1, when performing preamble in channel access in
port 3.

13. When the MOSCAD-M is configured to work with an internal Mobat radio on Port 3, this
parameter indicates the default channel (1-7) that the radio is programmed to transmit and receive
from. This channel could be changed by the ‘C’ application or by downloading a new
configuration with a new default channel.

14. This indicates the type of modem that is downloaded to the FPGA. The type can be one of:

• Dual Binary 9600 bps modem

• DPSK 1200 bps modem

15. This indicates to the system what type of radio is connected to Port 3 of the MOSCAD-M. This
value can either be Internal Radio or a variety of external radios.

16. This indicates whether the radio connected to Port3 of the MOSCAD-M is an internal or external
radio.

17. This bit indicates the channel busy indication from the radio.

• 0 - CM is originated from RSSI signal of the radio

• 1 - CM is originated from Q_SQE of the radio.

18. This field determines the TxA signal Level (The analog signal from the modem to the radio). The
higher the number in this field, the higher the deviation will be. This is a 6 bit parameter.

19. Indicator from FPGA controlled in FPGA out train via SPI 2.

• 0 - AGC for external portables enabled.

• 1 - Direct receive path is selected.

203
 Software Diagnostics Output

20. This indicates which line from the internal radio connector is routed to the RSSI mechanism.

• 0 - The RxA line is routed to the RSSI mechanism.

• 1 - The RSSI line from the internal radio connector is routed to the RSSI mechanism.

21. This bit determines the input impedance of the Tx_Lines.

• 0 - GND is not connected to External Radio Tx line for external radios that require low
impedance between the TX_line and the ground in order to transmit.
• 1 - GND is connected to External Radio Tx line.

22. This bit determines the differential on the Tx_Line in Transmit mode when using external radios.
This will cause external radios that are sensitive to differential on their Tx line to start
transmitting.

• 1 - This line is always off. Full Tx Level to External radio.

• 0 -This line is connected to the PTT line and is ON/OFF according to the PTT. This means
that when transmitting there is low Impedance and low Tx level when using GRI portable
radios.

23. This bit determines the differential on TX Line in receive mode.

• 1 - OFF
• 0 - ON

24. This parameter determines the comparator level to the RSSI input from the radio.

25. This bit is programmed by the CPU according to the radio's CM polarity which is configured in
the site configuration. It affects both the translation of Carrier Squelch and RSSI / CM to the
CPU.

• 0 - CM polarity in site configuration was programmed to Active Low. That means that the
FPGA recognizes level low on RSSI/SQE as channel active. The signal is inverted in this
mode before being transferred to the CPU.
• CM polarity in site configuration was programmed to Active High. That means that the
FPGA recognizes level high on RSSI/SQE pin as channel active. This signal is NOT inverted
in this mode before being transferred to the CPU.

204
 Software Diagnostics Output

## 3312 LEVEL = 2
Dradio software control and status :-
--------------------------------------
Channel addresses (BASE/CHAN/NEXT/MASK) : %% %% %% %%1
Channel Ack Slot : %%2
Channel status (NOISY) : %%3
(QUIET) : %%3
Channel preset/timers (OVERRIDE) : %% %%4
(RESOLUTE/QUIET) : %% %%5
(SHUTUP) : %% %%6
(GRANT) : %% %%7
(WARMUP) : %% %%8
(TRANSMIT) : %% %%9
(HOLDUP) : %% %%10
(RESPOND) : %% %%11
(PREAMBLE): %% %%12

1. All the legal addresses of the RTU.

2. Number of Slots for channel access.

3. Number of msecs that the channel identified quiet/noise.

4. Preset/Current timer to do override.

5. Time resolution of the channel.

6. Timer for Shutup.

7. Max Timer to try to occupy the Channel.

8. Preset/Current time for Warmup.

9. Preset/Current time channel is transmitted.

10. Preset/Current time for Holdup.

11. Preset/Current time for Respond.

12. Preset/Current time for Preamble.

205
 Software Diagnostics Output

LOGFLAS

## 3361 LEVEL = 1
LOGFLASH queue header
---------------------
start %%1
end %%2
head %%3
tail %%4
element size %%5
num elements %%6
free elements %%7

1. The beginning of the LOGFLASH operation queue.

2. The end of the LOGFLASH operation queue.

3. The head of the LOGFLASH operation queue (the next operation on the LOGFLASH queue to be
performed.)

4. The tail of the LOGFLASH operation queue (the last operation on the LOGFLASH queue to be
performed.)

5. The size of an element on the LOGFLASH queue.

6. The number of elements in the LOGFLASH queue.

7. The number of free elements in the LOGFLASH queue.

## 3363 LEVEL = 0
LOGFLASH status (Write/Append/Remove):
--------------------------------------
Current operated operation - %%1
Current file name - %%2
Last completed operation - %%3
Last file name - %%4
Last result - %%5

1. The current logging flash operation. Can be one of Erase All(1), Write(2), Append(3) and Erase File
(4).

2. The name of the file on which the current logging flash operation is being performed.

3. The last completed operation on the logging flash.

4. The name of the file in the logging flash on which the last completed operation was performed.

5. The result of the last completed operation in the logging flash.

206
 Software Diagnostics Output

## 3364 LEVEL = 2
LOGFLASH queue elements (Write/Append/Remove):
----------------------------------------------
Operation Data_ptr Data_len File_name

This table lists represents all of the access requests to logging flash which are accumulated to a queue

Operation The operation to be performed on the logging flash. One of: Write, Append and Remove.

Data_ptr A pointer to the logging data to be used in theWrite/Append logging flash operation.

Data_len The length of the data to be used in theWrite/Append logging flash operation.

File_name The name of the logging flash file on which the operation is to be performed.

## 3365 LEVEL = 3 (ACE3600)

LOGFLASH buffers in use:
----------------------------------
Data_ptr Data_len

Lists the address and length of each logging request buffer in the queue.

Data_ptr A pointer to the logging data to be used in theWrite/Append logging flash operation.

Data_len The length of the data to be used in theWrite/Append logging flash operation.

## 3366 LEVEL = 3 (IRRInet-M)

Serial number burned - %%1
No. of logging flash instances - %%2 -
- %%

1. Is the serial number was burn (Yes / No)

2. How many times the serial number was burned.

3. The serial number.

207
 Software Diagnostics Output

ACE_LED

## 3370 LEVEL = 255

Menu for ACE LEDS
-----------------
Level 1 - Get current state of all LEDS
Level 2 - Get LEDS private attributes
Level 255 - This menu

## 3371 LEVEL = 1
Current State of all LEDS
-------------------------

Index Colour Blinking

A table of the current state of all LEDS with the following columns:

Index – The index of the LED. 0 is the power LED, up to 21 (USER LED # 4)

Colour – The current color of the LED. 0 = OFF, 1 = RED, 2 = GREEN, 3 = ORANGE

Blinking – Is the LED blinking? 0 = NO, 1 = YES

## 3372 LEVEL = 2
LEDS Private Attributes
-----------------------

LEDS work mode (is in HW Test?) : %%1

Index Colours Users Blink Counter Blink Duration Elapsed Time ON

1. Whether the LEDS are currently in HW Test? 0 = NO, 1 = YES

A table of the LEDS private attributes with the following columns:

Index – The index of the LED. 0 is the power LED, up to 21 (USER LED # 4)

Colours – All possible colors of the LED, 2 = GREEN, 3 = GREEN + RED + ORANGE

Users – LED permitted users: 1 = SYSTEM, 3 = SYSTEM + USER

Blink Counter – Count down counter. When it becomes zero, the LED's state is toggled.

Blink Duration – In case of blinking, the time duration between toggling the LED’s state (in
milliseconds).

Elapsed Time ON – Elapsed time that the LED is ON (in milliseconds). -1 = FOREVER

208
 Software Diagnostics Output

ERRLOG

## 3410 LEVEL = 0
Errors log file pointer: %%1
Errors log current file size: %%2
Errors log file maximum size: %%3
Errors queue maximun size: %%4
Errors log file 'almost full' percentage: %%5
Errors log file delete mode: %%6
Errors logger logical channel No.: %%7
'Poll frames errors' function address: %%8
'Parse frames errors' function address: %%9

Flash memory error logger file in indicators:

1. Pointer to the error log file in flash memory.

2. Actual size of the error logger file in flash memory.

3. Maximum size of the error logger file in flash memory.

4. Maximum size of the queue used to accumulate errors before writing them to the error logger file.

5. How full the Error Logger file in the Flash memory (in percentage) must be before an ‘Almost Full’
warning is sent to the system. Corresponds to the STS Almost full value advanced parameter.

6. Error logger file delete mode: Can be either: by user or automatic.

7. The channel number used by the error logger. Internal use only.

8. Whether the “poll frame errors” function is initialized. Internal use only.

9. Whether the “Parse frames errors” function is initialized. Internal use only.

## 3411 LEVEL = 1
Number of errors not written to file because it was full: %%1
Number of errors not written to queue because it was full: %%2
Number of errors in file: %%3
Errors flag: %%4
Number of warnings in file: %%5
Warnings flag: %%6
Number of messages in file: %%7
Messages flag: %%8
Number of errors with wrong format (not written in queue): %%9

1. The number of errors which could not be written to the error logger file in flash memory because it
has reached its maximum size.

2. The number of errors which could not be written to the error logger queue because it has reached its
maximum size.

3. The total number of errors written to the error logger file.

4. Flag which indicates that errors exist in the file.

209
 Software Diagnostics Output

5. The total number of warnings written to the error logger file.

6. Flag which indicates that warnings exist in the file.

7. The total number of messages written to the error logger file.

8. Flag which indicates that messages exist in the file.

9. The number of errors which had the wrong format and therefore were not written to the queue.

## 3412 LEVEL = 2
Last added error level: %%1
Last polling client ID: %%2
Last polled error: %%3
Delete file after poll: %%4
Offset of next error to poll: %%5
Last poll done by: %%6

Specifies indicators about error logger after push/poll (from PC / from C application)

1. Level of the last added error (error, warning, message)

2. The ID of the last task (STS Error Logger/‘C’ application) to poll the error logger.

3. The serial number of the last error in the error logger file to be polled.

4. Whether the file should be deleted after being polled.

5. The offset in the error logger file of the next error to poll.

6. The indication of who performed the last poll. Can be one of:
"SESSION" (STS Error Logger utility)
"NONE" None polled errors or error file was deleted after poll
"GET_ERROR" (MOSCAD_get_error())

## 3414 LEVEL = 20, 21

Frame Num error logger comm. errors
%% %%

For each I/O expansion frame, the number of communication errors which occurred when the main frame
tried to collect error messages from the I/O expansion error logger.
Level 20 retrieves and clears the data, level 21 retrieves the data.

210
 Software Diagnostics Output

## 3416 LEVEL = 255

Error logger levels information:
Level 0 - General information
Level 1 - Error flag
Level 2 - Information of the last error
Level 3 - Error pipe
Level 10 - Errors queue
Level 20 - Clean expansion module fail comm error
Level 21 - Expansion module fail comm error
Level 100 - FD standart output default
Level 101 - FD standart output pipe maintained by error logger
Level 110 - FD standart error default
Level 101 - FD standart error pipe maintained by error logger
Level 120 - Delete pipe maintained
Level 121 - Add pipe maintained
Level 255 - This list

This lists all diagnostics provided for the device at all its supported levels.

I2C

## 3600 LEVEL = 0
I2C Config Params and creation data :
-------------------------------------
Internal software data (key) (DATA) : %%
Busy semaphore address : %%
I2C task semaphore address : %%
Send semaphore address : %%
Receive semaphore address : %%
Receive buffer descriptor address (RXBD) : %%
Transmit buffer descriptor address (TXBD) : %%
I2C Parameter RAM base address : %%
I2C baud rate : %%
Is MSB transmitted first (normal bit order) : %%
MRBLR - Max RX Buffer Length (MRBLR) : %%
I2C task stack size : %%
I2C task priority : %%
Is memory snooping enabled : %%
I2C task Id : %%
I2C input BRG Frequency : %%

General - Config parameters

211
 Software Diagnostics Output

## 3601 LEVEL = 1
Current status and last operation parameters :
----------------------------------------------
Last Address : %%
Last Buffer address : %%
Callback address : %%
User pointer : %%
Is I2C busy : %%
Timeout counter value : %%
Number of bytes in last transfer : %%
Status of last transfer : %%
Is last operation Tx : %%
Is last operation Sync : %%
Current value of events register (curr_events) : %%
Last value of events register (last_events) : %%
"Old" value of events register (old_events) : %%

Last transmission data.

## 3610 LEVEL = 10
I2C Rx and Tx Statistics - Report and CLEAR :
---------------------------------------------
Total Number of Tx Requests : %%
Total Number of Sync Tx Requests : %%
Total Number of Async Tx Requests : %%
Total Number of Successful Tx Requests : %%
Total Number of Tx Failures : %%
Total Number of NAK Tx Failures : %%
Total Number of UNDRN Tx Failures : %%
Total Number of COLL Tx Failures : %%
Total Number of Timeout Tx Failures : %%
Total Number of Rejected Tx Requests - sys busy : %%
Total Number of Rejected Tx Requests - bus busy : %%

Total Number of Rx Requests : %%

Total Number of Sync Rx Requests : %%
Total Number of Async Rx Requests : %%
Total Number of Successful Rx Requests : %%
Total Number of Rx Failures : %%
Total Number of OVERN Rx Failures : %%
Total Number of Timeout Rx Failures : %%
Total Number of Rejected Rx Requests - sys busy : %%
Total Number of Rejected Rx Requests - bus busy : %%

Get and reset statistics.

212
 Software Diagnostics Output

## 3611 LEVEL = 11
I2C Rx and Tx Statistics - Report - NO CLEAR :
----------------------------------------------
Total Number of Tx Requests : %%
Total Number of Sync Tx Requests : %%
Total Number of Async Tx Requests : %%
Total Number of Successful Tx Requests : %%
Total Number of Tx Failures : %%
Total Number of NAK Tx Failures : %%
Total Number of UNDRN Tx Failures : %%
Total Number of COLL Tx Failures : %%
Total Number of Timeout Tx Failures : %%
Total Number of Rejected Tx Requests - sys busy : %%
Total Number of Rejected Tx Requests - bus busy : %%

Total Number of Rx Requests : %%

Total Number of Sync Rx Requests : %%
Total Number of Async Rx Requests : %%
Total Number of Successful Rx Requests : %%
Total Number of Rx Failures : %%
Total Number of OVERN Rx Failures : %%
Total Number of Timeout Rx Failures : %%
Total Number of Rejected Rx Requests - sys busy : %%
Total Number of Rejected Rx Requests - bus busy : %%

Get statistics.

## 3612 LEVEL = 255

Menu for I2C
------------
Level 0 - General - Config params
Level 1 - Last transmission data
Level 10 - Get and reset statistics
Level 11 - Get statistics
Level 255 - This menu

This lists all diagnostics provided for the device at all its supported levels.

213
 Software Diagnostics Output

RS485

## 3620 LEVEL = 0
Power Quicc RS485 Config Params and creation data :
---------------------------------------------------
Channel software data (key) (DATA) : %%
Channel mode (mode_bits) : %%
Channel baud rate (baud_rate_value) : %%
Channel sync (bits_for_staggering) : %%
Channel "external" port number (starts from 1) : %%
Channel "internal" port number (starts from 0) : %%
Channel driver lock (chan_lock) : %%
Channel SW signals (chan_signal) : %%
Channel access type (chan_access) : %%
Channel min random (min_random) : %%
Channel max random (max_random) : %%
Channel dnp master bit (dnp_master_bit) : %%
Channel tx was aborted (tx_was_aborted) : %%
Channel random_init (random_init) : %%
Channel random_calc (random_calc) : %%

Channel random_register (random_register) : %%

Channel phys_dev_key (phys_dev_key) : %%
Channel i2phys_dev_key (i2phys_dev_key) : %%
Channel timer_dev_key (timer_dev_key) : %%
Channel time resolution (units_num_to_wake_on) : %%
Channel phys TX routine (physical_trans_routine) : %%

Channel pin_table_ptr (pin_table_ptr) : %%

Channel calc_res_time (calc_res_time) : %%
Channel hw_uart_dev_key (hw_uart_dev_key) : %%
Channel hw_uart_pin_table (hw_uart_pin_table) : %%

Channel Tx LED number (tx_led_num) : %%

Channel Rx LED number (rx_led_num) : %%
Channel CM LED number (cm_led_num) : %%

General – Configuration parameters.

214
 Software Diagnostics Output

## 3621 LEVEL = 1
Power Quicc RS485 Channel Addresses and Timers :
------------------------------------------------

Channel addresses (CHAN/BASE/NEXT/MASK) : %% %% %% %%

Channel num_of_ack_slots (num_of_ack_slots) : %%

Channel status (NOISY) : %%

(QUIET) : %%
Channel preset/timers (OVERRIDE) : %% %%
(RESOLUTE/QUIET) : %% %%
(SHUTUP) : %% %%
(GRANT) : %% %%
(WARMUP) : %% %%
(TRANSMIT) : %% %%
(HOLDUP) : %% %%
(RESPOND) : %% %%

Channel Addresses and Timers information.

## 3622 LEVEL = 255

Menu for Power Quicc RS485 :
----------------------------
Level 0 - General - Config params
Level 1 - Channel Addresses and Timers
Level 255 - This menu

This lists all diagnostics provided for the device at all its supported levels.

215
 Software Diagnostics Output

UART

## 3630 LEVEL = 0
UART software device key info :
-------------------------------

UART software data (key) (DATA) : %%

UART input mode bits (input_mode_bits) : %%
UART internal mode bits (internal_mode_bits) : %%
UART max idle value (max_idl_value) : %%
UART orig max idle value (orig_max_idl_value) : %%
UART baud rate value (baud_rate_value) : %%
UART "external" port number (starts from 1) : %%
UART "internal" port number (starts from 0) : %%
UART buffer type (uart_buffer_type) : %%
UART num of Tx BDs (tx_descriptor_size) : %%
UART num of Rx BDs (rx_descriptor_size) : %%

UART Tx BDs base address (p_tx_bd) : %%

UART Rx BDs base address (p_rx_bd) : %%

UART Rx control character 1 (char_backup[0]) : %%

UART Rx control character 2 (char_backup[1]) : %%
UART Rx control character 3 (char_backup[2]) : %%
UART Rx control character 4 (char_backup[3]) : %%
UART Rx control character 5 (char_backup[4]) : %%
UART Rx control character 6 (char_backup[5]) : %%
UART Rx control character 7 (char_backup[6]) : %%
UART Rx control character 8 (char_backup[7]) : %%
UART Tx fast character (toseq_char_backup) : %%

UART preset timeouts (uart_preset_timeouts)(QUIET) : %%

(GRANT) : %%
UART software signal (uart_sw_signal) : %%

UART Rx time stamp 1 (rx_time_stamp_ptr[0]) : %%

UART Rx time stamp 2 (rx_time_stamp_ptr[1]) : %%
UART Rx time stamp 3 (rx_time_stamp_ptr[2]) : %%
UART Rx time stamp 4 (rx_time_stamp_ptr[3]) : %%
UART Rx time stamp 5 (rx_time_stamp_ptr[4]) : %%
UART Rx time stamp 6 (rx_time_stamp_ptr[5]) : %%
UART Rx time stamp 7 (rx_time_stamp_ptr[6]) : %%
UART Rx time stamp 8 (rx_time_stamp_ptr[7]) : %%

UART Tx wait semaphore (wait_tx_sem) : %%

UART Warmup semaphore (warm_up_sem) : %%
UART "55" buffer address (p_buf_55) : %%
UART "55" buffer length (buf_55_len) : %%

UART Rx buffer free format (p_freeformat_rx_buff) : %%

UART HW device key (hw_uart_dev_key) : %%
UART HW pin table (hw_uart_pin_table]) : %%
UART channel device name (chan_dev_name) : %%
UART heap device name (heap_dev_name) : %%
UART channel device key (chan_dev_key) : %%
UART orig adap device key (original_adap_dev_key) : %%
UART heap device key (heap_dev_key) : %%

216
 Software Diagnostics Output

UART adaptor device key (adap_dev_key) : %%

UART i2phys device key (i2phys_dev_key) : %%
UART adaptor name (adap_name) : %%

UART adap time sync func (adap_time_sync_fun) : %%

UART GPS func (gps_func) : %%
UART channel pin table (chan_pin_table) : %%
UART cache funcs (uart_cache_funcs) : %%

UART RxBD lock semaphope (rxbd_lock) : %%

UART TxBD lock semaphope (txbd_lock) : %%
UART device lock semaphope (uart_lock) : %%

UART Rx BDs free address (rxbd_free) : %%

UART Rx BDs head address (rxbd_head) : %%
UART Tx BDs tail address (txbd_tail) : %%

UART is RS485 multidrop? (is_rs485_multidrop) : %%

UART is RS232 multidrop? (is_rs232_multidrop) : %%
UART time sync send (time_sync_send) : %%

UART is DTR ignored? (ignore_dtr) : %%

UART is RTS ignored? (ignore_rts) : %%
UART is CD ignored? (ignore_cd) : %%
UART is CTS ignored? (ignore_cts) : %%

UART is RTS on? (is_rts_on) : %%

UART is send 55 required? (send_55_required) : %%
UART is RTS always on? (rts_is_always_on) : %%
UART is in xon/xoff mode? (is_in_xon_xoff_mode) : %%
UART is snooping enabled? (is_snooping_enabled) : %%

UART Tx LED number (tx_led_num) : %%

UART Rx LED number (rx_led_num) : %%
UART CM LED number (cm_led_num) : %%

UART is in test mode? (is_in_test) : %%

PowerQuicc UART - Device key data

217
 Software Diagnostics Output

## 3631 LEVEL = 1
UART Detailed buffer descriptors information :
----------------------------------------------

Status Length Buffer

Receive buffer descriptor 0 (RXBD0): %% %% %%
Receive buffer descriptor 1 (RXBD1): %% %% %%
Receive buffer descriptor 2 (RXBD2): %% %% %%
Receive buffer descriptor 3 (RXBD3): %% %% %%
Receive buffer descriptor 4 (RXBD4): %% %% %%
Receive buffer descriptor 5 (RXBD5): %% %% %%
Receive buffer descriptor 6 (RXBD6): %% %% %%
Receive buffer descriptor 7 (RXBD7): %% %% %%

Transmit buffer descriptor 0 (TXBD0): %% %% %%

Transmit buffer descriptor 1 (TXBD1): %% %% %%
Transmit buffer descriptor 2 (TXBD2): %% %% %%
Transmit buffer descriptor 3 (TXBD3): %% %% %%
Transmit buffer descriptor 4 (TXBD4): %% %% %%
Transmit buffer descriptor 5 (TXBD5): %% %% %%
Transmit buffer descriptor 6 (TXBD6): %% %% %%
Transmit buffer descriptor 7 (TXBD7): %% %% %%

PowerQuicc UART - Detailed buffer descriptors data

## 3632 LEVEL = 2
UART Brief buffer descriptors information :
-------------------------------------------

UART software data (key) (DATA) : %%

UART "external" port number (starts from 1) : %%
UART RxBD lock semaphope (rxbd_lock) : %%
UART TxBD lock semaphope (txbd_lock) : %%
UART Rx BDs head address (rxbd_head) : %%
UART Rx BDs free address (rxbd_free) : %%
UART Rx current BD index (CUR_RX) : %%
UART Tx current BD index (CUR_TX) : %%
UART Tx BDs tail address (txbd_tail) : %%
UART software signal (uart_sw_signal) : %%
UART Rx BDs base address (p_rx_bd) : %%
UART Tx BDs base address (p_tx_bd) : %%
UART Rx BDs current address (curr_hw_rx_bd) : %%
UART Tx BDs current address (curr_hw_tx_bd) : %%
UART current Rx empty buffers : %%
UART current Rx ready buffers : %%
UART current Tx empty buffers : %%
UART current Tx ready buffers : %%

PowerQuicc UART - Brief buffer descriptors data

218
 Software Diagnostics Output

## 3633 LEVEL = 3
UART SCC device key info :
--------------------------
UART SCC software data (key) (DATA) : %%
UART SCC "external" port number (starts from 1) : %%
UART SCC "internal" port number (starts from 0) : %%
UART SCC scc number (scc_num) : %%
UART SCC internal mode bits (mode_bits) : %%
UART SCC interrupt number (INUM_value) : %%
UART SCC is snooping enabled? (is_snooping_enabled) : %%
UART SCC Rx BDs base address (p_rbase) : %%
UART SCC Tx BDs base address (p_tbase) : %%
UART SCC registers address (p_scc_regs) : %%
UART SCC Parameter RAM address (p_scc_regs) : %%
UART SCC BRGC address (BRGC) : %%
UART SCC CPM base address (pIMMR) : %%
UART SCC input BRG Frequency (brg_freq) : %%
UART SCC Command register sub block (uart_page_sub_block) : %%
UART SCC is CD ignored? (ignore_cd) : %%
UART SCC is CTS ignored? (ignore_cts) : %%

UART SCC hardware device key information.

219
 Software Diagnostics Output

## 3634 LEVEL = 4
UART SCC hardware control and status :
--------------------------------------

UART SCC software data (key) (DATA) : %%

UART SCC Internal HW SCC registers address : %%
UART SCC Internal HW SCC parameters address : %%
UART SCC Internal HW SCC protocol params addr : %%

UART SCC Clock control register (CMXSCR) : %%

UART SCC BRGC address (BRGC) : %%

SCC registers:
GSMR_L : %%
GSMR_H : %%
PSMR : %%
TODR : %%
DSR : %%
SCCE : %%
SCCM : %%
SCCS : %%

SCC parameters:
RBASE : %%
TBASE : %%
RFCR : %%
TFCR : %%
MRBLR : %%
RSTATE : %%
RPTR : %%
RBPTR : %%
RCOUNT : %%
RTEMP : %%
TSTATE : %%
TPTR : %%
TBPTR : %%
TCOUNT : %%
TTEMP : %%
RCRC : %%
TCRC : %%

SCC UART protocol parameters:

MAX_IDL : %%
IDLC : %%
BRKCR : %%
PAREC : %%
FRMEC : %%
NOSEC : %%
BRKEC : %%
BRKLN : %%
UADDR[0] : %%
UADDR[1] : %%
RTEMP : %%
TOSEQ : %%
CHAR[0] : %%
CHAR[1] : %%
CHAR[2] : %%
CHAR[3] : %%
CHAR[4] : %%

220
 Software Diagnostics Output

CHAR[5] : %%
CHAR[6] : %%
CHAR[7] : %%
RCCM : %%
RCCR : %%
RLBC : %%

UART SCC detailed hardware data.

## 3635 LEVEL = 10
UART SCC physical error counters info - Report and CLEAR :
----------------------------------------------------------
Rx parity error counter (PAREC): %%
Rx framing error counter (FRMEC): %%
Rx noise counter (NOSEC): %%
Rx break character counter (BRKEC): %%

UART SCC Get & reset statistics

## 3636 LEVEL = 11
UART SCC physical error counters info - NO CLEAR :
--------------------------------------------------
Rx parity error counter (PAREC): %%
Rx framing error counter (FRMEC): %%
Rx noise counter (NOSEC): %%
Rx break character counter (BRKEC): %%

UART SCC Get statistics

## 3637 LEVEL = 255

Menu for Power Quicc UART :
---------------------------
Level 0 - PQ UART - Dev key data
Level 1 - PQ UART - Detailed BDs data
Level 2 - PQ UART - Brief BDs data
Level 3 - UART SCC HW Device key
Level 4 - UART SCC detailed HW Data
Level 10 - UART SCC Get & reset statistics
Level 11 - UART SCC Get statistics
Level 255 - Diag Levels menu

This lists all diagnostics provided for the device at all its supported levels.

221
 Software Diagnostics Output

RS232

## 3650 LEVEL = 0
Power Quicc RS232 Config Params and creation data :
---------------------------------------------------
Channel software data (key) (DATA) : %%
Channel mode (mode_bits) : %%
Channel baud rate (baud_rate_value) : %%
Channel sync (bits_for_staggering) : %%
Channel "external" port number (starts from 1) : %%
Channel "internal" port number (starts from 0) : %%
Channel driver lock (chan_lock) : %%
Channel SW signals (chan_signal) : %%
Channel access type (chan_access) : %%
Channel min random (min_random) : %%
Channel max random (max_random) : %%
Channel dnp master bit (dnp_master_bit) : %%
Channel cm not exist (no_cm_bit) : %%
Channel tx was aborted (tx_was_aborted) : %%
Channel random_init (random_init) : %%
Channel random_calc (random_calc) : %%

Channel random_register (random_register) : %%

Channel phys_dev_key (phys_dev_key) : %%
Channel i2phys_dev_key (i2phys_dev_key) : %%
Channel timer_dev_key (timer_dev_key) : %%
Channel time resolution (units_num_to_wake_on) : %%
Channel phys TX routine (physical_trans_routine) : %%

Channel pin_table_ptr (pin_table_ptr) : %%

Channel calc_res_time (calc_res_time) : %%
Channel hw_uart_dev_key (hw_uart_dev_key) : %%
Channel hw_uart_pin_table (hw_uart_pin_table) : %%

Channel tx led num (tx_led_num) : %%

Channel rx led num (rx_led_num) : %%
Channel cm led num (cm_led_num) : %%

Power Quicc RS232 General - Config parameters

222
 Software Diagnostics Output

## 3651 LEVEL = 1
Power Quicc RS232 Channel Addresses and Timers :
------------------------------------------------

Channel addresses (CHAN/BASE/NEXT/MASK) : %% %% %% %%

Channel num_of_ack_slots (num_of_ack_slots) : %%

Channel status (NOISY) : %%

(QUIET) : %%
Channel preset/timers (OVERRIDE) : %% %%
(RESOLUTE/QUIET) : %% %%
(SHUTUP) : %% %%
(GRANT) : %% %%
(WARMUP) : %% %%
(TRANSMIT) : %% %%
(HOLDUP) : %% %%
(RESPOND) : %% %%

PowerQuicc RS232 Channel Addresses and Timers

## 3652 LEVEL = 255

Menu for Power Quicc RS232 :
----------------------------
Level 0 - General - Config params
Level 1 - Channel Addresses and Timers
Level 255 - This menu

This lists all diagnostics provided for the device at all its supported levels.

RADIO CHANNEL (RAD1C , RAD2C,…)

## 3660 LEVEL = 0
Radio brief status :-
-------------------------------------
RADIO Channel software key (DEV_KEY) : %%
Communication port (CHAN_PORT) : %%-> %%
Channel busy signals (CHAN_MODE0) : %%
Channel busy signals active low (CHAN_MODE1) : %%
Channel busy signals mask (BUSY_SIGNAL): %%
Channel driver lock (CHAN_LOCK) : %%
Channel signals (CHAN_SIGNAL): %%
Channel access type (CHAN_ACCESS): %%
Channel driver type (CHAN_TYPE) : %%

Brief radio status information.

223
 Software Diagnostics Output

## 3662 LEVEL = 3
Radio device key info :-
-------------------------------------

RADIO Channel software key (DEV_KEY) : %%

Communication port (HDLC_PORT) : %%-> %%
Channel busy signals (CHAN_MODE0) : %%
Channel busy signals active low (CHAN_MODE1) : %%
Channel busy signals mask (BUSY_SIGNAL): %%
Channel driver lock (CHAN_LOCK) : %%
Channel signals (CHAN_SIGNAL): %%
Channel access type (CHAN_ACCESS): %%
Channel driver type (CHAN_TYPE) : %%
Channel addresses (CHAN/NEXT/MASK) : %% %% %%
Channel retry random (RANDOM REGISTER) : %%
Channel hardware device key (HW_PHYS_KEY): %%
Channel hardware pin table (HW_PINTBL) : %%
Channel radio/modem board configuration param: %%
Channel modem parameters - tone_detect_level : %%
Channel modem parameters - rssi_level : %%
Channel modem parameters - tx_level : %%
Channel modem parameters - modem_type : %% -> %%
Channel modem parameters - is cm active low? : %%
Channel modem parameters - is ptt active low?: %%
Channel modem parameters - is it trunk? : %%
Channel was tx aborted ? : %%
Channel warmup phase 1 type : %%
Channel warmup phase 2 type : %%
Channel warmup phase 3 type : %%
Channel status (NOISY): %%
(QUIET): %%
Channel preset/timers (OVERRIDE): %% %%
(RESOLUTE/QUIET): %% %%
(SHUTUP): %% %%
(GRANT): %% %%
(WARMUP): %% %%
(WARMUP PAHSE_1): %% %%
(WARMUP PAHSE_2): %% %%
(WARMUP PAHSE_3): %% %%
(TRANSMIT): %% %%
(HOLDUP): %% %%
(RESPOND): %% %%

Radio channel device key information.

## 3663 LEVEL = 255

RADIO list of diagnostic levels :-
--------------------------------------
0 - Get RADIO brief status
1 - Get RADIO hardware control and status
2 - Buffers descriptors information
3 - Get RADIO device key info
4 - Get RADIO hardware device key info

This lists all diagnostics provided for the device at all its supported levels.

224
 Software Diagnostics Output

## 3664 LEVEL = 3
Radio Trunk device key info :-
-------------------------------------
RADIO Channel software key (DEV_KEY) : %%
Communication port (HDLC_PORT) : %%-> %%
Channel busy signals (CHAN_MODE) : %%
Channel busy signals active low (CHAN_MODE1) : %%
Channel busy signals mask (BUSY_SIGNAL): %%
Channel driver lock (CHAN_LOCK) : %%
Channel signals (CHAN_SIGNAL): %%
Channel access type (CHAN_ACCESS): %%
Channel driver type (CHAN_TYPE) : %%
Channel addresses (CHAN/NEXT/MASK) : %% %% %%
Channel ack slot number (ACK_SLOT) : %%
Channel retry random (RANDOM REGISTER) :%%
Channel hardware device key (HW_PHYS_KEY): %%
Channel hardware pin table (HW_PINTBL) : %%
Channel radio/modem board configuration param: %%
Channel modem parameters - tone_detect_level : %%
Channel modem parameters - rssi_level : %%
Channel modem parameters - tx_level : %%
Channel modem parameters - modem_type : %% -> %%
Channel modem parameters - is cm active low? : %%
Channel modem parameters - is ptt active low?: %%
Channel modem parameters - is it trunk? : %%
Channel was tx aborted ? : %%
Channel warmup phase 1 type : %%
Channel warmup phase 2 type : %%
Channel warmup phase 3 type : %%
Channel status (NOISY) : %%
(QUIET) : %%
(LATCH) : %%
(GRANT) : %%
(ACTIVE) : %%
(NON ACTIVE) : %%

Channel preset/timers (OVERRIDE): %% %%

(RESOLUTE/QUIET): %% %%
(SHUTUP): %% %%
(GRANT): %% %%
(WARMUP): %% %%
(WARMUP PAHSE_1): %% %%
(WARMUP PAHSE_2): %% %%
(WARMUP PAHSE_3): %% %%
(TRANSMIT): %% %%
(HOLDUP): %% %%
(RESPOND): %% %%
(RELEASE): %% %%
(RECEIVE/CHECK): %% %%
(REQUEST): %% %%
(RESTART): %% %%
SmartZone preset
(SHORT_WARMUP): %%
(SMART_MIN) : %%
(SMART_LONG) : %%
(SMART_WARM) : %%
(OFF_SLOT) : %%

225
 Software Diagnostics Output

Radio Trunk device key info.

SFLEVL

## 3700 LEVEL = 1, 2
SFL - Flash image data
----------------------
Image index - %%
Header signature - %%
Header version - %%
Header size - %%
Crc of image - %%
Is image zipped - %%
Image size in flash - %%
Ram capacity for image - %%
Evaluate request - %%
Check CRC on startup req- %%
Check RAM on startup req- %%
Burn index - %%
Temp status flag - %%

Safe firmware download – flash image 1, 2 data.

## 3701 LEVEL = 3
SFL - Device data
-----------------
Is evaluation mode? - %%
Max wait time for burn - %%
Was eval at startup - %%
Watch dog ID - %%
Is watch dog active - %%
Time until 'burn' came - %%
How many 'burn' came - %%
Semaphore ID - %%

Safe firmware download – device data.

226
 Software Diagnostics Output

## 3702 LEVEL = 10
SFL - Flash image data
----------------------
Image index - %%
Header signature - %%
Header version - %%
Header size - %%
Crc of image - %%
Is image zipped - %%
Image size in flash - %%
Ram capacity for image - %%
Evaluate request - %%
Check CRC on startup req- %%
Check RAM on startup req- %%
Burn index - %%
Temp status flag - %%

SFL - Flash image data

----------------------
Image index - %%
Header signature - %%
Header version - %%
Header size - %%
Crc of image - %%
Is image zipped - %%
Image size in flash - %%
Ram capacity for image - %%
Evaluate request - %%
Check CRC on startup req- %%
Check RAM on startup req- %%
Burn index - %%
Temp status flag - %%

SFL - Device data

-----------------
Is evaluation mode? - %%
Max wait time for burn - %%
Was eval at startup - %%
Watch dog ID - %%
Is watch dog active - %%
Time until 'burn' came - %%
How many 'burn' came - %%
Semaphore ID - %%

Safe firmware download – all flash image and device data.

## 3703 LEVEL = 255

SFL - diagnostic menu
---------------------
Level 1 - Image 1 data.
Level 2 - Image 2 data.
Level 3 - Device data.
Level 10 - All.
%%

This lists all diagnostics provided for the device at all its supported levels.

227
 Software Diagnostics Output

SFLLDR

## 3704 LEVEL = 255

SFL Loader - diagnostic menu
---------------------
Level 1 - device data.
Level 2 - last download image header.
Level 10 - All.

This lists all diagnostics provided for the device at all its supported levels.

## 3705 LEVEL = 1
semphore id - %%
current device status - %%
burn addres - %%
image address - %%
number of bytes burned - %%
number of burned slices - %%
number of before - %%
number of after - %%
number of burn - %%

SFL Loader device data.

## 3706 LEVEL = 2
last download image header
--------------------------
image crc - %%
is image zipped - %%
image size - %%
ram capacity - %%
evaluate req - %%
check crc on start up - %%
check ram on start up - %%

Last downloaded image header.

228
 Software Diagnostics Output

SOCKETF

## 3900 LEVEL = 0
Fusionsocket device state
--------------------------
Locked task name : %%
Number of times in locked : %%
Number of sockets for application : %%
Number of threads in socket_send() : %%
Number of threads in socket_recv() : %%
Number of threads in socket_accept() : %%
Number of threads in socket_connect() : %%
Number of threads in socket_shutdown() : %%
Number of threads in socket_close() : %%
Number of threads in socket_select() : %%
Inhibit application from accessing sockets ? : %%
Internal state of module : %%

Registered sockets for application use

---------------------------------------
Last Is Is Src Dest
FD error Flags Options Closing Connected Opened Protocol Address Address
-- ----- ----- ------- ------- --------- ------ -------- ------- -------
%%

Fusionsocket device state.

## 3910 LEVEL = 10, 11

Last socket error returned to application : %%
Number of times application got errors : %%
Number of times new sockets registered for application: %%
Number of times sockets de-registered from application: %%
Number of times socket_bind() succeed : %%
Number of times socket_bind() failed : %%
Number of times socket_connect() succeed : %%
Number of times socket_connect() failed : %%
Number of times socket_accept() succeed : %%
Number of times socket_accept() failed : %%
Number of times socket() succeed : %%
Number of times socket() failed : %%
Number of times socket_shutdown() succeed : %%
Number of times socket_shutdown() failed : %%
Number of times socket_close() succeed : %%
Number of times socket_close() failed : %%
Number of times released socket by force : %%
Number of times released socket : %%
Number of times bytes failed socket_send() : %%
Number of times bytes dropped socket_send() : %%
Number of times bytes sent via socket_send() : %%
Number of times bytes received via socket_recv() : %%

Get/Reset statistics

229
 Software Diagnostics Output

## 3955 LEVEL = 255

level 0 - get key
level 10 - get & reset statistics
level 11 - get statistics

This lists all diagnostics provided for the device at all its supported levels.

SPI

## 4000 LEVEL = 0
SPI Config Params and creation data :
-------------------------------------
Internal software data (manager key) (DATA) : %%
Internal software data (HW SPI key) (DATA) : %%
Maximum number of registered devices : %%
Actual number of registered devices : %%
Registered entities array address : %%
Registry indication array address : %%
Busy semaphore address (manager) : %%
32 bytes aligned Tx buffer address : %%
32 bytes aligned Rx buffer address : %%
Allocated Tx buffer address : %%
Allocated Rx buffer address : %%

HW SPI Details :
----------------
Internal software data (key) (DATA) : %%
Busy semaphore address : %%
Send semaphore address : %%
Receive semaphore address : %%
Cache funcs address : %%
Receive buffer descriptor address (RXBD) : %%
Transmit buffer descriptor address (TXBD) : %%
Internal memory map base address (pIMMR) : %%
SPI Parameter RAM base address : %%
SPI baud rate : %%
SPI clock polarity : %%
SPI clock phase : %%
Is MSB transmitted first (normal bit order) : %%
MRBLR - Max RX Buffer Length (MRBLR) : %%
SPI character length : %%
Is cache enabled : %%
Is memory snooping enabled : %%
SPI input BRG Frequency : %%

SPI General - Config parameters

230
 Software Diagnostics Output

## 4001 LEVEL = 1
Current status and last operation parameters :
----------------------------------------------
Actual number of registered devices : %%
Peripheral Id of last registered entity : %%
Peripheral Id of last user : %%
Chip select of last user : %%
Is last request Tx : %%
Status of last Tx : %%
Status of last Rx : %%
Number of bytes in last transfer : %%
Last Tx Buffer address : %%
Last Rx Buffer address : %%
User function address : %%
User pointer : %%

Registered Entities Details :

-----------------------------
Peripheral Id : %%
Baud rate : %%
Clock polarity : %%
Clock phase : %%
Is MSB transmitted first (normal bit order) : %%
Character length : %%
Is entity registered : %%

Peripheral Id : %%
Baud rate : %%
Clock polarity : %%
Clock phase : %%
Is MSB transmitted first (normal bit order) : %%
Character length : %%
Is entity registered : %%

Peripheral Id : %%
Baud rate : %%
Clock polarity : %%
Clock phase : %%
Is MSB transmitted first (normal bit order) : %%
Character length : %%
Is entity registered : %%

Peripheral Id : %%
Baud rate : %%
Clock polarity : %%
Clock phase : %%
Is MSB transmitted first (normal bit order) : %%
Character length : %%
Is entity registered : %%

Peripheral Id : %%
Baud rate : %%
Clock polarity : %%
Clock phase : %%
Is MSB transmitted first (normal bit order) : %%
Character length : %%
Is entity registered : %%

Peripheral Id : %%

231
 Software Diagnostics Output

Baud rate : %%
Clock polarity : %%
Clock phase : %%
Is MSB transmitted first (normal bit order) : %%
Character length : %%
Is entity registered : %%

HW SPI Details :
----------------
Peripheral Id of last user : %%
Chip select of last user : %%
Number of bytes in last transfer : %%
Last Tx Buffer address : %%
Last Rx Buffer address : %%
Is last request Tx : %%
Current (unhandled yet) events (SPIE) : %%
Latest (already handled) events (SPIE) : %%
Status of last Tx : %%
Status of last Rx : %%

SPI hardware control and status :

------------------------------------

SPI Registers :
---------------
SPI mode register (SPMODE) : %%
SPI event register (SPIE) : %%
SPI mask register (SPIM) : %%

SPI Parameter RAM Memory Map :

------------------------------
RBASE - RxBD table base address : %%
TBASE - TxBD table base address : %%
RFCR - Rx Function code : %%
TFCR - Tx Function code : %%
MRBLR - Max RX Buffer Length : %%
RPTR - Rx internal data pointer : %%
RBPTR - RxBD pointer : %%
RCOUNT - Rx internal byte count : %%
TPTR - Tx internal data pointer : %%
TBPTR - TxBD pointer : %%
TCOUNT - Tx internal byte count : %%

SPI RxBD internal data :

------------------------
Status and control word : %%
Data Length : %%
Buffer Pointer : %%

SPI TxBD internal data :

------------------------
Status and control word : %%
Data Length : %%
Buffer Pointer : %%

SPI Last transmission data

232
 Software Diagnostics Output

## 4010 LEVEL = 10
SPI Rx and Tx Statistics - Report and CLEAR :
---------------------------------------------

Total Number of Tx Requests : %%

Total Number of Successful Tx Requests : %%
Total Number of Tx Failures : %%
Total Number of Timeout Tx Failures : %%
Total Number of Rejected Tx Requests - sys busy : %%
Total Number of Rejected Tx Requests - usr unkn : %%

Total Number of Rx Requests : %%

Total Number of Successful Rx Requests : %%
Total Number of Rx Failures : %%
Total Number of Timeout Rx Failures : %%
Total Number of Rejected Rx Requests - sys busy : %%
Total Number of Rejected Rx Requests - usr unkn : %%

HW SPI Details :
----------------
Total Number of Tx Requests : %%
Total Number of Successful Tx Requests : %%
Total Number of Tx Failures : %%
Total Number of MME Tx Failures : %%
Total Number of UNDRN Tx Failures : %%
Total Number of Timeout Tx Failures : %%
Total Number of Rejected Tx Requests - sys busy : %%

Total Number of Rx Requests : %%

Total Number of Successful Rx Requests : %%
Total Number of Rx Failures : %%
Total Number of OVERN Rx Failures : %%
Total Number of MME Rx Failures : %%
Total Number of Timeout Rx Failures : %%
Total Number of Rejected Rx Requests - sys busy : %%

SPI - Get and reset statistics

233
 Software Diagnostics Output

## 4011 LEVEL = 11
SPI Rx and Tx Statistics - Report - NO CLEAR :
----------------------------------------------

Total Number of Tx Requests : %%

Total Number of Successful Tx Requests : %%
Total Number of Tx Failures : %%
Total Number of Timeout Tx Failures : %%
Total Number of Rejected Tx Requests - sys busy : %%
Total Number of Rejected Tx Requests - usr unkn : %%

Total Number of Rx Requests : %%

Total Number of Successful Rx Requests : %%
Total Number of Rx Failures : %%
Total Number of Timeout Rx Failures : %%
Total Number of Rejected Rx Requests - sys busy : %%
Total Number of Rejected Rx Requests - usr unkn : %%

HW SPI Details :
----------------
Total Number of Tx Requests : %%
Total Number of Successful Tx Requests : %%
Total Number of Tx Failures : %%
Total Number of MME Tx Failures : %%
Total Number of UNDRN Tx Failures : %%
Total Number of Timeout Tx Failures : %%
Total Number of Rejected Tx Requests - sys busy : %%

Total Number of Rx Requests : %%

Total Number of Successful Rx Requests : %%
Total Number of Rx Failures : %%
Total Number of OVERN Rx Failures : %%
Total Number of MME Rx Failures : %%
Total Number of Timeout Rx Failures : %%
Total Number of Rejected Rx Requests - sys busy : %%

SPI - Get statistics

## 4012 LEVEL = 255

Menu for SPI :
--------------
Level 0 - General - Config params
Level 1 - Last transmission data
Level 10 - Get and reset statistics
Level 11 - Get statistics
Level 255 - This menu

This lists all diagnostics provided for the device at all its supported levels.

234
 Software Diagnostics Output

IPPORTS

## 4100 LEVEL = 0
Ipport module version - %%
Device status - %%
Board type - %%
Port#,Device,Usage,DHCP,IP address ,Subnet Mask ,Default GW
,Active, Domain name
------------------------------------------------------------------------------
--------------
%% %%
%% %%
%% %%
%% %%

IPPORTS - All ports data

## 4101 LEVEL = 1, 2, 3, 4
Port %%
Domain %%
Zone %%
Build Domain %%
Unique ID %%
Class Id %%
Notify %%
Lease time %%
Link id %%

IPPORTS - Port configuration data

## 4102 LEVEL = 255

Menu for Ethernet - IPPORTS
Level 0 - Driver information
Level 1 - Plug-In 1 parameters
Level 2 - Plug-In 2 parameters
Level 3 - Ethernet 1 parameters
Level 4 - Ethernet 2 parameters
Level 5 - Ethernet ports status
Level 6 - Ethernet ports config setting
Level 255- This list

This lists all diagnostics provided for the device at all its supported levels.

## 4103 LEVEL = 5
Ethernet ports status:
PortName If-Name Link Auto AutoCompleted Duplex Speed
======== ======= ==== ==== ============= ====== =====
%% %% %% %% %% %% %%

This diagnostic displays the current status of the Ethernet ports installed on the board.

235
 Software Diagnostics Output

PortName Port name (e.g. PI1, PI2, ETH1)

If-Name Interface name of the IP port that is determined by the Ethernet communication driver (e.g.
motfcc1, motfcc2, motscc3).

Link Whether the link is up or down.

Auto Whether the port is in Auto Negotiation mode.

AutoCompleted Auto Negotiation is completed successfully.

Duplex Full or half duplex.

Speed 100Mb or 10 Mb.

## 4104 LEVEL = 6
Ethernet ports config setting:
PortName If-Name Eth# Config Mode
======== ======= ==== ===========

This diagnostic displays the configured settings of the Ethernet ports.

PortName Port name (e.g. PI1, PI2, ETH1)

If-Name Interface name of the port that is determined by the Ethernet communication driver (e.g.
motfcc1, motfcc2, motscc3).

Eth# Ethernet port number.

Config Mode Either Auto (i.e. in Auto Negotiation mode) or Fixed (Speed- either 10Mb or 100Mb +
Half Duplex-HD or Full Duplex-FD.)

E2_INTR

## 4200 LEVEL = 1
E2IF Module information
------------------------
Module version - %%

E2IF Module information.

## 4201 LEVEL = 10, 20

E2IF - Piggyback header
--------------------------------
Port index - %%
Header signature - %%
INI File size - %%
EEPROM Write counter - %%
Checksum - %%

E2IF Piggyback header.

236
 Software Diagnostics Output

## 4202 LEVEL = 11, 21

E2IF - Configuration data
----------------------------------
Port index - %%
Board ID - %%
Default build routine - %%
Driver ID list - %%
HW data string - %%

E2IF Configuration data.

## 4205 LEVEL = 255

Menu for E2IF (Piggyback Configuration information)
---------------------------------------------------
Level 1 - Print Module information
Level 10 - Print the EEPROM header - port 1
Level 11 - Print the Configuration data - port 1
Level 20 - Print the EEPROM header - port 4
Level 21 - Print the Configuration data - port 4
Level 255 - This menu

This lists all diagnostics provided for the device at all its supported levels.

IOSWITCH

## 4615 LEVEL = 255

Levels 0 - 4 SIO layer
------------------------
Level 0 - ID information.
Level 1 - DI information.
Level 2 - DO information.
Level 3 - AI information.
Level 4 - AO information.
Level 5 - Reserved.
Level 6 - Reserved
Level 7 - PDV, KLV & Mask information
Level 255- This list

Levels 10 - 15 PHYSIO layer

------------------------
Level 10 - ID information.
Level 11 - FPGA registers.
Level 12 - FPGA Loggers.
Level 13 - EMI registers.
Level 14 - EE image.
Level 15 - FPGA diagnostic counters.
Level 255- This list.

This lists all diagnostics provided for the device at all its supported levels.

237
 Software Diagnostics Output

## 4626 LEVEL = 5
Switch port general info
------------------------
Number of switch ports: %%
Switch ports size (in bytes): %%

General switch information for up to eight ports.

VXWDMNG

## 4300 LEVEL = 10
Vx_WATCHDOG MANAGER Diagnostic Level 10
==============================
Initial Number of watchdogs : %%1
Total number of watchdogs : %%2
Number of available watchdogs : %%3
Number of On-the-fly allocations (before reset) : %%4
Maximal number of occupied watchdogs (before reset) : %%5

Logs the watchdog quantities (initialized at system start-up, added in run-time, free for use)

1. The number of watchdog timers initialized at system start-up.

2. The total number of watchdog tasks in the system.

3. The number of watchdog timers still available for use.

4. The number of watchdog timers added in run-time. After this diagnostic is polled, this value is reset
to 0.

5. The maximum number of occupied watchdog timers. After this diagnostic is polled, this value is
reset to 0.

## 4301 LEVEL = 11
Vx_WATCHDOG MANAGER Diagnostic Level 11
==============================
Initial Number of watchdogs : %%
Total number of watchdogs : %%
Number of available watchdogs : %%
Number of On-the-fly allocations: %%
Maximal number of occupied watchdogs: %%

Logs the watchdog quantities (initialized at system start-up, added in run-time, free for use)

1. The initial size of the pool of watchdog tasks at system start-up.

2. The total number of watchdog tasks in the system.

3. The number of watchdog tasks still available for use.

238
 Software Diagnostics Output

4. The number of watchdog tasks added in run-time.

5. The maximum number of occupied watchdogs before reset.

These watchdog fields are not reset after these diagnostics are polled.

## 4302 LEVEL = 255

Vx_WATCHDOG MANAGER Diagnostic Level 255
==============================
Diagnostics level 0: Show watchdogs pool size
Diagnostics level 1: Show development variables
Diagnostics level 10: Show and reset variables
Diagnostics level 11: Show variables
Level 255- This list

This lists all diagnostics provided for the device at all its supported levels.

## 4303 LEVEL = 0
Vx_WATCHDOG MANAGER Diagnostic Level 0
==============================
Initial Number of watchdogs : %%1

1. The initial size of the pool of watchdog tasks at system start-up.

## 4304 LEVEL = 1

Vx_WATCHDOG MANAGER Diagnostic Level 1

======================================
Current Number of available watchdogs : %%1

WX_wD pool list elements:

No. NODE_ADDR NODE_NEXT_ADDR NODE_PREV_ADDR USER_ROUTINE_ADDR

WATCHDOG_DESCR_ADDDR
------------------------------------------------------------------------------
------------
% %% %% %% %% %%

1. The number of watchdog tasks still available for use during run-time. The watchdogs are organized
in a linked list.

For each watchdog in the linked list: specify its related linked list node, its linked lists neighbors, the
routine to operate when the watchdog expires and the watchdos VxWorks descriptor.

NODE_ADDR The address of the node in the linked list node for this watchdog.

NODE_NEXT_ADDR The next node in the linked list.

NODE_PREV_ADDR The previous node in the linked list.

239
 Software Diagnostics Output

USER_ROUTINE_ADDR The address of the routine to operate when the watchdog expires.

WATCHDOG_DESCR_ADDR The address of the watchdog VxWorks descriptor.

F_EVNT

## 4350 LEVEL = 0
Fast event feature (F_EVNT software device) disabled by system. : %%1
Fast process execution time limit : %%2
Fast events maximum queue size : %%3
Fast events delays list size : %%4
Max number of fast processes per trigger : %%5
Fast event task stop state : %%6
Number of unprocessed events : %%7
Last executed fast process address : %%8
Last executed fast process function address : %%9

General data about the F_EVNT device configuration parameters and overall execution.

1. Whether the F_EVNT device is supported.

2. The maximum time that the fast process can execute.

3. The maximum size of the queue for fast events.

4. The maximum size of the queue for fast events delays.

5. The maximum number of fast processes that can be associated with a trigger.

6. Fast event task stop state. Can either indicate that the task was never run by the OS after startup, or
the task was stopped (due to stop application) and its run was never renewed.

7. The number of unprocessed events in the fast event queue.

8. The address of the last executed fast process.

9. The address of the last executed fast process function.

## 4351 LEVEL = 1
Last error while fast process execution : %%1
Fast process address : %%2
Error code : %%3
Event type : %%4
Rack-module : %%5
Index : %%6
Direction: : %%7

Because an error that occurs during fast event execution cannot be logged during the execution, its data is
stored under the F_EVNT device.

1. The serial number of the last error to occur during the execution of the fast process.

240
 Software Diagnostics Output

2. The address of the fast process.

3. The error code of the last error which occurred.

4. The event type of the last error which occurred. Can be one of error, warning, message.

5. The location rack/module of the I/O which acts as the fast event trigger.

6. The index of the DI as defined in the I/O link table of the application.

7. The direction of the trigger (DI DOWN/UP/COS, PB UP, Delay)

## 4352 LEVEL = 10, 11

DI triggers

State Process Parms Ram adr Bit ExecTm Max ExecTm #calls #long
runs TmException #EventsNoDB #EventsNoIO LstErr

------------------------------------------------------------------------------
-----------------------------------------------

Table of all DI triggers in the system:

State Whether the trigger is enabled/disabled.

Process The address of the related process

Parms Related parameters passed to the process (by ‘C’ application only.)

Ram adr The address in RAM of the DI serving as a trigger (e.g. DI in the ladder’s database table.)

Bit The bit offset of the DI serving as a trigger from the RAM address.

ExecTm Last execution time of the fast process operated by the trigger.

Max ExecTm The longest execution time of the fast process operated by the trigger of all the times
it was activated.

#calls The number of times the fast process was activated.

#long runs The number of times the fast process execution exceeded the limit of fast process
execution time (as defined in site configuration advanced parameter.)

TmException A flag that indicates the fast process has exceeded the time limit in its last execution.

#EventsNoIO The number of times a fast event occured while the related DI trigger was disabled.

241
 Software Diagnostics Output

## 4354 LEVEL = 20, 21

Push Button triggers

State Process Parms Ram adr Bit ExecTm Max ExecTm #calls #long
runs TmException #EventsNoDB #EventsNoIO LstErr
------------------------------------------------------------------------------
-----------------------------------------------

Table of all pushbutton triggers in the system:

State Whether the trigger is enabled/disabled.

Process The address of the related process

Parms Related parameters passed to the process (by ‘C’ application only.)

Ram adr The address in RAM of the pushbutton serving as a trigger (e.g. PB in the ladder’s
database table.)

Bit The bit offset of the pushbutton serving as a trigger from the RAM address.

ExecTm Last execution time of the fast process operated by the trigger.

Max ExecTm The longest execution time of the fast process operated by the trigger of all the times
it was activated.

#calls The number of times the fast process was activated.

#long runs The number of times the fast process execution exceeded the limit of fast process
execution time (as defined in site configuration advanced parameter.)

TmException A flag that indicates the fast process has exceeded the time limit in its last execution.

#EventsNoIO The number of times a fast event occured while the related pushbutton trigger was
disabled.

## 4355 LEVEL = 255

"level 0 - General\n",
"level 1 - Last error while fast process execution",
"level 10 - DI triggers (clear counters)",
"level 11 - DI triggers",
"level 20 - Push button triggers (clear counters)",
"level 21 - Push button triggers"
"Level 255- This list"

This lists all diagnostics provided for the device at all its supported levels.

242
 Software Diagnostics Output

DHCPCL

## 4400 LEVEL = 255

DHCP Client diagnostics menu:
0 - Module data.
1 - Port 1 data.
2 - Port 2 data.
3 - Port 3 data.
4 - Port 4 data.
5 - Port 5 data.
6 - Port 6 data.
7 - Port 7 data.
......
10 - All ports data.

This lists all diagnostics provided for the device at all its supported levels.

## 4401 LEVEL = 0
Module version - %%
Last active port index - %%
--------------------------------
Port name | Has valid DHCP data
--------------------------------
%% | %%
%% | %%
%% | %%
%% | %%

DHCP Module data.

## 4402 LEVEL = 1
Port %% data.
Is data valid - %%
IP address - %%
Subnet mask - %%
Default router - %%
Lease time - %%
DNS servers address - %%,%%,%%,%%,%%
NTP servers address - %%,%%,%%,%%,%%
Zone name - %%
Domain name - %%
Notify domain flag - %%
FDQN rcode1 - %%
FDQN rcode0 - %%
FDQN MBZNOES response - %%
Vendor info - %%
TFTP server name - %%
Num of invalid call back - %%
Num of renew call back - %%
Cookie Ptr - %%

DHCP Port 1 data.

243
 Software Diagnostics Output

DNSCLI

## 4500 LEVEL = 255

DNS client diagnostic menu
--------------------------
Level 0 - Driver data.
Level 1 - DNS servers list.
Level 255- This list.

This lists all diagnostics provided for the device at all its supported levels.

## 4501 LEVEL = 0
Driver version - %%
Number of DNS servers - %%
Number of forward query - %%
Number of reverse query - %%

DNS driver data.

## 4502 LEVEL = 1
DNS servers list
----------------
%% %% %% %%
%% %% %% %%
%% %% %% %%
%% %% %% %%
%% %% %% %%

List of DNS servers.

DFLTCNF

## 4510 LEVEL = 0
Driver version - %%
Is configuration exist - %%
Configuration file len - %%

Is complement exist - %%
Complement file len - %%

Piggy 1 build routine - %%

Piggy 4 build routine - %%

Default configuration driver data.

244
 Software Diagnostics Output

## 4512 LEVEL = 255

Default configuration module menu
Level 0 - Driver data.
Level 255- This list

This lists all diagnostics provided for the device at all its supported levels.

CONFIG

## 4520 LEVEL = 10
Section names of burned configuration file -
%%

## 4521 LEVEL = 11
Current pointed section from burned configuration file -
%%

## 4522 LEVEL = 12
Goto the next section in burned configuration file.

## 4523 LEVEL = 20
Section names of default configuration file -
%%

## 4524 LEVEL = 21
Current pointed section from default configuration file -
%%

## 4525 LEVEL = 22
Goto the next section in default configuration file.

245
 Software Diagnostics Output

## 4526 LEVEL = 255

Menu for configuration data access -
Level 1 - Current burned configuration
Level 2 - Default Configuration
Level 10 - Section names ( Burned config ).
Level 11 - Print a section ( Burned config ).
Level 12 - Goto next section ( Burned config ).
Level 20 - Section names ( Default config ).
Level 21 - Print a section ( Default config ).
Level 22 - Goto next section ( Default config ).

This lists all diagnostics provided for the device at all its supported levels.

## 4527 LEVEL = 1
Current burned configuration

## 4528 LEVEL = 2
Default Configuration

## 4530
Driver version - %%
Init - %%
Is active - %%
Is address list empty - %%
Max ICMP ECHO size - %%
Num of rule groups - %%
Num of rule deleted - %%
Num of address add - %%
Num of address delete - %%

FIREWL

## 4531 LEVEL = 255

Firewall Menu
Level 0 - Module data.
Level 1 - Filter locations status (Input , Pre-input).
Level 2 - Input rules (Blocking by address)
Level 3 - Pre-input rules (Blocking by ports Udp&Tcp)
Level 4 - Input statistics
Level 5 - Pre-input statistics
Level 255- This list

This lists all diagnostics provided for the device at all its supported levels.

246
 Software Diagnostics Output

PS (POWER SUPPLY)

## 4550 LEVEL = 0
Power Supply Module information
------------------------
Module version - %%

The module version of the power supply module driver.

247
 Software Diagnostics Output

## 4551 LEVEL = 1, 2
Power Supply %% - information - raw data
----------------------------------------
AUX 1A state - %%
AUX 1B state - %%
AUX 2A state - %%
AUX 2B state - %%
AUX 2 DC value - %%
battery_charge_level - %%
battery_voltage - %%
dc_output_ok - %%
main_ps_dc_value - %%
discharge_battery_state - %%
do_voltage - %%
internal_temperature - %%
external_temperature - %%
inhibit_state - %%
input_power_exists - %%
ps_load_switch_state - %%
ps_type - %%
ps_switches_state_mask - %%
power_supply_exists_in_slot_flag - %%

Power Supply - information - translated data for user

--------------------------------------------------------
AUX 1A state - %%
AUX 1B state - %%
AUX 2A state - %%
AUX 2B state - %%
AUX 2 DC value - %%
battery_charge_level - %%
battery_voltage - %%
dc_output_ok - %%
main_ps_dc_value - %%
discharge_battery_state - %%
do_voltage - %%
internal_temperature - %%
external_temperature - %%
inhibit_state - %%
input_power_exists - %%
ps_load_switch_state - %%
ps_type - %%
ps_switches_state_mask - %%
power_supply_exists_in_slot_flag - %%

Track ID - %% %%
Protocol version - %%
Power supply's internal SW version - %%.%%
LED image - %%

Battery info:
1. Capacity - %%
2. External DC disconnect - %%
3. Reconnect threshold - %%

Battery charge points:

248
 Software Diagnostics Output

%% %% %% %% %% %% %% %%
%% %% %% %% %% %% %% %%

Battery disconnect points:

%% %% %% %% %% %% %% %% %%
%% %% %% %% %% %% %% %% %%

Level 1: Power Supply 1 hardware data

Level 2: Power Supply 2 hardware data

## 4552 LEVEL = 10
Display & reset Counters
----------------------------------
CRC errors counter - %%
Frames counter - %%
Last operation return code - %%
Number of failed HW set operations - %%

Counters Show - Reset

## 4553 LEVEL = 11
Display Counters - without clearing them
----------------------------------
CRC errors counter - %%
Frames counter - %%
Last operation return code - %%
Number of failed HW set operations - %%

Counters Show - No Reset

## 4554 LEVEL = 255

Power Supply - menu
---------------------------------------------------
Level 0 - Driver data - module version
Level 1 - Power Supply 1 HW Data
Level 2 - Power Supply 2 HW Data
Level 3 - Power Supply 1 Configuration and device key Data
Level 4 - Power Supply 2 Configuration and device key Data
Level 5 - Power Supply 1 Saved Data for HW Test
Level 6 - Power Supply 2 Saved Data for HW Test
Level 10 - Counters Show & Reset
Level 11 - Counters No Reset
Level 255 - menu

This lists all diagnostics provided for the device at all its supported levels.

249
 Software Diagnostics Output

## 4555 LEVEL =3, 4

Power Supply %% - Configuration and device key Data
---------------------------------------------------
ps_id - %%
AUX 1A state - %%
AUX 1B state - %%
AUX 2A state - %%
AUX 2B state - %%
AUX 2 DC value - %%
ps_switches_state_mask - %%
ps_battery_type - %%
min_dc_voltage - %%
ext_dc_hysteresis - %%

ps_actual_num_of_discharge_points - %%

Battery discharge points:

%% %% %% %% %% %% %% %% %%
%% %% %% %% %% %% %% %% %%
%% %% %% %% %% %% %% %% %%
%% %% %%

ps_actual_num_of_charge_points - %%

Battery charge points:

%% %% %% %% %% %% %% %% %%
%% %% %% %% %% %% %% %% %%
%% %% %% %% %% %% %% %% %%
%% %% %%

PS task id - %%
Is PS in HW TEST - %%
HW TEST PS switches state mask - %%
HW TEST previous DC value - %%
Active Power Supply ID - %%
Temporary interrupt counter - %%
Power supply DO voltage state - %%

Level 3 - Power Supply 1 Configuration and device key Data

Level 4 - Power Supply 2 Configuration and device key Data.

250
 Software Diagnostics Output

## 4556 LEVEL =5, 6

Power Supply %% - Saved Data for HW Test
----------------------------------------
AUX 1A state - %%
AUX 1B state - %%
AUX 2A state - %%
AUX 2B state - %%
AUX 2 DC value - %%
battery_charge_level - %%
battery_voltage - %%
dc_output_ok - %%
main_ps_dc_value - %%
discharge_battery_state - %%
do_voltage - %%
internal_temperature - %%
external_temperature - %%
inhibit_state - %%
input_power_exists - %%
ps_load_switch_state - %%
ps_type - %%
ps_switches_state_mask - %%
power_supply_exists_in_slot_flag - %%

Level 5 - Power Supply 1 Saved Data for HW Test

Level 6 - Power Supply 2 Saved Data for HW Test

251
 Software Diagnostics Output

## 4557 LEVEL =21-33

IOEX PS IMAGE details for expansion number %%

Active PS ID - %%
Refresh Counter - %%

Power Supply %% - information - translated data for user

--------------------------------------------------------

AUX 1A state - %%
AUX 1B state - %%
AUX 2A state - %%
AUX 2B state - %%
AUX 2 DC value - %%
battery_charge_level - %%
battery_voltage - %%
dc_output_ok - %%
main_ps_dc_value - %%
discharge_battery_state - %%
do_voltage - %%
internal_temperature - %%
external_temperature - %%
inhibit_state - %%
input_power_exists - %%
ps_load_switch_state - %%
ps_type - %%
ps_switches_state_mask - %%
power_supply_exists_in_slot_flag - %%

Power supply DO voltage state - %%

Power Supply %% - information - translated data for user

--------------------------------------------------------
AUX 1A state - %%
AUX 1B state - %%
AUX 2A state - %%
AUX 2B state - %%
AUX 2 DC value - %%
battery_charge_level - %%
battery_voltage - %%
dc_output_ok - %%
main_ps_dc_value - %%
discharge_battery_state - %%
do_voltage - %%
internal_temperature - %%
external_temperature - %%
inhibit_state - %%
input_power_exists - %%
ps_load_switch_state - %%
ps_type - %%
ps_switches_state_mask - %%
power_supply_exists_in_slot_flag - %%

Power supply DO voltage state - %%

252
 Software Diagnostics Output

Levels 21 – 33 reflect the image of the power supplies on the expansion frame from within the main CPU.

Each frame is represented in one unique level, which equals to (20 + frame number), that is, frame 1 in
level 21, and so on. The fields have the same meaning as in PS levels 1,2 for Power Supplies # 1 and 2,
respectively. In order to verify that the communication between the main CPU and the expansion module
is working properly, perform diagnostic PS, Level 1,2 directly on the expansion frame. The values should
be the same.

Note: The PS2 data is valid only if such a power supply exists. Relates to Dual Power Supply. Not
relevant for this version.

IOMNGR

## 4601 LEVEL = 0
IO amounts
Last possible Rack Module : %%
Last possible Rack Module (With IRQ) : %%
Last defined Rack Module. : %%
Total number of defined IO modules : %%
Total number of IO modules with time tag : %%
Total number of IO modules with fast event : %%
Max amount of DI in a specific IO module : %%
Max amount of DO in a specific IO module : %%
Max amount of AI in a specific IO module : %%
Max amount of AO in a specific IO module : %%
Sum of DI inputs in all IO modules : %%
Sum of DO outputs in all IO modules : %%
Sum of AI inputs in all IO modules : %%
Sum of AO outputs in all IO modules : %%
Sum of Counters inputs in all IO modules : %%
Sum of DI bytes in all IO modules : %%
Sum of DO bytes in all IO modules : %%
Sum of AI bytes in all IO modules : %%
Sum of AO bytes in all IO modules : %%
Sum of Counters bytes in all IO modules : %%

List of I/O module types in the unit.

## 4600 LEVEL = 255

IO Manager diag levels:
Level 0 - Configuration.
Level 1 - List of modules types.
Level 2 - Burned SIO section.
Level 3 - Default SIO section.
Level 4 - List of modules versions
Level 5 - PDV block information.
Level 6 - SBO information.
Level 255- This list.

This lists all diagnostics provided for the device at all its supported levels.

253
 Software Diagnostics Output

IOFPGA

## 4605 LEVEL = 255

IO FPGA diag levels:
Level 0 - General info.
Level 1 - IO FPGA IRQ registers.
Level 10 -19 - IO MODULE registers.

This lists all diagnostics provided for the device at all its supported levels.

## 4606 LEVEL = 0
Num of modules :%%
Modules expected :%%
Last expected module :%%
FPGA base address :%%
Number DI Event set func :%%
Number DI Event Get func :%%
Number DI TT Set func :%%
Number DI TT Get func :%%
Number DI TT Event Set func :%%
Number DI TT Event Get func :%%
IRQ4 counter :%%
IRQ5 counter :%%

General IO FPGA information.

RxMy
Where:

• R=Rack (another term for RTU frame) and x is the Rack number

• M=Module and y is the Module number

## 4615 LEVEL = 255

Levels 0 - 4 SIO layer
------------------------
Level 0 - ID information.
Level 1 - DI information.
Level 2 - DO information.
Level 3 - AI information.
Level 4 - AO information.
Level 5 - IO switch information.

Levels 10 - 12 PHYSIO layer

------------------------
Level 10 - ID information.
Level 11 - FPGA registers.
Level 12 - Logers.

This lists all diagnostics provided for the device at all its supported levels.

254
 Software Diagnostics Output

## 4616 LEVEL = 0
DI handle %%1
DO handle %%2
AI handle %%3
AO handle %%4
Number of DI %%5
Number of Counters %%6
Number of DO %%7
Number of AI %%8
Number of AO %%9
Number of PS %%10
Support WB (0 - No) %%11
Support SBO (0 - No) %%12
Valid module (0 - No) %%13

1. Null if no DI elements in the module.

2. Null if no DO elements in the module.

3. Null if no AI elements in the module.

4. Null if no AO elements in the module.

5. Number of DI in module in the module.

6. Number of Counters in the module.

7. Number of DO in the module.

8. Number of AI in the module.

9. Number of AO in the module.

10. Number of power supplies in the module.

11. 1 if the module supports Wire break.

12. 1 if the module supports SBO.

13. 1 if resources exist for module.

## 4617 LEVEL = 1
DI :
Number of DI %%1
Number of additional DI %%2
Number of DI bytes %%3
Number of DI Counters %%4

1. Number of DIs in module.

2. Number of DI from FET DO.

3. Number of DI in bytes (Bit per DI).

4. Number of DI counters.

255
 Software Diagnostics Output

## 4618 LEVEL = 2
DO :
Number of DO %%1
Number of DO bytes %%2
Number of masked DO %%3
Is SBO module (NO 0) %%4
SBO select timeout %%5
Number of BI errors %%6

1. Number of DOs in the module.

2. Number of DOs in bytes (Bit per DO).

3. Number of mask DOs – Use as FET DI.

4. 1 if module supports SBO.

5. Timeout in milliseconds for select operation.

6. Number of Back Indication errors.

## 4619 LEVEL = 3
AI :
Total number of AI channels :%%1
AI in freeze state (0-No) :%%2
AI differential mode :%%3
Number of AI samples for average :%%4
AI type :%%5
Range values for voltage :%%6
Range values for current :%%7
PDV information :%%8
PDV values KLV mask :%%9

1. Number of AI channels in the module.

2. 1 if AIs are frozen.

3. AI differential mode value.

4. Number of AI samples for average.

5. Voltage (1) or Current (2).

6. AI range in present (Voltage).

7. AI range in present (Current).

8. Internal

9. Internal

256
 Software Diagnostics Output

## 4620 LEVEL = 4
AO :

Future releases

## 4621 LEVEL = 10
Module Information:
----------------------------------------
Expected hardware Module type %%
Expected software Module type %%
Actual hardware Module type %%
Module available (1-Yes 0-No ) %%
Module freeze (1-Yes 0-No ) %%
Module slepp (1-Yes 0-No ) %%
FPGA version %%.%%.%%
FPGA File number %%

Burnd block information:

----------------------------------------
Block CRC %%
Block Version %%
Module type %%
Number DI %%
Number DO %%
Number DO-ML %%
Number DO-FET %%
Number counters %%
Number AI %%
Number AO %%
Num power supply %%
Number switch ports %%
AI resolution; %%
AO resolution; %%
Counters resolution %%
AI type %%
AI current range %%
AI voltage range %%
AO type %%
AO current range %%
AO voltage range %%
Features - SBO (0-No ) %%
Features – AC Type (0-No ) %%
Features - Sign (0-No ) %%
Features - WB (0-No ) %%
Factory 1 %% %% %%
Factory 2 %% %% %%
ML bits %% %% %%

Masks
----------------------------------------
Wire break mask %% %% %%
TT mask %% %% %%
TT Event mask %% %% %%
Fet mask %% %% %%

I/O Module information.

257
 Software Diagnostics Output

IOMNGR

## 4624 LEVEL =1
RM 1 Expected %% Actual %% V
RM 2 Expected %% Actual %% V
RM 3 Expected %% Actual %% V
RM 4 Expected %% Actual %% V
RM 5 Expected %% Actual %% V
RM 6 Expected %% Actual %% V
RM 7 Expected %% Actual %% V
RM 8 Expected %% Actual %% V
CRC at startup : %% - CRC for all IO modules – Calculated at startup
CRC at present : %% - CRC for all IO modules – Calculated at diag

Each row includes

- RM – Rack Module (1-8)

- Expected – Expected module type

- Actual - Actual module type

-V\X - V if expected I/O module in Rack/Module matches actual I/O module;

X if expected I/O module in Rack/Module does not match actual I/O module.

## 4625 LEVEL =4
RM %% Version1 7 0 File %%
RM %% Version2 1 1 File %%
RM %% Version1 7 0 File %%
RM %% Version2 1 1 File %%
RM %% Version1 6 1 File %%
RM %% Version1 6 1 File %%
RM %% Version1 5 1 File %%
RM %% Version1 5 1 File %%

Each row includes

- RM – Rack Module (1-8)

- Version – IO module software versions (Version.subversion.update).

- File - IO module software type.

258
 Software Diagnostics Output

SFM

## 4630 LEVEL = 0
Header Signature %%
Header mode %% (0-Safe 1-Unsafe}
Header Type %%
Header Rack %%
Header module %%

IO file number %%
User file number %%

External safe load %% {0-Safe 1-Unsafe}

Ignore header %% {0-No 1-Yes }

Download file address %%

Download file size %%
Last Download status %%
Last Redownload status %%

Upload file address %%

Upload file size %%
Last upload status %%

Internal serial flash memory. Internal Motorola use only.

RTC

## 4700 LEVEL = 0
Real-time Clock information
--------------------------------
module version - %%
Current time reading - %%
validity flag pattern - %% %% %%
Was the RTC ever initialized? - %%
Number of RTC sync events - %%
control register value - 0x%%
Status register value - 0x%%
Trickle Charge register value - 0x%%
Memory Dump -

address 0 - %%
address 1 - %%
address 2 - %%
address 3 - %%
address 4 - %%
address 5 - %%
address 6 - %%
address 7 - %%
address 8 - %%
address 9 - %%

RTC hardware registers information.

259
 Software Diagnostics Output

## 4701 LEVEL = 255

Menu for the real-time Clock diagnostics
---------------------------------------------------
Level 0 - RTC information.
Level 1 - RTC device key brief information.
Level 10 - RTC flags clear.
Level 255 - This menu.

This lists all diagnostics provided for the device at all its supported levels.

## 4702 LEVEL = 1
RTC device key brief information:
---------------------------------
Task ID : %%
Semaphore ID : %%
Timer pointer : %%
Sync counter : %%
Battery charging status : %%
Is time to charge check : %%
NO-CHARGE timeout expired : %%
Missing power supply message sent? : %%
Lithium bat. charge-command-fail msg sent? : %%
Lithium bat. NO-CHARGE message wdog ID : %%
Status register value at startup : %%
No HW RTC on board and device is a stub? : %%
Is time to status register check? : %%
Reset of RTC status register failed at startup? : %%
Runtime Reset failure COUNTER of RTC status register : %%

RTC module device key brief information.

## 4703 LEVEL = 10
RTC "message sent" flags are cleared.
Runtime Reset failure COUNTER of RTC status register is cleared.

A message that indicates that the Runtime Reset failure COUNTER counter was cleared.

PWR_MNG

## 4710 LEVEL = 0
Power Manager key members:
-------------------------
MessageQueue maximal size :%%
Current number of messages in queue :%%
Current number of messages in pool :%%

Power Manager key members

260
 Software Diagnostics Output

## 4711 LEVEL = 255

Power Manager Diagnostics Levels:
---------------------------------
Level 0 - key members
Level 255- This list

This lists all diagnostics provided for the device at all its supported levels.

HW_TST

## 4750 LEVEL = 1
HW_TST Module information
------------------------
Module version - %%

Hardware test - Module version

## 4751 LEVEL = 2
HW_TST - the last op-code
--------------------------------
Last op-code - %%

Hardware test - The last op-code

## 4752 LEVEL = 3
HW_TST - Number of get() calls
----------------------------------
Number of get() calls - %%

Hardware test - Number of get() calls

## 4753 LEVEL = 4
HW_TST - Last get() ret_code
----------------------------------
Last get() ret_code - %%

Hardware test - Last get() ret_code

## 4754 LEVEL = 5
HW_TST - Timers status
--------------------------------------
Freeze state - %%
Freeze timer counter value - %%
application state - %%
application timer counter value - %%

Hardware test - Timers status

261
 Software Diagnostics Output

## 4755 LEVEL = 255

HW_TST Menu - MOSCAD ACE HW TEST
---------------------------------------------------
Level 1 - Print Module version
Level 2 - Print the last op-code
Level 3 - Print the number of get() calls
Level 4 - Print the last get() ret_code
Level 5 - Print the timers' status
Level 255 - This menu

This lists all diagnostics provided for the device at all its supported levels.

PB

## 4760 LEVEL = 1
PB Module information
-------------------------------
Module version - %%
LEDS wakeup counter - %%
LEDs test counter - %%
PB1 presses counter - %%
PB2 presses counter - %%
PB1 current state - %%
PB2 current state - %%

Pushbutton information.

## 4761 LEVEL = 255

PB Menu
-------------------------------
1 - Module information
255 - This menu

This lists all diagnostics provided for the device at all its supported levels.

262
 Software Diagnostics Output

TIMESYN

## 4800 LEVEL = 0
MDLC Time Sync Module
---------------------
Last Time Synced [Sec.Nsec] : %%1
Remote RTU Time that was sent [Sec.Nsec] : %%2
Diff Time [Sec.Nsec] : %%3
Time offset between remote and myself [Sec.Nsec]: %%4
Was last Sync Local? : %%5
Time offset learned from time zone [sec] : %%6
Last Sync Type received : %%7
Password : %%8
Sync From Old RTU : %%9
Check Pwd On Recv : %%10
Sync To Old RTU : %%11
Is RTU secured ? : %%12
Was last sync request that set the time secured?: %%13
User ID of last sync request that set the time : %%14
Role ID of last sync request that set the time : %%15

Secured site ID : %%16

Does secured RTU check authentication of sync ? : %%17
Does secured RTU ignore integrity check of sync?: %%18
Security policy password length : %%19
Permission activity ID in hexadecimal : %%20
Was one of security policy parameter invalid ? : %%21
Does secured RTU check message life time ? : %%22
Security policy message life time duration : %%23

Locked task name : %%24

Number of nested locks : %%25
Address of lock mutex : %%26

MDLC Time Sync parameters.

1. The last time the RTU clock was synchronized relative to 1970. Internal use.

2. The last time that was sent to synchronize a remote RTU.

3. Amount of time was added to remote time because of channel delays.

4. Difference in time between the RTU clock and last synchronizing RTU. If sending two MDLC time
syncs, it shows the offset between the synchronizing RTU and the receiving one (depending on the
media and the delay of channel).

5. YES – if the last sync was legacy MDLC, or a new ACE extended time sync with no time zone. With
new ACE extended time sync, it is possible to get time sync from a different time zone. If this
parameter is YES, this is not the case.

6. With new ACE extended time sync, it is possible to get time sync from a different time zone. This
shows the last offset if obtained from a different time zone. In order to use the new ACE Extended
time sync, to synchronize RTUs in a different time zone, enable the advanced site configuration

263
 Software Diagnostics Output

parameter ‘Time sync method’ to Extended Sync, and set the time zone in both RTUs. If the time
zone is different, the receiving RTU will show that offset in this item.

7. Type of last time sync frame received: Legacy or Extended. Extended has time zone support and is
more accurate – but it only supported by ACE.

8. Password of the RTU in CRC format.

9. YES – if accept legacy sync. If not, sync frames received from a MOSCAD RTU or an ACE RTU
configured to send legacy sync will be ignored. See Time Sync advanced site configuration
parameter ‘What to do with received short sync messages.’

10. If YES – password is checked for extended MDLC time sync received frames. If the password is
invalid, the frame will be ignored. This corresponds to the ‘Password check in case of long sync’
Time Sync advanced site configuration parameter.

11. If YES – send MDLC time sync in extended sync format. This corresponds to the ‘Time sync
method’ Time Sync advanced site configuration parameter.

12. YES - if the RTU is secured with policy settings and relevant security files.

13. YES - if the last received sync request that set time&date was secured.

14. User ID of the last received sync request that set time&date that was secured (65535 if unknown).

15. Role ID of last received sync request that set time&date that was secured (65535 if unknown).

16. My site ID. In a redundant system, this is the RTU’s common site ID.

17. YES - if authentication is on. Relevant if RTU is secured.

18. YES - if configured to ignore time stamp integrity check. Relevant if RTU is secured.

19. Minimal size of password to check. Relevant if RTU is secured and authentication is on.

20. Internal use.

21. Internal use.

22. Is message life time enabled in the secured RTU.

23. Duration in seconds for message life time validity.

24. Internal use.

25. Internal use.

26. Internal use.

264
 Software Diagnostics Output

## 4810 LEVEL = 10, 11

MDLC time sync statistics
--------------------------
#of recv sync : %%1
#of sent sync : %%2
#of Old sent sync : %%3
#of Old recv sync : %%4
#of ignored old sync : %%5
#of bad pwd sync : %%6
#of unsupported time sync : %%7
#of ignored time sync : %%8
#of rejected sync because missing secured payload : %%9
last site rejected because of missing secured payload : %%10

#of rejected sync that failed integrity check : %%11

last site that sent sync for which integrity check failed : %%12

#of rejected sync because invalid secured payload : %%13

last site that sent secured sync having invalid secured payload : %%14

#of rejected secured sync because missing authentication : %%15

last site that sent secured sync missing authentication : %%16

#of rejected secured sync because it appears in legacy site list : %%17
last site that sent secured sync although it is not listed as legacy site:
%%18

#of rejected secured sync because it had invalid authentication size : %%19
#of rejected secured sync because failed authenticate : %%20
#of rejected secured sync because failed authentication (job queue was full):
%%21
Last site that sent secured sync but its authentication invalid or failed:
%%22

#of secured sync succeed authentication : %%23

Last site sent secured sync that succeed authentication : %%24

#of rejected secured sync because failed check authorization : %%25

Last site sent secured sync that failed check authorization : %%26

#of rejected secured sync because failed permission check : %%27

Last site sent secured sync that failed permission : %%28

#of valid secured sync received that failed forwarding : %%29

Last site that sent valid secured sync but failed forward : %%30

#of secured sync that failed transmission because cannot get my user ID : %%31
#of secured sync succeed transmission that were not encrypted : %%32
#of secured sync that failed transmission because failed update integrity:
%%33
#of secured sync that failed transmission because failed encrypt : %%34
#of secured sync that failed transmission because failed decrypt : %%35
#of secured sync that failed transmission because failed add payload : %%36

#of padded bytes added to last sent secured sync : %%37

#of times failed lock internal sync task : %%38
Last internal error when failed decrypt secured sync (in hexadecimal) : %%39

Last authentication job description : %%40

265
 Software Diagnostics Output

Last failed authentication job description : %%41

MDLC Time Sync statistics (Level 10 clears statistics; Level 11 does not clear statistics.)

1. Number of extended MDLC time sync frames received and processed (accepted).

2. Number of extended MDLC time sync frames sent.

3. Number of legacy MDLC time sync frames sent.

4. Number of legacy MDLC time sync frames received and processed (accepted).

5. Number of legacy MDLC time sync frames that were received but ignored because of Ignore
MOSCAD time sync, or because the RTU has a GPS or NTP valid clock.

6. Number of MDLC time sync frames that were ignored because of bad password.

7. Number of invalid MDLC time sync frames received and ignored.

8. Number of extended time sync frames that were received but ignored, because the RTU has a GPS or
NTP valid clock.

The following new statistics are relevant for an RTU in secured mode, and are also reflected in security
logger.

9. Number of received sync requests ignored because the RTU is secured but is expecting a nonsecured
sync from originating site but it has a security payload.

10. Last site ID which originated the above sync request, 65534 if STS.

11. Number of received sync requests ignored because the RTU is secured, expected and received a
secured sync, but its time stamp has failed integrity check.

12. Last site ID originated the above sync request, 65534 if STS.

13. Number of received sync requests ignored because the RTU is secured, expected and received a
secured sync from originating site, but it has invalid security payload.

14-Last site ID originated the above sync request, 65534 if STS.

15. Number of received requests ignored because the RTU is secured, expected and received a secured
sync from originating site, but sync request is missing authentication. Probably mismatch in policy
between originating site or STS and this RTU.

16. Last site ID originated the above sync request, 65534 if STS.

17. Number of received sync requests ignored because the RTU is secured and expecting a secured sync
from originating site but it has no security payload.

18. Last site ID originated the above sync request, 65534 if STS.

19. Number of received sync requests ignored because the RTU is secured, expected and received a
secured sync from originating site, but password is smaller than expected.

20. Number of received sync requests ignored because the RTU is secured, expected and received a
secured sync from originating site, but failed authentication.

266
 Software Diagnostics Output

21. Number of received sync requests ignored because the RTU is secured, expected and received a
secured sync from originating site, but failed process due to internal error.

22. Last site ID originated the above three sync requests.

23. Number of received sync requests that succeeded authentication and authorization for synchronizing
the clock.

24. Last site ID originated the above sync request.

25. Number of received sync requests ignored because the RTU is secured, expected and received a
secured sync from originating site, authentication succeeded, but authorization check failed.

26. Last site ID originated the above sync request.

27. Number of received sync requests ignored because the RTU is secured, expected and received a
secured sync from originating site, authentication succeeded, but user is not authorized.

The difference between #27 and #25 is that in #27 authorization check succeed, and found that user is not
permitted.

28. Last site ID originated the above sync request.

29. Number of times received valid secured sync when RTU is secured, but failed to forward it because
of internal error.

30. Last site ID originated the above sync request.

31. Number of times secured RTU failed transmit secured sync because internal error prevent getting my
user ID.

32. Number of times secured RTU transmitted a secured sync request, but did not encrypt it due to policy
encryption.

33. Number of times secured RTU failed to transmit because internal error prevented updating its time
stamp integrity code.

34. Number of times secured RTU failed to transmit because internal error prevented encrypting it.

35. Number of times secured RTU failed to transmit because internal error prevented decrypting it
(during transmission the frame is encrypted, decrypted and then encrypted again).

36. Number of times secured RTU failed to transmit because internal error prevented generating security
payload.

37. Internal use.

38. Internal use.

39. Internal use.

40. Internal use.

41. Internal use.

267
 Software Diagnostics Output

## 4855 LEVEL = 255

MDLC Time Sync Module Levels:
-----------------------------
Level 0 - Get parameters.
Level 10- Get and clear statistics.
Level 11- Get statistics without clear.
Level 255- This message.

This lists all diagnostics provided for the device at all its supported levels.

REQMNG (ACE IP Gateway Only)

## 5000 LEVEL = 0
Reqmng data:
max clients : %%1
max channels : %%2
max buffers : %%3
comm buffer length : %%4
clients offset : %%5
channels offset : %%6
buffers offset : %%7
read list offset : %%8
next client : %%9
next channel : %%10
n read channels : %%11
cur buffer : %%12
gateway id : %%13
gateway status : %%14
client error : %%15
mng thread channel : %%16
rx_thread_channel : %%17
tx global : %%18
rx global : %%19
mng global : %%20
site id : %%21
startup mode : %%22

1. The maximum number of clients.

2. The maximum number of channels.

3. The maximum number of buffers.

5.-13. Internal use

14. The status of the IP Gateway. 1H = Primary mode, 5H = Secondary mode.

15. – 21. Internal use.

22. The IP Gateway startup mode: 0 = Stand-alone, 1 = Redundant GW1, 2 = Redundant GW2

22. Internal use.

268
 Software Diagnostics Output

## 5005 LEVEL = 10, 11

Reqmng data:
In Buffers : %%1
Out Buffers : %%2
In Blocks : %%3
Out Blocks : %%4
Out Burst Blocks : %%5
In Buffers with Err : %%6

1. Number of buffers received from the SCADA driver to the IP Gateway for execution.

2. Number of buffers sent from the IP Gateway to the SCADA driver.

3. Number of blocks received from the SCADA driver to the IP Gateway for execution.

4. Number of blocks sent from the IPGW to the SCADA driver.

5. Number of Burst blocks (unsolicited messages) sent from the IP Gateway to the SCADA driver.

6. Number of buffers sent with Error.

## 5006 LEVEL = 255

level 0 - Configuration values and internal parameters
level 1 - Scada clients data
level 2 - Scada channels data
level 3 - Transmitted buffers to SCADA
level 4 - Scada application buffers data
level 10 - Get and clear inbound/outbound buffers/blocks statistics.
level 11 - Get inbound/outbound buffers/blocks statistics without clear.
level 255- This level

This lists all diagnostics provided for the device at all its supported levels.

269
 Software Diagnostics Output

HELTHCH (ACE IP Gateway Only)

## 5120 LEVEL = 0
Health Check Diagnostics
Actual number of RTUs: %%1
Maximum RTUs: %%2
Time to wait in ping task: %%3 mili seconds
Time to wait in pong task: %%4 mili seconds
Time to wait in dead task: %%5 mili seconds
Time to give up ping: %%6 seconds
Number of pings until fail: %%7

pointer to pingHndl: %%8

pointer to deadHndl: %%9
pointer to pongHndl: %%10
pointer to rtuList: %%11
pointer to notify function: %%12
parameter to notify function: %%13
TMUX key: %%14
FRAM_SEQ key: %%15
System maximum ping trials %%16
Time to wait after ping: %%17 mili seconds

1. The actual of number of RTUs included in the health check scan.

2. The maximum number of RTUs that can be included in the health check scan.

3. The number of milliseconds to wait between health check ping scans.

4. The number of milliseconds to wait between health check pong scans (reply to ping.)

5. The number of milliseconds to wait between health check dead scans.

6. The number of seconds to wait before timing out (giving up pinging).

7. The number of failed ping attempts before timing out (giving up pinging).

8-17. Internal use.

The HELTHCH device displays general information, last “ping” time and last response time per site and
link, “ping” results per site, “ping” timeouts per site, site and link status and “ping” information.

## 5121 LEVEL = 1
Health Check Diagnostics - Rtus (times are in seconds)
-------------------------------
SiteId LinkId Status PingTime ResponseTime PingsSent
------ ------ ------ -------- ------------ --------
%%1 %%2 %%3 %%4 %%5 %%6

1. The Site ID.

2. The Link ID of the link through which the site is connected to the network.

270
 Software Diagnostics Output

3. The status of the link (alive /dead / disabled)

4. The time that the last ping was sent.

5. The time of the last response to a ping.

6. The number of pings sent to the site.

## 5122 LEVEL = 2
Health Check Diagnostics - Rtus (trials due to busy in transmit)
-------------------------------
SiteId Status PingTrials MaxPingTrials
------ ------ ---------- -------------
%%1 %%2 %%3 %%4

1. The Site ID.

2. The status of the site (alive /dead / disabled)

3. The number of ping trials due to ERR_BUSY (busy in transmit).

4. The maximum number of ping trials that occurred due to ERR_BUSY (busy in transmit).

## 5123 LEVEL = 3
Health Check Diagnostics - Rtus (times are in seconds)
-------------------------------
SiteId Status DeadTime QuietTime BetwTime
------ ------ -------- --------- --------
%%1 %%2 %%3 %%4 %%5

For internal use.

## 5124 LEVEL = 4
Health Check Diagnostics - Rtus
-------------------------------
SiteId LinkId Network-LinkId Status HchkLinkStatus #Failures #TotalPings
------ ------ -------------- ------ -------------- --------- -----------
%%1 %%2 %%3 %%4 %%5 %%6 %%7

For internal use.

## 5125 LEVEL = 255

level 0 - general information
level 1 - last ping time & last response time per site & link
level 2 - ping results per site
level 3 - ping timeouts per site
level 4 - site & link status and pings information
level 255 - This level

This lists all diagnostics provided for the device at all its supported levels.

271
 Software Diagnostics Output

LNKHNDL (ACE IP Gateway Only)

## 5160 LEVEL = 0
Number of Link(s): %%

The number of links of all RTUs managed by the LNKHNDL device for the Health Check mechanism.

## 5161 LEVEL = 1
Site #: %%1
Site Up Time : %%2
Site Down Time : %%3
Primary Link %%4 is %%5 %%6 %%7
Secondary Link %%8 is %%5 %%6 %%7

1. The Site ID.

2. The time that “Site up” message was received . (measured in number of peaks since startup)

3. The time that “Site down” message was received. (measured in number of peaks since startup)

4. The Link ID of Primary Link to the site.

5. The status of the link (UP/DOWN).

6. Internal use

7. Internal use

8. The Link ID of Secondary Link to the site.

DCF6 (IRRIV Application for IRRInet-M and IRRInet-ACE)

## 8001 LEVEL = 31
index Counter TempFlow NextInRequestList RemainingStabilityTime
===== ======= ======== ================= ======================
RequestFlags HandleFlags Status Status Status Status Flag
Momentary Stable Comm HW FirstTimeRead
============ =========== ========= ====== ====== ====== =============

Table of Inputs Information on every input in the system.

## 8002 LEVEL = 32
index RemainingOpenTime ProgramsCounter ManualCounter
===== ================= =============== =============
NextOutputInRequestList NextOutputInOpenedList
======================= ======================

Table of Outputs Information on every output in the system.

272
 Software Diagnostics Output

## 8003 LEVEL = 33
index FetchFunc StoreFunc StoreDefaultsFunc NextCosFunc
===== ========= ========= ================= ===========

More Outputs Information on every output in the system.

## 8005 LEVEL = 34
TransmitScorpioIndex : %%1
ScorpiosArraySize : %%2
ChannelFree : %%3
TransmitNeed : %%4
ReceiveFrameExist : %%5
MasterLink : %%6
MasterSite : %%7

Scorpio information including information about who is the master.

LEVEL = 35
Scorpios Array
Adrs LinkType LinkId comm frames no, status sent ans
==== ======== ====== ==== ====== === =========== ===

Scorpio table information.

## 8007 LEVEL = 36
ChannelWait : %%1
ChannelFree : %%2
TransmitNeed : %%3
ImpactsArraySize : %%4

Address Frame Remain RemainTime TimeFrom New Opened

seq Retries TillRetry lastComm Req Max Time
======= ===== ======= ========== ======== === ========

Impacts information.

273
 Software Diagnostics Output

## 8009 LEVEL = 37
TxRegisteredAppMask : %%1
SemaphoreRadio : %%2
SemaphoreLine : %%3
ScorpiosRadioFreeWakeupTime : %%4
ScorpiosLineFreeWakeupTime : %%5
RxRegisteredAppMask : %%6
RadioChannelFreeTime : %%7
NextFrameIndex : %%8
LineChannelFreeTime : %%9
ImpactsRadioFreeWakeupTime : %%10
ImpactsLineFreeWakeupTime : %%11
ImpactsLineEndTransmitWakeup : %%12
ImpactsLineFreeWakeup : %%13
ImpactsRadioEndTransmitWakeup : %%14
ImpactsRadioFreeWakeup : %%15
ScorpiosLineEndTransmitWakeup : %%16
ScorpiosLineFreeWakeup : %%17
ScorpiosRadioEndTransmitWakeup : %%18
ScorpiosRadioFreeWakeup : %%19
RouterRadioFreeWakeup : %%20

Intrac communication information.

## 8010 LEVEL = 44
NumberOfObjects : %%1
Debug : %%2
pEventTempFrame : %%3
EventTransmitNeed : %%4

Multiplex information.

## 8011 LEVEL = 45
index CommandFunc
===== ===========

Multiplex information.

## 8012 LEVEL = 46
BufferSize : %%
CurrentPosition : %%
EndFramePosition : %%
TransmitNeed : %%
FrameSequence : %%
LastEventPosition : %%
RetryLevel : %%
RetryTimeout : %%
StartFramePosition : %%

Events information.

274
 Software Diagnostics Output

## 8013 LEVEL = 30
C application information
=========================
Version : %%.%%1
ApplicID (1 = slave, 2 = master) : %%2

Dat file information

====================
ApplicID : %%3
Version : %%4

1. C application version

2. Whether the application is slave or master.

3. Application ID - Dat file.

4. Dat file version.

## 8015 LEVEL = 41
Scorpios Queue

Number of frames
================
rec frame : %%1
rec from master : %%2
rec from master to slave : %%3
insert to queue : %%4
route via fsk : %%5
trans frame : %%6
rec from slave to master : %%7
route via mdlc : %%8
trans to master : %%9

Queue information
=================
first_msg : %%10
last_msg : %%11
num_of_objects_in_queue : %%12
num_of_overlapping : %%13

Scorpio queue information (relevant only on slave as router.)

LEVEL = 99
Scorpio reset queue.

275
 Software Diagnostics Output

## 8016 LEVEL = 42
Impacts Queue

Number of frames
================
rec frame : %%1
rec from master : %%2
rec from master to slave : %%3
insert to queue : %%4
route via fsk : %%5
trans frame : %%6
rec from slave to master : %%7
route via mdlc : %%8
trans to master : %%9

Queue information
=================
first_msg : %%10
last_msg : %%11
num_of_objects_in_queue : %%12
num_of_overlapping : %%13

Impact queue information (relevant only on slave as router.)

LEVEL = 98
Impacts reset queue.

## 8017 LEVEL = 50
COMM FAIL Information
=====================
Slave In Comm Fail : %%1

Retries Information
===================
Number of retries : %%2
Number of retry level : %%3

HANDSHAKE Information
=====================
Number of handshake : %%4
Last time handshake : %%:%%:%%5
Number of handshake when comm fail : %%6
Last time handshake when comm fail : %%:%%:%%7

Communication information ( Comm. Fail, retries and handshake.)

LEVEL = 51
Communication reset information.

276
 Software Diagnostics Output

## 8018 LEVEL = 47
Battery information
===================
AC Battery exist (1 = AC exist) :%%1
AC Battery status (0 = AC OK, 1 = AC Fail) :%%2
AC Battery state :%%3
AC Battery bat recover value :%%4
AC Battery low bat 1 value :%%5
AC Battery low bat 2 value :%%6
AC Battery Value In :%%7

Battery information (for IRRIV application on IRRInet-M slave.)

## 8019 LEVEL = 47
PS type : %%1 (AC=0,DC=1,12V DC=2,Unknown=255)
MAIN status : %%
Battery level * 10 : %%2
Battery Status : %%3 (OK=1,Fail=8,warn=9,alarm=10)
In pause mode : %%4
Battery recovery level * 10 : %%5
Battery low level warning * 10 : %%6
Battery low level alarm * 10 : %%7

Battery information (for IRRIV application on IRRInet-ACE master.)

Note: In 12V DC, the statuses are measured every 1 minute.

Otherwise, they are is measured every 1 minute, only when MAIN fails.

## 8020 LEVEL = 47
AC exists : %%1 (YES=1,NO=0,Unknown=255)
AC fail : %%2 (Applicable only if AC exists)
Battery level * 10 : %%3
Battery Status : %%4 (OK=1,Fail=8,warn=9,alarm=10)
In pause mode : %%5
Battery recovery level * 10 : %%6
Battery low level warning * 10 : %%7
Battery low level alarm * 10 : %%8

Note: If AC does not exists, the statuses are measured every 1 minute.

Otherwise, they are measured every 1 minute, only when AC fails.

Battery information (for IRRIV application on IRRInet–M master.)

## 8021 LEVEL = 52
Program Alarm Bits : %%1
MainLine Alarm Bits: %%2
Scorpios Alarm : %%3
Outputs Alarm : %%4
Ac Over Current : %%5

Alarm LEDs:

277
 Software Diagnostics Output

1. Not relevant.

2. Not relevant.

3. One or more scorpios in the scorpios table has COMM_FAIL.

or
One or more PIUs in the PIU table has COMM_FAIL.

4. One or more Piccolo-XRs reported hardware defects:

0x01 - SOL not connected
0x02 - Over current

5. Always 0 in IRRInet-M and IRRInet-ACE.

IPCNTBL

## 13241 LEVEL = 1
IP Conversion Table state
-------------------------
Number of link IDs : %% 1
Internal pointer of Table : %% 2
Self Site ID : %% 3
Is Conversion Table locked : %% 4
Task name locking conversion table : %% 5
Notify change on other link IDs : %% 6

1. The number of link IDs allocated in the IP conversion table for each site.

2. The internal pointer to the IP conversion table.

3. The self site ID.

4. Whether the table is locked by a task. Internal use.

5. The name of the task which has locked the IP conversion table.Internal use.

6. (V15.50 or higher) This reflects whether to notify of IP address changes from other links (ports). The
notification is sent as a setcall. See the ACE3600 STS Advanced Features manual for more on
setcalls.

## 13249 LEVEL = 255

level 1- Get IP Conversion Table state */
level 3 - All rows in conversion table of specific link ID
level 10- IP Conversion Table statistics

This lists all diagnostics provided for the device at all its supported levels.

278
 Software Diagnostics Output

## 13250 LEVEL = 10
IP Conversion Table statistics
------------------------------
Last Link ID inquired in get host by name : %% 1
Last Site ID inquired in get host by name : %% 2
Last Site name inquired in get host by name : %% 3
Last IP Address resolved in get host by name : %% 4
Number of times failed resolve host by name : %% 5
Number of times succeed resolve host by name : %% 6
Number of times failed update IP address in table : %% 7
Number of times succeed update IP address in table: %% 8
Number of times failed allocate new site : %% 9

1. The link ID of the last RTU from the last ‘get host by name’ inquiry.

2. The site ID from the last ‘get host by name’ inquiry.

3. Internal use.

4. The last IP address that resolved a hostname using ‘get host by name’.

5. The number of times that the ‘get host by name’ call failed to return a host address.

6. The number of times that the ‘get host by name’ call successfully returned a host address.

7. The number of times that the IP address could not be updated in the IP conversion table (e.g. due to
lack of memory.)

8. The number of times that the IP address was successfully updated in the IP conversion table.

9. The number of times the system failed to add a new site because of a memory problem.

VXNETPOOL

## 13300 LEVEL = 0
Vxworks NetPool parameters
--------------------------
Is netpool allocated : %%
Internal Pointer of netPool : %%
Is netpool OK : %%
Max clusters area size [bytes] : %%
Actual allocated clusters area [bytes] : %%
Allocated Partition ID : %%
Partition size [bytes] : %%
Actual Allocated partition size [bytes] : %%
Current free size of Partition [bytes] : %%
Current allocated size of Parition [bytes]: %%

Vxworks NetPool Parameters

279
 Software Diagnostics Output

## 13310 LEVEL = 10, 11

Vxworks NetPool statistics
---------------------------
Number of times failed free Mblk : %%
Last Mblk that failed free : %%
Last cluster that failed free : %%
Number of times failed allocate Mblk : %%

Vxworks NetPool Statistics

# 13355 LEVEL = 255

Vxworks NetPool available diagnostic levels
--------------------------------------------
level 0 - get parameters
level 10,11 - get & reset statistics

This lists all diagnostics provided for the device at all its supported levels.

VXPPP

## 13400 LEVEL = 0
PPP Port parameters
--------------------
Port index : %%
Port name : %%
Port type : %%
Channel ID : %%
Pointer to Framework : %%
Pointer to Profile : %%
Pointer to Stack : %%
Name of network memory pool : %%
Name of physical layer : %%
Name of TX Heap : %%
Pointer to Lock semaphore : %%
Physical port baud rate : %%
Physical port mode : %%
Physical mode : %%
Max size of transmit queue : %%
Interface subnet mask : %%
Interface IP Address : %%
Interface name in VxWorks : %%
Allow Duplicate Modem IP Addresses : %%

PPP port parameters.

280
 Software Diagnostics Output

## 13401 LEVEL = 1
PPP Port status
--------------------
PPP Port state : %%
LCP Layer state : %% %%
NCP Layer state : %% %%
Local authentication state: %%
Peer authentication state : %%

Is Task receiving data : %%

Is Task transmitting data : %%
Is transmission pending : %%
Is driver stopped : %%
Has reception ceased : %%
Has transmission ceased : %%

Has Rx Idle timer expired : %%

Maximal no reception time to declare disconnect [millisec]: %%
Time elapsed since last reception [millisec] : %%
Received AT response while driver was running : %%
Peer IP Address enabled in firewall : %%
Primary DNS IP Address enabled in firewall : %%
Secondary DNS IP Address enabled in firewall : %%

PPP port status.

## 13402 LEVEL = 2
PPP configuration options and timeouts
--------------------------------------
Is Protocol Compression enabled : %%
Is Address Compression enabled : %%
Async Control characters (ACCM) : %%
MAX Receive Unit (MRU) : %%
Authentication protocol : %%
Local IP Address : %%
Peer/modem IP Address : %%
User name to send : %%
Password to send : %%
DNS Zone name : %%
Primary DNS Server : %%
Secondary DNS Server : %%

Maximal no reception time to disconnect [millisec]: %%

PPP retry time [millisec] : %%
PPP Echo send interval [millisec] : %%
PPP Echo Send number of retries before disconnect : %%
Time elapsed since last reception [millisec] : %%
Maximal wait time for PPP to connect [millisec] : %%
Maximal wait time for PPP to close [millisec]: %%

PPP configuration options and timeouts.

281
 Software Diagnostics Output

## 13403 LEVEL = 3
Last PPP negotiated options
----------------------------
PPP Configuration My Their Negotiated
----------------- ------------ -------------- -------------
MRU %% %% %%
Async CTL (ACCM) %% %% %%
Protocol Compression %% %% %%
Authentication Protocol %% %% %%
Address Compression %% %% %%
IPCP Compressed protocol %% %% %%
IPCP Max Slot ID %% %% %%
IP Address %% %% %%
Primary DNS IP Address %% %% %%
Secondary DNS IP Address %% %% %%

Last PPP negotiated options.

282
 Software Diagnostics Output

## 13404 LEVEL = 4
PPP log information
---------------------
Last protocol received :%%
LCP protocol received :%%
LCP code received :%%
LCP id received :%%
LCP message length :%%
LCP message received :%%
Time received last LCP :%%
Number of Nak received: %%
Number of Rej received: %%

IPCP protocol received :%%

IPCP code received :%%
IPCP id received :%%
IPCP message length :%%
IPCP message received :%%
Time received last IPCP:%%
Number of Nak received: %%
Number of Rej received: %%

PAP protocol received :%%

PAP code received :%%
PAP id received :%%
PAP message length :%%
PAP message received :%%
Time received last PAP :%%

CHAP protocol received :%%

CHAP code received :%%
CHAP id received :%%
CHAP message length :%%
CHAP message received :%%
Time received last CHAP:%%
Number of 'Success' code:%%
Number of 'Fail' code : %%

Last protocol transmitted :%%

LCP protocol transmitted :%%
LCP code transmitted :%%
LCP id transmitted :%%
LCP message length :%%
LCP message transmitted :%%
Time transmitted last LCP :%%
Number of Nak transmitted :%%
Number of Rej transmitted :%%

IPCP protocol transmitted :%%

IPCP code transmitted :%%
IPCP id transmitted :%%
IPCP message length :%%
IPCP message transmitted :%%
Time transmitted last IPCP:%%
Number of Nak transmitted :%%
Number of Rej transmitted :%%

PAP protocol transmitted :%%

PAP code transmitted :%%

283
 Software Diagnostics Output

PAP id transmitted :%%

PAP message length :%%
PAP message transmitted :%%
Time transmitted last PAP :%%

CHAP protocol transmitted :%%

CHAP code transmitted :%%
CHAP id transmitted :%%
CHAP message length :%%
CHAP message transmitted :%%
Time transmitted last CHAP:%%
Number of 'Success' codes :%%
Number of 'Fail' codes :%%

Last PPP transmit and receive log information.

## 13410 LEVEL = 10, 11

PPP Port statistics
--------------------
Number of successfull transmissions : %%
Number of failed transmissions : %%
Number of successfull bytes received : %%
Number of failed receptions : %%
Number of times corrected bad received frames : %%
Size of last transmitted frame in bytes : %%
Number of times rejected transmission : %%
Number of times stopped driver : %%
Number of times failed stop driver : %%
Number of times received AT response while driver was running: %%
Number of times disconnected by force : %%
Number of timeouts when bringing device up : %%
Number of timeouts when bringing device down : %%
Number of times got bad IP Address : %%
Number of times disconnect because of idle timeout : %%
Number of times succeed authenticate : %%
Number of times failed authenticate : %%
Number of authenticated peer : %%
Number of rejected peer authentication : %%
Number of firewall rules added : %%
Number of firewall rules deleted : %%

Last Time received msg :%%

Last msg received len :%%
Last received msg :%%

Last Time transmit msg :%%

Last msg transmited len:%%
Last msg transmitted :%%

284
 Software Diagnostics Output

## 13455 LEVEL = 255

PPP Port available diagnostic levels
------------------------------------
level 0 - get parameters
level 1 - get PPP state
level 2 - get PPP configured options and timeouts
level 3 - get last PPP negotiated options
level 4 - get last PPP transmit and receive log information
level 10,11 - get & reset statistics

This lists all diagnostics provided for the device at all its supported levels.

VXROUTE

## 13500 LEVEL = 0
VxRoute routing Table
---------------------
Last modification description: %%

VxRoute routing table.

## 13501 LEVEL = 1
VxRoute routing Table
---------------------
Last modification description: %%

VxRoute routing table.

## 13502 LEVEL = 2
Network stack arp Table
-------------------------
%%

The firmware’s dynamic ARP table. Internal use only.

## 13503 LEVEL = 3
Network stack pool
-------------------------
%%

The firmware’s dynamic buffer pools allocation for IP communication. Internal use only.

285
 Software Diagnostics Output

## 13504 LEVEL = 4
VxRoute parameters
--------------------------
Maximal number of reserved entries in routing table : %%1
Calculated number of reserved routing entries in network pool: %%2
How long in ticks to keep route, 0 if forever : %%3
Avoid sending gratuitous ARP requests ? : %%4
Keep dynamic route for opened TCP sockets : %%5
When receiving ICMP avoid update routing table? : %%6
When receiving TCP avoid update routing table? : %%7
When receiving UDP avoid update routing table? : %%8
When receiving IGMP avoid update routing table? : %%9

1. The maximum number of entries in the dynamic IP routing table. Reflects the Size of dynamic IP
routing table Advanced site configuration parameter. 0=disable dynamic IP routing feature, -1=firmware
dependent. If the table is full, the RTU cannot communicate with new/learned IP addresses for a limited
time until an entry becomes vacant. This is to prevent resource exhaustion and denial of service.

2. If the previous parameter is -1=firmware dependent, this parameter reflects the actual number of entries
allocated by the firmware in the dynamic IP routing table. Otherwise, this value is equal to the previous
parameter.

3. The number of ticks (milliseconds) to keep a new learned learned IP address in the dynamic IP routing
table. If there is no activity with that host/RTU for this period, that entry will be cleared. Reflects the
Time to keep dynamic IP route Advanced site configuration parameter. (0=keep forever)

4. Whether or not gratuitous ARP transmissions are sent. Reflects the Avoid gratuitous ARP Advanced
site configuration parameter.

5. Whether or not to keep an entry in the dynamic IP routing table for an opened TCP socket, if there is
no activity for the period of time specified in 3 above. Reflects the Keep dynamic route for open socket
Advanced site configuration parameter. (TCP socket only)

6. Whether the RTU should learn the dynamic IP route when receiving an ICMP transmission, and update
the routing table accordingly. Reflects the Learn route-ICMP receive Advanced site configuration
parameter. Can be one of: Always learn/Never learn/Learn if not modified.

7. Whether the RTU should learn the dynamic IP route when receiving an TCP transmission, and update
the routing table accordingly. Reflects the Learn route-TCP receive Advanced site configuration
parameter. Can be one of: Always learn/Never learn/Learn if known ID.

8. Whether the RTU should learn the dynamic IP route when receiving an UDP transmission, and update
the routing table accordingly. Reflects the Learn route-UDP receive Advanced site configuration
parameter. Can be one of: Always learn/Never learn/Learn if known ID.

9. Whether the RTU should learn the dynamic IP route when receiving an IGMP (multicast)transmission,
and update the routing table accordingly. Reflects the Learn route-IGMP (multicast) receive Advanced
site configuration parameter. Can be one of: Always learn/Never learn.

Note: IPv4 generally assigns Class D addresses (224.0.0.0 through 239.255.255.255.)

286
 Software Diagnostics Output

## 13505 LEVEL = 5
%%

The VxRoute Internal dynamic list. After retrieving this diagnostic, the counters 6-11 are always cleared.

## 13510 LEVEL = 10, 11

VxRoute routing statistics
--------------------------
Last failure code in job : %%
Last failed description : %%
Number of times job queue filled : %%
Number of times failed set route : %%
Number of times succeed set route: %%
Number of times failed set route : %%
Number of times succeed set route: %%
Number of times did not update routing when received ICMP request: %%
Last ICMP request received that did not update routing table : %%
Number of times did not update routing when received UDP request : %%
Last UDP request received that did not update routing table : %%
Number of times did not update routing when received TCP request : %%
Last TCP request received that did not update routing table : %%
Number of times did not update routing when received IGMP request: %%
Last IGMP request received that did not update routing table : %%

VxRoute routing statistics.

## 13555 LEVEL = 255

VxRoute available diagnostics levels
-------------------------------------
Level 0 - Get routing Table in form 1
Level 1 - Get routing Table in form 2
Level 2 - Get arp table
Level 3 - Get Network Stack Memory Pools
Level 4 - Get Dynamic Routing Table parameters
Level 5 - Get Dynamic Routing Table state and & reset statistics
Level 10,11 - Get & reset (level 10) statistics
Level 255 - This list

This lists all diagnostics provided for the device at all its supported levels.

287
 Software Diagnostics Output

CAPPL (ACE3600)

## 13600 LEVEL = 0
Loaded 'C' blocks info.list ptr :%% 1
Unloaded 'C' blocks info.list ptr :%% 2
Loaded 'C' blocks data list size :%% 3
Actual number of loaded 'C' blcoks :%% 4
Actual number of unloaded 'C' blcoks :%% 5
Is 'Debug' block loaded :%% 6
Is 'UnDebug' block loaded :%% 7
Memory pool size for 'C' dynamic allocations :%% 8
Memory pool ptr for 'C' dynamic allocations :%% 9
100Ms timers handle :%% 10
10Ms timers handle :%% 11
Session comm. Master channel handle :%% 12
C heap handle :%% 13

1. Memory start address of loaded 'C' blocks data array

2. Memory address of unloaded 'C' blocks data array

3. Number of entries in loaded 'C' blocks data array

4. Number of 'C' blocks that were successfully loaded by the system

5. Number of 'C' blocks that failed their load by the system

6. Whether the user can debug the 'C' application control function

7. Whether the user can undo the debug of the 'C' application control function

8. Size of memory that is used by 'C' application allocations

9. Start address of memory that is used by 'C' application allocations

10. Memory address of 'C' application 100ms timers

11. Memory address of 'C' application 10ms timers

12. Memory address of 'C' application session comm. Handler

13. Memory start address of 'C' buffers heap

Note: a loaded 'C' block is a block which was loaded for run by the OS.

## 13601 LEVEL = 1
Ucalls RAM table
Address Name
--------------------------

The list of the addresses of 'ucall' functions expected by the Ladder and their names, as they appear in the
flash after download of the Ladder and/or C block.

288
 Software Diagnostics Output

## 13602 LEVEL = 2
Loaded 'C' blocks info. list
Mdl name Mdl path 'C'-block name jumptbl addr ctrlfunc addr
------------------------------------------------------------------------------
-------------

The list of loaded 'C' blocks with the location they were downloaded from, their name, user_jumptable
address in RAM memory and user_control_function address in RAM memory.

## 13603 LEVEL = 3
VxWorks current status for all the loaded modules:

The VxWorks operation system list of loaded 'C' blocks and the data kept about them by the OS.

## 13604 LEVEL = 4
Debug main callback function address: %% 1
Message queue of debug hook activation task: %% 2
Message queue of debug control activation task: %% 3
End debug semaphore: %% 4
End initalization semaphore: %% 5
Control code passed to debug tasks: %% 6
Time left to resume debug before user request to resume: %% 7

1. Memory address of the 'start debug' hook function

2. Message queue that is used by the task that activates the hook function

3. Message queue that is used by the task that activates the 'C' loaded blocks control functions

4. Memory address of semaphore in charge of debug termination

5. Memory address of semaphore in charge of debug initialization

6. Current control state which may be debugged

7. Time left to resume debug and continue the system's run after system starts up

## 13605 LEVEL = 5
Memory pool information:

VxWorks operation system information about the memory partition that reflects the 'C' application
dynamic memory pool.

## 13606 LEVEL = 6
Messages queues information:

OS information about the message queues that serve the 'C' application debug session.

289
 Software Diagnostics Output

## 13607 LEVEL = 7
Semaphores information:

OS information about the semaphores that serve the 'C' application debug session.

## 13608 LEVEL = 255

Level 0 - device key main fields
Level 1 - ucalls RAM table
Level 2 - Loaded 'C' blocks info. list
Level 3 - VxWorks moduleShow
Level 4 - Debug information
Level 5 - Memory pool information
Level 6 - Messages queues information
Level 7 - Semaphores information
Level 255 - This list

This lists all diagnostics provided for the device at all its supported levels.

PLCxIP (where x = the PLCx Link name)

## 13650 LEVEL = 0
Port name : %% 1
PLC access control device key : %% 2
PLC heap device key : %% 3
Port IP interface name : %% 4
TCP listening port : %% 5
TCP listening socket address : %% 6
TCP listening socket ID : %% 7
Maximum number of master connections : %% 8
Actual number of master connections : %% 9
Connections area start RAM address : %% 10
Connections area lock by task : %% 11
Connections area number of locks : %% 12
Listening task ID : %% 13
Is MODBUS backend ready : %% 14
Is periodic activity disabled : %% 15
TCP port is not filtered by firewall : %% 16
MODBUS TCP slave device NOT supported: %% 17

1. The ACE3600 RTU CPU port name, i.e. one of ETH1, PI1, PI2, SI1, SI2.

2. The PLC access control device key.

3. The device key for the PLC heap for incoming/outgoing requests/responses.

4. The name of the IP port’s interface name, i.e. one of motfcc1, motfcc2, motscc1, motscc2, motscc3.

5. The TCP listening port as configured in port’s advanced configuration.

6. The address of the listening socket on the TCP listening port, which permits the port to accept new
connections and to exchange data with the master.

290
 Software Diagnostics Output

7. The listening socket ID on TCP listening port, which permits the port to accept new connections and
to exchange data with the master.

8. The maximum number of master connections for the port.

9. The actual number of on-going master connections via this port.

10. The starting address in the RAM of the area which stores data on the PLC connections.

11. The task name that currently locks access to the connections data.

12. The total number of locks on the onnections data.

13. The listening task ID.

14. Whether the required MODBUS add-on file is burned/loaded in RTU.

15. Whether periodic activity of the connections validation is disabled.

16. Whether the TCP port is not filtered by firewall.

17. Whether the MODBUS TCP slave device is NOT supported. This occurs when the creation of the
PLCxIP device failed.

## 13650 LEVEL = 1
Connections:
ID State Socket: ID port address Last-RX Last-TX PrevSockID
---------------------------------------------------------------------

The table of connections listed for this PLCxIP device.

ID - Connection ID

State - Init/OK/Unstable/Disconnected

Connection socket:

ID – Connection’s socket ID

Port – Master’s TCP connection port

Address – IP address of the master’s TCP port

Last-RX - Last time the slave received via this connection.

Last-RX - Last time the slave transmitted via this connection.

PrevSockID - In case of disconnected connection, the socket ID before disconnect.

291
 Software Diagnostics Output

## 13652 LEVEL = 2
RTU's MODBUS slave RX tasks information:

RX task information for each active/unstable connection.

## 13653 LEVEL = 3
The last master request received on this connection AND the last slave response transmitted on this
connection.

## 13654 LEVEL = 4
Statistics:
Number of forced connection terminations: : %% 1
Number of released connection terminations: : %% 2
Number of connections closed by check alive: : %% 3
Number of ignored master requests: : %% 4
Number of overquota master accesses: : %% 5
Number of rejected masters accesses: : %% 6
Number of canceled authorized masters: : %% 7

1. The number of connections which were forced to terminate due to an IP interface availablity problem.

2. The number of connections released due to planned connections terminations.

3. The number of connections that were closed due to check alive timeout.

4. The number of invalid incoming master requests.

5. The number of times the master requested to open a new connection while maximum connections
were already opened.

6. The number of times master requests were rejected due to authorization filtering.

7. The number of times a cancelled authorized master tried to access the slave.

## 13655 LEVEL = 5
Connections IDs pool:
Is ID used ID assigned to connection

A table listing the occupied /free connection IDs for the PLCxIP device.

## 13655 LEVEL = 5
Connections IDs pool:
Is ID used ID assigned to connection
--------------------------------------

A table listing the occupied /free connection IDs for the PLCxIP device.

292
 Software Diagnostics Output

## 13656 LEVEL = 6
Incoming masters requests message queue information:

The incoming master requests message queue data.

## 13657 LEVEL = 255

level 0 - device key main fields
level 1 - masters connections data
level 2 - MODBUS slave RX tasks information
level 3 - last RXed request & last TXed response
level 4 - statistics
level 5 - connections IDs pool data
level 6 - Incoming masters requests message queue information
level 255 - This list

PLCIPAC

## 13700 LEVEL = 0
Maximum number of authorized masters : %% 1
Actual number of authorized masters : %% 2
Actual number of managed connections : %% 3
Last rejected master's IP address : %% 4
Last rejected master's TCP port : %% 5
Last rejected master's alert status : %% 6
Access control area is locked by task : %% 7
Access control area number of locks : %% 8

Authorized masters data

IP-address Via PLC port Total connections Active connections Unstable connections
---------------------------------------------------------------------------

1. The maximum number of authorized masters which can connect to the slave.

2. The actual number of authorized masters connected to the slave.

3. The actual number of the slave’s managed connections.

4. The IP address of the master which was last rejected.

5. The TCP port of the master which was last rejected.

6. The alert status of the master which was last rejected (the rejection is logged in the Error Logger.)

7. The name of the task which currently locks access to the device data .

8. The total number of locks on the slave’s connection data.

A table listing the authorized masters data - a refelection of the PLC IP access control system table as kept
under the device key.
293
 Software Diagnostics Output

## 13701 LEVEL = 1
Authorized masters history:
IP-address Via PLC port Alert
-----------------------------------

The list of masters whose authorization was canceled.

## 13702 LEVEL = 2
PLC access control Read function: : %% 1
PLC access control Write function: : %% 2
Is periodic activity disabled: : %% 3

1. The RAM address of the ‘Read’ function from the PLC IP access control table.

2. The RAM address of the ‘Write’ function to the PLC IP access control table.

3. Whether the periodic activity of synchronizing between the ladder's table and device key replica is
disabled.

## 13703 LEVEL = 255

level 0 - Authorized masters data
level 1 - Authorized masters history
level 2 - device key main fields

## 13750 LEVEL = 0
Remote TCP port: %%1
Keepalive mode: %%2
Keepalive timeout: %%3
Connection timeout: %%4
Max connections: %%5

User parameters of the MODBUS master.

## 13751 LEVEL = 1
Modbus Address Socket Id IP Address Creation Time Transmits Receives
Time since last Rx
------------------------------------------------------------------------------
------------------

A connection table which contains information about the active Modbus connections:

Modbus Address The PLC address

Socket Id The VxWorks socket ID.

IP Address The slave IP address.

Creation Time The time in seconds since the connection was created.

294
 Software Diagnostics Output

Transmits The number of transmitted packets.

Receives The number of received packets.

Time since last Rx The time in seconds since the last received packet.

## 13753 LEVEL = 10, 11

Connection create errors: %%1
Transmissions errors: %%2
Receive errors: %%3
Number of closed connections: %%4
Wrong transmission id errors: %%5

1. The number of times failed to create connections.

2. The number of times a packet failed to be transmitted.

3. The number of times the master did not receive a reply from the slave.

4. The number of connections that were closed due to an error.

5. The number of bad slave responses.

## 13754 LEVEL = 255

level 0 - User parameters
level 1 - Masters connections table
level 2 - Last RXed request & last TXed response
level 10 - Errors
level 255 - This list

This lists all diagnostics provided for the device at all its supported levels.

TMSEQSY

## 13800 LEVEL = 0
Time & sequence device key : %%1
FrameID : %%2
EMI device key : %%3
Time & sequence EMI's TX ID : %%4
Time & sequence EMI's RX ID : %%5
Time & sequence packet transit delay: %%6
Is Frame synchronized by NTP/GPS? : %%7

1. Internal use.

2. Internal use.

3. Internal use.

4. Internal use.

295
 Software Diagnostics Output

5. Internal use.

6. The Time&Sequence packet transit delay from the main CPU to the I/O expansion module, as
configured in the STS.

7. Whether the I/O expansion module time is synchronized by an NTP/GPS source or by the main CPU.

## 13801 LEVEL = 1
Global posix seconds : %%1
Global posix nanoseconds : %%2
Time stamp sampled on TX : %%3
PPM sampled on TX : %%4

This diagnostic displays the ‘clock values’ that are used to synchronize the I/O expansion module. If the
diagnostics are retrieved for the main CPU, the values of these fields reflect the synchronization source’s
values on the last packet transit. If the diagnostics retrieved for the I/O expansion modules, the values of
these fields reflect the synchronization source’s values on the last packet received.

## 13802 LEVEL = 2
Expansion module's time sync counter : %%
Expansion module's sequence sync counter : %%
Expansion module's calculated drift factor: %%
Expansion module's count for 'PPM was not recalculated': %%
Expansion module's calculated PPM : %%
Expansion module's minimal calculated PPM : %%
Expansion module's maximal calculated PPM : %%

Relevant for I/O expansion module. This diagnostic displays the factors involved in the PPM calculation
on this module. It also displays the last, minimal and maximal PPM values calculated along the sync
iterations (main CPU transmit - expansion module receive) of this module.

## 13803 LEVEL = 10, 11

Frame ID #received TMSEQ frames/#transmissions failures to Frame ID
------- ---------------------------------------------------------

For the main CPU, this diagnostic counts the number of failed transmissions of Time&Sequence packets
to each of the expected I/O expansion frames in the overall system.

For the I/O expansion module, this diagnostic counts the number of successful receptions of
Time&Sequence packets in this specific expansion module.

296
 Software Diagnostics Output

## 13804 LEVEL = 255

level 0 - device key main fields
level 1 - time & sequence packet contents
level 2 - Expansion module's PPM data
level 10 - Frame ID and MAIN CPU TX failures / Expansion Module RX packets
counters display and reset
level 11 - Frame ID and MAIN CPU TX failures / Expansion Module RX packets
counters display
level 255 - This list

This lists all diagnostics provided for the device at all its supported levels.

MI (MAPIMAGE)

## 13820 LEVEL = 0
Map Image / General information:
Is Main CPU (1=Yes, 0=No) %%
My Frame ID %%
EMI Key %%
IoeCommands section ID %%
IoeInfo section ID %%
IoePsInfo section ID %%

Map Image general information. For internal use only.

## 13821 LEVEL = 1
Map Image / MCPU General information:
-------------------------------------
# of "expected" expansion frames %%
Last error led color %%
Last config led color %%
Last IO_FAIL bit status %%
# of userrom_handle_flags() errors %%
Internal reserved flags %% (See level 20 for the flags' decoding)

Map Image – main CPU general information. For internal use only.

## 13822 LEVEL = 2
Map Image / MCPU information per expansion frame / general:
GetNextReport Last Read CMD CMD
Frame Frame Mark Frame indicated setEvOvfl SetHwTestOpr IoeImage Encryption PushB1Opr ErrLedColor CnfLedColor
ID disconnected disconnected disconnect counter errors errors Key errors errors errors errors
==== ============ ============ ============= ========= ============ ======== ========== ========== =========== ===========
%% %% %% %% %% %% %% %% %% %% %%

Map Image – main CPU general information per expansion frame. For internal use only.

297
 Software Diagnostics Output

## 13823 LEVEL = 3
Map Image / MCPU information per expansion frame / IoeInfoImages:
Frame ID BAT1V BAT2V setEvOvfl counter reservedFlags (See level 20 for the flags' decoding)
======== ======= ====== ================= =============

Map Image – main CPU information per expansion frame. For internal use only.

## 13824 LEVEL = 4
Map Image / MCPU information per expansion frame / IoeCommandImages, part 1:
Frame ErrLedColor CnfLedColor ScanInPS ScanOutPS1 ScanOutPS2 HwTestOpr HwTestOpr pushB1Opr pushB1Opr EncryptionKey
ID counter counter counter counter data counter data data
===== =========== =========== ========= ========== ========== ========= ========= ========= ========= =============
Map Image – main CPU information per expansion frame. For internal use only.

## 13825 LEVEL = 5
Map Image / MCPU information per expansion frame / IoeCommandImages, part 2:
Frame ePS1Out ePS2Out
ID [0] [1] [2] [3] [4] [0] [1] [2] [3] [4]
==== ===== ===== ===== ===== ===== ===== ===== ===== ===== =====

Map Image – main CPU information per expansion frame. For internal use only.

## 13826 LEVEL = 6
Map Image / MCPU information per expansion frame / InxOfFrameId:
Frame ID Index in MCPU arrays
======== ====================
Map Image – main CPU information per expansion frame. For internal use only.

## 13827 LEVEL = 7
Map Image / Expansion Frame / IoeCommandImages, part 1:
ErrLedColor CnfLedColor resetEvOvfl ScanOutPS1 ScanOutPS2 HwTestOpr HwTestOpr PushB1Opr PushB1Opr EncryptionKey
counter counter counter counter data counter data data
============ =========== =========== ========== ========== ========= ========= ========= ======== =============
Map Image –expansion frame information. For internal use only.

## 13828 LEVEL = 8
Map Image / Expansion Frame / IoeCommandImages, part 2:
ePS1Out ePS2Out
[0] [1] [2] [3] [4] [0] [1] [2] [3] [4]
===== ===== ===== ===== ===== ===== ===== ===== ===== =====
Map Image –expansion frame information. For internal use only.

## 13829 LEVEL = 9
Map Image / Expansion Frame / General information:
IoeInfoImage.setEvOvfl counter %%
Read MCPU command errors %%
getHwTestOpr errors %%
pushB1Opr errors %%
setEncryptionKey errors %%

Map Image –expansion frame general information. For internal use only.

298
 Software Diagnostics Output

## 13830 LEVEL = 255

Map Image levels:
Level 0 - General information:
Level 1 - MCPU General information:
Level 2 - MCPU information per expansion frame / general
Level 3 - MCPU information per expansion frame / IoeInfoImages
Level 4 - MCPU information per expansion frame / IoeCommandImages, part 1
Level 5 - MCPU information per expansion frame / IoeCommandImages, part 2
Level 6 - MCPU information per expansion frame / InxOfFrameId
Level 7 - Expansion Frame / IoeCommandImages, part 1
Level 8 - Expansion Frame / IoeCommandImages, part 2
Level 9 - Expansion Frame / General information, including the IoeInfoImage
Level 20 - IoeInfoImage Reserved flags' decoding

This lists all diagnostics provided for the device at all its supported levels.

## 13831
Diagnostic level is not applicable to expansion frame

If the user asks the main CPU for a diagnostic that is applicable only to the expansion modules, this
message is displayed.

## 13832
Diagnostic level is not applicable to main frame

If the user asks an expansion module for a diagnostic that is applicable only to the main CPU, this
message is displayed.

## 13833 LEVEL = 20
Reserved bit:
IO_Fl = 0x0001 (System reserved flag number 0)
MainFail = 0x0002 (System reserved flag number 3)
ErrLog = 0x0004 (System reserved flag number 16)
TimTag = 0x0008 (System reserved flag number 17)
PushB1 = 0x0010 (Push button 1 is pressed,while push button 2 is not
pressed)
Warn = 0x0020 (System reserved flag number 22)
Messg = 0x0040 (System reserved flag number 23)
ErAlmostFul = 0x0080 (System reserved flag number 24)
ErFull = 0x0100 (System reserved flag number 25)
ActivePS = 0x0200 (System reserved flag number 27)
PS1_MainFail = 0x0400 (System reserved flag number 28)
PS2_MainFail = 0x0800 (System reserved flag number 29)
PS1_12VDoFail = 0x1000 (System reserved flag number 30)
PS2_12VDoFail = 0x2000 (System reserved flag number 31)
expSyncFail = 0x8000 (System reserved flag number 33)

Reserved flags from the Reserved Flags system table.

299
 Software Diagnostics Output

EMI

## 13853 LEVEL = 10, 11

Display and reset general and peers counters
-------------------------------------------
General counters
----------------
Num of under-run errors (Tx): %%
Num of overrun errors (Rx): %%
Num of collisions (Tx): %%
Num of CRC errors (Rx): %%
Num of non-core frames MAC address not registered (Rx): %%
Num of RX length errors: %%
Num of total TX non-core packets: %%
Num of total RX non-core packets: %%
Num of times avoided response due to Rx disabled: %%
Num of times slave avoided response due to Tx disabled: %%
Num of times master Rx from non-active frame: %%
Microcode FCC hook error counter %%
Corrupted frame index counter: %%
--------------
Peers counters
--------------
1. Number of Rx error (common counter to different cases)
2 .Number of TX packets sent to a specific Frame
3. Number of correctly RX packets received from a specific frame
4. Number of over-sized received frames
5. Number of no responses from slaves (master only)
6. Number of frame index errors
--------------
Peer ID | 1. | 2. | 3. | 4. | 5. | 6 |
---------------------------------------------------------------

General and peer counter information. Diagnostic 10 performs counters reset and diagnostic presentation
while diagnostic 11 (#13854) displays counter data without resetting countersc.

MNTR

## 13870 LEVEL = 0
List of chaining tasks
Frame ID Task ID Last error

This diagnostic lists the download chaining tasks. There is one task per each configured I/O expansion
frame.

Frame ID - The I/O expansion frame ID.

Task ID - MTE task ID

Last Error - The code of last error occurred in chaining task.

300
 Software Diagnostics Output

## 13871 LEVEL = 1
Last download chaining time:
File name: %%1
File length (bytes): %%2
File ID: %%3
Chaining total time (msec): %%4
Frame ID time (msec)
-------------------------
5%% 6%%

This diagnostic displays the details of last chaining operation.

1. The chained file name

2. The chained file size in bytes

3. The chained file type ID

4. The time it took to download chain the file to all I/O expansion frames (in msec).

Frame ID The specific frame ID.

time The time it took to chain the file to each I/O frame (in msec).

## 13872 LEVEL = 255

Monitor Diagnostic Levels
level 0: Chaining Tasks Info
level 1: Last download chaining time

This lists all diagnostics provided for the device at all its supported levels.

301
 Software Diagnostics Output

IOEMNGR

## 13900 LEVEL = 0
IOEManager configuration parameters
-------------------------------------
Is auto recognition enabled : %%1
Number of expected frames : %%2
List of expected frame IDs : %%3
Number of registered frames : %%4

Physical port interface name : %%5

Expansion port MAC address : %%6
Base site ID for frames : %%7
Link ID of port : %%8
Use of NTP for time sync frames : %%9

IP address provided for frame ID 1 : %%10

Network mask provided for all frames : %%11
IP Gateway provided for all frames : %%12

IP address of expansion port : %%13

Network mask of expansion port : %%14
IP Gateway of expansion port : %%15

UDP control socket ID : %%16

TCP control socket ID to listen : %%17
TCP data socket ID to listen : %%18

Timeout waiting for recognition to complete [sec] : %%19

Timeout waiting for auto-recognition to complete [sec] : %%20
Timeout waiting for detecting frames during auto-recognition [sec]: %%21
Timeout waiting for frame to complete loading image [sec] : %%22
Timeout waiting for frame to complete initialization [sec] : %%23
Timeout waiting for frame to connect to EMI protocol [sec] : %%24
Timeout a failed frame is recognized as disconnected [sec] : %%25
Timeout after fail download to declare frame as disconnected [sec]: %%26
KeepAlive Time interval from frame [sec] : %%27
KeepAlive Time interval from frame when not being connected[sec] : %%28
Response time expected for sending a request to a frame [sec] : %%29
Wait time for connection during startup [msec] : %%30
Redundancy recovery timeout [msec] : %%31
Redundancy connect timeout [msec] : %%32
Redundancy peer IP address : %%33
Redundancy interface name : %%34

Main CPU (I/O Expansion Manager) Diagnostics:

1. Yes if auto-recognition is enabled (with default configuration or with a burned configuration).

2,3. - Number and list of configured frames. If auto-recognition is enabled, this is the number of detected
frames. Only these frames may connect. (Each frame has a rotary switch with that ID.)

4. A list of frame IDs that havebeen registered and may or may not be connected at this time. This list
shows the expansion modules that have registered and detected regardless if their cable is now connected
or not. It is a subset of the list in 3.

302
 Software Diagnostics Output

5. motfcc1 - the internal interface name for the ETH1 port.

6. The MAC address of the ETH1 port in the main CPU.

7. The site ID of frame ID #1 (i.e. the frame whose rotary switch is set to 1.) Each expansion module
learns its own site ID from the main CPU, according to this number, and its rotary ID.

8. The Link ID of the expansion port, as specified by the user configuration. Default is 25 (= LINE5.)

9. As an option, the NTP may be used for time synchronization of all expansion modules. This is a I/O
Expansion Manager advanced parameter. By default it is set to No, meaning that the EMI is used for time
synchronization.

10. The IP address of frame ID #1, as specified in the I/O Expansion Manager advanced parameter.

11. The network mask address of all expansion frames. Currently it is the same as configured by the user
in the expansion port of the main CPU.

12. The IP address of the gateway for all expansion frames. Currently it is the same as configured by the
user in the expansion port of the main CPU and does not serve any purpose (for future use).

13. The IP address of the Expansion port in the main CPU.

14,15. The Network mask and default router of the expansion port in the main CPU.

16. The UDP connection port number that is used for discovery of the main CPU and for providing IP
addresses for each expansion module. By default it is 57001, and may not be altered by the user.

17,18. The TCP connection and data/load port numbers for initializing the expansion module, and for
detecting connectivity with the main CPU. This can be configured in the I/O Expansion Manager
advanced parameters.

19,20,21,22,23,24,25,26,27,28,29. Various timeouts controlled by the user. For details, see the I/O
Expansion Manager advanced parameters in “Appendix A: Site Configuration Parameters” of the
ACE3600 STS User Guide.

30. This timeout is automatically learned during startup of the main CPU, and determines, in
milliseconds, how long to wait for the EMI to connect with all configured frames, before continuing the
startup operation of the main CPU.

31. Advanced IO Expansion Manager parameter. Relevant for the main CPU only. After active
switchover, the number of seconds the new active main CPU should wait for the expansion CPUs to
connect with it. If after that period they fail to connect, the main CPU will issue a restart command for all
expansions. If this parameter is set to zero, the main CPU will issue a restart command immediately after
the switchover.

32. Advanced IO Expansion Manager parameter. Relevant for a standby CPU when the site supports I/O
auto recognition. The number of seconds the standby CPU waits for the active CPU to complete I/O auto
recognition and send the recognized I/O module information to the standby CPU so it can complete the
startup.

33. With dual CPU, this is the peer IP address over the internal Ethernet port between primary and
secondary.

303
 Software Diagnostics Output

34. With dual CPU, this is the internal name of Ethernet port connecting the primary and secondary
CPUs.

## 13901 LEVEL = 1
IOEManager state and timers for each expected frame
---------------------------------------------------------

Frame Current state Prev. Current state Prev. state Last reception
ID State start time State elapsed time Elapsed Time elapsed time
---- ----- ------------- ----- ------------ ------------- --------------
%%1 %%2 %%3 %%4 %%5 %%6 %%7

This diagnostic lists all expected/configured expansion modules and their states in the main CPU.

1. The frame ID of the expansion module, as determined by its rotary switch.

2. The current state of the expansion module. Can be one of:

• -- (it has not been detected),

• Discovered,

• Loading firmware from main CPU,

• Initializing - The expansion image is loading the application files.

• Registered - The module has registered its local I/Os and power supply.

• Ready - The module has completed system startup and is ready to connect EMI. It also means it is
waiting for the EMI to connect, so if this takes a few seconds or more, check the cable.

• Connected - The module is communicating successfully with the main CPU via the EMI.

• Fail - The module was connected, but then was disconnected; check the cable.

• Fail-timeout - The module was in fail for "fail timeout". This duration is specified by the user.
By default, it is 1 minute.

• Fail-download - The main CPU failed to download the application to the expansion module, and
therefore it is about to restart it.

3. The time when the expansion module entered the current state.

4. The time when the expansion module entered the previous state.

5. How long the expansion module has been in the current state.

6. How long the expansion module was in the previous state.

7. The time elapsed since the main CPU last received any communication from the expansion module via
the connectivity channel.

304
 Software Diagnostics Output

## 13902 LEVEL = 2
IOEManager status attributes for each expected frame
----------------------------------------------------
Control Is Is
Frame Data IP address EMI Data IO
ID Identity MAC address Loader Version Image Version Sockets and TCP port On On Info
--- ------- --------- ----------- ---------- ------ ---------- -- ---- ---
%%1 %%2 %%3 %%4 %%5 %%6 %%7 %%8 %%9 %%10

This lists all expected/configured expansion modules and their states in the main CPU.

1. The frame ID of the expansion module, as determined by its rotary switch.

2. The expansion module identity derived from its MAC address.

3. The MAC address of the expansion module.

4. The Expansion Loader firmware version. You can also see this in the Hardware Test.

5. The Expansion Image firmware version.

6. The control and data socket IDs. Usually the data is 000. This is for internal use.

7. The IP address and TCP connectivity port number of the expansion module.

8. Yes, if the EMI (master) has been activated for this module, i.e. EMI tranmsissions are performed
periodically.

9. Yes, if the expansion module is in loading or initializing state, and uploading image or application files.
Usually it is No.

10. I/O Info. For internal use.

## 13903 LEVEL = 10, 11

IOEManager statistics
---------------------
Number of new requests from frames pending authentication : %%1
Number of times new requests ignored from unauthenticated frames : %%2
Number of times rejected new requests from unauthenticated frames : %%3
Number of times authenticated new requested from frames : %%4
Number of times failed authenticate new requests from frames : %%5
Number of request/response received with bad type : %%6
Number of request/response received with bad identity : %%7
Number of request/response received for unexpected frame ID : %%8
Number of illegal frames received : %%9
Number of times failed allocate IP address for expansion modules : %%10

1. For security purposes, each expansion module is authenticated when initialized. This shows the current
temporary number of expansion frames waiting for authentication. Usually it shows 0.

2. The number of requests from expansion modules failed authentication in the past. It is not uncommon
for this number to be non zero, as retries may overrule previous requests.

3. The number of times requests from expansion modules were dropped as they were not authenticated in
time or found to be invalid.

305
 Software Diagnostics Output

4. The number of times expansion modules were authenticated.

5. The number of times internal failures prevent authentication of expansion modules. Internal use only.

6,7,9. The number of illegal requests which were ignored.

8. The number of requests ignored because they came from frames that were not configured by the user.
Note: When the RTU is configured for auto-recognition, frames that were not detected during startup are
considered unexpected. This number will be incremented when getting requests from these unexpected
frames as well.

10. The number of expansion modules that failed to obtain an IP address from the main CPU. This is a
result of an "out of range" IP address, being on a seperate netmask or a default router IP. This is a result
of a configuration error for the expansion port IP address and network mask. . An error is logged as well.
Number Number Number Number Number Number Last Last Number Number Last Last
Frame Connect Disconn. Reset Busy Error Unknowns Error Request EMI EMI EMI EMI
ID Events Events Events Replied Replied Replied Replied Denied Ignored Process Ignored Processed
----- ------- ------- ------ ------- ------- -------- ------- ------- ------- ------- ------- --------
%%1 %%2 %%3 %%4 %%5 %%6 %%7 %%8 %%9 %%10 %%11 %%12 %%13

This lists all expected/configured expansion modules and their state in the main CPU.

1. The frame ID of the expansion module, as determined by its rotary switch.

2. The number of times the frame was connected at the EMI level.

3. The number of times the frame was disconnected. A frame needs to be connected in order to be
disconnected. This could be as a result of cable disconnect, or download failure.

4. The number of times the expansion module was restarted. This could be as a result of expansion
module power cycle, or disconnected cable for "fail timeout" (1 minute by default), or because of
download.

5-13. Internal. This is for debugging the handshake between the main CPU and expansion modules.

## 13905 LEVEL = 255

IOEManager diagnostic levels:
-----------------------------
0 - Get configuration parameters.
1 - Get state and timers for each expected frame
2 - Get status attributes for each expected frame
3 - Get redundancy state and statistics
10 - Get and clear statistics
11 - Get statistics
30 - Get redundancy state and clear redundancy statistics
255- This level

This lists all diagnostics provided for the device at all its supported levels.

306
 Software Diagnostics Output

## 13906 LEVEL = 3
IOEManager redundancy state and statistics
-------------------------------------------
Is redundancy supported : %% 1
Redundancy role : %% 2
TCP control socket ID to listen : %% 3
TCP control socket ID : %% 4
TCP control socket IP address and port of peer : %% 5
Is active CPU ready ? : %% 6
Number of frames currently in 'standby ready' state : %% 7
Was standby CPU became active during init ? : %% 8
Is active CPU ready ? : %% 9

Number of times became active : %%10

Number of times became standby : %%11
Number of times detected connection from standby : %%12
Number of times sent standby 'reset' : %%13
Number of times handled 'reset' in standby : %%14
Number request sent to standby : %%15
Number request that were dropped before they were sent to standby CPU : %%16
Number of illegal frames received : %%17
Number of response received and ignored : %%18
Number of requests received and processed : %%19
Number of requests received and ignored : %%20
Number of times standby CPU failed connecting with active CPU : %%21
Number of times restarted expansion as requested by standby CPU : %%22
Time elapsed in current state : %%23
Time elapsed in previous state : %%24
Rack Update IO Info IO info IO info requests request request Request recovery recovery
ID Identity IO Info Size ignored sent sent sent Received Received succeed failed
---- -------- ------- ------- ------- ------- -------- ------- -------- -------- -------- --------
%%25 %%26 %%27 %%28 %%29 %%30 %%31 %%32 %%33 %%34 %%35 %%36

1. YES if redundancy is supported.

2. Redundancy role can be one of Active, Standby or NO Role. NO Role means peer does not exist, or
has not been configured with the I/O expansion manager.

3. The active CPU listens to this TCP socket ID.

4. The standby CPU initiates connection with the active CPU using this socket ID.

5. Relevant for both active and standby CPUs. This is the socket ID and IP address which identifies the
connection.

6-9. Internal use.

10. The number of times the CPU changed roles from standby to active, or to NO role.

11. The number of times the CPU became standby.

12. The number of times the active CPU detected a new connection from the standby CPU.

13. Internal use.

14. Internal use.

307
 Software Diagnostics Output

15. Internal use.

16. Internal use.

17. The number of illegal frames received between the standby and active. Should be 0.

18. Should be 0.

19. The number of requests received from the standby CPU that were processed successfully by the active
CPU.

20. The number of responses received from the active CPU that were process edsuccessfully by the
standby CPU.

21. Internal use.

22. The number of times the expansion restarted in the active CPU, as requested by the standby CPU. For
example, when download configuration to standby CPU.

23. How long has this CPU been in the role specified in Redundancy role above? (hh::mm::ss.milli)

24. How long was this CPU in the previous role? (hh::mm::ss.milli)

25. Rack ID

26. Identity

27-34. Internal use.

35. The number of times expansion recovery succeeded without restarting it, when this CPU was standby
and became active.

36. The number of times expansion recovery failed, e.g. it was restarted, when this CPU was standby and
became active.

308
 Software Diagnostics Output

IOEMCLI

## 13950 LEVEL = 0
IOEM frame client manager parameters
-----------------------------------------
Expansion Port Interface name : %%1
Frame ID : %%2
Frame identity : %%3
MAC address of port : %%4
IOEM Site ID : %%5
MCPU Site ID : %%6
MDLC Link ID of port : %%7
Use NTP for time synchronization with MCPU : %%8
Initialization timeout in seconds : %%9
TCP socket connect/initiate timeout in seconds : %%10
Keepalive send interval to MCPU in seconds : %%11
Keepalive send interval to MCPU when not connected in seconds : %%12
EMI disconnect/fail timeout to restart in seconds : %%13
Expected response time from MCPU in seconds : %%14
UDP Control socket ID (for discovery) : %%15
TCP Control socket ID : %%16
MCPU Primary IP address from discovery: : %%17
MCPU Secondary IP address from discovery : %%18
Current MCPU IP address : %%19

Expansion Module (I/O Expansion Manager Client) diagnostics:

1. Internal use.

2. The frame ID of the expansion module, as determined by the rotary switch during startup.

3. The expansion module identity determined by the hardware MAC address.

4. The MAC address of the expansion port.

5. The site ID is derived from the frame ID, and a non-configurable base address in the main CPU
(currently 65500.)

6. The main CPU site ID configured by the user. By default, 1.

7. The link ID of the expansion port, as configured by the user. By default, 25 (LINE5).

8. Use of NTP protocol to obtain the time of day from the main CPU. This is configurable by the user. By
default it is disabled.

9. Internal use.

10. The number of seconds to wait for a TCP connection to be established. After this time expires, the
expansion module will try to initiate a new one.

11. After initialization is complete, the expansion module maintains the TCP connection with the main
CPU by sending it a ‘keepalive’ every interval. It is necessary to maintain the TCP connection, and
detect a change in connectivity status with the main CPU. This parameter is set by the user. By default it
is set to 60 seconds.

309
 Software Diagnostics Output

12. The expansion module sends a TCP ‘keepalive’ to the main CPU at a shorter interval when first
establishing the connection to the main CPU or when the TCP was disconnected. This parameter is set by
the user and by default is 4 seconds.

13. The ‘fail timeout’ specified by the user. After getting connected, the expansion module monitors the
connectivity both at the TCP and EMI levels. If the EMI gets disconnected, it will wait for this specified
time in seconds, and then restart itself. 0 means it will never restart itself as a result of EMI failure. This
parameter is configurable by the user and by default is 60 seconds.

14. In order to load files during initialization, the expansion module sends requests to the main CPU via
TCP. This parameter determines how long to wait for a reply before retrying. If a retry is made, the
expansion module will disconnect its TCP connection with the main CPU and initiate a new one. This
parameter is configured by the user and by default is 10 seconds.

15. The UDP port number used for performing discovery of the main CPU. Discovery is performed by the
Expansion Loader. This diagnostic is for internal use only. Note that the UDP port number is not
configurable by the user and is set to 57001.

16. The TCP connectivity port number configured by the user. By default it is 57001. The TCP
connectivity port is used for initialization - loading files, registering I/O modules in the main CPU, and
sending ‘keepalive’. It is also used by the main CPU to restart the expansion module.

17. The main CPU IP address.

18. Reserved for future use.

19.The main CPU IP address.

## 13951 LEVEL = 1
IOEM frame client manager current status
----------------------------------------------
State of manager : %%1
Time entered this state: : %%2
Previous state of manager : %%3
How long elapsed in current state (in milliseconds): : %%4
How long elapsed in previous state (in milliseconds): : %%5
How long it took for discovery (in milliseconds): : %%6
How long it took to initialize (in milliseconds): : %%7
How long it took for system startup to get ready (in milliseconds) : %%8
How long to took for EMI to connect with MCPU : %%9
MAC Address of MCPU : %%10
Internal control socket descriptor : %%11
Control socket address of MCPU : %%12
Is EMI active (ready for receive and transmit) : %%13
Internal keepalive state with MCPU : %%14
How long elapsed in current state (in milliseconds) : %%15
Fatal error code that requires restart : %%16

1. IOEM (I/O expansion module) connection state:

• Registered - It has completed initialization and has registered its local I/O modules within the
main CPU.

310
 Software Diagnostics Output

• Ready - Completed initialization and has started EMI Slave.

• Connected - Connected with the main CPU at its EMI level.

• Fail - The module was connected at the EMI level but then was disconnected.

• Fail Timeout - The module was connected for "fail timeout" time.

2. The time of day this state = started. May be Jan 01 during system startup.

3. Previous state.

4. How much time elapsed in present state. Time is displayed as hh:mm:ss.millisec.

5. How much time elapsed in previous state before moving to this one. Time is displayed as
hh:mm:ss.millisec.

6. How long it took to complete discovery. Note that the Expansion Image does not perform discovery if
was done by Expansion Loader, so it is set to 0. Internal use only.

7. How long it took to load files from the main CPU. This does not include the complete system startup of
expansion module.

8. How long it took, from beginning to end, for system startup to complete and get into ‘Ready’ state.

9. How much time elapsed from getting ‘Ready’ until getting ‘Connected’.

10. MAC address of the expansion port in the expansion module.

11. Internal.

12-IP address and TCP port of the main CPU.

13-YES means EMI receiver and transmitter are ready.

14-KeepAlive status. Keepalive has its own state: Disconnected, Connected, Connecting or KeepAlive.

15-How long it has been in the present KeepAlive state.

16-Fatal error code, reported when the expansion module is about to restart.

311
 Software Diagnostics Output

## 13952 LEVEL = 10, 11

IOEM frame client manager statistics
----------------------------------------------
Number of times succeeded connect control socket with MCPU : 1
Number of times failed connect control socket with MCPU : 2
Number of times succeeded connect data socket with MCPU : 3
Number of times failed connect data socket with MCPU : 4
Data block size in bytes to receive files from MCPU : 5
Address of MCPU for receiving data files : 6
Number of read requests sent to MCPU : 7
Number of read responses received from MCPU : 8
Number of illegal frames received from MCPU : 9
Number of discovery requests sent succesfully : 10
Number of discovery responses received : 11
Number of times failed initialize internal discovery socket : 12
Number of times succeeded initialize internal discovery socket: 13
Number of times succeeded send keepalive request to MCPU : 14
Number of times failed send keepalive request to MCPU : 15
Number of times received keepalive response from MCPU : 16
Number of times EMI notification was ignored : 17
Number of times EMI notification was received : 18
Last EMI callback type that was ignored : 19
Last EMI callback type that was processed : 20

1. The number of times the expansion established connection of TCP connectivity channel with the main
CPU.

2. The number of times the expansion failed to establish connection of TCP connectivity channel with the
main CPU.

3. The number of times the expansion established connection of TCP data channel with the main CPU (a
temporary channel used for loading files from the main CPU during initialization of the expansion
module.)

4. The number of times the expansion failed to establish connection for TCP data channel with the main
CPU.

5. The last known block size of each packet received when the expansion module loads files via the TCP
data channel during initialization.

6. The last known IP address and TCP port of the main CPU used by the expansion module for loading
files via TCP data channel during initialization.

7,8. The number of times read requests were sent to the main CPU. During initialization, when files are
read by the expansion module from the main CPU, each file is divided into blocks. The number of read
responses specifies the total number of blocks read.

9. The number of illegal frames received by the main CPU because of incompatibility or communication
errors.

10,11,12,13. Internal use. (Discovery statistics are not shown in these diagnostics).

14. The number of times ‘keepalive’ was sent over the TCP connecivity socket to the main CPU.

312
 Software Diagnostics Output

15. The number of times failed to send ‘keepalive’ over the TCP connecivity socket to the main CPU.
This could be an internal problem such as socket disconnected.

16. The number of times received ‘keepalive’ replies from the main CPU over the TCP connectivity
socket to the main CPU.

17,18,19,20. Refer to communication over EMI. Indicate if cable is connected or not. Internal use only.

## 13955 LEVEL = 255

IOEMClient manager diagnstics levels
--------------------------------------
level 0 - IOEM frame client manager parameters
level 1 - IOEM frame client manager current status
level 10- IOEM frame client manager get and clear statistics
level 11- IOEM frame client manager get statistics
level 255- This level

This lists all diagnostics provided for the device at all its supported levels.

RDNDNCY

## 13980 LEVEL = 0
Redundancy general information:
-------------------------------
Is redundancy supported by HW %% (0-NO 1-YES)
Am I primary %% (0-NO 1-YES)
Am I active %% (0-NO 1-YES)
Is peer active %% (0-NO 1-YES)
Am I alive %% (0-NO 1-YES)
Is peer alive %% (0-NO 1-YES)

General CPU redundancy information: whether the peer is primary orsecondary, active or standby, alive
(operational) or not.

313
 Software Diagnostics Output

## 13981 LEVEL = 10, 11

Redundancy internal counters:
-----------------------------
WD kick counter %%1
last WD kick counter %%2
Minimum WD kicks in 10ms %%3

Number of times giveup activity %%4

Number of times WD was delayed (>3ms) %%5

10MS to active counter %%6

10MS to standby counter %%7
IRQ activity change counter %%8
Task to active counter %%9
Task to standby counter %%10

Number of times fixing activity error %%11

Number of activity errors %%12

1-3. Internal use only.

4. The number of times the firmware initiates redundancy switchover.

5-8. Internal use only.

9. The number of times the CPU became active.

10. The number of times the CPU became standby.

11. The number of times the secondary CPU became standby because of Number of activity errors below.

12. The number of times both CPUs were active or standby at the same time. After several sequential
errors, the secondary CPU becomes standby.

## 13985 LEVEL = 255

Redundancy diagnostic levels:
-----------------------------
level 0 - Redundancy general information
levels 10 & 11 - Redundancy internal counters
level 255 - This level

This lists all diagnostics provided for the device at all its supported levels.

314
 Software Diagnostics Output

RDNDSRV

## 13990 LEVEL = 0
Redundancy service general information
---------------------------- ---------
Is redundancy supported by HW & configuration %%1 (0-NO 1-YES)
Am I primary? %%2 (0-NO 1-YES)

INTR1 Port name %%3

INTR1 IP address %%4
INTR1 Broadcast address %%5
INTR1 Network mask %%6
INTR1 Site ID %%7
INTR1 Link ID %%8
No. of times that customer giveup activity %%9

Customer State Role Peer-role Request Request Done

------- ----- ---- --------- ------- ------------
10%% 11%% 12%% 13%% 14%% 15%%
%% %% %% %% %% %%

1. Whether redundancy is supported.

2. Whether the RTU is the primary redundant peer.

3-8. INTR1 port information. Internal use only.

9. The number of times that the user initiated redundancy switchover (via Hardware Test or ‘C’
application.

10-15. Internal use only.

## 13993 LEVEL = 3
Redundancy services counters:
----------------------------
Customer Start Exit Exist lost IF Socket Nack Unexpected
-------- ----- ---- ----- ------ -- ------ ---- ----------
%%1 %%2 %%3 %%4 %%5 %%6 %%7 %%8 %%9
%% %% %% %% %% %% %% %% %%

1. Communication event customer 0 = I/O hot swap, 1 = Ladder.

2. The number of connections to the peer.

3. The number of disconnects from the peer.

4. The number of disconnects because of a ‘peer not alive’ event.

5. The number of disconnects because of a ‘to active’ or ‘to standby’ event.

6. The number of disconnects because of a dropped link between the peers.

7. The number of disconnects because of socket failure.

315
 Software Diagnostics Output

8. The number of disconnects because of a NACK.

9. The number of unexpected disconnects.

## 13995 LEVEL = 255

Redundancy services diagnostics levels
--------------------------------------
level 0 - Redundancy service general information
level 1 - Socket information
level 2 - Block information
level 3 – Redundancy services counters
level 255- This level

This lists all diagnostics provided for the device at all its supported levels.

## 14200 LEVEL = 0
USB host configuration parameters
---------------------------------

1. Support High Speed USB ? : %%1

2. BLE (bulk List Enable) off ratio (0=never, 1-100) : %%2

3. Memory Partition ID : %%3

4. Memory Partition maximal size : %%4
5. Memory Partition actual size : %%5

6. Module build date and time : %% %%6

1. Whether the port supports high speed USB. YES if the user configured High Speed USB in the
advanced configuration. NO if using Full Speed. Note that devices which support High Speed, will
operate on Full Speed as well.

2. The percentage of time that the USB Host Controller chip accesses the bus (transfer of USB host data
packets (bulk list) is OFF and only control packets are transferred.) (Relevant for Full Speed only.) A
higher value mean transfer of USB host data packets (bulk list) is OFF more. Used to mitigate hardware
performance issues concerning 100Mb Ethernet when the USB Host is used.

3,4,5. The USB internal memory allocation ID, maximum size, and actual size. The maximum size may
be configured in advanced USB parameters.

6. Internal use.

Expected device List

---------------------
HubPort Port Expected USB Expected Vendor/Device IDs Is Times
Location Index Class Sub Prot. #1 #2 #3 #4 Connected? Connected
-------- ----- ---- ---- ---- ------- ------- ------ ---- ---------- ---------
%%1 %%2 %%3 %%4 %%5 %%6 %%7 %%8 %%9 %%10 %%11

The configured/expected USB devices and their expected locations:

1. The expected location marks three coordinates, x.y.z, where x is the port itself, e.g. 1 is HU1 and 2 is
HU2. y is the location in a Hub connected to the RTU, and z is a location in a second Hub connected to

316
 Software Diagnostics Output

the previous one. For example 1.0.0 means port HU1. Note: For firmware 14.00.00 only MotoTrbo may
be configured directly to port HU1 or HU2 with no HUB.

2. The physical location (number) of the port : 7 is HU1 and 8 is HU2.

3,4,5. Expected device USB class, subclass and protocol, as configured.

6,7,8,9. Expected USB device vendor and ID. 0 is ignored. Up to four possible IDs for this device.

10. Whether the device is connected?

11. The number of times the device was connected.

USBCONF

## 14201 LEVEL = 1
Actual device List
---------------------
%%

The list of the actual devices connected to the ACE3600 RTU.

Note that if high speed was configured, two lists appear, one for the full speed devices, and another for
the high speed devices. Note: ACE3600 14.00.00 supports only full speed.

## 14202 LEVEL = 2
%%

The status of the internal hardware PCI bus within the ACE3600 board. Used for internal hardware debug
purposes.

317
 Software Diagnostics Output

## 14203 LEVEL = 3
USB Host OHCI Controller Registers
------------------------------------
Revision register (HcRevision) : %%
Command Status register (HcControl) : %%
Interrupt Status register (HcCommandStatus) : %%
Controller Interrupt Status (HcInterruptStatus) : %%
Interrupt Enable register (HcInterruptEnable) : %%
Interrupt Disable register (HcInterruptDisable) : %%
Communication Area register (HcHCCA) : %%
Periodic Current ED register (HcPeriodCurrentED) : %%
Control Head ED register (HcControlHeadED) : %%
Control Current ED register (HcControlCurrentED) : %%
Bulk Head ED register (HcBulkHeadED) : %%
Bulk Current ED register (HcBulkCurrentED) : %%
Done Head register (HcDoneHead) : %%
Frame Interval register (HcFmInterval) : %%
Frame Remaining register (HcFmRemaining)) : %%
Frame Number register (HcFmNumber) : %%
Periodic Start register (HcPeriodicStart) : %%
LS Threshold register (HcLSThreshold) : %%
Root Hub Descriptor A register (HcRhDescriptorA) : %%
Root Hub Descriptor B register (HcRhDescriptorB) : %%
Root Hub Status register (HcRhStatus) : %%
Port 1 Status Register (HcRhPortStatus1) : %%
Port 2 Status Register (HcRhPortStatus2) : %%

Shows the status of internal OHCI (Open Host Controller Interface) registers within the USB host
controller on the ACE3600 board. Used for internal hardware debug purposes. Refer to Open Host
Controller Interface Specification for USB Rev. 1.0a.

318
 Software Diagnostics Output

## 14204 LEVEL = 4
USB Host EHCI Controller Registers
------------------------------------
CAPLENGTH register : %%
HCIVERSION register : %%
HCSPARAMS register : %%
HCCPARAMS register : %%
HCSP-PORTROUTE register : %%

USBCMD register : %%
USBSTS register : %%
USBINTR register : %%
FRINDEX register : %%
CTRLDSSEGMENT register : %%
PERIODICLISTBASE register : %%
ASYNCLISTADDR register : %%
CONFIGFLAG register : %%

PORTSC1 register : %%
PORTSC2 register : %%

SYSTEM TUNING : %%

Shows the status of internal EHCI (Enhanced Host Controller Interface) registers within the USB host
controller on ACE board. The registers are described in the Enhanced Host Controller Interface
Specification for Universal Serial Bus Rev. 1.0. Used internally for hardware debug purposes.

For information on the non-standard dedicated System Tuning register, used to improve throughput in
USB transfers, refer to ISP1568 Hi-Speed USB PCI Host Controller.

## 14210 LEVEL = 10, 11

USB host configuration and PCI statistics
------------------------------------------
Number of times expected devices were connected : %%1
Number of times expected devices were disconnected : %%2
Number of times non expected devices were connected : %%3
Number of times failed add duplicate devices : %%4
Number of times 60x error original initiated for PCI : %%5
Number of times Illegal register access : %%6
Number of times I2O Error queue overflow inbound : %%7
Number of times I2O Error queue overflow outbound : %%8
Number of times PCI Error Parity Error on write : %%9
Number of times PCI Error Parity Error on read : %%10
Number of times PCI Error System error : %%11
Number of times PCI Error configuration access not available : %%12
Number of times PCI Error no response : %%13
Number of times PCI Error data parity error on read : %%14
Number of times PCI Error data parity error on write : %%15
Number of times PCI Error address parity error : %%16

1. The number of times USB devices configured by the user configured were connected.

2. The number of times USB devices configured by the user were disconnected.

319
 Software Diagnostics Output

3. For future use.

4. The number of times failed to configure a device, because it already is configured. For internal use in
software debugging.

5 – 16. PCI Bus errors. Internal use for debugging the hardware.

Level 10 clears these statistics.

## 14253
Cannot read USB host OHCI controller registers - USB host not configured.

An error displayed if the user requests device level 3, but no USB is configured.

## 14254
Cannot read USB host EHCI controller registers - USB host high speed was not
configured.

An error displayed if the user requests device level 4, but high speed USB was not configured. ACE3600
firmware 14.00.00 supports only full speed USB.

@14255 LEVEL = 255

USB host configuration statistics
-------------------------------
level 0 - USB configuration parameters
level 1 - USB device enumeration
level 2 - PCI registers
level 3 - USB Host OHCI Controller Registers
level 4 - USB Host EHCI Controller Registers
level 10 - Get & reset statistics
level 11 - Get statistics
level 255 - This level

This lists all diagnostics provided for the device at all its supported levels.

## 14300 LEVEL = 1
Remote NDIS channel parameters
-------------------------------
Port name : %%1
HubPort location : %%2
Internal END name : %%3
Internal END cookie : %%4
Number of allocated buffers to receive : %%5
Number of allocated buffers to transmit : %%6
KeepAlive timeout period in milliseconds: %%7
Radio/device description : %%8
Netpool ID : %%9
Netpool number of maximal mblks : %%10
Netpool number of allocated mblks : %%11
Module build date and time : %% %%12

320
 Software Diagnostics Output

1. Port name of the device.

2. The expected location marks three coordinates, x.y.z, where x is the port itself, e.g. 1 is HU1 and 2 is
HU2. y is the location in a Hub connected to the RTU, and z is a location in a second Hub connected to
the previous one. For example 1.0.0 means port HU1.

3. Interface name, “hostusb1” if port HU1.

4. Internal use.

5. The number of (input) buffers to allocate for receive, as specified in the port’s advanced physical
parameters.

6. The size of the queue (output buffers)for transmitting to USB, as specified in “number of allocated
buffers to transmit” in the port’s advanced physical parameters.

7. RNDIS keepalive interval in milliseconds, as specified Remote NDIS Specification version 1.1. If it is
not 0, keepalive is sent periodically, as long as USB connected, over RNDIS control channel to the radio.
If no response, ACM will declare port as “fail” and try and re-configure the radio in RNDIS protocol.

8. Expected radio manufacturer and device ID codes, as configured by the STS.

9. Internal use of network memory pool ID for USB.

10. Number of maximal buffers (memory clusters) used for reception, Derived from the ‘number of input
buffers’ parameter the port’s advanced physical parameters.

11. Current number of buffers (memory clusters) used for reception.

12. Internal use.

321
 Software Diagnostics Output

LINxRND

## 14301 LEVEL = 2
Remote NDIS channel status
---------------------------
Remote NDIS current channel state : %% for %%1
Remote NDIS current command state : %%2
Remote NDIS current command processed : %%3
Remote NDIS last command requestID : %%4
Remote NDIS last command response length in bytes : %%5
Remote NDIS pending command sent length in bytes : %%6

Internal data send queue address : %%7

Internal data send queue size (buffers no) : %%8
Internal data send queue maximal size (buffers no) : %%9
Internal data send queue transmit threshold size : %%10
Is send queue full ? : %%11
Is Remote NDIS channel being stopped ? : %%12
Is device/radio USB attached ? : %%13
Is being in a data callback ? : %%14

Maximal data transfer size in bytes : %%15

Maximal data frame size in bytes : %%16
Last radio/device IP address set in firewall : %%17
Last firewall rule ID set : %%18
My IP Address : %%19
primary DNS IP address : %%20
secondary DNS IP address : %%21

KeepAlive timeout period in milliseconds : %%22

Time passed since last received [milliseconds] : %%23

Is ACM connected ? : %%24

Is ACM being stopped ? : %%25
Is ACM OUT IRP (data) wait for end of transmission? : %%26
Is ACM IN IRP (data input) wait for receive ? : %%27
Maximal data receive buffer size in bytes : %%28
Is INTERRUPT IRP (control input) wait for receive? : %%29
Maximal INTERRUPT receive buffer size in bytes : %%30

In the device name, LINxRND, x denotes LINK ID, e.g. LINE1 is LIN1RND. This diagnostic shows the
MotoTrbo port status for the ACM (Abstract Control Model) class and the Remote NDIS (RNDIS). These
parameters are for internal debugging of these components.

1. State of the control channel with the radio per Remote NDIS Specification version 1.1.

2. Whether the command was sent to the radio via the control channel per Remote NDIS Specification
version 1.1.

3. Marks the response for the command sent in 2.

4. The last required ID of the command sent.

5. The size in bytes of the last command response received from the radio.

6. The size in bytes of the last command sent to the radio that is still pending (no response yet.)

322
 Software Diagnostics Output

7-11. The state of the data send queue when communicating over the radio. Internal use.

12. Yes if the driver is being shut down by the firmware. Internal use.

13. Yes if a radio is attached to the USB port.

14. Yes if in the middle of reception or transmission over data channel. Internal use.

15-16. Maximum transfer size that can be sent to the radio (1558 including RNDIS and Ethernet.)
Maximum frame size that can be sent to the radio (1500 not including RNDIS and Ethernet.)

17. Internal use.

18. Internal use.

19. The last IP address learned from the radio.

20,21. The IP addresses of the the DNS servers configured by the user for the MotoTrbo port, if any.

22. RNDIS keepalive interval in milliseconds, as specified in Remote NDIS Specification version 1.1. If
not 0, a keepalive is sent periodically, as long as the USB is connected, over the RNDIS control channel
to the radio. If no response, ACM will declare the port as failed and try to reconfigure the radio in the
RNDIS protocol.

23. The time in milliseconds which have elapsed since the last time data was received over the data
channel. The KeepAlive timer is triggered on each reception.

24-27. The state of the USB ACM (Access Control Model) layer. Internal use.

28. The maximum receive size from the USB data channel over the ACM layer.

29. Internal use.

30. The maximum receive size from the control interrupt channel over the ACM layer.

323
 Software Diagnostics Output

## 14310 LEVEL = 10, 11

Remote NDIS channel statistics
-------------------------------
Number of times ignored command response : %%1
Number of times failed process command response : %%2
Number of times received illegal command response : %%3
Last transmit failure return code : %%4
Number of times data send queue became full : %%5
Number of times discarded pending data transmission : %%6
Number of bytes discarded pending data transmission : %%7
Number of times RNDIS channel connected : %%8
Number of times RNDIS channel got disconnected : %%9
Number of data frames transmitted : %%10
Number of data bytes transmitted : %%11
Number of data frames received : %%12
Number of data bytes received : %%13
Number of times keepalive commands succeeded : %%14
Number of times keepalive commands failed : %%15
Number of times disconnected because of keepalive : %%16
Number of times entered HALT state : %%17
Number of times disconnected because of DHCP timeout : %%18

Number of data output errors in ACM level : %%19

Number of data input errors in ACM level : %%20
Number of interrupt control input errors in ACM level : %%21
Number of times failed configure ACM device : %%22
Number of times ACM device was disconnected : %%23
Number of times ACM device was reconnected abnormally : %%24

Elapsed time since last data transmission : %%25

Last transmitted data : %%26

Elapsed time since last data reception : %%27

Last received data : %%28

1. The number of times an unsolicited command response was received from the RNDIS control channel,
and it was ignored.

2. The number of times the radio responded “failed to process command”.

3. The number of invalid responses received by the radio. Check error logger for error 5904, as a radio
fault that needs to restart the radio, or upgrade its firmware.

4. Internal use.

5. The radio port is very slow, if transmitting too many frames at once; this may denote a transmission
failure. A queue is maintained per each radio port, transmitting one frame at a time. This diagnostic
shows the number of times transmission paused when the queue became full; transmission may or may
not have failed. If this occurs, increase the ‘number of output buffers’ in the port’s advanced physical
configuration and ease the transmission rate.

6. The number of times a pending data transmission was discarded due to a transmission failure at the
USB (ACM) level. This is a result of disconnecting the USB port or powering it off and on, not to the
transmission queue being full.

7. The number of bytes that were discarded due to failed transmissions as a result of disconnecting the
USB port or powering it off and on (see the previous diagnostic.)

324
 Software Diagnostics Output

8. The number of times connected to radio via Remote NDIS (RNDIS) protocol.

9. The number of times disconnected the radio via Remote NDIS (RNDIS) protocol.

10. The number of times transmitted IP or ARP packets via this port.

11. The number of IP or ARP data bytes transmitted via this port, including payload.

12. The number of times received IP or ARP packets via this port.

13. Number of IP or ARP data bytes received via this port, including payload.

14. The number of keepalive messages which succeeded in getting a response from the radio. In order to
maintain coherency between firmware port status and the radio port status, the radio is sent keepalive
messages periodically to check that it is connected. These messages are sent to the radio only, via the
RNDIS protocol and DHCP, once the radio is connected. If no response is received after several messages
are sent, the firmware detects the radio port status as disconnected, and initiates a connection with it via
the RNDIS protocol. This behavior is controlled via the 'keepalive timeout period' in the port’s advanced
physical parameters.

15. The number of times the keepalive messages failed, as a result of HW exception, radio disconnect, or
radio being powered off and on.

16. The number of times the firmware detected radio disconnect because the keepalive at the RNDIS layer
failed.

17. The number of times the unit failed to connect with the radio although its USB connection was
detected.

18. The number of times the firmware detected radio disconnect because keepalive failed in the DHCP
protocol.

19-23. Abnormal USB states when disconnecting the radio. Usually 20, 21 and 23 will show no zero
values when disconnecting the USB port, or powering off and on the radio. The other will be zero.

24. The number of times an abnormal situation occurred, where the port was reset at the USB level.

25, 26. The last transmitted data frame (IP or ARP) and the time elapsed from that transmission.

27, 28. The last received data frame (IP or ARP) and the time elapsed from that reception.

## 14355 LEVEL = 255

Remote NDIS channel device levels information:
-----------------------------------------------
level 0 - Remote NDIS channel parameters
level 1 - Remote NDIS channel status
level 10 - Get & reset remote NDIS channel statistics
level 11 - Get remote NDIS channel statistics
level 255 - This level

This lists all diagnostics provided for the LINxRND device at all its supported levels.

325
 Software Diagnostics Output

PORTMNG

## 14400 LEVEL = 0
Ports information
------------------------------
Maximum number of ports %%1
Current number of ports %%2
Support Disable port %%3

Index Name Type Build # Status Image

----- ---- ---- ------- ----------
%% %% %% %% %%
%% %% %% %% %%
%% %% %% %% %%
%% %% %% %% %%
%% %% %% %% %%
%% %% %% %% %%
%% %% %% %% %%
%% %% %% %% %%

1. The maximum number of ports for this CPU model.

2. The actual number of defined ports.

3. Does the firmware allow to disable and enable ports?

For each port – (Internal use)

Index The port index.

Name The port name.

Type The port type.

Build # The port build number.

Status Image 1- User request to enable port, or 0 - User request to disable port.

326
 Software Diagnostics Output

SECLOG

## 14000 LEVEL = 0
Security log record size :%%
Security log max number of records in log :%%
Security log input records queue (msg_q) size :%%
Security log max number of additional text buffers :%%
Security log severity flag threshold level :%%
Security log is filtering on? :%%
Security log filtering expiration time :%%
Security log filtering list size :%%
Security log filter events after X occurrences :%%

Security log parameters.

## 14001 LEVEL = 1
Security log file size :%%
Security log number of records in file :%%
Security log number of messages in input records queue (msg Q):%%
Security log number of events filtered out :%%
Security log number of severe records in ladder queue :%%

Security log general information.

## 14002 LEVEL = 255

Security log diagnostics menu:
------------------------------
Level 0 - Security log parameters
Level 1 - Security log general information
Level 2 - Security log user severity substitutions
Level 255 - This list

This lists all diagnostics provided for the SECLOG device at all its supported levels.

## 14003 LEVEL = 2
String ID Severity
--------- --------
%1 %2

If a secure logger severity file was downloaded to the STS to change default security event severities, this
lists the severity substitutions.

1. The String ID of the security event from C:\STS<version>\Prg\securelog.txt file.

2. The new severity set in the .sls file for that security event.

327
 Software Diagnostics Output

SECKEYS

## 14050 LEVEL = 0
Key type Num of keys Key num Last key expired?

For each encryption key type, the number of keys, the key number and whether the last key has expired.

## 14051 LEVEL = 1
Key type |Expiration date |Gracetime|Tx Gracetime|Enc. type|Enc. Package|
---------------------------------------------------------------------------------

Information on the current key for each encryption key type.

## 14062 LEVEL = 255

Keys diagnostics menu:
----------------------
Level 0 - Number of keys for each encryption type
Level 1 - Current key info for each encryption type
Level 10/11 - Error and counters
Level 255 - Diagnostics information

This lists all diagnostics provided for the SECKEYS device at all its supported levels.

SECPRVD

## 14100 LEVEL = 0
Security provider measured values
--------------------
Temperature (deg C) :%%
VI (x100) :%%
VO (x100) :%%
Vbat (x100) :%%
Seconds count (startup) :%%

Measured values from the internal security provider.

## 14101 LEVEL = 1
Security provider controls
-------------

Internal register controls.

328
 Software Diagnostics Output

## 14102 LEVEL = 2
Security provider registers
--------------

Internal registers.

## 14103 LEVEL = 3
Security provider serial number
---------------------------

Internal register serial number.

## 14104 LEVEL = 4
Security provider initilization status
----------------------------------
Init status : %%
Connected? : %%
init tumper occured or simulated? : %%
Init tamper value : %%

Status of initialization of internal security provider.

## 14105 LEVEL = 255

Security provider diagnsotics menu:
-------------------------------
Level 0 - Provider measured values
Level 1 - Provider control registers (Secured version only)
Level 2 - Provider serial number
Level 4 - Provider initialization status
Level 255- This list

This lists all diagnostics provided for the SECPRVD device at all its supported levels.

SECPOL

## 14150 LEVEL = 0
Is security policy active? : %%

The status of the security policy. Can be one of: 0 (inactive/No) or 1 (active/Yes).

## 14151 LEVEL = 1
Security policy xml file
--------------------------

The security policy xml file.

329
 Software Diagnostics Output

## 14152 LEVEL = 12
Security policy security logger parameters
------------------------------------------
Record size : %%
Maximum # events : %%
Max # of text buff : %%
Input records queue size : %%
high severity trigger level : %%
Task stack size : %%
Is filtering on ? : %%
Start filter after x occurrences : %%
Filtering list size : %%
Filter expiration time : %%
Verbose logging mode : %%

Security log parameters as set in the security policy.

## 14153 LEVEL = 13
Security policy encryption parameters:

Count key_type status max duration max # keys Nack on fail

----- -------- ------ ------------ ---------- ------------

## 14154 LEVEL = 14
Security policy users authentication parameters
-----------------------------------------------
Is users authentication active? : %%
Is authentication server? : %%
M2M type (0:common, 1: unique) : %%
Credentials cache timeout : %%
Permissions cache size : %%
# of fail attempts before lock : %%
# attempts before switch to next server : %%
Accounts lockout period : %%
Min password hash length sent for server : %%
Broadcast upon new users file? : %%
Failed server check alive interval : %%
Max password duration : %%
Max # of records in user cache : %%
timeout to declare server fail : %%
Unlock user and expiration check period : %%
Pre expiration password notification time: %%
Authentication Request Q size : %%
Session password len : %%
MiniSess password len : %%
FrameSeq password len : %%

330
 Software Diagnostics Output

## 14155 LEVEL = 15
Security policy files encryption parameters
--------------------------------------------
Is enabled : %%
Key size : %%
IV size : %%
Encryption type : %%
Encryption Package: %%

## 14156 LEVEL = 16
Security policy MDLC legacy sites, self test & whitelisting parameters
-----------------------------------------------------------------------
Version : %%
MDLC legacy sites support ? : %%
Self test enabled ? : %%
Whitelist enabled ? : %%

## 14157 LEVEL = 17
No policy information exist.

## 14158
Security policy Message Life Time parameters
--------------------------------------------
Version : %%
Is enabled ? : %%
Message Life Time Window [seconds]? : %%

## 14160 LEVEL = 255

Security policy diagnostics menu:
---------------------------------
Level 0 - Security policy status
Level 1 - Security policy XML
Level 12 - Security policy security logger parameters
Level 13 - Security policy encryption parameters
Level 14 - Security policy users authentication parameters
Level 15 - Security policy file encryption parameters
Level 16 - Security policy MDLC legacy sites, self test & white listing
parameters
Level 17 - Security policy 'Message Life Time' parameters
Level 255- This list

This lists all diagnostics provided for the SECPOL device at all its supported levels.

331
 Software Diagnostics Output

ENCRYP

## 14450 LEVEL = 10, 11

Encryption type|enc errors|enc successes|dec errors|dec successes|memory
allocation errors
------------------------------------------------------------------------------
--------------

## 14451 LEVEL = 255

Level 10/11 - Errors counters
Level 255 - Diagnostics information

This lists all diagnostics provided for the ENCRYP device at all its supported levels.

AUTCORE

## 14500 LEVEL = 0
UID | Access denied | Access granted
--------------------------------------------

## 14501 LEVEL = 1
Users file
-----------

## 14504 LEVEL = 10, 11

Authentication semaphore fails :%%

## 14505 LEVEL = 255

Users authorization diagnostics menu:
-------------------------------------
Level 0 - users access & authentication information
Level 1 - users file
Level 10 - counters reset
Level 11 - counters
Level 255- This list

This lists all diagnostics provided for the AUTCORE device at all its supported levels.

332
 Software Diagnostics Output

## 1

AUTHSRV

## 15000 LEVEL = 0
User id Role Time to expire

The list of users and roles in the RTU cache which have recently been authenticated by the authentication
server.

User id The unique user ID.

Role The assigned role of the user.

Time to expire The number of seconds until the user’s record in cache expires. After the user’s
record expires in cache, the user is authenticated by the authentication server.

## 15001 LEVEL = 1
Role Permission vector (cache)

The list of roles and permissions in the RTU cache which have recently been authenticated by the
authentication server.

Role The role ID, where role ID is defined as:

0 – Administrator
1 – A machine-to-machine role
2 – Technician role
3 – Viewer role
4 – User role.

Permission vector The permissions associated with the role.

## 15002 LEVEL = 2
Site_id Link_id Status Tm_to_comm Tries Retries

The list of authentication servers.

Role The role name as defined in the security policy.

## 15003 LEVEL = 3
Activity table total entries :%%
Activity table free entries :%%

333
 Software Diagnostics Output

## 15010 LEVEL = 10, 11

Authentication semaphore fails : %%
Authentication activity table entry found not in use: %%
Authentication response sequence errors : %%
Authentication response crc errors : %%

## 15020 LEVEL = 255

Level 0 - users and roles in cache
Level 1 - roles and permission vectors in cache
Level 2 - Authentication servers, status & peformance info
Level 3 - Activity table info
Level 10 - counters reset
Level 11 - general info
Level 255- This list

This lists all diagnostics provided for the AUTHSRV device at all its supported levels.

SECMNGR

## 15500 LEVEL = 0
Security manager, features status.
----------------------------------
Are all policy requirements fulfilled? : %%
Policy exist? : %%
Security provider exit? : %%
Security logger exist? : %%
MDLC users authentication active? : %%
Firmware includes crypto support? : %%
MDLC encryption status active? : %%
RTU white listing active? : %%
Message Lifetime active? : %%

Status of the Security manager and policy features.

## 15520 LEVEL = 255

Level 0 - Security manager, features status.
Level 255 - Diagnostics information

This lists all diagnostics provided for the SECMNGR.

334
 Software Diagnostics Output

WHITELS

## 16000 LEVEL = 0
Whitelisting approved files:

The list of whitelisted approved files.

## 16001 LEVEL = 1
Whitelisting suspected files:

The list of suspicious files which were not approved by whitelisting mechanism.

## 16020 LEVEL = 255

White listing diagnostics menu:
-------------------------------
Level 0 - Approved files list
Level 1 - Suspected files list
Level 255 - This list

This lists all diagnostics provided for the WHITELS device at all its supported levels.

SELFTST

## 16030 LEVEL = 0
Security Self-Test registered devices list:
===========================================

Device name | Device key | Time interval (seconds)

The list of registered devices in the RTU which undergo self test.

Device name The name of the S/W device undergoing self test (i.e. SECLOG, WHITELS,
SECCHP, ENCRYP, SECKEYS, AUTCORE.)

Device key The key of the S/W device undergoing self test.

Time interval How often the test is run (in seconds).

335
 Software Diagnostics Output

## 16031 LEVEL 10, 11

Security Self-Test results:
===========================

Device |Time until |Number| Max run | Time of | Results

name | next test | of | time | last test |
| (seconds) | fails| (ms) | |
------------------------------------------------------------------------

Device name The name of the S/W device undergoing self test (i.e. SECLOG, SECKEYS
SECPRVD, SECPOL, ENCRYP, AUTCORE, AUTHSRV, SECMNGR,
WHITELS.

Time until next test (seconds) The number of seconds until the next test.

Number of fails The number of failed tests.

Max run time (ms) The maximum run time of the test, in milliseconds.

Time of last test The date and time of the most recent test.

Results The result of the most recent test.

## 16036 LEVEL = 255

Security Self-Test diagnostics menu:
------------------------------------
Level 0 - Registered devices list
Level 10 - Get & clear statistics
Level 11 - Get statistics
Level 255 - This list

This lists all diagnostics provided for the SELFTST device at all its supported levels.

DBBKUP

## 16070 LEVEL = 0
Ladder's backup table number: %%1
Number of backup blocks: %%2
Ladder's backup table number of cols: %%3
Ladder's backup table number of rows: %%4
Back up table first column pointer: %%5
Back up table num columns pointer: %%6
Back up table first row pointer: %%7
Back up table num rows pointer: %%8
Back up table interval pointer: %%9
Back up table interval preset pointer: %%10
Back up table last store result pointer: %%11
Back up table last restore result pointer: %%12

1. The table number of the ‘BlocksToBackUp’ database user table.

336
 Software Diagnostics Output

2. The number of defined backup blocks to be processed by the backup mechanism.

3. The number of columns in 'BlocksToBackUp' table.

4. The number of rows in 'BlocksToBackUp' table.

5-12. Internal use only.

## 16071 LEVEL = 1
Max number of messages in Q: %%
Back up files list pointer: %%
Back up list pointer: %%
Back up msg Q pointer: %%
Back up last backed up block header pointer: %%
Back up last backed up block data pointer: %%
Back up tables to backup pointer: %%
Back up blocks data pointer: %%

This diagnostic is for internal use.

## 16072 LEVEL = 2
Tbl Rows Cols Fcol ExCols Frow ExRows Interval Preset Valid Srslt Rrslt DataP DataS
--- ---- ---- ---- ------ ---- ------ -------- ------ ----- ----- ----- ----- ------

For all defined blocks:

Tbl The table number of the database table specified for the block.

Rows The actual number of rows in the <Tbl> table.

Cols The actual number of columns in this <Tbl> table.

Fcol The first column to backup in the <Tbl> table.

ExCols The other columns, after the first column, to backup.

Frow The first row to backup in this <Tbl> table.

ExRows The other rows, after the first row, to backup.

Interval The amount of time, in seconds, until the next automatic store operation.

Preset The duration between automatic store operation in minutes.

Valid All block identifiers are valid? YES/NO

Srslt The result of the last store operation for this block.
Options: Never/Ok/PrepareErr/2FlashErr/MemErr/Invalid/StoreErr

Rrslt The result of the last restore operation for this block.
Options: Never/Ok/CompareErr/2TableErr/Invalid/NoStore/MemErr/RestoreErr

337
 Software Diagnostics Output

DataP Internal use only.

DataS Internal use only.

## 16073 LEVEL = 3
Backup current processed item:
- nodeInList: %%
- block: %%
- operation type: %%
- process status: %%

This diagnostic is for internal use.

## 16074 LEVEL = 4
Backup erase flags:
All blocks erased on control: %%1
All blocks erased on user's request: %%2

1. There was no match between the stored blocks in the flash and the current 'BlocksToBackup' table; all
blocks were erased. YES/NO

2. All backup blocks were removed from the flash by the ladder application. YES/NO

## 16075 LEVEL = 5
Last restored block header:
Version: %%
Revision: %%
Header length: %%
Data Length: %%
Table: %%
1st Column: %%
#Columns: %%
1st Row: %%
#Rows: %%
Column1 Type: %%
Column2 Type: %%
Column3 Type: %%
Column4 Type: %%
Column5 Type: %%
Column6 Type: %%
Column7 Type: %%
Column8 Type: %%

This diagnostic is for internal use.

338
 Software Diagnostics Output

## 16076 LEVEL = 6
Flash backup blocks after reboot/application download:
======================================================

This diagnostic specifies all backup blocks which were found in the flash, on system startup, prior to
system run-time.

To view the blocks currently stored in the flash, use the diagnostics for device=MFFS level=0 where the
blocks are named BFilei (i=block number).

LEVEL = 10
Reset 'Run-time block is different than defined block' indication

The error for a mismatch between a certain block's identifiers used for backup and the block's identifiers
in the ladder's backup table is produced only once. To get this error again, use this level.

Level 10 is also used to reset the ‘Backup queue is full’ indication. When the backup queue gets full, this
indication is set and one error message is written to the error logger. The indication remains set until the
queue is no longer full or the user performs level 10. When the backup queue gets full again, this
indication is set again and again one error message is written to the error logger.

## 16077 LEVEL = 255

Level 0 - back up table info.
Level 1 - device's pointers
Level 2 - blocks info.
Level 3 - back up processed operation
Level 4 - back up erase flags
Level 5 - last restored block header
Level 6 - flash backup blocks
Level 10 - Reset 'Run-time block is different than defined block' indication
Level 255 - This list

This lists all diagnostics provided for the DBBKUP device at all its supported levels.

339
 Software Diagnostics Output

MODBUS (ACE100)

##16100 LEVEL = 0
MODBUS FEP Config Params and Creation Data:
===========================================
Is MODBUS FEP serial? : %%1
Is MODBUS FEP serial 485? : %%2
Serial MODBUS FEP device file : %%3
Serial MODBUS FEP baud rate : %%4
Serial MODBUS FEP parity : %%5
Serial MODBUS FEP number of data bits : %%6
Serial MODBUS FEP number of stop bits : %%7
Serial MODBUS FEP modbus slave id : %%8

TCP MODBUS FEP IP address : %%9

TCP MODBUS FEP IP port number : %%10
TCP MODBUS FEP number of IP connections : %%11

Is MODBUS FEP in debug mode? : %%12

MODBUS FEP modbus module address (ctx) : %%13

MODBUS FEP modbus mapping DB address (mb_mapping) : %%14

MODBUS FEP unit id list address : %%15

MODBUS FEP unit id list allocation length : %%16
MODBUS FEP unit id list actual length : %%17

1-8. Serial port configuration parameters, relevant when the MODBUS SLAVE is on a serial port.

9-11. IP port configuration parameters, relevant when the MODBUS SLAVE is on an IP port.

12-17. Internal use only.

##16101 LEVEL = 1
MODBUS FEP READ COILS statistics:
=================================
Num of READ COILS requests : %%
Num of single READ COILS requests : %%
Num of single DO READ COILS requests : %%
Num of OK single DO READ COILS requests : %%
Num of FAIL single DO READ COILS requests : %%
Num of multiple READ COILS requests : %%
Num of multiple DO READ COILS requests : %%
Num of OK multiple DO READ COILS requests : %%
Num of FAIL multiple DO READ COILS requests : %%
Num of NOK multiple DO READ COILS requests : %%
Num of Addr Err NOK multiple DO READ COILS requests : %%
Num of Addr Err NOK READ COILS requests : %%
Num of NOK READ COILS requests : %%

Internal use only.

340
 Software Diagnostics Output

##16102 LEVEL = 2
MODBUS FEP READ DISCRETE INPUTS statistics:
===========================================
Num of READ DISCRETE INPUTS requests : %%
Num of single READ DISCRETE INPUTS requests : %%
Num of OK single READ DISCRETE INPUTS requests : %%
Num of FAIL single READ DISCRETE INPUTS requests : %%
Num of multiple READ DISCRETE INPUTS requests : %%
Num of OK multiple READ DISCRETE INPUTS requests : %%
Num of FAIL multiple READ DISCRETE INPUTS requests : %%
Num of NOK multiple READ DISCRETE INPUTS requests : %%
Num of Addr Err NOK multiple READ DISCRETE INPUTS requests : %%
Num of DO BI READ DISCRETE INPUTS requests : %%
Num of single DO BI READ DISCRETE INPUTS requests : %%
Num of OK single DO BI READ DISCRETE INPUTS requests : %%
Num of FAIL single DO BI READ DISCRETE INPUTS requests : %%
Num of multiple DO BI READ DISCRETE INPUTS requests : %%
Num of OK multiple DO BI READ DISCRETE INPUTS requests : %%
Num of FAIL multiple DO BI READ DISCRETE INPUTS requests : %%
Num of NOK multiple DO BI READ DISCRETE INPUTS requests : %%
Num of Addr Err NOK multiple DO BI READ DISCRETE INPUTS requests : %%

Internal use only.

##16103 LEVEL = 3
MODBUS FEP READ HOLDING REGISTERS statistics:
=============================================
Num of READ HOLDING REGISTERS requests : %%
Num of single READ HOLDING REGISTERS requests : %%
Num of OK single READ HOLDING REGISTERS requests : %%
Num of FAIL single READ HOLDING REGISTERS requests : %%
Num of multiple READ HOLDING REGISTERS requests : %%
Num of OK multiple READ HOLDING REGISTERS requests : %%
Num of FAIL multiple READ HOLDING REGISTERS requests : %%
Num of NOK multiple READ HOLDING REGISTERS requests : %%
Num of Addr Err NOK multiple READ HOLDING REGISTERS requests : %%
Num of single AO READ HOLDING REGISTERS requests : %%
Num of OK single AO READ HOLDING REGISTERS requests : %%
Num of FAIL single AO READ HOLDING REGISTERS requests : %%
Num of multiple AO READ HOLDING REGISTERS requests : %%
Num of OK multiple AO READ HOLDING REGISTERS requests : %%
Num of FAIL multiple AO READ HOLDING REGISTERS requests : %%
Num of NOK multiple AO READ HOLDING REGISTERS requests : %%
Num of Addr Err NOK multiple AO READ HOLDING REGISTERS requests : %%
Num of Addr Err NOK READ HOLDING REGISTERS requests : %%

Internal use only.

341
 Software Diagnostics Output

##16104 LEVEL = 4
MODBUS FEP READ INPUT REGISTERS statistics:
===========================================
Num of READ INPUT REGISTERS requests : %%
Num of single READ INPUT REGISTERS requests : %%
Num of OK single READ INPUT REGISTERS requests : %%
Num of FAIL single READ INPUT REGISTERS requests : %%
Num of multiple READ INPUT REGISTERS requests : %%
Num of OK multiple READ INPUT REGISTERS requests : %%
Num of FAIL multiple READ INPUT REGISTERS requests : %%
Num of NOK multiple READ INPUT REGISTERS requests : %%
Num of single SYS VAL READ INPUT REGISTERS requests : %%
Num of OK single SYS VAL READ INPUT REGISTERS requests : %%
Num of FAIL single SYS VAL READ INPUT REGISTERS requests : %%
Num of multiple SYS VAL READ INPUT REGISTERS requests : %%
Num of OK multiple SYS VAL READ INPUT REGISTERS requests : %%
Num of FAIL multiple SYS VAL READ INPUT REGISTERS requests : %%
Num of NOK multiple SYS VAL READ INPUT REGISTERS requests : %%
Num of single COM STT READ INPUT REGISTERS requests : %%
Num of OK single COM STT READ INPUT REGISTERS requests : %%
Num of FAIL single COM STT READ INPUT REGISTERS requests : %%
Num of U_ID Err NOK single COM STT READ INPUT REGISTERS requests : %%
Num of multiple COM STT READ INPUT REGISTERS requests : %%
Num of OK multiple COM STT READ INPUT REGISTERS requests : %%
Num of FAIL multiple COM STT READ INPUT REGISTERS requests : %%
Num of NOK multiple COM STT READ INPUT REGISTERS requests : %%
Num of Addr Err NOK multiple READ INPUT REGISTERS requests : %%

Internal use only.

##16105 LEVEL = 5
MODBUS FEP WRITE SINGLE COIL statistics:
========================================
Num of single WRITE COIL requests : %%
Num of single DO WRITE COIL requests : %%
Num of OK single DO WRITE COIL requests : %%
Num of FAIL single DO WRITE COIL requests : %%
Num of Addr Err FAIL single WRITE COIL requests : %%
Num of Data Err FAIL single WRITE COIL requests : %%

Internal use only.

##16106 LEVEL = 6
MODBUS FEP WRITE SINGLE REGISTER statistics:
============================================
Num of single WRITE REGISTER requests : %%
Num of OK single WRITE REGISTER requests : %%
Num of FAIL single WRITE REGISTER requests : %%
Num of OK single AO WRITE REGISTER requests : %%
Num of FAIL single AO WRITE REGISTER requests : %%
Num of Addr Err FAIL single WRITE REGISTER requests : %%

Internal use only.

342
 Software Diagnostics Output

##16107 LEVEL = 7
MODBUS FEP WRITE MULTIPLE COILS statistics:
===========================================
Num of multiple WRITE COILS requests : %%
Num of multiple DO WRITE COILS requests : %%
Num of OK multiple DO WRITE COILS requests : %%
Num of FAIL multiple DO WRITE COILS requests : %%
Num of Addr Err FAIL multiple WRITE COILS requests : %%

Internal use only.

##16108 LEVEL = 8
MODBUS FEP WRITE MULTIPLE REGISTERS statistics:
===============================================
Num of multiple WRITE REGISTERS requests : %%
Num of OK multiple WRITE REGISTERS requests : %%
Num of FAIL multiple WRITE REGISTERS requests : %%
Num of OK multiple AO WRITE REGISTERS requests : %%
Num of FAIL multiple AO WRITE REGISTERS requests : %%
Num of Addr Err FAIL multiple AO WRITE REGISTERS requests : %%
Num of Addr Err FAIL multiple WRITE REGISTERS requests : %%

Internal use only.

##16109 LEVEL = 9
MODBUS FEP READ WRITE REGISTERS statistics:
===========================================
Num of READ WRITE REGISTERS requests : %%
Num of OK READ WRITE REGISTERS requests : %%
Num of FAIL READ WRITE REGISTERS requests : %%
Num of NOK READ WRITE REGISTERS requests : %%
Num of Addr Err NOK READ WRITE REGISTERS requests : %%

Internal use only.

##16110 LEVEL = 10
MODBUS FEP Get & reset statistics:
==================================
Num of MODBUS requests : %%
Num of MODBUS replies : %%
Num of OK MODBUS requests : %%
Num of OK READ MODBUS requests : %%
Num of READ MODBUS requests : %%
Num of NOK MODBUS requests : %%
Num of NOK READ MODBUS requests : %%
Num of ID not found NOK MODBUS requests : %%
Num of FAIL MODBUS requests : %%
Num of FAIL READ MODBUS requests : %%
Num of WRITE MODBUS requests : %%
Num of OK WRITE MODBUS requests : %%
Num of FAIL WRITE MODBUS requests : %%

Internal use only.

343
 Software Diagnostics Output

##16111 LEVEL = 11
MODBUS FEP Get statistics:
==========================
Num of MODBUS requests : %%
Num of MODBUS replies : %%
Num of OK MODBUS requests : %%
Num of OK READ MODBUS requests : %%
Num of READ MODBUS requests : %%
Num of NOK MODBUS requests : %%
Num of NOK READ MODBUS requests : %%
Num of ID not found NOK MODBUS requests : %%
Num of FAIL MODBUS requests : %%
Num of FAIL READ MODBUS requests : %%
Num of WRITE MODBUS requests : %%
Num of OK WRITE MODBUS requests : %%
Num of FAIL WRITE MODBUS requests : %%

Internal use only.

##16112 LEVEL = 12
MODBUS FEP Get last command details:
====================================
Size in Bytes of last received command : %%1
MODBUS slave ID of last received command : %%2
Requested data items of last received command : %%3
MODBUS function code of last received command : %%4
MODBUS start address of last received command : %%5

Last READ Calls for Multiple Items

----------------------------------
Num in DB of DO COILS : %%
Num requested of DO COILS : %%
Num in DB of DISCRETE INPUTS : %%
Num requested of DISCRETE INPUTS : %%
Num in DB of HOLDING REGISTERS : %%
Num requested of HOLDING REGISTERS : %%
Num in DB of AO HOLDING REGISTERS : %%
Num requested of AO HOLDING REGISTERS : %%
Num in DB of INPUT REGISTERS : %%
Num requested of INPUT REGISTERS : %%

Internal use only.

##16113 LEVEL = 13
MODBUS FEP Get unit id list items:
==================================

modbus address unit ID

-------------- -------
%% %%

Internal use only.

344
 Software Diagnostics Output

##16117 LEVEL = 255

MODBUS FEP Diagnostic levels information:
=========================================
Level 0 - MODBUS FEP Configuration parameters
Level 1 - MODBUS FEP READ COILS statistics
Level 2 - MODBUS FEP READ DISCRETE INPUTS statistics
Level 3 - MODBUS FEP READ HOLDING REGISTERS statistics
Level 4 - MODBUS FEP READ INPUT REGISTERS statistics
Level 5 - MODBUS FEP WRITE SINGLE COIL statistics
Level 6 - MODBUS FEP WRITE SINGLE REGISTER statistics
Level 7 - MODBUS FEP WRITE MULTIPLE COILS statistics
Level 8 - MODBUS FEP WRITE MULTIPLE REGISTERS statistics
Level 9 - MODBUS FEP WRITE AND READ REGISTERS statistics
Level 10 - Get & reset statistics
Level 11 - Get statistics
Level 12 - MODBUS FEP Get last command details
Level 13 - MODBUS FEP Get unit id list items
Level 255 - This list

This lists all diagnostics provided for the MODBUS SLAVE device at all its supported levels.

345
 Software Diagnostics Output

RTU (ACE1000)
Same diagnostic levels in FEP and RTU. The device names are different: FEP/RTU.

FEP - Diagnostic for FEP all RTUs

RTU-1_10 - Diagnostic for FEP first RTUs group
RTU-11_20 - Diagnostic for FEP first RTUs group
...
RTU-241_250 - Diagnostic for FEP last RTUs group

##16200 LEVEL = 0
MONSRV - Monitor application information
======================================================
Application type: %%
Package: %%
Number of RTUs: %%
Time interval between periodic
polling cycles (Minutes): %%
Time interval between units
in each periodic polling cycle (Seconds): %%
Wait for answer response timeout (Seconds): %%
Wait for registration timeout (Seconds): %%
Number of transmission retries: %%
Interval between transmission retries (Seconds): %%
Number Of SIGUP via Deploy (Only in FEP): %%
Number Of communication driver restart (MDLC): %%
Communication driver is up (MDLC): %%
Application type - FEP or RTU
Package - Package version
Time interval between periodic polling cycles - User Configuration
Time interval between units in each - User Configuration
periodic polling cycle
Wait for answer response timeout - User Configuration
Wait for registration timeout - User Configuration
Number of transmission retries - User Configuration
Interval between transmission retries - User Configuration
Number Of SIGUP via Deploy - Number of deployments
Number Of communication driver restart - Comunication driver reinit
Communication driver is up - Comunication driver status

346
 Software Diagnostics Output

##16201 LEVEL = 1
MONSRV Communication Configuration
======================================================
RTU| IO type | Site | Site | Link | Site | Site | Link |
ID | | Index| ID | ID | Index| ID | ID |
| | 1 | 1 | 1 | 2 | 2 | 2 |

- IO type - IO modules combination

- Site Index 1 - Primary MDLC Site index in site table
- Site ID 1 - Primary MDLC Site ID
- Link ID 1 - Primary MDLC Link ID

- Site Index 2 - Redundent MDLC site index in site table

- Site ID 2 - Redundent MDLC site ID
- Link ID 2 - Primary MDLC Link ID

##16202 LEVEL = 2
MONSRV Registration & Health Check
======================================================
RTU| Reg | Reg | Reg | Health check | Health check
ID | Retries | Short (Sec)| Long (Sec)| Period (Sec) | Elapsed (Sec)

Reg Version - Registration version

Reg Size - Protocol frame size
Reg Short - Registration short period (User Configuration)
Reg Long - Registration long period (User Configuration)

##16203 LEVEL = 3
MONSRV Connection Information
======================================================
RTU|Connection| Number of | Connection | Reconnect
ID |Status | Reconnect | State | Reason

Connection status - Connection status - Connected \ Disconnected

Number of reconnect - Number of reconnections
Connection state - Internal

##16204 LEVEL = 4
MONSRV Time tags
======================================================

This level displays time tag for events.

When using a group device it also chronologically displays the status for
processes such as Polling, Syncronization, and Connectivity.

347
 Software Diagnostics Output

##16205 LEVEL = 5
MONSRV Polling
======================================================
Last ID : %% Cycle : %% Each : %% Elapsed : %%
======================================================
RTU| Manual| Periodic| Actual| Last
ID | Poll | Poll | Poll | Poll

Manual Poll - Number of manual poll requests

Periodic Poll - Number of manual periodic poll requests
Manual Poll - Number of performed poll requests
Last Poll - Last poll information

##16206 LEVEL = 6
MONSRV Controller
==============================================================================
RTU | Number of | Number of | Number of | Tables | Tables
ID | Tables COS | Tables Set| Tables Get | Signature Low | Signature High

Internal use only.

##16207 LEVEL = 7
MONSRV Communication
======================================================
Number of observers : %%
Unmanaged Site tried to communicate : %%

Internal use only.

##16208 LEVEL = 8
MONSRV Statistics
==========================================================================
RTU | Number of | Number | Number of Sync | Number of | Number of | Clear COS | Clear COS | Clear COS
ID | Disconnect | of Sync | Failures | Polling | Updates Sent| In Poll | In Sync | When Full

Number of Disconnect - Number of Disconnections

Number of Sync - Number of Syncronizations
Number of Sync failures - Number of Syncronization failures
Number of Polling - Number of Polling Processes
Number of Update Sent - Number of Update Sent to peers (Can be aggrigated)
Clear COS in Poll - Number of Change of states cleared while Polling
Clear COS in Sync - Number of Change of states cleared while
Syncronization
Clear COS in Full - Number of state changes cleared while to many
COS

348
 Software Diagnostics Output

##16209 LEVEL = 255

MONSRV Diagnostic levels information:
======================================================
Level 0 - Monitor Application Information
Level 1 - Communication Configuration
Level 2 - Registration & Health Check
Level 3 - Connection Information
Level 4 - Time Tags
Level 5 - Polling
Level 6 - Controller
Level 7 - Communication
Level 10 - Statistics - Clear after reading.
Level 11 - Statistics

Level 255 – This list

This lists all diagnostics provided for the RTU device at all its supported levels.

DNP3 Master

##16500
dnpmstr Level 0 - General Master configuration parameters:
DNP Master ID: %%
The DNP address of the master device.
Number of Slaves: %%
The total number of slave devices.
Net type: %%
Network type: IP or RS-232.

Failed remote units Integrity polling interval (seconds): %%

The time between periodic Integrity Polls of slaves that are in ‘communication fail’ status, in seconds.
Communication OK remote units Integrity polling interval (seconds): %%
The time between periodic Integrity Polls of slaves that are in ‘communication OK’ status, in seconds.
Fail remote units class polling interval (seconds): %%
The time between periodic Class Polls of slaves that are in ‘communication fail’ status, in seconds. The
Class Polls will request for all the checked classes below.
Communication OK remote units class polling interval (seconds): %%
The time between periodic Class Polls of slaves that are in ‘communication OK’ status, in seconds. The
Class Polls will request for all the checked classes below.
Need to periodic poll Class 0: %%
Should class 0 be polled in the periodic Class Polls.
Need to periodic poll Class 1: %%
Should class 1 be polled in the periodic Class Polls.
Need to periodic poll Class 2: %%
Should class 2 be polled in the periodic Class Polls.

349
 Software Diagnostics Output

Need to periodic poll Class 3: %%

Should class 3 be polled in the periodic Class Polls.

Log Level: %%
The level of diagnostic information logged to the internal logger file, in hexadecimal.

##16501
dnpmstr Level 1 - Master configuration parameters per slave, applicable only
if network type is IP. Note that some diagnostics are not relevant for all the
IP modes:
IP Network slaves:
-----------------
Slave|
Inx |
The sequential index of the slave device, starts from 0.
Slave |
ID |
The DNP address of the slave device.
NE |
ID |
The Network Element (NE) ID of the slave device.
IP |
Port |
The port number of the device to transmit to or connect with.
Dual |
Port |
The port number of the device to transmit to or connect with.

Note: This parameter is applicable only for Dual end point mode.
Dest UDP |
Port |
The port number of the device to transmit to or connect with.

Note: This parameter is applicable only for UDP only mode.

Local UDP |
Port |
Local port for sending and receiving UDP datagrams on. The port can be a number from 3 to 65535.

Note: This parameter is applicable for all IP modes except of the TCP Only mode.
IP |
Address |
The IP address of the slave device to connect or transmit.
Keep.A |
Interval |
The time interval in milliseconds to check if a device is connected by sending it Get Link Status requests.
This method is recommended by the DNP standard for checking device connection status.

350
 Software Diagnostics Output

Connect |
Timeout |
Specifies two parameters, in seconds:

- Absolute response timeout to any request generated to the slave device. This value is the maximum
amount of time the master device will wait for the final response to a request. This time starts as soon as
the request is put into the transmit queue.

The timeout period is per fragment, not per request. It should be large enough to allow the slave to
response.

-Number of seconds to wait for TCP connect to succeed or fail

Note: The second parameter is applicable for all IP modes except of the UDP Only mode.
Validate |
UDP Address|
Whether or not to validate source address of received UDP datagram.

Note: This parameter is applicable for all IP modes except of the TCP Only mode.
Enable |
Unsol |
Enable unsolicited events upon the slave device startup or the master device startup.
Auto Poll
Events
Issue Event poll with classes 1, 2, and 3 when class 1, 2, or 3 IIN bit is set

##16502
dnpmstr Level 1 - Master communication configuration parameters, applicable only if network type
is RS-232. The user should have selected the appropriate flow, parity, data bits, and stop bits combination
in the DNP master configuration, where the rest parameters setting is derived from the RS-232 port
configuration.
RS232 Network:
--------------
Port Name: %%
Baudrate: %%
Flow: %%
Parity: %%
# Stop Bits: %%
# Data Bits: %%
Close Char: %%

##16503
dnpmstr Level 2 - Slaves communication current status
Slaves communication status:
----------------------------
Slave|
Inx |
The sequential index of the slave device, starts from 0.
Slave |
ID |
The DNP address of the slave device.

351
 Software Diagnostics Output

NE |
ID |
The Network Element (NE) ID of the slave device.
Comm |
Status |
Current communication status with the slave: 1 for communication OK, 0 for communication failure.

Note: In RS-232, the communication status is updated only after response / missing responses.

##16504
dnpmstr Level 3 - Slaves configuration IOs
Slaves IO's:
-----------
Slave|
Inx |
The sequential index of the slave device, starts from 0.
Slave |
ID |
The DNP address of the slave device.
NE |
ID |
The Network Element (NE) ID of the slave device.
Num of |
DI's |
Number of Binary Input points of the slave device.
Number of |
DO's |
Number of Binary Output points of the slave device.
Number of |
AI's |
Number of Analog Input points of the slave device, including the Analog Input (16-bit) points, the
Analog Input (32-bit) points, and the Analog Input (Floating-point) points.
Number of |
AO's |
Number of Analog Output points of the slave device , including the Analog Output (16-bit) points, the
Analog Output (32-bit) points, and the Analog Output (Floating-point) points.
Number of |
Counters |
Number of Counters points of the slave device, including the Counters (16-bit) and the Counters (32-bit).
Number of |
Frozen Counters |
Number of Frozen Counters points of the slave device, , including the Frozen Counters (16-bit) and the
Frozen Counters (32-bit).

352
 Software Diagnostics Output

##16509
dnpmstr Levels 20/21 - Slaves statistics
Level 20 and 21 display the same statistics information, where level 20 clears the statistics afterwards.
Slave
Index
The sequential index of the slave device, starts from 0.
CHNL
ERROR
Number of times that an error occurred in the channel, on this slave. The next statistics lists the errors
types.

Note that dnpmstr Levels 10/11 show all the channel errors, were this statistic shows only the channel
errors that applicable to this slave.
CHNL
Mask
A mask (in hexadecimal) that lists types of the errors that were counted in the last statistics.

dnpmstr Level 22 gives more details on these errors.

ON
LINE
Number of times that the slave was marked as ON-LINE.
OFF
LINE
Number of times that the slave was marked as OFF-LINE.
ERROR
Number of times that an error occurred on this slave.
FRAGMENT
SENT
Number of the transmitted fragments.
FRAGMENT
RECEIVED
Number of the received fragments.
REQUEST
TIMEOUT
Number of the times that a request sent by a master has timed out before receiving the response.
REQUEST
FAILED
Number of the times that a request sent by a master received a failure response back from the this slave.

##16510
dnpmstr Levels 10/11 - Channel statistics.
Level 10 and 11 display the same statistics information, where level 10 clears the statistics afterwards.

353
 Software Diagnostics Output

In RS-232, there is only one channel.

In IP, there is a channel per slave; the channel’s index is the same as the slave’s index.
Channel
Index
The sequential index of the Channel, starts from 0.
CHNL
ERROR
Number of times that an error occurred in the channel. The next statistics lists the errors types.
CHNL
Mask
A mask (in hexadecimal) that lists types of the errors that were counted in the last statistics.

dnpmstr Level 12 gives more details on these errors.

OPEN
Number of times that the channel was successfully opened
CLOSED
Number of times that the channel was closed
FRAME
SENT
Number of the transmitted frames.
FRAME
RECEIVED
Number of the received frames.
FRAGMENT
SENT
Number of the transmitted fragments.
FRAGMENT
RECEIVED
Number of the received fragments.

354
 Software Diagnostics Output

##16511
dnpmstr Levels 255 – List of the dnpmstr diagnostics levels.
DNP3 Master info:
Level 0 - Master Parameters
Level 1 - Slaves Net Parameters
Level 2 - Slaves Communication Status
Level 3 - Slaves IOs
Level 10 - Statistics per channel - view and clear
Level 11 - Statistics per channel - view
Level 12 - Statistics per channel - 'CHNL Mask' decoding
Level 20 - Statistics per slave - view and clear
Level 21 - Statistics per slave - view
Level 22 - Statistics per slave - 'CHNL Mask' decoding
Level 255 - This list

DNP3 Slave

##16600
dnpslv Level 0 - General Slave configuration parameters:
Communication Status: %%
Current communication status with the slave: 1 for communication OK, 0 for communication failure.
DNP Slave ID: %%
The DNP address of the slave device.
DNP Master ID: %%
The DNP address of the master device.
Network type: %%
Network type: IP or RS-232.
Unsolicited responses are allowed: %%

This parameters determines whether unsolicited responses are allowed. If it is set to ‘Disable’ no
unsolicited responses will be generated and requests to enable or disable unsolicited responses will fail.
Log Level: %%
The level of diagnostic information logged to the internal logger file, in hexadecimal.

Obj01 Default Variation: %%

Binary Input (object 1) default variation, to which the slave should respond on a request with variation 0.
Obj02 Default Variation: %%
Binary Input Events (object 2) default variation, to which the slave should respond on a request with
variation 0.
Obj10 Default Variation: %%
Binary Output (object 10) default variation, to which the slave should respond on a request with variation
0.

355
 Software Diagnostics Output

Obj11 Default Variation: %%

Binary Output Events (object 11) default variation, to which the slave should respond on a request with
variation 0.
Obj20 Default Variation: %%
Counters (object 20) default variation, to which the slave should respond on a request with variation 0.
Obj21 Default Variation: %%
Frozen Counters (object 21) default variation, to which the slave should respond on a request with
variation 0.
Obj22 Default Variation: %%
Counters Events (object 22) default variation, to which the slave should respond on a request with
variation 0.
Obj23 Default Variation: %%
Frozen Counters Events (object 23) default variation, to which the slave should respond on a request with
variation 0.
Obj30 Default Variation: %%
Analog Input (object 30) default variation, to which the slave should respond on a request with variation
0.
Obj32 Default Variation: %%
(250=per point w time, 251=per point w/o time)
Analog Input Events (object 32) default variation, to which the slave should respond on a request with
variation 0.
Obj40 Default Variation: %%
Analog Output (object 40) default variation, to which the slave should respond on a request with variation
0.
Obj42 Default Variation: %%
(250=per point w time, 251=per point w/o time)
Analog Output Events (object 42) default variation, to which the slave should respond on a request with
variation 0.
Are DOs reported in Class0?: %%
Specify if the response to a Class 0 Read request contains the Binary Inputs static data (Object 1) or not: 1
means enabled, 0 means disabled.
Are Dos reported in Class0?: %%
Specify if the response to a Class 0 Read request contains the Binary Outputs static data (Object 10) or
not: 1 means enabled, 0 means disabled.
Are AIs reported in Class0?: %%
Specify if the response to a Class 0 Read request contains the Analog Inputs static data (Object 30) or not:
1 means enabled, 0 means disabled.
Are AOs reported in Class0?: %%
Specify if the response to a Class 0 Read request contains the Analog Outputs static data (Object 40) or
not: 1 means enabled, 0 means disabled.
Are Counters reported in Class0?: %%
Specify if the response to a Class 0 Read request contains the Counters static data (Object 20) or not: 1
means enabled, 0 means disabled.

356
 Software Diagnostics Output

Are Frozen Counters reported in Class0?: %%

Specify if the response to a Class 0 Read request contains the Frozen Counters static data (Object 21) or
not: 1 means enabled, 0 means disabled.

Generate events upon Freeze/Freeze and Clear? : %%

This parameters determines if Counters events and Frozen Counters Events will be generated upon
receiving a Freeze or Freeze and clear request.

##16601
dnpslv Level 1 - Slave communication configuration parameters, applicable only
if network type is IP. Note that some diagnostics are not relevant for all the
IP modes:

IP Network:
----------
Master IP Address: %%
The IP address of the master device.
Local UDP Port: %%
Local port for sending and receiving UDP datagram messages on. It should be configured to match the
UDP port that the master uses to send datagram messages to. The port can be a number from 3 to 65535.
TCP Connect timeout: %% seconds
Number of seconds to wait for TCP connect to succeed or fail.
keep Alive Interval: %% ms
The time interval in milliseconds to check if a device is connected by sending it Get Link Status requests.
This method is recommended by the DNP standard for checking device connection status.
Local TCP Port: %%
Local TCP port for listening. In Dual end point mode, the listening is done on this port and the connection
requests are sent to ‘Destination TCP port’ port. The port can be a number from 3 to 65535.

Applicable only for the TCP Client mode and Dual end point mode.
Destination UDP Port: %%
Destination UDP port to send responses to. The port can be a number from 3 to 65535.

Applicable only for the UDP Only mode.

Destination TCP Port: %%
Destination TCP port that the slave should send the connect request to when it initiates the connection. In
Dual end point mode, the listening is done on the ‘Local TCP port’ port and the connection requests are
sent to this port when needed.

Applicable only for the Dual end point mode.

Validate UDP Address: %%
Whether or not to validate source address of received UDP datagram.
Destination UDP port for initial Unsolicited response: %%
Destination UDP port to send the initial Unsolicited Null response to. The port can be a number from 3 to
65535. After receiving a UDP request from master, ‘Destination UDP port’ will be used for all responses.

357
 Software Diagnostics Output

Applicable only for the UDP Only mode.

##16602
dnpslv Level 1 - Slave communication configuration parameters, applicable only
if network type is RS-232. The user should have selected the appropriate flow,
parity, data bits, and stop bits combination in the DNP slave configuration,
where the rest parameters setting is derived from the RS-232 port
configuration.
RS232 Network:
--------------
Port Name: %%
Baudrate: %%
Flow: %%
Parity: %%
# Stop Bits: %%
# Data Bits: %%
Close Char: %%

##16603
dnpslv Level 2 – IO Configuration
IO's:
-----
Number of DIs: %%
Number of all the Binary Input points, including physical Binary Inputs and virtual Binary Input points.
Number of DOs: %%
Number of all the Binary Output points, including physical Binary Outputs and virtual Binary Outputs
points.
Number of AIs: %%
Number of all the Binary Input points, including physical Analog Inputs and virtual Analog Input points.
Number of AOs: %%
Number of all the Binary Output points, including physical Analog Output and virtual Analog Output
points.
Number of Counters: %%
Number of all the Counters, including physical DI Counters and virtual Counters points.
Number of Frozen : %%
Number of all the Frozen Counters. All of them are virtual Frozen Counters points.

##16607
Dnpslv Levels 30/31 - Events statistics.
Level 30 and 31 display the same statistics information, where level 30 clears the statistics afterwards.

358
 Software Diagnostics Output

Events statistics:
------------------
# events in DIs Event buffer: %%
Number of events currently store in the Binary Input events buffer, and were not reported yet, or were
reported but were not confirmed yet.

Note that after an event is reported and confirm, it is removed from the events buffer.
# events in DOs Event buffer: %%
Number of events currently store in the Binary Output events buffer, and were not reported yet, or were
reported but were not confirmed yet.

Note that after an event is reported and confirm, it is removed from the events buffer.
# events in Counters Event buffer: %%
Number of events currently store in the Counter events buffer, and were not reported yet, or were reported
but were not confirmed yet.

Note that after an event is reported and confirm, it is removed from the events buffer.
# events in Frozen Event buffer: %%
Number of events currently store in the Frozen Counter events buffer, and were not reported yet, or were
reported but were not confirmed yet.

Note that after an event is reported and confirm, it is removed from the events buffer.
# events in AIs Event buffer: %%
Number of events currently store in the Analog Input events buffer, and were not reported yet, or were
reported but were not confirmed yet.

Note that after an event is reported and confirm, it is removed from the events buffer.
# events in AOs Event buffer: %%
Number of events currently store in the Analog Output events buffer, and were not reported yet, or were
reported but were not confirmed yet.

Note that after an event is reported and confirm, it is removed from the events buffer.

# attempts to generate DIs Event: %%

Number of attempts to add a Binary Input event into the Binary Input events buffer.

Events might be added from physical IOs, from C application, or from IEC.
# attempts to generate DOs Event: %%
Number of attempts to add a Binary Output event into the Binary Output events buffer.

Events might be added from physical IOs, from C application, or from IEC.
# attempts to generate Counters Event: %%
Number of attempts to add a Counter event into the Counter events buffer.

Events might be added from physical IOs, from C application, from IEC or if the Generate Counters and
Frozen Counters events upon Freeze/Freeze and Clear commands parameter is enabled.

359
 Software Diagnostics Output

# attempts to generate Frozen Event: %%

Number of attempts to add a Frozen Counter event into the Frozen Counter events buffer. Events might
be added from physical IOs, from C application, or if the Generate Counters and Frozen Counters events
upon Freeze/Freeze and Clear commands parameter is enabled.
# attempts to generate AIs Event: %%
Number of attempts to add an Analog Input event into the Analog Input events buffer. Events might be
added from physical IOs, from C application, or from IEC.
# attempts to generate AOs Event: %%
Number of attempts to add an Analog Output event into the Analog Output events buffer.

Events might be added from physical IOs, from C application, or from IEC.

# successful attempts to add any event: %%

Number of successful attempts to add any event to any events buffer.
# No class failure attempts to add any event: %%
Number of failed attempts to add any event to any events buffer. Those events were not stored since no
class was defined for those points.
# No memory failure attempts to add any event: %%
Number of failed attempts to add any event to any events buffer. Those events were not stored since there
was not enough memory to store them.
# Null entry failure attempts to add any event: %%
Number of failed attempts to add any event to any events buffer. Those events were not stored because of
NULL pointer.
# 'Other' failure attempts to add any event: %%
Number of failed attempts to add any event to any events buffer. The reason for not storing those events
is not overflow or any of the reasons described above.

# Event buffer Overflow failure attempts to add any event:%%

Number of failed attempts to add any event to any events buffer. Those events were not stored because of
event buffer overflow. The next statistics depict this information per data type:
# Event buffer Overflow failure attempts to add DI event:%%
Number of failed attempts to add a Binary Output event to the Binary Output events buffer. Those events
were not stored because of Binary Output event buffer overflow.
# Event buffer Overflow failure attempts to add DO event:%%
Number of failed attempts to add a Binary Input event to the Binary Input events buffer. Those events
were not stored because of Binary Input event buffer overflow.
# Event buffer Overflow failure attempts to add Counter event:%%
Number of failed attempts to add a Counter event to the Counter events buffer. Those events were not
stored because of Counter event buffer overflow.
# Event buffer Overflow failure attempts to add Frozen event:%%
Number of failed attempts to add a Frozen Counter event to the Frozen Counter events buffer. Those
events were not stored because of Frozen Counter event buffer overflow.

360
 Software Diagnostics Output

# Event buffer Overflow failure attempts to add AI event:%%

Number of failed attempts to add an Analog Input event to the Analog Input events buffer. Those events
were not stored because of Analog Input event buffer overflow.
# Event buffer Overflow failure attempts to add AO event:%%
Number of failed attempts to add an Analog Output event to the Analog Output events buffer. Those
events were not stored because of Analog Output event buffer overflow.
# Event buffer Overflow failure attempts to add 'other' event:%%
Number of failed attempts to add an event with to any events buffer, where the event data type is not one
of the data types depicted above. Those events were not stored because of event buffer overflow.

# Sent events: %%
Number of events that were reported to the master, in responses or in unsolicited responses.
# Confirmed events: %%
Number of events that were reported to the master, in responses or in unsolicited responses, and were
confirmed by the master.

##16608
dnpslv Level 12 – List of the errors in the ‘CHNL Mask’ statistics displayed
in levels 10/11.
'CHNL Mask' errors:
-------------------

##16609
dnpslv Levels 20/21 – Slave session statistics.
Level 20 and 21 display the same statistics information, where level 20 clears the statistics afterwards.
CHNL
ERROR
Not applicable.
CHNL
Mask
Not applicable.
ON
LINE
Number of times that the slave was marked as ON-LINE.
OFF
LINE
Number of times that the slave was marked as OFF-LINE.
ERROR
Number of times that an error occurred on this slave.
FRAGMENT
SENT
Number of the transmitted fragments.

361
 Software Diagnostics Output

FRAGMENT
RECEIVED
Number of the received fragments.
REQUEST
TIMEOUT
Number of the times that a fragment sent by a slave has timed out before receiving the response.
REQUEST
FAILED
Not applicable.

##16610
dnpslv Levels 10/11 – Channel statistics.
Level 10 and 11 display the same statistics information, where level 10 clears the statistics afterwards.
CHNL
ERROR
Number of times that an error occurred in the channel. The next statistics lists the errors types.
CHNL
Mask
A mask (in hexadecimal) that lists types of the errors that were counted in the last statistics.

dnpslv Level 12 gives more details on these errors.

OPEN
Number of times that the channel was successfully opened
CLOSED
Number of times that the channel was closed
FRAME
SENT
Number of the transmitted frames.
FRAME
RECEIVED
Number of the received frames.
FRAGMENT
SENT
Number of the transmitted fragments.
FRAGMENT
RECEIVED
Number of the received fragments.

362
 Software Diagnostics Output

##16611
dnpslv Levels 255 – List of the dnpslv diagnostics levels.
DNP3 Slave info:
Level 0 - General parameters.
Level 1 - Network parameters.
Level 2 - IOs
Level 10 - Channel statistics - view and clear
Level 11 - Channel statistics - view
Level 12 - Channel statistics - 'CHNL Mask' decoding
Level 20 - Session statistics - view and clear
Level 21 - Session statistics - view
Level 30 - Events statistics - view and clear
Level 31 - Events statistics - view
Level 255- This list

## 16700 LEVEL = 0
MODBUS Master General Params:
---------------------------
Nr. of slaves: %%
The number of slave configured for this Master
Port Type: %%
The port type - RS485/RS232/IP
Polling Mode: %%
The Polling mode that configured for this Master MANUAL/AUTO
MANUAL - will poll slave upon request
AUTO - will poll all slaves periodicity according to configured timing
Log Level: %%
Advanced parameter - for programmer uses.

## 16701 LEVEL = 1
MODBUS Master Addresses:
---------------------------
Input Register 16Bit Start Address: %%
Input Register 32Bit Start Address: %%
Input Register Float Start Address: %%

Holding Registers 16Bit Start Address: %%

Holding Registers 32Bit Start Address: %%
Holding Registers Float Start Address: %%

Discrete Input Start Address: %%

Coils Start Address: %%
The Addresses configured for all slaves.

## 16702 LEVEL = 2
MODBUS Master Communication:
---------------------------
Polling Interval(ms): %%
When Master configured to Auto polling mode - this is the polling interval

363
 Software Diagnostics Output

Max Failures Before Comm Fail: %%

Response Timeout(ms): %%
Configured Timeout interval used to wait for a response from slave
Bytes Timeout(ms): %%
Configured Timeout interval between two consecutive bytes of the same message received from slave.
Bytes Order(ms): %%
The communication byte order configured - ABCD/CDAB

## 16703 LEVEL = 3
MODBUS Master IO's:
--------------------------
SLV Nr of Nr of Nr of 16 Nr of 32 Nr of F. Nr of 16 Nr of 32 Nr of F.
ADDR DIs DOs bit AIs bit AIs AIs bit AOs bit AOs AOs

The quantities of elements that were configured for each slave.

## 16706 LEVEL = 4
Nr. of Miliseconds before next poll = %%

Last poll start %%

Timestamp of the last slaves polling started
Last poll end %%
Timestamp of the last slaves polling ended

The above parameters are relevant for AUTO poll mode only.

## 16704 LEVEL = 10 to 19
Comm Info of Slave # %%
---------------------
Comm. Status %%
The current communication status with the slave (OK/FAIL/FAIL - TRYING TO CONNECT...)
Comm. Fail Counter %%
The number of time failed to receive answer from slave.
Max Failures Before comm Fail %%
Configured number of time failed to receive answer from slave before declaring comm. fail
Read DO's %% %%
The error got from Modbus driver when failed to read DO + the # of failures reading DO.

The same for the following:

364
 Software Diagnostics Output

Read DI's %% %%
Read 16 Ai's %% %%
Read 32 Ai's %% %%
Read float Ai's %% %%
Read 16 Ao's %% %%
Read 32 Ao's %% %%
Read float Ao's %% %%
Set Do's %%
The error got from Modbus driver when last failed to set DO request.
Same for the following:
Set 16 Ao's %%
Set 32 Ao's %%
Set float Ao's %%

## 16705 LEVEL = 10 to 19
Slave not exists %%
When trying to retrieve data of a non-configured slave ID.

##16707 LEVEL = 255

MODBUS MASTER info:
Level 0 - General Params.
Level 1 - Addresses.
Level 2 - Communication Params.
Level 3 - IO's Params.
Level 4 - Auto Polling Mode Params.
Level 10-19 - Slaves Comm Info. level 10 for slave 1, 11 for slave 2 etc..
Level 255- This list

LTRAPPL (ACE1000)

##17100 LEVEL = 0
LTR_APPL General Information :
================================

DI polling interval : %%1

AI polling interval : %%2
Rediscovery interval : %%3
Number of net elements : %%4
Number of System Values objects : %%5
Ltr_appl version number : %%6
Other error for main board : %%7
Other error for expansion 1 : %%8
Other error for expansion 2 : %%9

1. How often the DI (pushbutton status) polling occurs.

2. How often the AI (temperature and voltage) polling occurs.

3. How often the rediscover occurs.

4. The number of net elements.

5. The number of system values objects.

365
 Software Diagnostics Output

6. The module version number.

7-9. Internal use only.

##17101 LEVEL = 1
LTR_APPL Failures Counters Information :
==========================================

The Number of Failures to change Error Led Status :%%1

The Number of Failures to open a connection to the main K10 :%%2
The Number of Failures to open a connection to the expansion 1 K10 :%%3
The Number of Failures to open a connection to the expansion 2 K10 :%%4
The Number of Failures to get module information in main :%%5
The Number of Failures to get module information in expansion 1 :%%6
The Number of Failures to get module information in expansion 2 :%%7
The Number of Failures to get module configuration in main :%%8
The Number of Failures to get module configuration in expansion 1 :%%9
The Number of Failures to get module configuration in expansion 2 :%%10

Displays the status of failures in run-time.

##17102 LEVEL = 2
LTR_APPL Failures Counters Information - Read and Clear Counters :
===================================================================
The Number of Failures to change Error Led Status :%%
The Number of Failures to open a connection to the main K10 :%%
The Number of Failures to open a connection to the expansion 1 K10 :%%
The Number of Failures to open a connection to the expansion 2 K10 :%%
The Number of Failures to get module information in main :%%
The Number of Failures to get module information in expansion 1 :%%
The Number of Failures to get module information in expansion 2 :%%
The Number of Failures to get module configuration in main :%%
The Number of Failures to get module configuration in expansion 1 :%%
The Number of Failures to get module configuration in expansion 2 :%%

Displays the status of failures in run time – reads and clears the counters.

##17103
Displays the information on whether the unit's model initialization is completed or not.

##17150 LEVEL = 255

Level 0 - General information about ltr_appl app.
Level 1 - Failures Counters Information.
Level 2 - Failures Counters Information - Read and Clear Counters.
Level 255 - This list .

This lists all diagnostics provided for the LTRAPPL device at all its supported levels.

366
 Software Diagnostics Output

##17190 LEVEL = 0
%%

This diagnostic is provided for the FEPIO device. It includes the same information as the IO device but
for the FEP.

RTU1P (ACE1000)

##17200 LEVEL = 0
MDLC UART parameters:
---------------------
Port index : %%1
Port name : %%2
Port baud rate : %%3
Port Bits : %%4
Port flow control : %%5
Is Port 485 : %%6
Port Linux vmin : %%7
Port Linux vtime : %%8
End of tx timeout : %%9
Grant timeout : %%10
Quiet timeout : %%11
End of rx timeout : %%12
Wait resolution : %%13
Close character : %%14
UART is send 55 required? : %%15
# of retries in case of allocation fail : %%16
Interval in milliseconds between allocation fail: %%17

367
 Software Diagnostics Output

##17210 LEVEL = 10, 11

MDLC UART statistics
----------------------------
Number of frames transmitted = %%1
Number of bytes transmitted = %%2
Number of frames failed transmission = %%3
Number of bytes failed transmission = %%4
Number of frames received = %%5
Number of bytes received = %%6
Number of times failed open port = %%7
Number of times open port = %%8
Number of times warmup succeed = %%9
Number of times failed warmup = %%10
Number of times wait on tx but no pending = %%11
Number of times aborted wait tx = %%12
Number of times timeout end of tx = %%13
Number of times aborted wait rx = %%14
Number of times timeout when wait for end of tx = %%15
Number of times got timeout when wait rx quiet = %%16
Number of times aborted wait start tx = %%17
Number of times timeout wait start tx = %%18
Last error when transmit = %%19

##17211 LEVEL = 255

MDLC UART diagnostic levels:
----------------------------
Level 0 - Get parameters
Level 1 - Get status
Level 10 - Get & reset statistics
Level 11 - Get statistics

This lists all diagnostics provided for the RTU1P device at all its supported levels.

SYSTEM (ACE1000)

##17302 LEVEL = 2
IRMIPC_DIAG List of the most running tasks on the system :
===========================================================
%%

Displays system information about the running tasks.

##17303 LEVEL = 3
IRMIPC_DIAG Information about the Linux system’s memory :
==========================================================
%%

Displays system information about the memory usage.

368
 Software Diagnostics Output

##17304 LEVEL = 4
IRMIPC_DIAG Information about the available disk space on the file system :
===========================================================================
%%

Displays system information about the disk usage.

##17305 LEVEL = 5
IRMIPC_DIAG UART statistics :
=============================
%%

Displays system information about the UARTs.

##17306 LEVEL = 6
IRMIPC_DIAG Device list :
=========================
%%

Displays a list of the ACE1000 devices that are running.

##17307 LEVEL = 7

IRMIPC_DIAG System time :

==========================
%%

Displays the current time, how long the system has been running, how many users are currently logged
on, and the system load averages for the past 1, 5, and 15 minutes. System load average is the average
number of processes that are either in a runnable or uninterruptable state.

##17308 LEVEL = 8
IRMIPC_DIAG The configuration of the network interfaces :
==========================================================
%%

Displays the status of the currently active interfaces.

##17309 LEVEL = 9
IRMIPC_DIAG Network Information :
==================================
%%

Displays the network connections, routing tables, interface statistics, masquerade connections, and
multicast memberships.

369
 Software Diagnostics Output

##17311 LEVEL = 11
IRMIPC_DIAG site view :
===============================

This diagnostic displays the site field view of the unit, including the file system version, FailSafe system
version, FailSafe Kernel system version, installed bundles, installed packages, unit up time, product type,
unit type, site number, system address, configuration version, ports, I/Os, and baseline version.

For DEVICE=SYSTEM, LEVEL=1:

Features:
IEC61131 feature is enabled in RTU
or:
Features:
IEC61131 feature is NOT enabled in RTU

##17312 LEVEL = 12
IRMIPC_DIAG Running C processes :
==============================
%%

Displays process information of the running C Toolkit processes.

##17313 LEVEL = 13
IRMIPC_DIAG C process to diag device mapping :
================================================
%%

Displays the device name mapping to the running C Toolkit processes.

##17349 LEVEL = 254

IRMIPC_DIAG Copyright Notice:
=============================
Copyright © 2014 Motorola Solutions, Inc. All Rights Reserved.
Portions Copyright © 1990-2005 Info-ZIP. All rights reserved.
For legal information see: /opt/ltr/bin/legal_notices.txt

Displays the copyright notice.

370
 Software Diagnostics Output

##17350 LEVEL = 255

IRMIPC_DIAG Diagnostic levels information:
==========================================
Level 2 - IRMIPC_DIAG List of the most running tasks on the system
Level 3 - IRMIPC_DIAG Information about the Linux system’s memory
Level 4 - IRMIPC_DIAG Information about the available disk space on the file
system
Level 5 - IRMIPC_DIAG UART statistics
Level 6 - IRMIPC_DIAG Device list
Level 7 - IRMIPC_DIAG System time
Level 8 - IRMIPC_DIAG configuration of the network interface
Level 9 - IRMIPC_DIAG Network Information
Level 11 - IRMIPC_DIAG Site's field view
Level 12 - IRMIPC_DIAG Running C processes
Level 13 - IRMIPC_DIAG C process to diag device mapping
Level 254 - Copyright Notice
Level 255 - This list

This lists all diagnostics provided for the SYSTEM device at all its supported levels.

IRM, IRMSRV

##17400 LEVEL = 0
CPRS : Application Parameters
1 Application Name : %1
2 Tx Retry Interval [sec] : %2
3 Number of TX retries : %3
4 Number of broken connections : %4
5 Periodic keep-alive interval [sec] : %5
6 Try to connect Interval [sec] : %6
7 Protocol Window Size : %7

This shows the application parameters configured by the user.

1. Internal use

2. Interval between retries as was configured by the user in the IRM application. This parameter with TX
Number of retries, below, indicate how long it waits for connection with the peer (IRM1500 or IRM1500
Server) before declaring it as failed. Once the connection is maintained, the same applies to the timeout
waiting for acknowledgement before declaring "broken connection".

3. Number of retries.

4. Once the connection is failed (after the above retries are exhausted), this is the number of attempts to
restore the connection, before declaring the port as failed. For example if set to 3, we retry twice.

5. Optional parameter for checking the session connected with its peer. 0 means no keep-alive is sent.

6. After declaring a port as "failed" because of the above reasons, how long to wait before trying to
resume connection. If data is sent by the user or received, it will try immediately.

371
 Software Diagnostics Output

7. How many bytes can be sent before expecting acknowledgement. This does not determine the actual
amount of data being sent before expecting acknowledgement, since it is done by the MDLC driver for
smaller amounts of data.

##17401 LEVEL = 1
CPRS : Sites List
==========================================
Site Link IP Address
%% %% %%

It shows the list of peers, as configured by the user. In IRMSRV it shows the list of IRM1500 units that
were configured, and in IRM shows the IRM1500 Server.

In the list it shows the Site ID, Link ID, and IP address as was configured by the user. Note that the IP
address may not reflect the actual IP address being used because it is handled by the MDLC driver. It
only shows what the user configured.

##17402 LEVEL = 2 (for IRM1500 Server)

CPRS : Port parameters
==============================================
Site Number Idle Time End Character Name
%1 %2 %3 %4 %5

For the IRM1500 server, these parameters are listed for the local port configured by the user.

1. IRM site ID associated with this port.

2. TCP port number in the PC.

3. Idle time in milliseconds- how much time to wait when receive from local port before transmitting.

4. End character (for future use).

5. Description of port as specified by the user.

##17402 LEVEL = 2 (for IRM1500)

CPRS : Port parameters
Site ID : %1
Communication To Domestic RTU : %2
Serial Device name : %3
Flow Control : %4
Port Settings : %5
Data Speed : %6
Reception Idle Time : %7
Reception End Character : %8
Port Description : %9

372
 Software Diagnostics Output

For the IRM1500, these parameters are listed for the serial port parameters configured by the user:

1. IRM1500 Server site ID.

2. Type of communication RS232 or RS485.

3. Internal use - port name for linux.

4. Flow control of RS232 port.

5. Port setting for RS232 port: 8 bits, Np (No partity) 1s 1 stop bits.

6. Speed of port.

7. Idle time in milliseconds- how much time to wait when receive from local port before transmitting.

8. End character (for future use).

9. Description of port as specified by the user.

##17403 LEVEL = 10

##17404 LEVEL = 11

##17405 LEVEL = 12
TCP Port %1 Site ID %2
Local: %3 Remote: %4
|---------------|--------------- --|
| OK | Q | Lost | OK | Q | Lost |
|----------------------------------|
TX --> Bytes |0 |0 |0 |0 |0 |0 | %5
TX --> Frames|0 |0 |- |0 |- |0 | %6
RX <-- Bytes |0 |0 |0 |0 |0 |0 | %7
RX <-- Frames|0 |0 |- |0 |- |0 | %8
|----------------------------------|
Last Time Received Data (Local ): %9
Last Time Transmit OK (Local ): %10
Last Time Transmit Fail (Local ): %11
Last Time Received Data (Remote ): %12
Last Time Transmit OK (Remote ): %13
Last Time Received Ack (Remote ): %14
Last Time Transmit Fail (Remote ): %15
TX Full Count (Remote ): %16

These levels shows communication (TX/RX) statistics for the IRM and IRMSRV devices.

1. Port name (e.g. TCP port 14050 for IRM server, or /dev/ttyO1 for IRM).

2. Name of peer site ID via MDLC, e.g. Site 25.

3. State of local connection, e.g. Opened or closed.

4. State of remote connection with peer, e.g. connected or failed.

373
 Software Diagnostics Output

Initiated/Succeed/Accepted - the number of times a connection was established or a port was

opened.

Broken - the number of times a connection was disconnected.

Failed - the number of times a connection failed.

Ignored - the number of times received a connection request from a peer but ignored because port is
closed.

5. This row shows the number of bytes transmitted and acknowledged over MDLC to the peer.

OK = succeeded and got acknowledged,

Q = pending for transmission OR transmitted and waiting for ack,
Lost = were not transmitted, or transmitted but not acknowledged

6. This row shows the number of frames transmitted and acknowledged over MDLC to the peer. OK, Q,
and Lost the same as in 5.

7. This row shows the number of bytes received from MDLC and routed to the local port.

OK = succeeded - received from MDLC and routed to local port,

Q = pending data received from MDLC and in process of being routed to local port,
Lost = received but failed route to local port.

8. This row shows the number of frames received from MDLC and routed to the local port. OK, Q, and
Lost the same as in 7.

9. Time stamp of last time received data from the local port.

10. Time stamp of last time transmitted data to the local port.

11. Time stamp of last time failed transmission to the local port.

12. Time stamp of last time received over MDLC from the peer.

13. Time stamp of last time transmission succeeded over MDLC to the peer.

14. Time stamp of last time transmission succeeded and was acknowledged over MDLC from the peer.

15. Time stamp of last time transmission that failed because of full queue (up to 32 messages may be
pended before getting acknowledged), or because did not get acknowledged, or because transmission
failed.

16. Number of times transmission failed because of full queue (up to 32 messages may be pended for
transmission before getting acknowledged).

Where:

Level 10 shows and clears connection statistics for all ports (sites).

Level 11 shows and does not clear connection statistics for all ports (sites).

Level 12 shows and clears connection statistics for opened ports only.

374
 Software Diagnostics Output

##17406 LEVEL = 20

##17407 LEVEL = 21

##17408 LEVEL = 22
|----------------------------------------------------------------|
| Status | Initiated |Succeed |Accepted |Broken |Failed |Ignored | %3
|----------------------------------------------------------------|
TCP Port %1 |Closed |0 |0 |0 |0 |0 |0 |
SiteId %2 |Ignored |0 |0 |0 |0 |0 |0 |
|----------------------------------------------------------------|

Last Time Accepted (Local ):

Last Time Disconnected (Local ):
Try to connect Interval (Remote):
Time Elapse Since Fail (Remote):
Last Time Connected (Remote):
Last Time Start Connect (Remote):
Last Time Connect Failed (Remote):
Last Time Disconnected (Remote):
Last Time Accepted (Remote):

These diagnostics show statistics for connection with a peer in IRM and in IRMSRV (IRM1500 server).1.
Name of local connection (e.g. TCP port 14050 for IRM server, or /dev/ttyO1 for IRM).

2. Name of peer site ID via MDLC, e.g. Site 25.

3. Statistics:

Status - status of connection, e.g. Closed, Ignored, etc.

Initiated/Succeed/Accepted - the number of times a connection was established or a port was

opened.

Broken - the number of times a connection was disconnected.

Failed - the number of times a connection failed.

Ignored - the number of times received a connection request from a peer but ignored because port is
closed.

Where:

Level 20 shows all ports and clears statistics.

Level 21 shows all ports and does not clear statistics.

Level 22 shows only connected ports and does not clear statistics.

375
 Software Diagnostics Output

##17430 LEVEL = 255

CPRS Diagnostic levels information:
==========================================
Level 0 - Application Parameters
Level 1 - Site List
Level 2 - Port parameters

Level 10 - Communication Statistics - Show & Clean.

Level 11 - Communication Statistics - Show.
Level 12 - Communication Statistics - Show Only Active.

Level 20 - Connection Statistics - Show & Clean.

Level 21 - Connection Statistics - Show.
Level 22 - Connection Statistics - Show Only Active.

Level 255 - This list

This lists all diagnostics provided for the IRM/IRMSRV device at all its supported levels.

LOGIx, MLOGIx, MINIx, FRMSQx, BRSSQx, UTIL, MDLCSRV

(ACE1000)

##17500 LEVEL = 0
MDLC Driver general parameters
==============================
Number of openned channels : %%1
Number of busy channels : %%2

Internal use only.

LOGIx, MLOGIx, MINIx, FRMSQx, BRSSQx, UTIL (MDLCSRV)

(ACE1000)

##17501 LEVEL = 1
MDLC Driver channels parameters
================================
Channel number : %%1
Channel type : %%2
State of channel : %%3
Header length (in bytes) : %%4
Header message : %%5
Data length (in bytes) : %%6
Data message : %%7
Was header received : %%8
Is socket opened : %%9
Is answer expected : %%10

Internal use only.

376
 Software Diagnostics Output

##17502 LEVEL = 2
MDLC Driver channels status
================================
Size of last transmitted/received hdr : %%1
Last transmitted/received header : %%2

Size of last transmitted/received data: %%3

Last transmitted/received data : %%4

Was last header/data buffer transmitted to client ? : %%5

Was last message transmitted to client a data buffer ? : %%6

Internal use only.

##17503 LEVEL = 3
MDLC Driver channel logger
================================
Server ID : %%
Channel ID : %%
Dyanmic key: %%

Internal use only.

LOGIx, MLOGIx, MINIx, FRMSQx, BRSSQx, UTIL, MDLCSRV

(ACE1000)

##17510 LEVEL = 10, 11

MDLC Driver general statistics
================================
Number of requests sent : %%1
Number of time got connected : %%2
Number of time got disconnected: %%3

Internal use only.

MDLCSRV (ACE1000)

##17541 LEVEL = 255

MDLC Driver levels
================================
0- MDLC Driver general parameters.
10-Read general statistics.
11-Read and Clear general statistics.
255-This list

This lists all diagnostics provided for the MDLCSRV device at all its supported levels.

377
 Software Diagnostics Output

LOGIx, MLOGIx, MINIx, FRMSQx, BRSSQx, UTIL (MDLCSRV)

(ACE1000)

##17542 LEVEL = 255

MDLC Driver channels levels
================================
0- MDLC Driver general parameters.
1- MDLC Driver channels parameters.
2- MDLC Driver channels status.
3- MDLC Driver logger.
10-Read general statistics.
11-Read and Clear general statistics.
255-This list

This lists all diagnostics provided for the LOGIx, MLOGIx, MINIx, FRMSQx, BRSSQx, UTIL devices
at all supported levels.

MDLCSRV (ACE1000)

##30000 LEVEL = 0
MDLC driver Diagnostic Level 0
==============================
Instance Id : %%1
Service name : %%2
Topic name : %%3
Number of opened channels : %%4
Number of busy channels : %%5

Internal use only.

##30001 LEVEL = 1
MDLC driver Diagnostic Level 1
==============================
Channel number : %%1
Channel type : %%2
State of channel : %%3
Header length (in bytes) : %%4
Header message : %%5
Data length (in bytes) : %%6
Data message : %%7
Was header received : %%8
Item name : %%9
Conversation handle : %%10
Is answer expected from CPU: %%11
Is dialing in progress : %%12

Internal use only.

378
 Software Diagnostics Output

##30002 LEVEL = 2
Item string handle: %% "%%"
Topic string handle: %% "%%"
Server string handle: %% "%%"

Internal use only.

##30003 LEVEL = 3
Size of last transmitted/received hdr : %%1
Last transmitted/received header : %%2

Size of last transmitted/received data: %%3

Last transmitted/received data : %%4

Was last header/data buffer transmitted to client ? : %%5

Was last message transmitted to client in a data buffer ? : %%6

Internal use only.

##30010 LEVEL = 10
How many times handled XTYP_ADVSTART : %%
How many times handled XTYP_ADVSTOP : %%
How many times handled XTYP_POKE : %%
How many times handled XTYP_REQUEST : %%
How many times handled XTYP_ADVREQ : %%
How many times handled XTYP_CONNECT : %%
How many times handled XTYP_DISCONNECT : %%
How many times got Unknown transactions : %%
Total number of transactions : %%

How many times failed get topic in XTYP_ADVSTART : %%

How many times failed get topic in XTYP_ADVSTOP : %%
How many times failed get topic in XTYP_ADVPOKE : %%
How many times failed get topic in XTYP_REQUEST : %%
How many times failed get topic in XTYP_ADVREQ : %%
How many times failed get topic in XTYP_CONNECT : %%
How many times failed open channel in XTYP_ADVSTART : %%
How many times failed get channel in XTYP_ADVSTOP : %%
How many times failed get channel in XTYP_ADVPOKE : %%
How many times failed get channel in XTYP_ADVREQ : %%
How many times failed handle request in XTYP_REQUEST : %%
How many times failed handle tranzaction in XTYP_ADVREQ: %%

Internal use only.

##30040 LEVEL =
Could not match channel handle when diagnosing MDLC driver

Internal use only.

379
Error Messages

The STS Error Logger utility enables the user to retrieval details of software and hardware error
malfunctions from the RTU. For details on retrieving error logger messages, see the Operation chapter of
the ACE3600 STS User Guide.

Error Logger Messages

This section lists the errors and warnings which may be generated by the Error Logger. The messages are
listed as they appear on the screen, with %% signs in the text to represent alphanumeric values provided
by the Error Logger.

The description which follows the error messages, provides one or more possible causes for the error and
possible solutions.

Note: The VxWorks operating system may produce messages of severity ‘warning’ which include the
following text: “Message polled from standard output/standard error/messages logger: %%”
These messages generally do not represent serious problems. However, the product group may be
consulted.

Error #20: Invalid Box in TX Queue – Device: %%

This message appears due to a fault memory overwrite in the Tx Queue in the
link layer. The 'Device' is the name of the link layer (referring to the port).
Consult product group.

Error #21: Invalid Box in Positive ACK Queue – Device: %%

This message appears due to a fault memory overwrite in the ACK Queue in the
link layer. The 'Device' is the name of the link layer (referring to the port).
Consult product group.

Error #22: Invalid Box in Busy/Setcall Queue – Device: %%

This message appears due to a fault memory overwrite in the Busy/Setcall
Queue in the link layer. The 'Device' is the name of the link layer (referring to
the port). Consult product group.

Error #23: Can Not Get a New ACK Buffer, increase # of ACK Buffers – Device %%
For each link layer, 8 acknowledge buffers are defined. If all those buffers are
full and the link intends to prepare another acknowledgment for transmission,
this message is displayed and there will be a retry on behalf of the transmitting
side. Usually, this may occur in Nodes. Consult product group.

380
 Error Messages

Error #24: ACk Buffer (Formatted) is too Small – Device: %%

For system software developers only. Consult product group.

Error #25: Can Not Get a New ACK Buffer, ACKs Buffer was corrupted – Device: %%
This message appears due to a memory overwrite in the heap of the
acknowledgments in the link layer.

Error #26: Ignore frame(s) with unexpected source site ID (absolute id %%/ logical id %%),
since source site ID is equal to self site ID
This generally indicates that there are two or more sites with the same site ID.

Error #28: Ignore frame(s) with unexpected source site ID (absolute id %%/ logical id %%),
since source site ID is SETCALL
This generally indicates that there is a site ID equal to the System Address.

Error #29: Unexpected link layer error: %%.

Contact the product group.

Error #40: Illegal Operation Code For Configuration

Illegal operation code during configuration download.

Error #41: Low Byte Error When Using Flash Memory

This message appears during configuration download, while downloading the
flash. There is a problem in the flash.

Error #42: High Byte Error When Using Flash Memory

This message appears during configuration download, while downloading the
flash. There is a problem in the flash.

Error #43: Given address is not start address of flash memory

This message appears during configuration download, while downloading the
flash. This message indicates a software error in the Download program.

Error #44: Wrong number of bytes in flash memory

This message appears during configuration download, while downloading the
flash.

Error #45: Error After Send Struct

Communication problem during configuration download.

Error #46: Error After Get Struct

Communication problem during configuration download.

381
 Error Messages

Error #47: Control error !!

May indicate system software error. Consult product group.

Error #60: Can Not Remove Slice – Device: %% , Size: %%

This message appears when receiving a MDLC communication buffer, that
passed a CRC check, but one of the communication layers ('Device') can not
understand its contents (due to a bug or a unique case of an illegal buffer
receive). This buffer will be dumped into the heap.

Error #61: Can Not Get Slice – Device: %% , Size: %%

For system software developers only. Consult product group.

Error #62: Can Not Push Block – Device: %% , Length: %%

For system software developers only. Consult product group.

Error #80: Fixed transaction Index (%%) is Out Of Range

This message indicates that a fixed transaction that can not be found in the
transaction table was received. It is an illegal transaction.

Error #81: No Fixed transactions Table Was Assigned To Slave

A fixed transaction was received but the fixed transaction table was not
downloaded into the slave.

Error #82: Bad transaction Format

Illegal transaction. For example: 'Z' (table number) does not exist.

Error #83: Error from application routines -like fetchcom

Failure when trying to fetch data from a ladder application database table while
monitoring.

Error #84: Error in db_map level like qualifier error

Error in qualifier condition defined for ladder application database table
monitoring. Check user-defined qualifier conditions.

Error #85: Trying To Comm. After Session Was Ended

Illegal communication. The transaction ended but data still arriving. This may
occur due to differences in the data structure of master and slave.

Error #86: Transaction Length Exceeds 256 Bytes

Transaction is too big.

382
 Error Messages

Error #87: Bad transaction Flags: %%

Undefined bits are set in the flags area of the transaction.

Error #88: Data too long

Due to differences in the data structure between master and slave, spare data is
arriving.

Error #89: Data too short

Due to differences in the data structure between master and slave, only part of
the data has arrived.

Error #95: Queue in fram_seq is full

The Rev Seq queue is full and the application did not get the frames.

Error #96: Trouble in queue: %%

Illegal management of linked buffers.

Error #97: Queue in fram_seq indications is full

The application has not emptied the indications queue. Check application.

Error #98: Queue in fram_seq errors is full

The application has not emptied the errors queue. Check application.

Error #100: Trying to access illegal logical channel in transport layer

Illegal logic channel for the device.

Error #101: Illegal data in transport layer structure

Illegal data for the device.

Error #107: Queue in Burst Seq is full, frames might be lost

The application did not remove buffers from the queue or the queue wasn’t
emptied quickly enough. Frames may be lost.

Error #110: Illegal number of logical channels in transport multiplexer

The actual number of logical channels is bigger than the number defined during
the creation of the device.

Error #111: From Site : %%Link : %% can not communicate with current unit
Communication was initiated by a site which is not defined in the Site table.

383
 Error Messages

Error #112: Trouble in queue: %%

Illegal management of linked buffers.

Error #113: Illegal control byte : %%

Memory overwrite in a buffer that passed a CRC check. The buffer is dumped
into the heap.

Error #114: Illegal buffer : %%

The Transport Multiplex layer can not understand a buffer that passed a CRC
check. This buffer is dumped into the heap.

Error #115: Application Id not exists : %%

Applying to an application that does not exist in the RTU. This may occur when
using a new version of Tool Box with new features to communicate with an
older RTU that is not familiar with those new features.

Error #116: Machine code illegal : %%

Due to a bug in the Transport Multiplex layer, the 'states machine' has reached
an illegal state.

Error #117: Can't talk with master because unit was not defined as Slave !! OR flag Master
is Set but Unit was not defined as Master !!
For system software developers only. Consult product group.

Error #118: Encryption error

A frame sent by this RTU to the specified site ID and link ID was rejected due
to encryption mismatch. Check the encryption definitions.

Error #119: An illegal inbound frame was rejected.

Secured credentials in frame: %%
Frame encrypted : %%
New encryption: : %%
The inbound frame contains secured credentials and encrypted by legacy
encryption (TEA). This kind of frame is not supporte.d Consult product group.

Error #120: Can not get characters from existing buffer

May indicate system software error. Consult product group.

Error #121: Illegal compilation of SEND output

Indicates a software error in the Application Programmer. Consult product
group.

384
 Error Messages

Error #122: problem with changing port parameters !!

Runtime change in ladder of user port parameters (e.g. format: bit, parity,stop
bit) is invalid.

Error #123: ADAPTOR - RX User Queue is full

The User port receive queue is full.

Error #131 Illegal master channel -

Inbound channel ID : %%
Actual number of master channels: %%
Inbound source port ID : %%
Master's channel source port ID : %%
Inbound source site ID : %%
Master's channel source site ID : %%

Error #132 Frame sequence parse requests queue receive failure: error = %%, sent from
site id = %%, Q = %%
An illegal request to process inbound frame sequence frame sent from site ID
(site id) was retrieved from queue (Q)– unexpected size of request (error).

Error #133 Frame sequence parse requests queue send failure: error = %%, sent from site
id = %%, Q = %%
Failed (failure code = error) to add to queue (Q) a request to process inbound
frame sequence frame that came from site (site id).

Error #134 Security policy does not include Message Life Time parameters.
The message life time section in the security policy in the RTU is invalid.

Error #140: Invalid Link ID, network layer: %%, Dest Site: %%,
Dest Link: %%, Dest Port: %%
The network layer in a RTU is asked to transfer a communication buffer to the
Dest Site, Dest Link & Dest port but the specific link is not known to this RTU
(since other links are defined).

Error #141: Can not find Link ID in network configuration, network layer: %% Dest Site: %%,
Dest Link: %%, Dest Port: %%
The network layer in a RTU is asked to transfer a communication buffer to the
Dest Site, Dest Link & Dest port but there is no route defined in the network
configuration, which the communication can be transferred through.

385
 Error Messages

Error #142: Destination=Default Central, Network layer: %%, Dest Site: %%, Dest Link:
%%, Dest Port: %%
Network is trying to transfer a buffer to Default central before the last one
communicate with the transmitting site at least once.

Error #143: Fail to get a free box for distributing a default central.
Please enlarge the link TX queue size.
network layer: %%, dest link: %%
Network layer- Link is busy. Cannot distribute frame to default central.
Enlarge the TX queue size Advanced link parameter in the site configuration for
the specified link.

Error #144: Transparent Network layer !! Can not route via other Link ID network layer: %%
For system software developers only. Consult product group.

Error #145: Formatted buffer is smaller than the received frame,

network layer: %%
May indicate system software error. Consult product group.

Error #146: Fail to get a free box for distributing a setcall.

Please enlarge the link TX queue size.
dest link: %%, dest port: %%
Network layer- Link is busy. Cannot distribute setcall.
Enlarge the TX queue size Advanced link parameter in the site configuration for
the specified link.

Error #147: Mismatch between site_conf and network layer: Network direct_link_table,
while trying to reach site: %% / link %% using direct_link %%.
This error indicates mismatch between the site configuration and network
configuration files. The direct_link subsection of the network file does not
match the site configuration Links information.

Error #148: ECHO case (only available TX path is via the ‘FROM’ site).
Network layer: Network – STOCK table,
while trying to reach site: %%%% / link %%. Echo using ‘via link’: %%.
Probably mismatch between the network files at ‘from’ and ‘to’ RTUs.
The only link available for transmission is the link from which the frame was
received. The most common reason is an inconsistency in network definition
between the frame originator and this RTU.

Error #149: Could not transmit to CENTRAL/DEFAULT_CENTRAL, probably path is in fail,

Network layer: Network, desty link %%, dest site %%.
The frame to be transmitted to Central or to Default_central could not be
transmitted. Probably the link used for transmission is in fail. No alternative
path was chosen.

386
 Error Messages

Error #160: Timer service is not activated since timer is defined with 0 time units, device:
%%
The data of the timers device is corrupted. Trying to operate a timers routine
with no time units.

Error #161: # of time units passed without activating timer service is %%, device: %%
The timers task can not start its operation in a time interval which is bigger than
the time interval that was allocated for it in the device creation. This message
may indicate either a long scan time (above 500 msec) or an infinite loop in the
user application.

Error #170: Illegal data in constant cyclic buffer structure

May indicate system software error. Consult product group.

Error #171: Illegal data in variable cyclic buffer structure

May indicate system software error. Consult product group.

Error #175: Failed to process incoming 'Time&Sequence' synchronization frame.

May occur on I/O expansion module, when Time&Sequence RX fails. Consult
product group.

Error #177: Failed decode time zone %%

Cannot decode the timezone information received with the synch.
Check the timezone definition in the site configuration for the relevant sites.

Error #178: Failed encode time zone %%

Cannot encode the timezone information to transmit with the synch.
Check the timezone definition in the site configuration for the relevant sites.

Error #179: Bad daylight MM-DD-HH %% to %%

The definition of the Daylight Savings start/end dates in the ladder application
database is invalid. Check the table.

Error #180: Illegal setting of date & time:

Seconds: %% Minutes: %% Hours: %%
Day : %% Date : %% Month: %% Year: %%
The date and time settings are not correct. This message appears when the user
application updates the time and date in the Time & Date table and one or more
of the settings is incorrect.

387
 Error Messages

Error #181: Getting illegal date & time:

Seconds: %% Minutes: %% Hours: %%
Day : %% Date : %% Month: %% Year: %%
May indicate either system software error or incorrect real-time clock
component in the RTU. Consult product group.

Error #182: RTT (real time timer) is not functioning

A hardware problem with the Real Time Clock prevented reading the time
during power up. The time is reset to 1.1.80.

Error #185: RTC registers were not initialized.

The hardware Real Time Clock exists but it does not indicate a valid time.
Therefore during power up, the time is set to 1/1/1980.

Error #186: RTT (real time timer) is o.k., but nothing was written to it yet (reading it will give
junk).
The hardware Real Time Clock exists and it has a valid time, but for some
reason cannot read its time. Therefore during power up, the time is set to
1/1/1980.

Error #187: Failed to convert time inputed by user

Failed to use the time input by the user from the ladder, monitor or STS Date &
Time utility. As a result, the time was not changed. This occurs if trying to set
the time before 1.1.80. Internal use.

Error #188: Failed set time zone %% minutes

The time zone specified in the Advanced Site configuration parameters is
illegal, and therefore the time zone was not set. Time zone should be between –
720 and +720. Note that it does not include daylight saving time (and additional
1 hour.)

Error #189: Failed set auto time zone %% minutes

Failure when reading time zone from DHCP. For future use.

Error #190: Corrupted heap data base:

device : %%
pointer to start chain : %%
pointer to current chain : %%
pointer to end chain : %%
# of buffers left in heap : %%
May indicate system software problem. Consult product group.

388
 Error Messages

Error #191: Heap: buffer is allocated for too much time.

device : %%
buffer address : %%
allocated for more than %% minutes, it happened %% time(s).
May indicate system software problem. Consult product group.

Error #192: Buffer: %% is already free. Calling address is: %%

May indicate system software problem. Consult product group.

Error #200: Odd address of working area

For system software developers. Consult product group.

Error #201: Insufficient space in work area

May indicate system software problem. Consult product group.

Error #202: Corrupted device KEY

May indicate system software problem. Consult product group.

Error #203: Heap: %% is empty, device: %%

Empty heap. Consult product group.

Error #210: Corrupted Duty Cycle: %% or Gap Cycle: %%

Illegal percents (above 100% or negative) were assigned to the Duty Cycle in
the user application.

Error #212: Main process is running more than 1.2 seconds !!

The user application includes either an infinite loop or a loop that occupies the
CPU for a long time, and other tasks do not get CPU time.

Error #229: Two or more files with type %% were found during 'flash erase'
Only one file of this type should be in the Flash, however more than one file
was found when erasing the Flash.

Error #230: Bad table coordinate :%%

The 'Z' coordinate (table number) belongs to a table that does not exist in the
application, probably because of differences in the data structure between
master and slave.

Error #231: Bad row coordinate :%% in table #%%

The 'Y' coordinate (row number) does not exist in the table, probably because of
differences in the data structure between master and slave.

389
 Error Messages

Error #232: Bad column coordinate :%% in table #%%

The 'X' coordinate (column number) does not exist in the table, probably
because of differences in the data structure between master and slave.

Error #233: No COS memory space was allocated to table #%%

There is no 'COS' column defined in the table.

Error #234: NOT enough Space for Differentiators (%% Bytes). Application DISABLED.
Each application needs at least 256 bytes, which are not available, for
differentiators.

Error #235: Warning: Short USER RAM: %% Bytes

In case the free space available for application is less than 2 Kbyte, the user is
notified that the running application is limited.

Error #236: Index is out of range : %% %%

The index in the user application has reached 256 or exceeded it.

Error #237: No application in FLASH memory or Application was stopped !!

Trying to get data from some table, while the application was not downloaded
or was stopped.

Error #238: Task '%%' does NOT exist !!

For system software developers only. Consult product group.

Error #239: No Delta COS Area Was Allocated To Column #%% in Table #%%
Trying to read COS of a column that does not have COS area. Improper use of
DB_Map application.

Error #240: Invalid Time Tag List: %% OR Events list: %%

error returned from sio_set_di_cos_en(): %%
May indicate system software problem. Consult product group.

Error #245: #the 'Load' option was used to download the application, however the number
of diffrentiators were changed.
You should use the 'Reset Load' option instead and then do Download.

Error #246: Failed to perform automatic scan in for table %% column %%

Automatic scan in failed for this table/column, either because of database access
failure or I/O inputs scan failure.

390
 Error Messages

Error #247: Failed to perform automatic scan out for table %% column %%
Automatic scan out failed for this table/column, either because of database
access failure or I/O outputs scan failure.

Error #248: Failed to acquire from compilation output the RAM memory size to allocate for
ladder application
Indicates system software error. Consult product group.

Error #249: Ladder application CRCs comparison failure. Calculated CRC = %% ,

Downloaded CRC = %%
Mismatch between the system CRC and downloaded ladder application self
CRC. Try to recompile the ladder application.

Error #250: Cannot read module type at: %%

I/O module defined but physically missing.

Error #251: Module type does not match site configuration, module: %%
Incompatible module type. Configuration definition and physical module are
different.

Error #252: Module: %%, initial values are invalid.

There are no preset values in the control registers of the DO module gate array.

Error #253: Digital output module: %%, desired values in gate array are not equal to image
in memory.
The gate array data and the image in the RTU do not match.

Error #254: Digital output module: %%, actual values of relays are not equal to desired
values in gate array.
The gate array data and the image in the RTU do not match.

Error #255: I/O module: %% analog input not calibrated.

At least one of the analog input in the module is not calibrated.

Error #256: Cannot 'communicate' with module: %%

It is not possible to read data from the module; it is faulty.

Error #257: Some Failure In Module %%.

Faulty FIFO communication in the specified module.

Error #258: CLOCK fail flag in module %% is on.

The clock in the specified module is faulty.

391
 Error Messages

Error #259: I/O module: %% EE memory problem.

All the channels are calibrated, but the inner EE is problematic.

Error #260: Analog input module: %% FIFO time-out.

The Analog Input module does not respond to the RTU CPU.

Error #261: Mixed I/O module: %% analog input problem

There is a problem in the specified analog input of the Mixed I/O module.

Error #262: I/O Module: %% analog output not calibrated.

The specified analog input of the Mixed I/O module is not calibrated.

Error #263: I/O module: %% analog input calib. succeeded with borderline input.
Calibration succeeded but one of the measurements is out of range.

Error #264: DI FAIL In Module %%.

The specified module (DI or Mixed I/O) is in FAIL.

Error #265: AI FAIL In Module %%.

The AI module is in FAIL.

Error #266: Relay Check Back (CB) FAIL In Module %%.

Incompatibility between desired and actual status in DSP outputs.

Error #267: Module %%, Scale Factor or Threshold Changed From User Requested Value.
Incompatibility between desired and actual status in AO.

Error #268: Module %%, DSP Not Ready.

The AC Analyzer module does not respond due to hardware or software
problems. Consult product group.

Error #269: Module %%, DSP Reset.

The AC Analyzer module has reset itself. Hardware or software problems.
Consult product group.

Error #270: Incompatible Communication PROTOCOL on: PORT #%% CONTROL=%%

STATUS=%%
May indicate system software/hardware problem. Consult product group.

392
 Error Messages

Error #271: Uncontrollable Communication PHYSICAL on: PORT #%% CONTROL=%%

STATUS=%%
May indicate system software/hardware problem. Consult product group.

Error #272: Unoperational Communication PHYSICAL on: PORT #%% CONTROL=%%

STATUS=%%
May indicate system software/hardware problem. Consult product group.

Error #273: Unoperational PHYSICAL Internal LOOP on: PORT #%% CONTROL=%%
STATUS=%%
When checking the port (HDLC or UART), the RTU turns into a self loop
mode, sends a frame and receives it. This message is displayed if the received
frame is not equal to the one that was sent, and the port is port3.

Error #274: Unoperational PHYSICAL External LOOP on: PORT #%% CONTROL=%%
STATUS=%%
When checking the port (HDLC or UART), the RTU turns into an internal loop
mode, sends a frame and receives it. This message is displayed if the received
frame is not equal to the one that was sent, and the ports are 1 or 2.

Error #275: Unsuccessful PHYSICAL Configuration on: PORT #%% COMMAND=%%

ANSWER=%%
Internal modem does not exist or illegal parameters were downloaded to this
modem.

Error #276: Uncontrollable PHYSICAL Configuration on: PORT #%% COMMAND=%%

DATA=%%
Problem in the internal modem.

Error #280: Incompatible Communication BOARD on: PORT #%% CONTROL=%%

STATUS=%%
Piggyback on port3 is illegal.

Error #281: Uncontrollable Communication CHANNEL on: PORT #%% CONTROL=%%

STATUS=%%
Programmable RS-232 was not defined and the CTS & RTS detectors are
defected.

Error #282: Unoperational Communication CHANNEL on: PORT #%% CONTROL=%%

STATUS=%%
The port is transferred to software mode. This message is displayed if CD is not
active.

393
 Error Messages

Error #283: Unoperational CHANNEL Internal LOOP on: PORT #%% CONTROL=%%
STATUS=%%
Incompatibility between the frame that was sent and received by the internal
loop.

Error #284: Unoperational CHANNEL External LOOP on: PORT #%% CONTROL=%%
STATUS=%%
Incompatibility between the frame that was sent and received by the external
loop.

Error #285: Unsuccessful CHANNEL Configuration on: PORT #%% COMMAND=%%

ANSWER=%%
Internal modem does not exist or illegal parameters were downloaded.

Error #286: Uncontrollable CHANNEL Configuration on: PORT #%% COMMAND=%%

DATA=%%
Problem in the internal modem.

Error #287: No response from internal DPSK modem on: port #%% command=%%
data=%%
Problem in the internal modem-piggyback plug in Port Type unit for Port 3.

Error #289: Could not program the spread spectrum (aironet) radio successfully. The
readback registers value was different from the written ones.
Piggyback cannot be programmed. Switch or fix piggyback.

Error #290: A fault has occurred in the spread spectrum (aironet) radio. The system has
checked the radio registers and found that their values are different from the
expected ones. The system tried to correct the problem by reinitializing the radio
unsuccessfully. A power restart of the CPU and the radio may resolve the
problem.
Try to do a restart.

Error #291: Unsuccessful channel configuration on: port #%% command=%% answer=%%
Could not configure the modem. Either the connection does not fit or the data
speeds of the RTU and modem are not the same. Check the port configuration.

394
 Error Messages

Error #300: MTE CRASH:

Error Code : %%
Problematic Thread : %%
Problematic Device : %%
Status Register (SR) : %%
Program Counter (PC) : %%
Current Task : %%
Candidate Task : %%
May indicate system software problem. Consult product group.

Error #301: MTE WARNING: The MTE_VLD Lowest Priority Task in The System Was Not
Reached For %% Ticks. System is Either Overloaded Or Some Process is in
Infinite Loop !!!! . Maximum Allowed Time At Which The Lowest Task May Not
Activate is %% Ticks.
A task is in infinite loop. Consult product group.

Error #302: %% CRASH:

R/~W : %%
~I/N : %%
Function Code : %%
Access Address : %%
Instruction Register : %%
Status Register (SR) : %%
Program Counter (PC) : %%
Current Task : %%
Candidate Task : %%
Bus error or address error crash. May indicate system software problem. Consult
product group.

Error #303: %% CRASH:

Status Register (SR) : %%
Program Counter (PC) : %%
Current Task : %%
Candidate Task : %%
Illegal instruction crash. May indicate system software problem. Consult
product group.

Error #304: MTE: The CONTROL procedure of devices was not started, because the type of
control parameter is out of range !!
Type of requested control was : %%
The last valid control entry is : %%
Internal error. May indicate system software problem. Consult product group.

395
 Error Messages

Error #305: MTE: The MTE CONTROL procedure of devices failed !!!
Device Name : %%
Control Type : %%
Number of successive fails : %%
The control procedure of one of the devices has failed. May indicate system
software problem. Consult product group.

Error #306: System heavy load, probably due to communication attack.

It is likely that this error is caused due to communication attack via one of the
Ethernet ports. Please monitor the network traffic and if possible use the
firewall.

Error #350: Session layer: in function %% remove slice failed. Remove slice failed.
May indicate system software problem. Consult product group.

Error #351: Session layer: in function %% get slice failed. Get slice failed.
For system software developers. Consult product group.

Error #352: Session layer: in function %% allocation of formatted buffer failed. Allocation of
a buffer failed.
May indicate system software problem. Consult product group.

Error #353: Session layer: in function %% buffer in RX is kept by lower layer.

May indicate system software problem. Consult product group.

Error #354: Session layer: in function %% no more room for error buffers.
May indicate system software problem. Consult product group.

Error #355: Session layer: in function %% received not error buffer, while in tx.
May indicate system software problem. Consult product group.

Error #356: Session layer: in function %% format error. Protocol found error.
May indicate system software problem. Consult product group.

Error #357: Session layer: in function %% unable to perform abort session.

May indicate system software problem. Consult product group.

Error #358: SESSION: In Function %% Illegal Password. Session Not Opened.

Illegal password. Session was not opened.

Error #400: Presentation layer: in function %% remove slice failed. Remove slice failed.
May indicate system software problem. Consult product group.

396
 Error Messages

Error #401: Presentation layer: in function %% get slice failed. Get slice failed.
May indicate system software problem. Consult product group.

Error #402: Presentation layer: in function %% push byte in fbuf failed. Push byte failed.
May indicate system software problem. Consult product group.

Error #403: Presentation layer: in function %% pull byte from fbuf failed. Pull byte failed.
May indicate system software problem. Consult product group.

Error #404: Presentation layer: in function %% push block in fbuf failed. Push block failed.
May indicate system software problem. Consult product group.

Error #405: Presentation layer: in function %% pull block from fbuf failed. Pull block failed.
May indicate system software problem. Consult product group.

Error #406: Presentation layer: in function %% allocation of fbuf failed. Allocation problem.
Empty heap. Consult product group.

Error #407: Presentation layer: in function %% the presentation is in aborted state

May indicate system software problem. Consult product group.

Error #408: Presentation layer: in function %% the presentation is not in tx state.

May indicate system software problem. Consult product group.

Error #409: Presentation layer: in function %% the presentation is not in rx state.

May indicate system software problem. Consult product group.

Error #410: Presentation layer: in function %% the len of tx structure is out of range.
May indicate system software problem. Consult product group.

Error #411: Presentation layer: in function %% general format error. Protocol format error.
May indicate system software problem. Consult product group.

Error #412: Presentation layer: in function %% format error, compression not supported.
Format error. Compression is not supported.
May indicate system software problem. Consult product group.

Error #413: Presentation layer: in function %% format error, encryption not supported.
Encryption and compression are not supported.
May indicate system software problem. Consult product group.

397
 Error Messages

Error #414: Presentation layer: in function %% format error, control number out of range.
Protocol format error.
May indicate system software problem. Consult product group.

Error #415: Presentation layer: in function %% general synchronization error.

May indicate system software problem. Consult product group.

Error #416: Presentation layer: in function %% the rx applic, buffer size is too small.
May indicate system software problem. Consult product group.

Error #417: Presentation layer: in function %% no more rooms for error buffers.
May indicate system software problem. Consult product group.

Error #450: Stock set: the stock buffer is locked for too much time
For system software developers. Consult product group.

Error #451: Stock get: the stock buffer is locked for too much time
For system software developers. Consult product group.

Error #452: Could not create semaphore for Remote Link In Fail Table for locking. Table
size set to 0.
Could not allocate a semaphore needed to initialize the table used to handle the
network "Link In Fail Table". The table size is set to 0 and Routing using
Remote Failed Links Table feature is disabled.

Error #500: IOTEST: Invalid Option: %%

Applying to a non-existing option for I/O module testing in the RTU. This may
occur when using a new version of Tool Box with new features to communicate
with an older RTU that is not familiar with those new features.

Error #501: IOTEST: Bad Device Name %% for Service %%

Problem in getting device key & pin_table out of device name.

Error #520: Minisess: illegal box nr. %% , data problem !!!

May indicate system software problem. Consult product group.

Error #522: Authentication requests queue receive failure: error = %%, specific error = %%.
An illegal (failure code = specific error) request to process inbound minisession
frame was received – unexpected size of request (error). May indicate system
software problem. Consult product group.

398
 Error Messages

Error #523: Authentication requests queue send failure: specific error = %%, source site =
%%, destination site = %%.
This RTU (destination site) failed (failure code = error) to add to queue a
request to process inbound minisession frame that came from site (source site).
Consult product group.

Error #524: Failed to get or join minisession box no. %% (error %%).
Failed (failure code = error) to process inbound minisession frame in
minisession internal box (box no )resource. Consult product group.

Error #525: Failed to get a free element from authentication requests list (Count = %%).
There is no available minisession authentication request resource (total number
of request resources = Count ) to add to minisession frames awaiting
authentication. Increase the ‘Size of queue in receiving RTU awaiting response
from authentication server’ parameter in the policy.

Error #521: Minisess: Protocol mismatch, please reduce number of boxes.

The protocol was enlarged, with an extended number of boxes but the RTU does
NOT support the extended byte. Reduce the number of boxes in the
Minisession advanced parameter section of the site configuration.

Error #540: Time_tag rack module not exist: %%

Data was received for an I/O bit that exists in an I/O module, but not defined in
the user ROM.

Error #541: Time_tag->read %%> time_tag->write %%

May indicate system software problem. Consult product group.

Error #542: Unknown record type in Time_tag buffer.

record type is: %%.
The specified illegal record type was found in the Time Tag buffer. Software
error.

Error #560: The MC68882 Coprocessor is connected, but is not OK.

All floating point and double precision calculations are emulated by software.

Error #561: The MC68882 device data is corrupted. Software problem.

May indicate system software problem. Consult product group.

Error #562: The check validity or test of MC68882 device failed due to MTE_TSTNSET
locking. Software problem.
May indicate system software problem. Consult product group.

399
 Error Messages

Error #563: The MC68882 RAM jump table is too short !!! Software problem.
May indicate system software problem. Consult product group.

Error #564: The MC68882 Coprocessor is no more functioning.

All floating point and double precision calculations are emulated by software.

Error #565: Fatal !!!! The %% operation is not executed correctly !!!
May indicate system software problem. Consult product group.

Error #600: Unable to run %% from 2 different processes !!

Unable to run PPH from two different processes.

Error #601: The scan_discrete_in call in PPH module failed !!

May indicate system software problem. Consult product group.

Error #602: The call to prv_userrom_pph_timer from timer 10 ms is to late !!! PPH may have
lost pulses !!!!!!!!!
May indicate system software problem. Consult product group.

Error #603: The PPH structure is CORRUPTED !!! The PPH calculations may be wrong !!!
May indicate system software problem. Consult product group.

Error #604: Fatal !!! CPY Not Performed due to border problems !!!
Trying to use the CPY function with illegal parameters.

Error #605: Fatal !!! Division by 0 in rungs while performing the MODULO operation. The
result is undefined !!
Dividing by 0 in user application.

Error #606: Fatal !!! Division by 0 in rungs while performing the divide operation. The result
is undefined !!
Dividing by 0 in user application.

Error #607: application file can not be validated and can not be loaded. err = %%
Validation of burned ladder application failed upon system start-up due to one
of the following reasons:

- Application version is lower than the firmware version.

- Ladder application block access failure.
- Not enough RAM memory to load/parse application
- Application block CRC error

Please try to re-download application file.

400
 Error Messages

Error #620: Ticks disabled exceed allowed limit : SR=%% IPR/IMR=%% WRR/WCN=%%
May indicate system software problem. Consult product group.

Error #630: Downloading/running C application is disabled in configuration.

The 'Disable C applications in RTU' advanced site configuration parameter in
the Firewall & Hardening section is set.

Error #631:
Unique download/deploy/upload error. Resolve the indicated problem and
repeat download/deployment.

Error #640: Fatal !!! Not enough work space for Monitor application !!
Available space transferred for the Monitor – %% bytes.
Minimum space required for Monitor – %% bytes.
May indicate system software problem. Consult product group.

Error #641: Monitor device failed to burn a file to the flash (MFFS err = %%, err = %%)
Failure in burning (and validating) a file to the Flash file system.

Error #644: Failed to chain file: %% to IO expansion %%.

This message appears when main CPU fails to download a file to one or more
I/O expansion frames. As a result, these I/O expansion frames will be reset to
retrieve the file by themselves..

Error #645: Download Chaining - internal error: Chaining task exited due to initialization
problem.
For system software developers only. Consult product group.

Error #646: Download Chaining - internal error: The downloaded size %% is not equal to the
expected %%.
For system software developers only. Consult product group.

Error #647: Download Chaining - internal error: semaphore (id = %%) operation (%%)
failure (status = %%).
For system software developers only. Consult product group.

Error #648: Unexpected unload of file id

The file ID that is currently downloaded should have been unloaded from the
RAM after validation, but failed to be unloaded.

Error #649: Failed to validate file id

The file ID that is currently being downloaded to the RTU failed its validation,
therefore the previous instance of the file in the RTU will be used.

401
 Error Messages

Error #650: Power Supply: Software error - timeout during communication to power supply
(SemTake).
errno %%
PS Op-code %%
Internal software message

Error #651: Power Supply: Communication CRC error between the power supply and the
CPU..
CRC Found - %%
Internal software message

Error #652: Power Supply: SPI -Communication timeout error.

Internal software message

Error #653: Power Supply: The power supply failed to execute the requested command.
Op-code - %%
PS ID - %%
The hardware of the specifed power supply failed to execute the specified
command. The data of the command and response are given.

Error #656: Power Supply: The power supply failed to execute the above command
because of the following reason: %%
PS ID - %%
The hardware of the specifed power supply failed to execute the specified
command. The reason for the failure is given.

Error #700: Invalid next version pointer : %%

Current version pointer : %%
Entry pointer of list : %%
Illegal linked list in the FLASH memory.

Error #701: Invalid data pointer : %%

Current version pointer : %%
Entry pointer of list : %%
Illegal linked list in the FLASH memory.

Error #702: Start data pointer : %%

Length of data : %%
Illegal linked list in the FLASH memory.

Error #730: Device TOPLC,Function %%, Port Name %% : Illegal Request from application.
May indicate system software problem. Consult product group.

402
 Error Messages

Error #731: Device TOPLC,Function %%, Port Name %% : Unable To Unpack F-Buffer.
May indicate system software problem. Consult product group.

Error #732: Device TOPLC,Function %%, Port Name %% : ERR_LOCK In TX Physical.

May indicate system software problem. Consult product group.

Error #733: Device TOPLC,Function %%, Port Name %% : ERR_FULL In TX Physical.

May indicate system software problem. Consult product group.

Error #734: Device TOPLC,Function %%, Port Name %% : Unable to Push A Block In F-UF
Buffer. Push block failed.
May indicate system software problem. Consult product group.

Error #735: Device TOPLC,Function %%, Port Name %% : Unable To Alloc Uf Buffer.
Allocation problem.
May indicate system software problem. Consult product group.

Error #736: Device TOPLC,Function %%, Port Name %% : Unable To Unpack Uf Buffer.
Unpack Uf Buffer failed.
May indicate system software problem. Consult product group.

Error #737: Device TOPLC,Function %%, Port Name %% : Unable To Alloc Buffer.
Allocation problem.
Empty heap. Consult product group.

Error #738: Device TOPLC,Function %%, Port Name %% : The Port to PLC is busy.
The port is busy.

Error #739: Device TOPLC,Function %%, Port Name %% : Not enough memory for the
application !!
May indicate system software problem. Consult product group.

Error #740: Device TOPLC,Function %%, Port Name %% FATAL, State EQ Waiting Control
but f_buf NE NULL !! Software problem.
May indicate system software problem. Consult product group.

Error #741: Device TOPLC, Function %%, Port Name %% : Fbuf Must Be NULL !!
May indicate system software problem. Consult product group.

Error #742: Device TOPLC,Function %%, Port Name %% : flashapp_get_block() has failed
!!
May indicate system software problem. Consult product group.

403
 Error Messages

Error #743: Device TOPLC,Function %%, Port Name %% : flashapp_cur_burn() has failed !!
May indicate system software problem. Consult product group.

Error #744: Device TOPLC, Function %%, Port Name %% : Not found the loaded software
for the port. This port is not operational.
The third-party protocol port is not operational.

Error #745: Device TOPLC, Function %%, Port Name %%

The download of software for this port has failed.

Error #746: Device TOPLC, Function %%, Port Name %% Received a control from the
SWITCHER while there is no software loaded for the PLC port. The received
f_buf (control) has been freed.
The RTU has to switch frames while the protocol is not loaded in the FLASH
memory.

Error #760: Device TOSCADA, Function %% Port Name %% : Illegal Request from
application.
May indicate system software problem. Consult product group.

Error #761: Device TOSCADA, Function %% Port Name %% : Unable To Unpack F-Buffer.
Unpack F-Buffer failed.
May indicate system software problem. Consult product group.

Error #762: Device TOSCADA, Function %% Port Name %% : ERR_LOCK In TX Physical.

May indicate system software problem. Consult product group.

Error #763: Device TOSCADA,Function %% Port Name %% : ERR_FULL In TX Physical.

May indicate system software problem. Consult product group.

Error #764: Device TOSCADA, Function %% Port Name %% : Unable to Push a Block In F-
UF Buffer. Push block failed.
May indicate system software problem. Consult product group.

Error #765: Device TOSCADA, Function %% Port Name %% : Unable To Alloc Uf Buffer.
Allocation of buffer failed.
Empty heap. Consult product group.

Error #766: Device TOSCADA, Function %% Port Name %% : Unable To Unpack Uf Buffer.
Unpack Uf Buffer failed.
May indicate system software problem. Consult product group.

404
 Error Messages

Error #767: Device TOSCADA, Function %% Port Name %% : Unable To Alloc Buffer.
Allocation of buffer failed.
Empty heap. Consult product group.

Error #768: Device TOSCADA, Function %% Port Name %% : The Port to SCADA is busy.
The port is busy.

Error #769: Device TOSCADA, Function %% Port Name %% : The f_buf is missing !!
May indicate system software problem. Consult product group.

Error #770: Device TOSCADA, Function %% Port Name %% : Cannot find site index and
port.
There is a problem in PLC table or site table definition.

Error #771: Device TOSCADA, Function %% Port Name %% : Not enough memory for the
application.
Memory problem. Consult product group.

Error #772: Device TOSCADA, Function %% Port Name %% : flashapp_get_block() has

failed !!
May indicate system software problem. Consult product group.

Error #773: Device TOSCADA, Function %% Port Name %% : flashapp_cur_burn() has

failed !!
May indicate system software problem. Consult product group.

Error #774: Device TOSCADA, Function %% Port Name %% :

Not found the loaded software for the port. This port is not operational.
PLC port connected to master is not operational. Consult product group.

Error #775: Device TOSCADA, Function %% Port Name %%

The download of software for the port failed.
Download of software for third party protocol has failed.

Error #776: Device TOSCADA, Function %% Port Name %%

Received a reply frame from the SWITCHER while there is no software loaded
for the port.
The received frame (reply) has been freed. No software loaded for third party
protocol port.

405
 Error Messages

Error #820: Userrom Plc module, Function %%

Control Format Error !
Communication protocol format error. May indicate system software problem.
Consult product group.

Error #821: Userrom Plc module, Function %%

Pushbyte To fbuf Failed !
May indicate system software problem. Consult product group.

Error #822: Userrom Plc module, Function %%

Pusblock To fbuf Failed !
May indicate system software problem. Consult product group.

Error #823: Userrom Plc module, Function %%

Get_coldef_tab Failed !
May indicate system software problem. Consult product group.

Error #824: Userrom Plc module, Function %%

Data Type Format Error In Protocol !
Communication format error. Consult product group.

Error #825: Userrom Plc module, Function %%

Data Type Mismatch !
Data type error when accessing a column via PLC communication. Data type
mismatch.

Error #826: Userrom Plc module, Function %%

Number of elements must be greater from 0
May indicate system software problem. Consult product group.

Error #827: Userrom Plc module, Function %%

First Y – coord. out of range !
This message indicates that the SCADA accesses via PLC communication a row
which is out the range of defined rows.

Error #828: Userrom Plc module, Function %%

Last Y – coord. out of range !
This message indicates that the SCADA accesses via PLC communication a row
which is out the range of defined rows.

Error #829: Userrom Plc module, Function %%

Unpack of f_buf failed !
May indicate system software problem. Consult product group.

406
 Error Messages

Error #830: Userrom Plc module, Function %%

Scan failed. No rows in column !
May indicate system software problem. Consult product group.

Error #831: Userrom Plc module, Function %%

Cannot allocate f-buf !
Empty heap. Consult product group.

Error #832: Userrom Plc module, Function %%

Reply Format Error !
Communication format error in the reply frame. May indicate system software
problem. Consult product group.

Error #833: Userrom Plc module, Function %%

Cannot Find PLCStt !
May indicate system software problem. Consult product group.

Error #834: Userrom Plc module, Function %%

Iolink definition problem of PLC column !
May indicate system software problem. Consult product group.

Error #835: Userrom Plc module, Function %%

Some PLC address in not defined in PLC Table !
Define all PLC addresses in the PLC Table.

Error #836: Userrom Plc module, Function %%

Illegal Data Type !
May indicate system software problem. Consult product group.

Error #837: Userrom Plc module, Function %%

Reply ignored, when no application
This message may appear during an additional application download.

Error #838: Userrom Plc module, Function %%

Reply Ignored, Not Waiting For Reply !
May indicate system software problem. Consult product group.

Error #839: Userrom Plc module, Function %%

Reply Ignored due to unpack failure!
May indicate system software problem. Consult product group.

407
 Error Messages

Error #840: Userrom Plc module, Function %%

Reply Ignored, site index and port not as expected!
May indicate system software problem. Consult product group.

Error #841: Userrom Plc module, Function %%

Reply Ignored, sequence number not as expected!
Timeout problems. Consult product group.

Error #842: Userrom Plc module, Function %%

Reply Ignored, length is not as expected!
May indicate system software problem. Consult product group.

Error #843: Userrom Plc module, Function %%

Reply Application Error %% !
May indicate system software problem. Consult product group.

Error #844: Userrom Plc module, Function %%

Cannot Find PLC address %% in download process or userrom not OK.
Can not perform PLC communication while application not loaded or during
application download.

Error #845: Userrom Plc module, Function %%

Failed to find PLC address %% in PLC Table.
Define all PLC addresses in PLC Table.

Error #846: Userrom Plc module, Function %%

When referring RTU PLC from rungs, you must define in IOLINK only the (z,x,y)
coordinates !
The length of each coordinate must be 1 byte !
I/O link definition error in PLC type column.

Error #847: Userrom Plc module, Function %%

Destination PLC IOLINK data type error !
When referring RTU PLC from rungs, the data type of the column in I/O Link
must be defined as one of the followings:

a) PLCBIT
b) PLCVAL
c) PLCFLT

Communication protocol format error. Consult product group.

Error #848: Userrom Plc module, Function %%

The length of PLC column being scanned should not exceed 140 bytes !!!
Scan on PLC type column should not exceed 140 bytes.
408
 Error Messages

Error #861: The phone connection was established, but the RTU doesn't respond
Different Site ID of the addressed phone number.

Error #862: ML_Dial: TX fail, probably the phone line was disconnected.
Can not transmit due to disconnected phone line.

Error #863: No phone Book in flash memory.

Can not dial without phone book.

Error #875: Status is 'wait for call' but the line is active.
The RTU software status and phone line status do not match; the line will be
disconnected.

Error #876: The TX thread did not hang up the phone line as the RX thread asked.
For system software developers. Consult product group.

Error #877: Can not find Site Id – %% in phone book.

Can not dial a Site ID without it being defined in the phone book.

Error #878: Modem refuses to dial this phone number (too long, invalid command, or
answer mode only):
Invalid command (internal problem).

Error #879: Unsuccessful modem configuration (%%,%%)

Failed to configure modem for dialup.

The first %% - Indicates in what stage of configuration it failed:

Reset - Fail to reset modem - Probably wrong reset process; can be
changed in the .stm file.
AT - No response from the modem. - Probably a communication
problem.
File - Modem rejected AT commands from the .stm file. -
Probably wrong .stm file or section in file.

The second %% - Indicates which event caused the modem configuration

attempt.
Startup - Failure to configure modem at cold restart.
Warm reset - Failure to configure modem at warm restart.
Download file - Failure to configure modem after that a new .stm
file was downloaded.

Check that the modem is properly connected. If there is a modem configuration

(.stm) file, check that it is appropriate for the modem. Make sure the modem is
a type that is supported by the RTU.

409
 Error Messages

Error #900: PLC Switcher module, Function %%

Fatal ! The SWITCHER Device is destroyed – CRC error !
May indicate system software problem. Consult product group.

Error #901: PLC Switcher module, Function %%

Cannot allocate a formatted buffer !
Empty heap. Consult product group.

Error #902: PLC Switcher module, Function %%

Found in port table a logical port i.d with not expected direction
Third party protocol port definition problem.

Error #903: PLC Switcher module, Function %%

Remove slice of formatted buffer failed !
May indicate system software problem. Consult product group.

Error #904: PLC Switcher module, Function %%

Get slice of formatted buffer failed !
For system software developers. Consult product group.

Error #905: PLC Switcher module, Function %%

buf_f_init of formatted buffer failed !
For system software developers. Consult product group.

Error #906: PLC Switcher module, Function %%

Switcher format error of received frame !
May indicate system software problem. Consult product group.

Error #907: PLC Switcher module, Function %%

Illegal direction parameter!! Getting of PLC port failed !
Third party protocol port definition error.

Error #908: PLC Switcher module, Function %%

Cannot get the PIN Table !
May indicate system software problem. Consult product group.

Error #909: PLC Switcher module, Function %%

Cannot find the key of a PLC port software from logical port i.d.!
May indicate system software problem. Consult product group.

Error #910: PLC Switcher module, Function %%

Cannot find in switcher port table the key of PLC%% connected to %%
PLC table,site table or third party protocol port definition problem.

410
 Error Messages

Error #911: PLC Switcher module, Function %%

Pull Buffer from Head LIST Failed, although the list is not empty !!
May indicate system software problem. Consult product group.

Error #912: PLC Switcher module, Function %%

Push Buffer to Head LIST Failed.
Fatal !! The Head List is corrupted !
May indicate system software problem. Consult product group.

Error #913: PLC Switcher module, Function %%

Push Buffer to Head LIST Failed. Too many buffers in the head list!
The buffer was freed !!
May indicate system software problem. Consult product group.

Error #930: MODBUSTM module, Function %%

Illegal state !!
May indicate system software problem. Consult product group.

Error #931: MODBUSTM module, Function %%

Not enough RAM memory for MODBUS load module connected to MASTER !!
May indicate system software problem. Consult product group.

Error #932: MODBUSTM module, Function %%

Received the reply not in expected format
Timeout problems or system software problem. Consult product group.

Error #933: MODBUSTM module, Function %%

The size of MODBUS format reply is too large or too small
The master should not send frames or poll for frames longer than 140 bytes.

Error #934: MODBUSTM module, Function %%

The MODBUS reply frame CRC is not correct
CRC error in MODBUS reply frame.

Error #935: MODBUSTM module, Function %%

The size of RTU PLC format reply is too large or too small
The master should not send frames or poll for frames longer than 140 bytes.

Error #936: MODBUSTM module, Function %%

No support for broadcast. Frame ignored
The MODBUS module does not support broadcasts.

411
 Error Messages

Error #937: MODBUSTM module, Function %%

MODBUS to RTU PLC format translation of control failed !!
Unable to interpret MODBUS format frame. May indicate system software
problem. Consult product group.

Error #938: MODBUSTM module, Function %%

RTU to MODBUS format translation of reply failed !!
Unable to combine MODBUS reply. May indicate system software problem.
Consult product group.

Error #939: MODBUSTM module, Function %%

The received frame is too long for the RX buffer of the module !!
The MODBUS master should not send frames or poll for frames longer than 140
bytes.

Error #940: MODBUSTM module, Function %%

The size of translated to RTU PLC format control is too large for the buffer
The received MODBUS frame is too long.

Error #941: MODBUSTM module, Function %%

The RTU PLC reply format buffer is less than 2 bytes!
May indicate system software problem. Consult product group.

Error #942: MODBUSTM module, Function %%

The RTU PLC format NACK buffer is greater than 2 bytes!
May indicate system software problem. Consult product group.

Error #943: MODBUSTM module, Function %%

The RTU PLC format spare field is not 0 !!
May indicate system software problem. Consult product group.

Error #944: MODBUSTM module, Function %%

The box number of the reply is not as expected!!
Timeout problems. Consult product group.

Error #945: MODBUSTM module, Function %%

The length of pure data in frame is not as expected!!
Timeout problems or system software problem. Consult product group.

Error #946: MODBUSTM module, Function %%

Can not pack in 1 byte the N_BYTES field in 1 byte.
The value of N_BYTES > 0xff.
May indicate system software problem. Consult product group.

412
 Error Messages

Error #947: MODBUSTM module, Function %%

The ACK reply received with data. Expecting ACK with no data !
Timeout problems or system software problem. Consult product group.

Error #948: MODBUSTM module, Function %%

Received a non supported function request
Received a request from MODBUS master that is not supported by the RTU.
Request is ignored.

Error #949: MODBUSTM module, Function %%

Number of elements must be less from 0xff.
Received a request for more than 0xff elements.
The master should not send frames or poll for frames longer than 140 bytes.

Error #950: MODBUSTM module, Function %%

The FLUSH function failed, but continuing
May indicate system software problem. Consult product group.

Error #951: MODBUSTM module, Function %%

The Set Parameters function failed, but continuing
May indicate system software problem. Consult product group.

Error #970: MODBUSTS module, Function %%

Illegal state !!
May indicate system software problem. Consult product group.

Error #971: MODBUSTS module, Function %%

Not enough RAM memory for MODBUS load module connected to PLC !!
May indicate system software problem. Consult product group.

Error #972: MODBUSTS module, Function %%

The FLUSH function failed, but continuing
May indicate system software problem. Consult product group.

Error #973: MODBUSTS module, Function %%

The Set Parameters function failed, but continuing
May indicate system software problem. Consult product group.

Error #974: MODBUSTS module, Function %%

The size of MODBUS format reply is too large or too small
The master should not send frames or poll for frames longer than 140 bytes.

413
 Error Messages

Error #975: MODBUSTS module, Function %%

MODBUS to RTU PLC format translation of reply failed !!
May indicate system software problem. Consult product group.

Error #976: MODBUSTS module, Function %%

No support for broadcast. Frame ignored
No support for broadcast frames in MODBUS protocol.

Error #977: MODBUSTS module, Function %%

The CRC of MODBUS control frame is not correct !
Consult product group.

Error #978: MODBUSTS module, Function %%

The control frame in MODBUS format is too long for the module or is too short !
The master should not send frames or poll for frames longer than 140 bytes.

Error #979: MODBUSTS module, Function %%

The control frame in RTU PLC format is too long for the module or is too short !
The master should not send frames or poll for frames longer than 140 bytes.

Error #980: MODBUSTS module, Function %%

Illegal opcode (command) in RTU PLC format control !
May indicate system software problem. Consult product group.

Error #981: MODBUSTS module, Function %%

Pure data in Poll control. No data must appear in this control !!
May indicate system software problem. Consult product group.

Error #982: MODBUSTS module, Function %%

The N_ELM field in poll control is zero !
It must be GE from 1.
May indicate system software problem. Consult product group.

Error #983: MODBUSTS module, Function %%

Could not translate the RTU PLC to MODBUS because the MODBUS buffer is
too short
The master should not send frames or poll for frames longer than 140 bytes.

Error #984: MODBUSTS module, Function %%

Could not translate the RTU PLC to MODBUS !
No support for the data type appearing in a poll control !
May indicate system software problem. Consult product group.

414
 Error Messages

Error #985: MODBUSTS module, Function %%

The length of pure data in send control is 0 !!
It must be GE from 1
May indicate system software problem. Consult product group.

Error #986: MODBUSTS module, Function %%

The N_ELM field in send control is EQ 0 !
It must be GE from 1
May indicate system software problem. Consult product group.

Error #987: MODBUSTS module, Function %%

The length of pure data in send control is greater from 0xff !
It must be LE from 0xff !
May indicate system software problem. Consult product group.

Error #988: MODBUSTS module, Function %%

The length of pure data does not fit to the data type and to the N_ELM field in
RTU PLC format frame !
May indicate system software problem. Consult product group.

Error #989: MODBUSTS module, Function %%

No support for the data type in the send control frame !
May indicate system software problem. Consult product group.

Error #990: MODBUSTS module, Function %%

The expected length of pure data reply is GT 0xff bytes. Modbus protocol does
not allow read of DATA the length of which is GT 0xff bytes
The master should not send frames or poll for frames longer than 140 bytes.

Error #991: MODBUSTS module, Function %%

The length of exception reply is not as expected
Timeout problems or system software problem. Consult product group.

Error #992: MODBUSTS module, Function %%

The reply header contents is not as expected
Timeout problems or system software problem. Consult product group.

Error #993: MODBUSTS module, Function %%

The reply frame length is not as expected
Timeout problems or system software problem. Consult product group.

415
 Error Messages

Error #994: MODBUSTS module, Function %%

RTU to MODBUS format translation of control has failed !!
May indicate system software problem. Consult product group.

Error #1000: ABTS module, Function %%

Illegal state !!
May indicate system software problem. Consult product group.

Error #1001: ABTS module, Function %%

No support for non MOSCAD master in Allen Bradley protocol
No support for RTU as slave in Allen Bradley protocol. (Third party protocol)

Error #1002: ABTS module, Function %%

The control frame in RTU PLC format is too long for the module or is too short !
The master should not send frames or poll for frames longer than 140 bytes.

Error #1003: ABTS module, Function %%

The Set Parameters function failed, but continuing
May indicate system software problem. Consult product group.

Error #1004: ABTS module, Function %%

Could not translate the RTU PLC to Allen-Bradley !
No support for the data type appearing in a poll control !
May indicate system software problem. Consult product group.

Error #1005: ABTS module, Function %%

Number of bits must be a multiple of 16 !
The length of PLC_DI or PLC_DO column must be a multiple of 16.

Error #1006: ABTS module, Function %%

Failed to build the reply or command in Allen Bradley format !
May indicate system software problem. Consult product group.

Error #1007: ABTS module, Function %%

Pure data in Poll control. No data must appear in this control !!
May indicate system software problem. Consult product group.

Error #1008: ABTS module, Function %%

The N_ELM field in send control is EQ 0 !
It must be GE from 1
May indicate system software problem. Consult product group.

416
 Error Messages

Error #1009: ABTS module, Function %%

The length of pure data in send control is 0 !!
It must be GE from 1
May indicate system software problem. Consult product group.

Error #1010: ABTS module, Function %%

The N_ELM field in send control is EQ 0 !
It must be GE from 1
May indicate system software problem. Consult product group.

Error #1011: ABTS module, Function %%

No support for the data type in the send control frame !
May indicate system software problem. Consult product group.

Error #1012: ABTS module, Function %%

The opcode in RTU PLC format is neither SEND nor POLL !
May indicate system software problem. Consult product group.

Error #1013: ABTS module, Function %%

The expected reply length in RTU PLC format is too long !
There is no support for replies longer than 140 bytes. Do not scan columns
longer than 140 bytes.

Error #1014: ABTS module, Function %%

Failed to decode the Allen-Bradley reply !
May indicate system software problem. Consult product group.

Error #1015: ABTS module, Function %%

The size of Allen-Bradley format reply is too large or too small
The reply should not exceed 140 bytes.

Error #1016: ABTS module, Function %%

The FLUSH function failed, but continuing
May indicate system software problem. Consult product group.

Error #1017: ABTS module, Function %%

Not enough RAM memory for Allen-Bradley load module connected to PLC !!
May indicate system software problem. Consult product group.

Error #1018: ABTS module, Function %%

Allen-Bradley to RTU PLC format translation of reply failed !!
Internal communication protocol format error. Consult product group.

417
 Error Messages

Error # 1050: Insufficient memory for MODBUSTCPS device resources creation.

MODBUS TCP slave port is not supported. Please reboot the RTU.
Please reboot the RTU.

Error # 1051: Problem with masters incoming requests list creation.

MODBUS TCP slave port is not supported. Please reboot the RTU.
Please reboot the RTU.

Error # 1052: Problem with masters incoming requests message queue creation.
MODBUS TCP slave port is not supported. Please reboot the RTU.
Please reboot the RTU.

Error # 1053: Unauthorized master's attempt to access ACE slave port %% via TCP port %%
and IP address %%.
Connection socket with master is closed.
An unauthorized master (not listed in the PLC IP access control table) attempted
to communicate with the RTU. Either register this master in the table or
investigate the communication attempt.

Error # 1054: Master's attempt to connect to ACE slave port %% via TCP port %% and IP
address %% denied due to masters connection overquota.
No. of available connections = %%.
No. of used connections = %%.
No. of total connections = %%.
Connection socket with master is closed.
All 16 connections available for MODBUS TCP/IP communication are
occupied. There is a master trying to establish a new connection with the RTU.
Investigate the communication attempt.

Error # 1055: Can not process incoming requests from socket address %% over socket ID %%
(Failed to spawn RX task).
For each connection with MODBUS TCP/IP master there is a seperate RX task.

The VxWorks OS failed to initiate the Rx task for a connection with a

MODBUS TCP/IP master. Make sure there are enough resources for handling a
new task (sufficient memory is, etc.) Consider terminating all connections and
restarting them on the master side.

Error # 1056: Failed to terminate task ID %% in charge of RX from master (error = %%).
The VxWorks failed to delete an Rx task for a specific MODBUS TCP/IP
connection. Contact product support.

418
 Error Messages

Error # 1057: Failed to push an incoming master's request to message queue over PLC port
%% and connection %%.
Request identifiers: transaction ID=%%, unit ID=%%, socket ID=%% (error =
%%, OS error = %%).
The incoming masters request could not be pushed to the message queue. This
could be due to a number of reasons:
- The queue has no free buffer space.
- A timeout occurred while waiting for buffer space.
- The request length exceeded the limit (illegal request).
Contact product support.

Error # 1058: Failed to pull an incoming master's request from message queue (num msgs in
Q = %%, OS error = %%).
The incoming masters request could not be pulled from the queue, most likely
due to a timeout. Contact product support.

Error # 1059: MODBUS backend failed to receive incoming master's request from %% via PLC
port %% on connection %%.
Request identifiers: transaction ID=%%, unit ID=%%, socket ID=%% (error =
%%).
The MODBUS backend software failed to handle the incoming request
unformatted buffer. Contact product support.

Error # 1060: MODBUS backend failed to transmit master a response.

Response identifiers: transaction ID=%%, unit ID=%%, socket ID=%% (error =
%%).
The MODBUS backend software failed to handle the outgoing respond
unformatted buffer. Contact product support.

Error # 1061: Failed to update PLC access control connection statistics:

PLC port=%%, IP address=%%, statistics: type=%% & mode=%%,
connection_index=%%, error=%%.
Connection statistics for an authorized master cannot be updated due to limited
access to the PLC IP access control table. Consider terminating all connections
and restarting them on the master side.

Error # 1062: Failed to match between the incoming master's request unit ID and RTU's PLC
addresses, over PLC port %% and connection %%.
Request identifiers: transaction ID=%%, unit ID=%%, socket ID=%% (error =
%%).
The incoming request is addressed to a PLC address which is not this RTU's
PLC address. Either update the incoming request's address in the ladder
application PLC system table, or investigate the request.

419
 Error Messages

Error # 1063: Master's attempt to connect to ACE slave port %% via TCP port %% and IP
address %% denied (err = %%).
Failed to establish a new connection with a master (even though there are
available connections). Consider terminating all connections and restarting
them on the master side. Contact product support.

Error # 1064: Illegal requests pool's count for PLC port %% on connection %%.
Mismatch between the incoming requests pool counter and the actual number of
requests in the pool. Contact product support.

Error # 1080: MODBUS backend failed to receive incoming slave's request from %% via PLC
port %% on connection %%.
Request identifiers: transaction ID=%%, unit ID=%%, socket ID=%% (error =
%%).
There was a problem receiving the packet from the slave, due to a problem with
the buffer. Contact product support.

Error # 1081: MODBUS backend failed to transmit slave a response via PLC port %% on
connection %%.
Response identifiers: transaction ID=%%, unit ID=%%, socket ID=%% (error =
%%).
Could not transmit to the slave due to an internal operating system socket
problem. Contact product support.

Error # 1082: MODBUS backend failed to transmit a response to slave, MODBUS address
%%, because the userrom didn't return the appropriate information.
Due to an error with the specified MODBUS address, the application could not
find the correct information in the PLC table and therefore cannot transmit.
Make sure the PLC address does not change during runtime.

Error # 1083: MODBUS backend failed to transmit a response to slave, because the buffer
didn't start correctly.
Error number %%.
There was a problem transmitting the packet to the slave, due to a problem with
the buffer. Contact product support.

Error #1230: Chnltest -RX task got err Frame When Called From Trnsintr.
buf_f_get() Returned: %%
May indicate system software problem. Consult product group.

Error #1231: Chnltest -Received tested frame too small. Length of frame is %%
Frame lacks its header.
May indicate system software problem. Consult product group.

420
 Error Messages

Error #1232: Chnltest -Tx Task Could not get a new buffer from heap.
Ret: %%
No buffer for transmission.

Error #1233: Chnltest -Tx Task has Frame area too small for tested frame.
Frame Area Size is %%
Frame size is less than the user's definition in the test's setup. May indicate
system software problem. Consult product group.

Error #1234: Chnltest -Tx Task Failed Transmit Frame. trnsintr_tx_frame()

Returns : %%
Can not transmit a frame via Transport MUX. May indicate system software
problem. Consult product group.

Error #1235: Chnltest -Tx Task Failed Getting indx of tested_link in sites_table. Err code %%
Could not get tested link id's index in site table prior to transmitting a frame.
May indicate system software problem. Consult product group.

Error #1236: Chnltest -Cannot Handle Control Frame. Another Opcode Already Exist
May indicate system software problem. Consult product group.

Error #1237: Chnltest -Received Control Frame (pres_get_struct) too small to decode.
Length of Frame is %%
May indicate system software problem. Consult product group.

Error #1238: Chnltest -Control Frame too Small for answer. Length is %%
May indicate system software problem. Consult product group.

Error #1239: Chnltest -Received aplic structure with invalid size. Size is %% Length bigger
than buffer or Length small to contain opcode.
May indicate system software problem. Consult product group.

Error #1260: Tmrevent: Events/Timers Buffer is Full.

No more buffers for DI events and their related timers. Number of buffers can
be increased in expert screen in configuration.

Error #1261: Tmrevent: Events/Timers were Ignored – NO 'Get Event' for %% msec
DI events and/or related timers were not checked (by GtEvnt function in rungs)
during a time interval longer than the maximum time that was defined in the
expert screens, and therefore were ignored.

421
 Error Messages

Error #1262: Tmrevent: Invalid timer value (%% ms).

Timer Event: The SetTmr (Set Timer) function has been called with an invalid
event timer value. Please reduce the timer value or modify the ‘Max. EVENT
timer value’ site configuration advanced parameter.

Error #1263: Tmrevent: Allocation of heap buffer failed.

Timer Event heap element allocation failure.

Error #1264: Tmrevent: Deallocation of heap buffer failed.

Timer Event heap element deallocation failure.

Error #1265: Tmrevent: (Z, Y, X) coordinates were not found for

rack_module: %%, element (starting from 0): %%.
The GtEvnt (Get event) function failed to find the ZYX for the specified DI rack
module event.

Error #1266: Tmrevent - unknown event type during "Get" operation.

Event type: %%.
The GtEvnt (Get event) function got an invalid event type.

Error #1267: Tmrevent - There is a communication problem (MsgQ).

May indicate that the timer event queue is full. Contact product group.

Error #1268: Tmrevent - Error receiving acknowledge from main frame, expansion number
%%.
May indicate that a communication problem exists between the main frame and
I/O expansion frame. Check communication cables.

Error #1269: Tmrevent - Error receiving acknowledge from master expansion, wrong id,
expansion number %%.
May indicate lack of synchronization between the main frame and I/O
expansion frame. Restart the main CPU and expansion modules.

Error #1270: Tmrevent - Slave unit %% has overflowed.

Timer event queue is full. Either increase the STS advanced parameter ‘Timer
event time to buffer events in expansion’ or decrease the STS advanced
parameter ‘Total number of EVENTs (status/timer)’.

Error #1271: Tmrevent - Socket error, expansion number %%.

May indicate software problem. Contact product group.

422
 Error Messages

Error #1272: Expansion unit %% is not synchronized.

The expansion module is not synchronized with the main CPU. Restart the
main CPU and expansion modules.

Error #1400: %%
TCP/IP error message string.

Error #1450: Ladder or C application needs I/O modules with DI, but Configuration I/O
modules do not have the expected amount of DI
Define more DI modules in Site Configuration.

Error #1700: Failed initiating GPS port

Port 2, connected to GPS, cannot be initialized, because of hardware problem.

Error #1701: Transmission failure to GPS

Transmission to GPS failed because of hardware problem.

Error #1750: Insufficient dynamic memory. Needed: %%

Cannot allocate memory for “C” block because the size indicated in Site
Configuration is insufficient.

Error #1751: Invalid block

Invalid “C” block loaded to the RTU. Its calculated CRC does not match that of
the loaded block. Reload the “C” block.

Error #1752: User Application Error:

Occurs as a result of MOSCAD_error function usage in one of the “C” blocks
loaded to the RTU.

Error #1753: C Service not supported in this unit type.

The ‘C’ application downloaded to the Flash uses a C service which is not
supported by this RTU type and version. (MOSCAD)

Error #1770: The Downloadable "C" function is running too long. Could not delete it from
table.
Occurs as a result of error in one of the “C” blocks loaded to the RTU.

Error #1790: Socket Opening failed.

Communication problem with MDLC over IP.

Error #1791: Socket Connection failed.

Communication problem with MDLC over IP.

423
 Error Messages

Error #1810: Could not abort the master sessions. The master channels are not stopped.
Problem with C master session during Download.

Error #1810: Could not abort the master sessions. The master channels are not stopped.
Problem with C master session during Download.

Error #1852: Failed to allocate memory space to load errors from file.
RAM allocation problem when loading errors from the Flash.

Error #1853: Errors classification: %%

Heading text for the list of all the specific errors polled from the RTU.

Error #1854: Invalid error size %% greater than maximun size %%.
The length of the error to be written to the Error logger file in the flash exceeds
the maximum allowed error length.

Error #1855: Failed to read messages from error logger pipe (len=%%, errno = %%)
Messages that are redirected from VxWorks' messages logger/Standard
output/Standard error to ACE's error logger pipe cannot be polled.

Error #1856: Message polled from standard output/standard error/messages logger: %% …

This message may indicate one of two types of warning/error:
1. A VxWorks network stack error where the text above is followed by the
original text taken from the VxWorks messages logger/Standard
output/Standard error, such as “0x1628fb0 (tNetTask): arp info overwritten for
10.100.100.100 by 00:20:75:14:ae:e8.”

2. A warning/error related to an ACE3600 startup warning/error, where the text

above is followed by the the ACE3600 warning/error, such as. “IOEManager
warning 5505: Received a request from unexpected Expansion Module 7.
Check I/O configuration and Expansion Module’s rotary switch.”

Error #1859: Failed to open the syslog results file: %%

Error logger- Internal use only.

Error #1860: Could not read a line from syslog result file. Retcode: %%
Error logger- Internal use only.

Error #1861: Could not allocate memory. Size= %%

Error logger- Internal use only.

Error #1862: Could not read data in line. Retcode: %%

Error logger- Internal use only.

424
 Error Messages

Error #1863: Could not send line. Retcode: %%

Error logger- Internal use only.

Error #1864: No reply from client, Could not send line. Retcode: %%
Error logger- Internal use only.

Error #1865: Called with invalid commwrapper handle. Retcode: %%

Error logger- Internal use only.

Error #1866: Failed receive commwrapper handle. Retcode: %%

Error logger- Internal use only.

Error #1867: Activated with invalid errlog parameters. Retcode: %%

Error logger- Internal use only.

Error #1868: Failed to update the transaction DB. Err:%%

Error logger- Internal use only.

Error #1869: Failed to write error status on DB. Req ID: %% Req status: %% Error code %%
Error logger- Internal use only.

Error #1870: Failed to send protocol request. Err:%%

Error logger- Internal use only.

Error #1871: Failed to receive data from slave. Err:%% In number: %%

Error logger- Internal use only.

Error #1872: Failed to end session. Err:%%

Error logger- Internal use only.

Error #1873: Failed to receive comwrapper handle. Err:%%

Error logger- Internal use only.

Error #1874: Failed to allocate memory for reply. Err:%%

Error logger- Internal use only.

Error #1875: Failed to retrieve errors from error log (error code = %%)
Error logger- Internal use only.

Error #1876: Invalid data received. Err=%% Line number: %%

Error logger- Internal use only.
425
 Error Messages

Error #1904: Destination site ID %% not supported

Error in MDLC over IP. Site ID does not appear in the IP Conversion Table.
Check if Site has IP address or if Site ID is correct.

Error #1905: Sync transmission is not supported

Error in MDLC over IP. RTU cannot send Sync frames through this link. Error
is obsolete.

Error #1906: Invalid conversion table in Flash

Error in MDLC over IP. IP Conversion Table which was downloaded could not
be read or is invalid. There may be a problem with the Flash or with the IP
Conversion Tool. Consult product group.

Error #1907: IP address in conversion table for this CPU is %% instead of the configured %%
Error in MDLC over IP. Mismatch in IP Conversion Table between the IP
address of this RTU and the one configured in the table. Correct either the table
or the Site ID.

Error #1908: Configured IP address (%%) of this CPU is in use by site %%

Error in MDLC over IP. Error in IP addresses. This error is obsolete.

Error #1909: Failed configuring radio in encryption mode.

Error in MDLC over IP for Astro radio. Problem with radio configuration.
Relevant for encryption mode only.

Error #1910: Failed transmission to Site %% because its IP address is myself.

RTU tried to transmit to a destination site with the same IP address as the RTU.
As a result, transmission failed. Check IP address conversion table for the
specified site; it will have the same IP address as that of the RTU. Correct IP
address.

Error #1911: User configured RTU IP address as %% instead of modem’s configuration %%

Future use. This error will occur when connecting to a non-iDEN packet data
modem with Learn IP Address as NO. When the IP addresses configured in the
modem and RTU differ, the RTU has not learned the address from the modem.
Reconfigure RTU IP address or consult product group.

Error #1912: Modem not configured for Packet data properly (error code %%)
Modem packet data parameters are not appropriate, e.g. no Home Agent IP
address, or no RTU IP address as expected by the infrastructure.

Error #1913: Failed connect IPMODM to Timer key.

Internal use; should not occur. Denotes SLIP port configuration failure.

426
 Error Messages

Error #1914: Got alarm %% from iDEN modem

Got unexpected software alarm from modem (which is not software or
registration.) Denotes a problem with the modem software. Consult product
group.

Error #1915: Unsupported 'connect to' %% device in MDLC over IP port

‘Connect to’ parameter is not supported by this system. This is provided for
future configuration having new drivers that will be downloaded to older
systems that does not support them.

Error #1916: MDLC Compression not supported in Slip/PPP port

This error is set when future configurations that support MDLC compression on
Slip/PPP will be downloaded to older systems that do not support it.

Error #1917: MDLC confirmed link not supported in Slip/PPP port

This error is set when future configurations that support MDLC link capability
between adjacent sites on Slip/PPP will be downloaded to older systems that
does not support it.

Error #1918: Dial operation not supported in Slip/PPP port

This error is set when future configurations that support dial operation on
Slip/PPP will be downloaded to older systems that do not support this feature.
Dial operation is a qualifier specifying when RTU needs to connect and initiate
Slip/PPP. When not used or not supported RTU is always connected.

Error #1919: Dial number not supported in Slip/PPP port

This error is set when future configurations that support dial numbers on
Slip/PPP will be downloaded to older systems that do not support it. Dial
number is an alternate string (such as phone number) used when connecting to
modem instead of common ATD. Even though not supported, user can still
specify this string and others by using a Standard Modem configuration through
a downloaded IP Modem file.

Error #1920: %%
This error is set when there was a problem reading/executing a command from
the IP Modem file. The IP Modem file is read when configuring a Standard
Modem for Slip/PPP port.

Error #1921: Failed set PPP parameter %% as %%

The specified PPP parameter in the configuration file could not be set to the
specified value. Enter a valid value for this variable according to the MDLC
over IP description in the Toolbox documentation (modem configuration file
section).

427
 Error Messages

Error #1922: Failed configure %% %% times for %% seconds

The RTU failed to configure, connect or context activate a packet data
modem/radio after the specified amount of time. Check the connection with the
radio/modem, and check with the operator why radio/modem failed to connect
with infrastructure. To increase the timeout from the specified value, modify it
in the Site Configuration or in the max_failedtime variable in the modem
configuration file.

Error #1923: IP Conversion table is full cannot add site ID %%

The RTU could not add a new, learned site ID to the IP conversion table.
Therefore, it could not reply to this unregistered site ID. Increase the maximum
size of the IP Conversion Table in the Site Configuration.

Error #1924: Failed bind MDLC over IP socket result is %% port is %%

Failed to bing the MDLC over IP socket for the specified port. The same
radio/modem IP address was used in more than one port. Check the port and/or
radio configurations.

Error #1930: Bad IP conversion Table row %% offset %%

Failed to read the IP conversion table after download or startup because the
specified row is invalid. Check the specified row in the IP conversion table
using the STS.

Error #1931: Site name %% specified for site ID %% but link ID %% 'gethostbyName' is not
enabled
The specified host name was defined by the user for the specified site ID/link
ID, but the ‘Get host by name using DNS’ advanced link parameter for the port
is not enabled. There, this entry in the IP conversion table will be ignored.

Error #1932: Failed allocate memory for site name %% site ID %% link ID %%
An error occurred when reading a new IP conversion table and allocating
memory for a new entry with the specified site host full name. As a result, the
specified site was not read into the table.

Error #1933: Ignored IP address coming from site %% on link %%.

Ignored IP address is %% and current IP address is %%.
An ASTRO IV&D radio has transmitted a bad IP address to the LAN and it will
be ignored. It is assumed that the IP address of the radio is 192.168.128.xx for
the purposes of this test.

Error #1950: Failed to push buffer to the reception queue of the dowloaded protocol driver
May indicate system software error. Consult product group.

428
 Error Messages

Error #1951: Failed to get character(s) from the reception queue of the dowloaded protocol
driver
May indicate system software error. Consult product group.

Error #1952: The reception queue of the dowloaded protocol driver is full.
Driver of second protocol is not emptying frames from queue fast enough.

Error #2100: Unsupported service was called in radio port %% (%%) module.
Service request from radio channel access module at this port is not supported.

Error #2200 Failed to receive a backup operation from DB backup queue (RcvErr = %%,
errNo = %%).
Failed to process a database backup operation (store/restore/remove) from the
database backup operations queue. RcvErr/errNo are for internal use.

Error #2201 Failed to add a backup operation to DB backup queue (p1: %%, p2: %%, p3:
%%, p4: %%, p5: %%).
Failed to push a databae backup operation (store/restore/remove) to the database
backup operations queue.

p2=block No. p3=backup operation type. p1/p4/p5 are for internal use.

Error #2202 Invalid DB backup block identifiers (header %%, data %%).
Cannot read the database block from the flash since the memory resources for
read are still occupied. Header/data are for internal use.

Error #2203 All backup blocks in flash were removed since there is no valid ladder backup
table (entry %%, err %%).
The ladder's BlocksToBackUp table is invalid. entry/err are for internal use.

Error #2204 There is no backup block by the name %% to remove from flash.
Check theBlocksToBackup table that you defined.

Error #2205 Failed to prepare block %% for DB backup storage.

Error #2206 Failed to store DB backup block %% in flash.

Failed to write the database backup block number %% to flash.

429
 Error Messages

Error #2207 There is a mismatch between block identifiers used for backup and block
identifiers in ladder's backup table.
(table: %%<->%%, first column: %%<->%%, #columns: %%<->%%, first row:
%%<->%%, #rows: %%<->%%)
1st parameter in each %%<->%% pair is the block identifier used for backup,
2nd is block identifier in current ladder's 'BlocksToBackUp' table.

Error #2208 System is going to reset while block %% is used by an active %% operation.

Error #2209 There is more than one backup block defined for the same table.
(Block = %%, Duplicated = %% is reset and ignored).

Error #2210 Backup block %% has invalid identifiers in 'BlocksToBackUp' data base table
(%% %% %%)

Error #2211 Backup block %% was never restored from flash nor stored during application
run, therefore can not be restored.

Error #2212 Backup block %% can not be stored due to column %% memory overflow.

Error #2213 Backup block %% can not be restored due to column %% memory overflow.

Error #2214 Backup block %% was removed from flash (reason: %%).

Error #2215 Block %% does not exist, therefore can not be stored (#blocks: %%).

Errors #3000-3999 are used for MOSCAD NFM.

Error #4000: NTP error %%

Internal error in the NTP process such as lack of memory that may prevent it
from running and may require restart. This error may indicate bad configuration
parameter. Consult product support.

Error #4001: Failed connect NTP to timer

Internal software error. Contact product support.

430
 Error Messages

Error #4002: Failed initiating NTP (code %%)

An error occurred while starting the NTP process. It could have been caused by
bad parameters in the NTP advanced site configuration parameters or by lack of
memory. Contact product support.

Error #4004: Failed allocate %% bytes, NTP is being held

This may indicate a memory problem and should not occur. Check your
memory/application needs and reduce them, or contact product support.

Error #4006: NTP process has halted (code %%). Restart unit to let it resume
An internal error occurred in the NTP process such as lack of memory that
prevents it from continuing to run. May indicate bad NTP server. Consult
product support.

Error #4007: NTP sync lost for %% seconds after %% seconds being in sync.
Latest clock offset %% seconds
The NTP process has lost synchronization with its servers. This error is
produced based on the user-defined settings in the NTP site configuration
parameters ‘Max sync offset in msec’ (default 0= offset between RTU and
server is not checked) and ‘Time sync lost before declare ‘no sync’ in sec’
(default = 120). This error will typically appear when using GPS in an RTU that
lost connection with its satellites. To prevent this error from being logged, set
the advanced parameter ‘Notify error logger when losing sync’ to No in the site
configuration.

Error #4008: NTP sync lost after %% seconds being in sync because no system peer.
The NTP process has lost synchronization with its servers because of the lack of
connection with another NTP server or a GPS.

Error #4030: Invalid access code to logging flash %%.

May indicate system software error. Consult product group

Error #4031: Logflash operation (%%) failure: %%.

Operation to the logging flash has failed. See error codes in the ‘C” Toolkit for
MOSCAD Family RTUs manual.

Error #4100: Failed to load FPGA file. Radio & IO's are not supported.
Please contact the product group.

431
 Error Messages

Error #4101: Failed to read\check ID from board. Radio & IO's are not supported.
Please Contact the product group.

Error #4102: Conflict between site configuration ID & MAIN board ID . Radio & IO's are not
supported.
Check site configuration setting.

Error #4103: Conflict between site configuration ID & EXPANSION board ID . Expansion is
not supported.
Check site configuration setting.

Error #4104: Fail in calling build routine - %% of port %%

The specified communication port failed to start due to configuration failure or
due to hardware mismatch. Check the port configuration and the physical port.

Error #4105: Failed to find build routine's %% driver of port %% in the drivers list.
The plug-in port will not start due one of the following problems:

1. Piggyback does not support the requested driver

2. Build routine not supported

3. Piggyback is empty.

4. Wrong port number

5. Fail to read data from piggyback

6. Size of file in e^2 is out of range

7. General piggyback read error

Error #4106: No DNS Get HostbyName specified with no DNS Servers on port %%
DNS Get HostbyName in not specified in configuration file. Check the port
configuration.

Error #4107: No IP Address specified for port %%

IP Address in not specified in configuration file. Check the port configuration.

Error #4108: Missing LINK_NAME/LINK_NAME_0 for port %%

LINK_NAME is not specified in configuration file. Check the port
configuration.

Error #4109: Main board ID is invalid, Radio & IO's are not supported
Contact product support.

432
 Error Messages

Error #4110: Expansion board ID is invalid or invalid main & expansion boards combination
Only main will be supported, check your expansion board.
Check your expansion board.

Error #4111: Failed build device %% error %% (where device is numeric value and error is
the unique text-reason for failure)
A failure occurred when running the MDLC driver service, as a result of
parameters mismatch or lack of resource. The explanation that follows the
message explains the cause of the problem. Contact product support.

Error #4200: Failed to deregister application sockets after %% ms.

PureIP only – For internal use.

Error #4300: Illegal input parameters in I2C send / receive request:

Device key address: %%
Buffer address : %%
Data length : %%
Internal software message

Error #4320: Illegal peripheral id in SPI send / receive request: %%.

Internal software message

Error #4321: Illegal input parameters in SPI send / receive request:

Device key address: %%
Tx Buffer address : %%
Rx Buffer address : %%
Data length : %%
Internal software message

Error #4400: Pointer to NULL in routine - %%

May indicate software error.

Error #4401: prv_ipport_get_device_name bad device ID - %%

The specified Ethernet port device ID is not supported by the current firmware
or the specified device ID is jammed.

Error #4402: ifunit() fail to get device ptr,device name - %%

The specified Ethernet port device name is not supported by the current
firmware or the specified device name is jammed.

Error #4404: Got unknown device name type - '%%'

The specified Ethernet port device name type is not supported by the current
firmware or the specified device name type is jammed.

433
 Error Messages

Error #4405: muxDevLoad failed for device %% %%

Failed to start the Ethernet port.

Error #4406: muxDevStart failed for device %% %%

Failed to start the Ethernet port.

Error #4407: ipAttach() has failed on %%, error - %%

Failed to start the Ethernet port.

Error #4408: ifMaskSet() has failed on %%, ipMask=%8.8lx, error - %%

Failed to set the subnet mask for the Ethernet port.

Error #4409: ifAddrSet() has failed on %%, ipAddress=%%, error - %%

Failed to set the IP address for the Ethernet port.

Error #4410: routeAdd() has failed. Subnet - %%, GW - %%, error - %%.
Fail to add a router to the route table.

Error #4411: Port index is out of range - %%, max port index is - %%
The port index does not match this hardware platform or the index is jammed.

Error #4412: Bad port index - %%

The port index does not match this hardware platform.

Error #4413: Key - '%%' not found in section - '%%' in configuration file
The specified key was not found in the configuration file.

Error #4417: Port %% is HW empty

Trying to configure the IP port while it is physically does not exist. Probably
due to mismatch between the configuration file and the hardware platform.

Error #4418: Fail to start SCCFCC on device - %%

Ethernet port will not start.

Error #4419: Fail to start IP device on port - %%, IP - %%, Mask - %%, GW - %%
Ethernet port will not be configured.

Error #4420: Fail to get board type

Could not get board type. The firmware probably does not match the board
type.

434
 Error Messages

Error #4421: Fail to check SCC2 device

Failed to check the initalization fucntionality of the Ethernet port.

Error #4422: Fail to check SCC3 device

Failed to check the initalization fucntionality of the Ethernet port.

Error #4423: Fail to check FCC1 device

Failed to check the initalization fucntionality of the Ethernet port.

Error #4424: Bad board type - %% or type is not supported by this software.
Either the specified board type is invalid or is not supported by the software.

Error #4426: Fail to start dhcp client on port - %%

Could not start DHCP client on the specified port. Check the port
configuration.

Error #4427: hostAdd() has failed. GW - %%,Addr - %%,error - %%

May indicate software error.

Error #4428: ifunit fail to get pointer to interface - %%

May indicate software error.

Error #4450: VxWatchdogManager device creation failed.

Indicates software error in system start-up. Consult product group.

Error #4451: VxWorks Watchdog timer creation failed.

Indicates software error. Consult product group.

Error #4452: VxWatchdogManager memory allocation failed.

Indicates lack of RAM memory in the system. Consult product group.

Error #4453: VxWorks Watchdog timer creation, during initialization, failed.

The allocation of a single VxWorks watchdog timer has failed.

Error #4454: VxWatchdogManager memory allocation, during initialization, failed.

The allocation of a single VxWorks linked list node for storing a single
watchdog has failed.

Error #4540: Fail to disable pre-input filter

Indicates software error. This filter is used to filter IP addresses.

435
 Error Messages

Error #4541: Fail to disable input filter

Indicates software error. This filter is used to filter IP protocols.

Error #4542: Fail to enable pre-input filter

Indicates software error.

Error #4543: Fail to enable input filter

Indicates software error.

Error #4544: Fail to create filter group in routine %%

Failed to set Firewall filter rules.

Error #4545: Fail to set rule %% in routine %%*/

Failed to set a Firewall filter rule.

Error #4546: Fail to create rule in routine %%

Failed to set a Firewall filter rule.

Error #4547: Fail to set action %% for rule %%

Failed to set a Firewall filter rule.

Error #4548: Fail to set TCP Filter rules.

Failed to set a Firewall filter rule.

Error #4550: Memory allocation error while creating F_EVNT device.

Not enough RAM memory at startup to allocate for fast event mechanism.

Error #4551: VxWorks resource allocation error while creating F_EVNT device.
Not enough RAM memory at startup to allocate for fast event queues.

Error #4552: VxWorks resource allocation conflict while creating F_EVNT device.
There is a conflict between actual maximum item size owned by FASTEVNT
resource and initial F_EVNT device allocation.

Error #4553: Fast event msgQ receive error (unknown event size. error = %%).
An unidentified event (unknown event data size) is waiting in the fast event
message queue. Software error.

Error #4554: Fast event unknown trigger type %%

The incoming fast event relates to an unknown trigger type. Software error.

436
 Error Messages

Error #4555: Fast process function %% execution time exception %%

The execution of a fast process exceeded the maximum execution time specified
in the 'Max run time duration in micros' site configuration advanced parameter.

Error #4556: Enable IO trigger error: Retcode = %%. Rack %% Module %% Input %% Fast
Process %%
An error occurred when enabling a digital input trigger in the specified location
in the RTU from the specified fast process.

Error #4557: Disable IO trigger error:Retcode = %%. Rack %% Module %% Input %% Fast
Process %%
An error occurred when disabling a digital input trigger in the specified location
in the RTU from the specified fast process.

Error #4558: IO event fast process error. Fast process address %% Trigger's RAM addr. %%
Trigger's bit no. %%
The specified fast process associated with the specified trigger (I/O event)
executed with errors.

Error #4559: Enable delay trigger failure. Delays linked list is full
Cannot enable another new delay trigger because the delays linked list in RAM
memory is full. Increase the 'Number of delay triggers' site configuration
advanced parameters.

Error #4560: Failed to perform scan out for fast event process %%
The 'scan out' in the executed fast process failed.

Error #4561: IO triggers data base is invalid %%

Failed to access I/O triggers database to locate a certain trigger's data.

Error #4562: While fast process address (%%) execution, error %% occured, for trigger type
%% Rack %% Module %% Index %% Direction %%
Errors occurred during fast process execution. Cannot interrupt execution, so
the error alerts will be reported after execution is complete.

Error #4563: Enable PushButton trigger error: Retcode = %%. Fast Process %%
An error occurred when enabling a pushbutton digital input trigger associated
with the specified fast process.

Error #4564: Disable PushButton trigger error:Retcode = %%. Fast Process %%

An error occurred when disabling an existing enabled pushbutton digital input
trigger associated with the specified fast process.

437
 Error Messages

Error #4565: Failed to send fast event message to incoming fast events Queue. Error = %%
An incoming fast event could not be added to the fast event queue.

Error #4566: Events message queue is not empty during reset load (Num Events = %%).
Events will be deleted.
Events in events message queue will be deleted due to new ladder application
download. All the events should have been processed prior to handling the
download of the new ladder, therefore, there is a software error.

Error #4567: Failed to remove events message queue (err = %%).

Tried to delete existing events in events message queue due to new ladder
application download, but failed. Software error.

Error #4600: Checksum error. header checksum is - %% , Found - %%.

Piggyback was not burned or E^2 is jammed.

Error #4601: SPI timeout error.

Problem with SPI , If this problem occurs often, please contact product support
group.

Error #4602: Failed to burn eeprom.

For Motorola factory usage.

Error #4603: Failed during file/text processing - probably - key not found.
Piggyback was not burned successfuly or E^2 is jammed.

Error #4604: Driver ID syntax error. atol() parse error.

Piggyback was not burned successfuly or E^2 is jammed.

Error #4605: Unsupported port id.

Firmware may not support this type of plug-in (piggyback) port.

Error #4700: PORT %%, DHCP client failed to retrieve option %%, error %%.
Information was missing in the DHCP server response for the specified port.

Error #4701: PORT %%, Server failed to update DNS with FQDN , rcode1 - %%,rcode2 -
%%.
The DHCP server did not update the DNS with this port's FQDN.

Error #4702: PORT %%, Server refuse to client update.

DHCP server refused for FQDN update by client.

438
 Error Messages

Error #4703: Pointer to NULL. Function - %%, Pointer - %%.

Internal software error.

Error #4704: Fail to get pointer to port - %%.

Internal software error.

Error #4705: Fail to take a container semaphore. Port - %%. Error - %%.
Internal software error.

Error #4706: Fail to give a container semaphore. Port - %%. Error - %%.
Internal software error.

Error #4707: Domain name len %% and Zone name len %% are bigger than the max Domain
name len %%.
The length of the domain name is out of range. Please use a shorter name.

Error #4708: Option - '%%' len - %% is bigger than max option len - %%.
The length of the specified DHCP option data is out of range. Please use a
shorter string.

Error #4709: Fail to build fqdn for domain name %%. Err - %%.
Could not build a FQDN for the specified domain name.

Error #4710: Fail in call to DHCP bind. Err - %%.

Failed to launch DHCP.

Error #4711: dhcpcInit returned NULL. Interface - %%, Auto Falg - %%.errno - %%.
Error in initializing DHCP.

Error #4712: Fail to add dhcp option to request. Option - %%. errno - %%.
Failed to request the specified DHCP option.

Error #4713: Fail to create mutex semaphore for port - %%. . errno - %%.
Internal software error.

Error #4714: Fail to set dhcp call back routine for port - %%. . errno - %%
Failed to set DHCP routine for the specified port.

Error #4715: Fail to set dhcp cach hook routine for port - %%. . errno - %%
Failed to set DHCP routine for the specified port.

439
 Error Messages

Error #4800: Fail to set DNS server. Name - %%. Address - %% , %% , %% . Errno - %%
Failed to set the specified DNS server.

Error #4801: DNS client init fail int call to 'resolvInit'. Errno - %%
Failure when initializing the DNS client.

Error #4802: DNS client - Create SEM failed. Errno - %%

Internal software error.

Error #4803: No DNS server specified or learned on port %% cannot resolve %%

No DNS server was defined in the specified port’s configuration or could be
learned from the infrastructure. The specified domain name is configured in the
IP conversion table or API, but cannot be resolved. Check the port
configuration.

Error #4804: No DNS server specified or learned on any port cannot resolve %%
No DNS server was specified in the port configuration or could be learned from
the infrastructure for any port. The specified domain name is configured in the
‘C’ Toolkit API, but cannot be resolved. Check the port configuration.

Error #4811: Config - in section %% the key %% is missing

The configuration file is missing data. File may have been corrupted.

Error #4812: Warning. Config - section %% wasn't found in configuration file.

The configuration file is missing data. File may have been corrupted.

Error #4813: Warning - Key %% from section %% is missing. Took it from default. Value is -
%%
The configuration file is missing data. File may have been corrupted.

Error #4900: RTC: Could not send or receive information by I2C. Internal error code = %%.
General RTC error. Could not send or receive information to/from the real time
clock device via I2C.

Error #4901: RTC: Internal RTC time stamp is not valid. Failed to read system time from
RTC.
Time stamp information stored in RTC device is not valid. Failed to read system
time from RTC. RTC internal memory will be dumped.

Error #4902: RTC: Failed to lock semaphore needed for RTC internal control. Internal error
code = %%.
Failed to lock semaphore needed for RTC internal control. Current operation
aborted.

440
 Error Messages

Error #4903: RTC: Failed to update the RTC with the system time (set seconds). Internal
error code = %%.
Failed to update the RTC with the system time. The device may be out of sync.

Error #4904: Can not get temperature info while trying to control RTC battery charge.
Could not read temperature from main power supply. This reading is needed for
Lithium battery charge control. Charging state was not changed. Could be due
to bad communication with the power supply.

Error #4905: RTC Battery start/stop charge command has failed.

Failed to initiate Lithium battery charge control command. Charge or Stop-
charge command issued in order to control Lithium battery charge failed.

Error #4906: RTC Battery charge was stopped due to temperature limits.
Lithium battery charge (RTC battery) was stopped as temperature exceeded
charging temperature limits.

Error #4907: Unstable RTC clock was detected probably due to battery failure. RTC time may
not be accurate.
RTC detected that its clock source was not stable (or even available) during its
operation. It is probably due to battery failure. Time information stored in RTC
device may be incorrect. Connect the RTU to the main power in order to charge
the battery.

Error #4910: Startup - Call to %% Failed, Error %%

Failed to start up the CPU due to bad configuration or software error.

Error #4911: Configuration file was deleted due to failure in startup. Rolling back to the last
configuration file.
Failed to start up the CPU due to bad configuration or software error. The
previous configuration file will be used.

Error #4930: Invalid IO configuration (Return code %%).

STS downloads a configuration file (*.cfi) with an invalid IO section.

Error #4931: The connection to IO module was lost (Rack-%% Module-%%).

The system lost communication to the specified IO module. Module is missing
or out-of-order.

Error #4932: The communication to IO module was renewed (Rack-%% Module-%%).

The communication was renewed to a module that lost communication.

441
 Error Messages

Error #4933: An expected IO module was missing during startup (Rack-%% Module-%%).
The user defined an I/O module in STS, but the module was missing from the
RTU when the system restarted after downloading the configuration.

Error #4934: The system found a conflict between the PDV data and IO configuration.
When STS downloads a ladder or ‘C’ application, it also downloads predefined
I/O module values file (.ios) . The validation of this file failed.

Error #4935: Fail to load PDV file (Return code %%).

The system failed to check the predefined I/O module values file (PDV) file,
due to a lack of resources.

Error #4936: Actual and Desired values of DO are not equal (Rack-%% Module-%%).
Mismatch between digital outputs (DO) and back indications (BI) because of a
hardware failure.

Error #4937: Module fail to recover - Fail to read ID (Rack-%% Module-%%).

The communication to a specific I/O module was renewed but the system could
not read the module information.

Error #4938: Unexpected module type %%, Expected type %% (Rack-%% Module-
%%).
The system identified a module that does not match the rack/module slot
definition.

Error #4939: Fail to download a new FPGA file to Rack %% Module %%

The system failed to burn a new FPGA file to the specified IO module.

Error #4940: Fail to backup FPGA file from Rack %% Module %%

The system failed to upload the current FPGA file (for backup purposes before
downloading the new I/O FPGA software) from the specified I/O module.

Error #4941: Fail to download backup FPGA file to Rack %% Module %%

The system failed to restore the original FPGA file for the specified I/O module,
after it failed to load the new FPGA file.

Error #4942: FPGA file number mismatch, Expected %% but given %% Rack %% Module
%%
The STS tries to download an I/O FPGA file that is not compatible to the
module type for the specified module.

Error #4943: No 'operate' after 'select' ('select' timeout elapsed). All selected SBO were reset.
For future release.

442
 Error Messages

Error #4944 24V PS reached current limit - PS %% Rack %% Module %%

A current limit problem in the specified 24V power supply for the specified I/O
module.

Error #4945 24V PS over voltage - PS %% Rack %% Module %%

An overvoltage problem in the specified 24V power supply for the specified I/O
module.

Error #4946 Float PS reached current limit - Rack %% Module %%

A current limit problem in floating power supply for the specified I/O module.

Error #4947 Float PS over voltage - Rack %% Module %%

An overvoltage problem in the floating power supply for the specified I/O
module.

Error #4948 Malfunction in 12V main Rack %% Module %%

The 12V DO is off but should be on. (Source is 12V main.)

Error #4949 Malfunction in 12V relay Rack %% Module %%

The 12V DO is off but should be on. (Source is 12V relay.)

Error #4950:: Power Manager: MessageQueueReceive() failed.

Internal software message

Error #4951:: Power Manager: MessageQueueSend() failed.

Internal software message

Error #4952: Power Manager: Invalid messageQueue ID read from Queue.

Internal software message

Error #4953: Power Manager: SetMainPSElement() failed.

Set operation on the Main PS failed.

Error #4954: Power Manager: Buffers pool is empty

Internal software message

Error #4955: Power Manager: GetMainPSElement() failed.

Get operation on the main power supply failed.

443
 Error Messages

Error #4956: Power Manager: Slot PS Change (plugged in / out ):

Power Supplier ID : %%
Activity type : %%
Failure of main power supply input.

Error #4957: Power Manager: Switch On the main PS failed.

Power Supplier ID :%%
Switch Name :%%
The specified switch on the main power supply failed.

Error #4958: Power Manager: HandleMainPSInterrupt() failed.

Internal software message

Error #4960 12V relay is off (Check 12V jumper in power supply)
The 12V DO jumper is missing in the main power supply.

Error #4961 The system can not support the IO module driver number.
Contact product support.

Error #4962 The system can not support the IO module version number.
Contact product support.

Error #4963 Standby CPU failed to get IO information at startup.

At startup, the active CPU started negotiation with the standby peer but did not
finish it. Contact product support.

Error #4964 IO data update failure (redundancy).

During hot swap, the active CPU started negotiation with the standby peer but
did not finish it. Contact product support.

Error #4970: Failed to calculate calendar time while converting ticks to vxWorks timespec
structure
Could not convert time.

Error #4980: HW_TST: unsupported op-code

Buffer - %%
Unsupported op-code - %%
Bad communication between the STS hardware test and the RTU hardware test.

Error #4981: HW_TST: bad parameter number

Bad communication between the STS hardware test and the RTU hardware test.

444
 Error Messages

Error #4982: HW_TST: work area length error

Op-code - %%
Received length - %%
Bad communication between the STS hardware test and the RTU hardware test.

Error #4983: HW_TST: pres_send_struct error

Communication failure.

Error #4984: HW_TST: pres_abort_session error

Communication failure.

Error #4985: HW_TST: pres_end_session error

Communication failure.

Error #4986: HW_TST: HW_TST: memory allocation error

Internal software error.

Error #4990: Push Button: error during sem take

Error code = %%
Internal software error.

Error #5000: Corrupted heap: Failed free Mblk %%H NetPool %%H Next clBlk %%H
Indicates a software error in the VxWorks Heap. Probably occurred for PPP
when freeing a buffer. Contact product support.

Error #5001: NetPool corrupted cluster %% is %% expected %%

Indicates a software error in the VxWorks Heap. Probably occurred for PPP
when freeing a buffer. Contact product support.

Error #5002: NetPool corrupted cluster %% has netpool %% expected %% Net Pool %%
Internal use only, for when #5001 occurs.

Error #5003: NetPool corrupted cluster head (pClHead) %% is %% expected %%

Internal use only, for when #5001 occurs.

Error #5004: NetPool corrupted cluster %% Cluser %% out of area should be %%

Internal use only, for when #5001 occurs.

Error #5100: Failed connect PPP on port %% could not get an IP Address
The modem or radio failed to provide an IP address to the RTU for the PPP
protocol on the specified port. The PPP port cannot be connected. This is
probably due to bad configuration or lack of registration in the infrastructure.

445
 Error Messages

Check the modem and/or radio configuration. Contact the operator if you do not
see a problem in the RTU configuration.

Error #5101: Failed connect PPP on port %% IP Address in use by other ports.
The modem or radio provided an IP address to the RTU for the PPP protocol on
the specified port. The IP address provided is already set by another modem, so
the PPP port cannot be connected. The IP address provided by radio or modem
must be unique. For example, in the ASTRO IV&D radio, this address is set in
radio’s CPS. Modify the IP address when using more than one radio with the
same RTU.

Error #5102: Failed connect PPP on port %% Modem/radio IP Address in use by other ports.
When a using PPP port, two IP addresses are provided by the modem/radio
during connection for each port: One is the RTU IP address and the other is the
modem/radio IP address. Both must be unique for each port, but in each port
the RTU IP address and the modem/radio IP address can be identical.

For example a G18 modem provides the RTU with the IP address 128.29.31.28
when registering with the operator and also provides the same 128.29.31.28 to
itself. This is permitted in PPP and in this case you can connect another G18
modem on the same RTU in a different port, as it will have a different set of IP
addresses. A Siemens modem (such as MC75.stm) provide 128.29.31.28 for the
RTU as specified by the operator, but its internal IP address is always set to
10.0.0.1. In this case you can connect only one modem to a specific RTU,
because the modem IP address will be the same The same applies to iDEN
modem and some TETRA radios.

Error #5103: Warning: Failed set DNS Server in routing table for
port %% DNS IP Address :%
When using a PPP port, some modems such as G18 and iDEN modems, read the
DNS server list from the modem during PPP connection. This saves the user the
task of configuring DNS if host names are required instead of numeric IP
addresses. This error indicates that the firmware failed to configure those DNS
addresses in the VxWorks internal routing table. so it will not be able to resolve
host names via that PPP port. The PPP connection has completed successfully
regardless of this fact. Contact product support.

Error #5104: Failed allocate cluster size %% from netPool %%

Not enough memory for PPP port. Increase the memory in the PPP advanced
site configuration parameter: ‘Clusters size for PPP ports’ (640K byte by
default.)

Error #5105: PPP Error: %%

Internal problem in PPP port. Contact product Support.

446
 Error Messages

Error #5170 Invalid redundancy roles Peer Role-%% Peer role-%% (None=0, Active=1,
Standby=2) The secondary will try to give up the active role.
After CPU negotiation, both CPUs discover that they are active. In this case the
secondary will give up on being active. Contact product support.

Error #5173 Redundancy FPGA signals error

Error %%
Register %%%%
Am I primary %%
Am I active %%
Is peer active %%
Am I alive %%
Is peer alive %%
The firmware generates this error if for some reason both CPUs are in the same
status (active or standby). In this case the secondary CPU becomes standby
while the primary CPU is active. The error also lists the status of the five
redundancy flags. Contact product support.

Error #5200: Failed to load new burned file %% for C application run.
Failed to load the downloaded C block that supports the C debug process.

Error #5201: Failed to unload C block %%.

Tried to unload a C block due to download of a newer version of the block or
other erase operation, but failed.

Error #5202: Requested to unload C block %% which is not listed as a loaded modules.
Software error. A request was made to unload a C block, but the block is not
listed in RAM as loaded.

Error #5203: Ucall name %% in user jump table is illegal (name too long or includes invalid
character).
The name of the ‘C’ function to be called using Ucall is invalid.

Error #5204: Ucall number %% with name %% is never called from ladder.
Warning. The specified Ucall is never called from the ladder application.

Error #5205: Failed to get the address of ucall name %% found in entry %%
File %% is removed from RTU's flash memory.
The Ucall specified in the user_jump_table relates to a function that is not found
in RTU's run-time code.

447
 Error Messages

Error #5206: Ucall name %% found in entry %% is already used in another C block's user
jump table
File %% is removed from RTU's flash memory.
The Ucall specified in the user_jump_table relates to a function that is already
used in another C block's user jump table.

Error #5207: Failed to find 'user_control_function' in C block %% (err=%%)

File is removed from RTU's flash memory.
The C block does not contain a 'user_control_function' and will be deleted from
the Flash.

Error #5208: Failed to find 'user_jump_table' in C block %% (err=%%)

File is removed from RTU's flash memory.
The C block does not contain a jumptable and will be deleted from the Flash.

Error #5209: Failed to create/access C block %% in memory drive (err=%%)

Could not create/access the C block.

Error #5210: Failed to load C block %% for C application run (err =%%).
The VxWorks operating system failed to load the C block code for running.

Error #5213: Failed to find C object name in C block %% (err=%%)

File is removed from RTU's flash memory.
The C block does not contain the C object name and will be deleted from the
Flash.

Error #5214: Failed to find C object path name in C block %% (err=%%)

File is removed from RTU's flash memory.
The C block does not contain the C object path name and will be deleted from
the Flash.

Error #5215: There is no available entry to store information about loaded C block %%
File is removed from RTU's flash memory.
There is no room in RAM to store the C block indicators. The C block will be
deleted from the Flash.

Error #5216: Failed to set 'loaded' for C block %%

File is removed from RTU's flash memory.
Could not mark the C block as successfully loaded in the Flash. The C block
will be deleted from the Flash.

448
 Error Messages

Error #5217: C block %% failed to pass CRC check.

File is removed from RTU's flash memory.
The C block failed the CRC check and will be deleted from the Flash.

Error #5218: Failed to complete full load procedure for C block %%

System reboot occurred during the download of this C block to the Flash.
Reload failed.

Error #5219 : Failed to unzip C block %% (block's zipped header is invalid. error = %%).
No valid compression header in C block. Could not unzip the block.

Error #5220: Can not load C block %% (MOSCAD_() services used in this block require
RTU's firmware core version = %%).
The ‘C’ block uses a C service which is not supported by this RTU type and
core version. Could not load C block. (ACE)

Error #5221: 'C' core version symbol is missing in file %% (error = %%) .
File is removed from RTU's flash memory.
No ‘C’ core version data found in the downloaded C block. The C block will be
deleted from the Flash.

Error #5222: C toolkit version is missing in file %% (error = %%) .

File is removed from RTU's flash memory.
No ‘C’ toolkit version found in the downloaded C block. The C block will be
deleted from the Flash.

Error #5223: Queue failed (%%) to receive legal message (error = %%)
Debug of C application cannot be properly executed due to message queue
receive operation failure.

Error #5224: Failed (%%) to send legal message to Queue (error = %%)
Debug of C application cannot be properly executed due to message queue send
operation failure.

Error #5225: C debug task %% semaphore operation failure (semaphore status = %%)
Debug of C application cannot be properly executed due to semaphore operation
failure.

Error #5226: Failed to remove 'Undebug' file %% from flash memory

The C block which indicates the 'end of debug' cannot be removed from the
Flash memory.

449
 Error Messages

Error #5227: Failed to properly program C block %%

Failed to replace the existing (in Flash) C block with the newly downloaded
version of C block.

Error #5228: Failed to create memory drive from memory %% (size = %%)
Could not create a memory drive to load the ‘C’ blocks for running.

Error #5229: Failed to uncompress C block %% (uncompress size = %%, error = %%)
Uncompression of downloaded (compressed) C block in RAM for running
failed.

Error #5230: C block %% load failure. (C block was successfully loaded in the past)
Could not load the C block failed with the current firmware version. C block
was successfully loaded with an advanced firmware version.

Error #5231: User Application Warning:

C application error occurred. The user classified the C application error as a
warning.

Error #5232: User Application Message:

C application error occurred. The user classified the C application error as a
message.

Error #5233: No room to allocate space for C block/s loading.

The ‘C’ blocks burned in the RTU are loaded to run in alphabetical order. There
is not enough memory to allocate space to sort the block names. Internal error.

Error #5301: Data base table %% column %% has an unexpected column data type %%
related to the column's type %%.
Please contact ACE3600 support.
There is a mismatch between a ladder table’s specific column type (real, real
parameter, long value, etc.) and the column data type which is a 4-byte data type
(long/float).

Error #5302: Get Frame ID from the Expansions Reserved Values table failed: table not
found
The Expansions Reserved Values table was not found in the application
database. Check the the ladder application is V13.50 or higher.

Error #5303: Set Frame ID in the Expansions Reserved Values table failed: table not found
The Expansions Reserved Values table was not found in the application
database. Check the the ladder application is V13.50 or higher.

450
 Error Messages

Error #5304: Get Frame ID from the Expansions Reserved Values table failed:Got
unexpected Frame ID (%%)
Invalid frame ID was passed to the GtExDt ladder call or
MOSCAD_GetExpData ‘C’ function. Check the application.

Error #5305: Set Frame ID in the Expansions Reserved Values table failed: Attempt to set
unexpected Frame ID (%%)
Invalid frame ID was passed to the GtExDt ladder call or
MOSCAD_GetExpData ‘C’ function. Check the application.

Error #5306: Set Frame ID in the Expansions Reserved Values table failed: Fail to get
Expansions Reserved Value (index %%)
Internal error. Contact MOSCAD support.

Error #5307: Set Frame ID in the Expansions Reserved Values table failed: Fail to get
Expansions Reserved Flag (index %%)
Internal error. Contact MOSCAD support.

Error #5308: Set Frame ID in the Expansions Reserved Values table failed: Expansions
Reserved Flags table not found
Internal error. Contact MOSCAD support.

Error #5309: Set Aux ID in the PS tables failed: PS1 or PS2 table not found
Internal error. Contact MOSCAD support.

Error #5310: [Ladder application and C application | Ladder application | C application] run is
renewed after being stopped for 1 minute ---> 1 minute is the timeout set in
configuration.
If the user application is stopped in the Hardware Test and then run
automatically by the firmware after the timeout expires a message will specify
which (ladder, C application or both) application was stopped and then re-run.

Error #5400: SMA ONLINE ERROR:

Fatal !!! Not enough work space for Core Dump Upload Appl.
Available space transferred for Core Dump Upload Appl. - %% bytes.
Minimum space required for Core Dump Upload Appl. - %% bytes.
Core Dump Upload file is too big. Please contact product support.

Error #5401: SMA ONLINE ERROR:

%%
This header is used for many SMA errors and messages. The associated text
explains the specific circumstances.

451
 Error Messages

Error #5410: Fail to end 'Firmware Download Session',

Timeout in waiting for "BURN" message from STS.
RTU will reset in 1 Second and roll back to its previous firmware.
Please contact product support.

Error #5500: Main CPU has rejected a request coming from Expansion Module %% having
IOEM Identity %% because it already serves another Expansion Module with
IOEM Identity %% having the same ID.
Wait 1 minute after disconnecting an expansion module before replacing it with
another expansion module with the same frame ID.

Error #5501: Main CPU has rejected a request coming from Expansion Module %% with an
IOEM Identity %% because this channel already serves another Expansion
Module %% having IOEM Identity %%.
May indicate software problem. Contact product group.

Error #5502: Missing UDP or TCP port numbers from configuration. Cannot detect frames.
May indicate software problem. Contact product group.

Error #5503: Missing IP address or network mask from expansion port configuration. As a
result cannot detect Expansion Modules.
Check that the IP address and network mask was correctly entered, and is not 0.

Error #5504: Failed to initialize expansion port for IP address %% and network mask %%. As
a result cannot detect Expansion Modules.
Check that the IP address and network configuration were correctly entered.
Check cable connections.

Error #5505: Received a request from unexpected Expansion Module %%. Check I/O
configuration and Expansion Module's rotary switch.
Check that the frames in the I/O configuration were correctly entered and check
the setting of the module’s rotary switch.

Error #5506: Frame %% was configured but was not connected during startup. I/O modules
configured for that frame are not available.
When the main CPU is powered up, it checks if configured frames are ready
during startup. If not, it sends this warning for each missing frame.

Error #5507: Frame %% has high communication BER or has just been disconnected (%%).
When an I/O expansion frame is disconnected, the main CPU sends this warning
that the frame has been disconnected, including the string which describes the
reason for the disconnect.)

452
 Error Messages

Error #5508: Frame %% communication BER is OK or has just been connected.

When an I/O expansion frame is connected, this message is logged. This occurs
in two cases:

- A frame that was missing during startup and is now connected, or

- A frame that was disconnected and reconnected.

Error #5509: Failed to allocate IP address for one or more frames, e.g. frame %% with IP
address %%. Check Expansion port IP address and network mask.
This error message is a configuration error caused by the user. For example if
the user defines a network mask of 255.255.255.0 and an IP address
10.100.100.250. Frame ID 5 would have to be 10.100.100.255 which is illegal.
Frame ID 6 would be 10.100.101.0 which is both illegal and outside the network
mask 10.100.100.xxx. So the user is requested to modify the frame ID or the IP
address of expansion port or the network mask. Note: The user may specify in
the I/O Expansion Manager advanced parameter, the first IP address. If this
parameter exists, this error refers to this parameter rather than the expansion
port IP address.

Error #5510: User has changed Expansion Module rotary switch value and it is ignored. Its
original value is %%.
Check that the frames in the I/O configuration were correctly entered and check
the setting of the module’s rotary switch.

Error #5511: User has reset Expansion Module rotary switch to its original value %%.
Informative message only.

Error #5512: Received a redundancy request from active CPU for unexpected Expansion
Module %u. Check I/O configuration of both CPUs.
The standby CPU was configured with different frames than the active CPU.
This error also may appear if the standby CPU is powered AFTER the active
CPU is running, and was configured using auto-recognition, or has erased its
configuration.

Error #5513: Frame %% firmware version %% is different than expected %%. Restarting
frame.
There is a mismatch between the firmware versions of the primary and
secondary CPUs. Confirm the firmware versions using the STS field view and
download firmware versions as necessary.

Error #5600: Security log - message queue has reached its full capacity. Can not place
current message to the security log.
There is a security problem. Read the security log and find the problem.

453
 Error Messages

Error #5601: Security log - semaphore has been held for more than 60 sec. Can not place
current message to the security log.
Contact product group.

Error #5602: Security log - heap is full. Can not place current message to the security log.
Contact product group.

Error # 5603: Security log - severity list is full. This message can not be retrieved from user
application.
Check the user ladder application. The application is not calling GetSecLog.

Error # 5604: Security log - record encryption error. This record was not added to security log
file.
Contact product group.

Error # 5605: Security log - Not enough room in partition to push new record (size = %%) to
security log. Can not place current message to the security log.
Contact product group.

Error # 5606: Not enough room to add event (size = %%) to security log's filtering list.
Contact product group.

Error # 5607: Security log - Not enough memory to alloc the new user severity list.
Contact product group.

Error # 5608: Security log - Not enough memory to alloc a new element in the user severity
list.
Contact product group.

Error # 5700: Wrapper function %% not supported.

Internal use.

Error # 5701: OpenSSL error:

%%
Internal use.

Error # 5750: Dynamic IP routing table became full could not add host IP address %%
The dynamic IP routing table is full. Until an entry is removed or the size is
increased, no new/learned IP addresses can be added. Temporarily cannot
transmit to an RTU/host with an IP address that is not on the list. See the Size
of dynamic IP routing table Advanced Parameter.

454
 Error Messages

Error #5800: USB Host has detected a device on port %% which was not configured. Device
is %%. Please check your configuration.
The user has connected a device to a USB host port which was not configured.
In the USB standard, each device has vendor and product IDs. For this release
14.00 only MotoTrbo mobile radio (4128) and portable radio (4129) are
supported. Their vendor ID is 3245 Motorola CGISS. FUTURE USE.

Error #5801: USB Host has Detected a device on port %% which is configured but is
connected on a different location than expected. Device is %%. Please check
your configuration.
The user has connected the radio device to the wrong port, different than the one
configured in the STS. Because the two ports are connected as a USB root hub,
ACE3600 was able to detect that the user connected the device, and it turns on
its LED, even though it is on a different port than the one configured.

Error #5802: USB device port is not supported.

Internal use.

Error #5900: USB Host has failed connect to radio via remote NDIS on port %% could not get
an IP Address.
Problem getting an IP address from the radio. The MotoTrbo port uses Remote
NDIS protocol, and learns its IP address from the radio via DHCP. This error
shows it is unable to complete connection with the radio, because of no IP
address. This may denote a problem in the radio, or in the ACE firmware.
Contact MOSCAD support.

Error #5901: USB Host has failed connect to radio via remote NDIS on port %% learned IP
Address is in use by other ports. Please re-configure the radio with a correct IP
address.
The MotoTrbo port uses the Remote NDIS protocol and learns its IP address
from the radio via DHCP. This error means the user has connected several
radios having the same IP address. This IP address is internal between the
RTU/IPGW and radio and has a network mask of 255.255.255.0.
Using the CPS, the user can configure an IP address for the radio, e.g.
192.168.10.1. The RTU/IP address is plus one, e.g. 192.168.10.2.
If user configures in the STS more than one radio connected to THE SAME
RTU/IPGW, each should have a different IP address on a different network
mask, e.g. 192.168.10.1 and 192.168.11.1. If only a single radio is connected (to
a different RTU/IPGW), all radios can have the same IP address (but with a
different radio ID). Again, this IP is internal and does not reflect the actual IP
over the air.

455
 Error Messages

Error #5902: USB Host has failed connect to radio via remote NDIS on port %%. Radio IP
Address is in use by other ports. Please check radio unit ID and ACE
configured IP addresses.
This error is the same as previous one 5901, only it refers to the radio’s internal
IP address, instead of the one learned from it.

Error #5903: Configuration mismatch - USB Host is not supported on this board.
This error denotes a hardware issue with the board, unable to communicate via
PCI with the USB host controller. Only specific boards support USB Host. If
your board has a USB host port, contact MOSCAD support.

Error #5904: MotoTrbo radio on port %% does not respond in USB data channel and may
need to be powered off and on.
This error denotes a software issue with MotoTrbo radio. Old versions of the
MotoTrbo radios may experience a fault, where the ACE3600 is unable to
complete connecting with them over RNDIS and the radio needs to be restarted.
Check you have the recent firmware of the radio.

Error #5950: Security policy file was rejected.

The policy file is invalid (e.g. parameters are missing.) Contact product
support.

Error #6000 Security chip Tamper has occurred. Tamper code %%.
All encrypted files will be erased. See the Dedicated Security Repository
section of the ACE3600 Advanced System Security User Guide.

Error #6001: Security Chip Serial number is invalid.

Contact product support.

Error #6002: Security chip has invalid key.

Contact product support.

Error #6003: Security chip key was not generated.

Contact product support.

Error #6050: File decryption has failed.

If the problem appears after file download, try to re-download the file. Contact
product support.

Error #6100: Security key for file encryption was not loaded.
Contact product support.

456
 Error Messages

Error #6150: Authentication server msgq has failed.

Contact product support.

Error #6151: Authentication server minisession communication has been failed.

In Site configuration->Advanced->Minisession, increase the RTU to RTU
number of boxes for Minisession Authentication Server and Minisession
Authentication Client. Contact product support.

457
 Error Messages

Error #6250: Failed to create communication session for diagnostics purpose [reason=%].

Error #6251:

Error #6252: Failed to forward Diagnostics request to diagnostics server [reason=%%].

Error #6253: Failed to receive specific diagnostics reply [reason=%%].

Error #6254: Failed to terminate communication session [reason=%%].

Error #6256: Failed to create IRMIPC instance [reason=%%].

Error #6257: Failed to connect to Diagnostics daemon [reason=%%].

Error #6258: Failed to build message to send to Diagnostics daemon [reason=%%].

Error #6259: Failed to send message to Diagnostics daemon [reason=%%].

Error #6260: Failed to receive IRMIPC message from Diagnostics daemon [reason=%%].

Error #6261: Failed to parse IRMIPC message into Diagnostics reply [reason=%%].

Error #6262: Failed to disconnect from diagnostics daemon [reason=%%].

Error #6263: Failed to communicate with diagnostics daemon [reason=%%].

Error #6267: Failed to update transaction status %% in transactions data base.

Error #6268: Failed to allocate memory size %% for diagnostics reply to store in transactions
data base.

Error #6300: MODBUS daemon creation failed

Error #6301: Could not open data base: %%

Error #6302: MODBUS allocation failed

Error #6303: MODBUS mapping allocation failed

Error #6304: TCP select failed, errno: %%

Error #6305: Serial MODBUS configuration failed, is driver 485: %%, errno: %%, ctx s: %%

Error #6306: MODBUS parsing unit id list file failed

Error #6307: MODBUS unit id list allocation failed

Error #6500: Too many active applications: %%

Error #6501: Could not fork the application. Err=%%

458
 Error Messages

Error #6502: Could not set sid . Err=%%

Error #6503: Could not change dir to root

Error #6504: Could not create irmipc. Err=%%

Error #6505: Could not connect to irmipc server. Err=%%

Error #6506: Failed to receive message from IRMIPC. Err=%%

Error #6507: Parsing message failed

Error #6508: Parsing of the passed command line failed: %%

Error #6509: Error Logger parsing parameters Failed: %%

Error #6510: Diagnostics parsing parameters Failed: %%

Error #6511: Date&Time parsing parameters Failed: %%

Error #6512: Failed to create communication wrapper handle of type %%

Error #6513: Failed to start communication handshake for site %%, link %%, service %%

Error #6514: Failed to initialize before calling MDLC comm. application for type %%

Error #6515: Failed to initialize before binding to comm. session for type %%

Error #6516: Failed to bind to comm. session for type %%

Error #6517: Failed to parse MDLC monitor command=%% [file=%%, reboot=%%, err=%%]

Error #6600: Too many active applications: %%

Error #6601: Could not fork the application. Err=%%

Error #6602: Could not set sid . Err=%%

Error #6603: Could not change dir to root

Error #6604: Could not create irmipc. Err=%%

Error #6605: Could not connect to irmipc server. Err=%%

Error #6606: Failed to receive message from App_manager.

Error #6607: Unable to run application

Error #6608: Parsing of the passed command line failed: %%

Error #6609: Error Logger parsing parameters Failed: %%

459
 Error Messages

Error #6610: Diagnostics parsing parameters Failed: %%

Error #6611: Date&Time parsing parameters Failed: %%

Error #6612: Unable to create commwrapper

Error #6613: Application is busy with another session

Error #6800: Date and time master failed to update transaction %% status %% in
transactions data base [err=%%]

Error #6801: Date and time master failed to forward request to slave [err=%%]

Error #6802: Date and time master failed to retreive comm. reply [err=%%]

Error #6803: Date and time master received invalid date and time reply [length=%% err=%%]

Error #6804: Date and time master failed to terminate comm. session [err= %%]

Error #6805: Date and time master comm. handle is invalid [err = %%]

Error #6806: Date and time master format conversion problems

Error #6807: Date and time master failed to respond to request

Error #6808: Date and time master failed to convert reply from TM format to DT format
[err=%%]

Error #6809: Date and time master failed to convert year data [%%] as it is out of range

Error #6810: Date and time master received slave's response with invalid length [%%]

Error #6811: Date and time master internal software error

Error #6900: Failed to create irmipc_diag fork in daemon [pid=%%]

Error #6901: Failed to set SID in irmipc_diag [sid=%%]

Error #6902: Failed to change to root directory in irmipc_diag [%%]

Error #6903: Failed to create web listen handle for in irmipc_diag [%%]

Error #6904: Failed to connect to web listen port in irmipc_diag [%%]

Error #6906: irmipc_diag request handling failed [status=%%]

Error #6907: irmipc_diag pack message failure [status=%%]

Error #6908: irmipc_diag failed to send response [status=%%]

Errors #7000-9999 are used for C Applications.

460
 Error Messages

Error #7000: irmipc_diag malloc failure [function=%%]

Error #7001: irmipc_diag semaphore timeout [function=%% errno=%%]

Error #7002: irmipc_diag thread creation failure [entity=%%]

Error #7003: irmipc_diag null pointer sent to function [function=%%]

Error #7004: irmipc_diag diagnostics not processed [function=%% status=%%]

Error #7100: irmipc_diag malloc failure [function=%%]

Error #7101: irmipc_diag receive message failure [errno=%%]

Error #7200: No error messages

Error #7210: Failed to extract legacy file header from file %% [reason=%%].

Error #7211: Configuration file manager failure %%.

Error #7220: Failed to update request no. %% status as %% in transactions.db [reason=%%].

Error #7221: MDLC monitor master RX failure [reason=%%].

Error #7222: MDLC monitor master TX failure [reason=%%].

Error #7223: MDLC monitor master session termination failure [reason=%%].

Error #7224: MDLC monitor master is called with invalid parameter [reason=%%].

Error #7225: The actual number of bytes burned to unit %% is different from the total file size
%%.

Error #7226: Failed to write a result to transactions.db [reason=%%].

Error #7227: Failed to attach legacy file header to downloaded file [reason=%%].

Error #7228: Failed to rename file in order to attach legacy file header to downloaded file
[reason=%%].

Error #7229: Failed to aggregate uploaded configuration [reason=%%].

Error #7230: Failed to upload to file %% for request no. %% [reason=%%].

Error #7300: Failure on a serial port: %%

Error #7400: Received null parameter at function: %%, parameter name: %%

Error #7401: Failed to set a value in user values tables. Parameter id: %%, error: %%

Error #7402: Failed to get a value from user values tables. Parameter id: %%, error: %%

461
 Error Messages

Error #7403: Failed to set a value in float user values table. Parameter id: %%, error: %%

Error #7404: Failed to get a value from float user values table. Parameter id: %%, error: %%

Error #7405: Failed to get a value of parameter of type integer. Parameter id: %%, error: %%

Error #7406: Unsupported parameter id. Function name: %%, parameter id: %%

Error #7407: Invalid parameter mapping to scada tables. Function name: %%, table number:
%%, parameter id: %%

Error #7408: Received parameter which was not mapped to scada tables. Function name:
%%, parameter id: %%

Error #7409: Failed to set I\O (DO\AO) in scada tables. Function name: %%, table: %%, row:
%%, error: %%

Error #7410: Failed to get I\O (DI\AI\DO-BI\AO-BI ) from scada tables. Function name: %%,
table: %%, row: %%, error: %%

Error #7411: Codesys project device configuration doesn't match the configuration on the rtu.

Error #7500: FEP-RTU - received unmanaged site index: %%

Error #7550 CPRS - Fail to transmit - Transmission queue is full

The IRM1500 application transmit queue has limited size, for example it may
hold up to 32 messages. Each message has maximal frame size (default 2048),
and an idle time of 50 or 100 milliseconds to be packed and sent. So either
increase message size or increase the idle timeout. in order to have fewer
messages.

462
 Error Messages

Error #7600: Failed to fetch, unable to read BeginDataPtr. Error = %%

Error #7601: Failed to fetch, unable to read struct (spec). Error = %%

Error #7602: Failed to store, buffer is empty. Error = %%

Error #7603: Failed to store, unable to read BeginDataPtr. Error = %%

Error #7604: Failed to store, unable to read struct (spec). Error = %%

Error #7605: Failed to store msg, problem with endData ptr. Error = %%

Error #7606: Cos failed. buffer is empty. Error = %%

Error #7607: Cos failed, unable to read BeginDataPtr. Error = %%

Error #7608: Cos failed, unable to read struct (spec). Error = %%

Error #7609: Fetchend failed, buffer is empty. Error = %%"

Error #7610: Fetchend failed, unable to read struct (spec). Error = %%

Error #7611: Fetchend failed, problem with endData ptr. Error = %%

Error #7612: Fetchend failed, unable to read BeginDataPtr. Error = %%

Error #7613: Failed to fetch, pTable is NULL. Error = %%

Error #7614: Failed to fetch, pTable display is NULL. Error = %%

Error #7615: Failed to store, pTable is NULL. Error = %%

Error #7616: Failed to fetchend, pTable is NULL. Error = %%

Error #7617: Failed to cos, pTable is NULL. Error = %%

Error #7618: Failed to cos, pTable display is NULL. Error = %%

Errors #10000-12999 are used for IP Gateway (MCP-M/T).

Error: 15001 Reqmng - Buffer size problem : %% %% %%

Error: 15002 Reqmng - Buffer2 Size problem : %% %% %%

Error: 15003 Reqmng - Suspend failed : %% , ret code %%

Error: 15006 Reqmng - Problem mapping devices : %% %% %%

Error: 15007 Reqmng - No Comm buffers to fill. Last buffer is %%

Error: 15008 Reqmng - TX Q full - unable to push buffer %%

463
 Error Messages

Error: 15009 Reqmng - Create device failed %%

Error: 15010 Reqmng - Create Task failed %% %%

Error: 15011 Reqmng - Cannot Connect to manager.

Error: 15012 Reqmng - Unauthorized host logged in.

Error: 15013 Reqmng - No tx channel : rx channel type %% , Rx Channel %%

Error: 15014 Reqmng - Unmatching client IDs %%, %% reset anyway.

Error: 15015 Reqmng - Unmatching channel IDs %%, %% init anyway.

Error #15016: Client %% request to connect is denied (Clients database has no room for a
new client).
The client named by %% failed to connect because the maximum number of
connected clients was already reached.

464
 Error Messages

Error: 15017 Reqmng - Illegal tx channel %%.

Error: 15018 Reqmng - Get conf unmatch client/channel (%%,%%)

Error: 15019 Reqmng - No tx channel : Rx Channel %%

Error: 15020 Reqmng - Fail to send config block. Block Number %%, Channel ID %% Buffer
Number %%

Error: 15021 Reqmng - Fail to send block to threadpool. Block Number %%, client ID %%

Error: 15022 Reqmng - Double Duplication Loop. Dupping channel %% , Duped channel %%

Error: 15023 Reqmng - No channels left to alloc.

Error: 15030 Gtcpip - Unknown Protocol Type %%.

Error: 15050 Gtcpip - create socket error %% (%%)

Error: 15051 Gtcpip - Bind socket error %% (%%)

Error: 15054 Gtcpip - Problem reading from socket %%.

Error: 15055 Gtcpip - Select error %%.

Error: 15056 Gtcpip - Problem reading from socket %% (%%)

Error: 15060 Gtcpip - Create Device error %%

Error: 15061 Gtcpip - Problem writing to socket %% (%%)

Error: 15062 Gtcpip - Channel already occupied %% (%%).

Error: 15121 Gtos - Create Task Failed %%

Error: 15150 Gsim - Create Device Error %%

Error: 15202 Trdpool- Create device %% failed %%

Error: 15204 Trdpool- Init Boxes container %% faied %%

Error: 15206 Trdpool- Init threads container %% faied %%

Error: 15208 Trdpool- Container upb failed %% %%

Error: 15209 Trdpool- Container addr error %% %%

465
 Error Messages

Error: 15212 Trdpool- Container box range error %% %%

Error: 15213 Trdpool- Container thread range error %% %%

Error: 15215 Trdpool- Not enough boxes in queue %% %%.

Error: 15216 Trdpool- Get add box address failed.

Error: 15217 Trdpool- Add box to Queue failed %% %%

Error: 15221 Trdpool- Create task %% failed %%

Error: 15231 Trdpool- Q get error %% %%

Error: 15232 Trdpool- Free Q put error %% %%

Error: 15233 Trdpool- Free Q get error free %% %%

Error: 15234 Trdpool- Other Q get att %% %%

Error: 15235 Trdpool- Get lower thread %% %%

Error: 15236 Trdpool- Get thread failed %% %%

Error: 15237 Trdpool- Issue thread, get thread error %% %%

Error: 15238 Trdpool- Issue thread, get box error %% %%

Error: 15239 Trdpool- Block2Box, get box error %% %%

Error: 15241 Trdpool- Block2Box, request length too big %% %%

Error: 15242 Trdpool- Block2Box, copy failed %% %%

Error: 15243 Trdpool- Get from Free Q error %% %%

Error: 15244 Trdpool- Get from Other Q error %% %%

Error: 15245 Trdpool- Get from Other Lower Q error %% %%

Error: 15246 Trdpool- Box2Block, get box error %% %%

Error: 15249 Trdpool- Push to Unhandled Q failed %% %%

Error: 15250 Trdpool- Get thread attached box failed %% %%

Error: 15251 Trdpool- Get thread box to release failed %% %%

Error: 15252 Trdpool- Get attached Box to release failed %% %%

Error: 15253 Trdpool- Put box in the proper Q failed %% %%

466
 Error Messages

Error: 15260 Trdpool- Issue thread failed %% %%

Error: 15261 Trdpool- Thread pool suspend failed %% %%

Error: 15262 Trdpool- Get attached box failed %% %%

Error: 15263 Trdpool- Tp_get, box2block failed %% %%

Error: 15264 Trdpool- More requests than the ThreadPool can handle.

Error: 15265 Trdpool- Thread_pool Block Copy failed %% %%

Error: 15266 Trdpool- Tp_push, issue thread failed.

Error: 15300 Reqmng - ( %% ) create failed %%

Error: 15301 Reqmng - ( %% ) put failed : index %%, ret %%

Error: 15351 Gtappl - Nstart, map failed %% %%

Error: 15352 Gtappl - Nstart, thread map failed %% %%

Error: 15353 Gtappl - Nstart, setfunctab failed %% %%

Error: 15354 Gtappl - Nstart, trdpool get block failed %% %%

Error: 15355 Gtappl - Nstart, unknown application type %% %%

Error: 15357 Gtappl - Nstart, reqmng push block failed %% %%

Error: 15358 Gtappl - Nstart, threadpool release box failed %% %%

Error: 15359 Gtappl - Burst, map failed %% %%

Error: 15360 Gtappl - Burst, reqmng push block failed %% %%

Error: 15365 Gtappl - Mismatch in block data length %% %%

Error: 15366 Gtappl - Ctls2blk, spec data error %% %%

Error: 15367 Gtappl - Ctls2blk, site data error %% %%

Error: 15368 Gtappl - Block size error - expecting data %% %%

Error: 15369 Gtappl - Invalid pin called.

Error: 15370 Gtappl - Z_OK length problem.

Error: 15371 Gtappl - Fetch length problem %% %% %%

Error: 15373 Gtappl - Store length problem %% %%

467
 Error Messages

Error: 15376 Gtappl - Map failed %% %%

Error: 15377 Gtappl - Map thread failed %% %%

Error: 15378 Gtappl - Burst error %% %%

Error: 15380 Gtappl - Unknown block type %%

Error: 15381 Gtappl - Broadcast hb called

Error: 15382 Gtappl - Unknown Datetime block type.

Error: 15382 Gtappl - Diag hb called.

Error: 15384 Gtappl - Sync hb called.

Error: 15385 Gtappl - Ttag hb called.

Error: 15510 contalib – forbidden delete: class %% ptr %%

Error: 15511 contalib – forbidden resize: class %% ptr %%

Error: 15530 HelthChk – Create failed

Error: 15531 HelthChk – NULL parameter

Error: 15532 HelthChk failed

Error: 15533 Send ping failed for site id %% link id %% .

Trnsintr_tx_frame_seg_2id() failed. Error = %% Tried %% times.

Error: 15534 Get of formatted buffer (buf_f_get() ) failed. Error + %%.

Error: 15535 HelthChk failed to create ping task. Error = %%

Error: 15536 HelthChk failed to create pong task. Error = %%

Error: 15537 HelthChk failed to create dead task. Error = %%

Error: 15538 Ping RTUs failed. Error = %%

Error: 15539 Pong RTUs failed. Error = %%

Error: 15540 Update dead RTUs failed. Error = %%

Error: 15551 IPGWCTRL Failed to create Polling task. error = %%.

Error: 15552 IPGWCTRL Failed to create Link Up task. error = %%.

Error: 15553 IPGWCTRL Failed to create Link Down task. error = %%.

468
 Error Messages

Error: 15554 IPGWCTRL Communication Error.

Error: 15555 IPGWCTRL Burst Unknown.

Error: 15556 IPGWCTRL Link Up failed. Site = %%.

Error: 15557 IPGWCTRL Link Down failed. Site = %%.

469
 Error Messages

Compiler Error List

This section lists and explains the errors and warnings which may appear at the end of compilation.

Error #1 Failed to allocate compiler space

Not enough memory on the PC.

Error #2 Disk error

Not enough memory on the PC.

Error #3 Not enough memory

Not enough memory on the PC.

Error #4 Free memory error

Not enough memory on the PC.

Error #5 Compiler does not support this application version. Please upgrade.
For example, under the compiler option ≥ V3.70 you cannot compile an
application that has been developed under ToolBox version V1.61.

Error #6 <Element> cannot be used in this application version. Please upgrade: <rung
name>.
For example compiler version < 3.70 does not support CALC. The solution is to
upgrade to a version above 3.70 and to use the option above 3.70.

Error #7 <Element> is not supported by this compiler: <rung name>

For example, An application created under ToolBox < 3.70 does not support
CALC. You must upgrade the application to a version above 3.70.

Error #8 Cannot create application file

Creation of the application file has failed (in version <3.70 srecord file,
otherwise a binary file). Try closing applications that open files.

Error #9 Cannot create rungs map

Creation of map file produced by the compiler for monitoring has failed. Try
closing applications that open files.

Error #10 Cannot create DB map

Creation of map file produced by the compiler for monitoring has failed. Try
closing applications that open files.

470
 Error Messages

Error #11 Cannot create timers map

Creation of map file produced by the compiler for monitoring has failed. Try
closing applications that open files.

Error #12 Cannot create RAM map

Creation of file that includes the necessary RAM during download has failed.
Try closing applications that open files.

Error #13 RAM overflow

RAM overflow. In versions < 3.70 RAM is limited to 64Kbytes.

Error #14 Error: PPM list overflow

The memory allocated to PPM during compilation is full.

Error #15 Error: Time-tag list overflow

The memory allocated to Time-tag during compilation is full.

Error #16 Error: Application space overflow. Only <# of bytes> were allocated.
Not enough memory for compiling the application.

Error #17 Data type FLASH/RAM overflow

Error #18 Bit not in byte boundary: <symbol name> <rung name>
The operation requires this bit to be in the beginning of the byte.

Note: B,0 or B,1 as a byte notation is applicable only for the MOVE/MOVH
functions. In any other bit function, B,0 is identified as the first bit in a series,
bit B,1 as the second, and so forth. Bit,8 is the first bit in the second byte.

Error #19 JMP is valid only in the same process <rung name>
JMP is allowed only between rungs within the same process.

Error #20 JSP-RUNP is valid only to a process <rung name>

JSP-RUNP is allowed only to a process that appears in the process list.

Error #21 JMP-JSP-RUNP Missing symbol name <rung name>

The variable is not defined as a rung name/process name.

Error #22 JMP-JSP-RUNP to rung which does not exist: <rung name which does not
exist> <rung name>
JMP-JSP-RUNP outputs are allowed to existing rungs/processes.

471
 Error Messages

Error #23 JMP-JSP-RUNP longer than 32K bytes is not supported in this compiler option.
Try to relocate Rungs/Process or to upgrade <rung name>

Error #24 Cannot change a constant variable <rung name>

Constant value cannot be changed.

Error #25 Missing symbol name <rung name>

The variable is not defined in a rung name.

Error #26 Differentiator requires index

It is not allowed to use differentiators without an index variable in case indexed
elements exist in the rung.

Error #27 Cannot use more than 1024 differentiators up/down <rung name>
This error happens when executing compilation in version < 3.70.

Error #28 Differentiator requires input on the left side <rung name>
This element cannot appear at the beginning of a rung.

Error #29 Missing CALL name <rung name>

The CALL function is not defined. Enter the CALL output operator and select
the appropriate function allowed from the available possibilities.

Error #30 Error: Missing or invalid UCALL function name

The first parameter of UCALL, which is the function name, is missing.

Error #31 Cannot use timer ON&OFF in same timer: <symbol name><rung name>
It is not allowed to use DON and DOF operators on the same timer.

Error #32 Index value is too large: <symbol name> <rung name>
The defined index value (<IN,18>, for example) is greater than the last index
row in the multiple-column table. Correct the last index row or the rung.

Error #33 Bad mapping: <map symbol name> index value is too large: <map destination>
The defined index value (<IN,18>, for example) is greater than the last index
row in the multiple-column table. Correct the last index row or the rung.

Error #34 Cannot change index using another index: <rung name>
It is not allowed to move one index variable to another. For example, to define:
MOVE,I to J (where I and J are defined as index variables).

472
 Error Messages

Error #35 Cannot mix bit & value operands in OR, XOR, AND operators: <rung name>
It is not allowed to mix bit and value data types in Boolean operations: AND,
OR, and XOR.

Error #36 Cannot use indexed bit operand in this operation: <rung name>
It is not allowed to use an indexed bit variable (BIT,I for example) in this
operation.

Error #37 Output column length must be as long as input column length: <rung name>
Input(s) column length(s) should be as long as the output column length (for
example, in order to carry out MOVE operation of BIT1 and BIT2 to BIT3,
column index rows of BIT1, BIT2, and BIT3 should be the same).

Error #38 Index or indexed operand cannot mix with bit in this operation: <rung name>
In this operation it is not allowed to mix a symbol name which is an index or an
indexed symbol name with bits. For example, to MOVE bit to I, or IN,I to bit.

Error #39 Use MOVE (instead of MOVH) in bit to bit & value to value operations: <rung
name>
Use MOVE output operator (and not MOVH) to MOVE bit to bit, and value to
value operations.

Error #40 Cannot mix bit & float operands in this operation: <rung name>
It this operation it is not allowed to mix float and bit operands.

Error #41 Cannot mix value & float operands in this operation: <rung name>
It this operation it is not allowed to mix float and value operands.

Error #42 Cannot move float to index <rung name>

It is not allowed to MOVE from a float operand to an index operand.

Error #43 Cannot operate on empty table <rung name>

This operation cannot be carried out when the table is empty.

Error #44 Error: Cannot CPY to index <rung name>

You cannot copy into the index.

Error #45 Error: Cannot use float or bit operand as length in CPY
The length parameter cannot be of float or bit type.

Error #46 Use site name only as an input <rung name>

It is not allowed to use Site Names (defined in the Site table) as outputs.

473
 Error Messages

Error #47 Cannot use port with no matching line in ports table
Using one of the CALL functions on a row that does not exist in the User Ports
table.

Error #48 Scan in valid only in I/O columns <rung name>

SCAN output operators can be activated only on I/O columns.

Error #49 Fetch/Store requires at least nn bytes space: <rung name>

Error #50 Fetch/Store - illegal parameter data type: <rung name>

Error #51 Incompatible depts between duplicate & source columns: <column name>
<Table number>

Error #52 Cannot call AGA3 function - AGA3 tables missing

Error #53 Cannot call AGA7V function - AGA7V tables missing
Error #54 Cannot call AGA7M function - AGA7M tables missing
The indicated functions cannot be called because the corresponding tables are
missing.

Error #55 Cannot call PID function - PID tables missing

The indicated function cannot be called because the corresponding table is
missing.

Error #56 Constant index is required <rung name>

Error #57 Cannot open configuration file

It is impossible to compile without assigning configuration file.

Error #58 Error: In SEND – Index does not exist: <Index name> <rung name>
The index variable is not defined. For example, when using <IN,I> symbol
name, I is not defined. Return to the index table to define the index variable and
then compile.

Error #59 Error: In CALC - Cannot handle so many functions in a formula: <rung name>

Error #60 Error: In SEND – Name does not exist: <symbol name> <rung name>
Variable name is not defined in data base tables (IN, for example). Return to
data base builder to define the symbol name and then compile.

Error #61 Error: In CALC - Cannot handle so many symbols in a formula: <rung name>

Error #62 Error: In SEND – Simple table with index: <symbol name> <rung name>
It is not allowed to use a variable of a single-column table with index. Use
multiple-column table and define the symbol name.

474
 Error Messages

Error #63 Error: In CALC - Cannot use float operands with logic operation: <rung name>

Error #64 Error: In SEND – Index value too large: <symbol name> <rung name>
The defined index value (<IN,18>, for example) is greater than the last index
row in the multiple-column table. Correct the last index row and then return to
the rung.

Error #65 Error: In CALC - Empty formula: <rung name>

Error #66 Error: In SEND – Number exceeds size of vector: <rung name>
When the SEND operator uses the following format: '100<IN>, it means that
100 values should be sent under <IN> vector. This operation is not allowed if
the last index row in the multiple-column table is less than 100.

Error #67 Error: In CALC - Cannot CALL into an index: <rung name>

Error #68 Error: In SEND – Cannot operate on bits vector: <rung name>
SEND operator (in ASCII) is not applicable for a data base table of bits.

Error #69 Error: In CALC - Missing symbol name: <rung name>

Error #70 Error: In SEND - Cannot use more than 10 variable strings in message: <rung
name>
Up to 10 string variables can be used in SEND.

Error #71 Error: In SEND – Cannot Operate On Constants: <rung name>

With the SEND operator it is not allowed to use constants (only variables may
be used).

Error #72 Error: In SEND - Not enough space for message: <rung name>
Not enough memory to process all the text in SEND.

Error #73 Error: In I/O link - Fail to open I/O link, reoperate I/O link phase
Problem in I/O link file open (*.L4). Try closing applications that open files.

Error #74 Error: In I/O link - Application does not match I/O link file, reoperate I/O link
phase
Recreate the I/O link file.

Error #75 Error: In I/O link - Not enough memory, reoperate I/O link phase
Error #76 Error: In I/O link - Error while reading I/O link file, reoperate I/O link phase
The I/O link file is corrupted. Recreate the file.

475
 Error Messages

Error #77 Error: In I/O link - Fail to count I/O times, reoperate I/O link phase
The I/O link file is disrupted. Recreate the file.

Error #78 Internal error in in rung - re-write the rung <rung name>
Earlier versions contained an infrequent bug, and the new version of the
compiler checks for it. If this message appears, just re-write the rung.

Error #79 Error: In I/O link - Fail to load modtype.txt, reoperate I/O link pahse
The modtype.txt file is missing. Reinstall ToolBox.

Error #80 Error list was truncated – cannot display more errors
This error appears when the list exceeds 1,000 errors.

Corrupted Database Errors

The following is caused by a corrupted database:
1 Cannot get column type: <table number> <column number>
2 Cannot get table information: <table number>
3 Cannot get include file: <file name>
4 Cannot get rung: <rung name>
5 Error: In SEND - Cannot get table type: <rung name>
6 Cannot find process to which rung belongs: <rung name>
7 Cannot process rung elements
9 Cannot get constant value: <rung name>
10 Cannot find constant value: <rung name>
11 Branch stack empty: <rung name>
12 Branch stack full: <rung name>
13 Branch rung: <rung name>
14 Unknown JMP/JSR/RUNP element: <rung name>
15 Invalid rung: <rung name>
16 Internal error in disassembly

Warning List
1 Warning: JMP to same rung: <rung name>
2 Warning: JSP to same process: <rung name>
3 Warning: Undefined I/O LINK value
4 Warning: Undefined mapped field: table #<TAB NUMBER> column #<COL
NUMBER>
5 Warning: This function is not implemented yet: <rung name>
6 Warning: No SCAN operation

476
 Error Messages

7 Warning: Use MOVE to change element in Time & Date Table

8 Warning: Compiler ignores rungs without output element: <rung name>
9 Warning: The same UCALL function uses different parameters
NUMBER/ORDER/TYPE: <function name> <rung name>
10 Warning: DON without input is not an effective operation: <rung name>

477