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
...
Tip |
---|
It can take MQTT Transmission 1.5 times the configured Server Keep Alive time to determined that there is a connection failure. The Rolling History Max Age should be at least 2x the Transmitter Server Keep Alive timeout to ensure that all tag change events are captured during this period. |
The ideal settings for your Rolling Buffer configuration will be dependent on the rate that your tags are changing. For example, consider these settings:
Rolling history max age - 60s (2x the 30s keep alive timeout)
Rolling history prune interval - 60s
Rolling history prune quantity - 10
The rolling history prune interval is how frequently it checks to see if there is any data that’s older than the max age (60s). If there is, in this example, the prune quantity (10 metrics) will be pruned from the buffer for every prune interval (60s). If there’s 100 metrics in the buffer that are older than 60s, after pruning once, only the oldest 10 will be dropped and there will still be 90 old metrics there.
On a reconnect, these older metrics will be published since they’re still in the buffer. Having a lot of old tags in the buffer will increase the number of duplicates that you get. Keeping a proper balance between the tag change rate and these settings can be important for minimizing duplicates.
...
Note |
---|
Using this feature may result in duplicate tag change event data being reported to Ignition as there is the potential for the publish of historical data that was previously successfully received. This will generate errors reported by the StoreAndForward.Sink.HsqlDataStore.DatasourceForwardTransaction logger when inserting the data into a database. These are benign errors and will not result in data loss. |
...