Just saw all the posts about fw update issues. Sorry about that. I think this issue came about when messing with the serial comm delays to try and get the Mac working better. I'll work doing something different for the fw updates. The firmware update is actually very reliable in the sense that out of the thousands of updates, there has only been one time that someone had to send it back. I'll work on getting rid of the glitches. In the meantime, please try version 12-17_0713. This version has extra delay times added. It will take longer, but this may solve the issue with the fw update process and the other issues that have mentioned regarding having to write the configuration twice.
P25RX Firmware Updates / Testing
- Thread starter btt
- Start date
- Status
Sorry, had a typo in the link. You can find P25RX updates here: https://bluetailtechnologies.com/pages/p25rx-firmware-software
Tood.. I can not get any BTconfig versions above 11_24 to find my P25RXII.. The BTconig shows that it is searching for device.. Any Ideas?
I have tried both 10 and 40 second resets with no luck.
I have tried both 10 and 40 second resets with no luck.
BTConfig only works with the P25RX.
BTCFG-II software is here:
P25RX-II Software / Firmware
P25RX-II Software / Firmware You can find the "TESTING" versions of the tree-view-based,scanning release here latest btt-advanced-db software You can find the "EXPERIMENTAL" versions of the tree-view-based,scanning release here latest experimental btt-advanced-db software LATEST TESTING...
bluetailtechnologies.com
Sorry, that is usually the cause of this issue. I don't know what would cause this. I am currently working on improving the firmware update process for the P25RX. I should have it in the next hour or two. Once that is verified to be working, I will make the same changes to the BTCFG-II software update process.
Thank you. There was a driver update in versions 11-28 to 12-11 that may be causing issues. Have you tried version 12-13_0707?
Loaded v0713 on the P25RX this morning and it's running great now. The only thing I saw that does not appear to be working is the encryption enable/disable under the advanced tab. The device continues to pass the audio when checked or unchecked. I recycled the power but did not make a difference.
I took the device and placed it in a mobile environment on P25p1 system and this thing does just as good as my SDS200 and Unication G5!! I still need to check on a local Cap+ system here that the county switched over to but I would expect similar results.
Keep up the fantastic work Todd! They way you are progressing it won't be long when you can stop writing code and put emphasis with putting together additional devices and hopefully have a steady source of revenue ...
All I can say that whatever company you left, lost a great employee! You should have also been given the responsibility of customer support rep. 👍👍👍
I took the device and placed it in a mobile environment on P25p1 system and this thing does just as good as my SDS200 and Unication G5!! I still need to check on a local Cap+ system here that the county switched over to but I would expect similar results.
Keep up the fantastic work Todd! They way you are progressing it won't be long when you can stop writing code and put emphasis with putting together additional devices and hopefully have a steady source of revenue ...
All I can say that whatever company you left, lost a great employee! You should have also been given the responsibility of customer support rep. 👍👍👍
I second what W0RS said! Am also getting the encrypted audio, though, (no matter the setting) was going to bring that up myself, but otherwise doing very well. Having the selection to return to the CC on encrypted seems to help mitigate the issue somewhat. But there are some talk groups that have a mix of encrypted and clear and it would be nice to hear the clear fragments without hearing the encrypted garble.
-Mike
-Mike
Thank you for the feedback sir! I'm really really glad to hear that it is finally working well for you there in MO!
Version 12-17_1421 is available. This has been verified to be a glitch-free firmware update process on Windows 10. I will check Mac a bit later this eve. If this works well for everyone, I will get these changes made to the P25RX-II as well.
I will look into what could be done for the encryption. Does it happen only on P1? P2? both?
12-18_0652 may fix the encryption issue for P1.
Vermonster
Member
Updated from 1215_1638 to 1218_2009 with no issues.
Does not request permission to run firmware update (opinion: would be nice if it did)
Impression: firmware update takes longer than before (opinion: not a material change)
Previous issues that probably effect very few of us and remain on this firmware version . This also impacts RX-II
#1. P25 conventional. Does not record audio. Does not matter if recording to a single file or per-talkgroup.
#2. Sometimes TG log shows strange word "Time", instead of either TG Name or "(unknown tgroup)"
Example:
P25-P1 154.935000 MHz, TG 1 , NHSP, 2021-12-19-07:03:43, -110 dbm, cc_freq mhz, RID 231, P25-P1, EVM 11%,
P25-P1 154.935000 MHz, TG 1 , , Time, 2021-12-19-07:06:53, -109 dbm, cc_freq mhz, RID 11010, P25-P1, EVM 9%,
P25-P1 154.935000 MHz, TG 1 , , Time, 2021-12-19-07:06:57, -107 dbm, cc_freq mhz, RID 223, P25-P1, EVM 8%,
P25-P1 154.935000 MHz, TG 1 , NHSP, 2021-12-19-07:07:20, -108 dbm, cc_freq mhz, RID 11010, P25-P1, EVM 8%,
#3. At some point it would be nice to be able to manually enter a SYSID for P25 conventional (as currently enabled with DMR). This would allow naming of TG unique to the system. For the moment, if you manually create an entry in the TG Editor with a SYS_ID of "0x1" and WACN of "0x0" naming will work.
New issues with RX-I only.
#1. Log is displaying time in wrong format. Trunked systems are quiet here, so I can't check if this also occurs outside P25 conventional.
->(VOICE), freq: 154.935000, rssi: -108 dBm, TGroup: 1, Desc: , Time: 701288 erate: 0.000 $
handle HDU
P25_P1: SRC_RID: 230 GRP: 1 $
->(VOICE), freq: 154.935000, rssi: -108 dBm, TGroup: 1, Desc: (unknown tgroup), Time: 702022 erate: 0.000 $
->(VOICE), freq: 154.935000, rssi: -108 dBm, TGroup: 1, Desc: (unknown tgroup), Time: 702096 erate: 0.014 $
->(VOICE), freq: 154.935000, rssi: -108 dBm, TGroup: 1, Desc: (unknown tgroup), Time: 702144 erate: 0.018 $
#2. Does not capture NAC (does not show in conlog or in Display View)
Reception conditions are very difficult here this morning with freezing rain/snow and both RX-I and RX-II units voice transmissions are as good as my other radios. Impressive.
Does not request permission to run firmware update (opinion: would be nice if it did)
Impression: firmware update takes longer than before (opinion: not a material change)
Previous issues that probably effect very few of us and remain on this firmware version . This also impacts RX-II
#1. P25 conventional. Does not record audio. Does not matter if recording to a single file or per-talkgroup.
#2. Sometimes TG log shows strange word "Time", instead of either TG Name or "(unknown tgroup)"
Example:
P25-P1 154.935000 MHz, TG 1 , NHSP, 2021-12-19-07:03:43, -110 dbm, cc_freq mhz, RID 231, P25-P1, EVM 11%,
P25-P1 154.935000 MHz, TG 1 , , Time, 2021-12-19-07:06:53, -109 dbm, cc_freq mhz, RID 11010, P25-P1, EVM 9%,
P25-P1 154.935000 MHz, TG 1 , , Time, 2021-12-19-07:06:57, -107 dbm, cc_freq mhz, RID 223, P25-P1, EVM 8%,
P25-P1 154.935000 MHz, TG 1 , NHSP, 2021-12-19-07:07:20, -108 dbm, cc_freq mhz, RID 11010, P25-P1, EVM 8%,
#3. At some point it would be nice to be able to manually enter a SYSID for P25 conventional (as currently enabled with DMR). This would allow naming of TG unique to the system. For the moment, if you manually create an entry in the TG Editor with a SYS_ID of "0x1" and WACN of "0x0" naming will work.
New issues with RX-I only.
#1. Log is displaying time in wrong format. Trunked systems are quiet here, so I can't check if this also occurs outside P25 conventional.
->(VOICE), freq: 154.935000, rssi: -108 dBm, TGroup: 1, Desc: , Time: 701288 erate: 0.000 $
handle HDU
P25_P1: SRC_RID: 230 GRP: 1 $
->(VOICE), freq: 154.935000, rssi: -108 dBm, TGroup: 1, Desc: (unknown tgroup), Time: 702022 erate: 0.000 $
->(VOICE), freq: 154.935000, rssi: -108 dBm, TGroup: 1, Desc: (unknown tgroup), Time: 702096 erate: 0.014 $
->(VOICE), freq: 154.935000, rssi: -108 dBm, TGroup: 1, Desc: (unknown tgroup), Time: 702144 erate: 0.018 $
#2. Does not capture NAC (does not show in conlog or in Display View)
Reception conditions are very difficult here this morning with freezing rain/snow and both RX-I and RX-II units voice transmissions are as good as my other radios. Impressive.
I'm glad you pointed out the lack of recorded audio. That's a showstopper for me and I'm rolling back. What was the last version which recording worked on?
Thanks.
Vermonster
Member
Before you roll back, let me test on trunked system. It might be a problem unique to conventional P25 only. Honestly, I don't know if/when it was working on conventional.
Edited to add: I just tested on a Con+ trunked DMR system. The recording is working just fine. I don't have a P25 trunked system to test, but expect recording will work fine. The issue seems to be isolated to conventional (non-trunked) systems.
Last edited:
dispatchgeek
Control channel goes "brrrrr"
Running 12/18 2009, P1 Encryption issue appears to be resolved.
- Status
