I've begun to observe odd behavior involving both the 100 and 200.
I mostly monitor 800MHz Simulcast on a major system in my city. Both units have faithfully ticked away for over a year of everyday scanning without a single issue. Both radios have gone neck and neck with a work issued Motorola radio programmed to the same system without missing a single transmission. Because of such good operation, I've avoided all other sites in the area and only have the units set to scan simulcast only.
Recently, I've observed that the unit(s) will not "hear" any Talkgroups while monitoring the simulcast site, despite perfect RSSI reports and the "data" icon popping up, and I know there is traffic because I'm getting it through several different radios, some on the exact same antenna. When I switch to another non-simulcast site on the same system, the scanner resumes its normal operation and traffic comes through as normal. When I switch back to simulcast, the traffic disappears again.
This is only observed on the aforementioned system. I do not have the same issue while monitoring other simulcast sites on two major neighboring systems in my area.
Sometimes this is resolved by switching to another favorites list, and switching back. Sometimes turning the unit on and off works also. Sometimes after a while the radio starts working by itself again. This sometimes fixes the problem, however its annoying and worrisome in the sense that perhaps the radios are failing internally in some way. More worrisome is I can't find a way to replicate the fix as it seems to be different each time.
I've observed this behavior first on my SDS100, and now several weeks later the SDS200 has begun doing the same thing.
I've observed this behavior commonly starts when:
1: I've disconnected the scanner from a computer after making changes to my favorites list or database.
2: I've completed a "trunking discovery" and have resumed normal scanning.
After resolving the issue, the problem does not seem to return until the above actions are performed again.
Recently, I've begun to let the SDS200 run for extended periods of time while doing a trunking discovery when I'm away from home, which is around the same time I started observing this behavior. That is the only major change in usage this scanner has seen since I bought it. I am careful to download and delete the discovery off the scanner after I complete it to avoid running up the SD cards data. This activity shouldn't affect the SDS100 however because that scanner is only on when I'm out and about and I don't use it to do a trunking discovery.
Both radios have gone through quite a few upload and download cycles in the last few months as I tweak and improve my favorites lists.
---
Sorry for my post being long winded; I wanted to accurately paint the picture of the problem for you guys out there.
Are any other users aware of this issue? Some sort of data corruption working its way in maybe? Any fixes?
I mostly monitor 800MHz Simulcast on a major system in my city. Both units have faithfully ticked away for over a year of everyday scanning without a single issue. Both radios have gone neck and neck with a work issued Motorola radio programmed to the same system without missing a single transmission. Because of such good operation, I've avoided all other sites in the area and only have the units set to scan simulcast only.
Recently, I've observed that the unit(s) will not "hear" any Talkgroups while monitoring the simulcast site, despite perfect RSSI reports and the "data" icon popping up, and I know there is traffic because I'm getting it through several different radios, some on the exact same antenna. When I switch to another non-simulcast site on the same system, the scanner resumes its normal operation and traffic comes through as normal. When I switch back to simulcast, the traffic disappears again.
This is only observed on the aforementioned system. I do not have the same issue while monitoring other simulcast sites on two major neighboring systems in my area.
Sometimes this is resolved by switching to another favorites list, and switching back. Sometimes turning the unit on and off works also. Sometimes after a while the radio starts working by itself again. This sometimes fixes the problem, however its annoying and worrisome in the sense that perhaps the radios are failing internally in some way. More worrisome is I can't find a way to replicate the fix as it seems to be different each time.
I've observed this behavior first on my SDS100, and now several weeks later the SDS200 has begun doing the same thing.
I've observed this behavior commonly starts when:
1: I've disconnected the scanner from a computer after making changes to my favorites list or database.
2: I've completed a "trunking discovery" and have resumed normal scanning.
After resolving the issue, the problem does not seem to return until the above actions are performed again.
Recently, I've begun to let the SDS200 run for extended periods of time while doing a trunking discovery when I'm away from home, which is around the same time I started observing this behavior. That is the only major change in usage this scanner has seen since I bought it. I am careful to download and delete the discovery off the scanner after I complete it to avoid running up the SD cards data. This activity shouldn't affect the SDS100 however because that scanner is only on when I'm out and about and I don't use it to do a trunking discovery.
Both radios have gone through quite a few upload and download cycles in the last few months as I tweak and improve my favorites lists.
---
Sorry for my post being long winded; I wanted to accurately paint the picture of the problem for you guys out there.
Are any other users aware of this issue? Some sort of data corruption working its way in maybe? Any fixes?
