Date   

locked Re: rig.c(972):rig_open error on K2 #Cat_RigControl

Karza
 

On 27.3.2021 17.47, traylor.joe@... wrote:

I am connecting a K2 with PC running Ubuntu 20.04. wsjtx 2.3.0 configuration gives rig.c(972):rig_open error.

 

I have settings Serial Port /dev/ttyUSB0, Baud 4800, 8 data bits, 2 stop bits, NONE handshake, PTT set to CAT, Mode set to USB, Split Op set to None. The PC properly sees the FTDI cable and /dev/ttyUSB0 is identified with it.

 

The K2 is hearing signals. I have the K2 headphone output connected to PC mic input. The PC spkr output is connected to the K2 mic input. This arrangement worked correctly when I was used PTT set for VOX control; now trying to use CAT control, I get the error.

Please help.  Thanks.  Joe


Check that your user-id is a member of the 'dialout' group.

If not, use command "sudo adduser $USER dialout" to add it.

Then log off / log on again ( or reboot ).

73's de Kari, oh2gqc


locked Re: Two program releases: WSJT-X 2.3.1 (GA) and WSJT-X 2.4.0-rc4 #Q65

Bill Somerville
 

On 27/03/2021 16:14, w5ec wrote:
Sounds like a plan as I am not interested in Q65 at this time.
Best place to get 2.3.1?
Thanks
Bill W5EC
https://physics.princeton.edu/pulsar/K1JT/wsjtx.html

73
Bill
G4WJS.


locked Re: Two program releases: WSJT-X 2.3.1 (GA) and WSJT-X 2.4.0-rc4 #Q65

w5ec
 

Sounds like a plan as I am not interested in Q65 at this time.
Best place to get 2.3.1?
Thanks
Bill W5EC


locked Re: rig.c(972):rig_open error on K2 #Cat_RigControl

Bill Somerville
 

On 27/03/2021 15:47, traylor.joe@... wrote:

I am connecting a K2 with PC running Ubuntu 20.04. wsjtx 2.3.0 configuration gives rig.c(972):rig_open error.

 

I have settings Serial Port /dev/ttyUSB0, Baud 4800, 8 data bits, 2 stop bits, NONE handshake, PTT set to CAT, Mode set to USB, Split Op set to None. The PC properly sees the FTDI cable and /dev/ttyUSB0 is identified with it.

 

The K2 is hearing signals. I have the K2 headphone output connected to PC mic input. The PC spkr output is connected to the K2 mic input. This arrangement worked correctly when I was used PTT set for VOX control; now trying to use CAT control, I get the error.

Please help.  Thanks.  Joe

Hi Joe,

there should be more to the error message, can you provide the full details please?

73
Bill
G4WJS.


locked rig.c(972):rig_open error on K2 #Cat_RigControl

Joe N0NOW
 

I am connecting a K2 with PC running Ubuntu 20.04. wsjtx 2.3.0 configuration gives rig.c(972):rig_open error.

 

I have settings Serial Port /dev/ttyUSB0, Baud 4800, 8 data bits, 2 stop bits, NONE handshake, PTT set to CAT, Mode set to USB, Split Op set to None. The PC properly sees the FTDI cable and /dev/ttyUSB0 is identified with it.

 

The K2 is hearing signals. I have the K2 headphone output connected to PC mic input. The PC spkr output is connected to the K2 mic input. This arrangement worked correctly when I was used PTT set for VOX control; now trying to use CAT control, I get the error.

Please help.  Thanks.  Joe


locked Re: WSJT-X using Mac OS Catalina

Bill, W8BC
 

What transceiver are you using, wwindham?
--
Bill
W8BC


locked Re: Two program releases: WSJT-X 2.3.1 (GA) and WSJT-X 2.4.0-rc4 #Q65

Joe
 

Hi Les,

Thanks for the report!  Delighted to hear that you're enjoying Q65 for EME on 23 cm.

  -- Joe, K1JT


locked Re: #FT8 receptions report on PSK #FT8

Jacques Pecourt
 

Thank you Bill.  This makes sense and is certainly the reason. As you know, we  talked about that long ago, WSJT restriction does not allow me to incorporate the grid after CQ suqre as shown with the ft8/code. I will try your suggestion.

73's  Jacques.

On Sat, 27 Mar 2021 at 11:05, Bill Somerville <g4wjs@...> wrote:
On 27/03/2021 14:45, Jacques Pecourt wrote:
I have to ask the following question: I have not been able to understand  why PSK Reporter.only recognizes me as a :"Monitor station" (large bubble with no L inside). Is the fact I use a "compound call sign:'' the reason?  I have uploaded thousands of files to Lotw for years, even occasionally being called by stations with no CQ sent on my side. I would assume that all my settings are right (check in the reporting box, 6 characters in the grid number, antenna description/band).
Any suggestions or explanations on this issue?.Thank you.

Jacques  W2/F2YS.

Hi Jacques,

WSJT-X only spots to PSKReporter decodes with gridsquares. Try sending this after some of your QSOs:

DE F2YS FN31

73
Bill
G4WJS.





locked Re: #FT8 receptions report on PSK #FT8

Bill Somerville
 

On 27/03/2021 14:45, Jacques Pecourt wrote:
I have to ask the following question: I have not been able to understand  why PSK Reporter.only recognizes me as a :"Monitor station" (large bubble with no L inside). Is the fact I use a "compound call sign:'' the reason?  I have uploaded thousands of files to Lotw for years, even occasionally being called by stations with no CQ sent on my side. I would assume that all my settings are right (check in the reporting box, 6 characters in the grid number, antenna description/band).
Any suggestions or explanations on this issue?.Thank you.

Jacques  W2/F2YS.

Hi Jacques,

WSJT-X only spots to PSKReporter decodes with gridsquares. Try sending this after some of your QSOs:

DE F2YS FN31

73
Bill
G4WJS.


locked #FT8 receptions report on PSK #FT8

Jacques Pecourt
 

I have to ask the following question: I have not been able to understand  why PSK Reporter.only recognizes me as a :"Monitor station" (large bubble with no L inside). Is the fact I use a "compound call sign:'' the reason?  I have uploaded thousands of files to Lotw for years, even occasionally being called by stations with no CQ sent on my side. I would assume that all my settings are right (check in the reporting box, 6 characters in the grid number, antenna description/band).
Any suggestions or explanations on this issue?.Thank you.

Jacques  W2/F2YS.


locked Re: Two program releases: WSJT-X 2.3.1 (GA) and WSJT-X 2.4.0-rc4 #Q65

Les Listwa
 

Hi Joe and team,

Just want to  report a successful, quick and easy 1296 EME Q65-30 contact with a report of -27 db. Nice to see a real time signal report.   And just want to mention the auto doppler correction is pure magic, making 1296 mhz contacts so much easier. 

73
Les
W2LPL


locked Re: Ubuntu 20.04 & wsjtx2.3.0 ALSA audio HW:x,y challenges #AudioIssues #linux

Bill Somerville
 

On 27/03/2021 11:04, mike.j.kasper@... wrote:
I've spent WAY to much time trying to get WSJTX to share the audio input.  The primary goal is to get FLDIGI & WSJTX to share an input for decoding, but utilizing the DSNOOP option or trying to directly access the HW audio results in: "Error in Sound Input Requested input audio format is not supported on device".  Only using PLUGHW: "works"

I found that I have a USB microphone that does work with the DSNOOP, but both my radio USB audio card and the internal audio card refuse.  Strange thing is, the USB microphone (snowball) ONLY support S16_LE, while the other cards support other formats.

Audio card details:

Card 0, ID `Digital', name `Shure Digital'
  Device 0, ID `USB Audio', name `USB Audio', 1 subdevices (1 available)
    1..2 channels, sampling rate 8000..48000 Hz
    Sample formats: S8, S16_LE
      Subdevice 0, name `subdevice #0'
Card 1, ID `Snowball', name `Blue Snowball'
  Device 0, ID `USB Audio', name `USB Audio', 1 subdevices (1 available)
    1 channel, sampling rate 8000..48000 Hz
    Sample formats: S16_LE
      Subdevice 0, name `subdevice #0'
Card 2, ID `PCH', name `HDA Intel PCH'
  Device 0, ID `ALC231 Analog', name `ALC231 Analog', 1 subdevices (1 available)
    2 channels, sampling rate 44100..192000 Hz
    Sample formats: S16_LE, S32_LE
      Subdevice 0, name `subdevice #0'

Any pointers on what format wsjtx is asking for and/or why these cards refuse direct hardware (aka requiring PLUGHW)???
OM,

WSJT-X requests 48,000 Hz 16-bit little endian, but pulseaudio will do the necessary conversion if that is not available in the hardware. Some users have reported that changing the duplex settings of some sound cards is necessary.

73
Bill
G4WJS.


locked Re: #FT8 #FT8

Bill Somerville
 

On 27/03/2021 13:35, Jerry Lofstead wrote:
I can no longer find the menu on/off option in the .ini file.  what happened to it.  I want to see the menu bar.
Jerry W3CDE
Jerry,

what's wrong with checking/unchecking the "Menus" box to the right of the central row of buttons?

73
Bill
G4WJS.


locked Re: Two program releases: WSJT-X 2.3.1 (GA) and WSJT-X 2.4.0-rc4 #Q65

Bill Somerville
 

On 27/03/2021 13:55, w5ec wrote:
I have been using wsjtx xv2.1.2 from way back and are perfectly happy with it. I now want to go to v2.4.0 for all the improvements. What is best way to upgrade?
I want to be able to go back to v2.1.2 if bugs cause me problems. I don't want it to affect my settings. At my age I don't want any more problems!
Bill W5EC
Hi Bill,

unless you are interested in exploring the new Q65 mode I would recommend upgrading to v2.3.1 rather than the v2.4.0 release candidates.

73
Bill
G4WJS.


locked Re: Two program releases: WSJT-X 2.3.1 (GA) and WSJT-X 2.4.0-rc4 #Q65

w5ec
 

I have been using wsjtx xv2.1.2 from way back and are perfectly happy with it. I now want to go to v2.4.0 for all the improvements. What is best way to upgrade?
I want to be able to go back to v2.1.2 if bugs cause me problems. I don't want it to affect my settings. At my age I don't want any more problems!
Bill W5EC


locked #FT8 #FT8

Jerry Lofstead W3CDE
 

I can no longer find the menu on/off option in the .ini file.  what happened to it.  I want to see the menu bar.
Jerry W3CDE


locked 10m Q65/30A Testing 27Mar21 28.135MHz #Q65

Bob K4RCG
 

As known, Q65 was not developed for 10m, but remains an interesting possibility.  Testing today 28.135 MHz if anyone is around.

73 de Bob
K4RCG


locked Ubuntu 20.04 & wsjtx2.3.0 ALSA audio HW:x,y challenges #AudioIssues #linux

mike.j.kasper@...
 

I've spent WAY to much time trying to get WSJTX to share the audio input.  The primary goal is to get FLDIGI & WSJTX to share an input for decoding, but utilizing the DSNOOP option or trying to directly access the HW audio results in: "Error in Sound Input Requested input audio format is not supported on device".  Only using PLUGHW: "works"

I found that I have a USB microphone that does work with the DSNOOP, but both my radio USB audio card and the internal audio card refuse.  Strange thing is, the USB microphone (snowball) ONLY support S16_LE, while the other cards support other formats.

Audio card details:

Card 0, ID `Digital', name `Shure Digital'
  Device 0, ID `USB Audio', name `USB Audio', 1 subdevices (1 available)
    1..2 channels, sampling rate 8000..48000 Hz
    Sample formats: S8, S16_LE
      Subdevice 0, name `subdevice #0'
Card 1, ID `Snowball', name `Blue Snowball'
  Device 0, ID `USB Audio', name `USB Audio', 1 subdevices (1 available)
    1 channel, sampling rate 8000..48000 Hz
    Sample formats: S16_LE
      Subdevice 0, name `subdevice #0'
Card 2, ID `PCH', name `HDA Intel PCH'
  Device 0, ID `ALC231 Analog', name `ALC231 Analog', 1 subdevices (1 available)
    2 channels, sampling rate 44100..192000 Hz
    Sample formats: S16_LE, S32_LE
      Subdevice 0, name `subdevice #0'

Any pointers on what format wsjtx is asking for and/or why these cards refuse direct hardware (aka requiring PLUGHW)???


locked Re: program release WSJT-X 2.4.0-rc4 #linux #IssueReport #MSK144

Carlos
 

Hi to all,
Thanks für the new two program versions.
On 2.4.0-rc4 I found out that in MSK144 the call is not copied to the standard messages wehen doubleclick on a CQ call.
You have to double click the CQ call line in the Band Activity window.
then Generate Std Msgs
and the Enable TX.
In my opinion I found it useful to take over the call in the Std Msgs.
73, TU, Karl OE3JAG


locked Re: Two program releases: WSJT-X 2.3.1 (GA) and WSJT-X 2.4.0-rc4 #Q65

 

Hi friends
Thanks Joe and team for your work.
Installed the -rc4 Version of WSJT-X 2.4.0 without problems. It was too late for checking on 6m - nobody there and moon already too high - but I made a fine Q65_60A QSO (terrestrial) over 700 km. Nothing visible in the waterfall, but in the spectrum it was. Will try EME receiving on 2m and 6m today.
I came to having some minor "wishes" to the program concerning mainly the user interface and setup procedure. But this is secondary and I will address the items to the developpers directly.
73 de Christoph DF9CY
---

Christoph Petermann DF9CY

JO54al (Baltic Sea Coast)
7 MHz Dipole @9,5m - 400w

50MHz 6 ele OP-DES Yagi - 270w

144MHz 9 ele DK7ZB - 330w
432MHz 23 ele - 35w

https://www.df9cy.de

16201 - 16220 of 39792