DNP3 Master/Slave – (112_DNP3M_4.x)
This driver can communicate over serial or TCP/IP.
Allen Bradley (112-ABDF1-4.x)
The Cabdf1scan I/O driver is designed to communicate with Allen Bradley PLC 5’s and SLC 5’s utilizing DF1 communications protocol. This is an RS-232 interface protocol that enables RealFlex to acquire data from the remote device’s data files. The data types supported by the driver are: B-Binary bits, I-Input Image, O-Output Image, C-Counter, F-Floating Point, N-Integer (16 bits), and T-Timer. This driver will most likely be used with an Allen Bradley KF2 or KE interface module to connect the driver to the Data Highway. The driver also supports communications to the SLC series via a KF3 interface module or directly to the SLC’s RS-232 port.
Note: This I/O Driver supports serial port sharing via the Resource Manager (112-RSRC-4.x).
Allen Bradley (112-ABKT-4.x)
The Cabktscan I/O driver is designed to communicate through a KT1784 Data Highway Plus adapter card, which allows direct access to the Allen Bradley Data Highway for transfer at speeds up to 57.6 Kb. This driver utilizes the Data Highway/Data Highway Plus protocol command set. The data types supported by the driver are: B-Binary bits, I-Input Image, O-Output Image, C-Counter, F-Floating Point, N-Integer (16 bits), and T-Timer.
Note: Cabktscan requires the use of an Allen Bradley Data Highway Plus adapter card, which can be purchased from your Allen Bradley distributor.
Allen Bradley (112-ABSDKT-4.x)
The Cabsdscan I/O driver is designed to communicate through a Sutherland Schultz Data Highway Plus adapter card, which allows direct access to the Allen Bradley Data Highway for transfer at speeds between 57.6 and 115.2 Kb. This driver utilized the Data Highway / Data Highway Plus protocol command set. The data types supported by the driver are: B-Binary bits, I-Input Image, O-Output Image, C-Counter, F-Floating Point, N-Integer (16 bits), and T-Timer.
Note: Cabsdscan requires the use of a Sutherland Schultz Data Highway Plus adapter card
Allen Bradley (112-ABE-4.x)
Bendix Engine Control (112-ECS-4.x)
The Cecsscan I/O driver is designed to communicate with the Bendix Engine Control System (ECS) utilizing an RS-232 interface. Cecsscan communicates with the ECS on a one-to-one basis, i.e. each ECS system requires a separate serial port.
Best Power Technologies (112-UPS-4.x)
The Ctups I/O driver interface is designed to communicate via an RS-232 serial port with a Best Power Technologies UPS system. Ctups will read data using the “F” and “D” commands and send digital controls using the “P” command. Control password security is supported automatically if so required by the UPS system.
Bristol Babcock (112-BB-4.x)
The Cbbscan I/O driver is designed to communicate with Bristol Babcock remote devices via an RS-232 serial interface. This I/O driver uses the RTU (binary) protocol as defined in Gould Inc.’s Modbus Protocol Reference Guide and extended by Daniel Engineering for 2500 Flow Computer Host-Slave communications.
Bristol Babcock (112-BSAP-4.x)
The Cbsapscan I/O driver is designed to communicate to Bristol Babcock remote devices that support Network 3000 communications protocol. This is an RS-232 protocol, which supports communications to Bristol Babcock model 3330, 3350, 3380 and 3385 remote devices. Other remotes may be supported provided Network 3000 communication protocol is used. Cbsapscan is capable of acquiring analog and status data from the Bristol signals as well as polling for alarms from the remote device. In the event that alarms are acquired from the remote, Cbsapscan will generate the appropriate alarm within RealFlex with the remote timestamp (provided the signal has been defined within RealFlex).
Note: Currently, Cbsapscan does not support the Bristol Model 3755. Also, this driver requires that the “nettop” file defining the Bristol Network Topology be copied from the DOS / Windows system to the QNX system. This is required so that Cbsapscan can perform the proper addressing.
Cooper Power Systems (112-CPS-4.x)
The Ccps_scan I/O driver is designed to communicate with the Cooper Power Systems Form 4C reclosure via an RS-232 interface. This driver utilizes the Digital Communications Protocol as defined in the Cooper Power Systems document R280-90-12. This driver also supports retrieval of ‘Event Records’ and ‘Load Profiles’ as stored in the reclosure. A separate utility is included which provides the ability to view the event records and/or the load profiles.
Daniels (112-DAN-4.x)
The Cdanscan I/O driver is designed to communicate with the Daniels 2500 Flow Computer utilizing an RS-232 interface. The driver supports both RTU (binary) and ASCII communication modes. Cdanscan supports the acquisition of data from alias ranges: 1001 - 3000 (Status and Analog), 3001 - 5000 (Analog and Meter), 5001 - 7000 (Analog and Meter) and 7001 - 10000 (Analog and Meter). Cdanscan does not support Tank database types.
Daniels (112-DSI-4.x)
The Cdsiscan I/O driver is designed to communicate with a Daniels SolarFlow remote device using Daniels DSI protocol via an RS-232 interface. The driver is capable of supporting the different SolarFlow configurations by retrieving data by channel numbers. The Historical / Event data can also be retrieved from the remote device and stored locally on the RealFlex system as well as written directly to the RealFlex historian. A separate utility is included that provides the capability to view the historical data and events. The driver can also store this historical data in a binary format that the Daniels Data Manager program can access.
Dutec (112-IOPLEX-4.x)
The Cioplexscan I/O driver is designed to communicate with Dutec I/O Plexers, Dutec Basic I/O modules, and other “Opto-22” protocol boards utilizing either RS-232, RS-422 or RS-485 interfaces. In addition, Cioplexscan can connect directly to a single module through a Hayes compatible modem or radio that uses the RS-232 request-to-send (RTS) lead for “push-to-talk” control. Some of the modules that are supported by this driver are: 590 Temp Sensor, IV50M, IV100M, IV1, IV5, IO10, IV5B, IV10B, II420, OV5, OV10, OI420, JTCJ, ITCJ-1, ITCK, ITCK-1, and 100 RTD.
Fischer & Porter (112-FP-4.x)
The Cfpscan I/O driver is designed to communicate with Fischer & Porter devices using the ‘binary’ mode ‘data link’ communications protocol. This driver supports the following: Model 53MC500 Micro-DCI Modular Controller, Model 50KM2000 Chameleon Microcomputer Mark II, Model 53MC1100 Micro-DCI Controller, and Model 53SU1000 Micro-DCI. Cfpscan supports acquisition of the ‘L’, ‘B’, ‘C’ and ‘H’ data types from the remote devices.
Fisher ROC (112-ROC-4.x)
The Crocscan I/O driver is designed to communicate with the Fisher ROC 364 remote device via an RS-232 interface utilizing the Fisher ROC 364 communications protocol. Some of the functionality supported by Crocscan is as follows: scanning of alarm data, scanning of event data, scanning of historical data, utilizing store and for-ward messaging, etc. The driver supports the following Point Types: 1-Discrete Input, 2-Discrete Output, 3-Analog Input, 4-Analog Output, 5-Pulse Input, 6-PID (analog control loop), 7-AGA, 9-LCD, 10-AGA Flow, 11-Tank, 12-Clock, 13-System Flags, 14-Communications Port, 15-System, 16-FST (Function Sequence Table), 17-Soft Points, 19-Database, 20-Task. For additional information on any other Point Types supported, please contact RealFlex Software Technical Support.
Note: This I/O Driver supports serial port sharing via the Resource Manager (112-RSRC-4.x).
GE (112-CCM2-4.x)
The Cccm2scan I/O driver is designed to communicate through a standard RS-232 interface utilizing the GE CCM Serial Interface communications protocol. This includes the Siemens/TI 300 Series PLCs. Cccm2scan supports the acquisition of %R, %I, %Q, %AI and %AQ data types from the PLCs.
General Electric (112-GE-4.x)
The Cgescan I/O driver is designed to communicate with General Electric Series 6 and Series 90 (90/30 and 90/70) programmable controllers using the Genius I/O Bus communications protocol. This driver supports acquisition of the following data types from Series 6 PLCs: %R - Integer values (16 bit), Digital Inputs, Digital Outputs, Global Data Bits, Global Data (16 bit). The following data types are supported by the Series 90 PLCs: %R - Register Integer values, %I - Discrete Input Memory, %Q - Discrete Output Memory, %T - Discrete Temporary Memory, %M - Discrete Momentary Internal Memory, %SA - Discrete Group A, %SB - Discrete Group B, %SC - Discrete Group C, %S - Discrete System Memory, %G - Global Data (Read Only).
Note: This driver requires the use of a GE GENIUS I/O PCIM interface card that should be purchased from your GE distributor.
Harris (112-DNP-4.x)
Harris DNP-3 Protocol
Kimray (112-KIMRAY-4.x)
The Ckimray I/O driver is designed to communicate through a standard RS-232 interface utilizing the SAGE CQ-120/140/150 and KA-102 communications protocol. The driver can acquire data from the RTU Logic cards and the Flow Computer. A sample of the functionality provided by Ckimray includes: RTU time synchronization issued from RealFlex, Uploading / Downloading of Gas Chromatograph data, Uploading / Downloading of Flow Control data, Uploading / Downloading Meter Configuration data, Uploading / Downloading Analog Configuration data and Uploading of hourly and daily historical data.
Note: This I/O Driver supports serial port sharing via the Resource Manager (112-RSRC-4.x).
Kinemetrics (112-NIST-4.x)
The Cnist_clock I/O driver interface is designed to communicate via an RS-232 serial port with a Kinemetrics TrueTime 486-DC GPS RX (or protocol compatible) Satellite Clock. This interface will synchronize a stand-alone or networked RealFlex system to NIST time standards.
MetraByte (112-METRA-4.x)
The Cmetrascan I/O Driver is designed to communicate with MetraByte M1000/2000 Protocol devices via an RS-232 serial interface. Cmetrascan can be directly connected to RTUs or, it can interface via TNC packet modems or FreeWave radios
Mitsubishi (112-MIT-4.x)
The Cmitscan I/O driver is designed to communicate with Mitsubishi PLCs using an RS-232 interface. Cmitscan acquires the following data types from the PLC: X coils, Y coils, Internal Relays, Latching Relays, Step Relays, Link Relays, Timers, Counters, and Data Registers.
Modicon (112-CAC-4.x)
Ccacscan is a ‘general use” I/O driver designed to communicate with remote devices that support the Modicon Modbus communications protocol via an RS-232 serial interface. The driver supports PCU specific ASCII or RTU (binary) message mode and scan scheduling for every N cycles, N minutes, or N hours. Additionally, Ccacscan includes a configuration utility for custom definition of up to five (5) Modbus register configuration sets defining the following for up to eight (8) alias ranges: Start/End Register, Base Address, Data Type (bit, short, long, float), # Regs/Data Type, and Read/Write Function Codes
Modicon (112-MODSCAN-4.x)
The Cmodscan I/O driver is designed to communicate with remote devices that support the Modicon Modbus communications protocol via an RS-232 or TCP/IP interface. The driver supports both RTU (binary) and ASCII communication modes. Alias ranges that are supported by the driver are: 1-9999 [Status], 10001-19999 [Status], 30001-39999 [Status, Analog (16 bit integers), Meter], 40000-49999 [Status, Analog (16 bit integers), Meter], 50001 - 59999 [Analog (32 bit integers), Meter].
Please note, if this driver is used in TCP/IP mode then QNX TCP/IP Socklet w/o NFS is required.
Note: This I/O Driver supports serial port sharing via the Resource Manager (112-RSRC-4.x).
Modicon (112-MODSLV-4.x)
The Cmodslave I/O driver is designed to communicate with a Modbus Master system via an RS-232 or TCP/IP interface utilizing the Modbus RTU (binary) mode. The driver is capable of being configured to support exception reporting from a Modbus remote device. In this configuration, the remote device must be capable of concurrently supporting a Modbus Slave serial interface (if this device is to be scanned with the RealFlex Cmodscan I/O driver) as well as a Modbus Master serial interface. The driver supports the following function codes as defined in the Modbus protocol: 01- Read Coil Status, 02-Read Input Status, 03-Read Holding Registers, 04-Read Input Registers, 05-Force Coil, 06-Load Register, 15-Force Multiple Coils, and 16-Load Multiple Registers. For function codes 05, 06, 15 and 16 the driver only writes the data to the RealFlex database and does not actually send the value to the remote device.
Note: Please note, if this driver is used in TCP/IP mode then QNX TCP/IP Socklet w/o NFS is required.
Motorola (112-BGE-4.x)
The Cbgescan I/O driver is designed to communicate to the MOSCAD Modbus protocol devices using an RS-232 serial interface. This scanner uses the Remote Terminal Unit (RTU) protocol, which is a binary protocol.
Motorola (112-CIU-4.x)
The Cciuscan I/O driver communicates with Motorola ASC, EASC, and MRTU devices via an RS-232 serial interface to a Motorola INTRAC 2000 CIU. Although data acquisition is primarily achieved by unsolicited change-of-state notification from the field devices, the capability exists to post scan requests for RTU data based upon individually tunable interval timers. Cciuscan supports acquisition of data from the following groups: A – B (Status), C – H (Analog and Meter). Digital (status) Output FREEZE and UNFREEZE controls are supported for groups C – H and Analog Output (set point) controls are supported for groups E – H.
Motorola (112-MOSCAD-4.x)
The Cmoscad I/O driver is designed to communicate with Motorola RTUs utilizing the Moscad communications protocol via an RS-232 interface. This driver only supports RTU (Binary) mode of communications.
Resource Manager (112-RSRC-4.x)
Resource Manager allows dissimilar communication protocols to utilize a single RS-232 port. The communication protocols must be different enough so that remote devices don’t interpret the other protocol message. In order to use this product, the I/O drivers must be designed to utilize the serial port sharing feature. Indication as to whether or not a driver supports this feature is in the functional feature overview paragraph. In the event that the driver in question does not support this feature, a “one-time” development cost may be applied.
Siemens (112-SINEC-4.x)
The Csinecscan I/O driver is designed to communicate with Siemens 555 PLCs using a Control Technology Inc. Ethernet communications card (SINEC 505-CP2572) located in the PLC using TCP/IP. The driver is capable of supporting multiple PLCs on the same communications channel or separate PLCs on separate communications channels. Some of the data types that the driver supports are as follows: Discrete Input (X), Discrete Output (Y), Control Register (CR), Variable Memory (V), Constant Memory (K), Word Input (WX), Word Output (WY), etc. For additional data types supported contact RealFlex Technical Support.
Note: This driver requires the use of the CTI Sinec Ethernet TCP/IP (505-CP2572) interface card, which is installed in the PLC, an Ethernet card residing in the RealFlex PC, and QNX TCP/IP Runtime. The Ethernet card for the RealFlex PC and QNX TCP/IP are available through RealFlex. Refer to the Third Party Products section of the price list for additional pricing and information.
Square D (112-SYMAX-4.x)
The Csymax I/O driver is designed to communicate with Square D’s SY/MAX programmable controllers using a SY/MAX SY/LINK Network Interface card. The communications card can be directly connected to the RS-232 port on the SY/MAX PLC or connected to multiple SY/MAX PLCs through SY/NET Network Interface Modules.
Note: This driver requires the use of SY/MAX SY/LINK Network Interface card, which should be purchased from a Square D distributor.
Tejas/Valmet (112-TJSCAN-4.x)
The Ctjscan I/O driver is designed to communicate via an RS-232 interface to the Tejas / Valmet remote devices that support the Valmet Series V communications protocol via an RS-232 serial interface.
Texas Instruments (112-ETI-4.x)
The Cetiscan I/O driver is designed to communicate with Texas Instruments 8640/8644, 8641/8642/8643, and 8635 ETI Micro RTUs utilizing the ETI Dynamic Protocol via a RS-232 serial interface. Cetiscan supports the following ETI Data Types: Analog Input (AI,M056,M057), Digital Input (DI), Pulse Count Input (PCI), Pulse Duration Input (PDI), Pulse Period Input (PPI), High Speed Accumulator (HAS), Digital Output (DO), and Analog Output (AO).
TIWAY (112-TIWAY-4.x)
The Ctiway I/O driver is designed to communicate with TIWAY protocol devices via a UNILINK HOST Adapter (UHA) connected to the PC via an RS-232 serial interface cable. The UHA should be configured to operate in BDLC protocol mode, full duplex, asynchronous, MHIU/EIA and RUN mode. Some of the data types that the driver supports are as follows: Discrete Input (X), Discrete Output (Y), Control Register (CR), Variable Memory (V), Constant Memory (K), Word Input (WX), Word Output (WY), etc. For additional data types supported contact RealFlex. Software Technical Support.
Westinghouse (112-NUMA-4.x)
The Cnumascan I/O driver is designed to communicate with Westinghouse NUMA-LOGIC series PLCs via an RS-232 serial interface. Utilizing the Westinghouse NUMA-LOGIC protocol, Cnumascan supports direct PC-to-PLC, as well as PC-to-Network communications. Remote data types supported by the Westinghouse PLC are as follows: 0 (Holding Register), 1 (Output Register), 2 (Input Register), 3 (Discrete Output Force Table), 4 (Discrete Input Force Table), 5 (Discrete Output Table or Control Relay), 6 (Discrete Input Table). Status records can reference data types 0 – 6, whereas analog and meter records can only reference data types 0 – 2.
