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
|
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 |
|
Re: Grey line not showing on DXView World Map 4.1.8
If there's an errorlog.txt file in your DXView folder, please attach that to an email message, and send it to me via
toggle quoted message
Show quoted text
aa6yq (at) ambersoft.com If that's not the case, please reboot Windows just to make sure we're not chasing a transient Windows problem. If the behavior persists, then 1. on the Configuration window's General tab, check the "log debugging info" box 2. terminate DXView 3. start DXView 4. make sure the World Map window is visible 5. on the Configuration window's General tab, uncheck the "log debugging info" box 6. attach the errorlog.txt file from your DXView folder to an email message, and send it to me via aa6yq (at) ambersoft.com 73, Dave, AA6YQ -----Original Message-----
From: dxlab@... [mailto:dxlab@...] Sent: Tuesday, March 01, 2016 10:38 AM To: dxlab@... Subject: RE: [dxlab] Grey line not showing on DXView World Map 4.1.8 This is a new computer with a fresh load of DXlabs. I really don't remember if it happened when it was first loaded or not. Should I just CTL-LD DXView and start it fresh? Or would you prefer I turn on debugging? thanks jim ab3cv |
|
Re: ClubLog Inbound OQRS and QSL_Rcvd
-----Original Message-----AA6YQ comments below From: dxlab@... [mailto:dxlab@...] Sent: Tuesday, March 01, 2016 10:34 AM To: dxlab@... Subject: [dxlab] ClubLog Inbound OQRS and QSL_Rcvd I set up the Inbound OQRS according to the instructions and it works great. Thanks for the feature Dave. My question is about what gets printed in the 'QSL?' field on the labels. The QSL requests from ClubLog have QSL_Sent set to R and QSL_Rcvd empty. When I print labels I get 'pse!' in the 'QSL?' field. I would expect this field to be blank if QSL_Rcvd is empty. I have been filtering for QSL_Sent=R and then setting QSL_Rcvd=I before printing OQRS labels. I would like to eliminate this step. Is there a setting somewhere that would remove the return QSL request? 73,In the Options panel at the top of the "QSL Configuration" window's General tab, uncheck the "Outgoing QSLs request confirmation unless already confirmed" box Dave, AA6YQ |
|
ClubLog Inbound OQRS and QSL_Rcvd
I set up the Inbound OQRS according to the instructions and it works great. Thanks for the feature Dave.
My question is about what gets printed in the 'QSL?' field on the labels. The QSL requests from ClubLog have QSL_Sent set to R and QSL_Rcvd empty. When I print labels I get 'pse!' in the 'QSL?' field. I would expect this field to be blank if QSL_Rcvd is empty. I have been filtering for QSL_Sent=R and then setting QSL_Rcvd=I before printing OQRS labels. I would like to eliminate this step. Is there a setting somewhere that would remove the return QSL request? 73, Pat K?PC |
|
Re: Grey line not showing on DXView World Map 4.1.8
-----Original Message-----AA6YQ comments below From: dxlab@... [mailto:dxlab@...] Sent: Tuesday, March 01, 2016 10:19 AM To: dxlab@... Subject: [dxlab] Grey line not showing on DXView World Map 4.1.8 For some reason the greyline and sun position are not showing on my World Map. I can't find any option to enable or disable it. The map otherwise looks fine in size, resolution and plotting of paths to DX. Auroral zones also show properly when enabled. Win10, latest production lease. What am I missing? 73,Has this always been the case, Jim, or is this new behavior? If the latter, when did it start? What hardware or software changes did you make around the time it started? Dave, AA6YQ |
|
Re: "Inbound OQRS" greyed out
*** more AA6YQ comments below
toggle quoted message
Show quoted text
-----Original Message-----
From: dxlab@... [mailto:dxlab@...] Sent: Tuesday, March 01, 2016 2:02 AM To: dxlab@... Subject: [dxlab] Re: "Inbound OQRS" greyed out ---In dxlab@..., <aa6yq@...> wrote : >>>If a QSO's "QSL Sent" is set to 'N' - meaning "no card should be set" - any incoming OQRS request will be ignored. >>>Why was "QSL Sent" set to 'N' ? +++ I don't know why. Most of my old pre-DX-Keeper QSOs that I imported were set to QSL sent = N and were never changed. In my old DX Base log, from the very first QSO until about the time I converted to DX Lab, if I didn't sent for a card then the QSL-Sent field appears to be marked as N by default. I know I switched over from DX Base in the spring of 2013. From what looks like late February 2013, most QSOs had the QSL Sent set to Y, which lasted until late May 2013--even though I know I didn't QSL a great many of them. After that date the QSL Sent field was generally left blank or set to Y when a card was either sent as a direct request or a bureau reply. So what do you recommend I do? Is there any reason to leave those set to N? Should I just find all Qs with that QSL sent status and remove the flag altogether? I can't see any reason why I wouldn't want to confirm an old contact if I were to ever get a QSL request. I'm thinking I should filter the log from the beginning until May 21st (when the Y flags started to disappear on all QSOs and long after the N flags were gone), then find all records where Sent Via is blank and QSL Received is also blank, then bulk remove whatever value is in QSL-S. Does that sound right? August 2001 to May 2013, anything marked Y or N where QSL-R is blank and sent via is also blank, then mark sent as blank? *** Since QSL_RCVD = 'N' means "don't QSL" and since that's not your intention, then I suggest that you 1. backup your log (Configuration window, Log tab, Backup button) 2. filter the Log Page Display with QSL_RCVD = 'N' 3. In the "Modify QSOs" panel on the "Advanced Sorts, Filters, and Modifiers" window, 3a. set the "Item name" selector to QSL_Rcvd 3b. leave the "Item new value" selector empty 3c. click the Mod button 73, Dave, AA6YQ |
|
Grey line not showing on DXView World Map 4.1.8
Jim Miller
For some reason the greyline and sun position are not showing on my World Map. I can't find any option to enable or disable it. The map otherwise looks fine in size, resolution and plotting of paths to DX. Auroral zones also show properly when enabled. Win10, latest production lease. What am I missing? Thanks jim ab3cv |
Chuck, WS1L
to navigate to use esc to dismiss