P25RX Firmware Updates / Testing

[btt]

Is there a waiting list for the displays? Are they available? Price

Yes, there is a list. There aren't any available currently. I'm getting closer. Contact me via email for pricing. I will have it on the web site soon.

Todd........new antennas?

Yes, I should have some new portable antennas available soon. They will utilize the same helical antenna as the 700/800 mag-mount that comes with the P25RX. The threaded post is the same. They will consist of a small pcb with an SMA male connector, the post for the helical antenna at a right-angle, some matching components, and two flexible coax counterpoise radials to give good performance (unlike most portable monopoles). I'll share an image when the final boards show up.

 

[Tinkerwave]

Would fractal antennas help improve reception? If so, is that something you'd be interested in designing, making, and selling?

 

[btt]

Would fractal antennas help improve reception? If so, is that something you'd be interested in designing, making, and selling?

Fractal antennas do sound interesting. I don't think I will be working on one. Is this something you have experimented with?

 

[KC1UA]

Hello,

Using the latest stable version of BTConfig, I am experiencing a significant amount of drop-outs on a strong conventional P25 system that has recently come online in my area. Testing against a BCD436HP and DSD+, the P25RX is not receiving nearly as well. All devices are using the same antenna through a multicoupler. The signal I am receiving has an RSSI of -75. I'm attaching some of the console log to show the dropouts. I searched the thread and noticed mention of dropouts on VHF P25 systems, but I anticipate they refer to a trunked system and not conventional.

  ->(VOICE), freq: 156.217500, rssi: -105 dBm, TGroup: 0, Desc: , Time: 2056452 rfg 41, agc -32.9 $ ***___**,vql, $
  ->(VOICE), freq: 156.217500, rssi: -93 dBm, TGroup: 0, Desc: , Time: 2056524 rfg 41, agc -32.8 $ *********
P25_P1: SRC_RID: 1212 $  GRP: 1,vqg, $
  ->(VOICE), freq: 156.217500, rssi: -81 dBm, TGroup: 0, Desc: , Time: 2056590 rfg 41, agc -32.8 $ *********,vqg, $
  ->(VOICE), freq: 156.217500, rssi: -69 dBm, TGroup: 0, Desc: , Time: 2056666 rfg 41, agc -32.8 $ *********
P25_P1: SRC_RID: 8389820 $  GRP: 1,vqg, $
  ->(VOICE), freq: 156.217500, rssi: -77 dBm, TGroup: 0, Desc: , Time: 2056728 rfg 41, agc -32.6 $ *********,vqg, $
  ->(VOICE), freq: 156.217500, rssi: -77 dBm, TGroup: 0, Desc: , Time: 2056794 rfg 41, agc -33.1 $ *********
P25_P1: SRC_RID: 1212 $  GRP: 1,vqg, $
  ->(VOICE), freq: 156.217500, rssi: -77 dBm, TGroup: 0, Desc: , Time: 2056857 rfg 41, agc -32.9 $ *****__,vql, $
  ->(VOICE), freq: 156.217500, rssi: -77 dBm, TGroup: 0, Desc: , Time: 2057027 rfg 41, agc -33.0 $ *********,vqg, $
  ->(VOICE), freq: 156.217500, rssi: -77 dBm, TGroup: 0, Desc: , Time: 2057089 rfg 41, agc -32.1 $ ******_**
P25_P1: SRC_RID: 1212 $  GRP: 1,vqb, $
  ->(VOICE), freq: 156.217500, rssi: -77 dBm, TGroup: 0, Desc: , Time: 2057153 rfg 41, agc -33.1 $ _********,vqb, $
  ->(VOICE), freq: 156.217500, rssi: -77 dBm, TGroup: 0, Desc: , Time: 2057216 rfg 41, agc -33.0 $ *********
P25_P1: SRC_RID: 1212 $  GRP: 1,vqg, $
  ->(VOICE), freq: 156.217500, rssi: -77 dBm, TGroup: 0, Desc: , Time: 2057267 rfg 41, agc -33.3 $ *******_,vql, $
  ->(VOICE), freq: 156.217500, rssi: -77 dBm, TGroup: 0, Desc: , Time: 2057338 rfg 41, agc -33.0 $ *********
P25_P1: SRC_RID: 1212 $  GRP: 1,vqg, $
  ->(VOICE), freq: 156.217500, rssi: -77 dBm, TGroup: 0, Desc: , Time: 2057404 rfg 41, agc -33.0 $ *********,vqg, $
  ->(VOICE), freq: 156.217500, rssi: -77 dBm, TGroup: 0, Desc: , Time: 2057467 rfg 41, agc -33.2 $ *******_*
P25_P1: SRC_RID: 1212 $  GRP: 1,vqb, $
  ->(VOICE), freq: 156.217500, rssi: -77 dBm, TGroup: 0, Desc: , Time: 2057635 rfg 41, agc -33.3 $ *********
P25_P1: SRC_RID: 1212 $  GRP: 1,vqg, $
  ->(VOICE), freq: 156.217500, rssi: -77 dBm, TGroup: 0, Desc: , Time: 2057693 rfg 41, agc -33.2 $ *******__,vql, $
  ->(VOICE), freq: 156.217500, rssi: -77 dBm, TGroup: 0, Desc: , Time: 2057845 rfg 41, agc -33.2 $ *********.

Thanks for the continued great work, Todd.

 

[btt]

Hello,

Using the latest stable version of BTConfig, I am experiencing a significant amount of drop-outs on a strong conventional P25 system that has recently come online in my area. Testing against a BCD436HP and DSD+, the P25RX is not receiving nearly as well. All devices are using the same antenna through a multicoupler. The signal I am receiving has an RSSI of -75. I'm attaching some of the console log to show the dropouts. I searched the thread and noticed mention of dropouts on VHF P25 systems, but I anticipate they refer to a trunked system and not conventional.

Have you tried changing the P1 channel filter bandwidth around to see if it improves? It is a new configuration setting on the advanced tab.

 

[KC1UA]

Have you tried changing the P1 channel filter bandwidth around to see if it improves? It is a new configuration setting on the advanced tab.

I did, over a variety of settings, but didn't see any constant improvement anywhere. I went back to default setting at that point.

 

[btt]

I don't think it would be related to conventional. From your listing, it does appear I may have broken the talk group code for conventional. I will take a look at that. It was working in the past. The new bandwidth settings seemed to fix issues that two others that were having VHF.

 

[Tinkerwave]

Fractal antennas do sound interesting. I don't think I will be working on one. Is this something you have experimented with?

This fractal antenna has a range of 100-2700MHZ wideband:

Fractal Antenna Systems - Products

Our products remove the need to compromise. We deliver wideband performance, market leading gain, and aesthetic form-factors all at a competitive price.

www.fractenna.com

The owner of the site, W1YW, also designs and makes custom fractal antennas. If you're interested, you might want to partner with him?

 

[btt]

I probably should clarify why I will be offering another antenna. Some people don't consider the antenna that comes with the P25RX to be portable because it has a coax line on it. It works fine. It does have a counterpoise ground in the base. I tried ordering a cheap monopole antenna for testing, but the performance was very poor due to being a monopole. By adding the radials, performance of the monopole is dramatically improved (due to the radials effectively making it a dipole). Lets move any further discussion of antennas to an antenna thread.

 

[Cheeseburgers]

I use a sma base with a sma to bnc adapter and a Shure 774-865 antenna and the reception in most places, work and home is 3 - 4 bars, adverse weather requires i reposition occasionally thats it.

 

[btt]

Hello,

Using the latest stable version of BTConfig, I am experiencing a significant amount of drop-outs on a strong conventional P25 system that has recently come online in my area. Testing against a BCD436HP and DSD+, the P25RX is not receiving nearly as well. All devices are using the same antenna through a multicoupler. The signal I am receiving has an RSSI of -75. I'm attaching some of the console log to show the dropouts. I searched the thread and noticed mention of dropouts on VHF P25 systems, but I anticipate they refer to a trunked system and not conventional.

  ->(VOICE), freq: 156.217500, rssi: -105 dBm, TGroup: 0, Desc: , Time: 2056452 rfg 41, agc -32.9 $ ***___**,vql, $
  ->(VOICE), freq: 156.217500, rssi: -93 dBm, TGroup: 0, Desc: , Time: 2056524 rfg 41, agc -32.8 $ *********
P25_P1: SRC_RID: 1212 $  GRP: 1,vqg, $
  ->(VOICE), freq: 156.217500, rssi: -81 dBm, TGroup: 0, Desc: , Time: 2056590 rfg 41, agc -32.8 $ *********,vqg, $
  ->(VOICE), freq: 156.217500, rssi: -69 dBm, TGroup: 0, Desc: , Time: 2056666 rfg 41, agc -32.8 $ *********
P25_P1: SRC_RID: 8389820 $  GRP: 1,vqg, $
  ->(VOICE), freq: 156.217500, rssi: -77 dBm, TGroup: 0, Desc: , Time: 2056728 rfg 41, agc -32.6 $ *********,vqg, $
  ->(VOICE), freq: 156.217500, rssi: -77 dBm, TGroup: 0, Desc: , Time: 2056794 rfg 41, agc -33.1 $ *********
P25_P1: SRC_RID: 1212 $  GRP: 1,vqg, $
  ->(VOICE), freq: 156.217500, rssi: -77 dBm, TGroup: 0, Desc: , Time: 2056857 rfg 41, agc -32.9 $ *****__,vql, $
  ->(VOICE), freq: 156.217500, rssi: -77 dBm, TGroup: 0, Desc: , Time: 2057027 rfg 41, agc -33.0 $ *********,vqg, $
  ->(VOICE), freq: 156.217500, rssi: -77 dBm, TGroup: 0, Desc: , Time: 2057089 rfg 41, agc -32.1 $ ******_**
P25_P1: SRC_RID: 1212 $  GRP: 1,vqb, $
  ->(VOICE), freq: 156.217500, rssi: -77 dBm, TGroup: 0, Desc: , Time: 2057153 rfg 41, agc -33.1 $ _********,vqb, $
  ->(VOICE), freq: 156.217500, rssi: -77 dBm, TGroup: 0, Desc: , Time: 2057216 rfg 41, agc -33.0 $ *********
P25_P1: SRC_RID: 1212 $  GRP: 1,vqg, $
  ->(VOICE), freq: 156.217500, rssi: -77 dBm, TGroup: 0, Desc: , Time: 2057267 rfg 41, agc -33.3 $ *******_,vql, $
  ->(VOICE), freq: 156.217500, rssi: -77 dBm, TGroup: 0, Desc: , Time: 2057338 rfg 41, agc -33.0 $ *********
P25_P1: SRC_RID: 1212 $  GRP: 1,vqg, $
  ->(VOICE), freq: 156.217500, rssi: -77 dBm, TGroup: 0, Desc: , Time: 2057404 rfg 41, agc -33.0 $ *********,vqg, $
  ->(VOICE), freq: 156.217500, rssi: -77 dBm, TGroup: 0, Desc: , Time: 2057467 rfg 41, agc -33.2 $ *******_*
P25_P1: SRC_RID: 1212 $  GRP: 1,vqb, $
  ->(VOICE), freq: 156.217500, rssi: -77 dBm, TGroup: 0, Desc: , Time: 2057635 rfg 41, agc -33.3 $ *********
P25_P1: SRC_RID: 1212 $  GRP: 1,vqg, $
  ->(VOICE), freq: 156.217500, rssi: -77 dBm, TGroup: 0, Desc: , Time: 2057693 rfg 41, agc -33.2 $ *******__,vql, $
  ->(VOICE), freq: 156.217500, rssi: -77 dBm, TGroup: 0, Desc: , Time: 2057845 rfg 41, agc -33.2 $ *********.

Thanks for the continued great work, Todd.

Release 2021-05-27_1909 is available. It fixes the talk group information for P25 conventional mode.

 

[KC1UA]

Thanks! I'll test ASAP!

 

[shirsch101]

1909 working great for me

 

[btt]

New version available. Version 2021-06-02_1651 is an update of all MCU peripheral drivers. It appears the driver updates resolved the issue where Windows would not recognize the device after a re-boot (no need to cycle power after re-boot). There are a lot of changes in there. Let me know if you find any issues.

 

[Cheeseburgers]

New version available. Version 2021-06-02_1651 is an update of all MCU peripheral drivers. It appears the driver updates resolved the issue where Windows would not recognize the device after a re-boot (no need to cycle power after re-boot). There are a lot of changes in there. Let me know if you find any issues.

ill give it a spin in the am

 

[1969Roadrunner]

Very nice not to have to cycle the power after re-boot in Win 10.

 

[kruser]

New version available. Version 2021-06-02_1651 is an update of all MCU peripheral drivers. It appears the driver updates resolved the issue where Windows would not recognize the device after a re-boot (no need to cycle power after re-boot). There are a lot of changes in there. Let me know if you find any issues.

Todd, with this version, I'm now seeing a ton of "sync state: -2 (TDU)" 's on the green control channel sync state line when the unit it just sitting on the control channel with no voice traffic.
I don't recall seeing that on older FW versions but if they did exist, they didn't cause the sync state green line to load up with yellow dots for each -2 (TDU) reported.

This is with the non-simulcast VHF P1 sites I monitor.

It's the green line that's now full of small yellow dots all the way across the screen mixed in with the green line. Past firmware versions always gave me a nice and solid flat green line all the way across when there was no voice traffic.
It looks like every time the sync state changes from 1 to -2, the yellow dots appear in the green sync status line of the signal insights screen. Again, this is with no voice traffic, the P25RX is just monitoring the control channel.
The sync state is changing rather rapidly between 1 (Synced) and -2 (TDU) as I watch that screen. I'd guess for every 2 or 3 "1 (Synced)" readings, I'll see a "-2 (TDU)" reading. Sometimes a few -2's in a row.
The white signal level line is still nice and flat with this new version and the P25 voice decode quality seems as good as the previous version.
The signal level itself from the VHF site is a steady -70 dBm.

I do not see the -2 (TDU) sync state messages when I monitor an 800 MHz P1 simulcast site

I also hate to say it but the need to power cycle three times under Win 7 appears to still be needed. That's not a big deal though but I'll admit that I was hopeful the need to power cycle had been fixed!! During all my testing, I've never needed to power cycle my P25RX when I use it on a Win 10 machine.
I still have several Win 7 machines that my work pays for extended support that get monthly updates still so a Win 7 machine is my primary machine for the radio hobby.

I'm going to revert back to 05-23-0456 just to make sure something has not changed in my environment.

EDIT: I rolled back to 05-23-0456 and my Sync State status is now a solid 1 (Synced) with a solid green sync line again so something in the newer version is messing with that part. At least that's what the signal insight's screen is showing me!
No -2 (TDU)'s at all reported with this older version.

The voice quality was still fine in the newest version.

One other note, with the older FW vesions. I always saw the sync state -2 (TDU)'s during voice channel decode. The green line would have a lot of yellow and some red dots when actually decoding voice.
With the new version 1651, it seemed like the sync state stayed at 1 (Synced) during voice channel decodes. It's like the entire sync state routine is displaying in reverse when comparing what it shows between the older versions and this new 1651 version!

I also noticed the IQ Symbol Plot is a lot fuller or more active on the new 1651 version compared to the older versions. That has changed as much as the sync state line and -2 (TDU) errors have changed it seems.
I did just go back to the new 1651 version again and what I said about the sync state line staying green but only during actual voice decoding is true. During voice decodes, the sync state line is green while they are talking plus the sync state: indicator stays on "1 (Synced)" the entire time of voice decoding and no -2 (TDU) are seen. As soon as the voice channel drops, it goes back to the new behavior showing the -2 (TDU) errors again.

 

[rbjzx9]

Installed 6/3_0743. Seems to be good so far, and sound quality is good too.

I'm also on Windows 7, and it needed to be power cycled 3 times for me as well.

Thanks BTT.

 

[btt]

The issue that was resolved is Windows 10 not recognizing the device after a re-boot. I think the issue with having to power-cycle during a firmware update on Windows 7 is more of a BTConfig / Win 7 issue and probably not so much a firmware issue. I tested Windows 10 here and rebooted several times with no issues. Anyone else still having an issue with Windows not recognizing the device after a reboot?

 

[rdlafore]

Running 0743 here. No reboots on a Win10 laptop. Audio is good here on the Cobb County Regional system.