Tetra decoding
- Thread starter sq5bpf
- Start date
-
- Tags
- tetra decode
- Status
Hi hu. There are many reasons for the audio cut amid a transmission , you must first be sure to have a good level RF signal , second, that the waveform is well centered with two symmetrical sides in the graph , including the power of the CPU you 're using can make the audio is cut. In my case, I have a very strong signal and I dim it a little.
By the other hand, since the last uptade I´m still without error telive crash. I'm runing in VMware Ubuntu 12, 32bit. Still catching SDS data
By the other hand, since the last uptade I´m still without error telive crash. I'm runing in VMware Ubuntu 12, 32bit. Still catching SDS data
Telive in Wmware
Osmo -tetra needs a lot of memory to run in Wmware . Osmo-tetra can't work with funcube with 1GB memory but run with 4GB and 4 virtuals CPU in wmware settings
Even with 4GB memory in virtual memory , the Osmo-tetra diplay is loosing frames . (not on the same PC in dual boot)
the best use is dual boot . I m running telive with an Dell inspiron 5 YO old and 1GB RAM . It is working fine
To reduce CPU usage you can redirect script on /dev/null : no display but good audio
Osmo -tetra needs a lot of memory to run in Wmware . Osmo-tetra can't work with funcube with 1GB memory but run with 4GB and 4 virtuals CPU in wmware settings
Even with 4GB memory in virtual memory , the Osmo-tetra diplay is loosing frames . (not on the same PC in dual boot)
the best use is dual boot . I m running telive with an Dell inspiron 5 YO old and 1GB RAM . It is working fine
To reduce CPU usage you can redirect script on /dev/null : no display but good audio
my computer is 2GiB,Pentium(R) Dual-Core CPU E5500 @ 2.80GHz × 2
Kali Linux 1.0.6 32-bit Linux 3.12-kali1-686-pae
signal is very strong and symmetrical.
Help with RTL-SDR script
Hello. Hopefully you can help. Using a clean install ofUbuntu 14.04 64bit. I tried to run Marcus Leech's install script. After about 1 minute I fail at the GNU radio installation stage. I ran the command with -v at the end and i got :-
Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependancies.
libcheese-gtk23 : Depends: libclutter-gtk-1.0-0 (>=0.91.8) but it is not going to be installed
Depends: libcogl15 (>= 1.15.8) but it is not going to be installed
libcheese7 : Depends: libclutter-gst-2.0-0 (>= 0.10.0) but it is not going to be installed
Depends: gstreamer1.0-clutter but it is not going to be installed
libclutter-1.0-0
epends: libcogl-pango15 (>= 1.15.8) but it is not going to be installed
Depends: libcogl15 (>= 1.15.8) but it is not going to be installed
E: Error pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
Failed to find just-installed command 'git' after pre-requisite installation.
This very likely indicates that the pre-requisite installation failed to install one or more critical pre-requisites for GNU Radio/UHD
Any help would be appreciated. I really want to get this to work. Thanks very much. AJ
Hello. Hopefully you can help. Using a clean install ofUbuntu 14.04 64bit. I tried to run Marcus Leech's install script. After about 1 minute I fail at the GNU radio installation stage. I ran the command with -v at the end and i got :-
Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependancies.
libcheese-gtk23 : Depends: libclutter-gtk-1.0-0 (>=0.91.8) but it is not going to be installed
Depends: libcogl15 (>= 1.15.8) but it is not going to be installed
libcheese7 : Depends: libclutter-gst-2.0-0 (>= 0.10.0) but it is not going to be installed
Depends: gstreamer1.0-clutter but it is not going to be installed
libclutter-1.0-0
epends: libcogl-pango15 (>= 1.15.8) but it is not going to be installedDepends: libcogl15 (>= 1.15.8) but it is not going to be installed
E: Error pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
Failed to find just-installed command 'git' after pre-requisite installation.
This very likely indicates that the pre-requisite installation failed to install one or more critical pre-requisites for GNU Radio/UHD
Any help would be appreciated. I really want to get this to work. Thanks very much. AJ
try the distribution recommended in the telive documentation
i've pushed a few minor changes to telive: fix ncurses crash, disable KML export by default.
if you want to reenable KML export, then please uncomment the relevant ones in rxx. KML exporting was causing problems, and this is some bug which i can't resolve (in case anyone is interested: this is very simple code, i have a linked list with locations which sometimes gets corrupted, and absolutely i have no idea why, probably something is corrupting the heap)
if you want to reenable KML export, then please uncomment the relevant ones in rxx. KML exporting was causing problems, and this is some bug which i can't resolve (in case anyone is interested: this is very simple code, i have a linked list with locations which sometimes gets corrupted, and absolutely i have no idea why, probably something is corrupting the heap)
SSIs
Quick Question to anyone who can help, well not so much help but explain something.
Last night when I was running this I was filling in the ssi_descriptions, went well, I am able to add say '104555 Romeo 15' I was basically listening out for call-signs then adding it to the SSI Descriptions', but tonight when I am running this, their callsign seems to be Romeo 42, my question is... Is the SSI the ID of the Radio meaning that the SSI I seen last night is still the same radio I am seeing tonight or do the SSIs change.
I really hope this makes sense.
Ta!
Quick Question to anyone who can help, well not so much help but explain something.
Last night when I was running this I was filling in the ssi_descriptions, went well, I am able to add say '104555 Romeo 15' I was basically listening out for call-signs then adding it to the SSI Descriptions', but tonight when I am running this, their callsign seems to be Romeo 42, my question is... Is the SSI the ID of the Radio meaning that the SSI I seen last night is still the same radio I am seeing tonight or do the SSIs change.
I really hope this makes sense.
Ta!
the ssi is the id of the radio. so if different radios are dispatched to different people on every shift the ssis can change. maybe these radios are mounted in cars, and people get different cars for every shift. who knows.
but most probably some of the ssis stay the same. this will be dispatchers and other people important enough to have their own radio.
depends on the network you have.
osmo-tetra-sq5bpf communicates with telive via udp (but currently it is hardwired to send to localhost, but this can be easily changed). if you have a low latency network with no packet loss, then you could use this transport.
if you just want to have the dongle in a remote place, then use rtl_tcp or borip, and stream the data to your local gnuradio. there are probably lots of descriptions on the internet how to do this
a new version of telive is out.
this version should not crash with kml export (and kml export is enabled by default again).
it is also possible to change some internal timeout parameters, see the rxx script for a short description (RTFS for further info). this is only for people who know what they are doing, if you don't know what it's for then dont touch it
as usual please report bugs, crashes, interesting telive.log etc
this version should not crash with kml export (and kml export is enabled by default again).
it is also possible to change some internal timeout parameters, see the rxx script for a short description (RTFS for further info). this is only for people who know what they are doing, if you don't know what it's for then dont touch it
as usual please report bugs, crashes, interesting telive.log etc
ET-NL
Member
Thanks for all the hard work.
I will replace Telive today and will try this new version.
I will replace Telive today and will try this new version.
ok, i will implement this
a new version of osmo-tetra-sq5bpf is out (please also make sure that you have the newest telive)
this one parses the D-RELEASE message better, and implements SDS-TL header parsing (instead of just assuming that its 2 bytes long). thanks to SM0VEC for the bug report!
thanks to SDS-TL parsing SDS which were previously undecoded are supported now. this is a really big improvement, and i would urge everyone to update.
as usual please send me interesting logs and bug reports. i am especially interested in NMEA messages.
also if anyone knows how RTCM SC-104 location messages are coded, then please send me the info.
this one parses the D-RELEASE message better, and implements SDS-TL header parsing (instead of just assuming that its 2 bytes long). thanks to SM0VEC for the bug report!
thanks to SDS-TL parsing SDS which were previously undecoded are supported now. this is a really big improvement, and i would urge everyone to update.
as usual please send me interesting logs and bug reports. i am especially interested in NMEA messages.
also if anyone knows how RTCM SC-104 location messages are coded, then please send me the info.
SDS
I get a lot of SDS Messages, should these not be decoding ?, have I set my telive up wrong womewhere ?
20150314 20:26:58 FUNC:SDS [01001111100010011110101010001000011101110011111110101100100101]
20150314 20:26:58 FUNC:SDSDEC [CPTI:2 CalledSSI:5443919 CallingSSI:2599457 CallingEXT:14483122 UserData2: 0x74 0x30 0x44 0x69] RX:2
20150314 20:27:22 FUNC:SDS [01001111001000110011010101001011000001011001101100011010101011]
I get a lot of SDS Messages, should these not be decoding ?, have I set my telive up wrong womewhere ?
20150314 20:26:58 FUNC:SDS [01001111100010011110101010001000011101110011111110101100100101]
20150314 20:26:58 FUNC:SDSDEC [CPTI:2 CalledSSI:5443919 CallingSSI:2599457 CallingEXT:14483122 UserData2: 0x74 0x30 0x44 0x69] RX:2
20150314 20:27:22 FUNC:SDS [01001111001000110011010101001011000001011001101100011010101011]
- Status