Capture logs for the both 436 and the SDS100 side by side and post them both for comparison.Get a debug file together so UPMan can diagnose what you're seeing and send it to the engineers for future firmware upgrades?
Capture logs for the both 436 and the SDS100 side by side and post them both for comparison.Get a debug file together so UPMan can diagnose what you're seeing and send it to the engineers for future firmware upgrades?
According to the hpe file, the service types are Utilities and Business. Do you have these service types enabled?Tested with 1.04.01 Main / 1.01.05 Sub. Still not tracking. FL location control is set to "No". I've been using ID Search mode most of the time, however, I've tried ID Scan as well with no luck. LCN 1 is the control channel for this log so you see 2-6 for voice.
Thanks for your time.
Quote from previous thread:
According to the logs, the scanner receives the control channel, and has decoded ID 291.
As I wrote before, for some reason the scanner seems to be unable to move to the voice channels.
There are 5 LCNs (1, 2, 4, 5, 6) in the logs.
Please try using:
ID Search mode
Location Control disabled
Please check the above.
__________________
Uniden Product Ninja
Who is UpMan and why doesn't he answer my email/phone call?
Personal Blog
For better help, tell us specifically what you are trying to scan.
It sure is a great feature. I've been waiting on this one for a very long time....
- the latest being NAC filtering which started getting addressed in last week's (?) beta firmware.
It can (potentially) be a great feature - but full of pitfalls for new users, issues with the firmware and factory default settings, and bad data, it's more of a problem at this point.It sure is a great feature. I've been waiting on this one for a very long time.
Russell
Here is the logSomething broke nxdn.
I have 2 sds100s and I dropped one back to the 1.03.05. As soon as I did it started receiving the system again.
I'm recording a log file now on the scanner with 1.04.x on it.
Will post that when I get home from work.
the said pitfalls can be prevented by just leaving the Site NAC control to ignore, especially when using the full database, but even then the NAC is still displayed, eventually the databases will catch upIt can (potentially) be a great feature - but full of pitfalls for new users, issues with the firmware and factory default settings, and bad data, it's more of a problem at this point.
Yes - but that was recently added (if I am not mistaken) and novice users - those that are told all you have to do is enter a zip code - won't know that....the said pitfalls can be prevented by just leaving the Site NAC control to ignore, especially when using the full database,
Maybe but there was even a recent post by Paul responding to a user that some systems, etc. are still listed as location 0/0 -- and how many years has that feature/function been there?but even then the NAC is still displayed, eventually the databases will catch up
Yes - but that was recently added (if I am not mistaken) and novice users - those that are told all you have to do is enter a zip code - won't know that....
in beta firmware just recently released....correct?It’s default off when the Firmware is loaded
Sent from my iPhone 8 using Tapatalk Pro
Jason WX4JCW
XPR7550 - SDS100
My point is simply that there is always going to be "bad data" (or even unexpected data like large or small circles/ranges) in the database - some more impactful than others. Some of the default use of that data conflicts with the concept of novice users using simple zip code programming and then wondering why things don't work.The location 0/0 was not from the main dB, it was from the user's FL.
Your rule 11 applies, but from my side. need an alternate contact.The location 0/0 was not from the main dB, it was from the user's FL.
Hit factor: need more information. See my first post. Which system? Can you include the hpe?
On the whole, location based scanning is far superior to any other method for scan selection. And, it will only get better over time. Watch for new features in RRDB in the not-too-distant future related to this.
My point is simply that there is always going to be "bad data" (or even unexpected data like large or small circles/ranges) in the database - some more impactful than others. Some of the default use of that data conflicts with the concept of novice users using simple zip code programming and then wondering why things don't work.
One thing that jumps out (but probably not a big factor if it scans with one version but not the other) is that Site 2 is missing a freq (the first one on the license). And, of course, is missing some LCNs.Your rule 11 applies, but from my side. need an alternate contact.
K8HIT