📖
Cerulean Sonar Docs
Docs DirectoryStore
ROV Locator
ROV Locator
  • ROV Locator
  • Overview
  • General Specifications Mk II
  • General Specifications Mk III
  • System Variants
  • 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
  • Autosync Option (Mk II Only)
    • Autosync Mission Scenarios and Mission Suitability
    • Autosync Availability
    • Autosync GPS/GNSS Output
  • ROVL Channels (Autosync only; Operating Multiple Units in Proximity)
  • 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
  • Communicating With the ROVL
    • Serial Parameters
    • Packet Format
    • Messages from ROVL to Host
      • $USRTH Receiver-Transmitter Relative Angles Message
      • $USINF Information Message
      • $USERR Error Message
    • Messages from Host to ROVL
      • NMEA-Format Messages to Receiver
      • Valid Commands from Host to ROVL
  • Inertial Measurement Unit (IMU)
    • How To Tell Which IMU is Active
    • Mk II IMU Modes and Calibration
      • Mk II IMU Calibration Background
      • Mk II IMU Calibration General Procedures
    • 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
    • Multi-Unit n:1 (fixed transmitter)
    • Multi-Unit n:1 (mobile transmitter)
  • ROVL Mounting and Wiring
    • ROV/Deepside Mounting
    • Topside Mounting
    • Simple Topside Deployment Fixture
    • Wiring Notes
    • Electrical Noise
    • USB Interface using Blue Robotics BLUART Board
  • Mechanical Drawings
    • Mounting Footprint and Envelope, "S" Package
    • Mounting Footprint ("P" Package Mk II and Mk III)
    • Envelope Drawing. "P" Package ROVL Mk II Transmitter and Receiver, Mk III Transponder
  • 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. Communicating With the ROVL

Packet Format

The units send data using an ASCII packet compatible with NMEA-0183 sentence format. All transmitter/transponder messages can be ignored (you don’t need to bother to connect the serial wires to the transmitter/transponder unless you are updating firmware). The NMEA sentence device type is "US". The message format is:

$USxxx, … *hh

Where:

‘xxx’ is message type ID

… is/are variable comma-separated data fields per command

*hh is an asterisk followed by a NMEA-compatible hex checksum

All packets end in ASCII return/linefeed (0x0D, 0x0A)

Fields within a message may be “empty” as noted in the message description, and “empty” means there is a comma for the field but no characters in the field. For example, the message below has an empty field between the fields containing “FIELD1” and the field containing “FIELD3”.

$USTXT,FIELD1,,FIELD3*2A

Possible messages are:

$USRTH – receiver-transmitter relative angles and range

$USINF – informational message

$USERR – error message

$USDEB – developer debug message

$Gxyyy – GPS or GNSS retweeted messages, where 'x' is either 'P" or 'N'.

Beta releases may send other data formats for developer use. Some oddball messages may be provided for specific customer usage. Any message not beginning with ‘$’ may be safely ignored.

PreviousSerial ParametersNextMessages from ROVL to Host

Last updated 6 months ago