|
Re: SPOTCOLLECTOR ENHANCEMENTs (2)
Jose - N4BAA <jose-castillo@...>
### N4BAA comments -----Original Message-----
From: Dave AA6YQ <aa6yq@...> To: DXLab@groups.io Sent: Wed, Dec 29, 2021 11:36 pm Subject: Re: [DXLab] SPOTCOLLECTOR ENHANCEMENTs (2) + AA6YQ comments below
DF meaning or referring to the "freq" column in WSJT-X . In Spot Collector, it is annotated in the Notes column with the syntax for example like this: [1806 DF] + Thanks. So in the user manual's explanation, "Some modes include additional information such as frequency offset from nominal (DF)", the word "nominal" refers to the transceiver frequency. + With WSJT-X directly interoperating with DXLab, the local spots it generates are of the signal frequency (transceiver frequency plus frequency offset), and logged QSOs specify the signal frequency. + Is that not the case with local spots and logged QSOs initiated by JTAlert? ### 100% correct. The genesis of my question was intended to seek to understand an efficient way to be ablet to double click on a spot presented in SC (assuming a "NOTE" reflecting a DF) let's say for FT8 or FT4 and have WSJT-X's Rx data properly changed/updated to reflect that 'frequency offset' to accurately set things up for communication with them.
73, Dave, AA6YQ |
|
|
|
Re: an analysis of Remote Beacon Network (RBN) spots and their impact on SpotCollector's performance
Dave AA6YQ
+ AA6YQ comments below
* The time I spend helping users get things working is time I can't spend moving DXLab forward. Now you've forced me to spend time making sure that a DNS or hosts file entry can't be used to establish a direct connection to telnet.reversebeacon.net. Thanks a lot. I mean, come on. A hostname check will stop 99.9% of people from using it. The RBN guy here says it isn't a problem, and you're going to go out of your way to stop me from doing something I've been doing, with great success I might add, for a year? I guess I'll start writing a telnet proxy.. + Simply connect to a DX cluster like n6ws.ddns.net:7300 that conveys RBN spots. There will be no loss of functionality from what you have now and, according the RBN folks, you will see fewer skimmer-busted callsigns. Please try this, and report your results here. 73, Dave, AA6YQ |
|
|
|
Re: SC 8.9.4 not staying connected
Dave AA6YQ
+ AA6YQ comments below
+ "Yellow" means "connected, but not logged in". Choose one of those spot sources, and uncheck its Hide and "ANN/TALK" boxes on the Configuration window's General tab; a "Spot Source" window will appear that shows SpotCollector's interactions with the spot source. In the lower-left corner, there will be a Connect or Disconnect button. If there's a Disconnect button, click it, and a Connect button should appear. Then click the Connect button; what appears in the display panel that occupies the upper section of the window? The message in window is: "Winsock error # 10053- connection aborted due to timeout or other failure" + That means SpotCollector cannot connect to the spot source. Either the spot source is down, or something at your end is preventing SpotCollector from connecting to it. As a side note, clicking the disconnect/connect button shows the spotter closing and connecting, but the "yellow" button stays yellow, and there are no new spots even after waiting several minutes...the only way I can get Spotcollector to start showing spots again is to close down that program and restart... + So that I can see what's going on, please do the following: 1. start SpotCollector if it's not already running 2. on the Configuration window's General tab, check the "Log debugging info" box 3. terminate SpotCollector 4. start SpotCollector 5. wait 5 minutes 6. on the Configuration window's General tab, uncheck the "Log debugging info" box 7. 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 |
|
|
|
Re: Trouble Getting Spots.
Dave AA6YQ
+ AA6YQ comments below
What would be a symptom of not having enough Horsepower? + Extremely slow performance. As im can attest to, the ONLY change we made was to shut down all but VE7CC. + That's incorrect. SpotCollector was receiving RBN spots all along, but you didn't realize it because your Spot Database Display's Source column was too narrow to see the -# appended to the spotting stations callsigns. huh? + So far, every issue you've raised has been resolved via correcting your configuration. 73, Dave, AA6YQ |
|
|
|
Re: Trouble Getting Spots.
Joe WB9SBD
I'Ll change it back or
something. probably gonna leave it off anyway.
toggle quoted message
Show quoted text
Joe WB9SBD On 12/29/2021 6:49 PM, Jim N7US wrote:
|
|
|
|
Re: Trouble Getting Spots.
Oops, I should have left it dxspots.com and port 23. That cluster is a mirror image of VE7CC.
I think you were getting cluster spots from VE7CC but the source column was too narrow to show the “-#” indicating a Skimmer.
73, Jim N7US
From: DXLab@groups.io <DXLab@groups.io> On Behalf Of
Joe WB9SBD via groups.io
Sent: Wednesday, December 29, 2021 18:32 To: DXLab@groups.io Subject: Re: [DXLab] Trouble Getting Spots.
Yes incorrect port but also remember it was still getting data true? On 12/29/2021 5:31 PM, Jim N7US wrote: One spot source, AE5E, had an incorrect port. Another was the RBN, and I forget the other one.I suggested he connect to only VE7CC to be sure that would work, which it did. Joe is getting unfiltered spots from VE7CC, so he has LOTS.Jim N7US-----Original Message-----From: DXLab@groups.io <DXLab@groups.io> On Behalf Of Dave AA6YQ via groups.ioSent: Wednesday, December 29, 2021 17:19To: DXLab@groups.ioSubject: Re: [DXLab] Trouble Getting Spots.+ AA6YQ comments belowJim did a Teamviewer thing with me.We got it working now.but the ONLY change we did was to have ONLY VE7CC be the spot source, and none others.+ Many thanks to Jim N7US for his hands-on help!Possible to use up to 4, just not at the same time it seems here.+ That's false, unless the problem is that your system lacks the horsepower to handle more than one spot source. Spot sources are independent of each other: one spot source cannot prevent the correct operation of another spot source.73,Dave, AA6YQ |
|
|
|
Re: an analysis of Remote Beacon Network (RBN) spots and their impact on SpotCollector's performance
Jon KM8V
On Wed, Dec 29, 2021 at 06:26 PM, Dave AA6YQ wrote:
* The time I spend helping users get things working is time I can't spend moving DXLab forward. Now you've forced me to spend time making sure that a DNS or hosts file entry can't be used to establish a direct connection to telnet.reversebeacon.net. Thanks a lot.I mean, come on. A hostname check will stop 99.9% of people from using it. The RBN guy here says it isn't a problem, and you're going to go out of your way to stop me from doing something I've been doing, with great success I might add, for a year? I guess I'll start writing a telnet proxy.. |
|
|
|
Re: SC 8.9.4 not staying connected
Neil G
+ "Yellow" means "connected, but not logged in". Choose one of those spot sources, and uncheck its Hide and "ANN/TALK" boxes on the Configuration window's General tab; a "Spot Source" window will appear that shows SpotCollector's interactions with the spot source. In the lower-left corner, there will be a Connect or Disconnect button. If there's a Disconnect button, click it, and a Connect button should appear. Then click the Connect button; what appears in the display panel that occupies the upper section of the window?
The message in window is: "Winsock error # 10053- connection aborted due to timeout or other failure" as a side note, clicking the disconnect/connect button shows the spotter closing and connecting, but the "yellow" button stays yellow, and there are no new spots even after waiting several minutes... the only way I can get Spotcollector to start showing spots again is to close down that program and restart... 73 Neil ,AE1P |
|
|
|
Re: Trouble Getting Spots.
Joe WB9SBD
Yes incorrect port but also
remember it was still getting data true?
toggle quoted message
Show quoted text
it was the DXSPOTS.COM, you changed to .NET and a different port. But as .COM it was showing spots. soo strange he he he. Joe WB9SBD On 12/29/2021 5:31 PM, Jim N7US wrote:
One spot source, AE5E, had an incorrect port. Another was the RBN, and I forget the other one. I suggested he connect to only VE7CC to be sure that would work, which it did. Joe is getting unfiltered spots from VE7CC, so he has LOTS. Jim N7US -----Original Message----- From: DXLab@groups.io <DXLab@groups.io> On Behalf Of Dave AA6YQ via groups.io Sent: Wednesday, December 29, 2021 17:19 To: DXLab@groups.io Subject: Re: [DXLab] Trouble Getting Spots. + AA6YQ comments below Jim did a Teamviewer thing with me. We got it working now. but the ONLY change we did was to have ONLY VE7CC be the spot source, and none others. + Many thanks to Jim N7US for his hands-on help! Possible to use up to 4, just not at the same time it seems here. + That's false, unless the problem is that your system lacks the horsepower to handle more than one spot source. Spot sources are independent of each other: one spot source cannot prevent the correct operation of another spot source. 73, Dave, AA6YQ |
|
|
|
Re: Trouble Getting Spots.
Joe WB9SBD
What would be a symptom of not
having enough Horsepower?
toggle quoted message
Show quoted text
As im can attest to, the ONLY change we made was to shut down all but VE7CC. I already had the direct feed from the RBN of when jim connected, shut off. and like i said once we shut off the other two, it all started working. huh? Joe WB9SBD On 12/29/2021 5:18 PM, Dave AA6YQ
wrote:
|
|
|
|
Re: Launcher installation issues
Dave AA6YQ
+ AA6YQ comments below
Thank you Dave, I know you are busy with a ton of stuff. + Helping users overcome problems with DXLab applications is my highest priority.
I am not critical with this as it just an effort to use a laptop with a new small rig. I can do something else if it comes to that. As far as the 'administrator' thread in these messages go, I am aware of the need to be elevated if you decide to move the folder to a protected area. This is not the case and never has been. Launcher was installed as directed. + In what folder is the Launcher installed?
Launcher does appear in the task manager. This is the only way I have been able to kill the process without rebooting and trying to re-run the application after a change has been made. + Thanks. When you start it, does the Launcher appear on the Windows Task Bar? |
|
|
|
Re: Launcher installation issues
Thank you Dave, I know you are busy with a ton of stuff. I am not critical with this as it just an effort to use a laptop with a new small rig. I can do something else if it comes to that. As far as the 'administrator' thread in these messages go, I am aware of the need to be elevated if you decide to move the folder to a protected area. This is not the case and never has been. Launcher was installed as directed.
toggle quoted message
Show quoted text
Launcher does appear in the task manager. This is the only way I have been able to kill the process without rebooting and trying to re-run the application after a change has been made. One little bit more information, this is a fairly new Dell i7 machine that came with windows 10. I accepted the invitation to upgrade to Windows 11 and that is its current state. To be fair, I never tried to load Launcher under the previous OS so I cannot comment on usability with Windows 10 (on this laptop). So, it really is more upsetting because I cannot solve this issue than it is not having the ability to run DXLabs on this laptop. Again, no need to spend any more time on this. I will muddle with it and let you know if I come up with anything. Thanks again for your help. And thank you Neil for your input. Joe -----Original Message-----
From: DXLab@groups.io <DXLab@groups.io> On Behalf Of Dave AA6YQ Sent: Wednesday, December 29, 2021 18:41 To: DXLab@groups.io Subject: Re: [DXLab] Launcher installation issues + AA6YQ comments below Niel, the instructions say “Log into an account with administrator privilege” I am, of course, the administrator on this laptop. So I have done exactly what the instructions said accepting all the defaults and that is why the original message was sent. I went through all these other iterations trying to see if something would work. If you have read the last message I posted about Windows Defender you can see my multiple attempts at trying to fix this. Also, by default the Icon that appears on the desktop after installation appears with a Windows shield on it indicating that it wants to be run with elevated privileges. So, in any iteration of trying to run this ap, it runs but does not display the Launcher window. + Logging into an account with administrator privilege is only required if you install a DXLab application into a folder that Windows considers "protected", like C:\Program Files (x86)\DXLab + If you install your DXLab applications into the default folder C:\DXLab this is not required. + After you start the Launcher, please start the Windows Task Manager. Does "DXLabLauncher" appear in the list of running applications? 73, Dave, AA6YQ |
|
|
|
Re: Trouble Getting Spots.
Joe Subich, W4TV
On 2021-12-29 6:31 PM, Jim N7US wrote:
One spot source, AE5E, had an incorrect port.AE5E (a.k.a. DXSpots.com) is quite happily sending my *LOTS* of skimmer spots on port 23. 73, ... Joe, W4TV On 2021-12-29 6:31 PM, Jim N7US wrote: One spot source, AE5E, had an incorrect port. Another was the RBN, and I forget the other one. |
|
|
|
Re: Spot Collector not removing beacons
Dave AA6YQ
Thanks for the errorlog, Peter!
toggle quoted message
Show quoted text
It shows that your spot source is removing the /B the from and placing NCDXF B in the spot notes: 2021-12-29 21:36:09.340 > from NC7J: DX de K1TTT-#: 14100.0 4U1UN CW 21 dB 19 WPM NCDXF B 2136Z Your choices are 1. switch to a spot source that doesn't alter the spot data in this way 2. use a filter that hides spot database entries whose cumulative spot notes include NCDXF B 73, Dave, AA6YQ -----Original Message-----
From: Peter Dougherty [mailto:Peter@...] Sent: Wednesday, December 29, 2021 4:47 PM To: Dave AA6YQ Subject: Spot Collector not removing beacons Please find my ErrorLog.txt file attached. It is picking up all NCDXF beacon cluster spots (i.e. YV5B, ZS6DN, etc), but only triggering a "needed" alarm for 4U1UN. I see the logic, since I haven't worked 4U1UN this year, and I had Marathon checked (I have been frightfully inactive for the last two years), but the Special Callsigns filter should take care of the 4U1UN beacon spots, I should think, and leave the legit human-activity spots (FT8, CW, etc) for the UN. This is a screenshot of my Special Filters list. |
|
|
|
Re: Launcher installation issues
Dave AA6YQ
+ AA6YQ comments below
Niel, the instructions say “Log into an account with administrator privilege” I am, of course, the administrator on this laptop. So I have done exactly what the instructions said accepting all the defaults and that is why the original message was sent. I went through all these other iterations trying to see if something would work. If you have read the last message I posted about Windows Defender you can see my multiple attempts at trying to fix this. Also, by default the Icon that appears on the desktop after installation appears with a Windows shield on it indicating that it wants to be run with elevated privileges. So, in any iteration of trying to run this ap, it runs but does not display the Launcher window. + Logging into an account with administrator privilege is only required if you install a DXLab application into a folder that Windows considers "protected", like C:\Program Files (x86)\DXLab + If you install your DXLab applications into the default folder C:\DXLab this is not required. + After you start the Launcher, please start the Windows Task Manager. Does "DXLabLauncher" appear in the list of running applications? 73, Dave, AA6YQ |
|
|
|
Re: SPOTCOLLECTOR ENHANCEMENTs (2)
Dave AA6YQ
+ AA6YQ comments below
DF meaning or referring to the "freq" column in WSJT-X . In Spot Collector, it is annotated in the Notes column with the syntax for example like this: [1806 DF] + Thanks. So in the user manual's explanation, "Some modes include additional information such as frequency offset from nominal (DF)", the word "nominal" refers to the transceiver frequency. + With WSJT-X directly interoperating with DXLab, the local spots it generates are of the signal frequency (transceiver frequency plus frequency offset), and logged QSOs specify the signal frequency. + Is that not the case with local spots and logged QSOs initiated by JTAlert? 73, Dave, AA6YQ |
|
|
|
Re: Trouble Getting Spots.
One spot source, AE5E, had an incorrect port. Another was the RBN, and I forget the other one.
toggle quoted message
Show quoted text
I suggested he connect to only VE7CC to be sure that would work, which it did. Joe is getting unfiltered spots from VE7CC, so he has LOTS. Jim N7US -----Original Message-----
From: DXLab@groups.io <DXLab@groups.io> On Behalf Of Dave AA6YQ via groups.io Sent: Wednesday, December 29, 2021 17:19 To: DXLab@groups.io Subject: Re: [DXLab] Trouble Getting Spots. + AA6YQ comments below Jim did a Teamviewer thing with me. We got it working now. but the ONLY change we did was to have ONLY VE7CC be the spot source, and none others. + Many thanks to Jim N7US for his hands-on help! Possible to use up to 4, just not at the same time it seems here. + That's false, unless the problem is that your system lacks the horsepower to handle more than one spot source. Spot sources are independent of each other: one spot source cannot prevent the correct operation of another spot source. 73, Dave, AA6YQ |
|
|
|
Re: Launcher installation issues
Niel, the instructions say “Log into an account with administrator privilege” I am, of course, the administrator on this laptop. So I have done exactly what the instructions said accepting all the defaults and that is why the original message was sent. I went through all these other iterations trying to see if something would work. If you have read the last message I posted about Windows Defender you can see my multiple attempts at trying to fix this. Also, by default the Icon that appears on the desktop after installation appears with a Windows shield on it indicating that it wants to be run with elevated privileges. So, in any iteration of trying to run this ap, it runs but does not display the Launcher window.
Thanks
Joe
From: DXLab@groups.io <DXLab@groups.io> On Behalf Of neil_zampella
Sent: Wednesday, December 29, 2021 15:55 To: DXLab@groups.io Subject: Re: [DXLab] Launcher installation issues
Don't run with Administrator privileges .... the 'Getting Started' article listed here: http://www.dxlabsuite.com/dxlabwiki/RunningOnWin7 On 12/29/2021 2:19 PM, dxradio33 wrote:
|
|
|
|
Re: an analysis of Remote Beacon Network (RBN) spots and their impact on SpotCollector's performance
Dave AA6YQ
* More AA6YQ comments below
+ If it's possible, it must be 100% reliable on every reasonable computer configuration. Since Remote Beacon Net folks have made it clear here that they do not want SpotCollector users to directly connect to telnet.reversebeacon.net, my development time is better spent on tasks more beneficial to more DXLab users. I guess. Hopefully, it will just be a hostname check that I can, if desired, get around with a DNS or hosts file entry. * The time I spend helping users get things working is time I can't spend moving DXLab forward. Now you've forced me to spend time making sure that a DNS or hosts file entry can't be used to establish a direct connection to telnet.reversebeacon.net. Thanks a lot. 73, Dave, AA6YQ |
|
|
|
Re: SPOTCOLLECTOR ENHANCEMENTs (2)
Jose - N4BAA <jose-castillo@...>
Understood.
DF meaning or referring to the "freq" column in WSJT-X .
In Spot Collector, it is annotated in the Notes column with the syntax for example like this:
[1806 DF]
Jose -----Original Message-----
From: Dave AA6YQ <aa6yq@...> To: DXLab@groups.io Sent: Wed, Dec 29, 2021 10:07 pm Subject: Re: [DXLab] SPOTCOLLECTOR ENHANCEMENTs (2) + AA6QY comments below
+ For what is "DF" an abbreviation? ### From https://physics.princeton.edu/pulsar/k1jt/wsjtx-doc/wsjtx-main-2.0.1.html .. ...frequency offset from nominal (DF) I have JTAlert configured to send Spot Collector dB & DF & DT for each decoded signal. These values are displayed in SC's Notes column. + All the manual you cited says about DF is "Some modes include additional information such as frequency offset from nominal (DF)" + It doesn't explain what DF is, in what units it is measured, for which modes it is displayed, or how it should be used. If WSJT-X version 2.4.0 is displaying DF when configured for FT4 or FT8, I don't see it. 73, Dave, AA6YQ |
|
|