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: Filter Spots by Propagation?
Band filter and set the appropriate start/end UTC times.
toggle quoted message
Show quoted text
I typically use something like SS-90 for start and SR+90 for end (on 40/30) but you can adjust that for your QTH. 73, ... Joe, W4TV On 2025-02-01 1:33 PM, Jim Miller - AB3CV via groups.io wrote:
Since beginning to chase WAZ I get a lot of spots on 40m for R0*** (typ. zone 18) during the time of day when propagation (Min Useable Freq) makes that a non starter. Is there a way to filter these out so I don't get alerts on them? |
||||||||||||||||||||||||||||||||||||||||
|
Re: Filter Spots by Propagation?
toggle quoted message
Show quoted text
On Feb 1, 2025, at 12:33 PM, Jim Miller - AB3CV via <jtmiller47@...> wrote: Since beginning to chase WAZ I get a lot of spots on 40m for R0*** (typ. zone 18) during the time of day when propagation (Min Useable Freq) makes that a non starter. Is there a way to filter these out so I don't get alerts on them?
?
Thanks
?
Jim ab3cv
|
||||||||||||||||||||||||||||||||||||||||
|
Updated DARC DOK award list
Carlo IK2RPE has updated the award list that DXKeeper uses to populate its DOK award selectors - if you have the "DARC DOK region selection" box checked in the "Other Awards" panel on the Awards tab of DXKeeper's Configuration window. For immediate access to this updated list, 1. terminate DXKeeper 2. download the file from into DXKeeper's Databases folder, replacing the existing file with the same name 3. start DXKeeper This updated award list will be included with the next public version of DXKeeper. Thanks, Carlo! ? ? ? ? ?73, ? ? ? ? ? ? ? ? Dave, AA6YQ |
||||||||||||||||||||||||||||||||||||||||
|
Re: Recompute results-73 QSOs with "Broken ARRL Section"
+ AA6YQ comments below
That¡¯s pretty interesting. So the Alt/Recompute button must correlate with the LOTW data to show the correct ARRL section? + No, LoTW doesn't report ARRL sections. For the Continental US, Alaska, and Hawaii, DXKeeper's Secondary Subdivision Database contains all Counties. For Counties in States with multiple ARRL section, each County specifies its ARRL section. If so, that¡¯s another pretty deep little facet to this already comprehensive program. Does anyone have a dog-eared copy of the ¡°DXLab for Dummies¡± book? I need to borrow it¡ + My advice is contained in the opening section of + One-at-a-time, scan the Reference Documentation for each DXLab application your using, in whatever order you wish. Ignore details during this scan, but keep a list of functionality you'd like to explore later. When you're done scanning, prioritize the items on your "functionality to explore" list, and explorer them one at a time be returning to the Reference documentation and by searching the index to "Getting Started with DXLab" for step-by-step instructions: + This approach prevents burnout from attempting to grok it all in one fell swoop, and minimizes posts of the form "I wish I knew that functionality was available 3 years ago!" 73, Dave, AA6YQ |
||||||||||||||||||||||||||||||||||||||||
|
Re: Recompute results-73 QSOs with "Broken ARRL Section"
¿ªÔÆÌåÓýThat¡¯s pretty interesting. ?So the Alt/Recompute button must correlate with the LOTW data to show the correct ARRL section? ?If so, that¡¯s another pretty deep little facet to this already comprehensive program. ?Does anyone have a dog-eared copy of the ¡°DXLab for Dummies¡± book? ?I need to borrow it¡ Steve ?K4WA On Jan 31, 2025, at 6:07?PM, Jim McPhee via groups.io <jmcphee@...> wrote:
|
||||||||||||||||||||||||||||||||||||||||
|
Re: Recompute results-73 QSOs with "Broken ARRL Section"
Dave,,
?
Thanks for your response. I did just click the Recompute button with the Alt key depressed, and the inconsistencies were changed/corrected to the one that the "ARRL Section is inconsistent with". In trying to understand where the "correct ARRL Section" was coming from, I found that most, if not all, of these QSOs were with NPOTA/POTA stations. It would appear that the "correct ARRL Section" was being derived from the park ID, or somewhere else in the QSO details? And in the dozen or so that I checked the corrections did agree with the location of the parks.
?
Thanks for sharing with me how to make those corrections, even though they may not really matter as far as awards go.
--
Jim McPhee Placitas, NM W5ABA |
||||||||||||||||||||||||||||||||||||||||
|
Re: spotcollector fields?
toggle quoted message
Show quoted text
On Jan 31, 2025, at 1:14 PM, Jamie WW3S via <ww3s@...> wrote: Can I delete, add and/or rearrange columns in Spotcollector?? |
||||||||||||||||||||||||||||||||||||||||
|
Re: Recompute results-73 QSOs with "Broken ARRL Section"
+ AA6YQ comments below
+ In a QSO with a station in the US, Alaska, or Hawaii,? a broken ARRL Section is one that is inconsistent with its QSO's State and County. + In a QSO with a station in Canada, a broken ARRL Section is one that is inconsistent with its Province. + As stated in "If the Alt key is depressed when the Recompute button is clicked, correctable errors in primary and secondary administrative subdivisions and in ARRL sections will be corrected and the corrections reported as Actions; for example, each inconsistent ARRL section item will be replaced with a value deduced from its QSO's DXCC entity, State, and County items." ? ? ? ? ? ? ? ?Dave, AA6YQ |
||||||||||||||||||||||||||||||||||||||||
|
Recompute results-73 QSOs with "Broken ARRL Section"
After seeing Dave recommend another user invoke the "Recompute" function, I decided to do it as well. Result was 73 QSOs, 60 of them from 2016, flagged as ?"Broken ARRL Section". Interestingly, there are a few cases where multiple contacts with the same station resulted in different inconsistencies being reported. According to QRZ right now, N0UR is located in Steele County, MN. I do have the "Automatically recompute realtime award tracking" enabled. Should I be concerned by this, and if so, what actions should I take to remediate it?
?
?
--
Jim McPhee Placitas, NM W5ABA |
||||||||||||||||||||||||||||||||||||||||
|
Re: DXKeeper Online QSL Synchronization
+ AA6YQ comments below
+ So that I can see what's going on, please do the following: ?
1. on DXKeeper's Configuration window's General tab, check the "Log debugging info" box
2. terminate DXKeeper 3. start DXKeeper 4. on the Main window's QSL tab 4a. set the "QSL via" panel to QRZ 4b. click the "Sync QRZ QSLs" button, and wait for the operation to complete 5. on DXKeeper's Configuration window's General tab, uncheck the "Log debugging info" box 6. attach the errorlog.txt file from your DXKeeper folder to an email message, and sent that message to me via aa6yq (at) ambersoft.com ? ? ?73, ? ? ? ? ? Dave, AA6YQ |
||||||||||||||||||||||||||||||||||||||||
|
DXKeeper Online QSL Synchronization
Good evening -
?
I'm getting the following message when I do a Sync All -
?
updating 37541 logged QSOs with QRZ confirmations.? ?It only happens with QRZ.
?
it shows up every time I do a Sync All. ?The number remains the same. As you can imagine it takes a while for it to complete usually on the order of 15 to 30 minutes. ?The progress indicator speeds up noticeably once it reaches about 75% done.
?
The SyncAll.Txt shows the following:
eQSL.cc Sync QSLs: 1 QSL processed for N5RN, 0 log entries updated, 0 errors
eQSL.cc Sync QSLs: no new confirmations of previously unconfirmed entities, entity-bands, or entity-modes
LotW Sync QSOs: 1 QSO reported accepted
LotW Sync QSLs: 2 QSLs processed, 2 log entries updated, 0 errors
LotW Sync QSLs: no new confirmations of anything Needed And previously Unconfirmed
Club Log upload: 6 QSOs uploaded
QRZ upload: QRZ upload: 1 QSOs uploaded, 1 QSOs replaced, 0 QSOs rejected,
Club Log Sync QSLs: 15 QSLs processed, 15 log entries updated, 0 errors
Club Log Sync QSLs: no new confirmations of anything needed and previously unconfirmed
QRZ Sync QSLs: QSO reported as confirmed is not present in log (LogID = 1209158417)
QRZ Sync QSLs: QSO reported as confirmed is not present in log (LogID = 1211464199) QRZ Sync QSLs: 20533 QSLs processed, 472 log entries updated, 2 errors
?
I need some advice on what to do to speed this process up.
?
tia - glenn, n5rn
?
|
||||||||||||||||||||||||||||||||||||||||
|
Re: DXView Progress panel
¿ªÔÆÌåÓýDang it! ?That worked. ?I¡¯m going to have to try much harder. ?? Sorry for taking so long to figure this incredibly deep program suite out¡ Steve On Jan 30, 2025, at 5:27?PM, Dave AA6YQ <aa6yq@...> wrote:
|
||||||||||||||||||||||||||||||||||||||||
|
Re: DXView Progress panel
+ AA6YQ comments b
Eureka! Once again, I have been successful in my ongoing efforts to create a small glitch in the program by doing something stupid. Don¡¯t thank me, it was just apparent that someone had to explore all the nuances of errant entry in order to help the esteemed Chief Programmer determine how low to set the bar.+ Click the Recompute button along the bottom of the Main window's "Check Progress" tab. ? ? ?73, ? ? ? ? ? Dave, AA6YQ |
||||||||||||||||||||||||||||||||||||||||
|
DXView Progress panel
Eureka! Once again, I have been successful in my ongoing efforts to create a small glitch in the program by doing something stupid. Don¡¯t thank me, it was just apparent that someone had to explore all the nuances of errant entry in order to help the esteemed Chief Programmer determine how low to set the bar.
Here¡¯s how I did it: After seeing a spot on my iPad that JD1-m was on 10m, I rushed to my radio room, turned on the amp and radio, tuned to the appropriate split and worked him. Opened the capture window (DXKeeper, SpotCollector and DXView were already on) and filled in the data¡wait, I didn¡¯t turn on Commander. Did that, finished filling in the log data, clicked the Log button and¡oops, the frequency looks right, but it shows SSB as the mode and I worked him on CW. No problem, I just go to edit and change the mode to CW. Success! Wait, that¡¯s funny, DXView Progress panel shows I¡¯ve worked JD1-m on 10m CW AND SSB. Pretty sure I¡¯ve never worked it on phone¡click on the ¡°W¡± in the 10M Phone box, DXKeeper shows an empty log (which would be correct) and there seems to be no primate-level way of deleting the errant phone indication. My work is done, for now. Umm, does anyone know how to get that damned red W out of the phone box? It¡¯s starting to bother me¡ 73, Steve K4WA |
||||||||||||||||||||||||||||||||||||||||
|
Re: "The Windows January updates are a mess; here's why you should wait to install"
+ AA6YQ comments below
One good way to control/prevent Windows updates is the free utility from Gibson - InControl: <> + Nice! I've added a reference to this tool in the " Controlling Windows and Anti-Malware Updates" section of 73, Dave, AA6YQ |
to navigate to use esc to dismiss