How to read the Pulsenics dashboard — experiment states and panels
This article helps interpret what the Pulsenics Cloud Dashboard is showing during and after an experiment. Use it to understand experiment status, control delivery, hardware availability, and what to ask the client next based on what they are seeing or sharing.
This article helps interpret what the Pulsenics Cloud Dashboard is showing during and after an experiment. Use it to understand experiment status, control delivery, hardware availability, and what to ask the client next based on what they are seeing or sharing.
Probe model scope: The error message thresholds and fault descriptions in this article are based on the Probe V4 200–1200 A user manual and are also applicable to the Probe V4 100. They do not directly apply to the Probe V3 or the Probe 20/40, which have different operating limits and error thresholds. If the client is on a V3 or Probe 20/40, treat fault descriptions and threshold values as indicative only and escalate to Pulsenics for confirmation.
If you are unsure which Probe model the client has: a V4 has an EIS enable switch on the front panel. The model is also printed on the label on the back of the Probe.
Agent guidance — when a client shares a screenshot
When a client uploads a screenshot of the Pulsenics Dashboard experiments page, look for these elements in order:
- Probe Controls panel — were controls sent and received?
- Probe Messages panel — what is the most recent message and when was it sent?
- Hardware selection — is the Probe and CMU showing as available and green?
Experiment status bar
The status bar at the top of the experiment shows current state and progress.
| What you see | What it means | What to do |
|---|---|---|
| Green bar, percentage increasing | Experiment is running normally | No action needed |
| Green bar at 100% | Experiment completed all scheduled sampling | Confirm data is visible in Analytics |
| Orange or red text: "Experiment was stopped on [date] by [name]" | Experiment was manually stopped by a user | Check who stopped it and why — ask client if this was intentional |
| "Stopped Reason" button visible | A stop reason was recorded | Ask client to click the button and share what it says |
| Progress bar not moving | Sampling may be paused or stuck | Check Probe Messages for last known state |
Key point: "Stopped by [name]" always means a manual stop by that user — it is never an automatic system fault. If the client did not intend to stop the experiment, someone else on their team may have.
Stopped Reason button
The Stopped Reason button appears when an experiment has been stopped. It records the reason the stop command was sent.
Ask the client: "Can you click the Stopped Reason button and share what it says?"
Common stopped reasons and what they mean:
| Stopped Reason | What it means |
|---|---|
| Manually stopped by user | A user clicked Stop — intentional action |
| Output Over Current Detected | The Probe hit a current limit — see the overcurrent KB article |
| SIGEN fault | Signal generation fault — escalate to Pulsenics |
| Unable to take response | Probe could not achieve the requested measurement — see overcurrent KB article |
| Probe disconnected | Probe lost connection during the experiment — check network |
Probe Controls panel
The Probe Controls panel shows every control command sent to the Probe, when it was sent, when it was last resent, and how many times it was resent.
Key fields to read:
| Field | What it means |
|---|---|
| Type | The control command sent (e.g. Stop Sampling, Batch Sampling) |
| Added On | When the control was created in the dashboard |
| Last Sent On | When the Probe last received or acknowledged it |
| Number of Resent | How many times the dashboard had to resend — high numbers suggest connectivity issues |
| Added By | Which user sent the control |
How to interpret:
| What you see | What it means | What to do |
|---|---|---|
| Last Sent On is close to Added On, Resent = 0 | Control was received cleanly | No action needed |
| Last Sent On is much later than Added On | Probe was not reachable when control was sent | Check network connectivity |
| Number of Resent is high (3+) | Probe connection was unstable during this period | Review connectivity — see Probe offline or measurement restart articles |
| Control shows but experiment state has not changed | Probe may not have acted on the control | Check Probe Messages for confirmation |
| Stop Sampling control present, Sampling Rate: Stopped in Messages | Stop was received and confirmed by Probe | Experiment stopped cleanly |
Probe Messages panel
The Probe Messages panel shows the most recent 300 messages from the Probe in reverse chronological order (newest first). This is the primary source of ground truth for what the Probe was doing.
How to read it:
| Message | What it means |
|---|---|
| Starting 5.00 Hz – 40000.00 Hz at 0.400A with 30 pts, 30 simultaneous | New measurement run beginning — shows full configuration |
| Sampling Started: [range] Hz | Probe began sampling that frequency range |
| Estimated time remaining: X minutes Y seconds | Probe is actively sampling |
| Sampling Completed: [range] Hz | That frequency range finished successfully |
| Finished [range] Hz at [amplitude] | Full measurement run completed |
| Sampling Rate: Stopped | Probe confirmed it received and acted on a stop command |
| Output Over Current Detected | Current limit hit — see overcurrent KB article |
| SIGEN fault [number] | Signal generation fault — note the fault number and escalate |
| Unable to take response when injecting AC | Probe could not drive the requested perturbation — see overcurrent KB article |
| Probe reconnected | Probe lost and re-established connection — may trigger resample if enabled |
Healthy sequence looks like: Starting → Sampling Started (each range) → Estimated time remaining → Sampling Completed (each range) → Finished
Interrupted sequence looks like: Starting → Sampling Started → Starting (again, before previous Finished) → this indicates a restart — see measurement restart KB article
Hardware selection — Probe and CMU status
In the Hardware Selection section of an experiment, status indicators show whether hardware is available and online.
| Indicator | What it means |
|---|---|
| Green dot next to Probe | Probe is online and available |
| Yellow dot next to Probe | Probe is connecting but not stable |
| Grey or no dot | Probe is offline — cannot start experiment |
| Green dot next to CMU | CMU is online and communicating |
| No CMU shown | CMU is offline or not reporting — check cable and Probe boot state |
If hardware shows as unavailable when the client is trying to start an experiment, see: Why can't I start an experiment in the Pulsenics dashboard?
What to ask when a client shares a dashboard screenshot
Use these questions to extract the most useful information quickly:
- "Can you click the Stopped Reason button and share what it says?"
- "What is the most recent message in the Probe Messages panel, and what time did it appear?"
- "In the Probe Controls panel, what does the Number of Resent show for the last control?"
- "Is the Probe status indicator green, yellow, or grey?"
- "Can you paste the last 4–5 lines from the Probe Messages panel as text?"
Article status
This is a reference article for interpreting Pulsenics Cloud Dashboard states during and after experiments. Additional states and interpretations will be added as more cases are identified.
Tags: dashboard, experiment status, Probe Messages, Probe Controls, Stopped Reason, hardware selection, CMU status, sampling, stopped, overcurrent, SIGEN fault, controls not received