1. main@WSJTX.groups.io
  2. Messages
   Date   
locked Re: Class C Amplifier Application #transmit

alanbh@...
 

The answer would be NO. FT8 and FT4 is a tone modulate SSB type signal. You cannot put an SSB or modulated signal through class C amplifier without distorting the signal. The maximum class you can put a modulated of SSB type signal through without or absolute minimal distortion is a class B Amplifier.

73, alan WA3EKL

----- Original Message -----
From: "Bob McGraw - K4TAX" <rmcgraw@...>
To: WSJTX@groups.io
Sent: Tuesday, July 27, 2021 7:05:24 PM
Subject: [WSJTX] Class C Amplifier Application #transmit


I've not seen any clear or definitive answer to the question "can one
suddessfully run FT-8/4 or other WSJT-X modes via a Class C solid state
VHF amplifier?"  Asking because I have a VHF amplifier which is not linear.

73

Bob, K4TAX
locked Class C Amplifier Application #transmit

Bob McGraw - K4TAX <rmcgraw@...>
 
Edited

I've not seen any clear or definitive answer to the question "can one successfully run FT-8/4 or other WSJT-X modes via a Class C solid-state VHF amplifier?"  Asking because I have a VHF amplifier which is not linear.

73

Bob, K4TAX
locked Re: Excessive audio from K3S connected to MAC - no level controls #macOS

Bill Somerville
 

On 27/07/2021 15:53, Gareth, M5KVK wrote:
This is not strictly WSJT-X related, but I'm not sure where else to ask without having to explain having a radio connected to a Mac :-)

I'm running 2.4.0 on my iMac (Big Sur) and my K3S is connected using USB. The K3S appears as two USB Audio CODECs in the Audio MIDI Setup tool - one each for input and output.
I can receive in WSJT-X if I select USB Audio CODEC 2 (the i/p device) but the average level is way too high ( 60db with only noise). Thus it overloads with strong signals.

Unfortunately, the input device has the level controls greyed out in the MIDI control panel, so I can't drop the level there; and of course WSJT-X has no i/p volume control.

Has anybody else experienced this problem? If so, how did you resolve it.
If you didn't, how is your K3S, Mac, WSJT-X audio chain configured?

73, Gareth - M5KVK
Hi Gareth,

lower the MENU: LIN OUT level in the K3(S) settings.

73
Bill
G4WJS.
locked Re: Ver 2.4.0 Setup Help #TechnicalHelpQuestion #Cat_RigControl

Dave Garber
 

You do not mention what you gave for cat control , a signalink is not a cat device


On Sun., Jul. 25, 2021, 12:49 a.m. Kenneth Blackwell, <klblackw38@...> wrote:

I am using the following equipment/software for operating on WSJT-X. I NEED help with CAT setup


FT-891 Radio

Signalink USB sound card
Raspbery Pi computer
Raspberry Buster OS
WSJT-X 2.4


I want to operate with CAT as I have in the past with earlier versions of WSJT-X.


Please provide input about the following setup items.


I Need: "CAT Control Serial Port " under Radio page

I previously used /dev/ttyUSB0 which is no longer available. Current choices are:

USB or /dev/tty/AMA0


I also need:

Sound Card Input and Output, UNDER Audio page

Previously I used: frontCARD=CODECDEV=0 for both input and output

This doesn't work and I can't find anything that does.

 
locked Re: Time Synch. #Timesync

Michael Black
 

If you start it with -g it should sync immediately.


Open services and find Network Time Protocol -- stop it and add the -g switch -- then start it back up again and test.

Inline image



Mike W9MDB


On Tuesday, July 27, 2021, 12:47:16 PM CDT, Ron Schunk <ron051798@...> wrote:


I've been using Meinberg since February when I first got back on the air and also time.is ... when I bring my laptop back from 'sleep' mode I usually find that time.is never up to date...I always end up rebooting the laptop and then my time is exact...
Ron
WA8KQF

Virus-free. www.avast.com

On Mon, Jul 26, 2021 at 2:47 PM Kermit Lehman via groups.io <ktfrog007=aol.com@groups.io> wrote:
I have two computers I use for FT modes. As an experiment the one runs Dim4 and the other Meinberg. Both have worked well for me.

If you use Dim4, you need to find the closest open-access time server.  I use one from MIT, which is relatively nearby.  If you don't set Dim4 up properly in this regard, it won't work well.

73,
Ken, AB1J


-----Original Message-----
From: K0GU <k0gu@...>
To: main@WSJTX.groups.io
Sent: Mon, Jul 26, 2021 5:26 pm
Subject: Re: [WSJTX] Time Synch. #Timesync

Interesting, I have zero problems with Meinberg and until I switched had problems with DIM4 sometimes not finding the time server. Probably some setting I had wrong or I chose an intermittent time server. FWIW

gmendenh1947 if you have a callsign you might wish to create a signature line, or add your call to the post, so we have an idea who you are, or not. I'm going to guess you are one of the many Mendenhalls in the FCC data base that has a name starting with g.

--
73,  Jay  K0GU  DN70mq









locked Re: Time Synch. #Timesync

Pietro Molina
 

I suggest BktTimeSync  
locked Re: Time Synch. #Timesync

Ron Schunk
 

I've been using Meinberg since February when I first got back on the air and also time.is ... when I bring my laptop back from 'sleep' mode I usually find that time.is never up to date...I always end up rebooting the laptop and then my time is exact...
Ron
WA8KQF

Virus-free. www.avast.com


On Mon, Jul 26, 2021 at 2:47 PM Kermit Lehman via groups.io <ktfrog007=aol.com@groups.io> wrote:
I have two computers I use for FT modes. As an experiment the one runs Dim4 and the other Meinberg. Both have worked well for me.

If you use Dim4, you need to find the closest open-access time server.  I use one from MIT, which is relatively nearby.  If you don't set Dim4 up properly in this regard, it won't work well.

73,
Ken, AB1J


-----Original Message-----
From: K0GU <k0gu@...>
To: main@WSJTX.groups.io
Sent: Mon, Jul 26, 2021 5:26 pm
Subject: Re: [WSJTX] Time Synch. #Timesync

Interesting, I have zero problems with Meinberg and until I switched had problems with DIM4 sometimes not finding the time server. Probably some setting I had wrong or I chose an intermittent time server. FWIW

gmendenh1947 if you have a callsign you might wish to create a signature line, or add your call to the post, so we have an idea who you are, or not. I'm going to guess you are one of the many Mendenhalls in the FCC data base that has a name starting with g.

--
73,  Jay  K0GU  DN70mq






locked Excessive audio from K3S connected to MAC - no level controls #macOS

Gareth, M5KVK
 

This is not strictly WSJT-X related, but I'm not sure where else to ask without having to explain having a radio connected to a Mac :-)

I'm running 2.4.0 on my iMac (Big Sur) and my K3S is connected using USB. The K3S appears as two USB Audio CODECs in the Audio MIDI Setup tool - one each for input and output.
I can receive in WSJT-X if I select USB Audio CODEC 2 (the i/p device) but the average level is way too high ( 60db with only noise). Thus it overloads with strong signals.

Unfortunately, the input device has the level controls greyed out in the MIDI control panel, so I can't drop the level there; and of course WSJT-X has no i/p volume control.

Has anybody else experienced this problem? If so, how did you resolve it.
If you didn't, how is your K3S, Mac, WSJT-X audio chain configured?

73, Gareth - M5KVK
locked Re: Mac M1 Memory Error

Bill Somerville
 

On 27/07/2021 05:06, Bob Murphy N1KWH via groups.io wrote:
Hi Gentlemen,

If you make a shell command file with the necessary command line entries and include it with startup items, then every time you reboot it will automatically set the parameters for WSJT-X on every reboot.
Regards
Bob
N1KWH
Bob,

the ReadMe.txt file available at the root of the WSJT-X installer DMG has instructions for preparing macOS systems for use with WSJT-X. The latest version (WSJT-X v2.5.0 RC3) has instructions that work with all macOS systems.

73
Bill
G4WJS.
locked Re: Mac M1 Memory Error

Bob Murphy N1KWH
 

Hi Gentlemen,

If you make a shell command file with the necessary command line entries and include it with startup items, then every time you reboot it will automatically set the parameters for WSJT-X on every reboot. 
Regards
Bob
N1KWH
locked Re: PTT Cat Error when not using PTT #Cat_RigControl

danzee <k2ywe@...>
 

Thank You - Success at last!
Adjusting the VOX delay down to minimum fixed the problem. it was up at some ungodly number.
I will try PTT later.
VRY 73
Dan



Sent from my Verizon, Samsung Galaxy smartphone


-------- Original message --------
From: Bill Somerville <g4wjs@...>
Date: 7/26/21 5:36 PM (GMT-05:00)
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] PTT Cat Error when not using PTT #Cat_RigControl

On 26/07/2021 22:09, danzee via groups.io wrote:
> Fresh WSJT-X installation on fresh Windows7 SP1 machine.
> WSJT-X works and I'm able to make FT8 contacts (WSJT-X even controls
> the split transmit freq), but I get a Rig Control error message after
> each transmit cycle and have to check "retry" or "OK" & reconfigure. I
> have tried all combinations of handshake settings without success.
> I have had WSJT-X running on other Win7 machines and not experienced
> this error. I looked at the configuration file from my last WSJT-X
> installation and it was 8-2-N with no handshake for my FTdx-5K. Those
> settings still give me the error. I'm using VOX, not PTT and have
> WSJT-X set that way, i.e. VOX checked off.
> Rig Control error details:
>
> Hamlib error: Target VFO unaccessible
>
> newcat.c(1663):newcat_get_ptt return(0)
>
> newcat_set_freq: ptt still on...retry#0
>
> rig.c(1769):rig_set_freq return(12) while setting frequency
>
OM,

which version of WSJT-X are you using? If it is not WSJT-X v2.5.0 RC3
then can you try that please?

Your rig may require that "Settings->General->Allow Tx frequency changes
while transmitting" is not checked. When using VOX with rigs that don't
accept CAT QSY commands while transmitting you will have to reduce the
VOX hang delay to minimum. It is by far preferable to use a hard wired
PTT, particularly on rigs like yours where you can use either a CAT
command or RTS on the enhanced virtual serial port at zero extra cost.

73
Bill
G4WJS.
locked Re: PTT Cat Error when not using PTT #Cat_RigControl

danzee <k2ywe@...>
 

Allow Freq Changes has been checked all along as has Hold TX Freq



Sent from my Verizon, Samsung Galaxy smartphone


-------- Original message --------
From: Bill Somerville <g4wjs@...>
Date: 7/26/21 5:36 PM (GMT-05:00)
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] PTT Cat Error when not using PTT #Cat_RigControl

On 26/07/2021 22:09, danzee via groups.io wrote:
> Fresh WSJT-X installation on fresh Windows7 SP1 machine.
> WSJT-X works and I'm able to make FT8 contacts (WSJT-X even controls
> the split transmit freq), but I get a Rig Control error message after
> each transmit cycle and have to check "retry" or "OK" & reconfigure. I
> have tried all combinations of handshake settings without success.
> I have had WSJT-X running on other Win7 machines and not experienced
> this error. I looked at the configuration file from my last WSJT-X
> installation and it was 8-2-N with no handshake for my FTdx-5K. Those
> settings still give me the error. I'm using VOX, not PTT and have
> WSJT-X set that way, i.e. VOX checked off.
> Rig Control error details:
>
> Hamlib error: Target VFO unaccessible
>
> newcat.c(1663):newcat_get_ptt return(0)
>
> newcat_set_freq: ptt still on...retry#0
>
> rig.c(1769):rig_set_freq return(12) while setting frequency
>
OM,

which version of WSJT-X are you using? If it is not WSJT-X v2.5.0 RC3
then can you try that please?

Your rig may require that "Settings->General->Allow Tx frequency changes
while transmitting" is not checked. When using VOX with rigs that don't
accept CAT QSY commands while transmitting you will have to reduce the
VOX hang delay to minimum. It is by far preferable to use a hard wired
PTT, particularly on rigs like yours where you can use either a CAT
command or RTS on the enhanced virtual serial port at zero extra cost.

73
Bill
G4WJS.
locked Re: PTT Cat Error when not using PTT #Cat_RigControl

danzee <k2ywe@...>
 

No joy. Same problem with 2.5 RC3



Sent from my Verizon, Samsung Galaxy smartphone


-------- Original message --------
From: Bill Somerville <g4wjs@...>
Date: 7/26/21 5:36 PM (GMT-05:00)
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] PTT Cat Error when not using PTT #Cat_RigControl

On 26/07/2021 22:09, danzee via groups.io wrote:
> Fresh WSJT-X installation on fresh Windows7 SP1 machine.
> WSJT-X works and I'm able to make FT8 contacts (WSJT-X even controls
> the split transmit freq), but I get a Rig Control error message after
> each transmit cycle and have to check "retry" or "OK" & reconfigure. I
> have tried all combinations of handshake settings without success.
> I have had WSJT-X running on other Win7 machines and not experienced
> this error. I looked at the configuration file from my last WSJT-X
> installation and it was 8-2-N with no handshake for my FTdx-5K. Those
> settings still give me the error. I'm using VOX, not PTT and have
> WSJT-X set that way, i.e. VOX checked off.
> Rig Control error details:
>
> Hamlib error: Target VFO unaccessible
>
> newcat.c(1663):newcat_get_ptt return(0)
>
> newcat_set_freq: ptt still on...retry#0
>
> rig.c(1769):rig_set_freq return(12) while setting frequency
>
OM,

which version of WSJT-X are you using? If it is not WSJT-X v2.5.0 RC3
then can you try that please?

Your rig may require that "Settings->General->Allow Tx frequency changes
while transmitting" is not checked. When using VOX with rigs that don't
accept CAT QSY commands while transmitting you will have to reduce the
VOX hang delay to minimum. It is by far preferable to use a hard wired
PTT, particularly on rigs like yours where you can use either a CAT
command or RTS on the enhanced virtual serial port at zero extra cost.

73
Bill
G4WJS.
locked Re: PTT Cat Error when not using PTT #Cat_RigControl

danzee <k2ywe@...>
 

Humm. I see only 2.5 RC3 and I'm willing to try it but still,  l had no such problem a month ago on my old installation 


Sent from my Verizon, Samsung Galaxy smartphone


-------- Original message --------
From: Bill Somerville <g4wjs@...>
Date: 7/26/21 5:36 PM (GMT-05:00)
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] PTT Cat Error when not using PTT #Cat_RigControl

On 26/07/2021 22:09, danzee via groups.io wrote:
> Fresh WSJT-X installation on fresh Windows7 SP1 machine.
> WSJT-X works and I'm able to make FT8 contacts (WSJT-X even controls
> the split transmit freq), but I get a Rig Control error message after
> each transmit cycle and have to check "retry" or "OK" & reconfigure. I
> have tried all combinations of handshake settings without success.
> I have had WSJT-X running on other Win7 machines and not experienced
> this error. I looked at the configuration file from my last WSJT-X
> installation and it was 8-2-N with no handshake for my FTdx-5K. Those
> settings still give me the error. I'm using VOX, not PTT and have
> WSJT-X set that way, i.e. VOX checked off.
> Rig Control error details:
>
> Hamlib error: Target VFO unaccessible
>
> newcat.c(1663):newcat_get_ptt return(0)
>
> newcat_set_freq: ptt still on...retry#0
>
> rig.c(1769):rig_set_freq return(12) while setting frequency
>
OM,

which version of WSJT-X are you using? If it is not WSJT-X v2.5.0 RC3
then can you try that please?

Your rig may require that "Settings->General->Allow Tx frequency changes
while transmitting" is not checked. When using VOX with rigs that don't
accept CAT QSY commands while transmitting you will have to reduce the
VOX hang delay to minimum. It is by far preferable to use a hard wired
PTT, particularly on rigs like yours where you can use either a CAT
command or RTS on the enhanced virtual serial port at zero extra cost.

73
Bill
G4WJS.
locked Re: PTT Cat Error when not using PTT #Cat_RigControl

danzee <k2ywe@...>
 

Dang! It's 2.4. I'm embarrassed that I didn't check. I will update and report back. Thanks!



Sent from my Verizon, Samsung Galaxy smartphone


-------- Original message --------
From: Bill Somerville <g4wjs@...>
Date: 7/26/21 5:36 PM (GMT-05:00)
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] PTT Cat Error when not using PTT #Cat_RigControl

On 26/07/2021 22:09, danzee via groups.io wrote:
> Fresh WSJT-X installation on fresh Windows7 SP1 machine.
> WSJT-X works and I'm able to make FT8 contacts (WSJT-X even controls
> the split transmit freq), but I get a Rig Control error message after
> each transmit cycle and have to check "retry" or "OK" & reconfigure. I
> have tried all combinations of handshake settings without success.
> I have had WSJT-X running on other Win7 machines and not experienced
> this error. I looked at the configuration file from my last WSJT-X
> installation and it was 8-2-N with no handshake for my FTdx-5K. Those
> settings still give me the error. I'm using VOX, not PTT and have
> WSJT-X set that way, i.e. VOX checked off.
> Rig Control error details:
>
> Hamlib error: Target VFO unaccessible
>
> newcat.c(1663):newcat_get_ptt return(0)
>
> newcat_set_freq: ptt still on...retry#0
>
> rig.c(1769):rig_set_freq return(12) while setting frequency
>
OM,

which version of WSJT-X are you using? If it is not WSJT-X v2.5.0 RC3
then can you try that please?

Your rig may require that "Settings->General->Allow Tx frequency changes
while transmitting" is not checked. When using VOX with rigs that don't
accept CAT QSY commands while transmitting you will have to reduce the
VOX hang delay to minimum. It is by far preferable to use a hard wired
PTT, particularly on rigs like yours where you can use either a CAT
command or RTS on the enhanced virtual serial port at zero extra cost.

73
Bill
G4WJS.
locked Re: PTT Cat Error when not using PTT #Cat_RigControl

Bill Somerville
 

On 26/07/2021 22:09, danzee via groups.io wrote:
Fresh WSJT-X installation on fresh Windows7 SP1 machine.
WSJT-X works and I'm able to make FT8 contacts (WSJT-X even controls the split transmit freq), but I get a Rig Control error message after each transmit cycle and have to check "retry" or "OK" & reconfigure. I have tried all combinations of handshake settings without success.
I have had WSJT-X running on other Win7 machines and not experienced this error. I looked at the configuration file from my last WSJT-X installation and it was 8-2-N with no handshake for my FTdx-5K. Those settings still give me the error. I'm using VOX, not PTT and have WSJT-X set that way, i.e. VOX checked off.
Rig Control error details:

Hamlib error: Target VFO unaccessible

newcat.c(1663):newcat_get_ptt return(0)

newcat_set_freq: ptt still on...retry#0

rig.c(1769):rig_set_freq return(12) while setting frequency
OM,

which version of WSJT-X are you using? If it is not WSJT-X v2.5.0 RC3 then can you try that please?

Your rig may require that "Settings->General->Allow Tx frequency changes while transmitting" is not checked. When using VOX with rigs that don't accept CAT QSY commands while transmitting you will have to reduce the VOX hang delay to minimum. It is by far preferable to use a hard wired PTT, particularly on rigs like yours where you can use either a CAT command or RTS on the enhanced virtual serial port at zero extra cost.

73
Bill
G4WJS.
locked Re: WSJT-X Status File Error #IssueReport

Bill Somerville
 

Hi Harry,

it is Windows shells like CMD that are picky about path directory separators, the underlying file system accepts both, nothing to do with the Windows kernel. They are normally accepted in shells and applications when quoted. Anyway, it is of little matter and you can switch to what you call Windows path directory separators.

Let us know if the Avast whitelisting helps with the issue please?

73
Bill
G4WJS.

On 26/07/2021 22:13, harry wrote:
Bill:

Thanks for the quick reply.

>> MS Windows allows both types.
Including (old) Windows 7?  When you say "allow" I presume Windows converts "/" to "\" in path names (in the kernel I hope).

>> Make sure the full path to the file is whitelisted in your AV
My anti-virus program is Avast.  Avast whitelist will not accept UNIX path separators (as displayed in the WSJT-X  diagnostic).  I did whitelist the path with Windows separators.  I will see what happens.

73
harry
KN4IJY

My On 7/26/2021 16:23, Bill Somerville wrote:
On 26/07/2021 21:06, harry wrote:

I am a new group member but a multi year WSPR user.  I just installed the latest WSJT-X software for Windows7.  At various times for unknown reasons I get the following error:

As one can see, the diagnostic path separators are "/" which is the UNIX style.  The Windows7 path separator is "\".  Is the Status File Error caused by WSPR trying to open an invalid path in Windows or an error in the diagnostic text?  I never got this error in earlier WSPR versions.

KN4IJY

Hi Harry,

the path directory separators in the message are fine, MS Windows allows both types.

This error is usually caused by interference from anti-virus applications. Make sure the full path to the file is whitelisted in your AV exclusions.

73
Bill
G4WJS.
locked Re: Lonely Out West #Q65

Hasan Schiers N0AN
 

Dave,
I just got home from a trip. I am pointed your way, calling CQ on 2nd 50.275-30A on 1500 Hz. You or anyone is welcome to call.

I'm running about 600w out to a 5 EL LFA @ 55'.

It is 21:30z right now. 73, N0AN

EN22xc
Hasan


On Mon, Jul 26, 2021 at 2:06 PM Dave Harris <vlfwoody@...> wrote:
I've been calling CQ from Syracuse, Utah daily on Q65-30a with no success. I've tried calling mostly between 1700 and 1900 UTC.
Is there something similar to Ping Jockey for Q65? 
--
Dave, K7PDW
Keep On Ham'n


locked PTT Cat Error when not using PTT #Cat_RigControl

danzee <k2ywe@...>
 

Fresh WSJT-X installation on fresh Windows7 SP1 machine.
WSJT-X works and I'm able to make FT8 contacts (WSJT-X even controls the split transmit freq), but I get a Rig Control error message after each transmit cycle and have to check "retry" or "OK" & reconfigure. I have tried all combinations of handshake settings without success.
I have had WSJT-X running on other Win7 machines and not experienced this error. I looked at the configuration file from my last WSJT-X installation and it was 8-2-N with no handshake for my FTdx-5K. Those settings still give me the error. I'm using VOX, not PTT and have WSJT-X set that way, i.e. VOX checked off.
Rig Control error details:

Hamlib error: Target VFO unaccessible

newcat.c(1663):newcat_get_ptt return(0)

newcat_set_freq: ptt still on...retry#0

rig.c(1769):rig_set_freq return(12) while setting frequency

 
locked Re: WSJT-X Status File Error #IssueReport

harry
 

Bill:

Thanks for the quick reply.

>> MS Windows allows both types.
Including (old) Windows 7?  When you say "allow" I presume Windows converts "/" to "\" in path names (in the kernel I hope).

>> Make sure the full path to the file is whitelisted in your AV
My anti-virus program is Avast.  Avast whitelist will not accept UNIX path separators (as displayed in the WSJT-X  diagnostic).  I did whitelist the path with Windows separators.  I will see what happens.

73
harry
KN4IJY

My On 7/26/2021 16:23, Bill Somerville wrote:

On 26/07/2021 21:06, harry wrote:

I am a new group member but a multi year WSPR user.  I just installed the latest WSJT-X software for Windows7.  At various times for unknown reasons I get the following error:

As one can see, the diagnostic path separators are "/" which is the UNIX style.  The Windows7 path separator is "\".  Is the Status File Error caused by WSPR trying to open an invalid path in Windows or an error in the diagnostic text?  I never got this error in earlier WSPR versions.

KN4IJY

Hi Harry,

the path directory separators in the message are fine, MS Windows allows both types.

This error is usually caused by interference from anti-virus applications. Make sure the full path to the file is whitelisted in your AV exclusions.

73
Bill
G4WJS.


9881 - 9900 of 36849