Nate Duehr wrote: >On May 14, 2007, at 12:45 AM, Ed Yoho wrote: > > > >>The whole reason for my initial post was to find out if the new S-COM >>7330 can / will support pre-access. It does not mean everyone must use >>pre-access - just those who want to. If it does / will, it can be >>considered for use within systems that utilize pre access. If it does >>not, it goes on the 'does not meet our needs' list. >> >>Ed Yoho >>WA6RQD >> >> > >Ed, > >We've been doing this for a long time with the S-Com Windows >Programmer software out here... a master file with a macro (not to be >confused with controller macros, but in the programmer software >itself) that can replace digits in the file with a "site code", so >our most used features will be programmed into each controller. > >So I guess the answer is, technically ANY controller with the >capability of building custom user-definied macros has the capability >you're asking for by default... the first couple of digits of the >macro becomes the "site code" and the rest is standardized as the >"command" part. > >If you're hand programming, you have to be careful to put it all in >correctly. Using the programming software and pre-written files >helps to keep it all straight if you have multiple sites. > >Macros are wonderful things -- they allow the repeater controller >programmer to create "modes" or "features" that require multiple low- >level events to happen in the system, that have a single (hopefully >short and simple) command to trigger all those events. > >-- >Nate Duehr - WY0X > > > > Nate and all,
I feel like this is being beat to death, but I will try again. What you are doing above is not the same as site preaccess / prefixing as implemented on larger linked systems. 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. 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. 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. Ed Yoho WA6RQD
