Re: [wsjt-devel] Start With Main Window Minimized, Wide Graph Closed.
It o-end where you left it when last closed. Regards and 73s VE3FBZ London Amateur Radio Club www.larc.ca > On Oct 5, 2019, at 11:12, W3OA wrote: > > Is there a way to start WSJT-X so that the main window is minimized and the > Wide Graph window does not open or is closed immediately? > > If not, is this an option the developers would consider including in future > versions? > > This would be useful for users running multiple instances to forward spots to > the Reverse Beacon Network. > > 73 - Dick, W3OA > > > > ___ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] FT8 Screen Layout
Understandable with a small screen. I use a second screen and even add in QRZ info, call info window from JTALERT and ACLOG. I find the size of the icons ok. Being a previous programmer analyst the toughest job I had with clients was screen layout. No one would ever agree on placement of fields. The old adage “ you can please some of the people some of the time but not all of the people all the time.” Is the usual environment. I believe the code is available to modify if you wish. Moving the screen layout is no small task but can be done without reducing the functionality of the application. Unless one of the developers sole task is screen layout then it could be done in time. I’m sure they, the developers, have their hands full keeping up with bug fixes, maintaining compatibility with other application changes - everyone is enhancing - and maintaining several OSs. Good luck. Cheers Frank Regards and 73s VE3FBZ London Amateur Radio Club www.larc.ca > On Aug 15, 2019, at 15:06, David Gilbert wrote: > > > Apologies again if this has been covered before, but I went back through the > list archive to the beginning of 2019 and didn't see a related post. > > Why is so much of the FT8/4 main screen space devoted to the lower half of > the window at the expense of the activity windows? The layout just seems > really inefficient. The Frequency and Date/Time bars are huge, the DX Call, > DX Grid, Lookup, and Add blocks could all be arranged differently to save > both vertical and horizontal space, and the space between and around the > Standard Message blocks could be reduced. The Band Activity and Rx Frequency > titles could be part of the gray header bars instead of taking up their own > vertical space. Even the Log QSO, Stop, Monitor, Erase, etc buttons could be > arranged vertically just to the left of the standard messages instead of > having so much blank horizontal space in the message blocks. > > It just seems weird to me that the more useful Band Activity information > takes a back seat to other less useful formatting. I use a 1600 x 900 laptop > with minimal space devoted to JTAlert and the WSJT-X spectrum display, which > leaves only seven lines of info for the activity windows. Scrolling back is > a hassle and wastes time. The font on the menu bar is quite small so it > isn't likely that somebody decided that Frequency and Date/Time needed to be > that big to be seen. > > What am I missing here? > > Thanks es 73, > Dave AB7E > > > > ___ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Lid operators or bad design?
I agree with Steve. Like most old time (mature) hobbies the early pioneers are either SKs or nearing the time when they can no longer operate. We need young blood into the hobby. Not many, if any will build any more, so we must move a bit into their sphere. They are growing up in the “digital” times and are dragging us into the 21 century. They need an Elmer not a head master. If you are not willing to teach by setting example then stay away from the new and experimental modes and stick to SSB and CW. I do not know when they”lid” terminology originated, possibly it should be banned from our vocabulary and replaced with “how can I help “ Enjoy. Regards and 73s VE3FBZ London Amateur Radio Club www.larc.ca > On Jul 29, 2019, at 02:03, Stephen Ireland wrote: > > Hmmm . trying to stay out of this one but can’t > > Even a few minutes back on 20m minute I just had an op do just as Andy K3WYC > reported .. and then that very same station call CQ... > > The solution is as Bill and many others report to set “Hold Tx Freq” ... and > to ensure that this is set as default. > > At a technical level, perhaps any version upgrades (regardless of previous > state) should set this? > > Yet there is also an ethical aspect to this discussion it also highlights > the issue and concept of the arrogant term “LID” You see some ops now > sending (frustration) messages such as “LID ” ... > > Utilising this arrogant obnoxious term degrades all the Amateur community. > > Perhaps the greatest “LID” is actually the one identifying potential “LID’s”? > > Using the term “LID” in the first place is not helpful for the growth and > development of AR – with AR being a regulated place of education and > learning that should be safe (including bullying-free) for people of all ages > and ways of life. > > Many dominions are now permitting entry-level Licence classes to have digital > mode access, with more and more dominions (such as Australia) proposing and > granting these rights this every day. > > This opens the whole discussion internationally of whether entry-level ops > with entry-level qualifications, with potentially low competency levels, > should really have access to Digital modes – especially new and developmental > modes such as the relatively immature FT suites. This matter should be taken > up as a general discussion point with the IARU and perhaps a clear position > put forward for the guidance of all Amateur regulatory domains. > > Operators need to learn and will make what some perceive to be mistakes ... > and the only way they get better is through observation, practise and through > constructive guidance from others. > > Perhaps also a bit of tolerance (and massive discouragement of the use of the > term “LID”) is required ... and not just with the JT modes either? > > 73 > > Steve I > > Sent from Mail for Windows 10 > > From: rjai...@gmail.com > Sent: Monday, July 29, 2019 1:24:50 PM > To: WSJT software development > Subject: Re: [wsjt-devel] Lid operators or bad design? > > Are they in the same time slot? If they are on odd and you are on even, no > real harm. FT8 is operated primarily split anyway. > > I do know this used to be an issue when lock rx=tx was a thing that people > would work you then transmit in your frequency slot. > > 73, > Ria > N2RJ > >> On Sun, Jul 28, 2019 at 11:58 AM Andy Durbin wrote: >> Everyone who uses WSJT-X for FT8 must have noticed the number of operators >> who answer a CQ and then, when the QSO is complete, call CQ on the same >> frequency. Are all these operators really stupid or are they being trapped >> by a weakness in the user interface design? >> >> 73, >> Andy, k3wyc >> ___ >> wsjt-devel mailing list >> wsjt-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wsjt-devel > ___ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Lid operators or bad design?
Why do we have to hold “their” hand. In the documentation it says “To avoid QRM from competing callers, it is frequently desirable to answer a CQ on a different frequency from that of the CQing station. Choose a Tx frequency that appears to be not in use. The same is true when you tail-end another QSO.” Find an open spot, click hold TX and operate. When you change bands make sure you are still clear of other operators. Use common sense and courtesy. No sense brow beating the ones who do not care - they probably do not listen anyhow. My 2 cents Regards and 73s VE3FBZ London Amateur Radio Club www.larc.ca > On Jul 28, 2019, at 16:45, Jim Nuytens via wsjt-devel > wrote: > > No user interface design will ever be idiot proof. The supply of idiots far > outstrips the supply of programmers. > > Sent from my iPad > >> On Jul 28, 2019, at 11:53 AM, Andy Durbin wrote: >> >> Everyone who uses WSJT-X for FT8 must have noticed the number of operators >> who answer a CQ and then, when the QSO is complete, call CQ on the same >> frequency. Are all these operators really stupid or are they being trapped >> by a weakness in the user interface design? >> >> 73, >> Andy, k3wyc >> ___ >> wsjt-devel mailing list >> wsjt-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wsjt-devel > ___ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Lid operators or bad design?
Just hold TX.—- Regards and 73s VE3FBZ London Amateur Radio Club www.larc.ca > On Jul 28, 2019, at 11:53, Andy Durbin wrote: > > Everyone who uses WSJT-X for FT8 must have noticed the number of operators > who answer a CQ and then, when the QSO is complete, call CQ on the same > frequency. Are all these operators really stupid or are they being trapped > by a weakness in the user interface design? > > 73, > Andy, k3wyc > ___ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] WSJT Audio Input Loss
Yeah, in the old days of data bases we used to call that ac”deadly embrace” Regards and 73s VE3FBZ London Amateur Radio Club www.larc.ca > On Jul 6, 2019, at 14:54, Rick Drexel wrote: > > Your observations match those I have seen for about a year. I've tried to > find a common set of circumstances that always cause the failure but have had > no luck. I use WSJT-X in FT8 receive mode and PSKREPORTER to check band > performance over a long time period. After a random amount of time, WSJT-X > come to a halt. Specifically the Wide Graph Display and the Band Activity > Display stop updating. The UTC in the Wide Graph Display no longer matches > the UTC in the bottom left portion of the Main window. There is no > correlation between the activity on the band and the time it takes to hang. > Rarely does it not hang. > > As a software developer this has all the hallmarks of a race condition > failure. Two (or more) threads update a shared resource without using a > LOCK, UPDATE, UNLOCK sequence. During a thread context swap one of the > threads reads the value, loses control to another thread that updates the > value, then the first thread gets scheduled and writes back its stale value. > The result is undefined behavior. > > Most of the time there is no conflict. Even under a heavy load. Then it > fails unexpectedly. This makes it extremely difficult to debug. > > To recover I have to exit out of WSJT-X and restart it. > > This might not be the root cause but I would put it high on my list of the > usual suspects. > > 73, Rick > WK1P > > > From: Peter Putnam > Sent: Wednesday, July 3, 2019 3:06 PM > To: wsjt-devel@lists.sourceforge.net > Subject: [wsjt-devel] WSJT Audio Input Loss > > Greetings, > > I have been using WSJT-X quite successfully for several years during > June VHF Contests. I experienced a failure of the WSJT program to accept > received audio input after several hours of proper operation during the > recent Field Day exercise. > > I'll provide a brief outline and reply with more detail, should it be > needed. > > My computer is a Dell Optiplex 780 running Win 7 Pro SP1, 64-bit. The > WSJT-X software version is 2.0.1 7ddcb7. > > My receiver is a Flex 6500. It passes data to a Flex-supplied "DAX" > program that interfaces various applications that wish to receive the > audio stream. WSJT accepts the stream and displays results on the Wide > Graph and a small audio signal-strength window. Activity proceeded > normally for the first three hours of Field Day, until both the Wide > Graph and the audio signal-strength stopped showing any incoming audio. > > I can't offer any help on what might have caused the problem. It was > abrupt and seemingly unrelated to any other system actions. I am unable > to reproduce the problem. > > Several operators spent several hours speculating about what a solution > might be. Program restarts and computer re-boots (time-tested favorite > of generations) changed nothing. The only useful clue was that the DAX > audio output stream was present and could be re-directed to Fldigi, but > not to WSJT-X. > > I was able to restore operation for a brief period by stopping WSJT, > renaming WSJT.ini and restarting WSJT. That fix lasted for a half hour. > Repeating the procedure provided operation for the rest of Field Day. > > The two .ini files that were renamed are available for your inspection, > along with the one that continued to function. > > Any suggestions you can offer to prevent a recurrence would be greatly > appreciated. > > Regards, > Peter > NI6E > > > > > > > ___ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fwsjt-develdata=02%7C01%7C%7Cc8a88765c47b45e54e0208d6ffea13fc%7C84df9e7fe9f640afb435%7C1%7C0%7C63698175354267sdata=QIhhN8eBXU7WkgMKIK4WOGh%2BO2Zt6d3mRyQ5qFFV%2FGM%3Dreserved=0 > ___ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Announcing the World Wide Digi DX Contest
I use N3FJP logging program interfaced through JTALERT Regards and 73s VE3FBZ London Amateur Radio Club www.larc.ca > On Jul 3, 2019, at 11:56, Joe wrote: > > What Logger is anyone planning to use for this contest? > > Joe WB9SBD > > The Original Rolling Ball Clock > Idle Tyme > Idle-Tyme.com > http://www.idle-tyme.com >> On 6/29/2019 3:25 PM, Don Hill AA5AU wrote: >> For immediate release. June 29, 2019. >> >> The World Wide Radio Operators Foundation (“WWROF”), in collaboration with >> the Slovenia Contest Club (“SCC”), is pleased to announce the first annual >> World Wide Digi DX Contest (“WW Digi”). The new contest taps into the >> excitement being generated by the new digital modes pioneered by Joe Taylor >> K1JT and the WSJT-X development team. The contest will occur over 24 hours >> on August 31 and September 1, 2019 using the FT4 and FT8 modes on the 160, >> 80, 40, 20, 15, and 10-meter bands. >> >> WW Digi will utilize a distance-based scoring system to measure operators’ >> abilities in making DX contacts across the 6 HF amateur radio bands. >> Contacts will earn points based on the distance between grid square centers >> of the two stations. This will encourage operators to seek out long distance >> weak signal contacts that highlight the technical advantages of the new >> digital modes. >> >> To encourage activity across all bands, a multiplier will be given for each >> new 2-character grid field contacted on each band. The final score will the >> product of the total contact points times the number of grid fields >> contacted. There should be plenty of strategy required to balance distant >> QSOs and the need to work all available grid fields. Single and >> multi-operators are welcome to operate as much or as little of the 24-hour >> contest period as they wish. >> >> The contest has been designed to enable making contacts utilizing standard >> WSJT-X software behavior, making it easy for non-contesters to participate. >> At the same time, the contest supports some new techniques that will >> encourage operating innovation, such as permitting stations to work up to >> three “QSO streams” on a band at one time. Robotic operation is specifically >> prohibited in order to keep the human element as part of the game. The full >> rules and other information are available on the WW Digi DX contest web site >> at https://ww-digi.com >> >> It is fitting that the World Wide DX contest series be expanded with a >> fourth mode, Digi, to support evolution into ham radio’s future. >> Accordingly, with WWROF’s sponsorship of the World Wide Digi DX Contest, >> there will now be similar worldwide DX contests at the end of four >> successive months, August through November. >> >> Serious contesters and casual participants alike can make ham radio history >> and have fun as the hobby pioneers the exciting world of digital >> communication. WWROF hopes the WW Digi DX Contest will attract new digital >> operators into contesting. >> >> Plaques will be awarded for top scorers. Please contact the WW Digi Contest >> Director Ed Muns, W0YK at plaq...@ww-digi.com to sponsor an award. >> Electronic certificates will also be available for download for anyone that >> submits a log. The goal is to have results available on the web site within >> 90 days after the end of the contest. >> >> About WWROF >> The World Wide Radio Operators Foundation is dedicated to improving the >> skills and fun of amateur radio operators around the world by utilizing >> education, competition, advancement of technology and scientific research, >> promoting international friendship and goodwill. >> WWROF is a non-profit, donor-supported, organization which sponsors this >> contest and provides the infrastructure for log submission, log checking, >> and other services in support of many popular radio contests. Please visit >> wwrof.org for more information. >> >> About SCC >> The Slovenia Contest Club has a long tradition of supporting digital >> contesting with its annual RTTY Championship contest held the last weekend >> of August. For more information about SCC please visit >> http://lea.hamradio.si/scc/ >> >> >> >> >> ___ >> wsjt-devel mailing list >> wsjt-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wsjt-devel > > ___ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Clock patch
Island people can always sync from know short wave time standards. WWV, CHU. I send jtx msgs but they still not connect. Let them figure out that setting their time correctly will help increase their contacts. My 2 cents...again. Regards and 73s VE3FBZ London Amateur Radio Club www.larc.ca > On Jun 26, 2019, at 07:04, Roeland Jansen wrote: > > > you are right it does. On the other hand do you really want people to be off > on time? > > You could consider instead of b0rking out -- if there is no internet, warn > and go on. > > Then you have three groups: > > a) groups of people that understand that any system without correct time > settings should not be switched on for a start. > and they have good timing. this group is totally OK > > b) the peope without internet because they are on a weird idland without > internet --> they can go on. this group is totally OK > > c) people who have internet and have the time wrong. Those will be stopped > dead in the tracks. this group is NOK > > I know it's a bastard operator from hell solution but sometimes forcing > people helps. > > and it's just an idea... just an idea > > > >> On Wed, Jun 26, 2019 at 12:20 PM Bill Somerville >> wrote: >> On 26/06/2019 10:55, Roeland Jansen wrote: >> > I did not look at the patches Mike sent but: >> > >> > https://time.is/ >> > >> > gives you how good/bad the time is. If you start up: do check like >> > this and refuse to go on if the timeskew is too large. >> > Add a link how to fix in the message and you force people to fix it. >> > >> > (not that people read notices) >> > >> > just my bad idea. >> >> Hi Roeland, >> >> doesn't that miss the point that many of the poor time sync situations >> are where the user has no Internet connectivity? >> >> 73 >> Bill >> G4WJS. >> >> >> >> ___ >> wsjt-devel mailing list >> wsjt-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wsjt-devel > ___ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Field Day time problem
Why add complexity/code to the software app when the problem is the user - not the software or the rest of the community? Regards and 73s VE3FBZ London Amateur Radio Club www.larc.ca > On Jun 25, 2019, at 04:51, DG2YCB, Uwe wrote: > > The old JT65-HF Comfort had one additional feature: With “DT offset” one > could temporally shift DT until +- 2.5 seconds (in steps of 100 ms). Very > useful in situations where PC time sync failed, for whatever reasons. IMO > would be good to implement something like that to WSJT-X. Not a big deal, but > works 100 %. > Yes, TimeFudge could do something similar, but (A) it’s only available for > Windows, and (B) at least for me it was sometimes difficult to see which is > the correct system time and which is the “fudged” time (especially when one > had to do more than one correction). With the JT65-HF Comfort functionality > it was easy to see that. (After restarting the software it should be > automatically set to zero again.) > > > > 73 de Uwe, DG2YCB > ___ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Field Day time problem
Do not understand all the ragging about other people’s incorrect computer time. It’s their problem, not ours (mine). I simply avoid them and they miss out on a contact. Now that out of adjustment time is flagged, it’s a non issue. BTW if all returns are flagged as out of sync it’s your computers problem, not the rest of the world. I agree, let’s not turn a fantastic application into bloatware like Apple’s I-tunes and versions of Windows. Fantastic field day on FT8. Regards and 73s Frank VE3FBZ London Amateur Radio Club www.larc.ca > On Jun 24, 2019, at 06:00, Hasan al-Basri wrote: > > 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. > Another good program for setting time from GPS is NMEATime2, which I use. > > Let's not turn WSJT-X into Bloatware just because people can't seem to set > their own clocks from readily available sources. I'm not disputing the > problem, (FD particularly is full of incompetent first time, ill-trained > digital ops who have the thought, "oh, wouldn't this be fun, I'll show the > guys what a cool mode this is"). > > I just don't agree with constantly trying to make up for poor operating > practices with software solutions. > > In WSJT-X, not setting one's clock when only a cursory RTFM, as well as > minimal effort and investment are required is, to my mind, poor operating > practice. > > ...and BTW, get off my lawn. :-) > > 73, N0AN > > Hasan > > >> On Mon, Jun 24, 2019 at 4:11 AM Tom Melvin wrote: >> All >> >> This posting by Fred gets my vote - easy, fool proof and does not distract >> the dev team. >> >> >> -- >> 73’s >> >> Tom >> GM8MJV (IO85) >> >> >> >> >> >>> On 24 Jun 2019, at 09:27, Fred Price wrote: >>> >>> You are all overthinking the problem. There are programs to set your >>> computer clock by a GPS dongle. A good plug in dongle from Amazon is $12USD >>> and the program I use BktTimeSync is a free download. >>> Also if the dev group keeps adding more n more WSJT will become bloatware. >>> I'd rather see improvements in what is in the software already. If you want >>> a color to denote a time that is getting out use JTAlert, it already has >>> that in it. >>> >>> On Jun 24, 2019 4:07 AM, "DG2YCB, Uwe" wrote: >>> A very good idea to set up time beacons, Reino! I like this approach! >>> >>> >>> However, as a short-term solution IMO dev team should find a way to use the >>> EXISTING data set of DT values for a pop-up saying that very likely time is >>> not synced correctly, plus an option to correct time by one click. Look the >>> following example. Only one station has a DT value which is totally out of >>> the average. Would be easy to detect such things by any well programmed >>> algorithm. Even the old JT65-HF software had two additional buttons, where >>> one could simply set PC clock + or – some 100 ms (until +- 2.5 s). Was very >>> helpful for fieldday activities. Just click on + or – as long as most of >>> the other stations have DT around 0. Simple approach, but worked 100%. >>> >>> >>> >>> 73 de Uwe, DG2YCB >>> >>> >>> -Ursprüngliche Nachricht- >>> Hi, >>> >>> >>> We are amateurs and could provide another time distribution experiment >>> especially during Field Day events. I mean setting up time beacon or >>> beacons that send e.g. every 15 s a short pulse, say 100 ms, on the base >>> carrier frequency e.g. 14.080 MHz. Timing of that pulse could be 'minute >>> mark - 1 s' or something similar agreed time. It would allow manual PC time >>> setting in the same manner as time marks of standard frequency stations. >>> That transmission would not disturb any FT8 message as nobody should >>> transmit at that time. It could be more useful, if the beacon frequency is >>> set to 1 kHz up (14.081), then you could hear it without detuning VFO and >>> disturbing you normal operation. Well, you could get same information from >>> dT values providing there are enough time accuracy in other stations and >>> you timing is good enough for decoding. >>>
Re: [wsjt-devel] Initial thoughts on FT8 and FD
Perhaps drop the grid in FD mode and put in the Class letter. I strongly support this modification. This would allow us to select wanted/require call to complete our maps etc. Regards and 73s VE3FBZ London Amateur Radio Club www.larc.ca > On Jun 22, 2019, at 16:57, WB5JJJ wrote: > > I’ve noticed that rc7 32b is still fully functional after several restarts to > check, even in FT4. Oops. Of course it may stop at any time. > > Also had to turn Call 1st off (operating 1D) because of all the “D”’s calling > me. My CQ does not indicate my class so everybody is clueless unless they > also watch the left window all the time. > > Perhaps drop the grid in FD mode and put in the Class letter. Even better, > don’t allow a “D” to auto connect to another "D" calling CQ when Call 1st is > active. That would speed thing up for sure. > > I'm sure bullets are now flying my way to punch holes in my suggestion, but > I'll duck out of the way as best I can and just go with the flow. > > WB5JJJ - George > ___ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] QRZ
JTALERT can be set up to provide this as well. Has a current , if updated, call sign look up file as well. Regards and 73s VE3FBZ London Amateur Radio Club www.larc.ca > On Jun 16, 2019, at 13:52, ea4bas wrote: > > Hi, > > I do not know if what I am going to expose, would be interesting in the > software of wsjt-x, is something that comes to my mind as user of N1MM > software and that has this utility incorporated, consists of having a BUTTON > called QRZ, and when a callsign is inserted in the DX Call of WSJT-X to click > on the QRZ button and know the correspondent's data directly > > 73 > Miguel > > > > > ___ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] USB codec missing,
Try the small program called "Fix Code 10 error” The question , did it ever work or quit. If not - important - was icom instruction on install followed to the letter. Does the codec show up when displaying usb devices. Windows auto update usually causes the problem if it worked previously. Hope this helps a bit. Frank Regards and 73s VE3FBZ London Amateur Radio Club www.larc.ca > On Jun 12, 2019, at 19:03, Matthew Miller wrote: > > Interesting, that's another different data-point for frequencies to use (I'm > not familiar with that groups.io but I think that site is where I had seen > talk of checking "the standard frequencies"). > > And just today there was a big fuss on the repeater a number of guys saying > how "digital especially FT8 is jamming and spamming over CW stations down in > the CW part of the band"...so I know I have to be rather careful being able > to cite why I pick where to use. > > Yes - the club I'm in arranges how many stations will be doing what, they've > got "generally" stations one SSB and one CW per band, and then I'm tasked > with "digital modes" open ended no band restrictions (well, within the field > day rules). I have done RTTY and PSK31 in years past, this year I'm hoping > to do better with FT8. Nobody has complained about interference from me in > the past...but the CW stations always obliterate my digital reception and > sometimes kill SSB too. > > I guess I'll try and build a configuration in WSJTX that has the standard > frequencies as well as the ones listed in this thread and on the site you > linked...shame there doesn't seem to be more coordination as to where to > operate for field day. > > -Matt / KK4NDE > > -Original Message- > From: Matt Power [mailto:mhpo...@mit.edu] > Sent: Wednesday, June 12, 2019 8:30 AM > To: wsjt-devel@lists.sourceforge.net > Subject: Re: [wsjt-devel] Proposed FT8 Frequencies for ARRL Field Day > >> Was there any more recent info on frequencies for field day? > > https://groups.io/g/FT8-Digital-Mode/message/2202 has a different plan with > (for example) 14130 instead of 14080. That might be a better place for > discussion, because Field Day frequencies for this year probably won't have a > direct effect on WSJT-X development. > > https://www.arrl.org/files/file/Field-Day/2019/2019-Rules-RevA.pdf > says a club may operate on 20 FT8, 20 CW, and 20 SSB simultaneously (6.3, > 6.7). Depending on equipment, antenna spacing, and the relative skills of the > 20 SSB and 20 CW operators, a 20 FT8 signal might interfere with 20 SSB more > than with 20 CW, Or vice versa. > > One question is whether the 14130-versus-14080 choice is important to the > more common case of clubs who plan to operate 2 (not 3) stations on 20m at > the same time. For example: > > Many clubs have a station tuning around all of 20 SSB (14150 and up) to look > for new QSOs throughout the daytime. They do this every year. > Their station isn't big enough to call CQ and run stations on 20 SSB. > This year, someone wants to add a second 20m station that transmits very > frequently on 14130. Would that often be a realistic conflict? > > Conversely, a club may be historically successful with S on 20 CW. > This year, someone wants to add a second 20m station that transmits very > frequently on 14080. Is it realistic that they'll make substantially fewer CW > QSOs on the high end of 20 CW? > > Matt, KA1R > > > ___ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > > > ___ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] "Invalid QSO Data" when trying to log during
I had the same issue once - invalid QSO date. Filled in the one missing data box - left side - and logged ok. Quit and restarted app with no further issues. Logged over 40 QSOs when I was on and off the rig. Kudos development team . Frank Regards and 73s VE3FBZ London Amateur Radio Club 100 years old in 2020 www.larc.ca > On Jun 4, 2019, at 21:38, Palle Preben-Hansen, OZ1RH wrote: > > Same problem here, after the first 2-3 QSO's were logged the small error > logging window from WSJT-X popped up with an error about invalid QSO data as > my send rpt+exchange did not appear in the QSO data to be saved. Almost every > QSO thereafter I had to enter my send report and state/serial nr to log the > QSO. A few times the received rpr+exchange was not in the log window either. > Also the 'Enable TX' got unselected so I missed several periods as I had to > enter my send data and pres 'Enable TX'. > > FT4 RTTY RU, Win 10, -rc7 64 bit on Huawei Matebook 13.9 Pro, I7 quad+16 GB > RAM. > > 73, Palle, OZ1RH > > -- > > Message: 2 > Date: Tue, 4 Jun 2019 19:52:02 -0400 > From: "K2DBK-WSJT" > To: "'WSJT software development'" > Subject: [wsjt-devel] "Invalid QSO Data" when trying to log during > mock contest - RC7 > Message-ID: <015a01d51b30$82196460$864c2d20$@k2dbk.com> > Content-Type: text/plain; charset="us-ascii" > > I was making a few contacts in the mock contest this afternoon and ran in a > problem where to an issue where the QSO completed but when I tried to log it > a dialog popped up that said "Invalid QSO Data Check exchange sent and > received". I've attached a screenshot of what was going on at the time. The > Rpt Sent & Rcvd fields were initially populated corrected but are blank now > as I think this was my 2nd or 3rd attempt to fill in and log. To finally get > it to log I hit Cancel on the logging window then clicked on Log QSO, filled > in the same information as before, and it went through. > > This happened a second time in the exact same way, and one thing that I > noticed that was the same (although unfortunately I don't have a screenshot) > is that there was another signal decoded in the Rx Frequency window between > my report to the other station and his RR73 to me. I don't know if that's > related but I wanted to mention it. > > I do have Save All decodes checked so I can provide those if it will help. > I'll continue to see if I can see this again. This is on Window 10 Pro > 64-bit running the 64-bit version of WSJT-X. > > -- next part -- > ___ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Time
Essentially if everyone sets up some time sync process to a time standard then the issues will be minimized. Regards and 73s VE3FBZ London Amateur Radio Club www.larc.ca > On Jun 4, 2019, at 15:14, Bill Frantz wrote: > >> On 6/3/19 at 4:56 AM, slotter+w3...@gmail.com (Dave Slotter) wrote: >> >> It doesn't do much good to be "in-your-face" about clock synchronization >> issues to the receivers of signals which are off by too high a delta, >> because it's the sender that needs their clock adjusted, not the receiver. >> >> However, your attention to the issue gives me an idea... If an instance of >> WSJT-X sees that most (90%) of remote signals it sees are too far off from >> its own, the chances are is that it's *the local user's* clock that needs >> adjusting, and that user could be alerted to sync their clock in that case. >> >> What do you think? > > What I think is that if the DX is off by 1.6 seconds, as happened recently > with 3D2CR, I don't care about time standards. He is the only one that needs > to decode me. Everyone else can just look at my track on the waterfall and > try to avoid being QRMed by me. > > My opinion is very different when I'm not operating in Fox/Hound mode, > although I still want to be able to sync with a station with a bad clock if > he is an all time new one. > > In all cases, a warning that your clock differs from most others on the band > might be a useful warning. > > 73 Bill AE6JV > > --- > Bill Frantz| I like the farmers' market | Periwinkle > (408)356-8506 | because I can get fruits and | 16345 Englewood Ave > www.pwpconsult.com | vegetables without stickers. | Los Gatos, CA 95032 > > > > ___ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] Rc7
Downloaded RC7 Win 10 64 bit version Works great. QSOs On 14.080 Working with JTALERT 12.13.7 ok. Logging ok. Response great. Thanks a million Development Team. Regards and 73s VE3FBZ London Amateur Radio Club www.larc.ca ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Time
Morning all, continued super support group. I use Dimension 4 to keep my Win 10 laptop in sync. I like the the red flag on an out of step clock. I simply avoid the call. I’ve tried to inform the user in the past to no avail. Regards and 73s VE3FBZ London Amateur Radio Club www.larc.ca > On Jun 3, 2019, at 07:56, Dave Slotter wrote: > > Mike, > > It doesn't do much good to be "in-your-face" about clock synchronization > issues to the receivers of signals which are off by too high a delta, because > it's the sender that needs their clock adjusted, not the receiver. > > However, your attention to the issue gives me an idea... If an instance of > WSJT-X sees that most (90%) of remote signals it sees are too far off from > its own, the chances are is that it's the local user's clock that needs > adjusting, and that user could be alerted to sync their clock in that case. > > What do you think? > > -Dave > W3DJS > >> On Mon, Jun 3, 2019 at 7:48 AM Black Michael via wsjt-devel >> wrote: >> Would probably be good if WSJT-X did what JTAlert has started >> doing...highlighting DT values > 1.5 sec. >> >> For FT4 perhaps highlight > 0.5 seconds since if both sides are off -.5 and >> 0.5 I assume that would be an unlikely decode. >> This is what JTAlert does now. >> Then, also put some help in the manual about time setting on common >> platforms when people what to know why all of the DT values are being >> colored. I've been notifying quite a few people about their clocks but a >> lot of them don't even have email addresses on QRZ so can't be notified >> easily. There needs to be something a bit more in-your-face about time >> problems. >> >> <1559561734243blob.jpg> >> >> >> de Mike W9MDB >> >> >> >> >> ___ >> wsjt-devel mailing list >> wsjt-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wsjt-devel > ___ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] : Bug report - non urgent- WSJT-X V2.0.0 build 784f75 - comments and power not sticky.
Begin forwarded message: > From: VE3FBZ > Date: December 26, 2018 at 12:50:54 PM EST > To: wsjtgr...@yahoogroups.com > Subject: Bug report - non urgent- WSJT-X V2.0.0 build 784f75 - comments and > power not sticky. > > I have found both comments and power level shown on logging window are not > sticky although checked. > Comments can be changed but revert back on next log report. > > Comments are always what is in the config file section - > [LogQSO] > SaveTXPower=true > SaveComments=true. > LogComments=xx - whatever text. > > Changing comments here will appear on all log window pop up regardless how > they have been modified from QSO to QSO. > > I have closed the Pgm with exit,X or with JTALERT with no change in behavior. > > If mentioned before, apologize for another notification. > > > Keep up the good work. Kudos. > > Happy New Year. > > Regards and 73s > VE3FBZ > London Amateur Radio Club > www.larc.ca > > Regards and 73s VE3FBZ London Amateur Radio Club www.larc.ca > ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Transition to FT8 and MSK144 v2.0
Good show. Made 24 contacts in about 40 minutes this morning on 40M My screen was blue with new call CQs. Mostly eastern seaboard US. One QSO with Japan. Upgrade club PC , www.larc.ca, this morning. Regards and 73s VE3FBZ London Amateur Radio Club www.larc.ca > On Dec 14, 2018, at 12:14 PM, Joe Taylor wrote: > > Many thanks to all those who are helping to further the transition to new > protocols for FT8 and MSK144! > > This morning I ran an instance of WSJT-X v1.9.1 in parallel with WSJT-X 2.0. > An informal count of decodes in the old and new protocols shows far more > activity using the new 77-bit messages. Here are the rough statistics, given > as the ratio of new- to old-style decodes: > > For FT8: > --- > 17m: 10:1 > 20m: 3:1 > 30m: 6:1 > 40m 20:1 > > MSK144 > -- > Lots of activity on both 6 and 2m, all using v2.0 > > Clearly upgrading process is going well. > >-- 73, Joe, K1JT > > > ___ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] WSJT-X 2.0.0: GA release
Installed with issue. First contact on first chase. N4RCL USA Saw Contact in Romania so possibly EU moving to V2.0 gold. Regards and 73s VE3FBZ London Amateur Radio Club www.larc.ca > On Dec 10, 2018, at 9:05 AM, Joe Taylor wrote: > > The WSJT Development Group is pleased to announce the general availability > (GA) release of WSJT-X Version 2.0.0. > > If you have been using version 1.9.1 or earlier, or one of the candidate > releases v2.0.0-rc#, it's important to upgrade now. The original protocols > for FT8 and MSK144 are no longer supported. With v1.9.1 and earlier you > cannot communicate with WSJT-X 2.0 using these modes. > > We now recommend using WSJT-X 2.0 anywhere in the conventional FT8 and MSK144 > sub-bands. Everyone should upgrade to v2.0 by no later than January 1, 2019. > > NEW FEATURES IN WSJT-X 2.0 > -- > > 1. Compound and nonstandard callsigns are automatically recognized and > handled using new FT8 and MSK144 message formats. > > 2. The new FT8 protocol provides optimized message formats for North American > VHF contests, European VHF contests, ARRL Field Day, and ARRL RTTY Roundup. > Similarly, the new MSK144 protocol provides optimized message formats for > North American VHF and European VHF contests. Full support is provided for > "/R" and "/P" calls in the relevant contests. > > 3. The new protocols provide nearly equal (or better) sensitivity compared to > the old ones, and lower false decode rates. > > 4. New logging features are provided for contesting and for "Fox" > (DXpedition) mode. Logging is optionally integrated with N1MM Logger+ and > WriteLog. > > 5. Color highlighting of decoded messages provides worked-before status for > callsigns, grid locators, DXCC entities, continents, CQ Zones, and ITU zones > on a “by band” and “by mode” basis, and for stations that have uploaded their > logs to Logbook of the World (LoTW) within a specified time interval. > > 6. The WSPR decoder now achieves decodes down to S/N = -31 dB. For the > particular benefit of LF/MF users, an option "No own call decodes" has been > added. > > 7. The UDP messages sent to companion programs have been expanded and > improved. > > A more detailed list of program changes can be found in the cumulative > Release Notes: > http://physics.princeton.edu/pulsar/k1jt/Release_Notes.txt > > Upgrading from earlier versions of WSJT-X should be seamless. There is no > need to uninstall a previous version or move any files. > > Please do not continue to use any release candidate -- that is, any beta > release with "-rc#" in the version name. > > Links to installation packages for Windows, Linux, and Macintosh are > available here: > http://physics.princeton.edu/pulsar/k1jt/wsjtx.html > > You can also download the packages from our SourceForge site: > https://sourceforge.net/projects/wsjt/files/ > It may take a short time for the SourceForge site to be updated. > > We hope you will enjoy using WSJT-X Version 2.0.0. > > -- 73, Joe, K1JT, for the WSJT Development Group > > > ___ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] WSJT-X 2.0.0: GA release
Thank you. Kudos to you and you team for your expertise, and patience during the process. Thank you. Regards and 73s VE3FBZ London Amateur Radio Club www.larc.ca > On Dec 10, 2018, at 9:05 AM, Joe Taylor wrote: > > The WSJT Development Group is pleased to announce the general availability > (GA) release of WSJT-X Version 2.0.0. > > If you have been using version 1.9.1 or earlier, or one of the candidate > releases v2.0.0-rc#, it's important to upgrade now. The original protocols > for FT8 and MSK144 are no longer supported. With v1.9.1 and earlier you > cannot communicate with WSJT-X 2.0 using these modes. > > We now recommend using WSJT-X 2.0 anywhere in the conventional FT8 and MSK144 > sub-bands. Everyone should upgrade to v2.0 by no later than January 1, 2019. > > NEW FEATURES IN WSJT-X 2.0 > -- > > 1. Compound and nonstandard callsigns are automatically recognized and > handled using new FT8 and MSK144 message formats. > > 2. The new FT8 protocol provides optimized message formats for North American > VHF contests, European VHF contests, ARRL Field Day, and ARRL RTTY Roundup. > Similarly, the new MSK144 protocol provides optimized message formats for > North American VHF and European VHF contests. Full support is provided for > "/R" and "/P" calls in the relevant contests. > > 3. The new protocols provide nearly equal (or better) sensitivity compared to > the old ones, and lower false decode rates. > > 4. New logging features are provided for contesting and for "Fox" > (DXpedition) mode. Logging is optionally integrated with N1MM Logger+ and > WriteLog. > > 5. Color highlighting of decoded messages provides worked-before status for > callsigns, grid locators, DXCC entities, continents, CQ Zones, and ITU zones > on a “by band” and “by mode” basis, and for stations that have uploaded their > logs to Logbook of the World (LoTW) within a specified time interval. > > 6. The WSPR decoder now achieves decodes down to S/N = -31 dB. For the > particular benefit of LF/MF users, an option "No own call decodes" has been > added. > > 7. The UDP messages sent to companion programs have been expanded and > improved. > > A more detailed list of program changes can be found in the cumulative > Release Notes: > http://physics.princeton.edu/pulsar/k1jt/Release_Notes.txt > > Upgrading from earlier versions of WSJT-X should be seamless. There is no > need to uninstall a previous version or move any files. > > Please do not continue to use any release candidate -- that is, any beta > release with "-rc#" in the version name. > > Links to installation packages for Windows, Linux, and Macintosh are > available here: > http://physics.princeton.edu/pulsar/k1jt/wsjtx.html > > You can also download the packages from our SourceForge site: > https://sourceforge.net/projects/wsjt/files/ > It may take a short time for the SourceForge site to be updated. > > We hope you will enjoy using WSJT-X Version 2.0.0. > > -- 73, Joe, K1JT, for the WSJT Development Group > > > ___ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] WSJT-X 2.0 User Guide
On MAc Book Pro or IMacs issue print command, then in print window lower left select save as PDF. It came out as 94 pages. Also save to iBooks cloud and available on all Applebee’s devices and HP Laptop connected to your cloud. Regards and 73s VE3FBZ London Amateur Radio Club www.larc.ca > On Dec 4, 2018, at 6:24 PM, Richard Solomon wrote: > > I don't want to print it out, not yet. A simple conversion > will do. > > A Google search hasn't provided a "simple" method, yet. > > 73, Dick, W1KSZ > > Sent from Outlook > From: Ed Muns > Sent: Tuesday, December 4, 2018 4:07 PM > To: 'WSJT software development' > Subject: Re: [wsjt-devel] WSJT-X 2.0 User Guide > > If your goal with a PDF is to print, that can be done direct from the html. > And, it comes out perfectly formatted. In my Chrome browser, I simply > right-click the html manual and select ‘Print’ on the menu that comes up. > For me, it was 56 pages (28 sheets, double sided) in portrait orientation. > > If you really want a PDF file, then still use the browser print function and > direct it to a PDF create application. There are a number of freeware ones > that work fine. > > Ed W0YK > > From: Richard Solomon [mailto:w1...@outlook.com] > Sent: 04 December, 2018 14:39 > To: WSJT software development > Subject: Re: [wsjt-devel] WSJT-X 2.0 User Guide > > Any chance there is a pdf version of the Users Guide ?? > > Tnx, Dick, W1KSZ > > Sent from Outlook > From: Jim Nuytens > Sent: Tuesday, December 4, 2018 3:18 PM > To: wsjt-devel@lists.sourceforge.net > Subject: Re: [wsjt-devel] WSJT-X 2.0 User Guide > > You can lead them to the manual, but your can't make them RTFM. ;-) > > Just saying :-P > > On 12/4/2018 20:29, Joe Taylor wrote: > > Hi all, > > > > I have posted what I'm calling a "minimally acceptable" WSJT-X 2.0 > > User Guide on the WSJT web site: > > > > http://www.physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main-2.0.0.html > > > > > > > > It's what will come up in your browser when you click *Online User > > Guide" from the Help menu in RC4, RC5, or the soon-to-be posted GA > > release of WSJT-X 2.0. > > > > Like previous User Guides, tis one will continue to evolve as we make > > additions and corrections. If you find things missing or wrong, > > please let us know! > > > > -- 73, Joe, K1JT > > > --- > This email has been checked for viruses by AVG. > https://www.avg.com > > > > ___ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > ___ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] WSIT-X V2-RC3 - COLOURS in band activity - not showing non USA CQs
I notice only the USA CQ calls show the correct colours. >> Other non-USA, although new call, show white. >> If not an issue in RC4 I apologize for bringing this up. >> None of my logged CQs are shown as logged. Jtalert 2.12.7 indicates B4. >> >> Win 10 1803 WSIT-X RC3 IC-7300. 40M >> Regards and 73s >> VE3FBZ >> London Amateur Radio Club >> www.larc.ca >> >> >> ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] RC 4 testa.
I used rc3 for about 1/2 hour on several bands using 77 bit to tx and rx. I got one reply when there were hundreds on the bands. Possibly more will be on the practice today. Tuesday, November 20, 0200-0300 UTC (Monday evening, NA time Regards and 73s VE3FBZ London Amateur Radio Club www.larc.ca > On Nov 19, 2018, at 3:04 AM, dgb wrote: > > Amen > > I tried RC4 for the last hr. with CQ's on 160-30 and got many replies but not > one using RC4!! > > Apparently a very small part of the population using RC4. > > What's it going take to get them to change their ways? ;-) > > 73 Dwight NS9I > > > >> On 11/17/2018 4:01 AM, Krzysztof Krzemiński wrote: >> Ladies and gentelmen, HAMs, >> >> Where is the ham spirit? >> >> Quite nobody WW is using RC4. >> >> Let's start and run RC4, nobody will do it in your name. >> >> Even if new, super contact "do not change colour on your log". >> >> Help Joe and his team. >> >> Kris, SP5NOH >> >> >> Wysłano z TypeApp >> >> >> >> ___ >> wsjt-devel mailing list >> wsjt-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wsjt-devel > ___ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Resolved bugs wsjt-x v2.0.0-rc4 a891ad
Thanks. Like everything else, what works. I use a powered hub because my HP laptop USB power is an issue. Too much load I suspect. Anyway it works for me. Apologize that I did not include in last msg. V2-rc3 Win 10 1803 IC-7300 Long wire antenna. 43 ft vertical then runs 63 feet horizontal - west to east. MJF auto-tuner external - at base of vertical Antenna . Regards and 73s VE3FBZ London Amateur Radio Club www.larc.ca > On Nov 17, 2018, at 11:38 PM, Art Witmans wrote: > > Thank you VE3FBZ! > > You mentioned the hub and it triggered a memory of past issues with hubs. > The reason I used a hub is because the computer-end of the CAT cable for the > FT897 has the interface circuit moulded in and is therefore wider than normal > which in turn prevents the usb audio converter cable to be plugged into the > next usb port of the laptop. > > I carefully ground off enough plastic from one side of the wide plug so both > fit in the laptop. > > Result: No hub - problem gone! > > Thanks again! > Best Regards, > VE7WAE, > > Sent from ProtonMail Mobile > > >> On Sat, Nov 17, 2018 at 17:36, VE3FBZ wrote: >> Try putting a powered USB hub between. >> >> >> Regards and 73s >> VE3FBZ >> London Amateur Radio Club >> www.larc.ca >> >> >> >> >>> On Nov 17, 2018, at 6:06 PM, Art Witmans via wsjt-devel >>> wrote: >>> >>> >>> >>> >>> Sent with ProtonMail Secure Email. >>> >>> ‐‐‐ Original Message ‐‐‐ >>>> On Saturday, November 17, 2018 2:55 PM, Yahoo Groups >>>> wrote: >>>> >>>> Hello >>>> >>>> wsjt-x and js8call are really great fun to use! >>>> >>>> The problems I find is there is a frequent loss of audio link from laptop >>>> to transceiver. It goes ok for a while and than the modulation comes out >>>> the laptop speaker instead of going to the transceiver. Once this happends >>>> it will ignore the settings in the preferences. >>>> The only way to restore function is by quitting and restarting the >>>> software. >>>> FT991a has additional problem having 2 codecs and you never know which one >>>> it wants to use. If it is the "wrong" one, you have to force quitting the >>>> software because it does not quit normally. >>>> Flrig does not have this problem >>>> >>>> Same problem found in the js8call software. >>>> >>>> Laptop used: >>>> macOS Mojave 10.14.1 >>>> tranceivers used: >>>> FT-897D and FT-991A >>>> >>>> >>>> Sent with ProtonMail Secure Email. >>>> >>> ___ >>> wsjt-devel mailing list >>> wsjt-devel@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel > > ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] bugs wsjt-x v2.0.0-rc4 a891ad
Try putting a powered USB hub between. Regards and 73s VE3FBZ London Amateur Radio Club www.larc.ca > On Nov 17, 2018, at 6:06 PM, Art Witmans via wsjt-devel > wrote: > > > > > Sent with ProtonMail Secure Email. > > ‐‐‐ Original Message ‐‐‐ >> On Saturday, November 17, 2018 2:55 PM, Yahoo Groups >> wrote: >> >> Hello >> >> wsjt-x and js8call are really great fun to use! >> >> The problems I find is there is a frequent loss of audio link from laptop to >> transceiver. It goes ok for a while and than the modulation comes out the >> laptop speaker instead of going to the transceiver. Once this happends it >> will ignore the settings in the preferences. >> The only way to restore function is by quitting and restarting the software. >> FT991a has additional problem having 2 codecs and you never know which one >> it wants to use. If it is the "wrong" one, you have to force quitting the >> software because it does not quit normally. >> Flrig does not have this problem >> >> Same problem found in the js8call software. >> >> Laptop used: >> macOS Mojave 10.14.1 >> tranceivers used: >> FT-897D and FT-991A >> >> >> Sent with ProtonMail Secure Email. >> > ___ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
