Re: [Gpsbabel-code] Reading U-Blox EVK-M91 serial data
Brought to you by:
robertl
From: Geo D. <geo...@gm...> - 2022-07-31 15:50:04
|
thanks for the info and I apologize for some inappropriate phrases of mine. Roberto Il giorno dom 31 lug 2022 alle ore 13:56 Greg Troxel <gd...@le...> ha scritto: > > Geo DrinX <geo...@gm...> writes: > > >> > I am sure it is a standard gps NMEA sentence file format, but... how > to > >> > successfully read it? > >> > >> You are sure because > >> 1) you read the documentation and it says it is NMEA, and if so which > >> version? > >> 2) you looked at the data stream and it looks like NMEA? > >> 3) something else? > >> > > > > none of this. Perhaps I have simply misunderstood the data in my > possession. > > Obviously I wasn't blunt enough. You made a claim that you were "sure", > which I thought was unwarranted -- and it seems I was correct. I gave > two actual reasonable and plausible possibilities and "something else" > was meant as "so if it isn't 1 or 2, why do you believ this" and then > you didn't answer the question. When asking for help politeness demands > straightforward answers to reasonable, on-point questions, even if it's > "actually I was confused and I have no basis to believe anything; I'll > go figure it out". > > > Obviously, I also requested support from QGIS, > > It's not obvious. The only thing that's clear by now is that you have > provided much less information than is appropriate and that you have > declined to answer reasonable questions. If you had filed a bug with > qgis, you should have provided a URL to the issue, and you should have > described exactly what you did in the issue. > > > but for now they are not very interested in letting people know that > > there is something wrong with the gps reading. > > I am not surprised that your interaction there did not go well, given > this discussion. > > > Maybe it's complicated to fix, or it's just me, and therefore has a very > > low priority in their bug fix list. Wnho knows? > > I think it's mostly you and partly that the docs are not clear enough in > one small section. > > First, the qgis docs say: > > 1) For loading vector data *from files or from storage in devices* > - native is GPX > - it can use GPSBabel to read other formats > - it can use GPSBabel to download waypoints/tracks > > > https://docs.qgis.org/3.22/en/docs/user_manual/working_with_gps/plugins_gps.html > > 2) For live tracking, the options are: > - serial device > - gpsd > What is unsaid is what is normal these days and really has been for > a very long time: devices connected by serial are expected to > output NMEA. And, they say that it works with gpsd, and gpsd's > mission is to read real-time data from any device and transform it > into standard form. > > > https://docs.qgis.org/3.22/en/docs/user_manual/working_with_gps/live_GPS_tracking.html#gps-options > > I used an M8 (vs M9) with qgis via gpsd at some point and it worked > straightforwardly (on NetBSD; you seem to be using Windows and I have > zero experience with GNSS devices or qgis on Windows). In fact, I > have zero idea if gpsd runs on Windows. I do know that the people who > maintain it don't use Windows. > > Second, u-blox provides hundreds of pages of docs about the formats > spoken by their devices and how to configure them. They provide a > zero-cost proprietary program u-center that does that configuration. > You seem not to have read the docs. > > Third, one can connect to the device with kermit etc. and look at it. > Surely if you've written a plugin you know that you should do this and > you know how. > > The qfield docs also fail to state that external GNSS receivers are > expected to speak NMEA: > > https://docs.qfield.org/how-to/gnss/ > > but of course that is how it is. That also works, with an F9P, which is > pretty similar to an M9. > > |