
A-1
RLC-4 V1.79 Copyright © 1998 Link Communications Inc. 9/18/98
Appendix A: The Audio Routing Variable System
Explanation of the System
The key to controlling messages on the RLC-4 is understanding what the audio routing variable
needs to be in each different situation. Fortunately, the RLC-4 does most of the work for you.
When any command is executed by the user (either by DTMF or the serial port) or by the controller
itself (to send an ID, courtesy beep, etc.), the audio routing variable is automatically set to send the
audio to the logical place. You only need to concern yourself with this information if you wish to
change the way the audio is routed. The value of the audio routing variable in several situations is
listed below:
•
When a command is executed by DTMF, the audio routing variable is set to send all of the
responses to the port that the DTMF input came from.
•
Before a time out, time out clear, or any ID macro is executed, the audio routing variable is
set to send the message to the relevant port.
•
Before a courtesy beep is sent, the audio routing variable is set to send the beeps to the right
ports (repeater ports connected to the receiver that just unkeyed).
You probably noticed in the list above that the audio routing variable automatically sends the audio
where you would normally want it to go. The only reason you need to know about it is because
there a few situations where the controller can not know where you want the audio to go.
There are two ways for you to specify where messages go. First, choose where you want most of
the messages to go. Tell the controller what ports those are with Command 050. Now all of the
messages will go out those ports. What if you want one of the messages to go somewhere else?
Simply make the event that is causing a message call a user macro and program the first command
in the macro to be Command 037 D or unkey and list the ports where you want the message to go
to. This will change the audio routing variable for the rest of the commands in the macro.
Command 037 can be used to change where the messages generated by any macro will go. All
commands executed after Command 037 in a macro until the end of that macro will go to the ports
specified with Command 037.
A similar situation exists for commands entered from the serial port. Since the controller sends
serial responses to the commands that you execute, you don't have to worry about CW responses if
you don't want to. There are times, however, when you want to hear the CW messages that are
generated. You can use Command 050 to specify which ports get the audio that is caused by the
serial port. The RLC-4 defaults to sending these messages out of port one, but you can send them
to any ports you want to, or to no ports at all.
Suppressing Command Responses in Macros:
There is one other time when you will often want to change the audio routing variable. Suppose
that you have programmed macro 168 to connect ports 2 and 3 to the main repeater on port 1.
Summary of Contents for RLC-4
Page 2: ...RLC 4 V1 79 Copyright 1998 Link Communications Inc 9 18 98...
Page 4: ...RLC 4 V1 79 Copyright 1998 Link Communications Inc 9 18 98...
Page 14: ...RLC 4 V1 79 Copyright 1998 Link Communications Inc 9 18 98...
Page 18: ...RLC 4 V1 79 Copyright 1998 Link Communications Inc 9 18 98...
Page 52: ...2 14 RLC 4 V1 79 Copyright 1998 Link Communications Inc 9 18 98...
Page 80: ...5 12 RLC 4 V1 79 Copyright 1998 Link Communications Inc 9 18 98...
Page 96: ...6 16 RLC 4 V1 79 Copyright 1998 Link Communications Inc 9 18 98...
Page 110: ...8 10 RLC 4 V1 79 Copyright 1998 Link Communications Inc 9 18 98...
Page 116: ...9 6 RLC 4 V1 79 Copyright 1998 Link Communications Inc 9 18 98...
Page 117: ...10 1 RLC 4 V1 79 Copyright 1998 Link Communications Inc 9 18 98 Chapter 10 Not Currently Used...
Page 118: ...10 2 RLC 4 V1 79 Copyright 1998 Link Communications Inc 9 18 98...
Page 122: ...11 4 RLC 4 V1 79 Copyright 1998 Link Communications Inc 9 18 98...
Page 139: ...12 17 RLC 4 V1 79 Copyright 1998 Link Communications Inc 9 18 98...
Page 142: ...12 20 RLC 4 V1 79 Copyright 1998 Link Communications Inc 9 18 98...
Page 160: ...13 18 RLC 4 V1 79 Copyright 1998 Link Communications Inc 9 18 98...
Page 175: ...15 1 RLC 4 V1 79 Copyright 1998 Link Communications Inc 9 18 98 Chapter 15 Not Currently Used...
Page 176: ...15 2 RLC 4 V1 79 Copyright 1998 Link Communications Inc 9 18 98...
Page 182: ...16 6 RLC 4 V1 79 Copyright 1998 Link Communications Inc 9 18 98...
Page 190: ...17 8 RLC 4 V1 79 Copyright 1998 Link Communications Inc 9 18 98...
Page 191: ...18 1 RLC 4 V1 79 Copyright 1998 Link Communications Inc 9 18 98 Chapter 18 Not Currently Used...
Page 192: ...18 2 RLC 4 V1 79 Copyright 1998 Link Communications Inc 9 18 98...
Page 193: ...19 1 RLC 4 V1 79 Copyright 1998 Link Communications Inc 9 18 98 Chapter 19 Not Currently Used...
Page 194: ...19 2 RLC 4 V1 79 Copyright 1998 Link Communications Inc 9 18 98...
Page 201: ...B 1 RLC 4 V1 79 Copyright 1998 Link Communications Inc 9 18 98 Appendix B Not Currently Used...
Page 202: ...B 2 RLC 4 V1 79 Copyright 1998 Link Communications Inc 9 18 98...
Page 204: ...C 2 RLC 4 V1 79 Copyright 1998 Link Communications Inc 9 18 98...
Page 206: ...D 2 RLC 4 V1 79 Copyright 1998 Link Communications Inc 9 18 98...
Page 210: ...E 4 RLC 4 V1 79 Copyright 1998 Link Communications Inc 9 18 98...
Page 216: ...G 2 RLC 4 V1 79 Copyright 1998 Link Communications Inc 9 18 98...
Page 218: ...H 2 RLC 4 V1 79 Copyright 1998 Link Communications Inc 9 18 98...
Page 220: ...I 2 RLC 4 V1 79 Copyright 1998 Link Communications Inc 9 18 98...
Page 222: ...I 4 RLC 4 V1 79 Copyright 1998 Link Communications Inc 9 18 98...
Page 227: ...J 5 RLC 4 V1 79 Copyright 1998 Link Communications Inc 9 18 98 Bill of Materials...