P25RX P25 Phase 1/2/DMR Receiver With Bluetooth Audio Support

[kinglou0]

Fired up the new software. Monitoring Pierce County SCWCS/South Sound 911 South Simulcast tower in Eatonville. Was getting the following error when I first started.

control is switching to monitor grant for talkgroup on freq 771.131250
==============================================================================================
>== Conversation timed-out. Return To Control Channel Frequency 773.231250, rssi -68 ==<

rssi: -68 tsbk_ps 35 sa 1 ue 1 wacn_id 0xbee00 sys_id 0x3ac nac 0x000 rf_id 1 site_id 3 freq 773.231250 rfg 38 agc -23.0 $
$TDMA VOICE GRANT_02, freq 771.131250, tgroup: 40106, slot: 0
$TDMA need wacn, sys_id, and nac before P2 can decode
control is switching to monitor grant for talkgroup on freq 771.131250
==============================================================================================
>== Conversation timed-out. Return To Control Channel Frequency 773.231250, rssi -69 ==<

rssi: -69 tsbk_ps 35 sa 1 ue 1 wacn_id 0xbee00 sys_id 0x3ac nac 0x000 rf_id 1 site_id 3 freq 773.231250 rfg 38 agc -23.6 $
rssi: -69 tsbk_ps 35 sa 1 ue 1 wacn_id 0xbee00 sys_id 0x3ac nac 0x000 rf_id 1 site_id 3 freq 773.231250 rfg 38 agc -24.0 $
rssi: -70 tsbk_ps 35 sa 1 ue 1 wacn_id 0xbee00 sys_id 0x3ac nac 0x000 rf_id 1 site_id 3 freq 773.231250 rfg 38 agc -26.7 $
rssi: -72 tsbk_ps 35 sa 1 ue 1 wacn_id 0xbee00 sys_id 0x3ac nac 0x000 rf_id 1 site_id 3 freq 773.231250 rfg 38 agc -29.9 $
$TDMA VOICE GRANT_02, freq 771.131250, tgroup: 40106, slot: 0
$TDMA need wacn, sys_id, and nac before P2 can decode
control is switching to monitor grant for talkgroup on freq 771.131250
==============================================================================================
>== Conversation timed-out. Return To Control Channel Frequency 773.231250, rssi -68 ==<

Ended up increasing the talkgroup delay to 3 seconds and restarting the device. Started getting audio but extremely choppy and unintelligible.

Here's what is coming during up audio decode.

$TDMA VOICE GRANT_02, freq 771.131250, tgroup: 40106, slot: 1
$TDMA found 40-bit P25 Phase II sync @ 6000 sps!, p2 sync count: 1, rssi: -68 $
$TDMA found 40-bit P25 Phase II sync @ 6000 sps!, p2 sync count: 2, rssi: -70 $****
$TDMA found 40-bit P25 Phase II sync @ 6000 sps!, p2 sync count: 3, rssi: -70 $
$TDMA found 40-bit P25 Phase II sync @ 6000 sps!, p2 sync count: 4, rssi: -70 $********
$TDMA found 40-bit P25 Phase II sync @ 6000 sps!, p2 sync count: 5, rssi: -68 $
$TDMA found 40-bit P25 Phase II sync @ 6000 sps!, p2 sync count: 6, rssi: -68 $****
$TDMA found 40-bit P25 Phase II sync @ 6000 sps!, p2 sync count: 7, rssi: -68 $
$TDMA found 40-bit P25 Phase II sync @ 6000 sps!, p2 sync count: 8, rssi: -68 $******
$TDMA found 40-bit P25 Phase II sync @ 6000 sps!, p2 sync count: 9, rssi: -68 $
$TDMA found 40-bit P25 Phase II sync @ 6000 sps!, p2 sync count: 10, rssi: -68 $********
$TDMA found 40-bit P25 Phase II sync @ 6000 sps!, p2 sync count: 11, rssi: -68 $
$TDMA found 40-bit P25 Phase II sync @ 6000 sps!, p2 sync count: 12, rssi: -68 $****
$TDMA found 40-bit P25 Phase II sync @ 6000 sps!, p2 sync count: 13, rssi: -68 $
$TDMA found 40-bit P25 Phase II sync @ 6000 sps!, p2 sync count: 14, rssi: -68 $*_****
$TDMA found 40-bit P25 Phase II sync @ 6000 sps!, p2 sync count: 15, rssi: -68 $*****_**
$TDMA found 40-bit P25 Phase II sync @ 6000 sps!, p2 sync count: 17, rssi: -68 $
$TDMA found 40-bit P25 Phase II sync @ 6000 sps!, p2 sync count: 18, rssi: -68 $****
$TDMA found 40-bit P25 Phase II sync @ 6000 sps!, p2 sync count: 20, rssi: -68 $******
$TDMA found 40-bit P25 Phase II sync @ 6000 sps!, p2 sync count: 21, rssi: -68 $
$TDMA found 40-bit P25 Phase II sync @ 6000 sps!, p2 sync count: 23, rssi: -68 $
$TDMA found 40-bit P25 Phase II sync @ 6000 sps!, p2 sync count: 24, rssi: -68 $
$TDMA found 40-bit P25 Phase II sync @ 6000 sps!, p2 sync count: 25, rssi: -68 $
$TDMA found 40-bit P25 Phase II sync @ 6000 sps!, p2 sync count: 26, rssi: -68 $
$TDMA found 40-bit P25 Phase II sync @ 6000 sps!, p2 sync count: 27, rssi: -68 $
$TDMA found 40-bit P25 Phase II sync @ 6000 sps!, p2 sync count: 28, rssi: -68 $
$TDMA found 40-bit P25 Phase II sync @ 6000 sps!, p2 sync count: 29, rssi: -68 $
$TDMA found 40-bit P25 Phase II sync @ 6000 sps!, p2 sync count: 32, rssi: -68 $
$TDMA found 40-bit P25 Phase II sync @ 6000 sps!, p2 sync count: 33, rssi: -68 $
$TDMA found 40-bit P25 Phase II sync @ 6000 sps!, p2 sync count: 34, rssi: -68 $
$TDMA found 40-bit P25 Phase II sync @ 6000 sps!, p2 sync count: 35, rssi: -68 $
$TDMA found 40-bit P25 Phase II sync @ 6000 sps!, p2 sync count: 36, rssi: -68 $
$TDMA found 40-bit P25 Phase II sync @ 6000 sps!, p2 sync count: 37, rssi: -68 $
$TDMA found 40-bit P25 Phase II sync @ 6000 sps!, p2 sync count: 38, rssi: -68 $
$TDMA found 40-bit P25 Phase II sync @ 6000 sps!, p2 sync count: 40, rssi: -68 $
$TDMA found 40-bit P25 Phase II sync @ 6000 sps!, p2 sync count: 41, rssi: -68 $
$TDMA found 40-bit P25 Phase II sync @ 6000 sps!, p2 sync count: 42, rssi: -68 $
$TDMA found 40-bit P25 Phase II sync @ 6000 sps!, p2 sync count: 43, rssi: -68 $
$TDMA found 40-bit P25 Phase II sync @ 6000 sps!, p2 sync count: 44, rssi: -67 $
$TDMA found 40-bit P25 Phase II sync @ 6000 sps!, p2 sync count: 45, rssi: -67 $********
$TDMA voice timeout.
>== Conversation timed-out. Return To Control Channel Frequency 773.231250, rssi -116 ==<

bandicam 2020-08-25 22-00-08-776.mp4

 

[DewAddict]

Anyone try to bluetooth pair with a My Ford Touch Sync 3 system yet?

 

[btt]

Fired up the new software. Monitoring Pierce County SCWCS/South Sound 911 South Simulcast tower in Eatonville. Was getting the following error when I first started.

control is switching to monitor grant for talkgroup on freq 771.131250
==============================================================================================
>== Conversation timed-out. Return To Control Channel Frequency 773.231250, rssi -68 ==<

rssi: -68 tsbk_ps 35 sa 1 ue 1 wacn_id 0xbee00 sys_id 0x3ac nac 0x000 rf_id 1 site_id 3 freq 773.231250 rfg 38 agc -23.0 $
$TDMA VOICE GRANT_02, freq 771.131250, tgroup: 40106, slot: 0
$TDMA need wacn, sys_id, and nac before P2 can decode
control is switching to monitor grant for talkgroup on freq 771.131250
==============================================================================================
>== Conversation timed-out. Return To Control Channel Frequency 773.231250, rssi -69 ==<

kinglou0, Thanks for giving it a test and providing the output. The highlighted message indicates that the P25rx hasn't received the wacn, sys_id, and nac from the control channel yet. For Phase 2, these 3 values are needed to seed the xor descrambler. The talk group timeout doesn't affect that, but from the output, I can see that it is switching to monitor the voice channel anyway. Got that fixed. The tg timeout for Phase 2 was using a fixed value of 2 seconds. I've changed it to use the "talk group timeout" in the BTConfig software, so changing it to 3 seconds should actually make a difference.

The '*' characters are audio frames that decoded without errors, so I'm wondering if the voice audio in the video is encrypted since it was completely unintelligible. The new firmware can't detect Phase 2 encryption yet because I don't have the fec for that portion implemented.

A new (untested) version is available on the web site.

 

[btt]

kinglou0,
I see looking up the system on RR shows that the system_id should be 0x1e7, but the P25RX is showing a sys_id of 0x3ac. Can you verify the wacn, sys_id, and nac that the P25RX is displaying are all correct? (wacn and sys_id should be correct. they are crc checked). The P2 voice can't be decoded correctly without those 3 parameters being correct when the device receives the voice channel grant.

 

[boy7777777777]

I only have one phase 2 system in my area and it is not simulcast but I will set the unit to test the new firmware while I am at work today.

 

[Mike_G_D]

I am trying the new P2 software/firmware - it seems like the receiver is not logging talk groups when receiving P2 messages, at least in my case.

It seems like it just holds the P1 talk group in the Talk Group Log that it last noted (in P1 mode) while a P2 signal is being decoded.

The system I am monitoring generally has dedicated P2 talk groups (that can revert to P1 mode if a P1 only capability subscriber is part of the conversation) but I am only logging and seeing the P1 talk groups while I am hearing P2 voice. I can tell it is completely unrelated to the talk group displayed which is the P1 talk group and I can see the TDMA Phase II messages in the Console messages.

And like kinglou0 above, I am hearing some encrypted voice on some P2 signals unlike for P1 signals wherein encrypted is muted.

This is the release dated for today, 8/26/2020, downloaded just a couple hours ago.

-Mike

 

[btt]

I am trying the new P2 software/firmware - it seems like the receiver is not logging talk groups when receiving P2 messages, at least in my case.

It seems like it just holds the P1 talk group in the Talk Group Log that it last noted (in P1 mode) while a P2 signal is being decoded.

That makes sense. I'll get that fixed and post a new link. Thank you for testing!

Regarding the encrypted... I need to figure out how to do the RS fec for the encryption information before it will be able to detect encrypted voice frames. I will get that figured out as soon as I can. Once the talk groups for P2 are working (probably next release), you will be able to disable encrypted talk groups that way for now.

 

[Mike_G_D]

Thank you for the continued support and attention!

I have been trying to write up a report of my technical and operational observations but have been busy with work and am dealing with a difficult home situation (while trying to work from home) and haven't been able to finish it yet.

But have tried to spread the word about this device when I can.

For what it's worth - it has essentially become my primary monitoring receiver for the local system I monitor, San Diego County RCS NexGen.

-Mike

 

[btt]

But have tried to spread the word about this device when I can.

For what it's worth - it has essentially become my primary monitoring receiver for the local system I monitor, San Diego County RCS NexGen.

Thank you Mike. I appreciate the support! There is a new version on the web site (version _1016). This may fix the talk group issue with P2. I also recently made changes to voice audio buffering, so let me know if it is better / worse.

[edit]
Just realized version _1016 wasn't going to fix the talk group issue. updating with version _1032

 

[Mike_G_D]

Thank you Mike. I appreciate the support! There is a new version on the web site (version _1016). This may fix the talk group issue with P2. I also recently made changes to voice audio buffering, so let me know if it is better / worse.

[edit]
Just realized version _1016 wasn't going to fix the talk group issue. updating with version _1032

Yeah, been trying 1016 and it seems worse for me - P2 voice is badly broken up compared to the previous version (154) and, as you said, no talk groups displayed still. Will try 1032.

 

[btt]

Yeah, been trying 1016 and it seems worse for me - P2 voice is badly broken up compared to the previous version (154) and, as you said, no talk groups displayed still. Will try 1032.

New (untested) version added _1054. This has the same changes for the talk group issue as _1032, but the audio buffering changes were reverted to be the same as in the earlier version where audio was working for you.

 

[Mike_G_D]

New (untested) version added _1054. This has the same changes for the talk group issue as _1032, but the audio buffering changes were reverted to be the same as in the earlier version where audio was working for you.

Ok, will try that - 1032 was, as one might expect, yielding really poor broken P2 audio like 1016. No worries - I've done my share in development labs in my past life! And you are ONE person - Project Manager/Development Engineer/Engineering Technician/Sales Lead - all in one!

Kinda think some trial and error is somewhat likely...

 

[btt]

Normally, I would not attempt to debug something like this in a forum. In this case, I can't test P2 here, and I think we are getting really close now. I think we might be forgiven if the thread becomes a bit noisy if it means P2 TDMA is working today.

 

[Mike_G_D]

Definite improvement - now get decent P2 audio and can see the talk groups.

Audio leveling seems MUCH better than my only P2 capable scanner, a Whistler 1098. So that alone is a plus.

System is pretty big and complex. I am noticing a lot of talk groups as listed in the RR database as being P1 but I am getting P2 traffic on them; I believe this is because more and more subscribers are getting full P2 capable radio upgrades. One TG in particular I wondered why I hadn't heard anything on it in a while and noticing it was because the traffic is P2!

Need to monitor for awhile. And working.

-Mike

 

[amcferrin90]

There's always the option for a Telegram (ugh) or Discord channel for development testing.

 

[Mike_G_D]

Hmm, now it seems things have gone pretty wonky. I had to disconnect the radio for a while. I shut closed the config software and disconnected the radio.

Later, after reconnecting and restarting the software, same 1054 version, I seem to be getting a mix of some clear and some sounding like encrypted on ALL talkgroups, P1 and P2, including a lot that I know are never encrypted. I can't say whether the audio demodulator is going wonky or if the talk group following is screwed up such that when a message ends on a voice frequency it doesn't mute and lets encrypted audio from a totally different talk group through. It's a real mess now, unfortunately. I've tried disconnecting and reconnecting and restarting the program, etc. Always the same, things might sound ok for a little while and then EVERYBODY sounds like they are going encrypted, and then later back to normal. Maybe some synchronization has "floated off"? Can't seem to get it back to "stable" mode now. Haven't tried a hardware reset of the radio yet.

 

[relicwr]

@Mike_G_D are you using Bluetooth?

 

[Mike_G_D]

Well! I think we're going backwards, at least in my case. I tried downloading the 1218 version for today that I just saw on the website and installed it. Now - no audio at all! No matter what I do. Console looks like everything is working but not getting any audio out of the Line out.

Question - can we revert to older software and firmware (they seem to be linked)? I think, for now, I'd just like to go back to the 8/22/2020 1846 version for normal monitoring until some more bugs are worked out.

Oh well.

-Mike

 

[Mike_G_D]

@Mike_G_D are you using Bluetooth?

No. Bluetooth turned off. Just using line out to an audio mixer. PC audio turned off also but have played with that in the past (but not with the latest version).

 

[relicwr]

There has been degredation with Bluetooth when first paired but it clears up. I haven't had any problems as far as any bad garbling.