Our compressors are equipped with an SLC 5/04 controller that utilizes DH+ for connectivity to the PanelView, Data Highway, and Hwl Experion SCADA channel. However, we are experiencing communication issues, resulting in the SLC being unable to communicate with the PanelView or SCADA system. The PanelView displays an error message stating: "No acknowledgement reading N:10.0- N10.65 from the SLC at station 2 on the DH+ driver."
ctrleng14 mentioned a connectivity issue with their SLC 5/04 compressors, which are linked to Panelview and Datahighway via DH+. This has caused a loss in communication with the Hwl Experion SCADA system. The error message on the Panelview indicates a lack of acknowledgment from the SLC at station 2 on the DH+ network. To resolve this issue, it is crucial to troubleshoot and identify the point of failure in the link. It is recommended to check if other devices on the DH+ network are communicating properly and to test by disconnecting devices and adjusting terminating resistors to pinpoint the faulty device or cable. If you are experiencing similar connectivity problems, consider following these steps to diagnose and resolve the issue efficiently.
Recently encountered a communication loss problem with DH+, which was successfully remedied by re-terminating a single node. The issue was caused by a short circuit, resulting in sudden communication loss despite the network functioning properly. Looking forward to the day when DH+ and DeviceNet technology are no longer in use before my retirement.
Is it possible to access the DH+ network online? Which nodes can be identified in RSLynx? Explore the online capabilities of the DH+ network and discover the various nodes displayed in RSLynx.
I appreciate everyone for their responses. By "installing" the termination resistor, the problem was successfully resolved. It seems that the EOL resistor may have been accidentally shorted.
It seems like there could be quite a few elements affecting your communication in this scenario. It's possible that your SLC 5/04 controller's firmware might need an upgrade, or there might be physical wear and tear on the DH+ network cables affecting the signal. There could also be an incorrect routing path setup for the PanelView or SCADA system. Alternatively, if you have recently made modifications to your network or device configurations, there might be some settings you need to revisit.
It seems like you may be dealing with a connectivity issue on the Data Highway Plus (DH+). One possible cause could be a broken or defective cable which can lead to communication problems between devices. I recommend checking all your cables and their terminators at both ends. Additionally, this could also be caused by a problematic DH+ ring node or a terminated node. It might be worthwhile to isolate and test each node/device and consider the physical condition of your DH+ network. If swapping out the cables and checking the nodes doesn't work, it may be an issue with the PLC's DH+ port or a software configuration issue on PanelView or the SCADA system. Otherwise, consider reaching out to a specialist or the system producer for further assistance.
It sounds like you're dealing with a classic communication hiccup on the DH+ network. First, I'd recommend checking the DH+ connections and ensuring that the wiring is intact. Be sure to also verify the station addresses; sometimes a mismatch can lead to those acknowledgment errors. Additionally, try looking at the SLCβs configuration parameters to ensure they correspond correctly with the PanelView and SCADA system settings. If the issue persists, reviewing the data table N:10.0 to N:10.65 for any potential conflicts or corrupt data might help isolate the problem further. Good luck!
It sounds like a frustrating situation! Since youβre seeing the error about βNo acknowledgement,β it might be worth checking the cable connections and ensuring that the node addresses on the DH+ network are configured correctly. Sometimes interference or improper grounding can lead to communication drops as well. Additionally, verifying that the SLC is in fact programmed correctly to send those specific N:10.0 - N:10.65 values might help. If all that's good, you might want to try rebooting the devices or even testing the DH+ network with a diagnostic tool to pinpoint any issues. Good luck!
β 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: Communication issues can be caused by various factors such as incorrect network settings, faulty cables, improper addressing, or configuration mismatch between devices.
Answer: Answer: To troubleshoot this error, check the network configuration, verify the addressing settings on both the SLC and PanelView, ensure proper cable connections, and confirm that the DH+ driver settings are correctly configured.
Answer: Answer: Yes, the SLC5/04 controller needs to be properly configured with the correct DH+ network settings, including node addressing, baud rate, and communication protocol to establish seamless communication with the PanelView and SCADA system.
Answer: Answer: Start by checking the physical
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.