I have been trying to connect my BlueROV2 to my Ubuntu, but the Qgroundcontrol keeps showing ‘waiting for vehicle connection’
I have connected this BlueROV2 to a Windows system, the connection was good, and the I could control the thruster by programming. I believe the ROV is not broken.
Can you confirm that you have Pixhawk Autopilot as one of the detected serial devices in the companion web interface System page, and that mavproxy appears in the Active Services section on the same page? Would be good if you can provide a screenshot of the companion computer’s mavproxy screen session as outlined in the Check MAVProxy section of the troubleshooting page. If that’s all good then I’d suggest trying the Reset MavProxy Options instructions just underneath the Check MAVProxy section.
Note that the troubleshooting link you provided is to an old version of that page with some incorrect links in it - my link is to the new one. Not sure what the deal is there, and I’m chasing that up internally at the moment to try to find out why we have two versions of the same page. Same applies to the installation page you linked to. Out of interest, did you reach those pages directly through a search, or from somewhere else?
Those first two screenshots are of the “Network” page rather than the “System” page (you can change page with the buttons at the top, or by changing the url), but given the mavproxy setup is displaying, and the web terminal screen session is showing a connection then I’m assuming the Pixhawk Autopilot will be showing up as a serial device, and the mavproxy service will exist too.
Your screenshots show that you’re on companion version 0.0.17, but the latest one is 0.0.26. Can you please go through our Software Setup guide and make sure you’ve done all the steps? Hopefully once you’re through the Update Software section your connection issues should be sorted out
Ok cool, thanks for the info. There are apparently some old versions of pages left from a major website structure change a while ago, which I’m now in the process of sorting out. The troubleshooting page you linked to now redirects automatically to the new one
My laptop has dual systems, the connection is good in the Windows system, but not here in the Linux, could it because of something related to the dual systems?
Hi Brandon, that seems mostly fine to me, although the Pixhawk seems to be showing up as fmuv2 in the Serial Devices instead of as Pixhawk Autopilot.
I haven’t had this issue before, so I’ve asked our software team in case they have any additional information or suggestions. They or I will get back to you soon
Hi @Brandonyxf, a few more questions/things to try:
do you have any kind of firewall running on your ubuntu machine? They don’t tend to be enabled by default, but if you’ve put one there/enabled one it could be blocking access to the UDP connections for your mavlink and video data
if you run QGroundControl from the command-line are there any errors that come up?
can you try installing QGroundControl from the official QGC instructions? It will get you to install gstreamer, and the version of QGC will be 4.1 instead of our currently recommended 4.0.5, but it may work.
Once gstreamer is installed you can try running the command gst-launch-1.0 videotestsrc ! autovideosink to confirm that it’s working (it should open a rainbow window with some flickering white noise. If that works correctly then please try to run gst-launch-1.0 udpsrc port=5600 ! application/x-rtp, payload=96 ! rtpjitterbuffer ! rtph264depay ! h264parse ! avdec_h264 ! autovideosink to see if gstreamer can find the udp stream for your video. If that works then I expect QGC will as well, but see how you go.
your Active Services don’t seem to show that a ping device is connected (if you had a Ping1D connected it would show up as pingmav and pingproxy). The udp ‘detection’ you saw in PingViewer is just the default IP address, so it likely isn’t actually detecting udp at all. If you manually connect to a potential ping connection the PingViewer will sometimes continue to display it as an option in the connection manager even if it never successfully connected, so that likely doesn’t provide any extra information.
