![bu-353s4 usb gps receiver blinking red bu-353s4 usb gps receiver blinking red](https://m.media-amazon.com/images/S/aplus-media/vc/5ef2431e-e67f-4ffc-90e8-621d36b80201._SR150,300_.jpg)
#Bu 353s4 usb gps receiver blinking red download#
Download the latest Raspberry Pi OS Lite image.That battery pack is extreme overkill, and powers the unit continuously for 42 hours, when logging at a 5-second interval. I use a standard adapter when testing and a 10000mAh USB battery pack in the field (specifically the Anker PowerCore Speed 10000 QA).
#Bu 353s4 usb gps receiver blinking red driver#
* Some other variety of display, if you’re willing to write a driver class for it. Good if you’re using this in your vehicle and have “unlimited” power. This is much brighter than the e-Ink and can refresh at up to 30Hz, but draws more power. * An adafruit 4567 2.23” Monochrome OLED Bonnet OLED. The one I purchased is also fully assembled and just connects directly to the Pi’s 40-pin header. This means that if you have a GPS display that refreshes every minute, it will still show the last coordinates as of when it lost power. While e-Ink displays are comparatively sluggish (this one takes an astonishing 15 seconds to re-draw the screen), they offer some major advantages for this purpose: they have very low power consumption, and the displayed information stays visible until the next refresh even without power. * A bitmap display, such as the Waveshare 2.13 inch E-Ink Display Hat (B), which I got on Amazon for $25 USD. * Two GPIO-connected LEDs on the RPi, ideally different colors (see below). gpsd compatible GPS (I use a GlobalSat BU-353-S4 USB the gpsd folks say some pretty awful things about it, but we’ll see…).Raspberry Pi OS with Python3 (see installation instructions below).Raspberry Pi (tested with Pi Zero 1.3) and a MicroSD card (I’m using an 8GB SanDisk Ultra Class 10 UHS-1, which has enough space after the OS for 240 days of 5-second-interval data).There’s no reason for a logger to have to worry about the nuances of GPS communication itself.
![bu-353s4 usb gps receiver blinking red bu-353s4 usb gps receiver blinking red](https://www.manua.ls/thumbs/products/l/1325178-globalsat-bu-353s4.jpg)
This program relies on gpsd to interact with the GPS itself, as it’s very mature and stable software, exposes a simple JSON-based socket interface, and also has decent Python bindings. Data is written in gpsd’s native format, but a conversion tool is provided.
![bu-353s4 usb gps receiver blinking red bu-353s4 usb gps receiver blinking red](https://alexnld.com/wp-content/uploads/2018/12/b9906be8-de65-4cb7-9b18-a7d310acd366.jpg)
It writes the most recent position data from gpsd to disk at a user-defined interval, flushes IO after each write (so that it’s safe to just pull the power on the Pi), and uses two LEDs to indicate status while in the field. The goal is to package all of this together into a “small” (but not necessarily lightweight, based on the components) package that I can put in the outside pocket of my hiking pack, and record an accurate and detailed GPS track of my hikes. The hardware decision was mainly based on what I had lying around: a Raspberry Pi Zero, a 10,000mAh external battery pack for my cell phone, and a USB GPS (well, I thought I had one, and got far enough into the project when I decided it was missing for good that I bought another). This is a trivial (and not really “supported”) project of mine to couple a Raspberry Pi Zero with a USB GPS receiver and a battery pack to GPS track my hikes.