# No Telemetry After Updating Pixhawk firmware to v4.0.1 **URL:** \ **Category:** Blue Robotics Software\ **Created:** [April 21, 2020, 5:33pm UTC](https://discuss.bluerobotics.com/t/no-telemetry-after-updating-pixhawk-firmware-to-v4-0-1/7237 "2020-04-21T17:33:01Z")\ **Posts on this page:** 15\ **Page:** 1
**Author:** ![hube268](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/hube268/32/5292_2.png) [@hube268](https://discuss.bluerobotics.com/u/hube268)\ **Post date:** [April 21, 2020, 5:33pm UTC](https://discuss.bluerobotics.com/t/no-telemetry-after-updating-pixhawk-firmware-to-v4-0-1/7237/1 "2020-04-21T17:33:01Z")
Hi Jacob, We’re trying to get our BlueROV2 Heavy updated to the newest firmware but when we do, we lose telemetry. Video still displays correctly so I don’t think its a network or RPi issue. I have several Pixhawks and tried tried updating the firmware on a couple more and as soon as I update, I lose telemetry. I went through the troubleshooting guide and everything checked out as it should. After updating, even when wedirectly connecting the Pixhawk to the topside computer we cannot get telemetry even though we can confirm that the USB shows a connection. We also confirmed we have a good USB cable. We are using the latest stable version of QGC running on a Ubuntu linux topside station (latest Ubuntu). We updated the Pixhawk firmware through QGC. Please help us fix this? ---
**Author:** ![jwalser](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/jwalser/32/2234_2.png) [@jwalser](https://discuss.bluerobotics.com/u/jwalser)\ **Post date:** [April 21, 2020, 10:21pm UTC](https://discuss.bluerobotics.com/t/no-telemetry-after-updating-pixhawk-firmware-to-v4-0-1/7237/2 "2020-04-21T22:21:16Z")
Please [update companion](http://www.ardusub.com/operators-manual/software-update.html#companion), and make sure you are using the latest version (0.0.20). ---
**Author:** ![hube268](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/hube268/32/5292_2.png) [@hube268](https://discuss.bluerobotics.com/u/hube268)\ **Post date:** [April 22, 2020, 4:08am UTC](https://discuss.bluerobotics.com/t/no-telemetry-after-updating-pixhawk-firmware-to-v4-0-1/7237/3 "2020-04-22T04:08:43Z")
Hi Jacob, I confirmed that the companion software has the latest version 0.0.20 and was there prior to running the update… What else can I do? ---
**Author:** ![nmau](https://avatars.discourse-cdn.com/v4/letter/n/e68b1a/32.png) [@nmau](https://discuss.bluerobotics.com/u/nmau)\ **Post date:** [April 25, 2020, 2:00pm UTC](https://discuss.bluerobotics.com/t/no-telemetry-after-updating-pixhawk-firmware-to-v4-0-1/7237/4 "2020-04-25T14:00:01Z")
Hi, we have the same problem. We have tried two Pixhawk. We have to update through the web system page and directly through usb and QGC. We only managed to retrieve the older version. We had updated QGC and companion without any error message. Any idea? BR, nikos ---
**Author:** ![nmau](https://avatars.discourse-cdn.com/v4/letter/n/e68b1a/32.png) [@nmau](https://discuss.bluerobotics.com/u/nmau)\ **Post date:** [April 26, 2020, 9:17am UTC](https://discuss.bluerobotics.com/t/no-telemetry-after-updating-pixhawk-firmware-to-v4-0-1/7237/5 "2020-04-26T09:17:44Z")
Hi, I upload some photos for the problem: br2\_01 / br2\_02 → (first try) updating using the page 192.168.2.2:2770/system br2\_03 → (second try) updating using QGC and direct USB connection between Pixhawk and laptop br2\_04 / br2\_05 → the final result… Any idea? BR, nikos ![br2_01](https://us1.discourse-cdn.com/flex019/uploads/bluerobotics/original/2X/7/71204b384584d752d69fff8ae405895e1b48100b.png) ![br2_02](https://us1.discourse-cdn.com/flex019/uploads/bluerobotics/original/2X/8/8337fbfc7c31c62b054aeff21a2adda4d412dfb3.png) ![br2_03](https://us1.discourse-cdn.com/flex019/uploads/bluerobotics/original/2X/4/426a6a1ac20504abe17f9d96c96c7a76ba497d50.png) ![br2_04](https://us1.discourse-cdn.com/flex019/uploads/bluerobotics/original/2X/9/919f03f54ccaeac411d10e4bd8154e7237b1242d.png) ![br2_05](https://us1.discourse-cdn.com/flex019/uploads/bluerobotics/original/2X/6/606adf6d6bc43fc960053cddef89175ec8ef1284.jpeg) ---
**Author:** ![nmau](https://avatars.discourse-cdn.com/v4/letter/n/e68b1a/32.png) [@nmau](https://discuss.bluerobotics.com/u/nmau)\ **Post date:** [April 27, 2020, 10:34am UTC](https://discuss.bluerobotics.com/t/no-telemetry-after-updating-pixhawk-firmware-to-v4-0-1/7237/6 "2020-04-27T10:34:52Z")
kind remind! ---
**Author:** ![williangalvani](https://avatars.discourse-cdn.com/v4/letter/w/6f9a4e/32.png) [@williangalvani](https://discuss.bluerobotics.com/u/williangalvani)\ **Post date:** [April 27, 2020, 2:08pm UTC](https://discuss.bluerobotics.com/t/no-telemetry-after-updating-pixhawk-firmware-to-v4-0-1/7237/7 "2020-04-27T14:08:25Z")
Hi! If you have no telemetry when connected via direct USB connection to QGC, we can discard the companion as the failure point. Can you try booting the Pixhawk without it’s SD card (it should work fine in 4.0) and also after formatting it’s SD card? ---
**Author:** ![nmau](https://avatars.discourse-cdn.com/v4/letter/n/e68b1a/32.png) [@nmau](https://discuss.bluerobotics.com/u/nmau)\ **Post date:** [April 28, 2020, 10:05am UTC](https://discuss.bluerobotics.com/t/no-telemetry-after-updating-pixhawk-firmware-to-v4-0-1/7237/8 "2020-04-28T10:05:09Z")
@williangalvani, thank you for your answer. The situation is exactly the opposite: when I connect Pixhawk using USB I have telemetry and connection with QGC. The problem is when I try to connect using the companion computer! I will try to update the companion computer again… Nikos ---
**Author:** ![williangalvani](https://avatars.discourse-cdn.com/v4/letter/w/6f9a4e/32.png) [@williangalvani](https://discuss.bluerobotics.com/u/williangalvani)\ **Post date:** [April 28, 2020, 12:02pm UTC](https://discuss.bluerobotics.com/t/no-telemetry-after-updating-pixhawk-firmware-to-v4-0-1/7237/9 "2020-04-28T12:02:59Z")
Hi @nmau, Try resetting the mavproxy parameters to their defaults at [http://192.168.2.2:2770/mavproxy](http://192.168.2.2:2770/mavproxy) ---
**Author:** ![nmau](https://avatars.discourse-cdn.com/v4/letter/n/e68b1a/32.png) [@nmau](https://discuss.bluerobotics.com/u/nmau)\ **Post date:** [April 28, 2020, 12:28pm UTC](https://discuss.bluerobotics.com/t/no-telemetry-after-updating-pixhawk-firmware-to-v4-0-1/7237/10 "2020-04-28T12:28:16Z")
@williangalvani, it worked! Thank you! May you explain why I should resetting the mavproxy parameters? BR, nikos ---
**Author:** ![williangalvani](https://avatars.discourse-cdn.com/v4/letter/w/6f9a4e/32.png) [@williangalvani](https://discuss.bluerobotics.com/u/williangalvani)\ **Post date:** [April 28, 2020, 1:03pm UTC](https://discuss.bluerobotics.com/t/no-telemetry-after-updating-pixhawk-firmware-to-v4-0-1/7237/11 "2020-04-28T13:03:31Z")
The USB identifier in Ardusub 4.0 has changed and that was handled in companion a few versions ago, but we avoid changing the users parameters when updating so nothing breaks in custom setups. I put up an [issue to update our docs troubleshooting section](https://github.com/bluerobotics/ardusub-gitbook/issues/120). ---
**Author:** ![hube268](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/hube268/32/5292_2.png) [@hube268](https://discuss.bluerobotics.com/u/hube268)\ **Post date:** [May 5, 2020, 4:17am UTC](https://discuss.bluerobotics.com/t/no-telemetry-after-updating-pixhawk-firmware-to-v4-0-1/7237/12 "2020-05-05T04:17:51Z")
Just saw this, I will try this tomorrow. Hopefully I have the same result as @nmau ---
**Author:** ![hube268](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/hube268/32/5292_2.png) [@hube268](https://discuss.bluerobotics.com/u/hube268)\ **Post date:** [May 6, 2020, 4:19am UTC](https://discuss.bluerobotics.com/t/no-telemetry-after-updating-pixhawk-firmware-to-v4-0-1/7237/13 "2020-05-06T04:19:49Z")
That worked for me too! Thanks ---
**Author:** ![diegofox1990](https://avatars.discourse-cdn.com/v4/letter/d/278dde/32.png) [@diegofox1990](https://discuss.bluerobotics.com/u/diegofox1990)\ **Post date:** [July 11, 2020, 4:20am UTC](https://discuss.bluerobotics.com/t/no-telemetry-after-updating-pixhawk-firmware-to-v4-0-1/7237/14 "2020-07-11T04:20:09Z")
I am sorry, I do not use blueROV2 and ArduSub. but I’m facing the same problem, I’ve updated the PX4 firmware and the telemtry is not connecting to the Pixhawk. What do you mean when you say “Try resetting the mavproxy parameters to their defaults at [http://192.168.2.2:2770/mavproxy](http://192.168.2.2:2770/mavproxy)”? ---
**Author:** ![diegofox1990](https://avatars.discourse-cdn.com/v4/letter/d/278dde/32.png) [@diegofox1990](https://discuss.bluerobotics.com/u/diegofox1990)\ **Post date:** [July 12, 2020, 1:49pm UTC](https://discuss.bluerobotics.com/t/no-telemetry-after-updating-pixhawk-firmware-to-v4-0-1/7237/15 "2020-07-12T13:49:44Z")
I got the answer here [updating firmware](https://nxp.gitbook.io/hovergames/userguide/qgroundcontrol/firmware#updating-the-telemetry-radio-firmware)