FAQs – KYPN’s Stance on the Winlink vs NYU-Rappaport Clusterfudge

December 19, 2019

Ah, the Winlink versus NYU-Rappaport clusterfudge in progress. My, my, oh my what a mess the kids have made with this one.

I think G8BPQ summed up the core issue very well here:

“This is not an issue with Pactor but with FBB compression, which has been around on packet as well as pactor for over 25 years. To use it as an excuse to ban Pactor is laughable.”  John Wiseman, G8BPQ

Yeah, that John, the guy that rarely publicly comments on such things. I think I saw where even Phil Karn (KA9Q) voiced his concerns over this silliness.

 

For those asking “what if” the FCC does this or that with this Rappaport vs Winlink mess?

There are some good folks involved with Winlink. Unfortunately Winlink leadership and some of it’s HF gateway operators (and some users) have been their own worst enemy. As such many of us really struggle to feel sorry for them.

Ted Rappaport is definitely Winlink’s worst nightmare come true and a large flock of their chickens have come home to roost. That said, we are gravely concerned for all the collateral damage Ted’s poorly chosen approach here may bring to large swaths of the digital side of the hobby.

There used to be this well founded old ham wisdom about “Police ourselves, work together to solve our problems, and think twice before asking the FCC for their opinion.” Why? It has this nasty way of coming back to bite us all in our backsides.

While I’m sympathetic to some of Ted’s concerns, others are just off the charts ridiculous. Even worse it opened the doors to some more perpetually miserable, easily offended, and overly entitled kids wanting to get in on the dramafest.  Wow, all over core problems that could of been solved with some HF bandplan tweaks, Winlink leadership not ignoring ongoing complaints, Winlink HF gateways being A LOT more considerate in frequency choices, and better enforcement against flagrant abuses of our spectrum using the existing rules.

Given the spread of lack of personal responsibility and perpetual adolescence across our society today, I’m not surprised by this mess at all. Even more sadly, I suspect this is just the first legal battle on this topic. Something tells me Ted and crew are not going to give up if they don’t get the ruling they want this time around. Especially if it’s true what some think is actually driving this. All as we head into a new decade full of increasing threats to our spectrum from commercial interests that would love to see our ranks distracted and divided.

Plus let’s not kid ourselves here, Winlink is far from the only bad actor on our HF bands when it comes to piss poor operating, violations, and unnecessary QRM.  How much are you hearing about that side of things? ’nuff said.

 

Did Winlink contact you regarding the Open Message Viewer?

That question pretty much blew up the inbox for a couple weeks earlier this year. No they never contacted me regarding the Winlink Open Message Viewer or about the “A Compromise?” suggestions in one of my 2018 blog postings.

The interesting part was watching how long it took for the bulk of the ham Winlink community to realize it was out there. It was there for awhile before the news on it blew up. A lot of what followed reminded me of that old farmer saying of “If the rooster is crowing then he’s damn sure been in the henhouse.” LOL

IMHO what they did was a good start towards some needed transparency. I think a years worth of archives should be the minimal retention period. Should also be searchable by band and time/date period which would make going back to ID a QRM source a lot easier. Would even be handy for the ARRL to vet the Field Day bonus point messages having at least used some non-LTE (LOL) RF to leave the sites.

Gateway operators and members of the Official Observer program should be able to sign up for ongoing archives via email so they can archive and search for problems as needed. Now that it is undeniable that the Winlink system is being abused by some users, it seems the above would be a good minimal foundation towards real transparency and deterring abusive/violative behaviors.

I have mixed feelings about putting the archives behind a login. There are ways to mask out email addresses and PII data before serving it up publicly while maintaining the original message in case needed by the FCC.

 

For those I saw commenting “our served agencies are going to freak out over that Open Message Viewer”

Well that’s on you. You clearly oversold yourselves and the system to your served agencies. Anything that sensitive should of never been going over Part 97 airwaves to begin with. You don’t have to say “yes” to everything they want and frankly you shouldn’t be doing so.

It’s NOT the job nor the proper role of ham radio to routinely be the “Plan B” they should already have. Be the backup for their backup and make it clear what you can and can’t do for them.  Undersell, over deliver not the reverse. Learn to say “no” to folks that just want you to save them some budget money for backup comm gear they should already have.

We are the Amateur Radio Service not the Emergency Radio Service so know where draw that line. Hint, hint the FCC has previously reminded us of that.

 

The K4KPN-14 RMS Gateway’s future?

I suspect its days are numbered. Regardless, rest fully assured that I will not loose a single tear as I edit the config file on the Jonesville node/app stack to disable the RMS functions and restart things. You may well hear a “thank you lord” shouted from the radio room LOL. Those that followed the old blog know that I’m not exactly a big fan of Winlink.

The RMS gateway app on that BPQ32 node stack has been and continues to be an optional component of our local AuxComm digital plan in that it “might” be handy in some limited cases. That was turned on after hints and nudging from KY ARES, yet the only consistent ARES usage has been out of Ohio…not Kentucky LOL. Don’t get me wrong, they are welcome on the system, but that’s not our primary service area. Once the Winlink Open Message Viewer and WinlinkArmageddon news hit the ranks then the already minimal usage disappeared over the summer.

Outpost against the KYPN BPQ32 packet BBS has been and always will be our primary local digital messaging strategy, nothing has or is changing there.  Frankly these fiascos of late have helped us appreciate the wisdom in building our own locally owned, locally oriented, and locally controlled internet independent packet node and BBS system.

 

Predictions on the FCC ruling?

Who knows. I want to have faith that the FCC can sort through all the noise and give us a good ruling that doesn’t cripple a radio service that is already struggling to remain relevant and facing increasing threats to our spectrum.

I’m starting to detect they may not be overly happy with the PITA the ARS is becoming for them. Remember they don’t exactly make money off us.

We also need to realize that we don’t have a Riley Hollingsworth working at the FCC anymore. One of the things that makes what Ted & Crew did so darn reckless.

A good ruling could actually bring some clarity to some of the issues brought up here.

That said, if my ARES/AuxComm/CERT team was dependent upon Winlink I would be working on Plan B for my digital messaging needs.

 

73
WA4ZKO


KYPN Status, K4KPN-14 Shutdown Rumors, ARES, NG0O, Etc

December 19, 2019

Holiday greetings from a snowy 4-land…well it tried to snow. Lots going on around here which I will not even try to cover it all in this posting. Seems like just yesterday we just got back from a long Thanksgiving out in Iowa visiting the XYL’s family and tomorrow we start packing to go spend the holidays out in 7-land. Wow, time flew by this year.

Let’s deal with some rumors and FAQs showing up in the inbox lately.

 

KYPN Packet Systems Status?

All KYPN packet radio systems that were online last summer have been online all of 2019 and remain so as of today. Preventive maintenance was done back in the Spring and all systems are running fine.

Update:  Dec 19th – PM done. I tested all ports, QRP (4-5w)  mobile from 24 miles out, all functioning fine. Quick check on service monitor shows all radio gear operating fine,. Antennas checked, 10m port showing signs the surge suppressor might be failing, replaced, all is fine there.  441/223/28 MHz ports are the most used, all are in great shape. The 10m/6m/2m noise floor remains extremely low so excellent Rx range. 2m port often hears stations over in WV.

The “Orange” sheet for the packet system was updated in July and can be found here in PDF format. The public and internal County ICS-217a forms were refreshed in July and have been distributed as appropriate. New Outpost and BBS/Node cheat sheets were laminated and distributed as appropriate.

For those wondering about the color names?  We print many of the cheat sheets we use across our EOC, MCP, and go-kit documentation binders on colored paper to make them easier to find when needed. Examples?  A ham ICS-217a = red, PS/AuxComm 217 = blue, NTS = yellow, etc.

Some may of noticed that everything is being phased over to the club callsign (K4KPN). There is no need to read anything into that like some have. Nothing more than just part of our forward planning towards the day we fully retire out west and others will be taking over daily control op responsibilities.

Yes blogging has been very scarce and sporadic. No need to read anything into that. Frankly one should get used to that. I’ll try to post more in the coming winter months, especially if we decide to “winter” in 4-land again this year.

 

K4KPN-14’s Future?

Some have heard that we are shutting K4KPN-14 down on December 20th. Shutdown of the RMS (only the RMS functions) on the Jonesville node/app stack has been discussed, but no final decision has been made.

None of our local KYPN crew, FD/EMA, and CERT/AuxComm folks here are even interested in Winlink so its future has been a big ? for awhile now. Some of it is they were never interested in it and some not wanting to get near the black cloud that hangs over Winlink lately. If we need email access then we have a long list of ways to access that. We are far more concerned about what happens if the internet is down or is too hostile to be used and we have a heavy messaging need well suited to digital transport.

Outpost against the KYPN BPQ32 packet BBS has been and always will be our primary local digital messaging strategy, nothing has or is changing there.  Frankly these fiascos of late have helped us appreciate the wisdom in building our own locally owned, locally oriented, and locally controlled internet independent packet node and BBS system.

 

K4KPN-15 2m APRS Digipeater/I-Gate Shutdown Plans?

The only system we currently have any shutdown plans for is the K4KPN-15 2m APRS Digi/I-Gate. It is no secret that has been coming and many months (actually over a year) worth of notice has been given. This may be part of the rumor mill confusion regarding K4KPN-14 RMS.

Current plans are to turn K4KPN-15 off in late January 2020, maybe early July 2020 at the latest depending on how much longer I need to keep leasing it’s current home location as part of my day job needs. Have no doubt that its days are numbered. If there is enough 2m APRS interest in the area then hopefully some others will step up and run the needed infrastructure for it.

 

Are you still involved in KY ARES?

No I have not been active in KY ARES since around 2016. If nothing else was at play here, I wouldn’t have the time to commit to it even if I wanted to. Plus given my family plans there is little need for me to get involved in 4-land ARES when I’m scarce here and will become more so as time goes on.

I have a completed AF MARS application here in the office waiting on a date and signature. That will be the direction I go in when time allows for such a commitment after we get settled into retirement.

Locally our county, like many others, is going down the CERT/AuxComm team road. It has an amateur radio component and I’m helping facilitate that when and where I can. Our EM wants a well trained and well vetted (the felon and sex offender problem in our ham ranks is becoming an increasing concern) team of guys/gals ready to fit into an AuxComm environment more effectively than a group with to many unknowns.

KY ARES is suffering from a long list of problems and challenges that could be a lengthy blog posting alone. Let’s just boil it down to a lack of participation, lack of credibility, and obsessing over things not worthy of much (if any) attention when compared to the mission and current preparedness levels.

Lot of “wearing the hat, but not the boots” and tons of “all hat, no horse” as we say out west. Toss in some bullying (lets call it what it is, you should see an email that I was given a copy of, wowzer) of both ranks and critics and it’s not hard to see why participation is so low in state with nearly 10k hams. Actual relevant training and on a air practice of that training is MIA and what’s there is often counterproductive. Results of last major exercise revealed several problems including  basic message handling failures. It is what it is.

There are some good folks involved in places, I wish them well, but as a whole KY ARES has unfortunately have fallen into the same traps of the past.  I’ll leave it at that.

 

Seems 2019 vindicated your preaching about the coming spectrum threats.

I was not the only one warning of what is coming so nothing to vindicate. Yes “is coming” is exactly what I meant to say. What we’ve seen thus far is nothing compared to the spectrum sucking monster that is coming. The days of us being so lazy and complacent towards spectrum utilization must come to an end.

Soapbox warning……

Newington needs to stop the “quantity over quality” approach that is helping lead us down a road of ever decreasing relevance. We are not going to keep our spectrum just so a bunch of appliance operators can play with internet linked toys, contest, and DX. Not saying those are bad pursuits (I enjoy the last two myself), but they’re not going to keep a healthy sized band chart on our hamshack walls.

That said, if you are a U.S. ham radio operator and you are NOT a member of the ARRL….then shame on you if you don’t change that. Yeah I get it, I detest some of what they are doing but right now they are the only unified voice we have in Washington.  The last thing we need as we head into the new decade is a weakened ARRL. Plus it seems when they struggle for membership they become more open to dumb ideas LOL.  Yeah, pinch your nose, take a stiff drink, write the check and join.

AMSAT needed to get back to dreaming big a decade ago. Enough of the endless 2m/440 FM voice toys. Let’s get some serious birds up there that are truly useful for emergency and remote communications. Imagine where we’d be at if we had a few modernized 9600 baud store-n-forward birds up there?  Imagine if some of them had nice microwave data forwarding links on them?

Imagine if the crew that went into KP4 was able to fire up a D710 or D72 radio, a tablet, and modest antennas and not be screwed if there is a useful attachment because they had the speed to handle it. Imagine the field teams using D710/D72’s at 9600 back to the San Juan via a bird, then San Juan also has a multi-megabit microwave satcom link back stateside? Yeah that’s easier said than done, but we didn’t even try working towards it?  Available spectrum is not on the list of challenges here…well at least for now.

I look at something like the OtherNet box I installed this summer at a friend’s cabin in in southern Idaho. A 12 GHz LNB, no dish needed, just a freakin’ LNB strapped to a rail with some plumbing strap and pulling down a clean 20 kbps stream 24×7 of useful information for a remote location. Cell service is on the other side of the mountain (literally) so just the news feed alone is handy. Even as limited as OtherNet is one has to wonder why we hams don’t already have something similar to it.

AREDN, you guys were warned about focusing so much on the “easy” (and increasingly noisy) 2.4/5 GHz band approaches. Imagine where we’d be at if we’d focused a lot more on some of the other bands vs just letting them languish. My what we could of done with just 1.2 and 3 GHz makes one want to cry.

In case you haven’t noticed we’re going to have to start ACTUALLY justifying our spectrum going forward. A node on the air isn’t going to count for much minus actual usage data. Defensive arguments based upon theoretical or possible future uses of spectrum we are not using much (if at all) equals spectrum we best get ready to scratch off our band charts.

For the Ham Internet toy folks, how are you going to feel as we loose good chunks of our VHF/UHF bands? How are you going to feel when “they don’t need all that link/aux spectrum, they are already doing more and more of it over the internet vs RF anyways” is one of the compelling arguments the commercial interests use against us? May I suggest using a lot more Ham Radio and a lot less Ham Internet.

We have simply become too lazy, cheap, and apathetic towards real radio communications to survive much longer. Too many appliance operators, too few communicators. Even fewer with much useful technical talent beyond running to their favorite search engine to copy the work of others versus taking a manual and actually learning something. Well those lazy chickens are just starting to come home to roost. If we don’t snap out of this soon we’re going to be setting around wondering “what the hell happened to our hobby.” I used to think we had about 15-20 years left, but I’m starting to think that is a bit too optimistic.

The days of commercial interests thinking “don’t bother even asking about the amateur spectrum” is changing over to “it’s time they start justifying what they have or give it up to those that can put it to uses that better serve the public interest.”

Let there be another lackluster response like post-Katrina and brace yourself for a full on onslaught against all our spectrum.  Hint, they are doing their homework on our spectrum while we are doing what? Fighting over antiquated symbol rate silliness. Plus I’m sure all that symbol rate headache we’re causing the FCC is doing wonders for how they feel towards “the hams and all their valuable spectrum.”

We’ve gone from being respected by the commercial radio world to often being LOL material tying up way too much valuable spectrum. One doesn’t need much imagination to hear the arguments coming, we’ve done a wonderful job of providing them the ammo they need to come raid what they want.

Heck, one doesn’t have to read much between the lines of recent news to realize that our 3 GHz allocation is ALREADY gone. I don’t think I’ve seen a more thinly disguised “they want it, we’re taking it for them, thank you, you kids can feel free to formally pout about it if you want” NPRM in 30+ years.  Wowzer, OMG the precedent this is going to open up here stateside.

Wake up, pay attention, ignorance will not be bliss much longer.

 

What do you think of the NG0O murder case?

Obviously a tragedy. A major loss on many levels. A good reminder of how domestic violence can easily turn deadly.

As far as some of the good father or bad father allegations that are out there in public?  Who among us is a perfect Father? Sure there’s always a little room for a surprise in these things, but nothing justifies murder and the dots are not hard to connect here regarding what most likely happened.

I realize this seems completely out of fashion in our society lately, but let’s try waiting for all the facts to come out after a proper investigation has completed before passing much judgement.   #GoodFreakingGrief

Sorry, maybe I’m a tad jaded but my first instinct is to not trust anything coming from the mouth of a felon that just confessed to a murder after being caught fleeing the scene. If that’s not enough go read the existing DVO against him.

For the knuckleheads trying to make it anti-gun? Zero evidence of any gunfire involved. All evidence points to Marvin being killed with a hammer, a freaking hammer. Suspect we’ll find out that if he would of had a gun handy he might still be with us. Never mind it was good guys with guns that brought his killer in to face justice.

 

 

I’ve seen you out on the reservation. Arapaho or Shoshone?

Neither of those. I have a family there that I’m friends with that I met on a work project out there. We’ve spent a few nights with them there on the Res since the Iowa to NW Wyoming portion of our roadtrips is a wee bit too much for one day’s driving LOL.

I’m part Seneca Indiana via my Grandfather on my Dad’s side. A very distant descendant of Chief Strong of the Buffalo Creek Reservation. Family rumor is I likely have some Cherokee in me via my Grandmother’s family but she never wanted to talk about it.

Unlike a certain politician I don’t try to “gain” from it even though I suspect my bloodline is considerably thicker than her PPM levels LOL. I never lived their life or struggles so I would never try to profit off it. It’s just part of my ancestry and something my late Father and Uncle got me interested in. The other half says it explains my affinity towards horses and why riding into the backcountry to go fishing/camping is “Jeff’s happy place.” Guilty as charged LOL.

 

A true Wyomingite has a Wyoming worthy Rifle, what is yours?

Gee, never heard that before LOL.  Actually we both fit well into the rules of Wyoming worthy calibers…..those calibers that start with either a number 4 or 357 LOL.

Rifle = it depends. Trunk gun is usually an AR-10.  An old .444 Marlin lever-action is usually in my saddle scabbard and backed up by either a Glock 35 in .40sw or a Sig P320 in .357 Sig if needed. The other half is fond of her Henry lever-action in 357 Magnum and her work HK USP in .40sw. All go into the backcountry appropriately loaded with “hot-n-heavy” handloads well suited to intense final negotiations with a large angry or hungry 4-legged problem if it comes down to that.

 

Word is you camp in a real teepee?

Sometimes. A friend down in on the WY/CO border has one they built next to a private lake. The fishing isn’t that great, but the views there are awesome. They built it primarily for a hunting camp.

Don’t laugh, a well designed teepee is a great camping shelter, even in cold weather. It’s actually a pretty neat camping experience so don’t knock it if you haven’t tried it.

For the radio geeks….the top makes a decent antenna support and offers a couple easy feedline entrance options LOL. Hey most see top poles merging, I see antenna mast 😉

No, I haven’t done any sweats, put on war paint, wore a headdress, or smoked a peace pipe (I have one)…..yet LOL.

That’s enough for now.

 

73
WA4ZKO

9.6k Packet Myth #1 “9600 baud packet is not much faster than 1200 baud”

July 16, 2019

Claim:  9600 baud packet is not much faster than 1200 baud.

Fact Check:  Not true. Well that is unless you have a strange definition of “not much faster.”

9600 baud packet may not be 8 times faster, but several times faster throughput can be easily obtained off a user port if decent radios are used. If backbone grade radios are used then you can make 9600 go faster. Use backbone grade radios on a full duplex link then it will really push some bits along.

Real world example? After completing some project work at a client’s location down on the river I ran some quick tests off our 2m 1200 baud and 70cm 9600 baud user ports. Same client radio, same antenna, same software, same modem, linking to the same RMS.

Not a lab grade test, but a very “real world” and fair test. Both ports used on the remote RMS are user ports configured as they have been for years. The 2m port is ran about as aggressive as you would want on a 1200 baud port with a variety of client radios connecting. This also includes some users running soundcard interfaces that are often a bit slower on TX<>RX turnaround/recovery times. The 9600 baud port is also running somewhat restrained due to some users having slower radios.

Tests were from my FT-818 based portable HF Robust Packet, 1200 baud, and 9600 baud station using just a mobile antenna on the car in a parking lot. Just shy of a 15 mile mobile to base non-LOS link. It was 92F down on the river and I’d venture to say the “hot humid sunny afternoon effect” was in full effect. Trees are fully leafed out after a very wet spring so foliage losses are high. flat bands, elevated path losses, and some multi-path through the hills all equal a near worst case non-LOS link scenario for that path. Perfect for a real world test.

Could this be done in a more perfect lab like environment? Sure and those results would have value as long as one keeps in mind that the lab is not the real world. Nothing against lab tests, but we don’t operate in a lab here. Thus we prefer to see how things actually work out in the real world 😉

The TNC used on my end was a SCS Tracker DSP TNC running version 1.7m firmware. The RMS gateway was running as one of several applications on top of a BPQ32 node.  TNCs at the RMS Gateway are a KPC-9612+ for the 1200 baud port (so much for the myth that the Tracker is not compatible with Kantronics modems LOL) and a PacComm Spirit-2 TNC for the 9600 baud port. Both running in XKISS mode. Both those TNCs are arguably the gold standard for their particular uses.

Screen shots of the results speak for themselves….

9600 baud packet radio link test. 17k compressed, 28,791 bytes/min.

 

1200 baud packet radio link test. 17k compressed, 4,537 bytes/min.

Signals on my end were nearly full scale on 2 meters and floating around S9 to one bar over it on UHF. It was the middle of the afternoon on a hot sunny day down on the river with some terrain between my mobile and the site so some multipathing was in there but not severe.

Yes just like the Yaesu FT-817 and many of the VHF/UHF all-mode radios the Yaesu FT-818ND is a good radio for 9600 baud packet. It may be “new version bias” at play but I suspect the 818’s receiver is a bit better at 9600 baud. I would love to see ARRL Lab BER test data for it. Yes they are very similar, but contrary to popular myth there are some design changes in the FT-818 vs the FT-817…..hint take a look at the receiver section.

Nope I didn’t buy the FT-818 instead of another 817 for the extra watt of TX output advertised LOL. It is interesting lately watching how the manufactures have figured out how to market to (and milk) the growing appliance operator crowd in our hobby. I wanted to use my 817 for a remote IF radio in the 7-land shack so I needed a 2nd one for travel and 4-land.. The FT-817ND was out of stock and the 818 was on sale so that’s what I got, no regrets thus far.

Sidebar:  If you have a FT-817ND and are happy with it I don’t see a reason to go out and buy a FT-818. If you are in the market for your first or additional radio with the 817/818 capabilities and packaging then by all means consider the FT-818ND first.

FWIW I suspect the Tracker’s 1200 baud mode could use a bit more optimization to decode weak noisy signals better, but it appears the Tracker’s 9600 baud mode is working extremely well. The Tracker is a hybrid software/hardware TNC that can be firmware flashed (free downloads) with new features, bug fixes, and optimizations so it’s only been getting better over time. SCS has been great to work with on bug fixes and improvements.

Wondering what that binary attachment was? Here you go. A very useful graphic for those that work EmComm in the SE USA this weekend. With 9600 baud packet you can have that downloaded, reviewed, and moved onto other tasks before 1200 baud is halfway done downloading it.

Tropical Storm Barry weather graphic. Well under a minute to pull that down over 9600 baud packet radio versus nearly 4 minutes if you used 1200 baud.

True nearly 4 minutes versus a fraction of that may be NBD in some situations or a huge boost in messaging capacity and turn around time for other situations. Regardless, to claim 9600 baud packet is not much faster than 1200 baud is easily proven to be just another packet radio myth.

In closing I suspect this particular myth is just folks repeating what they heard or read as gospel. Sometimes I think it’s just an excuse to avoid learning something new and making packet radio even more useful. Regardless they obviously have never actually seen or used a properly configured 9600 baud packet system. Trust me once you use 9600 baud packet it will be painful to go back to 1200 baud for all but APRS and the lightest of duty needs.

No the above is not a dissing of 1200 baud packet in any way.  Hey, gotta be careful now that Perpetually Offended by Everything Syndrome seems to be infecting the hobby lately 😉

 

73
WA4ZKO


Inbox ?s Frequencies, 80 Meters?

November 5, 2018

Apparently starting blogging again after several months of being scarce results in a rash of inquiries. Since I have a rare Monday afternoon off after unpacking the car and running errands this morning I’ll tackle a couple things.

Frequency wise nothing has changed this year other than the addition of APRS to the six meter port of the Jonesville node. Below should make a good quick reference:

BPQ32 Node KYJVL - Jonesville, KY EM78PP 
Port 1: 441.0500 MHz 9.6k   (primary user port)
Port 2: 145.6900 MHz 1.2k   (user port)
Port 3: 223.6600 MHz 1.2k   (user port, low speed linking)
Port 4: WAN            (intrasite Canopy/VPN links)
Port 5: 28.1480 MHz USB RP  (user port)
Port 6: 50.6200 MHz 1.2k    (user port, APRS Digi/Gate)
 
NODE = K4KPN-4
BBS  = K4KPN-1
CHAT = K4KPN-13
RMS  = K4KPN-14

Some have asked if there will be an 80m RP port? Maybe a temporary one next Fall, but it will involve whether or not some spare gear becomes available. I’m not going to go “buy” gear just for an 80m port because it’s not going to be a viable band at the future site. Problem revolves around space constraints, local noise floors (80 is nasty there), and control op privileges.

10 meters may have to be it for HF depending on who eventually takes over daily control op responsibilities of all K4KPN gear. The two most likely future control ops are still “techs” so that plays into things – I’m doing some nudging LOL. The trustee/control op questions will be part of the decision making on what bands move to the future site. Technician class licensees can both use and be control ops of that 10 meter robust packet port above so NBD there.

 

WA4ZKO

 

 

 

 

 

 

 

 

 


K4KPN System FAQ

June 1, 2018

This is a work-in-progress….

FAQ #1 – Any other HF bands than 10 meters?

Answer:  Not at this time. We may add 80/40 or 30/17 meters in the future, but that is a big maybe at this time.

 

FAQ #2 – Why only 10 meters, why not a lower band?

Answer:  The 10 meter port’s primary purpose is to provide an additional coverage option for local fringe locations that even the 6 meter 1200 baud packet port struggles with due to noise/distance etc.

Remember 28 MHz behaves very much like 30 MHz VHF-Low with propagation characteristics well suited to the hills and valleys common to our coverage area. 10 meter Robust Packet fills the need.

We are not offering lower bands at this time due to the main HF antenna the site is dedicated to remote HF/VHF station use and that takes priority for now. A future site may allow for a 30/17m port, but no scheduled date of availability or guarantee on that.

 

FAQ #3 – Why Robust Packet, why not one of the soundcard modes?

Answer:  We have not found soundcard modems to be reliable enough for 24x7x365 use at a remote site. It is one thing if the system is down in your basement or over in the corner of your hamshack, but modem evaluation criteria changes when the system is miles away at a tower site. We also wanted a mode/modem that was suitable for BOTH interactive use with packet applications (BBS, Chat server, etc) and message transfers. Lot of the other modes are okay for message transfers as that was what they were designed/optimized for, but often poor choices for interactive connections.

Robust Packet is hardware modem based and gives us an excellent mode for interactive access and plenty of message transfer speed for our particular needs. It also works well with weak noisy signals, has considerable immunity to multi-path, and often works in fringe locations where the 6 meter AFSK packet port will not.

 

FAQ #4 – Is DX use of the  6 or 10 meter ports allowed?

Answer:  Yes, but please yield to any local users on QRG.  The 10 meter port beacons every 10 minutes to help detect band openings.

The 6 meter port beacons an APRS compatible beacon every 5 minutes to help detect band openings. The 6m port also functions as a WIDE1-1 APRS digipeater.

 

FAQ #5 – What is WYJAC, BBSJAC, etc?

Answer:  WYJAC (WA4ZKO-4) / BBSJAC (WA4ZKO-1) is a test/dev node and BBS at our 7-land QTH. The Dry Ridge site is linked to it over a private network, thus you will see those nodes/applications showing at times. It will also allow migration/expansion of the KYPN packet network and applications later on down the road.

Please do not leave messages on the WA4ZKO-1 BBS as it is just a test BBS for now.  Please leave all messages on the K4KPN-1 BBS unless instructed to do otherwise.

 

FAQ #6 – Is telnet access available?

Answer:  Yes, but it will be considered on a case by case basis. For now it is restricted to those with access to the inter-tower KY<>WY VPN LAN/WAN network. Those within VHF/UHF range will be required to have a functional and actively used “RF” packet station before telnet access will be considered. The goal of the packet BBS is to provide a RF only messaging system, not breed laziness and apathy towards having effective RF access.

Yes having a Winlink RMS gateway on the system kind of conflicts with the above LOL. It is secondary to the conventional packet systems. Trust me, it took some convincing for me to even offer it, especially on VHF/UHF.

The K4KPN-14 Winlink gateway is on “probation” as far as I’m concerned. If it’s not used then it will eventually be turned off. If it becomes a PITA in terms of admin or abuse then it will be turned off. Many said they wanted it, now we’ll see if that was just talk and how it will be used 😉
 

FAQ #7 – Does the KYPN systems have backup power?

Answer:  The K4KPN-10 HF RP APRS I-Gate/Digi is at a secure tower site with backup power options.

The K4KPN-1 (BBS), K4KPN-4 (Node), K4KPN-6 (6m digi/I-gate), K4KPN-13 (chat svr), and K4KPN-14 (RMS) systems are located on a private tower site near Jonesville. This site has short term battery bank backup in place to allow it to stay online till manual transfer to an on-site generator.

The K4KPN-15 2m APRS I-Gate/Digi is located in Williamstown. The station has very limited battery backup. Normally it will be shut down during an extended power outage. It should NOT be counted upon for emergency uses. Also note current plans are to decommission it in January 2020.

 

To be continued….

WA4ZKO