KF4JZY
Member
I have a 396XT that is acting up so much I'm starting to think it's defective and is becoming quite frustrating . Any advice would be appreciated before I send it off to Uniden for service.
Here's the problem:
I live in Wake County, NC monitoring the VIPER system (Voice Interoperability Plan for Emergency Responders (VIPER) Trunking System, Various, North Carolina - Scanner Frequencies). I programmed my radio using the latest version of Freescan, and I am confident that my configuration is correct (I can send it for confirmation if needed). What is happening is that the scanner is stopping on channels where the traffic and TGID does not match what I programmed into the radio. For example, I programmed the radio for Wake Med with a TGID of 34592 but will hear Raleigh police with a TGID of 40112 (among others) on that channel. This is just an example; I will also hear Highway Patrol where I have RPD TGIDs programmed, Wake Med on RPD TGIDs, Rex on HP channels, Wake Med on Sheriff dispatch, etc.
I understand that multi-select is being used with RPD dispatch and different TGIDs will show up on those channels. This is not what I am experiencing. I also understand that sometimes channels are linked when needed and can demonstrate this behavior. This is not what I am experiencing. I can also understand that sometimes anomalies can happen for this to occur. Again, I do not believe this to be the problem because it happens all the time I listen to the scanner. If this was considered "normal" I would have found a lot more data in researching the problem, so I do not think it is normal to the extent I am experiencing the issue.
Some things I have done:
Move the radio around in case of distortion, try different times of the day, etc.
made sure ID Scan is enabled, not ID search
turned off/on Unit IDs
Messed with audio types on the channels
reprogrammed the radio from scratch using Freescan
reflashed the radio back to 1.07; reprogrammed
reflashed the radio back to the most current firmware; reprogrammed
disabled "control channel only" in Freescan and placed all the trunk freqs in the sites
lowered the baud rate on the radio and com port to 9600 in case data was getting scrambled during transfer
monitored a single channel (instead of scanning) and experienced the same issue
reset the scanner and reprogrammed
programmed some systems in by hand
monitored scanning/TGIDs using Freescan to what was going on. I clearly see the scanner stopping where I have programmed a TGID 34593 with an alpha tag of "Wake Med" showing that TGI 40112 is what is being decoded and hearing police traffic on a hospital channel that should not be linked for any reason.
etc., etc.
Tried a sample Freescan config
I have also researched these forums and others.
I was not able to resolve the issue with any of these steps.
I found some in the past who had these same issues with a different scanner and tried putting all the trunk freqs instead of just the CCs. As noted above, I tried that with no avail.
I also read some that said this type of problem was normal for Uniden scanners. I question if it is normal to the degree I am experiencing the problem otherwise I think I would have found much more data on the problem.
Thanks for your time in reading this post. I would greatly appreciate any assistance with this. I would also like to know if you experienced this problem and sent it off to Uniden for repair and the outcome. BTW, I've had this scanner for over a year and had this problem before. I thought I resolved it before, but it was not.
Here's the problem:
I live in Wake County, NC monitoring the VIPER system (Voice Interoperability Plan for Emergency Responders (VIPER) Trunking System, Various, North Carolina - Scanner Frequencies). I programmed my radio using the latest version of Freescan, and I am confident that my configuration is correct (I can send it for confirmation if needed). What is happening is that the scanner is stopping on channels where the traffic and TGID does not match what I programmed into the radio. For example, I programmed the radio for Wake Med with a TGID of 34592 but will hear Raleigh police with a TGID of 40112 (among others) on that channel. This is just an example; I will also hear Highway Patrol where I have RPD TGIDs programmed, Wake Med on RPD TGIDs, Rex on HP channels, Wake Med on Sheriff dispatch, etc.
I understand that multi-select is being used with RPD dispatch and different TGIDs will show up on those channels. This is not what I am experiencing. I also understand that sometimes channels are linked when needed and can demonstrate this behavior. This is not what I am experiencing. I can also understand that sometimes anomalies can happen for this to occur. Again, I do not believe this to be the problem because it happens all the time I listen to the scanner. If this was considered "normal" I would have found a lot more data in researching the problem, so I do not think it is normal to the extent I am experiencing the issue.
Some things I have done:
Move the radio around in case of distortion, try different times of the day, etc.
made sure ID Scan is enabled, not ID search
turned off/on Unit IDs
Messed with audio types on the channels
reprogrammed the radio from scratch using Freescan
reflashed the radio back to 1.07; reprogrammed
reflashed the radio back to the most current firmware; reprogrammed
disabled "control channel only" in Freescan and placed all the trunk freqs in the sites
lowered the baud rate on the radio and com port to 9600 in case data was getting scrambled during transfer
monitored a single channel (instead of scanning) and experienced the same issue
reset the scanner and reprogrammed
programmed some systems in by hand
monitored scanning/TGIDs using Freescan to what was going on. I clearly see the scanner stopping where I have programmed a TGID 34593 with an alpha tag of "Wake Med" showing that TGI 40112 is what is being decoded and hearing police traffic on a hospital channel that should not be linked for any reason.
etc., etc.
Tried a sample Freescan config
I have also researched these forums and others.
I was not able to resolve the issue with any of these steps.
I found some in the past who had these same issues with a different scanner and tried putting all the trunk freqs instead of just the CCs. As noted above, I tried that with no avail.
I also read some that said this type of problem was normal for Uniden scanners. I question if it is normal to the degree I am experiencing the problem otherwise I think I would have found much more data on the problem.
Thanks for your time in reading this post. I would greatly appreciate any assistance with this. I would also like to know if you experienced this problem and sent it off to Uniden for repair and the outcome. BTW, I've had this scanner for over a year and had this problem before. I thought I resolved it before, but it was not.
