wavetar wrote: maelv wrote:
dsotm wrote:It's not a bug - you have to specify the 'Contact Name' under the TX side of the channel screen. It's just one of those new digital parameters that we don't have on the analog side.
The reason it works when you copy and paste from the sample file is that the sample file's sample channel was setup using a group call called 'Call1'. The CPS can't read our minds and know which Contact Name we want to use for new channels and it can't just use 'Call1' as the default for new channels because there's no guarantee that 'Call1' exists in a radio other than the example.
After you add all your digital channels you can use multiple-selection by clicking on your first digital channel in the treeview, hold down the shift key and then click on the last digital channel, now with all the digital channels selected, you can change the 'Contact Name' on the right hand side once and it will set it for all your digital channels at the same time.
Multiple-selection is a neat trick to change any other parameters for multiple channels.
YOU ARE EXACTLY RIGHT
Thanks dsotm for your reply that relly help me.!!!!!!!
it was an programming error from my side.. maybee it is because i have never used the motorola cps before
Yes, thank you. You'd think an hour on the phone with Moto tech support would've brought that little tidbit out at the time, but it didn't. I found out later on that you can't have "none" as the contact name, but didn't put 2 & 2 together & check to see if that's what happened when adding channels.
MotoTRBO (and its programming) is a bit of a new concept for most of us. Actually, a couple of hours spent going over the "System Planner" is helpful.
MT uses the concept of "talkgroups," which are logical channels (as opposed to physical channels) comprised of a group of users whose function means that each should hear the transmissions of all. This is similar, at least logically, to "talkgroups" in a SmartNet trunked system.
However, the similarity does not extend to the physical. In a conventional system, of course, there is a perfect overlap between logical channels and physical channels. In a trunked system, logical channels remain logical until a group call channel grant OSW is issued, at which point the subscriber equipment of the members of the logical channel all shift to the deployed voice repeater, which makes up a concurrent physical channel.
In MT, there are only two physical channels, represented by the A and B time slots on a two-slot TDMA digital voice system. A "talkgroup" is defined by its TGID; when a user presses his PTT, his radio (vs. the controller in a trunked system) sends an instruction (via a data packet) to all other radios on his time slot saying, in effect, "If you are listening to this TGID, open audio."
While this can be changed by programming, in the usual set up, once a given TGID issues an audio call, the "channel" (i.e., the time slot) is preempted for use by only that TGID for a given period of time; any other TGID on the same slot will get a "denied" tone if a member tries to key up until the preemption timer times out. Interestingly, this preemption is handled by the software in the subscriber equipment: except for TDMA slot synchronization, there is no supervisory control effected by the MT repeater itself.
Now, here's a wrinkle. When you define a "talkgroup" in a subscriber radio, you also have to define the "talkgroups" that the radio will hear when selected up on this entry, and you have to define the "talkgroups" that will be addressed by a group call command issued by that radio. In theory, you can have a "talkgroup" hear more than itself and address more than itself. At least with respect to true group definitions (i.e., what is sometimes called "one-to-many" and sometimes called "dispatch radio"), there is no reason for doing this. MT permits scanning of multiple TGs.
Therefore, RKG's Rule #1 for MT programming: When defining a TG, the "Rx Group" and the "Tx Group" should each consist of a single entry, namely the same TG.
If there is a reason for all of this (beyond the fact that the MT programming may well be the brain-child of some 20-year old raised on PC games), it is that both group definitions for true talkgroups and individual or "private" definitions for the MT equivalent of the SmartNet Private Call ISW are defined on the same page. That is to say, you can have a channel slot in your radio that, when you select it and then key, brings up only Fred's radio.
A couple of things to bear in mind. Unlike trunked radio, physical channels cannot be assigned on the fly, and a TG that "homes" to TDMA Slot A cannot utilize Slot B if Slot A is otherwise in use. Rather, on any given "channel" in the selector list, a MT subscriber unit is dedicated to one Slot or the other, and if the Slot is in use, the radio cannot transmit. (Again, barge-ins can be allowed by programming, but in general the statement made is true.) From this perspective, "talkgroups" in MT bear a strong resemblance to "talkgroups" in conventional (i.e., non-trunked) Astro 25. These, in turn, probably derive from the concept behind QC or MDC "selective calls," though control is via data packets, not signalling tones.
Now, if I've put a bunch of folks to sleep, sorry; this is all new. I cannot overemphasize that someone breaking in to MT would do well (and save himself a lot of headaches) by investing a couple of hours to read (and re-read) the "System Planner."