There is no "need" for multiple instances in their own directories. It may be good practice to keep them separate, but a necessity it most certainly is not. Some DSD+ users have a single set of files in a single directory for multiple systems of all types. Some of those files have thousands upon thousands of entries and have grown quite large. Again, that may not be ideal practice, but it remains fully functional. It takes the software mere fractions of a second to look up data in those files.You don't really want to do that. The program will save one set (each) of talkgroups, radio IDs and frequencies. Assuming that the SysID is also preserved as part of each entry, eventually you will have files that are unmanageable. I don't know what the ultimate size limit is, but eventually it could become too much info to process or search through during the length of a single transmission, so you would not be able to keep up with the channel grants.
For multiple systems, you need multiple instances, each in a directory of its own with its own system-specific data.
I'm not sure that how you've described it makes sense. If you put control channels into a scan list, FMP24/DSD+ is simply going to stop scanning when it acquires the first control channel. Since the carrier never drops, and there is no audio to process, why would it move on to the next scan list entry?You could create a scanlist with the control frequencies in it - I assume you have FMP24 connected to DSD+ via tcp.
It will scan the trunks and stop on them when voice is detected then move on with the scan when voice is not detected - I use this to monitor several lower traffic trunks and it works well for me... I have a X seconds delay for each in the scan list in case there is a reply.
No - Control frequencies are in the scanlist.I'm not sure that how you've described it makes sense. If you put control channels into a scan list, FMP24/DSD+ is simply going to stop scanning when it acquires the first control channel. Since the carrier never drops, and there is no audio to process, why would it move on to the next scan list entry?
Perhaps you meant to say "you could create a scanlist with the voice frequencies in it"
Sample FMP24 scanlist for P25 trunks (although you can have mixed types in the same scanlistThanks, I think I'll give it a try. I'm new to fmp24/dsd+.. Do you have an example scanlist file you can send me?
I tried it and it works ok. It would be nice if there was a way to make it dwell on each control frequency a bit longer.. Every time it switches it rebuilds the frequency list so there is some wasted time on each switch.No - Control frequencies are in the scanlist.
Regardless of the continuous carrier it only stops if there is voice on the trunk.
I think the official way is to send an email to the fastlane email address.Is there a place I can go to formally request this feature? Or do the devs watch this group?
I have no idea if any of these DSD+ switches would give you what you want, I have to say I have not used any except -m1 which for me is a money card when I do mixed analog/digital scan listsIt would also be nice if the scan list would skip over voice and only lock onto CC...