P25RX Firmware Updates / Testing

[beischel]

Running 12/18 2009, P1 Encryption issue appears to be resolved.

I just updated to the 12-18 version and I can report that my P25RX is still picking up encrypted communication on P1 transmissions.

 

[btt]

I just updated to the 12-18 version and I can report that my P25RX is still picking up encrypted communication on P1 transmissions.

Try version 12-21_0538.

 

[dcr_inc]

Todd... 12-20_2147 is a HIT for me.. P25RXII has come back alive and sounding as good as my G4 and G5 Unication.. THANKS AGAIN !!

 

[btt]

Todd... 12-20_2147 is a HIT for me.. P25RXII has come back alive and sounding as good as my G4 and G5 Unication.. THANKS AGAIN !!

Thank you for the feedback! I should have another P25RX-II release shortly with improved P1 encryption detection, logging, and programmable encryption TG timeout.

 

[beischel]

Try version 12-21_0538.

OK, I did install the 12-21 version late yesterday afternoon. So far I have not heard any encrypted transmissions coming through like before, but encryption is not always used so a little early to tell if the 12-21 version fixed the issue, but so far so good. Thanks!

 

[krutzy]

I have noticed lately (I really haven't looked to often) but when running P25RX my "Java Platform SE binary" runs very high CPU and Power. The CPU % is between 40% - 50%. That is pretty darn high. I have a AMD Phenom II X4 B50 Processor 3.2 GHz and 8 GB RAM 64 bit. This seems to be recent because I started looking because the PC has been running slower lately? Anything I can tweak

 

[maus92]

I have noticed lately (I really haven't looked to often) but when running P25RX my "Java Platform SE binary" runs very high CPU and Power. The CPU % is between 40% - 50%. That is pretty darn high. I have a AMD Phenom II X4 B50 Processor 3.2 GHz and 8 GB RAM 64 bit. This seems to be recent because I started looking because the PC has been running slower lately? Anything I can tweak

You will have high CPU usage when the program is doing a lot of drawing - like when viewing the Signal Insights tab.

 

[dcr_inc]

Todd.. The AGC Firmware is working great here.. KUDOS.. CC RSSI is around -90 but when a talkgroup is active, the RSSI goes to -75 to -77.. Makes hearing the P2 system here much better.. I am listening to a Harris P2 system

 

[shirsch101]

DCR_INC by any chance do you pick up any of the Chester County P25?

 

[dcr_inc]

Chester is too far away from me to hear it.. I believe there are P25RX users there..

 

[shirsch101]

Chester is too far away from me to hear it.. I believe there are P25RX users there..

I live outside the borough of West Chester any other P25RX users in the Chester County area?

 

[Vermonster]

First chance in a week to take a look at new firmware performance.
Running on my most challenging 900mhz system, voice quality is very good
Incorrect time format is fixed.

Three quirks identified.
#1
Same Con+ DMR system running on both RX-I and RX-II (both running latest 1224 firmware)
Status format identical for both: $P25_MODE$ CC BLKS_SEC $BLKS_SEC$
On RX-II, status line starts "DMR..."
But on RX-I, status line starts "P25-P1..."

#2
On both RX-I and RX-II, on this Con+ system identical errors are created in the TG log, where TG #s don't correctly match TG name; the errors are identical on both RX-I and RX-II. Example below, where TG names should be:
35: Eascare Ambulance Ch.09 Metrowe
133: Chair Van Service_unknown
199: 199???_unknown
498: Garbage Company
567: 567_unknown


P25-P1 935.250000 MHz, TG 567 , Eascare Ambulance Ch.09 Metrowe, 2021-12-29-14:22:58, -115 dbm, cc_freq Freq: mhz, RID 16126, P25-P1, EVM 9%,
P25-P1 935.750000 MHz, TG 567 , 567_unknown, 2021-12-29-14:23:15, -117 dbm, cc_freq Freq: mhz, RID 17333, P25-P1, EVM 9%,
P25-P1 935.750000 MHz, TG 567 , 567_unknown, 2021-12-29-14:23:35, -105 dbm, cc_freq Freq: mhz, RID 17333, P25-P1, EVM 4%,
P25-P1 935.512500 MHz, TG 567 , 567_unknown, 2021-12-29-14:24:20, -104 dbm, cc_freq Freq: mhz, RID 17333, P25-P1, EVM 5%,
P25-P1 935.512500 MHz, TG 498 , 567_unknown, 2021-12-29-14:24:55, -105 dbm, cc_freq Freq: mhz, RID 13848, P25-P1, EVM 6%,
P25-P1 935.537500 MHz, TG 199 , Garbage Company, 2021-12-29-14:25:22, -105 dbm, cc_freq Freq: mhz, RID 9661, P25-P1, EVM 10%,
P25-P1 935.750000 MHz, TG 133 , 199???_unknown, 2021-12-29-14:25:27, -117 dbm, cc_freq Freq: mhz, RID 15605, P25-P1, EVM 8%,
P25-P1 935.750000 MHz, TG 35 , Chair Van Service_unknown, 2021-12-29-14:25:45, -119 dbm, cc_freq Freq: mhz, RID 12514, P25-P1, EVM 13%,
P25-P1 936.200000 MHz, TG 35 , Eascare Ambulance Ch.09 Metrowe, 2021-12-29-14:25:48, -119 dbm, cc_freq Freq: mhz, RID 12514, P25-P1, EVM 10%,
P25-P1 936.200000 MHz, TG 35 , Eascare Ambulance Ch.09 Metrowe, 2021-12-29-14:25:54, -118 dbm, cc_freq Freq: mhz, RID 12514, P25-P1, EVM 12%,
P25-P1 936.200000 MHz, TG 498 , Eascare Ambulance Ch.09 Metrowe, 2021-12-29-14:26:01, -119 dbm, cc_freq Freq: mhz, RID 15703, P25-P1, EVM 6%,
P25-P1 935.537500 MHz, TG 458 , Garbage Company, 2021-12-29-14:26:06, -105 dbm, cc_freq Freq: mhz, RID 9242, P25-P1, EVM 9%,
P25-P1 935.250000 MHz, TG 498 , (unknown tgroup), 2021-12-29-14:26:10, -111 dbm, cc_freq Freq: mhz, RID 13848, P25-P1, EVM 8%,
P25-P1 935.250000 MHz, TG 498 , Garbage Company, 2021-12-29-14:26:20, -112 dbm, cc_freq Freq: mhz, RID 13853, P25-P1, EVM 5%,
P25-P1 935.512500 MHz, TG 35 , Garbage Company, 2021-12-29-14:26:36, -104 dbm, cc_freq Freq: mhz, RID 9227, P25-P1, EVM 5%,
P25-P1 935.512500 MHz, TG 498 , Eascare Ambulance Ch.09 Metrowe, 2021-12-29-14:26:40, -105 dbm, cc_freq Freq: mhz, RID 13853, P25-P1, EVM 5%,

I *think* what I am observing is that the instant the call is received, the TG # and name are displayed in the Status area, and a line is written in the TG log. If the call continues for a few seconds and the TG #/name is initially a mismatch, it will be corrected in the Status area, but the incorrect line remains in the log.

#3.
On Con+, encrypted voice is heard for extended period on both RX-I and RX-II despite "Enable Encrypted Audio Output" being unchecked.

 

[Mike_G_D]

I also noted encrypted voice audio regardless of setting of "Enable Encrypted Audio Output" for P25 P1 audio with the latest version. It seemed to "go away" in a previous version but I'm not sure which one after having been a problem for awhile and then returned with the latest version.

 

[btt]

In version 12-29_1710 (P25RX) and version 12-29_1704 (P25RX-II), the encryption algorithm is detected in the HDU. If there are no errors detected in the bits that define the encryption algorithm, then it will be processed before audio begins. (return to control channel on encrypted).

 

[radio3353]

Just a heads-up Todd...the P25RX Firmware/Software web page has an incorrect filename for the latest update. It says '24', not '29'. The actual file is correct however.

 

[btt]

I have noticed lately (I really haven't looked to often) but when running P25RX my "Java Platform SE binary" runs very high CPU and Power. The CPU % is between 40% - 50%. That is pretty darn high. I have a AMD Phenom II X4 B50 Processor 3.2 GHz and 8 GB RAM 64 bit. This seems to be recent because I started looking because the PC has been running slower lately? Anything I can tweak

There is a new version (12-31_0310) available with CPU usage options (high, normal, low, battery-save, and off) on the signal insights tab. My guess is that the high CPU usage is because the CPU is being throttled for battery saving purposes (and therefore relatively high usage), but these options should give you the ability to fine tune it for your situation. Happy New Years!

 

[btt]

I also noted encrypted voice audio regardless of setting of "Enable Encrypted Audio Output" for P25 P1 audio with the latest version. It seemed to "go away" in a previous version but I'm not sure which one after having been a problem for awhile and then returned with the latest version.

You are correct. I thought this was fixed, but it wasn't. It is fixed in version 12-31_1845.

 

[brndnstffrd]

Just a heads up, not sure if its something related to my computer or what the issue may be, but using version 2021-12-31-18:45 within the last 24 hours, 4 times the unit has locked up. Not sure if locked up is the right term or not, but without warning the unit freezes and no audio is received, basically like it is disconnected from the computer. If you unplug and reconnect BTTconfig it never detects the unit, even if the program is restarted or if the computer is restarted. The only thing that I have been able to do is put the unit into bootstrap mode and force a reload of the firmware, which fixes the unit, although it seems to repeat this behavior. I am unsure on the period of time that it takes for this to occur again, as I recovered it yesterday evening and it ran successfully overnight then died sometime during the day today, and then after recovering it this afternoon, it froze up again mid evening. Again there is a possibility that the issue is on my end and not related to the software or the unit.

 

[btt]

Just a heads up, not sure if its something related to my computer or what the issue may be, but using version 2021-12-31-18:45 within the last 24 hours, 4 times the unit has locked up. Not sure if locked up is the right term or not, but without warning the unit freezes and no audio is received, basically like it is disconnected from the computer. If you unplug and reconnect BTTconfig it never detects the unit, even if the program is restarted or if the computer is restarted. The only thing that I have been able to do is put the unit into bootstrap mode and force a reload of the firmware, which fixes the unit, although it seems to repeat this behavior. I am unsure on the period of time that it takes for this to occur again, as I recovered it yesterday evening and it ran successfully overnight then died sometime during the day today, and then after recovering it this afternoon, it froze up again mid evening. Again there is a possibility that the issue is on my end and not related to the software or the unit.

It sounds more like a USB cable issue or some type of hardware issue since you cannot recover by cycling power. There is a new firmware change available that might help with a potential lockup issue, but it doesn't really sound like the issue you are having. Let me know if you try a different cable and you still have issues. If you think it is firmware, then please revert back to a previous version and see if the issue goes away. Don't hesitate to email if you like.

 

[brndnstffrd]

Alright i will check it out and report back, although it will be harder to troubleshoot during the week since there are less chances of me being around when it fails. I will try the newer software/firmware and see how it goes, then next I will try a new usb cable if the issue persists.