Using your Opto 22 system as a Modbus slave over Ethernet? If so, Modbus/TCP communications are already built into SNAP PAC controllers and SNAP PAC EB brains.
Need to use your SNAP PAC controller as a Modbus/TCP master? You can do that, too. Use the Modbus Integration Kit for PAC Control. The Integration Kit contains PAC Control master subroutines, an example Modbus Master chart, and much more.
Need to communicate with a serial Modbus system? Our free Modbus Integration Kit for PAC Control connects SNAP PAC controllers via serial, as well as Ethernet, to any Modbus device.
The Integration Kit contains a set of PAC Control master subroutines, an example Modbus Master chart, a PAC Control slave subroutine, an example Modbus Slave that uses the slave subroutine, a demo data chart, and example initialization files.
As a founding member of the OPC Foundation, Opto 22 consistently supports connectivity with any OPC-compliant hardware or software. OPC driver support is built into all SNAP PAC controllers and Ethernet-based brains.
In addition, OptoOPCServer provides a fast and efficient OPC 2.0-compliant server for connecting SNAP PAC System controllers and I/O units to third-party systems and custom applications.
TCP/IP, UDP/IP, SNMP, SMTP, FTP...
The SNAP PAC System is designed on open standards. True Ethernet and standard TCP/IP provide a solid base for the system, making broad communications possible. Here are some of the Ethernet and Internet protocols built into the SNAP PAC System:
- UDP for data streaming
- FTP for transferring files
- SMTP client, for email (with authentication and attachments)
- SNMP for network management
- HTTP for communication online
- HTTPS (using SSL) for secure communication to IP devices with web interfaces
- PPP for remote communications over a modem
RS-232, RS-485/422, and More
SNAP PAC controllers are equipped with serial ports as well as Ethernet interfaces. Type and number vary—RS-232, with or without hardware handshaking, RS-485, 2-wire or 4-wire—so check the controller's specs.
In addition, SNAP serial communication modules provide more ways to connect with serial devices and systems. These modules go right on the mounting rack with analog and digital modules to provide the serial connections you need at any location:
Legacy Opto 22 Systems
The E1 digital brain board and the E2 analog brain board are drop-in replacements for the older, serial-only B1 and B2 brain boards, providing physical connections to Optomux systems using Ethernet (or serial) and integration with Modbus/TCP systems.
Legacy mistic I/O units, including B3000, B100, B200, and even G4 mistic bricks, can become part of a newer SNAP PAC System while keeping field wiring in place. See details in the SNAP PAC System Migration Technical Note.
If you're migrating from an older FactoryFloor system, you'll need to replace your FactoryFloor controller with a SNAP PAC S-series controller running PAC Control Professional.
The SNAP-PAC-S2 has four RS-485 serial ports for legacy I/O. See more information in the FactoryFloor to PAC Project Migration Technical Note.
Also be sure to see the Legacy and Current Products Comparison and Compatibility Charts, which lists all the Opto 22 products, old and new, that can be used together.
Need help with integration?
Choose an OptoPartner near you. OptoPartners provide knowledgeable assistance with your industrial control and monitoring applications. Installation, integration, system updating, and software programming are typical needs an OptoPartner can fill.
Find an OptoPartner.
SNAP PAC controllers and brains have built-in support for EtherNet/IP, the protocol used by many Allen-Bradley PLCs such as MicroLogix, CompactLogix, and ControlLogix, as well as other systems.
This built-in-support—and the distributed processing capabilities of Opto 22 I/O—make SNAP I/O ideal for use as intelligent, remote I/O in these PLC systems. (We call it IO4AB.)
In addition, SNAP PAC controllers can easily share data with systems using EtherNet/IP. Learn more in the EtherNet/IP Implementation technical note.
To communicate with Allen-Bradley Data Highway DF1 systems, use the Allen-Bradley Data Highway DF1 Integration Kit for PAC Control.
In this integration kit, subroutines provide an easy method of communicating with Allen-Bradley drivers or PLCs using the DF1 protocol. Opto 22 controllers can act as either a master or a slave device. They can be connected directly to the serial port on an Allen-Bradley PLC or to Data Highway networks using standard Data Highway interface devices.
802.11a, b, and g Wireless LAN
SNAP PAC Wired+Wireless™ controllers and brains meet Wireless LAN 802.11a, b, and g standards for physical connectivity, as well as 10/100 Mbps wired Ethernet. Wireless security includes WPA2-AES, WPA-TKIP, and WEP standards.
And then there's Opto iPAC, the mobile app that lets you wirelessly monitor and control all your Opto 22 SNAP I/O points and PAC Control variables, tables, and charts from your iOS device—iPhone, iPod Touch, or iPad.
SQL Server, Access, MySQL
To share SNAP PAC System data with company databases, use OptoDataLink software. Choose the data items you want from a convenient list of those you've already created during control programming. OptoDataLink provides multiple connections for data sharing with common SQL databases such as Microsoft SQL Server and MySQL.
BACnet and DNP3
BACnet is a communications protocol for building automation and control networks. To communicate with these systems, use the BACnet Protocol Integration Kit for SNAP-PAC-S.
Your SNAP PAC System equipped with a SNAP-PAC-S1 or SNAP-PAC-S2 controller can communicate with a BACnet MS/TP network via RS-485. (MS/TP is a Master-Slave/Token-Passing specification of BACnet.) The integration kit contains BACnet_Protocol and Master_Sub charts you can use in your PAC Control strategy.
Primarily used by utility companies, DNP3 is the Distributed Network Protocol. Opto 22 SNAP PAC controllers, using PAC Control, can connect via an Ethernet network or serial port and communicate using DNP3.
The DNP3 Integration Kit for PAC Control contains a set of PAC Control subroutines that are added to a strategy to add DNP events, an example DNP3 strategy containing the DNP3_protocol, and DNP3_CROB charts that are imported into a strategy to enable an Opto 22 controller to communicate as a DNP3 Level 2 Outstation.
Telecommunications and Specialty Protocols
You can manage telecommunication network elements (NEs) using the Transaction Language 1 (TL1) protocol, an element management protocol widely used in North America. See the TL1 Integration Kit for PAC Control, which contains an example strategy.
You can even use a SNAP PAC controller to read and write Modbus parameters to a DGC-2020 Digital Genset Controller by Basler Electric. The Basler DGC-2020 Digital Genset Controller Integration Kit for PAC Control contains PAC Control and PAC Display files provide the interface you need.
[Your Protocol Here]
Because SNAP PAC controllers support TCP, most other protocols that also support TCP can be programmed to communicate with the SNAP PAC System.
The same is true for serial. Since SNAP PACs have serial ports, with a little programming, most other devices with a serial port can communicate with them.
You have other programming options, too. OptoMMP is the open, documented, memory-mapped protocol our PACs and brains use. The OptoMMP Communication Toolkit includes C++ classes to make the job easier, and the SNAP PAC .NET OptoMMP Messaging Toolkit provides a simple, easy-to-use interface for a .NET developer.
Questions? Give us a call.
Have questions about integrating your Opto 22 system with other systems and protocols? Give us a call.
The call is free, and we're glad to help.