beautypg.com

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

Page 63

background image

MOD30ML and Modcell Maintenance Manual

COMMUNICATIONS

Message

Probable Cause

Action

Deferred response overrun,
parity or framing error

1. Momentary

communication

fault.

2. Parity mismatch between

instrument and
Communications Link.

1. Try

again.

2. Check that parity configured in

Serial Port Setup menu, Figure
4, matches setting of parity
status switch in link.

Device: device name not found
in Server.

Same cause as GetAddress
message in this table

See the action for the GetAddress
message in this table.

Do you wish to retain block
occurrence numbers in the
compound being loaded?

This message appears whenever
a compound is loaded.

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.

Download completed without
error

Information only

None

Downloading

Information only

None

Ending, changing instrument
state

Information only (3-10second
duration)

None

Error opening COMx (where x
is the Com port number)

The instrument is not connected
to the specified Communication
port.

Another device such as a PDA or
camera is connected to that
communication port.

A third party software such as PC
Synchronization for PDA or
Software for connecting other
devices is holding the port

Check/Change the Communication
port number and try again.


Remove the device and try again.



Disable the software so that it
releases the communication port
and then try again.

Error reading .ID1 file


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.

Error reading .ID1 or .ID2 file

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.

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.

4 -14