Record — Control Systems/Sinks

Record

Control Systems / Sinks

Plots what it receives and keeps it: the traces are drawn live on the chart attached to the block, and the same samples are saved into the variables space as time series, so a run's data outlives the run it was watched in. One trace and one variable per scalar channel – a [3,1] input draws three lines and saves three series.

Ports

• Inputs – one by default, and the count is user-editable. Any signal size is accepted.
• No outputs – Record is a pure sink and passes nothing on.

Channels

One variable per scalar channel, in port and element order. A single channel takes the configured name exactly as typed; several take name_0, name_1, and so on – the same naming the Signal Recorder uses.

Parameters

• Variable Name – the name to record under. This names something the block creates, so it is not looked up in the variables space; an existing variable of that name is overwritten at the end of the run.
• Max Samples – memory cap on the recording. Once reached, the most recent samples are kept and the oldest are dropped. Simulink's counterpart defaults to inf; a finite cap is kept here because a recorded series is stored in the project.
• Decimation – keep every Nth sample. 1 keeps every sample. It gates the plot and the recording together, which is the difference between this block and a Scope wired beside a Signal Recorder: what you see is exactly what was kept.
• Sampling Time (s) – how often a sample is taken. Zero or less inherits the solver's rate; a positive value runs the block at that period.

Code export

All ten targets: Python, MATLAB, Java, Rust, C, C++, VHDL, Verilog, SystemVerilog and PLC Structured Text – but no target has a chart or a variables space, so each records the way that target can be read back. The nine console targets stream one channel,time,value line per retained sample, so the run's transcript is a CSV of exactly the samples the in-app block would have kept and drawn, with identical channel names, channel order and decimation. PLC Structured Text instead owns one ring buffer per channel, sized to "Max Samples" – making ST the one target that reproduces the most-recent-N truncation exactly, and leaving the recording observable from an HMI or trace.

Simulink bridge

Import and export, mapped to simulink/Sinks/Record. "Variable Name" to VariableName, "Max Samples" to MaxDataPoints, "Decimation" to Decimation. "Sampling Time (s)" does NOT cross – Simulink's Record block defines no SampleTime parameter at all, and writing one is a hard error that aborts the whole generated script, so the rate stays on the ICore side and a Record configured with an explicit rate reports that it did not cross. The port count has no parameter behind it either: Simulink derives it from the block's own port configuration rather than from a settable number, so a multi-input Record must be widened on the far side.

Notes

• The recording is handed over when the run finishes, not while it runs; the traces, by contrast, are drawn live.
• The traces are cleared at the start of every run. The recorded variables are not – they are ordinary variables, and the previous run's are overwritten only when this run finishes.
• On an infinite simulation the chart streams a rolling window while the recording still honours "Max Samples".