Unrecognized TSBK Opcode Errors

[Brian Hall]

Hello,

I'm monitoring a new statewide P25 Phase 2 system in SDRTrunk that is coming online here in Utah (https://www.radioreference.com/db/sid/12042), and I'm seeing some interesting errors in the log:

0240611 162111.344 [sdrtrunk channel [1/P25-1] MULTI FREQ thread 1] INFO  i.g.d.m.d.p.p.P25P1DecoderState - Unrecognized TSBK Opcode: HARRIS_OSP_UNKNOWN VENDOR:HARRIS OPCODE:1 MSG:81A4110DFFFFFFFFFFFFF79D [Log Suppress 1/1]  [108MB/366MB 29%]
20240611 162111.389 [sdrtrunk channel [1/P25-1] MULTI FREQ thread 1] INFO  i.g.d.m.d.p.p.P25P1DecoderState - Unrecognized TSBK Opcode: HARRIS_OSP_UNKNOWN VENDOR:HARRIS OPCODE:15 MSG:8FA40A82000A00000000D513 [Log Suppress 1/1]  [133MB/366MB 36%]
2024

0611 163052.140 [sdrtrunk channel [1/P25-1] MULTI FREQ thread 1] INFO  i.g.d.m.d.p.p.P25P1DecoderState - Unrecognized TSBK Opcode: UNKNOWN_VENDOR_OSP VENDOR:V166 OPCODE:36 MSG:A4A6B80BB840AAE3EF1EB32B [Log Suppress 1/1]  [281MB/366MB 76%]
20240611 163122.840 [sdrtrunk channel [1/P25-1] MULTI FREQ thread 1] INFO  i.g.d.m.d.p.p.P25P1DecoderState - Unrecognized TSBK Opcode: UNKNOWN_VENDOR_OSP VENDOR:V173 OPCODE:52 MSG:B4ADB5F141008082373124C0 [Log Suppress 1/1]  [243MB/366MB 66%]
20240611 163613.689 [sdrtrunk channel [1/P25-1] MULTI FREQ thread 1] INFO  i.g.d.m.d.p.p.P25P1DecoderState - Unrecognized TSBK Opcode: UNKNOWN_VENDOR_OSP VENDOR:SEA OPCODE:18 MSG:92C03565654D6091701AB493 [Log Suppress 1/1]  [139MB/366MB 38%]
2024

I continue to get errors like these continuously. I'm not sure if it's just because it's a new system that is still in the deployment phase, or something else. I'm attaching the full log to this message in the hopes that it is helpful.

Let me know if I can provide any other data that might be useful.

[Brian Hall]

Signal strength seems to be pretty good:

[Adam L]

I have been having odd statements like these in the DOS prompt launch window. I have the "keep alive" function running and once in a while I'll see errors like this mentioning unrecognized things in P25 phase 1 and phase 2. I wonder if there is a lookup?

[dave38...@gmail.com]

"Let me know if I can provide any other data that might be useful.

Signal strength seems to be pretty good:"

Can you post some screenshots of the spectrum? 

[Brian Hall]

Sure thing!

Here's a snapshot of the spectrum:

Brian

--
You received this message because you are subscribed to the Google Groups "sdrtrunk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sdrtrunk+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sdrtrunk/c7f337a2-6276-4cb5-bfa6-7d8b2eb35632n%40googlegroups.com.

[dave38...@gmail.com]

A larger image would be nice but what is your gain set at? To me, the noise floor looks a little high.

Not perfectly scaled, but mine is on the left and yours is on the right.

[Brian Hall]

Gain was set to 20, but I lowered it to 18. Here's another screen capture that is hopefully helpful:

[charley....@gmail.com]

I'd go even lower with the gain.  The goal would be to find the lowest usable gain for the target system.  The yellow dots in the blue spectrum field indicate noise; try to lower gain to eliminate them.

[Brian Hall]

Previous gain settings were for my Airspy R2. The gain settings for the RTL-SDR running on the same system is set to 327. I'm getting the "Unrecognized TSBK Opcode" errors on both my R2 and RTL-SDR.

[Brian Hall]

Thanks for the suggestions on adjusting gain. I settled on a gain setting of 296 on the RTL-SDR, which seemed to give me a good ratio of signal/noise. I'll keep watching it to see if the "Unrecognized TSBK Opcode" errors go down.

[Zach Rutledge]

Just popping in to note that I'm also seeing these in the DOS box as well now, on a different system (AIRS in Alabama, a P25 system).  I'm using the latest nightly build now since it's the only way I can get the app to work with my new radio, an SDRPlay RSPdxR2 model.  

On the 0.6.1 beta build I would see these once in a blue moon in the logs but only here and there.  This seems to be a lot more common in the nightly build.

Unrecognized TSBK Opcode: UNKNOWN_VENDOR_OSP VENDOR:CYCOMM OPCODE:43 MSG:EB203FBF3FE808055A15F55A [Log Suppress 1/1]  [345MB/650MB 53%]
Unrecognized TSBK Opcode: UNKNOWN_VENDOR_OSP VENDOR:V254 OPCODE:35 MSG:23FEBFDD12E2FC3EB5E315FD [Log Suppress 1/1]  [339MB/650MB 52%]
Unrecognized TSBK Opcode: UNKNOWN_VENDOR_OSP VENDOR:SEA OPCODE:31 MSG:5FC00D1FC0040003FF42BEBF [Log Suppress 1/1]  [578MB/650MB 88%]
Unrecognized TSBK Opcode: OSP_RESERVED_07 VENDOR:STANDARD OPCODE:7 MSG:C7000552E1DD024500711A62 [Log Suppress 1/1]  [250MB/650MB 38%]
Unrecognized TSBK Opcode: UNKNOWN_VENDOR_OSP VENDOR:SEA OPCODE:52 MSG:74C0DA6B0AAFF7741016BFC0 [Log Suppress 1/1]  [336MB/650MB 51%]
Unrecognized TSBK Opcode: UNKNOWN_VENDOR_OSP VENDOR:V252 OPCODE:27 MSG:1BFC37224C0DD1A75489DAAD [Log Suppress 1/1]  [549MB/650MB 84%]
Unrecognized TSBK Opcode: UNKNOWN_VENDOR_OSP VENDOR:V6 OPCODE:43 MSG:2B0654441EF100D002A1E93F [Log Suppress 1/1]  [551MB/650MB 84%]
Unrecognized TSBK Opcode: UNKNOWN_VENDOR_OSP VENDOR:V143 OPCODE:18 MSG:528FB4A2FFFFFFFFDFFF60FA [Log Suppress 1/1]  [321MB/650MB 49%]
Unrecognized TSBK Opcode: UNKNOWN_VENDOR_OSP VENDOR:V35 OPCODE:19 MSG:93239183430580D0F6590D07 [Log Suppress 1/1]  [498MB/650MB 76%]
Unrecognized LCW Opcode: RESERVED_36 VENDOR:STANDARD OPCODE:54 MSG:F631B054C2A92999B0 CHAN:null FREQ:770118750 [Log Suppress 1/1]  [490MB/650MB 75%]
Unrecognized LCW Opcode: MOTOROLA_UNKNOWN VENDOR:MOTOROLA OPCODE:34 MSG:22909C4B93C9C4A834 CHAN:null FREQ:769343750 [Log Suppress 1/1]  [373MB/650MB 57%]
Unrecognized TSBK Opcode: UNKNOWN_VENDOR_OSP VENDOR:V107 OPCODE:28 MSG:1C6B6FA0BEBFFEFE8057DA05 [Log Suppress 1/1]  [317MB/650MB 48%]
Unrecognized TSBK Opcode: UNKNOWN_VENDOR_OSP VENDOR:V149 OPCODE:24 MSG:1895E00000000400003E2808 [Log Suppress 1/1]  [506MB/664MB 76%]
Unrecognized TSBK Opcode: UNKNOWN_VENDOR_OSP VENDOR:V143 OPCODE:16 MSG:508F2E80EBDBBF881500A8D0 [Log Suppress 1/1]  [433MB/664MB 65%]

[Brian Hall]

Yep, gain settings didn't do anything to address the "Unrecognized TSBK Opcode" errors:

[charley....@gmail.com]

The idea was to rule out bad decodes caused by unnecessarily large gain values.  Still best practice is to limit gain to what is actually needed to decode the traffic.  Seems like Harris has some vendor specific op codes not recognized by SDRT.

[tv...@tvsjr.com]

Because he sent you down a pointless path. If it was an RSSI/BER issue you'd be seeing sync fails/CRC errors, which you aren't. You're seeing legit data that SDRTrunk doesn't know what to do with.

The right answer would be to open an issue on GitHub and attach all the data you've collected. That way the issue can be tracked. 

---

From: Brian Hall <bhal...@gmail.com>
Sent: Friday, June 21, 2024 10:28
To: sdrtrunk
Subject: Re: Unrecognized TSBK Opcode Errors

To view this discussion on the web visit https://groups.google.com/d/msgid/sdrtrunk/c9c5e2bb-e62f-4a5a-a70e-f3e142237521n%40googlegroups.com.

[Brian Hall]

Thanks, TVSJR,

I added my comments to an already-open issue on GitHub: https://github.com/DSheirer/sdrtrunk/issues/1902

Thanks all!

[tv...@tvsjr.com]

Are you otherwise getting decode like you would expect? While I'm sure Denny would like to handle all the opcodes, it could be something related to OTAP/OTAR, Beon, or a host of other things that really don't mean a ton. 

---

From: Brian Hall <bhal...@gmail.com>
Sent: Friday, June 21, 2024 12:50

To view this discussion on the web visit https://groups.google.com/d/msgid/sdrtrunk/fc3b1028-5cf9-4cb6-b525-9a4298fd4068n%40googlegroups.com.

[tv...@tvsjr.com]

If you get them at random and with widely varied opcodes, it could be poor signal/high BER. But if you're getting the same ones over and over again, it's legit data. 

---

From: Bob Burkett <r.l.b...@gmail.com>
Sent: Friday, June 21, 2024 14:57
To: tv...@tvsjr.com
Cc: Brian Hall; sdrtrunk

Subject: Re: Unrecognized TSBK Opcode Errors

I likewise have been getting these errors and was advised it was a signal reception problem.  Through much tuning I still continue to get these errors. I do not recall seeing these on earlier versions.  As I am experimenting, I alway use the newest versions out. 

~Bob 

To view this discussion on the web visit https://groups.google.com/d/msgid/sdrtrunk/cbd66d5b-5940-4888-8c83-724b4407e5c8%40tvsjr.com.