Page 1 of 2

Digi modes etc.

Posted: Fri 11. Nov 2011, 14:23
by NF4L
I'm a New Mac and Rumlog user.

The Rumlog interface to CocoaModem isn't working, although if I run CocoaModem without Rumlog it works, and if I click Window on the Rumlog screen and evoke CocoaModem program it works in that CocoaModem instance. That usually brings up CocoaModem in Wide RTTY, which is not what I expect.

Clicking the Controls button does nothing.

Are there plans to add rotor control?

Is it possible to have Rumlog.app in the Application folder without breaking any links to data?

Thanks,
Mike NF4L

Re: Digi modes etc.

Posted: Fri 11. Nov 2011, 15:16
by DL2RUM
That usually brings up CocoaModem in Wide RTTY, which is not what I expect.
What do you would expect? The Wide RTTY modem is the only one available in the cM Lite Interface.

Are there plans to add rotor control?
No, I don't own any.

Is it possible to have Rumlog.app in the Application folder without breaking any links to data?
You have to keep all files in the same folder, see the manual for the required and used file names.

Re: Digi modes etc.

Posted: Fri 11. Nov 2011, 23:43
by NF4L
Thanks Tom.
Well, I was not aware that wide rtty was used by the interface. I'll have to dig into the CocoaModem docs.

What about the "Control" button?

Do you know if CocoaModem or Rumlog sets the mode on the radio? I have an Elecraft K3, and it gets switched from AFSK to FSK somehow.

73, Mike NF4L

Re: Digi modes etc.

Posted: Sat 12. Nov 2011, 06:03
by DL2RUM
You should use the Wide RTTY interface, even when using cocoaModem stand alone. The other RTTY modems are still operational, but depreciated.
cM don't have any rig control features, I guess you have your K3 connected to RUMlog. Only one application can use the COM port for a given time.
In the RUMlog preferences under the TRCVR tab you can select the K3 operation mode when you want to work RTTY. The default is FSK-D, what I prefer.
The "Control" button brings up the cocoaModem Control window (crossed bananas), while using the cM light interface.

Re: Digi modes etc.

Posted: Sun 13. Nov 2011, 14:23
by NF4L
Thanks again, Tom.
Rumlog is the only logging program I've liked that I didn't write. :lol:

I'm still unable to get the "Controls" button to do anything on the RL digi interface. Or did you mean it brings up the crossed bananas on the CM screen?
I'm using AFSK. I don't have an FSK interface for the K3.

I also cannot get the LoTW TQ8 out to be enabled. I have TQSL.exe in the RL directory.

The LoTW ADIF is enabled, but it writes a zero length file.

I wish I could persuede you to add rotor control. :D

73, Mike NF4L

Re: Digi modes etc.

Posted: Sun 13. Nov 2011, 14:40
by DL2RUM
Or did you mean it brings up the crossed bananas on the CM screen?
Yes, but this is applicable in the cocoaModem lite interface only.
I have TQSL.exe in the RL directory
You will need TQSL.app !!!
The LoTW ADIF is enabled, but it writes a zero length file.
You should get an error message, or an info about the written QSOs. Maybe there are no QSOs to send?

Re: Digi modes etc.

Posted: Mon 14. Nov 2011, 16:58
by NF4L
DL2RUM wrote:Yes, but this is applicable in the cocoaModem lite interface only.
Sorry, I still don't understand if the crossed bananas are supposed to appear on the Rumlog screen titled "cocoaModem - Tnx Chen, W7AY" or on the CocoaModem sceen titled "cocoaModem 2.0"
You will need TQSL.app !!!
Yes, of course. :oops:
You should get an error message, or an info about the written QSOs. Maybe there are no QSOs to send?
It does tell me there are 0 QSOs. The LoW column in the log are all set to "s". I'm unsure how that happened. Would a field in the original ADIF input have done that?

In addition to the plea for rotor control, I'd like to suggest when double-click a QSO in the log table, it is put into the log entry fields in edit mode. :idea:

73, Mike NF4L

Re: Digi modes etc.

Posted: Mon 14. Nov 2011, 17:32
by DL2RUM
cM.png
The Control button brings up the red marked control window, the "Open Controls" button on the cocoaModem main window has the same effect. The window button toggles the yellow marked main window.


It does tell me there are 0 QSOs. The LoW column in the log are all set to "s". I'm unsure how that happened. Would a field in the original ADIF input have done that?
I don't know if there were LoTW tags in your ADIF file. You can mark all the affected QSOs and select Menu-->QSL-->Send again LoTW QSL

Re: Digi modes etc.

Posted: Mon 14. Nov 2011, 22:57
by NF4L
Tom, thanks again so much!

I do not get the red marked window, nor can I find the "Open Controls" button on the cocoaModem main window. I have cocoaModem 2.0 v0.95. It is not a big deal, and I would just as soon not even evoke the cocoaModem main window. How does the tuning indicator in the lite screen work?

I actually have read the user manual :D

73, Mike

Re: Digi modes etc.

Posted: Mon 14. Nov 2011, 23:20
by K6LE
NF4L wrote: I'm still unable to get the "Controls" button to do anything on the RL digi interface. Or did you mean it brings up the crossed bananas on the CM screen?
I'm using AFSK. I don't have an FSK interface for the K3.
Mike,

You don't need an FSK interface with the RUMlog and the K3.

If you set the Digi preferences to "cM (RX + K3 (FSK)" then it will use the K3's internal FSK generator driven by the serial port.

Just make sure you are on the other stations frequency, or better yet operating split you don't have to even worry about that!

RUMlog is the only program I've seen that will use the internal K3 FSK like this.