MODCELL™ Multiloop Processor Maintenance

and MOD 30ML™ Multiloop Controller

Diagnostic Information and Troubleshooting Procedures

for 2001N, 2002N, and 1800R

ABB Instrumentation
 ABB INSTRUMENTATION
The Company
ABB Instrumentation is an established world force in the design and manufacture of BS EN ISO 9001
instrumentation for industrial process control, flow measurement, gas and liquid analysis St Neots -
and environmental applications. Certificate No. Q5907
Stonehouse -
As a part of ABB, a world leader in process automation technology, we offer customers
Certificate No. FM 21106
application expertise, service and support worldwide.
ISO 9001
We are committed to teamwork, high quality manufacturing, advanced technology and
Rochester, USA -
unrivaled service and support.
Certificate No. AQ-8618
The quality, accuracy and performance of the Company's products result from over 100
years experience, combined with a continuous program of innovative design and
development to incorporate the latest technology.
EN 29001 (ISO 9001)
The NAMAS Calibration Laboratory No. 0255(B) is just one of the ten flow calibration Lenno, Italy -
plants operated by the Company, and is indicative of ABB Instrumentation's dedication to Certificate No. 90/90A
quality and accuracy.
Stonehouse -
Certificate No. 0255

Use of Instructions

∆ Warning. An instruction that draws attention to the risk of
Note. Clarification of an instruction or additional
injury or death. information.

! Caution. An instruction that draws attention to the risk of

i Information. Further reference for more detailed
the product, process or surroundings. information or technical details.

Although Warning hazards are related to personal injury, and Caution hazards are associated with equipment or property damage, it
must be understood that operation of damaged equipment could, under certain operational conditions, result in degraded process
system performance leading to personal injury or death. Therefore, comply fully with all Warning and Caution notices.

Information in this manual is intended only to assist our customers in the efficient operation of our equipment. Use of this manual for
any other purpose is specifically prohibited and its contents are not to be reproduced in full or part without prior approval of ABB
Instrumentation.

Licensing, Trademarks and Copyrights

MODCELL, MOD 30ML, MOD 30 and PC-30 are trademarks of Asea Brown Boveri, Inc.
IBM Personal Computer AT is a trademark of International Business Machines Corporation
MODBUS is a trademark of Modicon Inc.

Health and Safety

To ensure that our products are safe and without risk to health, the following points must be noted:
1. The relevant sections of these instructions must be read carefully before proceeding.

2. Warning Labels on containers and packages must be observed.

3. Installation, operation, maintenance and servicing must only be carried out by suitably trained personnel and in accordance with the
information given or injury or death could result.
4. Normal safety procedures must be taken to avoid the possibility of an accident occurring when operating in conditions of high
pressure and/or temperature.

5. Chemicals must be stored away from heat, protected from temperature extremes and powders kept dry. Normal safe handling
procedures must be used.

6. When disposing of chemicals, ensure that no two chemicals are mixed.

Safety advice concerning the use of the equipment described in this manual may be obtained from the Company address on the back
cover, together with servicing and spares information.
 MODCELL and MOD 30ML Maintenance

CONTENTS
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––

CONTENTS

Page
SECTION 1 - INTRODUCTION
1.1 GENERAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.2 INSTALLATION INTEGRITY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.3 DIAGNOSTIC TOOLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.3.1 MODCELL Status LEDs ........................................ 2
1.3.2 Application Builder Software ..................................... 2
1.3.3 MOD 30ML Display ........................................... 2
1.4 REPAIR PHILOSOPHY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.5 RELATED INFORMATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

SECTION 2 - MODCELL STATUS INDICATORS

2.1 GENERAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.2 INTERPRETING STATUS LED INDICATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.3 TROUBLESHOOTING GUIDE ..................................... 6

SECTION 3 - VIEWING DIAGNOSTIC DATA

3.1 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3.2 APPLICATION BUILDER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3.2.1 Starting the Application Builder .................................. 12
3.2.2 Setting Up Communications .................................... 15
3.2.3 Reading Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
3.2.4 Reading and Writing Block Attributes .............................. 19
3.2.5 Commands ................................................ 20
3.3 MOD 30ML DISPLAY .......................................... 22
3.3.1 Reading MOD 30ML Diagnostics ................................. 22
3.3.2 MOD 30ML Commands ....................................... 25

SECTION 4 - COMMUNICATIONS
4.1 COMMUNICATING WITH A REPLACEMENT INSTRUMENT . . . . . . . . . . . . . . . 27
4.2 COMMUNICATION TROUBLESHOOTING . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
4.2.1 ICN Module Communication .................................... 29
4.2.2 Modbus Module Communication ................................. 32
4.2.3 Built-in ICN Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
4.2.4 Built-in Modbus Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
4.3 APPLICATION BUILDER/INSTRUMENT COMMUNICATION MESSAGES . . . . . . 37

SECTION 5 - DIAGNOSING ANALOG I/O MODULE PROBLEMS

5.1 GENERAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
5.2 READING EXTENDED ERROR CODES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
5.3 INTERPRETING EXTENDED ERROR CODE DATA . . . . . . . . . . . . . . . . . . . . . 53
5.4 COMMON MODULE ERRORS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

SECTION 6 - DIAGNOSING SHUTDOWN FAULTS

6.1 SHUTDOWN INFORMATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
6.2 RECORDING SHUTDOWN INFORMATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
6.2.1 Application Builder Method ..................................... 58
6.2.2 MOD 30ML Display Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
6.2.3 Memory Module Method ....................................... 61

i
MODCELL and MOD 30ML Maintenance

CONTENTS
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––

CONTENTS (Cont’d)

Page
SECTION 7 - EVENT CODES AND TRANSITION MESSAGES
7.1 GENERAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
7.2 TRANSITION MESSAGE DESCRIPTIONS ........................... 65
7.3 EVENT CODE DESCRIPTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

SECTION 8 - PARTS
8.1 PARTS AVAILABILITY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
8.2 BASIC HARDWARE ........................................... 85
8.2.1 MODCELL Multiloop Processor .................................. 85
8.2.2 MOD 30ML Multiloop Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
8.3 I/O MODULES ............................................... 85
8.4 COMMUNICATION MODULES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

SECTION 9 - HARDWARE, FIRMWARE, AND SOFTWARE REVISION HISTORY

9.1 GENERAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
9.2 HARDWARE AND FIRMWARE REVISIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
9.3 SOFTWARE REVISIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

ILLUSTRATIONS
Figure Page
1 Component Location, 2001N Processor ................................. 7
2 Component Location, 2002N Processor ................................. 7
3 Application Builder Untitled - (Root) Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
4 Serial Port Setup Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
5a Instrument Status Display, Version 4.0 and Lower Versions . . . . . . . . . . . . . . . . . . 16
5b Instrument Status Display, Version 4.01 ............................... 16
6 Communications Setup Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
7 Example of Diagnostic Alarm Display .................................. 23
8 Device Status and Device Event Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
9 Example of Display Pages for A Diagnostic Event ......................... 24
10 Voltage Traces for a Correctly Functioning ICN .......................... 31
10 Example of Extended Error Code (EXTERR) Data for a WRIM Module . . . . . . . . . . 53

ii
 MODCELL and MOD 30ML Maintenance

CONTENTS
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––

TABLES
Table Page
1 Status LED troubleshooting Guide ..................................... 8
2 Application Builder Startup Procedure ................................. 12
3 Serial Port Communication Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
4 Communication Setup Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
5 Instrument Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
6 Commands Accessible from MOD 30ML Display .......................... 25
7 Communication Messages, Cause and Recommended Action . . . . . . . . . . . . . . . . . 37
8 I/O Module Identification Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
9 Analog Input Module Extended Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
10 Analog Output Module Extended Error Codes ........................... 55
11 Event Transition Message Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
12 Event Codes, Description and Action ................................. 66
13 Hardware and Firmware Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
14 Software Revision History ......................................... 92

iii
MODCELL and MOD 30ML Maintenance

CONTENTS
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––

iv
 MODCELL and MOD 30ML Maintenance

INTRODUCTION

SECTION 1
INTRODUCTION

1.1 GENERAL
The MODCELL and MOD 30ML instruments contain extensive internal diagnostics which
continuously monitor instrument operation. If a malfunction is detected it is immediately
reported so that the user can take appropriate action. In addition, most routine instrument
events such as changes in operating state, switching of control modes, suppression or
enabling of various diagnostics, acknowledgement of alarm conditions, etc., are reported
for informational purposes. This diagnostic system provides, in effect, continuous
instrument maintenance. No periodic user maintenance activity is required when the
instrument is operating normally in the RUN state.

The purpose of this book is to provide detailed information about the instrument
diagnostics, and to provide procedures for accessing and using the diagnostic data to
isolate a problem and identify its cause. In the event that a malfunction is discovered,
guidelines for corrective action are provided.

1.2 INSTALLATION INTEGRITY

The procedures in this book are based on the assumption that the instrument has been
properly installed in accordance with the instructions in the installation instructions supplied
with the instrument. The applicable manuals are as follows:
IB-23C600 Installation instructions for MODCELL Multiloop Processor
IB-23C601 Installation instructions for Remote I/O Modules (Extended I/O)
IB-1800R-INS Installation instructions for MOD 30 ML,
IB-1800R-M30 Installation instructions for the Mod 30ML Replacement for MOD 30.
IB-23A160 Instructions for Instrument Communications Network (ICN) Planning

If a host computer is used with the ICN, instructions for setup of the communications link
are are provided in the following manuals:
IB-23C001 Instructions for 1720N Communications Link
IB-23C003 Users guide for 17321N ICN Mini Link
IB-23C004 Users Guise for 1733N Mini Link/External

The instrument diagnostics can identify some installation related problems such as burnout
of a thermocouple or a mismatch between the physical location of an I/O module and its
specified location in the data base configuration. For the most part, avoidance of
installation related problems depends on careful adherence to the installation instructions.
Problems related to electrical noise, input and output signals, and communication signals
can result from an improper installation. The instrument installation manuals provide
detailed connection information and typical connection diagrams for every I/O and
communication module, and for the built-in I/O and communication circuits in MOD 30ML.
This information should be reviewed when it is necessary to rule out the installation as the
source of a malfunction.

1
MODCELL and MOD 30ML Maintenance

INTRODUCTION

1.3 DIAGNOSTIC TOOLS

The MODCELL and MOD 30ML instruments are supported by the following diagnostic
tools:
• MODCELL Status LEDs
• Application Builder Software
• MOD 30ML Display

Use of these tools can provide diagnostic information which helps identify most instrument
problems.

1.3.1 MODCELL Status LEDs

The red and green status LEDs on the front of the MODCELL instrument provide
information about instrument power, instrument operating state, data base communication
with I/O, component failures, and data base and memory module integrity. A detailed
description of the status LED indications and a trouble shooting guide are provided in
Section 2.

1.3.2 Application Builder Software

The MODCELL and MOD 30ML instrument diagnostics generate a series of codes which
provide both operational status information and fault information. These codes can be
accessed via the instrument status display which is available in the Application Builder
Software. Instructions for using the Application Builder as a diagnostic tool are provided in
Section 3. A description of the diagnostic codes with recommended corrective actions is
provided in Section 7.

1.3.3 MOD 30ML Display

The device status and device events display groups show shutdown fault information and
diagnostic codes which provide operational status and fault information about a MOD
30ML instrument without using the Application Builder. A procedure for obtaining shutdown
fault information from the display is provided in Section 6.2.3. Accessing the diagnostic
codes is discussed in Section 3, and a detailed description of the codes with
recommended corrective actions is provided in Section 7.

1.4 REPAIR PHILOSOPHY

The repair philosophy for the MODCELL and MOD 30ML instruments is repair by
replacement at the module level. The module level includes those instrument components
which can be removed and installed manually via plug-in connections.The modularized
design of these instruments permits easy field replacement of components such as I/O
modules, communication modules, identity module and the portable memory module. If a
fault is detected in the processor (2001N, 2002N or 1800R) return of the unit for repair or
replacement is recommended.

All instrument components which are identified by a catalog number are available for
purchase. The components and their numbers are listed in Section 8.

2
 MODCELL and MOD 30ML Maintenance

INTRODUCTION

1.5 RELATED INFORMATION

A general description of the MODCELL and MOD 30ML instruments, mechanical
installation instructions, electrical connection instructions, and communication connection
instructions can be found in the following documents.
• IB-23C600 Installation for MODCELL Multiloop Processor
• IB-23C601 Installation for Remote I/O modules (Extended I/O)
• IB-1800R-INS Installation for MOD 30ML Multiloop Controller
• IB-1800R-M30 Installation for the MOD 30ML Replacement for MOD 30 Instruments
• IB-23A160 Instructions for Instrument Communications Network (ICN) Planning

Installation and setup information for the communications link can be found in the following
documents:
• IB-23C001 Instructions for 1720N Communications Link
• IB-23C003 Users guide for 17321N ICN Mini Link
• IB-23C004 Users Guise for 1733N Mini Link/External

Reference information on the data base structure and configuration parameters applicable
to both MODCELL and MOD 30ML instruments can be found in the following documents.
• IB-23G600 Data Base Reference for Logic I/O and Communication Functions
• IB-23G601 Data Base Reference for Advanced Control Functions
• IB-23G602 Data Base Reference for Algorithm, Table and Sequencer Functions
• IB-23H141 User’s Guide for MODCELL Application Builder Software

General operation and setup information, and reference information on the data base
structures and configuration parameters which apply only to the MOD 30ML Multiloop
Controller can be found in the following documents.
• IB-1800R-OPR Operation for MOD 30ML Multiloop Controller
• IB-1800R-APP Data Base Reference for Display, Alarm, and Built-in I/O Functions

3
MODCELL and MOD 30ML Maintenance

INTRODUCTION

4
 MODCELL and MOD 30ML Maintenance

MODCELL STATUS INDICATORS

SECTION 2
MODCELL STATUS INDICATORS

2.1 GENERAL
The red and green status LEDs on each MODCELL instrument, Figure 1 or 2, provide
continuous visual indication of the operational condition of the instrument. These LEDs
have five possible conditions as follows:
• Red off; Green off
• Red on; Green off
• Red off; Green on
• Red on; Green on
• Red flashing; Green on

Normal operation of the instrument in the RUN state is indicated by red off and green on.
The other conditions provide useful operational information when observed in conjunction
with events and conditions such as initial application of power, the instrument initialization
sequence, power-up after a shutdown, presence of a valid data base, use of a portable
memory module, and an I/O mismatch condition. The status LED indications are described
in detail in Section 2.2.

2.2 INTERPRETING STATUS LED INDICATIONS

• Initial power-up
When power is applied to the instrument, the red LED turns on indicating presence of
power to the instrument. If the red LED remains on and the green LED fails to turn on,
a fault condition is present in the instrument. Examples of problems in this case
include identity module not present, select module failure, processor failure, memory
failure, etc.

• After initialization sequence

After power up, the instrument and I/0 are initialized and the green LED is turned on.
From this point, several parameters affect the next state which the instrument can
enter. These include the presence of a backup memory module and if present, the
setting of its MODULE LOAD/NORMAL switch, the setting of the RUN/SERVICE
switch on the front of the instrument, the presence of a previous shutdown fault
condition logged in the instrument memory, the presence of a valid database in the
instrument memory or in the backup memory module, and if a database is present,
parameters in the database such as the warmstart/coldstart parameters, run on I/O
mismatch, and physical I/0 population vs. configured I/O module blocks.

• Power-up after shutdown

If the instrument is being powered up after it experienced a shutdown fault (checksum
error, spurious interrupt, watchdog, etc.), it will enter the DEFAULT state, leaving the
red and green LED's on. Previous shutdown fault information is recorded in the
instrument memory, and can be read with the read shutdown information message.

5
MODCELL and MOD 30ML Maintenance

MODCELL STATUS INDICATORS

The instrument can not be removed from the DEFAULT state in this case until the
shutdown is acknowledged with the ACK shutdown fault message (see Section 6).
When this message is received, the instrument continues through the startup process
and advances to the appropriate state.

• Memory module and database checks

If a memory module is present and its switch is in the MODULE LOAD position, the
instrument enters and runs in the UPLOAD state. During upload, the red LED is on. If
a valid main database is present and is successfully copied to the backup memory
module, the red and green LEDs will remain on. If there is a failure (bad main
database, bad memory module, memory module write protected), the green LED will
remain steady on and the red LED will flash. In either case, the instrument is
accessible for diagnostic and event information, and if I/O module blocks are
configured, the I/0 points are accessible (see Section 3).

If there is not a valid main database or memory module database available for
download, the instrument enters the DEFAULT state, leaving the red and green LEDs
on.

• I/O mismatch check

If there is a valid database present, the instrument checks the configured I/O
complement against the physical I/O modules present. An I/O mismatch diagnostic
compares each slot configured for an analog or digital I/O module against the content
of the slot during a power-up or data base download. If a slot configured for an analog
module is empty or the installed module does not match the configuration, a diagnostic
message is generated. If a slot configured for a digital module contains an intelligent
module (analog input or output, ICN, MSC, or RIO), a diagnostic message is
generated. Note that this diagnostic cannot distinguish between an empty slot and a
digital I/O module or between different types of digital I/O modules.

If an I/0 mismatch is found and this mismatch has not been previously acknowledged,
the instrument will enter the HOLD state unless it is configured to run on I/O
mismatch. An I/O mismatch can be acknowledged and overridden by sending a
run/warmstart command to the instrument (writing this value to the IF1,NXTISTAT
attribute). When this message is received, the instrument advances from the HOLD
state. Both the red and green LEDs remain on in the HOLD state. (See Section 3 for
information on read/write commands.)

If the instrument is powered down and powered up again, it will note that the
mismatched physical I/O complement matches the complement that was previously
acknowledged and overridden, and progress beyond the HOLD state.

• RUN/SERVICE switch check

Once the instrument has determined it can enter the RUN state, the RUN/SERVICE
switch on the front of the instrument is checked. If this switch is set to service, the
instrument enters the LOCAL HOLD state, and the red and green LEDs remain on. If
the switch is in the RUN position, the red LED is turned off and the green LED
remains on indicating the normal RUN condition.

2.3 TROUBLESHOOTING GUIDE

A troubleshooting guide providing recommended corrective actions in the event that fault
conditions are indicated is provided in Table 1.

6
 MODCELL and MOD 30ML Maintenance

MODCELL STATUS INDICATORS

Figure 1. Component Location, 2001N Processor

*CAUTION: DC power supply will be

damaged if connected to ac power.

Figure 2. Component Location, 2002N Processor

7
MODCELL and MOD 30ML Maintenance

MODCELL STATUS INDICATORS

Table 1. Status LED Troubleshooting Guide

Status LED
Problem Probable Cause Action
Condition
Red off No power 1. Power not turned on. 1. Turn on power.
Green off
2. Power not connected at 2. Connect power.
distribution panel(AC source).
3. Instrument power supply 3. Return instrument for repair
failed. or replacement.
Red on Green does not 1. Termination facility on front of 1. Tighten housing screw.
Green off turn on when Eurocard instrument, Figure
power is applied 1, not properly engaged.
2. Identity module not present. 2. Install identity module.
3. Select module failure, 3. Return instrument for repair
processor failure or memory or replacement.
failure.
4. Green LED failed. 4. Return instrument for repair
or replacement.
Red off None; normal 1. A valid data base was 1. None, wait for instrument to
Green on condition after previously loaded. Instrument enter next state.
power-up is initializing and checking
other parameters.
2. A data base has been 2. None
successfully downloaded.

Instrument does Problem with red LED. Change RUN/SERVICE

not run data base switch setting to SERVICE.
If no change in LED status,
tighten housing screw, and
return switch to RUN. If red
LED remains off and
instrument does not run data
base, return instrument for
repair or replacement.
Red on Instrument 1. No valid main data base. 1. None - Normal out-of-box
Green on without a memory condition.
module is in
2. Instrument experienced 2. Read shutdown information
DEFAULT state
shutdown fault on previous and acknowledge from
after power-up
power-up. status page.

After power-up Bad memory module data Read diagnostics from

instrument does base. status page to check validity
not accept of memory module data
download from base.
memory module

8
 MODCELL and MOD 30ML Maintenance

MODCELL STATUS INDICATORS

Table 1. Status LED Troubleshooting Guide (Cont’d)

Status LED
Problem Probable Cause Action
Condition
Red on After power-up Memory module switch is set Change memory module
Green on instrument is in at LOAD; main database has switch setting to NORMAL.
(Cont’d) UPLOAD state been successfully copied to
memory module.

Instrument Operator initiated command. Use status page or host

operating system to advance to next
normally in RUN state.
state, changes to
HOLD state.

Instrument in I/O mismatch reported or Send run/warmstart

HOLD state previously reported and is command to instrument
unacknowledged. (If1,NXTISTAT), then turn off
power and turn it on again.

All checking is RUN /SERVICE switch is set Change switch setting to

complete and at SERVICE or switch failure. RUN if appropriate or test
Instrument is in switch.
LOCAL HOLD
state
Red flashing After power-up, 1.Memory module write protected. 1. Change memory module
green on memory module switch setting to
upload failure. READ/WRITE.
2. Bad main data base; 2. Read diagnostic information
checksum error. and revise configuration.
3. Bad memory module. 3. Replace memory module.

9
MODCELL and MOD 30ML Maintenance

MODCELL STATUS INDICATORS

10
 MODCELL and MOD 30ML Maintenance

VIEWING DIAGNOSTIC DATA

SECTION 3
VIEWING DIAGNOSTIC DATA

3.1 INTRODUCTION
The purpose of this section is to provide specific how-to instructions for viewing diagnostic
data and issuing commands to the instrument. Two methods are available:

• Application Builder Software

The 2006S Application Builder Software can be used to view diagnostic event data
and issue commands to MODCELL and MOD 30ML instruments. See Section 3.2.

• MOD 30ML Display

The front panel displays on a MOD 30ML instrument can be used to view diagnostic
event data and issue commands to the instrument. See Section 3.3.

3.2 APPLICATION BUILDER

Diagnostic data is viewed via the Instrument Status display in the Application Builder
Software. This display also supports the issuance of a series of instrument commands,
and read/write commands to specific block attributes The following sections provide
procedures for accessing the status page, setting up communications with the required
instrument, and then executing commands as required.

Diagnostic data on all active and unacknowledged diagnostic conditions can be obtained
using a single read command. When the System Event Block is configured to report all
diagnostics, a history of diagnostic events is stored in the system event queue. Reading
the queue displays the events in order of occurrence. The capacity of the queue can be
configured to contain as many as 1000 events. If the capacity is exceeded, the oldest
events are overwritten by incoming events.

Users of the procedures in this section should have general knowledge of the Application
Builder software. Comprehensive user information is available in IB-23H141, User’s
Guide for MODCELL Application Builder Software.

11
MODCELL and MOD 30ML Maintenance

VIEWING DIAGNOSTIC DATA

3.2.1 Starting the Application Builder

This procedure is based on the assumption that the software is installed as described in
IB-23H141. Start the program using the step-by-step instructions in Table 2.

Table 2. Application Builder Startup Procedure

Step Procedure Comments

1 Access the DOS prompt for the drive and directory If the drive and directory are other
where the Application Builder resides. The following than C and APPBLD, the applicable
prompt appears: prompt appears instead of
C:\ APPBLD C:\APPBLD.
2 Type STRATEGY and press the ENTER key. The This action starts the Application
UNTITLED [ROOT] display appears in the Select Builder. It takes a few seconds for
mode with the workspace empty, Figure 3. the display to appear.
3 Click on the About icon and note the software version It is useful to know the version
number displayed in the About window, then click on number of your software because
OK to close the window. the version numbers are used as
required to identify procedural
variations in the following steps.
4 From the library icons on the left side of the display, Selection of one of the displayed
make a selection as follows: library icons is a procedural action
used to quickly obtain access to
• Click on any one of the displayed icons. A box
the status display. The icon is not
outline appears.
part of the instrument data base.
• Move the cursor to drag the box into the
workspace.
• Click the left mouse key. The box disappears
and after a few moments a block representing the
selected icon appears. This block carries the
default tag number 001.
• Click the right mouse key to close the icon
selection sequence.
5 Click on the Serial Port Setup icon to select it from
the TOOL BAR. A serial Port Setup menu,
Figure 4, appears.
6 Select the PC communication port you wish to use to
communicate with the instruments on your network.

12
 MODCELL and MOD 30ML Maintenance

VIEWING DIAGNOSTIC DATA

Mouse Cursor
Serial Port Setup Instrument Functions

Workspace

Figure 3. Application Builder Untitled - [Root] Display

Figure 4. Serial Port Setup Menu

13
MODCELL and MOD 30ML Maintenance

VIEWING DIAGNOSTIC DATA

Table 2. Application Builder Startup Procedure (Cont’d)

Step Procedure Comments

7 Configure the selected port as follows: The Base Address field is
automatically determined, if
• If your software is Version 3.00 or lower, select
possible, when a communication
the Link Type Field and scroll to obtain Link for
port is selected. In most cases the
ICN communication or None for Modbus
address (Hex number) can be left
Communication. This field is not used in later
unchanged. A zero appears if the
versions.
software cannot determine the
• If necessary, select the base address field and address. Enter the correct address
enter the required address. if a zero appears or if your
computer uses a different address
• Select the Baud Rate, Data Bits, Parity, and Stop
than that determined through the
Bits fields. The default values are shown in bold
software check of your computer’s
text in Table 3.
BIOS.

The communication parameters

may have to be changed to match
the instrument port parameter
settings after the port is initialized
in Section 3.2.2.
8 Select OK to activate the entries and return to the
workspace display.
9 Click on the Instrument Functions icon (ABB-KT or
ABB), Figure 3, to select it from the TOOL BAR. A
group of function icons appear below the tool bar.
10 Select the Status icon. The Select Tag window
opens, listing the default tag number 001.
11 Double click on the tag number. The Instrument Set up communications as
Status Display, Figure 5, appears. described in Section 3.2.2.

Table 3. Serial Port Communication Parameters

Comm Serial Data Stop

Link Baud Parity
Type Port Bits Bits
19200, 9600, 4800, 2400, None, Even,
1720N ------- 8 1, 2
1200 Odd
ICN 1731N Ports 1&2 19200, 9600, 8 1 None
Port A 19200, 9600, 4800, 2400,
1733N 8 1 None
(9 pin) 1200, 600, 300
Port B 19200, 9600, 4800, 2400,
1733N 8 1 None
(25 pin) 1200, 600, 300
38400,19200, 9600, 4800,
Modbus None ----- 8 1,2 None, Even, Odd
2400, 1200, 600, 300,150

14
 MODCELL and MOD 30ML Maintenance

VIEWING DIAGNOSTIC DATA

3.2.2 Setting Up Communications

This procedure provides for the selection of the specific instrument on which diagnostic
data is required, and defines the required communication parameters. Perform the setup
procedure using the step-by-step instructions in Table 4.

Table 4. Communication Setup Procedure

Step Procedure Comments

1 On the Instrument Status display,
Figure 5, click on Setup. The
communication setup menu, Figure 6,
appears.
2 Select the Communications Type field Communications module and wiring connections must
and scroll to select either Link (ICN) or be compatible with this selection.
Extended Modbus or Modbus.
3 If link communication was selected, The ICN and Instrument Number fields are not used
proceed as follows: if Modbus was selected in Step 2.

• Select the ICN Number field and If an ICN communications module is used, the target
enter the applicable ICN number: instrument number is determined by the setting of the
0 - 7 for standard link (depends on address switch on the module. This switch is read
board position) or 0-1 for a Minilink only at power up; cycle the power if the setting is
(depends on labeled connection changed.
port).
If the MOD 30ML built-in ICN communications circuit
• Select the Instrument Number field is used, the communications jumper must be set on
and enter the number (0-15) of the the ICN position, and the target instrument number is
target instrument. determined by configuring the ICN address and
enabling the ICN on the front panel device setup
display.
4 If Modbus communication was If a Modbus Communication module is used,the
selected, select the Modbus Address address of the target instrument is determined by the
field and enter the address (1 - 247) of settings of the two address switches on the module.
the target instrument. These switches are read only at power up; cycle the
power if the settings are changed.

If the MOD 30ML built-in Modbus communications

circuit is used, the communications jumper must be
set on the RS-232 or RS-485 position, and the target
instrument number is determined by configuring the
Modbus address and enabling Modbus
communication on the front panel device setup
display. Default is 247.
5 Select the Serial Port field and scroll to
select your computer communication
port (Com 1 - Com 4)

15
MODCELL and MOD 30ML Maintenance

VIEWING DIAGNOSTIC DATA

Figure 5a Instrument Status Display, Version 4.0 and Lower Versions

Figure 5b Instrument Status Display Version 4.01

16
 MODCELL and MOD 30ML Maintenance

VIEWING DIAGNOSTIC DATA

Figure 6 Communications Setup Menu

Table 4. Communication Setup Procedure (Cont'd)

Step Procedure Comments
6 Leave the Log File entry at No; The Log File is used to capture Link or Modbus
scrolling to Yes will slow communications to a disk file (*.LOG). The file helps
communication activities. determine the source of any communications
problems during configuration and runtime activities.
7 Select the Database to Read field and This selection affects only attribute read commands.
if necessary, scroll to select Current
8 Ignore the fields related to
downloading. They do not apply to
diagnostics.
9 Select OK to activate the setup entries Read/write commands can now be entered as
and return to the Instrument Status described in Sections 3.2.3, 3.2.4, and 3.2.5.
display.

17
MODCELL and MOD 30ML Maintenance

VIEWING DIAGNOSTIC DATA

3.2.3 Reading Diagnostics

Commands are typed on the command line near the bottom of the status display, Figure
5, and sent to the instrument by clicking on the ENTER button or pressing the enter key.
The command for reading diagnostics is:
R DIAGS type
When typing this command,the letter R and the abbreviation DIAGS must be followed by a
space. Upon entry of this command, the screen displays up to 15 diagnostics of the
specified type and a prompt to continue appears if necessary. The specified types may be:
AB Read abnormal diagnostics - Return points that are active or
unacknowledged (default if type is not specified)
ABQ Read abnormal or quality - Return points that are active, unacknowledged,
or have bad status qualities
UAK Read unacked - Return points that are unacknowledged
UAKQ Read unacked or quality - Return points that are unacknowledged or have
bad unacknowledged status quality
ACT Read active - Return points that are active
ACTQ Read active or quality - Return points that are active or have bad active
status quality
SUP Read suppressed - Return points that are suppressed
ALL Read all points - Return all diagnostic points

Active Diagnostics
An effective way to quickly check for active diagnostics is to use the R DIAGS command
without specifying a type. This returns all points that are active or unacknowledged. An
example of the message returned in response to an R DIAGS command is:
WRIM1 NEW/CLR UAK G ACT G
8 WRIM MODULE ERROR
This message, as it appears on the status display, is shown in Figure 10 (page 53, Section
5). The information contained is as follows:
• Block Type and Occurrence Number - This identifies the block reporting the
diagnostic (WRIM1 in the example).
• Classification of the diagnostic:
- NEW/CLR - Diagnostics having a sustained active state which is cleared when
normal conditions are restored.
- ACK ONLY - Diagnostics resulting from a momentary occurrence where the
abnormal condition is not sustained. This class is sometimes accompanied by
a counter attribute which counts the number of occurrences.
• Status - The diagnostic status at the time the read command is received (UAK G
ACT G in the example). This status data indicates that the diagnostic is
unacknowledged (UAK), unacknowledged attribute quality is good (G), diagnostic
condition is active (ACT), and active status quality is good (G). After
acknowledgement, the status changes to ACK G ACT G.
• Event Code and Message Text - Each diagnostic in a block has a unique code
number (8 in the example), and a brief text message (WRIM MODULE ERROR) is
appended to the code to indicate the nature of the problem.

18
 MODCELL and MOD 30ML Maintenance

VIEWING DIAGNOSTIC DATA

Use the block type and event code to locate the diagnostic description and corrective
action listed in Section 7. The description/action listed for WRIM,code 8 states that the
module has reported an extended error code, and references Section 5 which provides
detailed information about the error.

Diagnostic History
When the System Event block is configured to report all diagnostics, the block stores both
new/clear and acknowledge only diagnostics reported by the data base blocks. Viewing the
system event queue provides data on all diagnostics which have occurred since the
current data base was down loaded or the queue was cleared. The command for reading
the queue is:

RQ

This command returns the most recent event first (other types of system events such as
informational only, process alarms etc. are stored with the diagnostic events). The screen
displays up to 15 events and a prompt to continue appears if necessary. An example of
an event queue entry is as follows;

13:17:54:741 05/23/96 CLR/ACK

IF1 41 I/O IS LOCKED

The first line lists the time the diagnostic was reported, the date,and a transition message
(CLR/ACK). The second line lists the block type and occurrence number (IF1), event
code number (41), and diagnostic message text. See Section 7.2 for a description of the
transition messages, and use the block type and event code to find description/action
information in Section 7.3

3.2.4 Reading and Writing Block Attributes

The command format for reading or writing block attributes is as follows:

O_OOOO,OOOOOOOO_OOOOOOOO _ = Space

Data & data type if configurable

(See Table 5, Note 3)

Attribute Mnemonic

Block Identifier & Occurrence No.

Command Identifier: R (Read), W (Write)

Examples of typical commands are:

• Read the value of the PID Control Block Base Gain attribute:
R PID1,BGAIN
• Write a baud rate value of 38400 to the Modcell Serial Communications Block Baud
Rate attribute:
W MSC1,BAUDRATE 8 (8 is the entry code for 38400 baud)

19
MODCELL and MOD 30ML Maintenance

VIEWING DIAGNOSTIC DATA

All attribute data required for composing the read and write commands is provided in the
data base reference books listed in Section 1.4. The block identifiers for the data base
blocks are listed at the beginning of Section 7.3, and the block occurrence numbers are
listed in the .CRF file for your data base (see IB-23H141, Appendix A).

3.2.5 Commands
In addition to the read/write commands for diagnostics and block attributes, the status
display supports several other commands which provide for, reading the instrument
version number, setting the instrument time and date, etc. A list of all commands is
shown in Table 5 and the associated notes provide additional descriptive information. The
commands must be typed exactly as shown in the command column. Note that an
underscore is required in those commands which are not prefixed with an R or W. The
letters R (Read) and W (write) are always followed by a space.

Table 5. Instrument Commands

Equivalent
Command Description
Command
ACK_SD Acknowledge shutdown fault W IF1,CMD 1
UP_MOD Upload to module W IF1,CMD 2
DOWN_MOD Download from module W IF1,CMD 3
SET_WP Set module write protect W IF1,CMD 4
CLR_WP Clear module write protect W IF1,CMD 5
DEL_MAIN Delete main data base W IF1,CMD 6
RES_MAIN Restore main data base W IF1,CMD 7
RESET Restart instrument after task completes W IF1,CMD 8
KILL Restart instrument before completing task W IF1,CMD 9
CLR_MT Clear maximum execution times W IF1,CMD 10
CLR_Q Clear system event queue W SE1,CLRQCMD 1
ACK_ALL Acknowledge all diagnostics, W SE1,GLBACK 1
notification/request messages, and process
alarms
ACK_DIAGS Acknowledge all diagnostics W SE1,DGACK 1
ACK_ALMS Acknowledge all process alarms W SE1,PAACK 1
R TIME Read instrument time of day (Time includes R IF1,TIMEDAY
Date and Day or they can issued separately)
R DATE Read instrument calendar date R IF1,DATE
R DAY Read instrument day of week R IF1,DAY
R IOLOCK Read instrument I/O Lock status R IF1,IOLOCK
R STATE Read instrument state R IF1,INSTATE
W TIME data Write instrument time of day W IF1,TIMEDAY data
W DATE data Write instrument calendar date W IF1,DATE data
W DAY data Write instrument day of week W IF1,DAY data
W STATE data Write instrument state W IF1,NXTISTAT data
R FG Read Minimum Foreground None
R FGO lsp Read Foreground offset of attribute None
R BLOCK blkocc# Read block and display bytes in hex None

20
 MODCELL and MOD 30ML Maintenance

VIEWING DIAGNOSTIC DATA

Table 5. Instrument Commands (Cont’d)

Equivalent
Command Description
Command
R VERSION 1 Read instrument version None
R SD type 2 Read instrument shutdown area type None
R lsp Read specified attribute None
R lsp type 3 Read Byte Before attribute None
RS lsp Read specified string attribute (RS IF1,USRTAG) None
RS lsp type 3 Read Byte Before string attribute (RS EX1,13 H) None
W lsp data Write specified attribute None
W lsp data type 3 Write Byte Before attribute None
ACK blkocc# diag# 4 acknowledge diagnostic point (e.g. ACK IF1 9) None

NOTES for Table 5:

1. R VERSION command applies to any instrument on the network (ICN or Modbus)
and is returned as follows (current versions are bold, MOD 30 instruments start with
C, R, A, or S version id return data):

Description Return Data

2001P MODCELL Logic Controller Version 5 BxA__5xxxxxxx
" (Version 2, 3, 4 follow in same fashion) BxA__...
2001P MODCELL Logic Controller Version 1 BxA__1xxxxxxx
2002P MODCELL Regulatory Controller Version 3 DxA__3xxxxxxx
2002P MODCELL Regulatory Controller Version 2 DxA__2xxxxxxx
2002P MODCELL Regulatory Controller Version 1 DxA__1xxxxxxx
2004P MODCELL Batch Controller Version 1 GxA__1xxxxxxx
2004P MODCELL Advanced Controller Version 2 GxA__2xxxxxxx
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
1800P MOD 30ML Controller Functions Version 1 IxA__1xxxxxxx

2. R SD type is an engineering debug tool command that calls specific instrument

registers as displayed on the Shutdown Information page. Type indicates which
shutdown information to read. Type may be:
I = instrument information (default if type is not specified)
MP = module information at power up
M = module information
Be sure to write protect the memory module if the memory module is being placed
on another instrument to examine the shutdown information. Failure to write protect
the module will cause the shutdown information area to be written over by the
instrument when it powers up.

21
MODCELL and MOD 30ML Maintenance

VIEWING DIAGNOSTIC DATA

NOTES for Table 5 (Cont’d);

3. Commands specifying a data type (R lsp type, RS lsp type, W lsp data type) are
used with BYTE BEFORE data. A BYTE BEFORE attribute has a configurable data
type. For example, to write a BYTE BEFORE attribute of an Expression Block
input, the command might be: W EX1,I1 37.2 F. The specified types may be:
C: count D: discrete
S: short state L: long state
DA: date F: floating point
M: msec time A: ascii
H: hex
Data is the data to be written, expressed as follows:
count: 0-65535 discrete: 0-1
short state: 0-15 long state: 0-255
date: D,dd/mm/yy or M,mm/dd/yy floating pt: Floating point number
msec time: hh:mm:ss.sss ascii: “Text string in quotes.”
hex: Hexadecimal number (preceded by $)
NOTE: The "lsp", or Logical Source Pointer, is how individual database attributes
are addressed. It consists of the block name, block occurrence number, and
attribute name (e.g. TM10,TIME).

4. ACK blkocc# diag# (acknowledge diagnostic point command) is used to

acknowledge a diagnostic point. The read diagnostic command displays the block
occurrence and event code for each diagnostic point, which can then be used as
parameters for this command.

3.3 MOD 30ML DISPLAY

The instrument display supports viewing of diagnostic data and implementation of several
commands as described in the following sections.

NOTE: If the Application Builder software is available for use with the MOD 30ML
instrument, use of this software as described in Section 3.2 provides more
comprehensive diagnostic data and offers a wider command selection than the
instrument display.

3.3.1 Reading MOD 30ML Diagnostics

Active Diagnostics
An unacknowledged diagnostic condition is always indicated by flashing of the alarm LED.
The indication may also include a flashing display and a beep signal depending on
configuration. A dedicated alarm display provides information on all active diagnostics. An
example of the display with control key information is shown in Figure 7.

When the alarm light indicates an alarm condition, press the alarm key to access the alarm
displays. Pressing the key repeatedly scrolls through a series of displays covering all
unacked alarms and acknowledged alarms which are still active. Unacknowledged
diagnostics are always displayed first in the viewing sequence. See IB-1800R-OPR,
Section 3 for more information.

22
 MODCELL and MOD 30ML Maintenance

VIEWING DIAGNOSTIC DATA

Abbreviated diagnostic message.

[UAK] indicates that the alarm is active and has not been
acknowledged. Press the ‘A' key to acknowledge the alarm. If
alarm is still active [ACT] appears. If alarm is no longer active
[CLR] appears, and this display is deleted upon exit.

[RET] indicates that the R/L key can be pressed to return to

the runtime displays.

[7] is the Diagnostic event code number.

[AOUT] [2] indicates the block type and number.

Use the block type and event code number to locate a

description of the diagnostic event in Section 7.3. For
example, code 7 for the [AOUT] block indicates an AOUT
(module) error because the output circuit has reported an
output-too-high or output-too-low error.

Figure 7. Example of Diagnostic Alarm Display

Diagnostic History
The System Event block stores diagnostics reported by the data base blocks. Viewing the
system event queue provides data on all diagnostics which have occurred since the
current data base was down loaded or the queue was cleared. The queue contains both
informational and diagnostic data. The data for each event in the queue is displayed on
two pages. View the data in the event queue using the following procedure:

1. Press and hold the TAG key to obtain the Device Status display, Figure 8.

2. Press NXT repeatedly until the Device Events display appears.

3 Press down arrow to enter the event queue. Page 1 for the first event in the queue
appears, Figure 9.

4. View the events in the queue as follows:

• Press the down arrow again to view page 2 for the first event.
• Press the up arrow to return to page 1.
• Press NXT to view the next event; use down and up to view page 2 as required.
• Use the block type and event code, Figure 9, to locate the event description and
recommended action listed in Section 7.3.

5. Continue using the NXT, Down, Up sequence to view all the event data in the queue.

6. Press the TAG key to return to the DEVICE/EVENTS display, then press again to
return to the runtime display.

23
MODCELL and MOD 30ML Maintenance

VIEWING DIAGNOSTIC DATA

Figure 8. Device Status and Device Event Displays

Abbreviated
Event
Message Date

Time
Hr:Min:Sec

Event
Code
Time (msec)

Block Transition
Type Message

Block
Occurrence
Number Page 1 Page 2

Figure 9. Example of Display Pages for a Diagnostic Event

24
 MODCELL and MOD 30ML Maintenance

VIEWING DIAGNOSTIC DATA

3.3.2 MOD 30ML Commands

Access the commands as follows:

1. Press and hold the TAG key to obtain the Device Status display, Figure 8.

2. Press the down arrow to enter the the status setup sequence. The Device State
(DEV STAT) display or password request (CONFIG PASSWORD) display appears.

3. If a configuration password if required, proceed as follows:

• Use the arrow keys to display the password number.
• Press the scroll key while the ENT prompt is flashing to enter the password. The
Current Level display appears indicating that the correct configuration password
has been entered.
• Press ENT to return to the Device Status display.
• Press the down arrow to enter the the status setup sequence. The Device State
(DEV STAT) display appears.

4. From the DEV STAT display press NXT until COMMANDS appears on Line 2.

5. Press the down arrow to enter the command sequence. The Clear Q command
appears.

6. To execute this command, use the arrow keys to select YES, then press the scroll key
while the ENT prompt is flashing.

7. Press NXT repeatedly to scroll through the available status commands, Table 6, and
execute any required command using the method of Step 6.

8. Press the TAG key to return to the runtime display.

Table 6 . Commands Accessible from MOD 30 ML Display

Command Description
CLR Q Use to clear system event queue.
CLR MT Use to clear maximum scan times for all scan groups.
ACK ALL Use to send global acknowledge command causing all
diagnostics, notification/request messages, and process
alarms to be acknowledged.
RESET Use to complete tasks then perform a power-up.
KILL Use to perform an immediate power-up.
DEL MAIN Use to mark the main data base as bad and set the
instrument state to DEFAULT.
RES MAIN Use to mark the main data base as good in case DEL MAIN
command was issued by mistake. If data base is verified as
good, attempts to set instrument state to RUN.

25
MODCELL and MOD 30ML Maintenance

VIEWING DIAGNOSTIC DATA

26
 MODCELL and MOD 30ML Maintenance

COMMUNICATIONS

SECTION 4
COMMUNICATIONS

4.1 COMMUNICATING WITH A REPLACEMENT INSTRUMENT

! CAUTION When replacing an instrument on an ICN or MODBUS network, serious

network communication problems can occur if the assigned address of the
new instrument matches the address of another device on the network. Be
sure the address setting of the new instrument is correct before connecting it
to the network.

When replacing an instrument which communicates via an ICN or Modbus

communications module, the address of the new instrument can be easily verified by
reading the setting of the address switch(s) on the module prior to connecting the
instrument. When a MOD 30ML instrument using built-in communications is being
replaced, the address of the new instrument is set via the instrument display and
verification requires that the instrument be powered.

Connection of a replacement having a different address than the original instrument or

other incorrectly configured communication parameters causes problems in establishing
communication between the replacement instrument and the computer. These problems
are addressed in Section 4.2.

Connection of a MOD 30ML with an unknown address allows the possibility that the
unknown address matches the address of another device on the network. When two
devices with identical addresses are connected, the entire network communication is
disrupted. In the case of an ICN all communication ceases until the replacement is
disconnected. This problem can be avoided by using the following procedure when
installing a replacement MOD 30ML with an unknown address setting:

1. Before installing the instrument:

• Set the RUN/SERV switch at SERV.
• Verify that the communications jumper is in the correct location for built-in
communication via either the ICN, RS-232 Modbus or RS-485 Modbus.
• If the database of the new instrument is to be loaded from a memory module,
install the module and set the switches at READ/WRITE or READ ONLY and
NORMAL.

2. Install the instrument and apply power. The Device Status display appears with the
instrument state indicated on line 3 as follows:
• LHD indicates the instrument is in the local hold state and has a valid database.
• DEF indicates the instrument is in the default state and may or may not have a
valid database. This procedure can be successfully completed with the instrument
in the default state.

3. Press the alarm key and ACK key as required to view, acknowledge and clear the
power up/power down alarm, and any other alarms or diagnostics which are present.

27
MODCELL and MOD 30ML Maintenance

COMMUNICATIONS

4. Press the NXT key to access the Device Setup Display, then press the down ( ) key
to enter the setup sequence.

5. Configure the built-in (BI) communication parameters as follows:

• For ICN communication:
- Set ICN address to match the address of the instrument being replaced.
- Set ICN status active by entering YES in response to the ENABLE? prompt.
• For Modbus communication:
- Set Modbus address to match the address of the instrument being replaced.
- Set Modbus baud rate, parity, and stop bits to match the instrument being
replaced.
- Set Modbus status active by entering YES in response to the ENABLE?
prompt.

6. If a memory module is not being used, download a valid database from the Application
Builder.

NOTE: Because the RUN/SERV switch is at SERV, the application builder generates
the following message after completion of a successful download:
“Cannot change to run. State changed to LOCAL_HOLD.“

7. Set the RUN/SERV switch at RUN.

28
 MODCELL and MOD 30ML Maintenance

COMMUNICATIONS

4.2 COMMUNICATION TROUBLESHOOTING

When there is a problem in establishing communications between a host computer and the
instruments on an ICN or Modbus network, use the appropriate following procedure to help
isolate the source of the problem.

NOTE: If the communication problem is caused by replacing an instrument on a network,

refer to Section 4.1.

4.2.1 ICN Module Communication

Troubleshoot problems with ICN module communication as follows:

1. Remove power from the instrument and communications link.

2. Note the address switch setting on the ICN module. The address is indicated in
hexadecimal, with A through F representing 10 through 15.

On Model A modules, a rotary switch on the side of the module points to the
configured address. On Model B modules, a rotary switch is located on the top of the
module; the address is indicated by the flat side of the switch spindle.

3. If a 1720N Communication Link is being used, verify the setup as follows:

• The link can contain as many as 8 ICN interface boards each connected to a
single ICN with as many as 15 instruments. The interface board and instruments
on each ICN must have unique addresses. The hexadecimal address switch on
each interface board is factory set at 0; this allows addresses 1-15 ($1-$F) to be
assigned to the instruments via the ICN module address switch. The interface
board can be assigned any address (1-15). Be sure the interface board address
does not match the address of any instrument on the ICN.
• Note the number of each ICN. The ICNs are numbered 0 through 7 from left to
right. Earlier model links may number the ICNs 1 through 8 on the chassis,
though this address scheme is not used in the Application Builder. The ICN
number is not related to the ICN interface board address: they can have the same
numerical value.
• Note the link switch settings. The settings determine the communication
parameters for the serial port. Factory settings provide the following values:
- Odd parity, 8 data bits, and one stop bit
- 9600 baud
- Clear-to-send (CTS) permanently enabled
- RS-232 transmission standard

29
MODCELL and MOD 30ML Maintenance

COMMUNICATIONS

4. If a 1731N Mini Link or 1733N Mini Link/External is being used, verify the setup as
follows:
• The mini links provide the required interface for one ICN, and an optional interface
board supports a second ICN. Each ICN can be connected to as many as 15
instruments. The interface board and instruments on each ICN must have unique
addresses. The hexadecimal address switch on the interface board is factory set
at 0; this allows addresses 1-15 ($1-$F) to be assigned to the instruments via the
ICN module address switch. The interface board can be assigned any address (1-
15). Be sure the interface board address does not match the address of any
instrument on the ICN.
• On the 1731N link which is installed in the computer chassis, ensure that the link
address and interrupt settings are different from other ports in the PC. In most
cases, it is acceptable to share an interrupt with a parallel port.
• Note the number of each ICN. If a single ICN is connected its number is 0. The
optional second ICN is number 1. The ICN number is not related to the ICN
interface board address; they can have the same numerical value.
• Note the link jumper locations. The locations determine the communication
parameters for the two serial ports. The factory settings provide the following
values:
- 9600 baud
- No parity, 8 data bits, 1 stop bit (these parameters are not configurable)
- Clear-to-send (CTS) ignored
- RS-232 transmission standard (not configurable)

5. Verify that a wire is connected from the common of the ICN connector on the link
interface board to the common connection for the module. Be sure this wire is not
connected to earth or chassis ground. Note that the common terminal on the Mini
Link ICN connector is labeled with a ground symbol; disregard this marking because
the terminal functions as the common connection.

6. Apply power to the equipment. If the network contains a Mini Link, allow at least 30
seconds for the link to initialize.

7. Verify that the ICN has proper termination. The most common termination method
uses the 2030F ICN terminator connected to the terminal block of one instrument on
the network.

NOTE; Successful communication with any instrument on the network indicates that
the ICN is properly terminated and functioning correctly. Another method of
verifying proper ICN operation is to check the voltage pattern with an
oscilloscope. Typical voltage traces for a properly functioning ICN are shown
in Figure 10.

30
 MODCELL and MOD 30ML Maintenance

COMMUNICATIONS

24V

+ICN 13V
ICN Com 9V

0V
250 ms

24V

–ICN
ICN Com 12V
10V

0V
250 ms

Figure 10. Voltage Traces for a Correctly Functioning ICN

8. Start the Application Builder software and access the Serial Port Setup menu, Figure 4
(see Section 3.2.1 for procedure). Select the serial port that is connected to the link
and confirm that the port settings match the link configuration. If uncertain of the link
configuration, select the default configuration parameters from Table 3.

9. Access the Communications Setup menu, Figure 6, (See Section 3.2.2 for
procedure). Set the Communication Type to Link Set the ICN number and
Instrument address to match the values determined in Step 3 or 4.

10. Access the Instrument Status Display and click on the command line at the bottom of
the screen. Type R VERSION and click on Enter. This command returns the
version of any instrument connected to the ICN, even MOD 30. If the instrument
responds, confirm that the reported version agrees with the type of instrument that is
being tested. The version return data is listed in Section 3.2.5.

11. If you are unable to establish communications in Step 10 proceed as follows:

31
MODCELL and MOD 30ML Maintenance

COMMUNICATIONS

• If you are unsure of the link configuration, first access the serial port setup menu again
and change the baud rate to another setting. In most cases, the link is set at 9600 or
19200.

• If the problem still exists, change the parity setting. If a Mini Link is being used,
always set the parity at none. The data and stop bits are likely to be set at 8 and 1
respectively.

• If unable to establish communications, disconnect power and remove all analog and
communications modules, except for the ICN module being used. Restore power and
try to communicate again via the R VERSION command.

• If the problem still exists,do the following:

- Disconnect power.
- Disconnect all instruments from the ICN, other than the one being tested.
- Ensure that the address switch on the ICN module is set at a different address
than the switch on the ICN interface board in the link.
- Restore power and try to communicate again via the R VERSION command.

• If still unable to communicate, replace the ICN module, preferably with a Model B
version and terminator.

• If all previous procedures fail, replace the instrument.

4.2.2 Modbus Module Communication

Troubleshoot problems with Modbus module communication as follows:

NOTE: The extended Modbus communications required for diagnostics and downloading
is supported by the 2033N and 2034N modules only. On Modcell, the Identity
module firmware must be at least version 4 Logic, version 3 Regulatory, Batch,
Advanced. Refer to Section 9 for details of hardware and software compatibility.
1. Remove power from the instrument.

2. Note the switch settings on the Modbus module. Two rotary switches are used to
select the address. The address is indicated in hexadecimal, by the flat side of the
spindle, with A through F representing 10 through 15.

3. Set the COMM DEFAULTS switch to YES. This forces the module to communicate at
9600 baud, 8 data bits, 1 stop bit and no parity, regardless of the database
configuration.

4. If using an RS-485 module, set the TERM switch to NO. This switch provides pull-up
and pull-down resistors to stabilize the network. This function is defined by the
Modbus specification as the responsibility of the Modbus Master node, which is the
PC in this case. If the PC does not contain an RS-485 interface card with the required
bus stabilizing resistors, the TERM switch on one communications module on the
network can be set to YES to provide the required resistors.

32
 MODCELL and MOD 30ML Maintenance

COMMUNICATIONS

5. Apply power to the instrument.

6. Start the Application Builder software and access the Serial Port Setup menu, Figure 4
(see Section 3.2.1 for detailed procedure). Select the serial port that is connected to
the instrument and confirm the port settings. The standard Base Addresses are 3F8,
2F8, 3E8 and 2E8 for Com1 through Com4 respectively. If unsure of the address,
check the computer hardware manual for configuration information. Set the Baud
Rate to 9600, Data Bits to 8, Parity to None and Stop Bits to 1.

7. Access the Communications Setup Menu, Figure 6 (see Section 3.2.2 for detailed
procedure), Set the Communications Type to Extended Modbus, set the Modbus
Address to match the module setting, and select the com port to be used. The ICN
and Instrument number settings listed on the menu have no effect when modbus
communication is selected.

8. Access the Instrument Status Display and click on the command line at the bottom of
the screen. Type R VERSION and click on Enter. This command returns the version
of the instrument. If the instrument responds, confirm that the reported version agrees
with the type of instrument that is being tested. The version return data is listed in
Section 3.2.5.

9. If you are unable to establish communications in Step 8 proceed as follows:

• Disconnect power and remove all analog and communications modules, except for
the Modbus module being used. Restore power and try to communicate again via
the R VERSION command.
• If the problem still exists, disconnect all instruments from the network except the
one being tested. Restore power and try to communicate again via the R
VERSION command.
• If still unable to communicate, replace the Modbus module.
• If all previous procedures fail, replace the instrument.

4.2.3 Built-In ICN Communication

Troubleshoot problems with MOD 30ML built-in ICN communication as follows:

1. Remove power from the instrument and communications link.

2. Verify that the communications jumper in the instrument is in the correct location for
built-in communication via the ICN.

3. Verify that a communication module is not installed in instrument slots S9 and S10.

33
MODCELL and MOD 30ML Maintenance

COMMUNICATIONS

4. If a 1720N Communication Link is being used, verify the setup as follows:

• The link can contain as many as 8 ICN interface boards each connected to a
single ICN with as many as 15 instruments. The interface board and instruments
on each ICN must have unique addresses. The hexadecimal address switch on
each interface board is factory set at 0; this allows addresses 1-15 ($1-$F) to be
assigned to the instruments via the ICN module address switch. The interface
board can be assigned any address (1-15). Be sure the interface board address
does not match the address of any instrument on the ICN.
• Note the number of each ICN. The ICNs are numbered 0 through 7 from left to
right. Earlier model links may number the ICNs 1 through 8 on the chassis,
though this address scheme is not used in the Application Builder. The ICN
number is not related to the ICN interface board address: they can have the same
numerical value.
• Note the link switch settings. The settings determine the communication
parameters for the serial port. Factory settings provide the following values:
- Odd parity, 8data bits, and one stop bit
- 9600 baud
- Clear-to-send (CTS) permanently enabled
- RS-232 transmission standard

5. If a 1731N Mini Link or 1733N Mini Link/External is being used, verify the setup:
• The mini links provide the required interface for one ICN, and an optional interface
board supports a second ICN. Each ICN can be connected to as many as 15
instruments. The interface board and instruments on each ICN must have unique
addresses. The hexadecimal address switch on the interface board is factory set
at 0; this allows addresses 1-15 ($1-$F) to be assigned to the instruments via the
Device Setup display on the instrument front panel. The interface board can be
assigned any address (1-15). Be sure the interface board address does not match
the address of any instrument on the ICN.
• On the 1731N link which is installed in the computer chassis,ensure that the link
address and interrupt settings are different from other ports in the PC. In most
cases, it is acceptable to share an interrupt with a parallel port.
• Note the number of each ICN. If a single ICN is connected its number is 0. The
optional second ICN is number 1. The ICN number is not related to the ICN
interface board address: they can have the same numerical value.
• Note the link jumper locations. The locations determine the communication
parameters for the two serial ports. Factory settings provide the following values:
- 9600 baud
- No parity, 8data bits, 1 stop bit (these parameters are not configurable)
- Clear-to-send (CTS) ignored
- RS-232 transmission standard (not configurable)

34
 MODCELL and MOD 30ML Maintenance

COMMUNICATIONS

6. Verify that a wire is connected from the common of the ICN connector on the link
interface board to terminal 1 (common) on the instrument. Be sure this wire is not
connected to earth or chassis ground. Note that the common terminal on the mini link
ICN connector is labeled with a ground symbol; disregard this marking because the
terminal functions as the common connection.

7. Apply power to the equipment. If the network contains a Mini Link, allow at least 30
seconds for the link to initialize.

8. Verify that the ICN has proper termination. The most common termination method
uses the 2030F ICN terminator connected to the terminal block of one instrument on
the network.

NOTE: Successful communication with any instrument on the network indicates that
the ICN is properly terminated and functioning correctly. Another method of
verifying proper ICN operation is to check the voltage pattern with an
oscilloscope. The voltage traces for a properly functioning ICN are shown in
Figure 10.

9. Access the Device Setup display on instrument front panel and verify the following:
• The instrument being tested is set at a different ICN address than the address
switch on the ICN interface board in the link.
• ICN communication is enabled

10. Start the Application Builder software and access the Serial Port Setup menu, Figure 4
(see Section 3.2.1 for procedure). Select the serial port that is connected to the link
and confirm that the port settings match the link configuration. If uncertain of the link
configuration, select the default configuration parameters from Table 3.

11. Access the Communications Setup menu, Figure 6 (see Section 3.2.2 for procedure).
Set the Communication Type to Link . Set the ICN number and Instrument address to
match the values determined in Step 4 or 5.

12. Access the Instrument Status Display and click on the command line at the bottom of
the screen. Type R VERSION and click on Enter. This command returns the version
of any instrument connected to the ICN , even MOD 30. If the instrument responds,
confirm that the reported version agrees with the type of instrument that is being
tested. The version return data is listed in Section 3.2.5.

13. If you are unable to establish communications in Step 12 proceed as follows:

• If you are unsure of the link configuration, first access the Serial Port Setup menu
again and change the baud rate to another setting. In most cases, the link is set at
9600 or 19200. try to communicate again via the R VERSION command
• If the problem still exists, change the parity setting. If a Mini Link is being used,
always set the parity at none. The data and stop bits are likely to be set at 8 and 1
respectively and try again.
• If unable to establish communications, disconnect power and remove all analog and
communications modules. Restore power and try to communicate again via the R
VERSION command.

35
MODCELL and MOD 30ML Maintenance

COMMUNICATIONS

• If the problem still exists,do the following:

- Disconnect power.
- Disconnect all instruments from the ICN, other than the one being tested.
- Restore power and try to communicate again via the R VERSION command.
• If all previous procedures fail, replace the instrument.

4.2.4 Built-In Modbus Communication

Troubleshoot problems with MOD 30ML built-in Modbus communication as follows:

1. Remove power from the instrument.

2. Verify that the communications jumper is in the correct location for built-in
communication via either RS-232 Modbus or RS-485 Modbus.

3. Verify that a communication module is not installed in slots S9 and S10.

4. If RS-485 communication is being used, verify that the connection at the computer
(Modbus Master) is made via an RS-485 interface card containing the required bus
stabilizing resistors.

NOTE: The Port Functionality attribute of the MSC block must be configured as a
slave.

6. Apply power to the instrument.

7. Access the device setup display on the instrument front panel. Note the instrument
address and communication parameter settings, and verify that built-in (BI) MSC
communication is enabled.

8. Start the Application Builder software and access the Serial Port Setup menu, Figure 4
(see Section 3.2.1 for procedure). Select the serial port that is connected to the
instrument and confirm the port settings. The standard Base Addresses are 3F8, 2F8,
3E8 and 2E8 for Com1 through Com4 respectively. If unsure of the address, check
the computer hardware manual for configuration information. Set the Baud Rate, Data
Bits, Parity, and Stop Bits to match the instrument values noted in Step 7.

9. Access the Communications Setup menu, Figure 6 (see Section 3.2.2 for procedure).
Set the communications type to Extended Modbus. Set the Modbus Address to match
the instrument setting and select the com port to be used. The ICN and Instrument
number settings listed on the menu have no effect when modbus communication is
selected.

10. Access the Instrument Status Display and click on the command line at the bottom of
the screen. Type R VERSION and click on Enter. This command returns the version
of the instrument. If the instrument responds, confirm that the reported version agrees
with the type of instrument that is being tested. The version return data is listed in
Section 3.2.5.

36
 MODCELL and MOD 30ML Maintenance

COMMUNICATIONS

11. If you are unable to establish communications in Step 10, proceed as follows:
• Disconnect power and remove all analog and communications modules. Restore
power and try to communicate again via the R VERSION command.
• If the problem still exists,do the following:
- Disconnect power.
- Disconnect all instruments from the network, other than the one being tested.
- Restore power and try to communicate again via the R VERSION command.
• If still unable to communicate, replace the instrument.

4.3 APPLICATION BUILDER/INSTRUMENT COMMUNICATION MESSAGES

When using the Application Builder Software to communicate with a MODCELL or MOD
30ML instrument, the software provides numerous messages which inform the user about
the communication activity. The messages can appear during database downloading,
uploading or importing activities , and during communication activity initiated through the
instrument status display. They appear either in pop-up windows in the display
workspace or on the status bar at the bottom of the display screen.

These messages include both status and error information. The status messages simply
provide the user with information about a specific communication activity. For example,
the message Downloading notifies the user that the software is in the process of
transmitting a successfully compiled data base to an instrument. The error messages
provide the user with information about communication problems. For example, the
message No response was received notifies the user that the personal computer is not
communicating with the instrument, possibly because the configured ICN or Modbus
address is incorrect.

A list of the messages is provided in Table 7. The messages are listed in alphabetical
order. The table includes information about the probable cause of each message
appearance and recommended action as appropriate.

Table 7. Communication Messages, Cause and Recommended Action

Message Probable Cause Action

Attribute not writeable Attribute is read only. Check the database reference
block for valid read/write data(See
Section 1.5).
Block creation failed 1. Unable to decompile 1. Try upload operation again.
instrument database (.ID1) file
during upload from instrument
to Application Builder.

2. Unable to decompile 1706S 2. Be sure the .ID1 file contains a

Configurator .ID1 file during valid instrument database, then
import into Application Builder. try import operation again.
Cannot display menu Insufficient memory. Provide more memory.

37
MODCELL and MOD 30ML Maintenance

COMMUNICATIONS

Table 7. Communication Messages, Cause and Recommended Action (Cont’d)

Message Probable Cause Action

Cannot display status menu 1. Insufficient memory. 1. Provide more memory.
2. KT.MN file has been deleted. 2. Reinstall Application Builder.
Cannot open .ID1 or .ID2 file 1. Instrument data base file (.ID1) 1 Repeat compile activity to
was deleted or not created. create new file, then try to
download again (see IB-
23H141, Section 5.9).
2. LCP data base file (.ID2) was 2. Repeat data base upload
deleted or not created. using LCP Utility, then try to
download again (see IB-
23H141, Section 4.6.6).
Cannot open file SIO. DAT The Serial I/O Data file containing Perform serial port setup to create
communication parameters has new file (See Section 3.2.1).
been deleted or the serial port
setup has not been completed.
Checksum error 1. Momentary fault in a link 1. Try again.
communication.
2. Incorrect Serial Port Setup . 2. Check Serial Port Setup (see
Section 3.2.1).
CRC error 1. Momentary fault in an 1. Try again.
Extended Modbus
communication.
2. Incorrect Serial Port Setup . 2. Check Serial Port Setup (see
Section 3.2.1).
Cross reference table 1. Unable to decompile 1. Try upload operation again.
creation failed instrument database (.ID1) file
during upload from instrument
to Application Builder.

2. Unable to decompile 1706S 2. Be sure the .ID1 file contains a

Configurator .ID1 file during valid instrument database, then
import into Application Builder. try import operation again.
Data comparison error Data received by Communications Check Serial Port Setup (see
Link does not match data originally Section 3.2.1), then try again.
written due to incorrect serial port
setup, or momentary
communication fault.
Database file exists. A save operation is requested for Answer yes or no.
Overwrite? an existing data base.
Database not loaded Local Control Panel (LCP) data Use LCP utility to make data base
base has not been uploaded or available for download
loaded from disk. (see IB-23H141, Section 4.6.6).

38
 MODCELL and MOD 30ML Maintenance

COMMUNICATIONS

Table 7. Communication Messages, Cause and Recommended Action (Cont’d)

Message Probable Cause Action

Database not supported by Database being uploaded is not Obtain Application Builder with
this algorithm set supported by the configuration required configuration capability.
capability of the Application Builder There are 3 configuration types:
software. For example, a • MODCELL only
MODCELL database cannot be
• MOD 30ML only
uploaded if the Application Builder
has only the MOD 30ML • MODCELL and
configuration capability. MOD 30ML

NOTE:
Selection of the About icon in
the Application Builder tool bar
displays configuration
capability of the installed
software.
Deferred response overrun, 1. Momentary communication 1. Try again.
parity or framing error fault.
2. Parity mismatch between 2. Check that parity configured in
instrument and Serial Port Setup menu, Figure
Communications Link. 4, matches setting of parity
status switch in link.
Do you wish to retain block This message appears whenever a If a compound is saved and then
occurrence numbers in the compound is loaded. loaded within the same database
compound being loaded? for the purpose of moving (not
copying) a group of blocks from
one location to another in the
workspace, answer YES.
Otherwise answer NO because
retaining occurrence numbers
leads to duplicates if blocks with
the same numbers already exist in
the database.
Download completed without Information only None
error
Downloading Information only None
Ending, changing instrument Information only (3-10second None
state duration)

39
MODCELL and MOD 30ML Maintenance

COMMUNICATIONS

Table 7. Communication Messages, Cause and Recommended Action (Cont’d)

Message Probable Cause Action

Error reading .ID1 file 1. Unable to decompile 1. Try upload operation again.
instrument database (.ID1) file
during upload from instrument
to Application builder.

2. Unable to decompile 1706S 2. Be sure the .ID1 file contains a

Configurator .ID1 file during valid instrument database, then
import into Application Builder. try import operation again.
Error reading .ID1 or .ID2 file 1. There is an error in reading 1. Repeat compile activity to
the instrument Data Base file create new file , then try to
(.ID1) from disk. download again.
2. There is an error in reading 2. Repeat data base upload using
the LCP Data Base file (.ID2) LCP Utility to create new file,
from disk. then try to download again.
Error writing .ID1 or .ID2 file Instrument data base file (.ID1) or
LCP data base file (.ID2) cannot
accept data because:
1. disk is full. 1. Provide more disk space
2. Wrong drive selected. 2. Select correct drive
3. Diskette not installed. 3. Install diskette.
Error writing .SD1 file Shutdown data file (.SD1) cannot Provide more disk space.
accept data because disk is full.
ICN timeout - no response 1. Instrument power is off. 1. Turn on power.
from instrument
2. Configured ICN number or 2. Check communications setup
instrument number does not (see Section 3.2.2).
exist.
3. Termination facility on front of 3. Tighten housing screw,
MODCELL Eurocard Figure 1.
instrument not properly
engaged.
4. MOD 30ML instrument not 4. Push instrument into housing
fully seated in its housing. and tighter front panel retaining
screws.
Import aborted Information only This message follows the report of
error(s) which must be corrected
before the import can be
successfully completed.

40
 MODCELL and MOD 30ML Maintenance

COMMUNICATIONS

Table 7. Communication Messages, Cause and Recommended Action (Cont’d)

Message Probable Cause Action

Import completed without Information only None
error
In service manual RUN/SERV switch is in SERV. Set switch at RUN
In valid data type Specified data type is invalid. Correct entry and try again. See
e.g., RS IF1,TIME Section 3.2.5.
or
RS EX1,I3 F
(RS can only be used with hex or
ASCII data)
Inst in hold state A write command to change the If process condition is ready for
instrument STATE to RUN cannot normal operation, change switch
be accepted because the setting to RUN.
RUN/SERV switch is set at SERV.
Instrument is not a LCP Upload or download of LCP data Verify that instrument at address
base failed because instrument at configured on LCP Utility menu is
the configured address is not an an LCP
LCP.
Instrument is not a MODCELL A MOD 30 instrument or LCP is Verify that instrument at the
or connected at the specified ICN specified address is a MODCELL
MOD 30ML address. or MOD 30ML.

Instrument reports an error 1. Block containing the attribute 1. Configure the required block.
reading that attribute is not configured.
2. Attribute does not exist in the 2. Check block configuration.
specified block.
Instrument state in transition Information only. An instrument None
state transition is in process.
instrument version too low to Data base being downloaded Replace instrument identity module
run data base contains functions not supported with a version which accepts the
by the instrument. data base, or modify the
configuration to run on the existing
instrument version.
Interpreting database Information only None
Invalid ACK Diagnostic acknowledgement Retype command using correct
specifies nonexistent block number (See Section 3.2.5)
occurrence number, or inactive
diagnostic number.
Invalid ASCII string Specified ASCII data is invalid. Correct entry and try again.
e.g., W IF1,USRTAG 1
(ASCII data expected; 1 specified)

41
MODCELL and MOD 30ML Maintenance

COMMUNICATIONS

Table 7. Communication Messages, Cause and Recommended Action (Cont’d)

Message Probable Cause Action

Invalid attribute An invalid attribute name was Check the database reference
specified. block for list of valid attributes
e.g. ,R IF1. COMMAND (See Section 1.5).
(Command is not a valid attribute
for the IF block attribute.)
Invalid block checksums 1. Instrument is not in default 1. Answer YES to the request to
state when its database is continue. The upload will be
Followed by:
being uploaded to the successfully completed if the
Possibly invalid database. Do
Application Builder. The error database can be decompiled.
you wish to continue?
message appears because the
checksums are changing
during upload.

2. Unable to decompile 2. Answer NO to the request to

instrument database (.ID1) file continue and try upload
during upload from instrument operation again.
to Application Builder.

3. Unable to decompile 1706S 3. Answer NO to the request to

Configurator .ID1 file during continue. Be sure the .ID1 file
import into Application Builder. contains a valid instrument
database, then try import
operation again.
Invalid block type An invalid block type was Correct entry and try again.
specified.
e.g., W IFF1,CMD 1
(IF block is misspelled IFF)
Invalid block type or An invalid block type or Correct entry and try again.
occurrence number occurrence number was specified:
e.g., ACK AI1 5
(AI is invalid block type for a Built-
in Analog Input block; AIN is
correct)
e.g., ACK AIN9 5
(9 is an invalid occurrence number
for a Built-in Analog Input block)

42
 MODCELL and MOD 30ML Maintenance

COMMUNICATIONS

Table 7. Communication Messages, Cause and Recommended Action (Cont’d)

Message Probable Cause Action

Invalid constant A data constant entered in an
expression is invalid:
1. Error occurs during a compile 1. Enter a valid data constant.
activity.

2. Error occurs during an import 2. Obtain a valid database.

of a corrupt database.
Invalid database header 1. Unable to decompile 1. Try upload operation again.
instrument database (.ID1) file
during upload from instrument
to Application Builder.

2. Unable to decompile 1706S 2. Be sure the .ID1 file contains a

Configurator .ID1 file during valid instrument database, then
import into Application Builder. try import operation again.

Invalid diagnostic code Specified diagnostic number is Correct entry and try again. Refer
invalid. to Section 7 for a list of code
e.g., ACK AIN1 A numbers.
(Letter A is not valid, code must
be a number)
Invalid entry A command or part of a command Correct entry and try again.
is not understood.
e.g., W TIM 2:04:00.0
(TIME is misspelled TIM.)
Invalid hexadecimal number Specified hex number is invalid. Correct entry and try again.
e.g., W EX1,I3 $G H
(G is not a valid hex digit)
Invalid message function Momentary fault in Modbus Try again.
code communication.

Invalid mode The write message is not accepted Change the mode attribute to the
because of the state of the mode appropriate state.
attribute.
Invalid occurrence number An invalid block occurrence Correct entry and try again.
number was specified. Occurrence numbers are listed in
e.g. , R SE2,PKDLEN the Cross Reference Database
(block must be SE1 because there (.CRF) file which is created by the
is only one SE block in a Application Builder after a
database) database is successfully compiled.

43
MODCELL and MOD 30ML Maintenance

COMMUNICATIONS

Table 7. Communication Messages, Cause and Recommended Action (Cont’d)

Message Probable Cause Action

Invalid parameter Invalid write data was specified. Check the database reference
e.g. , W EX1,STATE 4 block for valid values (See
(4 is not a valid state value in the Section 1.5).
EX block.
Invalid RETURNING DATA Response from Communications Check Serial Port Setup (see
message was returned Link has an invalid message code. Section 3.2.1), then try again.
Invalid serial port base The base address specified in the Enter correct address in Serial
address Serial Port Setup menu is invalid Port Setup menu. (see Section
for the PC being used. 3.2.1)
Invalid setpoint state Writes to the PID block SETPOINT Check the database reference
are allowed only if the SP MODE book for detailed description of
STATUS attribute is FAULT or attributes (See Section 1.5).
LOCAL, or if the PID block state is
DEBUG, or if the loop state is
DEBUG.
Invalid table checksums 1. Instrument is not in default 1. Answer YES to the request to
Followed by: state when its database is continue. The upload will be
being uploaded to the successfully completed if the
Possibly invalid database. Do
Application Builder. The error database can be decompiled.
you wish to continue?
message appears because the
checksums are changing
during upload.

2. Unable to decompile 2. Answer NO to the request to

instrument database (.ID1) file continue and try upload
during upload from instrument operation again.
to Application Builder.

3. Unable to decompile 1706S 3. Answer NO to the request to

Configurator .ID1 file during continue. Be sure the .ID1 file
import into Application Builder. contains a valid instrument
database, then try import
operation again.
Invalid write by cfg. Because of the way the block is Check the configuration of the
configured, the attribute is not block.
writeable.

44
 MODCELL and MOD 30ML Maintenance

COMMUNICATIONS

Table 7. Communication Messages, Cause and Recommended Action (Cont’d)

Message Probable Cause Action

LCP not displaying main page Attempting a database upload or Exit current LCP display to return
(Master Display) download using the LCP Utility to Master Display.
when the LCP is not showing the
Master Display.
Main database invalid 1. Information 1. Read diagnostics to determine
specific cause.

2. Communication port mismatch 2 Verify that database contains

detected during database an ICN block or MSC block
download. which matches the instrument
communications module.
Matching includes slot
numbers, module type, and
module address switch setting
unless ANY is configured.
3. Instrument is unconfigured (no 3. Load a valid database.
valid database).

4. Main database checksum 4.Load a valid database.

error.
Memory module (or LCP A memory module has not been Install memory module.
backup database) not present installed in the instrument.
Module database invalid 1. Information about memory 1. Read diagnostics to determine
module. specific cause.

2. Communications port 2. Verify that database contains

mismatch detected during an ICN block or MSC block
download of backup main which matches the instrument
database from memory communications module.
module. Matching includes slot
numbers, module type, and
module address switch setting
unless ANY is configured.

3. No valid database in module. 3. Load a valid module database.

4. Module database checksum 4. Same as above.

error.

5 Module database version error. 5. Same as above.

45
MODCELL and MOD 30ML Maintenance

COMMUNICATIONS

Table 7. Communication Messages, Cause and Recommended Action (Cont’d)

Message Probable Cause Action

Module switch in upload The memory module NORMAL- Change switch setting if required.
MODULE LOAD switch is set at
MODULE LOAD.
Module write protected Memory module READ/WRITE- If overwriting is required, change
READ ONLY switch is set at switch setting to READ/WRITE
READ ONLY to protect backup
database from being overwritten.
No response was received 1. Specified ICN or Modbus 1. Enter correct address on
address is not correct. Communications Setup menu
(See Section 3.2.2).
2. Instrument is not connected to 2. Check network connections.
network.
Not a MODCELL database 1. Unable to decompile 1. Try upload operation again.
instrument database (.ID1) file
during upload from instrument
to Application builder.

2. Unable to decompile 1706S 2. Be sure the .ID1 file contains a

Configurator .ID1 file during valid instrument database, then
import into Application Builder. try import operation again.
Not authorized source Another source is in control of the Wait for the other source to
loop. release control, or issue an
override control message.
Not enough fields for a Insufficient data was specified in a Correct entry and try again.
multiple field entry command.
e.g., W EX1,I3 1.2
(data type not specified;
W EX1,I3 1.2 F is correct)
Operator missing or An operator entered in an
improperly used expression is wrong or missing:

1. Error occurs during a compile 1. Enter a valid operator.

activity.

2. Error occurs during an import 2. Obtain a valid database.

of a corrupt database.

46
 MODCELL and MOD 30ML Maintenance

COMMUNICATIONS

Table 7. Communication Messages, Cause and Recommended Action (Cont’d)

Message Probable Cause Action

Out of range A specified value is out of range. Correct the specified value and try
e.g., W EX1,I3 70000 C again.
(70000 is out of range for a count
data type)
Previous shutdown fault A shutdown fault was detected and Refer to Diagnosing Shutdown
has not been acknowledged. faults, Section 6.
Protection key not found Software protection key not Press any key to use application
installed in parallel port of builder in evaluation mode or
computer running Application install protection key (see IB-
Builder Software. 23H141, Section 2).
Protection key not found Protection key supplied with the Connect the protection key to the
software has not been installed. computer parallel connector and
try again.
Reading instrument version Information only at start of None
download activity.
Response overrun, parity or 1. Momentary communications 1. Try again.
framing error fault.
2. Parity mismatch between 2. Check that parity configured in
Note: The message
instrument and Serial Port Setup menu, Figure
Retrying may appear
communications link. 4, matches setting of parity
in response to these
status switch in link.
problems. See
below. 3. Parity mismatch between 3. Check that parity configured in
instrument and Extended Serial Port Setup menu, Figure
Modbus network. 4, matches parity configured
in MSC block.
4. Application Builder is being run 4. Use a PIF file to run strategy
through a DOS shell in EXE in text, full screen,
Windows. exclusive mode. Memory
requirements are: 0 required
and 100 desired; set EMS
memory at 0,0 and XMS
memory at 0,100. Set
background priority at 50 and
foreground at 10000. Use
high memory area and emulate
text mode.

47
MODCELL and MOD 30ML Maintenance

COMMUNICATIONS

Table 7. Communication Messages, Cause and Recommended Action (Cont’d)

Message Probable Cause Action

Retrying 1. Information only; a message 1. None if message is completed
error was detected and the successfully.
program is trying to complete
the message successfully.
2. Response overrun, parity or 2. See causes and actions
framing error above.
Save database, so that This message appears at the end The user should usually answer
occurrence numbers of each compile activity. The YES because not saving leads to
assigned to blocks will be reason is as follows: reassignment of numbers to any
saved? blocks with occurrence number
During configuration, blocks added zero at the next compile, and this
to the graphical database are assignment may differ from the
assigned an invalid occurrence previous compile.
number of zero. During the
compile activity these blocks are
assigned valid, non-zero
occurrence numbers. Valid
occurrence numbers, once
assigned, are not reassigned in
subsequent compiles. It is
important that occurrence numbers
not be reassigned because other
systems, such as the LCP or PC-
30, reference blocks by block type
and occurrence number. If these
numbers are allowed to change,
these systems would no longer
reference the correct blocks.
Scan message buffer full Information Try message again.
Selection array creation failed Same as above Same as above
Starting, changing instrument Information only (3-10 second None
state duration).
STX not found at start of Start of transmission code missing Check Serial Port Setup (see
returned message due to incorrect serial port setup, Section 3.1), then try again.
or momentary communication
fault.

48
 MODCELL and MOD 30ML Maintenance

COMMUNICATIONS

Table 7. Communication Messages, Cause and Recommended Action (Cont’d)

Message Probable Cause Action

Time expired, message One of the following messages has Check configured value for the
discarded been sent to the instrument: Write Message Timeout attribute in
• WRITE_ATTRIBUTE the MSC block.
• SEQ_WRITE_ATTRIBUTE
• TAKE_CONTROL
• RELEASE_CONTROL
• OVERRIDE_CONTROL.
These messages cannot be
processed until the scan task that
they are directed to is idle.
Therefore, when the Write
Message Action attribute in the
MSC block is set for discard, and
the Write Message Timeout
attribute expires, the message is
discarded and this error message
is returned.
Time expired, message This is an Extended Modbus write Check configured value for the
processed timeout NAK code. It applies to the Write Message Timeout attribute in
following messages: the MSC block.
• WRITE_ATTRIBUTE,
• SEQ_WRITE_ATTRIBUTE,
• TAKE_CONTROL,
• RELEASE_CONTROL
• OVERRIDE_CONTROL.
These messages cannot be
processed until the scan task that
they are directed to is idle.
Therefore, when the Write
Message Action attribute in the
MSC block is set for process, and
the Write Message Timeout
attribute expires, this error
message is returned and the
message will be processed when it
can but it may or may not be
accepted..

49
MODCELL and MOD 30ML Maintenance

COMMUNICATIONS

Table 7. Communication Messages, Cause and Recommended Action (Cont’d)

Message Probable Cause Action

Too many characters Too many ASCII or hex characters Shorten string and try again.
specified.
e.g., W IF1,USRTAG ------
string----------
(USRTAG specifies a string in
excess of 25 characters)
Unable to load LSP.DLL Logical Source Pointer Dynamic Reinstall Application Builder
Link Library file (LSP.DLL) has
been deleted.
Unable to load MASTER .DLL Master Dynamic Link Library file Reinstall Application Builder.
(MASTER.DLL) containing Help
information has been deleted.
Unable to load REALSIO.DLL Real serial I/O Dynamic Link Reinstall Application Builder.
Library file (REALSIO.DLL) has
been deleted.
Unrecognized database Attempting to download a data Use a compatible version of the
version base previously configured on a Application Builder, or reconfigure
newer version of the Application data base on current version of
Builder software. Application Builder.
Unrecognized database Database being uploaded has Obtain a version of the Application
version been configured on a newer Builder which supports the
version of Application Builder instrument database. See
software. Section 9, Table 14 for
compatibility of instrument and
software versions.
Unrecognized instrument Older version of Application builder Obtain new version of application
version software does not recognize builder.
current instrument version at
download.
Valid date is An invalid date was specified. Correct entry and try again.
M,month/day/year or e.g., W DATE 12/1/96
D,day/month/year (W DATE M,12/1/96 is correct)
Valid time is hh:min:ss.sss An invalid time was specified. Correct entry and try again.
(hours, minutes, seconds) e.g., W TIME M,12/1/96
(specified date instead of time)
Validating database Information only None

50
 MODCELL and MOD 30ML Maintenance

DIAGNOSING I/O MODULE PROBLEMS

SECTION 5
DIAGNOSING ANALOG I/O MODULE PROBLEMS

5.1 GENERAL
The status display in the Application Builder Software allows access to Extended Error
Codes which can help trouble shoot the instrument. The extended error data includes
both status information and fault information for analog I/O modules.

The extended error code is a two byte (16 bit) code from the module that is presented as
a count value. When the status display in the Application Builder Software is used to view
the code, the decimal count value is shown and the program automatically converts the
value to binary and displays a text message for each status bit and for any error bit
indicating an error. An example of the data for a WRIM module containing a fault is shown
in Figure 7. The count value, 14368, has been decoded to provide six status messages
and one error message. A complete list of the extended error code messages with
recommended action for fault conditions is shown in Tables 9 and 10.

NOTE: When PC-30 or a similar host system is used to view the error codes, the host
reads the Extended Error (EXTERR) attribute and returns only the decimal count
value. The user must program the host software to decode (or manually decode)
the bitmapped error pattern shown in Table 9 or 10.

5.2 READING EXTENDED ERROR CODES

If there is a suspected problem with either an analog input or output module, proceed as
follows:
1. Determine the database occurrence number of the I/O module block for the problem
module:
• Click on the I/O Graphic icon in the Tool Bar to access the graphical
representation of I/O module slots.
• Query the required slot by clicking the right mouse key on the slot number. A
window appears listing the tag name and type of module occupying the slot.
• Look up the tag name in the .CRF file to determine the block occurrence number.

2. Verify that the correct module is in the slot:

• Access the Instrument Status display.
• Read the module ID by typing the following on the command line:
R (module)(x),MODID
where (module) is the mnemonic for the type of module being addressed and (x)
is the occurrence number of the module block. For example, to read the ID for
occurrence number 1 of a VCIM module, type:
R VCIM1,MODID
• Compare the code returned to the ID codes listed in Table 8 to confirm that the
module is correct.

51
MODCELL and MOD 30ML Maintenance

DIAGNOSING I/O MODULE PROBLEMS

Table 8. I/O Module Identification Codes

Module Type Catalog No. ID Code

Voltage Input 2001A $FE0000
Current Input 2002A $FE0100
Current Input with 2-wire 2012A $FE0400
transmitter power
Thermocouple 2013A $FE0200
Cold Junction comp. (CJC) 2010A $FE0300
RTD, 2-wire 2009A $FE0500
RTD, 3-wire 2009A $FE0600
Analog Output 2003N $FD0500

3. Read the extended error from the module as follows:

• Type the following:
R (module)(x),EXTERR
where (module) and (x) are the same as in Step 2 For example, to read the
extended error for occurrence number 1 of a WRIM module, type:
R WRIM1,EXTERR

• Observe the data returned. An example of the data for a WRIM module with a
fault is shown in Figure 7. The decimal error code number, 14368, is converted to
a 16-bit binary number in which one group of bits provide status information and
the second group indicates errors. The software converts the decimal code and
groups the information as Status bits and Error Bits as shown in Figure 7.

4. Refer to Section 5.3 for information on interpreting the error code data.

52
 MODCELL and MOD 30ML Maintenance

DIAGNOSING I/O MODULE PROBLEMS

Figure 10. Example of Extended Error Code Data for a WRIM Module

5.3 INTERPRETING EXTENDED ERROR CODE DATA

Each analog I/O module updates the extended error data in the database only when an
error occurs. Thus, the error data returned when reading EXTERR represents one of
three conditions:
1. The reported data is current and there is a problem in the module.
2. The reported data applies to a previously corrected error and the database has not
been updated because a new error has not occurred.
3. The reported data is 0 (no error) because no error has occurred since the last
database download from the Application Builder. The EXTERR value is always set at
0 on download.

If condition 1 or 2 exists, determine if the error is current by writing a 0 to the EXTERR

attribute. If a current problem exists, a subsequent read should return the error code
number instead of the 0.

If condition 2 or 3 exists the data is not current and should be ignored. Also note that
because the data is not current, the reported Status Bit information may not represent the
actual current status of the module.

When it has been established that a current problem exists, refer to Table 10 or 11 for
additional information and recommended action.

53
MODCELL and MOD 30ML Maintenance

DIAGNOSING I/O MODULE PROBLEMS

Table 9. Analog Input Module Extended Error (EXTERR) Codes

Bit/Value Status Display Message Problem Action

15/1 Conversion overrange 1. Status report 1. None
2. Upscale burnout 2. Repair input circuit
15/0 No message ----------------- -----------------
14/1 Conversion underrange Status report None
14/0 No message ----------------- -----------------
13/1 Conversion complete Status report None
13/0 Conversion incomplete Status report None
12/1 Global error is indicated An error has been detected See error messages (bits 0-6)
12/0 No message No error None
11/1 Calculations performed in Status report None
module
11/0 Calculations not Status report None
performed in module
10/1 Line Frequency is 50 Hz Status report None
10/0 Line Frequency is 60 Hz Status report None
9/1 High range calibration Status report None
data loaded
9/0 Low range calibration Status report None
data loaded
8/1 Conversion range is high Status report None
8/0 Conversion range is low Status report None
7 Not used ----------------- -----------------
6/1* A/D converter error Fault in module Replace module
5/1* UART error Fault in module Replace module
4/1* Calibration data error Fault in module Replace module
3/1* EEPROM error Fault in module Replace module
2/1* Host communications Communications error Replace module
register range error
1/1* Host communications Communications error Acknowledge,
checksum errors then try again
0/1* UART timeout Fault in module Replace module
*0=No error

54
 MODCELL and MOD 30ML Maintenance

DIAGNOSING I/O MODULE PROBLEMS

Table 10. Analog Output Module Extended Error (EXTERR) Codes

Bit/Value Status Display Message Problem Action

15 Unused ----------------- -----------------
14/1 Readback is zero 1. Incorrect connection to 1. Verify connections
module terminals (see IB-23C600)

2. Fault in module 2. Replace module

14/0 No message Readback is OK None
13 Unused ----------------- -----------------
12/1 Global error is indicated An error has been detected See error messages (bits 0-6)
12/0 No message No error None
11/1 Readback is invalid Fault in module Replace module
11/0 No message Readback is OK None
10/1 Readback is out of range Fault in module Replace module
10/0 No message Readback is OK None
9/1 In calibration mode Status report None
9/0 In standard mode Status report None
8 Unused ----------------- -----------------
7/1* Power-up or watchdog 1. Power-up not 1. Acknowledge power-up
timeout acknowledged
2. Acknowledge does not 2. Replace module
clear power-up.
6/1* Configuration checksum Fault in module Replace module
error
5/1* Host communications Fault in module Replace module
invalid command error
4/1* EEPROM Calibration data Fault in module Replace module
error
3/1* EEPROM Fault in module Replace module
communications error
2/1* Host communications Instrument trying to write to If error is repeated replace
register range error unauthorized register module
1/1* Host communications Fault in module Replace module
checksum errors
0/1* Failsafe timeout Fault in module Replace module
*0=No error

55
MODCELL and MOD 30ML Maintenance

DIAGNOSING I/O MODULE PROBLEMS

5.4 COMMON MODULE ERRORS

Some common module errors and their decimal code numbers are as follows:

• Analog Input Modules

43766 - Module over range (status data)
27392 - Module under range (status data)
15136 - COPS UART failure, BADC crystal not operational (replace module)
15168 - A/D converter failure (replace module)

• Analog Output Modules

3072 - Daughter board failure (replace module)
2048 - Circuit board failure (replace module)
19456 - Circuit board failure (replace module)
4244 - Watchdog failure (replace module)
22656 - Readback failure with watchdog; daughter board failure (replace module)

56
 MODCELL and MOD 30ML Maintenance

DIAGNOSING SHUTDOWN FAULTS

SECTION 6
DIAGNOSING SHUTDOWN FAULTS

6.1 SHUTDOWN INFORMATION

When a MODCELL or MOD 30 ML instrument shuts down for any reason, status
information is saved in the instrument data base. If a memory module is installed, and its
switch is in the READ/WRITE position, a copy of the status information is also saved in the
module. This saved information can be interpreted by ABB Instrumentation support
personnel to determine the cause of the shutdown.

If an instrument with a memory module shuts down (watchdogs for example) and cannot
run again, it may still be possible to read the shutdown information in the memory module
using the procedure in Section 6.2.3.

When a shutdown fault occurs, the instrument reacts as follows:

• MODCELL
The red status LED turns on, the green LED turns off, and shutdown information is
stored in the instrument memory. Also, the instrument stops communicating and all
outputs go to their configured failsafe values.

• MOD 30ML
The beeper sounds, the red alarm indicator flashes, the word FAILURE appears on the
display, the control keys become inoperative, and shutdown information is stored in
the instrument memory. Also, the instrument stops communicating and all outputs go
to their configured failsafe values.

Use the method described in one of the following sections to obtain a record of the
shutdown fault information, and transmit the data to ABB Instrumentation support
personnel for analysis.

6.2 RECORDING SHUTDOWN INFORMATION

Select a method of recording the shutdown information as follows:

• For Modcell instruments, use the Application Builder Method, Section 6.2.1.

• For a MOD 30ML instrument which can be connected to a PC running the Application
Builder software, use the Application Builder Method, Section 6.2.1.

• For a MOD 30ML instrument without the Application Builder, use the MOD 30ML
Display Method, Section 6.2.2.

• The Memory Module Method, Section 6.2.3, is used only as an alternate approach
when specified in one of the other methods.

57
MODCELL and MOD 30ML Maintenance

DIAGNOSING SHUTDOWN FAULTS

6.2.1 Application Builder Method

After an instrument shutdown, obtain a record of the shutdown data using the following
procedure:

1. Turn off power to the instrument, then turn power back on.

2. Start the Application Builder Software. If communication with the instrument is via an
RS-232 or RS-485 port, the default parameters (9600 baud, no parity, 8 data bits, 1
stop bit) must be used. See Section 3 for the software startup procedure.

3. Access the Instrument Status display in the Application Builder.

4. On the status display command line, type the command R SD and click on ENTER. A
display providing shutdown data should appear.
• If the display appears, go to with Step 6.
• If the display does not appear and a memory module is present, continue with
Step 5.
• If a memory module is not installed, and the shutdown display cannot be obtained,
return the instrument for repair.

5. Check the memory module as follows:

• Remove the module and repeat the R SD command.
• If the shutdown display now appears, the memory module is faulty. Go to Step 11
• If the shutdown display still does not appear, it may be possible to obtain the
shutdown information from the module. Use the Memory Module Method,
Section 6.2.3, and return the instrument for repair.

6. Make a copy of the shutdown record form at the end of this section. The form
illustrates the shutdown display with blank data fields.
NOTES: If a facility for printing the display screen is available, it can be used to
generate a copy of the shutdown data. Starting with Application Builder 4.01,
the print button on the Status Display can be used to print the shutdown
record (or anything else that appears on the Status Display).
Starting with Application Builder 4.00, when the R SD command is issued, the
shutdown record is saved as a text file in the current directory. It is given the
instrument tag name and the extension SD1. If this file already exists, it is
overwritten. The current directory is the directory in which a database was
most recently saved or loaded, or if no save or load has taken place, the
directory from which the Application Builder was started.

7. Fill in the blank fields on the copy using the data from the display.

8. Type the command R VERSION and click on ENTER. The instrument version data
appears near the bottom of the status display.

9. Record the version data in the space provided on the form.

58
 MODCELL and MOD 30ML Maintenance

DIAGNOSING SHUTDOWN FAULTS

10. Fax a copy of the completed shutdown information form to:

ABB Instrumentation
Advanced Control Support
FAX: 716-273-6242

11. To restart the database, proceed as follows:

CAUTION This procedure can cause the instrument to start up in the RUN state. Be
sure the process can safely accept this operating condition before proceeding.
• Be sure all shutdown information has been recorded; the following commands
clear all previous shutdown data.
• Type the command ACK SD and click on ENTER to acknowledge the instrument
shutdown.
• If there is a Portable Memory Module in the instrument, and its switch is set at
READ/WRITE, type the command RESET and click on Enter to clear the
shutdown information from the data base in the memory module.
• For a Modcell instrument:
- Observe the status LEDs. The red LED should turn off unless there is still an
active problem in the instrument. The green LED remains on indicating
normal operation.
- If the red led remains on, use the R DIAGS (read diagnostics) command to get
a listing of all active and unacknowledged diagnostics. Refer to Section 7 for
descriptions of diagnostic event codes.
• For a MOD 30ML instrument:
- Observe the display. Depending upon the instrument configuration, either the
Device Status display or a user configured display will appear. The alarm light
should be off unless there is still an active problem in the instrument.
- If the alarm light is on or flashing, press the alarm key to access the diagnostic
alarm display. The display shows the diagnostic event code number and block
type. The diagnostics can also be viewed via the R DIAGS command from
the Application Builder. Refer to Section 7 for descriptions of diagnostic
event codes.

6.2.2 MOD 30ML Display Method

After shutdown of a MOD 30ML instrument, obtain shutdown data using the following
procedure:
NOTE Use this method of recording shutdown information only when the instrument
cannot be connected to a PC running the Application Builder software. The
application builder method provides more comprehensive shutdown data.
1. Turn off power to the instrument; if there is a memory module installed, remove it.

2. Turn power back on. The device status [DEV STAT] display, Figure 8, should
appear.
• If the display appears continue with Step 2.
• If a different display appears, press and hold the TAG key to obtain the device
display, then continue with Step 2.
• If the front panel keys are inactive and the device status display cannot be
obtained, the instrument must be returned for repair.

59
MODCELL and MOD 30ML Maintenance

DIAGNOSING SHUTDOWN FAULTS

3. Press the down arrow key to enter the status sequence, then press [NXT] to obtain
the [SHUTDOWN] entry display. Line 6 displays [YES] indicting that a shutdown
condition exists. Shutdown information is provided on the next 4 displays (Shutdown
pages 1-4). A form for recording the data on these pages is provided at the end of
this section.

4. Make a copy of the form and record the shutdown data as follows:

• Press the down arrow key to advance to page 1 and record the data displayed on
lines 1 and 2.

• Press NXT to advance through pages 2, 3 and 4 and record the data from each
page.

5 After completing the shutdown data record , determine the instrument firmware and
display version numbers as follows:

• Press the TAG key to return to the device status [DEV STAT] display.

• Press [NXT] repeatedly until [ABOUT] appears on Line 6.

• Press the down arrow key to obtain the firmware version and record the version
number.

• Press [NXT] to obtain the display version and record the version number.

• Press the up arrow key to return to the [ABOUT] display, then press [NXT]
repeatedly until the device status display appears.

6. Fax a copy of the completed shutdown information form to:

ABB Instrumentation
Advanced Control Support
FAX: 716-273-6242

7. To restart the database, proceed as follows:

CAUTION This procedure can cause the instrument to start up in the RUN state. Be
sure the process can safely accept this operating condition before proceeding.
• Be sure all shutdown information has been recorded; the following commands
clear all previous shutdown data.
• From the device status display, press the down arrow to move down to the next
display, then press [NXT] to obtain the [SHUTDOWN] entry display.
• Press the down arrow key to advance to shutdown page 1, then press [NXT]
repeatedly to advance to shutdown page 5 with [ACK SD] displayed on Line 2.
• Press the down arrow key to select [YES]. This action acknowledges the
shutdown condition, clears registers and should restart the instrument.

60
 MODCELL and MOD 30ML Maintenance

DIAGNOSING SHUTDOWN FAULTS

• Observe the display. Depending upon the instrument configuration, either the
Device Status display or a user configured display will appear. The alarm light
should be off unless there is still an active problem in the instrument.

If the alarm light is on or flashing, press the alarm key to access the diagnostic
alarm display. The display shows the diagnostic event code number and block
type. Refer to Section 7 for descriptions of diagnostic event codes.

6.2.3 Memory Module Method

Use this procedure to obtain shutdown information from the memory module in an
instrument which became inoperative due to a shutdown fault. This procedure is valid
only when the memory module was in place during the shutdown, and its switches were
set at NORMAL and READ /WRITE. A spare instrument in operating condition is required
for this procedure.

1. Remove the memory module from the inoperative instrument.

2. Change the READ/WRITE setting to READ ONLY, and NORMAL to MODULE LOAD.
This prevents the shutdown data from being overwritten and also prevents the module
database from being downloaded when the module is put into the spare instrument.

3. With power off, install the memory module in an operable spare instrument (either
MODCELL or MOD 30ML).

4. Apply power to the instrument.

5. Start the Application Builder Software. If communication to the instrument is via an

RS-232 or RS-485 port, the default parameters (9600 baud, no parity, 8 data bits, 1
stop bit) must be used. See Section 3 for the software startup procedure.

6. Access the status display in the application builder.

7. On the Instrument Status display command line, type the command R SD M and click
on ENTER. A display providing shutdown data appears. A form illustrating this
display with blank data fields is provided at the end of this section.

NOTE: If a facility for printing the display screen is available, it can be used to generate a
copy of the shutdown data.

8. Make a copy of the form and fill in the blank fields on the copy using the data from the
display.

9. Copy the Catalog No. and Version number from the identity module in the failed
instrument onto the shutdown data form.

10. Fax a copy of the completed shutdown information form to:

ABB Instrumentation
Advanced Control Support
FAX: 716-273-6242

61
MODCELL and MOD 30ML Maintenance

DIAGNOSING SHUTDOWN FAULTS

MODCELL SHUTDOWN DATA

62
 MODCELL and MOD 30ML Maintenance

DIAGNOSING SHUTDOWN FAULTS

MOD 30ML SHUTDOWN DATA

Line 1

Line 2

Line 6

Shutdown Entry Display

Line 1 Line 2 Line 3

Shutdown
Page 1 S —— —— —— —— —— —— 1 —— —— —— —— —— —— —— ——

Shutdown
Page 2 S —— —— —— —— —— —— 2 —— —— : —— —— : —— —— : —— —— —— —— / —— —— / —— ——
Shutdown
Page 3 S —— —— —— —— —— —— 3 —— —— —— —— —— —— —— —— —— —— —— —— —— —— —— ——

Shutdown
Page 4 S —— —— —— —— —— —— 4 —— —— —— —— —— —— —— —— —— —— —— —— —— —— —— ——

Identity Module Catalog Number ______________________

Version Information ________________

63
MODCELL and MOD 30ML Maintenance

DIAGNOSING SHUTDOWN FAULTS

64
 MODCELL and MOD 30ML Maintenance

EVENT CODES AND TRANSITION MESSAGES

SECTION 7
EVENT CODES AND TRANSITION MESSAGES

7.1 GENERAL
The transition messages and diagnostic and informational event codes described in
the following sections can be viewed on the status display in the Application Builder
Software or from the MOD 30ML display. Refer to Section 3 for information on
accessing the status display, and issuing the commands required to read the codes
and messages.

7.2 TRANSITION MESSAGE DESCRIPTIONS

Table 11 lists the event transition messages and their descriptions. These transition
messages apply to all events for all blocks.
Table 11. Event Transition Messages Descriptions
Message Description
INFOONLY An informational event. No appended text required.
UAK-ONLY Indicates the acknowledge only diagnostic has occurred.
UAK-ONLY Indicates the acknowledge only diagnostic has occurred.
ACT/UAK Indicates the event has gone active and unacknowledged.
ACT/ACK Indicates the process alarm has gone active but not unacknowledged because its
priority level is zero.
ACT/UAK Indicates the event has gone active while it was unacknowledged.
CLR/UAK Indicates the event has cleared while it was unacknowledged.
CLR/ACK Indicates the event has cleared after it was acknowledged.
CLR-SUPP Indicates the event was cleared by one of the suppression methods.
ACKED Indicates the event was acknowledged by a single ack message.
GLBL ACK Indicates the event was acknowledged by one of the global ack methods.
ACK-SUPP Indicates the event was acknowledged by one of the suppression methods.
SUPP Indicates the event’s suppression attribute has been set to YES.
ENABLED Indicates the event’s suppression attribute has been set to NO.

7.3 EVENT CODE DESCRIPTIONS

The diagnostic and informational event codes in Table 12 are related to block types
within the instrument database organization. Match the block type and code to get
the expanded description and corrective action. Informational events are not
acknowledged. The block types are identified as:
Type Description ICN Instrument Comm. Network RIM Resistance Input Module
AIN Built-in Analog Input Module RIO Remote I/O Interface Module
AOM Analog Output Module IF Interface Block RTI RTD Input Block
AOUT Built-in Analog Output LN Linearization Block RTTI RTD Transmitter Input Block
CJI Cold Junction Comp. Input Block LP Loop Block SE System Event
CJIM Cold Junction Comp. Input ML Modbus List Block SM Supervisory Message Block
Module MSC Modcell Serial Communication SEQ Sequencer Block
CL Configured List Block Module (DVC, LSEQ, SSEQ)
DDOM Dual Digital Output Module NM Notification Message Block TI Thermocouple Input Block
DI Digital Input Block OC Output Communication Block TIM Thermocouple Input Module
DIF Display Interface Block PA Process Alarm Block TM Timer Block
DIM Digital Input Module PAD Process Alarm Display Block TTI Thermocouple Trans. Input Block
DISP Display Block PID PID Control Block VCI Voltage/Current Input Block
DOM Digital Output Module PW Piecewise Table Block VCIM Voltage/Current Input Module
EX Expression Block RDIM Remote Digital Input Module WDOM Wide Digital Output Module
IC Input Communication Block RDOM Remote Digital Output Module WRIM Wide Resistance Input Module
RI Resistance Input Block

65
MODCELL and MOD 30ML Maintenance

EVENT CODES AND TRANSITION MESSAGES

Table 12. Event Codes, Description and Action

Block
Codes Full Message Text Description/Action
Type
AIN 4 I/O COMMUNICATIONS ERROR Diagnostic report of a communications problem.
AIN 5 AIN (MODULE) ERROR Output circuit reported an output too low or too
high error.
AIN 6 MODE SET TO AUTO Information only.
AIN 7 MODE SET TO MANUAL Information only.
AIN 8 CJC MODE SET TO AUTO Information only.
AIN 9 CJC MODE SET TO MANUAL Information only.
AOM 4 BLOCK MODE SET TO AUTO Information only.
AOM 5 BLOCK MODE SET TO MANUAL Information only.
AOM 6 I/O MISMATCH A configured slot is either empty or the installed
module does not match the slot configuration.
AOM 7 AO COMMUNICATIONS ERROR One of the following conditions was detected:
• There is a checksum error in the
communications between this block and the
module.
• The select circuit, which is used to
communicate with the module, has a
diagnostic error. In this case, all modules
report a communications error.
AOM 8 AO MODULE ERROR The module has reported an error which is
identified by an extended error code. The error
codes can be viewed via the Extended Error
(EXTERR).
AOUT 4 BLOCK MODE SET TO AUTO Information only.
AOUT 5 BLOCK MODE SET TO MANUAL Information only.
AOUT 6 AOUT COMMUNICATIONS ERROR Diagnostic report of a communications problem.
AOUT 7 AOUT (MODULE) ERROR Output circuit reported an output too low or too
high error.
CJI 0-4 See TI 0-4.
CJIM 4 BLOCK MODE SET TO AUTO Information only.
CJIM 5 BLOCK MODE SET TO MANUAL Information only.
CJIM 6 I/O MISMATCH A configured slot is either empty or the installed
module does not match the slot configuration.
CJIM 7 I/O COMMUNICATIONS ERROR One of the following conditions was detected:
• A checksum error in the communications
between this block and the module.
• The select circuit, which is used to
communicate with the module, has a
diagnostic error. In this case, all modules
report a communications error.
CJIM 8 CJC MODULE ERROR The module has reported an error which is
identified by an extended error code. The error
codes can be viewed via the Extended Error
(EXTERR).

66
 MODCELL and MOD 30ML Maintenance

EVENT CODES AND TRANSITION MESSAGES

Table 12. Event Codes, Description and Action (Cont’d)

Block
Codes Full Message Text Description/Action
Type
DDOM 4 BLOCK MODE_1 SET TO AUTO Information only.
DDOM 5 BLOCK MODE_1 SET TO MANUAL Information only.
DDOM 6 BLOCK MODE_2 SET TO AUTO Information only.
DDOM 7 BLOCK MODE_2 SET TO MANUAL Information only.
DDOM 8 I/O MISMATCH A slot configured for a digital module contains
an intelligent module (analog input, analog
output, ICN, MSC or RIO).
NOTE: This diagnostic cannot distinguish
between an empty slot and a digital I/O module
or between different types of digital modules.
DDOM 9 DDO_1_MODULE_ERROR The select circuit, which is used to
communicate with the module blocks, has a
diagnostic error. In this case, all modules
report this diagnostic.
DDOM 10 DDO_2_MODULE_ERROR Same as Code 9.
DI 0 BLOCK STATE SET TO RUN Information only.
DI 1 BLOCK STATE SET TO HOLD Information only.
DI 2 BLOCK STATE SET TO OFF Information only.
DI 3 BLOCK STATE SET TO DEBUG Information only.
DIF 4 FACEPLATE COMMUNICATIONS ERROR An error occurred when trying to communicate
with the faceplate. Instances are counted in
CMERRCTR or BFULLCTR.
DIF 5 NO KEYBOARD RESPONSE The faceplate failed to respond when keyboard
data was requested. Instances are counted in
KBERRCTR.
DIM 4 BLOCK MODE SET TO AUTO Information only.
DIM 5 BLOCK MODE SET TO MANUAL Information only.
DIM 6 I/O MISMATCH A slot configured for a digital module contains
an intelligent module (analog input, analog
output, ICN, MSC or RIO).
NOTE: This diagnostic cannot distinguish
between an empty slot and a digital I/O module
or between different types of digital modules.
DISP 4 INVALID DISPLAY OPERATION This error is reported if for example, an attempt
ATTEMPTED (Ack Only Diag). is made (via key event statement or remote
source) to perform some illegal operation.
DOM 4 BLOCK MODE SET TO AUTO Information only.
DOM 5 BLOCK MODE SET TO MANUAL Information only.
DOM 6 I/O MISMATCH A slot configured for a digital module contains
an intelligent module (analog input, analog
output, ICN, MSC or RIO).
NOTE: This diagnostic cannot distinguish
between an empty slot and a digital I/O module
or between different types of digital modules.
DOM 7 DO_MODULE_ERROR The select circuit, which is used to
communicate with the module blocks, has a
diagnostic error. In this case, all modules
report this diagnostic.

67
MODCELL and MOD 30ML Maintenance

EVENT CODES AND TRANSITION MESSAGES

Table 12. Event Codes, Description and Action (Cont’d)

Block
Codes Full Message Text Description/Action
Type
EX 0 BLOCK STATE SET TO RUN Information only.
EX 1 BLOCK STATE SET TO HOLD Information only.
EX 2 BLOCK STATE SET TO OFF Information only.
EX 3 BLOCK STATE SET TO DEBUG Information only.
EX 4 CALCULATION ERROR One of the following conditions was detected:
• There is a calculation error (calculation
overflow, divide by zero, square root of
negative number etc.). The block completes
the calculation using some reasonable value
(+ or - maximum value for overflows, zero for
square root of negative number, etc.), and
sets the output quality bad if Attribute No. 10,
Set quality bad on calculation error?
(SETQBAD) is YES. The diagnostic error
clears and the quality is set back to good
when a subsequent execution of the block
performs a successful calculation.
• Improper syntax in the expression.
• A stack overflow due to too many nested
operations.
IC 0 BLOCK STATE SET TO RUN Information only.
IC 1 BLOCK STATE SET TO HOLD Information only.
IC 2 BLOCK STATE SET TO OFF Information only.
IC 3 BLOCK STATE SET TO DEBUG Information only.
IC 4 RECEIVING UNEXPECTED MESSAGE There is a configuration error (source or data
type incorrect) within either this block or within
an Output Communication block in another
instrument.
IC 5 NOT RECEIVING DATA A break in the communications has halted the
continual flow of data from the source. No new
data has been received for 2 seconds.
IC 6 BLOCK MODE SET TO MANUAL Information only.
IC 7 BLOCK MODE SET TO AUTO Information only.

68
 MODCELL and MOD 30ML Maintenance

EVENT CODES AND TRANSITION MESSAGES

Table 12. Event Codes, Description and Action (Cont’d)

Block
Codes Full Message Text Description/Action
Type
ICN 4 MODULE MISMATCH The slots configured for an ICN
communications module are either empty or the
installed module does not match the slot
configuration.
ICN 5 ACCESS TIMEOUT Access to transmit has not been granted for at
least one second. Token ring is broken, ICN
restarted.
ICN 6 RESTART FAILURE Communications cannot be established.
ICN 7 INVALID MESSAGE The message code of a received message was
invalid or is not supported by the software.
ICN 8 MESSAGE DATA INVALID A received message could not be processed
because it failed the CRC check.
ICN 9 FRAMING ERROR No stop bit was detected by the 68032 for a
received byte.
ICN 10 NOISE ERROR The 68302 checked a bit three times and the
three samples were not identical.
ICN 11 OVERRUN ERROR The central processor could not store a
received byte before the next byte was
received.
ICN 12 INVALID MESSAGE SIZE The size of the message or its data field is
invalid.
ICN 13 EXCESS MESSAGES RECEIVED The receive buffer for this port had no room for
the message being received. A message is
"lost".
ICN 14 EXCESS MESSAGES TO TRANSMIT The buffer used for the messages to be
transmitted had no room for another. A
message is "lost".
ICN 15 UNEXPECTED COMM MESSAGE An input communications message was
RECEIVED received, but the occurrence for which it was
destined is not in the current configuration.
ICN 16 COMMUNICATION OVERLOAD The time for each instrument on the ICN to
transmit all messages exceeded the
recommended time of 250 msec.
ICN 17 EXCESS MESSAGES FOR TASK The maximum number of requests queued for a
group has been reached. A message is "lost".

69
MODCELL and MOD 30ML Maintenance

EVENT CODES AND TRANSITION MESSAGES

Table 12. Event Codes, Description and Action (Cont’d)

Block
Codes Full Message Text Description/Action
Type
IF 4 DEFAULT DATABASE CHECKSUM The instrument was shut down due to a
ERROR checksum error in the default database.
IF 5 MAIN DATABASE CHECKSUM ERROR The instrument was shut down due to a
checksum error in the main database.
IF 6 INSTRUMENT IS UNCONFIGURED There is no valid user database in the
instruments main RAM.
IF 7 MAIN DATABASE VERSION ERROR A user database was rejected because the
instrument does not have the hardware and/or
firmware resources to run it.
IF 8 MEMORY MODULE CHECKSUM ERROR The memory module database has been
marked bad because a checksum error was
found in it.
IF 9 MEMORY MODULE IS UNCONFIGURED A memory module database was not
downloaded because no valid database was
found in the module.
IF 10 MEMORY MODULE DATABASE VERSION A memory module database was not
ERROR downloaded because the instrument does not
have the hardware and/or firmware resources
to run it.
IF 11 MEMORY MODULE IS WRITE The switch on the module is in the ‘read only’
PROTECTED position.
IF 12 MEMORY MODULE IS SOFT WRITE The write protect bit in the module RAM has
PROTECTED been set by software.
IF 13 INSTRUMENT IS OVERCONFIGURED The instrument is unable to complete all of its
tasks at the intervals specified. The scan
execution times should be examined to
determine which tasks should be simplified or
run at a slower rate or items should be moved
to another task. Note that when the instrument
is overconfigured, all tasks run at a
proportionally slower rate. This may be a
temporary condition if the instrument is getting
too many messages. You should not ignore
this condition if it is persistent.
IF 14 INSTRUMENT POWERED UP The instrument went through power-up. A time
stamp indicating the time power was restored is
entered in the event queue.
IF 15 INSTRUMENT POWERED DOWN The instrument lost power. A time stamp
indicating the time power was lost is entered in
the event queue.

70
 MODCELL and MOD 30ML Maintenance

EVENT CODES AND TRANSITION MESSAGES

Table 12. Event Codes, Description and Action (Cont’d)

Block
Codes Full Message Text Description/Action
Type
IF 16 COMMUNICATIONS PORT MISMATCH One of the following conditions was detected:
• An ICN module (2030N)is installed but no
matching ICN block was found in the user
database. Matching includes slot numbers and
the module address switch setting, if not 'ANY'
in the ICN block.
• An RS-232 module (2033N) or an RS-485
module (2034N) is installed but no matching
MSC block was found in the user database.
Matching includes slot numbers/module type
and the module address switch setting unless
'ANY' is configured in the MSC block
IF 17 INSTRUMENT SHUTDOWN FAULT When the instrument was last powered, an
event occurred which caused it to shut down. It
is now locked in the DEFAULT state. The user
should investigate the cause of the shutdown
and try running the instrument again, if desired,
by writing ACK SHUTDOWN FAULT (value 1)
to IF block Attribute No. 141, Command (CMD).
This acknowledges that the user has seen the
information relating to a previous shutdown fault
and reinitializes the SHUTDOWN INFO area.
Until this is done, the instrument will not accept
commands which could cause it to leave the
DEFAULT state. Information preserved at
shutdown is stored in the non checksummed
save area in the battery backed up RAM and is
examined through the configurator STATUS
display activity.
IF 18 MODULE SHUTDOWN FAULT When the memory module was last used, the
instrument on which it was installed suffered a
shutdown fault. The shutdown information
preserved in the module is stored in volatile
RAM and is examined through the configurator
STATUS display activity. The battery backed
up RAM must be write protected (switch set at
READ ONLY) to prevent this data from being
overwritten when powered up for examination
on another instrument.
IF 19 PROCESSOR WATCHDOG FAULT When the instrument was last powered, the
processor got 'lost' and the watchdog timer shut
the instrument down. See Code 17,
INSTRUMENT SHUTDOWN FAULT.
IF 20 SPURIOUS EVENT FAULT When the instrument was last powered, the
processor was interrupted by an unexpected
event (i.e. it had no handler to respond to the
event) and the instrument therefore shut down.
See Code 17, INSTRUMENT SHUTDOWN
FAULT.

71
MODCELL and MOD 30ML Maintenance

EVENT CODES AND TRANSITION MESSAGES

Table 12. Event Codes, Description and Action (Cont’d)

Block
Codes Full Message Text Description/Action
Type
IF 21 EPROM CHECKSUM FAULT When the instrument was last powered, a
checksum error was found in the identity
module EPROM and the instrument therefore
shut down. See Code 17, INSTRUMENT
SHUTDOWN FAULT.
IF 22 BAD RAM FAULT When the instrument was last powered, one of
the RAM chips failed the read/write test, and the
instrument therefore shut down. The error
address is preserved at shutdown. See Code
17, INSTRUMENT SHUTDOWN FAULT.
IF 23 I/O BOARD 1 COMMUNICATIONS An error (no response or bad message
ERROR checksum) occurred in trying to communicate
with the carrier board. There are wrap around
counters for these errors at IF1,SLNORSPS
and IF1,SLCHKSMS.
IF 39 BAD CLOCK CHIP The real time clock chip is not working correctly.
Time and date information will not remain
current through a power outage.
IF 40 TIME AND DATE NOT VALID The time of day, calendar date, and day of
week need to be set.
IF 41 I/O IS LOCKED The I/O is locked because Attribute No.195,
Lock I/O Blocks (IOLOCK) is YES. In the
locked state, output function block values are
not copied to the output module block output
value, and input module block values are not
copied to the input function blocks. Field input
values continue to be updated in the input
module blocks and output module block values
can be written by the operator.
IF 42 COMMUNICATION BLOCKS ARE Communications are locked because Attribute
LOCKED No. 158, Lock ICN Communications Blocks ?
(COMMLOCK) is YES. In the locked state, the
output communication blocks do not fetch data
from their source pointers (they do continue to
send out their current value), and input
communication blocks do not refresh their
outputs from received messages. Input and
output communication block outputs can be
written to by the operator.
IF 43 DMA FAULT An error occurred in a DMA transfer and the
instrument therefore shut itself down. The
diagnostic is readable when the instrument is
powered up again. See Code 17,
INSTRUMENT SHUTDOWN FAULT .

72
 MODCELL and MOD 30ML Maintenance

EVENT CODES AND TRANSITION MESSAGES

Table 12. Event Codes, Description and Action (Cont’d)

Block
Codes Full Message Text Description/Action
Type
IF 44 I/O OVERRUN The instrument is unable to complete all I/O
sampling at the intervals specified. The scan
execution times should be examined to
determine which tasks should be simplified or
run at a slower rate. Note that when the
instrument is overconfigured, all tasks will run at
a proportionally slower rate.
IF 45 COMM HARDWARE FAULT A communication module is installed in slots 9
and 10 of a MOD 30ML (1800R) and the built-in
communication jumpers are set for built-in
communication; a conflict of resources occurs
since both require use of communication port 1.
The instrument is placed in the DEFAULT state.
No block is built for either case, leaving PC
communication only available via a
communication module in slot 7 & 8.
IF 46 EEPROM FAULT The data stored in EEPROM of a MOD 30ML
(1800R) could not be loaded into the instrument
database. Default values were loaded and are
being used. The data values include the
calibration data for the built-in I/O and
communication parameters for built-in
communication port.
IF 47 MEMORY MODULE DOWNLOAD FAILED The memory module database was not
downloaded. Another diagnostic will be present
to indicate why the download did not happen.
IF 128 DOWNLOAD FROM MEMORY MODULE Information only: The memory module
database was downloaded to main RAM.
IF 129 UPLOAD TO MEMORY MODULE Information only: The user database was
uploaded to the memory module.
IF 130 DOWNLOAD FROM SYSTEM Information only: A full or partial database
download was received from the external
system.
IF 131 UPLOAD TO SYSTEM Information only: A database was uploaded to
the external system.
IF 132 INSTRUMENT IN UPLOAD STATE Information only: The instrument has entered
the upload state and is now running the default
database.
IF 133 INSTRUMENT IN DEFAULT STATE Information only: The instrument has entered
the default state and is now running the default
database.
IF 134 INSTRUMENT BEING CONFIGURED Information only: The instrument has entered
the being configured state and is running the
default database to make the main database
area available for downloading.

73
MODCELL and MOD 30ML Maintenance

EVENT CODES AND TRANSITION MESSAGES

Table 12. Event Codes, Description and Action (Cont’d)

Block
Codes Full Message Text Description/Action
Type
IF 135 INSTRUMENT IN HOLD STATE Information only: The instrument has entered
the hold state and is now running only the i/o
section of the user database.
IF 136 INSTRUMENT IN LOCAL HOLD STATE Information only: The instrument has entered
the local hold state and is now running only the
i/o section of the user database. It will enter the
run state if the run/hold switch is moved to run.
IF 137 INSTRUMENT IN RUN STATE Information only: The instrument has entered
the run state and is now running the full user
database.
IF 138 TIME STAMP CHANGED Information only: Indicates that time of day,
calendar date or day of week has been written
to.
LN 0 BLOCK STATE SET TO RUN Information only.
LN 1 BLOCK STATE SET TO HOLD Information only.
LN 2 BLOCK STATE SET TO OFF Information only.
LN 3 BLOCK STATE SET TO DEBUG Information only.
LN 4 CALCULATION ERROR A calculation error (calculation overflow, divide
by zero, square root of negative number etc.)
has been detected. The block completes the
calculation using some reasonable value (+ or -
maximum value for overflows, zero for square
root of negative number, etc.), and sets the
output qualities bad if Attribute No. 13, Set
quality bad on calculation error? (SETQBAD) is
YES. The diagnostic error clears and the
quality is set back to good when a subsequent
execution of the block performs a successful
calculation.
LP 0 BLOCK STATE SET TO RUN Information only.
LP 1 BLOCK STATE SET TO HOLD Information only.
LP 2 BLOCK STATE SET TO OFF Information only.
LP 3 BLOCK STATE SET TO DEBUG Information only.
LP 4 REMOTE STATE INPUT INVALID The remote state input has an invalid value, and
the composite state takes on the remote error
state value.

74
 MODCELL and MOD 30ML Maintenance

EVENT CODES AND TRANSITION MESSAGES

Table 12. Event Codes, Description and Action (Cont’d)

Block
Codes Full Message Text Description/Action
Type
MSC 4 MODULE MISMATCH The slot(s) configured for a MODBUS
communications module is either empty or the
installed module does not match the slot
configuration.
MSC 5 MESSAGE CHECK ERROR A received message could not be processed
because it failed the Cyclical Redundancy
Check (CRC) check.
MSC 6 PARITY ERROR A parity error was detected for a received byte.
The message is discarded.
MSC 7 BREAK ERROR A break sequence was detected (a character
with zero value and framing error was received)
by the 68032 for a received byte. The message
is discarded.
MSC 8 FRAMING ERROR No stop bit was detected by the 68032 for a
received byte.
MSC 9 NOISE ERROR The 68302 checked a bit three times and the
three samples were not identical.
MSC 10 OVERRUN ERROR The central processor could not store a
received byte before the next byte was
received.
MSC 11 INVALID MESSAGE The message length was too large, the
message size was incorrect, or there was an
illegal use of a global message. The message
is discarded.
MSC 12 EXCESS MESSAGES FOR PORT The receive buffer for this port had no room for
the message being received. A message is
lost.
MSC 13 EXCESS MESSAGES FOR TASK The maximum number of requests queued for a
group has been reached. A message is lost.
MSC 14 DEFAULT COMM SWITCH SET The default communication switch is set (yes)
on the RS-232 or RS-485 module. Therefore,
this block is functioning as a SLAVE using 9600
baud, no parity and one stop bit for it’s
communication parameters.

75
MODCELL and MOD 30ML Maintenance

EVENT CODES AND TRANSITION MESSAGES

Table 12. Event Codes, Description and Action (Cont’d)

Block
Codes Full Message Text Description/Action
Type
NM 0 BLOCK STATE SET TO RUN Information only.
NM 1 BLOCK STATE SET TO HOLD Information only.
NM 2 BLOCK STATE SET TO OFF Information only.
NM 3 BLOCK STATE SET TO DEBUG Information only.
NM 4 REQUESTED DATA NOT RECEIVED Requested data has not been received within
the time-out period.
NM 5 NOTIFICATION MESSAGE Information only.
OC 0 BLOCK STATE SET TO RUN Information only.
OC 1 BLOCK STATE SET TO HOLD Information only.
OC 2 BLOCK STATE SET TO OFF Information only.
OC 3 BLOCK STATE SET TO DEBUG Information only.
OC 4 BLOCK MODE SET TO MANUAL Information only.
OC 5 BLOCK MODE SET TO AUTO Information only.
PA 0 BLOCK STATE SET TO RUN Information only.
PA 1 BLOCK STATE SET TO HOLD Information only.
PA 2 BLOCK STATE SET TO OFF Information only.
PA 3 BLOCK STATE SET TO DEBUG Information only.
PA 4 PROCESS ALARM Information only.
PAD 0 BLOCK STATE SET TO RUN Information only.
PAD 1 BLOCK STATE SET TO HOLD Information only.
PAD 2 BLOCK STATE SET TO OFF Information only.
PAD 3 BLOCK STATE SET TO DEBUG Information only.
PAD 4 PV LO Process Value Low
PAD 4 PV LOLO Process Value Low Low
PAD 4 PV HI Process Value High
PAD 4 PV HIHI Process Value High High
PAD 4 DEV LO Deviation Value Low
PAD 4 DEV LOLO Deviation Value Low Low
PAD 4 DEV HI Deviation Value High
PAD 4 DEV HIHI Deviation Value High High
PAD 4 OUT LO Output Value Low
PAD 4 OUT LOLO Output Value Low Low
PAD 4 OUT HI Output Value High
PAD 4 OUT HIHI Output Value High High

76
 MODCELL and MOD 30ML Maintenance

EVENT CODES AND TRANSITION MESSAGES

Table 12. Event Codes, Description and Action (Cont’d)

Block
Codes Full Message Text Description/Action
Type
PID 0 BLOCK STATE SET TO RUN Information only.
PID 1 BLOCK STATE SET TO HOLD Information only.
PID 2 BLOCK STATE SET TO OFF Information only.
PID 3 BLOCK STATE SET TO DEBUG Information only.
PID 4 CALCULATION ERROR A calculation error (calculation overflow, divide
by zero, etc.) has been detected in calculations
which do not affect the control output (e.g.,
adjusted set-point calculation). The block
completes the calculation using some
reasonable value (+ or - maximum value for
overflows, etc.), and sets the output qualities
according to the configuration of Attribute No.
58, Calculation Error Action (CERRACT). The
diagnostic error clears and the quality is set
back to good when a subsequent execution of
the block performs a successful calculation.
PID 5 CONTROL OUTPUT CALCULATION A calculation error (calculation overflow, divide
ERROR by zero, etc.) has been detected while
calculating the control output value. The block
completes the calculation using some
reasonable value (+ or - maximum value for
overflows, etc.), and sets the output qualities
according to the configuration of Attribute No.
58, Calculation Error Action (CERRACT).. The
diagnostic error clears and the quality is set
back to good when a subsequent execution of
the block performs a successful calculation.
RDIM 4 CHANNEL 0 MODE SET TO AUTO Information only.
RDIM 5 CHANNEL 0 MODE SET TO MANUAL Information only.
RDIM 6 ••• Repeat for Channels 1 to 14
RDIM 34 CHANNEL 15 MODE SET TO AUTO Information only.
RDIM 35 CHANNEL 15 MODE SET TO MANUAL Information only.
RDIM 36 I/O MISMATCH A configured address on the CS-31 bus is not
used or the installed remote module does not
match the address configuration.
RDIM 37 MODULE EXTENDED ERROR A remote module has reported an error.
Codes identifying reported error are stored in
the block database as extended errors. The
error codes can be viewed via Attribute Nos. 31
- 46, Extended Error (EXTERR).

77
MODCELL and MOD 30ML Maintenance

EVENT CODES AND TRANSITION MESSAGES

Table 12. Event Codes, Description and Action (Cont’d)

Block
Codes Full Message Text Description/Action
Type
RDOM 4 CHANNEL 0 MODE SET TO AUTO Information only.
RDOM 5 CHANNEL 0 MODE SET TO MANUAL Information only.
RDOM 6 ••• Repeat for Channels 1 to 14
RDOM 34 CHANNEL 15 MODE SET TO AUTO Information only.
RDOM 35 CHANNEL 15 MODE SET TO MANUAL Information only.
RDOM 36 I/O MISMATCH A configured address on the CS-31 bus is not
used or the installed remote module does not
match the address configuration.
RDOM 37 MODULE EXTENDED ERROR A remote module has reported an error.
Codes identifying reported errors are stored in
the block database as extended errors. The
error codes can be viewed via Attribute Nos. 15
- 30, Extended Error (EXTERR).
RI 0 BLOCK STATE SET TO RUN Information only.
RI 1 BLOCK STATE SET TO HOLD Information only.
RI 2 BLOCK STATE SET TO OFF Information only.
RI 3 BLOCK STATE SET TO DEBUG Information only.
RI 4 CALCULATION ERROR A calculation error (calculation overflow or
divide by zero) has been detected. The block
completes the calculation using some
reasonable value (+ or - maximum value for
overflows and divide by zero), and sets the
output quality bad if Attribute No. 10, Set quality
bad on calculation error? (SETQBAD) is YES.
The diagnostic error clears and the quality is set
back to good when a subsequent execution of
the block performs a successful calculation.
RIM 4 BLOCK MODE SET TO AUTO Information only.
RIM 5 BLOCK MODE SET TO MANUAL Information only.
RIM 6 I/O MISMATCH A configured slot is either empty or the installed
module does not match the slot configuration.
RIM 7 I/O COMMUNICATIONS ERROR One of the following conditions was detected:
• A checksum error in the communications
between this block and the module.
• The select circuit, which is used to
communicate with the module, has a
diagnostic error. In this case, all modules
report a communications error.
RIM 8 RIM MODULE ERROR The module has reported an error which is
identified by an extended error code. The
error codes can be viewed via Attribute No.18,
Extended Error (EXTERR).

78
 MODCELL and MOD 30ML Maintenance

EVENT CODES AND TRANSITION MESSAGES

Table 12. Event Codes, Description and Action (Cont’d)

Block
Codes Full Message Text Description/Action
Type
RIO 4 I/O MISMATCH A configured slot is either empty or the installed
module does not match the slot configuration.
RIO 5 CS-31 BUS COMMUNICATION ERROR There is an error in communication or loss of
communication between the RIO interface
module and the CS-31 bus.
RIO 6 I/O COMMUNICATIONS ERROR An error occurred in communication between
the RIO module and the instrument.
RIO 7 CS-31 DATABASE CHECKSUM ERROR The remote I/O database stored in the interface
module has been declared bad due to a
checksum error.
RIO 8 MODULE EXTENDED ERROR There is an RIO module error.
RTI 0 BLOCK STATE SET TO RUN Information only.
RTI 1 BLOCK STATE SET TO HOLD Information only.
RTI 2 BLOCK STATE SET TO OFF Information only.
RTI 3 BLOCK STATE SET TO DEBUG Information only.
RTI 4 CALCULATION ERROR A calculation error (calculation overflow or
divide by zero) has been detected. The block
completes the calculation using some
reasonable value (+ or - maximum value for
overflows and divide by zero), and sets the
output quality bad if Attribute No. 10, Set quality
bad on calculation error? (SETQBAD) is YES.
The diagnostic error clears and the quality is set
back to good when a subsequent execution of
the block performs a successful calculation.
RTTI 0 BLOCK STATE SET TO RUN Information only.
RTTI 1 BLOCK STATE SET TO HOLD Information only.
RTTI 2 BLOCK STATE SET TO OFF Information only.
RTTI 3 BLOCK STATE SET TO DEBUG Information only.
RTTI 4 CALCULATION ERROR A calculation error (calculation overflow or
divide by zero) has been detected. The block
completes the calculation using some
reasonable value (+ or - maximum value for
overflows and divide by zero), and sets the
output quality bad if Attribute No. 10, Set quality
bad on calculation error? (SETQBAD) is YES.
The diagnostic error clears and the quality is set
back to good when a subsequent execution of
the block performs a successful calculation.

79
MODCELL and MOD 30ML Maintenance

EVENT CODES AND TRANSITION MESSAGES

Table 12. Event Codes, Description and Action (Cont’d)

Block
Codes Full Message Text Description/Action
Type
SE 4 ALL DIAG, PA AND NM GLOBALLY Information only.
ACKED.
SE 5 ALL DIAGNOSTICS GLOBALLY ACKED. Information only.
SE 6 ALL PROCESS ALARMS GLOBALLY Information only.
ACKED.
SE 7 ALL NOTIF/REQ MSGS GLOBALLY Information only.
ACKED.
SE 8 ALL GROUP DIAGNOSTICS Information only.
SUPPRESSED
SE 9 ALL GROUP DIAGNOSTICS ENABLED Information only.
SE 10 GROUP 1 DIAGNOSTICS SUPPRESSED Information only.
SE 11 GROUP 1 DIAGNOSTICS ENABLED Information only.
SE 12 GROUP 2 DIAGNOSTICS SUPPRESSED Information only.
SE 13 GROUP 2 DIAGNOSTICS ENABLED Information only.
SE 14 GROUP 3 DIAGNOSTICS SUPPRESSED Information only.
SE 15 GROUP 3 DIAGNOSTICS ENABLED Information only.
SE 16 GROUP 4 DIAGNOSTICS SUPPRESSED Information only.
SE 17 GROUP 4 DIAGNOSTICS ENABLED Information only.
SE 18 GROUP 5 DIAGNOSTICS SUPPRESSED Information only.
SE 19 GROUP 5 DIAGNOSTICS ENABLED Information only.
SE 20 GROUP 6 DIAGNOSTICS SUPPRESSED Information only.
SE 21 GROUP 6 DIAGNOSTICS ENABLED Information only.
SE 22 GROUP 7 DIAGNOSTICS SUPPRESSED Information only.
SE 23 GROUP 7 DIAGNOSTICS ENABLED Information only.
SE 24 SYSTEM EVENT QUEUE CLEARED Information only.
SM 0 BLOCK STATE SET TO RUN Information only.
SM 1 BLOCK STATE SET TO HOLD Information only.
SM 2 BLOCK STATE SET TO OFF Information only.
SM 3 BLOCK STATE SET TO DEBUG Information only.
SM 4 SUPERVISORY MESSAGE ERROR A supervisory message failed.

80
 MODCELL and MOD 30ML Maintenance

EVENT CODES AND TRANSITION MESSAGES

Table 12. Event Codes, Description and Action (Cont’d)

Block
Codes Full Message Text Description/Action
Type
SEQ 0 BLOCK STATE SET TO RUN Information only.
SEQ 1 BLOCK STATE SET TO HOLD Information only.
SEQ 2 BLOCK STATE SET TO OFF Information only.
SEQ 3 BLOCK STATE SET TO DEBUG Information only.
SEQ 4 SEQ BLOCK BAD INPUT DETECTED Bad quality has been detected in an external
step input or transition expression input. The
block takes action in accordance with the
configuration of Attribute No. 41, Bad Input
Action (IACTION).
SEQ 5 SEQ BLOCK CALC ERROR A calculation error (calculation overflow, divide
by zero, etc.) has been detected in a calculation
to evaluate a transition expression. The block
completes the calculation using some
reasonable value (+ or - maximum value for
overflows and divide by zero), and takes action
in accordance with the configuration of Attribute
No. 42, Calculation Error Action (CACTION).
SEQ 6 SEQ BLOCK STEP OUT OF RANGE A calculated step is out of range or a syntax
error has been detected in a transition
expression. The block takes action in
accordance with the configuration of Attribute
No. 43, Bad Step Error Action (SACTION).
SEQ 7 SEQ BLOCK FAILURE As a result of a bad input error, calculation error
or step out of range error (Event Code 4, 5 or
6), the sequence has been driven to the Fail
Step
SEQ 8 BLOCK SET TO MANUAL Information only.
SEQ 9 BLOCK MODE SET TO AUTO Information only.
SEQ 10 BLOCK MODE SET TO SEMI-AUTO Information only.

81
MODCELL and MOD 30ML Maintenance

EVENT CODES AND TRANSITION MESSAGES

Table 12. Event Codes, Description and Action (Cont’d)

Block
Codes Full Message Text Description/Action
Type
TI 0 BLOCK STATE SET TO RUN Information only.
TI 1 BLOCK STATE SET TO HOLD Information only.
TI 2 BLOCK STATE SET TO OFF Information only.
TI 3 BLOCK STATE SET TO DEBUG Information only.
TI 4 CALCULATION ERROR A calculation error (calculation overflow or
divide by zero) has been detected. The block
completes the calculation using some
reasonable value (+ or - maximum value for
overflows and divide by zero), and sets the
output quality bad if Attribute No. 10, Set quality
bad on calculation error? (SETQBAD) is YES.
The diagnostic error clears and the quality is set
back to good when a subsequent execution of
the block performs a successful calculation.
TTI 0 BLOCK STATE SET TO RUN Information only.
TTI 1 BLOCK STATE SET TO HOLD Information only.
TTI 2 BLOCK STATE SET TO OFF Information only.
TTI 3 BLOCK STATE SET TO DEBUG Information only.
TTI 4 CALCULATION ERROR A calculation error (calculation overflow or
divide by zero) has been detected. The block
completes the calculation using some
reasonable value (+ or - maximum value for
overflows and divide by zero), and sets the
output quality bad if Attribute No. 10, Set quality
bad on calculation error? (SETQBAD) is YES.
The diagnostic error clears and the quality is set
back to good when a subsequent execution of
the block performs a successful calculation.
TIM 4 BLOCK MODE SET TO AUTO Information only.
TIM 5 BLOCK MODE SET TO MANUAL Information only.
TIM 6 I/O MISMATCH A configured slot is either empty or the installed
module does not match the slot configuration.
TIM 7 I/O COMMUNICATIONS ERROR One of the following conditions was detected:
• There is a checksum error in the
communications between this block and the
module.
• The select circuit, which is used to
communicate with the module, has a
diagnostic error. In this case, all modules
report a communications error.
TIM 8 TI MODULE ERROR The module has reported an error which is
identified by an extended error code. The
error codes can be viewed via Attribute No.18,
Extended Error (EXTERR).

82
 MODCELL and MOD 30ML Maintenance

EVENT CODES AND TRANSITION MESSAGES

Table 12. Event Codes, Description and Action (Cont’d)

Block
Codes Full Message Text Description/Action
Type
TM 0 BLOCK STATE SET TO RUN Information only.
TM 1 BLOCK STATE SET TO HOLD Information only.
TM 2 BLOCK STATE SET TO OFF Information only.
TM 3 BLOCK STATE SET TO DEBUG Information only.
VCI 0 BLOCK STATE SET TO RUN Information only.
VCI 1 BLOCK STATE SET TO HOLD Information only.
VCI 2 BLOCK STATE SET TO OFF Information only.
VCI 3 BLOCK STATE SET TO DEBUG Information only.
VCI 4 CALCULATION ERROR A calculation error (calculation overflow or
divide by zero) has been detected. The block
completes the calculation using some
reasonable value (+ or - maximum value for
overflows and divide by zero), and sets the
output quality bad if Attribute No. 10, Set quality
bad on calculation error? (SETQBAD) is YES.
The diagnostic error clears and the quality is set
back to good when a subsequent execution of
the block performs a successful calculation.
VCIM 4 BLOCK MODE SET TO AUTO Information only.
VCIM 5 BLOCK MODE SET TO MANUAL Information only.
VCIM 6 I/O MISMATCH A configured slot is either empty or the installed
module does not match the slot configuration.
VCIM 7 I/O COMMUNICATIONS ERROR One of the following conditions was detected:
• There is a checksum error in the
communications between this block and the
module.
• The select circuit, which is used to
communicate with the module, has a
diagnostic error. In this case, all modules
report a communications error.
VCIM 8 VI MODULE ERROR The module has reported an error which is
identified by an extended error code. The
error codes can be viewed via Attribute No.18,
Extended Error (EXTERR).

83
MODCELL and MOD 30ML Maintenance

EVENT CODES AND TRANSITION MESSAGES

Table 12. Event Codes, Description and Action (Cont’d)

Block
Codes Full Message Text Description/Action
Type
WDOM 4 BLOCK MODE SET TO AUTO Information only.
WDOM 5 BLOCK MODE SET TO MANUAL Information only.
WDOM 6 I/O MISMATCH A slot configured for a digital module contains
an intelligent module (analog input, analog
output, ICN, MSC or RIO).
NOTE: This diagnostic cannot distinguish
between an empty slot and a digital I/O module
or between different types of digital modules.
WDOM 7 WDO_MODULE_ERROR One of the following conditions was detected:
• The module readback value is not the same
as the previous result value.
• The select circuit, which is used to
communicate with the module blocks, has a
diagnostic error. In this case, all modules
report this diagnostic.
WRIM 4 BLOCK MODE SET TO AUTO Information only.
WRIM 5 BLOCK MODE SET TO MANUAL Information only.
WRIM 6 I/O MISMATCH A configured slot is either empty or the installed
module does not match the slot configuration.
WRIM 7 I/O COMMUNICATIONS ERROR One of the following conditions was detected:
• There is a checksum error in the
communications between this block and the
module.
• The select circuit, which is used to
communicate with the module, has a
diagnostic error. In this case, all modules
report a communications error.
WRIM 8 WRIM MODULE ERROR The module has reported an error which is
identified by an extended error code. The
error codes can be viewed via Attribute No.18,
Extended Error (EXTERR).

84
 MODCELL and MOD 30ML Maintenance

PARTS

SECTION 8
PARTS

8.1 PARTS AVAILABILITY

All MODCELL and MOD 30ML components which are identified by catalog numbers are
available for purchase. The available components and their base catalog numbers are
listed in the following sections. When ordering a replacement, specify the full catalog
number as stamped on the component data plate. A description of each component and
its complete catalog number is provided in the Installation Manual, IB-23C600 for Modcell
or IB-1800R-INS for MOD 30ML.

8.2 BASIC HARDWARE

8.2.1 MODCELL Multiloop Processor

2001N MODCELL Multiloop Processor - Eurocard Format
2002N MODCELL Multiloop Processor.- Flush Mount
2001P Logic Control Identity Module
2004P Advanced Control Identity Module
2010P Memory Module
2001F Instrument Housing
2002F Instrument Termination Assembly

8.2.2 MOD 30ML Multiloop Controller

1800R MOD 30ML Multiloop Controller
1800P MOD 30ML Identity Module
2010P Memory Module

8.3 I/O MODULES

The I/O modules are common to both the MODCELL and MOD 30ML
instruments.
2001A Voltage Input Module
2002A Current Input Module
2012A Current Input Module (with 2-wire transmitter power)
2013A Thermocouple Input Module (with upscale burnout detection)
2003A Current Output Module
2004A Solid-State Relay Input Module

85
MODCELL and MOD 30ML Maintenance

PARTS

8.3 I/O MODULES (Cont’d.)

2005A Solid-State Relay Output Module

2006A Nonisolated Digital Input Module
2007A Nonisolated Digital Output Module
2011A Mechanical Relay Output Module
2009A RTD Input Module
2020N Remote I/O Interface Module

8.4 COMMUNICATIONS MODULES

2030N ICN Communication Module
2030F ICN Terminator
2032N RS-485 Communication Module for Modbus (2-Wire)
2033N RS-232 Communications Module for Modbus
2034N RS-485 Communication Module for Modbus (4-Wire)

86
 MODCELL and MOD 30ML Maintenance

REVISION HISTORY

SECTION 9
HARDWARE, FIRMWARE AND SOFTWARE REVISION HISTORY
9.1 GENERAL
This section provides information about revisions introduced for Modcell and MOD 30ML
instruments and associated firmware, and revisions introduced for configuration software
and device driver software since the initial introduction of these products.

The starting point of these historical records is either the date of the initial product
introduction or the date of the revision which made the product usable with Modcell or
MOD 30ML instruments. The product revisions are identified by either a number or a
model letter. The numbers apply to firmware and software revisions; the model letters
apply to hardware revisions.

9.2 HARDWARE AND FIRMWARE REVISIONS

The revision history for Modcell and MOD 30ML instruments and associated firmware is
listed in Table 13. The products included in the listing are as follows:
• 1720N Communications Link
• ICN Mini Link
- 1731N Mini Link Board
- 1732N ICN Interface (Controller) Board
• 1733N Mini Link/External with 1732N ICN Interface (Controller) Board
• MOD 30ML Multiloop Controller - 1800R
• MODCELL Multiloop Processor
- 2001N, 2002N Base Boards
- 2001P, 2002P, 2004P, 2005P Identity Modules
- 2031N, 2032N, 2033N, 2034N Communications Modules
- 2020N Remote I/O Interface Module

9.3 SOFTWARE REVISIONS

The revision history for Modcell software is listed in Table 14. The products included in
the listing are as follows:
• 1706S Instrument Configuration Software
• 2006S Application Builder Software
• 1716S ICN Driver for PC-30
• 1719S Modbus Driver for PC-30
• 1733S Extended Modbus Driver for PC-30
• Extended Modbus Driver for FIX DMACS and FIX MMI
- 2010S 16-Bit Driver
- 2011S 32-Bit Driver

87
MODCELL and MOD 30ML Maintenance

REVISION HISTORY

Table 13. Hardware and Firmware Revision History

Instrument Rev Date Features Comments

Communications 2.0 Mid-1984 Initial firmware release
Links
3.0 Dec 1984 SLU compatibility
(1720N, 1731N,
1733N)
4.0 Link-wide supervisory
messages via SLU

5.0 Aug 1986 Enhanced Link CPU and ICN boards both at
communications for Ver 5
MOD 300 compatibility

5.1 Sept 1986 ICN driver enhancements.

Support for Accuray
product.

Communications 5.2 Jan 1992 Added support for Required for MODCELL and
Links, ICN MODCELL foreground MOD 30ML instruments
Controller only size.
Link CPU board current version is
(1720N, 1731N,
5.1, and Link ICN controller board
1733N, 1734N)
current version is 5.2

MOD 30ML Model A Mar 1996 Initial release Requires 2006S Ver 4.0
Multiloop Application Builder software
Controller
1.01 1.01 Requires 1716S Ver 9.0
1800R
ICN Driver for PC-30

MODCELL Model A Oct 1991 BETA release hardware; All BETA sites updated to
Multiloop limited shipment Model B
2001N, 2002N Base
Model B Dec 1991 Initial production hardware
Board
release

Model C Feb 1995 Larger Power Supply in No change in DC version

AC version

88
 MODCELL and MOD 30ML Maintenance

REVISION HISTORY

Table 13. Hardware and Firmware Revision History (Cont’d)

Instrument Rev Date Features Comments

MODCELL 1.0 Jan 1992 Initial firmware release
Multiloop
2.0 Jun 1992 RTD input support
2001P Logic Identity
Module
3.0 Mar 1993 Supervisory, Notification, Requires 1716S Ver 6 ICN Driver
and Expression block for PC-30.
enhancements; Modbus Requires 1706S Ver 5
slave communications Configuration software

3.1 Apr 1994 Supports Modbus Master

communications

4.0 Jul 1994 Supports download via Requires 2006S Ver.2

Modbus Application Builder, and 2033N
module for RS-232 comm or
2034N module for RS-485
(4-wire) comm

5.0 Sept 1995 Supports sequence Requires 2006S Ver 3.0

blocks and CS-31 Application Builder software
Remote I/O

5.1 Jan 1996 Corrects potential

shutdown problems

5.2 Mar 1996 ICN lockup problem

removed

MODCELL 1.0 Jun 1992 PID, RTD support Requires Ver 5.2 firmware for
Multiloop ICN controller in link and mini-
links
2002P Regulatory
Control Identity
2.0 Mar 1993 Supervisory, Notification, Requires 1716S Ver 6 ICN driver
Module
Expression block for PC-30.
enhancements; Modbus Requires 1706S Ver 5.0
slave communications Configuration software or 2006S
Ver 1.5 Application Builder.

2.1 Apr 1994 Supports Modbus Master

communications

3.0 Jul 1994 Supports download via Requires 2006S Ver 2

Modbus and extended Application Builder, and 2033N
Modbus Master module for RS-232 comm or
communication 2034N module for RS-485
(4-wire) comm

---- Nov 1995 Discontinued Functionality included in 2004P

Advanced Control Identity module

89
MODCELL and MOD 30ML Maintenance

REVISION HISTORY

Table 13. Hardware and Firmware Revision History (Cont’d)

Instrument Rev Date Features Comments

MODCELL 1.0 Jul 1994 Batch Control; Requires 2006S Ver 2.0
Multiloop includes all Logic 4.0 & Application Builder software.
Regulatory 3.0 functions Not supported in 1706S.
2004P
plus: Modbus download requires 2033N
Batch/Advanced
Sequence blocks, and module for RS-232 comm or
Control Identity
download capability via 2034N module for RS-485 (4
Module
Modbus. wire) comm.

2.0 Apr 1995 Name changed to Requires 2006S Ver 3.0

Advanced Control. Application Builder software .
All Batch Ver 1.0 Requires 1716N Ver 8.0 ICN
functions plus CS-31 Driver for PC-30.
Remote I/O support
(replaces Batch and
Regulatory identity
modules).

2.1 Jan 1996 Potential shutdown

problems corrected.

2.2 Mar 1996 INC lockup problem

corrected

MODCELL 1.0 Jan 1992 Sequence of events Requires PC-30 ICN driver
Multiloop recording for as many as version 8.0or higher.
29 digital inputs.
2005P Sequence of
Events Recorder
2.0 Jan 1995 Added Extended Modbus
Identity Module
communication and
Omega Clock support.

MODCELL Model A ------- Engineering development Never released for sale or

Multiloop only shipment.
2031NZ RS-232
Model B Mar 1993 Serial communication via Requires Logic ver 3 or
Communications
Modbus. Regulatory ver 2 identity module.
module
------ Aug 1994 Discontinued Replaced by 2033NZ RS-232
Communications module.

90
 MODCELL and MOD 30ML Maintenance

REVISION HISTORY

Table 13. Hardware and Firmware Revision History (Cont’d)

Instrument Rev Date Features Comments

MODCELL Model A ----- Special product for Never released for general sale or
Multiloop Systems Integrated. shipment.
2032NZ RS-485
(2-wire)
Communications
module
Model B Mar 1993 Serial communication via Requires Logic version 3 or
Modbus. Regulatory version 2 identity
Also used for Omega nodule.
Clock signal in Sequence Requires 2006S Ver 2.0
of Events Recorder. Application Builder.
Does not support
download.

Model C Aug 1994 Added isolation

MODCELL Model A Aug 1994 Master or slave serial Replaces 2031N Communications
Multiloop communications via module in new systems.
Modbus. Requires 2006S Ver 2.0
2033NZ RS-232
Supports download via Application Builder.
Communications
Modbus.
module
Isolated

MODCELL Model A Aug 1994 Serial communications via Required Logic 4, Regulatory 3 or
Multiloop Modbus. Batch 1 Identity module.
Supports host Requires 2006S Ver 2.0
2034NZ RS-485
communication and Application Builder software.
Communications
download via Modbus.
module (4-wire)
Isolated

MODCELL Model B Jan 1996 Interface for Requires 2006S Ver 2.0
Multiloop Communication with Application Builder .
remote I/O modules on Requires 1716S Ver 8.0 ICN
2020NZ Remote I/O
CS-31 bus. Driver for PC-30.
Interface module

91
MODCELL and MOD 30ML Maintenance

REVISION HISTORY

Table 14. Software Revision History

Instruments
Package Rev Date Added Features Comments
Supported
Instrument 3.0 Jan 1992 MODCELL 2000 MODCELL with 1706S software does
Configurator support. 2001P Ver 1.0 Logic NOT support
Help menus. Identity module Batch/Advanced
1706S
Subdirectory support. control Identity
Can use PC-30 modules for
Workstation MODCELL Multiloop
protection key. Processors and MOD
30ML Controller.

4.0 Jun 1992 MODCELL 2000 PID, MODCELL with LCP must be Model C
RTD support. 2001P Ver. 1 or 2
Upload/download of Logic Identity
LCP databases. module.
Fixed communication MODCELL with
problems with 486 2002P Ver 1
PCs. Regulatory Identity
module.
LCP firmware
Ver. 4.

5.0 Mar 1993 MODCELL MODCELL with

Supervisory, 2001P Ver 1,2 or 3
Notification, & Logic Identity
enhanced Expression module.
blocks; MODBUS MODCELL with
communications 2002P Ver 1&2
Regulatory Identity
module.

5.1 Apr 1993 Works with App Bldr Same as above

or PC-30 Work
Station copy
protection key

5.2 Jun 1993 Resolve minor bugs Same as above

92
 MODCELL and MOD 30ML Maintenance

REVISION HISTORY

Table 14. Software Revision History (Cont’d)

Instruments
Package Rev Date Added Features Comments
Supported
Instrument 5.2 Jun 1993 Resolve minor bugs MODCELL with
Configurator (refer to Rochester 2001P Ver 1,2 or 3
for more info). Logic Identity
1706S
module.
(Cont’d)
MODCELL with
2002P Ver 1&2
Regulatory Identity
module.

5.3 Feb 1994 Resolve minor bugs Same as above Most users
(refer to Rochester unaffected.
for more info).

5.4 Oct 1994 Resolve minor bugs. Same as above Does not provide new
Download lower features for Logic 4.0,
version MODCELL Regulatory 3.0, or
databases to higher any higher version.
version identity Does not support
modules without new Batch/Advanced
feature support. Control identity
module or MOD 30ML
Controller.

5.4A Mar 1995 LCP Upload/download Same as above Applies to specific

problems fixed. database sizes.

5.5 June 1996 Resolve minor bugs. Same as above Company name
changed to ABB
Instrumentation.
Application 1.00 May 1993 Initial release MODCELL with: Requires 1716N
Builder Logic Ver 1, 2, or 3 Ver 6 or higher ICN
Regulatory Ver 1 or Driver for PC-30.
2006S
2.0 No MOD 30 support.

1.01 Aug 1993 Maintenance release Same as above All users updated
automatically, no-
charge

93
MODCELL and MOD 30ML Maintenance

REVISION HISTORY

Table 14. Software Revision History (Cont’d)

Instruments
Package Rev Date Added Features Comments
Supported
Application 1.02 Nov 1993 Maintenance release MODCELL with: Correct password
Builder Logic Ver 1, 2, or 3 protect problem;
Regulatory Ver 1 or some fields in PID
2006S
2.0 block did not allow
Continued
negative values.

1.03 Nov 1993 Maintenance release Same as above PC Comm Port setup
menu did not appear
in 1.02.

1.04 Jan 1994 Maintenance release Same as above Remove debug

statement

1.05 Feb 1994 Maintenance release Same as above Databases >32K did
not compile properly

2.0 Aug 1994 Support Sequence Logic Ver 4, Required to support

block, 1706S import, Regulatory 3, Batch identity module
and Modbus Batch 1 and all 1706S no longer
download lower versions included

2.1 Dec 1994 Maintenance release Logic Ver 4, Correct import of

Regulatory 3 Sequence blocks
and Batch 1 and all from 1706S
lower versions Fix inter-compound
connection on import.
Retain occurrence
numbers on
compound load.

3.0 Sept 1995 Support CS-31 Logic Ver 5, Reads Sequence of

Remote I/O, faster Advanced Control 2, Events identity queue
compiler, Advanced SOE 1, and all lower
Control Identity versions
Module

4.0 Feb 1996 Support 1800R MOD Same as above plus

30ML Multiloop 1800R MOD 30ML
controller

4.01 Jul 1996 Enhanced Instrument Same as above Company name

Status display to allow changed to
printing of current ABB Instrumentation
display content, and
viewing of .CRF file.

94
 MODCELL and MOD 30ML Maintenance

REVISION HISTORY

Table 14. Software Revision History (Cont’d)

Instruments
Package Rev Date Added Features Comments
Supported
ICN 4.0 Mar 1991 Support for MODCELL with
Communication (3.50) MODCELL 2000 2001P Ver 1 Logic
Driver Logic identity. Identity module
Name changed to ICN
1716S
Communications.
Note:
5.0 Jul 1992 Support for MODCELL with
Genesis revision
MODCELL PID, RTD 2001P Ver 1 or 2
equivalents are
Logic Identity
in brackets.
module.
MODCELL with
2002P Ver 1
Regulatory Identity
module .

5.1 Jul 1992 Fixes an alarm Same as above

(3.53) problem

6.0 May 1993 MODCELL MODCELL with Required for

(3.58) Supervisory, 2001P Ver 1, 2 or 3 Application Builder
Notification, & Logic Identity support
enhanced Expression module.
blocks MODCELL with
2002P Ver 1 or 2
Regulatory Identity
module .

6.1 Apr 1993 Minor bug fixes Same as above

6.2 Jun 1993 Fix open files Same as above

7.0 Aug 1994 Support for MODCELL with the

(3.60) MODCELL Multiloop following Identity
Sequence Block modules:
2001P Ver 4 Logic
2002P Ver 3
Regulatory
2004P Ver 1 Batch

95
MODCELL and MOD 30ML Maintenance

REVISION HISTORY

Table 14. Software Revision History (Cont’d)

Instruments
Package Rev Date Added Features Comments
Supported
ICN 8.0 Jan 1995 Support for Same as previous
Communication (3.62) MODCELL Sequence page plus:
Driver of Events Recorder. MODCELL with
Support for CS-31 2005P Sequence of
1716S
Remote I/O. Events, or 2004P
Continued
Ver 2 Advanced
Control identity
module.

8.1 Aug 1995 Minor bug fixes - Mini Same as above

(3.63) link powerfail bit.

9.0 Mar 1996 MOD 30ML support Same as above plus Supports operation of
(3.64) MOD 30ML a PC-30 system with
Multiloop Controller two computers.

Modbus Driver 1.0 Mar 1993 Initial release MODCELL Multiloop Requires RS-232 or
for PC-30 with all versions of RS-485
all identity modules Communications
1719S
module

2.0 Aug 1993 Supports IEEE MODCELL Multiloop Requires modules as

floating point/long with all versions of above, or built-in
integer all identity modules communications
and MOD 30ML. circuit in MOD 30ML

3.0 Apr 1995 Same as above

Extended 3.0 Aug 1996 Initial release MODCELL Multiloop Extended Modbus
Modbus Driver with all versions of protocol driver.
for PC-30 all identity modules Requires an RS-232
and MOD 30ML. or RS-485
1733S
Communications
module, or built-in
communications
circuit in MOD 30ML.

96
 MODCELL and MOD 30ML Maintenance

REVISION HISTORY

Table 14. Software Revision History (Cont’d)

Instruments
Package Rev Date Added Features Comments
Supported
EMP 5.3 May 1996 Initial release MODCELL Multiloop Extended Modbus
Communication with all versions of protocol driver.
Driver for FIX all identity modules Requires an RS-232
DMACS - 16 Bit and MOD 30ML. or RS-485
Communications
2010S
module, or built-in
communications
circuit in MOD 30ML.
EMP 6.0 Sept1996 Initial release Same as above Same as above
Communication
Driver for FIX
DMACS - 32 Bit
2011S

97
MODCELL and MOD 30ML Maintenance

REVISION HISTORY

98
 PRODUCTS AND SERVICING

A Comprehensive Instrumentation Range Servicing

Sensors, transmitters and related instruments for flow, ABB Instrumentation provides a comprehensive
temperature, pressure, level and other process vari- after sales service via a Worldwide Service
ables Organization. Contact one of the following
Flowmeters offices for details on your nearest Service and
electromagnetic, ultrasonic, turbine, differential pressure, Repair Center.
Wedge, rotary shunt, coriolis, vortex.
Differential Pressure transmitters United Kingdom
electronic and pneumatic. London
Temperature ABB Kent-Taylor Limited
sensors and transmitters, fiber optic systems. Tel: (1480) 470781
FAX: (1480) 470787
Pressure transmitters
Level United States of America
sensors and controllers. Rochester, New York
Tank gauging systems ABB Instrumentation Inc.
Cable-length measuring systems
Tel: (716) 292-6050
Fax: (716) 273-6207

Italy
Indicators, recorders, controllers and process man- Lenno (Como)
agement systems ABB Kent-Taylor SpA
Tel: (0344) 58111
Recorders Fax: (0344) 56278
circular and strip-chart types - single and multi-point - for
temperature, pressure, flow and many other process mea-
surements.

Controllers
digital display, electronic, pneumatic. Discrete single-loop
and multi-loop controllers which can be linked to a common
display station, process computer or personal computer.

Pneumatic panel or rack-mounted display and control

instrumentation

Liquid and gas monitors and analyzers for on-line and

laboratory applications
Sensors
pH, redox, selective ion, conductivity and dissolved oxygen.

Monitors and Analyzers

for water quality monitoring in environmental and power gen-
eration and general industrial applications.

Packaged analytical instrumentation laboratories

Gas analyzers
Zirconia, paramagnetic, infrared, thermal conductivity.
 IB-23M601, Issue 1 10.96

ABB Kent-Taylor Ltd ABB Instrumentation Inc ABB Kent-Taylor SpA

Howard Road, St. Neots 1175 John Street P.O. Box 20550 22016 Lenno
Cambs. Rochester, New York 14602-0550 Como
England, PE19 3EU USA Italy
Tel: (44-1480) 475321 Tel: (716) 292-6050 Tel: (0344) 58111
Fax: (44-1480) 217948 Fax: (716) 273-6207 Fax: (0344) 56278