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
- DXLab
- Messages
Search
|
Re: "Inbound OQRS" greyed out
Getting there! Everything you mentioned worked well but I still don't have full understanding of how it handles a direct request. How does DX Keeper know whether the people requesting a card via OQRS have paid for a direct mail response or are just asking for a bureau card? Does DXK differentiate that when it downloads requests and imports that data?
And still one other very small problem. I have the "confirm multiple QSOs per QSL" set but there doesn't seem to be an override for different myQths. I made 3 QSOs with this test OQRS-request station, one from each of 3 different locations. Neither he nor I will really care where the Qs were made from, so long as they're from the same DXCC entity. They're even within the same circle for WAS eligibility. Is there any practical way around this or is it just easier to generate one label per QTH and stick 3 of them on the card instead of one multiple? |
|
Re: Background colors DXKeeper Log Page Display
-----Original Message-----AA6YQ comments below From: dxlab@... [mailto:dxlab@...] Sent: Tuesday, March 01, 2016 10:52 AM To: dxlab@... Subject: [dxlab] Re: Background colors DXKeeper Log Page Display Yes I have Spot Collector installed. Inside spot collector, all 4 are set to black, and they are well displayed in SC. But Inside DXkeeper..... if I change it, to the needed colors, DXK will not keep my setting after a restart and it will bring back the default colors. That's correct. If any background color specified by SpotCollector is "too dark", DXKeeper will employ the default background colors (white, yellow, cyan, and pink). 73,"Too dark" is defined as "one or more components of the color's RGB representation is 64 or less. Black is definitely "too dark". Dave, AA6YQ |
|
Re: A difficult request to clean up and old problem
---In dxlab@..., <aa6yq@...> wrote : >>>AA6YQ comments below >>>Try filtering the "Log Page Display" with the SQL expression (Comment like '18*') or (Comment like '35*')or (Comment like '70*') or (Comment like '71*') or (Comment like '101*') or (Comment like '14*') or (Comment like '21*') or (Comment like '24*') or (Comment like '28*') >>>Does the Log Page Display contain all of your split QSOs and only your split QSOs?Is it even worth considering? >>>I'll extend DXKeeper to look for a TX frequency in the first word of a Comment when importing QSOs with the "ADIF Style Options" panel set to DXBase or DXBase5, but that won't help anyone who has already imported their QSOs into DXKeeper.<snip> >>>That's why DXKeeper is so anal about identifying and reporting inconsistencies: it is far easier to correct them when they are first created than years later after you've forgotten the context. |
|
Re: New 6700- Win Warbler
-----Original Message-----AA6YQ comments below From: dxlab@... [mailto:dxlab@...] Sent: Tuesday, March 01, 2016 12:48 PM To: dxlab@... Subject: [dxlab] New 6700- Win Warbler Well--problem solved thanks to Dave on making Commander and the 6700 talk. My next task was to get CW Skimmer working--turned out I had to download another program SDR-Bridge to make that work. My last task and I need some help on is to get Win Warbler working with the 6700 so that I can do RTTY---PT31 and other digital modes. The 6700 has a TX stream that is used to send audio information to the 6700. It also has IQ streams----I enabled number 4---what I don't know is what settings or adjustments do I have to make on Win Warbler so that it hears and sees the digital signals. Any help is appreciated. I will also check the archives. <>You should review the Flex documentation so that you understand what DAX is, and how it's configured. Then take a look at 73, Dave, AA6YQ |
|
Re: A difficult request to clean up and old problem
-----Original Message-----AA6YQ comments below From: dxlab@... [mailto:dxlab@...] Sent: Tuesday, March 01, 2016 12:28 PM To: dxlab@... Subject: [dxlab] A difficult request to clean up and old problem There's one thing I'd love to do but honestly I don't know if it's possible or feasible. As you know, I converted my entire log from DX Base format three years ago, and that program has a bizarre way of recording split. Instead of logging RX and TX frequencies in their respective fields, as DXK does, it populates the TX Freq field with the RX freq and puts the TX Freq as the first string in the comments. So if I logged a station that was transmitting on 14.195 and I worked them by transmitting at 14.200, when that QSO was imported into DX Keeper, the entry's RX frequency field would be blank, the TX frequency would be converted to 14.195 and the comment field would begin with the characters 14200.00 (in kHz, not MHz). DX Base for whatever reason uses only the TX Frequency field to record the VFO-A frequency. This makes zero sense but it is what it is. Is it possible to bulk fix these? (Comment like '18*') or (Comment like '35*')or (Comment like '70*') or (Comment like '71*') or (Comment like '101*') or (Comment like '14*') or (Comment like '21*') or (Comment like '24*') or (Comment like '28*')Try filtering the "Log Page Display" with the SQL expression Does the Log Page Display contain all of your split QSOs and only your split QSOs? If so, you can use the "Modify QSOs" panel to copy each QSO's TX frequency to its RX frequency en masse. You could also use the "Modify QSOs" panel to increase the TX frequency by, say, 1 Khz to flag the QSO as "split", but there's no way (short of extending DXKeeper) to extract the actual TX frequency from Comment item. Is it even worth considering? I'll extend DXKeeper to look for a TX frequency in the first word of a Comment when importing QSOs with the "ADIF Style Options" panel set to DXBase or DXBase5, but that won't help anyone who has already imported their QSOs into DXKeeper. Below are just rambling, random comments, not requests/etc, that may be of interest to those who've imported their logs from other software into DX Keeper. Per my issue in the OQRS discussion thread, I spent about 4 hours this morning parsing my log for erroneous QSL sent settings. I set all the QSL_SENT requests that had been flagged "N" to nil (empty value), but the real fun one was about 500 QSOs from the spring of 2013 that had the sent flag set to S, but nothing in the sent-via field and no QSL sent or received date. The intention was to identify all of these and, like the first group, set their QSL Sent status to undefined. The filter I had to use for the latter took a while to build but it finally worked: (QSO_Begin between #2001-03-01# and #2013-05-21#) and (QSL_SENT_VIA not in ('E','B', 'D')) and (QSL_SENT in ('Y')) and (QSLSDATE = #4000-01-01#) and (QSLRDATE = #4000-01-01#). Then I bulk modified QSL_SENT to nil. I'm assuming that "no value" should be the default state of QSL_SENT and QSL_Rcvd unless deliberately acted upon (I've requested a QSL card or I've answered a QSL request). I also went through and set correct CONTEST_ID values for every contest Q dating back to the beginning, and everything's backed up to the cloud. I never realized how much erroneous info was in there over the years, and I'm sure there's so much more that remains hidden, awaiting some future attempt to do something. 73,That's why DXKeeper is so anal about identifying and reporting inconsistencies: it is far easier to correct them when they are first created than years later after you've forgotten the context. Dave, AA6YQ |
|
Re: "Inbound OQRS" greyed out
-----Original Message-----AA6YQ comments below From: dxlab@... [mailto:dxlab@...] Sent: Tuesday, March 01, 2016 12:14 PM To: dxlab@... Subject: [dxlab] Re: "Inbound OQRS" greyed out OK, done. I spent a couple of hours going through the log and getting rid of two classes of bad QSL entries; those with "N" that shouldn't have been and those with "Y" that were never, in fact, QSLd but marked that way for whatever reason. I take it there's no way to re-populate those Incoming OQRS requests at this point? It may be a long time before I ever get another OQRS request and I'd like to test it all out before I really need it. Speaking of OQRS, is there any way for DX Keeper to sort out Direct OQRS requests vs Buro OQRS requests and flag them separately? Direct to print right away, buro can print whenever?Of course there's a way to do that: click the date beneath the "Inbound OQRS" button, and in the OQRS window that appears, change the date to the day before those OQRS requests were created, and then click the OK button. 73,Yes. On the Main window's QSL tab, set the "QSL Via" selector to anything but eQSL.cc or LoTW, and then note the column of three checkboxes in the "Process QSLs and Addresses" panel. Dave, AA6YQ |
|
Re: DXKeeper pathing to network
-----Original Message-----AA6YQ comments below From: dxlab@... [mailto:dxlab@...] Sent: Tuesday, March 01, 2016 11:45 AM To: dxlab@... Subject: [dxlab] DXKeeper pathing to network Is it not possible to save downloaded eQSL images to another server or location on my network? I attempted to access the network using QSL config, then chose to browse to the network path I would like all eQSL's to be saved to but my network path will not open. How do I enable saving to another data storage center on the network? 73,If you want to save eQSL card images to a folder on another computer, first save them to a local folder, and then move them across your network using Windows Explorer. Dave, AA6YQ |
|
Re: Reload DXLab after IS Reinstall
-----Original Message-----AA6YQ comments below From: dxlab@... [mailto:dxlab@...] Sent: Tuesday, March 01, 2016 11:35 AM To: Alan Swinger; dxlab@... Subject: RE: [dxlab] Reload DXLab after IS Reinstall Dave - I spoke too soon. Download from LoTW is not working. When I click on Sync LoTW QSOs and Sync LoTW QSLs, I get this Message: "Unable to Download from LoTW: Download failure". <>See the "Download Failure" section of Also when I click on Add Requested, I get 5 Log entries that have been previously Uploaded, so system says they are dupes and will not Upload. Tried to add a new QSO and Add requested, and got the same results. 73,Why does TQSL think the QSOs in question have already been uploaded? Dave, AA6YQ |
|
New 6700- Win Warbler
Well--problem solved thanks to Dave on making Commander and the 6700 talk. ?My next task was to get CW Skimmer working--turned out I had to download another program SDR-Bridge to make that work. ?My last task and I need some help on is to get Win Warbler working with the 6700 so that I can do RTTY---PT31 and other digital modes. ?The 6700 has a TX stream that is used to send audio information to the 6700. ?It also has IQ streams----I enabled number 4---what I don't know is what settings or adjustments do I have to make on Win Warbler so that it hears and sees the digital signals. ?Any help is appreciated. I will also check the archives. Thanks, Mark WC3W |
|
A difficult request to clean up and old problem
There's one thing I'd love to do but honestly I don't know if it's
possible or feasible. As you know, I converted my entire log from DX Base format three years ago, and that program has a bizarre way of recording split.
Instead of logging RX and TX frequencies in their respective fields, as
DXK does, it populates the TX Freq field with the RX freq and puts the
TX Freq as the first string in the comments. So if I logged a station that was transmitting on 14.195 and I worked them by transmitting at 14.200,
when that QSO was imported into DX Keeper, the entry's RX frequency
field would be blank, the TX frequency would be converted to 14.195 and
the comment field would begin with the characters 14200.00 (in kHz, not
MHz). DX Base for whatever reason uses only the TX Frequency field to record the VFO-A frequency. This makes zero sense but it is what it is.
Below are just rambling, random comments, not requests/etc, that may be of interest to those who've imported their logs from other software into DX Keeper. Per my issue in the OQRS discussion thread, I spent about 4 hours this morning parsing my log for erroneous QSL sent settings. I set all the QSL_SENT requests that had been flagged "N" to nil (empty value), but the real fun one was about 500 QSOs from the spring of 2013 that had the sent flag set to S, but nothing in the sent-via field and no QSL sent or received date. The intention was to identify all of these and, like the first group, set their QSL Sent status to undefined. The filter I had to use for the latter took a while to build but it finally worked: (QSO_Begin between #2001-03-01# and #2013-05-21#) and (QSL_SENT_VIA not in ('E','B', 'D')) and (QSL_SENT in ('Y')) and (QSLSDATE = #4000-01-01#) and (QSLRDATE = #4000-01-01#). Then I bulk modified QSL_SENT to nil. I'm assuming that "no value" should be the default state of QSL_SENT and QSL_Rcvd unless deliberately acted upon (I've requested a QSL card or I've answered a QSL request). I also went through and set correct CONTEST_ID values for every contest Q dating back to the beginning, and everything's backed up to the cloud. I never realized how much erroneous info was in there over the years, and I'm sure there's so much more that remains hidden, awaiting some future attempt to do something. |
|
Re: "Inbound OQRS" greyed out
OK, done. I spent a couple of hours going through the log and getting rid of two classes of bad QSL entries; those with "N" that shouldn't have been and those with "Y" that were never, in fact, QSLd but marked that way for whatever reason.
I take it there's no way to re-populate those Incoming OQRS requests at this point? It may be a long time before I ever get another OQRS request and I'd like to test it all out before I really need it. Speaking of OQRS, is there any way for DX Keeper to sort out Direct OQRS requests vs Buro OQRS requests and flag them separately? Direct to print right away, buro can print whenever? |
|
Re: Commander Bandspread "tolerance"
¿ªÔÆÌåÓýPlease forgive fat fingers that was supposed to say 18.068126 :-(73, Rich - W3ZJ On 3/1/2016 11:54 AM, Rich - W3ZJ
rich@... [dxlab] wrote:
Just worked him 17M at 10.068126 (126 Hz inside the band) all the spots I see for him in 12M show he is on or slightly above the band edge. 3 of the 12M spots were from reverse beacon stations that show him at 24.891. He is working close to the band edges and guess he could have slipped a bit at one point but I would be pretty careful that close to the edge. |
|
Re: Commander Bandspread "tolerance"
¿ªÔÆÌåÓýJust worked him 17M at 10.068126 (126 Hz inside the band) all the spots I see for him in 12M show he is on or slightly above the band edge. 3 of the 12M spots were from reverse beacon stations that show him at 24.891. He is working close to the band edges and guess he could have slipped a bit at one point but I would be pretty careful that close to the edge.73, Rich - W3ZJ On 3/1/2016 10:51 AM, 'Joe Subich,
W4TV' lists@... [dxlab] wrote:
|
|
DXKeeper pathing to network
Is it not possible to save downloaded eQSL images to another server or location on my network?
I attempted to access the network using QSL config, then chose to browse to the network path I would like all eQSL¡¯s to be saved to but my network path will not open. How do I enable saving to another data storage center on the network? ¡ I¡¯m just sayin¡¯ 73 de K3JAE John Etling <mailto:k3jae@...> k3jae@... From: Alan Swinger awswinger@... [dxlab] [mailto:dxlab@...] Sent: Tuesday, March 01, 2016 10:35 To: Alan Swinger <awswinger@...>; dxlab@... Subject: RE: [dxlab] Reload DXLab after IS Reinstall Dave - I spoke too soon. Download from LoTW is not working. When I click on Sync LoTW QSOs and Sync LoTW QSLs, I get this Message: "Unable to Download from LoTW: Download failure". Also when I click on Add Requested, I get 5 Log entries that have been previously Uploaded, so system says they are dupes and will not Upload. Tried to add a new QSO and Add requested, and got the same results. Checked my network with my other Laptop that has DXLab and Keeper and Sync functions worked properly, and when I clicked Add Requested, the previously uploaded Qs did not show up. Suggestions? Thanks - Alan K9MBQ -----Original Message----- From: Alan Swinger Sent: Feb 29, 2016 5:18 PM To: dxlab@... Subject: RE: [dxlab] Reload DXLab after IS Reinstall Dave - Took your first recommendation - Uninstalled DXLab apps tks to the Dell Techs who used Revo Reg Cleaner Pro They cleaned it all out, and then I did a New Download from the DXLab web site. Installed Launcher and used it to install all Apps. Uploaded my DXKeeper Log file and updated all other missing data (I must not have done the Workspace saving correctly since had to re enter most data). Keeper Uploads to LoTW, and other apps seem to work all OK. So, my DX Lab Suite on the problem computer appears to be back up to full operations. . . . and the world is now safe!! Thanks for your continuing assistance. Best regards, Alan K9MBQ -----Original Message----- From: "' Dave AA6YQ' aa6yq@... [dxlab]" Sent: Feb 29, 2016 3:50 PM To: dxlab@... Subject: RE: [dxlab] Reload DXLab after IS Reinstall -----Original Message-----AA6YQ comments below From: dxlab@... [mailto:dxlab@...] Sent: Monday, February 29, 2016 1:16 PM To: DXLab Group Subject: RE: [dxlab] Reload DXLab after IS Reinstall OK, Dave. Will uninstall and do a new install. Any suggestions re a Windows Registry Cleaner? Also, I can open Commander and DXKeeper and use all OK, incl uploading recent QSOs to LoTW. However, once I open WW, it will not shut down.I have no experience with Registry Cleaners. A Registry Cleaner - I forget which one - was at one time recommended in "Getting Started with DXLab", but a user reported that it caused damage, so I removed the recommendation. 73,You could try leaving Commander and DXKeeper installed, an only uninstall/clean/re-install the applications that aren't working correctly. However, there is always the possibility of hidden damage. Dave, AA6YQ [Non-text portions of this message have been removed] |
|
Re: Reload DXLab after IS Reinstall
Dave - I spoke too soon. Download from LoTW is not working. When I click on Sync LoTW QSOs and Sync LoTW QSLs, I get this Message: "Unable to Download from LoTW: Download failure". Also when I click on Add Requested, I get 5 Log entries that have been previously Uploaded, so system says they are dupes and will not Upload. Tried to add a new QSO and Add requested, and got the same results. ? Checked my network with my other Laptop?that has?DXLab and Keeper ?and Sync functions worked properly, and when I clicked Add Requested, the previously uploaded Qs did not show up. ? Suggestions? ? Thanks - Alan K9MBQ -----Original Message----- |
|
Re: Commander Bandspread "tolerance"
I would guess that, technically, if the other fellow is out of band, then it's not a valid contact for DXCC.? I have run into that with a DX station recently, when I zero-beat him I concluded he was 30 Hz low.? Now, my rig might not be exactly on frequency... my justification for counting the QSO was that at least PART of his signal was within the band. Laugh if you will... 73 de Chuck, WS1L On Tue, Mar 1, 2016 at 9:51 AM, 'Joe Subich, W4TV' lists@... [dxlab] <dxlab@...> wrote:
--
|
|
Re: Background colors DXKeeper Log Page Display
Yes I have Spot Collector installed. Inside spot collector, all 4 are set to black, and they are well displayed in SC. But Inside DXkeeper..... if I change it, to the needed colors, DXK will not keep my setting after a restart and it will bring back the default colorsr. SC still OK at all time. Jeff VA2SS |
|
Commander Bandspread "tolerance"
This morning 3XY1T was calling CQ (split) just a hundred (if that) Hz
or so below 24,890 for a while. Tuning to him - even when split with the TX VFO in the band - caused Commander to blank the bandspread and switch to the "out of band" color. Short of editing the Sub-Band definition files to "extend" each band by 1 KHz, is there a way to: (1) provide some tolerance on the band edges or (2) trigger the blanking/out of band action based on the transmit frequency? If not, could there be? 73, ... Joe, W4TV |
wc3w
Chuck, WS1L
to navigate to use esc to dismiss