Date   

locked Re: #mac Support for Icom radio Silicon Labs a big issue getting bigger all the time #macOS

K3JRZ
 

Silicon Labs has updated drivers for Big Sur 11.x.

On Thu, Feb 4, 2021 at 15:11 km6hk via groups.io <km6hk=iCloud.com@groups.io> wrote:
Icom radios use Silicon Labs VCP Driver packages.
and now that package (after a recent uprgade of my mac to macOS Catalina Version 10.15.7)
shows this message




--

Thanks & 73,

Jeff
K3JRZ
100WAAW #404

--

Thanks & 73,

Jeff
K3JRZ
100WAAW #404


locked #mac Support for Icom radio Silicon Labs a big issue getting bigger all the time #macOS

km6hk@...
 

Icom radios use Silicon Labs VCP Driver packages.
and now that package (after a recent uprgade of my mac to macOS Catalina Version 10.15.7)
shows this message


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

Karza
 

On 4.2.2021 18.52, Mike Lavelle K6ML wrote:
JT4 decodes crash v2.4.0-rc1(-win64).   Happens repeatedly, often on first decode.

Does not happen Q65/FT4/FT8/JT65/JT9 modes.
Crash also happens on Linux Ubuntu 18.04.5 LTS

Running: /home/karza/ham/wsjtx/wsjtx240-rc1/bin/jt9 -s "WSJT-X - eirikia" -w 1 -m 3 -e /home/karza/ham/wsjtx/wsjtx240-rc1/bin -a "/home/karza/.local/share/WSJT-X - eirikia" -t "/tmp/WSJT-X - eirikia"
At line 13 of file /home/karza/ham/wsjtx/wsjtx240-rc1/build/wsjtx-prefix/src/wsjtx/lib/pctile.f90
Fortran runtime error: Index '-53' of dimension 1 of array 'tmp' below lower bound of 1

Error termination. Backtrace:
#0  0x7f3781d4f32a
#1  0x7f3781d4fed5
#2  0x7f3781d502a7
#3  0x559a6299b6b0
#4  0x559a62a0edc7
#5  0x559a6299f7c1
#6  0x559a629a041e
#7  0x559a62999128
#8  0x559a6298f1d4
#9  0x559a6298e6da
#10  0x559a6298c5ae
#11  0x7f3780df6bf6
#12  0x559a6298c619
#13  0xffffffffffffffff

73's de Kari, oh2gqc


locked Re: WSJTX Install Fail on Pi64bit #install #linux #IssueReport

Ken Hendrickson
 

Thanks Bill, It installs on the Pi os 64 fine. I am wondering if they are working on the 64 bit version at all. It still runs very slowly compared to the 32 bit version.


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

Mike Lavelle K6ML
 

JT4 decodes crash v2.4.0-rc1(-win64).   Happens repeatedly, often on first decode.

Does not happen Q65/FT4/FT8/JT65/JT9 modes.

---- error message ----

Subprocess failed with exit code 2:

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

At line 13 of file C:\Users\bill\src\k1jt\wsjtx\lib\pctile.f90

Fortran runtime error: Index '-26' of dimension 1 of array 'tmp' below lower bound of 1

 

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

#6 0xffffffff

#7 0xffffffff

#8 0xffffffff

#9 0xffffffff

#10 0xffffffff

#11 0xffffffff

#12 0xffffffff

#13 0xffffffff

#14 0xffffffff

#15 0xffffffff


locked Re: #Install #BugReport #WSJTX_config WSJT-X not working after 2.3.0 install #install #IssueReport #WSJTX_config

Karl Beckman WA8NVW - AFA5VB
 

Working as designed!  The internal and external plug-in sound cards are not supposed to appear in WSJTX if they are set to either DEFAULT or COMM DEFAULT devices.  Adjust your Windows 10 sound settings for each from the Windows Sound control panel to undo those two default settings which broadcasts alert sounds from MS Windows, WSJT, and GridTracker over the air, annoying LOTS of hams. 
If you are a senior op like me, it's helpful to rename your WSJT-X sound card dongle to something like "Dongle Tx Out" and "Dongle Rx In."  I also renamed my USB headset as HSTx-Mic and HSRx-Ear.  Here's a clean link:  https://winaero.com/rename-audio-device-windows-10/
--
Karl  WA8NVW  OH
WA8NVW@...
in WSJTX@groups.io


locked Re: I see my own callsign in the Band Activity Window #QSO_practices #FT8 #transmit

Jim KM6GUO
 

A few details... Running 2.2.2 on RPi. Radio is a Yaesu 857D. RigBlaster Advantage. (I believe I have also seen this when running 2.2.2 on Windows - same radio).
--
Jim
KM6GUO


locked I see my own callsign in the Band Activity Window #QSO_practices #FT8 #transmit

Jim KM6GUO
 

I see my own CQ on the activity window. Is that a good thing? Something I am doing wrong? It happens after the watchdog terminates transmit - and the timestamp corresponds to when it was transmitted. If I am transmitting on 00 and 30, it comes in on 15 or 45 after the watchdog stopped transmit - so it corresponds to the last transmit.
--
Jim
KM6GUO


locked Re: #BugReport #IssueReport

Bill Somerville
 

On 04/02/2021 16:25, David Ackrill wrote:

I've used the hastag "BugReport" as there didn't seem to be anything else that would cover this.

Using Q65 today someone, on one of the KST Chat rooms, mentioned that it was taking a long time from the end of a reception period before the decoded message appeared in the left-hand 'message' window on his set up.

I put a stopwatch on it, on my set up, and found the following delay from when the blue "Decoding" button came on until when the display put the previous RX period results up.

Q65-15A = 7 seconds, 15B = 6 seconds and C = 5 seconds. Q65-30A = 7 seconds, B = 7.5 seconds and C = 6 seconds.  The 'decoding' button does come up before the end of the RX period, of course, but the decoded message still took between 3 and 5 seconds to appear after the end of the RX period.  The other guy on the forum was reporting the decode not coming up until nearly the end of the transmit period on his set up at times, I have tried to be careful not to load up a lot of 'stuff' onto this 'new' (refurbished) machine so as not to slow it up too much.

I also noticed that, at times, the blue 'decoding' button stayed on well into the next period, but I couldn't say why, or whether that was supposed to happen, so I've ignored it at the moment.

Has anyone else noticed a significant delay in decoding on Q65?

Cheers - Dave (G0DJA)
Dave,

that decoding takes many millions of CPU cycles, it cannot be instant. There will surely be some optimizations that speed things up but this is just the first release candidate and there are still some rough edges. Use a narrower FTol once you know where your QSO partners are and decoding will be much faster. If you are on a sked then check the "Settings->General->Single decode" option to save the decoder having to look for signals outside of the FTol frequency window.

73
Bill
G4WJS.


locked #BugReport #IssueReport

David Ackrill
 

I've used the hastag "BugReport" as there didn't seem to be anything else that would cover this.

Using Q65 today someone, on one of the KST Chat rooms, mentioned that it was taking a long time from the end of a reception period before the decoded message appeared in the left-hand 'message' window on his set up.

I put a stopwatch on it, on my set up, and found the following delay from when the blue "Decoding" button came on until when the display put the previous RX period results up.

Q65-15A = 7 seconds, 15B = 6 seconds and C = 5 seconds.  Q65-30A = 7 seconds, B = 7.5 seconds and C = 6 seconds.  The 'decoding' button does come up before the end of the RX period, of course, but the decoded message still took between 3 and 5 seconds to appear after the end of the RX period.  The other guy on the forum was reporting the decode not coming up until nearly the end of the transmit period on his set up at times, I have tried to be careful not to load up a lot of 'stuff' onto this 'new' (refurbished) machine so as not to slow it up too much.

I also noticed that, at times, the blue 'decoding' button stayed on well into the next period, but I couldn't say why, or whether that was supposed to happen, so I've ignored it at the moment.

Has anyone else noticed a significant delay in decoding on Q65?

Cheers - Dave (G0DJA)


locked Re: WSJT-X 2.4.0 RC1 ceash MacOS #IssueReport

Bill Somerville
 

On 04/02/2021 14:42, alex wrote:
I just installed 2.4.0 RC1 next to 2.3.0 on MacOS Big Sur
The previous version runs OK, but the RC crashes after about 1 minute of monitoring FT8.
During the first period all stations are decoded correctly, the second period WSJT-X crashes.
This occurs also if the settings page is open.

73's de PE1EVX, Alex
Hi Alex,

see this post from the wsjt-devel Source Forge list:

https://sourceforge.net/p/wsjt/mailman/message/37212133/

73
Bill
G4WJS.


locked Re: Multiple Instances of WSJTX .. #FT8 #WSJTX_config

Bill Somerville
 

On 04/02/2021 14:13, Dave H wrote:

Hi Bill,

Many Thanks...

Another Q.? I assume I will therefore need a UDP Port Nos# per instance.

73 Dave G8LIY
Hi Dave,

that is not necessary when using multicast IP, but some servers, notably JTAlert, do not handle multicast quite right and require each WSJT-X instance to send to a different service port :(

73
Bill
G4WJS.


locked Re: #bugreport #IssueReport

Mike Lavelle K6ML
 

I get the exact same error running 2.4.0-rc1-win64 at the end of first JT4 decode period.

Does not happen in Q65/FT8/FT4 modes, will try some others


locked Re: Is this supposed to happen? #FoxAndHound #IssueReport

Tony Collett
 

Thanks Bill (& Dave)

I realised this was expected behaviour, as you say 3 periods then moved into what I called "no mans land" .
Good to know that if propagation or QRM allowed it would probably have completed even though I successfully chose to start fresh above 1000Hz.

What I didn't expect was that there appeared to be no time out on my subsequent transmissions while I was sending the report. - For the record how long would I have continued to transmit his report - is this set by the usual Tx timer that is set for "normal" FT8 mode or would it have continued forever until I decided to give up?

Thanks
Tony G4NBS


locked Re: #install - WSJT-X 2.3.0 Annoyance #install

w5ec
 

What was the idea behind the box?


locked WSJT-X 2.4.0 RC1 ceash MacOS #IssueReport

alex
 

I just installed 2.4.0 RC1 next to 2.3.0 on MacOS Big Sur
The previous version runs OK, but the RC crashes after about 1 minute of monitoring FT8.
During the first period all stations are decoded correctly, the second period WSJT-X crashes.
This occurs also if the settings page is open.

73's de PE1EVX, Alex


locked Re: Multiple Instances of WSJTX .. #FT8 #WSJTX_config

Dave H
 

Hi Karza,

Thanks.. 73 Dave G8LIY


locked Re: Multiple Instances of WSJTX .. #FT8 #WSJTX_config

Dave H
 

Hi Amos..

Thanks... I plan to use.? GRIDTRACKER if I can

73 Dave G8LIY


locked Re: Multiple Instances of WSJTX .. #FT8 #WSJTX_config

Dave H
 

Hi Bill,

Many Thanks...

Another Q.? I assume I will therefore need a UDP Port Nos# per instance.

73 Dave G8LIY


locked Re: #install - WSJT-X 2.3.0 Annoyance #install

Bob K4RCG
 

HIHIHI I find the freq box handy! :-)  I have a few FST4W skeds with DX stations and we use the freq to help ID traces of the participating stations if operating "random".  I don't know how to turn it off, but it is easier when using FST4W than "hovering" over the traces to ID the Hz.

73 de Bob
K4RCG

On Thu, Feb 4, 2021 at 1:40 PM Jon Ermels via groups.io <n0igu=yahoo.com@groups.io> wrote:
Amen

73 de NØIGU Jon


On Wednesday, February 3, 2021, 10:01:52 AM CST, Nathern Priddy via groups.io <nbpriddy=aol.com@groups.io> wrote:


I just downloaded and installed WSJT-X 2.3.0.  In this version, there is a little box on the waterfall that follows the cursor showing the frequency that the cursor is at.  I find this to be a distraction and an annoyance. 

I've searched for a way to turn the box off, but no success.  Is there a way to turn this box off?

Barry Priddy - K5VIP/KG4BP






13941 - 13960 of 35492