You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm playing around with FX.25 on 14.105Mhz and I'm curious if it would be possible to enhance Direwolf's heard debug feature to also record which stations are heard the strongest vs. weakest? Maybe the only way to do this would be to do this via CAT control and poll the S-meter setting and do a little coordination? I have attached a hacked up shell script that polls my FT950 every 250ms using the hamlib rigctl tool which simply prints the S-meter value. Values that are say <20 are strong signals and if Direwolf would correlate to say DCD and a value decode, this could be a very nice feature.
Hey John,
I'm playing around with FX.25 on 14.105Mhz and I'm curious if it would be possible to enhance Direwolf's heard debug feature to also record which stations are heard the strongest vs. weakest? Maybe the only way to do this would be to do this via CAT control and poll the S-meter setting and do a little coordination? I have attached a hacked up shell script that polls my FT950 every 250ms using the hamlib rigctl tool which simply prints the S-meter value. Values that are say <20 are strong signals and if Direwolf would correlate to say DCD and a value decode, this could be a very nice feature.
--David
KI6ZHD
W7BMH-7 audio level = 12 [NONE] |______
[0.0] W7BMH-7>ID:B/-1 CHAT/-5 N/-7 Eugene, OR CN84ka | w7bmh.loclx.io
ERROR!!! Unknown APRS Data Type Indicator "B"
mheard_save_rf: W7BMH-7 0 - update time, was 0 hops 1800 seconds ago.
callsign cnt chan hops RF IS lat long msp
W7BMH-7 2 0 0 0:00 - - - 0
VE3VTY-1 1 0 0 0:01 - - - 0
KE0GB-7 7 0 0 0:05 - - - 0
KE0GB-1 3 0 0 0:14 - - - 0
KJ7LVZ 2 0 0 0:15 - - - 0
N0HI-7 3 0 0 0:21 - - - 0
K8ZTT 2 0 2 0:48 - - - 0
KB9KC 2 0 0 0:51 - - - 0
W1JT 1 0 0 0:54 - - - 0
AC0VC-7 1 0 0 1:05 - - - 0
2023-11-18 14:25:22.236069077-08:00 -41
2023-11-18 14:25:22.747829735-08:00 -30
2023-11-18 14:25:23.253313981-08:00 -37
2023-11-18 14:25:23.759809036-08:00 -37
2023-11-18 14:25:24.265932220-08:00 -39
2023-11-18 14:25:24.772232551-08:00 -40
2023-11-18 14:25:25.279399629-08:00 -41
2023-11-18 14:25:25.786217339-08:00 -40
2023-11-18 14:25:26.294518403-08:00 -13 <------ incoming packet: start
2023-11-18 14:25:26.802475470-08:00 -14
2023-11-18 14:25:27.308300073-08:00 -17
2023-11-18 14:25:27.815305796-08:00 -18
2023-11-18 14:25:28.322647443-08:00 -20
2023-11-18 14:25:28.829325306-08:00 -19
2023-11-18 14:25:29.335718518-08:00 -23 <---- some fade on the signal
2023-11-18 14:25:29.842711179-08:00 -24
2023-11-18 14:25:30.350211219-08:00 -25
2023-11-18 14:25:30.857201070-08:00 -18
2023-11-18 14:25:31.364396788-08:00 -13
2023-11-18 14:25:31.871117124-08:00 -18 <------ incoming packet: end
2023-11-18 14:25:32.377914203-08:00 -34
2023-11-18 14:25:32.878546572-08:00 -35
2023-11-18 14:25:33.385440354-08:00 -31
2023-11-18 14:25:33.891214219-08:00 -25
2023-11-18 14:25:34.398308079-08:00 -35
2023-11-18 14:25:34.903963349-08:00 -39
2023-11-18 14:25:35.410485628-08:00 -41
2023-11-18 14:25:35.917659793-08:00 -37
The text was updated successfully, but these errors were encountered: