If I were setting up a new MOT system, I COULD start assigning TGs at 16, then count in multiples of 16, ie: 16, 32, 48, 64, 80, 96, 112, 128. These are all valid TG #'s on a Motorola system.

On the Utah system they started at 32, then counted in multiples of 32, ie: 32, 64, 96, 128. All these #'s are still multiples of 16

__and__ 32. All are valid #'s, but there are only half as many. If Utah runs out, maybe they will start to use every other /16 that they had previously skipped. At least the #'s within each agency could remain grouped together if desired.

Maybe your system ends up with the decimal TG coming out with an even number. The system

I just looked at the numbers come out with a xxx.5 when divided by 32. I know the system HEX

numbers are correct. So now explain to me why the xxx.5 number comes up and not an even

number as you claim it should.

Jim

If ALL the TGs on the above system are xxx.5 when divided by 32, then they must have started with 16 and then counted by 32, ie: 16, 48, 80, 112. If only SOME of them are xxx.5 and the others are xxx.0, they are using all the multiples of 16 (although surely they are not all assigned and in use yet). Any of these strategies would still result in valid MOT #'s.

It seems like I read some Motorola literature a while back that indicated the 5th binary bit on a type II system could be used alternatively as a status indicator, along with bits 1-4, or it could be used as part of the TGID along with bits 6-16 . If this is true it would sure explain a lot.

--bc