Test Against a Simulated, Continuously-Armed Mission#
PX4 SITL auto-disarms after a short idle period with no RC/GCS input. Both
pipeline_manager.py’s ARMED-triggered auto-start (standalone mode) and the
UAV Mission Compute SDK’s arm-gated RTSP publishing depend on the vehicle
staying armed. If you are testing pipelines interactively — not flying a
scripted mission — you will otherwise hit unexplained stream drop-outs.
Important
This tutorial describes simulation-only testing conveniences for interactive development against PX4 SITL. It is not a change to, and must never be applied to, real flight safety/arming logic.
Prerequisites#
A running simulated stack — standalone mode (
make pymav-up) or UAV Mission Compute SDK mode (SDK’smake up-sim-camera+make uavsdk-up).QGroundControl connected, if you also want to observe arming state visually — see the QGroundControl guide.
Why PX4 SITL auto-disarms#
PX4’s safety logic auto-disarms when it detects no active RC/GCS input for a timeout period — this exists to prevent a real vehicle from remaining armed unattended, and PX4 SITL faithfully reproduces it. During interactive pipeline testing (manually starting/stopping pipelines, checking overlays, tailing logs) rather than flying a scripted mission, that idle window is often exceeded, so the vehicle disarms and dependent pipelines/streams stop.
Steps#
Standalone (Pymavlink) mode — keep-alive pattern#
The standalone stack has no REST action endpoint (:8080/action/arm belongs to the UAV Mission Compute SDK).
Use one of:
Arm from QGroundControl and press takeoff, a vehicle that is flying does not auto-disarm (see the QGroundControl guide).
Run the cameras without depending on the arming state:
docker exec -it -e HOST_IP=<HOST_IP> uav-va-dlstreamer-pipeline-server python3 /home/pipeline-server/scripts/pipeline_manager.py --start-now.
Note
If you script the arm yourself (a MAVLink command over UDP 14551), repeat it on a timer
shorter than the idle-disarm timeout.
UAV Mission Compute SDK mode — keep-alive pattern#
The SDK exposes a REST action endpoint. Loop it the same way:
while true; do
curl -sf -X POST http://localhost:8080/action/arm > /dev/null 2>&1 || true
sleep 20
done
Run this in its own terminal so it keeps running while you separately start pipelines and inspect streams/logs in other terminals.
Verify#
curl -k -s https://<HOST_IP>/pipelines/status | python3 -m json.tool
Confirm the expected pipeline(s) stay RUNNING for longer than the normal
idle-disarm timeout, instead of stopping a few tens of seconds in.
Troubleshooting#
Arm/disarm flapping that leaves a stream down is covered in Troubleshooting — Rapid arm/disarm flapping. This keep-alive pattern is for SITL testing only; do not work around PX4’s idle-disarm safety behavior on real flight hardware.