When time marches across the world, it mostly begins the journey in New Zealand, because only Samoa is ahead of New Zealand by an hour.
Therefore, it is a great privilege for me to make braille real on the bands this year, to celebrate the 208th anniversary of the birth of Louis Braille, in France in 1809.
That is why I will be using the secondary callsign of ZL208BRL on the bands beginning appropriately on the 20th anniversary of the birth of Braille which occurs on 4 January, 2017.
These days, I do most of my New Zealand operating /ZL2 from ZL2TZE in Blenheim, but plan to have the call on the air as /W0 and /W8 when using remotes in Minnesota and Ohio respectively.
I know that many agencies may find interesting ways to publicise the event, but this is my personal desire to make a dot of difference.
Many believe Braille is dead, but while it largely hasn’t quite kept up with all the modern technology, I believe it is still very much relevant in the lives of people for whom it is a native reading and writing method.
In the old days, which I mean before I operated remotely, the common practice was to move a lot of traffic off the net frequency. NCS would direct stations down 3 or 4, or up 3 or 4 KHz, where the action actually took place. This largely still happens, but tonight, I was statled when the NCS sent me down 1 to pass some traffic. I briefly wondered if I’d copied it right. 1Khz? That would seem too close, and certainly would have been back younder, when receivers were wider. They are much tighter today, as I appreciated, after I moved to the newly directed frequency. Since I was using W8KF, he has the automatic mode set so that QSY anywhere automatically sets the mode for the appropriate sideband for the frequency, but I mainly operate CW, so it was necessary to press a few more keys to get back into the internal keyboard, because W8KF doesn’t have the serial interace installed on the server end. After this, I needed to change the mode several times in order to back into CW mode again. I was able to pass traffic even though I was only 1 KHz away from the net, and neither station suffered for the proximity. This was an incredible discovery to make!
Server owners can arrange the order of the modes any way they want.
This isn’t a problem for accessibility, but it can sometimes mean that you may have to hit control m several times before you’ll find that you have got the rig into CW mode.
Also important, even if you know how far around the wheel the CW position is, you can’t press control m in rapid succession to get there, because you must pause briefly, following each press of control m in order to give the rig time to adjust to the new mode being now currently selected.
Therefore, I have found a quicker way to get the rig functioning in the CW mode, that takes less time than all that extra army strategy of hurry up and wait, hi hi.
So here is how I do it.
This stragegy seems to work reliably on all the remotes I use, and more importantly, it doesn’t matter whether the remote has the serial keying interface which both of the Handiham club stations enjoy.
1. Control f and listen for RC Forab to prompt for the new frequency.
2. Enter the new frequency on the numbers row of the keyboard. Note, pay attention to whether the entry should be in Kilohertz or Megahertz, because this does matter, where you are going.
3. Press enter.
4. Press alt shift f and listen for RC Forb to verify that you’re where you believe you should be.
5. Press tab once.
6. Press alt w, then c, twice. The first time you press c, RC Forb should respond with number. The second time you press alt w, c, RC Forb should respond with Edit.
This means you are now in the box for sending.
7. Press a letter, I generally prefer e because as all CW ops know, E is the shortest letter, and therefore, is the least disruptive.
You’ll hear the rig switch to CW.
We held the 4th weekly session of the Handiham CW net on Friday August 19 at 4 pm CDT.
The club station W0ZSW was used remotely from New Zealand, and the performance was great!
Besides WD8LDY/0/NCS, the only other QNI was VE5SDH, though conditions were poor for propagation.
Afterward, a message was formatted for NTS and sent via NTS to VE7KI.
Attempts to locate a sub NCS for running the 2 Septmeber session has not yielded any firm commitment, although Lucinda AB8WF did indicate that she could pick it up if no one else was found.
KE5AL was asked, as was VE5SDH, but Jim was unsure he could make it, and also concerns were mentioned about coverage from his Texas, which were also raised by Summer from Saskatchewan.
We have had a low QNI count, but progress has happened because we’re up to 2 QNI per the last two sessions. Thanks to Summer VE5SDH for joining me, despite some bad QRN. Hope more will join us for a chat next Friday.