I had the following selected for my wsjtx v2.0 rc5 settings:
Radio tab (item selected)
- Cat
- Data/Pkg
- Rig
- Baud rate 38400
General tab
- Behaviour (item selected)
- Double-click on call sets TX enable
- Disable Tx after sending 73
- Allow Tx frequency changes while transmitting
I used a Yaesu FT-450D, signalink (there was some minimal delay about 2
tick marks away from the full counter clock wise setting - thanks Bill for
the suggestion, it is now at minimal delay), Ubuntu 16.04.
The only change I made during the contest when I noticed my Transmit marker
wasn't moving was to enable the "Allow Tx..." setting. After that, wsjtx
behaved as I hoped and the tx moved as I wanted...i.e., it moved :-).
Bill, I am not positive about whether the FT-450D, via cat control, can qsy
during Tx, but I can certainly change the freq of VFO B while transmitting
using the big tuning knob. So the Rig will allow it and likely via cat
control as well. You make a good point about a rig's ability to do this.
I took it for granted and perhaps got lucky that this Yaesu allows qsy
during transmit. I have an Elecraft KX3 as well and it seems to behave
similarly when it comes to qsy'nig during xmit.
Anyway, I am happy about the way wsjtx works with my rigs.
regards,
Brian
VE3IBW
On Mon, Dec 3, 2018 at 5:24 PM Jim Shorney <[email protected]> wrote:
>
> This was happening to me during RX periods. I do have the option mentioned
> below checked, and am not using CAT.
>
> 73
>
> -Jim
> NU0C
>
> On Mon, 3 Dec 2018 08:03:38 -0500
> Brian Waterworth <[email protected]> wrote:
>
> > I had the same issue as you describe and recalled that I had not selected
> > the "Allow TX Frequency changes while transmitting" setting on the
> > Settings...General tab. Checking this setting solved the first problem
> > highlighted in this thread.
> >
> > regards,
> > Brian
> > VE3IBW
> >
> > On Sun, Dec 2, 2018 at 10:07 PM Paul Kube <[email protected]> wrote:
> >
> > > Me three :).
> > >
> > > Well described by Charlie and Jim.
> > >
> > > 73, Paul K6PO
> > >
> > > On Sun, Dec 2, 2018 at 4:48 PM Jim Shorney <[email protected]>
> wrote:
> > >
> > >>
> > >> Thanks Charlie! Nice to know it isn't just me... :)
> > >>
> > >> 73
> > >>
> > >> -Jim
> > >> NU0C
> > >>
> > >>
> > >> On Sun, 2 Dec 2018 21:20:39 -0000
> > >> [email protected] wrote:
> > >>
> > >> > Hi Jim
> > >> >
> > >> > Yes, we experienced the same behaviour where clicking an earlier
> message
> > >> > when bailing on a QSO ended up splitting the TX and RX frequencies.
> > >> >
> > >> > We also found it labour intensive to have to select TX4 and enable
> TX
> > >> > manually when the calling station sent R report again, clearly not
> > >> having
> > >> > received our initial RR73 message. On some occasions we needed to
> do
> > >> this
> > >> > several times during more difficult QSOs.
> > >> >
> > >> > 73
> > >> >
> > >> > Charlie G3WDG
> > >> > >
> > >> > > I have noticed a specific scenario that has happened several
> times
> > >> during
> > >> > > the contest. This happens when I have called a CQing station two
> or
> > >> three
> > >> > > times with no reply and I bail and go call another. Then I see
> the
> > >> first
> > >> > > station replying to me with TX3 while I am calling the new one.
> So I
> > >> bail
> > >> > > on that call and try to go back to work the first station with a
> > >> > > double-click on the message. This moves the RX back to the first
> > >> station's
> > >> > > frequency, but not the TX. It is acting like Hold TX is on, but
> it is
> > >> not.
> > >> > > I tried toggling Hold TX. and shift-doubleclick, but the TX
> refuses to
> > >> > > move until I use one those "confusing" arrows. (j/k, I'm not
> > >> confused -
> > >> > > much).
> > >> > >
> > >> > > Maybe I'm just a bad op. I know we are supposed to offset our
> signals
> > >> and
> > >> > > call split, but that doesn't seem to be happening. At any rate,
> it
> > >> seems
> > >> > > like the TX should move in this scenario, otherwise I end up
> QRMing
> > >> the
> > >> > > second op until I remember where I am.
> > >> > >
> > >> > > While I am at it, it would be nice if, when calling running
> station,
> > >> Tx4
> > >> > > could me made sticky until the final 73 is received. Leave TX
> disable
> > >> > > alone, just let Tx4 stay selected in case it needs to be re-sent.
> One
> > >> less
> > >> > > thing to have to scramble for when things don't go as planned.
> > >> > >
> > >> > > Anyway, 70 contacts so far before I needed to take a break.
> > >> > >
> > >> > > 73
> > >> > >
> > >> > > -Jim
> > >> > > NU0C
> > >> > >
> > >> > >
> > >> > > --
> > >> > > The universe we're in will reach absolute zero in three hours.
> Safe is
> > >> > > relative. - Idris, "The Doctor's Wife"
> > >>
> > >>
> > >> _______________________________________________
> > >> wsjt-devel mailing list
> > >> [email protected]
> > >> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> > >>
> > > _______________________________________________
> > > wsjt-devel mailing list
> > > [email protected]
> > > https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> > >
>
>
>
> _______________________________________________
> wsjt-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
