Bill Somerville <g4wjs@...> writes: > > On 03/03/2015 09:21, Paul DU2/WA8UGN wrote: > > Bill Somerville <g4wjs <at> ...> writes: > > > >> Hi All, > >> > > Hi Bill > Hi Paul,
Hi again, Bill - > > > >> OK, take 2:- here's a new test version: > >> > >> https://dl.dropboxusercontent.com/u/4192709/wsjtx-1.4.0-rc3-win32- r4996- > > genmsg.exe > >> I would like some testing by someone with a type 1 compound call and > >> especially by someone with a type 2 compound call. If you can work each > >> other; better still ;) > >> > >> This includes much better decode highlighting, processing and logging > >> for those with compound call signs. > >> > >> (snip, snip) > >> > >> As before testing, comments and, suggestions most welcome. > >> > > Sorry, but I got as far as making unsuccessful calls to 5 different > > stations calling CQ (average dB -9) before I killed this version and > > reverted back to another that I'm testing (r4978). > > > > Sending out DE DU2/WA8UGN PK08 had the same effect on all five. > > > > They obviously thought that they were calling CQ on an occupied frequency > > and politely QSY'ed away from me. Attempts to follow one station resulted > > in a wild goose chase up and down the band, where "gentlemanly courtesy" > > won out every time over the "persistent DX-Chaser." > OK, that is a really useful data point. Thanks for trying it out. > > > > So, it's thanks, but no thanks from the Philippines, Bill. I'll stick with > > chasing CQ's with the old XXXXXX WA8UGN PK08, have my 4-5 minutes > > of QSO glory, then sign DE DU2/WA8UGN until something better comes > > along. > OK, frankly I am not too surprised but I was keen to try and improve the > likelihood of correct logging by your QSO partners but that is > completely pointless if you can't even start the QSOs :( > > What are your feelings about the original proposal given that sending a > second message (when replying to a CQ) like: > > DE DU2/WA8UGN R-10 > > will not automatically capture the -10 report in your QSO partners log? > > As discussed above I will change WSJT-X to capture that information but > existing versions do not do so. I don't know the position with with the > various JT65-HF versions. > I've had a bit of time to think it over, and do a little more testing, but it seems as if the more that (what I believe to be surefire) improvements are tried, the more confusion it causes on the airwaves. Case in point: Last tests were plagued with QSO partners who relied more on the Free Msg generator than on the "canned" messages to respond to my call sign. To top it off, calling CQ DU2/WA8UGN PK08 netted me one poor soul whose call sign I only partly received because he'd send his call via Free msg and would end up on my screen as DU2/WA8UGN JH . To help fend this off, I have a macro that sends USE ID WA8UGN which seems to work. > > > >> 73 > >> Bill > >> G4WJS. > >> > > Best 73, > > Paul DU2/WA8UGN > 73 > Bill > G4WJS. > > Again, best 73 from the islands Paul DU2/WA8UGN ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
