New RUMlogNG user here. MacOS Sonoma 14.7 on MacBook Pro (Intel). The transition from my old logger has gone well, but this morning I have two issues, which may or may not be related.
1. When I launched RUMlogNG, my iCloud-synced log did not open. Logbook -> iCloud synced logbook showed all options grayed-out. Typing command-M brought up an empty log. Rebooting the computer did not resolve it. Eventually, I opened an old .rlog file on my computer and then tried Logbook -> iCloud synced logbook -> Use it, and it worked, bringing up my log.
2. Once my logbook was back on the screen, I logged a new contact and observed that the date and time were set to 1/1/2014 and a time I don't recall. I could manually change them, but the date and time in the logging window continue not to track the computer.
Help, please?
Thanks,
Eric KB1VUN
date & time in logging window not tracking computer
Re: date & time in logging window not tracking computer
Set the logbook time to real time clock. There is a popup menu below the date read out.
73 and best dx de Tom, DL2RUM
Re: date & time in logging window not tracking computer
I saw that in the manual, but mine does not have it. Instead, it has a selector for "Log QSO end time" / "Log QSO start time" / "Enter time manually".
Eric

Eric

Re: date & time in logging window not tracking computer
Also...I see the behaviors described in my original post with both RUMlogNG versions 5.17.1 and 5.18.1.
To this may be added a third and a fourth issue:
3. The mode box has stopped following the transceiver frequency (it used to work).
4. I have never before tried the trick of typing a frequency into the callsign box to tune the transceiver, but after I read about it today I tried it and it does not work.
Not meaning to pile on here, just hoping to provide additional clues that may help with troubleshooting.
Eric
To this may be added a third and a fourth issue:
3. The mode box has stopped following the transceiver frequency (it used to work).
4. I have never before tried the trick of typing a frequency into the callsign box to tune the transceiver, but after I read about it today I tried it and it does not work.
Not meaning to pile on here, just hoping to provide additional clues that may help with troubleshooting.
Eric
Re: date & time in logging window not tracking computer
It seems your CAT control is not working properly.
73 and best dx de Tom, DL2RUM
Re: date & time in logging window not tracking computer
I switched to my usual contest logging program, and CAT control is fine. WSJT-X, standalone, also has functional CAT control.
Would lack of CAT control explain these issues?
1. No log automatically opens when RUMlogNG starts up. I have to type command-M, which brings up my current log, but empty, then do some clicking around to make the entries appear.
2. The log does not pick up date and time from my computer (the other programs do). It comes up 1/1/2014, 11:00:00. It can be manually set, but does not track the computer's clock. There is no "real time" checkbox under the date and time boxes.
The program was working fine until about three days ago. Might this be a case of a corrupted preferences file?
Eric
Would lack of CAT control explain these issues?
1. No log automatically opens when RUMlogNG starts up. I have to type command-M, which brings up my current log, but empty, then do some clicking around to make the entries appear.
2. The log does not pick up date and time from my computer (the other programs do). It comes up 1/1/2014, 11:00:00. It can be manually set, but does not track the computer's clock. There is no "real time" checkbox under the date and time boxes.
The program was working fine until about three days ago. Might this be a case of a corrupted preferences file?
Eric
Re: date & time in logging window not tracking computer
You use Real Time, when you don't have selected Enter time manually.There is no "real time" checkbox under the date and time boxes.
Since we do not know anything about your hardware setup and your CAT settings, you can't expect an useful answer.Would lack of CAT control explain these issues?
73 and best dx de Tom, DL2RUM