ADIS16365 interface with dsPIC

We will be glad to help.  What is strange about the data you are observing in the y-axis accelerometer data?  What are they other sensors reading?  What orientation is the device in while you are measuring this?  In other words, what should we expect if it were operating normally?  Thanks! We appreciate your post and look forward to your response. 

Thanks for your response .. actually , all other sensors reading are perfect , accelerometer x is almost 0 , accelerometer z is -1 approximately , gyros are almost 0 and their values changes logically with ADIS16365  movement , supply voltage is 5 volt and temperature readings are perfect .

during these readings , i put ADIS16365 IMU  on a table  , so , i expected some offset value , but the problem was here :

accelerometer y readings came like this :

-7.022631

-8.945773

-4.63620

-9.459054

all these strange readings are coming without any change in ADIS16365  position ,  i replaced this IMU by a new one but the problem was same , so , could you please suggest any solution for this strange problem ?

it looks like the address of accelerometer y  is not 0x0C , but i checked it in the datasheet and it is 0x0C

so, any help ?

What units are you associating with these numbers?

G is the unit  .. so , for example , if we take -4.63620 as an output , that means acceleration y = -4.63620 * 9.8 = -45.43476 .. so, it is a strange output 

I agree with you; that is well outside of normal expectation.  Do you have anything connected to pins 22, 23 or 24? 

Sorry for late .. I checked these pins and nothing connected .. I used SA16375 IMU breakout board and I remove the jumper that connected to pin 23 .. so , nothing connected to these pins ..

Thank you for sharing this! To be honest, I am stumped.  Pins 22, 23 and 24 offer access to the analog portion of each accelerometer's signal chain.  This had utility in an early application, but when we discovered that it was so easy to introduce undesirable influence, we decided to make these pins into "no connect" lines. Since you have two units, which are doing the exactly the same thing, on the same axis, while the rest of the device continues to work well, it is hard to imagine this as some sort of random failure event.  Is there any chance the units were subjected to any handling or application shock that is beyond the rated levels in the datasheet?  I am not sure what else to look at, but if you are convinced that you are doing everything correctly in the digital signal processing portion of your system, we do have a failure analysis service, which you can request, through your original point of sale.  Since that group does not use this forum for their inputs, you will want to provided a clear summary of your observations, methods and data (with annotations to make highlights easy to find).  When our F/A team has little or no description of the behavior, they are very limited in what they can do.  You can reference this discussion, but it would help to make sure that a link to this discussion is included in the F/A request form.