Device connections
Protocols
2WinScada connects to field devices through a channel, device and tag hierarchy. License scope and your project's compatibility are separate questions. We do not give a general compatibility statement for specific device models; we assess your devices with you before the quote.
Standard protocols
- Modbus: Modbus TCP, Modbus over a serial line and Modbus through a serial-to-Ethernet gateway. 2WinScada works as the client (master).
- Siemens S7: Communication over Ethernet (ISO-on-TCP) with the S7-200, S7-200 Smart, LOGO! 0BA8, S7-300, S7-400, S7-1200 and S7-1500 families. DB, input, output, memory, timer and counter areas are accessed by absolute address. On the S7-1200 and S7-1500, PUT/GET access must be allowed in the PLC and optimized block access must be off for the DBs used.
- BACnet: Works as a BACnet/IP (IPv4) client. The Present Value of objects is read; writing is done on Analog, Binary and Multi-state objects. Devices on the network can be discovered. BACnet MS/TP and COV subscriptions are not supported.
- MTConnect: Data is read over HTTP through an MTConnect agent. MTConnect is read-only.
Package: Modbus and Siemens S7 are included in every package. BACnet/IP and MTConnect are included in Standard and Professional. Starter includes two of OPC UA, BACnet/IP and MTConnect (choice; by default BACnet/IP and MTConnect); the third can be added to your quote.
OPC UA
- OPC UA client: connects to
opc.tcp://endpoints anonymously or with a username and password. - Signed and encrypted connections, browsing the server's address space, bulk tag import and reading through subscriptions.
- Certificate and IssuedToken user identities are not supported.
Package: Included in Professional. In Standard, operation is included; managing OPC UA definitions with your own team can be added to your quote. Starter includes two of OPC UA, BACnet/IP and MTConnect; OPC UA can be one of the two.
EtherNet/IP
- Explicit messaging and cyclic (implicit) I/O.
- Access to generic CIP objects, and symbolic tag access on Rockwell/Allen-Bradley Logix and Omron NX/NJ controllers.
- CIP Safety, CIP Motion and CIP Security are not supported. Do not use EtherNet/IP communication in place of a safety function.
Package: Included in Standard and Professional. In Starter it can be added to your quote.
MQTT, REST and database (ODBC)
- MQTT: 2WinScada subscribes to topics on an MQTT broker and writes incoming values to tags.
- REST: With REST Client, 2WinScada pulls data from an external system's HTTP API at set intervals. With REST Server, external systems send data to 2WinScada with a device key.
- Database (ODBC): Values are read from and written to address–value tables in another system's database. A suitable ODBC driver must be installed on the server.
Before the quote, we check compatibility with your broker, API or database for your project.
Package: Included in Standard and Professional. In Starter it can be added to your quote.
How we check compatibility
Select the protocols you use in the form and describe your needs. In the meeting we go through device models, addressing and the network layout with you.