Manual logging
Richard P
I’ve studied them manual, but no joy. This is what Dave would want, so I’m unhappy with myself. Problem: I entered a SSB QSO. It appears on the QSO logging window “spreadsheet” exactly as I entered it. Good. But 1) When I go to the QSL window and click “Add Requested,” nothing happens. And 2) When I go back to the QSO window and try clicking on the arrow next to the call sign I just entered, so I can tell it to upload to LoTW, I get the pop-up window that says “QSO was not uploaded to LoTW because its station callsign item is empty.” Clearly this confuses me, cuz I can see the callsign that I entered. It’s there. (I have been using DXKeeper successfully for uploading FT8 contacts to LoTW. This is my first effort to do so manually.)
|
|
W9MR Mike
Open the Auxiliary panel by clicking the checkbox to display that section. This will display that section. With the QSO selected in the log window ("spreadsheet") you'll see the station call, op call, and owner call. it is entirely likely that these would all be your call, but there may be some variations depending on your operating situation. If they should all be your call because you were the op at your own station, go ahead and make sure your call is in all three fields. In the Online QSL section, which may not be displayed due to the checkboxes for displaying that panel, similar to the auxiliary panel. Look for the Sent field in the LoTW section of this panel. If it is set to "R" you don't need to do anything, fixing the previous portion will allow it to be uploading using the Add Requested option. 73, Mike W9MR
|
|
Dave AA6YQ
+ AA6YQ comments below
+ Is the QSO's "LoTW Sent" item set to 'R' ?
+ I don't understand what "When I go back to the QSO window and try clicking on the arrow next to the call sign I just entered". Are you referring to the QSO panel at the top of the Main window's "Log QSOs" tab? If so, to what does the "arrow next to the callsign I just entered" refer? + Is the Defaults tab of DXKeeper's Configuration window configured to specify a "Station Callsign" that will be recorded with each QSO? + "Station Callsign" refers to the callsign that you used over the air during the QSO, not the callsign of the station you worked.
+ DXKeeper can submit QSOs to LoTW automatically, but let's hold off on that until we resolve the issues reported above> 73, |
|
Richard P
Gents, Many issues here I do not understand. But let me start with this: In the “Log QSOs” window, under “Auxiliary,” the field “station call” is empty, and the text is flashing blue. Same goes for the “QSO” window, where “my QTH” is flashing blue and the field is empty. |
|
Dave AA6YQ
+ AA6YQ comments below
many issues here I do not understand. But let me start with this: In the “Log QSOs” window, under “Auxiliary,” the field “station call” is empty, and the text is flashing blue. Same goes for the “QSO” window, where “my QTH” is flashing blue and the field is empty. + Every logged QSO must specify your "Station Callsign" - the callsign you used over-the-air when making the QSO. If you specify a default "Station Callsign" on the Configuration window's Defaults tab, then DXKeeper will automatically use it to specify the "Station Callsign" of each new QSO you create. + If you have specified one or more myQTHs on the Main window's "my QTHs" tab, then each logged QSO should specify the "myQTH ID" of the myQTH from which you made the QSO. You can specify a "Default myQTH ID" in the "Log Settings" panel on the Configuration window's Log tab. + Rather than continue to bump into sharp objects, I suggest that you remove your blindfold by scanning the reference documentation in https://www.dxlabsuite.com/dxkeeper/Help/index.htm + so that you'll understand the capabilities available to you - like the Capture window, which is optimized for logging new QSOs in real time. + Step-by-step instructions for frequent logging scenarios are provided here: https://www.dxlabsuite.com/dxlabwiki/Logging + I don't mean for you to stop asking questions here; you are welcome to do so. But you'll find it less frustrating to establish a mental model for how DXKeeper works, and why. 73,
|
|