locked
Re: ALL.TXT Append Error
#FT8
#IssueReport
Jeff Young
Further investigation. The error window appears as the latest decodes are being posted to the left window. I have removed McAfee LiveSafe from the computer and am only using the windows 10 built in security. I have excluded the entire folder where the logs files exist in the appdata/local/WSJT-X folder. I am only running Version 2.3.1 without JT-Alert and ACLog. Sometimes the error windows are 18 screens deep.
|
||
|
||
locked
Re: WSJT-X 2.4.0 rc-2 Subprocess Error #wsjt-x-crashing EXIT CODE 2
#wsjt-x-crashing
You might consider installing the release version of the software, as the rc versions are expired.
|
||
|
||
locked
Re: FT991A and MacOS
#WSJTX_config
#AudioIssues
#macOS
#NewUser
Hi Jeremy,
have you assigned the necessary rig USB
audio codec devices to the new aggregate device?
73
Bill G4WJS.
On 18/06/2021 15:53, Jeremy Stark via
groups.io wrote:
I created an aggregate device, and selected it in WSJT-X. I can hear there are signals present on the radio, but the software is not showing anything.
|
||
|
||
locked
#Cat_RigControl #error
#Cat_RigControl
#IssueReport
mattwood2000@...
Hi all,
I'm running into some rig control errors and I'm wondering if anyone has successfully used rigctld and remote (localhost or network) operation? My rig is an FT-897D. WSJT-x works perfectly fine when I directly connect to the rig over the serial port, but I get errors (ERR_IO, -6) when running rigctld-wsjtx with the same parameters and set the program to use HamLib NET 2. I've tried the 4.2 release, the integration release as well as the master branch of the code, all with the same results. Most of the time, wsjt-x comes up and reads the VFO and everything looks good, but as soon as I try to test the CAT or PTT it errors out. I realize this may be more of a hamlib issue, but figured I'd start here first. Thanks, Matt. N1YQE
|
||
|
||
locked
Re: FT991A and MacOS
#WSJTX_config
#AudioIssues
#macOS
#NewUser
Jeremy Stark
I created an aggregate device, and selected it in WSJT-X. I can hear there are signals present on the radio, but the software is not showing anything.
toggle quoted messageShow quoted text
-- Jeremy G7BHB
|
||
|
||
locked
Re: ALL.TXT Append Error
#FT8
#IssueReport
Jeff Young
Bill:
I am running wsjt-x, jt-alert and N3FJP AC Log. Jeff
|
||
|
||
locked
Re: WSJT-X 2.4.0 rc-2 Subprocess Error #wsjt-x-crashing EXIT CODE 2
#wsjt-x-crashing
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.Niece, please include the full error message, including details, and the version of WSJT-X you are using? 73 Bill G4WJS.
|
||
|
||
locked
Re: WSJT-X 2.4.0 rc-2 Subprocess Error #wsjt-x-crashing EXIT CODE 2
#wsjt-x-crashing
Niece KA1ULN <ka1uln1@...>
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.
|
||
|
||
locked
Re: [EXTERNAL] Re: [WSJTX] Cannot use /P in callsign when using JT65 and JT9 modes
#JT9
#IssueReport
#JT65
Hattori, Yoshihisa
We might be talking about something different.
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
On 17/06/2021 03:01, Hattori, Yoshihisa wrote:
|
||
|
||
locked
Re: ALL.TXT Append Error
#FT8
#IssueReport
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."
|
||
|
||
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/7Why? 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
|
||
|
||
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
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?
|
||
|
||
locked
Re: ALL.TXT Append Error
#FT8
#IssueReport
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." 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
|
||
|
||
Adding /7 should work OK. There will be “< call >” in the decode window but that is normal for a non-standard call.
toggle quoted messageShow quoted text
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@...> 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
|
||
|
||
locked
ALL.TXT Append Error
#FT8
#IssueReport
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
|
||
|
||
locked
Re: #Error Message
#IssueReport
Thanks for the replies.
|
||
|
||
locked
Anomalous Behavior
#IssueReport
#FT8
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
|
||
|
||
locked
Re: FT991A and MacOS
#WSJTX_config
#AudioIssues
#macOS
#NewUser
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:
|
||
|
||
locked
Re: #Error Message
#IssueReport
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
|
||
|