RLC-2 Software Version 4.14 Link Communications, Inc. 1035 Cerise Rd Billings, MT 59101 (406) 245-5002 Voice (406) 245-4889 Fax http://www.link-comm.com Table of Contents Chapter 1: Getting Started . . . . . . . . . . . . . . . . . . . . . . .1-1 Introduction:. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-2 Limited Warranty . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-3 User Survey (Optional) . . . . . . . . . . . . . . . . . . . . . . . . .1-4 Re-Initialization the Controller . . . . . . . . . . . . . . . . . . . .1-5 Resetting the Controller . . . . . . . . . . . . . . . . . . . . . . . .1-5 Troubleshooting the Controller. . . . . . . . . . . . . . . . . . . . .1-6 *** Getting On The Air Quickly *** . . . . . . . . . . . . . . . . . . .1-7 Setup and Interfacing. . . . . . . . . . . . . . . . . . . . . . . . . .1-8 Serial Port Interfacing. . . . . . . . . . . . . . . . . . . . . . . . 1-13 System Wide Errors . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15 Chapter 2: Port Connection Commands. . . . . . . . . . . . . . . . . . .2-1 000: Connect one Port to another Port. . . . . . . . . . . . . . . . .2-2 001: Monitor one Port from another Port. . . . . . . . . . . . . . . .2-3 002: Disconnect one Port from another Port . . . . . . . . . . . . . .2-4 009: Checking Cross-Point Connections. . . . . . . . . . . . . . . . .2-5 010: Time-Out Timer Enabled/Disabled . . . . . . . . . . . . . . . . .2-6 011: Check Time-Out Timer Status . . . . . . . . . . . . . . . . . . .2-7 012: Program a Receiver's Access Mode. . . . . . . . . . . . . . . . .2-8 013: Checking Access Modes . . . . . . . . . . . . . . . . . . . . . .2-9 014: Port Supervisory PTT Control. . . . . . . . . . . . . . . . . . 2-10 015: Check Port Supervisory Control Settings . . . . . . . . . . . . 2-11 018: Receiver Active - Inactive Control Command Execution. . . . . . 2-12 019: Check Receiver Active - Inactive Command Execution. . . . . . . 2-13 024: Controls a Port's COR/PL Polarity . . . . . . . . . . . . . . . 2-14 025: Interrogates a Port's COR/PL Polarity . . . . . . . . . . . . . 2-15 Chapter 2 Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16 Example 2-1: Configuring a Port as a Repeater, Link. . . . . . . . . . 2-17 Example 2-2: Enable Time-Out Timers. . . . . . . . . . . . . . . . . . 2-18 Example 2-3: Configuring a Ports COR/PL Polarity . . . . . . . . . . . 2-19 Chapter 3: System Audio Control . . . . . . . . . . . . . . . . . . . .3-1 003: User Control if Errors are Spoken . . . . . . . . . . . . . . . .3-2 007: Set Up the System's Audio Routing Variables . . . . . . . . . . .3-3 008: Recall the System's Audio Routing Variables . . . . . . . . . . .3-5 039: Change the Internal Audio Routing Variable. . . . . . . . . . . .3-6 020: Port DTMF Mute Control. . . . . . . . . . . . . . . . . . . . . .3-7 021: Check Port Mute Controls. . . . . . . . . . . . . . . . . . . . .3-8 022: Set-up DTMF Cover Tone Variables. . . . . . . . . . . . . . . . .3-9 Chapter 3 Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10 Example 3-1: RLC-2 Audio Routing Variables . . . . . . . . . . . . . . 3-11 Example 3-2: I want to enable DTMF muting on port 1,3 . . . . . . . . 3-13 Example 3-3: I want to disable DTMF cover tone on muted ports . . . . 3-13 Chapter 4: System Security. . . . . . . . . . . . . . . . . . . . . . .4-1 004: Setting Up the Master System Unlock Codes . . . . . . . . . . . .4-2 005: Unlocking the Controller. . . . . . . . . . . . . . . . . . . . .4-4 006: Locking the Controller. . . . . . . . . . . . . . . . . . . . . .4-5 027: Rename DTMF Command Name. . . . . . . . . . . . . . . . . . . . .4-6 028: Command Read Back by Command Number . . . . . . . . . . . . . . .4-7 029: Command Name Compare to Find Command Number . . . . . . . . . . .4-8 030: Change First,Second,Third Command Name Digits . . . . . . . . . .4-9 031: Group Assign DTMF Command Mask Assign . . . . . . . . . . . . . 4-10 032: Command Checks Value of DTMF Execution Register . . . . . . . . 4-11 033: Group Assign Master Unlock Requirement for DTMF . . . . . . . . 4-12 034: Individually Assign Unlock Requirement for DTMF . . . . . . . . 4-13 035: Recall DTMF Unlock Requirements on a Command. . . . . . . . . . 4-14 036: Group Assign Master Unlock Requirement for Serial . . . . . . . 4-15 037: Individually Assign Unlock Requirement for Serial . . . . . . . 4-16 038: Recall Serial Unlock Requirements on a Command. . . . . . . . . 4-17 040: User Forced Execution Digit Change. . . . . . . . . . . . . . . 4-18 041: Check the Forced Execution Digit. . . . . . . . . . . . . . . . 4-19 115: Assign the DTMF Decoder Priority. . . . . . . . . . . . . . . . 4-20 Chapter 4 Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21 Example 4-1: How to Access Locked Commands. . . . . . . . . . . . . . 4-22 Example 4-2: Renaming Commonly Used Commands. . . . . . . . . . . . . 4-23 Example 4-3: Renaming Commands. . . . . . . . . . . . . . . . . . . . 4-24 Example 4-4: Assigning DTMF, Un-Lock codes, Serial masks . . . . . . . 4-25 Example 4-5: Changing the Digit. . . . . . . . . . 4-27 Chapter 5: Messages, Tones and Responses. . . . . . . . . . . . . . . .5-1 042: Generate a Tone Sequence Out Selected Ports . . . . . . . . . . .5-2 043: Generate a CW Message Out Selected Ports. . . . . . . . . . . . .5-4 044: Generate a DTMF Sequence Out a Selected Port. . . . . . . . . . .5-5 045: Generate a Voice Message. . . . . . . . . . . . . . . . . . . . .5-7 046: Delete a Message Slot . . . . . . . . . . . . . . . . . . . . . .5-8 047: DTMF Keypad Message Generate. . . . . . . . . . . . . . . . . . .5-9 048: Recall a Message Slot 00..33. . . . . . . . . . . . . . . . . . 5-10 049: Program a Message Slot. . . . . . . . . . . . . . . . . . . . . 5-11 111: Set Up the CW Speed . . . . . . . . . . . . . . . . . . . . . . 5-12 112: Set Up the CW Tone Frequency. . . . . . . . . . . . . . . . . . 5-13 113: Program a 2-Tone Pager Slot . . . . . . . . . . . . . . . . . . 5-14 114: Recall the 2-Tone Paging Slot 01..20. . . . . . . . . . . . . . 5-17 Chapter 5 Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18 Example 5-1: Generating a Custom Courtesy Beep. . . . . . . . . . . . 5-19 Example 5-2: Building Port 1's ID's . . . . . . . . . . . . . . . . . 5-20 Chapter 6 System Timers . . . . . . . . . . . . . . . . . . . . . . . .6-1 050: Recall a Timer Slot . . . . . . . . . . . . . . . . . . . . . . .6-2 051: Start a Timer Slot. . . . . . . . . . . . . . . . . . . . . . . .6-5 052: Program a Timer Slot. . . . . . . . . . . . . . . . . . . . . . .6-6 066: Start a User Timer . . . . . . . . . . . . . . . . . . . . . . . .6-7 067: Stop a User Time . . . . . . . . . . . . . . . . . . . . . . .6-8 023: Control DTMF Timed Execution. . . . . . . . . . . . . . . . . . .6-9 Examples for Chapter 6 . . . . . . . . . . . . . . . . . . . . . . . . 6-10 Example 6-1: Using a User timer to Auto-Disconnect a Port. . . . . . . 6-11 Chapter 7 Scheduler, Time-of Day Clock . . . . . . . . . . . . . . . . .7-1 053: Speak Good Morning, Afternoon, or Evening . . . . . . . . . . . .7-2 054: Recall Time-of-Day Clock (Male) . . . . . . . . . . . . . . . . .7-3 055: Recall Time-of-Day Clock (Female) . . . . . . . . . . . . . . . .7-4 056: Recall Date (Male). . . . . . . . . . . . . . . . . . . . . . . .7-5 057: Recall the Day (Male) . . . . . . . . . . . . . . . . . . . . . .7-6 058: Setting the Time. . . . . . . . . . . . . . . . . . . . . . . . .7-7 059: Setting the Date. . . . . . . . . . . . . . . . . . . . . . . . .7-8 060: Scheduler Event Recall. . . . . . . . . . . . . . . . . . . . . .7-9 061: Scheduler Event Program . . . . . . . . . . . . . . . . . . . . 7-10 062: Scheduler Event Enable/Disable. . . . . . . . . . . . . . . . . 7-13 Examples for Chapter 7 . . . . . . . . . . . . . . . . . . . . . . . . 7-14 Example 7-1: Set-up the Scheduler to reset my Analog High/Low Readings at 12:00AM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-15 Example 7-2: Set-up the Scheduler to Enable Time readings on the hour beginning at 8:00 AM until 6:00 PM . . . . . . . . . . . . . . . . . . . . . . . . 7-16 Chapter 8: Event Tables . . . . . . . . . . . . . . . . . . . . . . . .8-1 063: Recall an Event . . . . . . . . . . . . . . . . . . . . . . . . .8-2 064: Program an Event. . . . . . . . . . . . . . . . . . . . . . . . .8-3 065: Enable/Disable an Event . . . . . . . . . . . . . . . . . . . . 8-10 Examples for Chapter 8 . . . . . . . . . . . . . . . . . . . . . . . . 8-11 Chapter 9: Analog Input System. . . . . . . . . . . . . . . . . . . . .9-1 070: Analog Line Faceplate Assignment. . . . . . . . . . . . . . . . .9-2 071: Recall Analog Faceplate . . . . . . . . . . . . . . . . . . . . .9-5 072: Analog Line Calibration . . . . . . . . . . . . . . . . . . . . .9-6 073: Recall Analog Line Calibration. . . . . . . . . . . . . . . . . .9-7 074: Reset Analog 1-4 High/Low Values. . . . . . . . . . . . . . . . .9-8 075: Read an Analog Line . . . . . . . . . . . . . . . . . . . . . . .9-9 076: Read an Analog High Value . . . . . . . . . . . . . . . . . . . 9-10 077: Read an Analog Low Value. . . . . . . . . . . . . . . . . . . . 9-11 078: Read an Analog High Line Time . . . . . . . . . . . . . . . . . 9-12 079: Read an Analog Low Line Time. . . . . . . . . . . . . . . . . . 9-13 080: Read an Analog High Date. . . . . . . . . . . . . . . . . . . . 9-14 081: Read an Analog Low Date . . . . . . . . . . . . . . . . . . . . 9-15 082: Analog Line Alarm Value Program . . . . . . . . . . . . . . . . 9-16 083: Check Analog Alarm Points . . . . . . . . . . . . . . . . . . . 9-19 084: Check Analog Active Alarms. . . . . . . . . . . . . . . . . . . 9-20 Examples for Chapter 9 . . . . . . . . . . . . . . . . . . . . . . . . 9-21 Analog Input Telemetry Lines . . . . . . . . . . . . . . . . . . . . . 9-22 Example 9-1: Configure a High Temperature Alarm. . . . . . . . . . . . 9-23 Temperature Sensor Hook-Up . . . . . . . . . . . . . . . . . . . . . . 9-25 Reading AC Voltage with an Analog Input Line . . . . . . . . . . . . . 9-26 Chapter 10: Input and Output Lines . . . . . . . . . . . . . . . . . . 10-1 085: Read Input Lines. . . . . . . . . . . . . . . . . . . . . . . . 10-2 086: Output Line 1 On. . . . . . . . . . . . . . . . . . . . . . . . 10-3 087: Output Line 1 Off . . . . . . . . . . . . . . . . . . . . . . . 10-3 088: Output Line 2 On. . . . . . . . . . . . . . . . . . . . . . . . 10-3 089: Output Line 2 Off . . . . . . . . . . . . . . . . . . . . . . . 10-3 090: Output Line 3 On. . . . . . . . . . . . . . . . . . . . . . . . 10-3 091: Output Line 3 Off . . . . . . . . . . . . . . . . . . . . . . . 10-3 092: Output Line #..# On . . . . . . . . . . . . . . . . . . . . . . 10-4 093: Output Line #..# Off. . . . . . . . . . . . . . . . . . . . . . 10-5 094: Check Output Lines. . . . . . . . . . . . . . . . . . . . . . . 10-6 Examples for Chapter 10. . . . . . . . . . . . . . . . . . . . . . . . 10-7 Example 10-1: Configure a Door Alarm . . . . . . . . . . . . . . . . . 10-8 Magnetic Door Switch Drawing . . . . . . . . . . . . . . . . . . . . . 10-9 Output Line Relay Driver Drawing . . . . . . . . . . . . . . . . . . .10-11 Logical Input Lines. . . . . . . . . . . . . . . . . . . . . . . . . .10-12 Input line reading AC power fail Drawing . . . . . . . . . . . . . . .10-13 Chapter 11: Doug Hall RBI-1, RLC-ICM and Misc.Remotes . . . . . . 11-1 A Brief Description on how to use: Remote Base Functions . . . . . . . 11-2 095: Enter Frequency Plus Offset for RBI-1, RLC-ICM. . . . . . . . . 11-3 096: Set PL Frequency, Encode On-Off, Decode On-Off. . . . . . . . . 11-4 097: Recall Memory Channels on RBI-1 . . . . . . . . . . . . . . . . 11-7 098: Set Power on the RBI-1. . . . . . . . . . . . . . . . . . . . . 11-8 099: Turn RBI-1 Radio Band Power On-Off. . . . . . . . . . . . . . . 11-9 100: Reset External Interface. . . . . . . . . . . . . . . . . . . .11-10 101: Configure the RLC-ICM Module. . . . . . . . . . . . . . . . . .11-11 102: Recall Frequency. . . . . . . . . . . . . . . . . . . . . . . .11-13 103: Recall All Remote Variables . . . . . . . . . . . . . . . . . .11-14 104: External Serial Data Send - Parallel BCD Controller . . . . . .11-15 110: Pulse Output Line 'X' 'Y' Times . . . . . . . . . . . . . . . .11-16 Chapter 11 Examples. . . . . . . . . . . . . . . . . . . . . . . . . .11-17 Building a cable to interface the RLC-ICM/RBI-1 Interfaces . . . . . .11-20 Chapter 12: HF Remote Base Radio . . . . . . . . . . . . . . . . . . . 12-1 105: HF Mode Configure . . . . . . . . . . . . . . . . . . . . . . . 12-2 106: HF Mode Enable. . . . . . . . . . . . . . . . . . . . . . . . . 12-3 HF Remote Base Keypad. . . . . . . . . . . . . . . . . . . . . . . . . 12-4 107: HF Mode Disable . . . . . . . . . . . . . . . . . . . . . . . . 12-6 108: Enter Icom's HF Radio Address . . . . . . . . . . . . . . . . . 12-7 109: Command Line Control of the HF Routines . . . . . . . . . . . . 12-8 Chapter 12 Examples. . . . . . . . . . . . . . . . . . . . . . . . . . 12-9 Example 12-1: I need a macro to set-up the HF remote up . . . . . . .12-10 HF Radio Interfacing . . . . . . . . . . . . . . . . . . . . . . . . .12-11 Chapter 13: Pre-Access Code Set-up . . . . . . . . . . . . . . . . . . 13-1 120: Assign the 3 Ports Link Prefixes. . . . . . . . . . . . . . . . 13-2 121: Configure Pre-Access on a Port (Not Currently Active) . . . . . 13-3 122: Enable/Disable Pre-Access on a Port . . . . . . . . . . . . . . 13-4 123: Pre-Access Configure for the Stop Access Mode . . . . . . . . . 13-5 Chapter 13 Examples. . . . . . . . . . . . . . . . . . . . . . . . . . 13-6 Example 13-1: Configuring ports for Pre-access. . . . . . . . . . . . 13-7 Chapter 14: The Autopatch System . . . . . . . . . . . . . . . . . . . 14-1 125: Reverse Autopatch Answer on the Repeater. . . . . . . . . . . . 14-2 126: Configure the Reverse Autopatch . . . . . . . . . . . . . . . . 14-3 127: Configure the Forward Autopatch . . . . . . . . . . . . . . . . 14-5 128: Program Dialing Number Allow Table. . . . . . . . . . . . . . . 14-6 129: Recall Dialing Number Allow Table . . . . . . . . . . . . . . . 14-7 130: Enable/Disable Number Allow Table Entry . . . . . . . . . . . . 14-8 132: Program Memory Dial . . . . . . . . . . . . . . . . . . . . . . 14-9 133: Recall Memory Dial Slot . . . . . . . . . . . . . . . . . . . .14-10 134: Enable/Disable Dialing Slot . . . . . . . . . . . . . . . . . .14-11 135: Program Call Sign Assignment. . . . . . . . . . . . . . . . . .14-12 136: Recall Call Sign Assignment . . . . . . . . . . . . . . . . . .14-13 137: Set Up Autodial Mode. . . . . . . . . . . . . . . . . . . . . .14-14 138: Program a Nuisance Number Slot. . . . . . . . . . . . . . . . .14-15 139: Recall a Nuisance Number Slot . . . . . . . . . . . . . . . . .14-16 140: Enable/Disable a Nuisance Slot. . . . . . . . . . . . . . . . .14-17 141: Programs Pre-Dial Digits and Controls Dialing . . . . . . . . .14-18 142: Recalls Pre-Dial Digits . . . . . . . . . . . . . . . . . . . .14-19 143: Patch On-Line with Error Checking . . . . . . . . . . . . . . .14-20 144: Patch On-Line without Error Checking. . . . . . . . . . . . . .14-21 145: Manual Patch On-Line. . . . . . . . . . . . . . . . . . . . . .14-22 146: Hanging Up the Patch. . . . . . . . . . . . . . . . . . . . . .14-23 147: Call Sign Request and Enter Programming Mode. . . . . . . . . .14-24 148: Last Number Redial. . . . . . . . . . . . . . . . . . . . . . .14-25 149: Reset Autopatch Time-Out Timer. . . . . . . . . . . . . . . . .14-26 Chapter 14 Examples. . . . . . . . . . . . . . . . . . . . . . . . . .14-27 Example 14-1: Configuring for 7 digit dialing . . . . . . . . . . . .14-28 Example 14-2: Setting the controller for Callsigns on dialing . . . .14-29 Example 14-3: Reverse Autopatch Programming . . . . . . . . . . . . .14-30 Example 14-4: Direct Dialing Flowchart. . . . . . . . . . . . . . . .14-31 Example 14-5: Memory Dialing Flowchart. . . . . . . . . . . . . . . .14-32 Chapter 15: Digital Voice Recorders. . . . . . . . . . . . . . . . . . 15-1 150: Playback Small DVR Slot 01..35. . . . . . . . . . . . . . . . . 15-2 151: Record a Small DVR Slot 01..35. . . . . . . . . . . . . . . . . 15-3 152: Delete a Small DVR Slot 01..35. . . . . . . . . . . . . . . . . 15-4 153: Select DVR Types. . . . . . . . . . . . . . . . . . . . . . . . 15-5 The Large Digital Voice Recorder . . . . . . . . . . . . . . . . . . . 15-6 154: Play DVR Track. . . . . . . . . . . . . . . . . . . . . . . . .15-13 155: Record DVR Track. . . . . . . . . . . . . . . . . . . . . . . .15-14 156: Erase DVR Tracks. . . . . . . . . . . . . . . . . . . . . . . .15-15 157: Retrieve Private Mail . . . . . . . . . . . . . . . . . . . . .15-16 158: Record Private Mail . . . . . . . . . . . . . . . . . . . . . .15-17 159: Erase Private Mail. . . . . . . . . . . . . . . . . . . . . . .15-18 160: Record Public Mail. . . . . . . . . . . . . . . . . . . . . . .15-19 161: Retrieve Public Mail. . . . . . . . . . . . . . . . . . . . . .15-20 162: Erase Public Mail . . . . . . . . . . . . . . . . . . . . . . .15-21 068: Check Public Mailboxes. . . . . . . . . . . . . . . . . . . . .15-22 163: Record and Play Audio Test. . . . . . . . . . . . . . . . . . .15-23 Chapter 15 Examples. . . . . . . . . . . . . . . . . . . . . . . . . .15-24 Example 15-1: Setting up message slots for Voice Mail . . . . . . . .15-25 Chapter 16: Macros . . . . . . . . . . . . . . . . . . . . . . . . . . 16-1 164: Serial Recall a range of Macros . . . . . . . . . . . . . . . . 16-2 165: Erase a Macro Position. . . . . . . . . . . . . . . . . . . . . 16-3 166: Enable/Disable a Macro Position . . . . . . . . . . . . . . . . 16-4 167: Recall a Macro Position . . . . . . . . . . . . . . . . . . . . 16-5 168: Program/Append a Macro Position . . . . . . . . . . . . . . . . 16-6 169: Cancel all Responses Following This Command. . . . . . . . . 16-7 170: Re-enables all Responses Following This Command. . . . . . . . . 16-7 171..240: Execute Macro #01..#70 . . . . . . . . . . . . . . . . . . 16-8 Chapter 16 Examples. . . . . . . . . . . . . . . . . . . . . . . . . .16-10 Chapter 17: Serial Commands. . . . . . . . . . . . . . . . . . . . . . 17-1 241: Serial Upload Data File . . . . . . . . . . . . . . . . . . . . 17-2 242: Serial Download Data File . . . . . . . . . . . . . . . . . . . 17-3 243: Serial Command Name List. . . . . . . . . . . . . . . . . . . . 17-4 244: Change the Serial Baud Rate or Send Serial Data . . . . . . . . 17-5 Chapter 17 Examples. . . . . . . . . . . . . . . . . . . . . . . . . . 17-6 Example 17-1: Setting up the Serial Port. . . . . . . . . . . . . . . 17-7 Example 17-2: I want to download the RAM into a file. . . . . . . . . 17-8 Chapter 18: Misc. Commands . . . . . . . . . . . . . . . . . . . . . . 18-1 116: Resistor #1,#2 Send Routine . . . . . . . . . . . . . . . . . . 18-2 117: Recall Software Resistor Settings . . . . . . . . . . . . . . . 18-3 225: Remotely Reset the Controller . . . . . . . . . . . . . . . . . 18-4 Chapter 18 Examples. . . . . . . . . . . . . . . . . . . . . . . . . . 18-5 Example 18-1: Applications for the software resistors . . . . . . . . 18-6 Squelch control with a Software Resistor . . . . . . . . . . . . . . . 18-6 Chapter 19: Tables, Drawings and Layouts . . . . . . . . . . . . . . . 19-1 Appendix A: ASCII Data Table. . . . . . . . . . . . . . . . . . . . . 19-1 Appendix B: Tone Frequency Conversion Table. . . . . . . . . . . . . . 19-2 Appendix C: Voice Word Look-up Table. . . . . . . . . . . . . . . . . 19-7 Special Voice Words. . . . . . . . . . . . . . . . . . . . . . . . . .19-12 Appendix D: Hardware . . . . . . . . . . . . . . . . . . . . . . . . .19-13 Board Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-14 Schematic Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . .19-16 Bill of Materials. . . . . . . . . . . . . . . . . . . . . . . . . . .19-30 Chapter 1: Getting Started This chapter deals with the information needed in getting the controller rolling and on the air. Read the sections carefully and familiarize yourself with the operations of the controller. Read through the sections on setting up events to allow ID's and enable messages. Introduction: Congratulations, you have purchased a very powerful tool for your group's repeater. The RLC-2 may seem complicated and intimidating at first, but don't worry. Setting it up and programming it are easy and straightforward, once you have read the manual. Please take the time to read it before you try to start programming. This will save you a lot of confusion and frustration, as it should answer most of your questions. The RLC-2 repeater controller consists of one repeater port, two linking ports, four analog voltage inputs, four logical (dry contact) inputs, and eight MOSFET output drivers. The repeater port and each of the linking ports can be configured to require one of several combinations of COR and PL inputs for access. The RLC-2 has a single DTMF decoder that scans between the three receiver ports, thereby supporting DTMF control from all ports of the controller. Synthesized voice prompts the users in the programming of the controller's variables, provides voice ID's and alarms based on the inputs, etc. This manual consists of three main sections: setup and interfacing, programming and commands, and the appendices with commonly referenced tables and charts. A glossary has also been included at the end to explain some of the terms and abbreviations that are used throughout the manual. We have attempted to explain everything in a way that is easy to understand, but some questions are inevitable. If you have carefully read the manual and still have questions, please contact us. Link Communications, Inc 1035 Cerise Rd Billings, MT 59101 (406) 245-5002 (406) 245-4889 fax info@link-comm.com Limited Warranty Coverage: Link Communications 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 will cover parts, labor and return shipping. If failure is caused by instances other than manufacturing defects, Link Communications will repair the product and bill the customer for parts and labor. Contact Link Communications for more information. What Link Communications will not cover: 1. Too much voltage to the controller. The RLC-2 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 for servicing information and authorization. Software Link Communications holds the copyright on the RLC-2'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. Software updates Link Communications will provide FREE Software updates for 6 months from the date of purchase. The owner must return replaced software chips to Link Communications in order to obtain further software updates. Software updates will cost $50.00 after the update warranty expires. Manual inserts and shipping are additional. 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-2 Serial Number ................. ________________ RLC-2 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 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 Comments: Re-In itialization the Controller When the RLC-2 powers up, a warm reset is processed. This reset will load the most recent variables into the controller. The variables are stored in the nonvolatile RAM chip located on the controller board. If the variables in the SRAM get scrambled somehow, a cold boot will be needed. This cold boot resets all of the RLC-2's variables to the preprogrammed values. This cold boot is accomplished by pressing and holding the initialize switch and pushing the reset switch. Another easier method of re-initializing the controller is to hold the initialization switch down and applying power to the controller. You must hold the initialize switch down for at least 5 seconds after you either reset the controller or apply power to the controller. Once the controller has been initialized, the reset switch must be pushed again. You know if the controller has been re-initialized if the voice speaks the message: "This Is The RLC-2 Repeater And Link Controller V 4.XX" *** Caution, Initialization will clear all user programmed variables *** 1. Depress the "Initialize (INIT)" switch and hold 2. Depress and Release the Reset Switch while continuing to hold the Initialize switch or while the Initialize (INIT) switch is depressed apply power to the controller. 3. After 5 seconds let go of the "Initialize" switch 4. Depress and Release the Reset switch to Initialize the RLC-2 Resetting the Controller Resetting the controller is as easy as pressing the Reset switch on the controllers board. The same function is possible by powering off the controller and powering it back on. Software access to a remote reset is possible by executing Command 245. All of these processes will soft boot the controller. When the controller has a soft boot, variables from the internal Non- Volatile SRAM chip will be loaded and used for the controllers operation. A reset will not effect the settings of these variables. Only a re-initialization will change the settings of the internal user programmed variables. Troubleshooting the Controller No LED's when the RLC-2 is powered up Check for +12 Volts at Power Connector Check for bad or blown fuse Make sure that the +12 Volts is connected correctly - Center of Plug is (+), Shield is (-) Only Some of the LED's are lit Cross-Point Board is not plugged in correctly (RLC-2 Rev. A,B) Short on that specific power supply - Call Link Communications Inc. if this occurs No Audio at Test Bus Check for main system power (All LED's lit) 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 controllers 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-2 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 terminals baud rate set to 9600,N,8,1 Are you wired to the correct connector: Serial/Resistor Are all the RS-232 TX and RX and ground wires connected The controller requires all RS-232 signals (TX/RX/Ground) the be connected *** Getting On The Air Quickly *** Follow the steps below to get your RLC-2 operational and on the air quickly. 1) Read the entire manual or go to step 2 2) Read the 'Setup and Interfacing' section to make sure you have all of the needed parts - This section describes how to adjust your controller 3) Wire up your power cord to +12 Volts DC. Center pin is positive, shield is ground. 4) Wire up your radio or audio amp. - pin 5 is your audio input (from your receiver audio out) - pin 4 is your audio output (to your mike jack or amp audio input) - pin 7 is your COR line (active low COR required (Goes to ground when active)) - pin 3 is your PTT input (active low on PTT (Goes to ground when active)) - pin 2 is your PL detect input (active low on detect (Goes to ground when active)) 5) Once you have your radio connected adjust your audio (See step 2) 6) Programming your controller - Command 048 recalls your Voice/CW messages - Command 049 programs your Voice/CW messages - Command 064 assigns what slot to use for the ID's, courtesy beeps etc... 7) If using an RS-232 port refer to 'Serial Port Interfacing' to get your RS-232 cable built - The RLC-2's serial port is not a standard DB-9 serial wiring - You must have both RX and TX wired for the serial port to work - You must have your grounds connected between the computer and RLC-2 ports 8) Once your serial is connected, press the reset button to see the RLC-2 copyright message - If you don't see the reset message check the following conditions - Is your Baud rate 9600 N 8 1 - Do you have your RX and TX leads swapped (Very Common) - Are your grounds tied together - Is your computer on the correct serial port 9) Now you can DTMF or RS-232 control the RLC-2 10) The serial port does not use command names, only command numbers that range from 000..245. 11) Call Link Communications Inc. for more help after - You have read the entire manual - Specific questions about the controller operation Setup and Interfacing 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-2. After that there is information concerning the other input and output features of the RLC-2: the serial interface, the logical output and input lines, and the analog input lines. Step #1: Check the Packing List Your package should contain the following items: (1) RLC-2 Repeater Controller (1) 2.50mm Power Connector (1) DB-9 Female Solder Connector (5) DB-9 Male Solder Connectors (1) RLC-2 Manual If any of these parts are missing, contact Link Communications Inc. Step #2: Connect Power - The RLC-2 is 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-2 controller, the 5 LED's on the RLC-2 controller should light, indicating proper board operation. If all of the LED's do not light, turn off the power immediately. Step #3: Connecting Your Receivers to the RLC-2 The main repeater and each of the links connect to the RLC-2 using a male DB-9 connector (included). The control receiver connects to the same DB-9 as the main repeater. The pin-outs are listed below. Port 1 (Repeater Port) Pin # Signal Name Default Condition 1 Control RX COR Active Low 2 PL Decoder Input Active Low 3 Transmitter PTT Always Active Low 4 Transmitter Audio Audio Output, 600 5 Receiver Audio Audio Input, 10K 6 Control Receiver Audio Audio Input, 10K 7 Receiver COR Input Active Low 8 Ground Available .... 9 Ground Available .... Ports 2 and 3 (Link or Repeater Ports) Pin # Signal Name Default Condition 1 Ground Available .... 2 PL Decoder Input Active Low 3 Transmitter PTT Always Active Low 4 Transmitter Audio Audio Output, 600 5 Receiver Audio Audio Input, 10K 6 Ground Available .... 7 Receiver COR Input Active Low 8 Ground Available .... 9 Ground Available .... Connecting the Receiver COR - The first step in connecting your receiver is to locate the receivers COR signal. The RLC-2 will accept either active low or active high COR signals. The default COR is set to Low. The signal must be able to sink 4mA to ground. The input impedance of the RLC-2 COR input is 10K and it is diode clamped with internal pull-up resistors. This allows it to handle input voltages of up to 15 volts without damage to the controller. The COR input must not go below 0V (ground); this would damage the 82C55 IC. Using one of the supplied DB-9 Male connectors, connect your COR signal to pin #7 (or pin #1 for the control receiver). Refer to Commands 024 and 025 to change your ports COR and PL polarity. Connecting a PL Input (optional) - If you wish to use a PL (CTCSS) decoder on any of the receivers, it can be connected to pin #2 of the appropriate connector in the same fashion as the COR input. This signal can be either an active low or active high signal. Refer to Commands 024 and 025 to change your ports COR and PL polarity. Connecting the Receiver Audio - 2 types of audio can be used on the RLC-2 controller: Type 1: De-emphasized audio (Speaker Audio) Type 2: Discriminator audio (Raw Unsquelched Audio) - If type 1 audio is used, remove the appropriate jumper on the controller. This removes the de-emphasis filter from the circuit. As the controller comes shipped, all ports are set up for type 2 audio. Receiver De-emphasis Jumpers J1 - Port 1 Receiver De-emphasis Jumper J2 - Port 2 Receiver De-emphasis Jumper J3 - Port 3 Receiver De-emphasis Jumper J4 - Control Receiver De-emphasis Jumper (J8 on Rev. A,B Boards) - If type 2 audio is used, place the appropriate jumper in circuit (over both pins). This will place a - 6dB/octave de-emphasis filter into the circuit. Some discriminators can not directly drive the 10K input impedance. If this is the case, a pre-driver or different audio access point will be required. The filter will not allow PL to pass through the controller. Contact Link Communications Inc. if your needs require PL to pass through the controller. - The audio input is connected to pin #5 of the male DB-9 connector (pin #6 for the control receiver). - The audio adjustments will be described in Step #4. How the DTMF Decoder Works - The RLC-2's DTMF decoding circuit uses a scanner that enables the controller to receive tones from all the ports, without mixing the three receiver's audio together. This allows the receivers to have total control of the DTMF decoder when its COR is active. If the control receiver is active, and the control receiver is configured for priority control, then the DTMF decoder is locked to the control receiver's port until its COR goes away. Once the decoder has detected a tone on one of the ports, it stops scanning and waits up to three seconds for the next digit. It is reset at the beginning of each DTMF digit. If any of the DTMF digits are held for longer than 5 seconds or there is a pause of 5 seconds between digits, the DTMF scanner will resume scanning and all digits entered up to that point are lost. Step #4: Connecting Your Transmitters to the RLC-2 Transmitter PTT - The RLC-2 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-2 provides a 10K 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 appropriate jack on the main board. The main repeater goes to the jack nearest the power jack, Port 2 is right next to it, and Port 3 is the third from the left (with the DB-9s toward you). Step #5: Adjusting the RLC-2 Controller - Locate connector JP1 on the RLC-2 (It is the 10 pin female connector). This test bus will provide the signals that we need to adjust the inputs on the RLC-2. In order to maintain audio deviation during channel switching, all of the receiver inputs to the Cross-Point Board must be set to the same level. These signals can be measured with an oscilloscope or a true RMS AC voltmeter. In order to obtain an audio signal on JP1, a valid COR or PL must be received. Once a valid access signal is received, the RLC-2 will un-squelch the audio and be present on JP1. Repeater (Port 1) Receiver Adjustment: - Execute Command 000 12 and 000 13 to enable Port 1-Port 2, and Port 1 - Port 3 Port 1 Receiver: Transmitter Port Adjustment: - Present a stable Tone or DTMF tone to Port 1 RX. - Adjust the 'Main RX' pot so that the signal on pin 1 of JP1 is 1 volt peak-to-peak. - Adjust the 'Main TX' pot to obtain the desired deviation. Port 2 Transmitter Port Adjustment: - Adjust the 'Link 1 TX' pot to obtain the same deviation as the Main TX is. Port 3 Transmitter Port Adjustment: - Adjust the 'Link 2 TX' pot to obtain the same deviation as the Main TX is. Port 2 Receiver Port Adjustment: - Present the same Tone or DTMF signal used in Port 1 receiver: transmitter port adjustment step. While watching the Port 1 TX audio, adjust 'Link 1 RX' pot for the same deviation that was present on the Port 1's TX. Port 3 Receiver Port Adjustment: - Present the same Tone or DTMF signal used in Port 1 receiver: transmitter port adjustment step. While watching the Port 1 TX audio, adjust 'Link 2 RX' pot for the same deviation that was present on the Port 1's TX. Voice Level Adjustment: - Use Keypad Test (047) to generate Voice Data. - Adjust 'Voice' pot to 2.0 KHz deviation or until it "sounds" good, this adjustment is for all transmitters. Tone Generators Adjustment: - Adjust 'Tone 1' to 1.5 KHZ deviation, Adjust 'Tone 2' to 1.5 KHZ deviation - This adjustment is for all transmitters. Control Receiver Adjustment - Present a stable Tone or DTMF Tone to Control RX. -- Use Command 000 15 to route the control receiver audio to Port 1's TX port - Adjust 'CON RX' pot to match the deviation used earlier Serial Port Interfacing The RLC-2 has a serial terminal port for interfacing to any serial device, i.e. packet and serial terminal. This allows the user to monitor, control, and program all facets of the controller. The serial terminal carries highest priority for access and programming of the RLC-2. RS-232 Signals and Interfacing The RLC-2 output is the RS-232 standard, 12V. The serial terminal port also contains the I/O pins for the software controlled resistors. (See the Software Resistor Section for interfacing programming information). Pin-Out Serial P6 Connector Pin Number DB-09 Computer DB-25 Computer Signal Definition 4 3 2 RS-232 Input 5 5 7 Ground 9 2 3 RS-232 Output Pin-Out Software Resistors P6 Connector Pin Number Definition 1 Wiper Resistor #2 2 Low Side Resistor #2 3 Wiper Resistor #1 6 High Side Resistor #2 7 Low Side Resistor #1 8 High Side Resistor #1 Local Terminal Interfacing When using a local ASCII terminal at the RLC-2's location, an ASCII terminal can be used to communicate with the programming features of the RLC-2. The terminal's communication parameters must be set to: Baud (Default).... 9600, Start Bits.... 1, Stop Bits ....1, Parity .... N, Word Length .... 8 These parameters will allow communication with the RLC-2. For system operations, see the next section "Operation and Programming Over the Serial Port". Configuration of the Serial Port - Command 244 is provided to configure the serial port baud rate. -- Baud rate: Allows baud rate changes from 300,600,1200,2400,4800, and 9600 baud. Operation and Programming Over the Serial Port - The RLC-2's serial port gives the controller the ability to communicate with the world over a digital radio link. Serial Command Structures: Upper or Lower case digits may be used for the DTMF digits 'ABCD' All commands entered must be the commands 3 digit number that ranges from 000..245 Spaces, Tabs, and backspaces can be used over the serial port Comments must begin with the ';' colon digit first. Any data following the ';' will be ignored. Example: 000 11 ; This command convert port 1 into a repeater port The example shows the command number as '000' with additional data of '11' and a comment that begins with the ';' digit. The command sequence can be entered with either the key or the forced execution digit. This digit defaults to the 'D' key. Serial Response: Voice words are printed in 2 styles - When the word is a number between 0..9 and\or the word is a letter of the alphabet The word is printed [X] where 'X' is the information - When the word is other than the above listed conditions The word is printed (###) where '###' is the word number Syste m Wide Errors The controller has several error messages that can be spoken if an error occurs during programming. These errors indicate that the format of the command requested does not match the data that you entered. If you get errors other than the errors listed in this section, refer to the command that you were trying to execute for more specifics. Error 1..5 - These errors are not system wide errors. Refer to the command you are executing if you get one of these errors. Error 6 - The command you requested is not allowed to be executed from this radio port. The command is DTMF masked off. Either change the DTMF mask (See Command 030,031) or try another radio port. Error 7 - The command you requested is locked. You must unlock the controller using Command 005 before this command will be executed. Error 8 - The command that you requested is above the requested command names. You should never get this command. If this command is spoken execute Command 244 and serially view the command names for any problems or contact Link Communications Inc. Error 9 - The command you are trying requires more or less additional data before it can be executed. Verify the format of the command and the amount of additional data that the command requires before trying to execute it again. If the command requires 5 digits of additional data then 5 digits must be entered Example: Command 127 sets up the out going autopatch. This command requires 5 fields of data be entered for the command to execute correctly. If you enter less than 5 variables, then controller will speak 'Error 9'. Check your data and then check the command and enter everything required. Chapter 2: Port Connection Commands This section describes the commands used to connect the various ports of the controller together. A port indicates where audio goes in\out of the controller. 000: Connect one Port to another Port This command allows you to connect one radio port to another radio port. It is also used to put a port into "repeater mode", by connecting that port to itself. "Connecting a port" means that the audio in and keying source from each port become the audio out and PTT source for the other port. Connecting a port to itself makes the audio that comes in your repeater's receiver go out your repeater's transmitter, making it into a repeater. If you connect two different ports together, they will hear the activity from the other port. <000 > x y Parameters: - X is the first port to connect - Y is the second port to connect Ports range from 1..5 1 - Port 1 2 - Port 2 3 - Port 3 4 - Autopatch Port 5 - Control Receiver Port Defaults: - Port 2,3 default as links, Port 1 defaults as a repeater Error Codes: E1 - Invalid port requested (System wide errors are listed in front of the manual) Example 1: Connect Port 1 to Port 3 000 14 * or unkey Voice response "1 3 Connect On" Want port 1 as a repeater port 000 11 D or unkey Response: "X Y Connect On" 001: Monitor one Port from another Port This command allows you to monitor one radio port from another radio port. <001 > x y Parameters: - X is the port doing the monitoring of port Y - Y is the port being monitored Ports range from 1..5 1 - Port 1 2 - Port 2 3 - Port 3 4 - Autopatch Port 5 - Control Receiver Port Defaults: - Port 2,3 default as links, Port 1 defaults as a repeater Error Codes: E1 - Invalid port requested (System wide errors are listed in front of the manual) Example 1: Monitor Port 3 by Port 1 001 13 D or unkey Response: "X Y Connect Monitor" 002: Disconnect one Port from another Port This command allows you to disconnect one radio port from another radio port. <002 > x y Parameters: - X is the first port to disconnect - Y is the second port to disconnect Ports range from 1..5 1 - Port 1 2 - Port 2 3 - Port 3 4 - Autopatch Port 5 - Control Receiver Port Defaults: - Port 2,3 default as links, Port 1 defaults as a repeater Error Codes: E1 - Invalid port requested (System wide errors are listed in front of the manual) Example 1: Disconnect Port 1 from Port 3 002 13 D or unkey Voice response "1 3 Connect Off" Port 1 is currently a repeater port and you want the port configured as a link port. 002 11 D or unkey Response: "X Y Connect Off" 009: Checking Cross-Point Connections This command allows you 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 if executed from the RS-232 port, and will speak the conditions out the port that DTMF requested the conditions. <009 > Parameters: There are no parameters for this command Defaults: There are no defaults for this command Error Codes: (Sys tem wide errors are listed in front of the manual) Response: Voice Format: 1 Connect 2 Connect 3 Connect 4 Connect 5 Connect Serial Format: TX 1 2 3 4 5 1 . . . . . 2 . . . . . RX 3 . . . . . 4 . . . . . 5 . . . . . An 'x' indicates connection and a '.' indicates no connection. 010: Time-Out Timer Enabled/Disabled This command allows the user to enable/disable the time-out timer port a selected port. <010 > x y Parameters: X is the port. This number ranges from 1..5 Y is the control information. 1 - Enable Time-out timer 0 - Disable Time-out timer Defaults: Port 1 time-out timer is enabled Ports 2,3,4,5 time-out timers are disabled Notes: The FCC requires a 3 minute time-out timer on all repeater channels Error Codes: E1 - Invalid port. Port must range from 1..5 (Syst em wide errors are listed in front of the manual) Example 1: I want to enable the time-out timer on Port 2's repeater 010 2 1 D or unkey Response: "Port " 011: Check Time-Out Timer Status This command checks the status of the time-out timers. <011 > x Parameters: X is the port. This number ranges from 1..5 Defaults: Port 1 time-out timer is enabled Ports 2,3,4,5 time-out timers are disabled Notes: The FCC requires a 3 minute time-out timer on all repeater channels Error Codes: E1 - Invalid port. Port must range from 1..5 (Sys tem wide errors are listed in front of the manual) Example 1: I want to make sure the time-out timer is enable for port 3. 011 3 D or unkey Response: "Port " 012: Program a Receiver's Access Mode This command allows the user to set the receiver's access mode. <012 > x y Parameters: X is the receiver that the access mode is being changed. This number ranges from 1..5 Y is the access mode Access Modes Number Access Mode Description 0 No Access from the receiver 1 COR Access 2 PL Access 3 COR and PL Access 4 COR or PL Access Defaults: All ports default to COR (1) access Error Codes: E1 - Invalid port. Port must range from 1..5 E2 - Invalid access mode. Modes are listed above. (Sys tem wide errors are listed in front of the manual) Example 1: I want port 1 to require both COR and PL for access. 012 1 3 D or unkey Response: "Port is " 013: Checking Access Modes This command checks the settings of the ports access modes. <013 > x Parameters: X is the port number Response: Access Modes Number Access Mode Description 0 No Access from the receiver 1 COR Access 2 PL Access 3 COR and PL Access 4 COR or PL Access Defaults: All ports default to COR (1) access Error Codes: E1 - Invalid port. Port must range from 1..5 (Sys tem wide errors are listed in front of the manual) Example 1: I am getting noise on my port 3. I need to see if it is still in COR and PL mode. 013 3 D or unkey Response: "Port is " 014: Port Supervisory PTT Control This command allows the user to command off the system PTT for a selective port. Only the transmitter PTT is controlled. To control receiver access see Command 12 <014> x y Parameters: X is the port. This number ranges from 1..5 Y is the control information. 1 - Enable Supervisory PTT control (Kills Transmitter) 0 - Disable Supervisory PTT control (Enables Transmitter) Defaults: All ports transmitter enabled Error Codes: E1 - Invalid port. Port must range from 1..5 E2 - Invalid access mode. Modes are listed above. (Syst em wide errors are listed in front of the manual) Example 1: I need to shut off port 1's transmitter PTT because of some noise 014 1 1 D or unkey Response: "Port is " 015: Check Port Supervisory Control Settings This command checks the settings of Command 014 <015 > x Parameters: X is the port. This number ranges from 1..5 Defaults: All ports are enabled to transmit Error Codes: E1 - Invalid port. Port must range from 1..5 (Sys tem wide errors are listed in front of the manual) Example 1: My port 2 transmitter will not activate. I need to see if it is enabled 015 2 D or unkey Response: "Port is " 018: Receiver Active - Inactive Control Command Execution This command allows the user to enable/disable the execution of commands when the receiver goes from inactive. If this command is disabled for a port, the user must force the execution of the command in order for it to be accepted. When this command is enabled on a port, simply the receiver drop can execute a command <018 > x y Parameters: X is the port. This number ranges from 1..5 Y is the control information. 1 - Enables Receiver drop to execute a command 0 - Disables Receiver drop to execute a command Defaults: All ports allow receiver drop to execute a command sequence Error Codes: E1 - Invalid port. Port must range from 1..5 E2 - Invalid access mode. Modes are listed above. (Syst em wide errors are listed in front of the manual) Example 1: I need to keep users on the repeater from executing commands when they DTMF page other users. 018 1 0 D or unkey Response: "Port is" 019: Check Receiver Active - Inactive Command Execution This command checks the settings of Command 018. <019 > x Parameters: X is the port. This number ranges from 1..5 Defaults: All ports allow receiver drop to execute a command sequence Error Codes: E1 - Invalid port. Port must range from 1..5 (Sys tem wide errors are listed in front of the manual) Example 1: I want to make sure port 1 does not execute commands with a receiver drop 019 1 D or unkey Response: "Port is " 024: Controls a Port's COR/PL Polarity This command allows the user to customize the COR and PL levels. Every radio differs in how the COR and PL levels are present when the receiver is active. This command allows either active high or active low COR and PL signals to be accepted. If your receiver is active high and you need to change the COR/PL polarity and you do not have a serial terminal to change it for you, then you need to fake the COR input by tying the COR input to ground while entering Command 024. Make sure you have disconnected the ports COR input before forcing the COR to ground. <024 > x y Parameters: X is the port. This number ranges from 1..5 Y is the COR and PL mode COR and PL Mode COR and PL Levels 0 Both COR and PL active Low 1 COR Active Low, PL active High 2 COR Active High, PL active Low 3 COR and PL active High Defaults: Both COR and PL are active Low Notes: When a receiver is not connected to the controller, the COR and PL levels on that port must be set to active low (Mode 0) Error Codes: E1 - Invalid port selected (Sys tem wide errors are listed in front of the manual) Example 1: I want to connect a GE Master II receiver to my repeater port. This receiver has an active high COR output. 024 1 1 D or unkey Response: "Port is " 025: Interrogates a Port's COR/PL Polarity This command checks the setting of Command 025 <025 > x Parameters: X is the port. This number ranges from 1..5 COR and PL Mode COR and PL Levels 0 Both COR and PL active Low 1 COR Active High, PL active Low 2 COR Active Low, PL active High 3 COR and PL active High Defaults: Both COR and PL are active Low Notes: When a receiver is not connected to the controller, the COR and PL levels on that port must be set to active low (Mode 0) Error Codes: E1 - Invalid port selected (System wi de errors are listed in front of the manual) Example 1: I want to check port 3's COR and PL polarity before I connect a new receiver. 025 3 D o r unkey Response: "Port is " Chapter 2 Examples Example 2- 1: Configuring a Port as a Repeater, 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', ID's 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 effecting 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 When the port is a link the courtesy beep is on port 'X' is only routed to port 'X' if the audio routing variable is not 00 (Refer to Command 064 for audio routing variables). ID's are enabled but only controlled by the other connected ports. Time-out timers, if enabled, are running when port 'X's receiver is active. Monitoring a port It is handy to monitor a connected ports receiver without keying the ports transmitter. Because the controllers 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 2-2: Enable Time-Out Timers Time out timers are a legal requirement on repeater system. The controller supports separate time-out timers on each receiver port. The time-out timer is assigned to a receiver, not the transmitter. Because the transmitter is keyed-up more continuous that the receivers, and because the time-out timers need a break in activity in order to reset their timers, the receivers are use as the control function. Because of this each port that is able to control the radios transmitter has a time-out timer. It is standard to configure the timers for 3 minutes of activity cause a time-out. 1) Enable all ports time-out timers 2) Program the time-out timers for 3 minutes Enable all port time-out timers: Command 010 is assigned to control each ports time-out timer. This command requires 2 digits of additional data to configure the command. The first digit is the port requested, the second is the control variable. Port 1: 010 1 1 D or unkey ; Time-out timer enabled Port 2: 010 2 1 D or unkey ; Time-out timer enabled Port 3: 010 3 1 D or unkey ; Time-out timer enabled Port 4: 010 4 1 D or unkey ; Time-out timer enabled on autopatch calls Port 5: 010 5 1 D or unkey ; Time-out timer enabled on control receiver Program the time-out timers for 3 minutes Command 052 programs the timers on the controller. Timers 05..09 are assigned for the separate time-out timers. These timers are programmed in 10sec. increments. 3 minutes = 10 sec. * 018. This command requires 5 digits of additional data to configure the command. The first two digits select what timer you are programming, the next 3 program the time from 001..999. Port 1: 052 05 018 D or unkey ; Time-out timer time at 3 minutes Port 2: 052 06 018 D or unkey ; Time-out timer time at 3 minutes Port 3: 052 07 018 D or unkey ; Time-out timer time at 3 minutes Port 4: 052 08 018 D or unkey ; Time-out timer time at 3 minutes Port 5: 052 09 018 D or unkey ; Time-out timer time at 3 minutes Time-out timers are now all enabled and set for 3 minutes. If the timer expires, all transmitters the pot that timed out will be disabled for the timed out port. When the ports receiver goes from active to inactive, connected transmitters will now again be enabled to carry the ports signal. Time-out timer messages: Each port contains its own custom time-out timer event. These events are called when the port times out, and again when the port comes out of a timed out condition. Refer to commands 063,064,065 to program the event tables events. Example 2-3: Configuring a Ports COR/PL Polarity In order for the controller to recognize a ports 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 you polarity is active 'High', you need to execute Command 024 and tell the controller your correct polarity. Active 'High' COR and active 'Low' PL (Or no PL at all) on Port 1 is configured as: 024 1 1 D or unkey (Refer to command 024 for more information) This configured port 1 for active 'High' COR and active 'Low' PL Chapt er 3: System Audio Control This chapter deals with the system audio controls. In this chapters commands that deal with audio routing of messages, execution of commands based on the audio routing, and how errors are spoken when encountered. 003: User Control if Errors are Spoken This command allows the users to enable\disable the speaking of errors. Errors are sent if the format of the input data is not as the command requested requires. <003 > x Parameters: X - the Control variable 1 - enables errors to be spoken 0 - disables error to be spoken Defaults: Errors speaking is enabled. Error Codes: E1 - Invalid port requested (Syst em wide errors are listed in front of the manual) Example 1: I want to disable the errors from being spoken 003 0 D or unkey Response: "Error Squawk " 007: Set Up the System's Audio Routing Variables This command allows the user to set-up the system audio routing variables. These variables tell the controller where to route messages when commands are executed. This allows the user to totally control where CW and Voice messages are routed. <007 > xx yy Parameters: XX is the audio routing slots YY is the audio routing variable calculated below Device that Executed the Commands (XX) Audio Routing Variable 00: Internal Audio Routing Variable 01: Route to Port 1 01: RS-232 port 01: Route to Port 1 02: Event Scheduler 01: Route to Port 1 03: Port 1 01: Route to Port 1 04: Port 2 02: Route to Port 2 05: Port 3 04: Route to Port 3 06: Autopatch 08: Route to Port 4 07: Control Receiver 01: Route to Port 1 08: Event Table 00: Use the routing variable in the event Calculation of the audio routing variable: The audio routing variable is calculated by adding up a number that corresponds to the port you want the response to be routed to. This number ranges from 00..31. DTMF Executing the Command Number that corresponds to the device Port 1 +1 Port 2 +2 Port 3 +4 Autopatch +8 Control Receiver +16 (YY) Audio routing variable = (port1)+(port2)+(port3)+(autopatch)+(control rx) Error Codes: E1 - Invalid audio routing source E2 - Audio routing variable to big. Must range from 00..31 (System wide errors are listed in front of the manual) Example 1: I want all commands executed from Port 3 to be routed out both Port 3 and Port 1. 1) Look-up port 3's audio routing slot. Slot 05 is port 3 2) Develop an audio routing variable that includes port 1,3 Audio Routing Variable = 1(Port 1)+0(Port 2)+4(Port 3)+0(Autopatch)+0(Control) = 05 3) Execute Command 007 007 05 05 D or unkey Response: 'Port' is 'Audio Routing Variable' 008: Recall the System's Audio Routing Variables This command recalls the settings programmed in Command 007. <008 > xx Parameters: XX is the audio routing slots. This number must range from 00..12 Defaults: There are no defaults for this command Error Codes: E1 - Invalid audio routing source (System wide errors are listed in front of the manual) Example 1: I want to see what the audio routing variable is for the autopatch port 008 06 D or unkey Response: "Slot is ARV" 039: Change the Internal Audio Routing Variable This command allows the user to change where messages are routed that are called from internal execution sources. Internal execution sources include macros and internal generated messages and errors. <039 > xx Parameters: XX is the audio routing variable. This number must range from 00..31 DTMF Allowed Execution of the Command Number that corresponds to the device Port 1 +1 Port 2 +2 Port 3 +4 Autopatch +8 Control Receiver +16 (XX) Audio routing variable = (port1)+(port2)+(port3)+(autopatch)+(control rx) Defaults: Internal audio routing variable is port 1 (XX=01) Error Codes: E1 - Invalid audio routing variable Example 1: I want all internal responses to be routed to port 2, not port 1. 039 02 D or unkey Response: There is no response for this command. - To check your programming execute Command 008 00. 020: Port DTMF Mute Control This command allows the user to control the DTMF mute function on a ports transmitter. When the mute is enabled for a transmitter, no DTMF tones will be re-broadcasted out the transmitter. <020 > x y Parameters: X is the port. This number ranges from 1..5 Y is the control information. 1 - Enables DTMF mute on the transmitter 0 - Disables DTMF mute on the transmitter Defaults: All ports DTMF mute is off. Error Codes: E1 - Invalid port. Port must range from 1..5 E2 - Invalid access mode. Modes are listed above. (Syst em wide errors are listed in front of the manual) Example 1: I want DTMF mute enabled on port 1 transmitter. 020 1 1 D or unkey Response: "Port ' 021: Check Port Mute Controls This command check the settings of Command 020. <021 > x Parameters: X is the port. This number ranges from 1..5 Defaults: All ports DTMF mute is off. Error Codes: E1 - Invalid port. Port must range from 1..5 (System wide errors are listed in front of the manual) Example 1: Receivers seem to be muting when they talk loud. I need to see if DTMF mute is enable for port 2's receiver. 021 2 D or unkey Response: "Port ' 022: Set-up DTMF Cover Tone Variables This command allows the user to set-up the DTMF cover tone frequencies and if a cover tone is used when muting the DTMF tones Sett ing up the Cover tone enable/disable <022 > x Sett ing up to Cover tone frequencies <022 > xxxx yyyy Parameters: X is the control variable (When setting up Cover tone enable/disable) 1 - enables cover tone when DTMF mute active 0 - disables cover tone when DTMF mute active XXXX and YYYY is the cover tone frequency counts (See Appendix B) Defaults: - Cover tone is enabled - Cover tone frequency is 1000Hz Error Codes: E1 - Invalid tone frequency E2 - Invalid Cover tone mode (System wide errors are listed in front of the manual) Example 1: I want a cover frequency of 1000 Hz and 1500 Hz. 022 1000 0665 D or unkey Response: Either "ON/OFF" when controlling cover tone or "Frequency is XXXX and YYYY" Chapter 3 Examples Example 3-1: RLC-2 Audio Routing Variables In order for your voice/cw/dvr messages to be routed where they are intended to go, you need a good understanding of audio routing variables and their function. Defining the system audio routing variables is accomplished using Command 007. This command lists the sources involved with executing commands. Command 007 definitions: Variable 00 define internal events. Internal events are messages that are requested from the internal audio routing variable. Run-time access to this variable is accomplished using Command 039. This variable is mainly not used. Applications for this variable is you want a message routed to places other than the port that executed the event. Default routing of messages is the port that executed the command. The routing defaults to 01, Port 1 Variable 01 defines serial events. When commands are executed from the serial port the responses are routed to the serial port, along with any combination of radio ports. This variable defaults to 01, Port 1. If you enter a variable of 00, the messages will only be routed to the serial port and no other ports. Variable 02 defines scheduler events. This event is not used. The scheduler events enter the routing variables to be used when the scheduler event is entered using Command 064. You should never have to change this variable. It defaults to 01, Port 1 Variable 03 defines execution from Port 1. This variable defaults to routing responses out only Port 1. It defaults to 01. Variable 04 defines execution from Port 2. This variable defaults to routing responses out only Port 2. It defaults to 02. Variable 05 defines execution from Port 3. This variable defaults to routing responses out only Port 3. It defaults to 04. Variable 06 defines execution from Port 4 (Autopatch). This variable has 2 uses. First, it routes ring signals to the correct port when in reverse patch mode 1, second it controls where messages are routed when programming in reverse autopatch mode 2. Before programming this variable determine what mode your reverse autopatch will be operating in. Mode 1 typically is set to 01 (Route ringing out port 1) and mode 2 typically is set to 08 (Route message responses out the autopatch port). This variable defaults to routing responses out only the autopatch. It defaults to 08. Variable 07 defines execution from Port 5. Because port 5 is a receive only port, its responses must be routed to a different port. This variable defaults to routing responses out only Port 1. It defaults to 01. Variable 08 defines execution from the event table. This variable is a master variable that overrides the audio routing variables that are entered with every event. When this variable is set to 00, the audio routing information that is part of the event will be used. If you change this audio routing variable to something other than 00, the value entered with Command 007 will contain the routing information. It defaults to 00, use the audio routing information from the event tables events. Variable 09..11 are not used Event table audio routing definitions: The event tables audio routing variables work similar to Command 007's variables with a few exceptions. Exception 1: If the audio routing variable entered for an event is 00, the audio is routed to the source that executed the command. If the serial port executes a command with a routing variable of 00, the response is routed out only the serial port. If a DTMF channel executes the same command, the response will be routed out the DTMF's channel. Exception 2: If Command 039 is present in the event tables execution. This command can change the routing of messages to selected ports thus bypassing all preset audio routing variables. Conclusion: Normal audio routing variables route to radio ports. Event audio routing is the same except you can assign three special cases that give more flexible routing to commands. Example 3-2: I want to enable DTMF muting on port 1,3 I want to enable DTMF muting on ports 1 and 3, but not on port 2. Port 2 connects to a link system that needs to receive all DTMF codes entered. Command 020 controls the enable or disable of selected ports for mute control. The format of the command requires 2 digits of control data entered in order for the command to execute correctly. The first data is the port number, the second is the control variable. Port 1 control: 020 1 1 D or unkey ; This enables muting on Port 1 Port 2 control: 020 2 0 D or unkey ; This disables muting on Port 2 Port 3 control: 020 3 1 D or unkey ; This enables muting on Port 3 Example 3-3: I want to disable DTMF cover tone on muted ports When the user enables DTMF muting the controller inserts a cover tone to break the silence of the muting action. The feature is nice so users do not key-up on you while you are programming the controller. Without the cover tone, the general user hears only silence. With the cover tone the general user hears a repeating tone beacon while DTMF data is being entered. The controller defaults the cover tone enabled. To disable the mute control: 022 0 D or unkey ; Tone cover is now disabled. Only audio mute is enabled Chapter 4: System Securi ty This chapter deals with system security and command name execution controls. Because all ports have the ability to access the commands in the controller, certain provisions are needed to protect execution. 004: Setting Up the Master System Unlock Codes This command allows the user to enter 16 unique digits for accessing the master unlock codes. When the user requests access to certain commands, and the controller speaks "Error 7", this indicates the need to unlock the controller before execution of the command is allowed. The user must execute Command 005 which will prompt the user to enter 4 codes that range from 0..15. These codes are programmed with this command. <004> (See Below) Parameters: The user must enter 16 digits from the DTMF pad. The digits can be any valid DTMF digit. It is very important to remember these codes for they access the master unlock command. If you forget the digits, and try to access a locked command, then re-initialization of the controller is the only way to access the command. Requested Digits Default Digits User Entered Digits 0 1 1 2 2 3 3 4 4 5 5 6 6 7 7 8 8 9 9 # 10 # 11 1 12 2 13 3 14 4 15 5 Error Codes: (Sys tem wide errors are listed in front of the manual) Example 1: I want to change the access codes to my own codes 004 ABC*1234###94123 Response: The controller will not speak back the codes for security. "System Lock Codes O K" 005: Unlocking the Controller This command allows the user to unlock the controller for accessing locked commands. The user will execute Command 005 and the controller will request unlock codes. These codes can be embedded with garbage codes for added security. The controller only requires the 4 requested codes to be entered in the requested sequence. Refer to Command 004 to program the access password. User : Request password <005 > Cont rollers voice: " Please enter code # # # #" User enters the password to unlock the controller <005 >...PPPP... Cont rollers voice: "System Lock On" If the wrong password entered or Controllers voice: "System Lock Off" If the correct password entered Parameters: ...PPPP... is the password information. The '...' indicate garbage data can be entered before and after the group of password data is entered. Defaults: The password defaults are listed in Command 004's table. Notes: Please note the password if you change it. Serial can bypass the unlock sequence if specified. If you do not note the password table, the serial may be able to change the table if Command 004 is not locked on the serial port. Error Codes: (Sys tem wide errors are listed in front of the manual) Example 1: The user enters Command 005 to get a password and the controller states codes 1,3,5,9 are needed. The user enters the following. 005 34512 1 3 5 9 #AB1239 The data '34512' and '#AB1239' is garbage data. The codes '1 3 5 9' is the correct password. The controller responds 'Controller Lock Off' indicating the lock is now disabled. Response: "Controller Lock Off" or "Controller Lock On" or "Please enter Code # # # #" 006: Locking the Controller This command locks the controllers access. Once the controller is locked the unlock sequence must be re-entered in order to gain access to locked commands. <006 > Parameters: There are no parameters for this command. Defaults: the controller defaults locked Error Codes: (Sys tem wide errors are listed in front of the manual) Example 1: The user is finished with programming and wants to re-lock the controller. 006 D or unkey Response: "Controller Lock On" 027: Rename DTMF Command Name This command allows the user to rename commands using the 3 digit command number as the look-up indicator. <027 > xxx y..y Parameters: XXX is the command number that ranges from 000..245 Y..Y is the 1-6 digit command name The command name can contain any of the 16 DTMF digits. The command names can be up to 6 digits in length Defaults: The command names correspond to the command numbers. Notes: It is important not to name 2 different command names the same name. If you do this the first command name matched will be executed. The controller scans from command number 000 to find a matching command name. If you rename 2 command names the same simply rename the later command name to a different name. The controller scans for name matches beginning with 6 digits down to single digit matches. When the controller finds a possible name match it compares the additional data that is present with the command name to what the controller expects that command names additional data needs. This matching sequence allows command names that are similar to be executed separately. For example: A command name '#' and '#12 with data 13 14' will be executed differently. The controller will match '#' because it does not need additional data and will match'#12' with its command name because it needs 4 digits of additional data. Error Codes: E1 - Invalid command number. Number ranges from 000..245 E2 - Not enough data present (System wide errors are listed in front of the manual) Example 1: I want to rename my autopatch hangup to '#' 027 146 # D or unkey Response: "Command Number is " 028: Command Read Back by Command Number This command allows the user to recall a command name using the command number as the look-up source. This is handy when the command name is not know. The command number never changes so it is therefore a constant that can always be used as a reference. <028 > xxx Parameters: XXX is the command number that ranges from 000..245 Defaults: The command names correspond to the command numbers. Error Codes: E1 - Invalid command number. Number ranges from 000..245 E2 - Not enough data present (Sys tem wide errors are listed in front of the manual) Example 1: I need to recall what I named my autopatch hang-up code. The command number is 146. 028 146 D or unkey Response: "Command Number is " 029: Command Name Compare to Find Command Number This command allows the user to recall a command number using the command name as the look-up source. This is handy when the command number is not know. The command number never changes so it is therefore a constant that can always be used as a reference. <029> x..x Parameters: X..X is the command name Defaults: The command names correspond to the command numbers. Error Codes: E1 - Invalid command name. (System wide errors are listed in front of the manual) Example 1: I need to recall what the command number is for my autopatch hang-up. 029 # D or unkey Response: "Command Number is " 030: Change First,Second,Third Command Name Digits This command allows the user to change the first, second, and third digits of a group of command names. This command is used when a group of commands names needs a common part of the command name changed. This will not effect the command numbers (first 3 digits of the command name). <030 > xxx yyy z..z Parameters: XXX is the beginning command number that ranges from 000..245 YYY is the ending command number that ranges from 000..245 Z..Z is the digits to assigned to the group of commands. Defaults: The first 3 digits of these command names are not defined. All command names are 3 digits in length referenced by the command number. Error Codes: (System wide errors are listed in front of the manual) Example 1: I want to make all my commands begin with the DTMF digit 'C' 030 000 245 C D or unkey Response: "First command number is , Second command number is " 031: Group Assign DTMF Command Mask Assign This command allows the user to assign a DTMF execution mask to a group of commands. Use of this command allows the control operator the ability to keep certain ports from executing certain commands and/or all commands. <031 > xxx yyy zz Parameters: XXX is the beginning command number ranging from 000..245 YYY is the ending command number ranging from 000..245 ZZ is the audio routing variable used to allow access to certain commands DTMF Allowed Execution of the Command Number that corresponds to the device Port 1 +1 Port 2 +2 Port 3 +4 Autopatch +8 Control Receiver +16 (ZZ) Audio routing variable = (port1)+(port2)+(port3)+(autopatch)+(control rx) Defaults: All ports can execute all commands (ZZ=31) Error Codes: E1 - E2 - Invalid command number. Command numbers range from 000..245 E3 - Invalid audio routing variable. Variables range from 00..31 (System wide errors are listed in front of the manual) Example 1: I have a remote base on port 3..I do not want this radio to execute any DTMF commands. (ZZ) Audio routing variable = 1(port1)+2(port2)+0(port3)+8(autopatch)+16(control rx) 031 000 245 27 D or unkey Response: "First command number is , Second command number is " 032: Command Checks Value of DTMF Execution Register This command checks the results of Command 31 on individual command numbers. <032 > xxx Parameters: XXX is the command number ranging from 000..245 Defaults: All ports can execute all commands (ZZ=31) Error Codes: E1 - Invalid command number. Command numbers range from 000..245 (System wide errors are listed in front of the manual) Example 1: I can not execute the "Check cross-point" command 009. I need to see if I am enabled to execute that command. 032 009 D or unkey Response: DTMF Allowed Execution of the Command Number that corresponds to the device Port 1 +1 Port 2 +2 Port 3 +4 Autopatch +8 Control Receiver +16 (ZZ) Audio routing variable = (port1)+(port2)+(port3)+(autopatch)+(control rx) 033: Group Assign Master Unlock Requirement for DTMF This command allows the user to assign lock code requirements for a group of commands. This only effects the DTMF lock/unlock assignment. Serial lock assignments are programmed starting with Command 036. To gain access to a locked command the controller must be unlocked. See Command 004,005, and 006 for unlock control. <033> xxx yyy z Parameters: XXX is the beginning command number ranging from 000..245 YYY is the ending command number ranging from 000..245 Z is the control function 1 - requires an unlock before execution 0 - does not require an unlock before execution Defaults: All commands are unlocked Notes: Command 005, the unlock command can never be locked. If it could be locked access to the controller could never be possible. Error Codes: E1 - Invalid command number. Command numbers range from 000..245 E2 - Invalid control variable. Variables range from 0..1 (System wide errors are listed in front of the manual) Example 1: I want all programming commands except macros, to require the unlock code entered. 033 000 170 1 D or unkey Response: "First command number is , Second command number is " 034: Individually Assign Unlock Requirement for DTMF This command allows the user to assign lock code requirements for individual commands. This only effects the DTMF lock/unlock assignment. Serial lock assignments are programmed starting with Command 036. To gain access to a locked command the controller must be unlocked. See Command 004,005, and 006 for unlock control. <034> xxx y Parameters: XXX is the command number ranging from 000..245 Z is the control function 1 - requires an unlock before execution 0 - does not require an unlock before execution Defaults: All commands are unlocked Notes: Command 005, the unlock command can never be locked. If it could be locked access to the controller could never be possible. Error Codes: E1 - Invalid command number. Command numbers range from 000..245 E2 - Invalid control variable. Variables range from 0..1 (System wide errors are listed in front of the manual) Example 1: I want to allow execution of 'Time-of-Day Reading' 034 055 0 D or unkey Response: "Command number is " 035: Recall DTMF Unlock Requirements on a Command This command checks the results of Commands 33,34. <035 > xxx Parameters: XXX is the command number ranging from 000..245 Defaults: All commands are unlocked Notes: Command 005, the unlock command can never be locked. If it could be locked access to the controller could never be possible. Error Codes: E1 - Invalid command number. Command numbers range from 000..245 (System wide errors are listed in front of the manual) Example 1: I keep getting an Error 7 when I try to read the time-of-day clock, Command 055. Why?? 035 055 D or unkey The lock is enabled for this command. Execute Command 005 to unlock the controller then try to execute the command. Response: "Command number is " 036: Group Assign Master Unlock Requirement for Serial This command allows the user to assign lock code requirements for a group of commands. This only effects the Serial lock/unlock assignment. DTMF lock assignments are programmed starting with Command 033. To gain access to a locked command the controller must be unlocked. See Command 004,005, and 006 for unlock control. <036> xxx yyy z Parameters: XXX is the beginning command number ranging from 000..245 YYY is the ending command number ranging from 000..245 Z is the control function 1 - requires an unlock before execution 0 - does not require an unlock before execution Defaults: All commands are unlocked Notes: Command 005, the unlock command can never be locked. If it could be locked access to the controller could never be possible. Error Codes: E1 - Invalid command number. Command numbers range from 000..245 E2 - Invalid control variable. Variables range from 0..1 (System wide errors are listed in front of the manual) Example 1: I want all programming commands except macros, to require the unlock code entered. 036 000 170 1 D or unkey Response: "First command number is , Second command number is " 037: Individually Assign Unlock Requirement for Serial This command allows the user to assign lock code requirements for individual commands. This only effects the Serial lock/unlock assignment. DTMF lock assignments are programmed starting with Command 036. To gain access to a locked command the controller must be unlocked. See Command 004,005, and 006 for unlock control. <037> xxx y Parameters: XXX is the command number ranging from 000..245 Z is the control function 1 - requires an unlock before execution 0 - does not require an unlock before execution Defaults: All commands are unlocked Notes: Command 005, the unlock command can never be locked. If it could be locked access to the controller could never be possible. Error Codes: E1 - Invalid command number. Command numbers range from 000..245 E2 - Invalid control variable. Variables range from 0..1 (System wide errors are listed in front of the manual) Example 1: I want to allow execution of 'Time-of-Day Reading' 037 055 0 D or unkey Response: "Command number is " 038: Recall Serial Unlock Requirements on a Command This command checks the results of Commands 33,34. <038 > xxx Parameters: XXX is the command number ranging from 000..245 Defaults: All commands are unlocked Notes: Command 005, the unlock command can never be locked. If it could be locked access to the controller could never be possible. Error Codes: E1 - Invalid command number. Command numbers range from 000..245 (System wide errors are listed in front of the manual) Example 1: I keep getting an Error 7 when I try to read the time-of-day clock, Command 055. Why?? 037 055 D or unkey The lock is enabled for this command. Execute Command 005 to unlock the controller then try to execute the command. Response: "Command number is " 040: User Forced Execution Digit Change This command allows the changing of the forced execution digit. This digit forces the execution of the commands entered before the receiver drops. Uses of this digit is the shut-off a receiver when the COR is stuck open, a jammer needs to be shut-off, quicker access to commands, and the list goes on. <040 > x Parameters: X is the new DTMF forced execution digit Defaults: The forced execution digit is the 'D' Notes: It is important not to define the forced execution digit to a commonly used DTMF digit. Once the DTMF digit is defined as being the forced execution digit, it can no longer be used for system wide applications. Typical DTMF digits used are 'D A B C D'. Error Codes: (System wide errors are listed in front of the manual) Example 1: I need the EOF digit to be a '*' so I can use the 'D' in command names. 040 * D or unkey Response: "Condition Entered With A ' 041: Check the Forced Execution Digit This command checks the current setting of the forced execution digit. <041 > Parameters: There are no parameters for this command Defaults: The forced execution digit defaults to a 'D' Error Codes: (System wide errors are listed in front of the manual) Example 1: I need to check the forced execution digit before I begin programming 041 D or unkey * Note: The 'D' in the above example is the forced execution digit. If the digit is actually a '*' then the command entry would look like. 041 * or unkey Response: "Condition Entered With A ' 115: Assign the DTMF Decoder Priority This command gives the controller the ability to assign highest priority to the DTMF decoder. When a port is assigned as highest priority, its activity determines where the DTMF decoder will be located for code input. Normally this port is "Port 5" the control receiver. This command is not discriminate. When the priority port is active, the decoder is changed to this port, regardless of data entry on the currently active port <115 > x Parameters: X is the radio port priority DTMF Allowed Execution of the Command Number that corresponds to the device Port 1 1 Port 2 2 Port 3 3 Autopatch 4 Control Receiver 5 Defaults: (X) is set for the control receiver Error Codes: E1 - Invalid radio port. Number must range between 1..5 (System wide errors are listed in front of the manual) Example 1: I want Port 3 to become DTMF priority. 115 3 D or unkey Response: "Radio Select " Chapter 4 Examples Example 4-1: How to Access Locked Commands The controller has a high security lock-out mode that keeps unwanted users from accessing certain commands. When the controller is un-locked, all commands can be accessed without security. This opens the programming of the controller up to anyone. Therefore the controller has the feature of locking access to any or all of the controllers commands. The only way to access these commands is by entering the correct unlock codes. Once the controller is unlocked open programming is again possible. How to tell the controller to unlock: The controllers unlock command is a challenging unlock code. When the user wants access to the locked commands, simply enter Command 005. This command will respond with the unlock code request. The voice message is 'Please Enter Code X X X X'. 'X X X X' refers to the numbers entered into the access code table (See Command 004). In order to unlock the controller the user must re-enter Command 005 followed by 'X X X X'. If the controller locates these codes correctly it will unlock the controller by speaking 'System Lock Off'. If the codes requested by the controller are incorrect, the controller will respond with the response 'System Lock On'. If you mess-up entering the codes simply execute Command 005 again and the controller will request another set of codes. The controller will never request the same codes twice in a row, and the code numbers will never be the same in the request. For example the controller will never request '1, 4, 4, 15' because there are 2-4's in the-4's in the same request. For security the user can embed the requested unlock code in a string of garbage data up to 100 DTMF digits in length. If the controller requests the unlock code '1 5 A 3' the user can enter the sequence '1 5 A 3' or '1 2 8 5 4 1 5 A 3 4 6 1 2' and the controller will unlock programming. If you notice the correct unlock code is present in the 13 digit sequence, but surrounded by garbage digits. Once programming is complete, the user can lock the controller using Command 006. If the user forgets to lock the controller, the System Un-Lock timer (See Command 050,051,052) will automatically lock the controller. The lock timer is reset after every command is executed without any errors. Example 4-2: Renaming Commonly Used Commands In order for the controller to handle your system existing codes, the RLC-2 has the ability of renaming the command names from 1..6 digits. The command names can contain any of the 16 DTMF digits except the forced execution digit. This digit defaults to the 'D' key. All command names default to their command number. Command numbers range from 000..245. All internal programming that handle any command names uses the command number as the command request. This insures the controller does not need to busy itself by handling the command name that can be as big as 6 digits. For example: In a macro I need to recall a voice message (Command 045). I have renamed this command name to 1234AA. Inside the macro I will use the command number (045) not the name of 1234AA. Rules to follow when deciphering the command name maze: 1) Use the 3 digit command numbers when the controller executes the command 2) Use the DTMF command name when executing from any of the radio\patch ports. 3) When executing from the serial port, use the command numbers, not the command names Default Command Names: All command names are initialized to their command number out of initialization. For example to execute Command 045 you enter 045 out of initialization. All of the manual pages that describe the commands functions begin with the commands command number. Exceptions: 1) Autopatch dial command: Command number = 143 Default command name = '*' Format: '*' followed by the phone number 2) Autopatch hang-up command: Command number = 146 Default command name = '#' Format: '#' hangs the phone up 3) Autopatch last number entered redialed: Command number = 148 Default command name = '**' Format: '**' redials the last number entered 4) Autopatch reset time-out timer: Command number = 149 Default command name = '**3' Format: '**3' will restart the patch time-out timer to its entered value Example 4-3: Renaming Commands In order for the controller to handle your system existing codes, the RLC-2 has the ability of renaming the command names from 1..6 digits. The command names can contain any of the 16 DTMF digits except the forced execution digit. This digit defaults to the 'D' key. All command names default to their command number. Command numbers range from 000..245. All internal programming that handle any command names uses the command number as the command request. This insures the controller does not need to busy itself by handling the command name that can be as big as 6 digits. Renaming commands using Command 027: Command 027 allows the user to rename any command number to a unique command name. The format of the command: 027 XXX #..# D or unkey Where 027 is the default command name of command 027 XXX is the command number needing the new command name #..# is the new command name that ranges from 1 to 6 digits Example: I want to recall my controller time using the code #83 1) Recall the time uses command number 055 2) Execute command 027 The format of the command: 027 055 #83 D or unkey Where 027 is the default command name of command 027 055 is the recall time command #83 is the new command name Exceptions: 1) Command names can not contain the forced execution digit. Forced execution digit defaults to the 'D' key If you need to change the forced execution digit, do it before you name any commands that will contain the new forced execution digit. 2) Duplicate command names are not allowed If you duplicate command names the controller will execute the first name that it comes to. The second instance will never be executed except by the serial port, and internal commands. If you accidentally name two commands the same name simply rename the duplicate command to another name using command 027. Recalling command names is accomplished using commands 028 and 029 028 recalls the command name using the command number as the key 028 XXX D or unkey ; recalls command name of command number 'XXX' 029 recalls the command number using the command name as the key 029 #..# D or unkey ; recalls command number of command name '#..#' Example 4-4: Assigning DTMF, Un-Lock codes, Serial masks The RLC-2 supports assignment of several user options to determine who can execute commands and from what source. The 3 types of masks: DTMF execution mask: This mask is used to determine what ports can execute what commands. If you do not want certain ports from executing commands. Command 031 is provided to assign DTMF masks to a group of command numbers. All commands default to execution from all ports. Format: Assign DTMF mask 031 XXX YYY ## D or unkey Where 'XXX' is the first command number 'YYY' is the second command number '##' is the execution mask (See Command 031) If you only want to assign a DTMF mask to 1 command, then enter that command number for both 'XXX' and 'YYY'. Example: I want port 3 no DTMF access to any commands 1) Calculate the mask (See Command 031) - The mask value calculated: 1 + 2 + 0 + 8 + 16 = 27 2) Execute command 031: - 031 000 245 27 D or unkey ; Allows DTMF execution from all ports except port 3 To check what DTMF execution mask is assigned to a command, see command 032. Unlock codes for DTMF access: This mask is used to determine what commands executed from DTMF can access programming commands only when the controller is unlocked. When the unlock code is assigned, the user must execute Command 005 before these commands can be executed. All commands default unlocked (No command 005 needed). Format: Assign Unlock code for a group of DTMF accessed commands 033 XXX YYY # D or unkey Where 'XXX' is the first command number 'YYY' is the second command number '#' is the lock mask 1=lock, 0=unlock Format: Assign Unlock code for an individual DTMF accessed command 034 XXX # D or unkey Where 'XXX' is the command number '#' is the lock mask 1=lock, 0=unlock To check what unlock code is assigned to a command, see command 035. Example: I want all commands from 000..142, 144,145 and 150..170 to require the unlock code be entered before accessing those commands 1) Execute command 033 for commands 000..142: - 033 000 142 1 D or unkey ; Require unlock code 2) Execute command 034 for commands 143 - 034 143 0 D or unkey ; Command unlocked 3) Execute command 033 for commands 144..145: - 033 144 145 1 D or unkey ; Require unlock code 4) Execute command 033 for commands 146..149: - 033 146 149 0 D or unkey ; Commands unlocked 5) Execute command 033 for commands 150..170: - 033 150 170 1 D or unkey ; Require unlock code This batch of commands only allows certain commands to be executed by the user. All other commands require the unlock code entered. Command 005 can never be locked. If this command were locked, the controller could never be locked. Unlock codes for serial port access: This mask is used to determine what commands executed only from the serial port can access programming commands only when the controller is unlocked. Format: Assign Unlock code for a group of serial port accessed commands 036 XXX YYY # D or unkey Where 'XXX' is the first command number 'YYY' is the second command number '#' is the lock mask 1=lock, 0=unlock Format: Assign Unlock code for an individual serial accessed command 037 XXX # D or unkey Where 'XXX' is the command number '#' is the lock mask 1=lock, 0=unlock To check what serial unlock code is assigned to a command, see command 038. Example: I want all commands execute from the serial port to require the unlock code be entered before accessing those comands 1) Execute command 036 for commands 000..245: - 036 000 245 1 D or unkey ; Require unlock code This batch of commands only allows certain commands to be executed by the user. All other commands require the unlock code entered. Command 005 can never be locked. If this command were locked, the controller could never be locked. Example 4-5: Changing the Digit The controller supports a special DTMF digit called the forced execution digit. This digit is special in the case that it forces the controller to execute the entered digits when this digit is entered. The controller has 3 ways of causing commands to be executed. 1) Receiver drops and causes the DTMF digits, if any, to be executed 2) Timed execution. After the DTMF digits are entered, and if the receiver does not unkey before the timer assigned to the timed execution expires, the DTMF data is executed. 3) Forced execution digit is received. Upon receipt of this digit, the controller will execute the entered digits. The forced execution digit defaults to the 'D' key. Because of the command executer the controller supports, and because the 'D' digit is not used very often, this digit as the enter digit. Other controllers, and earlier versions of software for this controller used the '*' as the forced execution digit. With the new executer on the controller, the '*' is defined for other purposes on the controller. Autopatch access begins with the '*'. 'D' can not be used in any functions on the controller except in the pre-access system. When choosing the forced execution digit, the user must keep in mind that the digit can not be used for any other function in the controller. If you are use to the '*' as this digit, simply include the '*' in your command name. Reverse autopatch access can not use the 'D' unless you have a 16 digit phone system. If you do not then see Command 023 to enable timed execution. This seems to work well with the phone system. Changing the forced execution digit. 1) Verify you do not use this digit in existing command names 2) Execute Command 040 followed by the new Forced digit 040 X D or unkey Where 'X' is you new forced execution digit Response "Command Entered With A 'X' " The controller defaults the forced execution digit as a 'D' Chapter 5: Messages, Tones and Responses This chapter deals with the programming, setup and sending of system voice, cw, and tone messages. 042: Generate a Tone Sequence Out Selected Ports This command is what generates tone sequences for courtesy beeps, paging tones, DTMF regeneration and any function that uses a tone generated tone sequence. Cust om developed tones <042 > xxxx yyyy ddd ppp Parameters: XXXX is the tone counts for frequency 1 (See Appendix B) YYYY is the tone counts for frequency 2 (See Appendix B) DDD is the length of the tone sequence in 10mS increments PPP is the length of the delay between the next tone sequence in 10mS increments Pre- Programmed tones <042 > xx Parameters: XX is the pre-programmed tone sequence (See Below) Tone Name Number Tone 1 Tone 2 Length Pause Bumble Bee 00 3029 0000 100mS 0mS 00 cont. 1999 0000 100mS 0mS 00 cont. 1514 0000 100mS 0mS Yellow Jacket 01 3029 0000 50mS 0mS 01 cont. 1999 0000 50mS 0mS 01 cont. 1514 0000 50mS 0mS Shooting Star 02 1135 0000 100mS 0mS 02 cont. 1135 0000 100mS 0mS 02 cont. 1850 0000 100mS 0mS Comet 03 1999 0000 100mS 0mS 03 cont. 1999 0000 100mS 0mS 03 cont. 1332 0000 100mS 0mS Stardust 04 1332 0000 120mS 0mS 04 cont. 1135 0000 80mS 0mS 04 cont. 0832 1135 80mS 0mS Duncecap 05 2271 1999 200mS 0mS 05 cont. 2271 2856 200mS 0mS Dial Tone 06 2856 2271 100mS 100mS Low-High Beep 07 2000 0000 100mS 0mS 07 cont. 1500 0000 100mS 0mS High-Low Beep 08 1500 0000 100mS 0mS 08 cont. 2000 0000 100mS 0mS Cover Tone 09 1000 0000 200mS 300mS Audible Ring Tone 10 2271 2082 400mS 400mS Notes: The tones are routed to the port that executed them. When a courtesy beep is requested from the event table (See Commands 63,64,65) the controller knows where to route the tones. Error Codes: E1 - Not enough data entered E2 - Invalid pre-programmed tone slot (System wide errors are listed in front of the manual) Example 1: I want to generate a pre-programmed beep #10 042 10 D or unkey Response: There is no voice response for this command 043: Generate a CW Message Out Selected Ports This command generates the CW messages used by the controller. <043> xx..xx Parameters: XX..XX is the CW code table 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 3 03 D 13 N 23 X 33 4 04 E 14 O 24 Y 34 5 05 F 15 P 25 Z 35 6 06 G 16 Q 26 / 36 7 07 H 17 R 27 . 37 8 08 I 18 S 28 ? 38 9 09 J 19 T 29 AR 39 Defaults: CW speed defaults to 20 WPM CW Frequency defaults to 1000HZ and 1500HZ Error Codes: E1 - To much CW data E2 - Invalid CW Character (System wide errors are listed in front of the manual) Example 1: I want to generate a CW message 'KF7FW/R' 043 20 15 07 15 32 36 27 D or unkey Response: There is no voice response for this command 044: Generate a DTMF Sequence Out a Selected Port This command allows the re-generation of DTMF tones down selected ports. With this command the user can send a DTMF data burst of up to 20 digits down any of the ports. <044 > xx yy..yy Parameters: XX is the audio routing variable DTMF Allowed Execution of the Command Number that corresponds to the device Port 1 +1 Port 2 +2 Port 3 +4 Autopatch +8 Control Receiver +16 (XX) Audio routing variable = (port1)+(port2)+(port3)+(autopatch)+(control rx) YY is the DTMF digits DTMF Digit Number Entered DTMF Digit Number Entered 0 00 9 09 1 01 A 10 2 02 B 11 3 03 C 12 4 04 D 13 5 05 D 14 6 06 # 15 7 07 Pause 16 8 08 Defaults: DTMF length = 100mS DTMF pause = 100mS Notes: When re-generating DTMF the controllers tone 1 and tone 2 need to adjusted correctly to provide to correct 'twist'. Most DTMF decoders are not picky about the twist factor. It is a good idea to adjust both tones to about the same level. DTMF re-generation length and pause is programmed with the timer commands (See Commands 50,51,52) for timer numbers. Error Codes: E1 - To many DTMF digits requested E2 - Invalid DTMF digit. Digits must be between 00..16 (System wide errors are listed in front of the manual) Example 1: I want to send a DTMF string 'pause, pause, pause 96 C000 * ' down port 3 044 04 16 16 16 09 06 12 00 00 00 14 D or unkey Response: DTMF digits is the only response 045: Generate a Voice Message This command allows the generation of voice messages. These messages can be either impolite (Can not be interrupted), polite (Can be interrupted and the message is canceled) or polite with a message sent (Can be interrupted and the message is canceled, when the message is canceled an event in the event table is requested. This event can then generate a CW message or another voice message if needed). See Appendix C for the voice word table. <045> xxx..xxx Parameters: XXX..XXX are the voice words for speaking. Notes: There two special words that effect how a voice message is spoken. Word 733: Indicates a polite message that when interrupted will cancel the voice message Word 734: Is the same as word 733 except when it is interrupted it requests an event from the event table. The user could send a CW message when the voice is interrupted. Error Codes: E1 - To much or to little data entered E2 - Incorrect voice word. See Appendix C for voice words (System wide errors are listed in front of the manual) Example 1: I want to speak the message "At You Are On The Repeater, " AT 077 701 You 480 Are 047 On 310 The 421 Repeater 361 Pause 528 700 045 077 701 48 0 047 310 421 361 528 700 D or unkey Response: Response is what you typed in. 046: Delete a Message Slot This command allows the deletion of certain message slots. This is useful when a message is no longer needed. When the message is deleted, there will be no key-ups or delays when the controller requests that message. <046 > xx Parameters: XX is the message slot number. This number ranges from 01..58 Notes: Once a message is deleted you must re-program the message. There is no way to undelete the message slot once it is deleted. Error Codes: E1 - Invalid message slot (System wide errors are listed in front of the manual) Example 1: I need to delete message slot 15. It is no longer used 046 15 D or unkey Response: "Cancel " 047: DTMF Keypad Message Generate This command allows the user to generate a voice message as a keypad test. Up to 20 keys can be entered to generate a voice message. The controller will respond with a voice message that is equivalent to the DTMF entered. <047 > x..x Parameters: X..X are the DTMF digits entered Defaults: There are no defaults for this command Notes: The "Forced Execution Digit" will never be spoken. All other 15 digits will be spoken Error Codes: E1 - To much or to little data entered (System wide errors are listed in front of the manual) Example 1: I want to test my keypads DTMF digits 047 1 2 3 4 5 6 7 8 9 0 A B C D # D or unkey Response: "" 048: Recall a Message Slot 00..33 This command allows the recalling of pre-programmed voice or cw messages. If the slot is empty you will get an error. <048 > xx Parameters: XX is the message slot number. This number ranges from 01..33 Defaults: All message slots are empty Error Codes: E1 - Invalid message slot E2 - Message slot is empty (System wide errors are listed in front of the manual) Example 1: I want to check message slot 14 for its contents 048 14 D or unkey Response: "Voice or CW data if the message is programmed otherwise Error 2" 049: Program a Message Slot This command allows you to program the message slots with voice or cw messages. Slots 51..58 are special analog faceplate slots but can be used for small messages if not used in the analog application. <049 > xx y zzz..zzz Parameters: XX is the message slot number. This number ranges from 01..33 Message Slot Length Description 00 ... Software Version 01..25 20 words User Message Slots 26..33 4 words Analog Faceplate Slots Y is the message type variable: 0 - CW Message 1 - Voice Message 2 - DVR Message ZZZ are the voice words from the Word Table (See Appendix C) or ZZ are the CW characters from the Code Table (See Appendix D) Defaults: All message slots are empty Error Codes: E1 - To much or to little data E2 - Invalid message type. Number must be between 0..2 E3 - Invalid message slot (System wide errors are listed in front of the manual) Example 1: I want to store the voice message in slot 01 "At You Are On The Repeater, " AT 077