Growing capabilities · Private owner development preview

Larry's Connected UI & I/O

Describe the behaviour. Larry builds the interface and connects the signals.

Larry now goes beyond arranging widgets. Describe how controls, measurements and alarms should behave, review the proposed connections in Studio, and run the result in ForgeUI's real LVGL simulator.

01 / Describe behaviour

02 / Review connections

03 / Test in real LVGL Sim

These demonstrations run generated C in real LVGL WebAssembly Sim. Runtime Controls inject simulated measurements and digital feedback. Physical I/O has not been proven by these recordings.

01 / Connect controls

Make the interface respond.

Start with Switch → LED or Slider → Bar. Keep several channels independent, or let one numeric control drive Bar, Progress and CircularProgress together. Direct connections are owner-tested in Sim; the fan-out recording shows the shared response.

One control, three displaysWatch Bar, Progress and CircularProgress follow the same Slider. These are linked UI values in real LVGL Sim.Open recording for a closer look

Inspect the independent-channel design

Three switches paired with LED indicators, with a Volume Slider and Bar below — A design capture of separate control paths. Select the image to inspect it; the owner reports successful Sim tests.

02 / Transform signals

Give values useful meaning.

Scale a 0–100 control into RPM or a 0–24 V display. Show exact numeric values with units and decimal precision. Add a threshold, retain state with high hysteresis, or invert a Boolean state or numeric range.

Threshold: A numeric value drives an LED across one boundary; Sim pass.
High hysteresis: Separate activation and clearing thresholds hold state between them; Sim pass.
Scaling & readouts: Scaling is owner-reported working; live SensorTile values, units and decimals work in Sim.
Inversion: Boolean opposite and reversed numeric range; Sim and save/reopen confirmed.

A value you can readThe SensorTile’s numeric value follows the Slider alongside the Bar. Numeric readouts support units and decimal precision; this example displays a percentage.Open recording for a closer look

Units such as V, A, Hz and RPM describe values; they do not prove physical acquisition. Commanded RPM is not measured motor speed. Watch the existing threshold, hysteresis and scaling examples.

03 / Separate command from feedback

What you ask for.
What comes back.

Named signals keep command and feedback distinct. A voltage command can drive a mirror display, while a separate analogue measurement comes from Runtime Controls. Moving the command must not masquerade as a measured change.

Command path

Slider → named command → command display

Feedback path

Runtime Control → simulated measurement → measured display

Command and measurement stay independentMove the command Slider, then inject a separate measured voltage through Runtime Controls. The measurement does not simply mirror the command. Both paths are simulated.Open recording for a closer look

Digital feedback works the same way: inject 0 or 1 to drive an LED directly or inverted, such as opposite door-open and door-closed indicators. Independent analogue feedback and digital feedback/inversion have Sim and save/reopen confirmation. Named voltage command and mirror behaviour has been tested.

04 / Build useful alarm logic

Turn disagreement into a visible state.

A relay command and its actual feedback are separate paths. Compare them to flag a mismatch, require continuous disagreement before alarming, or latch the alarm until a safe reset. The owner tested all four command/actual truth-table states for the basic mismatch alarm.

Notice when command and actual disagreeThe switch changes the relay command; Runtime Controls supplies independent digital feedback. Watch the mismatch LED respond to disagreement. ‘Actual’ here means injected Sim feedback, not a physical relay.Open recording for a closer look

Add a delay: alarm only after continuous disagreement

Wait for continuous disagreementWatch the alarm appear after command and feedback remain different. The owner reports successful delayed-mismatch tests in Sim; this is not a firmware-export qualification.Open recording for a closer look

Latch and reset: retain the alarm after the mismatch clears

Remember the fault until resetWatch the alarm remain after command and feedback match, then clear with Reset when safe. The owner reports successful tests in Sim; hardware protection is not demonstrated.Open recording for a closer look

Low-hysteresis and delayed/latched alarm paths include Sim-only support unless firmware export has separately been qualified. These examples do not establish physical relay operation, electrical protection or closed-loop hardware control.

05 / From Sim toward physical I/O

Test behaviour now.
Qualify the hardware path next.

Runtime Controls currently supply simulated measurements and feedback. Board-qualified GPIO, ADC and PWM adapters are the next chapter: later, named signals can be mapped to qualified physical hardware integration. The demonstrations on this page do not prove that integration today.

Larry proposes the design and connections. Studio validates supported contracts and generates runtime behaviour. Connections are supported combinations, not universal wiring between every widget. Browser Sim does not execute arbitrary user C. Layout precision can still be refined manually in Studio.

Design with Larry

An idea you can review, run and refine.

01Describe the interface and behaviour to Larry.
02Review Larry’s proposed widgets and connections.
03Apply the draft in Studio.
04Run the generated interface in real LVGL Sim.
05Test measurements and feedback with Runtime Controls.
06Save, reopen and continue refining.
07Later, map named signals to qualified physical hardware adapters.

Larry remains ForgeUI's Creative UI Manager, in private owner development. This Design with Larry workflow is distinct from Create UI with Larry.

Explore Larry's design approach →