Skip to content

About

Handheld for the Deep Robotics X30 (x30_ros): drive, patrol, inspection and recording from a Skydroid H12 or any Android

Resources

Stars

0 stars

Watchers

0 watching

Forks

Repository files navigation

X30 Controller

The handheld for the Deep Robotics Jueying X30 (x30_ros): drive it, teach and run its routes, inspect a substation and record its cameras, from a Skydroid H12 or any Android device in landscape.

The app talks the teleop protocol v1 straight to the robot's teleop_udp_node (x30_bridge, PROTOCOL.md) over the robot's Wi-Fi; there is no ROS on the handheld. It started from PashupatiController (the same protocol, so it drives a Pashupati robot too) and adds the X30's own parts.

Features

Drive

  • The Skydroid H12's own sticks (through Skydroid's SDK, below): left stick drives and strafes, right stick turns; key A switches AUTO / REMOTE, B is STOP, C / D and switch E set the speed level.
  • Or a gamepad (a Retroid, any Bluetooth pad), or touch sticks on the screen: the same APK runs on any Android 7+ phone or tablet (below).
  • AUTO / REMOTE, three speed levels, the X30's actions (stand up, sit down, stepping, gaits) as icons. STOP is the software e-stop, released by holding the button for a second.

See

  • The inspection camera, visible or thermal (one tap switches), and the map: the route with its stop points, the robot's trail, the LiDAR and the robot.

Patrol and inspect

  • Record a route and its stop points, record tags, localize, pick a route, start, pause, resume or end the patrol, set its speed.
  • Inspect where the robot stands: the PTZ camera and the acoustic camera at every target of that inspection point (minutes); the last point and its severity on the screen.
  • Record: the camera recorder of the robot's perception host (raw thermal frames, video, acoustic data) on and off by hand; it records every patrol by itself. Time, frames and the disk left are on the screen.

Monitor

  • Battery, link quality, protective field, health, localization, the computer's load and the trip.

Indonesian and English.

Install

From a release. Releases: the latest x30-controller-<version>.apk (its .sha256 beside it). Open the page in the H12's browser and install the download, or from a computer with the H12 on USB:

gh release download -R DarmawanRobotics/X30Controller -p 'x30-controller-*.apk'
adb install -r x30-controller-*.apk

From CI. Every push builds a release APK: open Actions, pick the latest green run, download the x30-controller-apk artifact, unzip it and install it the same way. Both carry Skydroid's SDK, fetched for the build (Skydroid H12).

From source. Flutter 3.35 or newer, the handheld on USB in adb devices:

git clone [email protected]:DarmawanRobotics/X30Controller.git && cd X30Controller
flutter pub get
flutter build apk --release
adb install -r build/app/outputs/flutter-apk/app-release.apk

First connection. Join the robot's Wi-Fi (X30*****, Application Manual 3.1). On the start screen tap the version three times: the robot is 192.168.1.106:9870 (its navigation host), and the token is the robot's X30_TELEOP_TOKEN (/etc/x30/navigation.env).

Any Android phone or tablet

The release APK runs on any Android device, not only the H12. Skydroid's SDK starts only on a Skydroid handheld (it recognizes them by model); anywhere else the app says Not a Skydroid handheld in the settings and drives with the touch sticks on the screen, or a gamepad.

Settings (gear), Sticks:

Choice Drives
Auto (default) the H12's sticks, else a gamepad, else the touch sticks
H12 only the H12's sticks; also starts Skydroid's SDK on a handheld whose model it does not recognize
Gamepad only a gamepad (Bluetooth or USB)
Touch only the touch sticks, even with a gamepad or the H12 there

The left touch stick drives and strafes, the right one turns; release them and the robot stops. Hold the phone in landscape.

Skydroid H12

The H12 sends its sticks over its own radio, not as an Android gamepad: only Skydroid's RC SDK reads them on the handheld. The SDK is Skydroid's and proprietary, so it is not in this repository; a build fetches it:

  1. tool/skydroid_sdk.sh fetch puts rcsdk-v1.9.2.aar in android/app/libs/, from Skydroid's demo (https://gitee.com/skydroid/rcsdk-demo, app/libs) or a copy of the same file, checked against its sha256 either way. CI and releases do this; a release without it fails.
  2. Build as above. The build finds it (build.gradle.kts) and compiles the SDK reader (android/app/src/skydroid); without it a stub says there is none. tool/skydroid_sdk.sh check <apk> says whether an APK carries it.
  3. On the H12: Settings (gear), Skydroid H12 sticks shows the link and the channels live. Pick the channels of forward, strafe and turn (default 2, 1, 3: the left stick drives, the right stick turns) and reverse those that go the wrong way.

A stick that does not spring back (a throttle stick without a centring spring) must not drive: map forward to a stick that centres by itself (CH4, the right stick's up and down, for example), or set the stick's centring in the H12's own assistant. A released stick must read about 1500.

The keys: A (CH5) AUTO / REMOTE, B (CH6) STOP, C (CH9) / D (CH10) speed down / up, switch E (CH7) the speed level. The robot only takes the sticks in REMOTE, and the control mux zeroes them when the handheld falls silent.

Controls

H12 Gamepad Touch
Drive and strafe left stick left stick left touch stick
Turn right stick right stick right touch stick
STOP (software e-stop) B B, on every page red button
AUTO / REMOTE A Start switch on top
Speed level C / D, switch E D-pad up / down Settings
Visible / thermal camera camera button by the small view
Robot actions L1 + A stand up, L1 + Y sit down icons under STOP

Teach and patrol. REMOTE, Record, drive the route, Point at each stop, Finish; then Routes, pick it, AUTO, Start. On a stop with an inspection point the robot inspects it by itself (x30_inspection).

Develop

lib/
├── protocol/   messages.dart (JSON of the teleop protocol, the X30's recorder and substation)
├── net/        teleop_client.dart (session, commands, sticks, the camera chosen), discovery.dart
├── input/      skydroid_input.dart (the H12 through its SDK), gamepad_input.dart, sticks.dart
├── widgets/    hud, camera, map, glance, x30_panel (recorder, inspection), touch_stick, trip
├── screens/    connect, drive (home), patrol, routes, settings
├── robot_actions.dart   icons and labels of known robot commands (the X30's too)
└── l10n.dart            Indonesian and English text
android/app/src/
├── main/kotlin/…/MainActivity.kt   gamepad events, the x30/skydroid channels
├── skydroid/java/…                 the H12 reader (with the SDK)
└── noskydroid/java/…               its stub
flutter analyze
flutter test

CI runs on every push: analysis, tests (failures as annotations), formatting notices, the APK.

Releases

Push a tag v<version>, the version in pubspec.yaml, to publish a GitHub Release with the APK (.github/workflows/release.yml):

git switch main && git pull && git tag v1.0.2 && git push origin v1.0.2

Bump version: in pubspec.yaml and appVersion in lib/screens/connect_screen.dart together (test/version_test.dart checks them), then tag main after the last pull request is merged: the release builds exactly the tagged commit. v1.0.0 was tagged before Skydroid's SDK was in the build and does not read the H12's sticks; v1.0.1 never built (the two versions differed). Use v1.0.2 or later.

The APK is signed with the release key when the repository has these secrets, so a new release installs over the old one: ANDROID_KEYSTORE_BASE64 (the keystore, base64), ANDROID_KEYSTORE_PASSWORD, ANDROID_KEY_ALIAS, ANDROID_KEY_PASSWORD. Without them it is signed with the runner's debug key: uninstall the old app before installing a new one.

License

Apache 2.0. Skydroid's SDK, when you add it, is under Skydroid's own terms.

About

Handheld for the Deep Robotics X30 (x30_ros): drive, patrol, inspection and recording from a Skydroid H12 or any Android

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages