Well, then you assume wrong. DFA means that the system supplies the actual TX and RX frequencies. They're right there in post #53.I've fine combed Internet and only reference to DFA are Nexedge Generation 2. So I will assume this system works as old Motorola, new Tetra and new DMR TierIII that it uses a base frequency and channel numbers are counted upwards from that frequency and the control channel only sends out channel numbers, no frequencies. And then the DSDPlus.frequency file are very much in use to display the correct frequencies in DSD+ that relates to the channel numbers.
You have to have the frequency file set up to get info? The frequency file is the info. You had to have the info first in order to add it to the frequency file!Unidens DMR scanners only go by channel numbers that are programmed next to a frequency and that frequency are used by the scanner, whatever that frequency might be. To be able to program a Uniden scanner one have to correctly link a channel number, LCN, to a frequency and either need to use LCN finder or have the frequencyfile in DSD+ correctly setup to get any kind of helpful info from that program.
The channel numbers and frequencies found so far doesn't match.
/Ubbe
It's quite possible that your scanner can't handle the system. And there should be no need for an LCN "finder" as the system broadcasts the LCN/frequency relationships. Like a P25 system, one should only need to program the control channels. If your scanner doesn't offer that option, it likely doesn't understand the system.I have tried the LCN finder and get nothing. Im going to give it another try tomorow when im back in that area.
You can add the channel info from post #53 to the frequencies file if you want DSD+ to follow voice traffic, but that's all.If there are any settings or DSD changes anyone wants me to try i can give it a shot.
Correction - I just tried it on a similar site here and DSD+ follows voice calls even without data in the .frequencies file. It pretty much acts like it does with a P25 control channel - just tune to the CC and off it goes.You can add the channel info from post #53 to the frequencies file if you want DSD+ to follow voice traffic, but that's all.
What? No - it's part of the DMR TIII Trunking standard...Is this DFA for DMR the answer from Hytera to Motorolas RAS, to lock out any competitors from selling equipment into the system?
What? DSD+ is displaying bogus values? How would you know? So this data, directly off the control channel, is bogus?When the CC sends the DFA frequency it doesn't send any channel number, what's the point, and it's only showing, and with bogus values,
I can't figure out what point you're trying to make here.because the normal DSD+ cannot handle it and you have to use the fastlane pay version from dec 2018 to be able to handle it correctly?
Plenty of NEXEDGE and TIII DFA traffic here...Upman implied that their scanners aren't really up to date about DFA and need debug logs from those system to figure out the protocol.
His scanner works because he added the relationships between LCNs and frequencies. If the scanner was fully DFA-compatible, he wouldn't need to.But Gary's scanner still follows the TG calls and private calls in the system. If a scanner works properly it ignores any voice channels and LCN programmed in the system, only the CC channels are used? Greg could delete any LCN info and voice frequencies and only track the system using CC, as it seems to track the calls as it is programmed now?
Every modern NEXEDGE and TIII radio is DFA and non-DFA capable, so they're already backward compatible. It's up to the system operators to choose DFA or non-DFA control channel messages.Could DFA radios be backward compatible, and some sites use LCN and others DFA in the same system that makes mapping out the system a bit more difficult?

I can't figure out what point you're trying to make here.the normal DSD+ cannot handle it and you have to use the fastlane pay version from dec 2018 to be able to handle it correctly?
Why can't they be separate networks/sites?The site listed in the DB 410.0125 I believe from one of the threads this was said to be somewhere in King City if I remember correctly..
But these two are reporting the same net/site (453.4875 & 462.1125) but is listed as the site being at 77 Davisville in Toronto.
I am confused about this, is it in Toronto or KC or are these somehow two different sites?
Matt
I think I agree.I suggest it be called Signalwireless for now. All the sites seem to fall into the map posted in #71.
Defaults usually are.Net 13 seems to be very popular
When the default network ID is 13, it's blindingly obvious whether all of these systems are actually using network ID 12 or 13. Hasn't stopped scanner manufacturers from getting it wrong though. And once they get it wrong, they won't fix it. Same as multiplying Motorola talkgroups by 16 for no good reason - it's a permanent fixture on the scanner landscape.To add to the confusion, DSD+ and Uniden scanners seem to differ in their interpretation of the Net ID. My memory is fuzzy, but I believe one displays it as 12 while the other displays it as 13. I gave up trying to figure it out, seems that different standards are followed depending on what software or hardware you're using.![]()
I think I agree.