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: Unable to upload to LotW
* NU6T comment below 6. in an hour or so, click the "Sync LoTW QSOs" button ? * Two QSOs show in the Log QSOs tab.?? ? *? I also see an Error File notice and in the notice I see a long list of errors for 2025-04-01.? Examples below: ? *? The errors are in about 82 sets of 7 of the first followed by 1 of the second. + Normally, interoperation with LoTW does not require all of these manual steps. You can configure DXKeeper to automatically upload QSOs to LoTW as you log them. WinWarbler and all of the digital mode applications that interoperate with DXKeeper can be configured to direct DXKeeper to automatically upload QSOs to LoTW as you log them. Then periodically invoking DXKeeper's "Sync All" command is all that's required.? ? * I thought I had the system set up to log each QSO to LotW and ClubLog, and checked in Lotw every so often and thought they were showing up there.? I'll double check. + Note: if you're a contester and concerned with optimizing rate, importing your contest log into DXKeeper at the end of each contest and directing DXKeeper to upload your QSOs is the better approach. ? *? I use N1MM+ and upload files to my log after each contest and then to LotW, and ClubLog.? I've only recently begun to use ClubLog. ? *? Rate optimization?is just a vertical dream.... + Unless you enjoy manual operations, avoid uploading QSOs to LoTW without first importing them into DXKeeper and uploading them to DXKeeper from there. ? *Grin, no I don't.? I'm looking forward to having enough knowledge to successfully keep up the automation of this amazing software. + See? ? *? Thank You + Similar automation is provided for Club Log, eQSL, and QRZ. ? *? Thank you. Rich, NU6T On Tue, Apr 1, 2025 at 1:18?PM Dave AA6YQ via <aa6yq=[email protected]> wrote:
Richard Hill |
|
Re: FW: [CC-User] Bogus DX Spot Attacks on Clusters
This is not the first time it happened.
toggle quoted message
Show quoted text
I informed Dave, but no action was needed in DXLab. Eddy ON5JK Op 1/04/2025 om 18:47 schreef Dave AA6YQ: FYI: |
|
Re: Unable to upload to LotW
+ AA6YQ comments below
Dave, I proceeded through the instructions to:? 3. click the "Upload to LoTW" button+ That means at least 1 of those 95 QSOs - 4E1DX - had already been uploaded to LoTW from your current computer, even though the QSO doesn't so indicate.? + Please do the following: 1. Filter the Log Page Display with the SQL expression app_dxkeeper_lotw_qsl_sent <> 'Y' 2. On the Main window's QSL tab, 2a. set the "QSL Via" panel to LoTW 2b. click the Clear button beneath the "QSL Queue" 2c. click the "Update from LoTW" button; this will direct LoTW to report the status of the QSOs in the Log Page Display as a result of step 1 3. When step 2b finished, again filter the Log Page Display with the SQL expression app_dxkeeper_lotw_qsl_sent <> 'Y' Do any QSOs appear in the Log Page Display? If so, on the Main window's QSL tab, 4, click the "Add All" button 5. click the "Upload to LoTW" button; this time, we're only seeking to upload QSOs that we are certain have not already been updated 6. in an hour or so, click the "Sync LoTW QSOs" button + Normally, interoperation with LoTW does not require all of these manual steps. You can configure DXKeeper to automatically upload QSOs to LoTW as you log them. WinWarbler and all of the digital mode applications that interoperate with DXKeeper can be configured to direct DXKeeper to automatically upload QSOs to LoTW as you log them. Then periodically invoking DXKeeper's "Sync All" command is all that's required.? + Note: if you're a contester and concerned with optimizing rate, importing your contest log into DXKeeper at the end of each contest and directing DXKeeper to upload your QSOs is the better approach. + Unless you enjoy manual operations, avoid uploading QSOs to LoTW without first importing them into DXKeeper and uploading them to DXKeeper from there. + See? + Similar automation is provided for Club Log, eQSL, and QRZ. ? ? ? 73, ? ? ? ? ? Dave, AA6YQ ?
? |
|
Re: Unable to upload to LotW
Dave, I proceeded through the instructions to:?
3. click the "Upload to LoTW" button At that point I received a message that, in part, there were no QSLs to upload: "TQSL Version 2.7.5 [v2.7.5] Signing using Callsign NU6T, DXCC Entity UNITED STATES OF AMERICA Already Uploaded QSO detected on line 5 CALL: 4E1DX TIME_ON: 174200 QSO_DATE: 20250401 MODE: FT8 BAND: 20M FREQ: 14.074996 Duplicate QSO detected No QSOs to upload Final Status: No QSOs to upload(8)" It is not clear to me whether the "no QSOs to upload" relates only to the 4E1DX QSO or to the set of 95 QSOs. I will continue with instruction #4 in an hour or so. Rich, NU6T On Tue, Apr 1, 2025 at 12:08?PM Dave AA6YQ via <aa6yq=[email protected]> wrote:
--
Richard Hill |
|
Re: Unable to upload to LotW
+ AA6YQ comments below
Dave, thank you.? Yes, I show 95 QSLs as a result of the query:? app_dxkeeper_lotw_qsl_sent <> 'Y'+ With those 95 QSOs present in the Log Page Display, select the Main window's QSL tab, and 1. set the "QSL VIa" panel to LoTW 2. click the "Add All" button; this will populate the QSL Queue with those 95 QSOs 3. click the "Upload to LoTW" button 4. wait an hour (the LoTW Queue duration was recently 18 minutes), and then 4a. click the "Sync LoTW QSOs" button 4b. on the Main window's "Log QSOs" tab, click the Filter panel's LoTW button; do any QSOs appear in the "Log Page Display"? ? ? ? 73, ? ? ? ? ? ? Dave, AA6YQ |
|
Re: Unable to upload to LotW
Dave, thank you.? Yes, I show 95 QSLs as a result of the query:?
app_dxkeeper_lotw_qsl_sent <> 'Y' Rich, NU6T On Sun, Mar 30, 2025 at 3:34?PM Dave AA6YQ via <aa6yq=[email protected]> wrote: + AA6YQ comments below --
Richard Hill |
|
Re: SpotCollector SPProb
+ AA6YQ comments below
+ Thanks for the errorlog.txt file. I shows that in the General panel on the Configuration window's General tab, neither the "Capture location info from notes" nor the "Lookup missing location info" options are enabled. Without an accurate location, SpotCollector does not direct PropView to generate a forecast. + After you configure SpotCollector, I suggest that you direct the Launcher to create and populate a Workspace containing the settings for all of your DXLab applications. Then the next time something stops working as expected, you can direct the Launcher to recover those settings as a second diagnostic step after rebooting Windows. See https://www.dxlabsuite.com/dxlabwiki/CreateUpdateWorkspace ? ? ? ?73, ? ? ? ? ? ? ?Dave, AA6YQ ?
? |
|
FW: [CC-User] Bogus DX Spot Attacks on Clusters
FYI:
From: [email protected] [mailto:[email protected]] On Behalf Of Lee Sawkins via groups.io Sent: Tuesday, April 01, 2025 10:25 AM To: [email protected] Subject: Re: [CC-User] Bogus DX Spot Attacks on Clusters What happened this weekend was that tens of thousands of bogus spots were entered into the cluster system. These spots were all for SSB. Since there are no SSB skimmers available yet, all of these spots appeared to be manually entered, but in fact they were generated by a computer. Normally the human entered spots never are more than 60 per minute. During the weekend spots that were bogus were entered at many thousands per minute. These spots were targeting specific active calls. These spots were giving different frequencies on all contest bands for each bogus spot. These spots had same DX call and a different spotter call and different originating cluster call. This caused many nodes to get bogged down trying to process all this data. Some crashed. Others got hopelessly behind and continued sending data to my cluster which dropped the spots because they were too old. Millions of spots were being dropped. My cluster limits the number of spots to 60 per minute. This limited bogus spots but also good spots in each minute. When bogus spots stopped, then all the new good ones got through. Lee VE7CC |
|
Re: AT&T ending email to text on June18
+ AA6YQ comments below
For me this will mean no more SpotCollector emails to my iPhone via SMS alerting me to a potentially needed and workable spot.+ According to the Perplexity response appended below, you can configure your iPhone's email client to alert you when an email message from SpotCollector is received. Please give this a try, and post your results here. ? ? ? ? 73, ? ? ? ? ? ? ? Dave, AA6YQ Yes, an iPhone email client can be configured to alert the user when a message from a specific email address is received. Here are the methods:
Using Apple's Mail App
1. VIP Feature: Add the sender's email address to your VIP list in the Mail app. Go to the Mail app, tap "VIP," then "Add VIP," and select or enter the desired contact. Enable VIP alerts in *Settings > Notifications > Mail > Customize Notifications* and turn on notifications for VIPs only[4][8]. 2. Custom Sounds: You can customize notification sounds for VIP emails in *Settings > Notifications > Mail > Customize Notifications*[7]. Gmail App 1. Labels and Filters: On Gmail's web interface, create a label and filter for the specific sender. Apply the label to emails from that sender. On your iPhone, enable notifications for that label by going to *Settings > Manage Labels* in the Gmail app[5]. 2. Priority Notifications: Mark emails as "important" or use the "star" feature to prioritize notifications for specific senders[2][5]. Using Third-Party Apps 1. Outlook App: Add the sender as a "favorite" in Outlook to receive notifications exclusively for emails from that sender[3]. 2. eNotify: This app allows advanced customization, such as continuous alerts until the email is addressed[9]. These methods ensure you receive timely alerts without being overwhelmed by notifications from other emails. Citations: [1] https://www.reddit.com/r/ios/comments/w872j3/how_do_i_create_a_custom_notificationalarmtrigger/ [2] https://www.youtube.com/watch?v=tlkhLUN1e1s [3] https://www.reddit.com/r/GMail/comments/1dg7veu/alerts_on_iphone_for_emails_received_from/ [4] https://support.apple.com/guide/iphone/set-email-notifications-iphc13a970c8/ios [5] https://www.youtube.com/watch?v=nrA4TKTnCtg [6] https://apple.stackexchange.com/questions/295541/can-i-get-a-notification-on-my-iphone-when-i-receive-a-certain-email [7] https://discussions.apple.com/thread/255472172 [8] https://www.businessinsider.com/guides/tech/how-to-get-email-notifications-on-iphone [9] https://apple.stackexchange.com/questions/42618/app-solution-for-having-alerts-for-emails [10] https://getemil.io/guides/iphone-gmail-notifications-from-specific-sender/ ---
Answer from Perplexity: pplx.ai/share |
|
Re: DX Marathon Year
Disregard. I see it is Ctrl. However, the help popup says at the end "Depress Alt to" and that is it.? Thanks 73On Tue, Apr 1, 2025 at 6:21?AM Kent Olsen <kilo6dko@...> wrote:
|
|
Re: SpotCollector SPProb
+ AA6YQ comments below
I rebooted Windows 11, with no improvement. + OK. Please do the following: 1. on the General tab of SpotCollector's Configuration window, check the "Log debugging info" box 2. terminate SpotCollector 3. start SpotCollector 4. wait until at least 5 new Spot Database Entries are created for stations operating on 80m through 10m 5. on the General tab of SpotCollector's Configuration window, uncheck the "Log debugging info" box 6. attach the errorlog.txt file from your SpotCollector folder to an email message, and send the message to me via aa6yq (at) ambersoft.com 73, Dave, AA6YQ From: [email protected] <[email protected]> On Behalf Of Stephen Rabinowitz via groups.io Sent: Monday, March 31, 2025 7:42 PM To: [email protected] Subject: [DXLab] SpotCollector SPProb The short path probability box on the Spotcollector 9.8.3 main panel has no entries, as it used to do. I don't know what I changed to cause this. On the configuration general tab, in the Propagation Prediction panel, the enable SNR box and for all stations boxes are checked. The default required SNR is set to 0 db. PropView 2.0.7 is open. On the config prediction tab, all bands except 60m are selected. The required SNR for CW is 10, for SSB 20, for FT8 -24. What am I missing? 73, Steve K2SN |
|
Re: SpotCollector SPProb
开云体育I rebooted Windows 11, with no improvement. ? From: [email protected] <[email protected]> On Behalf Of Stephen Rabinowitz via groups.io
Sent: Monday, March 31, 2025 7:42 PM To: [email protected] Subject: [DXLab] SpotCollector SPProb ? The short path probability box on the Spotcollector 9.8.3 main panel has no entries,?as it used?to do. I don't know what I changed to cause this. On the configuration general tab, in the Propagation Prediction panel, the enable SNR box and for all stations boxes are checked. The default required SNR is set to 0 db. PropView 2.0.7 is open. On the config prediction tab, all bands except 60m are selected. The required SNR for CW is 10, for SSB 20, for FT8 -24. What am I missing? 73, Steve K2SN |
|
Re: SpotCollector SPProb
+ AA6YQ comments below
The short path probability box on the Spotcollector 9.8.3 main panel has no entries, as it used to do. I don't know what I changed to cause this. On the configuration general tab, in the Propagation Prediction panel, the enable SNR box and for all stations boxes are checked. The default required SNR is set to 0 db. PropView 2.0.7 is open. On the config prediction tab, all bands except 60m are selected. The required SNR for CW is 10, for SSB 20, for FT8 -24. What am I missing? + As a first diagnostic step, please reboot Windows, and then start your DXLab applications. 73, Dave, AA6YQ |
|
SpotCollector SPProb
开云体育The short path probability box on the Spotcollector 9.8.3 main panel has no entries,?as it used?to do. I don't know what I changed to cause this. On the configuration general tab, in the Propagation Prediction panel, the enable SNR box and for all stations boxes are checked. The default required SNR is set to 0 db. PropView 2.0.7 is open. On the config prediction tab, all bands except 60m are selected. The required SNR for CW is 10, for SSB 20, for FT8 -24. What am I missing? 73, Steve K2SN |
Kent N6WT
to navigate to use esc to dismiss