Official PRO-2096 Discussion Thread

Status
Not open for further replies.

Voyager

Member
Joined
Nov 12, 2002
Messages
12,059
mlevin said:
Better guess this time, but I have CPU F1.1 :lol:

OK, just so we are all on the same page, if you have an ID entered (elsewhere) as TG 123 = "Dispatch 1", and you enter ID 123 in another slot, and press FUNC TRUNK, it will display "Dispatch 1", right? Or are you scanning when this is hapening? (a completely different scenario)

BTW, I'm going to start a new thread so we don't 'tie up' this one.

Joe M.
 

Pro-95

Member
Joined
Jun 22, 2004
Messages
798
Location
Washoe Valley Nevada
Pro-2096;

As of today 20-496 is still an invalid sku which means nothing in the stores yet. Searching for PRO-2096 yeilds no results for a 96-like desktop scanner.
 

scannerfreak

Well Known Member
Database Admin
Joined
Jul 3, 2003
Messages
5,193
Location
Indiana
It hasn't even received it's FCC grant yet. That will come before it's in RS's computers.
 

wolverine

Member
Joined
Dec 24, 2002
Messages
342
Location
Cincinnati, Ohio
I would like to see a scanner with a color LCD display, kind of like the ones on cell phones. Maybe GRE can do this with there next scanner.
 

WayneH

Forums Veteran
Super Moderator
Joined
Dec 16, 2000
Messages
7,538
Location
Your master site
rdale said:
No scanner ignores encrypted APCO-P25 transmissions.
Are you speaking strictly P25 Trunking? Mine ignores all encrypted conversations unless a conversation goes from clear to encrypted without dropping the repeater. This is with a 3600 system. Never tested on a P25 Trunked system.

-Wayne
 

NINN27

Member
Joined
Jun 8, 2004
Messages
209
Location
Maryland
to clear **** up...

ID#00016
1A DISPATCH
lets say this is stored in subbank 0-00

lets say i go to subbank 0-01 (BLANK) and enter 00016. i hit enter to store it. i hit enter to acknowledge that i know its a duplicate ID. i hit FUNC TRUCK and it WILL DISPLAY

1A DISPATCH


anybody else confused... try it for yourself... it works (btw... i have 1.1, so it dont matter if you have the new firmware or not)
 

mlevin

Member
Joined
Jan 29, 2003
Messages
2,527
Location
Baltimore, MD
NINN27,

Not to bust your bubble or anything, but we already solved the problem in a different thread. It turned out I was entering the new ID in a higher space then the original tag. In other words. TG 1648 was in space 2. It's tag was A2 DISPATCH. I entered TG 1648 in space 29. When I hit enter I got the original tag. When Voyager was doing this, he was entering the ID in a space lower then where the original tag was, therefro he didn't get any tag when he pressed enter.
 

NINN27

Member
Joined
Jun 8, 2004
Messages
209
Location
Maryland
yeah well it just seemed like everyone was confused... sorry if i came on strong... but glad we cleared it up...
 

mlevin

Member
Joined
Jan 29, 2003
Messages
2,527
Location
Baltimore, MD
No prob, any help is better then no help at all. The more people willing to help out others, the more happier we'll all be. :)
 

INDY72

Monitoring since 1982, using radios since 1991.
Joined
Dec 18, 2002
Messages
14,840
Location
Indianapolis, IN
From what I have been told there are a few technical issues being resolved before type acceptance by the FCC dealing with firmware and things.
 

INDY72

Monitoring since 1982, using radios since 1991.
Joined
Dec 18, 2002
Messages
14,840
Location
Indianapolis, IN
The four different Radio Shacks I have talked to, as well as an electronics specialty shop here that is contracted to both Radio Shack, and Uniden.
 

jbstahr

Member
Joined
Jul 20, 2003
Messages
178
Location
West Columbia, SC
milf said:
From what I have been told there are a few technical issues being resolved before type acceptance by the FCC dealing with firmware and things.


Perhaps a TG bug and a lockout bug? :shock: :lol:
 

Voyager

Member
Joined
Nov 12, 2002
Messages
12,059
jbstahr said:
milf said:
From what I have been told there are a few technical issues being resolved before type acceptance by the FCC dealing with firmware and things.


Perhaps a TG bug and a lockout bug? :shock: :lol:

Heh heh heh. No, it's probably them trying to get field upgradable firmware through the type acceptance. :wink:

Joe M.
 
Status
Not open for further replies.
Top