Drone Wiki
HE HE21 שפות
שפת Drone Wiki21
Remote controller profile

DJI RC Motion 3

DJI RC Motion 3 is a one-handed 118 g motion controller for compatible Avata 2, Avata 360, Neo/Neo 2 and selected camera drones. DJI rates stationary operating time up to ten hours with Goggles 3 in its test. Avata 360 requires Goggles 3 or Goggles N3; check the precise aircraft, headset and firmware combination before pairing.

Remote ControllerCompatibilityPairingInspection
DJI RC Motion 3
RCPROFILE TYPE
6COMPATIBLE MODELS
DJIECOSYSTEM
MAPPEDLISTING STATUS

Quick Answer

DJI RC Motion 3 supports the current DJI matrix models shown below. With Avata 360 it must be paired with DJI Goggles 3 or Goggles N3; verify firmware and regional availability.

Specifications

Controller typeOne-handed motion controller
ModelTKMO3
WeightApproximately 118 g
Battery2600 mAh; approximately 10 hours when stationary with Goggles 3 in DJI test conditions
ChargingApproximately 2 hours at 5 V/2 A
Avata 360 control pathRequires DJI Goggles 3 or DJI Goggles N3
Official sourceshttps://www.dji.com/support/product/rc-motion-3 · https://repair.dji.com/help/content?customId=01700010143&lang=en&paperDocType=ARTICLE&re=US&spaceId=17 · https://repair.dji.com/help/content?customId=01700043652&lang=en&paperDocType=ARTICLE&re=DK&spaceId=17

Compatibility Notes

DJI compatibility is aircraft, controller, headset, firmware, and region dependent.

Inspection Checklist

Pairing and firmware

Confirm the controller can bind to the exact target aircraft and firmware generation before treating it as compatible.

Controls and calibration

Check stick centering, wheel/dial response, shoulder buttons, pause/RTH, record/shutter, and calibration behavior.

Ports, antennas, and charging

Inspect USB-C, phone/screen connection, antennas, charging port, speaker, and battery behavior for wear or damage.

Mount and phone connection

For screen controllers, check display brightness, touch response, storage, Wi-Fi, and app login. For phone controllers, check clamp and cable behavior.

Common Failure Modes

Stick drift or calibration failure

Off-center sticks, dead zones, or failed calibration can cause unsafe inputs and should be verified before flight.

Binding or firmware mismatch

A controller can power on but fail pairing if aircraft generation, firmware, region behavior, or binding state is unsupported.

Port or charging fault

USB-C, phone link, charging, or screen connection faults can block updates, live view, or reliable operation.

Button, antenna, or internal board issue

Impact or moisture can affect antennas, button boards, joystick modules, internal flex cables, or RF modules.

Repair Notes

  • Do not assume DJI controllers with similar names are interchangeable; verify aircraft support and firmware first.
  • After stick, button, or board work, run controller calibration and a controlled low-risk pairing test.
  • Inspect ports, antennas, and battery behavior before blaming the aircraft for connection or signal faults.
  • If the controller was bound to another account or aircraft, resolve binding and firmware state before hardware diagnosis.

Pre-Owned Buying Checks

  • Confirm exact controller model, aircraft compatibility, and firmware pairing path.
  • Check stick centering, buttons, scroll wheels, antennas, screen/phone mount, ports, and charging behavior.
  • Avoid controllers with water exposure, impact damage, failed calibration, binding uncertainty, or port damage.
  • For screen controllers, inspect display, touch response, app login, Wi-Fi, storage, and battery condition.