RUMlog controls K4

[Rick Tavan-2]

FWIW, I have very little experience with RUMlog (or Skookum Logger which
may be a predecessor) but if you use RUMlog on your Mac you may be
encouraged by this tidbit: I have it running on MacOS Catalina doing rig
control of the K4 via the USB B port, calling it a K3. I'm keying CW
through the CAT interface which probably means CAT1ASC commands although
the documentation doesn't say. I've used both the general interface and the
contest window, both just enough to believe they work.

If you're a RUMlog expert waiting for your K4 and want to discuss, feel
free to contact me directly.

/Rick N6XI
--

Rick Tavan
Truckee and Saratoga, CA
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]

[Bill Frantz]

On 3/30/21 at 7:33 PM, [hidden email] (Rick Tavan) wrote:

>FWIW, I have very little experience with RUMlog (or Skookum Logger which
>may be a predecessor) but if you use RUMlog on your Mac you may be
>encouraged by this tidbit: I have it running on MacOS Catalina doing rig
>control of the K4 via the USB B port, calling it a K3. I'm keying CW
>through the CAT interface which probably means CAT1ASC commands although
>the documentation doesn't say. I've used both the general interface and the
>contest window, both just enough to believe they work.

I have run RUMlogNG for several years, including using it for CW
and RTTY contests. I have even hooked a protocol analyser up on
the RS-232 link between it and the radio to try to chase down a
problem. It has a very interesting approach to sending and
receiving CW and RTTY through the K3. It does both through the
CAT interface. To transmit, it uses KY and TB commands to keep
the radio from buffering more than 2 or 3 characters so the ESC
key will stop transmission promptly.

For example, to send AE6JV<space><eot> with the K3's response in [brackets]:

KY A;[KY0;]TB;[TB000;]
KY E6;[KY0;]TB;[TB200;]
KY J;[KY0;]TB;[TB200;]
KY V;[KY0;]TB;[TB300;]TB;[TB200;]
KY  ;[KY0;]TB;[TB300;]TB;[TB200;]
KY
<04>;[KY0;]TB;[TB300;]TB;[TB200;]TB;[TB100;]TB;[TB000;]TB;TB000; etc.

I have not carefully traced the receive path.

The problem I was trying to track down is the failure to
correctly chain transmissions in RTTY mode. CW works fine. If,
for example, I press F4 twice to send my call sign twice, the
radio will transmit AE6JV E6JV, dropping the first character
from the second press of F4. I used my KX3 to monitor what was
actually being transmitted. I got lots of useful advice from
N6TV in running these tests.


>If you're a RUMlog expert waiting for your K4 and want to discuss, feel
>free to contact me directly.

I won't say I'm a RUMlog expert, and I'm waiting for the K4 kit,
but if I can help, please let me know.

73 Bill AE6JV


-----------------------------------------------------------------------
Bill Frantz        | The race is not always to the swift, nor
the     |
[phone]      | battle to the strong, but that's the way to
bet. |
www.pwpconsult.com |       - Damon
Runyon                             |

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]