...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
| Expand | ||||
|---|---|---|---|---|
| ||||
|
...
Publisher object.
From the Publisher object, create the History output type object
...
| Info |
|---|
See the General Object Configuration |
...
Options Tab
See the Device Object General Options page.
Details Tab
See the Device Object General Details page.
Logging Tab
See the Device Object General Logging page.
Connection Tab
...
guide for assistance configuring the General, Options, Details, and Logging tabs. See the Device Object General Connection/Schedule page for assistance with the Connection tab. |
Device Tab
...
ROC Series
Select from REGFLO, Flowboss FloBoss™ 100 series & FBx, ROC300 ROCPAC (Default), ROC300 FLASHPAC, ROC407, Flowboss FloBoss™ 503, Flowboss FloBoss™ 504, and ROC 800 Series
Industry Canada ROC
...
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
...
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 FloBoss™ 503 models configured for AGA7 with old firmware (not typically the role of a Floboss 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 100FloBoss™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. 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.
...
Time Synchronization Configuration
Connection Object assigned to this device. Click 
to select or create one. See the Time Synchronization section for more details.
Time Synchronization Interval
Select the desired Time Synchronization Interval relating to the Schedule object assigned on the Connection tab. Time Synchronization checks occur on the frequency of this interval.
Time Synchronization Priority
Low. Queues up with other Low priority items.
Medium (Default). Interrupts Low priority items, and queues up with other Medium priority items.
High. Interrupts Medium and Low priority items, and queues up with other High priority items.
Timezone
Default = UTC-06:00 Central Time (US & Canada).
Archive Collection Tab
...
Collection Priority
Low (Default).Queues up with other Low priority items.
Medium. Interrupts Low priority items, and queues up with other Medium priority items.
High. Interrupts Medium and Low priority items, and queues up with other High priority items.
Collect Archive
Default = Not selected. Select to collect.
For more information on Haul, Gas Lift, and Cycle Transaction Log collection, see Transaction Logs.
Collection Interval
Select the desired Interval relating to the Schedule object assigned on the Connection tab.
| Info |
|---|
NoteIf multiple schedule objects are selected for this device (Primary, Secondary, or Alternate) ensure that each schedule has the same interval numbers configured. |
Archive Limits
Click to select or create an Archive Limits for each archive type. See the Archive Limits section for more details.
Archive Mapping (Optional)
...
Meter Runs Tab
...
Meter 1-18/Station Meter
Click to select or create the Meter Object assigned. See the Meter section for more details.
| Info |
|---|
Meter OrderingMeter run assignments in ACM are determined by meter type and position in the run listing above. Orifice meters are to be assigned before any Turbine/Linear meters (ROCPlus 800L). Example: The ROC device has 2 Orifice Meters and 1 Turbine Meter. The resulting assignments would be: Meter 01 = Orifice Meter Meter 02 = Orifice Meter Meter 03 = Turbine Meter If an additional Orifice Meter is configured in the ROC device, the ACM assignments above would be changed to the following: Meter 01 = Orifice Meter Meter 02 = Orifice Meter Meter 03 = New Orifice Meter Meter 04 = Turbine Meter |
...
The AUTOSOL ROC driver will examine each of the V-Cone points looking for an associated Orifice Run. If it finds an associated orifice run, the logical that it finds in the TLP is the index of the meter associated with the V-Cone point. In the example configuration in the figure below, the first orifice meter is associated with the first V-Cone point. As a result, when this meter is published, flow coefficient will be read from this point (61.2:0 in this example), in the published output the meter type will be set to V-Cone and the Calculation Method will be set to V-Cone.
...
History Segments Tab
...
Select the History Segments (or RAM Modules) should be included in the archive collection. All are selected by default.
...