Anyone else interested in a Raspberry Pi Hat/Shield for the SparkFun “GPS-RTK-SMA Breakout - ZED-F9P” and/or “Quadband GNSS RTK Breakout - LG290P” breakout boards, which I believe share the same pinouts - I’m thinking a wide DIL socket for the two parallel pin rows?
There are already generic qwiic and breadboard RPi adapters, but it would be great to be able to mount a Z9P or LG290P directly on top of an RPi for a compact rover or base station set up, perhaps in conjunction with a helical antenna?
I want to build a cheap rover with the Quadband GNSS RTK Breakout board - LG290P.
I am knowledgeable in GNSS but not in parts assembly projects.
I accept suggestions.
My idea is to use the board as a rover with Galileo HAS corrections.
Bluetooth is needed to transfer data to the cell phone.
How would the Bluetooth be connected to the board?
Greetings and thanks
Angel
@semuadmin - Yes, we plan to do more hats with GNSS receivers but we always have more ideas than we have time!
@amlago - The LG290P breakout connects with the BlueSMiRF Bluetooth module. You would need to solder on female headers to the LG290P breakout board.
Note: While the LG290P incorporates the E6 signal into its position fix, it does not (yet) utilize the signal for HAS PPP convergence. Currently, I’ve only seen the UM980 do that. If you are looking to play with HAS, use the UM980 breakout.
Hello. I have a module equipped with this component. Regarding the possibility of using the GALILEO HAS correction, it is a little ambiguous. I followed several posts on the Quectel forum, and george.gao from support told me that the service was currently supported by the LG290P. This appears to be supported by the manufacturer’s documentation. The Quectel_LG290P(03)_Hardware_Design_V1.0 document downloadable from the quectel.com site does not show a small red star on the PPP-B2b and Galileo HAS E6 functionality, but a small red star for QZSS L6. This little star indicates whether the feature is in development or not. However, for my part I was not able to find out if these corrections were correctly applied. However, my module has the latest firmware version. GNSS master tells me a DGNSS status, and barely metric precision…. I raised this problem on the forum, in different places, and so far no answers. We are still missing feedback on this issue. If the Sparkfun developers could give their point of view, that would be great, finding clear information on this subject is complicated
What I’ve been told by Quectel: HAS is not currently supported on the May-2024 firmware on the LG290P but should be supported in an upcoming firmware release.
Thank you for your response. Indeed the current firmware is LG290P03AANR01A03S dating from May. This therefore confirms that HAS is not supported. So we will wait for the firmware update
Has anyone gotten eyes on the new protocol doc? I’ve tried feeding various versions of RAW-HASE6 (as is, with PQTM, with PQTM-, and all variations with and without “,1”) into the $PQTMCFGMSGRATE,R, to no avail.
Not that I’d know what to do with the raw data without a protocol reference anyway, but it was a fun to try.
Also, use QGNSS and its ‘advance’ button to calculate the NMEA checksum. Then just enter commands complete with a * at the end. I have a running scratch pad of commands in a doc that help me do some low level config tests. Also, remember that you often have the do a save and unit reset for any given command to take effect (it’s annoyingly about 50% of the time, NMEA message enable no, RTCM message enable yes).
My go to GNSS app is actually GNSS Firebird from Locosys. When it is set to “CR LF CKS” it will append * and the checksum to any NMEA command. The killer feature that it has that QGNSS lacks is the ability to filter by strings in the text console. When I put in PQTM and click the magnifying glass, it hides any messages that don’t include PQTM.
BTW, the Locosys LU23030-V2 is a very nicely priced “GPS Mouse” using an Airoha chip. It is my first recommendation when anyone asks what GNSS module they should get for things like wardriving. I don’t think they have a US distributor … just saying.
