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: Scott A. <aa5...@gm...> - 2025-03-02 22:42:14
|
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 > |
|
From: Fred C. <fre...@gm...> - 2025-03-02 22:17:50
|
Hi Reino, I'll turn my reporting off rather than send bad information to HamSpots/PSK Reporter. Thanks for all the feedback. 73, Fred WX1S On 3/2/2025 5:02 PM, Reino Talarmo via wsjt-devel 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: Fred C. <fre...@gm...> - 2025-03-02 22:15:08
|
Hi Lauri, The WSJTx CAT frequency display does change and track when I turn the dial. The only issue I have is that Spots show up with the wrong frequency when I report. I run CAT through DXLab Commander and local spots show up with the correct frequency in Spot Collector when I turn the dial. 73, Fred WX1S On 3/2/2025 1:11 PM, Laurie, VK3AMA via wsjt-devel 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 |
|
From: Fred C. <fre...@gm...> - 2025-03-02 22:03:46
|
Thanks Kevin, It does track fine for local spots in SpotCollector. I'll take a look at the archives and see if I can fine a solution. For the time being I just need to remember to line the radio up first before launching WSJT on a non-standard frequency. Or perhaps putting DXpedition frequencies in the drop down window. Thanks again es 73, Fred WX1S On 3/2/2025 3:06 PM, Kevin McQuiggin via wsjt-devel 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 |
|
From: Reino T. <rei...@ko...> - 2025-03-02 22:02:38
|
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 |
|
From: Kevin M. <mcq...@sf...> - 2025-03-02 20:21:37
|
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 |
|
From: Scott A. <aa5...@gm...> - 2025-03-02 20:00:19
|
I am observing the same behavior. Running 2.7.0 GA Rig Icom IC-756ProII [image: image.png] and Hamlib version [image: image.png] In addition to PSKReporter,, HamSpots, etc... reporting the incorrect frequency I also see the incorrect frequency being logged in the ALL.txt file. Something within WSJT-X is not updating when the frequency changes via the dial even though the frequency is being displayed correctly on the WSJT screen, -Scott AA5AM On Sun, Mar 2, 2025 at 1:24 PM 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 > |
|
From: Laurie, V. <_vk...@vk...> - 2025-03-02 19:20:19
|
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) |
|
From: Fred C. <fre...@gm...> - 2025-03-02 17:57:02
|
Frequency Reporting Anomaly WSJT and FT8/FT4 Launch PSK reporter or HamSpots. Line up your radio to a non-standard FT8 frequency. Start WSJT and turn the radio dial to one of WSJT’s standard FT8 frequencies.Do not use the pull down menu to change your radio frequency, use the dial. Observe the frequency error of your spots.HamSpots or PSK Reporter will display the frequency you originally started on rather than the current dial frequency. How to reproduce: 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. 5.This anomaly was also observed while running FT4. 6.Your dial frequency will display properly in DXLab Spot Collector. Rig IC7610 Serial Interface DXLab Commander WSJT Version 2.7.0 rc8 e183d4 Reporting Enabled 73, Fred WX1S |
|
From: Rick E. <rel...@tw...> - 2025-02-27 23:45:16
|
Ok That makes sense then.. I passed this on to the user.. 73 Rick N2AMG On 2/27/2025 1:57 PM, Joseph Taylor via wsjt-devel wrote: > Hi Rick, > > Why should you be surprised? The calls you list do not have the format > specified in the WSJT-X User Guide for a standard callsign. > https://wsjt.sourceforge.io/wsjtx-doc/wsjtx-main-2.7.0.html#PROTOCOLS > > "A standard amateur callsign consists of a one- or two-character > prefix, at least one of which must be a letter, followed by a digit > and a suffix of one to three letters." > > -- 73, Joe, K1JT > > ------------------------------------------------------------------------ > *From:* Rick Ellison via wsjt-devel <wsj...@li...> > *Sent:* Thursday, February 27, 2025 12:25 PM > *To:* wsj...@li... <wsj...@li...> > *Cc:* Rick Ellison <rel...@tw...> > *Subject:* [wsjt-devel] Message Type 2 Output. > > > A user of N1MM brought something to my attention and after confirming > it today I see the same thing as he does. > > None of the following calls AN45AL, AN45CA, AN45CO, AN45GR, AN45HU, > AN45JA, AN45MA, AN45SE > > are sent out via a message type 2. I have trapped all of the calls > coming out of that message but when one of those calls are encountered > in the WSJTX Band activity window that call is not sent out. > > > 73 Rick N2AMG > > -- > This email has been checked for viruses by Avast antivirus software. > www.avast.com <http://www.avast.com> > > > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > <https://lists.sourceforge.net/lists/listinfo/wsjt-devel> > > > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel |
|
From: Joseph T. <jo...@Pr...> - 2025-02-27 22:28:16
|
Hi Rick, Why should you be surprised? The calls you list do not have the format specified in the WSJT-X User Guide for a standard callsign. https://wsjt.sourceforge.io/wsjtx-doc/wsjtx-main-2.7.0.html#PROTOCOLS "A standard amateur callsign consists of a one- or two-character prefix, at least one of which must be a letter, followed by a digit and a suffix of one to three letters." -- 73, Joe, K1JT ________________________________ From: Rick Ellison via wsjt-devel <wsj...@li...> Sent: Thursday, February 27, 2025 12:25 PM To: wsj...@li... <wsj...@li...> Cc: Rick Ellison <rel...@tw...> Subject: [wsjt-devel] Message Type 2 Output. A user of N1MM brought something to my attention and after confirming it today I see the same thing as he does. None of the following calls AN45AL, AN45CA, AN45CO, AN45GR, AN45HU, AN45JA, AN45MA, AN45SE are sent out via a message type 2. I have trapped all of the calls coming out of that message but when one of those calls are encountered in the WSJTX Band activity window that call is not sent out. 73 Rick N2AMG -- This email has been checked for viruses by Avast antivirus software. www.avast.com<http://www.avast.com> _______________________________________________ wsjt-devel mailing list wsj...@li... https://lists.sourceforge.net/lists/listinfo/wsjt-devel |
|
From: Sam W. <w2...@ao...> - 2025-02-27 18:24:17
|
Hi Rick,
Could it be that AN45 does not have a valid DX entity code ?
>From QRZ :
Page 1 of 1, of 9 matches for: AN45*
| AN45CE | UREM URE MALAGA Malaga |
| AN45JA | DIPLOMA DIA DE ANDALUCIA "JAEN" ANDALUCIA |
| AN45MA | DIPLOMA DIA DE ANDALUCIA ANDALUCIA |
| AN45GR | DIPLOMA DIA DE ANDALUCIA "GRANADA" ANDALUCIA |
| AN45SE | DIPLOMA DIA DE ANDALUCIA "SEVILLA" ANDALUCIA |
| AN45AL | DIPLOMA DIA DE ANDALUCIA "ALMERIA" ANDALUCIA |
| AN45HU | DIPLOMA DIA DE ANDALUCIA "HUELVA" ANDALUCIA |
| AN45CO | DIPLOMA DIA DE ANDALUCIA "CORDOBA" ANDALUCIA |
| AN45CA | DIPLOMA DIA DE ANDALUCIA "CADIZ" ANDALUCIA |
73,
Sam W2JDB
On Thursday, February 27, 2025 at 12:45:23 PM EST, Rick Ellison via wsjt-devel <wsj...@li...> wrote:
A user of N1MM brought something to my attention and after confirming
it today I see the same thing as he does.
None of the following calls AN45AL, AN45CA, AN45CO, AN45GR, AN45HU,
AN45JA, AN45MA, AN45SE
are sent out via a message type 2. I have trapped all of the calls
coming out of that message but when one of those calls are encountered
in the WSJTX Band activity window that call is not sent out.
73 Rick N2AMG
--
This email has been checked for viruses by Avast antivirus software.
www.avast.com
_______________________________________________
wsjt-devel mailing list
wsj...@li...
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
|
|
From: Rick E. <rel...@tw...> - 2025-02-27 17:38:11
|
A user of N1MM brought something to my attention and after confirming it today I see the same thing as he does. None of the following calls AN45AL, AN45CA, AN45CO, AN45GR, AN45HU, AN45JA, AN45MA, AN45SE are sent out via a message type 2. I have trapped all of the calls coming out of that message but when one of those calls are encountered in the WSJTX Band activity window that call is not sent out. 73 Rick N2AMG -- This email has been checked for viruses by Avast antivirus software. www.avast.com |
|
From: Andy D. <a.d...@ms...> - 2025-02-21 22:06:08
|
"In the 2.7 releases the rig moves to the correct frequency but the SteppIR does not. " How is your SteppIR controller connected so that rig frequency is available to it? There are many different ways of configuring this interface and it doubt it would be possible to investigate your problem without a lot more detail. In my station, when using WSJT-X, PstRotatorAZ receives rig frequency from DXLab Commander and PstRotatorAZ sends the frequency to my SDA 100 SteppIR controller. Both the SDA 100 and PstRotatorAz can be set to control how much frequency change is needed for a new frequency to cause a change in SteppIR element length. I have been using "v 2.7.1 devel 240721 improved PLUS" but I downloaded, installed, and ran the official 2.7.0. My SteppIR tracks just the same as it did before. Not surprising since WSJT-X has no interface to my SteppIR controller. Andy, k3wyc |
|
From: Joseph T. <jo...@Pr...> - 2025-02-21 03:17:11
|
Please read about nonstandard and compound callsigns in the WSJT-X User Guide, Section 7.5: https://wsjt.sourceforge.io/wsjtx-doc/wsjtx-main-2.7.0.html#COMP-CALL In particular, note this sentence: "WSJT-X 2.7 offers no support for two nonstandard callsigns to work each other." -- 73, Joe, K1JT WSJT-X User Guide<https://wsjt.sourceforge.io/wsjtx-doc/wsjtx-main-2.7.0.html#COMP-CALL> WSJT-X is a computer program designed to facilitate basic amateur radio communication using very weak signals. The first four letters in the program name stand for “Weak Signal communication by K1JT,” while the suffix “-X” indicates that WSJT-X started as an extended branch of an earlier program, WSJT, first released in 2001.Bill Somerville, G4WJS, Steve Franke, K9AN, and Nico Palermo ... wsjt.sourceforge.io ________________________________ From: Tom Hauer via wsjt-devel <wsj...@li...> Sent: Thursday, February 20, 2025 7:40 PM To: WSJT software development <wsj...@li...> Cc: Tom Hauer <rdr...@gm...> Subject: [wsjt-devel] Issue with LONG Call Signs V2.7.0 I am using the call sign V4/K0YA while in St. Kitts. I attempted a QSO with FJ/DK6AS. WSJT-X froze on that transaction with both call signs in the same message. I couldn't switch to another call sign, or abort the call. It resolved when DK6AS showed without the FJ prefix so I could complete the contact that way. I was able to log it correctly but am wondering if that was just too many characters in one line? Hung me up for a minute but was able to recover. Tom Hauer, K0YA ARES Emergency Coordinator Blanco, Burnet, Llano and Mason Counties ARRL ARES District 8, STX Section TDEM RACES District 12-053 319 551-9788 rdr...@gm...<mailto:rdr...@gm...> PO Box 1522 (mailing ADR) 11700 E FM 1431 R37 Marble Falls, Tx 78654 EM00wn Latitude: 30.568805 Longitude: -98.140287 |
|
From: Tom H. <rdr...@gm...> - 2025-02-21 00:41:10
|
I am using the call sign V4/K0YA while in St. Kitts. I attempted a QSO with FJ/DK6AS. WSJT-X froze on that transaction with both call signs in the same message. I couldn't switch to another call sign, or abort the call. It resolved when DK6AS showed without the FJ prefix so I could complete the contact that way. I was able to log it correctly but am wondering if that was just too many characters in one line? Hung me up for a minute but was able to recover. Tom Hauer, K0YA ARES Emergency Coordinator Blanco, Burnet, Llano and Mason Counties ARRL ARES District 8, STX Section TDEM RACES District 12-053 319 551-9788 rdr...@gm... PO Box 1522 (mailing ADR) 11700 E FM 1431 R37 Marble Falls, Tx 78654 EM00wn Latitude: 30.568805 Longitude: -98.140287 |
|
From: Lance C. W. <w7...@bi...> - 2025-02-17 23:39:16
|
TNX Joe et al! I was quite successful during the recent 6m EME DXpedition to ZD9, making 173 EME contacts, but I had the luxury there of being able to monitor a chat page while I was on the air. So I could see which stations reported copying me at a particular time. I am planning another 6m EME DXpedition and where I will not have access to real-time internet. So, you know what I am going to ask ;-) Is there any way with Q65-60A Q65 Pileup that there could be a bit that could signify that a caller was copying (or receiving well enough to decode if I were replying to them) during their previous receiving period? It would really be a HUGE ADVANTAGE to be able to identify callers that had the capability of a quick reciprocal contact. Just had to ask! MNI TNX and VY 73, Lance On 2/17/2025 13:02:17, Joseph Taylor via wsjt-devel wrote: > > The WSJT Development Team is pleased to announce the WSJT-X 2.7.0 General > Availability (GA) release. This is the first GA release since version 2.6.1, two > years ago. Major enhancements include a new companion program called QMAP, new > Special Operating Activities called “Q65 Pileup” and “SuperFox”, and a new “Message > System” feature designed for sending requests to change to another band or mode. > More details can be found in the Release Notes here: > _https://wsjt.sourceforge.io/Release_Notes.txt > <https://wsjt.sourceforge.io/Release_Notes.txt>_. > > Direct links for downloading pre-built installation packages for Windows, Linux, > and macOS can be found on the WSJT-X web page: > _https://wsjt.sourceforge.io/wsjtx.html <https://wsjt.sourceforge.io/wsjtx.html>_. > For those who like to compile from source, a complete source-code tarball is > available there as well. > > Please note: A few changes and updates to the WSJT-X User Guide are still to be > completed. > > If you will be translating the User Guide to another language, please wait for an > announcement that the updated English guide is ready and available online. > > WSJT-X is licensed under the terms of Version 3 of the GNU General Public License > (GPL). Development of this software is a cooperative project to which many amateur > radio operators have contributed. If you use our code, please have the courtesy to > let us know about it. > > The authors and Copyright holders of WSJT-X request that derivative works should > not publish programs based on features in WSJT-X before those features are made > available in a General Availability (GA) release of WSJT-X. We will cease making > public Release Candidates if this request is ignored. > > Feedback and bug reports should be sent to this email list or one of the of the > others mentioned here in the User Guide: > _https://wsjt.sourceforge.io/wsjtx-doc/wsjtx-main.html#SUPPORT > <https://wsjt.sourceforge.io/wsjtx-doc/wsjtx-main.html#SUPPORT>_. > > We hope you will enjoy using WSJT-X 2.7.0. > > -- 73 from Joe, K1JT; Steve, K9AN; Nico, IV3NWV; Uwe, DG2YCB; > > Brian, N9ADG; John, G4KLA; and Charlie, DL3WDG. > > > > > > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel -- Lance Collister, W7GJ(ex WA3GPL, WA1JXN, WA1JXN/C6A, ZF2OC/ZF8, E51SIX, 3D2LR, 5W0GJ, E6M, TX5K, KH8/W7GJ, V6M, T8GJ, VK9CGJ, VK9XGJ, C21GJ, CP1GJ, S79GJ, TX7MB, TO7GJ, 3B9GJ, ZD9GJ) P.O. Box 73 Frenchtown, MT 59834-0073 USA TEL: (406) 626-5728 QTH: DN27ub URL: http://www.bigskyspaces.com/w7gj Skype: lanceW7GJ 2m DXCC #11 - 6m DXCC #815 - FFMA #7 Interested in 6m EME? Ask me about subscribing to the new Magic Band EME email group, or just fill in the request box at the bottom of my web page (above)! |
|
From: Leslie L <ll...@gm...> - 2025-02-17 22:07:41
|
Thank you Joe and Team! 73 Les W2LPL On Mon, Feb 17, 2025, 1:04 PM <wsj...@li...> wrote: > Send wsjt-devel mailing list submissions to > wsj...@li... > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > or, via email, send a message with subject or body 'help' to > wsj...@li... > > You can reach the person managing the list at > wsj...@li... > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of wsjt-devel digest..." > > > Today's Topics: > > 1. WSJT-X 2.7.0 GA Release (Joseph Taylor) > 2. Re: WSJT-X 2.7.0 GA Release (Xavi Canyadell) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 17 Feb 2025 13:02:17 +0000 > From: Joseph Taylor <jo...@Pr...> > To: WSJT software development <wsj...@li...> > Subject: [wsjt-devel] WSJT-X 2.7.0 GA Release > Message-ID: > < > SA2...@SA... > > > > Content-Type: text/plain; charset="windows-1252" > > The WSJT Development Team is pleased to announce the WSJT-X 2.7.0 General > Availability (GA) release. This is the first GA release since version > 2.6.1, two years ago. Major enhancements include a new companion program > called QMAP, new Special Operating Activities called ?Q65 Pileup? and > ?SuperFox?, and a new ?Message System? feature designed for sending > requests to change to another band or mode. More details can be found in > the Release Notes here: https://wsjt.sourceforge.io/Release_Notes.txt. > > > > Direct links for downloading pre-built installation packages for Windows, > Linux, and macOS can be found on the WSJT-X web page: > https://wsjt.sourceforge.io/wsjtx.html. For those who like to compile > from source, a complete source-code tarball is available there as well. > > > > Please note: A few changes and updates to the WSJT-X User Guide are still > to be completed. > > If you will be translating the User Guide to another language, please wait > for an announcement that the updated English guide is ready and available > online. > > > > WSJT-X is licensed under the terms of Version 3 of the GNU General Public > License (GPL). Development of this software is a cooperative project to > which many amateur radio operators have contributed. If you use our code, > please have the courtesy to let us know about it. > > > > The authors and Copyright holders of WSJT-X request that derivative works > should not publish programs based on features in WSJT-X before those > features are made available in a General Availability (GA) release of > WSJT-X. We will cease making public Release Candidates if this request is > ignored. > > > > Feedback and bug reports should be sent to this email list or one of the > of the others mentioned here in the User Guide: > https://wsjt.sourceforge.io/wsjtx-doc/wsjtx-main.html#SUPPORT. > > > > We hope you will enjoy using WSJT-X 2.7.0. > > > > -- 73 from Joe, K1JT; Steve, K9AN; Nico, IV3NWV; Uwe, DG2YCB; > > Brian, N9ADG; John, G4KLA; and Charlie, DL3WDG. > > > > > -------------- next part -------------- > An HTML attachment was scrubbed... > > ------------------------------ > > Message: 2 > Date: Mon, 17 Feb 2025 19:04:12 +0100 > From: Xavi Canyadell <ea3...@gm...> > To: Joseph Taylor via wsjt-devel <wsj...@li...>, > jo...@Pr... > Subject: Re: [wsjt-devel] WSJT-X 2.7.0 GA Release > Message-ID: <ed4...@gm...> > Content-Type: text/plain; charset="utf-8"; Format="flowed" > > Hi Joe: > > > No files to translate the news ? > > > Thank you for your work ! > > > -- > Xavi Canyadell, EA3W > Tel?fon +34670243468 > http://www.ea3w.cat > > > El 17/2/2025 a les 14:02, Joseph Taylor via wsjt-devel ha escrit: > > > > The WSJT Development Team is pleased to announce the WSJT-X 2.7.0 > > General Availability (GA) release. This is the first GA release since > > version 2.6.1, two years ago. Major enhancements include a new > > companion program called QMAP, new Special Operating Activities called > > ?Q65 Pileup? and ?SuperFox?, and a new ?Message System? feature > > designed for sending requests to change to another band or mode. More > > details can be found in the Release Notes here: > > _https://wsjt.sourceforge.io/Release_Notes.txt > > <https://wsjt.sourceforge.io/Release_Notes.txt>_. > > > > Direct links for downloading pre-built installation packages for > > Windows, Linux, and macOS can be found on the WSJT-X web page: > > _https://wsjt.sourceforge.io/wsjtx.html > > <https://wsjt.sourceforge.io/wsjtx.html>_. For those who like to > > compile from source, a complete source-code tarball?is available there > > as well. > > > > Please note: A few changes and updates to the WSJT-X User Guide are > > still to be completed. > > > > If you will be translating the User Guide to another language, please > > wait for an announcement that the updated English guide is ready and > > available online. > > > > WSJT-X is licensed under the terms of Version 3 of the GNU General > > Public License (GPL). Development of this software is a cooperative > > project to which many amateur radio operators have contributed. If you > > use our code, please have the courtesy to let us know about it. > > > > The authors and Copyright holders of WSJT-X request that derivative > > works should not publish programs based on features in WSJT-X before > > those features are made available in a General Availability (GA) > > release of WSJT-X. We will cease making public Release Candidates if > > this request is ignored. > > > > Feedback and bug reports should be sent to this email list or one of > > the of the others mentioned here in the User Guide: > > _https://wsjt.sourceforge.io/wsjtx-doc/wsjtx-main.html#SUPPORT > > <https://wsjt.sourceforge.io/wsjtx-doc/wsjtx-main.html#SUPPORT>_. > > > > We hope you will enjoy using WSJT-X 2.7.0. > > > > -- 73 from Joe, K1JT; Steve, K9AN; Nico, IV3NWV; Uwe, DG2YCB; > > > > Brian, N9ADG; John, G4KLA; and Charlie, DL3WDG. > > > > > > > > > > > > _______________________________________________ > > wsjt-devel mailing list > > wsj...@li... > > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > > > -- > S'ha comprovat que aquest correu no contingui virus amb el programari > d'antivirus d'Avast. > www.avast.com > -------------- next part -------------- > An HTML attachment was scrubbed... > > ------------------------------ > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > > > ------------------------------ > > End of wsjt-devel Digest, Vol 132, Issue 11 > ******************************************* > |
|
From: Xavi C. <ea3...@gm...> - 2025-02-17 18:04:27
|
Hi Joe: No files to translate the news ? Thank you for your work ! -- Xavi Canyadell, EA3W Telèfon +34670243468 http://www.ea3w.cat El 17/2/2025 a les 14:02, Joseph Taylor via wsjt-devel ha escrit: > > The WSJT Development Team is pleased to announce the WSJT-X 2.7.0 > General Availability (GA) release. This is the first GA release since > version 2.6.1, two years ago. Major enhancements include a new > companion program called QMAP, new Special Operating Activities called > “Q65 Pileup” and “SuperFox”, and a new “Message System” feature > designed for sending requests to change to another band or mode. More > details can be found in the Release Notes here: > _https://wsjt.sourceforge.io/Release_Notes.txt > <https://wsjt.sourceforge.io/Release_Notes.txt>_. > > Direct links for downloading pre-built installation packages for > Windows, Linux, and macOS can be found on the WSJT-X web page: > _https://wsjt.sourceforge.io/wsjtx.html > <https://wsjt.sourceforge.io/wsjtx.html>_. For those who like to > compile from source, a complete source-code tarball is available there > as well. > > Please note: A few changes and updates to the WSJT-X User Guide are > still to be completed. > > If you will be translating the User Guide to another language, please > wait for an announcement that the updated English guide is ready and > available online. > > WSJT-X is licensed under the terms of Version 3 of the GNU General > Public License (GPL). Development of this software is a cooperative > project to which many amateur radio operators have contributed. If you > use our code, please have the courtesy to let us know about it. > > The authors and Copyright holders of WSJT-X request that derivative > works should not publish programs based on features in WSJT-X before > those features are made available in a General Availability (GA) > release of WSJT-X. We will cease making public Release Candidates if > this request is ignored. > > Feedback and bug reports should be sent to this email list or one of > the of the others mentioned here in the User Guide: > _https://wsjt.sourceforge.io/wsjtx-doc/wsjtx-main.html#SUPPORT > <https://wsjt.sourceforge.io/wsjtx-doc/wsjtx-main.html#SUPPORT>_. > > We hope you will enjoy using WSJT-X 2.7.0. > > -- 73 from Joe, K1JT; Steve, K9AN; Nico, IV3NWV; Uwe, DG2YCB; > > Brian, N9ADG; John, G4KLA; and Charlie, DL3WDG. > > > > > > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel -- S'ha comprovat que aquest correu no contingui virus amb el programari d'antivirus d'Avast. www.avast.com |
|
From: Joseph T. <jo...@Pr...> - 2025-02-17 17:36:42
|
The WSJT Development Team is pleased to announce the WSJT-X 2.7.0 General Availability (GA) release. This is the first GA release since version 2.6.1, two years ago. Major enhancements include a new companion program called QMAP, new Special Operating Activities called “Q65 Pileup” and “SuperFox”, and a new “Message System” feature designed for sending requests to change to another band or mode. More details can be found in the Release Notes here: https://wsjt.sourceforge.io/Release_Notes.txt. Direct links for downloading pre-built installation packages for Windows, Linux, and macOS can be found on the WSJT-X web page: https://wsjt.sourceforge.io/wsjtx.html. For those who like to compile from source, a complete source-code tarball is available there as well. Please note: A few changes and updates to the WSJT-X User Guide are still to be completed. If you will be translating the User Guide to another language, please wait for an announcement that the updated English guide is ready and available online. WSJT-X is licensed under the terms of Version 3 of the GNU General Public License (GPL). Development of this software is a cooperative project to which many amateur radio operators have contributed. If you use our code, please have the courtesy to let us know about it. The authors and Copyright holders of WSJT-X request that derivative works should not publish programs based on features in WSJT-X before those features are made available in a General Availability (GA) release of WSJT-X. We will cease making public Release Candidates if this request is ignored. Feedback and bug reports should be sent to this email list or one of the of the others mentioned here in the User Guide: https://wsjt.sourceforge.io/wsjtx-doc/wsjtx-main.html#SUPPORT. We hope you will enjoy using WSJT-X 2.7.0. -- 73 from Joe, K1JT; Steve, K9AN; Nico, IV3NWV; Uwe, DG2YCB; Brian, N9ADG; John, G4KLA; and Charlie, DL3WDG. |
|
From: Reino T. <rei...@ko...> - 2025-02-12 19:32:23
|
> Ed Kerns, Wednesday, February 12, 2025 5:44 PM wrote: > WSJT-X seems to accept a two-letter abbreviation for STATE/PROVINCE as a substitute for Grid. However, there does not seem to be a means by which NAME can be exchanged. The Tx5 message can be modified (e.g., $DXCALL mycall myname), but seems to terminate the myname at the first letter and it has a maximum length. Hi Ed, Simple answer is unfortunately no. A more detailed is that even the grid substitute is valid only at range AA to RR. The Tx5 can transport maximum 13 characters, no more. If you want to study the message encoding in detail there is an excellent document available as Reference 33, https://wsjt.sourceforge.io/FT4_FT8_QEX.pdf 73, Reino OH3mA |
|
From: Ed K. <ed...@ho...> - 2025-02-12 15:59:23
|
Is there a way to transfer a contest exchange: NAME and STATE/PROVINCE via WSJT-X and have it be accurately logged? This would be useful for a contest that uses this exchange. WSJT-X seems to accept a two-letter abbreviation for STATE/PROVINCE as a substitute for Grid. However, there does not seem to be a means by which NAME can be exchanged. The Tx5 message can be modified (e.g., $DXCALL mycall myname), but seems to terminate the myname at the first letter and it has a maximum length. Another modification might leave out my call (e.g., $DXCALL myname), but I'm not sure this would be properly logged by the receiving station. Many thanks and 73, Ed, N1...@AR... |
|
From: <gre...@sy...> - 2025-02-11 17:26:42
|
I am running an IC-7600 with a SteppIR, with Windows 11. I am currently running v2.7.0-rc8 The problem I am having started with the install of the 2.7 releases. In the prior releases when I change bands/modes the rig moves to the correct frequency and the SteppIR also tunes to the correct frequency. In the 2.7 releases the rig moves to the correct frequency but the SteppIR does not. If I move the VFO on the rig 10-20 Hz the SteppIR tunes to the correct frequency. If I make a band change (frequency of the SteppIR does not change ) but go to File>Settings>Radio and click "Test CAT" the SteppIR tunes Greg VE3PJ 613-328-6538 |
|
From: <fer...@ti...> - 2025-02-10 10:11:33
|
Dear all, I like the proposed RC8 message system. QSY to different (frequency and) mode will be great, but I would like to see also JS8 among the possible modes to be chosen. I understand that it is a mode outside of WSJT-X, but I see SSB or other available in the message system, and if I see correctly in the source code, it seems possible to add a new one-letter code for JS8. I don't know if such an addition is of interest to many, but I'm sure that JS8, sharing with FT8 the signal performances and allowing free text follow ups to FT8 QSOs, would be a great addition to the new message system. Thanks in advance for any comments (I hope to not have missed something ':) Regards & 73! /Claudio, IU2TUL |
|
From: Doug B. Sr. <dou...@gm...> - 2025-02-07 13:50:30
|
Thanks. The meter on Flrig itself. I assume it should be flashing some green with even noise? That brings up another thing, Flrig's sliders are there but grayed out. Any idea what that means? On Fri, Feb 7, 2025 at 8:45 AM Black Michael <mdb...@ya...> wrote: > Which signal meter are you referring to? The IC706 or FLRig's? > > Check the RF gain on FLRig. Should be the 2nd slider from the top. > > Mike W9MDB > > > > > On Friday, February 7, 2025 at 06:31:12 AM CST, Doug Breault, Sr. via > wsjt-devel <wsj...@li...> wrote: > > > Hello All, > > This might be a super dumb idea but just wanted to throw it out there: > > I was able to get my Linux Mint -> Digirig -> Icom 706 MkIIG working > perfectly with WSJTX, however, I can't for the life of me get it fully > working w/ Flrig. In Flrig, frequency control is working, Tx is going on > (and even off) w/ the PTT button, but now I'm noticing the signal meter has > nothing on it, like somehow it's not hearing signal. (using Flrig 2.0.0.4) > > This might not even be apples-to-apples or politically possible, but it > would be cool if WSJT-X could expose a settings file, and Flrig could read > it, fire up, and just work. > > Thanks, > 73 Doug KC1UUH > > > > > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > |
68 messages has been excluded from this view by a project administrator.
