Typically we would recommend connecting to those devices using our Siemens TCP/IP Ethernet driver If the vendor states that you cannot access the Modbus TCP port without separate components on their side, there is nothing within KEPServerEx that you can configure to circumvent that. Modbus is not the native protocol for an S7-300 device. You would then point the Master PLC, to read and write to our slave using the IP of the PC that is running KEPServerEX. If the PLC is a Master and you need KEPServerEX to act a Slave we can do this as well, the Device ID you would set in the KEPServerEX is 127.0.0.1.1, this would create a Slave Node 1 in the KEPServerEX. Third question: Modbus devices can be Master or Slave, most users are using KEPServerEX as the Master and the PLC as the Slave, assuming we are talking about a Modbus TCP Slave PLC we would need to be able to establish a TCP socket to some port the Slave is listening on. Second question: KEPServerEX supports OPC-DA/OPC-UA and many more client interfaces.
How can I read data from PLC if its Modbus ports are not opened? Can it be done with Kepware?įor the first question: You can connect the KEPServerEX to many types of PLCs, could you tell me a bit more about the devices you wish to connect to assuming they are not Modbus PLCs? We support Reads and Writes.
I can address these questions for I can I connect Kepware to any PLC and read the data from that PLC?ĭoes Kepware work as an OPC server to read data from PLC?