New TETRA Trunk Tracker for use with SDR# and the TETRA Demodulator Plugin

Over on our forums user thewraith2008 has just released news about his new software called TETRA Trunk Tracker. The software works in conjunction with the TETRA demodulator plugin for SDR#. It works by using two dongles, one to monitor a TETRA trunking channel, and the other to decode voice audio, although a single receiver mode is also available which works with a reduced and fixed bandwidth.

TETRA Trunk Tracker
TETRA Trunk Tracker

The post reads:

TETRA Trunk Tracker will follow calls on a TETRA network.

TETRA Trunk Tracker reads DATA that is output from the SDR# plug-in TETRA Demodulator (by TSSDR) via the 'Network Info' calls log window.

It interprets this DATA to determine when a call is set-up, then instructs SDR# (VC) to move to the carrier (frequency) that the call will be on.

It will also watch out for other PDUs to determine when a SSI starts or completes transmissions and when calls are complete (Released).

Features:

  • A basic call recording (All or Selective call recording).
  • Display current call details with list of seen SSIs for that call. (SSI populate as they TX).
  • GSSI holding - will only allow calls with selected GSSI to be heard.
  • Call lockout based on GSSI. Can be unchecked in list to lockout GSSI.
  • Call Priority. (Only normal version)
  • GSSI weighted 0-9, 9 is highest. If on active call and other call event occurs, if new call has higher
  • priority then will switch to it.
  • Collect/Save all seen GSSIs with Labels and Priority, By Network.
  • Collect/Save seen SSIs with Labels and Last seen Date/Time, By Network.
  • Set a call time-out. Returns to idle state if call does not see a release PDU
    after X time in seconds.
  • Log call events to screen and file, if enabled.
  • Log raw CC and VC PDU messages as seen by the 'TETRA Demodulator' plug-in, if enabled.
  • Log GSSI daily call activity. (Simple version does not play calls when this is selected)
  • Set base frequency via UI.
  • Set CC park carrier # via UI.
  • Set VC park carrier # via UI.
  • Suppress some PDUs. (unchecked is mainly for testing only)
  • Suppress lockout messages.
  • Sort SSI and GSSIs/Lockouts (by GSSI). This only occurs on start-up.
  • Country Code label, defined via file (shown as menu item)
  • Network label, defined via file (shown in tool tip where MNC,LA is in 'Call Details' panel)
  • Location Area label, defined via file (shown in tool tip where MNC,LA is in 'Call Details' panel)
    Only shown when Network label used.
  • Ignores Encrypted PDUs (with no reference to them)
  • Set a seen GSSI priority via UI.
  • Update a seen GSSI/SSI label via UI.
  • Call active indicator.
  • Restore SDR# windows to a defined position.

If the TETRA Demodulator does not work for you this program will do nothing to change that.

This is the third release of this program. (TETRA Trunk Tracker v0.99.6)
And 2nd release for (TETRA Trunk Tracker v0.99.6s - Simple)

Two versions are available:

  • Normal (Uses 2 SDR# and 2 Dongles) with TETRA Demodulator and Net Remote plug-ins
  • Simple (Uses 1 SDR# and 1 Dongles with some features not available) with TETRA Demodulator and Net Remote plug-ins

Backup your "Tetra-trunk-tracker.dat" settings file.
Then delete "Tetra-trunk-tracker.dat" as it has changed and old one will cause error on load.

Some work as gone into trying to make TETRA Trunk Tracker easier to run once the initial setup has been done.

A MCC (Country Code) label file is included for your convenience "TETRA_mcc.txt".

It has only been tested on Windows 7 - Professional SP1 (32 bit), English

You MUST have a PC that is capable of running SDR# x 2 with the TETRA plug-in. (Not overloaded CPU usage.)

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.

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.

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

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 6f33fcf9662573b77e177e899793b9f9

Video showing starting it and it running
Video showing starting it and it running - Simple version

44 comments

  1. qba

    Hi,

    I am struggling with the following:
    when I center the WFM band to the pick of TETRA signal and tetra_trunk_trucker_simple starts to finding calls, the center of the band within sdr# jumps 30Mhz down (from 391Mhz to 361Mhz and stops).
    The same situation when I manually start tetra_trunk_tracker by clicking on green start button.
    Any ideas ?

        • thewraith2008

          As I said in previous post, “You most likely have not set the “CC Park” carrier number.”
          And you have not.
          The video shows this to be “3648” (391.2125MHz). This is your “CC Park” carrier number.
          Main carrier = “CC Park” (CC = Control Channel)

          You also need to verify you are using the correct offset, or further incorrect tuning will occur.

          All this is covered in the supplied documentation.

  2. Anonymous

    https://forums.radioreference.com/voice-control-channel-decoding-software/370639-sdr-tetra-demodulator-trunk-tracking-demonstration-6.html

    TETRA Demodulator plug-in has been updated by me. “Tweaked Edition (Unofficial) v1.0.0.5” (tetra_x86_2018-09-11)
    It’s is required for some SDS features to work with TETRA Tunk Tracker v1.0.5. Please read text files in zip for plug-in.

    This plug-in version changes/adds and fixes some items:

    FIXED .NET pop-up errors. Should no longer require “TETRA popup error dismisser’ is you use it.
    ADDED: Increased some PDUs verbosity.
    ADDED: Audio DSP – Bandpass filter and AGC
    ADDED: Support for D_SDS_Data long location report. [Experimental]
    ADDED: Support for D_SDS_Data Text Messaging. [Experimental]
    Interval for displaying output to “Network Info” window.
    See ‘SETUP.TXT’ and ‘UPDATE.TXT’ for more details.

    Screen scraping logging : https://teknokoodiradio.vuodatus.net/lue/2018/09/sdr-tetra-plug-in-network-info-pdu-logger

  3. roboslaw

    My problem is that the value shown in ‘TETRA Demodulator’ “Network Info” > Current > Offset is “3”
    Any idea how to set this up?

  4. enCrypt

    Thankyou so much for this.
    I have it working, sort of, but i have the following questions:
    1. On my CC SDR any Tetra freq I connect to seems to imply that it is a control channel as it has Main and Current values the same. On the VC SDR I dont always see anything in Main (00.000MHz) but current is always correct. Do I need to be seeing something in the Main section on the VC SDR for it to work?

    2. Does the VC park freq need to be on a completely unused frequency that is within 12.5KHz of the CC freq?

    3. I see the volume slider moving on the VC SDR whenever “Call” is green but it is not actually un-muting the VC SDR. Any idea what that might be? (Just to confirm that I have a single SDR# running fine already with the Tetra Demodulator)

    3. In Tetra Demodulator, does the Voice Auto box need to ticked on both CC and VC SDRs, only on one or on neither?

    Thanks

    • enCrypt

      Hmm, now I’m hearing transmissions but it is the CC SDR that is un-muting!
      Going to try the simple (1 RTL) version…

        • thewraith2008

          1. If all your TETRA frequencies when tuned to, show ‘Main’ and ‘Current’ as the same value (but LA is different) then your network does not have additional traffic frequencies, only different location areas.

          2. Yes, must be unused. Can be any unused frequency within the selected frequency band. TETRA Demodulator plug-in does not always show correct carrier number when unused frequency is selected. (It does not know offset yet) That’s why I say NOT to place VC Park 12.5KHz from any other active frequency.

          3. Most likely you have not followed the set-up instructions.
          3(4). Auto should be off. See #3

          TETRA Trunk Tracker and SDR# needs to have an initial set-up completed before it works correctly.
          Please read the PDFs that are supplied in the zip file (in “docs” folder).
          -TTT_Set-up_manual.pdf [This is mistakenly named “TTT_SDS_Set-up_manual” in v0.99.8]
          -TTT_SDS_Set-up_manual.pdf [This is mistakenly named “TTT_Set-up_manual” in v0.99.8]
          -TTT_Features_and_Usage.pdf

          • enCrypt

            Thankyou very much for your reply, yes I do have a number of different LA values and colour codes within the same network, however I’m not sure if this makes it easier or harder for the Trunk Tracker to follow conversations?
            I did actually get it all working as it should last night after some trial and error. I found my main problem was that I needed to make sure I was exactly ‘bob on’ the signals on both SDRs (i.e. having to alter PPM values once the RTL sticks have warmed up. I assume that the number directly under the Red “Received” marker in Tetra Demodulator needs to be higher the better?)
            I did read through all the docs but may not have been interpreting some of them correctly.
            Anyway, thanks again for what you’ve done.
            I’m using it right now and going to try some of the more advanced uses like GSSI / SSI naming, recording etc

            • thewraith2008

              Glad to hear you got it going.


              yes I do have a number of different LA values and colour codes within the same network, however I’m not sure if this makes it easier or harder for the Trunk Tracker to follow conversations?

              TETRA Trunk Tracker determines where to switch to based on PDU D-Setup. So if it says call is on carrier 1234 @ timeslot 2 then it sets that up. It doesn’t switch between LAs in a network, although SSIs in a call can be connected from other LAs.

  5. uniden355

    Hi all. I’ve already try to configure as stated in the manual with supplied Net Remote plugin but the plug in is not appear on side bar of the SDRSharp. Mine using SDRSharp ver 1637, OS Windows 7 Ultimate x64 with SP1 installed, .Net Framework 4.72, VCredist 2017 and 2013 (both x86 and x64 installed). Trying with SDRSharp version 1668 with no luck (still no Net Remote plugin appear on side bar). But Tetra demodulator is working flawlessly. Can anybody give me some clue to solve my problem?

    • thewraith2008

      Please make sure your using the “Net Remote” from the TETRA Trunk Tracker v0.99.7.
      This has the the 32 bit version of “Net Remote” plug-in. (64 bit didn’t work.)

      Also make sure you have added the “MagicLine” to “Plugins.xml” file in your SDR# folder.
      Information about this is in “ThisVersion.txt” file in zip file “NetRemoteCustom.zip” in the plug-ins folder.

      I’ll update the PDF to include this info.

      • uniden355

        Yup, I’ve already put Net Remote plugin from the TETRA Trunk Tracker v0.99.7 onto SDR# folder (version 1670) and adding magic line into plugins.xml. Tetra Demodulator plugins is ok but Net Remote plugins still doesn’t appear on sidebar. I have no idea so far….

      • uniden355

        After trying many times, the last attempt is installing net remote plugin with the original one from Ear To Ear Oak. After successful installation then net remote plugin appear on SDRSharp side bar, continue to exit the application and replace with supplied net remote plugin from TTT. Voila… it works perfectly. This can be happened when net remote plugin not yet installed before (fresh install of SDRSharp). Problem solved…

        • thewraith2008

          Strange, as far as I know the installer for “net Remote” only copies the DLL file and modifies the “plugin.xml” file.

          It worked for you that’s the main thing.

    • thewraith2008

      The link to the latest version is in forum ‘User Projects’. Look for last update post.

      This link to forum post is given at beginning of article above as “released news”

      I have no idea how to add link here.

    • thewraith2008

      No one knows where TSSDR has gone. Maybe just a well deserved break. And from what I understand, he does not even have live TETRA in his location and developed the plug-in from IQ samples. Amazing really.

      I do not have his source code.
      My work is independent from his but with the goal of improving on what already has been done.
      People love to jump to conclusions.

        • thewraith2008

          I’m sure it would possible to process the Normal/Sync continuous downlink bursts output from UDP, I would be concerned that the further delay would cause an issue with timing of calls possibly cutting off the beginning of a call. Which already seems to happen in some cases.

          While I have inspected the UDP for bursts and found the sync, I have not gone further than the descrambling of broadcast/block1 and 2 bits through RM(30,14).
          This is a lot beyond my knowledge on the subject.

          I think in the end it would be better to start something from scratch.

          • Anonymous

            … realtime decoding may not be possible but how about some kind of buffering and decoding bit later in a separate process/machine …?

  6. Hennie

    I am using tetra_trunk_tracker_simple.exe and I am holding 1 group. This is working very well for a while but now and than I see the following error:

    System.NullReferenceException: Object reference not set to an instance of an object
    bij SDRSharp.Tetra.NetInfoWindow.UpdateTextBox(List`1 rawData)
    bij SDRSharp.Tetra.TetraPanel.TimerGui_Tick(Object sender, EventArgs e)
    bij System.Windows.Forms.Timer.OnTick(EventArgs e)
    bij System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
    bij System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

    I use the simple version because when I open 2 times SDR I get an error on “net remote”, port already opened. This makes sense since a port can be opened only once. How to solve these problems?

    • thewraith2008

      I made a utility program to deal with this pop-up error. It is supplied.
      You are not using the supplied ‘Net Remote’ plug-in.

      All this is covered in the supplied documentation. (Which I spent some time preparing)

  7. Lars

    Seems to work very well with MCC: 240 MNC: 11 in simple mode here in Stockholm.
    Each LA seems to have 4 channels in my area and my strongest ones are within 2 MHz so simple can handle it.

    • thewraith2008

      “… are within 2 MHz so simple can handle it.”

      TETRA Trunk Tracker is not restricted by the bandwidth of the dongle. VC (carrier/frequency) can be anywhere within the 100 MHz for a given frequency band.

        • thewraith2008

          Thanks, glad it’s working for you.
          Yes, that’s correct. No call priorities in single mode (Simple).
          Logging to CSV is restricted to a logging only mode, but in the end works the same.

          I’m testing adding SDS Location Data (GPS) as well. Which works with DSDPlus LRRP program to display on map. I’ll add more about this in a post in the forums with a link to a video demonstrating it later.

  8. Graham

    Figured it out.. Running really good on simple, I will sort out a 2nd dongle and try the advanced tracker… Class job.

  9. Graham

    Mines SEEMS to be working, it seems to be tracking etc but after a DRelease I get UI Reset and my freq changes to something random.. still figuring out..

    If my control channel is 393.8625 what should be my base and CC park be ?

    • thewraith2008

      Your Base Frequency would be “300 MHz”

      Select 393.8625 MHz frequency in SDR#. In the TETRA Demodulator panel, it will show the “Current” xxxx 393.8625 MHz
      “xxxx” is the carrier # and is the “CC Park”
      “Main” indicates what CC is for that network (MNC).

      “but after a DRelease I get UI Reset and my freq changes to something random”
      This is most likely moving to the default carrier “2604” and default “Base frequency” [800 MHz] which would be around 865 MHz

      Please also make sure you set the correct “Offset”.
      This value is shown in ‘TETRA Demodulator’ “Network Info” > Current > Offset

    • thewraith2008

      That error shows that you have not set-up the program correctly. Please read “TTT_Set-up_manual” for details on setting up properly. This is a must.

      I have only tested with Windows 7 Professional 32-bit.
      Others have said for Windows 10 run TETRA Trunk Tracker with elevated privileges “Run as Administrator”

      Please note that you must have TETRA Demodulator plug-in running and working with SDR# before using with TETRA Trunk Tracker.

Post a comment

You may use the following HTML:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>

This site uses Akismet to reduce spam. Learn how your comment data is processed.