Keyboard Shortcuts
Likes
- DXLab
- Messages
Search
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=ambersoft.com@groups.io> 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: CC-User@groups.io [mailto:CC-User@groups.io] On Behalf Of Lee Sawkins via groups.io Sent: Tuesday, April 01, 2025 10:25 AM To: CC-User@groups.io 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: DXLab@groups.io <DXLab@groups.io> On Behalf Of Stephen Rabinowitz via groups.io Sent: Monday, March 31, 2025 7:42 PM To: DXLab@groups.io 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: DXLab@groups.io <DXLab@groups.io> On Behalf Of Stephen Rabinowitz via groups.io
Sent: Monday, March 31, 2025 7:42 PM To: DXLab@groups.io 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 |
Re: MM to DXLab Bridge not working.
On 2025-03-31 1:36 PM, Rick Arzadon - N8XI via groups.io wrote:
First problem is there is No 'Setup Logging' in the Option Menu.The "Setup Logging" option is in the option menu of MMSSTV (not MMD). 73, ... Joe, W4TV On 2025-03-31 1:36 PM, Rick Arzadon - N8XI via groups.io wrote: Using Ver 1.13A of MMSSTV and Ver 6.0 of MMD. |
FW: [DXLab] IC-PW1 configuration in DXLabCommander
+ AA6YQ comments below
Dave, you note: “If the PW1 is connected to Commander's Secondary CAT port and no other device, then the only way CI-V collisions can occur is if the PW1 transmit CI-V messages.” Are you saying definitively that the PW1 is never shutting up? Could you can see this in an error log? + Yes, I should be able to do so. You should be able to see it in Commander's Messages window if you uncheck "Capture and display Primary CAT Port Messages" and check " Capture and display Secondary CAT Port Messages". The > and < characters to the immediate right of the timestamp will show whether Commander or the PW1 transmitted each message. 73, Dave, AA6YQ |
Re: IC-PW1 configuration in DXLabCommander
开云体育Dave, you note: “If the PW1 is connected to Commander's Secondary CAT port and no other device, then the only way CI-V collisions can occur is if the PW1 transmit CI-V messages.” Are you saying definitively that the PW1 is never shutting up? Could you can see this in an error log? ? 73, Dave, w6de ? From: DXLab@groups.io
<DXLab@groups.io> On Behalf Of Dave AA6YQ via groups.io
Sent: 30 March, 2025 23:42 To: DXLab@groups.io Subject: Re: [DXLab] IC-PW1 configuration in DXLabCommander ? + AA6YQ comments below
+ If the PW1 is connected to Commander's Secondary CAT port and no other device, then the only way CI-V collisions can occur is if the PW1 transmit CI-V messages. Larry K8UT's "riding the CI-V bus" document describes the conditions under
which it will do that. See section 4 in |
Re: IC-PW1 configuration in DXLabCommander
+ AA6YQ comments below
+ If the PW1 is connected to Commander's Secondary CAT port and no other device, then the only way CI-V collisions can occur is if the PW1 transmit CI-V messages. Larry K8UT's "riding the CI-V bus" document describes the conditions under which it will do that. See section 4 in ? ? ? 73, ? ? ? ? ? ? Dave, AA6YQ |
Re: IC-PW1 configuration in DXLabCommander
开云体育I have been working directly with Shige on this matter.? Shige did get DXLab Commander installed and working directly with his PW1.? However, the absence of CIV collisions is not consistent and most time fails to work properly after shut down and a restart.? Shige has performed exhaustive tests isolating various components and re-trying shut down and start up.? But the intermittent PW1 CIV collisions persist.? ? I believe the DXLab Commander PW1 CIV fix is working properly and there is a hardware intermittent somewhere we have been unable to detect. Shige is going to try a different hardware solution that I am sending him. ? 73, Dave, w6de ? From: DXLab@groups.io <DXLab@groups.io>
On Behalf Of Shigeru Ohsawa via groups.io
Sent: 20 March, 2025 22:24 To: DXLab@groups.io Subject: Re: [DXLab] IC-PW1 configuration in DXLabCommander ? ?Joe, W6TV, Dave AA6YQ, and Dave, W6DE ? I'm sorry. ? PC(DXLabCommander):USB A port?[USB cable]?IC-7600:USB B port PC(DXLabCommander):USB A port?CT-18(interface)?[REMOTE cable]?IC-PW1:Remote socket IC-7600:ACC-2 socket?[ACC cable]?IC-PW1:ACC-1 socket ? Does this tell you the status of the connection between my radio and my PC? The PC, IC-7600, and IC-PW1 are connected like this. In this state, IC-PW1 cannot be controlled well. ? Shige, JJ1BCM ? |
Re: Unable to upload to LotW
+ AA6YQ comments below
I've had one notice of a failed attempt to upload to LotW. I'm thinking that I need to manually upload later. I believe that this notice relates to a single QSO upload from DXLabs. I just don't know which one failed. Is there a DXLab way to find it? + Filter the Log Page Display with the SQL expression app_dxkeeper_lotw_qsl_sent <> 'Y' + Do any QSOs appear? 73, Dave AA6YQ |
Re: Double click on a spot doesn't change frequency on the RTX
I have recently stopped using a wireless keyboard and mouse and switched back to a wired keyboard and mouse due to too many missed keystrokes, missed mouse clicks, and difficulty with accurate mouse pointing.
toggle quoted message
Show quoted text
73, Dave, w6de -----Original Message-----
From: DXLab@groups.io <DXLab@groups.io> On Behalf Of Dave AA6YQ via groups.io Sent: 30 March, 2025 15:16 To: DXLab@groups.io Subject: Re: [DXLab] Double click on a spot doesn't change frequency on the RTX + AA6YQ comments below Now that you make me think about it, some months ago I've bought a new DELL Keyboard/Mouse wireless set. Apart from this i didn't make changes (hardware or software) except changing the mouse color pointer (Mouse Windows preferences) choosing black pointer on white background (I'm an Apple technician since 1984). After reading your post i restored the default setup (white pointer on white background) and double clicking on a spot now the frequency change! Incredible! + I'm glad that the "fix" was simple, Franco. + When the behavior of a DXLab application suddenly changes, it's essential to immediately determine what cause that change. If you procrastinate, you may forget information about what changes you made to your hardware and software that may be responsible. Dave, AA6YQ |