Date   

locked WSJT-X shuts down unexpectedly (Raspberry Pi Raspian OS) #wsjt-x-crashing

S Johnson
 

I am using Raspberry Pi 4b with Raspian OS. WSJT-X version is 2.4.0 (latest). I am using a XGGCOMMS Digimode-4 interface. 

I just removed and re-installed WSJT-X,  I'm using FLRIG for control.  WSJT-X starts normally and I can see decodes happening normally. But the instant I try to make any change that communicates to the radio the program quits - no warning or errors, it just shuts down. Actions which cause shut down include:

  • Try to change bands via WSJTX UI
  • Click in the waterfall to set receive/transmit frequency 
  • Try to save configuration settings
  • Try to transmit. 
If I just sit there and watch the reception/decoding that all happens normally. 
Anyone know what might cause this (I have so much ferrite on my cables that there is a magnetic anomaly at my grid location), so I don't think RFI is an issue.  Also, before this recent remove/re-install of WSJTX the same equipment configuration was working well on transmit).


locked Re: Yaesu 991A how did you make it work with WSJT-X #AudioIssues #Yaesu

Adrian Fewster <vk4tux@...>
 

Carl, What is the issue with using usb-data rather than usb ?

73

Adrian Fewster


locked Re: Yaesu 991A how did you make it work with WSJT-X #AudioIssues #Yaesu

Carl Andreasen
 

I have the FT-991 and have no trouble at all. The Mic/Rear is a radio setting not WSJTX and the mode, should be set as USB not Data. Either VOX or CAT will key the radio.

On 8/9/21 5:07 PM, wisconsinjimmy wrote:
A lot of good people have tried their best to help so I am reluctant to try anymore, I am going to ask 1 more time, How did you get your 991A to transmit using WSJT-X without any addon help. I think the problem is in the settings of WSJT_X in the CAT control as I cannot get the option to select the Rear/Data option.
Jim KD9DOG


-- 
Warren - K7CWA
http://k7cwa.me


locked WSJT-X v2.5.0 ,rc5 / MAP86 v3.0.0, rc5 #map65 3.0 #map65

Ken
 

Gentlemen,

I just loaded WSJT-X v2.5.0, rc5 which includes MAP65 v3.0.0, rc5.
Everything seems to be working OK. I will test more tomorrow.

One Issue with MAP65:
Checking the box Iitialize IQ+ on startup still causes a Windows note that the program must be closed. After closing MAP65, it will not restart unless InitIQPlus=true is changed to InitIQPlus=false in the map65.ini file.

Is this problem on your list of future MAP65 fixes ?
This feature was nice to have and worked in MAP65 v2.7, r8182.

Ken - W8KEN


locked Re: Time Synch. #Timesync

Bill Somerville
 

On 10/08/2021 18:51, Dave Tucker Nu4N wrote:
I have had this problem before. Meinberg will not start.
--
Thanks 73's de NU4N/Dave
Dave,

a common reason for the Meinberg NTP CLient service not starting is that another NTP client is already running. For example if you have installed the SNTP client Dimension4 before then you *must* uninstall it and restart your system, then the Meinberg NTP Client service should start automatically.

Check the Windows Event Log for errors from the ntp service, they may well indicate that the NTP service port is in use which will block the service from starting.

73
Bill
G4WJS.


locked Re: Time Synch. #Timesync

 

I think it's time for a new computer.
Thanks for the help folks.
--
Thanks 73's de NU4N/Dave


locked Re: Time Synch. #Timesync

Colin
 

If Meinberg won’t start, is it giving an error message?

One way to find out:

Launch a Command Prompt with Run as Administrator. That will give you admin privileges to start/stop/restart services.

Try launching it manually.  (eg look at the batch file commands)

Net start ntp

 

See if it tells you what is wrong.

 

I’ve seen windows Updates install / reinstall / re-enable Win32time service.

You could run Services.msc

Then look at the properties for Windows Time service. Make sure it is not running, and startup is Disabled.

 

Another possibility is that Meinberg NTP is having trouble accessing a network port – something else might be attached to that port.

 

GL and 73 de VE3MSC Colin

 

From: main@WSJTX.groups.io <main@WSJTX.groups.io> On Behalf Of Dave Tucker Nu4N
Sent: August 10, 2021 13:52
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] Time Synch. #Timesync

 

I have had this problem before. Meinberg will not start.
--
Thanks 73's de NU4N/Dave


locked Re: Time Synch. #Timesync

Carlos
 

Hi, Dave, did you install Meinberg as Administrator ??
In my case it worked only if installed as Admin.....

73, Karl OE3JAG


Am 10.08.2021 um 19:51 schrieb Dave Tucker Nu4N:

I have had this problem before. Meinberg will not start.
--
Thanks 73's de NU4N/Dave





locked Re: Time Synch. #Timesync

 

I have had this problem before. Meinberg will not start.
--
Thanks 73's de NU4N/Dave


locked Re: Time Synch. #Timesync

 

Malware bytes showed nothing.
--
Thanks 73's de NU4N/Dave


locked Re: CM108 Support #Cat_RigControl

Dave Garber
 

Try setting ptt to vox,not cat and have vox on in the radio.  Maybe?


On Tue., Aug. 10, 2021, 12:23 p.m. Michael - NA7Q, <mike.ph4@...> wrote:
With most applications on Windows supporting CM108 sound cards for PTT. Where is WSJT-X on this? It should be natively supported, yet it's not supported at all. There are issues with using flrig and it. Basically if CAT isn't available on your setup, it won't work. Flrig supports PTT with CM108, but if CAT isn't enabled WSJT-X errors out. While other applications have no issue. 



locked Re: wsjtx with the IC-2730 #Icom

Dave Garber
 

And also. Ci-v is only for cat.   As far as i know


On Tue., Aug. 10, 2021, 12:33 p.m. Bill Somerville, <g4wjs@...> wrote:
On 10/08/2021 17:22, George Weller wrote:
> wsjt-x shows the IC-2730 as a supported rig.  Looks like it might work
> with just CI-V (no Signalink).  Has anyone tried this?  73, KD9PCN

George,

WSJT-X requires an SSB transceiver.

73
Bill
G4WJS.





locked Re: Time Synch. #Timesync

Bill Seward
 

Get familiar with the “ping” command, then try pinging some of the time servers by name, ie time.foo.bar. If you don’t get replies, it’s a possibility that your home router is blocking the traffic. I’m not sure how most home routers come set up these days, but when I was running firewalls and routers professionally, one of the first things we did was block ping traffic for security purposes.

 

Bill


locked Re: wsjtx with the IC-2730 #Icom

Bill Somerville
 

On 10/08/2021 17:22, George Weller wrote:
wsjt-x shows the IC-2730 as a supported rig.  Looks like it might work with just CI-V (no Signalink).  Has anyone tried this?  73, KD9PCN
George,

WSJT-X requires an SSB transceiver.

73
Bill
G4WJS.


locked wsjtx with the IC-2730 #Icom

George Weller
 

wsjt-x shows the IC-2730 as a supported rig.  Looks like it might work with just CI-V (no Signalink).  Has anyone tried this?  73, KD9PCN


locked CM108 Support #Cat_RigControl

Michael - NA7Q
 

With most applications on Windows supporting CM108 sound cards for PTT. Where is WSJT-X on this? It should be natively supported, yet it's not supported at all. There are issues with using flrig and it. Basically if CAT isn't available on your setup, it won't work. Flrig supports PTT with CM108, but if CAT isn't enabled WSJT-X errors out. While other applications have no issue. 


locked Re: Odd behavior upon starting WSJTX #WSJTX_config #Cat_RigControl

Dave Garber
 

Did you move the usb to a different usb port.   Might be why usb0 now sorks


On Tue., Aug. 10, 2021, 10:02 a.m. Joe N0NOW, <traylor.joe@...> wrote:
Mike, you hit the target!  Thanks for your persistence!   ttyUSB0 brings instant CAT green light!   It's not clear to me why, however, since, ttyUSB0 had NEVER worked before. 

The outcome is not clean yet.  Now no signals decode.  Will be exploring this tomorrow and will post results.

Thanks,
Joe N0NOW



locked Re: Yaesu 991A how did you make it work with WSJT-X #AudioIssues #Yaesu

Richard Bertrand Larson
 

My tx audio on my 991A and Fine business making many QSO's

KD0XD Rick en12

On 8/9/2021 7:07 PM, wisconsinjimmy wrote:
A lot of good people have tried their best to help so I am reluctant to try anymore, I am going to ask 1 more time, How did you get your 991A to transmit using WSJT-X without any addon help. I think the problem is in the settings of WSJT_X in the CAT control as I cannot get the option to select the Rear/Data option.
Jim KD9DOG


--
There are no facts , only interpretations - Resistance is NOT futile, it's Voltage divided by Current - There's no time like the present for postponing what you don't want to do. HECHT'S FOURTH LAW


locked Re: Fw: Double Logging #logging

Bill Somerville
 

On 10/08/2021 14:15, Jim Johnson KC4HW wrote:
 
 
----- Original Message -----
From: Jim Johnson <jim@...>
Sent: 8/10/2021 8:14:53 AM
Subject: Double Logging

Using WSJT-X 2.5.0-rc3, JTAlert 2.50.4 and N3FJP 7.0.1
 
It appears that while using MSK144 that each station worked is double logged.  I have not noticed this with any other mode.
 
Something I have wrong? or just a WSJT-X anomaly?
 
Jim/KC4HW - EM71 Alabama

Hi Jim,

unless the double log entries are in the WSJT-X ADIF log file the issue is unlikely to be anything to do with WSJT-X or its settings.

73
Bill
G4WJS.


locked Re: Yaesu 991A how did you make it work with WSJT-X #AudioIssues #Yaesu

Bill Somerville
 

On 10/08/2021 14:38, wisconsinjimmy wrote:
When you first download WSJT-X in the install options there are three choices  do not add to system path, add to path for all users and add for current user I have been using the default should I add to system path
Jim KD9DOG
Hi Jim,

adding the WSJT-X binary path to the system PATH variable is not necessary unless you have specific requirements to run any of the command line tools from a command prompt, and even they it is probably not worth the trouble. For running WSJT-X from the Desktop shortcut it is definitely not needed.

73
Bill
G4WJS.

7881 - 7900 of 35397