Did you solve the mismatch by changing your qso start time in your log to be within 30 minutes of qso partner end time and resubmit to lotw? I too find msk qso's can take a VERY long time.

Thanks for this information. The QSO in question was 42 minutes from start to finish.

+ AA6YQ comments below + Please do the following: 1. on the Configuration window's General tab, check the "log debugging info" box 2. terminate DXKeeper 3. start DXKeeper 4. wait 1 minute 5. on the

No. I deleted the old and put the new one in place. C:\Program Files (x86)\DXKeeper\Databases\DefaultBands.txt This is in the txt file: 2190M, 0.1357,0.1378 630m, 0.472, 0.479 560M, 0.501, 0.504 160M,

+ AA6YQ comments below + LoTW allows for up to 30 minutes of difference between the "start time" you submit and the "start time" your QSO" partner submits; a ~20 minute discrepancy should not have

+ AA6YQ comments below + A mouse that does that is defective, and should be replaced. + Yours is the first request for this functionality in the ~20 years since Commander became publicly

Recently I worked a station on MSK144. The QSO took more than 20 minutes to complete. When I uploaded from DX Lab to LOTW the start time was the time used by LOTW. When I did not receive a

+ AA6YQ comments below+ My instructions were to download the file DefaultBands.txt, replacing the existing file in DXKeeper's Databases folder with that name. + If I correctly understand your report

Dave, Copied the DefaultBands from the web and pasted it into a new text file "DefaultBands.text" then placed that into the DXKeeper/Database - C:\Program Files (x86)\DXKeeper\Databases DxKeeper still

The logic has nothing to do with licensing rules. It comes about because the ten US call areas are used as geographic multipliers in their contests. If they did not have such a rule in effect, someone

Dave, My guess is that the sensitivity of some mouse scroll wheels is such that barely touching it causes the frequency to shift. I use the scroll feature constantly and have the mouse set so as not

BARTG sponsors contests in particular. Those Brits still think they have the right to override US rules. After almost 250 years they still have not learned! 73, ... Joe, W4TV

+ AA6YQ comments below Have used Commander over the years for three different Icom radios - R75, IC-7600, and now the R8600. Excellent software! Is there a way in Commander to lock the frequency?

Have used Commander over the years for three different Icom radios - R75, IC-7600, and now the R8600. Excellent software! Is there a way in Commander to lock the frequency? Often I find the tuned

+ AA6YQ comments below I recently uploaded my IOTA QSOs from DxKeeper to the IOTA website, that went fine and all QSOs were approved for credit. Today I downloaded the .csv file with the approved

+ AA6YQ comments below Additional info: where is the DXKeeper log page display configuration supposed to be saved? + You can configure DXKeeper to save it wherever you like. I think that the

Additional info: where is the DXKeeper log page display configuration supposed to be saved? I think that the location somehow became C:\Program Files (x86)\DXKeeper\Databases\DefaultBands.txt and

Which contests are these? If your address with the FCC is in Texas and you are operating from that QTH, the /5 is not required by FCC and not for major contests. Just curious. 73. Carl - WC4H

I'm seeing 1, 4, 118, 8 etc. Have I misconfigured?

I recently uploaded my IOTA QSOs from DxKeeper to the IOTA website, that went fine and all QSOs were approved for credit. Today I downloaded the .csv file with the approved QSOs from the