On 03/03/2015 17:22, Paul DU2/WA8UGN wrote: > Hi again, Bill - Hi Paul, > 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. Agreed, this is tricky because the behaviour of operators alongside what is common practise plus a mistaken perceived need to tell you your own callsign all interplay. > > 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. Well my aim is to try and make the standard generated messages work for everyone, that way it might become more likely that operators will only diverge from them for 73 type messages. It is unfortunate that WSJT-X currently doesn't extract the received report from a message that doesn't contain the DE callsign otherwise a message 3 like:
DE DU2/WA8UGN R-10 would be an excellent solution to this issue. Also in my tester sample of you and John TI4/N0URE (which is far too small a sample to make decisions with) I have 100% variance with you requiring message 1 as '<dx-call> WA8UGN PK08' and him requiring message 1 as 'DE TI4/N0URE EK70' and both being able to work that way. You both have a couple of free text messages for those situations where you need to send some extra guidance. Anyway, rather than force the situation, I have prepared a version that has a setting option to control the way the standard messages are generated for type 2 compound callsign holders. You can choose between having your full call in message 1 or message 3 or neither. Message 6 and 5 still continue to have your full callsign. Here it is: https://dl.dropboxusercontent.com/u/4192709/wsjtx-1.4.0-rc3-win32-r4996-genmsg.exe there are other changes that should also help you like highlighting and processing messages with either your full call or base call in. The same applies to compound DX calls that you work. > Again, best 73 from the islands > Paul DU2/WA8UGN 73 Bill G4WJS. ------------------------------------------------------------------------------ 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 wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
