<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>On 01/22/2014 11:13 AM, Tim Sawyer
wrote:<br>
</div>
<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>
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<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>
[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 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>