SDR# TETRA Demodulator Trunk Tracking Demonstration

[R3Natas]

* Do you use option in plug-in "Call list - Alternative generation". If not then you could be seeing anything there.

Enabled this function and still the same problem appears

 

[thewraith2008]

I'm using only Demodulator itself, without TTT.
Problem with ISSI occurs in TMO and no, I'm not using this feature "Call list - Alternative generation", can you specify what it does?

It uses d-steup PDU and the callid to add calls to list. any other PDUs (d_tx_ceased,d_tx_granted,d_release etc..)
it helps to only show actual call and not all the thru connects which are apart of call be not a call itself.

Can you explain in more detail what your seeing with the false ISSI and where.
Maybe include the PDU output from the plug-in.

thewraith2008
Sorry, mean not any harm just share information to get perfect. Please leave the panels in, other panels show handy information to use.
In your video i notice some analyzing tool, Personal iam interested in that plugin / tool.

Don't apologize for been curious. I have already removed the 'burst error' in it's current state it's just going to be trouble. It may make a return.

 

[R3Natas]

It uses d-steup PDU and the callid to add calls to list. any other PDUs (d_tx_ceased,d_tx_granted,d_release etc..)
it helps to only show actual call and not all the thru connects which are apart of call be not a call itself.

Can you explain in more detail what your seeing with the false ISSI and where.
Maybe include the PDU output from the plug-in.

For example in TMO mode, I select a group (i.e. 100) and transmit to it with my ISSI 1001 in the Calls section:
Call ID is OK, Group is OK, TXer is OK, but in the Users section there appears not only my ISSSI 1001, but for example 1002, 1003
But I'm sure I'm only one transmitting in that group

 

[thewraith2008]

In your video i notice some analyzing tool, Personal iam interested in that plugin / tool.

The only program in the video is SDR# with the TETRA Demodulator plug-in with the "Network Info" window opened on the "burst type" tab.
Also seen is the (IQ) File Player plug-in. IQ samples that are sent to me can be played with it.

For example in TMO mode, I select a group (i.e. 100) and transmit to it with my ISSI 1001 in the Calls section:
Call ID is OK, Group is OK, TXer is OK, but in the Users section there appears not only my ISSSI 1001, but for example 1002, 1003
But I'm sure I'm only one transmitting in that group

OK, I understand.
The PDU logging window ( "Network Info" Call tab under calls list). will (should) show all the PDUs that the plug-in reacts too.
It should show the PDUs with SSI:1002 and SSI:1003 (or Party_SSI:1002 and Party_SSI:1003) .

 

[R3Natas]

OK, I understand.
The PDU logging window ( "Network Info" Call tab under calls list). will (should) show all the PDUs that the plug-in reacts too.
It should show the PDUs with SSI:1002 and SSI:1003 (or Party_SSI:1002 and Party_SSI:1003) .

But why, in the previous versions of plugin everything was alright, there were no FALSE ISSI and now there's 1002 and 1003, but those do not exist, so how plugin finds them?

 

[thewraith2008]

But why, in the previous versions of plugin everything was alright, there were no FALSE ISSI and now there's 1002 and 1003, but those do not exist, so how plugin finds them?

I don't know.
So there are no PDUs in the log with those numbers?

I'll keep and eye open for it here.

 

[passie101]

When I tune on a freq with a DMO/Gateway on the first data burst SharpSDR crashes. On "normal" DMO repeaters no problem.

 

[RicardoRJ]

I am having the following error while running the TTT. The sdr # closes and the TTT continues to run. This happens when you click START.
The following is the description of the crash.txt file.
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)

 

[thewraith2008]

Hot-fix #2 for TTT v1.0.8 Public Release - Updates TETRA Trunk Tracker and plug-in to v1.0.9


This hot-fix #2 is only for the full release version of TTT v1.0.8 and no other version.
TTT v1.0.8 Must be installed first.

Only these two files have been updated:

• SDRSharp.Tetra.dll
• tetra_trunk_tracker.exe

Copy them to the usual places.




This plug-in version changes/adds and fixes some items:

v1.0.9.0

CHANGED: Many improvements to DMO code. (Both MS-MS and DM-REP)
         - Improved error handling between TMO/DMO
         - Defined rules for DMCC (Direct Mode Call Control)
            DM_SETUP
            DM_SETUP_PRES
            DM_CONNECT
            DM_DISCONNECT
            DM_OCCUPIED
            DM_TX_CEASED
            DM_RELEASE
            DM_RESERVED
            DM_INFO

NOTE: Only some information elements of these PDUs are shown in output.

CHANGED: Moved the DMO output back to normal PDU log panel in 'Calls' tab

CHANGED: Plug-in side panel in SDR#
         - Indicator for DMO (When ON, a green DMO is displayed next to 'Demodulator' checkbox)
         - Repeater address when used, is shown where LA: is normally shown. Will be shown as "REP:x".
         - DMO enable option state is now saved. (Don't leave it on and forget when trying to use TMO again)

REMOVED: 'burst errors' tab. In it's current form was not suitable for normal use. This was only for testing and probably should have not
           been originally included.

CHANGE: The textboxes in the tabs "Calls", "Burst type" and "MS Registration" if left for long periods of time
        would accumulate large amounts of data. This would eat memory. This clears the data after every 1000+ lines.
        The "Calls" tab is a little tricky because TTT uses this for call control. I've tried to make it clear
        at 1000+ lines when it's thinks activity is at a minimum.
        This may fix out of memory conditions.

It seems some ISSI are sent as a psuedo value. This is a random number.
The standard refers to this as a concealment option in radios. (see below)
----
C.2.3.2 Transmitting Party Number Identification (TPNI) (EN300-396-03)

This intrinsic service provides the ability for the MSs receiving a call to receive the number of the currently transmitting MS.
This requires that the transmitting MS transmits an individual subscriber number at each call transaction.
This allows the receiving MS(s) to display the identity of the transmitting MS.
A user option allows details of the originating ITSI to be concealed.
This option allows a transmitting MS to withhold its identity (by substituting a pseudo SSI), a feature which may be required for certain authorized users.
NOTE: The pseudo SSI is an identity chosen at random by the MS and declared as such when it is used
-----



NOTE: No entries to the call list (in 'Network Info') are made. Not sure if we need to use it.
NOTE: The signal diagram panel will look different due to the burst nature of the signal.
NOTE: The signal quality % will not show a correct value due to the burst nature of the signal.
NOTE: The "Received" (red) indicator not show steady due to the burst nature of the signal.


MD5 HASH: SDRSharp.Tetra.dll - fb9e9ccdb40a8bf1374351b0fb83fd1c

See 'changelog.txt' more details.


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

v1.0.9.0

FIXED: The option "Position SDR#" was throwing any error about position not set.
       While this is correct if fields are blank, in single mode you can not set the VC SDR# field
        which results in not being able to set the checkbox.
       Dual mode uses 3 fields and Normal only used 2 fields.

FIXED: TTT call state/priority sounds - "snd_ssi_granted"
       The "snd_ssi_granted" sound was triggering multiple times. This was due to the handling of the
       2 types of "D_TX_Granted" PDUs that are seen. The code that "DeDUPs" this PDU should work better
       at detecting the 2 types and if the 2 PDU are related. (In which case won't pass it on)

FIXED: A incomplete SDS GPS PDU that can be seen, caused TTT to crash with "Run-time error '5' invalid procedure call or argument"
       The crash occurred because of TTT expectation of text following certain fields in the PDU.
       Something to note: Why was this PDU incomplete. Is this a plug-in issue?
 

MD5 HASH: 4c9d555d8d38559a445a8f79e52b62bf for "tetra_trunk_tracker.exe"

See 'changelog.txt' for more details.


As usual, Please read the provided files for set-up and usage in the TTT v1.0.8 package:

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


Hopefully this fixes some of the major issues.
As the DMO code is in it's early stage, it's implementation may not be 100% as expected.
Please read the plug-in changelog in relation to "Psuedo SSI" that can be seen in DMO mode.

REMOVED LINK - It will return shortly - Sorry

MD5 HASH ccfc093ad41f1688774a1de5e0243fd9

 

[R3Natas]

Hello, thewraith2008,

Thanks for the update, tested with DMO, works perfectly, now I will try to collect some DMO Gateway IQ's to enable support, because now when I tune to DMO Gateway my SDR# just crashes.

 

[R3Natas]

Another question with TTT, can we transfer all the info to it, like SDS messages with pre-defined statuses, MS Registrations and etc.
Like make some tabs in the TTT, so we can see all the info and not only calls like now, so we leave Demodulator plugin only for technical purposes

 

[thewraith2008]

Bummer, missed the edit window

If you downloaded from original v1.0.9 from release post, please re-download.

New details

FIXED: 3 typos that stopped Burst type tab working, Oops.

MD5 HASH: 33f3e1c5c36518f667296dd439c816e1 for "SDRSharp.Tetra.dll"

New Download link

MD5 HASH 0e8682315378b29754fa8b8ce713b272

 

[thewraith2008]

Hello, thewraith2008,

Thanks for the update, tested with DMO, works perfectly, now I will try to collect some DMO Gateway IQ's to enable support, because now when I tune to DMO Gateway my SDR# just crashes.

Still crashes on new version?

Another question with TTT, can we transfer all the info to it, like SDS messages with pre-defined statuses, MS Registrations and etc.
Like make some tabs in the TTT, so we can see all the info and not only calls like now, so we leave Demodulator plugin only for technical purposes

Probably not at the moment, only the calls tab updates all the time. Other tabs only update when they are visible/open.
TTT is pretty busy scraping the calls tab and the method to get this data is not easy. A lot of code magic going on there.

 

[R3Natas]

Still crashes on new version?

Only when I tune to DMO gateway, MS-MS works OK

Probably not at the moment, only the calls tab updates all the time. Other tabs only update when they are visible/open.
TTT is pretty busy scraping the calls tab and the method to get this data is not easy. A lot of code magic going on there.

OK no problem, will stick with what we have for now

 

[hamradionl]

I love all those tabs with information screens what is going on
DUAL MODE TRUNK
1.09 is running, maby some little stutter when user talk loud audio, but let you know end of day.
DMO
Stil not find any possible way to test this

 

[RicardoRJ]

thewraith2008 when using the libtetradec.dll from version 1.08 of TTT generates the following error:
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)
With the old version of this dll it works normal!
The error happens when I click the START button of the TTT, it simply appears a WinSock error 10053 and the sdrsharp closes.
Can you guide me on this error?
thanks

 

[hamradionl]

RicardoRJ, its working here ok
i copied the full folder 1.08 to new folder 1.09 and overwrite 2x files, In config i reset the path to log files and TTT trunk.
Windows popup ask for the Firewall settings.
On first millisecondes of a conversation, Look like some little bit stutter or some "hash sound" but is not annoying.
(not all radio sound like this)

thewraith2008
AVG like to scan these new files but seem ok

 

[RicardoRJ]

RicardoRJ, its working here ok
i copied the full folder 1.08 to new folder 1.09 and overwrite 2x files, In config i reset the path to log files and TTT trunk.
On first millisecondes of a conversation, Look like some little bit stutter or some "hash sound" but is not annoying.
(not all radio sound like this)

Now works great, I install the vc++ 32 and 64 bits redistributable version.
Thanks

 

[thewraith2008]

Stil not find any possible way to test this

I can only use DMO via IQ samples . I'd like to see more live stuff.

thewraith2008 when using the libtetradec.dll from version 1.08 of TTT generates the following error:
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)
With the old version of this dll it works normal!
The error happens when I click the START button of the TTT, it simply appears a WinSock error 10053 and the sdrsharp closes.
Can you guide me on this error?
thanks

Haven't we covered this?

Do you have 'libtetradec.dll' in the same folder as SDR# ?
Run SDR# + plug-in and do not run TTT.
Start SDR# and plug-in, If crash then you try and re-install the MS C++ and .NET runtime libraries. This is mentioned in the documentation and main release posts.



EDIT: You got it going great.

 

[passie101]

Is still crash on DMO gateway mode burst . ( do you need IQ data I can make some samples if needed )