Re: [wsjt-devel] Changed to a new PC running Windows 11, now nothing works.

[Peter Sumner via wsjt-devel]

Hello David,
 have you installed one of the heavy handed security packages like Norton
to the PC ?  I have seen people caught up in problems where their
connections are deemed unsafe if the USB chip in the serial port is one of
the old Prolific 'pirated' devices.  Just a thought as you might be chasing
a ghost that is working against your best interests.

Regards,
Peter, vk5pj

On Wed, May 1, 2024 at 8:30 PM davidinlondon--- via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:

> Thanks NicI've probably made it all worse for the pc by trying both
> direct usb in from the rig and then usb in from the microham.  Lost the
> direct virtual comport and the microham program also won't now connect via
> usb.  Maybe optical in from the rig might be a possibility.
>
> Regards David G5HY
>
> Sent via BT Email App
>
>
> From: Nic Sears via wsjt-devel 
> Sent: 1 May 2024 11:14:04 BST
> To: WSJT software development 
> Cc: Nic Sears 
> Subject: Re: [wsjt-devel] Changed to a new PC running Windows 11, now
> nothing works.
>
> Hi David, I got caught out when I moved to windows 11. A number of the
> audio menus have options that are off the bottom of the screen which, due
> to the way it displays, are not obvious that they exist.
>
> Suggest you check this out.
>
> Rgds, Nic G3YEG
>
>
>
> On 1 May 2024 10:57, davidinlondon--- via wsjt-devel <
> wsjt-devel@lists.sourceforge.net> wrote:
>
> Thanks Charles, deleting that cleared wsjt-x OK.  Still can't get it to
> work via my microham III or via a direct USB connection into the rig.  I
> don't understand why it gradually became more unstable over some weeks.
> Wasn't as bad under W10.
>
> At this rate I may end up actually talking to people rather than using
> data!
>
>
>
>
> Sent via BT Email App
>
>
> From: Charles Suckling via wsjt-devel 
> Sent: 30 April 2024 19:50:40 BST
> To: WSJT software development 
> Cc: Charles Suckling 
> Subject: Re: [wsjt-devel] Changed to a new PC running Windows 11, now
> nothing works.
>
> Hi David
>
> Is a file called WSJT-X.ini.  Its usually in a path similar to
> C:\Users\User\AppData\Local\WSJT-X   .  You may not be able to see the
> AppData folder as on some systems it is hidden and you need to unhide it.
>
> 73
>
> Charlie DL3WDG
>
> On Tue, 30 Apr 2024 at 20:35, davidinlondon--- via wsjt-devel <
> wsjt-devel@lists.sourceforge.net> wrote:
>
> Having just changed to a new PC running Windows 11, now nothing works.
>
>
>
> I'll take the issues one at a time.
>
>
>
> For this post my question is...I've tried deleting WSJT-X 2.6.1 from my PC
> several times, even using "IOBit Uninstaller", to try to clear it, but when
> I download a fresh 2.6.1 from Sourceforge and run it, it still shows all my
> personal details, call etc., from the previous installations.  Somewhere
> there must be a hidden "details" file that isn't being deleted.  Any ideas
> where I can look?
>
>
>
> Thanks
>
>
>
> David G5HY
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
> --
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
>
> --
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] changes to the on screen display in WSPR mode

[Peter Sumner via wsjt-devel]

Hello Development team,
 this may seem like a cosmetic request but I have what i feel is a valid
reason (I bet we all say that).

I run a few dedicated WSPR setups here in VK5 on the VHF bands, some times
it can be days between decodes and with just the onscreen data showing only
the ZULU time in the left hand column it requires me to open the log file
to see when that decode happened.

Now I ask this ONLY for the WSPR display mode, which is different to all
the others so it should have a minimal roll on effect, could the Julian day
number be put to the left of the ZULU time in the WSPR screen display, so
instead of the current format (shown below)

2328  -20   0.2   50.2945100   VK7DC QE28 47931

we could have this instead:

123 2328  -20   0.2   50.2945100   VK7DC QE28 47931

I chose the Julian day for this request as it has a small 3 character foot
print for the display, as I know there are some who are short on screen
space and it can be readily converted to the current date via many online
resources.  I am not asking for any other portion of the reporting, logging
functions to change as I know many have add-on programs already in use,
just what is shown on-screen. Modes like FT8, JT65 and Q65 are all based
around users interacting with the software, where as WSPR mode is all about
long term trends and making use of surprises :-)

I hope this request finds you all well and ready for the coming
christmas season.

Regards,
Peter, vk5pj
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] spots to WSPRnet stop from a RaspPi

[Peter Sumner via wsjt-devel]

Thanks Mike,
I have forgotten about TCPdump...  yes wireshark only good on a local host
these days, or if I am at work on Cisco gear I can mirror a port :-)

Regards,
Peter

On Fri, Jun 2, 2023 at 9:55 PM Black Michael via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:

> You would run tcpdump on the PI.  You cannot watch one computer's network
> traffic from another computer using wireshark.   Everybody uses a switch
> now and the cheap switches do not have a monitoring capability (sometimes
> referred to as an aggregation port).  You can only see your own traffic.
>
> Mike W9MDB
>
>
>
>
>
>
>
>
> On Friday, June 2, 2023 at 06:04:08 AM CDT, Peter Sumner via wsjt-devel <
> wsjt-devel@lists.sourceforge.net> wrote:
>
>
>
>
>
> Hello Alex,
>  all other web related activities like web browsing, system update, NTP
> and the like remain functional through the whole time, it appears to be on
> traffic from WSJT-X that suffers.
>
> Each of the PI's run as a headless devices and all checks are done over
> VNC, which is quite sensitive to any network problems.
>
> Regards,
> Peter, vk5pj
>
> On Fri, Jun 2, 2023 at 4:37 PM Alex Lelievre via wsjt-devel <
> wsjt-devel@lists.sourceforge.net> wrote:
> > Have you tried running WireShark on another machine and watching the
> traffic?  Perhaps all the traffic dies and not just WSPRnet?
> >
> > alex
> > K6LOT
> >
> >> On Jun 1, 2023, at 10:03 PM, Peter Sumner via wsjt-devel <
> wsjt-devel@lists.sourceforge.net> wrote:
> >>
> >> Hello,
> >> while WSJT-X is a small part of this puzzle, it is a key one so hence I
> am posting this here. I have for a long time now been using WSJT-X (v1.8
> right through to the current release for ARM v2.61 ) on a Raspberry Pi for
> a dedicated WSPR station with two Icom rigs on VHF. Over time both the Pi3
> and Pi4 have been used along with tests with the Raspberry Pi 32 and 64 bit
> O/S.  Each of these configurations have been quite stable with the
> exception of the spots and status on WSPRnet just stop getting through.
> >>
> >> On the last incarnation of my setup I actually loaded one of the
> popular firewall packages (UFW) thinking I could then be exact by defining
> the allowed apps and ports for WSJT-X to get to WSPRnet. All was good for a
> few weeks then back to the no spots and no status on WSPRnet.
> >> A reboot of the PI brings things back to life for a period of time
> (seems to vary) but in the end my status and spot on WSPRnet stop appearing.
> >> Looking to see if anyone has come across anything similar or any good
> pointers on what might be wrong at my end?
> >>
> >> have looked for ways to set the WSJT-X syslogs to be more granular but
> no luck so far
> >>
> >> Regards,
> >> Peter, vk5pj
> >> ___
> >> wsjt-devel mailing list
> >> wsjt-devel@lists.sourceforge.net
> >> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> >
> >
> >
> > ___
> > wsjt-devel mailing list
> > wsjt-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> >
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] WSPR display feature request

[Peter Sumner via wsjt-devel]

Hello to you all,
 this might not be favoured by all but give the idea a chance,  on the WSPR
decode window, the UTC time is shown in the left most column, could this
field be augmented with the Julian day of the year also? for those who do
not know what the Julian day is, simply its the day number since Jan 1st
each year, so Dec 31 would be Julian day 365 and Jan 1st is Julian day 001

so instead of this:

1118  -12   0.2   50.2945480   VK5GF PF94 40102
2048  -21   0.1   50.294534   -3   VK2XDGQF56 47   1114

it could look like this:

127 1118  -12   0.2   50.2945480   VK5GF PF94 40102
127 2048  -21   0.1   50.294534   -3   VK2XDGQF56 47   1114

The reason I ask this is that my 3 WSPR stations run continuously on bands
that can be dead for days at a time, having the Julian day (or some other
date formatted number) ahead of the UTC time will easily show what day each
of the spots relate to without having to open the WSPR log file.

I fully realise there may be some compatibility issues but as the WSPR
display is normally a single wide payne fitting in the extra 4 characters
(yes accounting for the space) should not be a burden on display space.

Regards,
Peter, vk5pj
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] spots to WSPRnet stop from a RaspPi

[Peter Sumner via wsjt-devel]

Hello Alex,
 all other web related activities like web browsing, system update, NTP and
the like remain functional through the whole time, it appears to be on
traffic from WSJT-X that suffers.

Each of the PI's run as a headless devices and all checks are done over
VNC, which is quite sensitive to any network problems.

Regards,
Peter, vk5pj

On Fri, Jun 2, 2023 at 4:37 PM Alex Lelievre via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:

> Have you tried running WireShark on another machine and watching the
> traffic?  Perhaps all the traffic dies and not just WSPRnet?
>
> alex
> K6LOT
>
> > On Jun 1, 2023, at 10:03 PM, Peter Sumner via wsjt-devel <
> wsjt-devel@lists.sourceforge.net> wrote:
> >
> > Hello,
> > while WSJT-X is a small part of this puzzle, it is a key one so hence I
> am posting this here. I have for a long time now been using WSJT-X (v1.8
> right through to the current release for ARM v2.61 ) on a Raspberry Pi for
> a dedicated WSPR station with two Icom rigs on VHF. Over time both the Pi3
> and Pi4 have been used along with tests with the Raspberry Pi 32 and 64 bit
> O/S.  Each of these configurations have been quite stable with the
> exception of the spots and status on WSPRnet just stop getting through.
> >
> > On the last incarnation of my setup I actually loaded one of the popular
> firewall packages (UFW) thinking I could then be exact by defining the
> allowed apps and ports for WSJT-X to get to WSPRnet. All was good for a few
> weeks then back to the no spots and no status on WSPRnet.
> > A reboot of the PI brings things back to life for a period of time
> (seems to vary) but in the end my status and spot on WSPRnet stop appearing.
> > Looking to see if anyone has come across anything similar or any good
> pointers on what might be wrong at my end?
> >
> > have looked for ways to set the WSJT-X syslogs to be more granular but
> no luck so far
> >
> > Regards,
> > Peter, vk5pj
> > ___
> > wsjt-devel mailing list
> > wsjt-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
>
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] spots to WSPRnet stop from a RaspPi

[Peter Sumner via wsjt-devel]

Hello,
while WSJT-X is a small part of this puzzle, it is a key one so hence I am
posting this here. I have for a long time now been using WSJT-X (v1.8 right
through to the current release for ARM v2.61 ) on a Raspberry Pi for a
dedicated WSPR station with two Icom rigs on VHF. Over time both the Pi3
and Pi4 have been used along with tests with the Raspberry Pi 32 and 64 bit
O/S.  Each of these configurations have been quite stable with the
exception of the spots and status on WSPRnet just stop getting through.

On the last incarnation of my setup I actually loaded one of the popular
firewall packages (UFW) thinking I could then be exact by defining the
allowed apps and ports for WSJT-X to get to WSPRnet. All was good for a few
weeks then back to the no spots and no status on WSPRnet.
A reboot of the PI brings things back to life for a period of time (seems
to vary) but in the end my status and spot on WSPRnet stop appearing.
Looking to see if anyone has come across anything similar or any good
pointers on what might be wrong at my end?

have looked for ways to set the WSJT-X syslogs to be more granular but no
luck so far

Regards,
Peter, vk5pj
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X app list issue - confirmed repeatable

[Peter Sumner via wsjt-devel]

Hello Alan,
 to avoid running the installer all together, you can use the '7ZIP'
utility to uncompress the WSJT-X package EXE file straight into a folder on
the PC, yes it works.  This is the path I have taken, it allows me to have
many and varied copies of WSJT-X on a PC and no entries in the installed
apps catalogue of Windows or entries in the system registry.

Once the files have been extracted, you can go to the 'Bin' sub folder,
right click on the WSJT-X.EXE and select create shortcut if you need a
dedicated shortcut to start each copy (give each shortcut you create a
meaningful name).

Regards,
Peter, vk5pj




On Sun, Jan 1, 2023 at 2:39 AM Alan Groups via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:

> Last post on this issue.
>
>- I cleaned ap again, and installed version 2.5.3 into a wsjtx253
>folder, then version 2.5.4 into a wsjtx254 folder
>- That worked, apart from some initial "stale lock file" complaints
>that went away on retry.  The Start Menu entry for 2.5.3 started that
>version and the entry for 2.5.4 started that one
>- The 2.5.4 entry was missing the Start Menu entries for uninstaller,
>documentation and website, but the latter two appeared on their own when I
>uninstalled 2.5.3 from Settings>Apps and Features
>- The uninstaller for 2.5.4 nevertheless worked when I did so from
>Settings>Apps and Features
>
> Maybe something like that is all that's necessary to clear this one up -
> the installer to suggest a different default folder for each version?
>
> Alan G0TLK
>
> On 31/12/2022 13:46, Alan Groups via wsjt-devel wrote:
>
> Following a system clean-up I've looked a bit further into the weird menu
> and other entries I found on my system and found the same effects arising
> on version upgrade, so it's a repeatable issue:
>
> *The Uninstaller*
>
>- Following a system clean of WSJT-X, installation of v 2.5.4 and
>after a reboot I uninstalled WSJT-X 2.5.4 using the uninstal link under the
>Start button - it runs uninstal.exe
>- WSJT-X went from the Start menu, the W10 apps list, Control
>Panel>Programs & Features, and the registry
>- The uninstaller therefore seems to be doing it's job, if run.
>
> *Version upgrade*
>
> I then installed version 2.5.3 and rebooted, followed by an upgrade to
> version 2.5.4 by simply running the latter installer.  This gave me:
>
>- Start Menu - one entry labelled 2.5.3 that actually runs 2.5.4
>- Registry - two entries, for each of 2.5.3 and 2.5.4
>- Control Panel>Programs & Features - two entries in the list, one for
>2.5.3 and one for 2.5.4, both uninstalling only 2.5.4
>- Settings>Apps & Features - same as Control Panel
>
> The system entries are therefore incorrect, leading to user confusion and
> for all I know potential W10 system issues as well.
>
> *Diagnosis*
>
> I don't believe the installer is running the working uninstal.exe nor is
> it cleaning up system entries from the previous version, when a new version
> is installed over the top of an existing version
>
> *Suggested solutions*
>
>- Advise users to run the uninstaller first, before version upgrading;
>or
>- Incorporate minimum necessary system entry clean-up into the
>installer script; or
>- If an ability to run multiple versions on one machine is required
>then amend the installer script so that it handles the system entries to
>have each version remaining entirely separate
>
> Hope that helps!
>
> Alan G0TLK
>
>
>
>
> ___
> wsjt-devel mailing 
> listwsjt-devel@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] edit the default template for CQ callsign Grid

[Peter Sumner via wsjt-devel]

Hello,
  a lot of my time is spent on 50 MHz looking for contacts out of my local
area, the locals seem to want to call me each day, just because they can.
I usually change the TX 6 line to be "CQ DX VK5PJ PF95" to discourage the
locals from calling me but often get caught out when the default format
overwrites my preferred TX6 line.
Is there any way for an end user to change this template without a
recompile from source on Windows 10 ?

Regards,
Peter, vk5pj
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] FW: 2.6.0 RC and HamRadioDeluxe Radio issue

[Peter Sumner via wsjt-devel]

Hello Alan,
 there is one thing you should keep in mind before making your final
decision, there are limits on the number of endpoint devices for both USB2
and USB3 and these total-up on a per controller bassis, you can see each
USB Controller in Windows Device manager. These endpoints include the
serial ports, sound devices, mice and keyboard we all seem to accumulate.

In general while USB 3 is considered to be the fast and logical option for
most things, it can have far fewer endpoint devices connected than its
slower USB 2 cousin.  If you google the term "Not Enough USB Controller
Resources" you will start to understand what the limits are and ways to
check your system.

I see this USB problem regularly when my Elad FMDUO is connected to its own
mini desktop PC and that's just three USB leads, as the DUO has a tonne of
internal endpoints that are presented to Windows so I have distribute the
leads across USB2 at the rear, USB2 on the front and USB3 to get everything
to play.

Wish you the best of luck with your setup,
regards,
Peter, vk5pj



On Mon, Nov 28, 2022 at 3:43 PM Alan McDonald via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:

> OK it's been 2d since my last setup alteration and I have not experienced
> any TX dropout.
>
> I moved my radio to another USB port type 3.0. (as opposed to a non 3.0
> speed type)
> I can confirm at least on my setup, that there is no longer an issue with
> dropping Tx audio. The HamRadioDeluxe radio + USB Codecs are now solid and
> Tx does not drop out.
>
>
> I have even reinstated the sleep to “enabled” on all devices and still
> there are no dropouts.
>
>
> So, in my experience, this is not something to do with ports "sleeping",
> it's all to do with USB port speed. I suspect that having CAT + 2way Audio
> feeds + switching, on one port, is more demanding than a normal USB can
> handle.
>
>
>
> It’s nice to be able to leave the HamRadioDeulxe rig control ON and open
> and close WSJT-X without having to shut things down and start them up again.
>
>
>
> Thanks for your patients and assistance. This was a rather long series of
> changes and testing periods in all this. But it’s a nice feeling to have it
> sorted.
>
>
>
> Alan McDonald
>
> Worimi Country
>
>
>
> *From:* Black Michael via wsjt-devel 
> *Sent:* Wednesday, 23 November 2022 4:02 PM
> *To:* Alan McDonald via wsjt-devel 
> *Cc:* Black Michael 
> *Subject:* Re: [wsjt-devel] FW: 2.6.0 RC and HamRadioDeluxe Radio issue
>
>
>
> On my Windows 11 desktop it has it.
>
>
>
> [image: Inline image]
>
>
>
>
>
>
>
>
>
> On Tuesday, November 22, 2022 at 04:57:06 PM CST, Alan McDonald via
> wsjt-devel  wrote:
>
>
>
>
>
> I'm not using a laptop with a battery. These settings, as you describe,
> are not available on a mains power PC
>
> Alan McDonald
> Worimi Country
> 0413 657 427
>
> -Original Message-
> From: Glenn Williams via wsjt-devel 
> Sent: Wednesday, 23 November 2022 12:12 AM
> To: wsjt-devel@lists.sourceforge.net
> Cc: Glenn Williams 
> Subject: Re: [wsjt-devel] FW: 2.6.0 RC and HamRadioDeluxe Radio issue
>
> I thought I remembered something about USB ports.
>
> I googled:  "windows 10 USB ports randomly stop working"
>
> and got
>
> "Go to Power Options > Change Plan Settings > Change advanced power
> settings. Find USB Settings, then drill down to USB selective suspend
> setting. Disable the options next to On battery and Plugged in, then click
> Apply. You must then restart your PC to stop it from turning off the USB
> ports unnecessarily."
>
> ---Glenn, AF8C
>
> On 11/22/2022 1:27 AM, Alan McDonald via wsjt-devel wrote:
> > OK so I’ve been running standard V2.5.4, IC-7300 on COM6
> >
> > I have made further observations.
> >
> > I have all the devices I can find set to not sleep.
> >
> > After leaving WSJT-X running for a while, I often come back to find it
> > won’t transmit. It is still decoding fine.
> >
> > (as reported before using the HamRadioDeluxe radio)
> >
> > I tried quite a few things to make it come back to Txing other than
> > exit/restart cycling.
> >
> > I have found that going to Settings|Audio|Output and selecting
> > something other than (3-USB etc) e.g.
> >
> > Then re-selecting 3_USB
> >
> > My tx comes back into operation.
> >
> > I also tried moving my USB cable over to another port on the PC but
> > this makes no difference other than changin from say 2-USB to 3-USB etc.
> >
> > Alan McDonald
> >
> > Worimi Country
> >
>
> --
> This email has been checked for viruses by Avast antivirus software.
> www.avast.com
>
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
>
>
>
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net

Re: [wsjt-devel] FW: 2.6.0 RC and HamRadioDeluxe Radio issue

[Peter Sumner via wsjt-devel]

Hi Alan,
 I am afraid you will have to get used to this happening (No TX audio),
anytime a Windows PC sees a sound device come or go it reshuffles the audio
device ID assignments and you end up in the situation you see now.   I have
a HDMI connected monitor that has a sound device inbuilt. Turning it on /
off used to cause me grief as the USB sound reshuffle would occur (I went
to device manager and disabled that sound device associated with the
monitor) and immediately saw an improvement in reliability.   For reasons
unknown it appears to mostly impact the OUTPUT (Speaker devices) and the
desired TX audio path ends up going to a random output device.  If you're
lucky it goes to the default speakers and you get alerted by the WSJT audio
coming out the speakers, otherwise you just get no TX power : -(  which is
frustrating as I run my shack over VNC from the house PC quite often and
have no visibility of any of my normal power meters (job for the future).
then wonder why no one is responding on FT8 when I call.

I have three ICOM rigs connected full time to the shack PC and they all
have random events of no TX audio, it seems it is the price we have to
pay.  Have tried every flavor of WSJT-X and its clones, all have the same
problem so it is either just a windows thing or something buried in the
code libraries of the frameworks used to create the package (no direct
knowledge, just my best guess)

Has anyone ever experimented with disabling the Plug-n-Play service in
Windows?

regards,
Peter, vk5pj

On Wed, Nov 23, 2022 at 9:27 AM Alan McDonald via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:

> I'm not using a laptop with a battery. These settings, as you describe,
> are not available on a mains power PC
>
> Alan McDonald
> Worimi Country
> 0413 657 427
>
> -Original Message-
> From: Glenn Williams via wsjt-devel 
> Sent: Wednesday, 23 November 2022 12:12 AM
> To: wsjt-devel@lists.sourceforge.net
> Cc: Glenn Williams 
> Subject: Re: [wsjt-devel] FW: 2.6.0 RC and HamRadioDeluxe Radio issue
>
> I thought I remembered something about USB ports.
>
> I googled:   "windows 10 USB ports randomly stop working"
>
> and got
>
> "Go to Power Options > Change Plan Settings > Change advanced power
> settings. Find USB Settings, then drill down to USB selective suspend
> setting. Disable the options next to On battery and Plugged in, then click
> Apply. You must then restart your PC to stop it from turning off the USB
> ports unnecessarily."
>
> ---Glenn, AF8C
>
> On 11/22/2022 1:27 AM, Alan McDonald via wsjt-devel wrote:
> > OK so I’ve been running standard V2.5.4, IC-7300 on COM6
> >
> > I have made further observations.
> >
> > I have all the devices I can find set to not sleep.
> >
> > After leaving WSJT-X running for a while, I often come back to find it
> > won’t transmit. It is still decoding fine.
> >
> > (as reported before using the HamRadioDeluxe radio)
> >
> > I tried quite a few things to make it come back to Txing other than
> > exit/restart cycling.
> >
> > I have found that going to Settings|Audio|Output and selecting
> > something other than (3-USB etc) e.g.
> >
> > Then re-selecting 3_USB
> >
> > My tx comes back into operation.
> >
> > I also tried moving my USB cable over to another port on the PC but
> > this makes no difference other than changin from say 2-USB to 3-USB etc.
> >
> > Alan McDonald
> >
> > Worimi Country
> >
>
> --
> This email has been checked for viruses by Avast antivirus software.
> www.avast.com
>
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
>
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] V2.5.4 Auto Seq Issue

[Peter Sumner via wsjt-devel]

Hi Marty, it may help if you indicate what exact mode your are using ? FT8
Q65 or one of the others? Also at what point does it not progress?

Regards.
Peter, vk5pj

On Sun, Sep 25, 2022, 12:24 Marty Wayne via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:

> When using WSJTx 2.5.4, the auto sequencer frequently does not auto step
> to next TX.  Using V2.5.2, everything works dine.
>
> Radio: Yaesu FT-1000MP
> Comp: MacBook Pro
> Processoe: 2.8 GHz Quad Core Intel Core i7
> Memory: 16 GB 2133 MHz LPDDR3
> Graphics: Intel HD Graphics 630 1536 MB
>
> Any thoughts?
>
> 73,
>
> Marty, W6NEV
> _ . .   .   . _ _   _ . . . .   _ .   .   . . . _
> mcway...@comcast.net
> 408-234-8023
>
>
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] disable PSKreporter functions unless CAT control is active.

[Peter Sumner via wsjt-devel]

Hi Phillip,
 It would be nice if the problem could be reduced at the source of the spot
then there is less complexity needed upstream.  My thought is the
PSKreporter option in WSJT-X can only be enabled if CAT is defined, this
might filter some of the chaff from the wheat when it comes to spots before
it gets to upstream services like PSKreporter.  (by the way I am a Big fan
of your work Phillip)

Another avenue where CAT is not mandatory, might be for WSJT-X to include a
'quality' value with each spot when it is sent from WSJT-X to PSKreporter
that identifies those spots coming from a CAT controlled station and those
from non CAT stations, this could be used as a weighting factor when
looking for bad spots. That I am guessing would need to be a collaboration
between yourself and the DEV team as to how it was implemented.  The down
side would be the sheer weight of old software out there that would still
be sending spots.

Thanks for your input.

Regards,
Peter, vk5pj

On Tue, Aug 16, 2022 at 11:00 AM Philip Gladstone via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:

> pskreporter has an algorithm to identify and filter out most of those bad
> spots. However, this can only happen once confirming/disconfirming spot
> reports arrive from other monitoring stations. Thus HamSpots will be passed
> these bad spots before pskreporter can figure out that they are bad.
>
> Philip
>
> On Mon, Aug 15, 2022 at 8:01 PM Laurie, VK3AMA via wsjt-devel <
> wsjt-devel@lists.sourceforge.net> wrote:
>
>>
>>
>> On 16/08/2022 9:52 am, Laurie, VK3AMA via wsjt-devel wrote:
>> >
>> > HamSpots has a couple of thousand callsigns that have their spots
>> > permanently blocked because of repeated occurrences of wrong-band
>> > spotting by the callsign
>>
>> I neglected to add, that the majority of those habitual wrong-band
>> spotters spots are entering HamSpots via the PSKReporter spot feed.
>>
>> de Laurie VK3AMA
>>
>>
>>
>> ___
>> wsjt-devel mailing list
>> wsjt-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] disable PSKreporter functions unless CAT control is active.

[Peter Sumner via wsjt-devel]

Hello.
  I would like to see the PSKreporter functionality in WSJT-X be restricted
to situations where the CAT control of the rig is active.

Why?  oh too often many of us have seen 'false spots' from a busy band
appearing on what is a very quiet band via PSKreporter because an OP
somewhere has changed bands on the rig but not on WSJT-X.

I realise this will raise the ire of some who never use CAT control but I
would at least like the group to consider what could be done to improve the
current situation and allow PSKreporter to have reliable information and
not be repeatedly polluted by false spots like it is now.

Regards,
 Peter, vk5pj
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Hamlib testing

[Peter Sumner via wsjt-devel]

Hello Jarmo,
 when 'rig' or 'fake-it' is enabled the transmit frequency is moved to
improve the location of your TX tones. As a test, try changing your TX
baseband freq to say 200 Hz and set TX on, note the TX VFO frequency, then
move baseband TX to 2300Hz and repeat, I would bet that you will see the
are different frequencies offset on the TX vfo.   For me I only use fake-it
where the main VFO gets moved when I go to TX and it then comes back when I
receive, it's all done to fight audio harmonics in the TX chain and defeat
those masty images across our waterfall of people who unwittingly overdrive
things.

Regards,
Peter, vk5pj

On Thu, Jun 2, 2022 at 1:18 PM jarmo via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:

> Wed, 1 Jun 2022 16:13:42 + (UTC)
> Black Michael via wsjt-devel 
> kirjoitti:
>
> Tested, but don't  understand behaviour? Why freq goes -500 Hz when
> tx'ing and stays there. I.E. I set 21074, both vfo, when first TX, lets
> say vfo-b goes 21073500 and stays there. Where is this "delta" defined?
> Ok, I don't use "rig split", because I have other vfo in use cw/ssb,
> easy to change, when ever needed. And I don't use memories either...
> Only simple things for simple person :)
>
> Jarmo, oh1mrr
> > Could you please test the 890S in Rig Split?
> > I have a report that the TS590SG works in Rig Split OK.
> > Mike W9MDB
> >
> >
> >
> > On Wednesday, June 1, 2022, 10:57:51 AM CDT, jarmo via wsjt-devel
> >  wrote:
> >  Wed, 1 Jun 2022 08:05:06 -0700
> > Jim Preston via wsjt-devel 
> > kirjoitti:
> >
> > > On 5/31/2022 9:04 AM, Black Michael via wsjt-devel wrote:
> > > > I need everyone to test the latest Hamlib
> > > > Testing in Rig Split and Fake It would be appreciated.
> > > > Successes/Failures please report.
> >
> > Works ok with TS-590SG and TS-890S. Tested only "fake it". Fedora 36
> >
> > Jarmo, oh1mrr
> >
> >
> > ___
> > wsjt-devel mailing list
> > wsjt-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> >
>
>
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] wsjt-x v2.5.4 (configurations)

[Peter Sumner via wsjt-devel]

Hi David (AK2L),
 this does not have to be the case, if you tick enable the setting "Monitor
returns to last used frequency" in each of your configs on the main
settings page, you may get a  pleasant surprise. :-)

regards,
Peter, vk5pj

On Tue, Jan 11, 2022 at 10:21 AM david--- via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:

> Roger,
>
> When you switch modes as you described, WSJT-X will read the radio's
> current frequency, but will not automatically switch it for you.  I see
> this all the time when I switch between FT4 and FT8.
>
> It is normal behavior and you will have to select the frequency you want
> from the combo box.
>
> David, AK2L
>
>
> -Original Message-
> From: Martin Davies G0HDB via wsjt-devel 
>
> Sent: Monday, January 10, 2022 15:54
> To: WSJT software development 
> Cc: Martin Davies G0HDB 
> Subject: Re: [wsjt-devel] wsjt-x v2.5.4 (configurations)
>
> On 10 Jan 2022 at 22:26, roger stafford via wsjt-devel wrote:
>
> > Hi
> > I use both ft8 and 165 on six meters a lot and of late have to swap
> between the to modes often while trying to work dx.
> > So I set up 2 configurations which works well apart from the freq (ft8
> 313 and qt65 275 which I have to change each time the rest of the settings
> are saved every time.
> > Is this a fault my end ? or could it be changed to save the freq in the
> config.
> >
> > Many thanks stay SAFE
> >
> > De roger vk3fz
>
> Hi Roger, for each configuration you can edit the frequency list so that
> it includes only the frequencies appropriate for that configuration's mode,
> ie. when you're in the FT8 configuration you could edit the frequency list
> so that it contains only the 313 (and I'd suggest the 323) frequencies, and
> similarly for the Q65 config.
>
> When you edit the frequency list you can 'tag' each frequency with the
> mode to which it's appropriate, rather than having 'All' selected for the
> mode.
>
> HTH,
> --
> Martin G0HDB
>
> --
> This email has been checked for viruses by Avast antivirus software.
> https://www.avast.com/antivirus
>
>
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
>
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Cleaner Updates/Installs

[Peter Sumner via wsjt-devel]

Hello Dave,
 one way to approach this (what I do) is use the '7ZIP' utility to extract
the contents of the package (right click on EXE file / extract to /
folder-name.   recognises the packaged EXE as a type of archive file
and will allow you to extract the contents without running the EXE
installer.

This then gives you all the needed files in a folder structure, simply copy
the folder to your 'ham radio' folder tree and create your own shortcuts.

You are then free to prune the directory tree for OLD versions whenever you
like with zero impact on the installed packages.  My shack PC does not even
show that wsjt-x is installed on it as far as the Add/Remove programs panel
is concerned.

Regards,
Peter, vk5pj

On Mon, Jan 10, 2022 at 5:27 PM Dave Fitches via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:

> Hi folks,
>
> Firstly - awesome work with the program to everyone involved (past and
> present!)
>
> Just one nit-picky thing...
> When we have a new version come out, and I install it, it creates a brand
> new Start Menu folder for the new version.
>
> So I now have in my Start Menu:
> wsjtx 2.40
> wsjtx 2.50
> wsjtx 2.52
> wsjtx 2.54
>
> Likewise in my installed programs listing in "Add/Remove Programs" I have
> all 4 versions of the software listed. And given the program installs to
> the same location every time it installs, if I remove the old versions of
> the software, it causes no end of problems.
>
> To remove the old versions I have to remove the oldest. Then because all
> the files are gone, to remove the next oldest I have to re-install the new
> version. THEN remove the next oldest. ...rinse and repeat.
>
> To my mind - it should be working thus:
>
> * If you're installing over an existing version in the SAME INSTALL
> DIRECTORY (Default behaviour), then it should update the existing package
> and update the version number in the Installed Programs list to prevent
> duplicate listings of the same install location, and either use a Common
> Name for the Start Menu folder, or remove the OLD Start Menu folder for the
> previous version number and add the NEW version into Start Menu.
>
> * If you're installing to a brand new directory and there's an existing
> copy installed elsewhere, leave the existing stuff alone because some
> people might want to run an old version and a new version, so list them
> seperately.
>
> I admit - I have ZERO programming chops to do any of these things myself,
> but I can make constructive suggestions for future releases!
>
> Again - I wish to say I am in awe of the software as it stands! These
> points above are piddling things, especially when compared to the joy this
> program brings to a new Ham Operator working off a compromised antenna
> using QRP, and is still able to make DX contacts despite that! If there was
> a "Donate here to support this software" link - I'd be doing it!
>
> Thanks and 73
>
> de VK3DVF
>
> --
>
>
>   = Dave 'Rusti' Fitches =
>
> 
>  ,--__|\Dave 'Rusti' Fitches
> /   \   VK3DVF
> \_,--\_x/   * Mobile : +61-419-466-744
>v* E-mail : vk3...@fitches.com
>   Melbourne, Victoria, Australia
> ___
> Please Note: Unless this e-mail has been sent as PRIVATE, PERSONAL or
> CONFIDENTIAL, the receiver may forward copies of it on the condition
> that they send an advisory message to the original sender.
> If however the message has been marked PRIVATE, PERSONAL or CONFIDENTIAL
> prior consent MUST be obtained before the message can be forwarded.
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Q65 decoder only decodes only one of multiple signals in passband

[Peter Sumner via wsjt-devel]

Hello Joe and others.

It would seem I am the creator of my own problems, I have been chatting
with Charlie G3WDG and he made mention that he was using a narrow Ftol
value and could decode all signals from my shared test WAV file and the
multiple signals in the files he created and sent to me.

I have been setting my Ftol to be a large value (1,000Hz) which was
covering many of the wanted signals in the passband, something I thought I
needed to do, which is a bit of a hangover from using JT65 I guess.

As soon as I set my Ftol down to 20 Hz like Charlie and I now notice you
also made mention of 20Hz in your quick start guide, I am able to decode
all signals in my sample files and those from Charlie on a complete range
of WSJT-X instance I have on the shack PC's and Raspberry PI's I use for
WSPR duties.

For those who like to test it for themselves, my test file for Q65-A 30sec
period is here: https://vk5pj.com/wsjtx/220103_224100.wav
If successful you will see these three decodes:

224100  -7  0.3 1173 :  CQ OC W4TAA EL87  q0
224100 -11  0.2 1520 :  CQ AC4TO EM70  q0
224100 -17  0.2 2510 :  CQ KD5M EM60  q0

I suspect there are many more than I with this wrong setting, so would
encourage people to check their Q65 setup.

regards,
Peter, vk5pj


On Wed, Jan 5, 2022 at 2:43 AM Joe Taylor  wrote:

> Hi Peter,
>
> I tries WSJT-X 2.5.4 on the Q65 sample Q65 files.   I see all the
> decodes for Q65-60A and Q65-30A that are mentioned in the "Quick-Start
> Guide to Q65," so I have no idea what may be causing you trouble.  If
> you haven't figured it out, you could send me a copy of file WSJT-X.ini
> in your log directory, and I'll look further...
>
> -- 73, Joe, K1JT
>
> On 1/4/2022 5:16 AM, Peter Sumner via wsjt-devel wrote:
> > Hi,
> >at some point the Q65 decoder engine has stopped showing decodes from
> > multiple signals in the WSJT-X passband and I am at a loss to explain
> > how or when this has occurred.
> >
> > I have downloaded the sample files from the main Pulsar web site and
> > tried to follow the Q65 quick start guide to no avail.
> >
> > At this point none of the Q65-30A sample WAV files produce a decode for
> > me, the single sample for Q65-60A seems to have two signals but can not
> > get either to decode no matter what combination of Fast, Deep or Normal
> > I have tried.
> >
> > While I have successfully had some Q65 contacts to the USA today from
> > Australia, it is making me doubt the results of the decoder.
> >
> > Does anyone in the group have some proven Sample WAV files with multiple
> > stations in a period I could try? (other than the ones from the WSJT-X
> > web site)
> >
> > So far tried WSJT-X version, 2.4, 2.50, 2.51 and 2.54 with the
> > same result.  I know this used to work for me as in June July it was
> > doing multi pass decoding on the openings to the EU and was working on
> > EME during the recent W7GJ trip away.
> >
> > I am leaning to this being a problem with a windows update as going back
> > and testing with v2.4 should have given me good results but alas no
> >
> > Still scratching my head.
> >
> > Regards,
> > Peter, vk5pj
> >
> >
> > ___
> > wsjt-devel mailing list
> > wsjt-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Q65 decoder only decodes only one of multiple signals in passband

[Peter Sumner via wsjt-devel]

Hi Charlie,
  may I ask were the Q65-60D recordings were EME or terrestrial ?  I have
found that with Q65 it is quite dependent on the 'decode after eme delay'
setting as to whether the signal decodes or not.

After more testing last night, I found the samples from Lance W7GJ that
decoded in Q65-60A but required me to have 'decode after eme delay' ticked
which had me foxed for a few minutes.

So far I have had no luck with any of the Q65-30A samples decoding, on air
observations are the decoder works for one signal only. Checked again to be
sure and the 'single decode'  option is not enabled.   If I go back and
click on each signal I get a decode.

It is behaving like the decoder is in DEEP mode even though FAST is
selected.

Regards,
Peter, vk5pj


Regards,
Peter vk5pj

On Tue, Jan 4, 2022 at 9:18 PM Charles Suckling via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:

> Hi Peter
>
> This link has some Q65 examples, including simulated  one with two
> different  Q65-60D signals in the passband.
>
>  Make sure of course that you have 'single decode' in main settings
> unchecked (!).
>
>
> https://drive.google.com/drive/folders/1RMdrOT7SVIrTDz4hMdmzZkfXJ2daf0yu?usp=sharing
>
> 73
>
> Charlie G3WDG
>
>
>
> On Tue, 4 Jan 2022 at 10:24, Peter Sumner via wsjt-devel <
> wsjt-devel@lists.sourceforge.net> wrote:
>
>> Hi,
>>   at some point the Q65 decoder engine has stopped showing decodes from
>> multiple signals in the WSJT-X passband and I am at a loss to explain how
>> or when this has occurred.
>>
>> I have downloaded the sample files from the main Pulsar web site and
>> tried to follow the Q65 quick start guide to no avail.
>>
>> At this point none of the Q65-30A sample WAV files produce a decode for
>> me, the single sample for Q65-60A seems to have two signals but can not get
>> either to decode no matter what combination of Fast, Deep or Normal I have
>> tried.
>>
>> While I have successfully had some Q65 contacts to the USA today from
>> Australia, it is making me doubt the results of the decoder.
>>
>> Does anyone in the group have some proven Sample WAV files with multiple
>> stations in a period I could try? (other than the ones from the WSJT-X web
>> site)
>>
>> So far tried WSJT-X version, 2.4, 2.50, 2.51 and 2.54 with the
>> same result.  I know this used to work for me as in June July it was doing
>> multi pass decoding on the openings to the EU and was working on EME during
>> the recent W7GJ trip away.
>>
>> I am leaning to this being a problem with a windows update as going back
>> and testing with v2.4 should have given me good results but alas no
>>
>> Still scratching my head.
>>
>> Regards,
>> Peter, vk5pj
>> ___
>> wsjt-devel mailing list
>> wsjt-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Q65 decoder only decodes only one of multiple signals in passband

[Peter Sumner via wsjt-devel]

Hi,
  at some point the Q65 decoder engine has stopped showing decodes from
multiple signals in the WSJT-X passband and I am at a loss to explain how
or when this has occurred.

I have downloaded the sample files from the main Pulsar web site and tried
to follow the Q65 quick start guide to no avail.

At this point none of the Q65-30A sample WAV files produce a decode for me,
the single sample for Q65-60A seems to have two signals but can not get
either to decode no matter what combination of Fast, Deep or Normal I have
tried.

While I have successfully had some Q65 contacts to the USA today from
Australia, it is making me doubt the results of the decoder.

Does anyone in the group have some proven Sample WAV files with multiple
stations in a period I could try? (other than the ones from the WSJT-X web
site)

So far tried WSJT-X version, 2.4, 2.50, 2.51 and 2.54 with the
same result.  I know this used to work for me as in June July it was doing
multi pass decoding on the openings to the EU and was working on EME during
the recent W7GJ trip away.

I am leaning to this being a problem with a windows update as going back
and testing with v2.4 should have given me good results but alas no

Still scratching my head.

Regards,
Peter, vk5pj
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X settings Reporting tab

[Peter Sumner via wsjt-devel]

Hi Bill,
 typo on my part, the UDP server value I use is: 224.0.0.0

[image: image.png]

I use this for Gridtracker and also the wsjt 'message_aggregator.exe'
program that shows what each of my many instances are doing.

Regards,
Peter, vk5pj

On Thu, Nov 4, 2021 at 1:21 PM Bill Barrett via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:

> Hello Laurie-
> Is it 244 or 224? either on does not work on the initial instance.
> 244 does not reveal the extra fields. 224 reveals the extra fields but
> does not work.
> see ??? for band data on initial instance and no decodes in Call Signs
> window.
> Where am I going wrong?
> Thanks;
> Bill
>
> On Wed, Nov 3, 2021 at 10:32 PM Laurie, VK3AMA via wsjt-devel <
> wsjt-devel@lists.sourceforge.net> wrote:
>
>>
>>
>> On 4/11/2021 12:43 pm, Bill Barrett via wsjt-devel wrote:
>>
>> This is from 2.5.0, first and second instance on Win11
>> does anyone know why they are different?
>>
>> Thanks;
>> Bill W2PKY
>>
>> You're running multiple WSJT-X instances with incompatible udp server
>> settings. You have one instance running unicast (127.0.0.1) and the other
>> multicast (244.0.0.1). JTAlert when running in a multi-instance environment
>> requires that all WSJT-X instances be set to use multicast. You need to
>> change your unicast WSJT-X instance to multicast for the UDP server
>> settings.
>>
>> de Laurie VK3AMA
>> ___
>> wsjt-devel mailing list
>> wsjt-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X settings Reporting tab

[Peter Sumner via wsjt-devel]

Hello Bill,
 yes those displays are indeed different as on one you have defined a UDP
broadcast address of 244.0.0.1 which then prompts the WSJT software to
offer you a selection for an interface to apply this to. Ethrnet or
loopback normally, plus the multicast TTL, whereas the other version is the
STOCK config.

You can make them look the same by putting in the broadcast address of
127.0.0.1 and all the other options will go away after you hit OK

All of my instances of WSJT-X have the 244.0.0.1 setup so I can use the
monitoring software across my farm of PC's

Regards,
Peter, vk5pj

On Thu, Nov 4, 2021 at 12:20 PM Bill Barrett via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:

> This is from 2.5.0, first and second instance on Win11
> does anyone know why they are different?
>
> Thanks;
> Bill W2PKY
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Feature Request: Hound Mode

[Peter Sumner via wsjt-devel]

for the F/H - Contest brigade

Rather than extra buttons / tick boxes on the existing busy screen for a
dedicated group of users, would a small pop-out window like that used for
the Astronomical data display be a better proposal?

I know its a bit of a radical shift of thinking and of course would
initially require an extra mouse click but once opened it is from my eme
experience it is remembered.

The DEV team may consider this as a viable option to duplicate / group the
extra contest and F/H bits on rather than a re-hash of the GUI?

just a passing thought..

Regards,
Peter vk5pj



>
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] MAP65 with Icom 7610

[Peter Sumner via wsjt-devel]

On Fri, Aug 27, 2021 at 2:51 AM Bill Somerville via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:

> On 26/08/2021 17:49, Bill Somerville via wsjt-devel wrote:
>
> On 25/08/2021 02:32, Peter Sumner via wsjt-devel wrote:
>
> Hello,
>   was curious if anyone has a way to use the IQ data available over USB-3
> from the rear of an IC-7610 to feed into MAP65?
> I have the HDSDR software working with the ICOM supplied driver but as yet
> have not managed to get MAP65 to work with this source.
> With the new Q65 mode being spread across many regional frequencies on 50
> MHz, it is getting harder to keep an eye on each of the frequencies but
> with the Q65 mode in MAP65 it might help me and others with this, plus be
> handy for 50 MHz EME when the moon has multiple Q65 QSO's in progress.
>
> regards,
> Peter Sumner, vk5pj
>
>
> Hi Peter,
>
> MAP65 requires either a single or dual I/Q feed via an audio device at
> 96,000 frames per second, or a Linrad compatible UDP feed of one or two I/Q
> data channels, also at 96,000 frames per second.
>
> Icom provide some tools that can consume the IC-7610 single channel
> wide-band I/Q feed on the [USB 2] connector as an ExtIO library (MS Windows
> only) that can feed various SDR console applications. If one of those SDR
> console applications can decimate and output that at 96,000 frames per
> second to an audio device, then that would be compatible MAP65 in single
> polarization mode.
>
> 73
> Bill
> G4WJS.
>
> Hi Peter,
>
> note also that MAP65 only supports the 60 second T/R period variants of
> Q65 and that is unlikely to change, most terrestrial Q65 operation uses 30
> second periods.
>
> 73
> Bill
> G4WJS.
>

Thanks Bill,
I had forgotten about the limit on time sequences in MAP65 : -) looks like
I am back to using the SDR with multiple slices for terrestrial but will
explore the MAP65 option for EME in the coming weeks.

Regards,
Peter, vk5pj

> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] MAP65 with Icom 7610

[Peter Sumner via wsjt-devel]

Hello,
  was curious if anyone has a way to use the IQ data available over USB-3
from the rear of an IC-7610 to feed into MAP65?
I have the HDSDR software working with the ICOM supplied driver but as yet
have not managed to get MAP65 to work with this source.
With the new Q65 mode being spread across many regional frequencies on 50
MHz, it is getting harder to keep an eye on each of the frequencies but
with the Q65 mode in MAP65 it might help me and others with this, plus be
handy for 50 MHz EME when the moon has multiple Q65 QSO's in progress.

regards,
Peter Sumner, vk5pj
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Testing please ignore.

[Peter Sumner via wsjt-devel]

Oh you venturing down the rabbit hole of Dmarc are you.. been there and
have my scars ☹️
Peter, vk5pj

On Thu, 15 Jul 2021, 21:29 Bill Somerville via wsjt-devel, <
wsjt-devel@lists.sourceforge.net> wrote:

> Just testing message handling where DMARC is used.
>
>
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Block spot uploads when change of band occurs

[Peter Sumner]

Hello to the WSJT-X community,

Would the DEV team consider including some logic to abort the upload of
decodes in progress to spotting sites like PSKreporter when a change of
band is detected from within WSJT-X?

It would seem to be a regular thing where stations are reported on the
wrong band when a listening station receiving them on say 40M then changes
bands to say 6M and a report from a HF station is then attributed to 6M.
 While a small problem in the overall scheme of life it does cause
consternation to those on 6M as to how that station was being reported as
active on 6M.

>From my experimentation this occurs when listening to a busy HF band and
the decoder and display processes are busy, injecting a change of bands
from the band spinner appears to immediately change the frequency
attributes from 40M to be 6M on the data sent to PSK reporter.

I am not sure if it would be best to dump the queued decodes or block the
reporting action for the reporting system after a band change has been
detected but I am sure many may have opinions on this.

with thanks,

Peter, vk5pj
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] TX audio setting on RC4

[Peter Sumner]

Hello Joe,
 while not wishing to hijack the thread, I am a great believer of the use
of configurations for each setup ( I have one for each mode I use ) , the
one niggle is the "RC expires on " warning message we get when changing
from one to another configuration from the Release Candidate versions.  If
there was a way to only see that reminder message at initial startup and
not each time we change to a new configuration, that would be a step
forward to making the use of 'configurations' an easy sell.

as always, thanks to you and the team for the work you put in to make
WSJT-X possible.

Regards,
Peter, vk5pj

On Wed, Apr 21, 2021 at 11:30 AM Joe Taylor  wrote:

> Hi Rex,
>
> The general policy in WSJT-X is that we don't try to "remember" user
> settings by mode, band, or whatever.
>
> If you want parameters in reset to previously selected values according
> to band or mode, you should define a Configuration for each frequently
> used combination, and give it a convenient name.  You can have a dozen
> or more configurations, each one set up the way you want.  Don't just
> switch to Echo mode, switch to your Echo configuration.  If you use both
> Q65-60D and Q65-60E frequently, don't just use the ABCDE spinner --
> define a configuration for submode.
>
> Doesn't this approach solve your problem as well as any other scheme
> could do?
>
> -- 73, Joe, K1JT
>
> On 4/20/2021 7:22 PM, Rex Moncur wrote:
> > On RC3 Q65 automatically set the TX audio frequency to 1000 Hz for
> > Q65-60D (as well as the A to C sub-modes) and to 700 Hz for the E sub
> > modes.  That worked well for the upper microwave users and kept the
> > audio frequency within the bandpass of most SSB transceivers.
> >
> > Some VHF operators who use the narrow sub-modes asked that the TX audio
> > frequency be held constant at where it was last set and this was
> > introduced in RC4 with a red warning if the audio frequency was likely
> > to go outside the Bandpass.  The VHF operators argued in part that the
> > RC3 method would result in operators tending to focus on 1000 Hz and be
> > on top of each other.
> >
> > RC4 does however introduce a problem in that if you change to say WSPR
> > or echo mode the TX audio frequency is moved up to 1500 Hz and remains
> > at this when you go back to Q65. EME operators often do an echo test to
> > establish that their station is working prior to moving to another mode
> > and thus end up TXing Q65 on 1500 Hzrather than 1000 Hz which is
> > standard at the upper microwaves.   This is a particular problem for
> > weak signal microwave users who typically use a low Ftol and single
> > decodesand do not notice that the TX audio frequency has been moved up
> > to 1500 Hz.  The problem is further exacerbated if you are running a
> > sked with a weak station and use the 1000 Hz tune tone to establish that
> > both stations are on frequency and that you have viable signals.  In
> > this case the 1000 Hz tune tone does in fact show up at 1000 Hz,
> > indicating you are on frequency, but when you change to transmit
> > messages they come out at 1500 Hz and are generally outside Ftol and
> > thus do not decode.
> >
> > I can see a number options to mitigate these conflicting requirements
> > although none are perfect, for example:
> >
> > 1. The RC4 method could be changed such that all modes always returns to
> > the last TX audio frequency in use for that"mode".  While this will work
> > for microwave operators who are exactly on frequency  the audio
> > frequency will sometimes be changed off 1000 Hz to tune in a station off
> > frequency so it is less than ideal.
> >
> > 2. The RC3 method could be applied ifthe higher microwave frequencies
> > are selected and the RC4 method (modified to come back to the last
> > frequency used for each mode)  if VHF and lower microwave frequencies
> > are selected.  The problem is that there is no clear frequency boundary
> > where one or other method is preferred.  One possibility would be the
> > modified RC4 method up to and including the 3.4 GHz band MHz and  the
> > RC3 method above that.  The disadvantage of this approach is that people
> > would need to understand that if they changed to the higher microwave
> > frequencies the operating method has changed.
> >
> > While I don't see an ideal solution my preference for a compromise
> > solution would be option 2 above.  But I think it worth a wider
> > discussion to see if a better solution can be found.
> >
> > 73 Rex VK7MO
> >
> >
> >
> > ___
> > wsjt-devel mailing list
> > wsjt-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> >
>
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net

Re: [wsjt-devel] Release candidate: WSJT-X 2.4.0-rc2

[Peter Sumner]

Hello Joe,
 may I ask for one item to be added to the Quick Start Guide for Q65?

"If using Q65 on EME the option on the setting page for 'Decode after EME
delay' must be ticked before you use Q65 for EME." or similar wording that
conveys the needed message.

I spent many nights seeing zero decodes on 50 MHz EME using Q65 and was
ready to throw in the towel, could not for the life of me work out why as I
have never had this option ticked when using JT65 and on that mode I have
worked many stations over the last 3 years off the moon. It was not until
Tim N0TB kindly prodded me to check that setting and then there was no
stopping me as I knew Q65 worked as I have had many terrestrial QSO's using
this mode, experimenting with the various time periods.

Thanks to the team for all the hard work and for the evolution of QRA64
into Q65.

Regards,
Peter, vk5pj


On Sat, Mar 6, 2021 at 12:30 AM Joe Taylor  wrote:

> We are pleased to announce release candidate WSJT-X 2.4.0-rc2, which
> includes the new digital mode Q65.
>
> Q65 is designed for two-way QSOs over especially difficult propagation
> paths such as ionospheric scatter, troposcatter, rain scatter, TEP, EME,
> and other types fast-fading signals.  Details and recommendations
> concerning the Q65 submodes are provided in the "Quick-Start Guide to
> Q65", available here:
> https://physics.princeton.edu/pulsar/k1jt/Q65_Quick_Start.pdf
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Release candidate: WSJT-X 2.4.0-rc1

[Peter Sumner]

Hello Max,
 I think you have forgotten to tick "Enable VHF and submode features" on
page one of the Setup menu, works 100% here on JT65

Regards,
Peter, vk5pj

On Sun, Feb 7, 2021 at 10:32 AM Max Mucci, N5NHJ (I8NHJ) via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:

> Hello Joe,
> Looks like there is no option available to select JT65 sub-modes.
>
> --
> 73 de Max, N5NHJ (I8NHJ)
>
> Wednesday, February 3, 2021, 4:27:46 PM, you wrote:
>
> > We are pleased to announce availability of a release candidate for
> WSJT-X 2.4.0, introducing a new digital mode called Q65.  Timing of this
> release is unusual as it follows so closely the General Availability (GA)
> release of WSJT-X 2.3.0.  This timing anomaly occurs because development of
> new modes FST4 and FST4W (in v2.3.0) and Q65 (in 2.4.0) took place in
> parallel.
>
> > Q65 is designed for making two-way QSOs over especially difficult
> propagation paths such as troposcatter, ionospheric scatter, rain scatter,
> EME, and other types fast-fading signals.  Full details about Q65 submodes
> and their capabilities are provided in the Quick-Start Guide to Q65,
> available here:
>
> > https://physics.princeton.edu/pulsar/k1jt/Q65_Quick_Start.pdf
>
> > The main User Guide has not yet been updated with documentation for
> Q65.   Use the Quick-Start Guide, in the meantime.
>
> > Links to installation packages for Windows, Linux, and Macintosh are
> available here:
> > http://physics.princeton.edu/pulsar/k1jt/wsjtx.html
> > Scroll down to find "Candidate release:  WSJT-X 2.4.0-rc1".
>
> > You can also download the packages from our SourceForge site:
> > https://sourceforge.net/projects/wsjt/files/
> > It may take a short time for the SourceForge site to be updated.
>
> > WSJT-X is licensed under the terms of Version 3 of the GNU General
> Public License (GPL).  Development of this software is a cooperative
> project to which many amateur radio operators have contributed.  If you use
> our code, please have the courtesy to let us know about it.  If you find
> bugs or make improvements to the code, please report them to us in a timely
> fashion.
>
> > We hope you will enjoy using this beta release of WSJT-X 2.4.0 and
> exercising the new mode Q65.  Please report on your Q65 experiences,
> successful and otherwise, on one of the WSJT forums.  Bugs should be
> reported by following instructions found here in the User Guide:
>
> >
> https://www.physics.princeton.edu//pulsar/K1JT/wsjtx-doc/wsjtx-main-2.4.0-rc1.html#_bug_reports
>
> >-- 73 from Joe, K1JT; Bill, G4WJS; Steve, K9AN; and Nico, IV3NWV
>
>
> > ___
> > wsjt-devel mailing list
> > wsjt-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
>
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] WSPR spot upload stops on Raspberry PI

[Peter Sumner]

Hi,
 for a while now I have been using a PI 4 for my WSPR activities and it has
always been hit n miss as to whether my spots get to WSPRNET. In the end it
was like 3 months of unsuccessful activity reporting that forced me to
reformat the SD card and update to the BUSTER release of Raspian..  All
seemed to be going okay for a few weeks and now I find that from Dec 30 my
WSPR uploads have once again seem to have gone off into the ether.

I know this is strictly not a DEV question but am curious if any other PI 4
users have found an answer, maybe I need to Run Win 10 on my PI-4 :-) or
maybe another Linux distro.

Regards,
Peter, vk5pj
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] issue? report No change frequncy by FT8 to MSK144

[Peter Sumner]

Thanks Bill,
 that certainly has done the magic, to think I have struggled with this for
many years and not thought to ask..

Regards,
Peter, vk5pj

On Sun, Nov 22, 2020 at 8:38 AM Bill Somerville 
wrote:

> Hi Peter,
>
> switching configurations is equivalent to initial startup, it depends on
> the option "Settings->General->Monitor returns to last used frequency".
>
> 73
> Bill
> G4WJS.
>
> On 21/11/2020 20:16, Peter Sumner wrote:
>
> Hello Bill,
>  does your explanation of behavior hold for when the mode is changed via
> the selection of a different configuration?  In my experience the correct
> frequency is never selected when I change to a different configuration,  I
> have multiple configurations with matching modes for both my HF and VHF
> rigs, selecting a different configuration always leaves the rig at the
> previously used frequency, is this expected behavior?
>
> WSJT-X v2.30-RC2 and WSJT-X v2.21
>
> Regards,
> Peter vk5pj
>
>
>> WSJT-X will select the lowest frequency on the current band (or new band
>> if selecting a band) for the current mode (or new mode if changing
>> mode). The lowest frequency is the lowest one that is specified in
>> "Settings->Frequencies->Working Frequencies" that has a matching band,
>> mode if specified, and IARU Region that matches the one set in
>> "Settings->General". Have you set your IARU Region in "Settings
>> General"? If not then IARU Region filtering of frequencies will not be
>> done.
>>
>> 73
>> Bill
>> G4WJS.
>
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] issue? report No change frequncy by FT8 to MSK144

[Peter Sumner]

Hello Bill,
 does your explanation of behavior hold for when the mode is changed via
the selection of a different configuration?  In my experience the correct
frequency is never selected when I change to a different configuration,  I
have multiple configurations with matching modes for both my HF and VHF
rigs, selecting a different configuration always leaves the rig at the
previously used frequency, is this expected behavior?

WSJT-X v2.30-RC2 and WSJT-X v2.21

Regards,
Peter vk5pj


> WSJT-X will select the lowest frequency on the current band (or new band
> if selecting a band) for the current mode (or new mode if changing
> mode). The lowest frequency is the lowest one that is specified in
> "Settings->Frequencies->Working Frequencies" that has a matching band,
> mode if specified, and IARU Region that matches the one set in
> "Settings->General". Have you set your IARU Region in "Settings
> General"? If not then IARU Region filtering of frequencies will not be
> done.
>
> 73
> Bill
> G4WJS.
>
>
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Lookup of a DX call does not populate DX Grid

[Peter Sumner]

Hello,
  I am not sure if this is a defect in behavior or done by design. When I
use the 'Lookup' button from the main screen to get grid information from
call3.txt for a new value in the "DX Call" field, should there be an
existing "Dx Grid" value in the box from a previous QSO, the updated grid
information from Call3.txt is not displayed (old information remains
displayed).

If I clear the "Dx Grid" value, then using the Lookup button does then
insert the correct information in "DX Grid".

Windows 10 x64 build 19042 (20H2) but has been like this on all previous
Windows versions.

WSJT-X v2.3.0-rc1, tried using FT8, JT65 and MSK144

Regards,
Peter, vk5pj
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Fwd: TX1 double click does not survive change of configuration

[Peter Sumner]

Seems my original send did not make it to the list as it has been
extremely quiet for the last 5 days here.

Hello Dev team,
 the function to skip over sending a 'TX1' message is lost when I change
configuration to another mode, then come back to the original configuration
I started on, in this case my FT8 configuration but other modes behave this
way too.  Is this an expected behaviour or could the skip TX1 (Double mouse
click TX1) be preserved in some manner for each configuration where enabled?

WSJT-2.2.1 in use on X64 PC with Win10 1909, have not moved to 2.2.2 as
waiting for next maint release to help with WSPR freq hopping problem.

Regards,
Peter, vk5pj
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] TX1 double click does not survive change of configuration

[Peter Sumner]

Hello Dev team,
 the function to skip over sending a 'TX1' message is lost when I change
configuration to another mode, then come back to the original configuration
I started on, in this case my FT8 configuration but other modes behave this
way too.  Is this an expected behaviour or could the skip TX1 (Double mouse
click TX1) be preserved in some manner for each configuration where enabled?

WSJT-2.2.1 in use on X64 PC with Win10 1909, have not moved to 2.2.2 as
waiting for next maint release to help with WSPR freq hopping problem.

Regards,
Peter, vk5pj
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] dark theme and astronomical data view

[Peter Sumner]

On Thu, Jun 25, 2020 at 9:36 PM Bill Somerville 
wrote:

> On 25/06/2020 10:33, Peter Sumner wrote:
> > Hi Deve team,
> >  when starting WSJT-X with the Dark Theme, if I then open the
> > 'Astronomical Data' view I am greeted with an all white display,
> > Doppler Tracking checkbox is there but no text description, it would
> > seem the text is now white but the background is still white.  There
> > appears to be no option to change the text colour so I can not 100%
> > confirm this is the case.
> >
> > Version: WSJT-X 2.2.1 ( I have not tried 2.2.2 as there were bugs
> > already reported on WSPR hopping which I do use on VHF)
> >
> > Started by the shortcut:
> >
> > C:\ham_radio\wsjtx-2.2\bin\wsjtx.exe -r 910  --stylesheet
> > :/qdarkstyle/style.qss
> >
> > If there is anything me I can do to test this please let me know,
> > Regards,
> > Peter, vk5pj
>
> Hi Peter,
>
> thanks for the issue report. I can confirm that this is a defect, it is
> corrected for the next release. Unfortunately there is no easy
> workaround so all I can suggest for now is not to use the dark style
> sheet facility if you require the astronomical data window contents.
> Sorry for the inconvenience.
>
> 73
> Bill
> G4WJS.
>
> Hello Bill,
 have also noticed if I change from one WSJ-X configuration to another ( I
have configurations for FT8, JT65 and WSPR among others ) then 'Dark Theme'
is lost when WSJT-X re-opens on the new config.  It would seem the "Dark
Theme' setting is lost when the process restarts.  I am not wed to 'Dark
Theme' so have reverted to standard for now as it seems cleaner to do it
this way. but thought I should report this for completeness.

Do you ever manage to get on air these days Bill?

Regards,
Peter, vk5pj
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] dark theme and astronomical data view

[Peter Sumner]

Hi Deve team,
 when starting WSJT-X with the Dark Theme, if I then open the 'Astronomical
Data' view I am greeted with an all white display, Doppler Tracking
checkbox is there but no text description, it would seem the text is now
white but the background is still white.  There appears to be no option to
change the text colour so I can not 100% confirm this is the case.

Version: WSJT-X 2.2.1 ( I have not tried 2.2.2 as there were bugs already
reported on WSPR hopping which I do use on VHF)

Started by the shortcut:

C:\ham_radio\wsjtx-2.2\bin\wsjtx.exe -r 910  --stylesheet
:/qdarkstyle/style.qss

If there is anything me I can do to test this please let me know,
Regards,
Peter, vk5pj
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Error on Sound Input

[Peter Sumner]

Hello Don,
 as this is a new install of Windows 10, you may find the inbuilt Windows
10 security is preventing WSTJ-X from accessing a 'microphone device'.
Please go to Windows 10 start menu / Settings  / Privacy and then
Microphone and ensure the slider to allow all apps to access your
microphone device is enabled.
Hope this helps.
regards,
Peter, vk5pj

On Tue, Jun 16, 2020 at 5:09 AM DonMcMahon  wrote:

> I am getting an “Error on Sound Input” message when I start WSJT-X and
> have not been able to resolve it. It occurs immediately when I start WSJT-X
> v2.2.1 but, through troubleshooting, I noticed it is also occurring on
> earlier versions. It is not related to RFI since this occurs immediately
> after a program start well prior to any transmissions.
>
> I had just built a new Windows 10, 64-bit based machine with 64 GB memory
> and migrated my old hard drive to new M2 drives. My former machine had
> Windows version 1904 and after it was migrated to the new hardware, it was
> upgraded to Windows 2004 on the new hardware. All other programs appear to
> be working correctly except with the error message with loading WSJT-X.
>
> I am using an ICOM IC-7610 radio with built-in sound interface and I have
> verified its radio menu settings with a friend’s radio. The new computer
> has the ICOM driver installed, Silicon Labs USB to UART Bridge Drivers,
> version 1.30.
>
> These are the steps I have taken so far.
>
> 1.  Re-installed ICOM USB drivers,
>
> 2.  Rolled back WSJT-X to v2.0.0 with same results and then
> reinstalled v2.2.1,
>
> 3.  Confirmed no other programs are using the Silicon Labs USB to
> UART Bridge drivers,
>
> 4.  Confirmed microphone privacy settings are set to allow device,
>
> 5.  Confirmed IC-7610 set to Default Communications Device, and
>
> 6.  I did find that WJT-X can be set to another microphone input it
> will begin functioning; that leads me to believe it is a ICOM radio sound
> card problem.
>
> Has anyone come across this issue with “Error in Sound Input” and found
> how to resolve it with the ICOM IC-7610? Any trouble shooting ideas will be
> helpful.
>
> Don, N7BD
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Feature request: Dead Band Beacon

[Peter Sumner]

Hello Development team,
  while I know any QSO automation features are out of the question I would
like to ask that a 'dead band beacon' be considered for some future release
of WSJT-X.

My thought process sort of goes along these lines.

Enable Deadband beacon option tick box, and set "enable. TX" to be on.

WSJT-X send's text in TX 6, waits for 45 seconds and sends text from TX6
again but in the opposite time slot.

WSJT-X then sleeps the "Enable TX" function for xx minutes (user or system
set value) while keeping an eye on all incoming decodes.

Should any decode occur in a specified time window from the last Transmit
sequence then the next Transmit function is cancelled or delayed
(selectable option?).

WSJT-X again looks at any incoming decodes and if no RX decode has occurred
during the last specified time window, the Beacon sequence occurs again, in
the same manner as earlier.

By WSJT-X checking for any incoming decodes, it should stop the dead band
beacon from becoming annoying to other users.

Having the ability to 'deadband beacon' on bands like 50 /144 / 432 MHz
where openings can flit past in minutes would be a great plus for weak
signal operators.  I am in no way advocating for the 'dead band beacon' to
answer other callers, I will leave that part to the carbon life forms
operating the keyboards : -)

Hope you will take some time to consider this during your conversations on
what goes into new versions.

I am happy to discuss this further should the need arise.

Regards,
Peter, vk5pj
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X and PSKReporter

[Peter Sumner]

Hi Adrian, messages via TCP put a requirement on the local PC to handle
errors which all add complexity and resources to do it. The messages have
to be sent, an answer waited for and if no answer, sent again until a time
out is received, then handle this time out...  UDP on the other hand is a
send it and move on to the next thing process which requires very little
overhead and no error handling by the sender.  This is why UDP messaging is
so popular as you do not have to worry about the outcome of a send and
generally works on most networks.

Regards,
Peter, vk5pj

On Sun, Jun 7, 2020 at 3:03 PM Adrian  wrote:

> This sounds like a great idea. I am surprised it is not already done via
> tcp.
>
>
> On 7/6/20 11:23 am, Philip Gladstone wrote:
>
> There are a (small) number of WSJT-X users who have difficulty reporting
> their spots to pskreporter. Some of these are in "difficult" areas of
> network connectivity (e.g. Marine Mobile) and I suspect that the UDP
> transport is losing most of their packets. The general loss rate seems to
> be around 1%-2% which is somewhat higher than I would expect, but it is not
> unbelievable either.
>
> It is also difficult to diagnose these sort of problems as the packets
> appear to leave the PC running WSJT-X and not arrive at my server!
>
> PSKReporter was never supposed to be 100% reliable, but there seem to be a
> lot of people who think otherwise
>
> In an effort to improve the situation, I have now stood up a TCP listener
> that might help. The protocol is identical -- the only difference is that
> you send the same messages as before over a TCP connection to
> report.pskreporter.info port 4739 rather than over a UDP connection.
> There is no extra framing required as the messages already contain a length
> code.
>
> The listening server should be able to support enough connections. It will
> close a connection if an invalid message is received.
>
> Is this change something that could be implemented? Also, currently, you
> send a bunch of packets at the same time (on the five minute expiry). You
> could send them as soon as they get "full" rather than waiting.
>
> Thanks
>
> Philip
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Hold TX Frequency Default

[Peter Sumner]

Hi Jim,
 you should consider using different configurations for the modes and try
to not use the MODE selector when possible, using a Configuration for each
mode will return you to exactly where you were before on that mode.  I use
it exclusively on the three computers here (2 are PI's) and find it works a
treat.  It is just a small mind set change for changing modes to use the
Configuration menu, start with one sample setup like you use for FT8 and
Clone it, rename the clone to be MSK144, switch to that mode and alter the
settings to how you like it, even the waterfall changes are remembered.
You may be pleasantly surprised how well it works for you.

Regards,
Peter, vk5pj

On Tue, May 19, 2020 at 2:54 PM Jim Brown 
wrote:

> Joe, Bill, and Steve,
>
> I have made this "feature request before, and hoped to see it in this
> beta, but it's missing. My request is that either 1) WSJT-X remember my
> setting of Hold TX Frequency or 2) make Hold TX Frequency the default. I
> am continually bitten by this when I switch back and forth between the
> slow modes and fast modes on 6M. I ALWAYS want it ON, but when I return
> to FT8 from MSK144 or ISCAT, it's ALWAYS turned off and set to 1500 Hz.
>
> I'm THRILLED with the three-stage decode process. It speeds up general
> operation a lot, because I now nearly always have time to make TX
> decisions in time to start at the beginning of the TX period.
>
> I'm experiencing at least as many bad decodes as before, maybe more, and
> they seem to come from that last third decode operation. Not
> complaining, just observing.
>
> Thanks and 73, Jim K9YC
>
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Coming soon: WSJT-X 2.2.0-rc1

[Peter Sumner]

Hello Joe.
  thanks for the advance notice, I am sure the VHF Tropo and EME
communities will be eager to see what comes in the package and maybe after
all this time the now old and well worn war between WSJT 10 and WSJT-X for
JT65 can be put to bed : - )

VK has a very active VHF WSPR community so I imagine we will be all eager
to experience the enhancements to WSPR

Regards,
Peter vk5pj

On Wed, May 6, 2020 at 1:54 AM Joe Taylor  wrote:

> Hi all,
>
> This message is to let you know of some important WSJT-X development
> plans.  We plan to make a first candidate release of WSJT-X 2.2.0 next
> Monday, May 10.
>
> WSJT-X 2.2.0-rc1 will be a beta-quality release candidate providing a
> number of new features and capabilities.  These include:
>
>- Improvements to the decoders for five modes:
>
>FT4: Corrected bugs that prevented AP decoding and/or multi-pass
>decoding in some circumstances.  The algorithm for AP
>decoding has been improved and extended.
>
>FT8: Decoding is now spread over three intervals.  The first
>starts at t = 11.8 s into an Rx sequence and typically yields
>around 85% of the possible decodes for the sequence.  You
>therefore see most decodes much earlier than before.  A second
>processing step starts at 13.5 s, and the final one at 14.7 s.
>Overall decoding yield on crowded bands is improved by 10% or
>more.  (Systems with receive latency greater than 0.2 s will see
>smaller improvements, but will still see many decodes earlier
>than before.)
>
>JT4: Formatting and display of Averaged and Deep Search decodes
>has been cleaned up and made consistent with other modes.  JT4
>remains the digital mode of choice for EME and other extreme
>weak-signal work on microwave bands.
>
>JT65: Many improvements for Averaged and Deep Search decodes and
>their display to the user.  These improvements are particularly
>important for EME on VHF and UHF bands.
>
>WSPR: Significant improvements have been made to the WSPR
>decoder's sensitivity, its ability to cope with many signals in
>a crowded sub-band, and its rate of undetected false decodes.
>We now use up to three decoding passes.  Passes 1 and 2 use
>noncoherent demodulation of single symbols and allow for
>frequency drifts up to ±4 Hz in a transmission.  Pass 3 assumes
>no drift and does coherent block detection of up to three
>symbols.  It also applies bit-by-bit normalization of the
>single-symbol bit metrics, a technique that has proven helpful
>for signals corrupted by artifacts of the subtraction of
>stronger signals and also for LF/MF signals heavily contaminated
>by lightning transients.  With these improvements the number of
>decodes in a crowded WSPR sub-band typically increases by 10 to
>15%.
>
>   - New format for "EU VHF Contest" Tx2 and Tx3 messages
>
>When "EU VHF Contest" is selected, the Tx2 and Tx3 messages
>(those conveying signal report, serial number, and 6-character
>locator) now use hashcodes for both callsigns.  This change is
>NOT backward compatible with earlier versions of _WSJT-X_, so
>all users of EU VHF Contest messages should be sure to upgrade
>to versiion 2.2.0.
>
>   - Accessibility
>
>Keyboard shortcuts have been added as an aid to accessibility:
>Alt+R sets Tx4 message to RR73, Ctrl+R sets it to RRR.
>
>As an aid for partial color-blindness, the "inverted goal posts"
>marking Rx frequency on the Wide Graph's frequency scale are now
>rendered in a darker shade of green.
>
>   - Minor enhancements and bug fixes
>
>"Save None" now writes no .wav files to disk, even temporarily.
>
>An explicit entry for "WW Digi Contest" has been added to
>"Special operating activities" on the "Settings | Advanced" tab.
>
>Contest mode FT4 now always uses RR73 for the Tx4 message.
>
>The Status bar now displays the number of decodes found in the
>most recent Rx sequence.
>
> Release candidate WSJT-X 2.2.0-rc1 will be available for beta-testing
> for one month starting on May 10, 2020.  We currently plan a General
> Availability (GA) release of WSJT-X 2.2.0 on June 1, 2020.
>
> For those looking even farther ahead: We are well along in the
> development of two new modes designed for the LF and MF bands.  One
> mode is for WSPR-like activity and one for making 2-way QSOs.  Both
> use Low-density Parity Check (LDPC) codes, 4-GFSK modulation, and
> two-minute T/R sequences.  The QSO mode reaches threshold SNR
> sensitivity around -31 dB on the AWGN channel, and the WSPR-like mode
> better than -32 dB.
>
> With best wishes,
>
> -- Joe, K1JT, Steve, K9AN, and Bill, G4WJS
>
>
> ___
> wsjt-devel 

Re: [wsjt-devel] Logging

[Peter Sumner]

Joe,
 in WSJT-X on the settings menu, you have to put WSJT-X into contest mode
as the others have hinted at...  Only THEN will it auto log, the Auto log
for normal use was disabled a few releases back to stop people creating QSO
robots.

Regards,
Peter vk5pj

On Wed, Jul 24, 2019 at 12:56 AM Joe  wrote:

> But?
>
> It is a contest, it is fully integrated with N1MM+ the WWDIGI contest
> https://ww-digi.com/rules.htm
>
> The paired software is telling me who is a New mult, who is good to work,
> who is a dupe  etc. N1MM+ is even what opens WSJT-X, so what part of being
> in a contest am I missing?
>
> Joe WB9SBD
>
> On 7/23/2019 10:10 AM, Sam W2JDB via wsjt-devel wrote:
>
> Hi Joe,
>
> The automatic logging is only effective when you are in a contest mode.
> i.e. RTTY RU or FD etc.
>
> 73,
>
> Sam W2JDB
>
>
>
> -Original Message-
> From: Joe  
> To: Black Michael  ; WSJT
> software development 
> 
> Sent: Tue, Jul 23, 2019 11:00 am
> Subject: Re: [wsjt-devel] Logging
>
> OK,
>
> I have the Log Automatically check marked as seen below in earlier message.
>
> Now I see someone CQing, I double click on them and it calls them, all is
> well,
> The QSO proceeds along as usual, and when finished, instead of "Logging
> Automatically"
> I am still getting this.
>
>
> What do I need to check to make it do it automatically.
>
> Joe WB9SBD
>
> On 7/22/2019 10:15 PM, Black Michael via wsjt-devel wrote:
>
> If you're not in contesting mode it still asks.  Designed that way.
>
> de Mike W9MDB
>
>
>
>
> On Monday, July 22, 2019, 10:07:30 PM CDT, Joe  
> wrote:
>
>
> This logging Prompt,
>
> I had the box to ask me go get a prompt to log the contact.
>
> And id does.
>
> I changed it to automatically log it as the small red circle indicates. I
> checked that box and tried it again.
>
> But it still asks me with a prompt to log the contact.
>
> I see no difference.
>
> anyone?
>
> Joe WB9SBD
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
>
> ___
> wsjt-devel mailing 
> listwsjt-devel@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
>
> ___
> wsjt-devel mailing 
> listwsjt-devel@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Is it Heresy to QSY Without Adding a Frequency to the List

[Peter Sumner]

Hi Tim
 the only down side I have found of not adding it is . . .  If you go into
the CONFIG menu and click okay (even just for a look and make no changes)
when you come out WSJT-X will flip to the closest defined frequency in the
list for that mode.   In my case I found this when working EME on 50.190
MHz I went in to look at my decoder settings and then clicked OK. I did not
realise I had been QSY'd to be on 50.276 MHz for some minutes and wondered
where the signals had gone too.

Regards,
Peter VK5PJ

On Thu, Jun 20, 2019 at 9:33 AM Tim Goeppinger via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:

> I remember back a year ago when we did tests of DXpedition mode, I entered
> the
> DXpedition frequency into the list for the software.  I think it was 14090
> KHZ,
>
> Since then DXpeditions have done their operating on frequencies all over
> the digital subbands,
> and I got tired of adding their frequency to the list each time.  One time
> I decided to spin my dial
> to the frequency without entering it to the list.   The DXpedition mode
> worked great - it did all the
> QSYing within the audio spectrum to make the DX QSO, and the frequency
> logged just fine.  I have
> been spinning the dial without frequency entry ever since.
>
> Fast forward to this month for Field Day where I am heading up the FT8 For
> Field Day group in Facebook.  We have a separate list of frequencies to
> use, so that we don't disrupt normal FT8 activity.
> Many of our members are busy entering these frequencies to their list.  My
> opinion is that they do not
> need to do this.  Am I wrong, and am I leading them astray?   What is the
> down-side of operating on a frequency that is not on the list?
>
> Thanks & 73,
>
> Tim N6GP
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] WSJT-X under Win 7 x64 and Icom Audio

[Peter Sumner]

Hello list members
I have a friend trying to start using WSJT-X under Win 7 x64 and connect to
his Icom 9700 via the USB cable which uses the Icom Audio Codec.
He can see the output audio device in the pull down list all okay but there
is no corresponding entry for the Input audio selector for the Icom USB
Audio codec.  I had told him to check device security then remembered he is
using Windows 10 which as far as I know did not get that security feature
added in any updates.

In the device manager you can see both Recording and playback devices and
other sound software like 'Audacity' shows both the in and out USB Audio
codecs that go to his 9700, just not in WSJT-X which only shows the output
device.

He has tried WSJT-X 2.01 and at my request WSJT-X 1.91 both with the same
result. He is quite computer literate so it is unlikely to be a newbie
computer user solution but had wondered if anyone had seen and solved
this issue previously?

regards,
Peter, vk5pj
Down Under in PF95
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Run Two Versions of FT8

[Peter Sumner]

Hi Dick,
 you can run as many versions as you like, the best way is to create
seperate config spaces by using the "wjstx.exe -r NAME"

I do this for each of my radio's with short cuts that look like this:

 C:\ham_radio\wsjtx\bin\wsjtx.exe -r 7600

 C:\ham_radio\wsjtx-2\bin\wsjtx.exe -r 910

which keeps all the config files in their seperate spots in your user
profile, creating a sand box for each to play in and there is no cross
polination of config files.

Regards,
Peter, vk5pj

On Tue, Dec 11, 2018 at 1:22 AM Richard Solomon  wrote:

> Will there be any issues if I want to run both (1.9 & 2.0)
> versions ?
> I could put one in C:\WSJT1.9 and the other in C:\WSJT2.0
> Directories. Create shortcuts to both.
>
> That way, I could close down one and then open the other.
>
> It seems to me a way to ease into the transition until the
> majority switch over to 2.0.
>
> Does anyone see any issues with doing this ?
>
> Tnx es HH, Dick, W1KSZ
>
> Sent from Outlook 
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] a good time set package for WSJT users

[Peter Sumner]

Hi,
 over the years I have tried many of the time sync options from Dimension 4
through to Meinberg NTP on a collection of PC's.

Over the last 5 years I have been using BKT time sync from here:
https://www.maniaradio.it/en/bkttimesync.html it has performed flawlessly
for me since install and now have it on 4 different Win 10 and XP machines.
It provides an occasional small popup bubble to sooth your fears of any
time error and remind you your PC is 'on time' (can be turned off)

It can do more than just internet time as it can be used to read a hardware
GPS for sync when you have no net connection, along with provide you with a
large GREEN clock in UTC (optional to turn on).

I have no connection with the author of the software other than a happy
user.

Peter
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] tone markers in JT65

[Peter Sumner]

Hello Dev team,
 while reading the last batch of posts here, I noticed a reference by
another that their system appear to jump into JT9 in certain circumstances
so while pondering what is going on with my RC5 install, I noticed the Red
TX marker on the waterfall is the size I would expect for JT9 and not the
wider one expected for JT65 A, B or C. When I do select JT65C I can start
to see the RX tone marker but all scrunched up together, yet decoding of
our local JT65B beacon works when I go back to JT65B.

When I select JT9 the RX and TX markers are the expected small complimentry
'u' and 'n' shapes, when I switch to JT65 the TX marker is the same narrow
one it was for JT9.

As best as I can tell the actual decoder seems to be happy but the logic
teling the Wide graph what to do seems to be confused.

O/S reasonably fresh install of Windows 10 Pro X64, all updates applied

Is it possible for others to please check the behaviour of the JT65 modes
(VHF/UHF features enabled) ?
Regards,
Peter, vk5pj

On Wed, Nov 28, 2018 at 10:17 AM Peter Sumner  wrote:

> Hello Dev team,
>   I was asked today about the tone markers in the Wide Graph when using
> JT65 as it would seem in V2.x these have been dropped.  Could not see any
> mention of this in the release notes but guess it was a development
> decision, just want to make sure it was not an unexpected outcome?
>
> A side by side screen capture (1.91 and 2.0 TC5)  is here:
> http://www.users.on.net/~pedroj/wsjtx/WSJT-JT65.JPG
>
> Regards,
> Peter vk5pj
>
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] tone markers in JT65

[Peter Sumner]

Hello Dev team,
  I was asked today about the tone markers in the Wide Graph when using
JT65 as it would seem in V2.x these have been dropped.  Could not see any
mention of this in the release notes but guess it was a development
decision, just want to make sure it was not an unexpected outcome?

A side by side screen capture (1.91 and 2.0 TC5)  is here:
http://www.users.on.net/~pedroj/wsjtx/WSJT-JT65.JPG

Regards,
Peter vk5pj
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] strategy for release of version 2.0 of WSJT-X

[Peter Sumner]

Hello to the Dev team,
  with the impeding release of version 2.0 'gold' in December I have
started to put threads into some of the more active local forums in VK to
alert those who may not know that a new MAJOR update of WSJT-X is coming
and that FT8 and MSK modes will be changing. I have requested that each
reader of the thread to consult the version 2.0 document on the WSTJ web
site to stay in touch with developing news.

I would guess the DEV team are busy with the finishing touches and tests of
version 2.0 and may not have a fully formed release strategy in mind but
thought I should ask is there more that can be done by us non dev Ham's on
your behalf to help out ?

Regards,
Peter, vk5pj
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Yaesu FT-847

[Peter Sumner]

Hello Alan (vk2ziw),
CAT is sort of important to WSPR users as this allows us to do automated
band hopping, it also helps to stop spotting of activity on the wrong band
(WSPR and other modes) as if WSJT-X has a CAT link then it will know when
you change the frequency on the rig and then change the band for spots
to WSPRnet / pskreporter and the ADIF export for your logging program.

How many times have you seen bad spots on WSPRnet (like over 10,000 Km on
144.489)?  most of these erroreous spots are from non CAT linked users that
have forgoten to update WSJT-X when they do a manual band change.

Peter, vk5pj

>> >From: Alan VK2ZIW 
>> >Sent: Monday, October 8, 2018 6:41 PM
>> >To: WSJT software development
>> >Subject: Re: [wsjt-devel] Yaesu FT-847
>> >
>> >Hi all,
>> >
>> >Why do you need CAT control at all?
>> >
>> >What's really needed is a rig with Stability.
>> >
>> >Any rig with a digital VFO will do.
>> >
>> >My 2c.
>> >
>> >Yes, I have an FT-840 and it's OK.
>> >
>> >Alan VK2ZIW
>> >
>> >
>> >On Mon, 8 Oct 2018 10:54:42 -0400, Karl Heinz Kremer wrote
>> >> FT-840UNI would be OK. “Early† or “NoGet† would require the
user to
>> know more about what’s going on with these devices.
>> >
>> >>
>> >>
>> >Karl Heinz - K5KHK
>> >>
>> >
>> >
>> >>
>> >
>> >> On Oct 8, 2018, at 10:52 AM, Black Michael > mdblac...@yahoo.com>> wrote:
>> >
>> >>
>> >> What can we call these earlier rigs to make the apparent in the
riglist?
>> >>
>> >
>> >> FT-840EARLY  ???
>> >> Or
>> >> FT-840UNI (unidirectional)
>> >> FT-840NOGET
>> >
>> >>
>> >
>> >> Or any better idea?
>> >>
>> >
>> >> de Mike W9MDB
>> >
>> >>
>> >
>> >>
>> >>
>> >
>> >>
>> >
>> >>
>> >
>> >>
>> >> On Monday, October 8, 2018, 9:47:05 AM CDT, Karl Heinz Kremer <
>> k...@khk.net> wrote:
>> >>
>> >
>> >>
>> >
>> >>
>> >> This also seems to be the case with my early Yaesu FT-840 - it can
>> receive CAT commands, but does not report anything back.
>> >
>> >>
>> >>
>> >
>> >> Karl Heinz - K5KHK
>> >>
>> >
>> >
>> >
>> >>
>> >> On Mon, Oct 8, 2018 at 10:44 AM Black Michael via wsjt-devel <
>> wsjt-devel@lists.sourceforge.net>
>> wrote:
>> >
>> >>
>> >> What version of WSJT-X are you using right now?
>> >>
>> >
>> >> Looks like we need a new rig entry for the earlier serial #'s and I
can
>> build you one for testing.
>> >>
>> >
>> >> de Mike W9MDB
>> >
>> >>
>> >
>> >>
>> >>
>> >
>> >>
>> >
>> >>
>> >
>> >>
>> >> On Monday, October 8, 2018, 9:34:22 AM CDT, Shane Stroud <
>> shanestroud1...@hotmail.com> wrote:
>> >>
>> >
>> >>
>> >
>> >>
>> >> I have discovered that the early serial numbered models of the Yaesu
>> FT-847 had unidirectional CAT.  Basically, the software can send
>> frequencies and modes to the rig, but the rig cannot respond.  This
applies
>> to serial numbers through about 8G. Mine is an 8E series.
>> >>
>> >
>> >> In any version of WSJT, under any operating system, the rig will set
>> frequency and mode, then error out because it cannot respond to polling.
>> >>
>> >
>> >> I'm not sure if this needs fixed in WSJT or in hamlib, but other
hamlib
>> programs seem to work with the rig without issue.
>> ___
>> >wsjt-devel mailing list
>> >wsjt-devel@lists.sourceforge.net
>> >https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>> >___
>> >wsjt-devel mailing list
>> >wsjt-devel@lists.sourceforge.net
>> >https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>> >
>> >
>> >
>> >
>> >Alan
>> >
>> >Evil flourishes when good men do nothing.
>> >Consider the Christmas child.
>>
>>
>---
>> >Alan Beard   Unix Support Technician from 1984 to today
>> >70 Wedmore Rd.   Sun Solaris, AIX, HP/UX, Linux, SCO, MIPS
>> >Emu Heights N.S.W. 2750  Routers, terminal servers, printers, terminals
>> etc..
>> >+61 2 47353013 (h)   Support Programming, shell scripting, "C",
>> assembler
>> >0414 353013 (mobile) After uni, electronics tech
>> >
>>
>>
>> --
>> Ham Radio NU0C
>> Lincoln, Nebraska, U.S.S.A.
>> TR7/RV7/R7A/L7, TR6/RV6, T4XC/R4C/L4B, NCL2000, SB104A, R390A,
>> GT550A/RV550A, HyGain 3750, IBM PS/2 - all vintage, all the time!
>>
>> "Give a man a URL and he will learn for an hour. Teach him to Google and
>> he will learn for a lifetime."
>>
>> HyGain 3750 User's Group - http://groups.yahoo.com/group/HyGain_3750/
>> http://incolor.inetnebr.com/jshorney
>> http://www.nebraskaghosts.org
>>
>>
>>
>>
>> ___
>> wsjt-devel mailing list
>> wsjt-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>>
>


--
Ham Radio NU0C
Lincoln, Nebraska, U.S.S.A.
TR7/RV7/R7A/L7, TR6/RV6, 

Re: [wsjt-devel] New feature request

[Peter Sumner]

Gary,
 please try enabling the "CQ Only" filter (left side of WSJT-x) and that
limits the display to those people sending only a CQ when using FT8, this
reduces the number of updates to the decoded screen, which should give you
time to react. you can un tick it later if you want to see the RAW feed : -)

Regards,
Peter, vk5pj

On Mon, Oct 8, 2018 at 7:10 AM Gary Hinson  wrote:

> It’s an annoying little race condition.
>
>
>
> Here’s an illustration:
>
>
>
>
>
> Milliseconds before I clicked, the mouse had been pointing at N7DED’s CQ …
> but just as my eyes read the line and my brain told my right index finger
> to click the mouse, the decodes scrolled up a line as shown here … hence I
> unintentionally clicked the CQ NA from EC5AC/6.   I’m not in NA and should
> not have called him.
>
>
>
> I wish the decodes would stop updating (either indefinitely or pause for a
> few seconds at least) while the mouse pointer is in the decode text area
> (not the scroll bar).  Sometimes I notice some juicy DX has appeared in a
> previous timeslot but on a busy band it is really tricky to scroll back,
> search for and click his decode while the decodes keep on updating and
> scrolling.  I know I can unselect Monitor but I don’t want to stop all
> decoding, just pause the decode text updates for a bit while I hunt for my
> prey.
>
>
>
> 73
>
> Gary  ZL2iFB
>
>
>
> > -Original Message-
>
> > From: Gary McDuffie 
>
> > Sent: 08 October 2018 08:31
>
> > To: chuck.fur...@gmail.com; WSJT software development 
> > de...@lists.sourceforge.net>
>
> > Subject: Re: [wsjt-devel] New feature request
>
> >
>
> >
>
> >
>
> > > On Oct 6, 2018, at 19:59, Chuck Furman  wrote:
>
> > >
>
> > > Several times I accidentally clicked on a station calling CQ DX or
> some other
>
> > directed CQ. This often happens just as the Band Activity window
> updates.  I click on a
>
> > CQ, but as the window updates, I find that I've actually clicked on
> another station who
>
> > was calling CQ DX.
>
> >
>
> > Sorry, I don’t get it.  The line is printed all at once.  DX appears at
> the same time CQ
>
> > appears on the same line on the same screen, so why are you clicking on
> it?  That
>
> > action seems only possible when the station changes his mind and sends
> his second CQ
>
> > as CQ DX after a prior unqualified CQ.
>
> >
>
> > Gary - AG0N
>
> >
>
> > ___
>
> > wsjt-devel mailing list
>
> > wsjt-devel@lists.sourceforge.net
>
> > https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Icom IC-700/RS-BA1/WSJT-X

[Peter Sumner]

Hello John and maybe others who might be interested.

  a simple chinese built multi pupose interface might be you saving grace
for your Icom 7700, I use them on multiple Icom rigs, (7600, 910, 275H,
475H etc).

Look for "2018 U5 USB PC linker" on ebay (may ned to set your setting to
world wide)

These have a USB conection to your PC and use the provided 8 pin DIN lead
to plug (ACC 1) into the back of 90% of full size icoms for Audio PTT etc,
there is also a 3.5mm jack for CIV so you can control the rig via this box
too...  use two 3.5mm jumper cables (supplied) to plug the audio to your PC

They are proced around $50 and work a treat in my experience.

Regards,
Peter, vk5pj

On Wed, Jul 4, 2018 at 3:20 AM, John Zantek  wrote:

> True, but with a rig that has an Ethernet port, more hardware shouldn't be
> necessary.  I know the Flex 6xxx works well with WSJT-X via the network.  I
> guess we need someone to clone the code so that it uses Icom's CAT commands
> and IP ports. It's not a Fortran thing, so I don't have that talent.
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] NA VHF Contest mode false triggers

[Peter Sumner]

Hi, some recent 50 MHz activity between Europe and VK/ZL has shown that the
dreaded popup for NA VHF Contest mode still occurs during normal operations.

When double clicking on a CQ from a europe station on 50 MHz, the popup
occurs and then takes focus, this popup is not always on top of the main
WSJT program and can be lost on a busy screen.

Is there a way that a complete disable can be included for this most
annoying popup inside WSJT-X? perhaps a tick box on the advanced page for
those who will never ever want to use this 'feature'?

I am using the latest GOLD build 1.91 but do have VHF/UHF features enabled
as I have been doing a series of experiment with QRA64-D for scatter modes
on 50 MHz.

Regards,
Peter Sumner, vk5pj
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Audio issue(s) with Win10 April 2018 update

[Peter Sumner]

Hi Dave,
 as the audio in you case is going via a signal link, that might be the
problem.  Try setting WSJT-X to send the audio to the local PC speakers and
see if the problem persists for you.  Then you will know if its the Signal
link drivers or some thing deeper inside the PC.

I have updated the shack PC here to that release of Win 10  (core I5 and
4GB of ram on 32bit windows) and use two external USB sound cards (Sound
Blaster), the internal sound card plus a direct USB to the IC-7600 via the
ICOM audio driver for 6mx EME... no audio breakups on anything so far and
my PC is pretty busy running WSPR on 144 all day long and 50 MHz EME at the
same time.

Hope you find an answer

Regards
Peter, vk5pj


On Thu, May 24, 2018 at 1:59 AM, Dave Crockett  wrote:

> Yeah, I kinda think it was a drivers issue, too.  If nothing else, my
> experience should be considered a ‘heads-up’ to anyone having a similar
> issue in Win10.  That option to “revert to a previous version of Windows”
> in Win10 has a pretty short window of opportunity and why I didn’t spend
> longer trying to noodle it out.
>
> Tnx all!
>
> 73,
> Dave WB4DFW (EM84…)
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] using freqcal on a single VHF beacon

[Peter Sumner]

Hello,
 following suggestions from others on this list I have tried to use freqcal
from WSJT-X 1.9.0-rc3 on a single GPS locked VHF beacon.

This beacon on 144.450 (VK5VF) runs a mixture of carrier and CW ID (on off
keying).  Each time I run the process that is outlined in the documentation
when I select the "solve for calibration"  I end up with the quite
unhelpful error telling me: "Calibration error  Check fmt.all for possible
bad data" so I dutifully look in this file to try and identify what is
wrong (sample below)

21:34:34 144450  1  1500  1368.324  -131.676   14.5   39.8
21:34:36 144450  1  1500  1369.671  -130.329   14.9   38.5
21:34:39 144450  1  1500  1369.555  -130.445   14.8   40.1
21:34:41 144450  1  1500  1368.284  -131.716   17.2   34.2
21:34:44 144450  1  1500  1368.318  -131.682   16.5   36.1
21:35:34 144450  1  1500  1369.171  -130.829   15.9   38.1
21:35:36 144450  1  1500  1369.574  -130.426   14.9   39.5
21:35:39 144450  1  1500  1369.270  -130.730   15.8   36.2
21:35:41 144450  1  1500  1370.659  -129.341   15.4   36.1
21:35:43 144450  1  1500  1372.416  -127.584   14.9   38.3
21:35:49 144450  1  1500  1371.663  -128.337   14.8   39.2
21:36:19 144450  1  1500  1373.065  -126.935   14.7   41.5
21:36:21 144450  1  1500  1372.527  -127.473   15.7   35.2
21:36:24 144450  1  1500  1372.356  -127.644   19.3   28.5
21:36:26 144450  1  1500  1372.464  -127.536   20.3   26.5
21:36:28 144450  1  1500  1372.826  -127.174   19.7   28.8
21:36:34 144450  1  1500  1370.782  -129.218   14.8   40.4
21:36:36 144450  1  1500  1370.859  -129.141   14.9   38.2
21:36:39 144450  1  1500  1371.701  -128.299   14.7   41.4
21:36:41 144450  1  1500  1371.060  -128.940   16.1   37.6
21:36:43 144450  1  1500  1371.607  -128.393   14.8   39.4
21:36:49 144450  1  1500  1373.245  -126.755   14.8   38.1

Can any of the list members help me identify which of these lines of data
would be in error?  Is the variance in offset too high as it goes from,
-126 to -131 Hz across the 30 second period,  When I try a smaller sample I
get the error telling me there is not enough information in the file, so
that did not help,

Regards,
Peter, vk5pj
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] a project for some one who likes to code?

[Peter Sumner]

Hello Joe,
 I am unsure how you would use the calibration technique on a single band
VHF or UHF radio, as unless the operator has a known reference signal to
use I can not see how that works.

There are no in band reference signals for them to use in VK and other GPS
locked signals may be very weak for them to find and net to,  Most
operators seem to be able to get to within 500Hz of centre but it would
seem there are always a few who fall out of passband.

In WSPR 2.11 I could go and run multiple copies of the EXE and set the
middle frequency +300 on one copy and  -300 Hz on the other and give myself
a panorama but under Win 10 WSPR 2.x gives lots of error and dies for me,
so gave up on that.

Back to the drawing board...   Oh is there any way to set the middle freq
on WSJT-X in WSPR mode, if so I could repeat my earlier multi copy trick.

Regards,
Peter.


On Mon, Apr 30, 2018 at 10:59 PM, Joe Taylor <j...@princeton.edu> wrote:

> Hi Peter,
>
> On 4/26/2018 7:56 PM, Peter Sumner VK5PJ wrote:
>
>>as WSPR has been around for a long time now its value is well known on
>> HF and 50 MHz but as frequency increases the ability to find rigs with the
>> needed frequency stability and accuracy is not always easy.
>>
>> There is a diverse group of operators in VK that have been running WSPR
>> on 144 and sometimes 432 for many year but not all of us have access to a
>> rig with accurate frequency ability.  I am lucky to have a IC-910 with the
>> VK3HZ XREF locking board to my GPS but some others rely on what was there
>> when bought.
>>
>
> It seems that your query is really not about frequency stability, but
> rather frequency calibration.  WSJT-X has an easy-to-use facility for
> calibrating your radio.  Anyone using WSPR on VHF and higher bands should
> definitely use this feature -- and preferably leave the radio on at all
> times, so that it's always "up to temperature".  It's not difficult to
> ensure that your WSPR signal is where you want it, certainly to within 10
> Hz or so, even at 144 or 432 MHz.
>
> -- 73, Joe, K1JT
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] a project for some one who likes to code?

[Peter Sumner]

Hello to you all,
  as WSPR has been around for a long time now its value is well known on HF
and 50 MHz but as frequency increases the ability to find rigs with the
needed frequency stability and accuracy is not always easy.

There is a diverse group of operators in VK that have been running WSPR on
144 and sometimes 432 for many year but not all of us have access to a rig
with accurate frequency ability.  I am lucky to have a IC-910 with the
VK3HZ XREF locking board to my GPS but some others rely on what was there
when bought.

Is there any way to optionally expand the RX window of WSPR to capture
those that are outside the current 200 Hz window?  (extra 100Hz either
side?)

I expect this would cause an overall degradation of decoding across the
board but for my intended use would be to run two instances of the
software, one with the 'normal' 200Hz windows and then a second (modified /
stripped down) version to capture those who never seem to be on frequency.

Thanks for your patience in reading this and I wish you a pleasant day

Regards,
Peter, vk5pj
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] set colour of WSJT-X when Dxpedition mode it selected

[Peter Sumner]

Hello Dev team,
I am unsure if this can be done or is really desirable but could selecting
FT8 dxpedetion mode also change the whole colour scheme of WSJT-X to some
bright colour as a warning that is now selected?

It would seem WSJT-X needs to cater for those who have little regard for
others and in some areas dumb it down, which is something I thought I would
never have to say.

Regards,
Peter.
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Feature request: WSJT-X

[Peter Sumner]

Hello Bill,
  for a lot of my EME contacts on 50 MHz I had been using WSJT10, which
cannot do PTT via CAT so have changed over to use WSJT-X for these contacts
now as I have recently moved the IC-7600 to use only the onboard USB
interface in the radio to reduce the complexity of the shack PC as it had
three sound cards on it and multiple serial devices.  I am still trying to
find a good combination of settings to get the same decode rates as WSJT10
gave me on 50 MHz EME signals so at present there is a bit of fiddling
going on.

In the last few days have been running tests with Rex VK7MO on QRA64 on
144, he has a birdie on the standard QRA64 freq so we have moved up a bit,
in a similar way I have been experimenting with configurations to seek the
best decodes from WSJT-X and again come across the behavior of being QSY'd
back to the standard frequency mid experiment.

It would seem my difficulty is not very common so maybe I should just stop
fiddling : -)

Regards,
Peter, vk5pj

On Sat, Mar 17, 2018 at 7:08 AM, Bill Somerville <g4...@classdesign.com>
wrote:

> On 16/03/2018 20:29, Peter Sumner wrote:
>
>> eg. on WSPR, 144.489 if I type into the box as you suggested (not tried
>> that before I must admit), my test frequency was 144.085 which moved the
>> rig all okay, then if I open the settings menu and close I am now set back
>> to be on 144.489. This is the behaviour I would like to be able to
>> temporarily supress but still be able to use PTT via CAT.
>>
>> Hi Peter,
>
> can you explain why you need to open the settings menu mid-QSO please?
> This seems to be the root of the issue you are describing.
>
> 73
> Bill
> G4WJS.
>
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Feature request: WSJT-X

[Peter Sumner]

Hello Joe,
   I have just tried your suggested method, if I then go to the
configuration menu and press okay, when it returns to the main interface,
the rig reverts to the SET frequency for the WSJT mode selected.

eg. on WSPR, 144.489 if I type into the box as you suggested (not tried
that before I must admit), my test frequency was 144.085 which moved the
rig all okay, then if I open the settings menu and close I am now set back
to be on 144.489.  This is the behaviour I would like to be able to
temporarily supress but still be able to use PTT via CAT.

Regards,
Peter, vk5pj

On Fri, Mar 16, 2018 at 11:19 PM, Joe Taylor <j...@princeton.edu> wrote:

> Hi Peter,
>
> On 3/16/2018 1:28 AM, Peter Sumner VK5PJ wrote:
>
> I would like to see if it would be possible to include a toggle on the
>> main GUI that stops WSJT-X sending frequency set commands to the
>> transceiver.
>>
>
> I do manual QSYs all the time when using WSJ-X on VHF bands.  It's as
> simple as typing the desired new frequency into the band-selector drop-down
> control.  For example, I might type "50.285" (or abbreviated as "285k")
> into this window to escape a birdie on 20.260.
>
> Doesn't this capability address your problem?
>
> -- 73, Joe, K1JT
>
>
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Feature request: WSJT-X

[Peter Sumner]

>
> Hello,
>

firstly my thanks to those who are at the coal face developing WSJT and its
brothers.

I would like to see if it would be possible to include a toggle on the main
GUI that stops WSJT-X sending frequency set commands to the transceiver.
When I control my IC-7600 and my IC-910 with WSJT-X it does a great job of
setting the rig to the right frequency for the mode but some times there is
a need to be on a non standard frequency if some one has a birdie or
chasing EME.  I find if I go into the settings menu and then come out, (to
check a setting which we all do some times) the software does a frequency
set to the rig and I end up back on a standard frequency for that mode,
which is for those times very un helpful especially when chasing EME on 50
MHz

I had in the past set WSJT-X to be "no rig" to stop this but now I need to
send PTT via CAT to the IC7600 so cannot use that strategy now.

Could the big Green / Red indicator next to the frequency readout be made
into a toggle ? then a mouse click could change the rig mode, add the
colour BLUE (first colour that jumped into my head) to represent the rig
frequency will not be set by the software? (does not require any new GUI
real estate to add the feature).  Then a simple mouse click on the
tri-coloured dot can put it back to GREEN for automated setting of the rig.

Unsure if it is only me that experiences this in day to day operating, if
no others support it, then I expect this will not make it through.

Regards,
Peter, VK5PJ
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] tx audio equalisation, just a thought.

[Peter Sumner]

Hello Mike,
 can you offer some URL's as I have exhausted my google searches for both
of those suggestions... all I get is topic about fishing for rig split and
fake it gives me pages of topics about the US president and his fake news.
have tried various other combinations but as I do not know what they are
meant to do it is hard to refine the searches.

Peter.

On Fri, Jan 26, 2018 at 3:30 PM, Black Michael via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:

> You run either rig split or fakeit.  That keeps all your audio in the
> 1500-2000 range.
>
> de Mike W9MDB
>
>
>
> On Thursday, January 25, 2018, 7:02:45 PM CST, Peter Sumner <
> vk8...@gmail.com> wrote:
>
>
> Hello,
>  first off, sorry if this subject has already been discussed and resolved
> but could not see anything on my searches.
>
> As the owner of an older Icom VHF SSB rig, I have a seemingly common
> problem that my TX pass band is not flat, in fact using QRA64-D earlier
> today with Rex, VK7MO revealed a significant ripple across the tones (about
> 3db) seen on the Bird output power meter.
> As I am unsure how much control there is over the level of the tones
> generated by WSJT-X but I wondered if there is a way to build in a simple
> level control for TX tones across the passband?
> In my head I had thought an adjuster for 500-750 750-1000 1000-1250 and so
> on and be able to change the nominal value from 0db (flat) to be -1db or
> +1db for each segment of the decided passband...
>
> Maybe others have a better way of managing this that is not part of WSJTX?
>
> Regards,
> Peter, vk5pj
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot__
> _
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] tx audio equalisation, just a thought.

[Peter Sumner]

Hello,
 first off, sorry if this subject has already been discussed and resolved
but could not see anything on my searches.

As the owner of an older Icom VHF SSB rig, I have a seemingly common
problem that my TX pass band is not flat, in fact using QRA64-D earlier
today with Rex, VK7MO revealed a significant ripple across the tones (about
3db) seen on the Bird output power meter.
As I am unsure how much control there is over the level of the tones
generated by WSJT-X but I wondered if there is a way to build in a simple
level control for TX tones across the passband?
In my head I had thought an adjuster for 500-750 750-1000 1000-1250 and so
on and be able to change the nominal value from 0db (flat) to be -1db or
+1db for each segment of the decided passband...

Maybe others have a better way of managing this that is not part of WSJTX?

Regards,
Peter, vk5pj
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] NA VHF Contest mode

[Peter Sumner]

Hi Dev team,
   since the inclusion of "NA VHF Contest mode" in WSJT a lot of VK and I
believe also ZL operators get to see a popup from WSJT-X that wants them to
enable "Contest Mode?".  I have spoke directly to many that have
experienced this and a lot of them have just stopped using WSJT-X in favor
of the MSHV software to avoid the error.

All those I have asked about this assure me they do not have the tick in
the contest mode option but we still see this from WSJT-X during normal
operations on MSK144 & FT8 (screen grab attached)

Could an option be included in WSJT-X that forcibly disables the popup /
mode or some way for us to be rid of this?  In many case the pop up box
gets missed on a PC with a busy desktop and the OP wonders why WSJT-X has
stopped responding.

If there is any extra testing needed to chase this down,, I am happy to
provide as much detail as I can muster.

Regards,
Peter Sumner, VK5PJ from down under
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] hamlib not found while building wsjtx

[Peter Sumner]

Hi,
 hope this is the right list to ask this question, have been building
wsjt-x and others on my home pc (Windows 10 x86) for about 2 years now and
not ever struck a problem until the last few days when I decided to try
building wsjt-x 1.8  to see if the "NA Contest mode" popup was still going
to appear (separate problem we experience in VK land).

Went through the normal processes and issued a 'build-wsjtx -rinstall' to
test things still worked for a version 1.7x build but now get this odd
error telling me HAMLIB is not found.  Oh yes I had issues the UPDATE and
UPGRADE commands before I run the build (silly me)

-- Found hamlib
CMake Error at
C:/JTSDK/cmake/share/cmake-3.0/Modules/FindPackageHandleStandardArgs.cmake:136
(message):
  Could NOT find hamlib (missing: hamlib_LIBRARY_DIRS) (Required is at least
  version "3")
Call Stack (most recent call first):

C:/JTSDK/cmake/share/cmake-3.0/Modules/FindPackageHandleStandardArgs.cmake:343
(_FPHSA_FAILURE_MESSAGE)
  CMake/Modules/Findhamlib.cmake:81 (find_package_handle_standard_args)
  CMakeLists.txt:857 (find_package)


Now I know hamlib is there as I can build it with no errors, but the
JTSDK-QT session refuses to see it

---
  ADDING BUILD INFO [ Hamlib3.build.info ]
---

  Creating Hamlib3 Build Info File
  Finished


  FINISHED INSTALLING [ Hamlib3 ]


  Tool-Chain: QT 5.2
  Source Location...: C:/JTSDK/src/hamlib3/src
  Build Location: C:/JTSDK/src/hamlib3/build
  Install Location..: C:/JTSDK/hamlib3
  Package Config: C:/JTSDK/hamlib3/lib/pkgconfig/hamlib.pc

vk5pj@QRV-024~/hamlib-prefix/build$

Even if I try a build for 1.8 : "build-wsjtx -b dev -n wsjtx-1.8 -c release
-t install" I get the same error.

I have done the obligitory google searches about this and see reference to
replacing the hamlib folders but have no friends close by that have the
same JTSDK installed..

any clues please?  or should I just run the gold releases?

Regards,
Peter Sumner, vk5pj
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel