Re: [wsjt-devel] TX Freq lockout
Interesting. I had only put in a Tx freq below 1000 to see if it was allowed and it stuck. But if I put in something under 200, as soon as I click outside the Tx box, it goes back to whatever was in there above 1000. Never did an Enable TX since it was not normal to do so. Just tried it and yes, it does shift up to something over 1000. I see, the range 200-1000 displays a bit differently than under 200. 73's George - WB5JJJ 4 On Mon, Nov 16, 2020 at 12:31 AM 5p1kzx Michael <5p1...@gmail.com> wrote: > Hi George > > It's already there. If you are in Hound Mode and try to call FOX under > 1000 wsjt-x will move the TX over 1000 by it self. If one get a rpt from > the DXP wsjt-x will automatic jump to one of the DXP TX Slots and give your > rpt for max 3 times if no RR73 is received wsjt-x will jump to somewhere > between 600-1000 and keep sending rpt until it get RR73 or TX-Watch Dog > will be triggered. > > JTDX is working a bit different. With JTDX in Hound or HoundFC Mode one > can still TX Even/Odd and whereever you want too. If only in Hound Mode > (not HoundFC) JTDX will keep the same TX-slot during the QSO. > > One can water the horse but not force it to drink > > 73 de Michael 5p1kzx > > > Den 16-11-2020 kl. 06:46 skrev WB5JJJ: > > This was meant for HOUND mode only. If they are not using HOUND, then > they should not be calling the DXP when he's operating in F/H mode. > Defeats the purpose of F/H and only confuses the issue. > > 73's > George - WB5JJJ > > > 4 > > > On Sun, Nov 15, 2020 at 11:32 PM Reino Talarmo > wrote: > >> Hi George, >> >> There is a minor problem with your lockout proposal as that operator may >> not have used HOUND mode at all! >> >> 73, Reino OH3mA >> >> >> >> *From:* WB5JJJ [mailto:wb5...@gmail.com] >> *Sent:* 16. marraskuuta 2020 0:45 >> *To:* WSJT software development >> *Subject:* [wsjt-devel] TX Freq lockout >> >> >> >> With the 7Q7 being the first major DXP since early in the year, there are >> a lot of "new" hams to F/H that don't read the information available. They >> are hoping to "cut in line" by TXing initially below 1000, and even on the >> DXP calling frequency, with their R-xx report. This causes tons of QRM and >> bad feelings toward these LID's. >> >> >> >> Can we get a Tx lockout to the selector, so entering anything below 1000 >> (similar to selecting 100) on the HOUND side of things will, at least stop >> this in its tracks and still allow the FOX to move the HOUND to 300-900 for >> the R-xx report? Also perhaps lockout Tx3 as well. These items would sure >> help educate those users very quickly on procedures for the mode. >> >> >> >> Just as a comical observation, the other day I watched a guy call and >> call with his R-xx report on the DXP calling frequency. I never saw him >> above 1000 calling with his grid square. Someone "became" the FOX (to me a >> +05 vs a -17) and gave him a signal report to get rid of him. Illegal, >> without a doubt, but it worked. I suspect that in the future, he will >> continue the same method since it "worked" once. Now he's looking for a >> QSL -- good luck on that one. >> >> >> >> 73's >> >> George - WB5JJJ >> >> >> >> >> >> 4 >> ___ >> wsjt-devel mailing list >> wsjt-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wsjt-devel >> > > > ___ > wsjt-devel mailing > listwsjt-devel@lists.sourceforge.nethttps://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] TX Freq lockout
Hi George
It's already there. If you are in Hound Mode and try to call FOX under
1000 wsjt-x will move the TX over 1000 by it self. If one get a rpt from
the DXP wsjt-x will automatic jump to one of the DXP TX Slots and give
your rpt for max 3 times if no RR73 is received wsjt-x will jump to
somewhere between 600-1000 and keep sending rpt until it get RR73 or
TX-Watch Dog will be triggered.
JTDX is working a bit different. With JTDX in Hound or HoundFC Mode
one can still TX Even/Odd and whereever you want too. If only in Hound
Mode (not HoundFC) JTDX will keep the same TX-slot during the QSO.
One can water the horse but not force it to drink
73 de Michael 5p1kzx
Den 16-11-2020 kl. 06:46 skrev WB5JJJ:
This was meant for HOUND mode only. If they are not using HOUND, then
they should not be calling the DXP when he's operating in F/H mode.
Defeats the purpose of F/H and only confuses the issue.
73's
George - WB5JJJ
4
On Sun, Nov 15, 2020 at 11:32 PM Reino Talarmo
mailto:reino.tala...@kolumbus.fi>> wrote:
Hi George,
There is a minor problem with your lockout proposal as that
operator may not have used HOUND mode at all!
73, Reino OH3mA
*From:*WB5JJJ [mailto:wb5...@gmail.com <mailto:wb5...@gmail.com>]
*Sent:* 16. marraskuuta 2020 0:45
*To:* WSJT software development mailto:wsjt-devel@lists.sourceforge.net>>
*Subject:* [wsjt-devel] TX Freq lockout
With the 7Q7 being the first major DXP since early in the year,
there are a lot of "new" hams to F/H that don't read the
information available. They are hoping to "cut in line" by TXing
initially below 1000, and even on the DXP calling frequency, with
their R-xx report. This causes tons of QRM and bad feelings
toward these LID's.
Can we get a Tx lockout to the selector, so entering anything
below 1000 (similar to selecting 100) on the HOUND side of things
will, at least stop this in its tracks and still allow the FOX to
move the HOUND to 300-900 for the R-xx report? Also perhaps
lockout Tx3 as well. These items would sure help educate those
users very quickly on procedures for the mode.
Just as a comical observation, the other day I watched a guy call
and call with his R-xx report on the DXP calling frequency. I
never saw him above 1000 calling with his grid square. Someone
"became" the FOX (to me a +05 vs a -17) and gave him a signal
report to get rid of him. Illegal, without a doubt, but it
worked. I suspect that in the future, he will continue the same
method since it "worked" once. Now he's looking for a QSL -- good
luck on that one.
73's
George - WB5JJJ
4
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
<mailto:wsjt-devel@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
<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] TX Freq lockout
This was meant for HOUND mode only. If they are not using HOUND, then they should not be calling the DXP when he's operating in F/H mode. Defeats the purpose of F/H and only confuses the issue. 73's George - WB5JJJ 4 On Sun, Nov 15, 2020 at 11:32 PM Reino Talarmo wrote: > Hi George, > > There is a minor problem with your lockout proposal as that operator may > not have used HOUND mode at all! > > 73, Reino OH3mA > > > > *From:* WB5JJJ [mailto:wb5...@gmail.com] > *Sent:* 16. marraskuuta 2020 0:45 > *To:* WSJT software development > *Subject:* [wsjt-devel] TX Freq lockout > > > > With the 7Q7 being the first major DXP since early in the year, there are > a lot of "new" hams to F/H that don't read the information available. They > are hoping to "cut in line" by TXing initially below 1000, and even on the > DXP calling frequency, with their R-xx report. This causes tons of QRM and > bad feelings toward these LID's. > > > > Can we get a Tx lockout to the selector, so entering anything below 1000 > (similar to selecting 100) on the HOUND side of things will, at least stop > this in its tracks and still allow the FOX to move the HOUND to 300-900 for > the R-xx report? Also perhaps lockout Tx3 as well. These items would sure > help educate those users very quickly on procedures for the mode. > > > > Just as a comical observation, the other day I watched a guy call and call > with his R-xx report on the DXP calling frequency. I never saw him above > 1000 calling with his grid square. Someone "became" the FOX (to me a +05 > vs a -17) and gave him a signal report to get rid of him. Illegal, without > a doubt, but it worked. I suspect that in the future, he will continue the > same method since it "worked" once. Now he's looking for a QSL -- good > luck on that one. > > > > 73's > > George - WB5JJJ > > > > > > 4 > ___ > 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] TX Freq lockout
Hi George, There is a minor problem with your lockout proposal as that operator may not have used HOUND mode at all! 73, Reino OH3mA From: WB5JJJ [mailto:wb5...@gmail.com] Sent: 16. marraskuuta 2020 0:45 To: WSJT software development Subject: [wsjt-devel] TX Freq lockout With the 7Q7 being the first major DXP since early in the year, there are a lot of "new" hams to F/H that don't read the information available. They are hoping to "cut in line" by TXing initially below 1000, and even on the DXP calling frequency, with their R-xx report. This causes tons of QRM and bad feelings toward these LID's. Can we get a Tx lockout to the selector, so entering anything below 1000 (similar to selecting 100) on the HOUND side of things will, at least stop this in its tracks and still allow the FOX to move the HOUND to 300-900 for the R-xx report? Also perhaps lockout Tx3 as well. These items would sure help educate those users very quickly on procedures for the mode. Just as a comical observation, the other day I watched a guy call and call with his R-xx report on the DXP calling frequency. I never saw him above 1000 calling with his grid square. Someone "became" the FOX (to me a +05 vs a -17) and gave him a signal report to get rid of him. Illegal, without a doubt, but it worked. I suspect that in the future, he will continue the same method since it "worked" once. Now he's looking for a QSL -- good luck on that one. 73's George - WB5JJJ 4 ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] TX Freq lockout
With the 7Q7 being the first major DXP since early in the year, there are a lot of "new" hams to F/H that don't read the information available. They are hoping to "cut in line" by TXing initially below 1000, and even on the DXP calling frequency, with their R-xx report. This causes tons of QRM and bad feelings toward these LID's. Can we get a Tx lockout to the selector, so entering anything below 1000 (similar to selecting 100) on the HOUND side of things will, at least stop this in its tracks and still allow the FOX to move the HOUND to 300-900 for the R-xx report? Also perhaps lockout Tx3 as well. These items would sure help educate those users very quickly on procedures for the mode. Just as a comical observation, the other day I watched a guy call and call with his R-xx report on the DXP calling frequency. I never saw him above 1000 calling with his grid square. Someone "became" the FOX (to me a +05 vs a -17) and gave him a signal report to get rid of him. Illegal, without a doubt, but it worked. I suspect that in the future, he will continue the same method since it "worked" once. Now he's looking for a QSL -- good luck on that one. 73's George - WB5JJJ 4 ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
