Fisher ROC Serial

Download Free Demo


Fisher ROC Serial 设备驱动与 KEPServerEX 结合使用,在 OPC/DDE 客户端与远程操作控制器 (ROC) 协议设备之间提供数据交换。 



  • 支持以太网封装
  • 支持直接从 RTU 或配置文件自动生成标签,以快速部署通信
  • 运算符识别
  • 针对 EFM 轮询、用户指定的间隔或时间的时间同步
  • 调制解调器支持
    • 自动拨号配置
    • 多电话号码管理
  • 用户程序数据(用户定义的点)的读写和自动标签生成
  • 支持 OpCode 10 和 11 以读写用户表
  • 支持 OpCode 167 以进行单点读取
  • 支持 OpCode 180 以便在单一请求中进行多点读取
  • 支持高级统计数据标签,包括 _CommFailures、_ErrorResponses 等
  • 支持 VCone 仪表类型和计算方法
  • 针对极端条件(嘈杂的通信通道和低带宽)优化


  • ROC


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


  • 英语


  • 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) Clients
  • SuiteLink and FastDDE for Wonderware




  • Added a pointer rollback to retrieve lost data from a device. If the device’s cache pointer is valid, rollback will be applied to cache pointer, otherwise the rollback will be applied to the current device pointer.



  • Resolved an issue where EFM uploads failed if more than 50 History Points existed in the device. 



  • 修复了以下问题:启动与设备通信后,立即出现通信失败。



  • 增加了对点类型 48 参数 35-38 的支持。
  • 增加了对 VCone 仪表类型和计算方法的支持。>



  • 修复了点类型 7 和点类型 10 的自动标签生成导致生成逻辑点 0 的标签的问题。
  • 添加了针对数据长度、起始日志指针和历史点编号的验证,以防重复处理重新发送的数据包。
  • 修复了“K 因子”值可能被导出为“截止”而不是“公称 K 因子”的问题。
  • 将点类型 177 的地址表中的参数 #0(设备标签)的参数大小从 10 字节更新为 40 字节。


  • 增加了更多有关时间同步的选项:
    • 仅在设备时间与系统时间之差超过某个阈值时才允许时间同步。
    • 对 EFM 轮询执行时间同步。



  • 为 PT 48 的地址解析器添加了参数 35-38。
  • 为 PointType 10 和 7 的所有逻辑单元增加了对自动标记生成的支持。



  • 为 CEFMEventSM::_HandleReadEventsResponse 和 CEFMEventSM::_HandleReadPointerResponse 添加了更多验证,以使响应与最近的请求正确匹配。
  • 为 CEFMHistorySM::_HandleReadHistoryResponse 添加了更多验证,以避免处理错误的数据包。
  • 引入了 CEFMConfigMappingEntry::SetAttributeMapping() 以基于仪表类型处理不同映射。



  • 当禁用数据收集时,禁止时间同步。



  • 为 CEFMHistorySM::_HandleReadHistoryResponse、CEFMEventSM::_HandleReadEventsResponse 和 CEFMEventSM::_HandleReadPointerResponse 添加了更多验证,以使响应与最近的请求正确匹配。
  • 将点类型 177 的 #0 参数的大小从 10 字节更改为 40 字节。
  • 如果设备被禁用,则不允许显示时间同步消息。



  • 现在,仪表呈现在项目树状视图中,以改进可见性和编辑能力。
  • 解决了以下问题:avg_c8、avg_c9 和 avg_c10 的 EFM 数据无法导出到 CSV。
  • 纠正了 n-Pentane 和 neo-Pentane 的 EFM 数据的列映射。


  • 为 Roc+ 的 H2、HE、CO 和 AR 添加了缺失的气体属性映射。
  • 增加了对 c8、c9 和 c10 属性的支持。
  • 修复了 nPentane 映射错误的问题。
  • 为点类型 141 增加了对属性 56-112 的支持。



  • 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.



  • 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.



  • 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.



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



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



  • 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.



  • 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.


  • 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.


  • 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.



  • 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.



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.


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.


  • 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.


  • 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.

功能(包含在 EFM Suite 中时)

  • 支持气体电子式流量测量 (EFM)
  • EFM 配置和映射
    • 历史记录,包括气相色谱仪数据
      • 每小时
      • 每天
    • 警报
    • 事件


KEPServerEX 不仅是 OPC 服务器,它还是一种用于工业自动化和 IoT 的连接平台。只需下载 KEPServerEX,然后从包含 150 多种设备驱动、客户端驱动和高级插件的 Kepware 库中选择,就能满足您的工业控制系统的独特通信要求。

驱动是一种软件组件,能够使 KEPServerEX 满足某个特定设备、系统或其他数据源的连接要求。驱动可处理 KEPServerEX 与数据源进行的所有专属通信;客户端接口处理通向监控或控制设备的应用程序的所有连接,包括支持的 OPC 连接、专属连接和开放式标准连接。