Communication Tools & Protocols for Opto 22 Products

Development environment and integration support

Opto 22 SNAP PAC programmable automation controllersOpto 22 products support a wide variety of development environments and protocolsBecause Opto 22 products—both current and legacy—are based on open standards, you can use them with a variety of programming tools and communication protocols. In addition to monitoring and controlling sensors, machines, and equipment, you can exchange data with devices, databases, systems, software applications, and web services.

Thanks to open standards, Opto 22 products can make data available for integration, storage, analysis, and Industrial Internet of Things (IIoT) applications.

The table below shows the development tools and communication protocols you can use with Opto 22 products. Some require free software development kits (SDKs) or integration kits, listed in the Notes column.

made_in_the_usa.pngRemember that Pre-sales Engineers are available to help you with your application, and you receive free Product Support on all products you buy. All Opto 22 products are designed, manufactured, and supported in the U.S.A. from our headquarters and factory in Temecula, California. 

You can also download this information as a PDF.

Please note: Shaded cells indicate legacy products, which are not recommended for new development. 

Development Environment and/or Protocol Purpose Opto 22 Products Notes
Development Environments
C, C++, C#, Java, JavaScript, Perl, Python, or any other JSON-compati­ble programming lan­guage Access I/O point and variable data in a SNAP PAC controller, using the PAC’s REST API PAC Project and SNAP-PAC R-series or S-series controller See developer.Opto22.com for complete API documentation and steps for getting started.
Requires PAC firmware R9.5a or higher.
Access data in a groov® Data Store using the groov API groov See groov Build and View User’s Guide (form 2027). See API documentation within groov Build (choose Help > groov Public API).
Requires groov R3.3a or higher.
C, C++, Java, JavaS­cript, Perl, Python, or any other Raspberry Pi-compatible pro­gramming language Use a Raspberry Pi to monitor and control industrial digital sensors & devices - Digital I/O Carrier Board for Raspberry Pi
- G4PB8H or G4PB16H rack and G4 digital I/O modules
- SNAP-D4M rack and SNAP digital I/O modules
See developer.Opto22.com for getting started steps and code samples.
C++ Read or write to memory map addresses in the brain or controller - SNAP PAC controllers
- SNAP PAC brains
- E1 and E2 brain boards
PAC-DEV-OPTOMMP-CPLUS
- SNAP Ethernet I/O
- SNAP Simple I/O
- SNAP Ultimate I/O
- SNAP-LCE controller
.NET Read or write to I/O point and vari­able data in the PAC’s control pro­gram (PAC Control™) strategy PAC Project and SNAP PAC controller PAC-DEV-CONTROLLER-DOTNET

Read or write to memory map addresses in the brain or controller

- SNAP PAC controllers
- SNAP PAC brains
- E1 and E2 brain boards
PAC-DEV-OPTOMMP-DOTNET
Communicate with current loop devices using the HART® protocol HART SNAP I/O module(s) PAC-DEV-HART-DOTNET
Requires HART SNAP I/O module(s): SNAP-AIMA-iH, SNAP-AOA-23iH
Node-RED Wire together hardware devices, databases, web services, APIs - SNAP-PAC R-series
- SNAP-PAC-S series
- groov
Node-RED nodes for SNAP PACs (requires PAC firmware R9.5a or higher).
Node-RED node for groov
GROOV-AR1 groov Box includes Node-RED (requires groov Admin 1.570.44 or higher).
See developer.opto22.com.
Protocols and Data Exchange Options
BACnet/IP Communicate with devices on a BACnet/IP network PAC Project and SNAP PAC controller PAC-INT-BAC-IP
Requires PAC Project R9.4a or higher and PAC firmware R9.4a or higher.
BACnet MS/TP Communicate with systems using the BACnet protocol over RS-485 (serial) PAC Project and SNAP PAC S-series con­troller PAC-INT-BAC
Requires PAC Project R8.2a or higher.
CAN Receive data from systems using the CAN protocol PAC Project and SNAP PAC controller and SNAP-SCM-CAN2B PAC-INT-CAN-RX (Receive only)
Requires SNAP-SCM-CAN2B CAN com­munication module with firmware R1.0d or lower and PAC Control R9.2a or higher.
Transmit to and receive data from devices using the CAN protocol PAC Project and SNAP PAC controller and SNAP-SCM-CAN2B PAC-INT-CAN-RXTX (Transmit & receive)
Requires SNAP-SCM-CAN2B CAN com­munication module with firmware R2.0d or higher and PAC Control R9.2a or higher.
DF1 Communicate with older Allen-Brad­ley® drivers or PLCs using the DF1 protocol PAC Project and SNAP PAC controller PAC-INT-ABDF1
OptoControl and SNAP-LCM4 or M4 con­troller OPTOINTAB
DNP3 Communicate with systems using the DNP3 protocol PAC Project and SNAP PAC controller PAC-INT-DNP3 
Requires PAC Control Professional R8.1 or higher.
EtherNet/IP™ Allow Allen-Bradley PLCs to use SNAP-PAC I/O, using the Ether­Net/IP protocol - SNAP PAC controllers
- SNAP PAC EB brains
Direct communication over EtherNet/IP.
FTP (client) Work with data files - SNAP PAC controllers
- SNAP PAC EB brains
Direct communication over Ethernet.
FTP (server) Work with data files - SNAP PAC controllers
- SNAP PAC EB brains
Direct communication over Ethernet.
- SNAP Ultimate I/O
- SNAP Ethernet I/O
Direct communication over Ethernet.
HART Communicate with current loop devices using the HART protocol PAC Project and SNAP PAC controller and HART SNAP I/O module(s) Requires HART SNAP I/O module(s).
HART SNAP I/O module(s) and SNAP PAC R-series con­troller or SNAP PAC brain Custom program built using PAC-DEV-HART-DOTNET.
Requires HART SNAP I/O module(s).
HTTP
HTTPS
Communicate with other devices & software - SNAP PAC S-series
- SNAP PAC R-series
- groov
HTTP/HTTPS server is built in.
Requires PAC firmware R9.5a or higher.
IEC-60870 Communicate with systems using the 60870-5-101 and 60870-5-104 proto­cols PAC Project and SNAP PAC controller PAC-INT-IEC60870-5
Requires PAC Control Professional R9.3a or higher.
microSD card Local data storage - SNAP PAC S-series
- SNAP PAC R-series
Built-in microSD card slot (to 32 GB)(1)
mistic Communicate with legacy mistic I/O SNAP PAC S-series and PAC Project Professional Use legacy versions of the PAC Control, PAC Display™, and PAC Manager™ User’s Guides.
Also see the FactoryFloor to PAC Project Migration Technical Note.
Modbus®/TCP Exchange data with Modbus devices over Ethernet groov Direct Modbus master.
PAC Project and
SNAP PAC controller
For memory map addresses, direct Mod­bus slave-only communication.
For PAC Control data, use PAC-INT-MB (includes master and slave for both Ether­net and serial networks).
SNAP PAC EB brains Direct Modbus slave-only communication.
E1 and E2 brain boards Direct Modbus slave-only communication.
ioProject and SNAP Ultimate I/O IOP-INT-MBTCP
Modbus RTU
Modbus ASCII
Exchange data with Modbus devices over a serial network PAC Project and SNAP PAC controller PAC-INT-MB (includes master and slave for both Ethernet and serial network).
ioProject and SNAP Ultimate I/O IOP-INT-MBSER
OptoControl and SNAP-LCM4 or M4 con­troller(2) OPTOINTMB
Exchange data with Basler DGC-2020 Digital Genset Controller PAC Project and SNAP PAC controller PAC-INT-MBBAS
Requires PAC Control R9.0a or higher.
OPC UA Communicate as a client with sys­tems and equipment compatible with OPC UA groov Requires Enterprise platform on either groov Box or groov Server for Microsoft® Windows®.
OPC DA 2.0 Communicate as a server with OPC DA 2.0-compatible systems and equipment OptoOPCServer™ Included in PAC Project Professional or available for separate purchase.
OPC DA 1.0 Communicate as a server with OPC DA 1.0-compatible systems and equipment OptoServer Included in legacy FactoryFloor software suite.
OptoMMP Read and write memory map data in Opto 22’s OptoMMP-based brains and controllers - SNAP PAC controllers
- SNAP PAC brains
- E1 and E2 brain boards
PAC-DEV-OPTOMMP-DOTNET or
PAC-DEV-OPTOMMP-CPLUS
- SNAP Ultimate I/O
- SNAP Ethernet I/O
- SNAP Simple I/O
- SNAP-LCE controller
PAC-DEV-OPTOMMP-CPLUS
Optomux (serial)
Optomux (Ethernet)
Use Optomux protocol with I/O E1 & E2 brain boards Use Optomux Protocol Drivers & Utilities (compatible with Win XP/2000 only).
Pamux High-speed control of digital I/O PCI-AC51 or PCIe-AC51 adapter card and B4, B5, or SNAP-B4 brain PC-PAMUX-SDK (compatible with Win­dows 8/7/Vista/XP/2000 only).
Peer-to-peer Communicate between controllers SNAP PAC controllers See PAC Control User’s Guide for Scratch Pad method.
See developer.opto22.com for using PAC's RESTful API.
- SNAP Ultimate I/O
- SNAP-LCE controller
See PAC Control User’s Guide (Legacy Edition) for Scratch Pad information.
PPP Communicate over a dial-up modem SNAP PAC S-series
SNAP PAC R-series
Direct communication.
PROFIBUS® DP Communicate with PROFIBUS DP systems PAC Project and SNAP PAC controller and SNAP-SCM-PROFI PROFIBUS-DP Master Software 
Requires SNAP-SCM-PROFI module.
SMTP Send email - SNAP PAC controllers
- PAC Display™
SMTP client with authentication and attachments.
- SNAP Ultimate I/O
- SNAP Ethernet I/O
SMTP client.
SNMP Allow network management systems to communicate with non-IT devices, including controllers, brains, and their connected I/O, through an SNMP management console - SNAP PAC controllers
- SNAP PAC EB brains
Direct communication.
- Use OPTOMIB1 for SNMP v1-compliant Management Systems.
- Use OPTOMIB2 for SNMP v2-compliant Management Systems (Requires firmware version R8.2a or higher, or R9.4b or higher for high-density digital modules).
- SNAP Ultimate I/O
- SNAP Ethernet I/O
Direct communication.
Use OPTOMIB1 (SNMP v1-compliant Management Systems). Requires firmware version R5.0 or higher on SNAP Ultimate I/O.
SQL database Exchange data between Opto 22 system and SQL databases PAC Display or OptoDataLink™ and SNAP PAC controller
PAC Project and SNAP PAC controller Custom programs using the PAC’s REST­ful API
Requires PAC firmware R9.5a or higher.
groov Custom programs using the groov Data Store REST API.
Requires groov R3.3a or higher.
SSI Acquire data from linear or rotary transducers using the serial synchro­nous interface (SSI) protocol SNAP-SCM-SSI communi­cation module and SNAP PAC R-series con­troller or SNAP PAC brain See the SNAP SSI Module User’s Guide.
TL1 Integrate PAC Control with systems using the TL1 protocol PAC Project and SNAP PAC controller PAC-INT-TL1 (Requires PAC Project R8.2a or higher.)
TCP/IP
UDP/IP
Communicate over this Internet layer - groov
- SNAP PAC controllers
- SNAP PAC EB brains
- E1 and E2 brain boards
Built-in communication.
- SNAP-LCM4 and M4 con­trollers
- SNAP Ultimate I/O
- SNAP Ethernet I/O
Built-in communication.
1 PACs manufactured after November 2008 have a card slot; firmware R9.4a and loader R6.1a or higher required for microSD cards above 2 GB.
2 Requires an M4SENET-100 Ethernet card

 

Opto 22 Pre-Sales EngineersQuestions? We're here to help.

Free Pre-sales Engineering help

Free Product Support from experienced engineers

 

Call 800-321-6786 (toll-free in the U.S and Canada)

Or 1+951-695-3000