|
|
Product Catalog |
|
q |
|
|
Modbus OPC Server Usage Tips…
This OPC server is designed to be one of the quickest, easiest, and least expensive (it's free for SIXNET hardware users!) way to interface your industrial Windows software to SIXNET I/O. This server talks Modbus RTU protocol to SIXNET I/O over Ethernet or serial connections and makes the data available via OPC or DDE. Most HMI, SCADA, or industrial Windows software packages now support OPC and/or DDE.
When should I use this server to interface SIXNET I/O modules?
|
˘ |
1. Use the SIXNET I/O Tool Kit to configure and define I/O channel tag names for your SIXNET I/O. |
|
|
2. Use the SIXNET I/O Tool Kit to export this information to the KEPServer. (Note: this requires a license for the SCS feature set of the SIXNET I/O Tool Kit.) |
|
|
3. Open the exported file in KEPServer and simply run it. All the necessary settings have been made for you. |
|
|
4. Run the KEPServer and your tags are now available to any OPC client. Just follow the directions for your OPC client to link in your tags. |
Note: You only had to assign your I/O channel tag names once.
|
˘ |
When you want to interface to SIXNET I/O modules and other non-SIXNET devices simultaneously. This server comes with trial drivers for many different hardware lines. Multiple drivers can be run at the same time to interface to several different types of hardware. |
Note: The SIXNET drivers will run without restriction. However, other drivers will timeout after an hour. Contact Kepware Products to purchase a license to run these other drivers full-time.
When should I use the SIXNET OPC Server instead of this Modbus OPC Server?
|
˘ |
When you need to use the SIXNET "I/O for Windows" protocol for more advanced operations such as analog calibration, datalogging, or reporting on exception. The SIXNET OPC Server uses SIXNET Universal protocol to talk to SIXNET controllers and I/O modules. Unlike Modbus, this protocol supports multiple masters and other advanced communication modes. |