使用搜索功能查看 Kepware 的信息库,其中包含 500 多篇知识库文章。缩小搜索结果范围,或在下面的搜索字段中输入您的查询。

或者,如果您无法找到解决方案,我们还有另一个资源:我们的 PTC eSupport Portal。 如果系统提示您登录 eSupport Portal,您可以使用“我的 Kepware”凭据。需要一个“我的 Kepware”帐户吗?在此处创建

搜索解决方案结果:
View All Solutions

Kepware Knowledge Base: Solution


Unable to Communicate with a MicroLogix PLC


Last Update: 2018/11/12

Problem:
KEPServerEX cannot communicate to an Allen-Bradley Micrologix PLC. The server's Event Log is either displaying an error message that includes an error code or the error message "Device Not Responding."

Solution:
1. If the error code states that users are unable to read or write to registers, then the error is coming from the PLC. For more information, refer to the driver's help file.

2. If the error message "Device Not Responding" is received, the problem may be one of the following:

  • Bad cabling. To fix, use the same cable that was used to program the PLC.
  • Bad communication settings. To fix, match the settings configured in RSLogix. Use 8 data bits in the server: the PLC does not support 7 data bits.
  • An invalid Device ID. A MicroLogix PLC's Device ID is decimal; an SLC5 PLC's Device ID is octal. Users familiar with SLC5 PLCs may have used octal out of habit.

3. If using Ethernet Encapsulation, verify the following:

  • The communication settings in the Serial to Ethernet Converter match the settings that worked in the direct connection from the PC to the PLC.
  • The converter's IP address falls within the subnet of the PC. A socket connection cannot be made to an IP that is outside of the subnet.
Related Protocols
Allen-Bradley DF1