Tetra decoding

[sq5bpf]

i've made a demo telive image, that can be booted from a 16GB memory stick. this way windows people won't have to use VMs (which are slow), and hopefully i will get less questions about linux basics

short description:

1. download from here:

https://drive.google.com/open?id=0B-AD504JevuWNEhBS29qbkYzTE0

you should verify that the md5 sum is 9d5e47abb8633f583198d53d60f67802

2. gunzip telive_live_2016031101.img.gz
3. dd if=telive_live_2016031101.img of=/dev/sdXXX (where /dev/sdXXX is the memory stick device).

This site has instructions on how to do steps 2 and 3 on other operating systems including Windows:

https://doc.pfsense.org/index.php/Writing_Disk_Images

4. boot from the memory stick

5. read the README_FIRST.txt file on the desktop, the telive_doc.pdf and the rest of the docs

6. configure internet access, do the steps from the README_FIRST.txt

7. the demo gnuradio-companion config is deliberatly made for very slow hardware., but it's a good idea to run volk_profile on an idle system (regardless of the hardware used)

If someone needs help with linux, then use the internet and don't ask here. there is plenty of support for linux mint on the internet.

probably this image will run in a VM too, but it's not worth it

NOTE: this image doesn't have the ACELP codec due to licensing, but a script is provided so that the user can download and compile it

 

[martufello]

Hello to all

I was just wondering if the program can be installed on a tablet ?
Which would give more mobility, and longer battery life when out of home

I'm thinking about windows surface, or acer, asus ...etc

Thanks

I have a 2in1 Lenovo Yoga 2 with a bootable USB and is working fine.
While traveling in the car I'm using this PC in tablet mode...

 

[phk]

DMO

Thanks sq5bpf for the effort you have put into this project. Much appreciated!

A question regarding DMO. I've been trying to listen and record my own DMO calls. I see the transmissions, but telive won't detect and play them.

Do telive support DMO calls?

//phk

 

[FR3500]

Ok thanks to both;
That's good news indeed;
I will soon try it, cause i use a laptop which has only more than 1 hour

 

[jlxsolutions]

Thanks sq5bpf for the effort you have put into this project. Much appreciated!

A question regarding DMO. I've been trying to listen and record my own DMO calls. I see the transmissions, but telive won't detect and play them.

Do telive support DMO calls?

//phk

Telive does not support uplink or DMO hopefully it will come someday,

 

[phk]

Telive does not support uplink or DMO hopefully it will come someday,

@sq5bpf - Is there anything the community can do to help? Do you need DMO recordings/data dumps?

 

[sq5bpf]

@sq5bpf - Is there anything the community can do to help? Do you need DMO recordings/data dumps?

not yet. DMO and uplink decoding isn't in the plans right now.

the plan is to do a few bugfixes, maybe reintegrate the scanning stuff with new telive, and work on the tetra network list (the telive.xml file, btw if you know any networks which are not mentioned there, then please send me the MNCs and a short description). and after that maybe i will finally start working on version 2.0

DMO and uplink are more like v3.0

 

[FR3500]

Hi
Can you tell me how sound DMO signals ?
Is it more the buzzing sound, like repeaters, or rather the "rifle" sound that can be heard on uplink bands ?

Near where i live, i found a signal with my scanner, it seems Tetra transmitted by a mobile, as the strength is not constant; it sounds more like repeater, but not continuous ;
I couldn t try to decode it cause it's far away from home, and i would need my laptop

Thanks

 

[DualC]

Hi sq5bpf, i have trouble to write ur image to my usb memory card.

It's seems to big for my 16gb card, ... im using Windows 7, have tried with both win32imager and rufus but both say's the same.. it's to big to fit.

After i have formated it with Fat32 it 15 455 551 488 Bytes, and ur image is 15 502 147 584 Bytes, .. seems like a problem .. :/ at least fo me.

 

[sq5bpf]

Hi sq5bpf, i have trouble to write ur image to my usb memory card.

It's seems to big for my 16gb card, ... im using Windows 7, have tried with both win32imager and rufus but both say's the same.. it's to big to fit.

After i have formated it with Fat32 it 15 455 551 488 Bytes, and ur image is 15 502 147 584 Bytes, .. seems like a problem .. :/ at least fo me.

i have absolutely no expierience with the windows tools, but you are either writing the data to the partition (and not to the whole drive), or the pendrive is really smaller

if the pendrive is really smaller then this is not a problem, the data is deliberately smaller (it takes 14.5MB). unfortunately i forgot to chop off the unused data at the end. this would not be a problem if using dd under linux/unix. under windows you can just chop off a megabyte from the end and it should work

i will try post an updated image quickly.

 

[sq5bpf]

please use this link:

https://drive.google.com/file/d/0B-AD504JevuWM0tQQ1owUV9TTVE

the md5sum is b8afd972af638cbacc3671337efd6796

this image is a bit smaller, and should fit on some pendrives which advertise 16GB, but are really a bit smaller

i am moving the discussion about the bootable image to this radioreference thread:
http://forums.radioreference.com/vo...table-memory-stick-image-telive-software.html

 

[itundret]

Does someone now how to record the data from a basestation and feed the Telive later?

 

[sq5bpf]

Does someone now how to record the data from a basestation and feed the Telive later?

record the data to a file:

if you have a lot of disk space make a simple flowgraph with an osmocom source and a file sink. this will record the whole dongle bandwidth. a good rate to record is 1MHz

if you don't want the whole bandwidth, then tm /tmp/fifo*, take one of the flowgraphs that uses pipes ad run it. you will get files /tmp/fifoXXX


to play them back:

in case of the whole spectrum file: take a receiver flowgraph and instead of the osmocom source use a file source and a throttle block set to the rate that you've recorded the file with

in case of a single channel make a simple flowgraph with a file source, throttle block for 36samples/s and the desired sink (ether udp or sile sink to a pipe)



btw this is one of the reasons this software is so modular (and not in one application), you can easily modify blocks to suit your needs. and with gnuradio-companion you don't even need to know programming

 

[sq5bpf]

if you don't want the whole bandwidth, then tm /tmp/fifo*

this should of course be rm /tmp/fifo*

sorry but i can't edit my previous post

 

[sq5bpf]

new version of osmo-tetra-sq5bpf and telive v1.8 is out, please update both

osmo-tetra-sq5bpf has support for parsing D-CONNECT and D-TX COMPLETE messages

telive 1.8 tries harder to find SSIs from various messages. it will display the call identifier and [receiver] on the right of the usage identifier. there are also some fixes.

the output files are now called traffic_DATE_TIME_idxIII_callidCCC_SSI1_SSI2_SSI3.ogg

where III is the usage identifier, and CCC is the callid


please try it and report if you see a better list of the SSI numbers connected with the calls.

 

[sm0vec]

new version of osmo-tetra-sq5bpf and telive v1.8 is out, please update both

osmo-tetra-sq5bpf has support for parsing D-CONNECT and D-TX COMPLETE messages

Interesting update, but I get the same problem on two machines I've tested.

I could download and compile everything fine, but telive crashes on the first received audit, even if audio is muted (segmentation fault). I've tried to switch back to version 1.7 and that works fine, switching back to 1.8 gives same fault. I even tried to move all compiled files to the working 1.7 folder, with the same crash as result.

One machine was recently installed with version 1.7 by using the script. The other machine was older an manually installed.

I tried various things, but I'm out of ideas... so before I chase this further, I'll see if someone else report the same problem

 

[sq5bpf]

I could download and compile everything fine, but telive crashes on the first received audit, even if audio is muted (segmentation fault).

please see the documentation on how to send me a bug report (gdb telive core ; bt ; and send me the results)

 

[passie101]

Great update,

It looks like the receiver number after the call identifier is not working properly.
I monitor a 6 carrier system, and see in the "green" status windows the D-Connects from the 6 receivers RX:1 to RX:6 but the RX number after the new call identifier stays always [1]

 

[sq5bpf]

It looks like the receiver number after the call identifier is not working properly.
I monitor a 6 carrier system, and see in the "green" status windows the D-Connects from the 6 receivers RX:1 to RX:6 but the RX number after the new call identifier stays always [1]

thanks, i will look into it. it is the same here, and also some of the callid data does not time out and stays on the screen. this will be fixed in the next version

 

[sq5bpf]

telive crashes on the first received audit, even if audio is muted (segmentation fault).

thanks for the bug report. i added a small change which will hopefully fix the crash. please tell me if it solves the problem

i didn't get the crash on my system, but the fixed code is obviously bad.