Communication driver error messages

"CoilRead" is missing from the DASMBTCP.AAcfg file under <PLC name>.

The mandatory <CoilRead> field is absent from the DeviceNode named <PLC Name> in the configuration file.

The entry is deleted from the file manually.

Use the OI Server Manager to rebuild the file.

DASProtFail

"CoilWrite" is missing from the DASMBTCP.AAcfg file under <PLC name>.

The mandatory <CoilWrite> field is absent from the DeviceNode named <PLC Name> in the configuration file.

The entry is deleted from the file manually.

Use the OI Server Manager to rebuild the file.

DASProtFail

"ExtendedRegisterRead" is missing from the DASMBTCP.AAcfg file under <PLC name>.

The mandatory <ExtendedRegisterRead> field is absent from the DeviceNode named <PLC Name> in the configuration file.

The entry is deleted from the file manually.

Use the OI Server Manager to rebuild the file.

DASProtFail

"ExtendedRegisterWrite" is missing from the DASMBTCP.AAcfg file under <PLC name>.

The mandatory <ExtendedRegisterWrite> field is absent from the DeviceNode named <PLC Name> in the configuration file.

The entry is deleted from the file manually.

Use the OI Server Manager to rebuild the file.

DASProtFail

"HoldingRegisterRead" is missing from the DASMBTCP.AAcfg file under <PLC name>.

The mandatory <HoldingRegisterRead> field is absent from the DeviceNode named <PLC Name> in the configuration file.

The entry is deleted from the file manually.

Use the OI Server Manager to rebuild the file.

DASProtFail

"HoldingRegisterWrite" is missing from the DASMBTCP.AAcfg file under <PLC name>.

The mandatory <HoldingRegisterWrite> field is absent from the DeviceNode named <PLC Name> in the configuration file.

The entry is deleted from the file manually.

Use the OI Server Manager to rebuild the file.

DASProtFail

"InputRegisterRead" is missing from the DASMBTCP.AAcfg file under <PLC name>.

The mandatory <InputRegisterRead> field is absent from the DeviceNode named <PLC Name> in the configuration file.

The entry is deleted from the file manually.

Use the OI Server Manager to rebuild the file.

DASProtFail

"IPAddress" is missing from the DASMBTCP.AAcfg file under <PLC name>.

The mandatory <IPAddress> field is absent from the DeviceNode named <PLC Name> in the Configuration file.

The entry is deleted from the file manually.

Use the OI Server Manager to build the file.

DASProtFail

"MaxAddrExtendedRegisters" is missing from the DASMBTCP.AAcfg file under <PLC name>.

The mandatory <MaxAddrExtendedRegisters> field is absent from the DeviceNode named <PLC Name> in the configuration file.

The entry is deleted from the file manually.

Use the OI Server Manager to rebuild the file.

DASProtFail

"MaxAddrHoldingRegisters" is missing from the DASMBTCP.AAcfg file under <PLC name>.

The mandatory <MaxAddrHoldingRegisters> field is absent from the DeviceNode named <PLC Name> in the configuration file.

The entry is deleted from the file manually.

Use the OI Server Manager to rebuild the file.

DASProtFail

"MaxAddrInputRegisters" is missing from the DASMBTCP.AAcfg file under <PLC name>.

The mandatory <MaxAddrInputRegisters> field is absent from the DeviceNode named <PLC Name> in the configuration file.

The entry is deleted from the file manually.

Use the OI Server Manager to rebuild the file.

DASProtFail

"MaxAddrReadCoils" is missing from the DASMBTCP.AAcfg file under <PLC name>.

The mandatory <MaxAddrReadCoils> field is absent from the DeviceNode named <PLC Name> in the configuration file.

The entry is deleted from the file manually.

Use the OI Server Manager to rebuild the file.

DASProtFail

"MaxAddrWriteCoils" is missing from the DASMBTCP.AAcfg file under <PLC name>.

The mandatory <MaxAddrWriteCoils> field is absent from the DeviceNode named <PLC Name> in the configuration file.

The entry is deleted from the file manually.

Use the OI Server Manager to rebuild the file.

DASProtFail

"MaxQueuedMsgs" is missing from the DASMBTCP.AAcfg file under <PLC name>.

The mandatory <MaxQueuedMsgs> field is absent from the DeviceNode named <PLC Name> in the configuration file.

The entry is deleted from the file manually.

Use the OI Server Manager to rebuild the file.

DASProtFail

"RegisterSize" is missing from the DASMBTCP.AAcfg file under <PLC name>.

The mandatory <RegisterSize> field is absent from the DeviceNode named <PLC Name> in the configuration file.

The entry is deleted from the file manually.

Use the OI Server Manager to rebuild the file.

DASProtFail

"RegisterType" is missing from the DASMBTCP.AAcfg file under <PLC name>.

The mandatory <RegisterType> field is absent from the DeviceNode named <PLC Name> in the configuration file.

The entry is deleted from the file manually.

Use the OI Server Manager to rebuild the file.

DASProtFail

"ReplyTimeout" is missing from the DASMBTCP.AAcfg file under <PLC name>."

The mandatory <ReplyTimeout> field is absent from the DeviceNode named <PLC Name> in the Configuration file.

The entry is deleted from the file manually.

Use the OI Server Manager to build the file.

DASProtFail

"StringVariableStyle" is missing from the DASMBTCP.AAcfg file under <PLC name>.

The mandatory <StringVariableStyle> field is absent from the DeviceNode named <PLC Name> in the configuration file.

The entry is deleted from the file manually.

Use the OI Server Manager to rebuild the file.

DASProtFail

"UnitID" is missing from the DASMBTCP.AAcfg file under <PLC name>.

The mandatory <UnitID> field is absent from the DeviceNode named <PLC Name> in the Configuration file.

The entry is deleted from the file manually.

Use the OI Server Manager to build the file.

DASProtFail

"UseLongConceptDataStruct" is missing from the DASMBTCP.AAcfg file under <PLC name>.

The mandatory <UseLongConceptDataStruct> field is absent from the DeviceNode named <PLC Name> in the configuration file.

The entry is deleted from the file manually.

Use the OI Server Manager to rebuild the file.

DASProtFail

"UseRealConceptDataStruct" is missing from the DASMBTCP.AAcfg file under <PLC name>.

The mandatory <UseRealConceptDataStruct> field is absent from the DeviceNode named <PLC Name> in the configuration file.

The entry is deleted from the file manually.

Use the OI Server Manager to rebuild the file.

DASProtFail

<PLC Name> does not allow extended register <Item name>.

The PLC does support extended registers.

The client defined an extended register and it is not supported.

Remove extended register from client.

DASProtFail

<PLC Name>: Clamping a write to <Item Name> - Received <client value>, writing <clamped value>.

The client wrote a value that exceeded the item limits.

The client wrote an invalid value.

The client must write a smaller value.

DASProtWarn

An invalid floating point value was returned by the PLC for item name <PLC Name>.<Item Name>. The value was converted to a negative 3.4e38.

Invalid floating-point number (Negative Infinity). Set the item value to Negative Infinity 3.4e+38.

The values read from the PLC registers cannot be converted to a valid float number.

Check the PLC for the value in the registers.

DASProtFail

An invalid floating point value was returned by the PLC for item name <PLC Name>.<Item Name>. The value was converted to a positive 3.4e38.

Invalid floating-point number (Positive Infinity). Set the item value to Positive Infinity 3.4e+38.

The values read from the PLC registers cannot be converted to a valid float number.

Check the PLC for the value in the registers.

DASProtFail

Connection to PLC <PLC name> at IP Address <Host name> closed, error code = <Error code>.

The PLC closed the connection.

The PLC may be having problems.

Check the PLC.

DASProtFail

CreateItem failed <PLC name>.<Item Name>.

The server encountered an invalid item name.

An invalid item name was defined by the client.

Correct the item name defined by the client.

DASProtFail

CreateItem failed due to invalid item name <PLC name>.<Item Name>.

The server encountered an invalid item name.

The client defined an invalid item name.

The client must define a valid item name.

DASProtFail

DASMBTCP failed to allocate memory.

The server could not allocate memory to continue operating.

Too many items have been defined by client or too many programs are running in this PC.

Stop unwanted programs, define less points by client, or add more memory to the PC.

DASProtFail

DASMBTCPPLCSocket::OnSocketRead(1) failed with errorcode <Error code>.

The PLC returned an error code on a request for data.

The PLC may be having problems.

Check the PLC.

DASProtFail

DASMBTCPPLCSocket::OnSocketRead(2) failed with errorcode <Error code>.

The PLC returned an error code on a request for data.

The PLC may be having problems.

Check the PLC.

DASProtFail

DASMBTCPPLCSocket::OnSocketRead(3) failed with errorcode <Error code>.

The PLC returned an error code on a request for data.

The PLC may be having problems.

Check the PLC.

DASProtFail

DASMBTCPPLCSocket::OnSocketWrite failed with errorcode <Error code>.

The PLC returned an error code on a write to PLC command.

The PLC may be having problems.

Check the PLC.

DASProtFail

Error in Reading from PLC for item <PLC name>.<Item Name>.

The PLC returned an exception.

The PLC may be having problems.

Check the PLC.

DASProtFail

Error in Writing to PLC for item <PLC name>.<Item Name>.

The PLC returned an exception.

The PLC may be having problems.

Check the PLC.

DASProtFail

Fail to Connect to PLC <PLC name> at IP Address <Host name>, error code = <Error code>.

The host name used in the IP Address field is invalid.

Invalid IP Address was configured.

A valid host name or IP Address must be configured.

DASProtFail

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

The host name used in the IP Address field is invalid.

Invalid IP Address was configured.

A valid host name or IP Address must be configured.

DASProtFail

Failed to split the message from ReceiveBuffer for Sequence Number <Sequence Number>, message possibly revoked.

A message returned by the PLC was not found in the requested messages queue.

The message may have timed out and was removed from the queue.

Increase the ReplyTimeout timer.

DASProtFail

Invalid value read for Mod 10000 register: <Item Name> on Node: <PLC Name>. Not a valid BCD-value. Convert to 2147483647.

The Modulo-10000 point value overflows. The value is clamped to 2147483647 to indicate overflow condition.

The maximum usable value represented in three Modulo-10000 registers is 2,147,483,646.

Check the PLC for the value in the registers.

DASProtWarn

Read value beyond limits for Mod 10000 register: <Item Name> on Node: <PLC Name>. Value clamped to 9999.

The Modulo-10000 point value overflows. The value is clamped to 9999.

The maximum usable value represented in one Modulo-10000 registers is 9999.

Check the PLC for the value in the registers.

DASProtWarn

recv() failed with errorcode <Error Code>.

The PLC responded with an error.

The PLC may be down or there is a communications problem.

Check the PLC and the communications link.

DASProtFail

Register Type is ’BCD’. Value clamped to 9999.

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

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

The client must write a smaller value.

DASProtWarn

Register Type is hot-configured to <Register type>.

The Register Type parameter was modified at run time.

The user modified the Register Type parameter while the server was running.

The Register Type parameter can be modified at run time.

DASProtWarn

Reply Timeout is hot-configured to <Reply timeout value>.

The Reply Timeout parameter was modified at run time.

The user modified the Reply Timeout parameter while the server was running.

The Reply Timeout parameter can be modified at run time.

DASProtWarn

String Variable Style is hot-configured to <String variable style>.

The String Variable Style parameter was modified at run time.

The user modified the String Variable Style parameter while the server was running.

The String Variable Style parameter can be modified at run time.

DASProtWarn

The item name <PLC Name>.<Item Name> is Invalid. It is non-numeric.

The item name is invalid.

A non-numeric register was defined where numeric was required.

Make register a numeric register.

DASProtFail

The item name <PLC Name>.<Item Name> is invalid. The bit number is invalid.

The item name has an invalid bit number.

The client defined an item with an invalid bit number.

The item bit number must be between 1 (one) and 16.

DASProtFail

The item name <PLC Name>.<Item Name> is invalid. The bit number is out of range.

The item name has an invalid bit number.

The client defined an item with an invalid bit number.

The item bit number must be between 1 (one) and 16.

DASProtFail

The item name <PLC Name>.<Item Name> is invalid. The data type is invalid.

The server encountered an invalid data type.

The client defined a data type not supported by the server.

The client must use a valid data type.

DASProtFail

The item name <PLC Name>.<Item Name> is invalid. The register range is invalid.

The Modulo-10000 item defined by the client exceeds the 3 register limit.

The client defined an invalid item name.

The client must use two or three registers when defining Modulo-10000 item names.

DASProtFail

The item name <PLC Name>.<Item Name> written string value <String Value> was truncated to <Truncated String Value>. Not enough registers were defined to hold the string value.

The server truncated the string being written to the PLC.

Not enough registers were defined by the client to hold the string data being written.

Add more registers or write less data.

DASProtFail

The PLC <PLC Name> message timed out (OnPLCReceiverTimeout), revoking message <Message ID>.

The server did not get a response from the PLC in the <ReplyTimeout> allotted time.

The PLC is offline or the data request has an invalid register number obtained from the configuration file.

Check PLC's network connection or configuration file.

DASProtFail

The PLC <PLC name> reported receiving an ILLEGAL FUNCTION code from the OI Server. PLC errorcode 01.

The function code received in the query is not an allowable action for the slave.

This may be because the function code is only applicable to newer controllers, and was not implemented in the unit selected. It could also indicate that the slave is in the wrong state to process a request of this type; for example, because it is unconfigured and is being asked to return register values.

Check the item definition and PLC configuration.

DASProtFail

The PLC <PLC name> reported receiving an ILLEGAL DATA ADDRESS from the OI Server. PLC errorcode 02.

The data address received in the query is not an allowable address for the slave.

The item address is out of the configured-slave address range, or the combination of reference number and transfer length is invalid. For a controller with 100 registers, a request with offset 96 and length 4 would succeed, a request with offset 96 and length 5 will generate exception 02.

Check the item definition and PLC configuration.

DASProtFail

The PLC <PLC name> reported receiving an ILLEGAL DATA VALUE from the OI Server. PLC errorcode 03.

A value contained in the query data field is not an allowable value for the slave.

This indicates a fault in the structure of the remainder of a complex request. For example, the implied length is incorrect.

Check the data value sent to the PLC.

DASProtFail

The PLC <PLC name> reported ILLEGAL RESPONSE LENGTH while working on the current request. PLC errorcode 04.

An unrecoverable error occurred while the slave was attempting to perform the requested action.

Indicates that the request as framed would generate a response whose size exceeds the available MODBUS data size.

Check the PLC.

DASProtFail

The PLC <PLC name> reported ACKNOWLEDGE while working on the current request. PLC errorcode 05.

The slave has accepted the request and is processing it, but a long duration of time will be required to do so.

This response is returned to prevent a timeout error from occurring in the client (or master).

Check the PLC.

DASProtFail

The PLC <PLC name> reported SLAVE DEVICE BUSY and cannot process the current request. PLC errorcode 06.

The slave is engaged in processing a long-duration program command.

The PLC program is taking too long to respond to the OI Server.

Check the PLC.

DASProtFail

The PLC <PLC name> reported NEGATIVE ACKNOWLEDGE and cannot process the current request. PLC errorcode 07.

The slave cannot perform the program function received in the query.

The communications data is corrupted or a OI Server problem is encountered.

Check the PLC.

DASProtFail

The PLC <PLC name> reported MEMORY PARITY ERROR while attempting to read extended memory. PLC errorcode 08.

The slave attempted to read extended memory, but detected a parity error in the memory.

The PLC may need to be serviced.

Check the PLC's extended memory.

DASProtFail

The PLC <PLC name> reported GATEWAY PATH UNAVAILABLE while attempting to read extended memory. PLC errorcode 0A.

Specialized use in conjunction with gateways; it indicates that the gateway was unable to allocate a Modbus Plus PATH to use to process the request.

It usually means that the gateway is misconfigured.

Check the Bridge connected to the PLC.

DASProtFail

The PLC <PLC name> reported GATEWAY TARGET DEVICE FAILED TO RESPOND while attempting to read extended memory. PLC errorcode 0B.

Specialized use in conjunction with gateways; it indicates that no response was obtained from the target device.

It usually means that the device is not present on the network.

Check the Bridge connected to the PLC.

DASProtFail

The PLC <PLC name> reported unknown exception code. PLC errorcode <Error Number>.

The PLC returned an unknown error code.

The communications data is corrupted.

Check the PLC.

DASProtFail

The property RegisterSize value <Value> is invalid for PLC <PLC Name>.

The RegisterSize value in the configuration file is invalid.

The entry in the file was modified manually.

Use the OI Server Manager to rebuild the file.

DASProtFail

The register number for the item name <PLC name>.<Item Name> exceeds the configured PLC Maximum Addressable Registers.

The register defined by the client is out of range compared to the maximum addressable register number.

The client defined an invalid register number.

Client must use a register number less than or equal to the configured maximum addressable register.

DASProtFail

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

The connection to the PLC failed.

The PLC or the network may be having problems.

Check the PLC or the network.

DASProtFail

The write Item <Item Name> is invalid. The item is a read only item.

The register being written to is a read-only register.

The client is writing to a read-only register.

Select a different register.

DASProtFail

Write attempt beyond limits for Mod 10000 register: <Item Name> on Node: <PLC Name>. Value clamped to <new value>.

The output value was clamped to a predefined value because the output value exceeded certain limits.

The client wrote a value to the PLC that was too large for the register.

The client must write a smaller value.

DASProtFail