Micromod MOD: 30ML and Modcell Maintenance for 2001N, 2002N, and 1800R - Manual (Page 65)

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. Verify that instrument at the
specified address is a MODCELL
or MOD 30ML.
Instrument reports an error
reading that attribute
1. Block containing the attribute
is not configured.
2. Attribute does not exist in the
specified block.
1. Configure the required block.
2. Check block configuration.
Instrument state in transition Information only. An instrument
state transition is in process. None
Instrument version too low to
run data base
Database being downloaded
contains functions not supported
by the instrument.
Replace instrument identity
module with a version which
accepts the database, or modify
the configuration to run on the
existing instrument version.
Interpreting database Information only None
Invalid ACK Diagnostic acknowledgement
specifies nonexistent block
occurrence number, or inactive
diagnostic number. Retype command using correct
number (See Section 3.4.3)
Invalid ASCII string Specified ASCII data is invalid.
e.g., W IF1,USRTAG 1 (ASCII
data expected; 1 specified) Correct entry and try again.
Invalid attribute
An invalid attribute name was
specified. e.g. ,R IF1. COMMAND
(Command is not a valid attribute
for the IF block attribute.) Check the database reference
book for list of valid attributes
(See Section 1.5).
Invalid block checksums
Followed by:
Possibly invalid database. Do
you wish to continue?
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.
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.
Invalid block type
An invalid block type was
specified. e.g., W IFF1,CMD 1
(IF block is misspelled IFF) Correct entry and try again.
4 -16