Not sure when this change happened, but all of the end of last week I noticed that Raritan was now being dispatched full-time by county, and that they are using the identifier of '16' (that makes perfect sense, as it's their municipality code).

Also, Peapack & Gladstone PD have started ID'ing as '15' cars on PD NORTH. Has there been any other changes that I missed?

EDIT - Also, Branchburg is now on the TRS on PD REGION 5. Trying to figure out what TGID that is right now...

As of this morning, all the police departments being dispatched by the County are using the last two digits of the NJ Municipality number. Only exception at this time is when South Bound Brook is in Rocky Hill, they were told to continue to use 'Rocky' until changes are made in the computer system. Here's the municipality number list for the entire county:

Yeah, it's going to take awhile to get used to this change. As long as I can remember, South Bound Brook was always 'Sierra' cars. There's gonna be a lot of old habits to break with this change. I'm guessing that Raritan didn't want to be known as 'Papa' cars, and Somerville (to convert over this year) didn't want to be known as a 'Romeo' cars.

I still say North Plainfield would of been the worst if they were to transition over... haha

I've also noticed the control channel showing up on other frequencies full-time as well (used to be almost always on 501.9125, and then 502.6875 rarely).

Doug Rue gave a talk at our last RVRC meeting at the academy, and a tour of 99M. He mentioned that they are also planing a serious second-wave of console deployments as part of the P25 upgrade, so that leads me to believe that quite a few more towns are going to come over this year...

Also, 11760 (2DF): Montgomery DPW? Not in the database, and it's the only municipality with a "Main Blvd" as was being discussed on the TG. I locked it out (because they were annoying me), but perhaps someone can confirm and then update the database.

The TGID 727 is currently simulcasting transmissions from Raritan PD's analog talkgroup. I'm going to stay on top of this for the rest of the evening (so much for getting some Battlefield 3 play time in!)...

The TGID tables should be 1-to-1 as this progresses. (i.e. look at the HEX value on the current system and it should be the same on the new system). I already have my feed scanning the new P25S system (and will likely leave it up full-time as progress continues) in ID SEARCH mode.

As Scott said, if you have P25-Auto as an option then select it. You'll have to program it as a separate system even if you don't want to -- all scanners require different custom tables for the two systems, if not a wholly different system selected during the programming process.

These should work until/unless out-of-band frequencies are added (<470 or >512) or until the system changes its tables. I'm only an amateur here but the 502 table's existence surprises me since the 500 table can theoretically handle up to about 550MHz at the specified step. (P25 tables can handle many more channels than Motorola tables.)

If anyone has any trouble inputting the above tables, first make sure that your scanner can trunktrack P25 trunked systems. Some old models can receive P25 audio on conventional or Motorola trunked but cannot track P25 trunked systems. Second, make sure your scanner has the latest firmware.