Jed,

There are at least three ways this can be accomplished.?

1 - Use a RIM-SCOM 7330.? This interface simply plugs into a free controller port and adds ASL.? This allows the group to keep the conventional repeater controller and simply adds ASL as a link.

2 - This and the choice below would remove the conventional repeater controller and use ASL instead - by itself.? If using the simpleusb channel driver - set-up a GPIO to follow COS and use that to gate a CTCSS encoder.? ASL can't (on its own) generate a CTCSS tone using the simpleusb channel driver, but logic can be generated to turn a CTCSS encoder on and off.? This function is commonly called and might not be a valid choice in ASL3, but is with HamVoIP.

3 - Use the in ASL3 and use either "composite" or the second TX audio channel to generate the CTCSS tone.? If you're going to feed the TD (modulator) input of the TKR with voice audio that has been pre-emphasized and limited in software, program ASL so its encoder follows COS and use the composite setting.? If you're going to use the TA audio input for voice audio, then use the second channel of the radio interface to only generate the CTCSS tone and apply it (by itself) to the TD input.? I always recommend using discriminator audio from the receiver to feed the input of the radio interface - obviously setting ASL to de-emphasize the receive audio.? TKR's and NXR's are a little numb and require a good bit of TX audio.? I recommend an amplified radio interface like a Repeater Builder RIM (the full blown RIM not a RIM Lite) or a RA-40M or RA-42M from yours truly.

The fourth possibility is to NOT use any of ASL to generate PL on COS.? Simply use COS logic to gate a CTCSS encoder.? This would not necessarily be changeable - but if the group always has PL encode that follows COS, that's of no concern.

Kevin W3KKC


On 3/1/2025 7:21 PM, Jed Barton (N1JBC) via groups.io wrote: