Discontinued Products

GPS Time and Position Modes

The Time Sync module has optimized modes for both Time and Position functions and a custom mode as detailed below.

Mode Description
Time The module is configured to only use the GPS constellation for best time accuracy.
Position The module is configured to use GPS, SBAS and GLONASS satellite constellations to provide the most accurate positioning information.
Custom This mode allows the user to select the constellations that are needed for the required application.

Free Config Software

The Time Sync module is configured using the Aparian's Slate application. Slate offers various configuration methods. Slate can be downloaded here.

Sync with 1588 PTP and NTP Services

The module is a stand-alone device allowing it to operate across various platforms. The module can also seamlessly connect and integrate with Rockwell Automation’s Allen Bradley equipment. The module can operate in either a Logix “owned” or standalone mode. In stand-alone mode the module can be configured and connected to an Ethernet network to accurately synchronize devices using 1588 PTP and NTP. With a Logix connection the input and output assemblies will provide timing, positioning, and diagnostic information which will be available in the Logix controller environment in addition to the PTP and NTP services.

Current Time using Modbus TCP

The module can update a single Modbus slave device using Modbus TCP providing current time data.

Less Expensive Installation

The module uses an on-board GPS receiver to provide accurate time and position information. Because the module is stand-alone and connects to various devices over an Ethernet network the module can be placed as close as possible to the antenna position removing the need for costly low-loss coaxial cables.

GPS Position and Velocity

The on-board GPS receiver also provides velocity and an odometer reading allowing the user to implement the module in various vehicle and tracking applications. The GPS accuracy information provides the user/controller with quality metrics for the position, velocity, and odometer information.

NTP to PTP Synchronization

The Time Sync module can synchronize its internal clock to an external NTP source and then provide PTP messages synchronized to NTP source.

Status & Diagnostics

A built-in webserver provides detailed diagnostics of system configuration and operation, including the display of GPS time, position, and velocity, without the need for any additional software.

The HART 4 module can convert up to four analog devices int either EtherNet/IP, Modbus-TCP, or DNP3 TCP/UDP protocols. This includes 4 to 20 mA input and output devices with or without HART communications as well as 0 to 20 ma devices without HART.

The Hart 4 is available in Input or Output variations:

  • A-HRT-4I for HART input devices like process instruments.
  • A-HRT-4O for HART output devices like valve positioners.

The conversion to EtherNet/IP enables a HART device to be added directly into a Rockwell Automation Logix IO tree. The Modbus-TCP option enables a HART field device to be viewed as a Modbus Slave. The DNP3 option converts a HART field device into a DNP3 Outstation. The DNP3 option, also supports Secure Authentication, ensuring secure communications across the Ethernet network.

In addition, a rich collection of process and diagnostic information is provided directly into Logix, without the use of any explicit messaging. HART commands can also be relayed to the device using an EtherNet/IP message relay object. A DTM (Device Type Manager) is available further simplifying device configuration and management using an FDT frame. A built-in webserver provides detailed diagnostics of system configuration and operation as well as field device specific diagnostics.

The Modbus Router provides intelligent data routing between EtherNet/IP and Modbus (serial Modbus-RTU or Ethernet Modbus-TCP). NOTE: The Modbus Router 485 can communicate on serial RS485 whilst the Modbus Router can communicate on serial RS232. The Modbus Router allows the user to integrate Modbus devices into a Rockwell Logix platform (e.g. ControlLogix or CompactLogix) with minimal effort.

The router can be used to communicated with MicroLogix and SLCs.

The Modbus Router is able to transfer data from various Modbus devices to a maximum of three Logix controllers. The module operates in one of three modes, simplifying the configuration for all applications.

Mode Description Message Initiator
Reactive Tag

The Modbus Router will convert Modbus messages to Logix controller tag reads or tag writes.  (Modbus Slave)

Remote Device
Scheduled Tag

The Modbus Router transfers data between a Modbus device and a number of Logix tags, using a preconfigured scheduled.

(Modbus Master)

No Logix or remote device configuration is required.

Modbus Router
Unscheduled

The Modbus Router transfers messages received from a Logix Message Instruction.

(Modbus Master)

Logix (Msg)

The Modbus Router is configured using the Aparian Slate application. Slate offers various configuration methods, including a controller tag browser.

The module can operate in both a Logix "owned" and standalone mode. With a Logix connection the input and output assemblies will provide additional diagnostics information which will be available in the Logix controller environment.

The Modbus Router allows the user to integrate Modbus devices into a Logix system with minimal effort. No copying or mapping of data in the Logix controller is required as the Modbus Router writes directly into Logix tags.

The module also provides a range of statistics and traffic analyser to help fault find any problems.

The Modbus Router provides intelligent data routing between EtherNet/IP and Modbus (serial Modbus-RTU232, Modbus-RTU485, and Ethernet Modbus-TCP). The Modbus Router allows the user to integrate Modbus devices into a Rockwell Automation Logix platform (ControlLogix or CompactLogix) or PLC (SLC or MicroLogix) with minimal effort.

The module can be configured in one of six router modes:


Scheduled Tag

The MBR/B operates as a Modbus Client and transfers data between a Modbus device and a number of Logix tags, using a preconfigured scheduled. No Logix or remote device configuration is required. The MBR/B can execute up to 100 Modbus message instructions (e.g., Modbus Holding Register Read) and exchange the Modbus data with Logix tags in up to three Logix Controllers. Each Modbus Message instruction is executed at one of four configured rates. The Modbus data is exchanged using only one of the available ports (Ethernet TCP, RTU232, or RTU485).

Reactive Tag

The MBR/B operates as a Modbus Server and transfers data between Modbus Clients and a number of Logix tags, using a preconfigured tag map. No Logix or remote device configuration is required. The MBR/B can map up to 100 Modbus message instructions (e.g., Modbus Holding Register Read) and exchange the Modbus data with Logix tags in up to three Logix Controllers. The Modbus data is exchanged using only one of the available ports (Ethernet TCP, RTU232, or RTU485).

Unscheduled

The MBR/B operates as a Modbus Client and sends Modbus messages to Modbus devices when receiving a Logix Message Instruction. This provides the user with complete control (from Logix) of which Modbus instructions must be sent and at which frequency. The Modbus data is exchanged using only one of the available ports (Ethernet TCP, RTU232, or RTU485).

Enhanced

The user can decide if the MBR/B is operating as a Modbus Client or Server as well as if the MBR/B is operating as an EtherNet/IP Target or EtherNet/IP Originator.

In Enhanced Mode the MBR/B can be configured in any one of the four combinations:

Modbus Client - EtherNet/IP Target

Modbus Client - EtherNet/IP Originator

Modbus Server - EtherNet/IP Target

Modbus Server - EtherNet/IP Originator

 

Modbus Mode

Modbus Server

The data from the configured EtherNet/IP devices (using either Class 1 Assemblies, Explicit messaging or Logix Direct-to-Tag reads/writes) will be written to, or read from, the module’s internal Modbus Registers using the Internal Map. These registers can be accessed by a remote Modbus Client using either Modbus TCP, Modbus RTU232, Modbus RTU485, or any simultaneous combination of these.

Modbus Client

The data from the configured EtherNet/IP devices (using either Class 1 Assemblies, Explicit messaging or Logix Direct-to-Tag reads/writes) will be written to, or read from, the module’s internal Modbus Registers using the Internal Map. The Modbus Auxiliary Map can then be used to configure the Modbus data exchange between multiple remote Modbus Server devices and the module’s internal Modbus registers. The Modbus communication can be via Modbus TCP, Modbus RTU232, Modbus RTU485, or any simultaneous combination of these.

EtherNet/IP Mode

EtherNet/IP Target

As an EtherNet/IP target, the module can exchange the Class 1 data with devices on the Modbus network:

EtherNet/IP Class 1 connection

Here a remote EtherNet/IP device (e.g. a Logix controller) establishes between 1 and 5 Class 1 connections to the module. Modbus data can be mapped into four separate input and output class 1 cyclic connections to the Logix controller (allowing up to 2KB input and 2KB output to be exchanged at the requested packet interval – RPI).

EtherNet/IP Originator

As an EtherNet/IP originator, the module can use one of two methods to read and write data to and from the Modbus network:

EtherNet/IP Explicit Messaging

This allows the MBR/B to exchange data with up to 10 EtherNet/IP devices. The module can use either Class 3 or Unconnected Messaging (UCMM) to Get and Set data in the remote EtherNet/IP devices.

Direct-To-Tag

This allows the MBR/B to exchange data with a Logix controller without the need to write any application code (e.g. ladder) in Studio 5000. The Modbus data is directly read from, or written to, Logix tags.

EtherNet/IP Class 1 connection

Modbus data can be mapped to a maximum of 10 EtherNet/IP devices using input and output class 1 cyclic connections. This will allow the MBR/B to “own” the EtherNet/IP target device and exchange Modbus data using the EtherNet/IP device’s input and output assemblies.

Bridge

The MBR/B can operate as a transparent link for Modbus between different media (TCP, RTU232, and RTU485). This allows a Modbus client on Modbus TCP to communicate with Modbus devices on RS232 or RS485 and vice versa.

Concentrator

In Concentrator Mode, the MBR/B will collect data from a number of Modbus devices and provide the consolidated data to one or more Modbus Clients. The MBR/B will be a Modbus Server on one port, and Modbus Clients on the other ports. This will allow a Modbus SCADA to efficiently read the data from multiple Modbus devices, because the data from the various Modbus devices have been concentrated into the MBR/B.


The Modbus Router is configured using the Aparian Slate application. This program can be downloaded from www.aparian.com free of charge.

The module provides a range of statistics, a Modbus packet analyzer, and an Internal Modbus Register viewer to help fault find any problems.

The Modbus Router supports Modbus on three ports which can be configured from the Slate environment: Modbus-RTU232 (Serial), Modbus-RTU485 (Serial), and Modbus-TCP (Ethernet).

The Modbus Router uses isolated RS232 and isolated RS485 for Modbus serial communication providing better noise immunity. The RS232 and RS485 ports use a terminal block for convenient installation. 

The MBR/B supports security services allowing the user to configure various levels of module security.

The module has two Ethernet ports and supports Device-Level-Ring (DLR) architectures.

A built-in webserver provides detailed diagnostics of system configuration and operation, including the display of Modbus operation and communication statistics, without the need for any additional software.

The DH485 Router/B provides intelligent data routing between EtherNet/IP and DH485 which can help simplify the migration from MicroLogix and SLC systems to ControlLogix or CompactLogix platforms, where a DH485 interface is required.

The DH485 Router/B can also be used to program Allen-Bradley SLC5/03 PLCs via Ethernet. This is especially useful with certain legacy controllers that do not support Ethernet.

In addition, the DH485 Router/B can be used to connect newer PanelView Plus and PanelView 800 devices to a range of Rockwell Automation controllers. This is especially useful where newer PanelView Plus devices (supporting only Ethernet) are required to connect to controllers (new and old) via DH485.

The DH485 Router/B is able to transfer data from a DH485 device to a maximum of eight Logix controllers. The module operates in one of four modes, simplifying the configuration for all applications.

Mode Description Message Initiator
Transparent PCCC The DH485 Router/B will redirect DH485 PCCC messages to a Logix controller at a preconfigured EtherNet/IP path. Logix PLC Mapping configuration may also be required. This mode also enables remote programming using RSLogix 500. Remote Device
Reactive Tag The DH485 Router/B will convert DH485 messages to Logix controller tag reads or tag writes. No Logix PLC Mapping configuration is required. Remote Device
Scheduled Tag The DH485 Router/B transfers data between a DH485 device and a number of Logix tags, using a preconfigured scheduled.
No Logix or remote device configuration is required.
DH485 Router/B
Unscheduled The DH485 Router/B transfers messages received from a Logix Message Instruction. Logix (Msg)
AIC This will allow the user to connect a RS232 device (e.g. MicroLogix 1400) to a the DH485 network via the isolated RS485 port of the DH485 Router/B. This can be used as a direct replacement for the discontinued NET-AIC module. N/A

The DH485R/B Router is configured using the Aparian Slate application. Slate offers various configuration methods, including a controller tag browser.

The module can operate in both a Logix “owned” and standalone mode. The module can operate in both a Logix “owned” and standalone mode. With a Logix connection the input and output assemblies will provide additional diagnostics information which will be available in the Logix controller environment.

The module also provides a range of statistics and traffic analyser to help fault find anyproblems.

The router uses isolated RS232 or isolated RS485 for DH485 serial communication providing better noise immunity. The RS232 and RS485 ports use a terminal block for convenient installation.

A built-in webserver provides detailed diagnostics of system configuration and operation, including the display of received DH485 communication packets, without the need for any additional software.