Gateway industrial exchange protocols on Linux. Collect yourself

 3r3149. 3r3-31. I am engaged in the development, implementation and operation of automatic process control systems (APCS). At first he worked with SCADA-systems. Then he quickly switched to working with industrial device exchange protocols. Both self-writing drivers and setting up data collection systems. At the moment, my work is going through the atmosphere of Modbus, IEC-101/10? ORS and other protocols.
 3r3149. Gateway industrial exchange protocols on Linux. Collect yourself
 3r3149. Fig. 1. The variety of exchange protocols used in the process control system
 3r3149. IEC 60870-5-104;
 3r3149. 3r3-33132. IEC 60870-5-101;
 3r3149. 3r3-33132. Counters 3r362. Mercury 23? 23? 23? 23? 236
 3r3149. 3r3-33132. Counters 3r3677. SET-4TM, PSCh-3TM, PSCh-4TM
 3r3149. 3r3-33132. Counters 3r372. Energomera;
 3r3149. 3r3-33132. SNMP 3r3107. ;
 3r3149. 3r3-33132.
 3r3149. 3r3-33132. Counters Mercury 200 3r3107. .
 3r3149. In order to transfer data to the upper level not only via the OPC UA protocol, “
OPC UA to Modbus Converter and IEC 60870-5-104 3r3107. ". In addition to the data transfer function for these protocols, the “Converter” has an embedded web-server. With the help of a special editor, you can draw a diagram, display the tag values ​​on it, and then open it in the browser. It turns out mini-SCADA directly in the controller. How does the revitalization scheme I wrote
here is
, about the editor 3r3398. here is
. In the future, it is planned “OPC UA to MQTT Converter”.
 3r3149. OPC UA servers and converter work on x6? ARMv7 and AARCH64 architectures.
 3r3149. Thus, for hardware, you can use both time-tested solutions based on mini industrial computers, and all kinds of “raspberry pi compatible” ARM minicomputers. How to install and configure software with examples you can read here is or here is .
 3r3149. In general, the structure of the complex is as follows:
 3r3149. 3r33112.
 3r3149. The system has scalability. Components necessary only for the decision of the current task are used.
 3r3149. Using the OPC UA server, our schema transforms: 3r3133.  3r3149. 3r3119.
 3r3149. We got the following:
 3r3149. 3r3124.  3r3149. 3r3-33132. OPC UA server collects data from devices via RS-485 without long delays between requests;
 3r3149. 3r3-33132. The data in SCADA is issued in several pieces in a single TCP packet for change;
 3r3149. 3r3-33132. It is possible to connect several equally configured workstations to the OPC UA server. It is useful if you need duplication.
 3r3149. Thus, instead of a bunch of OPC-server and "Ethernet Converter to RS-485" we get one device that combines their functionality. I like this scheme more. And you? 3r3145. 3r3149. 3r3149. 3r3149. 3r3142. ! function (e) {function t (t, n) {if (! (n in e)) {for (var r, a = e.document, i = a.scripts, o = i.length; o-- ;) if (-1! == i[o].src.indexOf (t)) {r = i[o]; break} if (! r) {r = a.createElement ("script"), r.type = "text /jаvascript", r.async =! ? r.defer =! ? r.src = t, r.charset = "UTF-8"; var d = function () {var e = a.getElementsByTagName ("script")[0]; e. ): d ()}}} t ("//"""_mediator") () (); 3r3143. 3r3149. 3r3145. 3r3149. 3r3149. 3r3149. 3r3149.
+ 0 -

Add comment