[HamWAN PSDR] Beacon Tower-Capital Park Backbone Link

Thu Mar 29 18:30:45 PDT 2018

Ok, I will just get off the list.  I have the over 60 since the 24th, you may not call that a lot of email, I consider that to be a lot so best I just leave.  Thank you.

From: PSDR <psdr-bounces at hamwan.org> On Behalf Of Rob Salsgiver
Sent: Thursday, March 29, 2018 6:23 PM
To: 'Puget Sound Data Ring' <psdr at hamwan.org>
Subject: Re: [HamWAN PSDR] Beacon Tower-Capital Park Backbone Link

Randy,

I’m not sure what you’ve been receiving as far as “hundreds” of PSDR emails, but I went back and counted 67 since March 21st.  I may have deleted a few instead of having them auto-file into my folder, but prior to that my HamWAN folder shows that in order to get to the next 67 emails, I had to go back almost into November 2017.

The topics covered in the last week were essentially 4 items:

1.	Voting on power equipment for the Gold Mountain site
2.	Elections and voting
3.	Outage issues
4.	The current Beacon/Capital Park link discussion

I can understand the frustration with too much email, but I don’t see the same thing hitting my inbox.  Each of the topics above is exactly the type of traffic the list has been meant to carry.  Yes the traffic could be split up, but then you are asking to maintain 1,2,3 or more lists with essentially the same people to split up 150 emails since last November.  

I seldom have anything of value to contribute to a lot of discussions and when I can I put what traffic I can directly to individuals to help minimize list traffic (as I try to do in all lists I follow), but sometimes it just has to happen.

Given the level of involvement you have in EMCOMM and other aspects suggested in your signature, I would hope that you stay in touch with the list.  There is a lot that HamWAN technologies can do to help you in your role as EC in serving your Served Agencies if you have the time and personal bandwidth to stay in touch with developments.

If need be, you may see if your email client will automatically “file” the HamWAN list into a separate folder from your inbox.  That way you can read up when you have the time without it “cluttering” up your inbox.

73

Rob Salsgiver – NR3O

Past EC (and a bunch of other stuff) – Snohomish County

From: PSDR [mailto:psdr-bounces at hamwan.org] On Behalf Of runamuk52 at gmail.com <mailto:runamuk52 at gmail.com> 
Sent: Thursday, March 29, 2018 5:56 PM
To: 'Puget Sound Data Ring'
Subject: Re: [HamWAN PSDR] Beacon Tower-Capital Park Backbone Link

Maybe it is just me, but over the past week I have gotten hundreds of emails from PSDR.  Now I understand everyone has an opinion on almost everything, but is there not a way that say, those who can vote, have a different place to vote, those with technical issues have their group, and then a general group for those of us who don’t have interest in every fight or vote or whatever is going on?  I am trying to learn about HamWan and keeping up with where it is and where it is going, but have no interest in this kind of stuff.  Guess it is time to get off the group list entirely if this keeps up.

Randy Thomas - K7RHT

Kittitas County Ares EC

Kittitas County SAR-Comms

Auxcomm

MARS

206-255-9510 Cell

206-418-6541 Vonage

Skype = Runamuk52

Ellensburg Repeaters:

K7RHT repeater on 147.000 + offset 131.8 tone (Linked)

K7RHT repeater on 444.450 + offset 131.8 tone (linked)

K7RHT mobile repeater 145.29 - offset 131.8 tone (emcomm)

KC7DRA DMR repeater 440.925 + offset

From: PSDR <psdr-bounces at hamwan.org <mailto:psdr-bounces at hamwan.org> > On Behalf Of Rob Salsgiver
Sent: Thursday, March 29, 2018 5:51 PM
To: 'Puget Sound Data Ring' <psdr at hamwan.org <mailto:psdr at hamwan.org> >
Subject: Re: [HamWAN PSDR] Beacon Tower-Capital Park Backbone Link

If we’re looking at “experimenting” rather than jumping ship on standards at the moment, is there value in configuring two separate links at the same locations to compare/contrast with weather differences, etc – as well as find out any “cohabitation” problems between 2 or 3 frequency sets?  Obviously cost may be an issue, but if we have access and cooperative environments for both ends at the moment, why not learn as much as we can?

Just a thought.

Cheers,

Rob Salsgiver – NR3O

From: PSDR [mailto:psdr-bounces at hamwan.org] On Behalf Of Darcy Buskermolen
Sent: Thursday, March 29, 2018 5:45 PM
To: Puget Sound Data Ring
Subject: Re: [HamWAN PSDR] Beacon Tower-Capital Park Backbone Link

Although for my day job I represent a specific hardware vendor, from a services standpoint we will weploy multi vendor if it's the right tool for the job.  What we do is try to limit the number of ad hoc differences.  So I'd definitely be in support with the idea of using the 3.4 or 10 as a pure bridge. That way most of the skill/knowledge for the hard bits (ie layer 3) is still microtik centric.

On Thu, Mar 29, 2018, 17:38 Kenny Richards, <richark at gmail.com <mailto:richark at gmail.com> > wrote:

Another possible benefit, if we figure out how to make the 3.4Ghz solution work between Beacon/CP, is it could be re-used between CP and Queen Anne. 

I totally understand Bart's point, having common standards is important and has benefits. I think what Doug is suggesting is that maybe this is a case where we need a new standard. We have hit a situation that the old approaches are not working, so lets look for a new one.

On Thu, Mar 29, 2018 at 5:33 PM, Doug Kingston <dpk at randomnotes.org <mailto:dpk at randomnotes.org> > wrote:

First, about access:  ACS has full access, round the clcck to Beacon and Capitol Park limited only by our COMT's (Mark, Carl, Doug, Randy, Casey) availability.  Bringing third parties requires about a week to establish a training mission number.  If we can do the work ourselves, then only our schedules are factors.

Thank you Nigel for your detailed response on the reuse point.  I am guessing from this that there is no objection in principle to trying to put this link in place.  We just need to fine the most compatible and affordable solution.  Randy has started researching this but we should double down on this.

-Doug-

On Thu, Mar 29, 2018 at 5:21 PM, Bart Kus <me at bartk.us <mailto:me at bartk.us> > wrote:

Well, since you asked "why not":

One of the advantages we've found with keeping things on a compatible band is the ad-hoc ability to link dishes to sectors during emergencies, or use dishes and sectors for spectral analysis on the one common band.

Another advantage is the uniformity of config / interface / automation by using the same vendor.  Don't need to train folks on special procedures or write exceptions into automation.

--Bart

On 3/29/2018 4:45 PM, Bryan Fields wrote:

On 3/29/18 7:38 PM, Doug Kingston wrote:

For example... Can we reuse a PtoP 5GHz frequency with high isolation (shielding)?

Why not use 3.4 GHz UBNT radios?  We have a link here in Tampa at 16.2 miles
across Tampa Bay running at 130 Mbit/s.

3.37 to 3.5 GHz (the frequency range of the M3 radios) is totally unused for
the most part.  A complete link is well under $1000 including antennas.

_______________________________________________
PSDR mailing list
PSDR at hamwan.org <mailto:PSDR at hamwan.org> 
http://mail.hamwan.net/mailman/listinfo/psdr

_______________________________________________
PSDR mailing list
PSDR at hamwan.org <mailto:PSDR at hamwan.org> 
http://mail.hamwan.net/mailman/listinfo/psdr

_______________________________________________
PSDR mailing list
PSDR at hamwan.org <mailto: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/20180329/3d5e8e39/attachment-0001.html>