MStep
Member
What makes the difference---- do you suspect that the voltage used in mobile operation is somehow affecting the firmware?
No, there are lots of variables. There is definitely room for improvement. I'm working on this now. When you are mobile, the incoming signal is obviously changing in ways that it would not if you were stationary. The difference is in how the various filters, synchronization, bit decision, error detection / handling work. I'm currently working on improving all of these things based on I/Q files sent in by customers. The idea is that I will be able to make a change and create a summary of performance across all available I/Q files to determine if that change to any parameter is going to make a positive or negative impact overall. I hope to have some improved firmware based on this idea soon.What makes the difference---- do you suspect that the voltage used in mobile operation is somehow affecting the firmware?
No, the next update for the P25RX is going to be a lot of work. It will take some time. It will be worth the wait.Is all development now for the P25RX-II only? This has got to be the longest I've ever seen the FW thread quiet.
Is all development now for the P25RX-II only? This has got to be the longest I've ever seen the FW thread quiet.
Well, This FW thread is no longer quietThis has got to be the longest I've ever seen the FW thread quiet.
I agree completely. I have original P25RX and P25RX-ll playing right now, excellent audio from both.I have been using my P25RX for about one year. The current FW works great on the systems I monitor in the metro-Atlanta area! Its a great product!
No sir, I didn't take that way at all. It was quiet for a while. No worries at all!Everyone: I only asked because the forum was unusually quiet. I didn't criticize Todd or his business, and I never said there was a thing wrong with my P25RX, although judging by the posts, that appears to be the belief. I do not understand the tendancy of internet forum members to pile on for any perceived heresy. It's been this way since Usenet (and I saw it on Arpanet text file "chats" even before that).
I'll only say I am the owner of quite a few pieces of hardware that started with great intention and frequent updates that eventually just petered out in favor of the update of the newer models because of lack of ram, cpu, etc in the old hardware.. I keep my senses tuned for when and if that happens, so I can be ready to upgrade (or not, some just keep working, even when no longer updated).
Thanks Todd. I have the greatest respect for the business you have created here, and the superlative customer service that you provide. Thanks.No sir, I didn't take that way at all. It was quiet for a while. No worries at all!
It detected encryption so it didn't pass the audio.@btt Hi, loaded ver 11-16-23:26 Now getting this message. Just don't know what it means besides the obvious, thanks
P25P2 system no roaming. Getting a lot of them on this version.
TDMA Phase II sync, freq: 771.556250, rssi: -75 dBm, TGroup: 12051, Desc: PB BSO West, erate: 0.000 $
$TDMA: no audio due to !found_alg
$TDMA: no audio due to !found_alg
Possible but those channels are seldom encrypted. Usually they move to a different tac for that. and I have seen in the log encrypted skipping, but that was not shown.It detected encryption so it didn't pass the audio.
I looked through the code to verify this. The only thing that will cause that message is when a MAC PTT message is received for the currently monitored talk group and the message indicates that the voice is encrypted. You will see this message when this happens: '$TDMA current talk group is encrypted'. These messages are fully validated by CRC.@btt Hi, loaded ver 11-16-23:26 Now getting this message. Just don't know what it means besides the obvious, thanks
P25P2 system no roaming. Getting a lot of them on this version.
TDMA Phase II sync, freq: 771.556250, rssi: -75 dBm, TGroup: 12051, Desc: PB BSO West, erate: 0.000 $
$TDMA: no audio due to !found_alg
$TDMA: no audio due to !found_alg
Thanks. I’ve see the encrypted message as well. They are PD channels so that’s not surprising. But I am getting these sequences with no encryption notice message. This is a copy and paste. I had never seen them before I updated to this rev.I looked through the code to verify this. The only thing that will cause that message is when a MAC PTT message has been received for the currently monitored talk group and the message indicates that the voice is encrypted (prior to receiving voice). You will see this message when the MAC PTT is received: '$TDMA current talk group is encrypted'. These messages are fully validated by CRC.
I found it. I believe this issue is fixed in version 12-09_0713.Thanks. I’ve see the encrypted message as well. They are PD channels so that’s not surprising. But I am getting these sequences with no encryption notice message. This is a copy and paste. I had never seen them before I updated to this rev.