Date   

Re: DXKeeper, I do have a question

Dave AA6YQ
 

+ AA6YQ comments below

Yesterday I was trying DXaview as you have suggested. But I don't think I set it up properly or even understand the program.

I was looking on YouTube and hope to find some "DXView how to" but came up empty.

+ Start here:

<https://www.dxlabsuite.com/dxlabwiki/GettingStarted>


For example. I made a QSO with xx1xx in Japan. I see a blue dot showing up in Japan. All good. Then next QSO I made was with yy1yy in England. I see the blue dot moved from Japan to England.

Basically no matter how many QSO I made and logged in DXKEEPER I will be only me (black dot) and one blue dot.

+ That's correct. There are explicit steps one must take identify a set of QSO partners whose locations you want plotted on a world map. For example,

<https://www.dxlabsuite.com/dxlabwiki/QSOPlotting>


+ I suggest that you follow the "Getting Started with DXLab" article's recommendations for how to familiarize yourself with a DXLab application like DXView. If you have questions as you review this material, don't hesitate to post them here.

73,


Dave, AA6YQ


Re: N1MM-DXKeeper Gateway version 1.1.6

Dave AA6YQ
 

+ AA6YQ comments below

Subject: Re: [DXLab] N1MM-DXKeeper Gateway version 1.1.6

I had the same problem, Focus Stealing... which rendered the N1MM-DXK-GW unusable.
I hope this fix works.

+ The three ops to whom I have sent version 1.1.6 of the Gateway report that the focus stealing has been eliminated with one exception: Pathfinder steals focus on the first lookup, but not on subsequent lookups. I am investigating.

to get around this for this weekend's CQWW I had to revert to v1.1.4 which did NOT steal focus. Of course, one can just export/import post contest i guess.

however, i still had the "</contactinfo>: Foreign application won't perform DDE method or operation" fault/error message which results in the QSO NOT getting logged in DXK four times over the contest period.

+ As I pointed out to you in my response to your report of this behavior in November 2019, the above error message means that the Gateway directed Windows to convey message containing a QSO to DXKeeper, but Windows could not do so. I also pointed out that Windows has a long track record for failing to deliver such messages when it's "in trouble" -- e.g. does not have sufficient memory available.

https://groups.io/g/DXLab/message/189172

+ If you've done nothing to correct the conditions responsible for this message (insufficient resources), then it would be surprising if it stopped happening.


I thought v1.1.6 would fix it, but apparently not.

+ Are you reporting that you experienced the above error message while running version 1.1.6 of the Gateway?


maybe get rid of the entire DDE mechanism and use a diff IPC mechanism like TCP/IP instead??

+ As I posted here last week, version 1.1.6 of the N1MM-DXKeeper Gateway uses TCP (instead of DDE) to convey QSOs to DXKeeper.

<https://groups.io/g/DXLab/message/196903>



73,

Dave, AA6YQ


Apparent Bug in Commander?

Jon Gefaell
 
Edited

When typing into the 'Memory notes' fields, characters that match modes (F == FM, A == AM, etc) will change the mode on the radio. 

I have replicated this on purpose, and otherwise repeatedly. 

To reproduce (100%):

Be tuned in to a frequency and in SSB mode. Select "Memory Banks" and then the "Memory Notes" screen. Click on an empty field and observe field is selected and cursor is evident in field. Type 'F' and radio changes to FM. The "F" character appears in the "Memory Notes" section. Type "A", radio switches to AM. Characters "FA" appear in "Memory Notes". Repeat with R (RTTY), C (CW) and P (PSK). Characters "FARCP" appear in "Memory Notes" section.


AZ for SC spots

Joe K2UF
 

My DXLAB PC hard drive failed. Re-installed on new PC. Everything seems to
be working except I am not getting AZ data for spots. I get a few but not
as many as on the old pc. I can not find what I am doing wrong on SC help.

Please, any help.

Thanks

Joe K2UF


--
This email has been checked for viruses by AVG.
https://www.avg.com


Re: jtdxt not populating dxkeeper filter

 
Edited

Works now.  Did system shutdown, restarted all.  
Thanks for help
--
Norm WA4ZXV EM73vw


Re: New question: QRZ Logging

KD2HCE@...
 

I've been using the latter method Jim states above. DXKeeper is main log, it sends out to LoTW and eQSL, takes info FROM them and updates itself, of course after a 15 minute wait on LoTW. Then as QRZ is FREE to DOWNLOAD from LoTW (QRZ only costs you to UPload to LoTW,) even still the XML subscription is worth the non-worry of too many lookups per day, you just do a download FROM LotW every 15 minutes as QRZ now has a timer installed. I think that would be an issue for DXKeeper to instantly update QRZ, it would have to sniff out that remaining time to query LoTW again.
Also: The best ~$13 (10Euro) ever spent, was on LogPublisher by DL9HO, the PITA factor went to zero if you use HRDLog. Automates everything. EVEN SENDS QSOs instantly TO QRZ, but I've found the download from LoTW is much more accurate, and negates any dupes when you do download from LoTW for confirmations. The method Jim uses seems to be the best overall for now. I've been doing it this way for over a year now.
Hope this helps,
73,
Chris - KD2HCE


Re: jtdxt not populating dxkeeper filter

Mike, ND4V
 

Look at spot collector.  Is the right hand connection light green?
If not go into config and look at spot sources.  Is the box checked to enable the connection to jt ?

MW


On Oct 26, 2020, at 10:51, Norm <norman@...> wrote:

was working.  Now not.

--
Norm WA4ZXV EM73vw


jtdxt not populating dxkeeper filter

 

was working.  Now not.

--
Norm WA4ZXV EM73vw


Eqsl and Lotw

 

When you download eqsl and lotw it states how many were confirmed of course. But I dont see a report that tells u which ones were confired only the error report.
73
--
 Dave NU4N


Re: DXKeeper, I do have a question

Komkit Listisard
 

Dave,

Yesterday I was trying DXaview as you have suggested. But I don't think I set it up properly or even understand the program.

I was looking on YouTube and hope to find some "DXView how to" but came up empty.

For example. I made a QSO with xx1xx in Japan. I see a blue dot showing up in Japan. All good.  Then next QSO I made was with yy1yy in England. I see the blue dot moved from Japan to England.

Basically no matter how many QSO I made and logged in DXKEEPER I will be only me (black dot) and one blue dot.

I think I have no idea what I am doing with DXView


Re: N1MM-DXKeeper Gateway version 1.1.6

bob-w9zv
 

I had the same problem, Focus Stealing... which rendered the N1MM-DXK-GW unusable.
I hope this fix works.

to get around this for this weekend's CQWW I had to revert to v1.1.4 which did NOT steal focus.    Of course, one can just export/import post contest i guess.

however, i still had the  "</contactinfo>: Foreign application won't perform DDE method or operation"  fault/error message which results in the QSO NOT getting logged in DXK  four times over the contest period.   I thought v1.1.6 would fix it, but apparently not. 

maybe get rid of the entire DDE mechanism and use a diff IPC mechanism like TCP/IP instead??   


Re: DXKeeper Changing Windows focus

Dave AA6YQ
 

+ AA6YQ comments below

I am not sure if this is a Windows or DXLabs 'feature'.

If I have a callsign or part of entered into DXKeeper Capture window and press Ctrl-W to clear the window (which normally takes a second or so to complete) but I immediately change the windows focus to some other app (before DXKeeper has finished what it does, which includes refreshing the list of recent QSO's often at least twice) and start to type something into the other app the Windows focus changes back to DXKeeper and part of what I was trying to type into the other app ends up in the DXKeeper Call box causing me to have to clear the entry and try doing what I really wanted again (but having to wait for DXKeeper to catch-up first).

Similarly if I have typed a call in and press TAB key and then try to change to another app the focus gets changed back to the DXKeeper Capture RST field.

+ Has this been the case since you first began using DXKeeper, or did this behavior begin more recently? If the latter, when did it start, and what changes did you make to your hardware or software around that time?

+ Two possibilities come to mind:

1. you have a "keyboard helper" application installed on your system that intercepts "CTRL-W" and responds by inviking some procedure you've specified

2. interference from an anti-malware application

+ To check for the second possibility, reboot Windows into "safe mode with networking", and start DXKeeper. Enter a callsign into the Capture window, strike the Tab key, and then strike CTRL-W. Any difference in speed or behavior?

73,

Dave, AA6YQ


Re: RTTY Practice

ND9G Mike
 

You may also want to join the RTTY reflector.


73,
Mike ND9G


On Sun, Oct 25, 2020 at 10:04 AM <WALTDEWS@...> wrote:
Thanks for your responses.  Will keep chipping away at it.


Re: RTTY Practice

WALTDEWS@...
 

Thanks for your responses.  Will keep chipping away at it.


DXKeeper Changing Windows focus

Stewart Wilkinson
 

I am not sure if this is a Windows or DXLabs 'feature'.

If I have a callsign or part of entered into DXKeeper Capture window and press Ctrl-W to clear the window (which normally takes a second or so to complete) but I immediately change the windows focus to some other app (before DXKeeper has finished what it does, which includes refreshing the list of recent QSO's often at least twice) and start to type something into the other app the Windows focus changes back to DXKeeper and part of what I was trying to type into the other app ends up in the DXKeeper Call box causing me to have to clear the entry and try doing what I really wanted again (but having to wait for DXKeeper to catch-up first).

Similarly if I have typed a call in and press TAB key and then try to change to another app the focus gets changed back to the DXKeeper Capture RST field.

--
Stewart G0LGS


Re: Kids, help on submission

Dave AA6YQ
 

+ AA6YQ comments below

Yes I do. But a number of entries have been entered before I realized I had an issue

+ Since you don't know what damage was done to your current log, I suggest that you

1. manually review and correct the QSOs in your current log made after the date of your last backup

2. export an ADIF file containing the corrected QSOs in your current log made after the date of your last backup

3. terminate DXKeeper

4. rename your current log file by appending _DAMAGED to its filename, e.g. VA3BXG_DAMAGED.mdb

5. make a copy of your last backup file, and name the copy VA3BXG.mdb

6. start DXKeeper

7. direct DXKeeper to open VA3BXG

8. direct DXKeeper to import the ADIF file you created in step 3 above

73,

Dave, AA6YQ


Re: Kids, help on submission

Robert galambos
 

Yes I do. But a number of entries have been entered before I realized I had an issue

:-(


Re: DXKeeper, I do have a question

Dave AA6YQ
 

+ AA6YQ comments below

On the main log QSOs. I have question on 2 of the fields. One labeled RX Freq in the QSO block and the other labeled ADDR in the QSL block.

Where did the DXKeeper get the information from and how?

+ Since you were logging QSOs from JT-Alert, the information in both items came from JT-Alert.


I am asking because this morning I downloaded GridTracker and instructed GT to send the logging from JTDX to DXKeeper via GT. Everything seem to be okay except those two fields did not get fill properly (blank). For RX freq I will have to manually type it in and for ADDR, I will just hit EDIT and hit the CBA and save.

Prior I was using JTALERT sending logging information to DXKeeper, everything got filled properly.

With GT, those two were blank. I am wondering what did I miss. I setup the look up in GT so that was not it, I am thinking GT did not send those that were missing to DXKeeper. That is why I am curious on how / where DXKeeper got those information from.

+ I'm not aware of any interoperation between GridTracker and DXLab.

+ Note that DXLab can plot logged QSOs on DXView's native world map, Google Earth, and the DX Atlas world map; worked and confirmed grid squares can be plotted on the DX Atlas world map.

73,

Dave, AA6YQ


DXKeeper, I do have a question

Komkit Listisard
 

On the main log QSOs.  I have question on 2 of the fields.  One labeled RX Freq in the QSO block and the other labeled ADDR in the QSL block.

Where did the DXKeeper get the information from and how?

I am asking because this morning I downloaded GridTracker and instructed GT to send the logging from JTDX to DXKeeper via GT.  Everything seem to be okay except those two fields did not get fill properly (blank).  For RX freq I will have to manually type it in and for ADDR, I will just hit EDIT and hit the CBA and save.

Prior I was using JTALERT sending logging information to DXKeeper, everything got filled properly.

With GT, those two were blank.  I am wondering what did I miss.  I setup the look up in GT so that was not it, I am thinking GT did not send those that were missing to DXKeeper.  That is why I am curious on how / where DXKeeper got those information from.

Thank you kindly,


Re: N1MM-DXKeeper Gateway version 1.1.6

Dave AA6YQ
 

+ AA6YQ comments below

I have the same problem as Kent, if you use the space to change fields, the same thing happens, works fine (in my case Pathfinder to perform "lookup" operations) but you lose the focus.

+ I've sent Kent N6WT and Phil WR7T a new version of the Gateway that should prevent "focus theft". I just sent the new version to you as well; please let me know how it goes.

73,

Dave, AA6YQ

3041 - 3060 of 200001