PSR-500 and PSR-600 Pre Release (Continued)

[proquist96]

The PSR has a upgrade for the cpu firmware which i think is responsible for dealing with rebanding,the 96 doesn't. Thats the smoking gun. It seems that the new scanners will truly be upgradable and i will be happy to get one..

 

[bonus1331]

Am I missing something here?
The 500 will still have the 1800 "objects" contained within 20 scan lists along with the V-Scanners.
If this is the case, are we all still not going to be hand-cuffed to 20 "scan lists" or banks?
Meaning, does this still leave Uniden's Dynamic memory the more flexible of the radios?
I have over 40 systems loaded in my 330/396/15.

Am I correct in my assumption?

 

[rdale]

Do you really listen to all 40 individually? I can't imagine how long that takes your Unidens to go through!

 

[WayneH]

Do you really listen to all 40 individually? I can't imagine how long that takes your Unidens to go through!

Exactly! The GRE has a better approach in that it allows you to organize more for a regional area versus having to have a cheat sheet to remember which banks to enable when you travel to another area. With the GRE you just load up a new V-folder and go.

Though the Unidens have it with the sub-systems within a system. I'll give that to them. So, basically, neither one of them is perfect but they each allow a choice for how YOU will organize. Uniden needs to get on the ball and add NAC decoding to the 396/996 line (So my 396 will get some use). They're about to be left in the dust.

 

[DaveIN]

The part that is interesting to me is that you should be able to share talkgoup "objects" between more than one tower in a statewide system. This should speed up the scanning process for multi-trunking in these type of systems, as well as save on programming steps.

 

[DaveNF2G]

I use the System Quick Keys according to a numbering system that enables me to know where each system is located when I need to enable or disable it. One of my 396 profiles contains 53 systems and I have no trouble finding anything.

However, rdale's point is valid. It does take a long time to scan through that many objects.

 

[Stick0413]

The part that is interesting to me is that you should be able to share talkgoup "objects" between more than one tower in a statewide system. This should speed up the scanning process for multi-trunking in these type of systems, as well as save on programming steps.

Same thing as the 996.

Also agree that I like the 20 system along with 20 V-Folder approach better than just plain dynamic memory. I don't see anyone needing more than 20 in one area. I am sure it will be the same way the 996 is in that you can have mutiple groups under the initial system (i.e. on conventional freqs you can have a group of Fire, Police, Misc, ect. or under a trunked system you have both mutiple sites and you can group your talkgroups how you wish.) So you can organize everything into areas, say V-Folder 1 is XXX area of this state, and V-Folder 2 is YYY area of this state and you can change into the other with a few keystrokes. Really I think its taking the best of both worlds, the dynamic memory of the Unidens and the V-Folders of the RS/GREs.

 

[rdale]

It's not the same thing at all at the 996... Close - but the ability to put the talkgroups in different scanlists is not possible with the 996.

 

[UPMan]

I don't see anyone needing more than 20 in one area.

I have 110 systems assigned to 46 SQK's for just the DFW area.

 

[loumaag]

I have 110 systems assigned to 46 SQK's for just the DFW area.

But Paul, your hardcore! :lol:

Seriously, this argument goes both ways. Personally I hate the V-Folder concept. I barely use them on my Pro-96 or 2096 (and only because of limitation of 10 banks). If GRE wanted to go with dynamic memory, why make you have to load/unload V-Folders when the memory is all there; just let it be a pool and you can choose what you want to listen to. The objection that this requires a "cheat sheet" to remember what is assigned to what key does not change just because you load it in V-Folder except in addition to having to remember what key is what, you now have to remember what V-Folder is what. My solution would have been to make 1000 system keys available (000-999) and just let it be one big pool of memory. For those of you who like to keep things organized, you could have done it by using the hundreds for areas, or anything else. This load/unload feature of V-Folders (especially when mobile) is both a pain and a unnecessary added step in a dynamic memory architecture.

 

[n4jri]

Guys, there is no 20-system limit on this thing. Each TGRP is an object, and the data for each system is an object. There are 1800 objects. You can have as many talkgroups and systems a you want, provided that the number of TG's plus the number of different systems doesn't total to more than 1800.

It is true that there are only 20 scanlists, and this means that you might have to have more than one trunked system in the same scanlist. You can also have anything you want in that same scanlist. I would like to see more different scanlists myself, but I think I can make do with 20.

The V-folder concept may not provide the maximum degree of instant access, I will admit. But it's been very popular with PRO-96 users and it allows the 500 to have about three times the total capacity of the 396/996, so I don't think it's too bad a trade-off.

73/Allen (N4JRI)

 

[detroit780]

V Folders

Actually it's easy to remember what is in which V-Folder. Label each V-Folder by area. When travelling hit PGM FUNC PGM Press 2 for load and then press any number key to view the name of the V-Folder. In Michigan I name the V-Folders by County, several counties per V-folder or only one depending on what I actually want to listen to. So remembering is not an issue.

When I fly to another location I keep one V-folder as my home set-up and then the others get programmed for my travels.

I use the V-Folders almost everyday.

But Paul, your hardcore! :lol:

Seriously, this argument goes both ways. Personally I hate the V-Folder concept. I barely use them on my Pro-96 or 2096 (and only because of limitation of 10 banks). If GRE wanted to go with dynamic memory, why make you have to load/unload V-Folders when the memory is all there; just let it be a pool and you can choose what you want to listen to. The objection that this requires a "cheat sheet" to remember what is assigned to what key does not change just because you load it in V-Folder except in addition to having to remember what key is what, you now have to remember what V-Folder is what. My solution would have been to make 1000 system keys available (000-999) and just let it be one big pool of memory. For those of you who like to keep things organized, you could have done it by using the hundreds for areas, or anything else. This load/unload feature of V-Folders (especially when mobile) is both a pain and a unnecessary added step in a dynamic memory architecture.

 

[Stick0413]

Actually it's easy to remember what is in which V-Folder. Label each V-Folder by area. When travelling hit PGM FUNC PGM Press 2 for load and then press any number key to view the name of the V-Folder. In Michigan I name the V-Folders by County, several counties per V-folder or only one depending on what I actually want to listen to. So remembering is not an issue.

When I fly to another location I keep one V-folder as my home set-up and then the others get programmed for my travels.

I use the V-Folders almost everyday.

Exactly... On the Pro96 all you have to do is use the bottom line of the Welcome message and that is what shows up as the V-Folder name. I guess its just a matter of personal preference though and personally I do like the V-Folders.

 

[loumaag]

Exactly... On the Pro96 all you have to do is use the bottom line of the Welcome message and that is what shows up as the V-Folder name. I guess its just a matter of personal preference though and personally I do like the V-Folders.

Certainly the name appears, then you get to wipe out what is in memory for another setup. Somehow I guess I see scrolling to a named system in the active memory (providing you don't remember what quick key you have it stored under), then enabling it just seems a little easier than that. But everyone has their own opinion.

 

[kikito]

The PSR has a upgrade for the cpu firmware which i think is responsible for dealing with rebanding,the 96 doesn't. Thats the smoking gun.

Yes, IT IS true that the new PSRs have upgradeable firmware, so? Is it just for rebanding purposes? NO.

Upgradeable firmware is the most flexible way to change, fix or improve anything related to the scanner's features and capabilities. It does NOT have to do strictly and only with rebanding. Probably all scanners from now on, even after rebanding is completed (if ever), will be CPU/DSP firmware upgradeable. Just like computers, GPSs, PDAs, iPods and all kinds of other consumer electronics. If you ask me, I'll have to say: It's about time they had upgradeable firmware capabilities!

Why are you still stuck with that feature only having to do with rebanding? :roll:

 

[proquist96]

Yes, GRE scanners are now fully upgradable which will keep them cutting edge for years, I only hope the Unidens are Biodegradable.

 

[n4jri]

Yes, GRE scanners are now fully upgradable which will keep them cutting edge for years, I only hope the Unidens are Biodegradable.

ROTFL!

 

[kikito]

Yes, GRE scanners are now fully upgradable which will keep them cutting edge for years, I only hope the Unidens are Biodegradable.

Nevermind, I realize now your "trolling" ways... what a waste of time ever paying attention to your childish bull$#17....

 

[WayneH]

Nevermind, I realize now your "trolling" ways... what a waste of time ever paying attention to your childish bull$#17....

Please, lets not start an argument.

 

[DaveIN]

There is a nice two page ad in the center of the October issue of Popular Communications for the PSR-500 and all the other models are mentioned as well.