Error

Message

The response packet CRC 'V1' did not match the calculated CRC 'V2' of a response from PLC V3 on V4.

Request values: Function Code = V5, Starting Address = V6, Size = V7

Example

The response packet CRC '52485' did not match the calculated CRC '34273' of a response from PLC 2 on NODE13.

Request values: Function Code = 4, Starting Address = 1001, Size = 15

Cause

A response packet was received that contained a CRC value that did not match the CRC value calculated by the interface.

Resolution

The resolution to this problem will be site or even device specific. Some of the reasons which can cause this exception are an invalid Location2 attribute (sending requests to an unknown PLC), poll delays causing packets to merge, noise on the serial communication line and other unknown factors external to the interface.

Meaning

This is a non-standard exception specific to this interface in order to handle the case of an invalid CRC value in the response packet. The meaning of the values in the message are as follows:

V1 CRC value contained in the response packet

V2 CRC value calculated by the interface

V3 Number of PLC node request sent to

V4 Ethernet node request sent to

V5 Function code in the request

V6 Starting address in the request

V7 Number of coils/inputs/outputs/registers in the request

Message

Required parameter /DN was not found.

Cause

The configuration file has a record in which a device name parameter is expected to be the first entry but cannot be found.

Resolution

Reconfigure the interface with the Modbus Interface Configurator.

Meaning

The configuration file has a record in which the device name parameter is expected as the first parameter but it was not found. This condition is likely to be caused by a configuration file with no COM ports configured or a corrupt configuration file.

Message

Tag tagname rejected. Instrument tag cannot be blank.

Cause

The InstrumentTag attribute is not defined.

Resolution

Set the InstrumentTag attribute of tag tagname to COM# in which # is an integer value from 1 to 9999.

Message

Tag tagname rejected. System error err occurred when getting the square root attribute.

Cause

The SquareRoot attribute of tag tagname could not be retrieved. This problem will normally never occur, but may be due to loss of communications with the Data Archive.

Resolution

Run pidiag -e err to determine why the attribute could not be retrieved.

Message

Tag tagname rejected. System error err occurred when getting the conversion factor attribute.

Cause

The Convers attribute of tag tagname could not be retrieved. This problem will normally never occur, but may be due to loss of communications with the Data Archive.

Resolution

Run pidiag -e err to determine why the attribute could not be retrieved.

Message

Tag tagname rejected. System error err occurred when getting the scan bit attribute.

Cause

The scan bit attribute of tag tagname could not be retrieved. This problem will normally never occur, but may be due to loss of communications with the Data Archive.

Resolution

Run pidiag -e err to determine why the attribute could not be retrieved.

Message

Load PI point failed for tag tagname. An invalid unit ID of L2 was entered in Location2 .

The unit ID must be a value between min and max .

Cause

The Location2 attribute of tag tagname is out of range.

Resolution

Modify the Location2 attribute value L2 of tagtagname so that the Unit ID is between min and max inclusively.

Message

Load PI point failed for tag tagname. An invalid scan class of L4 was entered in Location4 .

The scan class must be a value between min and max.

Cause

The Location4 attribute of tag tagname is out of range.

Resolution

Modify the Location4 attribute value L4 of tag tagname so that the scan class is between min and max inclusively.

Message

Load PI point failed for tag tagname. An invalid register/coil address of L5 was entered in Location5 . The address must be a value between min and max .

Cause

The Location5 attribute of tag tagname is out of range.

Resolution

Modify the Location5 attribute value L5 of tag tagname so that the register/coil address is between min and max inclusively.

Message

Load PI point failed for tag tagname. An unknown data type was used in Location3.

Values read: Location3 = L3, Data Type = DT, Function Code = FC.

Cause

The Location3 attribute of tag tagname contains an invalid data type.

Resolution

Modify the Location3 attribute value L3 of tag tagname so that the data type value DT is valid.

Message

Load PI point failed for tag tagname. An unknown function code was used in Location3.

Values read: Location3 = L3, Data Type = DT, Function Code = FC.

Cause

The Location3 attribute of tag tagname contains an invalid function code.

Resolution

Modify the Location3 attribute value L3 of tag tagname so that the function code value FC is valid.

Message

Load PI point failed for tag tagname. Data type DT can only be used with function codes list.

Values read: Location3 = L3, Data Type = DT, Function Code = FC.

Cause

The Location3 attribute of tag tagname contains a data type combined with a function code that does not support the data type.

Resolution

Modify the Location3 attribute value L3 of tag tagname so that the data type value DT is combined with one of the functions codes in list .

Message

Load PI point failed for tag tagname. Extended descriptor bitmask option is valid only for data types 1, 7, 9 or 11 with an input tag.

Cause

The ExDesc attribute of tag tagname contains a bitmask descriptor which is not supported by the data type of the tag.

Resolution

Remove the ExDesc attribute bitmask descriptor of tag tagname or ensure that the tag is an input tag with a supported data type.

Message

Load PI point failed for tag tagname. Extended descriptor 'B=bitmask' must be in the form B=uuvvwwxxyyzz where uu, vv, ww, xx, yy and zz each refer to a single bit.

Cause

The ExDesc attribute of tag tagname contains a bitmask descriptor which is not valid.

Resolution

Modify the ExDesc attribute bit mask descriptor value bitmask of tag tagname.

Message

Load PI point failed for tag tagname. Extended descriptor 'B=bitmask' must be in the form B=uuvvwwxxyyzz where uu, vv, ww, xx, yy and zz each refer to a single bit and none can be 00.

Cause

The ExDesc attribute of tag tagname contains a bitmask descriptor which is not valid, probably because one or more of the masks are 00.

Resolution

Modify the ExDesc attribute bit mask descriptor value bitmask of tag tagname.

Message

Load PI point failed for tag tagname. Extended descriptor custom data type manipulator C=cdtm can only be used with an input tag.

Cause

The ExDesc attribute of output tag tagname contains a custom data type manipulator descriptor. Only input tags can have a custom data type manipulator.

Resolution

Remove the ExDesc attribute custom data type manipulator descriptor.

Message

Load PI point failed for tag tagname. Extended descriptor SWAP is only valid for data types 4, 6, 7, 13, 15, 16 and strings.

Cause

The ExDesc attribute of output tag tagname contains a swap descriptor. Only tags with a data type of 4, 6, 7, 13, 15, 16 or string (101 to 199) can have a swap descriptor.

Resolution

Remove the ExDesc attribute swap descriptor.

Message

Required parameter /ID must be an integer from 1 to 2147483647. It was being set to id.

Cause

The interface ID command-line parameter value id is not a valid interface ID.

Resolution

Reconfigure the interface so that the interface ID is an integer value from 1 to 99.

Message

Required parameter /ID was not found.

Cause

There is no interface ID command-line parameter.

Resolution

Reconfigure the interface.

Message

The parameter param is not a known parameter.

Cause

The command-line parameter param is not a valid parameter.

Resolution

Remove the unknown command-line parameter.

Message

Required parameter /ICF was not found.

Cause

There is no interface configuration file command-line parameter.

Resolution

Reconfigure the interface.

Message

The interface configuration file must have a .csv extension.

Cause

The interface configuration file name specified by the /ICF command-line parameter does not have a .CSV file extension.

Resolution

Rename the interface configuration file or change the file name specified by the /ICF command-line parameter.

Message

The interface configuration file 'file.csv' could not be opened.

Cause

The interface configuration file name file.csv specified by the /ICF command-line parameter could not be opened.

Resolution

The likely cause of this error is that the interface configuration file file.csv does not exist.

Message

An unknown error occurred when reading the communications configuration file.

Cause

An error occurred when reading the interface configuration file. This error is caused by records in the file that do not represent the interface or a COM port. A likely cause is extraneous empty records inadvertently added when manually editing the interface configuration file.

Resolution

Only edit the interface configuration file.

Message

The debug trace file must have a .txt extension.

Cause

The debug trace file name specified by the /DTF command-line parameter does not have a .TXT file extension.

Resolution

Rename the file name specified by the /DTF command-line parameter.

Message

Optional parameter /DTF must specify a file name.

Cause

The debug trace file command-line parameter /DTF must specify a valid file name with a .txt extension.

Resolution

Remove the /DTF command-line parameter or set a valid file name as the parameter value.

Message

Required parameter /DN must be in the form /DN=x:y in which x is a valid IP address or hostname. It was being set to addr.

Cause

The device name parameter value in the configuration file is in the correct format but the IP address or hostname addr is not valid.

Resolution

Set the /DN parameter value to x:y in which x is a valid IP address or hostname and y is a valid service port number.

Message

Required parameter /DN must be in the form /DN=x:y in which x is a valid IP address or hostname and y is a port number.

Cause

The device name parameter value in the configuration file is not valid. It has an invalid format or the IP address, hostname or service post is invalid.

Resolution

Set the /DN parameter value to x:y in which x is a valid IP address or hostname and y is a valid service port number.

Message

Tag tagname Instrument Tag attribute node is not a valid IP address or hostname.

Cause

The InstrumentTag attribute node is not in a valid format. This error will only occur if the node passes interface validation but fails Windows system validation.

Resolution

Modify the InstrumentTag attribute node of tag tagname so that it is in a valid IP address or hostname format.

Message

Tag tagname Instrument Tag attribute 'node' is not a valid IP address. It must be in the form of x.x.x.x, where x is a number from 0 to 255 and does not have a leading zero.

Cause

The InstrumentTag attribute node is not in a valid format. One or more parts of the IP address contain a leading zero. Since a leading zero will cause the part to interpret as an octal number the interface does not support that format to prevent multiple IP addresses resolving to a single unique node.

Resolution

Modify the InstrumentTag attribute node of tag tagname so that it is in a valid IP address format without a leading zero for any part of the address.

Message

Tag tagname Instrument Tag attribute 'node' is not a valid IP address. It must be in the form of x.x.x.x, where x is a number from 0 to 255.

Cause

The InstrumentTag attribute node is not in a valid format. One or more parts of the IP address contain more than 3 digit characters or represent a value of greater than 255.

Resolution

Modify the InstrumentTag attribute node of tag tagname so that it is in a valid IP address format with no part of the address being greater than 255 or containing more than 3 digit characters.

Message

Tag tagname Instrument Tag attribute node is not a valid IP address or hostname. It cannot have contiguous period (.) delimiter characters.

Cause

The InstrumentTag attribute node is not in a valid format. The IP address or hostname contains contiguous period delimiter characters.

Resolution

Modify the InstrumentTag attribute node of tag tagname so that it is in a valid IP address or hostname format.

Message

Tag tagname Instrument Tag attribute node is not a valid hostname. Each part of the complete name must be delimited by a period (.) and cannot begin or end with a hyphen (-) or underscore (_) character.

Cause

The InstrumentTag attribute node is not in a valid format. One or more parts of the hostname begin or end with a hyphen or underscore character.

Resolution

Modify the InstrumentTag attribute node of tag tagname so that it is in a valid hostname format.

Message

Tag tagname Instrument Tag attribute node is not a valid hostname. It must begin with an alphabetic (a to z) or numeric (0 to 9) character.

Cause

The InstrumentTag attribute node is not in a valid format. The first character in the complete hostname is not alphabetic or numeric.

Resolution

Modify the InstrumentTag attribute node of tag tagname so that it is in a valid hostname format.

Message

Tag tagname Instrument Tag attribute 'node' is not a valid hostname. It must end with an alphabetic (a to z) or numeric (0 to 9) character.

Cause

The InstrumentTag attribute node is not in a valid format. The last character in the complete hostname is not alphabetic or numeric.

Resolution

Modify the InstrumentTag attribute node of tag tagname so that it is in a valid hostname format.

Message

Tag tagname Instrument Tag attribute 'node' is not a valid hostname. It must contain only alphabetic (a to z), numeric (0 to 9), hyphen (-), underscore (_) and period (.) characters.

Cause

The InstrumentTag attribute node is not in a valid format. It contains one or more characters that are not an alphabetic, numeric, hyphen, underscore or period character.

Resolution

Modify the InstrumentTag attribute node of tag tagname so that it is in a valid hostname format.

Message

Tag tagname Instrument Tag attribute 'node' is not a valid hostname. Each part cannot contain more than 63 characters.

Cause

The InstrumentTag attribute node is not in a valid format. One or more parts of the hostname contain more than 63 characters.

Resolution

Modify the InstrumentTag attribute node of tag tagname so that it is in a valid hostname format.

Message

Tag tagname Instrument Tag attribute node is not a valid hostname. It cannot contain more than 255 characters.

Cause

The InstrumentTag attribute node is not in a valid format. The complete hostname contains more than 255 characters.

Resolution

Modify the InstrumentTag attribute node of tag tagname so that it is in a valid hostname format.

Message

Tag tagname rejected. Instrument tag 'node' is not a configured node.

Cause

The InstrumentTag attribute node is valid but has not been configured.

Resolution

Modify the InstrumentTag attribute node of tag tagname to a valid, configured node or configure the node represented bynode.