Do you have any code examples for the ADISUSB evaluation system?
The ADISUSB provides support for most of the iSensor products (ADIS16xxx). The original purpose of the ADISUSB was to provide demonstration of the basic functions in each iSensor device, along with some basic data capture that would support parametric characterization. It was not designed to provide a real-time, synchronous interface at the maximum sample rate for each iSensor device. For example, when evaluating the ADIS16334, with six output registers in a data capture, the ADISUSB will support approximately 200 samples per second. For this reason, we never developed a software development kit (SDK) for this system. Having said that, we have developed an unofficial DLL, which is written in VB6 (yes, we know that it is old and have moved to *.NET for the EVAL-ADIS software development).
The attached file contains some C++ files, which a customer shared with us. We have not tested these files ourselves, but understand that they served as a good starting point for some engineers that we have shared them with.
Here are the instructions that came with the files:
When using the class I sent you, the programmer first need to create an instance of the ADISUSBX class and after it need to call Initialize method. This method need on parameter called aDeviceName. This parameter indicate the hardware device to communicate to. When connecting the AnalogDevice evaluation board, Windows recognize the hardware device, install the needed driver and gave it a name a programme use to connect to. Windows name the first discovered AnalogDevice evaluation board “\\.\Ezusb-0”. So, a C/C++ programmer wanting to talk with the device will call Initialize this way:
lUsbX.Initialize( “\\\\.\\Ezusb-0” );
Remember that the SPI interface on the iSensor devices, such as the ADIS16334, enable a simple connection with an embedded processor. If you include a line for data-ready, this requires 5-connections with a processor, along with power and ground. Most procesors have dedicated lines and registers for managing SPI devices, so the firmware for managing SPI communications is fairly simple. For those who want to save time and have more flexibility in their early evaluation projects, developing an embedded interface is efficient and provides flexibility in data management as well.
For more information on connecting to an embedded processor with the SPI, see the product datasheet (ADIS16488, for example) and following posts:
Retrieving data ...