vault backup: 2026-02-04 12:13:30

Affected files:
.obsidian/workspace.json
99 Work/0 OneSec/OneSecNotes/Handover Planning.md

.obsidian/workspace.json

@@ -55,12 +55,12 @@
             "state": {
               "type": "markdown",
               "state": {
-                "file": "99 Work/Jobhunt/Interview Questions.md",
+                "file": "99 Work/0 OneSec/OneSecNotes/Handover Planning.md",
                 "mode": "source",
                 "source": false
               },
               "icon": "lucide-file",
-              "title": "Interview Questions"
+              "title": "Handover Planning"
             }
           },
           {
@@ -148,7 +148,7 @@
             }
           }
         ],
-        "currentTab": 9
+        "currentTab": 3
       }
     ],
     "direction": "vertical"
@@ -222,10 +222,10 @@
             "state": {
               "type": "file-properties",
               "state": {
-                "file": "0 Journal/0 Daily/2026-02-04.md"
+                "file": "99 Work/0 OneSec/OneSecNotes/Handover Planning.md"
               },
               "icon": "lucide-info",
-              "title": "File properties for 2026-02-04"
+              "title": "File properties for Handover Planning"
             }
           },
           {
@@ -268,12 +268,12 @@
             "state": {
               "type": "outgoing-link",
               "state": {
-                "file": "0 Journal/0 Daily/2026-02-04.md",
+                "file": "99 Work/0 OneSec/OneSecNotes/Handover Planning.md",
                 "linksCollapsed": false,
                 "unlinkedCollapsed": true
               },
               "icon": "links-going-out",
-              "title": "Outgoing links from 2026-02-04"
+              "title": "Outgoing links from Handover Planning"
             }
           },
           {
@@ -282,13 +282,13 @@
             "state": {
               "type": "outline",
               "state": {
-                "file": "0 Journal/0 Daily/2026-02-04.md",
+                "file": "99 Work/0 OneSec/OneSecNotes/Handover Planning.md",
                 "followCursor": false,
                 "showSearch": false,
                 "searchQuery": ""
               },
               "icon": "lucide-list",
-              "title": "Outline of 2026-02-04"
+              "title": "Outline of Handover Planning"
             }
           },
           {
@@ -460,12 +460,13 @@
       }
     ]
   },
-  "active": "df5aca211ac74a74",
+  "active": "27ad82034df6d692",
   "lastOpenFiles": [
-    "Temporary/My Health Products.md",
+    "99 Work/Jobhunt/Interview Questions.md",
     "0 Journal/0 Daily/2026-02-04.md",
-    "0 Journal/0 Daily/2026-01-28.md",
     "2 Personal/Lists/Business Ideas.md",
+    "Temporary/My Health Products.md",
+    "0 Journal/0 Daily/2026-01-28.md",
     "2 Personal/Lists/Packlisten/Packliste - Skitour.md",
     "0 Journal/0 Daily/2026-01-29.md",
     "99 Work/0 OneSec/OneSecNotes/Handover Planning.md",
@@ -483,7 +484,6 @@
     "2 Personal/Lists/Media/Bücher.md",
     "Attachments/ESPSomfyRTS 2026-01-18T16_26_16.backup",
     "Attachments/Pasted image 20260118150817.png",
-    "99 Work/Jobhunt/Interview Questions.md",
     "Temporary/Untitled 3.md",
     "2 Personal/Home Lab/Pangolin Installation.md",
     "0 Journal/0 Daily/2026-01-07.md",

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

@@ -71,4 +71,12 @@ tags:
 #### 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.