P25RX Firmware Updates / Testing

[epersson]

This is the same group on two different boxes both with the latest FW. The only difference is one is roaming one not.

Roaming:

rssi: -82 tsbk_ps 0 sa 1 ue 1 wacn_id 0xbee00 sys_id 0x997 nac 0x991 rf_id 1 site_id 1 freq 774.906250 rfg 38 agc -30.4 $
P25_AFFILIATION: 774.906250, 11000,7905040 $
SYS_INFO wacn 0xbee00 sys_id 0x997 nac 0x991 nco_off $
$TDMA VOICE GRANT_02, freq 772.856250, tgroup: 11012, slot: 0
control is switching to monitor grant for talkgroup on freq 772.856250
==============================================================================================*****
***
P25_PII: SRC_RID: 113 GRP 11012 $******
**********
*
P25_PII: SRC_RID: 113 GRP 11012 $*********
*******
P25_PII: SRC_RID: 7903247 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: 7903247 GRP 11012 $*********
*********
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: 7903247 GRP 11012 $****
*********
**********



Non Roaming system:

ssi: -68 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 -24.2 $
SYS_INFO wacn 0xbee00 sys_id 0x997 nac 0x991 $
$TDMA VOICE GRANT_00, freq 771.556250, tgroup: 11012, slot: 1
SYS_INFO wacn 0xbee00 sys_id 0x997 nac 0x991 $

==============================================================================================
grant (0x00) packet_idx 2, tgroup 11012 freq 771.5562 nac 2449 rf_channel 1529 follow: 0
desc: PB Fire Dispatch location:
control is switching to monitor grant for talkgroup on freq 771.556250
==============================================================================================
TDMA Phase II sync, freq: 771.556250, rssi: -67 dBm, TGroup: 11012, Desc: PB Fire Dispatch, erate: 0.000 $
$TDMA_PTT talk group 11012, non-encrypted
$TDMA_PTT talk group 11012, non-encrypted
P25_PII: SRC_RID: 113 GRP 11012 $***
TDMA Phase II sync, freq: 771.556250, rssi: -69 dBm, TGroup: 11012, Desc: PB Fire Dispatch, erate: 0.000 $*****
P25_PII: SRC_RID: 113 GRP 11012 $*

 

[goldmyne99]

During the patch time, the TG will be a "super group" with a different id.

An observation on patched TGs on my main P25 Phase One system.
I have not had any issues.
The supergroup ID has always been one of the patched sub group TG ids.
This example TG 58914 and TG 58915 are patched today.
The supergroup ID is 58914.

patched grant (0x02) packet_idx 2, supergroup 58914 freq 852.6125 nac 1681

Perhaps unique to this system.

 

[btt]

I think dispatch determines the super-group id, but I'm not 100% sure about that.

 

[vince48]

Todd,
Season Greetings, Can P25 decode MPT-1327 ?

 

[btt]

Seasons greetings Vince! No, it can't do that yet.

 

[dispatchgeek]

Sadly, the patches on my system just means that a few of our agencies will get around to adding the new talkgroups in their radios, someday. I’ve had a handful of “temporary patches” up for years now…

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.

 

[vince48]

Seasons greetings Vince! No, it can't do that yet.

ok, Thanks Todd. Relax and have a pleasant Holiday!

 

[dcr_inc]

Todd,
The system assigns the Super Group ID.. The dispatcher selects the talkgroups for the super group.

 

[btt]

Todd,
The system assigns the Super Group ID.. The dispatcher selects the talkgroups for the super group.

Thank you sir! I understand how it works now.

 

[dispatchgeek]

What he said. Many trunking systems feature dispatch consoles that tie directly into the trunking system. The direct connected consoles have the ability to make system level changes (such as the supergroup patch.) This is far superior to pass through patch days of old. The dispatcher isn’t usually the wiser and doesn’t have to be. The process is intuitive and seamless. The flip side is depending on how the subscriber radio is programmed, some of these system level actions can have unintended consequences.

Todd,
The system assigns the Super Group ID.. The dispatcher selects the talkgroups for the super group.

 

[epersson]

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

Hi, Sorry... ;-(
Besides the new strange console formatted messages, I think with my uncalibrated ear that the audio is a very slight bit more choppy with this release than the versions I was running previously 702 was one of them. every now and then there are short burps in the conversations.
You can hear it here:

Broadcastify

The worlds largest source of public safety, aircraft, rail, and marine live audio streams

www.broadcastify.com

 

[maus92]

What he said. Many trunking systems feature dispatch consoles that tie directly into the trunking system. The direct connected consoles have the ability to make system level changes (such as the supergroup patch.) This is far superior to pass through patch days of old. The dispatcher isn’t usually the wiser and doesn’t have to be. The process is intuitive and seamless. The flip side is depending on how the subscriber radio is programmed, some of these system level actions can have unintended consequences.

I beleive this is what happens on the JNCR system in the DC area. There are a set of 4 Supergroups in the 94xx range that get patched to several tgs each for the various bases and facilities in the area. The Supergroups can change daily, but the patched tgs are always the same. Harris system btw.

 

[turnpike61]

New update not working for me. I was able to get it loaded by restarting the P25RX in the middle of the process, but it logged a single call, no audio, and locked up. Am back on 20211116:2326 which has been working very well.

 

[raetex]

The latest update BT-Config-2021-12-09 1316 causes the same issues as @turnpike61 on 2 different computers. I have deleted the software, reinstalled, used the $factory command and still unable to overcome the issue. I also erased all entries and started with blank db and talkgroups and still no luck. In full screen mode, the bottom portion of the display is moves up/down. I am also experiencing the same problem when I revert to the last stable issue, which was working ok. All had been working ok until the update. Thanks. Robert

 

[btt]

The only changes since 11-16_2326 are the changes made recently for epersson. This is the bug fix for P2 encryption and the change to always enable patched talk groups. There were some other changes to the java software that were Mac related. 12-09_1316 is working well on Linux. I will do some Windows testing. In the mean time, I will revert the web site back to 11-16_2326.

 

[dcr_inc]

Latest is working good here on PI and PII.. Win 10

 

[turnpike61]

Latest is working good here on PI and PII.. Win 10

Win11 this end. Perhaps the problem.

 

[raetex]

Win11 this end. Perhaps the problem.

Win 10 here.

 

[epersson]

Win 10 here.

Win10 here as well.

 

[epersson]

The only firmware changes since 11-16_2326 are the changes made recently for epersson. This is the bug fix for P2 encryption and the change to always enable patched talk groups. There were some other changes to the java software that were Mac related. 12-09_1316 is working well on Linux. I will do some Windows testing. In the mean time, I will revert the web site back to 11-16_2326.

Hi. The logging changed. But only on some grant console displays. And i do think the audio is a very slight bit chopped. Very small gaps it’s not worth down reving because I don’t look at the console and the audio is plenty good enough for over broadcastify.