Re: [Paparazzi-devel] IMU Failure/Freezing

[Gautier Hattenberger]

Hi,

The difference between v2.1 and v2.2 is the configuration of the SPI 
slave select line for the baro. Not sure how this can change the behavior.
According to your log, all the raw accel and gyro values are equal to 1 
(or -1 depending on the axis), which is not a really usual failing 
value. I would have expect either 0 or the last valid value.
I don't have an explanation for this actually. Maybe the people who 
wrote the aspirin driver have an idea. By any chance, do you have a 
logic analyzer (http://wiki.paparazziuav.org/wiki/Tools#Logic_Analyzer) 
to have an idea of what is happening on the SPI lines ?

Gautier

Le 20/04/2014 03:06, paparazzi_guy a écrit :
> Hey everybody,
>
> Thank you for all your input and different opinions regarding this matter.
> It has been much appreciated since we are scrambling to get everything to
> work before our competition.
>
> Today after our flight we tried updating the drivers again to aspirin_v2.2
> and it seems to be working outside now. The IMU did not freak out after five
> minutes of being outside with this new update. We then switched back to
> aspirin_v2.1 and the PFD became responsive within ten seconds. We then went
> back to aspirin_v2.2 and the IMU still appeared to be working. I am unsure
> why this solution wasn't working last night; maybe I wasn't flashing it
> correctly.
>
> We are tentatively excited about this and we will confirm that everything is
> working when we fly again tomorrow. Thanks again for your help!
>
> Matthew
>
>
>
> --
> View this message in context: 
> http://lists.paparazziuav.org/IMU-Failure-Freezing-tp15129p15149.html
> Sent from the paparazzi-devel mailing list archive at Nabble.com.
>
> _______________________________________________
> Paparazzi-devel mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/paparazzi-devel