P25 TDMA Control Channel decoding -- requesting help from experts

[mtindor]

Any verdict yet? So is this taking a P25 signal and then doing a DMR-type slice on top of that where you cut that into two 'channels' of data? How much more overly complex and 'digital sounding' can one make it?
I'm almost ready to give-up the hobby now as my ears barely work okay on analog audio signals, but my hearing is compromised on P25 simulcast audio to where scanning isn't any fun anymore if you have to "squint" to hear what is being said.

There isn't going to be any difference in the voiced audio compared to any other Phase II voice. All this is doing is switching out the typical P25 single-timeslot control channel with a dual-timeslot control channel that will allow an additional voice talkpath. Relax.

Mike

 

[KA1RBI]

still checking a few things, so this data is very preliminary with the usual caveats. My hacked OP25 is not currently grokking the "Alice" site, so I'll hopefully have more to report on that soon...

Freer:

====== NAC 0x34 ====== TDMA ======
rf: syid 1f8 rfid 52 stid 52 frequency 854.087500 uplink 809.087500
net: syid 1f8 wacn 92715 frequency 854.087500
secondary control channel(s): 854.612500,855.137500,855.787500
stats: tsbks 0 crc 0

tbl-id: 8 frequency: 851.000000 step 0.012500 offset -45.000000
adjacent 857.412500: rfid: 51 stid:51 uplink:812.412500 tbl:8 sysid:0x1f8
adjacent 854.212500: rfid: 53 stid:53 uplink:809.212500 tbl:8 sysid:0x1f8
adjacent 854.437500: rfid: 58 stid:58 uplink:809.437500 tbl:8 sysid:0x1f8
adjacent 856.137500: rfid: 59 stid:59 uplink:811.137500 tbl:8 sysid:0x1f8
adjacent 854.912500: rfid: 41 stid:41 uplink:809.912500 tbl:8 sysid:0x1f8
adjacent 854.812500: rfid: 42 stid:42 uplink:809.812500 tbl:8 sysid:0x1f8

Corpus

====== NAC 0xe ====== TDMA ======
rf: syid 1f8 rfid 14 stid 14 frequency 855.312500 uplink 810.312500
net: syid 1f8 wacn 92715 frequency 855.312500
secondary control channel(s): 856.787500,857.787500,859.387500
stats: tsbks 0 crc 0

tbl-id: 8 frequency: 851.000000 step 0.012500 offset -45.000000
adjacent 854.812500: rfid: 42 stid:42 uplink:809.812500 tbl:8 sysid:0x1f8
adjacent 854.937500: rfid: 43 stid:43 uplink:809.937500 tbl:8 sysid:0x1f8
adjacent 854.762500: rfid: 44 stid:44 uplink:809.762500 tbl:8 sysid:0x1f8
adjacent 855.262500: rfid: 114 stid:114 uplink:810.262500 tbl:8 sysid:0x1f8
adjacent 857.312500: rfid: 8 stid:8 uplink:812.312500 tbl:8 sysid:0x1f8

Beeville

====== NAC 0x2a ====== TDMA ======
rf: syid 1f8 rfid 42 stid 42 frequency 854.812500 uplink 809.812500
net: syid 1f8 wacn 92715 frequency 854.812500
secondary control channel(s): 855.387500,855.937500,856.912500
stats: tsbks 0 crc 0

tbl-id: 8 frequency: 851.000000 step 0.012500 offset -45.000000
adjacent 854.087500: rfid: 52 stid:52 uplink:809.087500 tbl:8 sysid:0x1f8
adjacent 855.062500: rfid: 57 stid:57 uplink:810.062500 tbl:8 sysid:0x1f8
adjacent 855.262500: rfid: 114 stid:114 uplink:810.262500 tbl:8 sysid:0x1f8
adjacent 857.312500: rfid: 8 stid:8 uplink:812.312500 tbl:8 sysid:0x1f8
adjacent 854.787500: rfid: 13 stid:13 uplink:809.787500 tbl:8 sysid:0x1f8

 

[mtindor]

still checking a few things, so this data is very preliminary with the usual caveats. My hacked OP25 is not currently grokking the "Alice" site, so I'll hopefully have more to report on that soon...

Freer:

====== NAC 0x34 ====== TDMA ======
rf: syid 1f8 rfid 52 stid 52 frequency 854.087500 uplink 809.087500
net: syid 1f8 wacn 92715 frequency 854.087500
secondary control channel(s): 854.612500,855.137500,855.787500
stats: tsbks 0 crc 0

tbl-id: 8 frequency: 851.000000 step 0.012500 offset -45.000000
adjacent 857.412500: rfid: 51 stid:51 uplink:812.412500 tbl:8 sysid:0x1f8
adjacent 854.212500: rfid: 53 stid:53 uplink:809.212500 tbl:8 sysid:0x1f8
adjacent 854.437500: rfid: 58 stid:58 uplink:809.437500 tbl:8 sysid:0x1f8
adjacent 856.137500: rfid: 59 stid:59 uplink:811.137500 tbl:8 sysid:0x1f8
adjacent 854.912500: rfid: 41 stid:41 uplink:809.912500 tbl:8 sysid:0x1f8
adjacent 854.812500: rfid: 42 stid:42 uplink:809.812500 tbl:8 sysid:0x1f8

Corpus

====== NAC 0xe ====== TDMA ======
rf: syid 1f8 rfid 14 stid 14 frequency 855.312500 uplink 810.312500
net: syid 1f8 wacn 92715 frequency 855.312500
secondary control channel(s): 856.787500,857.787500,859.387500
stats: tsbks 0 crc 0

tbl-id: 8 frequency: 851.000000 step 0.012500 offset -45.000000
adjacent 854.812500: rfid: 42 stid:42 uplink:809.812500 tbl:8 sysid:0x1f8
adjacent 854.937500: rfid: 43 stid:43 uplink:809.937500 tbl:8 sysid:0x1f8
adjacent 854.762500: rfid: 44 stid:44 uplink:809.762500 tbl:8 sysid:0x1f8
adjacent 855.262500: rfid: 114 stid:114 uplink:810.262500 tbl:8 sysid:0x1f8
adjacent 857.312500: rfid: 8 stid:8 uplink:812.312500 tbl:8 sysid:0x1f8

Beeville

====== NAC 0x2a ====== TDMA ======
rf: syid 1f8 rfid 42 stid 42 frequency 854.812500 uplink 809.812500
net: syid 1f8 wacn 92715 frequency 854.812500
secondary control channel(s): 855.387500,855.937500,856.912500
stats: tsbks 0 crc 0

tbl-id: 8 frequency: 851.000000 step 0.012500 offset -45.000000
adjacent 854.087500: rfid: 52 stid:52 uplink:809.087500 tbl:8 sysid:0x1f8
adjacent 855.062500: rfid: 57 stid:57 uplink:810.062500 tbl:8 sysid:0x1f8
adjacent 855.262500: rfid: 114 stid:114 uplink:810.262500 tbl:8 sysid:0x1f8
adjacent 857.312500: rfid: 8 stid:8 uplink:812.312500 tbl:8 sysid:0x1f8
adjacent 854.787500: rfid: 13 stid:13 uplink:809.787500 tbl:8 sysid:0x1f8

Thanks, Max!

Mike

 

[boatbod]

You'll have to compile a special version, and then run it. And the details for doing that should probably occur in another thread. ( @boatbod -- if you are going to entertain helping people to get set up for OP25 and to compile your version, please consider opening another thread for that). I can't stop you from doing it here, but it sure could turn into a cluttered mess if there are a lot of OP25-compile-n-run posts inside this thread.

If anyone needs info on how to build op25 I'm happy to explain via PM. No need to dilute this thread. With that in mind though, there are already a bunch of people running the boatbod fork already so getting the latest changes isn't too troublesome.

 

[btt]

If anyone needs info on how to build op25 I'm happy to explain via PM. No need to dilute this thread. With that in mind though, there are already a bunch of people running the boatbod fork already so getting the latest changes isn't too troublesome.

Ahh.. burst_type==0x0d. Those bursts don't pass the crc12 check as-is, but it does deliver the Network Adjacent Broadcast info! Thanks!

Sample output from the 0x2c site
P25_PII: Network Status Broadcast Abbreviated, lra=0x04, wacn_id=0x92715, sys_id=0x1f8, ch=33370, ssc=0x70, colorcd=02c

 

[btt]

Adjacent info for the Alice site
$P25_PII, Adjacent Status Broadcast Abbreviated, lra=0x04, cfva=0x3, sys_id=0x1f8, rfss=42, site=42, ch=33378, ssc=0x70
$P25_PII, Adjacent Status Broadcast Abbreviated, lra=0x04, cfva=0x3, sys_id=0x1f8, rfss=43, site=43, ch=33398, ssc=0x70
$P25_PII, Adjacent Status Broadcast Abbreviated, lra=0x04, cfva=0x3, sys_id=0x1f8, rfss=44, site=44, ch=33370, ssc=0x70
$P25_PII, Adjacent Status Broadcast Abbreviated, lra=0x04, cfva=0x3, sys_id=0x1f8, rfss=49, site=49, ch=33454, ssc=0x70
$P25_PII, Adjacent Status Broadcast Abbreviated, lra=0x04, cfva=0x3, sys_id=0x1f8, rfss=51, site=51, ch=33794, ssc=0x70
$P25_PII, Adjacent Status Broadcast Abbreviated, lra=0x04, cfva=0x3, sys_id=0x1f8, rfss=52, site=52, ch=33262, ssc=0x70
$P25_PII, Adjacent Status Broadcast Abbreviated, lra=0x04, cfva=0x3, sys_id=0x1f8, rfss=57, site=57, ch=33418, ssc=0x70
$P25_PII, Adjacent Status Broadcast Abbreviated, lra=0x04, cfva=0x3, sys_id=0x1f8, rfss=59, site=59, ch=33590, ssc=0x70

 

[mtindor]

Adjacent info for the Alice site
$P25_PII, Adjacent Status Broadcast Abbreviated, lra=0x04, cfva=0x3, sys_id=0x1f8, rfss=42, site=42, ch=33378, ssc=0x70
$P25_PII, Adjacent Status Broadcast Abbreviated, lra=0x04, cfva=0x3, sys_id=0x1f8, rfss=43, site=43, ch=33398, ssc=0x70
$P25_PII, Adjacent Status Broadcast Abbreviated, lra=0x04, cfva=0x3, sys_id=0x1f8, rfss=44, site=44, ch=33370, ssc=0x70
$P25_PII, Adjacent Status Broadcast Abbreviated, lra=0x04, cfva=0x3, sys_id=0x1f8, rfss=49, site=49, ch=33454, ssc=0x70
$P25_PII, Adjacent Status Broadcast Abbreviated, lra=0x04, cfva=0x3, sys_id=0x1f8, rfss=51, site=51, ch=33794, ssc=0x70
$P25_PII, Adjacent Status Broadcast Abbreviated, lra=0x04, cfva=0x3, sys_id=0x1f8, rfss=52, site=52, ch=33262, ssc=0x70
$P25_PII, Adjacent Status Broadcast Abbreviated, lra=0x04, cfva=0x3, sys_id=0x1f8, rfss=57, site=57, ch=33418, ssc=0x70
$P25_PII, Adjacent Status Broadcast Abbreviated, lra=0x04, cfva=0x3, sys_id=0x1f8, rfss=59, site=59, ch=33590, ssc=0x70

Do you have the ability [yet] to process the Alice audio to get Site ID / NAC / CC / VCs ? I know Max reported above that he had difficulty with Alice.

 

[btt]

Do you have the ability [yet] to process the Alice audio to get Site ID / NAC / CC / VCs ? I know Max reported above that he had difficulty with Alice.

The Site ID column is there (42, 43, 44, 49, 51, 52, 57, 59). I still need to work on creating the base table frequencies in order to convert the channel numbers into absolute frequencies like Max has already done. I will definitely be working on that this evening. I just needed the hint about the new burst type. Right now I have to get some hardware ready to ship this afternoon before USPS closes.

 

[mtindor]

The Site ID column is there (42, 43, 44, 49, 51, 52, 57, 59). I still need to work on creating the base table frequencies in order to convert the channel numbers into absolute frequencies like Max has already done. I will definitely be working on that this evening. I just needed the hint about the new burst type. Right now I have to get some hardware ready to ship this afternoon before USPS closes.

Cool. Looking good so far.

Mike

 

[mtindor]

Ahh.. burst_type==0x0d. Those bursts don't pass the crc12 check as-is, but it does deliver the Network Adjacent Broadcast info! Thanks!

Some sample output from the 0x2c site
$P25_PII, lra=0x04, cfva=0x3, sys_id=0x1f8, rfss=52, site=52, ch=33262, ssc=0x70
P25_PII: Network Status Broadcast Abbreviated, lra=0x04, wacn_id=0x92715, sys_id=0x1f8, ch=33370, ssc=0x70, colorcd=02c
P25_PII: Network Status Broadcast Abbreviated, lra=0x04, wacn_id=0x92715, sys_id=0x1f8, ch=33370, ssc=0x70, colorcd=02c
$P25_PII, lra=0x04, cfva=0x3, sys_id=0x1f8, rfss=53, site=53, ch=33282, ssc=0x70
P25_PII: Network Status Broadcast Abbreviated, lra=0x04, wacn_id=0x92715, sys_id=0x1f8, ch=33370, ssc=0x70, colorcd=02c
P25_PII: Network Status Broadcast Abbreviated, lra=0x04, wacn_id=0x92715, sys_id=0x1f8, ch=33370, ssc=0x70, colorcd=02c

Are you sure this was the 0x2c site (George West)?

In Max's decode it showed the following peers:
adjacent 859.787500: rfid: 8 stid:8 uplink:814.787500 tbl:8
adjacent 855.312500: rfid: 14 stid:14 uplink:810.312500 tbl:8
adjacent 854.912500: rfid: 41 stid:41 uplink:809.912500 tbl:8
adjacent 854.812500: rfid: 42 stid:42 uplink:809.812500 tbl:8
adjacent 854.937500: rfid: 43 stid:43 uplink:809.937500 tbl:8
adjacent 854.087500: rfid: 52 stid:52 uplink:809.087500 tbl:8


No mention of 53 as a peer. But the snippet you provided for "2c" references a site 53 as well. I guess it could be that Max may have decoded from the original (small) file for the 0x2c site and you may have been decoding from the larger file, and the smaller file may not have had enough time in it to enumerate all of the peers -- or a new peer had come online within that 24 hour timeframe.

I'm making DB updates based this information, and that's why I just want to make sure you were copying 0x2c when you posted that.

Anyway, by all means go take care of your business. My question is in no way urgent. in fact, I'm stepping away for few hours.

mike

 

[btt]

That was for the 2nd larger file. The first file does not contain the 53 site. Here are all of them for the larger 0x2c file: (8,14,41,42,43,52,53,57)
$P25_PII, Adjacent Status Broadcast Abbreviated, lra=0x04, cfva=0x3, sys_id=0x1f8, rfss=8, site=8, ch=34174, ssc=0x70
$P25_PII, Adjacent Status Broadcast Abbreviated, lra=0x04, cfva=0x3, sys_id=0x1f8, rfss=14, site=14, ch=33458, ssc=0x70
$P25_PII, Adjacent Status Broadcast Abbreviated, lra=0x04, cfva=0x3, sys_id=0x1f8, rfss=41, site=41, ch=33394, ssc=0x70
$P25_PII, Adjacent Status Broadcast Abbreviated, lra=0x04, cfva=0x3, sys_id=0x1f8, rfss=42, site=42, ch=33378, ssc=0x70
$P25_PII, Adjacent Status Broadcast Abbreviated, lra=0x04, cfva=0x3, sys_id=0x1f8, rfss=43, site=43, ch=33398, ssc=0x70
$P25_PII, Adjacent Status Broadcast Abbreviated, lra=0x04, cfva=0x3, sys_id=0x1f8, rfss=52, site=52, ch=33262, ssc=0x70
$P25_PII, Adjacent Status Broadcast Abbreviated, lra=0x04, cfva=0x3, sys_id=0x1f8, rfss=53, site=53, ch=33282, ssc=0x70
$P25_PII, Adjacent Status Broadcast Abbreviated, lra=0x04, cfva=0x3, sys_id=0x1f8, rfss=57, site=57, ch=33418, ssc=0x70

 

[mtindor]

That was for the 2nd larger file. The first file does not contain the 53 site. Here are all of them for the larger 0x2c file: (8,14,41,42,43,52,53,57)
$P25_PII, Adjacent Status Broadcast Abbreviated, lra=0x04, cfva=0x3, sys_id=0x1f8, rfss=8, site=8, ch=34174, ssc=0x70
$P25_PII, Adjacent Status Broadcast Abbreviated, lra=0x04, cfva=0x3, sys_id=0x1f8, rfss=14, site=14, ch=33458, ssc=0x70
$P25_PII, Adjacent Status Broadcast Abbreviated, lra=0x04, cfva=0x3, sys_id=0x1f8, rfss=41, site=41, ch=33394, ssc=0x70
$P25_PII, Adjacent Status Broadcast Abbreviated, lra=0x04, cfva=0x3, sys_id=0x1f8, rfss=42, site=42, ch=33378, ssc=0x70
$P25_PII, Adjacent Status Broadcast Abbreviated, lra=0x04, cfva=0x3, sys_id=0x1f8, rfss=43, site=43, ch=33398, ssc=0x70
$P25_PII, Adjacent Status Broadcast Abbreviated, lra=0x04, cfva=0x3, sys_id=0x1f8, rfss=52, site=52, ch=33262, ssc=0x70
$P25_PII, Adjacent Status Broadcast Abbreviated, lra=0x04, cfva=0x3, sys_id=0x1f8, rfss=53, site=53, ch=33282, ssc=0x70
$P25_PII, Adjacent Status Broadcast Abbreviated, lra=0x04, cfva=0x3, sys_id=0x1f8, rfss=57, site=57, ch=33418, ssc=0x70

thank you!

 

[KA1RBI]

results for Alice (with the usual disclaimers)

====== NAC 0x29 ====== TDMA ======
rf: syid 1f8 rfid 41 stid 41 frequency 854.912500 uplink 809.912500
net: syid 1f8 wacn 92715 frequency 854.912500
secondary control channel(s): 855.912500,858.362500,859.362500
stats: tsbks 0 crc 0

tbl-id: 8 frequency: 851.000000 step 0.012500 offset -45.000000
adjacent 854.812500: rfid: 42 stid:42 uplink:809.812500 tbl:8 sysid:0x1f8
adjacent 854.937500: rfid: 43 stid:43 uplink:809.937500 tbl:8 sysid:0x1f8
adjacent 854.762500: rfid: 44 stid:44 uplink:809.762500 tbl:8 sysid:0x1f8
adjacent 855.287500: rfid: 49 stid:49 uplink:810.287500 tbl:8 sysid:0x1f8
adjacent 857.412500: rfid: 51 stid:51 uplink:812.412500 tbl:8 sysid:0x1f8

 

[mtindor]

results for Alice (with the usual disclaimers)

====== NAC 0x29 ====== TDMA ======
rf: syid 1f8 rfid 41 stid 41 frequency 854.912500 uplink 809.912500
net: syid 1f8 wacn 92715 frequency 854.912500
secondary control channel(s): 855.912500,858.362500,859.362500
stats: tsbks 0 crc 0

tbl-id: 8 frequency: 851.000000 step 0.012500 offset -45.000000
adjacent 854.812500: rfid: 42 stid:42 uplink:809.812500 tbl:8 sysid:0x1f8
adjacent 854.937500: rfid: 43 stid:43 uplink:809.937500 tbl:8 sysid:0x1f8
adjacent 854.762500: rfid: 44 stid:44 uplink:809.762500 tbl:8 sysid:0x1f8
adjacent 855.287500: rfid: 49 stid:49 uplink:810.287500 tbl:8 sysid:0x1f8
adjacent 857.412500: rfid: 51 stid:51 uplink:812.412500 tbl:8 sysid:0x1f8

Thank you!

 

[mtindor]

results for Alice (with the usual disclaimers)

====== NAC 0x29 ====== TDMA ======
rf: syid 1f8 rfid 41 stid 41 frequency 854.912500 uplink 809.912500
net: syid 1f8 wacn 92715 frequency 854.912500
secondary control channel(s): 855.912500,858.362500,859.362500
stats: tsbks 0 crc 0

tbl-id: 8 frequency: 851.000000 step 0.012500 offset -45.000000
adjacent 854.812500: rfid: 42 stid:42 uplink:809.812500 tbl:8 sysid:0x1f8
adjacent 854.937500: rfid: 43 stid:43 uplink:809.937500 tbl:8 sysid:0x1f8
adjacent 854.762500: rfid: 44 stid:44 uplink:809.762500 tbl:8 sysid:0x1f8
adjacent 855.287500: rfid: 49 stid:49 uplink:810.287500 tbl:8 sysid:0x1f8
adjacent 857.412500: rfid: 51 stid:51 uplink:812.412500 tbl:8 sysid:0x1f8

Max,

Is there any chance that the OP25 code isn't displaying all actual peers for this site?

BTT's post suggests 8 peers (42, 43, 44, 49, 51, 52, 57, 59).

Unless 52, 57, 59 are "offline / failed / not connected" and OP25 only reflects those peers with active connections?

Mike

 

[KA1RBI]

Max,

Is there any chance that the OP25 code isn't displaying all actual peers for this site?

Mike

Yes, this is likely, in fact.

There is a monster new version of OP25 (Osmocom) that is imminent - we've just cut a Release Candidate 2 (rc2). OP25 contributor "Triptolemus" has done a blockbuster job this time. That is happening at the same time as the TDMA control channel work (going on in this thread) and at this stage the state of the TDMA-CC code is pre-alpha-test quality pending more work. It's possible that we're missing up to say, 50% of available TDMA-CC data due to known syncing issues, and the ad-hoc code that I wrote to demodulate the .wav files is highly iffy.

If anyone reading this is interested in alpha-testing the new OP25 release candidate (you should have prior experience with OP25) please send me a PM. The experimental TDMA-CC mods are included, the remainder of the changes are outlined below...

1. With thanks to OP25 user Triptolemus, the web client is enhanced to
   include comprehensive logs of recent control channel signalling and
   call activity.  Many other features are also added: 
    * unit ID (subscriber ID) tagging - similar to the existing TGID
      tags setup.
    * tag color coding (for both TGID and SUID tags).
    * tag ranges and wildcarding - for both the TGID and SUID tag maps,
      a single definition line may be used to create tags for a range of
      IDs.
    * real time system frequency status table
    * smart colors
    * user settings (colors, preferences) may be edited and saved via a
      convenient set of web forms and applications

2. The multi_rx app adds extensions to include trunked P25 call following 
   concurrent with full-time tracking of one or more P25 control channels.
   If necessary, additional SDR devices may be configured to allow full
   coverage of all control channels without loss of CC data even during voice
   call reception.  Several new command line options to multi_rx have been
   added - -T (trunking TSV file) -l (terminal type) as well as -X and -U,
   all having the same meaning as in rx.py.

3. Control channel logging to SQL database is added.  For details see the
   section on the Flask Datatables App, below.

 

[mtindor]

Yes, this is likely, in fact.

There is a monster new version of OP25 (Osmocom) that is imminent - we've just cut a Release Candidate 2 (rc2). OP25 contributor "Triptolemus" has done a blockbuster job this time. That is happening at the same time as the TDMA control channel work (going on in this thread) and at this stage the state of the TDMA-CC code is pre-alpha-test quality pending more work. It's possible that we're missing up to say, 50% of available TDMA-CC data due to known syncing issues, and the ad-hoc code that I wrote to demodulate the .wav files is highly iffy.

If anyone reading this is interested in alpha-testing the new OP25 release candidate (you should have prior experience with OP25) please send me a PM. The experimental TDMA-CC mods are included, the remainder of the changes are outlined below...

1. With thanks to OP25 user Triptolemus, the web client is enhanced to
   include comprehensive logs of recent control channel signalling and
   call activity.  Many other features are also added:
    * unit ID (subscriber ID) tagging - similar to the existing TGID
      tags setup.
    * tag color coding (for both TGID and SUID tags).
    * tag ranges and wildcarding - for both the TGID and SUID tag maps,
      a single definition line may be used to create tags for a range of
      IDs.
    * real time system frequency status table
    * smart colors
    * user settings (colors, preferences) may be edited and saved via a
      convenient set of web forms and applications

2. The multi_rx app adds extensions to include trunked P25 call following
   concurrent with full-time tracking of one or more P25 control channels.
   If necessary, additional SDR devices may be configured to allow full
   coverage of all control channels without loss of CC data even during voice
   call reception.  Several new command line options to multi_rx have been
   added - -T (trunking TSV file) -l (terminal type) as well as -X and -U,
   all having the same meaning as in rx.py.

3. Control channel logging to SQL database is added.  For details see the
   section on the Flask Datatables App, below.

That's awesome man. Lots of nice new features. I'm going to have to pull my pi4 out of storage. Can't test TDMA CC, but I can certainly play around with the rest. Very nice. And thanks for the clarification regarding potential missing peers.

Mike

 

[Outerdog]

That's awesome man. Lots of nice new features. I'm going to have to pull my pi4 out of storage. Can't test TDMA CC, but I can certainly play around with the rest. Very nice.

New OP25 Osmocom Web UI:

 

[mtindor]

New OP25 Osmocom Web UI:

View attachment 106923

Wow, I'd say that looks different! Really nice

 

[btt]

I was thinking there might be some watching this thread that would like to help figure this out, but don't have a way to demodulate, etc. Here is a text file containing a dump of the new burst type (dec 13, 0x0d) in the first file released. I've added some notes to show partial decode info for a couple of them (sys_id, rfss, site_id, base frequency). Note that there could be some bit errors in there due to the CRC not being figured out yet (not by me anyway). If this is useful to anyone, and you want similar output for any of the other files, let me know.