SDR# TETRA Demodulator Trunk Tracking Demonstration

[iw2dtt]

sds

hello, it works very well, in the SDS decoding message appears with some information, but then the message appears as a text ..... @ '3 ££££ "" "" "===
question, but SDS decoding is possible today
thank you

 

[thewraith2008]

hello, it works very well, in the SDS decoding message appears with some information, but then the message appears as a text ..... @ '3 ££££ "" "" "===
question, but SDS decoding is possible today
thank you

I would need to see whole SDS line as returned in "TETRA_sds_data.log"

I think some SDS text messages are not always plain text. Maybe converted by MS.

I rarely see SDS messages with content, I only see "MessageType:SDS-Report" so it is not easy to test code I have in place.

 

[iw2dtt]

sds

SYSINFO - Main_carrier:2518 Offset:0 Frequency_Band:4
SSI:1180867 D_SDS_Data Party_SSI:1---------- Type:UDT-4 Length:96 Protocol:Simple_location_system DATA:'000000110000000000100100010100000101001101000011010011110100001101001101001011000011001000110000' LocationSystemCodingScheme:0
SYSINFO - Main_carrier:2518 Offset:0 Frequency_Band:4
SSI:1180867 D_SDS_Data Party_SSI:11------ Type:UDT-4 Length:96 Protocol:Simple_location_system DATA:'000000110000000000100100010100000101001101000011010011110100001101001101001011000011001000110000' LocationSystemCodingScheme:0
SYSINFO - Main_carrier:2518 Offset:0 Frequency_Band:4
SSI:1188155 D_SDS_Data Party_SSI:1---------- Type:UDT-4 Length:32 Protocol:Text_Messaging MessageType:SDS-Report Delivery_status:SDS_receipt_acknowledged_by_destination_Destination_Success TextCodingScheme:_7_bit_alphabet TimeStampUsed:No
SSI:1180867 D_SDS_Data Party_SSI:11-------- Type:UDT-4 Length:96 Protocol:Simple_location_system DATA:'000000110000000000100100010100000101001101000011010011110100001101001101001011000011001000110000' LocationSystemCodingScheme:0

 

[iw2dtt]

sds

SYSINFO - Main_carrier:2518 Offset:0 Frequency_Band:4
SSI:1180867 D_SDS_Data Party_SSI:1------- Type:UDT-4 Length:96 Protocol:Simple_location_system DATA:'000000110000000000100100010100000101001101000011010011110100001101001101001011000011001000110000' LocationSystemCodingScheme:0
SYSINFO - Main_carrier:2518 Offset:0 Frequency_Band:4
SSI:1180867 D_SDS_Data Party_SSI:1------ Type:UDT-4 Length:96 Protocol:Simple_location_system DATA:'000000110000000000100100010100000101001101000011010011110100001101001101001011000011001000110000' LocationSystemCodingScheme:0
SYSINFO - Main_carrier:2518 Offset:0 Frequency_Band:4
SSI:1188155 D_SDS_Data Party_SSI:1-------

Type:UDT-4 Length:32 Protocol:Text_Messaging MessageType:SDS-Report Delivery_status:SDS_receipt_acknowledged_by_destination_Destination_Success TextCodingScheme:_7_bit_alphabet TimeStampUsed:No
SSI:1180867 D_SDS_Data Party_SSI:----------- Type:UDT-4 Length:96 Protocol:Simple_location_system DATA:'000000110000000000100100010100000101001101000011010011110100001101001101001011000011001000110000' LocationSystemCodingScheme:0

 

[DarkAngelT]

Hello thewraith2008!
I want to thank you here for this spectacular Plugin! I would like to inform you of a few minor errors and if you will allow me to leave a humble suggestion.

About small errors:

1 - Sometimes I realize that the TTT loses some communications.
2 - TTT sometimes opens the audio of conversations that are disabled

Humble Suggestion:

Would it be possible to add transparency, redimensioning and change of the background color of the information window (F12)?

 

[thewraith2008]

D_SDS_Data Type:UDT-4 Length:96 Protocol:Simple_location_system
DATA:'000000110000000000100100010100000101001101000011010011110100001101001101001011000011001000110000'
LocationSystemCodingScheme:0

All the "Protocol:Simple_location_system" are returning same data. "$PSCOCM,20"

"LocationSystemCodingScheme:0" is National Marine Electronics Association "NMEA 0183 Interface Standard"

The "$P" indicates Extended messages. These extended messages are not standardized.

Some information on this protocol:
Info on Wiki
NMEA Revealed
NMEA Data

Decoding by hand from the above binary string is easy.
Just break it up in to 8 bits for each character.

Protocol ID = 00000011 [3]
Location System Coding Scheme = 00000000 [0] Must be 0 for MNEA 0183. Anything else is something else.

The remaining bits are for MNEA 0183 sentence.

00100100 $ 36 [0x24]
01010000 P 80 [0x50]
01010011 S 83 [0x53]
01000011 C 67 [0x43]
01001111 O 79 [0x4F]
01000011 C 67 [0x43]
01001101 M 77 [0x4D]
00101100 , 44 [0x2C]
00110010 2 50 [0x32]
00110000 0 48 [0x30]

If you see other messages that don't start with "$P" then you maybe able to decode something meaningful using the supplied resources.

 

[thewraith2008]

Hello thewraith2008!
I want to thank you here for this spectacular Plugin! I would like to inform you of a few minor errors and if you will allow me to leave a humble suggestion.

About small errors:

1 - Sometimes I realize that the TTT loses some communications.
2 - TTT sometimes opens the audio of conversations that are disabled

Humble Suggestion:

Would it be possible to add transparency, redimensioning and change of the background color of the information window (F12)?

Feedback and suggestions always welcome.

Can you elaborate on points 1 and 2.

1. You can only hear one call at a time. Missing other calls while listening to one call is the nature
of trunk radio. That's why you use lockouts and priorities.

2. Just a guess, in the main side panel for the plug-in (in SDR#) is the checkbox "Auto" checked. If yes then this is wrong. Must be unchecked.

I don't understand this "transparency". Can you add for what purpose.

The window already auto sizes to the largest label when seen, I don't see any reason for "redimensioning"

Changing of the background color could be done, but not high on the to do list. Any particular color?

 

[DarkAngelT]

Feedback and suggestions always welcome.

Can you elaborate on points 1 and 2.

1. You can only hear one call at a time. Missing other calls while listening to one call is the nature
of trunk radio. That's why you use lockouts and priorities.

2. Just a guess, in the main side panel for the plug-in (in SDR#) is the checkbox "Auto" checked. If yes then this is wrong. Must be unchecked.

I don't understand this "transparency". Can you add for what purpose.

The window already auto sizes to the largest label when seen, I don't see any reason for "redimensioning"

Changing of the background color could be done, but not high on the to do list. Any particular color?

Thanks for answering me.

The groups are already appointed and assigned priorities. But sometimes I realize that communication is rolling, but the other SDR is not active for listening. Simply The channel sometimes does not change or the listening frequency is not triggered.

As for the automatic function, it is already disabled

As for the suggestions, I will try to explain it better below:

Transparency: Possibility to use window transparency adjustable in percentage.

About resizing: I mean the hold and drag feature to increase or decrease window dimensions. (Done at the border with the mouse cursor)

About colors, background. It would be nice some button with color palettes.

Only same ideas!

Thank you once again for your work and attention!

 

[thewraith2008]

The groups are already appointed and assigned priorities. But sometimes I realize that communication is rolling, but the other SDR is not active for listening. Simply The channel sometimes does not change or the listening frequency is not triggered.

You are using the Dual mode of TTT, yes?

"But sometimes I realize that communication is rolling".
Can you explain this more. How do you "realize that communication is rolling" What is occurring with SDR#/Plug-in or TTT to indicate to you that you are missing something.

What is the "other SDR". Is that the SDR# CC or SDR# VC.

The SDR# CC is only for listening to the CC activity (in dual mode). It does not decode calls. That's what the SDR# VC is for.

I may try using SDR# CC for the 2nd half of the Duplex calls at a later date.

 

[hamradionl]

Just my ideas

I may try using SDR# CC for the 2nd half of the Duplex calls at a later date.

Yes, good idea.

Because iam not 24/7 whatching the screen some BLINKING background color or BEEP sound for the priority calls 1 or/and 2

 

[DarkAngelT]

You are using the Dual mode of TTT, yes?

"But sometimes I realize that communication is rolling".
Can you explain this more. How do you "realize that communication is rolling" What is occurring with SDR#/Plug-in or TTT to indicate to you that you are missing something.

What is the "other SDR". Is that the SDR# CC or SDR# VC.

The SDR# CC is only for listening to the CC activity (in dual mode). It does not decode calls. That's what the SDR# VC is for.

I may try using SDR# CC for the 2nd half of the Duplex calls at a later date.

1 - Yes, I am using dual mode. Because in dual the program works best in my opinion.

2 - I use two SDRSHARP folders. Named SDR1 and SDR2. One folder with SDR for #CC and one for #VC.
Here in my area #CC AND #VC happen on the same frequency. So ... When there is communication of some group that I prioritized and #VC is not triggered I soon realize, because the number of the group turns red in SDR # CC.

 

[DarkAngelT]

Just my ideas



Yes, good idea.

Because iam not 24/7 whatching the screen some BLINKING background color or BEEP sound for the priority calls 1 or/and 2

I would love it if it were possible to include in this program the sounds of the TELTRONIC MDT400 radio

With the initial and Final BIP similar to the TELTRONIC radios.

 

[DarkAngelT]

I would like to leave here, a message that appears right in my log. (I deleted some SSI-reported numbers, the rest of the information is complete.) I wonder if there is any location in it, because the only message that appears all the time is this type of message

TETRA_sds_data:

SSI: 2 ***** 7 D_SDS_Data Party_SSI: 1 ****** 3 Type: UDT-4 Length: 17 Protocol: Location_information SubType: Location_protocol_with_extension SubTypeExt: Immediate_location_report_request ReportType: Short

 

[DarkAngelT]

I would love it if it were possible to include in this program the sounds of the TELTRONIC MDT400 radio

With the initial and Final BIP similar to the TELTRONIC radios.

I already got the sounds from TELTRONIC. I also have HT SEPURA sounds.

If you decide to add this feature ... I would like to suggest you space for 3 sounds, so that we could choose the type of sound customizable for each option:

Sound for Group Communication Start (Group Communication Start Sound)

User transmission start tone (Each time a user speaks an initial beep)

And finally sound of the finalization of group communication. (it would be the sound of the end of the 5 seconds without transmission)

Basically with these 3 types

 

[thewraith2008]

2 - ..... So ... When there is communication of some group that I prioritized and #VC is not triggered I soon realize, because the number of the group turns red in SDR # CC.

I can't think of anything that would cause that. I'll try and keep an eye open to see if I get that here. I usually get 10000+ calls a day and I haven't seen that happen.

If you decide to add this feature ... I would like to suggest you space for 3 sounds, so that we could choose the type of sound customizable for each option:

Sound for Group Communication Start (Group Communication Start Sound)

User transmission start tone (Each time a user speaks an initial beep)

And finally sound of the finalization of group communication. (it would be the sound of the end of the 5 seconds without transmission)

Basically with these 3 types

How can something like that not drive you crazy.
Calls here are so fast and rapid that beeps would be going off all the time. Even with priorities been set.

TETRA_sds_data:

SSI: 2 ***** 7 D_SDS_Data Party_SSI: 1 ****** 3 Type: UDT-4 Length: 17 Protocol: Location_information SubType: Location_protocol_with_extension SubTypeExt: Immediate_location_report_request ReportType: Short

This is a request for "Location_information". Most likely the MS replies via uplink to the infrastructure and then is passed via internet or some other means. It can also be passing it to another LA as a downlink PDU. You would need to test that out by listening to different LAs in you network.

 

[thewraith2008]

Notes about how TETRA Demodulator plug-in handles calls.

Notes about how TETRA Demodulator plug-in handles calls.

The way that the plug-in indicates a call is via the main side panel:

And via "Calls" tab in "Network Info" window.

Because of the way the plug-in processes "calls", these two indicators do not always show correctly the real call details and is misleading people about what's really going on. They think they are missing something when they are not.

The plug-in activates calls via detecting the "D_TX_Granted" PDU. While this works as far as detecting any transmission, it does not serve to reflect a set-up call.

The correct way to display call is to use the "D_Setup" PDU and process all PDUs based on the "Call ID"

Calls can be:

• Individual [Simplex/Duplex]
• Group [Simplex]

The SSIs that are connected to a call can be anywhere on the network (MNC) across LAs.
You will only see a call set-up (D_Setup) on current LA if a SSI that is a part of the individual/group is on the LA.

Some generalized examples of different set-ups: (as seen via SSI1 on LA1)

Example #1
SSI1, SSI2 are on LA1
A "D_Setup" is sent from originating MS and both SSI move to carrier and timeslot and call occurs.
D_TX_Granted, D_TX_Ceased, D_Release are used during call and to end it.

Example #2
SSI1 is on LA1 and SSI2 is on LA2
A "D_Setup" is sent from originating MS SS2 (LA2) to LA1
A "D_Connect" is sent on LA1 and SS2 is setup on a carrier and timeslot (on LA1, this has it's own Call ID)
SSI1 and the patched in SSI call are set-up to a carrier and timeslot set by "D_Setup" PDU and call occurs.
The same is most likely occurring on LA2 so SSI2 can hear SSI1
D_TX_Granted, D_TX_Ceased, D_Release are used during call and to end it.

The plug-in simply shows example #2 as having two calls that could be listened too, when in fact the two Call IDs are the same call. One of the Call IDs (the D_Setup one) is the correct one to be listening too. The 2nd one is only the patched in SS2 and if you listen to this, is only one sided.


The "Calls" tab in "Network Info" window has the call list which is cleared via a timer and not when a call actually ends. (When D_Release is seen).
This method is necessary because D_Release is only seen on the carrier where call ends.
D_TX_Granted resets the timer for each Call ID when seen, there for prolonging calls presence in the list.

In the next release of the plug-in, I have added an alternative call list generation that uses "D_Setup" and some other PDUs to more accurately display Individual [simplex/duplex] and Group [simplex] calls.
This will be better suited to the Dual mode setup of TETRA Trunk Tracker since it does not change CC frequency. Single mode changes frequency when switching to VC there by resetting window contents.

Hopefully this helps understanding how the plug-in works with calls.

 

[hamradionl]

In the next release of the plug-in, I have added an alternative call list generation that uses "D_Setup" and some other PDUs to more accurately display Individual [simplex/duplex] and Group [simplex] calls.
This will be better suited to the Dual mode setup of TETRA Trunk Tracker since it does not change CC frequency. Single mode changes frequency when switching to VC there by resetting window contents.
Hopefully this helps understanding how the plug-in works with calls.

Thank you for explanation.

BEEPS and/or COLOUR labels
When we listening to analogue we hear 5TVO, Roger Beep, repeater Beep Callsign and more beeps the whole time of day and digital DMR also give some beeps sounds

TTT the BEEP only sounds when setup the Priority to 1 or 2 or 3 other priority's 4 - 9 No BEEP
And a Beep OFF or Mute is nice function when its get to wild or crazy
Its just because when TTT is running in background and listener is doing other things in the room or house or when driving around, the TTT priority user become active, the small beep sound give that attention.
Myself have also far over 10000 calls a day time and only 4x users GSSI or SSI i give a priority 1 message i dont want to missing those calls. Some have priority 4 and other calls are low level talk mostly woman about coffee and eating

 

[DarkAngelT]

In the future it would be great if we could have the TTT and the Tetra Demodulator merged into a single plugin! But I know how laborious every change in an application is! I will always be grateful to TSSDR who started the Tetra Demodulator and you thewraith2008 who created the TTT! Thank you for creating such good quality plugins! I confess that when the TETRA communications started in my area I still had no financial possibilities to even hear the analog and when I started to listen the communications were already digital for years. I was sad that I did not know how the services of my region worked. But years later, thanks to you, I can hear you today! Thank you so! You are making history! I hope this story lasts for many, many years!

 

[DarkAngelT]

I can't think of anything that would cause that. I'll try and keep an eye open to see if I get that here. I usually get 10000+ calls a day and I haven't seen that happen.

I think I figured out what was causing a loss in communications. A silly thing!
The Ignore Call Priority option was checked. With that some priority call came in, the communication did not change immediately for her!

After deselecting this option, whenever there is some non-priority communication and a priority is initiated, the TTT immediately changes the channel!

I'm currently experimenting with TTT Single mode and it's working just as well as Dual Mode!

Congratulations on the application! I never tire of thanking and praising! Thank you very much!

 

[thewraith2008]

I think I figured out what was causing a loss in communications. A silly thing!
The Ignore Call Priority option was checked. With that some priority call came in, the communication did not change immediately for her!

After deselecting this option, whenever there is some non-priority communication and a priority is initiated, the TTT immediately changes the channel!

I'm currently experimenting with TTT Single mode and it's working just as well as Dual Mode!

Congratulations on the application! I never tire of thanking and praising! Thank you very much!

Good to hear you you sorted your problem.

If your network is only one carrier then there is no difference between Single and Dual mode feature wise.

Thanks your your praise