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)
BBS  = K4KPN-1
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.












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….