[Trunkcom] MultiNet

Sun, 6 Jan 2002 15:07:44 -0500 (EST)

Well, you won't be able to put very many users on only a 3-channel system,
but person requesting the license should have had this in mind.  The FCC
would have given you more channels if you had indicated how many radios
would be working on the system.  For example, a five channel system you
could get with 70 radios but they'd like for you to have at least
100.  You figure 100 radios per channel, then a 3 channel would be able to
do 300 radios, but remember you have to think that new agencies could join
your system who either had no radios or just a few that would add to the
 equation.

On Sun, 6 Jan 2002, SJ wrote:

> --------Remember, if you have 3 channels in a system, there
> can only be 3 simultaneous conversations going on.------------
> 
>  That's what I meant, really. I mean think about it, you have say 3
> channels,3 very busy channels at one given time. It just doesn't make any
> sense to put more than 3 agencies/businesses on that system, especially if
> one of them is public safety(I'm theorizing LTR here). 3 years ago when we
> had the ice storm, I had 2 scanners going on the county trunk system just to
> keep up. We had people using their old low band stuff just to keep in touch,
> quite confusing.
>  It is possible, however unlikely, that this will happen again. considering
> the cost of the system, one would think they would have added a couple more
> freqs.
> 
> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]]On Behalf Of Larry Williams
> Sent: Saturday, January 05, 2002 10:36 PM
> To: [email protected]
> Subject: Re: [Trunkcom] MultiNet
> 
> 
> Man, you must not have much excitement in life if you have to worry
> about "busy tones".  Remember, if you have 3 channels in a system, there
> can only be 3 simultaneous conversations going on. So many low end users
> think of it as a CB and use it accordingly. They are in their trucks and
> get bored so they talk to the other bored drivers. THAT, eats up air
> space. Especially on a multinet system or any other where you have
> selective calling between individual users.  5 chan system, 1 company,
> 20 bored long winded drivers, ... BUSY SIGNALS.  By the way, same goes
> for cops and public service folks as well.
> 
> It would be interesting to see if someone was encountering a busy signal
> or two or  more.  At least when we made the move to the system here they
> told us about busy tones, and said that the chances of someone getting
> one
> were slim to none, but I heard that in Warren, Michigan they were
> telling
>  non public safety workers to quiet down because of busies.  By the way
> I
>  found out that Warren will be adding its old MDT channel to the trunked
>  system pool, because they just switched services, so the 856.0375 will
> soon
> be part of the system.
> 
> ------------------------
> >snip<
> Come on now. The only way you heard the LTR burst on the bus radios was
> if it was running conventional on the same freq as the LTR channel.  If
> it was LTR, the radio had to either been modified or defective.  The
> only thing you can "HEAR" on an LTR channel burp is the squelch on your
> radio opening and closing, period. The NEW Kenwood LTR radios have what
> is called FleetSync where they send out MFSK data either at the
> beginning or end of transmission that contains a 7 digit code that is
> unique for each radio in a fleet. It can also be used to send canned
> status messages or even short and long data messages like a MDT. You can
> hear that data but its only been in use a couple of years.
> 
> 
> >         Now, the LTR system that I used to have to listen to all the time
> > on 800 MHz in school like I said had the burst, and it was even coming in
> > over the bus radios.  This bus company is now on 900 MHz with I think a
> > conventional system but they are using CTCSS tones from what I've
> > noticed.  Aren't the newer LTR or multi-net systems using tones or data
> > bursts you can't hear?
> 
> _______________________________________________
> TrunkCom mailing list
> mailto:[email protected]
> http://mailman.qth.net/mailman/listinfo/trunkcom
> 
> _______________________________________________
> TrunkCom mailing list
> mailto:[email protected]
> http://mailman.qth.net/mailman/listinfo/trunkcom
> 