Manually entering TGs on the PRO-96 (Continued from 2096)

Status
Not open for further replies.

Voyager

Member
Joined
Nov 12, 2002
Messages
12,058
Reaction score
68
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.

P.S. Just for reference, here is the direct entry method:
PGM TRUNK <TG#> ENTER FUNC TRUNK

You WILL have to hit ENTER a second time if the TG is already stored elsewhere. You will also have to (only once) select your scratchpad slot after hitting PGM TRUNK. IF you make that slot x-4-29, you WILL retain the text tag of the original entry when holding that ID. I always used slot x-1-00, but will not use x-4-29 due to this bug/feature.
 

kg4icg

Crazy Trucking Mechanic
Joined
Nov 28, 2003
Messages
436
Reaction score
37
Location
Woodbridge, Va
On the Pro96 if you try to enter the same tg in the same bank more then once it's going to tell you that you are enterring it as duplicate and show you where it already exists if it's in the same bank of 150 tg storage area, it's in an entirely different tg area no problem but the same bank it will let you know, wither it be manual entry or thru scan.

R Collins

"cry havoc, and let loose the dogs of war" or
get your wife mad at you buy buying 1 electronic thing to much.
:twisted:
 

mlevin

Member
Joined
Jan 29, 2003
Messages
2,527
Reaction score
33
Location
Baltimore, MD
Re: Manually entering TGs on the PRO-96 (Continued from 2096

Voyager said:
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.

THAT'S IT!!!!! YOU GOT IT :lol:
 

scanfan03

Member
Joined
Jun 2, 2003
Messages
1,714
Reaction score
11
Location
Houston, Texas
Say I have a TG already entered in a slot, TG ID 5520. I want to hold that ID. I could press Prog Trunk 5 5 2 0 Enter Enter Func Trunk. That is 10 keystroks. When I could press Prog Trunk Trunk Trunk (Depending on what subbank it's in) Up Up (Depending on what slot) Func Trunk. That is only 8 keystrokes. So why remember the TG ID When it would be quicker to do it with only 8 keystrokes?
 

Voyager

Member
Joined
Nov 12, 2002
Messages
12,058
Reaction score
68
scanfan03 said:
Say I have a TG already entered in a slot, TG ID 5520. I want to hold that ID. I could press Prog Trunk 5 5 2 0 Enter Enter Func Trunk. That is 10 keystroks. When I could press Prog Trunk Trunk Trunk (Depending on what subbank it's in) Up Up (Depending on what slot) Func Trunk. That is only 8 keystrokes. So why remember the TG ID When it would be quicker to do it with only 8 keystrokes?

Yes - depending what slot. You have to search for each ID. You may be entering up to twenty-some keystrokes. Even if you know where it is, I don't agree it is faster than the direct method. Whn you average it out, considering that there is an AVERAGE of 8 keystrokes just for the bank, plus the bank keystrokes (1-4), plus the four to get there and hold (PGM TRUNK and FUNC TRUNK), the direct method is much faster.

But, you have to remember (or read) how this thread started: Wanting direct entry like the Uniden. Direct entry on the 96 is only two keystrokes more than the Uniden.

I'm having trouble duplicating Mo's actions. My unit (also F1.1) keeps showing the ID as "ID# XXXXX", not the ID that is in another memory slot.

Joe M.
 

Voyager

Member
Joined
Nov 12, 2002
Messages
12,058
Reaction score
68
Re: Manually entering TGs on the PRO-96 (Continued from 2096

mlevin said:
Voyager said:
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)

THAT'S IT!!!!! YOU GOT IT :lol:

I got it? There are two scenarios I mentioned. :?

Which one is 'it'?

I have an additional question: When it's displaying ID HOLD MODE, does it show the ID# XXXXX tag or the tag from the 'original' entry?

AH HAH! I think I got it :!:

If your scratchpad ID is HIGHER than the other TG memory slot, it WILL show the ID of the original entry. I always used slot 1-0-00, so it was lower than anything. BUT, if you use slot 1-4-29 as your scratchpad, it WILL show the text entry of the main TG entry. So, it will choose the text tag of the lowest memory slot no matter what you have in the higher slots.
BTW, when you hit PGM-TRUNK, it will default to the last chosen slot, so you can use 1-4-29 as the scratchpad (direct entry) slot.

Joe M.
 

loumaag

Silent Key - Aug 2014
Joined
Oct 20, 2002
Messages
12,935
Reaction score
11
Location
Katy, TX
scanfan03 said:
Say I have a TG already entered in a slot, TG ID 5520. I want to hold that ID. I could press Prog Trunk 5 5 2 0 Enter Enter Func Trunk. That is 10 keystroks. When I could press Prog Trunk Trunk Trunk (Depending on what subbank it's in) Up Up (Depending on what slot) Func Trunk. That is only 8 keystrokes. So why remember the TG ID When it would be quicker to do it with only 8 keystrokes?
I am obviously coming into this late as I was not monitoring the other thread, but taking what you said, you are comparing apples and oragnes.

Your 10 keystroke example:
If you press <PRG><TRUNK><5><5><2><0><ENTER> the Pro-96 will report you already have that ID in memory, pressing <ENTER> one more time will write it to the memory slot where you are, thus possibly overwriting something you didn't want to lose.

Your 8 keystroke example:
If you <PROG><TRUNK><TRUNK><TRUNK> at this point you are two (2) ID Banks away from whatever the last bank you had open (which may or may not be where you want); then pressing <up arrow><up arrow> will have you two (2) slots above the last slot number you were looking at. This is strange. Suppose you were starting from scratch (ID Bank 0, Slot 0) and what you wanted was on Bank 3, Slot 20... Unless my counting is wrong, that is 27 keystrokes to get there and hold.

Bottom line, the first method will overwrite something you certainly don't want overwritten, the second method is okay (but may wear out your finger); the best method is to wait until you hear traffic on the ID you want to hold on and press <PAUSE>, that is one keystroke. :D
 

loumaag

Silent Key - Aug 2014
Joined
Oct 20, 2002
Messages
12,935
Reaction score
11
Location
Katy, TX
Voyager said:
I'm having trouble duplicating Mo's actions. My unit (also F1.1) keeps showing the ID as "ID# XXXXX", not the ID that is in another memory slot.
That is because you have forced it into a new slot with no text tag.
 

Voyager

Member
Joined
Nov 12, 2002
Messages
12,058
Reaction score
68
loumaag said:
scanfan03 said:
Say I have a TG already entered in a slot, TG ID 5520. I want to hold that ID. I could press Prog Trunk 5 5 2 0 Enter Enter Func Trunk. That is 10 keystroks. When I could press Prog Trunk Trunk Trunk (Depending on what subbank it's in) Up Up (Depending on what slot) Func Trunk. That is only 8 keystrokes. So why remember the TG ID When it would be quicker to do it with only 8 keystrokes?
I am obviously coming into this late as I was not monitoring the other thread, but taking what you said, you are comparing apples and oragnes.

Your 10 keystroke example:
If you press <PRG><TRUNK><5><5><2><0><ENTER> the Pro-96 will report you already have that ID in memory, pressing <ENTER> one more time will write it to the memory slot where you are, thus possibly overwriting something you didn't want to lose.

Bottom line, the first method will overwrite something you certainly don't want overwritten,

You're missing a key issue. You are programming your scratchpad slot. Once you've done that, you don't care that it will overwrite the previous scratchpad entry. You can't monitor more than one TG at the same time. Again, this is a way to get effective direct entry with the PRO-96. Waiting does not accomplish that at all.

Joe M.
 

Voyager

Member
Joined
Nov 12, 2002
Messages
12,058
Reaction score
68
loumaag said:
Voyager said:
I'm having trouble duplicating Mo's actions. My unit (also F1.1) keeps showing the ID as "ID# XXXXX", not the ID that is in another memory slot.
That is because you have forced it into a new slot with no text tag.

Nope - my next post (past the one you quoted) explains it.

I am now duplicating what Mo is seeing.

Joe M.
 

scanfan03

Member
Joined
Jun 2, 2003
Messages
1,714
Reaction score
11
Location
Houston, Texas
loumaag said:
scanfan03 said:
Say I have a TG already entered in a slot, TG ID 5520. I want to hold that ID. I could press Prog Trunk 5 5 2 0 Enter Enter Func Trunk. That is 10 keystroks. When I could press Prog Trunk Trunk Trunk (Depending on what subbank it's in) Up Up (Depending on what slot) Func Trunk. That is only 8 keystrokes. So why remember the TG ID When it would be quicker to do it with only 8 keystrokes?
I am obviously coming into this late as I was not monitoring the other thread, but taking what you said, you are comparing apples and oragnes.

Your 10 keystroke example:
If you press <PRG><TRUNK><5><5><2><0><ENTER> the Pro-96 will report you already have that ID in memory, pressing <ENTER> one more time will write it to the memory slot where you are, thus possibly overwriting something you didn't want to lose.

Your 8 keystroke example:
If you <PROG><TRUNK><TRUNK><TRUNK> at this point you are two (2) ID Banks away from whatever the last bank you had open (which may or may not be where you want); then pressing <up arrow><up arrow> will have you two (2) slots above the last slot number you were looking at. This is strange. Suppose you were starting from scratch (ID Bank 0, Slot 0) and what you wanted was on Bank 3, Slot 20... Unless my counting is wrong, that is 27 keystrokes to get there and hold.

Bottom line, the first method will overwrite something you certainly don't want overwritten, the second method is okay (but may wear out your finger); the best method is to wait until you hear traffic on the ID you want to hold on and press <PAUSE>, that is one keystroke. :D

How many IDs are there per ID bank? Are there 30?
 

loumaag

Silent Key - Aug 2014
Joined
Oct 20, 2002
Messages
12,935
Reaction score
11
Location
Katy, TX
Voyager said:
You're missing a key issue. You are programming your scratchpad slot. ...
Ahh! A key bit of information which did not float over from the other thread. Okay, yes that will work.

But in regard to...
Voyager (other post) said:
I am now duplicating what Mo is seeing.
Unless I misunderstand this also, you sometimes see the ID number and sometime you see the previously programmed Alpha Tag for the same ID. I believe this is a positional thing, if your "scratch pad" slot is higher than the original, then the original text tag will display, so I guess if you make 4-29 your scratch pad slot, you would always see the previous alpha tag.
 

Voyager

Member
Joined
Nov 12, 2002
Messages
12,058
Reaction score
68
Voyager said:
I'll have to try scanning DOWN to see if this changes.

NO - it ALWAYS displays the LOWEST TG slot text tag - whether scanning UP or DOWN. So, Mo and I taught each other a new trick. Thanks back, Mo! :D

Joe M.
 

Voyager

Member
Joined
Nov 12, 2002
Messages
12,058
Reaction score
68
loumaag said:
Unless I misunderstand this also, you sometimes see the ID number and sometime you see the previously programmed Alpha Tag for the same ID. I believe this is a positional thing, if your "scratch pad" slot is higher than the original, then the original text tag will display, so I guess if you make 4-29 your scratch pad slot, you would always see the previous alpha tag.

My previous reply was overwritten. It will always display the text tag of the lowest slot, so if your scratchpad slot is lower than your original text tag, you will see the scratchpad slow tag. If your scratchpad is higher, it will display the original entry text tag.

So, if you use 4-29 as your scratchpad, it will always show the original text tag as long as there is a previous entry. If not, it will show the scratchpad text tag.

Joe M.
 

mlevin

Member
Joined
Jan 29, 2003
Messages
2,527
Reaction score
33
Location
Baltimore, MD
Voyager, I was refering to the first scenario. And yes, the TG ID was higher then the original, and it did show the tag.

What I was talking about on the Uniden wasn't direct entry. I can navigate to an ID with no more then 3-4 key strokes. (Keep in mind the ID has already been stored.) If I'm scanning I hit MAN to access the ID list. I hit the list number i.e. 2, and the space number i.e. 1, then I hit MAN again, and it takes me directly to list 2 space number 1. I'm sure anyone who ever had a Uniden knows this and this is what I refereing to when I was stating how nice that would be if you where driving. Of course on the 96 and 2096 since the list has more then ten spaces the whole thing would take at the most 5 keystrokes, and it would be harder to memorize lists of 30 as opposed to lists of 10. I still want lists of 16 like on the moto radios, and a selecter knob to switch the zones/numbers. That would make life so much easier.
 

Voyager

Member
Joined
Nov 12, 2002
Messages
12,058
Reaction score
68
mlevin said:
What I was talking about on the Uniden wasn't direct entry. I can navigate to an ID with no more then 3-4 key strokes. (Keep in mind the ID has already been stored.) If I'm scanning I hit MAN to access the ID list. I hit the list number i.e. 2, and the space number i.e. 1, then I hit MAN again, and it takes me directly to list 2 space number 1.

You can do that even if you're on a different bank when you hit manual? I would think that MAN LIST CH MAN would take you to a frequency stored in Bank 2, channel 1, not to a TG list.

As I said before, I agree with you that it would be nice to see an easier way to do all that in the 2096.

Joe M.
 
Status
Not open for further replies.
Top