Property template on persistent TCP data point
I am trying to determine the necessity for a property template on a Mango Persistent TCP data point. I noticed that when I export the json for a persistent point, there is no element for the template id. Other point types will at least have this element set to an empty string if not defined.
The lack of the template id element would lead me to believe that the property template is not required. The data history will be the same as the point to which it is linked; the logging type of "All Data" will ensure this.
Is this correct?
phildunlap last edited by
The lack of the template id element would lead me to believe that the property template is not required.
The data history will be the same as the point to which it is linked; the logging type of "All Data" will ensure this.
It's not that simple. If the publisher is sending realtime values with update / change as its update event, the data source is saving real time values, but the point on the publisher is logging on an interval then the updates within an interval would have been published and saved, while on the publisher side only the interval logging would be recorded longer term.
So the settings that go into it are:
- Publisher update event. All publishers have this setting, and it determines when you send a value from a point (or update the publishers' data image in the case of the Modbus or BACnet publisher).
- The logging type of the data point being sent. For a data point logging all data, for instance, the 'update' and 'logged' events are synonymous.
- If the publisher transmits real time data. If not, then only historical syncs will bring about data on the receiver.
- If the data source saves real time data. If not, then the points will appear to update in time, but their histories will only be filled in once a history sync is run.