rtl-sdr.com

alerosta wrote: ↑

Mon Aug 20, 2018 8:45 am

Hi, thanks for your work!

how i capture an audio sample for you of these log messages?

SSI:00 D_SDS_Data Party_SSI:000 Type:3 Protocol:Location_information SubType:Immediate_location_report_request
SSI:00 D_SDS_Data Party_SSI:000 Type:3 Protocol:Location_information SubType:Immediate_location_report_request
SSI:00 D_SDS_Data Party_SSI:000 Type:3 Protocol:Location_information SubType:Immediate_location_report_request
SSI:00 D_SDS_Data Party_SSI:000 Type:3 Protocol:Location_information SubType:Immediate_location_report_request

With sdr# the audio sample is mute, what do you need to record this? thanks in advance and sorry for my bad english!


Alessandro

This is the IQ record. of the Immediate_location_report_request
https://mega.nz/#!WB5UjSDB!TwqpEdOO_ApY ... s7WZk1DAbU

Thanks for the sample Alessandro.

This is what I see so far.

SSI:0000000 D_SDS_Data Party_SSI:0000001 Type:3 Length:52 Protocol:Location_information SubType:Long_location_report LongShapeType:Location_circle

This should have locations. I need to look into it some more.
I might need so more sample. I'll let you know.

I can show you a better way that makes IQ files smaller (or record longer for same file size.)
The plug-in needed is "IFRecorder"

After some tweaking of code this is what comes up for those PDUs.

SSI:0000000 D_SDS_Data Party_SSI:0000000 Type:3 Length:52 Protocol:Location_information SubType:Long_location_report TimeDataType:0 LongShapeType:No_shape LongVelocityType:No_velocity_information Reason_for_Sending:Response_to_an_immediate_location_request

SSI:0000000 D_SDS_Data Party_SSI:0000000 Type:3 Length:107 Protocol:Location_information SubType:Long_location_report TimeDataType:0 LongShapeType:No_shape LongVelocityType:Horizontal_velocity_and_vertical_velocity_with_uncertainty VelocityDataRaw:4 Reason_for_Sending:160

I'm sure this is correct. But I could be wrong.

The 2nd PDU here shows that is has velocity information (VelocityDataRaw:4)
This breaks down as follows:
0000000________Horizontal velocity = 0 km/h
000___________Horizontal velocity uncertainty = Less than 1,5 km/h
0 0000000_______Vertical velocity - Upwards = 0 km/h
100____________Vertical velocity accuracy = Less than 24 km/h

It also shows "Reason_for_Sending:160". 160 means that the reason is Reserved (or user defined)

Both PDUs here most likely contain type 5 elements going by UDT4 length but this doesn't contain location data.

More IQ samples would be required to see if any SDS PDUs sent carry the location data.

Ok made an error with displaying "VelocityDataRaw:4".
4 is the velocity data type. e.g. "Horizontal_velocity_and_vertical_velocity_with_uncertainty"

Now we have velocity (Is it correct?)

SSI:0000000 D_SDS_Data Party_SSI:0000000
Type:3 Length:107 Protocol:Location_information SubType:Long_location_report
TimeDataType:0 [No time data]
LongShapeType:No_shape [No GPS location data]
LongVelocityType:Horizontal_velocity_and_vertical_velocity_with_uncertainty
Type_of_additional_data:1 [User defined data]
Velocity:5.0km/h Vertical_Velocity:282.7km/h-upwards

282.7km/h upwards (78m a second climb rate) with 5km/h forward direction, is that a helicopter? Seems quick.

What do you think Alessandro.

no, is a car

In linux with gnu radio and telive there isnt speed, decode only coordinates latitude and longitude.

Thanks! if you need other sample i'm here!

Alessandro

This guide will help create more focused IQ recordings @300Kbps wide rather than at 2.4Mbps.
This has the benefit of smaller files or longer recordings.

Install the SDR# plug-in "IFRecorder" [SDRSharp.IFRecorder.dll]
- Download from here
- This install requires copying 2 .DDL files to your SDR# folder.
- Add MagicLine to "Plugins.xml" using Notepad (see 'MagicLine' below)
Start SDR# as normal

Tune to frequency (Make sure this frequency is centered in spectrum display) Use >|< to right of tuning frequency.

In SDR# set to WFM and Bandwidth to 30,000

Make sure all settings are what is used for normal TETRA operation. (But use above values)

On sidebar of SDR# there is a tab called 'IF Recorder *'
- Select '16 Bit PCM IQ'
- Select "Folder select" for file save location.
- Click 'Record'

Look at 'Write' (= File Size') in panel to monitor this size.

Capture PDUs of interest, Try and get a few. Keep size no bigger than 300MB.
If PDUs are sent infrequently, don't create a 300mb file with one event in it.

D_SDS_Data PDUs of interest:
- Protocol:Location_information SubType:Immediate_location_report_request
- Protocol:Location_information SubType:Long_location_report
- Protocol:Simple_immediate_text
- Protocol:Simple_text_msg
- Protocol:Simple_location_system
- Protocol:Text_Messaging

This recorded file is saved in your set "Folder select" folder under "IF" folder.(e.g. 22-31-06_435112kHz.wav)
Do not rename file as it is important in proper playback with SDR#.

Use ZIP to compress WAV file to smaller size. (7zip is best and can halve file size, but is slower to compress)

Upload file to online file host.

Advanced
Trimming of IQ recordings is possible using a free audio editor called Audacity.
Using SDR# WAVPlayer plug-in It is possible to find events on the timeline. Make note of the times and use below.
This is handy if you have a big file and only a few events in it. (Don't send me massive files with 1 or 2 events. Trim them)

Install then run Audacity
Drag and Drop the IQ file recorded with "IFRecorder" in to Audacity.
You will probably get a warning about import method. Choose "Read the files directly from the original" (faster).
The file should load with the correct SampleRate and bit depth. "300000" and "32-bit float"
Project Rate (Hz) on bottom left corner must be same as SampleRate (300000)
On the waveform window find the time and highlight with mouse. Click and drag.
Have a lead-in and lead-out of about 10 seconds from event.
With event highlighted select from menu File > Export Selection...
Use same file name (don't modify)
Save to different folder than original (Don't overwrite original)
Click save.
Don't add metadata. Click OK
Done. Repeat as required.

Any questions let me know.


Hi Alessandro, the more IQ samples you can provide the better.
Any of the PDUs listed above would be good, but mainly "Protocol:Location_information SubType:Long_location_report"

Hi Alessandro,

I've looked at the IQ sample you provided and adjusted the code to deal with the follow PDU:
D_SDS_Data:
Protocol: Location_information
SubType: Location_protocol_with_extension
SubTypeExt: Long_location_report

I think I now have the GPS location and I would like to confirm with you that this is correct. I just don't what to post on here directly so it protects your listening area.

Since this forum has no private messaging you could try and send me a PM over at the Radio Reference forum under the same user name.

This is the originating forum for TETRA Trunk Tracker

bonjour, je suis maxime et je suis français
je vous contact car j'utilise votre logiciel mais je remarque quelque problème

-je remarque que le logiciel fait basculé de fréquence après chaque appel et me coupe le son de sdr

-la partie lrrp ne fonctionne manifestement pas de mon coté surement un problème de configuration

pouvez-vous faire une prise en mains a distance avec teamviewer pour observer le problème en direct ?

voici mon mail [email protected]


hello, i'm maxime and i'm french
I contact you because I use your software but I notice some problem

I notice that the software switches frequency after each call and cuts me the sound of sdr

-the part lrrp obviously does not work on my side probably a problem of configuration

can you make a remote grip with teamviewer to observe the problem live?

here is my email [email protected]

I contact you because I use your software but I notice some problem

I notice that the software switches frequency after each call and cuts me the sound of sdr

Not sure I understand.
Which version. Single SDR#/Dongle or 2 x SDR#/Dongle.
TETRA Trunk Tracker follows call to VC carrier then turns up volume. It switches back to CC and lowers volume when call completes.
Are you saying, part of call is silenced before end of call?

-the part lrrp obviously does not work on my side probably a problem of configuration

You need to receive "D_SDS_Data" PDUs with "Protocol:Location_information" for this to work. Not always sent out by MS.

can you make a remote grip with teamviewer to observe the problem live?

No.

It would be better if you make a short video and upload it to file hosting site.
You can make video with free OBS Studio. Not to hard to setup and use.
You can capture desktop, part of desktop or just a window.
Use a low framerate when make video like 10fps. Don't make video file size to large.

It is in alpha stage. This means is may contain errors that may cause issues with the other programs it
works with. i.e. crashing them or itself. Although I'm not seeing this.


TETRA Demodulator plug-in has been updated by me. "Tweaked Edition (Unofficial) v1.0.0.5"
It's is required for some SDS features to work with TETRA Tunk Tracker v1.0.5. Please read text files in zip for plug-in.



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

• FIXED .NET pop-up errors. Should no longer require "TETRA popup error dismisser' is 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.
• See 'SETUP.TXT' and 'UPDATE.TXT' for more details.

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 TETRA Trunk Tracker version changes/adds and fixes some items:

• Have merged Simple[Single] and Normal[Dual] version in to one.
• Seperate output log file for all SDS_Data PDUs. (Can be disabled via commandline)
• Handling for 'Individual call' Simplex/Duplex[half] setups. [Experimental] (Can be disabled via commandline)
• 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.
• Save path for DSDPlus.LRRP. No need to copy LRRP and map data to TTT folder.
• FIXED: Some D_Setup PDUs don't have a Calling Party SSI included. Calls where not been set-up.
• See 'changelog.txt' for more details.

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

The more people that report what their OS is that they got TETRA Trunk Tracker working in, the better. I can add to list.
(Is it Windows 7,8,10 - Basic, Home, Professional, Ultimate, Enterprise - 32/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: [Not up to date with this test version]

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

It only works with the provided TETRA plug-in supplied in zip. (2018-September-11).
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.

Hopefully all goes well for you setting it up.

Download link

MD5 HASH 7fecfe8ea909ddf928c26fbaccbd2757