- DXLab
- Topics
Search
Callsign in DXKeeper - Problem
Fred - NA2U #178740 Log is PJ2/NA2U. Logged Qs the other day with no problem. Today when I log both Station Call and Owner Call are logging as NA2U and, of course, will not upload to LOTW. I have changed NOTHING in the configuration screens to cause this behavior. I modified each of the Qs and uploaded manually. How to fix, please? 73 and thanks from the desert, Fred/NA2U |
Dave w6de
#178743 What does "Will not upload to LotW mean." Please describe the what you do, Dave, w6de toggle quoted messageShow quoted text -----Original Message----- Log is PJ2/NA2U. Logged Qs the other day with no problem. Today when I log both Station Call and Owner Call are logging as NA2U and, How to fix, please? 73 and thanks from the desert, Fred/NA2U |
Dave w6de
#178744 In the DXLab wiki: Dave, w6de toggle quoted messageShow quoted text -----Original Message----- Log is PJ2/NA2U. Logged Qs the other day with no problem. Today when I log both Station Call and Owner Call are logging as NA2U and, How to fix, please? 73 and thanks from the desert, Fred/NA2U |
Fred - NA2U #178745 Thanks, Dave. I’ll take another look when I return home. I’ve had my multiple calls, including PJ2/NA2U, set up and working properly for almost fours years without incident. I changed nothing. Program behavior changed. Therefor the puzzlement. 73 from the desert, Fred/NA2U toggle quoted messageShow quoted text On Jul 8, 2018, at 12:01 PM, w6de <w6de@...> wrote: |
ve3ki
#178746 You mentioned that the QSOs with the problem were in FT8 and that CW worked properly. The FT8 protocol and the programs that implement it handle compound call signs differently, and somewhat awkwardly, as compared with unmodified call signs. That might have had something to do with the problem, e.g. perhaps the FT8 program didn't forward compound call signs properly to DXKeeper. If that is the case, you can probably correct the problem after the fact with the help of the Advanced Filters, Sorts and Modifiers window in DXKeeper. 73, toggle quoted messageShow quoted text On Sun, Jul 8, 2018 at 01:15 pm, Fred - NA2U wrote: Thanks, Dave. I’ll take another look when I return home. |
Dave AA6YQ
#178754 + AA6YQ comments below I've had my multiple calls, including PJ2/NA2U, set up and working properly for almost fours years without incident. I changed nothing. Program behavior changed. Therefor the puzzlement. + FT8 was first introduced a year ago. What's likely changed is that you're using a new application to log FT8 QSOs -- one that you have not correctly configured to log QSOs made as PJ2/NA2U. 73, Dave, AA6YQ |
Previous TopicNext Topic
