SDR# TETRA Demodulator Trunk Tracking Demonstration

[point2point]

Software request

Hi thewraith2008,

Thank you for creating this great program.
If you need access to a busy spyserver send me PM.

I also would like to ask you if you are going to plan to make an update can you add the feature that we can set the remote port(s) ?
If i run multiple instances on a server ports are in use, and i can't change them.
So even when you have big streaming machine a dual setup is the maximum.

Thanks !

P2P

 

[thewraith2008]

TETRA Trunk Tracker and SDR# need to be on same PC to work.
Some of what TTT does is scrape data directly from the plug-in windows and not via the 'Net Remote' port.
The 'Net Remote' is only to allow TTT to control SDR# (not the plug-in) and detect some control states in SDR#.

I was looking at multiple instances of TTT, but this is a bit of work to do because I need to manage SDR# instances and deal with shared record files.
Recording would also be affected.
And listening to 2 or more instances was chaotic.
Linking instances to manage calls across LAs would just be a nightmare (for me).

 

[point2point]

My problem is a bit different, i am on the same pc because i run windows 2012 server.
So if i create a specific useraccount and run TTT there, all directories are seperated.
On another user account i run TTT and again everything is seperated, but the sockets are in use. If i could set the port TTT wants to connect SDRsharp with on the localhost i would not have that problem and i can run multiple TTT's one one machine.
If you every planning to make a new release , can you take in consideration to set the recording/cvs directory somewhere else then inside TTT ?
Thanks,

PTP

 

[thewraith2008]

My problem is a bit different, i am on the same pc because i run windows 2012 server.
So if i create a specific useraccount and run TTT there, all directories are seperated.
On another user account i run TTT and again everything is seperated, but the sockets are in use. If i could set the port TTT wants to connect SDRsharp with on the localhost i would not have that problem and i can run multiple TTT's one one machine.
If you every planning to make a new release , can you take in consideration to set the recording/cvs directory somewhere else then inside TTT ?
Thanks,

PTP

The ability to set port will be in next release as it was mostly set up anyway. This will be set via command line.
In dual mode this value would set CC SDR# port # and VC SDR# port # will be CC SDR# port # + 1.

My original intention was to set ports automatically with a TTT instance management scheme. But as mentioned in previous post, this was going to add a level of complexity that I don't really want to deal with at the moment.

I have no plans to change log file and recordings location. I prefer to keep it all in one place.

As it stands, running multiple instances of TTT from same folder (this shouldn't work anyway) is not advised as TTT loads records into memory for each instance and saves periodically (and on exit). This would cause the problem of each instance would overwrite the others version of the record files.

The plan was to load records into shared memory to allow multiple instances of TTT to work with the records. This of course will not work if using TTT in different sessions (users).

 

[tsapers]

Thanks thewraith2008! Looking forward to giving this a go vs telive I am currently running.

 

[oz1jua]

DMO Option

I think there will be a lot of interrest for looking into decode DMO trafic.
Have you any plan to implement this in you code ?

I can send some recorded IQ of this. If this is something to look at.

 

[thewraith2008]

I think there will be a lot of interrest for looking into decode DMO trafic.
Have you any plan to implement this in you code ?

I can send some recorded IQ of this. If this is something to look at.

No plans at this stage. Probably a little beyond me at the moment.
Also no DMO detected in range to test. Only TETRA on 800MHz here.
I'd have to be standing next to some one to hear them.

You can make your IQ sample available and I can look at it sometime in the future. But I can't promise anything.

 

[woodpecker]

I think there will be a lot of interrest for looking into decode DMO trafic.
Have you any plan to implement this in you code ?

I can send some recorded IQ of this. If this is something to look at.

Is there much DMO around, I've never come across a single DMO signal.

 

[oz1jua]

No plans at this stage. Probably a little beyond me at the moment.
Also no DMO detected in range to test. Only TETRA on 800MHz here.
I'd have to be standing next to some one to hear them.

You can make your IQ sample available and I can look at it sometime in the future. But I can't promise anything.

This is a I/Q file of a simpel DMO call from TG: 141448

https://wetransfer.com/downloads/f8...853430c586d61cc813f540e520181025202349/8eb6f9

Hope you can see the MCC:238 and MNC:5. and the used GSSI=141448 and ISSI=819.
It is done as simple with no present check.

Many thanks for the amazing program and hopefully you will look at this in the future. !!

 

[thewraith2008]

This is a I/Q file of a simpel DMO call from TG: 141448

https://wetransfer.com/downloads/f8...853430c586d61cc813f540e520181025202349/8eb6f9

Hope you can see the MCC:238 and MNC:5. and the used GSSI=141448 and ISSI=819.
It is done as simple with no present check.

Many thanks for the amazing program and hopefully you will look at this in the future. !!

Thanks for the sample. I have downloaded it.

Is this transmission a MS-MS DMO or through a Type 1/2 repeater?

I haven't looked at the standard to see if there is any differences as far as decoding goes, but if you know then it helps with a place to start reading in the documentation.

 

[oz1jua]

Thanks for the sample. I have downloaded it.

Is this transmission a MS-MS DMO or through a Type 1/2 repeater?

I haven't looked at the standard to see if there is any differences as far as decoding goes, but if you know then it helps with a place to start reading in the documentation.

This is MS-MS DMO not through a repeater. But I will also send you a sample of DMO through repeater.
I have my own DMO Tetra freq, and repeater.

 

[oz1jua]

I have now done a sample of a DMO repeater transmission. It has another GSSI but the same radio ID.819.
https://we.tl/t-4nSI6EnjfB

 

[oz1jua]

I have now done a sample of a DMO repeater transmission. It has another GSSI but the same radio ID.819.
https://we.tl/t-4nSI6EnjfB

I do not know if this explain the Tetra DMO Repeater. http://www.telfor.rs/telfor2004/TELFOR2004_tetra.pdf
But I am sure that my repeater is a Type 1A and not Type 2.
I will also send you a sample of sending some SDS on DMO when i have some time.

 

[tsapers]

I am looking at buying SDRPlay, but from what I can see this would not work as it is no longer compatible with SDR# which TTT uses. Anyone confirm this? So basically one could then only use the SDRPlay with the old TELIVE on linux.

 

[grahampaull]

Updates?

Hey, been running this 24/7 for a good few weeks now and it's been flawless!

Any eta on any new updates or features?

Thanks again for your hard work!

 

[tsapers]

Wow 1stly , hats off! Job well done thewraith2008! Thank you!
Working good on Win 7 Home Basic 64bit. Still need to figure out the the checkbox checker, but no biggy.

Now, how to get this running on something like a Raspberry Pi

 

[thewraith2008]

7th Public Release - TETRA Tunk Tracker v1.0.7

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.


TETRA Demodulator plug-in has been updated by me. "Tweaked Edition (Unofficial) v1.0.7.0"
It's is required for some SDS features to work with TETRA Trunk Tracker v1.0.7. Please read text files in zip for plug-in.

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

• ADDED: Alternative Call list generation in "Network Info" window calls tab.
• FIXED: When "Network Info" window was opened to "Calls" tab, CPU usage jumped 5-15%.
• See 'changelog.txt' more details.

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:

• CHANGED: Sort algorithm. TTT should load a lot faster with larger SSI/GSSI records.
• ADDED: Dropdown list of the past 8 GSSIs that can be used to set a GSSI Hold.
• ADDED: Manual entry of a GSSI for use in setting GSSI Hold.
• ADDED: Automatically set Main carrier, Offset and Base Frequency when TETRA signal selected. (Requires new plug-in tetra_x86_2018-11-11)
• ADDED: Some colors (7 preset, 1 custom) to use with the Group/User fields in the 'Remote' window. (When call active).
• ADDED: Custom set base SDR# Net Remote port via commandline.
• ADDED: System sounds. Triggered when: Call started, Call ends, SSI grants, SSI ceased, Priority
• - Supplied some sample sounds to test with (bit rough).
• ADDED: A visual counter for the record 'Hold Delay' when it is active.
• FIXED: When SDS location data PDUs are see in short intervals, the DSDPlus.LRRP file would have a file access error.
• 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 - ? (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. (2018-November-11).
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 f1ba3b61360771775196fbcf22ec8f37

 

[R3Natas]

Hello, tested your updated version works fine, no errors, but the first problem I came around is about recording the calls, it takes input from the laptops mic, not the program itself. Another discussion is about decoding, this plugin doesn't decode GPS positions and SDS statuses from my network, maybe I should send you some examples, so you could have a look?

 

[thewraith2008]

Hello, tested your updated version works fine, no errors, but the first problem I came around is about recording the calls, it takes input from the laptops mic, not the program itself.

TTT will record from whatever the default audio device is. You will need to follow the instructions as set out in "TTT_Set-up_manual.pdf" section "Configuring for Recording calls"

Another discussion is about decoding, this plugin doesn't decode GPS positions and SDS statuses from my network, maybe I should send you some examples, so you could have a look?

The plug-in should decode short and long SDS location data PDUs. This has been tested and verified by other users.
You may only be seeing the request for location data but not the response. A lot of people seem to have this problem.
Did you enable the "Enable SDS - Location data (GPS)" option in TTT?
Did you copy over the supplied TETRA Demodulator plug-in files to your SDR# folder? Only this version will do it.

Not sure what "SDS statuses" is as the SDS PDU carries many messages. I would need to see the log.
Send to PM. If post here blank out the SSIs.

If none of the above helps, you can send me a PM to the link to the IQ sample/s of the event occurring.
When creating IQ files, use something like "IF Recorder" and don't make the file to large.

 

[gustavobm]

Very nice update thewraith2008!

Already running on my two networks flawlessly, I liked the new features.

Thanks again for your work!