Under its Services container, every NiagaraAX station has a PlatformServices container (Figure 29).
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.bogfile.
Do not attempt to edit platform.bogdirectly; always use PlatformServices’ views!
For any JACE-NXS, the platform service items of interest during commissioning are as follows:
-
HardwareMonitorService — Holds two internal JACE-NXS environmental values: CPU temperature and board temperature. Included for each is an adjustable alarm limit, with a “default” value. See Hardware monitoring JACE-NXS configuration.
-
PowerMonitorService — Provides monitoring of the SITOP UPS module connected via USB cable to the JACE-NXS, including alarms in the event of a power failure, battery test failure, or USB connectivity problem. See Power monitoring JACE-NXS configuration.
Also, you may review the parent container’s PlatformService properties and optionally adjust, if needed.
Unlike in a station running on a QNX-based JACE, the child SerialPlatformService contains read-only properties—JACE-NXS serial port setup is done in the operating system, Windows XP.However, there is also 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 13). These platform services support installations where all configuration must be possible using only a browser connection (and not Workbench connected to the JACE’s platform daemon).