# 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:** 20\ **Page:** 1
**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 19, 2024, 5:20pm UTC](https://discuss.bluerobotics.com/t/blueos-arduplane-4-5-4-firmware-no-sensors-detected-barometer-not-found/17488/1 "2024-07-19T17:20:14Z")
Navigator flight controller stuck at “INITIALISING” with barometer, accelerometer not detected. I have 3 navigator boards, the issue same on all. ---
**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 19, 2024, 8:25pm UTC](https://discuss.bluerobotics.com/t/blueos-arduplane-4-5-4-firmware-no-sensors-detected-barometer-not-found/17488/2 "2024-07-19T20:25:09Z")
here is a system status log I got using swagger ui get request [WeTransfer - Send Large Files & Share Photos Online - Up to 2GB Free](https://we.tl/t-at3mniLqT1?utm_campaign=TRN_TDL_05&utm_source=sendgrid&utm_medium=email&trk=TRN_TDL_05) ---
**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 19, 2024, 8:27pm UTC](https://discuss.bluerobotics.com/t/blueos-arduplane-4-5-4-firmware-no-sensors-detected-barometer-not-found/17488/3 "2024-07-19T20:27:10Z")
![telegram-cloud-photo-size-2-5249021369897834563-y](https://us1.discourse-cdn.com/flex019/uploads/bluerobotics/original/2X/9/9711a046a090180a83265f2331157f023f57d373.jpeg) ---
**Author:** ![williangalvani](https://avatars.discourse-cdn.com/v4/letter/w/6f9a4e/32.png) [@williangalvani](https://discuss.bluerobotics.com/u/williangalvani)\ **Post date:** [July 19, 2024, 10:09pm UTC](https://discuss.bluerobotics.com/t/blueos-arduplane-4-5-4-firmware-no-sensors-detected-barometer-not-found/17488/4 "2024-07-19T22:09:50Z")
Hi, can you ellaborate on the issue? I see some conflicting information. Your title mentions ArduPlane 4.5.4, but the picture shows ArduSub 4.1.2. I recommend updateing BlueOS to the latest beta, and resetting the parameters to the firmware defaults: ![Screenshot 2024-07-19 at 19.06.45](https://us1.discourse-cdn.com/flex019/uploads/bluerobotics/original/2X/5/51f74f3661720304e8cc8bcb301b065ea7d81dfb.jpeg) If the issue persisnt, send us the system logs. they can be found in the settings menu (gear icon under the main menu options): ![Screenshot 2024-07-19 at 19.09.14](https://us1.discourse-cdn.com/flex019/uploads/bluerobotics/original/2X/f/fbfcdbc1b9db8de1f2153f819ea031bfa86fa77d.png) ---
**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, 4:43pm UTC](https://discuss.bluerobotics.com/t/blueos-arduplane-4-5-4-firmware-no-sensors-detected-barometer-not-found/17488/5 "2024-07-20T16:43:01Z")
I installed ArduSub 4.1.2 just to test whether it would work with older versions of firmware, specifically with ardusub instead of arduplane. Ok, I updated BlueOS to latest Beta [1.3.0-beta.7](https://github.com/bluerobotics/BlueOS/releases/tag/1.3.0-beta.7) and flashed the latest Arduplane firmware through BlueOS.local web UI. Will send you all the logs, etc now ---
**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, 5:50pm UTC](https://discuss.bluerobotics.com/t/blueos-arduplane-4-5-4-firmware-no-sensors-detected-barometer-not-found/17488/6 "2024-07-20T17:50:12Z")
![image](https://us1.discourse-cdn.com/flex019/uploads/bluerobotics/original/2X/d/da090ad7f7a8177a1a30ba2d7209db7a3ac5e3c9.png) ---
**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, 5:52pm UTC](https://discuss.bluerobotics.com/t/blueos-arduplane-4-5-4-firmware-no-sensors-detected-barometer-not-found/17488/7 "2024-07-20T17:52:14Z")
I did reset all parameters, and rebooted as suggested. Does not help. ---
**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, 6:01pm UTC](https://discuss.bluerobotics.com/t/blueos-arduplane-4-5-4-firmware-no-sensors-detected-barometer-not-found/17488/8 "2024-07-20T18:01:14Z")
here are the system logs .zip [https://file.io/Tg6OQQitqDT9](https://file.io/Tg6OQQitqDT9) ---
**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, 6:14pm UTC](https://discuss.bluerobotics.com/t/blueos-arduplane-4-5-4-firmware-no-sensors-detected-barometer-not-found/17488/9 "2024-07-20T18:14:43Z")
In terminal I assume I have i2c devices listed (barometer, accelerometer, gyroscope, etc). Maybe i need to point somehow their addresses for blueos ![image](https://us1.discourse-cdn.com/flex019/uploads/bluerobotics/original/2X/6/65d054ca43cec8d5d69f800161ffa5d6c387b229.png) ---
**Author:** ![williangalvani](https://avatars.discourse-cdn.com/v4/letter/w/6f9a4e/32.png) [@williangalvani](https://discuss.bluerobotics.com/u/williangalvani)\ **Post date:** [July 20, 2024, 6:46pm UTC](https://discuss.bluerobotics.com/t/blueos-arduplane-4-5-4-firmware-no-sensors-detected-barometer-not-found/17488/10 "2024-07-20T18:46:28Z")
Hi, it seems that there are some issues on your i2c buses. are you using a navigator? do you have any other peripherals attached? Your BlueOS is sometimes identifying the Board as Argonot, which has a different set of sensors than navigator. ---
**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, 8:43pm UTC](https://discuss.bluerobotics.com/t/blueos-arduplane-4-5-4-firmware-no-sensors-detected-barometer-not-found/17488/11 "2024-07-20T20:43:47Z")
do you have a reference of what is Argonot? I cant even find it on google ---
**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… ---
**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:27pm UTC](https://discuss.bluerobotics.com/t/blueos-arduplane-4-5-4-firmware-no-sensors-detected-barometer-not-found/17488/13 "2024-07-20T21:27:19Z")
![2024-07-21 00.26.18](https://us1.discourse-cdn.com/flex019/uploads/bluerobotics/original/2X/8/8a5f0652352988d40839e0c782b4ef457b4a36ac.jpeg) ![2024-07-21 00.26.24](https://us1.discourse-cdn.com/flex019/uploads/bluerobotics/original/2X/7/78138440252ebe233c6f116a833328632293a70c.jpeg) ![2024-07-21 00.26.28](https://us1.discourse-cdn.com/flex019/uploads/bluerobotics/original/2X/d/da9c2cb9d07131fa886187cab6476a404dd9b0d4.jpeg) ---
**Author:** ![williangalvani](https://avatars.discourse-cdn.com/v4/letter/w/6f9a4e/32.png) [@williangalvani](https://discuss.bluerobotics.com/u/williangalvani)\ **Post date:** [July 20, 2024, 10:00pm UTC](https://discuss.bluerobotics.com/t/blueos-arduplane-4-5-4-firmware-no-sensors-detected-barometer-not-found/17488/14 "2024-07-20T22:00:17Z")
Somethign is probably off. Navigator is detect upon detecting these: ADS1115\_address = 0x48 on i2c-1 AK09915\_address = 0x0C on i2c-1 BME280\_address = 0x76 on i2c-1 (this one is the on-board baro) PCA9685\_address = 0x40 on i2c-4 Argonot is detected upon detecting: swap\_multiplexer\_address = 0x77 on i2c-1 If detection (and ardupilot itself) is failing, something is probably off with your board. Try reducing the i2c baud in /boot/config.txt you may need to add `# CUSTOM` after the changed lines so blueos doesnt change them back. ---
**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 21, 2024, 10:47am UTC](https://discuss.bluerobotics.com/t/blueos-arduplane-4-5-4-firmware-no-sensors-detected-barometer-not-found/17488/15 "2024-07-21T10:47:18Z")
Yes, I see it in [Detector.py](https://github.com/bluerobotics/BlueOS/blob/master/core/services/ardupilot_manager/flight_controller_detector/Detector.py). I might try switching i2c addresses, by making a fork of blueos and recompiling. Do you know a way of detecting via terminal the i2c devices or scanning for everything possibly connected? ---
**Author:** ![williangalvani](https://avatars.discourse-cdn.com/v4/letter/w/6f9a4e/32.png) [@williangalvani](https://discuss.bluerobotics.com/u/williangalvani)\ **Post date:** [July 21, 2024, 8:45pm UTC](https://discuss.bluerobotics.com/t/blueos-arduplane-4-5-4-firmware-no-sensors-detected-barometer-not-found/17488/16 "2024-07-21T20:45:37Z")
Yes, try `i2detect -y 1` to detect devices on i2c-1 and so on I recomend `watch -n 0.1 i2cdetect -y 1` to have it run at 10hz, so you can have an idea of how consistent/noisy the bus is ---
**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:** [August 4, 2024, 5:30pm UTC](https://discuss.bluerobotics.com/t/blueos-arduplane-4-5-4-firmware-no-sensors-detected-barometer-not-found/17488/17 "2024-08-04T17:30:09Z")
what if there is no config.txt in [_home_](http://192.168.2.2/file-browser/files)**/[system\_root](http://192.168.2.2/file-browser/files/system_root/)**/[boot](http://192.168.2.2/file-browser/files/system_root/boot/) I tried watching with i2cdetect, nothing changes only 2 addresses available all the time ![image](https://us1.discourse-cdn.com/flex019/uploads/bluerobotics/original/2X/9/9cbe588e1609cd53096cf49fca6d12be28fd1b9f.png) I tried: `find /boot -name "config.txt" | grep config.txt`. ![image](https://us1.discourse-cdn.com/flex019/uploads/bluerobotics/original/2X/b/b48ab405a65a3257dfa1eb21eb3ac61c42e7e3ed.png) I think overall this tutorial is the way to go.[Change Raspberry Pi I2C Bus Speed - Raspberry Pi Spy](https://www.raspberrypi-spy.co.uk/2018/02/change-raspberry-pi-i2c-bus-speed/) ---
**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:** [August 7, 2024, 6:17pm UTC](https://discuss.bluerobotics.com/t/blueos-arduplane-4-5-4-firmware-no-sensors-detected-barometer-not-found/17488/18 "2024-08-07T18:17:24Z")
Ok, I configured /boot/config.txt using this [GitHub - EmilGus/install\_raspi-config: Script to install raspi-config on Raspberry Pi devices with an Linux OS that's missing it, like Kali Linux.](https://github.com/EmilGus/install_raspi-config) ---
**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:** [August 7, 2024, 6:44pm UTC](https://discuss.bluerobotics.com/t/blueos-arduplane-4-5-4-firmware-no-sensors-detected-barometer-not-found/17488/19 "2024-08-07T18:44:58Z")
> [@williangalvani](#): > > # CUSTOM blueOS seems to always delete config.txt after each reboot of raspberry. Boot folder is empty after reboot. ---
**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:** [August 12, 2024, 2:09pm UTC](https://discuss.bluerobotics.com/t/blueos-arduplane-4-5-4-firmware-no-sensors-detected-barometer-not-found/17488/20 "2024-08-12T14:09:02Z")
![Знімок екрана 2024-08-12 о 17.01.09](https://us1.discourse-cdn.com/flex019/uploads/bluerobotics/original/2X/9/95e96c6976efe797a0998b5b60b1397bf3cdd81d.jpeg) so config is now booting ok, I am using different sd card and different raspberry 4. But when I edit the config.txt the blueOS changes it back. `# Custom` does not help. [Next page](https://discuss.bluerobotics.com/t/blueos-arduplane-4-5-4-firmware-no-sensors-detected-barometer-not-found/17488.md?page=2)