Date   

locked Re: IOS Big Sur problems

Bill Somerville
 

On 13/11/2020 20:41, Hamish G0GLG via groups.io wrote:
Hi,
My MacBook pro has as usual automatically updated the iOS and installed Big Sur.
First problem on starting WSJT-X was the memory error, no problem re-ran the script and restarted WSJT-X.
Started ok but Hamid error, should be no problem as I have to change the USB_UART driver nearly every time I start up WSJT-X so go to select the correct one out of the 4 choices I always get, no  drivers available?
No problem I will just re-install the driver and start again.

This is where the problem really starts, during installation it comes up with usual prompt to go into System preferences/security&privacy to allow the drivers to be installed. The problem is there is no prompt on the Security&Privacy screen?
This of course should be there at the lower portion of the window but it's not and no matter what I do I can't get them installed, even if I bypass the prompt by selecting 'already authorised' I can't do so.

So has anyone experienced this and what's the work round, any help greatly received.

Hamish G0GLG

Hi Hamish,

you could try taking the Gatekeeper quarantine flag off the driver installation file manually.

xattr -d com.apple.quarantine /path-to-quarantined-file

73
Bill
G4WJS.


locked Subprocess Failed with Exit Code 2 on WSJT-X v2.2.2

Lance Collister, W7GJ
 

This has happened a couple times recently on my second computer, which is just used for monitoring JT65A on 6m EME. It only seems to happen after it has been running for some time.


I am using Windows 10, and have selected all the DECODE options except Fast and Normal. I am feeding WSJT-X with VAC 4.64 from SDR Console Version 3.0.25.

I was unable to copy the text from the error screen, but here is what it said:

Running:

C:\WSJT\WSJTX\bin\jt9 -s WSJT-X -w 1 -m 3 -e

C:\WSKT\WSKTX\bin -a

C:\WSKT\WSKTX\AppData\Local\WSKT-X -t

C:\Users\w7gj\AppData\Local\Temp\WSJT-X

At line 210 of file C:\Users\bill\src\k1jt\wsjtx\lib\decoder.f90 (unit = 14)

Fortran runtime error:

Cannot open file 'C:\Users\w7gj\AppData\Local\Temp\WSJT-X/avemsg.txt: No such file or directory

Error termination.

Backtrace:

Could not print backtrace:libbacktrace

could not find excecutable to open

#0 0xffffffff

#1 0xffffffff

#2 0xffffffff

#3 0xffffffff

#40xffffffff

#50xffffffff

#6 0xffffffff

#7 0xffffffff

#8 0xffffffff

#9 0xffffffff

#100xffffffff

#11 0xffffffff

#120xffffffff

#13 0xffffffff

--
Lance Collister, W7GJ(ex WA3GPL, WA1JXN, WA1JXN/C6A, ZF2OC/ZF8, E51SIX, 3D2LR, 5W0GJ, E6M, TX5K, KH8/W7GJ, V6M, T8GJ, VK9CGJ, VK9XGJ, C21GJ, CP1GJ, S79GJ, TX7MB)
P.O. Box 73
Frenchtown, MT 59834-0073
USA
TEL: (406) 626-5728
QTH: DN27ub
URL: http://www.bigskyspaces.com/w7gj
Skype: lanceW7GJ
2m DXCC #11 - 6m DXCC #815 - FFMA #7

Interested in 6m EME? Ask me about subscribing to the Magic Band EME
email group, or just fill in the request box at the bottom of my web
page (above)!


locked Re: WSJT-X Keying failure with IC-7300 20% of the time.

John V
 

Thanks all,  yes connected vial USB only. I tried some of the suggested settings and still had no love, the 20% failure rate really had me puzzled. Sometimes the system would TX fine for several minutes then suddenly there would be no output. I think that by excluding the suggested changes suggested one at a time it lead me to the solution. I changed the 7300 Menu/set/connections/CI-V baud rate from 19200 or Auto to 115200 and made the same change to my logging/radio control SW (HRD) in the chose radio to connect section.  I've tested the changes about 50 times and all seems good now. Not sure why it was unhappy 20% of the time at 19200 or auto but it is not hiccupping at 115200 so I'm happy.  Now I have to readjust all of my audio settings and go activate more rare grids (-; 

Thanks again for the solutions, John NA6L       


locked Re: Something strange with WSJT-X

Martin G0HDB
 

On Fri, Nov 13, 2020 at 11:36 AM, Bill Somerville wrote:

Hi Martin,

you are correct. The example entries I specified are for the currently selected configuration, there is no ambiguity as entries for non-current configurations are stored with different (augmented) keys. There are also entries for other top level windows.

My suggestion was to try deleting the entries specifically for the current configuration main window, which I assume was the one you were having difficulty with since you didn't state which one you were referring to, with the intention to see if deleting them helped. If it does help then that is useful fro determining what is going on.

73
Bill
G4WJS.

Thanks again Bill, all understood.  I'll try deleting the three key/value pairs in the [MainWindow] section and see what happens, although for some reason the size and position of the main window seem to be behaving themselves today, so heaven knows what's going on with this new Windows 10 PC!

73
--
Martin G0HDB


locked Time for More FT4 Activity

Anthony Luscre
 

As the Sunspot numbers begin to edge up in the new cycle, I think it is a good time to consider using FT4 more. Although there is usually activity on 20 and occasional;y 17 & 40 Meters there seems to be a lack of activity on 15, 12 and 10 Meters. 

--
Anthony Luscre

K8ZT
Ohio Section Section Youth Coordinator & Education Outreach
ARRL - The National Association For Amateur Radio™
 
k8zt@... (best for Amateur Radio)

The Web Resource Hoarder- www.ZTLearn.com

K8ZT Radio Website- www.k8zt.com

Amateur Radio Resources for Students/Youth - www.k8zt.com/hry


locked Re: No FT8 contacts, however FT4 works perfectly.

Todd Shiffer (N3PKJ) <n3pkj@...>
 

Why are you using a signal link with a 991 when it has a built in sound card? No need for the signal link if you're connecting to the radio via USB.


locked Re: WSJT-X Keying failure with IC-7300 20% of the time.

Carl - WC4H
 

HI John.

Assuming that you are using the USB port on the radio.  If not, I recommend it.
Have you checked your USB MOD Level?  I usually set it between 23 and 28.  
Also the DATA MOD should be set to USB.   

I set the bandwidth on the radio to 3200.  That seems to work pretty well.  

73.
Carl - WC4H

 


locked Re: No FT8 contacts, however FT4 works perfectly.

Steve Thompson
 

Hi Patrick,

Thanks for your reply.

I think you may be right, as yesterday while on ft8 CQ'ing for ages I was getting the occasional answer. PSK reporter said I was not putting out an ft8 signal! I obviously was.

FT4 on psk comes back with speech bubbles within a few minutes.

Ironically wsjtx ft8 has started to work today! I have even had a VK from here (UK) that's pretty good at the moment.

I also put my usb connector in and out a few times.

Kind regards,

Steve 2E0WDM

On 13/11/2020 15:50, Patrick Hung wrote:

I've also experienced this, twice. The first time was a few weeks ago, and the latest yesterday, both on FT8. The problem went away after a while (I checked back after 20 minutes or so, and it was working). I think that it's a PSK-REPORTER glitch, as I made no changes to my radio/computer. I have not encountered this problem in FT4, yet.
--
73,
Patrick, W2TAR

Virus-free. www.avg.com




locked Re: No FT8 contacts, FT4 works perfectly! #FT8

Steve Thompson
 

Hi Phil,

Thanks for your reply.

Ironically wsjtx ft8 has started to work today! I have even had a VK!

The only thing I have done is to put  the usb plug in and out a few times, and re-started everything.

My clock is spot on via web service. Definitely in data-usb mode.

I will have a re-read of setting band widths etc as something weird is going on (you can guarantee it's operator error..haha)

Thanks for your help, I will give a remote RX a go.

Kind regards,

Steve

On 13/11/2020 08:54, Phil Davidson via groups.io wrote:

Hi Steve.

Interesting situation that usually means something obvious, that’s in your face but u cant see it.

 

Could it be something like the radio swapping to LSB for that mode?

 

Also, u might try a look/hear at your signal using a remote Rx. Try WebSDR in Twente ..  http://websdr.ewi.utwente.nl:8901/

Or the RSGB SDR

 

Also, time is vital. I assume your ‘clock’ is good.

 

Regards – Phil (G0DOR)

 

Sent from Mail for Windows 10

 

From: Steve Thompson
Sent: 12 November 2020 21:51
To: WSJTX@groups.io
Subject: [WSJTX] No FT8 contacts, FT4 works perfectly!

 

Hi,

I am new to your group so apologise if this has been covered before; I have found similar posts but no definitive answer.

I have been using wsjtx with psk reporter and Log4Om through my ft991a and signalink, successfully since the start of June this year.

A few days ago ft8 tx stopped, according to psk reporter and lack of  contacts. Ft4 remains working well also according to psk reporter and instant replies to CQ calls, both on 20m.

I have checked my radio settings, usb and other connections (windows settings are correct according to signalink manual). I am getting a clear tone out of my laptop on monitor and power out is showing on my rig meter for both ft8 and ft4. I have been through filter settings and have updated wsjtx to 2.2.2. The only setting I have changed recently is data vox. I changed it back to 300ms, still no ft8.

Does psk reporter ever glitch? Everything appears to work apart from no contacts or reports! I have tried TX at both ends and middle of waterfall.

Am I missing something? Probably user error like usual! Maybe in filter settings or band width?

Thankyou in advance.

Steve 2E0WDM

 


Virus-free. www.avg.com




locked Re: No FT8 contacts, however FT4 works perfectly.

Patrick Hung
 

I've also experienced this, twice. The first time was a few weeks ago, and the latest yesterday, both on FT8. The problem went away after a while (I checked back after 20 minutes or so, and it was working). I think that it's a PSK-REPORTER glitch, as I made no changes to my radio/computer. I have not encountered this problem in FT4, yet.
--
73,
Patrick, W2TAR


locked Re: WSJT-X Keying failure with IC-7300 20% of the time.

Andrew OBrien
 

I’m guessing Steve is correct .

Andy

On Nov 13, 2020, at 7:25 AM, sckeith@... wrote:

Hello

Is it possible that you are trying an FT8 contact above 2700HZ in the waterfall while the TBW setting is at its' default of 300-2700. Try changing to 300-2900 and see if you still have these issues. You still won't be able to TX above 2900.

Steve ve4fx


locked Re: WSJT-X Keying failure with IC-7300 20% of the time.

Steve VE4FX
 

Hello

Is it possible that you are trying an FT8 contact above 2700HZ in the waterfall while the TBW setting is at its' default of 300-2700. Try changing to 300-2900 and see if you still have these issues. You still won't be able to TX above 2900.

Steve  ve4fx


locked Re: Colors and Selection

Bill Somerville
 

On 13/11/2020 11:59, JD Delancy wrote:
Morning Bill

Appears to be both, General Font and Decoded Font

    jd
Hi JD,

so I can try and replicate this issue can you set the fonts so the issue is present, then quit WSJT-X and send me you ~/.config/WSJT-X.ini file for analysis please?

73
Bill
G4WJS.


locked Re: Colors and Selection

JD Delancy
 

Morning Bill

Appears to be both, General Font and Decoded Font

    jd


locked Re: Colors and Selection

JD Delancy
 

Morning Bill

Appears to be both, General Font and Decoded Font

    jd


locked Re: Colors and Selection

Bill Somerville
 

On 13/11/2020 11:30, JD Delancy wrote:
Roger/GW4HZA - no, Version 2.2.2 on a Fedora-33 work station box

Bill/G4WJS - If I change the font size to 12 pitch or less, the selection and the scroll bar appears
Hi JD,

for clarification, are you referring to the decoded text font size?

73
Bill
G4WJS.


locked Re: Something strange with WSJT-X

Bill Somerville
 

On 13/11/2020 11:22, Martin G0HDB wrote:
On Thu, Nov 12, 2020 at 01:49 PM, Bill Somerville wrote:

Hi Martin,

I have no idea why that is happening. Rather than deleting the whole WSJT-X.ini file you could try removing the entries in it that store the position, state, and geometry information. For the WSJT-X main window they look like this:

[MainWindow]
geometry=@ByteArray(\x1\xd9\xd0\xcb\0\x3\0\0\0\0\0\x4\0\0\x1P\0\0\x3\xb9\0\0\x3\xf5\0\0\0\f\0\0\x1o\0\0\x3\xb1\0\0\x3\xed\0\0\0\0\0\0\0\0\a\x80\0\0\0\f\0\0\x1o\0\0\x3\xb1\0\0\x3\xed)
geometryNoControls=@ByteArray(\x1\xd9\xd0\xcb\0\x3\0\0\0\0\0}\0\0\x1\x32\0\0\x3\x9e\0\0\x4\0\0\0\0\x85\0\0\x1Q\0\0\x3\x96\0\0\x3\xf8\0\0\0\0\0\0\0\0\a\x80\0\0\0\x85\0\0\x1Q\0\0\x3\x96\0\0\x3\xf8)
state=@ByteArray(\0\0\0\xff\0\0\0\0\xfd\0\0\0\0\0\0\x3\xa6\0\0\x2U\0\0\0\x4\0\0\0\x4\0\0\0\b\0\0\0\b\xfc\0\0\0\0)

You can safely delete the three key/value pairs (geometry, geometryNoControls, and state) from the [MainWindow] section. They will be recreated the next time you exit WSJT-X.

73
Bill
G4WJS.

Hi Bill, many thanks for the above.  Although I haven't yet tried editing the .INI file to remove those three key/value pairs I can see that they're in there, but...

When I did a search of the .INI file for the titles (geometry etc) I found several instances of them; do they also appear in the section of the .INI file for each individual configuration that's defined?  I currently have several (about ten!) different configs, for different modes and other operating preferences, and as far as I can tell each config has its own entries for those three key/value pairs in the .INI file.  Is my understanding correct?

73
--
Martin G0HDB

Hi Martin,

you are correct. The example entries I specified are for the currently selected configuration, there is no ambiguity as entries for non-current configurations are stored with different (augmented) keys. There are also entries for other top level windows.

My suggestion was to try deleting the entries specifically for the current configuration main window, which I assume was the one you were having difficulty with since you didn't state which one you were referring to, with the intention to see if deleting them helped. If it does help then that is useful fro determining what is going on.

73
Bill
G4WJS.


locked Re: Colors and Selection

JD Delancy
 

Roger/GW4HZA - no, Version 2.2.2 on a Fedora-33 work station box

Bill/G4WJS - If I change the font size to 12 pitch or less, the selection and the scroll bar appears


locked Re: Something strange with WSJT-X

Martin G0HDB
 

On Thu, Nov 12, 2020 at 01:49 PM, Bill Somerville wrote:

Hi Martin,

I have no idea why that is happening. Rather than deleting the whole WSJT-X.ini file you could try removing the entries in it that store the position, state, and geometry information. For the WSJT-X main window they look like this:

[MainWindow]
geometry=@ByteArray(\x1\xd9\xd0\xcb\0\x3\0\0\0\0\0\x4\0\0\x1P\0\0\x3\xb9\0\0\x3\xf5\0\0\0\f\0\0\x1o\0\0\x3\xb1\0\0\x3\xed\0\0\0\0\0\0\0\0\a\x80\0\0\0\f\0\0\x1o\0\0\x3\xb1\0\0\x3\xed)
geometryNoControls=@ByteArray(\x1\xd9\xd0\xcb\0\x3\0\0\0\0\0}\0\0\x1\x32\0\0\x3\x9e\0\0\x4\0\0\0\0\x85\0\0\x1Q\0\0\x3\x96\0\0\x3\xf8\0\0\0\0\0\0\0\0\a\x80\0\0\0\x85\0\0\x1Q\0\0\x3\x96\0\0\x3\xf8)
state=@ByteArray(\0\0\0\xff\0\0\0\0\xfd\0\0\0\0\0\0\x3\xa6\0\0\x2U\0\0\0\x4\0\0\0\x4\0\0\0\b\0\0\0\b\xfc\0\0\0\0)

You can safely delete the three key/value pairs (geometry, geometryNoControls, and state) from the [MainWindow] section. They will be recreated the next time you exit WSJT-X.

73
Bill
G4WJS.

Hi Bill, many thanks for the above.  Although I haven't yet tried editing the .INI file to remove those three key/value pairs I can see that they're in there, but...

When I did a search of the .INI file for the titles (geometry etc) I found several instances of them; do they also appear in the section of the .INI file for each individual configuration that's defined?  I currently have several (about ten!) different configs, for different modes and other operating preferences, and as far as I can tell each config has its own entries for those three key/value pairs in the .INI file.  Is my understanding correct?

73
--
Martin G0HDB


locked Re: No FT8 contacts, FT4 works perfectly! #FT8

Phil Davidson
 

Hi Steve.

Interesting situation that usually means something obvious, that’s in your face but u cant see it.

 

Could it be something like the radio swapping to LSB for that mode?

 

Also, u might try a look/hear at your signal using a remote Rx. Try WebSDR in Twente ..  http://websdr.ewi.utwente.nl:8901/

Or the RSGB SDR

 

Also, time is vital. I assume your ‘clock’ is good.

 

Regards – Phil (G0DOR)

 

Sent from Mail for Windows 10

 

From: Steve Thompson
Sent: 12 November 2020 21:51
To: WSJTX@groups.io
Subject: [WSJTX] No FT8 contacts, FT4 works perfectly!

 

Hi,

I am new to your group so apologise if this has been covered before; I have found similar posts but no definitive answer.

I have been using wsjtx with psk reporter and Log4Om through my ft991a and signalink, successfully since the start of June this year.

A few days ago ft8 tx stopped, according to psk reporter and lack of  contacts. Ft4 remains working well also according to psk reporter and instant replies to CQ calls, both on 20m.

I have checked my radio settings, usb and other connections (windows settings are correct according to signalink manual). I am getting a clear tone out of my laptop on monitor and power out is showing on my rig meter for both ft8 and ft4. I have been through filter settings and have updated wsjtx to 2.2.2. The only setting I have changed recently is data vox. I changed it back to 300ms, still no ft8.

Does psk reporter ever glitch? Everything appears to work apart from no contacts or reports! I have tried TX at both ends and middle of waterfall.

Am I missing something? Probably user error like usual! Maybe in filter settings or band width?

Thankyou in advance.

Steve 2E0WDM