Pro 96 Weird Alpha Tag

[retroactiv]

I had my new pro 96 for 3 days, it is programmed from the rr site, when I was listening to it on MOT Dig signal and one alpha tag was up, and the people were talking it was right, then I got a second hit, but it was a totally different county that has hit before and there apha tag came up right but this time the alpha tag stayed the same

it should of said 84-disp, but it said 61 disp which is like 2 counties away.

 

[SAR923]

This will happen occasionally. If you have simulcast sites, you can have one agency that ends tranmssion at almost the exact moment another agency begins transmission. The firmware isn't quite fast enoough to pick up the talk group change. If you see this happening a lot, you probably should take your Pro 96 back for exchange but an occasional glitch like this is why we pay $500 for a digital scanner instead of $3000 for digital Motorola portable.

 

[loumaag]

There is another possibiltiy. Make sure you have the proper TG# on the correct TG Alpha Tag.

Let me explain, if you have TG# 144 in slot 0-2 and it says "City Trash PU" and you also have TG# 144 in slot 4-9 and it says "Co. SO Disp"; you will never see "Co. SO Disp" becuase it will always show the first one in the list, which is the 0-2 slot ("City Trash PU").

I understand that you donwloaded the information for the site here, but that doesn't guarantee that all the data is 100% accurate, all data entered in the DB is done by hand so mistakes can happen.

 

[unitcharlie]

Sometimes, when the conditions are right I pick-up TG's from a system 70 miles or so north of me... they are both Motorola Type II systems and if both have the same freq as control channel and the ducting is favorable then I get some off-the-wall TG's..... made me scurry some mornings!

 

[loumaag]

Sometimes, when the conditions are right I pick-up TG's from a system 70 miles or so north of me... they are both Motorola Type II systems and if both have the same freq as control channel and the ducting is favorable then I get some off-the-wall TG's..... made me scurry some mornings!

Wouldn't it be great of one of the features of a scanner was to restrict the systems it would monitor by SysID? I mean you could have a choice of "ANY" or perhaps a list of 3 or 4. If the CC came in and it wasn't on the list, it would get ignored. This would be pleanty helpful on very large systems that end up sharing frequencies in different regions with other licensees. Entergy comes to mind as well as things like the Louisian State System. :wink:

 

[Voyager]

Wouldn't it be great of one of the features of a scanner was to restrict the systems it would monitor by SysID? I mean you could have a choice of "ANY" or perhaps a list of 3 or 4. If the CC came in and it wasn't on the list, it would get ignored. This would be pleanty helpful on very large systems that end up sharing frequencies in different regions with other licensees. Entergy comes to mind as well as things like the Louisian State System. :wink:

As TRSs become even more common, expect even more CCh duplication. As that happens, expect more TRS interference to scanners from 'distant' systems or when travelling into other areas that use the same CCs as a local system. SysID confirmation is going to be more important in the future.

I would make it a list of at least 6-10 SysIDs since there are already systems with 4.

Joe M.

 

[unitcharlie]

GRE, UNIDEN are your people reading this thread?

 

[retroactiv]

I'm reading, but I know what both of the things where that hit, becuase they called out there unit numbers...
one was 61-X unit, then they stopped talking and then 84-x unit was called... might of been a mix up with the system, just never seen something like that.