You are reading a single comment by @ioi-655321 and its replies. Click here to read the full conversation.
  • I realized the the error Uncaught InternalError: Timeout on I2C Write BUSY was because of bad header pins! I somehow got a batch of headers that didn't have any beveling on them, this caused damage to my solderless breadboard and contrsibuted to a poor connection. I always use high quality solderless breadboards to reduce issues but I never anticipated bad header pins!

    I think how the module initiates the MPU isn't perfect but it does work well enough for my purposes. If I have time , I might go though the module and modify it for myself. I want to see if I can make initialization more consistent and I want to eliminate verbose warning and error messages. My end goal it to interface my "robot" with an app on my phone(written with droidscript) . I like being able to interface directly using the console over BLE (jolt), it is very powerful and is one of the best features of the espruino environment. I don't want to filter all these warning messages from the module. The "puck" addon in Droidscript works flawlessly for interfacing with the espruino console over BLE and I have been using that for a bunch of little things. I like that I can program any BLE Espruino with my phone. I wrote a droidscript app with a dropdown menu of programs that I can upload at-will to espruino and it is very handy!

    When I get home from work I will try to use the soft I2c connection to see if it helps with MPU initialization, thanks for the suggestion! I forgot that I can do that.

    Keep up the good work with Espruino, It is by far my favorite platform for tinkering.

About

Avatar for ioi-655321 @ioi-655321 started