Date   

locked Alerts Sound Not Working #AudioIssues

Doug Bates - WB4JPG
 

I turned Sound ON and when there's an Alert JTAlert crashes.

When I go to Settings > Wanted Grid > Alert Sound and select Test JTAlert crashes.

Below is the output from Event Viewer > Windows Logs > Application

Faulting application name: JTAlertV2.Manager.exe, version: 2.50.1.0, time stamp: 0x602c44b3
Faulting module name: msvcrt.dll, version: 7.0.19041.546, time stamp: 0x564f9f39
Exception code: 0xc0000005
Fault offset: 0x0000000000074452
Faulting process id: 0x3040
Faulting application start time: 0x01d771291c8ce79b
Faulting application path: C:\Program Files (x86)\HamApps\JTAlert\pluginsX\JTAlertV2.Manager.exe
Faulting module path: C:\WINDOWS\System32\msvcrt.dll
Report Id: 902acfc6-be74-4bfd-bdea-560c4f7a5f43
Faulting package full name: 
Faulting package-relative application ID: 


locked Re: #WSJT-X #and #Flex-6400 #radio #FlexRadio #wsjt-x

Al Groff
 

If your not using WSJT-X v2.4.0 , you may wish to update..  That version solved some of the same problems for me.

AL, K0VM


On 7/3/2021 11:40 PM, Brian Stucker wrote:
Yes. I occasionally get this with my Flex 6400. I think the problem is with DAX (I’m on version 3.12ish). When the problem crops up it’s usually when I’ve been connecting DAX to different stations fairly quickly. 

I never see the problem on RX, just TX audio so I’m guessing there’s a bug somewhere in DAX. 

This all assumes that you’ve already made the change in windows to not allow USB ports to sleep. 

B

On Fri, Jul 2, 2021 at 9:56 PM Dennis Wage <dwage@...> wrote:
Is anyone having problems with the current version of WSJT-X stopping sending any tones to the radio, either tx or tune? The radio keys and everything looks normal but no tones are getting to the radio.

A restart of WSJT-X always fixes it and one time that I know of, it just started working again without a restart.









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

Niece KA1ULN <ka1uln1@...>
 

yes  i am  getting  same   error as Lance w7gj

i have been getting this rror for over 4 weeks now. using 2.3, 2.4 and 2.5 but went back to 2.4 hoping to get away from the error
here is the error (comes up very very very often and i have to restart) IS MY SETUP INCORRECT? plz help i cannot run wsjtx
*********************************************************************
Running: C:\WSJT\wsjtx\bin\jt9 -s WSJT-X -w 1 -m 3 -e C:\WSJT\wsjtx\bin -a C:\Users\raspb\AppData\Local\WSJT-X -t C:\Users\raspb\AppData\Local\Temp\WSJT-X
At line 616 of file C:\Users\bill\src\k1jt\wsjtx\lib\decoder.f90 (unit = 13, file = 'C:\Users\raspb\AppData\Local\Temp\WSJT-X/decoded.txt')
Fortran runtime error: Cannot write to file opened for READ
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


locked Re: Subprocess Error exit code 2

Niece KA1ULN <ka1uln1@...>
 

is that the   solution  because i am  not   saving  either
here is  my error... mostly with  decoded.txt

i have been getting this rror for over 4 weeks now. using 2.3, 2.4 and 2.5 but went back to 2.4 hoping to get away from the error
here is the error (comes up very very very often and i have to restart) IS MY SETUP INCORRECT? plz help i cannot run wsjtx
*********************************************************************
Running: C:\WSJT\wsjtx\bin\jt9 -s WSJT-X -w 1 -m 3 -e C:\WSJT\wsjtx\bin -a C:\Users\raspb\AppData\Local\WSJT-X -t C:\Users\raspb\AppData\Local\Temp\WSJT-X
At line 616 of file C:\Users\bill\src\k1jt\wsjtx\lib\decoder.f90 (unit = 13, file = 'C:\Users\raspb\AppData\Local\Temp\WSJT-X/decoded.txt')
Fortran runtime error: Cannot write to file opened for READ
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


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

Michael Black
 

What antivirus are you running?

Make sure that directory is excluded from scanning.

Mike W9MDB




On Sunday, July 4, 2021, 02:09:09 PM CDT, Niece KA1ULN <ka1uln1@...> wrote:


full error message  and  STILL happening?

i have been getting this rror for over 4 weeks now. using 2.3, 2.4 and 2.5 but went back to 2.4 hoping to get away from the error
here is the error (comes up very very very often and i have to restart) IS MY SETUP INCORRECT? plz help i cannot run wsjtx
*********************************************************************
Running: C:\WSJT\wsjtx\bin\jt9 -s WSJT-X -w 1 -m 3 -e C:\WSJT\wsjtx\bin -a C:\Users\raspb\AppData\Local\WSJT-X -t C:\Users\raspb\AppData\Local\Temp\WSJT-X
At line 616 of file C:\Users\bill\src\k1jt\wsjtx\lib\decoder.f90 (unit = 13, file = 'C:\Users\raspb\AppData\Local\Temp\WSJT-X/decoded.txt')
Fortran runtime error: Cannot write to file opened for READ
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




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

Niece KA1ULN <ka1uln1@...>
 

full error message  and  STILL happening?

i have been getting this rror for over 4 weeks now. using 2.3, 2.4 and 2.5 but went back to 2.4 hoping to get away from the error
here is the error (comes up very very very often and i have to restart) IS MY SETUP INCORRECT? plz help i cannot run wsjtx
*********************************************************************
Running: C:\WSJT\wsjtx\bin\jt9 -s WSJT-X -w 1 -m 3 -e C:\WSJT\wsjtx\bin -a C:\Users\raspb\AppData\Local\WSJT-X -t C:\Users\raspb\AppData\Local\Temp\WSJT-X
At line 616 of file C:\Users\bill\src\k1jt\wsjtx\lib\decoder.f90 (unit = 13, file = 'C:\Users\raspb\AppData\Local\Temp\WSJT-X/decoded.txt')
Fortran runtime error: Cannot write to file opened for READ
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


locked Re: Clock Sync #Timesync

Kevin McQuiggin (VE7ZD/KN7Q)
 

On 04/07/2021 15:40, Jim Pennino via groups.io wrote:
Re fake chips: I have no idea and don't care though u-blox might. The only features used by ntp is the output of NMEA sentences so any other capability the u-blox 8 series has is irrelevant to ntp. FYI u-blox makes dozens of different chips with different capabilities all of which identify as u-blox 8.

Actually ntpd doesn’t work very well using NMEA sentences via USB or serial port as input.  This is because of variance in the timing of the serial data stream and the way that the machine's CPU responds to interrupts on the serial or USB port from the GPS where the GPS unit is connected.  Timing can be all over the map due to CPU workload and other tasks which are running.

If you have a local GPS receiver, then a FAR better approach is to use a pulsed output from the device to generate a high priority interrupt that is handled directly by the time management processes.  This involves another daemon called gpsd and use of a GPS receiver that outputs a nanosecond-accurate “pulse per second” signal.  Cheap receivers usually do not provide a PPS signal but several slightly more expensive ones do.  

There is a good writeup on how to do this at https://www.lammertbies.nl/comm/info/gps-time.  

I use a Garmin Garmin 18x LVC GPS Navigator Unit, which is available on Amazon for about USD$68.  See the link for how to connect what to where!

73,

Kevin VE7ZD/KN7Q






Hi Jim,

one issue with "fake" u-blox boards (note they usually have real u-blox GPS/GNSS receivers but lack on the rest of the board) is that some have insufficiently sized SPI memory chips and as a result cannot be upgraded to newer firmware versions. That can be annoying if a new satellite constellation needs to be supported, for example.

73
Bil
G4WJS.






locked Re: Clock Sync #Timesync

Bill Somerville
 

On 04/07/2021 15:40, Jim Pennino via groups.io wrote:
Re fake chips: I have no idea and don't care though u-blox might. The only features used by ntp is the output of NMEA sentences so any other capability the u-blox 8 series has is irrelevant to ntp. FYI u-blox makes dozens of different chips with different capabilities all of which identify as u-blox 8.
Hi Jim,

one issue with "fake" u-blox boards (note they usually have real u-blox GPS/GNSS receivers but lack on the rest of the board) is that some have insufficiently sized SPI memory chips and as a result cannot be upgraded to newer firmware versions. That can be annoying if a new satellite constellation needs to be supported, for example.

73
Bil
G4WJS.


locked Re: No TX with v2.4.0 and IC-7610 #TechnicalHelpQuestion

Martin G0HDB
 

On Sun, Jul 4, 2021 at 01:10 AM, Tad Danley wrote:
I downloaded WSJT-X v2.4.0 and configured it to work with my IC-7610 - using my settings for N1MM+ as a guide.  I am able to decode stations using FT8 on 50.313 but the radio will not key the transmitter.  I have Enable TX selected and the button is Red. The right side of the WSJT window shows I am transmitting with my 'transmissions' highlighted in yellow, but the rig does not key. Under Settings and the Radio tab I have the following set:

Rig is IC-7610, Serial port is Com 3, Baud rate is 115200, 8 data bits and 1 stop bit, Handshake is set to hardware, Force control lines are both unselected, PTT method is VOX, Transmit audio source is unselected, Mode is USB, Split is set to Fake it.  Under Soundcard the Input is defaulted to Microphone (USB Audio codec).

I would appreciate any help with what I need to change to get it to TX properly.  Thanks and 73!
I'm not sure if VOX PTT works when you're using the audio codec as the source of the incoming Tx audio; try selecting CAT for the PTT method in WSJT-X.

As has already been mentioned you should also be selecting the 7610's USB-D mode for operation rather than plain ol' USB, and you'll have also have to go into the settings menu and select 'USB' as the DATA1 MOD input (go to Menu -> Connectors -> MOD Input -> DATA1 MOD -> USB).

--
Martin G0HDB


locked Re: #No TX with WSJT-X 2.4.0

Ray
 

Look at ICOM knowledge base for documentation on digital settings. For the IC 7300 setting power to 100% is recommended then use TF8 slider to set power out to desired. Green ALC is ok, just don’t go into red.  No ALC or little ALC  means no or little power out. Just look at power meter when transmitting. The power control is MAX power out, not a power control. I don’t know if this applies to 7610 but it probably does.

No ALC does not apply to all radios especially since FT8 is a constant power mode so read the manual. 
Ray
W8LYJ


locked Re: WSJT-X No Longer Opens on Raspberry Pi 3B+ #install #raspberryPi

Mendoza
 

Hello. I have same problem with same library in Ububtu 18. 

I had wsjtx 2.1.2 running fine on ubuntu 18. Then I went to update to 2.3.0 and it just never launched, although icon was there. I did uninstall and try several "tricks" but never launched. In the software center I had weird record saying I had 2.3.0 uninstalled and 2.1.2 installed. I did format my HD and install Ubuntu 18 from scratch to delete any inaccurate license record. Now with a clean fresh updated ubuntu 18, wsjtx 2.4.0 wont install (a bunch of dependency problems).
I have noticed that wsjtx.2.4.0...deb file is i386 for ubuntu 18, 32 bits, when ubuntu 18 is actually 64 bits (intell/amd 64). I am guessing there is the problem. The only wsjtx.2.4.0...deb file amd64 is stated for ubuntu 20, not 18.

I have narrowed down the error on installing wsjtx 2.4.0 on ubuntu 18 to the following:
"Unpacking wsjtx:i386 (2.4.0) ...
dpkg: dependency problems prevent configuration of wsjtx:i386:
wsjtx:i386 depends on libboost-log1.65.1."
This is preventing wsjtx to be completely installed. I do have wsjtx icon and when clicking to start, it just stays in sand-clock for a while and then I get a warning in ubuntu saying I have installed a package with unment dependencies. When I run the "fix" bay means of "partial upgrade" or by "sudo apt-get install -f" it automatically removes wsjtx because it is the problem.
“The following packages will be REMOVED:
wsjtx:i386”
The weird thing is that the libboost-log1.65.1 is actually installed as seen below:


ham@ham-V5-131:~$ apt list libboost-log1*

Listing... Done

libboost-log1.62-dev/bionic 1.62.0+dfsg-5 amd64

libboost-log1.62.0/bionic 1.62.0+dfsg-5 amd64

libboost-log1.65-dev/bionic,now 1.65.1+dfsg-0ubuntu5 amd64 [installed,automatic]

libboost-log1.65.1/bionic,now 1.65.1+dfsg-0ubuntu5 amd64 [installed]

 

ham@ham-V5-131:~$ cd Downloads

ham@ham-V5-131:~/Downloads$ sudo dpkg -i wsjtx_2.4.0_i386.deb

[sudo] password for ham:

Selecting previously unselected package wsjtx:i386.

(Reading database ... 190398 files and directories currently installed.)

Preparing to unpack wsjtx_2.4.0_i386.deb ...

Unpacking wsjtx:i386 (2.4.0) ...

dpkg: dependency problems prevent configuration of wsjtx:i386:

wsjtx:i386 depends on libboost-log1.65.1.

 

dpkg: error processing package wsjtx:i386 (--install):

dependency problems - leaving unconfigured

Processing triggers for gnome-menus (3.13.3-11ubuntu1.1) ...

Processing triggers for desktop-file-utils (0.23-1ubuntu3.18.04.2) ...

Processing triggers for mime-support (3.60ubuntu1) ...

Processing triggers for man-db (2.8.3-2ubuntu0.1) ...

Errors were encountered while processing:

wsjtx:i386

ham@ham-V5-131:~/Downloads$



Any help? Thanks.


locked Re: Clock Sync #Timesync

Jim Pennino
 

Re time1 vs time2: I am running the latest release of Meinberg and can state time1 does what it is supposed to do. If you are running an older version you should upgrade because many other bugs have been fixed.

Re cables: You can attach the VK-162 to your Pi if you don't have a serial GPS HAT and use it as a ntp server. There is a thumb drive receiver, VK-172, that uses the u-blox 7 chip set which eliminates the cables but isn't generally useful inside a building and has much more jitter than the VK-162.

Re fake chips: I have no idea and don't care though u-blox might. The only features used by ntp is the output of NMEA sentences so any other capability the u-blox 8 series has is irrelevant to ntp. FYI u-blox makes dozens of different chips with different capabilities all of which identify as u-blox 8.

Re Rubidium standard: The price I gave was for a frequency standard only. The price for the box with timekeeping ability is about $870, which should indicate why I haven't already tried one. GNSS-RB GPS GNSS Disciplined  Rubidium BG7TBL Rubidium Atomic Clock on e-bay.


locked Re: logging to HRD Logbook #logging

Bill M
 

I used HRD for many years(2010 al;l versions) and had no troubles, and none since logging since adding of WSJT-x FT8 and JTAlert a couple of years ago. Use what you like but avoid trashing others!
Bill W2CQ


locked Re: logging to HRD Logbook #logging

Gilbert Baron
 

Outlook Laptop Gil W0MN
Hierro candente, batir de repente
44.08226N 92.51265W EN34rb

-----Original Message-----
From: main@WSJTX.groups.io <main@WSJTX.groups.io> On Behalf Of Bruce Jungwirth via groups.io
Sent: Saturday, July 3, 2021 14:58
To: main@wsjtx.groups.io
Subject: Re: [WSJTX] logging to HRD Logbook #logging

I’ve been using WSJTX and JTAlert logging to HRD for over 2years and have never had a problem. Have I just been lucky?

YES


Bruce, K0SON
On Jul 3, 2021, at 10:22 AM, Robert Lorenzini <bob@...> wrote:

Expect HRD to be problematic on a regular basis.

Bob - wd6dod

On 7/3/2021 6:27 AM, Michael E Wilson Sr wrote:
I recently changed from DXKeeper log to HRD Logbook. The change was easy and worked. However, when JTAlert was set to log to HRD Logbook, I got triple entries in the log. Two of the entries were from JTAlert, one of which was flagged in the log with "date/time error". I disabled the JTAlert logging and every thing returned to normal with only WSJT-X providing the log info.
What is going on. Does the HRD Logbook network server port have anything to do with this issue? When I was using DXKeeper, every thing work great.






--
W0MN EN34rb 44.08226 N 92.51265 W

Hierro candente, batir de repente

HP Laptop


locked Re: logging to HRD Logbook #logging

Michael E Wilson Sr <ke5wct@...>
 

Turned off the secondary UDP and problem solved. Thanks.


locked VS: [WSJTX] received qsy when responding to a CQ #FT8 #wsjt-x #QSO_practices

Reino Talarmo
 

>the wsjt freq window turned red.

Mike,

No problem, as the QSY frequency was not defined as a working frequency for the band/mode. I think that it is just a reminder.

73, Reino OH3mA


locked Re: No TX with v2.4.0 and IC-7610 #TechnicalHelpQuestion

Derek Brown
 

Tad

The 7610 
Needs to be in mode USB Data.,  select USB and then select Data. 

73 Derek G8ECI






-------- Original message --------
From: Tad Danley <tdanley@...>
Date: 04/07/2021 01:10 (GMT+00:00)
To: main@WSJTX.groups.io
Subject: [WSJTX] No TX with v2.4.0 and IC-7610 #help

I downloaded WSJT-X v2.4.0 and configured it to work with my IC-7610 - using my settings for N1MM+ as a guide.  I am able to decode stations using FT8 on 50.313 but the radio will not key the transmitter.  I have Enable TX selected and the button is Red. The right side of the WSJT window shows I am transmitting with my 'transmissions' highlighted in yellow, but the rig does not key. Under Settings and the Radio tab I have the following set:

Rig is IC-7610, Serial port is Com 3, Baud rate is 115200, 8 data bits and 1 stop bit, Handshake is set to hardware, Force control lines are both unselected, PTT method is VOX, Transmit audio source is unselected, Mode is USB, Split is set to Fake it.  Under Soundcard the Input is defaulted to Microphone (USB Audio codec).

I would appreciate any help with what I need to change to get it to TX properly.  Thanks and 73!

-- 
Tad Danley, K3TD


locked Re: #WSJT-X #and #Flex-6400 #radio #FlexRadio #wsjt-x

Brian Stucker
 

Yes. I occasionally get this with my Flex 6400. I think the problem is with DAX (I’m on version 3.12ish). When the problem crops up it’s usually when I’ve been connecting DAX to different stations fairly quickly. 

I never see the problem on RX, just TX audio so I’m guessing there’s a bug somewhere in DAX. 

This all assumes that you’ve already made the change in windows to not allow USB ports to sleep. 

B

On Fri, Jul 2, 2021 at 9:56 PM Dennis Wage <dwage@...> wrote:
Is anyone having problems with the current version of WSJT-X stopping sending any tones to the radio, either tx or tune? The radio keys and everything looks normal but no tones are getting to the radio.

A restart of WSJT-X always fixes it and one time that I know of, it just started working again without a restart.





locked Re: Clock Sync #Timesync

Alan B
 

I've built a few NTP servers with various serial GPS's on the Pi ZeroW and 3B+ using PPS. Not hard to build and they support the whole Field Day group with a little low power box. We used two on Field Day this year. Client machines go on and off, so not a good source for sharing fundamental resources like NTP. Different choices for different purposes. Personally I don't care for a USB cable on my laptop, would rather get the NTP over the network, and VNC to the Pi to do digital modes, so the laptop doesn't have cables festooned all over the place. Also this USB GPS fails to restart properly on my laptop after it awakes from sleep mode whereas the networked NTP restarts smoothly. But this is a great low cost and simple solution for many use-cases and good to have in our bag of tools.

I'm running Meinberg NTPD on Windows 10 and time1 had no effect at all, I changed it to time2 and the offset started working properly. It may not be the latest version of Meinberg, but can't be too old as the laptop isn't that old. Something to try for folks that have no result from varying time1 - try time2. Use whatever works.

At $15 the u-blox in the VK-162 is almost certainly a fake chip copy, unfortunately (I didn't take it apart but the price point is indicative). I've used them (fakes) before in other modules and they usually work well but have various flaws or missing features, but these are unlikely to be important for NTP purposes. This puck works better than others I have tested, thanks for posting this info. This is perhaps the Baofeng of USB GPS pucks.

73 de w6akb


On Sat, Jul 3, 2021 at 5:39 PM Robert Lorenzini <bob@...> wrote:


On 7/3/2021 9:26 AM, Jim Pennino via groups.io wrote:


The VK-162 uses the u-blox 8 chip set which is GNSS, not just GPS, and has 72 channels. I could post a list of all the chip sets I have tested but see no point in it as the VK-162 has been shown to be the best of the cheap ones out there so far and again goes for about $15. If I find a better one, I will post it.

Nice choice (u-blox) and well supported.
Bob - wd6dod




    





locked Re: #Transmit #transmit

Karza
 

Tad,

On 3.7.2021 21.59, Tad Danley wrote:
I downloaded WSJT-X v2.4.0 and configured it to work with my IC-7610 - using my settings for N1MM+ as a guide.  I am able to decode stations using FT8 on 50.313 but the radio will not key the transmitter.  I have Enable TX selected and the button is Red. The right side of the WSJT window shows I am transmitting with my 'transmissions' highlighted in yellow, but the rig does not key. Under Settings and the Radio tab I have the following set:

Rig is IC-7610, Serial port is Com 3, Baud rate is 115200, 8 data bits and 1 stop bit, Handshake is set to hardware, Force control lines are both unselected, PTT method is VOX, Transmit audio source is unselected, Mode is USB, Split is set to Fake it.  Under Soundcard the Input is defaulted to Microphone (USB Audio codec).
I assume you are using single USB-cable between your rig and computer.

Try setting PTT method to "CAT", TX audio soutce to "Rear/data" and mode to "Data/Pkt".

You also need rig menus to set up correctly. I recently sold my 7610 so I cannot help you there but I'm sure there are some 7610 users on the list who can.

73's de Kari, oh2gqc

10781 - 10800 of 36959