Date   

locked Re: #mac Support for Icom radio Silicon Labs a big issue getting bigger all the time #macOS

Frederick Kent
 

I’m having a terrible time trying to get WSJTx going. The problem so far is with getting the CP210X driver installed correctly in my iMac computer.  The driver installs OK like it supposed to do in extensions and from what I’ve learned from others is that it needs to be listed in a utility terminal “ls /dev” for the WSJTx to recognize it. It is not. I’ve tried to load the  latest version of the driver for Mac from the SLab website and a legacy version that others have recommended to no avail. I’ve had many eMail conversations with SLab and Apple on the phone and Icom emails.. Has anyone ever had a similar problem and offer any advice on a solution to this issue?


locked Re: WSJT Sensitivity V MSHV #why ?

Chris, HB9DFG
 

Hello all

With interest I have read through this thread and I thought to myself: why shouldn't I test this as well with JTMS, since I assumed that all other
programmes concerning the FT8 decoder should actually react in the same way. I once compared an older Version of MSHV but it lost a lot
of decodes compared with WSJT-X so I did not tried anew since then.

Well, I now have tested JTDX 2.2.156 and WSJT-X 2.4.0c19d62 a short time (for about 30-40min) on a quiet 2m-band. The computer is still a
WIN7-machine with 8GB RAM and an onboard Realtek audiocard set to the 16bit 48000kHz DVD system. BKTIMESYNC is in use here als well.

WSJT-Xs decoder was set to "deep" and "AP", JTDXs decoder was set to: threats=auto, decoder cycles=1, decoder sensitivity=use low thesholds

Besides the good decodes on both programs (with big differences in the dB values), I took out 13 wave files where either WSJT-X or JTDX did not
decode something.

Results:

- All in all I have picked one periode where WSJT-X had 3 decodes (include one a1), and FTDX got 2 of them. Both programmes were able to read the
   corresponding other wave files of this periode where JTDX couldn't read the "a priori" decode.
- An other periode got 2 decodes on JTDX and one on WSJT-X
- Also one periode got 1 decode on WSJT-X and no decode on JTDX
- The rest of the periods (10) got 1 decode on JTDX and no decode on WSJT-X
- WSJT-X could read JTDXs only no-decode
- JTDX could read 5 of WSJT-Xs 10 no-decodes

Maybe if time permits I will try to make an other test with my other W10-computer with the "soundcard" of my IC-9700.

Bill Somerville wrote earlier:
"...the only way to analyze the issue you report is for you to provide a .WAV file recorded by WSJT-X along with a list of the messages that you think
should have been decoded. Anything else is simply subjective speculation."


Fine Bill, did you already got such files to investigate and did you found out something interesting? Or would you like to get my wav-files to investigate?
If yes, where can I sent them as zipped files?

Best regards de
Chris, HB9DFG



 


locked Re: Modes and Submodes with Frequencies for 6M #Q65

Michel Bernard VE2BJG
 

I have this. A cut/paste table from various sites.

Far from complete I guess but a start.

73   Michel


locked Re: Version 2.4.0 ate my adi file #IssueReport #logging

Julian Topolski
 

Log recovered with the help of Paul, G4IJE. Thanks to all who responded.


locked Modes and Submodes with Frequencies for 6M #Q65

Bobby Chandler
 

Is there a list of 6M frequencies with modes and submodes listed anywhere?
Sure would like to try some of them. I know about 50.275 for 30A and 50.235
for 120E. Any others. I see some reported on 50.267 but no luck for me.

Bobby/N4AU


locked Re: Can hamlib for Windows be used? #Cat_RigControl

Bill Somerville
 

On 19/06/2021 15:59, Fred Cole wrote:
Bill,

I got my answer in the Facebook group. All I needed to do was select "hamlib NET rigctl" in the "Radio" tab, to utilize rigctld. Log4OM can also talk to rigctld in its CAT control. I had been so focused on picking which rig, I never noticed the option for rigctl in the dropdown list.
Hi Fred,

OK, understood. I was not aware that Log4OM had support for Hamlib. Yes that is a good configuration with those applications.

73
Bill
G4WJS.


locked Re: Can hamlib for Windows be used? #Cat_RigControl

Fred Cole
 

Bill,

I got my answer in the Facebook group. All I needed to do was select "hamlib NET rigctl" in the "Radio" tab, to utilize rigctld. Log4OM can also talk to rigctld in its CAT control. I had been so focused on picking which rig, I never noticed the option for rigctl in the dropdown list.


locked Re: Can hamlib for Windows be used? #Cat_RigControl

Bill Somerville
 

On 19/06/2021 04:51, Fred Cole wrote:
I asked this on the Facebook group, but this question may be better suited here. Can WSJT-X on Windows 10 be configured to use hamlib/rigctld on the same machine, instead of its internal? What I would like to do is be able to have Log4OM running and be able to switch between apps like FLdigi, WSJT-X, and voice and still have Log4OM track the frequency. The same thing, I suppose, can be done with Omnirig but I've tried that and I couldn't get it to work. My guess is that it would require me to compile from source, a task I would have to learn under Windows. I can muddle through compiling on Linux so that won't hurt my brain too much.

Fred - N2NRV
Fred,

I do not understand what you are asking, can you clarify please? Log4OM is not compatabile with Hamlib AFAIK so you can use Hamlib to control your rig, or you can use Log4OM to control you rig. To have both involved would need a different arrangement.

73
Bill
G4WJS.


locked Can hamlib for Windows be used? #Cat_RigControl

Fred Cole
 

I asked this on the Facebook group, but this question may be better suited here. Can WSJT-X on Windows 10 be configured to use hamlib/rigctld on the same machine, instead of its internal? What I would like to do is be able to have Log4OM running and be able to switch between apps like FLdigi, WSJT-X, and voice and still have Log4OM track the frequency. The same thing, I suppose, can be done with Omnirig but I've tried that and I couldn't get it to work. My guess is that it would require me to compile from source, a task I would have to learn under Windows. I can muddle through compiling on Linux so that won't hurt my brain too much.

Fred - N2NRV


locked Re: ALL.TXT Append Error #FT8 #IssueReport

Jeff Young
 

Further investigation. The error window appears as the latest decodes are being posted to the left window. I have removed McAfee LiveSafe from the computer and am only using the windows 10 built in security. I have excluded the entire folder where the logs files exist in the appdata/local/WSJT-X folder. I am only running Version 2.3.1 without JT-Alert and ACLog. Sometimes the error windows are 18 screens deep.


locked Re: WSJT-X 2.4.0 rc-2 Subprocess Error #wsjt-x-crashing EXIT CODE 2 #wsjt-x-crashing

George J Molnar, KF2T
 

You might consider installing the release version of the software, as the rc versions are expired.


Bill Somerville
 

Hi Jeremy,

have you assigned the necessary rig USB audio codec devices to the new aggregate device?

73
Bill
G4WJS.

On 18/06/2021 15:53, Jeremy Stark via groups.io wrote:
I created an aggregate device, and selected it in WSJT-X. I can hear there are signals present on the radio, but the software is not showing anything.


-- 
Jeremy
G7BHB

On 17 Jun 2021, at 08:57, Bill Somerville <g4wjs@...> wrote:

Hi Jeff, and Jeremy,

you can get more certainty of audio device naming and selection on macOS by creating an aggregate audio device, then assign your rig's audio devices to it. You can name the aggregate device as to desire, and select that in WSJT-X. This is most useful when you have multiple rigs with in-built USB audio codecs, but can of course be used with a single radio as well.

73
Bill
G4WJS.



locked #Cat_RigControl #error #Cat_RigControl #IssueReport

mattwood2000@...
 

Hi all,

I'm running into some rig control errors and I'm wondering if anyone
has successfully used rigctld and remote (localhost or network)
operation?

My rig is an FT-897D. WSJT-x works perfectly fine when I directly
connect to the rig over the serial port, but I get errors (ERR_IO, -6)
when running rigctld-wsjtx with the same parameters and set the
program to use HamLib NET 2. I've tried the 4.2 release, the
integration release as well as the master branch of the code, all with
the same results.

Most of the time, wsjt-x comes up and reads the VFO and everything
looks good, but as soon as I try to test the CAT or PTT it errors out.

I realize this may be more of a hamlib issue, but figured I'd start here first.

Thanks, Matt.
N1YQE


Jeremy Stark
 

I created an aggregate device, and selected it in WSJT-X. I can hear there are signals present on the radio, but the software is not showing anything.


-- 
Jeremy
G7BHB

On 17 Jun 2021, at 08:57, Bill Somerville <g4wjs@...> wrote:

Hi Jeff, and Jeremy,

you can get more certainty of audio device naming and selection on macOS by creating an aggregate audio device, then assign your rig's audio devices to it. You can name the aggregate device as to desire, and select that in WSJT-X. This is most useful when you have multiple rigs with in-built USB audio codecs, but can of course be used with a single radio as well.

73
Bill
G4WJS.


locked Re: ALL.TXT Append Error #FT8 #IssueReport

Jeff Young
 

Bill:

I am running wsjt-x, jt-alert and N3FJP AC Log.

Jeff


locked Re: WSJT-X 2.4.0 rc-2 Subprocess Error #wsjt-x-crashing EXIT CODE 2 #wsjt-x-crashing

Bill Somerville
 

On 18/06/2021 02:01, Niece KA1ULN wrote:
i have had  this for  over  7 days now.....   what is  the  solution or  temp fix.. i cannot even use my wsjtx.

I AM  GETTING THE  SAME  ERROR   subprocess failed with exit  code 2.
Niece,

please include the full error message, including details, and the version of WSJT-X you are using?

73
Bill
G4WJS.


locked Re: WSJT-X 2.4.0 rc-2 Subprocess Error #wsjt-x-crashing EXIT CODE 2 #wsjt-x-crashing

Niece KA1ULN <ka1uln1@...>
 

i have had  this  for  over  7 days now.....   what is  the  solution or  temp fix.. i cannot even use my wsjtx.

I AM  GETTING THE  SAME  ERROR   subprocess failed with exit  code 2.


locked Re: [EXTERNAL] Re: [WSJTX] Cannot use /P in callsign when using JT65 and JT9 modes #JT9 #IssueReport #JT65

Hattori, Yoshihisa
 

We might be talking about something different.

 

  1. Decode a sig from /P station. (ex. G4WJS/P)
  2. Double click on the decode to generate the message, or populate the DX call manually then click on generate standard message, which will result TX1 without GL. (i.e. G4WJS/P JO1LVZ. Note: This does not occur in FT8.)
  3. If I send the message as it is, DX will receive G4WJS/P <…> so that he will not know who is calling.

 

The only solution at this moment is manually add my GL to TX1. (i.e. TX1 with GL is mandatory to make the protocol work.)

It was originally reported to wsjt-devel back in Mar, too.

All the issues could be fixed by adding GL correctly in TX1 when standard message is generated. (not exactly sure though.)

 

Hatt/JO1LVZ

 

From: main@WSJTX.groups.io <main@WSJTX.groups.io> On Behalf Of Bill Somerville
Sent: Thursday, June 17, 2021 5:12 PM
To: main@WSJTX.groups.io
Subject: Re: [EXTERNAL] Re: [WSJTX] Cannot use /P in callsign when using JT65 and JT9 modes #JT65 #JT9 #BugReport

 

Hi Hatt-san,

 

are you sure? The Q65 mode uses a 77-bit payload with a different message source encoding scheme that allows messages like:

G4WJS/P JO1LVZ/P R-10

so the problem does not occur for that mode.

 

73
Bill
G4WJS.

 

On 17/06/2021 03:01, Hattori, Yoshihisa wrote:

Bill,

 

This also happens to Q65, so please make sure the issue gets fixed for that mode, too.

 

Thanks.

Hatt/JO1LVZ

 

 

From: main@WSJTX.groups.io <main@WSJTX.groups.io> On Behalf Of Bill Somerville
Sent: Wednesday, June 16, 2021 6:42 PM
To: main@WSJTX.groups.io
Subject: [EXTERNAL] Re: [WSJTX] Cannot use /P in callsign when using JT65 and JT9 modes #JT65 #JT9 #BugReport

 


[CAUTION] This email originated from outside Travelport. Do not click links or open attachments unless you recognize the sender and know the content is safe.



On 16/06/2021 10:23, Jim Brown wrote:

On 6/16/2021 1:10 AM, Panos wrote:


Hi Bill, thanks I am waiting for it 73


I am not. Just like on all other bands and modes, the definition of a QSO is the ack of receipt of two pieces if information from the other party. When I copy RRR or RR73, I log the QSO, because I've already sent R plus a report, and the fact that he's sent me RRR or RR73 indicates he's copied my R-report. If he sends RR73 or R and his report again, it tells me he hasn't copied my R, so I send it again. And again, if he keeps sending. He can log it when he's satisfied. When he stops sending his report, I log it. If he doesn't, we don't have a QSO. It's that simple. And for skeds, like online, it's perfeectly legit for the guy getting RRR or RR73 to say so online, like Slack or ON4KST or Ping Jockey. This is VERY common practice when working grid expeditions.

73, Jim K9YC

Jim,

this issue is about operating with a /P or other type 1 prefix or suffix in JT65 mode (same applies to JT9 and JT4 modes), the defect means it is not possible to send a signal report, RRR or 73 message unless the generated messages are manually edited. The defect is a regression that happened some considerable time ago and it needs to be fixed, which is what I  am doing.

73                                                                           
Bill
G4WJS.

 


locked Re: ALL.TXT Append Error #FT8 #IssueReport

Dave Garber
 

if you open the log folder in wsjt, does the all.txt show in there with the other files.
is the folder you state a typo    folder ..../wjt-x/...
Dave Garber
VE3WEJ / VE3IE


On Thu, Jun 17, 2021 at 4:14 PM Jeff Young <kb3hf@...> wrote:
I keep getting this error whale running FT8. "Cannot open C:/Users/…./WJT-X/ALL.TXT for append: The process cannot access the file because it is being used by another process."

 


I have excluded ALL.TXT from scanning and turned off indexing in properties.

Running Win 10, WSJT-X Version 2.3.1



locked Re: #FT8 Not Possible to sign portable? #FT8 #wsjt-x

Jim Brown
 

On 6/17/2021 10:03 AM, robert scott wrote:
I will operating from a different Call Area and wanted to sign WR3Y/7
Why? I've lived in W6 for 15 years, and the only times I've ever used /6 was on 6M CW when the band was open, so that callers wouldn't turn their beams in the wrong direction. That issue is covered by the normal inclusion of our grid in a CQ.

73, Jim K9YC

8341 - 8360 of 34101