Hi Tom,
I defaulted to 50.260 because that was the default in my WSJT-X install and I
am in region 2. So that may be a problem as I do not receive indication of
regions.
However, as far as noticing it, QLog announces both the band and the exact
frequency you are operating on as soon as WSJT-X switches to that
band/frequency.
QLog announce the Configuration, Mode and Frequency when any one of those items
changes.It will announce who you are replying to including their call sig,
country and grid and the SNR your are reporting, who is replying to you CQ, the
exchanges/SNR whether you are transmitting or receiving. If you are waiting for
/receive an RRR, or RR73, if you are sending and/or receiving a 73 and finally
that you are logging the QSO locally and optionally to QRZ, Clublog and/or EQSL
73,
Sam W2JDB
-----Original Message-----
From: tom <t...@tkrh.co.uk>
To: Sam W2JDB <w2...@aol.com>; WSJT software development
<wsjt-devel@lists.sourceforge.net>
Sent: Fri, Sep 4, 2020 9:23 am
Subject: Re: [wsjt-devel] Bug when using MSK144?
Sam
Just a quick observation
You say you are defaulting QLog to 50.260 - Region 1 the default MSK144 freq is
50.280
If you are defaulting esp with a visually impaired operator, they may not
notice this and wonder why no QSO’s.
Would you not be better to look at the frequencies setup in wsjt-x and default
to what has been set by the user?
Regards
Tom
--
73
Tom
GM8MJV (IO85)
On 2 Sep 2020, at 16:40, Sam W2JDB via wsjt-devel
<wsjt-devel@lists.sourceforge.net> wrote:
Hi Bill,
Checked with the UDP_Daemon and the mode change was being captured.
I found the problem in my program and it is now working correctly. As soon as
QLog detects a mode change to MSK144 and the working frequency in WSJT-X is
below 6M, QLog changes the frequency in the band box 50.260 which then triggers
the CAT command to the rig.
Thank you again for all your help. As an FYI, Georgian (M0EBP) is now setup
with WSJT-X and QLog, I also express the opinion that it would be advantageous
to have CAT control with the TS200.
Helping multiple blind hams setup WSJT-X, I found that in cases where they are
not using multiple dedicated sound cards for their Audio software such as NDVA
or JAWS, I need to change the sound cardproperties and disable Exclusive
Control of the sound card.
73,
Sam W2JDB
-----Original Message-----
From: Bill Somerville <g4...@classdesign.com>
To: wsjt-devel@lists.sourceforge.net
Sent: Wed, Sep 2, 2020 10:17 am
Subject: Re: [wsjt-devel] Bug when using MSK144?
Hi Sam,
I am unable to reproduce that behaviour. Here's the output from the
udp_daemon tool from your first scenario:
C:\build>\test-install\wsjtx-dev\Release64\bin\udp_daemon.exe -g 239.255.0.1
Discovered WSJT-X instance: WSJT-X - test v2.3.0-devel (fcc5df)
WSJT-X - test: Dial frequency changed to 3574000
WSJT-X - test: Mode changed to MSK144
WSJT-X - test: Dial frequency changed to 50260000
WSJT-X - test: Mode changed to FT8
WSJT-X - test: Dial frequency changed to 50313000
WSJT-X - test: Dial frequency changed to 1840000
WSJT-X - test: Mode changed to MSK144
Continuing with your second scenario I see: Removed WSJT-X instance: WSJT-X
- test
Discovered WSJT-X instance: WSJT-X - test v2.3.0-devel (fcc5df)
WSJT-X - test: Mode changed to JT9A
WSJT-X - test: Mode changed to MSK144
WSJT-X - test: Dial frequency changed to 1840000
WSJT-X - test: Dial frequency changed to 145000000
WSJT-X - test: Dial frequency changed to 1840000
WSJT-X - test: Mode changed to FT8
WSJT-X - test: Dial frequency changed to 3573000
WSJT-X - test: Mode changed to MSK144
All the mode and frequency changes are faithfully reported by UDP status
messages.
73
Bill
G4WJS.
On 02/09/2020 14:51, Sam W2JDB via wsjt-devel wrote:
Hi Bill,
I have updated and tested my program and I can programmatically change the
value in the band box to 50.260 and thereby have WSJT-X issue the CAT command
to the radio and switch to the correct frequency.
However, I ran into a problem where if I then switch back to FT8, drop down
to a low HF band and then switch again to MSK144, there is no indication being
given through UDP status message that the mode was changed. If I then shutdown
WSJT-X while still in MSK144, then start it back up, switch to FT8 move to a
lower HF band and then switch back to MSK144, there is no UDP Traffic
indicating a mode change. If on the other hand, I switch to FT8 and to a lower
HF Band, before shutting down WSJT-X, start it up again, switch to MSK144, I do
received the UDP Status message indicating a mode change. It seems that the
mode change indication happens only once if you are not on the appropriate
MSK144 frequency. Anyway, I hope this information helps.
73,
Sam W2JDB
-----Original Message-----
From: Sam W2JDB via wsjt-devel mailto:wsjt-devel@lists.sourceforge.net
To: wsjt-devel@lists.sourceforge.net mailto:wsjt-devel@lists.sourceforge.net
Cc: Sam W2JDB mailto:w2...@aol.com
Sent: Wed, Sep 2, 2020 7:43 am
Subject: Re: [wsjt-devel] Bug when using MSK144?
Hi Bill,
Thank you very much for this thoughtful explanation regarding band changes in
WSJT-X. As I mentioned, I instructed Rich to update their document to change to
6M before selecting MSK144. I will update my program so that if it detects a
frequency lower than 6M, my program will update the frequency box.50.260
Thanks again.
73,
Sam W2JDB
_______________________________________________
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
