[arm-allstar] Problem with ID on simplex link

pjg pjg123 at comcast.net
Tue Oct 14 22:39:44 EST 2014


Mike,

This all started because a good friend and club member was spending 6 
months a year in Ireland.  So I do need to ID the link when he is on it. 
But the node keeps sendeing an ID even when the transmitter has not been 
active. (Under conditions described below.)

Paul


On 10/14/2014 8:46 PM, W5JR.Mike wrote:
> Paul, are you the only user and from the IP side? Or any others using 
> this as a remotely controlled station? If so, I don't believe you need 
> any additional ID'ing other than what you normally would as if you 
> were local to the radio using an attached microphone. This would even 
> be true when using a simplex frequency to talk to others. You 
> adequately identify the station during a conversation and at the end 
> of your conversation. When just listening to the repeater or a simplex 
> frequency (such as 146.490), no ID on the radio is required, needed or 
> desired, same as if you were in the shack with the radio.
>
> Now, if others are going to command the radio to transmit from the RF 
> side (like a repeater user), an ID from the radio is necessary.
>
> tnx
> Mike / W5JR
>
> On Oct 14, 2014, at 8:01 PM, Joel Jameson <w0kgw3 at gmail.com 
> <mailto:w0kgw3 at gmail.com>> wrote:
>
>> I've set my node up like this (11111 is your node number) so every 20 
>> minutes it sends out an ID and the time if there's no usage, but the 
>> normal 10 minute CW ID is sent out as well:
>> [schedule11111]
>> ;dtmf_function =  m h dom mon dow  ; ala cron, star is implied
>> 1=00 * * * *   ;run macro 1 on the hour
>> 1=20 * * * *   ;run macro x:20 on the hour
>> 1=40 * * * *   ;run macro x:40 on the hour
>>
>> [macro11111]
>> ;Macro number = command string (ea command separated by space) -end 
>> with HASH
>> 1=*81 *80#    ; play time and voice ID
>>
>>
>>
>> Cheers,
>> Joel
>> W0KGW
>>
>> On Tue, Oct 14, 2014 at 5:50 PM, Paul <pjg123 at comcast.net 
>> <mailto:pjg123 at comcast.net>> wrote:
>>
>>     Hi all,
>>
>>     I am playing with the BBB.  I am running a simplex node, the
>>     output transmit on the input of the local repeater and listens on
>>     the repeater output.  I dial in using Zoiper on an old smart
>>     phone or iaxRpt on my laptop to access the repeater.
>>
>>     The following condition accrued with all the default settings
>>     except */nounkeyct/* was changed from zero to one to stop
>>     courtesy tones. And stop the transmitter from keying every time
>>     it sees a signal:
>>
>>
>>     When first powered up, or if there is a power hit, or if
>>     astres.sh is executed, the node will key up and send an ID even
>>     if no one is connected to the node.If there is traffic on the
>>     frequency and the COR is operated within the ID period, the node
>>     will continue to send an ID every ten minutes as long as there is
>>     activity on the frequency.
>>
>>     If 10 minutes elapses with no receive activity, (no COR activity
>>     on the freq), the node will stop sending the ID even if a signal
>>     is received again after that period.
>>
>>     When someone is connected to the node, the ID works correctly and
>>     sends an ID every 10 minutes.  But again, after the user
>>     disconnects from the node, if the BBB node receives an
>>     over-the-air signal from the repeater after the last ID, The BBB
>>     node will continue to key up and send an ID every 10 minutes as
>>     long as there is activity on the repeater.
>>
>>     This will continue as long as the repeater is busy. When the
>>     repeater is no longer in use and there is 10 minutes of silence,
>>     then the BBB will stop sending the ID even if the repeater keys
>>     up again after the 10 minutes of silence.
>>
>>     If I key the BBB node and give my call, and no one answers in the
>>     next 10 minutes, The BBB node will act correctly and not send the
>>     ID again.It is only when it sees incoming traffic within the ID
>>     period that it will keep keying up and sending the ID.
>>
>>     I hope that was clear,
>>
>>     Paul
>>     WB8TFV
>>
>>     BTW the above scenario also happens if the node is operating on a
>>     simplex frequency instead of a repeater frequency.
>>
>>
>>     _______________________________________________
>>
>>     arm-allstar mailing list
>>     arm-allstar at hamvoip.org <mailto:arm-allstar at hamvoip.org>
>>     http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>>
>>     Visit the BBB web page -
>>     http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/
>>
>>
>> _______________________________________________
>>
>> arm-allstar mailing list
>> arm-allstar at hamvoip.org <mailto:arm-allstar at hamvoip.org>
>> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>>
>> Visit the BBB web page - 
>> http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/
>
>
> _______________________________________________
>
> arm-allstar mailing list
> arm-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
> Visit the BBB web page - http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20141014/a727d366/attachment-0001.html>


More information about the arm-allstar mailing list