By default, the Software Manager lists all the JACE’s out-of-date modules at the top of the table, then uninstalled modules, and lastly up-to-date modules (sorted alphabetically); see Figure 70.
-
Out of Date modules are older than what you have in your PC software database.
-
Not Installed modules do not exist on the platform, but are in your PC software database.
-
Up to Date modules are the same (or possibly newer) than that in your PC software database.
Both “out of date” and “not installed” modules may also show a “Requires Commissioning” status. This indicates you must upgrade
the JACE first, before installing that module version. For more details, see status descriptions for Software Manager table columns below.
As needed, you can scroll down the table or click on headers of table columns to resort alphabetically.
The Software Manager lists modules using four columns, from left-to-right labeled as follows:
-
File — File name of locally available module file, or blank if the module is on the remote host only.
-
Installed Version — Version of the module installed in the remote host, or blank if not installed.
For related details, see “About module versions” in the User Guide.
-
Avail. Version — Latest version of locally available module, or blank if the software is on the remote host only.
-
<unlabeled> — Status of the module in the remote JACE platform. For each module, status is one of the following:
-
Not Installed — Module is not in remote platform, but is available locally.
Blue text is used for this status.
-
Not Installed (Requires Commissioning)— Module is not in remote platform, but is available locally. Blue text is also used for this status.
Dependencies prevent you from installing it, unless you first upgrade the JACE, using the Commissioning Wizard. See Upgrading a JACE.
-
Up to Date — Module is installed in the remote platform, and is equal to (or higher) than locally available module version.
-
Out of Date — Module is installed in remote platform, and is older than your local version.
Red text is used for this status.
-
Out of Date (Requires Commissioning)— Module is installed in remote platform, and is older than your local version shown. Red text is also used for this status.
Dependencies prevent you from installing it, unless you first upgrade the JACE, using the Commissioning Wizard. See Upgrading a JACE.
-
Not Available Locally — Module installed in remote platform is not in your software database.
-
Cannot Install — Local module is unreadable or has a bad manifest; you cannot install it.
-
Bad Target — Remotely installed module is unreadable or has a bad manifest, and is therefore unusable by a station. Software in this state should probably be fixed, since it could cause the station to not work correctly.
-
Downgrade to
<version>— Remotely installed software is intended to be replaced with a module having a lower version. -
Install
<version>— Module is intended to be installed; it does not currently exist on the remote platform. -
Re-Install
<version>— Remotely installed module is intended to be replaced with a module having a the same version. -
Uninstall
<version>— Remotely installed module is intended to be uninstalled. -
Upgrade to
<version>— Remotely installed module is intended to be replaced with a module having a higher version.
“Intended” status values like “Install <version>” reflect un-committed actions made during your Software Manager session. Blue text is used to list these statuses. -
You can also view software details about any item in the table. In addition, you can filter (reduce) the number of software items listed, based on text included in file name or the softwares’ status values. See Filtering displayed software for more details.
From the Software Manager, double-click any module to see a popup dialog with details (Figure 71).
Details include a brief module description, comparisons between installed and available module, module file and size, and whatever module dependencies exist, by part names. Dependencies are listed for both cases: what software is required by this module, plus software dependent on this module.
Essentially, dependency details are for information only. When installing modules from the Software Manager, all dependent
modules are automatically included when you select a module to install.