Here’s a look at the other info area from the tether diagnostics extension:
Thanks for the tip about iperf3, I will give that a try when I have a chance.
Hi @rperkins -
The Outland system uses a slightly newer homeplug module - it is cool to see that the extension works with it and reports the higher bandwidth capacity! The bandwidth graph looks ok, but the second plot normally has the right side lower - I’ll ask internally to see what may be indicated by yours.
On the newest versions of BlueOS, you can right click the bar at the top and also add a real time network traffic indicator (alongside CPU and disk, which have been available for some time.)
iperf is definitely the way to go when diagnosing bandwidth capacity - the BlueOS metrics are generally good enough just to see that things are working nominally.
The outland system should deliver 1 or 1.6 kW (depending on revision), but the voltage drop does begin early. At 100% gain in water, does QGround Control (or the latest versions of Cockpit) report instantaneous power results that you would expect when trying to maximize consumption?
1 Like
Interesting about the different homeplug in the OTPS, that might explain things.
The most instantaneous power I ever see is around 600 watts, typically more like 540. That would be when combining lateral and vertical movements. Typically when just powering ahead with full throttle at 100% gain (pulling on a clump weight and a bunch of tether) I’ll see something like 380 watts. By my seat-of-the-pants gauge I would say those power levels match up pretty well with my previous battery-only experience.
Hi @rperkins -
The supply can only provide as much is demanded! A heavy configuration BlueROV2 should have no trouble pulling a kW or more… What is the power consumption reported by the vehicle when idle?
Power at idle (with sonar on but not transmitting) is 16 watts. That’s the same as when using batteries.
Voltage shows as 13.6. I thought it was supposed to be 15?
Hi Richard -
From the sound of it, you don’t have your PSM parameters configured correctly. The system only consumes 5-8 watts at idle…
You can double check with a multimeter what the voltage in the ROV actually is, and then use the powerswitch calibration extension to get the most accurate results - or set the parameters as detailed here.
Does this look right? I don’t see an option for the R2 power sense module here.
Hi @rperkins -
Can you check what value you have for the parameters (my values are shown)
BATT_AMP_OFFSET: 0.33
BATT_VOLT_MULT: 11
BATT_AMP_PERVLT: 37.88
My params are the same as yours.
Anecdotally, I’ve noticed that power saver settings can really mess with responsiveness of both USB and networking devices.
I would see if Allow the computer to turn off this device to save power is on for your network adapter and, if it is, turn it off.
2 Likes
Thanks Dan, I just took a look there and that option was checked so I unchecked it, will see what happens!
1 Like
Verified 13.7 volts at idle on the distribution bars inside the enclosure with a voltmeter.
Did that help with the network speeds?
1 Like
Not that I know of. It turns out our big problem was our old friend Windows firewall. Apparently Microsoft changed something recently regarding wired network connections-- it treats them as “public”, i.e. untrustworthy, and doesn’t give you an option to change them to “private”. This involves much stricter firewall rules which played havoc with our comms. If you try to turn the firewall off entirely Windows has a way of turning it back on, and if you use clever commands with PowerShell to reset the connections to “private” it has a way of resetting them back to “public”, so vigilance is your best friend here.
3 Likes
@rperkins we’ve seen this on a few different computers. Getting windows to keep a network adaptor as ‘private’ is a pain at times. We have a powershell script on hand on the desktop (assumes you have certain admin rights to run it). It does seem to revert back semi-randomly!
I’ll repost our script when I’m back on a machine with it to hand. But basic commands are:
get-netconnectionprofile
This lists network adaptors, note name of adaptor that is your FXTI box
Then run:
set-netconnectionprofile -name “Unidentified network” -networkcategory private
But replace ‘Unidentified network’ with correct name of adaptor.
Hope this helps others.
1 Like
Sorry Tony… Could you please explain to me why version QGC 4.2.8 is recommended? I know that newest version is 4.4.2. I have it on my ROV. Would I still be better off with v.4.2.8? I’m trying my best to keep my ROV as failsafe as possible without updating software or what is newest.
Hi @diveexplorer -
Blue Robotics ceased testing QGC after version 4.2.8, and focused instead on Cockpit development. Newer versions may work, but in my experience, eliminate menus (Camera in particular) that can make it a bit of a pain to work with. It is annoying to get the update QGC prompt when using 4.2.8, but all other functionality is stable!
1 Like
Super Tony. Thanks for explaining.