# No connection to Qgroundcontrol after changing RPI IP address

**URL:** https://discuss.bluerobotics.com/t/no-connection-to-qgroundcontrol-after-changing-rpi-ip-address/6426
**Category:** Blue Robotics Products
**Created:** [November 26, 2019, 3:18pm UTC](https://discuss.bluerobotics.com/t/no-connection-to-qgroundcontrol-after-changing-rpi-ip-address/6426 "2019-11-26T15:18:51Z")
**Posts on this page:** 7
**Page:** 1

<div class="post-metadata">

### Author: ![maxdrougge](https://avatars.discourse-cdn.com/v4/letter/m/f1d935/32.png) [@maxdrougge](https://discuss.bluerobotics.com/u/maxdrougge)
#### Post date: [November 26, 2019, 3:18pm UTC](https://discuss.bluerobotics.com/t/no-connection-to-qgroundcontrol-after-changing-rpi-ip-address/6426/1 "2019-11-26T15:18:51Z")

</div>

Hello.

I’ve been running my ROV without any problems for a while now. However. I decided to change the IP of the RPI (and PC) to 192.168.1.x to make it compatible with an ethernet sonar I’m using. When I changed the IP, Qgroundcontrol no longer connects to the pixhawk.  
I can still use the web interface for the RPI and once I changed the host ip for the video to the new IP address it works and shows up in Qgroundcontrol.

I’ve tried the troubleshooting on the homepage but nothing helps. I can see the pixhawk and software version through the RPI web ui. It just doesn’t want to connect via Qgroundcontrol.

So, this happened due to a change of IP on the RPI and PC. Nothing else.

Any idea how to solve this?

---

<div class="post-metadata">

### 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: [November 26, 2019, 7:49pm UTC](https://discuss.bluerobotics.com/t/no-connection-to-qgroundcontrol-after-changing-rpi-ip-address/6426/2 "2019-11-26T19:49:06Z")

</div>

This is not a supported use case yet.

The companion software is hardcoded to send telemetry to 192.168.2.1, your computer is not on this ip, so it cannot receive anything.

You can change the ip address at 192.168.2.2:2770/mavproxy and 192.168.2.2:2770/camera, or wait until dhcp is supported (scheduled by/before jan 1 2020).

---

<div class="post-metadata">

### Author: ![maxdrougge](https://avatars.discourse-cdn.com/v4/letter/m/f1d935/32.png) [@maxdrougge](https://discuss.bluerobotics.com/u/maxdrougge)
#### Post date: [November 27, 2019, 8:08am UTC](https://discuss.bluerobotics.com/t/no-connection-to-qgroundcontrol-after-changing-rpi-ip-address/6426/3 "2019-11-27T08:08:55Z")

</div>

Thanks for the response. Is it not possible to change the telemetry IP from somewhere in the raspberry image?

The reason I want to change is that I have a sonar that runs on 192.168.1.x. And it cannot be used along the raspberry pi as it is now.

---

<div class="post-metadata">

### 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: [December 2, 2019, 8:13pm UTC](https://discuss.bluerobotics.com/t/no-connection-to-qgroundcontrol-after-changing-rpi-ip-address/6426/4 "2019-12-02T20:13:19Z")

</div>

> [@maxdrougge](#):
>
> Is it not possible to change the telemetry IP from somewhere in the raspberry image?

It is possible:

> [@jwalser](#):
>
> You can change the ip address at 192.168.2.2:2770/mavproxy and 192.168.2.2:2770/camera

---

<div class="post-metadata">

### Author: ![maxdrougge](https://avatars.discourse-cdn.com/v4/letter/m/f1d935/32.png) [@maxdrougge](https://discuss.bluerobotics.com/u/maxdrougge)
#### Post date: [December 2, 2019, 8:49pm UTC](https://discuss.bluerobotics.com/t/no-connection-to-qgroundcontrol-after-changing-rpi-ip-address/6426/5 "2019-12-02T20:49:46Z")

</div>

But in your last post you said it was hardcoded to send telemetry to 192.168.2.1?

So i can actually change it to 192.168.1.1 and it will auto connect with qgroundcontrol?

---

<div class="post-metadata">

### 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: [December 3, 2019, 5:07pm UTC](https://discuss.bluerobotics.com/t/no-connection-to-qgroundcontrol-after-changing-rpi-ip-address/6426/6 "2019-12-03T17:07:59Z")

</div>

The ROV computer is configured to send telemetry to 192.168.1.2 by default. It is possible to change it as described above, but we do not support any other configuration at this time.

DHCP mode will be included in a later release.

---

<div class="post-metadata">

### 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: [December 3, 2019, 5:08pm UTC](https://discuss.bluerobotics.com/t/no-connection-to-qgroundcontrol-after-changing-rpi-ip-address/6426/7 "2019-12-03T17:08:05Z")

</div>


