Testing, testing and again testing - part 2

You may wonder what we do if we don't fly at the beach with the big drone testing the overall state of development. The answer is quite simple:

It's a lot of SW development done with bench testing, followed by system functionality verification by flight testing.
Due to the complexity of our system  we are flight testing every drone software change with a minimum of 10 flight hours on one of our small test drones before applying it on the project demonstrator

Example flight testing Radar & ROS2 based collision avoidance as well as UWB guided precision landing


The small test drone uses mainly the same NXP electronic components we have on the big X25 - NXP Auriol
  • MR-VMU-RT1176 (NXP i.MX RT1176) FMU running PX4
  • NavQplus (NXP i.MX8Mplus) companion computer running ROS2 Jazzy, connected via T1 ethernet to FMU
  • MR-T1ETH8 (NXP SJA1110) 10port T1 ethernet switch
  • FETtec ESC60A pro (NXP S32K146) controlled triple redundant via Dshot and 2x CAN bus
  • Consider-IT OBU (NXP SAF5400 & i.MX8) communication unit
  • Murata 2BP UWB development board (NXP SR150) for precision landing
  • smartmicro DRVEGRD®169 77GHz radar sensor based on NXP chipset.

Comments

Popular posts from this blog

Support to fire brigade at a wildfire

Successful test of ML based object detection

UWB guided drone landing