Comments (5)
Hi Jan, you are right. The fixed satellites are the initial ones searched
by the acquisition process. If the acquisition fails, then the satellite is
tried to be acquired once again, but if this second acquistion (named
reacquisition) falis again then the satellite is discarded and the channel
try to acquire the following PRN in the queue.
I don't know if this process will be changed in future versions of channel,
but feel free to implement your own state machine and share it with the
gnss-sdr community.
Hope this helps
Regards
Luis
2016-04-19 16:15 GMT+02:00 JJZim [email protected]:
Okay, so after a bit of additional investigation, I think my problem or
understanding of how to use fixed satellites for each channel is different
to how it is actually implemented in gnss-sdr.For me it would be greate to fix all channels to certain satellites (each
channel exactly to one) and let them do their work (even if this means that
they fail during acquisition all the time).However, the fixed sattelites for now are only "hints" for the channels
and maybe (after a acquisition fail for example) totally different
satellites are assigned to each channel.
Did I get it right? And if so, is this the intention of the implementation
and will not be changed in the future?Regards,
Janโ
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
#26 (comment)
from gnss-sdr.
I think I've worked out a patch for this problem.
How can I submit it to the project?
from gnss-sdr.
Hi,
you can send your patch to this mailing list or make a pull-request from
your github account. All these options are explained in our How to
contribute to the source code page
http://gnss-sdr.org/documentation/how-contribute-source-code
Hope this helps
Regards
Luis
2016-03-18 12:26 GMT+01:00 JJZim [email protected]:
I think I've worked out a patch for this problem.
How can I submit it to the project?โ
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#26 (comment)
from gnss-sdr.
Hey,
Thanks for your reply.
After some more detailed research on the source code (I'm working on master branch, is this boy the way a bad idea?) I came to the conclusion, that the Channel Statemachine as well as the message passing protocol (if you can call it one) are not really made to support channels with fixed satellites. I although implemented a solution of which I think it will work (at least for my constellation). However, as I am not really into details of the whole implementation I think that this fix maybe violates dependencies.
Was there any progress regarding that special feature since the last commit to the master branch? It's very hard to search through the commits of the next branch.
Thanks in advance
from gnss-sdr.
Okay, so after a bit of additional investigation, I think my problem or understanding of how to use fixed satellites for each channel is different to how it is actually implemented in gnss-sdr.
For me it would be greate to fix all channels to certain satellites (each channel exactly to one) and let them do their work (even if this means that they fail during acquisition all the time).
However, the fixed sattelites for now are only "hints" for the channels and maybe (after a acquisition fail for example) totally different satellites are assigned to each channel.
Did I get it right? And if so, is this the intention of the implementation and will not be changed in the future?
Regards,
Jan
from gnss-sdr.
Related Issues (20)
- error: call to non-โconstexprโ function HOT 1
- Observables doesnt give solution, but messages income HOT 13
- cross compiling user name and password
- trivial documentation correction for FIFO
- E5a Adquisition block is not dumping raw files HOT 2
- Segmentation fault using plutoSDR on Ubuntu LTS 22.04 HOT 3
- Fifo with rtl HOT 1
- The results of decoding navigation message is erro
- Impossible to build on MAC Sonoma 14.1.1 HOT 8
- 'msg_connect' error during make
- build of v0.0.19 fails with gnuradio v3.10.9.2 HOT 3
- E6 HAS decodeing
- HAS message ID reporting in stdout HOT 1
- Segmentation Fault using PlutoSDR on Ubuntu 20.04.6 HOT 2
- Build fail with glog-0.7.0 HOT 2
- Build error in uhd_signal_source.cc.o HOT 4
- Cannot fix the integer ambiguity for zero-baseline RTK with BDS B1I measurements
- Not saving Acq files for E5a signals HOT 1
- Initial values for Pseudorange
- GNSS-SDR on RHEL HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. ๐๐๐
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google โค๏ธ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from gnss-sdr.