Menu
▾
▴
wsjt-devel — WSJT software development
You can subscribe to this list here.
| 2007 |
Jan
(30) |
Feb
|
Mar
(10) |
Apr
(60) |
May
(62) |
Jun
|
Jul
(3) |
Aug
(3) |
Sep
(10) |
Oct
(17) |
Nov
(1) |
Dec
(14) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2008 |
Jan
|
Feb
(21) |
Mar
(4) |
Apr
(15) |
May
(37) |
Jun
(98) |
Jul
(120) |
Aug
(1) |
Sep
(14) |
Oct
|
Nov
(31) |
Dec
(8) |
| 2009 |
Jan
(1) |
Feb
(1) |
Mar
|
Apr
(25) |
May
(88) |
Jun
(5) |
Jul
(31) |
Aug
(25) |
Sep
(4) |
Oct
(19) |
Nov
(119) |
Dec
(11) |
| 2010 |
Jan
(3) |
Feb
(19) |
Mar
(4) |
Apr
|
May
(7) |
Jun
(17) |
Jul
|
Aug
(4) |
Sep
(20) |
Oct
(3) |
Nov
(29) |
Dec
(86) |
| 2011 |
Jan
(6) |
Feb
|
Mar
(6) |
Apr
(8) |
May
(1) |
Jun
(12) |
Jul
(9) |
Aug
(4) |
Sep
(7) |
Oct
(9) |
Nov
|
Dec
(1) |
| 2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(7) |
Jun
(5) |
Jul
|
Aug
|
Sep
(5) |
Oct
|
Nov
|
Dec
|
| 2013 |
Jan
(10) |
Feb
(7) |
Mar
(4) |
Apr
(76) |
May
(66) |
Jun
(101) |
Jul
(210) |
Aug
(255) |
Sep
(83) |
Oct
(18) |
Nov
(3) |
Dec
(3) |
| 2014 |
Jan
(187) |
Feb
(139) |
Mar
(99) |
Apr
(173) |
May
(106) |
Jun
(61) |
Jul
(50) |
Aug
(66) |
Sep
(342) |
Oct
(238) |
Nov
(251) |
Dec
(189) |
| 2015 |
Jan
(96) |
Feb
(295) |
Mar
(260) |
Apr
(271) |
May
(358) |
Jun
(531) |
Jul
(311) |
Aug
(231) |
Sep
(267) |
Oct
(219) |
Nov
(452) |
Dec
(390) |
| 2016 |
Jan
(367) |
Feb
(128) |
Mar
(208) |
Apr
(308) |
May
(237) |
Jun
(272) |
Jul
(90) |
Aug
(289) |
Sep
(153) |
Oct
(214) |
Nov
(167) |
Dec
(282) |
| 2017 |
Jan
(194) |
Feb
(173) |
Mar
(267) |
Apr
(102) |
May
(39) |
Jun
(201) |
Jul
(1064) |
Aug
(363) |
Sep
(383) |
Oct
(289) |
Nov
(237) |
Dec
(185) |
| 2018 |
Jan
(175) |
Feb
(198) |
Mar
(489) |
Apr
(222) |
May
(414) |
Jun
(297) |
Jul
(329) |
Aug
(136) |
Sep
(383) |
Oct
(590) |
Nov
(834) |
Dec
(1114) |
| 2019 |
Jan
(425) |
Feb
(177) |
Mar
(319) |
Apr
(515) |
May
(337) |
Jun
(447) |
Jul
(525) |
Aug
(252) |
Sep
(119) |
Oct
(108) |
Nov
(211) |
Dec
(228) |
| 2020 |
Jan
(158) |
Feb
(141) |
Mar
(94) |
Apr
(99) |
May
(545) |
Jun
(470) |
Jul
(211) |
Aug
(142) |
Sep
(181) |
Oct
(128) |
Nov
(219) |
Dec
(213) |
| 2021 |
Jan
(243) |
Feb
(514) |
Mar
(279) |
Apr
(101) |
May
(97) |
Jun
(259) |
Jul
(164) |
Aug
(205) |
Sep
(149) |
Oct
(301) |
Nov
(139) |
Dec
(159) |
| 2022 |
Jan
(116) |
Feb
(70) |
Mar
(63) |
Apr
(46) |
May
(50) |
Jun
(114) |
Jul
(173) |
Aug
(106) |
Sep
(127) |
Oct
(65) |
Nov
(117) |
Dec
(102) |
| 2023 |
Jan
(139) |
Feb
(99) |
Mar
(52) |
Apr
(132) |
May
(238) |
Jun
(75) |
Jul
(91) |
Aug
(25) |
Sep
(36) |
Oct
(64) |
Nov
(45) |
Dec
(91) |
| 2024 |
Jan
(156) |
Feb
(56) |
Mar
(30) |
Apr
(16) |
May
(40) |
Jun
(53) |
Jul
(327) |
Aug
(171) |
Sep
(67) |
Oct
(53) |
Nov
(43) |
Dec
(78) |
| 2025 |
Jan
(112) |
Feb
(27) |
Mar
(46) |
Apr
(49) |
May
(58) |
Jun
(54) |
Jul
(42) |
Aug
(10) |
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Charles S. <g3...@gm...> - 2025-03-06 10:12:45
|
Hi David It might be a useful start to know what PC operating system was in use. Not saying that this could be relevant, but perhaps useful to look for correlations. I have never seen QMAP crash here, on Win10 and Win7 machines, using both WSJT-X and WSJT-X -improved. 73 Charlie DL3WDG On Wed, 5 Mar 2025 at 15:42, David Hilton-Jones via wsjt-devel < wsj...@li...> wrote: > Thanks Nic > > > > Same here – no crashes with RC versions, although others say it has for > them > > > David > > > > *From:* Nic Sears via wsjt-devel [mailto:wsj...@li...] > > *Sent:* 05 March 2025 13:33 > *To:* WSJT software development > *Cc:* Nic Sears > *Subject:* Re: [wsjt-devel] QMAP crash > > > > Also seen 1 crash with 2.7.0 released version. More than last 6 months > running RC versions without a crash. > > > > Nic G3YEG > > > > On 5 Mar 2025 12:37, David Hilton-Jones via wsjt-devel < > wsj...@li...> wrote: > > Since I downloaded the latest WSJT (v2.7.0) release, QMAP has on two > occasions crashed/disappeared off screen. SDRC continues to run. Maybe > just > coincidence and something to do with my set up, but any other similar > reports? > > David, G4YTL > > > > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > > > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > |
|
From: Jim R. A. <jjr...@al...> - 2025-03-05 21:25:17
|
On Wed, Mar 5, 2025 at 8:42 AM Brian Morrison via wsjt-devel < wsj...@li...> wrote: > On Wed, 5 Mar 2025 04:29:24 -0700 > Jim Reisert AD1C via wsjt-devel <wsj...@li...> > wrote: > > > I just tried to update the data files in WSJT-X 2.7.0 in this order: > > > > 1. CTY.DAT > > 2. LoTW > > 3. HamLib > > > > Both #1 and #2 updated without any problems. But when I tried to > > update Hamlib, I received the following error. What does CTY.DAT have > > to do with updating Hamlib? > > > > [image: wsjtx_2025-03-05_04-25-43.png] > > When I clicked on OK above, I received a second error message: > > > > [image: wsjtx_2025-03-05_04-27-09.png] > > I exited the program and tried to update Hamlib again. This time, I > > did not see the CTY.DAT pop-up but did see the "Error loading > > hamlib-4.dll" popup. > > > > Do you have the openssl package installed in Windows? The errors are > for the previous step, so the failure of the LoTW step takes a while to > timeout and show the error. I've never had a problem updating LoTW in the past. I have the Cygwin openssl package(s) installed, but I doubt they would even apply in this case. LoTW did update correctly, before I tried to update Hamlib: Directory of C:\Users\jjrei\AppData\Local\WSJT-X\ 3/05/2025 4:23 5,726,555 lotw-user-activity.csv -- Jim Reisert AD1C, <jjr...@al...>, https://ad1c.us |
|
From: <lm...@im...> - 2025-03-05 19:25:18
|
<div dir='auto'>Might be apparmor or the like on broadcasting decodes, strange as it didn't happened before neither happens with other programs doing the same thing. Well, at least it's something new to look </div><div class="gmail_extra"><br><div class="gmail_quote">El 5 mar 2025 15:59, Nic Sears via wsjt-devel <wsj...@li...> escribió:<br type="attribution" /><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto">The crash looked like old issue of virus checker, Norton, causing issues before white listing all wsjt</div><div><br /><div class="elided-text">On 5 Mar 2025 14:27, David Hilton-Jones via wsjt-devel <wsjt-devel@lists.sourceforge.net> wrote:<br type="attribution" /><blockquote style="margin:0 0 0 0.8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><p><span style="font-size:11pt;font-family:'calibri' , 'sans-serif';color:#1f497d">Thanks Nic</span></p><p><span style="font-size:11pt;font-family:'calibri' , 'sans-serif';color:#1f497d"> </span></p><p><span style="font-size:11pt;font-family:'calibri' , 'sans-serif';color:#1f497d">Same here – no crashes with RC versions, although others say it has for them</span></p><p><span style="font-size:11pt;font-family:'calibri' , 'sans-serif';color:#1f497d"><br />David</span></p><p><span style="font-size:11pt;font-family:'calibri' , 'sans-serif';color:#1f497d"> </span></p><p><b><span style="font-size:10pt;font-family:'tahoma' , 'sans-serif'">From:</span></b><span style="font-size:10pt;font-family:'tahoma' , 'sans-serif'"> Nic Sears via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] <br /><b>Sent:</b> 05 March 2025 13:33<br /><b>To:</b> WSJT software development<br /><b>Cc:</b> Nic Sears<br /><b>Subject:</b> Re: [wsjt-devel] QMAP crash</span></p><p> </p><div><p>Also seen 1 crash with 2.7.0 released version. More than last 6 months running RC versions without a crash.</p><div><p> </p></div><div><p>Nic G3YEG </p></div></div><div><p> </p><div><p>On 5 Mar 2025 12:37, David Hilton-Jones via wsjt-devel <wsjt-devel@lists.sourceforge.net> wrote:</p><p>Since I downloaded the latest WSJT (v2.7.0) release, QMAP has on two <br />occasions crashed/disappeared off screen. SDRC continues to run. Maybe just <br />coincidence and something to do with my set up, but any other similar <br />reports? <br /><br />David, G4YTL <br /><br /><br /><br />_______________________________________________ <br />wsjt-devel mailing list <br />wsjt-devel@lists.sourceforge.net <br />https://lists.sourceforge.net/lists/listinfo/wsjt-devel </p></div><p> </p></div></div></div></blockquote></div><br /></div></blockquote></div><br></div> |
|
From: Brian M. <bd...@fe...> - 2025-03-05 15:42:33
|
On Wed, 5 Mar 2025 04:29:24 -0700 Jim Reisert AD1C via wsjt-devel <wsj...@li...> wrote: > I just tried to update the data files in WSJT-X 2.7.0 in this order: > > 1. CTY.DAT > 2. LoTW > 3. HamLib > > Both #1 and #2 updated without any problems. But when I tried to > update Hamlib, I received the following error. What does CTY.DAT have > to do with updating Hamlib? > > [image: wsjtx_2025-03-05_04-25-43.png] > When I clicked on OK above, I received a second error message: > > [image: wsjtx_2025-03-05_04-27-09.png] > I exited the program and tried to update Hamlib again. This time, I > did not see the CTY.DAT pop-up but did see the "Error loading > hamlib-4.dll" popup. > Do you have the openssl package installed in Windows? The errors are for the previous step, so the failure of the LoTW step takes a while to timeout and show the error. -- Brian G8SEZ |
|
From: Nic S. <nic...@ta...> - 2025-03-05 14:59:55
|
<div dir='auto'>The crash looked like old issue of virus checker, Norton, causing issues before white listing all wsjt</div><div class="gmail_extra"><br><div class="gmail_quote">On 5 Mar 2025 14:27, David Hilton-Jones via wsjt-devel <wsj...@li...> wrote:<br type="attribution" /><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><p><span style="font-size:11pt;font-family:'calibri' , 'sans-serif';color:#1f497d">Thanks Nic</span></p><p><span style="font-size:11pt;font-family:'calibri' , 'sans-serif';color:#1f497d"> </span></p><p><span style="font-size:11pt;font-family:'calibri' , 'sans-serif';color:#1f497d">Same here – no crashes with RC versions, although others say it has for them</span></p><p><span style="font-size:11pt;font-family:'calibri' , 'sans-serif';color:#1f497d"><br />David</span></p><p><span style="font-size:11pt;font-family:'calibri' , 'sans-serif';color:#1f497d"> </span></p><p><b><span style="font-size:10pt;font-family:'tahoma' , 'sans-serif'">From:</span></b><span style="font-size:10pt;font-family:'tahoma' , 'sans-serif'"> Nic Sears via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] <br /><b>Sent:</b> 05 March 2025 13:33<br /><b>To:</b> WSJT software development<br /><b>Cc:</b> Nic Sears<br /><b>Subject:</b> Re: [wsjt-devel] QMAP crash</span></p><p> </p><div><p>Also seen 1 crash with 2.7.0 released version. More than last 6 months running RC versions without a crash.</p><div><p> </p></div><div><p>Nic G3YEG </p></div></div><div><p> </p><div><p>On 5 Mar 2025 12:37, David Hilton-Jones via wsjt-devel <wsjt-devel@lists.sourceforge.net> wrote:</p><p>Since I downloaded the latest WSJT (v2.7.0) release, QMAP has on two <br />occasions crashed/disappeared off screen. SDRC continues to run. Maybe just <br />coincidence and something to do with my set up, but any other similar <br />reports? <br /><br />David, G4YTL <br /><br /><br /><br />_______________________________________________ <br />wsjt-devel mailing list <br />wsjt-devel@lists.sourceforge.net <br />https://lists.sourceforge.net/lists/listinfo/wsjt-devel </p></div><p> </p></div></div></div></blockquote></div><br></div> |
|
From: David Hilton-J. <g4...@ao...> - 2025-03-05 14:38:30
|
Thanks Nic Same here – no crashes with RC versions, although others say it has for them David From: Nic Sears via wsjt-devel [mailto:wsj...@li...] Sent: 05 March 2025 13:33 To: WSJT software development Cc: Nic Sears Subject: Re: [wsjt-devel] QMAP crash Also seen 1 crash with 2.7.0 released version. More than last 6 months running RC versions without a crash. Nic G3YEG On 5 Mar 2025 12:37, David Hilton-Jones via wsjt-devel <wsj...@li...> wrote: Since I downloaded the latest WSJT (v2.7.0) release, QMAP has on two occasions crashed/disappeared off screen. SDRC continues to run. Maybe just coincidence and something to do with my set up, but any other similar reports? David, G4YTL _______________________________________________ wsjt-devel mailing list wsj...@li... https://lists.sourceforge.net/lists/listinfo/wsjt-devel |
|
From: <lm...@im...> - 2025-03-05 14:37:37
|
<div dir='auto'>Mine crash every time it's decoding time leaving a JT9 process orphaned. No idea why this happens, all 2.7 RCs used to work just fine prior a theoretically unrelated system update. It should be something related with the system (arch derivative, so almost always bleeding edge). Core dumps pointed that it seems to happen after a QT notification.<div dir="auto"><br></div><div dir="auto"> Everything compiles ok as usual, either QT5 or 6, but I haven't been able to run cleanly anything either wsjtx, or any of the wsjtx-improved. Oddly enough 2.6 compiles and runs fine, as they do the 2.7 Ubuntu binaries. By now using jtdx there.</div><div dir="auto"><br></div><div dir="auto">Any ideas are welcome, because by now I've run out of them.</div></div><div class="gmail_extra"><br><div class="gmail_quote">El 5 mar 2025 14:32, Nic Sears via wsjt-devel <wsj...@li...> escribió:<br type="attribution" /><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto">Also seen 1 crash with 2.7.0 released version. More than last 6 months running RC versions without a crash.<div dir="auto"><br /></div><div dir="auto">Nic G3YEG </div></div><div><br /><div class="elided-text">On 5 Mar 2025 12:37, David Hilton-Jones via wsjt-devel <wsjt-devel@lists.sourceforge.net> wrote:<br type="attribution" /><blockquote style="margin:0 0 0 0.8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">Since I downloaded the latest WSJT (v2.7.0) release, QMAP has on two <br /> occasions crashed/disappeared off screen. SDRC continues to run. Maybe just <br /> coincidence and something to do with my set up, but any other similar <br /> reports? <br /> <br /> David, G4YTL <br /> <br /> <br /> <br /> _______________________________________________ <br /> wsjt-devel mailing list <br /> wsjt-devel@lists.sourceforge.net <br /> https://lists.sourceforge.net/lists/listinfo/wsjt-devel <br /> </p> </blockquote></div><br /></div></blockquote></div><br></div> |
|
From: Nic S. <nic...@ta...> - 2025-03-05 13:51:22
|
<div dir='auto'>Also seen 1 crash with 2.7.0 released version. More than last 6 months running RC versions without a crash.<div dir="auto"><br></div><div dir="auto">Nic G3YEG </div></div><div class="gmail_extra"><br><div class="gmail_quote">On 5 Mar 2025 12:37, David Hilton-Jones via wsjt-devel <wsj...@li...> wrote:<br type="attribution" /><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">Since I downloaded the latest WSJT (v2.7.0) release, QMAP has on two <br> occasions crashed/disappeared off screen. SDRC continues to run. Maybe just <br> coincidence and something to do with my set up, but any other similar <br> reports? <br> <br> David, G4YTL <br> <br> <br> <br> _______________________________________________ <br> wsjt-devel mailing list <br> wsj...@li... <br> https://lists.sourceforge.net/lists/listinfo/wsjt-devel <br> </p> </blockquote></div><br></div> |
|
From: David Hilton-J. <g4...@ao...> - 2025-03-05 13:08:09
|
Since I downloaded the latest WSJT (v2.7.0) release, QMAP has on two occasions crashed/disappeared off screen. SDRC continues to run. Maybe just coincidence and something to do with my set up, but any other similar reports? David, G4YTL |
|
From: Jim R. A. <jjr...@al...> - 2025-03-05 11:29:59
|
I just tried to update the data files in WSJT-X 2.7.0 in this order: 1. CTY.DAT 2. LoTW 3. HamLib Both #1 and #2 updated without any problems. But when I tried to update Hamlib, I received the following error. What does CTY.DAT have to do with updating Hamlib? [image: wsjtx_2025-03-05_04-25-43.png] When I clicked on OK above, I received a second error message: [image: wsjtx_2025-03-05_04-27-09.png] I exited the program and tried to update Hamlib again. This time, I did not see the CTY.DAT pop-up but did see the "Error loading hamlib-4.dll" popup. -- Jim Reisert AD1C, <jjr...@al...>, https://ad1c.us |
|
From: Uwe, D. <dg...@gm...> - 2025-03-05 08:54:44
|
Hi Andy, Don't give up hope, hi ... The next version of WSJT-X Improved will be able to log and post correct frequencies even if they have been changed via the VFO knob. The planned release date is March, 14. 73 de DG2YCB, Uwe ________________________________________ German Amateur Radio Station DG2YCB Dr. Uwe Risse eMail: dg...@gm... Info: www.qrz.com/db/DG2YCB Am 05.03.2025 um 01:05 schrieb Andy Durbin via wsjt-devel: > I gave up any hope of this being fixed because that's how the > developers want it to work but please understand the limitations. |
|
From: Andy D. <a.d...@ms...> - 2025-03-05 00:20:59
|
"I don't have to ever touch the radio dial, Andy. If SpotCollector shows a spot, I double click on it and it moves me to the mode and exact freq for the qso. (DXLabs Spot Collector). It's true for cw/ssb/digital." You don't appear to understand that, if you do this and the frequency of the spot you clicked does not match a stored WSJT-X frequency, the WSJT-X will spot the wrong frequency and record the wrong frequency in the all.txt file. You rig tunes the spot collector frequency, the frequency readout of WSJT-X reports the rig frequency, but WSJ-X may report a completely different frequency! I gave up any hope of this being fixed because that's how the developers want it to work but please understand the limitations. Andy, k3wyc |
|
From: Hasan N. <hba...@gm...> - 2025-03-04 17:27:14
|
I don't have to ever touch the radio dial, Andy. If SpotCollector shows a spot, I double click on it and it moves me to the mode and exact freq for the qso. (DXLabs Spot Collector). It's true for cw/ssb/digital. DXLabs Suite: (they all talk to each other) DXCommander (rig control) DX SpotCollector (spotting in/out) PropView: instant Prop Prediction to dx station DXView: summary details of DX station DXKeeper (logger) I do not use PSKr for anything but band activity, I don't have to type in any spots, they are way behind other spotting networks. (generally) 73, N0AN Hasan On Mon, Mar 3, 2025 at 7:01 PM Andy Durbin via wsjt-devel < wsj...@li...> wrote: > "Just remember: don't touch the radio vfo! If you make all changes in > frequency thru WSJT-X alone, then you will never have a problem." > > give up the ability to click tune DX spots - No thanks > > give up the ability to click on HDSDR activity - No thanks > > I want to spot the frequency to which I decided to set my transceiver no > matter how I decided to set that frequency. That is why I include the > dial frequency in my spots. It is the only number that can be trusted. My > PSKReporter spots may not be reliable - Don't use them. > > Andy, k3wyc > > > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > |
|
From: Fred C. <fre...@gm...> - 2025-03-04 14:14:27
|
Hi Andy, I don't want to beat a dead horse. First of all I'm not a developer so I don't know how difficult it would be to retrieve a radio's dial frequency before reporting. It seems somewhat involved and not how the program was designed. What I have come to realize is that typing a QSY frequency into WSJT's pull down box isn't really a big deal. To be honest, I never knew that feature existed. Once again thank you to everyone who helped me get a clear understanding of why I was spotting the wrong frequency. Spots are back on and I'm being more observant when I line up my rig and QSY. 73, Fred WX1S I would like to thank everyone for helping me understand why my spots were inaccurate. On 3/3/2025 5:22 PM, Andy Durbin via wsjt-devel wrote: > "Just remember: don't touch the radio vfo! If you make all changes in > frequency thru WSJT-X alone, then you will never have a problem." > > give up the ability to click tune DX spots - No thanks > > give up the ability to click on HDSDR activity - No thanks > > I want to spot the frequency to which I decided to set my transceiver > no matter how I decided to set that frequency. That is why I include > the dial frequency in my spots. It is the only number that can be > trusted. My PSKReporter spots may not be reliable - Don't use them. > > Andy, k3wyc > > > > > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel |
|
From: Andy D. <a.d...@ms...> - 2025-03-04 00:58:14
|
"Just remember: don't touch the radio vfo! If you make all changes in frequency thru WSJT-X alone, then you will never have a problem." give up the ability to click tune DX spots - No thanks give up the ability to click on HDSDR activity - No thanks I want to spot the frequency to which I decided to set my transceiver no matter how I decided to set that frequency. That is why I include the dial frequency in my spots. It is the only number that can be trusted. My PSKReporter spots may not be reliable - Don't use them. Andy, k3wyc |
|
From: Hasan N. <hba...@gm...> - 2025-03-03 12:51:58
|
The cure for this is simple: don't touch the radio dial. Just make all frequency changes with WSJT-X. You can do this by (as Joe pointed out) 071K or in the improved version 071 (without the K if it the feature is enabled). Just remember: don't touch the radio vfo! If you make all changes in frequency thru WSJT-X alone, then you will never have a problem. How hard is it to type 3 or 4 letters in the freq drop down box? I would think that turning off reporting because you can't touch the radio dial, when it is a simple matter to change freq with the drop down box, is self-defeating. 73, N0AN Hasan On Mon, Mar 3, 2025 at 6:43 AM Fred Coelho via wsjt-devel < wsj...@li...> wrote: > Hi guys, > > Thank you for the clarification. I now understand that I must place a > non-standard frequency such as 14.091 in the drop down list in order to > post the correct frequency. If I decide to re-enable spots I won't use the > radio knob. > > 73, > > Fred WX1S > > > > On 3/3/2025 3:14 AM, Reino Talarmo via wsjt-devel wrote: > > Scott, thanks a lot for spotting this for me. > > > > Now it is very clear to me, and I want to share that information with all > of you (again): > > > > “As things are presently coded, retuning your rig with front panel > controls (the "big knob") does NOT change the nominal frequency that you > have selected from the drop-down list. That's the frequency that will be > written to ALL.TXT and posted to PSK Reporter, etc. > > > > One reason this can make sense is that you want to be on 14.074 MHz, say > > -- or perhaps on 1296.065 MHz, for EME -- but you know that on that band > your dial calibration is off by -220 Hz. So, you select 14.074 in the > drop-down list and then tweak the dial by the necessary +220 Hz. > > Everything will then be recorded and posted correctly. > > > > If you want to be on 14.091 and have things recorded and posted as 14.091, > type "14.091" into the drop-down control. Better still, put > > 14.091 into your frequencies list. If you're already on 20 meters, say > 14.074, you can type "91k" (for kHz) into the drop-down list. > > > > -- 73, Joe, K1JT” > > > > I see that it would be a challenge to make a fail-safe code that allows > VFO turning in all cases to set the base frequency. Perhaps a new > confirmation window would be needed stating e.g. “Do you want to use the > new indicated frequency as the base frequency?” each time you turn VFO. I > don’t want to start that discussion again unless someone it willing to code > it and “all” frequency control situations are clearly defined on the user > point of view. > > To me the typing of the frequency into the drop-down control for a > temporary change or an additional entry to the frequency list for a more > permanent selection option is good enough. > > > > 73, Reino OH3mA > > > > *From:* Scott Armstrong via wsjt-devel <wsj...@li...> > <wsj...@li...> > *Sent:* Monday, March 3, 2025 2:38 AM > *To:* WSJT software development <wsj...@li...> > <wsj...@li...> > *Cc:* Scott Armstrong <aa5...@gm...> <aa5...@gm...> > *Subject:* Re: [wsjt-devel] Frequency Reporting Anomaly WSJT and FT8/FT4 > > > > Reino, > > Took a bit to find this one... > > I think the thread you are referring to is this one "ALL.TXT RX freq is > not RX DIAL freq" from July 2024. > > > 73, > Scott AA5AM > > > > On Sun, Mar 2, 2025 at 4:06 PM Reino Talarmo via wsjt-devel < > wsj...@li...> wrote: > > Fred, > > From some earlier discussion on this behavior, I got feeling that the > program is designed in that manner. The to be reported frequency needs to > be set by wsjt-x not by VFO. I am not familiar enough to tell the reason > for that behavior, but a proposed change was rejected at that time. I am > not sure whether the discussion was on this mail-list, but most probably. > > > > 73, Reino OH3mA > > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > > > > _______________________________________________ > wsjt-devel mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/wsjt-devel > > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > |
|
From: Fred C. <fre...@gm...> - 2025-03-03 12:41:21
|
Hi guys, Thank you for the clarification. I now understand that I must place a non-standard frequency such as 14.091 in the drop down list in order to post the correct frequency. If I decide to re-enable spots I won't use the radio knob. 73, Fred WX1S On 3/3/2025 3:14 AM, Reino Talarmo via wsjt-devel wrote: > > Scott, thanks a lot for spotting this for me. > > Now it is very clear to me, and I want to share that information with > all of you (again): > > “As things are presently coded, retuning your rig with front panel > controls (the "big knob") does NOT change the nominal frequency that > you have selected from the drop-down list. That's the frequency that > will be written to ALL.TXT and posted to PSK Reporter, etc. > > One reason this can make sense is that you want to be on 14.074 MHz, say > > -- or perhaps on 1296.065 MHz, for EME -- but you know that on that > band your dial calibration is off by -220 Hz. So, you select 14.074 > in the drop-down list and then tweak the dial by the necessary +220 Hz. > > Everything will then be recorded and posted correctly. > > If you want to be on 14.091 and have things recorded and posted as > 14.091, type "14.091" into the drop-down control. Better still, put > > 14.091 into your frequencies list. If you're already on 20 meters, > say 14.074, you can type "91k" (for kHz) into the drop-down list. > > -- 73, Joe, K1JT” > > I see that it would be a challenge to make a fail-safe code that > allows VFO turning in all cases to set the base frequency. Perhaps a > new confirmation window would be needed stating e.g. “Do you want to > use the new indicated frequency as the base frequency?” each time you > turn VFO. I don’t want to start that discussion again unless someone > it willing to code it and “all” frequency control situations are > clearly defined on the user point of view. > > To me the typing of the frequency into the drop-down control for a > temporary change or an additional entry to the frequency list for a > more permanent selection option is good enough. > > 73, Reino OH3mA > > *From:*Scott Armstrong via wsjt-devel <wsj...@li...> > *Sent:* Monday, March 3, 2025 2:38 AM > *To:* WSJT software development <wsj...@li...> > *Cc:* Scott Armstrong <aa5...@gm...> > *Subject:* Re: [wsjt-devel] Frequency Reporting Anomaly WSJT and FT8/FT4 > > Reino, > > Took a bit to find this one... > > I think the thread you are referring to is this one "ALL.TXT RX freq > is not RX DIAL freq" from July 2024. > > > 73, > Scott AA5AM > > On Sun, Mar 2, 2025 at 4:06 PM Reino Talarmo via wsjt-devel > <wsj...@li...> wrote: > > Fred, > > From some earlier discussion on this behavior, I got feeling that > the program is designed in that manner. The to be reported > frequency needs to be set by wsjt-x not by VFO. I am not familiar > enough to tell the reason for that behavior, but a proposed change > was rejected at that time. I am not sure whether the discussion > was on this mail-list, but most probably. > > 73, Reino OH3mA > > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > > > > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel |
|
From: Andy D. <a.d...@ms...> - 2025-03-03 12:29:12
|
This was documented in detail in the thread "ALL.TXT RX freq is not RX DIAL freq" July 2024. https://tinyurl.com/ynajnra7 Read it all to find out how the developers responded. Andy, k3wyc |
|
From: Reino T. <rei...@ko...> - 2025-03-03 08:15:06
|
Scott, thanks a lot for spotting this for me.
Now it is very clear to me, and I want to share that information with all of you (again):
“As things are presently coded, retuning your rig with front panel controls (the "big knob") does NOT change the nominal frequency that you have selected from the drop-down list. That's the frequency that will be written to ALL.TXT and posted to PSK Reporter, etc.
One reason this can make sense is that you want to be on 14.074 MHz, say
-- or perhaps on 1296.065 MHz, for EME -- but you know that on that band your dial calibration is off by -220 Hz. So, you select 14.074 in the drop-down list and then tweak the dial by the necessary +220 Hz.
Everything will then be recorded and posted correctly.
If you want to be on 14.091 and have things recorded and posted as 14.091, type "14.091" into the drop-down control. Better still, put
14.091 into your frequencies list. If you're already on 20 meters, say 14.074, you can type "91k" (for kHz) into the drop-down list.
-- 73, Joe, K1JT”
I see that it would be a challenge to make a fail-safe code that allows VFO turning in all cases to set the base frequency. Perhaps a new confirmation window would be needed stating e.g. “Do you want to use the new indicated frequency as the base frequency?” each time you turn VFO. I don’t want to start that discussion again unless someone it willing to code it and “all” frequency control situations are clearly defined on the user point of view.
To me the typing of the frequency into the drop-down control for a temporary change or an additional entry to the frequency list for a more permanent selection option is good enough.
73, Reino OH3mA
From: Scott Armstrong via wsjt-devel <wsj...@li...>
Sent: Monday, March 3, 2025 2:38 AM
To: WSJT software development <wsj...@li...>
Cc: Scott Armstrong <aa5...@gm...>
Subject: Re: [wsjt-devel] Frequency Reporting Anomaly WSJT and FT8/FT4
Reino,
Took a bit to find this one...
I think the thread you are referring to is this one "ALL.TXT RX freq is not RX DIAL freq" from July 2024.
73,
Scott AA5AM
On Sun, Mar 2, 2025 at 4:06 PM Reino Talarmo via wsjt-devel <wsj...@li... <mailto:wsj...@li...> > wrote:
Fred,
>From some earlier discussion on this behavior, I got feeling that the program is designed in that manner. The to be reported frequency needs to be set by wsjt-x not by VFO. I am not familiar enough to tell the reason for that behavior, but a proposed change was rejected at that time. I am not sure whether the discussion was on this mail-list, but most probably.
73, Reino OH3mA
_______________________________________________
wsjt-devel mailing list
wsj...@li... <mailto:wsj...@li...>
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
|
|
From: Reino T. <rei...@ko...> - 2025-03-03 07:11:18
|
Hi Fred, I got impression that in your setup wsjt-x does not follow VFO knob turning via DXLab Commander. In that situation wsjt-x cannot know the frequency even, if it could report it. I need to admit that I am not using it and cannot help on that issue. I still assume that it is possible to set also that system to follow VFO frequency back to wsjt-x. In any case wsjt-x can only report what it defines to be the base frequency i.e., is set by it. Now I am not sure what is reported, when you type the frequency into the drop-down field. I should test that myself, hi. 73, Reino OH3mA |
|
From: Laurie, V. <_vk...@vk...> - 2025-03-03 00:42:40
|
On 03/03/2025 10:58 am, Jim Preston via wsjt-devel wrote: > The spots from JTAlert to HamSpots are correct. The ones coming from > PSK Reporter to HamSpots are incorrect I have seen spots on HamSpots for identical decodes from the same spotter on 2 bands. The spots originating from JTAlert are correct while the wrong band spots are all originating from PSKReporter. Either something is broken in Wsjtx with respect to its PSKReporter spotting or something screwy is happening on PSKReporter (perhaps something to do with its bad spot algorithm). de Laurie VK3AMA (JTAlert author & HamSpots owner) |
|
From: Scott A. <aa5...@gm...> - 2025-03-03 00:38:07
|
Reino, Took a bit to find this one... I think the thread you are referring to is this one "ALL.TXT RX freq is not RX DIAL freq" from July 2024. 73, Scott AA5AM On Sun, Mar 2, 2025 at 4:06 PM Reino Talarmo via wsjt-devel < wsj...@li...> wrote: > Fred, > > From some earlier discussion on this behavior, I got feeling that the > program is designed in that manner. The to be reported frequency needs to > be set by wsjt-x not by VFO. I am not familiar enough to tell the reason > for that behavior, but a proposed change was rejected at that time. I am > not sure whether the discussion was on this mail-list, but most probably. > > > > 73, Reino OH3mA > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > |
|
From: Jim P. <jpr...@co...> - 2025-03-03 00:18:47
|
On 3/2/2025 2:59 PM, Laurie, VK3AMA via wsjt-devel wrote: > On 03/03/2025 9:17 am, Fred Coelho via wsjt-devel wrote: >> I'll turn my reporting off rather than send bad information to >> HamSpots/PSK Reporter. > > FYI, your HamSpots spots all originate from PSKReporter. Something is > wrong in the Wsjtx -> PSKReporter spotting. > > de Laurie VK3AMA > (HamSpots owner) Laurie, I just checked, and I see the same thing. My rig is a Yaesu FTDX 101MP. The rig is currently tuned to 18.095, but the spots showing on PSK Reporter are above 18.100 (my rx doesn't have that wide a bandwidth). The spots from JTAlert to HamSpots are correct. The ones coming from PSK Reporter to HamSpots are incorrect. I agree that it involves WSJT-X sending incorrect data. 73, Jim N6VH |
|
From: Fred C. <fre...@gm...> - 2025-03-02 23:23:54
|
Hi Scott, I tried turning off CIV Transsceive and it didn't help. I do run it on because my amp requires that signal to track my rig. For the time being I'll turn off reporting. I really don't want to spot the wrong frequency if I turn the dial. Thanks for the feedback. 73, Fred On 3/2/2025 5:41 PM, Scott Armstrong via wsjt-devel wrote: > Kevin, Fred, > > Found the posts in the archive. The solution/work around was to turn > CI-V Transceive OFF. > In my case CI-V Transceive has always been off. Don't know what Fred > has set on his 7610. > > I do see the lag in the frequency update on WSJT when tuning the radio > VFO but it always catches up and displays the correct frequency. > > What Fred and I are seeing appears to be a different issue. > > This is my take on what is happening from a 50k foot user's > perspective. Someone that can dig into the code may have a different > take on it > > The radio is tuned to whatever frequency. > Launch WSJT-X. WSJT-X initializes and reads the radio frequency.The > frequency display on the main screen is initialized and the correct > frequency is displayed. Another register/variable within the code is > also initialized with the same frequency. > > The user manually tunes the radio dial. > The frequency tracks correctly on the main screen of WSJT. > The mystery register/variable appears to be static and only gets > initialized at startup. This value is what gets used in logging the > decodes to the ALL.txt file and sent to external apps and servers via > the UPD and TCP/IP packets. > > Logged contacts have the correct frequency which equals the > displayed frequency on WSJT+ DF. > > > One additional quirk I am seeing is if the radio is tuned to a normal > WSJT FT8 frequency. WSJT is launched all is good as expected. > The VFO on the radio can be changed to another frequency and > everything appears to track correctly. All.txt and spots on PSKR and > Hamspots have the new frequency. If the VFO is tuned again, the > frequency is not updated and the All.txt and spotting apps still have > the old frequency. > > > Shouldn't be too difficult for someone that is familiar with the code > to track the frequency variable that is used for the All.txt file, UDP > and TCP/IP packets and see what it is/is not doing when initialized > and when the VFO is tuned. > > > 73, > Scott AA5AM > > > > > > > On Sun, Mar 2, 2025 at 2:26 PM Kevin McQuiggin via wsjt-devel > <wsj...@li...> wrote: > > There was a frequency tracking issue with Icom rigs a couple of > years ago where CAT could not keep up with manual tuning; hence > the WSJT-X frequency and that of the rig could get out of sync. > This sounds awfully similar. > > I don’t recall the specific fix, except that it was resolved > through adjustment of a CAT interface setting in the (sometimes > confusing) extensive menu system of my rig (an IC-9700). The > setting was non-intuitive but others with Hamlib experience were > able to help me resolve it. > > On the positive side, if you search the archives for somethign > along of line of "Icom, CAT, tracking, error” then the thread will > turn up. > > Hope this helps! > > 73, > > Kevin VE7ZD/KN7Q > > >> On Mar 2, 2025, at 10:11 AM, Laurie, VK3AMA via wsjt-devel >> <wsj...@li...> wrote: >> >> >> >> On 03/03/2025 4:56 am, Fred Coelho via wsjt-devel wrote: >>> >>> 1.Set Radio to 14.000 >>> >>> 2.Launch WSJT >>> >>> 3.Turn the radio dial to a standard FT8 frequency. >>> >>> 4.Observe that spots in HamSpots are not correct.You will also >>> see that your frequency is not correct on the PSK reporter map. >>> >> >> If the Wsjtx VFO frequency does not change following the radio >> than this is expected behavior. There is a problem with your CAT >> connection IMO. >> >> de Laurie VK3AMA >> (HamSpots owner) >> _______________________________________________ >> wsjt-devel mailing list >> wsj...@li... >> https://lists.sourceforge.net/lists/listinfo/wsjt-devel > > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > > > > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel |
|
From: Laurie, V. <_vk...@vk...> - 2025-03-02 22:59:27
|
On 03/03/2025 9:17 am, Fred Coelho via wsjt-devel wrote: > I'll turn my reporting off rather than send bad information to > HamSpots/PSK Reporter. FYI, your HamSpots spots all originate from PSKReporter. Something is wrong in the Wsjtx -> PSKReporter spotting. de Laurie VK3AMA (HamSpots owner) |
68 messages has been excluded from this view by a project administrator.
