ROC Device Tab Configuration

ROC Series

Select from REGFLO, FloBoss™ 100 series & FBx, ROC300 ROCPAC (Default), ROC300 FLASHPAC, ROC407, FloBoss™ 503, FloBoss™ 504, and ROC 800 Series

Industry Canada ROC

Default = Not selected. Select to enable Industry Canada Support.

ROC Unit Address

Default = 1.

Host Unit Address

Default = 1.

ROC Group Address

Default = 2.

Host Group Address

Default = 0.

TLP Format

• Use TLP Format (Default). When outputting data and item names are used, the item name will be written in TLP format. 

• Use String Format. When outputting data and item names are used, the item name will be written in String format.

Max Message Length

Default = 240. 

PGAS Output Options

Default: No special mapping for PGAS output. Option1: Map Volume to Index Off and '0' to Index On.

Schedule Reinitialization

Default: Off. Allows you to configure the device to execute the command “Reinitialize” on a scheduled interval. Reinitializing resets items, rebuilds poll messages, and rereads the field device configuration.

Protocol Options

• Do not retrieve config after comm fail. For communication efficiency, Meter Configuration data is only collected during specific history collections times. One of those times is the next history collection after a communication outage.  This option prevents ACM from re-reading meter characteristics after a communication outage.

• Read user opcode data via opcode 10. This option causes ACM to read user opcode points using ROC protocol opcode 10 instead of opcode 180.  This can be a more efficient way to read user opcode points, as long most of the requested points are continuous.  If there are many gaps between requested user opcode points, then this option may not be desirable, as gaps will cause items to be polled in separate reads.  This option is sometimes required to read user opcode data sourced from a user program running the ROC device that cannot be read with opcode 180.

• Log EFM Upload Progress. This option turns on detailed logging for history collection. 

• Do not switch ROC series automatically. ACM will internally change the configured ROC type, to the ROC series returned in the opcode 6 read that is performed the first time ACM communicates with a ROC device.  This automatic switch overrides the user selected device type and is intended to give ACM a better chance of accurately collecting and processing EFM data and dealing with the variances between ROC models. This automatic switch has caused issues for AUTOSOL users with FloBoss™ 503 models configured for AGA7 with old firmware (not typically the role of a FloBoss™ 503). This option was added to allow those users to disable the automatic switching behavior.

• Upload Alarms on Report-by-Exception. This option causes ACM to upload new alarm records from the device during RBX processing.

• Allow mapping of points to run from non-associated segments (ROC Plus). To be supplied.

• Disable writes (ROC Opcode 11 & 181). This option forces read only behavior from ACM to the ROC. It prevents any writes including set point changes, configuration changes, etc. from being sent from ACM to the ROC device.

• Use Mark West Liquid Setup. 

• Read K Factor from Point Type 7 Param 21 for FloBoss™100/500 series. 

• Store unmapped history points with Station Meter. 

• Store events only with associated meters. This option will take certain ROC configuration events and publish them only to meters associated with the specific run. If there is no specific run in the event, it will continue to be published to all meters. 

• Exclude NSV and S&W Fields Transaction/Batch Records. 

• Do not write to E2PROM at the end of GC Write. 

• Combine data from all segments into the same archive record (ROC Plus). This option should be used if advanced mapping is being used and history points from different segments are configured to go to the same meter.

• Use indicated volume for mass in liquid mass meters. This option should be used if the user needs indicated volume to be published to mass instead of indicated volume.

• Collect history on a ROC with no configured meters (non-RocPlus). This option should be used when the ROC device is running without meters in its configuration. An external map for the historical collection may be required. Not intended for use with ROC800 series.

• Device is an FB107 with firmware version 2.0 or higher. This option should be used if collecting history from an FB107 device that has had its firmware updated to version 2.0 or later. The new firmware removed Point Types that are used for meter configuration polling and this option will modify the read requests to use the updated Point Types.