Date   

locked Re: Don't forget about FT4 #FT4 #QSO_practices

Gwen
 

Try JS8Call instead of PSK31 On 12/14/21 4:10 PM, Gary trock wrote: > I enjoy the occasional rag chewing on PSK 31, but have more difficulty > making QSOs, especially DX. My own lack of experience I suspect. > Gary N8GT > > >> On Dec 14, 2021, at 5:42 PM, chas cartmel wrote: >> >>  >> >> Let’s also not forget about JT9 and JT65, PSK variations and many >> other data modes which allow conversational QSOs rather than >> click/exchange reports/log - rinse and repeat. >> >> >> *73 Charlie* >> >> *G4EST* >> >> _www.g4est.me.uk_ >> >> Stay safe out there >> >> *From:*main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] *On Behalf >> Of *David Maihofer >> *Sent:* Tuesday, December 14, 2021 6:28 PM >> *To:* main@wsjtx.groups.io >> *Subject:* Re: [WSJTX] Don't forget about FT4 #FT4 #QSO_practices >> >> Tim, >> >> I agree with your FT4 statement, seems many new users opt for FT8 as >> everything is shifted towards that. I think I would rather user FT4 >> most of the time saving half the time. >> >> There just does not seem to be a reason not too except that all the >> activity is on FT8. >> >> Thanks for bringing that up. >> >> 73 de David, in NW Arkansas >> >> >> >> On Dec 14, 2021, at 07:33, Timothy Brannon wrote: >> >>  >> >> 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 >> >> >> >> >> This email has been scanned by BullGuard antivirus protection. >> For more info visit www.bullguard.com >> >> >> >> > > >


locked Re: Portable calls crashing WSJT-X Version 2.5.3 #Windows10 #windows11 #decode

Rob Kivell
 

Ditto here. Replied to HC1MD\2 CQ call on 20m (if I remember correctly) this morning. He responded and WSJTX crashed. That was the first time the program ever just cashed. It was the last QSO I attempted for that particular session . Just thought it was one of those things. I thought I hit the wrong button but I’m not sure now . I’m using the latest 64 bit program W10 and a Dell laptop. I won’t be back on air tonight but imagine I will hit it again in the morning.

Cheers 

On Tuesday, December 14, 2021, 2:54 PM, Andrea Tommasi <atommasi@...> wrote:

Hello, 
Also i have similar behaviour trying to answer with tx2 (report) to hb0/hb9..... some days ago when wsjtx must send rr73 it crash, to run again wsjtx i need to kill jt9.exe process before.
Tryed two times with same crash.
Win10home 64 bit on xeon cpu and 6 gb ram, i have other qso with hb0/hb9... but never crash with previous release.

73 ik4idp
Andrea

Il 14 dic 2021 20:48, Max NG7M <ng7m@...> ha scritto:

Jim, W7CT and I have been duplicating an issue with 2.5.3 (64-bit version if that matters) this morning, where you start to work a portable call and the UI just terminates...a WSJT process is left running, so you can't start another instance of WSJT until you find terminate the process.  We have duplicated this issue trying to work portable callsigns.  Specifically, N6QEK/KL7, HC1MD/2 (12M), AE5KO/6 (20M).  Not that the bands matter.  But these were actual callsigns that caused the crash.  And I was able to duplicate it after a restart with N6QEK/KL7, he certainly is wondering why stations just stop completing the exchange if they are running 2.5.3. :)

Anyone else noticed this with 2.5.3?

This has been duplicated with Windows 10 and Windows 11.  NG7M running Windows 11 (64 bit obviously) and W7CT running 64bit Windows 10.

Max NG7M






locked Re: Portable calls crashing WSJT-X Version 2.5.3 #Windows10 #windows11 #decode

Rick
 

On 12/14/2021 3:48 PM, Max NG7M wrote:
Jim, W7CT and I have been duplicating an issue with 2.5.3 (64-bit version if that matters) this morning, where you start to work a portable call and the UI just terminates...a WSJT process is left running, so you can't start another instance of WSJT until you find terminate the process.  We have duplicated this issue trying to work portable callsigns.  Specifically, N6QEK/KL7, HC1MD/2 (12M), AE5KO/6 (20M).  Not that the bands matter.  But these were actual callsigns that caused the crash.  And I was able to duplicate it after a restart with N6QEK/KL7, he certainly is wondering why stations just stop completing the exchange if they are running 2.5.3. :)
Anyone else noticed this with 2.5.3?
This has been duplicated with Windows 10 and Windows 11.  NG7M running Windows 11 (64 bit obviously) and W7CT running 64bit Windows 10.
Max NG7M
Yes, exact same thing happened to me today.

Rick VE1GN


locked Re: Don't forget about FT4 #FT4 #QSO_practices

Gary trock
 

I enjoy the occasional rag chewing on PSK 31, but have more difficulty making QSOs, especially DX. My own lack of experience I suspect.
Gary N8GT


On Dec 14, 2021, at 5:42 PM, chas cartmel <chas@...> wrote:



Let’s also not forget about JT9 and JT65, PSK variations and many other data modes which allow conversational QSOs rather than click/exchange reports/log - rinse and repeat.


73 Charlie

G4EST

www.g4est.me.uk

Stay safe out there

 

 

 

From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of David Maihofer
Sent: Tuesday, December 14, 2021 6:28 PM
To: main@wsjtx.groups.io
Subject: Re: [WSJTX] Don't forget about FT4 #FT4 #QSO_practices

 

Tim, 

 

I agree with your FT4 statement, seems many new users opt for FT8 as everything is shifted towards that. I think I would rather user FT4 most of the time saving half the time. 

 

There just does not seem to be a reason not too except that all the activity is on FT8.

 

Thanks for bringing that up. 

 

73 de David, in NW Arkansas

 

 



On Dec 14, 2021, at 07:33, Timothy Brannon <timbmd@...> wrote:



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




This email has been scanned by BullGuard antivirus protection.
For more info visit www.bullguard.com




locked Re: Don't forget about FT4 #FT4 #QSO_practices

chas cartmel
 

Let’s also not forget about JT9 and JT65, PSK variations and many other data modes which allow conversational QSOs rather than click/exchange reports/log - rinse and repeat.


73 Charlie

G4EST

www.g4est.me.uk

Stay safe out there

 

 

 

From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of David Maihofer
Sent: Tuesday, December 14, 2021 6:28 PM
To: main@wsjtx.groups.io
Subject: Re: [WSJTX] Don't forget about FT4 #FT4 #QSO_practices

 

Tim, 

 

I agree with your FT4 statement, seems many new users opt for FT8 as everything is shifted towards that. I think I would rather user FT4 most of the time saving half the time. 

 

There just does not seem to be a reason not too except that all the activity is on FT8.

 

Thanks for bringing that up. 

 

73 de David, in NW Arkansas

 

 



On Dec 14, 2021, at 07:33, Timothy Brannon <timbmd@...> wrote:



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




This email has been scanned by BullGuard antivirus protection.
For more info visit www.bullguard.com


locked Re: Don't forget about FT4 #FT4 #QSO_practices

M0PWX
 

I tend to go to FT4 quite often, as it is less popular so you can actually work less common stations as there is space in the spectrum both side

 

I also like JTAlert,

 

Activity window is great to see the number of station on and you can see which bands are heavily used,, at which point I will often avoid them

 

73

Peter

M0PWX

 

M0PWX Grabber Page (qsl.net)

 

From: David Maihofer
Sent: 14 December 2021 19:17
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] Don't forget about FT4 #FT4 #QSO_practices

 

Tim, 

 

I agree with your FT4 statement, seems many new users opt for FT8 as everything is shifted towards that. I think I would rather user FT4 most of the time saving half the time. 

 

There just does not seem to be a reason not too except that all the activity is on FT8.

 

Thanks for bringing that up. 

 

73 de David, in NW Arkansas

 

 



On Dec 14, 2021, at 07:33, Timothy Brannon <timbmd@...> wrote:



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 WSIT-X RF & SQL affect on FT8 signals

 

I have used FT8 for for several years with much success with my TS-590SG, but I noticed something today that I never saw before and I need the forum's advice on it. I noticed that I had no WSJT left side dB bar reading in the green - no nothing. I then noticed that I had to have the SQL open (5.5) a little as well as the RF slightly closed (8.5) to even get a green bar? I don't believe this is normal? Shouldn't I be able to closed the SQL and RF completely (10 reading) and still have a green dB bar?  I checked my TS-590S & sound card settings and they all seem good. 

One other note when I reduce the RF gain even slightly, I get a board red line across the MSK144 waterfall?  See below attachment - Blue bar RF at 10 no left side dB green bar.  RF at 9.5 green bar and large red bar in waterfall.
Confused - any help appreciated



Tnx,
Glenn
K4ZOT


locked Re: Portable calls crashing WSJT-X Version 2.5.3 #Windows10 #windows11 #decode

Andrea Tommasi
 

Hello, 
Also i have similar behaviour trying to answer with tx2 (report) to hb0/hb9..... some days ago when wsjtx must send rr73 it crash, to run again wsjtx i need to kill jt9.exe process before.
Tryed two times with same crash.
Win10home 64 bit on xeon cpu and 6 gb ram, i have other qso with hb0/hb9... but never crash with previous release.

73 ik4idp
Andrea

Il 14 dic 2021 20:48, Max NG7M <ng7m@...> ha scritto:

Jim, W7CT and I have been duplicating an issue with 2.5.3 (64-bit version if that matters) this morning, where you start to work a portable call and the UI just terminates...a WSJT process is left running, so you can't start another instance of WSJT until you find terminate the process.  We have duplicated this issue trying to work portable callsigns.  Specifically, N6QEK/KL7, HC1MD/2 (12M), AE5KO/6 (20M).  Not that the bands matter.  But these were actual callsigns that caused the crash.  And I was able to duplicate it after a restart with N6QEK/KL7, he certainly is wondering why stations just stop completing the exchange if they are running 2.5.3. :)

Anyone else noticed this with 2.5.3?

This has been duplicated with Windows 10 and Windows 11.  NG7M running Windows 11 (64 bit obviously) and W7CT running 64bit Windows 10.

Max NG7M



locked Re: Don't forget about FT4 #FT4 #QSO_practices

Jim Brown
 

On 12/14/2021 5:04 AM, Timothy Brannon wrote:
I wish more people would try FT4 in the morning, and relieve the congestion on FT8.
There's plenty of room on CW, and conditions to Asia are usually good for two hours after our local sunrise.

73, Jim K9YC


locked Portable calls crashing WSJT-X Version 2.5.3 #Windows10 #windows11 #decode

Max NG7M
 

Jim, W7CT and I have been duplicating an issue with 2.5.3 (64-bit version if that matters) this morning, where you start to work a portable call and the UI just terminates...a WSJT process is left running, so you can't start another instance of WSJT until you find terminate the process.  We have duplicated this issue trying to work portable callsigns.  Specifically, N6QEK/KL7, HC1MD/2 (12M), AE5KO/6 (20M).  Not that the bands matter.  But these were actual callsigns that caused the crash.  And I was able to duplicate it after a restart with N6QEK/KL7, he certainly is wondering why stations just stop completing the exchange if they are running 2.5.3. :)

Anyone else noticed this with 2.5.3?

This has been duplicated with Windows 10 and Windows 11.  NG7M running Windows 11 (64 bit obviously) and W7CT running 64bit Windows 10.

Max NG7M


locked Re: Don't forget about FT4 #FT4 #QSO_practices

David Maihofer <maihofer.david@...>
 

Tim, 

I agree with your FT4 statement, seems many new users opt for FT8 as everything is shifted towards that. I think I would rather user FT4 most of the time saving half the time. 

There just does not seem to be a reason not too except that all the activity is on FT8.

Thanks for bringing that up. 

73 de David, in NW Arkansas



On Dec 14, 2021, at 07:33, Timothy Brannon <timbmd@...> wrote:



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 #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

Tim Brannon, WA5MD
 

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!

9681 - 9700 of 40097