DSDPlus DSD+ and Single Frequency DMR

[seagravebuff60]

I have a lot of DMR in my area and use DSD+ Primarily to decode it. For a long time whenever I would decode One Frequency DMR the group file would populate like this: (What mean by one frequency DMR is that it's the same as Single frequency DMR when programming Uniden Scanners)
;

DMR, 0, 5, 50, Normal, 2, 2023/09/18 15:03, ""
DMR, 0, 9008, 50, Normal, 13, 2023/09/18 14:51, ""

Just a lot more records and it was a pain to go through each log to find out the frequency and Talkgroup so I could label it appropriately.
Recently, I started to set up these one-frequency DMR systems in my files like a conventional P25 with a fake System ID and Site. I've been running a setup like this for about 3 days now and have had some success. Now each single frequency DMR Frequency has a .networks, .siteloader, .sites, .frequency, .groups & .radios record. So it's much easier to track down what record belongs to which.

This is what each file looks like:
.networks
DMR, 23, "Schools Busses (462.25)"

.sites
DMR, 23, 1, "Schools Busses (462.25)"

.siteloader
DMR, 23, 1, "Weston Schools Busses (462.25)"

.frequencies
DMR, 23, 1, 0, 462.2500, 0.0, 0

.groups
DMR, 23, 23, 50, Normal, 76, 2023/09/18 16:35, "Busses"

.radios
;Busses

DMR, 23, 23, 12, 50, Normal, 2, 2023/09/18 16:11, ""
DMR, 23, 23, 14, 50, Normal, 6, 2023/09/18 16:35, ""
DMR, 23, 23, 301, 50, Normal, 56, 2023/09/05 16:18, ""
DMR, 23, 23, 303, 50, Normal, 12, 2023/09/06 7:16, ""
DMR, 23, 23, 306, 50, Normal, 17, 2023/09/18 15:18, ""
DMR, 23, 23, 307, 50, Normal, 1, 2023/09/18 15:22, ""
DMR, 23, 23, 309, 50, Normal, 25, 2023/09/05 13:52, ""
DMR, 23, 23, 310, 50, Normal, 16, 2023/09/18 16:19, ""
DMR, 23, 23, 311, 50, Normal, 7, 2023/09/18 16:06, ""
DMR, 23, 23, 312, 50, Normal, 18, 2023/09/18 15:17, ""
DMR, 23, 23, 313, 50, Normal, 10, 2023/09/05 15:23, ""
DMR, 23, 23, 314, 50, Normal, 18, 2023/06/16 11:21, ""
DMR, 23, 23, 315, 50, Normal, 27, 2023/09/18 16:35, ""
DMR, 23, 23, 316, 50, Normal, 28, 2023/09/05 16:01, ""
DMR, 23, 23, 317, 50, Normal, 9, 2023/09/18 15:54, ""
DMR, 23, 23, 318, 50, Normal, 8, 2023/05/15 8:04, ""
DMR, 23, 23, 319, 50, Normal, 9, 2023/09/18 16:19, ""
DMR, 23, 23, 320, 50, Normal, 15, 2023/09/05 16:33, ""
DMR, 23, 23, 322, 50, Normal, 2, 2023/09/18 15:22, ""
DMR, 23, 23, 323, 50, Normal, 1, 2023/09/18 16:19, ""
DMR, 23, 23, 324, 50, Normal, 9, 2023/09/05 13:52, ""
DMR, 23, 23, 325, 50, Normal, 6, 2023/06/16 7:27, ""
DMR, 23, 23, 328, 50, Normal, 1, 2023/09/18 16:19, ""
DMR, 23, 23, 329, 50, Normal, 7, 2023/09/05 15:22, ""
DMR, 23, 23, 330, 50, Normal, 3, 2023/09/05 16:20, ""
DMR, 23, 23, 331, 50, Normal, 5, 2023/09/18 15:53, ""
DMR, 23, 23, 332, 50, Normal, 9, 2023/09/05 16:25, ""
DMR, 23, 23, 333, 50, Normal, 13, 2023/09/05 16:36, ""
DMR, 23, 23, 467, 50, Normal, 2, 2022/02/09 15:44, ""
DMR, 23, 23, 649, 50, Normal, 1, 2022/02/09 16:17, ""
DMR, 23, 23, 651, 50, Normal, 10, 2023/09/18 15:20, ""
DMR, 23, 23, 652, 50, Normal, 4, 2022/02/09 15:44, ""
DMR, 23, 23, 653, 50, Normal, 14, 2023/06/16 11:21, ""
DMR, 23, 23, 655, 50, Normal, 1, 2022/02/09 15:11, ""
DMR, 23, 23, 900, 50, Normal, 219, 2023/09/18 16:20, ""
DMR, 23, 23, 5010, 50, Normal, 1, 2023/09/18 15:20, ""

Now I've noticed that seemingly at random times, mostly when the frequency is inactive, like overnight or something the record at the bottom of the DSD screen will disappear. Forcing me to restart the frequency from the siteloader window. Most importantly when this happens the records inside the .groups and .radios files get messed up and instead of generating the fake System ID record they get thrown into the general DMR record mentioned above.

Has anyone had a setup like this before? Has anyone run into this issue? Does anyone have a better way to sort One Frequency DMR in DSD+ than the method above? Thanks.

 

[DaveNF2G]

It might help if the entries in .sites and .siteloader were the same.

 

[seagravebuff60]

It might help if the entries in .sites and .siteloader were the same.

They are, The only thing that's different is the alias. In my experience as long as the protocol, system ID, and site are there and the same, the alias doesn't matter.

 

[mcjones2013]

Why is 23 listed twice on the groups and radios lines?

 

[seagravebuff60]

Why is 23 listed twice on the groups and radios lines?

Thats Normal.
Because I have 23 as the System ID, if you check the other DSD+ entries in my post, you can see how I "coded" System ID 23. Im using a fake system ID Like P25 Conventional or Cap+ Systems use.

According to DSD+, the .groups file is formatted like this:
Line Format: protocol, networkID, group, priority, override, hits, timestamp, "group alias"
My Entry: DMR, 23, 23, 50, Normal, 76, 2023/09/18 16:35, "Busses"

According to DSD+, the .radios file is formatted like this:
Line Format: protocol, networkID, group, radio, priority, override, hits, timestamp, "radio alias"
My Entry: DMR, 23, 23, 12, 50, Normal, 2, 2023/09/18 16:11, ""

So, in my case, 23 is the (Fake) system ID and the group (TG). 23 is a fake system ID, but that shouldn't matter.

 

[mcjones2013]

Ok thanks. I’m not near my computer so I couldn’t remember the line format.

 

[cg]

Some random thoughts...
do you get any other traffic on the frequency? Perhaps a different digital or an analog transmission on the channel bumps the DMR and the info disappears. Does the Event Log show anything from last DMR traffic until you notice it is off?
Would using a scanlist with the target freq and a known dead channel allow it to keep refreshing every time the channel is active?
Adjacent channels could cause issues, I have a conventional P25 freq between 2 P25 control channels that requires me to disable the Auto center tuning (a). Also, a local trunk system that uses P25 voice channels in the business band keeps changing to DMR TierIII due to shared frequencies so I have to disable all other modes.

 

[seagravebuff60]

do you get any other traffic on the frequency? Perhaps a different digital or an analog transmission on the channel bumps the DMR and the info disappears.

I don't get anything else on that frequency, according to the logs.

Does the Event Log show anything from last DMR traffic until you notice it is off?

I would have to do some more logging for that, as it happens overnight, but ill let you know.

Would using a scanlist with the target freq and a known dead channel allow it to keep refreshing every time the channel is active?

I see what you are saying; I have had great success with the scanlist. I throw all of the DMR Channels in there, and each time one is active, it auto-tunes. But yeah, it does work to keep refreshing each channel. I just have never added a dead channel to help it refresh each time, I'll try that.

Adjacent channels could cause issues, I have a conventional P25 freq between 2 P25 control channels that requires me to disable the Auto center tuning (a). Also, a local trunk system that uses P25 voice channels in the business band keeps changing to DMR TierIII due to shared frequencies so I have to disable all other modes.

Ive never thought of disabling other modes; I'll have to try that out. Because of my range, sometimes I get all kinds of different things on one frequency.

 

[seagravebuff60]

Some random thoughts...
do you get any other traffic on the frequency? Perhaps a different digital or an analog transmission on the channel bumps the DMR and the info disappears. Does the Event Log show anything from last DMR traffic until you notice it is off?
Would using a scanlist with the target freq and a known dead channel allow it to keep refreshing every time the channel is active?
Adjacent channels could cause issues, I have a conventional P25 freq between 2 P25 control channels that requires me to disable the Auto center tuning (a). Also, a local trunk system that uses P25 voice channels in the business band keeps changing to DMR TierIII due to shared frequencies so I have to disable all other modes.

Just circling back, thaks for the recommendations, eveything is working.