Date   

locked Re: #FT8 and FST4 CRC differences #FT8

steve_k9an
 

Andy, 
The FT4/FT8 QEX paper says "The CRC is calculated on the source-encoded message, zero-extended from 77 to 82 bits.", so there's no mystery there.

Also, for your purposes there is no reason to calculate the CRC first and then encode. You can cascade the CRC generator matrix with the LDPC code generator matrix once and then use a single vector-matrix multiply to calculate all of the CRC+parity bits. This approach eliminates the need for a separate CRC calculation and would save you a little bit of memory as well. For example, in the case of FST4, instead of storing a 139x101 binary matrix like you do now, you would store the smaller 163x77 binary matrix. The latter is about 12% smaller than the former.

If you are interested in implementing this more efficient scheme,  I'll be happy to create and send to you the cascaded generator matrices for the FT8/FT4 and FST4/W codes.
73 Steve k9an


locked Re: Inscrutable WSJT-X problem! #Windows10 #Icom

Joseph Willis <ve2cy@...>
 

Yes, the NTP works well, but I think I gave the idea it fixed it ... it is not a timing problem, unfortunately.

Joe




On Wednesday, April 21, 2021, 01:38:00 p.m. EDT, Joel <styx@...> wrote:


Joe

I have been using Dimension 4 for years.... install and forget. Hope it works for you.

Joel
AC8WS

On Apr 21, 2021, at 1:03 PM, Joseph Willis via groups.io <ve2cy@...> wrote:


Thanks Joel ... at first I hadn't thought of that, but I was always manually resetting with windows.  Just yesterday I found out about NTP, so I won't have to keep doing that anymore.

Thanks for the suggestion,

Joe




On Wednesday, April 21, 2021, 11:16:15 a.m. EDT, Joel <styx@...> wrote:


Check your time sync on the computer that is not working.... that might be the issue.

Joel
AC8WS

On Apr 21, 2021, at 10:55 AM, Joseph Willis via groups.io <ve2cy@...> wrote:


I seem to have an unsolvable WSJT-X transmission problem, that came about while operating one day (I had been using it for several months).  I don't remember clearly how it occurred, because I was concentrating on making contacts, but it seemed the keyboard or operating system froze or bugged, and I could no longer use the FT8 session I was running at that time.

Even after a reboot, I could not make a contact, although everything seemed to work, and WSJT-X opened as normal.

I re-installed the WSJT-X program, reloaded the CP210 USB/UART codex s/w, and even ran a utility to clean up the registry.  No luck.  The program loads, goes into transmit mode, the monitor shows a modulated signal going out, but no one replies, and PSK Reporter acts as if it doesn't hear me.

As an experiment, I had another laptop, and installed the program on it.  It worked first time, every time, like the Eveready Bunny!  So, for the past few months, I have been scratching my head comparing everything I could between the two computers.

They both have Win10, CP210, WSJT-X 2.12, and use the same IC-7300 rig.  The Icom display looks like the same modulated FT8 signal when I transmit from either computer.

What else is there left to compare ?  I have checked, rechecked and re-re-checked all settings again and again.

Is there some other wsjt-x supporting file in Win10 that might have been corrupted on the one pc?  I hesitate to do a complete windows re-install and then have to re-install the dozens of programs I already have on the computer, but I am running out of ideas.

Thanks for any assistance you can give me.

VE2CY















locked #FT8 and FST4 CRC differences #FT8

Andy Talbot
 

Having looked at the encoding process for FST4, I started looking at FT8 which is essentially the underlying same process.   However, I came a cropper with the CRC generation in FT8

FST4 uses a 24 bit CRC, generated using Fortran90 code in an easy to follow, text book routine.   FT8 uses a 14 bit CRC and although there is Fortran90 code listed there, it is not called.   Instead the CRC is generated by calling out to a C-library (BOOST set) routine.
I tried rewriting the text-book routine to try to use it instead in my own code, but it would never give the same answer as the CRC delivered by the FT8CODE utility.

I'm totally unfamiliar with the C++ language, especially its templates and calls, so it was futile trying to wade though the BOOST library, so asked on the RSGB Tech Group if anyone could help solve the problem.  G3PLX, G4DBN and M0XGT got their heads together and worked out what was wrong.   Quite simple; when calling the C routines the 91 bit message consisting of 77 source bits plus augmentation zeros for the CRC, are padded out to byte width with an extra five '0's on top.  When this extended 96 bit message is passed though the textbook algorithm, it gives the right answer.

I can only assume the C library routine was selected for use as it's a lot faster; an essential requirement, presumably, for the quintillions of calls to it needed for LDPC decoding.  FST4 is a slower more leisurely single user mode, so no massive speed requirement there. 


locked Re: Inscrutable WSJT-X problem! #Windows10 #Icom

Joel
 

Joe

I have been using Dimension 4 for years.... install and forget. Hope it works for you.

Joel
AC8WS

On Apr 21, 2021, at 1:03 PM, Joseph Willis via groups.io <ve2cy@...> wrote:


Thanks Joel ... at first I hadn't thought of that, but I was always manually resetting with windows.  Just yesterday I found out about NTP, so I won't have to keep doing that anymore.

Thanks for the suggestion,

Joe




On Wednesday, April 21, 2021, 11:16:15 a.m. EDT, Joel <styx@...> wrote:


Check your time sync on the computer that is not working.... that might be the issue.

Joel
AC8WS

On Apr 21, 2021, at 10:55 AM, Joseph Willis via groups.io <ve2cy@...> wrote:


I seem to have an unsolvable WSJT-X transmission problem, that came about while operating one day (I had been using it for several months).  I don't remember clearly how it occurred, because I was concentrating on making contacts, but it seemed the keyboard or operating system froze or bugged, and I could no longer use the FT8 session I was running at that time.

Even after a reboot, I could not make a contact, although everything seemed to work, and WSJT-X opened as normal.

I re-installed the WSJT-X program, reloaded the CP210 USB/UART codex s/w, and even ran a utility to clean up the registry.  No luck.  The program loads, goes into transmit mode, the monitor shows a modulated signal going out, but no one replies, and PSK Reporter acts as if it doesn't hear me.

As an experiment, I had another laptop, and installed the program on it.  It worked first time, every time, like the Eveready Bunny!  So, for the past few months, I have been scratching my head comparing everything I could between the two computers.

They both have Win10, CP210, WSJT-X 2.12, and use the same IC-7300 rig.  The Icom display looks like the same modulated FT8 signal when I transmit from either computer.

What else is there left to compare ?  I have checked, rechecked and re-re-checked all settings again and again.

Is there some other wsjt-x supporting file in Win10 that might have been corrupted on the one pc?  I hesitate to do a complete windows re-install and then have to re-install the dozens of programs I already have on the computer, but I am running out of ideas.

Thanks for any assistance you can give me.

VE2CY












locked Re: Inscrutable WSJT-X problem! #Windows10 #Icom

Joseph Willis <ve2cy@...>
 

Which just made me think - does the sensitive timing also matter to PSK Reporter too ?


VE2CY



On Wednesday, April 21, 2021, 11:28:48 a.m. EDT, Joseph Willis <ve2cy@...> wrote:


Thanks Joel ... at first I hadn't thought of that, but I was always manually resetting with windows.  Just yesterday I found out about NTP, so I won't have to keep doing that anymore.

Thanks for the suggestion,

Joe




On Wednesday, April 21, 2021, 11:16:15 a.m. EDT, Joel <styx@...> wrote:


Check your time sync on the computer that is not working.... that might be the issue.

Joel
AC8WS

On Apr 21, 2021, at 10:55 AM, Joseph Willis via groups.io <ve2cy@...> wrote:


I seem to have an unsolvable WSJT-X transmission problem, that came about while operating one day (I had been using it for several months).  I don't remember clearly how it occurred, because I was concentrating on making contacts, but it seemed the keyboard or operating system froze or bugged, and I could no longer use the FT8 session I was running at that time.

Even after a reboot, I could not make a contact, although everything seemed to work, and WSJT-X opened as normal.

I re-installed the WSJT-X program, reloaded the CP210 USB/UART codex s/w, and even ran a utility to clean up the registry.  No luck.  The program loads, goes into transmit mode, the monitor shows a modulated signal going out, but no one replies, and PSK Reporter acts as if it doesn't hear me.

As an experiment, I had another laptop, and installed the program on it.  It worked first time, every time, like the Eveready Bunny!  So, for the past few months, I have been scratching my head comparing everything I could between the two computers.

They both have Win10, CP210, WSJT-X 2.12, and use the same IC-7300 rig.  The Icom display looks like the same modulated FT8 signal when I transmit from either computer.

What else is there left to compare ?  I have checked, rechecked and re-re-checked all settings again and again.

Is there some other wsjt-x supporting file in Win10 that might have been corrupted on the one pc?  I hesitate to do a complete windows re-install and then have to re-install the dozens of programs I already have on the computer, but I am running out of ideas.

Thanks for any assistance you can give me.

VE2CY









locked Re: Inscrutable WSJT-X problem! #Windows10 #Icom

Joseph Willis <ve2cy@...>
 

Thanks Joel ... at first I hadn't thought of that, but I was always manually resetting with windows.  Just yesterday I found out about NTP, so I won't have to keep doing that anymore.

Thanks for the suggestion,

Joe




On Wednesday, April 21, 2021, 11:16:15 a.m. EDT, Joel <styx@...> wrote:


Check your time sync on the computer that is not working.... that might be the issue.

Joel
AC8WS

On Apr 21, 2021, at 10:55 AM, Joseph Willis via groups.io <ve2cy@...> wrote:


I seem to have an unsolvable WSJT-X transmission problem, that came about while operating one day (I had been using it for several months).  I don't remember clearly how it occurred, because I was concentrating on making contacts, but it seemed the keyboard or operating system froze or bugged, and I could no longer use the FT8 session I was running at that time.

Even after a reboot, I could not make a contact, although everything seemed to work, and WSJT-X opened as normal.

I re-installed the WSJT-X program, reloaded the CP210 USB/UART codex s/w, and even ran a utility to clean up the registry.  No luck.  The program loads, goes into transmit mode, the monitor shows a modulated signal going out, but no one replies, and PSK Reporter acts as if it doesn't hear me.

As an experiment, I had another laptop, and installed the program on it.  It worked first time, every time, like the Eveready Bunny!  So, for the past few months, I have been scratching my head comparing everything I could between the two computers.

They both have Win10, CP210, WSJT-X 2.12, and use the same IC-7300 rig.  The Icom display looks like the same modulated FT8 signal when I transmit from either computer.

What else is there left to compare ?  I have checked, rechecked and re-re-checked all settings again and again.

Is there some other wsjt-x supporting file in Win10 that might have been corrupted on the one pc?  I hesitate to do a complete windows re-install and then have to re-install the dozens of programs I already have on the computer, but I am running out of ideas.

Thanks for any assistance you can give me.

VE2CY









locked Re: Inscrutable WSJT-X problem! #Windows10 #Icom

Joseph Willis <ve2cy@...>
 

Hello Tom - that is an angle I had not thought of before.  But I had been using it 4 to 5 months until then, although I could have changed something to cause it to start, maybe.

It's the desk one, in a metal cabinet, but who knows.  I will think through that idea further, thanks.


Joe



On Wednesday, April 21, 2021, 11:14:33 a.m. EDT, Tom V. Segalstad <la4ln@...> wrote:


Hi Joseph,

Is your PC more vulnarable to RFI (Radio Frequency Interference) than your laptop? Could this be the reason for your problem?

Have you tried using RFI-protection ferrites on all ends of PC-connecting cables?

73 from Tom (LA4LN)


Sent from Outlook Mobile



Fra: main@WSJTX.groups.io <main@WSJTX.groups.io> på vegne av Joseph Willis via groups.io <ve2cy@...>
Sendt: onsdag 21. april 2021, 16:54
Til: WSJT-x Group
Emne: [WSJTX] Inscrutable WSJT-X problem! #stopped_working

I seem to have an unsolvable WSJT-X transmission problem, that came about while operating one day (I had been using it for several months).  I don't remember clearly how it occurred, because I was concentrating on making contacts, but it seemed the keyboard or operating system froze or bugged, and I could no longer use the FT8 session I was running at that time.

Even after a reboot, I could not make a contact, although everything seemed to work, and WSJT-X opened as normal.

I re-installed the WSJT-X program, reloaded the CP210 USB/UART codex s/w, and even ran a utility to clean up the registry.  No luck.  The program loads, goes into transmit mode, the monitor shows a modulated signal going out, but no one replies, and PSK Reporter acts as if it doesn't hear me.

As an experiment, I had another laptop, and installed the program on it.  It worked first time, every time, like the Eveready Bunny!  So, for the past few months, I have been scratching my head comparing everything I could between the two computers.

They both have Win10, CP210, WSJT-X 2.12, and use the same IC-7300 rig.  The Icom display looks like the same modulated FT8 signal when I transmit from either computer.

What else is there left to compare ?  I have checked, rechecked and re-re-checked all settings again and again.

Is there some other wsjt-x supporting file in Win10 that might have been corrupted on the one pc?  I hesitate to do a complete windows re-install and then have to re-install the dozens of programs I already have on the computer, but I am running out of ideas.

Thanks for any assistance you can give me.

VE2CY




--
Tom (LA4LN)




locked Re: Inscrutable WSJT-X problem! #Windows10 #Icom

Joseph Willis <ve2cy@...>
 

I was using Win10, and constantly correcting for the time drift.  Since yesterday, I found out about "NTP", and now it takes care of itself.  But thanks, the timing was one of the things I verified.


Joe



On Wednesday, April 21, 2021, 11:14:24 a.m. EDT, Bill Somerville <g4wjs@...> wrote:


On 21/04/2021 15:07, Joseph Willis via groups.io wrote:
I seem to have an unsolvable WSJT-X transmission problem, that came about while operating one day (I had been using it for several months).  I don't remember clearly how it occurred, because I was concentrating on making contacts, but it seemed the keyboard or operating system froze or bugged, and I could no longer use the FT8 session I was running at that time.

Even after a reboot, I could not make a contact, although everything seemed to work, and WSJT-X opened as normal.

I re-installed the WSJT-X program, reloaded the CP210 USB/UART codex s/w, and even ran a utility to clean up the registry.  No luck.  The program loads, goes into transmit mode, the monitor shows a modulated signal going out, but no one replies, and PSK Reporter acts as if it doesn't hear me.

As an experiment, I had another laptop, and installed the program on it.  It worked first time, every time, like the Eveready Bunny!  So, for the past few months, I have been scratching my head comparing everything I could between the two computers.

They both have Win10, CP210, WSJT-X 2.12, and use the same IC-7300 rig.  The Icom display looks like the same modulated FT8 signal when I transmit from either computer.

What else is there left to compare ?  I have checked, rechecked and re-re-checked all settings again and again.

Is there some other wsjt-x supporting file in Win10 that might have been corrupted on the one pc?  I hesitate to do a complete windows re-install and then have to re-install the dozens of programs I already have on the computer, but I am running out of ideas.

Thanks for any assistance you can give me.

VE2CY

Hi Joesph,

what are you using to synchronize your PC to UTC?

73
Bill
G4WJS.





locked Re: Inscrutable WSJT-X problem! #Windows10 #Icom

Fred Roberts
 

Hi Joe!
       Just shooting from the hip, have you asked any close by hams to listen to your signal and report what they hear? After the latest Windows update I had a short lived problem due to Windows trying to use speaker audio to feed the XMTR rather than the CODEC. Without a second rig to listen to that output, I would never have realized what I was up against. 
       Also, have you looked at your RF  output with a watt meter using both computers? 
       After all of the continuing problems reported by the group, I continue to use WSJT-x 2.2.2, rather than 2.3x or 2.4.
Just a couple of thoughts, hope they help.
Fred
WB4QOC


Sent from my phone.....Fred


On Wed, Apr 21, 2021, 10:54 AM Joseph Willis via groups.io <ve2cy=yahoo.com@groups.io> wrote:
I seem to have an unsolvable WSJT-X transmission problem, that came about while operating one day (I had been using it for several months).  I don't remember clearly how it occurred, because I was concentrating on making contacts, but it seemed the keyboard or operating system froze or bugged, and I could no longer use the FT8 session I was running at that time.

Even after a reboot, I could not make a contact, although everything seemed to work, and WSJT-X opened as normal.

I re-installed the WSJT-X program, reloaded the CP210 USB/UART codex s/w, and even ran a utility to clean up the registry.  No luck.  The program loads, goes into transmit mode, the monitor shows a modulated signal going out, but no one replies, and PSK Reporter acts as if it doesn't hear me.

As an experiment, I had another laptop, and installed the program on it.  It worked first time, every time, like the Eveready Bunny!  So, for the past few months, I have been scratching my head comparing everything I could between the two computers.

They both have Win10, CP210, WSJT-X 2.12, and use the same IC-7300 rig.  The Icom display looks like the same modulated FT8 signal when I transmit from either computer.

What else is there left to compare ?  I have checked, rechecked and re-re-checked all settings again and again.

Is there some other wsjt-x supporting file in Win10 that might have been corrupted on the one pc?  I hesitate to do a complete windows re-install and then have to re-install the dozens of programs I already have on the computer, but I am running out of ideas.

Thanks for any assistance you can give me.

VE2CY






locked Re: Can't move forward! #Cat_RigControl #NewUser #WSJTX_config

Tony Castelli <kj4joa@...>
 

No problem, Chuck.


On Wed, Apr 21, 2021, 08:14 Chuck - KY4CU <k4cay.chuck@...> wrote:
Sorry, I had the red ptt button backwards, in my head. I won't ever answer, again, without actually looking at the software on my computer.



locked Re: Inscrutable WSJT-X problem! #Windows10 #Icom

Joel
 

Check your time sync on the computer that is not working.... that might be the issue.

Joel
AC8WS

On Apr 21, 2021, at 10:55 AM, Joseph Willis via groups.io <ve2cy@...> wrote:


I seem to have an unsolvable WSJT-X transmission problem, that came about while operating one day (I had been using it for several months).  I don't remember clearly how it occurred, because I was concentrating on making contacts, but it seemed the keyboard or operating system froze or bugged, and I could no longer use the FT8 session I was running at that time.

Even after a reboot, I could not make a contact, although everything seemed to work, and WSJT-X opened as normal.

I re-installed the WSJT-X program, reloaded the CP210 USB/UART codex s/w, and even ran a utility to clean up the registry.  No luck.  The program loads, goes into transmit mode, the monitor shows a modulated signal going out, but no one replies, and PSK Reporter acts as if it doesn't hear me.

As an experiment, I had another laptop, and installed the program on it.  It worked first time, every time, like the Eveready Bunny!  So, for the past few months, I have been scratching my head comparing everything I could between the two computers.

They both have Win10, CP210, WSJT-X 2.12, and use the same IC-7300 rig.  The Icom display looks like the same modulated FT8 signal when I transmit from either computer.

What else is there left to compare ?  I have checked, rechecked and re-re-checked all settings again and again.

Is there some other wsjt-x supporting file in Win10 that might have been corrupted on the one pc?  I hesitate to do a complete windows re-install and then have to re-install the dozens of programs I already have on the computer, but I am running out of ideas.

Thanks for any assistance you can give me.

VE2CY






locked Re: Inscrutable WSJT-X problem! #Windows10 #Icom

Tom V. Segalstad
 

Hi Joseph,

Is your PC more vulnarable to RFI (Radio Frequency Interference) than your laptop? Could this be the reason for your problem?

Have you tried using RFI-protection ferrites on all ends of PC-connecting cables?

73 from Tom (LA4LN)


Sent from Outlook Mobile



Fra: main@WSJTX.groups.io <main@WSJTX.groups.io> på vegne av Joseph Willis via groups.io <ve2cy@...>
Sendt: onsdag 21. april 2021, 16:54
Til: WSJT-x Group
Emne: [WSJTX] Inscrutable WSJT-X problem! #stopped_working

I seem to have an unsolvable WSJT-X transmission problem, that came about while operating one day (I had been using it for several months).  I don't remember clearly how it occurred, because I was concentrating on making contacts, but it seemed the keyboard or operating system froze or bugged, and I could no longer use the FT8 session I was running at that time.

Even after a reboot, I could not make a contact, although everything seemed to work, and WSJT-X opened as normal.

I re-installed the WSJT-X program, reloaded the CP210 USB/UART codex s/w, and even ran a utility to clean up the registry.  No luck.  The program loads, goes into transmit mode, the monitor shows a modulated signal going out, but no one replies, and PSK Reporter acts as if it doesn't hear me.

As an experiment, I had another laptop, and installed the program on it.  It worked first time, every time, like the Eveready Bunny!  So, for the past few months, I have been scratching my head comparing everything I could between the two computers.

They both have Win10, CP210, WSJT-X 2.12, and use the same IC-7300 rig.  The Icom display looks like the same modulated FT8 signal when I transmit from either computer.

What else is there left to compare ?  I have checked, rechecked and re-re-checked all settings again and again.

Is there some other wsjt-x supporting file in Win10 that might have been corrupted on the one pc?  I hesitate to do a complete windows re-install and then have to re-install the dozens of programs I already have on the computer, but I am running out of ideas.

Thanks for any assistance you can give me.

VE2CY




--
Tom (LA4LN)


locked Re: Inscrutable WSJT-X problem! #Windows10 #Icom

Bill Somerville
 

On 21/04/2021 15:07, Joseph Willis via groups.io wrote:
I seem to have an unsolvable WSJT-X transmission problem, that came about while operating one day (I had been using it for several months).  I don't remember clearly how it occurred, because I was concentrating on making contacts, but it seemed the keyboard or operating system froze or bugged, and I could no longer use the FT8 session I was running at that time.

Even after a reboot, I could not make a contact, although everything seemed to work, and WSJT-X opened as normal.

I re-installed the WSJT-X program, reloaded the CP210 USB/UART codex s/w, and even ran a utility to clean up the registry.  No luck.  The program loads, goes into transmit mode, the monitor shows a modulated signal going out, but no one replies, and PSK Reporter acts as if it doesn't hear me.

As an experiment, I had another laptop, and installed the program on it.  It worked first time, every time, like the Eveready Bunny!  So, for the past few months, I have been scratching my head comparing everything I could between the two computers.

They both have Win10, CP210, WSJT-X 2.12, and use the same IC-7300 rig.  The Icom display looks like the same modulated FT8 signal when I transmit from either computer.

What else is there left to compare ?  I have checked, rechecked and re-re-checked all settings again and again.

Is there some other wsjt-x supporting file in Win10 that might have been corrupted on the one pc?  I hesitate to do a complete windows re-install and then have to re-install the dozens of programs I already have on the computer, but I am running out of ideas.

Thanks for any assistance you can give me.

VE2CY

Hi Joesph,

what are you using to synchronize your PC to UTC?

73
Bill
G4WJS.


locked Inscrutable WSJT-X problem! #Windows10 #Icom

Joseph Willis <ve2cy@...>
 

I seem to have an unsolvable WSJT-X transmission problem, that came about while operating one day (I had been using it for several months).  I don't remember clearly how it occurred, because I was concentrating on making contacts, but it seemed the keyboard or operating system froze or bugged, and I could no longer use the FT8 session I was running at that time.

Even after a reboot, I could not make a contact, although everything seemed to work, and WSJT-X opened as normal.

I re-installed the WSJT-X program, reloaded the CP210 USB/UART codex s/w, and even ran a utility to clean up the registry.  No luck.  The program loads, goes into transmit mode, the monitor shows a modulated signal going out, but no one replies, and PSK Reporter acts as if it doesn't hear me.

As an experiment, I had another laptop, and installed the program on it.  It worked first time, every time, like the Eveready Bunny!  So, for the past few months, I have been scratching my head comparing everything I could between the two computers.

They both have Win10, CP210, WSJT-X 2.12, and use the same IC-7300 rig.  The Icom display looks like the same modulated FT8 signal when I transmit from either computer.

What else is there left to compare ?  I have checked, rechecked and re-re-checked all settings again and again.

Is there some other wsjt-x supporting file in Win10 that might have been corrupted on the one pc?  I hesitate to do a complete windows re-install and then have to re-install the dozens of programs I already have on the computer, but I am running out of ideas.

Thanks for any assistance you can give me.

VE2CY



locked #WSPR - band hopping #WSPR

d_ziolkowski
 

Hello-

win10, updated.
using wsjtx v2.4.0-rc4 for wspr monitoring. appears band hopping not working?  the "day part" does not show in bottom row of display.

also when i look at the 'schedule' , top row, last column to right says "24'. If  I click it, selects all of column 1 (far left- time groupings) as well as the the '24' column. 

nothing in manual i could find.

any advice please?
Thanks 
Dan KC2STA


locked #bugreport (more a suggestion?): stop auto scroll when scroll bar is not at bottom #IssueReport

Victor Reijs
 

Hello all of you,

I am a new user of wsjt-x (first as an SWL [NL413] and in the near future as pe1atn). Last Saturday the PACCDigi contest was happening. It was my first contest. So used wsjt-x (v2.3.0). I all worked fine, and I am sure that for a transmitter operator the GUI looks great.
As an SWL there is one thing that could be very handy. Being able to stop the scrolling of the 'Band activity' area. So if the scroll bar is not touching the bottom then it would be nice if the monitored messages are not resetting the scroll.  As SWL one wants to look in the past and at this moment the area scrolls up when a new message is decoded. So relaxed looking for earlier messages is very cumbersome. Pressing 'Stop' stops the monitoring, which is not handy as I want monitoring to continue (only the scrolling to be easier controlled).

Could that be implemented?

Another option in the Band Activity area (and Rx Frequency' area) would be a 'Find' (that colors the existing and new-decoded matching string).

Anyway thanks for providing this great program and mode.

All the best and stay healthy,

Victor (NL413 and PE1ATN)


locked OpenAcc programmer? #WSPR

John
 

Are there any OpenACC programmers here to might take a look at the standalone program daemon WSPRD that does the WSPR decode.?
I am hoping that there may be an opportunity to move much of wsprd  to GPU for much faster processing.

73
John
TI5JWC


locked Re: Can't move forward! #Cat_RigControl #NewUser #WSJTX_config

Chuck - KY4CU
 

Sorry, I had the red ptt button backwards, in my head. I won't ever answer, again, without actually looking at the software on my computer.


locked Re: Can't move forward! #Cat_RigControl #NewUser #WSJTX_config

Chuck - KY4CU
 

Since you have split set to fake it, and the test ptt  button is still red, the mismatch is probably because you are have the radio keyed. Unkey the radio by clicking test ptt again, and your displayed frequency in wsjtx should match your radio. 


Also, if you want to change bands, use the dropdown above the signal strength meter to select an appropriate frequency for the mode you have selected. 


locked Re: Can't move forward! #Cat_RigControl #NewUser #WSJTX_config

Bill Somerville
 

On 21/04/2021 11:53, Tony Castelli wrote:


A. J. Castelli 
KJ4JOA
General Class Operator
AEMT

Thanks Greg, knowing that about the frequencies helps. I'll use what's program default. I have attached a screenshot so you guys can see if I am messed up in the setting up or not. The "Test CAT" is green and the "Test PTT" is red, showing that the program is happy happy with my config. I can't show a side-by-side of the radio and the PC, but I'll try to explain what is happening. In screenshot01, notice the frequency: 14.072.711. My radio is dialed in at 14.075! That frequency does change as I change frequency, but still stays mismatched. 
The band activity window is empty. I know there isn't anything on the waterfall in the pic, but even when there is, the window is still empty/blank.
I hope that you guys can help me get everything meshing properly. If you need more input, please, let me know.


Hi Tony,

if you are seeing a difference between the displayed frequency in WSJT-X and you rig then you have probably entered calibration parameters into the "Settings->Frequencies" panel. To revert to no frequency calibration correction enter 0 for both the slope and intercept parameters.

73
Bill
G4WJS.

15621 - 15640 of 39846