I'm running into an issue where on a NXDN4800 system, DSD-FME never tells SDR# where to go to switch to a voice channel. If it looses the control channel, it will tell SDR# to try and hunt for a new control channel according to the nxdn channel table.
Without having access to seeing what is going on, nor any logs or screenshots or videos of the activity, or idea of the signal levels, I can only offer some basic suggestions for NXDN48. First, above all else, make sure to use the squelch in SDR# to make sure no noise floor passes to DSD-FME. NXDN has a very short sync patter, and its hard to gate out noise from false sync patterns. Other than that, just make sure that the RIGCTL (Gpredict) plugin is connected to make sure it can control and tune SDR#, and that your csv file is formatted correctly with the frequencies listed for it. Also, make sure to disable any audio filtering/processing inside of SDR#, and just pass the unfiltered audio to DSD-FME. That was covered just a littel while back, starting around this post.
the output I have in the terminal is the screen below, no errors were listed Decoding doesn't work, you should have the decoded frames displayed, as for example with NXDN48: Digital Speech Decoder: Florida Man Edition ██████╗ ██████╗██████╗ ███████╗███╗ ███╗███████╗...
forums.radioreference.com
I don't have the best antenna for it right now so I'm waiting on it to come in and I do get a lot of CRC errors. But, is there any other thing I can do to try and have it switch to voice channels? Do the talkgroups have to be known and assigned in as csv file for it to switch to the TG voice channels? The log never shows it saying to switch to such and such voice frequency, so I'm thinking there's a setting somewhere that I'm looking over.
You don't need to make a csv file for groups, those are all purely optional, you will only need a csv for frequencies as long as that system isn't a DFA system, which, as far as I can tell, is pretty rare in NXDN.
Also, might help to know which version you are currently running, and if your issues persist, screenshots, logs, video grab of the behavior will be helpful. Also include the full command you are running in your .bat file and link to system being monitored, or at the very least, the csv file, those can help out as well for troubleshooting.