SDR# TETRA Demodulator Trunk Tracking Demonstration

[thewraith2008]

None. When focusing the TTT window I get the spinning wheel cursor and the window is greyed out. When I click the red X to close, Windows offers to force-close and send a crash report to Microsoft.

Also which way have you set-up the recording.
Method #1 or Method #2 described in "TTT_Set-up_manual.pdf"

• see "Recording Audio set-up (Method #1)"
• see "Recording Audio set-up (Method #2)"

 

[thewraith2008]

Hi wraith,
Thanks again from New Zealand.
Im a bit rusty and havnt used since the first release.
How do i upgrade to the latest version, just download, copy paste and replace new files or?

Probably easier just to start fresh with SDR# and TTT. Try it, see what it does. Simples.

 

[Kasmus]

Also which way have you set-up the recording.
Method #1 or Method #2 described in "TTT_Set-up_manual.pdf"

• see "Recording Audio set-up (Method #1)"
• see "Recording Audio set-up (Method #2)"

#2 using Virtual Audio Cable and it's set to 2ch 16bit 48kHz as per default. The files recorded by TTT are 1ch 16bit 22050Hz so I tried creating another VAC using that sample rate but SDR# won't start then. While doing that, I noticed that I had been using the audio devices prefixed with [MME] in the Audio drop down menu in SDR#. I then switched to [Windows DirectSound], using the same 2ch 16bit 48kHz VAC as before.

What can I say, that seems to have fixed it. TTT started recording right away from the first call.

Now I feel a little stupid for not having tried that earlier.

 

[hamradionl]

Kasmus
Thank you,
i what not able get record work for longtime

 

[tomekjkp]

tomekjkp
Just to be sure i like try help, are you use SINGLE 1x RTLSDR or DUAL 2x RTLSDR?
SDR# config file, setting samplerate to 48000?
SDR# AUDIO FILTER OFF ?

.

I'm using Single RTLSDR
Samplerate is 48000 set
Audio filter ON, see screen in attachment no. 1

Assuming the original language was not English, did you set it to English?

The languages on which I tested were Polish, English EU, English US and German

 

[reckless76]

Any error message/pop-up shown?
Does SDR# + Plug-in work without using TTT?

No error, TTT simply freezes and does Not respond any more. Without TTT, sdr has no problems.

 

[hamradionl]

I'm using Single RTLSDR
Samplerate is 48000 set
Audio filter ON, see screen in attachment no. 1

SDR#
SDRSharp.exe.Config <add key="minOutputSampleRate" value="48000" />
SDR# AUDIO FILTER OFF <=== Empty

 

[Kasmus]

No error, TTT simply freezes and does Not respond any more. Without TTT, sdr has no problems.

Can you check which audio output device you have selected in SDR#? The ones prefixed [MME] always crashed TTT on my machine but [Windows DirectSound] seems to work now.


Don't mind the checked "Filter Audio" box, I was using SDR# for something else. It should be unchecked for TETRA.

 

[thewraith2008]

Can you check which audio output device you have selected in SDR#? The ones prefixed [MME] always crashed TTT on my machine but [Windows DirectSound] seems to work now.

Don't mind the checked "Filter Audio" box, I was using SDR# for something else. It should be unchecked for TETRA.

Setting it like that will also record any system sounds. This is method #1.

While the instructions in "TTT_Set-up_manual.pdf" for setting up both methods to record sound are for Windows 7, Window 10 is basically the same, except the starting point in Windows 10 is slightly different.

Windows 10 recording set-up

Method #1
NOTE: This method will also record any system sounds (Method 2 is better)
Right click the speaker icon on the systray and click 'Sounds'.
Select 'Recording' tab.
Select/highlight 'Wave'.
Click 'Set Default'
Click OK

In SDR# > Audio > Output > Select the 'Microsoft Sound Mapper - Output'.

Method #2
Install a virtual audio cable.

Right click the speaker icon on the systray and click 'Sounds'.
Select 'Recording' tab.
Select/highlight a virtual audio cable to use.
Click 'Set Default'
Click 'Properties'
Select 'Listen'
Enable 'Listen to this device' checkbox
Click OK

In SDR# > Audio > Output > Select the virtual audio cable you used above.

 

[Kasmus]

Setting it like that will also record any system sounds. This is method #1.

What makes you think that? You can't even see the audio device name in that screenshot.



BTW I had TTT run for 12 hours now using [Windows DirectSound] instead of [MME], still doing it's thing, no crashes anymore.

 

[DarkAngelT]

thewraith2008




TTT is showing Worm.Win32.WBVB infection
Can you tell why this is happening?
Is there a way for the program to work without this kind of warning?

 

[DarkAngelT]

The last version is the one that is showing this type of behavior. Strange that others have not presented and this one is showing this type of behavior

 

[thewraith2008]

TTT is showing Worm.Win32.WBVB infection
Can you tell why this is happening?

No

Is there a way for the program to work without this kind of warning?

A better AV software.
Set TTT in AV exclusions list.

The files provided in the zip are virus free. What happens to them after is out of my control.

Your AV claims TTT to be "Worm.Win32.WBVB'
from wiki:

A computer worm is a standalone malware computer program that replicates itself in order to spread to other computers.[1] Often, it uses a computer network to spread itself, relying on security failures on the target computer to access it. Worms almost always cause at least some harm to the network, even if only by consuming bandwidth, whereas viruses almost always corrupt or modify files on a targeted computer.

TTT does none of this, so your AV software is full of and is the one not to be trusted.

This is what TTT does to work with SDR#.
TTT reads from 'TETRA Demodulator' plug-in: (Using windows API)

• PDUs output from 'Network Info' 'Calls' tab.
• MCC/MNC/LA values

TTT interprets this data for call control.
TTT via the use of Windows API, sets:

• 'Net Remote' enable/disable and port #.
• 'TETRA Demodulator' enable/disable and timeslot 1-4.

TTT via the use of 'Net Remote' plug-in (which uses UDP) controls SDR# BW, Mode, frequency, volume/mute.

That's it

 

[thewraith2008]

What makes you think that? You can't even see the audio device name in that screenshot.

BTW I had TTT run for 12 hours now using [Windows DirectSound] instead of [MME], still doing it's thing, no crashes anymore.

Could not see the "Line 1" so I assumed
Glad it now works for you. Hopefully what you found out helps others with same issue.

 

[thewraith2008]

15th Public Release - TETRA Trunk Tracker and TETRA Demodulator plug-in - v1.0.15.9


This package (version) of TETRA Trunk Tracker and TETRA Demodulator plug-in (with codec libtetradec.dll) are only meant to be used
with each other and with no other previous versions. To do so will most likely cause issues.

No changes to TETRA Demodulator plug-in in this release.


If SDR# is crashing when 'Demodulator' is enabled, it's because you have not set-up the plug-in correctly.
You MUST do this 1st. This is NOT TETRA Trunk Trackers fault.

You generally need to get these installed:
"Microsoft .NET Framework 4.6.2 (Offline Installer)"
"Microsoft .NET Framework 4.7.2 (Offline Installer)"
"Microsoft Visual C++ 2015 Redistributable" and install both 32/64 bit versions (if you use 64 bit OS)


This should fix the issue as reported here

This TETRA Trunk Tracker version changes/adds and fixes some items:

v1.0.15.9 - Minor update

FIXED: String handling issue that affected some causing TTT not to start in non-English locales

FIXED: On 2nd start (after initial set-up) a pop-up error "LRRP path is not valid" would show when path
 field was left blank. Blank is valid (saves LRRP to TTT folder). The error should only show if set 
 path no longer exists.

Has been tested on Windows 7 - Basic (64 bit)
Has been tested on Windows 7 - Professional SP1 (32 bit), English
Has been tested on Windows 10 - Professional (64 bit)

I have created it to suit my needs. And it currently works for me with the TETRA network I monitor.

I make no claim that it will work for other networks.

Please read the provided files for set-up and usage:

• TTT_set-up_manual.pdf
• TTT_Features_and_Usage.pdf

I have tried to be as thorough as possible with the documentation to explain usage and features.
I believe any questions can be answered by reading these files.
These files most likely are not complete and contain errors and are not laid out as good as they could be.

The TETRA plug-in is now been mainly tested with SDR# 1700 on Windows 7 Professional 32 bit with no issues seen.
The TETRA plug-in with SDR# 1700 on Windows 7-10 64 bit PCs is untested by me and is known.

It only works with the provided TETRA plug-in supplied in zip. (2019-May-10).
This version uses a custom compiled version of 'Net Remote' supplied in zip

It is only meant to be a temporary solution until something better comes along.


Note: This link now is to a folder that stores the download, which means the link to the location of the files will stay the same but the files in it can vary.
Download

MD5 HASH c13abed7e6362a69e2a8d6ea9d5a72fd

 

[reckless76]

Can you check which audio output device you have selected in SDR#? The ones prefixed [MME] always crashed TTT on my machine but [Windows DirectSound] seems to work now.

View attachment 71437
Don't mind the checked "Filter Audio" box, I was using SDR# for something else. It should be unchecked for TETRA.

Changing outputs makes no different. TTT still crashes, even installing 1.0.15.09 makes no wonders.

 

[Ubbe]

TTT is showing Worm.Win32.WBVB infection
Can you tell why this is happening?
Is there a way for the program to work without this kind of warning?

I don't know if bigger companies that produce windows software somehow reports to different AntiVirus and AntiMalware companies what programs they create and their hash sums to put them on a white list, but any program that writes to an already existing file on the harddrive are suspicious of adding damaging code to it and are flagged as dangerous and if the code bytes sequence match an already known malware or virus it flags it with that name. Using code that handles ip numbers and/or network ports are treated as code that tries to spread the detected virus or malware over the network.

If TTT didn't had code that writes to an already existing log file that builds up in size with each recording, it probably wouldn't give false detects with some antivirus/antimalware programs.

/Ubbe

 

[reckless76]

Changing outputs makes no different. TTT still crashes, even installing 1.0.15.09 makes no wonders.

SOLVED, TTT was unable to open network info window. So the program went in a spiral.
Reinstallation of SDR and plugins did solve my problem.
Now running SDR# x86 rev 1700 / TTT_1.15.9

 

[thewraith2008]

If TTT didn't had code that writes to an already existing log file that builds up in size with each recording, it probably wouldn't give false detects with some antivirus/antimalware programs.

/Ubbe

TTT has created and appended log files (plain text) and recorded wav files since the start. (over 12 months ago).
Actually the WAVs recording and saving is handled by windows own 'mciSendString' function.

The AV vendors are pretty slow at detecting that TTT is supposed to be up to no good. If it was a real virus/trojan/worm it could have formatted a HDD hundred times over in that time.



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

 

[thewraith2008]

Changing outputs makes no different. TTT still crashes, even installing 1.0.15.09 makes no wonders.

You will just have to try different combinations of things to see if anything else works. What the "different combinations" are is the trick.
There is no reason why v1.0.15.9 would make any different to this crash issue as the update does not address this.
I don't know what's causing crash so I can't fix it, and it sounds more like OS specific set-up issue and/or possibly a limitation of the implemented recording function on the Windows 10 64 bit OS with some sound devices.



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