There are dedicated slots in the InfoSources' advanced configuration, which allow you to determine whether the sources should be propagated.
There is also a new component dedicated to the inter-station propagation, the SourceDeviceExt.
InfoSource Configuration
There are dedicated slots in the InfoSources' advanced configuration:
By default, the Inherit slot is set to true and the SyncUp and SyncDown slots are not displayed. To display them, Inherit must be set to false and you must refresh the page. If you set inherit to true and refresh the page, the SyncUp and SyncDown slots will be hidden again.
Depending on your InfoSource's configuration, your InfoSource will propagate to different stations
-
SyncUp will determine if the InfoSource will propagate to the stations with the Supervisor role.
-
SyncDown will determine if the InfoSource will propagate to the stations with the Subordinate role.
You can configure each of your InfoSource one by one using those two slots, but you can also use the Inherit slot. If it's enabled, the SyncUp and SyncDown slots are ignored and the configuration will be taken from the closest ascendant InfoSource with Inherit set to false.
Example:
Let's focus on the InfoSource inside the AAC20 EnumPoint
Its parent Device AHU 01 also has an InfoSource with the same AdvancedConfig.
And finally, the BacnetNetwork also has an InfoSource but with the Inherit property disabled
In this context, if you propagate the InfoSource in the AAC20 Enum Point or in the AHU01, it will get the configuration from the InfoSource in the BacnetNetwork.
In the Config, there is a Station InfoSource. In the Nav tree, it's the highest positioned InfoSource, so if there are no intermediate InfoSource to inherit the configuration from, the configuration will be taken from the Station InfoSource.
SourceDeviceExt Configuration
The SourceDeviceExt (absent by default) must be located in the target Niagara station in the NiagaraNetwork.
You can add it using the "InitializePropagation" Action in the "Propagation" Folder located in the BtibService.
You CANNOT propagate InfoSources between two Peer stations.
The configuration is pretty straightforward, a SourceDeviceExt can either be enabled or not, allowing you to totally stop propagations toward a specific station.
Next Step
Step 2 Launch a source propagation