The module can be configured to produce and consume PGNs allowing the user to not only integrate J1939 devices into a Logix or Modbus system, but to also allow the user to use EtherNet/IP or Modbus devices in an existing J1939 network.

Primary Interface:

The module can use one of four Primary Interface modes:

EtherNet/IP Target

Here a remote EtherNet/IP device (e.g. a Logix controller) establishes a number of Class 1 connections to the module. J1939 data can be mapped into two 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 J1939 network:

• • • EtherNet/IP Explicit Messaging

This allows J1939 devices 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 technology

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

• • • • EtherNet/IP Class 1 connection

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

Modbus Server

The diagnostics and J1939 data will be written to, or read from, the module’s internal Modbus Registers (Holding or Input Registers). These registers can be accessed by a remote Modbus Client using either Modbus TCP, Modbus RTU232, or Modbus RTU485.

Modbus Client

The diagnostics and J1939 data will be written to, or read from, the module’s internal Modbus Registers (Holding or Input Registers). 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, or Modbus RTU485.

The J1939 Router provides auto extraction and scaling of SPNs for standard SAE defined PGNs. These SPNs can then be mapped to Logix UDTs Tags which can also be automatically generated by the Slate software. This allows the user to create a J1939 Router project with all the required PGNs and then export a Logix L5X file which contains all the required Tags and UDTs for that specific J1939 Router project. This L5X file can be imported into Logix removing the hassle of creating UDTs for the numerous PGNs.

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