{"id":40,"date":"2022-04-29T05:51:31","date_gmt":"2022-04-29T05:51:31","guid":{"rendered":"https:\/\/blogs.oregonstate.edu\/spudlaunching\/?p=40"},"modified":"2022-04-29T05:51:31","modified_gmt":"2022-04-29T05:51:31","slug":"week-5-i2c","status":"publish","type":"post","link":"https:\/\/blogs.oregonstate.edu\/spudlaunching\/2022\/04\/29\/week-5-i2c\/","title":{"rendered":"Week 5 – I2C"},"content":{"rendered":"\n

This week I’m trying out a different IMU, the MPU-9250<\/a>. The Raspberry Pi communicates with this unit using the I2C protocol which is accessed through the GPIO pins on the Pi instead of USB. The purpose of the I2C protocol is to allow many peripheral devices to communicate with one or more controllers. On the Raspberry Pi, the two other options for protocols are UART and SPI. UART is intended for communication between only 2 devices and has no clock syncing. SPI can communicate from one controller to many peripherals, but uses many more wires that I2C. <\/p>\n\n\n\n

I2C allows for communication between many peripherals and many controllers, has clock syncing, and does this all over two wires: SDA (serial data line) and SCL (serial clock line). So I2C is an ideal protocol for communicating with peripherals like the MPU-9250. The Raspberry Pi has GPIO pins for SDA and SCL lines, as well as power and ground. <\/p>\n\n\n\n

\"\"
The MPU-9250 plugged into the Raspberry Pi<\/figcaption><\/figure>\n\n\n\n

On the Pi, you can check what I2C devices are connected with the command i2cdetect -y 1<\/code>. This shows the address of each device. Right now the MPU-9250 is at the address 0x68. This is the address to use for accessing the IMU in an application.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Up next I will be creating a simple program to read this data and sync it with the GPS!<\/p>\n","protected":false},"excerpt":{"rendered":"

This week I’m trying out a different IMU, the MPU-9250. The Raspberry Pi communicates with this unit using the I2C protocol which is accessed through the GPIO pins on the Pi instead of USB. The purpose of the I2C protocol is to allow many peripheral devices to communicate with one or more controllers. On the […]<\/p>\n","protected":false},"author":12370,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-40","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/blogs.oregonstate.edu\/spudlaunching\/wp-json\/wp\/v2\/posts\/40","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blogs.oregonstate.edu\/spudlaunching\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.oregonstate.edu\/spudlaunching\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.oregonstate.edu\/spudlaunching\/wp-json\/wp\/v2\/users\/12370"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.oregonstate.edu\/spudlaunching\/wp-json\/wp\/v2\/comments?post=40"}],"version-history":[{"count":6,"href":"https:\/\/blogs.oregonstate.edu\/spudlaunching\/wp-json\/wp\/v2\/posts\/40\/revisions"}],"predecessor-version":[{"id":48,"href":"https:\/\/blogs.oregonstate.edu\/spudlaunching\/wp-json\/wp\/v2\/posts\/40\/revisions\/48"}],"wp:attachment":[{"href":"https:\/\/blogs.oregonstate.edu\/spudlaunching\/wp-json\/wp\/v2\/media?parent=40"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.oregonstate.edu\/spudlaunching\/wp-json\/wp\/v2\/categories?post=40"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.oregonstate.edu\/spudlaunching\/wp-json\/wp\/v2\/tags?post=40"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}