diff options
| -rw-r--r-- | 11.-Kraken-Pro-Cloud-Mapper.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/11.-Kraken-Pro-Cloud-Mapper.md b/11.-Kraken-Pro-Cloud-Mapper.md index 8af6ae5..87abb9c 100644 --- a/11.-Kraken-Pro-Cloud-Mapper.md +++ b/11.-Kraken-Pro-Cloud-Mapper.md @@ -32,7 +32,7 @@ To use the live bearing plotting features of the software you will need to add y Enter the serial number of the KrakenSDR (don't forget the space), give it an easy to remember name (perhaps based on location), and enter a default frequency. -The decay time setting defines how long data from this KrakenSDR will contribute to the heatmap. Generally this could be anywhere from 10 to 120 seconds. Larger decay times result in more averaging over the grid space, and are useful if locating fixed stationary transmitters. Lower decay times result in more noise, but are required for moving transmitters. If your KrakenSDR is on a moving platform like a car, unless the TX is moving quickly, you probably want to set the decay time much larger (for example 30-60 minutes), as then you do not want to lose the older data from points collected over time. +The decay time setting defines how long data from this KrakenSDR will contribute to the heatmap. Generally this could be anywhere from 10 to 120 seconds. Larger decay times result in more averaging over the grid space, and are useful if locating fixed stationary transmitters. Lower decay times result in more noise, but are required for moving transmitters. If your KrakenSDR is on a moving platform like a car, unless the TX is moving quickly, you probably want to set the decay time much larger (for example 30-60 minutes / 1800-3600 seconds), as then you do not want to lose the older data from points collected over time. Once you have the details entered, click `Create Station`. |