P25RX Firmware Updates / Testing

[epersson]

I found it. I believe this issue is fixed in version 12-09_0713.

Your diligence dedication and response is unheard of!!! I’d say keep it up but don’t want to jinx us. 😄. I’ll load it in a hour or so on both units

 

[epersson]

I found it. I believe this issue is fixed in version 12-09_0713.

Was it doing anything beyond a message?

 

[epersson]

I found it. I believe this issue is fixed in version 12-09_0713.

I put this on the two, one of them has a strange display now and not getting entries in the TG log
It only does this with P2 transmissions, the P1 systems screen looks normal and the entries are in the TG log.

rssi: -74 tsbk_ps 4 sa 1 ue 1 wacn_id 0xbee00 sys_id 0x997 nac 0x991 rf_id 1 site_id 1 freq 774.906250 rfg 38 agc -27.2 $
SYS_INFO wacn 0xbee00 sys_id 0x997 nac 0x991 nco_off $
$TDMA VOICE GRANT_02, freq 771.556250, tgroup: 11040, slot: 1***
****
P25_PII: SRC_RID: 112 GRP 11040 $******
**********
***
P25_PII: SRC_RID: 112 GRP 11040 $******
$TDMA_PTT talk group 11040, non-encrypted
P25_PII: SRC_RID: 7818727 GRP 11040 $*
**********
**
P25_PII: SRC_RID: 7818727 GRP 11040 $********
**********
**********
***
P25_PII: SRC_RID: 7818727 GRP 11040 $*******
**********
**********
**********
**********
*
P25_PII: SRC_RID: 7818727 GRP 11040 $****
logging -999
~$

The other is not roaming and looks normal even though it's the same P2 system. and is recording TG Entries.

P25_PII: SRC_RID: 110 GRP 12050 $*
TDMA Phase II sync, freq: 771.856250, rssi: -70 dBm, TGroup: 12050, Desc: PB BSO East, erate: 0.000 $***
**********
***
TDMA Phase II sync, freq: 771.856250, rssi: -71 dBm, TGroup: 12050, Desc: PB BSO East, erate: 0.000 $***********
TDMA Phase II sync, freq: 771.856250, rssi: -71 dBm, TGroup: 12050, Desc: PB BSO East, erate: 0.000 $
P25_PII: SRC_RID: 110 GRP 12050 $****
TDMA Phase II sync, freq: 771.856250, rssi: -70 dBm, TGroup: 12050, Desc: PB BSO East, erate: 0.000 $********
P25_PII: SRC_RID: 110 GRP 12050 $*********
TDMA Phase II sync, freq: 771.856250, rssi: -71 dBm, TGroup: 12050, Desc: PB BSO East, erate: 0.000 $*****

Audio seems to be excellent though, so just seems to be a logging display issue

 

[epersson]

@btt I was listening to traffic on p25p2 where they patched a channel, the sds100 was picking up the traffic, but the P25rx wasn't getting any of it. the TG was the one in my TG list. Once they killed the patch I got traffic on that TG again.

I think this worked before as this same channel was patched the last time the Helo was up and I was listening, I think it was on the p25... :-( .

 

[btt]

Was it doing anything beyond a message?

Yes, it was some logic that was messed up in a previous version on both the P25RX-II and the P25RX. I already had it fixed in the P25RX-II, so the fix for the P25RX would have found its way in there sooner or later. I don't think this change would have anything to do with the new problems you are having with patches.

 

[epersson]

Yes, it was some logic that was messed up in a previous version on both the P25RX-II and the P25RX. I already had it fixed in the P25RX-II, so the fix for the P25RX would have found its way in there in the next big release. I don't think this change would have anything to do with the new problems you are having with patches.

Not sure it matters, but the patch was between a P25 p1 system and a P2 system. I was listening to the P2 only.

 

[btt]

Not sure it matters, but the patch was between a P25 p1 system and a P2 system. I was listening to the P2 only.

When a grant for a patch is received, the only difference is that it is a different talk group id. As long as you have that id enabled, or you allow "unknown talkgroups", then it will be treated like any other talk group. It shouldn't matter if it is P1 or P2. Let me know if you continue to have issues with this. It might be difficult for me to track down until I get IQ file recording working for the P25RX. The local systems here don't do patches yet.

 

[epersson]

When a grant for a patch is received, the only difference is that it is a different talk group id. As long as you have that id enabled, or you allow "unknown talkgroups", then it will be treated like any other talk group. It shouldn't matter if it is P1 or P2. Let me know if you continue to have issues with this. It might be difficult for me to track down until I get IQ file recording working for the P25RX. The local systems here don't do patches yet.

On the sds the TG showed as the same one I had enabled in my p25rx TG list, and the second the patch was enabled the grants stopped, the second they said they were killing it the audio grants for that TG started appearing on the P25rx. During the patch time the other two channels were getting utilized and were working. I can't enable unknown as there are thousands of PD channels and I only want the 2 local ones. One of which was the patched TG.

 

[dcr_inc]

Patched TG's are assigned a "Super Group" ID which is different than the normal ID for the groups..And that ID will change depending on other patches in use

 

[btt]

On the sds the TG showed as the same one I had enabled in my p25rx TG list, and the second the patch was enabled the grants stopped, the second they said they were killing it the audio grants started appearing on the P25rx. During the patch time the other two channels were getting utilized and were working.

Do you have "allow unknown talk groups" on the P25RX enabled? During the patch time, the TG will be a "super group" with a different id. I don't know how the SDS100 handles it, but the P25RX does not currently keep track of what groups the "super group" is composed of. That may be why you are seeing something different for behavior. In other words, when a patched grant is received, multiple talk group ids are associated with a super-group id. The P25RX does not currently keep track of all this information. It only looks at the super-group id in the grant and treats that like any other grant.

 

[epersson]

Do you have "allow unknown talk groups" on the P25RX enabled? During the patch time, the TG will be a "super group" with a different id. I don't know how the SDS100 handles it, but the P25RX does not currently keep track of what groups the "super group" is composed of. That may be why you are seeing something different for behavior. In other words, when a patched grant is received, multiple talk group ids are associated with a super-group id. The P25RX does not currently keep track of all this information. It only looks at the super-group id in the grant and treats that like any other grant.
[/QUOTE
No I do not have unknown talkgroups enabled, there are hundreds of PD channels and only want 2. East and West. West was patched to the neighboring town. They have ended the helo monitoring so I cannot check now. I am pretty sure that last week there was another helo operation and I was listening to it. I don't remember which radio was getting it. On the sds it just showed the local West TG ID. I only program the same 2 channels in the SDS.

 

[btt]

I'll add that to the list of things to do. It probably should keep track of the sub-group ids and use that to determine if the super-group is enabled.

 

[epersson]

I'll add that to the list of things to do. It probably should keep track of the sub-group ids and use that to determine if the super-group is enabled.

I'll enable unknown, then go out and 'borrow' a car and cross city lines. they should send the bird after me, when I get out in 3-6 with good behavior I'll check the P25 to see what it shows. or maybe next time I hear it I will just enable and watch the log. It doesn't happen every day. ;-)

 

[btt]

Would a better idea be to always enable patched groups?

 

[epersson]

Would a better idea be to always enable patched groups?

Ok, we'll do it your way.

 

[btt]

Easy enough. 12-09_1316 should always pass patched talk groups (plus it will keep you out of trouble). I'll work on some other options later on. Seems like this would be a good default since a patched talk group implies something interesting happening.

 

[epersson]

Easy enough. 12-09_1316 should always pass patched talk groups (plus it will keep you out of trouble). I'll work on some other options later on. Seems like this would be a good default since a patched talk group implies something interesting happening.

I thank you, my wife.. that remains to be seen... Downloading and testing now.

 

[epersson]

This version hung up on the reset to reload. the P25 is flashing fast but no activity on the screen.
edit - shut app down it is progressing with the load. Console Display still strange and not all granted logged in TG log but up and running.

 

[btt]

This version hung up on the reset to reload. the P25 is flashing fast but no activity on the screen.
edit - shut app down it is progressing with the load. Console Display still strange and not all granted logged in TG log but up and running.

For the TG logging issue, I recommend pressing the "edit" button on the TG Log tab. Enable all the log triggers. See if that fixes it for you.

 

[epersson]

For the TG logging issue, I recommend pressing the "edit" button on the TG Log tab. Enable all the log triggers. See if that fixes it for you.

Nope... the screen logging changed with the previous version.



It looks like this, no TG Name and its formatted strange.
rssi: -75 tsbk_ps 53 sa 1 ue 1 wacn_id 0xbee00 sys_id 0x997 nac 0x991 rf_id 1 site_id 1 freq 774.906250 rfg 38 agc -33.5 $
SYS_INFO wacn 0xbee00 sys_id 0x997 nac 0x991 $
$TDMA VOICE GRANT_00, freq 772.856250, tgroup: 11012, slot: 1
$TDMA_PTT talk group 11012, non-encrypted
$TDMA_PTT talk group 11012, non-encrypted
P25_PII: SRC_RID: 7879030 GRP 11012 $****
***
P25_PII: SRC_RID: 7879030 GRP 11012 $*******
**********
**********
*******
P25_PII: SRC_RID: 7879030 GRP 11012 $***
**********
**********
*******
P25_PII: SRC_RID: 7879030 GRP 11012 $***
*********
$TDMA_PTT talk group 11012, non-encrypted
$TDMA_PTT talk group 11012, non-encrypted
P25_PII: SRC_RID: 113 GRP 11012 $*
**********
**********
***
P25_PII: SRC_RID: 113 GRP 11012 $*******
*********
***
P25_PII: SRC_RID: 113 GRP 11012 $*******
**********
*
P25_PII: SRC_RID: 113 GRP 11012 $********
**********
**********
***


Used to look like this and log entries.
rssi: -67 tsbk_ps 54 sa 1 ue 1 wacn_id 0xbee00 sys_id 0x997 nac 0x991 rf_id 1 site_id 1 freq 774.906250 rfg 38 agc -26.0 $
SYS_INFO wacn 0xbee00 sys_id 0x997 nac 0x991 $
$TDMA VOICE GRANT_00, freq 772.856250, tgroup: 12051, slot: 0
SYS_INFO wacn 0xbee00 sys_id 0x997 nac 0x991 $

==============================================================================================
grant (0x00) packet_idx 1, tgroup 12051 freq 772.8562 nac 2449 rf_channel 1736 follow: 0
desc: PB BSO West location:
control is switching to monitor grant for talkgroup on freq 772.856250
==============================================================================================
TDMA Phase II sync, freq: 772.856250, rssi: -68 dBm, TGroup: 12051, Desc: PB BSO West, erate: 0.000 $
$TDMA_PTT talk group 12051, non-encrypted
TDMA Phase II sync, freq: 772.856250, rssi: -68 dBm, TGroup: 12051, Desc: PB BSO West, erate: 0.000 $
$TDMA_PTT talk group 12051, non-encrypted
P25_PII: SRC_RID: 7810733 GRP 12051 $*****
****
TDMA Phase II sync, freq: 772.856250, rssi: -68 dBm, TGroup: 12051, Desc: PB BSO West, erate: 0.000 $***
P25_PII: SRC_RID: 7810733 GRP 12051 $***
*******
TDMA Phase II sync, freq: 772.856250, rssi: -67 dBm, TGroup: 12051, Desc: PB BSO West, erate: 0.000 $**
***
P25_PII: SRC_RID: 7810733 GRP 12051 $*******
***
TDMA Phase II sync, freq: 772.856250, rssi: -67 dBm, TGroup: 12051, Desc: PB BSO West, erate: 0.000 $*******
**
P25_PII: SRC_RID: 7810733 GRP 12051 $***