
Siemens TCP/IP Ethernet Driver Help
Device <device name> is not responding.
Error Type:
Warning
Result:
If tag was being read:
l If tag is a block tag, the entire block will be invalidated. All tags within that block will be invalidated.
l If tag is an array tag or string tag, just this tag will be invalidated.
If tag was being written:
l Write operation for the given tag will not take place.
Possible Cause:
1. The connection between the device and the host PC is broken.
2. The response from the device took longer to receive than the amount of time specified in the "Request
Timeout" device setting.
3. The named device may have been assigned an incorrect IP address.
4. The device's CPU work load is too high.
Solution:
1. Verify the cabling between the PC and the PLC's device.
2. Increase the Request Timeout setting so that the entire response can be handled.
3. Verify the IP address given to the named device matches that of the actual device.
4. If this error occurs frequently, decrease the tag group scan rate to reduce the work load on the PLC's CPU.
5. Increase the Scan Cycle Load from Communication and Scan Cycle Monitoring Time.
Unable to connect to device <device name>. Device returned transport error
[Code=<code>].
Error Type:
Warning
Result:
1. If tag is to be read in the process of connecting, and a device error (transport) occurred:
l If tag is a block tag, the entire block will be deactivated. All tags within that block will be deactivated.
This is signified by the postfix message "...Block Deactivated."
l If tag is an array tag or string tag, just this tag will be deactivated.
This is signified by the postfix message "...Tag Deactivated."
2. If tag is to be read in the process of connecting, and no device errors occurred:
l If tag is a block tag, the entire block will be invalidated. All tags within that block will be invalidated.
l If tag is an array tag or string tag, just this tag will be invalidated.
3. If tag is to be written in the process of connecting:
l Write operation for the given tag will not take place.
Possible Cause:
An RFC1006 error (ISO over TCP/IP) occurred. This is the portion of the packet that encapsulates the S7
Messaging packet.
Solution:
Contact Technical Support.
www. kepware.com
72
Comentarios a estos manuales