The Trick-Tracker targets any user who is interested in tracking skill and improvement of certain fun sport devices. The Main focus of the first version are bikes but in general it can be used for any sort of sport devices which can be used to do stunts and tricks. It targets beginners as well as professionals to either compete or just compare skills like Wheelie/Manual driving distance, jump height and distance etc. how steep was that ride. What was the bike doing in its airtime while doing a trick. Visualize your tricks digital to go through them step by step to see what can be improved. Was the front wheel not high enough or maybe the angle to less during the landing.
MVP for Bikes:
- detect a jump
- measure height of the jump
- measure airtime of the jump
✓ Battery charging works incl. charging indicator LEDs!
✓ Reset and Event Button are running
✓ SD-Card works
The SD-Card Holder is pretty shitty and already kind of broke after a few times in and out. I created a 3D case which is about to be printed. With that case I can attach the device via the Wahoo connector to any bike.
I also wrote the code for data-logging to write the sensor data to the SD-Card. With this setup I can go out and collect data of different jumps and tricks on a bike which I then can throw into some TinyML processing tool like Edge Impulse or similar.
I still need to lean about machine learning on microntrollers.
✓ Battery charging works incl. charging indicator LEDs!
except that the LEDs are glimming if the LDO is disabled
❌ forgot to add GPIO0 to a button which was needed for flashing.
was able to patch it with a cable and disconnecting the btn1 button
❌ SD-Card is connected wrongly!
I use µSD-Card reader but connected the Pins like with default SD-Card. I thought the Pinout is the same but the default SD Card has one extra GND. Can not patch it :(
All in all I am happy that at least most of the things are working. I have to make new Boards to fix the SD-Card but before I am running more tests.
I am running a battery life-time test. The device is running for 7h+ with one charge being connected to WiFi sending continous data to the cloud. That will be more then sufficient for the use-case. Somehow my code dies at around 35% Battery life which seems a bit weird. Once restarted it runs just fine but now and then stops for no reason. But that might be a different issue because the device stays connected to WiFi and is reachable - just not sure what might causing that.