spooney said:
Yep, look at the first post of this thread (and a few other threads) for the link to the FCC draft manual.
PSR-500 and PSR-600 Pre Release (Continued)
- Thread starter DaveIN
- Start date
- Status
Yep, look at the first post of this thread (and a few other threads) for the link to the FCC draft manual.
KC9NEG
Member
Why?
Assuming you're interested in digital (of course) I can only speak to my experience of Uniden (396T) vs. GRE (Pro-96). I know it's an old debate, but IMHO GRE simply spanks Uniden when it comes to digital. The PSR500/600 _should_ be even better than the Pro-96. I'm sure GRE's learned a bit in over three years. Again, all my opinion, but if Uniden's latest can't outperform the previous generation of GRE's, the new generation of GRE's should be even better by comparison.
As always, YMMV
Todd/Indy
BOBRR said:
Assuming you're interested in digital (of course) I can only speak to my experience of Uniden (396T) vs. GRE (Pro-96). I know it's an old debate, but IMHO GRE simply spanks Uniden when it comes to digital. The PSR500/600 _should_ be even better than the Pro-96. I'm sure GRE's learned a bit in over three years. Again, all my opinion, but if Uniden's latest can't outperform the previous generation of GRE's, the new generation of GRE's should be even better by comparison.
As always, YMMV
Todd/Indy
Statevillian
Member
Quick Question.... I am not familiar with the object concept. If I enter a c onventional frequency and give it an alpha tag is that 1 or 2 objects?..... If i enter trunked frequencies...let's say 4 and 20 TGs and have 3 scan lists does that mean I have 27 objects not counting any alpha tags?.... Thanks!
Statevillian
Statevillian
KC9NEG
Member
#1: 1 object
#2: Each trunked freq (Control Channel) is one object. Each TGID is one object. Scan lists aren't objects.
The new GRE's hold 1800 objects in any combo which can be organized into 20 scan lists. An object can be in more than one list. This whole setup can be saved to a "V-scanner" so you can essentially have 21 entirely different setups on hand all the time. It's like having a laptop and programming software, wiping and reloading the radio at will (except it's all carried in radio memory).
This is all explained in the manual, including what constitutes an "object". It looks like a great system to me. Can't wait to get mine.
Todd/Indy
#2: Each trunked freq (Control Channel) is one object. Each TGID is one object. Scan lists aren't objects.
The new GRE's hold 1800 objects in any combo which can be organized into 20 scan lists. An object can be in more than one list. This whole setup can be saved to a "V-scanner" so you can essentially have 21 entirely different setups on hand all the time. It's like having a laptop and programming software, wiping and reloading the radio at will (except it's all carried in radio memory).
This is all explained in the manual, including what constitutes an "object". It looks like a great system to me. Can't wait to get mine.
Todd/Indy
Statevillian
Member
Thanks Todd. I did some reading but wasn't entirely sure. This capacity is just mind blowing. I pre ordered mine from Glenn at Scanners Unlimited. #3 on the list! If the release dates are correct......24 more days. It's like counting down to XMAS as a kid.
tbhausen said:
Actually, the news is even better than that. The system info for any trunked system is contained in a single object. That TSYS object includes all control channels (or LCN's for EDACS or LTR), trunking tables, and the system alpha tag. All in one object.
This can be a little hard to believe when reading the manual because each conventional frequency DOES require its own object.
Part of the confusion comes from the fact that you have to develop your TSYS (System) object as part of the process of setting up your first TGRP (talkgroup) object.
A lot of this will probably clear up when we get a newer version of the manual, or some software to play with. Will someone PLEEEEZE write some software to keep me sane until those radios come in!
73/Allen (N4JRI)
KC9NEG
Member
Interesting--I knew TSYS was created inside TGRP (and new TGRPs can contain new or "recycled" TSYS). But I see now that multiple freq's can be entered when setting up TSYS. Gotta "read between the lines" a bit but yes, it keeps getting better. I'd LOVE to see the final manual. I'm sure it's done and off for printing by now. Somebody from GRE (or a dealer, maybe?) PLEEZE throw us a bone here 
Todd/Indy
Todd/Indy
D
DaveNF2G
Guest
I preordered a PSR-500 from Universal Radio last week. I got a phone call from them the other day telling me that the in-stock date has been pushed back to December.
KC9NEG
Member
Maybe you're late in a backorder queue? I hope this isn't true.
Todd/Indy
Todd/Indy
fmon
Silent Key Jan. 14, 2012
I just talked with a Groves rep and they are still with mid Oct time frame.
I have never really totally understood object oriented programming. It was (and to some degree) still is big in data bases and programming. But for this case I will make a real WEAK attempt. A friend of mine once said they fumbled with OOP (object oriented programming) for a year or so, then one day the light came on and it became clear. I still need a white cane.
Reading some of the posts here and the manual an object contains the information for a system (trunked) or frequency (conventional).
So for a trunked system, the object is all the frequencies (or control channel freqs) and system talk group IDs entered. I am guessing this can be considered an object because when scanning, the scanner is really only listening to a single frequency, the active control channel. The scanner reacts to what the CC is telling it. If the channel is open (no IDs), then any TGID will be heard.
This is also why a conventional frequency is its own object. There is really nothing else to truly associate with it. It may seem that something like a police department (I'll use Tucson where I started my scanning and which is conventional) where each frequency is part of the system, but dedicated to a specific use.
The sharing of information across objects is the area where I bog down in OOP. It seems to be a math type use of sets and unions. I'm sure most of us remember drawing overlapping circles (the set) in math. The overlaps were the unions. Each object is a set and these sets may overlap (the unions).
I hope this makes more sense to me when I get mine (I'm number 18 on Glenn's list). I am still pretty much row and table oriented when it comes to data base organization. Maybe this will be the light I need.
Reading some of the posts here and the manual an object contains the information for a system (trunked) or frequency (conventional).
So for a trunked system, the object is all the frequencies (or control channel freqs) and system talk group IDs entered. I am guessing this can be considered an object because when scanning, the scanner is really only listening to a single frequency, the active control channel. The scanner reacts to what the CC is telling it. If the channel is open (no IDs), then any TGID will be heard.
This is also why a conventional frequency is its own object. There is really nothing else to truly associate with it. It may seem that something like a police department (I'll use Tucson where I started my scanning and which is conventional) where each frequency is part of the system, but dedicated to a specific use.
The sharing of information across objects is the area where I bog down in OOP. It seems to be a math type use of sets and unions. I'm sure most of us remember drawing overlapping circles (the set) in math. The overlaps were the unions. Each object is a set and these sets may overlap (the unions).
I hope this makes more sense to me when I get mine (I'm number 18 on Glenn's list). I am still pretty much row and table oriented when it comes to data base organization. Maybe this will be the light I need.
DaveNF2G said:
Could be, but they need to change their web site if this is true. It says 10/20.
An object is one of the following: a trunked system, a talkgroup (which is then linked to the system), a conventional channel, a stalker search, a service search, and a standard range search.
Basically, in order to get direct access/be a member of a scan list it has to have an object ID so those (above) are seen as objects. You would enter the object ID in like you would a channel with any normal scanner (Uniden dynamic memory ones excluded). You don't need to know the scan list. An object is essentially "attached" to a scanlist or lists.
Basically, in order to get direct access/be a member of a scan list it has to have an object ID so those (above) are seen as objects. You would enter the object ID in like you would a channel with any normal scanner (Uniden dynamic memory ones excluded). You don't need to know the scan list. An object is essentially "attached" to a scanlist or lists.
Ah, so this is a bit like programming Motorola Spectras or Thales25/Racal25 portables.
With the Racal you build a list of channels and their various attributes. They are then attached to a zone or scan list.
With a Spectra the same channel or what they call a "mode" can be linked to different zones "banks" of channels simultaneously.
With the Racal you build a list of channels and their various attributes. They are then attached to a zone or scan list.
With a Spectra the same channel or what they call a "mode" can be linked to different zones "banks" of channels simultaneously.
"So for a trunked system, the object is all the frequencies (or control channel freqs) and system talk group IDs entered."
No. One object for all control channels, each TGID is its own object too.
No. One object for all control channels, each TGID is its own object too.
KC9NEG
Member
The more I ponder it, the more I think I'll realy love the new GRE OOUI. Sure wish I could get the final manual.
Todd/Indy
Todd/Indy
It really is a great setup. A talkgroup is an object that you listen to just like a frequency. Think of the trunked system as simply a group of objects (the TG's) which simply require one more object (the system) to service them as a group.
What I like is the fact that if you're only interested in something like Fire Dispatch, you could load up a scan list with maybe 20 fire dispatch TG's, each of which would use one TGRP object and one TSYS object. That means you can get precisely what you want from twice as many systems as the PRO96 can accommodate, have them all in the same bank (scan list, sorry) and use only 40 of your 1800 objects.
If you wanted Police Dispatch from the same systems in another list, you could add the 20 police dispatch TG's for the same systems and they'd use the same TSYS objects that you already entered for Fire. I really like the idea that you don't have to confine everything in a trunked system to just one bank.
73/Allen (N4JRI)
What I like is the fact that if you're only interested in something like Fire Dispatch, you could load up a scan list with maybe 20 fire dispatch TG's, each of which would use one TGRP object and one TSYS object. That means you can get precisely what you want from twice as many systems as the PRO96 can accommodate, have them all in the same bank (scan list, sorry) and use only 40 of your 1800 objects.
If you wanted Police Dispatch from the same systems in another list, you could add the 20 police dispatch TG's for the same systems and they'd use the same TSYS objects that you already entered for Fire. I really like the idea that you don't have to confine everything in a trunked system to just one bank.
73/Allen (N4JRI)
bonus1331
Member
n4jri said:
I'm still trying to get my head around (also known as convincing myself to buy;-)) why this "architecture" is any better than my Uniden's DMA?
We can already mix and match any combination with the newest Unidens; but without the 20 scan list limit. (99 systems with 396/330/15/996).
Please....try and convince me not to pre-order since I already have 4 radios....
no really, please!!
fmon
Silent Key Jan. 14, 2012
Are you saying the 20 scan list is severly limited in systems? Read that back to me in the OM.bonus1331 said:
Saw a post earlier today where a 396 user was pissed when a warning appeared as he tried to enter the 251st talkgroup for a statewide system.
Let's say in a current scanner you want have bank 1 be Ingham County Fire (on a trunked system) and Eaton County Fire (conventional) and Clinton County Fire (different trunked system.)
Then bank 2 = IC police (same as IC fire trunked), EC police (conv) and CC police (same as CC fire trunked.)
You scanner would take 1-2 seconds to scan ICF, then ECF, then CCF, then another 1-2 seconds for ICP, ECP, CCP. You'll take 6-8+ seconds scanning all of those.
Now in the PSR500, you scanner only looks at the Ingham Co control channel once and will open up ICFire or ICPolice if there is a tranmission. Then it checks the conventionals, then it checks Clinton County's trunked just once. You scan everything in 1-2 seconds total. So in that aspect it breaks apart the trunked system, only scanning the control channel once and opening up for any scanlist that has an active talkgroup.
Also your ability to enter a BOATLOAD of talkgroups in your system doesn't exist elsewhere.
Then bank 2 = IC police (same as IC fire trunked), EC police (conv) and CC police (same as CC fire trunked.)
You scanner would take 1-2 seconds to scan ICF, then ECF, then CCF, then another 1-2 seconds for ICP, ECP, CCP. You'll take 6-8+ seconds scanning all of those.
Now in the PSR500, you scanner only looks at the Ingham Co control channel once and will open up ICFire or ICPolice if there is a tranmission. Then it checks the conventionals, then it checks Clinton County's trunked just once. You scan everything in 1-2 seconds total. So in that aspect it breaks apart the trunked system, only scanning the control channel once and opening up for any scanlist that has an active talkgroup.
Also your ability to enter a BOATLOAD of talkgroups in your system doesn't exist elsewhere.
- Status
Similar threads
- Locked
