Date   

locked rc5

Bob
 

IMHO, FT4 is ho-hum, but I really do like the way the placement of the OK/CANCEL buttons on the Log QSO confirmation window appear move around at random. I wonder what other eye candy FT2 and FT0 have in store? SeventyThree(s).


locked FT4 FT8 on 5357 kHz 60m band

Bonnie KQ6XA
 

FT4 and FT8 sharing 5357.0 kHz USB.

The 60 metre band is a sensitive subject due to its peculiar secondary allocations and delicate operating rules. 
Allocations and radio rules for 60 metre operation vary significantly in different countries.
5351.5 kHz to 5366.5 kHz has become an ITU VFO band, but it is not allocated yet in some countries (USA, Japan, and Australia for examples). 

There has been increasingly active FT8 operation on 60 metres over the past year, normally found on the 5357.0 kHz USB channel.
There are two reasons for this is:
 
  1. ) 5357.0 USB is the only "international interoperability channel" on the 60 metre band at the present time.
  2. ) Frequencies below 10 MHz are relied upon for HF propagation in the "valley years" between solar cycle peaks.
 
For international interoperability,  FT4 can share the 5357 channel with FT8. 
  • Although it was designed for fast contesting, FT4 as a mode is not inherently limited to "contesting" operation. 
  • The sharing or interleaving of FT4 contacts with FT8 contacts shouldn't be a problem, because these two narrowband FT sub-modes (and other modes) can co-exist peacefully within the same passband. 
  • They are decoded independently, according to the mode set by the operator. 
  • The modes are distinctly recognizable in timing and visual signature, so they can be differentiated by the operator on the waterfall. 

Split operation using the 5357 kHz channel is commonplace, and is absolutely necessary for operators in some countries, due to channel frequency limits or single frequency centre rules. 
  • USA operators would still need to select their own fixed transmit frequency to stay near 1500 Hz, to comply with the spirit of their FCC rules for the 60 meter band. 
  • UK operators would need to select their own fixed transmit frequency between 0 Hz and 1000 Hz to comply with the UK 5 MHz channel limit. 
 
For operators in countries which are not bound by channelization rules, perhaps the following suggestion could be helpful:
  • FT4 = 100 Hz to 1500 Hz (5357.1 to 5358.5 kHz limits) 
  • FT8 = 1500 Hz to 2900 Hz  (5358.5 to 5359.9 kHz limits) 

Although the 60 metre international ITU band is a VFO band, the popular activity trend worldwide is voluntarily channelized: 
  • 5351.5 ITU Band lower limit
  • 5351.5 USB (5351.6 - 5354.1 CW. Digital. All modes) Popular CW
  • 5354.0 USB (USB Voice. All modes) Popular SSB QSOs
  • 5357.0 USB (USB Voice. Digital. FT8. All modes) Popular FT8
  • 5360.0 USB (USB Voice. All modes.) Popular SSB Calling Channel
  • 5363.0 USB (USB Voice. All modes.) Popular SSB QSOs
  • 5365.5 USB (5366.0 - 5366.4 CW. Digital. All modes) Popular WSPR and CW.
  • 5366.5 ITU Band upper limit
 
-Bonnie KQ6XA


locked Re: FT4 LotW logging. What mode do you use?

Joe Subich, W4TV
 

On 2019-04-30 5:31 PM, Bill Somerville wrote:
I believe it is automatic when you install the updated configuration,
and re-upload all your F4 contacts.
User installed mode mapping is not removed when installing an updated
CONFIG.XML file from LotW. It will be necessary to remove the JT4 ->
DATA mapping the same way it was created.

73,

... Joe, W4TV


On 2019-04-30 5:31 PM, Bill Somerville wrote:
On 30/04/2019 22:24, Komkit Listisard via Groups.Io wrote:
Tried to log as FT4 contact but I can guess FT4 is not a valid mode on LotW (yet).

What mode do you use?

Error: Invalid MODE (FT4) on line 5
CALL: XXXXXX
TIME_ON: 204400
QSO_DATE: 20190430
MODE: FT4
BAND: 20M
FREQ: 14.08363
BAND_RX: 20M
FREQ_RX: 14.08363

Warning: Signing aborted
No records to upload
Hi Komkit,
LoTW should change their configuration file to accept FT4 when the ADIF committee adopt the mode to the ADIF specification. Until then you can add a mapping to tQSL to map FT4 mode to the more general DATA mode:
once you have done that your FT4 contacts will be accepted and you will get matches where your QSO partners have done the same. Once FT4 is adopted you can remove the mapping, I believe it is automatic when you install the updated configuration, and re-upload all your F4 contacts. They will then be automatically upgraded to FT4 and you will get new matches for FT4 mode as your QSO partners do the same.
73
Bill
G4WJS.


locked Re: Subprocess Error exit code 2

LA7NO
 

Thanks for info.
How do I save a .WAW file?

I have tried to recreate the error using the supplied F4 .WAW file, but so far no luck.

73,
Per-Tore / LA7NO


locked Re: 2.1.0-rc5 crashing on launch on mac

Alfonso J.
 

Same situation for me. This is what I see on Apple crash report when running App (simplified):

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY

Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [583]

And that is what I get running from Terminal:

malloc: can't allocate region
*** mach_vm_map(size=5044062055447924736) failed (error code=3)
wsjtx(639,0x1119705c0) malloc: *** set a breakpoint in malloc_error_break to debug
Segmentation fault: 11

Machines are an iMac 27" End 2013 with macOS Mojave 10.14.4 and MacBook Pro 13" End 2013 with macOS 10.14.4

73

Alfonso - EA5IUN


locked Re: FT4 LotW logging. What mode do you use?

Komkit Listisard
 

Sweet, never knew that option :)

Thanks so much..

73, Komkit W3KIT


locked Re: FT4 LotW logging. What mode do you use?

Bill Somerville
 

On 30/04/2019 22:24, Komkit Listisard via Groups.Io wrote:
Tried to log as FT4 contact but I can guess FT4 is not a valid mode on LotW (yet).

What mode do you use?

Error: Invalid MODE (FT4) on line 5
CALL: XXXXXX
TIME_ON: 204400
QSO_DATE: 20190430
MODE: FT4
BAND: 20M
FREQ: 14.08363
BAND_RX: 20M
FREQ_RX: 14.08363

Warning: Signing aborted
No records to upload

Hi Komkit,

LoTW should change their configuration file to accept FT4 when the ADIF committee adopt the mode to the ADIF specification. Until then you can add a mapping to tQSL to map FT4 mode to the more general DATA mode:

once you have done that your FT4 contacts will be accepted and you will get matches where your QSO partners have done the same. Once FT4 is adopted you can remove the mapping, I believe it is automatic when you install the updated configuration, and re-upload all your F4 contacts. They will then be automatically upgraded to FT4 and you will get new matches for FT4 mode as your QSO partners do the same.

73
Bill
G4WJS.


locked FT4 LotW logging. What mode do you use?

Komkit Listisard
 

Tried to log as FT4 contact but I can guess FT4 is not a valid mode on LotW (yet).

What mode do you use?

Error: Invalid MODE (FT4) on line 5
CALL: XXXXXX
TIME_ON: 204400
QSO_DATE: 20190430
MODE: FT4
BAND: 20M
FREQ: 14.08363
BAND_RX: 20M
FREQ_RX: 14.08363

Warning: Signing aborted
No records to upload


locked Re: FT4 and Linux dumb question

Greg Beam, KI7MT <ki7mt01@...>
 

Hi Bill, All,

One can use upate/config alternatives for multiple versions of a given application, however, for WSJTX it's not very practical.

Over the years, when using distro-installed versions of WSJTX, I found easiest to do as you suggested; uninstall the old version, then install the new when an RC has been released.

I do copy / backup / rename my ~/.local/WSJTX directory so I can easily restore for whatever version I am using.

For RC5, I used the *.deb file you all posted on Joe's website, and it's working as expected. I'm using Ubuntu 18.04 so I would think any of the resent Mint flavors should work equally as well.

73's
Greg, KI7MT

On 4/30/19 9:31 AM, Bill Somerville wrote:
On 30/04/2019 16:17, Bill Carpenter wrote:
I use Linux Mint 19.1 and want to try FT4.  In the protocol document it states that one should install 2.1.0-rc5 in a different directory than  the one used for 2.0.  I will admit that though I use Linux I am not all that well versed in it.  Does this rule apply to Linux or just to Windows?  And if it does apply to Linux how do I install into a different directory?  I used all the rc packages when the move to 2.0 from 1.9 was made with no problems.

73, Bill NZ0T
Hi Bill,
there are ways of installing a Linux package to an alternate location, I am not sure how to do it on Debian style distributions. OTOH it is pretty quick to uninstall a package and install another if you are not using the one from the distribution repositories. I believe both the WSJT-X v2.0.1 GA and the v2.1.0 release candidates cam be installed on Linux Mint 19 using the .deb files we provide at release time.
73
Bill
G4WJS.


locked Re: Subprocess Error exit code 2

Bill Somerville
 

On 30/04/2019 17:15, LA7NO wrote:
Hello Bill,

I will do my best to try to help.
How can I use a saved .WAW file_

One, maybe important info, that I forgot to tell: I am running remote using Remoterig RRC/1258 MkII.
With FT8 it has worked flawlessly for a long time. But on FT4 I have not yet got any response to my calls.
Plenty of strong stations received.

73,

Per-Tore / LA7NO

Hi Per-Tore,

to play back a saved .WAV file in WSJT-X, set the program to the correct mode and go to "Menu->File->Open" or CTRL+O as a keyboard shortcut. Select the .WAV file in the file chooser that opens then click "Open". The file will replay as if received, running the decoder at the end of the data. Subsequent .WAV files can be quickly replayed using the F6 shortcut key or using the "Menu->File" options. All of the remain files may be replayed in sequence using SHIFT+F6. The file names represent the start times of the periods that contain and the names are displayed at the bottom left of the main Window.

Your RemoteRig RRC connection may be less effective with FT4 as the time synchronization tolerances are tighter than with FT8, I think we currently support net DT values of ± 0.5 S. Other artefacts introduced by audio stream compression techniques may also have more of an impact on the shorter FT4 message periods.

73
Bill
G4WJS.


locked Re: FT4 public release now avaiablle

James Quick
 

Hello Bill,

Anything new on WSJT-X v2,1,0-rc5 for us Mac users? Thanks for your help.

73

Jim Quick / N4ULE
n4ule@...
On 4/29/19 6:51 PM, Bill Somerville wrote:

On 29/04/2019 23:29, James Quick wrote:

Installed WSJT-X 2.1.0-rc5 and now every time I try to start a QSO the program shuts down. I am running,

FTDX-3000

MacOS Mojave v 10.14.4

MacLoggerDx

I had no trouble with WSJT-X 2.0.1. Thanks for any help or advice.

73

Jim Quick / N4ULE
n4ule@...

Hi Jim,

sorry about this, we are looking into the cause of this crash on macOS.

73
Bill
G4WJS.


-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.

View/Reply Online (#3031): https://groups.io/g/WSJTX/message/3031
Mute This Topic: https://groups.io/mt/31411802/239407
-=-=-
Moderated by Andy K3UK and Roger G4HZA
-=-=-
Group Owner: WSJTX+owner@groups.io
Unsubscribe: https://groups.io/g/WSJTX/leave/484785/1156357303/xyzzy  [n4ule@...]
-=-=-=-=-=-=-=-=-=-=-=-


locked Re: Subprocess Error exit code 2

LA7NO
 

Hello Bill,

I will do my best to try to help.
How can I use a saved .WAW file_

One, maybe important info, that I forgot to tell: I am running remote using Remoterig RRC/1258 MkII.
With FT8 it has worked flawlessly for a long time. But on FT4 I have not yet got any response to my calls.
Plenty of strong stations received.

73,

Per-Tore / LA7NO




On Tue, 30 Apr 2019 at 16:04, Bill Somerville <g4wjs@...> wrote:
On 30/04/2019 00:12, LA7NO wrote:
> Got this several times under Windows 10 Build 18362:
>
> Subprocess Error
> exit code 2
>
> Running: C:\WSJT\wsjtx\bin\jt9 -s WSJT-X -w 1 -m 3 -e
> C:\WSJT\wsjtx\bin -a C:\Users\ptaa\AppData\Local\WSJT-X -t
> C:\Users\ptaa\AppData\Local\Temp\WSJT-X
> At line 41 of file C:\Users\bill\src\k1jt\wsjtx\lib\ft4\ft4_downsample.f90
> Fortran runtime error: Index '-2147483648' of dimension 1 of array
> 'cx' below lower bound of 0
>
> Error termination. Backtrace:
>
> Could not print backtrace: libbacktrace could not find executable to open
> #0  0xffffffff
> #1  0xffffffff
> #2  0xffffffff
> #3  0xffffffff
> #4  0xffffffff
> #5  0xffffffff
> #6  0xffffffff
> #7  0xffffffff
> #8  0xffffffff
> #9  0xffffffff
> #10  0xffffffff
> #11  0xffffffff
> #12  0xffffffff
> #13  0xffffffff

Hi OM,

thanks for this issue report. We think we have a fox for it, but as the
issue is intermittent we have not yet been able to verify the fix. If
you can reproduce this with a saved .WAV file, that file would be useful
for testing.

73
Bill
G4WJS.

-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.

View/Reply Online (#3045): https://groups.io/g/WSJTX/message/3045
Mute This Topic: https://groups.io/mt/31414869/211608
-=-=-
Moderated by Andy K3UK and Roger G4HZA
-=-=-
Group Owner: WSJTX+owner@groups.io
Unsubscribe: https://groups.io/g/WSJTX/leave/3802888/1672034803/xyzzy  [ptaa32@...]
-=-=-=-=-=-=-=-=-=-=-=-


locked Re: FT4 and Linux dumb question

Bill Somerville
 

On 30/04/2019 16:17, Bill Carpenter wrote:
I use Linux Mint 19.1 and want to try FT4.  In the protocol document it states that one should install 2.1.0-rc5 in a different directory than  the one used for 2.0.  I will admit that though I use Linux I am not all that well versed in it.  Does this rule apply to Linux or just to Windows?  And if it does apply to Linux how do I install into a different directory?  I used all the rc packages when the move to 2.0 from 1.9 was made with no problems.

73, Bill NZ0T
Hi Bill,

there are ways of installing a Linux package to an alternate location, I am not sure how to do it on Debian style distributions. OTOH it is pretty quick to uninstall a package and install another if you are not using the one from the distribution repositories. I believe both the WSJT-X v2.0.1 GA and the v2.1.0 release candidates cam be installed on Linux Mint 19 using the .deb files we provide at release time.

73
Bill
G4WJS.


locked Re: FT4 on 5357.0 USB 100 to 1500Hz

Guy G4DWV 4X1LT
 

Just work split. I always do on all bands.
--
73 de Guy G4DWV 4X1LT


locked Re: question on FT4.

Paul F6EXV <f6exv@...>
 

Hi
I thought FT4 was meant for contest....
Why can't people go by the rules ?
73
Paul F6EXV

Le 30/04/2019 à 16:12, pa3gcu@... a écrit :
Hi All.

Firstly thanks for the new mode.

When calling a stn, in FT4 the program cuts of my prefix (EA5/)pa3gcu,
in the TX1 box is written
DE EA5/PA3GCU JN00 photo attached.

Is this normal or am i missing something.??

Thanks Richard PA3GCU.

-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.

View/Reply Online (#3046): https://groups.io/g/WSJTX/message/3046
Mute This Topic: https://groups.io/mt/31420425/1617670
-=-=-
Moderated by Andy K3UK and Roger G4HZA
-=-=-
Group Owner: WSJTX+owner@groups.io
Unsubscribe: https://groups.io/g/WSJTX/leave/3548023/1633844922/xyzzy [f6exv@...]
-=-=-=-=-=-=-=-=-=-=-=-

---
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
https://www.avast.com/antivirus


locked FT4 and Linux dumb question

Bill Carpenter
 

I use Linux Mint 19.1 and want to try FT4.  In the protocol document it states that one should install 2.1.0-rc5 in a different directory than  the one used for 2.0.  I will admit that though I use Linux I am not all that well versed in it.  Does this rule apply to Linux or just to Windows?  And if it does apply to Linux how do I install into a different directory?  I used all the rc packages when the move to 2.0 from 1.9 was made with no problems.

73, Bill NZ0T


locked question on FT4.

pa3gcu@...
 
Edited

Hi All.

Firstly thanks for the new mode.

When calling a stn, in FT4 the program cuts of my prefix (EA5/)pa3gcu, in the TX1 box is written
DE EA5/PA3GCU JN00 photo attached.

Is this normal or am i missing something.??

Thanks Richard PA3GCU.


locked Re: Subprocess Error exit code 2

Bill Somerville
 

On 30/04/2019 00:12, LA7NO wrote:
Got this several times under Windows 10 Build 18362:

Subprocess Error
exit code 2

Running: C:\WSJT\wsjtx\bin\jt9 -s WSJT-X -w 1 -m 3 -e C:\WSJT\wsjtx\bin -a C:\Users\ptaa\AppData\Local\WSJT-X -t C:\Users\ptaa\AppData\Local\Temp\WSJT-X
At line 41 of file C:\Users\bill\src\k1jt\wsjtx\lib\ft4\ft4_downsample.f90
Fortran runtime error: Index '-2147483648' of dimension 1 of array 'cx' below lower bound of 0

Error termination. Backtrace:

Could not print backtrace: libbacktrace could not find executable to open
#0  0xffffffff
#1  0xffffffff
#2  0xffffffff
#3  0xffffffff
#4  0xffffffff
#5  0xffffffff
#6  0xffffffff
#7  0xffffffff
#8  0xffffffff
#9  0xffffffff
#10  0xffffffff
#11  0xffffffff
#12  0xffffffff
#13  0xffffffff
Hi OM,

thanks for this issue report. We think we have a fox for it, but as the issue is intermittent we have not yet been able to verify the fix. If you can reproduce this with a saved .WAV file, that file would be useful for testing.

73
Bill
G4WJS.


locked Re: 2.1.0-rc5 crashing on launch on mac

James Quick
 

They are working on it.

Jim Quick / N4ULE
n4ule@...
On 4/29/19 11:09 PM, Jim wrote:

Every time I try to launch WSJTX 2.1.0-rc5 on my mac it crashes. Ive tried re-downloading, reinstalling, rebooting, and still no joy. I'm using a 2010 iMac with Mac OS 10.13.6. 

Does anyone have any suggestions on how to get this fixed and up and running?

73

Jim - KH2SR

-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.

View/Reply Online (#3041): https://groups.io/g/WSJTX/message/3041
Mute This Topic: https://groups.io/mt/31416651/239407
-=-=-
Moderated by Andy K3UK and Roger G4HZA
-=-=-
Group Owner: WSJTX+owner@groups.io
Unsubscribe: https://groups.io/g/WSJTX/leave/484785/1156357303/xyzzy  [n4ule@...]
-=-=-=-=-=-=-=-=-=-=-=-


locked Re: FT4 on 5357.0 USB 100 to 1500Hz

Steve m0mvb
 

That Idea would not work over here in the UK as our allocation for that part of 60 meters is 5354 KHz to 5358 KHz, all our activity on 5357 KHz has to be below 1000 Hz on the waterfall, if above it will be out of band
--  (5357.0 KHz + 1000 Hz = 5358 KHz) 
Vy73
Steve M0MVB