Date   

locked Re: LDPC #Modes Coding Process draft doc. #modes

Andy Talbot
 

Thanks for comments from a couple of people, that and a bit of extensive re-reading myself, several errors have been found and corrected.   The latest version,  with a  correction to the way the parity generation is described, has been done just now.   The document keeps the same file name, but anyone interested in this process is advised to download the latest version.   http://g4jnt.com/WSJT-X_LdpcModesCodingProcess_DRAFT.pdf

Andy  G4JNT


locked WSJT-X 2.5.3 GA Release for macOS #general

Joe
 

John Nelson, G4KLA, has kindly prepared a macOS installation package for WSJT-X 2.5.3. A download link has been posted on the WSJT-X web page:
https://physics.princeton.edu//pulsar/k1jt/wsjtx.html

We hope that installation packages for other OS varieties and the source-code tarball can be made available in the near future.

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


locked Re: #WSJTX_config Problems setting colours on previously worked stations #WSJTX_config

Reino Talarmo
 

Bob,

I am as confused as you are, but I may have an answer still. You have in Colors “CQ in message” box selected and background color b/g is set, I assume. In addition your logging program changes only the color and background of the call sign part of the line. WSJT-X changes whole line font color and background color. The external control seems to affect only to the Band Activity display not on the RX Frequency display. I have no idea what is possible both in WSJT-X and in your logging program in that respect.

You may change how WSJT-X selects font and background colors by right clicking on the CQ in message line in the Colors page and select feature you want to modify on displayed menu. You may need to experiment to find how each feature actually behaves, hi! At least I had.
That may help depending how your logging program does the modification of the call sign font and background colors.

73, Reino OH3mA

 

From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of Bob Blauvelt via groups.io
Sent: 12. joulukuutata 2021 23:46
To: main@wsjtx.groups.io; main@WSJTX.groups.io
Subject: Re: [WSJTX] #WSJTX_config Problems setting colours on previously worked stations

 

Reino,

 

Thanks for your quick reply. I do not use JTAlert. The General Display “Show DXCC, grid, and worked-before status tab is and has always been unchecked.

 

My confusing issue is that the other instance (Right side of the screen shot) does not exhibit this symptom.

 

73, 

 

Bob   AJ4LJ

 

On Sunday, December 12, 2021, 04:41:49 PM EST, Reino Talarmo <reino.talarmo@...> wrote:

 

 

Hi Bob,

The issue you are seeing is not a WSJT-X issue as such. The highlighting is generated by another program e.g. JTAlert. You have two options either you don’t use Colors at all in WSJT-X, I think just untick File | Settings | General Display “Show DXCC, grid, and worked-before status tab, or don’t feed that information back to WSJT-X from your logging program.

73, Reino OH3mA




locked Re: WSJT-x 2.5.0-rc6 in FST4W mode I can only select 2M band and above #WSPR #FST4W

Dave Garber
 

I am not an fst4 user, but maybe the fact that you say you are using 2.5.0 RC6, instead of a full GA version .   now on 2.5.3, i believe...


Dave Garber
VE3WEJ / VE3IE


On Sun, Dec 12, 2021 at 3:34 PM <stanford.jw@...> wrote:
Hi group,

I haven't been able to decodes FST4 or FST4W on 160 (or 80 or other HF).
I've tried 1.839000 and WSPR freqs.  My K3 and iMac/Monterey decode FST4 in the WSJTX sample .wav file.   Any suggestions please!

73,
John, NN0F
Iowa 



locked Re: WSJT-X 2.5.3 GA Release (Win64 only) #general

Michael Black
 

The Icom fix will be available tonight.


Will have 20211213 date on it.

Mike W9MDB


On Sunday, December 12, 2021, 11:59:20 AM CST, Michael Black via groups.io <mdblack98@...> wrote:


Turn on echo.

This is the setting you want to turn on for now.  It's a bug in hamlib which I'm fixing now.
Will announce when a new DLL is available with the fix.


CI-V USB Echo Back (Default: OFF)
Turns the Data Echo Back function ON or OFF, when
remotely controlling the IC-9700 through the [USB]
CI-V port.
This setting is valid only when the “CI-V USB Port” item is
set to “Unlink from [REMOTE].”





On Sunday, December 12, 2021, 11:53:34 AM CST, groups.io@... <groups.io@...> wrote:


Exactly the same here (on IC-9700 and IC-7300). Updated from 2.3 to 2.5.3 and I was getting hamlib errors, installed 2.5.2 "over" 2.5.3 and all appears to be ok again.

I may try Stewart's suggestion later and go to 2.5.3 again.

Thanks for the release guys - Terry







locked Re: #WSJTX_config Problems setting colours on previously worked stations #WSJTX_config

Bob Blauvelt
 

Reino,

Thanks for your quick reply. I do not use JTAlert. The General Display “Show DXCC, grid, and worked-before status tab is and has always been unchecked.

My confusing issue is that the other instance (Right side of the screen shot) does not exhibit this symptom.

73, 

Bob   AJ4LJ

On Sunday, December 12, 2021, 04:41:49 PM EST, Reino Talarmo <reino.talarmo@...> wrote:


Hi Bob,

The issue you are seeing is not a WSJT-X issue as such. The highlighting is generated by another program e.g. JTAlert. You have two options either you don’t use Colors at all in WSJT-X, I think just untick File | Settings | General Display “Show DXCC, grid, and worked-before status tab, or don’t feed that information back to WSJT-X from your logging program.

73, Reino OH3mA





locked Re: #WSJTX_config Problems setting colours on previously worked stations #WSJTX_config

Reino Talarmo
 

Hi Bob,

The issue you are seeing is not a WSJT-X issue as such. The highlighting is generated by another program e.g. JTAlert. You have two options either you don’t use Colors at all in WSJT-X, I think just untick File | Settings | General Display “Show DXCC, grid, and worked-before status tab, or don’t feed that information back to WSJT-X from your logging program.

73, Reino OH3mA


locked #WSJTX_config Problems setting colours on previously worked stations #WSJTX_config

Bob Blauvelt
 

Hello all,
 
I am having an issue with one instance of WSJT-x showing previously worked stations in Yellow on Red. The other instance does not exhibit this issue. Nothing I try will restore back to the normal Black on Green for CQs. See attached picture. I find the Yellow on Red very difficult to read. I don't need the previously worked status as my logging program takes care of that function.
 
Any guidance will be appreciated.
 
Bob   AJ4LJ
  • WSJT-x.jpg
    924.1kB
 


locked Re: WSJT-x 2.5.0-rc6 in FST4W mode I can only select 2M band and above #WSPR #FST4W

John & Win Stanford
 

Hi group,

I haven't been able to decodes FST4 or FST4W on 160 (or 80 or other HF).
I've tried 1.839000 and WSPR freqs.  My K3 and iMac/Monterey decode FST4 in the WSJTX sample .wav file.   Any suggestions please!

73,
John, NN0F
Iowa 


locked Re: WSJT-X 2.5.0 and MCHF: issue reading-back the VFO setting #Cat_RigControl #linux #Yaesu #IssueReport

jamesraykenney
 

Thank you, thank you, thank you!
This has been driving me crazy for days!
I FINALLY reverted back to 2.1.2 to get things working, but this is such a better solution!


locked Re: WSJT-X 2.5.3 GA Release (Win64 only) #general

Michael Black
 

Turn on echo.

This is the setting you want to turn on for now.  It's a bug in hamlib which I'm fixing now.
Will announce when a new DLL is available with the fix.


CI-V USB Echo Back (Default: OFF)
Turns the Data Echo Back function ON or OFF, when
remotely controlling the IC-9700 through the [USB]
CI-V port.
This setting is valid only when the “CI-V USB Port” item is
set to “Unlink from [REMOTE].”





On Sunday, December 12, 2021, 11:53:34 AM CST, groups.io@... <groups.io@...> wrote:


Exactly the same here (on IC-9700 and IC-7300). Updated from 2.3 to 2.5.3 and I was getting hamlib errors, installed 2.5.2 "over" 2.5.3 and all appears to be ok again.

I may try Stewart's suggestion later and go to 2.5.3 again.

Thanks for the release guys - Terry




locked Re: WSJT-X 2.5.3 GA Release (Win64 only) #general

groups.io@...
 

Exactly the same here (on IC-9700 and IC-7300). Updated from 2.3 to 2.5.3 and I was getting hamlib errors, installed 2.5.2 "over" 2.5.3 and all appears to be ok again.

I may try Stewart's suggestion later and go to 2.5.3 again.

Thanks for the release guys - Terry


locked Re: Issues with LOTW and Worked Station after upgrading to 2.5.2 #stopped_working

Dave Garber
 

thats is why I prefer to keep jtalert to tell me all the info.  if you installed wsjt in a different folder, or with a -rig    it may have opened a new appdata folder under that name.   jtalert checks my full logging program, and then colours as per what my log says, not what wsjt says, and it marks eqsl users, lotw users, and a few more items as needed

maybe you were using jtalert previously, and forgot to reinstall it?

Dave Garber
VE3WEJ / VE3IE


On Sun, Dec 12, 2021 at 2:45 AM N2BRG <n2brg@...> wrote:

Hello,
I upgraded to 2.5.2 and the coloring from my previous settings stopped for LOTW and Worked Station.
I had Worked Station with a black background with a white foreground (forgot how I did that) and LOTW with the usual red text indication.

I have reinstalled the 2.5.2 twice and got LOTW to show but still no Worked Station.  After I change bands LOTW stopped showing color again.  
Neither LOTW nor Worked Station is showing coloring now.  DXCC and other colors are working fine even after juggling the priority positions.
Also, I cannot fetch the LOTW even after installing all the needed items per many groups.  I just manually download it and place it in the Logs now.
Being that I am manually downloading it, how often does that have to be updated?  I am still not fully grasping that.
If this helps, I am on Windows 10 Pro 21H2 Build 19044.1387.
I am not sure if this is a Windows issue or not since I completely purged the program from the computer and reinstalled it again.

I see that I may be probably the only one with these issues of color indications after scanning through the various groups.
The LOTW Fetch seems to be an ongoing issue with many even after the SSL\TSL installs from the recommended website.

It is a total pain to have to jump out to the web browser to check if the station uses LOTW and also to my ADIF to see if the station was worked.
I am getting too old to remember who is who and when or if I worked the station.
Any help would be greatly appreciated.
de N2BRG





locked Re: fmt.all file never written #Calibration

Jerry
 

Thank you Gary, standard deviation was .38 Hz, pretty darned good.

Jerry


- "Defeat lasts one day, giving up lasts a lifetime."

On Dec 11, 2021, at 4:35 PM, Gary - AC6EG <AC6EG@...> wrote:

Hi Jerry
Sounds like you were almost there. After you change Mode to FreqCal, go to the Tools menu and click on Execute Frequency Calibration Cycle. You should see data appear on screen as the program cycles through all the FreqCal frequencies in your Working Frequencies Table. This allows you to verify that you can copy all those frequencies and gives you an opportunity to see if you need to go back and edit the Working Frequencies Table. If you like what you are seeing, click on STOP, clear the screen by clicking on Erase, then put a check mark in front of Measure. (That checkmark is probably what you failed to do.) Now when you click on Monitor, the program will cycle through all the active FreqCal frequencies and collect data. Let this run for several cycles, then click on STOP. At this point, you should find a new FMT.ALL file in the log directory. Open that file with a text editor and delete all lines of data that end with an asterisk. Delete any other lines that appear to be anomalous. Close this file after saving your changes and make sure the file name is still FMT.ALL. Now go back to the Tools menu and choose Solve for Calibration Parameters.
If the program produces usable Calibration Parameters, you will be given an opportunity to apply them. If not, you'll have to repeat the process until you succeed in acquiring valid Calibration Parameters.
Good Luck! 😊
73 de Gary - AC6EG


locked Re: LDPC #Modes Coding Process draft doc. #modes

Reino Talarmo
 
Edited


 

Hi!

Interesting opinion as I have had no problem with the country display in any version of wsjt-x. You must have some setting not properly set. Of course it is difficult to give an advice without knowing exactly all your relates settings and whether the wsjtx_log.adi file is in the proper directory. Clearly it is not a question of program version, but something else.
I assume that e.g. you have first closed the program before installing the previous version and most probably you have also restarted your PC.

73, Reino OH3mA


locked Re: WSJT-X 2.5.3 GA Release (Win64 only) #general

Karza
 

On 12.12.2021 15.30, Jim Bacher - WB8VSU wrote:
The source is on Sourceforge.
..not the latest version 2.5.3

'Kari, oh2gqc


locked Re: WSJT-X 2.5.3 GA Release (Win64 only) #general

Michael Black
 

Could you also please test echo off?  It should not be required.

Mike W9DMB




On Sunday, December 12, 2021, 02:17:08 AM CST, Stewart Wilkinson <stewart.g0lgs@...> wrote:


2.5.3 GA seems to work fine on my 9700 and 7300 without making any changes to my settings.

However I did see someone say that you need to have 'CIV USB Echo Back' set to ON (mine already was on both radio's).




locked Re: Need help understanding Echo mode. #Echo

Michael Black
 

We fixed several Elecraft problems in Hamlib 4.4 to improve speed -- please try that.

Mike W9MDB




On Sunday, December 12, 2021, 04:10:22 AM CST, Charles Suckling <g3wdg1@...> wrote:


Hi Scott

It looks to me that you have some delays with CAT control of your K3.  Echo mode only produces audio to drive the TX once all the CAT traffic has completer, so very short transmitting duration is a sign that the CAT traffic is taking a while to complete.  I had the same problem here a couple of months ago, which was traced (with Bill G4WJS's help)  to delays in completing the CAT traffic.  That was solved (thanks also to G4JNT)  and then Echo mode reverted to operating normally.  I saw the same issue when pressing 'Tune' in that the rig took a second or two (variable) to produce RF output.  It was due to the same issue, and solved similarly.

Before fixing the problem, switching Doppler to 'None' resulted in normal operation (except that I could not tune to the echo (10GHz)

On 6m, the Doppler shift will be small enough so that very likely you would see any echoes on the Echo Graph, but not quite in the center of the plot, due to your local Doppler shift.  Mighe be worth trying that in the first instance, before tackling your CAT delays.

73

Charlie DL3WDG

On Sat, 11 Dec 2021 at 21:12, Scott Townley <scott@...> wrote:
Trying to use Echo mode to 'hear' myself off the moon on 6m.
Using 6el LFA yagi at 40', K3 and KPA1500.  Seems like that should be sufficient for moonset/moonrise.  
Really my question is around how Echo mode operates.  Here's what I see happening on the front panel of my K3 (this was moonset on 11 Dec 21).  I had Echo set for "Doppler Tracking" and "Constant frequency on Moon".  DF was reported as -123 Hz.
1. Very short TX at 50.19994
2. RX for about 4.5-4.6 seconds on 50.19994 (measured with stopwatch)
3. Radio would go split to 50.20006 for a very short listen
4. Back to 50.19994 and repeat.

It's #2 that has me stumped.  That delay to split RX should only be about 2.6 seconds, right?  So no wonder it doesn't hear me.
I suspect that there is some timing gremlin in my setup.  Candidates could be:
a. I do have my K3 remoted (just in the back of the basement) via RemoteRig boxes.
b. I hear the HamLib application used for CAT control has in the past had K3 issues with PTT turnover.  I have downloaded/installed HamLib 4.3.1 but I don't know if there is an additional step to "link" WSJT-x with that version, or how to check that they are 'linked' (or if that's even necessary).

Would love to hear any suggestions/thoughts on how to move forward.  Thanks in advance,






locked Re: WSJT-X 2.5.3 GA Release (Win64 only) #general

Jim Bacher - WB8VSU
 

The source is on Sourceforge.

In the user's manual see section

1.4. How You Can Contribute

Jim Bacher, WB8VSU
wb8vsu@...

On Dec 11, 2021, at 6:47 PM, Joseph Counsil <counsil@...> wrote:
Joe,

So sad about Bill's passing -- praying for his family.

Would it be possible to make the 2.5.3 source available?  I build on Linux...

73,
-Joe-




locked Re: WSJT-X 2.5.3 GA Release (Win64 only) #general

Mike Abbott
 

I have the same issue.  IC-9700 and IC-7300 will not connect after updating to 2.5.3.  I had to revert back to 2.5.2 and everything worked perfectly.  A real head-scratcher.  I wonder if it's related to the OmniRig package...

5021 - 5040 of 35421