SCOTTER
Member
So can you guys chill out long enough to let me know if the NXDN and also the DMR upgrades worth getting now or should I wait till the bugs get worked out ?
NXDN Upgrade for BCD436HP and BCD536HP Now Available!
- Thread starter UPMan
- Start date
- Status
troymail
Silent Key
DMR has been out for quite a while as is as stable as it is probably going to get.
NXDN works for most things I'd tried if programmed correctly and you have a strong enough signal. HOWEVER, unless you try/buy a third-party software package, you'll have to program NXDN stuff by hand as Sentinel doesn't handle it yet.....
Get the NXDN now at the introductory price. If you wait until sentinel supports it the price goes up. DMR has been out for awhile and seems stable.
Very Chill here!
I'd recommend getting the upgrades, The bugs are minimal, and will "hopefully" be corrected if need be.
It all depends on an individual's needs, and signals in your location(s).
Plus the price for NXDN will be going up...
I'd recommend getting the upgrades, The bugs are minimal, and will "hopefully" be corrected if need be.
It all depends on an individual's needs, and signals in your location(s).
Plus the price for NXDN will be going up...
SCOTTER
Member
Thanks guys I will give it a shot because I need a headache to take my mind off my other headaches. lol
Some folks (I for one) would like to be able to at least log TG's & RID's when researching a system for the purpose of determining & submitting to RR. If everything is encrypted then there is no research that can be performed. Effectively turning a $500 tool into a paper weight is BS Uniden.
No, I don't want to listen to un-intelligible audio but I'd like it to be an option.
It sounds like you want to analyze the system. There is a built-in tool for doing just that called ANALYZE. It's in the root menu list.
You can also pause on a TG and see the info.
Just because it doesn't work the way you want it to work does not mean it's not possible.
That is why we buy PROSCAN for logging and recording data.
troymail
Silent Key
So - effectively - another "indirect paid upgrade" (purchase of a third party product) is required.... or at least that's the way I read it...
I buy the upgrades as they come out... Half price, then I us discovery a few times. Because the firmware is also updated, it seems I pick up some channels more clearly, and some new channels. When Sentinel updates, more good stuff
... I don't understand all this other banter. The rest of this is way too confusing...As is the manual, Why don't you write BCD436HP for Dummies book for us instead of arguing?
... I don't understand all this other banter. The rest of this is way too confusing...As is the manual, Why don't you write BCD436HP for Dummies book for us instead of arguing?
Already been done:
Easier to Read BCD436/536HP Digital Scanner Manual
Happy Monitoring!
Marshall KE4ZNR
I want the radio to respond (under normal scanning conditions [Like Whistlers & older Radio Shack P25 Scanners]) to any active TG.
It's really so simple that smart folks can't get it through their skulls. :roll:
Should not have to delve into analyzing/discovery or anything else.
WHY IS THIS SO CONFUSING?
?
Then turn ID Search on. It works regardless of whether the talkgroup is encrypted, or the encrypted audio is muted. The only thing encryption muting does is silences the garble noise. Encryption muting has no effect on logging or displaying talkgroup IDs or radio IDs, either in the radio, or externally via ProScan. As long as the transmission continues, the scanner pauses on the channel and displays the same ID data as on an unencrypted transmission.
This is really getting tedious.
ID SEARCH IS ENABLED! (IT WAS A GIVEN FROM THE GET GO)
ENCRYPTION MUTING (AS UNIDEN SEES IT) IS TO IGNORE ANY TALKGROUP THAT IS ENCRYPTED REGARDLESS OF WHETHER A TG IS ALREADY SAVED IN THE PROGRAMMING OR NOT, REGARDLESS OF HOLD TIMES/DELAYS WHATEVER SETTING YOU WISH TO ADJUST. (DURING NORMAL SCANNING MODE)
YES YOU CAN HEAR ENCRYPTED (garbled) COMS ON P25 PH2 BECAUSE THEY HAVE NOT PERFECTED IT YET (THE MUTING FEATURE). ON P25 PH1 SYSTEMS IT WILL NOT EVEN STOP ON AN E TG CURRENTLY. IF YOUR SCANNER IS STOPPING ON E TG'S THEN I WOULD HAVE TO POSE THE QUESTION "WAS IT SOMETHING OTHER THAN PH1? AND WAS THE COMM YOU HEARD REALLY ENCRYPTION"
I KNOW WHAT I'M TALKING ABOUT AND WILL NOT RELENT ON THE SUBJECT.
Do you have any other moves?
No need to shout man.
I feel my simple suggestion (begining back at post http://forums.radioreference.com/un...hp-bcd536hp-now-available-12.html#post2914476) has merit and won't allow others to bash it, they are apparently of their rockers and must have an answer for everything. Even if it the responses were well intended it was misguided and continues on and on and on.
It's become personal and I did not start that!
It's become personal and I did not start that!
Last edited:
Why are people seeing different results? There has to be a difference in programming or system type or something that isn't being stated/detailed but will be an "ah ha!" moment for one or the other.
As it is, it seems two people are reporting opposing results from "the same thing".
Maybe each needs to detail exactly what they are talking about - including settings, monitoring mode (i.e. search, scan, discovery, analyze, making toast, whatever) - to see where the difference lies.
Otherwise, it seems one is wrong and the other is right...yet both insist they are right...which is interesting. I'm genuinely curious.
The arguing and yelling doesn't help. Rational explanation should, though. Remember - you both are in front of your scanners and have your scanner setup a certain way but the other isn't seeing your scanner like you are so there has to be a difference somewhere in there if the results are different...
As it is, it seems two people are reporting opposing results from "the same thing".
Maybe each needs to detail exactly what they are talking about - including settings, monitoring mode (i.e. search, scan, discovery, analyze, making toast, whatever) - to see where the difference lies.
Otherwise, it seems one is wrong and the other is right...yet both insist they are right...which is interesting. I'm genuinely curious.
The arguing and yelling doesn't help. Rational explanation should, though. Remember - you both are in front of your scanners and have your scanner setup a certain way but the other isn't seeing your scanner like you are so there has to be a difference somewhere in there if the results are different...
I just confirmed that encrypted talk group IDs (and UIDs) are captured during trunking discovery.
It's not "personal" to point out that x36 scanners do not behave the way you describe for most types of encrypted audio (tested and verified with NXDN, DMR, and P25 Phase II), or to post evidence demonstrating that fact. It is also not "personal" to point out ways to accomplish what you say you are trying to do with functions in the scanner menu and 3rd-party software.
You are the one shouting and ranting and questioning other people's intelligence.
If there is any rational conversation to be had here, it should be about possible inconsistencies in the way encrypted audio is handled, e.g. what type of encryption is used on the system you monitor that causes the scanner to ignore the transmission completely vs displaying ENC and the talkgroup and radio ID's while the transmission is in progress, which is how encryption is handled in the majority of cases. An additional useful discussion would be about the types of encryption that are not muted vs those that are, so that the handling of encryption could be made more consistent.
Assuming that your particular case is what happens all the time is not accurate or productive.
You are the one shouting and ranting and questioning other people's intelligence.
If there is any rational conversation to be had here, it should be about possible inconsistencies in the way encrypted audio is handled, e.g. what type of encryption is used on the system you monitor that causes the scanner to ignore the transmission completely vs displaying ENC and the talkgroup and radio ID's while the transmission is in progress, which is how encryption is handled in the majority of cases. An additional useful discussion would be about the types of encryption that are not muted vs those that are, so that the handling of encryption could be made more consistent.
Assuming that your particular case is what happens all the time is not accurate or productive.
Yeah, have that, is so not easy or step by step on anything.
- Status
