Date   

locked Re: CQ instead of 73 #FT8

Bill Somerville
 

John,

look again at the exchange! EA4SM never sent his gridsquare.

73
Bill
G4WJS.

On 17/02/2021 18:18, JP Tucson, AZ wrote:

Actually, I am looking at the log box with the empty "grid" block. Something I have been trying to inform you about for a while.  As you 
can see, it DOES happen to other users.  

But hey, whatever... I'm obviously lying about it. Right?


 - John - N7GHZ

On Wed, Feb 17, 2021, 11:12 AM Bill Somerville <g4wjs@...> wrote:
John,

you must be looking at a different exchange from the one I see.

73
Bill
G4WJS.

On 17/02/2021 18:07, JP Tucson, AZ wrote:
Notice also that the logging box  DID NOT PICK UP THE GRID SQUARE!  ...though it is clearly listed in the data exchanges!



73 - John - N7GHZ

On Wed, Feb 17, 2021, 10:59 AM Ken WB8UFC <wb8ufc@...> wrote:
On Wed, Feb 17, 2021 at 12:49 PM, Ken WB8UFC wrote:
I'll try deferring the logging and see if that makes a difference.
Nope. No difference.

I didn't log and it WSJT-X still sent the 73 in response to the second RR73.
I then double-clicked on the RR73 at 175430 and WSJT-X then sent the second CQ at 175446.
The 73 at 175441 I did manually.




locked Re: CQ instead of 73 #FT8

JP Tucson, AZ
 

Actually, I am looking at the log box with the empty "grid" block. Something I have been trying to inform you about for a while.  As you 
can see, it DOES happen to other users.  

But hey, whatever... I'm obviously lying about it. Right?


 - John - N7GHZ


On Wed, Feb 17, 2021, 11:12 AM Bill Somerville <g4wjs@...> wrote:
John,

you must be looking at a different exchange from the one I see.

73
Bill
G4WJS.

On 17/02/2021 18:07, JP Tucson, AZ wrote:
Notice also that the logging box  DID NOT PICK UP THE GRID SQUARE!  ...though it is clearly listed in the data exchanges!



73 - John - N7GHZ

On Wed, Feb 17, 2021, 10:59 AM Ken WB8UFC <wb8ufc@...> wrote:
On Wed, Feb 17, 2021 at 12:49 PM, Ken WB8UFC wrote:
I'll try deferring the logging and see if that makes a difference.
Nope. No difference.

I didn't log and it WSJT-X still sent the 73 in response to the second RR73.
I then double-clicked on the RR73 at 175430 and WSJT-X then sent the second CQ at 175446.
The 73 at 175441 I did manually.






locked Re: CQ instead of 73 #FT8

Bill Somerville
 

John,

you must be looking at a different exchange from the one I see.

73
Bill
G4WJS.

On 17/02/2021 18:07, JP Tucson, AZ wrote:

Notice also that the logging box  DID NOT PICK UP THE GRID SQUARE!  ...though it is clearly listed in the data exchanges!



73 - John - N7GHZ

On Wed, Feb 17, 2021, 10:59 AM Ken WB8UFC <wb8ufc@...> wrote:
On Wed, Feb 17, 2021 at 12:49 PM, Ken WB8UFC wrote:
I'll try deferring the logging and see if that makes a difference.
Nope. No difference.

I didn't log and it WSJT-X still sent the 73 in response to the second RR73.
I then double-clicked on the RR73 at 175430 and WSJT-X then sent the second CQ at 175446.
The 73 at 175441 I did manually.



locked Re: CQ instead of 73 #FT8

JP Tucson, AZ
 

Notice also that the logging box  DID NOT PICK UP THE GRID SQUARE!  ...though it is clearly listed in the data exchanges!



73 - John - N7GHZ

On Wed, Feb 17, 2021, 10:59 AM Ken WB8UFC <wb8ufc@...> wrote:
On Wed, Feb 17, 2021 at 12:49 PM, Ken WB8UFC wrote:
I'll try deferring the logging and see if that makes a difference.
Nope. No difference.

I didn't log and it WSJT-X still sent the 73 in response to the second RR73.
I then double-clicked on the RR73 at 175430 and WSJT-X then sent the second CQ at 175446.
The 73 at 175441 I did manually.





locked Re: CQ instead of 73 #FT8

Bill Somerville
 

On 17/02/2021 17:59, Ken WB8UFC wrote:
On Wed, Feb 17, 2021 at 12:49 PM, Ken WB8UFC wrote:
I'll try deferring the logging and see if that makes a difference.
Nope. No difference.

I didn't log and it WSJT-X still sent the 73 in response to the second RR73.
I then double-clicked on the RR73 at 175430 and WSJT-X then sent the second CQ at 175446.
The 73 at 175441 I did manually.

Ken,

the only reasonable replies to an RR73 message are either nothing, a 73 message, or some free text message sending extra information. If your QSO partner elects to send an RR73 message in reply to your R+report message then they should not expect any reply.

73
Bill
G4WJS.


locked Re: CQ instead of 73 #FT8

Ken WB8UFC
 

On Wed, Feb 17, 2021 at 12:49 PM, Ken WB8UFC wrote:
I'll try deferring the logging and see if that makes a difference.
Nope. No difference.

I didn't log and it WSJT-X still sent the 73 in response to the second RR73.
I then double-clicked on the RR73 at 175430 and WSJT-X then sent the second CQ at 175446.
The 73 at 175441 I did manually.


locked Re: CQ instead of 73 #FT8

Ken WB8UFC
 

On Wed, Feb 17, 2021 at 11:27 AM, Reino Talarmo wrote:
At what point you log the QSO? Have you already logged the QSO before you receive the repeated RRR or RR73?
You directed that to Chuck, but I have ALWAYS logged the QSO by that point.
I have "Prompt me to log QSO" checked on the Reporting tab of Settings.
So WSJT-X prompts me to log as soon as I initiate my first 73 - which I do.

I'll try deferring the logging and see if that makes a difference.


locked Re: CQ instead of 73 #FT8

Ken WB8UFC
 

Chuck,

That is definitely NOT the behavior I observe.

Like you, I click the "Enable Tx" immediately after logging the contact.

In the snapshot below, when that second RR73 was sent at 173600, "Enable Tx" was enabled.
It did not cycle back to another 73 from me.
Instead, it sent the CQ at 173615.

I then had to click "Halt Tx," click the radio button for my "73" message, and then click "Enable Tx."

I wouldn't mind that so much except by the time all that is done, they often don't get the 73 and so I need to send another one just to be sure.

Bill, double-clicking on the message at 173600 would have made no difference.
The CQ message is sent - not the 73 response to his RR73.


locked Re: #bugreport JT4 decodes crash v2.4.0-rc1 #IssueReport

g3wdg <charlie@...>
 

correction for 'f' read 'g'.

There is also no 'g' in Q65, although it is selectable in -rc1.


Hi David

I think that's happening because you were on a submode letter (f) when in
JT4 and when going to Q65 that would have persisted as the selected
submode.

There is currently no f submode coded in WSJT-X and when a decode is
attempted it may crash with that error.

I believe that this has been fixed already and will be in the next
release.

For now, just reselect a valid submode having switched to Q65.

The other, and better, approach is not to just switch modes, but create
configurations for them using the configuration menu and following the
instructions in the User Guide. That way, your preferred settings for
different modes will be retained.

73

Charlie G3WDG

It was happeneing to me yesterday when trying to decode a couple of 23cm
beacons that run JT4g.

I'm running Windows 10 Pro on an Intel i5, 3.2GHz with 4GB RAM, if that
helps?

Today, when I swapped from FT8 to Q65 it happened again.  Error message
as follows;

Running: C:\WSJT\RC1\wsjtx\bin\jt9 -s WSJT-X -w 1 -m 3 -e
C:\WSJT\RC1\wsjtx\bin -a C:\Users\Owner\AppData\Local\WSJT-X -t
C:\Users\Owner\AppData\Local\Temp\WSJT-X

At line 24 of file C:\Users\bill\src\k1jt\wsjtx\lib\spec64.f90

Fortran runtime error: Array bound mismatch for dimension 1 of array
'cs'
(1800/0)

Error termination. Backtrace:

Could not print backtrace: libbacktrace could not find executable to
open

#0 0xffffffff

#1 0xffffffff

#2 0xffffffff

#3 0xffffffff

#4 0xffffffff

#5 0xffffffff





locked Re: Subject Tags #GeneralGroupInfo

Roger
 

On 17/02/2021 15:01, John, K9MM wrote:
I thought it was OK to use a new subject tag if the subject didn't already have an appropriate one at the end of the digest. I had some questions about FST4 so I sent a message with the subject line
"JT9 vs FST4 #FST4". It would have been OK if the message had gone to a moderator for review, but it actually bounced.
Hi John

That hashtag now exists and I've created others to ensure they exist for every mode.

We're bound by what is possible on groups.io and I don't think it's possible to create a hashtag in that manner.


73
Roger
G#4HZA
moderator


locked Re: Subject Tags #GeneralGroupInfo

Bob Cutter <ki0g@...>
 

I had some issue, sent one to config#?  No response, yet. 

Bob KI0G




On Wednesday, February 17, 2021, 8:01 AM, John, K9MM <johnb3030@...> wrote:

I thought it was OK to use a new subject tag if the subject didn't
already have an appropriate one at the end of the digest. I had some
questions about FST4 so I sent a message with the subject line
"JT9 vs FST4 #FST4". It would have been OK if the message had gone to a
moderator for review, but it actually bounced.
======================================================
      This is an automatically generated Delivery Status Notification.


Delivery to the following recipients failed permanently:


Reason: Permanent Error


Reporting-MTA: dns; resqmta-ch2-04v.sys.comcast.net [69.252.207.36]
Received-From-MTA: dns; resomta-ch2-03v.sys.comcast.net [69.252.207.99]
Arrival-Date: Mon, 15 Feb 2021 21:14:23 +0000


Final-recipient: rfc822; main@wsjtx.groups.io
Diagnostic-Code: smtp; 500 Members are not allowed to create new
hashtags. Please resend your message using only approved hashtags in the
subject.
========================================================
So I resent the message with this subject line and it went through
"JT9 vs FST4 vs Q65 #Q65"

The original message DID address Q65 tangentially, but it mainly was
about JT9 and FST4. There are no APPROVED tags for either FST4 or JT9.

I don't want to start a long discussion about this, but just suggesting
perhaps the tag process needs to be massaged a bit. Thanks!

73,

John, K9MM




locked Re: #bugreport JT4 decodes crash v2.4.0-rc1 #IssueReport

g3wdg <charlie@...>
 

Hi David

I think that's happening because you were on a submode letter (f) when in
JT4 and when going to Q65 that would have persisted as the selected
submode.

There is currently no f submode coded in WSJT-X and when a decode is
attempted it may crash with that error.

I believe that this has been fixed already and will be in the next release.

For now, just reselect a valid submode having switched to Q65.

The other, and better, approach is not to just switch modes, but create
configurations for them using the configuration menu and following the
instructions in the User Guide. That way, your preferred settings for
different modes will be retained.

73

Charlie G3WDG

It was happeneing to me yesterday when trying to decode a couple of 23cm
beacons that run JT4g.

I'm running Windows 10 Pro on an Intel i5, 3.2GHz with 4GB RAM, if that
helps?

Today, when I swapped from FT8 to Q65 it happened again.  Error message
as follows;

Running: C:\WSJT\RC1\wsjtx\bin\jt9 -s WSJT-X -w 1 -m 3 -e
C:\WSJT\RC1\wsjtx\bin -a C:\Users\Owner\AppData\Local\WSJT-X -t
C:\Users\Owner\AppData\Local\Temp\WSJT-X

At line 24 of file C:\Users\bill\src\k1jt\wsjtx\lib\spec64.f90

Fortran runtime error: Array bound mismatch for dimension 1 of array 'cs'
(1800/0)

Error termination. Backtrace:

Could not print backtrace: libbacktrace could not find executable to open

#0 0xffffffff

#1 0xffffffff

#2 0xffffffff

#3 0xffffffff

#4 0xffffffff

#5 0xffffffff


locked Re: CQ instead of 73 #FT8

Reino Talarmo
 

From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of Chuck - KY4CU
Sent: 17. helmikuuta 2021 16:51
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] CQ instead of 73 #FT8

 

I usually click on allow transmit as soon as the software thinks the exchange is complete.

Then, if you get a repeat RRR or RR73, the software auto sequences to your 73 msg instead of cq.

Sometimes it's like whack-a-mole trying to keep the button red if I'm on a busy band and getting late decodes.

 

Chuck,

At what point you log the QSO? Have you already logged the QSO before you receive the repeated RRR or RR73?

73, Reino OH3mA

 


locked Re: #Q65 #Q65

Kevin McQuiggin (VE7ZD/KN7Q)
 

No problem, try 50.275 MHz and 30A, there seems to be a lot of activity there.  People have also been on 50.235 MHz 120E


On Feb 17, 2021, at 08:08, Darl DEEDS <na8w@...> wrote:



Thanks Kevin, that helps a lot. I was looking for a button to set for sub modes. In fact this is simpler.

 

73

 

Darl  NA8W

 

From: Kevin McQuiggin (VE7ZD/KN7Q)
Sent: Wednesday, February 17, 2021 11:06
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] #Q65

 

Hi Darl, after you select Q65 mode then you set the timing and sub mode using the controls in the centre part of the WSJT-X window.

For example, to set what people are calling “30A” within Q65, select 30 seconds as the transmit/receive cycle and “Submode A” using the Submode control to the left of the transmit messages box.

Same for other settings like 120E: set T/R cycle at 120 seconds and Submode to E.

Hope that this helps, 73,

Kevin
> On Feb 17, 2021, at 07:51, Darl DEEDS <na8w@...> wrote:
>
> I know I am missing something really simple but I am trying to set up Q65 to listen to and maybe operate. I read the quick start guide, sorry I didn't play the test files, but I can't find how to set the individual sub modes. It shows Q65 only.
>
>
> Darl  NA8W
>
>

 





locked Re: #Q65 #Q65

Darl DEEDS
 

Thanks Kevin, that helps a lot. I was looking for a button to set for sub modes. In fact this is simpler.

 

73

 

Darl  NA8W

 

From: Kevin McQuiggin (VE7ZD/KN7Q)
Sent: Wednesday, February 17, 2021 11:06
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] #Q65

 

Hi Darl, after you select Q65 mode then you set the timing and sub mode using the controls in the centre part of the WSJT-X window.

For example, to set what people are calling “30A” within Q65, select 30 seconds as the transmit/receive cycle and “Submode A” using the Submode control to the left of the transmit messages box.

Same for other settings like 120E: set T/R cycle at 120 seconds and Submode to E.

Hope that this helps, 73,

Kevin
> On Feb 17, 2021, at 07:51, Darl DEEDS <na8w@...> wrote:
>
> I know I am missing something really simple but I am trying to set up Q65 to listen to and maybe operate. I read the quick start guide, sorry I didn't play the test files, but I can't find how to set the individual sub modes. It shows Q65 only.
>
>
> Darl  NA8W
>
>

 


locked Re: WSJT-X v2.4.0 feature request #mainscreen #Waterfall

Alan G4ZFQ
 

JJ wrote:
Setting the drive level using the Pwr slider as currently done is good.  Would also love two (2) small "up" and "down" buttons for adjusting the power in small increments (e.g.:  0.1, 0.2, or 0.3 dB steps)
The mouse wheel does 0.3dB. The up/down keys 0.1dB.
I'm not sure why such precision is required, not many can tell or measure 1dB?

73 Alan G4ZFQ


locked Re: #Q65 #Q65

Kevin McQuiggin (VE7ZD/KN7Q)
 

Hi Darl, after you select Q65 mode then you set the timing and sub mode using the controls in the centre part of the WSJT-X window.

For example, to set what people are calling “30A” within Q65, select 30 seconds as the transmit/receive cycle and “Submode A” using the Submode control to the left of the transmit messages box.

Same for other settings like 120E: set T/R cycle at 120 seconds and Submode to E.

Hope that this helps, 73,

Kevin

On Feb 17, 2021, at 07:51, Darl DEEDS <na8w@...> wrote:

I know I am missing something really simple but I am trying to set up Q65 to listen to and maybe operate. I read the quick start guide, sorry I didn't play the test files, but I can't find how to set the individual sub modes. It shows Q65 only.


Darl NA8W


locked #Q65 #Q65

Darl DEEDS
 

I know I am missing something really simple but I am trying to set up Q65 to listen to and maybe operate. I read the quick start guide, sorry I didn't play the test files, but I can't find how to set the individual sub modes. It shows Q65 only. 


Darl  NA8W


locked Re: WSJT-X v2.4.0 feature request #mainscreen #Waterfall

Michel Bernard VE2BJG
 

I second the request. Be able to combine or separate the waterfall would be nice.


locked Subject Tags #GeneralGroupInfo

John, K9MM
 

I thought it was OK to use a new subject tag if the subject didn't already have an appropriate one at the end of the digest. I had some questions about FST4 so I sent a message with the subject line
"JT9 vs FST4 #FST4". It would have been OK if the message had gone to a moderator for review, but it actually bounced.
======================================================
This is an automatically generated Delivery Status Notification.


Delivery to the following recipients failed permanently:

* main@wsjtx.groups.io

Reason: Permanent Error


Reporting-MTA: dns; resqmta-ch2-04v.sys.comcast.net [69.252.207.36]
Received-From-MTA: dns; resomta-ch2-03v.sys.comcast.net [69.252.207.99]
Arrival-Date: Mon, 15 Feb 2021 21:14:23 +0000


Final-recipient: rfc822; main@wsjtx.groups.io
Diagnostic-Code: smtp; 500 Members are not allowed to create new hashtags. Please resend your message using only approved hashtags in the subject.
========================================================
So I resent the message with this subject line and it went through
"JT9 vs FST4 vs Q65 #Q65"

The original message DID address Q65 tangentially, but it mainly was about JT9 and FST4. There are no APPROVED tags for either FST4 or JT9.

I don't want to start a long discussion about this, but just suggesting perhaps the tag process needs to be massaged a bit. Thanks!

73,

John, K9MM

17901 - 17920 of 40086