What happens when you press Ctrl-Alt-T or AltGr-T? That should put both headphones on the secondary radio. Ctrl-Alt-A or AltGr-A will put both headphones back on the primary radio. If these keys do not work, something must be wrong with the Win-Test configuration (or Win-Test didn't implement those features of the OTRSP protocol).<div>
<br></div><div>Do you have any LPT pins set for headphone control in Win-Test SETUP menu? Any COM port pins set to "Headphones Control"? If so, OTRSP headphone control may not work.</div><div><ol><li>Type SETUP [Enter] in the Win-Test logging window</li>
<li>Look for any ports that say "RX", e.g. "9600 8-N-1 RX"</li><li>If you see any ports like that, click the <b>Configure</b> button and disable Headphones Control, and press OK</li><li>Temporarily check the LPT box and press the <b>Configure </b>button</li>
<li>Make sure that <b>Headphones Control</b> (pin 4) is <i>not</i> checked</li><li>Press OK</li><li>Uncheck the LPT port if you are not using it for PTT or DVK control</li><li>Press OK again to return to the WT logging window</li>
<li>Type SCRIPTS [Enter] to see if any scripts are assigned to F1. If so, disable them.</li><li>Type DEFINEKEYS [Enter] to see if F1 was redefined there too?</li>
</ol><div>According to the manual, you can also use the $LATCH macro to enable latch mode, though perhaps it doesn't work with the OTRSP box.</div></div><div><br></div><blockquote style="margin:0 0 0 40px;border:none;padding:0px">
<div><div>F1 = $RESET $R2R2 $F1 $RESET $R1R1 $LATCH</div></div><div><div><br></div></div><div><div>When the operator pushes the F1 key, Win-Test will reset to automatic control any manual audio setting in</div></div><div>
<div>case there was one, switch the headphone to radio2 only, transmit the content of the voice keyer F1, reset to</div></div><div><div>automatic control in case any manual audio control while F1 was being sent, and switch the headphones to</div>
</div><div><div>radio1 only. The latch command sets the Latch Mode in case the operator uses the microphone during the next</div></div><div><div>moment of the QSO, and wants to listen to the secondary radio while talking on the microphone.</div>
</div></blockquote><div><br></div><div><div>If you still can't get it to work, please send me a screen shot of your Win-Test SETUP screen and the SO2R setup screens.</div><div><br></div><div>73,<div>Bob, N6TV</div><br>
<div class="gmail_quote">On Fri, Oct 26, 2012 at 8:31 AM, Bob Henderson <span dir="ltr"><<a href="mailto:bob@5b4agn.net" target="_blank">bob@5b4agn.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
It is looking that way. Verbose SO2R reports exchanges when the numeric
* key is pressed and we switch between left and right radios. When any
of the function keys are pressed any associated voice keyer message is
played but there is no audio switching and nothing whatsoever reported
on the verbose SO2R screen so there appears to be no data traffic
between WT and the SO2R+ software.<br>
<br>Mark will have to work around this through use of permanent split
audio when SO2R. It'll be painful but it seems like his only option at
this stage.<br><br>Thanks for your help. I'll get back to this after the weekend.<br>
<br>73 Bob, 5B4AGN<div><div><br><br><div class="gmail_quote">On 26 October 2012 15:01, Dennis Egan <span dir="ltr"><<a href="mailto:egan.dennis88@gmail.com" target="_blank">egan.dennis88@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Bob<br>
<br>
According to the manual, that greying out of the Latch means that the<br>
SO2R Box controller<br>
doesn't support that function. If that's the case, its doubtful<br>
anything we do will get it to work for this weekend.<br>
It sounds like something that the WinTest authors and Paul will have<br>
to get together on.<br>
<br>
Dennis W1UE<br>
<div><div><br>
On Fri, Oct 26, 2012 at 10:41 AM, Dennis Egan <<a href="mailto:egan.dennis88@gmail.com" target="_blank">egan.dennis88@gmail.com</a>> wrote:<br>
> Bob<br>
><br>
> Make sure software/firmware are current- software is 1.3, firmware is<br>
> 1.2. Update if needed. Rx switch should bein center position.<br>
><br>
> On the SO2R box software, check the "verbose so2r" box. You should<br>
> now be able to see commands as they<br>
> are sent to the box. You can make note of the commands. You can also<br>
> send the commands that work- I imagine they should be the same. Paul<br>
> K1XM can modify software/firmware if needed, but he's in 6Y right now<br>
> with limited computer access, so it won't happen before the contest,<br>
> if that is the issue.<br>
><br>
> Try turning off "Tools | Data Entry | Enable Run/S&P switching"- that<br>
> should ungrey the Latch mode on the secondary window, and try it<br>
> again.<br>
><br>
> UE<br>
><br>
><br>
><br>
><br>
> On Fri, Oct 26, 2012 at 10:16 AM, Bob Henderson <<a href="mailto:bob@5b4agn.net" target="_blank">bob@5b4agn.net</a>> wrote:<br>
>> Thanks Dennis.<br>
>><br>
>> With SO2R advanced mode set within WT the scenario buffers contain these<br>
>> macros. Unfortunately the SO2R+ box doesn't seem to want to respond to<br>
>> them.<br>
>><br>
>> Under scenario 1 the F1 box contains:<br>
>><br>
>> $RESET $R2R2 $F1 $R1R2<br>
>><br>
>> F2 box contains:<br>
>><br>
>> $R2R2 $F2 $R1R2<br>
>><br>
>> Pressing F1 plays the F1 DVR message but apparently ignores the R2R2 and<br>
>> R1R2 commands.<br>
>><br>
>> Similarly pressing F2 plays the F2 DVR message but ignores the routing<br>
>> commands.<br>
>><br>
>> Might I have an SO2R+ hardware issue?<br>
>><br>
>> 73 Bob<br>
>><br>
>><br>
>> On 26 October 2012 13:49, Dennis Egan <<a href="mailto:egan.dennis88@gmail.com" target="_blank">egan.dennis88@gmail.com</a>> wrote:<br>
>>><br>
>>> Bob<br>
>>><br>
>>> 2nd option- In some of the Wintest documentation, they actually showed<br>
>>> how to use macros<br>
>>> to emulate a LATCH situation- I ifted this from that.<br>
>>> Setting up scenarios<br>
>>><br>
>>> A standard F1 message contains only the content of what is sent, i.e.<br>
>>> F1 = TEST CT3NT. When using Advanced SO2R mode the F1 message will<br>
>>> have the content plus the scenario to control audio and transmitting.<br>
>>> Imagine the following scenario:<br>
>>> F1 = $R2R2 $F1 $R1R2<br>
>>> This simple scenario will do the following. When the operator pushes<br>
>>> the F1 key, Win-Test will switch the headphones to radio2 only<br>
>>> ($R2R2), transmit the content of standard F1 message (TEST CT3NT) and<br>
>>> when that is over will switch the headphones to left ear on radio1 and<br>
>>> right ear on radio2 ($R1R2).<br>
>>> $R2R2 $F1 set up the audio headphone settings and transmission in<br>
>>> moment 1 of the QSO<br>
>>> $R1R2 sets the audio headphone settings for moment 2 of the QSO<br>
>>><br>
>>> I realize it may not be exactly what you are looking for, but it might<br>
>>> work for you.<br>
>>><br>
>>> GL<br>
>>><br>
>>> UE<br>
>>><br>
>>> On Fri, Oct 26, 2012 at 9:41 AM, Bob Henderson <<a href="mailto:bob@5b4agn.net" target="_blank">bob@5b4agn.net</a>> wrote:<br>
>>> > Dennis<br>
>>> ><br>
>>> > Many thanks but checking the LATCH box in the SO2R program makes no<br>
>>> > difference to audio routing. LATCH box in the WT Secondary Radio window<br>
>>> > is<br>
>>> > permanently greyed out. I don't know whether that's significant.<br>
>>> ><br>
>>> ><br>
>>> > 73 Bob, 5B4AGN<br>
>>> ><br>
>>> ><br>
>>> > Bob<br>
>>> ><br>
>>> > In the SO2R Box program, there is a box called "LATCH". Check that<br>
>>> > and you should get the<br>
>>> > functionality you seek.<br>
>>> ><br>
>>> > Dennis W1UE<br>
>>> ></div></div></blockquote></div></div></div></blockquote></div></div></div>