P25RX Firmware Updates / Testing

[FP761]

@FP761,

Try the following command in the console:

$ add_tdu_silence 0
$ save

Does this help? This command disables adding a short period of silence to the audio output buffer when a TDU/TDULC is received. The yellow areas on the sync line indicate an incoming TDU/TDULC. This only applies to phase 1 decoding.

Todd,

Still using version "1808", I entered the commands indicated. I have only heard a few voices transmissions so far, but my perception is that there is improvement, and I haven't heard any "chop" yet. An additional observation is on the "Signal Insights" page, the I/Q Plot now appears different. Could this be due to current atmospheric conditions?
.

 

[btt]

Todd,

Still using version "1808", I entered the commands indicated. I have only heard a few voices transmissions so far, but my perception is that there is improvement, and I haven't heard any "chop" yet. An additional observation is on the "Signal Insights" page, the I/Q Plot now appears different. Could this be due to current atmospheric conditions?
.

I think the I/Q symbol plot probably looks different because "auto scale" got turned off. Thanks for reporting on the 'add_tdu_silence' option. I am going to make this option default off for the next release.

 

[FP761]

I think the I/Q symbol plot probably looks different because "auto scale" got turned off. Thanks for reporting on the 'add_tdu_silence' option. I am going to make this option default off for the next release.

Excellent. I will continue to monitor over the next few days and provide an update. Thanks for your continued support as always!

 

[kinglou0]

Thank you to the admin for giving us our own sub forum!!

Well deserved and I'm sure it makes things a little more organized.

 

[Cheeseburgers]

I went back to 1047, had the 0 BLKS per sec again

 

[epersson]

I don’t know which system this is. I suspect FLL which lists as a P2 but displays as a P1. Very frequently I am getting green sig and a TG goes active. The sig starts flashing fast green the audio goes choppy and then drops out. I’ll email a short video direct. I can’t attach it.

 

[epersson]

I don’t know which system this is. I suspect FLL which lists as a P2 but displays as a P1. Very frequently I am getting green sig and a TG goes active. The sig starts flashing fast green the audio goes choppy and then drops out. I’ll email a short video direct. I can’t attach it. Latest stabile firmware

 

[btt]

I don’t know which system this is. I suspect FLL which lists as a P2 but displays as a P1. Very frequently I am getting green sig and a TG goes active. The sig starts flashing fast green the audio goes choppy and then drops out. I’ll email a short video direct. I can’t attach it.

The green flashing led is most likely the TDU period (idle time with no voice). I didn't see an email with the video link.

 

[epersson]

The green flashing led is most likely the TDU period (idle time with no voice). I didn't see an email with the video link.

I got pulled away. I’ll send it in a bit. I can’t send it from My phone. Have to power up the laptop.

 

[epersson]

I got pulled away. I’ll send it in a bit. I can’t send it from My phone. Have to power up the laptop.

The led starts flashing in the middle of a conversation. Then dumps audio. I can hear the rest of it on my 100.

 

[btt]

The led starts flashing in the middle of a conversation. Then dumps audio. I can hear the rest of it on my 100.

I didn't see this before replying to the email, but I'll reply here too. The led flashing green (TDU/idle period) as in the video and listening to the audio sounds like the TG timeout expired (default of 2 seconds) for a different talk group and what you are hearing is the very end of a conversation on a different talk group? Try setting the TG Timeout value to a low value like 100ms on the P25RX Config tab. Does that help?

 

[btt]

A firmware bug has been discovered. I'm not sure how long it has been in there, but it is present in the "latest stable" version. This emerged while emailing @epersson. He sent a video showing garbage characters showing up in the console. I think others have reported this, but I never did understand that Bluetooth being enabled is what led to the issue. This issue is almost certainly related to the last remaining issue with the P25RX /Display (why I have not shipped any displays yet). If you are running BTConfig and you enable Bluetooth, you may see garbage characters show up in the console periodically and eventually the BTConfig software will lock-up. I think I have been testing Bluetooth on new units without running the BTConfig software, so did not catch it then. I hope those of you who are waiting for me to have more units ready to sell won't mind if I get this issue figured out before finishing the build.

 

[epersson]

A firmware bug has been discovered. I'm not sure how long it has been in there, but it is present in the "latest stable" version. This emerged while emailing @epersson. He sent a video showing garbage characters showing up in the console. I think others have reported this, but I never did understand that Bluetooth being enabled is what led to the issue. This issue is almost certainly related to the last remaining issue with the P25RX /Display (why I have not shipped any displays yet). If you are running BTConfig and you enable Bluetooth, you may see garbage characters show up in the console periodically and eventually the BTConfig software will lock-up. I think I have been testing Bluetooth on new units without running the BTConfig software, so did not catch it then. I hope those of you who are waiting for me to have more units ready to sell won't mind if I get this issue figured out before finishing the build.

Sorry to anyone waiting on hardware. ☺️

 

[btt]

Sorry to anyone waiting on hardware. ☺

Not your fault : ) That is on me.

--------
Results from today:

Based on today's experience, I am starting to come to the conclusion that some USB host ports will not allow more than 500mA peaks in USB 2.0 mode, even if they are capable of supplying more than 500mA current and the average current draw is less than 500mA. With the latest version (2021-03-07_1559), If you enable Bluetooth and you see garbage characters in the console and the console information stops, then you are experiencing this issue. You will need to use a different port or you can use a powered USB hub that will supply more current. This unit is similar (but different) to the one that I experience no issues with: https://www.amazon.com/AmazonBasics-Port-2-5A-power-adapter/dp/B00DQFGH80 Again, I'm not 100% sure that this is the issue and there may still be a firmware resolution possible.

While trying to figure this issue out, I believe many improvements were made to the firmware and software with regards to USB communications. Everyone should install the new "latest stable" version: 2021-03-07_1559. Let me know if you find any major issues (other than scanning related. I will work on improving scanning soon).

 

[btt]

Already found a case that needs to be fixed. Sorry. Here is the latest:

-edit: link removed due to another issue.

 

[Cheeseburgers]

think this bricked my device... cant get into bootloader mode

 

[btt]

think this bricked my device... cant get into bootloader mode

The last link I removed made the audio worse due to a delay, but shouldn't have bricked anything. Have you tried the "hold button for 10 seconds on power-up method?"

 

[Cheeseburgers]

yep, but 1754 just stops at discovering device.

 

[Cheeseburgers]

cant roll back either, stops halfway at discovering device every time.

 

[Cheeseburgers]

I think I may have hit my frustration limit here.. sorry Todd.