Date   

locked Re: Display the last few QSOs from WSJT-X log

n9bt@...
 

Thanks Zeev,
    That script works great!
73
Bill
N9BT


locked Re: Decode cycle dropped #FT8

K9RX - Gary
 

I've seen this issue for some time now - a good number of versions ... AND it happens in JTDX at the same time/same sequence! So thanks Bill for the explanation. Although I'm not sure which of these would be the cause at my end.

-I will check the clock to see if Windows reset this, however if that were the case it makes no sense that it would be just one sequence out of the blue, be working fine - miss one sequence, go back to working fine. 
- high CPU is not likely with an i7-8770 and CPU typically sub 10% but I suppose possible...
-not an OL issue as I've seen this happen on quiet bands ... 

Gary 
K9RX


locked Re: Monitor specific call sign

John Morphet
 

There are companion programs like GridTracker and JTAlert that can do that for you.

 

John, WØZI

 

From: WSJTX@groups.io <WSJTX@groups.io> On Behalf Of Mikael Rytky
Sent: Monday, January 13, 2020 10:48 AM
To: WSJTX@groups.io
Subject: [WSJTX] Monitor specific call sign

 

Hi!

I have been using WSJT-X for FT8 mode for some time. As a DX hunter I am missing one function, or, I have not found it yet.
If there is a weak DX active on FT8, I simply want to monitor / filter out info in the left window sent by that specific station only to see if I copy. For a weak DX stn, 99% of the DX station related info in the window is from stations calling the DX, often random zombie calling without even copying the DX because of a cluster spot. If I "see" the DX answering someone, I can click at that "QSO" and start following its transmissions, otherwise I have to starr at the window until my eyes spot something in the text mass rolling by.

When a lot of text rolls every 15 sec my only way to filter out the desired info is to every few minutes "select all" in the window & copy, paste it to a text editor, then search for DX callsign in the column that would be a transmission from the DX itself. Its like hearing the whole pile-up + DX station on CW.

Does this function already exist?

BR Mikael SM6VJA


locked Re: Decode cycle dropped #FT8

Bill Somerville
 

On 14/01/2020 03:49, Steve Miller wrote:

This is with version WSJT-X 2.1.2 using FT-8 mode but has been experienced on previous WSJT-X versions as well.

 

WSJT-X will skip decoding a cycle for no apparent reason. Signals are present as observed in the waterfall but nothing in that Rx cycle gets decoded. It happens randomly while just monitoring. Also running JTAlert, 2.15.6.

 

Anyone else seen this?

Hi Steve,

there are many possible causes for this, some examples:

1) clock synchronization issues. Some third-party clock sync applications adjust the time in large steps and when that happens during an Rx period it is unlikely to decode successfully. One notable cause of this issue is that on Windows 10 some updates have gratuitously re-enabled the Windows Internet Time Sync application which then gets into a fight with the third-party application about the clock adjustments. You must only have one clock synchronization application active at any time.

2) high CPU resource spikes during Rx periods. Particularly disruptive are Deferred Procedure Calls (DPC) where, usually badly coded, operating system interrupt handlers block processing of critical functions like audio handling. There are a few free DPC checkers that can be run to determine if your system is suitable for near real-time audio handling. Reducing system load from other applications or devices may improve matters.

3) any form of audio level overload, even for short time periods, may disrupt the decoder. Noise spikes or very strong signals that exceed the maximum input level of the sound card ADC such clipping creates discontinuities in the received waveform. These discontinuities represent considerable wide-band noise added to the waveform that can mask all signals present. Make sure that you have sufficient headroom for strong signals by ensuring that the quiet band band noise is at 30dB or so on the WSJT-X thermometer type Rx level indicator (note that the indicator turns red if clipping is likely to occur due to excessive levels).

One indicator of problems with the incoming audio stream is a failure to save a .WAV file even when "Menu->Save->Save all" is checked, OTOH if a .WAV file is available for an Rx period that apparently failed to decode good signals; then that file should be shared with us for analysis.

73
Bill
G4WJS.


locked Re: Decode cycle dropped #FT8

Dick
 

 > WSJT-X will skip decoding a cycle for no apparent reason.

> Signals are present as observed in the waterfall but nothing in that Rx cycle gets decoded.

> It happens randomly while just monitoring. Also running JTAlert, 2.15.6.

 

> Anyone else seen this?

Yes, in  my case it was always related to (periods of)  high CPU usage.

 

73, Dick PA-2015


locked Decode cycle dropped #FT8

Steve Miller
 

This is with version WSJT-X 2.1.2 using FT-8 mode but has been experienced on previous WSJT-X versions as well.

 

WSJT-X will skip decoding a cycle for no apparent reason. Signals are present as observed in the waterfall but nothing in that Rx cycle gets decoded. It happens randomly while just monitoring. Also running JTAlert, 2.15.6.

 

Anyone else seen this?


locked Decode cycle dropped

Steve Miller
 

This is with version WSJT-X 2.1.2 using FT-8 mode but has been experienced on previous WSJT-X versions as well.

 

WSJT-X will skip decoding a cycle for no apparent reason. Signals are present as observed in the waterfall but nothing in that Rx cycle gets decoded. It happens randomly while just monitoring. Also running JTAlert, 2.15.6.

 

Anyone else seen this?

 

 

Sent from Mail for Windows 10

 


locked Re: Monitor specific call sign

John Wisniowski
 

Well, I just learned how to do screenshots and add them to email.  

This is what I was referring to in my last reply.  
I know it works because I used it for Pitcairn Island.  

73, John-N6DBF


locked Re: Monitor specific call sign

John Wisniowski
 

In JTAlert, set an "Alert" for the call sign or "Contains" the following.


locked Re: IC-7600 CODEC problem

John Wisniowski
 

Your Codec ports are likely reversed.  


locked Re: WSJT-X & Com Ports

Gwen Patton <ardrhi@...>
 

John,

I don't use an external log program with WSJT-X. I let it log internally, then import its .adi file into another log. Mostly, I was doing that at the end of 2018, when I got my KX3. I did a fair bit of FT8 back then, and I didn't use N3FJP then. I mostly imported my contacts into the QRZ logbook. I also don't use WSJT-X along with WinK3Suite, because WSJT-X is enough to control the frequency. I use the WinK3Suite so I don't have to crane my neck around to use the KX3. Running FT8 doesn't require the extra rig control software. The only rig controlling necessary is setting frequency and keying. Even audio is controlled largely by Windows settings, or using the Power slider in WSJT-X. So while I HAVE all of those pieces of software, I generally don't have to use them all *at the same time*. WSJT-X will do just fine logging the contacts internally. Then you can do what you need to do with the .adi file. That's what I did.

N3FJP does integrate well with WinK3Suite, using their com port pass-through capability, the "3rd party software" feature. But there's no need to add WSJT-X into that, so I've never run all three at the same time.

73,
Gwen, NG3P

On Mon, Jan 13, 2020 at 4:21 PM John Ratcliffe <john_ratcliffe@...> wrote:
Hello Gwen,

Do you have any issues integrating WSJT-X with N3FJP and Win4K3? Which radio are you using?

Many Thanks,

John


From: WSJTX@groups.io <WSJTX@groups.io> on behalf of Gwen Patton <ardrhi@...>
Sent: 13 January 2020 18:23
To: WSJTX@groups.io <WSJTX@groups.io>
Subject: Re: [WSJTX] WSJT-X & Com Ports
 
I've tried N1MM, Swisslog, DXLabs, and HRD. I find that N3FJP is FAR easier to use, and it integrates nicely with Win4K3Suite. I use the general log for everyday use, and the separate, specific contest logs when appropriate. I like that they have separate logs for separate contests, and that they have so MANY such contest logs. I bought the entire bundle -- very economical!

Gwen, NG3P

On Mon, Jan 13, 2020 at 11:49 AM <john_ratcliffe@...> wrote:
Thanks for the response Andy.

I did look at DXLabs but didn't like it. I'd prefer to stick with N3FJP if possible; it's a really simple logger to use.

73s,

John M7JHA


--

-+-+-+-+-
Jenny Everywhere's Infinite: Quark Time
http://quarktime.net



--

-+-+-+-+-
Jenny Everywhere's Infinite: Quark Time
http://quarktime.net


locked Re: Monitor specific call sign

JTAlert Support (VK3AMA)
 

On 14/01/2020 8:19 am, Herb Blue wrote:
I like using the Decodes Window in JTAlert.  I filter out the US stations, and can easily see all the rest....and they stay on the screen.

You can go one step further and filter on an individual Callsign and only see decodes of that Station.

de Laurie VK3AMA


locked Re: Signals in Spectrum Monitor or Decodes, Input level in the green #AudioIssues

George J Molnar, KF2T
 

A couple of suggestions,

Uncheck “Flatten.” You don’t need it with a Flex.

Ensure your DIGU bandwidth is set to 3000 Hz or better.

Open up the Wide Graph to 3000 also (Bins/Pixel) / WSJT-X won’t decode outside what the wide graph is set for.

Check to make sure your RX antenna is correctly selected.

Make sure your receive audio bit rate is 48000.

In the Audio tab, make sure you’re using the correct L/R channel (L usually works)

In the Advanced tab, make sure that the Tone Spacing x2 and x4 are NOT selected.

Hopefully, something there will help!


73,

George/KF2T


locked Re: Signals in Spectrum Monitor or Decodes, Input level in the green #AudioIssues

NC3Z
 

I get this issue all the time with my Flex, it's a bug (one of many) with DAX. You have to shut Flex down (and remove power for a few) and restart DAX. For me it's just a fact of life using a Flex 6600M.

--
Gary Mitchelson
NC3Z/4 Pamlico County, NC FM15
NC AHIMT COML
SHARES NCS997
NC Deputy Auxcomm Coordinator - Statewide
www.mitchelson.org


locked Re: Signals in Spectrum Monitor or Decodes, Input level in the green #AudioIssues

KI0KK - Greg Wolfe
 

TNX for the help. I pulled up the profile that I had saved for Maestro SSB and WSJT-X started working again. If I open the Global profile it stops working. I created a new Global profile for Digital saved it and it works. Would not have thought the profile was corrupted but it must be.

On 1/13/2020 3:03 PM, AB8WD via Groups.Io wrote:
I had a similar problem like this yesterday with the flex and wjst I shut it all down and pulled the power connector from the flex and rebooted all of it one at a time and when it came back up to sdr for flex I pulled the profile I had saved it it started working again just an Idea but it did work for me. 

    


locked Re: Monitor specific call sign

Nc8q-mesh@gelm.net
 

On 1/13/20 12:48 PM, Mikael Rytky wrote:
Does this function already exist?
You may reduce the span of the 'Wide Graph'.


--


locked Re: WSJT-X & Com Ports

John Ratcliffe
 

Hello Gwen,

Do you have any issues integrating WSJT-X with N3FJP and Win4K3? Which radio are you using?

Many Thanks,

John


From: WSJTX@groups.io <WSJTX@groups.io> on behalf of Gwen Patton <ardrhi@...>
Sent: 13 January 2020 18:23
To: WSJTX@groups.io <WSJTX@groups.io>
Subject: Re: [WSJTX] WSJT-X & Com Ports
 
I've tried N1MM, Swisslog, DXLabs, and HRD. I find that N3FJP is FAR easier to use, and it integrates nicely with Win4K3Suite. I use the general log for everyday use, and the separate, specific contest logs when appropriate. I like that they have separate logs for separate contests, and that they have so MANY such contest logs. I bought the entire bundle -- very economical!

Gwen, NG3P

On Mon, Jan 13, 2020 at 11:49 AM <john_ratcliffe@...> wrote:
Thanks for the response Andy.

I did look at DXLabs but didn't like it. I'd prefer to stick with N3FJP if possible; it's a really simple logger to use.

73s,

John M7JHA


--

-+-+-+-+-
Jenny Everywhere's Infinite: Quark Time
http://quarktime.net


locked Re: Monitor specific call sign

Herb Blue - WB8ASI
 

I like using the Decodes Window in JTAlert.  I filter out the US stations, and can easily see all the rest....and they stay on the screen.

On January 13, 2020 at 12:48 PM Mikael Rytky <vfr_micke@...> wrote:

Hi!

I have been using WSJT-X for FT8 mode for some time. As a DX hunter I am missing one function, or, I have not found it yet.
If there is a weak DX active on FT8, I simply want to monitor / filter out info in the left window sent by that specific station only to see if I copy. For a weak DX stn, 99% of the DX station related info in the window is from stations calling the DX, often random zombie calling without even copying the DX because of a cluster spot. If I "see" the DX answering someone, I can click at that "QSO" and start following its transmissions, otherwise I have to starr at the window until my eyes spot something in the text mass rolling by.

When a lot of text rolls every 15 sec my only way to filter out the desired info is to every few minutes "select all" in the window & copy, paste it to a text editor, then search for DX callsign in the column that would be a transmission from the DX itself. Its like hearing the whole pile-up + DX station on CW.

Does this function already exist?

BR Mikael SM6VJA

 


locked Re: WSJT-X & Com Ports

Gwen Patton <ardrhi@...>
 

I've tried N1MM, Swisslog, DXLabs, and HRD. I find that N3FJP is FAR easier to use, and it integrates nicely with Win4K3Suite. I use the general log for everyday use, and the separate, specific contest logs when appropriate. I like that they have separate logs for separate contests, and that they have so MANY such contest logs. I bought the entire bundle -- very economical!

Gwen, NG3P

On Mon, Jan 13, 2020 at 11:49 AM <john_ratcliffe@...> wrote:
Thanks for the response Andy.

I did look at DXLabs but didn't like it. I'd prefer to stick with N3FJP if possible; it's a really simple logger to use.

73s,

John M7JHA


--

-+-+-+-+-
Jenny Everywhere's Infinite: Quark Time
http://quarktime.net


locked Monitor specific call sign

Mikael Rytky
 

Hi!

I have been using WSJT-X for FT8 mode for some time. As a DX hunter I am missing one function, or, I have not found it yet.
If there is a weak DX active on FT8, I simply want to monitor / filter out info in the left window sent by that specific station only to see if I copy. For a weak DX stn, 99% of the DX station related info in the window is from stations calling the DX, often random zombie calling without even copying the DX because of a cluster spot. If I "see" the DX answering someone, I can click at that "QSO" and start following its transmissions, otherwise I have to starr at the window until my eyes spot something in the text mass rolling by.

When a lot of text rolls every 15 sec my only way to filter out the desired info is to every few minutes "select all" in the window & copy, paste it to a text editor, then search for DX callsign in the column that would be a transmission from the DX itself. Its like hearing the whole pile-up + DX station on CW.

Does this function already exist?

BR Mikael SM6VJA