As needed, from the Software Manager you can take actions on modules, such as install, uninstall, upgrade, downgrade, and re-install. You flag intended actions on software items using action buttons near the bottom of the manager’s view pane, as shown in Figure 74. Action buttons become enabled when you have one or more items selected.
Included in action buttons are and . When you reset, all flagged module changes (since the last commit) are cleared. Commit is how you actually launch the flagged changes.
When you , one of these two things happens:
-
If upgrading (or downgrading) modules, a confirmation popup dialog appears, telling you the host must be rebooted and/or station stopped. Then, after the software operation completes, the host is rebooted (if a QNX-based JACE), or if a Windows-based JACE, its station is restarted.
Before committing, make sure that controlled equipment that might be adversely affected by the JACE’s station stopping and then
host rebooting (from software changes) is put in a manually controlled state.
-
In many cases, if only installing new module(s), meaning modules not previously installed, the station continues running on that platform. The software is immediately installed.
The following action buttons are explained in further detail:
Also see Right-click option to install earlier version.
Whenever one or more local modules are newer than in the opened JACE platform, the Software Manager enables an button. This allows you to flag all out-of-date modules to be upgraded. Unlike other action buttons, specific item(s) do not need selection first.
When you click it, the status of all out-of-date modules changes to “Upgrade to <version>,” and the button becomes unavailable. If needed, you can still make additional changes, such as choosing additional modules
to install.
This button is available in the Software Manager when you have one or more modules selected with a status of “Not Installed.” When you click it, the status of the selected
modules changes to “Install <version>,” and the button changes to .
If a selected module has dependencies on modules not already installed (or also flagged to install), a dialog appears explaining additional software is needed,
as shown in Figure 75. After you click from this dialog, the additional modules are flagged, the status of all affected modules changes to “Install <version>,” and
the button changes to .
This button is available in the Software Manager when you have one or more installed modules selected (status of either “Up to Date” or “Out of Date”). If the selected module(s) are not dependencies of other
installed modules, when you click Uninstall the module(s) status changes to “Uninstall <version>,” and the button changes to .
If other installed modules have dependencies on one or more modules you selected, a dialog appears explaining the uninstall cannot occur, as shown in Figure 76. You can then decide if you want to
reflag another uninstall, selecting also all modules that are dependent.
In the Software Manager, when you have one or more installed software items selected, the “install” button changes to show one of these options.
-
appears if the installed item is the same version as your locally available one.
-
appears if the installed item is an earlier version than your locally available one.
-
appears if the installed item is an newer version than your locally available one.
When you click this button, the software’s status correspondingly changes to either “Re-Install <version>”, “Upgrade <version>”, or “Downgrade <version>”, and the button changes to , for example: .
In the Software Manager, when you have one or more pending actions in place on software items, the button is available. This is how you initiate the software action.
At any time before you commit, you can also click the button. This removes all pending actions in place on software items, and makes the button unavailable again.