I have an ArduSub system on the bench that consists of a Pi B companion linked via network cable to Windows 10 desktop PC with static IP on 192.168.2.1. I have both PixHawk 4 and Cube Orange (on mini carrier) available.
The PixHawk4 works fine, the Cube Orange does not.
The issue is that when checking the companion web interface, the Cube Orange is listed as a serial device in “Detected Devices” but no communication with QGroundControl takes place. Under “ArduSub Version” is the text “not found”.
When using the PixHawk4, I immediately get communication with QGC.
The ArduSub.com troubleshooting guide is excellent, and I have worked my way though it but no luck unfortunately.
Here is a quick summary:
Network configuration is verified. Using ping to the companion computer works fine. The web interface download and upload tests are both strong at around 95Mbps using a 4m RJ45 cable.
Firewall exceptions set up for both UDP ports (also tried disabling the firewall).
PC, companion and autopilot systems all rebooted numerous times in various sequences.
All cabling swapped out. 3 differentRaspberry Pi units tried.
QGC set to autoconnect to UDP and USB
On the system page there is a correct entry under serial devices for PixHawk4 and for Cube Orange, depending on which device is connected.
When using the terminal page to check MavProxy with the screen command, the PixHawk4 gives a sensible response but the Cube Orange gives only a blank terminal screen.
Resetting MavProxy options has no effect
I am unable to upload firmware via the web interface on either device. Both fail with “waiting for bootloader”. Both devices update with no issues when using QGC with a direct USB connection.
QGC, companion and ArduSub are all the latest ‘stable’ code versions
Have to say I am running out of ideas here. Would appreciate any help…