Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
Search
Progress window
|
Dave,
When I click on a callsign in DXKeeper, obviously I have worked the guy, but the progress window does not always indicate any contact with his country. Also, I have worked 3G0Y 8 times on 80,30,20,10 meter CW, and 10, 15 meter SSB. The progress window shows only an F in CW and 40 meters. DXView shows that the prefix is CE0E. So I entered that in the filter window and clicked DXCC it came up with another station on Easter Island that I had worked on 40 CW but nothing for 3G0Y. I did a recompile in the progress window but nothing changed. Also, when I do a DXCC Summary, it shows 97 countries worked and 96 confirmed. Logger, which has a duplicate of the same log shows 252 countries worked and 52 confirmed which is correct. There are just short of 5000 entries in my log dating back to November 1999. Most of the entries in DXKeeper were imported from Logger. ----- 73, Rich - W3ZJ www.w3zj.com |
|
Dave Bernstein
Without seeing your log, I can't know for sure, but my suspicion is
toggle quoted message
Show quoted text
that many of your DXKeeper log entries are missing DXCC country codess -- likely because DXView was not running when these entries were created or imported. At the moment, DXKeeper relies on DXView to determine the DXCC entity associated with a callsign. I'll be adding this capability to DXKeeper before releasing it to beta test. If my diagnosis is correct, you can update your log entries by starting DXView and then recomputing progress. Let me know how it goes... 73, Dave --- In dxlab@y..., "Richard B Drake" <rich@w...> wrote:
Dave, |
|
I'm not sure if DXView was open when I did the import. However, it
toggle quoted message
Show quoted text
was open when I did the recompute. I just did that again to make sure, it didn't help. However, I just noticed something else. When I click on 3G0Y in DXKeeper, the correct prefix, CE0Y shows up in DXView but the QSO window in DXKeepr shows CE which isn't right. When I do a lookup in the new capture window it correctly shows CE0Y. Does that tell you anything? Ah!!! That gave me a clue. What if Logger exported the wrong prefix. I just checked that and that's what happened. So, what that says is that recompute looks first in the log to see if there is a prefix present and only checks DXView if there is not one there. Is that the way you want it to work? If so, I can probably fix it by removing all the prefixes from the import ADIF file, removing the current DXKeeper log and doing the import again. That should force everything to be looked up in DXView - Right? ------- 73, Rich - W3ZJ -----Original Message----- |
|
Dave Bernstein
Yes, if there's a country code present in the imported QSO, DXKeeper
toggle quoted message
Show quoted text
respects it. The procedure you suggest will result in each imported callsign being checked by DXView to determine a country code. Does this explain the large variance in confirmed countries you mentioned earlier? 73, Dave, AA6YQ --- In dxlab@y..., "Richard B Drake" <rich@w...> wrote:
I'm not sure if DXView was open when I did the import. However, it |
I don't know, but I am having a great deal of difficulty with the import. I took out all the DXCC entries in the ADIF file to force a lookup in DXView. It starts off going OK, pretty slow but I can live with that. Then it suddenly seems to lose communication with DXView and starts flying along without putting in a DXCC prefix. The first time I tried it, it only put in about 10 prefixes before that happened. I tried again and this time it got to about 400 before it lost the connection. In any case it will not handle my 5000 entry log in one go. It gets up to QSO# 3762 and dies. I can handle that by doing it in two pieces but I don't know what to do about the loss of communication with DXView. ---- 73, Rich - W3ZJ |
|
Dave, AA6YQ
Sounds like there's a latent defect in the DDE connection between DXKeeper
toggle quoted message
Show quoted text
and DXLab. I suggest you hold off until I release a version of of DXKeeper that performs the country code lookup without consulting DXView. Shouldn't take too long... 73, Dave, AA6YQ -----Original Message-----
From: Richard B Drake [mailto:rich@...] Sent: Wednesday, March 21, 2001 17:50 PM To: dxlab@... Subject: RE: [dxlab] Re: Progress window > > Does this explain the large variance in confirmed countries you > mentioned earlier? > I don't know, but I am having a great deal of difficulty with the import. I took out all the DXCC entries in the ADIF file to force a lookup in DXView. It starts off going OK, pretty slow but I can live with that. Then it suddenly seems to lose communication with DXView and starts flying along without putting in a DXCC prefix. The first time I tried it, it only put in about 10 prefixes before that happened. I tried again and this time it got to about 400 before it lost the connection. In any case it will not handle my 5000 entry log in one go. It gets up to QSO# 3762 and dies. I can handle that by doing it in two pieces but I don't know what to do about the loss of communication with DXView. ---- 73, Rich - W3ZJ Yahoo! Groups Sponsor iWin.com - The Place to Win Stuff! To unsubscribe from this group, send an email to: dxlab-unsubscribe@... Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service. |
|
Ron Eberson
I import more than 1000 qso's from logger with out problems
-----Oorspronkelijk bericht----- Van: Richard B Drake [mailto:rich@...] Verzonden: woensdag 21 maart 2001 23:50 Aan: dxlab@... Onderwerp: RE: [dxlab] Re: Progress window I don't know, but I am having a great deal of difficulty with the import. I took out all the DXCC entries in the ADIF file to force a lookup in DXView. It starts off going OK, pretty slow but I can live with that. Then it suddenly seems to lose communication with DXView and starts flying along without putting in a DXCC prefix. The first time I tried it, it only put in about 10 prefixes before that happened. I tried again and this time it got to about 400 before it lost the connection. In any case it will not handle my 5000 entry log in one go. It gets up to QSO# 3762 and dies. I can handle that by doing it in two pieces but I don't know what to do about the loss of communication with DXView. ---- 73, Rich - W3ZJ To unsubscribe from this group, send an email to: dxlab-unsubscribe@... Your use of Yahoo! Groups is subject to |
|
Dave Bernstein
To ensure its ability to perform callsign lookups, DXKeeper will from
now on include a copy of the DXCC database previously only packaged with DXView. During startup, DXKeeper will determine whether DXView is installed. If so, it will reference DXView's copy of this database, ignoring its own copy -- this permits a single point of database maintenance, e.g. when adding a new DXCC entity. If DXView is not installed, then DXView will refer to its own copy of the database. Callsign lookups during import operations will directly reference a DXCC database, either DXView's (if installed) or DXKeeper's. DXView itself will not participate in import operations, which should speed things up quite a bit. For callsign lookups during interactive operations (such as logging a QSO), DXKeeper will attempt the callsign lookup via DXView if its running; in performing this lookup, DXView updates its information display. If DXView is not running, then DXKeeper will perform the lookup using its copy of the database. So import operations run fast and don't depend on (or overload) DXView, interactive operations use DXView if its running, but in no case will DXKeeper create a QSO that's missing DXCC prefix or country code information. There's more complexity here than I'd like, but most of it is hidden from the user. If you've installed DXView, then you can use it to maintain your DXCC database and DXKeeper will automatically be consistent. If you aren't using DXView, then DXKeeper has its own DXCC database (though you lack a tool to update it, and thus have to download updates from DXKeeper web site). Comments? The above approach is implemented (in DXView 1.1.5) and appears to work, but I'd like to test a few more cases before posting it. 73, Dave, AA6YQ --- In dxlab@y..., "Dave, AA6YQ" <dhb@m...> wrote: Sounds like there's a latent defect in the DDE connection betweenDXKeeper and DXLab. I suggest you hold off until I release a version of ofDXKeeper that performs the country code lookup without consulting DXView.Shouldn't take too long...Service. |
|
Wow, that is a bit complex but it sounds like you have a good
toggle quoted message
Show quoted text
handle on it. The problem of keeping two copies of a database in sync without requiring data to be entered in two places is always a bit tricky. I take it from this that when DXView is installed it is the master, DXKeeper is the slave and one should never directly update DXkeeper (assuming that there will eventually be a tool to do it). You sure are fast at this stuff!! ---- 73, Rich - W3ZJ -----Original Message----- |
|
OK, a bunch of stuff here.
First I have succeeded in getting the import to work with DXView. Here is what I did: 1) Closed all applications and closed my dial up connection. 2) Disabled Norton Antivirus autoprotect, disabled task scheduler. I'm not sure this was necessary but my object was to eliminate any possible interference from external software interrupts. 3) Opened DXView, Opened DXKeeper. 4) Started the Import. It proceeded to import and fill in the prefix info for the first 3762 QSO's, then halted as before. 5) Created another ADIF file containing only the remaining 1238 QSO's and started again. It completed normally. Its interesting that after staring the import, the DXKeeper window is on top and has the focus. Clicking on the DXView window so that it becomes the top window with the focus speeds up the import by a ratio of at least ten times, maybe more. This did not fix the summary discrepancy of countries worked. It also did not fix the 3G0Y problem, though he now shows with the proper CE0Y prefix, my contacts with him still do not show in the progress window. What it looks like is that it just stops recording info in the progress window at some point. For example, if I search for the ZS prefix using filter DXCC it shows I have worked a bunch of them, yet no contacts with ZS show up in the progress window. I'm not sure how to find exactly where it stops counting. The summary shows 96 countries (mixed band/mode), there are actually 252. ------ 73, Rich - W3ZJ |
|
Dave Bernstein
Yes, multiple databases are to be avoided. I started with the notion
toggle quoted message
Show quoted text
of one DXCC database managed by DXView, with other applications invoking DXView for callsign lookups, etc. But its unacceptable for DXKeeper to record QSOs without DXCC prefixes and country codes just because DXView is either not installed, or installed but not running. And we see that relying on DXView for batch operations like "import" significantly reduces performance. Its no problem to have DXKeeper directly access DXView's database (rather than send a message to DXView to perform that access on its behalf) -- that eliminates the performance problem, and the requirement that DXView be running. But it does require DXView to be installed, which may not be the case. So providing a duplicate copy of the database with DXKeeper, and arranging for DXKeeper to automatically use it if DXView isn't installed solves the problem in a manner that's completely transparent to the user. I could make DXKeeper delete its DXCC database if it finds that DXView is installed; this eliminates any user confusion as to which database to update (e.g. adding a new DXCC entity) and saves the disk space. Its only a problem if the user subsequently uninstalls DXView, but this could be corrected by downloading a DXCC database from the DXKeeper web site. --- In dxlab@y..., "Richard B Drake" <rich@w...> wrote:
Wow, that is a bit complex but it sounds like you have a good |
|
Dave Bernstein
I should have a new version of DXKeeper ready tonite -- it doesn't
toggle quoted message
Show quoted text
use DXView during imports, and thus should eliminate the performance problem. Then we can determine whether there is an additional progress tracking problem, or whether that was a side effect of the DXView lookup problem. Loss of the DDE link between DXKeeper and DXView may be nothing more than a timeout -- I left this at the 5 second default, and have not yet added autorecovery code to re-establish the link should it break. Do check for the presence of error logs in your DXView and DXKeeper folders. 73, Dave, AA6YQ --- In dxlab@y..., "Richard B Drake" <rich@w...> wrote:
OK, a bunch of stuff here. |
to navigate to use esc to dismiss