From a57de0e5b46addf45eeead0ec558732a3683c358 Mon Sep 17 00:00:00 2001 From: Lewie Date: Sat, 18 May 2024 02:57:27 -0400 Subject: [PATCH] Update README.md Clikcing --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 820aa15..673646d 100644 --- a/README.md +++ b/README.md @@ -27,7 +27,7 @@ Its going to be noisy. The louder the better. If you don't want noise, you are in luck. As you are running one device, you can send the signal directly to the analyzer in its purest form. Make sure the `Output` is set to Analyser. If you want to experience the audio and the errors often related to demodulating the signal, switch over to Speakers and check the Microphones "Listen" checkbox. The progess bar will show both yellow and red colors. Red indicates the percent of packets that failed while yellow are successful. If packets have failed after the signal stops, the packet numbers will be listed in the `Packet Errors`. You may click the "Request" button to send only those packets. The order does not matter. If a packet is out of range, the sender will continue to send all other valid packets. -Being that you are both the sender and receiver, you have the option to use Automatic Repeat Request. If there are any packet errors after a signal completes, then the process of clicking "Request" will be automated repeatedly until the signal compeletes. Clikcing "Stop" in the `Message` area will not stop the automated process. You'll need to click `Manual Repeat Request` to prevent it from continuing. +Being that you are both the sender and receiver, you have the option to use Automatic Repeat Request. If there are any packet errors after a signal completes, then the process of clicking "Request" will be automated repeatedly until the signal compeletes. Clicking "Stop" in the `Message` area will not stop the automated process. You'll need to click `Manual Repeat Request` to prevent it from continuing. Under `Message`, you see an option to `Send First Packet Twice`. I often found that the first packet failed to transfer. Since the first packet containes the data length header, it is fairly important that it comes through so that we can see a progress bar and discard packets that are out of range - even if the crc passes. The failing first packet is really annoying when `Automatic Repeate Request` gets into an endless loop trying to request a single packet. The quick fix was to just send the first packet twice. I suspect the issue is with the first sample period.