Date
1 - 13 of 13
Character by character lookup no good with QRZ
Jim Miller, AB3CV <jtmiller47@...>
When I type in a call sign into WSJT-x (v2.6.1) the characters get sent apparently thru SC to Pathfinder which makes immediate request on QRZ.
It doesn't take too much typing before QRZ throws up its hands and says "Too Many Requests".
Is there a way to keep this from happening?
Thanks
Jim ab3cv
Dave AA6YQ
+ AA6YQ comments below
When I type in a call sign into WSJT-x (v2.6.1) the characters get sent apparently thru SC to Pathfinder which makes immediate request on QRZ.
+ I'll assume that means you're using the direct interoperation between WSJT-X and DXLab.
It doesn't take too much typing before QRZ throws up its hands and says "Too Many Requests".
Is there a way to keep this from happening?
+ Yes: either
1. uncheck the Callbook box in the "WSJT-X" panel on the "Spot Sources" tab of Spotcollector's Configuration window, or
2. switch to an "unlimited" Callbook like HamQTH on the Callbook tab of DXKeeper's Configuration window, or
3. purchase an annual subscription to QRZ.com.
73,
Dave, AA6YQ
When I type in a call sign into WSJT-x (v2.6.1) the characters get sent apparently thru SC to Pathfinder which makes immediate request on QRZ.
+ I'll assume that means you're using the direct interoperation between WSJT-X and DXLab.
It doesn't take too much typing before QRZ throws up its hands and says "Too Many Requests".
Is there a way to keep this from happening?
+ Yes: either
1. uncheck the Callbook box in the "WSJT-X" panel on the "Spot Sources" tab of Spotcollector's Configuration window, or
2. switch to an "unlimited" Callbook like HamQTH on the Callbook tab of DXKeeper's Configuration window, or
3. purchase an annual subscription to QRZ.com.
73,
Dave, AA6YQ
Dave AA6YQ
When I type in a call sign into WSJT-x (v2.6.1) the characters get sent apparently thru SC to Pathfinder which makes immediate request on QRZ.
+ If you're using the direct interoperation, a callbook lookup is only initiated when you direct WSJT-X to log the QSO; callsign characters are not sent to QRZ one at a time, each triggering a "lookup".
73,
Dave, AA6YQ
+ If you're using the direct interoperation, a callbook lookup is only initiated when you direct WSJT-X to log the QSO; callsign characters are not sent to QRZ one at a time, each triggering a "lookup".
73,
Dave, AA6YQ
By far, Nr 3 is the best. Also you now have QRZ access with many other applications that use QRZ.
Outlook LT Gil W0MN
Hierro Candente Batir de Repente
44.08226 N 92.51265 W EN34rb
toggle quoted message
Show quoted text
Outlook LT Gil W0MN
Hierro Candente Batir de Repente
44.08226 N 92.51265 W EN34rb
-----Original Message-----
From: DXLab@groups.io <DXLab@groups.io> On Behalf Of Dave AA6YQ
Sent: Friday, February 24, 2023 6:58 PM
To: DXLab@groups.io
Subject: Re: [DXLab] Character by character lookup no good with QRZ
+ AA6YQ comments below
When I type in a call sign into WSJT-x (v2.6.1) the characters get sent apparently thru SC to Pathfinder which makes immediate request on QRZ.
+ I'll assume that means you're using the direct interoperation between WSJT-X and DXLab.
It doesn't take too much typing before QRZ throws up its hands and says "Too Many Requests".
Is there a way to keep this from happening?
+ Yes: either
1. uncheck the Callbook box in the "WSJT-X" panel on the "Spot Sources" tab of Spotcollector's Configuration window, or
2. switch to an "unlimited" Callbook like HamQTH on the Callbook tab of DXKeeper's Configuration window, or
3. purchase an annual subscription to QRZ.com.
73,
Dave, AA6YQ
--
W0MN EN34rb 44.08226 N 92.51265 W
Hierro candente, batir de repente
HP Laptop
From: DXLab@groups.io <DXLab@groups.io> On Behalf Of Dave AA6YQ
Sent: Friday, February 24, 2023 6:58 PM
To: DXLab@groups.io
Subject: Re: [DXLab] Character by character lookup no good with QRZ
+ AA6YQ comments below
When I type in a call sign into WSJT-x (v2.6.1) the characters get sent apparently thru SC to Pathfinder which makes immediate request on QRZ.
+ I'll assume that means you're using the direct interoperation between WSJT-X and DXLab.
It doesn't take too much typing before QRZ throws up its hands and says "Too Many Requests".
Is there a way to keep this from happening?
+ Yes: either
1. uncheck the Callbook box in the "WSJT-X" panel on the "Spot Sources" tab of Spotcollector's Configuration window, or
2. switch to an "unlimited" Callbook like HamQTH on the Callbook tab of DXKeeper's Configuration window, or
3. purchase an annual subscription to QRZ.com.
73,
Dave, AA6YQ
--
W0MN EN34rb 44.08226 N 92.51265 W
Hierro candente, batir de repente
HP Laptop
Jim Miller, AB3CV <jtmiller47@...>
I'm already a premium subscriber at QRZ.
I use the SC gateway from WSJT-x to SC. Not using JTALERT or anything similar.
I just tried it again. Typing an 'A" in the DX Call box of WSJT and without a carriage return immediately does a Pathfinder lookup to QRZ and produces the SV2RSG/A page.
Something is amiss....
SC v9.4.0 PF v5.3.5 WSJT-x v2.6.1
Win11 all updates.
jim ab3cv
I use the SC gateway from WSJT-x to SC. Not using JTALERT or anything similar.
I just tried it again. Typing an 'A" in the DX Call box of WSJT and without a carriage return immediately does a Pathfinder lookup to QRZ and produces the SV2RSG/A page.
Something is amiss....
SC v9.4.0 PF v5.3.5 WSJT-x v2.6.1
Win11 all updates.
jim ab3cv
Dave AA6YQ
+ AA6YQ comments below
I'm already a premium subscriber at QRZ.
+ Then QRZ should not be complaining about the number of lookups you initiate; you should take that up with them.
I use the SC gateway from WSJT-x to SC. Not using JTALERT or anything similar.
I just tried it again. Typing an 'A" in the DX Call box of WSJT and without a carriage return immediately does a Pathfinder lookup to QRZ and produces the SV2RSG/A page.
+ I'm not in the shack, but WSJT-X evidently sends a "here's a new callsign" message on any change to the contents of its "DX Call" box. I typically populate this box by clicking on a decoded callsign (in the WSJT-X "Band Activity" panel) of a station I wish to work, or by double-clicking on a callsign in SpotCollector's Spot Database Display.
73,
Dave, AA6YQ
JTAlert Support (VK3AMA)
On 28/02/2023 5:57 am, Dave AA6YQ wrote:
Consumers (software) of the WSJTX UDP messages should be utilizing some sort of de-bounce handler such that frequently changing status conditions are ignored until the changes stabilize. For example, JTAlert will only trigger a Callsign lookup once the DXCall changes have stabilized after 1000ms.
The relevant UDP Status message format is.
de Laurie VK3AMA
(JTAlert author)
WSJT-X evidently sends a "here's a new callsign" message on any change to the contents of its "DX Call" box.The is no "New Callsign" message within the WSJTX UDP API. There is a status message (#1) that is emitted whenever there is a change in any of several conditions including the DXCall value. WSJT will emit this status message for each character typed in the DXCall field. This is not new behavior, it has been done this way since the first release of WSJTX several years ago.
Consumers (software) of the WSJTX UDP messages should be utilizing some sort of de-bounce handler such that frequently changing status conditions are ignored until the changes stabilize. For example, JTAlert will only trigger a Callsign lookup once the DXCall changes have stabilized after 1000ms.
The relevant UDP Status message format is.
* Status Out 1 quint32
* Id (unique key) utf8
* Dial Frequency (Hz) quint64
* Mode utf8
* DX call utf8
* Report utf8
* Tx Mode utf8
* Tx Enabled bool
* Transmitting bool
* Decoding bool
* Rx DF quint32
* Tx DF quint32
* DE call utf8
* DE grid utf8
* DX grid utf8
* Tx Watchdog bool
* Sub-mode utf8
* Fast mode bool
* Special Operation Mode quint8
* Frequency Tolerance quint32
* T/R Period quint32
* Configuration Name utf8
* Tx Message utf8
de Laurie VK3AMA
(JTAlert author)
Dave AA6YQ
de AA6YQ comments below.
Consumers (software) of the WSJTX UDP messages should be utilizing some sort of de-bounce handler such that frequently changing status conditions are ignored until the changes stabilize.
+ Only hardware switches "bounce"; software selectors do not "bounce".
For example, JTAlert will only trigger a Callsign lookup once the DXCall changes have stabilized after 1000ms.
+ I dislike user interfaces based on time constants, as they produce different behavior as a function of the user's "timing". The Enter key is the traditional way of indicating that an entry is ready for processing: I'll see if that's possible with WSJT-X.
73,
Dave, AA6YQ
JTAlert Support (VK3AMA)
On 28/02/2023 7:01 am, Dave AA6YQ
wrote:
Only hardware switches "bounce"; software selectors do not "bounce"
I understand.
My use of "debounce" is due to its common usage in some software development circles. I personally have been referring to software debounce for decades.
A Bing search on "software debounce" yields in excess of 1 million hits.
de Laurie VK3AMA
Jim Miller, AB3CV <jtmiller47@...>
One reason I type in the box is to prep the WSJT-x apriori capability for someone like FK8CP to increase the likelihood of a first decode on a weak signal.
Of course I could always type it elsewhere and copy and paste.
jim (if i remembered....increasingly difficult...)
Of course I could always type it elsewhere and copy and paste.
jim (if i remembered....increasingly difficult...)
Dave AA6YQ
+ AA6YQ comments below
One reason I type in the box is to prep the WSJT-x apriori capability for someone like FK8CP to increase the likelihood of a first decode on a weak signal.
Of course I could always type it elsewhere and copy and paste.
+ The current situation wouldn't be problematic if QRZ weren't erroneously complaining.
73,
Dave, AA6YQ
Dave AA6YQ
Unfortunately, WSJT-X does not provide a way to wait until you've typed a full callsign into its "DX Call" box before sending that callsign to another application; it sends what you type, letter-by-letter. It also doesn't distinguish between specifying a new "DX Call" by typing or specifying a new "DX Call" by double-clicking in its "Band Activity" panel.
I've sent you a new version of the component I developed to enable direct interoperation between WSJT-X and SpotCollector that waits one half second before conveying a change in the WSJT-X "DX Call" to SpotCollector. I first tried a full second, as Laurie VK3AMA suggested, but that's too much of a delay when double-clicking a callsign in the WSJT-X "Band Activity" window. Half a second seems a reasonable compromise; please let me know how it goes...
73,
Dave, AA6YQ
toggle quoted message
Show quoted text
I've sent you a new version of the component I developed to enable direct interoperation between WSJT-X and SpotCollector that waits one half second before conveying a change in the WSJT-X "DX Call" to SpotCollector. I first tried a full second, as Laurie VK3AMA suggested, but that's too much of a delay when double-clicking a callsign in the WSJT-X "Band Activity" window. Half a second seems a reasonable compromise; please let me know how it goes...
73,
Dave, AA6YQ
-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Jim Miller, AB3CV
Sent: Monday, February 27, 2023 1:31 PM
To: DXLab@groups.io
Subject: Re: [DXLab] Character by character lookup no good with QRZ
I'm already a premium subscriber at QRZ.
I use the SC gateway from WSJT-x to SC. Not using JTALERT or anything similar.
I just tried it again. Typing an 'A" in the DX Call box of WSJT and without a carriage return immediately does a Pathfinder lookup to QRZ and produces the SV2RSG/A page.
Something is amiss....
SC v9.4.0 PF v5.3.5 WSJT-x v2.6.1
Win11 all updates.
jim ab3cv
From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Jim Miller, AB3CV
Sent: Monday, February 27, 2023 1:31 PM
To: DXLab@groups.io
Subject: Re: [DXLab] Character by character lookup no good with QRZ
I'm already a premium subscriber at QRZ.
I use the SC gateway from WSJT-x to SC. Not using JTALERT or anything similar.
I just tried it again. Typing an 'A" in the DX Call box of WSJT and without a carriage return immediately does a Pathfinder lookup to QRZ and produces the SV2RSG/A page.
Something is amiss....
SC v9.4.0 PF v5.3.5 WSJT-x v2.6.1
Win11 all updates.
jim ab3cv