Main/99 Work/0 OneSec/OneSecNotes/Handover Planning.md

title, created_date, updated_date, aliases, tags

title	created_date	updated_date	aliases	tags
Handover Planning	2025-12-18	2025-12-18

Handover Planning

home office tomorrow:

• Loom video of meta data system
• Loom video of VPS in general
• Loom video of rustdesk and log portal
• Code review

Active Work

• Get Propulsion System to work
• get the battery pack to work
  • do thermal tests with different thermal pads
  • finalize v1.0.0 of battery driver.
• Setup Vidit for self sufficiency
  • review pcbs
  • system

Projects

• PCBs and electronics
  • PCB and electronics hands on work
  • review system
  • google drive system.
  • OKRs for Vidit
• Simulator
  • explain the meta data system in detail in a loom video
  • explain meta data analyzer and how to use it
  • explain meta data analyzer and how to extend it
  • merge the meta data analyzer
• VPS
  • log portal
  • n8n
  • rustdesk
• Software
  • battery driver
  • teststand
  • autopilot?
  • flightcontroller?
  • auto review system (active work)
  • teensy tester software stack.
• hardware
  • battery pack --> learnings from Jakub
• Admin
  • hiring advice and report.
  • jira system

Todos

Admin

• Pensionskasse access?
• PK: alles korrekt eingezahlt?
• Verträge unterschrieben

VPS

• Create a loom video and update the confluence article.
  • explain how to access it
  • explain tech stack (caddy, docker, docker compose)
  • explain that we have 2 vpses (main one with netcup, n8n one with hostinger)
  • explain each application we're actively hosting
  • explain working principle of the logserver, API, etc. create documentation therefore. also a loom video on how its built and how it works.

Electronics and PCB

• Do detailed planning with Vidit with OKRs --> make clear that he has ownership now. He is responsible that the quality assurance is good, etc.
• Finalize the current set of PCBs and test extremely throughly
  • Rotorhead boards
  • propulsion harness
  • wiring harness
  • upper pdb
  • lower pdb

BMS

• golden file still missing
• driver is flaky: what registers do we want to read at what frequency?

---

Future

Flightcontroller

• update chirp to not use std::vector and then update the logging path to not use std::vector. this uses dynamic allocation and can cause heap fragmentation
• implement a watchdog --> safe the current state into a reboot safe memory location and if a watchdog resets the flightcontroller you can immediately recover the flightstate.
• use smaller software watchdogs to ensure that the control loop is executed correctly () --> e.g. that the SD logging does not block the control loop.
• similarly there should be an i2c bus recovery method. if a chip breaks, it might corrupt the i2c line, thus all other chips are not reachable --> we need to recover this.