finds.dev← search

// the find

Aidan-McNay/5220-telehealth

C · updated May 2025

The code for our MAE 5220 Final Project, involving remote blood pressure monitoring

Firmware for a Raspberry Pi Pico W that reads blood pressure readings from an Omron Evolv BP7000 over BLE and forwards them over LoRaWAN to The Things Network, built as a class project for an IoT course. It also includes the custom PCB design that joins the board together. Most useful to someone building a similar BLE-to-LoRaWAN bridge or trying to see how the pieces fit on a Pico.

The BLE code lives in its own directory (ble/omron.cpp and ble/client.cpp, on top of BTstack), apart from the lorawan/ and ui/ code, so the Omron-specific parsing can be read or replaced without touching the radio stack. The hardware side is included too: a KiCad project, schematic, Gerbers and a STEP model, which is more than most student IoT repos ship. The encryption/ directory pairs C encryption code (encryption.cpp over rijndael.c) with Python decrypt scripts such as process_decrypt.py, so the payload handling can be checked from both ends.

The README describes the directory layout and the goal but gives no build steps, no flashing instructions, no TTN payload format, and no note on which BP7000 firmware or BLE pairing sequence the code expects. To learn what a packet looks like, you have to read omron.cpp. The encryption/ directory holds bp_log.csv, myData.csv and myData.txt next to the code. If those are real readings, that is personal health data in a public repo and the .gitignore needs a look. If they are test fixtures, the README should say so. app/ mixes finished entry points with scratch files (foobar.cpp, switch_test.cpp, button_test.cpp), and a .ipynb_checkpoints folder was committed, so nothing says which target is the real one. The last push was in May 2025, and nothing in the README pins the Pico SDK version or the lorawan-library-for-pico submodule commit, so reproducing a build later will take guesswork.

View on GitHub →

// want more like this?

We dig through GitHub every week and send a few repos picked for what you actually care about — each with an honest take like this one.

Get finds in your inbox → Search again →