# Station ID trigger

**URL:** <https://community.allstarlink.org/t/station-id-trigger/19637>\
**Category:** AllStarLink\
**Tags:** nnx-tips\
**Created:** [October 13, 2022, 1:43pm UTC](https://community.allstarlink.org/t/station-id-trigger/19637 "2022-10-13T13:43:34Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![KP3DF](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/k/b5ac83/32.png) [@KP3DF](https://community.allstarlink.org/u/KP3DF)\
**Post date:** [October 13, 2022, 1:43pm UTC](https://community.allstarlink.org/t/station-id-trigger/19637/1 "2022-10-13T13:43:35Z")

</div>

I have three remote base radios operating in simplex mode on 6, 2 and 70cm bands. I’m trying to figure out if there’s a way to trigger the base radio ID only when there’s a key up through the IP side and NOT through COR activity on the donor radio.

The problem I want to solve is stay in compliance with ID requirements but at the same time NOT bother stations operating in the base radio frequency (simplex) by triggering the station ID when it detects activity in the RF channel.

So far, the way to do this is to suppress the ID all together and do it manually.

Any suggestions will be appreciated.  
73’s

---

<div class="post-metadata">

**Author:** ![WD6AWP](https://community.allstarlink.org/user_avatar/community.allstarlink.org/wd6awp/32/5_2.png) [@WD6AWP](https://community.allstarlink.org/u/WD6AWP)\
**Post date:** [October 13, 2022, 2:16pm UTC](https://community.allstarlink.org/t/station-id-trigger/19637/2 "2022-10-13T14:16:47Z")

</div>

It’s not possible to modify the behavior of the IDer. I think the IDer is triggered on PTT activity rather than COR and would require changing the app\_rpt C to modify. However, it might be possible to use events [Event Management - AllStarLink Wiki](https://wiki.allstarlink.org/wiki/Event_Management) to trigger an ID script.

---

<div class="post-metadata">

**Author:** ![KP3DF](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/k/b5ac83/32.png) [@KP3DF](https://community.allstarlink.org/u/KP3DF)\
**Post date:** [October 13, 2022, 3:52pm UTC](https://community.allstarlink.org/t/station-id-trigger/19637/3 "2022-10-13T15:52:22Z")

</div>

Good point. Then I will try the following

duplex=1  
idrecording=|iDE KP3DF/L  
nounkeyct=1  
beaconing=0

That should prevent any TX if the COR activates in the remote base.

setting “nounkeyct=0” which is the default, will trigger the TX if any RX activity is noticed on the remote base receiver.

---

<div class="post-metadata">

**Author:** ![WD6AWP](https://community.allstarlink.org/user_avatar/community.allstarlink.org/wd6awp/32/5_2.png) [@WD6AWP](https://community.allstarlink.org/u/WD6AWP)\
**Post date:** [October 13, 2022, 4:03pm UTC](https://community.allstarlink.org/t/station-id-trigger/19637/4 "2022-10-13T16:03:13Z")

</div>

Maybe I missed what you want to prevent. Remote base nodes do not send an ID on the remote freq, only on the talk back. Are these nodes configured as remotes?

See:  
[https://wiki.allstarlink.org/wiki/Standard\_Node\_vs\_Remote\_Base](https://wiki.allstarlink.org/wiki/Standard_Node_vs_Remote_Base)  
[https://wiki.allstarlink.org/wiki/Remote\_Base](https://wiki.allstarlink.org/wiki/Remote_Base)  
[https://wiki.allstarlink.org/wiki/Remote\_Base:\_Doug\_Hall\_RBI-1](https://wiki.allstarlink.org/wiki/Remote_Base:_Doug_Hall_RBI-1)