Re: [wsjt-devel] Second Public Test of FT8 DXpedition Mode: early results

Hi Joe, Any reason why W1/KH7Z ceased transmissions at 143630? Wasn’t in the plan... — John G4KLA -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org!

Re: [wsjt-devel] "CQ only", UDP and ALL.TXT bug

Hi! This small patch seems to stop duplicate decodes in BandActivity/UDP/ALL.TEXT  and makes touching "CQ only" to take *effect from next decode onwards*. Just what I tried to describe... -- Saku OH1KH Bill Somerville kirjoitti 06.04.2018 klo 19:43: On 06/04/2018 17:39, Bill Somerville

[wsjt-devel] Second Public Test of FT8 DXpedition Mode: early results

Hi all, Many people have asked for a list of stations heard and worked in the Second Public Test of FT8 DXpedition Mode, held on April 7. I have attached a brief summary. It's a plain text file containing four lists of callsigns: 1. 61 logged by W1/KH7Z in 36 minutes: rate = 61*60/36 =

Re: [wsjt-devel] Second Public Test of FT8 DXpedition Mode: early results

Hi John, On 4/9/2018 12:00 PM, John Nelson G4KLA wrote: Any reason why W1/KH7Z ceased transmissions at 143630? Wasn’t in the plan... Our announcements have included this advice: "Real-time liaison will be available on the "Ping Jockey Relief" chat page (PJB),

[wsjt-devel] Cannot find path

Hi: After the fun of about a thousand Qs and switching to 1.9, I started to get the "cannot find path specified" error message with every cycle. I have attempted to reset "Location" in the Audio Save Directory with no success. Can someone please give me a pointer on how establish the path to

Re: [wsjt-devel] Second Public Test of FT8 DXpedition Mode: April 7, 1400-1600 UTC

Hi Bill and Robin, I think I do not need to further explain about my words in my previous memo to WSJT-X experts like you but I doublchedked my understanding about “TDM and FDM” fundamentals has the validity or not through google search. You can see several cons for TDM about non-linearity

Re: [wsjt-devel] Cannot find path

Hi Jim The same happened to me just before the FT8 Dxpedition test, for the first time. In my case this was with 1.9 that has been installed and stable for some time. I was able to fix it by going to Settings-> Audio and pressing 'Select' and browsing to the standard locations (in my case

Re: [wsjt-devel] Second Public Test of FT8 DXpedition Mode: April 7, 1400-1600 UTC

On 08/04/2018 23:14, David Tiller wrote: The W1/KH7Z fox was barely audible in FM17 - I only got a few decodes. K1JT was a bit louder, but still not loud enough to warrant calling him. Hi David, unless the Fox is QRO (Joe wasn't) then you should call if you copy them at all, if they are

[wsjt-devel] Test

First hour signal was +3 and I got -24 I started with 20 watts and ended to 200 watts, when I got that -24dB report. Second hour hear best -8dB and started again from 20 watts went up to 1K and didn't get w7/kh7z :(. Tried several places, no lucky. At the end of test last decoded signal was -15dB.

[wsjt-devel] CPU Usage Over Time

Using 1.9 (8603) under MacOS 10.13.4. Upon launch, program operates smoothly. As Band Activity window fills, CPU usage rises slowly, until the program becomes unresponsive. At that point, only a forced quit recovers the app. It does keep receiving and decoding, however. If I catch it early

Re: [wsjt-devel] CPU Usage Over Time

Hi George, Evidently you are building the program yourself. It seems that you should look carefully into why you are having this issue with your home-built executable. I do not think our builds show any problem of this kind. -- 73, Joe, K1JT On 4/9/2018 8:33 AM, George Molnar

Re: [wsjt-devel] CPU Usage Over Time

Thanks, Joe. Will check my build environment. George J Molnar Washington, DC, USA KF2T - @GJMolnar > On Apr 9, 2018, at 5:52 AM, Joe Taylor wrote: > > Hi George, > > Evidently you are building the program yourself. > > It seems that you should look carefully