<div dir="ltr">You should also be able to provide a startup message for RTKLIB to send to the receiver. I use it with str2str and if I recall rtkrcv / RKNAVI support it as well. For ublox it looks like:<div><br></div><div>
<div>!UBX CFG-RATE 1000 1 1 # set update period in milliseconds</div><div>!UBX CFG-MSG 2 17 0 0 0 1 # RXM RAW - required for rtklib</div><div>!UBX CFG-MSG 2 16 0 0 0 1 # RXM SFRB - recommended for rtklib</div><div>
!UBX CFG-MSG 240 0 0 0 0 1 # NMEA GGA</div><div>!UBX CFG-MSG 240 1 0 0 0 0 # NMEA GLL</div><div>!UBX CFG-MSG 240 2 0 0 0 0 # NMEA GSA</div><div>!UBX CFG-MSG 240 3 0 0 0 0 # NMEA GSV </div><div>!UBX CFG-MSG 240 4 0 0 0 1 # NMEA RMC</div>
<div>!UBX CFG-MSG 240 5 0 0 0 0 # NMEA VTG</div><div>!UBX CFG-MSG 240 8 0 0 0 0 # NMEA ZDA</div></div><div><br></div><div>The first two numbers of each CFG-MSG line define the message, and the following 4 0s and 1s turn that message on and off for different interfaces (usb, serial, etc)</div>
<div><br></div><div>-Josh</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Apr 30, 2014 at 1:46 PM, Danny Miller <span dir="ltr"><<a href="mailto:dannym@austin.rr.com" target="_blank">dannym@austin.rr.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Be sure to increase your serial port baud rate.<br>
<br>
There's MUCH longer packets, and more of them, than data than NMEA fixes. In my experience if there's too much data it just overruns the buffer and data gets lost. The link is full of errors and the fix disappears.<br>
<br>
It may appear fine early on after power-up. But as more satellites get added, the data gets longer and longer, and you may oddly lose the fix as it becomes "good".<br>
<br>
You can also disable data you don't need to keep the link bandwidth down.<br>
<br>
The graphical interface of U-Center allows you to turn on/off msg types for each port. It'll be saved if you have a battery on the GPS, which you should to maintain the RTC.<span class="HOEnZb"><font color="#888888"><br>
<br>
Danny</font></span><div class="HOEnZb"><div class="h5"><br>
<br>
On 4/30/2014 12:16 PM, Scott Harrison wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Leor,<br>
<br>
You have to go into U-Center and enter the following custom message:<br>
<br>
to enable RXM-RAW<br>
<br>
b5 62 09 01 10 00 c8 16 00 00 00 00 00 00 97 69 21 00 00 00 02 10 2b 22<br>
<br>
to enable RXM-SFRB<br>
<br>
b5 62 09 01 10 00 0c 19 00 00 00 00 00 00 83 69 21 00 00 00 02 11 5f f0<br>
<br>
This will turn on the raw data you need, but it is stored in RAM so<br>
you will need to resend the codes every time you power up.<br>
<br>
Also, set your type to PPP and then you should start to see sub-meter<br>
accuracy with RTKLib.<br>
<br>
see <a href="http://wiki.openstreetmap.org/wiki/RTKLIB" target="_blank">http://wiki.openstreetmap.org/<u></u>wiki/RTKLIB</a><br>
<br>
<br>
Scott<br>
<br>
On Wed, Apr 30, 2014 at 7:56 AM, vbenso <<a href="mailto:vbenso@gmail.com" target="_blank">vbenso@gmail.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Leor,<br>
<br>
It's been a long time since I don't touch my GPS hardware, so I could be<br>
wrong. That being said.<br>
As far as I remember, rtklib needs more information than just UBX-RXM-RAW in<br>
order to obtain an accurate fix. The neo6m should send another message<br>
(maybe RXM-SFRB?) that I wasn't able to get from the receiver.<br>
I could get ordinary gps precision in static and single modes of rtklib.<br>
Good luck, and in case of any development let me know.<br>
<br>
<br>
Victor A. P. Benso<br>
Sementes Benso<br>
Major Vieira - SC<br>
<a href="tel:%2847%29%209922-9599" value="+14799229599" target="_blank">(47) 9922-9599</a><br>
(47) 3655-1192<br>
<br>
<br>
On Mon, Apr 28, 2014 at 4:49 PM, leor [via Open Source GPS-related<br>
discussion and support] <[hidden email]> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I got 2 CN-06 (neo6m) recievers to output into RTKlib both over serial<br>
COM. Problem is that I have not been able to get a fix and always get a<br>
single status. Also whenever I choose static it seems to change everytime I<br>
start it. Using dgps and kinematic gives me an accuraccy of around 50m. I<br>
have tested this indoors and managed to get RAW data. Any idea how it would<br>
perform outdoors? I am trying to collect data to creat GCP for use in ortho<br>
correction<br>
[IMG]<a href="http://i.imgur.com/kj3Z5IV.jpg%5B/IMG%5D" target="_blank">http://i.imgur.com/<u></u>kj3Z5IV.jpg[/IMG]</a><br>
<br>
<br>
Great info you guys have. I got it to work but I am not sure what kind of<br>
accuracy I will be getting<br>
<br>
______________________________<u></u>__<br>
If you reply to this email, your message will be added to the discussion<br>
below:<br>
<br>
<a href="http://open-source-gps-related-discussion-and-support.1099874.n2.nabble.com/Raw-Data-from-NEO-6M-tp7572786p7572854.html" target="_blank">http://open-source-gps-<u></u>related-discussion-and-<u></u>support.1099874.n2.nabble.com/<u></u>Raw-Data-from-NEO-6M-<u></u>tp7572786p7572854.html</a><br>
To unsubscribe from Raw Data from NEO-6M, click here.<br>
NAML<br>
</blockquote>
<br>
<br>
______________________________<u></u>__<br>
View this message in context: Re: Raw Data from NEO-6M<br>
Sent from the Open Source GPS-related discussion and support mailing list<br>
archive at Nabble.com.<br>
<br>
______________________________<u></u>_________________<br>
This message is sent to you from <a href="mailto:FOSS-GPS@lists.osgeo.org" target="_blank">FOSS-GPS@lists.osgeo.org</a> mailing list.<br>
Visit <a href="http://lists.osgeo.org/mailman/listinfo/foss-gps" target="_blank">http://lists.osgeo.org/<u></u>mailman/listinfo/foss-gps</a> to manage your<br>
subscription<br>
For more information, check <a href="http://wiki.osgeo.org/wiki/FOSS-GPS" target="_blank">http://wiki.osgeo.org/wiki/<u></u>FOSS-GPS</a><br>
</blockquote>
______________________________<u></u>_________________<br>
This message is sent to you from <a href="mailto:FOSS-GPS@lists.osgeo.org" target="_blank">FOSS-GPS@lists.osgeo.org</a> mailing list.<br>
Visit <a href="http://lists.osgeo.org/mailman/listinfo/foss-gps" target="_blank">http://lists.osgeo.org/<u></u>mailman/listinfo/foss-gps</a> to manage your subscription<br>
For more information, check <a href="http://wiki.osgeo.org/wiki/FOSS-GPS" target="_blank">http://wiki.osgeo.org/wiki/<u></u>FOSS-GPS</a><br>
<br>
</blockquote>
<br>
______________________________<u></u>_________________<br>
This message is sent to you from <a href="mailto:FOSS-GPS@lists.osgeo.org" target="_blank">FOSS-GPS@lists.osgeo.org</a> mailing list.<br>
Visit <a href="http://lists.osgeo.org/mailman/listinfo/foss-gps" target="_blank">http://lists.osgeo.org/<u></u>mailman/listinfo/foss-gps</a> to manage your subscription<br>
For more information, check <a href="http://wiki.osgeo.org/wiki/FOSS-GPS" target="_blank">http://wiki.osgeo.org/wiki/<u></u>FOSS-GPS</a><br>
</div></div></blockquote></div><br></div>