Event Log Messages
Internal error occurred while attempting to write tag. Unexpected data type. | Tag address = '<address>', Data type = '<type>', DTRV = <code>.
Error Type:
Error
The following errors occurred uploading controller project from device. Resorting to symbolic protocol.
Error Type:
Error
Possible Cause:
The device returned an error within the CIP portion of the Ethernet/IP packet during an automatic tag generation request.
Possible Solution:
The solution depends on the error codes returned.
See Also:CIP Error Codes
Unknown error occurred.
Error Type:
Error
Low memory resources.
Error Type:
Error
Invalid or corrupt controller project detected while synchronizing. Synchronization will be retried shortly.
Error Type:
Error
Project download detected while synchronizing. Synchronization will be retried shortly.
Error Type:
Error
Encapsulation error occurred while uploading project information. | Encapsulation error = <code>.
Error Type:
Error
Possible Cause:
The device returned an error within the encapsulation portion of the Ethernet/IP packet during an automatic tag generation request.
Possible Solution:
The driver attempts to recover from this error.
Note:This excludes error 0x02, which is device-related and not driver-related.
Error occurred while uploading project information. | CIP error = <code>, Extended error = <code>.
Error Type:
Error
Possible Cause:
The device returned an error within the CIP portion of the Ethernet/IP packet during an automatic tag generation request.
Possible Solution:
The solution depends on the error codes returned.
See Also:CIP Error Codes
Framing error occurred while uploading project information.
Error Type:
Error
Possible Cause:
1. The packets are misaligned due to the connection or disconnection between the PC and device.
2. There is bad cabling connecting the device causing noise.
Possible Solution:
1. Place the device on less noisy network.
2. Increase the Request Timeout and/or Request Attempts.
CIP connection timed-out while uploading project information.
Error Type:
Error
Database error. CIP connection timed-out while uploading project information.
Error Type:
Error
Database error. Error occurred while uploading project information. | CIP error = <code>, Extended error = <code>.
Error Type:
Error
Possible Cause:
The device returned an error within the CIP portion of the Ethernet/IP packet during an automatic tag generation request.
Possible Solution:
The solution depends on the error codes returned.
See Also:CIP Error Codes
Database error. Encapsulation error occurred during register session request. | Encapsulation error = <code>.
Error Type:
Error
Database error. Framing error occurred during register session request.
Error Type:
Error
Possible Cause:
The device returned an error within the encapsulation portion of the Ethernet/IP packet during an automatic tag generation request.
Possible Solution:
The driver attempts to recover from this error.
Note:This excludes error 0x02, which is device-related and not driver-related.
See Also:Encapsulation Error Codes
Database error. Internal error occurred.
Error Type:
Error
Database error. Encapsulation error occurred during fwd. open request. | Encapsulation error = <code>.
Error Type:
Error
Possible Cause:
The device returned an error within the encapsulation portion of the Ethernet/IP packet during an automatic tag generation request.
Possible Solution:
The driver attempts to recover from this error.
Note:This excludes error 0x02, which is device-related and not driver-related.
See Also:Encapsulation Error Codes
Database error. No more connections available for fwd. open request.
Error Type:
Error
Possible Cause:
Omron devices support a finite number of connections. The connection limit has been exceeded.
Possible Solution:
Reduce the number of connections from the servers to the device and try again.
Database error. Error occurred during fwd. open request. | CIP error = <code>, Extended error = <code>.
Error Type:
Error
Possible Cause:
Omron devices support a finite number of connections. The connection limit has been exceeded.
Possible Solution:
Reduce the number of connections from the servers to the device and try again.
Database error. Framing error occurred during fwd. open request.
Error Type:
Error
Possible Cause:
1. The packets are misaligned due to the connection and/or disconnection between the PC and device.
2. There is bad cabling connecting the device causing noise.
Possible Solution:
1. Place the device on less noisy network.
2. Increase the Request Timeout and/or Request Attempts.
Database error. Encapsulation error occurred while uploading project information. | Encapsulation error = <code>.
Error Type:
Error
Possible Cause:
The device returned an error within the encapsulation portion of the Ethernet/IP packet during an automatic tag generation request.
Possible Solution:
The driver attempts to recover from this error.
Note:This excludes error 0x02, which is device-related and not driver-related.
See Also:Encapsulation Error Codes
Database error. Framing error occurred while uploading project information.
Error Type:
Error
Possible Cause:
1. The packets are misaligned due to the connection and/or disconnection between the PC and device.
2. There is bad cabling connecting the device causing noise.
Possible Solution:
1. Place the device on less noisy network.
2. Increase the Request Timeout and/or Request Attempts.
Frame received from device contains errors.
Error Type:
Warning
Possible Cause:
1. The packets are misaligned due to connection and/or disconnection between the PC and device.
2. There is bad cabling connecting the device causing noise.
Possible Solution:
1. Place the device on less noisy network.
2. Increase the Request Timeout and/or Attempts.
Error occurred during a request to device. | CIP error = <code>, Extended error = <code>.
Error Type:
Warning
Possible Cause:
The device returned an error within the CIP portion of the Ethernet/IP packet during a request. All reads and writes within the request failed.
Possible Solution:
The solution depends on the error codes returned.
See Also:CIP Error Codes
Write request for tag failed due to a framing error. | Tag address = '<address>'.
Error Type:
Warning
Possible Cause:
1. A write request for the specified tag failed after so many retries due to an incorrect request service code.
2. A write request for the specified tag failed after so many retries because more or fewer bytes than expected were received.
Possible Solution:
If this error occurs frequently, there may be an issue with the cabling or device. Increasing the retry attempts allows more opportunities to recover from this error.
Read request for tag failed due to a framing error. | Tag address = '<address>'.
Error Type:
Warning
Possible Cause:
1. Incorrect request service code.
2. Received more or fewer bytes than expected.
3. There may be an issue with the cabling or device.
Possible Solution:
Increasing the Retry Attempts gives the driver more opportunities to recover from this error.
Block read request failed due to a framing error. | Block size = <number> (elements), Starting tag address = '<address>'.
Error Type:
Warning
Possible Cause:
1. The specified tag address and count failed due to an incorrect request service code.
2. The specified tag address and count failed because more or fewer bytes than expected were received.
Possible Solution:
If this error occurs frequently, there may be an issue with the cabling or the device itself. Increasing the request attempts allows more opportunities to recover from this error. In response to this error, the elements of the block are deactivated and it is not processed again.
Block read request failed due to a framing error. | Block Size = <number> (bytes), Tag Name = '<tag>'.
Error Type:
Warning
Possible Cause:
1. The specified tag address and count failed due to an incorrect request service code.
2. The specified tag address and count failed because more or fewer bytes than expected were received.
Possible Solution:
If this error occurs frequently, there may be an issue with the cabling or the device itself. Increasing the request attempts allows more opportunities to recover from this error. In response to this error, the elements of the block are deactivated and it is not processed again.
Unable to write to tag. | Tag address = '<address>', CIP error = <code>, Extended error = <code>.
Error Type:
Warning
Possible Cause:
1. The Ethernet connection between the device and the host PC is broken.
2. The communication parameters for the Ethernet connection are incorrect.
3. The named device may have been assigned an incorrect IP address.
Possible Solution:
1. Verify the cabling between the PC and the device.
2. Verify that the correct port has been specified for the named device.
3. Verify that the IP address given to the named device matches that of the actual device.
Unable to read tag. | Tag address = '<address>', CIP error = <code>, Extended error = <code>.
Error Type:
Warning
Possible Cause:
The device returned an error within the CIP portion of the Ethernet/IP packet during a read request for the specified tag.
Possible Solution:
The solution depends on the error codes returned.
See Also:CIP Error Codes
Unable to read block on device. | Block Size = <number> (elements), Starting Tag address = '<address>', CIP error = <code>, Extended error = <code>.
Error Type:
Warning
Possible Cause:
The device returned an error within the CIP portion of the Ethernet/IP packet during a read request for the specified tag.
Possible Solution:
The solution depends on the error codes returned.
See Also:CIP Error Codes
Unable to read block on device. | Block size = <number> (bytes), Tag name = '<tag>', CIP error = <code>, Extended error = <code>.
Error Type:
Warning
Possible Cause:
The device returned an error within the CIP portion of the Ethernet/IP packet during a read request for the specified tag.
Possible Solution:
The solution depends on the error codes returned.
See Also:CIP Error Codes
Unable to write to tag. Controller tag data type unknown. | Tag address = '<address>', Data type = <type>.
Error Type:
Warning
Possible Cause:
A read request for the specified tag failed because the variable data type is not supported.
Possible Solution:
Remove references to this variable. In response to this error, the tag is deactivated and not processed again.
Unable to read tag. Controller tag data type unknown. Tag deactivated. | Tag address = '<address>', Data type = <type>.
Error Type:
Warning
Possible Cause:
A read request for the specified tag failed because the variable data type is not supported.
Possible Solution:
Remove references to this variable. In response to this error, the tag is deactivated and not processed again.
Unable to read block on device. Controller tag data type unknown. Tag deactivated. | Block Size = <number> (elements), Starting tag address = '<address>', Data type = <type>.
Error Type:
Warning
Possible Cause:
A read request for the specified tag failed because the variable data type is not supported.
Possible Solution:
Remove references to this variable. In response to this error, the block is deactivated and not processed again.
Unable to write to tag. Data type not supported. | Tag address = '<address>', Data type = '<type>'.
Error Type:
Warning
Possible Cause:
A write request for the specified tag failed because the client tag data type is not supported.
Possible Solution:
Change the tag data type to one that is supported and try again.
Unable to read tag. Data type not supported. Tag deactivated. | Tag address = '<address>', Data type = '<type>'.
Error Type:
Warning
Possible Cause:
A read request for the specified tag failed because the client tag data type is not supported.
Possible Solution:
Change the tag data type to one that is supported. In response to this error, the tag is deactivated and will not be processed again.
Unable to read block on device. Data type not supported. Block deactivated. | Block size = <number> (elements), Starting tag address = '<address>', Data type = '<type>'.
Error Type:
Warning
Possible Cause:
A read request for the specified tags to the specified tag address and count failed because the client tag data type is not supported.
Possible Solution:
Change the data type for tags within this block to supported types. In response to this error, elements of the block are deactivated and will not be processed again.
Unable to write to tag. Data type is illegal for this tag. | Tag address = '<address>', Data type = '<type>'.
Error Type:
Warning
Possible Cause:
A write request for the specified tag failed because the client tag data type is illegal for the given variable.
Possible Solution:
Change the tag data type to one that is supported.
See Also:Data Type Coercion
Unable to read tag. Data type is illegal for this tag. | Tag address = '<address>', Data type = '<type>'.
Error Type:
Warning
Possible Cause:
A read request for the specified tag failed because the client's tag data type is illegal for the given variable.
Possible Solution:
Change the tag data type to one that is supported.
See Also:Data Type Coercion
Unable to read block on device. Data type is illegal for this block. | Block size = <number> (elements), Starting tag address = '<address>', Data type = '<type>'.
Error Type:
Warning
Possible Cause:
A read request for the specified tag failed because the client tag data type is illegal for the given variable.
Possible Solution:
Change the tag data type to one that is supported.
See Also:Data Type Coercion
Unable to write to tag. Tag does not support multi-element arrays. | Tag address = '<address>'.
Error Type:
Warning
Possible Cause:
A write request for the specified tag failed because the driver does not support multi-element array access to the given variable.
Possible Solution:
Change the tag data type or address to one that is supported.
Unable to read tag. Tag does not support multi-element arrays. Tag deactivated. | Tag address = '<address>'.
Error Type:
Warning
Possible Cause:
A read request for the specified tag failed because the driver does not support multi-element array access to the given variable.
Possible Solution:
Change the tag data type or address to one that is supported. In response to this error, the tag is deactivated and will not be processed again.
Unable to read block. Block does not support multi-element arrays. Block deactivated. | Block size = <number> (elements), Starting tag address = '<address>'.
Error Type:
Warning
Possible Cause:
A read request for the specified tags to the specified tag address and count failed because the driver does not support multi-element array access to the given variable.
Possible Solution:
Change the data type or address for tags within this block to one that is supported. In response to this error, elements of the block are deactivated and will not be processed again.
Unable to write to tag. Native tag size mismatch. | Tag address = '<address>'.
Error Type:
Warning
Unable to read tag. Native tag size mismatch. | Tag address = '<address>'.
Error Type:
Warning
Unable to read block on device. Native tag size mismatch. | Block size = <number> (elements), Starting tag address = '<address>'.
Error Type:
Warning
Unable to read block on device. Native tag size mismatch. | Block size = <number> (bytes), Tag name = '<tag>'.
Error Type:
Warning
Unable to write to tag. | Tag address = '<address>'.
Error Type:
Warning
Possible Cause:
1. The Ethernet connection between the device and the host PC is broken.
2. The communication parameters for the Ethernet connection are incorrect.
3. The named device may have been assigned an incorrect IP address.
Possible Solution:
1. Verify the cabling between the PC and the device
2. Verify that the correct port has been specified for the named device.
3. Verify that the IP address given to the named device matches that of the actual device.
Unable to read tag. Tag deactivated. | Tag address = '<address>'.
Error Type:
Warning
Unable to read block. Block deactivated. | Block size = <number> (elements), Starting tag address = '<address>'.
Error Type:
Warning
Unable to read block on device. Block deactivated. | Block Size = <number> (bytes), Tag Name = '<tag>'.
Error Type:
Warning
Unable to read tag. Internal memory is invalid. | Tag address = '<address>'.
Error Type:
Warning
Unable to read tag. Data type is illegal for this tag. | Tag address = '<address>', Data type = '<type>'.
Error Type:
Warning
Possible Cause:
A read request for the specified tag failed because the client tag data type is illegal for the given variable.
Possible Solution:
Change the tag's data type to one that is supported.
See Also:Data Type Coercion
Unable to read block on device. Internal memory is invalid. Tag deactivated. | Tag address = '<address>'.
Error Type:
Warning
Unable to read block on device. Internal memory is invalid. Block deactivated. | Block size = <number> (elements), Starting tag address = '<address>'.
Error Type:
Warning
Unable to write to address. Internal memory is invalid. | Tag address = '<address>'.
Error Type:
Warning
Unable to read block on device. Block deactivated. | Block Size = <number> (elements), Starting Tag address = '<address>', CIP error = <code>, Extended error = <code>.
Error Type:
Warning
Device returned more data than expected while reading tag. Verify the address includes an element offset and all dimensions in that offset. | Tag address = '<address>'.
Error Type:
Warning
Possible Cause:
The tag address references an array variable, but not all dimensions were specified in the element offset or no element offset was specified. For example, the array variable "MyArray" is defined as ARRAY[0..2,0..9] OF INT. Creating a tag address like MyArray[0]{2}@Word Array may cause this error to occur because the second dimension is not specified. In this example, a read of the tag would result in 10 INTs returned versus the 2 INTs that are expected. Likewise, creating a tag address like MyArray@Word may cause this error to occur because neither the first nor second dimension was specified. In this example, a read of the tag would result in 30 INTs returned versus the 1 INT that is expected.
Possible Solution:
Add the fully-qualified element offset to the tag address. In the examples above, the correct tag address could be MyArray[0,0]{2} and MyArray[0,0] respectively.
Note:This message is only a warning. Reads succeed, but are less efficient because of the extra overhead in the read response. It is recommended that users fix tag addresses that exhibit this behavior.
Device returned more data than expected while reading block. Verify the address includes an element offset and all dimensions in that offset. | Block Size = <number> (elements), Starting Tag address = '<address>'.
Error Type:
Warning
Possible Cause:
The tag address references an array variable, but not all dimensions were specified in the element offset or no element offset was specified. For example, the array variable "MyArray" is defined as ARRAY[0..2,0..9] OF INT. Creating a tag address like MyArray[0]{2}@Word Array may cause this error to occur because the second dimension is not specified. In this example, a read of the tag would result in 10 INTs returned versus the 2 INTs that are expected. Likewise, creating a tag address like MyArray@Word may cause this error to occur because neither the first nor second dimension was specified. In this example, a read of the tag would result in 30 INTs returned versus the 1 INT that is expected.
Possible Solution:
Add the fully-qualified element offset to the tag address. In the examples above, the correct tag address could be MyArray[0,0]{2} and MyArray[0,0] respectively.
Note:This message is only a warning. Reads succeed, but are less efficient because of the extra overhead in the read response. It is recommended that users fix tag addresses that exhibit this behavior.
Unable to write to tag. Address exceeds current CIP connection size. | Tag address = '<address>'.
Error Type:
Warning
Possible Cause:
The tag address size resulted in a request frame that exceeds the protocol limits.
Possible Solution:
Increase the CIP Connection Size to a value that accommodates the tag request frame.
Unable to read block on device. Address exceeds current CIP connection size. | Block size = <number> (elements), Starting tag address = '<address>'.
Error Type:
Warning
Possible Cause:
The tag address size resulted in a request frame that exceeds the protocol limits.
Possible Solution:
Increase the CIP Connection Size to a value that accommodates the tag request frame.
Unable to read tag. Address exceeds current CIP connection size. | Tag address = '<address>'.
Error Type:
Warning
Possible Cause:
The tag address size resulted in a request frame that exceeds the protocol limits.
Possible Solution:
Increase the CIP Connection Size to a value that accommodates the tag request frame.
Requested CIP connection size is not supported by this device. Automatically falling back to maximum size. | Requested size = <number> (bytes), Maximum size = <number> (bytes).
Error Type:
Warning
Current value not supported for an XML element on this model. Automatically setting to new value. | Current value = '<value>', XML element = '{<namespace>}<element>', Model = '<model>', New value = '<value>'.
Error Type:
Warning
Database error. Data type of complex type is not supported. A tag for this member will not be added to the database. | Data type = <type>, Complex Type = '<type>', Member = '<name>'.
Error Type:
Warning
Possible Cause:
The device configuration of the complex type member uses an unsupported data type.
Possible Solution:
Modify the device configuration of the complex type member to use a supported data type.
See Also:Address Descriptions
Database error. Unable to resolve CIP data type for tag. Tag is not added to the database. | Data type = <type>, Tag name = '<tag>'.
Error Type:
Warning
Possible Cause:
1. A communications error occurred during automatic tag database generation that was caused by Ethernet encapsulation, the device, or framing.
2. The CIP data type is not supported by the driver.
Possible Solution:
1. Correct the communications error and retry automatic tag database generation.
2. Change the variable data type to one that is supported.
Database error. Address validation failed for tag. Tag is not added to the database. | Tag name = '<tag>', Tag address = '<address>'.
Error Type:
Warning
Possible Cause:
The tag address size exceeds the protocol limits.
Possible Solution:
Reduce the number of characters in the tag name. If the error persists, reduce the number of characters in the structure or union (including any nested structures or unions) under which the tag is located.
Unable to retrieve the identity for device. | Encapsulation error = <code>.
Error Type:
Warning
Possible Cause:
The identity was not retrieved because the device returned an error within the encapsulation portion of the Ethernet/IP packet during a request.
Possible Solution:
The driver attempts to recover from such an error.
Note:This excludes error 0x02, which is device-related, not driver-related.
See Also:Encapsulation Error Codes
Unable to retrieve the identity for device. | CIP error = <code>, Extended error = <code>.
Error Type:
Warning
Possible Cause:
The identity was not retrieved because the device returned an error within the CIP portion of the Ethernet/IP packet during a request.
Possible Solution:
The solution depends on the error code returned.
See Also:CIP Error Codes
Unable to retrieve the identity for device. Frame received contains errors.
Error Type:
Warning
Possible Cause:
1. The packets are misaligned due to connection and/or disconnection between the PC and device.
2. There is bad cabling connecting the devices causing noise.
3. The wrong frame size was received.
4. There is a TNS mismatch.
5. An invalid response command was returned from the device.
6. The device is not Ethernet/IP enabled.
Possible Solution:
1. The driver recovers from this error without intervention. There may be an issue with the cabling, the network, or the device itself.
2. Verify that the device being communicated with is an Omron Ethernet/IP-enabled device.
Encapsulation error occurred during a request. | Encapsulation error = <code>.
Error Type:
Informational
Possible Cause:
The device returned an error within the encapsulation portion of the Ethernet/IP packet during a request. All reads and writes within the request failed.
Possible Solution:
The driver attempts to recover from such an error.
Note:This excludes error 0x02, which is device-related, not driver-related.
See Also:Encapsulation Error Codes
Memory could not be allocated for tag. | Tag address = '<address>'.
Error Type:
Informational
Possible Cause:
Memory required for generation could not be allocated. The process is aborted.
Possible Solution:
Close any unused applications and/or increase the amount of virtual memory and try again.
Database error. Tag renamed because it exceeds maximum character length. | Tag name = '<tag>', Maximum length = <number>, New tag name = '<tag>'.
Error Type:
Informational
Database error. Array tags renamed because it exceeds max character length. | Array tag name = '<name>', Maximum length = <number>, New array tag name = '<name>'.
Error Type:
Informational
Database status: Tags imported. | Data types = <type>, Tags imported = <number>.
Error Type:
Informational
Database status: Generating OPC tags.
Error Type:
Informational
Database status: Building tag projects, please wait. | Tag project count = <number>.
Error Type:
Informational
Database status: Retrieving controller project.
Error Type:
Informational
Elapsed Time = <number> (seconds)
Error Type:
Informational
Symbolic Device Reads = <number>
Error Type:
Informational
Symbolic, Array Block Device Reads = <number>
Error Type:
Informational
Symbolic, Array Block Cache Reads = <number>
Error Type:
Informational
Symbol Instance Non-Block Device Reads = <number>
Error Type:
Informational
Symbol Instance Non-Block, Array Block Device Reads = <number>
Error Type:
Informational
Symbol Instance Non-Block, Array Block Cache Reads = <number>
Error Type:
Informational
Symbol Instance Block Device Reads = <number>
Error Type:
Informational
Symbol Instance Block Cache Reads = <number>
Error Type:
Informational
Tags Read = <number>
Error Type:
Informational
Packets Sent = <number>
Error Type:
Informational
Packets Received = <number>
Error Type:
Informational
Initialization Transactions = <number>
Error Type:
Informational
Read/Write Transactions = <number>
Error Type:
Informational
Avg. Packets Sent/Second = <number>
Error Type:
Informational
Avg. Packets Received/Second = <number>
Error Type:
Informational
Avg. Tag Reads/Second = <number>
Error Type:
Informational
Avg. Tags/Transaction = <number>
Error Type:
Informational
----------------------------------------------------------------------------------------------------
Error Type:
Informational
%s | DEVICE STATISTICS
Error Type:
Informational
Average Device Turn-Around Time = <number> (milliseconds).
Error Type:
Informational
%s | CHANNEL STATISTICS
Error Type:
Informational
DRIVER STATISTICS
Error Type:
Informational
Details. | IP = '<address>', Vendor ID = <vendor>, Device type = <type>, Product code = <code>, Revision = <version>, Product name = '<name>', Product SN = <number>.
Error Type:
Informational
Errors occurred retrieving controller project.
Error Type:
Informational
Internal driver error occurred.
Error Type:
Informational
Invalid or corrupt controller project detected while synchronizing. Try again later.
Error Type:
Informational
Project download detected while synchronizing. Try again later.
Error Type:
Informational
Low memory resources.
Error Type:
Informational
Unknown error occurred.
Error Type:
Informational