Rise Time — Control Systems/Pulse Metrics

Rise Time

Control Systems / Pulse Metrics

Reports the duration of the most recent rising transition – the time the waveform took to travel from the lower reference level to the upper one, 10% to 90% by default. This is MATLAB's risetime.

⚠ The two endpoints are found asymmetrically, and that is IEEE Std 181-2003 rather than a shortcut: the lower endpoint is the last crossing of the lower level at or before the transition instant, and the upper endpoint is the first crossing of the upper level at or after it. On a clean edge the two rules agree; on an edge that wobbles near a reference level they do not, and a block that took the first of both would report a longer rise than MATLAB does.

Ports

• u – the bilevel waveform to measure. Scalar – see Notes.
• r – the duration of the most recent rising transition, in seconds, held until the next one. Scalar.

Parameters

• Low State Level – the value the waveform sits at in its low state. 0 by default.
• High State Level – the value it sits at in its high state. 1 by default. Every threshold below is a percentage of the distance between these two, so they must differ.
• State Level Tolerance (%) – how far into the amplitude a sample must be before it counts as having settled into a state. 2 by default, the value IEEE Std 181-2003 uses. Samples between the two boundaries belong to no state and are treated as part of a transition.
• Lower Percent Reference Level – the level a transition is timed FROM on a rising edge and TO on a falling one, as a percentage of the amplitude. 10 by default, as IEEE Std 181-2003 specifies.
• Upper Percent Reference Level – the other end of the same measurement: timed TO on a rising edge and FROM on a falling one. 90 by default. ⚠ These two also decide where a transition is DATED, because the mid reference level is their mean – the same rule MATLAB's transdurs applies, so an asymmetric pair such as 20/70 moves the transition instant to 45% rather than leaving it at 50%.
• Sampling Time (s) – 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.

Every threshold is structural and is inlined into the comparisons at export time rather than exposed as a tunable parameter – they follow from the state levels and the percentages, and the emitted core carries the numbers rather than the percentages. Re-export after changing any of them.

⚠ The three HDL targets are simulation-only. They carry this block's arithmetic in real rather than Q16.16, quantising only at the port boundary, for a reason specific to what it measures: an instant is a sample index plus a fraction, and a 16-bit integer part runs out after 32767 samples – five and a half minutes at a 10 ms rate. The comparisons and the interpolation are exact in real, which is what makes the exported core agree with the simulation; a synthesizable variant would have to carry the index some other way and is not what this block offers.

Simulink bridge

No equivalent (Support::None). Measured rather than assumed: a find_system sweep over 22 DSP System Toolbox and Simulink libraries on R2026a finds no block matching duty, pulse, rise, fall, slew, overshoot, settling or state level – the whole Pulse Metrics group is MATLAB functions with no Simulink counterpart. The bridge reports this block rather than dropping it silently, and it therefore has no parity testbench. Code export verification still covers it across all ten languages.

Notes

• Stateful, and discrete by nature (setDiscreteOnlyBlock(true)): the tracker advances once per sample.
• A measurement appears one sample after the transition that produced it, in the live run and in all ten exported languages alike. A hardware block cannot read back a value it computes in the same clocked interval, so publishing immediately would put the three HDL targets one sample behind the other seven on every edge; the delay is uniform instead, and deliberate.
• Crossing instants are interpolated between the two samples that straddle a reference level, exactly as IEEE Std 181-2003 Sec 5.3.3.2 specifies and MATLAB implements – so a measurement is not quantised to the sampling period.
• The output is 0 until the first measurement exists, and holds its last value between them. A run that never settles into both states produces no transitions and the output stays at 0.
• The state levels are PARAMETERS here, not estimated from the data. MATLAB's pulse-metric functions call statelevels to guess the two levels from a histogram of the WHOLE signal when you do not supply them; that is a batch operation over samples a streaming block has not seen yet. This block takes the levels the way those same functions do when you pass 'StateLevels' explicitly.
• Scalar only. One waveform and its own tracker; wire one block per channel.
• No state space. The block is not linear in its input – it is a sequence of comparisons – so it carries none and model reduction correctly declines to merge it.
• Falling transitions are ignored – they update the tracker but not the output. Use Fall Time for those, or Slew Rate for both.
• A transition inside one sample interval still has a duration. Both endpoints are interpolated within that interval, so a step that crosses the whole amplitude between two samples reports the fraction of the period the 10–90% span occupies rather than zero.