![]() ![]() I will have very limited down time at each site so I’d like to keep physical changes limited to the screen. Of course there is always the option of installing hardware, either a little PLC or modifying the Mitsubishi PLC, I’ve found that Mitsubishi PLC and Modbus are not easy bedfellows. Kepware seems to have a slave option so I will look at that, How to use KEPServerEX OPC Server (Kepware) with ioLogik 4000 (Modbus TCP/IP NA-4010 and Modbus Serial NA-4020/NA-4021) Alex Chen, Senior Engineer, Moxa Technical Support Dept. ![]() ![]() I have licences for MXOPC for the Mitsubishi PLC, that OPC also has a Modbus driver but cannot act as a Modbus slave. KEPServerEX OPC Server(Kepware) - Free download as PDF File (.pdf), Text File (.txt) or read online for free. Now you can use the same registry addresses for every node. In Kepware you can access all these devices independently by using the IP address followed by the node name: 192.168.1.10.x Search for Bridge in the Kepware manual. It is the Modbus slave that I am trying to replicate. Every Modbus RTU slave should have a unique ID. It is not feasible to change these systems at this stage.Īt present the Proface screen acts a Modbus master to collect data from various devices, it has a Mitsubishi driver to collect from a PLC and has a Modbus Slave driver. I need each remote instance of ignition, which will be a vision module and the SQL Bridge Module, to have a set of Modbus registers available on IP port 502 for other local systems to read. Description: Kepwares Modbus OPC Server Suite works in conjunction with KEPServerEX to provide OPC Data Access to Modbus compatible devices and PLCs. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |