Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

PI Interface for Modbus Ethernet PLC

Warning

  • Last UpdatedNov 05, 2024
  • 5 minute read

Message ID

43417

Message

Tag 'V1' was rejected because it was invalid.

Example

Tag 'DemoTag25' was rejected because it was invalid.

Cause

The tag was not properly configured.

Resolution

The interface continues on without loading the tag. The tag must be correctly configured and the interface must be restarted before the tag can be loaded

Meaning

The format of this message is the same for all interface parameter out of range errors. The meaning of the values in the message itself are as follows:

V1 Long name of the tag

Note: This message is preceded by a more specific message noting the exact problem with the tag.

Message ID

43430

Message

Load PI point failed for tag tagname. An invalid combination of data type and 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 combination of data type and function code.

Resolution

Modify the Location3 attribute value L3 of tag tagname so that the combination of the function code value FC and the data type value DT is valid.

Message ID

43431

Message

Changing function code for tag tagname from 6 to 16. Function code 6 does not support data types 5, 6, 7, 8, 12, 13, 15 and 16.

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

Cause

The Location3 attribute of tag tagname contains a data type that is not supported by function code 6.

Resolution

The interface will change the Location3 attribute value L3 of tag tagname so that the function code value FC is 16.

Message ID

43433

Message

PI point tagname has a PI point type that is incompatible with the Modbus data type. Loss of precision or invalid values may occur.

Cause

The Location3 attribute of tag tagname contains a data type that is incompatible with the PI point type.

Resolution

No resolution is required but the user must be aware of a potential loss of precision or invalid values.

Message ID

43435

Message

Optional parameter V1 must be an integer from V2 to V3. It is being set to V4.

Example

Optional parameter /DTFMAX must be an integer from 1 to 100. It is being set to 10.

Cause

An optional interface or Ethernet node configuration parameter is out of range.

Resolution

The interface will set the parameter to the default value.

Meaning

The format of this message is the same for all optional interface parameter out of range errors. The meaning of the values in the message itself are as follows:

V1 Parameter token (i.e. name)

V2 Minimum possible value for the parameter

V3 Maximum possible value for the parameter

V4 Default value for the parameter

Message ID

43439

Message

Load PI point failed for tag tagname. Extended descriptor trigger EVENT=triggertag resulted in system error err when attempting to retrieve the trigger tag.

Cause

The ExDesc attribute of tag tagname contains a trigger descriptor in which trigger tag triggertag cannot be retrieved. The following are the possible reasons for a failure:

err = -2 The trigger tag name is all spaces

err = -5 Trigger tag not found, or not yet connected to a server err = >0 A system error occurred

Resolution

If err is a negative number the resolution is implied by the error itself. Otherwise, run pidiag -e err to determine why the trigger tag could not be retrieved.

Message ID

43440

Message

Load PI point failed for tag tagname. Extended descriptor trigger 'EVENT' or 'TRIG' can only be used with an input tag.

Cause

The ExDesc attribute of output tag tagname contains a trigger descriptor. Only input tags can have a trigger tag.

Resolution

Remove the ExDesc attribute trigger descriptor.

Message ID

43441

Message

Load PI point failed for tag tagname. Extended descriptor trigger 'EVENT=triggertag' is not valid.

Cause

The ExDesc attribute of output tag tagname contains a trigger descriptor which is not valid. The value is probably incorrectly formatted due to extraneous space characters or missing single quote delimiter characters.

Resolution

Modify the ExDesc attribute trigger descriptor value triggertag of tag tagname.

Message ID

43442

Message

Load PI point failed for tag tagname. Extended descriptor trigger 'EVENT=triggertag condition' does not contain a valid condition.

Cause

The ExDesc attribute of tag tagname contains a trigger descriptor which does not have a valid event condition.

Resolution

Modify the ExDesc attribute trigger descriptor event condition value condition of tag tagname.

Message ID

43443

Message

Load PI point failed for tag tagname. Extended descriptor custom data type manipulator C=cdtm is invalid. It must be a value between 0 and 4.

Cause

The ExDesc attribute of output tag tagname contains an invalid custom data type manipulator descriptor cdtm.

Resolution

Update the ExDesc attribute custom data type manipulator descriptor to be a valid value.

Message ID

43455

Message

Required parameter /ID in configuration file is param, but it should match the interface ID of intf.

Cause

The interface ID parameter value param in the interface configuration file does not match the interface ID value intf of the interface reading the configuration file.

Resolution

This message is only a warning that the interface configuration file may be the wrong one for the interface loading it. At some point the use should ensure that the interface ID of the interface itself and the ID in the configuration file match.

Message ID

43473

Message

Timeout on node. Retries failed while trying to request data from Node ID plc.

Cause

The connection to the device plc on communications node node timed-out.

Resolution

This message is a warning that the interface has received no response to requests to the specified device on the specified communications node. This indicates that the device may be temporarily down, communications may be abnormally slow or the retry count needs to be increased.

Message ID

43474

Message

Timeout cleared on node Node ID plc.

Cause

The connection to the device plc on communications node node resumed after a timeout.

Resolution

This message is a warning that the interface has begun receiving a response to requests to the specified device on the specified communications node after it had previously timed-out.

Message ID

43498

Message

Required parameter /DN=X is a duplicate node.

Cause

The device name parameter value in the configuration file is valid but the node has already been configured.

Resolution

Remove the entry from the configuration file or change node to an Ethernet node that has not been configured.

Message ID

43510

Message

Tag 'V1' loaded but not ready.

Instrument tag 'V2' is not yet a configured node.

Example

Tag 'DemoTag25' loaded but not ready.

Instrument tag 'plc2.osisoft.int' is not yet a configured node.

Cause

The tag was loaded but will not be updated because the Ethernet node of the tag has not been configured yet.

Resolution

Once the node has been configured the tag will begin to update.

Meaning

The format of this message is the same for all interface parameter out of range errors. The meaning of the values in the message itself are as follows:

V1 Long name of the tag

V2 Ethernet node in the instrument tag attribute

Related Links
TitleResults for “How to create a CRG?”Also Available in