Contents
Cirrus Link Resources
Cirrus Link Website
Contact Us (Sales/Support)
Forum
Cirrus Link Modules Docs for Ignition 7.9.x
Inductive Resources
Ignition User Manual
Knowledge Base Articles
Inductive University
Forum
Page History
...
The control and information tags created in the tag folder are:
| Name | Type | Description |
|---|---|---|
| Last Published File | String | Name of last published file |
| Last Published Sequence Number | Integer | Sequence number of last published file since last reset of metrics |
| Percent Completed | Byte | Publish completion percent for file being published |
| Publish File | Boolean | Manual trigger to publish file |
| Publish File Count | Long | Number of files published since last reset of metrics |
| Publish File in Transit | String | Name of current file being published |
| Publish File Path | String | Full path to the target file to publish over MQTT. Created if 'Enabled Auto-Publish' is disabled |
| Publish Files Folder | String | Full path to the target file folder to publish over MQTT. Created if 'Enabled Auto-Publish' is enabled |
| Publish Operation Status | String | Status description of current publish operation |
| Publish Operation Status Code | Integer | Status code for current publish operation |
| Remaining Retries | Integer | Number of remaining retries for current publish operation |
| Reset | Boolean | Trigger to reset publish metrics |
Anchor FilesFileSettings FilesFileSettings
Files - File Settings
| FilesFileSettings | |
| FilesFileSettings |
...
- Name
- The name of the History Store.
- Enabled
- Checkbox to enable/disable the History Store. Not selected by default.
- Type
- The type of History Store.
- Data stored in an In_Memory History Store will not be persisted across a module disable/enable, module restart or power loss.
- Data stored in a Disk-Backed History Store will persist across a module disable/enable, module restart or power loss.
- Edge Node Tag Capacity
- Maximum number of Edge Node level tag change events to store per Edge Node before dropping oldest historical Edge Node tag change events. This value is independent of the 'Device Tag Capacity' and only applies to how many 'Edge Node level' tag change events are stored per Edge Node.
- A tag change event is triggered by either a change in value or quality and results in the tag's Qualified Value (which has three attributes of value, quality and timestamp) being stored.
- Device Tag Capacity
- Maximum number of Device tag change events to store per Device before dropping oldest historical Device tag change events. This value is independent of the 'Edge Node Tag Capacity' and only applies to how many 'Device level' tag change events are stored per Device.
- A tag change event is triggered by either a change in value or quality and results in the tag's Qualified Value (which has three attributes of value, quality and timestamp) being stored.
- Flush Quantity
- The maximum number of tags to publish in a single message upon reestablishing communication.
- Flush Period
- The period to wait in milliseconds between publishes when flushing messages upon reestablishing communication
...
Overview
Content Tools