Are there any tips for minimizing the time it takes for the DVL A50 to “wake up” after connecting the battery?
We experience very long delays at times. Does shutting down the ROV rather than just pulling the battery matter, in terms of processes next time it boots? (For the DVL or for ROV reboot generally). Is there any trigger to cause it to connect? Can we diagnose what we’re waiting for (eg. DVL boot vs comms with ROV).
Thanks,
-Scott
Hi @ScottM -
How you shut down the system will not affect the time for things to start up.
How long are you waiting for the DVL? Are you waiting for it to start up with the vehicle already in the water?
DVL takes 6 minutes to boot.
We have two ROVs each with a DVL, both similar times.
Not in water.
Hi Scott -
That does seem a bit long. The DVL may be looking for an IP address before settling on the fall-back, static IP of 192.168.2.3. You could try enabling the DHCP server BlueOS can provide.
Or verify that the DVL static IP address has been set.
I just booted my ROV and the dvl was detected as soon as BlueOS finished booting (1~2min). I do have a DHCP server on that network (but not on the rov, not sure if that matters).
I have DHCP on in BlueOS.
I generally connect to the DVL independently through a separate browser window addressed to the DVLs assigned IP 192.168.2.117 for one , and 2.165 for the other.
The wait time is the same using the BlueOS DVL extension.
