Hi.

The only way I can think of, is to launch things in sequence using a
Batch file (Windows) or shell script (Linux.)

Flrig can have multiple instances running, just change the localhost
network port they listen on in their own settings, and address each one
as needed from WSJTx.  Check the Flrig help files, you can invoke it to
pull settings from an alternate radio specific folder.

Should work.

73.

Dave G0WBX.


--
Created on and sent from a Unix like PC running and using free and open source software:

On 15/05/2020 13:10, Tom NS8K wrote:

Thanks Bill, old dog, new tricks for sure.

Thinking about this a little more, I can see where earlier operating procedures using RRR and leaving Tx5 after logging worked perfectly.  With the transition to RR73, Tx4 & Tx5 remaining would, in my opinion, be preferred because realizing what has happened, double-clicking, enabling transmit etc. might cause me to be too late and extend the QSO to another Tx/Rx cycle.  Just my thoughts, I'll be fine as it is too.

To the entire WSJT-X Team, you folks are modern pioneers in communications.  A notch below Marconi I suppose but right up there with some of the best.  Thank you.

73,
Tom - NS8K

Hi Tom,

if you check the "Settings->General->Double-click on call sets Tx enable" option then all you need do is double-click of the unexpectedly repeated message to you to generate the correct response *and* enable Tx.

73
Bill
G4WJS.

Thanks Bill, old dog, new tricks for sure.

Thinking about this a little more, I can see where earlier operating procedures using RRR and leaving Tx5 after logging worked perfectly.  With the transition to RR73, Tx4 & Tx5 remaining would, in my opinion, be preferred because realizing what has happened, double-clicking, enabling transmit etc. might cause me to be too late and extend the QSO to another Tx/Rx cycle.  Just my thoughts, I'll be fine as it is too.

To the entire WSJT-X Team, you folks are modern pioneers in communications.  A notch below Marconi I suppose but right up there with some of the best.  Thank you.

73,
Tom - NS8K

Been running the regular version of WSJT-X with JTAlert, does not give these dark green colors. JTAlert settings are unchanged. Hello Joe???

Could it be that during the decode sequences within the 15 second period, the dark green CQs represent the last decodes of each sequence? Now that I watch it closer that appears to be the case.  No idea why, and does not cause problems. I like this beta version...

yes I see the same thing on both 2 and 6m with strong local steady signals - i'm not sure that's not by design ?
--
jay ny2ny

On 15/05/2020 11:10, Fred, DH5FS wrote:

Same here Win XP doesn't work anymore, with the newest RC.

@development team: is there a need to stop support? Yes, we know about outdated OS'es :)

73 Fred

Hi Fred,

parts of WSJT-X, particularly the Qt framework we use for the GUI and other cross platform support have completely dropped support for Windows XP and Windows Vista. The only way we can continue to support these long obsolete and insecure operating system versions would be to use an old version of these essential parts of WSJT-X. There are two issues, firstly Qt for example cannot be obtained any more in a version that supports these old o/s versions, and secondly by using such an old version we deprive all the users with more up to date operating systems of all the defect  repairs and new features within them.

The alternative would be to support multiple versions of WSJT-X but remember we are a small team supporting many thousands of users and adding to our support load is not something we wish for. I would also be very uncomfortable with using tools that can no longer be obtained in at the required versions, just in case a development system needed to be rebuilt from scratch.

73
Bill
G4WJS.

Herb,

 

the Tx5 message is not cleared for that very reason.

 

73
Bill
G4WJS.

Bill,

I'm with Herb on this.  What I have experienced is I send RR73 which initiates the logging process.  If I complete the log, messages disappear and sometimes I will get a dreaded R xx on the next receive cycle.  Panic sets in and I scramble to get back an RR73.  I don't want to send 73 because that doesn't send an acknowledgment.  If I was on the other end, I'd consider it a failed contact.

I must be missing something here.  Maybe everyone waits until they have received a 73 before logging?  Tx4 and Tx5 would be the messages I'd need to remain with the way I operate.

73,
Tom - NS8K

Hi Tom,

you should get the required response by double-clicking the unexpected repeat of the R+report message to you.

73
Bill
G4WJS.

Same here Win XP doesn't work anymore, with the newest RC.

@development team: is there a need to stop support? Yes, we know about outdated OS'es :)

73 Fred

--

Herb,

 

the Tx5 message is not cleared for that very reason.

 

73
Bill
G4WJS.

Bill,

I'm with Herb on this.  What I have experienced is I send RR73 which initiates the logging process.  If I complete the log, messages disappear and sometimes I will get a dreaded R xx on the next receive cycle.  Panic sets in and I scramble to get back an RR73.  I don't want to send 73 because that doesn't send an acknowledgment.  If I was on the other end, I'd consider it a failed contact.

I must be missing something here.  Maybe everyone waits until they have received a 73 before logging?  Tx4 and Tx5 would be the messages I'd need to remain with the way I operate.

73,
Tom - NS8K

Dear All,

I have successfully setup two instances of WSJT-X and Flrig respectively for my IC-7300 and IC-9700, the reason I need to use Flrig instead of WSJT-X's direct cat control is I need to monitor the rigs, especially SWR, for remote operation via VNC viewer.

The problem I have now is I can not assign specific Flrig instance to specific WSJT-X instance, if I open two flrig and two WSJT-X instances, both of the WSJT-X would be associate with the first Flrig I opened.

Is there any possible solution?

Thank you.

De BU2EQ Willis

On 14/05/2020 02:37, JP Tucson, AZ wrote:

Ok, attached is what I got... fail...  hmmm, looks oddly familiar...

Next...

Hi John,

I am not sure if this will fix anything but can you do the following please.

In WSJT-X go to "Settings->Radio", check the "PTT Method->RTS" option, change the "PTT Method->Port" to COM7, and finally check the "PTT Method->CAT" option.

Try "Test CAT" and report back any error please?

73
Bill
G4WJS.

I suggest changing the Tune audio signal to a dual audio frequency from a single frequency, or add a second "Tune" dual audio frequency function so that the user can adjust the Pwr level while looking at the transmitter response on a scope.  The two audio frequencies need to be equal and need to be half the amplitude of the present Tune signal, and should be a few hundred Hertz apart and not harmonically related.  Many of us will be surprised how distorted our output is if the Pwr setting is too high.  Don't be a rock star and just crank it up to "11".
Dick, W9ZB

Sorry Bill.

I spent quite a bit of time on the N1MM site to find out what they did
as best I could.

I also thought that John (N7GHZ) had these issues originally with the
last "release" version, not just the new RC1, as I see he has confirmed.

Walter DK1BN's idea of using DXlab commander might be a viable stopgap,
if it gets things moving, could be a good test move anyway.

The TS440 (no 's') is listed, but from what Jon found out from Kenwood
they are one and the same anyway.

http://www.dxlabsuite.com/commander/

Cheers All.

Dave G0WBX.

--
Created on and sent from a Unix like PC running and using free and open source software:

I'm still using a laptop with XP. WSJTX works fine with the v2.1.0 24fcd1.  Do I understand correctly that the newest version will not work on XP?
Bob W1EQ

Thanks for the explanation Bill. Guess some of us are always in a rush LOL and I wanted to skip a transmission :)
I will go back to using the RRR for TX4

73
Frank

On 15/05/2020 00:16, Tom Carrubba KA2D wrote:

Also, If another station calls K2H/ NY county with a slash "/" in call it will not sequence OR DISPLAY THE REPORT. When you toggle to Tx4 or Tx5 the 73 it will log OK with report... same will happen if another K2H/ SES calls you..Issue the other station might not know they are logged..

Hi Tom,

as stated in the WSJT-X User Guide here in the last sentence of the third paragraph:

https://physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main-2.2.0-rc1.html#COMP-CALL

QSOs between two non-standard calls are not supported.

73
Bill
G4WJS.

On 14/05/2020 22:56, WA2NDV via groups.io wrote:

I am running SES K2H/NAS and I can not toggle TX4 to RR73 when using that call. If I change call to K2H I am able to toggle. It will stay in the selected message when changing it back to K2H/NAS

I have seen it in the rc1 code and the previous GA release.

73
Frank
WA2NDV

Hi Frank,

if you look at the example in the WSJT-X User Guide here:

https://physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main-2.2.0-rc1.html#COMP-CALL

you will see that the final 73 message is the only time that a station working another with a non-standard call sends the full call rather than a hash code. This is important because hash codes are not 100% two way, they may be incorrectly translated. The intent is that like reports full calls *sent in full* are confirmed by the station receiving them. Using a shortcut of RR73 means no 73 message is expected so in this case the minimum QSO may not be completed in full.

73
Bill
G4WJS.

Hi Frank

I ran into the same issue soo..
After the RRR
I set free text Tx5 to
K2H V QRZ 73
to end contact plus promote webpage..

NOW... Today as K2H/SUF Tx4 is back to RR73... go figure.. I kinda like the extra TX as it promotes web..

Also, If another station calls K2H/ NY county with a slash "/" in call it will not sequence OR DISPLAY THE REPORT. When you toggle to Tx4 or Tx5 the 73 it will log OK with report... same will happen if another K2H/ SES calls you..Issue the other station might not know they are logged..

Ten is still open to SA... and I did work a few EU off the back of antenna..

CU -Tom KA2D