Tetra decoding

[sq5bpf]

I think my question has been overlooked due to the fact that the first posts must be approved by an admin.

sometimes new posts appear not as the last ones (which is probably due to approval), and it is easy to overlook these

regarding your original question about merging the changes back to the main tree, i don't think that tree has any development now (apart from a change to add gr 3.7 support). some functionality can be merged (various decoders, SDS etc), some is a horrible hack they would probably like to keep out of their tree (like communication with telive). i don't see any efforts to merge from the other osmo-tetra trees out there too

this is often the case. this is just too expensive for most private users (which pay with their money), so only the goverment uses it (guess who pays here). people use DMR, and even there they don't use most of the functionality

 

[lx3gr]

regarding your original question about merging the changes back to the main tree, i don't think that tree has any development now (apart from a change to add gr 3.7 support). some functionality can be merged (various decoders, SDS etc), some is a horrible hack they would probably like to keep out of their tree (like communication with telive). i don't see any efforts to merge from the other osmo-tetra trees out there too

You're right, there haven't been many commits in the osmo-tetra tree, but what about the libosmocore?

73, Gilles

 

[ET-NL]

I'm trying to get locations in Google earth working.

What I have done,
I installed a webserver on my Telive machine,
Edited rxx so the tetra1.kml file is placed in the web root.

So far so good, if I open the website form a remote computer, I can upload the tetra1.kml in a google maps session (and I see markers on the map), so this works.
After that I edited the example_google_earth.kml, the line file://tetra/log/tetra1.kml is replaced by http://webserver_ip/tetra1.kml.
When I try to use this file in google maps I get an error, network link in KML-file is not accessible or is not a KML file. (The webserver on my telive machine is only accessible via my LAN, can that be the problem, must it be directly accessible by the google servers via the internet ???)

Anybody who can help me out with this.

Elmar

 

[sq5bpf]

So far so good, if I open the website form a remote computer, I can upload the tetra1.kml in a google maps session (and I see markers on the map), so this works.
After that I edited the example_google_earth.kml, the line file://tetra/log/tetra1.kml is replaced by http://webserver_ip/tetra1.kml.
When I try to use this file in google maps I get an error, network link in KML-file is not accessible or is not a KML file. (The webserver on my telive machine is only accessible via my LAN, can that be the problem, must it be directly accessible by the google servers via the internet ???)

Anybody who can help me out with this.

please look at the web server logs, maybe you have 404s (missspelled file name?). maybe you're not getting any requests at all? (missspelled host?)

also please try to put the example_google_earth.kml on the wer server too, maybe google earth has some sort of same origin policy

 

[jlxsolutions]

I'm trying to get locations in Google earth working.

What I have done,
I installed a webserver on my Telive machine,
Edited rxx so the tetra1.kml file is placed in the web root.

So far so good, if I open the website form a remote computer, I can upload the tetra1.kml in a google maps session (and I see markers on the map), so this works.
After that I edited the example_google_earth.kml, the line file://tetra/log/tetra1.kml is replaced by http://webserver_ip/tetra1.kml.
When I try to use this file in google maps I get an error, network link in KML-file is not accessible or is not a KML file. (The webserver on my telive machine is only accessible via my LAN, can that be the problem, must it be directly accessible by the google servers via the internet ???)

Anybody who can help me out with this.

Elmar

First check you can acces the file(s) via your webbrowser ie http://192.168.0.120/log/
then try this -->
What i have done is edit the example_google_earth.kml file to point to my on Lan webserver like this
and copy it to desktop and open it as a file in google earth

------------------------------------------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8"?>
<kml xmlns="http://earth.google.com/kml/2.1">
<Document>
<NetworkLink>
<Link>
<href>http://192.168.0.120//log/tetra1.kml</href>
<refreshMode>onInterval</refreshMode>
<refreshInterval>2</refreshInterval>
</Link>
<name>Tetra RX</name>
<visibility>1</visibility>
</NetworkLink>
</Document>
</kml>
-----------------------------------------------------------------------------

 

[ET-NL]

When I open the tetra1.kml directly from my LAN webserver in google it works, as soon as I try to use the auto refresh kml with the link to the same tetra1.kml it fails.
I used the example from JXSolutions and edited the IP but no go "the networklink in the KML-File is not accessible".
I placed a test tetra1.kml on my public website and edited the auto refresh kml to this public website and then it works (autorefresh.kml on desktop tetra1.kml on public home page).
Looks like some troubles with my webserver, but I can open tetra1.kml from my remote workstation but not with the auto refresh kml

There are no error's or access denied in the apatche log files.

Elmar

 

[sq5bpf]

When I open the tetra1.kml directly from my LAN webserver in google it works, as soon as I try to use the auto refresh kml with the link to the same tetra1.kml it fails.
I used the example from JXSolutions and edited the IP but no go "the networklink in the KML-File is not accessible".
I placed a test tetra1.kml on my public website and edited the auto refresh kml to this public website and then it works (autorefresh.kml on desktop tetra1.kml on public home page).
Looks like some troubles with my webserver, but I can open tetra1.kml from my remote workstation but not with the auto refresh kml

maybe it doesn't like to have an IP in the uri?

i'd try to give your host a name, either via dns or via /etc/hosts, and then use this name in the autorefresh.kml , maybe this will help.

also try to put the autorefresh.kml on the same web server, and give google earth it's url, this might solve some same origin policy problems

There are no error's or access denied in the apatche log files.

but do you see google earth reaching for the file in access.log?

 

[jlxsolutions]

sounds more like the router is not letting google earth trough for some reason.

 

[sq5bpf]

sounds more like the router is not letting google earth trough for some reason.

no, because he could access the kml file directly from google earth

this is why i suspect something like "same origin policy", this is why putting the autorefreshing kml file on the web server might solve the problem.

unfortunately i can't test it at this moment

 

[ET-NL]

I can try the hostname as url option.
Same origin is not a problem, when I put the autrefresh on my desktop and tetra1 on my public home side it works.
When I look At the access.log i see opening the autrefresh. No entries for the tetra1.kml

I will start trying from the beginning, with the original files and from my Telive host. And step by step move to the finish and find where it stops working.
I hope to find some time tomorow, after that I go offline and find me some time on the beach (and my boat).

Elmar

 

[sameehosen]

Sorry I Many Questions
I have read the documents and tried but I missing
I hope you writing the appropriate instruction to add tetra1.kml View
What is the location information that must be provided
Please include a case in point. Thank you

 

[tiptappers]

Hello friends.

First of all, lovely software you have made sq5bpf, thank you.

I'm having a slight dilemma on which frequencies to listen to.

I have gone through the designated TETRA frequencies in the capital of my country and noted their information.

I theoretically have enough hardware and SDR equipment to listen to all of those, but I think that might be unnecessary since my 6 channel setup picked up quite alot of duplicates(recorded audio).

Also, sq5bpf, what is your preferred method of recieving logs?


391.0000MHz - CC 1 - LA 23
391.1250MHz - CC 1 - LA 3
391.2250MHz - CC 1 - LA 22
391.3000MHz - CC 1 - LA 1 (identifies as 391.4000MHz)
391.3500MHz - CC 1 - LA 83
391.4000MHz - CC 1 - LA 1
391.5500MHz - CC 1 - LA 5 (identifies as 391.1250MHz)
391.6000MHz - CC 1 - LA 19
391.6250MHz - CC 1 - LA 3 (identifies as 391.1250MHz)
391.7000MHz - CC 1 - LA 19 (identifies as 391.6000MHz)
391.7250MHZ - CC 1 - LA 1 (identifies as 392.0250MHz)
391.7750MHz - CC 1 - LA 22 (identifies as 391.2250MHz)
391.8500MHz - CC 1 - LA 13 (heaps of weird SDS data)
391.9250MHz - CC 1 - LA 3 (identifies as 391.1250MHz)
392.0250MHz - CC 1 - LA 1
392.1500MHz - CC 1 - LA 13 (identifies as 391.8500MHz)
392.2000MHz - CC 1 - LA 8 (identifies as 392.4500MHz)
392.3000MHz - CC 1 - LA 20
392.3750MHz - CC 1 - LA 76
392.4000MHz - CC 1 - LA 20 (identifies as 392.3000MHz)
392.4750MHz - CC 1 - LA 21
392.5250MHz - CC 1 - LA 57 (identifies as 392.9500MHz)
392.5500MHz - CC 1 - LA 21
392.6250MHz - CC 1 - LA 21 (identifies as 392.4750MHz)
392.6500MHz - CC 1 - LA 21 (identifies as 392.5500MHz)
392.7250MHz - CC 1 - LA 17 (identifies as 392.8750MHz)
392.7500MHz - CC 1 - LA 2
392.8500MHz - CC 1 - LA 2 (identifies as 392.7500MHz)
392.8750MHz - CC 1 - LA 17
392.9250MHz - CC 1 - LA 23 (identifies as 391.000MHz)
392.9500MHz - CC 1 - LA 57
392.9750MHz - CC 1 - LA 59

Regards,
Tip Tappers

 

[jlxsolutions]

CQ sq5bpf
While it might be kinda inapproriate to ask.
i am wondering what kind of ETA window are we looking at before the next major version of Telive is out?
That would follow the Call ID and not ssi?
being summer and busy times for most im not expecting it any time soon.
but some words of comfort would be nice.
hi
73 de oh2eko

 

[sq5bpf]

I have gone through the designated TETRA frequencies in the capital of my country and noted their information.

I theoretically have enough hardware and SDR equipment to listen to all of those, but I think that might be unnecessary since my 6 channel setup picked up quite alot of duplicates(recorded audio).

i'd listen to as much as you can on your hardware, but feed each LA into its own telive instance.
so for example feed this into one telive instance:
392.3000MHz - CC 1 - LA 20 (this is the control channel)
392.4000MHz - CC 1 - LA 20 (identifies as 392.3000MHz, because that is the control channel)

you should not get duplicates in recorded audio this way. use the lock feature, so that you don't listen to multiple calls at the same time, when using multiple telive instances

Also, sq5bpf, what is your preferred method of recieving logs?

via email

btw this looks interesting: 391.8500MHz - CC 1 - LA 13 (heaps of weird SDS data)
i like to get logs with SDS

 

[sq5bpf]

i am wondering what kind of ETA window are we looking at before the next major version of Telive is out?
That would follow the Call ID and not ssi?

i still want to get a few features out before doing the next major version (iron out a few bugs, maybe add simple scanning support, work on the installer script, update the documentation). i want to implement everything in this version, before i move on to the next.

also i wont be able to do any serious programming before november, only quick hacks/bugfixes.

i can't give you an eta, but it will probably take about 1/2 year after i start (i'm writing this in my spare time)

 

[jlxsolutions]

your answer is satisfactory sir and thank you for putting time on this when you can

 

[sameehosen]

Hello my friends
1. In telive tried to use the screen lock feature (lock = 0) and experimented with all possible keys did not work this feature
2. Is there an update to assemble ETSI EN 300 395-2 V1.3.1 another new and what is the way to get it?
3-What are the orders that should be added? Wayne added? Tetra1.kml to activate the feature writing I ask you a case in point

 

[tiptappers]

Hello my friends
1. In telive tried to use the screen lock feature (lock = 0) and experimented with all possible keys did not work this feature
2. Is there an update to assemble ETSI EN 300 395-2 V1.3.1 another new and what is the way to get it?
3-What are the orders that should be added? Wayne added? Tetra1.kml to activate the feature writing I ask you a case in point

1. You need to uncomment the TETRA_LOCK_FILE line in the rxx script.

 

[skittles23]

hey,

Is it not possible that anyone, who have an working vm, would copy and share it?

installed it now 6-7 times and it doesnt work.

using virtual box, vmware and mac... stick is nooelec r820t2.... thank you


y

 

[sq5bpf]

Is it not possible that anyone, who have an working vm, would copy and share it?

please read the docs or the comments in this thread why this would not be a great idea

installed it now 6-7 times and it doesnt work.

using virtual box, vmware and mac... stick is nooelec r820t2.... thank you

it is very simple:
install debian 8.1
run the provided installer script (look in comments in this thread on how to use the install script)