Skip to main content

Signals and thresholds

Signal tree​

Drag a signal from the tree at the bottom left onto a plot in the Live tab. Signals the controller declares are at the top; built-in signals are under Built-in. For per-joint signals, expand the group and pick one joint at a time.

GroupKindSignals
Controller signals (such as error, eso_comp)One sample per control cycleWhatever the controller declares
rt_rawRaw data, one sample per control cyclePer joint: actual position, velocity and torque (actual_position, actual_velocity, actual_torque), commanded position and torque (command_position, command_torque); bus cycle time and cycle error
rt_diagnosticsDiagnostics aggregated over a window of about 1 secondMaximum and mean time of the control loop and bus cycle, overrun count, command update latency, EtherCAT missed-response count and more
ft_sensorOnly on robots with a tool F/T sensor. About 100 HzForce force x/y/z [N], torque torque x/y/z [N·m] (sensor frame, no gravity compensation)

actual_torque is estimated from motor current, not measured by a torque sensor. In rt_diagnostics, …_max is the worst cycle in the 1-second window and …_mean is the window average.

F/T sensor signals​

In the signal tree, the ft_sensor group under Built-in is expanded to show force x, y, z [N] and torque x, y, z [N·m]. The Live tab plots force z [N] and torque x [N·m].

  • The ft_sensor group appears only after the first reading of this connection arrives. It does not appear on robots without a sensor, and after a reconnect it hides again until the next reading.
  • Stretches where the sensor sent invalid values (cable unplugged, overload, frozen value) are dropped, not drawn as 0. The plot bridges them with a straight line, exported files leave them empty, and threshold dwell time does not count across them.
  • F/T signals have no gap chip.
  • Export them like the other built-in signals, with the pane's download button. Run & capture recordings do not include them.
  • A layout that contains ft_sensor opens without a warning on a robot without a sensor; that signal just stays empty.

For sensor setup and zeroing, see F/T sensor.

Working with plots​

The Live tab split in two. The top pane plots three error channels, the bottom pane plots eso_comp[0], and a right-click menu (Split horizontally · Split vertically · Thresholds… · Close) is open over the top pane.

ToDo this
Change the time windowThe 1s … 120s buttons at the top, or type a number (1–120 seconds)
Pause and inspectDrag on a plot to zoom; this pauses the view (Paused · data kept · drag to zoom). Double-click or Resume to go live again
Read valuesHover over the plot to see each signal's value
Split a plotThe buttons at the pane's top right, or right-click → Split horizontally / Split vertically
Hide or remove a signalClick its chip on the pane to hide it (the axis stays). The chip's ✕ removes it
ClearThe eraser at the top discards the data in every plot
ExportThe pane's download button saves that pane's signals as CSV and JSON

The Live tab split into a top and a bottom pane. The top pane plots three error channels and the bottom pane plots eso_comp[0].

  • Data keeps accumulating while the view is paused.
  • The gap chips at the top show transport gaps. The controller signal chip shows the number of gaps and the time missing; the rt_raw chip shows the number of samples lost.
  • Over a wide window the plot is drawn from a summary, but recording and threshold checks use the data as received.
  • Controller signal amplitudes have no physical unit. Only time (s), percentages and the built-in timing signals (µs, ns) carry units.
  • When the robot is BRAKED, the tab shows BRAKED — no live telemetry. Switch to TRAJECTORY to stream signals.

Saving layouts​

You can save the pane arrangement, signals, threshold bands and time window to a JSON file and load it again with the save and open buttons at the top. Built-in… offers ready-made layouts, such as a cycle jitter watch. If a loaded signal is not in the current controller, Lab skips that signal and tells you.

Thresholds: convergence and violation​

Put a band on a signal and the console judges it for you. Add one with the pane's target button, or right-click → Thresholds….

The Thresholds panel after pressing Add band: fields for Target signal, Mode (Converge), Min −2, Max 2 and Dwell 1 s, and an Add threshold button.

FieldMeaning
Target signalOne of the signals in the pane
ModeConverge: staying inside the band counts as converged. Violate: leaving the band counts as a violation
Min · MaxThe band. Equal values mean "exactly this value"
Dwell (s)How long the condition must hold. 0 means the first matching sample decides

When a band decides, a badge appears on the pane: green for converged, red for violated. Click the badge to open its report.

The convergence report. Settling metrics lists Time since armed, Overshoot (beyond band), Steady-state error, Mean, Std dev, Min and Max. Below, Gain snapshot (at convergence) shows the controller's kp and b0 at convergence, with Export, Re-arm (same band) and Remove band buttons.

Convergence report

ItemMeaning
Time since armedTime from arming the band to convergence. If you applied a gain after arming, it reads Settling time (since last gain apply) and counts from that apply
Overshoot (beyond band)How far the signal went past the band
Steady-state errorMean of all samples since arming, minus the band centre. It is not the error of the settled stretch alone
Mean · Std dev · Min · MaxStatistics since arming
Gain snapshotThe gains the controller was using, shown when tuning was not locked (see Gains). Otherwise No tuning gains recorded.
ButtonAction
ExportExports CSV and JSON
Re-arm (same band)Watches again with the same band
Remove bandDeletes the band
Close (✕, Escape, click outside)Keeps the band

Violation report

Shows the time of the first violation, the violation count, the last violation, and whether the data had gaps while watching.

ButtonAction
Re-arm (same band)Resets the count
Remove bandDeletes the band
CloseKeeps watching

Gaps in a controller signal do not count toward dwell time. rt_raw is different: even with lost samples, the time between neighbouring samples counts in full.