📖
Cerulean Sonar Docs
Docs DirectoryStore
Ethernet ROV Locator
Ethernet ROV Locator
  • ROV Locator
  • Overview
  • General Specifications
  • Quick Start for BlueROV
  • Fundamentals Useful to System Designers
    • Sound Reflection and Absorption
    • Multipath
    • Ping Length
    • What to Do About Multipath and Other Issues
    • Clock Drift Expectations
    • Accuracy Expectations
      • Accuracy Test: Topside GPS
      • Accuracy Test: 110 Meter Slant Range
      • Accuracy Test: 295 Meter Slant Range
    • Operation in a Pool
  • Configuring the ROVLe
    • Finding the Configuration Web Page
    • Example Configuration Web Page
    • Live Status Page
    • Setting Device Type
    • Setting the Static IP Address
    • Setting the Fallback IP Address
    • Setting the MAVLink REST Server Parameters
    • Setting the Secondary (GNSS) MAVLink Interface
    • GPS/GNSS Forwarding (Re-tweeting)
    • Magnetic Declination
    • CIMU Calibration Offsets
    • Speed of Sound
    • GNSS Antenna Mounting Rotation
    • Output Messages
    • Configure Simulation
  • System Variants
  • Autosync
    • Autosync Mission Scenarios and Mission Suitability
    • Autosync Availability
    • Autosync GPS/GNSS Output
    • ROVL Channels (Autosync only; Operating Multiple Units in Proximity)
  • Communicating With the ROVL
    • Serial Parameters
    • The Ethernet Interface
      • Tips on How to Find the IP Address Assigned to Your Ethernet Adapter
      • Blue Robotics Discovery Protocol (Ethernet Only)
    • Packet Format
    • Messages from ROVL to Host
      • $USRTH Receiver-Transmitter Relative Angles Message
      • $USTLC Target Location Message
      • $USINF/$USTXT Information Message
      • $USERR Error Message
      • $USNVM Non-Volatile Memory Message
    • Messages from Host to ROVL
      • NMEA-Format Messages to Receiver
      • Valid Commands from Host to ROVL, Serial and Ethernet
      • Valid Commands from Host to ROVL, Ethernet Only
        • Command: DHCP
        • Command: FALLBACK-ADDRESS
        • Command: IP-ADDRESS
        • Command: HOST-ADDRESS
        • Command: MAVLINK-ADDRESS
        • Command: MAVLINK-AUTO-ORIGIN
        • Command: MAVLINK-SYSID
        • Command: PAUSE
        • Command: RESUME
        • Command: RETWEET-GPS
        • Command: RETWEET-GPS-ADDRESS
        • Command: RETWEET-message
        • Command: SEND-ROV-POS-TO-MAP
        • Command: SEND-TOPSIDE-TO-MAP
        • Command: SEND-USRTH
        • Command: SEND-USTLC
        • Command: UNICAST-TO-ME
  • Cerulean Inertial Measurement Unit (CIMU)
    • CIMU Calibration Background
      • CIMU Magnetometer Calibration
      • CIMU Accelerometer Calibration
      • CIMU Gyro Calibration
  • Operating and Accuracy Considerations
  • Multi-Unit Operation (Swarms)
    • Multi-Unit 1:1
    • Multi-Unit 1:2
    • Multi-Unit 2x1:1
  • ROVL Mounting
    • ROV/Deepside Mounting
    • Topside Mounting
    • Simple Topside Deployment Fixture
  • ROVL Wiring
    • Standard Cabling Options
    • ROVL-e PC Board Internal Connections
      • JST-GH Connector Pin 1 Identification
      • Ethernet/Power Connections
      • Serial Connection
      • USB Connection
      • GNSS Compass Main (4-pin) RS-232 Connection
      • GNSS Compass RTK (2-pin) RS-422 Connection
    • Electrical Noise
  • Connecting and Powering Your ROVLe Ethernet Receiver or Transceiver
    • Example Power Injectors
    • Data Connection
    • Example Power/Wi-Fi Setup for Remote Usage
    • Battery
  • Mounting Dimensions
    • Mk II Receiver with Omnitrack Top
    • Transmitter/Transceiver/Receiver with Standard Top
    • Mk III Transcceiver
    • ROVLe Omnitrack Top
    • ROVLe Standard Top
    • Example Mounting Scheme with 3D-Printed Bracket
  • ROVL Coordinate Systems and Angles
    • Definitions
    • NED or "Compass" vs. ENU or "Math" Angles
    • Math to Compass Frame Conversions
    • Transducer Down Orientation
    • Transducer Up Orientation
    • Receiver/Transceiver Orientation Frames
    • Best Operating Envelope
  • Appendix: Math for Computing Remote Latitude/Longitude
    • Receiver & GPS at Topside and Transmitter Deepside
    • Transmitter & GPS Topside and Receiver Deepside
  • Appendix: Factory Usage Command Set
  • Troubleshooting
    • How to Tell if Your Mk II Receiver is Working
    • How to tell if your Mk II Transmitter is working
    • What to do when you find an unresolvable problem when troubleshooting
  • Copyright
Powered by GitBook
On this page
  1. Autosync

Autosync Mission Scenarios and Mission Suitability

PreviousAutosyncNextAutosync Availability

Autosync works by exposing the Receiver and Transmitter to GPS or GNSS signals at the start of the mission, and optionally at intervals during the mission. This exposure sets the timebase of the Receiver or Transmitter to match GPS time. Satellite acquisition normally occurs within 30 seconds of powerup. In the canonical case of an ROVL Receiver sited near the ROV operator and an ROVL Transmitter mounted on the ROV, the satellite acquisition will normally occur in the background while the ROV is being readied for launch and while the ROVL Receiver IMU calibration is being done.

  • The Receiver must be out of the water (or at the surface) and in view of satellites at the start of the mission. This is often the time when IMU calibration maneuvers are being done, so you may not ever find this to be a constraint. Once satellites are acquired, the Receiver can be put into the water. You can tell when satellites are acquired and the Receiver is ready to submerge in one of two ways: (1) monitor the $USRTH message, and when the Last Sync field is no longer “-1”, satellites have been acquired; (2) If using the CeruleanTracker application, a status indicator will show on the dashboard tab of the main window, and the $USRTH window will show the value of the Last Sync field. It’s a good idea to give the unit about 10 seconds after satellite acquisition before submerging it so the GPS can stabilize.

  • The Transmitter must be out of the water (or at the surface) and in view of satellites at the start of the mission. Once satellites are acquired, the Transmitter can be submerged. You can tell if the Transmitter has a satellite lock because the Transmitter will not start transmitting until satellites are acquired. You can hear the Transmitter click once per second and feel the ping impulse if you put your hand on the Transmitter. It’s a good idea to give the unit about 10 seconds after it starts clicking before submerging it so the GPS can stabilize.

  • Transmitter and Receiver satellite acquisition can be done independently, i.e., they do not have to happen at exactly the same time, nor in the same location. Either unit can be reset or power-cycled during the mission, and after satellites are acquired again, the system will resume at full accuracy.

  • Once submerged, satellite lock will be lost almost immediately, and the Receiver and Transmitter will each start using their internal timebase to calculate the distance between units. The internal timebase is not as stable as the satellite atomic clocks and thus will immediately begin to drift. Drift will result in a growing error in the calculation of slant range between units (just like in systems without autosync). The error will typically accumulate at roughly 0.5 meter (often less) of slant range error per hour out of satellite lock. See for an example of clock drift.

  • At any time during the mission, either the Transmitter or Receiver can be surfaced to reset the internal timebase back to GPS time. Satellite re-acquisition usually takes less than 15 seconds. Resetting only one of the two partially but not completely will reduce the total error in slant range. Resetting both is required to return the accuracy to the best possible. It is not necessary to reset both at exactly the same time, but as with the initial sync, each internal timebase will begin to drift immediately after loss of satellite lock.

In non-canonical applications, if it is not possible to surface both the Receiver and Transmitter at the start of a mission and/or every couple of hours during a mission, the autosync option may not be suitable for your application, and a Mk III unit should be used.

here