<div dir="ltr">Hey there,<div><br></div><div>Matt here, just commenting on your closing comment ( sorry you didn't mention your name ) about the Morse ID's etc. </div><div><br></div><div>I just wanted to share with you an idea I had a while ago and it seems to work really well in practice so maybe some of you out there in Allstar land would like to copy this.</div>
<div><br></div><div>On my node, I have two completely separate RPT.CONF files, one is called rptconn.conf and the other rptdis.conf.</div><div><br></div><div>I have two simple bash scripts that gets called by the "connectprog=" and "disconnprog=" statements in rpt,conf. </div>
<div><br></div><div>The function of the connectprog script is to rename rptconn.conf as rpt.conf and then execute the rpt reload command on the node, thereby making it effective. </div><div><br></div><div>Similarly the function of the disconnprog script is to rename the rptdis.conf file as rpt.conf and then rpt reload.</div>
<div><br></div><div>What all this means is that I can have two completely different behaviors for my node depending upon whether it is connected to another node or not. </div><div><br></div><div>When it is not connected to another node, I have a long list of tail messages, time announcements on the quarter hour and voice ID's that play out.</div>
<div><br></div><div>When it is connected ( i.e. in use ) then the other rpt.conf file suppresses all the time announcements, tail messages and other stuff and just has CW ID's and thats it.</div><div><br></div><div>I thought it was quite an elegant solution, perhaps done in a strange way but it seems to work really well.</div>
<div><br></div><div>Hopefully someone will come up with an improvement on my (nasty) method but it just goes to show another aspect of the wonderfully versatile Allstar system!</div><div><br></div><div>Cheers,</div><div>Matt., G4RKY </div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On 4 March 2014 15:16, ARS W5OMR <span dir="ltr"><<a href="mailto:ars.w5omr@gmail.com" target="_blank">ars.w5omr@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<div text="#000000" bgcolor="#FFFFFF">
Sorry for the l-o-n-g delay... found this in my 'Drafts' folder. Maybe my phone rang, or the door-bell rang - don't know why I didn't finish it, but it's pertinent to discussion of app_rpt<br></div>
<div text="#000000" bgcolor="#FFFFFF">-Geoff<br><br><br></div><div text="#000000" bgcolor="#FFFFFF"><div class="">
<div>On 01/22/2014 11:13 AM, Tim Sawyer
wrote:<br>
</div>
</div><div class=""><blockquote type="cite">
<pre>Good point. And the telemetry stanza comments say:
; Telemetry entries can be shared across all repeaters, or defined for each repeater.
So I’d say you CANNOT have separate morse stanzas.
</pre>
</blockquote>
<br></div>
Well... kinda...<br>
<br>
Technically, yes - only one morse stanza can be defined, but
different ID strings can be entered for each node.<br>
<br>
What's funny is, (it's really comical) my node 29657 (2m simplex node)
is the *3rd* node defined in rpt.conf.<br>
If I key up the simplex node *first*, upon an asterisk re-start, then
the morse stanza for 29657 is used through out rpt.conf.<br>
<br>
Meaning<div class=""><br>
[morse29655]<br>
speed=20 ; Approximate speed in WPM<br>
frequency=500 ; Morse Telemetry Frequency<br>
amplitude=2048 ; Morse Telemetry Amplitude<br>
idfrequency=1000 ; Morse ID Frequency <br>
idamplitude=2048 ; Morse ID Amplitude<br>
<br></div><div class="">
[morse29657]<br>
speed=20 ; Approximate speed in WPM<br>
frequency=1000 ; Morse Telemetry Frequency<br>
amplitude=2048 ; Morse Telemetry Amplitude<br>
idfrequency=500 ; Morse ID Frequency <br>
idamplitude=2048 ; Morse ID Amplitude<br><br></div></div><div text="#000000" bgcolor="#FFFFFF">If I key up the 2m simplex node, the freqency of the ID is low, and enjoyable. If the repeater is keyed first, there's a 1k tone used for the ID. (I'm old school - not that 'up' on voice ID's) CW doesn't bother the on-going conversation like a voice-id does.<br>
<br><br>
</div>
</div>
<br>_______________________________________________<br>
App_rpt-users mailing list<br>
<a href="mailto:App_rpt-users@ohnosec.org">App_rpt-users@ohnosec.org</a><br>
<a href="http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users" target="_blank">http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users</a><br>
<br>
To unsubscribe from this list please visit <a href="http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users" target="_blank">http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users</a> and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"<br>
You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem. <br></blockquote></div><br></div>