Hello everyone, I am in need of assistance with my setup involving a SLC 5/04 PLC connected to a PanelView Plus 600 via a DF-1 protocol over a serial 232 port. Even though the PanelView Plus resets and displays a message indicating that its DF-1 driver has automatically configured and started, I am unable to establish communication between the two units. I have ensured that I am using the correct cable, set the PanelView Plus to auto configure, and experimented with various settings for the SLC channel 0 without success. I am struggling to establish proper communication between the PanelView Plus and the SLC PLC via the serial port. Any guidance or assistance would be greatly appreciated.
Are you encountering issues with a system that was once functional but now seems to have stopped working, or are you setting up a new system for the first time? I recommend sticking to the default settings on the PanelView Plus and SLC-5/0x controller, rather than using the AutoConfigure feature on the PV+. Make sure both sides are set to DF1 Full Duplex 19200 baud, with CRC error checking, 8 data bits/No parity/1 stop bit. If the SLC-5/04 is unresponsive to the PanelView Plus, you may receive timeout error messages on the PV+ indicating failed requests to the controller. What symptoms are you observing on the PV+ display?
Do you know the precise Model Number of your PanelView Plus device? Have you confirmed that the SLC Port is configured for DF1 instead of DH485? Let's double-check to ensure everything is correctly set up for optimal performance.
When configuring communication settings between a PVP600 and a 1747-L532B 5/03 over serial, it is important to ensure the following parameters are set: PLC-CH0DF1 Full Duplex, 19200 baud rate, No Parity, Source ID - 1, No Handshaking, and BCC Error Detection. For Panelview Plus Serial Comms on Com Port 1, ensure the device is set to SLC or MicroLogix with Station Number 0192001, 1 Stop Bit, and BCC Error Checking. It is recommended to manually set up the communications rather than using auto configure to avoid potential issues. Additionally, testing the project by directly connecting to the PLC with a laptop via RSLinx can help verify settings. Checking the PLC status in the communications tab of FactoryTalk View Studio can also confirm the health of the PLC connection.
Thank you for your responses everyone. Marcwand, your settings closely resemble mine. Sthompson, I currently have the 600 touch model with only an RS232 port, and the SLC is definitely set to DF-1. Ken, this is a new system for me, my first time working with the "plus" panel views. When I reboot the PV with cables disconnected, it shows a message stating it is unable to configure DF-1 port 1. Once I connect the cable, it retries and confirms that the DF-1 is configured and the driver is active. However, despite this indication, I do not see any communication lights or data transfer occurring. I suspect that perhaps my SLC tags are not correctly addressed in the tag database, even though the tags were set for me when I converted a PanelBuilder 32 program to RSView (example: {SLC}B3:0/2).
Hey Simmo, are you able to connect to the PLC online using a serial connection on your laptop? By setting up the communications in the design tab, you can easily browse the PLC tags directly from the programming software. To do this, configure RSLinx Enterprise by creating a browsing shortcut, setting up a communication path (serial), configuring the device (SLC), and assigning the communication path and device to your shortcut. Make sure to apply these changes. Once set up, you can browse online to assign tags to status indicators. Test the panelview screen by clicking the play button in RSView to see live status changes on your laptop. After verifying PLC communications, open the RSLinx Enterprise communication setup and click on "copy from design to runtime" to compile the communication path with the runtime project. Ensure that the setup has been transferred successfully to the runtime tab. When downloading to the panelview, select the option to replace communications to load the setup into the panelview along with the project. Check the panelview communication setup by reviewing the RSLinx Enterprise section in the panelview configuration. The paths and shortcuts should mirror the setup on your laptop. If you are unable to connect to the PLC online, you can manually set up communications in the runtime tab of RSLinx Enterprise. Make sure to check the box to replace communications when downloading to the panelview. If this all seems a bit basic, it's because this is your first panelview plus, and I'm working from memory here. Hopefully, this info helps you out. Good luck!
I would suggest checking the baud rate, parity, stop bits and other communication parameters to ensure they match on both the PLC and PanelView. Also, consider possible issues related to the addressing of the tags. Make sure that the tags in the PanelView project are addressing the correct PLC data. Additionally, the PLC port might be defective, the RS232 cable could be damaged, or the terminal block might need reinstalling. Lastly, think about updating the firmware of your PanelView Plus 600 to rectify any possible bugs.
✅ 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: - It is possible that there could be issues with the cable connection, settings mismatch between the devices, or incorrect configuration of the communication protocol. Troubleshooting these areas can help resolve the communication problem.
Answer: - To troubleshoot communication problems, ensure the cable connection is secure, verify the settings of both devices are correctly configured for DF-1 protocol over serial 232 port, and check for any errors in the SLC channel 0 settings.
Answer: - Check the PanelView Plus display for any error messages related to the DF-1 driver configuration. Ensure that the PanelView Plus is set to auto-configure for the DF-1 protocol and that the driver has successfully started without any errors.
Answer: - Common reasons for communication problems could include incorrect cable connection, mismatched settings for the DF-1 protocol, incorrect baud rates or data bits configuration, or issues with the SLC
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.