Happy it works for you.
TNM came after TTT+plug-in but I decided to focus on developing TTT before merging the changes to TNM.
TETRA in my region has mostly shutdown and traffic that exists is not frequent enough to bother with. This is one of the reasons why TNM as paused with any further development.
I can sent you raw audio of TETRA if you need for future development !Happy it works for you.
TNM came after TTT+plug-in but I decided to focus on developing TTT before merging the changes to TNM.
TETRA in my region has mostly shutdown and traffic that exists is not frequent enough to bother with. This is one of the reasons why TNM as paused with any further development.
Latest version (v1.7.1.0) can be found here: Release post
Thanks for the kind worksI think in that case we can all say a massive Thank You for the time effort blood sweat and tears you have put into this project! This is by far the best and most complete SDR tool out there and one that will be used for years into the future. Well done and thanks again.
Thanks.I can sent you raw audio of TETRA if you need for future development !
Hello thewraith2008. I would like to say thanks for your hard work/time and dedication/periodic updates/ easy to follow documentation.Happy it works for you.
TNM came after TTT+plug-in but I decided to focus on developing TTT before merging the changes to TNM.
TETRA in my region has mostly shutdown and traffic that exists is not frequent enough to bother with. This is one of the reasons why TNM as paused with any further development.
Latest version (v1.7.1.0) can be found here: Release post
First off, I'll also thank you for all the work you've done. If it's of any use, I may have seen an odd protocol in the wild: TEDS. Well, I think that's what it is, traffic chopper said something about sending live video over 4g and tetra at the same time. Again, thanks for making Tetra easy and accesible to windows users.Thanks for the kind works
Thanks.
All of the TETRA protocols (MAC,MLE,CMCE,SNDCP,MM) have been added now but some parts have been left out in some of them because they have never been seen in the wild. Not point wasting time on something that is not used.
If people start to see a particular service/feature then they would need to supply an IQ sample of it if they wish to see something added in the future. No guarantees though.
Latest version (v1.7.1.0) can be found here: Release post
There does exist "TETRA Multimedia Exchange (MEX) Layer".First off, I'll also thank you for all the work you've done. If it's of any use, I may have seen an odd protocol in the wild: TEDS. Well, I think that's what it is, traffic chopper said something about sending live video over 4g and tetra at the same time. Again, thanks for making Tetra easy and accesible to windows users.
Yeswhen using the DMO mode, should both demodulator and DMO boxes be ticked?
Sure it's DMO? It could be the uplink (MS to BS) which can look and sound like DMO.And second question, the DMO channels what i've heard is often in the lower end of the spectrum of the tetra channels and they are "burst like". Not a continous 25 kHZ like a normal base station channel? Did not find any good examples of how a DMO channel look like.
A little noob friendly tutorial "how to identify a DMO" channel would be great
Yeah I've tried it before but I only get the calls that are on the same carrier as the control channel. I'd like to chase the calls especially since the encrypted channels are usually the crowded ones.If you use the Tetra demod plugin with TTT not enabled you should hear the decoded but encrypted audio.
That is the whole purpose of the program, to follow calls to other carriers.Hello! is there a way that the program stops to change the frequency by itself? at a longer time this is a bit frustating but in the end i like it anyways. only that the software change the frequency by itself is not so nice.
TETRA encrypts all aspects of the data used for call control.Yeah I've tried it before but I only get the calls that are on the same carrier as the control channel. I'd like to chase the calls especially since the encrypted channels are usually the crowded ones.
TETRA encrypts all aspects of the data used for call control.
This means that TTT cannot follow encrypted calls to different carriers.
You would only be able to hear the encrypted voice on the carrier you are tuned too. (so long as the right options are selected)
No that is not possible with TTT.
TNM has that capability but it is not as developed as TTT.
Latest version (v1.7.1.0) can be found here: Release post