Ardu frame client
This page describes the ArduPilot-specific implementations of the IFrameClient microservice.
Both clients work with the Params client to read and write the underlying ArduPilot parameters. The concrete parameter names differ between Copter and QuadPlane.
They share a common IDroneFrame implementation — ArduDroneFrame.
Implementations
ArduCopterFrameClient (source)
Reads/writes ArduPilot params:
FRAME_CLASSFRAME_TYPE
Uses map as a compability reference.
ArduQuadPlaneFrameClient (source)
Reads/writes ArduPilot params:
Q_FRAME_CLASSQ_FRAME_TYPE
Uses map as a compability reference.
ArduDroneFrame (source)
Represents an ArduPilot frame. It exposes the FrameClass and an optional FrameType; their values align with the corresponding device parameters.
The optional Meta dictionary contains device‑specific parameter metadata and maps parameter names to enum names (e.g., FRAME_CLASS: "Quad", FRAME_TYPE: "X").
The Id is a human‑readable identifier composed from the class and (optionally) the type (e.g., "Quad (1) / X (1)").
Exceptions
ArduFrameClassUnknownException (source)
Raised when the current device frame class can’t be mapped to the known enum values.
ArduFrameTypeUnknownException (source)
Raised when the current device frame type can’t be mapped to the known enum values.