Update for README.md

[csylvain]

ubxtool does not work "out of the box" with the uBlox MAX-M8Q on the Uputronics Raspberry Pi+ GPS Expansion shield. the software itself does build on Raspbian Buster, so there is hope. toward that end, i propose for now these changes to the README.md file (no need yet to clone the repo just for these changes):

--- a/README.md                                                                                                        
+++ b/README.md                                                                                                        
@@ -5,7 +5,8 @@ galileo/GPS/GLONASS/BeiDou open source monitoring. GPL3 licensed.                                       Live website: https://galmon.eu/

 Theoretically multi-vendor, although currently only the U-blox 8 chipset is
-supported. Navilock NL-8012U receiver works really well, as does the U-blox evaluation kit for the 8MT.               
+supported. Navilock NL-8012U receiver works really well, as does the U-blox evaluation kit for the 8MT,               
+as well as the Uputronics Raspberry Pi+ GPS Expansion board in a future release.                                      
 Highlights:
  * Processes raw frames/strings/words from GPS, GLONASS, BeiDou and Galileo
@@ -31,13 +32,13 @@ Goals:                                                                                                 order calculations

 Works on Linux (including Raspbian on Pi Zero W), OSX and OpenBSD.
-                                                                                                                      
+Builds on Raspbian Buster [g++-8] (but not Raspbian Stretch [g++-6]).                                                 

 Build locally
 -------------

-To get started, make sure you have a C++17 compiler, git, protobuf-compiler.

+To get started, make sure you have a C++17 compiler (g++ version 8 or better), git, protobuf-compiler, and ncurses-dev.                                                                                                                       

Then run 'make ubxtool navdump' to build the receiver-only tools.

 To also run the webserver locally, intall libh2o-dev and run 'make'.

@@ -45,7 +46,7 @@ To also run the webserver locally, intall libh2o-dev and run 'make'.                                  To build everything, try:

-apt-get install protobuf-compiler libh2o-dev libcurl4-openssl-dev libssl-dev libprotobuf-dev libh2o-evloop-dev libwslay-dev                                                                                                                  
+apt-get install protobuf-compiler libh2o-dev libcurl4-openssl-dev libssl-dev libprotobuf-dev libh2o-evloop-dev libwslay-dev libncurses-dev                                                                                                    git clone https://github.com/ahupowerdns/galmon.git --recursive
cd galmon                                                                                                              
make

[ahupowerdns]

Hi - I have updated the README with some of these details. Can you tell what does not work out of the box so we can help? Thanks!

[csylvain]

just did a git pull ( 91df9d4 ) and am building navparse and ubxtool on RPi 3B+ with Raspbian Buster.
GPS Expansion Board is at /dev/ttyS0 (verified with minicom ).

navparse build died:

coverage.cc:11:10: fatal error: eigen3/Eigen/Dense: No such file or directory
 #include <eigen3/Eigen/Dense>
          ^~~~~~~~~~~~~~~~~~~~
compilation terminated.

ubxtool builds. results:

$ ./ubxtool --debug --port /dev/ttyS0 --gps --station 1 --stdout
Sat, 09 Nov 2019 23:54:52 +0000 initFD()
Sat, 09 Nov 2019 23:54:52 +0000 initFD - open(/dev/ttyS0)
Sat, 09 Nov 2019 23:54:52 +0000 initFD - open successful
Sat, 09 Nov 2019 23:54:52 +0000 will enable RTSCTS
Sat, 09 Nov 2019 23:54:52 +0000 initFD - tty set

no other output produced. did i do something wrong?

immediately after trying ubxtool shown above, double-checking with "minicom -D /dev/ttyS0 -b 9600" produces the usual stream of NMEA sentences.

[csylvain]

better results with

 ./ubxtool --debug --port /dev/ttyS0 --baud 9600 --gps --galileo --glonass --stdout --keep-nmea --wait

output:

Sun, 10 Nov 2019 00:04:50 +0000 initFD()
Sun, 10 Nov 2019 00:04:50 +0000 initFD - open(/dev/ttyS0)
Sun, 10 Nov 2019 00:04:50 +0000 initFD - open successful
Sun, 10 Nov 2019 00:04:50 +0000 will enable RTSCTS
Sun, 10 Nov 2019 00:04:50 +0000 initFD - tty set
Sun, 10 Nov 2019 00:04:52 +0000 Sending version query
Sun, 10 Nov 2019 00:04:52 +0000 swVersion: ROM CORE 3.01 (107888)
Sun, 10 Nov 2019 00:04:52 +0000 hwVersion: 00080000
Sun, 10 Nov 2019 00:04:52 +0000 Extended info: FWVER=SPG 3.01
Sun, 10 Nov 2019 00:04:52 +0000 Extended info: PROTVER=18.00
Sun, 10 Nov 2019 00:04:52 +0000 Extended info: GPS;GLO;GAL;BDS
Sun, 10 Nov 2019 00:04:52 +0000 Extended info: SBAS;IMES;QZSS
Sun, 10 Nov 2019 00:04:53 +0000 Sending GNSS query
Sun, 10 Nov 2019 00:04:53 +0000 GNSS status, got 7 rows:
Sun, 10 Nov 2019 00:04:53 +0000 GNSSID 0 enabled 1 minTrk 8 maxTrk 16 1 0  1 1
Sun, 10 Nov 2019 00:04:53 +0000 GNSSID 1 enabled 1 minTrk 1 maxTrk 3 1 0  1 1
Sun, 10 Nov 2019 00:04:53 +0000 GNSSID 2 enabled 0 minTrk 4 maxTrk 8 0 0  1 1
Sun, 10 Nov 2019 00:04:53 +0000 GNSSID 3 enabled 0 minTrk 8 maxTrk 16 0 0  1 1
Sun, 10 Nov 2019 00:04:53 +0000 GNSSID 4 enabled 0 minTrk 0 maxTrk 8 0 0  1 3
Sun, 10 Nov 2019 00:04:53 +0000 GNSSID 5 enabled 1 minTrk 0 maxTrk 3 1 0  1 5
Sun, 10 Nov 2019 00:04:53 +0000 GNSSID 6 enabled 1 minTrk 8 maxTrk 14 1 0  1 1
Sun, 10 Nov 2019 00:04:53 +0000 Got an ack for 6 62 while waiting for 6 62
Sun, 10 Nov 2019 00:04:53 +0000 Got ACK for our poll of GNSS settings
Sun, 10 Nov 2019 00:04:53 +0000 Sending GNSS setting, GPS: 1, Galileo: 1, BeiDou: 0, GLONASS: 1, SBAS: 0
Sun, 10 Nov 2019 00:04:54 +0000 Got an ack for 6 62 while waiting for 6 62
Sun, 10 Nov 2019 00:04:54 +0000 Got ack on GNSS setting
Sun, 10 Nov 2019 00:04:54 +0000 Polling port settings
Sun, 10 Nov 2019 00:04:54 +0000 Protocol settings on port:
3 0 0 0 0 0 0 0 0 0 0 0 7 0 3 0 0 0 0 0
Sun, 10 Nov 2019 00:04:54 +0000 Got an ack for 6 0 while waiting for 6 0
Sun, 10 Nov 2019 00:04:54 +0000 Got ACK for our poll of port protocol settings
Sun, 10 Nov 2019 00:04:54 +0000 Enabling UBX-RXM-RLM
Sun, 10 Nov 2019 00:04:54 +0000 Got an ack for 6 1 while waiting for 6 1
Sun, 10 Nov 2019 00:04:54 +0000 Enabling UBX-RXM-RAWX
Sun, 10 Nov 2019 00:04:54 +0000 Got an ack for 6 1 while waiting for 6 1
Sun, 10 Nov 2019 00:04:54 +0000 Enabling UBX-RXM-SFRBX
Sun, 10 Nov 2019 00:04:54 +0000 Got an ack for 6 1 while waiting for 6 1
Sun, 10 Nov 2019 00:04:54 +0000 Enabling UBX-NAV-POSECEF
Sun, 10 Nov 2019 00:04:54 +0000 Got an ack for 6 1 while waiting for 6 1
Sun, 10 Nov 2019 00:04:54 +0000 Enabling UBX-NAV-SAT
Sun, 10 Nov 2019 00:04:54 +0000 Got an ack for 6 1 while waiting for 6 1
Sun, 10 Nov 2019 00:04:54 +0000 Enabling UBX-NAV-PVT
Sun, 10 Nov 2019 00:04:54 +0000 Got an ack for 6 1 while waiting for 6 1
Sun, 10 Nov 2019 00:04:54 +0000 Entering main loop
^C

[csylvain]

 ./ubxtool --port /dev/ttyS0 --baud 9600 --gps --galileo --glonass --keep-nmea --wait --sbas --stdout | ./navdump
Sun, 10 Nov 2019 00:14:25 +0000 swVersion: ROM CORE 3.01 (107888)
Sun, 10 Nov 2019 00:14:25 +0000 hwVersion: 00080000
Sun, 10 Nov 2019 00:14:25 +0000 Extended info: FWVER=SPG 3.01
Sun, 10 Nov 2019 00:14:25 +0000 Extended info: PROTVER=18.00
Sun, 10 Nov 2019 00:14:25 +0000 Extended info: GPS;GLO;GAL;BDS
Sun, 10 Nov 2019 00:14:25 +0000 Extended info: SBAS;IMES;QZSS
Sun, 10 Nov 2019 00:14:34 +0000 Entering main loop

no more output seen after "Entering main loop"

[csylvain]

is the fix for my issue to use what looks like a new ubxtool parameter

--ubxport <id>

??

[csylvain]

i can answer my own question now: yes. the new "--ubxtool" parameter ensures the response from the chipset returns via the path used to put the chipset into uBlox binary output mode. with some coaxing using "--reset" parameter, i can delicately get the Uputronics GPS Shield for RPi reporting data which navparse can display in the local web browser.
the new "--ubxtool" parameter needs some documenting, though. otherwise, i feel this issue is successfully closed.