Home

Aparian has released the DeviceNet Router/B providing intelligent data routing between either EtherNet/IP or Modbus TCP/RTU and a DeviceNet network. This allows the user to integrate DeviceNet devices into a Rockwell Logix platform (e.g., ControlLogix or CompactLogix) or any Modbus Client or Server device with minimal effort. This module serves as a replacement for the existing DeviceNet Router series A.

The module can operate in one of two DeviceNet modes:

  • DeviceNet Scanner - When the module operates as a DeviceNet Scanner, it can connect to a maximum of 63 DeviceNet Devices. The input and output data from each DeviceNet Device can be mapped to any of the operating interfaces (EtherNet/IP Target, Modbus Server, Modbus Client, or EtherNet/IP Originator).
  • DeviceNet Device - When the module is configured to be a DeviceNet Device, it will allow the module to have input and output data sizes of up to 128 bytes.

The primary interface can be configured to operate in one of five modes: 

  • EtherNet/IP Originator - In this mode the module can either exchange data with an EtherNet/IP device using either Explicit messaging (Unconnected/Class 3) or a Class 1 cyclic connection. 
  • EtherNet/IP Target - The module will be owned by a EtherNet/IP originator using a Class 1 cyclic connection.  
  • Modbus Client - In this mode the module will communicate with Modbus Server devices using either TCP, RTU232, or RTU485.
  • Modbus Server - In this mode various Modbus Clients can communicate with the module over TCP, RTU232, and RTU485 simultaneously. 
  • PCCC Client - The DeviceNet Router is able to asynchronously exchange data between a DeviceNet polling master (scanner) and an Ethernet PCCC device.

The DV Scanner allows interfacing between a Rockwell Automation Logix system and the DeltaV™ M-series IO. (DeltaV™ is a mark of one of the Emerson Process Management family of companies.)

The DV Scanner connects to a Rockwell Automation Logix Controller (e.g. ControlLogix or CompactLogix) via EtherNet/IP and connects to the DeltaV™ M-series LocalBus via a Right Carrier Extender (KJ4001X1-NA1) using a standard D-shell cable (KJ4002X1-BF2). This allows the DV Scanner to connect to, and control, the IO in an M-series system.

The following IO cards are supported:
• KJ3001X1-CA1 – 32 Channel, 24Vdc Dry Contact, Digital Input (DI)
• KJ3204X1-BA1 – 32 Channel, 24Vdc High-Side, Series 2 Digital Output (DO)
• KJ3222X1-BA1 – 8 Channel, 4-20mA HART, Series 2 Analog Input (AI)
• KJ3221X1-BA1 – 8 Channel, 4-20mA HART, Series 2 Analog Output (AO)
• KJ3001X1-BA1 – 8 Channel, 24Vdc Isolated, Digital Input (DI)
• KJ3001X1-BG1 – 8 Channel, 24Vdc Isolated, Digital Output (DO)
• KJ3002X1-BC1– 8 Channel, 4-20mA, Analog Input (AI)
• KJ3002X1-BB1– 8 Channel, 4-20mA, Analog Output (AO)

To aid in migration, the DV Scanner provides a Shadow mode where the DV Scanner can run in parallel with the existing DeltaV™ M-series controller. In this mode the existing CPU is controlling the IO cards and the DV Scanner is listening-in and providing the input and output readback data to the Logix.

Aparian has recently released the FF Link module providing an easy-to-configure interface between FOUNDATION™ Fieldbus (FF) H1 devices and either EtherNet/IP (Target or Originator) or Modbus TCP (Master or Slave). This module serves as a replacement for the legacy 1788-EN2FFR and 1788-CN2FFR devices with the ability to import the configuration from their legacy 1788-xN2FFR AOP configuration.

The FF Link operates as an FF H1 master allowing EtherNet/IP devices (e.g. Rockwell Automation Logix platform) or Modbus devices to exchange process, alarming, and diagnostic data with H1 devices as well as provide parameterization and asset management of H1 devices using either the Slate software or Device Type Managers (DTMs).

Up to 32 FOUNDATION™ Fieldbus H1 devices are supported by the FF Link. The data is formatted into the engineering units for use in either a Logix platform or Modbus Master/Slave device by using the automatically generated mapping imports for Logix User Defined Data Types (UDTs) or padding for Modbus Registers.

The FF Link supports module redundancy when in EtherNet/IP Target mode, where two identically configured FF Link modules operate in an “Active – Standby” strategy.

The module’s dual Ethernet ports can be configured for either a Linear or Ring (Device Level Ring – DLR) Ethernet topology.

The FF Link will allow the user to monitor and extract FOUNDATION™ Fieldbus H1 device alarms from each H1 device on the connected H1 fieldbus from either a Logix controller or Modbus Master/Slave device.

 

The Enhanced ControlNet Router provides intelligent data routing between either EtherNet/IP or Modbus TCP/RTU and a ControlNet network. This allows the user to integrate ControlNet devices into a EtherNet/IP based Rockwell Logix platform (e.g., ControlLogix or CompactLogix) or any Modbus Master or Slave device with minimal effort.

The ControlNet Router also provides intelligent data routing between ControlNet and Ethernet PCCC (CSP). This will allow the user to connect new PanelView Plus devices (with no ControlNet interface) to existing ControlNet networks.

The Enhanced ControlNet Router now also supports owning ControlNet IO by scheduling the ControlNet network in the Slate software environment whilst the ControlNet Router is operating as a ControlNet Keeper. The Enhanced ControlNet Router can also own EtherNet/IO IO whilst being a ControlNet Target.

The CANopen Router/B module provides intelligent data routing between either EtherNet/IP or Modbus TCP/RTU and the CANopen bus network. This allows the user to integrate CANopen devices into a Rockwell Logix platform (e.g., ControlLogix or CompactLogix) or any Modbus Master or Slave device with minimal effort. The module can be configured to be either a CANopen Master or CANopen Slave allowing the user to not only integrate CANopen devices into a Logix or Modbus system, but to also allow the user to use EtherNet/IP or Modbus devices in an existing CANopen network (by using the CANopen Router/B in Slave mode).

  • Module has various operating interfaces:
    • EtherNet/IP Target (Class 1 connection as well as Direct-To-Tag Logix tag access)
    • Modbus Slave (TCP, RTU232, and RTU485)
    • Modbus Master (TCP, RTU232, and RTU485)
    • EtherNet/IP Originator (Class 1 connection with up to 5 EtherNet/IP devices and Explicit Messaging with up to 5 EtherNet/IP devices).

The CANopen Router/B can have up to 124 CANopen Slave devices (when operating as a CANopen Master) each with up to 32 PDOs. When operating as a CANopen Slave the module can emulate up to 128 PDOs with various CANopen node addresses.

The CANopen Router/B can map up to 100 Service Data Objects (SDOs) from various CANopen Slaves into any of the of the operating interfaces (EtherNet/IP Target, Modbus Slave, Modbus Master, or EtherNet/IP Originator) similar to the mapping of CANopen Slave Process Data Objects (PDOs).

The CANopen Router/B also supports NMT management and LSS Node and Bit Rate Assignment as well as Time Synchronization and Emergency message handling on the CANopen network.

See  CANopen Router/B.