SDR# TETRA Demodulator Trunk Tracking Demonstration

[RMW1010]

That's the best plot I've seen yet. Glad it's working well for you.



You are only seeing the request, looks like the MS are not setup to reply. I don't think its "protocol" as there is only one.

Thanks for your reply.
I've added some output from Telive:

20180811 14:21:26 FUNC:SDS [010011110100000000000000111100101011000000100010000101001000101101000000000000000001000010000000000000000000000000000000000]

20180811 14:21:26 FUNC:SDSDEC [CPTI:1 CalledSSI:10xxxxx CallingSSI:xxx CallingEXT:0 UserData4: len:9 protoid:0A(Location information protocol) LIP:[LONG PDU TYPE 1 Immediate location report request (not implemented yet)]] RX:1

20180811 14:21:26 FUNC: D-SDS DATA SSI:010xxxx IDX:000 IDT:1 ENCR:0 RX:1

20180811 14:22:05 FUNC:SDS [010011110100000000000000111100101011000000100010000101001000101101000000000000000001000010000000000000000000000000000000000]

20180811 14:22:05 FUNC:SDSDEC [CPTI:1 CalledSSI:10xxxxx CallingSSI:xxx CallingEXT:0 UserData4: len:9 protoid:0A(Location information protocol) LIP:[LONG PDU TYPE 1 Immediate location report request (not implemented yet)]] RX:1

20180811 14:22:05 FUNC: D-SDS DATA SSI:010xxxxx IDX:000 IDT:1 ENCR:0 RX:1

 

[thewraith2008]

Yes the units reply, When see this request, very short after you notice a response on slot 4.
When use the early plugin versions from February 2018, the GPS location is shown in SDS screen or test with the older/ early versions uses the M-SYS shell. Older versions the SDS screen is not resizeable yet, dont see the full length GPS string activity.

The DATA you refer to been off screen does not exits beyond what is also seen in the console window.

This is what is shown in console window:

D-SDS DATACPTI:1 CalledSSI:1234567 CallingSSI:89 CallingEXT:0 UserData4: len:9 protoid:0A(Location information protocol) LIP:[LONG PDU TYPE 1 Immediate location report request (not implemented yet)]
sq5bpf

As you can see, there is no Lat/Long GPS DATA there. And it is also mentioned "not implemented yet".

The plug-in version I tested with was posted on 13th January 2018 (last to use MSYS)
The IQ data I used was the one you provided.

You can look for yourself when you run a MSYS session,
Just type:

 startrx > tetra.log

This file is saved in "x:\mys64\home" folder.
Just log until you see SDS show up in the "Network Info" window then stop session (CTRL-C)
Search file for "SDS"

Note: When you log to file the console does not show anything (because it's been redirected to file)

 

[hamradionl]

Yes, those are a record from the latest plugin version. Unfortunately i never made a record with the older plugin version, There are records from the old version with GPS from local.

 

[thewraith2008]

I've added some output from Telive:

20180811 14:22:05 FUNC:SDS [01001111010000000000000011110010101100000010001000 01010010001011010000000000000000010000100000000000 00000000000000000000000]

This is the "Long location report" with Lat/Long positions with altitude.
They both decode as Lat:2.995330° - Long:0.083320° - Alt:1463m which doesn't make sense. The Gulf of Guinea, west coast of Africa over the ocean. I'm sure my math is good. But I could be wrong.

Maybe you could make a IQ sample in SDR# when these SDS PDUs are occurring and I could look into it further.

Yes, those are a record from the latest plugin version. Unfortunately i never made a record with the older plugin version, There are records from the old version with GPS from local.

It would not make a difference what TETRA plugin version you used when you recorded that Raw IQ sample, as the recording is done with SDR# and not the TETRA plug-in.

I do not see the SDS MS reply in that IQ sample like RMW1010 posted.

 

[thewraith2008]

I have be doing some testing and I think I can add detection for the "Long location report PDU".
Currently the TETRA Demodulator plug-in only does "Short location report PDU".
The only thing is I don't receive these location PDUs where I am.

I need someone to upload some IQ samples (create by SDR#) of these "Long location report PDUs" occurring.

[size=+2]With out these samples I can't do much to implement it.[/size]​

 

[RMW1010]

I have be doing some testing and I think I can add detection for the "Long location report PDU".
Currently the TETRA Demodulator plug-in only does "Short location report PDU".
The only thing is I don't receive these location PDUs where I am.

I need someone to upload some IQ samples (create by SDR#) of these "Long location report PDUs" occurring.

[size=+2]With out these samples I can't do much to implement it.[/size]​

Excellent.

I can send you some IQ recordings in the weekend. Am now on a different location.

 

[thewraith2008]

That would be great.

 

[thewraith2008]

I have received a sample from RMW1010 and I thought I'd post the results.

I have run it through SDR# and TETRA Demodulator plug-in (my custom version) and this is what is seen:

 SSI:1234567 D_SDS_Data Party_SSI:123 Type:3 Length:17 Protocol:Location_information SubType:Immediate_location_report_request ReportType:Short
 SSI:1234567 D_SDS_Data Party_SSI:123 Type:3 Length:17 Protocol:Location_information SubType:Immediate_location_report_request ReportType:Short
 SSI:1234568 D_SDS_Data Party_SSI:123 Type:3 Length:17 Protocol:Location_information SubType:Immediate_location_report_request ReportType:Short

These PDUs are only the "Immediate_location_report_request"
TeLive also is reporting this (from RMW1010 supplied log):

[LONG PDU TYPE 1 [b][color=red]Immediate location report request[/color][/b] (not implemented yet)]

These are requesting a SDS Short Location PDU from the MS.

Most likely that what is happening, is that request is been sent (via downlink as expexcted to MS) but the response PDU from the MS (which carries the GPS locations) is sent via uplink and then either:

A location PDU is sent via downlink to a different LA (location in network).

Or once the location PDU hits the infrastructure it is sent via network/internet/landline/gateway to destination.

The standard plug-in only processes the short location PDUs not the long ones. I have added some test code for the long PDUs in my version. But without IQ samples with these PDUs in them, I can't test this out.
If these long location PDU where sent on the downlink they would be reported by the plug-in as "SubType: Long_location_report"

 

[ET-NL]

I have send you a link to an IQ file with location data in it.

ET

 

[thewraith2008]

Thanks, received ET.


So can anyone out there provide "SubType: Long_location_report" PDU samples please.

 

[digiman1]

I would love to help but I don't seem to get ANY SMS/Location stuff

 

[digiman1]

Hey, any new updates coming up ? I love my TTT but curious if there will be any new features or tweaks etc.

 

[thewraith2008]

Always.

Hope to release new version soon. No timeline on release. (When its done) Still doing some testing.

Coming changes/additions and fixes to some items:

• Have merged Simple[Single] and Normal[Dual] version in to one.
• Separate output log file for all SDS_Data PDUs
• Handling for 'Individual call' Simplex/Duplex[half] setups. [Experimental]
• Support for D_SDS_Data long location report
• Remote window. (as "On Top") - This shows G/SSI and their labels if exists.
• Hold delay after recorded calls.

I have also compiled a new version of the TETRA Demodulator plug-in, here is some of the changes:

• FIXED .NET pop-up errors. Should no longer require "TETRA popup error dismisser' if you use it.
• ADDED: Increased some PDUs verbosity.
• ADDED: Audio DSP - Bandpass filter and AGC
• ADDED: Support for D_SDS_Data long location report. [Experimental]
• ADDED: Support for D_SDS_Data Text Messaging. [Experimental]
• Interval for displaying output to "Network Info" window.

 

[gustavobm]

Always.

Hope to release new version soon. No timeline on release. (When its done) Still doing some testing.

Coming changes/additions and fixes to some items:

• Have merged Simple[Single] and Normal[Dual] version in to one.
• Separate output log file for all SDS_Data PDUs
• Handling for 'Individual call' Simplex/Duplex[half] setups. [Experimental]
• Support for D_SDS_Data long location report
• Remote window. (as "On Top") - This shows G/SSI and their labels if exists.
• Hold delay after recorded calls.

I have also compiled a new version of the TETRA Demodulator plug-in, here is some of the changes:

• FIXED .NET pop-up errors. Should no longer require "TETRA popup error dismisser' if you use it.
• ADDED: Increased some PDUs verbosity.
• ADDED: Audio DSP - Bandpass filter and AGC
• ADDED: Support for D_SDS_Data long location report. [Experimental]
• ADDED: Support for D_SDS_Data Text Messaging. [Experimental]
• Interval for displaying output to "Network Info" window.

Wow! Nice update coming!

Thank you thewraith2008!

 

[digiman1]

Always.

Hope to release new version soon. No timeline on release. (When its done) Still doing some testing.

Coming changes/additions and fixes to some items:

• Have merged Simple[Single] and Normal[Dual] version in to one.
• Separate output log file for all SDS_Data PDUs
• Handling for 'Individual call' Simplex/Duplex[half] setups. [Experimental]
• Support for D_SDS_Data long location report
• Remote window. (as "On Top") - This shows G/SSI and their labels if exists.
• Hold delay after recorded calls.

I have also compiled a new version of the TETRA Demodulator plug-in, here is some of the changes:

• FIXED .NET pop-up errors. Should no longer require "TETRA popup error dismisser' if you use it.
• ADDED: Increased some PDUs verbosity.
• ADDED: Audio DSP - Bandpass filter and AGC
• ADDED: Support for D_SDS_Data long location report. [Experimental]
• ADDED: Support for D_SDS_Data Text Messaging. [Experimental]
• Interval for displaying output to "Network Info" window.

That's an epic update! I look forward to trying this out.

I look forward to this update specifically for "Handling for 'Individual call' Simplex/Duplex[half] setups. [Experimental]". I get quite a lot of calls where I only hear one side of a conversation so hopefully this is what I need.

 

[thewraith2008]

It's odd that this is happening using TETRA Trunk Tracker and the TETRA plug-in.
If the TETRA plug-in checkbox "Auto" is checked, then this is not how it should be set-up with TETRA Trunk Tracker. (should be unchecked)

Not all traffic is unique. You can see this in the Network Info window. A SSI and GSSI will appear more than once at the same time. This usually means the a caller is on another LA and is been connected to the call setup on the LA you listening too.

Most of the 'Individual calls' I receive are one sided.
Very rarely do I hear 2 people talking. When I do, these are normally simplex individual calls and both parties are on the same LA.

Individual duplex[half] calls are always going to be one sided. This is mainly because it's not implemented.
But also because the 2nd half of the duplex call is not always on the same LA.

It would not be to hard to follow, but one needs to know the setup procedure for this.
Also when the CC SDR# is moved off the CC, then some functionality is lost in TETRA Trunk Tracker.

 

[digiman1]

Individual duplex[half] calls are always going to be one sided. This is mainly because it's not implemented.
But also because the 2nd half of the duplex call is not always on the same LA.

It would not be to hard to follow, but one needs to know the setup procedure for this.
Also when the CC SDR# is moved off the CC, then some functionality is lost in TETRA Trunk Tracker.

I think that is what is happening to me quite a lot, I am getting a call handler calling a mobile station on a different LA so I only hear one part of the conversation, every now and again I will hear the call handler talking to someone in the same LA and I hear the response. This is something I would love implemented if possible.

I have 10 LA's

LA1 = 4 Freqs 1 of which is the Control Channel
LA2 = 3 Freqs 1 of which is the Control Channel
LA3 = 3 Freqs 1 of which is the Control Channel
LA4 = 2 Freqs 1 of which is the Control Channel
LA5 = 3 Freqs 1 of which is the Control Channel
LA6 = 3 Freqs 1 of which is the Control Channel
LA7 = 2 Freqs 1 of which is the Control Channel
LA8 = 3 Freqs 1 of which is the Control Channel
LA9 = 5 Freqs 1 of which is the Control Channel
LA10 = 2 Freqs 1 of which is the Control Channel

LA 9 Seems to be my Local LA as I get most activity here but I do from time to time listen to a different LA to see if I hear anything different.

 

[thewraith2008]

Individual duplex calls are setup up a little differently to the group calls.
While they still use D_Setup PDUs, the ones I see, always have "Transmission Not_granted" and there for are not setup by TETRA Trunk Tracker at all.

If you are using TETRA Trunk Tracker, it might be interesting to see a log file from your network to see if these are different. Use the option "Create CC VC log"

Upload to file host and send link to me via PM.

If one user is on LA1 and other user is on LA2 and you are listening on LA1, then you probably hear user from LA2 (which is sent to user on LA1)

User LA1 audio is sent via uplink through infrastructure to LA2 then via downlink to LA2 user.
User LA2 audio is sent via uplink through infrastructure to LA1 then via downlink to LA1 user (What you hear)

You won't be able to hear the uplink audio at all.

 

[digiman1]

Upload to file host and send link to me via PM.

It seems the Call Handler guy can talk across all LAs as I hear him all the time, I do hear responses to mobile stations on the same LA that I am on but sometimes I am hearing him talking to someone on another LA so yeah, it is making a bit more sense now.

If I switch LA I am able to hear the other end of the conversation with both call handler AND the mobile station. If it would be possible to change or even list the LA that the call handler is talking across to then that would be cool but I don't think it would be doable.

I will keep logging, once I have plenty I will upload and send you a link.

1 More thing, at the minute we are able to tag GSSI and SSI, is there a way I can Tag LAs ?

Thanks,
G

 

[thewraith2008]

If it would be possible to change or even list the LA that the call handler is talking across to then that would be cool but I don't think it would be doable.

Yes that info is not provided in the PDU. Infrastructure sends PDUs to LAs (MSs)

1 More thing, at the minute we are able to tag GSSI and SSI, is there a way I can Tag LAs ?

Yes. Create file "TETRA_la.txt"

' MCC;MNC;LA;LABEL
'
123;4;5;SomePlace

See "TTT_Features_and_Usage.pdf" section "TETRA Trunk Tracker created files"
And much much more...