ADIS16375 Connection/Operational Requirements

I am experiencing strange behaviour with the ADIS16375 which i mounted on the ADIS16IMU1/PCBZ.

When connecting the device to the microcontroller and power supply I am not able to get feedback. This is not the case every time. For example, when I wrote the previous post I could communicate with the device perfectly. When I finished with my tests I disconnected everything and stored them away. Today I connected the hardware and using the same firmware on the microcontroller I cannot communicate with the device at all. From the power supply I can see that it is drawing current, but it does not supply any output on the MISO pin. In addition I cannot see it driving the DIO2(INT) pin.

Should I place any resistors on the MISO and INT pins ?

Also, I am supplying 3.5V at 2A max. When reading the wiki guide for evaluation with the ADISUSB board, it states that :

The following picture (left side) shows JP1 in the +3.3V position (factory-default). Change the JP1 jumper setting on the ADISUSB to the +5Vposition (shown on the right) required for the ADIS16375AMLZ

Should I power the board with 5V instead of 3.3V ? I am a bit confused.

Thank you for your time.

Message was edited by: Mark Looney to focus on the contents that relate to the new question.

  • I hope that you do not mind, but I branched this to a new discussion because we are trying to keep each discussion focused on one question, for each of search/find in the future.  We appreciate your confirmation in the original message and will be glad to help.

  • First, thank you for the feedback on the ADIS16375 Evaluation on the ADISUSB Wiki Guide. The note that states that the JP1 should be +5V was incorrect and has already been corrected, based on your feedback. We appreciate you telling us about this. Here is the link for reference:

  • Second, I would consider the following opportunities for differences between the two setups:

    1. Power supply behaviors during the transient current demand associated with start-up, which can reach a peak of 1.5A and have a pulse width of 400us. You can use a digital scope to trigger on any negative transition that dips below 3.1V to look for dips or transient behaviors that can come from inductance in cables combining with the 24uF of capacitance inside of the ADIS16375.
    2. Noise on the ~RST line, perhaps make sure this is a solid high.
    3. Probe the SPI signals while looping on a single register to create a consistent read pattern. In this mode of operation, you can use a scope to trigger off of CS high-to-low transitions, to get a consistent pattern on all four SPI signals. This is a good way to look for ringing, noise and other signal integrity issues.

    I hope that this helps.

  • Thank you very much clearing that out and moving my question to a different thread.

    If you could provide me with some pointers as to the hardware connection for SPI communication I would be grateful.

    I am using TI's Tiva microcontroller and I can have pins setup with a weak pull-up or pull-down or open-drain.

    Each pin has a maximum drive strength of 8mA.

    Since I'm more of a software guy I cannot conclude on the proper configuration. Should I add/remove resistors on any of the SPI (CLK,MISO,MOSI,CS), DIO or RST pins ? Right now I have the RST pin unconnected.

    Using a logic analyzer I power up the ADIS16375 IMU and attempt to detect the interrupt on DIO2 but with no luck so far.

  • From a general-purpose point of view, this blog post gives a list of typical challenges and solutions that we have observed in helping many other customers work through their initial connection process. I hope that this helps.

    Connecting to Smart Sensors, it Takes More Than Code