Re: [wsjt-devel] CQ Hound mode
The one thing I have noticed on every dxpedition I've worked over the last year so WSJTX Fox mode bill on an 300Hz offset for channel 1.MSHV will normally be above 500Hz. You'll also see MSHV work people calling below 1000Hz. I can always tell the difference. And you don't really need Hound mode -- just be prepared to stop the last 73 tranmission (it's definitely not needed for dxpeditions and just causes QRM). Mike W9MDB On Monday, November 6, 2023 at 02:31:48 AM CST, Reino Talarmo via wsjt-devel wrote: Sure, of course nothing what so ever! Mshv should in that case *not* to use it on the standard frequencies and when they are just using multifrequency, but not F/H protocol. Otherwise we gain nothing at all, hi! I just wanted to point that it requires everybody to update their wsjt-x version. In addition should that specific CQ type extended to cover other situations where the operator wants to tell what kind of station he is using? Or is it just because mshv and perhaps other derivate programs don’t follow the intention of the original F/H protocol? Possible additional cases could be QRP, POTA, VOTA, etc. a continuously expanding situations where the operator want to differentiate from the normal users. As already proposed the directed call gives a possibility for the indication, such as CQ FOX … Should then the program have an automatic jump into Hound mode, when user double clicks on that message? 73, Reino OH3mA From: Sam W2JDB via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] Sent: Sunday, November 5, 2023 11:53 PM To: Reino Talarmo via wsjt-devel Cc: Sam W2JDB Subject: Re: [wsjt-devel] CQ Hound mode and what's to stop mshv from adapting the same call method? 73 Sam W2JDB On Sunday, November 5, 2023 at 04:27:38 PM EST, Reino Talarmo via wsjt-devel wrote: Just a minor point, I assume. If that is programmed into wsjt-x, then the change will not be backwards compatible. The CQ part of the message is actually a specific pretty long bit string (28 bits, ‘c28’). There could be another bit string for the CQF, but none of the current versions would present it as the CQF and the protocol machine would not work. If you feel a need to study it further, see https://wsjt.sourceforge.io/FT4_FT8_QEX.pdf. 73, Reino OH3mA From: Scott Armstrong via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] Sent: Sunday, November 5, 2023 10:53 PM To: WSJT software development Cc: Scott Armstrong Subject: Re: [wsjt-devel] CQ Hound mode I believe he meant Fox. CQF I like that idea. It would differentiate between F/H and MSHV. But this all assumes the DX stops and calls CQ ever once in a while. -Scott AA5AM On Sun, Nov 5, 2023 at 2:38 PM Gary McDuffie via wsjt-devel wrote: > On Nov 5, 2023, at 13:08, Pino Zollo via wsjt-devel > wrote: > > Just an idea: > > When in Hound mode the DX station should call as: > > CQH DX0CALL GRID > > or > > CH DX0CALL GRID But why? He should only be hound if he is on his published frequency (which you can determine yourself), and he should never be in hound mode if he is in the normal FT frequency segment. Gary - AG0N ___ 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 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] CQ Hound mode
Sure, of course nothing what so ever! Mshv should in that case *not* to use it on the standard frequencies and when they are just using multifrequency, but not F/H protocol. Otherwise we gain nothing at all, hi! I just wanted to point that it requires everybody to update their wsjt-x version. In addition should that specific CQ type extended to cover other situations where the operator wants to tell what kind of station he is using? Or is it just because mshv and perhaps other derivate programs don’t follow the intention of the original F/H protocol? Possible additional cases could be QRP, POTA, VOTA, etc. a continuously expanding situations where the operator want to differentiate from the normal users. As already proposed the directed call gives a possibility for the indication, such as CQ FOX … Should then the program have an automatic jump into Hound mode, when user double clicks on that message? 73, Reino OH3mA From: Sam W2JDB via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] Sent: Sunday, November 5, 2023 11:53 PM To: Reino Talarmo via wsjt-devel Cc: Sam W2JDB Subject: Re: [wsjt-devel] CQ Hound mode and what's to stop mshv from adapting the same call method? 73 Sam W2JDB On Sunday, November 5, 2023 at 04:27:38 PM EST, Reino Talarmo via wsjt-devel mailto:wsjt-devel@lists.sourceforge.net> > wrote: Just a minor point, I assume. If that is programmed into wsjt-x, then the change will not be backwards compatible. The CQ part of the message is actually a specific pretty long bit string (28 bits, ‘c28’). There could be another bit string for the CQF, but none of the current versions would present it as the CQF and the protocol machine would not work. If you feel a need to study it further, see https://wsjt.sourceforge.io/FT4_FT8_QEX.pdf. 73, Reino OH3mA From: Scott Armstrong via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] Sent: Sunday, November 5, 2023 10:53 PM To: WSJT software development mailto:wsjt-devel@lists.sourceforge.net> > Cc: Scott Armstrong mailto:aa5am.sc...@gmail.com> > Subject: Re: [wsjt-devel] CQ Hound mode I believe he meant Fox. CQF I like that idea. It would differentiate between F/H and MSHV. But this all assumes the DX stops and calls CQ ever once in a while. -Scott AA5AM On Sun, Nov 5, 2023 at 2:38 PM Gary McDuffie via wsjt-devel mailto:wsjt-devel@lists.sourceforge.net> > wrote: > On Nov 5, 2023, at 13:08, Pino Zollo via wsjt-devel > mailto:wsjt-devel@lists.sourceforge.net> > > wrote: > > Just an idea: > > When in Hound mode the DX station should call as: > > CQH DX0CALL GRID > > or > > CH DX0CALL GRID But why? He should only be hound if he is on his published frequency (which you can determine yourself), and he should never be in hound mode if he is in the normal FT frequency segment. Gary - AG0N ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net> https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net <mailto: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] CQ Hound mode
Re: Reino Talarmo via wsjt-devel > Just a minor point, I assume. If that is programmed into wsjt-x, then the > change will not be backwards compatible. The CQ part of the message is > actually a specific pretty long bit string (28 bits, ‘c28’). There could be > another bit string for the CQF, but none of the current versions would > present it as the CQF and the protocol machine would not work. If you feel a > need to study it further, see https://wsjt.sourceforge.io/FT4_FT8_QEX.pdf. "No bits left" was my first thought as well, but people can put "FOX" or "FH" in the CQ message even today: "CQ FH X0YZ AB12" (If they are lucky, someone from Mayotte might even answer. :D) Christoph ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] CQ Hound mode
and what's to stop mshv from adapting the same call method? 73 Sam W2JDB On Sunday, November 5, 2023 at 04:27:38 PM EST, Reino Talarmo via wsjt-devel wrote: Just a minor point, I assume. If that is programmed into wsjt-x, then the change will not be backwards compatible. The CQ part of the message is actually a specific pretty long bit string (28 bits, ‘c28’). There could be another bit string for the CQF, but none of the current versions would present it as the CQF and the protocol machine would not work. If you feel a need to study it further, see https://wsjt.sourceforge.io/FT4_FT8_QEX.pdf. 73, Reino OH3mA From: Scott Armstrong via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] Sent: Sunday, November 5, 2023 10:53 PM To: WSJT software development Cc: Scott Armstrong Subject: Re: [wsjt-devel] CQ Hound mode I believe he meant Fox. CQF I like that idea. It would differentiate between F/H and MSHV. But this all assumes the DX stops and calls CQ ever once in a while. -Scott AA5AM On Sun, Nov 5, 2023 at 2:38 PM Gary McDuffie via wsjt-devel wrote: > On Nov 5, 2023, at 13:08, Pino Zollo via wsjt-devel > wrote: > > Just an idea: > > When in Hound mode the DX station should call as: > > CQH DX0CALL GRID > > or > > CH DX0CALL GRID But why? He should only be hound if he is on his published frequency (which you can determine yourself), and he should never be in hound mode if he is in the normal FT frequency segment. Gary - AG0N ___ 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 mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] CQ Hound mode
Just a minor point, I assume. If that is programmed into wsjt-x, then the change will not be backwards compatible. The CQ part of the message is actually a specific pretty long bit string (28 bits, ‘c28’). There could be another bit string for the CQF, but none of the current versions would present it as the CQF and the protocol machine would not work. If you feel a need to study it further, see https://wsjt.sourceforge.io/FT4_FT8_QEX.pdf. 73, Reino OH3mA From: Scott Armstrong via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] Sent: Sunday, November 5, 2023 10:53 PM To: WSJT software development Cc: Scott Armstrong Subject: Re: [wsjt-devel] CQ Hound mode I believe he meant Fox. CQF I like that idea. It would differentiate between F/H and MSHV. But this all assumes the DX stops and calls CQ ever once in a while. -Scott AA5AM On Sun, Nov 5, 2023 at 2:38 PM Gary McDuffie via wsjt-devel mailto:wsjt-devel@lists.sourceforge.net> > wrote: > On Nov 5, 2023, at 13:08, Pino Zollo via wsjt-devel > mailto:wsjt-devel@lists.sourceforge.net> > > wrote: > > Just an idea: > > When in Hound mode the DX station should call as: > > CQH DX0CALL GRID > > or > > CH DX0CALL GRID But why? He should only be hound if he is on his published frequency (which you can determine yourself), and he should never be in hound mode if he is in the normal FT frequency segment. Gary - AG0N ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net <mailto: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] CQ Hound mode
I believe he meant Fox. CQF I like that idea. It would differentiate between F/H and MSHV. But this all assumes the DX stops and calls CQ ever once in a while. -Scott AA5AM On Sun, Nov 5, 2023 at 2:38 PM Gary McDuffie via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > > > > On Nov 5, 2023, at 13:08, Pino Zollo via wsjt-devel < > wsjt-devel@lists.sourceforge.net> wrote: > > > > Just an idea: > > > > When in Hound mode the DX station should call as: > > > > CQH DX0CALL GRID > > > > or > > > > CH DX0CALL GRID > > But why? He should only be hound if he is on his published frequency > (which you can determine yourself), and he should never be in hound mode if > he is in the normal FT frequency segment. > > Gary - AG0N > > ___ > 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] CQ Hound mode
He would also be the fox if he's calling CQ, not one of the hounds. 73 Fred K3FRK On Sun, Nov 5, 2023 at 2:38 PM Gary McDuffie via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > > > > On Nov 5, 2023, at 13:08, Pino Zollo via wsjt-devel < > wsjt-devel@lists.sourceforge.net> wrote: > > > > Just an idea: > > > > When in Hound mode the DX station should call as: > > > > CQH DX0CALL GRID > > > > or > > > > CH DX0CALL GRID > > But why? He should only be hound if he is on his published frequency > (which you can determine yourself), and he should never be in hound mode if > he is in the normal FT frequency segment. > > Gary - AG0N > > ___ > 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] CQ Hound mode
> On Nov 5, 2023, at 13:08, Pino Zollo via wsjt-devel > wrote: > > Just an idea: > > When in Hound mode the DX station should call as: > > CQH DX0CALL GRID > > or > > CH DX0CALL GRID But why? He should only be hound if he is on his published frequency (which you can determine yourself), and he should never be in hound mode if he is in the normal FT frequency segment. Gary - AG0N ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] CQ Hound mode
Just an idea: When in Hound mode the DX station should call as: CQH DX0CALL GRID or CH DX0CALL GRID best 73 Pino ZP4KFX ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
