Re: [wsjt-devel] Configurations

I use configurations for every mode as well as DXpeditions. They work great. *One feature I never understood is the "Clone Into"* I guessed that it might be a simultaneous Clone and Rename, but I've never used it. The way I make new configurations is to start from a known perfectly working

Re: [wsjt-devel] new version 2.2.

Frank, It's probably not delay, but the decoder finishing earlier than you expect. On a crowded band you will see the decoder finish early, then about 2 sec later, add a few more stations 73, N0AN (new feature) Hasan On Mon, May 18, 2020 at 1:31 AM Frank Hunger wrote: > Hi, installing new

Re: [wsjt-devel] DB.EXE attachment?

Rich, Someone may have included a link to my google drive to the file db.exe which is a signal analysis progrm written by w9mdb that I posted in another thread a few days ago. It is a small dos program that looks at your all.txt file and shows the differences in reports sent and received by band,

Re: [wsjt-devel] F/H with the DX calling on 2nd (odd)

When working one of the non-F/H multi-streamers, I would recommend calling them >1000 Hz above their freq, to keep their area clean. Basically there are two types of Multi-Streaming operations: 1. F/H which is the WSJT-X Standard 2. All others, including MSHV, for which you *do not* use F/H

[wsjt-devel] 2nd Errror in WSJT-x This Morning

Enclosed my 2nd crash this morning from WSJT-X. I have been getting these crashes fairly consistently since running the trace version of 2.1.2 to look at a different problem. Ever since I reinstalled 2.1.2 normal over the trace version, I have been left with an unstable setup for WSJT-X.

Re: [wsjt-devel] WSJT-X ver 2.1.0 spontaneous frequency changes

I missed it in the discussion. I've adopted yours and see if it improves. I just had it happen twice on AO-85 and AO-91 under the old settings of 100 and 200 ms. Thanks again. 73, N0AN Hasan On Sun, Aug 18, 2019 at 5:12 PM Andy Durbin wrote: > "What values are you using for Poll and Timeout

Re: [wsjt-devel] WSJT-X ver 2.1.0 spontaneous frequency changes

Andy, What values are you using for Poll and Timeout in OmniRig? I'm using 100 ms polling and 200 ms timeout. I ask because I have been having a problem with transmitting (with an external radio in FM mode when using SDRC's External Radio capability) I have played with the Polling and Timeout

Re: [wsjt-devel] FT8 decodes only on alternate 15-second cycles

I've seen it before and I had to reboot the computer which solved the problems. I've also seen pending Windows Updates cause this and other problems. win10 is ready to update, but you have done it. If you Right click to shut down Win10, it may say Update and Restart. If it does, it's a sure sing

Re: [wsjt-devel] Loss of Decoding in WSJT-X with Audio Still Present

perly" ? Once I have that, I can put it in the batch file and JTA will close gracefully and it can be restarted a few minutes later. Hasan On Tue, Jul 30, 2019 at 4:41 PM Hasan al-Basri wrote: > Ok, I'll look at another way to close it. > Tnx tip, 73, N0AN > Hasan > > > On

Re: [wsjt-devel] Loss of Decoding in WSJT-X with Audio Still Present

Ok, I'll look at another way to close it. Tnx tip, 73, N0AN Hasan On Tue, Jul 30, 2019 at 3:53 PM Laurie, VK3AMA <_vk3a...@vkdxer.net> wrote: > > On 31/07/2019 2:03 am, Hasan al-Basri wrote: > > Put this in a batch file: (use notepad to create) > > taskkill /F /IM jtaler

Re: [wsjt-devel] Loss of Decoding in WSJT-X with Audio Still Present

> It has to be doing something to the sound recording -- > > Having both the Audacity and WAV files would be of use. > > > On Tuesday, July 30, 2019, 08:21:29 AM CDT, Hasan al-Basri < > hbasri.schie...@gmail.com> wrote: > > > Hi Mike > > Never. The monitor (Hi-

Re: [wsjt-devel] Loss of Decoding in WSJT-X with Audio Still Present

nd note the > time it stops an starts and we can look at the WAV file to see what changes. > > Recording with Audacity would be nice. > > Mike > > > > On Tuesday, July 30, 2019, 08:04:14 AM CDT, Hasan al-Basri < > hbasri.schie...@gmail.com> wrote: > > > Totall

Re: [wsjt-devel] Loss of Decoding in WSJT-X with Audio Still Present

her) troubles with JTAlert, but it turned >> out that some files on my computer must have been corrupted. Uninstalled >> JTAlert completely, removed all remaining files manually and the >> reinstalled JTAlert again, and all the errors were gone. Maybe also worth >> to try… >

Re: [wsjt-devel] Loss of Decoding in WSJT-X with Audio Still Present

On Tue, Jul 30, 2019 at 7:43 AM Black Michael via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > What do you have for the soundcard setting in JTAlert and WSJT-X? > > > > > On Tuesday, July 30, 2019, 07:30:17 AM CDT, Hasan al-Basri < > hbasri.schie...@gm

Re: [wsjt-devel] Loss of Decoding in WSJT-X with Audio Still Present

nually and the > reinstalled JTAlert again, and all the errors were gone. Maybe also worth > to try… > > > > 73 de Uwe, DG2YCB > > > > *Von:* Hasan al-Basri [mailto:hbasri.schie...@gmail.com] > *Gesendet:* Dienstag, 30. Juli 2019 12:33 > *An:* WSJT software deve

[wsjt-devel] Loss of Decoding in WSJT-X with Audio Still Present

First of all, no, the cause is not clock error. I have found the "proximate" cause, however, after weeks of hunting. I worked with W9MDB and tested/considered many potential causes. I even thought I had found it several times. In all those cases there was a confounding variable, which I have now

Re: [wsjt-devel] FT4 Default Frequencies

Well said and to the point. Perhaps the most important thing to understand is that this is an experimental and adjustment time for FT4 that will (and needs to) fade away. It's use after the current fascination with it subsides, needs to be reserved for contests only. Its only advantage is speed.

Re: [wsjt-devel] WSJT-X 2.1.0 64-bit GA release: TX audio level has changed

yes, had to go to 100% but works just fine 73, N0AN Hasan On Mon, Jul 15, 2019 at 4:09 PM Jim Record wrote: > Yes. I had to push it to almost 100% and push the Windows Pro 10 audio to > 60%. > > On Mon, Jul 15, 2019 at 9:52 AM DG2YCB, Uwe wrote: > >> Many thanks for the new GA version! Works

Re: [wsjt-devel] WSJT-X 2.1.0 64-bit GA release: TX audio level has changed

Yes, same here, my power slider now has to be set at maximum to just barely tickle the ALC on my TS-590sg. Not a problem, just different from some of the prior versions...in fact a recent debug version showed the same characteristic, requiring power slider to be at max with Speaker Output level at

Re: [wsjt-devel] WSJT Audio Input Loss

her version that had > problems?) and see if it locks up. > > Just add the -r option and pick a name > > wsjtx -r test > > de Mike W9MDB > > > > > On Saturday, July 6, 2019, 04:57:44 PM CDT, Hasan al-Basri < > hbasri.schie...@gmail.com> wrote: > &g

Re: [wsjt-devel] WSJT Audio Input Loss

31 hours and counting since I installed the debug version you sent me the link to. No errors. Will report more tomorrow morning. I can't imagine that this install somehow fixed the issue? 73, N0AN Hasan On Sat, Jul 6, 2019 at 2:38 PM Black Michael via wsjt-devel <

Re: [wsjt-devel] WSJT Audio Input Loss

in > your case? > > On Fri, Jul 5, 2019 at 8:59 AM Hasan al-Basri > wrote: > >> Ok, I'll check it out. >> >> Downloading now, then will install right over the top of my existing 2.01 >> Tnx >> 73, N0AN >> >> Hasan >> >>

Re: [wsjt-devel] WSJT Audio Input Loss

, Jul 5, 2019 at 9:53 AM Hasan al-Basri wrote: > Ok, I'll check it out. > > Downloading now, then will install right over the top of my existing 2.01 > Tnx > 73, N0AN > > Hasan > > > On Fri, Jul 5, 2019 at 7:46 AM Black Michael wrote: > >> This

Re: [wsjt-devel] WSJT Audio Input Loss

-2.0.1-win32-dropouts.exe?dl=1 > > de Mike W9MDB > > > On Friday, July 5, 2019, 04:45:38 AM CDT, Hasan al-Basri < > hbasri.schie...@gmail.com> wrote: > > > Ok Mike, it decoded for > 24 hours but then stopped early this morning > just before I got to the

Re: [wsjt-devel] WSJT Audio Input Loss

nce, ...even though the thermometer and the waterfall show sigs for the full sequence. Any other suggestions? 73, N0AN Hasan On Thu, Jul 4, 2019 at 5:35 AM Hasan al-Basri wrote: > Ok, I'll check it out. Time is perfect and always is, I'm GPS locked to it. > > When I got down here

Re: [wsjt-devel] WSJT Audio Input Loss

r tune causes no generated audio > to the DAX software which has a meter that shows me no incoming audio is > present from WSJT-X. > > Typically corrected with a WSJT-X restart > > -- > 73 > > TodWE5TR > While mobile > > On Jul 3, 2019, at 16:52, Hasan a

Re: [wsjt-devel] WSJT Audio Input Loss

I also followed the link from Mike and verified that I had already done what he recommended...months and months ago. It's not an RFI problem. I've thought about uninstalling X and then going into the registry and searching for anything related to WSJT-X and deleting it, along with any left-over

Re: [wsjt-devel] WSJT Audio Input Loss

Hi Mike, No transmitting at all. RF Chokes all over the place. No issues running KW out on any band 6m through 80m. (if I have just rebooted the computer). Once it has run for several hours. it will stop decoding, whether I have transmitted or not, no matter qrp or qro. I monitor 24x7 , go days

Re: [wsjt-devel] clock patch

Not all USB based GPS have issues. Not all software is the same. NMEATime2 does not show the issues you describe with a USB GPS. while the BKT software does. (for me) This one, from Amazon works. I have two of them. GlobalSat BU-353-S4 USB GPS Receiver (Black) The above USB based GPS used with

Re: [wsjt-devel] Field Day time problem

I also agree with Fred, why do we constantly focus on reinventing the wheel? WWV or other world time services and a mouse click will even work. A Cheap CASIO watch has NIST time in it for $30. (works well Stateside). The GPS dongles are dirt cheap and some even come with time setting software.

Re: [wsjt-devel] WSJT-X 2.1.0-rc7

Working fine 64 bit Win10 Home Tnx quick fix! 73, N0AN Hasan On Mon, Jun 3, 2019 at 2:04 PM Al wrote: > RC 7 OK so far.. > AL, K0VM > > On 6/3/2019 12:56 PM, Joe Taylor wrote: > > To: Users of WSJT-X -- especially those interested in radio contesting > From: WSJT Development Group > > We

Re: [wsjt-devel] Bug report

Same here, 64 bit win won't start and does not show up as an installed program. The files are in the install directory, but it neither starts, nor does is show up in the start program list. N0AN Hasan On Sun, Jun 2, 2019 at 2:00 PM Jari A wrote: > win 7 64 bit > > Does not start, reboot does

Re: [wsjt-devel] No Longer Decoding

I've had the new 64 bit version go deaf in a similar manner after sitting unused perhaps 36 hours. Nothing would solve it...rebooted, fixed it immediately with no changes of any kind. 73, N0AN Hasan On Thu, May 9, 2019 at 7:02 PM Ed Deichler wrote: > Both LINE IN and LINE OUT were previously

Re: [wsjt-devel] Another observed drawback - audio input level

Thanks Bill, and yes it does get set to +23 dB with any change in config. Think I'll leave the sound setting window open :-) 73, N0AN Hasan On Tue, Apr 30, 2019 at 5:01 PM Bill Somerville wrote: > On 30/04/2019 22:42, Hasan al-Basri wrote: > > BTW, I assume we are talking about

Re: [wsjt-devel] Another observed drawback - audio input level

I am also using an external usb sound dongle (the $5 variety from Amazon). I am not seeing any of the noted audio issues with the 64 bit version. I have set the audio once, gone back and forth, started, stopped the program, changed configs. I don't see it. I assumed it was because it was not the

Re: [wsjt-devel] The FT4 Protocol for Digital Contesting - more on frequencies

Hi Jim, and tnx 20m FT4 qso. I have been spotted on 40m, 20m, 30m in the last 10 min or so. I have not seen any spots from my 17m signal, nor have I seen any sigs. I'll try a few CQs on 15 and 10 to see if any spots show up. 73, N0AN Hasan On Tue, Apr 30, 2019 at 9:50 AM James Shaver wrote:

Re: [wsjt-devel] PJ4P Operation

I worked them in the normal mode calling them about 100 Hz above where they were tx'ing. 73, N0AN Hasan On Wed, Jan 23, 2019 at 4:00 PM John Zantek wrote: > Has anyone observed the FT8 operation of the PJ4P expedition team? Maybe > I’m missing something obvious, but…. > > > > It LOOKS they’re

Re: [wsjt-devel] Required duplication feature

san al-Basri wrote: > > *Bill, what do you think about installing N1MM+ given it's requirement to > install as Admin?* > > Hi Hasan, > > I am not aware that it does need to be installed as Administrator. > Installers on Windows normally run from a non-privileged user acco

Re: [wsjt-devel] Required duplication feature

Admin install, I'll give it a try. The X software performed just beautifully during the contest, and made operating a real pleasure. 73, N0AN Hasan On Mon, Jan 21, 2019 at 4:41 PM Bill Somerville wrote: > On 21/01/2019 22:09, Hasan al-Basri wrote: > > I like your suggestion

Re: [wsjt-devel] Required duplication feature

I agree, George, CM worked wonderfully. Processing my log for ARRL was a complete pain. The cab file has full freq in it, and ARRL won't accept it in the upload. So I had to edit the file. The file had full freq and ARRL would only accept 50 (for 6m) I like your suggestion about just real time

Re: [wsjt-devel] Possible bug in V2 GA ?

d up on, to better understand? > > Thanks > Chris. - N3PLM > > On Mon, Dec 31, 2018 at 4:41 PM Hasan al-Basri > wrote: > >> Chris, >> If you are not calling right on or close to the station's frequency, the >> tx will not go out, it will continue. This is a featu

Re: [wsjt-devel] Possible bug in V2 GA ?

Chris, If you are not calling right on or close to the station's frequency, the tx will not go out, it will continue. This is a feature, not a bug. It allows the "rare" station to queue up some callers while continuing to work an existing station that may or may not be on his tx freq. 73, N0AN

Re: [wsjt-devel] Mobile operation

For time lock, I use this: http://visualgps.net/nmeatime2 It does a lot more than just time, but it won't automatically update your grid square inside X 73, N0AN Hasan On Sun, Dec 23, 2018 at 7:42 PM Chris Knox wrote: > Is there a way to have the program automatically update your grid

Re: [wsjt-devel] Tab 2

I prefer TAB 1, do not use TAB 2, ever. Hasan On Sun, Dec 2, 2018 at 8:06 AM WB5JJJ wrote: > Bill: > > As you requested, I have never used Tab 2. One vote to remove it. Tab 1 > has all the information as to what is going on during a contact with no > thinking required. > > I have NOT had

[wsjt-devel] View Contest Log Shows No Data Under Received Column?

As I look at my log from last night's Mock : View > Contest Log There are no entries displayed under the Received Column. Should there be? Looking at the Cabrillo export Log: QSO: 7078 DG 2018-11-19 2006 N0AN 569 IAK9AN 569 IL ... shows that a Rx exchange exists. What

[wsjt-devel] Contest Log: Received not filled in

In View > Contest Log The Sent is filled in, the Rx is empty Hasan ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] 2.0 RC4

GA Jim, Tnx qso earlier. Win10 decided it needed to update, so it started to misbehave. All is well., 73, N0AN Hasan On Mon, Nov 19, 2018 at 4:17 PM wrote: > Just my .02 worth. On 40m now with very compromised antenna ( a 20’ piece > of downspout) and I’m decoding a lot of 77bit traffic. Even

Re: [wsjt-devel] RC 4 testa.

Ya know, Chuck, it's almost refreshing not having a bajillion sigs to hunt thru. I'm find RC4 just fine. I'm on 40m right now, have worked about 6 guys in the last 15 minutes, and had time to ready your email :-) 73, N0AN Hasan On Mon, Nov 19, 2018 at 12:35 PM Chuck Furman wrote: > I have gone

Re: [wsjt-devel] Problems with RC4

days. I can get > spots on PSK Reporter from stations running RC3. It's just that if they > respond to me without setting RC3 to 77-bit, I'll never decode them. > > Jim > > On 11/17/2018 14:53, Hasan al-Basri wrote: > > RC4 cannot be copied by RC3 in FT8. RC3 cannot be copie

Re: [wsjt-devel] Problems with RC4

Giuseppe, It may appear that RC4 is less sensitive, but that is not true. It is most likely that you are misinterpreting what you are seeing. The reason you see 90% fewer decodes on RC4 than RC3 is that there are 90% fewer people using RC4 at this point. RC4 cannot be copied by RC3 in FT8. RC3

Re: [wsjt-devel] Candidate release WSJT-X 2.0.0-rc4

The five minute mouse timer business is going too far. Long MSK144 qsos over difficult paths, should not require the OP to be chained to the desk. Several ops are running (on a clear freq), for hours to complete. They aren't sitting in front of the mouse. The developers may not approve of this

Re: [wsjt-devel] Error loading LoTW Users Data and Network Error

Thanks! Hasan On Fri, Oct 19, 2018 at 8:35 AM Bill Somerville wrote: > On 19/10/2018 14:26, Hasan al-Basri wrote: > > Bill, > > I downloaded and installed the 32 bit OpenSSL software this morning. > (after I had downloaded and copied the the *.csv file yesterday as

Re: [wsjt-devel] Error loading LoTW Users Data and Network Error

Bill, I downloaded and installed the 32 bit OpenSSL software this morning. (after I had downloaded and copied the the *.csv file yesterday as a short term fix) ...and the copy fix worked. So, I thought I would do the full fix. After the install, I went to the colors tab where the Fetch button

Re: [wsjt-devel] "L" instead of colors for LOTW

I agree, the colors are becoming so ubiquitous, that they end up diguising as much as they highlight. Some color is good, a lot of color can be overwhelming. I like a simple L for LoTW user. Save the colors for things more dramatic that require immediate notice like CQ, and My call Hasan On

Re: [wsjt-devel] Major Virus Like Bug in V2

That's why I said "virus-like" in that anyone receiving the bad tone set would begin transmitting it. ...but it pays to be careful., I don't want anyone thinking I was saying that the team unleashed a computer virus :-) Thanks for the quick attention. 73, N0AN Hasan On Wed, Sep 19, 2018 at

Re: [wsjt-devel] Major Virus Like Bug in V2

to 1.9 on 260, V2 abandoned until fixed. > > > > > 73 Steve k9an > > > On Sep 19, 2018, at 10:52 AM, Hasan al-Basri > wrote: > > > > When running MSK144, the program will start tx'ing some weird sounding > tones...they will "infect" any V2 MSK144 s

[wsjt-devel] Major Virus Like Bug in V2

When running MSK144, the program will start tx'ing some weird sounding tones...they will "infect" any V2 MSK144 station that hears them and they will start sending the same strange tones. 5 of us have experienced this same bug...all simultaneously upon hearing those "odd" tones. I'm betting it

Re: [wsjt-devel] WSJT-X 2.0 possible new mode/protocol

Igor, If you believe that DX-Spotting is equivalent to internet assisted sensitivity enhancement, then there is no point in further discussion. Apples and oranges, at the very least. N0AN Hasan On Mon, Sep 10, 2018 at 12:58 AM Игорь Ч via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: >

Re: [wsjt-devel] WSJT-X 2.0 possible new mode/protocol

Bravo, George! Internet help with the decode? That's downright silly. If we are going to use the internet to replace even a portion of the performance of rf, heck why bother with rf at all, and we can have infinite sensitivity? Hasan On Sat, Sep 8, 2018, 6:13 PM George J Molnar wrote: >

Re: [wsjt-devel] Observation on Expedition Mode

1239 UTC 01July18 , 14.090 USB Fox/Hound FT8 Up to 4 streams running -3 dB with a Tribander at 52'. Also seeing them with 110' CF dipole at -8 db, and with -8 dB on my 6 meter LFA! In other words, very good signals on 20m I worked them in less than 2 minutes, probably first call. Latest 5

Re: [wsjt-devel] How much operating time before rebooting your computer

I have observed this issue when win10 is waiting to update, but I haven't been notified that an update is pending. I discovered this when I noticed My 2nd wsjt-x machine was only decoding about one half the stations that my other machine was. When I told the 2nd ma Hine to restart, it immediately

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

Random callers below 1000 are ignored. Those who have already "engaged" the Fox are automatically moved below 1000 to finish the qso...that's how the software works. Of course, there are those who have no idea what they are doing, can't read and/or won't read, plus the deliberate qrm'ers...I saw

Re: [wsjt-devel] DXpedition Mode on 40 Meters?

Agreed on all counts, Gary. 73, N0AN Hasan On Wed, Mar 28, 2018 at 1:21 PM, Gary McDuffie <mcduf...@ag0n.net> wrote: > > > > On Mar 28, 2018, at 5:48 AM, Hasan al-Basri <hbasri.schie...@gmail.com> > wrote: > > > > Running DXp by the developers fo

Re: [wsjt-devel] WSJT-X v1.9.0-rc3: Testing of FT8 DXpedition Mode

Excellent, Look forward to it, Joe. 73, N0AN Hasan On Wed, Mar 28, 2018 at 12:35 PM, Joe Taylor wrote: > The second public test of FT8 DXpedition mode will be conducted on April > 7, a little over a week from now. You are cordially invited to join us for > this test. See

Re: [wsjt-devel] Alternative FT8 DXpedition mode freqs.

*The WSJT-X Development Group selected the FT8 frequencies now being used by all. I believe that after serious consideration, they should define a recommended DXpedition mode frequencies for each HF band. I'd further recommend that the 'Frequencies' table be populated with these recommended

Re: [wsjt-devel] DXpedition Mode on 40 Meters?

Quoting from K9YC: "It is a LONG established principle of ham radio, defined by FCC Rules and corresponding laws in other countries, that no one person or group has priority on any given frequency at any given time; indeed, these Rules (laws) establish only permitted emission types for a range of

Re: [wsjt-devel] DXpedition Mode on 40 Meters?

r DX operations? > > 73’ > Tom > GM8MJV > > > > > On 27 Mar 2018, at 13:15, mwbese...@cox.net wrote: > > Hasan, > > Thank you for that very eloquent post! I think your suggestions are > spot-on and I'd LOVE to see all of them implemented. > > 73,

Re: [wsjt-devel] DXpedition Mode on 40 Meters?

My suggestions were specifically about the DXp mode, not FT8 in general. ..and it isn't a popularity contest, it's about observing the existing watering holes. PSK31 is in use, it will recover somewhat when more people get bored with "wham bam , thankyou ma'am" operating style. I enjoy both FT8

Re: [wsjt-devel] DXpedition Mode on 40 Meters?

I agree with every point that Mike (WM4B) made. DXpedition mode is becoming a scourge on the bands w/r to other modes. Another person asked for suggestion instead of complaints. OK, try this on: 1.Disable the mode until *real* precautions are taken to observe the current watering holes for

Re: [wsjt-devel] DXpedition mode: dissapointed somehow

...but, they DO QRM others, that is why DXp is reserved for legitimate full blown DXpeditions, not just rare DX Stations, but Full DXpeditions. Otherwise, any time a "rare" dx station comes on, DXp mode destroys the entire segment that it has hijacked from some other digital mode that is used to

Re: [wsjt-devel] Status patch

Bill and Mike: I have received an updated pstRotatorAZ file from Codrut, to test with the new Grid Square presence in wsjtx_status.txt Initial tests successful. I clicked on a CQ with Grid square and rotor turned to grid coordinateAND, there was no lookup or call fill-in next to the green

Re: [wsjt-devel] Frequency Labels Suggestion

You can have as many lists with as much or as little frq info as you like, if you will just create a configuration for it. I did this for the Fox/Hound Test. I Cloned a working FT8 configuration. I switched to that "Copy (as it is labled -Copy) , then renamed it to Fox/Hound Test. Then I went

Re: [wsjt-devel] Timer

All four stations were strong. K1JT started out at +15 on 20 meters, but within 20 minutes had dropped to -23 (late afternoon band change). 30 dB change in about 20 minutes...talk about catching the band moving! Completed with all 4 stations, but one completion was aided by a trick on my end.

Re: [wsjt-devel] Timer

Bill, TX timeout timer is about right. Prevents non-stop (when not being heard) QRM from Hounds. Also, when it times out, you have time to let a couple cycles go by and see where in the band it might be best to call (look for hole). I did this multiple times (let it expire), watched the pileup,

Re: [wsjt-devel] Timing

1. Cheap: WWV (free) Set manually. It's easy to get within 1 second. 2. BktTimeSync (free and will use either internet or gps) 3. Meinberg (free) 4. Dimension4 (free) All work . I have used 2 and 4 and they are both terrific. Lastly, the timing requirement has been relaxed a bit, about 2 seconds

Re: [wsjt-devel] False Frequency reports

If that was fixed, I missed it! It would be wonderful if that's the case. I'll have to watch for it. Tnx tip 73, N0AN Hasan On Wed, Oct 25, 2017 at 9:17 PM, Gary McDuffie <mcduf...@ag0n.net> wrote: > > > > On Oct 25, 2017, at 7:51 PM, Hasan al-Basri <hbasri.schie.

Re: [wsjt-devel] Capter 13.1 Freq Cal document problems 1.8-RC3

gt; The missing manual :-) > > As a thanks, I took a try at cleaning up the text formatting, and > re-attached the MS doc file for you. > > THANKS again, > > Neal > N6YFM > > On Fri, Oct 20, 2017 at 4:16 PM, Hasan al-Basri <hbasri.schie...@gmail.com > > wrote: &g

Re: [wsjt-devel] Capter 13.1 Freq Cal document problems 1.8-RC3

Neal, That's why I wrote the attached. If you follow it, it will work. (I'm not a developer...I had to work through the instructions to end up with what I"m sending you.) If you have RC3 1.80 WSJT-X, these instructions work perfectly. Lemme know how you make out. 73, N0AN Hasan On Fri, Oct

Re: [wsjt-devel] WSJT 1.8.0 RC3

only have one functioning hand! > > > > Regards > > > > Dave > > (M6RUG) > > > > *From:* Hasan al-Basri [mailto:hbasri.schie...@gmail.com] > *Sent:* 17 October 2017 21:19 > *To:* WSJT software development <wsjt-devel@lists.sourceforge.net>

Re: [wsjt-devel] WSJT 1.8.0 RC3

Probably not and easily worked around. Instead of double clicking on the station, do a Ctrl-Double Click...that will put rx and tx on same freq. Just learn the "new" way to do the old thing and you will be fine. Lock Rx /Tx was removed for good reasons...but I don't want to get into a discussion

[wsjt-devel] r8053 FreqCal with Apply Works Very Well

I just did a FreqCal on my SDR using the new method in r8053. It now not only calculates and tests the values collected in fmt.all, it has an Apply button that writes the values for Slope and Intercept to the Settings > Frequencies boxes supplied for same. It also deletes fmt.all, after you tell

[wsjt-devel] Solve For Calibration Parameters: Suggestion

r8144 When the pop up window shows the results of the calibration run with Slope and Intercept presented, wouldn't it be nice to have a button or check box that says: "Apply Calibration Results Now"...or some such? Right now OK, closes the window, which is fine, but it would save a lot of

[wsjt-devel] Repeating Crash When Changing Slope and Intercept

Every time I either zero out or change the slope and intercept after doing a calibration run, I get a program crash, and stale lock. When I restart, the new values are in place and things run fine. This has been last several versions since I've been playing with FreqCal Currently r8144 73,

[wsjt-devel] New Internal FreqCal Mode with Solve For ...

r8144 for reference First of all WONDERFUL. Makes all that writing I did superflous. An important reminder (I think): If you are going to do repeated runs using different frequencies (for example, eliminating 20 MHz wwv for a night run, or eliminating 2.5 MHz wwv for a day run), be sure to ZERO

Re: [wsjt-devel] Same freq moves = QRM!

Rich, I agree with you completely, as my experience is the same as yours. No matter how it is implemented, I'm typically NOT going to call on on the OPS Tx freq...it is too congested and just adds to the "local" QRM. It is true that the band fills up with spread out callers using our

Re: [wsjt-devel] Another r8123 Comment

as much a problem with JT65 or JT9 when there are > approximately 10 seconds to react and disable Tx manually. > > Ed, K0KC > > k...@arrl.net > http://k0kc.us/ > > > On Tuesday, September 26, 2017, 8:03:08 AM EDT, Hasan al-Basri < > hbasri.schie...@gmail.com> wr

Re: [wsjt-devel] Another r8123 Comment

That's a feature, not a bug, i.e., intentional 73, N0AN Hasan On Tue, Sep 26, 2017 at 6:30 AM, Ed Wilson via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > Although it is not new to r8123, I have noticed that when I call a station > and someone else is also calling him or her and that

Re: [wsjt-devel] Dx Call Entry with Gnerate Std Msgs Should Default to TX6 (CQ)

x and then call CQ. As you know, skeds > sometimes proceed this way - two stations meet on a frequency with a prior > understanding that, say, “A” would answer “B’s” CQ, if possible. > > Steve k9an > > On Sep 12, 2017, at 9:22 PM, Hasan al-Basri <hbasri.schie...@gmail.com>

[wsjt-devel] Dx Call Entry with Gnerate Std Msgs Should Default to TX6 (CQ)

I have played with this quite a bit and cannot figure out the reason for the following: I meet a station on Ping Jockey and we agree to begin a qso. I enter his call in the blank DX Call box , K1SIX. I click the Generate Std Msgs box, and the TX1 thru TX6 populate. But...the TX defaults to