Date   

Re: ALL.TXT Append Error #FT8 #error

Jeff Young
 

Bill:

I am running wsjt-x, jt-alert and N3FJP AC Log.

Jeff


Re: WSJT-X 2.4.0 rc-2 Subprocess Error #wsjt-x-crashing EXIT CODE 2 #wsjt-x-crashing

Bill Somerville
 

On 18/06/2021 02:01, Niece KA1ULN wrote:
i have had  this for  over  7 days now.....   what is  the  solution or  temp fix.. i cannot even use my wsjtx.

I AM  GETTING THE  SAME  ERROR   subprocess failed with exit  code 2.
Niece,

please include the full error message, including details, and the version of WSJT-X you are using?

73
Bill
G4WJS.


Re: WSJT-X 2.4.0 rc-2 Subprocess Error #wsjt-x-crashing EXIT CODE 2 #wsjt-x-crashing

Niece KA1ULN
 

i have had  this  for  over  7 days now.....   what is  the  solution or  temp fix.. i cannot even use my wsjtx.

I AM  GETTING THE  SAME  ERROR   subprocess failed with exit  code 2.


Re: [EXTERNAL] Re: [WSJTX] Cannot use /P in callsign when using JT65 and JT9 modes #JT9 #BugReport #JT65

Hattori, Yoshihisa
 

We might be talking about something different.

 

  1. Decode a sig from /P station. (ex. G4WJS/P)
  2. Double click on the decode to generate the message, or populate the DX call manually then click on generate standard message, which will result TX1 without GL. (i.e. G4WJS/P JO1LVZ. Note: This does not occur in FT8.)
  3. If I send the message as it is, DX will receive G4WJS/P <…> so that he will not know who is calling.

 

The only solution at this moment is manually add my GL to TX1. (i.e. TX1 with GL is mandatory to make the protocol work.)

It was originally reported to wsjt-devel back in Mar, too.

All the issues could be fixed by adding GL correctly in TX1 when standard message is generated. (not exactly sure though.)

 

Hatt/JO1LVZ

 

From: main@WSJTX.groups.io <main@WSJTX.groups.io> On Behalf Of Bill Somerville
Sent: Thursday, June 17, 2021 5:12 PM
To: main@WSJTX.groups.io
Subject: Re: [EXTERNAL] Re: [WSJTX] Cannot use /P in callsign when using JT65 and JT9 modes #JT65 #JT9 #BugReport

 

Hi Hatt-san,

 

are you sure? The Q65 mode uses a 77-bit payload with a different message source encoding scheme that allows messages like:

G4WJS/P JO1LVZ/P R-10

so the problem does not occur for that mode.

 

73
Bill
G4WJS.

 

On 17/06/2021 03:01, Hattori, Yoshihisa wrote:

Bill,

 

This also happens to Q65, so please make sure the issue gets fixed for that mode, too.

 

Thanks.

Hatt/JO1LVZ

 

 

From: main@WSJTX.groups.io <main@WSJTX.groups.io> On Behalf Of Bill Somerville
Sent: Wednesday, June 16, 2021 6:42 PM
To: main@WSJTX.groups.io
Subject: [EXTERNAL] Re: [WSJTX] Cannot use /P in callsign when using JT65 and JT9 modes #JT65 #JT9 #BugReport

 


[CAUTION] This email originated from outside Travelport. Do not click links or open attachments unless you recognize the sender and know the content is safe.



On 16/06/2021 10:23, Jim Brown wrote:

On 6/16/2021 1:10 AM, Panos wrote:


Hi Bill, thanks I am waiting for it 73


I am not. Just like on all other bands and modes, the definition of a QSO is the ack of receipt of two pieces if information from the other party. When I copy RRR or RR73, I log the QSO, because I've already sent R plus a report, and the fact that he's sent me RRR or RR73 indicates he's copied my R-report. If he sends RR73 or R and his report again, it tells me he hasn't copied my R, so I send it again. And again, if he keeps sending. He can log it when he's satisfied. When he stops sending his report, I log it. If he doesn't, we don't have a QSO. It's that simple. And for skeds, like online, it's perfeectly legit for the guy getting RRR or RR73 to say so online, like Slack or ON4KST or Ping Jockey. This is VERY common practice when working grid expeditions.

73, Jim K9YC

Jim,

this issue is about operating with a /P or other type 1 prefix or suffix in JT65 mode (same applies to JT9 and JT4 modes), the defect means it is not possible to send a signal report, RRR or 73 message unless the generated messages are manually edited. The defect is a regression that happened some considerable time ago and it needs to be fixed, which is what I  am doing.

73                                                                           
Bill
G4WJS.

 


Re: ALL.TXT Append Error #FT8 #error

Dave Garber
 

if you open the log folder in wsjt, does the all.txt show in there with the other files.
is the folder you state a typo    folder ..../wjt-x/...
Dave Garber
VE3WEJ / VE3IE


On Thu, Jun 17, 2021 at 4:14 PM Jeff Young <kb3hf@...> wrote:
I keep getting this error whale running FT8. "Cannot open C:/Users/…./WJT-X/ALL.TXT for append: The process cannot access the file because it is being used by another process."

 


I have excluded ALL.TXT from scanning and turned off indexing in properties.

Running Win 10, WSJT-X Version 2.3.1



Re: #FT8 Not Possible to sign portable? #FT8 #wsjt-x

Jim Brown
 

On 6/17/2021 10:03 AM, robert scott wrote:
I will operating from a different Call Area and wanted to sign WR3Y/7
Why? I've lived in W6 for 15 years, and the only times I've ever used /6 was on 6M CW when the band was open, so that callers wouldn't turn their beams in the wrong direction. That issue is covered by the normal inclusion of our grid in a CQ.

73, Jim K9YC


VS: [WSJTX] #FT8 Not Possible to sign portable? #FT8 #wsjt-x

Reino Talarmo
 

Hi Rob,

You may try it. I did and it is working, but program is using hash for the other or for your call. That’s fine. Only difficulty is that you cannot work other stations using special call signs. It fills the message correctly, but leave at transmission out e,g, “R-01” and sends only the call signs (one hashed).

73, Reino OH3mA

 

Lähettäjä: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] Puolesta robert scott
Lähetetty: 17 June 2021 20:03
Vastaanottaja: main@WSJTX.groups.io
Aihe: [WSJTX] #FT8 Not Possible to sign portable? #wsjt-x

 

I will operating from a different Call Area and wanted to sign WR3Y/7. I was told that wsjt-x will not pick up appending my call/7 ? I will of course be signing with the correct grid square. Is that true?

TU
Rob
WR3Y


Re: ALL.TXT Append Error #FT8 #error

Bill Somerville
 

On 17/06/2021 17:20, Jeff Young wrote:
I keep getting this error whale running FT8. "Cannot open C:/Users/…./WJT-X/ALL.TXT for append: The process cannot access the file because it is being used by another process."

 


I have excluded ALL.TXT from scanning and turned off indexing in properties.

Running Win 10, WSJT-X Version 2.3.1

Hi Jeff,

are you running any other ham radio software that might possibly be trying to scan the WSJT-X ADIF log for QSOs?

73
Bill
G4WJS.


Re: #FT8 Not Possible to sign portable? #FT8 #wsjt-x

Bill, WB6JJJ
 

Adding /7 should work OK. There will be “< call >” in the decode window but that is normal for a non-standard call.
Is there a good reason for adding portable 7? In most cases it is not needed since your grid square indicates where you are located. Also, merging your normal log with a portable 7 log along with uploading to LotW is a bit more of a chore.

Have fun,
Bill
WB6JJJ
Sherwood, Oregon (7)

On Jun 17, 2021, at 1:14 PM, robert scott <robertgscott@gmail.com> wrote:

I will operating from a different Call Area and wanted to sign WR3Y/7. I was told that wsjt-x will not pick up appending my call/7 ? I will of course be signing with the correct grid square. Is that true?

TU
Rob
WR3Y


#FT8 Not Possible to sign portable? #FT8 #wsjt-x

robert scott
 

I will operating from a different Call Area and wanted to sign WR3Y/7. I was told that wsjt-x will not pick up appending my call/7 ? I will of course be signing with the correct grid square. Is that true?

TU
Rob
WR3Y


ALL.TXT Append Error #FT8 #error

Jeff Young
 

I keep getting this error whale running FT8. "Cannot open C:/Users/…./WJT-X/ALL.TXT for append: The process cannot access the file because it is being used by another process."

 


I have excluded ALL.TXT from scanning and turned off indexing in properties.

Running Win 10, WSJT-X Version 2.3.1


Re: #Error Message #error

Bob Chortek
 
Edited

Thanks for the replies.  


Ferrites added to the USB cable solved the problem.

Much appreciated!

73 

Bob/AA6VB


Anomalous Behavior #BugReport #FT8

Pete Ritter
 


Yesterday I noticed a behavior in WSJT-X (FT8 mode) that I'd not seen before.  After every QSO was completed, if I moved to a new audio frequency by positioning the cursor on the Wide Graph and pressing Shift-Left Click, my TX6 text ("CQ K5CPR EM13") would print on the bottom line of the RX Frequency window.  After each QSO, WSJT-X remained in Monitor mode with TX6 checked and did not enter a transmit cycle (all that is normal) unless I activated the Enable Tx button.  I was able to cause WSJT-X to repeat this behavior several times.  Only when I changed bands did the behavior disappear.  I don't recall having done anything "unusual" prior to noticing the behavior.

WSJT-X v2.4.0 c19d62
FT8 mode
Windows 10
IC-7300
6m band


Re: FT991A and MacOS #WSJTX_config #AudioIssues #mac #NewUser

Bill Somerville
 

Hi Jeff, and Jeremy,

you can get more certainty of audio device naming and selection on macOS by creating an aggregate audio device, then assign your rig's audio devices to it. You can name the aggregate device as to desire, and select that in WSJT-X. This is most useful when you have multiple rigs with in-built USB audio codecs, but can of course be used with a single radio as well.

73
Bill
G4WJS.

On 16/06/2021 18:24, K3JRZ wrote:
Jeremy,

Check your audio settings in WSJT-X again. Sometimes macOS will add multiple USB sound card ports. I have to every once in a while change the SERIAL port that WSJT-X is listening to under Preferences - Radio.



On Wed, Jun 16, 2021 at 1:17 PM Jeremy Stark via groups.io <jrmstark=mac.com@groups.io> wrote:
I installed 2.4.0 and it worked for a while, including the waterfall display.

However, it has now gone deaf again.

--
Jeremy G7BHB

> On 26 May 2021, at 13:21, Brian Morrison <bdm@...> wrote:
>
> On Wed, 2021-05-26 at 11:06 +0100, Jeremy Stark via groups.io wrote:
>> I lost the audio device and unplugged the USB, restarted the software with the USB back in. It was briefly working, including Tx. I stopped transmit, and then I couldn’t select “Enable Tx” again.
>
>
> I think you should install the new GA version 2.4.0 as you are actually now 2 releases behind. There are some bugs fixed relating to this sort of problem so it would be better to assess it again with the fixed code.
>
> --
>
> Brian  G8SEZ






--

Thanks & 73,

Jeff
K3JRZ



Re: #Error Message #error

Alan G4ZFQ
 

Bob

Can someone please explain what the error message means and possible solutions, on the assumption that it isn’t RF but some other cause?
The error message seems to say there is a problem opening the sound device.
I can think of no way, (assuming amplifier on/off is repeatable) that it is anything other than RF in the shack upsetting operation of the computer.

73 Alan G4ZFQ


Re: [EXTERNAL] Re: [WSJTX] Cannot use /P in callsign when using JT65 and JT9 modes #JT9 #BugReport #JT65

Bill Somerville
 

Hi Hatt-san,

are you sure? The Q65 mode uses a 77-bit payload with a different message source encoding scheme that allows messages like:
G4WJS/P JO1LVZ/P R-10
so the problem does not occur for that mode.

73
Bill
G4WJS.

On 17/06/2021 03:01, Hattori, Yoshihisa wrote:

Bill,

 

This also happens to Q65, so please make sure the issue gets fixed for that mode, too.

 

Thanks.

Hatt/JO1LVZ

 

 

From: main@WSJTX.groups.io <main@WSJTX.groups.io> On Behalf Of Bill Somerville
Sent: Wednesday, June 16, 2021 6:42 PM
To: main@WSJTX.groups.io
Subject: [EXTERNAL] Re: [WSJTX] Cannot use /P in callsign when using JT65 and JT9 modes #JT65 #JT9 #BugReport

 



[CAUTION] This email originated from outside Travelport. Do not click links or open attachments unless you recognize the sender and know the content is safe.


On 16/06/2021 10:23, Jim Brown wrote:

On 6/16/2021 1:10 AM, Panos wrote:

Hi Bill, thanks I am waiting for it 73


I am not. Just like on all other bands and modes, the definition of a QSO is the ack of receipt of two pieces if information from the other party. When I copy RRR or RR73, I log the QSO, because I've already sent R plus a report, and the fact that he's sent me RRR or RR73 indicates he's copied my R-report. If he sends RR73 or R and his report again, it tells me he hasn't copied my R, so I send it again. And again, if he keeps sending. He can log it when he's satisfied. When he stops sending his report, I log it. If he doesn't, we don't have a QSO. It's that simple. And for skeds, like online, it's perfeectly legit for the guy getting RRR or RR73 to say so online, like Slack or ON4KST or Ping Jockey. This is VERY common practice when working grid expeditions.

73, Jim K9YC

Jim,

this issue is about operating with a /P or other type 1 prefix or suffix in JT65 mode (same applies to JT9 and JT4 modes), the defect means it is not possible to send a signal report, RRR or 73 message unless the generated messages are manually edited. The defect is a regression that happened some considerable time ago and it needs to be fixed, which is what I  am doing.

73
Bill
G4WJS.



Re: All #udp error popup buttons are unresponsive #udp

Bill Somerville
 

On 17/06/2021 03:06, Alwin N6ATF wrote:
Have to force quit my way out from this:
Hi Alwin,

most uses of the WSJT-X UDP Message protocol are to communicate with a server running on the same machine as WSJT-X and would use a local loopback IP address like 127.0.0.1. It seems you have configured WSJT-X to talk to a server on IP address 192.168.1.117, is that a different machine? If you are using a 3rd party aniti-virus product that includes a firewall, then ensure that your machine is allowed to send UDP traffic on port 2237 to that address.

73
Bill
G4WJS.


Re: #Error Message #error

Bill Somerville
 

On 16/06/2021 23:44, Bob Chortek wrote:
Good Day,

If I operate my 7610 with the SPE 1.5 K- FA amplifier I get a message which says “An error opening sound input device has occurred“.

If run the rig barefoot at say 10 W, it operates fine and no error message appears.

I’m guessing possible RF and so I’ll add some fair rates to the USB cable.

Can someone please explain what the error message means and possible solutions, on the assumption that it isn’t RF but some other cause?

Any suggestions would be greatly appreciated.

73,

Bob/AA6VB
Hi Bob,

the message means that the audio stream that WSJT-X is listening on has gone away, a likely cause is that the USB connection to your rig has been disrupted by RFI and reset itself. Most users with such configurations are running CAT control over the same USB cable, they would also find CAT control disrupted.

73
Bill
G4WJS.


Re: [EXTERNAL] Re: [WSJTX] Cannot use /P in callsign when using JT65 and JT9 modes #JT9 #BugReport #JT65

Panos
 

Hi maybe it'll be more easy and less time and effort consuming if problems like this examined and fixed for all modes at once. Thanks forall 73


Re: Rig Control Error v2.4.0 #NewUser #WSJTX_config

Alan G4ZFQ
 

Derek

am getting a "Rig Control Error"
Have you a CAT connection?
If not set Radio to "None"

73 Alan G4ZFQ

1 - 20 of 25763