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

MOD30ML and Modcell Maintenance Manual
COMMUNICATIONS
Message Probable Cause Action
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 Buil-
tin Analog Input block; AIN is
correct)
e.g., ACK AIN9 5
(9 is an invalid occurrence
number for a Built-in Analog Input
block) Correct entry and try again.
Message Probable Cause
Action
Invalid constant
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. Enter a valid data constant.
2. Obtain a valid database.
Invalid database header
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. Try upload operation again.
2. Be sure the .ID1 file contains a
valid instrument database,
then try import operation
again.
Invalid diagnostic code
Specified diagnostic number is
invalid.
e.g., ACK AIN1 A
(Letter A is not valid, code must
be a number) Correct entry and try again. Refer
to Section 7 for a list of code
numbers.
Invalid entry
A command or part of a
command
is not understood.
e.g., W TIM 2:04:00.0
(TIME is misspelled TIM.) Correct entry and try again.
Invalid hexadecimal number
Specified hex number is invalid.
e.g., W EX1,I3 $G H
(G is not a valid hex digit) Correct entry and try again.
Invalid message function code
Momentary fault in Modbus
communication. Try again.
Invalid mode
The write message is not
accepted because of the state of
the mode attribute. Change the mode attribute to the
appropriate state.
Invalid occurrence number
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) 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