Untracked files
This commit is contained in:
parent
024a9bf692
commit
8f860ca853
Binary file not shown.
Binary file not shown.
|
@ -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
|
||||
|
Loading…
Reference in New Issue