Date   

locked Re: Hamlib error v2.3.0-rc3 on Mac OS #IssueReport #macOS #Cat_RigControl

Bill Somerville
 

On 16/01/2021 16:53, Frank, DH4FR wrote:
So, my ‘outsider’ analysis, is that the symlink is interpreted as network connection, i.e. host:port and this fails.
Hi Frank,

exactly right. Looks like a regression in Hamlib, it certainly should not be treating a filesystem path as a network address. I'll have a look and sort out a patch to send upstream to Hamlib.

73
Bill
G4WJS.


locked Re: No audio on double click to work a new station #IssueReport #FT8 #txaudio

David Stout
 

Thanks. That's been done for years.

Dave


locked Re: Hamlib error v2.3.0-rc3 on Mac OS #IssueReport #macOS #Cat_RigControl

Frank, DH4FR
 

Hi Bill,

Attached the log file. Failed scenario first, then I changed the serial port via drop-down menu and you’ll get an OK scenario.

With the symlink, I can see that the function network_open is called:

[2021-01-16 16:32:32.688564][00:00:03.349221][RIGCTRL:debug] rig_set_conf: rig_pathname='/tmp/IC-7300_03003333'
[2021-01-16 16:32:32.688575][00:00:03.349232][RIGCTRL:debug] rig_token_lookup called
[2021-01-16 16:32:32.688581][00:00:03.349239][RIGCTRL:debug] rig_confparam_lookup called
[2021-01-16 16:32:32.688590][00:00:03.349247][RIGCTRL:debug] rig_set_conf called
[2021-01-16 16:32:32.688596][00:00:03.349254][RIGCTRL:debug] rig_confparam_lookup called
[2021-01-16 16:32:32.688605][00:00:03.349262][RIGCTRL:debug] rig_set_conf: serial_speed='115200'
[2021-01-16 16:32:32.688615][00:00:03.349273][RIGCTRL:debug] rig_token_lookup called
[2021-01-16 16:32:32.688622][00:00:03.349280][RIGCTRL:debug] rig_confparam_lookup called
[2021-01-16 16:32:32.688629][00:00:03.349287][RIGCTRL:debug] rig_set_conf called
[2021-01-16 16:32:32.688636][00:00:03.349294][RIGCTRL:debug] rig_confparam_lookup called
[2021-01-16 16:32:32.688644][00:00:03.349301][RIGCTRL:debug] rig_set_conf: no_xchg='1'
[2021-01-16 16:32:32.688651][00:00:03.349309][RIGCTRL:debug] icom_set_conf called
[2021-01-16 16:32:32.688829][00:00:03.349488][RIGCTRL:trace] starting: Icom: IC-7300
[2021-01-16 16:32:32.688860][00:00:03.349518][RIGCTRL:debug] rig_open called
[2021-01-16 16:32:32.688880][00:00:03.349538][RIGCTRL:trace] rig_open: using network address /tmp/IC-7300_03003333
[2021-01-16 16:32:32.688894][00:00:03.349552][RIGCTRL:debug] port_open called
[2021-01-16 16:32:32.688908][00:00:03.349566][RIGCTRL:debug] network_open called
[2021-01-16 16:32:32.688920][00:00:03.349578][RIGCTRL:debug] network_open version 1.0
[2021-01-16 16:32:32.688937][00:00:03.349595][RIGCTRL:error] network_open: hoststr=/tmp/IC-7300_03003333, portstr=
[2021-01-16 16:32:32.690374][00:00:03.351035][RIGCTRL:error] network_open: cannot get host "/tmp/IC-7300_03003333": Unknown error
[2021-01-16 16:32:32.690408][00:00:03.351067][RIGCTRL:error] error: Invalid configuration


With the SLAB device file, the function serial_open is called.

[2021-01-16 16:32:46.816346][00:00:17.477004][RIGCTRL:debug] rig_set_conf: rig_pathname='/dev/cu.SLAB_USBtoUART29'
[2021-01-16 16:32:46.816357][00:00:17.477015][RIGCTRL:debug] rig_token_lookup called
[2021-01-16 16:32:46.816364][00:00:17.477021][RIGCTRL:debug] rig_confparam_lookup called
[2021-01-16 16:32:46.816372][00:00:17.477030][RIGCTRL:debug] rig_set_conf called
[2021-01-16 16:32:46.816425][00:00:17.477084][RIGCTRL:debug] rig_confparam_lookup called
[2021-01-16 16:32:46.816445][00:00:17.477103][RIGCTRL:debug] rig_set_conf: serial_speed='115200'
[2021-01-16 16:32:46.816465][00:00:17.477123][RIGCTRL:debug] rig_token_lookup called
[2021-01-16 16:32:46.816477][00:00:17.477136][RIGCTRL:debug] rig_confparam_lookup called
[2021-01-16 16:32:46.816490][00:00:17.477148][RIGCTRL:debug] rig_set_conf called
[2021-01-16 16:32:46.816502][00:00:17.477160][RIGCTRL:debug] rig_confparam_lookup called
[2021-01-16 16:32:46.816511][00:00:17.477169][RIGCTRL:debug] rig_set_conf: no_xchg='1'
[2021-01-16 16:32:46.816519][00:00:17.477176][RIGCTRL:debug] icom_set_conf called
[2021-01-16 16:32:46.816591][00:00:17.477250][RIGCTRL:trace] starting: Icom: IC-7300
[2021-01-16 16:32:46.816614][00:00:17.477272][RIGCTRL:debug] rig_open called
[2021-01-16 16:32:46.816629][00:00:17.477287][RIGCTRL:debug] port_open called
[2021-01-16 16:32:46.816652][00:00:17.477311][RIGCTRL:debug] serial_open called
[2021-01-16 16:32:46.820497][00:00:17.481158][RIGCTRL:debug] serial_setup called
[2021-01-16 16:32:46.820527][00:00:17.481185][RIGCTRL:trace] serial_setup: tcgetattr
[2021-01-16 16:32:46.820577][00:00:17.481235][RIGCTRL:trace] serial_setup: cfmakeraw
[2021-01-16 16:32:46.820605][00:00:17.481263][RIGCTRL:trace] serial_setup: cfsetispeed=115200,0x1c200
[2021-01-16 16:32:46.820629][00:00:17.481287][RIGCTRL:trace] serial_setup: cfsetospeed=115200,0x1c200
[2021-01-16 16:32:46.820649][00:00:17.481307][RIGCTRL:trace] serial_setup: data_bits=8
[2021-01-16 16:32:46.820663][00:00:17.481321][RIGCTRL:trace] serial_setup: parity=0
[2021-01-16 16:32:46.821262][00:00:17.481920][RIGCTRL:trace] serial_setup: tcsetattr TCSANOW
[2021-01-16 16:32:46.822825][00:00:17.483486][RIGCTRL:debug] serial_flush called

So, my ‘outsider’ analysis, is that the symlink is interpreted as network connection, i.e. host:port and this fails.


NewMini:~ Frank$ ls -la /tmp/IC-7300*
lrwxr-xr-x  1 Frank  wheel  25 Jan 16 15:35 /tmp/IC-7300_03003333 -> /dev/tty.SLAB_USBtoUART29
NewMini:~ Frank$ 


Best 73 Frank







locked Re: No audio on double click to work a new station #IssueReport #FT8 #txaudio

neil_zampella
 

Could be that the USB sound device was put to sleep by the OS?    I'd do the usual checks, go into the Device Manager and check if any of the USB hubs and devices properties have the Power setting setup to allow the OS to turn off the device.    If so, disable that function.

Neil, KN3ILZ

On 1/16/2021 8:46 AM, David AD4TJ via groups.io wrote:
Happens to me frequently. The easiest thing to do is immediately hit Halt TX, then quickly hit Enable TX. For some reason, that revives the audio. Never have found a good reason that causes it.
David AD4TJ



locked Re: Hamlib error v2.3.0-rc3 on Mac OS #IssueReport #macOS #Cat_RigControl

Bill Somerville
 

On 15/01/2021 15:21, Frank, DH4FR wrote:
Hi Bill,

Thanks for the in-depth reply and confirming that my ‘workaround’ with symlinks is valid.
However, this would imply that the Hamlib error I’m getting on v2.3.0-rc3 is a bug? After all, the same setup on v2.2.2 works fine.

(I did some testing with linking to the ‘cu’ device instead of ‘tty’ and I get the same error)

Best 73 Frank
Hi Frank,

sorry for the delay, I'm rather busy at the moment.

So I can see what is going on please put the attached file into ~/Library/Preferences/ . That will cause WSJT-X to write a log file with detailed rig control trace information to the Desktop called WSJT-X_RigControl.log . Run a minimal test starting WSJT-X that fails to connect to your CAT serial device using the symlink, then quit WSJT-X. Send me the WSJT-X_RigControl.log file for analysis please?

73
Bill
G4WJS.


locked Re: No audio on double click to work a new station #IssueReport #FT8 #txaudio

David Stout
 

I had my eye on the Hamlib 7600 driver. May I ask what XCVR you're using?

Dave


locked Re: #WSJTX_config #WSJTX_config

Bill Somerville
 

On 16/01/2021 14:30, Michael Salmi wrote:
Following. I have the same issue.
Mike, N9MDS


-- Mike Salmi, N9MDS
Hi Mike,

given that unhelpful topic subject, please confirm that you are trying to run WSJT-X v2.3.0 RC3 on macOS Big Sur using Intel hardware.

73
Bill
G4WJS.


locked Re: No audio on double click to work a new station #IssueReport #FT8 #txaudio

David AD4TJ
 

Happens to me frequently. The easiest thing to do is immediately hit Halt TX, then quickly hit Enable TX. For some reason, that revives the audio. Never have found a good reason that causes it.
David AD4TJ


locked No audio on double click to work a new station #IssueReport #FT8 #txaudio

David Stout
 

Forgive me if this has been asked before but I've never seen anything on the subject and none of my friends have this issue. I'm using a 7600, a Timewave Navigator and WSJT-X v2.22. OS is Win7 SP1 x64. Only once in awhile, when I double click on a new call in either the Band Activity or Rx Freq window the program/rig goes into XMIT but no audio. If I Halt Tx and either double click again or Enable Tx, audio resumes. My settings for Radio:



I've installed the latest Icom and Navigator USB drivers. Has anyone else encountered this?

Thanks
Dave


locked Re: #WSJTX_config #WSJTX_config

Michael Salmi
 

Following. I have the same issue.
Mike, N9MDS


--
Mike Salmi, N9MDS


locked Re: my computer updated to Big Sur and wsjtx won't work anymore #macOS

Bill Somerville
 

On 16/01/2021 13:30, Richard Dickerson wrote:
I updated to macOS Big Sur and it kicked out the Sysct.cor file.  How do I reinstall it. I recently had an eye stroke so my vision isn't great right now.

WF2F
Richard
Hi Richard,

the post install instructions for WSJT-X are in the ReadMe.txt file on the installer DMG.

73
Bill
G4WJS.


locked Re: suddenly getting low power output

Bill Somerville
 

On 16/01/2021 12:49, ki5cey@... wrote:
I was having this problem after I updated on the 3rd, until last night when I figured it out. I have an FT891 and the signalink, but it can be any soundcard. The problem I had was at split. I had WSJT set for Data/Pkt and rig set to split. However when when it would transmit it wouldn't move the ALC. It wasn't until my son dropped a paint tray in the shack while I was transmitting that I figured it out. The ALC jumped, the mic was hot in transmit. I looked at the radio closer and saw that on VFOB the mode was USB and not D-U. WSJT isn't changing the mode for VFOB when in split. This might be your problem. There are two ways to address it, you can hold the F key for the big of setting and go to 11-05 and set to REAR(mic won't work in voice mode), EX11051; in CAT. Or just set the mode on VFOB to D-U. Hold BAND for a few and then select DATA. Which is MD0C; in CAT? I think. Hope this helps.
Hi OM,

do you have "Settings->Radio->Mode->Data/Pkt" set in WSJT-X?

73
Bill
G4WJS.


locked my computer updated to Big Sur and wsjtx won't work anymore #macOS

Richard Dickerson
 

I updated to macOS Big Sur and it kicked out the Sysct.cor file.  How do I reinstall it. I recently had an eye stroke so my vision isn't great right now.

WF2F
Richard


locked #WSJTX_config #WSJTX_config

James Quick
 

I can’t get WSJT-X 2.3.0-rc3 to run on my Mac Big Sur it keeps crashing so I am running v2.3.0-rc2. the rc2 is set to stop working on the 19th. Is there any way to reconfigure rc2 past the 19th? Thanks for any help or advice.

73

Jim Quick / N4ULE
jimn4ule@...


locked Re: suddenly getting low power output

ki5cey@...
 

I was having this problem after I updated on the 3rd, until last night when I figured it out. I have an FT891 and the signalink, but it can be any soundcard. The problem I had was at split. I had WSJT set for Data/Pkt and rig set to split. However when when it would transmit it wouldn't move the ALC. It wasn't until my son dropped a paint tray in the shack while I was transmitting that I figured it out. The ALC jumped, the mic was hot in transmit. I looked at the radio closer and saw that on VFOB the mode was USB and not D-U. WSJT isn't changing the mode for VFOB when in split. This might be your problem. There are two ways to address it, you can hold the F key for the big of setting and go to 11-05 and set to REAR(mic won't work in voice mode), EX11051; in CAT. Or just set the mode on VFOB to D-U. Hold BAND for a few and then select DATA. Which is MD0C; in CAT? I think. Hope this helps.


locked Re: Unable to Open WSJT-X #wsjt-x-crashing

kh6dc@...
 
Edited

Same thing - I tried it as a stand alone without the remote software running and WSJT closes.  The radio is upstairs at my QTH but I prefer to sit in the living room which is cooler.  Thanks


locked Re: WSJT-X waterfall freezes & stops decoding @ raspberry pi

Georgina Joyce
 

Hello,

I am struggling with this too. I have TS-590SG. I know my cable connection provides this output:

sources:
alsa_output.usb-Burr-Brown_from_TI_USB_Audio_CODEC-00.analog-stereo.monitor/#3: Monitor of PCM2903B Audio CODEC Analog Stereo
alsa_input.usb-Burr-Brown_from_TI_USB_Audio_CODEC-00.analog-stereo/#4: PCM2903B Audio CODEC Analog Stereo

This was from the command:

pacmd list-card.

I can amend the playback level but not the capture level. Like you it is hard to identify which setting to select on the audio tab of WSJTX. From memory, those drivers you tried were the audio stream for the HDMI ports.

I am sure you are right with using the burr brown identifier but as it has several listings it is difficult to know which are those required for RX & TX levels.

I shall watch this thread with interest because it is looking like these radios with a USB lead are probably using a very similar configuration.

Good luck

Gena
On 15 Jan 2021, at 17:13, dpsm64@... wrote:

Hi --

I too was suffering from the same problem until last night, when I stumbled upon a partial answer. I'm using a Raspberry Pi 4 which I loaded with the latest HamPi image, and was consistently finding that WSJT-X would freeze up after transmitting on either WSPR or FT8 (the only modes I tried). flrig stayed active, the transceiver (IC-7200) would still behave normally, and WSJT-X was still responsive (i.e., could still scroll the band activity window and click buttons, and still controlled the rig through flrig), but the waterfall froze and there was no further decoding of incoming signals.

My "fix", if you can call it that, was to go into the audio tab of WSJT-X settings and change the input device. I had it set to "default", which appeared to work -- before transmitting I was getting plenty of decodes, so the audio was definitely getting through. I changed the input to also_input.usb-Burr-Brown_from_TI_USB_Audio_CODEC-00.analog.mono. Doing that kept the waterfall working after transmitting, at least in my environment, and the decodes keep rolling in.

Now, the reason I say this is a partial fix is because I'm not sure I have the audio output settings right. I had that set to "default" too originally, so I suspect it needs to be set to something else. There are currently 31 options listed for audio output devices, and I'm not sure which one to pick. I'm pretty sure it's neither of the two "alsa_output.platform-bcm2835_audio.*" options -- tried both of those on WSPR last night and nobody seemed to hear me. The rig is keying up, but I suspect that I'm not modulating at all. So there's still work to do, but at least I have consistent decodes.

Hope this helps someone.

Georgina


Call: M0EBP
DMR ID: 2346259
Allstar: 52178
Locater: IO83PS


locked Re: missing wsjt.log.adi file #logging

Борис Романов
 

Hi Scott!
If these QSOs are not in the external journal, and you did not upload them to eQSL or LotW, you can use the Adif Master program
 
 
73 Boris UX8IW
Пятница, 15 января 2021, 19:10 +03:00 от skj 73 <skjasper73@...>:
 
I accidentally overwrote my wsjt.log.adi file.

the wsjt.log file is still intact.

how do i recreate the .adi file?  it looks like its the file wsjt uses
to identify new stations as everything i hear now pops up as new!


--
Scott- NE9U

Sent from my Cray-1


--
This email has been checked for viruses by AVG.
https://www.avg.com

 



 
 
 
--
Борис Романов
 


locked Re: WSJT-X waterfall freezes & stops decoding @ raspberry pi

dpsm64@...
 

Update on audio output settings -- on a hunch, I changed to "plughw:CARD=CODEC,DEV=0" and now I'm getting out! Just made a bunch of WSPR contacts on 20m, which unfortunately was at 20 watts by mistake, sorry about that everyone. But at least now I know I'm modulating. And, the waterfall is still going and I'm still decoding.


locked Re: WSJT-X waterfall freezes & stops decoding @ raspberry pi

dpsm64@...
 

Hi --

I too was suffering from the same problem until last night, when I stumbled upon a partial answer. I'm using a Raspberry Pi 4 which I loaded with the latest HamPi image, and was consistently finding that WSJT-X would freeze up after transmitting on either WSPR or FT8 (the only modes I tried). flrig stayed active, the transceiver (IC-7200) would still behave normally, and WSJT-X was still responsive (i.e., could still scroll the band activity window and click buttons, and still controlled the rig through flrig), but the waterfall froze and there was no further decoding of incoming signals.

My "fix", if you can call it that, was to go into the audio tab of WSJT-X settings and change the input device. I had it set to "default", which appeared to work -- before transmitting I was getting plenty of decodes, so the audio was definitely getting through. I changed the input to also_input.usb-Burr-Brown_from_TI_USB_Audio_CODEC-00.analog.mono. Doing that kept the waterfall working after transmitting, at least in my environment, and the decodes keep rolling in.

Now, the reason I say this is a partial fix is because I'm not sure I have the audio output settings right. I had that set to "default" too originally, so I suspect it needs to be set to something else. There are currently 31 options listed for audio output devices, and I'm not sure which one to pick. I'm pretty sure it's neither of the two "alsa_output.platform-bcm2835_audio.*" options -- tried both of those on WSPR last night and nobody seemed to hear me. The rig is keying up, but I suspect that I'm not modulating at all. So there's still work to do, but at least I have consistent decodes.

Hope this helps someone.

16501 - 16520 of 37037