|
11 | 11 | This document describes the setup requirements for demonstration of I2C communication on the hardware platform |
12 | 12 | [EV74H48A](https://www.microchip.com/en-us/development-tool/EV74H48A) "Curiosity Platform Development Board" and [EV02G02A](https://www.microchip.com/en-us/development-tool/EV02G02A) "dsPIC33AK128MC106 General Purpose Dual In-Line Module (DIM)" using MPU9250 sensor on the MPU 9DOF Click Board.</p> |
13 | 13 |
|
14 | | -MPU-9250 is a multi-chip module (MCM) with 9-axis MotionTracking device that combines a 3-axis gyroscope, 3-axis accelerometer, 3-axis magnetometer and a Digital Motion Processor™ (DMP). This example uses all the three sensors to estimate the roll, pitch and yaw angles. |
| 14 | +MPU-9250 is a multi-chip module (MCM) with 9-axis Motion Tracking device that combines a <b>3-axis gyroscope, 3-axis accelerometer, 3-axis magnetometer and a Digital Motion Processor™ (DMP)</b>. This example uses all the three sensors to estimate the roll, pitch and yaw angles. |
15 | 15 |
|
16 | 16 | ## 2. SUGGESTED DEMONSTRATION REQUIREMENTS |
17 | 17 |
|
18 | 18 | ### 2.1 MATLAB Model Required for the Demonstration |
19 | 19 |
|
20 | 20 | To clone or download this MATLAB model on GitHub, |
21 | 21 |
|
22 | | -- MATLAB model can be cloned or downloaded as zip file from the Github repository ([link](https://github.com/microchip-pic-avr-solutions/matlab-dspic33a-curiosity-i2cexample-mpu9250)). |
| 22 | +- MATLAB model can be cloned or downloaded as zip file from the Github repository ([link](https://github.com/microchip-pic-avr-examples/matlab-dspic33a-curiosity-i2cexample-mpu9250)). |
23 | 23 |
|
24 | 24 | ### 2.2 Software Tools Used for Testing the MATLAB/Simulink Model |
25 | 25 |
|
@@ -58,7 +58,7 @@ This section describes the hardware setup required for the demonstration. |
58 | 58 | <p align="left" > |
59 | 59 | <img src="images/microbusA.png"width="500"></p> |
60 | 60 |
|
61 | | -3. The development board has an onboard programmer **PICkit™ On Board (PKoBv4)** , which can be used for programming or debugging the microcontroller or dsPIC DSC on the DIM. To use the onboard programmer, connect a micro-USB cable between the Host PC and **connector J24** on the development board. |
| 61 | +3. The development board has an onboard programmer **PICkit™ On Board (PKoBv4)**, which can be used for programming or debugging the microcontroller or dsPIC DSC on the DIM. To use the onboard programmer, connect a Micro-C® cable between the Host PC and **connector J24** on the development board. |
62 | 62 |
|
63 | 63 | The development board is also powered by this USB itself. |
64 | 64 |
|
@@ -97,44 +97,44 @@ This section describes the hardware setup required for the demonstration. |
97 | 97 | </p> |
98 | 98 |
|
99 | 99 | > **Note:** </br> |
100 | | - >Two COM ports are available on the development board. Select the second COM port number for the external mode (if COM2 and COM3 are available on the development board, select COM3). |
| 100 | + >The PKOB4 based USB-UART Channel is used in this example for USB-UART communication. The development board has a 2-port USB hub. |
101 | 101 |
|
102 | 102 | 6. <p style='text-align: justify;'> To generate the code and run the I2C communication on hardware, click on <b>"Monitor & Tune" </b> option under the <b>Hardware</b> tab and ensure that <b>"Stop Time" </b> is set to <b>"inf"</b>. |
103 | 103 |
|
104 | 104 | <p align="left"> |
105 | 105 | <img src="images/dem6.png"width="500"></p> |
106 | 106 | </p> |
107 | | -7. <p style='text-align: justify;'> After compilation and programming the device. The external mode will be running on the dsPIC. |
| 107 | +7. <p style='text-align: justify;'> After compiling the code and programming the device, External Mode will be activated on the dsPIC DSC. |
108 | 108 |
|
109 | 109 | <p align="left"> |
110 | 110 | <img src="images/dem7.png"width="500"></p> |
111 | 111 |
|
112 | | - </p><p style='text-align: justify;'> The <b>General Purpose LED's</b> will be blinking. |
| 112 | +8. </p><p style='text-align: justify;'> The <b>General Purpose LED's</b> will be blinking. |
113 | 113 |
|
114 | 114 | <p align="left"> |
115 | 115 | <img src="images/debug_led.png"width="500"></p> |
116 | 116 | </p> |
117 | 117 |
|
118 | | -8. <p style='text-align: justify;'> The <b> RGB LEB</b> will be glowing in different colors. To increase the brightness of the RGB LED, vary the <b>Potentiometer</b> on the development board. |
| 118 | +9. <p style='text-align: justify;'> The <b> RGB LEB</b> will be glowing in different colors. To increase the brightness of the RGB LED, vary the <b>Potentiometer</b> on the development board. |
119 | 119 |
|
120 | 120 | <p align="left"> |
121 | 121 | <img src="images/led_rgb.png"width="500"></p> |
122 | 122 | </p> |
123 | 123 |
|
124 | | -9. <p style='text-align: justify;'> To view the estimated roll, ptch and yaw angles from the <b>accelerometer, gyroscope and magnetometer sensors of MPU9250</b> double click on the scope. This opens the scope view. Tilt or turn the development board by hand to view variations in the roll, pitch and yaw angles. |
| 124 | +10. <p style='text-align: justify;'> To visualize the estimated roll, pitch and yaw angles from the <b>accelerometer, gyroscope </b> and <b> magnetometer</b> sensors of <b>MPU9250 </b> double click on the scope. This opens the scope view. Tilt or turn the development board by hand to view variations in the roll, pitch and yaw angles. |
125 | 125 |
|
126 | 126 | <p align="left"> |
127 | 127 | <img src="images/dem9.png"width="500"></p> |
128 | 128 | </p> |
129 | 129 |
|
130 | | -10. <p style='text-align: justify;'>Click on the <b>Stop</b> button to stop the I2C communication and external mode. |
| 130 | +11. <p style='text-align: justify;'>Click on the <b>Stop</b> button to stop the I2C communication and external mode. |
131 | 131 |
|
132 | 132 | <p align="left"> |
133 | 133 | <img src="images/dem10.png"width="500"></p> |
134 | 134 | </p> |
135 | 135 |
|
136 | 136 | > **Note:** </br> |
137 | | ->Ensure that at startup, the **development board** and **MPU9250** remain static and level for about 2 seconds for calibration. After calibration, the board can be tilted or rotated to observe angle variations. |
| 137 | +>At each startup, the system calibrates the **accelerometer, gyroscope** and **magnetometer** of the **MPU 9DOF Click board**. During this 2-second calibration period, the **development board** and **MPU 9DOF Click board** must remain stationary (do not move/ shake). After calibration, the board can be tilted or rotated to observe angle variations. |
138 | 138 |
|
139 | 139 | ## REFERENCES: |
140 | 140 | For more information, refer to the following documents or links. |
|
0 commit comments