‘When Run clicked’ block starts a normal LiteWing Blockly program. Blocks connected below run from top to bottom when you select Run code. Think of it as the green flag for an autonomous mission, it tells the app where the main program begins.

Use one at the top of each flight program. You can arrange and store multiple programming block stacks in the same workspace at the same time.

By moving the blocks connected below When Run clicked, you can choose which programming block stack runs when you select Run code. This is useful when you want to keep several program ideas in one workspace but run only one at a time.

‘When key pressed’ block sets up an asynchronous keyboard teleoperation handler. When you press the configured key on your physical keyboard while the LiteWing Blockly window is active, the attached sub-routine runs immediately.

Unlike a normal top-to-bottom stack, a key-event stack waits for the chosen key instead of running once and ending. This makes it useful for interactive programs.

Arm drone block prepares the drone for flight. It tells the connected LiteWing controller that the program is about to use flight commands and gives the flight system a chance to confirm that it is ready for takeoff. An arming does not lift the drone or make it move by itself.

An Arm drone block must be used before a Takeoff block. Place it after any LED-ready indication or logging setup and immediately before the first takeoff in a basic program.

Takeoff block makes the drone take off. The LiteWing Drone rises to the selected height above the ground, using the Drone Positioning Module’s downward-facing height sensor as part of the height-hold system. A Takeoff block must be used after an Arm drone and before any flight movement.

Takeoff is an autonomous command, not a manual throttle control. After reaching the selected height, use Hover or another flight command to define what happens next.

Hover block makes the drone hold its current position for a chosen time. The Drone Positioning Module uses its height sensor and optical-flow sensor to help the drone maintain a stable hover.

During a hover, the height sensor measures distance to the ground while the optical-flow sensor measures movement across the floor texture. The flight controller uses these measurements to correct small height and position changes. A plain, dark, glossy, or poorly lit floor can reduce optical-flow accuracy.

This block changes the current hover height by a relative amount. It does not set an absolute height. For example, if LiteWing is hovering at 0.3 m, increasing height by 0.1 m requests a new height of about 0.4 m.

Use this block after takeoff while the drone is already in a stable hover. It is useful for simple step-up and step-down activities, but large changes are not recommended for a first indoor program.

Land block makes the drone descend in a controlled way and stop its motors after touchdown. Put a Land block at the end of every flight program.

Land is the normal way to finish a flight because it requests a controlled descent. It is different from Emergency Stop, which removes motor power immediately.

This block immediately cuts motor power. The drone will fall, so this block is only for an emergency such as an imminent collision, propeller entanglement, or loss of safe control.

Emergency Stop is deliberately different from a landing command. It prioritises stopping the propellers over maintaining altitude, which is why it should never be used as the usual last block of a flight program.

This block sets all four LEDs on the Drone Positioning Module to one RGB colour. It is useful for a safe connection test or for showing a program state, such as green for ready, blue for connected, or red for a warning.

RGB colour uses three light levels: red, green, and blue. A value of 0 turns that colour channel off and 255 gives its highest intensity. Combining channels creates other colours, such as yellow from red 255, green 255, and blue 0\.

This block sets one selected LED to an RGB colour. The LED index identifies one of the four LEDs on the Drone Positioning Module, allowing a program to create patterns instead of using a single all-LED colour.

This block makes all LEDs blink using the selected off and on times. The off time tells the app how long the LEDs stay dark, the on time tells it how long the LEDs stay illuminated.

This block turns all four LEDs off. Use it to finish a visual test cleanly or to remove a status colour after a program is complete.

Pitch forward block moves the drone forward along its longitudinal X-axis by the selected distance. “Forward” means the direction LiteWing is facing when the command runs, so a rotation changes the direction of a later forward command.

Pitch backward block moves the drone backward along its longitudinal X-axis by the given distance.

Roll left block moves the drone laterally to the left along its transverse Y-axis by the selected distance. Left and right are relative to the drone’s current heading, not to the person watching it from the side of the room.

Roll right block moves the drone laterally to the right along its transverse Y-axis by the selected distance. Plan enough space on both sides of the flight area before using this block.

This block rotates the drone counter-clockwise around its vertical axis. Rotation is also called yaw, it changes where the front of the drone points without asking it to travel forward or sideways.

This block rotates the drone clockwise around its vertical axis. Use modest angles such as 45 or 90 degrees while learning, then allow the drone to stabilise before the next movement.

This block makes the drone fly to a selected X and Y coordinate. You can add Z, rotation, and speed modifier blocks to the open parameter socket.

For example, X 0.5 and Y 0.0 asks LiteWing to fly about half a metre forward from the launch point. X 0.0 and Y 0.3 asks it to move about 0.3 m left. The block can be used repeatedly to build a route one target at a time.

This block makes the drone visit a sequence of waypoint blocks. Place waypoint blocks inside its waypoints area and optionally attach a speed value.

The waypoint stack is read from top to bottom. Each waypoint becomes one coordinate in the generated Python path list, so the order of the blocks is the order in which LiteWing visits the locations.

This block defines X and Y points inside a Fly path block. It can accept Z and rotation modifiers. It is not a free-standing flight command, it only belongs inside the waypoint area of a Fly path block.

This block makes the drone fly a square path. The specified length determines the distance of each side of the square. It generates and executes a four-sided trajectory, returning the drone to its original hover position after completing the pattern.

This block enables the drone to fly an equilateral triangle path. The specified length determines the distance of each equal side. It generates and executes a precise three-sided trajectory with 60° interior turns, returning the drone to its original hover position after completing the pattern.

This block directs the drone along a smooth circular trajectory. Set the diameter in meters to determine the circle’s overall width, and ensure there is enough open space for the drone to complete the maneuver safely.

This block makes the drone fly in a regular pentagon pattern. The Length value specifies the length of each side, allowing the drone to trace a five-sided polygon with equal-length sides.

This value block chooses whether the drone should point in its direction of travel during a shape path. Select True when the flight path should guide the drone’s heading and False when it does not need that behaviour.

This reporter block reads the current battery voltage. It is an important safety value because a low 1S LiPo battery can reduce flight performance and should be charged before flight.

Parameters: none.

This reporter block reads the current estimated height in metres. The value is based on the available position module height sensing and is especially useful for observing a hover or explaining how a condition can use real sensor data.

Parameters: none.

This reporter block reads the estimated X and Y position relative to the launch point. The values are estimates, not a GPS location, and they depend on optical-flow tracking over a textured, well-lit surface.

Parameters: none.

This block prints a selected telemetry value in the console. It is the simplest way to see a live value while testing a connection, a sensor, or a short flight program.

Parameters: Battery, Height, Position, or Velocity.

This block starts recording available telemetry data into a CSV file. A CSV file can be opened later in a spreadsheet or data-analysis program.

Telemetry logging is useful for capturing flight data that can be reviewed after the flight. Start logging before the commands or flight sequence you want to analyze, and stop logging after the drone has landed.

Parameters: Battery, Height, Position, or Velocity.

This block stops recording and closes the current CSV file. Always use it after Start logging so the recorded file is finished correctly and can be opened later.

Parameters: Battery, Height, Position, or Velocity.

This value block supplies a movement or navigation speed. It does not run by itself, snap it into a compatible speed socket. A lower speed gives the flight controller more time to correct its position.

This value block supplies a time to Takeoff, Land, or a shape command. It does not run by itself, snap it into the compatible input socket. With a shape block, duration controls the intended time for completing that path.

When Debug mode is on, the program can be tested while keeping the propellers inactive.

Debug mode is useful for checking block order, delays, console output, LED sequences, and sensor logic. It is not a flight simulator, It helps verify the program flow.

This block pauses the program for a selected number of seconds. It is useful when a program needs to leave time between visible actions, such as changing an LED colour or fetching sensor value and clearing it later.

Parameters: 0.1 s to 60 s in 0.1-second steps.

This block prints a text message or compatible value in the console. Print is useful for making a program explain what it is doing, for example Starting LED test, Taking off, or Flight complete.