5 files changed, 40 insertions, 4 deletions
diff --git a/02.-Direction-Finding-Quickstart-Guide.md b/02.-Direction-Finding-Quickstart-Guide.md
index 794da21..5dc26bc 100644
--- a/02.-Direction-Finding-Quickstart-Guide.md
+++ b/02.-Direction-Finding-Quickstart-Guide.md
@@ -54,7 +54,7 @@ The image below explains how the antennas should be mounted. Make sure the array
 
 The next step is to burn the KrakenSDR Direction Finding (DF) image to an SD Card. For the Pi 4 image you will need an 8GB or larger card, and for the Pi5 and OPI5B images you will need a 16GB or larger card. We also recommend using class 10 or faster to ensure no file system slowdowns.
 
-1. Using a PC, download the “Etcher” software from [balena.io/etcher](https://www.balena.io/etcher/). 
+1. Using a PC, download the “Etcher” software from [balena.io/etcher](https://www.balena.io/etcher/). NOTE: Do not use the Raspberry Pi imager software to burn the SD card, and do not customize the login details, as the code relies on the username being kept as the default "krakenrf".
 2. Download the latest KrakenSDR image zip file for your Pi 4, Pi 5 or Orange Pi 5B from the SD card folder linked above.
 3. Use [Balena Etcher](https://www.balena.io/etcher/) to burn the image onto the SD Card. Using Etcher you can burn directly from the ZIP file. (There was a report that Etcher does not properly work on MacOS, MacOS users can try [Raspberry Pi's Imager](https://www.raspberrypi.com/software) instead)
 4. Insert the card into your Raspberry Pi 4.
diff --git a/05.-KrakenSDR-Web-Interface-Controls.md b/05.-KrakenSDR-Web-Interface-Controls.md
index e7aeb24..781adcc 100644
--- a/05.-KrakenSDR-Web-Interface-Controls.md
+++ b/05.-KrakenSDR-Web-Interface-Controls.md
@@ -323,7 +323,7 @@ This provides an option to calibrate the full system by compensating for phase d
 
 `explicit-time-delay` - If you've measure time delay with a VNA you can input the time differences in nanoseconds here. Please note the differences must be measured relative to channel 0. 
 
-`touchtone` - You can output .s1p files from your VNA for the 5 coax cables in your system, and copy them to the _calibration folder. Name them as cable_ch0.s1p, cable_ch1.s1p and so on for each of your five cables used in the system. You need to ensure that the touchstone file covers the frequency range that you will be using.
+`touchtone` - You can output S21 or S12 .s1p files from your VNA for the 5 coax cables in your system, and copy them to the _calibration folder. Name them as cable_ch0.s1p, cable_ch1.s1p and so on for each of your five cables used in the system. You need to ensure that the touchstone file covers the frequency range that you will be using. Note that this will only work as long as the phase compensation does not wrap - e.g. make sure that the cables you are calibrating have length differences much less than the frequency wavelength you are working with.
 
 **IQ Adjust Amplitude**
 
diff --git a/07.-KrakenSDR-Troubleshooting.md b/07.-KrakenSDR-Troubleshooting.md
index 75ae9ee..5e6d223 100644
--- a/07.-KrakenSDR-Troubleshooting.md
+++ b/07.-KrakenSDR-Troubleshooting.md
@@ -43,7 +43,11 @@ Alternatively, just connect an HDMI screen and keyboard, and the terminal will a
 ### View and Enable Logging
 If you have installed the software from scratch, and suspect some issue with missing packages or similar you can enable error logging to try and diagnose the problem. Edit the daq_chain_config.ini text file with `nano ~/krakensdr_doa/heimdall_daq_fw/Firmware/daq_chain_config.ini`, and change `log_level = 2`. Log files will be written to `krakensdr_doa/heimdall_daq_fw/Firmware/logs`.
 
-Also, you can enable logging on the DOA DSP software by editing the settings.json text file `nano ~/krakensdr_doa/krakensdr_doa/settings.json` and setting `logging_level = 2`. The DOA DSP logs will be written to `~/krakensdr_doa/krakensdr_doa/_share/logs/krakensdr_doa/ui.log`.
+Also, you can enable logging on the DOA DSP software by editing the settings.json text file `nano ~/krakensdr_doa/krakensdr_doa/settings.json` and setting `logging_level = 2`. 
+
+The DOA DSP logs will be written to `~/krakensdr_doa/krakensdr_doa/_share/logs/krakensdr_doa/ui.log`.
+
+The Heimdall DAQ log files will be written to `~/krakensdr_doa/heimdall_daq_fw/Firmware/_logs`
 
 Remember to turn logging off again by setting the logging levels to 5 after the issue is fixed, to avoid a large log file growing on the SD card.
 
@@ -52,6 +56,12 @@ Here we will confirm that all the tuners in the KrakenSDR system are seen by the
 
 Connect an HDMI monitor and keyboard, or SSH into the terminal as shown above.
 
+If you are using one of our ready-to-use images, be sure to stop the KrakenSDR software first by running the following commands.
+
+```
+cd krakensdr_doa
+./kraken_doa_stop.sh
+```
 In a terminal window run “kraken_test -d0” (NOTE: Older image files will use "rtl_test -d0"). You should see a message like the following.
 
 ```
@@ -82,6 +92,13 @@ If all the tuners showed similar messages, then we have confirmed that all the t
 ## Power Supply Test
 Remember that the KrakenSDR **must** be powered with a 5V/2.4A+ capable external power supply. No power is provided over the USB data port.
 
+If you are using one of our ready-to-use images, be sure to stop the KrakenSDR software first by running the following commands.
+
+```
+cd krakensdr_doa
+./kraken_doa_stop.sh
+```
+
 Open four terminals, and in each individual terminal run kraken_test for an individual tuner. (NOTE: In older images use rtl_test instead of kraken_test if kraken_test is missing)
 
 `kraken_test -d0`
diff --git a/11.-Kraken-Pro-Cloud-Mapper.md b/11.-Kraken-Pro-Cloud-Mapper.md
index 3e89b48..4ef3f8c 100644
--- a/11.-Kraken-Pro-Cloud-Mapper.md
+++ b/11.-Kraken-Pro-Cloud-Mapper.md
@@ -24,7 +24,7 @@ At least two and ideally three or more KrakenSDRs spread out over some distance
 
 Kraken Pro Cloud can be accessed by browsing to https://map.krakenrf.com. To sign up you will need to enter your email address and have the serial number of any KrakenSDR that you own. This is the 8 to 12-digit number printed under the CE/FCC/UKCA/NoBinning logos on the front-right of the device.
 
-**KerberosSDR Owners:** KerberosSDR owners are also welcome to use this software. However as the KerberosSDR does not have a serial number, please email us at thekraken@krakenrf.com with proof of ownership details. Be it a photo of the KerberosSDR with the current date, or an invoice. We will generate a serial number for you.
+**KerberosSDR Owners:**  KerberosSDR owners are also welcome to use this software. However as the KerberosSDR does not have a serial number, please email us at thekraken@krakenrf.com with proof of purchase details. We will then generate a serial number for you.
 
 Once logged in your will be presented with a map and control sidebar.
 
diff --git a/12.-Appendix.md b/12.-Appendix.md
index 5402dfd..135c798 100644
--- a/12.-Appendix.md
+++ b/12.-Appendix.md
@@ -35,6 +35,25 @@ network={
 ```
 Then Press “CTRL+X”, “Y” to close and save the file. Now when you reboot the Pi 4 should automatically connect to your network.
 
+On the Pi 5 simply use the network manager GUI in the desktop OS to change WiFi credential information.
+
+## Editing the Mobile Hotspot Connection Credentials
+On the Pi 4 image, to change the details of the mobile hotspot that the KrakenSDR will automatically connect to, edit wpa_supplicant.conf
+
+`sudo nano /etc/wpa_supplicant/wpa_supplicant.conf`
+
+change the SSID and psk password of the "KrakenAndroid" entry to your preferred credentials.
+
+On the Orange Pi 5 and Raspberry Pi 5, simply use the built-in network manager GUI as part of the OS.
+
+## Editing the Default Raspberry Pi 4 Hotspot Credentials
+
+```
+cd Autohotspot
+sudo ./autohotspot-setup.sh
+```
+Select option 7 and follow the instructions.
+
 ## Port Forwarding
 If you wish to make your KrakenSDR remotely accessible over the internet you will need to set your router to forward ports 8080 for the web interface, and port 8081 for the data output for external apps.