K4KPN-10 Storm Damage

July 3, 2018

Update July 4th . K4KPN-10 is back in service.

So far the damage sounds like a power supply (likely repairable), a few fuses/tripped breakers, and unfortunately the tragic sacrifice of a kind gentle soul of a Rev 1 SCS Tracker TNC to the thunder gods. Thankfully there were spares nearby and we were able to get things back online last night.

There may be some brief outages later in the week due to electrical work/repairs at the site.

73 de WA4ZKO

Apparently around noon eastern time the Dry Ridge site took a major lightning hit. Mike ran by and his quick assessment is the site is dark and the transfer switch got smoked pretty good. Judging by telemetry things ran till the UPS systems told things to shut down.He did a cold start and it looks like at least a PSU and the Tracker modem on K4KPN-10 is dead…radio came on but may well be damaged.

He’s heading back out there this evening to get the tower lights back on and start checking and bringing the commercial gear online. Once the commercial gear is back up he’s going to call me and we’ll start doing further damage assessment on the ham gear. I have some spares on hand, but depending on how bad things are K4KPN-10 may be down for the count.

WA4ZKO /7


6 Meter APRS Lives

June 21, 2018

Update:  Dale N0KQX has joined in from SW Kansas as of June 24th. N0KQX-6 has already been heard several times at K4KPN-4 in KY.  The K7BC-6 Virginia I-gate appears offline since the 21st. A few more I-gates on frequency would be nice. I believe I can enable gating on K4KPN-4’s 6m port (ah the flexibility of BPQ32) without impacting general packet operations on that port. I plan to test that option on my next trip back thru 4-land.

It’s not every day you hear and “digi” off the 50 MHz APRS digipeater at the Pentagon.

K4AF-6_20180619_6m_APRS_map_pent

Map showing location of the K4AF-6 six meter digipeater at the Pentagon. I believe this is part of the MARS radio station located there. Frequency is 50.620 MHz using 1200 baud AFSK packet.

 

June 19th 2018 a nice strong opening into NE Virginia revealed that the 50.6200 MHz 1200 baud 6 meter APRS and long time 6m packet “calling” frequency still has some action on it.

K4AF-6_20180619_6m_APRS_KYRDG_Terminal

The monitor for the 6m (50.620 1.2k) and 10m packet/robust packet ports at the K4KPN-4 N. Kentucky node. K4AF-6 is at the Pentagon. K7BC-6 is a few miles to the SW. Both are just over 400 miles away. Opening was very brief. June 20th would produce a stronger opening. Times are UTC.

 

On June 20th things would liven up even more with the Conway AR node “CON50” W5AUU-6 (likely bleed-over from 50.615 MHz) coming in. There was also an extended and strong e-skip opening to Wash DC with APRS packets bouncing around and being digipeated like it was 2m APRS at times. Several K4KPN-4’s beacons were getting digipeated and I-gated into APRS-IS via K7BC-6 in Springfield VA.

 

6m_aprs_raw_pkts_20180620

The June 20th 6 meter APRS opening into the Wash DC area lasted for over an hour. K4AF-6 was even audible at times on a HT (Yaesu VX-8DR) setting on my desk. Gotta love the Magic Band of 50 MHz!

Distances involved where about 410 miles from Kentucky to DC. So I wouldn’t call it really short skip, but definitely shorter than normal. General rule of thumb is when 6 meter e-skip shortens up to 250-300 miles then it’s time to start checking 144 MHz for possible e-skip on that band.

Good to see there is still some life on 6m APRS. Band openings can make things interesting, even on VHF packet. Also nice to see there is some packet radio gear at the Pentagon MARS / AR station(s).

K4KPN-4’s 10m port beacons every 10 minutes and the 6m port beacons every 5 minutes with APRS compatible beacons to help detect band openings. The 50.620 MHz 1200 baud port on K4KPN-4 also supports WIDE1-1 digipeating in addition to normal packet radio connects.

 

WA4ZKO

 


SCS Tracker DSP TNC Firmware v1.7F Available

June 19, 2018

SCS Tracker DSP packet radio TNC firmware version 1.7F is now available for download from the Files section of the Robust Packet Yahoo Group or via the the beta firmware option in the SCSupdate program.

An easily overlooked source code formatting error snuck into a subroutine portion of the code in a way that didn’t throw any errors when compiled. This impacted the HDLC state machine’s ability to properly track multiple incoming frames. This is the bug detailed in some of my recent RP Group postings.

While this should be considered “beta” firmware for now, it appears to have solved the above problem. My initial testing is showing the problem resolved. If you use your Tracker DSP TNC for VHF/UHF packet then you should strongly consider installing this free firmware update.

NOTE: I have SCS looking into another packet mode bug that is on the transmission side of things. The TNC will never send more than 2 frames regardless of MAXFRAME settings. This may be a Winlink Express bug and more testing is needed. This would generally only impact 9600 baud users with degraded upload speeds.

Do note that RPR is hard coded to limit maxframe to 2 by design. This issue does not impact RP mode.

My thanks to John KX4O of VAPN for his help and testing.

Thanks to SCS for their excellent ongoing support and desire to further improve the Tracker DSP TNC for both ARPS and non-APRS uses.

WA4ZKO


K4KPN BBS & RMS Gateway are Available

June 9, 2018

KYPN would like to announce the full availability of the KYPN Dry Ridge BPQ32 based packet radio site as of June 9, 2018.

The following packet radio applications are available:

K4KPN-1    BBS
K4KPN-4    Node
K4KPN-13  Chat/Conference Server
K4KPN-14  RMS Gateway

The above packet radio applications are normally available 24x7x365 to appropriately licensed amateur radio operators on the following frequencies/modes:

SYSTEM PORTS:
441.0500 MHz 9600 baud *
145.6900 MHz 1200 baud
223.6600 MHz 1200 baud *
28.1480 MHz USB dial, 28.1495 CF, Robust Packet “NET10R” *
50.6200 MHz 1200 baud **
* High availability, primary port.
** Dual-use port, both general use & 6m APRS WIDE1-1 Digi

All 5 bands and 3 modes are published to the Winlink channel listing.

Recommended user software:

KYPN recommends Outpost Packet Message Manager version 3.0.0.333 for BBS access. Full installer is available for download here.

KYPN recommends Winlink Express v1.5.12.0 or newer for RMS access. Available for download from here.

More details can be found on the K4KPN-1 packet BBS under messages #1 thru 8.

More details in future blog posts and the work in progress draft KYPN System FAQ.

 

The KYPN team.


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

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.

 

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.

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 where 6 meter AFSK packet 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 / BBSJAC is a test/dev node and BBS at my Wyoming QTH. The Dry Ridge site is linked to it thus you’ll see those nodes/applications showing at times. Please do not leave messages on the WA4ZKO-1 BBS, again it is a test BBS for now.  Please leave all messages on K4KPN-1 (netrom alias BBSNKY) unless instructed to do otherwise.

 

FAQ #6 – Is telnet access available?

Answer:  Yes, but it will be considered on a case by case basis. Those within VHF/UHF range will be required to have a functional “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 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 considerable commercial grade backup power on stand-by.

The K4KPN-1 K4KPN-4 K4KPN-13 K4KPN-14 systems are at another 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 (few minutes) battery backup. Normally it will be shut down during an extended power outage. It should NOT be counted upon for emergency uses.

 

To be continued….

WA4ZKO


K4KPN-10 Robust Packet I-Gate / Digipeater Update and APRS-IS Gotchas

May 26, 2018

K4KPN-10 has clearly benefited from the combination of antenna system repairs and noise floor (NF) reduction work at the site last Fall. Performance is back to what one would expect from it.

For those that ask why Robust Packet? One word….performance. Below is a screencap of what the 30m RP APRS world looks like from the Kentucky gate’s perspective over a few days.

RPR_K4KPN-10_20180519

K4KPN-10’s view of the 30m Robust Packet APRS world. Why RP? One word….Performance.

Around 25 to 30 of those stations on there have been heard direct on RF at some point. Single hop stateside coverage is easy. Europe is in to some degree nearly every evening and EU mobiles are often heard. Even the challenging polar path over to RT9K-15 is in there at times.

I’m hesitant to use APRS-IS for serious coverage analysis since it doesn’t begin to reflect everything heard on RF, especially on HF. Regardless K4KPN-10’s “heard” and “heard by” data is interesting:

RPR_K4KPN-10_heard_201805

APRS-IS perspective on RP HF APRS stations heard by K4KPN-10 so far this month.

RPR_K4KPN-10_heard_by_201805

APRS-IS perspective on RP HF APRS stations that have heard K4KPN-10 direct so far this month.

Yes some of the soundcard modems will do good work on 300 baud AFSK for single hop HF APRS and some occasional DX can get through. Some can do even better with bit fixing. The problem with bit fixing (guessing) is it breaks spec and can easily cause corruption if done too aggressively even on APRS. Thus why we so often trace corruption on the VHF APRS feeds back to soundcard modem equipped gates. Even with bit fixing the limitations of 300 baud AFSK become apparent over long haul DX paths.

Where Robust Packet shines is it uses Pactor-III like modulation that allows error correction without breaking spec. RP offers good noise immunity and deals with the multi-path on long haul DX packets better than a typical AFSK modem can.  Since RP uses space and power efficient dedicated hardware it is also well suited to stand-alone portable/mobile tracker uses without the need for a PC/laptop.

Robust packet is a mode and hardware built from the ground up for improved performance on HF and well suited to HF APRS. DX reception is not occasional, it is commonplace. I admit to sort of taking 4,000+ mile APRS DX as NBD till one of the HF AFSK guys sent me a “holy $#@$ what are you using that hears across the pond nightly” email LOL.

For those asking “where is K4KPN-10 hearing RT9K-15? Oh it is in there on RF, but due to his gate configuration it’s going to be difficult for stations other than a few lucky EU gates to ever get credit (APRS-IS perspective) for hearing him.

RT9K-15_at_K4KPN-10

RT9K-15 being heard direct at K4KPN-10.

Well here is an opportunity for a good lesson on the flaws of assuming APRS-IS gives a complete picture of what is going on at the RF level.

It is important to realize that APRS-IS does dupe checking. If I-Gate A and I-Gate B hear the same packet only one of them can get credit for it from the APRS-IS perspective. Which one gets credit? The first one that gets that packet to APRS-IS. The one with the lowest latency to the APRS-IS system.

If you run an I-Gate or home APRS system on both IP and RF you can easily screw yourself with bad timing values. The RT9K-15 I-gate is doing something that will make it very hard for coverage analysis via APRS-IS. It appears to be aggressively beaconing to APRS-IS every few minutes? I’m told that it is heard often in EU, but rarely does an EU gate get credit for it in the eyes of APRS-IS. This tells me it is probably making the 2nd mistake of beaconing to APRS-IS and RF at the same time. This means even if another gate hears his packet on RF then it’s unlikely outside of internet congestion on his link that another gate can decode that packet off RF and inject it into APRS-IS before his internet beacon gets into APRS-IS.

Another problem this creates for APRS-IS analysis is it throws the packet counts off on the above pages. A good example is it shows a monthly total of 5 packets for DF1CHB /AM.  He was in direct on the eastern USA I-gates for hours earlier this morning, but also hitting EU gates so NOAM will only get occasional credit for gating him even after dozens of packets gated in. Tonight he is airborne over Serbia and K4KPN-10 is hearing him direct like clockwork on 30 meters:

DF1CHB_30m_rpr_aprs_20180526

DF1CHB /AM over Serbia and coming in on 30m robust packet almost as if he’s a local on VHF LOL.

Don’t get me wrong, this is not a complaint towards APRS-IS. It’s just how the system works and how it has to work. It’s just important for APRS operators to understand that APRS-IS doesn’t give you the full RF picture due to the necessary dupe checking going on. This is especially true on HF where the same packet can easily be heard by multiple I-Gates hundreds or thousands of miles apart.

Also noteworthy that some stations run beacons marked “RFONLY” or “NOGATE” paths. A properly configured I-Gate will not gate those beacons into APRS-IS. This is another gotcha if you’re trying to get a full picture of RF level activity via APRS-IS based systems and apps.

Recommendations based upon lessons learned here if you are interested in getting decent coverage analysis via APRS-IS?

  1. There is normally no need for an APRS station to position beacon on their internet port (APRS-IS) more than once or twice an hour unless it is moving. Serves no useful purpose for fixed stations and it only adds to the cumulative load on the APRS-IS system.
  2.  I-gates should consider beaconing on their internet port at a rate of just under 60 minutes.
  3.  Avoid beaconing via RF and internet ports at the same time.
  4.  If you are not moving, then you don’t need to be pounding the heck out of the RF side either. 2-3 RF beacons an hour from a fixed station is more than enough to keep you on most maps and fresh in APRS-IS for messaging/gating purposes if you are in range of an I-Gate.

WA4ZKO


Packet Update, Winlink, Is Ham Radio Dying? Puerto Rico

May 26, 2018

Since the inbox shows some got worried when we went west early with only the APRS gate/digi project done I guess an update would be a good idea.

We went west for a friend’s wedding.  Pro Tip: Few things can compare to a wedding set against the Teton Mountains. Since we spent most of the post-holiday Winter season in 4-land I also had several 7-land biz/personal items needing attention. I flew back and the XYL is driving back as she wanted to stop and visit with her Iowa family.

For the worries about the packet stuff getting done this Spring/Summer? Well I had been waiting on two Liebert UPS systems to come in so I can finish up the power and remote control side of the “packet/HF” rack. They are in and this looks like a somewhat slow weekend/week ahead so we’ll see what gets done this week. completion time = good question. Between work and Dad’s health issues I’m not going to commit to any timelines on hobby stuff as I can barely nail down a work schedule beyond a week out. It is what it is, family and work come first.

What’s going to be put on the air?  Well I can say for sure that a 10m RP port and a UHF 9.6k port are coming. Our core occasional EMCOMM needs can be met by a local packet BBS with a 10m RP port plus a UHF 9.6k port. I’m still back-n-forth on spinning up the 2m/220 1.2k stuff. Granted we have lost several local ops in the last decade or so due to SK and job related moves, but I’m frankly more than a little shocked at how dead ham radio seems around here and across Kentucky.

A lot of area packet and voice infrastructure has came and gone within the last few years. “Lack of usage” is usually the reason given. Even worse I often hear sysops of existing gear commenting that they really can’t justify keeping unused stuff on the air. Several have said they’ll run it till they take storm damage then it will not be repaired. Use it or loose it folks.

APRS activity for “Dayton” seemed to be down somewhat. On that note, one of the western Kentucky ops emailed me that he came up for Dayton and could not hit a single Winlink packet gateway with his D710. I looked at the Winlink gateway map below and could only ask where are all the gateways? Lexington/Frankfort is a dead zone??? Several of the WKY gateways seem MIA. The SE KY gateway doesn’t exist, it is actually just a misconfigured Georgia gateway.

ky_rms_pkt_map_dayton_wknd_20180520

The other day I was at a tower site and tapped into a VHF-Hi antenna port to a nice true 6 dBd omni up at 210′ AHAG that I can hit repeaters from Lexington/Richmond, Louisville, and up into Dayton/Columbus from. Fired up Winlink Express, pulled the freshly updated channel list below and could not hit anything. Granted I was just using 4-5w from a FT-817 (very possible 25/45w could change things) to a 150-160 MHz optimized antenna. Still that’s not much of a gateway selection list compared to a few years ago. Lot of previously active systems around here are gone, misconfigured, or off the air for some reason. Yes I checked for the EMCOMM group.

RMS_Packet_few_20180526

Past chats with some of the Winlink sysops I know all reveal a common thread. Folks talk of wanting this or that infrastructure and it sees a brief burst of interest then activity just fades away. One sysop that shut his gateway down told me it was seven months before someone asked about his gateway’s status LOL.

In fairness this is not just a packet problem, we also see similar with the current state of D-Star, DMR, and the analog repeater scenes. I ran our group’s portable analog repeater from a couple sites from October 2017 till early May 2018. I kept it patched into a couple systems so I could both record and monitor any activity on it.  Over all that time the repeater’s total transmit time was just over 52 minutes. 99% of that was just the IDer running from lots of kerchunking, only four unique callsigns heard beyond mine, and two brief QSOs. As I told the guys, no need of risking that to storm damage for that amount of activity so it is back in storage till this Fall.

Several have commented that the hobby is dying a slow death. While I’m not going to be that dramatic the hobby is definitely facing some serious activity related challenges in most areas of the country. This even includes areas which used to be hotbeds of activity. We now have a boatload of paper hams and hams that have gone or remain inactive for a wide variety of reasons.

Kentucky has nearly 10,000 licensed hams so “where the heck are they?” is a fair and obvious question. I found it revealing awhile back when the primary ham radio mailing list for the state revealed only about 450 subscribers when they began a move to another mailing list system. I just looked and only around 190 have migrated to the new system after several months. One does not need to be a Harvard MBA to be floored by those numbers. Yes it’s easy to be a Negative Nate on this stuff, but Step 1 to fixing a problem is recognizing that you have one.

When asked about the latest ARRL licensing proposal I can only respond with “I  don’t think lowering our standards once again is going to change much. The downsides are many for a hobby of technical pursuits. I do thank the ARRL for the free lunch.”  For those wondering about the “free lunch” portion of that? Well I made a lunch bet back in 2016 that if ARRL membership continues to decline then expect another push to lower licensing standards.

To be blunt, the further “dumbing down” of the hobby is not the fix unless the problem revolves around fixing the flow of subscription/advertising money. You know it’s not like passing the current General class test is so difficult. Common to hear stories of folks that take the Tech test, pass it, then be handed the General for giggles and either pass it or barely fail it. It’s not like during the last solar cycle we had Techs piled up deep on the sweet chunk of 10m spectrum they already have access to. Since chasing “quantity” (ahem money) hasn’t worked out so well maybe it’s time to try focusing on quality?  I could go on and on but this post will likely be long enough as is LOL.

So back to VHF/UHF packet…..

Considering all the above I’m obviously going to have to ponder how much 1200 baud VHF gear I want to put on the air. Would it see enough BBS and Winlink usage to justify it? If it wasn’t for already having the gear and putting in the extra rack space for the remote HF-UHF station then it wouldn’t even be on the table for consideration.

 

My stance on Winlink….

I’ve never been overly warm to the VHF/UHF side of Winlink. It doesn’t make as much sense as the HF side of Winlink does. One of the locals did make a reasonable argument that since the Dry Ridge site serves several counties across a handful of power grids and ISPs then there are a few EMCOMM scenarios when VHF/UHF packet Winlink access could be useful, especially at 9600 baud.

I’ve never been a huge fan of Winlink for a variety of reasons. Some are security related, the abuse that goes on, software stability, software roadmap stability, and ability to audit what content is flowing over systems under my license. Let’s examine each one of these..

  1. Security remains a big concern. Moving things onto a certain cloud provider doesn’t help make one feel all warm and fuzzy but I get why they did it.
  2. The abusive use of Winlink on HF remains a concern. Sounds like it’s gotten worse now that the solar cycle has forced more and more of the HF Winlink folks down onto already crowded lower HF bands.
  3. Software stability issues remain. Client software glitches are one thing, but gateway software needs to be rock solid. We are now how many years into the development of the RMS software?
  4. The software roadmap appears as spastic as ever. There is really no reason why the version silliness needs to go on to the degree that it does. I mean come on after all this time surely we can have long term production versions that do the basics and do them well. Then have a beta fork for those that wish to play with whatever new shiny soundcard mode is the current rage. If I put RMS services on my gateway and it’s a never ending PITA of having to upgrade and revalidate new software versions then RMS will quickly go bye bye. I can always use the SMTP functions in BPQ32 for my own limited “Plan D” backup email needs.
  5. The ability of the sysop to audit content flowing over his/her RMS gateway is a mandatory requirement in my book. If you can’t inspect the content flowing over your system then how do you detect abuse and ensure rule compliance. While it’s not as good as it could be I will  credit the WDT for giving RMS gateway sysops some ability to review messages flowing over their gateways. Does it need improvements? Yes, but it is a start in the right direction.

So as you can hopefully see there are many things being considered in regards to what will be reinstalled and what new features will or will not be available.

 

Packet TNC options…..

Some have commented they would consider saving up for some packet gear if they knew with some certainty about what is going to be available long term. 10m RP (Robust Packet), 9.6k UHF, and maybe the 6m/220 1.2k baud AFSK ports should be around for the long haul. Due to how noisy the VHF band can be in some of our needed coverage locations I may convert the 6m 1.2k port to RP also. If I put the 2m 1.2k and 220 1.2k ports back online their future will be dependent upon their usage levels which I will examine in a couple years to see if they are worth maintaining.

Two decades of experience showed the 220 band was more useful than the 2m port. This was due to being cleaner spectrum and greatly reduced desense/bleed-over issues when we worked along side our public safety systems which are predominately 150 MHz. 145 MHz also tends to be full of various noise/QRM sources and that problem is only getting worse.

 

The ARRL / ARES Puerto Rico Adventures?

My KP4 trip was months afterwards and unrelated to any of that hot mess. I’ve heard both some first hand accounts and a lot of second hand stuff including the thought provoking interview the HRN crew did with a couple ops that went into post-hurricane KP4 for disaster relief. In short I could write a mini-novel on that topic. I’ll just hit on a few key points here that will be lengthy enough.

First – The ham radio failures in more than a view major drills and disasters of the last couple years should serve as major wake-the-heck-up calls for the EMCOMM folks. I’m around a lot of LMR and EMA folks for my day job. Trust me today many of these leaders are not impressed by the local ARES groups and are going to call the MARS folks first. Lot of this is due to past bad experiences and the often correct observation that their MARS teams are both better equipped, better trained, and thus more likely to meet a particular EMCOMM tasking.

If ARES wants to sell itself as the ones to call for when all else fails then ARES better be equipped, trained, and well practiced at operating under such conditions.  Hint – it takes more than fancy radios and go kits.

Second – Please DO NOT send folks into disaster zones with only soundcard modes for Winlink needs. Yes I concede that it sounded like they had to put that HF gear together quickly (didn’t already have it????) with portability and accountability in mind. Still for the love of Pete equip them with quality Pactor modems that are going to work better under the often marginal conditions of such deployments. Keep the soundcard modems as backups if you wish. That “you get what you pay for” saying has some merit to it.  Hint – there are reasons why SCS doesn’t sell soundcard Pactor software when they could make a fortune if they did.

PS – SCS would probably deeply discount Pactor modems to such official staged HF disaster go kits if asked via the proper channels. They have been generous towards good causes in the past. Hint hint hint hint!

Third – Even at this point in the solar cycle, down there, that time of the year, the higher bands will often be your best friends so take appropriate antenna system(s) with you. This “we’ll do it all on 80/40m” mentality continues to be a recipe for failure. 60m NVIS will be handy and having a good antenna for the WARC bands is a really good idea. Be aware that 15-10 meters may not only be open some during the day but may provide some nice SNR on the link. The propagation predictions within the Winlink software are barely useful for the lower bands and can’t predict all the propagation modes on the higher bands. A good op learns HF propagation, understands both solar cycle and seasonal changes, is aware of single/multi hop short skip possibilities on the higher bands, checks the beacon subbands, and tries to use the highest band available for a particular path.

Forth – It seems time for AMSAT to start dreaming big again. Imagine what could be done with a 9600 baud store-n-forward digital bird or two up there. Yes that is easier said than done, but we also need to think beyond HF.

All the above aside, at least some aspects of the KP4 deployments in 2017 were moments ham radio could be proud of even if it was an ugly year for ARES stateside. We also got a real world lesson on the importance of knowing how to handle formal traffic and the NTS folks have things to be proud of.

I see some latched onto the lack of good ICS over the deployment cycle. Not thoroughly knowing both sides of the problems revealed afterwards I would refrain from bashing that aspect of things. As someone that was a first responder for nearly two decades I can tell you that regardless of what you are told beforehand you need to go in prepared to walk right into chaos. You’re not there because things are going well. You must be flexible, able to prioritize, work as a team, and able to adapt on the fly to various surprises. These are situations poorly suited to those that can only function off checklists in textbook scenarios. Ultimately they got a limited crew in, did some good, and then got everyone out safely. Could it of gone better? Of course it could of. There will always be room for improvement.

Non-ham politics of the Puerto Rico disaster? Well in many ways KP4 was a long neglected mess before recent events put it front and center. It did not get that way overnight and it will not be fixed overnight. I think the bigger question is will the repaired infrastructure be well maintained long term? Can their previously struggling economy recover from all that has happened?

WA4ZKO