Each system has it's own quick key in my programming. I will upload an HPE file of the favorite list later today for testing.
Sent from my SM-G965U using Tapatalk
- Status
Each system has it's own quick key in my programming. I will upload an HPE file of the favorite list later today for testing.
Sent from my SM-G965U using Tapatalk
If you're using software programming, Erase the entire scanner and allow the programming a fresh canvas. It's also possible you might have not deleted previous programming before you overwrote it.
Yes, Just the UID has a tone assigned, Not the TG.
It occurs on multiple system types, P25 PH1, PH2, DMR CON+, and Multiple Alert Tones,
Volume set to Auto.
Yes just as you described! it goes all digital and the conversation becomes unintelligible because of the strange alert behavior.
It's like the Alert Tone restarts several times in the beginning before finishing correctly. (Instead of playing one time) Just like a Hiccup, Hiccup, Hiccup..
It's a Uniden BCD436HP. (Two of 'em)
Last edited:
Yup. That a what I have as well. 436. So far I've only noticed it happen on 2 different RID's but on the same system.
http://www.radioreference.com/apps/db/?sid=2560
Sent from my SM-G390W using Tapatalk
-----------------------
Uniden 436HP/VHF/UHF NMO Ground Plane Base Antenna
Anytone 6666/Sirio Tornado 27 Antenna
President Grant II/K40 Magnet Antenna
TRC-465 - Spare
I am posting this under the assumption that you already know this, but...you do realize that iDAS uses NXDN correct? I suspect it is as Jon said and sees the NXDN first and then sees the iDAS and switches.
More in iDAS here, just in case: IDAS Digital Land Mobile Radio System - Features - Icom America
I do think you knew this already but just making sure...and posting for anyone else's benefit who may not.
Even though iDAS and NexEDGE are both NXDN, they are not the same. Each has subtle proprietary variations unique to its Vendor. iDAS is iCOM, and NexEDGE is Kenwood. On the trunking side, this makes the format differences. Like with P25, the CAI may be the same with ALL Vendors, each TRS format is unique. An NexEDGE 4800 should only show as NX4, 9600 as NX9, and iDAS as IDS. Just as DMR is DMR.. Capacity Plus, Connect Plus, and Tier 3 all are different.
I’ve seen that as well it will give IDS then NX4 so something is up
Sent from my iPhone 8 using Tapatalk Pro
Jason WX4JCW
Unication G4, BCD536HP
I thought i was seeing things, but watching a couple of tx the scanner displays nx4 and then ids on a conventional Nxdn.
I had read somewhere, there is a combo. So is this a unique system of the combination?
Could they use one type at one tower and then another type with another tower?
I had read somewhere, there is a combo. So is this a unique system of the combination?
Could they use one type at one tower and then another type with another tower?
Last edited:
Alright, I formatted the card that was in the scanner and reloaded the programming, and it is still having the same HOLD issue.
I also used a different formatted card with the programming loaded onto it, and it too is having the same issue.
I was asked earlier to upload an HPE file of the favorite list in question, it is attached. The system that is having the issue is Fisher Wireless TeamTalk. To recap, the scanner will not HOLD on the system even though it is supposed to.
The Fisher Wireless TeamTalk system is a Connect Plus system. I have multiple sites programmed in for it. When I hold on any other DMR/MOTOTRBO system, it doesn't have the issue (all of which do not have multiple sites programmed).
I have a case where the same thing happens. The scanner is receiving a NX9 system when a stronger IDAS system beacons. Since the IDAS system is stronger, the scanner flashes that. Then it goes back to decoding the weaker NX9 system.
That case is not a bug, but a change in what is actually being decoded.
That said, since both NexEdge and IDAS are both NXDN, it's not like it's showing a completely different format. Both have similar data since both are NXDN-based.
Try removing the tone to see if the issue resolves itself completely. And/or try a different tone.
It could also be a 'weak' decode of the UID where it loses it then starts again (hence another alert).
You made my point better than I did. Those subtle variations are not always decoded immediately. It's not much different than P25 falsing 67.0 Hz on a CTCSS decoder. P25 does not use CTCSS, but the endcode can false CTCSS and make it look as if the signal had CTCSS.
Any chance that it's a simple case of a composite control channel? If it was originally (or still is) a single frequency site, or if they administrators simply chose to make the CC share duties with voice when the system is loaded, then you've got a composite control channel. It'll show NX4 when there is no voice traffic on the CC, but when voice traffic is occurring on the CC it'll show IDS.
I've never had access to an NXDN48 system using a composite control channel, but I monitored a local NXDN96 running composite control channels for a long time.
Mike
I've never had access to an NXDN48 system using a composite control channel, but I monitored a local NXDN96 running composite control channels for a long time.
Mike
Hence my saying you have to ASK that QUESTION: Is this ONE SYSTEM?
crash1
Member
Capacity Plus is still missing a lot of the communication and there are a lot of false IDs
I can confirm that fw 1.17.0 is causing ghost tg and UID instead of the saved ones. 3 frequency cap+ uses tg 1 through 16, and 40% of the time they are ghosting to 4 or 5 digit tg numbers and the same with RIDs. 3 digit radio id's are showing up as 6 or 7 digit id's...
While showing the errouness numbers, turing the function knob either direction will bring the conversation showing back up with the correct and stored tg id and names and radio id's..
There is most definitely something batty with the dmr cap+ decode code in this fw.
Sent from my SM-G935V using Tapatalk
All I can say is that the in the Domer NXDN96 system in Ohio, composite control channels showed NXDN in DSDPlus when monitoring the control channel, and when the CC switched to voice it showed IDAS. At least it did that a year ago. That particular system now has multiple frequencies per site and I'm not sure if any of the sites are set up for composite control channel trunking any longer.
Mike
- Status
