SDR# TETRA Demodulator Trunk Tracking Demonstration

hamradionl

Member
Joined
Mar 23, 2014
Messages
730
When SDR# + TTT in Dual Mode and ALL programs are running
CPU = InTel - i5 = jump between 42 - 50%
CPU SDR# 1 = jump between 11 - 14%
CPU SDR# 2 = jump between 11 - 14%
Ttrunker = 1%


1530 hours local GMT Europe i did full install and restart SDR# 1671+TTT 1.08 + hotfix - 3 + 5 + 6
1600 hours local All is still running

Later this day i will test again SDR# 1700
 
Last edited:

hamradionl

Member
Joined
Mar 23, 2014
Messages
730
I give up for today need do other thinks.
1530 hours local GMT Europe i did full install and restart SDR# 1671+TTT 1.08 + hotfix - 3 + 5 + 6
1642 hours local GMT and after 45 minutes running
VC = crasht
CC = alive

CPU = InTel - i5 = 30%
CPU SDR# 1 = jump between 10% - 13%
CPU SDR# 2 = crasht gone
Ttrunker = 0%

type System.OutOfMemoryException.
at mscorlib.dll.Dictionary`2.Resize (IL offset: 0x19)
at mscorlib.dll.Dictionary`2.Insert (IL offset: 0x10e)
at SDRSharp.Tetra.dll.GlobalFunction.ParseParams (IL offset: 0x8f)
at SDRSharp.Tetra.dll.PduParser.MacEndPDU (IL offset: 0x4)
at SDRSharp.Tetra.dll.PduParser.ParsePDU (IL offset: 0xca)
at SDRSharp.Tetra.dll.TetraDecoder.Process (IL offset: 0x2735)
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
22.30 hours local GMT Europe i did full install and restart SDR# 1700 +TTT 1.08 + hotfix - 3 + 5 + 6 DUAL mode
CPU = InTel - i5 = 52% All programms
CPU SDR# 1 = jump between 12% - 15%
CPU SDR# 2 = jump between 12% - 15%
Ttrunker = 0.5%

CPU = InTel - i5 = 54 % memory All programms
Memory use SDR# 1 = 40 Mb
Memory use SDR# 2 = 54 Mb
Ttrunker = 1.9 Mb
 
Last edited:

hamradionl

Member
Joined
Mar 23, 2014
Messages
730
2230 hours local GMT Europe i did full install and restart SDR# 1700 +TTT 1.08 + hotfix - 3 + 5 + 6 DUAL mode
2306 hours local GMT
VC = crasht
CC = alive

type System.OutOfMemoryException.
at mscorlib.dll.Dictionary`2.Resize (IL offset: 0x19)
at mscorlib.dll.Dictionary`2.Insert (IL offset: 0x10e)
at SDRSharp.Tetra.dll.SduParser.ParseLLC (IL offset: 0x13)
at SDRSharp.Tetra.dll.SduParser.Parse (IL offset: 0x0)
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: 0x2735)
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)


2320 hours local GMT Europe i did full install and restart SDR# 1700 +TTT 1.08 + hotfix - 3 + 5 + 6 DUAL mode

This all for today
 
Last edited:

gustavobm

Member
Joined
Aug 21, 2016
Messages
15
Running the last fix in single mode for several hours now. No glitches.

The ISSI/GSSI issue is gone.

Thanks!
 

hamradionl

Member
Joined
Mar 23, 2014
Messages
730
2320 hours local GMT Europe i did full install and restart SDR# 1700 +TTT 1.08 + hotfix - 3 + 5 + 6 DUAL mode
0040 hours local GMT
VC = crasht
CC = alive

More messages
SDR# TETRA Plugin Now Available At RTL-SDR.RU

type System.OutOfMemoryException.
at mscorlib.dll.Dictionary`2.Resize (IL offset: 0x0)
at mscorlib.dll.Dictionary`2.Insert (IL offset: 0x10e)
at SDRSharp.Tetra.dll.SduParser.ParseLLC (IL offset: 0x13)
at SDRSharp.Tetra.dll.SduParser.Parse (IL offset: 0x0)
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)


0040 hours local GMT Europe i did full install and restart SDR# 1700 +TTT 1.08 + hotfix - 3 + 5 + 6
This time use SINGLE mode

.
 
Last edited:

thewraith2008

Member
Joined
Nov 22, 2016
Messages
1,850
While I added it in the changelog in post for hot-fix 6 I'll mention it here again.

The issue with ISSI showing as GSSI also affected new entries into the 'TETRA_SSI.txt' and 'TETRA_GSSI.txt' record files.
It shouldn't be to hard to remove the dodgy entries manually (only while TTT is closed) if care is taken. Probably 5 minutes to do if that.


Also the current test with SDR# 1700(x2) + plug-in and TTT in dual mode is still going strong after 10hr 30min.
 

thewraith2008

Member
Joined
Nov 22, 2016
Messages
1,850
The TETRA Demodulator plug-in that I've used here with TTT is no longer the same as TSSDR version.
Under the hood there are things that improve different aspects of it's functionality.

The TSSDR version will not work with current version TTT.
It's probably not a good idea posting about a plug-in that will not work with TTT.

It will only serve to confuse people and that they may think the TSSDR version is OK to use with TTT. And it's not.
 

tsapers

Member
Joined
Aug 25, 2011
Messages
68
Also the current test with SDR# 1700(x2) + plug-in and TTT in dual mode is still going strong after 10hr 30min.

Do you have any recordings enabled in TTT? I suspect the error and SDR# crash on my side is related to a recording issue.
@hamradionl: Do you have any recording enabled in TTT?
 

hamradionl

Member
Joined
Mar 23, 2014
Messages
730
lynzoid
I run TTT from version 0.99 for days, never have this crash issue before
1 year old brandnew PC - CPU intell i5 - CPU load only 35% is stress ?
But like do test, advice for any stress test software?
Last week there is new WIN10 update.

TSapers
Thank you for this tip, no record ON
i try to find out by turn OFF / ON some functions typically crash seem after 45 minutes and only in DUAL mode
Funny part, DUAL mode 1e SDR# crashing the 2e SDR# after crash keep running the whole day
SINGLE mode keep running
Also search if a mouse click in the VC screen maby cause crash ( when a active call is running )
Also search while running and i go to some screen, resize or move or Click inside Trunk screen.
Also search its something with record Priority or setting
Also turn OFF sounds
 
Last edited:

hamradionl

Member
Joined
Mar 23, 2014
Messages
730
thewraith2008
DUAL mode could be possible when both SDR# want USB communication, 1e one get stuck en crash?
I try reinstall ZADIG, is not possible because USB driver is still active after crash

type System.OutOfMemoryException.
at SDRSharp.Radio.dll.ComplexFifoStream.AllocBlock (IL offset: 0xe)
at SDRSharp.Radio.dll.ComplexFifoStream.GetWBlock (IL offset: 0x0)
at SDRSharp.Radio.dll.ComplexFifoStream.Write (IL offset: 0x44)
at SDRSharp.exe.MainForm.ProcessBuffer (IL offset: 0x4a)
at SDRSharp.Radio.dll.StreamControl.ProcessIQ (IL offset: 0x18)
at SDRSharp.Radio.dll.StreamControl.DSPProc (IL offset: 0x5b)
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)
 

thewraith2008

Member
Joined
Nov 22, 2016
Messages
1,850
Do you have any recordings enabled in TTT? I suspect the error and SDR# crash on my side is related to a recording issue.
@hamradionl: Do you have any recording enabled in TTT?

Yes recording for selected GSSIs.
The recording is done by a Windows API via TTT. If there was an issue with it, then SDR# would not crash, as it has nothing to do with it.

The continuing test with SDR# 1700(x2) + plug-in and TTT in dual mode is still going strong after 25hr 30min.

Maybe you guys with the crashing issue should try a few different set-ups to test if crash occurs.
  1. SDR# with no TETRA demodulator plug running on frequency with signal. (No TTT running)
  2. SDR# with TETRA demodulator plug [NOT ON] running on frequency with signal. (No TTT running)
  3. SDR# with TETRA demodulator plug [ON] running on frequency with signal. (No TTT running)
  4. Maybe even repeat the above 1-3 with a second SDR# running.
What happens?
 

DarkAngelT

Member
Joined
Sep 27, 2018
Messages
131
Thewraith, I want to contribute here to the problem that the colleague is reporting, because I went through similar things in part when using two SDR cards! When I left the computer on using two SDRs, one of them would freeze and the other would work. To be more specific the one that does the LA exchange and reproduces the communications. The SDR card that read the information kept working (In vain obviously, because the one that reproduced was frozen) That's when the computer did not really turn blue !!!!
 

tsapers

Member
Joined
Aug 25, 2011
Messages
68
@thewraith2008: Thanks I will run the above tests and see what happens.

From the thread I can see there are 3 distinct issues.
1) "type System.OutOfMemoryException." as per hamradionl. This crashes SDR#.
2) "An item with the same key has already been added. " as per tsapers on post #464 https://forums.radioreference.com/t...nk-tracking-demonstration.370639/post-3061730 This also crashes SDR#.
3) Lastly the situation where CC or VC freezes and no longer processes which could also result in a crash of SDR# in some cases.

I will monitor issue #1 and #3 here and do my own tests for #2 and feedback once I have more clarity.
 

thewraith2008

Member
Joined
Nov 22, 2016
Messages
1,850
Another thing I've seen that can ruin a SDR# session is when a (my) monitor goes to sleep (not screensaver). For whatever reason, it seems to corrupt USB comms when waking up monitor again. But that didn't crash SDR# it just made SDR# lag.
 

hamradionl

Member
Joined
Mar 23, 2014
Messages
730
tsapers
In SDR# 1700 install.BAT file i dont know if link to zadig work. Last week WIN 10 update so i install zadig 2.4 manual, again
thewraith2008
thank you,
never be problem in TTT versions, wil kill screensaver to be sure


1920 hours local GMT Europe i did full install and restart SDR# 1700 +TTT 1.08 + hotfix - 3 + 5 + 6 SINGLE mode
 

klausserthib

Member
Joined
Jan 27, 2019
Messages
8
Hi All,

I'm new on radioreference forum and follow this topic actively since a few days ! I'm testing the last release of Tetra Demodulator Plugin with last SDR Sharp Version. TTT version is 1.0.8 on my environnement.

Everything works fine for many hours/days but GSSI display bug persist (TTT is still displaying ISSI number instead of GSSI but not at each time). This bug never appear on previous versions. Something will be done to correct this issue on future versions ? Thanks !
 

hamradionl

Member
Joined
Mar 23, 2014
Messages
730
type System.OutOfMemoryException.
at mscorlib.dll.Dictionary`2.Resize (IL offset: 0x19)
at mscorlib.dll.Dictionary`2.Insert (IL offset: 0x10e)
at SDRSharp.Tetra.dll.SduParser.ParseLLC (IL offset: 0x13)
at SDRSharp.Tetra.dll.SduParser.Parse (IL offset: 0x0)
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: 0x2735)
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)
 

DarkAngelT

Member
Joined
Sep 27, 2018
Messages
131
thewraith2008

As promised, I'm passing by here to give my feedback on how the latest update works and indeed! He stopped losing most of the communications he had been missing and stopped the problem of confusing ISSI with GSSI!

Congratulations on the improvements, my friend!
 
Top