<div>Hi Andy</div>
<div> </div>
<div>A couple of answers:<br><br></div>
<div class="gmail_quote">2008/4/8 Andy Cook, G4PIQ <<a href="mailto:g4piq@btinternet.com">g4piq@btinternet.com</a>>:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div>
<div><span><font face="Arial" size="2">I ran my second serious contest with Win-Test as M6T SOAB during WPX SSB. I had SO2R better configured this time but I still ran across a few problems. </font></span></div>
<div><span><font face="Arial" size="2"></font></span> </div>
<div><span><font face="Arial" size="2">1. There were occasions where pressing any of the DVP keys would put the active radio into transmit, but would connect the microphone rather than play the DVP message. I think this was usually after aborting a DVP message on the second radio (e.g. via shift F4 and pressing Esc before the message completed). Needed to restart Win-Test to get everything working again. Probably happened about 20 times during 36 hours operating. </font></span></div>
<div><span><font face="Arial" size="2"></font></span> </div>
<div><span><font face="Arial" size="2">2. Sometimes the outgoing DVP messages would become chopped-up as if another process was getting CPU time priority. Again - needed a restart. Happened about 10 times during 36 hours operating.</font></span></div>
<div><span><font face="Arial" size="2"></font></span> </div>
<div><span><font face="Arial" size="2">3. When running alternating CQs in SO2R mode (using the default macro), when it came to answer a caller (so using the microphone, not sending a DVP message) sometimes the PTT and microphone line would be directed to the wrong radio. I think I cleared this with a couple of presses of the * key and then sending a DVP message. Only happened about 5 times, but I didn't use alternating CQs very much (< 1 hour). </font></span></div>
<div><span><font face="Arial" size="2"></font></span> </div>
<div><span><font face="Arial" size="2">4. I couldn't see how to configure Latch mode. I only had 2 COM ports on the PC and those were being taken up by the radios. I tried (briefly) configuring various other fake SO2R controllers on one of those COM ports as a test, but still couldn't get Latch mode to work. So my technique for working someone on the second radio was a rather clunky, SHIFT-F4, *, enter callsign, send report, hit enter, *.</font></span></div>
<div><span><font face="Arial" size="2"></font></span> </div>
<div><span><font face="Arial" size="2">Then I have three feature requests. These fall into the category of - can we make Win-Test behave more like TR Log - for which I apologise. I used TR for a long time and it really does have a very slick SO2R interface - but equally, I'm happy to be told that I'm just not using Win-Test right though!</font></span></div>
<div><span><font face="Arial" size="2"></font></span> </div>
<div><span><font face="Arial" size="2">1. When in alternating CQ mode, as soon as you start to enter a callsign, drop the CQ on the second radio and return PTT and microphone to the radio where the caller is. Currently Win-Test seems to wait until the end of the DVP message to do this (or at least doesn't abort quickly enough with Esc) and I was left with a lot of awkward pauses. </font></span></div>
</div></blockquote>
<div> </div>
<div>I wrote the specs with F5MZN for SO2R in WT.</div>
<div>When you start typing something on the callsign field, the CQ is not supposed to be dropped on the other radio as you ask.</div>
<div>The CQ must go on the other radio until you start transmitting (hit INSERT ON CW) what you just typed. Only when you start transmitting the CQ ahould be dropped.</div>
<div>This was the request and this is the way it should be to have the maximum efficiency in SO2R Alternate Mode!</div>
<div> </div>
<div> </div>
<div> </div>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div>
<div><span><font face="Arial" size="2"><span id=""></span></font></span></div>
<div><span><font face="Arial" size="2"></font></span> </div>
<div><span><font face="Arial" size="2">2. Strangely, I find having to either toggle CAPS LOCK on or off, or hold the SHIFT key down to enter a callsign in the 2nd radio window awkward (especially when your fingers are frozen!), and more so having to hit SHIFT-F11 to clear the window if it's a dupe, or SHIFT-CTRL-ENTER to clear it and put it into the bandmap. Is there any config which makes this as simple as TR's ALT-D, enter Callsign, ENTER to do a DUPE check, MULT check, band map enter and if not a dupe line up ready to call with just the SPACE bar. </font></span></div>
</div></blockquote>
<div> </div>
<div>Ther are two things here</div>
<div> </div>
<div>1- is how to access the call sign fields of each radio</div>
<div>2- is how to act on calls that are on the callsign fields</div>
<div> </div>
<div>The CAPS LOCK / SHIFT KEY is there because there is only one keyboard (just like Alt-D on TR). With this functionality you can still type calls on the two callsign fileds (radio1 or radio2 callsign fields) particularly if you are using the SHIFT key.</div>
<div>NO SHIFT- what you type goes to primary radio</div>
<div>SHIFT ON - what you type goes to secondary radio. </div>
<div>With this way of doing things you can alternate calls on the two fields very easily. I do this a lot when in intense SO2R.</div>
<div>WIth TR once you hit ALT-D you are locked into that field. To get out of ALT-D you need to hit ESC. So if you are using WT, and Shift key, you don't need to use the ESC key, one less key to push.</div>
<div> </div>
<div>Now you have calls in the callsign fields of each radio.</div>
<div> </div>
<div>With TR you are locked in the ALT-D filed and you can only act on the "secondary radio" hitting space to start transmitting.</div>
<div>With WT you have one more option. You can start transmitting on primary radio (INSERT) or on secondary radio (SHIFT+INSERT)</div>
<div> </div>
<div>In conlcusion, WT behaviour was designed to be one step ahead in this functionality, in situations where more intense SO2R require full control of both radios.</div>
<div> </div>
<div> </div>
<div> </div>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div>
<div><span><font face="Arial" size="2"><span id=""></span></font></span></div>
<div><span><font face="Arial" size="2"></font></span> </div>
<div><span><font face="Arial" size="2">3. Aborting CQs with Esc isn't instant - it takes a few hundred ms which means a few more lost characters when you realise that someone was just starting to call you as you hit F1 or the auto CQ went off. </font></span></div>
<div><span><font face="Arial" size="2"></font></span> </div>
<div><span><font face="Arial" size="2">Configuration was P4 1.6 GHz, 1 Gb RAM, Win XP Pro SP2, Homebrew SO2R controller from LPT port.</font></span></div>
<div><span><font face="Arial" size="2"></font></span> </div>
<div><span><font face="Arial" size="2">If anyone can shed any light on any of these problems (do others see them as well), that would be really helpful. I've made the switch to Win-Test now (reconfigured my SO2R controller!) - just need to get it working 100%.</font></span></div>
<div><span><font face="Arial" size="2"></font></span> </div>
<div><span><font face="Arial" size="2">73,</font></span></div>
<div><span><font face="Arial" size="2"></font></span> </div><font color="#888888">
<div><span><font face="Arial" size="2">Andy, G4PIQ</font></span></div></font></div><br>_______________________________________________<br>Support mailing list<br><a href="mailto:Support@win-test.com">Support@win-test.com</a><br>
<a href="http://www.f5mzn.org/cgi-bin/mailman/listinfo/support" target="_blank">http://www.f5mzn.org/cgi-bin/mailman/listinfo/support</a><br><br></blockquote></div><br><br clear="all"><br>-- <br>-- <br>José Nunes<br>CONTEST CT1BOH - <a href="http://www.qsl.net/ct1boh">http://www.qsl.net/ct1boh</a>