DSD+ and CC following Using the proper Slot rather than both slots

[jkraemer]

When using DSD+ ( latest Fastlane version). Cap+ and Con+ do not distinguish a distinct SLOT # when using a CC decoder with a VC decoder. Both slots are opened. Can this be addressed in future releases of DSD+?

 

[natedawg1604]

Can you post a screenshot? I'm pretty sure you should see a slot number in the VC channel activity window, along with the terminal log output (if you start DSD+ with the -v flag). I'm not sure what you mean by "both slots are opened", seeing a screenshot would be helpful.

 

[jkraemer]

This is not a display issue. When DSD+ is decoding any DMR signal there is an option to press 1 for the 1st slot, 2 for the second slot, 3 is both slots. Decode for both slots is the default. What I would like to see is an automatic option where the appropriate individual slot is decoded only. This is to eliminate a second conversation being decoded on top of the wanted transmission. Right now manually pressing 1 or 2 will set the proper slot for decoding but there is no automatic option in DSD+ for this.

 

[natedawg1604]

This is not a display issue. When DSD+ is decoding any DMR signal there is an option to press 1 for the 1st slot, 2 for the second slot, 3 is both slots. Decode for both slots is the default. What I would like to see is an automatic option where the appropriate individual slot is decoded only. This is to eliminate a second conversation being decoded on top of the wanted transmission. Right now manually pressing 1 or 2 will set the proper slot for decoding but there is no automatic option in DSD+ for this.

Well you can already hold on a single talkgroup with the spacebar key. Just hit the spacebar when the talkgroup of interest is active and you'll see the talkgroup light-up in the cc activity window, confirming you're holding on that talkgroup. Does that make sense?

You can also set different priority levels and colors for individual talkgroups, which makes the above process even easier.

 

[slicerwizard]

This is not a display issue. When DSD+ is decoding any DMR signal there is an option to press 1 for the 1st slot, 2 for the second slot, 3 is both slots. Decode for both slots is the default. What I would like to see is an automatic option where the appropriate individual slot is decoded only. This is to eliminate a second conversation being decoded on top of the wanted transmission. Right now manually pressing 1 or 2 will set the proper slot for decoding but there is no automatic option in DSD+ for this.

What is the "appropriate individual slot"?

When running a full trunking setup (two FMP24 and two DSD+), the control channel copy of DSD+ doesn't decode any voice traffic, only the voice copy does, and that copy only decodes one talkgroup at a time, based on group priorities that you control.

I just tried this and CC DSD+ auto muted when it was hearing a control/rest channel. There was never any doubling, even when the other timeslot of the CC frequency was carrying a voice call. When I tuned CC FMP24 to a non-trunked channel, it auto unmuted (so I could hear any conventional digital voice traffic)


CC DSD+ event log:

2016/09/27 19:15:14 Freq=770.000000 DSD+ 2.18 / Fast Lane Release
2016/09/27 19:15:14 Freq=770.000000 [Andrew Porrett wap@ica.net]
2016/09/27 19:15:14 Freq=770.000000 D-STAR decoding enabled
2016/09/27 19:15:14 Freq=770.000000 NXDN4800 decoding enabled
2016/09/27 19:15:14 Freq=770.000000 NXDN9600 decoding enabled
2016/09/27 19:15:14 Freq=770.000000 DMR/MotoTRBO decoding enabled
2016/09/27 19:15:14 Freq=770.000000 P25 Phase 1 decoding enabled
2016/09/27 19:15:14 Freq=770.000000 X2-TDMA decoding enabled
2016/09/27 19:15:14 Freq=770.000000 ProVoice decoding enabled
2016/09/27 19:15:30 Freq=463.325000 Current network: 171 SaiaNet
2016/09/27 19:15:30 Freq=463.325000 Current site: 171-17 Colden
2016/09/27 19:15:30 Freq=463.325000 DCC=7 171-17 neighbor: Site 171-1 South Buffalo
2016/09/27 19:15:30 Freq=463.325000 DCC=7 171-17 neighbor: Site 171-2 Attica
2016/09/27 19:15:30 Freq=463.325000 DCC=7 171-17 neighbor: Site 171-3 Perrrysburg
2016/09/27 19:15:30 Freq=463.325000 DCC=7 171-17 neighbor: Site 171-11
2016/09/27 19:15:30 Freq=463.325000 DCC=7 171-17 neighbor: Site 171-24
2016/09/27 19:15:37 Freq=463.325000 DCC=7 Group call; TG=503206 RID=5032043 Ch=2 6s
2016/09/27 19:15:37 Freq=463.325000 DCC=7 Auto disabling audio synthesis
2016/09/27 19:15:45 Freq=463.325000 DCC=7 Group call; TG=503206 RID=5032043 Ch=2
2016/09/27 19:15:49 Freq=463.325000 DCC=7 Group call; TG=503206 RID=5032043 Ch=2 7s
2016/09/27 19:15:57 Freq=463.325000 DCC=7 Group call; TG=503206 RID=5032043 Ch=5 2s
2016/09/27 19:16:01 Freq=463.325000 DCC=7 Group call; TG=503206 RID=5032043 Ch=5 4s
2016/09/27 19:17:12 Freq=463.325000 DCC=7 Auto enabling audio synthesis
2016/09/27 19:17:14 Freq=463.375000 DCC=7 463.375 94.5 km MAPLE LEAF FOODS I HAMILTON (IN-PLANT) 11K0F3EJN 11K0F2DXN
2016/09/27 19:17:14 Freq=463.375000 Group call; TG=500901 RID=5009014 Ch=4 5s
2016/09/27 19:17:14 Freq=463.375000 Current network: 171 SaiaNet
2016/09/27 19:17:14 Freq=463.375000 Current site: 171-15 Olcott
2016/09/27 19:17:15 Freq=463.375000 DCC=15 171-15 neighbor: Site 171-2 Attica
2016/09/27 19:17:15 Freq=463.375000 DCC=15 171-15 neighbor: Site 171-4 North Buffalo
2016/09/27 19:17:15 Freq=463.375000 DCC=15 171-15 neighbor: Site 171-8 Lewiston
2016/09/27 19:17:15 Freq=463.375000 DCC=15 171-15 neighbor: Site 171-10 Lancaster
2016/09/27 19:17:15 Freq=463.375000 DCC=15 171-15 neighbor: Site 171-16 Rochester
2016/09/27 19:17:16 Freq=463.375000 DCC=15 Auto disabling audio synthesis
2016/09/27 19:17:20 Freq=463.375000 DCC=15 Group call; TG=500901 RID=5009011 Ch=4 3s
2016/09/27 19:17:27 Freq=463.375000 DCC=15 Group call; TG=500901 RID=5009014 Ch=4
2016/09/27 19:17:47 Freq=463.375000 DCC=15 Auto enabling audio synthesis
2016/09/27 19:17:47 Freq=463.662500 Current network: 158 Fleet Connect
2016/09/27 19:17:47 Freq=463.662500 Current site: 158-13 King City
2016/09/27 19:17:47 Freq=463.662500 DCC=1 158-13 neighbor: Site 158-10 Milton
2016/09/27 19:17:47 Freq=463.662500 DCC=1 158-13 neighbor: Site 158-11 Hamilton
2016/09/27 19:17:47 Freq=463.662500 DCC=1 158-13 neighbor: Site 158-12 Toronto
2016/09/27 19:17:47 Freq=463.662500 DCC=1 158-13 neighbor: Site 158-14 Blackstock (Raglan Pit)
2016/09/27 19:17:47 Freq=463.662500 DCC=1 158-13 neighbor: Site 158-15 Wilmot

 

[jkraemer]

What is the "appropriate individual slot"?

Monitoring the Guelph City Services system using FMP24/DSD as CC and a second FRMP24/DSD+ as VC.
The rest channel is currently Ch9 (repeater 5th site so it's 5th system slot 1). A TG activates and the VC becomes live. The rest channel moves to CH 10 (second slot of the 5th repeater system) Despite the fact that a different TG actives but is set as L/O in DSD+ that voice path is opened despite the L/O on the 2nd slot of the same repeater, There's no distinction that second slot should be muted or disabled while the TG is active on Channel 9 and maintained in that mode until the repeater releases both slots.

 

[slicerwizard]

So you're saying that VC DSD+ synthesizes the voice on slots 9 and 10? I don't think I've ever seen a DSD+ trunking setup do that. Most of the Cap+ systems around here aren't very busy, so getting simultaneous calls on the same repeater is rare, but not unheard of, yet I can't recall hearing two simultaneous calls.

Definitely not seeing that behaviour on Con+ systems and some of them manage to get busy during the day.

Only thing that comes to mind is are you running a normal trunking setup? An FMP24 - DSD+ pair and both of them are running in CC mode? And a second FMP24 - DSD+ pair and both of them are running in VC mode? Simultaneous voice sounds like something in the second pair isn't running in VC mode.

 

[DaveNF2G]

The trunking commands cause DSD+ to behave in a particular way. It will synthesize audio for two slots in non-trunking mode and send one left and the other right. In trunking mode, it synthesizes audio for the selected talkgroup.