As I've recited in my "Success" thread in the forum, I've actually figured out how to have success with the built-in memory keyer. Greedy fellow that I am, however, I want even more.

And, by the way, I think I'm the "purest" operational experiment Flex Radio has going just now (though I'd love to be contradicted here):

1. I have probably the worst antenna. Certainly the worst I've ever used for this sort of thing. 2. I have no accessories such as Griffin Knobs nor, presently, my keyer, in use. 3. I don't even have a second receiver for comparison. I have to go on the air to find out (e.g.) if my SSB has reverb, depending on the kindness of strangers -- or the glories of Teamspeak. 4. My sole amplifier -- at present -- is the PA. Eventually, I'll have a big amp for 80. If I go by my own history, that's probably all I'll use it for. Maybe 20. Maybe. And, that's tomorrow anyway.

And, as my SDR-only country count goes north of 75, I'm beginning to find it expedient to enter full-bore, "professional" grade pileups.

It is a thrill to report that I have won a few of these.

However, it's when I lose that contemplation begins. Clearly, a better antenna and more power would have helped some of it. But, I've always won before with comparable power. So, it is natural for me to look for seeming small, but none-the-less vital improvements to our favorite rig.

Thus, the very nature of my operation will put every detail of this thing we love under the microscope. I accordingly hope that the people who matter will continue to read my little success thread and see if inspiration strikes.

If nothing else, a lot of that thread is a valentine to the many things that work very well and those that made them so. In a radio that begs for improvements by its very premise, it's easy to lose sight of how far we've come and how much a determined operator can get out of it as it stands. I've gone from barely being able to talk to Texas with Teamspeak for a "liason frequency" to working the world in only a few short weeks.

Still, my recent experiences have lead to a dream, one that I'll recite here. This one may be difficult for the radio as it stands, but it is a dream none the less.

I have said in the forum that I miss my MFJ paddle/Bencher keyer. That's really kind of half true. What I miss is: semi-break in, and the ability to use my keyer to answer the DX' questions or come up with unique responses.

In truth, most of the time, the memory keyer is actually better. What better way to loop my call two or three times in marginal conditions without me having to key over and over? What better way to insure I never, ever mess up my call sign when I've got the attention of Mr. Rare DX? And so on.

The problem is, without this dream, I may have to abandon it in whole or in part.

What I want is easy to describe, but may be hard to do.  What I want is:

1. If I click on "memory", then the memory keyer is operational as it is today. 2. If I as much as touch my paddle, however, I want the PC/Flex combination to somehow detect this and turn on the last known keyer mode, be it straight key (so my external keyer would work as I have it) or as the right kind of iambic mode (if that's how the other fellow has it set up) and start operating the keyer from the first touch (finishing the current memory character -- or not -- is something we can discuss as I can see advantages both ways). 3. Pressing the memory radio button will again select memory keying at the next "send" key pressing.

It is 2, I suspect, that may prove the hard part. If we have a good solution for break-in and not chopping the first character, as I have been promised is coming, then this might work.

Another option that might be even better (and easier to implement, perhaps) is a new radio button that says "memory plus keyer". Here, pressing "send" on the display starts sending from the current memory setting as now, but pressing the external keyer causes that to take over until the "send" button is again pressed on the form. As before, the last setting of the external keyer would be respected for this.

This mode of operation, especially the second form, probably implies semi-break-in is enabled. But, since I presuppose that works for this, it isn't a problem to have it come on or at least come to its last known state. The more I think about it, the more likely the second option would be the better design for usability and coding.


Larry  WO0Z



Reply via email to