Managing PlatformServices properties

The properties in this topic apply in general to all controllers. Specific differences are noted.
Prerequisites: The controller is licensed with the dataRecovery feature. A station in the controller is running and open in Workbench.
  1. In the Nav tree, click Services > PlatformServices.
    The Platform Service container view opens in the view pane.
    Image

    Some properties are read-only status types, similar to many seen in the Platform Administration view. Other configuration properties are available. A group of three properties allows adjustment of the time, date, and time zone settings for the host controller (alternately accessible using a platform connection to the host). Access to these properties is useful if the installation requires all setup access using a browser only.

  2. Scroll down to the Battery Present property.
    Image

    By default, Battery Present is set to true. This is the proper setting for any controller, unless:

    • The controller has SRAM and has no backup battery installed (NiMH and/or external 12V), and:
    • The controller has the DataRecoveryService running and enabled (license includes a dataRecovery feature).

    In this case only, set Battery Present to false and click Save. After the next reboot (required), this configuration property prevents battery bad nuisance alarms from occurring.

  3. As needed, review other platform service configuration properties, which include the following:
     
    NOTE: Leave these properties at their default values, unless otherwise directed by Systems Engineering.
    • Locale — determines behavior that is specific to your geographical location, such as date and time formatting, and also which lexicon to use. The string you enter must use the form: language [“_” country [“_” variant]]

      For example U.S. English is en_US and traditional Spanish would be es_ES_Traditional.

    • Engine Watchdog Policy — defines the response taken by the platform daemon if it detects a station engine watchdog timeout. With the watchdog, the station periodically reports to the platform daemon its updated engine cycle count. The purpose of the watchdog is to detect and deal with a hung (stalled) station, and is automatically enabled when the station starts.

      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 platform. If automatic start is enabled, the station restarts after the system reboots.
    • Engine Watchdog Timeout — defaults to one (1) minute with a range of 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 enables (default) or disables the feature.

      Allows for the automatic saving of a running station to the config_backup_<YYMMDD>_<HHMM>.bog file at the frequency defined by the next property. Auto-saved backup files are kept under that station’s folder.

    • Station Auto-Save Frequency — defaults to every 24 hours for any embedded controller with a range of from one (1) to many hours.
    • Station Auto-Save Versions to Keep — defaults to zero (0). Once the specified limit is reached, the oldest of the saved backups is replaced at the next manual save or auto-save backup. Significant flash space is saved by keeping this property set to 0 or perhaps 1.
    • RAM Disk Size — Specifies in MB the size of RAM disk used to store history and alarm files. where the default is 32 for JACE-3E, JACE-6 and JACE-6E series, or 48 for JACE-7 series.

     

    For further details on these and other PlatformServices properties, refer to the Niagara Platform Guide.

  4. To write any configuration change to the host controller, click Save.