Skip to content
ARGUS User Manual

Connectivity troubleshooting

When ARGUS loses its link to the TACLINK fabric or to Firestore you will see one of a handful of symptoms. This page is a checklist for operators plus an escalation path for support.

Symptoms

  • “Reconnecting…” banner along the top of the app. TACLINK has lost the SFU socket and is attempting backoff reconnect.
  • Frozen video tiles while telemetry still updates. Usually a peer- specific transport failure rather than a full outage.
  • Robotic or choppy PTT from operators on the same op. Indicates uplink packet loss or CPU starvation on the publisher side.
  • Telemetry gaps in the HUD or charts. Firestore lost its long-poll or the flight_status channel stopped arriving.
  • Map tiles fail to load but the rest of the UI works. Typically a CDN-specific problem rather than ARGUS.

Fast checks — 30 seconds

  1. General internet. Open a new tab and hit any unrelated site. If that’s slow, the problem is upstream.
  2. Toolbar network indicator. The wifi/cloud icon in the top bar shows three states: solid (healthy), amber (degraded — at least one transport is on relay), red (disconnected). Hover for details.
  3. TURN relay fallback. If the icon is amber, TACLINK has fallen back to a TURN relay. That is fine for control but will reduce video quality. Relay sessions resolve back to host/srflx once a clean path is rediscovered.
  4. Firewall — UDP 443 and MQTTS 8883. Corporate networks often block UDP 443 (used by WebRTC / QUIC) or the 8883 MQTTS port used by DJI docks. Ask IT to allow those specifically; we cannot tunnel them over 80/443 TCP without significant quality loss.
  5. Refresh. If state looks stuck, a hard reload (Ctrl+Shift+R) will rebuild the TACLINK client cleanly. Your op session survives this.

Browser compatibility

  • Chromium (Chrome, Edge, Brave) — best supported. All features tested here.
  • Firefox — works, with fallbacks. Simulcast layers are more limited and some getStats fields are missing from the TACLINK debug tile.
  • Safari — 17 or newer is required. Older Safari lacks transform-streams and will break E2E.
  • Mobile browsers — viable for viewing but not for commanding. Use the argus-android tablet for field operation.

DJI-specific connectivity

If the drone or dock is the one with the problem, jump to DJI troubleshooting — dock offline, live_start_push NACKs and FlySafe lock states are covered there.

Escalation

If the fast checks don’t help and you’re about to open a support ticket, grab this before you call:

  1. Mission ID and timestamp (UTC). The mission ID is the last segment of the URL when you’re in the op.
  2. Browser console log. Right-click → Inspect → Console → “Save as…”. Include the last 5 minutes before the problem.
  3. TACLINK debug JSON. From the op, open the TACLINK debug tile and click Copy as JSON. Paste into the ticket.
  4. argus-android diagnostics if the drone side is suspect — the tablet has its own Send diagnostics button in the app’s About screen.

Support can reproduce most issues from those four artefacts alone. Screenshots of symptoms help but are not a substitute for the debug JSON.