Loading...

Fisher ROC Serial

See purchasing information for more details
Download Free Demo

Product Overview

The Fisher ROC Serial device driver works in conjunction with KEPServerEX to provide data exchange between OPC/DDE clients and Remote Operation Controllers (ROC) protocol devices. 

Resources

Performance

  • Supports Ethernet Encapsulation
  • Supports Automatic Tag Generation directly from the RTU or configuration file for rapid deployment of communications
  • Operator Identification
  • Time synchronization on EFM poll, user-specified interval, or time of day
  • Modem Support
    • Automatic Dial Configuration
    • Multiple Phone Number Management
  • Read, Write, and Auto Tag Generation of User Program Data (User Defined Points)
  • Supports OpCodes 10 and 11 for reading and writing to user tables
  • Supports OpCodes 167 for single point reads
  • Supports OpCodes 180 for multiple point reads in a single request
  • Supports Advanced Statistics Tags, including _CommFailures, _ErrorResponses, and more
  • Optimized for extreme conditions (noisy communication channels and low-bandwidth)

Protocols

  • ROC

Supported Devices

  • FloBoss 100 Series
  • FloBoss 407
  • FloBoss 500 Series
  • RegFlo
  • ROC 300 Series - FlashPAC
  • ROC 300 Series - ROCPAC

Available Languages

  • English

Application Support

  • DDE Format CF_Text and AdvancedDDE
  • NIO Interface for iFIX
  • OPC .NET Service (OPC .NET) Version 1.00
  • OPC Alarms and Events (OPC AE) Version 1.10
  • OPC Data Access (OPC DA) Versions 1.0a, 2.0, 2.05a, and 3.0
  • OPC Unified Architecture (OPC UA) Version 1.02
  • SuiteLink and FastDDE for Wonderware

Release Notes

6.4.321.0

12/13/2017

  • Fixed an issue where Automatic Tag Generation for Point Type 7 and Point Type 10 would result in generating tags for Logical Point 0.
  • Added validation for data length, starting log pointer, and history point number to prevent re-sent packets from being processed again.
  • Fixed an issue where a K Factor value can be exported as Cutoff instead of Nominal K Factor.
  • Updated the parameter size for parameter #0(Device Tag) in Point Type 177's address table from 10 bytes to 40 bytes.

6.3.273.0

9/27/2017

  • Added additional options for time synchronization:
    • Only allow time synchronization when the difference between device and system time exceeds a certain threshold.
    • Perform a time synchronization on an EFM poll.

6.1.601.0

4/4/2017

  • Disabled time synchronization when data collection is disabled.

6.0.2107.0

11/15/2016

  • Meters are now represented in the Project Tree View to improve visibility and editing.
  • Fixed an issue where EFM data for avg_c8, avg_c9, and avg_c10 was not exported to CSV.
  • Corrected column mapping of EFM data for n-Pentane and neo-Pentane.

5.20.396.0

5/3/2016

  • Resolved a Time Sync issue where, if no reads are active; only the first four (4) devices successfully synchronize.
  • Enhanced the driver to allow UDP tags to use the correct data type set (not default). This allows the data type of these tags to be manually modified.
  • Fixed an issue where “Bad” quality was reported for historical data when new records were not available.

5.19.467.0

10/20/2015

  • Added support for Advanced Statistics Tags, including _CommFailures, _ErrorResponses, and more.
  • The driver now includes the #n syntax when auto-generating tags for similarly named point types in point type tables to avoid duplicate tag names. This may change the default name for some auto-generated tags from previous versions.
  • Changed the alarm state from OFF to On for string events.
  • Resolved an issue where attempting to read a tag from a non-responsive device could falsely cause a timeout when reading the next tag on a different device.
  • Resolved an issue where reading multiple tags in the same point type logical could result in two separate read requests rather than one.

5.18.662.0

6/23/2015

  • The driver no longer performs a time synchronization operation on startup when the Time Sync Method is Absolute.
  • Added support for reading and writing to user tables using Opcodes 10 and 11.
  • Added the ability to ignore extra bytes received on the wire that are not part of the ROC communications. These bytes are sometimes added by radio modems and other networked equipment.
  • Enhanced the drivers to support Opcode 180. Enabled per device, this allows the driver to read multiple TLP and UDPs per read request.

5.17.495.0

2/24/2015

  • Spaces are no longer allowed in liquid and gas meter names.

5.15.588.0

9/23/2014

  • Removed the potential for a hang when a client accesses tags containing UDP point types.

5.15.585.0

7/22/2014

  • Enhanced the driver to cache the pointer file to disk so that it will not re-poll for data already collected on start-up.
  • Added support for Point Type 98.

5.14.491.0

2/18/2014

  • Fixed an issue where Default data type was always returned for UDP tags, even if the UDP data type was known by the server. This could cause writes that occurred before an initial read of the UDP tag to fail.

5.13.191.0

10/15/2013

  • Enhanced the Fisher ROC Serial Driver to support User-Defined Points. This includes support for Dynamic Tag Creation as well as Online and Offline Automatic Tag Generation.
  • Resolved an issue where, depending on the size and number of parameters in a block, the driver could request more parameters than will fit into a ROC serial response frame. An example of this is reading parameters 53 through 75 of point type 80 on a FloBoss Model 107 device, which would result in framing errors and bad quality for the entire block of parameters.
  • Increased the maximum number of supported channels to 1024.
  • Added support for FloBoss Model 107 specific parameters in point type 14. This support resolves an issue where adding or enabling parameter 37 of point type 14 would cause the entire set of point type 14 tags to go bad.
  • Added support for FloBoss Model 107 specific parameters in point type 57. This support resolves an issue where adding or enabling parameter 5 of point type 57 would cause the entire set of point type 57 tags to go bad.

5.11.250.0

3/5/2013

  • Improved the driver's EFM data collection performance and efficiency when intermittent communication errors are seen with the connection to the EFM data source. The optimizations are handled in the driver automatically and no project configuration changes are required in the driver UI.
  • Fixed an issue where the driver could incorrectly interpret the meter type returned by the device, potentially leading to missing EFM attribute data in the final EFM export.

5.10.205

11/13/2012

  • Added Electronic Flow Measurement (EFM) Support
  • Updated the driver with the new Connection Sharing feature.
  • Added a device setting to enable/disable sending a device login password.
  • When transactions fail due to an Operator ID failure, a single custom error message will now be posted per device.
  • Enhanced the driver to consume the extra bytes that may be received following a valid frame. This allows communication with ROC 300 devices, which may append an extra byte to every frame they transmit.

5.9.170

6/26/2012

Added support for the use of legacy tag names as part of Automatic Tag Generation. This enhancement was made to resolve a change introduced in the 5.8 release where tag formats created via Automatic Tag Generation were different than previous versions. This tag format issue only affects users who upgraded to version 5.8 and triggered tag regeneration.

For new installations of Fisher ROC Serial driver (server version V5.9 and up), the default setting for this checkbox is 'checked' so legacy tag names are used.

5.8.109.0

2/21/2012

Added support for Channel Serialization, Inter-Device Delay, and RTS Line Control. Updated the Operator Identification tab in Device Properties to be more consistent with ROCLINK configuration software. Consolidated Tag Import Settings under a single tab in Device Properties.

5.7.84.0

10/24/2011

  • Increased the channel limit to 256.
  • Fixed an issue caused when a controller responded with a data length greater than the data length supported by the protocol. This would cause a buffer overflow which could cause the driver to stop working. Added verification of data length returned by controller.

5.6.122.0

7/25/2011

  • Fixed an issue where the driver was sending the incorrect date (last two digits of year) when Time Synchronization is enabled for a device.
  • Increased the maximum devices per channel from 32 to 255.

Features when part of the EFM Suite

  • Support for gas Electronic Flow Measurement (EFM)
  • EFM Configuration and Mapping
    • History, including Gas Chromatograph data
      • Hourly
      • Daily
    • Alarms
    • Events

What Is a Driver?

KEPServerEX is more than an OPC server—it's a connectivity platform for industrial automation and IoT. Simply download KEPServerEX, and then select from Kepware's library of more than 150 device drivers, client drivers, and advanced plug-ins to fit the communication requirements unique to your industrial control system.

A driver is a software component that enables KEPServerEX to meet the connectivity requirements of a specific device, system, or other data source. The driver handles all proprietary communications to the data source for KEPServerEX; the client interfaces handle all supported OPC, proprietary, and open standards connectivity to applications that monitor or control the devices.

Drivers may be licensed individually or in suites. Additional drivers can be licensed on demand as connectivity needs evolve.

Purchasing Information

Fisher ROC Serial

This product is available for purchase through the following suites: