Go to flight

Your payload passed the bench. This page lists what to finish before it flies. Send the list to Urban Sky with your flight request.

Before you start

Complete Test and troubleshoot on a Husky bus. A cloud bench bus does not test power, logs and metrics, or radio links.

Lab checks and the qualification run

Your payload needs all five Lab checks passing. Send the saved diagnostic report with your flight request.

A Lab report is diagnostic. It does not approve a payload for flight. Before a new payload flies, Urban Sky runs a trusted qualification on a real bus with your flight software, and records the software version and capability document it tested. A change to either after qualification needs a new run.

Pending

Balto does not yet run or record the qualification itself. Today Urban Sky staff run it with the checks on this page and keep the record with your flight request.

1. Freeze the software

• Record the software version you will fly: identity.software_version in your capability document (device API), or softwareVersion in your announcement (self-announce).
• Build the flight image from that version. Install credentials outside the image.
• Run the acceptance checks again on the flight image.

2. Check the payload on the flight bus

On the bus that will fly, with the flight image:

Check	Balto command	Pass
Registered under the flight bus	balto payloads list --bus <flight bus>	Your serial, with parent_serial set to the flight bus. Device API: the bus allows your module (PAYLOAD_LAN_MODULES).
Telemetry at the flight rate	balto trace <payload> --up --follow	One report for each interval, for 10 minutes.
A harmless command works end to end	balto payloads send <payload> <command> ..., then balto payloads audit <payload> --limit 1	COMMAND_STATE_APPLIED, and the effect in telemetry.
Restart	Power-cycle the payload rail	It reports again within one interval (self-announce: it announces again first).
Logs and metrics	GET /api/v1/payload/status on the bus	No drops after a 10-minute run.

Adoption and enable-commands are per payload and per serial. A new serial, or a registration that was retired, starts discovered again.

3. Agree the flight plan with Urban Sky

• Commands. Which commands operators may send in flight, and which are engineering-only (audience: "AUDIENCE_ENGINEERING"). Who in your team sends them.
• Power. The rail voltage and the peak current.
• Data. Your telemetry interval and the size of each report. Logs and metrics stay inside the limits.
• Video. The route, codec and bit rate. See Video.
• Support. Who Urban Sky calls during the flight, and how your team reads balto trace and balto payloads audit while it flies.

During the flight

Use the same tools as on the bench: balto trace <payload> --follow for live traffic, balto payloads audit <payload> for commands. Report problems with the serial, the UTC time and the request ID.

---

← Test and troubleshoot · Back to overview