-
Notifications
You must be signed in to change notification settings - Fork 30
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
Server always returning -2 #3
Comments
Hi I found this https://github.com/gnss-sdr/gnss-sdr/tree/master/src/core/libs/supl Which looks like an updated set of files, but if I drop them in and compile them I just get segmentation fault Shame, looked a really useful tool |
I use gnss-sdr every day, that bit should compile |
I got it (eventually) to compile, I had to install asn1c libgnutls28-dev libssl-dev and edit this line in the make file
...but even after that I just get "segmentation fault" when I run it. So I'm missing something, my coding skills on Linux are not super so it may just be me. It's a bit beyond my ability to track down what's wrong and get it working unfortunately, I just thought it was worth posting about the possibility of dragging over what looks like a newer set of files. Perhaps someone with more "ninja skills" can look at it |
Oh, that's progress anyway. I've never actually used SUPL in gnss-sdr because I always get to process datasets offline and SUPL is only for real time. Anyway, I did manage to use Google's own SUPL client in Java. That's somewhere here on GitHub |
This code would need some care and love, but anyway it should compile and run without adding gnutls-openssl or something to supl-client when using pre-compiled asn1 files. Newer distribution provided asn1c compiler may generate code that the tool is not prepared for. Only option -t 0 and 3 actually work with supl.google.com, for others the server just closes the connection (or something). I committed some small changes so that it should compile, even though it will throw some warnings that should be fixed (but as they come from the asn1c generated files it is a bigger task). At least this worked on my Ubuntu 20.10 (with all required -dev packages installed)
If you do get some weird errors, one option is to turn on all -enable-*-debug options in configure and then make clean all. Now it should spit out a ton of asn1 related en/decoding stuff, searching there for Fail would indicate where the asn1c en/decodig went wrong and maybe that would give some hints what to fix or change. Hope this helps ;-) |
Wow, that's great work! I still get an error when I follow your procedure mind you, so not entirely sure where the bug is there :-(
MCC = 234
But this at comes back with a result :
|
Buidling with
That is, the value 713492 (i.e. 0xAE314) for CI is out of range. Nothing much to do here as in
But running it as |
Well don't I feel stupid.. Yes it's on a LTE cell of course! Doh! Thanks for your patience |
No worries ;-) Closing the ticket. |
Have the same problem. Is it fixed or not? |
Hey, I've compiled and run the program with no errors, but the program seems to always returning -2.
This is the setups I have tried so far:
I've set up a currect location with the SUPL_FAKE_POS env, and took the mcc,mnc,lat,cid from my modem which still returned -2.
I tried to play with the configuration in your example which result with the same "SUPL protocol error -2"
It seems that the problem is in supl_ulp_encode fucntion at the supl.c file.
the function at uper_encode_to_buffer returns -1. which in the end result in E_SUPL_ENCODE_START
(which is the -2 error)
The text was updated successfully, but these errors were encountered: