Week 17

Sharing Krypto Support with the world

Krypto Support was born from a personal need — monitoring my dog's IVDD condition — but the concept applies to any pet owner dealing with neurological or mobility conditions. The dissemination plan focuses on making the project fully reproducible by others and reaching the communities that would benefit most.

Licensing strategy

The project has three distinct layers — hardware, software, and documentation — and each one uses the license best suited to its type. The common thread is that all three are permissive and open: anyone can use, modify, and redistribute the work, as long as they give attribution and share improvements under the same terms.

From prototype to impact

The current prototype solves one problem for one dog. The following outlines how to turn future possibilities into concrete probabilities — with specific actions, not just wishes.

What tasks have been completed, and what tasks remain?

What's working? What's not?

What questions need to be resolved?

• ? What is the optimal IMU sampling rate to balance data quality and battery life? (Testing 10Hz vs 50Hz vs 100Hz)
• ? Should alerts trigger on raw threshold crossings or on a rolling average to avoid false positives?
• ? How to waterproof the enclosure seam without making the PCB inaccessible for debugging?
• ? What data visualization format is most intuitive for a vet who has never seen IMU data before?
• ? Can the vest pattern be simplified so someone without sewing experience can assemble it?

Planned — what will happen when?

Reflections

Building Krypto Support has been a journey through every discipline in Fab Academy and the most important lesson is that a real project forces you to connect them all. Electronics design is not separate from garment design when the PCB has to fit inside a pocket sewn into a vest worn by a living animal. Firmware is not separate from user interface when the data you transmit has to make sense to a veterinarian who has never seen an accelerometer reading.

Some specific things I've learned along the way:

• 1 KiCad from zero — I had never designed a PCB before Fab Academy. Going from a blank schematic to a milled, soldered, working board was one of the steepest and most satisfying learning curves.
• 2 Designing for a living user — a dog can't tell you the vest is uncomfortable. I learned to observe Krypto's body language and iterate the garment based on how he behaves, not on what looks good on paper.
• 3 System thinking — each subsystem (sensor, processor, garment, dashboard) depends on decisions made in every other subsystem. Planning the integration before fabrication saved weeks of rework.
• 4 I2C debugging — getting the MPU-6050 to communicate reliably taught me to read datasheets carefully, check pull-up resistors, and use a logic analyzer when serial prints aren't enough.
• 5 Documentation as design — writing clear documentation while building (not after) helped me catch design flaws early and make better decisions.
• 6 Open source is a responsibility — publishing files isn't enough. Good documentation, clear licensing, and a readable README are what make a project actually reproducible by someone else.