Date   

locked Re: WSJT not driving 7610

Bill Somerville
 

On 16/03/2020 23:43, eam1212003 via Groups.Io wrote:
So I just upgraded to 1.20 from 1.06. No prob with radio in cw or ssb. WSJT gives me no power out. CAT is fine, audio is fine, codec...in fact all my settings in WSJT are as they were before upgrade...any suggestions what to look at...

Tnx Eli, N6PF
Hi Eli,

what did you upgrade? I don't recognize those version numbers.

73
Bill
G4WJS.


locked Re: WSJT not driving 7610

Lawrence (VA3IQ)
 

Menu->Set->Connectors->USB AF/IF Output->Output Select AF and AF Output Level 30%

Hit the USB key on the transmit side of the touch screen.
Hit the Data key on the mode select that pops up.

Should toggle to USB-D2.

Hope this helps.

Lawrence



On Mon, Mar 16, 2020 at 7:49 PM eam1212003 via Groups.Io <eam1212003=yahoo.com@groups.io> wrote:
Indeed I am in “regular” usb...how do I get to D-2.  Sorry, newbie here


locked Re: Seeing a Lot of Skipping Decodes Every Other Sequence FT8

Hasan Schiers N0AN
 

I have no idea if it's the cause, Laurie. I will stop using it simply because when it runs in my system, X misbehaves. I can't exactly stop using X.

We pursued all sorts of diagnostics in X and learned absolutely nothing.

I really don't know a darn thing, so absent anything concrete,  all I can do is eliminate what I can,  one thing at a time and see what happens.

That's what I'm stuck with, which is very disappointing because JTA is one of my favorite programs.

Maybe some day someone will stumble on to the cure for this particular problem.  There have been plenty of other reports of missing decode sequences where JTA is not being used.

Something isn't right. Maybe more than one thing.

73, N0AN 

On Mon, Mar 16, 2020, 6:11 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
On 17/03/2020 9:26 am, Hasan Schiers N0AN wrote:
On a busy FT8 Band like 20m, I'm seeing more and more tendencies to skip an entire sequence following a decoded sequence.

I'm on 20m FT8 now and it is happening nearly every other sequence, or it will decode 2 seq in a row and then start skipping again, without any intervention on my part.

Then it will start decoding again, do several sequences in a row (with me not transmitting, just monitoring), and then skip another sequence. I just watched it do it again while typing.

I have stopped interacting with the program, I am just letting it run with no intervention, receiving:

Two more in a row of > 20 stations
Then skipped an entire sequence
Full seq of decodes > 20
Skipped the next sequence
Full seq of decodes > 20 stations
Skipped the next seq
Full seq of decodes > 20 stations
Skipped the next seq: no decodes
Full seq of decodes > 20 stations
Skipped the next seq: no decodes
Full seq of decodes > 20 stations
Skipped the next seq.

The computer running the X software is not being touched. I'm typing on a different machine.

WSJT-X 2.12, Win10 Pro, Core I5 3.2 GHz,  8 gB of RAM (Win10 Pro is fully up to date)

While receiving CPU is about 6 %
While decoding at end of seq: 30-50%
When it skips a cycle, CPU does not go nearly as high, perhaps 25% max

UDP > JTAlert
JTAlert Rebroadcast UDP > DXLab SpotCollector


I have WSTX folder excluded from virus check
I have the WSJTX appdata folder excluded.

I just stopped JTAlert and am now having WSJT-X talk UDP directly to SpotCollector.

Every sequence is decoding > 20 stations, No Skips
CPU Utilization is 30 to 50 % as before at the decode
++++++++++++++++++++++++++++++++++++++++++
It's been about 20 minutes with absolutely perfect decoding of > 20 stations every sequence. I only made one change.

Last decode seq, the CPU went as high as 66% ...still got perfect decodes.

I have no explanation or theories to offer, but if I want consistent decodes I can't run JTAlert ...and I love JTAlert, but I'm tired of fighting this.

Hasan


FWIW,

The only direct interaction JTAlert has with WSJT-X is when it either sends an instruction that a Callsign has been clicked or when painting the decodes with Alert coloring, both of which occur AFTER WSJT-X has produced its decodes. Unless decodes are excessively delayed such that JTAlert is sending coloring instructions to WSJT-X long after a new period has started, there is nothing that JTAlert is doing that would interfere with WSJT-X decoding. try turning the Decodes coloring off in JTAlert.

If your not happy with JTAlert and believe it is the true cause of random WSJT-X decode failings, the answer is simple, don't use it!

de Laurie VK3AMA


Hasan


locked Re: CAT issue with FTDX1200 / 3000 #Cat_RigControl

Jim Brown
 

On 3/16/2020 7:47 AM, Kai-KE4PT wrote:
I've been running the Yaesu FT-817 on SSB to unsolicited rave reviews on the audio quality. Also no complaints on CW, RTTY (via sound card),
The problem with these cheap rigs aren't heard by the stations you're working, but by those on adjacent frequencies. I suggest that you look at it on a spectrum display with waterfall while TX SSB -- what I've repeatedly seen are pronounced widening of the signal on voice peaks on both sides of the 2.8 kHz bandwidth, and if the amplitude display is set for averaging or to accumulate peaks, I often see that the splatter is less than 20 dB below the 2.8 kHz envelope.

Same for the clicks. Here are reports I put together several years ago. The first is all ARRL Lab data which they sent me electronically, the second is all my own work.

http://k9yc.com/TXNoise.pdf

http://k9yc.com/P3_Spectrum_Measurements.pdf

I should put together another report with plots of clean and dirty rigs. A group of west coast contesters hangs out on LSB just above the FT8 watering hole on 160M. Most of the guys have a nice clean envelope, while a few splatter like mad, down into the top of the FT8 bandpass!

A great place to see this is on 40M.

W4TV, a retired broadcast engineer, looked into the this and chased down the reasons.

73, Jim K9YC


locked Re: WSJT not driving 7610

eam1212003
 

Found D2 but still no power out...power slider all the way up...


locked Re: WSJT not driving 7610

eam1212003
 

Indeed I am in “regular” usb...how do I get to D-2.  Sorry, newbie here


locked Re: WSJT not driving 7610

Lawrence (VA3IQ)
 

The thing that I forget to do is ensure that my 7610 is in USB-D2 for mode, not just USB.

73 de VA3IQ

Lawrence

On Mon, Mar 16, 2020 at 7:43 PM eam1212003 via Groups.Io <eam1212003=yahoo.com@groups.io> wrote:
So I just upgraded to 1.20 from 1.06. No prob with radio in cw or ssb. WSJT gives me no power out. CAT is fine, audio is fine, codec...in fact all my settings in WSJT are as they were before upgrade...any suggestions what to look at...

Tnx Eli, N6PF


locked WSJT not driving 7610

eam1212003
 

So I just upgraded to 1.20 from 1.06. No prob with radio in cw or ssb. WSJT gives me no power out. CAT is fine, audio is fine, codec...in fact all my settings in WSJT are as they were before upgrade...any suggestions what to look at...

Tnx Eli, N6PF


locked Re: Seeing a Lot of Skipping Decodes Every Other Sequence FT8

JTAlert Support (VK3AMA)
 

On 17/03/2020 9:26 am, Hasan Schiers N0AN wrote:
On a busy FT8 Band like 20m, I'm seeing more and more tendencies to skip an entire sequence following a decoded sequence.

I'm on 20m FT8 now and it is happening nearly every other sequence, or it will decode 2 seq in a row and then start skipping again, without any intervention on my part.

Then it will start decoding again, do several sequences in a row (with me not transmitting, just monitoring), and then skip another sequence. I just watched it do it again while typing.

I have stopped interacting with the program, I am just letting it run with no intervention, receiving:

Two more in a row of > 20 stations
Then skipped an entire sequence
Full seq of decodes > 20
Skipped the next sequence
Full seq of decodes > 20 stations
Skipped the next seq
Full seq of decodes > 20 stations
Skipped the next seq: no decodes
Full seq of decodes > 20 stations
Skipped the next seq: no decodes
Full seq of decodes > 20 stations
Skipped the next seq.

The computer running the X software is not being touched. I'm typing on a different machine.

WSJT-X 2.12, Win10 Pro, Core I5 3.2 GHz,  8 gB of RAM (Win10 Pro is fully up to date)

While receiving CPU is about 6 %
While decoding at end of seq: 30-50%
When it skips a cycle, CPU does not go nearly as high, perhaps 25% max

UDP > JTAlert
JTAlert Rebroadcast UDP > DXLab SpotCollector


I have WSTX folder excluded from virus check
I have the WSJTX appdata folder excluded.

I just stopped JTAlert and am now having WSJT-X talk UDP directly to SpotCollector.

Every sequence is decoding > 20 stations, No Skips
CPU Utilization is 30 to 50 % as before at the decode
++++++++++++++++++++++++++++++++++++++++++
It's been about 20 minutes with absolutely perfect decoding of > 20 stations every sequence. I only made one change.

Last decode seq, the CPU went as high as 66% ...still got perfect decodes.

I have no explanation or theories to offer, but if I want consistent decodes I can't run JTAlert ...and I love JTAlert, but I'm tired of fighting this.

Hasan


FWIW,

The only direct interaction JTAlert has with WSJT-X is when it either sends an instruction that a Callsign has been clicked or when painting the decodes with Alert coloring, both of which occur AFTER WSJT-X has produced its decodes. Unless decodes are excessively delayed such that JTAlert is sending coloring instructions to WSJT-X long after a new period has started, there is nothing that JTAlert is doing that would interfere with WSJT-X decoding. try turning the Decodes coloring off in JTAlert.

If your not happy with JTAlert and believe it is the true cause of random WSJT-X decode failings, the answer is simple, don't use it!

de Laurie VK3AMA


locked Seeing a Lot of Skipping Decodes Every Other Sequence FT8

Hasan Schiers N0AN
 

On a busy FT8 Band like 20m, I'm seeing more and more tendencies to skip an entire sequence following a decoded sequence.

I'm on 20m FT8 now and it is happening nearly every other sequence, or it will decode 2 seq in a row and then start skipping again, without any intervention on my part.

Then it will start decoding again, do several sequences in a row (with me not transmitting, just monitoring), and then skip another sequence. I just watched it do it again while typing.

I have stopped interacting with the program, I am just letting it run with no intervention, receiving:

Two more in a row of > 20 stations
Then skipped an entire sequence
Full seq of decodes > 20
Skipped the next sequence
Full seq of decodes > 20 stations
Skipped the next seq
Full seq of decodes > 20 stations
Skipped the next seq: no decodes
Full seq of decodes > 20 stations
Skipped the next seq: no decodes
Full seq of decodes > 20 stations
Skipped the next seq.

The computer running the X software is not being touched. I'm typing on a different machine.

WSJT-X 2.12, Win10 Pro, Core I5 3.2 GHz,  8 gB of RAM (Win10 Pro is fully up to date)

While receiving CPU is about 6 %
While decoding at end of seq: 30-50%
When it skips a cycle, CPU does not go nearly as high, perhaps 25% max

UDP > JTAlert
JTAlert Rebroadcast UDP > DXLab SpotCollector


I have WSTX folder excluded from virus check
I have the WSJTX appdata folder excluded.

I just stopped JTAlert and am now having WSJT-X talk UDP directly to SpotCollector.

Every sequence is decoding > 20 stations, No Skips
CPU Utilization is 30 to 50 % as before at the decode
++++++++++++++++++++++++++++++++++++++++++
It's been about 20 minutes with absolutely perfect decoding of > 20 stations every sequence. I only made one change.

Last decode seq, the CPU went as high as 66% ...still got perfect decodes.

I have no explanation or theories to offer, but if I want consistent decodes I can't run JTAlert ...and I love JTAlert, but I'm tired of fighting this.

Hasan


locked Re: CAT issue with FTDX1200 / 3000 #Cat_RigControl

Hasan Schiers N0AN
 

Unrelated to WSJT-X as such, but a very important consideration for satellite work w/r to the FT-817 and for that matter, the FT-857D and a few other Yaesu rigs is that neither of these radios will accept frequency data via CAT while PTT is asserted.

This means that they cannot do doppler correction, without dropping PTT, which makes satellite, ops even with a separate receiver laborious at best.

So, if you are going to get a new radio for WSJT-X,. and have any intentions of ever using it for satellite operation, do not buy these two radios and be very careful to find out if any radio you purchase will accept CAT commands while PTT is asserted.

Take it from someone who learned the hard way. I have a virtually new FT-857d sitting on a shelf. Wonderful radio in terms of price/performance, but near useless for satellite work where real time doppler correction is important.

73, N0AN
Hasan


On Mon, Mar 16, 2020 at 9:54 AM Kai-KE4PT <k.siwiak@...> wrote:
Jim,
I've been running the Yaesu FT-817 on SSB to unsolicited rave reviews on the audio quality. Also no complaints on CW, RTTY (via sound card), and many of the modes in WSJT-X and FLdigi, via Signaling USB auido/PTT unit.
That is a good reason to buy Yaesu!
Kindest regards,
Kai Siwiak, KE4PT


locked Re: CAT issue with FTDX1200 / 3000 #Cat_RigControl

Kai-KE4PT
 

Jim,
I've been running the Yaesu FT-817 on SSB to unsolicited rave reviews on the audio quality. Also no complaints on CW, RTTY (via sound card), and many of the modes in WSJT-X and FLdigi, via Signaling USB auido/PTT unit.
That is a good reason to buy Yaesu!
Kindest regards,
Kai Siwiak, KE4PT


locked Re: WSJTX time program

 

Small addendum to Martins excellent post below. 

 

The latest Meinberg version is available at: https://www.meinbergglobal.com/english/sw/ntp.htm#ntp_stable.  As of this morning the latest version is ‘ntp-4.2.8p13’ published 8 March 2019.  Meinberg recommends upgrading to the latest version as it contains some security upgrades.

 

__________

Dan – K4SHQ

CFI/II

 

From: WSJTX@groups.io [mailto:WSJTX@groups.io] On Behalf Of Martin G0HDB
Sent: Sunday, March 15, 2020 5:36 PM
To: WSJTX@groups.io
Subject: Re: [WSJTX] WSJTX time program

 

In my opinion and experience the Meinberg NTP implementation is by far the best way of keeping a PC's clock accurately sync'ed to 'real time' - it adjusts and keeps the PC clock disciplined by making smooth adjustments rather than the crude step-changes applied by apps such as Dimension 4 that use SNTP rather than the 'proper' NTP protocol.  However...

There's a few pitfalls to avoid when installing the Meinberg NTP client so I'd very strongly recommend anyone considering installing it to read and follow the guidance given by GM8ARV on his website at:

https://www.satsignal.eu/ntp/setup.html

In particular, take note of the 'Where to install NTP?' section about NOT installing the NTP client in the usual C:\Program Files location.  Also, the 'Why NTP?' section way down towards the bottom of the web page gives some of the reasons why a proper NTP app gives much better results than a cruder, SNTP one.

As mentioned by Max NG7M above, I'd also recommend installing the Meinberg Time Server Monitor app - it's a nice way to get a good view of how the NTP client is keeping the PC's clock correctly sync'ed. 

In my setup I have my own GPS-derived stratum 1 NTP server, built on a Raspberry Pi, and the Meinberg NTP client that's installed on all my PCs uses this local NTP server to achieve an offset from 'real time' that only very rarely exceeds 1 or 2millisecs, which is more than adequate for WSJT-X's purposes!  Knowing that my PCs are accurately time-sync'ed also means that I can be pretty confident that any DT offsets shown in WSJT-X decodes are due to time errors at the other station's end and not at my end.

--
Martin G0HDB


locked Re: PTT issue

Bill Somerville
 

On 16/03/2020 13:33, OGANE YOSHIAKI wrote:
Hi all,

I am new to the group.

I have a PTT issue. When I click Tune button several times repeatedly, my K3 will be keyed to TX for the first two to three times of clicking Tune. However, it will not be keyed after that with the same setting. Restarting WSJTX program or even PC does not cure the problem. I also deleted and reinstalled WSJTX program without a joy.

I am running DXLab on the same PC(OS Windows 10 Pro) that runs WSJTX. A USB serial cable with FTDI chipset connects PC and K3 for PTT. For the precise timing of PTT, I prefer RTS to CAT as PTT method.

Does anyone have any clue?

JL1CNY/ND1Y Sam
Hi Sam,

this is a long standing known issue. We do not currently have a fix but avoiding repeated fast PTT assertions is advised.

Are you using commander for rig control?

73
Bill
G4WJS.


locked Re: CAT issue with FTDX1200 / 3000 #Cat_RigControl

Greg Chartrand
 

It sure would be nice to have a reviewer of radios specifically for the WSJT modes that takes into account all aspects of performance so people like me can judge based on relative elements of the digital modes. 

Just for the record, I'm extremely pleased over-all with my FTDX-1200, it is clean, stable, and has a extraordinary receiver that on CW will compete with the best of all the other radios in the market. The CAT antenna switch issue is my only complaint and will get fixed when I purchase an amplifier and tuner that is programmable. I will not bash Yaesu over-all in fact hardly any of the radio's available are fully designed with digital in mind so virtually all are compromises in one way or the other. Roger, I think this horse has been sufficiently beaten to death!


locked PTT issue

OGANE YOSHIAKI
 

Hi all,

I am new to the group.

I have a PTT issue. When I click Tune button several times repeatedly, my K3 will be keyed to TX for the first two to three times of clicking Tune. However, it will not be keyed after that with the same setting. Restarting WSJTX program or even PC does not cure the problem. I also deleted and reinstalled WSJTX program without a joy.

I am running DXLab on the same PC(OS Windows 10 Pro) that runs WSJTX. A USB serial cable with FTDI chipset connects PC and K3 for PTT. For the precise timing of PTT, I prefer RTS to CAT as PTT method. 

Does anyone have any clue?

JL1CNY/ND1Y Sam


locked Re: Desktop Icon for different location

Herb Blue - WB8ASI
 

Wow.  That was easy.  Thanks much. 73, Herb WB8ASI

On March 16, 2020 at 5:28 AM Tom Melvin < tom@...> wrote:


On a Windows PC :

Right click existing desktop icon
Select ‘copy’
Select ‘paste’

You will now have a new icon on desktop ‘wsjt-x - Copy’
Right click it
Select Properties
Change General -> Name to suit
Add to to command line in Shortcut -> Target —rig-name=IO85 (Or make it any name to suit you - make sure you have a hyphen between rig and name))
Click OK

When selected wsjt will be started with settings in IO85 (in my example), if does not exist will be created, adjust WSJT settings as appropriate.

I believe Mac desktop icons are similar - if your using a *nix version can’t help.

Tom

--
73’s

Tom
GM8MJV (IO85)





On 16 Mar 2020, at 02:34, Herb Blue < WB8ASI@...> wrote:

How to add an additional desktop icon for different grid location?


locked Re: wave files

m_scot_alex
 

There have been several threads regarding sound files in general and discussions about how to create custom sound files in the JT Alert group:

https://hamapps.groups.io/g/Support/search?q=sounds

73,

Mike - N8MSA


locked Re: Desktop Icon for different location

Tom Melvin
 

On a Windows PC :

Right click existing desktop icon
Select ‘copy’
Select ‘paste’

You will now have a new icon on desktop ‘wsjt-x - Copy’
Right click it
Select Properties
Change General -> Name to suit
Add to to command line in Shortcut -> Target —rig-name=IO85 (Or make it any name to suit you - make sure you have a hyphen between rig and name))
Click OK

When selected wsjt will be started with settings in IO85 (in my example), if does not exist will be created, adjust WSJT settings as appropriate.

I believe Mac desktop icons are similar - if your using a *nix version can’t help.

Tom

--
73’s

Tom
GM8MJV (IO85)

On 16 Mar 2020, at 02:34, Herb Blue <WB8ASI@...> wrote:

How to add an additional desktop icon for different grid location?


locked Desktop Icon for different location

Herb Blue - WB8ASI
 

How to add an additional desktop icon for different grid location?