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”.
Current local time in host (read-only if a Windows host).
Current local date in host (read-only if a Windows host).
Current local time zone for host (read-only if a Windows host). For more details, see “Time Zones and Niagara 4” on page 129.
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:
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.
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.
Default is every 24 hours for any JACE platform, or every (1) hour if a Windows host. Range is from 1 to many hours.
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.
(Applies only if a JACE host other than a JACE-8000) Applies to configuration of a JACE’s backup battery. Used to specify whether the controller has an integral backup battery, typically an onboard NiMH battery. The default property value is true—which is recommended unless the controller is both SRAM-equipped and is without an attached backup battery (there is no way to detect the latter through software).
If set to false and saved, upon the next reboot the station’s PowerMonitorService no longer monitors for a backup battery,
with the underlying “power daemon” stopped. This prevents nuisance “battery bad” alarms. Station backup is dependent totally
on SRAM and the station’s DataRecoveryService (the JACE must have the platDataRecovery module installed, and be licensed for DataRecovery).
The configuration described above is only one of three possible backup options for an SRAM-equipped controller that can also have a backup battery installed (e.g. JACE-6E or JACE-3E, or else a JACE-6 or JACE-7 with an SRAM option card). The two other options are to use both backup battery and SRAM for backup, or to use backup battery only (and not SRAM). These other two options require that this Battery Present property is set to true.
For related details, refer to the document JACE Data Recovery Service (SRAM support).
(JACE platforms only) Limits the number of station restarts that can be triggered by station failures, within the Failure Reboot Limit Period, below (if the host is so configured using the Application Director, see “Start checkboxes” on page 33). Default value is 3.
(JACE platforms only) Specifies the repeating frequency of the Failure Reboot Limit period, with a default value at 10 minutes.
These two “Failure Reboot” settings are also adjustable (in any version of QNX-based host) within that JACE’s !daemon/daemon.properties file, in the following two properties:
failureRebootLimit=x (where x is integer, default is 3)failureRebootLimitPeriod=y (where y is long in milliseconds, default is 3600000)Has one configurable field and one read-only field:
Has one configurable “Min Free” field, in MB. Specifies the minimum free Java heap size, in MB, against which the station compares (tests) for low memory conditions, that is excessive Java heap. The default varies according to JACE model.This test automatically runs once a minute. If the heap free byte count is less than the defined minimum free heap size, a “low memory warning” appears in all Workbench views of the station. The warning is a yellow message box overlaid on any new view accessed, or on any current view that is refreshed. This warning is removed when the heap free byte count rises above the defined minimum size—such as might occur if enough components are deleted from the station.
All memory statistics, including those for heap, are accessible on a station opened in Workbench, via the Resource Manager view of the Station component.
Has one configurable “Min Free” field, related to number of files (and/or open sockets). Specifies the maximum amount of file descriptors that can be used. That is, the read-only “Max Open” number minus the “Min Free” amount. File descriptors are used for histories, modules, and Fox connections If exceeded a “Station has too many open files or sockets” warning is overlaid in all Workbench views of the station.
Has one configurable “Min Free” field, in KB. Specifies the minimum RAM that can be left free during station operation. If status is not Ok, a “Low free RAM” warning is overlaid in all Workbench views of the station.
Has one configurable “Min Free” field, in %. Specifies the minimum percentage of disk storage that can be left free during station operation. Below this amount, a “Platform running low on disk space” warning is overlaid in all Workbench views of the station.
Has one configurable “Min Free” field, to specify the minimum number of free files available during station operation. Below this amount, a related platform warning appears. Note that the PlatformServiceContainer status property “Filesystem” includes both the current number of files and the maximum number of files for each partition on a JACE controller.
Also see the section “Model-specific PlatformServiceContainer properties”.
Copyright © 2000-2016 Tridium Inc. All rights reserved.