[FOSS-GPS] Configuring a NV08C for rtklib

Thu Oct 8 06:45:49 PDT 2015

All,

I have finally found some time to play with that again.  I am trying to set the device to send BINR on port 1, where the USB is attached to, because that would be a lot more convenient in our application (only one connection rather than having to use the USB to power the device and the serial connection to get the data).

So I have modified the command at startup with two additional lines (before the lines that were suggested earlier in this thread):

$PORZA,1,115200,3*7F
!WAIT 500

which are supposed to set port 1 to send BINR data at 115200 bauds.  This seems to work.  However, I need to connect once first with no parity for the first line to work, then disconnect and reconnect again with odd parity to be able to get the BINR.

I, possibly wrongly, thought that I needed to tell the device to switch to BINR using NMEA as it, by default, sends NMEA so would presumably not understand BINR.  Is that a right assumption?  If yes, is there a way around that issue of having to connect, disconnect and reconnect again?

Cheers,

Fred

PS, In fact it seems that sometimes I have to disconnect and reconnect again a couple of times before I get BINR data, but this might be just a question of flushing ports or waiting more, I haven’t yet found a solution.

> On 25 Sep 2015, at 14:18, Fred Labrosse <ffl at aber.ac.uk> wrote:
> 
> That was it! Odd parity!  So simple.
> 
> Thank you!
> 
> My view of the sky is far from good where I am, but now rtklib is reporting data, and I briefly got a fix (single) from one receiver.  Now to try the tow together.
> 
> Thanks again.
> 
> Fred
> 
>> On 25 Sep 2015, at 12:19, Artyom G <gnsssdr at gmail.com> wrote:
>> 
>> Hi Fred,
>> 
>> There is only one last thing that I have forgetten to mention. Did you set Odd parity in COM-port settings in your experiments???
>> 
>> Today I've used thik kit: http://www.nvs-gnss.com/products/evk/item/4-evk-csm.html with RTKlib2.4.2 and it worked fine. I used the following commands at start-up:
>> !NVS CFG-PVTRATE 2
>> !WAIT 1000
>> !NVS CFG-RAWRATE 2
>> 
>> In order to get data from USB (COM PORT0) at first I switched from NMEA to BINR in BM control (alternatively NMEA $PORZA message can be used for this purpose). When I used COM PORT with DB9 connector I didn't make any preparations.
>> 
>> Regards,
>> Artyom
>> 
>> On Thu, Sep 24, 2015 at 7:35 PM, Fred Labrosse <ffl at aber.ac.uk> wrote:
>> 
>>> 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. Or you can find in the documentation special command that changes NMEA to BINR and send them yourself.
>> 
>> Thanks again for the pointers, they have been very useful.
>> 
>> Today we played a lot with BM_Ctrl (V0434 provided with the evaluation kit).  We managed to set the mode of the various ports, to get the necessary data (in BM_Ctrl), etc.  However, this is all reset when the board is disconnected (for example to use it on the actual computer that runs rtklib for our experiments).  Is there a way to save the settings permanently in the board so that they survive a restart?
>> 
>> We have also been playing with BM_Ctrl talking to the NV08C on one port, setting the other to BINR and using that port with rtklib.  However, rtklib does not seem to receive anything when the port is in BINR mode (sometimes does but only a couple of message types, not enough for rtklib, and we haven’t found out why sometimes and not always).  We came to the conclusion that we either need to find the instructions to tell the NV08C to always send the needed data or to have rtklib to regularly ask for it (as BM_Ctrl seems to be doing).  I have tried the commands given by Artyom below and tried the file on onetalent, but neither did that.  We seem to connect from rtklib on a BINR port but we do not get sent anything.
>> 
>> What are we missing?  What are the correct instructions to send?
>> 
>> Cheers,
>> 
>> Fred
>> 
>>> 
>>> RTKlib works with "raw data" from nv08c (pseudorange+pseudophase and ephemeris data). By default these messages are turned off in the receiver. 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.
>>> 
>>> 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.
>>> 
>>> 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.
>>> 
>>> 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
>> 
>> _______________________________________________
>> 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
> 