Pro96Com Behavior On Astro 7.16 System

[wa3ysu]

I have been monitoring a very large 700 MHz Motorola P25 phase 2 system since it was first turned on. Pro96com has worked excellent the past 2 years on this Astro 7.14 system, but after a recent system upgrade to Astro 7.16, I am seeing unusual behavior by the program.

Specifically, the control channel, after the Astro 7.16 upgrade, now incrementally updates the number of 'hits' several times a second. So where the control channel on version 7.14 was a constant indication and not increasing the number of 'hits', the new 7.16 system shows tens of thousands of hits each day.

I am assuming this is directly related to the change from 7.14 to 7.16, since I have not made any other changes to the monitoring setup.

Thoughts??

 

[mikey60]

Can you provide a control channel dump of the system and send it to me at mike@psredit.com?

Mike

 

[GTR8000]

Starting with ASTRO System Release 7.16, systems will now broadcast a BSI on the control channel nearly continuously. This accounts for the "hits" you're seeing.

 

[slicerwizard]

They definitely do not. A BSI is an audible Morse identifier sent on a traffic channel. A control channel sends control channel data (TSDUs and optionally, some PDUs) 100% of the time. There is no opportunity to send a BSI on a control channel frequency.

These systems are announcing that the control channel is sending BSIs, when of course it actually is not.

2017.01.08 22:27:37                                    RFSS_STS_BCST        SysID=1AC LRA=0 RFSS=1 Site=1 CC=410.2125 SC=60
2017.01.08 22:27:37  Sync:+P25p1 NAC:1A1 TSDU          MOT_PATCH_ANN        Supergroup=402  Subgroups=405 / 401
2017.01.08 22:27:37  Sync:+P25p1 NAC:1A1 TSDU          IDEN_UP_TDMA         ID=0 Base=380.0125 Offset=+5 Spacing=25 BW=12.5 Slots=2
2017.01.08 22:27:37                                    SCCB                 RFSS=1 Site=1 [ch=411.2875 SSC=04] [ch=412.2875 SSC=04]
2017.01.08 22:27:37                                    MOT_PATCH_ANN        Supergroup=204  Subgroup=251
2017.01.08 22:27:37  Sync:+P25p1 NAC:1A1 TSDU          MOT_PATCH_ANN        Supergroup=240  Subgroups=201 / 241
2017.01.08 22:27:37                                    ADJ_STS_BCST         CFVA=3 SysID=1AC LRA=0 RFSS=1 Site=2 CC=410.5375 SC=70
2017.01.08 22:27:37                                    SYNC_BCST            US=0 IST=1 MMU=0 MC=0 VL=0  LTO=-5h  2017/01/09 03:27 uSlot=4970
2017.01.08 22:27:37  Sync:+P25p1 NAC:1A1 TSDU          NET_STS_BCST         WACN ID=BEE00 SysID=1AC LRA=0 CC=410.2125 SC=60
2017.01.08 22:27:37                                    MOT_BSI_GRANT        Null BSI  ch=410.2125
2017.01.08 22:27:37                                    MOT_PATCH_ANN        Supergroup=256  Subgroup=205
2017.01.08 22:27:37  Sync:+P25p1 NAC:1A1 TSDU          MOT_PATCH_ANN        Supergroup=243  Subgroup=244
2017.01.08 22:27:37                                    MOT_PATCH_ANN        Supergroup=254  Subgroup=208
2017.01.08 22:27:37                                    MOT_PATCH_ANN        Supergroup=108  Subgroup=102
2017.01.08 22:27:37  Sync:+P25p1 NAC:1A1 TSDU          MOT_PATCH_ANN        Supergroup=103  Subgroup=104
2017.01.08 22:27:37                                    RFSS_STS_BCST        SysID=1AC LRA=0 RFSS=1 Site=1 CC=410.2125 SC=60
2017.01.08 22:27:37                                    MOT_PATCH_ANN        Supergroup=209  Subgroup=253
2017.01.08 22:27:37                                    IDEN_UP_VU           ID=2 Base=380 Offset=+5 Spacing=12.5 BW=12.5
2017.01.08 22:27:37  Sync:+P25p1 NAC:1A1 TSDU          SCCB                 RFSS=1 Site=1 [ch=412.2875 SSC=04] [ch=411.5625 SSC=04]
2017.01.08 22:27:37                                    MOT_PATCH_ANN        Supergroup=252
2017.01.08 22:27:37                                    MOT_PATCH_ANN        Supergroup=255  Subgroup=207
2017.01.08 22:27:37  Sync:+P25p1 NAC:1A1 TSDU          ADJ_STS_BCST         CFVA=3 SysID=1AC LRA=0 RFSS=1 Site=5 CC=410.5375 SC=70
2017.01.08 22:27:38                                    SYNC_BCST            US=0 IST=1 MMU=0 MC=0 VL=0  LTO=-5h  2017/01/09 03:27 uSlot=5030
2017.01.08 22:27:38                                    NET_STS_BCST         WACN ID=BEE00 SysID=1AC LRA=0 CC=410.2125 SC=60
2017.01.08 22:27:38  Sync:+P25p1 NAC:1A1 TSDU          MOT_PATCH_ANN        Supergroup=203  Subgroup=250
2017.01.08 22:27:38                                    MOT_PATCH_ANN        Supergroup=402  Subgroups=405 / 401
2017.01.08 22:27:38                                    MOT_PATCH_ANN        Supergroup=204  Subgroup=251
2017.01.08 22:27:38  Sync:+P25p1 NAC:1A1 TSDU          MOT_PATCH_ANN        Supergroup=240  Subgroups=201 / 241
2017.01.08 22:27:38                                    MOT_PATCH_ANN        Supergroup=256  Subgroup=205
2017.01.08 22:27:38                                    RFSS_STS_BCST        SysID=1AC LRA=0 RFSS=1 Site=1 CC=410.2125 SC=60
2017.01.08 22:27:38  Sync:+P25p1 NAC:1A1 TSDU          MOT_PATCH_ANN        Supergroup=243  Subgroup=244
2017.01.08 22:27:38  Sync:+P25p1 NAC:1A1 TSDU          IDEN_UP_TDMA         ID=0 Base=380.0125 Offset=+5 Spacing=25 BW=12.5 Slots=2
2017.01.08 22:27:38                                    MOT_BSI_GRANT        Null BSI  ch=410.2125

 

[GTR8000]

Yes, thank you for the technical clarification, but you knew what I meant. It's called a "Digital BSI" by Motorola. Obviously there is no analog Morse ID being transmitted over the control channel. :roll:

The point is that the system now broadcasts the BSI OSP over the control channel nearly continuously as a form of "Digital ID" for the system.

 

[mikey60]

Ok, now I see what's going on. I've been decoding these messages for a long time, but they've never used the control channel as the channel id.

 

[slicerwizard]

The point is that the system now broadcasts the BSI OSP over the control channel nearly continuously as a form of "Digital ID" for the system.

Around here, those frequent broadcasts contain no ID, so it's not even a "Digital ID".

 

[mikey60]

Try this version and let me know if it resolves the issue.

http://www.psredit.com/beta/Pro96Com-1.11.6.zip

I haven't checked to see if the MPSCS in Michigan is up on 7.16 yet so I haven't been able to test the change.

Mike

 

[rbrtklamp2]

fixed my problems

Mikey 60 1.11.6 completely solved the issue for me on the Starcom21 system in IL. I no longer have the control channel jumping back and forth between control and ID just a steady control channel. Thank you for the timely fix, I appreciate all the work you put into Pro96Com I use it everyday.

Thanks again for your continued support of p96c it is very much appreciated,
Bob

 

[mikey60]

Thanks for the confirmation.

Mike

 

[wa3ysu]

FIXED! Thanks a million for the quick update!!

 

[WyoWabbit]

Recently I noticed that the WyoLink system site 243 (TALL GRASS 800) was doing the same thing with the control channel. I started using Pro96Com 1.11.6 and it started working properly. However, once in a while, the control channel will show up as having a transmission on it with no callsign.

"Timestamp","Type","Channel","Frequency","TG ID","TalkGroup Description","Radio ID","Radio Description"
"02/27 11:48:49","Station ID","00-0877","856.48750","","","",""
"02/27 11:51:38","Group (Enc)","00-0717","855.48750","14115","[+13DPDENC ]E","11340011","13 :MS-226 :-"
"02/27 11:51:42","Group (Enc)","00-0717","855.48750","14115","[+13DPDENC ]E","11399003","13DPD ISPATCH :-"
"02/27 11:53:22","Group","00-0757","855.73750","14106","[+13GPD ]C","11310073","13CCAS :MS-63 :-"
"02/27 11:53:25","Group","00-0757","855.73750","14106","[+13GPD ]C","11399501","13GPD ISPATCH :-"
"02/27 11:53:27","Group","00-0757","855.73750","14106","[+13GPD ]C","11310073","13CCAS :MS-63 :-"
"02/27 11:53:33","Group","00-0757","855.73750","14106","[+13GPD ]C","11399501","13GPD ISPATCH :-"
"02/27 11:53:59","Station ID","00-0677","855.23750","","WQVU425","",""
"02/27 11:56:06","Group (Enc)","00-0717","855.48750","14115","[+13DPDENC ]E","11320061","13DPD : :-"
"02/27 11:56:11","Group (Enc)","00-0717","855.48750","14115","[+13DPDENC ]E","11399003","13DPD ISPATCH :-"

As you can see at 02/27 11:48:49, the control channel (856.4875) showed a transmission, then at 02/27 11:53:59, the normal ID transmitted on 855.2375 with the callsign. - Tom

 

[mikey60]

Recently I noticed that the WyoLink system site 243 (TALL GRASS 800) was doing the same thing with the control channel. I started using Pro96Com 1.11.6 and it started working properly. However, once in a while, the control channel will show up as having a transmission on it with no callsign.

"Timestamp","Type","Channel","Frequency","TG ID","TalkGroup Description","Radio ID","Radio Description"
"02/27 11:48:49","Station ID","00-0877","856.48750","","","",""

As you can see at 02/27 11:48:49, the control channel (856.4875) showed a transmission, then at 02/27 11:53:59, the normal ID transmitted on 855.2375 with the callsign. - Tom

That's part of what changed with the latest 7.16 update. The control channel now sends the Station ID message on a regular basis. In most cases it sets the channel to the control channel (which was what was confusing Pro96Com). Pro96Com now attempts to ignore the messages that set the control channel as the ID frequency. I need to look at the filter again to see why some are slipping through like this.

Mike