P25RX Firmware Updates / Testing

[pdhall54]

New version available 2021-04-10_0908. This version no longer temporarily disables talk groups when encryption is detected. The audio should mute if configured that way, but will continue to receive the encrypted communications instead of returning to the control channel. This should work the same way for phase 1 and 2. There isn't much going on here with encrypted, so it isn't tested yet. The "auto disable encrypted" option in the talk group tab should still work, but has not been verified. The talk group log should show (ENC) for talk groups with encryption.

Running 0908 on a P1 TRS that is 100% encrypted. Disabled "Encrypted Audio Output" :

1. Hear short burst of encrypted audio and yellow TG goes blank, audio is muted.
2. Console indicates still receiving but adds text (see below)

==============================================================================================
grant (0x00) packet_idx 1, tgroup 10905 freq 852.9625 nac 624 rf_channel 313 follow: 0
desc: TGRP 10905 location: Unidentified Usage
control is switching to monitor grant for talkgroup on freq 852.962500
==============================================================================================,vql, $
->(VOICE), freq: 852.962500, rssi: -101 dBm, TGroup: 10905, Desc: TGRP 10905, Time: 213 rfg 38, agc -55.9 $ *********
P25_P1: SRC_RID: 0 $ GRP: 10905,vqg, $
->(VOICE), freq: 852.962500, rssi: -101 dBm, TGroup: 10905, Desc: TGRP 10905, Time: 255 rfg 38, agc -58.1 $ *********,vqg, $
->(VOICE), freq: 852.962500, rssi: -102 dBm, TGroup: 10905, Desc: TGRP 10905, Time: 312 rfg 38, agc -58.7 $ *********,vqg, $
->(VOICE), freq: 852.962500, rssi: -103 dBm, TGroup: 10905, Desc: TGRP 10905, Time: 376 rfg 38, agc -57.7 $ ******************,vqg, $
->(VOICE), freq: 852.962500, rssi: -104 dBm, TGroup: 10905, Desc: TGRP 10905, Time: 508 rfg 38, agc -56.3 $ *****
ENCRYPTED talkgroup 10905 , ess_algid: 0xa2, Unknown Encryption Alg, ****,vqg, $
->(VOICE), freq: 852.962500, rssi: -103 dBm, TGroup: 10905, Desc: TGRP 10905, Time: 564 rfg 38, agc -56.0 $ *********
P25_P1: SRC_RID: 2210377 $ GRP: 10905,vqg, $
->(VOICE), freq: 852.962500, rssi: -103 dBm, TGroup: 10905, Desc: TGRP 10905, Time: 621 rfg 38, agc -55.6 $ *****
ENCRYPTED talkgroup 10905 , ess_algid: 0xa2, Unknown Encryption Alg, *************,vqg, $
->(VOICE), freq: 852.962500, rssi: -102 dBm, TGroup: 10905, Desc: TGRP 10905, Time: 743 rfg 38, agc -55.5 $ *****
ENCRYPTED talkgroup 10905 , ess_algid: 0xa2, Unknown Encryption Alg, ****,vqg, $
->(VOICE), freq: 852.962500, rssi: -102 dBm, TGroup: 10905, Desc: TGRP 10905, Time: 801 rfg 38, agc -55.3 $ *********
P25_P1: SRC_RID: 2210377 $ GRP: 10905,vqg, $
->(VOICE), freq: 852.962500, rssi: -102 dBm, TGroup: 10905, Desc: TGRP 10905, Time: 862 rfg 38, agc -55.2 $ *****
ENCRYPTED talkgroup 10905 , ess_algid: 0xa2, Unknown Encryption Alg, ****,vqg, $
->(VOICE), freq: 852.962500, rssi: -102 dBm, TGroup: 10905, Desc: TGRP 10905, Time: 911 rfg 38, agc -55.6 $ ********,vqb, $
->(VOICE), freq: 852.962500, rssi: -102 dBm, TGroup: 10905, Desc: TGRP 10905, Time: 978 rfg 38, agc -57.8 $ *****
ENCRYPTED talkgroup 10905 , ess_algid: 0x82, Unknown Encryption Alg, ****,vqg, $
->(VOICE), freq: 852.962500, rssi: -102 dBm, TGroup: 10905, Desc: TGRP 10905, Time: 1042 rfg 38, agc -57.1 $ *********
P25_P1: SRC_RID: 2210377 $ GRP: 10905,vqg, $
->(VOICE), freq: 852.962500, rssi: -102 dBm, TGroup: 10905, Desc: TGRP 10905, Time: 1105 rfg 38, agc -55.1 $ *****
ENCRYPTED talkgroup 10905 , ess_algid: 0xa2, Unknown Encryption Alg, *************
P25_P1: SRC_RID: 0 $ GRP: 10905,vqg, $
->(VOICE), freq: 852.962500, rssi: -101 dBm, TGroup: 10905, Desc: TGRP 10905, Time: 1663 rfg 38, agc -55.9 $ *****
ENCRYPTED talkgroup 10905 , ess_algid: 0xa2, Unknown Encryption Alg, ****,vqg, $
->(VOICE), freq: 852.962500, rssi: -102 dBm, TGroup: 10905, Desc: TGRP 10905, Time: 1709 rfg 38, agc -55.7 $ *********,vqg, $
->(VOICE), freq: 852.962500, rssi: -102 dBm, TGroup: 10905, Desc: TGRP 10905, Time: 1769 rfg 38, agc -55.9 $ *****
ENCRYPTED talkgroup 10905 , ess_algid: 0xa2, Unknown Encryption Alg, ****,vqg, $
->(VOICE), freq: 852.962500, rssi: -98 dBm, TGroup: 10905, Desc: TGRP 10905, Time: 2740 rfg 38, agc -51.2 $ *
link-control end call received.
>== TDULC - Return To Control Channel Frequency 855.487500, rssi -98 ==<

While testing I enabled "AUTO DISABLE ENCRYPTED" and it appears to be auto adding Talk Groups:

false	0x27a	1	10937	10937_encrypted	unknown	0xbee00
false	0x27a	1	10915	10915_encrypted	unknown	0xbee00
false	0x27a	1	11225	11225_encrypted	NORCROSS,GA_GWINNETT_COUNTY_GOVE	0xbee00
false	0x27a	1	10203	10203_encrypted	DULUTH,GA_GWINNETT_COUNTY_GOVERN	0xbee00
false	0x27a	1	11061	11061_encrypted	unknown	0xbee00
false	0x27a	1	10629	10629_encrypted	unknown	0xbee00
false	0x27a	1	10617	10617_encrypted	unknown	0xbee00
false	0x27a	1	11063	11063_encrypted	unknown	0xbee00
false	0x27a	1	11003	11003_encrypted	unknown	0xbee00
false	0x27a	1	10621	10621_encrypted	unknown	0xbee00
true	0x27a	1	11223	11223_unknown	unknown	0xbee00
false	0x27a	1	10911	10911_encrypted	unknown	0xbee00
false	0x27a	1	11005	11005_encrypted	unknown	0xbee00

 

[kruser]

New version available 2021-04-10_0908. This version no longer temporarily disables talk groups when encryption is detected. The audio should mute if configured that way, but will continue to receive the encrypted communications instead of returning to the control channel. This should work the same way for phase 1 and 2. There isn't much going on here with encrypted, so it isn't tested yet. The "auto disable encrypted" option in the talk group tab should still work, but has not been verified. The talk group log should show (ENC) for talk groups with encryption.

So far this works great Todd!
I've also not tested the auto disable feature but it is working great as far as muting encryption.
I'm sure someone will want it to start looking for other in the clear traffic as soon as it detects ENC instead of hanging on the enc TG but that may just cause the P25RX to just find the same end TG over and over again on a system that's not busy.
I could see users wanting little or no delay when enc is detected so they don't miss clear traffic but hey, this is a great start!
I know a lot of people like to stop on enc TGs for logging purposes so this will probably suit their needs well. Myself, I'd probably like to see it resume the search for other active TGs as soon as it detects enc instead of hanging on the enc TG until the repeater drops. I think it's working pretty much how GRE or Whistler handles encrypted TG's. They also hold on the TG for the duration of the communication and just silence the audio or replace it with a busy tone depending on what the user wants. Uniden models on the other hand make a very good attempt at not even stopping on an ENC TG. They do sometimes pause for a very short period but then they continue looking at the CC data for other active TGs.
I know here at RR there has been a lot of discussion amongst users who want it the Whistler way and many who want it the Uniden way! The ultimate solution and asked for fix is a toggle that the user can switch to stop and log ENC TG activity or switch it to the Uniden way and ignore it completely kind of like avoiding or locking out a talkgroup would do.
Of course locking out a TG with clear and ENC traffic is not always ideal as you do miss the clear traffic then.
I know you have a lot of other things going on but maybe down the road (in the distant future!) you can figure out a way to toggle different modes of muting and/or ignoring ENC traffic that does not hang the P25RX up on the ENC TG.

And no, I'm not complaining about the way this new version works! I actually love how it's working. I've been hearing a lot of traffic that I had to lockout before because the P25RX was still passing the encrypted audio for some reason.

Thanks for your very prompt new version release as usual!!

 

[APX7500X2]

MSP is a smartzone system

Except for the part around Boston that's P25(Troop A+), or Worcester, Logan airport, Cambridge. Worked great on my Unication G5 last week while up there, The blue tail will have plenty to listen to when you go by. I got the MSP P25 system into NH a little.
Also Manchester and Nashua play well depending where you are up there

 

[Cheeseburgers]

You think I could get it out on the Cape? Mid-Cape / Dennis?

 

[KC1UA]

You think I could get it out on the Cape? Mid-Cape / Dennis?

CoMIRS has not made it down this way yet, and short of a band opening I'm thinking no. The only P25 systems that can be heard from here in my case are the Nantucket system and on a good day RISCON....on a REALLY good day...

 

[epersson]

Except for the part around Boston that's P25(Troop A+), or Worcester, Logan airport, Cambridge. Worked great on my Unication G5 last week while up there, The blue tail will have plenty to listen to when you go by. I got the MSP P25 system into NH a little.
Also Manchester and Nashua play well depending where you are up there

Ya, I'm up in SE NH near the seacoast, none of the systems around make it this far, and I'm in a lowlands. The Portsmouth Shipyard has the DoD P25P2 but no traffic on it at all. I'll go back to SO FL in the fall and be back in the thick of it..

 

[btt]

So far this works great Todd!
I've also not tested the auto disable feature but it is working great as far as muting encryption.
I'm sure someone will want it to start looking for other in the clear traffic as soon as it detects ENC instead of hanging on the enc TG but that may just cause the P25RX to just find the same end TG over and over again on a system that's not busy.
I could see users wanting little or no delay when enc is detected so they don't miss clear traffic but hey, this is a great start!
I know a lot of people like to stop on enc TGs for logging purposes so this will probably suit their needs well. Myself, I'd probably like to see it resume the search for other active TGs as soon as it detects enc instead of hanging on the enc TG until the repeater drops. I think it's working pretty much how GRE or Whistler handles encrypted TG's. They also hold on the TG for the duration of the communication and just silence the audio or replace it with a busy tone depending on what the user wants. Uniden models on the other hand make a very good attempt at not even stopping on an ENC TG. They do sometimes pause for a very short period but then they continue looking at the CC data for other active TGs.
I know here at RR there has been a lot of discussion amongst users who want it the Whistler way and many who want it the Uniden way! The ultimate solution and asked for fix is a toggle that the user can switch to stop and log ENC TG activity or switch it to the Uniden way and ignore it completely kind of like avoiding or locking out a talkgroup would do.
Of course locking out a TG with clear and ENC traffic is not always ideal as you do miss the clear traffic then.
I know you have a lot of other things going on but maybe down the road (in the distant future!) you can figure out a way to toggle different modes of muting and/or ignoring ENC traffic that does not hang the P25RX up on the ENC TG.

And no, I'm not complaining about the way this new version works! I actually love how it's working. I've been hearing a lot of traffic that I had to lockout before because the P25RX was still passing the encrypted audio for some reason.

Thanks for your very prompt new version release as usual!!

There is a new option on the advanced tab for "return to CC on encryption". Not tested yet. Version 2021-04-14_1055

 

[btt]

New testing version with some bugs fixed related to the roaming mode of operation. Version 2021-04-16_0948.

@goldmyne99, I believe this may fix the issue you were observing in this post (#28) here:

Not receiving VC/audio

I will try alt version in about an hour and post the results.

forums.radioreference.com

 

[goldmyne99]

New testing version with some bugs fixed and some performance improvements related to the roaming mode of operation. Version 2021-04-16_0948.

@goldmyne99, I believe this may fix the issue you were observing in this post (#28)

Thanks! I do not see it happen often, but will keep an eye out for it with this fix installed.

 

[Cheeseburgers]

Using my Shure Antenna attached to a SMA base... I love my P25rx, especially with the new firmware. Plus Todd is constantly improving stuff.

 

[brndnstffrd]

I discovered a bug with the latest firmware. Ever since updating, every RID shows as 0 in the log. If i turn off the option for logging with RID 0, then nothing shows in the talkgroup log. Previous to this I had been using the BTConfig-2021-03-25_0703 software and firmware.

When I reverted back to this software and firmware, the RID and talkgroup log functions correctly.

 

[btt]

I discovered a bug with the latest firmware. Ever since updating, every RID shows as 0 in the log. If i turn off the option for logging with RID 0, then nothing shows in the talkgroup log. Previous to this I had been using the BTConfig-2021-03-25_0703 software and firmware.

When I reverted back to this software and firmware, the RID and talkgroup log functions correctly.

Are you monitoring a phase 1 or phase 2 system when it doesn't work right? The reason for allowing an RID of 0 is that some systems such as "restricted tones" or automated fire dispatch only transmit an RID of 0. I wonder if this is what you ran into while testing later versions?

 

[brndnstffrd]

I am monitoring a Phase 2 system. We have no RID of 0 on either of the systems I monitor, and roaming is not enabled, since I only monitor 1 at a time.

 

[turnpike61]

Two complete windows lockups in the past two days. I returned to the machine, and screens completely frozen. No keyboard or mouse input. Only change appears to be running 2020-04-16_1727. I have reverted to 4-11_1224 to see if this recurs.

 

[btt]

Two complete windows lockups in the past two days. I returned to the machine, and screens completely frozen. No keyboard or mouse input. Only change appears to be running 2020-04-16_1727. I have reverted to 4-11_1224 to see if this recurs.

That doesn't sound like a BTConfig issue. That sounds like a computer hardware or Windows issue.

I am monitoring a Phase 2 system. We have no RID of 0 on either of the systems I monitor, and roaming is not enabled, since I only monitor 1 at a time.

I made a change to the phase 2 code related to the RID updates. version 2021-04-18_1159. I can't test it here yet, but I think it should be the same as earlier versions with respect to the RID update.

 

[brndnstffrd]

That doesn't sound like a BTConfig issue. That sounds like a computer hardware or Windows issue.


I made a change to the phase 2 code related to the RID updates. version 2021-04-18_1159. I can't test it here yet, but I think it should be the same as earlier versions with respect to the RID update.

It appears to still be doing the same thing in that with the allow logging of RID 0, all RID's are shown as 0. When the option is unselected, no talkgroup info shows up in the talkgroup log and the RID doesnt display like it usually would in the info bar at the bottom of the BTTconfig window.

 

[kruser]

Two complete windows lockups in the past two days. I returned to the machine, and screens completely frozen. No keyboard or mouse input. Only change appears to be running 2020-04-16_1727. I have reverted to 4-11_1224 to see if this recurs.

I had computer freezes with BTConfig running using several different versions back during the earlier days of the P25RX.
I learned that plugging my P25RX into any USB port that connected to one of the motherboards ASMEDIA USB controllers was the culprit.
I can still create the same freeze or lockup today with the latest BTConfig version after they run random amounts of time and are plugged into an ASMedia port.
As long as I use any of the Intel based USB chipsets built on the same motherboard, BTConfig will run for days without ever freezing. I'm with @btt on this one with his thinking it's probably a hardware issue.
I've also had some luck in the past by using a tiny non powered or powered USB 2.0 hub plugged into the ASMedia 3.1 ports.
The use of the 2.0 speed hub seemed to greatly reduce the frequency of freezing I'd see not just with BTConfig but with RTL-SDR tuners and their software also. I never did figure out the root cause of the freezing problem when some devices were plugged into USB 3.0 or 3.1 ports but putting them on slower speed hubs often helped.
If you have different chipset USB ports on your computer and still see freezes with BTConfig, try plugging you P25RX into one of the other USB ports and see if that helps.

 

[goldmyne99]

I discovered a bug with the latest firmware. Ever since updating, every RID shows as 0 in the log. If i turn off the option for logging with RID 0, then nothing shows in the talkgroup log.

I also see only RID 0 on "TG log screen" on a Phase 2 system.
The "Console screen" messages do show the correct RIDs (none are RID 0).
The P25RX is sending the correct RIDs, my Android apk is displaying them correctly. The BTConfig TG log is showing them all to be RID 0.

 

[btt]

Updated again. Version 2021-04-19_2046 reverted the firmware back to what it was prior to the previous version. Changed the RID code for phase 2 to be identical to the phase 1 code. Let me know if there is still an issue.

 

[brndnstffrd]

Updated again. Version 2021-04-19_2046 reverted the firmware back to what it was prior to the previous version. Changed the BTConfig RID code for phase 2 to be identical to the phase 1 code. Let me know if there is still an issue.

I will do some testing on this tomorrow and will report back.