Progea Connext

Manufacturer	Protocol	Requirements	Package	Win32	Win64	Linux/.NET Core
3S	CODESYS	3S Software CODESYS SoftPLC version 3.	Automation		*
B&R	B&R	B&R devices that implement the communication protocol INA2000	Automation	*	*
Beckhoff	Beckhoff TwinCAT ADS	Beckhoff TwinCAT system	Automation	*	*
GE General Electric	GE Ethernet	Support GE intelligente platform PLCs series 90, GE intelligente platform micro series	Automation	*	*	*
Hilscher	Hilscher CIFX Fieldbus Multiprotocol	Hilscher cifX card for fieldbus PCI interface	Automation	*	*
Mitsubishi	Melsec FX	PLC MELSEC-FX and MELSEC-FX2N PLCs and compatible	Automation	*	*	*
Mitsubishi	Melsec FX3U-TCP	PLC MELSEC-FX3U	Automation	*	*	*
Mitsubishi	Melsec Q TCP	Melsec Q PLC	Automation	*	*	*
Omron	EtherNet/IP	Omron NJ, NX PLCs	Automation	*	*	*
Omron	Fins Ethernet	Omron SYSMAC PLCs	Automation	*	*	*
OPC Foundation-Progea	OPC UA Client	All OPC UA Server	Automation	*	*	*
Panasonic	FP MEWTOCOL	PLC NAIS FP Series	Automation	*	*	*
Rockwell Automation	Allen Bradley -EtherNet/IP	PLC-5, SLC-500, MicroLogix, ControlLogix, CompactLogix and FlexLogix	Automation	*	*	*
SAIA-Burgess	Saia S-BUS Serial	All Saia PLCs, PCD Series	Automation	*	*	*
Siemens	S7-Ethernet TCP	Simatic-S7-200-300-400 Vipa System 200v, 300v, 300s	Automation	*	*	*
Siemens	Siemens PC Adapter MPI	Simatic PLCs-S7-300-400, Vipa PLCs and compatible device	Automation	*	*	*
Siemens	S7-TIA PORTAL (Symbolic)	Simatic-S7-1200-1500	Automation	*	*
Siemens	Siemens PPI	Simatic-S7-200 and compatible	Automation	*	*	*
Modbus	Modbus Serial RTU	Any standard Serial Plug and Cable supported device	Basic	*	*	*
Modbus	Modbus TCP-IP Master	Any standard Modbus slve device	Basic	*	*	*
Modbus	Modbus TCP-IP Slave	Any standard Modbus Master device	Basic	*	*	*
Progea	SQL Driver	SQL Driver is able to connect to a database server that supports the TCP/IP protocol.	Basic	*	*	*
BacNet/IP	BacNet/IP	Any device supporting Bacnet IP	Facilities	*	*	*
Konnex KNX	KNX EIBUS (Falcon) Ethernet	Building automation device supporting or compliant KNX	Facilities	*	*	*
SNMP	SNMP Manager	Device supporting SNMP protocol acting as SNMP Agents	Facilities	*	*	*
IoT PubNub	PubNub IoT Cloud	PubNub Applications	IOT	*	*
IoT Progea Databoom	IoT Progea Databoom	IoTProgeaCloud Applications on Databoom Cloud Platform	IOT	*	*	*
MQTT	MQTT Client	Support MQTT brokers	IOT	*	*	*
IEC 60870-5-104	IEC 60870-5-104 TCP/IP	Any server supporting IEC 60870-5-104 via TCP/IP networking	Telemetry	*	*	*
IEC 61850 MMS	IEC 61850 MMS Client.	IEC 61850 MMS servers.	Telemetry	*	*	*
Lacroix Sofrel	LACBUS-PC	FR1000 RTU	Telemetry	*	*

3S CODESYS

The CODESYS Driver was designed specifically to get in communication with 3S Software softPLC, connected through TCP/IP network protocols. An instance of the CODESYS SoftPLC can be installed on a desktop computer or on a Windows CE panel; the driver is able to access both. Our driver support PLC versions 3. The runtime and the Programming environment are different for the two versions, for the configuration of the 3S system, please refer to their documentation.

Interface Device: 3S Software CODESYS SoftPLC version 3
Manufacturer: 3S
Requirements: In order to communicate with the device it is necessary to install the “CODESYS Gateway” application on the PC where NExT will be executed.
Import Tags: Import Tags supported
Operating System: WIN 64

Download links:

Movicon.NExT – Ver. 4.0.300

B&R

The “B&R PVI” Driver was designed specifically for use with B&R devices that implement the communication protocol INA2000.The connection can be a point-to-point serial connection (RS-232 or RS-422) or a multi-point Ethernet connection. This driver requires the installation of B&R PVI libraries.

Interface Device: devices that implement the communication protocol INA2000
Manufacturer: B&R
Requirements: B&R PVI libraries.
Import Tags: Support Import Tags
Operating System: WIN 32/64

Download links:

Movicon.NExT – Ver. 4.0.300

SQL Driver

SQL Driver is able to connect to a database server that supports the TCP/IP protocol.
This driver creates a new table in an existing database which allow to record the tag’s name and value. During the runtime the driver create the chosen table in the database and creates one record per tag, once it created all the records it updates only the value of the value column of the specified tag.

Interface Device:
Manufacturer: Progea
Requirements:
Import Tags: Import Tags not supported
Operating System: WIN 32/64

Download links:

Movicon.NExT – Ver. 4.0.300

IEC 61850 MMS

IEC 61850 is a standard for the design of electrical substation automation, and is a part of the IEC Technical Committe (57 TC57) reference architecture for electric power systems. Data objects and control functionality of a substation are modelled into different standard logical nodes, which can be grouped under different logical devices.

Interface Device: IEC 61850 MMS servers
Manufacturer: –
Requirements:

The driver does not support:

Generic Substation Events (GSEE/GOOSE)
Logs
Sampled Values

Import Tags: Support Import Tags
Operating System: WIN 32/64

Download links:

Movicon.NExT – Ver. 4.0.300

Fill out the form to download the selected file.

Company*
Name and Surname*
Position*
Country*
Country
Email*
Phone*
Privacy*
- I accept the conditions according to the law. Privacy Policy
CAPTCHA

Fill out the form to download the selected file.

Company*
Name and Surname*
Position*
Country*
Country
Email*
Phone*
Privacy*
- I accept the conditions according to the law. Privacy Policy
CAPTCHA

Fill out the form to download the selected file.

Company*
Name and Surname*
Position*
Country*
Country
Email*
Phone*
Privacy*
- I accept the conditions according to the law. Privacy Policy
CAPTCHA

Fill out the form to download the selected file.

Company*
Name and Surname*
Position*
Country*
Country
Email*
Phone*
Privacy*
- I accept the conditions according to the law. Privacy Policy
CAPTCHA

MQTT Client

MQTT Client is a driver over TCP/ IP that implements a “publish-subscribe” lightweight messaging protocol client side. MQTT Client driver requires an MQTT message broker. The broker is responsible for distributing messages to interested clients based on the topic of a message.

Interface Device:
Manufacturer: MQTT
Requirements:
Import Tags: Import Tags not supported
Operating System: WIN 32/64

Download links:

Movicon.NExT – Ver. 4.0.300

Facilities Pack

• BacNET/IP Annex J
• Konnex – EIB
• SNMP Manager (as Agent)
• Altri…

Telemetry Pack

• IEC 60870-5-104
• IEC 61850 (in progress)
• Lacroix-Sofrel LACBUS

IIoT Pack

• PubNub
• Progea Cloud IIoT Databoom
• MQTT (in progress)

Automation Pack

• Siemens S7 TCP
• Siemens S7-MPI
• Siemens S7-PPI
• Siemens TIA PORTAL
• Ethernet/IP
• GE Ethernet SRTP-2
• Omron FINS Ethernet
• Omron Ethernet IP

• Hilscher CIFX Interface Cards (Profibus, Profinet..)
• Mitsubishi FX Series
• Mitsubishi FX3U TCP
• Mitsubishi Q Series
• Panasonic FP MEWTOCOL
• SAIA-Burgess S-BUS Ethernet
• Beckhoff TwinCAT
• Altri…

Fanuc GE srtp2

The GE SRTP2 driver has been developed to exchange data, through Ethernet lan, with GE PLCs series 90. The driver acts as a client. The SRTP2 protocol (Service Request Transfer Protocol 2), often referred to simply as SRTP, is an optimized version of the obsolete protocol SRTP.

Interface Device: GE PLCs series 90.
Manufacturer:GE Fanuc
Requirements: Standard Ethernet cables
Import Tags: Support Import Tags
Operating System: WIN 32/64

Download links:

Movicon.NExT – Ver. 4.0.300

IoT Progea Databoom

The incoming data collected by the service are processed and inserted in a non-relational database which is automatically replicated in several servers to ensure that recorded information is always available. All data are saved automatically by a backup program.

Interface Device: –
Manufacturer: Progea
Requirements: Internet connection
Import Tags: Import Tags not supported
Operating System: WIN 32/64

Download links:

Movicon.NExT – Ver. 4.0.300

OPC UA Client

OPC Unified Architecture is the new generation from the OPC foundation for data security, reliability and transport.
The OPC UA integrates the current OPC industrial standards with important features such as platform independency, scalability, increased availability and Internet capability.
The OPC UA is no longer based on DCOM and has been designed based on a service-oriented architecture (SOA).

Interface Device: –
Manufacturer: Progea
Requirements: OPC UA Server
Import Tags: Import Tags not supported
Operating System: WIN 32/64

Download links:

Movicon.NExT – Ver. 4.0.300

Mitsubishi Melsec QE

The “Mitsubishi MELSEC-Q TCP” Driver was designed for use with Mitsubishi MELSEC-Q PLCs equipped with a QJ71E71 communication module, over Ethernet networks.

Interface Device: Mitsubishi Q PLCs or any compatible device.
Manufacturer: Mitsubishi
Requirements: Standard Ethernet cables
Import Tags: Support Import Tags
Operating System: WIN 32/64

Download links:

Movicon.NExT – Ver. 4.0.300

Siemens S7 TCP

The S7 TCP Driver was designed specifically for the use with Siemens S7 300, 400, 1200, 1500 and VIPA System 200V, 300V, 300S and 500S series. This driver implement the ISO over TCP protocol and the natural physical media is an Ethernet network, eventually connected with switches or hubs. Obviously, the PLC has to have an Ethernet port or an Ethernet module in its rack.

Interface Device: Simatic-S7- 300 – 400 – 1200 – 1500
Manufacturer: Siemens
Requirements: Siemens S7 – TCP protocol – SIMATIC PLCs S7-300/400/1200/1500 and compatibles PLC series
Import Tags: Support Import Tags
Operating System: WIN 32/64

Download links:

Movicon.NExT – Ver. 4.0.300

Twincat

This driver needs the ADS software library (from Beckhoff) in order to communicate with the routing system that rules every intermodule exchange of data. PLCs and I/O systems are controlled by the TwinCAT System Control Module, make sure that this Configuration end monitoring system is correctly set up and enabled, before establishing communication.
For the use of TwinCAT System Control and PLC, please refer to Beckhoff TwinCAT documentation.

Interface Device: Beckhoff TwinCat SoftPLC Beckhoff I/O
Manufacturer: Beckhoff
Requirements: Require ADS Software Library
Import Tags: Support Import Tags
Operating System: WIN 32/64

Download links:

Movicon.NExT – Ver. 4.0.300

Hilscher CifX Multiprotocol

The drivers allow you to access the data card based on the Hilscher netX chip, using the API functions provided by the software “cifX Device Driver”. These are advanced functions that render the protocol used by the Hilscher transparent to the driver in order to communicate with the BUS devices. By configuring the Hilscher card in this way will enable the driver to be used for communicating with both master and slave devices using the following protocols:

AS-Interface
CAN open
CC-Link
CompoNet
DeviceNet
EtherCAT
POWERLINK
PROFIBUS-DP
PROFINET IO RT

Interface Device: All devices that support one of the communication protocols listed above.
Manufacturer: Hilscher
Requirements: An Hilscher NETcoreX board properly configurated.
Import Tags: Import Tags Not Supported
Operating System: WIN 32/64

Download links:

Movicon.NExT – Ver. 4.0.300

IEC 60870-5-104

The IEC Technical Committee 57 ( Working Group 03) have developed a protocol standard for telecontrol, teleprotection, and associated telecommunications for electric power systems. The result of this work is IEC 60870-5. Five documents specify the base IEC 60870-5.

The documents are:

IEC 60870-5-1 Transmission Frame Formats
IEC 60870-5-2 Data Link Transmission Services
IEC 60870-5-3 General Structure of Application Data
IEC 60870-5-4 Definition and coding of Information Elements
IEC 60870-5-5 Basic Application Functions

The IEC Technical Committee 57 have also generated a companion standard IEC 60870-5-104 especially for remote controlled units RTU, connected to a Controlling Station either via TCP/IP networking. The IEC 60870-5-104 is based on the five documents IEC 60870-5-1 – 5 and IEC60870-5-101.

Interface Device: Any RTU compliant, connected to a Controlling Station via TCP/IP networking.
Manufacturer: IEC
Requirements: IEC 60870-5-104 for remote controlled units RTU via TCP/IP
Import Tags: Import Tags not supported
Operating System: WIN 32/64

Download links:

Movicon.NExT Ver. 4.0.300

Konnex -EIB

The EIBus – Konnex Driver was designed specifically to get in communication with Building Automation Devices, connected through EIB bus, or with the new Konnex System, which is the compatible successor of EIB.
EIB devices, like lights, dimmer, lamps, curtains, switches, …, have to be configured for their net address with the aid of the ETS software. In order to operate correctly with EIB devices, a good knowledge of the Konnex architecture and of the ETS software is required. For more information about this bus and the related tools, please refer to www.knx.org
Our driver can operate in Ethernet communication, where the link between IP network and EIB devices are one or more EIBNet/IP routers. Each communication channel requires a dedicated interface.

Interface Device: Any Konnex/EIB devices
Manufacturer: Konnex
Requirements: KONNEX- EIB – Falcon Library (Ethernet)
Import Tags: Support Import Tags
Operating System: WIN 32/64

Download links:

Movicon.NExT – Ver. 4.0.300

Mitsubishi Melsec FX TCP

The Melsec FX TCP Driver was designed specifically for communication with Mitsubishi FX3U PLCs, connected to the PC through the Ethernet module FX3u-ENET. A number of PLCs can be connected over the Ethernet network. The FX3u-ENET module needs to be configured with a dedicated Mitsubishi software tool.

Interface Device: PLC MELSEC-FX3U
Manufacturer: Mitsubishi
Requirements: Mitsubishi – MELSEC-FX3U Ethernet TCP
Import Tags: Support Import Tags
Operating System: WIN 32/64

Download links:

Movicon.NExT – Ver. 4.0.300

Mitsubishi Melsec FX

The Mitsubishi MELSEC-FX Driver was designed for use with Mitsubishi MELSEC-FX, FX1N, FX2N, FX3U PLCs or any compatible device. The communication protocol used by the driver is the serial point-to-point protocol configurated on the controller’s standard RS-422 port.

Interface Device: PLC Mitsubishi MELSEC-FX, FX1N, FX2N, FX3U
Manufacturer: Mitsubishi
Requirements: Serial Cable
Import Tags: Support Import Tags
Operating System: WIN 32/64

Download links:

Movicon.NExT – Ver. 4.0.300

Modbus RTU

The Modbus Serial Driver was designed for use with serial devices that support the Modbus RTU or Modbus ASCII protocol as “Master”.
Modbus Protocol is a messaging structure developed by Gould Modicon in 1979, used to establish master-slave/client-server communication between intelligent devices. It is a de facto standard, truly open and the most widely used network protocol in the industrial manufacturing environment. It is literally implemented by hundreds of vendors on thousands of different devices in order to transfer discrete/analog I/O and register data between control devices.

Modbus is an application layer messaging protocol, positioned at level 7 of the OSI model, that provides client/server communication between devices connected on different types of buses or networks.
The Modbus protocol has been accepted by the IEC as a Public Available Specification (IEC PAS 62030).
The Modbus Serial driver has been developed to support a wide range of Modbus RTU compatible devices available in the automation world.

The driver permits also to send broadcast messages (only output requests) on device ID 0.

Interface Device: Any standard Modbus Slave device
Manufacturer: Modbus
Requirements: Modbus RTU or Modbus ASCII protocol as Master
Import Tags: Support Import Tags
Operating System: WIN 32/64

Download links:

Movicon.NExT – Ver. 4.0.300

Modbus Slave

Modbus Slave driver has been developed on the basis of Modbus protocol, according to Modbus specification. MODBUS Protocol is a messaging structure developed by Gould Modicon in 1979, used to establish master-slave/client-server communication between intelligent devices.It is literally implemented by hundreds of vendors on thousands of different devices in order to transfer discrete/analog I/O and register data between control devices. MODBUS is an application layer messaging protocol, positioned at level 7 of the OSI model, that provides client/server communication between devices connected on different types of buses or networks.
The MODBUS protocol has been accepted by the IEC as a Public Available Specification (IEC PAS 62030). The MODBUS Slave driver has been developed to support a wide range of MODBUS compatible devices available in the automation world. The driver simulates one or more MODBUS slaves, defined as stations. The data of the slaves can be defined as tasks, associating the tags of the supervisor to the MODBUS addresses of a slave (station).

Interface Device: Any standard Modbus Master device
Manufacturer: Modbus
Requirements: Modbus RTU or Modbus ASCII protocol as Slave
Import Tags: Support Import Tags
Operating System: WIN 32/64

Download links:

Movicon.NExT – Ver. 4.0.300

Modbus TCP

Modbus TCP driver has been developed on the basis of Modbus protocol, according to Modbus specification. The driver acts as a client and allows communication with many devices classes supporting this protocol, such as PLCs, remote terminal units, analyzers, I/O modules, sensors, controllers, AC/DC drive control devices. This driver does not implement the Modbus messaging on TCP/IP service. Modbus TCP/IP specification has been developed in 1999. The specification of this protocol and its implementation guide can be obtained on www.modbus.org.
The devices can be direct part of an Ethernet network. The use of interconnection devices like bridge, router or gateway for interconnection between the TCP/IP network and a serial line sub-network permits connections of Modbus serial line client and server end devices. In this latter case, it is important to understand that the communication protocol Modbus TCP/IP is not simply MODBUS over TCP, i.e. is not equal to the MODBUS serial protocol wrapped by a TCP frame. So please be aware that this driver does not support those RS485/Ethernet gateways that add a TCP/IP wrapper to the serial Modbus messages.
The option “String Length” to Exchange Tags in string format has now been added (supported character format: ASCII).

Interface Device: Any standard Modbus Ethernet device
Manufacturer: Modbus
Requirements: Modbus TCP-IP Ethernet protocol
Import Tags: Support Import Tags
Operating System: WIN 32/64

Download links:

Movicon.NExT – Ver. 4.0.300

Omron Ethernet-IP

EtherNet/IP is an industrial networking standard that takes advantage of commercial off-the-shelf Ethernet communication chips and physical media. IP stands for ‘industrial protocol’ and it is what distinguishes this network. Unlike many options in the industrial Ethernet crowd, EtherNet/IP uses an open protocol at the application layer. Moreover, more than one vendor or organization backs EtherNet/IP. It is the only standard supported by three networking organizations: ControlNet International (CI), the Industrial Ethernet Association (IEA) and the Open DeviceNet Vendor Association (ODVA).

See the web site http://www.ethernet-ip.org for more information.

This driver has been expressly thought to communicate with Omron NJ and NX PLC series over the Ethernet network. This driver uses symbolic tag addressing (tags names) with Ethernet/IP native commands.

Interface Device: Omron SYSMAC PLCs
Manufacturer: Omron
Requirements: Omron Ethernet-IP protocol
Import Tags: Support Import Tags
Operating System: WIN 32/64

Download links:

Movicon.NExT – Ver. 4.0.300

Omron Fins Ethernet

The Omron FINS Ethernet driver was designed specifically for the use with OMRON programmable controllers. This protocol connect a number of OMRON controllers over an Ethernet network.

Interface Device: Omron SYSMAC PLCs
Manufacturer: Omron
Requirements: Omron FINS Ethernet protocol
Import Tags: Support Import Tags
Operating System: WIN 32/64

Download links:

Movicon.NExT – Ver. 4.0.300

Panasonic FP

Panasonic FP allows the data exchange with Panasonic FP series PLCs, using the MEWTOCOL protocol. The driver has been developed for both serial and Ethernet communication.
Before using the driver the PLC must be properly configured through the specific programming software. The Windows version is named “FPWIN GR” or “FPWIN PRO”. The PLC communication parameters may be set by the “OptionPLC Configuration…” menu command in the GR package, while in the PRO package the menu command is under “OnlineCommunication Parameters”.
The Panasonic FP Driver can communicate with either the PLC programming port (“Tool port”) or the PLC “COM port”. For the latter it is important to set the parameter “Port Selection” to the value “Computer Link”.

Note that with this setting the “Communication Format” parameters named “Terminator” and “Header” can be left to their default values (“CR” and “STX not exist”) because they are not used.

The Panasonic FP Driver can also communicate with FP PLCs using TCP/IP over Ethernet.
Panasonic FP Driver supports also the communication via the USB port of the PLC. In this case, the software “Panasonic Electric Works PLC Virtual UART” must be installed.

Please refer to Panasonic documentation for further information.

Interface Device: PLC Panasonic FP Series
Manufacturer: Panasonic
Requirements: Panasonic MEWTOCOL protocol – serial and Ethernet communication
Import Tags: Support Import Tags
Operating System: WIN 32/64

Download links:

Movicon.NExT – Ver. 4.0.300

Saia Data Mode

The SaiaDataMode driver has been developed to communicate with Saia-Burgess PCD series PLCs. It is a direct driver, not based on Saia libraries, making it possible to communicate in different ways:

S-BUS mode via S-BUS network (RS485). The connection needs a RS232/RS485 converter, in order to connect a serial port of the PC with a RS485 net that can hold a number of PLCs. (S-BUS).
S-BUS mode via Ethernet. The PC and the PLCs have only to be connected in the same Ethernet TCP/IP network, with address compatible with the current subnet. (SOCKET).

Interface Device: All PCD series PLCs with RS-485 or Ethernet port
Manufacturer: Saia
Requirements: Saia PLC – S-BUS, Ethernet, Serial (Data mode)
Import Tags: Import Tags not supported
Operating System: WIN 32/64

Download links:

Movicon.NExT – Ver. 4.0.300

BacNet/IP

The BACnet/IP driver provides communication with devices supporting BACnet protocol in its implementation over IP.
BACnet is a protocol defined by ASHRAE (American Society of Heating, Refrigeration and Air-conditioning Engineers). The ANSI/ASHRAE Standard 135-2004 document contains the protocol definition. Annex to the document contains specification of the BACnet transported over IP, which is the implementation chosen for this driver.

The BACnet protocol has a number of services that permit to read/write the properties of the configured Data Objects. In order to get the value of the property “Present_Value”, it is possible to choose between two ways : sending a request “ReadProperty” or subscribing a COV (Change Of Value) notification for the Data Object. Using the service “ReadProperty” means polling the object with a request, and receive an answer containing the data; using COV notification means subscribing to the device for a notification when the “Present_Value” of a Data Object changes. This second way results in a spontaneous message from the device, whenever a Present_Value changes its value, reducing the traffic at the minimum.

Interface Device: Any standard device BacNet/IP
Manufacturer: BacNet
Requirements: Binary / Analog / Multistate – I/O and value
Import Tags: Support Import Tags
Operating System: WIN 32/64

Download links:

Movicon.NExT – Ver. 4.0.300

Siemens S7 TIA

The S7 TIA Symbolic Driver was designed specifically to access the SIMATIC S7-1200 and S7-1500 with symbolic addressing and accessing the optimized data blocks.
This driver needs the ACCON-AGLink software library (from DELTALOGIC Automatisierungstechnik GmbH) in order to communicate with server devices. The file of this library is named “AGLink40.DLL”.

Interface Device: Siemens SIMATIC PLCs S7-1200/1500 series
Manufacturer: Siemens
Requirements: Require Ethernet board, Support PLC S7-1200 and S7-1500 , ACCON-AGLink software library
Supported protocol: S7-TCP/IP TIA
Import Tags: Support Import Tags
Operating System: WIN 32/64

Download links:

Movicon.NExT – Ver. 4.0.300

Siemens S7 MPI

The Siemens S7 MPI PC Adapter was designed specifically for use with Siemens S7 300 and 400 PLCs communicating via the MPI interface connected on the Serial RS232 port. The Siemens S7 MPI serial port adapter handles MPI connectivity on the PC.
This driver supports VIPA PLCs through Green Cable as well.
Any other device compatible with the S7-MPI protocol is supported.

The Siemens S7 MPI PC Adapter and the S7 MPI driver have been designed to allow more than one master device to exist on the network. This allows a programming package to operate while this driver is running or while additional PCs are accessing the network.

Interface Device: Simatic-S7-300 – 400
Manufacturer: Siemens
Requirements: Siemens S7 – MPI protocol for PC Adapter – SIMATIC PLCs S7-300/400 series
Import Tags: Support Import Tags
Operating System: WIN 32/64

Download links:

Movicon.NExT – Ver. 4.0.300

Siemens S7 PPI

The Siemens S7 PPI Driver was designed specifically for use with Siemens S7 200 PLCs communicating via the PPI interface connected on the Serial RS232 port. The Siemens S7 PPI serial port adapter handles PPI connectivity on the PC.
Any other device compatible with the S7-PPI protocol is supported.

The S7 PPI driver supports Single Master Multidrop RS485 PPI networks via the Siemens PPI Serial cable. See the section “Cable” for more information.

Interface Device: Simatic-S7-200
Manufacturer: Siemens
Requirements: Siemens S7-Simatic S7-200 PPI protocol
Import Tags: Support Import Tags
Operating System: WIN 32/64

Download links:

Movicon.NExT – Ver. 4.0.300

SNMP Manager

The SNMP driver permits to communicate with devices that support the SNMP (Simple Network Management Protocol) protocol. SNMP is an Internet-standard, introduced in 1988. This driver works as a SNMP “Manager”, and supports the following versions of the protocol: SNMPv1, SNMPv2c.
This driver implements the SNMP “Get” and “Set” requests to, respectively, read and write data from and to the connected devices. This driver does not manage “Trap” notifications. The devices must act as SNMP “Agents”. The database of a SNMP agent is called MIB (Management Information Base). Each value stored in a MIB can be addressed using a “readable” name or a numeric value, expressed in dot-notation, called OID (Object IDentifier). This driver uses OIDs in numeric format to address data.

Interface Device: Any SNMP compliant device
Manufacturer: Various
Requirements: SNMP Manager, for any devices supporting SNMP protocol acting as SNMP Agents
Import Tags: Import Tags not supported
Operating System: WIN 32/64

Download links:

Movicon.NExT – Ver. 4.0.300

EtherNet/IP

EtherNet/IP is an industrial networking standard that takes advantage of commercial off-the-shelf Ethernet communication chips and physical media. IP stands for ‘industrial protocol’ and it is what distinguishes this network. Unlike many options in the industrial Ethernet crowd, EtherNet/IP uses an open protocol at the application layer. Moreover, more than one vendor or organization supports EtherNet/IP. It is the only standard supported by three networking organizations: ControlNet International (CI), the Industrial Ethernet Association (IEA) and the Open DeviceNet Vendor Association (ODVA).

Interface Device: PLC-5, SLC-500, MicroLogix, ControlLogix, CompactLogix and FlexLogix
Manufacturer: Rockwell Automation (Allen Bradley)
Requirements: Rockwell Allen-Bradley – EtherNet/IP (PLC-5, SLC-500, MicroLogix, ControlLogix, CompactLogix and FlexLogix)
Import Tags: Support Import Tags
Operating System: WIN 32/64

Download links:

Movicon.NExT – Ver. 4.0.300

PubNub

PubNub is a driver based on the Data Stream Network (DSN). PubNub is like a global Content Delivery Network (CDN), but streams realtime data using the web.
A Data Stream Network (DSN) is optimized for serving dynamic content (i.e. ‘data in motion’) in realtime.
PubNub’s globally distributed network infrastructure powers two core services:

Publish/Subscribe: this is the messaging pattern used to stream data in realtime across the PubNub network.
BLOCKS: this enables you to run code directly inside the PubNub network, which is executed in your data as it is being streamed between senders and receivers.

The driver PubNub supports only the publish/subscribe model.
PubNub Inc also provides client libraries for board platforms including Raspberry Pi, Arduino, Texas Instruments, and Microchip.

Interface Device: all devices that supports PubNub programmable network
Manufacturer: PubNub
Requirements: –
Import Tags: Import Tags not supported
Operating System: WIN 32/64

Download links:

Movicon.NExT – Ver. 4.0.300

LACBUS PC

The Lacbus-PC driver permits communication with lacroix-sofrel devices using the FR1000 front end, that operates as a Gateway, incapsulating messages in Lacbus-PC communication protocol packets from and for devices.
The Lacroix -sofrel devices use 4 different types of communication protocols (Lacbus-RTU, Sofbus-PL, Lacbus-SMS, Sofbus-SMS). The Lacbus-PC driver supports only two of these protocols:

Lacbus-RTU
Sofbus-PL
Interface Device: Driver supports all Lacroix-Sofrel devices that implement the Lacbus RTU and Softbus PL communication protocols by means of connecting with FR 1000.
Manufacturer: Lacroix-Sofrel
Requirements: FR1000 front end
Import Tags: Support Import Tags
Operating System: WIN 32/64

Download links:

Movicon.NExT – Ver.3.1.123

Sign in

Restore password

Industrial communication has exceeded the capabilities of traditional OPC UA Servers

Each Connext communication protocol supports automatic tag importation from the field or PLC for smoother and faster communication configuring.

Communication Protocols

The OPC UA Server Connext offers a suite of communication protocols. Users can activate them one at a time or several at a time when using the Multidrivers option.

Listed below are the I/O Drivers that are available and included within the software product

Subscribe to Progea’s Newsletter

Contact us!

Menu