Converting a controller

Perform the following procedure for each controller for which you have secured N4.0 license, and have successfully migrated its station database.

Prerequisites:

Workbench is open, you have used it to check the migrated station for this controller, and confirmed that the migration was successful.

Open a platform connection to the controller to be converted, and access the Distribution File Installer.
The list of distribution files opens.

NOTE: N4 may display the cleanDist or other files for other controllers, but you can select only the file that is appropriate for your controller. This file is only for a unit already converted to Niagara 4. If you do not see the appropriate *.dist file, verify that you are in the conversion folder. If necessary, use the buttons at the bottom of the view to navigate and browse for the file.

Point the installer to the !/sw/N4buildNumber folder, for example: !/conversion/4.0.15.619.

Only one of several listed should be selectable. This is an example of the file for converting a controller:

aAXtoN4-qnx-jace-npm6e-etfs2048.dist
Select the appropriate .dist file and click the Install button.

NOTE: Installation clears all data in the controller, including AX licenses and certificates, environment and properties files, SSL certificates and key files, along with all station data and NiagaraAX software. The controller’s IP configuration is retained. You must use the default platform credentials to regain access.
After this .dist file installs and the controller reboots, re-open a platform connection (port 3011) using the factory default credentials.
If you previously exported SSL certificate stores from this controller, access the platform Certificate Manager view, and do the following:
1. On the User Trust Store tab, click Import, and navigate to select the previously saved public key certificate (typically common among all platforms at the job).
2. On the User Key Store tab, click Import, and navigate to select the previously saved private key certificate unique to this platform.
3. Access the platform Platform Administration view, click the Change SSL Settings button, and select the new server certificate you just imported.
4. Run the platform Commissioning Wizard (right-click the Platform node, and select Commissioning Wizard).
In this initial commissioning of the controller, you typically use all default step selections. This includes most steps except Install lexicons (but if you use text-based lexicons, select this too).

In most cases you select to:
- Install the licenses from the licensing server (unless you already have these as files).
- Use runtime profiles RUNTIME and UX, or else RUNTIME, UX, and WB.
- Install the specific station that you migrated for this controller, choosing to:
  Copy files from selected directories.
  
  NOTE: You typically select all directories shown in the migrated station, including the alarm and history subfolder (to migrate prior alarms and histories). Apart from the migration, this is an unusual practice. If you are installing the same station in different/multiple platforms, be sure to deselect (clear) the alarm and history subfolders.
- Install all pre-selected software modules required for this station.
- Install all listed core software distribution files.
- Review, and if necessary change, the controller’s TCP/IP configuration.
- You must add at least one new platform admin user in the “Remove platform default user account” step (initial Platform Daemon Authentication dialog). This replaces the factory-default platform user. Note that in N4, platform credentials require a stronger password than in AX. The password must be at least 8 characters, with at least 1 digit (numeral). If the password does not meet this requirement, an error dialog prompts you to create a valid one.
  Make note of these platform credentials; you should use a login as such a platform user upon next access.
  
  NOTE: For this platform session, Workbench remembers the first platform admin user you created to replace the factory default platform user. This simplifies re-connection after the controller reboots.
For related details, see the JACE Niagara 4 Install and Startup Guide. Example screen captures of a few of these Commissioning Wizard steps are shown in the Controller conversion examples
Review and finish the commissioning wizard, to install all selected items and reboot the controller. After several minutes, the conversion completes, and platform access should be possible.

CAUTION: Do not remove power from the controller during this reboot, which may take up to 7 or more minutes to complete. Removing power could easily cause the unit to become unrecoverable. If desired (and convenient), you can use a serial shell connection to the controller to monitor progress as files are installed, the platform is rebooted, and the unit is prepared.
Re-open a platform connection to the converted controller, using a new platform account you entered in the wizard. Go to the Application Director and view the station standard output.

Again, there may be warnings and messages, but its station status should change to “running”.
In Workbench, open a station connection (Fox or Foxs) to the converted controller, typically using the admin (superuser) login. Verify the station opens.
For each remainin controller to be converted, repeat the above steps

When done with this, all converted controllers should be running stations as N4.0 platforms, as well as the Supervisor station.

Converting a controller

Related Links