Trouble with your


Real Time Automation’s Enginerds® are here to help!
View some common issues and questions below.

Please select what most closely describes the issue you are experiencing

Having trouble powering the gateway? Here is a suggestion:

If the green Power LED is off, then most likely the hardware is damaged due to improper voltage or there is no power being supplied. RTA units require 8 VDC @ 230mA to 28 VDC @ 80 mA. Call the RTA support team to be issued an RMA number.

Having trouble accessing the gateway webpage? Here is a suggestion:

By default, we ship RTA units out at as DHCP (meaning we are waiting for your computer to assign it an IP address). Every unit is shipped with a CD and within it contains a document called Accessing Browser Configuration. This will give you instructions on how to setup your PC for DHCP and how to recover a lost IP Address. Be sure to turn off the wireless internet connection and run the IP Setup tool from your desktop, not from the provided RTA CD. Verify from command prompt using ipconfig that your PC is assigned a 169.254.x.x address. Once your PC has this address, it can assign RTA an address of this range.

Are you experiencing an error code? Below are the four most common error codes. For additional error codes, refer to the Diagnostic Section of your product’s User Guide.

0x1e Embedded Server Error: This can mean the Controller Slot, IP Address or Tag Name does not match what is configured on the gateway. The Tag is not defined as a Controller Scope Tag within the PLC, or the Tag does not have Read/Write privileges.

Connection Retry Delay: Displays when a valid PLC Type and IP Address is configured, and gateway tried to connect to the PLC but failed. Verify the PLC Type, IP Address, Controller Slot, and Communication Mode to ensure information entered is correct.

Error Timeout: Node Missing: This means no devices are configured. Verify the device(s) configuration is valid, i.e… Slave address, IP Address, Unit ID, Serial Setting, Wiring.

Error Code 2: The register received by the Slave is not valid. For example, if the Master device is asking for a register address of 1 and the Slave device(s) doesn’t have it this will result in this error.

Having trouble connecting to the gateway? Here are some suggestions:

One of the most common failures is due to ground faults. If your unit was working fine and then it stopped suddenly or there was a heavy storm in the area, your issue is likely a result of a ground fault. Check “no” to the question “Did any of these suggestions help to solve your issue?” and click the “Submit” button to initiate RMA.

If connecting via TCP: Make sure you can ping the target device and verify all devices are on the same network. Server/Slave devices will have an “ID” or “Slave Address”- ensure they are correct to what the Master/Client is configured for. Also check the polling speed. If the Master/Client is polling too fast, slow down the polling.

If connecting via Serial: Ensure that the serial settings of the end device matches the port configuration of the RTA device. Server/Slave devices will have an “ID” or “Slave address”-ensure they are correct to what the Master/Client is configured for. Check the RS485 (Modbus RTU) wiring and verify that TXA (-) goes to TXA (-), TXB (+) goes to TXB (+), and GND goes to GND. If it is, attempt swapping TXA (-) and TXB (+) and check to see if there is termination at two ends. Also check the polling speed. If the Master/Client is polling too fast, slow down the polling.

Having trouble moving or seeing data? Here are some suggestions:

If your data consists of all zeros, verify that the end device has meaningful data. You can use third party tools to connect your PC to the end device and verify it is sending data.

If there is data and it’s not meaningful, it could be related to little endian vs big endian. If available with the RTA product, try using the “swap words” option. TIP: if you are expecting a value of ‘123.456’ and you see ‘-0.123456489e+’ this is an indicator to swap words.

If you’re reading a 16bit unsigned value and trying to send it to a 16bit signed value, and you are seeing a negative value versus a positive value, this indicates a data type range limitation.

If you are seeing dashes (–) with the display data, this indicates that the source has not yet been validated and no data is being sent to the destination.

Verify that within the display data that the points are mapped accordingly. Make sure there are no sections that display in yellow “Point Not Mapped”.


Q: What if I ordered or received an incorrect product? Can I send it back for a replacement?

A: Depending on your application and your connection needs, the majority of RTA products can be easily flashed to a different part number to meet your needs. Contact the RTA Support team for the firmware at 262-436-9299.

Q: What is the default IP Address?

A: RTA ships units out as DHCP.  Simply locate the Accessing Browser Configuration guide on the CD or via this link.

Q: Are there any example codes for the PLC with your product?

A: Current the only example is for the 435/490 product line. We do have simple ladder Logix examples for handshaking and an AOI available for download by clicking here.

Q: What is the power requirement for your hardware?

A: All units require 12-24VDC

Q: What sort of Integration Services you provide?

A: RTA prides itself on our easy to use products; however, few have the time or desire to configure 100 data points and mapping. RTA offers custom part numbers and device template solutions to make the process as drop and place as possible. Call the RTA Solutions team for more details on these tools at 262-436-9299 or by emailing

Q: Does RTA recommend any third-party tools for troubleshooting?

A: Reference RTA’s blog called The Art of CYA: Useful Troubleshooting Tools providing information to some useful tools and adapters.