www.dl2rum.de

Here are the latest changes. Only minor changes were made:

Version 5.1.3 23-March-2012

• New logging time mode added: DL4XT: stops the clock when tapping out of the call sign field
• New Apple Script commands: getHeading, TxRprt, RxRprt and Comment

The Apple Script implementation is completely new, so your scripts may need to be recompiled.
Mike, NF4L uses the getHeading command for his rotor control application. See: http://nf4l.com/rotor/rot.htm


Version 5.1.2 13-February-2012

• cocoaModem doesn't open any longer when uploading LoTW data

Version 5.1.1 31-January-2012

• Option added to suppress qrz.com und HamQTH.com "Callsigns don't match!" messages
• Commands to set the callsign in Fldigi and cocoaModem added (see the Digi menu)
• IC-765 added

Version 5.1 20-December 2012

• Support for the Polish SP-PA award added
• Bug fixes in the County window and in the Multiple QSO Editing routine

Only the application file itself was changed.
Download the full package: http://www.dl2rum.de/rumsoft/RUMlog.zip
Download the application only: http://dl2rum.de/rumsoft/RUMlogApp.zip
Changes: http://dl2rum.de/rumsoft/rumlognews.html

may be a  (PPC) EDIT: 10.4.11 Version one time? tnx!

Version 5.1.4 31-May-2013

• Changes made to work with Fldiigi version >= 3.21.71
• Option added to reset both repots to 59(9) after logging (Preferences—>General)
• Support for 630m and 2.2km band added

Only the application file itself was changed.
Download the full package: http://www.dl2rum.de/rumsoft/RUMlog.zip
Download the application only: http://dl2rum.de/rumsoft/RUMlogApp.zip
Changes: http://dl2rum.de/rumsoft/rumlognews.html

DL2RUM wrote: [*]Option added to reset both repots to 59(9) after logging (Preferences—>General)

nice option, thank you Tom.
The text next to the checkbox says "Reset rst zu 599". Now I know what "zu" means in German

73, de Ulde IK2TYL

I am a very happy user of RUMLog !
Using RumLog ver 5.1.4 on a MacBook Air (1.7GHz, i5 processor) and Mac OS X 10.7.5, 4GB RAM

I have to report following bugs:
1) Using Growl 2.1 I can not see that DX alerts are coming to Growl. Growl is not identifying RumLog as an application either.
2) Rotor direction is faulty with prefixed calls, i.e. HB9/LA0FA as a callsign makes the rotor to point to LA and not HB9. Should be the other way round.
3) By picking up call signs for logging from the band map/DX Spots window not all fields in the logging form are reset, i.e. the manager field is from the previous qso/logging entry.


I hope its ok that I write this report here. Those are cosmetic bugs written here with the intention that future versions of Rumlog are even more perfect !!

Best 73 and keep on the good work with this software.
Matthias, LA0FA

Hi Matthias,
Feedback is always welcome.

1) Using Growl 2.1 I can not see that DX alerts are coming to Growl. Growl is not identifying RumLog as an application either.

No problem here, maybe other users can confirm that? Do you have activated the Growl option in the DX Alarm settings? Please note, only new ones will be announced.

2) Rotor direction is faulty with prefixed calls, i.e. HB9/LA0FA as a callsign makes the rotor to point to LA and not HB9. Should be the other way round.

I can't confirm that. Can you post a screen shot?

3) By picking up call signs for logging from the band map/DX Spots window not all fields in the logging form are reset, i.e. the manager field is from the previous qso/logging entry.

Yes, this is the designed way it should work. This behavior fits better to my workflow. Clear all fields pressing Command W.

Thanks a lot for your quick response !

1)Growl: strange, now I installed 1.2.2 and it works. I will upgrade again to 2.1 and recheck.
2) Prefixed callsign: You are perfectly right, when I test now it works as you say. I need to observe that. I have seen it sometimes like I described, but I obviously jumped to a conclusion here. Sorry.
3) Ok, understand your preference. I need to "learn" the command W prior clicking on call on the band map, I feel this is a hurdle - why would I want to keep a previous QSO´s QSL manager in that field ? However, I have to accept your choice hi.


Matthias, LA0FA

Here you see an example CP6/DF9GR and the beam heading points to DL .....
I get this result by both taking over the call from the band map or entering the callsign manually into the callsign logging field.
Matthias
LA0FA

another example: W1/IK2NCJ ... pointing to Italy instead of W1

73 de LA0FA

Oh, this seems to be another story. Do you use the Auto fill up option from qrz.com?
For these portable stations qrz.com returns the data from home. So the grid square is most probably wrong.
Please check the grid square in the Locator field when you see a wrong direction. RUMlog uses the exact station location for calculation when available.