RUMlogNG version 4.4.1

[DL2RUM]

RUMlogNG 4.4 is available for direct download here:
http://dl2rum.de/RUMlogNG/RUMlogNG.zip
Available in the App Store: https://itunes.apple.com/app/rumlogng/id964454561?mt=12

English manual: http://dl2rum.de/RUMlogNG/docs/en/
German manual: http://dl2rum.de/RUMlogNG/docs/de/

What's new?

• Fix: Unwanted scope mode switching (IC-7300/7610/9700) - Tnx Terry, M0CLH
• Fix: Rule changes for the Pennsylvania QSO Party added
• Fix: ITU Zone for CE corrected
• Fix: ADIF tag prop_mode added for satellite QSOs to the eQSL upload
• Fix: Satellite QSOs will be clearly marked on printed QSL labels
• New: Changes in the DXLab Suite Commander Server for more flexibility when using two transceivers
• New: Autodiscovery function for the IC-9100
• New: Contextual menu added to the contest interface QSO table
• New: SCC RTTY Championship
• New: SARTG WW RTTY Contest
• New: WW Digi Contest

[LA0FA]

Hi, I suddenly noticed that current version is not accepting VFO changes from WSJT-X program, hence the Fake Split operations in WSJTX is not operational anymore. It seems to me that its the RumLogNG side which causes the program. Appreciate if you can check. 73 de LA0FA

[DL2RUM]

Which trx do you use?
Where do you have configured your Dx Suite Commander Settings? Under the TRX tab or under the UDP tab?

[LA0FA]

IC7610. I have added screenshots for TRX/UDP from RumlogNG and Radio from Wsjtx.

[DL2RUM]

Which exact RUMlog version do you use? See the About menu. Do you have configured two transceivers? I'm wondering, your Auto Discovery function isn't available (grayed out in your screen shot?). The port name could change every power up and the Auto Discovery will fix that problem.

Further more you have set two PTT options, this may cause trouble. When you enable CAT as PTT Method in WSJT-X the tcp/ip CAT connection will be used. A working CAT connection is required.
When you enable Switch PTT in the RUMlog UDP settings, RUMlog watches the PTT status via the UDP broadcasts. A CAT connection is not required.

But I can't duplicate your problem, I use the IC-7610 here as well. I tried your settings with success. I got few reports with the same problem, so I guess there is a real issue. But I never got a feedback, maybe the problem is gone.
Try this:

• In RUMlog deactivate Exchange CAT data in Preferences-->UDP-->WSJT-X
• In RUMLog activate Start in the Preferences-->TX1-->Dx Lab Suite Commander
• Watch the Network window for status messages.

[LA0FA]

Hi again and thanks for all suggestions, I have tried them all and the problem remains. As I do not keep any of the older versions of rum log so I don't know when this feature stopped working. I use the latest 4.4 (355). I have also changed the PC - on my iMac I have High Sierra and on my MacPro I have Mojave but its the same on both. By the way: the auto discover only works on Mojave. So until further I will have to operate the wsjtx without split parameter and rather modulate with the real audio frequency. I don't operate a second TRX.

[DL2RUM]

Correct, the Auto Discovery works in Mohave only. Is the CAT control bubble in WSJT-X green?

[LA0FA]

yes its green

[fpz]

Hi,

I'm seeing a similar and possibly related issue, rig control in WSJT-X stopped working.

Setup:
macOS Mojave 10.14.6
WSJT-X v2.1.0 24fcd1
RUMlogNG 4.4 (355) using these settings:

Network Status messages:

Code: Select all

20:34:47 [localhost] WSJT checked in
20:40:37 [Local] Listening to WSJT-X on port 2237
[DxLab Cmdr #1] 20:40:50 Connection established to: localhost
20:40:54 [DxLab Cmdr #1] Closed connection to localhost: Socket closed by remote peer

WSJT-X shows this error when trying re-enable the Rig in the Radio configuration tab:

This setup was working in the previous version (installed and updated from the App Store). If there's any other information from logs that I can collect or if there's something I can do to help debugging the issue please let me know.

Best regards,
fpz

[DL2RUM]

Can you still set the trx mode and frequency from RUMlog? (double click on the frequency from a dx spot, or just enter a frequency into the callsign field).

I appreciate any help, I would prepare a version to find the problem. I would continue the conversation via e-mail.