D
DaveNF2G
Guest
377 is an APD Traffic Division supervisor.
Albany County P25
- Thread starter sav1350
- Start date
- Status
Thanks for information guys. That certainly makes more sense that it’s an APD talkgroip as it fits the numbering of those.
I assume this means the entry in the database for APD Special Ops (13931) is incorrect?
I don’t believe I’ve ever logged traffic on the talkgroup in the database.
I assume this means the entry in the database for APD Special Ops (13931) is incorrect?
I don’t believe I’ve ever logged traffic on the talkgroup in the database.
The database was just revised today to reflect this. This certainly makes more sense given the type of traffic we're hearing.
Ok, so the RR.com database shows 13031 as "Police Special Operations". However, my just-updated Sentinel database for my 536 shows 13931 as the TGID for "Police Special Operations". To make matters more confusing, I just updated Albany County in FreeScan for my 996xt, from RR, and the TGID for "APD Special Ops" is 13031! WTF!
D
DaveNF2G
Guest
They say timing is everything.
Sentinel doesn't update their database constantly. I believe they pull Uniden pulls the full database from Radio Reference once a week or so.
Looks like unit numbers for EMS are changing as part of the county's roll out of the system. ACSO County Paramedic's had changed to using four digit numbers of 6191-6195 from just Medic 1 - Medic 5. Now they are 5591 - 5595. The county ambulances also operated by ACSO which were using their ACSO numbers of 82x (where x was the ambulance number) are now 5580 - 5585.
Now that Guilderland is starting to switch over, Guilderland EMS has taken over the 56 number that Voorheesville had been using before they merged with Delmar-Bethlehem. They are now using the IDs of 5691 - 5697. Same goes for Western Turnpike RS and Altamont RS. They are using their county IDs on Guilderland channels as well.
Certainly a lot of changes happening. Interested to see what else may change. Definitely makes sense now that its even easier for everyone else to talk to each other on a shared system to have consistent numbering. Although, many of these agencies could talk between each other before without confusion.
Now that Guilderland is starting to switch over, Guilderland EMS has taken over the 56 number that Voorheesville had been using before they merged with Delmar-Bethlehem. They are now using the IDs of 5691 - 5697. Same goes for Western Turnpike RS and Altamont RS. They are using their county IDs on Guilderland channels as well.
Certainly a lot of changes happening. Interested to see what else may change. Definitely makes sense now that its even easier for everyone else to talk to each other on a shared system to have consistent numbering. Although, many of these agencies could talk between each other before without confusion.
D
DaveNF2G
Guest
Yes, it's confusing at first on the local talkgroups/frequencies, but in the long run having everyone compliant with the county numbering system (which has existed for a long time) will make things much easier.
Thanks everyone for all the updates. And yes, having the numbering consolidated makes sense.
I have been logging using ProScan for the past 24 hours. I've noted that Albany County Law 1 and Fire 1 have appeared on both the Metro Cell and County Cell at various times. Is this just a ProScan fluke, or have others noticed this as well?
What is the issue? Your scanner can only pick up on activity from one site at a time, so as it's scanning between both cells it's going to randomly stop on whichever talkgroup is active on whichever cell. It may happen to be decoding the Metro Cell with Law 1 active one minute, then the County Cell with Law 1 active the next minute. If you scan both sites then it'll be the luck of the draw.
This doesn't have any detrimental effect. If I hadn't been logging transmissions, I'd not have noticed this. While the site in use doesn't matter to my 536HP, it will matter when I program my Unication G5 currently en-route. At least as far as I understand.
The trouble is that by only using the 536HP/ProScan as a reference point, you have no way of knowing if those talkgroups were active on both sites at the same time. The scanner can only "see and hear" one site at a time. It could very well be that while the scanner is stopped on Law 1 or Fire 1 on the County Cell, those talkgroups are also active on the Metro Cell.
The only way you can know for certain is to monitor both sites at the same time. Scan only the Metro Cell with the 536HP and only the County Cell with the G5, for example, and compare the activity in real time.
My hunch is that significant talkgroups such as Law 1 and Fire 1 would probably be carried on both cells full-time. However that's just speculation, and it's important to note that the default behavior of an ASTRO 25 system is to only carry a talkgroup's traffic on a particular site when a subscriber radio is actually affiliated with that talkgroup.
The only way you can know for certain is to monitor both sites at the same time. Scan only the Metro Cell with the 536HP and only the County Cell with the G5, for example, and compare the activity in real time.
My hunch is that significant talkgroups such as Law 1 and Fire 1 would probably be carried on both cells full-time. However that's just speculation, and it's important to note that the default behavior of an ASTRO 25 system is to only carry a talkgroup's traffic on a particular site when a subscriber radio is actually affiliated with that talkgroup.
I can’t say it’s 100% of the time, but those 2 TG appear to be full time on both cells...or at least very frequently both.
I would setup the G5 with both cells (on different knob positions) and put all the TGs of interest in both. So you can easily switch between cells.
I would setup the G5 with both cells (on different knob positions) and put all the TGs of interest in both. So you can easily switch between cells.
I suspect programming the G5 will require some experimentation at first. Logging all system transmissions allows me to determine the most active frequencies and what sites they associate with. This will be important considering I need to separate the sites into separate knob positions.
The trouble with relying on ProScan logging is that it's a crapshoot as to which site the 536HP is going to stop on for any given transmission. You'd really be better off logging the Metro Site for a week, then switch to the County Site for a week. You can then get a pretty good sense of how active each talkgroup is on either site.
That, or buy some RTL dongles and log both sites simultaneously with Unitrunker or DSD+. That way you can truly see which talkgroups are carried on both sites simultaneously.
That, or buy some RTL dongles and log both sites simultaneously with Unitrunker or DSD+. That way you can truly see which talkgroups are carried on both sites simultaneously.
My approach is to run two simultaneous instances of ProScan. One connected to the 536 and held on the Metro Cell site, while the other is connected to my 996xt only scanning the County Cell. We'll let that run for the next day or so and see what happens.
Sorry for the confusion. I did only have the 536 running. Then I got smart!
I've already confirmed that Alb. County Law 1, at least, is being transmitted on both the Metro and County Cells simultaneously. I'll have a better picture by tomorrow night.I can confirm this normal operation. County Fire 1 and Country Law 1 are always on the Metro Cell and County Cell at the same time. I don't know for sure but i would assume they are probably on the Cohoes Cell as well. I can't receive the Cohoes Cell from my location.
- Status
