EMAX Tinyhawk II Freestyle FPV Drone with F4 Flight Controller RunCam Nano2 and 7000KV Motors

Price: 214.99$
Model:

Get Quote

+86-13959965075

Revision-specific interface file

Connect Tinyhawk II hardware without blending revisions

All inspected views match a Tinyhawk II Freestyle airframe. The archived controller, receiver protocol, camera, motor, battery arrangement, measured mass and video-radio language still requires a revision-specific bill of materials. An interface map can show which labels and records belong together without turning model-family recognition into a technical guarantee.

Control board

Radio

EMAX Tinyhawk II Freestyle airframe retained for revision-specific identity review. — The overall view supports model recognition while controller and receiver details require labels.

Imaging

Power train

Tinyhawk II interface register

Interface group	Evidence source	Release question
Control board	Board label, target and firmware archive	Installed revision
Radio	Receiver protocol, antenna and regional record	Ordered option
Imaging	Camera label and original sample file	Current camera
Power train	Motor markings, battery arrangement and measured state	Matched configuration

Tinyhawk II interface checks

Photograph controller, receiver, camera and motor identifiers.
Archive firmware target and settings before changes.
Record battery arrangement and measured receiving condition.
Attach video-radio evidence to the applicable hardware and region.

Receiver protocol needs an order link

A family photograph cannot identify the receiver fitted to the current unit. The order line, visible label and software record should agree.

Video settings have a regional context

Channel and output statements belong with the actual transmitter revision and applicable regional file. They should not be presented as a universal setting list.

Separate battery format from receiving mass

Photograph each battery label, connector and installed orientation before weighing the delivered aircraft in a defined receiving state. This keeps battery arrangement and measured mass tied to one unit instead of importing a model-family value into the current revision.

Tinyhawk II evidence questions

Do the images prove the receiver protocol?: No. Confirm it through the current order, visible receiver evidence and software record.
What supports the camera identity?: Use the camera label and an original sample file from the delivered unit.
How should the battery arrangement be recorded?: Photograph the installed setup and retain the measured state beside the exact battery labels.

Review EMAX interface records

Use the EMAX category for identity context, then request the Tinyhawk II revision file.

View EMAX product evidence

Interface Map

Tinyhawk II interface card

Connect controller, receiver, camera, propulsion and battery evidence without merging revisions.

01: Photograph flight-controller, receiver-protocol, camera and motor identifiers.
02: Document the delivered battery arrangement and measured mass separately.
03: Keep video-channel and output evidence attached to the applicable radio region.