Differences

This shows you the differences between two versions of the page.

--- ee:hydrophones:start [2018/01/28 11:03]
Ryan Summers
+++ ee:hydrophones:start [2018/01/28 15:41]
Ryan Summers
@@ Line 4: / Line 4: @@
 ===== Introduction =====
-//Note: The purpose of this page is to describe how the arrival times are acquired on a number of hydrophone channels. This documentation does //not// describe how that information is turned into bearings or how it is used in localization.//
+//Note: The purpose of this page is to describe how the arrival times are acquired on a number of hydrophone channels. Documentation describing how that information is turned into a pinger bearing is found [[cs:hydrophones:pinger_bearing:start|here]].//
@@ Line 11: / Line 11: @@
 {{https://media.giphy.com/media/VVPKOXc6aY1Lq/source.gif}}
-Further simplifications can be applied to the problem as well. By ensuring that the hydrophones are close enough, it can be guaranteed that the arrival time difference will never exceed one half wavelength. Therefore, the cross correlation only needs to be completed within +/- half a wavelength. The signals occur at a maximum frequency of approximately 40KHz, which means that the arrival time difference can never exceed approximately 12.5 microseconds. This means that the hydrophones must be spaced within 1.8cm of each other due to the speed of sound in water.
+Further simplifications can be applied to the problem as well. By ensuring that the hydrophones are close enough, it can be guaranteed that the arrival time difference will never exceed one half wavelength (the signals are sinusoidal with a maximum frequency of 40KHz). The cross correlation now only needs to be completed within +/- half a wavelength (which increases accuracy and decreases required processing). This means that the arrival time difference can never exceed approximately 12.5 microseconds. Because the speed of sound in water is 1498 m/s, the hydrophones must be spaced within 1.8cm of each other.
-Now that the theoretical aspects are out of the way, the foundation of the problem starts to take shape.
+To calculate a cross correlation, set time delays of [-12.5, 12.5] microseconds on the signal and calculate the overlapping area for each time delay. Calculating overlap is done by multiplying the value of the origin hydrophone at a time step by the value of the shifted hydrophone function at the same time step and summing up all multiplied values. When both are positive or negative, a point constructively adds to the correlation. When the signs don't match on the points, the correlation decreases. When both signals are identical, the correlation is maximal.
-) Acquire signals on all four hydrophones (one reference and 3 along each X, Y, and Z axis)
-) Cross-correlate the X, Y, and Z axis signals against the reference to calculate time of flight delay.
-The cross correlation step is simple mathematics. Note that cross-correlation boils down to multiplying individual points of two signals together and accumulating, so if the signals are big it can take quite a bit of time. We will discuss how to handle this later.
+==== Summary ====
+Now that the theoretical aspects are out of the way, the foundation of the problem starts to take shape.
-The main difficulty exists in sampling the signals. It is important that samples are taken simultaneously on each of the hydrophones and that the signals are sampled fast enough to ensure that the precision in time of flight is accurate enough (for example, at a sampling frequency of 1MHz, the time of arrival can never be more precise than a signal microsecond). Therefore, the system must be capable of simultaneously sampling four channels at a minimum rate of 1MHz.
+  - Acquire signals on all four hydrophones (one reference and 3 along each X, Y, and Z axis)
+  - Cross-correlate the X, Y, and Z axis signals against the reference to calculate time of flight delay.
+The main difficulty exists in sampling the signals. It is important that samples are taken simultaneously on each of the hydrophones and that the signals are sampled fast enough to ensure that the precision is accurate enough (for example, at a sampling frequency of 1MHz, the time of arrival can never be more precise than a single microsecond). Therefore, the system must be capable of simultaneously sampling four channels at a minimum rate of 1MHz.
@@ Line 29: / Line 30: @@
 ==== Code ====
-All software and firmware is available in [[https://github.com/PalouseRobosub/hydro-zynq|the GitHub repository]]. There are two primary directories: hardware and software. The hardware folder contains all the Verilog and TCL files for interracting with Vivado. TCL scripts have been generated to rebuild the block design in vivado, and a README.txt file in proj/ describes how to use them. Additionally, the IO constraints file is provided for the current hardware.
+All software and firmware is available in [[https://github.com/PalouseRobosub/hydro-zynq|the GitHub repository]]. There are two primary directories, ''%%hardware/%%'' and ''%%software/%%''. The ''%%hardware/%%'' folder contains all the Verilog and TCL files for interacting with Vivado. TCL scripts have been generated to rebuild the block design in [[https://www.xilinx.com/products/design-tools/vivado.html|Vivado]], and a ''%%README.txt%%'' file in ''%%proj/%%'' describes how to use them. Additionally, the IO constraints file is provided for the current hardware.
-The software folder contains all C source code used in programming the HydroZynq. An ELF file can be created by using the `mk` script supplied with the source file name.
+The software folder contains all C source code used in programming the HydroZynq. An ELF file can be created by using the ''%%mk%%'' script supplied with the source file name.
 Example:
   ./mk app/main_bin.c
-All files located in src/ will be compiled against the application specified to generate the binary. Finally, a BOOT.bin file (binary image that is used for booting off the SD cared) can be created through the utilization of the 'doit' script.
+All files located in ''%%src/%%'' will be compiled against the application specified to generate the binary. Finally, a ''%%BOOT.bin%%'' file (binary image that is used for booting off the SD cared) can be created through the utilization of the ''%%doit%%'' script.
 Example:
   ./doit app/main_bin.c bit/adc_dma_revb.bit
-This will automatically mount and copy over the BOOT.bin to the card for the HydroZynq. This script takes in the source file name of the main application as the first argument and the bit stream file as the second parameter.
+This will automatically mount and copy over ''%%BOOT.bin%%'' to an SD card for the HydroZynq. This script takes in the source file name of the main application as the first argument and the bit stream file as the second parameter.
-**The current firmware utilizes software/bit/adc_dma_revb.bit as the bitstream file.**
+//The current firmware utilizes **software/bit/adc_dma_revb.bit** as the bitstream file.//
 ==== Programming & Debugging ====
-Programming and debugging can be completed through creation of new BOOT.bin files on the SD card, but this is often extremely inefficient. The [[https://store.digilentinc.com/jtag-hs3-programming-cable/|Digilent HS3]] can be used as a JTAG access point for GDB debug interfaces. To interact with the HydroZynq through JTAG, use the `xmd` command (provided by Xilinx).
+Programming and debugging can be completed through creation of a new ''%%BOOT.bin%%'' on the SD card, but this is often inefficient. The [[https://store.digilentinc.com/jtag-hs3-programming-cable/|Digilent HS3]] can be used as a JTAG access point for GDB debug interfaces. To interact with the HydroZynq through JTAG, use the ''%%xmd%%'' command (provided by the Xilinx Vivado tool suite).
 After executing xmd from the command line, you will enter a shell-like environment. To connect to the ARM core for programming, enter:
   > connect arm hw
-Once connected, if you desired to program the FPGA or the ARM, first stop the ARM CPU.
+Once connected, if you desired to program the FPGA or the ARM, stop the ARM CPU:
   > stop
-To program a new bitstream,
+To program a new bitstream:
   > fpga -f [bitstream_file_path]
-To load a new ELF onto the CPU,
+To load a new ELF onto the CPU:
   > dow [elf_file_path]
-Finally, the CPU can be restarted,
+Finally, the CPU can be restarted:
   > run
-Once XMD has been started, a remote GDB server is automatically instantiated. To connect to the GDB server, simply use the debug.sh script located in `software/` to launch up a GDB session.
+Once XMD has been started, a remote GDB server is automatically instantiated. To connect to the GDB server, use the ''%%software/debug.sh%%'' script to launch up a GDB session.
   [hydrozynq-repo-path]/software/debug.sh
 ==== Communication ====
-The HydroZynq communicates primarily through UDP. A number of user scripts have been created in the `scripts/` folder for ease of use with UDP. For example, the stdout of the application is sent to Cobalt's UDP port 3000 (e.g. 192.168.0.2:3000). A simple python application ([hydrozynq-repo-path]/scripts.debug_stream.py) can be used to view the standard output of the application (e.g. dbprintf() statements).
+The HydroZynq communicates through UDP. A number of user scripts have been created in the ''%%scripts/%%'' folder for ease of use with UDP. For example, the stdout of the application is sent to Cobalt's UDP port 3004 (e.g. 192.168.0.2:3004). A simple python application ([hydrozynq-repo-path]/scripts.debug_stream.py) can be used to view the standard output of the application (such as dbprintf() statements).
 === Port Descriptions ===
@@ Line 78: / Line 79: @@
 | 3004        | Cobalt      | Debug/STDOUT port                 |
-Note that the HydroZynq does not run ROS natively, so python scripts running on cobalt are necessary for interfacing the HydroZynq with ROS. As of now, these scripts are still under initial development.
+Note that the HydroZynq does not run ROS natively, so python scripts running on cobalt are necessary for interfacing the HydroZynq with ROS. As of now, these scripts are still under development.
-The HydroZynq currently sends out all data used in the cross-correlation and the results of the final cross-correlation. These can be visualized using python and MatPlotLib through the scripts made available:
+The HydroZynq currently sends out all samples used in the cross correlation and the results of the final cross-correlation. These can be visualized using python and MatPlotLib through the scripts made available here:
   python [hydrozynq-repo-path]/scripts/data_receiver.py
@@ Line 86: / Line 87: @@
 The data and correlation results are sent using a trivial packet format:
-<packet_number as unsigned, little-endian 4-byte integer> <Sample 1> ... <Sample N>
+{{ :ee:hydrophones:wavedrom.png |Packet Formats}}
-Data results contain 4 channels per Sample, where each channel is a 16-bit unsigned integer (little-endian) value. (E.g. each sample is 64 bits and has 4 values).
+All data is little-endian integers. Bit sizes are shown in parentheses. Data packets send the raw ADC reading for each point and correlation packets send the correlation function values for each time shift calculated.
-Correlation results contain 3 channels per Sample, where each channel is a 4-byte integer (little-endian) value. The first sample is the correlation between Channel 1 and reference, teh second is between Channel 2 and reference, and the last is between Channel 3 and reference.
+The HydroZynq also allows for run-time parameters to be set dynamically, including the ping detection threshold. These can be sent to the HydroZynq command port in a simple ASCII string.
-The HydroZynq allows for a number of run-time parameters to be set dynamically, including the ping detection threshold. These can be sent to the HydroZynq command port in a simple ASCII string.
   [keyword]:[value],[keyword]:[value],.... (etc)
+Examples:
+  threshold:500,debug:1
+  reset:1
 Note that the string must terminate without a trailing comma and that it is able to only have a single key-value pair. The current supported keys are as follows:

User Tools

Differences

Page Tools

Palouse RoboSub Technical Documentation

Site Tools