soapInstances

Inspect running instances, trigger scenarios, and check logs.

Purpose

The Instances section covers two views: the Instances list and the Instance View (detail tabs). Use the list to locate and manage running instances, and use the Instance View to inspect state, run scenarios, and troubleshoot behavior.

Back to UI Overview: UI Overview.

Where to find it

In the UI navigation, select Instances to open the list. Use the Open action to open the Instance View in a new tab.

Instances list

The list shows active instances with Name, Model, and Status. It also provides model filtering, creation, and bulk actions.

1

Filter the list by model to focus on a specific group.

Filter instances by model name
2

Create a new instance (single or bulk) by choosing a model and name or name prefix.

Adding new instance
3

Select instances and use bulk actions to start, stop, delete, or open multiple rows.

Bulk operations on selected instances
4

Use per-row actions (Start, Stop, Delete, Open) and the status indicator to control or inspect a single instance.

Instance View

Open the Instance View in a new tab from the list. The header shows the instance name, model, and current status, and the control bar provides action buttons.

Instance view

Controls and modes

  • Use Continuous mode for Start/Stop and real-time updates.

  • Use Stepper mode to Prepare and Run single steps.

  • Use Reset or Delete to clear state or remove the instance.

  • Stop actions use a dedicated stop icon, and command actions show short visual feedback after successful send.

Tabs and panels

  • Attributes: view and edit attribute values, select axes, and inspect the time-series chart (range, refresh rate, clear, export CSV, print). The table also shows a responsive UNIT column (when space allows), command/key attribute styling, and a short “Command sent” badge after command writes.

Instance attributes, and time-series chart

Image placeholder: Attributes table with UNIT column and command feedback badge.

  • Physics: review actions, toggle enabled state, and inspect action attributes.

Physics tab (actions)
  • Scenarios: start or stop scenarios and confirm state transitions.

Defined ready to use scenarios
  • Communication: review protocol bindings, toggle enabled state, and open per-binding logs. When a log row is expanded, live updates are temporarily held to keep the view stable.

Communication with protocols
Communication logs (per attribute/register/binding)
  • Polling: inspect per-instance polling attributes and adjust settable values.

Instance polling parameters
  • Timer: inspect per-instance timer attributes and adjust settable values.

Instance timer parameters
  • Logger: view instance logs and confirm there are no errors. For cross-instance diagnostics, use the dedicated Logs page.

Instance logs

Typical workflow

  1. Open Instances and filter by model if needed.

  2. Create or select an instance and check its status indicator.

  3. Open the detail view, review Attributes, and select axes to plot in the chart.

  4. Run a scenario (or toggle an action in Physics) and confirm values change.

  5. Check the Logger tab for errors or warnings.

  6. If needed, switch to Logs and compare instance logs with system-level logs.

What to verify

  • Integrator: the status indicator reflects the expected state and values change when the SUT drives them.

  • QA: scenario start/stop commands update values while time is stepped deterministically.

  • Developer: Start/Stop or Prepare/Run commands take effect and Logger stays clean.

Common issues

  • Server connection not established: connect in Settings and refresh the list.

  • No instances for selected model: clear the model filter or re-run the installer bootstrap.

  • Instance detail shows "not found": the instance was deleted or renamed; refresh the list.

  • Commands disabled: check the instance state and selected mode (Continuous vs Stepper).

  • Logger shows errors: align timestamps with recent changes and check model logs.

  • Chart feels “too short”: the history buffer is large (up to 100000 entries), so use range controls to focus the view.

Last updated