📖
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 GPS/GNSS Output

A Transmitter with autosync installed will automatically forward (“re-tweet”) all GPS/GNSS sentences from the GNSS receiver to the main interface. Thus, it can be simultaneously used as a GPS unit on the ROV. Due to this feature, Transmitters with autosync default to 9600 baud (Obsolete Mk II non-autosync transmitters default to 115,200 baud). This is to better emulate a GPS receiver. Mk III transponders are always set to 115,200 baud since they cannot have an autosync option installed.

Most users don't bother to connect the transmitter or transponder serial input and output to anything as the system will work fine without looking at the transmitter/transponder data. Using the GPS/GNSS re-tweet would be one exception to this rule.

A Receiver with autosync installed can be commanded to forward all GPS/GNSS sentences from the GNSS receiver to the main interface (see “V3” and “V0” commands). Since the receiver must be submerged in normal operation (and thus the GPS lock is lost during operation), we do not provide a method for using the ROVL RX GNSS as a substitute for a topside GPS.

The forwarded/re-tweeted GPS sentences from the ROVL units may include:

$GPGSA and/or $GNGSA - GPS dilution of position and active satellites

$GPGSV - Number of SVs in view, PRN, elevation, azimuth, and SNR

$GPVTG and/or $GNVTG - Actual track made good and speed over ground

$GPGGA and/or $GNGGA - Time, position, and fix related data

$GPGLL and/or $GNGLL - Position data: position fix, time of position fix, and status

$GPTXT - Free text, manufacturer defined

$GPRMC and/or $GNRMC - Minimum recommended Position, Velocity, and Time

PreviousAutosync AvailabilityNextROVL Channels (Autosync only; Operating Multiple Units in Proximity)

Last updated 1 month ago