GamecockSJ
Member
Since the Uniden 436/536 scanners have an NXDN option now I thought I'd create a thread similar to the DMR one. Haven't made the upgrade purchase yet myself. Anyone know of any active NXDN systems in NC?
Guys,
I’m new to NXDN and have a question. I monitor S.C. Fleetnet on 463.9 (Brunswick County site). I receive the RAN (15), SYS: 219, Site 15 info on my 536 screen. Is it possible to have a signal threshold be just enough to provide that data but not be strong enough to decode?
Additionally, am I wrong in thinking I should program that as a OFT as opposed to Conventional?
Thank you.
Thank you Troymail. Yes, I was aware of the UNCW NXDN and it was one of the reasons I purchased my DV1, only to discover the DV1 doesn’t “do” 9600. Now that I have the NDXN capable 536 I will give their maintence xmissions a shot.
I’m going to try to enter all of the Fleetnet frequencies manually as a trucked system and see how that goes.
John
Good Friday holiday.
Ronnie
I reprogrammed the Brunswick Transit frequency (452.75000) again - directly on the radio as a NXDN One Frequency
Well, I finally got hits on the SC Fleettalk (Supply site) overnight.
The TRX-1 recorded them and there were a few that were at least 7-8 seconds long.
The 436 captured nothing.
I have "system" programmed into the 436 two different ways - once as a NXDN One Frequency system and the other as a NXDN trunk system.
EDIT: Even in OFT mode, I see the 436 "hanging" on the system for extended periods with no activity.... the display is showing NX4 most times and occasionally NX0 (?)
Why are you programming it as NXDN OFT? It's in the DB as a conventional NXDN. All you have to do is add it as a conventional channel on the 436.
1. Add conventional frequency: 452.75
2. Edit that conventional frequency's characteristics -- specifically:
Set Audio Type: Digital Only --> Set NEXEDGE RAN: 30
RAN (and LCN on trunked) should never be left default. The Unidens require said information.
Mike
For Unidens:
- New System
- NXDN Trunk
- Edit Sys Options --> ID Search: ON
- Edit Site --> New Site --> Set Frequencies
- New Frequency: 463.900 , Input LCN: 713 ; Set RAN/Area: 15
Never leave RAN / LCN as default. If you didn't know the RAN / LCN, set the RAN to "Search" and then run LCN Finder on the system to allow the scanner to find the LCN. Once it finds the LCN, back out and save the found LCN(s) to the system. In this case, assuming RAN 15 and LCN 713 in the DB are correct, there is no need for running LCN Finder.
Mike
I was basing the programming (to some degree) on the way Uniden handles conventional DMR... obviously, this isn't DMR and is different.
I've now configured as you stated above -- I see in conventional mode that they did not provide an option for RAN search which is what I would expect the default to be.
Watching now for activity.
I get the LCN issue -- I'll be dealing with that on a short drive tomorrow (probably) on a nearby county system where the LCNs are all still 0 in the database.On trunked DMR and trunked NXDN Type-C systems (where there is a control channel present), you absolutely have to have those types of details filled in on a Uniden. This is specifically because the Uniden's actually do use/rely upon the control channel for trunking. And, since there are not default bandplans for DMR / NXDN like there are for P25 / Moto Type II, anything monitoring the control channel only knows about LCNs. You have to have the frequency<-->LCN pairing in place so that when the CC tells the scanner to switch to LCN 453, the scanner knows to switch to VC frequency 123.4567.
The reason why you can get away without adding a lot of this on the Whistlers is because they aren't relying upon the control channel for trunking and are simply scanning / checking every frequency programmed into a given site during every scan pass in order to see if there is activity.
Yeah, it's a pain in the rear to have to know / add that information, but in the end it really should perform 100%. I'm hoping it does for you.
Mike