Date   

locked #MSK144 Waveform #MSK144

Andy Talbot
 

Purely out of interest :
While looking at the MSK144 coding process I noted there are two procedures in the Fortran code to generate the waveform for transmission.

First is to use the raw output from the coding process, ie. sync+message+CRC+parity and alternately modulate I and Q12kHz sampled  NCO data streams to generate offset QPSK at audio.
This is what is actually done inside WSJT-X to generate MSK144

But there's a secondary bit of code in there whose output is used in the MSK144CODE.EXE utility.  That differentially encodes that stream of '1's and '0's, inverting alternate bits to generate a pattern for modulating an FSK source for a frequency shift exactly half that of the symbol rate. Another way of generating MSK.

I've taken that bit pattern and applied it to a two channel quadrature DDS to generate the two frequencies [plus] +500Hz  and [minus] -500Hz, ie FSK at 1000Hz shift centred on zero frequency.  This can be done by swapping the I/Q channels, or inverting one of them, but in a quadrature output DDS it's easier to feed the NCO with +/- twos complement values of the increment for the wanted frequency.

The attached picture is of the two I/Q baseband streams from the DDS.  As can be seen, the maximum of one channel flips at the zero crossing of the other - exactly what you'd expect of an offset QPSK baseband signal.

It is nice to see theory and practice come together once in a while!
http://www.g4jnt.com/DropF/img3225.JPG


locked Don't forget about FT4 #FT4 #QSO_practices

Timothy Brannon
 

I like to get on 40 meters in the predawn hours (US Central Time), but most mornings are absolute bedlam on 7074 kHz. The FT8 waterfall is so full of strong signals, I can hardly find a clear spot to transmit.
So, I often click Mode in WSJT-X and switch to FT4 on 7047.5 kHz, but the problem there is the opposite -- the waterfall is completely empty! I did just complete a contact with VK2LAW with nice -12 dB signals both ways, but then my 25 CQ calls went unanswered.
Remember, with FT4 you're only giving up 3.5 dB of sensitivity, but the SNR is much better without the crowding/QRM, and contacts are completed in half the time. I wish more people would try FT4 in the morning, and relieve the congestion on FT8. Come try it!
73 de Tim, WA5MD in Dallas


locked Re: Capture Raw View to file? #QSO_practices

Reino Talarmo
 

>Is it possible to capture the Raw View data to a file?

Hi Barry,

It depends what you mean by “Raw View data”. If you mean what you see in the Band Activity window, then that data is stored into ALL.TXT file in the Log Directory.

If you mean audio signal before decoding, then you may Save it into .vaw files with a selection in the Save menu.

73, Reino OH3mA


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

Brian G3VGZ
 

I tried FST4 last February. Total 19 qsos on 160, but activity dried up.


"Jim Brown" <k9yc@...> wrote:


I haven't been able to decodes FST4 or FST4W on 160 (or 80 or other HF).
That may be because these modes have not been adopted by users. I haven't
looked this season, but last winter I saw no FST4 or FST4W activity on
160M. FST4 is the dominant mode on 630m.

73, Jim K9YC

--
Brian D
G3VGZ G8AOE G3T
IO94im


locked Capture Raw View to file? #QSO_practices

WØIY
 

Is it possible to capture the Raw View data to a file?

I'd like to do some offline analysis. For example the time of first JA heard, and the last.
There is some very interesting Dx on 20m overnight.

It would also be possible, looking at signal levels, to show how many Qs could have been done on FT4 rather than FT8. It is very evident that many stations running high power would be better off on FT4.

I'm running on a Pi400.
Barry w0iy


locked WSJT-X 2.5.3 GA Release for 32-bit Windows 7 and later #general

Joe
 

Uwe Risse, DG2YCB, has kindly prepared a 32-bit Windows installation package for WSJT-X 2.5.3. A download link has been posted on the WSJT-X web page here:
https://physics.princeton.edu//pulsar/k1jt/wsjtx.html

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


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

Jim Brown
 

I haven't been able to decodes FST4 or FST4W on 160 (or 80 or other HF).
That may be because these modes have not been adopted by users. I haven't looked this season, but last winter I saw no FST4 or FST4W activity on 160M. FST4 is the dominant mode on 630m.

73, Jim K9YC


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

Michael Black
 

It should also be fixed in the latest DLL -- echo on or off







On Monday, December 13, 2021, 09:08:41 AM CST, Mike Abbott via groups.io <kk4ma@...> wrote:


Echo ON fixed the USB comm failure for me on both the IC-7300 and IC-9700!  Whoo-Hoo!  Back up and running in time for Geminids!




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

Mike Abbott
 

Echo ON fixed the USB comm failure for me on both the IC-7300 and IC-9700!  Whoo-Hoo!  Back up and running in time for Geminids!


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



7621 - 7640 of 38026