E - upload/download error messages, Upload/download error messages, Appendix – Rockwell Automation 2706-MB1 MESSAGEVIEW 421 SOFTWARE MANUAL User Manual

Page 296

Advertising
background image

Appendix

E

Publication 2706-817

Upload/Download Error

Messages

This appendix lists error messages that may appear during a
download or upload operation. Messages are listed alphabetically.

For messages that may appear during creation or editing of an
application, see Appendix C.
For messages that may appear during validation, see Appendix D.
For messages that may appear during a tag import or export, see
Page 8–22.

Error Message

Meaning

What to do

Address overlaps Block Transfer Control Byte.

A tag is assigned the same address as the
Block Transfer Control Byte, the lowest
accessible byte in the discrete I/O rack.

Enter a different address for the tag in the Tag
Editor. Or if BTs are not used, disable block
transfers in the Block Transfer dialog.

Application (Data) file CRC is incorrect.

The computed CRC of the MVA file does not
match the CRC stored in the program.

The file is corrupted. Specify a valid MVA file.

Application file length does not match file
header record.

The MVA file has a different file length
recorded than the length of the file.
This typically occurs when a file is being
downloaded which was truncated by an
aborted upload.

Specify a valid MVA file.

Application matches file in terminal, no
download is necessary.

The CRC of the MVA file is identical to the
CRC or the application in the terminal.

No action is necessary.

Application type does not match terminal type.
Re-configure in Terminal Setup.

The application is configured for a
communication protocol that does not match
the terminal port.

From the Setup tab in Terminal Setup, select
a terminal type that matches the application.
Or convert the application to match the
terminal type, then update the tags
appropriately.

Block Transfer Channel Number: [Num] –
Length is invalid.

The block transfer length is defined as 0 or
exceeds the maximum of 64.

In the Block Transfer dialog, correct the
invalid length of a block transfer.

Cannot continue, terminal is BUSY.
– – – – – – – – OR – – – – – – – –
Cannot continue, terminal is not in RUN
mode.

The terminal is in a mode that will not support
file transfers.

Wait until the terminal is in RUN mode, then
retry the file transfer.

Cannot continue, terminal is in PROGRAM
mode.

The terminal is transferring a file to or from
another computer.

Wait until the terminal completes the other
transfer, then retry the operation.

Cannot perform file transfer operation, no
INTERCHANGE communication drivers are
currently running.

INTERCHANGE drivers are not loaded on the
computer.

Exit Windows. Configure the appropriate
INTERCHANGE drivers and load them as
described in Chapter 2.

Data file CRC is incorrect.

The CRC of the historical event data file did
not match the CRC sent by the MessageView
terminal.

Retry the historical event stack upload
operation.

Data file length is incorrect.

The historical event data file did not match the
length sent by the MessageView terminal.

Retry the historical event stack upload
operation.

Error while scanning for application file CRC

MessageBuilder software could not read the
MVA file to verify the CRC.

Specify a valid MVA file.

Note: CRC is Cyclic Redundancy Check, a check for errors in files.

Advertising