- Status
Thanks for the update Uniden and Upman! Firmware is working great for me.
Any chance on being able to toggle on/off the viewing of ENC unit ID's? So far, my work around is hutting punching "E" when it says ENC on the screen. Then saving the radio ID if I haven't done so already. I would rather see the ENC radio ID flash on the screen though so I can see if I have saved it already.
There is a military installation nearby and I am able to discover ENC TGID's by running trunked discovery. Would like to discover ENC radio ID's as well.
Any chance on being able to toggle on/off the viewing of ENC unit ID's? So far, my work around is hutting punching "E" when it says ENC on the screen. Then saving the radio ID if I haven't done so already. I would rather see the ENC radio ID flash on the screen though so I can see if I have saved it already.
There is a military installation nearby and I am able to discover ENC TGID's by running trunked discovery. Would like to discover ENC radio ID's as well.
Ubbe
Member
Would it be possible to have a selectable "skip enc" enable/disable? I have a DMR system where the dispatcher are always in the clear but some mobiles are enc and the scanner then of course immediatly leaves the system. It would also help to traffic analyze encoded systems during normal scan.
/Ubbe
/Ubbe
I've already requested these features and have been told by respected contributors in this forum to just go away. Don't believe me? follow the links..
http://forums.radioreference.com/un...hp-bcd536hp-now-available-14.html#post2919857 :roll:
But I know I'm not the only Nut!
PJH
Member
- Joined
- Aug 23, 2002
- Messages
- 3,621
So... Finally found a NXDN4800 system to monitor. I do not know if its correctly in the DB, but looking into the backend it appears it is:
https://www.radioreference.com/apps/db/?sid=7531
The 536 does NOT see this system, with the most recent updates. Does not scan it, does not show up for analyze or discovery functions.
It does see a site via CC reporting NX4 and RAN 1, but otherwise the system is not seen by the 536.
https://www.radioreference.com/apps/db/?sid=7531
The 536 does NOT see this system, with the most recent updates. Does not scan it, does not show up for analyze or discovery functions.
It does see a site via CC reporting NX4 and RAN 1, but otherwise the system is not seen by the 536.
Did you put the channel numbers in?
You have to drill down to the site information to see them. Since this is a VHF system, it's actually pretty simple.
https://www.radioreference.com/apps/db/?siteId=21370
VHF NXDN systems are a bit rare, but I've successfully monitored one in DSD+. Other than the channel numbers, the rest should be simple.
You have to drill down to the site information to see them. Since this is a VHF system, it's actually pretty simple.
https://www.radioreference.com/apps/db/?siteId=21370
VHF NXDN systems are a bit rare, but I've successfully monitored one in DSD+. Other than the channel numbers, the rest should be simple.
You MUST put in the LCNs. Though it is surprising that by entering ALL freqs, use analyze for the RAN Etc.. and then LCN Finder you not getting anything?
You need to make sure the system is in an FL and that it is enabled before you can do any Analyzing or LCN Finding.
The system must have at least one site enabled as well. Since it's a one site system (per the DB) it should be straight forward.
CH ID Frequency
1 154.0625
2 154.0325
3 154.7475
4 154.7625
5 154.9725
The system must have at least one site enabled as well. Since it's a one site system (per the DB) it should be straight forward.
CH ID Frequency
1 154.0625
2 154.0325
3 154.7475
4 154.7625
5 154.9725
When you enter a frequency for a NXDN system in the X36HP scanners, you need to put the proper channel numbers (or LCN) in or the system will not track.
See this thread in the Alabama forum,
https://forums.radioreference.com/a...hne-foley-robertsdale-system.html#post2931899
VHF is pretty straightforward, compared to UHF. The system I've tracked in DSD uses Channel Numbers (or LCN) of 1, 3, 5, 7..., but it appears that VHF uses a custom LCN as opposed to the complex formula used for UHF.
RAN follows the site number and is the same for all channels on a site. Since this appears to be a single site system, the RAN should be 1 across the board.
If you have any questions beyond that, feel free to PM me since it's sort of outside the scope of this thread.
See this thread in the Alabama forum,
https://forums.radioreference.com/a...hne-foley-robertsdale-system.html#post2931899
VHF is pretty straightforward, compared to UHF. The system I've tracked in DSD uses Channel Numbers (or LCN) of 1, 3, 5, 7..., but it appears that VHF uses a custom LCN as opposed to the complex formula used for UHF.
RAN follows the site number and is the same for all channels on a site. Since this appears to be a single site system, the RAN should be 1 across the board.
If you have any questions beyond that, feel free to PM me since it's sort of outside the scope of this thread.
I just got back from a 4 hour drive in the Tennessee Homeland Security District 7 area worked great received about 90% traffic I had the delay set to 2 seconds and 4 seconds would have worked better. The over the air alias worked good. I did see the scanner sit on a ENC DMR signal that 19 detected and ignored.
6079smithw
Member
Might be just me, but...
After installing the update my 536 seems to hold the control channel(s) on the county EDACS system here in Reno a little longer distance-wise from the xmit site and that's a good thing...
After installing the update my 536 seems to hold the control channel(s) on the county EDACS system here in Reno a little longer distance-wise from the xmit site and that's a good thing...
PJH
Member
- Joined
- Aug 23, 2002
- Messages
- 3,621
So basically it’s still fubar on the x36’s to make it work the same way as everything else does. I was expecting that the system would show up and be scanned just as any other, and the system does not appear on any menu in the scanner.
Last edited:
What is not working?
The channel IDs are wrong. If you sort frequencies in ascending order, the channel IDs will also be in order if correct. That is not the case with the system you linked. Also, NXDN channel IDs don't always start with 1 like DMR numbers, and will not be consecutive unless every frequency is immediately adjacent to its neighbors, and that is not the case here. Run LCN Finder first, before trying to do any other discovery or analysis on the system.
If the system isn't showing up to be scanned, make sure your Sentinel database is up to date, and then copy the system to a Favorite List with Location Control turned OFF, and Download & Moritor turned ON. If the Favorite List isn't active/scannable, or the system is disabled by Location Control or a Quick Key, then it won't show in the Analyze or Discovery menus.
PJH
Member
- Joined
- Aug 23, 2002
- Messages
- 3,621
The initial point I am making, a system in the database should show up reguardless of what the sites say, in th scanner.
When you go to “E” in analyze, discovery, or just scrolling thru th available counties/systems for the area, it’s “no system found” and does not scroll thru.
So on the scanner, it’s not even an option to place into FL to begin with.
I went into the admin side and verified that the system is public and ranged correctly, and it is. It’s been in the db for months.
When you go to “E” in analyze, discovery, or just scrolling thru th available counties/systems for the area, it’s “no system found” and does not scroll thru.
So on the scanner, it’s not even an option to place into FL to begin with.
I went into the admin side and verified that the system is public and ranged correctly, and it is. It’s been in the db for months.
The scanner database does not support NXDN yet that part is still being worked on if I understand your post. This is still all being worked on along with Sentinel to support NXDN. This is also why you got NXDN for $30 and not $60. So had you rather waited and not had NXDN? I am glad I got NXDN for $30 and learned how to program my scanner by hand.
And it says he's a "global database admin"... shouldn't he know this already? I wasn't following his question so I don't know if this is what he means or not but... if so...
Edit: Summary - the db import won't import the NXDN system, correct?
Actually, no, because then every system in North America would appear in every scanner menu and finding the one you want would be impossible. Limiting the Discovery and Analyze menus to scannable systems keeps the number of menu options to a manageable level. Also note that the location coding for Departments has to be correct for the system to be scanned. A system will not be scanned from the database unless at least one Site and at least one Department are within range as defined by Location Control. That's why I said to copy the system to a Favorite List that has Location Control turned off. That eliminates several variables that could cause the system to not be scanned.
Also since Sentinel hasn't been updated to support NXDN, NXDN systems are not yet included in the full database, and you will NOT be able to add them to a Favorite List in the scanner menu or in Sentinel. You will need to add the system to a Favorite List with ProScan or ARC, or else program everything by hand in the scanner menu, until Sentinel is updated to support NXDN.
- Status
