1. main@WSJTX.groups.io
  2. Messages
   Date   
locked Re: WSJT-X 2.5.0 RC5 Not repeating RR73 when R report resent #FT8

Chris Hannagan
 

Hi Martin,
This may be somewhat specific to my operating technique.
When I am on HF I am invariably operating with call 1st checked as I seem to be unable to have just a single QSO.
I drag the Log QSO box over the main screen so that the Log QSO button is directly over the TX Enable button
Every time I log a QSO it is a double click that logs and re-enables the TX so that way the TX is enabled 99% of the time.
If a station comes back with the R-xx report the software used to immediately resend the RR73 message and then disengages the TX enable
On re-enabling the TX if the station again is still sending the RR-xx report the same behaviour happens - but now no longer.

I appreciate the comments regarding fox and hounds operation but Chathams is not rare enough to be able to get that sort of momentum going.
People need to be watching a F/H frequency for an expected DX operation to happen.
73
Chris zl7dx
locked Re: WSJT-X 2.5.0 RC5 Not repeating RR73 when R report resent #FT8

JJ Knight
 

I had the same issue and some others from just installing updates and not doing any clean installs.

I went to this folder and copied all of these files and folders into a separate folder: C:\Users\n5mnx\AppData\Local\WSJT-X   Then Delete this folder.

Then Uninstall WSJT-X completely, and then Delete the installation folder under:  C:\WSJT

Then do a clean install of 2.5.0 RC5. Drop your files you copied from C:\Users\n5mnx\AppData\Local\WSJT-X back into that same folder. 

Should come up clean, still have your logs and configuration files intact.

JJ N5MNX
locked Re: Audio and CAT errors #Cat_RigControl #AudioIssues

Chuck Moore
 

Bill

Thank you for the quick reply.

The USB Connectors were checked at both ends when the cable was
replaced yesterday. While not rock solid they were firmly in place for
a USB device.

The shack ground consists of a 10 gauge bare copper wire  run
along the shack table top back edge, primarily to mitigate the digital
noise. The PC, rig, and tuner are all bonded to the wire using strips of
copper flashing and the wire exits the window, to the ground and
attaches to the ground rod. Thus far I have seen no other indictators
of stray currents running around other than potentially this error message
popping up. Still it will be examined with a bit more scrutiny.

Thanks again for the guidance.

Chuck WD4HXG



classdesign.com> wrote:

On 05/09/2021 17:03, Chuck Moore via groups.io wrote:
In the middle of a contact and the screen down below the version
display with the
popup message about the "Error in Sound Card Input popped up again. It
is occur-
ring about once a day over the last three days.

Hi Chuck,

when both CAT control and audio fail, and they are both carried over the
same USB connection, it is invariably an RFI or physical issue with the
USB connection. You must ensure a good chassis bonding between your rig,
interface and PC, without that significant RF currents can flow over
data signalling lines like a USB connection and disrupt the
communications. Clip-on ferrites may not be sufficient to choke off
common mode RF currents on the USB connection.

73
Bill
G4WJS.
locked Re: Audio and CAT errors #Cat_RigControl #AudioIssues

Lynn Mears
 

So I’ve got to ask…

ULI sands for ??
It’s a file format and a company nvidia bought is all I can find.


and I’m pretty computer literate or thought I was!

Lynn, WA4FKX

On Sep 5, 2021, at 10:49 AM, Chuck Moore via groups.io <wd4hxg@...> wrote:


In the middle of a contact and the screen down below the version display with the
popup message about the "Error in Sound Card Input popped up again. It is occur-
ring about once a day over the last three days.

Software & Hardware list

WSJT-X
<PastedImage-4.png>

Windows 10 Pro
___________________


<PastedImage-5.png>
SCU-17 Interface (Yaesu)
FTdx-5000 (Yaesu) - set to less than 30 watts
Johnson Matchbox
450 Ohm Ladder line out of Matchbox to Horizontal Full Wave Loop for 80 Meters

Tried new USB cable last night after it showed up again second day. Have placed
Fair-Rite Type 31 suppression clamp cores on USB and RS-232 cable at end of
each cable on chance RF is getting into one of the cables.


<PastedImage-2.png>
Have to click OK
about six to ten times (number varies) and then this popup appears:

<PastedImage-3.png>

Clicking on 'Retry' results in what seems to be normal operation.

On the outside chance it might be OS related Microsoft claptrap
the machine was rebooted at 1 AM this morning. Will try shutdown,
power off and restart after sending this message.



Any ideas on what else I might try?

Regards

Chuck WD4HXG

locked Re: #txaudio #txaudio

KT7AZ
 

A quick fi to try when TX audio is lost is to go to the WSJT  audio settings and re-select your audio card.  Even though it shows to be already selected choose it again.

It is a short term possible solution, it is not in the Microsoft ULI I believe.
--
KT7AZ
locked Re: Audio and CAT errors #Cat_RigControl #AudioIssues

Brian Morrison
 

On Sun, 2021-09-05 at 16:03 +0000, Chuck Moore via groups.io wrote:
Any ideas on what else I might try?

Have you considered checking for a BIOS update for your motherboard?  You appear to have an ASUS m/board, and 2018 seems quite old for a board with an i9 CPU.

Just a thought.

-- 

Brian  G8SEZ
locked Re: Audio and CAT errors #Cat_RigControl #AudioIssues

Bill Somerville
 

On 05/09/2021 17:03, Chuck Moore via groups.io wrote:
In the middle of a contact and the screen down below the version display with the
popup message about the "Error in Sound Card Input popped up again. It is occur-
ring about once a day over the last three days.
Hi Chuck,

when both CAT control and audio fail, and they are both carried over the same USB connection, it is invariably an RFI or physical issue with the USB connection. You must ensure a good chassis bonding between your rig, interface and PC, without that significant RF currents can flow over data signalling lines like a USB connection and disrupt the communications. Clip-on ferrites may not be sufficient to choke off common mode RF currents on the USB connection.

73
Bill
G4WJS.
locked Audio and CAT errors #Cat_RigControl #AudioIssues

Chuck Moore
 

In the middle of a contact and the screen down below the version display with the
popup message about the "Error in Sound Card Input popped up again. It is occur-
ring about once a day over the last three days.
 
Software & Hardware list
 
WSJT-X                    PastedImage-4.png
 
Windows 10 Pro 
___________________ 
 
 
PastedImage-5.png
SCU-17 Interface (Yaesu)
FTdx-5000 (Yaesu) - set to less than 30 watts
Johnson Matchbox
450 Ohm Ladder line out of Matchbox to Horizontal Full Wave Loop for 80 Meters
 
Tried new USB cable last night after it showed up again second day. Have placed
Fair-Rite Type 31 suppression clamp cores on USB and RS-232 cable at end of
each cable  on chance RF is getting into one of the cables.
 
 
PastedImage-2.png Have to click OK 
about six to ten times (number varies) and then this popup appears:
  PastedImage-3.png
 
Clicking on 'Retry' results in what seems to be normal operation.
 
On the outside chance it might be OS related Microsoft claptrap
the machine was rebooted at 1 AM this morning.  Will try shutdown,
power off and restart after sending this message.
 
 
Any ideas on what else I might try?
 
Regards
 
Chuck WD4HXG 
locked Re: JT65 On 2m #JT65

Amos Sobel 4X4MF
 

Bill

Thanks for your help.

1. I am planning to go EME in the next few weeks. I have to install my yagi on a moon tracking rotator.
2. I am trying to verify my hardware by receiving something on 2m FT8, FT4, MSK144, Q65 and JT65 from Europe. So far only local stations received.
3. PSK Reporter does show JT65 activity in Europe. How can I receive it? What is the preferred configuration.

Amos 4X4MF

-----Original Message-----
From: main@WSJTX.groups.io <main@WSJTX.groups.io> On Behalf Of Bill Somerville
Sent: Sunday, September 5, 2021 6:48 PM
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] JT65 On 2m #JT65

On 05/09/2021 16:29, Amos Sobel 4X4MF wrote:
I am trying hard to work on 2m. FT8 does not function here because of
severe interference on 144.175 MHz.
Trying JT65A on 144.120 Mhz, I get the following:
<snip>
What's wrong here?

I am using Win 10. and WSJT-X v2.5.0-rc5.

Amos 4X4MF
Hi Amos,

JT65 is normally used on 2m for EME, are you trying EME?

There is nothing wrong, except that there are no signals to decode. The
JT65 decode in VHF and up mode will indicate sync detection, this is useful to home in on signals that may be there but in your case I expect they are simply false detections.

73
Bill
G4WJS.
locked Re: JT65 On 2m #JT65

Bill Somerville
 

On 05/09/2021 16:29, Amos Sobel 4X4MF wrote:
I am trying hard to work on 2m. FT8 does not function here because of severe interference on 144.175 MHz.
Trying JT65A on 144.120 Mhz, I get the following:
<snip>
What's wrong here?

I am using Win 10. and WSJT-X v2.5.0-rc5.

Amos 4X4MF
Hi Amos,

JT65 is normally used on 2m for EME, are you trying EME?

There is nothing wrong, except that there are no signals to decode. The JT65 decode in VHF and up mode will indicate sync detection, this is useful to home in on signals that may be there but in your case I expect they are simply false detections.

73
Bill
G4WJS.
locked Re: #IssueReport #WSPR #IssueReport #WSPR

Hasan Schiers N0AN
 

Last two days, it has behaved normally. Looks like it was a random glitch, possibly cleared by a reboot.
73, N0AN
Hasan


On Sat, Sep 4, 2021 at 12:35 PM Hasan Schiers N0AN via groups.io <hbasri.schiers6=gmail.com@groups.io> wrote:
Thanks Bill, I'll keep watch for it the next time it happens. It ran for two hours without that error this morning, but was doing it frequently yesterday
73, N0AN
Hasan


On Sat, Sep 4, 2021 at 12:21 PM Bill Somerville <g4wjs@...> wrote:
On 04/09/2021 13:34, Hasan Schiers N0AN wrote:
WSJT-X 2.5.0 RC5
Mode WSPR
 
Issue:
 
When in Band Hopping Mode, with a proper schedule, the Enable Transmit button randomly goes dark and never lights up again.
 
This results in hours and hours of listening overnight with no transmitting. 
 
Is there an order effect or something that would cause this in terms of setup? It used to work perfectly with identical settings many versions ago.
 
Anyone else seen this?
 
TIA, 73, N0AN
Hasan

Hi Hasan,

that behaviour may be caused by a CAT error. Have a look in the wsjtx_syslog.log file (in the WSJT-X log files directory) for any Hamlib error messages around the time that the "Enable Tx" button resets.

73
Bill
G4WJS.
locked JT65 On 2m #JT65

Amos Sobel 4X4MF
 

I am trying hard to work on 2m. FT8 does not function here because of severe interference on 144.175 MHz.
Trying JT65A on 144.120 Mhz, I get the following:



What's wrong here?

I am using Win 10. and WSJT-X v2.5.0-rc5.

Amos 4X4MF
locked Re: Virtual null modem cable for Linux #Cat_RigControl #linux

d_ziolkowski
 

Bill, Michael

I can't test at this time, CubicSDR will not allow me to enter a port manually. I have contacted the developer in regards to that issue. 

Thanks 

On Sat, Sep 4, 2021 at 2:54 PM Bill Somerville <g4wjs@...> wrote:
On 04/09/2021 17:59, d_ziolkowski wrote:
> Hi to all:
>
> OS Ubuntu 18.04, CubicSDR-2.5, WSJTX 2.1.0 . SDR Airspy HF+
> I am trying to get rig control from WSJTX to Cusbic SDR. So i need to
> create a VSP pair.
> I am using WSJTX 2.1, as the wspr band hopping works.
> I have tried socat, which creates the pair, but they are in dev/pts ,
> not dev/ as other serial ports are.
> $ socat -d -d pty,raw,echo=0 pty,raw,echo=0
> 2021/09/03 14:14:23 socat[25506] N PTY is /dev/pts/1
> 2021/09/03 14:14:23 socat[25506] N PTY is /dev/pts/2
> 2021/09/03 14:14:23 socat[25506] N starting data transfer loop with
> FDs [5,5] and [7,7]
> Does anybody know how to either:
> Get wsjtx and Cubic SDR to see them as they are in dev/pts rather then
> dev/?
> Move the ports to dev/
> There does appera to be a command it socat to link a vsp to another
> port, which I tried but still no connectity.
> Any help is appreciated
> Thanks
> Dan KC2STA

Hi Dan,

BTW what happens if you use /dev/pts/1 (or whatever) in the WSJT-X
"Settings->Radio->CAT Serial Port" field? Even though WSJT-X offers a
list of available tty devices it will accept any input there.

73
Bill
G4WJS.






--
Dan Ziolkowski KC2STA
SKCC #4290T
Ubuntu LINUX
locked Re: LoTW Confirmations #TechnicalHelpQuestion

Philip Rose
 

Patrick,

My return rate through LotW is 66%. I upload automatically to LotW and eQSL when I log each QSO (using HB logger). Receive rate for physical cards is 6% as I only send one in return for one I receive. I don't chase awards though.

--
73 Phil GM3ZZA
locked Re: #txaudio #txaudio

Tom Melvin
 

You have to read the ULI - important stuff in there - what to expect and what not to expect and recompense.

No point in going off on a rant when it’s documented that it may happen.

ULI, Terms and Conditions cookie policies etc are a must read.

Irresponsible if you don’t IMO

Tom
GM8MJV

On 5 Sep 2021, at 00:52, KT7AZ <kt7az.v69@...> wrote:

Oh, so your the guy who actually read the ULI, wow, never met anyone that did before. Anyway, you are right. I just wish you could do them on your own time. I have four repeater sites I am still running win7 Pro at. I just don’t want to drive up a mountain to reboot after the a win10 update cuts off the RealVNC connection. Guess this is one of things I am Pro Choice on.

Gary
--
KT7AZ

locked Re: LoTW Confirmations #TechnicalHelpQuestion

Tom Melvin
 

Thanks for that David

I was looking at the ‘proper’ bands - 6m and up - those are physical cards and LOTW as of 6months ago - will be applying for update soon so will check.

Tom
GM8MJV

On 5 Sep 2021, at 01:12, David VK3DRH <groups.io@...> wrote:

G'day Tom,

The RSGB also accepts Clublog for QSO verification for many of its HF awards.

Cheers, David VK3DRH

locked Re: #txaudio #txaudio

NR4U Bob AFMARS
 

Hello Pete Singleton via groups.io:
Thursday, September 2, 2021, 12:43:23 PM, you chiseled out:

I have a PC with Win10 Pro 64bit.  I use WSJT-X (now v2.4.0) for FT8.  I connect to my radio (various Icom, Yaesu) via an USB 'Audio Codec'.  The cabling is stable - I don't replug my USB ports.
This is happening to me, mostly with my Yaesu FT-450. The audio path ends up on the display's audio codec "usually" ...and randomly throiughout the day. thanks for writing this up.

--
Best regards,
Bob KD7YZ EM88LL



--
--
Bob KD7YZ in NE Kentucky
locked Re: "Error in Sound Input" (message box) Circle w/ RED X ---- my WSJT is "BRICKED" #AudioIssues #Windows10 #Elecraft

Phil Davidson
 

You don't mention Windows updates. Issues often occur after updates that 'decide' what the correct usb allocations should be.


On Sun, 5 Sep 2021, 07:39 , <bill333@...> wrote:
Thanks:  To All who have Helped
Understand that I have my computer stripped down to the most basic form, and able to successfully decode SAMPLE .wav files,  just as if I had no radio and wanted to experience WSJT-X.  There is no radio or cables connected and I have gone so far as to removing all Sound Card Drivers (Device Manager shows empty) and  SETTINGS: RADIO = NONE.  Yet when I touch MONITOR,  I Get the Error.

Further note, that my office computer,  6ft away, is a mirror hardware copy, and configured the identical way with WSJT-X , Yet  i get no error when I touch MONITOR.

I can only assume problem is within the computer.  Yes I have reloaded Windows 10.  It is further noted that I have been using FT-8 for a year with this rig, when suddenly it quit.

To prove my diagnosis....... I have ordered a longer CAT cable that will reach my office computer as well as new audio cables.   If this don't work I might want to change my brand of cologne.
Bill


locked Re: "Error in Sound Input" (message box) Circle w/ RED X ---- my WSJT is "BRICKED" #AudioIssues #Windows10 #Elecraft

Alan G4ZFQ
 

I have gone so far as to removing all Sound Card Drivers (Device Manager shows empty) and  SETTINGS: RADIO = NONE.  Yet when I touch MONITOR,  I Get the Error.
Bill,

Of course you will get an error!
With no working soundcard WSJT-X can not work.
You need a properly working sound device.

73 Alan G4ZFQ
locked Re: "Error in Sound Input" (message box) Circle w/ RED X ---- my WSJT is "BRICKED" #AudioIssues #Windows10 #Elecraft

Bill
 

Thanks:  To All who have Helped
Understand that I have my computer stripped down to the most basic form, and able to successfully decode SAMPLE .wav files,  just as if I had no radio and wanted to experience WSJT-X.  There is no radio or cables connected and I have gone so far as to removing all Sound Card Drivers (Device Manager shows empty) and  SETTINGS: RADIO = NONE.  Yet when I touch MONITOR,  I Get the Error.

Further note, that my office computer,  6ft away, is a mirror hardware copy, and configured the identical way with WSJT-X , Yet  i get no error when I touch MONITOR.

I can only assume problem is within the computer.  Yes I have reloaded Windows 10.  It is further noted that I have been using FT-8 for a year with this rig, when suddenly it quit.

To prove my diagnosis....... I have ordered a longer CAT cable that will reach my office computer as well as new audio cables.   If this don't work I might want to change my brand of cologne.
Bill
7161 - 7180 of 35419