Converting from a BACnet Supervisor (BacnetWsNetwork)

Remember that different host licensing is required. See AWS and OWS Supervisor module and license requirements.

Running the station BOG file offline converter

Using Workbench, save the existing BACnet Supervisor station, such that its config.bog file is up-to-date.
Using a Workbench platform connection to the Supervisor, stop the station.
Copy its entire station folder to the AX-3.6 or later Workbench stations directory.
In AX-3.6 or later Workbench, open a console window. You can use the Workbench menubar option Window->Console (shortcut F3) to open a console area at the bottom of the Workbench view.

The command prompt shows the current working directory, e.g. d:\niagara\niagara-3.6.36>
Change directory (cd) to the station folder under the stations subdirectory, for example:

d:\niagara\niagara-3.6.36> cd stations\MyBacSupvsr

d:\niagara\niagara-3.6.36\stations\MyBacSupvsr
You can skip the step above, but it makes it easier to issue the command. Otherwise, you must include the relative path for the target config.bog file in the utility command.
From the stations folder for the BACnet Supervisor, enter one of the following commands:
- For a BACnet AWS Supervisor conversion, enter:
```
nre bacnetAws:com.tridium.bacnetAws.migrate.MigrateWsToAws
config.bog
```
- Or, for a BACnet OWS Supervisor conversion, enter:
```
nre bacnetOws:com.tridium.bacnetOws.migrate.MigrateWsToOws
config.bog
```
This utility starts running, and after several seconds should complete with console results similar to those shown in Figure A.26 below.

Figure A.26. Example converting BOG file for station BnetWsSup34 to one compatible as AWS Supervisor

Results with “Success” mean you can start and run the converted Bacnet Supervisor station as either a BACnet AWS Supervisor or BACnet OWS Supervisor, as appropriate.
A few warnings may occur in the conversion, as shown in Figure A.26 above. In this case, this occurred because the source BACnet Supervisor station database was from a host running AX-3.4—and it had uploaded BACnet properties that were “unknown” to that Bacnet driver version, but known in AX-3.6.

Notes on a converted BACnet Supervisor station

The following notes apply to a BACnet Supervisor station that has been converted to a BACnet AWS Supervisor or BACnet OWS Supervisor station:

Following the conversion, components like the BacnetWsNetwork and BacnetWsDevice (from the bacnetws module) are changed to the BacnetAwsNetwork or BacnetAwsDevice, and so on.

However, names of all components remain unchanged. This means if you used default names, like “BacnetWsNetwork” for the top network component, it remains that way. See Figure A.27.

Figure A.27. Converted AWS Supervisor with BacnetAwsNetwork named “BacnetWsNetwork”

To reduce confusion, you should rename such components as appropriate. Note that the default views for such changed components will automatically be the correct ones—for example, the Bacnet Aws Device Manager, the Bacnet Aws Config Manager, and so forth.