|
locked
Compile 2.2.2 Deb (Buster), 84% stopped at cannot find -ludev
Hi all, took me a while to sort this out. Got stopped at 84% with
cannot find -ludev
Might help someone else if they get hung up here.
apt install libudev-dev
Fixed it :-)
[ 84%] Building CXX object
CMakeFiles/wsjtx.dir/wsjtx_autogen/mocs_compilation.cpp.o
[ 84%] Linking CXX executable wsjtx
/usr/bin/ld: cannot find -ludev
collect2: error: ld returned 1 exit status
make[5]: *** [CMakeFiles/wsjtx.dir/build.make:787: wsjtx] Error 1
make[4]: *** [CMakeFiles/Makefile2:379: CMakeFiles/wsjtx.dir/all] Error
2
make[3]: *** [Makefile:152: all] Error 2
make[2]: *** [CMakeFiles/wsjtx-build.dir/build.make:61: wsjtx-
prefix/src/wsjtx-stamp/wsjtx-build] Error 2
make[1]: *** [CMakeFiles/Makefile2:233: CMakeFiles/wsjtx-build.dir/all]
Error 2
make: *** [Makefile:84: all] Error 2
dkc@BlackBox:~/wsjtx222/wsjtx-2.2.2$
|
|
|
locked
Re: miles instead of km?
What do you want miles for? 73 Phil GM3ZZA Sent from Mail for Windows 10
From: diyerSent: 03 November 2020 19:45 To: main@WSJTX.groups.ioSubject: [WSJTX] miles instead of km? after an update I'm showing km not miles. I found a setting to change before but I can't find it anymore. I wonder if new versions don't have that option? -- 73 Phil GM3ZZA
|
|
|
locked
Re: miles instead of km?
Bill Somerville
On 03/11/2020 19:39, diyer wrote: after an update I'm showing km not miles. I found a setting to change before but I can't find it anymore. I wonder if new versions don't have that option? OM, "Settings->General->Display->Display distance in miles". 73 Bill G4WJS.
|
|
|
locked
Re: miles instead of km?
oops, my bad under preferences display. how did I miss that?
|
|
|
after an update I'm showing km not miles. I found a setting to change before but I can't find it anymore. I wonder if new versions don't have that option?
|
|
|
locked
Re: Dependency is not satisfiable: libgfortran3 (>= 4.8.2)
Hi Dale
Go for it !
I built from sources for 2.2.2 on the current Debian Buster (in a VM). Easy - see attached. Also built 2.3.0rc1 the same way.
I got several error 502s (server hang up) from the repository when downloading the tools and libs (422MB), retrying worked ok though, so no problem.
I have a bash script if you need it.
73's
Rick(GM4JIB)
toggle quoted messageShow quoted text
On 03/11/2020 14:41, Dale Coleman wrote: On Mon, 2020-11-02 at 13:11 +0000, Bill Somerville wrote:
Thanks for the replies, I did find: libgfortran3_6.3.0
But it had a dependency issue with gcc-6-base.
Kinda like the idea of compiling from souce.
First I think I will reveiw the change log from my version 2.0.0 and
compare it to 2.2.2. 2.0.0 is working great so I might wait a bit.
root@BlackBox:/home/dkc/Downloads# gdebi libgfortran3_6.3.0-
18+deb9u1_amd64.deb
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading state information... Done
This package is uninstallable
Dependency is not satisfiable: gcc-6-base (= 6.3.0-18+deb9u1)
root@BlackBox:/home/dkc/Downloads#
|
|
|
Ken Bills
Have an ANAN-100 and use Kenwood TS-2000 for rig control.
I can send a few screenshots if you need any help.
73
Ken-W9KB
|
|
|
locked
Re: sound device settings changed
Nope Ken, micros*!t effect! Though they are spooky... 73 - John - N7GHZ
Also experienced the same situation this morning.... and setup hasn’t changed for months.
Windows playback slider was mysteriously lowered to about 75 percent.
‘Halloween’ effect?
73
Ken-W9KB
|
|
|
locked
Re: sound device settings changed
Ken Bills
Also experienced the same situation this morning.... and setup hasn’t changed for months.
Windows playback slider was mysteriously lowered to about 75 percent.
‘Halloween’ effect?
73
Ken-W9KB
|
|
|
locked
Re: Dependency is not satisfiable: libgfortran3 (>= 4.8.2)
On Mon, 2020-11-02 at 13:11 +0000, Bill Somerville wrote: Thanks for the replies, I did find: libgfortran3_6.3.0 But it had a dependency issue with gcc-6-base. Kinda like the idea of compiling from souce. First I think I will reveiw the change log from my version 2.0.0 and compare it to 2.2.2. 2.0.0 is working great so I might wait a bit. root@BlackBox:/home/dkc/Downloads# gdebi libgfortran3_6.3.0- 18+deb9u1_amd64.deb Reading package lists... Done Building dependency tree Reading state information... Done Reading state information... Done This package is uninstallable Dependency is not satisfiable: gcc-6-base (= 6.3.0-18+deb9u1) root@BlackBox:/home/dkc/Downloads# Hi Dale and Jeff,
that is correct and they seem to prefer new packages rather often, I
assume because of breaking changes as the Fortran language evolves. I
have tried to include alternatives in the Debian and RPM control file
requirements for the next release. Unfortunately there is a defect in
the dependencies listed for WSJT-X v2.3.0 RC1, the next release will
be better.
Note that the Debian package we release for WSJT-X v2.3.0 RC1 targets
Debian 10 (Buster) based distribution versions like Ubuntu 20.04. As
Rick notes, building from sources is the right way to go if there are
dependency issues. I don't understand why anyone would consider
importing packages not in the mainstream distro repositories, that is
risking breaking any number of other packages whereas building WSJT-X
from sources will never require any packages not in your current
distro repositories.
73
Bill
G4WJS.
On 02/11/2020 10:30, Rick Chapman wrote:
Jeff
I think you are mistaken. libfortran3 and libfortran5 are
different packages, so libfortran5 can never satisfy a dependency
on libfortran3.
Dale
If libfortran3 is not in your repository, you can (should) build
WSJT-X from sources. Download the wsjtx-2.2.2.tgz file and read
the install file it contains.
Build from sources is pretty easy but there are some fairly obvious
typos in the install file.
Where it refers to "SVN" this may be in your repository as
"subversion"
"libqt5libserialport5-dev" should be "libqt5serialport5-dev"
"libusb-1.0.0-dev" should be "libusb-1.0-0-dev"
Also prior to running the line "$ tar xzf wsjtx-2.0.0.tgz" which
should be "$ tar xzf wsjtx-2.2.2.tgz" you need to have copied the
tgz file into the build directory
Also "cmake -DWSJT_SKIP_MANPAGES=ON -DWSJT_GENERATE_DOCS=OFF
../wsjtx-2.0.0" should end with 2.2.2 as well
Also be aware at the line "$ cmake --build ." this ends with a
dot which is important. The tools and libraries were about 300Mb to download Build will
take a few minutes to complete. This approach will get round all
your dependency problems.
Hope this helps
Rick(GM4JIB)
On 02/11/2020 02:45, Jeff Stillinger via groups.io wrote:
Read your error message " wsjtx depends on libgfortran3 (>=
4.8.2); however: "
The ">=" is the mathematical symbol for equal to or greater
than. Therefore, libgfortran5 is greater than 4.8.2 and should
meet the dependency.
On 11/1/20 12:22 PM, Dale Coleman wrote:
On Sun, 2020-11-01 at 10:46 -0600, Jeff Stillinger via
groups.io wrote:
Thanks for the reply. I'm confused over libgfortran3 vs
libgfortran5
and the required version.
Looks like libgfortran5 is avaiable but not libgfortran3
root@BlackBox:/home/dkc# apt-cache search libgfortran5
libgfortran5 - Runtime library for GNU Fortran applications
libgfortran5-dbg - Runtime library for GNU Fortran applications
(debug
symbols)
libgfortran5-amd64-cross - Runtime library for GNU Fortran
applications
libgfortran5-arm64-cross - Runtime library for GNU Fortran
applications
libgfortran5-armel-cross - Runtime library for GNU Fortran
applications
libgfortran5-armhf-cross - Runtime library for GNU Fortran
applications
libgfortran5-i386-cross - Runtime library for GNU Fortran
applications
libgfortran5-mips-cross - Runtime library for GNU Fortran
applications
|
|
|
locked
Re: new computer, CAT doesn't work right
Yes, thats what I was thinking of. For some reason I thought it also broke the 991
On Nov 3, 2020, at 8:42 AM, Bill Somerville < g4wjs@...> wrote:
Jeff,
that's news to me, are you sure you are
not thinking of the issues with the FT-897(D) and FT-817(D) models
in WSJT-X v2.2.2 where the FT-857 model has to be used because of
a Hamlib defect?
73
Bill
G4WJS.
On 03/11/2020 13:37, Jeff Townsend
wrote:
Bill,
If he is using 2.2.2 isn’t the FT991 support broken?
Won’t he need to select the other Yaesu rig? I don’t remember
which one.
On Nov 3, 2020, at 6:51 AM, Bill Somerville
< g4wjs@...>
wrote:
Hi Jon,
from what you have reported
you seem to have everything set up correctly for CAT
control of your FT-991A, it should be working. All I
can suggest is double-checking everything again. Here
is a list of things to check:
- Virtual serial port drivers installed,
if the two COM ports appear in Windows Device
Manager when you connect the USB cable, that is
reasonable evidence that is working.
- USB cable connected (I note that with
an alternative cable you had audio errors which
make me suspicious that particular cable may have
a problem).
- Yaesu FT-991 selected in WSJT-X
"Settings->Radio->Rig.
- The COM port that is the Enhanced
serial port selected in
"Settings->Radio->CAT Control->Serial
Port".
- In "Settings->Radio->CAT
Control->Serial Port Parameters":
- Baud rate matching rig (MENU 031)
"CAT RATE",
- Data Bits and Stop Bits both set to
Default,
- Handshake set to Default or Hardware
if the rig (MENU 033) "CAT RTS" is ENABLE, None
if it is DISABLE,
- In Force Control Lines both DTR and
RTS set to blank.
- For "Settings->Radio->PTT
Method", and "Settings->Radio->PTT
Method->Port", you have several options:
- Select "CAT" and on the rig (MENU
071) "DATA PTT SELECT" DAKY,
- Select "RTS" and on the rig (MENU
071) "DATA PTT SELECT" RTS and select the
Standard COM port,
- Select "DTR" and on the rig (MENU
071) "DATA PTT SELECT" DTR and select the
Standard COM port.
- Set the rig (MENU 070) "DATA IN SELECT"
to REAR.
- Set the rig (MENU 072) "DATA PORT
SELECT" to USB, and
"Settings->Radio->Mode->Data/Pkt".
73
Bill
G4WJS.
On 03/11/2020 03:26, Jon
Ermels via groups.io wrote:
i HAVE
THREE HERNIATED DISCS IN MY BACH AND IT'S TIME
FOR THE OXYCODONE AND TRACTION, i'LL TRY
TOMORROW, WHO KNOWS, IT MIGHT JUST WORK. THANK
YOU FOR HELPING ME.
73 de NØIGU Jon
|
|
|
locked
Re: new computer, CAT doesn't work right
Bill Somerville
Jeff,
that's news to me, are you sure you are
not thinking of the issues with the FT-897(D) and FT-817(D) models
in WSJT-X v2.2.2 where the FT-857 model has to be used because of
a Hamlib defect?
73
Bill
G4WJS.
toggle quoted messageShow quoted text
On 03/11/2020 13:37, Jeff Townsend
wrote:
Bill,
If he is using 2.2.2 isn’t the FT991 support broken?
Won’t he need to select the other Yaesu rig? I don’t remember
which one.
On Nov 3, 2020, at 6:51 AM, Bill Somerville
< g4wjs@...>
wrote:
Hi Jon,
from what you have reported
you seem to have everything set up correctly for CAT
control of your FT-991A, it should be working. All I
can suggest is double-checking everything again. Here
is a list of things to check:
- Virtual serial port drivers installed,
if the two COM ports appear in Windows Device
Manager when you connect the USB cable, that is
reasonable evidence that is working.
- USB cable connected (I note that with
an alternative cable you had audio errors which
make me suspicious that particular cable may have
a problem).
- Yaesu FT-991 selected in WSJT-X
"Settings->Radio->Rig.
- The COM port that is the Enhanced
serial port selected in
"Settings->Radio->CAT Control->Serial
Port".
- In "Settings->Radio->CAT
Control->Serial Port Parameters":
- Baud rate matching rig (MENU 031)
"CAT RATE",
- Data Bits and Stop Bits both set to
Default,
- Handshake set to Default or Hardware
if the rig (MENU 033) "CAT RTS" is ENABLE, None
if it is DISABLE,
- In Force Control Lines both DTR and
RTS set to blank.
- For "Settings->Radio->PTT
Method", and "Settings->Radio->PTT
Method->Port", you have several options:
- Select "CAT" and on the rig (MENU
071) "DATA PTT SELECT" DAKY,
- Select "RTS" and on the rig (MENU
071) "DATA PTT SELECT" RTS and select the
Standard COM port,
- Select "DTR" and on the rig (MENU
071) "DATA PTT SELECT" DTR and select the
Standard COM port.
- Set the rig (MENU 070) "DATA IN SELECT"
to REAR.
- Set the rig (MENU 072) "DATA PORT
SELECT" to USB, and
"Settings->Radio->Mode->Data/Pkt".
73
Bill
G4WJS.
On 03/11/2020 03:26, Jon
Ermels via groups.io wrote:
i HAVE
THREE HERNIATED DISCS IN MY BACH AND IT'S TIME
FOR THE OXYCODONE AND TRACTION, i'LL TRY
TOMORROW, WHO KNOWS, IT MIGHT JUST WORK. THANK
YOU FOR HELPING ME.
73 de NØIGU Jon
|
|
|
locked
Re: new computer, CAT doesn't work right
Bill,
If he is using 2.2.2 isn’t the FT991 support broken? Won’t he need to select the other Yaesu rig? I don’t remember which one. On Nov 3, 2020, at 6:51 AM, Bill Somerville < g4wjs@...> wrote:
Hi Jon,
from what you have reported you seem to
have everything set up correctly for CAT control of your FT-991A,
it should be working. All I can suggest is double-checking
everything again. Here is a list of things to check:
- Virtual serial port drivers installed, if the two COM ports
appear in Windows Device Manager when you connect the USB
cable, that is reasonable evidence that is working.
- USB cable connected (I note that with an alternative cable
you had audio errors which make me suspicious that particular
cable may have a problem).
- Yaesu FT-991 selected in WSJT-X "Settings->Radio->Rig.
- The COM port that is the Enhanced serial port selected in
"Settings->Radio->CAT Control->Serial Port".
- In "Settings->Radio->CAT Control->Serial Port
Parameters":
- Baud rate matching rig (MENU 031) "CAT RATE",
- Data Bits and Stop Bits both set to Default,
- Handshake set to Default or Hardware if the rig (MENU 033)
"CAT RTS" is ENABLE, None if it is DISABLE,
- In Force Control Lines both DTR and RTS set to blank.
- For "Settings->Radio->PTT Method", and
"Settings->Radio->PTT Method->Port", you have several
options:
- Select "CAT" and on the rig (MENU 071) "DATA PTT SELECT"
DAKY,
- Select "RTS" and on the rig (MENU 071) "DATA PTT SELECT"
RTS and select the Standard COM port,
- Select "DTR" and on the rig (MENU 071) "DATA PTT SELECT"
DTR and select the Standard COM port.
- Set the rig (MENU 070) "DATA IN SELECT" to REAR.
- Set the rig (MENU 072) "DATA PORT SELECT" to USB, and
"Settings->Radio->Mode->Data/Pkt".
73
Bill
G4WJS.
On 03/11/2020 03:26, Jon Ermels via
groups.io wrote:
i HAVE THREE HERNIATED
DISCS IN MY BACH AND IT'S TIME FOR THE OXYCODONE AND
TRACTION, i'LL TRY TOMORROW, WHO KNOWS, IT MIGHT JUST WORK.
THANK YOU FOR HELPING ME.
73 de NØIGU Jon
i EVEN TRIED A NEW CABLE, NO JOY. NOW
IT SAYS " ERROR IN SOUND INPUT " WHEN I START THE
PROGRAM. I REBOOTED THE COPMPTER ALSO
73
de NØIGU Jon
On Monday, November 2, 2020, 08:34:43 PM
CST, Bill Somerville
<g4wjs@...> wrote:
Jon,
when
you have the virtual COM port drivers
installed and the rig plugged in you will
have two COM ports visible in the Windows
Device Manager, the second port (Enhanced)
is the one that is used for CAT control,
that is the one that needs to be selected
in "Settings->Radio->Cat->Serial
Port".
If
you have Hardware handshaking enabled then
you must also have the rig menu item 33
(CAT RTS) set to ENABLE.
73
Bill
G4WJS.
On
03/11/2020 02:25, Jon Ermels via
groups.io wrote:
SRI ABOUT MY TYPING,
TRYING TO HURRY, ANSWERS BELOW
73
de NØIGU Jon
On Monday, November 2, 2020,
07:18:45 PM CST, Bill Somerville <g4wjs@...>
wrote:
Hi
Jon,
have
you installed the virtual
COM port drivers for the rig
on your PC? YES, COPIED FROM
THE YAESU WEB SITE
Do you have the
right COM port selected for
CAT (you need the extended
COM port)? YES, COMPORT,
RADIO AND WSJTX ARE SAME
As you have
Hardware handshaking
enabled, do you have RTS
enabled in the rig's menu?
NOTHING IS BUT WHAT PORT?
73
Bill
G4WJS.
On
03/11/2020 01:12, Jon
Ermels via groups.io
wrote:
Hi
Bill, FT-991A, USB
on radio to USB on
computer, same as
old computer. what
baffles me is it
turns on the radio
and decodes and then
says the CAT doesn't
work.
Com
poer at the
codex
port says,
Baud
38400 same as radio,
8 data
bits,
1 stop
bit,
HDW
hand shake
73
de NØIGU Jon
On Monday,
November 2, 2020,
07:01:18 PM CST,
Bill Somerville <g4wjs@...>
wrote:
On
03/11/2020 00:45,
Jon Ermels via
groups.io wrote:
> old computer
worked on same
radio, new
computer, used it
for WSJTX
> before with
different radio,
CODEX ok, WXJTW
version 2.2.2, I
get rig
> failure
message, hamlib
error IO error
while testing VFO,
cat test in
> settings
stays red, it
decodes whatever
freq the radio is
set to but
> says it's on
160M, stills start
the radio when
WSJTX starts up.
Hi Jon,
which radio? How
is it connected to
your PC for CAT
control? What
settings do you
have in
"Settings->Radio" com
port 6, as the
Port says, ?
73
Bill
G4WJS.
|
|
|
locked
Re: new computer, CAT doesn't work right
Bill Somerville
Hi Jon,
from what you have reported you seem to
have everything set up correctly for CAT control of your FT-991A,
it should be working. All I can suggest is double-checking
everything again. Here is a list of things to check:
- Virtual serial port drivers installed, if the two COM ports
appear in Windows Device Manager when you connect the USB
cable, that is reasonable evidence that is working.
- USB cable connected (I note that with an alternative cable
you had audio errors which make me suspicious that particular
cable may have a problem).
- Yaesu FT-991 selected in WSJT-X "Settings->Radio->Rig.
- The COM port that is the Enhanced serial port selected in
"Settings->Radio->CAT Control->Serial Port".
- In "Settings->Radio->CAT Control->Serial Port
Parameters":
- Baud rate matching rig (MENU 031) "CAT RATE",
- Data Bits and Stop Bits both set to Default,
- Handshake set to Default or Hardware if the rig (MENU 033)
"CAT RTS" is ENABLE, None if it is DISABLE,
- In Force Control Lines both DTR and RTS set to blank.
- For "Settings->Radio->PTT Method", and
"Settings->Radio->PTT Method->Port", you have several
options:
- Select "CAT" and on the rig (MENU 071) "DATA PTT SELECT"
DAKY,
- Select "RTS" and on the rig (MENU 071) "DATA PTT SELECT"
RTS and select the Standard COM port,
- Select "DTR" and on the rig (MENU 071) "DATA PTT SELECT"
DTR and select the Standard COM port.
- Set the rig (MENU 070) "DATA IN SELECT" to REAR.
- Set the rig (MENU 072) "DATA PORT SELECT" to USB, and
"Settings->Radio->Mode->Data/Pkt".
73
Bill
G4WJS.
toggle quoted messageShow quoted text
On 03/11/2020 03:26, Jon Ermels via
groups.io wrote:
i HAVE THREE HERNIATED
DISCS IN MY BACH AND IT'S TIME FOR THE OXYCODONE AND
TRACTION, i'LL TRY TOMORROW, WHO KNOWS, IT MIGHT JUST WORK.
THANK YOU FOR HELPING ME.
73 de NØIGU Jon
On Monday, November 2, 2020, 08:50:03 PM CST, Jon Ermels
via groups.io <n0igu@...> wrote:
i EVEN TRIED A NEW CABLE, NO JOY. NOW
IT SAYS " ERROR IN SOUND INPUT " WHEN I START THE
PROGRAM. I REBOOTED THE COPMPTER ALSO
73
de NØIGU Jon
On Monday, November 2, 2020, 08:34:43 PM
CST, Bill Somerville
<g4wjs@...> wrote:
Jon,
when
you have the virtual COM port drivers
installed and the rig plugged in you will
have two COM ports visible in the Windows
Device Manager, the second port (Enhanced)
is the one that is used for CAT control,
that is the one that needs to be selected
in "Settings->Radio->Cat->Serial
Port".
If
you have Hardware handshaking enabled then
you must also have the rig menu item 33
(CAT RTS) set to ENABLE.
73
Bill
G4WJS.
On
03/11/2020 02:25, Jon Ermels via
groups.io wrote:
SRI ABOUT MY TYPING,
TRYING TO HURRY, ANSWERS BELOW
73
de NØIGU Jon
On Monday, November 2, 2020,
07:18:45 PM CST, Bill Somerville <g4wjs@...>
wrote:
Hi
Jon,
have
you installed the virtual
COM port drivers for the rig
on your PC? YES, COPIED FROM
THE YAESU WEB SITE
Do you have the
right COM port selected for
CAT (you need the extended
COM port)? YES, COMPORT,
RADIO AND WSJTX ARE SAME
As you have
Hardware handshaking
enabled, do you have RTS
enabled in the rig's menu?
NOTHING IS BUT WHAT PORT?
73
Bill
G4WJS.
On
03/11/2020 01:12, Jon
Ermels via groups.io
wrote:
Hi
Bill, FT-991A, USB
on radio to USB on
computer, same as
old computer. what
baffles me is it
turns on the radio
and decodes and then
says the CAT doesn't
work.
Com
poer at the
codex
port says,
Baud
38400 same as radio,
8 data
bits,
1 stop
bit,
HDW
hand shake
73
de NØIGU Jon
On Monday,
November 2, 2020,
07:01:18 PM CST,
Bill Somerville <g4wjs@...>
wrote:
On
03/11/2020 00:45,
Jon Ermels via
groups.io wrote:
> old computer
worked on same
radio, new
computer, used it
for WSJTX
> before with
different radio,
CODEX ok, WXJTW
version 2.2.2, I
get rig
> failure
message, hamlib
error IO error
while testing VFO,
cat test in
> settings
stays red, it
decodes whatever
freq the radio is
set to but
> says it's on
160M, stills start
the radio when
WSJTX starts up.
Hi Jon,
which radio? How
is it connected to
your PC for CAT
control? What
settings do you
have in
"Settings->Radio"
com
port 6, as the
Port says, ?
73
Bill
G4WJS.
|
|
|
locked
Re: Continuing problem, WSJT-X fails to decode
I had the same problem. I tried the DG2YCB clone and the decode problem is gone.
https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.3.0/
Copy from Uwe:
” - I kept the DX-optimized FT8 and FT4 decoders from previous version 2.2.2.”
The drawback is that it might be some more ghosts, but that I can live with.
Lars SM3CCM
Skickades från
E-post för Windows 10
Hi Bill,
Just thought I’d try this one last time.
If there is some reason you don’t want to respond to this could you please just let me know so I can stop trying ?
toggle quoted messageShow quoted text
HI Bill,
Just following up on this - I hope you got my reply below. Did you want me to send the video and if so, where ?
Hi Bill,
Again, thanks for the response.
No, that’s not the issue here. I have seem that come up on the forum many times. I’ve never used that function so never checked it and just to be complete verified again
that it’s still unchecked before posting this. This is something different, like several others have reported, and has been going on for a long long time. After grabbing the .wav files this time I restarted WSJT-X and it’s unfrozen now but if there’s something
else you’d like me to collect and send please let me know.
On Oct 28, 2020, at 2:45 PM, Bill Somerville <g4wjs@...> wrote:
there is a known defect in WSJT-X where the Band Activity window stops scrolling down to show them latest decodes, the defect only occurs when "Settings->General->Start new
period decodes at top" is checked. It occurs after a large number of decodes are printed. You can check if this is the issue you are suffering by manually scrolling down the Band Activity window to reveal the apparently missing decodes.
You can work around this issue either by unchecking the "Settings->General->Start new period decodes at top" option or by erasing the Band Activity window periodically (right-click
and select "Erase").
On 28/10/2020 21:40, Russ Ravella via groups.io wrote:
Hi Bill,
Yeah, that’s what I was saying in my post. Yet WSJT-X was frozen when I collected them. This thread is asking why that’s happening. You asked its originator to provide
.wav files so I have also. As I mentioned in my post, I also took a video which I can provide if you think it might be helpful. The question remains, why is WSJT-X freezing ?
On Oct 28, 2020, at 9:05 AM, Bill Somerville <g4wjs@...> wrote:
On 28/10/2020 04:52, Russ Ravella via groups.io wrote:
HI Bill,
Following up on this, I’ve been off the air for a few days but fired up WSJT-X today and got another freeze. I’m sending you the last three .wav files that were saved consistent
with your request below. To me they just sound like normal audio and seem to terminate normally. WSJT-X was up and frozen when I grabbed them and after I did, and closed WSJT-X, I checked and no more .wav files had been written. I also took a short video
showing WSJT-X with the waterfall frozen but the 15-sec timer still running and Flex DAX showing audio still being generated by the radio (that is, the radio and audio connection weren't frozen). Being a video file, I won’t attach it here in case you’d rather
I sent it via another means.
I’ve been getting these freezes since at least the first V2 and maybe before. I can’t correlate them to anything. During that time I’ve had four different Flex radios (quality
is not a Flex Radio attribute - software or hardware) and several revisions of SSDR, CAT, DAX and Windows 10 software (I’m on 2004 now) running on three different fast laptops each set up from scratch. I don’t use any third party AV software as they’re all
basically malware themselves. The freezes seem to just “happen”. Sometimes closing and restarting WSJT-X fixes it and sometimes I have to restart the whole computer. I’ve lost at least one potential ATNO due to this.
Thanks for helping as always !
Hi Russ,
those three .WAV files look fine to me, I get the following decodes from them:
------------------------------------ 20m
230330 10 0.4 1847 ~ YS1GMV VE7XT R-18
230330 0 0.3 1331 ~ N2MSF AG5VE R+03
230330 7 0.3 2144 ~ JA9IFF W3MMM -08
230330 5 0.4 445 ~ CQ KF5TVG EM26 CQ Zone 4
230330 -3 0.3 900 ~ CQ KQ1S EM94 U.S.A.
230330 2 0.3 2199 ~ PP5DE K0HMZ R-16
230330 21 0.3 672 ~ YS1GMV WB0TAX EM32
230330 -8 0.3 1594 ~ KM6KJI W3DJS EM83
230330 -12 0.4 1102 ~ XL3T K4TT FN44
230330 -12 0.3 2550 ~ CQ LU5CAT GF05 SA
230330 -6 0.4 1791 ~ WA8QNN KC5TT -02
230330 -10 0.4 360 ~ YS1GMV KE0ELU -19
230330 -1 1.3 734 ~ CQ AF5DE EM25 CQ Zone 4
230330 -6 0.8 2324 ~ BU2BV KJ7OTZ CN87
230330 -8 0.3 833 ~ W7SWB WD9IQN -16
230330 -5 0.1 1642 ~ NN2T WA5VXI EM25
230330 -8 0.3 778 ~ CQ KC9VW EL29 CQ Zone 4
230330 -19 0.3 2086 ~ CQ KD9KCK EN61 CQ Zone 4
230330 -10 0.4 2332 ~ KJ4SRY VA6KL -06
230330 -6 0.4 1822 ~ KE3VV W6ASO R+01
230330 -15 0.4 1313 ~ JA0ARF KR7X R-14
230330 -9 0.5 1639 ~ NN2T AC0FS EN34
230330 -18 0.3 983 ~ BH4TVU K9RR R-16
230330 -18 0.5 1976 ~ VE2JI LW8DHX -13
230330 -18 0.5 2016 ~ KI5KSE KB4DPH EL88
230330 -24 0.1 1084 ~ W5FHW WB9MSM EN53
230330 -23 0.7 2000 ~ CQ KF0AQK EN21 CQ Zone 4
230330 -14 0.4 1648 ~ VA3TPS KD9MKR RR73
230330 -13 0.1 1608 ~ CQ KF9KV EN52 CQ Zone 4
------------------------------------ 20m
230345 -17 -0.1 1492 ~ VY1MB KN4GGH EM91
230345 -3 -1.6 1415 ~ CQ AI4QT EM74 U.S.A.
230345 -10 0.5 2275 ~ CQ W7OK CN86 CQ Zone 3
230345 -7 0.3 888 ~ KB7THX AI4VV RRR
230345 8 0.4 1638 ~ AC0FS NN2T +01
230345 0 0.6 1208 ~ WB9MSM W5FHW EM02
230345 -3 0.3 1942 ~ KB4DPH KI5KSE +06
230345 -13 0.3 2051 ~ W5CRN KB7SAT 73
230345 9 0.3 1695 ~ CQ W0WND DM97 CQ Zone 4
230345 17 0.3 530 ~ AB1WG N5LDO 73
230345 -13 0.3 2206 ~ JE3BMU N7CTB CN85
230345 6 0.4 424 ~ CO8AFG W8KEN -14
230345 -14 0.4 1890 ~ VA6KL KJ4SRY R-17
230345 -6 0.3 2795 ~ AG5VE N2MSF RR73
230345 -15 0.4 1553 ~ XP3A N4AN R-19
230345 -14 0.5 744 ~ EA5IYK VE6ATS R-11
230345 -2 0.3 575 ~ KN6ITP K4BWM FM14
230345 -4 0.4 1667 ~ J88DCP/R WB4KTF EM10
230345 -12 0.2 852 ~ KN6ITP KB4RRN EM90
230345 -17 0.3 1958 ~ KR7X JA0ARF RR73
230345 -16 0.3 900 ~ CQ KK4OMJ EM78 U.S.A.
230345 -24 0.3 1777 ~ KC4VKG N8FRI EN81
230345 -22 0.3 2054 ~ CQ N2OO FM29 U.S.A.
230345 -10 0.4 1072 ~ KD9KCK N3CKI FM03
230345 -14 0.4 1717 ~ WA2EPI <...> -08
230345 -1 0.4 628 ~ JE3BMU WA7VIZ CN92
230345 -9 0.3 1624 ~ KC9VW W0BLE EN31
230345 -10 0.4 1605 ~ KN6ITP KB8SRX 73
230345 -24 -0.1 1365 ~ CQ K3ADU FN10 a1 U.S.A.
230345 -20 0.6 1649 ~ KD9MKR VA3TPS 73
------------------------------------ 20m
230400 -18 1.0 1488 ~ HC5EG PY7YZ 73
230400 8 0.3 1331 ~ N2MSF AG5VE 73
230400 -5 0.3 900 ~ CQ KQ1S EM94 U.S.A.
230400 -1 0.1 1966 ~ N5AQM WA5VXI EM25
230400 4 0.4 445 ~ VE3XTF KF5TVG -16
230400 7 0.3 2144 ~ JA9IFF W3MMM RR73
230400 0 0.3 778 ~ CQ KC9VW EL29 CQ Zone 4
230400 1 0.3 2199 ~ PP5DE K0HMZ 73
230400 -8 0.4 360 ~ YS1GMV KE0ELU -19
230400 -12 0.3 1051 ~ N2OO KE5GXX EL17
230400 -4 0.5 1639 ~ NN2T AC0FS R+07
230400 -8 0.4 1102 ~ XL3T K4TT FN44
230400 -9 0.3 2548 ~ CQ LU5CAT GF05 SA
230400 -5 0.8 2324 ~ BU2BV KJ7OTZ CN87
230400 -15 0.3 983 ~ BH4TVU K9RR R-16
230400 5 0.4 1847 ~ YS1GMV VE7XT R-18
230400 6 0.4 1823 ~ KE3VV W6ASO R+01
230400 -13 0.3 833 ~ W7SWB WD9IQN -16
230400 -12 0.5 2015 ~ KI5KSE KB4DPH R+01
230400 -7 0.3 1313 ~ JA0ARF KR7X 73
230400 2 0.1 1791 ~ WA8QNN KC5TT -14
230400 -9 0.4 2333 ~ KJ4SRY VA6KL RR73
230400 -19 0.3 2088 ~ CQ KD9KCK EN61 CQ Zone 4
230400 -15 0.7 2000 ~ CQ KF0AQK EN21 CQ Zone 4
230400 -8 0.3 1794 ~ LU9HCO W3DJS EM83
230400 -16 0.5 1977 ~ VE2JI LW8DHX -13
230400 -15 0.2 1608 ~ CQ KF9KV EN52 CQ Zone 4
230400 -12 0.4 1649 ~ VA3TPS KD9MKR RR73
73
Bill
G4WJS.
|
|
|
locked
Re: Continuing problem, WSJT-X fails to decode
Hi Bill,
Just thought I’d try this one last time.
If there is some reason you don’t want to respond to this could you please just let me know so I can stop trying ?
Thanks, Russ KR6W
HI Bill,
Just following up on this - I hope you got my reply below. Did you want me to send the video and if so, where ?
Thanks, Russ KR6W
Hi Bill,
Again, thanks for the response.
No, that’s not the issue here. I have seem that come up on the forum many times. I’ve never used that function so never checked it and just to be complete verified again that it’s still unchecked before posting this. This is something different, like several others have reported, and has been going on for a long long time. After grabbing the .wav files this time I restarted WSJT-X and it’s unfrozen now but if there’s something else you’d like me to collect and send please let me know.
Thanks, Russ KR6W
On Oct 28, 2020, at 2:45 PM, Bill Somerville < g4wjs@...> wrote:
Russ,
there is a known defect in WSJT-X where the Band Activity window stops scrolling down to show them latest decodes, the defect only occurs when "Settings->General->Start new period decodes at top" is checked. It occurs after a large number of decodes are printed. You can check if this is the issue you are suffering by manually scrolling down the Band Activity window to reveal the apparently missing decodes.
You can work around this issue either by unchecking the "Settings->General->Start new period decodes at top" option or by erasing the Band Activity window periodically (right-click and select "Erase").
73
Bill
G4WJS.
On 28/10/2020 21:40, Russ Ravella via groups.io wrote: Hi Bill,
Thanks for the response.
Yeah, that’s what I was saying in my post. Yet WSJT-X was frozen when I collected them. This thread is asking why that’s happening. You asked its originator to provide .wav files so I have also. As I mentioned in my post, I also took a video which I can provide if you think it might be helpful. The question remains, why is WSJT-X freezing ?
Thanks, Russ KR6W
On Oct 28, 2020, at 9:05 AM, Bill Somerville < g4wjs@...> wrote:
On 28/10/2020 04:52, Russ Ravella via groups.io wrote: HI Bill,
Following up on this, I’ve been off the air for a few days but fired up WSJT-X today and got another freeze. I’m sending you the last three .wav files that were saved consistent with your request below. To me they just sound like normal audio and seem to terminate normally. WSJT-X was up and frozen when I grabbed them and after I did, and closed WSJT-X, I checked and no more .wav files had been written. I also took a short video showing WSJT-X with the waterfall frozen but the 15-sec timer still running and Flex DAX showing audio still being generated by the radio (that is, the radio and audio connection weren't frozen). Being a video file, I won’t attach it here in case you’d rather I sent it via another means.
I’ve been getting these freezes since at least the first V2 and maybe before. I can’t correlate them to anything. During that time I’ve had four different Flex radios (quality is not a Flex Radio attribute - software or hardware) and several revisions of SSDR, CAT, DAX and Windows 10 software (I’m on 2004 now) running on three different fast laptops each set up from scratch. I don’t use any third party AV software as they’re all basically malware themselves. The freezes seem to just “happen”. Sometimes closing and restarting WSJT-X fixes it and sometimes I have to restart the whole computer. I’ve lost at least one potential ATNO due to this.
Thanks for helping as always ! Russ KR6W
Hi Russ, those three .WAV files look fine to me, I get the following decodes from them: ------------------------------------ 20m 230330 10 0.4 1847 ~ YS1GMV VE7XT R-18 230330 0 0.3 1331 ~ N2MSF AG5VE R+03 230330 7 0.3 2144 ~ JA9IFF W3MMM -08 230330 5 0.4 445 ~ CQ KF5TVG EM26 CQ Zone 4 230330 -3 0.3 900 ~ CQ KQ1S EM94 U.S.A. 230330 2 0.3 2199 ~ PP5DE K0HMZ R-16 230330 21 0.3 672 ~ YS1GMV WB0TAX EM32 230330 -8 0.3 1594 ~ KM6KJI W3DJS EM83 230330 -12 0.4 1102 ~ XL3T K4TT FN44 230330 -12 0.3 2550 ~ CQ LU5CAT GF05 SA 230330 -6 0.4 1791 ~ WA8QNN KC5TT -02 230330 -10 0.4 360 ~ YS1GMV KE0ELU -19 230330 -1 1.3 734 ~ CQ AF5DE EM25 CQ Zone 4 230330 -6 0.8 2324 ~ BU2BV KJ7OTZ CN87 230330 -8 0.3 833 ~ W7SWB WD9IQN -16 230330 -5 0.1 1642 ~ NN2T WA5VXI EM25 230330 -8 0.3 778 ~ CQ KC9VW EL29 CQ Zone 4 230330 -19 0.3 2086 ~ CQ KD9KCK EN61 CQ Zone 4 230330 -10 0.4 2332 ~ KJ4SRY VA6KL -06 230330 -6 0.4 1822 ~ KE3VV W6ASO R+01 230330 -15 0.4 1313 ~ JA0ARF KR7X R-14 230330 -9 0.5 1639 ~ NN2T AC0FS EN34 230330 -18 0.3 983 ~ BH4TVU K9RR R-16 230330 -18 0.5 1976 ~ VE2JI LW8DHX -13 230330 -18 0.5 2016 ~ KI5KSE KB4DPH EL88 230330 -24 0.1 1084 ~ W5FHW WB9MSM EN53 230330 -23 0.7 2000 ~ CQ KF0AQK EN21 CQ Zone 4 230330 -14 0.4 1648 ~ VA3TPS KD9MKR RR73 230330 -13 0.1 1608 ~ CQ KF9KV EN52 CQ Zone 4 ------------------------------------ 20m 230345 -17 -0.1 1492 ~ VY1MB KN4GGH EM91 230345 -3 -1.6 1415 ~ CQ AI4QT EM74 U.S.A. 230345 -10 0.5 2275 ~ CQ W7OK CN86 CQ Zone 3 230345 -7 0.3 888 ~ KB7THX AI4VV RRR 230345 8 0.4 1638 ~ AC0FS NN2T +01 230345 0 0.6 1208 ~ WB9MSM W5FHW EM02 230345 -3 0.3 1942 ~ KB4DPH KI5KSE +06 230345 -13 0.3 2051 ~ W5CRN KB7SAT 73 230345 9 0.3 1695 ~ CQ W0WND DM97 CQ Zone 4 230345 17 0.3 530 ~ AB1WG N5LDO 73 230345 -13 0.3 2206 ~ JE3BMU N7CTB CN85 230345 6 0.4 424 ~ CO8AFG W8KEN -14 230345 -14 0.4 1890 ~ VA6KL KJ4SRY R-17 230345 -6 0.3 2795 ~ AG5VE N2MSF RR73 230345 -15 0.4 1553 ~ XP3A N4AN R-19 230345 -14 0.5 744 ~ EA5IYK VE6ATS R-11 230345 -2 0.3 575 ~ KN6ITP K4BWM FM14 230345 -4 0.4 1667 ~ J88DCP/R WB4KTF EM10 230345 -12 0.2 852 ~ KN6ITP KB4RRN EM90 230345 -17 0.3 1958 ~ KR7X JA0ARF RR73 230345 -16 0.3 900 ~ CQ KK4OMJ EM78 U.S.A. 230345 -24 0.3 1777 ~ KC4VKG N8FRI EN81 230345 -22 0.3 2054 ~ CQ N2OO FM29 U.S.A. 230345 -10 0.4 1072 ~ KD9KCK N3CKI FM03 230345 -14 0.4 1717 ~ WA2EPI <...> -08 230345 -1 0.4 628 ~ JE3BMU WA7VIZ CN92 230345 -9 0.3 1624 ~ KC9VW W0BLE EN31 230345 -10 0.4 1605 ~ KN6ITP KB8SRX 73 230345 -24 -0.1 1365 ~ CQ K3ADU FN10 a1 U.S.A. 230345 -20 0.6 1649 ~ KD9MKR VA3TPS 73 ------------------------------------ 20m 230400 -18 1.0 1488 ~ HC5EG PY7YZ 73 230400 8 0.3 1331 ~ N2MSF AG5VE 73 230400 -5 0.3 900 ~ CQ KQ1S EM94 U.S.A. 230400 -1 0.1 1966 ~ N5AQM WA5VXI EM25 230400 4 0.4 445 ~ VE3XTF KF5TVG -16 230400 7 0.3 2144 ~ JA9IFF W3MMM RR73 230400 0 0.3 778 ~ CQ KC9VW EL29 CQ Zone 4 230400 1 0.3 2199 ~ PP5DE K0HMZ 73 230400 -8 0.4 360 ~ YS1GMV KE0ELU -19 230400 -12 0.3 1051 ~ N2OO KE5GXX EL17 230400 -4 0.5 1639 ~ NN2T AC0FS R+07 230400 -8 0.4 1102 ~ XL3T K4TT FN44 230400 -9 0.3 2548 ~ CQ LU5CAT GF05 SA 230400 -5 0.8 2324 ~ BU2BV KJ7OTZ CN87 230400 -15 0.3 983 ~ BH4TVU K9RR R-16 230400 5 0.4 1847 ~ YS1GMV VE7XT R-18 230400 6 0.4 1823 ~ KE3VV W6ASO R+01 230400 -13 0.3 833 ~ W7SWB WD9IQN -16 230400 -12 0.5 2015 ~ KI5KSE KB4DPH R+01 230400 -7 0.3 1313 ~ JA0ARF KR7X 73 230400 2 0.1 1791 ~ WA8QNN KC5TT -14 230400 -9 0.4 2333 ~ KJ4SRY VA6KL RR73 230400 -19 0.3 2088 ~ CQ KD9KCK EN61 CQ Zone 4 230400 -15 0.7 2000 ~ CQ KF0AQK EN21 CQ Zone 4 230400 -8 0.3 1794 ~ LU9HCO W3DJS EM83 230400 -16 0.5 1977 ~ VE2JI LW8DHX -13 230400 -15 0.2 1608 ~ CQ KF9KV EN52 CQ Zone 4 230400 -12 0.4 1649 ~ VA3TPS KD9MKR RR73 73
Bill
G4WJS.
|
|
|
locked
Re: new computer, CAT doesn't work right
i HAVE THREE HERNIATED DISCS IN MY BACH AND IT'S TIME FOR THE OXYCODONE AND TRACTION, i'LL TRY TOMORROW, WHO KNOWS, IT MIGHT JUST WORK. THANK YOU FOR HELPING ME.
73 de NØIGU
Jon
On Monday, November 2, 2020, 08:50:03 PM CST, Jon Ermels via groups.io <n0igu@...> wrote:
i EVEN TRIED A NEW CABLE, NO JOY. NOW IT SAYS " ERROR IN SOUND INPUT " WHEN I START THE PROGRAM. I REBOOTED THE COPMPTER ALSO
73 de NØIGU
Jon
On Monday, November 2, 2020, 08:34:43 PM CST, Bill Somerville <g4wjs@...> wrote:
Jon,
when you have the virtual COM port
drivers installed and the rig plugged in you will have two COM
ports visible in the Windows Device Manager, the second port
(Enhanced) is the one that is used for CAT control, that is the
one that needs to be selected in
"Settings->Radio->Cat->Serial Port".
If you have Hardware handshaking
enabled then you must also have the rig menu item 33 (CAT RTS) set
to ENABLE.
73
Bill
G4WJS.
On 03/11/2020 02:25, Jon Ermels via
groups.io wrote:
SRI ABOUT MY TYPING, TRYING
TO HURRY, ANSWERS BELOW
73 de NØIGU Jon
On Monday, November 2, 2020, 07:18:45 PM CST, Bill
Somerville <g4wjs@...> wrote:
Hi
Jon,
have
you installed the virtual COM port drivers for the rig
on your PC? YES, COPIED FROM THE YAESU WEB SITE
Do you have the right
COM port selected for CAT (you need the extended COM
port)? YES, COMPORT, RADIO AND WSJTX ARE SAME
As you have Hardware
handshaking enabled, do you have RTS enabled in the
rig's menu? NOTHING IS BUT WHAT PORT?
73
Bill
G4WJS.
On
03/11/2020 01:12, Jon Ermels via groups.io wrote:
Hi Bill, FT-991A, USB on radio to
USB on computer, same as old computer. what
baffles me is it turns on the radio and
decodes and then says the CAT doesn't work.
Com poer at the
codex port says,
Baud 38400 same as radio,
8 data bits,
1 stop bit,
HDW hand shake
73
de NØIGU Jon
On Monday, November 2, 2020, 07:01:18 PM
CST, Bill Somerville <g4wjs@...>
wrote:
On 03/11/2020 00:45, Jon Ermels
via groups.io wrote:
> old computer worked on same radio, new
computer, used it for WSJTX
> before with different radio, CODEX ok,
WXJTW version 2.2.2, I get rig
> failure message, hamlib error IO error
while testing VFO, cat test in
> settings stays red, it decodes whatever
freq the radio is set to but
> says it's on 160M, stills start the
radio when WSJTX starts up.
Hi Jon,
which radio? How is it connected to your PC
for CAT control? What
settings do you have in "Settings->Radio"
com port 6, as the Port says, ?
73
Bill
G4WJS.
|
|
|
locked
Re: new computer, CAT doesn't work right
i EVEN TRIED A NEW CABLE, NO JOY. NOW IT SAYS " ERROR IN SOUND INPUT " WHEN I START THE PROGRAM. I REBOOTED THE COPMPTER ALSO
73 de NØIGU
Jon
On Monday, November 2, 2020, 08:34:43 PM CST, Bill Somerville <g4wjs@...> wrote:
Jon,
when you have the virtual COM port
drivers installed and the rig plugged in you will have two COM
ports visible in the Windows Device Manager, the second port
(Enhanced) is the one that is used for CAT control, that is the
one that needs to be selected in
"Settings->Radio->Cat->Serial Port".
If you have Hardware handshaking
enabled then you must also have the rig menu item 33 (CAT RTS) set
to ENABLE.
73
Bill
G4WJS.
On 03/11/2020 02:25, Jon Ermels via
groups.io wrote:
SRI ABOUT MY TYPING, TRYING
TO HURRY, ANSWERS BELOW
73 de NØIGU Jon
On Monday, November 2, 2020, 07:18:45 PM CST, Bill
Somerville <g4wjs@...> wrote:
Hi
Jon,
have
you installed the virtual COM port drivers for the rig
on your PC? YES, COPIED FROM THE YAESU WEB SITE
Do you have the right
COM port selected for CAT (you need the extended COM
port)? YES, COMPORT, RADIO AND WSJTX ARE SAME
As you have Hardware
handshaking enabled, do you have RTS enabled in the
rig's menu? NOTHING IS BUT WHAT PORT?
73
Bill
G4WJS.
On
03/11/2020 01:12, Jon Ermels via groups.io wrote:
Hi Bill, FT-991A, USB on radio to
USB on computer, same as old computer. what
baffles me is it turns on the radio and
decodes and then says the CAT doesn't work.
Com poer at the
codex port says,
Baud 38400 same as radio,
8 data bits,
1 stop bit,
HDW hand shake
73
de NØIGU Jon
On Monday, November 2, 2020, 07:01:18 PM
CST, Bill Somerville <g4wjs@...>
wrote:
On 03/11/2020 00:45, Jon Ermels
via groups.io wrote:
> old computer worked on same radio, new
computer, used it for WSJTX
> before with different radio, CODEX ok,
WXJTW version 2.2.2, I get rig
> failure message, hamlib error IO error
while testing VFO, cat test in
> settings stays red, it decodes whatever
freq the radio is set to but
> says it's on 160M, stills start the
radio when WSJTX starts up.
Hi Jon,
which radio? How is it connected to your PC
for CAT control? What
settings do you have in "Settings->Radio"
com port 6, as the Port says, ?
73
Bill
G4WJS.
|
|
|
locked
Re: new computer, CAT doesn't work right
toggle quoted messageShow quoted text
On Monday, November 2, 2020, 08:34:43 PM CST, Bill Somerville <g4wjs@...> wrote:
Jon,
when you have the virtual COM port
drivers installed and the rig plugged in you will have two COM
ports visible in the Windows Device Manager, the second port
(Enhanced) is the one that is used for CAT control, that is the
one that needs to be selected in "Settings->Radio->Cat->Serial Port". I HAVE THE ENHANCED PORT SELECTED. IN WSJTX SETTINGS> RADIO>CAT> SERIAL PORT IDS ALREADY SET THAT WAY
If you have Hardware handshaking
enabled then you must also have the rig menu item 33 (CAT RTS) set
to ENABLE. RIG ITEM 33 IS ALREADDY SET TO ENABLE
73
Bill
G4WJS.
On 03/11/2020 02:25, Jon Ermels via
groups.io wrote:
SRI ABOUT MY TYPING, TRYING
TO HURRY, ANSWERS BELOW
73 de NØIGU Jon
On Monday, November 2, 2020, 07:18:45 PM CST, Bill
Somerville <g4wjs@...> wrote:
Hi
Jon,
have
you installed the virtual COM port drivers for the rig
on your PC? YES, COPIED FROM THE YAESU WEB SITE
Do you have the right
COM port selected for CAT (you need the extended COM
port)? YES, COMPORT, RADIO AND WSJTX ARE SAME
As you have Hardware
handshaking enabled, do you have RTS enabled in the
rig's menu? NOTHING IS BUT WHAT PORT?
73
Bill
G4WJS.
On
03/11/2020 01:12, Jon Ermels via groups.io wrote:
Hi Bill, FT-991A, USB on radio to
USB on computer, same as old computer. what
baffles me is it turns on the radio and
decodes and then says the CAT doesn't work.
Com poer at the
codex port says,
Baud 38400 same as radio,
8 data bits,
1 stop bit,
HDW hand shake
73
de NØIGU Jon
On Monday, November 2, 2020, 07:01:18 PM
CST, Bill Somerville <g4wjs@...>
wrote:
On 03/11/2020 00:45, Jon Ermels
via groups.io wrote:
> old computer worked on same radio, new
computer, used it for WSJTX
> before with different radio, CODEX ok,
WXJTW version 2.2.2, I get rig
> failure message, hamlib error IO error
while testing VFO, cat test in
> settings stays red, it decodes whatever
freq the radio is set to but
> says it's on 160M, stills start the
radio when WSJTX starts up.
Hi Jon,
which radio? How is it connected to your PC
for CAT control? What
settings do you have in "Settings->Radio"
com port 6, as the Port says, ?
73
Bill
G4WJS.
|
|
|
locked
Re: new computer, CAT doesn't work right
Bill Somerville
Jon,
when you have the virtual COM port
drivers installed and the rig plugged in you will have two COM
ports visible in the Windows Device Manager, the second port
(Enhanced) is the one that is used for CAT control, that is the
one that needs to be selected in
"Settings->Radio->Cat->Serial Port".
If you have Hardware handshaking
enabled then you must also have the rig menu item 33 (CAT RTS) set
to ENABLE.
73
Bill
G4WJS.
toggle quoted messageShow quoted text
On 03/11/2020 02:25, Jon Ermels via
groups.io wrote:
SRI ABOUT MY TYPING, TRYING
TO HURRY, ANSWERS BELOW
73 de NØIGU Jon
On Monday, November 2, 2020, 07:18:45 PM CST, Bill
Somerville <g4wjs@...> wrote:
Hi
Jon,
have
you installed the virtual COM port drivers for the rig
on your PC? YES, COPIED FROM THE YAESU WEB SITE
Do you have the right
COM port selected for CAT (you need the extended COM
port)? YES, COMPORT, RADIO AND WSJTX ARE SAME
As you have Hardware
handshaking enabled, do you have RTS enabled in the
rig's menu? NOTHING IS BUT WHAT PORT?
73
Bill
G4WJS.
On
03/11/2020 01:12, Jon Ermels via groups.io wrote:
Hi Bill, FT-991A, USB on radio to
USB on computer, same as old computer. what
baffles me is it turns on the radio and
decodes and then says the CAT doesn't work.
Com poer at the
codex port says,
Baud 38400 same as radio,
8 data bits,
1 stop bit,
HDW hand shake
73
de NØIGU Jon
On Monday, November 2, 2020, 07:01:18 PM
CST, Bill Somerville <g4wjs@...>
wrote:
On 03/11/2020 00:45, Jon Ermels
via groups.io wrote:
> old computer worked on same radio, new
computer, used it for WSJTX
> before with different radio, CODEX ok,
WXJTW version 2.2.2, I get rig
> failure message, hamlib error IO error
while testing VFO, cat test in
> settings stays red, it decodes whatever
freq the radio is set to but
> says it's on 160M, stills start the
radio when WSJTX starts up.
Hi Jon,
which radio? How is it connected to your PC
for CAT control? What
settings do you have in "Settings->Radio"
com port 6, as the Port says, ?
73
Bill
G4WJS.
|
|
|
