FAQ; EVAL-ADIS Software Development Tools, VB.NET DLL

Q:

Do you have a VB.NET software development kit (SDK) for  the EVAL-ADIS?

A:

--------------------------------------------------------------------------------------------------------------

The EVAL-ADIS provides a basic communication conduit between Windows-PCs and many of the iSensor products (ADIS16xxx).  It provides functional evaluation support to those who were also developing a direct interface between an ADIS16xxx product and their preferred SPI-compatible processor.  Custom software development is not listed as a "feature" or "promised function" in any of the EVAL-ADIS documentation, but the attached file provides a potential starting point for prototype data collection.  Download this file to access the VB.NET DLL file, along with an example VB.NET project. The project file provides examples for reading registers, writing to registers and a streaming data acquisition function.

Attachments:
Comments
Anonymous
  • in reply to NevadaMark

    Hello Everyone!

    We just posted a 64-bit version of this DLL at https://ez.analog.com/docs/DOC-17643

    Take care!

  • in reply to NevadaMark

    I just learned that I was incorrect in my expectation. This platform collects data using the embedded processor resource to capture and transmit data in batches, not sample by sample, over the USB.  So, it is not possible to use event-triggered requests at the PC, to collect samples from the IMUs on the EVAL-ADIS platform.  Sorry about that.

  • in reply to BMillikan

    I appreciate that, but we probably can't accept "as accurate as possible" as our objective.  I can imagine a number of limitations to this, some of which could be very expensive for us to address on this platform.  Let me give this a little more thought, but it might help to know which IMU you are evaluating with the EVAL-ADISx platform to evaluate.  Can you share that?

  • in reply to NevadaMark

    Let me give you some brief details of what we'd like to do.  We want to be able to put a high precision time-stamp on motion data for a platform.  It needs to be as accurate as possible.  So, we need to be able to capture the time when the measurement is generated.  If it is put into a queue without a timestamp, then we have no way of knowing when that sample was created.  We realize that this is a non-realtime, development system.  But, we are in the evaluation (R&D) stage and just need the ability to capture accurate, time-stamped motion data.

  • in reply to BMillikan

    I am not a software developer, but I was under the impression that the data reads in this SPI were triggered by the data-ready signal pulsing, which the IMUs provide for this exact purpose. Let me ask one of our developers if they can comment on this and get back to you.

Related