# BlueOS Arduplane 4.5.4 firmware no sensors detected (barometer not found) **URL:** \ **Category:** Sensors\ **Created:** [July 19, 2024, 5:20pm UTC](https://discuss.bluerobotics.com/t/blueos-arduplane-4-5-4-firmware-no-sensors-detected-barometer-not-found/17488 "2024-07-19T17:20:14Z")\ **Posts on this page:** 1\ **Showing post:** 12
**Author:** ![rosss](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/rosss/32/13957_2.png) [@rosss](https://discuss.bluerobotics.com/u/rosss)\ **Post date:** [July 20, 2024, 9:08pm UTC](https://discuss.bluerobotics.com/t/blueos-arduplane-4-5-4-firmware-no-sensors-detected-barometer-not-found/17488/12 "2024-07-20T21:08:35Z")
> [@williangalvani](#): > > Argonot I have tried building my own navigator using your schematic, I havent changed a thing (same IMU and sensors), check the thread where the guy also did something similar > [@Custom ROV with custom flight controller running BlueRobotics Software](https://discuss.bluerobotics.com/t/custom-rov-with-custom-flight-controller-running-bluerobotics-software/15845/2): > > Hello @Lord_Slothman , I believe we have a similar project on the go. Take a look here, [Is QGroundControl needed to control my rover or can I use a BlueOS extension? - #4 by EliotBR](https://discuss.bluerobotics.com/t/is-qgroundcontrol-needed-to-control-my-rover-or-can-i-use-a-blueos-extension/13874/4). @rafael.lehmkuhl was hugely helpful to get the respective scripts to recognise the “flight controller”. Due to the required channel volumes, our flight controller is a stack of boards. We have a board that handles the communications and on it is a chip with a unique identifier/address. The detect.py looks for this… --- _[View the full topic](https://discuss.bluerobotics.com/t/blueos-arduplane-4-5-4-firmware-no-sensors-detected-barometer-not-found/17488)._