Archives

AOI 2.0 Drive Control Emulation

This Add-on Instruction (AOI) is designed to be used in

places where the user doesn’t want to have to modify

the existing control code for Rockwell Drives. The AOIs

and UDTs are already setup to mimic the existing control

and status tags, so just find and replace the existing tags

with the newly created ABB tags and the existing RSLogix

5000 code will control the ABB drive seamlessly. Built in

scaling for customized data is available.

Supported Profile Types

• PF520 series

• PF750 series

More to come in future development

Benefits

• Benefit from pre-defined tag descriptions that mimic

tag descriptions in existing Rockwell drives

• Minimize commissioning cost

• Quickly replace existing drive with ABB without having

to rewrite PLC code

• Leverage modular programming to easily copy and

paste Add-On Instruction for additional drives

• Enjoy the flexibility and versatility of ABB drives

connected to EtherNet/IP and ControlNet network

Benefits

• Reduce development time and simplify diagnostics with

pre-defined tag descriptions and data types

• Minimize commissioning cost

• Create consistent PLC code regardless of programmer

• Easily rename tag description to an installation-specific name

• Leverage modular programming to easily copy and paste

Add-On Instruction for additional drives

• Save time and money by re-using the same User Defined

Data Type for duplicate drives

• Enjoy the flexibility and versatility of ABB drives connected

to EtherNet/IP and ControlNet networks

AOI 2.0 Drive Control Emulation

This Add-on Instruction (AOI) is designed to be used in

places where the user doesn’t want to have to modify

the existing control code for Rockwell Drives. The AOIs

and UDTs are already setup to mimic the existing control

and status tags, so just find and replace the existing tags

with the newly created ABB tags and the existing RSLogix

5000 code will control the ABB drive seamlessly. Built in

scaling for customized data is available.

Universal Connectivity – Simplifying ABB drive commissioning

and connectivity to EtherNet/IP™ and ControlNet™ networks

AOI 1.0 for New VFD Applications

This Add-on Instruction is designed to be used in new VFD

applications. The User Defined Data Type (UDT) defines the

tag descriptions, such as control word, status word,

references and actual speed & torque. UDTs provide users

with an interface that enables them to add specific tag

descriptions into the dynamic datasets supported by ABB

low voltage AC and DC drives. It will map the EtherNet/IP or

ControlNet module to the User Defined Data Type providing

a seamless and simplified connection to the network.

Supported Profile Types

• ABB Drives

• ODVA

• Transparent (16-bit and 32-bit)

Modbus RTU to Modbus conversion

Modbus field devices use usually serial mode (RTU or ASCII)

protocol while the SCADA communication uses TCP/IP based

Modbus TCP protocol. The Modbus user community has

defined the functionality for required protocol integration, that

is, how the Modbus RTU devices can talk to the Modbus TCP

SCADA system. This functionality is a protocol conversion

and it is implemented in ARC600. Many industrial devices like

PLCs and RTUs support RS-485 Modbus RTU mode. In

RS-485 mode, ARC600 can integrate unlimited number of

serial slaves to TCP/IP network (SCADA).

ARC600 has two application serial ports. Serial port 1 is

configurable to either console or data mode and it supports

only RS-232. while serial port 2 is configurable to multiple

serial modes (RS-232/RS-422/RS-485). Serial port

connectors are 9-pin D-sub (male) connectors.

IEC-101 to IEC-104 conversion

With ARC600. conventional IEC 60870-101 serial devices can

be attached to a modern TCP/IP based IEC 60870-5-104

control system. This is enabled by the protocol conversion

from IEC 60870-5-101 to IEC 60870-104. In this case,

ARC600 (IEC-101 master) uses local synchronous data

polling where it continuously sends requests and the IEC-101

device (IEC-101 slave) responds. In the direction of the

control room, the communication protocol is IEC-104 and

ARC600 can send events asynchronously as they arise while

SCADA performs only slow-period background scans.

Another advantage of the local protocol conversion is an

advanced data acknowledgement mechanism. IEC-104

allows multiple packets, and multiple events in a single

packet, to be acknowledged collectively and the packets can

be buffered up to the time of acknowledgement from SCADA.

Modbus to IEC-104 conversion

ARC600 provides support for generic Modbus RTU and

Modbus TCP devices such as ABB’s RIO600. In addition,

support is also provided for the preselected Modbus

parameters for Fault Passage Indicators (FPI). Currently,

Horstmann Compass B and Kries IKI-50 are supported.

ARC600 polls the fault indicator devices, connected to the

serial port, using Modbus protocol and converts the values to

IEC 60870-5-104. Up to four fault indicators can be

connected to one device. IEC 60870-5-104 is used to

communicate towards a SCADA via the Arctic M2M Gateway

over the available customer chosen cellular data network.

In the direction of the control room, the communication protocol is IEC-104 and

ARC600 can send events asynchronously as they arise while

SCADA performs only slow-period background scans.

Another advantage of the local protocol conversion is an

advanced data acknowledgement mechanism. IEC-104

allows multiple packets, and multiple events in a single

packet, to be acknowledged collectively and the packets can

be buffered up to the time of acknowledgement from SCADA.