Date   

Re: Logging for multiple contests on same date?`

Carl - WC4H
 

Hi Steve.

Contests aren't really designed so that you operate two at a time.  Having said that, you can try running an instances of N1MM++ for one and DXKeeper for the other.

Just don't interface them to talk to each other so that you don't have a mess with the QSOs.

Another alternative, if possible, is to use two computers, one fore each contest.

I suspect that either it could be confusing.

73.
Carl - WC4H


Re: Spotcollector Message

Rien Aarden
 

Hello Dave, 

And other DXLabusers and SpotSpy  I have sent Volker 2 weeks ago a mail with this Error but no response on the mail.

So Have anyone contact with Volker??


Hope to hear soon from someone!
73 Rien, PA7RA 


Re: Logging for multiple contests on same date?`

Dave AA6YQ
 

+ AA6YQ comments below

In some cases multiple state QSO parties are scheduled for the same date and time. For example, the Louisiana and Mississippi QSO Parties run concurrently this weekend, and the Nebraska, New Mexico, Georgia, and North Dakota QSO Parties all overlap at least part of the time the following weekend.

If you want to participate in all of these QSO parties and your next QSO could be with a station from any one of them, what is the best way to handle logging in DXKeeper so that your QSO rate is not slowed down while insuring that each QSO is assigned the correct CONTEST_ID?

+ If you're concerned about "rate", you should be logging with a specialized contesting application like N1MM and then importing your QSOs into DXKeeper at the end of the contest(s).

73,

Dave, AA6YQ


Logging for multiple contests on same date?`

Steve, N5EP
 

In some cases multiple state QSO parties are scheduled for the same date and time.  For example, the Louisiana and Mississippi QSO Parties run concurrently this weekend, and the Nebraska, New Mexico, Georgia, and North Dakota QSO Parties all overlap at least part of the time the following weekend.

If you want to participate in all of these QSO parties and your next QSO could be with a station from any one of them, what is the best way to handle logging in DXKeeper so that your QSO rate is not slowed down while insuring that each QSO is assigned the correct CONTEST_ID? 

Steve, N5EP


Re: Telepathic Receiver

Dave AA6YQ
 

+ AA6YQ comments below.
I like that idea but, when you get version 1.0 done, could you include a function to tell me where I left whatever I went after that I no longer have when I get to where I thought I needed it ? Telling me what I had and why I thought I needed it would be nice too

+ Of course. You should also be able go back in time to get the other stuff that you didn't realize you would need.

        73,

              Dave, AA6YQ

 


Re: Call Override list for DxView?

Jesper Wolf Jespersen
 

Hello Dave.

Thank you for the polite reminder, I had plain forgotten that you allready implemented this and I have clearly used it before since both sources had a date in ocktober 20.

Nice that you can remind me.

Nice work, an answer within 30 minutes I wonder how many commercial software houses can match that.

Outstanding service.

Happy Greetings from Denmark
Jesper Wolf Jespersen.

PS. i like the idea of a telepathic interface :-D

On 02-04-2021 00:26, Dave AA6YQ wrote:
+ AA6YQ comments below

I have been annoyed a few times this spring with calls that did not resolve in a DXCC being automatically chosen, this has typically hapened when logging from JtDx where I notice the logging to fail but cant do anything about it at once.

I typically have to create an entity override in DxView and the log all the JtDx information by hand.

I would like to avoid this manual maintenance of the override list and
am wondering why that list is not distributed or at least avaiable for
download somewhere ?

I can see that there are quite a number of overrides in my list
allready, and I havent entered thousands in there, so they must come
from somewhere.

+ As described in its reference documentation, DXView enables you to populate its Override list from Club Log, BigCTY, or by inserting entries manually:

https://www.dxlabsuite.com/dxview/Help/Configuration.htm#Entity%20Overides

Does a list exist that I can download?

+ There are two sources of information, and you evidently downloaded information from at least one of them.

Last call to bother me was TO1K that had to point to Saint Marten before could log it.

I have DxKeeper look stuff up on QRZ via XML, but still it seems this list needs to be updated, wonder why?

+ The Override list needs to be updated because its contents change.

+ Some ops prefer to populate their override list from ClubLog exclusively. Some ops prefer to use BigCTY exclusively. Some ops first populate their Override List with information from Club Log, and then populate their list with information from BigCTY -- so that conflicts are resolved in favor of BigCTY; some ops populate their Override list in the reverse order.

+ Whichever source you prefer, visit the Overrides tab of DXView's Configuration window each week to update your overrides, and minimize the agonizing frustration caused by ambiguous callsigns.

+ The next version of DXView will include a telepathic receiver that automatically discerns which source of information your prefer, eliminating the need for you to think about which button to click.

73,

Dave, AA6YQ





Telepathic Receiver

Mike Rhodes / W8DN
 

Dave,
  I like that idea but, when you get version 1.0 done, could you include a function to tell me where I left whatever I went after that I no longer have when I get to where I thought I needed it ? Telling me what I had and why I thought I needed it would be nice too.
😉😁😂

Mike / W8DN


Re: Call Override list for DxView?

Dave AA6YQ
 

+ AA6YQ comments below

I have been annoyed a few times this spring with calls that did not resolve in a DXCC being automatically chosen, this has typically hapened when logging from JtDx where I notice the logging to fail but cant do anything about it at once.

I typically have to create an entity override in DxView and the log all the JtDx information by hand.

I would like to avoid this manual maintenance of the override list and
am wondering why that list is not distributed or at least avaiable for
download somewhere ?

I can see that there are quite a number of overrides in my list
allready, and I havent entered thousands in there, so they must come
from somewhere.

+ As described in its reference documentation, DXView enables you to populate its Override list from Club Log, BigCTY, or by inserting entries manually:

https://www.dxlabsuite.com/dxview/Help/Configuration.htm#Entity%20Overides

Does a list exist that I can download?

+ There are two sources of information, and you evidently downloaded information from at least one of them.

Last call to bother me was TO1K that had to point to Saint Marten before could log it.

I have DxKeeper look stuff up on QRZ via XML, but still it seems this list needs to be updated, wonder why?

+ The Override list needs to be updated because its contents change.

+ Some ops prefer to populate their override list from ClubLog exclusively. Some ops prefer to use BigCTY exclusively. Some ops first populate their Override List with information from Club Log, and then populate their list with information from BigCTY -- so that conflicts are resolved in favor of BigCTY; some ops populate their Override list in the reverse order.

+ Whichever source you prefer, visit the Overrides tab of DXView's Configuration window each week to update your overrides, and minimize the agonizing frustration caused by ambiguous callsigns.

+ The next version of DXView will include a telepathic receiver that automatically discerns which source of information your prefer, eliminating the need for you to think about which button to click.

73,

Dave, AA6YQ


Call Override list for DxView?

Jesper Wolf Jespersen
 

Hello to all of you.

I have been annoyed a few times this spring with calls that did not resolve in a DXCC being automatically chosen, this has typically hapened when logging from JtDx where I notice the logging to fail but cant do anything about it at once.

I typically have to create an entity override in DxView and the log all the JtDx information by hand.


I would like to avoid this manual maintenance of the override list and am wondering why that list is not distributed or at least avaiable for download somewhere ?

I can see that there are quite a number of overrides in my list allready, and I havent entered thousands in there, so they must come from somewhere.

Does a list exist that I can download?

Last call to bother me was TO1K that had to point to Saint Marten before i could log it.

I have DxKeeper look stuff up on QRZ via XML, but still it seems this list needs to be updated, wonder why?


Greetings from Denmark

Jesper Wolf Jespersen

OZ8ACE


PS. Thanks to Dave for a fantastic set of applications :-)


Re: Spotcollector Message

Dave AA6YQ
 

@ more AA6YQ comments below
I think I found it
I have installed SpotSpy and if I don't run it, it isn't
At least I tested this this afternoon and without Spotspy I don't get the message.
But I do hope there is a solution for it

@ I suggest that you report this behavior to the developer of SpotSpy, Volker DL9HO.

      73,

            Dave, AA6YQ

 


Re: Spotcollector Message

Rien Aarden
 

On Thu, Apr 1, 2021 at 12:26 AM, Dave AA6YQ wrote:
@ When did this behavior first appear? What changes do your hardware or software did you make around that ime?
Hi Dave,
I think I found it
I have installed SpotSpy and if I don't run it, it isn't
At least I tested this this afternoon and without Spotspy I don't get the message.
But I do hope there is a solution for it.
thanks Greetings Rien, PA7RA


Re: ADIF import from N1MM+

Andy - K0AF
 

Thank you to Rich, Joe, and Dave!

Joe, I see you posted on the N1MM+ group to inform them of the error of their ways. Thanks! And Dave, thanks for pointer on using <compute> to fix the PFX entries. Just one more feature I was not aware of. Now if you could enhance <compute> to fix busted callsigns, that would be great. Maybe after you finish your sunspot app?

The DXLab suite is amazing and so is the support.

73 & thanks!
Andy - K0AF


Re: Spotcollector Message

Dave AA6YQ
 

@ more AA6YQ comments

 

On Sat, Mar 13, 2021 at 11:39 AM, Dave AA6YQ wrote:
Windows is preventing SpotCollector from compacting the Spot Database, probably because Windows erroneously considers one of the files involved to be still "in use". As a first step, try rebooting Windows.
Good morning Dave,

Unfortunately I keep getting this message back (The Spot Datase cannot be accessed for compactions: permissoin denied)
What is very annoying what else can I do?
@ When did this behavior first appear? What changes do your hardware or software did you make around that ime?

        73,

                Dave, AA6YQ


Re: Spotcollector Message

Rien Aarden
 

On Sat, Mar 13, 2021 at 11:39 AM, Dave AA6YQ wrote:
Windows is preventing SpotCollector from compacting the Spot Database, probably because Windows erroneously considers one of the files involved to be still "in use". As a first step, try rebooting Windows.
Good morning Dave,

Unfortunately I keep getting this message back (The Spot Datase cannot be accessed for compactions: permissoin denied)
What is very annoying what else can I do?
Thanks and a Happy Easter to you and your family.

73, Rien, PA7RA


Re: ADIF import from N1MM+

Dave AA6YQ
 

+ AA6YQ comments below

I don't see an obvious way to deal with this from within DXKeeper

+ The "Modify QSOs" panel can be used to recompute the WPX prefix for each QSO in the Log Page Display. See

https://www.dxlabsuite.com/dxkeeper/Help/ModifyLog.htm

73,

Dave, AA6YQ


Re: ADIF import from N1MM+

Dave AA6YQ
 

+ AA6YQ comments below

This morning I imported an ADIF from N1MM+ into DXKeeper. In DXKeeper the prefix (PFX) entry for all imported US stations is "K" rather than the station's actual prefix. The N1MM+ ADIF includes a PFX field and the value is "K" for all US stations.

I've imported ADIF from N1MM+ several times in the past and the PFX entry in DXKeeper was always correct. I looked at ADIF files exported from N1MM+ previously and they do not have a PFX field. Evidently this is a recent addition. Is there a way to have DXKeeper overwrite the imported PFX with the correct prefix?

+ No, DXKeeper always respects contents of each imported ADIF field. To correct your WPX items after importing,

1. backup your log (Configuration window, Log tab, Backup button)

2. filter the Log Page Display to contain the QSOs you just imported (easier if before importing, you invoke the "Clear Select" function and check the "Set Select in imported QSOs to Y" box on the Main window's "Import QSOs" tab; then you can filter the Log Page Display to contain the QSOs you just imported by clicking the Sel button in the Filter panel at the bottom of the Main window's "Log QSOs" tab)

3. In the "Modify QSOs" panel on the "Advanced Sorts, Filters, and Modifiers" window,

3a. set the "Item name" selector to PFX

3b. type

<compute>

in the "Item new value" box

3c. click the Mod button

73,

Dave, AA6YQ


Re: ADIF import from N1MM+

Joe Subich, W4TV
 

The ADIF fields are clearly defined in the current specification:
<http://adif.org/311/ADIF_311.htm>

PFX: <http://adif.org/311/ADIF_311.htm#QSO_Field_PFX>
DXCC: <http://adif.org/311/ADIF_311.htm#QSO_Field_DXCC>

Misuse of any field has the potential of breaking interchange - as
in this case!

73,

... Joe, W4TV

On 2021-03-31 2:22 PM, Joe Subich, W4TV wrote:

I just checked the N1MM+ update history for the latest version
(1.0.90xx). One of the changes was:

/ADIF Export: Added PFX tag (Coded by AB2ZY)/
Argh! Can't N1MM developers read the ADIF specs?  PFX is WPX Prefix
not DXCC Prefix.  If one is going to code "DXCC prefix" it should be
the country code (*ADIF NUMBER*) not an arbitrary prefix that changes
depending on the application/sponsor.
73,
  ... Joe, W4TV
On 2021-03-31 1:57 PM, Andy - K0AF wrote:
Thanks Rich! Editing the ADIF and renaming <PFX: to to an unrecognized field is an easy remedy.
I just checked the N1MM+ update history for the latest version (1.0.90xx). One of the changes was:

/ADIF Export: Added PFX tag (Coded by AB2ZY)/
I'm pretty new to N1MM+ and just learning how to use it. N1MM+ appears to get updated frequently and I'm sure I'm not the only one who ran in to this so I'll wait and see if it gets fixed. I hesitate to join the N1MM+ group and make suggestions to the experts on how to change their program.

Thanks Rich!


Re: ADIF import from N1MM+

Joe Subich, W4TV
 

I just checked the N1MM+ update history for the latest version
(1.0.90xx). One of the changes was:

/ADIF Export: Added PFX tag (Coded by AB2ZY)/
Argh! Can't N1MM developers read the ADIF specs? PFX is WPX Prefix
not DXCC Prefix. If one is going to code "DXCC prefix" it should be
the country code (*ADIF NUMBER*) not an arbitrary prefix that changes
depending on the application/sponsor.

73,

... Joe, W4TV


On 2021-03-31 1:57 PM, Andy - K0AF wrote:
Thanks Rich! Editing the ADIF and renaming <PFX: to to an unrecognized field is an easy remedy.
I just checked the N1MM+ update history for the latest version (1.0.90xx). One of the changes was:
/ADIF Export: Added PFX tag (Coded by AB2ZY)/
I'm pretty new to N1MM+ and just learning how to use it. N1MM+ appears to get updated frequently and I'm sure I'm not the only one who ran in to this so I'll wait and see if it gets fixed. I hesitate to join the N1MM+ group and make suggestions to the experts on how to change their program.
Thanks Rich!


Re: ADIF import from N1MM+

Andy - K0AF
 

Thanks Rich! Editing the ADIF and renaming <PFX: to to an unrecognized field is an easy remedy.
 
I just checked the N1MM+ update history for the latest version (1.0.90xx). One of the changes was:

   ADIF Export: Added PFX tag (Coded by AB2ZY)
 
I'm pretty new to N1MM+ and just learning how to use it. N1MM+ appears to get updated frequently and I'm sure I'm not the only one who ran in to this so I'll wait and see if it gets fixed. I hesitate to join the N1MM+ group and make suggestions to the experts on how to change their program.

Thanks Rich!


Re: ADIF import from N1MM+

ve3ki
 

It looks as if the programmer may have interpreted the PFX field as if it meant the standard prefix for the DXCC entity instead of the WPX prefix of the call sign. The ADIF specification clearly says WPX prefix, but maybe that was missed.

In fact, the field might have been added to the export in response to requests from users who wanted the DXCC prefix made available, not from users who wanted to see the WPX prefix. After all, deducing the WPX prefix form the call sign is trivial in most cases, whereas the DXCC prefix requires more calculation and is something users who don't have all the international prefix allocations memorized might appreciate more.

Anyway, you should raise this on the N1MMLoggerPlus group, which all of the programmers monitor (they do not all monitor this group). If what people want is the DXCC prefix, a different tag (such as APP_N1MM_DXCC_Prefix) should be used.

I don't see an obvious way to deal with this from within DXKeeper, but there is an easy way to fix it in the ADIF file before importing it: Open the ADIF file with Notepad and do a global replace to change all occurrences of <PFX: to <JUNK: (or any other name you care to call it, as long as you don't use the name of a field that is in the ADIF specification), save the corrected file and import it into DXKeeper. DXKeeper will ignore the changed field name and will calculate the correct WPX prefix automatically during the import.

73,
Rich VE3KI


On Wed, Mar 31, 2021 at 12:12 PM, Andy - K0AF wrote:
This morning I imported an ADIF from N1MM+ into DXKeeper. In DXKeeper the prefix (PFX) entry for all imported US stations is "K" rather than the station's actual prefix. The N1MM+ ADIF includes a PFX field and the value is "K" for all US stations.

I've imported ADIF from N1MM+ several times in the past and the PFX entry in DXKeeper was always correct. I looked at ADIF files exported from N1MM+ previously and they do not have a PFX field. Evidently this is a recent addition. Is there a way to have DXKeeper overwrite the imported PFX with the correct prefix?

Thanks!
Andy - K0AF

3281 - 3300 of 203962