SDR# TETRA Demodulator Trunk Tracking Demonstration

[digiman1]

Awesome

@thewraith2008 Awesome update! Thank you!

 

[DarkAngelT]

Thanks for taking my suggestion! For having inserted colors in the remote window and for the possibility of personalizing sounds in the communications!

I only realize that the communication status in the tetra demudolator, the remote window, and the TTT log are slow in relation to the audio response.

I would like an information if possible.

What is the difference between libtetradec and libtetradec that is inside the altDLL folder?

 

[thewraith2008]

What is the difference between libtetradec and libtetradec that is inside the altDLL folder?

The 'libtetradec.dll' is the TETRA Speech codec.
'libtetradec' source code was taken directly from the TETRA standard "EN 300395" and made available in curlyboi's Github.

The two 'libtetradec.dll' supplied in my package are as they where originally supplied by TSSDR at different release points.

I don't know what is different between each one (if any) in my package and if they differ from the curlyboi's source code.

For me, the altDLL 'libtetradec.dll' was the only one that worked on my Windows 7 Pro 32bit PC. Now both work. Don't know why.

 

[DarkAngelT]

When it appears the Release happens due to the timeout (when the message: Call timeout occurred - Did not see D-Release)
Bip is not triggered. How can I make this Release to have a BIP sound too?

 

[DarkAngelT]

Is there a way to decode D_STATUS?

I realize that this information appears to me a lot.

 

[thewraith2008]

When it appears the Release happens due to the timeout (when the message: Call timeout occurred - Did not see D-Release)
Bip is not triggered. How can I make this Release to have a BIP sound too?

This is a bug. Will be fixed in next release.

Is there a way to decode D_STATUS?

I realize that this information appears to me a lot.

Yes, but there is not much in the way of interesting information there.
There is a 16 bit field call "Pre-coded status", this is a value between 0-65535 and is broken down as follows.
___________0 - Emergency
____1 to 31743 - Reserved
31744 to 32767 - Refer to SDS-TL
32768 to 65535 - Available for TETRA network and user specific definitions

Each value is not defined in the standard and is most likely defined by equipment manufacturers.

 

[DarkAngelT]

This is a bug. Will be fixed in next release.



Yes, but there is not much in the way of interesting information there.
There is a 16 bit field call "Pre-coded status", this is a value between 0-65535 and is broken down as follows.
___________0 - Emergency
____1 to 31743 - Reserved
31744 to 32767 - Refer to SDS-TL
32768 to 65535 - Available for TETRA network and user specific definitions

Each value is not defined in the standard and is most likely defined by equipment manufacturers.

Got it.
I do not know if you know ... The priority wav tone is not working properly. No more congratulations and thanks for the updates!

 

[DarkAngelT]

I was able to resolve the bug provisionally by increasing the release time on TTT from 5 seconds to 7 seconds! With that the beeps started to be fired.

 

[thewraith2008]

I do not know if you know ... The priority wav tone is not working properly.

The priority sound is assigned a number and when the priority is triggered, as long as the set GSSI priority value is equal or higher in value then sound is heard.

e.g.
The supplied file name is "snd_priority5.wav". This means that if a GSSI that triggers the priority is equal to 5 or higher then you will hear the sound. If the priority value for the GSSI is lower, then no sound is heard.

If you wish to hear sound on all priorities when they are triggered, then make filename "snd_priority1.wav". A restart of TTT is required if it is running.

 

[DarkAngelT]

The priority sound is assigned a number and when the priority is triggered, as long as the set GSSI priority value is equal or higher in value then sound is heard.

e.g.
The supplied file name is "snd_priority5.wav". This means that if a GSSI that triggers the priority is equal to 5 or higher then you will hear the sound. If the priority value for the GSSI is lower, then no sound is heard.

If you wish to hear sound on all priorities when they are triggered, then make filename "snd_priority1.wav". A restart of TTT is required if it is running.

I understand, but if the snd_call_setup sound is enabled, the priority sound does not come in. Only if I disable snd_call_setup.

It would be nice if the given priority was played instead of the snd_call_setup and if only the given priority was played without touching the priorities above it.

 

[DarkAngelT]

Dear thewraith200, I must inform you that the TTT update was very good. However the update of SDRSharp.Tetra.dll has some error that leaves the communications mute.

I was able to receive better communications using the version 1.05.0 file along with TTT and SDRSharp.NetRemote updated in version 1.07.0

Now, I do not know if it would be a sum of factors, because using the file from the previous version improved, but did not fully fix the failure. Could not it be some bug in version 1.07.0?

 

[thewraith2008]

I understand, but if the snd_call_setup sound is enabled, the priority sound does not come in. Only if I disable snd_call_setup.

It would be nice if the given priority was played instead of the snd_call_setup and if only the given priority was played without touching the priorities above it.

This probably occurs because priority and setup sound play at almost the same time. I hear both on my end but in any case the next release will only play priority sound when triggered and not the setup sound.

Dear thewraith200, I must inform you that the TTT update was very good. However the update of SDRSharp.Tetra.dll has some error that leaves the communications mute.

I was able to receive better communications using the version 1.05.0 file along with TTT and SDRSharp.NetRemote updated in version 1.07.0

Now, I do not know if it would be a sum of factors, because using the file from the previous version improved, but did not fully fix the failure. Could not it be some bug in version 1.07.0?

I don't see this problem on my setup. Not sure what could be wrong other than something in the setup/options for both plug-in and/or TTT that is not right.

Changes that where made to the plug-in where not that major and would not have impact on audio muting.

 

[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.

Found this document for DMO.
https://www.etsi.org/deliver/etsi_etr/300_399/30003/01_60/etr_30003e01p.pdf

 

[thewraith2008]

Found this document for DMO.
https://www.etsi.org/deliver/etsi_etr/300_399/30003/01_60/etr_30003e01p.pdf

Yes, already have relevant documents.
I looked at them and TMO and DMO are quite different in structure and don't really share to much in common.

I can detect the different bursts (normal/sync) for DMO and extract the data, but that's where it stops. The higher protocols would require major code implementation to make it work. For me it it would be a case of diminishing returns.

If I had a radio with DMO for testing or received DMO signals at all, I maybe motivated to do something.

 

[Kenzi]

Hello i see in the TETRA demodulator in sdrsharp following MCC, MNC, LA, COLOR, MAIN, CURRENT each of them has appropriate numbers. My question is what does indicate the red text "Received" below the text is see low numbers like 0-9 and they are constantly changing. Does the low number 0, 1 up to 9 mean that the signal is too weak to intercept or it is not locking the tetra signal correctly?

 

[thewraith2008]

Hello i see in the TETRA demodulator in sdrsharp following MCC, MNC, LA, COLOR, MAIN, CURRENT each of them has appropriate numbers. My question is what does indicate the red text "Received" below the text is see low numbers like 0-9 and they are constantly changing. Does the low number 0, 1 up to 9 mean that the signal is too weak to intercept or it is not locking the tetra signal correctly?

This value is related to the amount of information in the rawdata buffer. The alternating values are normal.
It is only indicating that decoding is occurring and filling the buffer and other code is emptying the buffer. Not really that useful.
It is not an indicator of signal strength or quality. You can use the tuning display for that.

If the "Received" is a solid red then you should see good decodes.
If flickering red then there maybe be problems in decoding.

 

[RicardoRJ]

Congratulations on the beautiful work.
Here in Brazil the TTT plugin works very well, but I've been noticing that sometimes it just does not work. The network here does not use encryption.
I have some Teltronics MDT-400 and Motorola MTM5400 radios, and I notice that during a plugin listening it is working very well when it does not change at all. It stops working but on the radios I normally hear the audio. soon after the next change the plugin works again! I do not know if it is a plugin problem but this has been happening frequently! Can you say something about it?
Sorry for English, I'm using google to translate!

Thank you

 

[Kenzi]

Thank you thewraith2008 very well explained !
Ive got another question my setup is 1x sdrsharp and 1x airspy r2, operation system windows 10 x64. So whenever I click/enter the correct tetra frequency in sdrsharp, then after like 5 seconds the trunk traker will jump off little bit of the tetra frequency (trunk tracker will jump off little bit but enought not to get the signal) so i have to re-click/enter the correct frequency in sdrsharp. I have read the manual as I understand it should be auto corrected in version 1.07. I have also tryed out pre offset values in trunk tracker, non will help. Why does the trunk tacker jumps off little bit ? Is it a bug or something else?

 

[thewraith2008]

Congratulations on the beautiful work.
Here in Brazil the TTT plugin works very well, but I've been noticing that sometimes it just does not work. The network here does not use encryption.
I have some Teltronics MDT-400 and Motorola MTM5400 radios, and I notice that during a plugin listening it is working very well when it does not change at all. It stops working but on the radios I normally hear the audio. soon after the next change the plugin works again! I do not know if it is a plugin problem but this has been happening frequently! Can you say something about it?
Sorry for English, I'm using google to translate!

Thank you

What setup you using, Dual/Single?
What options do you use?

Is this happening after a call has been recorded? The option in 'R' > 'Hold Delay' can cause this missing other calls, as it waits to see if current GSSI resumes talking.

I notice that during a plugin listening it is working very well when it does not change at all. It stops working but on the radios I normally hear the audio

Is this for same GSSI or 2 different GSSIs? Do you have any lockouts set?
See G/SSI editor for GSSI that are unchecked.

Does your network use more than 1 frequency?

If none of the above helps you may need to send me a IQ sample of this occurring.

 

[thewraith2008]

Thank you thewraith2008 very well explained !
Ive got another question my setup is 1x sdrsharp and 1x airspy r2, operation system windows 10 x64. So whenever I click/enter the correct tetra frequency in sdrsharp, then after like 5 seconds the trunk traker will jump off little bit of the tetra frequency (trunk tracker will jump off little bit but enought not to get the signal) so i have to re-click/enter the correct frequency in sdrsharp. I have read the manual as I understand it should be auto corrected in version 1.07. I have also tryed out pre offset values in trunk tracker, non will help. Why does the trunk tacker jumps off little bit ? Is it a bug or something else?

This could be a bug, not sure. I would need an IQ sample of your CC frequency (Main_carrier)

...then after like 5 seconds the trunk traker will jump off little bit of the tetra frequency

How much is a "little bit" off frequency.
Is it +/- 0.00625 MHz off or 0.0125 MHz off or something else.

In the meantime you can disable the auto set Base frequency/Main carrier (CC) and Offset by using the command line option. ( -dm )
For more information see "TTT_Features_and_Usage.pdf' > "Command line options"