Different heat sources can produce similar hotspots in a single-channel thermal image, leaving the operator to determine the source. We want to test with a European manufacturer of unmanned aircraft systems (UAS), on its own platform, whether MIRGUARD 614 can distinguish relevant heat-source classes and reduce the alerts an operator checks by hand.
Before that test, you need the starting parameters and their limits. Both are below.
What we want to test with you
MIRGUARD 614 reads the scene in the 6–14 μm band. Beyond temperature, it uses that spectral information to classify the heat source. Atmospheric auto-calibration accounts for humidity and rain.
A joint test answers three questions on your mission profile:
- Does MIRGUARD separate the source classes your operators care about? For example, sun-heated metal versus a chemical spill, or a real heat source versus a reflection.
- On the same flights, how many of the alerts raised by your current thermal channel would MIRGUARD clear?
- How does the reading hold up in the weather your platform actually flies in?
The output is a written comparison against ground truth, not a demo video. We do not claim the answer to question 3 in advance. The field pilot measures it.
The current demonstrator
- Length: 140 mm
- Diameter: Ø115 mm
- Mass: approx. 1.5 kg including mounting hardware and cables
- Channels: 8 in 6–14 μm; NETD 50–200 mK @ 1 Hz; IP54 (datasheet, Oct 2026)
- Band: 6–14 μm
- Power consumption: 7 W average; 13 W maximum
The current unit measures 140 mm × Ø115 mm (product datasheet, October 2026). The final integration envelope will be confirmed during the platform fit assessment.
Limits to put on the sheet first
- Mass. Approx. 1.5 kg includes mounting hardware and cables. Platform fit and the required payload margin are assessed case by case during the fit assessment.
- Envelope. The envelope is 140 mm along the sensor axis × Ø115 mm (datasheet, October 2026). The fit assessment confirms connector and cable clearance and mounting compatibility for your platform.
- Power and data interface. Power consumption is 7 W on average and 13 W maximum at +5 V DC. Data output is XML 16-bit to SD card, with optional LTE transmission (datasheet, October 2026).
- Environment. Vibration, shock, temperature, EMC and flight stability have not been tested on a UAS yet. That testing happens with the OEM, on the OEM’s platform.
- Datasheet. Published 15 October 2026: 8 channels in 6–14 μm, NETD 50–200 mK @ 1 Hz, IP54, operating −20…+50 °C.
Proposal: a first-pass integration assessment
- You send: bay internal dimensions and mounting points, available payload mass and your margin policy, available power (voltage, watts), data interface, CG constraints, and the mission profile (altitude, speed, typical weather).
- We return a written first-pass assessment against the current demonstrator: go, conditional go or no-go, with each open point named, for example mounting compatibility or cable routing.
- If it is a go, we scope a paid PoC on your platform in one of three formats: lab screening on materials you supply, a field pilot on your test area, or integration of the instrument on your airframe. Each is priced per project, by scope, area and location.
The split of work stays the same throughout. You keep the airframe, the end customer and system certification. We bring the payload and carry the sensor-level integration work.
Next step
Send us your bay envelope: r.ledak@mirores.eu. You get the written first-pass assessment. If the numbers work, a short technical call with our engineers scopes the PoC.