[HamWAN PSDR] HamWAN client testing

[Kyle Burgess]

Good to know.  I guess I will take the Westin coordinates out of the
pointer then.  Capitol Park was my next guess beings it would have been
somewhat in-line.  But, when I pointed it to that site, it definitely
couldn't hear it.

Based on that log, we were obviously communication with Paine.  Is it
possible we could have been picking up a reflection of the signal from
Paine somehow (bouncing off a building, etc)?  The pointer is GPS enabled,
so it should have been quite accurate with its heading; especially after I
re-ran the calibration.  It has always been dead-on in the past, so that's
why I question the reflection idea.  I tested it a few days prior at
another location, which connected to Paine with great accuracy.

Thanks for the confirmation.

Kyle

On Sat, Aug 11, 2018 at 4:23 PM Tom Hayward <tom at tomh.us> wrote:

> On Sat, Aug 11, 2018 at 4:09 PM Kyle Burgess <kd7iyt at gmail.com> wrote:
>
>> Thanks, Tom.  I'll keep that in mind for the next go-around.  Here is the
>> MAC we were using during the test: 4C:5E:0C:31:C4:43
>>
>> It was acting like we were making a connection to the Westin, based on
>> the coordinates that were dialed in.  I really wasn't expecting anything
>> from that direction.  However, it would be cool to verify if it truly was
>> the Westin that we were passing traffic through.  The best RSSI we saw was
>> right around 75.
>>
>
> There are no HamWAN sectors installed at the Westin, so you would not have
> been able to accidentally connect to it.
>
> Here's what I found for that MAC in the log. Looks like you were able to
> connect to SnoDEM-S1.
>
> 5,1,Aug 10 19:15:39,ether1.snodem-s1.hamwan.net,44.24.240.131,wireless,info,
> 4C:5E:0C:31:C4:43 at wlan1: connected, signal strength -84
> 5,1,Aug 10 19:15:41,ether1.snodem-s1.hamwan.net,44.24.240.131,dhcp,info,
> dhcp1 assigned 44.24.240.155 to 4C:5E:0C:31:C4:43
> 5,1,Aug 10 19:16:00,ether1.snodem-s1.hamwan.net,44.24.240.131,wireless,info,
> 4C:5E:0C:31:C4:43 at wlan1: disconnected, control frame timeout
> 5,1,Aug 10 19:16:32,ether1.snodem-s1.hamwan.net,44.24.240.131,wireless,info,
> 4C:5E:0C:31:C4:43 at wlan1: connected, signal strength -84
> 5,1,Aug 10 19:17:47,ether1.snodem-s1.hamwan.net,44.24.240.131,wireless,info,
> 4C:5E:0C:31:C4:43 at wlan1: disconnected, control frame timeout
> 5,1,Aug 10 19:18:04,ether1.snodem-s1.hamwan.net,44.24.240.131,wireless,info,
> 4C:5E:0C:31:C4:43 at wlan1: connected, signal strength -82
> 5,1,Aug 10 19:28:27,ether1.snodem-s1.hamwan.net,44.24.240.131,wireless,info,
> 4C:5E:0C:31:C4:43 at wlan1: disconnected, control frame timeout
> 5,1,Aug 10 19:28:41,ether1.snodem-s1.hamwan.net,44.24.240.131,wireless,info,
> 4C:5E:0C:31:C4:43 at wlan1: connected, signal strength -84
> 5,1,Aug 10 19:28:54,ether1.snodem-s1.hamwan.net,44.24.240.131,wireless,info,
> 4C:5E:0C:31:C4:43 at wlan1: disconnected, control frame timeout
> 5,1,Aug 10 19:32:26,ether1.snodem-s1.hamwan.net,44.24.240.131,wireless,info,
> 4C:5E:0C:31:C4:43 at wlan1: connected, signal strength -84
> 5,1,Aug 10 19:36:00,ether1.snodem-s1.hamwan.net,44.24.240.131,wireless,info,
> 4C:5E:0C:31:C4:43 at wlan1: disconnected, control frame timeout
> 5,1,Aug 10 20:32:26,ether1.snodem-s1.hamwan.net,44.24.240.131,dhcp,info,
> dhcp1 deassigned 44.24.240.155 from 4C:5E:0C:31:C4:43
>
> Tom
> _______________________________________________
> PSDR mailing list
> PSDR at hamwan.org
> http://mail.hamwan.net/mailman/listinfo/psdr
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.hamwan.net/pipermail/psdr/attachments/20180811/be0ee4a2/attachment.html>