SDR# TETRA Demodulator Trunk Tracking Demonstration

[yugps]

Is there a virus detected by WINRAR?

 

[thewraith2008]

Is there a virus detected by WINRAR?

No virus. A false positive.
I had someone say the other day the same about v1.0.15.
I don't know why all of a sudden that this is occurring.
Like most virus detection, useless names that can't be used to determined why.

If in doubt don't use. Your call.

 

[ET-NL]

Thanks for the update.
But the latest version (1.0.15.5) is still leaking audio. On the network I monitor there is a mix of encrypted and clear audio. I can hear the encrypted audio "leak" to my speakers if there is now clear voice communication. Sometimes, if there is encrypted and clear data at the same time (on different timeslots), you can hear the encrypted data with the clear data.
I'm using TTT in single mode.

And for the reccord, Windows 10 Defender was putting the two latest versions (1.0.15 and 1.0.15.5) in quarantaine.

ET

 

[thewraith2008]

Thanks for the update.
But the latest version (1.0.15.5) is still leaking audio. On the network I monitor there is a mix of encrypted and clear audio. I can hear the encrypted audio "leak" to my speakers if there is now clear voice communication. Sometimes, if there is encrypted and clear data at the same time (on different timeslots), you can hear the encrypted data with the clear data.
I'm using TTT in single mode.

And for the reccord, Windows 10 Defender was putting the two latest versions (1.0.15 and 1.0.15.5) in quarantaine.

ET

For TTT dual mode, You will get this audio bleed through if you don't park SDR# VC on an unused carrier (as per instructions)

For mixed speech calls, nothing can be done about bleed through of encrypted speech if the encrpyted speech traffic is controlled by encrypted PDUs. I have tried to add code that can try and guess, but I think it's it a bit average at best.

For mixed speech calls, if you see bleed through of encrypted speech where the E2EE (End 2 End Encrption) is set.
This probably should not be occuring. I should not be passing the encrypted audio.
If you have this last example then a IQ sample would be good to see as IQ samples I have are the encrypted PDU types.

As for "Windows 10 Defender" this seems to be a bit touchy about it's detection. There are posts on the net about the same name detected from years ago. As I said in my last post "I don't know why all of a sudden that this is occurring."



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

 

[ET-NL]

Also seen some readeble SDS messages, so thats working also over here

ET-NL

 

[point2point]

my DSDPlus.LRRP is not updated anymore, anyone with the same problem ?

 

[thewraith2008]

my DSDPlus.LRRP is not updated anymore, anyone with the same problem ?

Assuming you are still seeing the location PDUs.
Check to see if TTT options in "G" are OK.

• "Enable SDS - Location Data (GPS)" is enabled
• "LRRP (Public release)" is correct for the version of DSDPlus you use.
• Path to the working folder for DSDPlus.LRRP is correct.

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

 

[point2point]

Hi,

Yes correct see a lot of location PDU's , fast lane and public release does not show any location anymore.
I have been away for a while , but version 1.14 is doing fine.

 

[kikosgc]

Assuming you are still seeing the location PDUs.
Check to see if TTT options in "G" are OK.

• "Enable SDS - Location Data (GPS)" is enabled
• "LRRP (Public release)" is correct for the version of DSDPlus you use.
• Path to the working folder for DSDPlus.LRRP is correct.

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

For information, when i checked the box "Enable SDS - Location Data (GPS)", map plotting doesn't work (both in v1.0.15 and v1.0.15.5)

 

[thewraith2008]

my DSDPlus.LRRP is not updated anymore, anyone with the same problem ?

For information, when i checked the box "Enable SDS - Location Data (GPS)", map plotting doesn't work (both in v1.0.15 and v1.0.15.5)

OK, I had a look.
It seems when I moved some code around when I added the code for the SDS unknown Protocol ID, I inadvertently reversed the checkbox "Enable SDS - Location Data (GPS)" state.

If you turn OFF "Enable SDS - Location Data (GPS)" it should work.
I will upload the fix when I can, soon.



Latest version (v1.0.15.5) can be found here: Links for v1.0.15 and v1.0.15.5 removed.

 

[thewraith2008]

13th Public Release - TETRA Trunk Tracker and TETRA Demodulator plug-in - v1.0.15.6


This package (version) of TETRA Trunk Tracker and TETRA Demodulator plug-in (with codec libtetradec.dll) are only meant to be used
with each other and with no other previous versions. To do so will most likely cause issues.

No changes to TETRA Demodulator plug-in in this release.

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)


This TETRA Trunk Tracker version changes/adds and fixes some items:

v1.0.15.6 - Minor update

FIXED: The option "Enable SDS - Location Data (GPS)" checkbox was working in reverse.

FIXED: For SDS UDT-4 unknown protocol IDs - Removed the testing string which was appended to end "--TEST--"

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.

The TETRA plug-in is now been mainly tested with SDR# 1700 on Windows 7 Professional 32 bit with no issues seen.
The TETRA plug-in with SDR# 1700 on Windows 7-10 64 bit PCs is untested by me and is known.

It only works with the provided TETRA plug-in supplied in zip. (2019-April-15).
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.

Please look at the "changelog.txt" for both plug-in and TTT as these maybe contain instructions/explanations for features that may not be covered in the PDF documentation.

Thanks to point2point and kikosgc for the feedback.

Checked "tetra_trunk_tracker.exe" with Windows Defender (Windows 7, 32 bit) and Comodo AV and result was clean.

Download

MD5 HASH fff102e7864824799374dfaed593a7e1

 

[ET-NL]

Thanks for the update.
I have a (small) feature request. Is there a way we can get something like TETRA_mnc so the mcc/mnc combination of a network can be named.
There are a lot of different networks over here that I can receive, a name would be helpfull. Only a textfile without a fancy editor would be fine by me.

ET-NL

 

[thewraith2008]

Thanks for the update.
I have a (small) feature request. Is there a way we can get something like TETRA_mnc so the mcc/mnc combination of a network can be named.
There are a lot of different networks over here that I can receive, a name would be helpfull. Only a textfile without a fancy editor would be fine by me.

ET-NL

Can you elaborate.
With TETRA_mnc.txt, MCC and MNC values are used together to label a MNC.
With TETRA_la.txt, MCC and MNC and LA values are used together to label a LA.



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

 

[hamradionl]

Can you elaborate.
With TETRA_mnc.txt, MCC and MNC values are used together to label a MNC.
With TETRA_la.txt, MCC and MNC and LA values are used together to label a LA.

Not interesting in the country
example simple config file like same way you used the TETRA_status_codes.txt
MCC;MNC;La:Courier service (or any other txt)
MCC;MNC;La:Bus service
MCC;MNC;La:Taxi

 

[thewraith2008]

Not interesting in the country
example simple config file like same way you used the TETRA_status_codes.txt
MCC;MNC;La:Courier service (or any other txt)
MCC;MNC;La:Bus service
MCC;MNC;La:Taxi

But that is not how LA's are used.
Here and in other network examples I've seen, a LA is a position on a map. LA's are arranged to maximize coverage for an area (say a large city). For me, hundreds of GSSI's can use any of these LA's anywhere in the network (MNC). To label it 'Taxi' would be incorrect. "City central" or "City north" would be more accurate.

MCC / MNC / LA / GSSI / ISSI
UK / BritishTETRA / London Central / London Taxis Company / Driver 456

 

[hamradionl]

To label it 'Taxi' would be incorrect. "City central" or "City north" would be more accurate.

ET-NL he give just a suggestion and understand why he is asking for name label
But if not possible, its oke

 

[thewraith2008]

ET-NL he give just a suggestion and understand why he is asking for name label
But if not possible, its oke

TTT gives the ability to label MCC / MNC / LA individually to whatever you want.

ET-NL issue is relate to network providers using the same (MCC) MNC values in some cases. e.g.:
(MCC) 123 - (MNC) 456 = Network provider company A
(MCC) 123 - (MNC) 456 = Network provider company B

In TTT, you can not define two different labels for same MCC/MNC values.

When network providers don't use a central authority to registry MNC values, this is the pain they put us through. They have no consideration.

EDIT: Currently this would be too much effort to correct.
i.e. Add frequency to TETRA_mnc.txt and make other changes to recognize this.

e.g.:
123;456;410000000;Company A
123;456;415000000;Company B

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

 

[hamradionl]

EDIT: Currently this would be too much effort to correct.
i.e. Add frequency to TETRA_mnc.txt and make other changes to recognize this.

No problem, understand

 

[R3Natas]

Same issue as before, I only see network info, but calls are not going to TTT

 

[hamradionl]

TetraDecoder without TTT running, you hear voice?
See calls in TetraDecoder Network Window?

Your Tetra signal SNR ?
SDR# AudioFilter OFF?