Date   

locked #FST4W FST4[W] Beacon Source #FST4W

Andy Talbot
 

The PIC/DDS beacon source is now running, and it's being tested  on air for the first time with FSTW-120, -300 and now -900 

There's just have one issue to sort out.   I generate the Gaussian glide by using just two adjacent symbols and adding their weighted components based on a lookup table, sampled at 64* the sample rate.
Doing it like that means each session starts half a symbol late.   For the faster modes this doesn't matter, it's less than a second on DT.  On FSTW-900 the resulting delay of half a symbol is 2.8 seconds - which the decoder seems able to cope with but on -1800 the delay, DT,  becomes 5.6 seconds which doesn't work.

I can sort this by doing the job properly, and adding weighted versions of three symbols, last, this and next.  A few more lines of code, but easy enough to do

and.. as I write ... just checked WSPRNET, and there's a decode of the first -900 signal off air.   It works !


locked Re: No Tx audio after inactivity. #AudioIssues

Pete Singleton
 

Hi Phil,
I understand the USB port may need 'power management'.  I'd already turned that off.  This is about the driver software that uses the port.  Why does that ALSO need power management?

73 PeteS

On Fri, 26 Mar 2021 at 13:18, Philip Rose via groups.io <gm3zza=btinternet.com@groups.io> wrote:

It’s not the software, it’s the USB hardware that consumes power, regardless of whether it is active. Current laptops try and remove every single “unnecessary” use of power.

 

73 Phil.

 

Sent from Mail for Windows 10

 

From: Pete Singleton
Sent: 25 March 2021 18:04
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] No Tx audio after inactivity. #AudioIssues #txaudio

 

Update: I discovered that the 'CP210x USB to UART Bridge' had 'Allow power management' turned on.  Unticked the box and Tx audio stays alive during inactivity.

I don't understand how a minor bit of software can drain power.

I'm still getting the 'no Tx audio after band change' problem - new in v2.3.0

I REALLY, REALLY hate Win10.

73 de M0PTB
PeteS

 


--
73 Phil GM3ZZA



locked WSPR receiving bandwidth adjustment? #WSPR

Bruce KX4AZ
 

Now and then I see a poor little WSPR signal coming in just outside of the 1400-1600 Hz standard bandwidth, so it won't be decoded as far as I understand.  Wondering if there is any kind of setting in WSJTx that would allow me to pad the upper/lower audio edges, say to add an extra 20 Hz on each end?

Of course I could simply shift the entire slot up/down by changing my receiver frequency, but then I would be chopping signals at one of the ends.


locked Re: 2.4 rc4 and FTDX101MP #Cat_RigControl

Buddy Morgan
 

Downloaded 2.4 rc4. It works fine with my IC 9700 and my IC 7100. Still can't get any version of 2.4 to work with my FTDX101MP. 2.2 worked fine with the FTDX101MP. I tried an early version of 2.3 and it did not work with the '101.
I get the following error message,from 2.4 rc4:

Hamlib error: Feature not implemented
newcat_set_freq: special_60m=0, 60m freq=0, is_ftdx3000=0
newcat.c(784):newcat_set_freq return(-4)
rig.c(1724):rig_set_freq return(-4) while setting frequency

Timestamp: 2021-03-26T16:37:57.789Z

I would really like to get it working with my FTDX101. I am using Windows 10, on a HP All-In-One. I have not changed any settings on either the radio or the WSJT software.
Any ideas?

Buddy WB4OMG


locked Re: Conflicts with KA6LMS Stations #FT8

Kermit Lehman
 

I'm apparently the only W1 person (actually signing up, at least) who's doing any digital KA6LMS/1 operating.  All FT4/8.  I enjoy it, so I'll keep at it.


The problem is one left for the log checkers at KA6LMS Central.


This weekend the SSB bands will be full of the WPX-SSB contingent.


73,

Ken, AB1J, KA6LMS/1


-----Original Message-----
From: John KC4LZN <kc4lzn@...>
To: ktfrog007@...
Cc: main@WSJTX.groups.io <main@wsjtx.groups.io>
Sent: Fri, Mar 26, 2021 3:50 pm
Subject: Re: [WSJTX] Conflicts with KA6LMS Stations #FT8

Thanks Ken.

I may have to stick to sideband and CW then.

73

John
KC4LZN

On Fri, Mar 26, 2021, 11:39 <ktfrog007@...> wrote:
There are problems with these KA6LMS stations using different portable indicators.  The WSJT-S program apparently only pay attention to the KA6LMS part of the call and therefore mixes up calls when several are operating on the same band at the same time.

Be especially careful when logging the QSO (on the 73 or RR73).  You may inadvertently log another station.  Yesterday I saw several stations I worked log me as <KA6LMS/5> when I was <KA6LMS/1>.  Both of us were on 20m FT8 at the time.

73,
Ken, AB1J






-----Original Message-----
From: John KC4LZN <kc4lzn@...>
To: main@WSJTX.groups.io
Sent: Fri, Mar 26, 2021 9:10 am
Subject: [WSJTX] Conflicts with KA6LMS Stations #FT8

I worked KA6LMS/2 this morning on 80. Then KA6LMS/VE7 came on. I tried calling them and the /2 kept answering. If I addressed the /VE7 in my calling, why would the /2 pick up? Is this a bug in the software when it comes to the stroke calls? Screenshot attached.

John
KC4LZN







locked Re: Two program releases: WSJT-X 2.3.1 (GA) and WSJT-X 2.4.0-rc4 #Q65

Hasan Schiers N0AN
 

Installed, running, watching new averaging behavior. Seems more sensitive, but may be an illusion. Needs many more runs to get a feel for it. 120E sync now proper (Red Line)

Tnx as always, will pound on it tomorrow morning. 
73, N0AN
Hasan


On Fri, Mar 26, 2021 at 10:34 AM Joe <joe@...> wrote:
We are pleased to announce two new releases of program WSJT-X: a General
Availability (GA) release of version 2.3.1, and release candidate RC4 of
version 2.4.0.  Please read this announcement and relevant sections of
the Release Notes carefully.


1. WSJT-X 2.3.1 is a bug-fix release.  It includes updates to the User
Guide covering new modes FST4 and FST4W, and repairs defects and
regressions discovered since the v2.3.0 release.  Further details of
changes since v2.3.0 can be found in the Release Notes:
https://physics.princeton.edu//pulsar/k1jt/Release_Notes.txt
Scroll down to the section titled "Release: WSJT-X 2.3.1" and dated
"Mar 26, 2021."

Links to WSJT-X 2.3.1 installation packages for Windows, Linux, and
Macintosh are available here:
http://physics.princeton.edu/pulsar/k1jt/wsjtx.html


2. Release candidate WSJT-X 2.4.0-rc4 includes the new digital mode Q65.
Q65 is designed for two-way QSOs over especially difficult propagation
paths including ionospheric scatter, troposcatter, rain scatter, TEP,
EME, and other types of fast-fading signals.  Details and
recommendations concerning the Q65 submodes are provided in the
"Quick-Start Guide to Q65", available here:
https://physics.princeton.edu/pulsar/k1jt/Q65_Quick_Start.pdf

The WSJT-X User Guide now includes details about Q65 and is available
here:
https://www.physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main-2.4.0-rc4.html

Changes since WSJT-X 2.4.0-rc3 are summarized at the top of Release
Notes: https://physics.princeton.edu//pulsar/k1jt/Release_Notes.txt

Links to WSJT-X 2.4.0-rc4 installation packages for Windows, Linux, and
Macintosh are available here:
http://physics.princeton.edu/pulsar/k1jt/wsjtx.html
Scroll down to find "Candidate release:  WSJT-X 2.4.0-rc4".

You can also download the packages from our SourceForge site:
https://sourceforge.net/projects/wsjt/files/
It may take a short time for the SourceForge site to be updated.


GENERAL ADVICE FOR UPGRADING:  If you are not currently interested in
Q65 you should update to WSJT-X 2.3.1.  If you wish to participate in
testing and reporting feedback on Q65, you should upgrade to WSJT-X
2.4.0-rc4. Please remember that by using a release candidate you are
joining a beta test group.  This brings a responsibility to report your
experiences on one of the relevant user forums.


WSJT-X is licensed under the terms of Version 3 of the GNU General
Public License (GPL).  Development of this software is a cooperative
project to which many amateur radio operators have contributed.  If you
use our code, please have the courtesy to let us know about it.  If you
find bugs or make improvements to the code, please report them to us in
a timely fashion.

The authors and Copyright holders of WSJT-X request that derivative
works do not publish programs based on features in WSJT-X before those
features are made available in a General Availability (GA) release of
WSJT-X.  We will cease making public Release Candidate (RC) pre-releases
for testing and user early access purposes if this request is ignored.

We hope you will enjoy using this candidate release of WSJT-X 2.4.0 and
exercising the new mode Q65.  Please report on your Q65 experiences,
successful and otherwise, on one of the WSJT forums.  Bugs should be
reported by following instructions found here in the User Guide:

https://www.physics.princeton.edu//pulsar/K1JT/wsjtx-doc/wsjtx-main-2.4.0-rc4.html#_bug_reports

   -- 73 from Joe, K1JT; Bill, G4WJS; Steve, K9AN; and Nico, IV3NWV




locked Re: Conflicts with KA6LMS Stations #FT8

Bill Somerville
 

Hi Paul,

that's great, please apologize for the issue, they should be able to work around it with a little care. Have a great w/e with the LMS op.

73
Bill
G4WJS.

On 26/03/2021 16:10, Paul Braun wrote:
Good morning.

I'm on the KA6LMS team. I just shared the comments with them. I'm not one who's using FT8, but hopefully the ones who are can sort it out on our end.

Thanks for the heads-up.

On 3/26/21 10:51 : , Bill Somerville wrote:
Hi John and Ken,

I can confirm there is a defect. At the K6LMS end they will see messages sending reports to their other operations, with the same base callsign, highlighted with a red background, it would seem they are double-clicking them and responding which is understandable. Hopefully they will realize the issue and take care to check the messages they double-click are really for them.

73
bill
G4WJS.

On 26/03/2021 15:39, Kermit Lehman via groups.io wrote:
There are problems with these KA6LMS stations using different portable indicators.  The WSJT-S program apparently only pay attention to the KA6LMS part of the call and therefore mixes up calls when several are operating on the same band at the same time.

Be especially careful when logging the QSO (on the 73 or RR73).  You may inadvertently log another station.  Yesterday I saw several stations I worked log me as <KA6LMS/5> when I was <KA6LMS/1>.  Both of us were on 20m FT8 at the time.

73,
Ken, AB1J






-----Original Message-----
From: John KC4LZN <kc4lzn@...>
To: main@WSJTX.groups.io
Sent: Fri, Mar 26, 2021 9:10 am
Subject: [WSJTX] Conflicts with KA6LMS Stations #FT8

I worked KA6LMS/2 this morning on 80. Then KA6LMS/VE7 came on. I tried calling them and the /2 kept answering. If I addressed the /VE7 in my calling, why would the /2 pick up? Is this a bug in the software when it comes to the stroke calls? Screenshot attached.

John
KC4LZN



locked Re: Conflicts with KA6LMS Stations #FT8

Paul Braun
 

Good morning.

I'm on the KA6LMS team. I just shared the comments with them. I'm not one who's using FT8, but hopefully the ones who are can sort it out on our end.

Thanks for the heads-up.

On 3/26/21 10:51 : , Bill Somerville wrote:
Hi John and Ken,

I can confirm there is a defect. At the K6LMS end they will see messages sending reports to their other operations, with the same base callsign, highlighted with a red background, it would seem they are double-clicking them and responding which is understandable. Hopefully they will realize the issue and take care to check the messages they double-click are really for them.

73
bill
G4WJS.

On 26/03/2021 15:39, Kermit Lehman via groups.io wrote:
There are problems with these KA6LMS stations using different portable indicators.  The WSJT-S program apparently only pay attention to the KA6LMS part of the call and therefore mixes up calls when several are operating on the same band at the same time.

Be especially careful when logging the QSO (on the 73 or RR73).  You may inadvertently log another station.  Yesterday I saw several stations I worked log me as <KA6LMS/5> when I was <KA6LMS/1>.  Both of us were on 20m FT8 at the time.

73,
Ken, AB1J






-----Original Message-----
From: John KC4LZN <kc4lzn@...>
To: main@WSJTX.groups.io
Sent: Fri, Mar 26, 2021 9:10 am
Subject: [WSJTX] Conflicts with KA6LMS Stations #FT8

I worked KA6LMS/2 this morning on 80. Then KA6LMS/VE7 came on. I tried calling them and the /2 kept answering. If I addressed the /VE7 in my calling, why would the /2 pick up? Is this a bug in the software when it comes to the stroke calls? Screenshot attached.

John
KC4LZN






-- 
Paul Braun WD9GCO
Amateur Radio Newsline Anchor
ARNewsline.org
Certified Music Junkie

"Music washes from the soul the dust of everyday life." -- Berthold Auerbach

"Never follow anyone. Be your own hero." -- Neil Peart


locked Re: Conflicts with KA6LMS Stations #FT8

Bill Somerville
 

Hi John,

yes that would certainly cause issues if one of the K6LMS stations is calling CQ on the same band at the same time as another is working stations.

73
Bill
G4WJS.

On 26/03/2021 16:02, John KC4LZN wrote:
Thanks Bill.

They may want to uncheck the Call 1st box. 

73

John
KC4LZN

On Fri, Mar 26, 2021, 11:51 Bill Somerville <g4wjs@...> wrote:
Hi John and Ken,

I can confirm there is a defect. At the K6LMS end they will see messages sending reports to their other operations, with the same base callsign, highlighted with a red background, it would seem they are double-clicking them and responding which is understandable. Hopefully they will realize the issue and take care to check the messages they double-click are really for them.

73
bill
G4WJS.

On 26/03/2021 15:39, Kermit Lehman via groups.io wrote:
There are problems with these KA6LMS stations using different portable indicators.  The WSJT-S program apparently only pay attention to the KA6LMS part of the call and therefore mixes up calls when several are operating on the same band at the same time.

Be especially careful when logging the QSO (on the 73 or RR73).  You may inadvertently log another station.  Yesterday I saw several stations I worked log me as <KA6LMS/5> when I was <KA6LMS/1>.  Both of us were on 20m FT8 at the time.

73,
Ken, AB1J






-----Original Message-----
From: John KC4LZN <kc4lzn@...>
To: main@WSJTX.groups.io
Sent: Fri, Mar 26, 2021 9:10 am
Subject: [WSJTX] Conflicts with KA6LMS Stations #FT8

I worked KA6LMS/2 this morning on 80. Then KA6LMS/VE7 came on. I tried calling them and the /2 kept answering. If I addressed the /VE7 in my calling, why would the /2 pick up? Is this a bug in the software when it comes to the stroke calls? Screenshot attached.

John
KC4LZN



locked Re: Conflicts with KA6LMS Stations #FT8

John KC4LZN
 

Thanks Bill.

They may want to uncheck the Call 1st box. 

73

John
KC4LZN


On Fri, Mar 26, 2021, 11:51 Bill Somerville <g4wjs@...> wrote:
Hi John and Ken,

I can confirm there is a defect. At the K6LMS end they will see messages sending reports to their other operations, with the same base callsign, highlighted with a red background, it would seem they are double-clicking them and responding which is understandable. Hopefully they will realize the issue and take care to check the messages they double-click are really for them.

73
bill
G4WJS.

On 26/03/2021 15:39, Kermit Lehman via groups.io wrote:
There are problems with these KA6LMS stations using different portable indicators.  The WSJT-S program apparently only pay attention to the KA6LMS part of the call and therefore mixes up calls when several are operating on the same band at the same time.

Be especially careful when logging the QSO (on the 73 or RR73).  You may inadvertently log another station.  Yesterday I saw several stations I worked log me as <KA6LMS/5> when I was <KA6LMS/1>.  Both of us were on 20m FT8 at the time.

73,
Ken, AB1J






-----Original Message-----
From: John KC4LZN <kc4lzn@...>
To: main@WSJTX.groups.io
Sent: Fri, Mar 26, 2021 9:10 am
Subject: [WSJTX] Conflicts with KA6LMS Stations #FT8

I worked KA6LMS/2 this morning on 80. Then KA6LMS/VE7 came on. I tried calling them and the /2 kept answering. If I addressed the /VE7 in my calling, why would the /2 pick up? Is this a bug in the software when it comes to the stroke calls? Screenshot attached.

John
KC4LZN



locked Re: Conflicts with KA6LMS Stations #FT8

Bill Somerville
 

Hi John and Ken,

I can confirm there is a defect. At the K6LMS end they will see messages sending reports to their other operations, with the same base callsign, highlighted with a red background, it would seem they are double-clicking them and responding which is understandable. Hopefully they will realize the issue and take care to check the messages they double-click are really for them.

73
bill
G4WJS.

On 26/03/2021 15:39, Kermit Lehman via groups.io wrote:
There are problems with these KA6LMS stations using different portable indicators.  The WSJT-S program apparently only pay attention to the KA6LMS part of the call and therefore mixes up calls when several are operating on the same band at the same time.

Be especially careful when logging the QSO (on the 73 or RR73).  You may inadvertently log another station.  Yesterday I saw several stations I worked log me as <KA6LMS/5> when I was <KA6LMS/1>.  Both of us were on 20m FT8 at the time.

73,
Ken, AB1J






-----Original Message-----
From: John KC4LZN <kc4lzn@...>
To: main@WSJTX.groups.io
Sent: Fri, Mar 26, 2021 9:10 am
Subject: [WSJTX] Conflicts with KA6LMS Stations #FT8

I worked KA6LMS/2 this morning on 80. Then KA6LMS/VE7 came on. I tried calling them and the /2 kept answering. If I addressed the /VE7 in my calling, why would the /2 pick up? Is this a bug in the software when it comes to the stroke calls? Screenshot attached.

John
KC4LZN



locked Re: Conflicts with KA6LMS Stations #FT8

John KC4LZN
 

Thanks Ken.

I may have to stick to sideband and CW then.

73

John
KC4LZN


On Fri, Mar 26, 2021, 11:39 <ktfrog007@...> wrote:
There are problems with these KA6LMS stations using different portable indicators.  The WSJT-S program apparently only pay attention to the KA6LMS part of the call and therefore mixes up calls when several are operating on the same band at the same time.

Be especially careful when logging the QSO (on the 73 or RR73).  You may inadvertently log another station.  Yesterday I saw several stations I worked log me as <KA6LMS/5> when I was <KA6LMS/1>.  Both of us were on 20m FT8 at the time.

73,
Ken, AB1J






-----Original Message-----
From: John KC4LZN <kc4lzn@...>
To: main@WSJTX.groups.io
Sent: Fri, Mar 26, 2021 9:10 am
Subject: [WSJTX] Conflicts with KA6LMS Stations #FT8

I worked KA6LMS/2 this morning on 80. Then KA6LMS/VE7 came on. I tried calling them and the /2 kept answering. If I addressed the /VE7 in my calling, why would the /2 pick up? Is this a bug in the software when it comes to the stroke calls? Screenshot attached.

John
KC4LZN




locked Re: Conflicts with KA6LMS Stations #FT8

Kermit Lehman
 

There are problems with these KA6LMS stations using different portable indicators.  The WSJT-S program apparently only pay attention to the KA6LMS part of the call and therefore mixes up calls when several are operating on the same band at the same time.

Be especially careful when logging the QSO (on the 73 or RR73).  You may inadvertently log another station.  Yesterday I saw several stations I worked log me as <KA6LMS/5> when I was <KA6LMS/1>.  Both of us were on 20m FT8 at the time.

73,
Ken, AB1J






-----Original Message-----
From: John KC4LZN <kc4lzn@...>
To: main@WSJTX.groups.io
Sent: Fri, Mar 26, 2021 9:10 am
Subject: [WSJTX] Conflicts with KA6LMS Stations #FT8

I worked KA6LMS/2 this morning on 80. Then KA6LMS/VE7 came on. I tried calling them and the /2 kept answering. If I addressed the /VE7 in my calling, why would the /2 pick up? Is this a bug in the software when it comes to the stroke calls? Screenshot attached.

John
KC4LZN




locked Two program releases: WSJT-X 2.3.1 (GA) and WSJT-X 2.4.0-rc4 #Q65

Joe
 

We are pleased to announce two new releases of program WSJT-X: a General Availability (GA) release of version 2.3.1, and release candidate RC4 of version 2.4.0. Please read this announcement and relevant sections of the Release Notes carefully.


1. WSJT-X 2.3.1 is a bug-fix release. It includes updates to the User Guide covering new modes FST4 and FST4W, and repairs defects and regressions discovered since the v2.3.0 release. Further details of changes since v2.3.0 can be found in the Release Notes:
https://physics.princeton.edu//pulsar/k1jt/Release_Notes.txt
Scroll down to the section titled "Release: WSJT-X 2.3.1" and dated
"Mar 26, 2021."

Links to WSJT-X 2.3.1 installation packages for Windows, Linux, and Macintosh are available here:
http://physics.princeton.edu/pulsar/k1jt/wsjtx.html


2. Release candidate WSJT-X 2.4.0-rc4 includes the new digital mode Q65.
Q65 is designed for two-way QSOs over especially difficult propagation paths including ionospheric scatter, troposcatter, rain scatter, TEP, EME, and other types of fast-fading signals. Details and recommendations concerning the Q65 submodes are provided in the "Quick-Start Guide to Q65", available here:
https://physics.princeton.edu/pulsar/k1jt/Q65_Quick_Start.pdf

The WSJT-X User Guide now includes details about Q65 and is available here: https://www.physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main-2.4.0-rc4.html

Changes since WSJT-X 2.4.0-rc3 are summarized at the top of Release Notes: https://physics.princeton.edu//pulsar/k1jt/Release_Notes.txt

Links to WSJT-X 2.4.0-rc4 installation packages for Windows, Linux, and Macintosh are available here:
http://physics.princeton.edu/pulsar/k1jt/wsjtx.html
Scroll down to find "Candidate release: WSJT-X 2.4.0-rc4".

You can also download the packages from our SourceForge site:
https://sourceforge.net/projects/wsjt/files/
It may take a short time for the SourceForge site to be updated.


GENERAL ADVICE FOR UPGRADING: If you are not currently interested in Q65 you should update to WSJT-X 2.3.1. If you wish to participate in testing and reporting feedback on Q65, you should upgrade to WSJT-X 2.4.0-rc4. Please remember that by using a release candidate you are joining a beta test group. This brings a responsibility to report your experiences on one of the relevant user forums.


WSJT-X is licensed under the terms of Version 3 of the GNU General Public License (GPL). Development of this software is a cooperative project to which many amateur radio operators have contributed. If you use our code, please have the courtesy to let us know about it. If you find bugs or make improvements to the code, please report them to us in a timely fashion.

The authors and Copyright holders of WSJT-X request that derivative works do not publish programs based on features in WSJT-X before those features are made available in a General Availability (GA) release of WSJT-X. We will cease making public Release Candidate (RC) pre-releases for testing and user early access purposes if this request is ignored.

We hope you will enjoy using this candidate release of WSJT-X 2.4.0 and exercising the new mode Q65. Please report on your Q65 experiences, successful and otherwise, on one of the WSJT forums. Bugs should be reported by following instructions found here in the User Guide:

https://www.physics.princeton.edu//pulsar/K1JT/wsjtx-doc/wsjtx-main-2.4.0-rc4.html#_bug_reports

-- 73 from Joe, K1JT; Bill, G4WJS; Steve, K9AN; and Nico, IV3NWV


locked Re: Easiest transceiver/computer combo to configure for FT8 #install

Tom Arny
 

Hi Joghn,


locked Re: No Tx audio after inactivity. #AudioIssues

 

It’s not the software, it’s the USB hardware that consumes power, regardless of whether it is active. Current laptops try and remove every single “unnecessary” use of power.

 

73 Phil.

 

Sent from Mail for Windows 10

 

From: Pete Singleton
Sent: 25 March 2021 18:04
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] No Tx audio after inactivity. #AudioIssues #txaudio

 

Update: I discovered that the 'CP210x USB to UART Bridge' had 'Allow power management' turned on.  Unticked the box and Tx audio stays alive during inactivity.

I don't understand how a minor bit of software can drain power.

I'm still getting the 'no Tx audio after band change' problem - new in v2.3.0

I REALLY, REALLY hate Win10.

73 de M0PTB
PeteS

 


--
73 Phil GM3ZZA


locked Conflicts with KA6LMS Stations #FT8

John KC4LZN
 
Edited

I worked KA6LMS/2 this morning on 80. Then KA6LMS/VE7 came on. I tried calling them and the /2 kept answering. If I addressed the /VE7 in my calling, why would the /2 pick up? Is this a bug in the software when it comes to the stroke calls? Screenshot attached.

John
KC4LZN


locked Re: VS: [WSJTX] Import ADI Log File #WSJTX_config

robert scott
 

Reino thank you so much. I discovered that my logging program Log4OM placed a header in the adi file when I created it. I edited that out and all my QSOs load properly. I never would have figured that out without your help.

TU again and best 73

Rob
WR3Y


locked Re: Not able to make contact #FT8

Chuck Adams
 

To:  csnyder1975

 

Microsoft just issued an online update that included the Silicon Labs CP210X USB to UART Bridge drivers that the Icom 7100 uses to communicate with computers.

 

Check Device Manager > Ports and Device Manager > Sound to make sure these drivers are loaded and working properly.

 

Also check Control Panel > Sound to make sure these drivers are working when you have your Icom radio powered up and connected to your computer.

 

Let us know what you find.

 

73,

 

Chuck Adams

KV4VT

 

 

 

 

 

From: main@WSJTX.groups.io <main@WSJTX.groups.io> On Behalf Of csnyder1975 via groups.io
Sent: 25 March, 2021 8:03 PM
To: main@WSJTX.groups.io
Subject: [WSJTX] Not able to make contact #FT8

 

Hello everyone. I have a icom 7100 set up running wsjt-x on windows 10 64 bit and everything was working great until last night. All of the sudden I started getting error message after error message. I did a default reset of WSJT-X and reset all the setting on both my radio and the software and now it looks like it is running and okay when I look at Grid Tracker but I have been sending out CQs and trying to make contacts for 8 hours now without a single reply. Any ideas? Sorry but I'm new to this. 


locked Re: Not able to make contact #FT8

Hank Pfizenmayer
 

If you have another receiver with WSJT set up see if you can decode yourself. Barring that see if you can get a local to take a listen.

I went thru several weeks  with a W10 64 Dell workstation   and WSJT/  Ft8 - It would  decode received signals but the transmitted signal was missing what I assume was  a sync pulse at start of each transmission. The tones themselves sounded just like the ones that were working -but I finally recorded the tx signals and the one that worked had a very low level pulse at start and the one that did not work did not . have the pulse.. I had two computers with W10 64bit -could just move the usb cable to the other Dell workstation computer  and it worked fine - I looked at audio drivers and setup could not find any differences . Did the usual sys restores to earlier points  SFC stuff etc etc . I finally gave up and did a completely clean reinstall of W10   and its worked. I still cannot figure how the devil  an OS could corrupt to not send that sync pulse and yet decode perfectly -. but its been months and still works fine.

I was fortunate in that I had WSJT on a W7 laptop and a K3 / Signalink so I could see if things were decoding and what the spectrum looked like on a panadaptor etc


Hank K7HP

13281 - 13300 of 36850