SDR# TETRA Demodulator Trunk Tracking Demonstration

[Ubbe]

Hello,

Unfortunately the link to the download is no longer available. Is there still a way to get the latest version of the TTT?

Greetings from Germany

Use the link from NVE

/Ubbe

 

[FR33MAN]

Hello,

Unfortunately the link to the download is no longer available. Is there still a way to get the latest version of the TTT?

Greetings from Germany

File folder on MEGA

mega.nz

 

[adryd]

Is there source code available for TTT and the TETRA demodulator plugin? I'm trying to make a full-system decoder based on tetra-kit and trying to understand why I'm not getting D-RELEASE or D-TX CEASED PDUs when i expect and want to compare implementations.

Thanks.

 

[itundret]

Is there source code available for TTT and the TETRA demodulator plugin? I'm trying to make a full-system decoder based on tetra-kit and trying to understand why I'm not getting D-RELEASE or D-TX CEASED PDUs when i expect and want to compare implementations.

Thanks.

You can find a old source here: GitHub - vgpastor/SDR-Tetra-Plugin: Plugin to SDR# to interprete TETRA signals.

 

[konca]

Hello,I have the programs in the following versions.

-Tetra Trunk Tracker v.1.8.9.0
-Airspy SDR# Studio V.1.0.0.1920

My AirSpy Studio have the SDRSharp.Tetra.dll on your folder.

But TTT shows the following message "Is SDR# open for CC?".

The firewall has all ports open for both programs.

Anyone help me?

 

[dolman]

I know TTT is quite limited when it comes to call recording and probably doesn’t support what I’m aiming for, but maybe someone has an idea for a workaround using an extra bit of software? Ideally, I’d like to save each call as a separate file, named using the format: DDMMYYYY_HHMMSS_GSSI_SSI. I want to ingest them into Rdio Scanner.

 

[adryd]

I know TTT is quite limited when it comes to call recording and probably doesn’t support what I’m aiming for, but maybe someone has an idea for a workaround using an extra bit of software? Ideally, I’d like to save each call as a separate file, named using the format: DDMMYYYY_HHMMSS_GSSI_SSI. I want to ingest them into Rdio Scanner.

I have a fork of tetra-kit that does this GitHub - adryd325/tetra-kit-timeslots: OFF PLATFORM FORK OF https://gitlab.com/larryth/tetra-kit

you can edit the output format in recorder-js/call.ts getFilename()

 

[dolman]

It seems to be working well – everything that should be received is coming through. The only issue is that it’s combining individual calls into one long recording of the whole conversation. Is there a way to turn that off and save raw files as separate calls instead?

Unfortunately, I’m not too familiar with JS, so if it’s possible, would you mind sending me a modified version of `call.ts` in a private message – one that stops combining the calls and uses the filename format: DDMMYYYY_HHMMSS_GroupID_RadioID? Would really appreciate it!

 

[Center]

Because of an instable old laptop I've switched to a new Windows11 laptop with SDR#, Tetra Plug-in and TTT. Like on the old one. Everything is working fine again but if it comes to reording the calls an error occures: " #5: The specified parameter is out of range for the specified command" and TTT doesn't record audio. Without recording I've no issues. If I start recording in TTT this error comes up, in single mode and in dual mode. I use record method #2, Virtual Audio Cable, with all settings equal to the old machine as far as I've seen. Is this error known and, more important, where to look for a solution?

 

[Center]

I've fixed the issue with recording in TTT as mentioned earlier. I now use a really old version of VB Audio Cable. With that old version the error is gone and recording is fine now.

Can I use 2 instances of TTT on my PC, every instance with it's own Plug-in, if I change the portnumbers as stated in the documentation?