The PA Link module simplifies the implementation of PROFIBUS PA by combining an EtherNet/IP and ModbusTCP Linking device with an internal isolated power conditioner and bus terminator.
The PA Link can either operate as a PROFIBUS DPV0/DPV1 master allowing EtherNet/IPThe PA Link can either operate as a PROFIBUS DPV0/DPV1 master allowing EtherNet/IP devices (e.g. Rockwell Logix platforms) or Modbus devices to exchange process, alarming, and diagnostic data with PROFIBUS PA devices as well as provide parameterization and asset management of slave devices using Device Type Managers (DTMs).
The module supports up to 32 PA slave devices and is capable of exchanging up to 2 kilobytes of PROFIBUS data with either a Rockwell Automation Logix controller or any Modbus TCP master or slave device.
The internal power conditioner is capable of supplying up to 420 mA with a software configurable over-current limit. It can also be disabled for applications requiring an external power conditioner.
The PA Link can synchronize to an NTP Server allowing for automatic time synchronization. The PA Link can synchronize to an NTP Server allowing for automatic time synchronization. It also supports an onboard non-volatile event log for improved fault finding.
The PA Link supports module redundancy allowing two PA Link masters to be connected to the same PROFIBUS PA segment in a one-active-one-standby strategy.
The module hosts two Ethernet ports which can be configured in a Device Level Ring or Linear topology.
Configuration is achieved using Aparian's free downloadable Slate configuration environment. Slate generates PROFIBUS PA device specific UDTs and mapping code which can be imported into Studio 5000, allowing even complex systems to be configured in minutes.
The PA Link also provides DPV1 communication allowing the user to exchange DPV1 Class 1and Class 2 data with each slave device. The PA Link Gateway DTM can be used to configure and parameterize each slave device using Device Type Manager (DTM) technology.
The PA Link will allow the user to monitor and extract DPV1 alarms from each slave device on the connected PROFIBUS PA fieldbus.
The PA Link provides a range of statistics and tools to provide a detailed diagnostic overviewof each PA Link which speeds-up fault finding. The Slate configuration utility allows the user to perform a PROFIBUS PA packet capture of the running fieldbus which can be used to analyse the bus behaviour and packets received. The PA Link also provides global and device specific statistics.
The FF Link allows the user to interface Foundation Fieldbus (FF) H1 devices to EtherNet/IP (Target or Originator) or Modbus TCP (Master or Slave).
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).
The Primary Interface can be configured to be any one of the following four interface modes:
A Logix controller can own the FF Link over EtherNet/IP using up to four class 1 connections. This will allow the FF Link to exchange data with the Logix controller using the input and output assembly of the EtherNet/IP Class 1 connections. Data from H1 devices are mapped to the Logix controller over EtherNet/IP.
Modbus TCP Master
The data from H1 devices will be written to, or read from, the module’s internal Modbus Registers. The Modbus Auxiliary Map can then be used to configure the Modbus data exchange between multiple remote Modbus Slave devices and the module’s internal Modbus registers. The Modbus communication utilizes Modbus TCP.
Modbus TCP Slave
The data from H1 devices will be written to, or read from, the module’s internal Modbus Registers using the internal mapping functions. These Modbus registers can be accessed by a remote Modbus Master using Modbus TCP.
As an EtherNet/IP originator, the module can use one of two methods to read and write data to and from the EtherNet/IP network:
- EtherNet/IP Class 1 Connection
The FF Link can be configured to own EtherNet/IP IO by using the Slate software to configure the Class 1 connections. Each FF Link can own up to 10 EtherNet/IP devices. Data from the EtherNet/IP IO (via the input and output assemblies) can be exchanged with the H1 devices.
- EtherNet/IP Explicit Messaging
This allows the FF Link to exchange data with up to 10 EtherNet/IP devices using explicit messaging over EtherNet/IP. The module can use either Class 3, Unconnected Messaging (UCMM), or Logix Tag (Direct-To-Tag) to exchange data with the remote EtherNet/IP devices with configurable Class, Instance, Attribute values (when using UCMM or Class 3). Logix Tag messages are used to exchange data with a Logix controller by directly writing to or reading from Logix tags. The user can browse to the Logix controller (using the Slate Target Browser) as well as browse the Logix Controller Tag list (using the Slate Tag Browser) to select the desired destination Tag.
The FF Link has a built-in Isolated Power Conditioner which can supply up to 420mA. The power conditioner is protected against a configurable overcurrent limit. The module also has a configurable built-in fieldbus terminator.
The FF Link uses an internal mapping strategy allowing the user to map any FF H1 data to any supported interface and vice versa.
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 latter ensures alignment with the 16-bit data structure.
The FF Link supports module redundancy when using EtherNet/IP Target mode. This allows two identically configured FF Link modules to operate in an “Active – Standby” strategy. Using the provided Logix Add-On-Instruction (AOI), the H1 data from the Active FF Link is marshalled to the Logix user tags. Should the Active FF Link fail for any reason (e.g. loss of power, network failure, bus failure), then the previously Standby FF Link will automatically become the new Active module.
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.
A range of statistics and tools are available to provide a detailed diagnostic overview of each FF Link which simplifies commissioning. The Slate configuration utility allows the user to perform an H1 packet capture of the running fieldbus which can be used to analyse the bus behaviour and packets received. The FF Link also provides global and device specific statistics.
The FF Link module has two Ethernet ports allowing the user to configure either a Linear or Ring (Device Level Ring – DLR) Ethernet topology. The Ethernet ports can also be setup for port mirroring allowing for better fault analysis.
The FF Link can synchronize to an NTP Server allowing for automatic time synchronization. It also supports an onboard non-volatile event log for improved fault finding.
|Connectors||2 x 3-Way Terminal|
|Intrinsically Safe (IS) applications||Supported|
|Advanced H1 Scheduling||Supported|
|Maximum Slave Devices||32|
|Internal Power Conditioner Voltage||Maximum: 23.0 V DC
Minimum: 19.0 V DC
|Internal Power Conditioner Current||Maximum: 420 mA – Max. Ambient Temperature <= 50 °C
Maximum: 320 mA – Max. Ambient Temperature <= 60 °C
Maximum: 220 mA – Max. Ambient Temperature <= 70 °C
Note: Includes 20mA for internal MAU
|Internal Termination||100 Ω - Software Enabled|
The DV Scanner provides an interface between DeltaV™ M-series IO and a Logix system using multiple EtherNet/IP class 1 connections. The DV Scanner supports up to 32 DeltaV™ M-series IO cards and consumes 8 Logix IO (Class 1) connections.
Within the Slate environment each DV IO card can be configured to match the application. 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)
Using the EDS AOP (Add-On-Profile) in Studio 5000, the DV Scanner can be added directly into the Logix IO tree. AOIs (Add-On-Instructions) are provided for both Standalone and Redundant architectures and facilitate the mapping of IO and diagnostic information to meaningful (UDT) structures.
In the case of a redundant system, the AOI also automatically switches between the Active and Standby DV Scanner.
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.
The DV Scanner hosts two Ethernet ports which can either be used as an unmanaged switch or in a Device-Level-Ring (DLR) topology providing Ethernet redundancy.
The DV Scanner has a range of diagnostics, statistics, and tools to support the user during the migration process. This will speed up fault finding and reduce down-time.
The DeltaV Scanner connection to the MSeries I/O requires a Right Carrier Extender using a standard D-shell cable.