[FOSS-GPS] Configuring a NV08C for rtklib

[Fred Labrosse]

hi Artyom,

Thank you for all that.  See my answers below.

> On 24 Sep 2015, at 07:06, Artyom G <gnsssdr at gmail.com> wrote:
> 
> Hi Fred,
> 
> USB port can output BINR data too. You can use "BM control" programm ( http://navis.ru/assets/images/prog_ob/BM_Ctrl_V0430.zip ) to switch from NMEA to BINR.

Yes, we have tried that but this seems to be reset when the device is restarted, so does not help.

> Or you can find in the documentation special command that changes NMEA to BINR and send them yourself.

That is indeed my understanding, but so far I have not found what to send and how to send it!

We tried a few things like sending proprietary NMEA sentences, starting in $PORZA for example.  However, when trying that from rtknavi nothing was received from the receiver and sending that in minicom seem to produce nothing.

We have tried to send that on the USB port (still configured for NMEA) and the serial port.

> 
> RTKlib works with "raw data" from nv08c (pseudorange+pseudophase and ephemeris data).

Yep, I understand that.

> By default these messages are turned off in the receiver.

Which confirms what we found yesterday.

> So you have to send special BINR commands to activate them. BINR protocol is published by receiver manufacturer: http://www.nvs-gnss.com/support/documentation/item/download/39.html . 

> 
> All descriptions in internet of how to connect nv08c to RTKlib copy settings that can be found here: http://www.onetalent-gnss.com/ideas/usb-hw-receivers/denga10 (http://www.onetalent-gnss.com/ideas/usb-hw-receivers/denga10/rtklib242b4_mb.zip?attredirects=0&d=1). You can copy settings of the nvs_raw_1Hz.txt or nvs_raw_10Hz.txt to the cmd window of input stream.

I’ll have a look at these.  Thank you for the pointers.

> 
> But if you use the latest version of RTKlib you can use commands that are more readable. In the RTKlib manual on page 11 there are commands that rtklib supports for nv08c:
> 
> !NVS ... : NVS NV08C binary command 
> !NVS CFG-PVTRATE [arg...] configure PVT rate 
> !NVS CFG-RAWRATE [arg...] configure raw data rate 
> !NVS CFG-SMOOTH configure smooth range 
> !NVS CFG-BINR xx [...] send binary command for NVS 
> (input hexadecimal series) 
> !WAIT time : wait for time (ms) 
> 
> So in the cmd window of input stream you can simply print something like:
> !NVS CFG-PVTRATE 1
> !WAIT 1000
> !NVS CFG-RAWRATE 1
> 
> And you will get 1HZ raw data stream to RTKnavi.

I had seen these, but discarded them because this seems to imply that they only change the rate, not what is sent.  But obviously changing the rate may also change what is sent.

So I just tried, and this does not work.  I have tried to send that to both ports.  RTKnavi does not receive anything, or at best incomplete NMEA sentences.

Also, I’m not sure what PVT means.  Finally, is that a rate in Hz you give or a delay (i.e. 0.1 for 10Hz).  I tried 10, 1, and 0.1 and none of them seem to work.

> 
> You can check that RTKnavi is receiving raw data by clicking on the button "RTK monitor" and then choosing "Obs data" or "Nav GPS" or "NAV GLONASS" and you should see there observations, GPS ephemeris and GLONASS ephemeris respectively.

Yes, this is what I have been using to check what was received from the receivers.  Very useful tool!

Fred

> 
> Regards,
> Artyom
> 
> 
> On Wed, Sep 23, 2015 at 8:39 PM, Fred Labrosse <ffl at aber.ac.uk> wrote:
> All,
> 
> I am not quite new with RTKLIB (I have used it at some point with a pair of Yuan10 receivers).  We have just taken delivery of 2 NV08C evaluation kits (NV08C-EVK-CSM) and tried to use rtklib.
> 
> So far not much success.  The first issue is that we finally realised that the USB port only sends NMEA by default.  So we switched to the D9 connector that does send BINR data.  Clearly rtklib is receiving the data (the data display window in NVS BINR mode shows regular lines with a message type and length), but no processing is happening (solid rather than flashing processing “LED” in rtknavi and no solution data displayed or logged).  The receiver do get a fix, according to the NMEA we get on the USB port.
> 
> The documentation seems to indicate that what data we want to get has to be configured, but we have not yet found a way to do that.  Any chance anybody has managed that could share info please?
> 
> Cheers,
> 
> Fred
> 
> _______________________________________________
> This message is sent to you from FOSS-GPS at lists.osgeo.org mailing list.
> Visit http://lists.osgeo.org/mailman/listinfo/foss-gps to manage your subscription
> For more information, check http://wiki.osgeo.org/wiki/FOSS-GPS
> 
> _______________________________________________
> This message is sent to you from FOSS-GPS at lists.osgeo.org mailing list.
> Visit http://lists.osgeo.org/mailman/listinfo/foss-gps to manage your subscription
> For more information, check http://wiki.osgeo.org/wiki/FOSS-GPS