[WT-support] LATCH in SSB scenarios

[Tõnno Vähk]

Jose, If I understand correctly then Latch mode is the only way to avoid listening to your monitor tone while transmitting through mic and footswitch is pressed. Without Latch activated the audio does not switch to R2R2 when I press footswitch but it will stay where it is (R1R2 or R2R2) and I have to listen to my monitor instead of being able to listen to 2nd Radio while speaking.
 
So I surely want to use scenarios but cannot avoid my monitor tone as Latch does not work in Plain Pile Up scenarios..
 
73
es5tv

________________________________

From: support-bounces at win-test.com [mailto:support-bounces at win-test.com] On Behalf Of José Nunes CT1BOH
Sent: Monday, October 09, 2006 1:34 AM
To: support at win-test.com
Subject: Re: [WT-support] LATCH in SSB scenarios


Why do you want to use the $latch variable in the scenarios? This variable sets the Latch mode (i.e. listen to secondary radio on transmit) but you should use the variables $R1R1 or $R2R2 instead.
 
I always think, latch mode still exits because it was in WT before advanced mode was developed, and ....stayed there. Actually the latch mode was the basic SO2R mode back then in the dark ages :-), and may be it needs to be there for NOT Advanced SO2R mode 
 
I guess if you don't want to configure any scenarios, then leave all the fields open and just use the latch to go over the secondary radio on transmit in the first.
 
73
José

 
On 10/8/06, Tõnno Vähk <Tonno.Vahk at gildbankers.com > wrote: 


	Trying to set the scenarios for CQWW and found that can't use $LATCH command in Plain Pile Up scenarios that end with $R1R2 because if $LATCH is anywhere in this particular command line then the audio always terminates at $R1R1 - both ears at Primary Radio. Whereever I put $LATCH it does not help. Maybe it possible to fix somehow? 
	
	73
	es5tv
	_______________________________________________
	Support mailing list
	Support at win-test.com 
	http://www.f5mzn.org/cgi-bin/mailman/listinfo/support
	


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.f5mzn.org/pipermail/support/attachments/20061009/d0ac53b9/attachment.htm