SDR# TETRA Demodulator Trunk Tracking Demonstration

pingirona

Member
Joined
Aug 10, 2009
Messages
25
Location
Europe
Hello
using TTT 1.11 (hotfix 6) in SINGLE mode I get this error. Sometimes after 2 hours, sometimes after 12h. Is there any solution?

Ya se agregó un elemento con la misma clave. (An item with the same key has already been added.)
at mscorlib.dll.ThrowHelper.ThrowArgumentException (IL offset: 0x10)
at mscorlib.dll.Dictionary`2.Insert (IL offset: 0x81)
at SDRSharp.Tetra.dll.MM_protocol.ParseMMPDU (IL offset: 0x219)
at SDRSharp.Tetra.dll.MLE_protocol.ParseMLEPDU (IL offset: 0x62)
at SDRSharp.Tetra.dll.SduParser.Parse (IL offset: 0x58)
at SDRSharp.Tetra.dll.PduParser.MacEndPDU (IL offset: 0x96)
at SDRSharp.Tetra.dll.PduParser.ParsePDU (IL offset: 0xca)
at SDRSharp.Tetra.dll.TetraDecoder.Process (IL offset: 0x195f)
at SDRSharp.Tetra.dll.TetraPanel.DecodingThread (IL offset: 0x98)
at mscorlib.dll.ThreadHelper.ThreadStart_Context (IL offset: 0x14)
at mscorlib.dll.ExecutionContext.RunInternal (IL offset: 0x79)
at mscorlib.dll.ExecutionContext.Run (IL offset: 0x0)
at mscorlib.dll.ExecutionContext.Run (IL offset: 0x2b)
at mscorlib.dll.ThreadHelper.ThreadStart (IL offset: 0x8)
 

hamradionl

Member
Joined
Mar 23, 2014
Messages
730
pingirona
Thank you for information, i also have crash but my first txt line is different from yours.
To find out why the SDR# crashing on my standard PC and to get all clear, buy new PC. But the new PC the SDR# also crash. So its 100% clear its not hardware but software related.

.
 

pingirona

Member
Joined
Aug 10, 2009
Messages
25
Location
Europe
pingirona
Thank you for information, i also have crash but my first txt line is different from yours.
To find out why the SDR# crashing on my standard PC and to get all clear, buy new PC. But the new PC the SDR# also crash. So its 100% clear its not hardware but software related.

.
thanks for your answer
I've been trying everything, in windows 10, in windows 7, with SDR to 1024, to 2018, to 0.25mbps, blocking direct calls, etc ... nothing has worked for me. Now I'm trying to disable automatic frequency control .... The only thing that worked for me was a downgrade to TTT 1.07. A pity, because the 1.07 does not have automatic frequency control and that makes many modulations are received with words cut, because the control channel operates theoretically at 391.737.500 and the automatic setting led to 737.612 for example, where the audio was perfect. Regards!
 

hamradionl

Member
Joined
Mar 23, 2014
Messages
730
pingirona
Exactly same, it look like its this file cause crash SDRSharp.Tetra.dll
I downgrade to version TTT_1.09.0_hotfix_3 + TTT - 1.0.12 thats for me the version working.
 

Ubbe

Member
Joined
Sep 8, 2006
Messages
9,796
Location
Stockholm, Sweden
That's only a 120Hz error. The correction of the SDR receiver goes in 1ppm steps which is 400Hz. You must have some serious configuration problem if you can not decode a tetra signal 100% even if you are 1000Hz in error. If you look in the tetra folder in the left menu in SDR# under receive, does it say 100% quality and the frame numbers are ticking at a crazy speed? If you have less than 100% then TTT can not function and you need to fix your hardware or software to get that 100% value.

With the RTL-SDR and a weak signal I can go 1200Hz off the correct frequency before the procentage starts to drop. The RTL-SDR also has a temperature stability oscillator and are kept on the exact frequency from it starts cold until it is so hot you can barely touch it.

/Ubbe
 

Erik211

Member
Joined
Feb 3, 2019
Messages
27
Location
Stockholm, Sweden
I still experience occasional crashes, running the lastest hotfix. I'm a real noob in programming, so I actually don't know how to debug the software. I believe there's a piece of Microsoft software for programming, is that the one to use? Or some other debugging tool?
I'm happy to share debugging reports, if someone could be so kind and explain how it's done. :oops:

Edit: I'm running Windows 10 Pro, 64 bits (Swedish)
 

hamradionl

Member
Joined
Mar 23, 2014
Messages
730
Erik211
crash.txt is to be found in the folder from SDR# program
Win10 there is a function : event log
 

pingirona

Member
Joined
Aug 10, 2009
Messages
25
Location
Europe
Hello everyone and thanks for your answers. In my case I solved it by deactivating AFC in the Tetra demodulator module. Now it has been running for 18h straight without crash with TTT 1.11 hotfix6. regards.
 

Erik211

Member
Joined
Feb 3, 2019
Messages
27
Location
Stockholm, Sweden
Thanks and tack så mycket :)

OK here is text from a crash this morning. It had been running without problems for about 1 hour at that point the error says "the index was outside the boundaries of the matrix":

Indexet låg utanför gränserna för matrisen.
at SDRSharp.Tetra.dll.GlobalFunction.ParseParams (IL offset: 0x0)
at SDRSharp.Tetra.dll.SdsParser.ParseSDS (IL offset: 0x2f9)
at SDRSharp.Tetra.dll.CMCE_protocol.ParseCMCEPDU (IL offset: 0x192)
at SDRSharp.Tetra.dll.SduParser.Parse (IL offset: 0x49)
at SDRSharp.Tetra.dll.PduParser.MacEndPDU (IL offset: 0x96)
at SDRSharp.Tetra.dll.PduParser.ParsePDU (IL offset: 0xca)
at SDRSharp.Tetra.dll.TetraDecoder.Process (IL offset: 0x698)
at SDRSharp.Tetra.dll.TetraPanel.DecodingThread (IL offset: 0x98)
at mscorlib.dll.ThreadHelper.ThreadStart_Context (IL offset: 0x14)
at mscorlib.dll.ExecutionContext.RunInternal (IL offset: 0x79)
at mscorlib.dll.ExecutionContext.Run (IL offset: 0x0)
at mscorlib.dll.ExecutionContext.Run (IL offset: 0x2b)
at mscorlib.dll.ThreadHelper.ThreadStart (IL offset: 0x8)
 

living_death

Newbie
Joined
Feb 12, 2019
Messages
3
Location
Vantaa, Finland
TETRA Trunk Tracker v1.08.0 + hotfix_6_release_1.11.0

Here is crash.txt

Code:
Unable to load DLL 'libtetradec': The specified module could not be found. (Exception from HRESULT: 0x8007007E)
at SDRSharp.Tetra.dll.NativeMethods.tetra_decode_init  (IL offset: 0xffffffff)
at SDRSharp.Tetra.dll.TetraPanel.DecodingThread  (IL offset: 0x7)
at mscorlib.dll.ThreadHelper.ThreadStart_Context  (IL offset: 0x14)
at mscorlib.dll.ExecutionContext.RunInternal  (IL offset: 0x79)
at mscorlib.dll.ExecutionContext.Run  (IL offset: 0x0)
at mscorlib.dll.ExecutionContext.Run  (IL offset: 0x2b)
at mscorlib.dll.ThreadHelper.ThreadStart  (IL offset: 0x8)

Where can i download newer version of TTT?
 

hamradionl

Member
Joined
Mar 23, 2014
Messages
730
Erik211,
I write to Wraiht2008 several time that 1 hour, is the magic time line for crashes
I downgrade to version TTT_1.08.0_hotfix_3 + TTT_1.0.11 thats for me the version working for 18 hours and is still running this moment.
There are still some bugs in this version

living_death,
You have the latest public version try downgrade to hotfix_3
 

oz1jua

Member
Joined
Dec 15, 2014
Messages
127
Location
Copenhagen
@oz1jua

It does seem for the most part that the code for TMO SDS will work with DMO SDS.

However when I play these DMO SDS IQ samples you provided, the DM_SDS_UDATA PDUs is seen but the protocol identifier element (the part that determines if text message or GPS locations or other) is a reserved type (i.e unknown).

When I look at the buffer where the SDS is stored, nothing but zero's follow for the length of the message.

When you send a SDS message, does the receiving MS receive/display it?

I know the code used for TMO SDS is OK and I have rechecked the code for DMO SDS that proceeds it, and it seems OK.
Not sure what's been missed here.
I am sure that both radio has acepted and reply with receive acepted. And there schould be more than 1 SDS both way.
And the recording has it all. So what is missing I can't tell. And it was simple text in english.
 

thewraith2008

Member
Joined
Nov 22, 2016
Messages
1,884
I am sure that both radio has acepted and reply with receive acepted. And there schould be more than 1 SDS both way.
And the recording has it all. So what is missing I can't tell. And it was simple text in english.

Had a little time to investigate further. I will need to add the PDU de-fragmentation code to handle the SDS PDUs. That's why the buffer was blank after certain point. I will get to it a little later.

I'm testing TMO private full duplex calls at the moment.
 

DarkAngelT

Member
Joined
Sep 27, 2018
Messages
131
pingirona
Thank you for information, i also have crash but my first txt line is different from yours.
To find out why the SDR# crashing on my standard PC and to get all clear, buy new PC. But the new PC the SDR# also crash. So its 100% clear its not hardware but software related.

.

Weird...
I used it from yesterday to today for 16 hours in single mode and I used today for 12 hours in dual mode and it is working perfectly! That is ... Using the 28 hours! In my case here working without any problem!
 

hamradionl

Member
Joined
Mar 23, 2014
Messages
730
DarkAngelT
DUALmode i use 1.08 hotfix3_TTT_1.0.11 for 36++ hours but when upgrade the file SDRSharp.Tetra.dll to hotfix-6, than it totally go wrong on both PC
 

evilSparks

Member
Joined
Feb 8, 2019
Messages
11
Help Wanted
Please anyone who have a TTT running in both Single Mode or Dual Mode after some period, the SDR# screen seem Crash.
(some after short period running, some after several hours or longer)
When this Crash is happen on your system, Please be so helpfull report any SDR# crash to Wraith2008.
What file version you are using?
File size + File date
SDRSharp.Tetra.dll
libtetradec.dll
tetra_trunk_tracker.exe

.

SDR# has a tendency to freeze here. V1700 (iirc). Does not seem to be related to using TTT in conjunction. It freezes on its own.
 

thewraith2008

Member
Joined
Nov 22, 2016
Messages
1,884
@oz1jua

Added the code for the fragmented SDS PDUs. I had to tweak TSSDR's code a little as he had not completed it yet.

This is what I'm seeing now from your IQ samples: (This is the output of the plug-in)
from "22-01-18_428500kHz.wav"
Code:
 DMAC-DATA : ISSI:819 to ISSI:860 Type:UDT-4 Length:184 Protocol:Text_Messaging_TL MessageType:SDS-Transfer TextCodingScheme:Latin_1 TimeStampUsed:No TEXT:'Test from radio 819'  DM_SDS_UDATA

from "22-02-11_428500kHz.wav":
Code:
 DMAC-DATA : ISSI:819 to ISSI:860 Type:UDT-4 Length:184 Protocol:Text_Messaging_TL MessageType:SDS-Transfer TextCodingScheme:Latin_1 TimeStampUsed:No TEXT:'Test from radio 819'  DM_SDS_UDATA
 DMAC-DATA : ISSI:860 to ISSI:819 Type:Precoded Status Length:16 Data:32277  DM_SDS_UDATA (This is repeated quite a few times)
 
Top