Date   

locked Re: Version 2.4.0 ate my adi file #IssueReport #logging

Julian Topolski
 

OK Paul I will email it to you.

73, Julian KR5J


locked Re: Icom 703+ and WSJT #Icom

Joe Subich, W4TV
 

Old habits. I have lots of cables with 13 pin and lots of 13 pin
connectors on hand from my days selling SCS modems.
According to the manual, SSB-D works with the ACC (13 pin DIN)
connector.

73,

... Joe, W4TV


On 2021-06-11 9:10 AM, Don Melcher wrote:
On Thu, Jun 10, 2021 at 06:11 PM, Joe Subich, W4TV wrote:


If you would use SSB-D you would not need to remove the mic (Note:
on page 69 of the IC703 Instruction Manual).
Old habits. I have lots of cables with 13 pin and lots of 13 pin connectors on hand from my days selling SCS modems. They’re a lot easier to solder to then Mini-DIN.
--
Don
W6CZ/W6ZB
DM07bk


locked Re: Icom 703+ and WSJT #Icom

Robert Newell <coffeecanuck@...>
 

The ICOM 703+ is now on the air and talking nicely with my Lenovo laptop -

All the advice was perfect - needed a couple of tweaks in my settings and I was good
to go.

Many thank you's to all the folks that jumped in so quickly.

Colin - VA7WWV - CN88


locked Re: WSJT-X and N1MM and GridTracker-can they all work together?

John
 

Or you could try "com-0-com".

John
VE7KKQ


On Fri, Jun 11, 2021 at 2:13 AM Gerrit via groups.io <hf-sparks=quicknet.nl@groups.io> wrote:

Hello Arthur,

 

Maybe you can use LBP2 software, with this program multiple programs can share 1 port.

I dont work with it so you have to read the manual.

LP-Bridge (telepostinc.com)

 

73’s

Gerrit – PA3DJY

 

Van: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] Namens Arthur Tanner via groups.io
Verzonden: maandag 7 juni 2021 16:43
Aan: main@WSJTX.groups.io
Onderwerp: [WSJTX] WSJT-X and N1MM and GridTracker-can they all work together? #N1MMlogger

 

This three-some would make a great display for Field Day, but N1MM and GridTracker seem to share the same ports, and although I get N1MM working well with WSJT-X, I  can't seem to add GridTracker.   Does anyone have a solution?  Thanks.





locked Re: 2.5 RC1 #wsjt-x-crashing

ny2ny
 

Hi Joe - hope u are well...yes of course I suspected some local problem here -- uninstalled all versions of WSJT and did fresh install of 2.5.0 rc1 and problem seems to have been resolved. At the time of the repeated crashes i was running 2 programs of WSJT simultaneously and transmitting on 1296 ft8. Problem was not there on 2m so I now suspect 1296 RF was getting into my computer (running 200w to antenna directly over my shack)...have not been able to duplicate it again...hope I cant hihi....Thanx for all your work on WSJT over the years- it sure has transformed ham radio, especially on the VHF/UHF bands.
73 - stay safe
--
jay ny2ny


locked Re: VS: [WSJTX] Q65 and non-linear RF power amplifiers #Q65

Steve Kavanagh
 

Hi Peter

Yes, I saw your posting earlier...an interesting thread.  I am not sure I understand what the reasons are for the ramp up and down.  My interest in Q65 is really for VHF and up, where Class D and E amps are mostly impractical (though getting closer over time as technology improves), but running a Class C amp (or class A or AB in hard saturation) is easy.  I'm guessing there would be no equivalent issue with the ramps in this case, though I suppose there might be a momentary increase in dissipation.  But it would be helpful to know the waveform and what one gives up by eliminating the ramps.

74,
Steve VE3SMA


locked Re: #Band #band

Bill Somerville
 

On 11/06/2021 12:24, James Quick wrote:

I am going to try this again,

I am running a MacOS Big Sur, IC-7300, with WSJT-X. I can start WSJT-X v2.3.1 and everything is ok. If change bands on WSJT-X 2.3.1 the 7300 changes bands. I close v2.3.1 and start v2.5.0 rc1 it starts as it should but if I try to change bands it will not change on the program or the 7300. I can manually change bands on the 7300 and it will change the band on WSJT-X. None of the updates after v2.3.1 will work. I am at a complete loss as to what to do. I have uninstalled the program, deleted the INI file, and reinstalled the program with no luck. Any help would be a big help.


73


Jim Quick / N4ULE / Ex KA4BEG

Hi Jim,

please put the attached file into your WSJT-X configuration files directory (on macOS that is ~/Library/Preferences), then restart WSJT-X and do a minimal test that demonstrates the issue. In this case that would seem to be merely a band change using the WSJT-X band selection drop-down list. Then quit WSJT-X. It will have created a file on your Desktop called WSJT-X_RigControl.log , send me that file for analysis please (g4wjs <at> classdesign <dot> com).

Once you have sent the log file you can delete it from your Desktop and also delete the log configuration file to revert to normal operation.

73
Bill
G4WJS.


locked Re: Icom 703+ and WSJT #Icom

Don Melcher
 

On Thu, Jun 10, 2021 at 06:11 PM, Joe Subich, W4TV wrote:
If you would use SSB-D you would not need to remove the mic (Note:
on page 69 of the IC703 Instruction Manual).
Old habits. I have lots of cables with 13 pin and lots of 13 pin connectors on hand from my days selling SCS modems. They’re a lot easier to solder to then Mini-DIN. 
 
--
Don
W6CZ/W6ZB
DM07bk


locked Re: Call for information about PC systems being used for WSJT-X #general

Derek Brown
 

Hi Bill

Here's the info for the three PC's I use

IC756  - Intel(R) Core(TM)2 Duo CPU E7400 2.80Ghz

IC7610 - Intel(R) Core(TM) i5 CPU @3.20Ghz

IC9700 - Intel(R) Core(TM)2 Duo CPU     E7400  @ 2.80GHz   2.80 GHz

OS on all Win10

73 Derek G8ECI
On Wednesday, 9 June 2021, 00:37:35 BST, Bill Somerville <g4wjs@...> wrote:


Hi all WSJT-X users,

we are looking into some performance enhancements that will take
advantage of some parallel processing features of modern CPU
architectures. In order to gauge how much backwards compatibility for
older CPUs we will have to implement it would help to know who is using
such older processors. Please don't turn this thread in to a mine is
better than yours conversation, all I need to know is who or how many of
you are using the older CPU architectures. Note that this applies to MS
Windows, Intel Linux, and Intel macOS users, it is about CPUs not
operating systems.

The technology we will use is called AVX and that is present on all
Intel CPUs branded Core i3/i5/i7/i9 (circa 2010 to present), it is also
present on AMD CPUs since the Jaguar or Puma based CPU models (some late
Athlon-II CPUs, all Zen based CPUs, including Ryzen) circa 2013 to present.

Notably Intel CPUs branded Celeron, Pentium, or Atom do not support the
AVX technology.

So in summary, look up your CPU and if it **does not support AVX**

73
Bill
G4WJS.





locked #Band #band

James Quick
 


I am going to try this again,

I am running a MacOS Big Sur, IC-7300, with WSJT-X. I can start WSJT-X v2.3.1 and everything is ok. If change bands on WSJT-X 2.3.1 the 7300 changes bands. I close v2.3.1 and start v2.5.0 rc1 it starts as it should but if I try to change bands it will not change on the program or the 7300. I can manually change bands on the 7300 and it will change the band on WSJT-X. None of the updates after v2.3.1 will work. I am at a complete loss as to what to do. I have uninstalled the program, deleted the INI file, and reinstalled the program with no luck. Any help would be a big help.


73


Jim Quick / N4ULE / Ex KA4BEG

Sent with Shift


locked Re: VS: [WSJTX] Q65 and non-linear RF power amplifiers #Q65

Peter Hall, VK6HP
 

Hello Steve,

I was the poster who raised the issue with the FST4(W) waveforms in this forum and in the RSGB LF group.  You can see the later part of the discussion here:

https://wsjtx.groups.io/g/main/topic/79269122#20188

The problem arises because, at some point in the chain, the analog drive signal has to be converted to digital form, preferably with as little jitter as possible.  Typical squaring circuits have a dead or indeterminate band - however tiny - and, with very slow envelopes, produce erratic pulse drive to the (very widely used) Class D or E PAs, the designs of which typically requires a well-tempered pulse train.  As you see from the previous discussion there are several solutions possible, the most satisfactory being the setting of the environment variable as outlined by Bill.

I haven't tried Q65 yet but can do so in the next week.  Whether there's a problem will depend on the how slow the envelope rise and fall is.  I agree it'd be handy to have some descriptions or, better yet, sketches of the various WSJT mode signals.

73, Peter.


locked Re: Call for information about PC systems being used for WSJT-X #general

Bill Somerville
 

Hi Rick,

my apologies, you are correct, the Core i3-370M does not support AVX:


73
Bill
G4WJS.

On 11/06/2021 11:26, Rick Chapman wrote:

Hi Bill

Thanks for the response.

However, I'm unable to see AVX mentioned under the Core I3-370M processor column in the attachment.

The second column which does include AVX is for a different processor - Core I7-2600.

I extracted the data on the two processors I use for wsjt-x, the I3 is in the shack laptop and the I7 is in a desktop in another building, which I often use to run wsjt-x remotely  by piping the audio to and from the shack laptop over the lan.

I'd be happy if the laptop I3 does support AVX but i don't think so.

Cheers

Rick (GM4JIB)

On 09/06/2021 11:23, Bill Somerville wrote:
Rick,

that's not correct, the information that your CPU supports AVX is right there in the screen capture you attached!

73
Bill
G4WJS.

On 09/06/2021 09:46, Rick Chapman wrote:

Hi Bill

I'm currently running an Intel Core I3-370M processor, which apparently does not support AVX (see attached under Instruction Set Extensions)

Data from https://ark.intel.com/content/www/us/en/ark/compare.html?productIds=52213,49020

Cheers

Rick (GM4JIB)



locked Re: Call for information about PC systems being used for WSJT-X #general

Rick Chapman
 

Hi Bill

Thanks for the response.

However, I'm unable to see AVX mentioned under the Core I3-370M processor column in the attachment.

The second column which does include AVX is for a different processor - Core I7-2600.

I extracted the data on the two processors I use for wsjt-x, the I3 is in the shack laptop and the I7 is in a desktop in another building, which I often use to run wsjt-x remotely  by piping the audio to and from the shack laptop over the lan.

I'd be happy if the laptop I3 does support AVX but i don't think so.

Cheers

Rick (GM4JIB)

On 09/06/2021 11:23, Bill Somerville wrote:

Rick,

that's not correct, the information that your CPU supports AVX is right there in the screen capture you attached!

73
Bill
G4WJS.

On 09/06/2021 09:46, Rick Chapman wrote:

Hi Bill

I'm currently running an Intel Core I3-370M processor, which apparently does not support AVX (see attached under Instruction Set Extensions)

Data from https://ark.intel.com/content/www/us/en/ark/compare.html?productIds=52213,49020

Cheers

Rick (GM4JIB)

On 09/06/2021 00:37, Bill Somerville wrote:
Hi all WSJT-X users,

we are looking into some performance enhancements that will take advantage of some parallel processing features of modern CPU architectures. In order to gauge how much backwards compatibility for older CPUs we will have to implement it would help to know who is using such older processors. Please don't turn this thread in to a mine is better than yours conversation, all I need to know is who or how many of you are using the older CPU architectures. Note that this applies to MS Windows, Intel Linux, and Intel macOS users, it is about CPUs not operating systems.

The technology we will use is called AVX and that is present on all Intel CPUs branded Core i3/i5/i7/i9 (circa 2010 to present), it is also present on AMD CPUs since the Jaguar or Puma based CPU models (some late Athlon-II CPUs, all Zen based CPUs, including Ryzen) circa 2013 to present.

Notably Intel CPUs branded Celeron, Pentium, or Atom do not support the AVX technology.

So in summary, look up your CPU and if it **does not support AVX** (https://en.wikipedia.org/wiki/Advanced_Vector_Extensions) then let me know.

73
Bill
G4WJS.






locked Re: Not seeing stations previously worked/needed, plus JTAlert problems #logging

neil_zampella <neilz@...>
 

There's no 'bug' in JTAlert ... the problem that's being referred to recently is the issue with the MS .NET update causing sound problems.
It has nothing to do with not displaying colors as that has been found to be issues with not having the UDP settings properly set.

Neil, KN3ILZ

On 6/11/2021 12:44 AM, Chris Levingston wrote:

Hi, Bill - thanks for the quick response.

I have uninstalled JTAlert as the author has found a bug and is working on it.

WSJT-X no longer shows the colour alerts that worked fine until the upgrade - ATNO, worked, etc.
I keep screen shots of every installation and there has been no change since v2.2.0 which is what I just upgraded from.

73s,

Chris    VK5SA



locked Re: Can't access F3, F5, F11 and F12 in v250.0 #install

neil_zampella <neilz@...>
 

I would report this to the HAMAPPS support list on groups.io, WSJT-X has nothing to do with these function keys.

Neil, KN3ILZ

On 6/11/2021 2:46 AM, Chris Levingston wrote:

I can't get any of these to work clicking on them in the View window or using the Function keys.

So, no Activity window, among others!

I have gone back to v2.16.4 so missing all of the new features.

Help!

Chris



locked Re: WSJT-X and N1MM and GridTracker-can they all work together?

Gerrit
 

Hello Arthur,

 

Maybe you can use LBP2 software, with this program multiple programs can share 1 port.

I dont work with it so you have to read the manual.

LP-Bridge (telepostinc.com)

 

73’s

Gerrit – PA3DJY

 

Van: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] Namens Arthur Tanner via groups.io
Verzonden: maandag 7 juni 2021 16:43
Aan: main@WSJTX.groups.io
Onderwerp: [WSJTX] WSJT-X and N1MM and GridTracker-can they all work together? #N1MMlogger

 

This three-some would make a great display for Field Day, but N1MM and GridTracker seem to share the same ports, and although I get N1MM working well with WSJT-X, I  can't seem to add GridTracker.   Does anyone have a solution?  Thanks.


locked Re: Call for information about PC systems being used for WSJT-X #general

Lars Berg
 

Download free https://www.ccleaner.com/speccy/download , install and run. Look at CPU > Instructions

Does it containe AVX? My Fujitsu Esprimo does not. ( My Dell XPS does. )

 

Intel Pentium G4400T

                             Cores                 2

                             Threads             2

                             Name                 Intel Pentium G4400T

                             Code Name     Skylake

                             Package            Socket 1151 LGA

                             Technology      14nm

                             Specification   Intel Pentium CPU G4400T @ 2.90GHz

                             Family                6

                             Extended Family                         6

                             Model                E

                             Extended Model                        5E

                             Stepping           3

                             Revision            R0

                             Instructions     MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, Intel 64, NX, VMX, AES

73 de Lars SM3CCM

 

Skickades från E-post för Windows 10

 

Från: John Deegan
Skickat: den 11 juni 2021 06:28
Till: main@WSJTX.groups.io
Ämne: Re: [WSJTX] Call for information about PC systems being used for WSJT-X #general

 

As I understand the technology, my desktop PC (an older Sandy Bridge I-7 2600K) is capable of supporting AVX.

73s de John K9XT

-----Original Message-----
From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of Bill Somerville
Sent: Tuesday, June 8, 2021 7:37 PM
To: WSJTX@groups.io
Subject: [WSJTX] Call for information about PC systems being used for WSJT-X #general

Hi all WSJT-X users,

we are looking into some performance enhancements that will take advantage of some parallel processing features of modern CPU architectures. In order to gauge how much backwards compatibility for older CPUs we will have to implement it would help to know who is using such older processors. Please don't turn this thread in to a mine is better than yours conversation, all I need to know is who or how many of you are using the older CPU architectures. Note that this applies to MS Windows, Intel Linux, and Intel macOS users, it is about CPUs not operating systems.

The technology we will use is called AVX and that is present on all Intel CPUs branded Core i3/i5/i7/i9 (circa 2010 to present), it is also present on AMD CPUs since the Jaguar or Puma based CPU models (some late Athlon-II CPUs, all Zen based CPUs, including Ryzen) circa 2013 to present.

Notably Intel CPUs branded Celeron, Pentium, or Atom do not support the AVX technology.

So in summary, look up your CPU and if it **does not support AVX**
(https://en.wikipedia.org/wiki/Advanced_Vector_Extensions) then let me know.

73
Bill
G4WJS.


 


locked Can't access F3, F5, F11 and F12 in v250.0 #install

Chris Levingston VK5SA
 

I can't get any of these to work clicking on them in the View window or using the Function keys.

So, no Activity window, among others!

I have gone back to v2.16.4 so missing all of the new features.

Help!

Chris


locked Re: Call for information about PC systems being used for WSJT-X #general

David Redman
 

Bill,
Many thanks for your detailed explanation of the need for AVX implementation , which makes total sense to me.
As you know I am a keen user of MAP65 and fully support this AVX development for use on Q65 decoding and other areas of the WSJT-X / MAP65 applications.

Keep up the great work
Dave
G4IDR



On Fri, 11 Jun 2021 at 01:05, Bill Somerville <g4wjs@...> wrote:
On 09/06/2021 00:37, Bill Somerville wrote:
> Hi all WSJT-X users,
>
> we are looking into some performance enhancements that will take
> advantage of some parallel processing features of modern CPU
> architectures. In order to gauge how much backwards compatibility for
> older CPUs we will have to implement it would help to know who is
> using such older processors. Please don't turn this thread in to a
> mine is better than yours conversation, all I need to know is who or
> how many of you are using the older CPU architectures. Note that this
> applies to MS Windows, Intel Linux, and Intel macOS users, it is about
> CPUs not operating systems.
>
> The technology we will use is called AVX and that is present on all
> Intel CPUs branded Core i3/i5/i7/i9 (circa 2010 to present), it is
> also present on AMD CPUs since the Jaguar or Puma based CPU models
> (some late Athlon-II CPUs, all Zen based CPUs, including Ryzen) circa
> 2013 to present.
>
> Notably Intel CPUs branded Celeron, Pentium, or Atom do not support
> the AVX technology.
>
> So in summary, look up your CPU and if it **does not support AVX**
> (https://en.wikipedia.org/wiki/Advanced_Vector_Extensions) then let me
> know.
>
> 73
> Bill
> G4WJS.

Hi all,

thanks for all those who took the time to check their systems and report
those without AVX support. That has helped to get a broad picture of the
numbers with older CPUs that pre-date this feature. Not unsurprisingly a
significant proportion lack AVX, this is almost certainly due to systems
being acquired second-hand, repurposed from other uses, or kept for
extended periods as they are more than adequate for the average shack
PC.  Some have suggested that we should not abandon owners of these
older PCs, don't worry as that has never been the intention of this
exercise, here is some background that should help to clarify what may
happen.

The MAP65 application, as of WSJT-X v2.5.0 RC1 has been updated to
decode Q65 signals, this is because we feel certain that Q65 is superior
for EME use on all bands and the prior JT65 decoding ability will be
superseded by Q65. The MAP65 decoder is able to decode many signals
across a wide pass-band, and also implements polarization diversity with
suitably equipped stations. Automatic linear drift compensation has also
been added to compensate for less well specified stations. This all
requires a lot of signal processing effort, but users expect signals to
be decoded in the short interval between the end of transmission and the
start of the next period (note with EME the path delay means that up to
2 1/2 seconds of that interval is lost compared with terrestrial paths).
The first use of hand coded micro-optimizations using AVX instructions
on suitable CPUs will be aimed at getting Q65 decodes done faster in
MAP65. Because the Q65 decoder is shared by WSJT-X and MAP65, the same
optimizations will be there for WSJT-X Q65 users. None of this is
particularly relevant to the survey of CPUs done here as I am sure that
PC costs are such a small part of the typical EME station investment
that users will find a way to upgrade their PCs if necessary.

So why did I ask the question about AVX? Once we start using AVX for
some parts of WSJT-X it makes sense to find other opportunities for
similar hand coded micro-optimizations elsewhere in out code base, not
only that but once implemented we may well choose to increase the
decoding depth of other decoders by taking advantage of such performance
gains. The net effect would be that those with AVX equipped PCs will see
faster and deeper decoding, those with older PCs will see the same extra
depth but overall decoding will take longer than before. My aim was to
judge what proportion of users might suffer this speed degradation
versus those that will see both faster and deeper decoding.

To reassure those that may have misunderstood, there is no intention to
exclude users from the latest WSJT-X enhancements just because they have
older CPUs. We would implement AVX implementations of critical
algorithms alongside their current linear implementations and the choice
of which to use would be made at runtime according to the available CPU
features. Note exactly this already happens in the FFT library we use
called FFTW3, so WSJT-X and MAP65 users have always had AVX specific
algorithm implementations for FFT calculations if the CPU they run on
supports them. We are investigating coding other critical algorithms in
a similar fashion. Notwithstanding that, we also have no intention of
dropping support for ARM CPU architectures like the Raspberry Pi, yet we
have no intention of similar hand coded micro-optimizations for that
platform since the required tools do not exist, so for that platform our
linear implementations would still be used, just like on non-AVX Intel
or AMD CPUs.

73
Bill
G4WJS.





locked Re: Not seeing stations previously worked/needed, plus JTAlert problems #logging

Chris Levingston VK5SA
 

Rolling back to an older version of JTAlert fixed the problem - strange.....

14461 - 14480 of 40054