RLC-Club Deluxe II Repeater, Link and Remote Base Controller Software Version 2.15 Copyright 2004, All Rights Reserved Link Communications, Inc. 1035 Cerise Rd Billings, MT 59101-7378 (406) 245-5002 Voice (406) 245-4889 Fax http://www.link-comm.com Introduction: The RLC-Club Deluxe II is a powerful tool for controlling radio systems. It features include: 6 radio ports, each of which can be interfaced to a repeater, link or remote base Commands can be entered from any receiver, the reverse autopatch, or a computer. Separate DTMF decoders for each receiver input and the autopatch. Voice synthesizer with 680+ word library speaks ID and alarm messages and provides feedback while configuring the controller. Nearly all command codes, timer values, and messages are programmable. Each message can contain combinations of Morse code characters, synthesized speech words, sound effects, DVR tracks, etc. Hundreds of macros allow for the creation or custom commands. Real time clock/calendar chip allows the controller to speak the time or date and to execute macros at scheduled times. Autopatch with 501 programmable autodial numbers, cover tone, semi-private mode and a variety of voice response options (kerchunk to dial, etc). Reverse autopatch with over-the-air ringing, directed callout, or full control of the system. Support for frequency control of a variety of HF and VHF/UHF radios for remote bases. Built-in digital voice recorder (7.5 seconds total message length) and optional support for DVR-1 (up to 30 minutes total message length, requires Deluxe or Deluxe II option). Extensive security system prevents unauthorized changes. 5 analog voltage inputs 8 logic inputs 11 open collector output drivers. I/O alarms can send alarm messages or trigger other actions when conditions change. Beaconing system can repeat alarm messages over the air or call phone numbers until an alarm is acknowledged. Chapter 1 of this manual contains the information you will need to interface it with your radios. The RLC-Club Deluxe II default settings will allow you to get on the air quickly; setting your ID message may be all you need to do. Almost every feature can be customized if you wish; Chapters 2 though 20 are organized by feature so you can quickly find the information you need. There are several appendices with information you will probably refer to often. Near the beginning of this manual you will find a "Table Of Contents" organized by topic and a "Command List By Number" that lists all of the setup commands in numeric order, along with the pages on which more information can be found. Nearly every feature of the controller can be configured using a radio with a DTMF pad (a 16- key pad, with 'A', 'B', 'C' and 'D', is helpful for some commands) or with a computer or serial terminal. Using a computer can save you a lot of time in the long run, as you can save a file with all of the commands used to set up the Deluxe II and make future changes by modifying that file, then uploading the settings to the controller again. For more information about using a computer with the Deluxe II, see Appendix F. If you have questions the manual doesn't answer, there are a variety of ways to get help: Through the Internet: FAQs (Frequently Asked Questions): FAQs and their answers can be found at http://www.link-comm.com/faqs.html. User's Groups. You can ask questions and exchange information with other users (and us) by email by joining one of these groups. Email Us: You can get support for any of our products by emailing support@link- comm.com. Support Web Page: Links to the above support options and more can be found at http://www.link-comm.com/support.html. By Phone: (406) 245-5002 (406) 245-4889 fax By Mail Link Communications, Inc. 1035 Cerise Rd Billings, MT 59101-7378 Table of Contents Command List by Number . . . . . . . . . . . . . . . . . . . . 15 Limited Warranty . . . . . . . . . . . . . . . . . . . . . . . 21 Return Policy. . . . . . . . . . . . . . . . . . . . . . . . . 22 Regulatory Information . . . . . . . . . . . . . . . . . . . . 23 Telephone Grounding Precautions:. . . . . . . . . . . . . 24 User Survey (Optional) . . . . . . . . . . . . . . . . . . . . 25 Chapter 1: Getting Started. . . . . . . . . . . . . . . . . .1-1 Setup, Interfacing and Adjustment . . . . . . . . . . . .1-1 What Each Connector is For. . . . . . . . . . . . . . . .1-2 What the LED's Represent: . . . . . . . . . . . . . . . .1-3 Configuring the Controller. . . . . . . . . . . . . . . .1-9 Serial Port Interfacing . . . . . . . . . . . . . . . . .1-9 Reset and Power Up. . . . . . . . . . . . . . . . . . . 1-13 Entering Commands . . . . . . . . . . . . . . . . . . . 1-14 Error Messages. . . . . . . . . . . . . . . . . . . . . 1-16 How to Configure a Port as a Repeater . . . . . . . . . 1-18 Example 1-1: Configuring a Port as a Repeater or Link . 1-19 Example 1-2: Configuring a Port's COR/PL Polarity . . . 1-20 Troubleshooting the Controller. . . . . . . . . . . . . 1-22 Chapter 2: Port Connection Commands . . . . . . . . . . . . .2-1 "Connected Ports" . . . . . . . . . . . . . . . . . . . .2-1 Turning a Repeater Off. . . . . . . . . . . . . . . . . .2-2 000: Connect Ports. . . . . . . . . . . . . . . . . . . .2-4 001: Monitor Ports. . . . . . . . . . . . . . . . . . . .2-6 002: Disconnect Ports . . . . . . . . . . . . . . . . . .2-8 061: Disconnect all Ports from a Radio Port. . . . . . 2-10 068: Disconnect all Ports (but leave repeaters). . . . 2-10 008: "Smart" Connect Ports. . . . . . . . . . . . . . . 2-11 003: Recall Which Transmitters A Receiver Is Connected To2-17 004: Recall Which Receivers Are Connected to a Transmitter2-18 009: Recall Controller's Entire Audio Crosspoint. . . . 2-19 005: Set Receiver and DTMF Decoder Conditions . . . . . 2-20 006: Set or Recall Receiver Priorities (monitor mute) . 2-23 013: Set COR and PL Active Levels . . . . . . . . . . . 2-24 155: Enable or Disable PTT for a Port. . . . . . . . . 2-25 156: Recall Which PTT are Enabled. . . . . . . . . . . 2-25 Chapter 3: Audio and DTMF configurations . . . . . . . . . . .3-1 007: Configure DTMF Mute/Cover Tone/Bypass. . . . . . . .3-6 Chapter 4: Timers. . . . . . . . . . . . . . . . . . . . . . .4-1 020: Set or Recall a Timer's Duration . . . . . . . . . .4-2 List of Timers. . . . . . . . . . . . . . . . . . . . . .4-3 021: Restart a Timer (if already running) . . . . . . . 4-18 022: Start/Restart a Timer. . . . . . . . . . . . . . . 4-19 023: Stop a Timer . . . . . . . . . . . . . . . . . . . 4-20 025: Sets the Time of Day Clock . . . . . . . . . . . . 4-20 026: Recall the Time of Day Clock in Male Speech. . . . 4-21 027: Recall the Time of Day Clock in Female Speech. . . 4-21 028: Sets the Date. . . . . . . . . . . . . . . . . . . 4-22 029: Recall the Date. . . . . . . . . . . . . . . . . . 4-23 Chapter 5: Command Names. . . . . . . . . . . . . . . . . . .5-1 How Command Names and Command Numbers are Used: . . . . .5-1 010: Re-Program Command Names . . . . . . . . . . . . . .5-6 062: Change the Beginning of Command Names . . . . . . .5-8 011: Recall Command Name. . . . . . . . . . . . . . . . .5-9 012: Find Commands Named ... . . . . . . . . . . . . . 5-10 Blocking Execution from Certain Ports . . . . . . . . . 5-11 130: Block Command Execution From Port . . . . . . . . 5-12 131: Allow Command Execution From Port . . . . . . . . 5-12 Chapter 6: CW, DTMF, Voice and DVR Messages . . . . . . . . .6-1 030: Send a CW Message. . . . . . . . . . . . . . . . . .6-2 031: Send a DTMF Sequence . . . . . . . . . . . . . . . .6-3 069: Send a DTMF To Specified Transmitter . . . . . . . .6-5 036: Send a Voice Message . . . . . . . . . . . . . . . .6-7 066: Send a Voice Message Using English Words . . . . . .6-8 040: Send One or Two Tone Sequence . . . . . . . . . . .6-9 Note about Courtesy Beeps . . . . . . . . . . . . . . . 6-10 041: Set/Recall Courtesy Beep Settings. . . . . . . . . 6-13 042: Set CW Speed for a Selected Port. . . . . . . . . 6-14 043: Set CW 2-Tone Frequencies for a Selected Port . . 6-15 044: Set Up DTMF Regenerate Parameters . . . . . . . . 6-16 051: Start Dial-Tone . . . . . . . . . . . . . . . . . 6-16 063: Send a Polite Voice Message . . . . . . . . . . . 6-17 064: Send a Polite Voice Msg, If Interrupted Execute Cmd6-18 163: Keypad Test . . . . . . . . . . . . . . . . . . . 6-19 The DVR1 Digital Voice Recorder . . . . . . . . . . . . 6-20 What the DVR1 is: . . . . . . . . . . . . . . 6-20 182: Enable/Disable RLC-DVR1 . . . . . . . . . . . . . 6-28 170: Record and Play Audio Test. . . . . . . . . . . . 6-28 171: Record DVR Track (non-prompted) . . . . . . . . . 6-29 172: Record DVR Track (prompted) . . . . . . . . . . . 6-30 173: Play DVR Tracks . . . . . . . . . . . . . . . . . 6-30 174: Erase DVR Tracks. . . . . . . . . . . . . . . . . 6-31 175: Record Public Mail. . . . . . . . . . . . . . . . 6-32 176: Check Public Mailboxes. . . . . . . . . . . . . . 6-32 177: Retrieve Public Mail. . . . . . . . . . . . . . . 6-33 178: Erase Public Mail . . . . . . . . . . . . . . . . 6-33 179: Record Private Mail . . . . . . . . . . . . . . . 6-34 180: Retrieve Private Mail . . . . . . . . . . . . . . 6-34 181: Erase Private Mail. . . . . . . . . . . . . . . . 6-34 The Internal Digital Voice Recorder . . . . . . . . . . 6-35 183: Record a Message on the Internal DVR. . . . . . . 6-36 184: Playback an Internal DVR Message(s) . . . . . . . 6-37 185: Erase Internal DVR Message(s) . . . . . . . . . . 6-37 052: Audio Test using the Internal DVR . . . . . . . . 6-38 034: Adjust each Port's Internal DVR Record Level. . . 6-39 Chapter 7: Serial Port Commands . . . . . . . . . . . . . . .7-1 024: Set Up RS-232 Serial Baud Rate . . . . . . . . . . .7-3 060: Set Up Serial Port Options. . . . . . . . . . . . .7-4 032: Send Serial Message. . . . . . . . . . . . . . . . .7-6 162: Always Send Serial Message out the Main Serial Port7-6 169: Always Send Serial out Main Serial Port by ASCII Code7-7 138: Direct SPI Send using Open Collector Output Lines .7-8 Chapter 8: Macros. . . . . . . . . . . . . . . . . . . . . . .8-1 How Macros Get Executed:. . . . . . . . . . . . . . . . .8-1 What a macro is:. . . . . . . . . . . . . . . . . . . . .8-1 Advanced Macro Topics:. . . . . . . . . . . . . . . . . .8-2 200..499: Execute an Automatic Macro . . . . . . . . . .8-5 500..999: Execute a User Macro . . . . . . . . . . . . .8-5 055: Erase Macro . . . . . . . . . . . . . . . . . . . .8-6 056: Add Command to a Macro . . . . . . . . . . . . . . .8-6 053: Erase Then Add Command To Macro. . . . . . . . . . .8-7 054: Recall Macro Contents . . . . . . . . . . . . . . .8-8 057: Copy a Macro. . . . . . . . . . . . . . . . . . . .8-9 058: Erase a Command in a Macro. . . . . . . . . . . . .8-9 059: Insert a Command in a Macro . . . . . . . . . . . 8-10 067: Set Macro Data Length. . . . . . . . . . . . . . . 8-11 Automatic Macros. . . . . . . . . . . . . . . . . . . . 8-12 Chapter 9: Pre-Access Commands . . . . . . . . . . . . . . . .9-1 What preaccess is:. . . . . . . . . . . . . . . . . . . .9-1 What you need to know:. . . . . . . . . . . . . . . . . .9-1 049: Set Link Access Tone Frequencies . . . . . . . . . .9-2 070: Configure a Repeater for Preaccess. . . . . . . . .9-3 071: Configure a Link for Preaccess. . . . . . . . . . .9-4 072: Disable Preaccess Requirement for a Port. . . . . .9-5 073: Recall Ports with Preaccess Requirement . . . . . .9-5 074: Allow Access To a Port that Requires Preaccess. . .9-6 075: Set Stop Access Conditions. . . . . . . . . . . . .9-7 076: Recall Stop Access Conditions . . . . . . . . . . .9-8 077: Isolate a Port from the Rest of the System. . . . .9-8 Chapter 10: Scheduler. . . . . . . . . . . . . . . . . . . . 10-1 How the Scheduler Works:. . . . . . . . . . . . . . . . 10-1 082: Set Up a Scheduler Event. . . . . . . . . . . . . 10-1 083: Recall a Scheduler Event. . . . . . . . . . . . . 10-6 084: Enable/Disable a Scheduler Event . . . . . . . . . 10-7 Chapter 11: The ID System. . . . . . . . . . . . . . . . . . 11-1 How the IDs Work: . . . . . . . . . . . . . . . . . . . 11-1 Polite Voice IDs: . . . . . . . . . . . . . . . . . . . 11-1 To Program Your Own IDs:. . . . . . . . . . . . . . . . 11-2 More about Programming IDs: . . . . . . . . . . . . . . 11-3 ID Timing:. . . . . . . . . . . . . . . . . . . . . . . 11-3 085: Enable/Disable IDing a Port . . . . . . . . . . . 11-5 086: Recall Which Ports have IDs Enabled . . . . . . . 11-6 087: Set Random or Rotating Pending IDs. . . . . . . . 11-6 088: Recall Random or Rotating Pending ID Selection. . 11-6 Chapter 12: I/O System . . . . . . . . . . . . . . . . . . . 12-1 About the I/O System. . . . . . . . . . . . . . . . . . 12-1 Open Collector Output Lines . . . . . . . . . . . . . . 12-1 Analog/Digital Input Lines. . . . . . . . . . . . . . . 12-1 Digital Input Lines . . . . . . . . . . . . . . . . . . 12-2 Analog Input Lines. . . . . . . . . . . . . . . . . . . 12-2 Inputs Connector Pin-Out. . . . . . . . . . . 12-4 090: Read Whether Digital Input Line is High or Low. . 12-6 091: Execute Digital Input Line High or Low Macro. . . 12-6 092: Enable/Disable Digital Input Line Alarm . . . . . 12-7 093: Turn Open Collector Output Line On. . . . . . . . 12-7 094: Turn Open Collector Output Line Off . . . . . . . 12-8 095: Recall Whether Open Collector Output Line is On or Off12-9 100: Read Analog Input Line . . . . . . . . . . . . . .12-10 101: Set Resolution For Analog Input . . . . . . . . .12-11 102: Set Conversion Ratio For Analog Input . . . . . .12-13 Custom Analog Conversion Ratios:. . . . . . .12-14 103: Calibrate an Analog Input . . . . . . . . . . . .12-16 104: Set an Analog Alarm . . . . . . . . . . . . . . .12-17 105: Set Analog Alarm Hysteresis . . . . . . . . . . .12-18 106: Enable/Disable an Analog Alarm. . . . . . . . . .12-20 107: Recall Analog Lines in Alarm. . . . . . . . . . .12-20 108: Recall Analog Line Configuration. . . . . . . . .12-21 160: Clear Analog High/Lows. . . . . . . . . . . . . .12-21 161: Set Analog Smoothing Factor . . . . . . . . . . .12-22 109: Configure Wind Speed Reading . . . . . . . . . . .12-23 096: Control or Recall Extended Output Lines. . . . . .12-24 Chapter 13: Autopatch Routines . . . . . . . . . . . . . . . 13-1 Configuring the Autopatch:. . . . . . . . . . . . . . . 13-1 Autopatch Up Commands:. . . . . . . . . . . . . . . . . 13-1 Using '*' for the Autopatch Up Command: . . . . . . . . 13-2 Hanging Up: . . . . . . . . . . . . . . . . . . . . . . 13-2 Automatic Hang Up (line current sense relay): . . . . . 13-2 Connected Ports:. . . . . . . . . . . . . . . . . . . . 13-3 Predial Digits: . . . . . . . . . . . . . . . . . . . . 13-3 The Autodialer: . . . . . . . . . . . . . . . . . . . . 13-3 Limiting Call Duration: . . . . . . . . . . . . . . . . 13-4 How the Dialing Tables Work:. . . . . . . . . . . . . . 13-4 Other Commands that Affect the Autopatch: . . . . . . . 13-6 110: Configure the Autopatch . . . . . . . . . . . . . 13-7 111: Manual Off Hook . . . . . . . . . . . . . . . . . 13-8 112: Normal Forward Dial. . . . . . . . . . . . . . . . 13-8 113: Forward Dial with no Long Distance Checking . . . 13-9 137: Autodial Only . . . . . . . . . . . . . . . . . . 13-9 129: Repeat Dial (or recall last number dialed). . . .13-10 114: Hang up the Autopatch . . . . . . . . . . . . . .13-11 115: Possibly Hang up the Autopatch. . . . . . . . . .13-11 116: Set / Recall the Predial Digits and Timing. . . .13-12 119: Set Allowed Numbers Table Slot. . . . . . . . . .13-13 120: Recall Allowed Numbers Table Slot . . . . . . . .13-13 121: Set Nuisance Numbers Table Slot . . . . . . . . .13-14 122: Recall Nuisance Numbers Table Slot. . . . . . . .13-14 123: Test Dialing Tables . . . . . . . . . . . . . . .13-15 124: Set Autodial Slot . . . . . . . . . . . . . . . .13-15 125: Recall Autodial Slot. . . . . . . . . . . . . . .13-16 126: Send Predial Digits / Callsign for Autodial Slot?13-17 127: Enable/Disable an Autodial Slot . . . . . . . . .13-18 128: Set/Recall Patch Audio Options for a TX . . . . .13-19 133: Set up Reverse Patch. . . . . . . . . . . . . . .13-21 134: Access Reverse Patch Control Mode . . . . . . . .13-23 135: Answer Reverse Patch. . . . . . . . . . . . . . .13-23 132: Start Reverse Patch Call-Out . . . . . . . . . . .13-24 136: Set up Reverse Autopatch Ring . . . . . . . . . .13-26 192: Set/Recall Call-Out Options. . . . . . . . . . . .13-27 Chapter 14: Doug Hall RBI-1 and RLC-ICM Routines . . . . . . 14-1 What the RBI-1 is:. . . . . . . . . . . . . . . . . . . 14-1 What the RLC-ICM is:. . . . . . . . . . . . . . . . . . 14-1 Interfacing and Setup:. . . . . . . . . . . . . . . . . 14-1 Using the RBI-1 or the RLC-ICM: . . . . . . . . . . . . 14-2 Building the RBI-1/RLC-ICM Cable. . . . . . . 14-5 139: Set Up the RLC-ICM Interface. . . . . . . . . . . 14-8 RLC-ICM Internal Operation Test Points. . . . . . . . .14-12 140: Set Control Connector for RBI-1 or RLC-ICM. . . .14-13 142: Set Frequency (and Offset) for RBI-1 or RLC-ICM .14-14 143: Set Offset for RBI-1 or RLC-ICM . . . . . . . . .14-15 144: Set Offset and Frequency Readback Styles. . . . .14-16 145: Set Power Level for RBI-1 . . . . . . . . . . . .14-18 146: Set PL Frequency for RBI-1 or RLC-ICM . . . . . .14-19 147: Turn PL Encode Off/On for RBI-1 or RLC-ICM. . . .14-21 148: Turn PL Decode Off/On for RBI-1 or RLC-ICM. . . .14-21 149: Recall Frequency and Offset for RBI-1 or RLC-ICM.14-22 150: Recall All RBI-1 or RLC-ICM Settings. . . . . . .14-22 151: Turn Radio Power On or Off for RBI-1. . . . . . .14-23 152: Goto Radio Memory Channel for the RBI-1 . . . . .14-24 141: Control/Recall RBI-1 Output Lines. . . . . . . . .14-25 Chapter 15: Serial Controlled (HF) Radio Support . . . . . . 15-1 HF Radio Interfacing. . . . . . . . . . . . . . . . . . 15-1 HF Radio Control: . . . . . . . . . . . . . . . . . . . 15-2 195: Configure HF Mode . . . . . . . . . . . . . . . . 15-4 196: Configure HF Radio. . . . . . . . . . . . . . . . 15-5 197: Set/Recall Transmit/Scan Band Edges . . . . . . . 15-8 198: HF Mode Enable. . . . . . . . . . . . . . . . . .15-11 HF Remote Base Keypad Definition: . . . . . .15-12 199: Enter HF Command (w/o being in HF mode) . . . . .15-18 Chapter 16: Special Audio Routing Commands . . . . . . . . . 16-1 037: Set Audio Routing Variable for Commands In a Macro 16-2 038: Execute the Rest Of This Macro Silently. . . . . . 16-3 065: Restore Audio Routing Variable (Undo 037 and 038) 16-4 039: Recall the Ports in the Current Audio Routing Variable16-6 050: Set Up or Recall Default Audio Routing Variables. 16-7 Chapter 17: Special Control Commands . . . . . . . . . . . . 17-1 035: Remotely Reset the Controller. . . . . . . . . . . 17-1 078: Set Command Entry Options for a Port. . . . . . . 17-2 079: Seed Command Buffer . . . . . . . . . . . . . . . 17-5 080: Execute Command by Number. . . . . . . . . . . . . 17-6 164: Recall Software Version . . . . . . . . . . . . . 17-7 165: Reset COP Watchdog Timer. . . . . . . . . . . . . 17-8 167: Do Nothing. . . . . . . . . . . . . . . . . . . . 17-8 014..019: Not Currently Used. . . . . . . . . . . . . . 17-9 033: Not Currently Used . . . . . . . . . . . . . . . . 17-9 089: Not Currently Used. . . . . . . . . . . . . . . . 17-9 097..099: Not Currently Used . . . . . . . . . . . . . 17-9 117..118: Not Currently Used . . . . . . . . . . . . . 17-9 153..154: Not Currently Used . . . . . . . . . . . . . 17-9 166: Not Currently Used. . . . . . . . . . . . . . . . 17-9 168: Not Currently Used. . . . . . . . . . . . . . . . 17-9 193..194: Not Currently Used . . . . . . . . . . . . . 17-9 Chapter 18: 500 User Structure . . . . . . . . . . . . . . . 18-1 The Password System . . . . . . . . . . . . . . . . . . 18-1 Method #1 - No Passwords: . . . . . . . . . 18-3 Method #2 - Fixed Passwords: . . . . . . . . 18-4 Method #3 - Challenge Passwords: . . . . . . 18-4 Method #4 - Challenge Passwords with Decoy Digits: 18-5 186: Set up User Password. . . . . . . . . . . . . . . 18-6 187: User Log-on . . . . . . . . . . . . . . . . . . . 18-7 188: Recall Who Is Logged In . . . . . . . . . . . . . 18-8 189: User Log-off. . . . . . . . . . . . . . . . . . . 18-8 190: Assign a User Level to a Command. . . . . . . . . 18-9 191: Assign a Callsign to a User . . . . . . . . . . .18-10 Chapter 19: The Beaconing System . . . . . . . . . . . . . . 19-1 045: Setup Beacon Table . . . . . . . . . . . . . . . . 19-2 046: Start Beacon . . . . . . . . . . . . . . . . . . . 19-3 047: Cancel Beacon. . . . . . . . . . . . . . . . . . . 19-3 048: Start Beacon Using English Words . . . . . . . . . 19-4 Chapter 20: Event Triggers . . . . . . . . . . . . . . . . . 20-1 157: Set/Recall Event Trigger. . . . . . . . . . . . . 20-1 158: Default Event Trigger Action . . . . . . . . . . . 20-2 159: Enable/Disable Event Trigger. . . . . . . . . . . 20-2 Appendix A: The Audio Routing Variable System . . . . . . . .A-1 Explanation of the System . . . . . . . . . . . . . . . .A-1 Suppressing Command Responses in Macros:. . . . . . . . .A-2 Appendix B: Voice Word Table. . . . . . . . . . . . . . . . .B-1 Appendix C: CW Code Table . . . . . . . . . . . . . . . . . .C-1 Appendix D: Reset and Initialization. . . . . . . . . . . . .D-1 Appendix E: Not Currently Used. . . . . . . . . . . . . . . .E-1 Appendix F: Programming with the Serial Port. . . . . . . . .F-1 Voice responses to commands entered serially: . . . . . .F-2 Using a serial upload file: . . . . . . . . . . . . . . .F-2 Note about spaces in serial commands: . . . . . . . . . .F-3 Note about comments in serial upload files: . . . . . . .F-3 Note about capital letters: . . . . . . . . . . . . . . .F-3 Note about upload speeds: . . . . . . . . . . . . . . . .F-4 Serial responses to commands entered from a radio:. . . .F-5 Very Long Serial Commands:. . . . . . . . . . . . . . . .F-5 QuickStart Software For WindowsTM . . . . . . . . . . . .F-5 Installation: . . . . . . . . . . . . . . . . .F-5 Operation:. . . . . . . . . . . . . . . . . . .F-6 Limitations:. . . . . . . . . . . . . . . . . .F-6 Appendix G: ASCII Chart . . . . . . . . . . . . . . . . . . .G-1 Appendix H: Using the LM335 Temperature Sensor. . . . . . . .H-1 Appendix I: Software Problem and Request Form . . . . . . . .I-1 Appendix K: Internet Linking (VoIP) . . . . . . . . . . . . .J-1 Appendix L: Use '*' For the Current Port. . . . . . . . . . .K-1 Hardware Reference Section . . . . . . . . . . . . . . . . . .L-1 RLC-Club Notes. . . . . . . . . . . . . . . . . . . . . .L-1 RLC-Club Deluxe II Notes. . . . . . . . . . . . . . . . .L-1 RLC-Club, Revision C, PCB Layout. . . . . . . . . . . . .J-3 RLC-Club, Revision C, Schematics . . . . . . . . . . . .J-4 RLC-Club, Revision C, Bill of Materials. . . . . . . . .J-7 RLC-Club Deluxe PCB Layout. . . . . . . . . . . . . . . J-12 RLC-Club, Revision E, Schematics. . . . . . . . . . . . J-13 RLC-Club, Revision E, Bill of Materials . . . . . . . . J-16 RLC-Club Deluxe II PCB Layout . . . . . . . . . . . . . J-20 RLC-Club Deluxe II Schematics . . . . . . . . . . . . . J-21 RLC-Club Deluxe II Bill of Materials. . . . . . . . . . J-26 Command List by Number 000: Connect Ports . . . . . . . . . . . . . . . . . . . . . .2-4 001: Monitor Ports . . . . . . . . . . . . . . . . . . . . . .2-6 002: Disconnect Ports. . . . . . . . . . . . . . . . . . . . .2-8 003: Recall Which Transmitters A Receiver Is Connected To. . 2-17 004: Recall Which Receivers Are Connected to a Transmitter . 2-18 005: Set Receiver and DTMF Decoder Conditions. . . . . . . . 2-20 006: Set or Recall Receiver Priorities (monitor mute). . . . 2-23 007: Configure DTMF Mute/Cover Tone/Bypass . . . . . . . . . .3-6 008: "Smart" Connect Ports . . . . . . . . . . . . . . . . . 2-11 009: Recall Controller's Entire Audio Crosspoint . . . . . . 2-19 010: Re-Program Command Names. . . . . . . . . . . . . . . . .5-6 011: Recall Command Name . . . . . . . . . . . . . . . . . . .5-9 012: Find Commands Named .... . . . . . . . . . . . . . . . 5-10 013: Set COR and PL Active Levels. . . . . . . . . . . . . . 2-24 014..019: Not Currently Used. . . . . . . . . . . . . . . . 17-9 020: Set or Recall a Timer's Duration. . . . . . . . . . . . .4-2 021: Restart a Timer (if already running). . . . . . . . . . 4-18 022: Start a Timer . . . . . . . . . . . . . . . . . . . . . 4-19 023: Stop a Timer. . . . . . . . . . . . . . . . . . . . . . 4-20 024: Set Up RS-232 Serial Baud Rate. . . . . . . . . . . . . .7-3 025: Sets the Time of Day Clock. . . . . . . . . . . . . . . 4-20 026: Recall the Time of Day Clock in Male Speech . . . . . . 4-21 027: Recall the Time of Day Clock in Female Speech . . . . . 4-21 028: Sets the Date . . . . . . . . . . . . . . . . . . . . . 4-22 029: Recall the Date . . . . . . . . . . . . . . . . . . . . 4-23 030: Send a CW Message . . . . . . . . . . . . . . . . . . . .6-2 031: Send a DTMF Sequence. . . . . . . . . . . . . . . . . . .6-3 032: Send Serial Message . . . . . . . . . . . . . . . . . . .7-6 033: Not Currently Used. . . . . . . . . . . . . . . . . . . 17-9 034: Adjust each Port's Internal DVR Record Level . . . . . 6-39 035: Remotely Reset the Controller . . . . . . . . . . . . . 17-1 036: Send a Voice Message. . . . . . . . . . . . . . . . . . .6-7 037: Set Audio Routing Variable for Commands In a Macro. . . 16-2 038: Execute the Rest Of This Macro Silently . . . . . . . . 16-3 039: Recall the Ports in the Current Audio Routing Variable 16-6 040: Send One or Two Tone Sequence. . . . . . . . . . . . . .6-9 041: Set/Recall Courtesy Beep Settings . . . . . . . . . . . 6-13 042: Set CW Speed for a Selected Port . . . . . . . . . . . 6-14 043: Set CW 2-Tone Frequencies for a Selected Port. . . . . 6-15 044: Set Up DTMF Regenerate Parameters. . . . . . . . . . . 6-16 045: Setup Beacon Table. . . . . . . . . . . . . . . . . . . 19-2 046: Start Beacon. . . . . . . . . . . . . . . . . . . . . . 19-3 047: Cancel Beacon . . . . . . . . . . . . . . . . . . . . . 19-3 048: Start Beacon Using English Words. . . . . . . . . . . . 19-4 049: Configure a Port's Tone Response when in Preaccess . . .9-2 050: Set Up or Recall Default Audio Routing Variables . . . 16-7 051: Start Dial-Tone. . . . . . . . . . . . . . . . . . . . 6-16 052: Audio Test using the Internal DVR. . . . . . . . . . . 6-38 053: Erase Then Add Command To Macro . . . . . . . . . . . . .8-7 054: Recall Macro Contents. . . . . . . . . . . . . . . . . .8-8 055: Erase Macro. . . . . . . . . . . . . . . . . . . . . . .8-6 056: Add Command to a Macro. . . . . . . . . . . . . . . . . .8-6 057: Copy a Macro . . . . . . . . . . . . . . . . . . . . . .8-9 058: Erase a Command in a Macro . . . . . . . . . . . . . . .8-9 059: Insert a Command in a Macro. . . . . . . . . . . . . . 8-10 060: Set Up Serial Port . . . . . . . . . . . . . . . . . . .7-4 061: Disconnect all Ports from a Radio Port . . . . . . . . 2-10 062: Change the Beginning of Command Names. . . . . . . . . .5-8 063: Send a Polite Voice Message. . . . . . . . . . . . . . 6-17 064: Send a Polite Voice Message and if Interrupted.... . . 6-18 065: Restore Audio Routing Variable (Undo 037 and 038). . . 16-4 066: Send a Voice Message Using English Words. . . . . . . . .6-8 067: Set Macro Data Length . . . . . . . . . . . . . . . . . 8-11 068: Disconnect all Ports (but leave repeaters) . . . . . . 2-10 069: Send a DTMF To Specified Transmitter. . . . . . . . . . .6-5 070: Configure a Repeater for Preaccess . . . . . . . . . . .9-3 071: Configure a Link for Preaccess . . . . . . . . . . . . .9-4 072: Disable Preaccess Requirement for a Port . . . . . . . .9-5 073: Recall Ports with Preaccess Requirement. . . . . . . . .9-5 074: Allow Access To a Port that Requires Preaccess . . . . .9-6 075: Set Stop Access Conditions . . . . . . . . . . . . . . .9-7 076: Recall Stop Access Conditions. . . . . . . . . . . . . .9-8 077: Isolate a Port from the Rest of the System . . . . . . .9-8 078: Set up Force-Execution Functions for a Port. . . . . . 17-2 079: Seed Command Buffer. . . . . . . . . . . . . . . . . . 17-5 080: Execute Command by Number . . . . . . . . . . . . . . . 17-6 082: Set Up a Scheduler Event . . . . . . . . . . . . . . . 10-1 083: Recall a Scheduler Event . . . . . . . . . . . . . . . 10-6 084: Enable/Disable a Scheduler Event. . . . . . . . . . . . 10-7 085: Enable/Disable IDing a Port. . . . . . . . . . . . . . 11-5 086: Recall Which Ports have IDs Enabled. . . . . . . . . . 11-6 087: Set Random or Rotating Pending IDs . . . . . . . . . . 11-6 088: Recall Random or Rotating Pending ID Selection . . . . 11-6 089: Not Currently Used . . . . . . . . . . . . . . . . . . 17-9 090: Read Whether Digital Input Line is High or Low . . . . 12-6 091: Execute Digital Input Line High or Low Macro . . . . . 12-6 092: Enable/Disable Digital Input Line Alarm. . . . . . . . 12-7 093: Turn Open Collector Output Line On . . . . . . . . . . 12-7 094: Turn Open Collector Output Line Off. . . . . . . . . . 12-8 095: Recall Whether Open Collector Output Line is On or Off 12-9 096: Control or Recall Extended Output Lines . . . . . . . .12-24 097..099: Not Currently Used. . . . . . . . . . . . . . . . 17-9 100: Read Analog Input Line. . . . . . . . . . . . . . . . .12-10 101: Set Resolution For Analog Input. . . . . . . . . . . .12-11 102: Set Conversion Ratio For Analog Input. . . . . . . . .12-13 103: Calibrate an Analog Input. . . . . . . . . . . . . . .12-16 104: Set an Analog Alarm. . . . . . . . . . . . . . . . . .12-17 105: Set Analog Alarm Hysteresis. . . . . . . . . . . . . .12-18 106: Enable/Disable an Analog Alarm . . . . . . . . . . . .12-20 107: Recall Analog Lines in Alarm . . . . . . . . . . . . .12-20 108: Recall Analog Line Configuration . . . . . . . . . . .12-21 109: Configure Wind Speed Reading. . . . . . . . . . . . . .12-23 110: Configure the Autopatch. . . . . . . . . . . . . . . . 13-7 111: Manual Off Hook. . . . . . . . . . . . . . . . . . . . 13-8 112: Normal Forward Dial . . . . . . . . . . . . . . . . . . 13-8 113: Forward Dial with no Long Distance Checking. . . . . . 13-9 114: Hang up the Autopatch. . . . . . . . . . . . . . . . .13-11 115: Possibly Hang up the Autopatch . . . . . . . . . . . .13-11 116: Set / Recall the Predial Digits and Timing . . . . . .13-12 117..118: Not Currently Used. . . . . . . . . . . . . . . . 17-9 119: Set Allowed Numbers Table Slot . . . . . . . . . . . .13-13 120: Recall Allowed Numbers Table Slot. . . . . . . . . . .13-13 121: Set Nuisance Numbers Table Slot. . . . . . . . . . . .13-14 122: Recall Nuisance Numbers Table Slot . . . . . . . . . .13-14 123: Test Dialing Tables. . . . . . . . . . . . . . . . . .13-15 124: Set Autodial Slot. . . . . . . . . . . . . . . . . . .13-15 125: Recall Autodial Slot . . . . . . . . . . . . . . . . .13-16 126: Send Predial Digits / Callsign for Autodial Slot?. . .13-17 127: Enable/Disable an Autodial Slot. . . . . . . . . . . .13-18 128: Set Full or Half-Duplex Patch Audio for a TX . . . . .13-19 129: Repeat Dial (or recall last number dialed) . . . . . .13-10 130: Block Command Execution From Port. . . . . . . . . . . 5-12 131: Allow Command Execution From Port. . . . . . . . . . . 5-12 132: Start Reverse Patch Call-Out. . . . . . . . . . . . . .13-24 133: Set up Reverse Patch . . . . . . . . . . . . . . . . .13-21 134: Access Reverse Patch Control Mode. . . . . . . . . . .13-23 135: Answer Reverse Patch . . . . . . . . . . . . . . . . .13-23 136: Set up Reverse Autopatch Ring. . . . . . . . . . . . .13-26 137: Autodial Only. . . . . . . . . . . . . . . . . . . . . 13-9 138: Direct SPI Send using Open Collector Output Lines. . . .7-8 139: Set Up the RLC-ICM Interface . . . . . . . . . . . . . 14-8 140: Set Control Connector for RBI-1 or RLC-ICM . . . . . .14-13 141: Control/Recall RBI-1 Output Lines . . . . . . . . . . .14-25 142: Set Frequency (and Offset) for RBI-1 or RLC-ICM. . . .14-14 143: Set Offset for RBI-1 or RLC-ICM. . . . . . . . . . . .14-15 144: Set Offset and Frequency Readback Styles . . . . . . .14-16 145: Set Power Level for RBI-1. . . . . . . . . . . . . . .14-18 146: Set PL Frequency for RBI-1 or RLC-ICM. . . . . . . . .14-19 147: Turn PL Encode Off/On for RBI-1 or RLC-ICM . . . . . .14-21 148: Turn PL Decode Off/On for RBI-1 or RLC-ICM . . . . . .14-21 149: Recall Frequency and Offset for RBI-1 or RLC-ICM . . .14-22 150: Recall All RBI-1 or RLC-ICM Settings . . . . . . . . .14-22 151: Turn Radio Power On or Off for RBI-1 . . . . . . . . .14-23 152: Goto Radio Memory for RBI-1. . . . . . . . . . . . . .14-24 153..154: Not Currently Used. . . . . . . . . . . . . . . . 17-9 155: Enable or Disable PTT for a Port . . . . . . . . . . . 2-25 156: Recall Which PTT are Enabled . . . . . . . . . . . . . 2-25 157: Set/Recall Event Trigger . . . . . . . . . . . . . . . 20-1 158: Default Event Trigger Action. . . . . . . . . . . . . . 20-2 159: Enable/Disable Event Trigger . . . . . . . . . . . . . 20-2 160: Clear Analog High/Lows . . . . . . . . . . . . . . . .12-21 161: Set Analog Smoothing Factor. . . . . . . . . . . . . .12-22 162: Always Send Serial Message out the Main Serial Port. . .7-6 163: Keypad Test. . . . . . . . . . . . . . . . . . . . . . 6-19 164: Recall Software Version. . . . . . . . . . . . . . . . 17-7 165: Reset COP Watchdog Timer . . . . . . . . . . . . . . . 17-8 166: Not Currently Used . . . . . . . . . . . . . . . . . . 17-9 167: Do Nothing . . . . . . . . . . . . . . . . . . . . . . 17-8 168: Not Currently Used . . . . . . . . . . . . . . . . . . 17-9 169: Always Send Serial out Main Serial Port by ASCII Code. .7-7 170: Record and Play Audio Test . . . . . . . . . . . . . . 6-28 171: Record DVR Track (non-prompted). . . . . . . . . . . . 6-29 172: Record DVR Track (prompted). . . . . . . . . . . . . . 6-30 173: Play DVR Tracks. . . . . . . . . . . . . . . . . . . . 6-30 174: Erase DVR Tracks . . . . . . . . . . . . . . . . . . . 6-31 175: Record Public Mail . . . . . . . . . . . . . . . . . . 6-32 176: Check Public Mailboxes . . . . . . . . . . . . . . . . 6-32 177: Retrieve Public Mail . . . . . . . . . . . . . . . . . 6-33 178: Erase Public Mail. . . . . . . . . . . . . . . . . . . 6-33 179: Record Private Mail. . . . . . . . . . . . . . . . . . 6-34 180: Retrieve Private Mail. . . . . . . . . . . . . . . . . 6-34 181: Erase Private Mail . . . . . . . . . . . . . . . . . . 6-34 182: Enable/Disable RLC-DVR1. . . . . . . . . . . . . . . . 6-28 183: Record a Message on the Internal DVR . . . . . . . . . 6-36 184: Playback an Internal DVR Message(s). . . . . . . . . . 6-37 185: Erase Internal DVR Message(s). . . . . . . . . . . . . 6-37 186: Set up User Password . . . . . . . . . . . . . . . . . 18-6 187: User Log-on. . . . . . . . . . . . . . . . . . . . . . 18-7 188: Recall Who Is Logged In. . . . . . . . . . . . . . . . 18-8 189: User Log-off . . . . . . . . . . . . . . . . . . . . . 18-8 190: Assign a User Level to a Command . . . . . . . . . . . 18-9 191: Assign a Callsign to a User. . . . . . . . . . . . . .18-10 192: Set/Recall Call-Out Options . . . . . . . . . . . . . .13-27 193..194: Not Currently Used. . . . . . . . . . . . . . . . 17-9 195: Configure HF Mode. . . . . . . . . . . . . . . . . . . 15-4 196: Configure HF Radio . . . . . . . . . . . . . . . . . . 15-5 197: Set/Recall Transmit/Scan Band Edges. . . . . . . . . . 15-8 198: HF Mode Enable . . . . . . . . . . . . . . . . . . . .15-11 199: Enter HF Command (w/o being in HF mode). . . . . . . .15-18 200..499: Execute an Internal Macro . . . . . . . . . . . . .8-5 500..999: Execute a User Macro. . . . . . . . . . . . . . . .8-5 Limited Warranty COVERAGE: Link Communications, Inc. warrants that its products will be free from defects in materials and workmanship for a period of one year from the date of shipment. During this time, Link Communications, Inc. will cover parts, labor and return shipping. If failure is caused by instances other than manufacturing defects, Link Communications, Inc. will repair the product and bill the customer for parts and labor. Contact Link Communications, Inc. for more information. What Link Communications, Inc. will not cover: 1. Too much voltage to the controller. The RLC-Club Deluxe II operates at +11V to +15V, negative ground. 2. Damage to the controller by lightning, accident, or incorrect power hook-up. 3. Incorrect unit installation. 4. Damage caused by shipment (damage claims are handled by the carrier). 6. Repairs by other than Link Communications, Inc. THIS WARRANTY HOLDS ONLY TO THE ORIGINAL PURCHASER HOW TO GET SERVICE Please contact Link Communications, Inc. for servicing information and authorization. SOFTWARE Link Communications, Inc. holds the copyright on the RLC-Club Deluxe II's software and hardware. Changes to the software, copying of the software, and use of the voice code is prohibited without the written consent of Link Communications, Inc. SOFTWARE UPDATES Link Communications, Inc. will provide FREE Software updates for 6 months from the date of purchase. The owner must return replaced software chips to Link Communications, Inc. in order to obtain further software updates. Software updates costs will be determined at the release of the update. Manual inserts and shipping are additional. Return Policy These policies supersede policies appearing on all other Link Communications, Inc. literature and are in effect for purchases made after March 1, 1989. Please keep all packing material and documentation in the event that your equipment has to be serviced or returned. Before returning any product, you must obtain a Return Authorization (RMA) number. You can obtain this by calling (406) 245-5002. No returns, of any type, will be accepted without an RMA number. Please have the following information on hand when calling for an RMA number: customer name, invoice number, serial number, and the nature of the problem. All can be found on your invoice. All product to be returned must be returned within 30 days from the invoice date, 100% complete, and must include manuals, parts bags, and other accessories provided by the manufacturer. All defective products will be accepted directly by Link Communications, Inc. for credit, exchange, replacement, or repair at Link Communications, Inc.'s discretion. After 30 days from invoice date, the manufacturer's warranty applies. All non-defective returns for credit, exchange, or refund are subject to a restocking fee on the schedule listed below. No returns will be accepted beyond the 30 day period. Shipping costs are not refundable. 0 to 10 days 5% restocking 11 to 20 days 10% restocking 21 to 30 days 15% restocking Link Communications, Inc. reserves the right to authorize product returns beyond 30 days from date of invoice. If the product is accepted after 30 days, credit will be issued toward FUTURE PURCHASE ONLY. If you have any questions JUST ASK. All of us have tried to make sure that this order has been shipped correctly. If we have made an error - we want to make it right. If you have a question or problem with this order, just write or call, and our staff will personally handle your situation. Link Communications, Inc. is a Montana Corporation FEIN 81-0490597 Regulatory Information Federal Communications Commission ( FCC ) Regulations: To comply with FCC regulations, the following requirements must be met: The FCC Registration Number of this device and Ringer Equivalence Number ( 0.7B ), if requested by the telephone company, must be reported. This information is attached to a label found the bottom of this device. The sum of Ringer Equivalence Numbers for all devices connected to a single telephone line should not exceed 5 for reliable operation. This device must not be installed on coin-operated telephone lines or party lines. This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions: 1. this device may not cause harmful interference, and 2. this device must accept any interference received, including interference that may cause undesired operation. Repair work on this device must be done by Link Communications, Inc. or an authorized repair station. Made in the USA Telephone Grounding Precautions: The autopatch interface on the RLC-Club contains a 3 pole SIDACtorTM that is used to provide surge and lightning protection to the circuits of the controller. You will notice that there is a separate ground terminal provided. This terminal must be connected to an external earth ground to provide the controller with the designed protection. Do not connect this ground to your power supply ground terminal. Connection to the power supply ground can damage both the controller and the power supply incase of a surge/lightning strike on the phone lines. The autopatch provides 2 fuses (500mA) in series with the phone line (F3 is series with the telephone TIP, and F2 is series with the telephone RING circuits). If either or both of the fuses blow, a surge/lightning incident has occurred. Only replace the fuses with 500mA, pico fuses. If larger fuses are used, damage to the controllers telephone interface can occur. UL1459 regulations require the fuses, so don't bypass them. Note that it is possible for the resistors that are in series with those fuses to be blown in addition to or instead of the fuses. SIDACtorTM is a registered trademark of Teccor Electronics, Inc. User Survey (Optional) A knowledge of the user base will allow us to better serve you in the future by helping us develop more specialized software and hardware. Please take a few minutes and fill out this questionnaire. RLC-Club Deluxe II Serial Number ................. ________________ (The serial number should be noted on your invoice and handwritten on the Deluxe II circuit board) RLC-Club Deluxe II Purchase Date ................. ________________ Application: (Circle All That Apply) Ownership: - 1 - Privately Owned Repeater - 2 - Club Owned Repeater - 3 - Group Owned Repeater - 4 - Commercial Business Repeater - 5 - Other _______________________ Installation: - 1 - Wide Coverage Repeater with Chain Links - Port to Port Linking - 2 - Full Duplex Links - 3 - Half Duplex Links - 4 - VHF Repeater: Power _____ Make ____________ - 5 - UHF Repeater: Power _____ Make ____________ - 6 - Link Ports Used as Repeater Ports: Yes No - 7 - Serial Data Used to Control Repeater: Yes No - 8 - Other Amateur Repeaters At the Site: Yes No - 9 - Other Link Communication Inc. Products Used: Yes No Misc: - 1 - User Base: Technical Rag Chew Personal - 2 - Autopatch used on the System: Yes No - 3 - Frequency Adjustable Remotes: Yes No - 4 - Linking to Other Repeaters: Yes No - 5 - Linking Closed Access: Yes No - 6 - PL Required on Main Repeater: Yes No Varies - 7 - PL Required on Linking System: Yes No Varies Please Return to: Link Communications, Inc. 1035 Cerise Rd Billings, MT 59101-7378 Comments: Chapter 1: Getting Started Setup, Interfacing and Adjustment This section of the manual contains everything you should need to know to get your repeater controller up and running. The numbered steps cover the basics, through connecting your radios and adjusting the RLC-Club Deluxe II. After that there is information about the I/O and serial port connections. Step #1: Check the Packing List Your package should contain the following items: (1) RLC-Club Deluxe II Repeater Controller (1) 2.50mm Power Connector (2) DB-9 Male Solder-cup Connectors (1) RLC-Club Deluxe II Manual If you ordered the optional Deluxe II expansion board: (1) Deluxe II Expansion board (1) Ribbon Cable for connection to the main controller board (7) DB-9 Male Solder Connector Any other options you ordered. If any of these parts are missing, contact Link Communications Inc. What Each Connector is For When you look at the back of the RLC-Club Deluxe II cabinet, you will see three horizontal slots. The leftmost slot provides access to the RJ-11 for the autopatch and the power jack. The middle slot is for three DB-9 connectors. The left connector is the serial port that you can connect to a computer or serial terminal to program the controller. The middle connector is for the analog/digital input lines (for reading contact closures, voltages and temperatures). The rightmost connector in the middle slot is radio port #1, where you usually hook up your main repeater. It has connections for audio in, audio out, COR, PTT, and PL detect. If you have the optional Deluxe II board, there will be five more DB-9 connectors showing through the back in the cabinet for radio ports 2 through 6. On the side of the cabinet you will see three connectors, a DB-25 and two DB-9s. The DB-25 provides an interface for the optional DVR1. The middle connector (a DB-9) supplies eight open collector output lines (used for turning things on and off). It has the same pinout as the outputs connector on the original RLC- Club Deluxe board and the RLC-2. The right connector (a DB-9) has three more open collector outputs and three digital inputs. What the LED's Represent: The figure above shows each of the RLC-Club Deluxe II's 28 LEDs. The LEDs are broken up into 6 groups of 4 for each of the Deluxe II's 6 ports, 1 group of 3 for the patch and 1 LED for the DVR. Each LED has a single letter label above it to signify its meaning. The meaning of these labels are: C - COR Active for Port P - PL Active for Port T - Transmitter(PTT) Active for Port D - DTMF Detected on Port R - Autopatch Ringing H - Autopatch off-hook A - DVR Active (Playing or Recording, blinks when waiting to record) Step #2: Connecting Power - The RLC-Club Deluxe II was designed to run off of 12V DC. 11V to 14V should work fine. - Locate the 2.50mm power connector included in your parts bag. - Unscrew the plastic outer shield and thread your power and ground wires through it (20 gauge suggested). - Solder the +12V wire to the center pin of the 2.50mm connector. - Solder the ground wire to the shield of the 2.50mm power connector. - Screw on the plastic outer shield. - When power is applied to the RLC-Club Deluxe II controller, some of the front panel LED's will light indicating a PTT condition. If none of the LED's light, turn off the power immediately. Step #3: Connecting Your Receivers to the RLC-Club Deluxe II The radios connect to the RLC-Club Deluxe II using a male DB-9 connector (included). The pin-outs are listed below. Pin Number Description 1 Ground 2 PL Input (From your PL Decoder) 3 PTT Output (To the Transmitter) 4 Audio Output (To the Transmitter) 600 5 Audio Input (From the Receiver) 10K 6 Ground 7 COR (From your Receiver) 8 Ground 9 Ground Connecting the Receiver COR The first step in connecting your receiver is to locate an active receiver signal. If the voltage goes from a voltage above 5 volts to ground when a signal is present, the signal is active low. If the voltage goes from a ground to a voltage above 5 volts the signal is active high. The signal must be able to sink 4mA to ground. The input impedance of the RLC-Club Deluxe II COR input is 10K and it is diode clamped with internal pull-up resistors. This allows it to handle input voltages of up to 40 volts without damage to the controller. The COR input must not go below 0V (ground); this would damage radio port's COR/PL input. Using one of the supplied DB-9 Male connectors, connect your COR signal to pin #7. The COR defaults to active low. If the signal is not active low the user must change the controller's COR polarity (try entering "013 110" on your radio's DTMF pad - see command 013 for more information). The front panel LED labeled RX will light when a correct activity signal is received. If the LED lights at the wrong times, you probably have your COR or PL polarity backwards. If the LED does not light at all, the RLC-Club Deluxe II is not detecting your COR/PL input correctly. Use a volt meter to make sure that the signal from your receiver changes from ground to above 5 volts (or vice versa) when the receiver goes active. Once you have the receiver's COR polarity set correctly, you should reconfigure port 1 with the following commands: 005 111 ; set the DTMF decoder for COR access 078 100 ; turn off timed execution That will allow the controller to execute DTMF commands immediately when you unkey. To make it easier to set up initially, the DTMF decoder for port 1 defaults to ignoring the COR input and executing about 4 seconds after you release the a DTMF digit. That allows you to enter command 013 to change the COR polarity if it is wrong. Connecting a PL Input (optional) If you wish to use a PL (CTCSS) decoder on any of the receivers, its detect line can be connected to pin #2 of the appropriate connector in the same fashion as the COR input. You can select the PL polarity (see command 013). You will probably also want to use the audio filter on the PL decoder board to filter the PL signal out of the receiver's audio before it goes to the RLC-Club Deluxe II. Connecting the Receiver Audio - 2 types of audio can be used on the RLC-Club Deluxe II controller: Type 1: De-emphasized audio (Speaker Audio) Type 2: Discriminator audio (Raw Unsquelched Audio) - If type 1 audio is used, remove the "-6dB Filter" jumper. This removes the de-emphasis filter from the circuit. If you are using discriminator audio, install the jumper. The filter will not allow PL to pass through the controller. Contact Link Communications Inc. if you need to pass PL through the controller. - The audio input is connected to pin #5 of the male DB-9 connector - The audio adjustments will be described in Step #5. - Preferred audio input level to the controller is 100mV - 500mV peak-peak audio Summary of Jumper Settings -6dB deemphasis switch. When this jumper is off, flat audio is required. When this jumper is across the 2 pins, pre-emphasis audio is used. RLC-ADM digital audio delay module interface connector. This connector allows direct connection to the digital audio delay module. If the module is not used, pins 1,2 must be jumpered (Default). When using the module make sure the RLC-ADM's connector labeled RLC-Club Deluxe II is the one that is loaded, not the connector at the other end. When using the RLC-ADM module remove the jumper and simply install the module. RLC-MOT squelch module interface connector. This connector allows direct connection to the squelch module. If the module is not used, pins 2,3 must be jumpered (Default). When using the RLC-MOT module remove the jumper and simply install the module. Deluxe II Jumpers RX 1 RX 2 RX 3 RX 4 RX 5 RX 6 -6 dB Deemphasis J3 J3 J5 J7 J9 J12 RLC-ADM J2 J2 J4 J6 J8 N/A RLC-MOT J1 N/A N/A N/A N/A N/A Step #4: Connecting Your Transmitters to the RLC-Club Deluxe II Transmitter PTT - The RLC-Club Deluxe II produces an active low PTT signal (ground when PTT is active). This output is buffered with an open collector type driver capable of sinking 150mA. There is a built in 30V zener clamping diode to protect the PTT MOSFET from the high voltage spikes that can be caused by interfacing to a PTT relay coil. Your transmitter PTT input should be connected to pin #3 of the DB-9 connector. Transmitter Audio - The RLC-Club Deluxe II provides a 600 output impedance to your transmitter audio input. - The transmitter audio is connected to pin #4 of the DB-9 connector. - If it is not already, the DB-9 plug can now be plugged into the radio port connector on the controller. - You may need to adjust the mike level pot on your transmitter to give the controller more range in its adjustments. A good rule is to set the transmit pot on the controller mid scale in its adjustment. Then set your transmitters mike level pot to obtain the correct deviation. Step #5: Adjusting the RLC-Club Deluxe II Receivers - Connect a scope probe to the audio test point for each receiver (one at a time). Connector J11 on the Deluxe II option board has test points for all of the receivers. Present a stable tone (1 KHz tone at 3KHz deviation) to the receiver and adjust the receive pot (labeled something like "RX", "Receiver" or "R2") to obtain a 1 volt peak-peak reading at the test point (0.35Vrms). Make sure your audio deemphasis jumper is present if Type 2 audio is used. Repeat this step for each of the other receivers that is installed. Transmitter Port Adjustment: Present a stable Tone or DTMF tone to the receiver that you are adjusting. Configure the controller so that one of the receivers is "connected" to the transmitter you wish to adjust (enter "000 11" and unkey or press enter to connect receiver 1 to transmitter 1. "000 12" will connect it to transmitter 2, etc.). Once the ports are connected, present a stable test tone to the receiver and do the following: Verify that your receiver's audio level is adjusted to 1 volt peak-peak at the test point (as in the "Receivers" adjustment above). Adjust the transmitter level pot (labeled something like "TX", "transmitter" or "T2") to achieve a transmitter deviation of 3KHz (to match the deviation of your test signal). Repeat for each of the other transmitters. Note that it doesn't matter which receiver is used for the transmitter adjustment, as all of the receiver levels should be identical. Step #6: Connect the Autopatch The autopatch is built into the motherboard of the RLC-Club Deluxe II, so all you have to do is plug a phone line into the RJ-11 phone jack on the controller. The phone line can be split if needed, with one line going to the controller and the other to a telephone, modem, answering machine, etc. Adjustment: Since every phone line is different, it is easiest to just adjust the autopatch until it sounds good rather than to some specific level. Use command 110 to enable the autopatch, then enter 111 from a radio port and unkey. You should hear dial tone. If you do not, either something isn't hooked up right, or the levels are turned all the way down. Entering 114 and unkeying will hang the patch up. Once you verify that you can get dial tone, hang up and have someone use a different phone line to call the controller. While the line is ringing (the "Ring" LED should light), enter 111 to make the controller "pick up the phone" and answer the call. You should then be able to use your radio to talk to the person on the phone (note that autopatch communications are usually half-duplex, unlike normal phone calls). Adjust the pot labeled "P.IN" or "Patch->Club" until the voice of the person talking on the phone sounds right to you as you listen on the radio. Adjust the pot labeled "P.OUT" or "Club->Patch" until your voice sounds right to them. If you don't have a way to contact someone to have them call the controller as suggested above, try entering 111 to get dial tone, then entering the phone number of someone that can help you set the levels. As soon as you press the first digit of the phone number, the dial tone should stop and after you enter the number, you should hear the phone ring. If either the dial tone continues or the phone won't ring, try adjusting the pot labeled "P.OUT" (or "Club->Patch). Once you are able to place the call, adjust the pots as described above. The final adjustment is the pot labeled "DTMF" or "Patch DTMF". It controls the level of the DTMF digits that the controller generates to dial phone numbers. To test it, hang up the patch, then enter 113 and unkey. You will hear nothing for a few seconds while the controller dials the number, then connects the audio so you can hear the phone ring. If it doesn't ring or you hear dial tone, adjust the DTMF pot and try again until it dials consistently. If you can't get it to dial consistently, try splitting the phone line that is connected to the controller (adapters are available at Radio Shack and many other places), plugging in another phone, and "listening in" while the controller tries to place the call. Make sure that the controller is sending the right number of DTMF digits and that they sound reasonably loud. If you don't have a phone line splitter, you can call someone using command 111 (unkey and wait for dial tone, key and enter a phone number, wait for them to answer) and use command 031 to send DTMF digits. They should be able to tell you whether the digits sound too loud or too soft. Voice Level Adjustment: - Generate a voice test message using RLC-Club Deluxe II command 036 Example: 036 001 002 003 004 005 006 007 D or unkey or - Adjust 'Voice' pot to 2 KHz deviation, this adjustment is for all transmitters. The adjustment is located next to the audio transformer and above the 'XECOM' module. Tone Generator Adjustment: - Generate a tone test sequence using RLC-Club Deluxe II Command 040: 040 2000 0001 1000 D or unkey or will generate a 1000Hz tone for 20 seconds - Adjust "Tone" pot on the RLC-Club Deluxe II to the desired deviation, 1.5KHz deviation is typical Configuring the Controller The RLC-Club Deluxe II can be configured in several ways. Although a radio with a DTMF pad can be used to enter the commands, it is recommended that you use a computer. Not only is typing in commands on a computer generally faster and less error prone than using a DTMF keypad, but if you save the configuration information on your computer, you can edit and upload it again later, without manually entering everything again. It is not difficult to do this with a text file and standard communications program (advanced users may prefer that method), but even easier is using the free QuickStart program. It runs under WindowsTM and lets you set up ID messages, timers, and many other things with a simple point-and-click interface. QuickStart may be downloaded free from our web site (on the Internet or from the CD-ROM version). See Appendix F for more information about using a computer to configure the controller. Serial Port Interfacing To configure the RLC-Club Deluxe II with a computer, you will need to connect its serial port to a computer or serial terminal's serial port. The controller's serial port is a DB-9 connector right next to the main power plug. This connection can be made with just a cable, a telephone modem, a packet TNC, or any other method that will send the serial characters back and forth (some have even used Telnet over the Internet). You can use this serial interface to monitor and program the controller. See Appendix F for more information about controlling from the serial port. RS-232 Signals and Interfacing The RLC-Club Deluxe II input and output is the RS-232 standard, 12V. The pinout is standard for a 9-pin serial connector (DCE). To connect to a terminal or computer's 9-pin serial connector, use a straight-through cable (not a null modem) with at least pins 2, 3, and 5 connected. To connect to a computer with a 25-pin serial connector, you can use a standard 9 to 25-pin converter or wire your own cable. To wire your own, connect the RLC-Club Deluxe II's pins 2, 3, and 5 to the computer's 3, 2, and 7 respectively. If you are connecting the controller to a modem, you will need to swap pins 2 and 3 relative to how you would connect it to a computer or run your cable through a null-modem adaptor. This is because master and slave devices (DTE and DCE devices) are wired differently. When hooking the controller and a modem (both slave devices) together, you have to adjust accordingly. The following chart summarizes the four different types of cables you may need. Controller to Computer or Modem Cable Controller DB-9 Description Computer DB-9 Computer DB-25 Modem DB-9 Modem DB-25 2 Data Out of Controller 2 3 3 2 3 Data Into Controller 3 2 2 3 5 Ground 5 7 5 7 Using a Telephone Modem There are two ways to control the RLC-Club Deluxe II over the phone line. If the RLC-Club Deluxe II has an autopatch, you can control it using the reverse autopatch and entering commands with the telephone's DTMF pad. This works well for small changes, but if you want to do a lot of programming remotely, it is nice to do it with a computer. You can do this by putting an external modem on the controller and calling it from a modem attached to your computer (either internal or external). The modem should be connected to the controller's serial port - it has nothing to do with the autopatch. You can run separate phone lines to the autopatch and the modem or split a single phone line and use it for both (one at a time, of course). Most modems have two RJ-11 jacks; you can connect "line" to the incoming phone line and "phone" to the controller. You can either have your computer call the modem and have it answer or you can have the controller call your computer. If you want to call the controller and have the modem answer and you plan to use the reverse autopatch, you will have to have a way of determining which one answers the phone. The most common way is to set the modem to answer on three rings, then to change the reverse patch setup to make it answer on either 1 or 5 rings (you can do that with a couple of macros). Whichever one answers first will make the connection. It is also possible to use a call routing interface (similar to a fax switch) to detect whether you are calling with a modem or not or to make you press DTMF digits to get to the modem. The other option is to make the controller call your computer. This is usually done by sending a DTMF command to the controller to tell it to call you, which means you can't connect with the modem if there is a problem with your receiver. The DTMF command usually calls a macro that sends "ATDT " to the modem (using command 162). The advantage of having the controller call you is that it doesn't conflict with the reverse patch and since the phone number is hard coded in the macro, you can be sure that no one else will call the controller with their modem and get control (since the modem can be set not to answer). If you plan to use this method, you may have to turn off line feed sending with command 060, since most modems will abort the dialing process if they receive any more serial characters after "ATDT" and the controller usually sends both a carriage return and line feed at the end of each line. Before connecting the external modem to the controller, you should connect it to your computer or serial terminal and enter some setup commands. Even if you already have a modem in your computer, you need to hook up the modem that will go on the controller to set it up. You can use a standard modem cable for this, or build one according to the chart below. Note that this cable is different than the one that you will use between the controller and the modem, even if the connectors are the same (pins 2 and 3 are swapped). Computer to Modem Cable Computer DB-9 Computer DB-25 Description Modem DB-9 Modem DB-25 3 2 Data Out of Computer 3 2 2 3 Data Into Computer 2 3 5 7 Ground 5 7 You will not need to connect the modem to the phone line to enter these setup commands. Load your communications program and set the comm port to talk to the external modem (it will probably be set for the internal modem when you start). Enter "ATZ" (without the quotes) and press enter. You will see an "OK" response if everything is hooked up right. Then enter (without the quotes, pressing enter after each command): "AT&F" to set everything to factory defaults. "ATS0=3" to make the modem answer after 3 rings or "ATS0=0" to keep the modem from answering at all. "AT&K0" to disable local flow control (the controller doesn't support it). "ATE0" to disable local echo. "ATQ1" to keep the modem from sending result codes. "AT&W" to store the settings to the modem's non-volatile memory. If you are unable to disable your modem's flow control in software, you may have to put jumper wires between some of the pins on its DB-25 connector to fool it. Shorting pins 4 and 5 together and pins 6, 8 and 20 together should fool the flow control into working. Communications Parameters After connecting your terminal, computer, or modem (either packet or telephone) to the RLC-Club Deluxe II, you need to make sure that the communications parameters for the controller and the communications program on your computer. The default settings for the RLC-Club Deluxe II are 9600 N81: Baud Rate 9600 Parity None (N) Word Length 8 Stop bits 1 Handshaking None You can change the baud rate the RLC-Club Deluxe II uses with command 024. If you are using a modem, you may be able to set the baud rate that the modem uses to communicate with the controller to be different than the speed at which it connects to the other modem. In other words, a 2400 baud modem may be able to connect to the controller at 9600 baud and to the other modem at 2400 baud. Troubleshooting If you can't get the connection between your computer or serial terminal and the controller to work, there are several things you can check. Make sure that the serial cable is properly connected between a serial port on your computer and the serial port on the controller and that the controller is powered up. Load your communications software (Procomm, Telix, the Windows terminal program, etc) and make sure it is set for the right comm port and baud rate. Whenever you reset the controller (or cycle the power) it will output a serial message you should see on the screen. Pressing enter should get you a "DTMF>" prompt that indicates that it is ready to accept the same commands you might enter from a radio's DTMF pad. If neither the reset message or pressing enter gets any response, double check that you have the comm port set right. Then disconnect the serial cable from the controller and short pins 2 and 3 on that end of that cable together (those are the data in and out pins). Then type on the keyboard and see if what you type shows up on the screen - it should (even with echo turned off). If you quit shorting those pins, the data should not show up on the screen. If you cannot get the data to show up on the screen by shorting those two pins, the problem is either in the computer or the cable (the controller isn't even hooked up). The most common problem is having the comm port set wrong - try all the settings. Then check your cable again. If you still can't get it to echo, unhook the cable from the computer and try shorting pins 2 and 3 together on the serial port right at the computer, eliminating the cable as a possible problem. Again, you should see whatever you type appear on the screen. If you don't, the problem is in the computer or how you have the comm program set up. Once you get it to echo with the jumper wire at the computer, hook up the cable to the computer and try the jumper wire at the other end of the cable. If that doesn't work, the problem is in the cable. Finally hook the cable back up to the controller and try again. If the characters echo but don't work, you may be in 7 bit mode rather than 8 bit mode. If all else fails, write down how your cable is wired and call Link Communications for help. After you get it working, see Appendix F for information about controlling from the serial port. Reset and Power Up If you have a transmitter connected to port 1, you should hear "controller ready" when you turn the power to the controller on. This message is sent whenever the controller goes through its reset routine, which happens in the following instances: 1) Power has just been turned on 2) The user has pressed the "RESET" button 3) The Reset command has been executed (command 035) 4) The controller's watchdog timer has expired. This is an internal protection timer that can reset the controller automatically if something goes wrong in the software. When the controller resets, it does not lose any of the things you have programmed into it, like your IDs and timer settings. It does hang up the autopatch, turn off the HF remote base and a few other things, to make sure they are ready for use. It then calls a macro that makes it speak "controller ready". If you want it to speak something else or do other things when the controller resets, look into changing how the "reset macro" is programmed in Chapter 8. For information about resetting all of the variables in the controller back to factory settings, see Appendix D. Entering Commands It is really easy to enter commands on the controller. If you have a receiver and transmitter hooked up and adjusted, key up, press "026" on your DTMF pad, and unkey; the controller will tell you the time. Most of the commands in the controller are like this - you just have to enter the command name on your DTMF pad and unkey. If you have a computer hooked up to the serial port, you can type "026" (without the quotes) on your computer and the controller will print the time on the screen and speak it on the transmitter connected to port 1. Entering More Digits after the Command Name: Some of the commands take more digits; if you want to change the time, try "025 HH MM X" where HH is the hour, MM is the minute, and X is 0 if it is AM and 1 if it is PM. Command 025 needs more digits after the command name so it knows what to set the time to. The description for each command in this manual will tell you if you need to enter more digits after the command name or not. Command Names: When you first receive the controller (or right after everything has been set to factory settings by reinitializing - see Appendix D), all of the command names will be three digit numbers, 000 to 999. Command 26 must be entered as "026"; the leading zero is needed to make the command name three digits long. You can change any or all of the command names if you want to. You can make them almost any combination of DTMF digits up to six digits long. Normally you will want to avoid using the digit 'D' in any of the command names. For more information about command names, see Chapter 5. Unkey or Press 'D' to Execute: After entering a command name and any other digits that command might require, you can tell the controller to go ahead and execute the command in several ways. If you are entering the command from a radio, you should normally just unkey. The controller will execute the command and speak a voice message to tell you what it did (except for a few commands that don't have voice messages). There may be times when the receiver's squelch is too loose and is stuck open or when someone sits on their mike when the controller won't be able to tell when you unkey. At those times, you need another way to make the commands execute. That is the purpose of the "force-execution" digit. It tells the controller to execute the command right away. It is normally set to the digit 'D'. You should not use it when it is not necessary, because as soon as you release the 'D', the controller will start speaking the command response, even if you haven't unkeyed yet, and you won't hear the first few words of that response. When you are entering commands from a computer or serial terminal, you can tell the controller to execute a command in two ways, either by entering a 'D' or pressing the enter key. When entering commands from the reverse autopatch, you can't unkey or press 'D' (on most phones), so there is another way, called "timed execution". When timed execution is turned on, you can just enter a command and wait for a few seconds and the controller will execute it. For more information about the force-execution digit and timed execution, see command 078. Error Messages If errors are encountered while programming the user can use this page as a reference to locate what caused the errors. Most errors are caused due to the command formats not matching what the controller is expecting. The user can change what an error macro speaks by changing the contents of the error macros. The error macros are numbered 200..219. Refer to the Macro programming section of the manual the modify and program selected macro positions. Error 200 - Command Name Length not Matched If the controller can not locate the command name this error is called Error 201 - Too few data digits entered If the controller expects more digits on a command than entered you will get this error Error 202 - Too many data digits entered If the controller expects less digits on a command than entered you will get this error. You can also get this error if you try to put more commands into a macro than it will hold. Error 203 - Invalid number of data digits entered If a command expects increments of 3 digits (Speaking a Voice Word) and you give it a wrong number of digits you will get this error. Error 204 - Execution blocked from this port The command you are trying to execute has been blocked from being executed. Error 205 - User level to low to execute this command The command you are trying to execute is at a higher user level than your assigned level. A lower level user can not execute commands assigned to a higher level. Error 206 - This macro is reserved for internal use Do not edit, erase or alter this macro position. It is for internal use only. Error 207 - Command executed OK When a command executes correctly (User and/or macro execution) this macro is called. Error 208 - Internal error just occurred If you get this error please contact Link Communications, Inc. with a detailed description on how you made this error occur. Error 209 - Macro depth limit reached This error occurs if a macro is calling itself or you have a macro call another macro for six levels. For example, Macro 300 calls macro 301 calls macro 302 etc. for 6 levels. Error 210 - Invalid data value entered This error occurs if a value is entered into a command that is invalid. Error 211 - Command does not exist This error is similar to error macro 200 except it occurs when a listed command that is not enabled, is called. The command name exists but the command does not exist. Error 212 - Bad Autopatch Number You tried to enter a number in the autopatch that is invalid or blocked. Error 213 - General Autopatch error There is a general autopatch error that just occurred. Refer to the command you are executing and verify the format or the autopatch is not configured (See Command 110) Error 214 - User requested is disabled This error is encountered if a user that is disabled tries to log-on to the system. A nice voice message indicating the user is not enabled is a good use for this macro. Error 215 - Digital Voice Recorder (DVR) is busy This error is spoken if the DVR is currently busy and the requested DVR function can not be processed. This error will also occur on RLC-Club or Deluxe2 with V2.10 or later if try to record and none of the ports in the audio routing mask are eligible to record. Error 216 - Macro is full This error indicates a macro position if full. No more commands can be added to the specific macro. Error 217 - HF Error This error indicates that the last digits entered were not a valid HF command. It will usually occur when you are in HF mode (see command 198). You will probably want to disable this error message by erasing the contents of macro 217: "055 217" to avoid getting an error message every time you enter an HF command wrong. Error 218 - Reserved Error 219 - Reserved How to Configure a Port as a Repeater The RLC-Club Deluxe II controller can support a repeater on all ports. This allows multiple stand alone repeaters to operate at the same time, on the same controller (with their own courtesy beeps, hang time, IDs, etc.). We will describe how to configure and setup port one as a repeater. Simply follow this example to configure any additional port as a repeater. Configure the port's as a repeater: 000 1 1 D or unkey or This command connects port 1's receiver to port 1's transmitter. When you do this ports 1 receiver will cause a PTT on port one's transmitter. You could call this putting it into repeater mode. This is the default for port 1, but not for the other ports. Configure the port's Hang timer: 020 13 200 D or unkey or This command sets the hang timer to 200 * 10mS = 2 seconds. Configure the port's ID message: 085 1 1 D or unkey or This command enables the ID for port 1. The ID timer defaults to 10 minutes. Programming in your ID: Macros 220, 226, 232, 238, 244 and 250 are set aside for your initial ID, rotating IDs and impolite IDs. See Chapter 11 and command 064 for more information about programming IDs. Note: the IDs will automatically be sent to the right ports, so don't worry about the "message routing variable". Configure the courtesy beep: The courtesy beep is already configured and stored in Macro 256. When you execute Command 256 you will get a "beep" at 500 Hz for 200mS. To program your own beeps refer to Chapter 6, especially Command 040. Configure the time-out timer: The time-out timer defaults to 3 minutes and is programmable with Command 020. You can change the time out message by re-programming macro 118 and the time out clear message by re-programming macro 125. Now your port is configured as a repeater port. Example 1-1: Configuring a Port as a Repeater or Link Repeaters and links indicate how a port is configured. Repeater A repeater is defined as a port that loops the ports receive audio out the ports transmitter. When the receiver becomes active, the transmitter of the same port should go active. When the receiver goes from active to inactive, a courtesy beep and hang time will be generated. It is required that the radios on a repeater port be only full duplex. To convert a port into a repeater port the following command is used: 000 X X Where X and X are the same number indicating what port the repeater is on When the port is looped back the courtesy beep is on port 'X', IDs are started and routed to port 'X'. Time-out timers, if enabled, are running when port 'X's receiver is active. Link A link is defined as a port that does not loop the ports receive audio out the ports transmitter. When the receiver becomes active, the transmitters of all connected ports should go active except its own port. A link can be either half or full duplex. Full duplex links allow the ports transmitter to operate without affecting the receivers function. Half duplex links are similar to full duplex with the exception that the transmitters operation causes the receiver to be shut-off. To convert a port into a link port the following command is used: 002 X X Where X and X are the same number indicating what port the link is on Monitoring a port It is handy to monitor a connected port's receiver without keying the ports transmitter. Because the controller has full duplex ports, the controller can be monitoring another ports receiver while the monitoring port continues to have a conversation. To monitor a port from another port the following command is used: 001 X Y Where X is the port doing the monitoring of port Y, Y is the port being monitored Example 1-2: Configuring a Port's COR/PL Polarity In order for the controller to recognize a port's receiver: The receivers COR signal is used to tell the controller when the receiver is active An external decoder can be used to decode a receivers CTCSS 'PL' tone for controller access Each one of these signals can be either high when active, or low when active. What 'High' really means A 'High' COR or PL signal indicates the input goes from a ground (0Volts) to either an open (High Z) or to a voltage above 4 volts. The controller has protection that safely allows 'High' voltages up to 15 volts without any damage to the controller. With a voltage meter you will read a voltage on the COR and PL inputs with nothing connected. This indicates the input is 'Pulled Up'. An input is 'pulled up' so the controller always has a voltage on the COR and PL inputs. This keeps the inputs from floating between 'High' and 'Low' If you do not have a receiver connected to the controller, the controller will treat the COR and PL active high. It is very important to tell the controller the COR and PL inputs are active low if nothing is connected to the port. What 'Low' really means A 'Low' COR or PL signal indicates the input goes from an open or a voltage above 4 volts to ground (0Volts). Ground does not mean open or nothing connected to a pin. Ground means just that, ground or the same voltage and impedance as your power supply (-) terminal. The controller has protection that safely allows 'High' voltages up to 15 volts without any damage to the controller. If you do not have a receiver connected to the controller, the controller will treat the COR and PL active high. It is very important to tell the controller the COR and PL inputs are active low if nothing is connected to the port. Polarity Control Once you have determined the ports COR and PL polarity you need to configure the controller to accept the correct polarities. The controller defaults to active 'Low' on both the COR and PL inputs of all ports. If your receivers are already 'Low' you do not need to change the configuration. If your polarity is active 'High', you need to execute Command 013 and tell the controller the correct polarity. Active 'High' COR and active 'Low' PL (Or no PL at all) on Port 1 is configured as: 013 1 0 D or unkey (Refer to command 013 for more information) This configures port 1 for active 'High' COR and active 'Low' PL Troubleshooting the Controller No LED's when the RLC-Club Deluxe II is powered up Check for +12 Volts at Power Connector Make sure that the +12 Volts is connected correctly: Center of Plug is (+), Shield is (-). Check for bad or blown fuse No Audio at Test Bus Check for main system power Is there a valid COR signal present on the receiver: (Default: Active Low) Have audio at the test bus, but not on the transmitter Are the output audio pots adjusted correctly Is the transmitter connected to the controller's audio output: Pin 4 on the DB-09 Is the PTT connected to the controller: Pin 3 (Low on Transmit) The Voice Synthesizer seems muffled Turn down the pot marked 'Voice' When I connect my COR, the RLC-Club Deluxe II will not accept it My COR is set for active Low, does the COR go to ground when active My COR is set for active High, does the COR go to ground when inactive Can the COR sink (2mA) when active Does the 5V pull-up resistor conflict with your radio - Motorola R-100 Repeaters are susceptible to this - Open collector the driver on R-100 repeaters When I connect my serial terminal, I do not get any data Is your terminal's baud rate set to 9600,N,8,1 Are all the RS-232 TX and RX and ground wires connected The controller requires all RS-232 signals (TX/RX/Ground) be connected Chapter 2: Port Connection Commands This chapter deals with the commands used in connection and control of the radio ports. The areas dealt with in this chapter are: Radio port connections Receiver access control COR and PL polarity control Transmitter PTT control "Connected Ports" In this chapter you will often see references to ports being "connected". When two ports are connected, they hear each other (the COR from each port will activate the PTT on the other, and the audio from each will be transmitted out the other). All of the radio ports on the controller can work independently, or they can be connected together in any combination. If all of the ports are connected to each other, the whole controller works as one unit, with audio received on any of the receivers going out all of the transmitters. You can make a port a repeater by connecting it to itself with command 000, so it hears (repeats) its own audio. When using a port for a link or remote base, it should not be connected to itself; when audio is received on a remote it should not be transmitted back out the remote. Instead, the audio from the remote should be transmitted out of a repeater, and the audio from the repeater should go out the remote. So the repeater port should be connected to itself (to make it a repeater) and the repeater port should be connected to the remote base port (so they can hear each other). The remote base port should not be connected to itself. To turn the remote off, you can disconnect it from the repeater port and they will no longer hear each other. It is also possible to make a one-way connection, that is to have one port monitor another. If you make the repeater port monitor the remote base port, the people listening to the repeater would be able to hear the remote base, but the remote base would not transmit the audio received on the repeater. In this case we could say that the remote receiver is connected to the repeater transmitter, but that the repeater receiver is not connected to the remote transmitter. When you make an autopatch call, the controller automatically connects the radio port that made the call to the autopatch port. It also may connect to the patch any ports that were connected to (or monitoring) the port that made the call, to avoid one-way conversations. It also connects the autopatch to itself (to keep it off hook when you unkey) even though it doesn't get it's own audio looped back (there is a special case in the code to break that audio connection). There are a variety of commands to provide you the flexibility to configure the port connections any way you might want them. To minimize confusion, use them as follows: Command 000 - to configure ports as repeaters. Command 002 - to take ports out of repeater mode (opposite of command 000). Command 008 - to connect ports together. Command 068 - to disconnect ports from each other. Command 001 - to make one port monitor another port. Turning a Repeater Off There is more than one way to turn a repeater off, each of which has advantages and disadvantages. For this example, we will assume that you have a repeater connected to port 1. One option is to disable the repeater transmitter. This will keep the transmitter from coming up for any reason. It will not repeat audio, it will not ID, it will not send any messages that may be caused by the scheduler (like speaking the time on the hour) or any alarm messages, and if a remote is connected, it will not send the audio from that remote. The receiver will still work normally. You can still use the receiver to turn the repeater back on or enter any other commands, and if you have a remote base port connected to the repeater port, your receiver's audio will still go out the remote. The repeater transmitter can be disabled by entering "155 10". Another option is to disable the repeater's receiver. In this case, the receiver will not cause any transmitters to key up and no audio that is received by that receiver will be transmitted out the repeater or any remotes. The repeater transmitter will continue to work normally. It will still ID (when it needs to), send scheduled and alarm messages, and if a remote is connected, it will still send the audio from that remote. You can disable port 1's receiver by entering "005 10". You can also choose whether or not to allow commands to be entered when the receiver is disabled with command 005. Entering "005 100" will make the controller ignore any commands that are entered on that receiver. This may be useful for keeping someone who is trying to break into your controller from getting in. It will also keep you from doing anything from that receiver - even turning it back on. If you set command 005 this way and disable the receiver, you will have to turn the receiver back on from another receiver on the controller, from the reverse patch, or from the serial port. If you enter "005 101" instead, the disabled receiver will still not cause any transmitters to key, but you will be able to enter commands on that receiver. If you enter "005 110", the repeater will continue to work but it won't accept any commands, including the command to turn it back on. The final method for disabling a repeater is to disconnect the repeater port from itself by entering "002 11" (or from itself and any remotes that might be connected: "061 1"). This does not disable either the repeater receiver (it can still receive commands) or the transmitter (it can still send IDs and scheduled messages), but it keeps the repeater receiver from being heard on any transmitters and keeps the transmitter from sending the audio from any receivers. This is the best method for most systems. Whichever of the methods you choose to turn your repeater off, you will probably want to program a macro to do it with a simple DTMF code and program another macro to turn it back on. An example of the final (recommended) method is shown below. Entering "A1" should shut the repeater off and "A2" should turn it back on. 055 500 ; erase macro 500 056 500 036 411 354 ; speak "repeater off" 056 500 038 ; be quiet for the rest of this macro 056 500 061 1 ; disconnect all ports from port 1 010 500 A1 ; name the repeater off code "A1" 055 501 ; erase macro 501 056 501 036 411 358 ; speak "repeater on" 056 501 038 ; be quiet for the rest of this macro 056 501 000 11 ; make port 1 a repeater again - this will not reconnect any remotes 010 501 A2 ; name the repeater on code "A2" 000: Connect Ports This command allows you to "connect" radio ports to each other. When two ports are "connected," audio received by each port will be transmitted by the other. It is also used to put a port into "repeater mode," by connecting that port to itself ("000 11" makes port 1 a repeater, for example). More than two ports can be connected at a time. Also see command 008. <000> x x Make port 'x' a repeater <000> x y Connect port 'x' to port 'y' <000> x y z Connect ports 'x', 'y' and 'z' <000> x..z Connect all ports 'x' through 'z' Parameters: - 000 is the default command name - X, Y and Z are the port numbers to connect (use '*' for the current port, see Appendix L) Default: - Port 1 defaults as a repeater - Port 2 defaults as a link - Port 3 defaults as a link - Port 4 defaults as a link - Port 5 defaults as a link - Port 6 defaults as a link - Port 7 defaults as a autopatch Notes: If you want a one-way connection, where port A can monitor port B but port B can not hear port A, use command 001. This command makes the connection both ways. There is no need to enter both "000 12" and "000 21", for example; either command will make the connection. When more than two ports are listed, all combinations of those ports are connected. For example "000 X Y Z" connects X to Y, X to Z and Y to Z. If a port is listed more than once, it put into repeater mode. For example, "001 1123" will set up port 1 for repeater mode and connect all combinations of ports 1, 2 and 3 (connecting 1 to 2, 1 to 3 and 2 to 3). It may be better to use command 008 instead of command 000 in some cases. See command 008 for more information about the differences. Example 1: Connect Port 1 to Port 2 000 1 2 D or unkey or Response: Voice Response: "Connect 1 2" Example 2: Want port 2 as a repeater port 000 2 2 D or unkey or Response: Voice Response: "Connect 2 2" 001: Monitor Ports This command sets up one-way connections so one radio port will monitor the audio received on other radio ports. It can be used to monitor a weather receiver, shuttle audio receiver or other audio source that you don't want to transmit back to. When audio is available from two connected receivers at the same time, the controller normally mixes the audio from the two sources. If you want one of them to be muted instead, see command 006. <001> x y Make port 'x' monitor port 'y' <001> x y..z Make port 'x' monitor ports 'y' through 'z' Parameters: - 001 is the default command name - X is the port that will be transmitting the audio from port Y (use '*' for the current port, see Appendix L) - Y and Z are the ports (receivers) being monitored by port X (use '*' for the current port, see Appendix L) Default: - Port 1 defaults as a repeater - Port 2 defaults as a link - Port 3 defaults as a link - Port 4 defaults as a link - Port 5 defaults as a link - Port 6 defaults as a link - Port 7 defaults as a autopatch Notes: Setting a port to monitor itself puts it into repeater mode, just as command 000 does. "001 X Y" not only makes transmitter X monitor receiver Y, it disconnects transmitter Y from receiver X. Because of this, "001 X Y" followed by "001 Y X" does not make a two-way connection (command 000 can be used for that). To mute the audio from a port you are monitoring when other audio is received (to mute the weather receiver when someone keys the repeater, for example), see command 006. Example: Make port (transmitter) 1 monitor port (receiver) 2 <001> 1 2 D or unkey or Response: Voice response "1 MON 2" 002: Disconnect Ports This command allows you to disconnect radio ports from each other (so audio received on one will not be heard on the other). It can also be used to take a port out of repeater mode (so you can use it for a link, remote base, etc.), by disconnecting it from itself. <002> x x Take port 'x' out of repeater mode <002> x y Disconnect port 'x' from port 'y' <002> x y z Disconnect ports 'x', 'y' and 'z' <002> x..z Disconnect all ports 'x' through 'z' Parameters: - 002 is the default command name - X, Y and Z are the ports to disconnect (use '*' for the current port, see Appendix L) Default: - Port 1 defaults as a repeater - Port 2 defaults as a link - Port 3 defaults as a link - Port 4 defaults as a link - Port 5 defaults as a link - Port 6 defaults as a link - Port 7 defaults as a autopatch Note: If you want to break all of the connections to a port, check out Command 061. This command breaks the connection both ways. There is no need to enter both "002 12" and "002 21", for example; either command will break the connection. When more than two ports are listed, all combinations of those ports are disconnected. For example "000 X Y Z" disconnects X from Y, X from Z and Y from Z. If a port is listed more than once, it will be taken out of repeater mode. For example, "002 1123" will take port 1 out of repeater mode and disconnect all combinations of ports 1, 2 and 3 (disconnecting 1 from 2, 1 from 3 and 2 from 3). Example 1: Disconnect Port 1 from Port 2: <002> 1 2 D or unkey or Response: Voice response "No Connect 1 2" Example 2: Port 2 is currently a repeater port. You want to disable repeater mode (so you can use it for a link): <002> 2 2 D or unkey or Response: Voice response "No Connect 2 2" 061: Disconnect all Ports from a Radio Port This command allows you to disconnect all of the other radio ports from one radio port with one command. Please note that if you execute this command for a repeater port, it will disconnect it from itself, breaking it out of repeater mode (command 068 is similar but doesn't do that). If you only want to break some of the connections to a port, see commands 001 and 002. <061> p Disconnect all ports from port 'p' <061> p..p Disconnect all ports from each of ports "p..p" Parameters: - 061 is the default command name - P is the port to disconnect all other ports from (use '*' for the current port, see Appendix L) Shortcut: If you want to break all of the connections to several ports, list all of them. For example: 061 1234567 D or unkey or breaks every connection in the whole crosspoint. Example: Disconnect all other ports from Port 1 <061> 1 D or unkey or Voice Response: "1 Clear" 068: Disconnect all Ports (but leave repeaters) This command allows you to disconnect all of the other radio ports from one radio port with one command. It will not disconnect ports from themselves (like command 061 does). <068> p Disconnect all ports from port 'p' <068> p..p Disconnect all ports from each of ports "p..p" 008: "Smart" Connect Ports This command is similar to command 000; it allows you to "connect" ports, so that audio received on each port will be transmitted on the others. It is "smarter" than command 000 in that it tries to avoid situations where only one side of a conversation is heard on some transmitters (hereafter called "one-way conversations"). It does this by automatically connecting other ports according to the following rules. When you "smart" connect ports X and Y: Rule #1: X and ports that are connected to X will be connected to Y and ports that are connected to Y. Rule #2: Ports that X is monitoring (see command 001) will be monitored by Y and ports connected to Y. Likewise, ports that Y is monitoring will by monitored by X and ports connected to X. Rule #3: No port will be connected to itself (put into repeater mode) even if X=Y (use command 000 for that). This rule overrides the above rules in some cases. In general, you can think of this command as letting port X in on whatever port Y is doing and port Y in on whatever port X is doing. <008> x y "Smart" connect port 'x' to port 'y' Parameters: - 008 is the default command name - X and Y are the port numbers to "smart" connect (use '*' for the current port, see Appendix L) About the Following Examples: The following examples show how this command changes the "crosspoint" in various situations (see command 009 for more information about the crosspoint). To save space, only the number of ports needed for each example are shown; your controller may have more or less ports than the example shows. Example #1: Basic Connections Work Like Command 000 Port 1 is a repeater. Port 2 is a link. TX> 1 2 RX> 1 X 2 "Smart" connect ports 1 and 2 by entering "008 12". TX> 1 2 RX> 1 X X 2 X Ports 1 and 2 get connected just as they would if command 000 had been used. Example #2: Ports Connected to X or Y get Connected to the Other Ports 1 and 2 are repeaters. Port 3 is a link. Ports 2 and 3 are connected to each other. TX> 1 2 3 RX> 1 X 2 X X 3 X "Smart" connect ports 1 and 2 by entering "008 12". TX> 1 2 3 RX> 1 X X X 2 X X X 3 X X Port 1 gets connected to both ports 2 and 3. Example #3: Ports Monitored by X or Y get Monitored by the Other Ports 1 and 2 are repeaters. Port 3 is a link. Port 2 is monitoring port 3. TX> 1 2 3 RX> 1 X 2 X 3 X "Smart" connect ports 1 and 2 by entering "008 12". TX> 1 2 3 RX> 1 X X 2 X X 3 X X Port 1 gets connected to port 2 and monitors port 3. Example #4: Ports Monitoring X or Y are not Affected Ports 1 and 2 are repeaters. Port 3 is a link. Port 3 is monitoring port 2. TX> 1 2 3 RX> 1 X 2 X X 3 "Smart" connect ports 1 and 2 by entering "008 12". TX> 1 2 3 RX> 1 X X 2 X X X 3 Port 1 gets connected to port 2. There is no change with port 3. About the Following Examples: If ports are always connected using this command (008) and disconnected using command 068, the controller should never get into a state where it transmits only one side of a conversation. If you use command 000, 001 or 002, it is possible to configure the port connections so that only one side of a conversation can be heard on one or more transmitters. For example, port 1 might be connected to ports 2 and 3 without connecting ports 2 and 3 to each other (by entering "000 12" and "000 13"). Only one side of a conversation between port 1 and port 2 would then be heard on port 3. If you do use commands 000, 001 or 002 and set up such a one-way conversation, then use command 008, it will try to preserve the way things are configured, but will sometimes "fix" the port connections so that everyone can hear each other. Example #5: Command 008 Tries to Preserve Existing Configurations Ports 1 and 2 are repeaters. Port 3 is a link. Port 1 is connected to ports 2 and 3, but they are not connected to each other (possibly by entering "000 12" and "000 13"). TX> 1 2 3 4 RX> 1 X X X 2 X X 3 X 4 "Smart" connect port 1 with port 4. Rule #1 says, "Ports 1, 2 and 3 will be connected to port 4." TX> 1 2 3 4 RX> 1 X X X X 2 X X X 3 X X 4 X X X Note that ports 2 and 3 are still not connected to each other (command 008 preserved the way it was previously set up). Example #6: Repeating Command 008 May Connect More Ports Continuing the previous example, "smart" connect port 1 with port 4 again. Rule #1 now says that, "Ports 1, 2, 3 and 4 will be connected to ports 1, 2, 3 and 4." TX> 1 2 3 4 RX> 1 X X X X 2 X X X 3 X X X 4 X X X Ports 2 and 3 are now connected to each other. Note that executing "008 14" a second time connected ports that it left alone the first time. That could be seen as an advantage (it "fixed" the one-way conversations) or a disadvantage (it "messed up" the original configuration). Example #7: "Smart" Connecting a Port with Itself Fixes One-Way Conversations Ports 1 and 2 are repeaters. Port 3 is a link. Port 1 is connected to ports 2 and 3, but they are not connected with each other. TX> 1 2 3 RX> 1 X X X 2 X X 3 X "Smart" connect port 1 with itself by entering "008 11". Port 1 is connected to ports 2 and 3, so Rule #1 reads, "Ports 1 2 and 3 will be connected to ports 1, 2 and 3." Rule #3 says that this will not change port 3 into a repeater. TX> 1 2 3 RX> 1 X X X 2 X X X 3 X X Ports 2 and 3 get connected together, "fixing" the one-way conversation. In general, connecting a port to itself "fixes" any one-way conversations among ports that are connected to it. Summary of Command 008: Command 008 can make avoiding one-way conversations much easier. If you use it to make all port connections and use command 068 to break them, everything works in very straightforward ways. If you use command 001 (which always sets up a one-way conversation) then command 008, command 008 adds one-way connections to the new ports you connect. If you use commands 000 and 002 and manually set up one-way conversations (rather than using 008 and 068 which automatically avoid them) and then use command 008, command 008 will try to logically extend the way you have things configured. In some cases, it will "fix" the one-way conversations as a side effect of connecting the ports (like example #6). To avoid confusion, it is probably best to use command 008 to make all port connections and avoid the complicated scenarios. Notes: The combination of command 008 and the ability to enter a '*' as a port number to represent the port that entered the command makes it possible to program a macro that will "connect me to ...". For example: 010 500 AB ; name this macro "AB" 067 500 01 0 ; accept exactly one data digit 053 500 008 * ; smart connect current port to specified port ; the last digit will be specified by the user Now entering "AB3" will "smart connect" the port from which the command was entered to port 3. 003: Recall Which Transmitters A Receiver Is Connected To This command allows you to find out which transmitters will send the audio received on the specified receiver. <003> x Recall Receiver Connections Parameters: 003 is the default command name. This command finds what transmitters are connected to receiver 'X'. X is the receiver to recall the connections to (use '*' for the current port, see Appendix L) Default: - Port 1 defaults as a repeater - Port 2 defaults as a link - Port 3 defaults as a link - Port 4 defaults as a link - Port 5 defaults as a link - Port 6 defaults as a link - Port 7 defaults as a autopatch Example: Receiver 1 is connected to transmitters 2 and 3 <003> 1 D or unkey or Response: Voice Response "1 Connect 2 3" 004: Recall Which Receivers Are Connected to a Transmitter This command allows you to find out which receivers will cause the specified transmitter to key and send the received audio. <004> x Recall Transmitter Connections Parameters: 004 is the default command name. This command finds what receivers are connected to transmitter 'X'. X is the transmitter to recall the connections to (use '*' for the current port, see Appendix L) Default: - Port 1 defaults as a repeater - Port 2 defaults as a link - Port 3 defaults as a link - Port 4 defaults as a link - Port 5 defaults as a link - Port 6 defaults as a link - Port 7 defaults as a autopatch Example: Receivers 1 and 2 are connected to transmitter 3 <004> 3 D or unkey or Response: Voice response "3 Connect 1 2" 009: Recall Controller's Entire Audio Crosspoint This command allows you to check the audio crosspoint conditions on all radio ports on the controller. This command will check the connected conditions and both show the crosspoint map on the RS-232 serial port, and will speak the conditions out the port that DTMF requested the conditions. <009> Parameters: - 009 is the default command name. Voice Response: The voice response will only speak if a receiver is connected on the selected port. If a receiver is connected to a port's transmitter, the controller will speak "RX connect TX" where RX and TX are the port numbers of the receiver and transmitter, respectively. Voice Format: 1 Connect 2 Connect 3 Connect 4 Connect 5 Connect 6 Connect 7 Connect Serial Response: TX 1 2 3 4 5 6 7 1 . . . . . . . 2 . . . . . . . 3 . . . . . . . RX 4 . . . . . . . 5 . . . . . . . 6 . . . . . . . 7 . . . . . . . 005: Set Receiver and DTMF Decoder Conditions This command lets you specify whether a user must have PL (CTCSS) to key up your repeater or whether it can be keyed with just carrier, among many other options. By selecting a "mode" from the table below, you can tell the controller what conditions must be met for a receiver to be considered active, that is to make it key connected transmitters. Each mode is described in detail on the following page. This command also lets you specify the conditions the controller requires to be met for DTMF tones to be processed. Normally they are the same as the conditions for activating the receiver, but you can set them to be different. You can, for example, allow access to your repeater with just carrier, but require PL to enter any commands (enter "005p13"). Or you can require PL to access the repeater but provide a PL override command that can be entered with only carrier (enter "005p31). The controller will mute DTMF digits (if you have that option enabled, see command 007) regardless of the conditions you have set to execute commands. <005> p Recall settings <005> p y Set receiver's access mode <005> p y z Set receiver's and DTMF decoder's access modes Parameters: - 005 is the default command name. - 'p' is the port number (1..6) - 'y' is the receiver's access mode - 'z' is the DTMF decoder's access mode. If not specified and the receiver's access mode is not zero, it will automatically be set the same as the receiver's access mode. To set 'z' to zero, all three digits of "p y z" must be entered. Defaults: - Receiver defaults to mode 1 on all ports. - The DTMF decoders default to mode 1 on all ports except port 1, where it is "always active". That should be changed once the COR polarity for port 1 is set up by entering "005 111". - If a port is connected to an RLC-ICM, use Mode 1. Mode Definitions: Mode Definition 0 No Access 1 COR Access 2 PL Access 3 COR and PL Access 4 COR or PL Access 5 Always Active Description of Modes: Mode 0: The receiver is effectively disabled; even if the carrier and/or PL is received, the controller will ignore that receiver and will not key connected transmitters. If you are going to do this, you need to have another way to enter commands to re-enable DTMF access (reverse patch, serial port, another radio port, scheduler...). Mode 1: The controller will respond to the COR signal, allowing access with carrier. The PL signal is ignored. Mode 2: The controller will respond to the PL signal. The COR signal is totally ignored. This mode may cause very long squelch tails since PL decoders are generally slow to recognize when the PL tone goes away (see mode 3). Mode 3: Both COR and PL must be active at the same time for the controller to respond to the receiver. Repeaters that require PL usually use this mode because it eliminates the long squelch tails often heard when using mode 2. Typically, when someone keys a repeater with PL, the receiver's COR signal will go active first. The controller will ignore it for the moment. Perhaps 100 milliseconds later (the actual time varies) the PL decoder will recognize the subaudible tone and will activate the PL signal going to the controller. At that point the controller will see that the COR and PL are both active and will key up any connected transmitters (subject to the keyup delay filter and other factors). As long as both the COR and PL signals are active, the controller will consider that receiver to be active. When that person unkeys, the receiver's squelch circuit will recognize the loss of carrier very quickly (some squelch circuits are faster than others - ask about the RLC-MOT) and deactivate the COR signal. The controller will see the change in the COR signal and mute the audio right away, so you get a short squelch tail. The PL decoder will eventually figure out that the subaudible tone went away and deactivate the PL signal, perhaps 200 milliseconds later. The delay in sensing the loss of PL won't matter because the audio is already muted (unlike mode 2). Mode 4: Either COR or PL will cause the controller to respond to the receiver. This mode is useful if you want to allow access to a repeater without PL, but you have to set the squelch relatively tight to keep noise from keying the repeater. As long as your signal to the repeater is relatively strong, you can transmit without PL and you will get short squelch tails just like in mode 1. If you are too far away and can't get a strong enough signal to the repeater to open the squelch, you can transmit a PL tone. If your signal is strong enough for the PL decoder at the repeater to work, you will be able to talk on the repeater, even if you can't open the squelch (similar to mode 2). Note that for this mode to work, the receiver must not mute the audio going to the controller when the squelch is closed (you must use unsquelched audio). When using this mode, you should transmit PL to the repeater only when necessary, as whenever you use PL, you will get long squelch tails. Mode 5: The controller considers the receiver to be active all of the time, regardless of the COR and PL signals. This mode is useful for working with HF radios, with or without all- mode squelch. If the HF radio doesn't have squelch, or if it does but it is set too tight and the signal keeps dropping out, you can select this mode to tell the controller to treat it like it is always active while you are using it. You may want to change the access mode to mode 0 when you are not using it, to keep it from timing out. Example: You want to change the receiver and DTMF mode to COR and PL (mode 3) on port 2. Note that you don't need to specify the DTMF mode if it is the same as the receiver mode: <005> 2 3 or <005> 2 3 3 Voice Response: "Two CAP CAP" (CAP is for COR and PL) Example: You want to allow carrier access to a repeater on port 1, but you want to require PL to enter DTMF commands. <005> 1 1 3 Response: Voice Response "One CAP COR" 006: Set or Recall Receiver Priorities (monitor mute) This command allows audio from a receiver to be automatically muted whenever audio from another receiver is heard. This can be used to mute a weather radio, for example, when someone keys the repeater. The weather radio will remain muted as long as the repeater receiver is active and for a few seconds afterward (this time can be changed). This is sometimes known as "monitor mute" because it is often used when monitoring another repeater system, weather radio, space shuttle audio, etc. For each transmitter, you can specify the "priority" of each receiver. If two receivers of the same priority are active (keyed up) at the same time, their audio will be mixed (the way the controller always worked in firmware versions V1.80 and earlier). If they have different priority settings, the audio from the lower priority receiver will be muted. <006> T Recall settings for TX "T" <006> T RP Set priority for one RX <006> T RP RP Set priority for two RX <006> T RP RP...RP Set priority for multiple RX Parameters: - 006 is the default command name. - 'T' is the TX number (1..6) - 'R' is the RX number (1..6) - 'P' is the priority (default priority for all receivers is 4, allowed values are 0..9) Examples: You have a repeater on port 1 and a weather radio on port 2. You want to mute the weather radio if any other receiver can be heard on transmitter 1. If all of the other receivers are still set to their default priority level (4), we just need to set the priority for RX 2 to something less than 4. We will set it to zero in this example. <006> 1 2 0 D or unkey or Notes: Timers (51..56) control how long lower priority receivers stay muted after higher priority receivers become inactive. 013: Set COR and PL Active Levels This command allows you to select whether the COR and PL inputs are active low or active high. The default is active low; when the controller sees a COR line go to ground, it thinks that the receiver is getting a signal. If you have a radio or PL detector that goes high when active, you can use this command to tell the RLC-Club Deluxe II to consider high to be the active level. <013> p c l Set Active Level <013> p 0 0 Reset to Defaults Notes: This command does not affect the input circuits at all; it does not disable the built-in pullup resistors on the RLC-Club Deluxe II's COR and PL inputs. If you are not able to enter commands using DTMF, you may need to temporarily fool the RLC-Club Deluxe II into thinking that your receiver's active level is different than it is. For example, if your receiver outputs an active high COR signal to the RLC-Club Deluxe II, the Deluxe II will not accept DTMF commands from that receiver until its COR polarity is changed with this command. You could solve this problem by temporarily disconnecting the COR line from the receiver and manually attaching it to ground. This will cause the RLC-Club Deluxe II to think that the receiver is active (COR line is active low by default). You will have to disconnect that line from ground or press the 'D' key to simulate unkeying after entering each command. Parameters: - 013 is the default command name. - P is the port to select the active levels for. - C is the COR polarity, 0 for active low, 1 for active high. - L is the PL polarity, 0 for active low, 1 for active high. Default: - All COR and PL inputs default to active low. Example: Change Port 2's COR input to active high: <013> 2 1 0 D or unkey or Voice Response: "2 1 0" 155: Enable or Disable PTT for a Port This command allows you to turn a PTT off regardless of what else the controller is doing. It doesn't matter whether it is a repeater or a link, what receivers are active, or anything else, if this command gets executed with F=0, the PTT goes off and stays off. This command is not the best way to regularly shut off a repeater or link (use Commands 000..002 for that), but will get the job done in an emergency. The only way to make the PTT work normally is to execute this command with F=1 or to reinitialize the controller. <155> p f Parameters: - 155 is the default command name. - P is which transmitter to turn off - F is 1 to enable the PTT (the default) or 0 to disable it Notes: This command does not disable the receiver, so you can normally turn the repeater back on by executing this command and enabling the PTT. However, if you have the controller set up to require a challenge password and this command is password protected, you will not be able to hear the challenge with the PTT disabled so you won't be able to log on and enable the PTT again. In that case you will have to access the controller another way, such as from another radio port, from the reverse autopatch, or from the serial port. 156: Recall Which PTT are Enabled This command allows you to recall which PTT are enabled and which have been turned off with Command 155. <156> Parameters: - 156 is the default command name. Voice Response: Ports that are set to operate normally are listed. Any ports not listed have their PTT disabled. Normal response: "1234567". Chapter 3: Audio and DTMF configurations This chapter deals with how the controller handles DTMF digits that are received from a radio or the reverse autopatch. You can control both what is heard on the repeater while digits are being entered and what the controller does with those digits - whether it uses them to execute commands or ignores them. Background: The controller has a DTMF decoder that is constantly listening to each receiver. A DTMF decoder works by watching for 8 tone frequencies, 4 that represent the row and 4 that represent the column of a 16 key DTMF keypad. If a row frequency and a column frequency are detected at the same time, the decoder registers it as a valid digit and tells the microprocessor. This takes about 40 or 50 milliseconds from the time the DTMF digit starts. DTMF Mute: If you have the controller set to mute DTMF digits on a transmitter (see command 007), it will turn off the audio from the receiver that is receiving DTMF digits to that transmitter as soon as the digit is detected. Normally you will hear the first few milliseconds of the DTMF digit before it is detected and muted, although you can avoid hearing it at all with an audio delay module (available from Link Communications). The audio stays muted for a few seconds (see command 020, DTMF mute timers) after each digit is released. If you press another digit during those few seconds (while the audio is still muted), you won't hear any part of the following digits. So when you key up to enter a command, those listening to the repeater will hear a short beep when you hit the first digit and then your digits will be muted (unless you wait too long between digits and the timer expires). DTMF Cover Tone: If you want to, you can turn on a "cover tone" that is sent while the DTMF digits are muted (see command 007). This constant beeping while digits are being entered lets people know that someone is programming, so they don't just key up and talk over the silence of the DTMF mute. You can change what the cover tone sounds like by editing macro 339. Drop Transmitters When DTMF Muted Option: In some cases (usually for link transmitters), it is desirable to let a transmitter unkey when DTMF is muted rather than transmitting a dead carrier or cover tone while DTMF is muted. Command 007 has an option to enable this. Note that after the DTMF mute starts, the transmitter's hang timer (and mini-hang timer) will run before the PTT will be turned off (the hang time is often very short on link transmitters, so this may not be noticeable). Also note that if there is another reason for the transmitter to stayed keyed up (another connected active receiver, synthesized voice message, etc.), the transmitter remain keyed and the receiver that is entering DTMF will simply be muted. Finally, if the DTMF mute bypass is used, the transmitter will remain keyed so the DTMF digits can be heard. DTMF Mute Options are Set for Each Transmitter: The DTMF mute options are set for each transmitter (not receiver). This means, for example, that if you turn on the DTMF mute for your repeater transmitter, that DTMF tones will be muted on the repeater whether they are received from the repeater receiver, a link receiver, the autopatch, etc. In most systems, the DTMF mute (and often cover tone) are turned on for repeater transmitters. DTMF Mute Bypass: The DTMF mute bypass, if enabled, allows the mute to be temporarily bypassed so DTMF digits can be heard on transmitters where they are normally muted. The mute bypass is activated when the force-execution digit (usually 'D', see command 078 to change) is the first digit detected after a receiver becomes active (when the user keys up). The bypass feature can be used to send DTMF paging codes over a repeater that mutes DTMF digits or for passing commands out a link transmitter that normally mutes DTMF tones. When the DTMF mute is bypassed in this way, the controller ignores the DTMF digits that are entered; they will not cause the controller to execute commands or send error messages. The bypass feature is de-activated when the receiver becomes inactive (when the user unkeys). A typical example involves a repeater and link port. Both transmitters have their DTMF mute functions enabled (possibly with cover tone or the drop-transmitter option), so when DTMF commands are sent to the controller, it will mute the digits. If the DTMF mute bypass feature is turned on for the link transmitter but not for the repeater transmitter, a user can key up, press 'D' to activate the bypass, then enter the DTMF digits. Those digits will be passed out the link transmitters but will still be muted on the repeater transmitter. The 'D' (force-execution digit) itself will be muted as soon as it is detected. If you do not have an audio delay module, the first part of that 'D' will be heard and might mess up whatever you are passing tones to. There are a variety of ways to deal with this: Some devices (such as IRLP interfaces) automatically ignore 'D', so even if they do decode the part of the 'D' that is not muted, it won't have any effect. Install an audio delay module on the receiver the tones are being entered from. That will allow the 'D' to be completely muted, so the listening device won't hear it at all. If the tones are going to another controller that supports the same command 007 features: Turn off the DTMF bypass on the other controller so the 'D' won't cause it to ignore the digits Or see the "Advanced DTMF Mute Bypass Option" described at the end of command 007. It lets you disable the DTMF mute bypass for selected receivers. If the listening device has a force-execution digit or something similar that will cause it to ignore any digits already received, that digit could be sent after the 'D' and before the other digits. If the listening device resets when the signal goes away, use command 007 DTMF mute option 2 to drop the transmitter while digits are being muted and set the transmitters hang timer (and mini-hang timer) to zero. When the force-execution digit is detected and muted, the transmitter will drop until that digit is released. Then it will come back up allowing the other digits to be passed through. Turn DTMF mute off and enter the digits without using a 'D' first. In firmware versions V1.80 and earlier, the DTMF mute bypass could be enabled or disabled for each receiver. If the bypass feature was used, the DTMF mute was disabled on all transmitters. In all firmware versions since then, the DTMF bypass is enabled or disabled individually for each transmitter. It doesn't matter which receiver the DTMF digits are entered from (but see the "Advanced DTMF Mute Bypass Option" at the end of command 007); if the force execution digit is the first digit entered, any transmitters connected to that receiver will have their DTMF mute functions temporarily disabled (until that receiver unkeys). This change makes it possible to normally mute DTMF on both repeater and link outputs and to use the mute bypass to allow DTMF digits to be sent down links without those digits being heard on the repeater output. Passing DTMF Digits Down Links: Link transmitters can be handled in a variety of ways. If the DTMF mute is left off for link transmitters, all DTMF tones entered on the repeater receiver will be passed down the link (assuming that the repeater and link ports are connected, see command 000). If the controller at the other end of the link is has similar command names to the local controller, it may try to execute commands that are not intended for it. If it has completely different command names (command 061 can help with this), uses preaccess (see Chapter 9), or has some other way of figuring out which commands it should try to process, this can work fine. If the DTMF mute is turned on for link transmitters and you need to send DTMF tones down the links to the repeater controller on the other end of the link, you have two options: bypass the DTMF mute or make the controller generate DTMF digits. Command 007 allows the DTMF mute bypass feature to be enabled for link transmitters. Once it is enabled, digits can be passed from the repeater receiver out the link transmitters by keying up, pressing 'D' to activate the mute bypass, then entering the DTMF digits that need to go down the link. User macros (see Chapter 8) can be executed in response to user-entered DTMF commands. Those macros can be named almost anything from 1 to 6 DTMF digits long using command 010. They can be programmed to send any string of DTMF digits out any transmitter. For example: 010 500 ABC123 ; name macro 500 "ABC123" 055 500 ; make sure macro 500 is empty 056 500 037 2 ; send audio out transmitter 2 056 500 031 01 02 03 04 ; send DTMF "1234" Note that the DTMF digits sent by the macro ("1234") may be completely different than the digits the user entered to cause the macro to be executed ("ABC123"). Voice Falsing: As mentioned earlier, a DTMF decoder works by watching for 8 tone frequencies, 4 that represent the row and 4 that represent the column of a 16 key DTMF keypad. If a row frequency and a column frequency are detected at the same time, the decoder registers it as a valid digit. Sometimes peoples' voices have those frequencies in them and cause the DTMF decoder to think that a digit is present when it is not. If you have the DTMF mute turned on, this will cause it to be activated and your voice will "drop out" for a couple of seconds as the controller thinks it is muting a DTMF digit. If you have the cover tone turned on, you will hear it as well. The voice falsing of the DTMF decoder is not the decoder's fault - it is just watching for those tones. Occasional falsing can be made less noticeable by reducing the duration of the DTMF mute timers. If you have an audio delay module installed, that timer can be set to one half second or so with no negative consequences. The disadvantage of short DTMF mute timer setting on inputs without audio delay modules is that if you pause between digits, the first digit entered after the pause may be heard on the repeater output. A mute time of one or two seconds usually works well. There are a couple of things you can do to reduce falsing at its source. The first thing is to check all of your audio levels. If you have the receive audio turned up too high at any point before it gets to the decoder, it may be distorted, which adds harmonics and makes falsing more likely. If your audio levels are OK, you have older versions of the hardware, and you still have falsing problems, you may be able to change some components to minimize the problem. These modifications have been included in later revisions of the controller hardware, so if your controller is new, you can skip the rest of this section. There is a resistor that controls how long a DTMF digit must be present before the DTMF decoder will consider it to be valid. Increasing the value of this resistor will increase the required time and decrease the chances of falsing, but may keep fast autodialers from working. Some early controllers may have used a 300K resistor, while later controllers use 470K. Even larger values (up to about 700K, where the decoder stops working at all) can be used in extreme cases. All of the Deluxe II boards and RLC-Club controllers starting with revision E (the first surface- mount version) have an additional circuit paralleled across the resistor described above. That circuit consists of a resistor and a diode in series. It does not change the amount of time it takes a digit to decode (the diode prevents that), but they help reduce falsing by "resetting" the decoder faster when a digit goes away. This resistor is normally 220K; smaller values would "reset" the decoder even faster. This should not be necessary except perhaps in extreme cases. Board Decode Time Resistor "Reset" Resistor RLC-Club (revisions A..D) R14 (main receiver) R15 (autopatch) N/A RLC-Club (revision E) R14 (main receiver) R15 (autopatch) R122 (main receiver) R123 (autopatch) Deluxe Board R19 N/A Deluxe II R1, R2, R3, R4, R193 R13, R14, R15, R16, R196 007: Configure DTMF Mute/Cover Tone/Bypass This command allows you to configure a what is heard on the specified transmitter when a user enters DTMF digits. By default they are passed through the controller just as any other audio would be. In some cases (such as when you are configuring the controller), it may be preferable to keep the digits from being heard. This command lets you simply mute the digits, mute them and send a cover tone (constant beeping), or drop the transmitter completely while the digits are being entered. A "bypass" function can also be enabled to allow DTMF digits to be passed through (rather than muted) if the force-execution digit (usually "D") is the first DTMF digit pressed after keyup. See the beginning of this chapter for more detailed explanations. <007> p Recall settings <007> p m Configure DTMF mute <007> p m b Configure DTMF mute and bypass <007> p 0 1 Restore defaults Parameters: - 007 is the default command name. - P is the port to set up or recall - M turns the DTMF mute on or off 0 - Disables DTMF mute on the selected transmitter (default) 1 - Enable DTMF mute on the selected transmitter 2 - Enable DTMF mute with cover tone on the selected transmitter 3 - Drop the transmitter when DTMF tones are being received - B (optional) turns the DTMF mute bypass on or off 0 - Disable the DTMF bypass for the selected transmitter 1 - Enable the DTMF bypass for the selected transmitter (default) Voice Response: Notes: A DTMF digit will be muted, cause cover tone, let the transmitter drop, etc. as long as it is held. It will continue to have an effect after it is release for the duration of the DTMF interdigit timer (see Chapter 4) controls how long after a digit is released it will continue to cause muting / cover tone / transmitter drop. Example: For port 1,turn on DTMF mute with cover tone and turn off the mute bypass: <007> 1 2 0 unkey, 'D' or Voice Response "1 2 OFF" Notes about the Autopatch: When using the autopatch, if the other end is hung up before the autopatch is, you may get a "second dial tone" which allows you to make another call without hanging up. Since the controller doesn't know that the other end hung up, it doesn't know that you are placing another call and will not prevent you from making a long distance call, even if long distance numbers are normally blocked. To prevent this, you can turn on the DTMF mute for the autopatch port, although there are some drawbacks to that. If you turn on DTMF mute for the autopatch port, command 111 will no longer let you dial, you will not be able to enter digits to control answering machines, leave pages, etc., or do anything else that requires passing DTMF digits entered from the radio down the phone line. In most cases, the DTMF mute can be left off with minimal risk of abuse. Advanced DTMF Mute Bypass Option: An optional digit can be appended to command 007 as described above, using the format "<007> p m b r" where "r" is the additional digit. If "r" is 1 (the default) and "D" is the first digit entered from receiver "p", the DTMF bypass will work normally. If "r" is 0, the DTMF bypass feature will not work from receiver "p". In that case, if "D" (the force-execution digit) is the first digit detected from receiver "p", it will just be ignored and following digits will be processed and muted as if the 'D' was never heard (those DTMF digits can cause commands to be executed, may cause error messages, etc.). It might be useful to disable the DTMF bypass for link receivers. Then if a link receiver hears part of the DTMF "D" coming down the link from another site that is using the DTMF bypass feature to pass DTMF tones out its link transmitter, that 'D' won't cause that link receiver to ignore the following digits. Chapter 4: Timers This chapter deals with the controllers timers and time related issues. The areas dealt with in this chapter are: Programming, starting, restarting and recalling timers Setting and recalling the time-of-day clock 020: Set or Recall a Timer's Duration This command allows you to set the duration of a timer. <020> xxx Recall timer's duration <020> xxx t..t Set timer's duration Parameters: 020 is the default command name. 'xxx' is the timer to be programmed (three digits) 't..t' is the value to be programmed into the timer, 0 to 9999, one to four digits. The first group of timers are set in 10mS increments (100 counts per second). The rest of the timers are set in 1 second increments (60 counts per minute, 3600 per hour). Note: When a timer is set, a count variable associated with that timer is set equal to duration of the timer (t..t from command 020). Once the timer is set, the count variable starts counting down from the timer_duration 0 and then stops after expiring. If command 020 is used to set a timer's duration while the timer is running, the count associated with that timer will be adjusted accordingly. If the timer's duration is set to a value less than the current count, the timer will expire immediately. Conversely, if the timer is set to a value greater than the count, the appropriate time will be added to the count to lengthen the timer accordingly. Pseudo Code: IF( count != 0 ) THEN // Timer already running IF( input_duration > current_duration ) THEN count += input_duration - current_duration // Add appropriate time to count current_duration = input_duration // Set new timer's duration ELSE count = 0 // Stop timer, it has already run longer than input_duration current_duration = input_duration // Set new timer's duration END IF ELSE // Timer not running current_duration = input_duration // Set new timer's duration END IF List of Timers Message Start Delay Timer: This timer controls how long the controller will wait before sending any tones or voice messages in two situations. The first is when you enter a command and unkey; it controls how long it will be before the response to that command will be sent. If the delay is set too short, you might miss the first word or two while your HT finishes switching from transmitting to receiving. The second situation in which this timer might delay tones or voice messages is when they need to be sent out of a transmitter that is not keyed up at the time. The transmitter will be keyed for at least the duration of this timer before the tone or voice is started. If this timer is too short, the transmitter might not have time to come up to full power and the beginning of the tone or voice message might be missed. If the tone or voice message is being sent down a link system with multiple hops, more time might be needed so all of the link transmitters will have time to come up. - This timer is programmed in 10mS increments from 0..9999. - If a timer value of 000 is entered, the timer is disabled. Timer Number Defaults 000. Message Start Delay Timer, Transmitter 1 . . . . 500mS (050) 001. Message Start Delay Timer, Transmitter 2 . . . . 500mS (050) 002. Message Start Delay Timer, Transmitter 3 . . . . 500mS (050) 003. Message Start Delay Timer, Transmitter 4 . . . . 500mS (050) 004. Message Start Delay Timer, Transmitter 5 . . . . 500mS (050) 005. Message Start Delay Timer, Transmitter 6 . . . . 500mS (050) 006. Message Start Delay Timer, Autopatch . . . 500mS (050) Courtesy Beep Delay Timer: This timer specifies the minimum time between when a receiver unkeys and when its courtesy beep will be sent out connected repeater ports. The courtesy beep can also be delayed by other tones in the tone queues and the synthesized voice. - This timer is programmed in 10mS increments from 001-9999 - If a timer value of 000 is entered, the transmitter will hang on the air forever. Timer Number Defaults 007. Courtesy Beep Delay Timer, Receiver 1 . . . 1 sec (100) 008. Courtesy Beep Delay Timer, Receiver 2 . . . 1 sec (100) 009. Courtesy Beep Delay Timer, Receiver 3 . . . 1 sec (100) 010. Courtesy Beep Delay Timer, Receiver 4 . . . 1 sec (100) 011. Courtesy Beep Delay Timer, Receiver 5 . . . 1 sec (100) 012. Courtesy Beep Delay Timer, Receiver 6 . . . 1 sec (100) Transmitter Hang Timer: This timer holds the transmitter PTT active after a connected receiver goes inactive. If a courtesy beep is sent, this is the minimum time after the courtesy beep before the PTT drops. This timer only has an effect when a connected receiver has been active since the PTT went active; otherwise this timer is ignored and the mini-hang timer (timer 036..042) is the only thing that will cause a delay. You must set the mini-hang timer shorter than this timer or this timer won't have any effect, as the actual delay is the longer of the two timers. - This timer is programmed in 10mS increments from 000-9999 (000 is OK). Timer Number Defaults 013. Hang Timer for Transmitter 1. . . 2 sec (200) 014. Hang Timer for Transmitter 2. . . 2 sec (200) 015. Hang Timer for Transmitter 3. . . 2 sec (200) 016. Hang Timer for Transmitter 4. . . 2 sec (200) 017. Hang Timer for Transmitter 5. . . 2 sec (200) 018. Hang Timer for Transmitter 6. . . 2 sec (200) 019. Hang Timer for Autopatch . . . . 2 sec (200) DTMF Mute Timer: This timer controls the amount of time a receiver entering DTMF stays muted after a DTMF digit is released (assuming the DTMF mute is enabled with command 007). If following digits are entered within the duration of this timer after the previous digit is released, they will be completely muted. If this timer is set shorter than the time between digits, the beginning of the following digits will be heard. In other words, setting this timer longer allows DTMF digits to be entered more slowly without hearing the beginning of the second and following digits. The disadvantage of increasing the duration of this timer is that if the DTMF decoder voice falses (see the beginning of Chapter 3 for more information about voice falsing), it will mute the voice longer. If an audio delay module is installed for a receiver, this timer can be set quite short (to the length of the delay, usually about 100mS) or slightly longer. The audio delay module will keep the beginning of any digits from being heard and the short delay will minimize the problems with voice falsing. If it is set too short, the end of each digit may be heard (if the controller quits muting before the audio gets through the audio delay module). This timer is programmed in 10mS Increments from 001-9999 If a timer value of 000 is entered, your audio will be muted forever, so if you want it to be as short as possible, enter 001 Timer Number Defaults 020. DTMF Mute Timer, Receiver 1 . . . 1 sec (100) 021. DTMF Mute Timer, Receiver 2 . . . 1 sec (100) 022. DTMF Mute Timer, Receiver 3 . . . 1 sec (100) 023. DTMF Mute Timer, Receiver 4 . . . 1 sec (100) 024. DTMF Mute Timer, Receiver 5 . . . 1 sec (100) 025. DTMF Mute Timer, Receiver 6 . . . 1 sec (100) 026. DTMF Mute Timer, Autopatch . . . 1 sec (100) I/O Polling Timer: This timer determines how often the controller checks to see if any of the analog/digital input lines have changed from high to low or low to high or if any analog alarm conditions have changed. If you want quicker response to changes, shorten this timer. If you don't want to hear about changes that happen more often than every minute or so, lengthen it to a minute. The default is one second. Timer Number Defaults 027. I/O Polling Timer . . . 1 sec (100) Courtesy Beep After Voice or Tones Timer: This timer keeps a courtesy beep from being sent immediately after a voice message. It sets the minimum amount of time the controller will wait after the voice and tone generators stop before a courtesy beep will be sent. The courtesy beep delay timers (timers 007..012) control how long after unkeying the controller will wait, but if they have already expired and the courtesy beep is just waiting for the voice to finish, this timer will have an effect. An example of this is when you kerchunk a repeater after a long period of inactivity and then wait for the initial ID then the courtesy beep. - This timer is programmed in 10mS Increments from 001-9999 Timer Number Defaults 028. Courtesy Beep After Voice Timer, Transmitter 1. . . . 1 sec (100) 029. Courtesy Beep After Voice Timer, Transmitter 2. . . . 1 sec (100) 030. Courtesy Beep After Voice Timer, Transmitter 3. . . . 1 sec (100) 031. Courtesy Beep After Voice Timer, Transmitter 4. . . . 1 sec (100) 032. Courtesy Beep After Voice Timer, Transmitter 5. . . . 1 sec (100) 033. Courtesy Beep After Voice Timer, Transmitter 6. . . . 1 sec (100) Doug Hall RBI-1 or RLC-ICM Delayed Send Timer: Buffers inside the RBI-1 or the RLC-ICM overflow if it is sent too many changes too quickly. The RLC-Club Deluxe II avoids this potential problem by collecting all of the changes that occur quickly (such as within a macro) and sends the combined result of all of them only when no changes have been made for the duration of this timer. This timer also affects the RLC-ICM. - This timer is programmed in 10mS Increments from 001-9999 Timer Number Defaults 034. RBI-1 or RLC-ICM Delayed Send Timer . . . . 500 mS (050) HF Radio Scan Delay Timer: This timer determines how quickly the HF radio will scan by controlling how long it waits before sending the next frequency step. Smaller timer values make it scan more quickly. It affects all three scan step sizes (slow, medium and fast) equally. It also has an effect on how quickly other changes are sent to the radio, although reasonable changes in that time won't be very noticeable. There is a limit to how quickly the controller can send command to the radio, so if setting this timer to a smaller value doesn't increase the scan speed past a certain point, you have probably reached that limit. Some radios such as the Yaesu FT-767 require an acknowledgment to be sent after every command. This causes them to scan only half as fast as other radios given the same scan timer setting (since the controller has to send the frequency command and the acknowledgment for each step). When using those radios, you may wish to set the scan timer to about the duration you would for other radios. - This timer is programmed in 10mS Increments from 001-9999 Timer Number Defaults 035. HF Scan Delay Timer . . . . 500 mS (050) Transmitter Mini-Hang Timer: This timer holds the transmitter PTT active for a minimum time after any keying source (connected receiver, synthesized voice, tone, CW, DVR message, etc) goes inactive. It can be used to keep the transmitter from dropping out immediately after a message. To control the hang time after a connected receiver unkeys, you can also use the normal hang timers (013..019); the actual hang time will be the longer of the two. - This timer is programmed in 10mS increments from 000-9999 Timer Number Defaults 036. Mini-Hang Timer, Transmitter 1 . . . . 500 mS (050) 037. Mini-Hang Timer, Transmitter 2 . . . . 500 mS (050) 038. Mini-Hang Timer, Transmitter 3 . . . . 500 mS (050) 039. Mini-Hang Timer, Transmitter 4 . . . . 500 mS (050) 040. Mini-Hang Timer, Transmitter 5 . . . . 500 mS (050) 041. Mini-Hang Timer, Transmitter 6 . . . . 500 mS (050) 042. Mini-Hang Timer, Autopatch . . . 500 mS (050) Keyup Delay Timer: The keyup delay timer is used to keep short noise bursts that open the receiver's squelch from keying up the repeater. It can also keep people from kerchunking the repeater. When enabled, it makes the controller totally ignore keyups shorter than the duration of this timer (the rest of this explanation will assume second). If the receiver is keyed for longer than second, the first second will be ignored, then it will respond normally, bringing up the transmitter, triggering the ID system, etc. To keep every keyup from being delayed, the keyup delay is automatically disabled while the repeater is being used. It is only re-enabled when the repeater is not used for a default of 60 seconds (see timers 182..187. If this timer is set to zero (the default), the keyup delay is disabled. A typical setting would be 50, which is second. Timer Number Defaults 043. Keyup Delay Timer, Receiver 1 . . 0 (Disabled) 044. Keyup Delay Timer, Receiver 2 . . 0 (Disabled) 045. Keyup Delay Timer, Receiver 3 . . 0 (Disabled) 046. Keyup Delay Timer, Receiver 4 . . 0 (Disabled) 047. Keyup Delay Timer, Receiver 5 . . 0 (Disabled) 048. Keyup Delay Timer, Receiver 6 . . 0 (Disabled) Wind Speed Timer: This timer is used to help determine the wind speed indicated by an anemometer. The number of pulses counted during the duration of this timer becomes the pseudo-analog value. For more information, see command 109. Timer Number Defaults 049. Wind Speed Timer . . . 2.26 sec (226) Word Too Long Timer: There is no need to change this timer! It is used to ensure that even if the voice synthesizer messes up, that it will not cause the controller to leave a transmitter keyed. If a word takes longer than this timer, it will be truncated and the controller will go on to the next word. Timer Number Defaults 050. Word Too Long Timer . . . . 1.5 sec (150) Receiver Priority Mute Timer: This timer keeps lower priority receivers (as set with command 006) muted for the specified time after a higher priority receiver becomes inactive. - This timer is programmed in 10mS increments from 000-9999 Timer Number Defaults 051. Receiver Priority Mute Timer, Receiver 1 . . . . 150 mS (015) 052. Receiver Priority Mute Timer, Receiver 2 . . . . 150 mS (015) 053. Receiver Priority Mute Timer, Receiver 3 . . . . 150 mS (015) 054. Receiver Priority Mute Timer, Receiver 4 . . . . 150 mS (015) 055. Receiver Priority Mute Timer, Receiver 5 . . . . 150 mS (015) 056. Receiver Priority Mute Timer, Receiver 6 . . . . 150 mS (015) Impolite ID Timer: This timer waits until either the timer expires or activity goes away before sending an ID. - This timer is programmed in 1Sec increments from 001-9999 - If a timer value of 000 is entered, the controller will not interrupt a conversation to send an ID. Timer Number Defaults 100. Impolite ID Timer, Transmitter 1 . . . 20 sec (020) 101. Impolite ID Timer, Transmitter 2 . . . 20 sec (020) 102. Impolite ID Timer, Transmitter 3 . . . 20 sec (020) 103. Impolite ID Timer, Transmitter 4 . . . 20 sec (020) 104. Impolite ID Timer, Transmitter 5 . . . 20 sec (020) 105. Impolite ID Timer, Transmitter 6 . . . 20 sec (020) Initial ID Timer: This timer times the amount of inactivity before an initial ID is sent. - This timer is programmed in 1Sec increments from 001-9999 - If a timer value of 000 is entered, the controller will never send an initial ID. Timer Number Defaults 106. Initial ID Timer, Transmitter 1. . . . 10 min (600) 107. Initial ID Timer, Transmitter 2. . . . 10 min (600) 108. Initial ID Timer, Transmitter 3. . . . 10 min (600) 109. Initial ID Timer, Transmitter 4. . . . 10 min (600) 110. Initial ID Timer, Transmitter 5. . . . 10 min (600) 111. Initial ID Timer, Transmitter 6. . . . 10 min (600) Pending ID Timer: This timer times inner activity ID timer so a proper Pending ID can be send during activity. - This timer is programmed in 1Sec increments from 001-9999 - If a timer value of 000 is entered, the controller will never send a rotating ID. - This timer should normally be set shorter than the initial ID timer (one minute shorter works well). You may need to make sure that the duration of this timer plus the duration of the impolite ID timer is less than 10 minutes to meet requirements for ID timing. Timer Number Defaults 112. Pending ID Timer, Transmitter 1. . . . 9 min (540) 113. Pending ID Timer, Transmitter 2. . . . 9 min (540) 114. Pending ID Timer, Transmitter 3. . . . 9 min (540) 115. Pending ID Timer, Transmitter 4. . . . 9 min (540) 116. Pending ID Timer, Transmitter 5. . . . 9 min (540) 117. Pending ID Timer, Transmitter 6. . . . 9 min (540) Timeout Timers: This timer times how long each receiver has been active. If the receiver is active longer than the duration of this timer, it is disabled until it goes inactive, and its time out message (see Chapter 8 for list of macros) is sent out all transmitters that are connected to it. It is reset and the time out clear message is sent when a timed out receiver goes inactive. - This timer is programmed in 1 second increments from 001-9999 - If a timer value of 000 is entered, the controller will never time-out. - By default the time out timer is reset as soon as a receiver unkeys. To make it wait until the courtesy beep to reset (which may help discourage "tailgating"), see command 041. Timer Number Defaults 118. Time Out Timer, Receiver 1. . . . 3 min (180) 119. Time Out Timer, Receiver 2. . . . 3 min (180) 120. Time Out Timer, Receiver 3. . . . 3 min (180) 121. Time Out Timer, Receiver 4. . . . 3 min (180) 122. Time Out Timer, Receiver 5. . . . 3 min (180) 123. Time Out Timer, Receiver 6. . . . 3 min (180) 124. Time Out Timer, Autopatch . . . . 3 min (180) Dial Tone Timers: These timers are used to limit how long the dial tone will run. The dial tone can also be stopped by other things, such as a DTMF character being entered on the port the dial tone is being set out of or the preaccess timer expiring (since indicating that a link has been preaccessed is what dial tone is used for most). If you want to generate dial tone that can't be stopped by any of these things, use Command 040 and generate a two tone chord with frequencies of 350 and 440 Hz. - This timer is programmed in 1Sec increments from 001-9999 - If a timer value of 000 is entered, this timer will never stop the dial tone. Timer Number Defaults 125. Dial Tone Timer, Transmitter 1 . . . . 8 sec (008) 126. Dial Tone Timer, Transmitter 2 . . . . 8 sec (008) 127. Dial Tone Timer, Transmitter 3 . . . . 8 sec (008) 128. Dial Tone Timer, Transmitter 4 . . . . 8 sec (008) 129. Dial Tone Timer, Transmitter 5 . . . . 8 sec (008) 130. Dial Tone Timer, Transmitter 6 . . . . 8 sec (008) 131. Dial Tone Timer, Autopatch . . . 8 sec (008) Preaccess Timers: These timers control how long the "window" of access is between when you enter the preaccess code and when you have to enter a DTMF digit or be locked out. It starts running again as soon as each DTMF digit is released, and will lock you out if it expires. When it expires, it throws away whatever DTMF digits have been entered so far and won't accept any more commands until the controller is accessed again. It also stops the dial tone when it expires. - This timer is programmed in 1Sec increments from 001-9999 - If a timer value of 000 is entered, this timer will never expire. Timer Number Defaults 132. Preaccess Timer, Port 1. . . 8 sec (008) 133. Preaccess Timer, Port 2. . . 8 sec (008) 134. Preaccess Timer, Port 3. . . 8 sec (008) 135. Preaccess Timer, Port 4. . . 8 sec (008) 136. Preaccess Timer, Port 5. . . 8 sec (008) 137. Preaccess Timer, Port 6. . . 8 sec (008) 138. Preaccess Timer, Autopatch . . . 8 sec (008) User Timers: These timers are not normally used by the controller. They are provided for your use. You can start them running by executing Command 022 and stop them with 023 (or they will stop automatically when they expire). Also, when one of these timers expires, the corresponding special macro (see Chapter 8) is automatically executed. This allows you to start these timers when certain things in the controller happen, and do something when the timer expires. These timers are programmed in one second increments. Timer Number Defaults 139. User Timer 00. . . 0 sec (000) 140. User Timer 01. . . 0 sec (000) 141. User Timer 02. . . 0 sec (000) 142. User Timer 03. . . 0 sec (000) 143. User Timer 04. . . 0 sec (000) 144. User Timer 05. . . 0 sec (000) 145. User Timer 06. . . 0 sec (000) 146. User Timer 07. . . 0 sec (000) 147. User Timer 08. . . 0 sec (000) 148. User Timer 09. . . 0 sec (000) 149. User Timer 10. . . 0 sec (000) 150. User Timer 11. . . 0 sec (000) 151. User Timer 12. . . 0 sec (000) 152. User Timer 13. . . 0 sec (000) 153. User Timer 14. . . 0 sec (000) 154. User Timer 15. . . 0 sec (000) DTMF Interdigit Timers or Auto-execution timers (See Command 078): These timers are used to get rid of stray DTMF digits after several seconds without entering any more digits. For example, if you key and press a DTMF digit, then start talking, this timer will throw that digit away after a default of 5 seconds. That way if, after you talk a while, you try to enter a command, the digit you entered 30 seconds ago won't mess it up. Of course if you unkeyed during that time, all of the digits would be either executed or discarded anyway. This also reduces problems caused by voice falsing the DTMF decoder, by discarding the incorrectly received digits if no more digits are received during the duration of this timer. This timer starts running when the DTMF digit is released, so you can hold a DTMF digit as long as you like without it being discarded. Timer Number Defaults 155. DTMF Interdigit Timer, Receiver 1. . . 5 sec (005) 156. DTMF Interdigit Timer, Receiver 2. . . 5 sec (005) 157. DTMF Interdigit Timer, Receiver 3. . . 5 sec (005) 158. DTMF Interdigit Timer, Receiver 4. . . 5 sec (005) 159. DTMF Interdigit Timer, Receiver 5. . . 5 sec (005) 160. DTMF Interdigit Timer, Receiver 6. . . 5 sec (005) 161. DTMF Interdigit Timer, Autopatch . . . 5 sec (005) Reverse Patch Ring Timer: This timer sets the maximum time between rings allowed for the reverse patch to work. If this timer expires between rings, the ring count starts over. This would keep the reverse patch from ever answering the phone. - This timer is programmed in 1 second increments from 001-9999 Timer Number Defaults 162. Reverse Patch Ring Timer . . . . 10 sec (010) DVR Start Recording Timer: This timer sets the maximum time allowed after entering a command to start recording a DVR message and when you actually key up to start the recording. If you wait longer than this timer, it will not record. This is so a command to record a DVR message can not be executed and end up recording someone that keys up an hour later. If you start the recording with a DTMF digit, this timer will not have any effect. - This timer is programmed in 1 second increments from 001-9999 Timer Number Defaults 163. DVR Start Recording Timer . . . . 10 sec (010) DVR Record Length Limit Timer: This timer sets the maximum length of message that can be recorded using the DVR. If you try to record a longer message, it will be truncated at this length. Of course, if you unkey, press a DTMF digit or the DVR runs out of memory before this time is up, it will quit recording sooner. You can set this timer to be relatively long while setting up the DVR, then shorter to keep people from leaving very long voice mail messages for people. - This timer is programmed in 1 second increments from 001-9999 - This timer defaults to 030 Timer Number Defaults 164. DVR Record Length Limit . . 30 sec (030) User Log-off Timer: This timer specifies the amount of time between correctly executed command entries that a user has before the controller logs the user off the system. Timer Number Defaults 165. Log-off timer for Port 1 . . 60 sec (060) 166. Log-off timer for Port 2 . . 60 sec (060) 167. Log-off timer for Port 3 . . 60 sec (060) 168. Log-off timer for Port 4 . . 60 sec (060) 169. Log-off timer for Port 5 . . 60 sec (060) 170. Log-off timer for Port 6 . . 60 sec (060) 171. Log-off timer for the Autopatch . 60 sec (060) 172. Log-off timer for the Serial Port 60 sec (060) Internal DVR Record Window: This timer specifies the amount of time you have between entering a command to record a message on the internal DVR and when you have to key up and actually begin recording the message. If you wait longer than this, the controller will clear the record command and you will have to enter it again. Timer Number Defaults 173. Internal DVR Record Window . . . 10 sec (010) Beacon Timer: This timer specifies the amount of time the controller will wait before trying to send the next beacon. See Chapter 19 for more information about the beaconing system. Timer Number Defaults 174. Beacon Timer . . . 1 sec (001) Tail Message Timers: These timers determine the minimum time between tail messages being sent. If they are set to 000, a tail message will be sent every time the transmitter drops. Otherwise, a tail message will be sent before a transmitter drop only if it has been longer than the timer's duration since the last drop out message was sent. In no case will the tail message cause the transmitter to key up; they will only be sent if something else brings up the transmitter. For more information about tail messages, see the event triggers table associated with command 157. Timer Number Defaults 175. Tail Message Timer TX 1. . . 5 minutes (300) 176. Tail Message Timer TX 2. . . 5 minutes (300) 177. Tail Message Timer TX 3. . . 5 minutes (300) 178. Tail Message Timer TX 4. . . 5 minutes (300) 179. Tail Message Timer TX 5. . . 5 minutes (300) 180. Tail Message Timer TX 6. . . 5 minutes (300) 181. Tail Message Timer Autopatch 5 minutes (300) Re-Enable Keyup Delay Timers: These timers determine how long a receiver must be inactive after being keyed up before the keyup delay will be re-enabled. See the description for timers 043..048 for more information. Timer Number Defaults 182. Re-Enable Keyup Delay Timer, RX 1. . . 60 sec (060) 183. Re-Enable Keyup Delay Timer, RX 2. . . 60 sec (060) 184. Re-Enable Keyup Delay Timer, RX 3. . . 60 sec (060) 185. Re-Enable Keyup Delay Timer, RX 4. . . 60 sec (060) 186. Re-Enable Keyup Delay Timer, RX 5. . . 60 sec (060) 187. Re-Enable Keyup Delay Timer, RX 6. . . 60 sec (060) 021: Restart a Timer (if already running) The controller automatically starts and stops most timers, but you can override the controller's normal way of doing things with this command. You can also use this command with the user timers (timers 139..154). This command allows you to restart a timer if it is currently running. This means that the count associated with the timer has not yet expired (count = 0). When recall the timer, get a message like this, "Timer TTT LL count CC" where TTT is the timer number, LL is the duration it is set to, and CC is the current count, the amount of time left before it expires if it is currently running. Also see command 022. <021> xxx Parameters: - 021 is the default command name. - XXX is the timer to restart (three digits, see command 020 for list of timers) Pseudo Code: IF( count != 0 ) THEN // Timer already running count = timer_duration // Start timer over at beginning END IF 022: Start/Restart a Timer The controller automatically starts and stops most timers, but you can override the controller's normal way of doing things with this command. You can also use this command to make the user timers (timers 139..154) start running. This command sets the count variable associated with a specific timer equal to the duration of the timer set with command 020 or to a value specified in this command. Once the count variable is set, the countdown to expiration begins. If the timer is already running, this command will make it start over. <022> xxx Start timer 'xxx' for the duration set with command 020 <022> xxx t..t Start timer 'xxx' for duration 't..t' Parameters: - 022 is the default command name. - 'xxx' is the timer to start (three digits, see command 020 for list of timers) - 't..t' is the duration the timer should run for this time only. This does not permanently change the duration of the timer; that is what command 020 is for. Notes: Some timers (such as the ID timers) are reset to their normal duration periodically by the firmware, so command 022 may be ineffective on those timers. If a timer's normal duration has been set to 0 with command 020, it will not run even if you specify a value for t..t with command 022. A duration of zero set with command 020 totally disables the timer. Pseudo Code: IF( Setting new temp_time ) THEN count = input_duration // Start timer for temporary duration ELSE count = timer_duration // Start timer for duration set by command 020 END IF 023: Stop a Timer This command allows you to stop a timer, so that it will not finish counting down and eventually expire. The controller automatically stops most timers as needed, so the only time you should need to use this command is when you want to change the way the controller normally works. Most timers automatically stop when they expire. <023> xxx Parameters: - 023 is the default command name. - XXX is the timer number Pseudo Code: count = 0 // Stop timer 025: Sets the Time of Day Clock This command allows you to set the time of day clock on the RLC-Club Deluxe II. <025> hh mm a/p Parameters: - 025 is the default command name. - HH is the actual hours with leading zeros - MM is the actual minutes with leading zeros - a/p is the AM/PM selection (1=PM, 0=AM) Example: Want to set the time to 3:25 PM <025> 03 25 1 D or unkey or Voice Response: " " 026: Recall the Time of Day Clock in Male Speech This command allows you to read the Time of Day Clock. The readback is Male time reading. Refer to Command 025 for setting the clocks time. <026> Parameters: - 026 is the default command name. Voice Response: "Male voice: " 027: Recall the Time of Day Clock in Female Speech This command allows you to read the Time of Day Clock. The readback is Female time reading. Refer to Command 025 for setting the clocks time. <027> Parameters: - 027 is the default command name. Voice Response: "Female voice: " 028: Sets the Date This command allows you to set the date on the RLC-Club Deluxe II Clock. <028> mm dd yy w Parameters: - 028 is the default command name. - MM is the month with leading zeros - DD is the day of the month with leading zeros - YY is the last two digits of the year W is the day of the week Number Day 1 Sunday 2 Monday 3 Tuesday 4 Wednesday 5 Thursday 6 Friday 7 Saturday Example: Want to set the date to January 2, 1996 <028> 01 02 96 3 029: Recall the Date This command allows you to read the date stamp of the controller. The readback is Male date reading. Refer to Command 028 for setting the date. <029> Note: if you want to recall the date as part of a message, you may want to try the variable words (Appendix B, words 800 and above). Speaking those words with command 036 will let you format the date readback any way you like it. Parameters: - 029 is the default command name. Voice Response: "This is " Chapter 5: Command Names This chapter deals with command names and controlling when those command names will be accepted and executed by the controller. Command name programming, checking and recalling Blocking and allowing command execution How Command Names and Command Numbers are Used: The RLC-Club Deluxe II controller has 1000 commands. The first 200 are commands that do a specific task and are described in this manual. The rest of the commands are macros that automatically execute a sequence of other commands. The controller automatically uses some of the macros to send IDs, courtesy beeps, and other things. These macros that are called automatically are described in Chapter 8. The remainder of the macros can be used for anything you want, such as turning on a link and sending a message for example. Command Names: Any of the 1000 commands can be executed by entering DTMF digits from a radio, from the reverse autopatch, or with a computer or serial terminal that is connected to the controller's RS- 232 serial port. To execute the commands, you enter the command's name and unkey or press enter. To execute some of the first 200 commands, you have to enter more digits after the command name, to give the controller more information. The command names default to 000, 001, 002..999. So to recall the time (command 026), you would just enter 026 and unkey. To set the time (command 025), you would enter "025" followed by the current time (two digits for the hour, two digits for the minute, and one digit to specify AM or PM). All of the other commands are similar. You can change the name of any or all of the commands using command 010. The name can be changed to any combination of DTMF digits up to six digits long. Normally you should avoid using the 'D' as part of the command names to avoid conflicting with the force-execution digit. If you are doing your programming from a computer or serial terminal, you can use characters that aren't DTMF digits in your command names, but then you won't be able to execute them from a radio. Command Numbers: The controller keeps track of both what the command was originally named (what it is in the manual) and what you may have renamed it to (they start out the same, 000, 001...). The original name is sometimes called the command number and it never changes. The command number is used for several things. One of them is renaming commands. To rename command 009 to ABC, you would enter "010 009 ABC", where 010 is the rename command, 009 is the command number, and ABC is the new name. If you then change your mind and want it to be called CBA, you would enter "010 009 CBA". Note that you still use 009, not ABC, when renaming it to CBA. You always rename the command number to the new name, not the old name to the new name. This eliminates any confusion if you forget a command's name or if you have more than one command with the same name. Command numbers are also used when programming macros (see commands 053 and 056), setting DTMF execution masks (commands 130 and 131) and several other things. Remember that you use the command name to execute the commands; you sometimes use the command number as part of the information you enter after a command name. When you execute a command from the serial port, you can enter the command name just as you would from a radio or the reverse patch, hitting enter instead of unkeying when you are finished. That is why the prompt you get when you press enter is "DTMF>"; you can enter digits just like they were DTMF digits. There is also a way to execute commands from the serial port using the command number. This is handy because the command number never changes. To execute a command using its number, just put an N at the beginning of the line, followed by the command number and any other digits that command might need (see command 080 for information about how this works internally). We could rename command 009 to ABC from the serial port just as we did from the radio, by entering "010 009 ABC" and pressing enter (spaces are always accepted but never required). But if the name of command 10 was changed, that would no longer work. If we enter "N010 009 ABC", it will work even if command 10 has been renamed because the N makes the controller use the command number for command 010 rather than its name. This is especially useful if you store a list of commands in a file on a computer (so you can upload the whole file to the controller and set it up all at once), as you don't have to worry about whether any of the commands you use in that file have been renamed. The N cannot be used from a radio, since there is no DTMF digit N. You wouldn't want it to be possible from a radio anyway, or it would be a major security problem. Converting Command Name <--> Command Number: Command Number ---> Command name is accomplished with Command C011 If you have forgotten the name of command number 009, you can find out what it is by entering "011 009" and unkeying or pressing enter, or you can just change it to the name you want it to have with 010. Command Name ---> Command number is accomplished with Command 012 If you know that entering a command name of "ABC123" causes a command to execute but you don't know what command number it is executing, you can use command 012 to find out by entering "012 ABC123" and unkeying or pressing enter. Advanced Command Naming Topics: You probably don't need to read this section, but it is here just in case. If it doesn't make sense to you, just skip it. The controller has a table which it uses to keep track of the information for each command. This information is used when the controller tries to find out what command you have entered the name for. If more than one command have the same name, it can also be used to intelligently figure out which one you wanted. Some of the entries are: Command name (including the length of the name). Data length: that is how many digits, if any, are needed after the command name. If the data length is not zero, whether the amount must be exact or whether more digits can be entered. DTMF execution mask (see command 130) User level required to execute (see Chapter 18) For example, Command 009 would have a data length of zero, command 000 would have a data length of 2 which must be exact, and command 036 would have a minimum data length of 3, but could be longer. Other checking such as making sure that the data for 036 is a multiple of three digits and limiting the maximum length is done by the commands themselves. Where the checking is done is important. The checks that can be done with the information in the table can be used to help figure out which command you want to execute when the names are ambiguous, while the checks that are done within the commands themselves are too late. When you enter a command and unkey or press enter, the controller scans the whole table of commands looking for a match. It ignores any commands that would be blocked by the DTMF execution mask or that require that you log on using a password to execute. It also ignores any that it knows have the wrong number of data digits after the command name (using the information in the table as discussed above), although there are some cases where it can't tell until the command is chosen and causes an error. From the remaining commands, it chooses the one with the longest name that matches what was entered. In case of a tie, it chooses the one with the lowest command number. For example, if you have commands named "1", "12", "123", "1234" and "12345" and you enter "12399", assuming that all of them pass the initial execution mask and password and data length checks, the controller will select the command named "123" and will execute it with the data digits "99". That is it will find the longest match, then use the rest of the digits as data. Keep this in mind when you change command names to be less than three digits. If you change the "Retrieve Public Mail" command (177) to have the name "12", then enter "123" to get the mail from mailbox 3, you may instead execute command "123" because it also matches and has a longer name. If command 123 needs additional digits after the command name, the controller will figure out what you mean, but sometimes it just can't tell. So when you rename commands, keep in mind that any name that is the same as the beginning of another name might be ambiguous. This ability of the controller to find the longest matching name can be used in several practical ways. For example, command 000 connects two ports together. It normally sends "X connect Y" as the voice response. If you have a repeater on port 1 and a link to another site on port 2, you might want the message to be "Link up" instead. You could make a macro named "00012" or "00021" that would connect the two ports and send that message. Then entering "00012" or "00021" would cause your custom message to be sent, while "00013" or any other command starting with "000" would access the normal command 000 and cause the normal "X connect Y" message. Another example: your autopatch up code is '*' and your autodial slot is number 43. Pressing "*43" normally causes the response, "Autodial 43". You want to make it say "KC7HXB home" instead. To do this, make a macro called "*43" and make it speak that voice response, then make the call. '*' followed by any other number will still make it say "Autodial", but "*43" will find the macro and cause your custom message. This technique can also be used to turn off the time out timer for emergency numbers. It is possible, although not recommended, to give several commands the same name. For example, 000, 009 and 036 could all be named "ABC" and the controller would always be able to figure out which one you wanted because of the information stored in the command table. Command 000 always takes exactly two data digits, 009 never takes any, and command 036 requires three or more. So "ABC" would select command 009, "ABC12" would select command 000 and connect ports 1 and 2, and "ABC001002003" would make command 036 speak "one two three". This feature is most often used when trying to clone the command codes used on a previous controller, using more than one command on this controller. In summary, the controller lets you name commands just about any way you want to, even if it is confusing for you and it. It does its best to figure out what you mean, using the data length, DTMF execution masks and passwords to eliminate some possibilities, but sometimes it is impossible. If you can't get it to work the way you want it to, check the command names with commands 011 and 012, then start naming them back to their original names with 010 until the confusion goes away. The most common confusion is having one command that is named the same as the beginning of another command, so the longer one gets executed when you expected the shorter one. When all of the commands have their original names, there is no confusion because every command has its own unique three digit name, the command number. 010: Re-Program Command Names This command allows you to re-name the command names on the controller. The names can be from 1 to 6 digits in length. <010> xxx yyyyyy Shortcut: If you want to change the first few digits of a whole range of command names, check out command 062. Notes: You should avoid renaming command 080, or the 'N' method of entering commands from the serial port will quit working. See Appendix F for more information about using 'N'. Parameters: - 010 is the default command name. - XXX is the command's number. It is the same as the last three digits of the command name as listed in the manual. Examples: the command number for this command (010) is 010. For command 123, the command number is 123. The command number is always three digits. Renaming the command does not change the command number - you still use the command number as listed in the manual. - YYYYYY is the new command name. -- You only enter as many digits for the command name as the length you want the new name to be. You do not need to enter any leading digits for the command name. Acceptable entries: XXX Y - New command name is 1 digit in length XXX YY - New command name is 2 digits in length XXX YYY - New command name is 3 digits in length XXX YYYY - New command name is 4 digits in length XXX YYYYY - New command name is 5 digits in length XXX YYYYYY - New command name is 6 digits in length Default: - Command names begin with 000 and end with 999 Voice Response: "Change " The new name is not read back for security. To check that the command was renamed correctly, use "011 ". Example #1: Want to re-name command 013 to ABC12 1) Command Number is 013 2) New command name is ABC12 3) 010 013 ABC12 D or unkey or 4) Voice response: "Change thirteen" Example #2: You changed your mind. Now you want command number 013 (which we just renamed to ABC12) to ABC123 instead. 1) Command Number is 013 2) New command name is ABC123 3) 010 013 ABC123 D or unkey or 4) Voice response: "Change thirteen" Note that the current command name does not matter at all, only the command number (the last three digits of the command name in the manual) and the new name. 062: Change the Beginning of Command Names This command allows you to change the first one, two or three digits of the names of a range of commands. If you specify one digit, all of the command names in the range you specified will become four digits long. If you specify 2, they will be 5 long (and 3, 6). The last three digits of a command's name can not be changed with this command (see command 010). This is to avoid accidentally assigning the same name to multiple commands. <062> bbb eee d Change the first digit of the name in a range <062> bbb eee dd Change the first and second digits of the name in a range <062> bbb eee ddd Change the first, second and third digits of the name in a range <062> bbb eee Strip off enough leading digits to make each command name three digits or less. This will "undo" most of the changes made with the above formats. Parameters: - 062 is the default command name. - BBB is the number of the first command in the range that you want to change - EEE is the number of the last command in the range that you want to change - D or DD or DDD are the new first digits of the command names Notes: You should avoid renaming command 080, or the 'N' method of entering commands from the serial port will quit working. See Appendix F for more information about using 'N'. Any commands in the range that have names shorter than three digits long will have zeros added before their names to make them three digits long before this command changes the other digits. For example, 062 010 050 A changes C010 to A010, 123 to A123, A1 to A0A1, and # to A00#. Example 1: You want to change the names of all of the commands in the controller to start with '#' so that they can be executed from a 12-key touch tone pad: <062> 000 999 # D or unkey or Example 2: You want to make the names of commands 010 through 050 more difficult to guess by making them 6 digits long, starting with the digits 96C: <062> 010 050 96C D or unkey or 011: Recall Command Name This command allows you to recall the name of a command. It also tells you whether it requires more digits to be entered after the command name, if so how many, and whether more digits than that will be accepted. You specify the command number (the name of the command in this manual) and the controller will look up its name. <011> xxx Parameters: - 011 is the default command name. - XXX is the command number ranging from 000-999 Voice Response: The voice response is XXX YYYYYY 'ED' (Number of Digits of Extra Data) -- "ED" signifies that the following number is the amount of additional data needed for that command. -- If the word "Variable" is spoken, the controller will accept more than the specified number of digits. If not, exactly that many digits must be entered. See the discussion about command names and numbers at the beginning of this chapter for more information. Parameters: - 011 is the default command name. -- This command recalls the command number for the associated command name - YYYYYY is the command name with default command name of 000-999 Voice Response: The voice response is "Command Number (000-999)" is YYYYYY 012: Find Commands Named ... This command tells the controller to find all of the commands that have the name you specify. Normally it will only find one command, but if you have several commands with the same name, it will list them all. <012> y..y Parameters: - 012 is the default command name. - Y..Y is the command name with default command name of 000-999 Voice Response: The voice response is "y..y is , ..." or "y..y is not used" if there are no commands that have that name. Blocking Execution from Certain Ports Purpose of these commands: The following two commands allow you to mark (or unmark) certain commands so that they can not be executed from certain ports. You might want to use them to make it so your autopatch can not be accessed from the link ports. If you are using one of the ports as a control port, you could make all of the commands in the controller so they could only be executed from that control port. You could call these commands from the scheduler to disable some or all of the commands at night. This adds a lot of security to your controller. Caution: Because these commands can keep you from executing commands, they can lock you out of your own controller. If you have a terminal or computer hooked up to the serial port, these commands can not lock you out, so you don't have to worry about it. Also, you can always re-initialize the controller (see Appendix D), but that erases all of your programming and you have to be at the site to do it. In other words, be careful what commands you block and what ports you block their execution from. If you don't want to use these functions and you want to erase their names so that they can not be entered accidentally, enter the following commands: Command 010 130 D or unkey or Command 010 131 D or unkey or These commands erase the names of command numbers 130 and 131 so that they can not be executed without renaming them to a valid name. If you think you have locked yourself out, execute the following command from every port you can get touch tones to, or from the serial port. If they are executed they will allow access to every command from every port and the reverse autopatch. Command 131 x 000 999 D or unkey or --- x is the port number you are trying to restore access to 130: Block Command Execution From Port This command allows you to block execution of a command or a range of commands by a port. Before using it, please read the cautions on the previous page. <130> ccc Recall which ports are blocked from executing this command <130> p ccc Block execution for a single command <130> p ccc ddd Block execution for a range of commands Parameters: - 130 is the default command name. - P is the port to block access by (use '*' for the current port, see Appendix L) - CCC is the first command number to block - DDD is the last command number in the range of commands to block 131: Allow Command Execution From Port This command allows you to reverse the effects of Command 130 and allow the specified port to execute a command or range of commands again. This command is not dangerous - it can not lock you out of your own controller. <131> ccc Recall which ports are blocked from executing this command <131> p ccc Allow execution for a single command <131> p ccc ddd Allow execution for a range of commands Parameters: - 131 is the default command name. - P is the port to allow access by (use '*' for the current port, see Appendix L) - CCC is the first command number to allow - DDD is the last command number in the range of commands to allow Chapter 6: CW, DTMF, Voice and DVR Messages This chapter deals with all of the different types of messages that can be sent from the controller: CW, DTMF, synthesized voice and real voice from the digital voice recorder. Sending of CW Messages - CW speed and tone control DTMF regeneration - Regeneration parameters Send a Voice message Play, Record and Erase a Digital Voice Recorder message Generate one and two tone sequences DTMF Keypad test The controller normally figures out which transmitters each message should go to. Responses to commands go to the port that executed the command, IDs go to the port that needs them, and courtesy beeps go to all of the repeaters that could hear the audio from the receiver that caused the ID. Almost all of these defaults can be overridden by the user, if you so desire. For more information about how the messages are routed and how you can change the default routing, see Chapter 16 and Appendix A. 030: Send a CW Message This command allows you to send a CW message. It will be sent to the ports that are in the audio routing variable at the time this command is executed (for more info, see Appendix A). The message will be sent at the speed and frequency that has been set up for the specific port with 042 and 043. <030> cc..cc Parameters: - 030 is the default command name. CC is the CW data, two digits per character CW XX . CW XX . CW XX . CW XX . CW XX 0 00 . A 10 . K 20 . U 30 . SPACE 40 1 01 . B 11 . L 21 . V 31 . PAUSE 41 2 02 . C 12 . M 22 . W 32 . DVR 1 42 3 03 . D 13 . N 23 . X 33 . DVR 2 43 4 04 . E 14 . O 24 . Y 34 . DVR 3 44 5 05 . F 15 . P 25 . Z 35 . 6 06 . G 16 . Q 26 . / 36 . 7 07 . H 17 . R 27 . 0 37 . 8 08 . I 18 . S 28 . ? 38 . 9 09 . J 19 . T 29 . AR 39 . Notes: This table is duplicated in Appendix C for ease of reference. Sending the "CW" character 42, 43 or 44 actually plays one of the internal DVR messages. 031: Send a DTMF Sequence This command allows you to send DTMF tones. For each DTMF digit sent, two digits must be entered (that allows special characters like pause and the force-execution digit (see command 078) to be sent). They will be sent to the ports that are in the audio routing variable at the time this command is executed (for more info, see Appendix A). See Command 044 to set up the duration of the tones and pauses between tones. See command 069 (below) for an alternate way to send DTMF tones. <031> DD..DD Parameters: - 031 is the default command name. - DD is the DTMF data (See Below) Number DTMF Digit 00 0 01 1 02 2 03 3 04 4 05 5 06 6 07 7 08 8 09 9 10 A 11 B 12 C 13 D 14 * 15 # 16 Example: Want to send the DTMF data '0 0 0 1 1 D' <031> 00 00 00 01 01 13 D or unkey or Notes: When DTMF is being generated, audio from receivers that would otherwise be sent on that transmitter is muted. That prevents the receiver audio from mixing with the DTMF digits, which could make them hard to decode. Receiver audio is also muted between generated DTMF digits (the duration of that pause can be set with command 044). 069: Send a DTMF To Specified Transmitter This command allows you to send DTMF tones to a specified transmitter. The digits are sent as entered, with one DTMF digit sent for each DTMF digit entered (because of that, the force- execution digit (see command 078) cannot be sent with this command - use command 031 if that is necessary). See Command 044 to set up the duration of the tones and pauses between tones. <069> T D..D Parameters: - 069 is the default command name. - T is the transmitter number the DTMF digits should be sent to (use '*' for the current port, see Appendix L) - D..D are the DTMF digits to be sent. Example: Send DTMF "026" out transmitter 2: <069> 2 026 D or unkey or Example #2: Make a macro to send user-entered DTMF digits out transmitter 2: 010 500 ABC ; name macro "ABC" 067 500 01 1 ; allow macro to take data (see command 067) 055 500 ; make sure macro is empty 056 500 069 2 ; user-entered data will be appended here Now entering "ABC 026" will cause DTMF "026" to be generated out transmitter 2. Example #3: Same as Example #2, but send a 'D' after the user-entered digits (if 'D' is the force- execution digit for whatever is listening to that transmitter, it will make the command execute right away). Add the following onto the macro started in Example #2: 056 500 037 2 ; send the following data out TX 2 056 500 031 13 ; send DTMF 'D' Notes: Remember that this command cannot be used to send the force execution digit (usually 'D') of the port that is entering the command because as soon as that digit is pressed, the command will be executed. Example #3 above shows one way to deal with this. See command 078 for more information about the force-execution digit. If this command is entered from the serial port, any invalid DTMF digit (anything but 0..9, A..D, * and #) will be sent as a pause (and "Debug code 38" will be output on the serial port). Spaces will not have any effect, as they are always stripped out of commands entered from the serial port before the controller executes them. When DTMF is being generated, audio from receivers that would otherwise be sent on that transmitter is muted. That prevents the receiver audio from mixing with the DTMF digits, which could make them hard to decode. Receiver audio is also muted between generated DTMF digits (the duration of that pause can be set with command 044). 036: Send a Voice Message This command allows you to send a voice message out of the radio ports on the controller. This is handy for building voice messages for macro sequences, sending voice IDs, etc. Which ports will send the message is determined by the current audio routing variable at the time the command is executed (see Appendix A). <036> vvv..vvv Parameters: - 036 is the default command name. - VVV is the Voice word to be spoken -- See Appendix B for voice word numbers Note: if you want the voice message to stop if someone keys up in the middle of the message (a polite voice message), see commands 063 and 064. These commands are often used for IDs. 066: Send a Voice Message Using English Words This command allows you to send a voice message out of the radio ports on the controller, just like command 036 does. The difference is that you have to look up word numbers to use command 036, while this command lets you just type in the words in English, with underscores between the words. If you enter a word that isn't in the controller's voice library, it will spell it. Since DTMF keypads only have the letters A..D (if that), this command is only useful when working from the serial port. There is no polite version of this command (see commands 063 and 064). <066> w..w Parameters: - 066 is the default command name. - w..w are the words to be spoken, in English, with underscores between words Example: 066 this_is_a_test_message Sending DVR-1 Messages: If you have the optional DVR-1 (Digital Voice Recorder), you can include DVR tracks in the messages you generate with this command. Simply put "DVRxxx" where 'xxx' is a track number wherever you want the DVR track to go in the message. For example: "066 this_is_a_test_pause_DVR123_repeater_DVR32" will make the synthesized voice speak "This is a test", then the DVR will play track 123, then the synthesized voice will speak "Repeater", and finally the DVR will play track 32. 040: Send One or Two Tone Sequence This command causes a tone "sequence" to be sent out the ports specified by the routing variable (see Appendix A for information about the routing variable). A "sequence" is composed of one or two tones which are generated simultaneously for a specified duration and followed by a specified pause. Most courtesy beeps use only one tone at a time, although many have several tones in sequence. This type of courtesy beep would be generated by calling this command several times from a macro, sending a one-tone chord each time (see examples on the following pages). DTMF digits and dial tone are familiar two-tone combinations, and can be easily generated using this command. Sequence Command Type Single Tone <040> ttt ppp ffff Single Tone <040> tttt pppp ffff Dual Tone <040> ttt ppp ffff gggg Dual Tone <040> tttt pppp ffff gggg Parameters: - TTT or TTTT is a number representing the duration of the tone in 10mS increments. If you use four digits for the duration of the tone, you must also use four digits for the duration of the pause. The tone duration is limited to 60 seconds (6000). - PPP or PPPP is a number representing the duration of the pause to follow the tone in 10mS increments. If you use four digits for the duration of the tone, you must also use four digits for the duration of the pause. The pause duration is limited to 60 seconds (6000). - FFFF is the frequency of the primary tone in hertz. All four digits must be entered. - GGGG is the frequency of the secondary tone in hertz. All four digits must be entered. It is only used when you want both tones active at the same time, like a DTMF tone. If you want a beep at one frequency then a beep at another frequency, call this command twice from a macro and only specify one frequency each time. Notes: The RLC-Club does not have the hardware to send arbitrary tone frequencies to the telephone. It can send DTMF tones. If you attempt to send a dual tone to the telephone with this command, it will actually be sent as a DTMF '1' regardless of the frequencies you specify. The Deluxe II does not have the ability to generate tones on transmitter 6 at all. It can send a beep by speaking "word" 598 with command 036. Note about Courtesy Beeps The RLC-Club Deluxe II courtesy beeps are not simply a programmable beep. When it is time to send a courtesy beep, the RLC-Club Deluxe II decides which ports should receive the courtesy beep, sets the audio routing variable to those ports (see Appendix A), and calls that port's courtesy beep automatic macro (see Chapter 8). This makes it possible for you to make your courtesy beep do a lot more than just beep. If you call command 040 (send One, Two or Three Tone Chord), it will beep. If you call 040 more than once in the courtesy beep macro, it will beep more than once (examples below). If you call 036 (speak voice message), you will get a voice message for your courtesy beep. If you call 030, it will send CW. If you call 031, it will send DTMF. If you really want to, you can do several of the above. Since most people want a sequence of beeps for their courtesy beep, we will provide some examples. Note that to get a single-beep courtesy beep, you just call 040 once from the courtesy beep macro. To get a three tone sequence, you call 040 three times within that macro. Each time command 040 is called, it can send one or two simultaneous tone frequencies. Below are some widely used courtesy beep sequences. Examples: All tone frequencies are in hertz. All times are in milliseconds. Sequence Name Tone 1 Tone 2 Duration Pause Command to Program Beep Replace "mmm" with macro num 1 - Bumble Bee 0330 N/A 100mS 0mS 053 mmm 040 010 000 0330 .... 0500 N/A 100mS 0mS 056 mmm 040 010 000 0500 .... 0660 N/A 100mS 0mS 056 mmm 040 010 000 0660 2 - Yellow Jacket 0330 N/A 50mS 0mS 053 mmm 040 005 000 0330 .... 0500 N/A 50mS 0mS 056 mmm 040 005 000 0500 .... 0660 N/A 50mS 0mS 056 mmm 040 005 000 0660 3 - Shooting Star 0800 N/A 100mS 0mS 053 mmm 040 010 000 0800 .... 0800 N/A 100mS 0mS 056 mmm 040 010 000 0800 .... 0540 N/A 100mS 0mS 056 mmm 040 010 000 0540 4 - Comet 0500 N/A 100mS 0mS 053 mmm 040 010 000 0500 .... 0500 N/A 100mS 0mS 056 mmm 040 010 000 0500 .... 0750 N/A 100mS 0mS 056 mmm 040 010 000 0750 5 - Stardust 0750 N/A 120mS 0mS 053 mmm 040 012 000 0750 .... 0880 N/A 80mS 0mS 056 mmm 040 008 000 0880 .... 1200 0880 80mS 0mS 056 mmm 040 008 000 1200 0880 6 - Duncecap 0440 0500 200mS 0mS 053 mmm 040 020 000 0440 0500 .... 0440 0350 200mS 0mS 056 mmm 040 020 000 0440 0350 7 - Dial Tone 0440 0350 100mS 100mS 053 mmm 040 010 010 0440 0350 8 - Low-High Beep 0500 N/A 100mS 0mS 053 mmm 040 010 000 0500 .... 0665 N/A 100mS 0mS 056 mmm 040 010 000 0665 9 - High-Low Beep 0665 N/A 100mS 0mS 053 mmm 040 010 000 0665 .... 0500 N/A 100mS 0mS 056 mmm 040 010 000 0500 10 - Cover Tone 0440 N/A 200mS 300mS 053 mmm 040 020 030 0440 11 - Audible Ring Tone 0440 0480 400mS 400mS 053 mmm 040 040 040 0440 0480 Example: I want port 1's courtesy beep to be number 5 as listed above. 1) Locate the courtesy beep macro for port 1 in Chapter 8. - 256 is Port 1's courtesy beep macro 2) Command 055 erases the old contents of a macro 055 256 D or unkey or 3) Command 056 appends a command onto the end of a macro - we will do the first tone 056 256 040 012 000 0750 D or unkey or 012 is the duration of the beep in 10 millisecond increments 000 is the duration of the pause in 10 millisecond increments 0750 is the frequency of the tone in hertz 4) Command 056 appends a command onto the end of a macro - the second tone 056 256 040 008 000 1200 D or unkey or 008 is the duration of the beep in 10 millisecond increments 000 is the duration of the pause in 10 millisecond increments 1200 is the frequency of the tone in hertz 5) Command 056 appends a command onto the end of a macro - the third beep - It is a dual tone beep 056 256 040 008 000 1200 0880 D or unkey or 008 is the duration of the beep in 10 millisecond increments 000 is the duration of the pause in 10 millisecond increments 1200 is the frequency of one tone in hertz 0880 is the frequency of the other tone in hertz 6) Now when port 1's courtesy beep needs to be sent, the courtesy beep macro will call Command 040 three times to generate the three beeps. 041: Set/Recall Courtesy Beep Settings This command allows you control several options for courtesy beeps. In most cases the default values will work fine, so you may not need to use this command at all. One thing this command allows you to do is to turn courtesy beeps on or off for a selected transmitter. Normally courtesy beeps are sent out of repeater transmitters and not out of link transmitters, so if that is what you want, you won't have to change anything. If you want a courtesy beep out of a link transmitter or you want to turn courtesy beeps off for a repeater transmitter, then you should use this command. If you want a particular receiver to quit generating courtesy beeps (to be sent out any transmitter), erase the courtesy beep macro for that receiver (see Chapter 8 for more details about the courtesy beep macros). Normally courtesy beeps are not sent when using the autopatch or HF remote base. This command allows you to change that. Normally the time out timers are reset each time a receiver unkeys. This command lets you change that, so they aren't reset until the courtesy beep for that receiver is sent. This setting may help discourage "tailgating." <041> p e Enable/disable courtesy beeps <041> p e a Enable/disable, autopatch <041> p e a h Enable/disable, autopatch, HF <041> p e a h t Enable/disable, autopatch, HF, TOT Parameters: - 041 is the default command name. - P is the selected port (1..6) - E sets the conditions under which courtesy beeps are enabled E Description 0 Disable courtesy beeps for this transmitter 1 Enable courtesy beeps for this transmitter only if it is a repeater (the default) 2 Enable courtesy beeps for this transmitter, even if it is a link - A - 0 to disable courtesy beeps during autopatch calls (the default), 1 to enable them for this transmitter. - H - 0 to disable courtesy beeps while using HF remote base (the default), 1 to enable them for this transmitter. - T - 0 to reset the time out timer for this receiver when the receiver drops (the default), 1 to wait until the courtesy beep. Setting it to wait for the courtesy beep will encourage users to not to reply until the courtesy beep has been sent to avoid being cut off by the time out timer. Once a receiver has timed out, even a momentary unkey will clear the timed-out condition (since no courtesy beep is sent at that time, no delay is necessary). 042: Set CW Speed for a Selected Port This command allows you to set up the CW systems speed in words per minute. The maximum CW speed the FCC allows for identification is 20 WPM, but the controller will handle 05..50 words per minute. <042> p ss Parameters: - 042 is the default command name. - P is the selected port (1..7) - SS is the words per minute send value Default: All ports default to 20 words per minute 043: Set CW 2-Tone Frequencies for a Selected Port This command allows you to set up the CW tone frequencies used by the CW system. <043> p aaaa Set CW to a single tone <043> p aaaa bbbb Set CW to dual tones Parameters: - 043 is the default command name. - P is the selected port (1..7) - AAAA is the first tone frequency (0000..9999) Hz - BBBB is the second tone frequency (0000..9999) Hz Default: Tone 1 is set to 1064 Hz. Tone 2 is set to 0000 Hz. Notes: You should not set "aaaa" and "bbbb" to the same value or they will cause the output of the two tone generators to be superimposed. Depending on the phase shift between them, the amplitude may be louder or software than a single tone, and may change at seemingly random times. 044: Set Up DTMF Regenerate Parameters This command allows you to set up the DTMF regenerate parameters for each attached port. You may need to use this command to slow your DTMF tones down if a scanning DTMF decoder is on any of the attached systems that you want the RLC-Club Deluxe II to control. <044> p aaaa bbbb Parameters: - 044 is the default command name. - P is the selected port (1..7) - AAAA is the duration of the DTMF sequence in 10mS steps (0000..9999) - BBBB is the pause between DTMF digits in 10mS steps (0000..9999) Default: Both duration and pause set to 100mS 051: Start Dial-Tone This command allows you to generate a dial tone down for a given time down the port that requested this command. This command is used to give you an indication that access to the controller has been accomplished. This is not pre-access, simply dial tone generation. The dial tone is routed to the port that DTMF requested the command. This command is used in conjunction with the pre-access macros. <051> Parameters: - 051 is the default command name. . Notes: How to cancel the dial tone once it is running: 1) You can cancel the dial tone with a DTMF digit on the port dial tone is present. 2) When the dial tone timer expires (See Command 020) 063: Send a Polite Voice Message This command is identical to 036 except that audio from receivers is given priority over the voice message. If a receiver that is on the same port as, or is connected to, any transmitter that is sending the voice message keys up, the voice message will be discarded so you can hear the receiver instead. In other words, if someone is talking, the controller won't interrupt (it is "polite). If someone interrupts the controller (keys up while it is speaking), it will finish the word it is currently speaking and then throw the rest of the message away. This is commonly used for speaking scheduled messages, such as reading the time at the top of every hour. It could also be used for IDs, but if you want a CW ID to be sent when the voice ID is interrupted, use command 064 instead. <063> vvv..vvv Parameters: - 063 is the default command name. - VVV..VVV is a list of synthesized voice words to be spoken (See Appendix B for word numbers) Example: Speak the time only if it won't play over someone talking: "063 810". Note that word 810 is a special word that speaks the current time. To put that command into macro 500, enter: "053 500 063 810". You can then call macro 500 from a macro, the scheduler, a tail message, etc. to speak the time politely. Notes: The autopatch will not interrupt polite voice messages. In other words, a polite voice message that is spoken to the autopatch port will not be interrupted by the autopatch "receiver," even though it is always active during a call. 064: Send a Polite Voice Msg, If Interrupted Execute Cmd This command is identical to Command 063 except that if a receiver is active and causes the voice message to be thrown away, it will cause another command to be executed. This is used to make a voice ID that gets interrupted cause a CW ID to be sent instead (see the example below). <064> ccc vvv..vvv Parameters: - 064 is the default command name. - CCC is the command number to execute if the message is interrupted - VVV is the Voice word to be spoken -- See Appendix B for voice word numbers Example: You want to program a polite voice pending ID message for port 1 that will send a CW ID if it is interrupted. Since the first pending ID for port 1 is sent by macro 226, we will program that macro to execute command 064. We will tell command 064 to either speak the voice ID, or if it is interrupted, to execute the impolite ID (command number 250) instead. We will make the voice ID say the words "I D" with are word numbers 039 and 034 (you would want to change this - see Appendix B for other word numbers): 053 226 064 250 039 034 unkey, D or The above string uses command 053 to program macro 226 to execute command number 064. When command 064 executes, it checks for receiver activity. If the receiver is active, it executes command 250 (the impolite ID). Otherwise it speaks the voice message "ID". See Chapter 11 for more information about programming IDs. Notes: The autopatch will not interrupt polite voice messages. In other words, a polite voice message that is spoken to the autopatch port will not be interrupted by the autopatch "receiver," even though it is always active during a call. 163: Keypad Test This command will read back whatever digits are entered. This allows you to check your DTMF keypad and make sure that the controller is accepting all of the digits. The '*' character will be spoken as "Star" and '#' will be "Pound". <163> d..d Parameters: - 163 is the default command name - D..D are the digits to be read back The DVR1 Digital Voice Recorder What the DVR1 is: The DVR1 is an optional device that allows you to record sounds, store them in memory and play them at any time. It can be used to personalize your controller by recording any message or sounds that you want and playing them back for ID messages or in place of most other synthesized voice messages. Some of these messages are played in response to commands that you or the users enter; others are played at certain times, such as for an ID. Both types of messages will be described below. DVR Tracks: All DVR recordings are stored in numbered "tracks." Certain tracks have special purposes and are played automatically at certain times. Others are available for you to use in any way you wish. The length of each track is limited only by available memory. Each track uses only as much storage space as is actually needed. The first 250 tracks (numbered 000..249) have no predetermined use - you may use them for ID messages, command responses (by calling Command 173 from a macro), or anything else you can think of. Tracks 250..260 or so are used for prompting. They are discussed further in the section below titled "Recording the Prompting Tracks". The remaining tracks are not directly accessible by number. They are used to support the mailbox features and are automatically accessed by the mailbox commands. Public Mailboxes: The DVR uses special internal tracks to provide two types of mailboxes: public and private. Both types allow you to leave messages for other repeater users. You can leave a message in a public mailbox by simply entering the "Leave Public Mail" command (after setting up the prompting tracks as described below). The DVR will then ask you who the mail is for. You key up and say their name or call sign. The DVR will then ask you to record your message. When you are through, it will tell you that your message has been stored. You can check if there is mail for you by simply entering the "Check Public Mail" command. It will list the names or call signs of the people that there is mail for, or will tell you that there is no mail. If there is mail for you, you can listen to your message by entering the "Retrieve Public Mail" command. Up to nine public mailboxes can be in use at a time. Private Mailboxes: Private mailboxes allow you to leave voice mail in someone's private mailbox. To do this you have to know the number of their mailbox. There are 500 private mailboxes, so everyone in your club can have their own. Each private mailbox can hold up to five messages at a time. You can retrieve or delete the mail in your own mailbox without affecting anyone else's mailbox. Interfacing: The DVR1 can be ordered with or without an optional rack mount cabinet. There is not enough room to mount it inside of the RLC-Club Deluxe II cabinet. You must have the Deluxe or Deluxe II option to use the DVR1. A DB-25 male-male cable (included) plugs into a connector on the Deluxe/Deluxe II option board and into the DVR. The only other required connection to the DVR is power (12 volts, center positive, plug included). Optional connections include a backup power plug that can be connected to a battery pack or another power supply (make sure ground is common between the supplies) to preserve the messages stored in the DVR if the main power goes out. The remaining connector can be connected to a computer or serial terminal (more about that later). Note that this serial port is separate from the serial port on the controller. Memory Installation and Testing: The DVR supports four different memory configurations, all using 70ns or faster standard 30 pin SIMMs. Either 8 or 9 bit wide SIMMs can be used; the parity bit is ignored. You may be able to find 8 bit wide SIMMs cheaper (they are used in Macs). Each configuration requires a different set of EPROMS in the DVR: Two one megabyte SIMMs (2 megabytes total) Four one megabyte SIMMs (4 megabytes total) Two four megabyte SIMMs (8 megabytes total) Four four megabyte SIMMs (16 megabytes total) If only two SIMMs are installed, they must be in the RAM #1 sockets. Note that all of the SIMMs must be the same size. All of the memory is tested each time the DVR is powered up. If you want to see the results of the memory test, connect a computer or serial terminal to the DVR (it need not be connected to the RLC-Club Deluxe II at this time) and power up the DVR. You should see a printout on the serial screen noting how much memory is expected (based on which version of the EPROMS you have) and then how the memory test is progressing. If the DVR does not run at all, check the power and the serial connection. The DVR will attempt to run even if errors are detected during the memory test. If the memory test indicates that there are many errors, you may have the wrong size or number of SIMMs installed, or the SIMMs may be faulty. If there are only a few errors, you may be able to use the SIMMs with errors in the RAM #2 sockets with only a slight loss of audio quality. Errors in the SIMMs installed in the RAM #1 sockets are likely to cause serious problems. The memory test performed when the DVR is powered up is very thorough and therefore can take quite a while, especially if you have a lot of memory installed, so you may have to wait for it to finish before testing. With 2, 4, 8 and 16 megabytes of memory, the test takes about 20, 40, 80 and 160 seconds (about 2.5 minutes), respectively. Since you won't be powering up very often, this shouldn't be a problem. If you have the serial port connected and the serial screen scrolls constantly after the memory test is finished, it is probably because you don't have the DVR connected to the controller, or the controller is not powered up. Audio Quality/Recording Time: The audio quality of tracks played with the DVR is nearly identical to the original. You will probably not be able to distinguish between a recording and someone talking "live." Technically, the DVR samples and plays audio at 8KHz with 8 bit resolution (256 voltage levels). This uses 64000 bits per second, which is 8000 bytes per second. At this rate, each megabyte of memory will hold 131 seconds of recorded audio. A small portion of the memory is used for other purposes, so the actual amount of storage will be slightly less than 131 seconds per megabyte. In a future software version, it may be possible to record with lower quality to extend the recording time. Adjusting the DVR: There are only two adjustments on the DVR: record level and playback level. Both are preset before the DVRs are shipped, and should not need to be changed, at least for initial testing. When/if you do decide to adjust the levels, the playback level should be set so that the audio is played back at the same volume it was when it was "live". If you decide to change the record level, the playback level should be adjusted again before any judgement is made as to whether the new record level is better or worse. The record level is important because it affects the quality of the recording. If it is set too low, the full resolution of the digital storage will not be utilized and there will be more background noise in the audio than is necessary. If the record level is set too high, the audio peaks will be clipped off and the audio will sound distorted, especially the loudest parts. There are many factors that determine the best level, so experiment with the Audio Check Command and adjust the record level until it sounds the best. Looking at the audio with a scope as it is played back will help identify if the record level is set too loud, as the top and bottom of the waves will be flattened (a little bit of clipping on the louder parts is normal and expected). If you have a computer or serial terminal hooked up, you can also record a message with Command 171 and look at it with the software oscilloscope function to see how much of the available range you are using. The record and playback levels can be returned to the factory settings as follows: Set up a service monitor to generate a 1KHz tone with 3KHz deviation. Adjust the controller to get one volt peak to peak at the audio test point on the controller (the way the controller receive level is normally set up). Turn the generate function off. To make sure that the DVR is set up and working, use an HT to enter Command 170, unkey, key and say something, then unkey and listen. The DVR should play back whatever you said. If it does not, review the interfacing and testing sections above. Now key and enter Command 170 and unkey, then turn the service monitor's generate function on. This will cause the DVR to record the 1KHz tone into track 0. Adjust the voltage at pin 1 of the DVR's audio test bus for one volt peak to peak. When you get it adjusted or after 30 seconds (when the DVR will automatically quit recording), turn the generate function off and enter Command 174 0 D or unkey to erase DVR track 0. Repeat entering Command 171 0 D or unkey, recording the tone and erasing it with Command 174 0 D or unkey until you are satisfied that the record level is set, then record the 1KHz tone into DVR track 0 once more and don't erase it. Play it back by entering Command 173 0 D or unkey. While it is playing, adjust the voltage at pin 3 of the DVR's audio test bus for one volt peak to peak. Command 173 0 D or unkey may be entered as many times as needed to get the level set. This sets the DVR to play back tracks at the exact same level they were recorded at. If the transmit level is set correctly on the controller, playing this track should cause about 3KHz of deviation. Finally, erase track 0 by entering Command 174 0 D or unkey. The Audio Check Command: Before executing any DVR commands on the RLC-Club Deluxe II you should enter Command 182 1 D or unkey to tell the RLC-Club Deluxe II that the DVR is installed. The controller will respond by saying "one". If you do not do this, some of the commands will work, but others will not. The easiest way to test the DVR is to execute the "Audio Check" command. To use it, simply key your radio and enter "Command 170", then unkey. Key up again and say something. When you unkey, the DVR will play whatever you said back to you, then erase it. If this command works, you have the DVR connected and working. You can execute this command as many times as you want to without harm and without wearing anything out. It can also be used to help you know if your signal is noisy into the repeater; just use this command to record a test message and you can listen to your own audio. Yet another use for this command is to find out how much record time (memory) is still available. To do this, start recording and count off the minutes and seconds you have been recording. When the DVR's memory is full, it will stop recording. When you unkey and the message is played back, you will hear yourself count as long as the DVR was able to record before it ran out of memory (this could take a long time if the memory is not almost full - if it takes too long, the max record length timer could stop it before the memory is full). Recording DVR Tracks: Before recording a track, you should make sure it is empty. If a track has already been recorded, you will not be able to record it again until you erase it. All tracks are empty when the DVR is powered up. To record a track using COR to start and stop the recording, you should enter the record command followed by the track number, "171 TTT" (where TTT is the track number), then unkey (to tell the controller to execute that command and get ready to record). Then key up and start speaking your message. When you are finished, simply unkey. The DVR will automatically delete a fraction of a second of the beginning and end of your message to get rid of any noise caused by keying or unkeying. If you wish to record a track without using COR, such as from the reverse autopatch in programming mode, you can use a DTMF digit to start and stop the recording. For example, to record track 0, you could enter "Command 171 000 D". As soon as you release the 'D', the DVR will begin recording. When you are finished speaking your message, press any DTMF digit to stop the recording. The DVR will automatically delete a fraction of a second at the end of your message to make sure that the sound of the DTMF digit is completely erased. Note that some phones (especially ones that can be used as speaker phones) mute about the first second of each phrase you say; this makes recording nice DVR messages with them very difficult. After you have recorded the prompting tracks (described later), you can use a more friendly version of the record command. Command 172 performs the same function as Command 171, but plays a DVR track that says something like "Please record your message now" after you enter the command and unkey (or press 'D'). When recording using either the prompted or non-prompted command, you must start recording within 10 seconds of entering the record command and unkeying or you will have to enter the command again. This is so a record command can't be entered and end up recording someone that keys up an hour later not knowing that the record command was the last thing entered. The default 10 second window can be changed with Command 020; it is the "DVR Start Recording Timer". The only limit on the length of message that can be recorded is the amount of memory that is still available. To keep people from leaving long mailbox messages, the DVR record length limit timer (timer 164) can be set to limit the length of message that can be left. It defaults to 30 seconds, but can be lengthened or shortened as desired using Command 020. You may also need to lengthen your time out timer to record very long messages. Note that because some of the audio switching circuits are shared between the voice synthesizer and DVR, that only one may be playing at a time. If you play an exceptionally long DVR message, it may postpone the sending of synthesized voice IDs and other messages. For this reason, you should keep your DVR messages relatively short. Playing Messages: There are many things that can cause a DVR message to be played. For example, Command 170 records a message, then plays it back automatically. Command 172 plays a message to tell you to start recording a new message, then lets you record it. To simply play a message that has already been recorded, you can use Command 173. It works a lot like Command 036 does with the synthesized voice, playing the messages you request. Command 173 can be called from any macro to provide DVR IDs, courtesy beeps, autopatch off messages, etc. Erasing Tracks: There are several reasons to erase tracks. Tracks that have been recorded before must be erased before they can be recorded again. Tracks that are no longer being used should be erased to make more storage space available for new messages. Once a track has been erased, there is no way to recover it, so be careful when deleting tracks, especially when deleting a whole range at once. Deleting tracks can take several seconds, so don't be surprised if it takes a while before you hear the message erased message. If you are erasing a single message, the controller will continue to run normally while it waits for the DVR to finish deleting the message and send "message erased". If you delete a range of DVR messages with one command, the controller will stop everything else it is doing while it tells the DVR to delete each of the tracks. When it is finished, the DVR will speak "message erased" to let you know it is finished. Recording the Prompting Tracks: There are several special messages that are played automatically at certain times. They should be recorded before attempting to use the prompted record command or the mailboxes. The messages shown below are only suggestions; you can record them to say anything you want them to. To record them, enter the commands and speak the messages shown below. For more information about recording tracks, see the "Recording Tracks" section above. Command 171 250 D or unkey "Please record your message now" Command 171 251 D or unkey "Your message is stored" Command 171 252 D or unkey "Message erased" (track 253 is not used) Command 171 254 D or unkey "Who is your message for?" Command 171 255 D or unkey "There are no messages." Command 171 256 D or unkey "There is mail for..." If you want to see how your messages sound, you can play most of them by entering Command 173 250 (for track 250). Message 256 can not be checked this way, so record it and don't worry about checking it until you try out Command 175..178. If you want to erase one of these tracks so you can record it again, enter Command 174 250 (to erase track 250). After recording these messages, the DVR is ready for use. Flip through the manual and try all of the commands until you are comfortable with them. If you want to erase all of your messages and start over, you can erase them with Command 174 or you can unplug the DVR and controller for several seconds, then power them back up (and wait for the DVR to finish its memory test). The Serial Interface: The DVR includes a serial port for interfacing to a serial terminal or a computer running terminal software. This connection is not needed for normal operation, but it does provide some capabilities that are not available otherwise. A complete list of commands can be viewed by pressing "H" (for "help") at the "DVR>" prompt. Some of these are: The messages in the DVR can be downloaded to a computer with a hard drive for backup, including the public and private mailboxes. In the event that both the main and backup power supplies fail and the DVR's memory is erased or you have to power down to install a software upgrade, you will be able to restore all of your messages. When the messages are downloaded, it is also relatively easy to edit out dead space at the beginning and end of messages. Please note that because the DVR has such a large amount of storage and because serial port transfers are relatively slow, that downloading takes a very long time, like overnight. It can also take up to twice as much space on the hard drive as the amount of memory you have installed in the DVR. A "software oscilloscope" function lets you view a graphical representation of what is stored in any one of the slots. This feature is not real-time and requires that your serial terminal or terminal emulation software supports ANSI cursor control commands (most do). This feature is useful for checking how much of the range of the analog to digital converter is being used. A status display lets you check how much storage time is used for each message and mailbox. This can help you know what you should delete when the memory gets full. If you have connected a terminal or computer to your RLC-Club Deluxe II, all you have to do is unplug the cable from the RLC-Club Deluxe II and plug it into the DVR. The default setting is 9600 baud, N81, the same as the default for the RLC-Club Deluxe II. If you do not already have a cable and your computer or serial terminal has a DB-9 connector, you can use a straight through DB-9 cable (not a null modem cable). If you are using a modem or TNC, note that pins 2 and 3 will have to be swapped (a null modem adapter will do this). If you are using a modem or TNC, you will probably have to set them up to make them work transparently - contact Link Communications if you need more information about how to do this. If everything you type shows up double on your serial screen like this "tteesstt", turn the local echo off on your communications program. The DVR is unavailable to the controller while it is executing a command entered from the serial port. Because of this, most of the serial commands will time out if you do not respond within about 10 seconds. Pressing the escape key will also get you out of most commands. The default baud rate of 9600 baud works well for both uploading and downloading. Faster baud rates are supported, but may not work reliably. Downloading may work at a higher baud rate than uploading. When uploading, you may have to set the character pacing time (check the ASCII transfer settings on your communications program) to avoid overruns. The line pacing can be set relatively small, often to 0. When uploading at high baud rates, if the data that appears on your screen has missing or incorrect characters but you are not getting error messages, the data is probably being uploaded correctly and you can ignore the incorrect characters that you see on the screen. Most errors in uploading are caused by trying to upload to a track that is not empty. If the DVR is reset either by powering it down or by the serial reset commands, the baud rate is automatically reset to 9600 baud. Making DVR-1 Messages Polite: Currently, DVR command 173 is similar to the synthesized voice command 036 in that they are both impolite (see commands 063 and 064 for more information about "polite" messages). There are no DVR commands similar to the synthesized voice commands 063 (speak politely) or 064 (speak politely and do something if interrupted) in this firmware version (they are planned for a future version), but they can be simulated on the DVR-1 (the big DVR, not the small one) by programming macros similar to those shown below. To make polite DVR messages, the DVR-1 must be running V1.50 or later firmware; older versions of DVR firmware will continue to work but will not be polite and may cause the following (harmless) message to be printed to the controller's serial port: "DVR is not responding (1), Error sending command to DVR". Speak polite DVR message (like command 063): 055 500 ; erase macro 500 056 500 036 801 ; start polite mode 056 500 173 ; play dvr tracks 056 500 036 802 ; stop polite mode Speak polite DVR message and do macro 250 if interrupted (like command 064): 055 501 ; erase macro 056 501 036 801 ; start polite mode 056 501 173 ; play dvr tracks 056 501 036 803 250 ; stop polite mode, do 250 if interrupted 182: Enable/Disable RLC-DVR1 This command tells the RLC-Club Deluxe II if an RLC-DVR1 is installed. If you do not tell the controller that a DVR1 is installed, it will not work properly. If you tell the controller that a DVR1 is installed when it is not, it may cause problems, such as the transmitter coming up or staying up when it shouldn't. The internal DVR is always enabled; this command will not affect it at all. <182> 0 DVR1 Not Installed (default) <182> 1 DVR1 Is Installed 170: Record and Play Audio Test This command makes the DVR start recording. When you unkey or press a DTMF digit to stop recording, it automatically plays it back. This is useful for testing the DVR and for checking how your signal sounds into the repeater. To use this command enter 170 and unkey, then key up and talk or enter "170 D" and start speaking immediately. When through speaking, unkey and your recording will be played back immediately. The track is automatically erased after it is played back. <170> Parameters: - 170 is the default command name 171: Record DVR Track (non-prompted) This command makes the DVR start recording a track. To use this command enter Command 171 TTT D or unkey. Either way, you message will be recorded and stored in track TTT. <171> t Record track 0..9 <171> tt Record track 00..99 <171> ttt Record track 000..260 Please note that a DVR track that has been recorded before must be erased before it can be recorded again. This is to avoid accidentally recording over an existing message. Parameters: - 171 is the default command name - T, TT, TTT is the DVR track number (1..3 digits, track 0..260) 172: Record DVR Track (prompted) This command has the same result as Command 171: it records a DVR track. The difference is that after entering the Command 172 TTT and unkeying, this command plays a special DVR track to tell you it is ready to start recording. This is useful because it lets you know that the command has been executed and the DVR is ready. After the prompting message is finished, you can key up and start recording. The disadvantage of this command compared with Command 171 is that you have to wait until the prompting message is finished before you can start recording. If you are recording a lot of tracks, it is faster to use Command 171. <172> t Record prompted track t <172> tt Record prompted track tt <172> ttt Record prompted track ttt Please note that a DVR track that has been recorded before must be erased before it can be recorded again. This is to avoid accidentally recording over an existing message. Parameters: - 172 is the default command name - T, TT, TTT is the DVR track number (1..3 digits, track 0..260) 173: Play DVR Tracks This command makes the DVR start playing the specified track or tracks. They will be heard on the ports that are in the current audio routing variable (see Appendix A), just like the other commands that send tones or synthesized voice are. This is the command that you would use in an ID macro to send a DVR ID. <173> ttt Play single track <173> t..t Play multiple in-a-row tracks <173> ttt ttt..ttt Play multiple separate tracks Parameters: - 173 is the default command name - TTT is a DVR track number. If only one track specified, can enter 1..3 digits. If more than one track is specified, must enter groups of three digits. 174: Erase DVR Tracks This command makes the DVR erase the specified track or range of tracks. There are several reasons to erase tracks. Tracks that have been recorded before must be erased before they can be recorded again. Tracks that are no longer being used should be erased to make more storage space available for new messages. Once a track has been erased, there is no way to recover it, so use this command with caution, especially when erasing a range of tracks. <174> ttt Erase single track <174> t..t Erase multiple in-a-row tracks <174> ttt ttt..fff Erase multiple separate tracks Parameters: - 174 is the default command name - TTT is a DVR track number to be erased. If only specify one track can use 1..3 digits. - FFF (optional). If specified, DVR tracks TTT through FFF will be erased. FFF must be larger than TTT. Note: If the DVR track for "message erased" is not heard, make sure you have entered Command 182 1 D or unkey to set up the DVR and that the "message erased" track has been recorded. You may have to wait for several seconds after entering the command for the DVR to finish deleting the message and send "message erased". 175: Record Public Mail This command allows the user to record a message and who it is for and stores it in a public mailbox. It uses some of the special tracks to prompt the user to record the name or call sign and the message, and to tell him that the message has been stored. For more information, see the "Public Mailboxes" section at the beginning of the DVR section. <175> Parameters: - 175 is the default command name 176: Check Public Mailboxes This command recalls who has mail in the public mailboxes. The DVR will either play the special track that says, "There is mail for", then the name or call sign for each of the messages that are stored in the public mailboxes or it will play the special track, "There is no public mail". The names or call signs will be spoken in the order that the messages were recorded. If you want to check the public mail without the DVR saying anything if there is no mail, enter "173 256 257". <176> Parameters: - 176 is the default command name 177: Retrieve Public Mail This command allows a user that has mail in a public mailbox to retrieve it. This command is usually used after checking the public mailboxes with Command 176. When you check the public mailboxes with Command 176, you should keep track of where your name or call sign are in the list of people that have mail. For example, if Command 176 says, "There is mail for Joe, Mary, Bob, Jim", and you are Bob, your mail will be stored in public mailbox #3, because your name is third in the list. To retrieve your mail, you would enter "Command 177 3 D or unkey". <177> s Parameters: - 177 is the default command name - s is which mailbox your mail is in (1..9) 178: Erase Public Mail This command throws away the contents of a public mailbox, the last one that was retrieved. It must be used only after retrieving a public mailbox message with Command 177. It erases only the last public mailbox message that was retrieved; all of the others remain unchanged (although they may be moved up to a lower numbered mailbox to avoid leaving gaps). <178> Parameters: - 178 is the default command name 179: Record Private Mail This command allows the user to record a message and store it in a private mailbox. You must know the mailbox number you wish to leave a message in to use this command. Since each user has his own mailbox, there is no need for you to record his name or call sign as with the public mailboxes. <179> sss Parameters: - 179 is the default command name - SSS is the number of the mailbox to leave the message in 180: Retrieve Private Mail This command allows a user to retrieve the mail that has been left in his private mailbox. If he has no mail, the special DVR track "You have no mail" will be spoken. If there is more than one message in his mailbox, all of them will be spoken consecutively. <180> sss Parameters: - 180 is the default command name - SSS is the number of the mailbox get the mail from 181: Erase Private Mail This command throws away the contents of a private mailbox, the last one that was retrieved. It must be used only after retrieving a private mailbox message with Command 180. It erases all of the messages in that mailbox, but does not affect any of the other private mailboxes. <181> Parameters: - 181 is the default command name The Internal Digital Voice Recorder The internal DVR is built into the RLC-Club Deluxe II controller. It gives you only some of the features and much less record time than the DVR1, but it should be enough for you to get your feet wet. It has a total of eight seconds of record time, which can be split into two four second tracks (tracks 1 and 2) or used as one combined eight second track (track 3). Be careful not to confuse the commands for the internal DVR with the commands for the DVR1. On the RLC-Club Deluxe II, you can only record to the internal DVR from receiver 1 or the reverse autopatch. Once messages have been recorded, they can be played back on any of transmitters 1 through 5, but not transmitter 6 or the patch (forward or reverse). 183: Record a Message on the Internal DVR This command allows you to record a DVR message on one of the three internal DVR message tracks. The tracks are limited to 4 seconds for tracks 1 and 2 or 8 seconds for track 3. Track 3 is simply a combination of tracks 1 and 2; don't use track 3 if you are using track 1 or track 2. On the RLC-Club Deluxe II, you can only record to the internal DVR from receiver 1 or the reverse autopatch. <183> s Record a track Parameters: - 183 is the default command name. - S is the DVR track number (1..3) Examples: To record track 3 from a radio, key up, enter "183 3", then unkey to execute this command and tell the controller to get ready to record. After you hear the repeater's courtesy beep, key up and speak the message you want to be recorded. Unkey when you are through speaking. To record track 3 from the autopatch, set your force-execution digit for the autopatch port (port 7) to a '#' using command 078. Then call up on the reverse patch (which should have been set up with command 133) and enter your password. Then enter "183 3" and press the '#' digit. As soon as you release the '#', the DVR will begin recording. When you are done speaking, press the '#' again to tell the DVR to stop recording. Notes: Track 1 = first 4 seconds Track 2 = second 4 seconds Track 3 = Track 1 + Track 2 = 8 seconds See Command 034 to adjust the record level When the DVR stops recording because you unkey or press a DTMF digit, it attempts to back up and erase the squelch tail or DTMF burst so that your message sounds clean. When it stops recording because it reaches the end of a track, it does not back up to avoid wasting record time. The audio test track defaults to using track 1, if track 1 has not been recorded. Otherwise it records on track 2. If you record a message on both tracks then do not use the test track because it will overwrite the second recorded message. 184: Playback an Internal DVR Message(s) This command allows you to playback send one or more internal DVR messages. It will be sent to the ports that are in the audio routing variable at the time this command is executed (for more information about audio routing, see Appendix A). On the RLC-Club Deluxe II, messages can be played back on any of transmitters 1 through 5, but not transmitter 6 or the patch (forward or reverse). <184> s Playback a single message 1..3 <184> s..s Playback multiple messages 1..3 Parameters: - 184 is the default command name. - S is the DVR track number Notes: DVR messages can be intermixed with CW messages and the RLC-Club Deluxe II will make sure that they are sent in the right order. For example, you could write a macro that would send your call sign using the CW generator, then use the DVR to speak "Link Up". Playback of internal DVR messages is only supported on the radio ports, not on the reverse autopatch. See Command 034 for further explanation. 185: Erase Internal DVR Message(s) This command allows you to delete one or a range of DVR messages. If an erased message is later played, it will sound like a short pause. There is no way to "un-erase" a message once it is erased. <185> s Erase a single message <185> s..e Erase multiple messages Parameters: - 185 is the default command name. - S is the DVR track number to erase - E (optional). If E is not specified, only one track will be erased. If E is specified, the DVR will delete tracks S through E. 052: Audio Test using the Internal DVR This command allows a user to test the quality of their audio into the controller using the internal DVR system. When this command is executed the controller will record the audio and play it back. The recording is stopped when either a DTMF digit is detected or the receiver drops. Applications for this command include signal strength readback by audio quality, not just a number; testing the audio of a receiver, and checking adjustment of the DVR's record level before recording a track. This command is similar to command 170 for the optional DVR1. <052> unkey then key up and talk or... <052> D then talk, unkey and listen Parameters: - 052 is the command name Notes: The audio test track normally records on track 1. If track 1 is full it starts recording on track 2. If both tracks are empty the audio test track can be up to 8 seconds in length. Refer to Command 034 to adjust each port's record audio level 034: Adjust each Port's Internal DVR Record Level This command allows the adjustment of the internal DVR's record level for each port. Because the internal DVR uses the tone generation DAC to playback the recorded voice, the level of the tones (CW and courtesy beeps) should be adjusted before adjusting record levels with this command. <034> p Recall Record Level for Port 'p' <034> p lll Set Record Level for Port 'p' to 'lll' Parameters: - 034 is the default command name - P is the port to set the record level for 1 - Port 1 7 - Reverse Autopatch (record only, can not play back) - LLL is the record level adjustment number (000..255) 064 is the default level Notes: Only Ports 1 and 7 (the reverse autopatch) can record on the internal DVR. Ports 1..5 can play back. If you adjust the record volume to high the recording will be 'raspy' Note: This command will not change the level of messages you have already recorded. It will change the level of messages you record afterward. Adjustment: The tone level pot also adjusts the DVR voice playback level. Adjust your tones for a correct level on the port's transmitter. Once your tones are adjusted record a track with the audio test command (052) and verify the record level when the DVR track plays back. If you need to increase the record level execute Command 034 and give it a number greater than 064. If it is too loud or distorted, set the record level to a number smaller than 64. Repeat this process until you reach a level that is correct for the DVR's recording. Adjustment procedures are the same for other radio ports. Port 7, the autopatch, can not play back the recorded DVR message because it does not have a DAC (Digital Analog Convertor). The autopatch is allowed to record because of the increased record quality from the telephone line vs. a radio port. When recording a message from the phone the only means of verifying the recorded message is to play the message back over one of the radio ports. Chapter 7: Serial Port Commands This chapter deals with the following topics: Information about serial transfers RS-232 baud rates Other serial port options Sending serial messages out of the main serial port Sending SPI serial data with the output lines Where the Serial Ports Are: The RLC-Club Deluxe II has a serial port on the motherboard (the closest DB-9 connector to the power jack) that is used for entering commands on the controller. This is called the main serial port. There is also a type of serial data ("SPI") that can be sent with the open collector output lines that is usually used for controlling remote base interfaces (RLC-ICM, Doug Hall RBI-1, or BCD-controlled radios). Controlling what Serial Messages are Sent: This section only refers to the main serial port, since it is the one you use for entering commands and that the controller uses to tell you when there is an error. When the controller is reset (such as when the power is turned on), it sends a serial message that tells you the controller type, software version, etc. Of course you will only see this message if you have a computer or serial terminal connected to the main serial port. If you then type a command on the computer or serial terminal and press enter, the controller will process the command and print on the screen either what it did (except for a few commands that don't print anything) or an error message telling you what went wrong. If you enter a command from a radio using DTMF, the controller normally will not print anything on the serial screen. It "suppresses" that serial so if you are programming from the serial port at the same time someone is entering DTMF commands, the responses to their commands won't confuse you. You can keep the responses to commands entered by DTMF from being suppressed by turning serial suppression off with command 060. This can be handy for figuring out what is going wrong when entering DTMF commands. Commands 162 and 169 bypass the check to see if serial is suppressed so they always print. Since you will normally want serial suppression to be turned on, these commands are useful for sending messages that you always want to be printed, even if the command to send them is entered from a radio port or executed by the scheduler or some other internal device. The RS-232 Serial Protocol: Most serial devices (computers, mice, external modems, serial terminals, etc.) use the RS-232 serial protocol. The main serial port on the RLC-Club Deluxe II is RS-232 compatible. All you need to connect it to a computer, terminal or modem is the proper cable. The SPI Serial Format: There is another type of serial protocol that is totally unrelated to RS-232. It is used for controlling some remote base interfaces, such as the Doug Hall RBI-1, RLC-ICM and BCD radio interfaces. Instead of using a data in and data out line like RS-232, it uses two lines for output: data out and clock out. There is no input to the controller; data is transferred only one way. Since there is a clock line, there is no need to specify a baud rate (although there are a few timing restrictions). The RLC-Club Deluxe II uses the open collector output lines on the Deluxe II board to send this type of serial. It is sent automatically by the RBI-1 / RLC-ICM commands and can be sent manually using command 138. Remember that the outputs are open collector and require pullup resistors (pullups are built into the RBI-1 and RLC-ICM). 024: Set Up RS-232 Serial Baud Rate This command allows you to set up the baud rate for the RLC-Club Deluxe II's main serial port. The baud rate for the main serial port should be set to match the computer, serial terminal, or modem that you have connected to it to program the controller with (it defaults to 9600 baud). If you are using the serial port for controlling an HF remote base (see Chapter 15), the controller will set the baud rate automatically for the type of HF radio you are using. <024> x..x Parameters: 024 is the default command name. x..x is the baud rate. Any baud rate from 300-19200 including non-standard rates can be specified. The baud rate you enter will be rounded slightly to the nearest available rate, but should always be compatible with the actual rate selected. The standard baud rates supported are 300, 600, 1200, 2400, 4800, 9600 and 19200 baud. Example: To set the baud rate to 2400 baud <024> 2400 unkey, 'D' or 060: Set Up Serial Port Options This command allows you to turn several options on or off for the main serial port. Each of these options is discussed below. The first is whether or not the serial port converts all characters that you type to upper case or not. The default is to convert them, because all of the default command names are in upper case (they must be to be executed by DTMF). Converting all of the characters makes it impossible to do a few things however, such as programming serial messages that contain lower case letters. The second allows you to choose whether the controller will send a carriage return and line feed at the end of each line (the default) or just a carriage return. The latter might be useful in situations where the line feed messes up a modem or packet radio. Most communications programs can automatically add the line feeds back in when they receive a carriage return so that the screen will scroll, rather than printing each line over top of the last one. If you are trying to make a modem dial you, you will have to turn line feed sending off or when you send "ATDT" the controller will follow it with a CR/LF (carriage return and line feed). The CR will tell the modem to start dialing. The LF will make it stop dialing - if a modem receives any characters from the controller while it is dialing, it will abort. The third determines whether serial messages that are generated by commands that are executed by DTMF are suppressed or printed. If they are suppressed (the default), the only serial messages that will be printed are: the reset/copyright message, serial responses to commands executed from the serial port (not DTMF), and serial messages sent with Command 162. The fourth is whether the serial is queued (buffered) or not. Normally it is buffered so that the controller can continue to run while the serial is sent in the background. Occasionally, usually for debugging purposes, you may want the serial to be sent before execution continues. In this case, you can turn queuing off. It automatically gets turned on whenever the controller is reset. <060> x y Set case sensitivity and line feeds. <060> x y z Set case sensitivity, line feeds and suppression. <060> x y z q Set case sensitivity, line feeds, suppression and queuing. <060> 0 1 1 1 Set all settings to default values. Parameters: - 060 is the default command name. - X is 1 to make the serial port case sensitive (no automatic conversion to upper case) 0 to make the serial port convert all characters entered to upper case - Y is 1 to send line feeds (the default) or 0 to suppress them - Z (optional) is 1 to suppress serial (the default) or 0 to send serial caused by commands entered from DTMF - Q (optional) is 1 for queued serial (the default) or 0 to send it before continuing 032: Send Serial Message This command allows you to send a custom message out the controller's serial port. If the message is entered with DTMF the serial message will only contain DTMF digits. If the message is entered using the RS-232 port, then the message will contain whatever characters you enter. This command is used to display serial error messages (they are sent from macros 200..219 using this command), among other things. The message will only be sent if you cause this command to be executed from the serial port or if you turn suppressed serial off with command 060, to minimize the amount of stuff being sent out of the serial port. If you want a message to be sent no matter what, use command 162. <032> s..s Parameters: - 032 is the default command name. - s..s is the data to be sent over the RS-232 port -- The message length is limited to the maximum command length (about 200 characters) or if used in a macro, by the space left in a macro (less than 100 characters). If you need a longer message, split it up between several macros and use one macro to call the next macro in the sequence. Voice response: There is no voice response for this command Notes: To change the baud rate, see command 024. Serial output is normally queued (buffered) so that controller operation does not wait for the message to be sent before continuing. Queueing can be controlled with command 060. Spaces are automatically stripped when the controller processes commands, including commands that send serial messages. This allows upload files to contain spaces without affecting the format of the input data. If a user wishes to have a 'space like character' sent the '_' (underscore) data can be used. 162: Always Send Serial Message out the Main Serial Port This command is identical to Command 032 except that it always sends its message, regardless of whether command 060 is set to suppress serial sending or not. 169: Always Send Serial out Main Serial Port by ASCII Code This command does the same thing as Command 162, but lets you enter characters by their ASCII codes. For each character you want to send, you have to enter a three digit number - that character's ASCII code (in decimal, not hex). This allows you to send characters that are not on the keyboard, or to send characters that are not on a DTMF pad when programming by DTMF. For a table of the ASCII codes, see Appendix G. <169> ccc ccc ... ccc Parameters: - 169 is the default command name - CCC is the ASCII code for one serial character. Notes: To send a space with this command, use the ASCII code 032 (hex 0x20). This command does not automatically send carriage returns (ASCII 013) or line feeds (ASCII 010). If you do send a carriage return, the controller may automatically send a line feed afterward (see command 060). 138: Direct SPI Send using Open Collector Output Lines This command is provided only for advanced use controlling SPI devices. Unless you need to control a serial shift register, ignore this command (it could be used to send data to the Doug Hall RBI-1 or the RLC-ICM, but using the specialized commands is much easier). This command accepts data in hex (two digits per byte) and sends that data in an SPI format (with data and clock line) using the open collector output lines on the Deluxe/Deluxe II board. <138> xx Send individual byte <138> xx..xx Send multiple bytes Parameters: - 138 is the default command name. - XX is the hex number (00..FF) representing a byte of data to send. To send codes with 'E' or 'F', you will have to enter this command from the serial port. You may have to change your force execution digit (see command 078) to be able to enter some hex codes. You must enter an even number of XX digits since it takes two hex digits to make one byte of data. Notes: External shift registers like the 74HC164 will decode the shifted data and return it to 1's and 0's for external BCD radio control. Each hex digit entered corresponds with four binary digits. If you are sending only digits 0..9, they can be used as BCD data. Key Entered Data Sent . Key Entered Data Send 0 0000 . 8 1000 1 0001 . 9 1001 2 0010 . A 1010 3 0011 . B 1011 4 0100 . C 1100 5 0101 . D 1101 6 0110 . E 1110 7 0111 . F 1111 The data is output on the pins of the outputs connector shown below: Data Output - Output #7 (Pin 6) Clock - Output #8 (Pin 2) Ground - Pin 1 Chapter 8: Macros How Macros Get Executed: Macros can be executed just like any other commands: you can enter the name of the macro from a radio and unkey (or press the force execution digit), you can enter the macro name from the serial port, you enter an 'N' followed by the macro number from the serial port, etc. In addition, the controller will automatically execute macros at certain times, such as to send an ID or a courtesy beep. The macros that the controller calls in this way are called "automatic macros" because they are called automatically. The automatic macros are listed in this chapter along with descriptions of when they get executed. When the controller is reinitialized (at the factory or if you do it), many of these macros are programmed with examples of what you might want to do: the ID macros speak sample IDs, the courtesy beep macros send beeps and the I/O macros send messages that tell you what changed. You can change what is in any or all of the automatic macros to make them do what you want. Macros numbered 500 and higher are not listed with descriptions, because the controller doesn't have a specific purpose for them; they are called "user macros". They are extras that can be used for anything else you might want to do. You will probably want to keep a list of what you use each one for so you can remember it later. After you program them, you may want to change their names and execute them from your radio with DTMF, program the automatic macros to execute them, or tell the controller to execute them at certain times using the event triggers (see Chapter 20). What a macro is: There are at least two common understandings of what a macro is. The RLC-Club Deluxe II currently supports the more flexible of the two types; eventually it may support both. The kind the RLC-Club Deluxe II supports could be called a "multiple command macro" because it provides a way to execute a sequence of internal commands in response to one command from the user. In other words, this kind of macro contains a list of commands that are executed in order when the macro is executed. If you commonly want to connect your repeater port to a link port and turn DTMF muting on and change your courtesy beep, you could program a macro to execute the appropriate commands. This type of macro is very similar to the macros that many word processors and other computer programs allow you to make to automate things that you do often. The other commonly used kind of macro (that the RLC-Club Deluxe II does not currently support) could be called a "snapshot macro". It allows you to set up the controller the way you like it, take a snapshot of it, and restore the controller to that configuration at any time by recalling the snapshot. While this may be convenient, it is also limiting. Consider an example: you have two stand alone repeaters running off of one RLC-Club Deluxe II controller. You are setting up one repeater today and plan to set up the other tomorrow. You set up the repeater with a certain courtesy beep and take a snapshot. You then set it up with a different courtesy beep and take another snapshot. Now you can easily switch back and forth between the two courtesy beeps just by recalling the appropriate snapshot. The next day you set up the other repeater port in a similar way, with two different courtesy beeps. Now you start having problems. Whenever you change the courtesy beep on one repeater, it messes up the courtesy beep on the other repeater as well, since everything gets stored in one big snapshot macro. You can't make a snapshot macro that does just what you want; it always restores a whole configuration at once. The solution to the dilemma illustrated above is to use multiple command macros that do exactly what you want them to and nothing else. If you want a macro to connect you to Link A and not to Link B, make a multiple command macro to disconnect your repeater from Link B and connect it to Link A. Executing this macro will not interfere with anything else that is going on in the controller like a snapshot would. Advanced Macro Topics: Limits on Macros: Since one macro can call another macro, you may wonder if macro 500 could call 501, which could call 502, which could call 503, etc. until you had called 100 macros or so. The answer is not quite. There are two limits. One is that if the total time it takes the processor to decode and execute the whole chained macro sequence is more than 1/2 second or so, the controller may reset itself. It is unlikely that you will ever reach this limit (it would probably take more than 20 macros all hooked together to even come close to this limit). The other limit restricts how deeply the macros can be nested (called from another macro). This is not a limit on how many commands can be called inside of a macro. It is not a limit on how many macros can be executed from one macro. It is a limit on one macro calling another macro that calls another macro that calls another macro. You can think of it as a limit on how deep an outline can go. For example, you execute macro 500. It calls Command 038, macro 501, and Command 000. This can be shown as the level with Roman numerals: I Call Command 038 II Call macro 501 III Call Command 000 and connect port 1 and 3 Macro 501 could contain Command 007 and call macro 502. Since macro 501 is called from macro 500, it is nested one level deeper, to level 2. This could be shown as capital letters in the outline: I Call Command 038 II Call macro 501 A Call Command 007 B Call macro 502 III Call Command 000 and connect port 1 and 3 Macro 502 could call macros 503,504 and 505. Macro 502 is nested one level deeper than 501, so it is at level 3. I Call Command 038 II Call macro 501 A Call Command 007 B Call macro 502 1 Call macro 503 2 Call macro 504 3 Call macro 505 III Call Command 000 and connect port 1 and 3 Macros 503 , 504 and 505 are at level 4. Note that they are all at the same level. Any commands that are called from these macros will be at level 5. This is about as deep as the RLC-Club Deluxe II will let you nest macros, 5 or 6 levels. If you ever exceed this limit, error macro 209 will be executed. This is the nested macro depth limit. Macros that Accept Data at Runtime: Normally macros must be programmed with all of the data they will need to execute. For example, a macro that dials a phone number could be programmed as follows: 055 500 ; erase macro 500 056 500 112 123 4567 ; call 123-4567 Such a macro will always call the same phone number. It can be executed by entering "500". There is a way to make macros that accept more information at the time they are executed, and pass that data into the commands that are executed by the macro. For example: 055 500 ; erase macro 500 056 500 112 ; phone number will be supplied at runtime contains everything it needs to know to make the call, except for what phone number it is supposed to use. You can tell the controller to get the rest of the information needed to execute the macro at the time you tell it to execute the macro with command 067. For the above example, you could enter: 067 500 07 0 ; make macro 500 accept exactly seven digits Command 067 tells the controller that a macro will need more information at runtime. In this case, we specified that the user would enter exactly seven digits. It would also be possible to let the user enter seven or more digits ("067 500 07 1"), or any number of digits ("067 00 1"). See command 067 for more information. 200..499: Execute an Automatic Macro These commands allows you to manually recall program macro sequences. These sequences are executed automatically by the controller to send IDs, courtesy beeps, alarm analog lines, recall input conditions, etc. These macros are programmed the same way as user macros, but are automatically called by the controller when certain events occur. You can also execute them manually by entering the command name (200 through 499). This is useful for testing the macros to make sure that they are programmed the way you want them to be. They are described in the "Automatic Macro Explanations" section at the end of this chapter. <200>..<499> Parameters: - 200..499 is the default command name. 500..999: Execute a User Macro These commands allow you to execute user macro sequences. These macros are not used by the controller for any specific purpose, so you can use them for any purpose. <500>..<999> Parameters: - 500..999 is the default command name. 055: Erase Macro This command erases a macro. If it is executed after it has been erased, nothing will happen. There is no way to "unerase" a macro that has been erased. <055> mmm Parameters: - 055 is the default command name. - MMM is the command number of the macro to erase. 056: Add Command to a Macro This command allows you to add a command to a macro. If the macro was empty (contained no commands), it becomes the first command in the macro. <056> mmm ccc d..d Parameters: - 056 is the default command name. - MMM is the macro number for this sequence to be stored in - CCC is the command number within a macro - D..D is the additional data associated with command CCC Example: Want to execute command 031 using macro 500 031 with 20 additional digits: 00 01 02 03 04 05 06 07 08 09 (sends 0, 1, 2, 3, 4, 5, 6, 7, 8, 9 in CW) <056> 500 031 00 01 02 03 04 05 06 07 08 09 D or unkey or 053: Erase Then Add Command To Macro This command is just a shortcut for entering command 055 then 056 (to erase then add a command to a macro). <053> mmm ccc d..d The following examples are equivalent: ; Example #1 055 500 ; erase macro (make sure it is empty) 056 500 066 TEST ; make macro speak "test" ; Example #2 053 500 066 TEST ; erase macro then make it speak "test" Parameters: - 053 is the default command name. - MMM is the macro number for this sequence to be stored in - CCC is the command number to be executed by the macro - D..D is the additional data associated with command MMM Example: Want to execute command 031 using macro 500 031 with 20 additional digits: 00 01 02 03 04 05 06 07 08 09 (sends 0, 1, 2, 3, 4, 5, 6, 7, 8, 9 in CW) <053> 500 031 00 01 02 03 04 05 06 07 08 09 D or unkey or 054: Recall Macro Contents This command recalls the contents of a macro so that you can find out what the macro is programmed to do. It does not execute the commands in the macro, only recalls them to the serial screen or speaks them with the voice synthesizer. The format of the response is explained below. <054> mmm Parameters: - 054 is the default command name. - MMM is the macro number to recall Format of the Voice Response: "M" [macro number] "N" [number of commands in the macro] "C" [which command in the macro] [command number] "D" [number of digits of data] [the digits of data] repeat last two lines until all commands in macro have been recalled ? "percent" how many percent full the macro is Example: Recall Default Contents of Macro 200 (Command length not matched error handling macro): You enter the command "054 200 D or unkey or " The serial response is: Macro 200 contains 2 commands: #1 Command #032 with 31 digits of data: Command name length not matched #2 Command #036 with 09 digits of data: 133002028 The voice response is: "M 200" macro number 200 "N2" number of commands in the macro is 2 "C1 32" the first command in the macro is command number 032 (send serial message) "D31" this command has 31 digits of data which are: "Command name length not matched" (speaks each letter, with pauses for spaces) "C2 36" the second command in the macro is command number 9 "D9" this command has 9 digits of data which are: "133002028" the words "Error Two-Hundred" 057: Copy a Macro This command allows you to copy a macro. It erases whatever used to be in the destination macro and replaces it with a copy of whatever is in the source macro. <057> mmm ddd Parameters: - 057 is the default command name. - MMM is the number of the source macro - DDD is the number of the destination macro 058: Erase a Command in a Macro This command allows you to erase a command in a macro without erasing the whole macro. The commands inside of the macro are numbered 00, 01, 02... so the first command is numbered 00. It may be helpful to execute command 054 to recall the contents of the macro so that you know which command to erase. <058> mmm nn Parameters: - 058 is the default command name. - MMM is the number of the macro - NN is the number of command inside of the macro to erase (00, 01, 02...) Voice Response: "M 059: Insert a Command in a Macro This command allows you to insert a command in a macro without erasing the following commands. This is useful for adding a command to the beginning or middle of a macro. The commands inside of the macro are numbered 00, 01, 02... so the first command is numbered 00. It may be helpful to execute command 054 to recall the contents of the macro so that you know where you want to insert the new command. <059> mmm nn ccc d..d Parameters: - 059 is the default command name. - MMM is the number of the macro - NN is the where inside of the macro to insert the new command (00, 01, 02...) If NN is larger than the number of commands in the macro, the new command will be appended to the macro. - CCC is the command number of the command to insert - D..D is the data for the above command Voice Response: "M 067: Set Macro Data Length This is an advanced command that lets you specify that a macro should gather some extra information (more digits entered after the name of the macro) when it is executed and pass that information on to the commands inside of the macro. See the examples below for some of the possible uses of this command. <067> mmm recall data length for macro 'mmm' <067> mmm xx y 'mmm' is the macro number 'xx' is number of digits of data 'y' is '0' if the amount of data must be exact or '1' if more data is OK. Notes: When the macro executes, any commands in the macro that require a fixed amount of data will first take the data that was specified when the macro was programmed, then will take as many of the digits specified at runtime as needed. Commands in the macro that will accept a variable amount of data get all of the remaining digits specified at run-time. Any extra digits will be discarded. Default: <067> mmm 00 0 Examples: Extra autopatch up code: 067 500 01 1 ; allow macro 500 to take 1 or more digits 053 500 112 ; make macro 500 call patch up command ; the phone number will be specified at runtime 010 500 n..n ; rename new patch up code to "n..n" Usage: "n..n " Connect port 3 to the port that user specifies: 067 501 01 0 ; allow macro 500 to take 1 digit 053 501 000 3 ; connect port 3 to port specified at runtime Usage: "501 x" will connect port 3 to port x Automatic Macros The following is a list of the macros that are automatically executed by the controller at certain times. Because they are executed automatically when something happens (like a timer expiring) rather than because a user specifically told it to execute by entering the macros name, they are called "automatic" macros. The only difference between automatic and user macros is who (or what) decides that they should be executed. They are named according to the function that they usually perform. If you want to change how something works, you can change what commands the macro executes to suit your own desires. An example of this would be changing an impolite ID macro to send your repeater's ID rather than the example ID that is programmed in at the factory. You can execute any of these macros by entering its name which corresponds to its macro number followed by a 'D' or unkey or (example 200 would execute macro 200). This is useful for finding out what is already in the macros. You find out even more about what is in a macro by recalling its contents with Command 054 D or unkey or then the macro's number. If you do this from a serial terminal, it will be relatively easy to understand. If you do it from a DTMF pad, the voice message may seem long and complicated. This is because the synthesized voice must spell out the messages that are programmed in the macros. You can learn a lot about how the controller works by looking at what is inside of the macros with Command 054. Command 054 also tells you how many percent full a macro is. Each macro can store 100 bytes of information, about 100 keystrokes. Automatic Macro Explanations Macros 200..219 are where your error messages come from. Whenever an error occurs in the controller, it will cause one of these macros to be executed. To find out what caused the error, remember what the error number is and look at the description of the corresponding macro number below. You can change the error messages to say anything you want them to, or nothing at all, by changing these macros. Please note, however, that if you remove the error messages completely, that you may not be able to tell when an error occurs. See the section about error messages in Chapter 1 for more detailed descriptions. Macro Definition . Macro Definition 200 No matching Command Name . 210 Invalid data value 201 Too few data digits . 211 Command does not exist 202 Too many data digits . 212 Bad Autopatch number 203 Invalid number of data digits . 213 Autopatch error 204 Execution blocked from port . 214 Invalid User 205 User level to low . 215 DVR is busy 206 Reserved . 216 Macro is full 207 Command executed OK . 217 HF Error 208 Internal problem . 218 Not Defined 209 Macro depth problem 219 Not Defined Macros 220..255 These macros are automatically called when it is time to send an ID. You will want to erase (with Command 055) what is in these macros when you get the controller and put your own ID messages in these macros. It would be worth your time to study the way these IDs are programmed at the factory (see Command 054) so that you can make yours work the same way. Note that Command 064 is used to speak the voice IDs so that they will be polite and will automatically call the impolite ID macro (which is usually CW) if they are interrupted. Shortcut: if you want all four of the pending IDs for a port to send the same message, program that message in the first of the four pending ID macros, then program the other three to execute the first one. To change the ID timers, see Command 020. Macro Definition Macro Definition 220. . .Initial ID, Port 1 221. . .Initial ID, Port 2 222. . .Initial ID, Port 3 223. . .Initial ID, Port 4 224. . .Initial ID, Port 5 225. . .Initial ID, Port 6 226. . .Pending ID #1, Port 1 227. . .Pending ID #1, Port 2 228. . .Pending ID #1, Port 3 229. . .Pending ID #1, Port 4 230. . .Pending ID #1, Port 5 231. . .Pending ID #1, Port 6 232. . .Pending ID #2, Port 1 233. . .Pending ID #2, Port 2 234. . .Pending ID #2, Port 3 235. . .Pending ID #2, Port 4 236. . .Pending ID #2, Port 5 237. . .Pending ID #2, Port 6 238. . .Pending ID #3, Port 1 239. . .Pending ID #3, Port 2 240. . .Pending ID #3, Port 3 241. . .Pending ID #3, Port 4 242. . .Pending ID #3, Port 5 243. . .Pending ID #3, Port 6 244. . .Pending ID #4, Port 1 245. . .Pending ID #4, Port 2 246. . .Pending ID #4, Port 3 247. . .Pending ID #4, Port 4 248. . .Pending ID #4, Port 5 249. . .Pending ID #4, Port 6 250. . .Impolite ID, Port 1 251. . .Impolite ID, Port 2 252. . .Impolite ID, Port 3 253. . .Impolite ID, Port 4 254. . .Impolite ID, Port 5 255. . .Impolite ID, Port 6 Macros 256..261 are executed when it is time to send a courtesy beep. You would normally call Command 040 from this macro to generate the tones of your courtesy beep. If you want your courtesy beep to contain several beeps in sequence, you can call Command 040 multiple times within one macro, once for each beep. Note: Before this macro is automatically called after you unkey, the audio routing variable is set to make the tones go to the proper ports, so you do not have to worry about that at all. Just call the commands you want to be executed when it is time for a courtesy beep (you could send beeps, DTMF digits, voice messages...) and the audio will automatically be sent to the correct ports. To change the courtesy beep timers, see Command 020. Macro Definition 256. Courtesy Beep Slot, Port 1 257. Courtesy Beep Slot, Port 2 258. Courtesy Beep Slot, Port 3 259. Courtesy Beep Slot, Port 4 260. Courtesy Beep Slot, Port 5 261. Courtesy Beep Slot, Port 6 Macros 262..262+5-1+ are called when the analog input lines go into a High alarm. You may want to use these macros to speak an voice message indicating the alarm, start a beaconing alarm (see Chapter 19) and/or take some other action such as turning off an open collector output line. To change how often the RLC-Club Deluxe II checks to see if an alarm has occurred, see the I/O polling timer in Chapter 4. The default is once per second. Macro Definition 262. High Alarm, Analog Line 1 263. High Alarm, Analog Line 2 264. High Alarm, Analog Line 3 265. High Alarm, Analog Line 4 266. High Alarm, Analog Line 5 Macros 267..267+5-1+ are called when the analog input lines go into a Low alarm. You may want to use these macros to indicate an alarm condition. Macro Definition 267. Low Alarm, Analog Line 1 268. Low Alarm, Analog Line 2 269. Low Alarm, Analog Line 3 270. Low Alarm, Analog Line 4 271. Low Alarm, Analog Line 5 Macros 272..272+5-1+ are called when the analog input lines go out of either High or Low alarm into a Normal condition. You may want to use these macros to indicate that the analog reading is no longer causing an alarm. Macro Definition 272. Alarm to Normal, Analog Line 1 273. Alarm to Normal, Analog Line 2 274. Alarm to Normal, Analog Line 3 275. Alarm to Normal, Analog Line 4 276. Alarm to Normal, Analog Line 5 Macros 277..277+8-1+ are called when the digital inputs lines go from Low to High. You may want to use these macros to indicate an alarm condition. These macros are only called if the input alarms are enabled with command 092 (see Chapter 12). Macro Definition 277. Low to High, Input Line 1 278. Low to High, Input Line 2 279. Low to High, Input Line 3 280. Low to High, Input Line 4 281. Low to High, Input Line 5 282. Low to High, Input Line 6 283. Low to High, Input Line 7 284. Low to High, Input Line 8 Macros 285..285+8-1+ are called when the digital input lines go from High to Low. You may want to use these macros to indicate an alarm condition. These macros are only called if the input alarms are enabled with command 092 (see Chapter 12). Macro Definition 285. High to Low, Input Line 1 286. High to Low, Input Line 2 287. High to Low, Input Line 3 288. High to Low, Input Line 4 289. High to Low, Input Line 5 290. High to Low, Input Line 6 291. High to Low, Input Line 7 292. High to Low, Input Line 8 Macros 293..299 are called when the Time-Out Timer expires. You may want to program these messages to indicate when a time-out condition occurred. They default to speaking "One Time Out" (or whatever receiver it is that just timed out). To adjust the time out timers, see Command 020. Macro Definition 293. Time-out Timer Message, Port 1 294. Time-out Timer Message, Port 2 295. Time-out Timer Message, Port 3 296. Time-out Timer Message, Port 4 297. Time-out Timer Message, Port 5 298. Time-out Timer Message, Port 6 299. Time-out Timer Message, Autopatch Macros 300..306 are called when the Time-Out Timer comes out of a time-out condition. You may want to program these messages to indicate that a time-out condition has just been cleared. Macro Definition 300. Time-out Condition Clear Message, Port 1 301. Time-out Condition Clear Message, Port 2 302. Time-out Condition Clear Message, Port 3 303. Time-out Condition Clear Message, Port 4 304. Time-out Condition Clear Message, Port 5 305. Time-out Condition Clear Message, Port 6 306. Time-out Condition Clear Message, Autopatch Macros 307..313 If you don't use preaccess, you can totally ignore these macros. Even if you do use preaccess, you don't have to worry about them. They are automatically renamed and programmed when you configure a port for preaccess with Command 070 or 071. If you are curious, however, read on. When a port is set to require preaccess (either with Command 070 or 071), these macros are automatically programmed and renamed. The access code ("*" for a repeater, "#??" for a link) is actually the new name of these macros. Also, the command decoder is told to ignore every command that is entered from that port except for these macros. When you enter the access code, one of these macros is executed. The commands that are automatically programmed into these macros may do a lot of things (such as start dial tone for a link), but they always do this one thing, they execute Command 074. Command 074 tells the command decoder to let that port access all of the commands in the controller again, but only until the preaccess timer (see Command 020) runs out. You should never have to change the contents of these macros by hand (since Command 070 and 071 do the work for you), but you might want to change their names. When you use Command 070 to configure a port as a preaccess repeater, it assumes that you want the local-mode access code to be "*". If that is not true, you can simply rename the first preaccess macro for that port to something else. Similarly, the link access code that is usually "#" plus two digits, can be changed to any valid command name up to six digits long. Macro Definition 307. Pre-Access Storage, Port 1 308. Pre-Access Storage, Port 2 309. Pre-Access Storage, Port 3 310. Pre-Access Storage, Port 4 311. Pre-Access Storage, Port 5 312. Pre-Access Storage, Port 6 313. Access Password, Autopatch Macro 314 is called whenever the controller is reset, whether it is reset because the power was just turned on, because you pressed the reset button, or because you executed the remote reset command. You can use it to execute any commands that you want to be executed on reset. If you run out of space in this, or any other macro, because you are trying to do too much, just call another macro, or several of them, from this macro and split up the work. Macro Definition 314. Macro Called on Reset Macro 315 is a temporary macro that is used when appending macros etc. It is of no use to you because it will be overwritten often. Macro Definition 315. System Temporary Macro Macros 316..331 are called when the corresponding user timer (see Command 020) expires. These timers can be started with Command 022 and stopped with Command 023. They are not normally used, but are provided for users that have a special purpose for them. Macro Definition Macro Definition 316. . .User Timer # 00 317. . .User Timer # 01 318. . .User Timer # 02 319. . .User Timer # 03 320. . .User Timer # 04 321. . .User Timer # 05 322. . .User Timer # 06 323. . .User Timer # 07 324. . .User Timer # 08 325. . .User Timer # 09 326. . .User Timer # 10 327. . .User Timer # 11 328. . .User Timer # 12 329. . .User Timer # 13 330. . .User Timer # 14 331. . .User Timer # 15 Macro 332 is automatically executed immediately before the autopatch is taken off hook when a call is made. It can be used to disconnect link ports before the call begins. Macro Definition 332. Called before Autopatch is taken Off Hook Macro 333 is automatically executed immediately after the autopatch is hung up. It can be used to reconnect the links that were disconnected in macro . Macro Definition 333. Called after Autopatch is placed On Hook Macro 334 is used to speak "Autopatch Busy" when you try to use the patch when it is already in use. It is automatically programmed when the controller is reinitialized. You can erase it and program your own autopatch busy message if you wish. Macro Definition 334. Called when the Autopatch is Busy Macro 335 is used to speak "Autopatch" before the phone number is read back and dialed. It is automatically programmed when you set up the autopatch with Command 110. You can erase it and program your own message if you wish, but be sure that you recall the pre-programmed message first and understand what it does (it may do some other things depending on the number readback mode). You can also change the number of pauses that are spoken after the word "Autopatch" to change the delay before the number readback begins. See also macro 345. Macro Definition 335. Called before Autopatch number is read-back Macro 336 is used to speak pauses after the number is read back. It is automatically programmed when you set up the autopatch with Command 110. You can change it if you wish, but be sure that you recall the pre-programmed macro first and understand what it does. You can change the number of pauses that are spoken to change the time that you can wait after the number is read back and still be able to kerchunk to make it dial/not dial (depending on the number readback mode). Macro Definition 336. Called after Autopatch number is read-back Macro 337 is an autopatch macro that is used for number readback mode 2. Macro Definition 337. Internal Autopatch Macro Macro 338 is used to speak "Call complete at