Low-altitude logistics multimodal system: one order, relayed through air and ground

A low-altitude logistics multimodal management system for campus and community scenarios: an on-site kiosk handles scan-to-buy and pickup-code collection, while the back-office control centre dispatches drones, AGV carts, PLC and smart cabinets as one relay — drones deliver to cabinets, carts bring goods to the door, an operation-mutex waiting screen guards the kiosk during flight, and every command is logged in an MQTT ledger.

Industry
Low-altitude economy / smart logistics and unmanned delivery (campus, community)
System type
Control kiosk (on site) + control back end + drone / AGV cart / PLC / smart-cabinet hardware integration
Key technology
Drone routes & simulated delivery · AGV waypoint dispatch · PLC cabinet release · operation mutex · MQTT command logging · vending-cabinet integration · third-party weather feed
Jiding scope
Requirement shaping, hardware-in-the-loop dispatch architecture, front and back end, device communication integration, launch support
4boards: control kiosk, control back end, drone link, unmanned-cart link
3hardware types on two-way commands: drones, AGV carts, PLC — commands and receipts both flow
10back-office pages from login to message management, permission split by role
2automated chains: drone delivery and remote pickup, both with no manual steps
Commands flow from the back end to the devices; status flows back to the order Users Kiosk Back end Devices On-site users Scan to buy · pickup code · watch ads Third-party services Live weather · vending cabinets · extension protocols Control kiosk (on-site terminal) Weather · cabinet stats · ads · scan-to-buy · quick pickup · support Operation-mutex waiting screen Other kiosk functions locked mid-delivery Drone mgmt List · routes Parcels Parcels · shipments Smart cabinets Cabinet params Cart mgmt Vehicles · waypoints Messages MQTT ledger System Permissions Drone Fly · arrive · drop · return AGV cart Get address · deliver · report back PLC Drop goods · report · open cabinet Smart cabinet Deposit · pickup · stats The four device types never talk to each other directly — they all answer to the control centre. One command from the back end, and drone, cart and PLC relay the order; every command and receipt lands in the MQTT ledger. Kiosk and back end are separate tiers.
Four layers: users act on the kiosk, the back end dispatches, four device types relay the order; weather and vending cabinets come in through reserved protocol interfaces

Challenges

Three breaks: devices in silos, on-site safety, commands nobody can trace

Drones, carts, PLC and cabinets each ship with their own control software. The hard part is not making any single device move — it is making them relay one order.

Break one: four device silos

Drones had a flight console, carts a dispatch screen, cabinets their own panel, and the PLC only listened for signals. Delivering one order meant hopping between four interfaces, with nobody sure which step had actually happened.

Break two: on-site safety

During the tens of seconds a drone hovers to drop goods, a kiosk still running sales, ads or accepting touches is an accident waiting to happen. Safety cannot depend on a person watching — it needs a mechanism.

Break three: untraceable commands

Why did the drone return early? Why did the cabinet not open? Why is the cart parked? Device payloads lived in four vendor consoles, so troubleshooting ran on memory. No raw messages, no operations.

One judgement shaped the architecture: the hard part of low-altitude logistics is not making a drone fly — it is making drone, cart, PLC and cabinet relay one order automatically, with every step traceable. So the unified dispatcher and order spine came first; the operation mutex and message logging came with them.

Modules

Two ends, six back-office modules and one kiosk

The back end owns dispatch and ledgers; the kiosk owns the on-site interaction. Both ends look at two halves of the same order: the back end watches commands and states, users scan to buy or collect.

ModuleWhat is insideWho uses it
Control kioskThird-party live weather, cabinet operation stats, ads, scan-to-buy, quick pickup and support on one home screen; operation-mutex waiting screen; restocking and maintenance require a dedicated login, split between ordinary users and administratorsVisitors and on-site staff: buy, collect and restock on one terminal
Back-end homeAggregated cabinet stats; simulated order entry tracked end to end; select a pending order and dispatch a simulated drone delivery; launch a remote pickup task that engages the AGVOperations: one place to dispatch from
Drone managementDrone list (multi-condition filter, add, view, edit, simulated delivery, gateway registration, delete) + route management (route parameter entry and maintenance)Maintenance: device registry and route planning in the back end
Parcel managementParcel list (add / view / edit / delete) + shipment list (waybills, flight preparation)Operations: parcel to waybill to flight prep, one line per order
Cabinet managementCabinet list: parameter entry, viewing and editingMaintenance: one registry of cabinets
Cart managementCart list (vehicle parameters) + waypoint list (delivery points)Maintenance: two ledgers, vehicles and waypoints
Message managementMQTT raw-data table: every two-way command and receipt, filterableMaintenance and troubleshooting: the payload is the evidence
System managementBack-office accounts, departments, role permissions, global menu routes, password changes; reserved extension-protocol config and user data maintenanceAdministrators: who sees and edits what is a config decision

One design worth naming: simulated delivery is a shipped feature, not a debug switch. New routes and new cabinets run the full flow on simulation first — command, waiting screen, cabinet release, drop-off, return — and only then touch a real drone. On-site trial-and-error cost drops to zero.

Delivery Journey

Six steps for one delivery: one command from the centre, devices relay the rest

From the flight command to the drone’s return, one delivery walks six steps. The point is that all six are dispatched by the control centre — nobody runs goods across the site, nobody switches screens.

①②③ ④⑤⑥ Control centre Devices & kiosk Back to centre Flight command Pick a pending order Drone arrives Above the cabinet Kiosk locks Waiting screen forced Cabinet opens Released remotely Goods dropped Drop-off signalled Auto return Order state updates Order tracked end to end Logged via MQTT Arrival syncs the kiosk Delivery state begins Sales and ads paused Mis-touch risk removed Open signals the drone to drop the goods Drone returns on its own Kiosk resumes itself State fully traceable User collects by code Step three is the safety valve: while the waiting screen is up, every other kiosk function is locked — and it resumes itself when delivery ends In this order, drone, cabinet, kiosk and back end do one thing each: relay by order state. The user collects by pickup code or scan, and no human passes a message anywhere on the chain — that is what multimodal means in system terms: leg by leg, handover by state.
Delivery in six steps: the kiosk lock (operation mutex) is the safety valve, the order state is the baton — every command and receipt lands in the MQTT ledger

Why simulated delivery is a shipped feature

New routes need validation and new cabinets need integration runs; real test flights cost money and carry risk. The system puts simulated delivery inside the drone list: pick an order, issue the command, and the whole flow runs without a real aircraft attached.

Integration work becomes a back-office job: whether the command format is right, when the waiting screen fires, whether the cabinet receipt returns — one simulated pass answers all three. Launch rhythm moves from “test-fly when nobody is around” to “simulate first, fly second”.

Why gateway registration lives in the drone list

Each drone must join the system’s communication gateway before it can receive commands. Putting “register gateway” in the drone list’s action column means device registry and connection happen in one place: add the drone, enter parameters, register the gateway — and the device is in the system.

The registry and the link state live on the same list, so maintenance sees “which device, on which gateway, what was its last command” at a glance.

Pickup Journey

Remote pickup: one command, two branches

After a remote pickup starts, the control centre does two things at once: the PLC drops the goods and opens the cabinet, and the cart carries them to the delivery address. Both branches report back; nothing needs a person.

Pickup command out To PLC and cart at once PLC drops goods Per the command PLC reports back Drop-off receipt Cabinet opens Ready for pickup Address pushed Sent with the command Cart delivers Drives by waypoint Return reported Enters waiting zone PLC branch: gets the goods out Open cabinet = ready Cart branch: gets goods there Back means ready, no dispatcher needed One command, two actions: PLC and cart run their own legs, the centre only watches receipts.
Two branches: the PLC gets the goods out, the cart gets them there — each reports its own receipt, and a returning cart parks itself in the waiting zone

Why a returning cart enters the waiting zone by itself

A cart that stops where it finished its last delivery has to be fetched by a dispatcher. With return reporting, the system puts it back into the waiting zone and marks it available.

The dispatch console loses a job: nobody needs to know where each cart is, only how many carts the waiting zone holds. Device status and dispatch capacity are the same dataset.

Why PLC and cart run as branches, not in series

The cabinet release and the cart run do not depend on each other: the cart can be on its way while the goods come out. In series, pickup time doubles and the user waits longer at the kiosk.

Parallelism only works because each branch owns a receipt: the PLC’s drop-off receipt and the cart’s return report both land back at the centre, and the order state closes. The hard part of concurrency is not running in parallel — it is collecting the receipts.

Traceability

Back-office panorama: ten pages, every command and receipt logged

The back office is organised by device and business, ten pages in all. The MQTT raw-data table in message management is the operations foundation: every command sent and every receipt returned has one row.

Every module is a list plus maintenance actions: filter, add, view, edit, delete — and a few device-specific actions Drone management Parcel management Cabinet management Cart management Message management System management Control kiosk List (filter / add / edit / simulate / register gateway / delete) · route management Parcel list · shipment list (waybills / flight preparation) Cabinet list: parameter entry, viewing, editing Cart list · waypoint list: two ledgers, vehicles and points MQTT raw-data table: every two-way command and receipt queryable Accounts · departments · roles · menu routes · passwords Weather · stats · ads · scan-to-buy · quick pickup · waiting screen 2 pages 2 pages 1 page 2 pages 1 page 1 page Kiosk Pages total 10 + 1 on-site kiosk Device-specific actions only grow where they belong: drones get simulate and gateway, shipments get flight prep — nothing generic is rebuilt
Back-office panorama: ten pages plus one kiosk; the MQTT table in message management makes every command queryable — troubleshooting runs on payloads, not memory

Why message management is its own module

Four device types speak different payloads at different rates; scattered across modules, a timeline has to be stitched from four screens. The MQTT raw-data table gathers them into one grid: filter by time, device or topic, one row per message.

During integration it is the debugger: if a command does not take effect, first check whether it was sent and what the device answered. In operation it is the black box: any “cabinet did not open” has a raw record to replay.

Why reserved protocol interfaces ship in version one

Weather and vending cabinets are third-party services integrated from day one; the extension protocols reserve interfaces without implementing them — the client explicitly planned later expansion with the business shape still open.

The cost of reserving interfaces is paid at design time: abstracting “third-party service access” into a protocol layer means every future service is a configuration job, not a rebuild. In a hardware-integrated system that is the most valuable architectural decision on the list.

Deliverables & Results

What the client got

Delivered

  • Control kiosk: weather feed, cabinet stats, ads, scan-to-buy, quick pickup and support on one home screen
  • Operation mutex: kiosk functions locked with a waiting screen during delivery, resumed automatically afterwards
  • Control back end: aggregated stats, simulated order entry with end-to-end tracking, simulated delivery, remote pickup, vending-cabinet integration, user data and settings
  • Drone chain: drone list (simulated delivery, gateway registration), route management, delivery commands, auto return
  • Parcel chain: parcel list, shipment list (waybills, flight preparation)
  • Cabinets and carts: cabinet parameters, vehicle list, waypoint list
  • PLC link: remote goods drop, drop-off receipt, cabinet release
  • Messages and system: MQTT raw-data table, accounts / departments / roles / menu routes, reserved extension protocols

Effect & de-identification

The most direct change: four consoles became one. A delivery is dispatched from a single control centre, and drone, PLC and cart relay by order state — nobody hops between four vendor screens to pass a message.

The second change is safety: the operation mutex and waiting screen remove “kiosk touched while a drone hovers” from the process altogether — safety runs on mechanism, not on staff attention.

The third change is operations: every device message is logged, so any anomaly has a record to replay; with simulated delivery, new-device integration moved from on-site test flights to back-office rehearsal. As agreed, this page shows no client name and no production screenshots, and third-party hardware brands are not disclosed.

Building low-altitude logistics, unmanned delivery or campus multimodal transport? The hard part is rarely one device’s integration — it is the unified order state machine, the operation-mutex safety mechanism, and device message logging. We have ground through all three on this system; bring your device list and we will tell you which linkage is your bottleneck.

MORE CASES

More Related Cases

Low-altitude logistics multimodal management system
System Integration OMLow-altitude logistics, fully automated distribution

Low-altitude logistics multimodal management system

A low-altitude logistics multimodal management system for campus and community scenarios: an on-site...

View Details →
Smart fire-safety platform for residential communities
System Integration OMSmart fire protection, community fire protection IoT

Smart fire-safety platform for residential communities

A fire-safety management platform for property managers and district fire supervision: admin console...

View Details →

View All Cases →

Planning a similar production line or enterprise system?

Start with our pricing logic, then let's talk requirements — cost structure, technology comparison and acceptance criteria, all laid out in the open.