GESRTP Communication Driver error messages

DASProtFail Messages

GESRTP Server creation failed.

The GESRTP Communication Driver cannot create an object.

The Communication Driver is not properly installed or it may be a memory-related issue.

Reinstall the Communication Driver.

Demo license mode for GESRTP Server expired.

The GESRTP Communication Driver was running in demo mode and the time expired.

The demo license time period expired.

Purchase a license.

Failed to initialize listen socket. Hence no unsolicited messages will be received.

The Unsolicited Listen socket failed to initialize.

The socket initialization could not be done properly.

Check the connection and re-start the server.

Attempt to resolve remote hostname "<host_name>" failed.

The hostname could not be resolved.

The hostname specified is not a valid hostname.

Verify the correct IP address of the PLC and the hostname in the hosts file.

Connection attempt for the PLC:<plc_name> has timed out, closing socket at <time>.

The connection attempt to the PLC has timed out.

Network problem.

Check the network connection and try again.

Connection socket to the PLC: <plc_name> failed at <time>.

The socket connection failed.

Network problem.

Check the network connection and try again.

Poke value string length to the Item:'<item_name>' is exceeding 2000 characters. values cannot be processed.

The poke value to the string item is exceeding the protocol limit.

The poke value to the string item is exceeding the protocol limit.

The client must write a smaller value.

<item_name>: Bad Poll Response Received::Error Codes Major:"<major_code>" Minor:"<minor_code>".

The poll operation to an item has a bad response.

The poll could not be done properly.

Check the major and minor code information for more details.

Fault Table: Response packet received from the PLC has insufficient data.

The response packet for the fault number is bad.

The request packet was not sent properly or the fault does not exist in the PLC.

Retry the operation. If the problem persists, contact Technical Support.

Bool items: Response packet from the PLC has insufficient data.

The response packet from the PLC has insufficient data for the advised Boolean items.

The request packet was not sent properly.

Retry the operation. If the problem persists, contact Technical Support.

Insufficient response packet received from the PLC while advising an item.

The response packet from the PLC after advise is bad.

The packet information is lost.

Un-advise and advise again. If the problem persists, contact Technical Support.

Poke operation failed for the item:'<item_name>.

The poke could not be done to the PLC item.

Could not get the poked value from the client.

Retry the poke to the item. If the problem persists, contact Technical Support.

<item_name> : Bad Poke Response Received:: Error Codes Major:<major_code> Minor:<minor_code>

The poke response for the poke operation to an item has a bad response.

The poke could not be done properly.

Check the major and minor code information for more details.

Insufficient response packet received from the PLC while poking to an item.

The response packet from the PLC after the poke is bad.

The packet information is lost.

Retry the poke.

Failed to retrieve host information from a host database. Error code = <error_code>.

The hostname configured for the PLC could not be resolved.

N/A

Use a valid hostname for the PLC.

The socket is marked as nonblocking and the connection cannot be completed immediately for host <host_name>.

A connection could not be established.

The socket could not get the connection established.

Check the network connection and try again.

Socket Read failed with errorcode <error_code>.

The socket read failed while reading a value from the PLC item.

Network problem.

Check the network connection and try again.

SocketWrite failed with errorcode <error_code>.

The socket write failed while updating a value to an item.

Network problem.

Check the network connection and try again.

Unsolicited socket read failed with errorcode <error_code>.

The read from the unsolicited socket failed.

Network problem.

Check the network connection and try again.

Unsolicited socket write failed with errorcode <error_code>.

The write to the unsolicited socket failed.

Network problem.

Check the network connection and try again.

DASProtWarn Messages

PLC Type configured for the host::%s is not matching with the actual PLC type, this may affect the PLC Type dependent items.

The PLC type selected does not match the actual connected PLC.

Either the wrong PLC type is selected or the specified host name is wrong.

Select the correct setting and re-start the server.

Reply Timeout is hot-configured to <new_value> millisecs for PLC node '<plc_name>'.

The Reply Timeout parameter is changed while server is running.

You changed the parameter.The change takes effect immediately.

N/A

Connection Timeout is hot-configured to <new_value> millisecs for PLC node '<plc_name>.

The Connection Timeout parameter is changed while server is running.

You changed the parameter. The change takes effect immediately.

N/A

Max outstanding messages is hot-configured to <new_value> messages for PLC node '<plc_name>'.

The Max outstanding messages parameter os changed while server is running.

You changed the parameter. The change takes effect immediately.

N/A

Program Name is hot-configured to <new_value> for PLC node '<plc_name>'.

The Program Name parameter is changed while server is running.

You changed the parameter. The change takes effect immediately.

N/A

Value of attribute '<attribute_name>' for PLC node '<plc_name>' has changed - Need to restart the server to make the changed value affective.

The attribute is changed while the server is running and the attribute is not hot configurable.

The value change does not go into effect until the server is restarted.

Restart the server.

'<item_name>' is not a valid item name for this PLC<plc_name>.

The item is not supported by the connected PLC.

The wrong item name was specified.

Specify the correct item name.

Read value of element <register_number> in the Item:'<item_name>'is clamped to BCD value 9999.

The value of the register in the register array is clamped to 9999 BCD value.

The BCD limit was reached.

N/A

ServiceRequest code didn't not match the Code:<service_code>,while updating the data to items.

The service request code did not match the supported items service request code in the response packet.

N/A

If the problem persists, contact Technical Support.

Program Name in the PLC<plc_name> is not matching with the Program Name configured in the PLC faceplate; Hence %P and %L items can't be accessed.

The configured program name does not match the program name running in the PLC.

The wrong program name was specified.

Change (hot configure) the program name.

Mixed Suffix: It is not allowed to mix suffix M with suffix A(Register Array).

An unsupported suffix combination is used.

Suffix M and A are used for a single item. This is not supported.

Un-advise the item.

Mixed Suffix: It is not allowed to mix more than one suffix with suffix A(Register Array).

An unsupported suffix combination is used.

More than one suffix is used with suffix A while advising an item as a register array. This is not supported.

Un-advise the item.

Mixed Suffix: Multiple suffixes to an item are not allowed except with suffix A(Register Array).

An unsupported suffix combination is used.

More than one suffix is used while advising an item and one of the suffixes is not suffix A.

Un-advise the item.

Sub-ProgramName supplied along with %L is not a valid name.

The sub-program name is wrong.

N/A

Check the PLC program and correctly specify the sub-program name.

Item <item_name> cannot be added to the PLC <plc_name> due to invalid range, valid range is between 1 to 65535.

The item could not be advised to the PLC because it is not supported by the PLC.

Either the wrong syntax or an invalid range is specified while advising an item.

Check the valid syntax and ranges of the items supported by the PLC.

Invalid suffix type for ASCII string or Register array type item.

The suffixes specified for the ASCII string or register array items are wrong.

Invalid suffixes are applied for the items.

For a detailed explanation of the items advised with suffixes, see the item reference in this documentation.

Item <item_name> cannot be added to the PLC <plc_name>, because range specified are not registers.

The array registers specified are not valid registers.

The array registers specified are not valid registers.

Advise the item with correct registers.

Item:<item_name> cannot be added, Range specified is more than <packet_size>.

The register array or ASCII item specified is more than the protocol limit data size.

The protocol packet limit is exceeded for the advised item.

Advise the item within the supported limit.

Sub-BlockName for the %L item cannot be more than eight characters.

The wrong sub-block specified is.

The sub-block name specified in the item syntax does not match the sub-block constraints.

Check the sub-block naming constraints in the item reference.

Not a valid bit specification in advising Item as discrete, please specify a valid bit number between 0 and 15.

An invalid bit specification is specified.

An invalid bit specification is specified.

Check the item syntax. The valid bit specification to read is from 0 to 15.

Item <item_name> cannot be added as the Item name is invalid for PLC<plc_name>.

The item specified is not supported by the PLC in advise.

An invalid item is advised to the PLC.

Check the item syntax.

PLC Fault Number is out-of-range, please specify valid PLC fault number between 1 and 16.

The PLC fault table fault number advised is not supported.

The PLC fault table fault number advised is not supported.

Retry with a valid fault number. The supported PLC faults range from 1 to 16.

IO Fault number is out-of-range, please specify the valid IO fault number between 1 and 32.

The IO fault table fault number advised is not supported.

The IO fault table fault number advised is not supported.

Retry with a valid fault number. The supported IO faults range from 1 to 32.

Item <item_name> cannot be added to the PLC <plc_name>, Invalid system item.

An invalid system item is advised.

An invalid system item is advised.

Retry with correct item syntax.

Invalid item name <item_name> for the PLC <plc_name>, Unknown Memory Type.

An unknown item type is advised.

An item type unknown by the server is advised.

Retry with correct item syntax.

Specifying bit position is not valid for boolean items.

A Boolean item is advised for a specific bit position.

It is not allowed to read the bit positions in the Boolean items.

Retry with correct item syntax.

No suffix is allowed with boolean Items.

A Boolean item is advised with a suffix.

Boolean items do not support the item suffixes.

Check the suffix constraints specified in this documentation.

Sub-BlockName for %L items cannot be more than eight characters or NULL.

The specified sub-block is wrong.

The sub-block name specified in the item syntax does not match the sub-block constraints.

Check the sub-block naming constraints in the item reference in this documentation.

Sub-Block Name for %L item provided is more than eight characters.

The specified sub-block is wrong.

The sub-block name specified in the item syntax does not match the sub-block constraints.

Check the sub-block naming constraints in the item reference in this documentation.

Poke value to the item '<register_no>' is clamped to <clamped_val>(<actual_val>).

The Modulo-10000 point output value overflowed. The value is clamped.

The Modulo-10000 value written to the PLC exceeded the maximum limit.

The client must write a smaller value.

Poke value to item '<item_name>' is clamped to BCD value 9999(<Poked_value>)

The Modulo-10000 point output value overflowed. The value is clamped.

The Modulo-10000 value written to the PLC exceeded the maximum limit.

The client must write a smaller value.

Poke value to item '<item_name>' is clamped to value <clamped_value>(<poked_value>).

The Modulo-10000 point output value overflowed. The value is clamped.

The Modulo-10000 value written to the PLC exceeded the maximum limit.

The client must write a smaller value.

Poke value to element <register_number> of item '<item_name>' is clamped to value <clamped_value>(<poked_value>).

The Modulo-10000 point output value overflowed. The value is clamped.

The Modulo-10000 value written to the PLC exceeded the maximum limit.

The client must write a smaller value.

Poke value to element <register_number> of item '<item_name>' is clamped to BCD value 9999(<poked_value>).

The Modulo-10000 point output value overflowed. The value is clamped.

The Modulo-10000 value written to the PLC exceeded the maximum limit.

The client must write a smaller value.

Number of values poked to array item '<item_name>' exceeds its size, hence limited to <clamped_value>(<poked_value>).

The values poked to an item exceeded the size of the array item. The value is clamped.

Too many values were poked to an array item.

N/A

Poke value to the item :'<item_name>' is clamped <clamped_val>(<actual_val>).

The value poked to an item exceeds its capacity. The value is clamped.

A value larger than the data type was poked.

Poke a value within the valid range.

%P item is supported by 'Series 9070' PLCs only. Hence item <item_name> cannot be added to PLC<plc_name>

%P item is advised to an unsupported PLC type.

%P and %L items are supported only by Series 90-70 PLCs

Advise the items %P and %L to Series 90-70 PLCs.

%L item is supported by 'Series 9070' PLCs only. Hence item <item_name> cannot be added to PLC<plc_name>

%L item is advised to an unsupported PLC type.

%P and %L items are supported only by Series 90-70 PLCs

Advise the items %P and %L to Series 90-70 PLCs.

DASReceive Messages

Data socket handling reply '%s

This is a data reply from the Read socket.

N/A

N/A

DASSend Messages

Unsolicited response send() - operation not complete, wait for event

The socket Write operation for the unsolicited message fails to complete.

The Send operation fails to complete.

Wait for the Send event to complete.

Unsolicited response send() - WSAGetLastError = %d

The socket Write operation for the unsolicited message fails.

The acknowledgement packet for the unsolicited message cannot be sent.

Check the network connection. If the problem persists, contact Technical Support.

Info Messages

Re-trying connection for the PLC:<plc_name> after slowpoll interval.

The PLC connection failed, so a retry occurs after the specified slow poll interval.

The connection to the PLC failed.

Wait for the connection until the server comes out of slow poll mode.