Deciphering TSDU Data Packets

[adamfancher]

So this has already been asked (but never answered) in a much broader thread about one of last year's releases of DSD+ (New DSD+ 2.464) so just wanted to start a specific conversation about the topic of TSDU packets.

Like several people had mentioned, I am seeing the unhandled parm request followed by a packet of data.

Is there any rhyme or reason to what values these individual bytes represent across the board, or does every agency have a different format?

TIA

 

[boatbod]

So this has already been asked (but never answered) in a much broader thread about one of last year's releases of DSD+ (New DSD+ 2.464) so just wanted to start a specific conversation about the topic of TSDU packets.

Like several people had mentioned, I am seeing the unhandled parm request followed by a packet of data.

Is there any rhyme or reason to what values these individual bytes represent across the board, or does every agency have a different format?

TIA

Generally 'unhandled means the app either received a message with a manufacturer-specific flag and an unknown opcode, or a generic message of a type that the app doesn't care about. For example, op25 doesn't process user-to-user calls or associated messaging, so any opcodes concerning that activity will appear in the log as unhandled.