On May 15, 2007, at 10:44 AM, Ed Yoho wrote: > The method above gives 27 separate commands (example 27 pl on > codes) for > 27 sites regardless of where the command originates. As a user travels > throughout the network coverage area, the command requirements change > for the repeater input he/she is currently using. The user must > constantly be aware of which site prefix number he/she is using.
Ah okay I understand now. > Site prefixing / preaccess as implemented uses a standard command set > across the network for ALL repeater inputs. No matter where you are > within the network coverage range, you can enter the same exact > command > and get the same exact results from the local repeater (assuming the > command is implemented locally - ie autopatch commands only work on > sites with autopatches implemented). A user can enter ##12345 on any > site and expect the same thing to occur. The only time a different > command sequence is required is when a remote (non local / linked) > site > is commanded. This is where the site specific prefix is used (from the > link and not the mobile input). All commands from the mobile input are > prefixed with ## (##12345) and all commands from a distant linked site > are prefixed with the site specific code *#373 (*#37312345) or > whatever. Okay. > Your method would require two sets of macros - one with a ## prefix > and > another with *#373 or whatever. You would still need to map the > prefixes > to only one portion of the system (mobile input or links). Otherwise > every time someone entered ##12345 it would be recognized and operated > on by all linked sites. DISCLAIMER: I haven't had a chance to try it on a real controller to see if it happens fast enough, so it'll react quickly enough, and my 7K is currently up on a mountain filling in until a few 7330's arrive. (GRIN) Here's a way to do it. I don't know what number of macros you could get away with, but probably enough. I'm too tired to look up the limits and do the math. First off, on all sites... SITECODE12345* does something on a specific site and these macros are always active and programmed separately into specific controllers. Next, set up a hidden start-of-activity macro on all controllers on only the local user port's receiver (RX1) that renames macros stored in "parking" macros to the local macro commands that users would use locally. The parking macros are unpublished. Example, A12345 gets renamed 12345, and A23456 gets renamed 23456. A12345* (and it's cousin, the renamed 12345* whenever local user activity is present) is a macro that calls the local repeater's SITECODE12345 macro. During "local commanding", other repeaters in the network will be listening for the "parking" macros and won't respond to the command. Only the repeater(s) with active RX1's will respond to the "local" commands. Then an end-of-activity macro calls a 2nd hidden macro that names all "local" macros back from their new 12345 to A12345. Now, obviously that leaves a problem... if two repeaters in the network are both keyed on their user inputs when a so-called "local" command is executed, both will respond. To make this more robust... You tell end users that "All commands are available by typing the sitecode and the command on any repeater. However, if you don't want to type the sitecode, press 1* plus the command on your local repeater." In this case, you set up 1* to mute DTMF. Your end-of-activity macro now must both copy the local macros back to "parking" and unmute DTMF. (In fact, if you do this you don't need the start-of-activity macro at all, but I like that one better. You could have *1 do both setup of the macros and the DTMF mute.) To make this work, the default "*" as "enter" key option in the S- Com, must be on. This is so users don't even have to unkey to have the 1* execute. The users don't have to know the preceeding 1* is a separate command. They just know to prefix any local "simple" command with 1*. If they hit 1* and drop key, the local controller will immediately revert back to only responding to the SITECODE commands, and unmute DTMF, resetting everything back to the state where any machine in the system can respond to either a local or remote SITECODE prefixed command. -- Nate Duehr - WY0X [EMAIL PROTECTED]
