MODCELL & MOD 30ML Maintenance: Diagnostics & Troubleshooting

MODCELL™ Multiloop Processor
and MOD 30ML™ Multiloop Controller
Diagnostic Information and Troubleshooting Procedures
for 2001N, 2002N, and 1800R
Maintenance
MicroMod Automation, Inc.
The Company
MicroMod Automation is dedicated to improving customer efficiency by providing the most cost-effective, application-specific process
solutions available. We are a highly responsive, application-focused company with years of expertise in control systems design and
implementation.
We are committed to teamwork, high quality manufacturing, advanced technology and unrivaled service and support.
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.
Use of Instructions
Ì Warning. An instruction that draws attention to the risk of
injury or death.
Note. Clarification of an instruction or additional
information.
q Caution. An instruction that draws attention to the risk of
the product, process or surroundings.
i Information. Further reference for more detailed
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 MicroMod
Automation, Inc.
Licensing, Trademarks and Copyrights
MOD 30 and MOD 30ML are trademarks of MicroMod Automation, Inc.
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:
The relevant sections of these instructions must be read carefully before proceeding.
1.
Warning Labels on containers and packages must be observed.
2.
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.
3.
Normal safety procedures must be taken to avoid the possibility of an accident occurring when operating in conditions of high
4.
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.
All software, including design, appearance, algorithms and source
codes, is copyrighted by MicroMod Automation, inc. and is owned by
MicroMod Automation or its suppliers.
MOD30ML and Modcell Maintenance
CONTENTS
CONTENTS
Page
SECTION 1 - INTRODUCTION
1.1
1.2
1.3
1.3.1
1.3.2
1.3.2
1.3.3
1.4
1.5
GENERAL ..............................................................................................................................1-1
INSTALLATION INTEGRITY ..................................................................................................1-1
DIAGNOSTIC TOOLS ...........................................................................................................1-1
MODCELL Status LEDs .........................................................................................................1-2
Application Builder Software ..................................................................................................1-2
ViZapp Software......................................................................................................................1-2
MOD 30ML Display ................................................................................................................1-2
REPAIR PHILOSOPHY .........................................................................................................1-2
RELATED INFORMATION ....................................................................................................1-3
SECTION 2 - MODCELL STATUS INDICATORS
2.1
2.2
2.3
GENERAL ..............................................................................................................................2-1
INTERPRETING STATUS LED INDICATIONS .....................................................................2-1
TROUBLESHOOTING GUIDE ..............................................................................................2-3
SECTION 3 - VIEWING DIAGNOSTIC DATA
3.1
3.2
3.2.1
3.2.2
3.3
3.3.1
3.3.2
3.3.3
3.3.4
3.3.5
3.3.6
3.3.7
3.4.1
3.4.2
3.4.3
3.5
3.5.1
3.3.2
GENERAL ..............................................................................................................................3-1
APPLICATION BUILDER .......................................................................................................3-1
Starting the Application ..........................................................................................................3-2
Setting Up Communications ...................................................................................................3-5
VIZAPP SOFTWARE ..............................................................................................................3-8
Extended Modbus (XModbus) OPC Server............................................................................3-8
ICN OPC Server......................................................................................................................3-8
Setting up Communications ....................................................................................................3-8
Setting up Communications with XModbus OPC Server........................................................3-9
Setting up Communications with ICN OPC Server.................................................................3-13
Instrument Status Viewer........................................................................................................3-18
Printing from the Status Window to a Text file........................................................................3-22
Reading Diagnostics ...............................................................................................................3-23
Reading and Writing Block Attributes .....................................................................................3-26
Commands..............................................................................................................................3-26
MOD 30ML DISPLAY .............................................................................................................3-29
Reading MOD 30ML Diagnostics ...........................................................................................3-29
MOD 30ML Commands .........................................................................................................3-32
SECTION 4 - COMMUNICATIONS
4.1
4.2
4.2.1
4.2.2
4.2.3
4.2.4
4.3
COMMUNICATING WITH A REPLACEMENT INSTRUMENT .............................................4-1
COMMUNICATION TROUBLESHOOTING ..........................................................................4-2
ICN Module Communication ..................................................................................................4-2
Modbus Module Communication ...........................................................................................4-5
Built-in ICN Communication ...................................................................................................4-6
Built-in Modbus Communication ............................................................................................4-8
APPLICATION BUILDER/INSTRUMENT COMMUNICATION MESSAGES ........................4-10
SECTION 5 - DIAGNOSING I/O MODULE PROBLEMS
5.1
5.2
5.3
5.4
GENERAL ..............................................................................................................................5-1
READING EXTENDED ERROR CODES ..............................................................................5-1
INTERPRETING EXTENDED ERROR CODE DATA ...........................................................5-3
COMMON MODULE ERRORS .............................................................................................5-6
1 -1
MOD30ML and Modcell Maintenance
CONTENTS
SECTION 6 - DIAGNOSING SHUTDOWN FAULTS
6.1
6.2
6.2.1
6.2.2
6.2.3
SHUTDOWN INFORMATION ............................................................................................... 6-1
RECORDING SHUTDOWN INFORMATION ........................................................................ 6-1
Application Builder/ViZapp Method ....................................................................................... 6-2
MOD 30ML Display Method ................................................................................................... 6-3
Memory Module Method ........................................................................................................ 6-4
SECTION 7 - EVENT CODES AND TRANSITION MESSAGES
7.1
7.2
7.3
GENERAL .............................................................................................................................. 7-1
TRANSITION MESSAGE DESCRIPTIONS .......................................................................... 7-1
EVENT CODE DESCRIPTIONS ........................................................................................... 7-2
SECTION 8 - PARTS
8.1
8.2
8.2.1
8.2.2
8.3
8.4
8.5
PARTS AVAILABILITY .......................................................................................................... 8-1
BASIC HARDWARE .............................................................................................................. 8-1
MODCELL Multiloop Processor ............................................................................................. 8-1
MOD 30ML Multiloop Controller ............................................................................................. 8-1
I/O MODULES ....................................................................................................................... 8-1
COMMUNICATION MODULES ............................................................................................ 8-2
PARTS.................................................................................................................................... 8-2
SECTION 9 - HARDWARE, FIRMWARE, AND SOFTWARE REVISION HISTORY
9.1
9.2
9.3
GENERAL .............................................................................................................................. 9-1
HARDWARE AND FIRMWARE REVISIONS ....................................................................... 9-1
SOFTWARE REVISIONS ...................................................................................................... 9-1
APPENDIX 1
A1.1
GENERAL .............................................................................................................................. A1-1
A1.2
CABLE PIN OUTS ................................................................................................................ A1-1
A1.2.1 Cables for 1720N Communication Link.................................................................................. A1-1
A1.2.2 Cables for Mini-Link External ................................................................................................. A1-2
A1-3 Technical Notes...................................................................................................................... A1-2
TECHNICAL NOTES
1.
2.
3.
4.
5.
Analog Output Readback Error Diagnostic ............................................................................
B Type Thermocouple problem with MOD 30ML and Modcell ..............................................
Faceplate Communication Error with MOD 30ML..................................................................
Grounding and Wiring Guidelines for MOD 30ML..................................................................
Instrument over-configured diagnostic with MOD 30ML and Modcell....................................
ILLUSTRATIONS
Figure
2-1
2-2
3-1
3-2
3-3
3-4
3-5
3-6
3-7
3-8
1 -2
Component Location, 2001N Processor ............................................................................... 2-3
Component Location, 2002N Processor ............................................................................... 2-3
Application Builder Untitled - (Root) Display .......................................................................... 3-3
Serial Port Setup Menu .......................................................................................................... 3-3
Instrument Status Display, Version 4.0 and Lower Versions ................................................ 3-6
Instrument Status Display, Version 4.01 ................................................................................ 3-6
Communications Setup Menu ............................................................................................... 3-7
MicroMod Extended Modbus OPC Server ............................................................................. 3-9
Add new Extended Modbus Device ....................................................................................... 3-10
Port Properties........................................................................................................................ 3-11
MOD30ML and Modcell Maintenance
CONTENTS
3-9
3-10
3-11
3-12
3-13
3-14
3-15
3-16
3-17
3-18
3-19
3-20
3-21
3-22
3-23
3-24
3-25
4-1
5-1
6-1
6-2
8-1
8-2
8-3
8-3a
8-4
8-4a
MicroMod Extended Modbus OPC Server database..............................................................3-11
MicroMod ICN OPC Server.....................................................................................................3-12
Add new ICN Device ...............................................................................................................3-13
Modcell Interface File ..............................................................................................................3-14
Port Properties ........................................................................................................................3-14
Save ICN OPC Server file.......................................................................................................3-15
Communication Setup.............................................................................................................3-16
Select OPC Server..................................................................................................................3-17
Select Device ..........................................................................................................................3-17
Communication Setup.............................................................................................................3-18
Instrument Status Window ......................................................................................................3-18
Instrument Status – Application Builder..................................................................................3-21
Instrument Status – ViZapp ....................................................................................................3-22
Command Format for Reading and Writing ............................................................................3-23
Example of Diagnostic Alarm Display ....................................................................................3-26
Device Status and Device Event Displays .............................................................................3-28
Example of Display Pages for A Diagnostic Event ................................................................3-28
Voltage Traces for a Correctly Functioning ICN ....................................................................4-4
Example of Extended Error Code (EXTERR) Data for a WRIM Module ...............................5-1
Shutdown Data Form ..............................................................................................................6-6
Shutdown Entry Display..........................................................................................................6-7
Parts for MOD 30ML (Standard) 1800RZ2_ _ _ _ _...............................................................8-3
Parts for MOD 30ML (MOD 30 Conversion Style) 1800RZ1_ _ _ _ _....................................8-3
Parts for Modcell Multi-loop Processor (Flushmount) 2002NZ_ _ _ _ _ _..............................8-4
Parts for Modcell Multi-loop Processor (Flushmount) 2002NZ_ _ _ _ _ _..............................8-4
Parts for Modcell Multi-loop Processor (Eurocard) 2001NZ_ _ _ _ _ _..................................8-5
Parts for Modcell Multi-loop Processor (Eurocard) 2001NZ_ _ _ _ _ _..................................8-5
TABLES
Table
2-1
3-1
3-2
3-3
3-4
3-5
3-6
3-7
3-8
3-9
4-1
5-1
5-2
5-3
7-1
7-2
8-1
9-1
9-2
Status LED troubleshooting Guide ........................................................................................2-4
Application Builder Startup Procedure ...................................................................................3-2
Serial Port Communication Parameters ................................................................................3-4
Communication Setup Procedure ...........................................................................................3-5
Setting up Communications with XModbus OPC Server........................................................3-9
Setting up Communications with ICN OPC Server.................................................................3-12
Instructions for using Instrument Status Viewer .....................................................................3-16
Instructions for printing to a text file ........................................................................................3-19
Status Window Commands ....................................................................................................3-24
Commands Accessible from MOD 30ML Display ..................................................................3-29
Communication Messages, Cause and Recommended Action ............................................4-11
I/O Module Identification Codes .............................................................................................5-2
Analog Input Module Extended Error (EXTERR) Codes ........................................................5-4
Analog Output Module Extended Error (EXTERR) Codes .....................................................5-5
Event Transition Message Descriptions ................................................................................7-1
Event Codes, Description and Action ....................................................................................7-2
MOD 30ML and Modcell Parts................................................................................................8-2
Hardware and Firmware Revision History .............................................................................9-2
Software Revision History ......................................................................................................9-6
1 -3
MOD30ML and Modcell Maintenance
CONTENTS
Notes
1 -4
MOD30ML and Modcell 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 Multi-loop 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
IB-MODBUS RTU – Communications Guide for use with Modcell, MOD 30ML and
Commander products
If a host computer is used with the ICN, instructions for setup of the communications link 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 -1
MOD30ML and Modcell 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
•
Mini Link / External Status LEDs
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 that
provide both operational status information and fault information. These codes can be
accessed via the instrument status display that 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
ViZapp 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 ViZapp Software. In
addition to the status display, ViZapp also provides Debug mode for troubleshooting and
Simulation. Instructions for using the ViZApp Software 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.4
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 o ViZapp Software. 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.3.5
Mini Link / External LEDs
The front panel of the External Mini Link is divided into two sections labeled ICN0 and ICN1.
Each section has three LED indicators. These Indicators provide status on the health status
of the ICNs. This is discussed in Section 4.2.5.
1 -2
MOD30ML and Modcell Maintenance
INTRODUCTION
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.
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
Training labs and tutorial can be found in the following documents:
•
IB-VIZAPP-TUT – Training labs for configuring MOD 30ML using ViZapp Software.
1 -3
MOD30ML and Modcell Maintenance
INTRODUCTION
1 -4
•
IB-1800R-SCR – Display Guide – Scripting hints, help and examples formed 30ML using
ViZapp Software
•
IB-MLOPR-TUT – MOD 30ML Operation Training manual
MOD30ML and Modcell 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. 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.
2 -1
MOD30ML and Modcell Maintenance
MODCELL STATUS INDICATORS
•
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.
•
2 .3
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.
TROUBLESHOOTING GUIDE
LEDs in the Modcell make troubleshooting easier. A troubleshooting guide providing
recommended corrective actions in the event that fault conditions are indicated is provided in
Table 2-1.
2 -2
MOD30ML and Modcell Maintenance
MODCELL STATUS INDICATORS
Figure 2-1. Component Location, 2001N Processor
Figure 2-2. Component Location, 2002N Processor
2 -3
MOD30ML and Modcell Maintenance
MODCELL STATUS INDICATORS
Table 2 -1. Status LED Troubleshooting Guide
Status LED
Condition
Red off
Green off
Problem
No power
Probable Cause
1. Power not turned on.
1. Turn on power.
2. Power not connected at
distribution panel (AC
source).
2. Connect power.
3. Instrument power supply
failed.
Red on
Green off
Green does not
turn on when
power is applied
None; normal
condition after
power-up
Instrument does
not run data
base
Red on
Green on
Instrument
without a
memory module
is in DEFAULT
state after
power-up
After power-up
instrument does
not accept
download from
memory module
2 -4
3. Return instrument for repair or
replacement.
1. Termination facility on front of
Eurocard instrument, Figure
1, not properly engaged.
1. Tighten housing screw.
2. Identity module not present.
3. Return instrument for repair or
replacement.
3. Select module failure,
processor failure or memory
failure.
Red off
Green on
Action
4. Green LED failed.
1. A valid data base was
previously loaded. Instrument
is initializing and checking
other parameters.
2. Install identity module.
4. Return instrument for repair or
replacement.
1. None, wait for instrument to
enter next state.
2. None
2. A data base has been
successfully downloaded.
Problem with red LED.
Change RUN/SERVICE 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 database, return
instrument for repair or
replacement.
1. No valid main database.
1. None - Normal out-of-box
condition.
2. Read shutdown information
and acknowledge from status
page.
2. Instrument experienced
shutdown fault on previous
power-up.
Bad memory module
database.
Read diagnostics from status
page to check validity of
memory module database.
MOD30ML and Modcell Maintenance
MODCELL STATUS INDICATORS
Status LED
Condition
Red on
Green on
(Cont’d)
Problem
After power-up
instrument is in
UPLOAD state
Instrument
operating
normally in RUN
state, changes
to HOLD state.
Instrument in
HOLD state. All
checking is
complete and
Instrument is in
LOCAL HOLD
State
Red flashing
green on
After power-up,
memory module
upload failure.
Probable Cause
Memory module switch is
set at LOAD; main
database has been
successfully copied to
memory module.
Operator initiated
command. I/O mismatch
reported or previously
reported and is
unacknowledged.
RUN /SERVICE switch is
set at SERVICE or switch
failure.
1. Memory module write
protected.
2. Bad main data base;
checksum error.
3. Bad memory module.
Action
Change memory module
switch setting to NORMAL.
Use status page or host
system to advance to next
state.
Send run/warmstart
command to instrument
(If1,NXTISTAT), then turn
off power and turn it on
again.
Change switch setting to
RUN if appropriate or test
switch.
1. Change memory module
switch setting to
READ/WRITE.
2. Read diagnostic
information and revise
configuration.
3. Replace memory module.
2 -5
MOD30ML and Modcell Maintenance
MODCELL STATUS INDICATORS
Notes:
2 -6
MOD30ML and Modcell Maintenance
VIEWING DIAGNOSTIC DATA
SECTION 3
VIEWING DIAGNOSTIC DATA
3.1
GENERAL
The purpose of this section is to provide specific how-to instructions for viewing diagnostic
data and issuing commands to the instrument. Three methods are available:
3.2
•
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.
•
ViZapp Software
The VIZapp Software can be used to view diagnostic event data and issue
commands to MODCELL and MOD 30ML instruments. See Section 3.3.
•
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.4.
APPLICATION BUILDER
Diagnostic data is viewed via the Instrument Status display in the Application Builder or
ViZapp 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 Application Builder Software.
3 -1
MOD30ML and Modcell 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 IB23H141. Start the program using the step-by-step instructions in the next.
Table 3 .1. Application Builder Startup Procedure
.
Step
Procedure
Comments
1
Access the DOS prompt for the drive and directory
where the Application Builder resides. The following
prompt appears:
C:\ APPBLD
Type STRATEGY and press the ENTER key. The
UNTITLED [ROOT] display appears in the Select mode
with the workspace empty, Figure 3.1.
Click on the About icon and note the software version
number displayed in the About window, then click on
OK to close the window.
If the drive and directory are other
than C and APPBLD, the
applicable prompt appears instead
of C:\APPBLD.
This action starts the Application
Builder. It takes a few seconds for
the display to appear.
It is useful to know the version
number of your software because
the version numbers are used as
required to identify procedural
variations in the following steps.
Selection of one of the displayed
library icons is a procedural action
used to quickly obtain access to
the status display. The icon is not
part of the instrument database.
2
3
4
From the library icons on the left side of the display,
make a selection as follows:
•
Click on any one of the displayed icons. A box
outline appears.
•
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.
•
5
6
3 -2
Click the right mouse key to close the icon
selection sequence.
Click on the Serial Port Setup icon to select it from the
TOOL BAR. A serial Port Setup menu, Figure 3.2,
appears.
Select the PC communication port you wish to use to
communicate with the instruments on your network.
MOD30ML and Modcell Maintenance
VIEWING DIAGNOSTIC DATA
Figure 3.1. Application Builder Untitled - [Root] Display
Figure 3.2. Serial Port Setup Menu
3 -3
MOD30ML and Modcell Maintenance
VIEWING DIAGNOSTIC DATA
Step
7
8
9
10
11
Procedure
Comments
Configure the selected port as follows:
•
If your software is Version 3.00 or lower, select
the Link Type Field and scroll to obtain Link for
ICN communication or None for Modbus
Communication. This field is not used in later
versions.
•
If necessary, select the base address field and
enter the required address.
•
Select the Baud Rate, Data Bits, Parity, and Stop
Bits fields. The default values are shown in bold
text in the next Table.
Select OK to activate the entries and return to the
workspace display.
Click on the Instrument Functions icon (ABB-KT or
ABB), Figure 3.1, to select it from the TOOL BAR.
A group of function icons appear below the tool bar.
Select the Status icon. The Select Tag window opens,
listing the default tag number 001
Double click on the tag number. The Instrument Status
Display, Figure 3.3, appears.
The Base Address field is
automatically determined, if
possible, when a communication
port is selected. In most cases the
address (Hex number) can be left
unchanged. A zero appears if the
software cannot determine the
address. Enter the correct address
if a zero appears or if your
computer uses a different address
than that determined through the
software check of your computer’s
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.
Set up communications as
described in Section 3.2.2.
Table 3 .2. Serial Port Communication Parameters
Comm
Type
ICN
Link
1720N
1731N
1733N
1733N
Modbu
s
3 -4
Serial
Port
None
Baud
19200, 9600, 4800, 2400,1200
Ports 1&2
Port A
(9 pin)
Port B
(25 pin)
19200, 9600
19200, 9600, 4800,
2400,1200, 600, 300
19200, 9600, 4800,2400,
1200, 600, 300
38400,19200, 9600, 4800,
2400, 1200, 600, 300,150
Data
Bits
8
Stop
Bits
1, 2
Parity
None, Even, Odd
8
8
1
1
None
None
8
1
None
8
1, 2
None, Even, Odd
MOD30ML and Modcell 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 the next Table.
Table 3 .3. Communication Setup Procedure
Step
Procedure
1
On the Instrument Status display, Figure 3.3 or
3.4, click on Setup. The communication setup
menu, Figure 3.5, appears.
Select the Communications Type field and scroll
to select either Link (ICN) or Extended Modbus or
Modbus.
If link communication was selected, proceed as
follows:
2
3
•
•
4
Select the ICN Number field and enter the
applicable ICN number: 0 - 7 for standard
link (depends on board position) or 0-1 for a
Mini-link (depends on labeled connection
port).
Select the Instrument Number field and
enter the number (0-15) of the target
instrument.
If Modbus communication was selected, select
the Modbus Address field and enter the address
(1 - 247) of the target instrument.
Comments
Communications module and wiring
connections must be compatible with
this selection.
The ICN and Instrument Number fields
are not used if Modbus was selected in
Step 2.
If an ICN communications module is
used, the target instrument number is
determined by the setting of the
address switch on the module. This
switch is read only at power up; cycle
the power if the setting is changed.
If the MOD 30ML built-in ICN
communications circuit is used, the
communications jumper must be set on
the ICN position, and the target
instrument number is determined by
configuring the ICN address and
enabling the ICN on the front panel
device setup display.
If a Modbus Communication module is
used, the address of the target
instrument is determined by the settings
of the two address switches on the
module. 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)
3 -5
MOD30ML and Modcell Maintenance
VIEWING DIAGNOSTIC DATA
Figure 3.3. Instrument Status Display, Version 4.0 and Lower Versions
Figure 3.4. Instrument Status Display Version 4.01
3 -6
MOD30ML and Modcell Maintenance
VIEWING DIAGNOSTIC DATA
Figure 3.5. Communications Setup Menu
Step
Procedure
6
Leave the Log File entry at No; scrolling to Yes
will slow communication activities.
7
Select the Database to Read field and if
necessary, scroll to select Current
Ignore the fields related to downloading. They do
not apply to diagnostics.
Select OK to activate the setup entries and return
to the Instrument Status display.
8
9
Comments
The Log File is used to capture Link or
Modbus communications to a disk file
(*.LOG). The file helps determine the
source of any communications
problems during configuration and
runtime activities.
This selection affects only attribute read
commands
Read/write commands can now be
entered as described in Sections 3.2.3,
3.2.4, and 3.2.5.
3 -7
MOD30ML and Modcell Maintenance
VIEWING DIAGNOSTIC DATA
3.3
VIZAPP SOFTWARE
Diagnostic data is viewed via the Instrument Status display in the ViZApp 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 ViZapp
software and the corresponding OPC Server. Comprehensive user information is available in
the ViZapp Help File and in the ViZapp Training Manual. You could be using either of the two
OPC Servers to communicate with the controller:
1. Extended Modbus OPC Server
2. ICN OPC Server
ViZapp Software also provides a way of to debug the control strategy and read diagnostic
information by displaying the live data from the instrument on the algorithm blocks in the
strategy. This is called the Debug mode in ViZapp. See section 3.4 for details.
3.3.1
Extended Modbus (XModbus) OPC Server
The MicroMod Extended Modbus OPC Server is an OPC compliant Server able to
communicate with Extended Modbus devices (MODCELL / MOD 30ML) and serve data to
OPC clients. This OPC server was implemented using advanced programming concepts of
OPC specifications.
The MicroMod Extended Modbus Server is installed along with ViZapp Software. Refer to the
ViZapp installation lab in the ViZapp Training Manual (IB-VIZAPP-TUT) for details.
3.3.2
ICN OPC Server
The MicroMod ICN OPC Server is an OPC compliant Server able to communicate over the
Instrument Communication Network with ICN devices (MODCELL / MOD 30ML) and serve
data to OPC clients. This OPC server was implemented using advanced programming
concepts of OPC specifications.
The MicroMod ICN OPC Server is installed along with ViZapp Software. Refer to the ViZapp
installation lab in the ViZapp Training Manual (IB-VIZAPP-TUT) for details.
3.3.3
Setting up Communications
We need to setup communications for communicating with the MOD 30ML or Modcell
instrument so that we can communicate with the instrument. You can use the built-in comm.
port of the MOD 30ML or add a comm. module to MOD 30ML or Modcell and use that port.
ViZapp lets you use the XModbus OPC Server or the ICN OPC Server to communicate with
the instrument. You need to have the right comm. port to use the OPC Server.
3 -8
MOD30ML and Modcell Maintenance
VIEWING DIAGNOSTIC DATA
The communication parameters for the built-in communication port of the MOD 30ML are
setup from the front face of the controller using the SETUP menu.
3.3.4
Setting up Communications with XModbus OPC Server
In the following example, we will use the built-in communication port of the MOD 30ML
selected as RS-232 Modbus using the comm. port jumper on the main board.
Table 3 .4. Setting up communications with XModbus OPC Server
Step
Procedure
Comments
1
Launch the Extended Modbus OPC Server:
From the Windows Start menu, select ProgramsMicroMod Automation – Control Solutions
Software Suite - XModbus OPC Server.
We will add a device to this database. We will
save this database later.
The OPC Server will launch as shown
in the next figure.
A blank tag database Untitled is
opened by default.
2
Figure 3.6. MicroMod Extended Modbus OPC Server
3
Add a hardware device to the database: Click
on the New XModbus Device button on the
toolbar or select Add-New XModbus Device
from the menu bar at the top.
This will open the Extended Modbus
Device Properties dialog box as shown
in the next figure:
3 -9
MOD30ML and Modcell Maintenance
VIEWING DIAGNOSTIC DATA
Figure 3.7. Add new Extended Modbus Device
4
We will configure the properties of the device we
are adding in this dialog box.
•
Type the name MOD30ML in the Name field
(the name is user-configurable and can be
anything!).
•
Select the serial communication port of the
computer to which the MOD 30ML is
connected, in the Port field. Click on the down
arrow in this field to show the list of enabled
serial ports and then select the port. (COM1
for example).
•
Type the instrument’s Modbus address in the
address field.
Timeout value in ms is the time for
which the OPC server tries to reestablish communication with the
device in the case of a communication
failure.
If the drop-down menu does not display
any serial port in the list, you will need
to enable the serial port to which the
device is connected to. See step 5
below.
•
5
6
3 -10
Leave the Timeout in the default value of 1000
ms.
Configure the serial port for the
communication: Click on the Edit – Ports button
on this dialog box.
Select the COMM port from the drop-down menu
in the Port field and then enable it by checking the
box next to the Enable field.
The Port Properties dialog box will be
displayed as shown below:
MOD30ML and Modcell Maintenance
VIEWING DIAGNOSTIC DATA
Figure 3.8. Port Properties
7
Choose the Baud Rate, Parity, Flow Control,
Data bits and Stop bits from this dialog box.
Click on OK to complete the Port configuration.
Make sure these entries match the settings of the
instrument.
8
Leave other fields on this dialog box at their
default values. Click on OK.
The Extended Modbus Device
Properties dialog box will redisplay with
the port number.
The default values for baud rate, data
bits and stop bits for various
communication equipment are shown in
Table 3.2.
The added device will be displayed in
the Device Tree on the left frame as
shown in the next figure:
Figure 3.9. MicroMod Extended Modbus OPC Server database
9
Open the device by double-clicking on it and
select the serial port from the Port drop-down list
if it was not already started in step 4 above. Click
on OK.
See the next figure.
3 -11
MOD30ML and Modcell Maintenance
VIEWING DIAGNOSTIC DATA
Figure 3.10. MicroMod Extended Modbus OPC Server database
10
11
11
3 -12
Save the database: Select File – Save from the
menu bar. Refer to the following figure.
Type a name for the OPC tag database file in the
File name field. Click on the Save button to save
the file.
You can now either minimize the Extended
Modbus OPC Server application or close it.
The Save As dialog box will be
displayed next.
The Title bar of the OPC Server will
redisplay with the saved file name.
MOD30ML and Modcell Maintenance
VIEWING DIAGNOSTIC DATA
3.3.5
Setting up Communications with ICN OPC Server
In the following example, we will use the built-in communication port of the MOD 30ML
selected as ICN using the comm. port jumper on the main board.
Table 3 .5. Setting up communications with ICN OPC Server
Step
Procedure
Comments
1
Launch the ICN OPC Server: From the Windows
Start menu, select Programs-MicroMod
Automation – Control Solutions Software
Suite - ICN OPC Server.
We will add a device to this database. We will
save this database later.
The OPC Server will launch as shown
in the next figure.
A blank tag database Untitled is
opened by default.
2
Figure 3.11. MicroMod ICN OPC Server
3
4
Add a hardware device to the database: Click
on the New ICN Device button on the toolbar or
select Add-New ICN Device from the menu bar
at the top.
We will configure the properties of the MOD 30ML
device we are adding in this dialog box.
•
Type the name MOD30ML in the Name field
(the name is user-configurable and can be
anything!).
•
Click on the Type drop-down menu and select
MOD 30ML or Modcell Controller.
•
Select the serial communication port of the
This will open the ICN Device
Properties dialog box as shown in the
next figure:
Timeout value in ms is the time for
which the OPC server tries to reestablish communication with the
device in the case of a communication
failure.
3 -13
MOD30ML and Modcell Maintenance
VIEWING DIAGNOSTIC DATA
computer to which the ICN Link (1731N or
1733N Mini link or 1720N Communication
Link) MOD 30ML is connected, in the Port
field. Click on the down arrow in this field to
show the drop-down menu and then select the
port. (COM1 for example).
•
Type the ICN number in the ICN Number field.
This is the ICN card’s number in the 1720N
Communication Link or 0 or 1 in the case of
Mini-link or Mini-link Ext.
•
Type the instrument’s ICN address in the
Instrument address field.
•
Leave the Timeout in the default value of 1000
ms. Click on the OK button.
If the drop-down menu does not display
any serial port in the list, you will need
to enable the serial port to which the
device is connected to. See step 7
below.
Figure 3.12. Add new ICN Device
3 -14
5
Specify a MIF file (Modcell Interface File) for
this device. The .MIF file consists of list of tags
that can be accessed by a host application like
the ICN OPC Server from this device.
6
Click on the button next to the File Name field.
Locate the file by choosing the path for the .MIF
The Modcell Interface File dialog box as
shown in the next figure will be
displayed next.
The .MIF file is created at he time of
compiling the instrument database
using the ViZapp or Application Builder
software.
The Modcell Interface File dialog box
will be displayed next. (Figure not
MOD30ML and Modcell Maintenance
VIEWING DIAGNOSTIC DATA
file and then select the file. Click on the Open
button on this dialog box.
shown).
The selected .MIF file name will be
displayed in the File Name field of the
dialog box (see the next figure).
Note:
If you are not using the OPC Server or any other
host software package for Human System
Interface, you do not have to specify the .MIF file.
Figure 3.13. Modcell Interface File
7
8
Configure the serial port for the
communication: Click on the Edit – Ports button
on this dialog box.
Select the COMM port from the drop-down menu
in the Port field and then enable it by checking the
box next to the Enable field.
The Port Properties dialog box will be
displayed as shown below:
Figure 3.14. Port Properties
9
Choose the Baud Rate, Parity, Flow Control,
Data bits and Stop bits from this dialog box.
The ICN Device Properties dialog box
will redisplay with the port number.
3 -15
MOD30ML and Modcell Maintenance
VIEWING DIAGNOSTIC DATA
Click on OK to complete the Port configuration.
Make sure these entries match the settings of the
instrument.
10
Open the device by double-clicking on it and
select the serial port from the Port drop-down list.
The default values for baud rate, data
bits and stop bits for various
communication equipment are shown in
Table 3.2.
See the next figure.
Figure 3.15. MicroMod ICN OPC Server
11
3 -16
Leave other fields on this dialog box at their
default values. Click on OK.
The added device will be displayed in
the Device Tree on the left frame as
shown in the next figure:
MOD30ML and Modcell Maintenance
VIEWING DIAGNOSTIC DATA
Figure 3.16. Save ICN OPC Server File
12
13
14
Save the database: Select File – Save from the
menu bar. Refer to the following figure.
Type a name for the OPC tag database file in the
File name field. Click on the Save button to save
the file.
The Save As dialog box will be
displayed next.
The Title bar of the OPC Server will
redisplay with the saved file name.
Note that the file has an extension
.ICNS.
You can now either or minimize the Extended
Modbus OPC Server application or close it the by
selecting File – Exit from the menu bar at the top.
3 -17
MOD30ML and Modcell Maintenance
VIEWING DIAGNOSTIC DATA
3.3.6
Instrument Status Viewer
Table 3 .6. Instructions for using Instrument Status Viewer
Step
Procedure
1
2
Switch back t the ViZapp Software.
Start the Instrument Status Viewer:
Select Instrument – Status from the menu bar at
the top. This will display the Communication
Setup dialog as shown below:
Comments
This will show the Server name and the
Device name in the respective fields.
Figure 3.17. Communication Setup
Click on the Browse button near the Server
Name field.
Select MMA.Xmodbus if you are using Extended
Modbus to communicate with the device or
MMA.ICN.DataAccess if you are using the
Instrument Communication Network (ICN) to
communicate with the device from the menu that
appears.
3 -18
A menu will appear listing all the OPC
Servers that are registered with the
system.
MOD30ML and Modcell Maintenance
VIEWING DIAGNOSTIC DATA
Figure 3.18. Select OPC Server
Click on the Browse button near the Device
Name field.
Select the device you need to communicate to
from the list
The OPC Server will be launched. A
menu will appear listing all the devices
from the OPC Server file that was last
opened by the OPC Server.
Figure 3.19. Select ICN Device
3 -19
MOD30ML and Modcell Maintenance
VIEWING DIAGNOSTIC DATA
Figure 3.20. Communication Setup
3
4
3 -20
Make no changes to the other fields in this dialog
box.
Click on OK. This will start the Instrument Status
display as shown below:
This Instrument Status display has a
text field to enter commands and a set
of buttons.
MOD30ML and Modcell Maintenance
VIEWING DIAGNOSTIC DATA
Figure 3.21. Instrument Status Window
3 -21
MOD30ML and Modcell Maintenance
VIEWING DIAGNOSTIC DATA
3.3.7
Printing from the Status Window to a text file:
Table 3 .7. Instructions for printing to a text file
1
2
3
3 -22
Add a printer in the Printers menu from the
Windows Control Panel.
Select Local Printer and then choose Text in the
Select Printer Port menu
Select Generic as the manufacturer and select
Generic/Text only as the printer
Type a name for the printer.
Click on the Print button on the Status Window
and select The printer you just added.
You will have to search for this file using Windows
Search for Files.
Open the file with Notepad.
This procedure is different for different
operating systems.
You may need your Windows CD-ROM
to install the drivers needed.
This will install the printer
This will print to a file called Text on the
hard disk.
You could rename it to desired filename
with extension txt.
MOD30ML and Modcell Maintenance
VIEWING DIAGNOSTIC DATA
3.4.1
Reading Diagnostics
Commands are typed on the command line near the bottom of the status display (Figures 33, 3-4 and 3-17) 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)
Read abnormal or quality - Return points that are active,
unacknowledged, or have bad status qualities
Read unacknowledged - Return points that are unacknowledged
Read unacknowledged or quality - Return points that are
unacknowledged or have bad unacknowledged status quality
Read active - Return points that are active
Read active or quality - Return points that are active or have bad
active status quality
Read suppressed - Return points that are suppressed
Read all points - Return all diagnostic points
ABQ
UAK
UAKQ
ACT
ACTQ
SUP
ALL
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 the next figures for Application
Builder. 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:
o
o
•
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.
3 -23
MOD30ML and Modcell Maintenance
VIEWING DIAGNOSTIC DATA
•
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.
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.
Figure 3. 22. Instrument Status – Application Builder
Another example of the message returned in response to an R DIAGS command is:
IF1 ACK_ONLY UAK G CLR G
14 INSTRUMENT POWERED UP
IF1 ACK_ONLY UAK G CLR G
14 INSTRUMENT POWERED DOWN
This message, as it appears on the status display, is shown in the next figures for viZapp.
The information contained is as follows:
•
Block Type and Occurrence Number - This identifies the block reporting the
diagnostic (IF1 in the example).
•
Classification of the diagnostic:
o
3 -24
NEW/CLR - Diagnostics having a sustained active state, which is cleared
when normal conditions are restored.
MOD30ML and Modcell Maintenance
VIEWING DIAGNOSTIC DATA
o
•
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.
Figure 3.23. Instrument Status - ViZapp
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
3 -25
MOD30ML and Modcell Maintenance
VIEWING DIAGNOSTIC DATA
messages, and use the block type and event code to find description/action information in
Section 7.3
3.4.2
Reading and Writing Block Attributes
The command format for reading or writing block attributes is as follows:
Figure 3.24. Command Format for Reading and Writing
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)
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 database 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.4.3
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 the next table
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.
3 -26
MOD30ML and Modcell Maintenance
VIEWING DIAGNOSTIC DATA
Table 3 .8. Status Window Commands
Command
ACK_SD
UP_MOD
DOWN_MOD
SET_WP
CLR_WP
DEL_MAIN
RES_MAIN
RESET
KILL
CLR_MT
CLR_Q
ACK_ALL
ACK_DIAGS
ACK_ALMS
R TIME
R DATE
R DAY
R IOLOCK
R STATE
W TIME data
W DATE data
W DAY data
W STATE data
R FG
R FGO lsp
R BLOCK blkocc#
R VERSION 1
R SD type 2
R lsp
R lsp type 3
RS lsp
RS lsp type 3
W lsp data
W lsp data type 3
ACK blkocc# diag# 4
Description
Acknowledge shutdown fault
Upload to module
Download from module
Set module write protect
Clear module write protect
Delete main data base
Restore main data base
Restart instrument after task completes
Restart instrument before completing task
Clear maximum execution times
Clear system event queue
Acknowledge all diagnostics, notification/
request messages, and process alarms
Acknowledge all diagnostics
Acknowledge all process alarms
Read instrument time of day (Time includes
Date and Day or they can issued separately)
Read instrument calendar date
Read instrument day of week
Read instrument I/O Lock status
Read instrument state
Write instrument time of day
Write instrument calendar date
Write instrument day of week
Write instrument state
Read Minimum Foreground
Read Foreground offset of attribute
Read block and display bytes in hex
Read instrument version
Read instrument shutdown area type
Read specified attribute
Read Byte Before attribute
Read specified string attribute (RS IF1,USRTAG)
Read Byte Before string attribute (RS EX1,13 H)
Write specified attribute
Write Byte Before attribute
acknowledge diagnostic point (e.g. ACK IF1
9)
Equivalent
Command
W IF1,CMD 1
W IF1,CMD 2
W IF1,CMD 3
W IF1,CMD 4
W IF1,CMD 5
W IF1,CMD 6
W IF1,CMD 7
W IF1,CMD 8
W IF1,CMD 9
W IF1,CMD 10
W SE1,CLRQCMD 1
W SE1,GLBACK 1
W SE1,DGACK 1
W SE1,PAACK 1
R IF1,TIMEDAY
R IF1,DATE
R IF1,DAY
R IF1,IOLOCK
R IF1,INSTATE
W IF1,TIMEDAY data
W IF1,DATE data
W IF1,DAY data
W IF1,NXTISTAT data
None
None
None
None
None
None
None
None
None
None
None
None
NOTES for Table 3.8:
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 6
BxA__6xxxxxxx
(Version 1, 2, 3, 4, 5 follow in same fashion)
BxA__...
2002P MODCELL Regulatory Controller Version 3
DxA__3xxxxxxx
(Version 1, 2 follow in same fashion)
DxA__...
3 -27
MOD30ML and Modcell Maintenance
VIEWING DIAGNOSTIC DATA
2004P MODCELL Batch Controller Version 1
GxA__1xxxxxxx
2004P MODCELL Advanced Controller Version 2
GxA__2xxxxxxx
2004P MODCELL Advanced Controller Version 3 GxA__3xxxxxxx
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
1800P MOD 30ML Controller Functions Version 2 IxA__2xxxxxxx
IxA__1xxxxxxx
1800P MOD 30ML Controller Functions Version 1
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.
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 -28
MOD30ML and Modcell Maintenance
VIEWING DIAGNOSTIC DATA
3.5
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.5.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 the next Figure. 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.
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 3.25. 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 as shown in the next
figure.
2. Press NXT repeatedly until the Device Events display appears.
3 -29
MOD30ML and Modcell Maintenance
VIEWING DIAGNOSTIC DATA
3 Press down arrow to enter the event queue. Page 1 for the first event in the queue
appears (figure at the bottom left of next page).
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, 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.
3 -30
MOD30ML and Modcell Maintenance
VIEWING DIAGNOSTIC DATA
Figure 3.26. Device Status and Device Event Displays
Page 1
Page 2
Figure 3.27. Example of Display Pages for a Diagnostic Event
3 -31
MOD30ML and Modcell Maintenance
VIEWING DIAGNOSTIC DATA
3.5.2
MOD 30ML Commands
Access the commands as follows:
1. Press and hold the TAG key to obtain the Device Status display.
2. Press the down arrow to enter 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:
o Use the arrow keys to display the password number.
o 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.
o Press ENT to return to the Device Status display.
o Press the down arrow to enter 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 3.8, and
execute any required command using the method of Step 6.
8. Press the TAG key to return to the runtime display.
Table 3 .9. Commands Accessible from MOD 30 ML Display
Command
CLR Q
CLR MT
ACK ALL
RESET
KILL
DEL MAIN
RES MAIN
3 -32
Description
Use to clear system event queue.
Use to clear maximum scan times for all scan groups.
Use to send global acknowledge command causing all diagnostics,
notification/request messages, and process alarms to be acknowledged.
Use to complete tasks then perform a power-up.
Use to perform an immediate power-up.
Use to mark the main database as bad and set the instrument state to
DEFAULT.
Use to mark the main database as good in case DEL MAIN command
was issued by mistake. If database is verified as good, attempts to set
instrument state to RUN.
MOD30ML and Modcell Maintenance
VIEWING DIAGNOSTIC DATA
3 -33
MOD30ML and Modcell Maintenance Manual
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.
4 -1
MOD30ML and Modcell Maintenance Manual
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:
1. Set ICN address to match the address of the instrument being replaced.
2. Set ICN status active by entering YES in response to the ENABLE?
prompt.
•
For Modbus communication:
1. Set Modbus address to match the address of the instrument
being replaced.
2. Set Modbus baud rate, parity, and stop bits to match the
instrument being replaced.
3. 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.
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 replacing an instrument on a network causes the communication problem, 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 flat side of the switch
spindle indicates the address.
3. If a 1720N Communication Link is being used, verify the setup as follows:
4 -2
MOD30ML and Modcell Maintenance Manual
COMMUNICATIONS
•
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
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
4 -3
MOD30ML and Modcell Maintenance Manual
COMMUNICATIONS
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
the next figure.
Figure 4 .1. Voltage traces for a correctly functioning ICN
8. Start the Application Builder software and access the Serial Port Setup menu, Figure 3.2.
(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.2.
9. Access the Communications Setup menu, Figure 3.5, (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.
4 -4
MOD30ML and Modcell Maintenance Manual
COMMUNICATIONS
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.4.3.
11. If you are unable to establish communications in Step 10 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.
•
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:
1. Disconnect power.
2. Disconnect all instruments from the ICN, other than the one being tested.
3. 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.
4. Restore power and try to communicate again via the R VERSION command.
4.2.2
•
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.
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
4 -5
MOD30ML and Modcell Maintenance Manual
COMMUNICATIONS
can be set to YES to provide the required resistors.
5. Apply power to the instrument.
6. Start the Application Builder software and access the Serial Port Setup menu, Figure 3.2.
(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 3.5 (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 communication 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.4.3.
9. If you are unable to establish communications in Step 8 proceed as follows:
4.2.3
•
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.
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 builtin communication via the ICN.
3. Verify that a communication module is not installed in instrument slots S9 and S10.
4. If a 1720N Communication Link is being used, verify the setup as follows:
•
4 -6
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
MOD30ML and Modcell Maintenance Manual
COMMUNICATIONS
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.
•
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 (19200 for the second port on the Mini-Link External.
•
No parity, 8data bits, 1 stop bit (these parameters are not configurable)
•
Clear-to-send (CTS) ignored
•
RS-232 transmission standard (not configurable)
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; This is signal ground (or common), not
earth or chassis ground.
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
4 -7
MOD30ML and Modcell Maintenance Manual
COMMUNICATIONS
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 3.2
(see Section 3.2.1 for procedure) or Start ViZapp Software (section 3.3.4) and set the
parameters in the OPC Server Device Properties. 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 3.5 (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.4.3.
13. If you are unable to establish communications in Step 12 proceed as follows:
4.2.4
•
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.
•
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.
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 -8
MOD30ML and Modcell Maintenance Manual
COMMUNICATIONS
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.
5. Apply power to the instrument.
6. 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.
7. Start the Application Builder software and access the Serial Port Setup menu, Figure 3.2
(see Section 3.2.1 for procedure) or start the ViZapp Software and access the Device
and Port Properties from the OPC Server (section 3.3.4). 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.
8. Access the Communications Setup menu, Figure 3.5 (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.
9. 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.4.3.
10. If you are unable to establish communications, 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 -9
MOD30ML and Modcell Maintenance Manual
COMMUNICATIONS
4.2.5 Mini Link/ External
Front Panel Indicators LEDs) on the Mini Link / External indicate the health status of the
ICNs. The front panel of the External Mini Link is divided into two sections labled ICN0 and
ICN1. Each section has three LED indicators as described below:
ENABLED: When lit, this LED indicates that the circuit controlling the instrument
communications through the corresponding ICN is active and responding properly to the
main processor.
RCV: This LED flashes during instrument to Mini Link/EXT digital communications.
SEND: This LED flashes during Mini Link/EXT to instrument digital communications.
4 -10
MOD30ML and Modcell Maintenance Manual
COMMUNICATIONS
4.3
APPLICATION BUILDER/ VIZAPP 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 database 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.
4 -11
MOD30ML and Modcell Maintenance Manual
COMMUNICATIONS
Table 4 .1. Communication Messages, Cause and Recommended Action
Message
Probable Cause
Attribute not write able
Attribute is read only.
Block creation failed
1. Unable to decompile
instrument database (.ID1)
file during upload from
instrument to Application
Builder.
2. Unable to decompile 1706S
Configurator .ID1 file during
import into Application
Builder.
Cannot change file while OPC
clients are connected to this
server
Cannot display menu
Cannot display status menu
Cannot open .ID1 or .ID2 file
This message occurs in the OPC
Server if any OPC client is
connected to the server and you
tried to open a different file from
the File menu.
Insufficient memory.
1. Insufficient memory.
2. KT.MN file has been deleted.
1. Instrument data base file
(.ID1) was deleted or not
created.
2. LCP data base file (.ID2) was
deleted or not created.
Cannot open file SIO. DAT
Checksum error
CLSIDFormString: Invalid Class
String
The Serial I/O Data file containing
communication parameters has
been deleted or the serial port
setup has not been completed.
1. Momentary fault in a link
communication.
2. Incorrect Serial Port Setup.
This error occurs while entering
one of the following modes:
Status, Upload or Download from
VIZapp Software.
No OPC Server is selected for
communication in the
Communication Setup dialog box.
(See Section 3.3.4 or 3.3.5)
4 -12
Action
Check the database reference
book for valid read/write data (See
Section 1.5).
1. Try the upload operation
again.
2. Be sure the .ID1 file contains a
valid instrument database and
then try import operation
again.
Stop the clients and then try
opening the file again.
Provide more memory.
1. Provide more memory.
2. Reinstall Application Builder.
1. Repeat compile activity to
create new file, then try to
download again (see IB23H141, Section 5.9).
2. Repeat data base upload
using LCP Utility, then try to
download again (see IB
23H141, Section 4.6.6).
Perform serial port setup to create
new file (See Section 3.2.1).
1. Try again.
2. Check Serial Port Setup (see
Section 3.2.1).
Select an OPC Server for
communication by clicking on the
Browse button on the
Communication Setup dialog box.
MOD30ML and Modcell Maintenance Manual
COMMUNICATIONS
Message
Probable Cause
Comm errors detected, Please
exit debug mode
Or
Comm errors detected for
document name, Debug mode
not available.
This error occurs when entering
ViZapp’s Debug mode and on or
more of the instrument document
(.afbd) does not have a valid OPC
Server device, or the device is not
communicating. These errors
may be acknowledged and
ignored if they do not relate to the
device that is being debugged.
CRC error.
Cross reference table creation
failed
Data comparison error
Database file exists.
Overwrite?
Database not loaded
Database not supported by
this algorithm set
Note that the error message in
ViZapp 2.0 does not indicate
which document is experiencing
the error.
1. Momentary fault in an
Extended Modbus
communication.
2. Incorrect Serial Port Setup
1. Unable to decompile
instrument database (.ID1)
file during upload from
instrument to Application
Builder.
2. Unable to decompile 1706S
Configurator .ID1 file during
import into Application
Builder.
Data received by
Communications Link does not
match data originally written due
to incorrect serial port setup, or
momentary communication fault.
A save operation is requested for
an existing database.
Local Control Panel (LCP)
database has not been uploaded
or loaded from disk.
Database being uploaded is not
supported by the configuration
capability of the Application
Builder software. For example, a
MODCELL database cannot be
uploaded if the Application
Builder has only the MOD 30ML
configuration capability.
Action
Exit debug mode.
To fix the problem, refer to the
Actions for the following messages
in this table:
1. Send Packet Unspecified Error
2. GetAddress: Unspecified Error
1. Try again.
2. Check Serial Port Setup (see
Section 3.2.1).
1. Try upload operation again.
2. Be sure the .ID1 file contains a
valid instrument database,
then try import operation
again.
Check Serial Port Setup (see
Section 3.2.1), then try again.
Answer yes or no.
Use LCP utility to make data base
available for download (see IB23H141, Section 4.6.6).
Obtain Application Builder with
required configuration capability.
There are 3 configuration types:
•
MODCELL only
•
MOD 30ML only
•
MODCELL and MOD 30ML
NOTE: Selection of the About icon
in the Application Builder tool bar
displays configuration capability of
the installed software.
4 -13
MOD30ML and Modcell Maintenance Manual
COMMUNICATIONS
Message
Deferred response overrun,
parity or framing error
Probable Cause
1. Momentary communication
fault.
2. Parity mismatch between
instrument and
Communications Link.
Device: device name not found
in Server.
Do you wish to retain block
occurrence numbers in the
compound being loaded?
Same cause as GetAddress
message in this table
This message appears whenever
a compound is loaded.
Download completed without
error
Downloading
Ending, changing instrument
state
Error opening COMx (where x
is the Com port number)
Information only
Error reading .ID1 file
Error reading .ID1 or .ID2 file
4 -14
Action
1. Try again.
2. Check that parity configured in
Serial Port Setup menu, Figure
4, matches setting of parity
status switch in link.
See the action for the GetAddress
message in this table.
If a compound is saved and then
loaded within the same database
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.
None
Information only
Information only (3-10second
duration)
The instrument is not connected
to the specified Communication
port.
None
None
Another device such as a PDA or
camera is connected to that
communication port.
Remove the device and try again.
A third party software such as PC
Synchronization for PDA or
Software for connecting other
devices is holding the port
1. Unable to decompile
instrument database (.ID1)
file during upload from
instrument to Application
builder.
2. Unable to decompile 1706S
Configurator .ID1 file during
import into Application
Builder.
1. There is an error in reading
the instrument Data Base file
(.ID1) from disk.
2. There is an error in reading
the LCP Data Base file (.ID2)
from disk.
Disable the software so that it
releases the communication port
and then try again.
Check/Change the Communication
port number and try again.
1. Try upload operation again.
2. Be sure the .ID1 file contains a
valid instrument database,
then try import operation
again.
1. Repeat compile activity to
create new file, then try to
download again.
2. Repeat data base upload
using LCP Utility to create new
file, then try to download
again.
MOD30ML and Modcell Maintenance Manual
COMMUNICATIONS
Message
Error writing .ID1 or .ID2 file
Error writing .SD1 file
GetAddress: Unspecified Error
Probable Cause
Instrument data base file (.ID1) or
LCP data base file (.ID2) cannot
accept data because:
1. Disk is full.
2. Wrong drive selected.
3. Diskette not installed.
Shutdown data file (.SD1) cannot
accept data because disk is full.
This error occurs while entering
one of the following modes:
Status, Upload or Download in
ViZapp.
Device name specified in the
Communication Setup dialog box
(See Section 3.3.4 or 3.3.5) does
not exist in the OPC Server
database.
ICN timeout - no response from
instrument
No device is selected in the
Communication setup dialog box
in ViZapp
1. Instrument power is off.
2. Configured ICN number or
instrument number does not
exist.
3. Termination facility on front of
MODCELL Eurocard
instrument not properly
engaged.
4. MOD 30ML instrument not
fully seated in its housing.
Import aborted
Information only
Import completed without error
In service manual
In valid data type
Information only
RUN/SERV switch is in SERV.
Specified data type is invalid.
e.g., RS IF1,TIME or RS EX1,I3 F
(RS can only be used with hex or
ASCII data)
A write command to change the
instrument STATE to RUN cannot
be accepted because the
RUN/SERV switch is set at
SERV.
Upload or download of LCP
database failed because
instrument at the configured
address is not an LCP.
Inst in hold state
Instrument is not a LCP
Action
1. Provide more disk space
2. Select correct drive
3. Install diskette.
Provide more disk space.
1. Select a device from the OPC
Server database by clicking on
the Browse button in the
Communication Setup dialog
box.
2. If the device name does not
exist in the OPC Server
database, add it.
1. Turn on power.
2. Check communications setup
(see Section 3.2.2).
3. Tighten housing screw, Figure
1.
4. Push instrument into housing
and tighter front panel
retaining screws.
This message follows the report of
error(s), which must be corrected
before the import can be
successfully completed.
None
Set switch at RUN
Correct entry and try again. See
Section 3.4.3.
If process condition is ready for
normal operation, change switch
setting to RUN.
Verify that instrument at address
configured on LCP Utility menu is
an LCP
4 -15
MOD30ML and Modcell Maintenance Manual
COMMUNICATIONS
Message
Probable Cause
Action
Instrument is not a MODCELL
or MOD 30ML
A MOD 30 instrument or LCP is
connected at the specified ICN
address.
1. Block containing the attribute
is not configured.
2. Attribute does not exist in the
specified block.
Information only. An instrument
state transition is in process.
Database being downloaded
contains functions not supported
by the instrument.
Verify that instrument at the
specified address is a MODCELL
or MOD 30ML.
1. Configure the required block.
Instrument reports an error
reading that attribute
Instrument state in transition
Instrument version too low to
run data base
Interpreting database
Invalid ACK
Invalid ASCII string
Invalid attribute
Invalid block checksums
Followed by:
Possibly invalid database. Do
you wish to continue?
Invalid block type
4 -16
Information only
Diagnostic acknowledgement
specifies nonexistent block
occurrence number, or inactive
diagnostic number.
Specified ASCII data is invalid.
e.g., W IF1,USRTAG 1 (ASCII
data expected; 1 specified)
An invalid attribute name was
specified. e.g. ,R IF1. COMMAND
(Command is not a valid attribute
for the IF block attribute.)
1. Instrument is not in default
state when its database is
being uploaded to the
Application Builder. The error
message appears because
the checksums are changing
during upload.
2. Unable to decompile
instrument database (.ID1)
file during upload from
instrument to Application
Builder.
3. Unable to decompile 1706S
Configurator .ID1 file during
import into Application
Builder.
An invalid block type was
specified. e.g., W IFF1,CMD 1
(IF block is misspelled IFF)
2. Check block configuration.
None
Replace instrument identity
module with a version which
accepts the database, or modify
the configuration to run on the
existing instrument version.
None
Retype command using correct
number (See Section 3.4.3)
Correct entry and try again.
Check the database reference
book for list of valid attributes
(See Section 1.5).
1. Answer YES to the request to
continue. The upload will be
successfully completed if the
database can be decompiled.
2. Answer NO to the request to
continue and try the upload
operation again.
3. Answer NO to the request to
continue. Be sure the .ID1 file
contains a valid instrument
database then try import
operation again.
Correct entry and try again.
MOD30ML and Modcell Maintenance Manual
COMMUNICATIONS
Message
Probable Cause
Invalid block type or occurrence
number
An invalid block type or
occurrence number was
specified:
e.g., ACK AI1 5
(AI is invalid block type for a Builtin Analog Input block; AIN is
correct)
e.g., ACK AIN9 5
(9 is an invalid occurrence
number for a Built-in Analog Input
block)
A data constant entered in an
expression is invalid:
1. Error occurs during a compile
activity.
2. Error occurs during an import
of a corrupt database.
1. Unable to decompile
instrument database (.ID1)
file during upload from
instrument to Application
Builder.
2. Unable to decompile 1706S
Configurator .ID1 file during
import into Application
Builder.
Specified diagnostic number is
invalid.
e.g., ACK AIN1 A
(Letter A is not valid, code must
be a number)
A command or part of a
command
is not understood.
e.g., W TIM 2:04:00.0
(TIME is misspelled TIM.)
Specified hex number is invalid.
e.g., W EX1,I3 $G H
(G is not a valid hex digit)
Momentary fault in Modbus
communication.
The write message is not
accepted because of the state of
the mode attribute.
An invalid block occurrence
number was specified.
e.g. , R SE2,PKDLEN
(block must be SE1 because
there is only one SE block in a
database)
Message Probable Cause
Action
Invalid constant
Invalid database header
Invalid diagnostic code
Invalid entry
Invalid hexadecimal number
Invalid message function code
Invalid mode
Invalid occurrence number
Action
Correct entry and try again.
1. Enter a valid data constant.
2. Obtain a valid database.
1. Try upload operation again.
2. Be sure the .ID1 file contains a
valid instrument database,
then try import operation
again.
Correct entry and try again. Refer
to Section 7 for a list of code
numbers.
Correct entry and try again.
Correct entry and try again.
Try again.
Change the mode attribute to the
appropriate state.
Correct entry and try again.
Occurrence numbers are listed in
Cross Reference Database
(.CRF) file which is created by the
Application Builder after a
database is successfully compiled.
4 -17
MOD30ML and Modcell Maintenance Manual
COMMUNICATIONS
Message
Invalid parameter
Invalid RETURNING DATA
message was returned
Invalid serial port base address
Invalid setpoint state
Invalid table checksums
Followed by:
Possibly invalid database. Do
you wish to continue?
Invalid write by cfg.
Message Probable Cause
Action
LCP not displaying main page
(Master Display)
Main database invalid
Probable Cause
Invalid write data was specified.
e.g. , W EX1,STATE 4
(4 is not a valid state value in the
EX block.
Response from Communications
Link has an invalid message
code.
The base address specified in the
Serial Port Setup menu is invalid
for the PC being used.
Writes to the PID block
SETPOINT are allowed only if the
SP MODE STATUS attribute is
FAULT or LOCAL, or if the PID
block state is DEBUG, or if the
loop state is DEBUG.
1. Instrument is not in default
state when its database is
being uploaded to the
Application Builder. The error
message appears because
the checksums are changing
during upload.
2. Unable to decompile
instrument database (.ID1)
file during upload from
instrument to Application
Builder.
3. Unable to decompile 1706S
Configurator .ID1 file during
import into Application
Builder.
The attribute is not configured as
writeable.
Attempting a database upload or
download using the LCP Utility
when the LCP is not showing the
Master Display.
1. Information
2. Communication port
mismatch detected during
database download.
3. Instrument is unconfigured
(no valid database).
4. Main database checksum
error.
4 -18
Action
Check the database reference
book for valid values (See
Section 1.5).
Check Serial Port Setup (see
Section 3.2.1), then try again.
Enter correct address in Serial
Port Setup menu. (see Section
3.2.1)
Check the database reference
book for detailed description of
attributes (See Section 1.5).
1. Answer YES to the request to
continue. The upload will be
successfully completed if the
database can be decompiled.
2. Answer NO to the request to
continue and try the upload
operation again.
3. Answer NO to the request to
continue. Be sure the .ID1 file
contains a valid instrument
database, then try import
operation again.
Check the configuration of the
block.
Exit current LCP display to return
to Master Display.
1. Read diagnostics to determine
specific cause.
2. Verify that database contains
an ICN block or MSC block
which matches the instrument
communications module.
Matching includes slot
numbers, module type, and
module address switch setting
unless ANY is configured.
3. Load a valid database.
4. Load a valid database.
MOD30ML and Modcell Maintenance Manual
COMMUNICATIONS
Message
Probable Cause
Memory module (or LCP
backup database) not present
Module database invalid
A memory module has not been
installed in the instrument.
1. Information about memory
module.
2. Communications port
mismatch detected during
download of backup main
database from memory
module.
Module switch in upload
Module write protected
No response was received
Not a MODCELL database
Not authorized source
Not enough fields for a multiple
field entry
3. No valid database in module.
4. Module database checksum
error.
5. Module database version
error.
The memory module
NORMAL/MODULE LOAD switch
is set at MODULE LOAD.
Change switch setting if required.
Module write protected Memory
module READ/WRITEREAD
ONLY switch is set at READ
ONLY to protect backup database
from being overwritten.
Memory module READ/
WRITEREAD ONLY switch is set
at READ ONLY to protect backup
database from being overwritten.
1. Specified ICN or Modbus
address is not correct.
2. Instrument is not connected
to network.
1. Unable to decompile
instrument database (.ID1)
file during upload from
instrument to Application
builder.
2. Unable to decompile 1706S
Configurator .ID1 file during
import into Application
Builder.
Another source is in control of the
loop.
Insufficient data was specified in
a command.
e.g., W EX1,I3 1.2
(data type not specified;
W EX1,I3 1.2 F is correct)
Action
Install memory module.
1. Read diagnostics to determine
specific cause.
2. Verify that database contains
an ICN block or MSC block
which matches the instrument
communications module.
Matching includes slot
numbers, module type, and
module address switch setting
unless ANY is configured.
3. Load a valid module database.
4. Same as above.
5. Same as above.
If overwriting is required, change
switch setting to READ/WRITE
If overwriting is required, change
switch setting to READ/WRITE
1. Enter correct address on
Communications Setup menu
(See Section 3.2.2).
2. Check network connections.
1. Try upload operation again.
2. Be sure the .ID1 file contains a
valid instrument database,
then try import operation
again.
Wait for the other source to
release control, or issue an
override control message.
Correct entry and try again.
4 -19
MOD30ML and Modcell Maintenance Manual
COMMUNICATIONS
Message
Probable Cause
Operator missing or improperly
used
An operator entered in an
expression is wrong or missing:
1. Error occurs during a compile
activity.
2. Error occurs during an import
of a corrupt database.
A specified value is out of range.
e.g., W EX1,I3 70000 C
(70000 is out of range for a count
data type)
A shutdown fault was detected
and has not been acknowledged.
Software protection key not
installed in parallel port of
computer running Application
Builder Software.
Protection key supplied with the
software has not been installed.
Out of range
Previous shutdown fault
Protection key not found
Protection key not found
Reading instrument version
Response overrun, parity or
framing error
Note: The message Retrying
may appear in response to
these problems.
Information only at start of the
download activity.
See below.
1. Momentary communications
fault.
2. Parity mismatch between
instrument and
communications link.
3. Parity mismatch between
instrument and Extended
Modbus network.
4. Application Builder is being
run through a DOS shell in
Windows.
Retrying
4 -20
1. Information only; a message
error was detected and the
program is trying to complete
the message successfully.
2. Response overrun, parity or
framing error
Action
1. Enter a valid operator.
2. Obtain a valid database.
Correct the specified value and try
again.
Refer to Diagnosing Shutdown
faults, Section 6.
Press any key to use application
builder in evaluation mode or
install protection key (see IB23H141, Section 2).
Connect the protection key to the
computer parallel connector and
try again.
None
1. Try again.
2. Check that parity configured in
Serial Port Setup menu, Figure
4, matches setting of parity
status switch in link.
3. Check that parity configured in
Serial Port Setup menu, Figure
4, matches parity configured in
MSC block.
4. Use a PIF file to run strategy
EXE in text, full screen,
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.
1. None if message is completed
successfully.
2. See causes and actions
above.
MOD30ML and Modcell Maintenance Manual
COMMUNICATIONS
Message
Probable Cause
Action
Save database, so that
occurrence numbers assigned
to blocks will be saved?
This message appears at the end
of each compile activity. The
reason is as follows:
During configuration, blocks
added to the graphical database
are assigned an invalid
occurrence number of zero.
During the compile activity these
blocks are assigned valid, nonzero 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.
Same as above
1. Specified ICN or Modbus
address is not correct.
The user should usually answer
YES because not saving leads to
reassignment of numbers to any
blocks with occurrence number
zero at the next compile, and this
assignment may differ from the
previous compile. Scan message
buffer full Information Try message
again.
Selection array creation failed
SendPacket: Unspecified Error
Or
SendPacket: device name
Unspecified Error
Starting, changing instrument
state
STX not found at start of
returned message
2. Instrument is not connected
to network.
Same as above
1. Enter correct address on
Communications Setup menu
(See Section 3.3.4 or 3.3.5).
2. Check network connections.
3. Momentary communications
fault.
3. Try again.
4. Parity mismatch between
instrument and Device
Properties in OPC Server.
4. Check that parity configured in
Device Properties in the OPC
Server, matches setting of
parity setup in the Instrument
configuration (MSC or ICN
blocks) or the Communication
parameters for the built-in port
from the front-face Setup
menu.
None
Information only (3-10 second
duration).
Start of transmission code
missing due to incorrect serial
port setup, or momentary
communication fault.
Check Serial Port Setup (see
Section 3.1), then try again.
4 -21
MOD30ML and Modcell Maintenance Manual
COMMUNICATIONS
Message
Time expired, message
discarded
Probable Cause
Action
One of the following messages
has been sent to the instrument:
Check configured value for the
Write Message Timeout attribute in
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 discard, and
the Write Message Timeout
attribute expires, the message is
discarded and this error message
is returned.
Check configured value for the
Write Message Timeout attribute
in the MSC block.
Time expired, message
processed
This is an Extended Modbus write
timeout NAK code. It applies to
the following messages:
•
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.
4 -22
MOD30ML and Modcell Maintenance Manual
COMMUNICATIONS
Message
Too many characters
Unable to load LSP.DLL
Unable to load MASTER .DLL
Unable to load REALSIO.DLL
Unrecognized database version
Unrecognized database version
Unrecognized instrument
version
Valid date is M,month/day/year
or D,day/month/year
Valid time is hh:min:ss.sss
(hours, minutes, seconds)
Validating database
Values written to the instrument
while in Debug mode or Run
mode are not saved to the
configuration.
Probable Cause
Too many ASCII or hex
characters specified.
e.g., W IF1,USRTAG -----string---------(USRTAG specifies a string in
excess of 25 characters)
Logical Source Pointer Dynamic
Link Library file (LSP.DLL) has
been deleted.
Master Dynamic Link Library file
(MASTER.DLL) containing Help
information has been deleted.
Real serial I/O Dynamic Link
Library file (REALSIO.DLL) has
been deleted.
Attempting to download a
database previously configured
on a newer version of the
Application Builder software.
Database being uploaded has
been configured on a newer
version of Application Builder
software.
Older version of Application
builder software does not
recognize current instrument
version at download.
An invalid date was specified.
e.g., W DATE 12/1/96
(W DATE M,12/1/96 is correct)
An invalid time was specified.
e.g., W TIME M,12/1/96
(specified date instead of time)
Information only
Information only. This means that
if you changed any of the block
parameters in debug or run
mode, these parameters are
updated in the instrument, but are
not saved to the instrument
configuration (function block
diagram) in ViZapp.
Action
Shorten string and try again.
Reinstall Application Builder
Reinstall Application Builder.
Reinstall Application Builder.
Use a compatible version of the
Application Builder, or reconfigure
database on current version of
Application Builder.
Obtain a version of the Application
Builder, which supports the
instrument database. See Section
9, Table 9.2 for compatibility of
instrument and software versions.
Obtain new version of application
builder.
Correct entry and try again.
Correct entry and try again.
None
None
4 -23
MOD30ML and Modcell Maintenance Manual
COMMUNICATIONS
4 -24
MOD30ML and Modcell Maintenance Manual
DIAGNOSING I/O MODULE PROBLEMS
SECTION 5
DIAGNOSING 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 5.1. 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 5.2 and 5.3.
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 5.2 or 5.3.
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 5.1 to confirm that the
module is correct.
5 -1
MOD30ML and Modcell Maintenance Manual
DIAGNOSING I/O MODULE PROBLEMS
Table 5 .1. I/O Module Identification Codes
Module Type
Voltage Input
Current Input
Current Input with 2-wire
transmitter power
Thermocouple
Cold Junction comp.(CJC)
RTD, 2-wire
RTD, 3-wire
Analog Output
Catalog No.
2001A
2002A
2012A
ID Code
$FE0000
$FE0100
$FE0400
2013A
2010A
2009A
2009A
2003N
$FE0200
$FE0300
$FE0500
$FE0600
$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 5.1. 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 5.1.
4. Refer to Section 5.3 for information on interpreting the error code data.
Figure 5 .1. Example of Extended Error Code Data for a WRIM Module
5 -2
MOD30ML and Modcell Maintenance Manual
DIAGNOSING I/O MODULE PROBLEMS
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.
5 -3
MOD30ML and Modcell Maintenance Manual
DIAGNOSING I/O MODULE PROBLEMS
Table 5 .2. Analog Input Module Extended Error (EXTERR) Codes
Bit/Value
15/1
Status Display Message
Conversion over-range
15/0
14/1
14/0
13/1
13/0
12/1
No message
Conversion under-range
No message
Conversion complete
Conversion incomplete
Global error is indicated
12/0
11/1
No message
Calculations performed in
module
Calculations not performed in
module
Line Frequency is 50 Hz
Line Frequency is 60 Hz
High range calibration data
loaded
Low range calibration data
loaded
Conversion range is high
Conversion range is low
Not used
A/D converter error
UART error
Calibration data error
EEPROM error
Host communications register
range error
Host communications
checksum errors
UART timeout
No error
11/0
10/1
10/0
9/1
9/0
8/1
8/0
7
6/1*
5/1*
4/1*
3/1*
2/1*
1/1*
0/1*
*0
*0 = No Error
5 -4
Problem
1. Status report
2. Upscale burnout
----------------Status report
----------------Status report
Status report
An error has been detected
No error
Status report
Action
1. None
2. Repair input circuit
----------------None
----------------None
None
See error messages (bits
0-6)
None
None
Status report
None
Status report
Status report
Status report
None
None
None
Status report
None
Status report
Status report
----------------Fault in module
Fault in module
Fault in module
Fault in module
Communications error
None
None
----------------Replace module
Replace module
Replace module
Replace module
Replace module
Communications error
Acknowledge, then try
again
Replace module
Fault in module
MOD30ML and Modcell Maintenance Manual
DIAGNOSING I/O MODULE PROBLEMS
Table 5 .3. Analog Output Module Extended Error (EXTERR) Codes
Bit/Value
15
14/1
Status Display Message
Unused
Read-back is zero
14/0
13
12/1
No message
Unused
Global error is indicated
12/0
11/1
11/0
10/1
10/0
9/1
9/0
8
7/1*
No message
Read-back is invalid
No message
Read-back is out of range
No message
In calibration mode
In standard mode
Unused
Power-up or watchdog
timeout
6/1*
5/1*
Configuration checksum error
Host communications invalid
command error
EEPROM Calibration data
error
EEPROM communications
error
Host communications register
range error
Host communications
checksum errors
Failsafe timeout
4/1*
3/1*
2/1*
1/1*
0/1*
Problem
----------------1. Incorrect connection to
module terminals
2. Module Error and Read
back Error
3. Fault in module or
Continuous error or
physical output errors
Read-back is OK
----------------An error has been detected
No error
Fault in module
Read-back is OK
Fault in module
Read-back is OK
Status report
Status report
----------------1. Power-up not
acknowledged
2. Acknowledge does not
clear power-up.
Fault in module
Fault in module
Action
----------------1. Verify connections
(see IB-23C600)
2. Refer to the technical
note TNML1001-2.
See Appendix.
3. Replace module
None
----------------See error messages (bits
0-6)
None
Replace module
None
Replace module
None
None
None
----------------1. Acknowledge powerup
2. Replace module
Replace module
Replace module
Fault in module
Replace module
Fault in module
Replace module
Instrument trying to write to
unauthorized register
Fault in module
If error is repeated replace
module
Replace module
Fault in module
Replace module
*0 = No Error
5 -5
MOD30ML and Modcell Maintenance Manual
DIAGNOSING I/O MODULE PROBLEMS
5.4
SAMPLE MODULE ERRORS
Some sample module errors and their decimal code numbers are as follows:
5 -6
•
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 – Read-back failure with watchdog; daughter board failure (replace module)
MOD30ML and Modcell Maintenance Manual
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 database. 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.
MicroMod Automation support personnel can interpret this saved information 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 MicroMod Automation 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.
6 -1
MOD30ML and Modcell Maintenance Manual
DIAGNOSING SHUTDOWN FAULTS
6.2.1
Application Builder / ViZapp 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 or the ViZapp. 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 from the software.
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.
6 -2
MOD30ML and Modcell Maintenance Manual
DIAGNOSING SHUTDOWN FAULTS
10. Keep a copy of the completed shutdown information for future reference.
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.
•
•
•
•
•
6.2.2
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.
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.
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.
6 -3
MOD30ML and Modcell Maintenance Manual
DIAGNOSING SHUTDOWN FAULTS
•
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. Keep a copy of the completed shutdown information for future reference.
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.
6.2.3
•
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.
•
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.
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.
6 -4
MOD30ML and Modcell Maintenance Manual
DIAGNOSING SHUTDOWN FAULTS
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 RS232 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 number and Version number from the identity module in the failed
instrument onto the shutdown data form.
10. Keep a copy of the completed shutdown information for future reference.
6 -5
MOD30ML and Modcell Maintenance Manual
DIAGNOSING SHUTDOWN FAULTS
MODCELL SHUTDOWN DATA
Figure 6 .1. Shutdown Data Form
6 -6
MOD30ML and Modcell Maintenance Manual
DIAGNOSING SHUTDOWN FAULTS
MOD 30ML SHUTDOWN DATA
Figure 6 .2. 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 ________________
6 -7
MOD30ML and Modcell Maintenance Manual
DIAGNOSING SHUTDOWN FAULTS
Notes:
6 -8
MOD30ML and Modcell Maintenance Manual
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 or ViZapp 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 7-1 lists the event transition messages and their descriptions. These transition
messages apply to all events for all blocks.
Message
Table 7-1. Event Transition Messages Descriptions
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 -1
MOD30ML and Modcell Maintenance Manual
EVENT CODES AND TRANSITION MESSAGES
7.2.
EVENT CODE DESCRIPTIONS
The diagnostic and informational event codes in Table 7-2 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
AIN
AOM
AOUT
CJI
CJIM
CL
DDOM
DI
DIF
DIM
DISP
DOM
EX
IC
ICN
IF
LN
LP
ML
MSC
NM
OC
7 -2
Description
Built-in Analog Input
Analog Output Module
Built-in Analog Output
Cold Junction Comp. Input Block
Cold Junction Comp. Input Module
Configured List Block
Dual Digital Output Module
Digital Input Block
Display Interface Block
Digital Input Module
Display Block
Digital Output Module
Expression Block
Input Communication Block Module
Instrument Comm. Network
Interface Block
Linearization Block
Loop Block
Modbus List Block
Modcell Serial Communication Module
Notification Message Block
Output Communication Block
PA
PAD
PID
PW
RDIM
RDOM
RI
RIM
RIO
RTI
RTTI
SE
SM
SEQ
TI
TIM
TM
TTI
VCI
VCIM
WDOM
WRIM
Process Alarm Block
Process Alarm Display Block
PID Control Block
Piecewise Table Block
Remote Digital Input Module
Remote Digital Output Module
Resistance Input Block
Resistance Input Module
Remote I/O Interface Module
RTD Input Block
RTD Transmitter Input Block
System Event
Supervisory Message Block
Sequencer Block (DVC, LSEQ, SSEQ)
Thermocouple Input Block
Thermocouple Input Module
Timer Block
Thermocouple Trans. Input Block
Voltage/Current Input Block
Voltage/Current Input Module
Wide Digital Output Module
Wide Resistance Input Module
MOD30ML and Modcell Maintenance Manual
EVENT CODES AND TRANSITION MESSAGES
Table 7-2. Event Codes, Description and Action
Block
Codes
Full Message Text
Type
AIN
4
I/O COMMUNICATIONS ERROR
AIN
5
AIN (MODULE) ERROR
AIN
AIN
AIN
AIN
AOM
AOM
AOM
6
7
8
9
4
5
6
MODE SET TO AUTO
MODE SET TO MANUAL
CJC MODE SET TO AUTO
CJC MODE SET TO MANUAL
BLOCK MODE SET TO AUTO
BLOCK MODE SET TO MANUAL
I/O MISMATCH
AOM
7
AO COMMUNICATIONS ERROR
AOM
8
AO MODULE ERROR
AOUT
AOUT
AOUT
4
5
6
BLOCK MODE SET TO AUTO
BLOCK MODE SET TO MANUAL
AOUT COMMUNICATIONS ERROR
AOUT
7
AOUT (MODULE) ERROR
CJI
CJIM
CJIM
CJIM
0-4
4
5
6
BLOCK MODE SET TO AUTO
BLOCK MODE SET TO MANUAL
I/O MISMATCH
CJIM
7
I/O COMMUNICATIONS ERROR
CJIM
8
CJC MODULE ERROR
Description/Action
Diagnostic report of a communications
problem.
Output circuit reported an output too low or too
high error.
Information only.
Information only.
Information only.
Information only.
Information only.
Information only.
A configured slot is either empty or the installed
module does not match the slot configuration.
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.
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).
Information only.
Information only.
Diagnostic report of a communications
problem.
Output circuit reported an output too low or too
high error.
See TI 0-4.
Information only.
Information only.
A configured slot is either empty or the installed
module does not match the slot configuration.
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.
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).
7 -3
MOD30ML and Modcell Maintenance Manual
EVENT CODES AND TRANSITION MESSAGES
Table 7-2. Event Codes, Description and Action (Cont’d)
Block
Codes
Full Message Text
Type
DDOM
4
BLOCK MODE_1 SET TO AUTO
DDOM
5
BLOCK MODE_1 SET TO MANUAL
DDOM
6
BLOCK MODE_2 SET TO AUTO
DDOM
7
BLOCK MODE_2 SET TO MANUAL
DDOM
8
I/O MISMATCH
DDOM
9
DDOM
DI
DI
DI
DI
DIF
10
0
1
2
3
4
DIF
5
DIM
DIM
DIM
4
5
6
DISP
4
DOM
DOM
DOM
4
5
6
DOM
7
7 -4
Description/Action
Information only.
Information only.
Information only.
Information only.
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.
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.
DDO_2_MODULE_ERROR
Same as Code 9.
BLOCK STATE SET TO RUN
Information only.
BLOCK STATE SET TO HOLD
Information only.
BLOCK STATE SET TO OFF
Information only.
BLOCK STATE SET TO DEBUG
Information only.
FACEPLATE COMMUNICATIONS ERROR An error occurred when trying to communicate
with the faceplate. Instances are counted in
CMERRCTR or BFULLCTR.
NO KEYBOARD RESPONSE
The faceplate failed to respond when keyboard
data was requested. Instances are counted in
KBERRCTR.
BLOCK MODE SET TO AUTO
Information only.
BLOCK MODE SET TO MANUAL
Information only.
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.
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.
BLOCK MODE SET TO AUTO
Information only.
BLOCK MODE SET TO MANUAL
Information only.
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.
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.
MOD30ML and Modcell Maintenance Manual
EVENT CODES AND TRANSITION MESSAGES
Table 7-2. Event Codes, Description and Action (Cont’d)
Block
Codes
Full Message Text
Type
EX
0
BLOCK STATE SET TO RUN
EX
1
BLOCK STATE SET TO HOLD
EX
2
BLOCK STATE SET TO OFF
EX
3
BLOCK STATE SET TO DEBUG
EX
4
CALCULATION ERROR
IC
IC
IC
IC
IC
0
1
2
3
4
BLOCK STATE SET TO RUN
BLOCK STATE SET TO HOLD
BLOCK STATE SET TO OFF
BLOCK STATE SET TO DEBUG
RECEIVING UNEXPECTED MESSAGE
IC
5
NOT RECEIVING DATA
IC
IC
6
7
BLOCK MODE SET TO MANUAL
BLOCK MODE SET TO AUTO
Description/Action
Information only.
Information only.
Information only.
Information only.
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.
Information only.
Information only.
Information only.
Information only.
There is a configuration error (source or data
type incorrect) within either this block or within
an Output Communication block in another
instrument.
A break in the communications has halted the
continual flow of data from the source. No new
data has been received for 2 seconds.
Information only.
Information only.
7 -5
MOD30ML and Modcell Maintenance Manual
EVENT CODES AND TRANSITION MESSAGES
Table 7-2. Event Codes, Description and Action (Cont’d)
Block
Codes
Full Message Text
Type
ICN
4
MODULE MISMATCH
ICN
5
ACCESS TIMEOUT
ICN
ICN
6
7
RESTART FAILURE
INVALID MESSAGE
ICN
8
MESSAGE DATA INVALID
ICN
9
FRAMING ERROR
ICN
10
NOISE ERROR
ICN
11
OVERRUN ERROR
ICN
12
INVALID MESSAGE SIZE
ICN
13
EXCESS MESSAGES RECEIVED
ICN
14
EXCESS MESSAGES TO TRANSMIT
ICN
15
UNEXPECTED COMM MESSAGE
RECEIVED
ICN
16
COMMUNICATION OVERLOAD
ICN
17
EXCESS MESSAGES FOR TASK
7 -6
Description/Action
The slots configured for an ICN
communications module are either empty or the
installed module does not match the slot
configuration.
Access to transmit has not been granted for at
least one second. Token ring is broken, ICN
restarted.
Communications cannot be established.
The message code of a received message was
invalid or is not supported by the software.
A received message could not be processed
because it failed the CRC check.
No stop bit was detected by the 68032 for a
received byte.
The 68302 checked a bit three times and the
three samples were not identical.
The central processor could not store a
received byte before the next byte was
received.
The size of the message or its data field is
invalid.
The receive buffer for this port had no room for
the message being received. A message is
"lost".
The buffer used for the messages to be
transmitted had no room for another. A
message is "lost".
An input communications message was
received, but the occurrence for which it was
destined is not in the current configuration.
The time for each instrument on the ICN to
transmit all messages exceeded the
recommended time of 250 msec.
The maximum number of requests queued for a
group has been reached. A message is "lost".
MOD30ML and Modcell Maintenance Manual
EVENT CODES AND TRANSITION MESSAGES
Table 7-2. Event Codes, Description and Action (Cont’d)
Block
Codes
Full Message Text
Type
IF
4
DEFAULT DATABASE CHECKSUM
ERROR
IF
5
MAIN DATABASE CHECKSUM ERROR
IF
6
IF
7
IF
8
IF
9
IF
10
IF
11
IF
12
IF
13
IF
14
IF
15
Description/Action
The instrument was shut down due to a
checksum error in the default database.
The instrument was shut down due to a
checksum error in the main database.
INSTRUMENT IS UNCONFIGURED
There is no valid user database in the
instruments main RAM.
MAIN DATABASE VERSION ERROR
A user database was rejected because the
instrument does not have the hardware and/or
firmware resources to run it.
MEMORY MODULE CHECKSUM ERROR The memory module database has been
marked bad because a checksum error was
found in it.
MEMORY MODULE IS UNCONFIGURED A memory module database was not
downloaded because no valid database was
found in the module.
MEMORY MODULE DATABASE
A memory module database was not
VERSION ERROR
downloaded because the instrument does not
have the hardware and/or firmware resources
to run it.
MEMORY MODULE IS WRITE
The switch on the module is in the ‘read only’
PROTECTED
position.
MEMORY MODULE IS SOFT WRITE
The write protect bit in the module RAM has
PROTECTED
been set by software.
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.
INSTRUMENT POWERED UP
The instrument went through power-up. A time
stamp indicating the time power was restored is
entered in the event queue.
INSTRUMENT POWERED DOWN
The instrument lost power. A time stamp
indicating the time power was lost is entered in
the event queue.
7 -7
MOD30ML and Modcell Maintenance Manual
EVENT CODES AND TRANSITION MESSAGES
Table 7-2. Event Codes, Description and Action (Cont’d)
Block
Codes
Full Message Text
Type
IF
16 COMMUNICATIONS PORT MISMATCH
IF
17
INSTRUMENT SHUTDOWN FAULT
IF
18
MODULE SHUTDOWN FAULT
IF
19
PROCESSOR WATCHDOG FAULT
IF
20
SPURIOUS EVENT FAULT
7 -8
Description/Action
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
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.
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.
When the instrument was last powered, the
processor got 'lost' and the watchdog timer shut
the instrument down. See Code 17,
INSTRUMENT SHUTDOWN 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.
MOD30ML and Modcell Maintenance Manual
EVENT CODES AND TRANSITION MESSAGES
Table 7-2. Event Codes, Description and Action (Cont’d)
Block
Codes
Full Message Text
Type
IF
21 EPROM CHECKSUM FAULT
IF
22
BAD RAM FAULT
IF
23
I/O BOARD 1 COMMUNICATIONS
ERROR
IF
39
BAD CLOCK CHIP
IF
40
TIME AND DATE NOT VALID
IF
41
I/O IS LOCKED
IF
42
COMMUNICATION BLOCKS ARE
LOCKED
IF
43
DMA FAULT
Description/Action
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.
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.
An error (no response or bad message
checksum) occurred in trying to communicate
with the carrier board. There are wrap around
counters for these errors at IF1,SLNORSPS
and IF1,SLCHKSMS.
The real time clock chip is not working
correctly. Time and date information will not
remain current through a power outage.
The time of day, calendar date, and day of
week need to be set.
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.
Communications are locked because Attribute
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.
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 .
7 -9
MOD30ML and Modcell Maintenance Manual
EVENT CODES AND TRANSITION MESSAGES
Table 7-2. Event Codes, Description and Action (Cont’d)
Block
Codes
Full Message Text
Type
IF
44 I/O OVERRUN
Description/Action
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.
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.
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.
MEMORY MODULE DOWNLOAD FAILED The memory module database was not
downloaded. Another diagnostic will be present
to indicate why the download did not happen.
DOWNLOAD FROM MEMORY MODULE Information only: The memory module
database was downloaded to main RAM.
IF
45
IF
46
IF
47
IF
128
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.
7 -10
MOD30ML and Modcell Maintenance Manual
EVENT CODES AND TRANSITION MESSAGES
Table 7-2. Event Codes, Description and Action (Cont’d)
Block
Codes
Full Message Text
Type
IF
135 INSTRUMENT IN HOLD STATE
Description/Action
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
LN
LN
LN
LN
LN
0
1
2
3
4
BLOCK STATE SET TO RUN
BLOCK STATE SET TO HOLD
BLOCK STATE SET TO OFF
BLOCK STATE SET TO DEBUG
CALCULATION ERROR
LP
LP
LP
LP
LP
0
1
2
3
4
BLOCK STATE SET TO RUN
BLOCK STATE SET TO HOLD
BLOCK STATE SET TO OFF
BLOCK STATE SET TO DEBUG
REMOTE STATE INPUT INVALID
Information only: Indicates that time of day,
calendar date or day of week has been written
to.
Information only.
Information only.
Information only.
Information only.
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.
Information only.
Information only.
Information only.
Information only.
The remote state input has an invalid value,
and the composite state takes on the remote
error state value.
7 -11
MOD30ML and Modcell Maintenance Manual
EVENT CODES AND TRANSITION MESSAGES
Table 7-2. Event Codes, Description and Action (Cont’d)
Block
Codes
Full Message Text
Type
MSC
4
MODULE MISMATCH
MSC
5
MESSAGE CHECK ERROR
MSC
6
PARITY ERROR
MSC
7
BREAK ERROR
MSC
8
FRAMING ERROR
MSC
9
NOISE ERROR
MSC
10
OVERRUN ERROR
MSC
11
INVALID MESSAGE
MSC
12
EXCESS MESSAGES FOR PORT
MSC
13
EXCESS MESSAGES FOR TASK
MSC
14
DEFAULT COMM SWITCH SET
7 -12
Description/Action
The slot(s) configured for a MODBUS
communications module is either empty or the
installed module does not match the slot
configuration.
A received message could not be processed
because it failed the Cyclical Redundancy
Check (CRC) check.
A parity error was detected for a received byte.
The message is discarded.
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.
No stop bit was detected by the 68032 for a
received byte.
The 68302 checked a bit three times and the
three samples were not identical.
The central processor could not store a
received byte before the next byte was
received.
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.
The receive buffer for this port had no room for
the message being received. A message is
lost.
The maximum number of requests queued for a
group has been reached. A message is lost.
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.
MOD30ML and Modcell Maintenance Manual
EVENT CODES AND TRANSITION MESSAGES
Table 7-2. Event Codes, Description and Action (Cont’d)
Block
Codes
Full Message Text
Type
NM
0
BLOCK STATE SET TO RUN
NM
1
BLOCK STATE SET TO HOLD
NM
2
BLOCK STATE SET TO OFF
NM
3
BLOCK STATE SET TO DEBUG
NM
4
REQUESTED DATA NOT RECEIVED
NM
OC
OC
OC
OC
OC
OC
PA
PA
PA
PA
PA
PAD
PAD
PAD
PAD
PAD
PAD
PAD
PAD
PAD
PAD
PAD
PAD
PAD
PAD
PAD
PAD
5
0
1
2
3
4
5
0
1
2
3
4
0
1
2
3
4
4
4
4
4
4
4
4
4
4
4
4
NOTIFICATION MESSAGE
BLOCK STATE SET TO RUN
BLOCK STATE SET TO HOLD
BLOCK STATE SET TO OFF
BLOCK STATE SET TO DEBUG
BLOCK MODE SET TO MANUAL
BLOCK MODE SET TO AUTO
BLOCK STATE SET TO RUN
BLOCK STATE SET TO HOLD
BLOCK STATE SET TO OFF
BLOCK STATE SET TO DEBUG
PROCESS ALARM
BLOCK STATE SET TO RUN
BLOCK STATE SET TO HOLD
BLOCK STATE SET TO OFF
BLOCK STATE SET TO DEBUG
PV LO
PV LOLO
PV HI
PV HIHI
DEV LO
DEV LOLO
DEV HI
DEV HIHI
OUT LO
OUT LOLO
OUT HI
OUT HIHI
Description/Action
Information only.
Information only.
Information only.
Information only.
Requested data has not been received within
the time-out period.
Information only.
Information only.
Information only.
Information only.
Information only.
Information only.
Information only.
Information only.
Information only.
Information only.
Information only.
Information only.
Information only.
Information only.
Information only.
Information only.
Process Value Low
Process Value Low Low
Process Value High
Process Value High High
Deviation Value Low
Deviation Value Low Low
Deviation Value High
Deviation Value High High
Output Value Low
Output Value Low Low
Output Value High
Output Value High High
7 -13
MOD30ML and Modcell Maintenance Manual
EVENT CODES AND TRANSITION MESSAGES
Table 7-2. Event Codes, Description and Action (Cont’d)
Block
Codes
Full Message Text
Type
PID
0
BLOCK STATE SET TO RUN
PID
1
BLOCK STATE SET TO HOLD
PID
2
BLOCK STATE SET TO OFF
PID
3
BLOCK STATE SET TO DEBUG
PID
4
CALCULATION ERROR
PID
5
CONTROL OUTPUT CALCULATION
ERROR
RDIM
RDIM
RDIM
RDIM
RDIM
RDIM
4
5
6 •••
34
35
36
CHANNEL 0 MODE SET TO AUTO
CHANNEL 0 MODE SET TO MANUAL
Repeat for Channels 1 to 14
CHANNEL 15 MODE SET TO AUTO
CHANNEL 15 MODE SET TO MANUAL
I/O MISMATCH
RDIM
37
MODULE EXTENDED ERROR
7 -14
Description/Action
Information only.
Information only.
Information only.
Information only.
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.
A calculation error (calculation overflow, divide
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.
Information only.
Information only.
Information only.
Information only.
A configured address on the CS-31 bus is not
used or the installed remote module does not
match the address configuration.
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).
MOD30ML and Modcell Maintenance Manual
EVENT CODES AND TRANSITION MESSAGES
Table 7-2. Event Codes, Description and Action (Cont’d)
Block
Codes
Full Message Text
Type
RDOM
4
CHANNEL 0 MODE SET TO AUTO
RDOM
5
CHANNEL 0 MODE SET TO MANUAL
RDOM 6 ••• Repeat for Channels 1 to 14
RDOM
34 CHANNEL 15 MODE SET TO AUTO
RDOM
35 CHANNEL 15 MODE SET TO MANUAL
RDOM
36 I/O MISMATCH
RDOM
37
MODULE EXTENDED ERROR
RI
RI
RI
RI
RI
0
1
2
3
4
BLOCK STATE SET TO RUN
BLOCK STATE SET TO HOLD
BLOCK STATE SET TO OFF
BLOCK STATE SET TO DEBUG
CALCULATION ERROR
RIM
RIM
RIM
4
5
6
BLOCK MODE SET TO AUTO
BLOCK MODE SET TO MANUAL
I/O MISMATCH
RIM
7
I/O COMMUNICATIONS ERROR
RIM
8
RIM MODULE ERROR
Description/Action
Information only.
Information only.
Information only.
Information only.
A configured address on the CS-31 bus is not
used or the installed remote module does not
match the address configuration.
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).
Information only.
Information only.
Information only.
Information only.
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.
Information only.
Information only.
A configured slot is either empty or the installed
module does not match the slot configuration.
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.
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).
7 -15
MOD30ML and Modcell Maintenance Manual
EVENT CODES AND TRANSITION MESSAGES
Table 7-2. Event Codes, Description and Action (Cont’d)
Block
Codes
Full Message Text
Type
RIO
4
I/O MISMATCH
RIO
5
CS-31 BUS COMMUNICATION ERROR
RIO
6
I/O COMMUNICATIONS ERROR
RIO
7
CS-31 DATABASE CHECKSUM ERROR
RIO
RTI
RTI
RTI
RTI
RTI
8
0
1
2
3
4
MODULE EXTENDED ERROR
BLOCK STATE SET TO RUN
BLOCK STATE SET TO HOLD
BLOCK STATE SET TO OFF
BLOCK STATE SET TO DEBUG
CALCULATION ERROR
RTTI
RTTI
RTTI
RTTI
RTTI
0
1
2
3
4
BLOCK STATE SET TO RUN
BLOCK STATE SET TO HOLD
BLOCK STATE SET TO OFF
BLOCK STATE SET TO DEBUG
CALCULATION ERROR
7 -16
Description/Action
A configured slot is either empty or the installed
module does not match the slot configuration.
There is an error in communication or loss of
communication between the RIO interface
module and the CS-31 bus.
An error occurred in communication between
the RIO module and the instrument.
The remote I/O database stored in the interface
module has been declared bad due to a
checksum error.
There is an RIO module error.
Information only.
Information only.
Information only.
Information only.
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.
Information only.
Information only.
Information only.
Information only.
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.
MOD30ML and Modcell Maintenance Manual
EVENT CODES AND TRANSITION MESSAGES
Table 7-2. Event Codes, Description and Action (Cont’d)
Block
Codes
Full Message Text
Type
SE
4
ALL DIAG, PA AND NM GLOBALLY
ACKED.
SE
5
ALL DIAGNOSTICS GLOBALLY ACKED.
SE
6
ALL PROCESS ALARMS GLOBALLY
ACKED.
SE
7
ALL NOTIF/REQ MSGS GLOBALLY
ACKED.
SE
8
ALL GROUP DIAGNOSTICS
SUPPRESSED
SE
9
ALL GROUP DIAGNOSTICS ENABLED
SE
10 GROUP 1 DIAGNOSTICS SUPPRESSED
SE
11 GROUP 1 DIAGNOSTICS ENABLED
SE
12 GROUP 2 DIAGNOSTICS SUPPRESSED
SE
13 GROUP 2 DIAGNOSTICS ENABLED
SE
14 GROUP 3 DIAGNOSTICS SUPPRESSED
SE
15 GROUP 3 DIAGNOSTICS ENABLED
SE
16 GROUP 4 DIAGNOSTICS SUPPRESSED
SE
17 GROUP 4 DIAGNOSTICS ENABLED
SE
18 GROUP 5 DIAGNOSTICS SUPPRESSED
SE
19 GROUP 5 DIAGNOSTICS ENABLED
SE
20 GROUP 6 DIAGNOSTICS SUPPRESSED
SE
21 GROUP 6 DIAGNOSTICS ENABLED
SE
22 GROUP 7 DIAGNOSTICS SUPPRESSED
SE
23 GROUP 7 DIAGNOSTICS ENABLED
SE
24 SYSTEM EVENT QUEUE CLEARED
SM
0
BLOCK STATE SET TO RUN
SM
1
BLOCK STATE SET TO HOLD
SM
2
BLOCK STATE SET TO OFF
SM
3
BLOCK STATE SET TO DEBUG
SM
4
SUPERVISORY MESSAGE ERROR
Description/Action
Information only.
Information only.
Information only.
Information only.
Information only.
Information only.
Information only.
Information only.
Information only.
Information only.
Information only.
Information only.
Information only.
Information only.
Information only.
Information only.
Information only.
Information only.
Information only.
Information only.
Information only.
Information only.
Information only.
Information only.
Information only.
A supervisory message failed.
7 -17
MOD30ML and Modcell Maintenance Manual
EVENT CODES AND TRANSITION MESSAGES
Table 7-2. Event Codes, Description and Action (Cont’d)
Block
Codes
Full Message Text
Type
SEQ
0
BLOCK STATE SET TO RUN
SEQ
1
BLOCK STATE SET TO HOLD
SEQ
2
BLOCK STATE SET TO OFF
SEQ
3
BLOCK STATE SET TO DEBUG
SEQ
4
SEQ BLOCK BAD INPUT DETECTED
SEQ
5
SEQ BLOCK CALC ERROR
SEQ
6
SEQ BLOCK STEP OUT OF RANGE
SEQ
7
SEQ BLOCK FAILURE
SEQ
SEQ
SEQ
8
9
10
BLOCK SET TO MANUAL
BLOCK MODE SET TO AUTO
BLOCK MODE SET TO SEMI-AUTO
7 -18
Description/Action
Information only.
Information only.
Information only.
Information only.
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).
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).
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).
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
Information only.
Information only.
Information only.
MOD30ML and Modcell Maintenance Manual
EVENT CODES AND TRANSITION MESSAGES
Table 7-2. Event Codes, Description and Action (Cont’d)
Block
Codes
Full Message Text
Type
TI
0
BLOCK STATE SET TO RUN
TI
1
BLOCK STATE SET TO HOLD
TI
2
BLOCK STATE SET TO OFF
TI
3
BLOCK STATE SET TO DEBUG
TI
4
CALCULATION ERROR
TTI
TTI
TTI
TTI
TTI
0
1
2
3
4
BLOCK STATE SET TO RUN
BLOCK STATE SET TO HOLD
BLOCK STATE SET TO OFF
BLOCK STATE SET TO DEBUG
CALCULATION ERROR
TIM
TIM
TIM
4
5
6
BLOCK MODE SET TO AUTO
BLOCK MODE SET TO MANUAL
I/O MISMATCH
TIM
7
I/O COMMUNICATIONS ERROR
Description/Action
Information only.
Information only.
Information only.
Information only.
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.
Information only.
Information only.
Information only.
Information only.
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.
Information only.
Information only.
A configured slot is either empty or the installed
module does not match the slot configuration.
One of the following conditions was detected:
• There is a checksum error in the
communications between this block and the
module.
TIM
8
TI MODULE ERROR
• The select circuit, which is used to
communicate with the module, has a
diagnostic error. In this case, all modules
report a communications 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).
7 -19
MOD30ML and Modcell Maintenance Manual
EVENT CODES AND TRANSITION MESSAGES
Table 7-2. Event Codes, Description and Action (Cont’d)
Block
Codes
Full Message Text
Type
TM
0
BLOCK STATE SET TO RUN
TM
1
BLOCK STATE SET TO HOLD
TM
2
BLOCK STATE SET TO OFF
TM
3
BLOCK STATE SET TO DEBUG
VCI
0
BLOCK STATE SET TO RUN
VCI
1
BLOCK STATE SET TO HOLD
VCI
2
BLOCK STATE SET TO OFF
VCI
3
BLOCK STATE SET TO DEBUG
VCI
4
CALCULATION ERROR
VCIM
VCIM
VCIM
4
5
6
BLOCK MODE SET TO AUTO
BLOCK MODE SET TO MANUAL
I/O MISMATCH
VCIM
7
I/O COMMUNICATIONS ERROR
Description/Action
Information only.
Information only.
Information only.
Information only.
Information only.
Information only.
Information only.
Information only.
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.
Information only.
Information only.
A configured slot is either empty or the installed
module does not match the slot configuration.
One of the following conditions was detected:
• There is a checksum error in the
communications between this block and the
module.
VCIM
7 -20
8
VI MODULE ERROR
• The select circuit, which is used to
communicate with the module, has a
diagnostic error. In this case, all modules
report a communications 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).
MOD30ML and Modcell Maintenance Manual
EVENT CODES AND TRANSITION MESSAGES
Table 7-2. Event Codes, Description and Action (Cont’d)
Block
Codes
Full Message Text
Type
WDOM
4
BLOCK MODE SET TO AUTO
WDOM
5
BLOCK MODE SET TO MANUAL
WDOM
6
I/O MISMATCH
WDOM
7
WDO_MODULE_ERROR
Description/Action
Information only.
Information only.
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.
One of the following conditions was detected:
• The module read-back value is not the same
as the previous result value.
WRIM
WRIM
WRIM
4
5
6
BLOCK MODE SET TO AUTO
BLOCK MODE SET TO MANUAL
I/O MISMATCH
WRIM
7
I/O COMMUNICATIONS 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.
Information only.
Information only.
A configured slot is either empty or the installed
module does not match the slot configuration.
One of the following conditions was detected:
• There is a checksum error in the
communications between this block and the
module.
WRIM
8
WRIM MODULE ERROR
• The select circuit, which is used to
communicate with the module, has a
diagnostic error. In this case, all modules
report a communications 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).
7 -21
MOD30ML and Modcell Maintenance Manual
EVENT CODES AND TRANSITION MESSAGES
7 -22
MOD30ML and Modcell Maintenance Manual
PARTS
SECTION 8
PARTS
8.1
PARTS AVAILABILITY
All MODCELL and MOD 30ML components, which are identified by catalog numbers or part
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
2005A Solid-State Relay Output Module
2006A Nonisolated Digital Input Module
2007A Nonisolated Digital Output Module
2011A Mechanical Relay Output Module
8 -1
MOD30ML and Modcell Maintenance Manual
PARTS
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)
8 -2
MOD30ML and Modcell Maintenance Manual
PARTS
8.5
PARTS
The following table lists all the saleable parts of the MOD 30ML and Modcell instruments:
Table 8.1 MOD 30ML and Modcell Parts
Part No.
MOD 30ML
125U2955-3B
125U2955-3C
125U2955-3D
125U2955-3E
125U2888-1
125U2917-2
125U3034-2
125U2916-2
1800FZ00003A
1800FZ00002A
124S2330-4A
124S2330-4B
124S2330-5A
124S2330-5B
Description
Standard display assembly
NEMA 4 display assembly
Narrow Bezel (1801R) display assembly
Russian display assembly
CPU board
Main Board - AC
Main Board - DC
Main Board – MOD30 Conversion
Not published
DC with MOD30 Cable
Connections
Housing & Termination – Standard
Housing & Termination – MOD30
Conversion
Terminal Block – Lower Left (1-15)
Terminal Block – Lower Right (Chassis-40)
Terminal Block – Upper Left (16-25)
Terminal Block – Upper Right (41-Chassis)
MODCELL Multiloop
125U2971-1
Carrier board - Flushmount
125U2874-2
Carrier board - Eurocard
125U2976-1
CPU board - Flushmount
125U2888-1
CPU board - Eurocard
125U2931-1
Select module
125U2873-2
AC Power supply
125U2873-3
AC Power supply - CE Mark
125U2973-1
DC Power supply
175S28
Flushmount termination block kit
2050R
125U2951-16
125U2955-3
125U2955-3A
124S2330-1
Notes
CPU board
Display assembly
2051R display assembly
Termination Assembly
Same for Eurocard and Flushmount
There is no CE-mark DC version
Plug-in side of terminations
Includes Terminal Blocks (3)
The following figures illustrate the MOD 30ML parts for both the standard and the MOD 30
replacement models:
8 -3
MOD30ML and Modcell Maintenance Manual
PARTS
Figure 8 .1. Parts for MOD 30ML (Standard) 1800RZ2_ _ _ _ _
Figure 8 .2. Parts for MOD 30ML (MOD 30 Conversion Style)1800RZ1_ _ _ _ _
8 -4
MOD30ML and Modcell Maintenance Manual
PARTS
Figure 8 .3. Parts for Modcell Multi-loop Processor (Flushmount) 2002NZ_ _ _ _ _ _
Power Supply
125U2873-2
125U2873-3 (CE mark)
125U2973-1 (DC)
Termination block kit
175S28
Modules
Identity Module
2001P/2004P
CPU board
125U2976-1
Memory
module
2010P
Select Module
125U2931-1
Carrier board
125U2971-1
Figure 8 .3a. Parts for Modcell Multi-loop Processor (Flushmount) 2002NZ_ _ _ _ _ _
8 -5
MOD30ML and Modcell Maintenance Manual
PARTS
Figure 8 .4. Parts for Modcell Multi-loop Processor (Eurocard) 2001NZ_ _ _ _ _ _
Identity module
2001P/2004P
Power supply
125U2873-2
125U2873-3 (CE mark)
125U2973-1 (DC)
Termination Shell
2002FZ10001A
Modules
Memory module
2010P
Select module
125U2931-1
Carrier board
125U2874-2
Comm. Module
slots
CPU board
125U2888-1
Figure 8 .4a. Parts for Modcell Multi-loop Processor (Eurocard) 2001NZ_ _ _ _ _ _
8 -6
MOD30ML and Modcell Maintenance Manual
PARTS
8 -7
MOD30ML and Modcell Maintenance Manual
HARDWARE, FIRMWARE AND SOFTWARE 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. Either a number or a model letter identifies the product revisions. 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 9.1. 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
9.3
•
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
SOFTWARE REVISIONS
The revision history for Modcell software is listed in Table 9.2. 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
9 -1
MOD30ML and Modcell Maintenance Manual
HARDWARE, FIRMWARE AND SOFTWARE REVISION HISTORY
Table 9.1. Hardware and Firmware Revision History
Instrument
Communications
Links
(1720N, 1731N,
1733N)
Rev
Date
Features
2.0
Mid-1984
Initial firmware release
3.0
December 1984 SLU compatibility
4.0
5.0
August 1986
5.1
September
1989
Link-wide supervisory messages via
SLU
Enhanced communications for
MOD 300 compatibility
ICN driver enhancements
Comments
NOT compatible with SLU
REQUIRES VERSION 4
INSTRUMENTS
REQUIRES VERSION 3 SLU
CPU and ICN boards both at v.5
CPU and ICN boards both at 5.1
Support for Accuray product
Communications
Links, ICN
Controller only
(1720N, 1731N,
1733N, 1734N)
5.2
MOD 30ML
Multiloop
Controller 1800R
Model A
March 1996
Initial release
Model B
May 1997
CE LVD, EMI/RFI compliance
March 1996
Initial release
1.02
Sept 1996
2.00
April 97
Model C
April 97
2.01
June 97
Simplify factory calibration; fix display
script & format anomalies
Add Totalizer and Ramp/Soak block; Requires Application builder
2006S version 5.0 and PC-30
increase EX inputs; tunable PW
ICN interface version 9.0
tables; deviation in PAD
New flash EEPROM
No effect on form, fit, function or
compatibility
Fix anomaly: built-in AIN configured as Resistance causes shutdown
2.02
Oct 97
1.01
MOD 30ML
Firmware revision
1800P Identity
Module
Model A
MODCELL
Multiloop
2001N, 2002N Base Model B
Board
Model C
9 -2
January 1992
ICN CONTROLLER ONLY
CPU BOARD CURRENT
VERSION IS 5.1
Support for MODCELL foreground
size
ICN CONTROLLER BOARD
CURRENT VERSION IS 5.2
REQUIRED for MODCELL and
MOD30 ML
Used on 1731N,1732N, 1733N
and 1734N
Fix ICN anomalies (timeouts,
shutdowns etc.)
October 1991 BETA release hardware; limited
shipments
December 1991 Initial production hardware release
February 1995
Larger Power Supply in AC version
Requires Application builder
2006S version 4.0 and PC-30
ICN interface version 9.0
All BETA sites updated to Model
B
No change in DC version
MOD30ML and Modcell Maintenance Manual
HARDWARE, FIRMWARE AND SOFTWARE REVISION HISTORY
Table 9.1. Hardware and Firmware Revision History (Cont’d)
Instrument
MODCELL
Multiloop
2001P Logic
Identity Module
MODCELL
Multiloop
2002P Regulatory
Control
Identity Module
Rev
Date
Features
1.0
January 1992
Initial firmware release
2.0
June 1992
RTD Input support
3.0
March 1993
3.1
April 1994
4.0
July 1994
Supervisory, Notification, Expression
block
enhancements; Modbus slave
communications
Supports Modbus Master
communications
Supports download via Modbus
5.0
5.1
September
1995
January 1996
5.2
March 1996
Supports Sequence Blocks and CS31 Remote I/O
Corrects Potential Shutdown
Problems
ICN lockup problem removed
5.3
Jan 1997
Incorporate new I/O code
6.00
April 1997
Model C
April 97
Comments
REQUIRES V. 5.2 FIRMWARE
FOR ICN CONTROLLER
IN LINK AND MINI-LINKS
Requires version 6 ICN driver
1716S
Requires version 5 Configuration
software 1706S
Requires v.2 Application Builder
2006S and 2033N RS-232
or 2034N RS-485 (4-wire)
communication module
Requires Application Builder
software version 3.0
No effect on users or
compatibility
Add Totalizer and Ramp/Soak block; Requires Application builder
2006S version 5.0 and PC-30
increase EX inputs; tunable PW
ICN interface version 9.0
tables; deviation in PAD
New flash EEPROM
No effect on form, fit, function or
compatibility
Fix ICN anomalies (timeouts,
shutdowns etc.)
PID, RTD support
REQUIRES V. 5.2 FIRMWARE
FOR ICN CONTROLLER
IN LINK AND MINI-LINKS
6.01
October-97
1.0
June 1992
2.0
March 1993
Supervisory, Notification, Expression
block
enhancements; Modbus slave
communications
2.1
April 1994
3.0
July 1994
Supports Modbus Master
communications
Supports download via Modbus and
enhanced Modbus Master
communications
November 1995 Discontiniued.
Requires version 6 ICN driver
1716S
Requires 1706S Config. S/W
5.0 or 2006S Application
Builder version 1.5
Requires v.2 Application Builder
2006S and 2033N RS-232
or 2034N RS-485 (4-wire)
communication module
Functionality included in 2004AP
Adv. control Id. module
9 -3
MOD30ML and Modcell Maintenance Manual
HARDWARE, FIRMWARE AND SOFTWARE REVISION HISTORY
Table 9.1. Hardware and Firmware Revision History (Cont’d)
Instrument
MODCELL
Multiloop
2004P
Batch/Advanced
Control
Identity Module
MODCELL
Multiloop
2005P Sequence of
Events
Recorder Identity
Module
Rev
1.0
9 -4
Comments
Requires Application Builder
software version 2.0
NOT SUPPORTED in 1706S
Sequence blocks
Modbus download requires
2033N RS-232 or
Download via Modbus
2034N RS-485 (4-wire)
communications module
Name changed to Advanced Control. Requires Application Builder
software version 3.0 or higher
All Batch 1.0 functions plus CS-31
Requires PC-30 ICN interface
Remote
S/W version 8.0 or higher
I/O support (replaces Batch and
Regulatory
identity modules)
2.0
April 1995
2.1
January 1996
2.2
March 1996
Corrects Potential Shutdown
Problems
Fix problem with ICN lockup when used with older versions
2.3
Jan 1997
Incorporate new I/O code
3.00
April 1997
Model C
April 97
3.01
October-97
1.0
January 1992
2.0
January 1995
2.01
MODCELL
Multiloop
2033NZ RS-232
Module
Features
Batch control
All Logic 4.0 & Regulatory 3.0
functions plus:
Model C
MODCELL
Multiloop
2031NZ RS-232
Module
Date
July 1994
April 97
Ext Modbus Comm and Omega
Clock Support
New flash EEPROM
Model A
N/A
Fix ICN anomalies (timeouts,
shutdowns etc.)
Engineering development only
Model B
March 1993
Serial communications via Modbus
August 1994
DISCONTINUED
August 1994
Serial communications via Modbus;
Model A
October-97
No effect on users or
compatibility
Add Totalizer and Ramp/Soak block; Requires Application builder
2006S version 5.0 and PC-30
increase EX inputs; tunable PW
ICN interface version 9.0
tables; deviation in PAD
New flash EEPROM
No effect on form, fit, function or
compatibility
Fix ICN anomalies (timeouts,
shutdowns etc.)
Sequence of Events recording for up Requires PC-30 ICN driver
to
version 8.0
29 digital inputs
No effect on form, fit, function or
compatibility
Never released for sale/shipment
Master or Slave
Requires Logic v. 3 or
Regulatory v. 2 identity module
Replaced by 2033NZ RS-232
communications
Replaces 2031NZ in new
systems; support for download
via Modbus; isolated
Logic 4, Regulatory 3, Batch 1 &
above
Requires 2006S Application
Builder version 2.0 or higher
MOD30ML and Modcell Maintenance Manual
HARDWARE, FIRMWARE AND SOFTWARE REVISION HISTORY
Table 9.1. Hardware and Firmware Revision History (Cont’d)
Instrument
Rev
Features
Comments
March 1993
Special product for Systems
Integrated
Serial communications via Modbus
Never released for general
sale/shipment
Requires Logic v. 3 or
Regulatory v. 2 identity module
(Note: does not support
download via Modbus)
Also used for SOE Omega Clock
Signal
Requires 2006S Application
Builder version 2 or higher
Model C
August 1994
Added Isolation
Model A
MODCELL
Multiloop
2034NZ RS-485 (4wire) module
Model B
MODCELL
Multiloop
2020NZ Remote I/O
i/f module
August 1994
Serial communications via Modbus
Model A
MODCELL
Multiloop
2032NZ RS-485 (2- Model B
wire) module
Date
N/A
January 1996
Logic 4, Regulatory 3, Batch 1 &
above
Extended/Remote I/O Interface
module
Supports host communications &
download via Modbus; Isolated
Requires Application Builder
version 2.0 or higher
Requires Application Builder
version 3.0
Requires PC-30 ICN interface
S/W version 8.0
9 -5
MOD30ML and Modcell Maintenance Manual
HARDWARE, FIRMWARE AND SOFTWARE REVISION HISTORY
Table 9.2. Software Revision History
Packag
Instrument
Configurator
(1706S)
Rev
1.0
Date
May
1988
Added Features
Original release
Comments
Stand-alone package
Note: 1706S
software
does NOT support
Batch/Advanced 2.0
control
Identity for
MODCELL
Multiloop
Processors and
MOD 30ML
Controller.
2.1
2.2
2.3
2.4
3.0
1700J Recorder v.4,5,6,7
1700N Math Unit v.4
Sept
1988
Full support for SLU functions
Piecewise
4
1710R SLU v.5
As above, plus 1710R
SLU v.6
Linearization
Totalizer
Dec
1988
Sept
1989
May
1990
June
1991
Compatible with math
As above
coprocescor
Update recorder download
As above
software
Update SLU alarm block size
and add error checking for
event equations on event, drum,
channel selector
Recorder engineering units
As above, plus 1700N Math
V.5 Math Unit
Unit v.5
SLU - Full AI block configuration
(1-70)
Download lower version
databases to higher version SLU
Proper entry of ICN # in
supervisory message blocks
(SLU)
Invalid source pointer checks in
SLU loop block
Enhanced color for various CRT
screens
COMM ports 3 & 4 support
Same as above
19.2K baud support
Jan 1992 MODCELL 2000 support
Help menus
9 -6
Instruments Supported
1700R Controller v.4,5
June
1992
Subdirectory support
Can use PC-30 Workstation
protection key
MODCELL 2000 PID, RTD
support
Upload/download of LCP
databases
Fixed communication problems
with 486 PCs.
Same as above
MODCELL Logic Identity
v.1.0
Dual floppy support
discontinued
Hard disk required
MODCELL Logic ver. 1 and
2
MODCELL Regulatory ver.
1
LCP firmware ver. 4
LCP must be Model
C
MOD30ML and Modcell Maintenance Manual
HARDWARE, FIRMWARE AND SOFTWARE REVISION HISTORY
Table 9.2. Software Revision History (Cont’d)
Packag
Rev
5
Date
March
1993
Added Features
MODCELL Supervisory,
Notification, & enhanced
Expression blocks; MODBUS
communications
5.1
April
1993
June
1993
Works with App Bldr or PC-30
WorkStation copy protection key
Resolve minor bugs (refer to
Same as above
Rochester for more info)
5.2
5.4A March
1995
5.5
1997
Application
Builder
1.00
2006S
1.01
1.02
1.03
1.04
1.05
2.0
2.1
3.0
May
1993
Instruments Supported
MODCELL Logic ver. 3 &
below
MODCELL Regulatory ver.
1&2
All MOD 30 instruments,
LCP
Same as above
LCP Upload/download problems
fixed.
Company name ABB;
compatible w/ more PCs
Initial release
Logic 3.0, Regulatory 2.0
and
Comments
Most users
unaffected
and MOD 30ML
Controller
Applies to specific
database sizes
REQUIRES ICN
DRIVER V. 6 or
higher
below
No MOD 30 support
Aug
Maintenance release
As above
All users updated
1993
automatically, nocharge
Nov
Maintenance release
As above
Correct password
1993
protect problem;
some fields in
PID block did not
allow negative
values
Nov
Maintenance release
As above
PC Comm Port
1993
setup menu did not
appear in 1.02
Jan 1994 Maintenance release
As above
Remove debug
statement
Feb
Maintenance release
As above
Databases >32K did
1994
not compile properly
Aug
Support Sequence block, 1706S Logic v. 4.0, Regulatory
Required to support
1994
import, Modbus download
v.3.0
Batch identity
module
LCP database upload/download and Batch v. 1.0 and below 1706S no longer
included
Dec
Maintenance release
Logic v. 4.0, Regulatory
Correct import of
1994
v.3.0
Sequence blocks
from 1706S
and Batch v. 1.0 and below Fix inter-compound
connection on import
Retain occurrence
no's on compound
load
Sept
Support CS-31 Remote I/O,
Logic 5.0, Advanced Control Reads Sequence of
1995
faster compiler, Advanced
2.0
Events identity
queue
Control identity module
SOE 1.0 and below
Includes Extended
Modbus support
9 -7
MOD30ML and Modcell Maintenance Manual
HARDWARE, FIRMWARE AND SOFTWARE REVISION HISTORY
Table 9.2. Software Revision History (Cont’d)
Packag
Rev
4.0
Date
Feb
1996
4.01
Added Features
Support 1800R MOD 30ML
Multiloop controller
View Report & Status Display
print to LPT1
ML Upload / Import; includes
maintenance release
4.02
Feb
1997
5.00
April
1997
Support new TOT and RSK
blocks, enhanced EX, PW and
PAD blocks
5.01
May
1997
Maintenance release
5.02
June
1997
Maintenance release
1.0
ICN
Communications
May
1989
Original release
Driver (1716S)
Instruments Supported
As above and 1800R MOD
30ML
As above
Comments
As above
DESC block text
strings fixed, PID
init/restart modes
fixed
Logic 6.0, Advanced Control EX block inputs
3.0, MOD 30ML 2.0
expanded to 46;
tunable PW tables;
deviation in PAD
As above
Fix compounds,
change TIF file limits
that crashed GFW
As above
Change
ICOM/OCOM default
data type; EX block
upload (v1 or v2 to
v3)
1701R Controller XL v.1,2,3 Older version
instruments
supported through
1700J Recorder v.6,7
background
communications only
Note: Genesis
equivalents
are given in 2.0
April
SLU support
As above, plus
brackets.
1990
(3.23)
Faster communications
1710R SLU v.6
3.0
Jan 1991 Foreground communication with 1700R Controller v.4 & 5
REQUIRED for
"older" instruments
Networking
1701R Controller XL v.1,2,3
Re-initialization of off-scan
1700J Recorder v.4,5,6,7
instruments
1700N Math Unit v.4,5
1710R SLU v.5,6
3.1
April
1991
(3.27)
4.0
Mar
Name changed to ICN
MOD 30 as above
1991
Communications
(3.50)
Support for MODCELL 2000
MODCELL Logic ver. 1
Logic identity
5.0
July
Support for MODCELL PID, RTD MOD 30 as above
1992
MODCELL Logic ver. 1 and
2
MODCELL Regulatory ver.
1
5.1
July
Fixes an alarm problem
1992
(3.53)
9 -8
MOD30ML and Modcell Maintenance Manual
HARDWARE, FIRMWARE AND SOFTWARE REVISION HISTORY
Table 9.2. Software Revision History (Cont’d)
Packag
Rev
6.0
ICN
Communications
Driver (1716S)
Date
May
1993
(3.58)
Added Features
MODCELL Supervisory,
Notification, & enhanced
Instruments Supported
MOD 30 as above
Expression blocks
MODCELL Logic ver. 3 &
below
MODCELL Regulatory ver.
1&2
Same as above
(continued)
6.1
April
1993
6.2
June
1993
7.0
Aug
1994
Minor bug fixes (run strategies
from separate
directory, "time" data type in
SLU)
Fix open files
Same as above
Support for MODCELL Multiloop MOD 30 as above
Sequence Block
(3.60)
MODCELL Logic v.4
MODCELL Regulatory v.3
MODCELL Batch v.1
8.0
Jan 1995 Support for MODCELL
Same as above
Sequence of Events Identity
(3.62)
Support for CS-31 Remote I/O
MODCELL S.O.E and
Advanced Control identity
Note: Genesis
8.1
August Minor bug fixes - Mini link
Same as above
equivalents
1995
powerfail bit.
are given in (3.63)
brackets.
9.0
Mar
MOD 30ML Support
Same as above plus MOD
(3.64) 1996
30ML
Micro-Scan 500
and
Fulscope ER/C
Driver
(1717S)
1.0
July
1989
Supports SYS block
outs OFF, and fixes
database caching
bug
500R v.2 and above
1900J v.3 and above
2.0
Aug
1990
April
1994
Note: Genesis
3.0
equivalents
are given in (3.50)
brackets.
3.1
April
1994
April
1995
KTX Driver
(1740S)
Original release
Comments
REQUIRED FOR
APPLICATION
BUILDER
SUPPORT
(3.51)
1.0
July
1992
EMS compatibility
1900R v.1 and above
As above
Add totalizer functions for ER/C
1900J v.4
1900R v.3 and higher
XCOM support
As above
Required to support
totalizer and valve
deadband functions
Required for use
with PC-30 XCOM
option
Suppots up to 52 device blocks
Initial release
MX/PX/PXR instruments
with
communications
9 -9
MOD30ML and Modcell Maintenance Manual
HARDWARE, FIRMWARE AND SOFTWARE REVISION HISTORY
Table 9.2. Software Revision History (Cont’d)
Packag
4500 Analyzer
Driver
(1718S)
Micro-Scan 200
Driver
(1741S)
MODBUS Driver
Rev
1.0
Date
Feb
1992
Added Features
Initial release
Instruments Supported
4535,4545 pH/redox
1.0
Jan 1993 Initial release
4510,4520 conductivity
200R Series controllers
1.0
March
1993
Initial release
MODCELL Multiloop all
versions
2.0
Aug
1993
Supports IEEE floating point/long As above and MOD 30ML.
integer
3.0
April
1995
MP90 Driver
1742S
1.0
Extended
Modbus 1733S
for PC-30 and
GFW
EMP Driver
2010S
3.5
July
Initial release
1993
Oct 1995 Discontinued; Use MODBUS
Driver.
August Initial Release
1996
Comments
Recommend use at
4800 baud
Requires RS-232/RS
485 module
(1719S)
5.3
May
1996
for FIX DMACS
16-bit
EMP Driver
2011S
for FIX DMACS
32-bit
9 -10
Sept
1996
Uses MODBUS
protocol
MOD 30ML, MODCELL
MLP
DOES NOT
SUPPORT
STANDARD
MODBUS DEVICES
Supports MB1
Standard Modbus
and Extended
Modbus on
Supporting
Instruments
Supports MB1
Standard Modbus
and Extended
Modbus on
Supporting
Instruments
Extend Modbus Protocol Driver - MOD30 ML, MODCELL
16 bit
MLP and
Initial Release
6.0
ABB MasterPiece 90
Standard Modbus Devices
Extend Modbus Protocol Driver - MOD30 ML, MODCELL
32 bit
MLP and
Initial Release
Standard Modbus Devices
MOD30ML and Modcell Maintenance
APPENDIX 1
APPENDIX 1
A1.1
GENERAL
This section provides additional information such as cable pin outs and technical notes for
maintaining and troubleshooting MOD 30ML and Modcell instruments.
A1.2
CABLE PIN OUTS
The most commonly used cable for communication with MOD 30ML is the RS 232 cable with
Model number 109S1854. The pin outs for this cable are given below:
Wire
No.
1
2
3
A1.2.1
Color
RED
BLACK
BARE
WIRING CHART FOR CABLE 109S1854
Pin no. on the 9
Function
To the connector on
pin connector side
the MOD 30ML side
2
Rx (from PC)
TIP
3
Tx (from PC)
RING
5
Common
SLEEVE
Function
Tx
Rx
Common
Cables for 1720N Communication Link:
Pin outs for the 1774F RS-232 cable for connecting PC to 1720 Communication Link is given
below:
Color
BLACK
BLACK
RED
GREEN
WHITE
Pin no. (9 pin connector on the PC
side)
2 Rx
3 Tx
5 Common
7 RTS
8 CTS
1 GND
Pin no. (25 pin connector on the
Comm. Link side)
2 Tx
3 Rx
7 Common
5 CTS
4 RTS
Shield
Pin outs for the 1753F RS-232 cable for connecting PC to 1720 Communication Link is given
below:
Color
BLACK
BLACK
BLACK
GREEN
WHITE
RED
Pin no. (25 pin connector on the PC
side)
1 GND
2 Tx
3 Rx
4 RTS
5 CTS
7 Common
Pin no. (25 pin connector on the
Comm. Link side)
1 GND
3 Rx
2 Tx
5 CTS
4 RTS
7 Common
A1 -1
MOD30ML and Modcell Maintenance
APPENDIX 1
A1.2.2
Cables for Mini Link External
Pin outs for the RS-232 cable for connecting PC to 1733N Mini Link External is given below:
25 Pin port DB25f
1
2
3
7
6
20
PC side
9 Pin port
- DB9f
Shell
3
2
5
6
4
Function
Function
Ground
Tx Data
Rx Data
Common
DSR
DTR
Ground
Rx Data
Tx Data
Common
RTS
CTS
+5 Vdc
Mini Link External Side
9 Pin port25 Pin port –
DB9m
DB 25m
1
1
2
2
3
3
5
7
7
4
8
5
9
Notes:
1. DSR-RTS and DTR-CTS connections are not required if Jumpers W16 and W17 are
removed.
2. The +5Vdc connection is for test purposes only.
3. The Ground connections are optional.
4. The cable shield may be connected to ground at either end, but not both
A1 -2
MOD30ML and Modcell Maintenance
APPENDIX 2
APPENDIX 2
A2.1
Technical Notes
This section has technical notes on known issues and problems. Contact MicroMod
Automation, Inc at 585 321 9200 or visit http://www.MicroModAutomation.com and select
Technical Support page for the latest list of tech notes.
A2 -1
MOD30ML and Modcell Maintenance
APPENDIX 2
A2 -2
Analog Output Readback Error
Diagnostic
MOD 30ML and Modcell have
Analog Output Module Error
Problem Description:
Instrument display or status display in ViZapp or Application Builder Software show “Module Error” for
AOM and extended error report shows a Readback Error
Applies to:
MOD 30ML configured from front face or Application Builder software or Visual Application Designer
ViZapp Software. It also applies to the Modcell Multiloop Processor.
Explanation:
This diagnostic can be triggered by a number of different problems, some of which are external to the
module. To determine if the error is due to a module failure, the extended error information must be read.
The extended error report can be read from the Status Page with the command R AOMn,EXTERR,
replacing "n" with the occurrence number of the module. Extended error information must be read after
receiving the module error, and before it has been acknowledged. Reading this information under any
other conditions will return a meaningless report.
Solution:
If the extended error report shows a Readback Error, the output circuit should be tested for noise
feedback from the field device. If the signal is clean, it may be a random occurrence, which can be
ignored.
We have conducted testing on modules manufactured over the last few years, and have found that a
percentage show occasional readback errors. The frequency of the error was random, but it always
cleared on the next scan (150mSec).
Topic: MOD 30ML/Modcell
MicroMod Automation, Inc.
AOM Readback.doc
Technote: TNML1001-2
Rev. 08-July-2003
Page 1 of 2
Technical Notice
On examining the problem in detail it was determined that this is an invalid diagnostic and does not affect
the output signal to the field.
After reviewing the design schematics with one of the development
engineers, it was determined that there may have been a change in a vendors' component tolerance
used inside the modules, causing the readback diagnostic error. It is believed to be a timing issue.
It is not uncommon for a vendor to change a component's speed, timing or tolerance without notifying
their customers. This has been encountered before on other products.
Because this does not cause any change in the field output and clears on the next scan cycle, the
recommended course of action is to disable the diagnostic. This diagnostic has been observed and
monitored on processes including industrial boiler controls and there has been no effect on the process.
To disable this particular diagnostic, set AOMn.AOMERRS to 1 (n = analog output module occurrence
number). In ViZapp, this error can be suppressed by checking the Module error box on the Diagnostics
tab of the AOM block. If, for a particular application, you wish to ensure there is not really a readback
problem on the output, the readback signal can be compared to the calculated output, with a small time
delay. The result of this comparison can be forwarded to a PA or PAD block.
Topic: MOD 30ML/Modcell
MicroMod Automation, Inc.
AOM Readback.doc
Technote: TNML1001-2
Rev. 08-July-2003
Page 2 of 2
Temperature values are not
accurate with B type T/C if CJC
is used in MOD 30ML/Modcell
MOD 30ML and Modcell have
Analog Output Module Error
Problem Description:
The configuration involves a Thermocouple input on the MOD 30ML/Modcell. The controller is configured
with a TIM module/ AIN block configured as T/C and TI block with CJC. The TIM/AIN block is configured
as a B type thermocouple. The compensation works properly at some temperatures, but not at others.
This problem is seen only with the B type thermocouple configuration. The type of CJC selected (internal,
built-in or modular) does not have any effect on this.
Applies to:
MOD 30ML/Modcell configured from Application Builder software or Visual Application Designer ViZapp
Software. This also applies to MOD 30ML configured from front face.
Explanation:
It appears that the compensation for a Type B thermocouple is not working, due to an incomplete table in
the instrument's firmware. The table that converts from millivolts to degrees and the reverse, has values
for the range of 200 to 1820 degrees C. This range may be fine for converting a process signal from
millivolts to degrees C.
The problem appears when the instrument tries to inverse calculate a millivolt value from room
temperature for compensation. There are no table values to support this low value, and an invalid value is
produced.
With a constant temperature at the terminal block, the number of degrees of compensation varies,
depending on where the process temperature is on thermocouple's curve. It is not simply a matter of
adding the reference temperature to the calculated thermocouple temperature.
It is noted that even though the range of a Type B thermocouple is 0 to 1700 degrees C, its useful range
begins above 800 degrees C.
Because its linearization curve is nearly flat below this point, there are no accuracy specifications below
that point.
Topic: MOD 30ML/Modcell
MicroMod Automation, Inc.
B Type TC Problem.Doc
Technote: TNML0501-1
Rev. May-2001
Page 1 of 6
Technical Notice
Dynamic Compensation: Since this Type of thermocouple has a curve that produces almost no signal a
room temperature, dynamic compensation really is not necessary. The millivolt value in a Type B curve
that corresponds to 23 degrees C is -0.003 mV. At normal operating temperatures (above 800 degrees
C), this relates to about 1/3 of a degree offset. Adding a fixed compensation value is all that is necessary
for this type of thermocouple.
Using dynamic compensation may not help since the Type B tables indicate that the mV signal will
fluctuate between 0.000 and -0.003 for any temperature under 45 degrees C.
Solution:
The solution to this problem is to perform the linearization manually with other blocks. We will use an EX
(expression) block and a LN (linearization) block to this. This is explained below with configuration in
ViZapp. If you use Application Builder, you can still follow the steps below. If you configured the controller
from the front face, consider configuring it from the ViZapp or Application Builder software as the fix
involves EX and LN blocks. The solution is different for Built-in inputs and Module inputs. Both types are
discusseed below. The following 3 schemes are discussed in this Technote:
1. Built-In input 1 in MOD 30ML configured as B type thermocouple
2. Built-In input 2 in MOD 30ML configured as B type thermocouple
3. Thermocouple module 2013A configured as B type thermocouple in MOD 30ML or Modcell
Note: The Default Gallary in VIZapp includes these schemes as compounds. You can also simply
load the compound and use it.
Built-In Input 1 configured as B type T/C:
1. This scheme requires an AIN block, EX blocks and a LN block in your control strategy as shown in
the next figure
2. Configure the AIN block for B type thermocouple and the desired Temperature scale.
3. Configure the first EX block’s (mV2uVBI1) General tab as shown in the figure below: (Tag names and
descriptions are optional).
Topic: MOD 30ML/Modcell
MicroMod Automation, Inc.
B Type TC Problem.Doc
Technote: TNML0501-1
Rev. May-2001
Page 2 of 6
Technical Notice
4. Add 3 inputs: RawData (Floating point), CJConst (Floating point with internal data value of –0.003)
and Dampfact (Floating point with internal data value of 25) in the Inputs tab of this EX block as
shown in the next figure:
5. Configure the Expression tab of this EX block by typing the expression:
Topic: MOD 30ML/Modcell
MicroMod Automation, Inc.
B Type TC Problem.Doc
Technote: TNML0501-1
Rev. May-2001
Page 3 of 6
Technical Notice
R + (((RawData + CJCconst) * 1000)-R)/DampFact
6. Click on OK.
7. Configure the LIN block with the Linearization type as Thermocouple Type B as shown in the next
figure: Choose the appropriate Temperature scale:
8. Click on OK and connect the blocks as below: (Refer to the figure on the second page).
Topic: MOD 30ML/Modcell
MicroMod Automation, Inc.
B Type TC Problem.Doc
Technote: TNML0501-1
Rev. May-2001
Page 4 of 6
Technical Notice
Connect R form the TIM block to the input RawData of the EX block.
Connect the R of the EX block to the INPUT of the LN block.
9. Optional: Add another EX block (tag name: CJTemp in the figure) to display the value of the
temperature at the terminals. This EX block will have inputs CJC (Floating point) and DampFact
(Floating point with internal data value of 2.0). The Expression for this EX block will be:
R + (CJC-R)/DampFact
The Result type is default (Floating point) for this EX block. Connect the CJC attribute from the TIM
block to the CJC input of this EX block as shown on the figure on the second page. This EX block’s
result can be connected to a display block to display the value of the temperature at the terminals. As
mentioned, this EX block is optional only and does not partcipate in the temperature calculation for
the B type T/C.
10. Compile your database.
Built-In Input 2 configured as B type T/C:
1. This scheme requires an AIN block, EX block and a LN block in your control strategy as shown in the
next figure:
2. The AIN block is configured as input number 2 and type as Thermocouple Type B.
3. Configure the desired Temperature scale.
4. Configure the EX block’s (mV2uVBI2). Add 3 inputs: RawData (Floating point), CJConst (Floating
point with internal data value of –0.003) and Dampfact (Floating point with internal data value of 25)
in the Inputs tab of this EX block.
5. Configure the Expression tab of this EX block by typing the expression:
R + (((RawData + CJCconst) * 1000)-R)/DampFact
6. Click on OK.
7. Configure the LIN block with the Linearization type as Thermocouple Type B. Choose the
appropriate Temperature scale.
Topic: MOD 30ML/Modcell
MicroMod Automation, Inc.
B Type TC Problem.Doc
Technote: TNML0501-1
Rev. May-2001
Page 5 of 6
Technical Notice
8. Click on OK and connect the blocks as below: (Refer to the figure above). Connect R form the TIM
block to the input RawData of the EX block. Connect the R of the EX block to the INPUT of the LN
block.
9. Compile the database.
TIM module block configured as B type T/C:
1. This scheme requires a TIM block, EX block and a LN block in your control strategy as shown in
the next figure:
2. The TIM block is configured as Thermocouple Type B.
3. Configure the desired Temperature scale.
4. Configure the EX block’s (mV2uVMOD). Add 3 inputs: RawData (Floating point), CJConst (Floating
point with internal data value of –3.0) and Dampfact (Floating point with internal data value of 25) in
the Inputs tab of this EX block.
10. Configure the Expression tab of this EX block by typing the expression:
R + ((4.0 * RawData + CJCconst) - R)/DampFact
11. Click on OK.
12. Configure the LIN block with the Linearization type as Thermocouple Type B. Choose the
appropriate Temperature scale.
13. Click on OK and connect the blocks as below: (Refer to the figure above). Connect R form the TIM
block to the input RawData of the EX block. Connect the R of the EX block to the INPUT of the LN
block.
14. Compile the database.
Topic: MOD 30ML/Modcell
MicroMod Automation, Inc.
B Type TC Problem.Doc
Technote: TNML0501-1
Rev. May-2001
Page 6 of 6
Faceplate Communication Error
and no keyboard respose in
MOD 30ML
Diagnostic Error codes DIF 4
and 5 are reported. Instrument
locks up with a shutdown fault.
Problem Description:
This problem starts with diagnostic errors DIF 4 and 5. The keyboard might get locked up. The instrument
eventually goes into a shutdown.
Applies to:
MOD 30ML configured from front face or Application Builder software or Visual Application Designer
ViZapp Software.
Explanation:
This problem may be due to noise or static discharges on the analog inputs. The built-in analog inputs
use the same communication channel on the processor as the display, which explains the faceplate
communication errors.
Solution:
Check whether the analog inputs are currently floating. To reduce electrical noise and eliminate static
build-up, we recommend grounding these inputs.
The configuration default for a faceplate communication error is to force a shutdown. This default can be
changed, so that the controller will continue to operate, as long as there are no other critical errors. The
faceplate communication error would still be reported, allowing you to determine whether the added
grounding corrected the problem. This is done in the DIF (Display Interface block) block’s configuration
as shown in the next figure:
Topic: MOD 30ML/Modcell
MicroMod Automation, Inc.
Faceplate Error.doc
Technote: TNML0801-2
Rev. August-2001
Page 1 of 2
Technical Notice
Check the grounds on all the inputs and make sure they are properly grounded.
Reference:
Also read the Technote on Grounding.
Topic: MOD 30ML/Modcell
MicroMod Automation, Inc.
Faceplate Error.doc
Technote: TNML0801-2
Rev. August-2001
Page 2 of 2
Grounding and Wiring
Guidelines for MOD 30ML
To avoid associated diagnostic
errors and shutdowns
Symptoms:
Faceplate communication error, faceplate FAILURE error, analog input diagnostic errors, instrument
shutdowns occurring on a regular or intermittent basis.
Applies to:
MOD 30ML
Explanation:
The MOD 30ML controllers require good signal and power grounding for proper operation. A very large
percentage of the field problems reported are due to poor grounding and wiring practices. This is
especially true when the MOD 30ML is installed as an upgrade to pneumatic instrumentation, where no
grounding was required, or to the old MOD 30 series instrumentation, which had different grounding
requirements than current technology.
Improper grounding can cause noise or static discharges on the analog inputs and power lines. This can
show up as faceplate communication failures, analog input failures, and instrument shutdown errors.
Solution:
It is important to check all signal and power grounding and wiring, following the recommendations
provided below.
Power Safety / Protective Ground
•
The green ground lug on the MOD30ML is where the power safety or protective ground is to be
connected.
•
No other connections are to be made to this lug.
Topic: MOD 30ML/Modcell
MicroMod Automation, Inc.
GroundingWiring.doc
Technote: TNML1001-1
Rev. 3, Feb-2005
Page 1 of 4
Technical Notice
•
If the installation includes an AC power neutral, test for voltage between it and this ground. If there is
more than 2 volts, it is quite likely that there is a defective ground or neutral connection.
Shields
•
Usually, shield wires are connected to ground only at one end.
•
In noisy environments, it may be necessary to connect the shield to ground at both ends. In this
case, it is imperative that a high quality ground is available at both ends, to prevent ground loop
currents.
•
All shield grounding is to be made on the Chassis terminals. There are two of these terminals, one
above terminal 49 and one below L2/N. They connect directly to the instrument housing, as does the
ground lug.
Instrument, I/O and Communication Circuit Commons
•
The instrument circuit common, built-in analog inputs, modular analog I/O and communication circuit
commons are isolated from the protective ground. This makes it easier to avoid dc ground loops, and
helps isolate the instrument from noise, which may be present on the protective ground.
•
If the installation does not include a dedicated instrument system ground, then connect circuit
commons to one of the terminals identified as Chassis.
•
Never leave circuit commons completely floating.
•
Circuit commons must always have some dc path to ground to prevent the possible build up of static
charges, to reduce noise pickup, and to comply with EU EMC requirements.
•
If a separate instrument ground is available, connect commons to it, instead of the power or safety
ground.
•
Instrument circuit common (terminal 25) and the negative or return of all isolated analog signal inputs
and outputs are to be connected to ground. Note that the built-in analog outputs are not isolated and
require no additional grounding, when the instrument common is tied to ground.
•
When using the built-in communications, connect terminal 1 of each instrument on the bus together.
This circuit common must also be connected to ground at one point.
•
The common of ICN and RS-232 modules is to be connected in the same manner as the built-in
communications.
•
RS-485 modules provide no connection to circuit common and usually do not require grounding. For
installations where high levels of noise or static charges are present, it may be necessary to ground
the circuit. If the circuit is grounded at the PC interface or another device, adding a ground could
cause adverse affects. If the communication circuit is not grounded elsewhere, it may be grounded at
the terminations. To ground at the terminations, it is necessary to use two 60 ohm resistors in series,
instead of one 120 ohm resistor. The junction between the two resistors may then be connected to
ground.
Topic: MOD 30ML/Modcell
MicroMod Automation, Inc.
GroundingWiring.doc
Technote: TNML1001-1
Rev. 3, Feb-2005
Page 2 of 4
Technical Notice
Wiring
•
When using a dedicated instrument ground, the resistance to ground should be less than 1 ohm.
Use stranded wire for best noise immunity, of sufficient gauge to keep the resistance low. For
example, at least 18 AWG (1.02 mm) wire would be required for a distance of 150 feet, or 10 AWG
(2.6 mm) for 1000 feet.
•
Since instrument common terminals 25, 16 and 41 are all internally tied together, 16 and 41 will also
be tied to ground when terminal 25 is connected to ground.
•
If necessary, use a “pigtail” wire from the terminal and splice it to multiple common or shield wires.
•
Spliced wires should be twisted before applying a crimp connector.
•
All ground wires should be kept as short as possible.
•
DO NOT use the wire’s shield for a signal or common.
•
Analog input signal wiring must be at least 22 AWG (0.65 mm), though larger is perferred.
•
Wire Recommendations:
Stranded shielded twisted pair wire should be used for all signal and communication wiring. The wire
should have a minimum of a 2-inch lay (6 twists per foot). It is best for each pair to have its own
shield. If using multiple pairs that share a shield, do not mix high and low voltage signals within the
same shield.
•
I/O Signals
•
•
Remote I/O Communications
•
•
•
Up to 1600 ft (500 m)
24 AWG (0.51 mm) overall foil shield and drain wire
(Beldon 9841 or equiv.)
ICN Communications
•
Up to 500 ft (150 m)
18 AWG (1.02 mm)
•
500-1500 ft (150-460 m)
18 AWG (1.02 mm), 18-25 pf/ft (60-83 pf/m)
•
1500-2000 ft (460-610 m)
22 AWG (0.64 mm)
RS-232 Communications
•
•
At least 22 AWG (0.65 mm), though larger is perferred
Up to 50 ft (15 m)
virtually any standard shielded twisted pair with drain
(Beldon 9502 or equivalent)
RS-422 and RS-485
•
Up to 20 ft (6 m)
virtually any standard shielded twisted pair with drain
•
20-1000 ft (6-305 m)
24 AWG (0.51 mm) overall foil shield and drain wire
(Beldon 9841 for 2-wire and 9502 for 4-wire, or equiv.)
•
1000-4000 ft (305-1220 m) 24 AWG (0.51 mm) overall foil shield and drain wire on each pair
(Beldon 9841 for 2-wire and 9729 for 4-wire, or equiv.)
Topic: MOD 30ML/Modcell
MicroMod Automation, Inc.
GroundingWiring.doc
Technote: TNML1001-1
Rev. 3, Feb-2005
Page 3 of 4
Technical Notice
I/O Grounding
•
The built-in analog outputs are internally tied to circuit common, and require no external grounding.
•
The built-in analog inputs, and all modular analog I/O, are isolated and should be externally
grounded.
Reference:
TechNote
TNML0801-2
Faceplate Communication Errors
Instruction
IB-MODBUS-RTU
Modbus RTU Communications Guide
Instruction
IB-1800R-INS
MOD30ML Installation Guide
Instruction
IB-23C601
Remote I/O Module Installation Guide
Support Web Site
Topic: MOD 30ML/Modcell
MicroMod Automation, Inc.
GroundingWiring.doc
http://www.micromodautomation.com
Technote: TNML1001-1
Rev. 3, Feb-2005
Page 4 of 4
Instrument Overconfigured
Diagnostic alarm in MOD
30ML/Modcell
Problem Description:
The overconfigured diagnostic indicates that it is taking longer than the configured time to execute the
database. This usually is not a problem, if it occurs occasionally. If the diagnostic is continuously active,
the database should be revised to correct the error.
Applies to:
MOD 30ML and MODCELL Multiloop Processor
Solution:
There are nine scan intervals, 1 through 5 are for user configured functions, 6 is for the Interface Block itself,
and 7 through 9 are for communication channels. Scan intervals 1 through 5 can be configured in increments
of 50mS. Scan interval 6, which is fixed at 50mS, is for managing instrument states, diagnostics, events and
I/O. Scan intervals 7 and 8 are for managing the communications ports one and two. Scan interval 9 is for
communications port 3 on Modcell MultiLoop Processor, or the display and built-in I/O on the MOD 30ML.
Scan intervals 7 through 9 are fixed at 50mS for installed ports and set to zero for unused ports.
To accurately determine the scan times, the instrument must be configured, in the RUN state, and with valid
I/O connected. Using the Application Builder status screen, issue the command CLR_MT to reset all MTIME
values to zero. If these attributes are not zeroed after startup, they may represent a startup “surge” in some
cases. After waiting a few minutes, or longer if required for supervisory messages or event-triggered
operations to be executed, issue the command R XTIMES and record the MTIME values. From these
readings, it can be determined to what degree the instrument is overconfigured. It is easiest to base the
calculations on the shortest scan interval, which is 50mS.
Topic: MOD 30ML/Modcell
MicroMod Automation, Inc.
Overconfig.doc
Technote: TNML0302-2
Rev. 2, Mar-2002
Page 1 of 2
Technical Notice
Below is a sample calculation for an overconfigured instrument. The interval ratio is a factor used to
normalize each scan group to a time slice of a 50mS unit.
Scan
Group
Scan
Interval
MTIME
1
2
3
4
5
6
7
8
9
300
350
400
450
500
50
50
50
50
314
324
295
310
404
24
13
0
0
Interval
Ratio
x 50/300
x 50/350
x 50/400
x 50/450
x 50/500
x 50/50
x 50/50
x 50/0
x 50/0
Total
Time/50mS
=
=
=
=
=
=
=
=
=
=
52.3
46.3
36.9
34.4
40.4
24.0
13.0
0.0
0.0
247.3
The calculations above show that the configuration is asking for over 247mS of processing to be done every
50mS. Notice that only group 1 is overconfigured, but even if its MTIME value was zero, the instrument would
still be overconfigured.
To eliminate the overconfigured diagnostic, there are three directions that can be taken.
1. Increase one or more of the group scan interval times
2. Optimize the configuration for more efficient operation
3. Remove some of the functions from the database
The easiest solution would be to increase the scan interval times, assuming that acceptable updates could still
be performed. The best solution may be to implement a combination of all three actions.
Topic: MOD 30ML/Modcell
MicroMod Automation, Inc.
Overconfig.doc
Technote: TNML0302-2
Rev. 2, Mar-2002
Page 2 of 2
Communication Cables Pin-Outs
Cables for Minilink, Comm link and MOD 30ML
Problem Description:
This tech-note covers the pin-outs for the communication cables used with the MOD 30, MOD 30ML and
Modcell equipment.
Applies to:
MOD 30, MOD 30ML, Modcell, Comm link (1720N), Mini-link Ext (1733N) and personal computer.
Explanation:
Following is a table that summarizes the cables:
Cable Model Number
Connecting eqipment
Communication Satndard
109S1854
MOD 30ML Built-in RS-232 port in the
RS-232
front on the controller to PC
1774F
Comm link (1720N) and PC’s 9 pin serial
RS-232
port
1753F
Comm link (1720N) and PC’s 25 pin serial
RS-232
port
Generic
Mini link – Ext (1733N) 9 pin port and
RS-232
PC’s 9 pin serial port
Generic
Mini link – Ext (1733N) 9 pin port and
RS-232
PC’s 25 pin serial port
Generic
Mini link – Ext (1733N) 25 pin port and
RS-232
PC’s 25 pin serial port
Generic
Mini link – Ext (1733N) 25 pin port and
RS-232
PC’s 9 pin serial port
Topic: MOD 30ML/Modcell
MicroMod Automation, Inc.
Comm Cables.doc
Technote: TNML0702-1
Rev. July-2002
Page 1 of 4
Technical Notice
The most commonly used cable for communication with MOD 30ML is the RS 232 cable with Model
number 109S1854. The pin outs for this cable are given below:
WIRING CHART FOR CABLE 109S1854
Wire No.
Color
Pin no. on the 9
pin connector
side
Function
To the connector
on the MOD 30ML
side
Function
1
RED
2
Rx (from
PC)
TIP
Tx
2
BLACK
3
Tx (from
PC)
RING
Rx
3
BARE
5
Common
SLEEVE
Common
Cables for 1720 Communication Link:
Pin outs for the 1774F RS-232 cable for connecting PC to 1720 Communication Link is given below:
Color
Pin no. (9 pin connector on the PC
side)
Pin no. (25 pin connector on the
Comm. Link side)
BLACK
2 Rx
2 Tx
BLACK
3 Tx
3 Rx
RED
5 Common
7 Common
GREEN
7 RTS
5 CTS
WHITE
8 CTS
4 RTS
1 GND
Shield
Topic: MOD 30ML/Modcell
MicroMod Automation, Inc.
Comm Cables.doc
Technote: TNML0702-1
Rev. July-2002
Page 2 of 4
Technical Notice
Pin outs for the 1753F RS-232 cable for connecting PC to 1720 Communication Link is given below:
Color
Pin no. (25 pin connector on the PC
side)
Pin no. (25 pin connector on the
Comm. Link side)
BLACK
1 GND
1 GND
BLACK
2 Tx
3 Rx
BLACK
3 Rx
2 Tx
GREEN
4 RTS
5 CTS
WHITE
5 CTS
4 RTS
RED
7 Common
7 Common
Cables for Mini Link External
Pin outs for the RS-232 cable for connecting PC to 1733N Mini Link External is given below:
PC side
Mini Link External Side
25 Pin port DB25f
9 Pin port
- DB9f
Function
Function
9 Pin port- DB9m
25 Pin port
–
DB 25m
1
Shell
Ground
Ground
1
1
2
3
Tx Data
Rx Data
2
2
3
2
Rx Data
Tx Data
3
3
7
5
Common
Common
5
7
6
6
DSR
RTS
7
4
20
4
DTR
CTS
8
5
+5 Vdc
9
Notes:
1.
DSR-RTS and DTR-CTS connections are not required if Jumpers W16 and W17 are removed.
2. The +5Vdc connection is for test purposes only.
3. The Ground connections are optional.
4. The cable shield may be connected to ground at either end, but not both.
For the latest list of technotes, visit http://www.micromodautomation.com or contact us at 585 321
9200
Topic: MOD 30ML/Modcell
MicroMod Automation, Inc.
Comm Cables.doc
Technote: TNML0702-1
Rev. July-2002
Page 3 of 4
Technical Notice
Topic: MOD 30ML/Modcell
MicroMod Automation, Inc.
Comm Cables.doc
Technote: TNML0702-1
Rev. July-2002
Page 4 of 4
The Company’s policy is one of continuous product improvement and the right
is reserved to modify the information contained herein without notice, or to
make engineering refinements that may not be reflected in this bulletin.
Micromod Automation assumes no responsibility for errors that may appear in
this manual.
© 2004 MicroMod Automation, Inc.
Printed in USA
IB-23M601, Issue 3 2/2005
MicroMod Automation, Inc.
140 Mushroom Blvd
Rochester, NY USA 14623
Tel. 585-292-6050
Fax 585-273-6969
www.micromodautomation.com