wr7agt
Member
Well, they finally are attempting to use the Lewis and Clark County system here in Helena. I am playing with the Pro-96 again and have discovered a difficulty.
First, I am monitoring a single tower site that has 3 frequencies, VHF. Using Pro96com, I have verified the frequencies and the ID tables assigned to each. They are, 3, 9, and 11. The PC96 software says that the base freq is 136.000, 136.000, and 144.110 respectively. I did the math 3 times and have come up with the Hi, Lo, and offset numbers. I put all three into the trunking tables listing in win96 programming software, loaded to the scanner. They are using 12.5Khz according to pro96com tower data.
Here is the problem. The CC is on 154.340, the ACC is 161.975, and the last is 159.000. When putting the Pro 96 on the one bank with just these three channels and starting scan, the radio isn't correctly following the trunking. When someone talks on 159.000, while in scan, the 96 display shows that it is trying to listen to 164.475 (not even programmed, nor is it even licensed, much less at the site), displays the proper talkgroup (29), but does not actually open up and allow me to hear anything. If I take the scanner out of scan and go to 159.000, everybody is there and I hear normally. 159.000 seems to be the default Voice channel as it is the one almost always used. Now, when back in scan, if the site selects the 161.975 freq for a voice channel, the scanner locks up fine and displays all the info. It seems like there is a bug in the ID tables or something else goofy.
Any ideas or heard anything about this?
First, I am monitoring a single tower site that has 3 frequencies, VHF. Using Pro96com, I have verified the frequencies and the ID tables assigned to each. They are, 3, 9, and 11. The PC96 software says that the base freq is 136.000, 136.000, and 144.110 respectively. I did the math 3 times and have come up with the Hi, Lo, and offset numbers. I put all three into the trunking tables listing in win96 programming software, loaded to the scanner. They are using 12.5Khz according to pro96com tower data.
Here is the problem. The CC is on 154.340, the ACC is 161.975, and the last is 159.000. When putting the Pro 96 on the one bank with just these three channels and starting scan, the radio isn't correctly following the trunking. When someone talks on 159.000, while in scan, the 96 display shows that it is trying to listen to 164.475 (not even programmed, nor is it even licensed, much less at the site), displays the proper talkgroup (29), but does not actually open up and allow me to hear anything. If I take the scanner out of scan and go to 159.000, everybody is there and I hear normally. 159.000 seems to be the default Voice channel as it is the one almost always used. Now, when back in scan, if the site selects the 161.975 freq for a voice channel, the scanner locks up fine and displays all the info. It seems like there is a bug in the ID tables or something else goofy.
Any ideas or heard anything about this?
