Date   

locked Re: wsjtx V 1.8 for Linux : Answer #WSJTX_config

Carl Andreasen
 

I have found the answer.
My FT-100D has not been used much for a long time and I have had to refer to the manual to relearn how to use the features.
I discovered it was in the split-mode, and the "B" VFO was in the VHF frequencies.
I had to disable the "split" function so I transmit on the same frequency I am listening on, no more problem. WSJTX Linux version, now works with the FT-100D.


locked submodes

Fairchild, William
 

Feature suggestion: Implement the JT9 submodes JT9-2, JT9-5, JT9-10, and JT9-30. This could be very helpful for say, stations trying to complete 160 meter WAS. (The Version 1.0 User's Guide had an intriguing table showing a -42 db S/N threshold for JT9-30.) Admittedly these modes require patience from two operators at a time, and schedules perhaps, but the possibilities beckon.


73, 

Bill, wo2v


locked wsjtx V 1.8 for Linux #WSJTX_config

Carl Andreasen
 

I have wsjtx V1.8 installed on my Linux machine which is running Linux Mint version 18.2.
With everything configured and connected to my FT-100D radio which is using a SignaLink interface, everything seems perfect. CAT works for PTT and the frequency display both reads the correct frequency, or is set by the program.
The configuration does not have a FT-100D but it does have the FT-100.
The problem is when I go to transmit, be it the tune button or an actual transmission, it almost instantly crashes wsjtx. Apparently the CAT tries to poll the radio during transmit and the radio won't allow the function to work and the program crashes.

Anybody know about this? Or better yet, a solution?


locked Re: RX=TX #FT8

jgmags2000 <jgmags2000@...>
 

Thank You again Bill.. installed it O.K. and works perfectly. I hope I don't need to ask some simple questions.

73, John


locked Re: RX=TX #FT8

Bill Somerville
 

On 30/10/2017 20:53, jgmags2000 via Groups.Io wrote:
Thanks Bill. I have no idea how to install the GA release. From what I find it is for Linux. Is that right? I guess I quite do not understand , sorry.
73, John
Hi John,

GA stands for General Availability, i.e. v1.8.0 is no longer a beta release. Download and install the latest version from the project web site.

https://physics.princeton.edu/pulsar/k1jt/wsjtx.html

73
Bill
G4WJS.


locked Re: RX=TX #FT8

jgmags2000 <jgmags2000@...>
 

Thanks Bill. I have no idea how to install the GA release. From what I find it is for Linux. Is that right? I guess I quite do not understand , sorry.
73, John


locked Re: RX=TX #FT8

Bill Somerville
 

On 30/10/2017 19:48, jgmags2000 via Groups.Io wrote:
I have 1.8.0-rc3.. there is no RX=TX box available. Have to adjust TX after changing RX
73, John KJ1J
Hi John,

the v1.8.0 GA release is now out, you should probably upgrade from the release candidate version.

CTRL+click on he waterfall to set both Tx and Rx offset to a free frequency before calling CQ. If you don't like using two hands then you also have the option to right-click on the waterfall and that brings up a button (actually a menu of buttons but there's only one at the moment) to set both Tx and Rx to the original click mouse cursor position.

73
Bill
G4WJS.


locked RX=TX #FT8

jgmags2000 <jgmags2000@...>
 

I have 1.8.0-rc3.. there is no RX=TX box available. Have to adjust TX after changing RX
73, John KJ1J


locked WSJT-X 1.8.0 GA Release via Launchpad PPA #NewUser

Greg Beam, KI7MT <ki7mt01@...>
 

Hello All,

 

Following Joe's WSJT-X 1.8.0 GA Release message, I've updated my Lauchpad PPA’s

(WSJTX and WSJTX-NEXT) as released by the WSJT Development Team. Both

packages are sitting at the tagged revision number r8193.

 

Supported Distributions:

* Trusty, Xenial, Zesty

* Supported Arch: amd64, i386, arm64, armhf, ppc64el

 

GA Release

Installation / Upgrade Information:

https://launchpad.net/~ki7mt/+archive/ubuntu/wsjtx

 

Development

Installation / Upgrade Information:

https://launchpad.net/~ki7mt/+archive/ubuntu/wsjtx-next

 

73's

Greg, KI7MT

 


locked Personalized 73 Bug in rc2 & rc3 FT8 Auto Sequence #FT8

Gary - AC6EG <gdefeyter@...>
 

For years, I've been using JTAlert macros to send personalized 73 text messages when operating JT65 or JT9.  I recently had a FT8 QSO with Bob Hensy, K4VBM, in which I sent TU BOB GL 73.  The auto sequence response I got back from him was BOB K4VBM 73.  I had seen several other responses like this, NAME CALLSIGN 73, and thought they were unusual, but didn't realize what was happening until Bob sent me an email warning that there was a bug in WSJT-X.  Bob reported this in the Sourceforge mailing list where it has not gotten much attention, but it should have.  Here is part of what he reported:
*171013_181900  Transmitting 21.074 MHz  FT8:  CQ K4VBM EM73 *
*181915 -12  0.1  901 ~  K4VBM AC6EG CM94 *
*171013_181930  Transmitting 21.074 MHz  FT8:  AC6EG K4VBM -12 *
*181945 -16  0.1  901 ~  K4VBM AC6EG R-07 *
*171013_182000  Transmitting 21.074 MHz  FT8:  AC6EG K4VBM RRR*
*182015 -15  0.1  900 ~  TU BOB GL 73*
*1**71013_182030  Transmitting 21.074 MHz  FT8:  BOB K4VBM 73

*As you can see above, my partner sent me a free text message of "TU BOB GL 73",
and the autopilot somehow decided to change his call sign instead to be
"BOB" from that message.  I will also tell you that the main wsjtx.adi
log file ended up having "BOB' as the call sign logged instead of the AC6EG call
sign used at the start, as well as a missing Grid among other things.

The net result was that I had to go and manually fix the wsjtx.adi file
which I have already done, so I do not have the exact data to share for
that - only what I can remember.
I realized that maybe I should report this occurrence to the forum.
Hope this info is enough to re-create the problem.
Love the software and the new FT-8 mode! Thanks, Joe, for creating
things that makes this hobby so much more enjoyable!
Bob - K4VBM

I suspect the reason Bob's post got little attention is that FT8 QSO's move so quickly that few people are attempting to use personalized 73 text, but with the help of JTAlert I was delighted to find that is quite easy to do.  I had seen others respond to my 73 with Their-Name Their-Call 73, and thought it was a little odd, but didn't really think too much about it until I heard from Bob.  I will of course refrain from using personalized 73 text going forward until this bug is fixed and want to advise other FT8 operators to be careful about altering text messages when using auto sequence.

Gary - AC6EG
 


locked WSJTX RC3 for Ubuntu via Launchpad PPA #NewUser

Greg Beam, KI7MT <ki7mt01@...>
 

Hello All,

Following Joe's WSJT-X RC3 message yesterday, I've updated my Lauchpad PPA
(WSJTX-NEXT) to RC3 as released by the WSJT Development Team.

Supported Distributions:
* Trusty, Xenial, Zesty
* Supported Arch: amd64, i386, arm64, armhf, ppc64el

Installation / Upgrade Information:
https://launchpad.net/~ki7mt/+archive/ubuntu/wsjtx-next

73's
Greg, KI7MT


locked Re: WSJT-X-rc2: Generate Std Msgs button doesn't work #WSJTX_config

Gary - AC6EG <gdefeyter@...>
 

Thanks Bill
I didn't realize I could reset T5 to the default 73 by simply double clicking the T5 button.
That might be a handy feature to add to the T6 button. I'm finding that if I edit the CQ message by adding DX or a state destination code between CQ and my callsign, the only way I've found to restore a standard CQ message is to manually edit the message.  If I highlight the altered T6 message, hit delete to clear it, and click the Generate Std Msgs button to restore it, the program crashes. 

73 de Gary - AC6EG


locked Re: WSJT-X-rc2: Generate Std Msgs button doesn't work #WSJTX_config

Bill Somerville
 

On 09/10/2017 20:40, Gary - AC6EG wrote:
RC2 is awesome! I'm finding, though, that the Generate Std Msgs button doesn't work as expected.  I like to use JT-Alert Macros to send a personalized 73  ( ie.  TU BOB GL 73 )  Sometimes this confuses the other operator and he sends repeated RRR's.  When that happens I used to be able to click the Generate Std Msgs button and it would instantly replace the macro with a regular YOURCALL MYCALL 73.  I'd send that and everybody would be happy.  But now if I click on Generate Std Msgs nothing happens. I could probably create a workaround with another macro that would quickly generate a standard 73 message, but it would probably be better to fix whatever is wrong with the GSM button. It is possible that is a mode specific problem. I've only seen this when operating FT8.
Many thanks to you who are developing this fantastic software!
Hi Gary,

what you describe is a feature, not a defect. There are many cases where you might need to re-send a custom signoff message even after you have logged a QSO and cleared the DX call and messages, because of this WSJT-X now preserves the Tx5 message until a new DX Call is entered (or picked up by double clicking or the FT8 auto-sequencer). If you wish to reset the Tx5 message then double-click the Tx5 next or send now button to the right of the message.

As an aside, in general WSJT-X will take a free text message containing the word 73 as equivalent to the standard form 73 message, so try and include the word 73 in your custom signoff messages. The latest v1.8.0 versions also accept the word RR73 in a grid format message as equivalent to a standard form 73 message.

73
Bill
G4WJS.


locked WSJT-X-rc2: Generate Std Msgs button doesn't work #WSJTX_config

Gary - AC6EG <gdefeyter@...>
 

RC2 is awesome!  I'm finding, though, that the Generate Std Msgs button doesn't work as expected.  I like to use JT-Alert Macros to send a personalized 73  ( ie.  TU BOB GL 73 )  Sometimes this confuses the other operator and he sends repeated RRR's.  When that happens I used to be able to click the Generate Std Msgs button and it would instantly replace the macro with a regular YOURCALL MYCALL 73.  I'd send that and everybody would be happy.  But now if I click on Generate Std Msgs nothing happens. I could probably create a workaround with another macro that would quickly generate a standard 73 message, but it would probably be better to fix whatever is wrong with the GSM button. It is possible that is a mode specific problem. I've only seen this when operating FT8.
Many thanks to you who are developing this fantastic software!

Gary - AC6EG  


locked Re: WSJT-X v1.8.0 rc2 8069 Issue #NewUser #GeneralGroupInfo

Eddy van Keulen
 

I think I know what you’re talking about.  I like to do that too; not wait until the other station calls CQ again but jump into the gap after the 73 of the previous contact. I’ve had a lot of JP stations do it to me too.

 

RC2 has a new feature that I like very much. When you answer the CQ of a station but that station didn’t hear you and calls someone else, RC2 will turn off your transmit.. JT65 gives you enough time so you can manually cancel the transmit before it actually starts transmitting but FT8 is too fast. It starts transmitting and then you end up breaking it off a few seconds in. RC2 prevents this unwanted transmission. An unfortunate side effect is that when you want to pounce after the station’s 73 to someone else, it will do the same thing. It is detected as a transmission to someone else and RC2 turns off your transmit. Knowing it will do that, I will hover the mouse over the transmit button and quickly turn it on again. Hopefully the software developers catch on to this side effect and fix it to only disable the transmit when answering a CQ, not when you’re pouncing a 73. 😉

 

Eddy – W6EDY

 

 

Sent from Mail for Windows 10

 

From: kk5aa_fred via Groups.Io
Sent: Monday, September 18, 2017 1:31 PM
To: WSJTX@groups.io
Subject: [WSJTX] WSJT-X v1.8.0 rc2 8069 Issue #new #new #GeneralGroupInfo

 

I ran into this last week and asked about it on the Facebook group but no one seemed to understand what I was talking about.

I personally like to hunt and pounce. I'll spot a station I want to work and I'll double click their call to get things set up and ready to roll. When I spot his contact sending 73, I figure he is about to send 73 and leave a gap. So, when he begins his transmission, I will select transmit so when he finishes, I'll immediately call him. Ezcept, with RC2 8069, the program shuts off transmit as soon as he sends 73!

RC1 does not do this but I like the sensitivity of RC2 and really would rather not roll back to it. I did roll back for a time but RC2 is so much better, I went back to it..

Does anyone have a clue about what is going on here and if there is aby way for me to fix this?

Fred - KK5AA
EM25xh

 


locked Re: Split Operations #GeneralGroupInfo

Bill Engel K5DHY
 

Check: File -> Settings. On the radio tab check the "Split Operation" section.

It keeps your transmit audio around 1500 Hz which allows you to work the edges of the band and keeps the second audio harmonic outside the transmit bandpass in case of overmod.

Bill

On 9/20/2017 4:47 PM, Chuck Roth via Groups.Io wrote:
Why does Wsjtx set my rig to split operations upon transmit? For example 14.074.15 to 14.073.15
Chuck
KB7OGE


locked Split Operations #GeneralGroupInfo

Chuck Roth <kb7oge@...>
 

Why does Wsjtx set my rig to split operations upon transmit? For example 14.074.15 to 14.073.15

Chuck
KB7OGE


locked Re: WSJT-X v1.8.0 rc2 8069 Issue #NewUser #GeneralGroupInfo

kk5aa_fred
 

But it is shutting off MY transmit when HE sends 73...

Also noticed that if you double click on his call when he is calling CQ, it does not do this.
Only when you double click when he is talking to a contact. 

I don't think this is a setting I've gotten wrong, it is something in the program.

Fred - KK5AA
EM25xh


locked Re: WSJT-X v1.8.0 rc2 8069 Issue #NewUser #GeneralGroupInfo

Rory Sena
 

It's my understanding this is to speed up the QSO process when the station gets a 73 all the information for a valid QSO has been received.


locked WSJT-X v1.8.0 rc2 8069 Issue #NewUser #GeneralGroupInfo

kk5aa_fred
 

I ran into this last week and asked about it on the Facebook group but no one seemed to understand what I was talking about.

I personally like to hunt and pounce. I'll spot a station I want to work and I'll double click their call to get things set up and ready to roll. When I spot his contact sending 73, I figure he is about to send 73 and leave a gap. So, when he begins his transmission, I will select transmit so when he finishes, I'll immediately call him. Ezcept, with RC2 8069, the program shuts off transmit as soon as he sends 73!

RC1 does not do this but I like the sensitivity of RC2 and really would rather not roll back to it. I did roll back for a time but RC2 is so much better, I went back to it.

Does anyone have a clue about what is going on here and if there is aby way for me to fix this?

Fred - KK5AA
EM25xh