-
Notifications
You must be signed in to change notification settings - Fork 106
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problem with the GNURadio. #36
Comments
did you try the source code from osmo-tetra? I saw that it supports encryption, but only for those who know how to find a key, Jaceck will make many fixes in his code in the future |
I'm not sure what source code you're referring too. Are you talking about tetra-rx? I just used the source code from this repo. I'll try the osmo-tetra repo code if you think it's worth a try. There were so many bugs in this repo's code, mostly simple bugs that even I could fix, but I don't think I'm going to be able to get it working. I can't see receiver1udp making a connection on port 7379 and only see the gsmtap port on 4729. |
nice, thanks for the advice man, I got it working, kind of. For some reason I couldn't compile the tetra-rx executable and was getting an error message but I just copied it from the other directory and it seems to be working, at least receiver1udp is. I'm getting loads of text through so it's definitely getting a signal (unfortunately it's encrypted). I'm not getting anything in the telive window though. Does it ignore encrypted channels entirely? |
I am getting a strange problem with the GNU-Radio when opening the telive_1ch_gr37_udp_xmlrpc_headless.py script. When running it in GNURadio (after replacing the missing blocks) I get an error message:
The strange part about it is that the file is exactly where it's supposed to be and copy/pasting the command opens up an x-terminal just fine. I've moved the folder around to different locations and tried running it again and still get the same error.
I'm not very good with all this programming stuff and I don't even know where main.cc is to try and see what's causing this problem. It seems like it should be so simple to fix but I have no idea what could be causing this issue. The
The text was updated successfully, but these errors were encountered: