When you set up KepServer on a development PC, the serial port it's using is seldom COM1, which means when the *.PFE file is copied to the terminal it is often pointed at COM4 or COM5 or something else. Unfortunately my laptop doesn't have a serial port, so no, I haven't been able to. Have you been able to test the KepServer driver on your development PC ?
I'm not quite sure what you mean by that - onboard the PLC? Within KEPServer, the "device" (that is, the PLC in question) has been configured for SERIAL1, is that what you mean? Make sure that onboard the PLC the KepServer is configured for SERIAL1. Thanks for all the ideas! I'll go through them one at a time. I'm using 9600 baud rate, even parity, 1 stop bit - as far as I can see they're uniform across the KEP server and the Quantum.Ĭan anyone suggest what I could try next? Do I need to configure the serial port in the PV itself somehow? My cable is a straight-through 9 pin D shell (pin 1 to pin 1, pin 2 to pin 2, etc.) pfe file is correct, etc, but something in my communications setup is wrong, or my cable is the wrong one. It appears that the PV knows where to look (it has the channel and device name correct, so obviously my.
When I run the application on the PV, though, I get the error bar with ". So I have KEP Server installed and configured, I have updated the firmware on the PV to include the KEP drivers, and to the best of my knowledge, the PLC port is configured correctly (although I've never configured a Modbus port on a PLC before, so if anyone knows any hints, traps or otherwise useful info, please let me know). Actually, I have two PLC's, a Schneider 984 and a Schneider Quantum, but I'll start with one at a time.
0 kommentar(er)
