About Platform Services

Under its Services container, every NiagaraAX station has a PlatformServices container (Figure 23).

Figure 23. JACE station’s PlatformServices

PlatformServices is different from all other components in a station in the following ways:

It acts as the station interface to specifics about the host platform (whether JACE or a PC).
It is built dynamically at station runtime—you do not see PlatformServices in an offline station.
Any changes you make to PlatformServices or its child services are not stored in the station database.

Instead, changes are stored in other files on the host platform, such as its platform.bog file.
With one exception, do not attempt to edit platform.bog directly; always use PlatformServices’ views! At the time of this document, the single exception is to enable station monitoring of an external sealed lead-acid battery connected to a JACE-x02 Express platform (aka “M2M JACE”). For details, see Configure JACE-x02 Express (M2M JACE) for dual battery monitoring.

Included under PlatformServices are a TcpIpService and LicenseService, providing station (Fox) access to dialogs used in platform views, for instance the TCP/IP Configuration dialog as shown in Figure 18. These services support installations where all configuration must be possible using only a browser connection (and not Workbench connected to the JACE’s platform daemon).

PlatformServices items of interest for JACE commissioning

For any QNX-based JACE, the following child platform services in the station’s PlatformServices are of chief importance when commissioning a new controller.

PowerMonitoringService — Holds properties for configuration and status of the JACE’s battery monitoring and primary power monitoring, and power-fail shutdown. For details, see JACE power monitoring configuration.

(In the special case of a JACE with an SRAM option card, running an early AX-3.6 build (prior to 3.6.44), this service is automatically removed. This controller is always assumed to be “battery-less”. However, an SRAM-equipped controller running build 3.6.44 or later is configurable for simultaneous support of a backup battery (if installed) and SRAM. Or, the JACE may be re-configured to support only one or the other.)
DataRecoveryService — For operation/monitoring of the ongoing SRAM backups for an SRAM-equipped JACE. Starting in build 3.6.44, it includes a “Service Enabled” configuration property, such that you can disable it (viable only if the controller has a backup battery installed). For details, see JACE SRAM support enabling/disabling.
SerialPortService — Holds properties for the status of serial ports. Typically, this platform service is important only if an older (JACE-403 or JACE-545) series platform, to access “Port Config” properties. In this case configuration may be needed because one or more ports may be “dual-duty”, that is either RS-232 or RS-485.

Also, you may wish to review the parent container’s PlatformServices properties and adjust, if needed.

For any SRAM-equipped JACE running build 3.6.44 or later that is installed “battery-less” (without any backup battery), you must adjust its “Battery Present” property from (the default) true to false. See To review/adjust PlatformServices properties for the JACE.
PlatformServices in a JACE-700 (JACE-7 series) station include properties for an onboard “tamper switch” CI. See Controller-specific PlatformServices properties.