# No telemetry or command input problem **URL:** \ **Category:** Blue Robotics Software\ **Created:** [January 29, 2021, 2:03pm UTC](https://discuss.bluerobotics.com/t/no-telemetry-or-command-input-problem/8983 "2021-01-29T14:03:21Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![Garch](https://avatars.discourse-cdn.com/v4/letter/g/e9a140/32.png) [@Garch](https://discuss.bluerobotics.com/u/Garch)\ **Post date:** [January 29, 2021, 2:03pm UTC](https://discuss.bluerobotics.com/t/no-telemetry-or-command-input-problem/8983/1 "2021-01-29T14:03:21Z")
In Q Ground Control we have video but no telemetry and cannot input any commands to our BlueROV2. The message ‘Waiting for Vehicle Connection’ is displayed. Under the Companion Computer Setup System tab, Pixhawk 1 is a detected serial device and Mavproxy is an active service. Companion software version is 0.0.25. Under Pixhawk Firmware update, ArduSub version says ‘not found’. We have followed the ArduSub troubleshooting guide for No Telemetry (No Autopilot Connection). Working down the list to Check Mavproxy, we have logged into the Companion Computer via web terminal and entered the screen -r mavproxy command. The following message is displayed. Can you help? ![Mavproxy](https://us1.discourse-cdn.com/flex019/uploads/bluerobotics/original/2X/2/285b0a27960530cfd7ee09cc25c226e3c6483843.jpeg) ---
**Author:** ![williangalvani](https://avatars.discourse-cdn.com/v4/letter/w/6f9a4e/32.png) [@williangalvani](https://discuss.bluerobotics.com/u/williangalvani)\ **Post date:** [January 29, 2021, 3:16pm UTC](https://discuss.bluerobotics.com/t/no-telemetry-or-command-input-problem/8983/2 "2021-01-29T15:16:11Z")
Hi @Garch , Try going to [http://192.168.2.2/mavproxy](http://192.168.2.2/mavproxy) and restore the [MAVProxy](http://www.ardusub.com/reference/companion/mavproxy.html) settings to default. ---
**Author:** ![Garch](https://avatars.discourse-cdn.com/v4/letter/g/e9a140/32.png) [@Garch](https://discuss.bluerobotics.com/u/Garch)\ **Post date:** [January 29, 2021, 3:43pm UTC](https://discuss.bluerobotics.com/t/no-telemetry-or-command-input-problem/8983/3 "2021-01-29T15:43:46Z")
Thanks Willian Ardusub version now shows as 4.0.2 and I have telemetry. **However** , I cannot arm the vehicle or input commands through our Logitech controller (set to X). The attached error message appears in Q Ground Cont ![Screen_cap](https://us1.discourse-cdn.com/flex019/uploads/bluerobotics/original/2X/5/5185c74cb3fb2e0702893ae4bd821dccff5aaa98.jpeg) rol. Any solution please? ---
**Author:** ![williangalvani](https://avatars.discourse-cdn.com/v4/letter/w/6f9a4e/32.png) [@williangalvani](https://discuss.bluerobotics.com/u/williangalvani)\ **Post date:** [January 29, 2021, 3:48pm UTC](https://discuss.bluerobotics.com/t/no-telemetry-or-command-input-problem/8983/4 "2021-01-29T15:48:39Z")
This usually means that the vehicle is not getting your messages, but you are receiving the vehicles’. What do your network settings look like? Make sure that the [network settings are correct](http://www.ardusub.com/quick-start/installing-companion.html#network-setup) (especially that your netmask is exactly `255.255.255.0`). ---
**Author:** ![Garch](https://avatars.discourse-cdn.com/v4/letter/g/e9a140/32.png) [@Garch](https://discuss.bluerobotics.com/u/Garch)\ **Post date:** [January 29, 2021, 3:53pm UTC](https://discuss.bluerobotics.com/t/no-telemetry-or-command-input-problem/8983/5 "2021-01-29T15:53:58Z")
Hi Willian, Yes, settings are good. See attached. Firewall is set to allow Q Ground Control. Graham ![IP4](https://us1.discourse-cdn.com/flex019/uploads/bluerobotics/original/2X/2/2f4702a09e26d729c592b51884b54a0b6c0c48d7.jpeg) ---
**Author:** ![williangalvani](https://avatars.discourse-cdn.com/v4/letter/w/6f9a4e/32.png) [@williangalvani](https://discuss.bluerobotics.com/u/williangalvani)\ **Post date:** [January 29, 2021, 4:05pm UTC](https://discuss.bluerobotics.com/t/no-telemetry-or-command-input-problem/8983/6 "2021-01-29T16:05:09Z")
I usually have this happen to me when I have the same IP on two different networks and my OS picks the wrong one to send data out of. I also notice you are using and older QGC version, but that **should** not cause this. ---
**Author:** ![Garch](https://avatars.discourse-cdn.com/v4/letter/g/e9a140/32.png) [@Garch](https://discuss.bluerobotics.com/u/Garch)\ **Post date:** [January 29, 2021, 4:05pm UTC](https://discuss.bluerobotics.com/t/no-telemetry-or-command-input-problem/8983/7 "2021-01-29T16:05:53Z")
Having rebooted the ROV and surface computer, I am getting this message: ![new message](https://us1.discourse-cdn.com/flex019/uploads/bluerobotics/original/2X/1/1ad3914c022c6e6be3f09a28ea7386c23008a66d.jpeg) ---
**Author:** ![Garch](https://avatars.discourse-cdn.com/v4/letter/g/e9a140/32.png) [@Garch](https://discuss.bluerobotics.com/u/Garch)\ **Post date:** [January 29, 2021, 4:07pm UTC](https://discuss.bluerobotics.com/t/no-telemetry-or-command-input-problem/8983/8 "2021-01-29T16:07:33Z")
We have a Ping 360 set to 192.168.2.2 ---
**Author:** ![williangalvani](https://avatars.discourse-cdn.com/v4/letter/w/6f9a4e/32.png) [@williangalvani](https://discuss.bluerobotics.com/u/williangalvani)\ **Post date:** [January 29, 2021, 4:21pm UTC](https://discuss.bluerobotics.com/t/no-telemetry-or-command-input-problem/8983/9 "2021-01-29T16:21:23Z")
> [@Garch](#): > > Ping 360 set to 192.168.2.2 I would use something else. That is also likely to cause some conflicts (you request params to 192.168.2.2 and the request goes to the ping360 instead of rov)