SDR# TETRA Demodulator Trunk Tracking Demonstration

hg69956

Newbie
Joined
Apr 1, 2019
Messages
3
I'm using W10 and did install .NET 4.7.2 before and i started testing TTT. I somehow got it working after disabling logging and recording directly after TTT was started. When the first call came in it didn't crash en turning on logging en recording after that didn't cause TTT to crash.

After that no more crashed when the first call comes in. I'm not completely sure disabling both did the trick because I can't reproduce the problem.
 

DriverVehicle

Newbie
Joined
Apr 3, 2019
Messages
1
Hi!
I am using the TTT in simple mode for a few days.
Is there any possibility to listen both sides of a talk in individual calls?
I only listen to the control center but not to the addressed radio.

In group calls I can listen to the whole conversation.

In TX ISSI I see the correct ISSI of the radio and I guess, that the radio is transmitting, but I don't hear the voice.

Is this helping?
Code:
03.04.2019 21:38:23 - Call ID: 6182 - On carrier: 1132 TS:3 - Private call - Simplex[half] (534345 to 185950)
03.04.2019 21:38:23 - Call ID: 6182 - Calling ISSI: 534345
03.04.2019 21:38:24 - Call ID: 6182 - VC D-TX-Ceased ISSI: 534345
03.04.2019 21:38:26 - Call ID: 6182 - VC D-TX-Granted ISSI: 185950
03.04.2019 21:38:28 - Call ID: 6182 - VC D-TX-Ceased ISSI: 185950
03.04.2019 21:38:31 - Call ID: 6182 - VC D-TX-Granted ISSI: 534345
03.04.2019 21:38:49 - Call ID: 6182 - VC D-TX-Granted ISSI: 185950
03.04.2019 21:38:58 - Call ID: 6182 - VC D-TX-Ceased ISSI: 185950
03.04.2019 21:38:59 - Call ID: 6182 - VC D-TX-Granted ISSI: 534345

Code:
21:38:23 - SSI:534345 Call ID:6182 D_Setup Transmission Not_granted Party_SSI:185950 Mode_of_Operation:Simplex Basic_service:Individual Clear Speech_TCH_S
21:38:23 - Carrier:1132 TimeSlot:3 SSI:534345 Call ID:6182 D_Connect_Acknowledge Transmission Granted_to_another_user
21:38:24 - SSI:534345 Call ID:6182 D_TX_Ceased
21:38:26 - SSI:534345 Call ID:6182 Encrypt:Clear D_TX_Granted Transmission Granted_to_another_user Party_SSI:185950
21:38:28 - SSI:534345 Call ID:6182 D_TX_Ceased
21:38:31 - SSI:534345 Call ID:6182 Encrypt:Clear D_TX_Granted Transmission Granted
21:38:49 - SSI:534345 Call ID:6182 Encrypt:Clear D_TX_Granted Transmission Granted_to_another_user Party_SSI:185950
21:38:58 - SSI:534345 Call ID:6182 D_TX_Ceased
21:38:59 - SSI:534345 Call ID:6182 Encrypt:Clear D_TX_Granted Transmission Granted
21:39:06 - TS3_unallocated 5
21:39:24 - SSI:534345 Call ID:6182 Encrypt:Clear D_TX_Granted Transmission Granted_to_another_user Party_SSI:185950
21:39:30 - SSI:534345 Call ID:6182 D_TX_Ceased
21:39:32 - SSI:534345 Call ID:6182 Encrypt:Clear D_TX_Granted Transmission Granted

Code:
21:38:23 - Call ID               : 6182
21:38:23 - Seen D_Call_Proceeding: False
21:38:23 - Seen D_Setup(No grant): True
21:38:23 - Seen D_Alert          : False
21:38:23 - Seen D_Connect        : False
21:38:23 - Seen D_Connect_Ack    : True
21:38:23 - Carrier 1             : 1132
21:38:23 - TS1                   : 3
21:38:23 - Carrier 2             : 0
21:38:23 - TS2                   : 0
21:38:23 - GSSI                  : 0
21:38:23 - ISSI Caller           : 534345
21:38:23 - ISSI Called           : 185950
21:38:23 - Call type             : Individual
21:38:23 - Mode                  : Simplex
21:38:23 - result                : 3

Code:
21:38:23 -  SSI:534345 Call ID:6182 D_Setup Transmission Not_granted Party_SSI:185950 Mode_of_Operation:Simplex Basic_service:Individual Clear Speech_TCH_S
21:38:23 -  Carrier:1132 TimeSlot:3 SSI:534345 Call ID:6182 D_Connect_Acknowledge Transmission Granted_to_another_user

I am looking forward to your help or solutions. :)
 
Last edited:

Ubbe

Member
Joined
Sep 8, 2006
Messages
9,796
Location
Stockholm, Sweden
Tetra isn't a repeater system like DMR and others. The info it receives from a basestation are decided by the system if it should be retransmitted out on particular basestations or not. TG's are sent out to basestations where the system has logged that a user with that TG are listening. Private calls radio to radio are transmitted out on a single basestation where the other party is listening. If a dispatcher and radio talks in a private call the audio from the radio are not transmitted out on any site. If a radio sends status messages or GPS positions those are also not retransmitted out on any basestations.

/Ubbe
 

thewraith2008

Member
Joined
Nov 22, 2016
Messages
1,884
Hi,

I've been using TTT 1.0.7 for some while now and is all working fine. I'm trying out TTT 1.0.14 on my mobile setup to see if it's safe to upgrade my setup at home. When trying 1.0.14 it crashes as soon somebody is talking on the Tetra network.

TTT freezes but SDR# keeps running. I'm using SDR# v1700 and used the files from the latest release (plugins etc.). I also tried running TTT as admin but no difference.

Does anyone experienced this problem before?

Does it crash with a error message? Or is the crash just the freezing?
After some pop-up errors TTT is halted and requires restart.
By freezing do you mean TTT has become unresponsive or nothing is happening anymore. (i.e. halted)

I find when TTT freezes, it is hung up on waiting for a response from SDR#. Normally SDR# has crashed in this case, which you said your SDR# has not crashed.

When updating TTT, if TTT doesn't do it for you, then deleting the file "tetra_trunk_tracker.dat" may help with some of the strange unforeseen errors. Re-configuring will be required.



Latest version (v1.0.14) can be found here: Release post
 

thewraith2008

Member
Joined
Nov 22, 2016
Messages
1,884
Hi!
I am using the TTT in simple mode for a few days.
Is there any possibility to listen both sides of a talk in individual calls?
I only listen to the control center but not to the addressed radio.

In group calls I can listen to the whole conversation.

Private calls require a few PDUs to allow a full simplex/duplex call.
As Ubbe mentioned, users can be in different places (LA) in a network (MNC)

When both MS's are on same LA, then all the required PDUs (+speech) are sent on downlink to allow identification of both MS's (ISSI) that enter a call. These are the full simplex/duplex private call set-ups. Full duplex can only seen when TTT is in 'Dual mode').

When MS's are on different LA's, then only the PDU's addressing the MS on the current LA will be seen on the downlink, this is to allow identification of the MS (ISSI). The speech for the other MS on a different LA will be heard but not the local MS speech. If it where a group call and there were more MS's on the current LA then the MS's speech would be returned to the downlink.
Both MS's can still be identified even though only one MS will be heard, like in your case. These are the "[half]" private call set-ups.

In TX ISSI I see the correct ISSI of the radio and I guess, that the radio is transmitting, but I don't hear the voice.
I am looking forward to your help or solutions. :)

As describe above, the local MS speech is not returned to to downlink, because there is no-one there to listen to it. The BS still sends the D-TX-Granted and D-TX-Ceased PDUs so the local MS still knows when it can TX/RX.

The next update will have an option to ignore these '[half]' calls and only allow calls that have both MS's present.
There will also be an alternate private call set-up option. These are only [half] set-ups and are only included for those who maybe interested in the content of such transmissions.



Latest version (v1.0.14) can be found here: Release post
 

hermite

Member
Premium Subscriber
Joined
Nov 24, 2010
Messages
42
Location
Montreal Quebec
8th Public Release - TETRA Trunk Tracker v1.0.8 - PART 2 of 2 post.



This TETRA Trunk Tracker version changes/adds and fixes some items:
Code:
v1.0.8.0

FIXED: There was no call release sound (when used) when D_Release PDU was not seen (when call timeout occurred)

CHANGED: TTT call state/priority sounds
         The call setup sound will not play if priority is triggered and if the priority sound exists.
         If the priority sound does not exist and priority is triggered then the call setup sound will play.
         Because playback of both sounds occur almost at same time, it can make it a bit hard to hear each sound.

ADDED: Option to disable the 'Network Info' window minimizing.
ADDED: Save/Restore 'Network Info' window position.

ADDED: G/SSI Editor - Right clicking in GSSI lisbox and pressing either "CTRL" or "Shift" will set or
       clear all GSSIs lockout states in the list respectively.
       A limitation of the listbox with checkbox means multi-select entries is not possible.

ADDED: Cancel the record 'Hold Delay' by clicking the visual counter for the record 'Hold Delay' when it is active.
       The counter is in the same place as the call timeout counter which is next to the call indicator and is redish when active.

FIXED: Position SDR#/Network Info window value, if not set would cause crash of TTT.
ADDED: If desktop size has changed since last run and window positions are outside desktop, then values will be
       reset to a default values inside desktop.

FIXED: TTT would hang on shutdown when SDR# was started with no dongles connected.

ADDED: Timeslot information to call event log entry. (as TS:#)

FIXED: Some D_TX_Granted PDUs where been missed because of a slight difference in element structure.

FIXED: Some D_TX_Ceased PDUs where been missed because of De-duplication of PDUs.
       These PDUs are fairly generic and where been removed in some cases.

ADDED: Defined rules for PDU 'D_STATUS'. NOTE: The Pre-coded values are mostly user defined (i.e. Unknown) except 0 which is 'Emergency'

FIXED: G/SSI Editor. The label "Seen SSI for GSSI (####)" was wrapping around on 4+ digit values.

CHANGED: Changes to the TETRA demodulator plug-in required a change to the Network Info PDU panel detection.

CHANGED: Mode (Dual/Single) change has always required a TTT restart.
         This change now forces a call halt state and pop-up message to restart.
         This is to prevent unknown errors because of the changed conditions.

ADDED/FIX: This is to deal with the missing "D_Release" PDUs
           I do not know why this PDU is missing:
           - I don't think dropped burst cause this (I don't see dropped burst when PDU is expected)
           - A bug with some MS radios. (I think the BS would still send if MS dropped out)
           - A bug with BS. Maybe a bug when radios drop out?
           - A guess is the call moves off the current LA. I think PDUs exits which would indicate this. But I don't see them.

          Plug-in (v1.0.8) now outputs when the timeslot becomes unallocated, This is to help deal with when "D_Release" is not seen.
          Normally "D_Release" will be seen before the unallocated timeslot occurs so the call with end as expected.
          TTT looks for this unallocated timeslot output during a call and if it see's it, will end the call rather than go into the
           usual timeout state. (which it will still do if both "D_Release" and unallocated timeslot detection are not seen.)
          This fix may prevent missing the following calls after a missing "D_Release" (GSSI related or not).

          I have seen when "D_Release" is not seen (and when unallocated timeslot detection is seen), calls seem to abruptly end.
          No further transmissions are usually seen and a call release does not occur. This for some reason results in the call just aborting.

          To disable this feature use '-du' on the commandline (shortcut). See v0.99.8 in changelog for creating shortcut.

FIXED: G/SSI Editor: The G/SSI label fields where only allowing ACSII characters up to 0x7F, this was preventing country specific characters.

CHANGED: The TTT call state/priority sounds presence is now scanned for about every second. No TTT restart is required when adding and removing the WAVs.

FIXED: Compact mode was not saving last state

CHANGED: Added MNC,LA labels to exiting MCC label in menu bar.
         Also added labels to entry in event log panel (when carrier changed on CC) if they exist.
         Will show # if no label exists.
         Will only show # when in compact mode. MNC/LA label will still be shown as a tooltip when mouse hover over "MNC:x  LA:x"
          in either mode.
         This menu bar is limited to a combined MCC/MNC/LA size of 65 characters. Anything over will be truncated.
         If you use an altered font sizes for windows and the labels overflow the menu bar area, Window corruption may result for TTT.
See 'changelog.txt' for more details.

Has been tested on Windows 7 - Basic (64 bit)
Has been tested on Windows 7 - Professional SP1 (32 bit), English
Has been tested on Windows 10 - Professional (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

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. (2019-January-10).
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.

[size=+2]Download link[/size]

MD5 HASH ba116affce865dee426efa760f65c813



Hopefully not to many bugs, after all these changes.:unsure:
I can’t seem to get this link established.... file does not exist...?
 

hermite

Member
Premium Subscriber
Joined
Nov 24, 2010
Messages
42
Location
Montreal Quebec
Hello, I'm new to TETRA and TTT. I just setup my Plugins in SDRSharp. I have decent signal on CC, but I'm not observing any calls. Any clue what I'm doing wrong? Tks.

SYSINFO - Main_carrier:2402 Offset:3 Frequency_Band:8
SYSINFO - Main_carrier:2402 Offset:3 Frequency_Band:8
TS4_unallocated 6
TS3_unallocated 5
SYSINFO - Main_carrier:2402 Offset:3 Frequency_Band:8
SYSINFO - Main_carrier:2402 Offset:3 Frequency_Band:8
TS4_unallocated 6
TS3_unallocated 5
SYSINFO - Main_carrier:2402 Offset:3 Frequency_Band:8
SYSINFO - Main_carrier:2402 Offset:3 Frequency_Band:8
TS4_unallocated 6
TS3_unallocated 5
SYSINFO - Main_carrier:2402 Offset:3 Frequency_Band:8
SYSINFO - Main_carrier:2402 Offset:3 Frequency_Band:8
TS4_unallocated 6
TS3_unallocated 5
SYSINFO - Main_carrier:2402 Offset:3 Frequency_Band:8
SYSINFO - Main_carrier:2402 Offset:3 Frequency_Band:8
TS4_unallocated 6
TS3_unallocated 5
SYSINFO - Main_carrier:2402 Offset:3 Frequency_Band:8
SYSINFO - Main_carrier:2402 Offset:3 Frequency_Band:8
TS4_unallocated 6
TS3_unallocated 5
SYSINFO - Main_carrier:2402 Offset:3 Frequency_Band:8
SYSINFO - Main_carrier:2402 Offset:3 Frequency_Band:8
TS4_unallocated 6
TS3_unallocated 5
SYSINFO - Main_carrier:2402 Offset:3 Frequency_Band:8
SYSINFO - Main_carrier:2402 Offset:3 Frequency_Band:8
TS4_unallocated 6
TS3_unallocated 5
SYSINFO - Main_carrier:2402 Offset:3 Frequency_Band:8
SYSINFO - Main_carrier:2402 Offset:3 Frequency_Band:8
TS4_unallocated 6
TS3_unallocated 5
SYSINFO - Main_carrier:2402 Offset:3 Frequency_Band:8


1554854523483.png

1554855310547.png
 

Attachments

  • TETRA_TTT.jpg
    TETRA_TTT.jpg
    82.1 KB · Views: 45
Last edited:

thewraith2008

Member
Joined
Nov 22, 2016
Messages
1,884
Hello, I'm new to TETRA and TTT. I just setup my Plugins in SDRSharp. I have decent signal on CC, but I'm not observing any calls. Any clue what I'm doing wrong? Tks.

Nothing stands out as been set-up wrong. It just looks like you don't have any call activity.

The lower part of 'Network Info' > 'Current cell' may shed some light. May be it's only a data network? Have you heard voice on it before?

EDIT:
Seeing 'TS4_unallocated 6' and 'TS3_unallocated 5' indicates that those slots are becoming assigned at some point. (Circuit mode or SNDCP data?)



Latest version (v1.0.14) can be found here: Release post
 

thewraith2008

Member
Joined
Nov 22, 2016
Messages
1,884
On the picture Notice Duplex spacing = 45 MHz.
Is Hamrite using Single mode or Dual mode?

The element 'Duplex spacing' is only related to the spacing used between uplink (MS to BS) and downlink (BS to MS) as has no bearing on decoding by the plug-in and the handling of the calls by TTT.

Hamrite is using TTT in 'Single' mode.
 

hermite

Member
Premium Subscriber
Joined
Nov 24, 2010
Messages
42
Location
Montreal Quebec
The element 'Duplex spacing' is only related to the spacing used between uplink (MS to BS) and downlink (BS to MS) as has no bearing on decoding by the plug-in and the handling of the calls by TTT.

Hamrite is using TTT in 'Single' mode.
Where can I deposit my recording of the Baseband file so you can detect my issue? Tks.
 

hermite

Member
Premium Subscriber
Joined
Nov 24, 2010
Messages
42
Location
Montreal Quebec
1554895816129.png
With the above image scenario, I hear the 'Bad Audio frame' beep as it scrolls down. If I Enable 'Fasle positives' the scrolling stops.

If I DISABLE DMO, the Burst is as follows:

1554896474849.png

More info from the current Cell...
1554896051980.png

This is the first TETRA System in my Area, perhaps it is still in testing/deployment mode?
 
Last edited:

thewraith2008

Member
Joined
Nov 22, 2016
Messages
1,884
The System Code (= 2) of your cell means that it is TMO (Trunking). DMO should not be enabled.
The second image looks OK with an exception of the assigned for the SYSINFO (sync bursts).

You can upload IQ sample to dropbox or similar then PM me with the link.

EDIT: Please record IQ sample with 'IF Recorder' plug-in and record in NFM mode (SDR#). This will allow a longer record time without an overly large file.
 

thewraith2008

Member
Joined
Nov 22, 2016
Messages
1,884
thewraith2008
TTT in Single mode RTL-SDR will jump in 45MHz?

No, TETRA uses frequency bands and TTT will jump anywhere within that frequency band.
(Actually TTT can jump anywhere in dongles frequency range [e.g. 24-1800MHz] if it had too.)

e.g.:
Frequency band = 800MHz
Frequency band range = 100MHz (800-899.9999MHz)



Latest version (v1.0.14) can be found here: Release post
 

Ubbe

Member
Joined
Sep 8, 2006
Messages
9,796
Location
Stockholm, Sweden
Your dongle is a bit off in frequency. Set the frequency to 860.0625 and go into the cog wheel settings of SDR# and adjust frequency correction ppm to minus values (probably -3) until the spectrum looks balanced again with equal plus and minus modulation from the center.

/Ubbe
 

hermite

Member
Premium Subscriber
Joined
Nov 24, 2010
Messages
42
Location
Montreal Quebec
The System Code (= 2) of your cell means that it is TMO (Trunking). DMO should not be enabled.
The second image looks OK with an exception of the assigned for the SYSINFO (sync bursts).

You can upload IQ sample to dropbox or similar then PM me with the link.

EDIT: Please record IQ sample with 'IF Recorder' plug-in and record in NFM mode (SDR#). This will allow a longer record time without an overly large file.
 
Top