Drone Operators · Step 3

Fly a drone

A geoNFT flight has a clear beginning and end. You open it in the console, the ground station arms with a pairing code, the drone signs while it flies, and the flight is sealed and closed. Closing mints the flight's geoNFT on Hyperledger Fabric.

Before take-off

  • The drone is registered and selected on the Drones page.
  • The console shows Ledger <name> is open.
  • The gateway is powered; MAVProxy is running with the tcs module and the downlink on 127.0.0.1:5763 (see ground station).
  • The flight will last less than 8 hours; the flight token expires eight hours after you open the flight.

1. Open the flight

  1. Open Flights and check that Drone shows the right drone.
  2. Set Flight name (default survey). This becomes the flight's label in the catalog later.
  3. Optional: press Import flight plan and choose a JSON file. A Polygon geometry becomes the flight's area; a description is stored with the flight.

    {
      "description": "Roof inspection, Marienplatz block",
      "geometry": {
        "type": "Polygon",
        "coordinates": [[[11.5790, 48.1340], [11.5850, 48.1340],
                         [11.5850, 48.1365], [11.5790, 48.1365],
                         [11.5790, 48.1340]]]
      }
    }
  4. Press Open flight and complete the passkey prompt.

The page shows the Pairing code, the token expiry, and the eight-hour warning. The code also stays on the flight's card under Active flights as Arming code, even after a reload. One drone can have only one open flight at a time.

2. Arm the ground station

At the MAVProxy prompt, type the code from the page (without angle brackets):

tcs arm <pairing-code>

The module prints tcs arming, fetches the flight token in the background (for up to 25 seconds), sends the token, the observation addresses and the clock to the gateway, and prints tcs armed. From then on:

  • the gateway turns each position fix into a signed observation (every 5 seconds by default) and each camera frame into a picture with its own signature;
  • MAVProxy posts them to cs.geonft.eu with the drone's proof attached. You do not type the posts yourself;
  • Connected Systems checks each proof, stores the observation, pins pictures on IPFS, and queues a hash for Fabric.

Arming, linking and posting run in the background, so the MAVProxy console, map and vehicle link never freeze while waiting on the network.

The tcs commands

CommandWhat it does
tcs helpLists every tcs command with a one-line explanation.
tcs arm <code>Fetches the flight token with the pairing code and configures the gateway. Prints tcs armed, failed or cancelled.
tcs interval <seconds>How often the gateway emits a position observation (default 5).
tcs sealEnds the flight's signed record. The gateway sends what it still holds, then signs the seal and signs nothing more for this flight. Prints tcs sealed n=… received=… missing=[…].
tcs disarm [--force]Stops posting, discards queued observations and tells the gateway to stop signing. Before the seal it only warns; --force skips the seal. Not the same as the vehicle's disarm.
tcs link <host> <port>Opens the downlink to the gateway in the background (default 127.0.0.1 5763).
tcs push http · tcs push mqttPosts position observations with HTTP (default) or publishes them to the MQTT broker. Pictures always use HTTP.
tcs config mqtt <url> [port]Sets the broker, e.g. mqtt://cs.geonft.eu 10883; mqtts:// turns TLS on.
tcs config as <url>Operator address used by tcs arm, e.g. https://operator.geonft.eu.
tcs configPrints the operator address, Connected Systems origin, push mode and broker.
Network trouble

If the API falls behind, the oldest of 256 queued observations is dropped and counted; a queued seal is never dropped. An HTTP 401 disarms like tcs disarm; run tcs arm again with the same code. Dropped observations appear as gaps in the drone's chain; they cannot be hidden.

3. Watch the flight

On Flights, press Refresh. Active flights shows each open flight with the drone DID, the resolver link, the deployment id, and the datastreams with their observation counts. The last card shows the selected drone's latest latitude, longitude, height and heading, updated live while observations arrive.

Stored observations are on the Connected Systems API. To inspect them, press Bearer token in the console header, copy the token (valid 5 minutes), open cs.geonft.eu/docs, choose Authorize, paste it, and call GET /datastreams/{id}/observations.

4. Seal and close

A flight ends in two steps: the ground station seals it, then you close it.

  1. After landing, on the ground station:

    tcs seal
    tcs disarm

    Wait for tcs sealed n=… received=… missing=[…] before disarming. missing lists observations that were signed but never reached the server.

  2. In the console the flight's card shows Seal Sealed … within a few seconds, and Close flight becomes active.
  3. Press Close flight and complete the passkey prompt.

The page confirms the flight is closed and shows its deployment hash. Further telemetry from this flight is rejected, and the drone can open a new flight.

The geoNFT is minted

Closing writes the flight's manifest and mints its hash on Fabric. The deployments table shows the NFT state:

StateMeaning
NFT queuedWaiting to be minted.
NFT on FabricMinted, endorsed, and read back from the ledger with the same hash. The flight can now be published.
NFT failedMinting failed after retries; ask your administrator to retry.
NFT offFabric submission was switched off when the flight closed.
When the drone cannot seal

After a crash, a lost link or an expired token, Close flight stays greyed out. Use Close without seal, read the warning, and confirm with your passkey. The flight still gets an end time, but its record says the drone did not sign the end of its chain, and the QGIS verification will show that. Seal and close within the eight hours whenever you can.

What the ground crew needs from you

MomentYou hand over
After registrationThe alias and the did:indy:… value
After opening the flightThe pairing code
Before closingThe request to run tcs seal, then tcs disarm
After closingConfirmation that the flight is closed, and its deployment hash

Your closed flight is now ready for a flight analyst to publish in the catalog.