# Can't connect to vehicle **URL:** \ **Category:** Blue Robotics Software\ **Created:** [February 28, 2022, 3:46pm UTC](https://discuss.bluerobotics.com/t/cant-connect-to-vehicle/11638 "2022-02-28T15:46:54Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![niklas\_diver](https://avatars.discourse-cdn.com/v4/letter/n/7ba0ec/32.png) [@niklas\_diver](https://discuss.bluerobotics.com/u/niklas_diver)\ **Post date:** [February 28, 2022, 3:46pm UTC](https://discuss.bluerobotics.com/t/cant-connect-to-vehicle/11638/1 "2022-02-28T15:46:54Z")
Hey! I was out yesterday testing ROV and everything worked fine. Today when I start, I get no contact (only camera is shown). I have removed the memory card from Raspberry and formatted but no success. I have also tested on another computer but the same problem there. I can connect to 192.168.2.2 ![A8225756-3DD7-4C76-9AAC-9A130022DB67](https://us1.discourse-cdn.com/flex019/uploads/bluerobotics/original/2X/c/c6bb28b855ea0a6d6608564fe694df2bbb7ebeb9.jpeg) ---
**Author:** ![EliotBR](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/eliotbr/32/6937_2.png) [@EliotBR](https://discuss.bluerobotics.com/u/EliotBR)\ **Post date:** [March 3, 2022, 11:27am UTC](https://discuss.bluerobotics.com/t/cant-connect-to-vehicle/11638/2 "2022-03-03T11:27:40Z")
Hi @niklas_diver, apologies on the delay in getting to this. > [@niklas\_diver](#): > > I was out yesterday testing ROV and everything worked fine. > > Today when I start, I get no contact (only camera is shown). That’s quite unusual, and unexpected. Assuming you’re using our Companion software, are you able to see Pixhawk as a Detected Device, and `mavproxy` as one of the Active Services on the [System page](https://www.ardusub.com/reference/companion/system.html) of the Companion web interface? Out of interest, did you update your macOS version recently? About a week ago we had an issue where [MacOS 12.2 seemingly caused some issues with UDP communication](https://discuss.bluerobotics.com/t/macos-monterey-12-2-udp-not-working/11608). ---
**Author:** ![niklas\_diver](https://avatars.discourse-cdn.com/v4/letter/n/7ba0ec/32.png) [@niklas\_diver](https://discuss.bluerobotics.com/u/niklas_diver)\ **Post date:** [March 3, 2022, 8:24pm UTC](https://discuss.bluerobotics.com/t/cant-connect-to-vehicle/11638/3 "2022-03-03T20:24:41Z")
Hi Eliot! After having both memory cards out and formatting and updating the software, it’s up and running again. Surprised at how it can stop working from one day to the next without having configured or updated the computer. Glad it works again, thanks for the help. This link led to success > [@Software Updates](https://discuss.bluerobotics.com/t/software-updates/1128): > > If you purchased your BlueROV2 after June 2017, you do not need to do this software update! We’ve got a big round of updates! To start, ArduSub V3.5 has been released and is the now the current stable version of ArduSub. You can see the release notes for ArduSub [here](https://raw.githubusercontent.com/ArduPilot/ardupilot/master/ArduSub/ReleaseNotes.txt). QGroundControl has seen many updates since 3.1.3 (no more calibrating joysticks in reverse!), and we are now recommending an updated build for use with ArduSub (required for use with ArduSub v3.5 and up). This version of QGC has … //Niklas, Sweden ---
**Author:** ![EliotBR](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/eliotbr/32/6937_2.png) [@EliotBR](https://discuss.bluerobotics.com/u/EliotBR)\ **Post date:** [March 8, 2022, 4:54am UTC](https://discuss.bluerobotics.com/t/cant-connect-to-vehicle/11638/4 "2022-03-08T04:54:04Z")
Hej @niklas_diver, > [@niklas\_diver](#): > > After having both memory cards out and formatting and updating the software, it’s up and running again. > … > Glad it works again, thanks for the help. Glad to hear you managed to sort out the issue! 🙂 > [@niklas\_diver](#): > > Surprised at how it can stop working from one day to the next without having configured or updated the computer. So are we - that’s not expected behaviour, and is understandably something we actively try to avoid! On that note, one of the main goals with [BlueOS](https://discuss.bluerobotics.com/t/blueos-1-0-beta-testing/10830) (which will be replacing the Companion software) is increased robustness. While it’s definitely convenient to have a “nuke the system” option for starting fresh, that should be an absolute last resort, particularly given the work involved in opening up the vehicle and removing and flashing SD cards. The existing software stack and updating processes unfortunately haven’t been sufficiently stable to provide the experience we want, and BlueOS has been very much designed with lessons from that in mind, along with the intent that opening the enclosure should only need to happen when hardware is actually being modified or added 🙂