You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+8-2Lines changed: 8 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -140,7 +140,13 @@ The same behaviour was observed when we tried to *read a register*. The first pi
140
140
141
141
## 4 - Future
142
142
143
-
### 4.1 - Wakeup-mode
143
+
### 4.1 - Process the data
144
+
145
+
Right now data doesn't really get read in by the sensor, only the LED is turned on and the interrupt on the accelerometer is cleared if necessary. In the future this could change.
146
+
147
+
<br/>
148
+
149
+
### 4.2 - Wakeup-mode
144
150
145
151
The accelerometer can be put in a `wakeup-mode` where he only consumes about **270 nA** (@2.0V) and measures the acceleration *about six times per second* to determine whether motion is present or absent. If motion is detected, the accelerometer can respond autonomously in the following ways:
146
152
@@ -154,7 +160,7 @@ In wake-up mode, all accelerometer features are available with the exception of
154
160
155
161
<br/>
156
162
157
-
### 4.2 - FIFO and wave frequency
163
+
### 4.3 - FIFO and wave frequency
158
164
159
165
We can perhaps use the `FIFO` to store measurements at an optimal `ODR` (Output Data Rate) so the **wave frequency** can be calculated using *FFT* functionality available in `CMSIS` libraries. The accelerometer could fill this FIFO on it's own and signal to the microcontroller when it is filled by using an interrupt (there is still one pin unused). Then the microcontroller can read all these values at once and calculate the frequency, after which he again goes to sleep. *We also need to look into the amount of samples we need for this to work.*
0 commit comments