# BASEstartm Open DAS
for Allen-Bradley Data Highwaytm
on Tru64tm UNIX
Installation and User's Guide

Previous | Contents | Index

# Appendix B
DAS Error Messages

This appendix contains returned values and associated error messages specific to the DAS for Allen-Bradley Data Highway.

> aborting, The connection to the device is being aborted,

Explanation: Error. The connection to the device is being aborted by an error or by user request. No more requests will be processed by the DAS until the connection is restored.
User Action: If the abort was caused by a device error, take action based on the error that occurred. If the abort was a result of a user request. Reconnect to the device before attempting further operations.

> addresstoolong, Variable address string too long,

Explanation: Error. A variable address that is being defined is too long. An address must be 30 characters of less in length.
User Action: Redefine the variable using a shorter address.

> apptypeunsupp, The given application type is not supported for this DAS,

Explanation: Error. The application type that was specified in the variable definition is not supported by this DAS.
User Action: Change the application type to a valid type for this DAS.

> badaddress, PLC XX sent data for address XX, but this address does not exist on the host,

Explanation: Error. A variable was received from a PLC and the address did not match any variables defined on the host.
User Action: Define a variable with the correct address on the host or change the address of the variable being sent from the PLC.

> badbcdvalue, Bad BCD value,

Explanation: Error. A request was made to convert from or to a BCD number and the number was not a valid BCD value.
User Action: Modify the value to be converted into a valid BCD number.

> badmodel, The given PLC model is not supported,

Explanation: Error. The model number that was specified in the device definition is not supported by this DAS.
User Action: Change the model number to one that is supported by this DAS.

> bufferoverrun, Buffer overrun on line XX - terminator missed in data highway message,

Explanation: Error. When reading a data highway message, the maximum PDU length was reached before the end of message character was received. This problem is most likely caused by a communications error with the PLC.
User Action: Check all cabling to make sure that it is properly shielded, grounded and seated.

> datatoolarge, Application data too large for the data size of the variable,

Explanation: Error. The actual size of a string variable being sent to a device is larger than that defined by the variable definition. An actual size that is smaller than the variable definition is allowed but not one that is larger.
User Action: Define a variable with the correct size as the data being sent or change the size of the data being sent by the application.

> datatoosmall, PLC data too small for the data size of the variable,

Explanation: Error. A variable was received from a PLC and the address matched a host variable, but the size of the data defined for the variable is larger than the size of the data actually received.
User Action: Define a variable with the correct size as the data being sent or change the size of the data being sent by the PLC.

> datatrunc, PLC data from XX to XX too large for variable XX,

Explanation: Error. A variable was received from a PLC and the address matched a host variable, but the size of the data defined for the variable is smaller than the size of the data actually received. The data returned is truncated to fit into the variable.
User Action: Define a variable with the correct size as the data being sent or change the size of the data being sent by the PLC.

> duptrans, Duplicate transaction received on line XX, transaction number = !UW,

Explanation: Warning. A duplicate transaction number was received on the data highway line. In most cases this is probably caused by too long a delay in responding to a message sent by the KE/KF card to the host. The duplicate message is discarded by the host.
User Action: Increase the KE/KF card timeout value by modifying the KE_TIMEOUT line attribute in ODS.

> exterrsts, PLC XX sent extended status error = X'XX',

Explanation: Error. An Allen-Bradley extended status error occurred.
User Action: Consult the Allen-Bradley PLC communications manual to determine the cause of the error and take appropriate action based on the error code.

> extrachars, Extraneous characters before message start on line XX,

Explanation: Warning. Extra characters were received before the DLE STX on the line. The most likely cause is the remains of a timed out previous transaction. It is also possible that there is noise on the line.
User Action: If this message persists, then check shielding, length of cabling or other factors that may result in a noisy communications signal. Correct any problems that are found.

> extsts06, Ext Sts X06 - address doesn't point to something usable,

Explanation: Error. An attempt was made to read or write to a PLC address that isn't a valid PLC data table address for this PLC.
User Action: Define a variable with an address that matches actual PLC memory or reconfigure the PLC memory to include the requested address.

> extsts07, Ext Sts X07 - file is wrong size,

Explanation: Error. An attempt was made to write to a PLC address that is beyond the end of a PLC data table address.
User Action: Define a variable with an address that matches actual PLC memory or reconfigure the PLC memory to include the requested address.

> extsts0a, Ext Sts X0A - transaction size plus word address is too large,

Explanation: Error. An attempt was made to read from a PLC address that is beyond the end of a PLC data table address.
User Action: Define a variable with an address and size that matches actual PLC memory or reconfigure the PLC memory to include the requested address.

> extsts11, Ext Sts X11 - illegal data type,

Explanation: Error. An attempt was made to read from a PLC address that does not exist in the PLC or that is not valid for the table being accessed.
User Action: Define a variable with an address that matches the actual PLC memory or reconfigure the PLC memory to include the requested address.

> extsts12, Ext Sts X12 - invalid parameter or invalid data,

Explanation: Error. An invalid command or data was sent to the PLC.
User Action: Submit an SPR describing the circumstances that caused the error.

> extstserr, PLC extended status error,

Explanation: Error. An Allen-Bradley extended status error occurred.
User Action: Use a data scope to capture the error code and take appropriate action based on the error code.

> internalerror, Internal error,

Explanation: Error. An internal error occurred in the DAS.
User Action: Submit an SPR describing the circumstances that caused the error.

> invaddresstype, Invalid address type,

Explanation: Error. A variable that is being defined is defined as an illegal address type. Only unconstrained address types are allowed.
User Action: Redefine the variable using the unconstrained address type.

> invalidaddress, The specified PLC address is not supported by this DAS,

Explanation: Error. An address was sent by a PLC but the address is not supported by this DAS.
User Action: Reprogram the PLC and specify a valid address for this DAS. Consult the DAS documentation to determine a valid address.

> invalidbitwrite, Bit writes cannot span more than one element,

Explanation: Error. An attempt was made to do a bit write that spanned more than one element. The DAS supports writes to only one element at a time.
User Action: Change the starting bit or change the number of bits that are being written so that the write spans only one element.

> invalidcommand, Invalid command code received in a message from the PLC,

Explanation: Error. A message was received from the PLC, but the command code used by the PLC in the write command is not supported by the DAS.
User Action: Reprogram the PLC to send the correct command code.

> invaliddrop, Invalid drop time specified in DH_TELNET ODS entry,

Explanation: Error. The drop time specified is not a valid number. The drop time must be a number greater than 0.
User Action: Use ODS to enter a valid drop time attribute.

> invalidenqretries, Invalid ENQ retries number in the DH_LINE ODS entry,

Explanation: Error. The ENQ retries attribute must be between 0-20.
User Action: Use ODS to enter an ENQ retries number between 0-20.

> invalidfunction, Invalid function code received in a message from the PLC,

Explanation: Error. A message was sent from the PLC, but the function code used by the PLC in the write command is not supported by the DAS.
User Action: Reprogram the PLC to send the correct function code.

> invalidgroup, Variables in a group must all belong to the same file,

Explanation: Error. A group read was attempted without all the variables in the group belonging to the same file type and file number or a subelement of a structure file was included in the group.
User Action: Examine the members of the group to determine which variable does not belong, remove that variable from the list and retry the group read.

> invalidgroupmem, Variable XX in a group read for device XX does not belong,

Explanation: Error. A group read was attempted without all the variables in the group belonging to the same file type and file number.
User Action: Remove the incorrect variable from the list and retry the group read.

> invalidipaddress, Invalid IP_ADDRESS ODS attribute for the given line,

Explanation: Error. The IP_ADDRESS must be less than 50 characters in length.
User Action: Enter an IP address that is 50 characters or less in length.

> invalidkestation, Invalid KE station number in the DH_LINE ODS entry,

Explanation: Error. AB station numbers must be an octal number between 0-377.
User Action: Use ODS to enter a station number between 0-377 octal.

> invalidmodem, Invalid modem attribute specified in the DH_LINE ODS entry,

Explanation: Error. The modem attribute must be one of TRUE, ON, YES, 1 or FALSE, OFF, NO, 0.
User Action: Use ODS to enter a valid modem attribute.

> invalidnakretries, Invalid NAK retries number in the DH_LINE ODS entry,

Explanation: Error. The NAK retries attribute must be between 0-20.
User Action: Use ODS to enter a NAK retries number between 0-20.

> invalidparity, Invalid parity specified in the DH_LINE ODS entry,

Explanation: Error. The parity defined must be either EVEN or NONE.
User Action: Use ODS to enter a valid parity (EVEN, NONE).

> invalidport, Invalid port name specified in the DH_LINE ODS entry,

Explanation: Error. Port names must be 10 characters or less.
User Action: Use ODS to enter a port name that is less than 10 characters.

> invalidportnum, Invalid PORT_NUMBER ODS attribute for the given line,

Explanation: Error. The PORT_NUMBER must be less than 10 characters in length.
User Action: Enter a PORT_NUMBER address that is 10 characters or less in length.

> invalidprobe, Invalid probe time specified in DH_TELNET ODS entry,

Explanation: Error. The probe time specified is not a valid number. The probe time must be a number greater than 0.
User Action: Use ODS to enter a valid probe time attribute.

> invalidspeed, Invalid speed (baud rate) specified in the DH_LINE ODS entry,

Explanation: Error. Baud rates from 110 to 19200 are supported for the AB DAS.
User Action: Use ODS to enter a speed from 110 to 19200.

> invalidstation, Invalid station number in the DH_PATH ODS entry,

Explanation: Error. AB station numbers must be an octal number between 0-377.
User Action: Use ODS to enter a station number between 0-377 octal.

> invalidstructread, Variables in a group must read the entire structure,

Explanation: Error. A group read was attempted without all the variables in the group reading a complete structure element. For example, a timer element is being read, and an accumulator subelement was specified in the address.
User Action: Examine the variables in the group and specify an address for the entire structure for all members of the group.

> invalidtimeout, Invalid timeout value in the DH_LINE ODS entry,

Explanation: Error. An invalid timeout value was entered for the timeout value in ODS. Timeouts must be between 2 and 6 seconds.
User Action: Use ODS to enter a timeout value between 2-6.

> invalidtrace, Invalid trace attribute specified in the DH_LINE or DH_PATH ODS entry,

Explanation: Error. The trace attribute must be one of TRUE, ON, YES, 1 or FALSE, OFF, NO, 0.
User Action: Use ODS to enter a valid trace attribute.

> iotimeout, AB Data Highway I/O timeout on line XX,

Explanation: Error. The PLC began to respond but the host timed out when attempting to read the complete response from the PLC. The response could be part of a read or a write operation.
User Action: Check all cabling to make sure that it is properly shielded, grounded and seated. Verify that the communication parameters are set up properly on both PLC and the host.

> linenoise, Noise encountered on data highway communications line XX,

Explanation: Error. An unexpected character was received on the data highway communications line. The DAS ignores the character received.
User Action: Check all cabling to make sure that it is properly shielded, grounded and seated.

> locerrsts, PLC XX sent local status error = X'XX',

Explanation: Error. An Allen-Bradley local status error occurred.
User Action: Consult the Allen-Bradley PLC communications manual to determine the cause of the error and take appropriate action based on the error code.

> locsts02, Loc Sts X02 - link layer timed out or received a NAK,

Explanation: Error. A local error occurred when communicating with the KE/KF card. This error is usually caused by the not being at the address specified in the STATION ODS attribute.
User Action: Check the PLC station ID in ODS and on the PLC to make sure that they match.

> locstserr, PLC local status error,

Explanation: Error. An Allen-Bradley local status error occurred.
User Action: Examine the log file (BASEstar Open) or stderr to determine the exact error status returned. Then consult the Allen-Bradley PLC communications manual to determine the cause of the error and take appropriate action based on the error found.

> mmsaddrtypeunsupp, The given MMS type is unsupported for the given address,

Explanation: Error. The MMS type is not supported for the variable address given.
User Action: Modify the MMS type to one supported for the given address or modify the address to one supported for the MMS type.

> mmstypeunsupp, The given MMS type is not supported for this DAS,

Explanation: Error. The MMS type that was specified in the variable definition is not supported by by this DAS.
User Action: Change the MMS type to a valid type for this DAS.

> msgtooshort, A message received from the PLC was too short,

Explanation: Error. A message was received from the PLC, but the message couldn't be decoded because it didn't contain enough data. This error is most likely caused by improper programming of the PLC or by communication errors.
User Action: Check the PLC program for errors and check that all communications plugs are properly seated and all communications cabling is not shorted, not broken and is properly terminated and shielded.

> nak, Bad checksum - NAK sent on line XX, transaction number = !UW,

Explanation: Warning. A bad checksum was detected, so a NAK was sent in response to the message. A bad checksum is most likely the result of noisy communications.
User Action: If NAK messages persist, then check shielding, length of cabling or other factors that may result in a noisy communications signal. Correct any problems that are found.

> neterr, AB Data Highway Network error occurred,

Explanation: Error. A network error on the Allen-Bradley Data Highway occurred.
User Action: Examine the network status in the returned IOSB to determine the specific network error that occurred and take action based on that error.

> noenqretries, No "ENQ_RETRIES" ODS entry for the given line,

Explanation: Error. The AB DAS requires an ENQ_RETRIES attribute defined in ODS. The ENQ_RETRIES attribute is defined for the DH_LINE object class within ODS.
User Action: Use the DH_LINE object class within ODS to define the ENQ_RETRIES attribute for this line. Use a valid number when defining the ENQ_RETRIES attribute.

> noipaddress, No "IP_ADDRESS" ODS entry for the given line,

Explanation: Error. The AB DAS requires an IP_ADDRESS attribute defined in ODS. The IP_ADDRESS attribute is defined for the DH_TELNET class within ODS.
User Action: Use the DH_TELNET object class within ODS to define the IP_ADDRESS attribute for this line. Use a valid IP address for this attribute.

> nokestation, No "KE_STATION" ODS entry for the given line,

Explanation: Error. The AB DAS requires a KE_STATION attribute defined in ODS. The KE_STATION attribute is defined for the DH_LINE object class within ODS.
User Action: Use the DH_LINE object class within ODS to define the KE_STATION attribute for this line. Use a valid number when defining the KE_STATION attribute.

> noketimeout, No "KE_TIMEOUT" ODS entry for the given line,

Explanation: Error. The AB DAS requires a KE_TIMEOUT attribute defined in ODS. The KE_TIMEOUT attribute is defined for the DH_LINE object class within ODS.
User Action: Use the DH_LINE object class within ODS to define the KE_TIMEOUT attribute for this line. Use a valid number when defining the KE_TIMEOUT attribute.

> nolicense, No software license,

Explanation: Error. The AB DAS requires a software license.
User Action: Install the license PAK for the AB DAS.

> noline, No "/LINE=" ODS entry for the given application simple name,

Explanation: Error. The AB DAS requires a /LINE= attribute defined for the ODS entry corresponding to the application simple name entry for the VMD. The /LINE= attribute is defined for DH_PATH object class within ODS.
User Action: Use the DH_PATH object class within ODS to define the application simple name for this VMD. Use a valid line name when defining the /LINE= attribute.

> nomodem, No "MODEM" ODS entry for the given line,

Explanation: Error. The AB DAS requires a MODEM attribute defined in ODS. The MODEM attribute is defined for the DH_LINE object class within ODS.
User Action: Use the DH_LINE object class within ODS to define the MODEM attribute for this line. Modem control is either enabled (TRUE, ON, YES, 1) or disabled (FALSE, OFF, NO, 0).

> nonakretries, No "NAK_RETRIES" ODS entry for the given line,

Explanation: Error. The AB DAS requires a NAK_RETRIES attribute defined in ODS. The NAK_RETRIES attribute is defined for the DH_LINE object class within ODS.
User Action: Use the DH_LINE object class within ODS to define the NAK_RETRIES attribute for this line. Use a valid number when defining the NAK_RETRIES attribute.

> noparity, No "PARITY" ODS entry for the given line,

Explanation: Error. The AB DAS requires a PARITY attribute defined in ODS. The PARITY attribute is defined for the DH_LINE object class within ODS.
User Action: Use the DH_LINE object class within ODS to define the PARITY attribute for this line. Use a valid parity (EVEN, NONE) when defining the PARITY attribute.

> noport, No "PORT" ODS entry for the given line,

Explanation: Error. The AB DAS requires a PORT attribute defined in ODS. The PORT attribute is defined for the DH_LINE object class within ODS.
User Action: Use the DH_LINE object class within ODS to define the PORT attribute for this line. Use a valid port name when defining the PORT attribute.

> noportnumber, No "PORT_NUMBER" ODS entry for the given line,

Explanation: Error. The AB DAS requires a PORT_NUMBER attribute defined in ODS. The PORT_NUMBER attribute is defined for the DH_TELNET class within ODS.
User Action: Use the DH_TELNET object class within ODS to define the PORT_NUMBER attribute for this line. Use a valid IP port number for this attribute.

> noresponse, No response from the PLC within the timeout period,

Explanation: Error. A message was sent to the PLC and was acknowledged, but no confirmation message was received by the host in the required timeframe.
User Action: Ensure that the timeout value in the line parameters is large enough based on the data highway network load.

> nospeed, No "SPEED" ODS entry for the given line,

Explanation: Error. The AB DAS requires a SPEED attribute defined in ODS. The SPEED attribute is defined for the DH_LINE object class within ODS.
User Action: Use the DH_LINE object class within ODS to define the SPEED attribute for this line. Use a valid baud rate when defining the SPEED attribute.

> nostation, No "STATION" ODS entry for the given application simple name,

Explanation: Error. The AB DAS requires a STATION attribute defined for the ODS entry corresponding to the application simple name entry for the VMD. The STATION attribute is defined for DH_PATH object class within ODS.
User Action: Use the DH_PATH object class within ODS to define the application simple name for this VMD. Use a valid data highway station number when defining the STATION attribute.

> notimeout, No "TIMEOUT" ODS entry for the given line,

Explanation: Error. The AB DAS requires a TIMEOUT attribute defined in ODS. The TIMEOUT attribute is defined for the DH_LINE object class within ODS.
User Action: Use the DH_LINE object class within ODS to define the TIMEOUT attribute for this line. Use a valid number when defining the TIMEOUT attribute.

> notrace, No "TRACE" ODS entry,

Explanation: Error. The AB DAS requires a TRACE attribute defined in ODS. The TRACE attribute is defined for the DH_PATH object class and for the DH_LINE object class within ODS.
User Action: Use the DH_LINE and DH_PATH object classes within ODS to define the TRACE attribute for this line. Trace is either enabled (TRUE, ON, YES, 1) or disabled (FALSE, OFF, NO, 0).

> parsefailed, The parsing of an ASCII address failed,

Explanation: Error. When defining a variable, the parsing of the ASCII address failed. Either the syntax or the value of a portion of the address is incorrect.
User Action: Consult the user documentation to determine a valid address for the variable being defined and redefine the variable using the correct syntax.

> rcvthreaddied, Receiver thread died for line XX, status = X,

Explanation: Error. Receiver thread exited with an error.
User Action: Take action based on the error code.

> rcvthreadexcep, Receiver thread for line XX caught an exception, status = X,

Explanation: Error. Receiver thread caught an exception. The exception that was caught is in this message.
User Action: Examine the exception that was caught and take action based on the error code.

> remerrsts, PLC XX sent remote status error = X'XX',

Explanation: Error. An Allen-Bradley remote status error occurred.
User Action: Consult the Allen-Bradley PLC communications manual to determine the cause of the error and take appropriate action based on the error code.

> remsts60, Rem Sts X60 - function disallowed due to command protection selection,

Explanation: Error. The PLC is in the wrong protection mode for the command being attempted.
User Action: Change the protection mode to one appropriate for the command.

> remsts70, Rem Sts X70 - processor is in program mode,

Explanation: Error. The PLC is in the wrong processor mode for the command being attempted.
User Action: Change the processor mode to one appropriate for the command.

> remstserr, PLC remote status error,

Explanation: Error. An Allen-Bradley remote status error occurred.
User Action: Examine the log file (BASEstar Open) or stderr to determine the exact error status returned. Then consult the Allen-Bradley PLC communications manual to determine the cause of the error and take appropriate action based on the error found.

> reqpending, Conclude rejected because of a pending read/write request,

Explanation: Error. The conclude request was rejected because either a read or a write request was currently pending.
User Action: Either abort the connection or wait for the current request(s) to complete before retrying the conclude.

> retriesexceeded, The NAK retry count was exceeded,

Explanation: Error. When trying to communicate to the device, the NAK retry count was exceeded. The NAK retry being exceeded means that the message being sent to the device was garbled during transmission and did not match the checksum.
User Action: Check cabling to ensure there are no shorts or breaks. Check/replace KE/KF card.

> retriesexcline, The NAK retry count was exceeded for line XX,

Explanation: Error. When trying to communicate to the device, the NAK retry count was exceeded. The NAK retry being exceeded means that the message being sent to the device was garbled during transmission and did not match the checksum.
User Action: Check cabling to ensure there are no shorts or breaks. Check/replace KE/KF card.

> structwriteunsup, Structure writes are not supported,

Explanation: Error. Writes to structure variables are not supported. Reads of structure variables are supported, but not writes.
User Action: Write only to elements of the structure.

> timeout, AB Data Highway timeout when reading from the PLC,

Explanation: Error. The PLC did not respond when attempting to read a response from the PLC. The response could be part of a read or a write operation.
User Action: Check all cabling to make sure that it is properly shielded, grounded and seated. Verify that the communication parameters are set up properly on both PLC and the host. Verify that the correct station address has been selected on the PLC and on the host.

> timeoutreq, AB Data Highway request timeout on line XX,

Explanation: Error. The PLC did not respond when attempting to read a response from the PLC. The response could be part of a read or a write operation.
User Action: Check all cabling to make sure that it is properly shielded, grounded and seated. Verify that the communication parameters are set up properly on both PLC and the host. Verify that the correct station address has been selected on the PLC and on the host.

> timeoutresp, AB Data Highway response timeout on line XX,

Explanation: Error. The PLC did not respond when attempting to read a response from the PLC. The response was part of a write indication confirmation.
User Action: Check all cabling to make sure that it is properly shielded, grounded and seated. Verify that the communication parameters are set up properly on both PLC and the host. Verify that the correct station address has been selected on the PLC and on the host.

> tmrthreadcancel, Timer thread was cancelled,

Explanation: Error. Timer thread was cancelled.
User Action: Restart the OMNI application.

> tmrthreadexcep, Timer thread caught an exception, status = X,

Explanation: Error. Timer thread caught an exception. The exception code that was caught is in the message.
User Action: Examine the exception that was caught and take action based on the error code.

> transnotfound, Matching transaction number not found for data highway message on line XX, station XX, transaction number = !UW,

Explanation: Error. A response was received from the PLC but there wasn't found a matching request transaction number to the transaction number in the response.
User Action: Check all cabling to make sure that it is properly shielded, grounded and seated. If the transaction had previously timed out, take steps to reduce Data Highway network traffic or the load on the host or both.

> transtimedout, No response from VMD XX, transaction number = !UW,

Explanation: Error. A message was sent to the PLC and was acknowledged, but no confirmation message was received by the host in the required timeframe.
User Action: Ensure that the timeout value in the line parameters is large enough based on the data highway network load.

> unexpcommand, Unexpected command received from PLC XX. Expected command code was X'XX'; received command code was X'XX',

Explanation: Error. An unexpected command was received in a message from the PLC.
User Action: Reprogram the PLC to send the correct command code.

> unexpfunction, Unexpected function received from PLC XX. Expected function code was X'XX'; received function code was X'XX',

Explanation: Error. An unexpected function code was received in a message from the PLC.
User Action: Reprogram the PLC to send the correct function code.

> unsupported, The requested function is not supported by the DAS,

Explanation: Error. An attempt was made to execute an OMNI function that is not supported by this DAS.
User Action: Consult the user documentation to determine which functions are supported by the DAS and limit the OMNI functions used to those supported by the DAS.

> variablenotfound, Variable not found with the specified address,

Explanation: Error. A variable was received from a PLC and the address did not match any variables defined on the host.
User Action: Define a variable with the correct address on the host or change the address of the variable being sent from the PLC.

> wrongindication, An indication was received from an unknown PLC - line XX, station XX,

Explanation: Error. An indication was received from a PLC station address, but the station is not known by the DAS.
User Action: Create a VMD with the station address of the PLC sending data to the DAS, or reprogram the PLC that is sending the data so that it is no longer sends data to the DAS.

Index | Contents