DSDPlus Fastlane Transient Groups

[sunwave]

After joining the premium subscriber train I began updating my DSDPlus groups. This is not the issue.

What is the issue:
Seen these two pop up in DSDPlus.groups file (reference RRDB site 6949)

No site NAC. Why is it putting them there?

 

[Kazzaw]

Possibly a bad decode - I've noticed a couple times I can get a few odd records if I'm trying to decode a site just out of range which will cause weird TG's and Network ID's

 

[dave3825]

After joining the premium subscriber train I began updating my DSDPlus groups.

Seen these two pop up in DSDPlus.groups file (reference RRDB site 6949)

6949? That comes back to Oklahoma Wireless Interoperability Network (OKWIN) (P25) and does not reflect your screenshot.

Oklahoma Wireless Interoperability Network (OKWIN) (P25) Trunking System, Various, Oklahoma

Oklahoma Wireless Interoperability Network (OKWIN) (P25) Trunking System Profile

www.radioreference.com

10198 comes back to Oklahoma City Metro Public Safety and has tg's and system info that match your screen shot.

Oklahoma City Metro Public Safety Trunking System, Oklahoma City, Oklahoma

Oklahoma City Metro Public Safety Trunking System Profile

www.radioreference.com

Neither one of those tg's shown in your pic are listed on either system.

When updating the groups file with the confirmed talk group info from Radio Reference, DSDPlus will also auto generate entries when it sees and decodes something not already predefined in the file.

So at some point, DSDPlus decoded something and started populating the groups file. DSDPlus will not populate the alpha / text tag. (on p25). It could be a bad decode or tg's were detected on a freq that did not have a system id. Pretty common on conventional p25 freqs as seen below.

;

; DSD+ 2.395; group records
;
; this file is populated automatically by DSD+
;
; you can edit this file while DSD+ is running
;
; line format: protocol, networkID, group, priority, override, hits, timestamp, "group alias"
;
;
; protocols:
;
; ProVoice
; dPMR
; IDAS
; NEXEDGE48
; NEXEDGE96
; DMR
; TIII
; DCDM
; Cap+
; Con+
; XPT
; P25
; X2-TDMA

;

P25, 0, 1, 50, Normal, 4786, 2023/02/28 11:51, ""
P25, 0, 11, 50, Normal, 8, 2022/08/15 8:21, ""
P25, 0, 17, 50, Normal, 4, 2022/08/15 8:21, ""
P25, 0, 19, 50, Normal, 1, 2022/08/15 8:20, ""
P25, 0, 23, 50, Normal, 12, 2022/08/15 8:25, ""
P25, 0, 25, 50, Normal, 1, 2022/08/15 8:20, ""
P25, 0, 27, 50, Normal, 16, 2022/10/03 11:12, ""
P25, 0, 93, 50, Normal, 1, 2022/08/15 8:19, ""
P25, 0, 256, 50, Normal, 0, 0000/00/00 0:00, ""
P25, 0, 1685, 50, Normal, 0, 2022/06/14 0:52, ""
P25, 0, 2177, 50, Normal, 15, 2017/09/21 16:35, ""
P25, 0, 4095, 50, Normal, 733, 2017/09/22 8:01, ""
P25, 0, 4097, 50, Normal, 10, 2018/09/14 9:12, ""
P25, 0, 4649, 50, Normal, 0, 2022/06/14 0:53, ""
P25, 0, 5175, 50, Normal, 0, 2022/06/14 0:52, ""
P25, 0, 30420, 50, Normal, 0, 0000/00/00 0:00, ""
P25, 0, 30882, 50, Normal, 0, 0000/00/00 0:00, ""
P25, 0, 31319, 50, Normal, 0, 0000/00/00 0:00, ""
P25, 0, 34371, 50, Normal, 0, 2022/06/30 7:36, ""
P25, 0, 34860, 50, Normal, 0, 2022/06/30 7:36, ""

; Metro 25

P25, 91FE8.26D, 603, 50, Normal, 0, 0000/00/00 0:00, "[MTAPD Citywide]"
P25, 91FE8.26D, 604, 50, Normal, 0, 0000/00/00 0:00, "[MTAPD D1/2 Disp]"
P25, 91FE8.26D, 1001, 50, Normal, 0, 0000/00/00 0:00, "[Radio Techs]"
P25, 91FE8.26D, 1002, 50, Normal, 0, 0000/00/00 0:00, "[Radio Techs]"

No site NAC. Why is it putting them there?

The groups file do not contain site nac.

; DSD+ 2.395; group records
;
; this file is populated automatically by DSD+
;
; you can edit this file while DSD+ is running
;
; line format: protocol, networkID, group, priority, override, hits, timestamp, "group alias"

 

[Reconrider]

As @Kazzaw said, it's just bad decode.
It happens to us all. I have talkgroups on systems that are 0, and ask we know, it's not possible to have that

 

[dave3825]

As @Kazzaw said, it's just bad decode.
It happens to us all. I have talkgroups on systems that are 0, and ask we know, it's not possible to have that

While it may be a bad decode, that is not the only definitive answer and or explanation since DSDPlus will populate the groups file the same way when scanning P25 conventional freqs or when decoding a voice freq that's part of a trunked system.

When there is not a defined system id being broadcast on conventional, or DSDPlus does not pick it up on a voice freq, it will populate with a sys id of zero in the groups file. That does not definitively mean its a bad decode.

These are all entries generated by DSDPlus in my groups file.... Tg's 11, 17, 19, 23, 25, 27 and 93 are from my local trunked system voice freqs and the rest are from conventional P25 freqs.








I just parked on a local trs voice freq.

This is from the event file




This is the entry created in the groups file.




Notice that Tg 3803 got entered with sys id of 0?



Depending on what the OP's logging options are set to, tg's 635 and 807 should be in the DSDPlus.event file and may display the freq and nac where those tg's were picked up on.

 

[cg]

If you aren't running a single system/site 24/7, sometimes voice activity is seen upon startup before the program catches the SYSID. It will show them as SYSID 0.

 

[sunwave]

6949? That comes back to Oklahoma Wireless Interoperability Network (OKWIN) (P25) and does not reflect your screenshot.

The order in which the groups file was filled in I had started with groups in 6949, 10198 then 7985. I blanked out the entire groups file to start out fresh. Then added the groups file content from RRDB as I switched between systems in DSDPlus FL because it creates them with commented out names per what is in the networks file.

As for the entire thread I thank you! I now see that is is common for DSDPlus FL to start the groups file with SYSID 0 upon startup of the program kind of like it jumped the gun went straight to the bullet for a split second. I do not run it 24/7.

If you aren't running a single system/site 24/7, sometimes voice activity is seen upon startup before the program catches the SYSID. It will show them as SYSID 0.

It is working pretty good otherwise! Low RF gain because it is running the orange Flightaware dongle which has a hot LNA built in but no 1090MHz filter.