Mark, If you were previously seeing signals in the -91 sort of range, you were on the hairy edge of seeing anything at all. Below around -90 you’re unlikely to see anything or get any sort of connection. If you do, you’re lucky. The weather and many other things impact the signal a bit. We usually see winter signals be a couple dB higher than summer. So, I think it’s entirely likely that if you were previously seeing signals down that low, that the conditions are just a little different and there’s not enough there. Nigel
On Aug 29, 2018, at 22:31, David Haworth via PSDR <psdr@hamwan.org> wrote:
Hi Mark,
When I configured the QRT 5 International this month. Only three amateur radio frequencies are scanned: 5.880, 5.9 and 5.92.
In WinBox terminal command /interface wireless monitor 0 will show the frequencies and bandwidth being scanned if no radio is found.
If a radio is found you will see the details like
[admin@WA9ONY-LARCH] > /interface wireless monitor 0 status: connected-to-ess channel: 5880/5/an wireless-protocol: nv2 tx-rate: 1.6Mbps-5MHz/1S rx-rate: 1.6Mbps-5MHz/1S ssid: HamWAN bssid: 64:D1:54:6A:64:26 radio-name: S3.Larch/K7WAN signal-strength: -68dBm signal-strength-ch0: -72dBm signal-strength-ch1: -71dBm tx-signal-strength: -70dBm tx-signal-strength-ch0: -72dBm tx-signal-strength-ch1: -73dBm noise-floor: -125dBm signal-to-noise: 57dB tx-ccq: 6% rx-ccq: 6% authenticated-clients: 1 current-distance: 22 wds-link: no bridge: no routeros-version: 6.42.3 current-tx-powers: 6Mbps:27(27/30),9Mbps:27(27/30),12Mbps:27(27/30),18Mbps:27(27/30),24Mbps:27(27/30), 36Mbps:27(27/30),48Mbps:25(25/28),54Mbps:24(24/27),HT20-0:27(27/30),HT20-1:27(27/30), HT20-2:27(27/30),HT20-3:27(27/30),HT20-4:27(27/30),HT20-5:27(27/30),HT20-6:25(25/28), HT20-7:23(23/26) notify-external-fdb: no 73 David Haworth http://www.stargazing.net/david/sdr/HamWAN.html <http://www.stargazing.net/david/sdr/HamWAN.html>
On Aug 29, 2018, at 10:21 PM, Mark Weisenfeld <mark@weisenfelds.com <mailto:mark@weisenfelds.com>> wrote:
I have this 25/27 dB MikroTik LHG XL HP5 device that I can move around Tumwater (south Olympia) and measure the signal from Capitol Peak at various places at around 10 miles. The last two nights I have reset and completely reconfigured the device and I still cannot register any signal from Capitol Peak in several locations.
After I do a reset, and before I reconfigure the routerOS, I see that it scans all the regular 802.11 channels and registers a whole list of local APs. Then I go on to finish inputting all the settings and it becomes silent. I can't get a single 5.8 Ghz signal to show up from several locations around my local area.
So has something changed? Do I need to apply some other setting? Did HAMWAN suddenly change all their frequencies? (smirk) Is Capitol Peak asleep? (smirk²)
I could assume that somehow my device has crapped out, after less than a year an no real usage, ever. I used to get -91dB and similar from scanning at my home and at the local DEM, but now nothing. It shows all 6 channels enabled, but a scan shows nothing.
Is there a way to test this thing? Could I enter an additional standard USA 5Ghz channel and see my own 5Ghz wireless show up?
Thanks y'all.
****************************************** Mark Weisenfeld K7TUM CN87na <http://www.levinecentral.com/ham/grid_square.php?Grid=CN87na> (SW corner) ************************** _______________________________________________ PSDR mailing list PSDR@hamwan.org <mailto:PSDR@hamwan.org> http://mail.hamwan.net/mailman/listinfo/psdr
_______________________________________________ PSDR mailing list PSDR@hamwan.org http://mail.hamwan.net/mailman/listinfo/psdr