Could the one without the LCN be the control channel?
Determining LCN's for NX4 System w/Sentinel v2.02 (revision 01)
- Thread starter jimv
- Start date
- Status
Not likely...control channel has a channel assignment in the systems i've seen.
You are correct. I have only submitted those five with confirmed LCN's to the RR DB. I ran the LCN finder for 15 hours and still only get those five. I've entered that one as a conventional frequency and if it ever gets active as NXDN I'll scan for the LCNs again.
Agreed and I noticed that too. I was wondering if being off by 1 or so KHz (453.01875 is 453.0187 in my units) could effect the proper LCN find, although, by SDS100 and 436HP seem to be receiving the system fairly well. I say fairly because there does seem to be missed transmissions. There are also a lot of i-whatever radio to radio transmissions on this system.
Agreed. The CC is properly listed in the RR DB and it does have a LCN assigned.
If transmissions are being missed, might have to expand your horizons to other licenses. Or...hold on some of the conversations and confirm if you are following, but due to your attention is focused on finding new talk groups, you might be hearing them just missing the replies.
Could one of the channels be data only? Maybe the scanner stops on that just long enough to miss a voice traffic conversation on another channel.
Ubbe
Member
The IF filters in a scanner that dictates the maximum allowed frequency modulation are wide enough to include any "normal" frequency errors and shouldn't distort any digital demodualtion. People have even modified scanners to use a more narrow filter that are more suited to NFM modulation but any frequency error will have more impact on digital distorsion and the squelch will also behave differently.
Unidens control channel trunking are not really suited to i-calls, user to user, but Whistlers voice channel trunking works perfect for that.
When an iCall, user to user, are set up the info are sent just briefly on the CC of the site where the two individuals are logged in with their radios and the setup telegram will not be continously repeated, late entry, as it will with TG's. It makes it crucial to have the scanner sit on that sites CC just in the brief fraction of a second when the call are set up or it will be lost for the Uniden scanner, and even if the call continues on the sites for several minutes the Uniden scanner will not be aware of it.
Whistlers way of scanning voice channels will always detect all iCalls and if I compare a BCD536 with TRX-2 in normal scanning I would say that the 536 captures 10% of iCalls and TRX-2 all 100%.
/Ubbe
Unidens control channel trunking are not really suited to i-calls, user to user, but Whistlers voice channel trunking works perfect for that.
When an iCall, user to user, are set up the info are sent just briefly on the CC of the site where the two individuals are logged in with their radios and the setup telegram will not be continously repeated, late entry, as it will with TG's. It makes it crucial to have the scanner sit on that sites CC just in the brief fraction of a second when the call are set up or it will be lost for the Uniden scanner, and even if the call continues on the sites for several minutes the Uniden scanner will not be aware of it.
Whistlers way of scanning voice channels will always detect all iCalls and if I compare a BCD536 with TRX-2 in normal scanning I would say that the 536 captures 10% of iCalls and TRX-2 all 100%.
/Ubbe
I will disagree with you on this. In every digital system I have programmed, TGID i0 is texted tagged Private Call and I am receiving them without issue. I'm not sure of your programming, but I-Calls work perfectly here.
- Status
Similar threads
