TheArchive/mayhem-firmware
1
0
Fork 0
mirror of https://github.com/portapack-mayhem/mayhem-firmware.git synced 2024-11-27 12:05:34 +00:00
Code Issues Packages Projects Releases Wiki Activity

Added information about scan speed

gullradriel 2023-08-14 18:45:02 +02:00
parent 9ee7cbf678
commit 9ca9cac294
1 changed files with 26 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
Recon.md

@ -255,6 +255,32 @@ If you're not having your frequencies searched in both direction, maybe you misw
Using the same input and output file is not going to pause a problem until you forgot to uncheck 'clear output at start'. Yeah, you've just clear what you wanted to scan Using the same input and output file is not going to pause a problem until you forgot to uncheck 'clear output at start'. Yeah, you've just clear what you wanted to scan
# Scan speed vs Chosen modulation mode
Detection of power level to match against the given squelch value is made at each firmware statistic updates. This determine how long we are staying on a frequency to have a corresponding squelch value.
In all AM/NFM/WFM modes, it's an average of 100ms per statistic update.
In SPEC mode, depending on the selected bandwidth, rounded to average upper nice looking value:
* 12k5 = 65 ms
* 16k = 30 ms
* 25k = 170 ms
* 50k = 300 ms
* 100k = 790 ms
* 150k = 375 ms
* 250k = 800 ms
* 500k = 800 ms
* 600k = 800 ms
* 650k = 800 ms
* 750k = 800 ms
* 1000k = 800 ms
* 1500k = 800 ms
* 2750k = 800 ms
* 2000k = 800 ms
* 2500k = 800 ms
* 2750k = 800 ms
# Power consumption # Power consumption
A continuous search of 63H41M43S was run by user @vag3d, using the default antenna. Settings were a range from 10MHz to 6GHz, WFM, 5kHz steps, 1s wait A continuous search of 63H41M43S was run by user @vag3d, using the default antenna. Settings were a range from 10MHz to 6GHz, WFM, 5kHz steps, 1s wait