P25RX Firmware Updates / Testing
- Thread starter btt
- Start date
- Status
Thanks for the update. For others reading, the latest versions will strip any non-standard ASCII from the CSV imports. (version 02-09_2005 and later).
For anyone that doesn't update but the console looks like my example above and the call log doesn't show all the voice grants there is a special Character inserted after the name field. It can't be seen in text editor or excel but Notepad++ or many other programming editors, shows it as below when you select UTF-8 (not ASCII)
Delete it, reimport it and the call logs and console appear normally.
Delete it, reimport it and the call logs and console appear normally.
dispatchgeek
Control channel goes "brrrrr"
I am also on MPSCS- I have to use the CQPSK setting as well. Should be interesting to see once the simulcast project is complete in my area.
dispatchgeek
Control channel goes "brrrrr"
I am noticing a new issue on 2-10 1045. I am writing logs to file now, but of course the problem hasn't shown up all day.
It appears at some point, the P25RX stops picking up on talkgroups. Logs indicate it is constantly monitoring the control channel, that all looks correct. Sometimes I am able to clear it by randomly enabling/disabling zones, sometimes I have to re-write config to the P25RX. It seems to have this behavior with or without roaming enabled.
I generally run everything in Zone 1, so the zones I am enabling/disabling should be arbitrary.
I will post a log once I catch it again.
It appears at some point, the P25RX stops picking up on talkgroups. Logs indicate it is constantly monitoring the control channel, that all looks correct. Sometimes I am able to clear it by randomly enabling/disabling zones, sometimes I have to re-write config to the P25RX. It seems to have this behavior with or without roaming enabled.
I generally run everything in Zone 1, so the zones I am enabling/disabling should be arbitrary.
I will post a log once I catch it again.
I'm using LSM with the MPSCS Detroit simulcast and everything is sounding great.
2 questions about the new EVENT log.
1) Is it possible to get a timestamp included in the record output? That would be really useful on the patch entries to be able to notice a pattern related to the day/time period a recurring patch happens.
2) On the PATCH entries, what are the 3 digit numbers after each of the 2 TGID's?
Thanks in advance.
James
1) Is it possible to get a timestamp included in the record output? That would be really useful on the patch entries to be able to notice a pattern related to the day/time period a recurring patch happens.
2) On the PATCH entries, what are the 3 digit numbers after each of the 2 TGID's?
Thanks in advance.
James
The channel number that is associated with the group. Tuned frequency = base frequency + (channel * channel_spacing)
I have not seen this issue here. Hopefully this will get cleared up on the next update which will be significant.
@btt Hi there, I can't fully prove this but figured I would report it as I see it... I have two p25rx on win10. Both running 2022-02-10-1045 Over the last month or so they locked up every 1-2 weeks to the point I lost my remote access to them., I'm back north they are in FL so I VNC to them. Just a blank black screen I couldn't get around. Last time I rebooted I turned off scrolling and they have been running without incident for 3 weeks so far. If that changes I'll mea culpa and let you know.
edit to this: the reason I slightly suspect the BT scrolling is the Broadcastify feeds stay active but with no audio from the BTConfig. I'm running the BTConfig to Virtual Audio ports to the Broadcastify.
edit to this: the reason I slightly suspect the BT scrolling is the Broadcastify feeds stay active but with no audio from the BTConfig. I'm running the BTConfig to Virtual Audio ports to the Broadcastify.
Last edited:
My experience with 2 receivers plugged into a MacBook Air or 1 receiver connected to an iMac is that the application memory used for each instance of JAVA slowly increases over time until the software stops running for lack of application memory. I typically reboot the radios when they approach 5GB of MacOS application memory to keep the software running/logging. That seems to avoid the problem. Not sure if that scenario would be similar with Windows.
Thanks, just looked, been running 3+ weeks now with scrolling turned off and its sitting at 5g of 31g so I don't think that's the issue in this case.
@btt Hi, following up on the java statement.. do you know of a memory leak in BTConfig? or what is the memory usage that is normal? I'm going to monitor now that kb8q has me nervous.... My overall is sitting at 5.8g with the two java instances at 89.5m and 120.2m right now. I'll see if it climbs over the next few days. Thanks
It will take up memory if you let it. It is highly dependent on the Java Virtual Machine implementation. If you aren't having problems, I wouldn't worry about it too much. You could make some batch files to start the software with command line options that will limit the memory usage like: java -Xmx256m -Xms256m -jar BTConfig.exe (note that case and no spaces is important for those options) This would limit the usage to 256 Megabytes if that option works right on your platform. I did work on optimizing memory usage to slow it down on the latest versions I'm working on. It will be a while before I can port to the P25RX.
There is a new release available. 2022-06-01_0432. This version is for those currently running the stable release (02-10_1045) that experience an occasional firmware lock-up. This release is identical to the 02-10_1045 release, but with some changes to the drivers taken from the experimental release. The driver changes fix the lock-up issue. The issue became more noticeable with the experimental release (with scanning support) because it is related to frequency changes. Version 2022-06-01_0432 will become the new stable release after some testing.
FreqNout
Member
Sorry. I put it in the wrong thread. This only applies to the P25RX-II.
This post does apply to the P25RX (not the P25RX-II). I currently have a P25RX connected to a hardware debugger (as of this morning). I will let it run and see if we can catch a lock-up. I don't think I ever observed a lock-up issue with the P25RX and the latest release, but I may not have let it run long enough. As @epersson indicated, it may take a week or two for the unit(s) he has running. If it locks up, I may be able to find out what code is causing it and get it fixed.
dispatchgeek
Control channel goes "brrrrr"
The type of lock-up I'm referring to would be a firmware lock-up. Restarting the java software would not get it going again. It would require a power cycle to get it working. As I said, I have not observed this with the latest firmware, but this is what I'm currently testing for.
- Status
