[wsjt-devel] 2.6.0 RC1 : 'a7' message in FT8
Hello, I found 'a7' message in FT8 with Normal decoding while disabling AP. Does it show regardless "Enable AP"? Besides, 1.6.0 manual says 'a7' is shown at message component of "Call_1 Call_2 ?" though it also appears in CQ message. Belows are the list of 'a7' from ALL.TXT file. 220617_231200 7.041 Rx FT8-24 1.3 1091 JQ3BBQ JA0EKS PM87 a7 220617_231815 7.041 Rx FT8-14 0.6 2500 JH5CHY JQ2GWH 73 a7 220617_232145 7.041 Rx FT8-10 0.6 2500 JN7BPV JQ2GWH R-21 a7 220617_232215 7.041 Rx FT8-21 1.2 1732 7M4HIC JA0PBK PM96 a7 220617_233730 7.041 Rx FT8-15 -0.8 1594 CQ JR1EMO PM95 a7 220617_235930 7.041 Rx FT8-24 -0.2 923 JH9ATW JE2DIR 73 a7 220618_000545 7.041 Rx FT8 -2 0.2 779 JE2DIR 7N4NGN +01 a7 220618_000845 7.041 Rx FT8-19 0.0 648 JQ7BOF JK1MWK PM95 a7 220618_001015 7.041 Rx FT8-22 0.0 1855 JE2DIR JE1BFK QM05a7 220618_001045 7.041 Rx FT8-20 0.0 1854 JE2DIR JE1BFK QM05a7 220618_001145 7.041 Rx FT8-22 0.0 1854 JE2DIR JE1BFK QM05a7 220618_001600 7.041 Rx FT8-23 0.4 977 JP3SML JJ1BCB PM95 a7 220618_002815 7.041 Rx FT8-14 0.0 2351 CQ JH1RNS PM95 a7 220618_002900 7.041 Rx FT8-24 0.5 978 JA2ITK JJ1BCB PM95 a7 220618_003315 7.041 Rx FT8-23 0.0 1224 JQ7BQT JA9ASN PM86 a7 220618_003330 7.041 Rx FT8 -8 0.5 450 CQ JO1LAC QM06a7 220618_003430 7.041 Rx FT8 -4 0.1 2204 JA2ITK JH1OBY QM05 a7 220618_003500 7.041 Rx FT8 -5 0.1 2204 JA2ITK JH1OBY QM05 a7 220618_003900 7.041 Rx FT8-24 0.0 1608 JJ3UBI JN1WGZ 73 a7 220618_003945 7.041 Rx FT8-16 0.1 2153 JN1FVW JH1FNU +09a7 220618_005700 7.041 Rx FT8-24 0.1 1206 JM4CNU JA6FOD R-03 a7 220618_011730 7.041 Rx FT8-16 -0.0 2479 JA3CAW JA9KTT RR73 a7 73 Yukio JG1APX ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] RC1 UI bug
Il 17/06/22 17:00, Joe Taylor via wsjt-devel ha scritto: Marco -- On 6/17/2022 3:50 PM, Marco Calistri via wsjt-devel wrote: What is that "FT8-D" mode? There is no mode FT8-D. That label on the K0VM screen shot is a name he selected for a Configuration. -- Joe, K1JT Thanks Joe for your specification! I will be wait a bit to upgrade to 2.6. 2.5.4 is working very well here for FT8/FT4 modes. Best regards! --- 73 de Marco, PY1ZRJ (former IK5BCU) ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] RC1 UI bug
Il 17/06/22 17:00, Reino Talarmo ha scritto: Hi Marco. It is just a title defined for a Configuration by AL. 73, Reino >What is that "FT8-D" mode? Thanks Reino! --- *73 de Marco, PY1ZRJ (former IK5BCU)* **___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] RC1 UI bug
Hi Marco. It is just a title defined for a Configuration by AL. 73, Reino >What is that "FT8-D" mode? ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] RC1 UI bug
Al -- Your screen shot shows an inadvertent user error, not a program bug. It seems you have mistakenly checked "SWL Mode" on the View menu. -- Joe, K1JT On 6/17/2022 3:50 PM, Marco Calistri via wsjt-devel wrote: Il 17/06/22 12:17, Al via wsjt-devel ha scritto: ( 2.6.0-rc1, W11) Some how while transmitting and looking at mode in title bard I ended up with this and could not recover this missing controls until I restored my .ini from daily backup. AL, K0VM ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel What is that "FT8-D" mode? Thanks! --- *73 de Marco, PY1ZRJ (former IK5BCU)* ** ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] RC1 UI bug
Marco -- On 6/17/2022 3:50 PM, Marco Calistri via wsjt-devel wrote: What is that "FT8-D" mode? There is no mode FT8-D. That label on the K0VM screen shot is a name he selected for a Configuration. -- Joe, K1JT ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] 2.6.0 RC1 - wspr timing off
2.6.0-rc1, built from source for 64-bit linux Fedora Core - In WSPR mode, repeatedly switches bands on odd-minutes, after only 1 minute of receive/transmit. -- P.J. "Josh" Rovero http://www.roveroresearch.org Ham Radio: KK1D ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Ver 2.6.1 rc1: Possible bug in writing out the WSJT-X.ini file
Hi Sam, You did not explain why you think there is a bug. Or (except perhaps for curiosity?) why you need to examine the contents of file WSJT-X.ini. Anyway, the line you want looks like this: RespondCQ=2 The value will be 0 for "CQ: None", 1 for "CQ: First", or 2 for "CQ: Max Dist". -- 73, Joe, K1JT On 6/17/2022 10:53 AM, Sam W2JDB via wsjt-devel wrote: Hi, In testing RC1 and trying to find the place where the new option of Max Distance is recorded in the WSJT-X.ini file I compare the file where Call First is selected with the file where Max Distance is selected. It seems that the wsjt-x.ini file was changed on line 46 which has nothing to do with the currently selected configuration. Below are the 2 lines from the 2 files The top line is from the ini file where Max Distance was selected The bottom line is from Call first selected. IC7300%20NoBridge\Common\pwrBandTuneMemory=@Variant(\0\0\0\x1c\0\0\0\x4\0\0\0\x6\0\x34\0\x30\0m\0\0\0\x2\0\0\0\x95\0\0\0\b\0\x31\0\x36\0\x30\0m\0\0\0\x2\0\0\0\x95\0\0\0\x6\0\x33\0\x30\0m\0\0\0\x2\0\0\0\x63\0\0\0\x6\0\x32\0\x30\0m\0\0\0\x2\0\0\0\x64) IC7300%20NoBridge\Common\pwrBandTuneMemory=@Variant(\0\0\0\x1c\0\0\0\x4\0\0\0\x6\0\x34\0\x30\0m\0\0\0\x2\0\0\0\x95\0\0\0\x6\0\x33\0\x30\0m\0\0\0\x2\0\0\0\x63\0\0\0\x6\0\x32\0\x30\0m\0\0\0\x2\0\0\0\x64\0\0\0\b\0\x31\0\x36\0\x30\0m\0\0\0\x2\0\0\0\x95) In both cases the CallFirst was set to true in the currently selected configuration. Running latest Win/10. 73, Sam W2JDB ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] RC1 UI bug
( 2.6.0-rc1, W11) Some how while transmitting and looking at mode in title bard I ended up with this and could not recover this missing controls until I restored my .ini from daily backup. AL, K0VM___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Ver 2.6.1 rc1: Possible bug in writing out the WSJT-X.ini file
Hi, I forgot to mention that the line affected was number 46. 73, Sam W2JDB -Original Message- From: Sam W2JDB via wsjt-devel To: wsjt-devel@lists.sourceforge.net Cc: Sam W2JDB Sent: Fri, Jun 17, 2022 10:53 am Subject: Re: [wsjt-devel] Ver 2.6.1 rc1: Possible bug in writing out the WSJT-X.ini file Hi, In testing RC1 and trying to find the place where the new option of Max Distance is recorded in the WSJT-X.ini fileI compare the file where Call First is selected with the file where Max Distance is selected. It seems that the wsjt-x.ini file was changed on line 46 which has nothing to do with the currently selected configuration. Below are the 2 lines from the 2 files The top line is from the ini file where Max Distance was selected The bottom line is from Call first selected. IC7300%20NoBridge\Common\pwrBandTuneMemory=@Variant(\0\0\0\x1c\0\0\0\x4\0\0\0\x6\0\x34\0\x30\0m\0\0\0\x2\0\0\0\x95\0\0\0\b\0\x31\0\x36\0\x30\0m\0\0\0\x2\0\0\0\x95\0\0\0\x6\0\x33\0\x30\0m\0\0\0\x2\0\0\0\x63\0\0\0\x6\0\x32\0\x30\0m\0\0\0\x2\0\0\0\x64) IC7300%20NoBridge\Common\pwrBandTuneMemory=@Variant(\0\0\0\x1c\0\0\0\x4\0\0\0\x6\0\x34\0\x30\0m\0\0\0\x2\0\0\0\x95\0\0\0\x6\0\x33\0\x30\0m\0\0\0\x2\0\0\0\x63\0\0\0\x6\0\x32\0\x30\0m\0\0\0\x2\0\0\0\x64\0\0\0\b\0\x31\0\x36\0\x30\0m\0\0\0\x2\0\0\0\x95) In both cases the CallFirst was set to true in the currently selected configuration. Running latest Win/10. 73, Sam W2JDB ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Ver 2.6.1 rc1: Possible bug in writing out the WSJT-X.ini file
Hi, In testing RC1 and trying to find the place where the new option of Max Distance is recorded in the WSJT-X.ini fileI compare the file where Call First is selected with the file where Max Distance is selected. It seems that the wsjt-x.ini file was changed on line 46 which has nothing to do with the currently selected configuration. Below are the 2 lines from the 2 files The top line is from the ini file where Max Distance was selected The bottom line is from Call first selected. IC7300%20NoBridge\Common\pwrBandTuneMemory=@Variant(\0\0\0\x1c\0\0\0\x4\0\0\0\x6\0\x34\0\x30\0m\0\0\0\x2\0\0\0\x95\0\0\0\b\0\x31\0\x36\0\x30\0m\0\0\0\x2\0\0\0\x95\0\0\0\x6\0\x33\0\x30\0m\0\0\0\x2\0\0\0\x63\0\0\0\x6\0\x32\0\x30\0m\0\0\0\x2\0\0\0\x64) IC7300%20NoBridge\Common\pwrBandTuneMemory=@Variant(\0\0\0\x1c\0\0\0\x4\0\0\0\x6\0\x34\0\x30\0m\0\0\0\x2\0\0\0\x95\0\0\0\x6\0\x33\0\x30\0m\0\0\0\x2\0\0\0\x63\0\0\0\x6\0\x32\0\x30\0m\0\0\0\x2\0\0\0\x64\0\0\0\b\0\x31\0\x36\0\x30\0m\0\0\0\x2\0\0\0\x95) In both cases the CallFirst was set to true in the currently selected configuration. Running latest Win/10. 73, Sam W2JDB ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
