SDR# TETRA Demodulator Trunk Tracking Demonstration

[hamradionl]

TETRA_la.txt is working fine, GREAT jobe my friend, Very Great jobe !

555;30;10;420112500;Gotham
TTT TOP bar show LA: Gotham must this be LA: 10 User: Gotham
TETRA_la.txt in my case is very long and have many lines
For future TTT is possible or some place to make this function a separate window or menu in TTT?
Left or right side op the TTT window?

 

[thewraith2008]

TETRA_la.txt is working fine, GREAT jobe my friend, Very Great jobe !

555;30;10;420112500;Gotham
TTT TOP bar show LA: Gotham must this be LA: 10 User: Gotham
TETRA_la.txt in my case is very long and have many lines
For future TTT is possible or some place to make this function a separate window or menu in TTT?
Left or right side op the TTT window?

Not sure what your saying here.
LA = Location Area or a place somewhere. This is not a 'user'
"Gotham", as in Gotham City from Batman is a place like London is.
"Gotham" is a alias for LA: 10

The MNC and LA numerical values are still shown in the "Call details" panel.



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

 

[RMW1010]

A big thanks to thewraith2008
With the new version my issue has been resolved.

 

[hamradionl]

thewraith2008,
I use your batman example to point out what i notice TTT TOP bar
What i aspected to see:
MCC: countryName MNC: xxx LA: 10 User: name used in the file TETRA_la.txt

 

[thewraith2008]

thewraith2008,
I use your batman example to point out what i notice TTT TOP bar
What i aspected to see:
MCC: countryName MNC: xxx LA: 10 User: name used in the file TETRA_la.txt

What is expected to be seen on menubar at top of TTT is as follows:
MCC: x MNC: x LA: x

What is actually shown is dependent on if the record files exist:

• MCC will show label/alias if 'TETRA_mcc.txt' exists and the 'label' element is NOT empty. (MCC: Spain)
• MCC will show MCC # if 'TETRA_mcc.txt' NOT exists or the 'label' element is empty (when file exists). (LA: 214)

• MNC will show label/alias if 'TETRA_mnc.txt' exists and the 'label' element is NOT empty. (MNC: Network Provider Name)
• MNC will show MNC # if 'TETRA_mnc.txt' NOT exists or the 'label' element is empty (when file exists). (MNC: 3456)

• LA will show label/alias if 'TETRA_la.txt' exists and the 'label' element is NOT empty. (LA: A place in Spain)
• LA will show MCC # if 'TETRA_la.txt' NOT exists or the 'label' element is empty (when file exists). (LA: 789)

There is no "User: name" used in TETRA_la.txt, it is only location.

Example:

MCC: Spain MNC: TETRANET LA: Madrid or MCC: 214 MNC: 3456 LA: 1
MCC: Spain MNC: TETRANET LA: Teruel or MCC: 214 MNC: 3456 LA: 4



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

 

[tsapers]

Is it just my installation or did the Diagram(green dots) in SDR# change post the last update? Previously on my strongest CC signal (-10db) I would have those dots in a perfect line in the middle of each slot, where now it is much more random, but still "relatively" grouped.

 

[hamradionl]

thewraith2008
Big thank you, for your effort and clear explanation

 

[thewraith2008]

Is it just my installation or did the Diagram(green dots) in SDR# change post the last update? Previously on my strongest CC signal (-10db) I would have those dots in a perfect line in the middle of each slot, where now it is much more random, but still "relatively" grouped.

I changed TTT to start SDR# in NFM with a bandwidth of 25000Hz.
Try setting SDR# to WFM, this should make it tighten up again.

I started adding the code improvements to the demodulator code for the plug-in that TSSDR made available to me.
I am testing slowly as I get time. This change is on a development version of the plug-in not the current release version.
I shouldn't have release TTT with NFM just yet.



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

 

[tsapers]

I changed TTT to start SDR# in NFM with a bandwidth of 25000Hz.
Try setting SDR# to WFM, this should make it tighten up again.

Aha, Thanks for clarifying. I thought I was going mad Keep up the good work! Thanks

 

[R3Natas]

Hi, thewraith2008,

Installed your latest version, everything seems to be fine, except that I'm constantly experiencing crashed after about 5 minutes of use and in the crash log I see "Out of memory". Currently using Windows 10 Pro x64 with SDR# 1700 and TTT version 1.0.14

 

[hamradionl]

R3Natas,
After i installed both .NET 4.6 and 4.7 latest versions, seen only 1 time crash.
( not using google Chrome when use TTT maby help, slurping memory and cpu)

 

[hamradionl]

I'd find it hard to believe that with only "Length:32" (that's 32 bits, assuming no other overhead) that it would be able to convey all that information.

alberts1987 binary string to text, assuming 8 bits per character and that converting to text is done anyway is:

€#/4
Œ
¹
€f9X
J
®
•?V

The "&#" could indicate HTML codes

€ euro sign (€)
Œ  latin capital letter OE (Œ)
¹  superscript one (¹)
€ euro sign (€)
  ?
®  registered trade mark sign (®)
&#8226  bullet (•)

€#/4Œ¹€f9X ? J®•

Does that mean anything to anyone?

I still be curious to let show what inside those RAW data packs and see to make any sens out of it

SSI:xxx D_SDS_Data Party_SSI:100 Type:UDT-4 Length:32 Protocol:User_Defined_192
SSI:xxx D_SDS_Data Party_SSI:100 Type:UDT-4 Length:72 Protocol:User_Defined_192
SSI:xxx D_SDS_Data Party_SSI:100 Type:UDT-4 Length:72 Protocol:User_Defined_192
SSI:xxx D_SDS_Data Party_SSI:100 Type:UDT-4 Length:72 Protocol:User_Defined_192
SSI:xxx D_SDS_Data Party_SSI:100 Type:UDT-4 Length:160 Protocol:User_Defined_192
SSI:xxx D_SDS_Data Party_SSI:100 Type:UDT-4 Length:176 Protocol:User_Defined_192
SSI:xxx D_SDS_Data Party_SSI:100 Type:UDT-4 Length:72 Protocol:User_Defined_192
SSI:xxx D_SDS_Data Party_SSI:100 Type:UDT-4 Length:176 Protocol:User_Defined_192
SSI:xxx D_SDS_Data Party_SSI:100 Type:UDT-4 Length:72 Protocol:User_Defined_192
SSI:xxx D_SDS_Data Party_SSI:100 Type:UDT-4 Length:160 Protocol:User_Defined_192
SSI:xxx D_SDS_Data Party_SSI:100 Type:UDT-4 Length:32 Protocol:User_Defined_192
SSI:xxx D_SDS_Data Party_SSI:100 Type:UDT-4 Length:32 Protocol:User_Defined_192
Found this info
https://github.com/itds-consulting/tetra-multiframe-sds-decoder

 

[digiman1]

Excellent Update, I am loving the LA Selector, this makes things a lot easier than having to use Frequency Manager in SDR#

I have a question though, is there any way for me to suppress the SYSINFO - Main_carrier:3758 Offset:3 Frequency_Band:3 messages, this is happening every second.

 

[digiman1]

I have a tetra question unrelated to TTT

Anybody know what this could be? (Image attached) right smack bang in the middle of a tetra band.

I thought it was just two Tetra signals beside each other but TTT does not detect this so I am thinking it is something else altogether. Any ideas?

 

[Ubbe]

SDR dongles shows a lot of false frequencies that are images from other frequencies. You can usually tell by that the exact frequency doesn't match into the bandplan. Untick the tetra Demodulation box and listen to the audio. Compare with a real tetra signal and other signals if you can match the audio type. Try reducing the RF gain 10dB and check that all signals also reduce abround 10dB and if some signal reduce more or dissapears then they are a result of overloading the SDR dongle with too much signal.

/Ubbe

 

[digiman1]

SDR dongles shows a lot of false frequencies that are images from other frequencies. You can usually tell by that the exact frequency doesn't match into the bandplan. Untick the tetra Demodulation box and listen to the audio. Compare with a real tetra signal and other signals if you can match the audio type. Try reducing the RF gain 10dB and check that all signals also reduce abround 10dB and if some signal reduce more or dissapears then they are a result of overloading the SDR dongle with too much signal.

/Ubbe

This is 100% a real signal, if I drop the db it drops but keeps in line with the rest of the peaks, I also compared the sounds and it sounds like tetra also, it would be hard to tell the difference when listening to it. This also gets picked up on my scanner quite strong too so I am 100% sure this is a real signal rather than an image.

 

[Ubbe]

When the signals are that close together it could be a problem for SDR# to single out one of them. As you think that it sounds like Tetra then that could be the problem that it cannot be decoded. I believe the frequency authorities normally reserve a whole frequency range for a big Tetra system to not let other users interfere.

TTT doesn't detect the signals, the tetra plugin in SDR# does, so look at the SDR# tetra plugin info and see if it decodes with 100% and displays all the info about country, system, color codes and frequencies. One thing that stands out are that the two carriers are so close together without any gap, like in your other frequencies and I also have the same gap. I still think that it indicates some kind of problem with your receive chain.

/Ubbe

 

[thewraith2008]

I have a question though, is there any way for me to suppress the SYSINFO - Main_carrier:3758 Offset:3 Frequency_Band:3 messages, this is happening every second.

No, TTT uses the SYSINFO to automatically set those values.
The SYSINFO as an interval of 2 seconds. I can probably increase, but I can't make to long as it will also delay the start of the first call.
I have a fairly active network and the SYSINFO entries are interleaved with all the other PDUs been displayed.

I have a tetra question unrelated to TTT

Anybody know what this could be? (Image attached) right smack bang in the middle of a tetra band.

I thought it was just two Tetra signals beside each other but TTT does not detect this so I am thinking it is something else altogether. Any ideas?

This looks like a 50Khz signal (possibly TETRA) The standards mention this. (25,50,100KHz). Of course the plug-in does not support.



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

 

[hamradionl]

Future when this more common, will TT and TTT support these new standard?

 

[thewraith2008]

Future when this more common, will TT and TTT support these new standard?

The access scheme is TDMA with 4 physical channels per carrier. For phase modulation the carrier bandwidth is
25 kHz. For QAM the carrier bandwidth is 25 kHz, 50 kHz, 100 kHz or 150 kHz.

Plug-in only decodes phase modulation. QAM is not and most likely won't be, because it would need a completely new everything.



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