Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| en:iot-open:remotelab:sut:roboarm:b1 [2019/03/19 15:55] – gdrabik | en:iot-open:remotelab:sut:roboarm:b1 [2020/07/20 09:00] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ==== Controling stepmotor and monitoring it using accelerometer on LCD ==== | ==== Controling stepmotor and monitoring it using accelerometer on LCD ==== | ||
| - | //Students should check position the arm, and display it on display. For confirmation propriety of readings, student should move the arm using servo motor// | + | Students should check position the arm, and display it on display. For confirmation propriety of readings, student should move the arm using stepmotor. |
| === Target group === | === Target group === | ||
| - | //This hands-on lab guide is intended for the Beginners.// | + | This hands-on lab guide is intended for the Beginners. |
| === Prerequisites === | === Prerequisites === | ||
| - | //Generally students need skill using I2C bus. For realising scenario, students need access to documentation for registers of sensors (accelerometer), | + | Generally students need skill using I2C bus. For realising scenario, students need access to documentation for registers of sensors (accelerometer), |
| === Scenario === | === Scenario === | ||
| - | - using schematic, check ESP ports with I2C controlled, | + | - using schematic, check ESP ports which I2C controlled, |
| - | - using sensor documentation check registers | + | - using schematic, check ESP ports which DIR and STEP (stepmotor) |
| + | - using sensor documentation check registers | ||
| - using display documentation check way for display digits on HD44780, | - using display documentation check way for display digits on HD44780, | ||
| - check I2C address for every device, | - check I2C address for every device, | ||
| - write the program loop which: | - write the program loop which: | ||
| - | * send command for reading | + | * send command for reading |
| * wait for processing | * wait for processing | ||
| * transform result for display | * transform result for display | ||
| - | * send this to display interface | + | * send this to display interface, |
| - | * send command | + | * send command |
| * wait for processing, | * wait for processing, | ||
| * transform result for display, | * transform result for display, | ||
| * send this to display interface. | * send this to display interface. | ||
| + | * move one step a stepmotors. | ||
| - using the camera observe display and check credibility of displayed value. | - using the camera observe display and check credibility of displayed value. | ||
| + | NOTE: arm move only in 2 accelerometer axis. Reading of acceleration from third axis should be constant. (or with small fluctuations) | ||
| === Result === | === Result === | ||
| - | //Describe expected result when scenario is finished.// | + | On display should be visible acceleration for every axis. (always below 1G). |
| === Start === | === Start === | ||
| - | //Write starting conditions, i.e. what to do at the beginning, what to pay attention before beginning, how the mechanical part should look like, etc.// | + | |
| === Steps === | === Steps === | ||
| - | // Write some extra information if i.e. some steps are optional otherwise cancel this paragraph (but do not remove header).// | ||
| - | == Step 1 == | ||
| - | //Describe activities done in Step 1.// | ||
| - | ... | ||
| - | == Step n == | ||
| - | //Describe activities done in Step n.// | ||
| === Result validation === | === Result validation === | ||
| - | //Provide some result validation methods, | + | Only way for validation is check display by camera. |
| === FAQ === | === FAQ === | ||
