Bill - good points, all. I wasn't advocating a situation where the response to CQ is fully automated (robo-operator), but rather where (for example), I see G4WJS working a station and realize I want to work you. I know you're about finished with the previous QSO, so put my cursor on your DF and select "Auto call to CQ/73" (or whatever we call it). Once the program decodes a TX5 or TX6 with G4WJS as calling station, it sets TX1 and Enable Tx. So, it's still me initiating the call, but the timing element is eliminated. It's the same auto sequence in theory, but allows us to start the process one step back, given the stringent timing requirements for FT8.
I must say that while my early use of the mode has me liking it, at least half of the QSOs I've completed have an extra 30 seconds added to them because I or the other station was a little slow to respond to the first CQ and had to repeat the call. While K1JT has indicated that a partial decode in excess of 50% of the period can theoretically be decoded, I am finding (with very small N so far) that a late start is usually not decded. Given the goal of taking advantage of short-duration openings, seems like saving 30 seconds could be make-or-break on VHF Es. In any case, I'm excited to see how the mode works out when there's a freely available version and we get a decent Es opening on 6 M. 73, Eric NC6K -----Original Message----- From: Bill Somerville [mailto:[email protected]] Sent: Sunday, July 9, 2017 9:27 AM To: [email protected] Subject: Re: [wsjt-devel] FT8 Issue On 09/07/2017 17:16, Eric Gruff wrote: > My suggestion was to enable a check box that auto sequences a call (HISCALL MYCALL MYGRID) on the cursor frequency only if a CQ (TX6) is selected. That way, you can park on his DF, and when he sends CQ, you will automatically call him. I suppose we can get fancy and allow selection of any CQ (including CQ DX) or just the standard one. It would also be nice to have a check box that only calls another station after he sends 73- this would be for when you want to work someone that is already in a QSO. If set up this way, you won't QRM an ongoing QSO. Hi Eric, the model WSJT-X has always adhered to is that the user must initiate QSOs and take action to progress QSOs. When fast modes were added it became apparent that auto sequencing once a QSO has started was desirable, so the requirement for user action to progress a QSO was relaxed. Imagine the problems some are suffering with a 15s T/R period mode magnified when using 5s T/R periods in MSK144 or JT9(Fast). Although FT8 is technically a slow mode (message is not repeated during a transmission), the 15s T/R periods make auto sequencing equally necessary. So I would be surprised if further QSO automation were to be accepted by the development team. I'm sure that Laurie VK3AMA or some other enterprising developer will solve the problem of picking which caller to respond to by scanning your station log using some user defined rules to pick the best candidates in a fraction of a second after decodes occur. Even with JTAlert Laurie follows our lead in that you must start each QSO yourself by clicking a button. You should have the final word on when you call someone. 73 Bill G4WJS. ---------------------------------------------------------------------------- -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
