Hello there! I am a new intern delving into the exciting world of automation. My current task involves mastering the programming of a Delta DVP80ES200R PLC and a Delta DOP-112WX HMI. The PLC runs on ISPSoft 3.17 software, while the HMI operates on DOPSoft 4.00.16. Unfortunately, I've encountered an issue with communication between the PLC and HMI. While the HMI successfully sends data to the PLC, the reverse communication is not functioning as expected. For instance, when pressing the M0 button on the HMI, the Y0 indicator should light up on the PLC, but the corresponding indicator on the HMI remains unlit. I have followed the designated connection process as outlined in the manual (https://deltronics.ru/images/manual/DOP-112-115+Quick+start+manual_EN.PDF), with the HMI connected via RS-485 COM1 to the PLC's RS-485 COM2 port. If you have any further inquiries or suggestions, please don't hesitate to reach out. Your input is highly appreciated. Thank you!
Hello, As an intern and newcomer in the automation field, I have been tasked with learning and programming a PLC and HMI system together. The PLC in question is the Delta DVP80ES200R (DVP ES2) running ISPSoft 3.17, while the HMI is the Delta DOP-112WX (from the DOP-100 Series) using DOPSoft 4.00.16. However, I am encountering a problem where the HMI and PLC are not communicating effectively. Although the HMI is able to send data to the PLC, the PLC does not send the data back to the HMI. For example, when I press the M0 button on the HMI, the Y0 light illuminates on the PLC, but the Y0 indicator on the HMI does not reflect this change. I have followed the connection setup guide for linking the HMI to the PLC via RS-485 COM1 on the HMI to RS-485 COM2 on the PLC, as outlined in the manual (https://deltronics.ru/images/manual/DOP-112-115+Quick+start+manual_EN.PDF). If you have any further inquiries or suggestions, please feel free to reach out. Thank you for your assistance in advance. Kind regards, Konstantin Kolev
If you are experiencing communication errors, there is likely an issue with the display object. Keep an eye out for any "com errors" that may pop up, indicating a malfunction in the communication system.
Hello everyone, I appreciate the assistance. As mentioned by Konstantin, the issue lies in the read/write address of each object, a simple yet crucial detail. Thank you once again for your help!
Jerico expressed gratitude for the assistance provided. As mentioned by Konstantin, the issue lies in the read/write address of each object. Despite initially feeling it was a simple problem, Jerico is thankful for the help. Can you please elaborate on how you successfully resolved the issue, as I am currently facing the same challenge?
Hello! Congrats on your internship and your venture into automation. Based on what you've shared, there could be several reasons why you're not seeing the expected result. Here are a few suggestions: First, double-check your HMI configuration to ensure it is set up to receive data from the PLC. Second, if your RS-485 COM2 port is used for other communication tasks, there could potentially be some interferences. One way to isolate this issue is to try connecting it with an RS-232 port to see if the HMI’s Y0 indicator lights up. If it does, you'll know the issue lies in the communication setup. Lastly, ensure your HMI and PLC have the same baud rate and communication parameters, slight mismatches can cause unexpected results. Hope you find this useful and good luck with your project!
Welcome to the fascinating world of automation! It sounds like you're doing everything right from your description. You might want to cross-verify the Modbus address settings on your PLC and HMI, which is quite a common issue. Sometimes the Modbus slave address of PLC in HMI settings does not match with the Modbus address of PLC. Also, don't forget to check your HMI button settings, ensuring that the registers assigned for the M0 button and Y0 indicator are correct and not reversed/overlapped. Good luck and don't stop experimenting!
Hey there! It sounds like you're really diving into some interesting tech with those Delta devices. Since the HMI can send data to the PLC but not vice versa, it might be worth double-checking your wiring and ensuring that your COM settings match on both devices—sometimes baud rate or parity settings can cause communication issues. Also, make sure that the Y0 output on the PLC is correctly programmed and enabled in ISPSoft. It could also be helpful to test the PLC’s output independently to ensure it’s functioning as expected. Good luck, and feel free to keep us updated on your progress!
✅ Work Order Management
✅ Asset Tracking
✅ Preventive Maintenance
✅ Inspection Report
We have received your information. We will share Schedule Demo details on your Mail Id.
Answer: Answer: The communication issue could be due to incorrect settings or configurations, wiring issues, software compatibility problems, or communication protocol mismatches.
Answer: Answer: You can troubleshoot by checking the wiring connections, ensuring the correct communication settings are configured in both the PLC and HMI software, verifying the communication protocol compatibility, and testing communication using diagnostic tools if available.
Answer: Answer: You should double-check the RS-485 connections between the HMI and PLC, verify the communication settings (baud rate, data bits, parity, stop bits), confirm the correct communication protocol is selected, and ensure both devices are properly powered and configured to communicate with each other.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.