Date   

locked Xeigu G90 // XPA125B amp // WSJT-X #transmit issue 40/30m #transmit

Mark Bell
 

Hello all. First off I'd like to thank the creators for the hours and hours of entertainment you've given me and others with the WSJT-X software! I love every aspect of this thing -- so seriously: Thank you!

I am writing today about an issue I am having with running FT8/FT4/other WSJT-X modes on 30m and 40m bands. This is an issue that just developed within the past few weeks for me, as previously I had been able to transmit on 30m and 40m no problem. 

My rig is the Xeigu G90 using the CE19 interface running into an external USB sound card on my HP Omen laptop running Windows 10, build 19043.1288 (21H1). I also use the XPA125B amplifier and tend to run FT8/FT4/others at around 35-50 watts depending upon band conditions. I use an Chameleon Emcomm III-B end-fed dipole with a MAT-TUNER mAT-125E external tuner. My SWR tends to hang around anywhere from 1.1 to 1.4 in normal conditions. I pair to WSJT-X using FLDigi and use CAT control. 

I still have no trouble operating on 10, 12, 15, 17, 20, 80 and 160, but over the past month I am unable to run more than 10w on 30 or 40 meters without the transmit immediately stopping on me. As soon as I start to increase power, I notice the SWR climbs to as high as 1.7. The amp is capable of running with SWR of up to 3.5 (know that isn't good for it though), but the transmit stops. I have also noticed power fluctuations of up to 70w when this happens. 

I have checked all connections and grounding and everything looks good. Antenna configuration is a half square on my roof and again this was working fine before this month. 

Any ideas what is happening? I am on the latest release of WSJT-X.


locked Re: new version 25 doesnt switch ic9100 to usb-d mode #Cat_RigControl #Icom

Bruce N7XGR
 

I can not understand what this problem really is because all three USB-D
filters can be adjusted to user preference.  Page 73 of the IC9100
user manual describes on how to adjust the filter widths.
In fact I prefer FIL2 because I have it adjusted to a wider setting.
Just follow the instructions on page 73 and all will be fine.
Also the regular 3 USB mode RX filters can be adjusted the same way.
Remember that since this 9100 does not have a SD card for saving
settings it is advised to write down all settings that have been changed
by the user.  Print out the SET mode pages out of the manual and make
your notations accordingly along with any TX and RX filter settings.

Bruce  N7XGR

On Fri, Oct 15, 2021 at 11:24 AM bob lee <ve3cga@...> wrote:
Hi Bill, well just about there.
the usb-d mode is now selected going into wsjtx
however the rig is put into filter 2 which really narrows the field of view
additionally it leaves the USB mode in filter#2 as version 24 does as I found out yesterday (below)

Running version 24 I never realized it (originally thought it had been previously set by me) but although it starts up just fine with usb-d mode & filter set at #1, when I exit and manually switch back out of data mode, whatever band was selected with wsjt-x is left in filter #2 even though wsjt-x ran in data mode with the filter set to filter #1.
In other words, with wsjtx exited, manually switching to usb mode the filter is now filter #2. Manually switching back to data mode shows filter #1 (good)

I dont know if the data mode ON cmd $FEFE7cE01A060101FD could be inserted into the 9100 configuration 
Different program but I have do this with mmsstv radio commands for each bands then I deselect, put mode back to USB with filter untouched: $FEFE7cE01A060000FD

From the manual pg 193:

 
I wonder if there is somewhere in the wsjtx files where I could insert these command strings

tnx Bob VE3CGA




locked Re: new version 25 doesnt switch ic9100 to usb-d mode #Cat_RigControl #Icom

Bruce N7XGR
 

I can not understand what this problem really is because all three USB-D
filters can be adjusted to user preference.  Page 73 of the IC9100
user manual describes on how to adjust the filter widths.
In fact I prefer FIL2 because I have it adjusted to a wider setting.
Just follow the instructions on page 73 and all will be fine.
Also the regular 3 USB mode RX filters can be adjusted the same way.
Remember that since this 9100 does not have a SD card for saving
settings it is advised to write down all settings that have been changed
by the user.  Print out the SET mode pages out of the manual and make
your notations accordingly along with any TX and RX filter settings.

Bruce  N7XGR


On Fri, Oct 15, 2021 at 11:45 AM bob lee <ve3cga@...> wrote:
Hi Bill, I sent a few minutes ago but it must have gone to cyberspace so I'll try again

I added the dll to ver25 and it does startup data mode (great) however the filter is changed to #2 position which is narrower

Yesterday I noticed after using ver 24 that is sets up fine  usb=d and filter #1 but after closing wsjtx and going back to just USB mode that the filter was selected as #2
I had noticed this before but thought I had selected it working SSB with some adjacent qrm

So when I use mmsstv I set it up in the menus to call the freq (not shown) and usb data mode FEFE7cE01A060101FD
I also setup a data mode off button for when I leave mmsstv FEFE7cE01A060000FD

I'm wondering if there is some place in the files where as wsjtx is initialized that the USB data mode command could be inserted
This was from the manual pg 193

I though of using a script or bat file but I think wsjtx would write over it with the usb-d with filter#2

thanks, Bob VE3CGA




locked Re: WARNING GPS u-blox driver and NTP #Windows10 #Timesync

Brad, K8ZM
 

What's even more fun is when windows swaps your driver for the GPS and makes it a mouse.  Try chasing it all over your screen as it moves with the GPS data stream.....hilarious !!

Brad, K8ZM

S10 "Not So" Smartphone


-------- Original message --------
From: "Jim Pennino via groups.io" <penninojim@...>
Date: 10/15/21 2:07 PM (GMT-05:00)
To: main@WSJTX.groups.io
Subject: [WSJTX] WARNING GPS u-blox driver and NTP #Windows10 #Timesync

In the latest Windows update an updated u-blox driver showed up, so I installed it.

Wrong move.

This driver causes the GPS receiver to show up as a sensor instead of a COM port which breaks NTP.

If you do this, you will have to go to sensors in device manager and remove the device AND the driver for it and restart to get NTP working again.


locked WARNING GPS u-blox driver and NTP #Windows10 #Timesync

Jim Pennino
 

In the latest Windows update an updated u-blox driver showed up, so I installed it.

Wrong move.

This driver causes the GPS receiver to show up as a sensor instead of a COM port which breaks NTP.

If you do this, you will have to go to sensors in device manager and remove the device AND the driver for it and restart to get NTP working again.


locked Re: new version 25 doesnt switch ic9100 to usb-d mode #Cat_RigControl #Icom

Michael Black
 

Just put in a patch that should re-use the existing filter if RIG_PASSBAND_NOCHANGE  is requested.

So at least once a filter is selected it should stick.

Mike W9MDB




On Friday, October 15, 2021, 10:55:46 AM CDT, Bill Somerville <g4wjs@...> wrote:


Mike,

WSJT-X always requests a mode change with no change in the filter settings. I know this is somewhat problematic with some Icom rigs that do not allow reading the filter settings on the SPLIT Tx VFO without swapping VFOs. Perhaps those that want to use the Icom default filter settings and can't be bothered to customize them as needed should be forced to put up with VFO swapping when changing modes in SPLIT, so Hamlib can read the current filter settings and honour the RIG_PASSBAND_NOCHANGE option by reading the current value to reuse just before setting the mode.

Note that WSJT-X always requests a mode switch (possible redundant) when setting the frequency, this will not change as it copes well with inadvertent operator mode changes via the front panel.

73
Bill
G4WJS.

On 15/10/2021 16:47, Michael Black via groups.io wrote:
I've gone back and forth with Icom several times....

Their default mode is filter 2 and I used to force it to filter 1.  I changed hamlib to let the rig default to whatever it wants and if Icom ever fixes that (not holding my breath) so that the filter follows the band stack then everybody will be happy.

Meanwhile you need to set filter 2 to your data mode wide filter.

My other choice is to do same as FLRig and "remember" whatever filter you select but hamlib currently doesn't try to remember anything so would be a significant change to having hamlib save a config file.

Mike W9MDB




On Friday, October 15, 2021, 10:24:58 AM CDT, bob lee <ve3cga@...> wrote:


Hi Bill, well just about there.
the usb-d mode is now selected going into wsjtx
however the rig is put into filter 2 which really narrows the field of view
additionally it leaves the USB mode in filter#2 as version 24 does as I found out yesterday (below)

Running version 24 I never realized it (originally thought it had been previously set by me) but although it starts up just fine with usb-d mode & filter set at #1, when I exit and manually switch back out of data mode, whatever band was selected with wsjt-x is left in filter #2 even though wsjt-x ran in data mode with the filter set to filter #1.
In other words, with wsjtx exited, manually switching to usb mode the filter is now filter #2. Manually switching back to data mode shows filter #1 (good)

I dont know if the data mode ON cmd $FEFE7cE01A060101FD could be inserted into the 9100 configuration 
Different program but I have do this with mmsstv radio commands for each bands then I deselect, put mode back to USB with filter untouched: $FEFE7cE01A060000FD

From the manual pg 193:

 
I wonder if there is somewhere in the wsjtx files where I could insert these command strings

tnx Bob VE3CGA






locked Re: MAP65 Installation #map65

Ian Morrison <ve7ai73@...>
 

Hi Joe
Thank you for your reply.

Linrad is set up to send tf2 at 96000 to the network.

Any thoughts on why my MAP65 installation only receives starting at the zero second to second six, does a decode and the receive shuts off until the next zero second?

The wide graph is only adding traces for six seconds.

73
Ian
VE7AI

On Fri, Oct 15, 2021 at 8:25 AM Joe <joe@...> wrote:
Hi Ian,

Behavior of the MAP65 files that you describe is exactly as it should be.  Xpol data files have extension .tf2 and are opened when Xpol is selected.  Single-polarization files are half as big, have the .iq extension, and are opened whan Xpol is not selected.

Opening a file causes MAP65 to read and decode the entire file.  Normally this takes just a few seconds.  A screenshot showing MAP65 after reading Xpol example file 061111_0745.tf2 is attached.  Seven EME signals are found and decoded.

  -- 73, Joe, K1JT



locked Re: Sample Files for FST4 #FST4

Joe N0NOW
 

Of course.   Thanks, Bill, both for your quick reply and your patience!

73,
Joe
N0NOW


locked Re: Sample Files for FST4 #FST4

Bill Somerville
 

On 15/10/2021 17:48, Joe N0NOW wrote:
I'm running WSJT-X 2.4.0 (on Ubuntu linux), installed as a update a year or so ago.  I have a neighbor running v. 2.5 on a Mac, also a recent update.  Both of us are curious about FST4.  We are following the documentation guidelines for setup and we cannot find the SAMPLES files to use for the demo and testing.  The SAMPLES directory opens properly, but it is empty.  Does updating WSJT-X not load sample files (that is, only the initial distribution does), or do I need to download samples as a separate step?  If so, where are they?

Thanks everyone. I know it's a dumb question.

Joe  N0NOW
Joe,

the WSJT-X User Guide has the answer to your query:

https://physics.princeton.edu/pulsar/k1jt/wsjtx-doc/wsjtx-main-2.5.0.html#DOWNLOAD_SAMPLES

73
Bill
G4WJS.


locked Sample Files for FST4 #FST4

Joe N0NOW
 

I'm running WSJT-X 2.4.0 (on Ubuntu linux), installed as a update a year or so ago.  I have a neighbor running v. 2.5 on a Mac, also a recent update.  Both of us are curious about FST4.  We are following the documentation guidelines for setup and we cannot find the SAMPLES files to use for the demo and testing.  The SAMPLES directory opens properly, but it is empty.  Does updating WSJT-X not load sample files (that is, only the initial distribution does), or do I need to download samples as a separate step?  If so, where are they? 

Thanks everyone. I know it's a dumb question.

Joe  N0NOW


locked Re: new version 25 doesnt switch ic9100 to usb-d mode #Cat_RigControl #Icom

Bill Somerville
 

Mike,

WSJT-X always requests a mode change with no change in the filter settings. I know this is somewhat problematic with some Icom rigs that do not allow reading the filter settings on the SPLIT Tx VFO without swapping VFOs. Perhaps those that want to use the Icom default filter settings and can't be bothered to customize them as needed should be forced to put up with VFO swapping when changing modes in SPLIT, so Hamlib can read the current filter settings and honour the RIG_PASSBAND_NOCHANGE option by reading the current value to reuse just before setting the mode.

Note that WSJT-X always requests a mode switch (possible redundant) when setting the frequency, this will not change as it copes well with inadvertent operator mode changes via the front panel.

73
Bill
G4WJS.

On 15/10/2021 16:47, Michael Black via groups.io wrote:
I've gone back and forth with Icom several times....

Their default mode is filter 2 and I used to force it to filter 1.  I changed hamlib to let the rig default to whatever it wants and if Icom ever fixes that (not holding my breath) so that the filter follows the band stack then everybody will be happy.

Meanwhile you need to set filter 2 to your data mode wide filter.

My other choice is to do same as FLRig and "remember" whatever filter you select but hamlib currently doesn't try to remember anything so would be a significant change to having hamlib save a config file.

Mike W9MDB




On Friday, October 15, 2021, 10:24:58 AM CDT, bob lee <ve3cga@...> wrote:


Hi Bill, well just about there.
the usb-d mode is now selected going into wsjtx
however the rig is put into filter 2 which really narrows the field of view
additionally it leaves the USB mode in filter#2 as version 24 does as I found out yesterday (below)

Running version 24 I never realized it (originally thought it had been previously set by me) but although it starts up just fine with usb-d mode & filter set at #1, when I exit and manually switch back out of data mode, whatever band was selected with wsjt-x is left in filter #2 even though wsjt-x ran in data mode with the filter set to filter #1.
In other words, with wsjtx exited, manually switching to usb mode the filter is now filter #2. Manually switching back to data mode shows filter #1 (good)

I dont know if the data mode ON cmd $FEFE7cE01A060101FD could be inserted into the 9100 configuration 
Different program but I have do this with mmsstv radio commands for each bands then I deselect, put mode back to USB with filter untouched: $FEFE7cE01A060000FD

From the manual pg 193:

 
I wonder if there is somewhere in the wsjtx files where I could insert these command strings

tnx Bob VE3CGA



locked Re: new version 25 doesnt switch ic9100 to usb-d mode #Cat_RigControl #Icom

Michael Black
 

I've gone back and forth with Icom several times....

Their default mode is filter 2 and I used to force it to filter 1.  I changed hamlib to let the rig default to whatever it wants and if Icom ever fixes that (not holding my breath) so that the filter follows the band stack then everybody will be happy.

Meanwhile you need to set filter 2 to your data mode wide filter.

My other choice is to do same as FLRig and "remember" whatever filter you select but hamlib currently doesn't try to remember anything so would be a significant change to having hamlib save a config file.

Mike W9MDB




On Friday, October 15, 2021, 10:24:58 AM CDT, bob lee <ve3cga@...> wrote:


Hi Bill, well just about there.
the usb-d mode is now selected going into wsjtx
however the rig is put into filter 2 which really narrows the field of view
additionally it leaves the USB mode in filter#2 as version 24 does as I found out yesterday (below)

Running version 24 I never realized it (originally thought it had been previously set by me) but although it starts up just fine with usb-d mode & filter set at #1, when I exit and manually switch back out of data mode, whatever band was selected with wsjt-x is left in filter #2 even though wsjt-x ran in data mode with the filter set to filter #1.
In other words, with wsjtx exited, manually switching to usb mode the filter is now filter #2. Manually switching back to data mode shows filter #1 (good)

I dont know if the data mode ON cmd $FEFE7cE01A060101FD could be inserted into the 9100 configuration 
Different program but I have do this with mmsstv radio commands for each bands then I deselect, put mode back to USB with filter untouched: $FEFE7cE01A060000FD

From the manual pg 193:

 
I wonder if there is somewhere in the wsjtx files where I could insert these command strings

tnx Bob VE3CGA




locked Re: new version 25 doesnt switch ic9100 to usb-d mode #Cat_RigControl #Icom

bob lee
 

Hi Bill, I sent a few minutes ago but it must have gone to cyberspace so I'll try again

I added the dll to ver25 and it does startup data mode (great) however the filter is changed to #2 position which is narrower

Yesterday I noticed after using ver 24 that is sets up fine  usb=d and filter #1 but after closing wsjtx and going back to just USB mode that the filter was selected as #2
I had noticed this before but thought I had selected it working SSB with some adjacent qrm

So when I use mmsstv I set it up in the menus to call the freq (not shown) and usb data mode FEFE7cE01A060101FD
I also setup a data mode off button for when I leave mmsstv FEFE7cE01A060000FD

I'm wondering if there is some place in the files where as wsjtx is initialized that the USB data mode command could be inserted
This was from the manual pg 193

I though of using a script or bat file but I think wsjtx would write over it with the usb-d with filter#2

thanks, Bob VE3CGA


locked Re: MAP65 Installation #map65

Joe
 

Hi Ian,

Behavior of the MAP65 files that you describe is exactly as it should be.  Xpol data files have extension .tf2 and are opened when Xpol is selected.  Single-polarization files are half as big, have the .iq extension, and are opened whan Xpol is not selected.

Opening a file causes MAP65 to read and decode the entire file.  Normally this takes just a few seconds.  A screenshot showing MAP65 after reading Xpol example file 061111_0745.tf2 is attached.  Seven EME signals are found and decoded.

  -- 73, Joe, K1JT


locked Re: new version 25 doesnt switch ic9100 to usb-d mode #Cat_RigControl #Icom

bob lee
 

Hi Bill, well just about there.
the usb-d mode is now selected going into wsjtx
however the rig is put into filter 2 which really narrows the field of view
additionally it leaves the USB mode in filter#2 as version 24 does as I found out yesterday (below)

Running version 24 I never realized it (originally thought it had been previously set by me) but although it starts up just fine with usb-d mode & filter set at #1, when I exit and manually switch back out of data mode, whatever band was selected with wsjt-x is left in filter #2 even though wsjt-x ran in data mode with the filter set to filter #1.
In other words, with wsjtx exited, manually switching to usb mode the filter is now filter #2. Manually switching back to data mode shows filter #1 (good)

I dont know if the data mode ON cmd $FEFE7cE01A060101FD could be inserted into the 9100 configuration 
Different program but I have do this with mmsstv radio commands for each bands then I deselect, put mode back to USB with filter untouched: $FEFE7cE01A060000FD

From the manual pg 193:

 
I wonder if there is somewhere in the wsjtx files where I could insert these command strings

tnx Bob VE3CGA


locked Re: my memory is failing... #NewUser

Reino Talarmo
 

Perhaps it was GridTracker.
73, Reino OH3mA

-----Original Message-----
From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of Bill Somerville
Sent: 15. lokakuutata 2021 17:05
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] my memory is failing... #NewUser

On 15/10/2021 14:29, Andrew Thall k2oo wrote:
I've been away from FT8 for a long time. Besides WSJT-x, I remember a
program that showed callsigns in a grid that ran at the same time --
but I can't remember the name of the program. Can you give me the
name of that program????
Thanks.
Andy, k2oo
Hi Andy,

if that is on MS Windows then you probably mean JTAlert.

73
Bill
G4WJS.


locked Re: my memory is failing... #NewUser

Bill Somerville
 

On 15/10/2021 14:29, Andrew Thall k2oo wrote:
I've been away from FT8 for a long time.  Besides WSJT-x, I remember a program that showed callsigns in a grid that ran at the same time --
but I can't remember the name of the program.  Can you give me the name of that program????
Thanks.
Andy, k2oo
Hi Andy,

if that is on MS Windows then you probably mean JTAlert.

73
Bill
G4WJS.


locked Re: my memory is failing... #NewUser

Michael Black
 

You thinking of JTAlert?


Mike W9MDB




On Friday, October 15, 2021, 08:59:50 AM CDT, Andrew Thall k2oo <thall@...> wrote:


I've been away from FT8 for a long time.  Besides WSJT-x, I remember a program that showed callsigns in a grid that ran at the same time -- but I can't remember the name of the program.  Can you give me the name of that program????
Thanks.
Andy, k2oo




locked my memory is failing... #NewUser

Andrew Thall k2oo
 

I've been away from FT8 for a long time.  Besides WSJT-x, I remember a program that showed callsigns in a grid that ran at the same time -- but I can't remember the name of the program.  Can you give me the name of that program????
Thanks.
Andy, k2oo


locked Re: MAP65 Installation #map65

Ian Morrison <ve7ai73@...>
 

Hi Bill

Checked the configuration several times all seems good.

Did an uninstall and a fresh download and copied the demo files.

The first is an iq type file of 19 MB and can only be selected if x pol is set.

The second is a tf2 type file of 38 MB and can only be selected by MAP65 if x pol is not set (single polarization)

Both files run for a few seconds and stop. The wide spectrum advances but no signals are visible.

Have you tried these files with MAP65 3.0 ?

73
Ian

On Thu, Oct 14, 2021 at 3:55 AM Bill Somerville <g4wjs@...> wrote:
Hi Ian,

the "Decode" button should turn cyan for a second or more at around seconds 51 and 57 of the minute (depends on the modes selected). The correct timing of the decoder activity also depends on the correct sample rates being selected, are you you using the default 96000 rate, and does that match the rate that Linrad is sending I/Q data at? Do you have the MAP65 Xpol setting set correctly for your system?

73
Bill
G4WJS.

On 14/10/2021 11:47, Ian Morrison wrote:
Hi Bill

I have not yet seen a MAP65 operating normally. What time does the decode light normally blink?
Does the decode light blink even if a decode is not likely? Is the decoder solely time initiated?
Any bit of information will give me a direction to snoop.

73
Ian 

On Thu, Oct 14, 2021 at 3:22 AM Bill Somerville <g4wjs@...> wrote:
Hi Ian,

yes that may be a clue, but I have no idea what is happening. Perhaps a conversation with one of the other EME ops using Linrad as a source for MAP65 may help discover what is different about your system.

73
Bill
G4WJS.

On 13/10/2021 23:36, Ian Morrison wrote:
Hi Bill
The timing is curious isn't it?
Always starts receiving at the zero second of the minute and stops at seven seconds.

73
Ian

On Wed, Oct 13, 2021 at 2:40 PM Bill Somerville <g4wjs@...> wrote:
On 13/10/2021 22:30, Ian Morrison wrote:
> Hi Bill
> I moved the UDP port in Linrad back to 50004 instead of taking Linrads
> assignment and get the same result.
> also did a restart same result. This windows 10 PC is brand new and
> has no other software loaded but Windows 10, Linrad and WSJT-X with
> MAP65 3.0.
> Used netstat -ab to check who is using what ports and found Edge may
> be using 50024.
> The end of the 7 seconds shows a decode light but the rx stays off
> until the next minute zero.
>
> 73 Ian

Hi Ian,

I doubt Edge is using UDP on any port so that is not an issue, TCP and
UDP are separate.

The only requirement on port numbers is that whatever you set in the
MAP65 settings for the port to listen on (default is 50004) must be the
same port you have Linrad sending on. Whichever port being used will
have to be opened on the Windows machine firewall for incoming UDP
traffic to MAP65.

Ephemeral ports are granted to processes on some internal basis by the
operating system, a restart should always sort out any issues where the
o/s has granted a port you want to use to another process.

So I am not sure what is happening. Other MAP65 users are able to use
Linrad to feed I/Q data to MAP65 so it would appear to be something
specific to your machine.

73
Bill
G4WJS.





7541 - 7560 of 36726