Date   

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

Bill Somerville
 

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,

WSJT-X (actually Hamlib) expects a CAT connection to be a tty, a pty is not the same thing as it doesn't include the modem control signal lines. There may be some virtual null modem cable applications available although I am not sure if any are included in the Ubuntu repositories.

73
Bill
G4WJS.


locked Virtual null modem cable for Linux #Cat_RigControl #linux

d_ziolkowski
 

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


locked Re: WSJT-X 2.5.0 RC5 Not repeating RR73 when R report resent #FT8

Bill Somerville
 

On 04/09/2021 19:01, Chris Hannagan wrote:

Thank you Phil but I do understand the operator requirements for it RR73 to be resent.

As I said “Running this afternoon” as in - a pileup with call 1st checked and auto sequence checked, and on several occasions the station came back with R-xx and my end did not repeat the RR73 message and proceeded on to the next caller at the top of the call 1st list.

My problem is that trying to respond to the R-xx station causes me (and the pileup) to get out of sync and the whole momentum gets lost

What I am pointing out is that this action differs to previous versions where the RR73 message became resent and TX-enable was again turned off.

73

Chris zl7dx

Chris,

this is the main reason that we recommend not using the RR73 response when it is possible that it may not be copied. Of course sometimes that just happens even when propagation is good. You can always respond to the repeated R+report message from your QSO partner by double-clicking the decoded message.

As for the "Pile-up" and you getting out of sync, I do not understand that at all. Are you saying that you do not want to complete a QSO with a station who does not hear your first RR73 response?

73
Bill
G4WJS.


locked Re: WSJT-X 2.5.0 RC5 Not repeating RR73 when R report resent #FT8

Chris Hannagan
 

Thank you Phil but I do understand the operator requirements for it RR73 to be resent.

As I said “Running this afternoon” as in - a pileup with call 1st checked and auto sequence checked, and on several occasions the station came back with R-xx and my end did not repeat the RR73 message and proceeded on to the next caller at the top of the call 1st list.

My problem is that trying to respond to the R-xx station causes me (and the pileup) to get out of sync and the whole momentum gets lost

What I am pointing out is that this action differs to previous versions where the RR73 message became resent and TX-enable was again turned off.

73

Chris zl7dx


locked Re: WSJT-X 2.5.0 RC5 Not repeating RR73 when R report resent #FT8

 

I do sometimes worry about cat control, because occasionally he lies with his bum against the main dial. I know I can lock the dial with the IC-7300. Does that stop CAT control from changing frequency?

 

Phil GM3ZZA

 

Sent from Mail for Windows

 

From: Brian Morrison
Sent: 04 September 2021 18:00
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] WSJT-X 2.5.0 RC5 Not repeating RR73 when R report resent #FT8

 

On Sat, 2021-09-04 at 08:39 +0100, Philip Rose via groups.io wrote:

I know this afternoon I made a few mistakes, as I had a cat lying on the mouse cable - .

 

Better than a mouse chewing on the CAT cable.

 

-- 

 

Brian  G8SEZ

 

 


--
73 Phil GM3ZZA


locked Re: #IssueReport #WSPR #IssueReport #WSPR

Hasan Schiers N0AN
 

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 Re: #IssueReport #WSPR #IssueReport #WSPR

Bill Somerville
 

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 Re: WSJT-X 2.5.0 RC5 Not repeating RR73 when R report resent #FT8

Brian Morrison
 

On Sat, 2021-09-04 at 08:39 +0100, Philip Rose via groups.io wrote:
I know this afternoon I made a few mistakes, as I had a cat lying on the mouse cable - .

Better than a mouse chewing on the CAT cable.

-- 

Brian  G8SEZ


locked Re: LoTW Confirmations #TechnicalHelpQuestion

Ron Schunk
 

HI...I run eQSL automatically via JTAlert (click on the option)...QRZ.com allows you the ability to download from lotw into QRZ...I use both...if I can't get a confirmation (which I've tried several time via email to the station), I just give it up and move on...there are plenty of amateurs out there...configure your JTALERT callsign box to show eqsl and lotw and pick your contacts...
WA8KQF
Ron

Virus-free. www.avast.com


On Sat, Sep 4, 2021 at 11:17 AM Patrick Hung <pathung@...> wrote:
Hi All,

Thank you all very much for your comments, as well to those who emailed me with their thoughts directly.

In sum, it seems that I will need to collect physical cards from these missing DXs, and submit them to a local checker. Thanks to Brian's link, I have a found an ARRL checker within 50 miles of me; I'll take my cards and a printout from ARRL's online QSL entry form to him when ready. 

All of your suggestions were excellent, and I've tried a few of them, one being researching the DX's instructed methods on QRZ.com for requesting a card ($3 via Paypal etc.); some have instructions, some don't. I've also checked for my callsign in some of their ClubLog accounts - again, some upload their QSOs while some don't - it's a real crapshoot. I've sent off a few requests with funds via ClubLog's OQRS, but have not seen anything sent to me for my efforts - one of you mentioned your return ratio as being 80% - looks like I'm hitting the 20% first. I am now considering having JTAlert filter stations with LoTW accounts, I'll consider others on a case by case basis.

In any case, I have my question answered - thank you all, again, very much!!

--
73,
Patrick, W6AJR



locked Re: LoTW Confirmations #TechnicalHelpQuestion

Jim Shorney
 

It can take a while to get a card via ClubLog OQRS. Be patient.

73

-Jim
NU0C

On Sat, 04 Sep 2021 08:17:36 -0700
"Patrick Hung" <pathung@...> wrote:

I've sent off a few requests with funds via ClubLog's OQRS, but have not seen anything sent to me for my efforts


locked Re: LoTW Confirmations #TechnicalHelpQuestion

Patrick Hung
 

Hi All,

Thank you all very much for your comments, as well to those who emailed me with their thoughts directly.

In sum, it seems that I will need to collect physical cards from these missing DXs, and submit them to a local checker. Thanks to Brian's link, I have a found an ARRL checker within 50 miles of me; I'll take my cards and a printout from ARRL's online QSL entry form to him when ready. 

All of your suggestions were excellent, and I've tried a few of them, one being researching the DX's instructed methods on QRZ.com for requesting a card ($3 via Paypal etc.); some have instructions, some don't. I've also checked for my callsign in some of their ClubLog accounts - again, some upload their QSOs while some don't - it's a real crapshoot. I've sent off a few requests with funds via ClubLog's OQRS, but have not seen anything sent to me for my efforts - one of you mentioned your return ratio as being 80% - looks like I'm hitting the 20% first. I am now considering having JTAlert filter stations with LoTW accounts, I'll consider others on a case by case basis.

In any case, I have my question answered - thank you all, again, very much!!

--
73,
Patrick, W6AJR


locked Re: #txaudio #txaudio

KT7AZ
 

Something else that helps with Power Saving mode killing sound cards and USB devices.

go to Win 10 control panel, (make sure your view is “Large Icons”). View selections is on top right of screen.

then select “Power Options”, Once there make sure “High Performance” is selected.  Then to the right of this selection click on “Change Plan Settings”

Here you will see an option to click on “Change advanced power settings”. Click 

A new window will appear, expand all the options, you can set timers for suspend, sleep etc.  I either disable all of them or put the most outrageous time I can.  

The USB settings are very important,  disable the “ USB selective suspend settings”.

This all helps but Microsoft seems to think they know better than you and will do things on their unsolicited updates.

Good luck,
Gary
--
KT7AZ


locked Re: #txaudio #txaudio

KT7AZ
 
Edited

When Win 10 does one of the upgrades from say 20H? To 20H?? It resets many of your hardware settings to default, this includes your sound cards.  These default settings include “power save” modes.  Unfortunately these settings are notorious for breaking the sound card settings used.  I have found that my sound card would quit working when computer screen would turn off buy the timer I set in Windows.

I finally gave up and turned that feature off.

you can also go to Control Panel, Device Manager and right click your hardware devices one by one, right click and select Properties, then look for a tab called “Power Management”.  Once there uncheck the box next to “Allow the computer to turn off this device to save power”

Not sure why Microsoft forces this feature, guess they are just green zealots.

Gary
KT7AZ
--
KT7AZ


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

 

Phil,

 

I find that W10 only gets confused if you move USB cables around. I tend to keep my cables connected. HF Rig and USB hub in the back of the PC. Keyboard, webcam/microphone, mouse and VHF rig programming cable in the hub.

 

I made the mistake of unplugging them while I tidied the desk wiring to remove unnecessary walwart cables adding 100 Hz crosstalk to the rig DC cables. That’s the only time I’ve had to rename the USB Audio codecs for the rig. Also I think the rig has its serial number encoded in the USB interface.

 

73 Phil GM3ZZA

 

Sent from Mail for Windows

 

From: Phil Davidson
Sent: 04 September 2021 08:47
To: main@wsjtx.groups.io
Subject: Re: [WSJTX] "Error in Sound Input" (message box) Circle w/ RED X ---- my WSJT is "BRICKED" #Windows10 #Elecraft #AudioIssues #AudioIssues

 

Did u try resetting the USB system?

Windows tends to get usb inputs confused. It keeps a 'list' that can be cleared. This usually fixes the problem.

 

 

On Tue, 24 Aug 2021, 05:42 , <bill333@...> wrote:

"so try a Windows restart"  .....was suggested...... yes I did a restart ....I did a zillion restarts while troubleshooting

Please note that ..................my radio is disconnected and OFF
Please note again that ........Rig = none
Please note again that ........FT-8 sample files decode flawlessly and repeatedly with clicking DECODE button

Please note again that ..     "Error in Sound Input" happens immediately when I click MONITOR button

Please note that .................I have been using wsjt-x for 2 years with same hardware and connections.
Pleaase note that................I have uninstalled and tries different wsjt-x versions many many many times

 


--
73 Phil GM3ZZA


locked #IssueReport #WSPR #IssueReport #WSPR

Hasan Schiers N0AN
 

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


locked Re: #txaudio #txaudio

Alan G4ZFQ
 

Pete

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.
You must make your on-board sound default for PC sounds.
I'm not sure how you can be sure of being completely stable when you change rigs. Windows may see them as different devices, if it does there is a good chance it will reconfigure.

If you setup one rig and make sure it is switched on when you reboot then you have a good chance of retaining settings. That would also work if you use two rigs simultaneously. Unfortunately any change may alter configuration.

Have all power saving turned off including HDMI screens.

73 Alan G4ZFQ


locked Re: #txaudio #txaudio

Phil Davidson
 


On Thu, 2 Sep 2021, 18:01 Pete Singleton via groups.io, <pete.singleton.46=googlemail.com@groups.io> wrote:
Hi

I hate Windows 10.  It keeps messing with my audio setup.  

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.

When I boot up the PC, turn on the radio and load WSJT-X Rx seems fine but the Tx audio usually doesn't work.  The volume mixer shows that audio outputs are randomly scrambled. Often the audio from 'system sounds' and/or browsers go to the 'Radio In' codec but WSJT-X audio goes to the 'Display Audio' speakers.

To unscramble the mess I unload WSJT-X,  use 'Sound Settings' to disable the 'Radio In' codec to force everything to go to  'Display Audio'.  After reloading WSJT-X I go back to 'Sound Settings' and check that the WSJT-X audio (and no others) goes to 'Radio In'.

Occasionally, reasons unknown, the scrambling re-occurs if I come back to the radio after being away for a while.  Same procedure sorts it out.

Does anyone know how to fix the setup to be stable?

73 de M0PTB
 



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

Phil Davidson
 

Did u try resetting the USB system?
Windows tends to get usb inputs confused. It keeps a 'list' that can be cleared. This usually fixes the problem.


On Tue, 24 Aug 2021, 05:42 , <bill333@...> wrote:
"so try a Windows restart"  .....was suggested...... yes I did a restart ....I did a zillion restarts while troubleshooting

Please note that ..................my radio is disconnected and OFF
Please note again that ........Rig = none
Please note again that ........FT-8 sample files decode flawlessly and repeatedly with clicking DECODE button
Please note again that ..     "Error in Sound Input" happens immediately when I click MONITOR button
Please note that .................I have been using wsjt-x for 2 years with same hardware and connections.
Pleaase note that................I have uninstalled and tries different wsjt-x versions many many many times



locked Re: WSJT-X 2.5.0 RC5 Not repeating RR73 when R report resent #FT8

 

It needs specific operator behaviour to enable the resending of RR73 in this case. When RR73 is sent, Enable TX is disabled. If the operator re-enables it, the sequence will resend RR73 if R-xx is received or to CQ if either 73 or no reply is received.

 

I know this afternoon I made a few mistakes, as I had a cat lying on the mouse cable - .

 

73 Phil GM3ZZA

 

Sent from Mail for Windows

 

From: Chris Hannagan
Sent: 04 September 2021 07:39
To: main@WSJTX.groups.io
Subject: [WSJTX] WSJT-X 2.5.0 RC5 Not repeating RR73 when R report resent #FT8

 

Running this afternoon on FT8 on 20 metres I noticed that if the station resends the R-dB report the sequence is ignoring it and carrying on to the next QSO rather than resending the RR73
This may be intentional but it is a change in behaviour.
I saw this multiple times today
73
Chris zl7dx

 


--
73 Phil GM3ZZA


locked WSJT-X 2.5.0 RC5 Not repeating RR73 when R report resent #FT8

Chris Hannagan
 

Running this afternoon on FT8 on 20 metres I noticed that if the station resends the R-dB report the sequence is ignoring it and carrying on to the next QSO rather than resending the RR73
This may be intentional but it is a change in behaviour.
I saw this multiple times today
73
Chris zl7dx

11821 - 11840 of 40041