Updated Home (markdown)

Home.md

@@ -72,3 +72,26 @@ A new window will pop up with the signal parameters.  From top to bottom:
 - `Initial Byte Offset`: `0`
 - `Sample Rate`: Change to `Custom` and enter the sample rate (in Hz) of your collected file (mine was 30720000)
 - `Channels`: `2` and check both `Quadrature` and `Flip Complex`
+- `Decode Format`: This will depend on how you collected the signal.  If you used `osmocom_fft` or my graph example then this will be `32-bit float`.  If you used the HackRF command line tool, then this might be `8-bit linear (signed)`.  Otherwise it's going to be `16-bit linear` as that's really the only other common sample size.  Do not change the endianness unless you really know what you're doing!
+- `Normalization`: `auto measure`
+
+![image](https://user-images.githubusercontent.com/4240543/162874818-bd2bff86-7b69-4d3a-8352-926743adf5cb.png)
+
+Click on `Open` and the popup should go away and the main window should update with something similar to the following
+
+![image](https://user-images.githubusercontent.com/4240543/162874903-0db9ffc1-a9d4-40ff-bdd4-56ae3aa2fa26.png)
+
+The first thing to do is fix the FFT size.  Right click in the main window, select `Processing` -> `Transform Size`, and select `4096`.  Dropping the FFT size is fine now that the file is loaded.  Any size over 4096 usually results in having to scroll left and right to see the full bandwidth.
+
+![image](https://user-images.githubusercontent.com/4240543/162875065-580cfee6-144d-4b11-b055-8dcb8ac972a4.png)
+
+In my case the collect was long enough that `baudline` didn't show my anything useful at first.  This happend because `baudline` zooms you all they way out at first.  So you're seeing the entire collect in one window.  To zoom in press `alt` and scroll forward with the mouse wheel (might be the `windows` key for some window managers).  You should hopefully see something like this after scrolling and zooming around
+
+![image](https://user-images.githubusercontent.com/4240543/162875284-d4eb7a59-13a9-4897-b422-b10aae43e600.png)
+
+That is a DroneID burst!  
+
+The important information that we need now is when does the burst start, and how long does it stay active.  Handily, `baudline` gives us tools for doing just that.  Right click in the main window and select `measure` -> `system` and select `delta selected`, then go to the same menu again and select `cursor time`.  
+
+By default the windows might be absolutely tiny.  If they are, click on one of them and press the up arrow until they are the correct size
+![image](https://user-images.githubusercontent.com/4240543/162875585-14dcbacd-0f9b-4de2-8af9-28892c2a4c13.png)