Yes, agree with beischel. 1928 is a winner. Recordings are so much better. Really like this one Todd. Thanks for correcting the issues.
P25RX Firmware Updates / Testing
- Thread starter btt
- Start date
Thank you for the feedback! I'm really glad to hear that we finally got this figured out. I've heard positive feedback from a couple of others as well.
brndnstffrd
Member
This is kind of a minor issue more than anything, but I have noticed that on occasion the P25RX will stop adding RID's to the alias log. It still logs them correctly in the log and the display, and all other log functions work correctly. It is entirely possible that it is an issue on my end with the specific computer and not a software glitch, however the last time it wrote to the log was on 2/6 and even if i manually go into the RID Alias screen and edit something, it will let me make changes in the software, however it doesnt save them to the log file, and the disappear if i close and reopen the software. I almost think that it might be something as simple as adding a save or export button would fix it because the software might not be pointing to the existing Alias file for whatever reason. Beyond that im really not sure, but im willing to give whatever suggestions you have a shot.
I see the $ZONE$ and %ZONE_ALIAS$ keywords were added. The $ZONE$ keyword is working - how is the ZONE_ALIAS configured or setup?
Press the shift key, then press the zone button. A window will pop up that will let you enter the zone alias. If you hold the mouse over the buttons, you will see the text.
I took the plunge and updated to 2022-02-04-1928. One really neat feature is I am locking on a major incident, and happened this morning with a multifamily structure fatal structure fire. The zone buttons let me select the tac quick.
One minor point is the logging is still screwed up on the one P25. is shows as if is can't identify the name in the TGID table and just shows the TG ID. I've done a flash reset and reload to no avail.
i: -75 tsbk_ps 25 sa 1 ue 1 wacn_id 0xbee00 sys_id 0x997 nac 0x991 rf_id 1 site_id 1 freq 774.906250 rfg 23 agc -31.9 tgzone 1 $
P25_SITE,PRIMARY,774.906250 $
control is switching to monitor grant for talkgroup on freq 772.581250
==============================================================================================
$TDMA_PTT talk group 11015, non-encrypted
P25_PII: SRC_RID: 118 GRP 11015 $
P25_PII: SRC_RID: 118 GRP 11015 $
P25_PII: SRC_RID: 118 GRP 11015 $
P25_PII: SRC_RID: 118 GRP 11015 $
TG Table:
true 0x997 1 11015 Dispatch 6 0xbee00 1
The other (below) shows the entries correctly the log settings are identical and no mods make a difference.
MA VOICE GRANT_00, freq 772.331250, tgroup: 12051, slot: 1
SYS_INFO wacn 0xbee00 sys_id 0x997 nac 0x991 cc_freq 774.906250 $
==============================================================================================
grant (0x00) packet_idx 1, tgroup 12051 freq 772.3312 nac 2449 rf_channel 1653 follow: 0
desc: PB BSO West location:
control is switching to monitor grant for talkgroup on freq 772.331250
==============================================================================================
TDMA Phase II sync, freq: 772.331250, rssi: -72 dBm, TGroup: 12051, Desc: PB BSO West, erate: 0.000 $
$TDMA_PTT talk group 12051, non-encrypted
$TDMA_PTT talk group 12051, non-encrypted
TDMA Phase II sync, freq: 772.331250, rssi: -73 dBm, TGroup: 12051, Desc: PB BSO West, erate: 0.000 $
P25_PII: SRC_RID: 7812570 GRP 12051 $
One minor point is the logging is still screwed up on the one P25. is shows as if is can't identify the name in the TGID table and just shows the TG ID. I've done a flash reset and reload to no avail.
i: -75 tsbk_ps 25 sa 1 ue 1 wacn_id 0xbee00 sys_id 0x997 nac 0x991 rf_id 1 site_id 1 freq 774.906250 rfg 23 agc -31.9 tgzone 1 $
P25_SITE,PRIMARY,774.906250 $
control is switching to monitor grant for talkgroup on freq 772.581250
==============================================================================================
$TDMA_PTT talk group 11015, non-encrypted
P25_PII: SRC_RID: 118 GRP 11015 $
P25_PII: SRC_RID: 118 GRP 11015 $
P25_PII: SRC_RID: 118 GRP 11015 $
P25_PII: SRC_RID: 118 GRP 11015 $
TG Table:
true 0x997 1 11015 Dispatch 6 0xbee00 1
The other (below) shows the entries correctly the log settings are identical and no mods make a difference.
MA VOICE GRANT_00, freq 772.331250, tgroup: 12051, slot: 1
SYS_INFO wacn 0xbee00 sys_id 0x997 nac 0x991 cc_freq 774.906250 $
==============================================================================================
grant (0x00) packet_idx 1, tgroup 12051 freq 772.3312 nac 2449 rf_channel 1653 follow: 0
desc: PB BSO West location:
control is switching to monitor grant for talkgroup on freq 772.331250
==============================================================================================
TDMA Phase II sync, freq: 772.331250, rssi: -72 dBm, TGroup: 12051, Desc: PB BSO West, erate: 0.000 $
$TDMA_PTT talk group 12051, non-encrypted
$TDMA_PTT talk group 12051, non-encrypted
TDMA Phase II sync, freq: 772.331250, rssi: -73 dBm, TGroup: 12051, Desc: PB BSO West, erate: 0.000 $
P25_PII: SRC_RID: 7812570 GRP 12051 $
Do you ever see any lines that start with '$TDMA Phase II sync:' for the talk group that isn't showing up? I can't see anything that would cause an issue like that.
Hi, I don't see it, shws the slot # but not that sync line.
22 TGs in the list. 1 shows correctly. This started when I did an upgrade back in August.
also I didn't mention ONE channel comes across correctly, its one in a list of 20 channels.
SITE,PRIMARY,774.906250 $
SYS_INFO wacn 0xbee00 sys_id 0x997 nac 0x991 cc_freq 774.906250 $
$TDMA VOICE GRANT_00, freq 772.856250, tgroup: 11021, slot: 0
SYS_INFO wacn 0xbee00 sys_id 0x997 nac 0x991 cc_freq 774.906250 $
==============================================================================================
grant (0x00) packet_idx 1, tgroup 11021 freq 772.8562 nac 2449 rf_channel 1736 follow: 0
desc: Dispatch 8 Hollywood location:
control is switching to monitor grant for talkgroup on freq 772.856250
==============================================================================================
TDMA Phase II sync, freq: 772.856250, rssi: -74 dBm, TGroup: 11021, Desc: Dispatch 8 Hollywood, erate: 0.000 $
$TDMA_PTT talk group 11021, non-encrypted
$TDMA_PTT talk group 11021, non-encrypted
P25_PII: SRC_RID: 7876113 GRP 11021 $
TDMA Phase II sync, freq: 772.856250, rssi: -75 dBm, TGroup: 11021, Desc: Dispatch 8 Hollywood, erate: 0.000 $
P25_PII: SRC_RID: 7876113 GRP 11021 $
TDMA Phase II sync, freq: 772.856250, rssi: -76 dBm, TGroup: 11021, Desc: Dispatch 8 Hollywood, erate: 0.000 $
P25_PII: SRC_RID: 7876113 GRP 11021 $
TDMA Phase II sync, freq: 772.856250, rssi: -76 dBm, TGroup: 11021, Desc: Dispatch 8 Hollywood, erate: 0.000 $
TDMA Phase II sync, freq: 772.856250, rssi: -75 dBm, TGroup: 11021, Desc: Dispatch 8 Hollywood, erate: 0.000 $
Todd,
Latest firmware( LATEST RELEASE 02-07_0013) sounds great BUT when I open it up, I get a short look at the page then when the P25RXII connects, the screen minimizes and I can't get it to maximize.. The P25RXII is receiving but I can not see the screen to change anything.. Win10 PC All other versions worked
Latest firmware( LATEST RELEASE 02-07_0013) sounds great BUT when I open it up, I get a short look at the page then when the P25RXII connects, the screen minimizes and I can't get it to maximize.. The P25RXII is receiving but I can not see the screen to change anything.. Win10 PC All other versions worked
Give 02-09_1245 a try. Note that this is the P25RX thread. The fix is for the P25RX-II.
I am getting garbled/dropped audio with the last two releases (2-07 and 2-10). I've tried both PC Audio (my normal method) and BT, and both are similar. No changes to my physical setup/location, and my RF Sig Level is showing 2.5 green bars (avg around -70dBm). Is it possible to reload an older version? Or any other suggestions?
For reference, my Unication is fine with the same TGs.
For reference, my Unication is fine with the same TGs.
Yes, you can reload an older version. First, you might try changing the demod mode on the P25RX Config tab. Most likely, that is the cause. There are only two choices currently. Select whatever the other mode is and see if that works better. Would be good to know if that doesn't solve the issue.
Hey Todd!
Speaking of the P25 Modulation type choices.
I have a statewide system here that uses CQPSK/C4FM for the non simulcast VHF sites and then LSM for the 800 MHz sites.
I can no longer roam between these sites as the P25 mode will be wrong when it roams from a VHF to a 800 MHz LSM site for example.
I know that a write to the P25RX occurs each time you wish to change the P25 Modulation type so setting the modulation type in the frequency DB stored in the P25 RX would not be a good idea as each time it roamed to a different type of site on this system, you'd have that long delay while it writes the new mode to the P25RX!
Is there a faster way to switch the P25 modulation type that does not require a write to the P25 each time you change the P25 Modulation type?
If so, then perhaps a P25 Modulation column could be added within the frequency DB table stored in the P25RX so users with these multi mode (modulation) P25 systems could still utilize the roaming feature.
I did try monitoring both types of P25 sites here while altering the P25 modulation type and the audio gets really bad and broken when the mode is not set correctly on an LSM site or C4FM site.
So for now, I just monitor the C4FM VHF sites but I do miss traffic is I must disable roaming so it does not roam to the 800 MHz LSM site!
Of course I must select LSM mode when I do monitor this systems 800 MHz sites but then reception of the CQPSK/C4FM sites goes down the drain.
I do love the ability to be able to change the P25 Modulation type however as it does help a lot in clearing up audio so hopefully there will be some way of changing the P25 mode from one to the other on the fly depending on a value set by the user in the frequency DB perhaps.
Thanks
This is a good point and one that I'm working on. The delay is not due to changing the demod mode, so that isn't an issue. I am working on a new version of the software that will have many more options for each frequency defined. What is now the roaming table will become the channel configuration table with fields for enable, sys_name, channel_type, frequency, channel profile, demod type, channel filter, and DMR_LCN (if applicable). Due to all the things I am trying to juggle, this may take a while to complete the new software/firmware. In the meantime, I will work on getting an extra column added to the existing firmware/software for the roaming mode/demod type.
That all sounds great Todd!
I also figured you were probably already looking into how to handle quick P25 mode changes for those that monitor systems like the MOSWIN system here that has a mix of mostly CQPSK/C4FM VHF and 700 MHz sites along with a handful or two of LSM type 7/800 MHz sites mostly within the large city areas like St Louis and Springfield, MO at least.
I switched to 'CQPSK/C4FM' and that helped with the audio. I've never changed this setting before, so I'm not sure why it started having problems. This is on the Michigan MSPSC 800MHz system. I'll keep monitoring it, and try switching back and forth to make sure that is the issue. Is there a way to determine what P25 Modulation setting should be used for a particular system?
It is a new option. It may auto-detect in a future version (this is the intent). For now, you will need to determine which of the two settings works better. If you are monitoring a system with linear amps and true QPSK output, then (linear simulcast modulation) the LSM option will give better performance.
I've switched back and forth between the two modes, and that was definitely my audio issue. CQPSK/C4FM isn't garbled and doesn't drop audio.
Thanks for the help!
Thanks for the help!
Similar threads
