Measuring response time
The response time is the time from setting a PLC output until the model’s answer arrives as a PLC input. It is the number that decides whether your PLC logic sees the model react in time. CONNECT can measure it without a PLC program: it plays the PLC’s part itself.
Each measurement repeats this many times and reports the statistics. It covers CONNECT, the connection to the browser, the browser’s signal handling and one simulation step. It does not include your PLC’s own scan time or the network between the PLC and CONNECT.
Requirements
Section titled “Requirements”- CONNECT is connected, and the model is loaded in exactly one tab that holds the document. If no tab has the model, or several tabs could answer, the measurement is refused.
- A signal pair: one PLC output that CONNECT writes, and one PLC input that the model answers on. Both must be Bool signals with the right direction. Something in the model must switch the input when the output changes, for example a signal that a component or logic step writes in response.
- Neither signal is forced, and no CONNECT signal mapping writes the input signal. The answer has to come from the model.
Run a measurement
Section titled “Run a measurement”- Open the CONNECT page and find the Response time section.
- Pick the Output signal and the Input signal from the lists. They only show Bool signals of the matching direction.
- Optionally change Samples (default 200), Pause between samples in ms (default 100) and Timeout per sample in ms (default 2000).
- Click Measure. Progress shows as completed over requested samples.
The original value of the output signal is restored when the run ends. Only one measurement can run at a time.
For the most useful result, set the performance level first and keep the tab visible while you measure. To compare levels, run the same pair once at Low and once at High and note which level each result belongs to.
Read the result
Section titled “Read the result”| Value | Meaning |
|---|---|
| Mean | Average response time in milliseconds over all successful samples |
| Min / Max | Fastest and slowest successful sample |
| P95 | 95 % of the samples were at least this fast. Use it instead of the mean when you care about the worst typical case. |
| Samples | Number of successful samples |
| Timeouts | Samples that got no answer within the timeout. A timeout is counted, never entered as a time. |
The values stay empty until the first sample succeeds. A run that ends early keeps its partial result.
If no sample gets an answer, the page shows No answer on signal. Check that the model is loaded, that a component actually writes the selected input, and that the tab holds the document (see document ownership).
Why a measurement is refused or stopped
Section titled “Why a measurement is refused or stopped”CONNECT refuses to start when the setup cannot give a valid result, and names the reason.
| Refusal | Cause and fix |
|---|---|
| invalid-request | A value is out of range. Samples: 10 to 5000. Pause: 0 to 5000 ms. Timeout: 100 to 60000 ms. Both signals must be given and different. |
| busy | Another measurement is still running. Wait for it to finish. |
| unknown-signal | A signal does not exist on the gateway. Check the name. |
| not-bool | A signal is not a Bool. Pick Bool signals. |
| wrong-direction | The output must be a PLC output and the input a PLC input. |
| forced | A signal is forced. Release the force first. |
| mapping-writes-input | A CONNECT signal mapping writes the input. Disable the mapping or choose another input. |
| no-viewer | No browser with the model is connected to CONNECT. Open the model. |
| ambiguous-viewer | Several tabs could answer. Close all tabs except the one that holds the document. |
A running measurement stops as aborted with a reason, and you keep the partial result:
| Abort reason | Cause |
|---|---|
| viewer disconnected | The answering tab closed or lost its connection. |
| interface disconnected: name | The interface that owns one of the two signals left the Connected state. |
| signal removed: name | One of the signals was removed or renamed during the run. |
| no answer | A sample timed out, and the next one timed out again after CONNECT resynchronized. |
Browser-side timing
Section titled “Browser-side timing”While a measurement runs, the browser also records its own part of the loop. Read it with web_status and detail: "full", or with connect.loopProbe.status. The signalChain block contains:
| Field | Meaning |
|---|---|
active, probeId, outSignal, inSignal, reason | The current or last announced run and why it ended |
received, samples, superseded | Output edges received, samples completed, and edges replaced by a newer value before they were applied |
receiveToCommit | From receipt of the value to its application in the model, including the wait for the next simulation step |
commitToSend | From application until the answering input value is sent back |
receiveToSend | The whole browser part of the loop |
Each timing has meanMs and maxMs, empty until a sample is complete. The browser part is a subset of the gateway’s total. The difference is the transport time between CONNECT and the browser. Superseded and incomplete samples are left out.
Commands
Section titled “Commands”Both commands work from the page and from an AI assistant: connect.loopProbe.run through web_execute, connect.loopProbe.status through web_query. A measurement is not recorded into macros.
connect.loopProbe.run- starts a measurement withoutSignal,inSignaland optionalsamples,pauseMs,timeoutMs. It returns at once; the run continues in the background.connect.loopProbe.status- read-only. Returns state (idle,running,done,aborted), reason, progress, the statistics and thesignalChainblock. The gateway offers the same throughGET /diagnose/loop-probe; see REST and WebSocket API.
Limits
Section titled “Limits”- The loop shows what CONNECT and the browser add. It cannot measure your PLC’s acquisition or CONNECT’s write to the PLC.
- Only the latest value of a signal is transmitted. A pulse shorter than a polling or sending step can be overwritten, so use signals that stay set long enough, as the measurement does.
- A hidden tab, a busy computer or a long frame raises the maximum and the P95. Repeat the measurement on a quiet machine before you draw conclusions.