www.dl2rum.de

Few important commands for CW are missing. Was it for canceling the transmission? I can't remember, but there was reason for that.
Please note the RUMlog internal CW keyer, this one is more reliable and better integrated: https://dl2rum.de/RUMlogNG/docs/en/page ... al_CW.html

I would like to have the problem resolved. Of course, I can't rule out the possibility of an error in RL. However, I consider that rather unlikely.
Please check your activity report on the LoTW web site: https://lotw.arrl.org/lotwuser/account? ... d=activity
What do you see?

If you are absolutely certain that the user name (callsign) and password are correct, I'm out of ideas.
When you use a file based logbook (not iCloud synced) you could send me the file for an investigation.

Do not interact with the displayed LoTW login page! This page is displayed just to see the error message.
In the RUMlog LoTW settings select explicit your callsign in the For Callsign field.

RL and LOTW time match are identical ( see photo)

NO! The incoming QSL shows 0744, your log shows 0745. This means your QSO was uploaded with 0744.

Please check your work flow. If the entry is made in red text, the status is not set to X. The upload might have occurred twice, from different programs?
Often, the LoTW QSO time does not exactly match the time in the logbook. However, this can only happen if RL was not used for the upload.

I've managed to screw something up somehow. There is an options in the Preferences to remove your own background. You can create/use your own background just using drag and drop. See here: https://dl2rum.de/rotor/docs/en/pages/AzimuthWin.html A good source for maps is here: https://ns6t.net ...

No.
Just go to the App Store and download a keyboard that fits your needs.

Works well here, more information would be useful.
Please note: Only TRX#1 works in the contest module.

From Club Log:

For QSOs on 2026-06-24 12:31...
RI0SP maps to MARITIME MOBILE
Not valid for DXCC on this date