System Platform Service Plugin (platform-SystemPlatformServicePlugin)

System Platform Service Plugin allows you to view and edit platform properties on a Windows-based host running the station, and is the default view on the station’s System Configuration (SystemPlatformServiceWin32).

Figure 1. System Platform Service Plugin view


To access, click Config > Services and right-click PlatformServices > Ax Property Sheet then right -click SystemService > Views > System Configuration.

Column Name Description
Name Name of running station.
Host IP address of host platform.
Model Model of host platform type, such as NPM6, JACE-8000, or Workstation.
Model Version Reports the version number of the host model.
Product Defines the product.
Host ID Niagara host identifier, a string unique to this one machine.
Niagara Version Version and build number of the Niagara distribution running in the host platform.
Java VM Name Java virtual machine used, for example, “Java HotSpot(TM) Embedded Client VM” for any N4 controller, or “Java HotSpot(TM) 64-Bit ServerVM” for a Supervisor on a Windows host.
Java VM Vendor Vendor for Java VM: Oracle Corporation.
Java VM Version Version of Java VM, for example, “25.0-b 70” for the Java 8 compact3 VM on a controller, or “25.31-b07” for the Java 8 SE VM on a Windows host.
OS Name Operating System name, such as “QNX” or “Windows 10.”
OS Arch. Machine architecture for OS, such as “arm” or “ppc” (controller hosts) or “amd64” (Windows hosts).
OS Version Operating System version, such as “6.5.0” (QNX) or “10.0” (Windows 10).
Platform Daemon Port Port number on which the platform daemon that started the station is listening for its platform server (3011, or another port number). This can prove useful in case you changed the platform port, but then forgot what the new port is.
Platform Daemon TLS Port Port number on which the platform daemon is listening for its platform TLS server (5011, or another port number, provided that platform TLS enabled). If platform TLS is disabled, it reads Unknown. This can prove useful in case you changed the platform TLS port), but then forgot what the new port is.

In the container plugin, most of the remaining entries are configuration propertiess. However a few status values are also mixed in, and are described below.
Locale Determines locale-specific behavior such as date and time formatting, and also which lexicons are used. A string entered must use the form: language [“_” country [“_” variant]]. For example, U.S. English is “en_US” and traditional Spanish would be “es_ES_Traditional”.
System Time Current local time in host (read-only if a Windows host).
Date Current local date in host (read-only if a Windows host).
Time Zone Current local time zone for host (read-only if a Windows host).
Engine Watchdog Policy The engine watchdog is a platform daemon process, to which the station periodically reports its updated engine cycle count. The watchdog purpose is to detect and deal with a “hung” or “stalled” station, and is automatically enabled when the station starts.

The Engine Watchdog Policy defines the response taken by the platform daemon if it detects a station engine watchdog timeout. Watchdog policy selections include:

  • Log Only — Generates stack dump and logs an error message in the system log. (The station should ultimately be restarted if a watchdog timeout occurs with the “Log Only” setting).

  • Terminate — (Default) Kills the VM process. If “restart on failure” is enabled for the station (typical), the station is restarted.

  • Reboot — Automatically reboots the host controller platform. If “auto-start” is enabled for the station, the station is restarted after the system reboots.
Engine Watchdog Timeout Default is 1 minute, and range is from 0 ms to infinity. If the station’s engine cycle count stops changing and/or the station does not report a cycle count to the platform daemon within this defined period, the platform daemon causes the VM to generate a stack dump for diagnostic purposes, then takes the action defined by the Engine Watchdog Policy.
Engine Station Auto-Save Either Enable (default) or Disable. Allows for “auto save” of running station to “config_backup_<YYMMDD>_<HHMM>.bog” file at the frequency defined in next property. Auto-saved backup files are kept under that station’s folder.
Station Auto-Save Frequency Default is every 24 hours for any JACE platform, or every (1) hour if a Windows host. Range is from 1 to many hours.
Station Auto-Save Version to Keep

Oldest of kept backups is replaced upon next manual save or auto-save backup, once the specified limit is reached. The default value for JACE platform is 0 (none), and should be kept low.

However, changing to 1 provides a benefit in the case where a catastrophic (yet inadvertent) station change is made, such that a station “kill” can be issued to revert back to the backup copy on the JACE.

In Windows hosts, the default is 3, and typically can be safely adjusted up, if desired.
Number of CPUs Number of CPUs used in the host platform (typically 1 if a controller, more if a Windows host).
Current CPU Usage Percentage of CPU utilization in the last second.
Overall CPU Usage Percentage of CPU utilization since the last reboot.
Filesystem File storage statistics for the host, including total file space, available (free) space, and file block size (minimum size for even the smallest file). For the JACE-8000 host, it may look similar to:
 Total         Free      Files  Max Files
    /        3,476,464 KB 3,039,088 KB  602     108640
/mnt/aram0     393,215 KB   381,019 KB    0          0
/mnt/ram0        8,192 KB     8,192 KB    0          0
Physical RAM Current total and free RAM statistics for the host. For the JACE-8000, it may look similar to:
Total Free
 1,048,576 KB 113,424 KB