![[note]](Images/noteicon.png)
The Allen-Bradley scan task uses the Allen-Bradley Interchange software to communicate to ethernet based PLCs. You will have to have the Interchange software already installed and configured on the HP machine before starting up the scan task.
The scan task supports both polling and Spontaneous Report By Exception (SRBX) messaging.
The Bailey Network 90 Scan Task provides the ability to poll a Bailey Controls Computer Interface Unit (CIU) for data. This is provided as a standard RTAP/Plus RTU scan task.
The driver establishes the point index list in the CIU upon initialization. Points may be left connected or disconnected between each scan, thereby allowing control of the Network 90 communications load.
|
This scan task is now discontinued due to the discontinuance of the CIU card from Bailey. This scan task will be continued to be supported. |
The Broadcast scan task is strictly an output only scan task. The scan task will send out IP multicast/unicast messages.
IP multicasting provides a mechanism for sending a single datagram to a group of systems. Only systems that have joined the multicast group will receive the datagram.
Multicast datagrams are transmitted and delivered with the same "best effort" reliability as regular unicast IP datagrams. There is no guarentee that the datagram will arrive intact at all members of the multicast group or in the same order as the datagrams were sent.
Membership in a multicast group is dynamic. Systems can join and leave groups at any time.
A Class D IP address in the range 224.0.0.0 to 239.255.255.255 is a "multicast address". It is also known as a "host group address", since datagrams with a multicast destination address can be received by all hosts that have joined the group that an address represents. The address 224.0.0.0 is reserved, and 224.0.0.1 is assigned to the permanent group of all IP hosts.
Multicast addresses provide a limited form of broadcasting, but without the problems and limitations of traditional broadcasts.
Sending datagrams to a multicast address is analogous to transmitting radio signals on a particular frequency. Just as you must tune a radio receiver to the particular frequency, you must join a multicast group in order to receive the multicast datagrams. All that is required between sender and receiver is a properly configured multicast router(s).
IP unicasting provides a mechanism for sending a single datagram to a single system.
Now available for RTAP on Linux.The Broadcast Receiver scan task is strictly an SRBX input only scan task. The type in the message received is associated with a particular record in the scan input table. The scan task will receive IP unicast/multicast messages.
IP multicasting provides a mechanism for sending a single datagram to a group of systems. Only systems that have joined the multicast group will receive the datagram.
Multicast datagrams are transmitted and delivered with the same "best effort" reliability as regular unicast IP datagrams. There is no guarentee that the datagram will arrive intact at all members of the multicast group or in the same order as the datagrams were sent.
Membership in a multicast group is dynamic. Systems can join and leave groups at any time.
A Class D IP address in the range 224.0.0.0 to 239.255.255.255 is a "multicast address". It is also known as a "host group address", since datagrams with a multicast destination address can be received by all hosts that have joined the group that an address represents. The address 224.0.0.0 is reserved, and 224.0.0.1 is assigned to the permanent group of all IP hosts.
Multicast addresses provide a limited form of broadcasting, but without the problems and limitations of traditional broadcasts.
Sending datagrams to a multicast address is analogous to transmitting radio signals on a particular frequency. Just as you must tune a radio receiver to the particular frequency, you must join a multicast group in order to receive the multicast datagrams. All that is required between sender and receiver is a properly configured multicast router(s).
IP unicasting provides a mechanism for sending a single datagram to a single system.
Now available for RTAP on Linux.The BSAP Scan Task support the BSAP protocol using the OpenBSI product from Bristol Babcock. This scan task is available for RTAP/NT 8.0 only.
The BSAP Scan Task requires that OpenBSI version 3.1 or greater be already installed on the machine in which the scan task will be run. The OpenBSI runtime should be purchased separately from Bristol Babcock and is not supplied as part of the scan task.
Use the OpenBSI utilities to configure the "communication lines" to the Bristol Babcock RTU's. The scan task does not provide any communication configuration capabilities. The name of the "communication line" used in the OpenBSI utilities are the same name as the RTAP communication ports point name.
The BSAP Scan Task supports both polled and spontaneous report by exception (SRBX) requests. The SRBX requests support the BSAP RBE (Report By Exception) messages and the BSAP alarm messages.
Now available for HP-UX.Now available for RTAP on Linux.
The Dynamic Data Exchange (DDE) Scan Task provides a bi-directional link between RTAP/Plus and a DDE Application. The DDE Application may be in a remote node on another type of processor, typically MS Windows.
Data can be moved in either direction at timed intervals. It supports all standard DDE messages. Loads on the real-time system can be controlled thru configuration.
|
This scan task is now discontinued due to the discontinuance of the NetDDE software from Wonderware. This scan task will be continued to be supported. |
The DMS-2 Scan Task provides a link to get data from DMS-2 power monitors.
Data can be retrieved at timed intervals. It supports all of the data values returned from the DMS-2 power monitor.
The DNP Scan Task provides the ability to poll a device that supports the DNP 3.0 protocol. This is provided as a standard RTAP/Plus RTU scan task.
The following set of objects are supported:
Binary Input, all variations Binary Input Change, all variations Binary Output Status, all variations Control Relay Output Block,
variation 01 Pattern Control Block, variation 02 Pattern Mask, variation 03 Binary Counters, all variations Frozen Counters, all variations Counter Change Events, all
variations Frozen Counter Change Events, all
variations Analog Input, all variations Frozen Analog Input, all variations Analog Change Event, all variations Frozen Analog Event, all variations Analog Output Status, all variations Analog Output, all variations Time and Date, variation 01 Time and Date with Interval,
variation 02 Time and Date - Common Time of
Occurance, all variations Time Delay, all variations The Fisher Provox Chip Scan Task provides the ability to interface RTAP/Plus to a Provox Distributed Control System (DCS). The interface is provided as a standard RTAP/Plus RTU scan task that is used in conjuction with a CHIP database and Network Interface Unit (NIU).
The scan task provides the ability to move data between the DCS and RTAP/Plus or RTAP and the DCS. Typical applications have used an RTAP/Plus system as a front end SCADA system which provides remote data on the DCS consoles for operator viewing and control. In addition, the RTAP/Plus system has been used to provide high level services such as data conversion or leak detection that could not be easily provided on the DCS system.
The Foxboro scan task provides functionality which allows an Rtap scan system to acquire real time data from Foxboro DCS systems based around an AP-51. A separate instance of the scan task has to be configured for every Foxboro DCS system. Each instance of the scan task deals with exactly one Foxboro system.
Field data maintained within the AP-51 can be scanned on a regular and on demand basis. The scan task supports scanning of the following data types:
boolean (digital) values short integer values (8 bits) integer values (16 bits) long integer values (32 bits) time values floating point values (analogues) string values short packed booleans (16 bits) long packed booleans (32 bits) Time values in the Foxboro DCS system are either stored in long integers (as seconds since Jan. 1, 1970) or as strings. Both types are supported by the scan task.
The scan task also provides functionality to write setpoint values to the DCS system for each of the above point types.
The Landis and Gyr Scan Task provides the ability to poll a device that supports the Telegyr protocol developed by Landis and Gyr. This is provided as a standard RTAP/Plus RTU scan task.
The scan task supports:
All
reporting functions All change reporting functions Grouping of analogs for
configuration Grouping of analogs for polling SOE log reporting All output functions RTU configuration RTU restart Analog deadbands Firmware poll Table read/write The enhanced Modbus Master scan task implements the modbus master protocol. This is provided as a standard RTAP/Plus RTU scan task.
The protocol has been enhanced to provide data movement of floating point and 32 bit integers in the standard protocol function codes. In addition, with the use of special registers, a PRBX mode can be supported.
Now available for RTAP on Linux.The enhanced Modbus Plus Master scan task implements the Modbus Plus protocol. It supports full network communication paths. This is provided as a standard RTAP/Plus RTU scan task.
The protocol has been enhanced to provide data movement of floating point and 32 bit integers in the standard protocol function codes. In addition, with the use of special registers, a PRBX mode can be supported.
The use of this scan task requires the installation of an SA/85 card from Modicon in an EISA slot in the host computer.
The Modbus Slave Scan Task implements the modbus slave protocol. The protocol has been enhanced to provided data movement of floating point and 32 bit integers in the standard protocol function codes. Several PLCs can be simulated in one RTAP/Plus system.
Typical applications have been in system replacements in which a master device exists and polls for information from the RTAP/Plus system or in using an RTAP/Plus system to act as a data concentrator.
The enhanced Modbus TCP Master scan task implements the modbus TCP/IP protocol. This is provided as a standard RTAP/Plus RTU scan task.
The protocol has been enhanced to provide data movement of floating point and 32 bit integers in the standard protocol function codes. In addition, with the use of special registers, a PRBX mode can be supported.
Now available for RTAP on Linux.The Oracle Interface provides a bi-directional link between RTAP/Plus and an Oracle database. The Oracle database may be resident on the RTAP/Plus database server or may be in a remote node on another type of processor.
Several types of cross references can be made with each cross reference being used on multiple points in the RTAP/Plus database. Each cross reference is applicable to a particular table in the Oracle database. This allows the setup of a cross reference for each point type in an RTAP/Plus database to a point table in the Oracle database.
Data can be moved in either direction at timed intervals.
Now available for RTAP on Linux.The ROC-300 scan task implements the protocol required to communicate with a Fisher controls ROC RTU. This is provided as a standard RTAP/Plus RTU scan task.
The scan task has been implemented such that a debug output is available. The debug output shows the protocol output and input bytes and can be turned off and on for individual RTUs.
The Rogue GPS scan task implements the protocol required to communicate with the Allen Osborne Associates Turbo Rogue GPS Receiver.
The RTAP to RTAP scan task allows transfer of scalar and vector values from a remote RTAP environment into the local RTAP environment. Since the transfer uses the scan system, the data types can be intermixed (ie. read a float from the remote environment into a double in the local environment). Table values can be transferred by either reading a single record and field (scalar value) or a single field with a number of records (vector value).
The scan task mux is a software multiplexer that allows multiple scan tasks to communicate out the same physical communication port. Each scan task talks through a the slave side of a pseudo-terminal device pair. The scan task mux, receives requests and sends responses through the master side of a pseudo-terminal device. Because the scan task mux talks through the master side, the scan task mux must be started before the scan system. This is easily accomplished, by putting the scan task mux in a phase previous to the scan system manager. The scan task mux will issue a start next phase request once it has completed it's initialization.
Responses from the communication port, is strictly terminated based on an inter-character timeout value.
The scan task mux allows for a many to one multiplexing (many scan tasks through one communication port) or many to many multiplexing (many scan tasks through many communication ports). The later may be used if a single radio channel is available, but different modems are required to transmit/receive the request/response.
The TDC3000 scan task provides support for the facilities used by the Honeywell TDC3000 Distributed Control Systems (DCS). The scan task works in combination with HP's Computer Gateway Communications Unit CGCU and supports the following types of data retrieval:
real
values integer values ASCII strings relative historical values ordinal values internal LCN time values These values can be retrieved by means of a single point fetch or by means of a DDT fetch.
The scan task supports the output to the TDC on a single point basis for reals, integers, ASCII ordinal values and internal LCN time values. The scan task also supports the output to the TDC on a multiple point basis for reals, integers, ordinals and ASCII values.
The TRW Scan Task provides the ability to poll a device that supports the TRW S-70 protocol. This is provided as a standard RTAP/Plus RTU scan task.
The S-70 protocol is implemented as an asynchronous protocol due to hardware requirements of the HP computers. A conversion device to the synchronous protocol is available.