Search found 28 matches
- Thu 15. Oct 2026, 19:32
- Forum: RUMlogNG
- Topic: LoTW In Broken?
- Replies: 10
- Views: 468
Re: LoTW In Broken?
You are right! Remember that funny message I received when I initially tried dragging RUMlogNG into the applications folder? That must've caused some funny system cache thing due to permissions. I may not have had the proper permissions set for the older RUMlogNG file. I copied and pasted the new ...
- Thu 15. Oct 2026, 18:18
- Forum: RUMlogNG
- Topic: LoTW In Broken?
- Replies: 10
- Views: 468
Re: LoTW In Broken?
I spoke too soon! The LoTW In function has stopped working now.
After a few hours away from the station computer, I tried again. No window.
After a few hours away from the station computer, I tried again. No window.
- Thu 15. Oct 2026, 12:21
- Forum: RUMlogNG
- Topic: LoTW In Broken?
- Replies: 10
- Views: 468
Re: LoTW In Broken?
Whatever you did seems to have fixed that issue. The proper window appears and I get LoTW downloads. Funny thing is, when I moved the application into the Applications folder, I got a pop-up telling me: The operation can't be completed because some items had to be skipped. For each item, choose File ...
- Thu 15. Oct 2026, 01:32
- Forum: RUMlogNG
- Topic: LoTW In Broken?
- Replies: 10
- Views: 468
Re: LoTW In Broken?
macOS 15.8.2 Sequoia. (No Apple Intelligence...) Here's the thing. Before upgrading to this version of RUMloigNG, it all worked perfectly with this version of macOS which I didn't change. I just did another test. I have RUMlogNG installed on a second machine running macOS 15.8.2, just as with the ...
- Wed 14. Oct 2026, 22:18
- Forum: RUMlogNG
- Topic: LoTW In Broken?
- Replies: 10
- Views: 468
Re: LoTW In Broken?
I looked everywhere, too. The window must be invisible.
Also using the latest version of Sequoia, although that same version worked fine before upgrading RUMlogNG.
Also using the latest version of Sequoia, although that same version worked fine before upgrading RUMlogNG.
- Wed 14. Oct 2026, 14:34
- Forum: RUMlogNG
- Topic: LoTW In Broken?
- Replies: 10
- Views: 468
LoTW In Broken?
It seems like the LoTW In function does not work in the very recent RUMlogNG update. When I click on LoTW In using the mouse or use the keyboard command, nothing happens. It's like the mouse or the keyboard has no effect. No errors or anything of the sort. LoTW out for new QSOs works as always, with ...
- Sat 27. Dec 2025, 19:34
- Forum: RUMlogNG
- Topic: WSJT-X Not Connecting in version 6.0
- Replies: 2
- Views: 7399
Re: WSJT-X Not Connecting in version 6.0
Yes, "localhost" was the UDP Server field. Changing to 127.0.0.1 fixed it.
Thanks!
Clarke K1JX
Thanks!
Clarke K1JX
- Sat 27. Dec 2025, 17:06
- Forum: RUMlogNG
- Topic: WSJT-X Not Connecting in version 6.0
- Replies: 2
- Views: 7399
WSJT-X Not Connecting in version 6.0
For some reason, the latest 6.0 is not connecting to WSJT-X through UDP. Everything else works fine, but there is no connection, so logging doesn't happen. Reverting back to 5.2 fixes the problem, with no change in Settings. This is what the Network Status looks like with 5.2: Screenshot 2025-12-27 ...
- Wed 23. Apr 2025, 02:19
- Forum: RUMlogNG
- Topic: USB-C Serial Adaptor
- Replies: 3
- Views: 8400
Re: USB-C Serial Adaptor
Well, you were right, in a way. It wasn't the levels. It's that RS-232 is inverted TTL, at least for Elecraft radios. I found a comment to that effect buried in a forum from years ago. But, I learned that FTDI based USB to serial parts can be easily programmed. (And, bricked I'm told.) FTDI offers a ...
- Tue 22. Apr 2025, 16:46
- Forum: RUMlogNG
- Topic: USB-C Serial Adaptor
- Replies: 3
- Views: 8400
Re: USB-C Serial Adaptor
That is a good thought, but according to N6KR:
"The input can accept the full RS232 range, +/- 25 V. But 0-5 V will
also work. In fact 0-3 V will work."
I'd think he would know, but he made that comment early on in KX3 production and things could have changed.
I'll keep looking.
"The input can accept the full RS232 range, +/- 25 V. But 0-5 V will
also work. In fact 0-3 V will work."
I'd think he would know, but he made that comment early on in KX3 production and things could have changed.
I'll keep looking.