1783 natr manual

Overview of the 1783-NATR Device

The 1783-NATR device facilitates connecting a small private network to a larger network without altering the private network’s IP addresses. It acts as a default gateway, translating private to public IPs using 1:1 NAT, simplifying integration.

Purpose and Functionality

The primary purpose of the 1783-NATR device is to enable seamless integration of machine networks into larger, plant-wide networks. This is achieved through Network Address Translation (NAT), specifically 1:1 NAT, which maps private IP addresses within the machine network to unique public IP addresses on the control network. Functionally, the 1783-NATR acts as a gateway, allowing devices on the private network to communicate with devices on the public network without requiring any IP address changes on the private network side. This simplifies network management and avoids potential IP address conflicts. It supports protocols like EtherNet/IP, CIP, ICMP, HTTP, and DNS. Configuration is possible via web page or EDS AOP.

Key Features and Specifications

The 1783-NATR boasts features like 1:1 NAT, support for protocols such as EtherNet/IP and HTTP, and configuration via web page or EDS AOP. It is designed for seamless network integration.

1:1 Network Address Translation (NAT)

The 1783-NATR device employs 1:1 Network Address Translation (NAT) to establish a direct mapping between private IP addresses within a machine network and public IP addresses on a larger control network. This ensures each device on the private network has a unique, corresponding public IP, enabling seamless communication and preventing IP address conflicts.

This NAT functionality allows machines with identical network settings to operate on a single line. It simplifies remote support and integration into existing network architectures. Supporting up to 32 translation mappings, the 1783-NATR facilitates the isolation of machine networks while maintaining connectivity.

Supported Protocols

The 1783-NATR device supports a comprehensive suite of protocols, enabling versatile integration within industrial networks. Key protocols include EtherNet/IP, facilitating seamless communication with Allen-Bradley PLCs and other industrial automation devices. CIP (Common Industrial Protocol) is also supported.

For general network communication, the 1783-NATR supports ICMP (Internet Control Message Protocol) for pinging and network diagnostics, HTTP (Hypertext Transfer Protocol) for web-based configuration, and DNS (Domain Name System) for hostname resolution. The device’s protocol support ensures compatibility with a wide range of network devices and applications, simplifying network integration and troubleshooting.

Performance Metrics

The 1783-NATR’s performance is characterized by its ability to handle a substantial volume of network traffic. In high-performance testing, the device demonstrated a capability of processing up to 25,000 packets per second (PPS). This metric reflects its capacity to efficiently translate network addresses and route data between networks without introducing significant latency.

However, it is crucial to recognize that actual performance can vary depending on factors such as network topology, traffic patterns, and configuration settings. Matching the speed and duplex settings of connected devices is essential to avoid errors and maintain network connectivity.

Configuration and Setup

Configuration of the 1783-NATR device can be achieved through two primary methods. Users can utilize a web page interface for simpler configurations, or employ the EDS AOP for more advanced setup options and parameters.

Web Page Configuration

The 1783-NATR device offers a web page interface for simplified configuration. Accessing this interface requires knowing the device’s initial IP address. Once connected, users can modify network settings, including IP addresses, subnet masks, and gateway configurations. This method is suitable for basic setup and allows for easy adjustment of 1:1 NAT mappings. Be sure to match the speed and duplex settings of the 1783-NATR router when you configure the Ethernet port on the device you connect to the router. The web interface streamlines the process of establishing communication between private and public networks. It also provides a user-friendly way to manage basic device functionalities and monitor network status. Make sure to save the configuration after making changes.

EDS AOP Configuration

The 1783-NATR device also supports configuration through an EDS AOP (Electronic Data Sheet Add-On Profile). This method allows integration with Rockwell Automation’s Studio 5000 environment, offering a more integrated configuration experience for users familiar with the Rockwell ecosystem. The EDS AOP provides a graphical interface within Studio 5000 to configure the device’s parameters. It offers features such as simplified management of the device’s settings and the ability to configure network settings, including IP addresses, subnet masks, and gateway configurations. This method is suitable for complex setup and allows for easy adjustment of 1:1 NAT mappings. It also includes diagnostic tools and monitoring capabilities. This integration streamlines the configuration process.

Troubleshooting and Common Issues

Users may encounter connectivity problems and RSLinx visibility issues when setting up the 1783-NATR. Addressing these common problems often involves verifying IP settings and speed/duplex configurations for connected devices.

Connectivity Problems

One common issue encountered with the 1783-NATR is the inability to establish network connectivity after the initial configuration. This can manifest as an inability to ping devices on either side of the NATR or a complete loss of network communication. Several factors can contribute to these connectivity problems.

Incorrect IP address configurations are a primary suspect. Ensure that the IP addresses, subnet masks, and gateway settings are correctly configured on both the private and public sides of the 1783-NATR. Also, verify that the devices connected to the NATR are using the correct IP addresses and gateway settings to communicate through the translated network. Mismatched speed and duplex settings between the 1783-NATR and connected devices, such as PLCs or switches, can also lead to connectivity issues; Always ensure that these settings are aligned to prevent communication errors and network instability.

RSLinx Visibility Issues

A frequent challenge encountered while using the 1783-NATR is the inability to see devices behind the NATR in RSLinx. Even after successful initial configuration, the translated side of the network may remain invisible within RSLinx. This issue often stems from how RSLinx browses the network and how the NATR handles broadcast messages.

RSLinx relies on broadcast messages to discover devices on the network, but the 1783-NATR, by design, does not forward broadcast traffic across the NAT boundary. To resolve this, you’ll need to manually add the devices to RSLinx using their translated IP addresses. Ensure that the RSLinx OPC server is configured to use the correct network interface and that there are no firewall rules blocking communication between RSLinx and the translated devices. Additionally, verify that the NATR’s routing table is correctly configured to direct traffic between the RSLinx workstation and the devices behind the NATR.

Integration with Ignition

Integrating the 1783-NATR with Ignition allows seamless communication with PLCs on a private network. Ignition connects using the NATR’s public IP, accessing PLCs via translated addresses, simplifying network architecture.

Connecting to PLCs through 1783-NATR

To establish a connection between Ignition and Allen-Bradley PLCs using the 1783-NATR, ensure the NATR device is correctly configured. Verify that you can successfully ping the PLCs from the Ignition server. Within Ignition, instead of using the PLC’s actual IP address, use the NATR’s corresponding public IP address assigned for that PLC.

Double-check that the IP address configured in Ignition matches the public IP address defined in the 1783-NATR for the target PLC. Utilizing RSLinx to confirm connectivity to the PLC through the NATR can aid in verifying the configuration.

If experiencing connection issues, review the NATR’s settings, ensuring correct IP address translations and proper network configurations. The 1783-NATR simplifies machine integration into existing networks.