Search results

  1. JoeBearcat

    SDS100/SDS200: Uniden Repair service sent my SDS100 back without the NXDN and DMR Keys.

    Did the ESN change? Did you mention when you sent it in that it had those keys installed?
  2. JoeBearcat

    BCD160DN/BCD260DN now shipping!

    The BCD160DN/BCD260DN scanner models are now shipping from the Uniden website!
  3. JoeBearcat

    SDS100/SDS200: Waterfall

    https://my.uniden.com/
  4. JoeBearcat

    BCD436HP/BCD536HP: Loss of scanning of selected systems 436HP

    Could be. Also check any Quick Keys. Basically, go over the 'nothing to scan' checklist.
  5. JoeBearcat

    BCD436HP/BCD536HP: Loss of scanning of selected systems 436HP

    That sounds like a Service Type issue.
  6. JoeBearcat

    BCD396XT/BCD996XT: Loose BNC connector BCD996XT

    ... In theory at least..... I put it on a non-scanner object (don't want to use the 'g' word) and it worked so well the screw heads stripped out when trying to remove them. I ended up having to drill them out and replace the adapter. But it should be OK for the BNC connector.
  7. JoeBearcat

    BCD325P2/BCD996P2: BCD325P2 Programming 5 decimal (50 KHz) control channels

    It's not rounding - it's masking. That means the frequency is correct even though the 5th digit is not shown. You may see 453.0162 but the scanner 'sees' 453.01625. BTW, if it really bugs you don't listen to the aircraft band where they say "Switch to 123.07" when they are talking about...
  8. JoeBearcat

    SDS100/SDS200: SDS100/SDS200 New Public Release Sub CPU 1.03.05

    Not needed, as they are incorporated in the regular firmware release.
  9. JoeBearcat

    SDS100/SDS200: SDS 100 Site hold issue

    I will pass that on.
  10. JoeBearcat

    Sentinel: Not all sites included in Sentinel

    Yes. Data that is not usable is excluded. If the data is submitted to RR to make the channels usable by a scanner they should show in Sentinel after the next data update.
  11. JoeBearcat

    SDS100/SDS200: Delaying Opening Screen

    There is not, but anyone can use a phone to capture it or can just restart it multiple times to get the data.
  12. JoeBearcat

    SDS100/SDS200: SDS 100 Site hold issue

    I edited my post before your post to clarify things.
  13. JoeBearcat

    SDS100/SDS200: SDS 100 Site hold issue

    HOLD TIME should stay on the *system* for at least the set time. If set for 0 it will evaluate each site and stay on the system only long enough to evaluate each one at least once. If set for 4 seconds, for example, it may evaluate multiple sites more than once. But it should not move off that...
  14. JoeBearcat

    SDS100/SDS200: SDS100/SDS200 New Public Release Sub CPU 1.03.05

    That could be a symptom of an SD card getting full or going bad. Not sure why, but others have reported that decode issues were solved by new cards.
  15. JoeBearcat

    SDS100/SDS200: SDS 100 and 200 not muting Encryption

    FWIW encryption detection is being fine tuned by engineering. The new version should be in beta test shortly.
  16. JoeBearcat

    SDS100/SDS200: SDS100/SDS200 New Public Release Sub CPU 1.03.05

    Also WRT protocol for the waterfall, that should be published soon (if not already). https://info.uniden.com/twiki/bin/view/UnidenMan4/SDS200FirmwareUpdate
  17. JoeBearcat

    SDS100/SDS200: SDS100/SDS200 New Public Release Sub CPU 1.03.05

    Would you be willing to make some test logs and forward them to me?
  18. JoeBearcat

    SDS100/SDS200: SDS100/SDS200 New Public Release Sub CPU 1.03.05

    Good intuition. Another version will soon be in beta testing.
  19. JoeBearcat

    SDS100/SDS200: New Firmware ! 1.23.05

    It also resolved the issue of some users being 'stuck' at v1.23.03A since Sentinel saw that as being the same as 1.23.03.
Top