I know it is near the release of RC2, but I hope you will reconsider
removing the Lock TX=RX checkbox altogether. It seems that most run with
it on, and by calling offset, they end up moving to the caller's QRG
rather than staying put. With the importance of calling offset with FT8,
it makes th
back to JT65.
73
Charlie
_
From: Allan Downie [mailto:vk...@westnet.com.au]
Sent: 06 November 2016 06:51
To: WSJT software development
Subject: Re: [wsjt-devel] Lock Tx=Rx issue
Hi Charlie and all,
Many thanks for your reply and all comments noted.
I did as you suggested, I
Hi Charlie and all,
Many thanks for your reply and all comments noted.
I did as you suggested, I edited the WSJT-X.ini file to change to
/LockTxFreq=*false*./ Interestingly, after editing and saving the .ini
file and confirming that indeed the edit has taken place, closing WSJT-X
and restarti
Hi Allan
I can reproduce the behaviour you see.
I edited one line in [common] of the .ini file as follows:
LockTxFreq=false
then saved the file and closed WSJT-X.
After restarting it, the tickbox appeared checked, and tx/rx frequencies
followed each other.
Unchecking the box made them indepen
Hi Joe and all,
I originally started this enquiry on Yahoo Groups 'wsjtgroup' and very
kindly received a possible solution from Joe K1JT. However I seem to be
having great trouble with Yahoo, so I am continuing on here. I hope that
is okay.
My Original posting was something like: -
/I curre
Uncheck "Enable VHF/UHF/Microwave Features" in the settings menu (General tab)
and the lock option will return.
73,
Jim S.
N2ADV
> On Oct 16, 2016, at 11:29 AM, David Tiller
> wrote:
>
> All,
>
> I noticed that sometime between r6353 and r7028 the option "Lock RX=TX" seems
> permanently
All,
I noticed that sometime between r6353 and r7028 the option "Lock RX=TX" seems
permanently greyed out in all the modes that support it (JTx, ISCAT, etc). It's
still greyed out in r7184. Was this a design choice, or is it a bug?
I don't use hamlib to control my rig, so I have the CAT control
Is it the intent to force Tx=Rx when double-clicking a QSO...ignoring the check
box for it? Not something you want for EME, is it?
The last else clause in this section of code seems pretty useless.
if(!m_bFastMode) { // Don't change Tx freq if in a fast mode; also not if a
station is callin
Disable VHF/UHF/Microwave Features and the Lock TX/RX functionality returns.
> On Aug 8, 2016, at 8:21 PM, Pino Zollo wrote:
>
> Version 1.7.0 rc1 Linux mode JT9+JT65
>
> Lock TX=RX is gray ...can not be disabled, while TX<-RX and RX<-TX are
> black...but useless ..
>
> Whats the problem
Version 1.7.0 rc1 Linux mode JT9+JT65
Lock TX=RX is gray ...can not be disabled, while TX<-RX and RX<-TX are
black...but useless ..
Whats the problem ?
73
Pino ZP4KFX
--
What NetFlow Analyzer can do for you? Monitor
10 matches
Mail list logo
