Re: [wsjt-devel] callsigns in <>
Hi Bruce, Please read Section 7.5, "Nonstandard Callsigns", in the WSJT-X User Guide. https://wsjt.sourceforge.io/wsjtx-doc/wsjtx-main-2.6.1.html#COMP-CALL Take particular notice of this sentence: "Except for the special cases involving /P or /R used in VHF contesting, WSJT-X 2.6 offers no support for two nonstandard callsigns to work each other." In such a situation you should work WB0GAG/1 as WB0GAG. -- 73, Joe, K1JT On 12/27/2023 10:37 AM, Bruce Dagel via wsjt-devel wrote: WSJT-X version 2.6.1 My mistake, I was going from memory. The actual problem comes with a longer call. WB0GAG/1 R+11 transmits as WB0GAG 73, Bruce, WB0GAG ___ 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] callsigns in <>
This is outlined in section 7.5 “non-standard callsigns” - specifically the last sentence in that section: “ offers no support for two nonstandard callsigns to work each other.” > On Dec 27, 2023, at 10:43 AM, Bruce Dagel via wsjt-devel > wrote: > > WSJT-X version 2.6.1 > > My mistake, I was going from memory. > The actual problem comes with a longer call. WB0GAG/1 R+11 > transmits as WB0GAG > > 73, > Bruce, WB0GAG > > > ___ > 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] callsigns in <>
That's correct -- you cannot do two compound calls like that. It's a known limitation of the message format. There is an option for "full call in..." options but they don't seem to honored. I'm still seeing full call transmitted in all messages. Would be more than nice if WSJT-X could call ft8code internally and show what is actually going to get transmitted. 1. W9MDB/4 +11 W9MDB/4 * 4. Nonstandard call Mike W9MDB On Wednesday, December 27, 2023 at 09:44:28 AM CST, Bruce Dagel via wsjt-devel wrote: WSJT-X version 2.6.1 My mistake, I was going from memory. The actual problem comes with a longer call. WB0GAG/1 R+11 transmits as WB0GAG 73, Bruce, WB0GAG ___ 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] callsigns in <>
WSJT-X version 2.6.1 My mistake, I was going from memory. The actual problem comes with a longer call. WB0GAG/1 R+11 transmits as WB0GAG 73, Bruce, WB0GAG ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] callsigns in <>
Bruce, when callsigns are in angle brackets WSJTx is actually sending a hash of the callsign and not the actual callsign. The software is not sending plaintext as a string. More info here: https://wsjt.sourceforge.io/wsjtx-doc/wsjtx-main-2.7.0-rc2.html#COMP-CALL -- 73 Chris kc2ieb On Wed, Dec 27, 2023 at 9:53 AM Bruce Dagel via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > While coordinating W1AW/O for Iowa, I observed that I couldn't make some > contacts because the signal report was cut off, i.e., Tx2 would be > WB0GAG when WB0GAG R+11 should be sent. I believe it > is a matter of too many characters. The called station had nothing to > confirm. > > A solution would appear to be to change so that the angle brackets > replace the spaces instead of being added to them, i.e. > WB0GAGR+11, where the angle brackets would do double duty. > > 73, > Bruce, WB0GAG > > > ___ > 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] callsigns in <>
What version of WSJT-X? This message seems to encode OK as a standard message. Is it possible your decode window isn't wide enough to see the R+11?? C:\WSJT\wsjtx\bin>ft8code "WB0GAG R+11" Message Decoded Err i3.n3 1. WB0GAG R+11 WB0GAG R+11 1. Standard msg Mike W9MDB On Wednesday, December 27, 2023 at 08:59:04 AM CST, Bruce Dagel via wsjt-devel wrote: While coordinating W1AW/O for Iowa, I observed that I couldn't make some contacts because the signal report was cut off, i.e., Tx2 would be WB0GAG when WB0GAG R+11 should be sent. I believe it is a matter of too many characters. The called station had nothing to confirm. A solution would appear to be to change so that the angle brackets replace the spaces instead of being added to them, i.e. WB0GAGR+11, where the angle brackets would do double duty. 73, Bruce, WB0GAG ___ 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] callsigns in <>
While coordinating W1AW/O for Iowa, I observed that I couldn't make some contacts because the signal report was cut off, i.e., Tx2 would be WB0GAG when WB0GAG R+11 should be sent. I believe it is a matter of too many characters. The called station had nothing to confirm. A solution would appear to be to change so that the angle brackets replace the spaces instead of being added to them, i.e. WB0GAGR+11, where the angle brackets would do double duty. 73, Bruce, WB0GAG ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
