I've been a Logic user for maybe 20 years--there's a lot I love about Logic, but I have to say it is just not keeping up with the ham radio world that I know. I thought maybe when you began the annual subscription, maybe things would pick up, but I honestly don't see it.

More than five years ago you said you would add a MMTTY interface. Let that sink in. Five years ago.

Four years ago you said you were reluctant to commit to a delivery date. Four years ago.

Two years ago you said you were "finalizing" the JT-65 interface and then would get on MMTTY. JT-65 has been overcome by events (FT-) for years, and you are still promising to maybe one day get that delivered. Then maybe work in the MMTTY you committed to five years ago.

C'mon, really? Is that what we can expect going forward?

Dennis, for those of us who have paid the annual subscription, I think you owe us an answer on when you will deliver on these ancient commitments. I don't care if you miss by a week, or even a month. But five years in you still give me no idea if you are ever really going to deliver. I think I paid for better than that.

Like others, I like many things about Logic, and I'd hate to go through the learning curve to get up to speed with new logging software. But more than half the contacts I am logging these days are FT-8, and Logic no longer passes muster for what I do. If something doesn't give soon, I'm simply going to have to move on.

Dave KE4UW

Dennis, are you "listening"?

REALLY????

Dennis,
Since you are working on some of the requested changes, let me offer a few suggestions. The things I'd most like to see are:

Integration with WSJT-X so that QSOs logged in WSJT-X are also logged automatically in Logic. In addition to simplifying logging, this would also allow use of Logic to send spots to the DX cluster for the FT-8 QSOs made using WSJT-X (something that’s way too difficult in the current version of Logic).

Capture decoded signals from WSJT-X in the spot log in Logic (possibly by integration with JT-Alert software), thus providing the standard spot log info on whether that entity is needed on that band/mode. Preferably this would have some sort of timer so multiple decodes of the same call sign/frequency don’t get sent to the spot log every 30 seconds.

Support upload to Clublog similar to what currently exists for LOTW, with options to upload entire log, or only new QSOs since last update.

Add some kind of RTTY interface, preferably MMTTY, to allow making and logging RTTY contacts from within Logic.

Fix glitch during logging that deletes DXCC entity of previous logged QSO if ESC is hit to clear the log screen. So here’s the scenario: You click on an entry in the spot log so the radio moves to the right frequency and mode, and the call sign information is entered in the Logging screen. But you are unsuccessful in completing the qso, so you hit ESC on the keyboard to clear the log screen and not enter the QSO in the log. When this is done, the entry for the DXCC entity for the PREVIOUS QSO is deleted. Its sort of an annoying back door way to inadvertently inject errors in the log that will need to be sorted out manually later. Note that if the ESC icon on the logging screen is used, the previous logged QSO is not affected—as should be the case. (It took me quite a while to figure out why so many logged qsos had a blank DXCC entity, when this is auto-filled when the qso is logged!)

In the Tools menu, have separate options to disable/reset the various radio and rotor interfaces individually. I often need to disable one radio interface in Logic so I can use WSJT-X. However, it would be nice to still be able to use the rotor interface, and the radio interface for a second radio. (maybe the keyer too?). One way to do this would be to have the Tools menu selection bring up a list of the interfaces and let the user select which one(s) to disable/reset.

I certainly wouldn't want to delay any pending update, but just thought I'd offer my wish list.

Dave KE4UW

We've all been waiting for MMTTY for over 5 years now. Don't hold your breath.

Just to add my wishes to the discussion:

1) Support upload to Clublog similar to what currently exists for LOTW, with options to upload entire log, or only new QSOs since last update.

2) Add some kind of RTTY interface, preferably MMTTY, to allow making and logging RTTY contacts from within Logic.

3) Fix glitch during logging that deletes DXCC entity of previous logged QSO if ESC is hit to clear the log screen. So here’s the scenario: You click on an entry in the spot log so the radio moves to the right frequency and mode, and the call sign information is entered in the Logging screen. But you are unsuccessful in completing the qso, so you hit ESC on the keyboard to clear the log screen and not enter the QSO in the log. When this is done, the entry for the DXCC entity for the PREVIOUS QSO is deleted. Its sort of an annoying back door way to inadvertently inject errors in the log that will need to be sorted out manually later. Note that if the ESC icon on the logging screen is used, the previous logged QSO is not affected—as should be the case.
Some days ago I made a Log (Search: DXCC = Empty) and manually corrected 75 QSO, as I earlier have done too. Would of course be nice to avoid...

WSJT-X has not yet infected my station, but may be come...

Just for letting you know...

Best 73 Carsten / OZ4CG

Please ask him to contact me.

Sincerely,

Dennis WN4AZY