Howdy,
When scanning NXDN, I strongly suggest scanning all NXDN systems as conventional frequencies. Yes, even if it is a trunked system, import all of the trunked frequencies to EZ Scan as conventional objects.
Unless there is a compelling reason to add NXDN as a trunked system, I would not use NXDN as a trunked system. Compelling reasons might include the following:
The TRX does not trunk track. Programming NXDN as trunked objects is useful only if you are dealing with locking out a bunch of talkgroups or doing other talkgroup specific tasks (where a large number of talkgroups are being dealth with). Otherwise, there is no benefit to programming as trunked; in fact, programming NXDN as trunked is likely hurting your scanner's performance. It is also more complicated and slower to program.
You do not have to program trunked NXDN systems as trunked to receive them. Trunked systems will be received when programmed as conventional objects.
I encourage you to program all NXDN as conventional frequencies with "any" RAN and a wildcard for the talkgroup.
Additionally, I have a website that will allow you to accomplish this quickly: Digital Frequency Quick Import
I write this so that hopefully people can use their scanners more effectively. I don't have any product or marketing interest, which stakeholders in certain entities may have. My goal is to make scanning easier and more accessible. I think the tactic I've explained above will help many of you.
When scanning NXDN, I strongly suggest scanning all NXDN systems as conventional frequencies. Yes, even if it is a trunked system, import all of the trunked frequencies to EZ Scan as conventional objects.
Unless there is a compelling reason to add NXDN as a trunked system, I would not use NXDN as a trunked system. Compelling reasons might include the following:
- You want to listen to only certain talkgroups on a trunked system (e.g. you want to lockout two talkgroups but listen to three).
- However, if you are interested in just one talkgroup on the system, you should still program as conventional.
The TRX does not trunk track. Programming NXDN as trunked objects is useful only if you are dealing with locking out a bunch of talkgroups or doing other talkgroup specific tasks (where a large number of talkgroups are being dealth with). Otherwise, there is no benefit to programming as trunked; in fact, programming NXDN as trunked is likely hurting your scanner's performance. It is also more complicated and slower to program.
You do not have to program trunked NXDN systems as trunked to receive them. Trunked systems will be received when programmed as conventional objects.
I encourage you to program all NXDN as conventional frequencies with "any" RAN and a wildcard for the talkgroup.
Additionally, I have a website that will allow you to accomplish this quickly: Digital Frequency Quick Import
I write this so that hopefully people can use their scanners more effectively. I don't have any product or marketing interest, which stakeholders in certain entities may have. My goal is to make scanning easier and more accessible. I think the tactic I've explained above will help many of you.
Last edited: