Date   

locked Re: Frequencies are different when switching between FT8 and FT4 #FT8 #WSJTX_config #FT4

neil_zampella
 

There will always be a frequency change, as the frequencies of the FT4 'areas' are different from the FT8 areas.   As far as why its missing, have you tied doing a Frequency List reset?

Go into Settings -> Frequencies and RIGHT click in the list, from the menu select RESET.    You should then see a 20m FT4 frequency.   

Neil, KN3ILZ

Neil, KN3ILZ

On 8/31/2021 11:18 AM, Jack Olivieri wrote:
When switching from FT8 to FT4 (under the Mode pulldown), I get a different set of frequencies  and there is no choice for 14.080. In fact there is no 20M choice at all.
What am I doing wrong?
Jack WA!FEF






locked Re: Frequencies are different when switching between FT8 and FT4 #FT8 #WSJTX_config #FT4

Bill Somerville
 

On 31/08/2021 17:18, Jack Olivieri wrote:
When switching from FT8 to FT4 (under the Mode pulldown), I get a different set of frequencies and there is no choice for 14.080. In fact there is no 20M choice at all.
What am I doing wrong?
Jack WA!FEF
Hi Jack,

FT8 and FT4 use different transmit periods so are not compatible, they are used in different frequency sub-bands. The WSJT-X "Settings->Frequencies->Working Frequencies" table defines the frequencies offered on the main window pop up list, they can be mode and region specific. If you have upgraded from an older version of WSJT-X you probably need to reset the list to the current defaults (right-click the table body and press the "Reset ..." button in the contextual pop up menu that appears.

73
Bill
G4WJS.


locked Frequencies are different when switching between FT8 and FT4 #FT8 #WSJTX_config #FT4

Jack Olivieri
 

When switching from FT8 to FT4 (under the Mode pulldown), I get a different set of frequencies and there is no choice for 14.080. In fact there is no 20M choice at all.
What am I doing wrong?
Jack WA!FEF


locked Re: Adding WSJTX to Mac #TechnicalHelpQuestion #macOS

Marty Bigos
 

Bill -

Thanks for the input. The sound card has analog audio out (of course) but I don't know how much, if any amplification, it has. 

I modified my settings by decreasing the KX3 mic gain to 10, and raising the WSJT-x pwr to -15db (sound card still at -8db). Monitoring both the WSJT output and the sound card output with  headphones I hear a clear warble moderately loud. Operating in these conditions appear to give me more frequent QSOs. The signal reports haven't changed, but maybe my signal is now easier to decode at the receiving end?

Marty
KN6OKN


locked Re: Two copies of WSJT-X open - slight glitch #transmit #networking

Bill Somerville
 

On 31/08/2021 15:23, groups.io@... wrote:
Apologies if this has been asked before.

I have one copy open for my IC-9700 on VHF/UHF and the other for HF on my IC-7300.

I use the call roster on GridTracker and when I double click on a station it populates the correct copy of WSJT-X and if the station is calling CQ then it toggles Enable-TX to on.

However, particularly if it is an HF link from GT and if I am already in Enable-TX on VHF then the Enable-TX is toggled to off on the VHF copy as the HF is turned on.

I am guessing that this is something that GridtRcaker might be "doing/causing" inadvertantly?

Thanks in advance - Terry
Hi Terry,

you can diagnose which end the problem lies by using the test application message_aggregator that ships with WSJT-X. Run that with two instances of WSJT-X and use it to initiate QSOs to see if there is an cross "interference" between WSJT-X instances.

73
Bill
G4WJS.


locked Two copies of WSJT-X open - slight glitch #transmit #networking

groups.io@...
 

Apologies if this has been asked before.

I have one copy open for my IC-9700 on VHF/UHF and the other for HF on my IC-7300.

I use the call roster on GridTracker and when I double click on a station it populates the correct copy of WSJT-X and if the station is calling CQ then it toggles Enable-TX to on.

However, particularly if it is an HF link from GT and if I am already in Enable-TX on VHF then the Enable-TX is toggled to off on the VHF copy as the HF is turned on.

I am guessing that this is something that GridtRcaker might be "doing/causing" inadvertantly?

Thanks in advance - Terry


locked Re: Map65 issue #map65

Peter Hutchison
 

Bill,

Yes - I knew about the release of WSJT-X V2.5.0-rc5 but as I'm not very good with computers thought that I'd leave it to much better beta testers first.

I will continue to run the old Map65 on the old HP notebook / FCR Pro+ combination for the time being then re-visit in a few weeks time.

I've sorted out the screen issue by hooking the notebook upto an old 21" monitor!

It was just that the symptons were  (and still are) very puzzling.

Cheers, Peter G4URT


locked Re: Windows 10 "crash"? #WSPR #IssueReport

Ryan Trullinger (KC0QNB)
 

Never thought about that after the latest update, I changed the power management to off, thanks!


locked Re: Windows 10 "crash"? #WSPR #IssueReport

William Smith
 

Is it possible you (un)plugged a USB device, (dis)connected a Remote Desktop connection, (had Windows automatically and without warning) do a Windows Update, or something else?

It might be useful to iterate through all your USB devices, hubs, and connections with Device Manager and disable any power saving settings.

73, Willie N1JBJ


On Aug 31, 2021, at 8:59 AM, Ryan Trullinger (KC0QNB) <rt83021@...> wrote:

Over the past week or so, I have been receiving WSPR, after a while I check and WSJT-X closed. At first, I thought when my screensaver turned on it somehow caused the program to close.
This morning I was running WSPR on RX and TX while working in my room, the program just quit out of the blue, and no, the screensaver wasn't running.
The latest version of WIN 10, WSJT-X V2.4.0.
Thoughts, Ideas?


locked Re: Windows 10 "crash"? #WSPR #IssueReport

 

Ryan

 

Is there a memory leakage somewhere along the line. Keep an eye on the amount of memory WSJT-X is using. If it is slowly climbing up, sooner or later it will crash. How long depends on what else you have running at the time and how much memory you have fitted in your PC.

 

That said it might not be a fault condition. If the software is keeping a list of events (such as decodes) this will also slowly build up the amount of memory used.

 

73 Phil GM3ZZA

 

Sent from Mail for Windows

 

From: Ryan Trullinger (KC0QNB)
Sent: 31 August 2021 13:59
To: main@WSJTX.groups.io
Subject: [WSJTX] Windows 10 "crash"? #WSPR #IssueReport

 

Over the past week or so, I have been receiving WSPR, after a while I check and WSJT-X closed. At first, I thought when my screensaver turned on it somehow caused the program to close.
This morning I was running WSPR on RX and TX while working in my room, the program just quit out of the blue, and no, the screensaver wasn't running.
The latest version of WIN 10, WSJT-X V2.4.0.
Thoughts, Ideas?

 


--
73 Phil GM3ZZA


locked Windows 10 "crash"? #WSPR #IssueReport

Ryan Trullinger (KC0QNB)
 

Over the past week or so, I have been receiving WSPR, after a while I check and WSJT-X closed. At first, I thought when my screensaver turned on it somehow caused the program to close.
This morning I was running WSPR on RX and TX while working in my room, the program just quit out of the blue, and no, the screensaver wasn't running.
The latest version of WIN 10, WSJT-X V2.4.0.
Thoughts, Ideas?


locked FTDX-10 for MSK144? #MSK144

Steve Kavanagh
 

I am considering purchasing one, partly for 6 m meteor scatter operation using MSK144. I saw in another topic that WB4OMG posted that his FTDX-101 (somewhat similar design) required the use of the 12 kHz roofing filter to receive well on MSK144.

It appears from the block diagram that the transmitter in the '10 is a true software defined architecture, so any bandwidth/group delay shortcomings in the receive 3 kHz roofing filter should not be an issue on transmit.  I do note, however that the specified TX SSB audio response (for both the FTDX-10and -101D) is a bit narrow for MSK144 ("not more than -6 dB from 300 to 2700 Hz").  There is no spec for data modes.  Has anyone any experience with this aspect?

Are there any practical pitfalls to using a 12 kHz wide roofing filter for 6 m MSK144?

Has anyone else had experience with the FTDX-10 or -101 on MSK144 that I should be aware of?  

73,
Steve VE3SMA


locked Re: MODE vs. SUBMODE for FT8 or FT4 #adiFiles #logging #FT4 #FT8

 

LotW accepts the ADIF as specified. LotW were part of the discussion as were most of the log developers.

 

LotW are only interested in the fact that it was a DATA mode as that’s the category in DXCC awards.

 

Phil GM3ZZA

 

Sent from Mail for Windows

 

From: Rick Tavan
Sent: 30 August 2021 18:31
To: main@wsjtx.groups.io
Subject: Re: [WSJTX] MODE vs. SUBMODE for FT8 or FT4 #adiFiles #logging #FT4 #FT8

 

Thanks, Phil. Far be it from me to question the work of The Committee, regardless of inconsistencies and consequent obligations upon downstream developers. My loggers (N1MM, RUMlog, WSJT-X Windows, and WSJT-X MacOS) all display actual mode, translating correctly from the spec. But my all-QSOs database (DX4WIN) does not. It displays my digi QSOs as either FT8 or MFSK (with no sub-mode reported). I may have to edit all inbound logs manually before importing to DX4WIN but I'm trying to get more recent info on possible updates to that program - what I've found so far is discussion from 2019 showing that the problem was understood but nothing about any fix. And I wonder what will happen if I submit these Qs to LoTW. Any idea?

 

73,

 

/Rick N6XI

 

On Mon, Aug 30, 2021 at 7:02 AM Philip Rose via groups.io <gm3zza=btinternet.com@groups.io> wrote:

Rick,

 

When the ADIF committee were asked to add FT8 as a mode – it was rushed through and the MODE FT8 was added. When asked to add FT4, there was more notice and in line with ADIF 3 policy was added as MODE=MFSK and SUBMODE=FT4.

 

It’s up to your logger how it chooses to display the resultant MODE/SUBMODE to the user. ADIF is ONLY a data interchange format – unfortunately it is also human-readable.

 

73 Phil GM3ZZA

 

Sent from Mail for Windows

 

From: Rick Tavan
Sent: 29 August 2021 21:22
To: main@wsjtx.groups.io
Subject: [WSJTX] MODE vs. SUBMODE for FT8 or FT4 #adiFiles #logging #FT4 #FT8

 

It appears that ADIF files produced by WSJT-X say FT8 for FT8 and MFSK FT4 for FT4. Why the difference? I'm seeing this in ADIF files produced directly by WSJT-X and also ADIF files exported by N1MM Logger when interfaced to WSJT-X. 

 

I'm running experimental V2.5.0 with some K4 fixes. Is this a bug related to the experimental version? I'd prefer not to regress to 2.4 because 2.5.0 expires 8/31 and by then should have been replaced with a non-experimental version.

 

Thanks,

 

/Rick N6XI

 

--

--


Rick Tavan
Truckee and Saratoga, CA

 


--
73 Phil GM3ZZA



--

--


Rick Tavan
Truckee and Saratoga, CA

 


--
73 Phil GM3ZZA


locked Re: occasional FT8 no decode, new computer? #Windows10 #raspberryPi #decode

Jim-KM4JSI <KM4JSI@...>
 

I fix it. Some how my sound settings got changed in the laptop. I do need more horsepower and it’s being prepared for me and will be ready next week.

On Mon, Aug 30, 2021 at 8:25 PM RichardH <jrhoye@...> wrote:
Hi, Jim.  I had a different set of issues getting WSJT-X to work on my Optiplex 5050 (Dell) desktop, and after wrestling with it on and off for a couple of weeks, I threw in the towel and bought an inexpensive laptop to essentially dedicate to digital mode radio.  Reading between the lines in your posts, it looks like you may need more horsepower to handle tasks in addition to digi-mode radio so this may not be for you.

But just in case this provides at least a frame of reference, here's what I got from Dell's direct online store for about $400:  Dell Inspiron 5402, i3 chipset @3.0GHz, 4GB memory, 128GB SSD; O/S is Win10. The rig is an ICOM 7410.  This setup worked like a charm right out of the gate -- I've never had an issue 8 months and 3,500 FT8 contacts later.  There have been a few evenings where conditions were so good that the contacts were rolling in faster than I could log them -- classic one-armed paper hanger mode, so no decode latency as far as I can tell.  Running Dimension 4 (freeware) for time sync, also trouble free.  Also, I have a ham buddy with exactly the same laptop (rig is an ICOM 706) and he's had the same experience -- no issues.

You wouldn't want this machine for CPU pegging, processing intensive applications but for WSJT-X and basic computing tasks, it does just fine.  And the price is right.

73 and good luck getting to the promised land!

Dick
KK6LE



locked Re: error message program will not start #IssueReport

Michael Black
 

cd %LOCALAPPDATA%
ren WSJT-X WSJT-X.bak

Start WSJT-X and it will be a new configuration.

Or this will start a new config also.

cd \WSJT\wsjtx\bin
wsjtx -r test

See if either of those solve your problem.

Mike W9MDB




On Monday, August 30, 2021, 07:25:41 PM CDT, Dave Garber <ve3wej@...> wrote:


I had this error message show today while monitoring ft4. Wsjt quit (2.4.0)  but jtalert stayed running.  A trip to task manager and telling jt9 to end task let me restart wsjt.    

Hope thats sheds light.   Not sure why the error and shut down though

On Mon., Aug. 30, 2021, 10:23 a.m. Gwen, <gsw2@...> wrote:

That was what was happening to me  (and why I don't like Windows)


On 8/29/21 11:54 PM, Jim-KM4JSI wrote:
I started getting error messages and the now the program will not start. I have uninstalled it and delete the download and started over and still getting the same messages,

    







locked Re: occasional FT8 no decode, new computer? #Windows10 #raspberryPi #decode

RichardH
 

Hi, Jim.  I had a different set of issues getting WSJT-X to work on my Optiplex 5050 (Dell) desktop, and after wrestling with it on and off for a couple of weeks, I threw in the towel and bought an inexpensive laptop to essentially dedicate to digital mode radio.  Reading between the lines in your posts, it looks like you may need more horsepower to handle tasks in addition to digi-mode radio so this may not be for you.

But just in case this provides at least a frame of reference, here's what I got from Dell's direct online store for about $400:  Dell Inspiron 5402, i3 chipset @3.0GHz, 4GB memory, 128GB SSD; O/S is Win10. The rig is an ICOM 7410.  This setup worked like a charm right out of the gate -- I've never had an issue 8 months and 3,500 FT8 contacts later.  There have been a few evenings where conditions were so good that the contacts were rolling in faster than I could log them -- classic one-armed paper hanger mode, so no decode latency as far as I can tell.  Running Dimension 4 (freeware) for time sync, also trouble free.  Also, I have a ham buddy with exactly the same laptop (rig is an ICOM 706) and he's had the same experience -- no issues.

You wouldn't want this machine for CPU pegging, processing intensive applications but for WSJT-X and basic computing tasks, it does just fine.  And the price is right.

73 and good luck getting to the promised land!

Dick
KK6LE


locked Re: error message program will not start #IssueReport

Dave Garber
 

I had this error message show today while monitoring ft4. Wsjt quit (2.4.0)  but jtalert stayed running.  A trip to task manager and telling jt9 to end task let me restart wsjt.    

Hope thats sheds light.   Not sure why the error and shut down though

On Mon., Aug. 30, 2021, 10:23 a.m. Gwen, <gsw2@...> wrote:

That was what was happening to me  (and why I don't like Windows)


On 8/29/21 11:54 PM, Jim-KM4JSI wrote:
I started getting error messages and the now the program will not start. I have uninstalled it and delete the download and started over and still getting the same messages,






locked Re: MODE vs. SUBMODE for FT8 or FT4 #adiFiles #logging #FT4 #FT8

 

When I mentioned committee, that was a polite word for the blog collective. But it is obviously DX4WIN that is confusing you. How does DX4WIN display SSB contacts? Contact them about this matter.

 

LotW drove the immediate need to adopt FT8 as a mode as a lot of people were already uploading a lot of contacts. However LotW will record the current ADIF MODE/SUBMODE classification.

 

73 Phil GM3ZZA

 

Sent from Mail for Windows

 

From: Rick Tavan
Sent: 30 August 2021 18:31
To: main@wsjtx.groups.io
Subject: Re: [WSJTX] MODE vs. SUBMODE for FT8 or FT4 #adiFiles #logging #FT4 #FT8

 

Thanks, Phil. Far be it from me to question the work of The Committee, regardless of inconsistencies and consequent obligations upon downstream developers. My loggers (N1MM, RUMlog, WSJT-X Windows, and WSJT-X MacOS) all display actual mode, translating correctly from the spec. But my all-QSOs database (DX4WIN) does not. It displays my digi QSOs as either FT8 or MFSK (with no sub-mode reported). I may have to edit all inbound logs manually before importing to DX4WIN but I'm trying to get more recent info on possible updates to that program - what I've found so far is discussion from 2019 showing that the problem was understood but nothing about any fix. And I wonder what will happen if I submit these Qs to LoTW. Any idea?

 

73,

 

/Rick N6XI

 

On Mon, Aug 30, 2021 at 7:02 AM Philip Rose via groups.io <gm3zza=btinternet.com@groups.io> wrote:

Rick,

 

When the ADIF committee were asked to add FT8 as a mode – it was rushed through and the MODE FT8 was added. When asked to add FT4, there was more notice and in line with ADIF 3 policy was added as MODE=MFSK and SUBMODE=FT4.

 

It’s up to your logger how it chooses to display the resultant MODE/SUBMODE to the user. ADIF is ONLY a data interchange format – unfortunately it is also human-readable.

 

73 Phil GM3ZZA

 

Sent from Mail for Windows

 

From: Rick Tavan
Sent: 29 August 2021 21:22
To: main@wsjtx.groups.io
Subject: [WSJTX] MODE vs. SUBMODE for FT8 or FT4 #adiFiles #logging #FT4 #FT8

 

It appears that ADIF files produced by WSJT-X say FT8 for FT8 and MFSK FT4 for FT4. Why the difference? I'm seeing this in ADIF files produced directly by WSJT-X and also ADIF files exported by N1MM Logger when interfaced to WSJT-X. 

 

I'm running experimental V2.5.0 with some K4 fixes. Is this a bug related to the experimental version? I'd prefer not to regress to 2.4 because 2.5.0 expires 8/31 and by then should have been replaced with a non-experimental version.

 

Thanks,

 

/Rick N6XI

 

--

--


Rick Tavan
Truckee and Saratoga, CA

 


--
73 Phil GM3ZZA



--

--


Rick Tavan
Truckee and Saratoga, CA

 


--
73 Phil GM3ZZA


locked Re: Full duplex mode for Satellite operations #EnhancementReqest

Andy Talbot
 

Furthermore, on a reliable strong clean fade-free satellite link, there are far more suitable data modes than ones designed for weak signals and the HF environment with pre-formatted rubber stamps.

PSK31 would work well, as does JS8CALL.   Even RTTY if you want to go retro.


locked Re: #MAP65 3.0 stopped working, what to do? #map65

Bill Somerville
 

On 30/08/2021 19:18, Roger Shultz via groups.io wrote:
I've had MAP65 3.0 working nicely since it was first released
embedded in WSJT-X.

It has now stopped opening. When I click the shortcut, the
shortcut window opens but it now gray instead of the usual black.
The other MAP65 3.0 windows try to open except for the main window
then I get the error that MAP65 has working.

Normally I'd assume it has become corrupted, uninstall it and
reinstall then run the Zadig USB tool and hope for the best. 

Here's the problem. It seems when I look under Control Panel in
Windows 7 I see 4 versions of WSJT-X which has MAP65 embedded in
it. I have rc1, 2 3 and 5 showing. 

When I open X alone it only opens rc0 so I have no idea why it is
not opening rc5. 

Since WSJT-X rc0 will expire tomorrow August 31, what is going to
happen? Which versions do I uninstall? Will I lose the shortcuts
I've established to have two instances of WSJT-X and all the
configurations? 

And as I started this question, how do I fix MAP65 3.0?

73, Roger, NJ2R

Hi Roger,

there is a possibility that the audio device settings in the MAP65 settings file (map65.ini) get out of sync with the devices on your system. If you don't mind setting up from scratch you can simply delete the map65.ini file and restart MAP65, otherwise you can try editing the map65.ini file with a basic text editor like notepad.exe and delete the lines starting:

paInDevice=

and

paOutDevice=

73
Bill
G4WJS.

9841 - 9860 of 37978