We started up our bot after about a couple of months, and we had to update QGC and after multiple firmware updates, the bot is only recognized when the PixHawk is hardwired to the computer. Any suggestions on how to set up the Ethernet connection? We tried to change the IP address. We can provide more details if needed. Thank you!
We tried everything on the troubleshooting guide. Nothing has worked so far.
Can you specify:
- Top computer operating system (e.g. windows, linux, macOS)
- Assuming you’re using a companion computer, does video streaming appear in QGC?
- Does the weblink work? http://192.168.2.2:2770/system
We’re using Windows, and nothing shows up in QGC currently, we only see a Waiting for Vehicle Connection. The weblink works, meaning that the ethernet cable is good to go and the Pixhawk is connecting to the computer, but QGC is not recognizing the connection.
Please go through the troubleshooting steps here and let us know:
Hi, I’m with Spruha. We are running Windows, we are using a companion computer that is successfully streaming video feed, and the weblink does work (caveat is that it shows “not found” for ardusub version), When we connect everything on the ROV directly to the computer, it works, however when we use the companion computer it does not. Do you know anything we can do to fix this? We are only allowed to use hard wired connections, so no wifi control.
Alright, so it seems like your issue is that the pixhawk isn’t connecting correctly to the companion computer. Does anything come up in the “Detected Devices” section of the system page of the weblink? There should be something like “FT231X_USB_UART”, as in the example on the page that @williangalvani linked to earlier.
If that is there then see if you can run a pixhawk firmware update by updating to the latest stable version. If it’s not there then the companion computer isn’t detecting the pixhawk at all, in which case you’ll want to check that it’s plugged in correctly, make sure it beeps when powered on (it should make a low tone followed by a high tone, like “booop-beeep”), and see if you can update the companion software (also from the system page of the weblink) in case that helps.
From what I recall, we were unable to see anything in the “Detected Devices” section of the weblink. Assuming this does not appear, the beep pattern you mention happens every time we power it on. I will try to update the software on Thursday and will let you know if anything happens. The firmware is updated to the latest version, but we may need to update the companion computer software. I will let you know on Thursday.