Br330t random tgs

[dave3825]

I am not sure why its doing it, but I am listening to the Suffolk CountyTrs and I have the whole system programmed into the radio. I have it in id search mode with everything I don't want to hear turned off.

I have all the freqs for the system entered correctly.

I have the correct rebanded info entered

The issue, is if the scanner is not set to control channel only, it will display random td ids and they are one sided transmissions.

I have a video and towards the end, you hear the female dispatcher come up on 2 different tgs and its one sided.

Any suggestions?

Scan - YouTube

 

[ka3jjz]

The one thing you didn't mention is: did you update your firmware? The 330T out of the box can't handle rebanding - here's the update page

BR330TFirmwareUpdate < UnidenMan4 < TWiki

Mike

 

[UPMan]

I'd recommend you set Status Bit to Ignore (you are seeing some TGID's with their status flags set...all normal TGIDs are divisible by 16).

All the channels that come up seem to be undocumented, but it is difficult to tell with the status bits being counted.

It is not exhibiting incorrect band plan behavior, and you do indicate that you've enter the correct band plan, so that isn't going to be a factor.

In ID search mode, with all known channels disabled, you are going to get random, primarily one-sided broadcasts on unknown talk groups. That appears to be consistent with the video.

 

[dave3825]

Yes I did it the day it was available.

 

[dave3825]

Paul, I have it set to ignore. Are you saying that the scanner will create random tgs when in search mode? That does not seem right. I'd search from my understanding is to find a tg that's not programmed in and is able to divide by 16.

 

[UPMan]

The scanner does not "create tgs." It watches the control channel for channel grants and channel updates and compares those that come across with those you've stored in the scanner. Since you've stored and locked out all known channels for the system, that means it is only going to stop on unknown channels, which could be anything (i.e. random). In your video, it stopped on some odd-numbered talk groups, which is not possible on a Motorola Type II system when Status Bits is set to ignore.

 

[dave3825]

In your video, it stopped on some odd-numbered talk groups, which is not possible on a Motorola Type II system when Status Bits is set to ignore.

You say it is not possible with status bit set to ignore. Below is a log from last night. I left only Command Band active and it had 150 hits. Ok, then all these other random tgs were logged.. Most of them only had I transmission/hit. The talk groups are right after the frequencies.

And here is a new video showing the status bits set to ignore, and it displaying random talk groups.




INFO SYSTEM FREQ ID SUB COUNT NAME MODE TIME DATE
LOG S C P D/ 853.8000 56496 1 NFM 7:16:01 11/7/2014
LOG S C P D/ 853.6750 16560 2 NFM 7:15:43 11/7/2014
LOG S C P D/S C P D 853.8250 60848 150 Command NFM 7:15:09 11/7/2014
LOG S C P D/ 853.5250 52848 2 NFM 7:14:46 11/7/2014
LOG S C P D/ 853.6750 30496 1 NFM 7:14:36 11/7/2014
LOG S C P D/ 852.6750 54640 5 NFM 7:12:50 11/7/2014
LOG S C P D/ 852.7375 15056 1 NFM 7:12:26 11/7/2014
LOG S C P D/ 853.6750 7968 1 NFM 7:07:38 11/7/2014
LOG S C P D/ 853.6750 49568 1 NFM 7:06:40 11/7/2014
LOG S C P D/ 852.9250 23408 1 NFM 7:06:22 11/7/2014
LOG S C P D/ 853.1250 144 2 NFM 7:06:12 11/7/2014
LOG S C P D/ 853.8250 39024 1 NFM 7:05:32 11/7/2014
LOG S C P D/ 852.6750 11120 3 NFM 7:04:58 11/7/2014
LOG S C P D/ 852.6750 2640 1 NFM 7:04:06 11/7/2014
LOG S C P D/ 853.2500 51344 6 NFM 7:03:01 11/7/2014
LOG S C P D/ 851.1625 50800 2 NFM 7:02:45 11/7/2014
LOG S C P D/ 852.8500 2320 2 NFM 7:02:08 11/7/2014
LOG S C P D/ 853.3750 57744 5 NFM 7:01:43 11/7/2014
LOG S C P D/ 852.6750 11088 1 NFM 6:50:56 11/7/2014
LOG S C P D/ 852.7375 24624 1 NFM 6:49:40 11/7/2014
LOG S C P D/ 852.9250 1200 2 NFM 6:45:08 11/7/2014
LOG S C P D/ 853.6750 29712 1 NFM 6:43:30 11/7/2014
LOG S C P D/ 853.6750 2352 2 NFM 6:42:18 11/7/2014
LOG S C P D/ 852.6750 33072 1 NFM 6:38:58 11/7/2014
LOG S C P D/ 853.1250 16656 2 NFM 6:38:14 11/7/2014
LOG S C P D/ 853.5250 33040 1 NFM 6:37:17 11/7/2014
LOG S C P D/ 852.6750 10800 2 NFM 6:32:42 11/7/2014
LOG S C P D/ 851.2375 24208 33 NFM 6:31:58 11/7/2014
LOG S C P D/ 852.9250 49584 4 NFM 6:29:06 11/7/2014
LOG S C P D/ 853.3750 61168 2 NFM 6:28:51 11/7/2014
LOG S C P D/ 852.6750 52880 2 NFM 6:27:08 11/7/2014
LOG S C P D/ 852.8500 52336 4 NFM 6:27:03 11/7/2014
LOG S C P D/ 852.4250 54528 1 NFM 6:25:00 11/7/2014
LOG S C P D/ 852.6750 3344 4 NFM 6:17:20 11/7/2014
LOG S C P D/ 853.2500 58800 2 NFM 6:16:59 11/7/2014
LOG S C P D/ 853.8000 53424 1 NFM 6:15:40 11/7/2014
LOG S C P D/ 852.4250 50480 1 NFM 6:14:30 11/7/2014
LOG S C P D/ 853.8250 53232 2 NFM 6:12:13 11/7/2014
LOG S C P D/ 853.5250 288 2 NFM 6:08:42 11/7/2014
LOG S C P D/ 851.1625 49744 1 NFM 6:07:34 11/7/2014
LOG S C P D/ 852.6750 51248 2 NFM 6:00:40 11/7/2014
LOG S C P D/ 852.9250 8560 1 NFM 5:58:17 11/7/2014
LOG S C P D/ 853.6750 19376 1 NFM 5:57:48 11/7/2014
LOG S C P D/ 852.7375 39104 1 NFM 5:53:20 11/7/2014
LOG S C P D/ 853.8250 3408 1 NFM 5:51:30 11/7/2014
LOG S C P D/ 852.7375 6464 1 NFM 5:51:25 11/7/2014
LOG S C P D/ 852.6750 3680 1 NFM 5:46:32 11/7/2014
LOG S C P D/ 853.3750 33840 1 NFM 5:38:11 11/7/2014
LOG S C P D/ 852.7375 16400 1 NFM 5:35:22 11/7/2014
LOG S C P D/ 852.6750 16640 1 NFM 5:26:50 11/7/2014
LOG S C P D/ 852.7375 2832 1 NFM 5:26:10 11/7/2014
LOG S C P D/ 851.1625 46192 1 NFM 5:22:42 11/7/2014
LOG S C P D/ 852.8500 59120 2 NFM 5:15:30 11/7/2014
LOG S C P D/ 852.9250 2432 1 NFM 5:13:44 11/7/2014
LOG S C P D/ 853.8250 60336 1 NFM 5:13:22 11/7/2014
LOG S C P D/ 853.3750 55920 1 NFM 5:12:58 11/7/2014
LOG S C P D/ 852.6750 1760 1 NFM 5:09:04 11/7/2014
LOG S C P D/ 853.6750 13376 1 NFM 5:06:50 11/7/2014
LOG S C P D/ 853.2500 19280 1 NFM 4:58:23 11/7/2014
LOG S C P D/ 852.6750 59824 2 NFM 4:54:08 11/7/2014
LOG S C P D/ 853.3750 53664 1 NFM 4:45:26 11/7/2014
LOG S C P D/ 853.6750 40688 1 NFM 4:40:13 11/7/2014
LOG S C P D/ 853.6750 27648 1 NFM 4:33:40 11/7/2014
LOG S C P D/ 852.4250 54128 1 NFM 4:31:02 11/7/2014
LOG S C P D/ 853.3750 55664 1 NFM 4:29:14 11/7/2014
LOG S C P D/ 852.7375 16816 4 NFM 4:26:51 11/7/2014
LOG S C P D/ 852.7375 49712 2 NFM 4:23:03 11/7/2014
LOG S C P D/ 852.7375 43520 1 NFM 4:21:05 11/7/2014
LOG S C P D/ 853.1250 36080 1 NFM 4:19:41 11/7/2014
LOG S C P D/ 853.8000 57968 4 NFM 4:19:30 11/7/2014
LOG S C P D/ 853.6750 1472 3 NFM 4:15:13 11/7/2014
LOG S C P D/ 852.8500 5584 1 NFM 4:08:56 11/7/2014
LOG S C P D/ 852.6750 11328 1 NFM 4:08:03 11/7/2014
LOG S C P D/ 852.6750 13776 1 NFM 4:05:08 11/7/2014
LOG S C P D/ 852.8500 20208 1 NFM 4:02:08 11/7/2014
LOG S C P D/ 853.3750 22960 1 NFM 3:57:16 11/7/2014
LOG S C P D/ 853.8000 44784 1 NFM 3:49:15 11/7/2014
LOG S C P D/ 852.6750 49760 1 NFM 3:40:53 11/7/2014
LOG S C P D/ 853.6750 55472 2 NFM 3:38:07 11/7/2014
LOG S C P D/ 853.6750 49808 2 NFM 3:37:16 11/7/2014
LOG S C P D/ 852.7375 416 2 NFM 3:35:56 11/7/2014
LOG S C P D/ 851.1625 2256 1 NFM 3:34:49 11/7/2014
LOG S C P D/ 852.8500 3440 1 NFM 3:32:24 11/7/2014
LOG S C P D/ 853.5250 33200 1 NFM 3:30:22 11/7/2014
LOG S C P D/ 851.1625 15472 1 NFM 3:29:08 11/7/2014
LOG S C P D/ 853.6750 11040 2 NFM 3:28:51 11/7/2014
LOG S C P D/ 852.7375 34176 1 NFM 3:27:49 11/7/2014
LOG S C P D/ 852.8500 34192 1 NFM 3:27:34 11/7/2014
LOG S C P D/ 852.7375 50288 1 NFM 3:22:05 11/7/2014
LOG S C P D/ 851.1625 51440 3 NFM 3:20:26 11/7/2014
LOG S C P D/ 852.9250 52944 1 NFM 3:13:10 11/7/2014
LOG S C P D/ 852.7375 18928 1 NFM 3:08:43 11/7/2014

 

[UPMan]

Every one of those TGs are divisible by 16, so I agree that Status Bits are now likely set to Ignore.

The scanner is now operating exactly as you have set it to operate. Any time a channel on the system becomes active that you have not stored into the scanner and locked out, the scanner stops on the transmission and you hear the traffic. (But it looks like you didn't lock out the channel named "COMMAND.")

 

[dave3825]

Every one of those TGs are divisible by 16, so I agree that Status Bits are now likely set to Ignore.

The scanner is now operating exactly as you have set it to operate. Any time a channel on the system becomes active that you have not stored into the scanner and locked out, the scanner stops on the transmission and you hear the traffic. (But it looks like you didn't lock out the channel named "COMMAND.")

Paul, status bits have been set to ignore for a long time. I don't think your understanding whats going on.

The scanner , with most tgs locked out, will stop on these random tgs, and there will be voice traffic. Then no response and it resumes scanning. One sided voice. I know my system, and know Suffolk County. I will hear a precinct come up on an unknown tg , a precinct thats locked out, and hear dispatcher give out a job. There is never any response on these random tgs. Then another unknown tg will come up, and its like the middle of a conversation.

I am fully aware how the id search works.I have been using it for a long time to id new channels. And it will id new tgs when there legit. However, these random unknowns come up with one sided voice.I have hit hold on a bunch and never hear 2 way traffic, just one sided...

Anyone who knows suffolks system, knows these random tgs are not legit.

And on top of that, I have every tg on this system stored and there were 155 unknown tgs that were logged from 12 30pm to 7 am this morning.

 

[UPMan]

No idea. I do not recall ever seeing anything like this reported, before.

 

[phask]

Could it have anything due to receiving those on the voice channels and not the control channel?

Just a wild guess. Is there a reason you have the voice channels programmed?

 

[dave3825]

It does make a difference. It does not do this if set to control channel only.

That's how I know there is an issue with this scanner.


I always program voice channels in the event the agency should ever change something..

I will try this on another MOT type 2 system.


Also, at one time i had only the cc and alternate cc programed in and it still displayed the voice channels.

 

[jonwienke]

Here's the short version: you're programming the scanner in a non-standard way, and then complaining that it behaves in a non-standard way.

There's no reason not to use control channel only, as any system changes are broadcast on the control channel.

 

[UPMan]

If it works correctly when set to CC only, I'd leave it at that setting. I don't anticipate a firmware update to this model and, even if we did, what we would do is remove the option (and it would be CC only all the time, just like all our current models).

 

[dave3825]

Ok, so I took out the voice channels, status bit is still set to ignore and its set to control channel only.

The scanner is still doing it.

first last system count freqtgid modulation site type signal
11/11/2014 1:04 11/11/2014 1:04 S C P D 1 57984 NFM M82C 0
11/11/2014 1:10 11/11/2014 9:41 S C P D 25 62240 NFM M82C 0
11/11/2014 5:33 11/11/2014 5:33 S C P D 1 65296 NFM M82C 0
11/11/2014 9:30 11/11/2014 9:30 S C P D 1 51024 NFM M82C 0
11/11/2014 9:33 11/11/2014 9:33 S C P D 1 52496 NFM M82C 0
11/11/2014 9:34 11/11/2014 9:34 S C P D 1 24048 NFM M82C 4

 

[dave3825]

So after all the suggestions and resetting the scanner and reprogramming the system, its safe to say this bug sucks...