Micromod MOD: 30ML and Modcell Maintenance for 2001N, 2002N, and 1800R User Manual
Page 70

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, non-
zero occurrence numbers. Valid
occurrence numbers, once
assigned, are not reassigned in
subsequent compiles. It is
important that occurrence
numbers not be reassigned
because other systems, such as
the LCP or PC-30, reference
blocks by block type and
occurrence number. If these
numbers are allowed to change,
these systems would no longer
reference the correct blocks.
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
Same as above
Same as above
SendPacket: Unspecified Error
Or
SendPacket: device name
Unspecified Error
1. Specified ICN or Modbus
address is not correct.
2. Instrument is not connected
to network.
3. Momentary
communications
fault.
4. Parity mismatch between
instrument and Device
Properties in OPC Server.
1. Enter correct address on
Communications Setup menu
(See Section 3.3.4 or 3.3.5).
2. Check network connections.
3. Try
again.
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.
Starting, changing instrument
state
Information only (3-10 second
duration).
None
STX not found at start of
returned message
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