TETRA Trunk Tracker for use with SDR# and TETRA Demodulator plug-in

Show off any of your RTL-SDR or cheap SDR related projects.
thewraith2008
Posts: 15
Joined: Sat Mar 24, 2018 1:38 am

Re: TETRA Trunk Tracker for use with SDR# and TETRA Demodulator plug-in

Post by thewraith2008 » Fri Jul 27, 2018 3:16 pm

I just tried link and it's OK. (with Firefox)

If you are using content/ad-blockers, you may need to disable them.

oscarhsu84727
Posts: 2
Joined: Fri Jul 27, 2018 2:25 pm

Re: TETRA Trunk Tracker for use with SDR# and TETRA Demodulator plug-in

Post by oscarhsu84727 » Fri Jul 27, 2018 3:34 pm

I tried Chrome, Firefox and IE, and turn off all plugins.
The problem still occurred.
Can you send the file to my via e-mail.
My mail address is [email protected]
Thank you again!!

digiman
Posts: 5
Joined: Wed Jul 25, 2018 8:25 am

Re: TETRA Trunk Tracker for use with SDR# and TETRA Demodulator plug-in

Post by digiman » Sat Jul 28, 2018 2:17 pm

Every now and again I see some SSI coming up as if there is a call about to take place these it disappears, these are listed with D_Connect_Acknowledgea.. What are these ? should these be coming through as calls ?

thewraith2008
Posts: 15
Joined: Sat Mar 24, 2018 1:38 am

Re: TETRA Trunk Tracker for use with SDR# and TETRA Demodulator plug-in

Post by thewraith2008 » Sat Jul 28, 2018 3:16 pm

D_Connect_Acknowledge is to tell the Called MS that it's time to through-connect.
This is only part of a call set-up process.

Many connections can be made with different combinations.

A call can be Individual (Simplex or Duplex) or Group (Simplex)
The plug-in can only play the simplex transmissions that SSI make via D_TX_Granted and D_TX_Ceased PDUs. I'm sure it ignores any duplex transmissions, That's why you sometimes see activity indicated but no audio.
It can be a little erratic with playing these transmissions.

With Duplex, the plug-in can't play two timeslots at once. (What a bummer.)
I'm not sure if duplex calls must be on same carrier or can be on different carriers or even different carriers on another LA. It stands to reason it would.

Any duplex calls set-up with "D-Setup" in my network are always "Not Granted" even though the call is actually taking place. I have manually verified this.
Because the plug-in doesn't output any usable info to make the connection, using TETRA Trunk Tracker to listen to duplex it is not yet possible. Not sure if plug-in is altering it to be "Not Granted" or if its sent that way as a protection trick?

All calls are (and should be) set-up with D-Setup PDUs. I found the stand alone plug-in hard to listen to because it was jumping from one timeslot to the next when more the one was in use. (because it only used D_TX_Granted and D_TX_Ceased PDUs)
Because of the nature of trunking you don't always see these D-Setup PDUs. These where probably sent on a different LA then the one you where listening too. You only see D_Connect.

Hopefully this helps. Ended up been a bit longer post then expected.

digiman
Posts: 5
Joined: Wed Jul 25, 2018 8:25 am

Re: TETRA Trunk Tracker for use with SDR# and TETRA Demodulator plug-in

Post by digiman » Tue Jul 31, 2018 10:56 am

Thank you for that!.. I think it makes sense :)

thewraith2008
Posts: 15
Joined: Sat Mar 24, 2018 1:38 am

New Update

Post by thewraith2008 » Sat Aug 04, 2018 1:37 am

This is the fifth release of this program. (TETRA Trunk Tracker v0.99.8)

It is in alpha stage. This means is may contain errors that may cause issues with the other programs it
works with. i.e. crashing them or itself. Although I'm not seeing this.

If SDR# is crashing when 'Demodulator' is enabled, it's because you have not set-up the plug-in correctly.
You MUST do this 1st. This is NOT TETRA Trunk Trackers fault.

You generally need to get these installed:
"Microsoft .NET Framework 4.6.2 (Offline Installer)"
"Microsoft .NET Framework 4.7.2 (Offline Installer)"
"Microsoft Visual C++ 2015 Redistributable" and install both 32/64 bit versions (if you use 64 bit OS)

The TETRA plug-in currently(?) been developed by TSSDR is also in early development. Because of this
any changes made in plug-in releases most likely will break this program.


Two versions are available:
  • Normal (Uses 2 SDR# and 2 Dongles)
  • Simple (Uses 1 SDR# and 1 Dongle with some features not available)
This version adds and fixes some items:
  • Have merged SDS location plotting (via DSDPlus LRRP) back into in both versions.
  • - Settings are return back to be saved as "tetra_trunk_tracker_simple.dat"
  • - New version of settings file requires re-creating it.
  • ADDED: Command line option for SDR# bandwidth adjustment.
  • ADDED:Compact mode now is "On Top" of all other windows.
  • FIXED: When TTT was closed in Compact mode then restarted, there was no way to start TTT (click Start)
  • - This adds start button to compact window.
  • ADDED: Simple version - Restored call priorities (limited function).
  • FIXED: Tool "TETRA popup error dismisser" did not work with non english pop-ups dialogs.
  • See 'changelog.txt' for more details.
Has been tested on Windows 7 - Professional SP1 (32 bit), English
Has been tested on Windows 10 - ? (64 bit)

The more people that report what their OS is that they got TETRA Trunk Tracker working in, the better. I can add to list.
(Is it Windows 7,8,10 - Basic, Home, Professional, Ultimate, Enterprise - 32/64 bit)


I have created it to suit my needs. And it currently works for me with the TETRA network I monitor.

I make no claim that it will work for other networks.

Please read the provided files for set-up and usage:
  • TTT_set-up_manual.pdf
  • TTT_Features_and_Usage.pdf
  • TTT_SDS_test_version_usage.pdf


I have tried to be as thorough as possible with the documentation to explain usage and features.
I believe any questions can be answered by reading these files.
These files most likely are not complete and contain errors and are not laid out as good as they could be.

It only works with the provided TETRA plug-in supplied in zip. (2018-June-06).
This version uses a custom compiled version of 'Net Remote' supplied in zip

It is only meant to be a temporary solution until something better comes along.

Hopefully all goes well for you setting it up.

Download link

MD5 HASH 463482c9f730fe09dad1fb4c0cb3b4ca

polar
Posts: 1
Joined: Sun Aug 12, 2018 4:09 pm

Re: TETRA Trunk Tracker for use with SDR# and TETRA Demodulator plug-in

Post by polar » Sun Aug 12, 2018 4:16 pm

Greetings!

Thank you for this software, it works great on Windows 10 Pro 1803 x64.
I have a question regarding future releases. Would it be possible to decode message content? Every now and then I see messaging_protocol listed on log, is it possible to see the content without registering to the network?
Here in Zagreb, local public transport service uses their own tetra network for voice, vehicle position and the service I'm trying to get to: public display information. Tetra is being used to send real time schedule updates to station displays for trams and buses. Signal is not encrypted, at least voice is not, but I'm trying to intercept the display messages without registration.

Thank you in advance for reply!

EDIT:

Here is the log line i was refering to:
SSI:20123 D_SDS_Data Party_SSI:1008 Type:3 Protocol:Text_Messaging

thewraith2008
Posts: 15
Joined: Sat Mar 24, 2018 1:38 am

Re: TETRA Trunk Tracker for use with SDR# and TETRA Demodulator plug-in

Post by thewraith2008 » Mon Aug 13, 2018 1:31 am

TETRA Trunk Tracker can not do what the plug-in doesn't.
That been said, I have been playing around with the plug-in trying to see these two items:

"Text_Messaging"
"Long location report PDUs" i.e GPS Location data.
The TETRA Demodulator plug-in only does "Short location report PDUs".

I've increase the output of "Text_Messaging" to see whats there.
SSI:123456 D_SDS_Data Party_SSI:789012 Type:3 Length:32 TextCodingScheme:16 Textdata:0000000010001100 Protocol:Text_Messaging
Only 1 character = "Œ" (DEC[140], HEX[8C])
I think most of whats here is user defined. And I doubt there would be any readable stuff. Doesn't hurt to look though.

For "Long location report PDUs" I have setup some code but unfortunately I don't receive these PDUs where I am so I can't test it.

I need someone to upload some IQ samples (created by SDR#) of these "Long location report PDUs" and "Text_Messaging" occurring.

With out these samples I can't do much to implement it.

Post Reply