diff --git a/hardware/case/powerpcb_adaptor.FCStd b/hardware/case/powerpcb_adaptor.FCStd
new file mode 100644
index 0000000..6beb9ac
Binary files /dev/null and b/hardware/case/powerpcb_adaptor.FCStd differ
diff --git a/hardware/case/upper_part.FCStd b/hardware/case/upper_part.FCStd
new file mode 100644
index 0000000..6ce12c9
Binary files /dev/null and b/hardware/case/upper_part.FCStd differ
diff --git a/testsystem/plan.md b/testsystem/plan.md
new file mode 100644
index 0000000..ccdd608
--- /dev/null
+++ b/testsystem/plan.md
@@ -0,0 +1,36 @@
+
+Next steps:
+  - write firmware that gets motor instructions over http
+      - check motor driver parametrization
+      - think about data model for motor driver
+      - give sensible hostname to testdriving system
+  - manually start a test cycle and view in app
+  - for debugging write a python logger that shows current state in a graph (live)
+    and prints live prints the current logs
+     
+{"speeds":[-0.1, 0, 0.1, 0], "durations":[500, 1000, 500, 1000]}
+
+{"speeds":[0], "durations":[10]}
+
+
+
+
+Test could produce a html report with graphs and tables
+
+
+Short physical test:
+--------------------
+  Sequence:
+    - start session
+    - phase 1: no load
+      - check sample rate
+      - check min/max values
+      - output: graph, min, max
+    - phase 2: 
+      - periodic loading/unloading
+        - about 20 cycles
+      - run peak detector, compute cycles
+      - output: graph
+    - stop session
+    - download session
+  
\ No newline at end of file