SDR# TETRA Demodulator Trunk Tracking Demonstration

[jlmarc33]

Thank you for your help and your tests.
I have installed last SDR# and TTT on another PC (Laptop with W10 Home v1909 - french),... and I can't reproduce the problem seen on W10 Pro v2004.
I will continue to investigate about my W10Pro security parameters.

 

[FERRAINAELENA]

ho visto che gli algoritmi sono stati rotti

 

[tomekjkp]

ho visto che gli algoritmi sono stati rotti

Cos'è questo software?

 

[lc24cxx]

Cos'è questo software?

decodio

same pic Decodio

 

[Motik]

Hi,

I'm getting an error which I can't find how to correct, although I'm sure I already corrected it in the past on another computer

When launching TTT it complains about syntax errors where, instead of the expected values "true" and "false", it finds the equivalent in my local language (French) :

==============
11/11/2020 11:26:19
Unknown ERROR[RAW]:
Last DATA: Result:Error,Type:Syntax error,Message:{\command\: \set\, \method\: \netinfowindowopen\, \value\: vrai}
==============
Syntax error in \method\: \netinfowindowopen\ invalid \value\: vrai}
==============
Call active: Faux
tmrSaveTimed: Vrai
==============

I know the error comes from inside TTT because it also saves GSSI info with the same translated values, although the TETRA plugin in SDR# correctly uses English values.

from TETRA_GSSI:
3001922;208;82;;0;Vrai
3001926;208;82;;0;Vrai
3003922;208;82;;0;Vrai
3003923;208;82;;0;Vrai

from tetraSettings.xml:
<AutoPlay>false</AutoPlay>
<IgnoreEncodedData>false</IgnoreEncodedData>
<IgnoreEncodedSpeech>false</IgnoreEncodedSpeech>
<TttModeEnabled>true</TttModeEnabled>
<TttUdpPort>3383</TttUdpPort>
<IsCc>true</IsCc>

As said, I have another computer where this problem doesn't appear, and on which I remember getting the same errors and finding how to correct them a year or so ago...

Anybody can point me to the right direction?

 

[FERRAINAELENA]

decodio

same pic Decodio

SI CONFERMO DECODIO

 

[thewraith2008]

Hi,

I'm getting an error which I can't find how to correct, although I'm sure I already corrected it in the past on another computer

When launching TTT it complains about syntax errors where, instead of the expected values "true" and "false", it finds the equivalent in my local language (French) :

==============
11/11/2020 11:26:19
Unknown ERROR[RAW]:
Last DATA: Result:Error,Type:Syntax error,Message:{\command\: \set\, \method\: \netinfowindowopen\, \value\: vrai}
==============
Syntax error in \method\: \netinfowindowopen\ invalid \value\: vrai}
==============
Call active: Faux
tmrSaveTimed: Vrai
==============

I know the error comes from inside TTT because it also saves GSSI info with the same translated values, although the TETRA plugin in SDR# correctly uses English values.

from TETRA_GSSI:
3001922;208;82;;0;Vrai
3001926;208;82;;0;Vrai
3003922;208;82;;0;Vrai
3003923;208;82;;0;Vrai

from tetraSettings.xml:
<AutoPlay>false</AutoPlay>
<IgnoreEncodedData>false</IgnoreEncodedData>
<IgnoreEncodedSpeech>false</IgnoreEncodedSpeech>
<TttModeEnabled>true</TttModeEnabled>
<TttUdpPort>3383</TttUdpPort>
<IsCc>true</IsCc>

As said, I have another computer where this problem doesn't appear, and on which I remember getting the same errors and finding how to correct them a year or so ago...

Anybody can point me to the right direction?

I don't know why this works OK for some people/PCs and not other people/PCs.

I did a test (mentioned here) and could not repeat error.
This makes it hard to work out problem.

While TTT is reporting the error, it looks like the plug-in has the problem as noted by the response: "Result:Error" for "netinfowindowopen".
Plug-in could be expecting "True" instead of "vrai", but why does it work on other PCs in same region?



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

 

[Motik]

I don't know why this works OK for some people/PCs and not other people/PCs.

I did a test (mentioned here) and could not repeat error.
This makes it hard to work out problem.

While TTT is reporting the error, it looks like the plug-in has the problem as noted by the response: "Result:Error" for "netinfowindowopen".
Plug-in could be expecting "True" instead of "vrai", but why does it work on other PCs in same region?



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

Thank you thewraith2008 for your answer (and for the amazing work on TTT!) I had forgotten about that other French person who got the same error although it was only a couple weeks ago and I had myself answered that I didn't have the problem (on my other machine, obviously)

FWIW both my machines are running the same version of Windows 10 Insider (20H2 19042.610). I'll try to find what differences there are.

 

[thewraith2008]

@Motik : I have done another test with the following system settings changed:

Languages           > France
Preferred languages > France
Region              > My Default Region
Region format       > English
Language for non-Unicode programs > English

Languages           > France
Preferred languages > English
Region              > My Default Region
Region format      > English
Language for non-Unicode programs > English

Languages           > France
Preferred languages > France
Region              > France
Region format       > French (France)
Language for non-Unicode programs > English

Languages           > France
Preferred languages > English
Region              > France
Region format       > French (France)
Language for non-Unicode programs > English

Languages           > France
Preferred languages > France
Region              > France
Region format       > French (France)
Language for non-Unicode programs > French (France)

Languages           > France
Preferred languages > English
Region              > France
Region format       > French (France)
Language for non-Unicode programs > French (France)

TTT is starting as expected with the plug-in.
When TETRA_gssi.txt is created/saved, it uses "True" not "Vrai"
It is assumed that that commands sent to the plug-in are also sending "True" not "Vrai".

It seems likely that the plug-in is having a problem with the boolean type and not translating "Vrai" as "True".
I could probably make this a fixed string, but I would prefer to find why this is occurring only in some cases.

Do other French users with a working TTT out there see "Vrai" in the TETRA_gssi.txt file or is it using "True"?



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

 

[jlmarc33]

@thewraith2008 and @Motik.
Hi,
With my fully working TTT on laptop (W10 Home, french, now in 20H2 release), all TETRA_GSSI.txt lines are generated with "True" strings.
On my desktop, with netinfowindowopen error (W10 Pro, french, 20H2), TETRA_GSSI.txt lines are generated with "Vrai" strings.

 

[thewraith2008]

@thewraith2008 and @Motik.
Hi,
With my fully working TTT on laptop (W10 Home, french, now in 20H2 release), all TETRA_GSSI.txt lines are generated with "True" strings.
On my desktop, with netinfowindowopen error (W10 Pro, french, 20H2), TETRA_GSSI.txt lines are generated with "Vrai" strings.

Well, so far the only obvious difference is Window 10 Home and Pro.

Do you see the same settings (in Languages and Region) between the Desktop and Laptop in Windows 10?

Languages
Preferred languages
Region
Region format
Language for non-Unicode programs

Another possible guess, is that the installed .NET runtime libraries maybe of different languages between desktop and laptop
Not sure how you would check this.


I would have also expected to see other people with languages other than English mention this problem by now.
Strange indeed.



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

 

[SignalPatcher]

I got interested in the signal below. It has got width 50 kHz. It is on 390,9750 frequency and sounds like TETRA. I managed to read that it might be TEDS, but there is no available decoder which reads that. I'm sending links about TEDS below and a recording. Could anybody have a closer look on that?

TETRA Release 2 - TCCA

https://www.etherstack.com/us/pdf/TETRA-TEDS.pdf

About TEDS (TETRA2) Modulation Analysis

TETRA DIB-R5 | TETRA Systems

https://core.ac.uk/download/pdf/80702135.pdf

https://www.bakom.admin.ch/dam/bakom/en/dokumente/faktenblatt_tetra.pdf

File on MEGA

mega.nz

 

[jlmarc33]

Well, so far the only obvious difference is Window 10 Home and Pro.

Do you see the same settings (in Languages and Region) between the Desktop and Laptop in Windows 10?

Languages
Preferred languages
Region
Region format
Language for non-Unicode programs

Another possible guess, is that the installed .NET runtime libraries maybe of different languages between desktop and laptop
Not sure how you would check this.

I would have also expected to see other people with languages other than English mention this problem by now.
Strange indeed.

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

Here are the results

1) Language and Région parameters check

On desktop PC: Windows 10 Pro - 20H02 (19042.630)
Windows feature experience pack: 120.2212.31.0
Languages > French (France)
Preferred languages > French (France)
Region > France
Region format > French (France)
Language for non-Unicode programs > French (France)

On laptop PC: Windows 10 Home - 20H02 (19042.630)
Windows feature experience pack: 120.2212.31.0
Languages > French (France)
Preferred languages > French (France)
Region > France
Region format > French (France)
Language for non-Unicode programs > French (France)

... so, same Windows configuration for Language and Région parameters.

2) .NET framework version check
Need to know the .NET version on Windows 10? Here's how in three ways.

I used W10 PowerShell console to check the installed .NET versions with the following command:

Get-ChildItem 'HKLM:\SOFTWARE\Microsoft\NET Framework Setup\NDP' -Recurse | Get-ItemProperty -Name version -EA 0 | Where { $_.PSChildName -Match '^(?!S)\p{L}'} | Select PSChildName, version

In W10 Pro, I found different versions of .NET framework



In W10 Home, I found only last 4.8 .NET framework (the last 3 lines in PS console).

 

[thewraith2008]

@jlmarc33

Not sure if it really matters, but can you check the language of the v4.x .NET runtime on both desktop and laptop?
I'm guessing that these were already installed with Windows 10 Home/Pro, but it can't hurt to check anyway.

A possible way of determining this is to go to: "C:\Windows\Microsoft.NET\Framework\v4.0.30319" and look at the properties (right click file) for "Accessibility.dll". Look at the "Details" tab and find "Language" property: e.g. English (United States)



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

 

[thewraith2008]

I got interested in the signal below. It has got width 50 kHz. It is on 390,9750 frequency and sounds like TETRA. I managed to read that it might be TEDS, but there is no available decoder which reads that. I'm sending links about TEDS below and a recording. Could anybody have a closer look on that?

TETRA Release 2 - TCCA

https://www.etherstack.com/us/pdf/TETRA-TEDS.pdf

About TEDS (TETRA2) Modulation Analysis

TETRA DIB-R5 | TETRA Systems

https://core.ac.uk/download/pdf/80702135.pdf

https://www.bakom.admin.ch/dam/bakom/en/dokumente/faktenblatt_tetra.pdf

File on MEGA

mega.nz

This would require something to be made from the ground up.
- Demodulator for 4/14/32/QAM
- Decoder for the layers above the physical layer.
- MELPe Voice Codec or AMR
- Months/Years of time

This would require at least the air interface/voice codec standards documentation.

I would not be motivated to do something like this if it did not exist locally (which it does not).
Most providers here have/are shutting down TETRA and seem to be opting for the cheaper lower quality DMR.



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

 

[Sinager]

Hi,
I run successfully TTT on several other PCs, however there's one where the Tetra Plugin crashes SDR# with this .Net error:

************** Testo dell'eccezione **************
System.NullReferenceException: Riferimento a un oggetto non impostato su un'istanza di oggetto.
in SDRSharp.Tetra.TetraPanel.AfcTimer_Tick(Object sender, EventArgs e)
in System.Windows.Forms.Timer.OnTick(EventArgs e)
in System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
in System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

Unfortunately Win10 doesn't allow reinstalling .Net these days.
Any hints? I'd rather not wipe and reinstall the full system.

SDR# version doesn't seem to matter.
Standard (non TTT custom) Tetra plugin gives the same error.
Full log attached.

Thanks
Sinager

 

[jlmarc33]

@jlmarc33

Not sure if it really matters, but can you check the language of the v4.x .NET runtime on both desktop and laptop?
I'm guessing that these were already installed with Windows 10 Home/Pro, but it can't hurt to check anyway.

A possible way of determining this is to go to: "C:\Windows\Microsoft.NET\Framework\v4.0.30319" and look at the properties (right click file) for "Accessibility.dll". Look at the "Details" tab and find "Language" property: e.g. English (United States)

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

@thewraith2008

I checked all Acessibility.dll for desktop and laptop PC in C:\Windows\Microsoft.NET\Framework\v4.0.30319, and also in \Framework64 directory.
They all own the same language property : English (United States).
... No new tracking idea.

 

[Sinager]

I run successfully TTT on several other PCs, however there's one where the Tetra Plugin crashes SDR# with this .Net error:

Nevermind, I nuked the damn thing

 

[thewraith2008]

@Motik @jlmarc33 and maybe @Sinager

I think I may have an answer to your problem.

In the newer SDR# (around v1733+) a feature was added for the lazy loading of plug-ins.
This will stop the plug-in from running the UI if the side panel for plug-in is minimized.
This results in an internal error when TTT tries to set 'netinfowindowopen' (because UI is not there) and the plug-in returns the error response to TTT which just keeps retrying it and will not proceed until it gets a OK response from the plug-in.

So if the plug-in side panel is minimized when you start TTT, then the following error is seen:

==============
14/11/2020 9:35:46 AM 
Unknown ERROR[RAW]:
Last DATA: Result:Error,Type:Syntax error,Message:{\command\: \set\, \method\: \netinfowindowopen\, \value\: true}
==============
Syntax error in \method\: \netinfowindowopen\ invalid \value\: true}
==============
Call active: False
tmrSaveTimed: True
==============

So make sure it's not minimized and it should be OK.
Let me know if this works for you.



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

 

[Motik]

@Motik @jlmarc33 and maybe @Sinager

I think I may have an answer to your problem.

In the newer SDR# (around v1733+) a feature was added for the lazy loading of plug-ins.
This will stop the plug-in from running the UI if the side panel for plug-in is minimized.
This results in an internal error when TTT tries to set 'netinfowindowopen' (because UI is not there) and the plug-in returns the error response to TTT which just keeps retrying it and will not proceed until it gets a OK response from the plug-in.

So if the plug-in side panel is minimized when you start TTT, then the following error is seen:

==============
14/11/2020 9:35:46 AM
Unknown ERROR[RAW]:
Last DATA: Result:Error,Type:Syntax error,Message:{\command\: \set\, \method\: \netinfowindowopen\, \value\: true}
==============
Syntax error in \method\: \netinfowindowopen\ invalid \value\: true}
==============
Call active: False
tmrSaveTimed: True
==============

So make sure it's not minimized and it should be OK.
Let me know if this works for you.



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

Thank you @thewraith2008 for investigating this. Unfortunately, in my case, the TETRA demodulator side panel has always been open.