If the payload feeding an IoT Live node does not contain a key that matches the IoT Server Key exactly for a dial, that dial will show up with specification limits but without a needle. Follow these steps to help ensure that all dials have values:
- For data sources connected directly on IoT, if there's a payload key that matches a Braincube Digital Twin platform dial's IoT Server Key, the IoT Live dial will be populated by that data source. This will typically provide for the fastest update to dials.
- If you have variables Calculated in Braincube Digital Twin platform, in many cases the braindata-compute node can be used. The braindata-compute node uses the Braincube API to pull formula logic from the Digital Twin platform which is then applied to edge data with tag names that match the referenced IoT Server Keys. This may not work for all calculations particularly those with many layers of nesting or moving functions. This will also typically provide for the fastest update to dials.
- If you have other variables in Live that were created in MX (the Braincube Digital Twin backend), the Live API can pull values for those dials. Dial updates will be only as quickly as they are on the Digital Twin Live for these tags.
Any other data gaps whether from tags missing in the directly connected data source, IoT keys with errors in linking, complex calculated formulas etc, will also be filled in using the Live API flow.
From the IoT Live display it will not be possible to tell the source of the data on each dial. We suggest using the Stale Threshold to ensure update times as desired.