|
1 | 1 | # LIS3DH Examples #
|
2 | 2 |
|
3 |
| -All examples are configured to run on an [impExplorer Kit](https://developer.electricimp.com/hardware/resources/reference-designs/explorerkit). Each example shows simple usage of the accelerometer interrupts. All code runs on the device side only, no agent code is needed. |
| 3 | +All examples are configured to run on an [impExplorer™ Kit](https://store.electricimp.com/collections/getting-started/products/impexplorer-developer-kit?variant=31118866130). Each example shows simple usage of the accelerometer interrupts. All code runs on the device side only, no agent code is needed. |
4 | 4 |
|
5 | 5 | ## Click Interrupt ##
|
6 | 6 |
|
7 |
| -This example configures a double click interrupt. The device will create a log each time a double click event is captured. |
| 7 | +This example configures a double-click interrupt. The device will create a log each time a double-click event is captured. |
8 | 8 |
|
9 | 9 | ### Device Code ###
|
10 | 10 |
|
11 |
| -Copy and paste the [code](./simpleClickInterrupt.example.device.nut) into the device coding window in impCentral. |
| 11 | +Copy and paste the [code](./simpleClickInterrupt.example.device.nut) into the device coding window in impCentral™. |
12 | 12 |
|
13 |
| -## Free Fall Interrupt ## |
| 13 | +## Free-fall Interrupt ## |
14 | 14 |
|
15 |
| -This example shows how to put the imp into deep sleep and configure wakes based on a timer expiring or a free fall event condition detection. When the device wakes on a timer it will take and log a reading. If a free fall event is detected it will log the event. A free fall event can be triggered by throwing the device in the air. |
| 15 | +This example shows how to put an imp into deep sleep and configure wakes based on the firing of a timer or a free-fall event condition detection. When the device wakes on a timer it will take and log a reading. If a free-fall event is detected it will log the event. A free-fall event can be triggered by throwing the device up in the air. |
16 | 16 |
|
17 | 17 | ### Device Code ###
|
18 | 18 |
|
19 | 19 | Copy and paste the [code](./simpleFreefallInterrupt.example.device.nut) into the device coding window in impCentral.
|
20 | 20 |
|
21 | 21 | ## FIFO Streaming Interrupt ##
|
22 | 22 |
|
23 |
| -This example configures the FIFO buffer in streaming mode and also configures a FIFO watermark interrupt that triggers when the buffer is almost full. When the interrupt is triggered the readings in the buffer will be checked and logged in a quick burst, preventing a buffer overflow. The stream & interrupt are stopped after a set time, since this example creates numerous logs. |
| 23 | +This example configures the FIFO buffer in streaming mode and also configures a FIFO watermark interrupt that triggers when the buffer is almost full. When the interrupt is triggered, the readings in the buffer will be checked and logged in a quick burst, preventing a buffer overflow. The stream and interrupt are stopped after a set time, since this example creates many log entries. |
24 | 24 |
|
25 | 25 | ### Device Code ###
|
26 | 26 |
|
27 | 27 | Copy and paste the [code](./simpleFIFOStream.example.device.nut) into the device coding window in impCentral.
|
28 | 28 |
|
29 |
| -## Motion & Impact Monitoring ## |
| 29 | +## Motion And Impact Monitoring ## |
30 | 30 |
|
31 |
| -This example configures the FIFO buffer, a high pass filter and an inertial interrupt. The high pass filter and inertial interrupt are configured to trigger an interrupt when movement is detected. When the interrupt is triggered the FIFO buffer will fill up, storing readings immediately after the motion event was detected. The interrupt handler then looks for the maximum reading captured in the stored readings from the FIFO buffer before clearing and resetting the buffer. |
| 31 | +This example configures the FIFO buffer, a high-pass filter and an inertial interrupt. The high-pass filter and inertial interrupt are configured to trigger an interrupt when movement is detected. When the interrupt is triggered, the FIFO buffer will fill up, storing readings immediately after the motion event was detected. The interrupt handler then looks for the maximum reading captured in the stored readings from the FIFO buffer before clearing and resetting the buffer. |
32 | 32 |
|
33 | 33 | ### Device Code ###
|
34 | 34 |
|
|
0 commit comments