gateway icon  PRODUCT SELECTOR:

Connect Your:

To:

RTA's Blog

Ensuring You Get the Best Protocol Gateway

Posted on by Scott Zukewich & Pat Lafferty
04
Apr

Here at Real Time Automation®, we specialize in making easy-to-use connectivity products, including industrial protocol gateways, embedded source code stacks and customized OEM solutions. And while protocols are easily the most important part of integrating factory floor communication, we can’t forget about the gateway hardware that houses all that technology.

There are an infinite number of variables to consider when choosing the proper hardware for your specific application.

  • Is a barrel connector for power acceptable or do you need a terminal block?
  • Is a DB9 male connector acceptable for serial communication or do you need a terminal block that doesn’t have all nine pins called out as a DB9 would?
  • Better yet, what certifications does your application require, like UL or CE or Div1Class2?

These are just some of the questions that need to be answered to ensure you get what you need.

In this blog, we go over some of the more technical aspects of our gateway hardware to help you navigate the specific variables of your application and select the option that best suits your needs based on the equipment and protocols you’re working with.

First, let’s organize the major protocols that are available into four physical layer categories.

  • Ethernet Protocols: BACnet/IP, EtherNet/IP, Ethernet TCP/IP, PROFINET, Modbus TCP/IP and Web Interface
  • Serial Protocols: ASCII, BACnet MS/TP, DF1 and Modbus RTU
  • CAN Protocols: DeviceNet and J1939
  • USB Protocols: USB Class 3 and Class 7

Much like the protocols within each category, each of these platforms have their own unique set of pros and cons. The best hardware option for your application will be based on your priorities and configuration requirements as well as the specifications and limits of each hardware variation. Below are RTA’s seven hardware options with a brief overview of their specifications and best use cases.

    N700

  • Power (Terminal Block, 7V-24V DC, 12V @90mA)
  • Certifications (UL, C/UL, CE, FCC, RoHS)
  • Ethernet Communication (1 available)
  • Serial Communication (2 Male DB9)
    • Port 0: RS-232 or RS-485 or RS-422
    • Port 1: RS-232
    • Limits: None
  • Application LEDs (0 available)
  • Reasons to Use
    • Dual Serial protocols running RS-232
    • Serial communication requires a Male DB9 connector
    • Serial communication and an Ethernet communication protocol
    • Serial Hardware/Software Flow Control required
    N34

  • Power [Barrel Connector or Terminal Block (pins 1 & 5)]
  • Certifications (UL, C/UL, CE, FCC, RoHS)
  • Ethernet Communication (1 available)
  • Serial Communication (1 Terminal Block and 1 Male DB9)
    • Port 0/1: RS-232 or RS-485 or RS-422 or CAN
    • Limits: 1 RS-232, 2 RS-485, 1 RS-422, and 1 CAN
  • Application LEDs (2 available)
  • Reasons to Use
    • Dual Serial protocols running RS-485
    • Dual Serial protocols running RS-422 and RS-485
    • Serial Hardware/Software Flow Control required
    • A CAN protocol is running and an Ethernet protocol
    • A CAN protocol is running and a Serial protocol
    • Div1Class2 Certified
    NNA1

  • Power (Terminal Block)
  • Certifications (UL, C/UL, CE, RoHS)
  • Ethernet Communication (1 available)
  • Serial Communication (1 Terminal Block)
    • Port 0: RS-232 (Pins 1, 2, 3) or RS-485 (Pins 3, 4, 5)
    • Limits: None
  • Application LEDs (2 available)
  • Reasons to Use
    • Dual Ethernet protocols running on the same network
    • Serial communication and an Ethernet protocol
    NNA4

  • Power (Terminal Block)
  • Certifications (UL, C/UL, CE, RoHS)
  • Ethernet Communication (1 available)
  • Serial Communication (1 Terminal Block)
    • Port 0: RS-485 (Pins 1, 2, 3)
    • Port 1: RS-485 (Pins 3, 4, 5)
    • Limits: None
  • Application LEDs (2 available)
  • Reasons to Use
    • Dual Ethernet protocols running on the same network
    • Serial communication and an Ethernet communication protocol
    • Dual Serial protocols running RS-485
    NNCU

  • Power (Terminal Block)
  • Certifications (CE, RoHS)
  • Ethernet Communication (1 available)
  • USB Communication (2 USB Connectors)
    • Port 1/2: USB
    • Limits: Dual USB (USB Class 3 and Class 7)
  • Application LEDs (1 available + 2 USB status)
  • Reasons to Use
    • A single or dual USB device is used
    N2E

  • Power (Terminal Block)
  • Certifications (UL, C/UL, CE, RoHS)
  • Ethernet Communication (2 available)
    • Independent and Switch Mode available
  • Serial Communication (1 Terminal Block)
    • Port 0: RS-232 (Pins 1, 2, 3) or RS-485 (Pins 3, 4, 5) or RS-422 (Pins 3, 4, 5, 6, 7)
    • Limits: None
  • Application LEDs (2 available)
  • Reasons to Use
    • Dual Ethernet protocols running on different networks
    • Use of the second ethernet port for daisy-chaining devices together (Switch Mode)
    • Serial communication and an Ethernet communication protocol
    • Serial communication requires serial isolation
    • Only power available is AC
    • Div1Class2 Certified
    N70U

  • Power (Terminal Block or Barrel Connector)
  • Certifications (UL, C/UL, CE, FCC, RoHS)
  • Ethernet Communication (1 available)
  • USB Communications (2 available)
  • Serial Communication (1 Terminal Block)
    • Port 3: RS-485 (Terminal Block)
    • Port 4: RS-232 (1 Female DB9)
    • Limits: USB Class 3 and Class 7
  • Application LEDs (2 available)
  • Reasons to Use
    • Dual USB protocols
    • Single USB and a Serial protocol running RS-232 or RS-485

As you can see, there’s a lot more to picking the right gateway than just knowing which protocols you’re dealing with. But no matter what your application requirements are, Real Time Automation has the technology to move your data, the gateway hardware options to house that technology and the personnel to figure out which combination is right for you. Call RTA at 800-249-1612 to ensure you get the perfect solution for your needs. And remember: that solution is always in stock and ready to ship.

Avatar photo
Scott Zukewich & Pat Lafferty

This blog was originally written by Scott Zukewich. Since joining Real Time Automation in 2008, Scott (BS Computer Science, University of Wisconsin-Milwaukee) has become a thought leader of industrial automation communication protocols, helping thousands of customers integrate devices into control systems and industrial communication protocols into their products. He was a long-time Board Member and Treasurer for the International Society of Automation (Milwaukee Chapter) and was named to Control Engineering’s Engineering Leaders Under 40, Class of 2022. Lastly, according to the mug on his desk, he’s the World’s Best Dad. This blog was subsequently edited by Pat Lafferty, a marketing copywriter who spent the last three decades writing everything from two-word billboards to 20,000-word whitepapers.