www.dl2rum.de

This results in sending reverse. You haven‘t mentioned, you use an external device. But I'm not using an external device to my knowledge. The FSK is generated in the K3, I'm sending the text from the contest module software, OR I can use the internal keyer sending manual CW to result in RTTY out to...

DL2RUM wrote: ↑Sat 10. Feb 2024, 10:39 Revers? Wrong shift? Wrong baud rate?

Thank you. It was a POL setting that isn't even mentioned in the manual, In the MENU CONFIG settings there is an FSK POL selection. Choices are 0 (zero) or 1 (one). When I set it to 1 I was successfully decoded.

Thank you again.

It's been a very long time since I've run RTTY in this configuration, but I had a notion to participate in the CQ-WPX-RTTY contest this weekend. I set it all up and everything looks good. I can hear and decode other users and I'm sending messges seemingly OK, BUT no matter who I call, they cannot de...

I'm using a CAT interface through a USB adapter. The radio is using FSK. This is on my Elecraft K3. Also, FYl I tried an older RUMlog version. I went back to version 5.9 and it works just fine in this setup. (I had been using 5.11 before I installed version 5.12, but apparently I didn't keep that in...

I'm working in RUMlogNG version 5.12 and trying to set up for CQ WPX RTTY this coming weekend. It seems to be working fine except for the function key messages. No matter what I try, the program insists on sending every message twice, the second immediately after the first with no break at all betwe...

DL2RUM wrote: ↑Sun 11. Oct 2020, 16:03

Hope this helps.

Not really. Could you e-mail me your log file for further investigations?

OK, I'll attach It to an email and send it your way.

Let me change that, based on a different discovery. The changes that I made that had times the same as I had before were done using the logbook mask in the Search QSOs window. If I make the same type of change in the main log window, the times are much shorter. I did a change on an S50 callsign (16...

I made a test log with 210.000 QSOs. Now I can notice a hung, pending on the number of affected QSOs. While editing a QSO with S01 doesn't show any delay, there is a hung of up to eight seconds when editing a QSO with a DL station (22.000 Qs in the log) I addressed a performance problem and made fe...

I made a test log with 210.000 QSOs. Now I can notice a hung, pending on the number of affected QSOs. While editing a QSO with S01 doesn't show any delay, there is a hung of up to eight seconds when editing a QSO with a DL station (22.000 Qs in the log) I addressed a performance problem and made fe...

in a log of over 175K QSOS. Every time I make an edit to a QSO, I have a spinning rainbow wheel for at least 18 to 20 seconds before the log is usable again I will check if I can create a so huge file, 20 seconds are not acceptable. I agree. Actually, that time comes from a check done some time ago...