FoundryNet / Error codes / MAVLink MAV_RESULT 3
MAVLink error code

MAV_RESULT 3 (3) — UNSUPPORTED — command not supported

The autopilot does not implement this command at all. Distinct from DENIED, where it is implemented but refused.

Start free All protocols

Diagnosis

When you hit this


Resolution

How to fix it

  1. Check the firmware's supported command set
    Autopilot documentation lists supported MAV_CMD values per version.
  2. Fall back to an older equivalent
    Many newer commands have a deprecated predecessor that older firmware accepts.

Normalization

What Forge does about it

This is a configuration or addressing mistake on the wire, upstream of anything Forge sees. Where Forge helps is the step after you fix it: once the point returns data, its vendor tag name maps to a canonical field automatically, so you do not also have to hand-maintain a name table for every point you just re-addressed.


Connect

Normalize MAVLink telemetry

One MCP endpoint serves every protocol adapter. 16,908 curated mappings, 366 canonical fields.

# normalize telemetry from MAVLink — and 13 other protocols
claude mcp add --transport http forge https://mcp.foundrynet.io/mcp \
  --header 'Authorization: Bearer YOUR_FORGE_KEY'
✓ forge connected — 32 tools available

Related

Keep reading

Other MAVLink codes: MAV_RESULT 2 MAV_RESULT 4 Heartbeat timeout

Other protocols: Modbus OPC UA MQTT / Sparkplug B FANUC FOCAS EtherNet/IP PROFINET / S7 BACnet/IP J1939 (CAN) MTConnect ROS 2 (DDS) SNMP HTTP / REST CSV ingest

All error codes · All OEMs · All protocols

Industrial AI fails at the data layer. The Machine Agent explains why, weekly. Read it →
Get the thesis behind this infrastructure — The Machine Agent, weekly.