| Auto-start |
check box |
Specifies whether the station starts following platform daemon startup. A station restart occurs:
- Following a host reboot, such as after a power cycle
- As the result of a Reboot command
- Following the installation of any dist file(s)
- Following any TCP/IP-related changes
- When changing any existing module (upgrading or downgrading)
A station restart may or may not follow the installation of new modules using the Software Manager—say, for a new driver. If a station restart is required for a module to become effective, a reboot is prompted.
|
| Restart on Failure |
check box |
Specifies whether the platform daemon restarts the station if its process exits with a non-zero return code (for example,
the engine watchdog had killed the station because of a deadlock condition).
In
Niagara 4, controllers can have a station restart without a reboot. Therefore, if this option is enabled, and the station fails (terminates with error), the station is restarted.
If a controller has three automatic restarts within 10 minutes (or however many specified in the station’s PlatformService
Failure Reboot Limit property, the station remains in a failed state, regardless of the setting above.
|
| Start |
Button enabled if the selected station has an Idle or Failed status in the installed applications area.
|
When pressed, the host’s platform daemon immediately starts the station, clears the text in the station output, and displays
messages for the new station.
|
| Stop |
Button enabled if the selected station has a Running status in the installed applications area.
|
When pressed, opens a popup confirmation window. If you confirm, the host’s platform daemon shuts the station down gracefully (saving configuration to its config.bog file, and potentially saving history data).
|
| Restart |
Button enabled if the selected station has a Running status in the installed applications area.
|
When pressed, opens a popup confirmation window. If you confirm, the host’s platform daemon shuts the station down gracefully,
then restarts it.
|
| Reboot |
Button always enabled. |
When pressed, opens a popup confirmation window. If you confirm, reboots the selected host. This is considered a drastic action.
|
| Kill |
Button enabled only if the selected station has a status of Starting, Stopping, or Running the installed applications area.
|
When pressed, opens a popup confirmation window. If you confirm, the host’s platform daemon terminates the station process
immediately.
Always use Stop instead of Kill, unless unavailable (stuck for a long time as either Starting or Stopping). Unlike a station stop, a station kill does not cause the station to save its database (config.bog), histories or alarms,
nor does it update the station output area.
|
| Dump Threads |
Button enabled only if the station has a Running status in the installed applications area.
|
When pressed, the host’s platform daemon has the station send a VM thread dump to its station output. |
| Save Bog |
Button enabled only if the station has a Running status in the installed application area.
|
When pressed, the host’s platform daemon has the station locally save its configuration to config.bog. |
| Verify Software |
Button enabled regardless of station status. |
When pressed,
Workbench parses the station’s config.bog and the host’s platform.bog files, looking for module references. It then checks to see if
those modules (and any other software upon which they depend) are installed. If available in your
Workbench installation, any missing software is listed in a popup window, the window offers to install the missing software into the
remote host.
Only modules (or versions of modules) needed by the station are installed that do not require commissioning. If the station
needs modules that require commissioning, meaning an upgrade of core software, those modules are not copied.
|
| Clear Output |
Button enabled only if the station has a Running status in the installed application area.
|
When pressed, the button toggles to Load Output, and the next press toggles back to Pause Output (and so on).
- During a paused output, text remains frozen in the standard ouput area. This is useful when the station is rapidly writing
output.
- When you press Load Output, text in the station output area is reloaded with the station’s buffered output, and output remains updating in real time.
|
| Output Dialog |
Button enabled regardless of station status. |
When pressed, it produces a separate non-modal output window displaying the same output text as in the Application Director’s standard output area. Included are buttons to Dump Threads, Pause Output, Clear Output, and Close the window.
NOTE: You may find this compact version of a station’s standard output easier to work with than in the main area of the Application Director. Also, if needed you can open multiple output dialogs for comparison purposes.
|
| Stream To File |
Button |
Opens a window for assigning a file name. Once open, the system saves all application output to this file. |
| Output Settings |
additional properties |
Opens a window for specifying how the platform daemon buffers the output from the station. |
