]>
Commit | Line | Data |
---|---|---|
1 | ------------------------------------------------------------------------------- | |
2 | PulsedLight3D LIDARlite module | |
3 | ------------------------------------------------------------------------------- | |
4 | ||
5 | This is the capture of data output from a LIDARlite module with various short | |
6 | range distances. | |
7 | ||
8 | Each 10 uS the PWM/MODESEL line is high equals one centimeter, and continuous | |
9 | trigger is enabled via keeping the line strongly low. For long distances the | |
10 | rate can be limited due to the longer time to PWM the distance than processing | |
11 | time for the next sample. | |
12 | ||
13 | Details: | |
14 | - Sparkfun product page: | |
15 | * https://www.sparkfun.com/products/13167 | |
16 | - LIDARlite product spec + developer docs: | |
17 | * http://kb.pulsedlight3d.com/support/home | |
18 | ||
19 | ||
20 | Logic analyzer setup | |
21 | -------------------- | |
22 | ||
23 | The logic analyzer used was a Saleae Logic16 (at 5MHz): | |
24 | ||
25 | Probe LIDARlite | |
26 | --------------------- | |
27 | 1 (black) Mode select pin | |
28 | ||
29 | Note: The 'Mode select' pin is pulled low strongly with 1K ohm resistor | |
30 | to trigger continuous sampling). | |
31 | ||
32 | ||
33 | Data | |
34 | ---- | |
35 | ||
36 | The data contains various PWM encoded distances. | |
37 | ||
38 | The sigrok command line used was: | |
39 | ||
40 | sigrok-cli --driver saleae-logic16 --samples 100M --config samplerate=5mhz \ | |
41 | -C 0=PWM -o lidarlite_5mhz.sr |