Getting your station ready for propagation can get confusing, there are many steps to follow and many properties to handle. Getting an unexpected result after all this work can be frustrating.


That's why the BtibService now comes with a Propagation Diagnostic component.


This component will provide you with a complete diagnostic over your station and will detect any anomaly. Simply trigger the "Execute" action and wait for the "Info" slot to update.


Let's see the content of the "Info" slot.

Before moving to the Stations Test or the SyncTasks Test, always check that the previous tests are succesful.

Model Test


The Model Test will check the configuration of your whole model:

  • Are there some Aspects with SyncEnabled set to true?
  • Are there some Node Definitions with SyncUp set to true?
  • Are there some Node Definitions with SyncDown set to true?

Example

  • Successful Test:

Here we know that some Aspects have syncEnabled set to true, and in those Aspects, there are some Node Defintions configured to propagate toward a SUPERVISOR station but not toward a SUBORDINATE station.


  • Failed Test:

In this station, no propagation is possible.

Niagara stations



The Stations Test will check the configuration of the stations in the NiagaraNetwork:

  • Are there some Stations with a SUBORDINATE OR SUPERVISOR role?
  • Can we successfully ping those stations?
  • Are there some elements to propagate for a station with a given type?

Example

  • Successful Test:


Everything went fine, we can ping the station and there are Nodes and InfoSources ready for propagation.


  • Failed Connection:


We cannot connect to the second station: it has no address.


  • Missing elements to propagate:

There are no Sources nor InfoSources to propagate.


  • Failed Test:


There are only Peer stations in the NiagaraNetwork.


SyncTasks Test


The SyncTasks Test will check the configuration of the SyncTasks in the stations in the NiagaraNetwork:

  • Do the stations have a ModelDevicExt and a SourceDeviceExt?
  • Are they enabled, disabled or missing?

Example

  • Successful message:

The Niagara station has an enabled ModelDeviceExt and an enabled SourceDeviceExt.


  • Missing or disabled DeviceExts:

If the whole network has no DeviceExts (SourceDeviceExt or ModelDeviceExt) or if none of them are enabled, warning messages will be displayed.

Model Summary


The Model Summary won't perform any tests, it will simply display the configuration of the whole model

Example


InfoSource Summary


The InfoSource Summary won't perform any tests, it will simply display a summary of InfoSources' configurations

Example