GRE Still Planningon Oct Release?

[Ejohnsonmfr]

Well, according to what I've read, GRE is still planning on the October release of the new scanners. I'm thinking of getting the handheld, only because it's easier to transfer from the home to the car (velcro on the dash).
I haven't found much on the cost yet. One projection was around $400 for the multi-trunking digital. I hope so, maybe it'll drive the others down.

 

[Gilligan]

I'd love to go digital right now but I'm waiting until the new releases to see if I like them. And I'm curious to see how Uniden & Radio Shack compete as well.

 

[scanjunkie]

I don't think Uniden really has to compete...they already have a similar product out. And you will probably not see much from RS...

 

[rdale]

$500, not 4

 

[walter900]

Scanners should be released during the summer when all the outdoor activities are going on.... 4th of july, six flags, outdoor concerts, parades, & carnivals just to name a few!!

 

[n4jri]

Yeah, but I don't want to wait until Summer 08! I'd be glad to get one in time for Christmas shopping.

73/Allen (N4JRI)

 

[Ejohnsonmfr]

I agree. I'm tired of waiting. Bring them on!

 

[N4JNW]

Yeah, but I don't want to wait until Summer 08! I'd be glad to get one in time for Christmas shopping.

73/Allen (N4JRI)

You like listening in on mall security too?

 

[Saint]

New Scanners

Did Someone say that one of these new scanners coming out has the discriminator tap already done to it ???
Steve

 

[ka3jjz]

The Wiki is, once again, your friend .... the answer is yes (the PSR600 has such a tap, and likely others...) However, the output is in some sort of ASCII format - it remains to be seen how much rewriting the developers for Pro96Com, UniTrunker, ect will have to do to make it work. How much data is in this ASCII data stream remains to be seen.

73s Mike

 

[mikey60]

The Wiki is, once again, your friend .... the answer is yes (the PSR600 has such a tap, and likely others...) However, the output is in some sort of ASCII format - it remains to be seen how much rewriting the developers for Pro96Com, UniTrunker, ect will have to do to make it work. How much data is in this ASCII data stream remains to be seen.

73s Mike

I look forward to the rewrite of the decode stream... However I don't know when I'll be able to afford on of these radios to be able to get Pro96Com to work with them. Controlling them shouldn't be a problem, decoding will have to wait until I can afford one.

Mike
Pro96Com author

 

[bagmouse7]

If the following is true, then this is not really what I would call a discriminator tap. While it might be useful for the scanner to provide a datastream output, this really limits the programs that will be compatible with the scanner.
An example is Unitrunker. It recovers the trunked datastream from the AF output of a radio with a discriminator tap. It will need to be rewritten if the new GRE scanners only provide an datastream output.
A pure dataslicer output (like the old Optocom could do) on the serial interface could be more flexible since you could then recover the datastream from a PC application listening to the dataslicer output on the serial port. But once again, this would require applications to be rewritten.
I am looking forward to seeing these new GRE scanners. They seem to have some very cool features...

The Wiki is, once again, your friend .... the answer is yes (the PSR600 has such a tap, and likely others...) However, the output is in some sort of ASCII format - it remains to be seen how much rewriting the developers for Pro96Com, UniTrunker, ect will have to do to make it work. How much data is in this ASCII data stream remains to be seen.

73s Mike

Update:
I just checked the Wiki and it says this:
-Built in discriminator data output in simple ASCII output using the PC/IF port
What is unclear is if this PC/IF port is a serial port that just outputs that datastream, or if it also contins the "real" discriminator level audio output...

 

[n4jri]

You like listening in on mall security too?

I'm not quite as mall-active as I used to be, but yes, I enjoy digging out security freqs and am really looking forward to some of the capabilities that this radio is going to lend to the task.

I keep optimized files for security-hunting with my radios, but optimum performance in that arena, can make other things further out of reach. This object-oriented memory thing is going to change that considerabliy.

In fact, I'm already getting lazy about updating my Win96 files, as I look at how lo-tech this makes my PRO96 and PRO97. The 500 isn't hitting the shelves 'till fall and I ALREADY can't live without it!

73/Allen (N4JRI)

 

[n4jri]

I look forward to the rewrite of the decode stream... However I don't know when I'll be able to afford on of these radios to be able to get Pro96Com to work with them. Controlling them shouldn't be a problem, decoding will have to wait until I can afford one.

Mike
Pro96Com author

We should probably all get together and start you a fund, Mike. Pro96Com has done an awful lot for some of us in this hobby.

73/Allen (N4JRI)

 

[WayneH]

A pure dataslicer output (like the old Optocom could do) on the serial interface could be more flexible since you could then recover the datastream from a PC application listening to the dataslicer output on the serial port. But once again, this would require applications to be rewritten.

What is unclear is if this PC/IF port is a serial port that just outputs that datastream, or if it also contins the "real" discriminator level audio output...

Not requiring a slicer allows more people to be introduced to and use trunked software decoding applications. From what I've read all supported trunking formats are supposed to be output. Also, software will not need to be rewritten. You simply bypass the code the software uses for the raw conversion and just send the signaling words directly to that decoding portion of the software.

This is by far the better approach. For those that want to run other applications, which are few, they can tap their own discriminator or use another scanner.

 

[mikey60]

We should probably all get together and start you a fund, Mike. Pro96Com has done an awful lot for some of us in this hobby.

73/Allen (N4JRI)

I'll figure out some method to get one... Maybe I'll win the lottery..

Mike

 

[bagmouse7]

My point is that many programs these days just require feeding the discriminator audio into the soundcard (which then does the conversion into the datastream) so a slicer is not usually not needed. Unitracker is a perfect example. We used to need a slicer to feed a program like trunker that datastream, but as soundcards have become better and computers faster the slicer is often not needed.
I am a programmer, so when ANY code needs to be changed I call it rewritten. Of course the whole program does not need to be rewritten, but some code WILL have to be rewritten to deal with the change.
In any case my only point in posting this was to comment on the fact that it would be nice to have the discriminator audio output from these new GRE scanners.

Not requiring a slicer allows more people to be introduced to and use trunked software decoding applications. From what I've read all supported trunking formats are supposed to be output. Also, software will not need to be rewritten. You simply bypass the code the software uses for the raw conversion and just send the signaling words directly to that decoding portion of the software.

This is by far the better approach. For those that want to run other applications, which are few, they can tap their own discriminator or use another scanner.

 

[FCVPI99]

I don't think Uniden really has to compete...they already have a similar product out. And you will probably not see much from RS...

uniden has nothing on the 500 and 600 radio from what its sounds like

plus not a uniden lover i have had them (796) it sounded like crap and my buddy has a 996 (he said it was a waste of $$) he keep trying to get me to trade him my Pro 96 for it

 

[WayneH]

My point is that many programs these days just require feeding the discriminator audio into the soundcard (which then does the conversion into the datastream) so a slicer is not usually not needed. Unitracker is a perfect example. We used to need a slicer to feed a program like trunker that datastream, but as soundcards have become better and computers faster the slicer is often not needed.

What about LTR? It requires a dedicated low-pass filter regardless of what you use. Software just doesn't compare (like decoding DTMF for example) to hardware decoding or filtering in these situations.

I don't see having a discriminator tap as a huge selling point that the GRE decision makers would agree is one; more a hidden feature if there was one. Though using the soundcard isn't that new of an idea it still is not a good defense for having the tap point. I'm sure they would also like consumers to use the radio for what it's for, which is take advantage of its features. With what they have so far it doesn't require anything done on the hardware side as it's all software. Providing a tap point would require an extra effort to tool into the physical build, which is quite a lot for a "hidden feature".