Climb Rate Indicator — Robotics/Flight Instruments
Robotics/Flight_Instruments/Climb_Rate_Indicator · 0 input / 0 output port(s) at insert · exports to Python, MATLAB, Java, Rust, C, C++, VHDL, Verilog, SystemVerilog, PLC Structured Text
Description#
The block's own DESCRIPTION_HTML, rendered verbatim — the same text the config dialog's info panel and the library navigator show. Fix a wrong sentence in the block's .cpp (R-D9), never here.
Climb Rate Indicator
Robotics / Flight Instruments
A vertical-speed dial. It shows the value of a signal it is told the name of as a needle turned 180·value/Maximum Rate degrees from 0 at nine o'clock – clockwise over the top for a climb, counter-clockwise under the bottom for a descent – and stopped at ±180°, where both halves meet at three o'clock. It has no ports at all.
Ports
- None. Not one input, not one output: the dial reads the signal it is bound to by name, as Simulink's binds to the one selected on its canvas.
Parameters
- Signal – the name of the link to read, for example
climb_rate, or its full path when the name contains/. Matching runs over this block's own subsystem and everything below it. It names a link, not a variable, so it is never looked up in the variables space. A name that matches no link is reported when the run starts, and the dial then shows no value. Only the first entry of the signal is read. - Maximum Rate – the rate at either end of the scale, default
4000as on Simulink's block. The needle turns 180·value/Maximum Rate degrees from nine o'clock – clockwise over the top for a climb, under the bottom for a descent – and stops at ±180°. The labels read in thousands: 0, then a quarter of the maximum per 45° on each half. It must be above zero. - Refresh Period (s) – how often the dial is repainted, in wall-clock seconds, so a fast run does not turn the face into a blur. Zero or less repaints on every sample; the final sample of a run is always shown.
- Sampling Time (s) – how often the value is read. Zero or less inherits the solver's rate.
Notes
- The value is one sample behind. A block with no inputs has no input dependency, so it runs at the head of every step and reads what its source published on the previous one.
- Stateless: it draws, and computes nothing a later step reads.
Code export
All ten targets: Python, MATLAB, Java, Rust, C, C++, VHDL, Verilog, SystemVerilog and PLC Structured Text. A deployable target has no dial, so each one prints the bound VALUE, as it arrives (the ±180° stop is the dial's). PLC Structured Text emits comments only, naming the signal array entry to tap. The one-sample shift applies to the exported code too.
Code-export verification
This block is excluded from the code-export verification matrix, by name: the verifier records a terminal block's input signals, and a block with no inputs records nothing, so a rig around it would fail all ten languages at residual 0 and say nothing about the block.
Simulink bridge
None, and that is a measurement. Simulink's Climb Rate Indicator
(aerolibhmi/Climb Rate Indicator, BlockType=ClimbIndicatorBlock) has ZERO ports of any kind
and no SampleTime, measured on R2026a; it reaches its signal through
Binding, a canvas selection stored outside the block's parameters, and ICore has
no counterpart for that. This block is the ICore reading of it – the signal is named
rather than clicked – so it is reported on exchange rather than mapped.
Code facts#
| Fact | Value |
|---|---|
| registered type | Robotics/Flight_Instruments/Climb_Rate_Indicator |
| family | Robotics/Flight_Instruments |
| solver environment class | ICoreBlock_0_Robotics_1_Flight_Instruments_2_Climb_Rate_Indicator |
| source | src/ICoreBlocks/ICoreBlockLibrary/Blocks/Robotics/Flight_Instruments/Climb_Rate_Indicator/ICoreBlock_0_Robotics_1_Flight_Instruments_2_Climb_Rate_Indicator.cpp |
| header | src/ICoreBlocks/ICoreBlockLibrary/Blocks/Robotics/Flight_Instruments/Climb_Rate_Indicator/ICoreBlock_0_Robotics_1_Flight_Instruments_2_Climb_Rate_Indicator.h |
| ports at insert | 0 in, 0 out |
| code generators implemented | Python, MATLAB, Java, Rust, C, C++, VHDL, Verilog, SystemVerilog, PLC Structured Text |
Ports#
The constructor creates no port explicitly — the port list comes from registerInitialPorts (0 in, 0 out) or from the block's configuration.
Configuration variables#
| Config variable | Default | Simulink parameter |
|---|---|---|
Signal | — | — |
Maximum Rate | 4000 | — |
Refresh Period (s) | 0.1 | — |
Every block also carries Sampling Time (s) from ICoreBlockSolverEnvironment: zero or less inherits the solver's rate, a positive value runs the block at that period.
Simulink bridge#
| support | Support::None |
| Simulink path | — |
| port-count rule | PortsParam::None |
SampleTime parameter | yes |
Caveat (shown to the user): Simulink's Climb Rate Indicator (aerolibhmi, BlockType=ClimbIndicatorBlock) has ZERO ports of any kind and no SampleTime - measured on R2026a. It does not receive its value on a wire: it reaches the signal through Binding, a canvas selection stored outside the block's parameters, and ICore has no counterpart for that. This block is the ICore reading of that dial - the signal is named rather than clicked - so it is reported on exchange rather than asserted
Catalog contract: src/ICoreBlocks/ICoreCoder/ICoreCommandSystem/SimulinkBridge/ICoreSimulinkBlockCatalog.h
Description vs code#
The checker has a blind spot here — it could not resolve something (a grouped port bullet, a computed config name), which is reported and never counted as a pass. A reader has to settle it:
B0no sample under docs/generated/samples/ — nothing to cross-check (P8.1)
The verdict above is
tools/docs/check_block_descriptions.py(P7.1), which compares LISTS. It cannot read a sentence: "stateless" on a block with a state, an initial-value semantic the recursion does not implement, a "not synthesizable" caveat the HDL banner contradicts. That is the agent audit (P7.3) on BLOCK_DESCRIPTION_AUDIT.md, and this tool's green is not a substitute for one.
File banner (developer view)#
The top comment of the block's .cpp — the maths, the realization and the export strategy, addressed to whoever changes it. It must not contradict the description above (P7.5).
Climb Rate Indicator -- a vertical-speed dial bound to a signal by name The Aerospace Blockset's Flight Instruments/Climb Rate Indicator, measured on R2026a (BlockType=ClimbIndicatorBlock): ZERO ports, no SampleTime, one parameter, MaximumRate, default 4000. Read from the component that draws it: the needle angle is 180 * v / max degrees, clamped to +/-180, from nine o'clock -- a climb turns it over the top, a descent under the bottom. The labels are in thousands: 0 at nine o'clock, a quarter of the maximum per 45 degrees, mirrored into the descent half, and the maximum at three o'clock; a label that is not a whole number prints the Simulink faces' decimals, so a 2000 dial reads 0.50, 1 and 1.50.
Sample results#
No sample run is committed for this block. Samples come from the headless harness (DOCS_PLAN.md P8.1) into docs/generated/samples/; until one exists this block's behaviour is witnessed by the parity and export-verification suites, not by a plot here.