MasterOPC Modbus Server Download now
Multi-Protocol MasterOPC Download now
MasterOPC Multi-Protocol OPC Server Multi-Protocol MasterOPC Server is a modular OPC server that provides device data acquisition via various protocols. In addition, the server provides the following features: Support custom protocols written in Visual C++ – for users skilled in Visual C++ Support custom protocols written in the built-in script programming language – for automation engineers The built-in script programming language is the same as for MasterOPC Universal Modbus Server. Unique technical peculiarities Support of the following OPC standards: 1. OPC DA (Data Access, processed data) 2. OPC HDA (Historical Data Access, archived data), including archiving instantaneous values of acquired variables. Archival storage of acquired variables is organized using built-in SQL server 3. OPC UA complies with modern cross-platform software standards Support of OPC UA standard, including data transfer in open or encrypted mode. OPC UA is based not on Microsoft DCOM but on open cross-platform technologies. This provides secure data transfer not only over a local network but over any routed network, including Internet. Communication with OPC UA clients on other operating systems (for instance, Linux or Android) is also available. In favor of the built-in OPC DA client, Multi-Protocol MasterOPC Server provides conversion from OPC DA to OPC UA. If an OPC UA client is not installed on the remote computer, Multi-Protocol MasterOPC Server can perform reverse conversion from UA to DA or had, in this case DA/HDA data transfer is exhibited using tunneling protocol over routed networks, where the referred protocols cannot be used directly in the underlying network. The built-in IEC 60870-5-104 server provides data transfer to IEC104 clients via the tunneling protocol that protocol. This enables Multi-Protocol MasterOPC Server to work with other data acquisition systems that are based on different communication protocols (SNMP, Profinet, other OPC servers, etc.), and transfer data received via IEC-104 clients using the usual data transfer and routing methods). The built-in programming editor provides initial processing of the received data from external devices as well as processing of the data being sent to external devices. The script language can also be used for the following purposes: Development of new drivers Development of signal simulators and generators Data transfer with other programs Writing data to a database Supported Operating systems: Windows 7 Windows Server 2008R2 Windows 8, Windows 8.1 Windows Server 2012 Windows 10 Licensing of Multi-Protocol MasterOPC Server In Multi-Protocol MasterOPC Server, by default drivers of all protocols are plugins in the main server program. In addition, the server may contain the following plugins: User Protocol – for developing custom protocols in C++ User Script – for developing custom protocols using the built-in programming language The demo version of Multi-Protocol MasterOPC Server includes all plugins but limited to support 32 tags only. A dongle version of Multi-Protocol MasterOPC Server includes the respective plugin (or plugins) without restrictions on tags count. Note: A dongle version by default include all other plugins in its demo version (that is with tags count restriction); Plugins in the demo version may be disabled by the user.  MasterOPC Multi-Protocol OPC Server
MasterOPC Tunneler OPC Server When building complicated automation systems, creation of distributed systems sometimes is inevitable, in which cases an OPC client is connected to one or several OPC servers running on remote computers (workstations). OPC technology solves this problem by standard means: DCOM should be configured on each machine. However, if those machines belong to different LANs (for instance LANs separated from each other by Internet), such a communication procedure could be a difficult task to handle, and would require to use VPN technologies. Some companies offer special programs that facilitate connection of remote OPC servers over routed networks. Such programs are commonly named “tunnellers” or “bridges”. The essence of this solution is described below. A special OPC client, the one side of a tunnel, is installed on a machine running the OPC server. The OPC client acquires data from the server and then transfers data via a compatible tunneling protocol in contrast with OPC communication establishment methods with routed networks which should comply with the underlying network architecture and protocols. On the remote machine, a program is installed, which receives data via the tunneling protocol and then outputs them via OPC interfaces, so an OPC client installed on the remote machine thinks that gets data from a local OPC server. Such a communication scheme solves both the problem of DCOM configuration and the problem of secure data transfer. However, most companies use in such products their proprietary (elsewhere incompatible) communication protocols between two parts of the tunnel. The peculiar about MasterOPC Tunneler is that it uses OPC UA as an intermediate protocol, and the entire solution is based on the plugins of Multi-Protocol MasterOPC Server. Data is encrypted and transferred in binary sequences. This grants a number of benefits: Not only clients of Multi-Protocol MasterOPC Server can connect to the server part of a bridge but also any UA client. The final part of processing data is done by the converter of OPC DA/HDA to OPC UA. It is possible to build structures of distributed systems that include an arbitrary number of servers and clients. In addition to conversion functions of OPC “classic” interfaces to the modern OPC UA interface, other standard plugins can be plugged into Multi-Protocol MasterOPC Server. To build a tunnel, you need at least two Multi-Protocol MasterOPC Servers. On each machine where you want to run an OPC server, you need to install Multi-Protocol MasterOPC Server with the “OPC DA Client” or “OPC DA+HDA Client” plugin. On each machine where you want to run an OPC client or a SCADA system, you need to install Multi-Protocol MasterOPC Server with the “OPC UA Client” plugin.   A server plugin can be purchased separately; this provides flexible selection of configuration for any specific task.   MasterOPC Tunneler OPC Server
MasterOPC IoT Gateway OPC Server MQTT (MQ Telemetry Transport) emerged as a protocol designed for such constrained devices and low-bandwidth, high-latency or unreliable networks where IoT devices are frequently deployed. It is a publish/subscribe, extremely simple and lightweight messaging protocol, The design principles are to minimize network bandwidth and device resource requirements whilst also attempting to ensure reliability and some degree of assurance of delivery. MQTT allows for receipt acknowledgement, data encryption, and has a convenient administration mechanism. Presently MQTT is actively used in the cloud on Microsoft Azure, Amazon Web Services and others. This opens enormous possibilities for connecting devices to high-performance virtual servers as well as bleeding edge technologies like machine-learning. Our product range includes IoT gateway designed for integration of devices and services via MQTT protocol. Our Modbus Universal MasterOPC and Multi-Protocol MasterOPC servers also have a built-in MQTT client. This client provides extensive functionality to: 1. Communicate with devices that support MQTT protocol and send received data over any other supported protocol: Modbus, Profinet, Bacnet or IEC104 and to SCADA systems via the OPC DA, UA and HDA interfaces. 2. Integrate IoT devices into cloud services effectively converting industry protocols to MQTT. 3. Receive data from third-party software or cloud services and send it to SCADA systems. MasterOPC IoT Gateway OPC Server