From 75e5d2b8c32a1b3b584e8007b795fee55163a433 Mon Sep 17 00:00:00 2001
From: Athanasios Pantazides
 <46729485+thanasipantazides@users.noreply.github.com>
Date: Tue, 3 Dec 2024 09:10:23 -0600
Subject: [PATCH] Update README.md

---
 README.md | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/README.md b/README.md
index ea09ed8..9615f8b 100644
--- a/README.md
+++ b/README.md
@@ -234,9 +234,10 @@ On startup, this `Listener` application creates a set of log file at this locati
 Additionally, an ASCII-formatted file called `catch.log` is produced to log any received packets that can't be parsed into a system-specific file. Each entry in this file is newline-separated, and tagged at the start of the file with an offset timestamp from the creation time of the file.
 
 ## Common issues
-1. If you run the formatter software, kill it, then try to run it immediately again, you will get an error containing `connect: Address already in use`. This is because the kernel retains control of TCP sockets for a while (~1 minute) after you close them to allow any messages still on the wire to come through. Just wait a moment and try running again. Of course, it is possible (depending on your configuration) that another process on the same machine actually is using the IP address you want as well.
-2. Unix time resets to a similar value on every reboot. Do not trust any timestamps you get out of this software.
-3. If you never clear the `~/foxsi-4matter/log/` folder, you can completely fill the disk and get a read-only filesystem. Then you will need to edit `fstab` manually and with a racing heart  while the whole flare campaign waits for you. This happened at PFRR during the FOXSI-4 launch campaign. 
+1. In a typical lab or flight setup, physical connections, GSE computer network configuration, and `systems.json` mismatch cause far more problems than the code internals. If you're having issues, verify your connections with simple tests before you try anything else. Check if everything is plugged in, and your GSE machine shows Ethernets are "connected." Check if you can `ping` from the GSE to the Formatter. Check in Wireshark if you get packets from the Formatter to the right IP address. 
+3. If you run the formatter software, kill it, then try to run it immediately again, you will get an error containing `connect: Address already in use`. This is because the kernel retains control of TCP sockets for a while (~1 minute) after you close them to allow any messages still on the wire to come through. Just wait a moment and try running again. Of course, it is possible (depending on your configuration) that another process on the same machine actually is using the IP address you want as well.
+4. Unix time resets to a similar value on every reboot. Do not trust any timestamps you get out of this software.
+5. If you never clear the `~/foxsi-4matter/log/` folder, you can completely fill the disk and get a read-only filesystem. Then you will need to edit `fstab` manually and with a racing heart  while the whole flare campaign waits for you. This happened at PFRR during the FOXSI-4 launch campaign. 
 
 ## Documentation
 If you enjoyed this measly little README, you're going to *love* the rest of the documentation! You can view these docs in a web browser (they are HTML), and until they are hosted somewhere, you will need these instructions to build them: