Скачать с ютуб How to troubleshoot a "Device no response" message (Part 1) - EasyBuilder Pro в хорошем качестве

How to troubleshoot a "Device no response" message (Part 1) - EasyBuilder Pro

Within this tutorial, we demonstrate the procedure for troubleshooting a "Device no response" message that appears when the HMI can still communicate with the PLC. Part 2:    • How to troubleshoot a "Device no resp...   Given this scenario, a "Device no response" message may occur due to any of the following reasons: - An incorrect data type may have been configured within the format tab of the numeric object. If for example, the register that you are reading occupies one word within PLC memory and the data type is configured such that HMI polls 2 words from the PLC. A communication error may occur. - You may be using the wrong register type for the device register that you intend to read. For example, if you are communicating with a Modbus device that does not support Modbus function code 16 (decimal) and you use the 4X address type within our software, you will likely experience a communication error. - A register used within an object may not have been used or made accessible within PLC memory or when using a tag-based PLC the tag name may have been changed within the PLC project. - If the HMI has a bad connection due to a faulty Ethernet or serial cable or if the flow of packets is restricted due to an issue with a router or switch. The HMI may only display several objects at a time. - It is also possible that “emi” noise may disrupt the HMI’s ability to communicate with a PLC or external device. In this case the issue may be resolved by using a shielded cable and a ferrite core if necessary… #Weintek #PLC #HMI #EasyBuilderPro #Troubleshoot