[HamWAN PSDR] SnoDEM (Paine) is well-connected again

[Dean Gibson AE7Q]

Yes, I have the July 10 eMail, but I got the impression from the eMail 
that the temporary change for a day or two, so I did nothing, as I was 
busy with other matters.

On 2015-10-16 01:56, Bart Kus wrote:
> Well, July is about when we installed the ETiger-SnoDEM link.  We 
> reconfigured your sector (S2) for the purpose and sent you a notice on 
> July 10th.  :)  Your sector returned to normal service on Oct 7th.  It 
> was a really ugly hack to keep SnoDEM connected to the network.
>
> Did you ever try the config change I sent you to try and stay 
> connected to the sector at its new temporary frequency & bandwidth?
>
> --Bart
>
> On 10/16/2015 12:34 AM, Dean Gibson AE7Q wrote:
>> OK, I wondered what happened. Did you work on the sector antennas?
>>
>> As you know (but for lurkers), when I installed my HamWAN node in 
>> March 2014, I had a good connection until late July, whereupon it 
>> went to zero. At first I thought that this was due to foliage, but 
>> when it came back in February 2015, I attributed it to the a huge 
>> water tower in the path, and whether it was full of water or not.
>>
>> On schedule, I lost my connection again this July, and have been 
>> resigned to not getting it back until early next year, so I haven't 
>> been checking it every day.
>>
>> Today I have a solid connection. Not a great connection, but a lot 
>> better than zero.
>>
>> On 2015-10-16 00:23, Bart Kus wrote:
>>> Hi All,
>>>
>>> Nigel and I did a trip today to SnoDEM to re-align a couple of the 
>>> dishes.  We've got nice strong signals now from East Tiger and 
>>> Haystack going to SnoDEM.  After Saturday's Gold Mtn deploy we'll 
>>> need to take 1 more trip to align a SnoDEM dish to aim back @ Gold 
>>> Mtn.  This should make SnoDEM triple redundant, which is great for 
>>> an EOC.  Things got super sketchy there for a while, as multiple 
>>> events coincided to wreak havoc on SnoDEM's connectivity:
>>>
>>> 1) Nigel moved and his uplink was disconnected as a result.
>>> 2) The CapitolPark-SnoDEM link faded into the useless signal range. 
>>> We disabled it since it could hardly pass any packets.
>>> 3) A modem died @ Haystack which killed the SnoDEM feed from there.
>>> 4) My uplink to SnoDEM got tree-faded into uselessness and was 
>>> disabled.
>>>
>>> And that's how a quad-redundant site suddenly became a disconnected 
>>> site!
>>>
>>> --Bart
>>