www.dl2rum.de

I have had no issues with fldigi, flrig, flwkey, wsjtx with macOS Sierra on a 2012 mac mini.

Winkeyer key 1&2 correlate to the setup gui key designations now. Thanks Billy

I have winkey version 23 per flwkey startup response, tnx Billy NN5EE

I was trying to get cw to work with winkeyer and had to turn key2 line on to get the line connected to key1 to work. Bug?

Yes, "Transceiver" is set as CW Interface in CW menu.

Noting LA0FA's post for the FTdx5000 cw memory, I explored the TS590S/RUMLogNG 1.0.9 CAT keying interactions further. I don't use the TS590S internal keyer much but I do see that the CW window always says "CW interface not available". I can send from the RUMLogNG Software CW memories or from the ...

I have seen this before when deleting made up qso's for testing. Will look at console next time
Tnx Billy NN5EE

Tom; I can verify 1.07 reads HamQTH data for new contacts correctly as far as I can tell. I import many contacts from WSJT-X logs into my main logger, RUMLog classic and hopefully RUMLogNG. Is there a way or are updates planned to allow updating existing qso data from HamQTH or QRZ as there was in ...

I am using 1.0.6 also and receiving DX Spots according to filters. Have one cluster running.

Yes, I am using USB interface. I read elsewhere you can use both interfaces with new 590 2.0 firmware. Haven't tried that yet. Had code break many times in my day using vendor output to draft code by. Been there. I assumed fldigi log entries would be caught and included in RUMlogNB similar to ...