Page History

The Google Cloud Injector module provides the ability to push Tag data to a Cloud IoT Core.  The settings configuration for this module are located under the Configure tab of the Ignition Gateway web UI.                                                                      

Image Removed

Once in the configuration section there are four tabs: General, Cloud IoT Core, Sets, and Tag Agents.  Each of these tabs is described in detail in the following sections.

...

The Sets tab contains a list of Google Cloud Sets.  Each set represents a grouping of Cloud IoT Core endpoints.  When a set is referenced by a Tag Agent the Agent will push Tag data to all Cloud IoT Core endpoints contained within that Set. The Sets are disjoint, meaning that a single Cloud IoT Core endpoint cannot be in more than one set.  Out of the box the Google Cloud Injector module will have one "Default" set defined.

Image RemovedImage Added

Additional Sets can be configured for situations where multiple Tag Agents will need to push to different Cloud IoT Core endpoints. The configuration options for Sets are listed below.

...

• Name
  • This is the friendly name of the set used to easily identify it.
• Description
  
  • This is a friendly description of the set.
• Push Policy
  • This defines which endpoints to push to. If PUSH_TO_ALL is selected, every endpoint that is part of this set will receive all messages. If PUSH_TO_ANY is selected, only one of the endpoints that is part of this set will receive any given message. PUSH_TO_ANY is useful when adding endpoint configurations to increase the throughput of the Injector.

Clicking on the 'Create new Google Cloud Set...' link will bring up the following form to add a new Set.

Image RemovedImage Added

Tag Agents

Tag Agents are the workers within Google Cloud Injector that monitor tag events, convert them to a JSON representation, and push them to one or more Cloud IoT Core endpoints. Out of the box the Google Cloud Injector module will have one "default" Tag Agent defined.

Image RemovedImage Added

Tag Agents are configured to point to a single folder.  All Tags within that folder will be monitored by the Tag Agent. 

...

• Tag Provider Name
  
  • The name of the Tag provider containing the tags.
• Tag Path
  • An optional folder path under the Tag provider where the root folder of the Tags can be found.
• Tag Pacing Period
  • The buffer period, in milliseconds, that Tag events will be aggregated into a single payload before pushing.
• Convert UDTs
  • Whether to convert UDT members to normal Tags before publishing.  If enabled the Tags representing the UDT member will retain their member path prefixed by the UDT Instance name.
  • Publish UDT Definitions
    • This can only be set if 'Convert UDTs' is false
    • Whether or not to publish UDT definitions in the NBIRTH messages
• Set
  • The Set of Cloud IoT Core endpoints that the Tag Agent will push to.
• Auto-discover Tags
  • Whether newly added tags should be dynamically scanned and their values pushed.  This field is disabled by default.  It should remain disabled while manually editing tags and/or their configurations. It should only typically be enabled in systems where tags are created in real time.

...

As you can see, the Sparkplug settings can be used to either hard-code defined by setting these IDs in this configuration page, or leave them blank so that the Agent will scan and discover them based on the tag tree layout. 

Clicking on the 'Create new Tag Agent Settings..' link will bring up the following form to add a new Tag Agent.

Image Modified