Date   

locked Re: #bug #macos #hamlib #wsjtx #thank #IssueReport

Miloš Soukup
 

Hi Bill,

It is my file.

Thx & 73 de Miloš, OK1FMY


Hi Miloš,

as far as I can see that settings file should have made the FT-857 Hamlib rig model behave as the FT-817 rig model did in previous versions. Can you send the file as you created it as an attachment so I can check the contents please?

73
Bill
G4WJS.

On 06/07/2020 09:07, Miloš Soukup wrote:
Hi Bill,

I stored the json file to:
C:\Users\Miloš\AppData\Local\WSJT-X
and it did not help.

I can use my HS1 with 2.1.2 and my FT-817 with 2.2.2.
I can do with it.

Tnx and 73! de Miloš, OK1FMY


Hi Miloš,

unfortunate coincidences when things are not working are all too common, sorry you had a triple hit!

The mcHf and similar rigs will occasionally work with the Yaesu FT-857 model, it is a timing issue that is resolved in the FT-817 Hamlib model by extra retries, but because of a Hamlib breakage that model is not available to you until the next release. Please try creating a file in the WSJT-X log files directory called hamlib_settings.json with the following contents:
{
    "config": {
    "retry": "5",
    "timeout": "3000"
    }
}
and see if that helps when using the Yaesu FT-857 model with your Ailunce HS1 rig.

73
Bill
G4WJS.

On 03/07/2020 16:08, Miloš Soukup wrote:
Hi Bill,

I am sorry for the delay.
I was fighting three issues simultaneously:
1. Update to WSJT-X 2.2.2.
2. HW defect - the 3.5mm Jack I use for connecting to my external USB sound card became an "insulator".
3. My cellphone updated to Android 10 and the app by IZ2BKT I use for syncing time over bluetooth stopped working.
All the three things happened nearly at the same day.
I was not able to transmit anything. I blamed 2.2.2 but it was caused by the connector.

I can summarize my results related to WSJT-X:
1. My FT-817 works with 2.2.2 as FT-857.
2. I have my second rig: Ailunce HS1 - another Chinese cousin of mcHf by M0NKA. 
HS1 works as FT-817 with 2.1.2 but refuses to work with 2.2.2 as FT-857.

73! and tnx de Miloš, OK1FMY


Hi Miloš,

are you still having issues with your rig using the FT-857 model on v2.2.2 of WSJT-X?

73
Bill
G4WJS.

On 26/06/2020 04:01, Miloš Soukup wrote:
Hello Bill,

Thank you for your info.
Pls, which is the last version not affected by it? 2.2.0?

thx & 73 de Miloš, OK1FMY


On 25/06/2020 17:11, Miloš Soukup wrote:
>
> Hello Bill,
>
> I have the same problem with FT-817. I returned to 2.1.2 - it works
> for me fine. Should I select FT-857 also?
>
> tnx & 73 de Miloš, OK1FMY
>
Hi Miloš,

Glenn's issue was slightly complicated because he is not using a real
FT-817D but a UbitX rig that uses an FT-817D protocol. In your case the
FT-857 rig option should work OK.

73
Bill
G4WJS.




locked Re: #bug #macos #hamlib #wsjtx #thank #IssueReport

Bill Somerville
 

Hi Miloš,

as far as I can see that settings file should have made the FT-857 Hamlib rig model behave as the FT-817 rig model did in previous versions. Can you send the file as you created it as an attachment so I can check the contents please?

73
Bill
G4WJS.

On 06/07/2020 09:07, Miloš Soukup wrote:
Hi Bill,

I stored the json file to:
C:\Users\Miloš\AppData\Local\WSJT-X
and it did not help.

I can use my HS1 with 2.1.2 and my FT-817 with 2.2.2.
I can do with it.

Tnx and 73! de Miloš, OK1FMY


Hi Miloš,

unfortunate coincidences when things are not working are all too common, sorry you had a triple hit!

The mcHf and similar rigs will occasionally work with the Yaesu FT-857 model, it is a timing issue that is resolved in the FT-817 Hamlib model by extra retries, but because of a Hamlib breakage that model is not available to you until the next release. Please try creating a file in the WSJT-X log files directory called hamlib_settings.json with the following contents:
{
    "config": {
    "retry": "5",
    "timeout": "3000"
    }
}
and see if that helps when using the Yaesu FT-857 model with your Ailunce HS1 rig.

73
Bill
G4WJS.

On 03/07/2020 16:08, Miloš Soukup wrote:
Hi Bill,

I am sorry for the delay.
I was fighting three issues simultaneously:
1. Update to WSJT-X 2.2.2.
2. HW defect - the 3.5mm Jack I use for connecting to my external USB sound card became an "insulator".
3. My cellphone updated to Android 10 and the app by IZ2BKT I use for syncing time over bluetooth stopped working.
All the three things happened nearly at the same day.
I was not able to transmit anything. I blamed 2.2.2 but it was caused by the connector.

I can summarize my results related to WSJT-X:
1. My FT-817 works with 2.2.2 as FT-857.
2. I have my second rig: Ailunce HS1 - another Chinese cousin of mcHf by M0NKA. 
HS1 works as FT-817 with 2.1.2 but refuses to work with 2.2.2 as FT-857.

73! and tnx de Miloš, OK1FMY


Hi Miloš,

are you still having issues with your rig using the FT-857 model on v2.2.2 of WSJT-X?

73
Bill
G4WJS.

On 26/06/2020 04:01, Miloš Soukup wrote:
Hello Bill,

Thank you for your info.
Pls, which is the last version not affected by it? 2.2.0?

thx & 73 de Miloš, OK1FMY


On 25/06/2020 17:11, Miloš Soukup wrote:
>
> Hello Bill,
>
> I have the same problem with FT-817. I returned to 2.1.2 - it works
> for me fine. Should I select FT-857 also?
>
> tnx & 73 de Miloš, OK1FMY
>
Hi Miloš,

Glenn's issue was slightly complicated because he is not using a real
FT-817D but a UbitX rig that uses an FT-817D protocol. In your case the
FT-857 rig option should work OK.

73
Bill
G4WJS.



locked Re: #bug #macos #hamlib #wsjtx #thank #IssueReport

Miloš Soukup
 

Hi Bill,

I stored the json file to:
C:\Users\Miloš\AppData\Local\WSJT-X
and it did not help.

I can use my HS1 with 2.1.2 and my FT-817 with 2.2.2.
I can do with it.

Tnx and 73! de Miloš, OK1FMY


Hi Miloš,

unfortunate coincidences when things are not working are all too common, sorry you had a triple hit!

The mcHf and similar rigs will occasionally work with the Yaesu FT-857 model, it is a timing issue that is resolved in the FT-817 Hamlib model by extra retries, but because of a Hamlib breakage that model is not available to you until the next release. Please try creating a file in the WSJT-X log files directory called hamlib_settings.json with the following contents:
{
    "config": {
    "retry": "5",
    "timeout": "3000"
    }
}
and see if that helps when using the Yaesu FT-857 model with your Ailunce HS1 rig.

73
Bill
G4WJS.

On 03/07/2020 16:08, Miloš Soukup wrote:
Hi Bill,

I am sorry for the delay.
I was fighting three issues simultaneously:
1. Update to WSJT-X 2.2.2.
2. HW defect - the 3.5mm Jack I use for connecting to my external USB sound card became an "insulator".
3. My cellphone updated to Android 10 and the app by IZ2BKT I use for syncing time over bluetooth stopped working.
All the three things happened nearly at the same day.
I was not able to transmit anything. I blamed 2.2.2 but it was caused by the connector.

I can summarize my results related to WSJT-X:
1. My FT-817 works with 2.2.2 as FT-857.
2. I have my second rig: Ailunce HS1 - another Chinese cousin of mcHf by M0NKA. 
HS1 works as FT-817 with 2.1.2 but refuses to work with 2.2.2 as FT-857.

73! and tnx de Miloš, OK1FMY


Hi Miloš,

are you still having issues with your rig using the FT-857 model on v2.2.2 of WSJT-X?

73
Bill
G4WJS.

On 26/06/2020 04:01, Miloš Soukup wrote:
Hello Bill,

Thank you for your info.
Pls, which is the last version not affected by it? 2.2.0?

thx & 73 de Miloš, OK1FMY


On 25/06/2020 17:11, Miloš Soukup wrote:
>
> Hello Bill,
>
> I have the same problem with FT-817. I returned to 2.1.2 - it works
> for me fine. Should I select FT-857 also?
>
> tnx & 73 de Miloš, OK1FMY
>
Hi Miloš,

Glenn's issue was slightly complicated because he is not using a real
FT-817D but a UbitX rig that uses an FT-817D protocol. In your case the
FT-857 rig option should work OK.

73
Bill
G4WJS.





locked Re: Help Please

Bill Somerville
 

On 06/07/2020 10:38, Dave, G8PGO wrote:
Just an update. wsjtx does run but do get these messages when I start it from the command line
ALSA lib pcm_usb_stream.c:508:(_snd_pcm_usb_stream_open) Unknown field hint
ALSA lib pcm_direct.c:2023:(snd1_pcm_direct_parse_open_conf) Unknown field tstamp_type
ALSA lib pcm_usb_stream.c:508:(_snd_pcm_usb_stream_open) Unknown field hint
ALSA lib pcm_usb_stream.c:508:(_snd_pcm_usb_stream_open) Unknown field hint
ALSA lib pcm_direct.c:2023:(snd1_pcm_direct_parse_open_conf) Unknown field tstamp_type
ALSA lib pcm_route.c:869:(find_matching_chmap) Found no matching channel map
ALSA lib pcm_route.c:869:(find_matching_chmap) Found no matching channel map
ALSA lib pcm_route.c:869:(find_matching_chmap) Found no matching channel map
ALSA lib pcm_usb_stream.c:508:(_snd_pcm_usb_stream_open) Unknown field hint
Hi Dave,

if Tx and Rx audio are working  then those warnings can be ignored.

73
Bill
G4WJS.


locked Re: WSJTX shows good waterfall but no decoding

Dave Garber
 

are you listening still for jt65 signals, but perhaps the waterfall is displaying ft8 mode.   what mode is set in the drop down, what frequency are you on, are you in USB or USB-data on the radio


Dave Garber
VE3WEJ / VE3IE


On Mon, Jul 6, 2020 at 4:19 AM Steve marsh (M0NMA) <m0nma@...> wrote:
Dennis

the most likely candidate is tat your clock is off slightly. If it is more than 3 seconds out then nothing will decode as it is listening at the wrong time. 

The fastest way to check the time is on the website time.is which will tell you how far out you are. 

Steve


locked Re: Help Please

Dave, G8PGO
 

Just an update. wsjtx does run but do get these messages when I start it from the command line
ALSA lib pcm_usb_stream.c:508:(_snd_pcm_usb_stream_open) Unknown field hint
ALSA lib pcm_direct.c:2023:(snd1_pcm_direct_parse_open_conf) Unknown field tstamp_type
ALSA lib pcm_usb_stream.c:508:(_snd_pcm_usb_stream_open) Unknown field hint
ALSA lib pcm_usb_stream.c:508:(_snd_pcm_usb_stream_open) Unknown field hint
ALSA lib pcm_direct.c:2023:(snd1_pcm_direct_parse_open_conf) Unknown field tstamp_type
ALSA lib pcm_route.c:869:(find_matching_chmap) Found no matching channel map
ALSA lib pcm_route.c:869:(find_matching_chmap) Found no matching channel map
ALSA lib pcm_route.c:869:(find_matching_chmap) Found no matching channel map
ALSA lib pcm_usb_stream.c:508:(_snd_pcm_usb_stream_open) Unknown field hint


locked Re: Logging process Log4OM v2 - Wsjt-x and JTAlert

Gerrit
 

Hello Malcolm,

 

I wanted to inform you that the integration of Log4OM v2 with Wsjtx and JTAlert went smootly.

Up and running well now thanks to you all.

 

Again thanks (also Charlie K5EY and Laurie VK3AMA).

 

Please all stay safe and hope to catch you on the air.

 

73’s

Gerrit – PA3DJY

 

Van: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] Namens Malcolm Appleby
Verzonden: zaterdag 13 juni 2020 18:57
Aan: main@WSJTX.groups.io
Onderwerp: Re: [WSJTX] Logging process Log4OM v2 - Wsjt-x and JTAlert

 

Gerritt

(At the risk of someone pointing out I've got it wrong...)  Here's the screenshots of my setup which is working for me.  
First WSJT-X:


Then JTAlert, two parts to this, first the logging part:


And then the UDP relay:


And finally LOG4OM:


Hope that works for you too, and sorry for the huge screenshots (can't be bothered to resample them).

73, Malcolm G3ZNU


locked Re: Help Please

Dave, G8PGO
 

Hi visitslovenija

No its on a laptop
Buster is the Linux version codename on the Debian platform
as in:
Debian 10 Buster
               9 Stretch
               8 Jessie
etc
I know many people associate it with the Pi


locked Re: Help Please

Dave, G8PGO
 

Thanks Bill
Must learn to read the instructions properly, then again maybe too late at 73
Almost there just an error when I run 'sudo cmake --build . --target install'
I get this error
CMake Error at cmake_install.cmake:289 (file):
  file INSTALL cannot find "/home/dave/build/wsjtx/RIGCTLCOM_EXE-NOTFOUND".

make: *** [Makefile:140: install] Error 1

Thanks again for your help


locked Re: WSJTX shows good waterfall but no decoding

Steve marsh (M0NMA)
 

Dennis

the most likely candidate is tat your clock is off slightly. If it is more than 3 seconds out then nothing will decode as it is listening at the wrong time. 

The fastest way to check the time is on the website time.is which will tell you how far out you are. 

Steve


locked Re: Programmer Contact

Michael Pittaro
 

There is a developer mailing list - wsjt-devel

You can subscribe to that, and post the details.
mike, kj6vcp



locked Programmer Contact

Mike ZooLoo
 

Is there a preferred contact to send error issues that crop up with WSJT program? I hate to occupy space in the group for something that is more a program fix if there such a contact point. This is not a wish list kind of thing. This is an error that occurred. Thanks, Jim (AA0MZ)


locked WSJTX shows good waterfall but no decoding

DB
 

I am using WSJTX but have no decoding.  Using Windows 10 - 64 bit version.  The audio level is at 30 so that level seems good with only noise.  The waterfall looks good and shows many signals but nothing decodes.  Using Yeasu FT-840.  I read the previous posts about this topic but nothing seems to click.  I would appreciate any suggestions as I am new to JT65 and digital modes after being off the air for a while.  Dennis  K0DB


locked Re: Signalink No Power out

David Lane <k4zzr@...>
 
Edited

I don't know if this will help but I use a SignaLink USB interface between my Icom IC-7600 and computer and use my DXLab Suite's "Commander" which passes radio info to WSJTX. 

In WSJTX Settings under Radio I have "DX Lab Suite Commander" selected.  I also have PTT Method set to VOX.  I'm using the Icom's data mode USB-D1 and have WSJTX Mode set to "Data/Pkt.  Under Settings Audio, I have Input set to Microphone (USB Audio CODEC) and Output set to Speakers (USB Audio CODEC).

73,
David, K4ZZR


locked Involuntary CQing

Jim SIMON
 

I have WSJT-x set to “disable Tx after sending 73”. Nevertheless, often when I finish a contact and the “73” message is sent in Tx5, Tx6 triggers with me transmitting an unwanted CQ. How can I prevent that from happening?

 

Tnx es 73,

 

Jim  W1YY

 


locked Re: Signalink No Power out

Harold Miller
 

If running Windows 10, go to Signalink website and download new W10 manual…  shows how to set up Signalink for W10…   I did it and made lots of improvements for me…

 

Hal, KB1ZQ

 

 

From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of Daniel Curry
Sent: Sunday, July 05, 2020 2:38 PM
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] Signalink No Power out

 

To all thank you for the information. However, none of them was successful. Any other ideas?


locked Re: Pi3 stretch build for WSJT-X 2.2.2 hamlib error

Greg Cook
 

Hi,

Just read Bill's reply on another thread on same issue. Yes specifying FT857 instead of my actual radio (FT897) did the trick. Now only probelm I have with this build is no tx audio. Sound card appears correctly in list, and receives fine....and worked fine in 2.1.2. Oh well....


locked Pi3 stretch build for WSJT-X 2.2.2 hamlib error

Greg Cook
 

Hi 
Built and used WSJT-X v2.1.2 on Pi3 Stretch with no problems. Built v2.2.2 from tarball and now get hamlib error 'Target VFO unaccessible while getting current frequency' and no PTT control either. Previously I used the hamlib compiled into WSJT-X executable, so did not build and link the libs in the wsjtx-2.x.x/src dir. Do I need to do this now and if so is it the hamlib-4.0~git.tar.gz? But why should there be any difference between how 2.1.2 and 2.2.2 behave in this matter?

Thanks,

Greg g4cui


locked Re: WSJT-X/FT8 Turns on IC-9700 and IC-7610

Bill Somerville
 

On 06/07/2020 01:22, Jim Brassell, K4ZMV wrote:
Thanks, Bill.  That answers my question.  It would be nice if that 'feature' was documented somewhere.  Is It?

73, Jim
Hi Jim,

other than in the source code, no. Just Yesterday I contributed a patch to Hamlib to make it a configuration option with a default to not attempt to turn on the rig. That has been accepted so will be in the next WSJT-X release.

73
Bill
G4WJS.


locked Re: WSJT-X/FT8 Turns on IC-9700 and IC-7610

Jim Brassell, K4ZMV
 

Thanks, Bill.  That answers my question.  It would be nice if that 'feature' was documented somewhere.  Is It?

73, Jim