Page 1 of 1

RUMlogNG version 3.1

Posted: Wed 28. Dec 2016, 18:02
by DL2RUM
What's new?
  • Fixed: Station Info Box shows correct distance now when english units are used - Tnx KH6BE
  • Fixed: Printing 60m QSLs without a Crash now - Tnx DK5LP
  • Fixed: Scrolling in the log using the arrow keys works doesn't cause the app to crash - Tnx N9JR
  • Change: New rules for the Helvetia Contest implemented
  • Change: New rules for the NAQP implemented
  • New: A row for the QSO serial number can be shown in the log table now. These number is valid for the seen QSOs only!
  • New: QSL label format Avery 5363 (2-13/16" x 1-3/8" at US Letter, 3 x 8)
  • New: Changes made for latest microHAM firmware updates (MKII: 6.7, DKII: 3.6)
  • New: Added few Apple Script commands required for JT-Bridge, see function library
  • New: Support for 60m added in:
    • Station Info Box
    • DXCC Info Box
    • Paper QSL In Info Box
    • Paper QSL Out RIG Text
    • DXCC List and counter
    • DX cluster

Available in the App Store now: https://itunes.apple.com/app/rumlogng/id964454561?mt=12

Download the latest version here: http://dl2rum.de/RUMlogNG/RUMlogNG.zip Please note, Apple Maps will not work in this version!

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

For printing (Version 2.11 - English, ca. 25Mb): http://dl2rum.de/RUMlogNG/docs/RUMlogNG_english.pdf
For printing (Version 2.11 - German, ca. 26Mb): http://dl2rum.de/RUMlogNG/docs/RUMlogNG_deutsch.pdf

Re: RUMlogNG version 3.1

Posted: Thu 29. Dec 2016, 22:38
by IV3TMM
Hi Tom, you miss this ...

http://dl2rum.de/forum/viewtopic.php?f=10&t=917

Please update. TY.

Re: RUMlogNG version 3.1

Posted: Fri 30. Dec 2016, 00:46
by DL2RUM
I don't missed that. Changes are not planned. DXCC can't be set to 0 according the ADIF specification.

Re: RUMlogNG version 3.1

Posted: Wed 4. Jan 2017, 02:29
by va3cp
Hello Tom,

First of all, Happy New Year.
Just installed 3.1 and was looking through the modes and do not see MSK144 which is part of the WSJT-X package.
Any plans to add this into the mode list? I just made a contact using MSK144 and don't see how to log it.

Thanks....

Dave, VA3CP

Re: RUMlogNG version 3.1

Posted: Wed 4. Jan 2017, 09:32
by DL2RUM
Hi Dave,

RUMlog allows you to log ADIF specification conform modes only, see here: http://adif.org/304/ADIF_304.htm#Mode_Enumeration
This is due to compatibility reasons.

If you want to use other than listed modes on your own risk and with unknown side effects, you can edit the file Modes&Submodes.txt. The format is simple:
Mode, submode, submode, submode, …
Mode, submode, submode, submode, …

The file is located in your users directory: ~/Library/Containers/de.dl2rum.RUMlogNG/Data/Library/Application Support/de.dl2rum.RUMlogNG/

Re: RUMlogNG version 3.1

Posted: Wed 4. Jan 2017, 13:31
by va3cp
Thanks Tom,

I think I will leave well enough alone.

Re: RUMlogNG version 3.1

Posted: Fri 6. Jan 2017, 05:00
by ik5zui
Hi Tom,
I'm not able to to edit QSO on the contest window. When I try the window become "transparent".
Is it possible to fix it?
Thanks!

Re: RUMlogNG version 3.1

Posted: Fri 6. Jan 2017, 06:50
by DL2RUM
I can't see this problem here.
Please check Console for Error messages while you go into the Edit mode.
Which macOS version do you use?

Re: RUMlogNG version 3.1

Posted: Mon 9. Jan 2017, 10:07
by M0CLH
WSJT-X 1.7/JT-Bridge 2.0.1 seem to have stopped working with this release. Fldigi is fine but no CAT control with the others. Any ideas? Running OS X 10.10.5.
Thanks, Terry, M0CLH

To clarify, it's ok from fresh boot, run RUMLogNG, initialise IC-7300, run JT-Bridge and then WSJT-X. The problem seems to arise when JT-Bridge and WSJT-X are terminated, Fldigi is used (successfully) and terminated before JT-Bridge and WSJT-X are restarted. CAT control is then lost until machine is switched off and restarted. Hope that helps.

Re: RUMlogNG version 3.1

Posted: Mon 9. Jan 2017, 17:41
by ik5zui
DL2RUM wrote:I can't see this problem here.
Please check Console for Error messages while you go into the Edit mode.
Which macOS version do you use?
Thanks for your message.
I'm using OSX 10.10.5.