ENVIRONMENTAL VERIFICATION

Proving the design holds
when the temperature moves.

A flight controller that works on the bench at 20°C tells you very little. We verify custom flight controllers across their operating temperature range — powered, with MAVLink telemetry live throughout — and interpret what the data says about the design.

What is actually measured

The board stays powered and connected for the entire profile. Nothing is inferred from a cold start afterwards.

Thermocouple placement

IMU sub-board, enclosure surface, and voltage regulator. Placement is a judgement call, not a checklist — the point is to separate ambient temperature from self-heating.

Live telemetry

MAVLink streams throughout the profile. IMU bias drift, EKF innovation and convergence behaviour, and rail voltage are logged continuously against measured temperature.

Failure characterisation

If the EKF diverges or an axis drifts, the question is why. Sensor part-to-part variation, thermal design, or firmware compensation — the three are distinguished, not guessed.

Why this is difficult to source

Test houses can run a chamber. Board designers can lay out a PCB. Firmware engineers can read an EKF log. Environmental verification of a flight controller requires all three at once, because the interesting failures sit exactly where those disciplines meet.

A rail that sags 80 mV at −20°C is a regulator problem. An accelerometer bias that walks with case temperature is a placement problem. An EKF that refuses to converge only after a cold soak is usually neither — it is a compensation coefficient that was fitted at room temperature. Telling these apart is the work.

We design and build the flight controllers we test. That is the difference.

Facility

Testing is performed using the environmental chamber at a public testing institute in Tokyo. Using an independent public facility rather than in-house equipment means the measurement environment itself is not ours to influence.

Temperature range−40°C to +85°C (chamber capability to +100°C)
Humidity range20–98% RH (control range varies with temperature)
Chamber volume1000 × 800 × 1000 mm
Cable portsØ50 mm and Ø120 mm, 2 positions
Powered testingYes — power and telemetry routed through cable ports

Chamber size permits testing of a complete airframe, not only the board. Where relevant, we verify the flight controller as installed rather than in isolation — enclosure, harness and mounting all affect thermal behaviour.

Deliverables

  1. Test plan — profile, instrumentation points, pass criteria, agreed before testing begins.
  2. Raw data — thermocouple logs and MAVLink telemetry, time-aligned.
  3. Test report — observed behaviour, anomalies, and their attributed cause.
  4. Design rationale — where a change is required, what to change and why.

Documents are written to be usable in certification discussions, not only as an internal record.

On type certification. In Japan, testing formally required for aircraft type certification must be conducted by a registered inspection body. We are not one, and this service does not replace that process.

What we provide is pre-compliance verification — finding and correcting design problems before formal certification, where a failure costs months and a re-submission. The intent is that you enter that process already knowing how the design behaves.

Who this is for

Airframe manufacturers

Approaching type or airworthiness certification and wanting design issues found before formal testing.

Operators importing hardware

Deploying flight controllers of unverified provenance and needing to establish how they actually behave outside room temperature.

Defence and public safety

Operating in conditions where the specification sheet and the field are not the same thing.

Request verification

Written specifications are sufficient to begin — a call is not required. We reply in writing within 2 business days. We operate from Japan (JST, UTC+9).

← Back to Custom Flight Controller Development