Led Output
This function block provides a simple visual indicator for boolean signals. Use it to quickly check whether a condition in your scenario is TRUE, FALSE, or undefined.
π₯ Inputs
Boolean This input socket accepts a boolean signal to drive the LED indicator. Connect any logic or condition output here.
π€ Outputs
This function block does not have outputs.
πΉοΈ Controls
led Visual LED indicator shown on the block:
Gray β input is undefined / None.
Green β input is TRUE.
Red β input is FALSE.
π¨ Features
Real-time visual feedback for boolean signals.
Clear color coding for three states: undefined, TRUE, and FALSE.
Lightweight and suitable for dashboards or quick debugging.
π Usage Instructions
Provide a boolean signal to the
Booleaninput.Observe the
ledcolor to understand current state:Green for TRUE
Red for FALSE
Gray when no value is present
Use this block on UI screens where immediate visual feedback is helpful.
π Evaluation
When the scenario runs, the block checks the boolean value arriving at the Boolean socket and updates the led color accordingly. If no value is present, the indicator shows the undefined state.
π‘ Tips and Tricks
For manual testing, connect a
Logic Inputto theBooleansocket so an operator can toggle the LED on the fly.Combine condition checks before the LED using logic blocks such as
And,Or, andNotto visualize combined conditions.Use comparison blocks like
Equals,Greater, orSmallerto convert numeric measurements into boolean signals for the LED.Use edge detectors such as
Rising EdgeorEdge Risingto show event pulses instead of continuous states.Add temporal behavior with
Delay Step,ON Delay, orOFF Delayif you want the LED to respond only after a sustained condition.Use
Set - Resetto latch a condition and keep the LED on until explicitly reset.Integrate with data or communication blocks upstream (for example, use
Data Write Local/Data Write GlobalorMQTT Publishon the logic feeding this block) to reflect remote or network-driven states locally.
π οΈ Troubleshooting
LED stays gray: Check that the previous block is producing a boolean value. Consider using
Is Noneor a simpleLogic Inputto test the path.LED always red/green but condition seems wrong: Verify the upstream logic (comparisons, merges) with intermediate indicators or debug blocks before connecting to the LED.
Need persistent indicator for transient events: Use
Set - Resetor an edge-to-latch pattern so a short pulse becomes a sustained visual state.
Last updated
Was this helpful?