đź“–
Cerulean Sonar Docs
Docs DirectoryStore
DVL-75
DVL-75
  • DVL-75
  • Overview
    • General Specifications
    • General Use Cases
    • The Basic System
    • System Components
    • Comparison of Tracker 650 and DVL-75
  • Usage Considerations and Scenarios
    • General Usage
    • Scenario: GPS Emulation
    • Scenario: Holding Position
    • Scenario: Autonomous Waypoint Navigation
    • Scenario: Returning to a Series of Known Positions
    • Scenario: Returning to Home
    • Scenario: Using GPS Assist
    • Scenario: Doing Your Own Dead Reckoning
    • Additional Connection Possibilities
    • General Hints and Tips
    • Operation in a Pool
  • Using MAVLink and BlueOS for Position Hold on a BlueROV2
    • ArduPilot Parameters
    • DVL Setup for MAVlink Support
  • Using Other Than the Bottom for the DVL (Side-Tracking Capability)
    • Side-Tracking Capability Design Use-Cases
    • Side-Tracking Capability Considerations
  • Mounting the DVL Components
    • Sensor Head Typical Mounting
    • Sensor Head Side-Tracking Mounting Alignment
    • All-in-One and Most-in-One Mounting Considerations
    • Mounting the Electronics Stack
    • Mounting an Auxiliary GPS
  • Assembling the Electronics Stack
    • Cerulean 300m Electronics Enclosure Assembly
  • Inertial Measurement Unit (IMU)
    • Baseline IMU Calibrations
    • Baseline IMU Background
    • Baseline IMU Blind Initial Calibration Procedure
    • Baseline IMU Status-Assisted Initial Calibration Procedure
    • Baseline IMU Calibration for Each Mission or Each Time Power is Applied
    • Upgraded IMU Calibration for Each Mission or Each Time Power is Applied
  • Communicating with the DVL
    • Factory Defaults and Default Messages
    • The Ethernet Interface
    • Tips on How to Find the IP Address Assigned to Your Ethernet Adapter
    • The Serial Interface
    • Resetting the Communications Parameters to Factory Default
    • What Do the LEDs Mean?
    • Outgoing Message Formats, DVL to Host
      • $GPRMC: NMEA standard Recommended Minimum GPS/Transit Data
      • $DVEXT: DVL Extended Data
      • $DVPDL: DVL Position and Angle Deltas Message
      • Freeform Error and Informational messages ($DVTXT)
      • Re-Tweeted GPS Messages
      • Re-Tweeted IMU Messages (IMU Raw Data)
      • $DVKFA, $DVKFB Kalman Filter Support Messages
        • Driving your own Kalman Filter
    • Commands Accepted by the DVL
      • $GPRMC
      • SET-POSITION
      • CONFIGURATION
      • SUPPRESS-GPS
      • DECLINATION
      • SET-SPEED-OF-SOUND
      • SET-VELOCITY-ADJUSTMENT
      • SEND-GPRMC
      • SEND-DVEXT
      • SEND-DVKFA
      • SEND-DVKFB
      • SEND-FREEFORM
      • SEND-DVPDL
      • RETWEET-GPS
      • RETWEET-IMU
      • SET-SENSOR-ORIENTATION
      • GRAB-IMU-CAL
      • VOID-IMU-CAL
      • BAUD-RATE
      • IP-ADDRESS
      • HOST-ADDRESS
      • MAVLINK-ADDRESS
      • FALLBACK-ADDRESS
      • UNICAST-TO-ME
      • PAUSE
      • RESUME
      • REBOOT
    • Blue Robotics Ping360 Discovery Protocol (Ethernet Only)
    • ARP (Address Resolution Protocol)
    • DHCP (Dynamic Host Configuration Protocol)
    • Ping (Internet Control Message Protocol Ping)
    • Mechanical Drawings
      • Mounting Dimensions, Sensor Head
      • Mounting Dimensions, Electronics Stack
      • RAM Mount Adapter Plate
      • Electronics Stack Assembly Drawing
      • Mounting Bracket for 300m Electronics Enclosure
      • Mounting Bracket for Sensor Head or Electronics Enclosure, fits BlueROV2 Heavy Thruster Guard
      • Mounting Bracket for All-in-One Enclosure, fits BlueROV2 Heavy Thruster Guard
      • Mounting Dimensions, Cerulean 300m Enclosure
      • Mounting Dimensions for the Cerulean All-in-One Enclosure
      • Mounting Dimensions, Cerulean GPS
  • Electrical Drawings
    • Serial Cable Supplied with Baseline Electronics Stack
    • DVL Serial Connection Example
    • Power over Ethernet (POE) Cabling
    • Standard Ethernet Pinouts
    • Optional GPS Wiring
    • Sensor Head Wiring
    • Using External Power with Serial Cable
    • Serial to USB Interface Using Blue Robotics BLUART Board
  • CAD Models
  • Appendix – Coordinate Systems
  • Copyright
Powered by GitBook
On this page
  1. Communicating with the DVL

Tips on How to Find the IP Address Assigned to Your Ethernet Adapter

PreviousThe Ethernet InterfaceNextThe Serial Interface

Last updated 3 years ago

Refer to the figure below. On a Windows machine open a command window and type “ipconfig -all”. If you are using a Linux machine we assume you already know how to set up networks.

The program will output the status of all the attached Ethernet, WiFi, and Bluetooth adapters. We are only interested in the adapters that are attached and on an Ethernet network.

Note the adapter called “USB for DVL”. In the network properties windows I assigned it this name when I set up the adapter and its address (the default name was something like “Realtek USB Adapter”).

The IP address assigned to this adapter is 192.168.2.5 (this is the PC’s IP address, not the DVL’s IP address). In binary this looks like 11000000.10101000.00000010.00000101.The subnet mask is 255.255.252.0. In binary, this looks like 11111111.11111111.11111100.00000000. For IP addresses to be on the same subnet, anywhere there is a binary “1” in the subnet mask, the corresponding bits in the IP addresses must match. Note: if you follow the Blue Robotics directions, your PC’s address on the ROV network should be 192.168.2.2. This means my PC’s “USB for DVL” adapter and a properly-configured Blue Robotics PC are on the same subnet, and if the DVL is on its default fallback address of 192.168.2.3 it’s also on the same subnet, and if a BlueROV is assigned its default address of 192.168.2.1, it’s on the same subnet as well.

Note that the PC office network IP address is 10.0.3.108, and the office network subnet mask is 255.255.248.0. If all the devices mentioned in the previous paragraph were moved to my office network without changing any addresses, the PC could not talk to the DVL et al., nor vice versa (except for broadcast messages, which are generally sent by a PC to all its adapters, and received by all stations on a network).

Bottom line: if you are using fallback or static addresses, you want to be sure the DVL is connected to a PC Ethernet interface on the proper subnet.

If the DVL receives its address using DHCP, then the DVL address should already be on the proper subnet to talk to a PC, but may need to use a broadcast address to reach a Blue Robotics PC or ROV.

The “ping” command can be used to establish if a DVL is connected and is on a reachable subnet. The following figures show examples of the “ping” command. Linux machines have a “ping” command that works the same as the Windows “ping” for our purposes.

Using Windows Command Prompt to find Adapter IP Addresses
This ping command used the address assigned to the DVL by the DHCP process. The DVL address was found using the Blue Robotics Ping360 Ethernet discovery protocol. The ping was successful.
This ping command used the DVL static address 192.168.2.3 assigned by the user. The DVL address was found using the Blue Robotics Ping360 Ethernet discovery protocol. Even though the DVL is on the network and is successfully sending and receiving broadcast packets, the ping was unsuccessful because the domain gateway server is telling the PC the network is not reachable. Moving the DVL to a different Ethernet adapter with a static address on the same subnet as the DVL might fix this.