Skip to content

Releases

koebelt dash 1.4.0

Choose a tag to compare

@github-actions github-actions released this 09 Nov 19:21

koebelt dash now speaks your language and your units, and knows more machines: planes, boats, legged robots, two-wheeled balancing robots and humanoids, each with its own 3D shape.

Languages

  • Seven languages. English, French, Spanish, German, Brazilian Portuguese, Japanese and Simplified Chinese, guides included. Settings > Language follows the system, or picks one.
  • Made with AI. Every translation but English was made with AI and may contain mistakes; a note in Settings and Guides says so and links to this repository, where corrections are welcome.
  • Traditional Chinese. A system in Traditional Chinese is asked once, at first launch, whether to use Simplified Chinese, English or another language.

Units

  • Metric or imperial. Settings > Units shows lengths in feet, speeds in mph and temperatures in °F, or follows the region (imperial in the US). Readouts, charts, alerts, sequences, the map and the 3D view all follow; devices, scripts and recordings keep metres.

More machines

  • Planes. A fixed-wing plane takes off, flies a circuit through waypoints, circles while it holds and lands in a glide. Try the simulated one, Swift.
  • Boats. Driven like a ground robot, drifting with the current. Try Otter.
  • Legged robots. Quadrupeds, hexapods and humanoids walk forward, sideways and turning at once: the right stick walks, the left one turns and sets the body height. Stand and sit, walk and trot from Control; sequences walk to waypoints. Try Scout (a quadruped) and Ada (a humanoid).
  • Two-wheeled balancing robots. A ground robot that leans into what it does. Try Wobble.
  • Shapes. The 3D view draws what your machine looks like: a quad, hexa, octo or helicopter; a trainer, flying wing or VTOL plane; a 4WD, car, tracked or balancing rover; a hull or a catamaran; a quadruped, hexapod or humanoid. Devices declare it, ArduPilot and PX4 vehicles get it from their frame type, and Devices > Shape picks it for firmware that does not say.
  • ArduPilot and PX4. Planes, quadplanes and boats connect as such, and ArduPlane and PX4 fixed-wing logs open as planes.

koebelt/link 1.2.0

  • The Arduino, Python and Rust libraries and the ROS 2 bridge declare planes, boats and legged robots, and their shape, and run their stored sequences.
  • MicroPython. A new library for an ESP32 or a Raspberry Pi Pico W, over Wi-Fi, USB, a UART, a radio or a Bluetooth serial module: mpremote mip install github:koebelt/koebelt_dash/libs/micropython. Guides > Quickstart > MicroPython.
  • New device guide: Legged robot, with a complete program for Arduino, Python and MicroPython.

Also

  • Linux on ARM64 (Raspberry Pi 5, Jetson, ARM laptops), next to x64; updates pick the right one. Chinese and Japanese use the system's CJK font: install.sh says when to add fonts-noto-cjk.
  • Phones: four tabs. Live, Control, Automate and More; More opens Tune, Replay, Devices, Guides and Settings.
  • The 3D view shows the ground as far as the camera sees, its lines fading with distance; simulated planes bank into their turns.
  • Long words in every language fit: buttons, tabs, readouts and the top bar, at every screen size.
  • koebelt-dash-scripts 1.4.0 is on PyPI.

Updating

From 1.1.0 or later, use the Update button in the app. From 1.0.0, install this version by hand once.

macOS 12 or later koebelt-dash-1.4.0-macos.dmg
Windows 10 or later (x64) koebelt-dash-1.4.0-windows-x64-setup.exe (not code-signed yet: if SmartScreen stops it, choose More info, then Run anyway)
Linux (x64) koebelt-dash-1.4.0-linux-x64.tar.gz
Linux (ARM64) koebelt-dash-1.4.0-linux-arm64.tar.gz
Android 7 or later koebelt-dash-1.4.0-android.apk
iPhone and iPad the App Store

koebelt dash 1.4.0-beta.2

Pre-release

Choose a tag to compare

@github-actions github-actions released this 09 Nov 00:06

The second beta of 1.4: two more kinds of robot, a shape for every machine, and a simpler tab bar on phones.

Robots

  • Two-wheeled balancing robots. A ground robot shape that leans into what it does: forward to speed up, back to brake. Try the simulated one, Wobble.
  • Humanoids. A legged robot shape on two legs, with knees and elbows: it walks, steps sideways, turns, crouches with the height stick, and stands or sits. Try the simulated one, Ada.
  • Pick a shape. Devices > Shape chooses what the 3D view draws for a device whose firmware does not say (a hexacopter, a tracked rover, a catamaran, a humanoid…). Auto keeps the one it declares.

Guides

  • Legged robot. A new device example: the sticks and commands, standing and sitting, gaits, and a complete program for Arduino, Python and MicroPython. In every language.

Phones

  • Four tabs. Live, Control, Automate and More; More opens Tune, Replay, Devices, Guides and Settings.

Fixes

  • The top bar keeps STOP and its controls in view with two devices and an alert, in every language, and its link, battery and status sit centred.

koebelt dash 1.4.0-beta.1

Pre-release

Choose a tag to compare

@github-actions github-actions released this 03 Nov 12:47

The first beta of 1.4: koebelt dash in your language, in your units, for more machines and more boards.

Languages

  • Seven languages. English, French, Spanish, German, Brazilian Portuguese, Japanese and Simplified Chinese, guides included. Settings > Language follows the system, or picks one.
  • Made with AI. Every translation but English was made with AI and may contain mistakes; a note in Settings and Guides says so and links to the repository, where corrections are welcome.
  • Traditional Chinese. A system in Traditional Chinese is asked once, at first launch, whether to use Simplified Chinese, English or another language.

Units

  • Metric or imperial. Settings > Units shows lengths in feet, speeds in mph and temperatures in °F, or follows the region (imperial in the US). Readouts, charts, alerts, sequences, the map and the 3D view all follow; devices, scripts and recordings keep metres.

Planes and boats

  • Two new device kinds. A fixed-wing plane takes off, flies a circuit through waypoints, circles while it holds and lands in a glide; a boat is driven like a ground robot and drifts with the current. Both have their own 3D model, dashboard and sequences, and a simulated one to try (Swift and Otter).
  • ArduPilot and PX4. Planes, quadplanes and boats connect as such, and ArduPlane and PX4 fixed-wing logs open as planes.
  • koebelt/link. The Arduino, Python and Rust libraries declare planes and boats (KLink::PLANE, kind="boat", Kind::Plane), and run their stored sequences.

Legged robots and body shapes

  • Legged robots. Quadrupeds and hexapods walk forward, sideways and turning at once: the right stick walks, the left one turns and sets the body height. Stand and sit, walk and trot from Control; sequences walk to waypoints. A simulated one (Scout) stands up when armed.
  • Body shapes. The 3D view draws what your machine looks like: a quad, hexa, octo or helicopter; a trainer, flying wing or VTOL plane; a 4WD, car or tracked rover; a hull or a catamaran; a quadruped or a hexapod. ArduPilot and PX4 vehicles get theirs from their frame type; koebelt/link devices declare it (body="hexa", setBody("car"), .body("tracked")).

3D view

  • The ground grid reaches as far as the camera sees, and its lines fade in and out with distance instead of popping.
  • Simulated planes bank into their turns, and drones lean into their slide.

MicroPython

  • koebelt/link for MicroPython. One file for an ESP32 or a Raspberry Pi Pico W, over Wi-Fi, USB, a UART, a radio or a Bluetooth serial module: mpremote mip install github:koebelt/koebelt_dash/libs/micropython. Guides > Quickstart > MicroPython, and a complete ground robot in the device examples.

Linux

  • ARM64. A Linux build for ARM64 (Raspberry Pi 5, Jetson, ARM laptops), next to the x64 one; updates pick the right one.
  • Chinese and Japanese use the system's CJK font: install.sh says when to add fonts-noto-cjk.

Fixes

  • Many layouts checked at every screen size and in every language: long words no longer overflow buttons, tabs and readouts.

koebelt dash 1.3.0

Choose a tag to compare

@github-actions github-actions released this 02 Nov 16:45

koebelt dash now runs your Python scripts, with any package you like, and lets AI assistants help you, with the operator always in charge.

Automate

  • Two ways to automate a device. Program becomes Automate: a page that presents Sequences (steps in order, no code, run on the device) and Scripts (Python) side by side, with a guide, Sequence or script?, that compares them. On desktops the sidebar lists both; a pulsing dot marks the one that runs.
  • Sequences, by name. What was called a program is a sequence everywhere: scripts call dev.run_sequence("Survey square") (the *_program names still work), and assistants run_sequence.

Scripts

  • Drive a device from Python. Automate > Scripts holds your scripts: create one from a template, import a .py or a .zip with its files, start from eight examples, edit in the built-in editor, check it, and run it on any connected device, simulated ones included. The screen opens the script you had open.
  • Any Python package. Scripts run in your own Python, so OpenCV, PyTorch and YOLO work: the camera arrives as NumPy images, newest first, and dev.overlay() draws what your model sees over the camera in dash. The first time, Set up Python prepares an environment with the koebelt-dash-scripts package. A script that imports something its Python lacks offers to install it.
  • An editor that knows your code. Completion for the API, your own names, the device's sticks, telemetry and sequences, the libraries you import (np., cv2.) and file paths; parameter hints as you type; details when you hover a name.
  • Check before it moves. Check finds syntax errors, missing imports, names that are not defined (pritn) and calls the device does not have, each underlined on its line; Run checks first.
  • Pictures and charts in Live. dev.show("tracking", frame) puts a picture in the Live view (a camera frame with what the script found drawn on it, a mask, a matplotlib figure), dev.chart() a line, bar or scatter chart, and dev.plot() several series. They are recorded, and Replay shows them at their time.
  • A console that reads at a glance. Errors in red, warnings in amber, info: lines in blue, debug: lines in grey (or Python's logging).
  • Steps and sequences. Scripts take off, fly or drive to points, land, move arms and run your sequences, each returning once done. # requires: drone, gps, camera limits a script to the devices that fit.
  • Triggers. Fire a script's events from a button or a switch (also on Control, next to the sticks), a key, a controller button, a condition (battery.pct < 25 for 3s), a device event or a timer.
  • You stay in charge. STOP ends every script. Moving the sticks takes over until you resume. Each script has limits you set (speed, geofence, ceiling; no arming or parameter writes unless allowed). If a script crashes, hangs or leaves its geofence, the device holds and the script waits for you. A script runs only with a device connected.
  • Phones and tablets run scripts on a script host: any computer on the same network running koebelt-dash-scripts host, paired once with a code. The phone keeps the device link, the sticks and STOP.
  • Vision without hardware. The cameras of simulated drones and rovers show a yellow ball and a person walking near home: the Colour tracker and Follow a person examples work on them as they are.
  • Errors that explain themselves: what went wrong, the line of your script, why, how to fix it, and the name you meant (koebelt-dash-scripts ERRORS.md).

Modes

  • A device connects disarmed in HOLD (simulated ones too: the drone waits on the ground). Arming hands it to you in MANUAL. AUTO is dash's: only while a sequence or a script drives the device, and it goes back to HOLD when that ends. MAVLink vehicles keep their own modes.
  • The mode control is MANUAL | HOLD | AUTO, with AUTO lit and naming what drives; choosing a mode or moving the sticks takes over. Live has it in its bar, and choosing MANUAL there opens Control.

Proximity sensors

  • Ultrasonic, infrared and time-of-flight sensors show on Live from above, a wedge each, coloured by how close; the Obstacle close alert warns while armed. Scripts read them with dev.proximity(), and conditions with prox.front or prox.nearest. Devices declare them with koebelt/link 1.1.0 (Arduino, Python, Rust, ROS 2); the simulated rover and drone have some.

AI assistants

  • Turn on Settings > AI assistants to let Claude, Cursor, Codex, OpenCode or another MCP client read the guides, look at your devices and recordings, write, check and test scripts on simulated devices, and use the app.
  • On real hardware, every action an assistant takes waits for your approval on a card in dash. You can allow a kind of action for the session; arming and take-off always ask. STOP never asks, and safety settings stay out of reach.
  • koebelt dash sends nothing to any AI service itself.

Every screen size

  • Small phones, phones held sideways, tablets upright, small windows and ultrawide monitors: nothing overflows or overlaps, also with large system text and several devices connected. A tablet held upright gets its own Live layout; in a short window the sidebar scrolls; Replay scrolls on a short screen.

Also

  • Maps from Mapbox. Dark, Outdoors and Satellite maps replace OpenStreetMap's servers. You can use your own Mapbox token in Settings > Map.
  • New guides: Scripts, AI assistants, and Sequence or script?
  • Settings on a wide screen lists its sections beside them: click one to jump there.
  • The chase view stays behind the drone as it yaws.
  • Tilt control no longer reports errors on a computer, where there is no accelerometer.
  • koebelt-dash-scripts 1.3.0 is on PyPI: pip install koebelt-dash-scripts (dash's Set up Python installs it by itself).

Updating

From 1.1.0 or later, use the Update button in the app. From 1.0.0, install this version by hand once.

macOS 12 or later koebelt-dash-1.3.0-macos.dmg
Windows 10 or later (x64) koebelt-dash-1.3.0-windows-x64-setup.exe (not code-signed yet: if SmartScreen stops it, choose More info, then Run anyway)
Linux (x64) koebelt-dash-1.3.0-linux-x64.tar.gz
Android 7 or later koebelt-dash-1.3.0-android.apk

koebelt dash 1.3.0-rc.1

Pre-release

Choose a tag to compare

@github-actions github-actions released this 28 Oct 13:49

Release candidate. koebelt dash 1.3 as it should ship: scripts and AI assistants. It is offered only to apps with Settings > Updates > Betas on; please report problems on GitHub before the final 1.3.0.

koebelt dash now runs your Python scripts, with any package you like, and lets AI assistants help you, with the operator always in charge.

New in RC 1

  • Every screen fits every screen. Small phones, phones held sideways, tablets upright, small windows and ultrawide monitors: nothing overflows or overlaps any more, also with large system text and several devices connected.
    • On a small phone, Control keeps its buttons in one row that scrolls sideways and the readouts on one line; Live's view switches scroll; the device list puts its buttons under the name.
    • A tablet held upright gets its own Live layout, with the tiles across the width, and Control shows the readouts between the sticks again.
    • In a short window the sidebar scrolls; in a narrow one the top bar uses its compact parts, and the link, latency and battery figures leave out whole items rather than cutting one in half.
    • Replay scrolls on a short screen instead of squashing the player; short tiles and charts keep their numbers readable.
  • Tilt control no longer reports errors on a computer, where there is no accelerometer: the pad is dragged with the mouse there.

New in beta.5

  • Modes, simpler. A device connects disarmed in HOLD (simulated ones too: the drone waits on the ground). Arming hands it to you in MANUAL. AUTO is dash's: only while a sequence or a script drives the device, and it goes back to HOLD when that ends. The mode control is MANUAL | HOLD | AUTO, with AUTO lit and naming what drives; choosing a mode or moving the sticks takes over. Scripts no longer switch to MANUAL themselves: arm the device, and dash drives it in AUTO for them.
  • The mode on Live. Live has the mode control in its bar (on phones, the badge at the top lights up in AUTO); choosing MANUAL there opens Control, where the sticks are.
  • Proximity sensors. Ultrasonic, infrared and time-of-flight sensors show on Live from above, a wedge each, coloured by how close; the Obstacle close alert warns while armed. Scripts read them with dev.proximity(), and conditions with prox.front or prox.nearest. Devices declare them with koebelt/link 1.1.0 (Arduino, Python, Rust, ROS 2); the simulated rover and drone have some.
  • What runs shows. A pulsing dot marks Sequences and Scripts (and Automate) while one runs, and Automate's cards say what.
  • A console that reads at a glance. Errors in red, warnings in amber, info: lines in blue, debug: lines in grey (or Python's logging); tracebacks and the library's errors colour themselves.
  • Follow a person turns towards the person (it turned away), and both vision examples say what they see and do in the console.
  • The Scripts screen opens the script you had open; the examples fold away once you have scripts of your own.

New in beta.4

  • Automate. Program becomes Automate: a page that presents the two ways to automate a device side by side, Sequences (steps in order, no code, on the device) and Scripts (Python), with a guide, Sequence or script?, that compares them. On desktops the sidebar always lists both.
  • Sequences, by name. What was called a program is a sequence everywhere: scripts call dev.run_sequence("Survey square") (the *_program names still work), and assistants run_sequence.
  • Pictures and charts in Live. dev.show("tracking", frame) puts a picture in the Live view (a camera frame with what the script found drawn on it, a mask, a matplotlib figure), dev.chart() a line, bar or scatter chart, and dev.plot() takes several series. Each is a widget: on the wall at once, on the HUD in a free spot.
  • An editor that knows your code. Completion for the API, your own names, the device's sticks, telemetry and sequences, the libraries you import (np., cv2.) and file paths; parameter hints as you type; details when you hover a name, with the whole docstring of a library function.
  • Recorded, and replayed. What scripts show is kept with the recording: Replay shows the pictures and charts at their time, next to the telemetry.
  • Vision without hardware. The cameras of simulated drones and rovers show a yellow ball rolling near home and a person in red walking round it: the Colour tracker example follows the ball on a simulated rover as is.
  • Check, for real. Check now finds what would stop a script before it moves anything: syntax, imports this Python lacks (with the pip install to run), names that are not defined (pritn), and calls the device does not have or with the wrong arguments. Each problem is underlined on its line, and Run checks first: with errors, it asks before starting.
  • Missing packages. A script that imports something its Python lacks offers to install it, on its page and when you press Run.
  • What a script needs. # requires: drone, gps, camera limits a script to the devices that fit: the others are marked in its device menu, and Run says what they lack.
  • No device, no run. Run waits until a device is connected (or the one chosen for the script is).
  • Maps from Mapbox. Dark, Outdoors and Satellite maps replace OpenStreetMap's servers. You can use your own Mapbox token in Settings > Map.
  • Installing or updating koebelt-dash-scripts says how it went, and stays a few seconds.
  • The scripts folder link opens the folder (it tried to open it in a text editor on macOS).

Scripts

  • Drive a device from Python. Automate > Scripts holds your scripts: create one from a template, import a .py or a .zip with its files, start from eight examples, edit in the built-in editor, check it, and run it on any connected device, simulated ones included.
  • Any Python package. Scripts run in your own Python, so OpenCV, PyTorch and YOLO work: the camera arrives as NumPy images, newest first, and dev.overlay() draws what your model sees over the camera in dash. The first time, Set up Python prepares an environment with the koebelt-dash-scripts package.
  • Steps and sequences. Scripts take off, fly or drive to points, land, move arms and run your sequences, each returning once done.
  • Triggers. Fire a script's events from a button or a switch (also on Control, next to the sticks), a key, a controller button, a condition (battery.pct < 25 for 3s), a device event or a timer.
  • You stay in charge. STOP ends every script. Moving the sticks takes over until you resume. Each script has limits you set (speed, geofence, ceiling; no arming or parameter writes unless allowed). If a script crashes, hangs or leaves its geofence, the device holds and the script waits for you.
  • Phones and tablets run scripts on a script host: any computer on the same network running koebelt-dash-scripts host, paired once with a code. The phone keeps the device link, the sticks and STOP.
  • Errors that explain themselves: what went wrong, the line of your script, why, how to fix it, and the name you meant (koebelt-dash-scripts ERRORS.md).

AI assistants

  • Turn on Settings > AI assistants to let Claude, Cursor, Codex, OpenCode or another MCP client read the guides, look at your devices and recordings, write, check and test scripts on simulated devices, and use the app.
  • On real hardware, every action an assistant takes waits for your approval on a card in dash. You can allow a kind of action for the session; arming and take-off always ask. STOP never asks, and safety settings stay out of reach.
  • koebelt dash sends nothing to any AI service itself.

Also

  • New guides: Scripts, AI assistants, and Sequence or script?
  • Settings on a wide screen lists its sections beside them: click one to jump there.
  • The script panel shows the koebelt-dash-scripts version in each Python and offers updates; choosing a Python checks it again.
  • The chase view stays behind the drone as it yaws.
  • koebelt-dash-scripts 1.3.0rc1 is on PyPI: pip install --pre koebelt-dash-scripts (dash's Set up Python installs it by itself). show(), chart(), run_sequence() and proximity() need it.

Updating

From 1.1.0 or later: turn on Settings > Updates > Betas, then use the Update button, or choose it in Settings > Updates > Versions. From 1.0.0, install this version by hand once. The final 1.3.0 will be offered to everyone when it is out.

macOS 12 or later koebelt-dash-1.3.0-rc.1-macos.dmg
Windows 10 or later (x64) koebelt-dash-1.3.0-rc.1-windows-x64-setup.exe (not code-signed yet: if SmartScreen stops it, choose More info, then Run anyway)
Linux (x64) koebelt-dash-1.3.0-rc.1-linux-x64.tar.gz
Android 7 or later koebelt-dash-1.3.0-rc.1-android.apk

koebelt dash 1.3.0-beta.5

Pre-release

Choose a tag to compare

@github-actions github-actions released this 28 Oct 11:29

Beta. A beta of koebelt dash 1.3: scripts and AI assistants. It is offered only to apps with Settings > Updates > Betas on; please report problems on GitHub.

koebelt dash now runs your Python scripts, with any package you like, and lets AI assistants help you, with the operator always in charge.

New in beta.5

  • Modes, simpler. A device connects disarmed in HOLD (simulated ones too: the drone waits on the ground). Arming hands it to you in MANUAL. AUTO is dash's: only while a sequence or a script drives the device, and it goes back to HOLD when that ends. The mode control is MANUAL | HOLD | AUTO, with AUTO lit and naming what drives; choosing a mode or moving the sticks takes over. Scripts no longer switch to MANUAL themselves: arm the device, and dash drives it in AUTO for them.
  • The mode on Live. Live has the mode control in its bar (on phones, the badge at the top lights up in AUTO); choosing MANUAL there opens Control, where the sticks are.
  • Proximity sensors. Ultrasonic, infrared and time-of-flight sensors show on Live from above, a wedge each, coloured by how close; the Obstacle close alert warns while armed. Scripts read them with dev.proximity(), and conditions with prox.front or prox.nearest. Devices declare them with koebelt/link 1.1.0 (Arduino, Python, Rust, ROS 2); the simulated rover and drone have some.
  • What runs shows. A pulsing dot marks Sequences and Scripts (and Automate) while one runs, and Automate's cards say what.
  • A console that reads at a glance. Errors in red, warnings in amber, info: lines in blue, debug: lines in grey (or Python's logging); tracebacks and the library's errors colour themselves.
  • Follow a person turns towards the person (it turned away), and both vision examples say what they see and do in the console.
  • The Scripts screen opens the script you had open; the examples fold away once you have scripts of your own.

New in beta.4

  • Automate. Program becomes Automate: a page that presents the two ways to automate a device side by side, Sequences (steps in order, no code, on the device) and Scripts (Python), with a guide, Sequence or script?, that compares them. On desktops the sidebar always lists both.
  • Sequences, by name. What was called a program is a sequence everywhere: scripts call dev.run_sequence("Survey square") (the *_program names still work), and assistants run_sequence.
  • Pictures and charts in Live. dev.show("tracking", frame) puts a picture in the Live view (a camera frame with what the script found drawn on it, a mask, a matplotlib figure), dev.chart() a line, bar or scatter chart, and dev.plot() takes several series. Each is a widget: on the wall at once, on the HUD in a free spot.
  • An editor that knows your code. Completion for the API, your own names, the device's sticks, telemetry and sequences, the libraries you import (np., cv2.) and file paths; parameter hints as you type; details when you hover a name, with the whole docstring of a library function.
  • Recorded, and replayed. What scripts show is kept with the recording: Replay shows the pictures and charts at their time, next to the telemetry.
  • Vision without hardware. The cameras of simulated drones and rovers show a yellow ball rolling near home and a person in red walking round it: the Colour tracker example follows the ball on a simulated rover as is.
  • Check, for real. Check now finds what would stop a script before it moves anything: syntax, imports this Python lacks (with the pip install to run), names that are not defined (pritn), and calls the device does not have or with the wrong arguments. Each problem is underlined on its line, and Run checks first: with errors, it asks before starting.
  • Missing packages. A script that imports something its Python lacks offers to install it, on its page and when you press Run.
  • What a script needs. # requires: drone, gps, camera limits a script to the devices that fit: the others are marked in its device menu, and Run says what they lack.
  • No device, no run. Run waits until a device is connected (or the one chosen for the script is).
  • Maps from Mapbox. Dark, Outdoors and Satellite maps replace OpenStreetMap's servers. You can use your own Mapbox token in Settings > Map.
  • Installing or updating koebelt-dash-scripts says how it went, and stays a few seconds.
  • The scripts folder link opens the folder (it tried to open it in a text editor on macOS).

Scripts

  • Drive a device from Python. Automate > Scripts holds your scripts: create one from a template, import a .py or a .zip with its files, start from eight examples, edit in the built-in editor, check it, and run it on any connected device, simulated ones included.
  • Any Python package. Scripts run in your own Python, so OpenCV, PyTorch and YOLO work: the camera arrives as NumPy images, newest first, and dev.overlay() draws what your model sees over the camera in dash. The first time, Set up Python prepares an environment with the koebelt-dash-scripts package.
  • Steps and sequences. Scripts take off, fly or drive to points, land, move arms and run your sequences, each returning once done.
  • Triggers. Fire a script's events from a button or a switch (also on Control, next to the sticks), a key, a controller button, a condition (battery.pct < 25 for 3s), a device event or a timer.
  • You stay in charge. STOP ends every script. Moving the sticks takes over until you resume. Each script has limits you set (speed, geofence, ceiling; no arming or parameter writes unless allowed). If a script crashes, hangs or leaves its geofence, the device holds and the script waits for you.
  • Phones and tablets run scripts on a script host: any computer on the same network running koebelt-dash-scripts host, paired once with a code. The phone keeps the device link, the sticks and STOP.
  • Errors that explain themselves: what went wrong, the line of your script, why, how to fix it, and the name you meant (koebelt-dash-scripts ERRORS.md).

AI assistants

  • Turn on Settings > AI assistants to let Claude, Cursor, Codex, OpenCode or another MCP client read the guides, look at your devices and recordings, write, check and test scripts on simulated devices, and use the app.
  • On real hardware, every action an assistant takes waits for your approval on a card in dash. You can allow a kind of action for the session; arming and take-off always ask. STOP never asks, and safety settings stay out of reach.
  • koebelt dash sends nothing to any AI service itself.

Also

  • New guides: Scripts, AI assistants, and Sequence or script?
  • Settings on a wide screen lists its sections beside them: click one to jump there.
  • The script panel shows the koebelt-dash-scripts version in each Python and offers updates; choosing a Python checks it again.
  • The chase view stays behind the drone as it yaws.
  • koebelt-dash-scripts 1.3.0b5 is on PyPI: pip install --pre koebelt-dash-scripts (dash's Set up Python installs it by itself). show(), chart(), run_sequence() and proximity() need it.

Updating

From 1.1.0 or later: turn on Settings > Updates > Betas, then use the Update button, or choose it in Settings > Updates > Versions. From 1.0.0, install this version by hand once. The final 1.3.0 will be offered to everyone when it is out.

macOS 12 or later koebelt-dash-1.3.0-beta.5-macos.dmg
Windows 10 or later (x64) koebelt-dash-1.3.0-beta.5-windows-x64-setup.exe (not code-signed yet: if SmartScreen stops it, choose More info, then Run anyway)
Linux (x64) koebelt-dash-1.3.0-beta.5-linux-x64.tar.gz
Android 7 or later koebelt-dash-1.3.0-beta.5-android.apk

koebelt dash 1.3.0-beta.4

Pre-release

Choose a tag to compare

@github-actions github-actions released this 25 Oct 21:04

Beta. A beta of koebelt dash 1.3: scripts and AI assistants. It is offered only to apps with Settings > Updates > Betas on; please report problems on GitHub.

koebelt dash now runs your Python scripts, with any package you like, and lets AI assistants help you, with the operator always in charge.

New in beta.4

  • Automate. Program becomes Automate: a page that presents the two ways to automate a device side by side, Sequences (steps in order, no code, on the device) and Scripts (Python), with a guide, Sequence or script?, that compares them. On desktops the sidebar always lists both.
  • Sequences, by name. What was called a program is a sequence everywhere: scripts call dev.run_sequence("Survey square") (the *_program names still work), and assistants run_sequence.
  • Pictures and charts in Live. dev.show("tracking", frame) puts a picture in the Live view (a camera frame with what the script found drawn on it, a mask, a matplotlib figure), dev.chart() a line, bar or scatter chart, and dev.plot() takes several series. Each is a widget: on the wall at once, on the HUD in a free spot.
  • An editor that knows your code. Completion for the API, your own names, the device's sticks, telemetry and sequences, the libraries you import (np., cv2.) and file paths; parameter hints as you type; details when you hover a name, with the whole docstring of a library function.
  • Recorded, and replayed. What scripts show is kept with the recording: Replay shows the pictures and charts at their time, next to the telemetry.
  • Vision without hardware. The cameras of simulated drones and rovers show a yellow ball rolling near home and a person in red walking round it: the Colour tracker example follows the ball on a simulated rover as is.
  • Check, for real. Check now finds what would stop a script before it moves anything: syntax, imports this Python lacks (with the pip install to run), names that are not defined (pritn), and calls the device does not have or with the wrong arguments. Each problem is underlined on its line, and Run checks first: with errors, it asks before starting.
  • Missing packages. A script that imports something its Python lacks offers to install it, on its page and when you press Run.
  • What a script needs. # requires: drone, gps, camera limits a script to the devices that fit: the others are marked in its device menu, and Run says what they lack.
  • No device, no run. Run waits until a device is connected (or the one chosen for the script is).
  • Maps from Mapbox. Dark, Outdoors and Satellite maps replace OpenStreetMap's servers. You can use your own Mapbox token in Settings > Map.
  • Installing or updating koebelt-dash-scripts says how it went, and stays a few seconds.
  • The scripts folder link opens the folder (it tried to open it in a text editor on macOS).

Scripts

  • Drive a device from Python. Automate > Scripts holds your scripts: create one from a template, import a .py or a .zip with its files, start from eight examples, edit in the built-in editor, check it, and run it on any connected device, simulated ones included.
  • Any Python package. Scripts run in your own Python, so OpenCV, PyTorch and YOLO work: the camera arrives as NumPy images, newest first, and dev.overlay() draws what your model sees over the camera in dash. The first time, Set up Python prepares an environment with the koebelt-dash-scripts package.
  • Steps and sequences. Scripts take off, fly or drive to points, land, move arms and run your sequences, each returning once done.
  • Triggers. Fire a script's events from a button or a switch (also on Control, next to the sticks), a key, a controller button, a condition (battery.pct < 25 for 3s), a device event or a timer.
  • You stay in charge. STOP ends every script. Moving the sticks takes over until you resume. Each script has limits you set (speed, geofence, ceiling; no arming or parameter writes unless allowed). If a script crashes, hangs or leaves its geofence, the device holds and the script waits for you.
  • Phones and tablets run scripts on a script host: any computer on the same network running koebelt-dash-scripts host, paired once with a code. The phone keeps the device link, the sticks and STOP.
  • Errors that explain themselves: what went wrong, the line of your script, why, how to fix it, and the name you meant (koebelt-dash-scripts ERRORS.md).

AI assistants

  • Turn on Settings > AI assistants to let Claude, Cursor, Codex, OpenCode or another MCP client read the guides, look at your devices and recordings, write, check and test scripts on simulated devices, and use the app.
  • On real hardware, every action an assistant takes waits for your approval on a card in dash. You can allow a kind of action for the session; arming and take-off always ask. STOP never asks, and safety settings stay out of reach.
  • koebelt dash sends nothing to any AI service itself.

Also

  • New guides: Scripts, AI assistants, and Sequence or script?
  • Settings on a wide screen lists its sections beside them: click one to jump there.
  • The script panel shows the koebelt-dash-scripts version in each Python and offers updates; choosing a Python checks it again.
  • The chase view stays behind the drone as it yaws.
  • koebelt-dash-scripts 1.3.0b4 is on PyPI: pip install --pre koebelt-dash-scripts (dash's Set up Python installs it by itself). show(), chart() and run_sequence() need this version.

Updating

From 1.1.0 or later: turn on Settings > Updates > Betas, then use the Update button, or choose it in Settings > Updates > Versions. From 1.0.0, install this version by hand once. The final 1.3.0 will be offered to everyone when it is out.

macOS 12 or later koebelt-dash-1.3.0-beta.4-macos.dmg
Windows 10 or later (x64) koebelt-dash-1.3.0-beta.4-windows-x64-setup.exe (not code-signed yet: if SmartScreen stops it, choose More info, then Run anyway)
Linux (x64) koebelt-dash-1.3.0-beta.4-linux-x64.tar.gz
Android 7 or later koebelt-dash-1.3.0-beta.4-android.apk

koebelt dash 1.3.0-beta.3

Pre-release

Choose a tag to compare

@github-actions github-actions released this 23 Oct 11:16

Beta. A beta of koebelt dash 1.3: scripts and AI assistants. It is offered only to apps with Settings > Updates > Betas on; please report problems on GitHub.

koebelt dash now runs your Python scripts, with any package you like, and lets AI assistants help you, with the operator always in charge.

Scripts

  • Drive a device from Python. A new Scripts screen (under Program on phones) holds your scripts: create one from a template, import a .py or a .zip with its files, start from eight examples, edit in the built-in editor (colours, completion for the API, a syntax check), and run it on any connected device, simulated ones included.
  • Any Python package. Scripts run in your own Python, so OpenCV, PyTorch and YOLO work: the camera arrives as NumPy images, newest first, and dev.overlay() draws what your model sees over the camera in dash. The first time, Set up Python prepares an environment with the koebelt-dash-scripts package.
  • Steps and programs. Scripts take off, fly or drive to points, land, move arms and run your Program sequences, each returning once done.
  • Triggers. Fire a script's events from a button or a switch (also on Control, next to the sticks), a key, a controller button, a condition (battery.pct < 25 for 3s), a device event or a timer.
  • You stay in charge. STOP ends every script. Moving the sticks takes over until you resume. Each script has limits you set (speed, geofence, ceiling; no arming or parameter writes unless allowed). If a script crashes, hangs or leaves its geofence, the device holds and the script waits for you.
  • Phones and tablets run scripts on a script host: any computer on the same network running koebelt-dash-scripts host, paired once with a code. The phone keeps the device link, the sticks and STOP.

AI assistants

  • Turn on Settings > AI assistants to let Claude, Cursor or another MCP client read the guides, look at your devices and recordings, write and test scripts on simulated devices, and use the app.
  • On real hardware, every action an assistant takes waits for your approval on a card in dash. You can allow a kind of action for the session; arming and take-off always ask. STOP never asks, and safety settings stay out of reach.
  • koebelt dash sends nothing to any AI service itself.

Also

  • New guides: Scripts, and AI assistants.
  • Settings on a wide screen lists its sections beside them: click one to jump there.
  • Settings > AI assistants gives the setup for Codex and OpenCode too.
  • Script errors explain themselves: what went wrong, the line of your script, why, how to fix it, and the name you meant (koebelt-dash-scripts ERRORS.md).
  • Choosing a Python checks it again, and offers to install koebelt-dash-scripts in it.
  • The script panel shows the koebelt-dash-scripts version in each Python and offers updates; scripts warn when their library is older than the app.
  • Looking for script hosts shows the searching animation.
  • The chase view stays behind the drone as it yaws (it turned the other way, which made yawing look twice as fast).
  • koebelt-dash-scripts is on PyPI as a beta: pip install --pre koebelt-dash-scripts (dash's Set up Python installs it by itself).

Updating

From 1.1.0 or later: turn on Settings > Updates > Betas, then use the Update button, or choose it in Settings > Updates > Versions. From 1.0.0, install this version by hand once. The final 1.3.0 will be offered to everyone when it is out.

macOS 12 or later koebelt-dash-1.3.0-beta.3-macos.dmg
Windows 10 or later (x64) koebelt-dash-1.3.0-beta.3-windows-x64-setup.exe (not code-signed yet: if SmartScreen stops it, choose More info, then Run anyway)
Linux (x64) koebelt-dash-1.3.0-beta.3-linux-x64.tar.gz
Android 7 or later koebelt-dash-1.3.0-beta.3-android.apk

koebelt dash 1.2.3

Choose a tag to compare

@github-actions github-actions released this 17 Oct 17:40

A small fix for iPhones held upright.

  • iPhone, upright: the tab bar sits a little higher, so the labels of the outer tabs are no longer cut by the screen's rounded corners.

Updating

From 1.1.0 or later, use the Update button in the app. From 1.0.0, install this version by hand once.

macOS 12 or later koebelt-dash-1.2.3-macos.dmg
Windows 10 or later (x64) koebelt-dash-1.2.3-windows-x64-setup.exe (not code-signed yet: if SmartScreen stops it, choose More info, then Run anyway)
Linux (x64) koebelt-dash-1.2.3-linux-x64.tar.gz
Android 7 or later koebelt-dash-1.2.3-android.apk

koebelt dash 1.2.2

Choose a tag to compare

@github-actions github-actions released this 16 Oct 12:50

A better fit for phones, held either way.

  • Held sideways: Control is laid out like a game controller, with bigger sticks in the bottom corners, the readouts between them and the buttons in two compact rows at the top. Live gets its own layout too, with taller tiles in the corners and the 3D view in the middle. Layouts you have already edited stay as they are.
  • iPhone, sideways: the screens use the whole height down to the bottom edge. On Live and Control the home indicator dims, and a first swipe up from the edge stays in the app, so a stick moved near the edge does not send you home; swipe again to leave.
  • iPhone, upright: the tab bar is slimmer and reaches into the strip at the bottom, leaving only the part the home swipe needs.

Updating

From 1.1.0 or later, use the Update button in the app. From 1.0.0, install this version by hand once.

macOS 12 or later koebelt-dash-1.2.2-macos.dmg
Windows 10 or later (x64) koebelt-dash-1.2.2-windows-x64-setup.exe (not code-signed yet: if SmartScreen stops it, choose More info, then Run anyway)
Linux (x64) koebelt-dash-1.2.2-linux-x64.tar.gz
Android 7 or later koebelt-dash-1.2.2-android.apk