RUMlogNG and RUMped here as well. Have been using them for several years and am extremely happy. I use it on a MacBook Pro with my K3 at home and then portable with my KX3. Integration is great with Elecraft gear.

I use FLdigi for PSK and RTTY, which integrates well with some applescript so the logging is done to RUMlogNG. Works very well and there are examples and samples out there.

Tighe
NK4I


On 7/10/15 8:08 AM, Joel Black wrote:
Byron,

When I switched from Windows to Mac, my first logging program was Aether 
Logging. Don’t bother with it. The author is completely unresponsive to help 
and requests for improvement. I shoved $50 up a wild hog’s butt and just yelled 
“Suey!” That’s been two years ago and I’m still ticked about it.

I found RUMlog and haven’t looked back. It’s free. The author has a forum page 
where he is *extremely* helpful to both problems and requests for improvement. 
The newest version is RUMlogNG and is available from the app store.

Once you get used to the Mac, you’ll never want to see another Windows machine. 
Unfortunately, I have to use Win7 at work and I *hate* the way it does things.

73,
Joel - W4JBB

On Jul 10, 2015, at 6:37 AM, Byron Peebles <[email protected]> wrote:

With my migration from TenTec to Elecraft, I was planning to also move my 
logging and station control from Windows to MacOSX.  I have found sources like 
DogParkRadio to be tempting, but I wanted to check with Elecraft users on which 
packages best support the K3 (and upcoming K3S).

I use mostly HF CW/SSB, but rotor control (M2),, LoTW, DX Cluster integration 
are important.  And I might try other digital modes in the future.

73, Byron
______________________________________________________________

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[email protected]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [email protected]

Reply via email to