64 •
••
• Allen-Bradley QUICKDESIGNER
Optional Data File Names
The data file names used in previous examples were automatically generated by the software. These
names were coded to indicate the rack/group/module address and the type of block transfer. For
example, the data file name BTR0120 indicates that the data file is a block transfer read and the
emulated slot address is rack 1, group 2, module 0. You have the option of naming these data files
anything you want, we just tried to make it easier for you. You can name them BUTTONS, or
VALVES, or whatever. The format of the tag name remains the same. The word specifier must be
contained in brackets and the bit specifier must be designated by a slash (/). Therefore,
VALVES[00]/01 is word 00, bit 01 of data file named VALVES.
There are some precautions when using your own naming system. It becomes difficult to remember
what kind of block transfer is associated with optional file names. For example, is VALVES a BTR or
BTW file name? We suggest you adopt a naming convention that includes a reference to the type of
block transfer. This will prevent you from trying to write a bit to a block transfer read data file.
The name of the data file can be up to 31 characters, so you can be creative with naming conventions.
Instead of VALVES, perhaps VALVES(BTW) would better indicate the type of file.
There is also a caution about using automatically named files. Make sure the rack/group/module you
pick to emulate will not be needed later on. If you are forced to give up that rack/group/module
location, you will be stuck with many operators that now have the wrong file name. For example, if you
start out using the file name BTR0120, and you must release rack 01, group 2, module for a real rack,
you will be stuck with operators assigned to that file name. You can assign a new rack by turning off
the automatic name feature and use the old name, but now it will be very confusing. If you assign your
own file names, it will always be easy to remember what the file names are for and how they are used.
Error Codes
The error code table is now as follows:
(02:C0) Fatal error, Detected wrong or missing I/O card
(02:C1) Fatal error, I/O card failed to initialize & start
(02:C2) Fatal error, Invalid configuration (rack, BTR, or BTW)
(02:C3) Fatal error, undefined
(02:C4) I/O card error, command error
(02:C5) I/O card error, status error
(02:C6) I/O card error, watchdog failure
(02:C7) I/O card error, memory failure
(02:C8) I/O card error, passthrough error
(02:C9) I/O card error, Invalid command
(02:CA) I/O card error, undefined
(02:CB) Com error, S1 file failed to open
(02:CC) Com error, I/O link error
(02:CD) Com error, undefined
(02:CE) Com error, undefined
(02:CF) Com error, Timeout (also fe & ff)
(02:FB) Data memory table overflow
(02:FC) Protocol error
(02:FD) Data error
(02:FE) RX timeout
(02:FF) TX timeout or SIO error
To Next Page
Loading...
