|
locked
Re: Mac M1 Memory Error
On 27/07/2021 05:06, Bob Murphy N1KWH via groups.io wrote:
Hi Gentlemen,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
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 > 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 > 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 > 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 > 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 > 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
On 26/07/2021 22:09, danzee via groups.io wrote:
Fresh WSJT-X installation on fresh Windows7 SP1 machine.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
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:
|
|
|
|
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.
|
|
|
|
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:
|
|
|
|
If you are not using JTAlert, you are missing out on a great supporting program. Download it at HamApps.com
Among the many things it does is provide an activity window that shows HF/VHF digital activity by band for FT4, FT8, QT65, JT65, JT9… Great for spotting band openings and where the digital activity is occurring. But that is only a very small part of what it provides.
______________ 73, Jim – N4ST
From: main@WSJTX.groups.io <main@WSJTX.groups.io> On Behalf Of PATRICK COKER
Sent: Monday, July 26, 2021 16:05 To: main@wsjtx.groups.io Subject: Re: [WSJTX] Lonely Out West #Q65
What is jtalert monitor ?
|
|
|
|
locked
Re: WSJT-X Status File Error
#IssueReport
On 26/07/2021 21:06, harry wrote:
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
|
|
|
|
locked
WSJT-X Status File Error
#IssueReport
harry
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
|
|
|
|
Jim Brown
On 7/26/2021 12:05 PM, Dave Harris 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.Not DEDICATED to Q65, but ON4KST chat and the Slack VHF group are used for coordinating all sorts of skeds, including Q65. Use the link below to join the Slack group. https://join.slack.com/t/vhf-chat/shared_invite/zt-a8qh72u9-PVVYUdMiSyuswPGAtIti9w 73, Jim K9YC
|
|
|
|
PATRICK COKER
What is jtalert monitor ?
toggle quoted messageShow quoted text
On Jul 26, 2021, at 12:57 PM, Jim - N4ST <newsgroup@...> wrote:
|
|
|
|
I just keep an eye on the JTAlert activity monitor.
__________ 73, Jim – N4ST
From: main@WSJTX.groups.io <main@WSJTX.groups.io> On Behalf Of Dave Harris
Sent: Monday, July 26, 2021 15:07 To: main@WSJTX.groups.io Subject: [WSJTX] Lonely Out West #Q65
Sorry I neglected to say I'm calling on 6M.
|
|
|
|
Dave Harris
Sorry I neglected to say I'm calling on 6M.
-- Dave, K7PDW Keep On Ham'n
|
|
|
|
Dave Harris
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
|
|
|
