Sunday, May 28, 2017

Day 21

Topics

  • EEProm
  • MPU9255
EEprom

    I setup the component as was outlined in the lab. 



    I ran the first program after making the changes in code to account for a the changes in the library over time. 



   I am not entirely certain what this was actually doing.  OOOOOO; now I see. It's writing random numbers to the EEprom at the specific address and then telling me what the address has.  I loaded the next part of the lab but didn't get the same thing I got during class. I am trying to remember what I had to do during class to fix it. 


   I must have been mistaken. As I reviewed the code, it appears "DATA READ" is the only thing sent to the serial monitor. I added some Serialprints to satisfy my mind, as to the efficacy of the loops. Not a problem.



MPU9255

   I could attempt lying (conduct unbefitting a gentleman) but that seems needless. We were instructed to break up these labs between the group members. I worked on logging data and getting the sweeper working while Ed go this sensor to work. I now shamelessly report on what sense I can make of it, post hoc. Clearly this sensor needed some header files, I suppose another library would also work.  There also an object made from the MPU9255 class.



   Then we have some class specific function that are initialize the sensors on the board. I can see at the end there is a reference between the millis() count and an myIMU.count. possibly has it's own crystal. I wonder what the the difference between the two clocks gives? 



    Wait! the line before! I think it's grabbing the millis time in the timerupdata and then using that to mark change. Then, the line after the counter one has a change in time being half a second.  I could change that number if i wanted to increase collection rate, I bet. Lets check.



   That worked! The next part is a straightforward printing of data. Adapting this or the project shouldn't be difficult. 




No comments:

Post a Comment