I thought it saved the frequency. I will check into that.
-edit: Nope. Thanks for pointing that out. I think I have that fixed now. It will be in the next release.
Last edited:
P25RX Firmware Updates / Testing
- Thread starter btt
- Start date
- Status
-edit: Nope. Thanks for pointing that out. I think I have that fixed now. It will be in the next release.
For _1649, I am seeing a significant decrease in RF Signal level, as compared to previous versions. I was getting -60dBm before with outside antenna, now getting -90dBm. I am going to go back to a previous version to check levels.
* UPDATE: RF Signal level is fine. I had selected a different CC as Primary. Another case of "Operator Error" - Time for sleep
* UPDATE: RF Signal level is fine. I had selected a different CC as Primary. Another case of "Operator Error" - Time for sleep
Last edited:
For _1649, I am seeing a significant decrease in RF Signal level, as compared to previous versions. I was getting -60dBm before with outside antenna, now getting -90dBm. I am going to go back to a previous version to check levels.
* UPDATE: RF Signal level is fine. I had selected a different CC as Primary. Another case of "Operator Error" - Time for sleep
I was going to say that the recent changes would have nothing to do with signal level. Glad you figured it out.
Last edited:
I have been testing the 2021-03-17_1649 version. Two minor things I have found, otherwise it seems to be working well otherwise.
1. The P25 Frequency on the P25RX Configuration tab resets to 859.xxxx. It threw me for a loop at first because the system I monitor is 857.9625 and the frequency changed to 859.9625 but I didn't notice this right away. All I knew was that I was getting 0 BLKS/SEC and a -131db signal (no signal). Once I changed that frequency to the correct frequency, all was good.
2. I noticed that clearing all of the talkgroups, saving the config (so there are no talkgroups) and then trying to restore from TGP or Import CSV locks up the P25RX consistently. It gets stuck at Reading Talkgroups from the P25RX after restoring from TGP or the Import CSV function. I must power cycle the P25RX and restarting the BTConfig software.
3. After restoring the backup file made, the first 3 talkgroups are restored properly, the 4 is mostly restored with 4 gibberish characters in the description and the other 10 talkgroups are all messed up with totally incorrect information. The only way to restore the information is by opening up the CSV file (which looks correct) and manually re-entering all of the talkgroup information.
Attached is a ZIP file containing the screenshot of what it looks like after the Restore from TGP and Import CSV function was performed, as well as my TGP and CSV files I used to restore it from.
Other than these observations -- the software seems to be performing well.
Please note that I am running the BTConfig on Mac OSX during these observations so perhaps running it on a PC could be different.
1. The P25 Frequency on the P25RX Configuration tab resets to 859.xxxx. It threw me for a loop at first because the system I monitor is 857.9625 and the frequency changed to 859.9625 but I didn't notice this right away. All I knew was that I was getting 0 BLKS/SEC and a -131db signal (no signal). Once I changed that frequency to the correct frequency, all was good.
2. I noticed that clearing all of the talkgroups, saving the config (so there are no talkgroups) and then trying to restore from TGP or Import CSV locks up the P25RX consistently. It gets stuck at Reading Talkgroups from the P25RX after restoring from TGP or the Import CSV function. I must power cycle the P25RX and restarting the BTConfig software.
3. After restoring the backup file made, the first 3 talkgroups are restored properly, the 4 is mostly restored with 4 gibberish characters in the description and the other 10 talkgroups are all messed up with totally incorrect information. The only way to restore the information is by opening up the CSV file (which looks correct) and manually re-entering all of the talkgroup information.
Attached is a ZIP file containing the screenshot of what it looks like after the Restore from TGP and Import CSV function was performed, as well as my TGP and CSV files I used to restore it from.
Other than these observations -- the software seems to be performing well.
Please note that I am running the BTConfig on Mac OSX during these observations so perhaps running it on a PC could be different.
Thank you for testing and reporting the results. I have not been able to reproduce your results here so far, but I am testing on Linux. I will test on Windows 10 next.
rdlafore
Member
The new test version, _1649, has been running smoothly since I installed it last night. Good audio, no "lock ups" etc. Thank You!!!!
Yes, I will get that added as another option. The skip function currently disables the talk group for 60 minutes. It is temporary and a power cycle does reset it.
rbjzx9
Professional Lurker
If it's possible, in the future could an option be added to the software for a user selectable time? Twice a day the local fire dept does a radio test. I'd like to be able to set this for 10 minutes or so to avoid listening to the test.
Also just wanted to thank you again for the quick support on the "0" trunk group issue. It's been going strong for two days now.
Ron
Yes, I can get that added.
Version 1649:
Are the "Button CFG" features enabled yet? Example: Where it says one click to (for example) hold on a talk group, where exactly do you click? I've tried everywhere, and I can't get it to work.
Are the "Button CFG" features enabled yet? Example: Where it says one click to (for example) hold on a talk group, where exactly do you click? I've tried everywhere, and I can't get it to work.
freqseeker
Member
Have you tried the blue button on the receiver itself?
You must write the configuration to the unit first.
I haven't used this yet, but that's how I understand it to work. This way it will work in stand alone mode.
You must write the configuration to the unit first.
I haven't used this yet, but that's how I understand it to work. This way it will work in stand alone mode.
Yes, they are working now. As freqseeker pointed out, this is the configuration for the TG button on the receiver.
TomTN
Member
This has been mentioned before but despite trying the suggestions and many many suggested "fixes" on the Internet it is still an issue.
Whenever I reboot or do a full shutdown then restart, the device is unable to be recognized until the USB cable is removed and reinstalled. This has been tested on two Dell desktops and an HP desktop, all running Windows 10 64 bit. Both USB 3 and USB 2 ports do the same thing. Power settings have been changed many ways without any effect. BIOS settings have been changed without any effect. With or without an external hub makes no difference. Multiple USB cables have been tried. Disabling/Enabling/Uninstalling USB port does not help.
I'm starting to wonder if I have a defective device. Once power cycled via USB it works though.
On restart, the USB controller states: "Unknown USB Device (Device Descriptor Request Failed)"
Device Status:
"Windows has stopped this device because it has reported problems. (Code 43)
A request for the USB device descriptor failed."
This is a great device and I appreciate the work Todd has put into this. The lack of ability to restart without having to power cycle the device is, however, maddening.
Have any of you had this issue and solved it? Not sure if this is a hardware or firmware issue. It has done the same thing with every version.
Whenever I reboot or do a full shutdown then restart, the device is unable to be recognized until the USB cable is removed and reinstalled. This has been tested on two Dell desktops and an HP desktop, all running Windows 10 64 bit. Both USB 3 and USB 2 ports do the same thing. Power settings have been changed many ways without any effect. BIOS settings have been changed without any effect. With or without an external hub makes no difference. Multiple USB cables have been tried. Disabling/Enabling/Uninstalling USB port does not help.
I'm starting to wonder if I have a defective device. Once power cycled via USB it works though.
On restart, the USB controller states: "Unknown USB Device (Device Descriptor Request Failed)"
Device Status:
"Windows has stopped this device because it has reported problems. (Code 43)
A request for the USB device descriptor failed."
This is a great device and I appreciate the work Todd has put into this. The lack of ability to restart without having to power cycle the device is, however, maddening.
Have any of you had this issue and solved it? Not sure if this is a hardware or firmware issue. It has done the same thing with every version.
It is a known bug. At one point, the "USB watchdog" was added to try and mitigate the issue. It was causing more issues than it was solving, so that change was reverted. I believe the actual issue is in the MCU manufacturer's USB Device driver code. I've been hoping they would fix and release an update, but I have not seen one so far. I'm going to download the latest tools today and see if they changed anything. I believe this issue is related to the remaining issue I have with the display not always initializing USB communications correctly on startup. It will be fixed eventually (I'll try to speed this up).
-edit: Latest driver did not help. Note that this issue with not being detected on reboot appears to only happen with WIndows OS (Win10 here). Linux is fine.
Last edited:
boy7777777777
Member
I have a whistler trx-1 and it has been that way since the day I bought it. Whistler never fixed it. Todd is an awesome guy. I know he will get it fixed. I've never saw anybody anywhere as responsive and on top of trying to fix stuff.
TomTN
Member
Oh well, you gave it a try! Hopefully they will fix the issue some day.
I'm used to needing to pull the USB cable three times each time I do a firmware update. It's not really a big deal plus I do it from the computer end so I don't wear out the USB-C jack on the P25RX even though it's a very durable jack of high quality.
- Status
