sghctoma / sst Goto Github PK

MTB suspension telemetry

License: MIT License

CMake 2.11% C 22.91% Python 42.78% Go 12.30% CSS 3.79% HTML 0.26% Makefile 0.15% Dockerfile 0.38% JavaScript 15.20% Mako 0.12%

sst's Introduction

Sufni Suspension Telemetry

Sufni* Suspension Telemetry is a mountain bike suspension telemetry system that was born out of sheer curiosity. The data acquisition unit is built around the Raspberry Pi Pico W and uses affordable off-the-shelf components, so anybody with a bit of soldering skills can build it.

Contrary to most (all?) suspension telemetry systems, Sufni uses rotary encoders to measure movement. They are cheap, reasonably accurate, and can reach pretty high sample rates. An additional benefit is that on some frames they are easier to attach to rear shocks than linear sensors, because they can fit into much tigther spaces.

The DAQ uses a WiFi network to send recorded sessions to the backend server. When processing is done, data can be analyzed on the web user interface that provides plots useful for setting up the spring rate, damping and the bike's overall balance. GPX tracks can also be uploaded, and MP4 videos can be opened from the local machine. These are synchronized to the travel plot, so you can easily find how your suspension behaved on a certain part of the trail.

The user interface has two additional functionalities:

New bike setups can be created, and they can be associated with a DAQ unit based on the Pico's uniqe identifer.
Normalized (travel percentage, or a number between 0 and 1) data can also be imported from CSV files, so you can use the webapp without being tied to Sufni's hardware.

Please refer to the wiki for a quickstart guide, build instructions, and a full tour on the user interface, plots etc.

* The word "sufni" (pronounced SHOOF-nee) means tool shed in Hungarian, but also used as an adjective denoting something as DIY, garage hack, etc.

sst's People

Contributors

Stargazers

Watchers

Forkers

jeromelacote jayblack squirl0007 ssonparote chipperatkins finnitio

sst's Issues

Use GPS data from GoPro videos

This should be pretty straightforward with JuanIrache/gopro-telemetry, I just need to get my hands on some GoPro footage (I only have a Hero 3 Silver, so no GPS data for me :) )

Add session rename/delete functionality

Alternative mounting solution that does not require a triangle?

exploring this project, really great work!

Any alternatives for the sensors that don't require the triangle built with equal lenght rods?
On long travel up side down forks that would be really exposed to the "events" and low to the ground
Could use some lego gears and strings as reducer or directly a string potentiometer like this https://www.printables.com/model/178470

Load settings from a file

The following should be loaded from a file on the MicroSD card rather than being hardcoded:

SST server domain / IP
WiFi SSID and PSK
NTP server domain / IP
~~timezone (?)~~

Bluetooth session synchronization

Raspberry Pi Pico SDK v1.5 introduced Bluetooth support, so it might be a good idea to explore it as a possiblity to sync with mobile phones and/or cycling computers.

Open last imported session instead of the absolute newest

Handle SQLITE_BUSY errors

Deduplicate API endpoints

Some HTTP API endpoints are implemented in both gosst-http and server.py. The ones in server.py has to go. Additionaly, the GPX API should also be implemented in gosst-http.

Fix dupicate imports

.SST files are moved to the uploaded directory when all the uploads are done, so if the upload process is somehow interrupted, the successfull imported sessions will be imported again on the next upload.

Fix Wiki TODOs

Recent changes have to be reflected in the README:

DAQ hardware build instructions
DAQ firmware build instructions on Windows

Allow importing PSST files

The PutSession function in gosst-http accepts raw SST files. It should also accept PSST files, so client-side converter applications could easily be written.

Caddy HTTPS certificate

Hello,

Unfortunately I'm more skilled on the hardware side than software (which looks impressive!)

I'm trying to run it in Docker desktop, and managed to get a successful build, however when trying to go to localhost:443, I get an "Client sent an HTTP request to an HTTPS server." error, or when using https://localhost:443, I get a "This site can’t provide a secure connection" - it seems like the default caddyfile is not providing a self-signed certificate. Is there a quick fix, or should I just try to build it on a web platform?

Add BLE GoPro control

As a possible solution to the video sync issue caused by the 1 second resolution timestamp on both the camera and DAQ, the DAQ should have a functionality to start recording on a paired GoPro when a session is started.

This seems pretty straighforward using OpenGoPro BLE specification. Officially only Hero 9 and later are supported, but https://github.com/KonradIT/gopro-ble-py states that the protocol is the same for Hero 5+ (at least for the minimal functionality I need here).

Add initial setup / configuration UI

Almost the entire database is accessible through the gosst-http API, we just need to write a user interface that makes adding calibrations, linkages, setups, etc. possible without issuing HTTP request from the command line.

Allow loading a video recording

Loading action camera footage and synchronizing it to the travel plot crosshair would probably make identifying interesting sections of a trail easier than using the map. I don't want video uploading though, so this feature will only support video loading from local system.