ROC
General
Property | Description |
|---|---|
Name | The name of this ROC Protocol object. The name is used as a ‘key’ to associate EFM data with this object. For the EFM Collection Service in ACM to publish eACM EFM records seen on the MQTT broker, ACM must have a placeholder ROC object with the same name configured. In addition, ACM is required to have a placeholder meter object for each meter run with the same name and the same meter run number assignment in both eACM and ACM. The ROC object does not need to be enabled in ACM for publishing from the EFM Collection Service to work. |
Enabled | If checked, Edge ACM will poll this device when running |
ROC Series | The type of ROC you wish to poll:
|
Industry Canada ROC | Indicates that the device has been configured to Industry Canada standards |
ROC Unit | Sets the ROC Unit Address, valid values 0-255 |
ROC Group | Sets the ROC Group Address, valid values 0-255 |
Host Unit | Sets the Host Unit Address, valid values 0-255 |
Host Group | Sets the Host Group Address, valid values 0-255 |
Max Message Length | Sets a limit on the maximum number of bytes to send in a single message to the End Device, valid values 8-240 |
Tag Groups | The Tag Groups that are associated with this device. Edge ACM will only poll this device for the tags in the groups selected here |
Connection Settings | The object that contains the connection settings Edge ACM will use to connect to the End Device |
Folder | The parent folder for this item |
TLP Format |
|
PGAS Output Options |
|
Protocol Options |
|
Details
Property | Description |
|---|---|
User01 | Optional user supplied meta data string. Included with EFM record if supplied. |
User02 | Optional user supplied meta data string. Included with EFM record if supplied. |
User03 | Optional user supplied meta data string. Included with EFM record if supplied. |
Logging
Property | Description |
|---|---|
Logging | Logging from the perspective of this device object.
|
Footprint Level |
|
Security
If security is required in the ROC device then security needs to be enabled in eACM.
To determine if security is enabled look in the ROCLINK 800 Client, select the “ROC” menu option and then select “Security”.
Example screen shot of ROCLINK Device Security page:
eACM supports the enhanced security feature in the newer firmware.
Property | Description |
|---|---|
Enable Roc Login | Enable security login for this ROC device. |
Operator Id | Refer to ROCLINK device security page for appropriate value. |
Send Password | Send password with ROC login message. |
Password | Refer to ROCLINK device security page for appropriate value. |
Send Access Level | Send requested access level with ROC login message. |
Access Level | Refer to ROCLINK device security page for appropriate value. |
Inactivity Timeout (ROC800 Only) | The frequency with which eACM will log back into the ROC device. In ROC 800 series devices this value is configurable in ROCLINK. It should match eACM. This is the not the same value as the Timeout column on the ROCLINK Device Security page. |
Comm Stats
See the Comm Stats entry on the Common Tabs page: Common Tabs | Comm Stats
Time Sync
Property | Description |
|---|---|
Enable Time Sync | Check box to enable time synchronization. |
Time Synchronization Configuration | Reference to TimeSync object configuration. |
Time Sync Interval | Interval to check if time synchronization is required. |
Time Sync Priority | Priority of time synchronization poll task. |
Time Zone | Time zone to consider during time synchronization. |
Archive Collection
Where the supported archive types are:
Alarm
Daily
Event
Extended
Hourly
Minute
Batch
Meter Configuration
Property | Description |
|---|---|
Collection Priority | Queues up history collection by priority as related to other tasks.
|
Collect (Archive Type) Archive | Check box to collect this type of archive. |
(Archive Type) Interval | Reference an interval object to declare how often the archive will be polled to see if there are new records to collect. |
(Archive Type) Archive Limits | Reference an archive limits object to (optionally) assign the limit for the first collection. |
(Archive Type) Map Rule |
The AUTOSOL ROC protocol driver has an internal archive map for each type of ROC device it supports. The internal archive maps are based on information obtained from Emerson’s documentation on EFM and AGA Reporting. They contain the details of each point that is expected to be defined in the ROC history configuration and cover the majority of gas and liquid measurement applications. The default setting (Internal Map) will work for most scenarios. |
External (Archive Type) Map | Reference to a History Map object is required if (Archive Type) Map Rule is not assigned to Internal Map. |
Meter Runs
Click the + icon to add the desired number of meter runs. Assign a reference to a meter for that meter run.
For EFM, at least 1 assigned meter run is required.
Do not share meter objects between meter runs.
For the EFM Collection Service in ACM to publish eACM EFM records seen on the MQTT broker, ACM must have a placeholder ROC object with the same name configured.
In addition, ACM is required to have a placeholder meter object for each meter run with the same name and the same meter run number assignment in both eACM and ACM.
The ROC object does not need to be enabled in ACM for publishing from the EFM Collection Service to work.
History Segments
Select the History Segments (or RAM Modules) should be included in the archive collection. All are selected by default.
Store and Forward
Select to enable ROC Store and Forward Protocol which is used to communicate with a given ROC through intermediaries. Select to configure the address and group fields.
For assistance, please submit a ticket via our Support Portal, email autosol.support@autosoln.com or call 281.286.6017 to speak to a support team member.