# LG290P with Raspberry Pi

**URL:** <https://community.sparkfun.com/t/lg290p-with-raspberry-pi/62263>\
**Category:** GPS/GNSS\
**Created:** [December 11, 2024, 7:47pm UTC](https://community.sparkfun.com/t/lg290p-with-raspberry-pi/62263 "2024-12-11T19:47:06Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![Planxty312](https://avatars.discourse-cdn.com/v4/letter/p/5f9b8f/32.png) [@Planxty312](https://community.sparkfun.com/u/Planxty312)\
**Post date:** [December 11, 2024, 7:47pm UTC](https://community.sparkfun.com/t/lg290p-with-raspberry-pi/62263/1 "2024-12-11T19:47:06Z")

</div>

I’m trying to use a LG290P with a Pi 3 through the USB interface. The Pi doesn’t seem to recognize the 290P.

Is there a driver that needs to be installed on the Pi?

---

<div class="post-metadata">

**Author:** ![TS-Russell](https://yyz1.discourse-cdn.com/sparkfun/user_avatar/community.sparkfun.com/ts-russell/32/6092_2.png) [@TS-Russell](https://community.sparkfun.com/u/TS-Russell)\
**Post date:** [December 11, 2024, 7:55pm UTC](https://community.sparkfun.com/t/lg290p-with-raspberry-pi/62263/2 "2024-12-11T19:55:26Z")

</div>

The product page notes ‘only the UART interface is supported by the module’

I would just pass one of the UARTs [Hardware Overview - SparkFun LG290P Quadband GNSS RTK Breakout Hookup Guide](https://docs.sparkfun.com/SparkFun_LG290P_Quadband_GNSS_RTK_Breakout/hardware_overview/#peripherals-and-io-pins) Tx & Rx to the Rx & Tx of the Pi, then listen to those pins

---

<div class="post-metadata">

**Author:** ![Planxty312](https://avatars.discourse-cdn.com/v4/letter/p/5f9b8f/32.png) [@Planxty312](https://community.sparkfun.com/u/Planxty312)\
**Post date:** [December 11, 2024, 8:16pm UTC](https://community.sparkfun.com/t/lg290p-with-raspberry-pi/62263/3 "2024-12-11T20:16:58Z")

</div>

Thanks. Somehow I thought UART included USB.

---

<div class="post-metadata">

**Author:** ![TS-Russell](https://yyz1.discourse-cdn.com/sparkfun/user_avatar/community.sparkfun.com/ts-russell/32/6092_2.png) [@TS-Russell](https://community.sparkfun.com/u/TS-Russell)\
**Post date:** [December 12, 2024, 5:31pm UTC](https://community.sparkfun.com/t/lg290p-with-raspberry-pi/62263/4 "2024-12-12T17:31:50Z")

</div>

You might be able to use raspi-config and enable serial and see if something shows up over the usb (bc the LG290P has a UART-USB on it) but hardwiring to Rx/Tx will definitely work 😉

---

<div class="post-metadata">

**Author:** ![Planxty312](https://avatars.discourse-cdn.com/v4/letter/p/5f9b8f/32.png) [@Planxty312](https://community.sparkfun.com/u/Planxty312)\
**Post date:** [December 12, 2024, 5:53pm UTC](https://community.sparkfun.com/t/lg290p-with-raspberry-pi/62263/5 "2024-12-12T17:53:18Z")

</div>

What is the initial baud rate on the 290P? How does one change that?

---

<div class="post-metadata">

**Author:** ![TS-Russell](https://yyz1.discourse-cdn.com/sparkfun/user_avatar/community.sparkfun.com/ts-russell/32/6092_2.png) [@TS-Russell](https://community.sparkfun.com/u/TS-Russell)\
**Post date:** [December 12, 2024, 7:20pm UTC](https://community.sparkfun.com/t/lg290p-with-raspberry-pi/62263/6 "2024-12-12T19:20:36Z")

</div>

Looks like 460800 [Hardware Overview - SparkFun LG290P Quadband GNSS RTK Breakout Hookup Guide](https://docs.sparkfun.com/SparkFun_LG290P_Quadband_GNSS_RTK_Breakout/hardware_overview/#peripherals-and-io-pins)

You shouldn’t need to change the board’s baud; change the Pi’s  
[You may need drivers for CH342 for the Pi](https://github.com/WCHSoftGroup/ch343ser_linux)…not sure how drivers work for those

---

<div class="post-metadata">

**Author:** ![Planxty312](https://avatars.discourse-cdn.com/v4/letter/p/5f9b8f/32.png) [@Planxty312](https://community.sparkfun.com/u/Planxty312)\
**Post date:** [December 15, 2024, 4:26pm UTC](https://community.sparkfun.com/t/lg290p-with-raspberry-pi/62263/7 "2024-12-15T16:26:49Z")

</div>

Using the UART pins on the PI works fine, ty.

---

<div class="post-metadata">

**Author:** ![semuadmin](https://yyz1.discourse-cdn.com/sparkfun/user_avatar/community.sparkfun.com/semuadmin/32/7096_2.png) [@semuadmin](https://community.sparkfun.com/u/semuadmin)\
**Post date:** [April 2, 2025, 12:24pm UTC](https://community.sparkfun.com/t/lg290p-with-raspberry-pi/62263/8 "2025-04-02T12:24:58Z")

</div>

More an observation than a fix, but in deploying [PyGPSClient](https://github.com/semuconsulting/PyGPSClient) on a Raspberry Pi 5 to monitor and configure an LG290P, I noticed that none of the UART ports are recognised automatically by the standard Python function used by PyGPSClient to detect comms ports ( `serial.tools.list_ports.comports()`), _even after_ enabling the serial interface in `raspi-config` _and_ making the recommended changes to the `/boot/firmware/config.txt` file:

```auto
dtoverlay=uart2
dtoverlay=uart3
dtoverlay=uart4

```

This would seem to suggest there’s something slightly unusual about Quectel’s UART implementation on the LG290P - I’ve not seen this behaviour on any other serial GNSS device with a Raspberry Pi 4 or 5.

PyGPSClient does, however, allow users to manually add a user-defined serial port e.g. `\dev\ttyAMA0`, and it then works fine. The default baud rate for all 3 UART ports is 460800.

**Note that** some cheaper UART-USB FTDI adapters don’t support this baud rate, at least not reliably.

---

<div class="post-metadata">

**Author:** ![millerjs2](https://yyz1.discourse-cdn.com/sparkfun/user_avatar/community.sparkfun.com/millerjs2/32/8372_2.png) [@millerjs2](https://community.sparkfun.com/u/millerjs2)\
**Post date:** [April 3, 2025, 4:51pm UTC](https://community.sparkfun.com/t/lg290p-with-raspberry-pi/62263/9 "2025-04-03T16:51:49Z")

</div>

@Planxty312 Are you using the sparkfun LG290P breakout board, or another? If you’re using the Sparkfun LG290P board - it is kind of unique in that the UART to USB chip on it shows up in linux as two different ports, but only one is connected to UART1 from the LG290P.

Make sure you are using the right one. On my system they come up as ttyACM0 and ttyACM1 - and for me ttyACM1 is the one with data, but that can change.
