So Kepware's EX OPC server will not provide an HMI interface to interact with the UP750. The OPC server is there to interface (exchange data) with the field device. The OPC client is the software part that does the data collection or has the GUI that interacts with the field device. gateways connected via Modbus Plus to an NT hardened personal computer. Just remember that an OPC server exists solely to talk to an OPC client (a different software function). To create the filter, it is necessary to know which TCP/UDP ports are used for. Time is not an issue, but cost-effectiveness is. Develop a small OPC server that runs on PV+ (somehow) that provides data to FTView, much like the Kepware, but a much smaller and probably cheaper than Kepware. Their EX server software runs in demo mode for 2 hours at a stretch, and can be restarted after the 2 hours expires, so it is an excellent tool for experimenting to see if it works. Develop a FTView Driver for Modbus Master that directly integrates Modbus Slave (both on RTU and TCP). Kepware's been doing OPC servers for a long time now, so I suspect that they have some means of accomplishing this. I'm trying to recall how Kepware EX addresses the device and whether it is done strictly by IP address, but can't recall. I suspect that the UP750 (is that a setpoint programmer?) uses a serial interface, but maybe it has an ethernet port (but having an ethernet port doesn't guarantee that the Modbus data is available on the port, either). I've used Kepware's OPC server on Modbus/TCP devices, but I haven't used it with Modbus RTU device over a serial interface, like RS-485.
0 Comments
Leave a Reply. |