Is there anyway to get more distance between the ADIS16488 and the EVAL-ADIS? I am not sure if 12 inches will be enough.
All iSensor devices use the Serial Peripheral Interface (SPI) protocol for data communications with embedded processors. The SPI is a synchronous interface, which transmits and receives data, using a serial clock to “trigger” bit transitions (transmit) and sampling (receive). It uses four signals: chip-select (CS), serial clock (SCLK), data-input (DIN) and data output (DOUT). This protocol has no inherent error checking and relies on “decent” signal integrity to provide reliable and accurate data communications.
The EVAL-ADIS was designed to support a direct connection with iSensor devices, such as the ADIS16488AMLZ. This post discusses the use of the ADIS16488/PCBZ to help facilitate a remote connection: http://ez.analog.com/message/44679#44679
In order to use the EVAL-ADIS to communicate with a remote device, such as the ADIS16488/PCBZ, additional circuit functions can help mange signal integrity and EMI influences that are often associated with standard cabling systems. We typically suggest that when the cable length must be greater than 12 inches, that the system use buffers, with Schmidt-triggered inputs, to help manage the signal integrity. When used on the “transmit” side of a signal, the output buffers provide additional drive current, which helps “sharpen” the signal transitions. When used on the “receive” side, the Schmitt-triggered input buffers reduce noise sensitivity and “false triggers” that can result from cabling/EMI exposure. The EVAL-ADIS transmits the CS, SCLK, and DIN signals, while the remote iSensor device transmits the DOUT and DIOx signals (when they are configured for output I/O functions, such as data-ready). In ADI test systems, using the Schmidt trigger devices in both “host” and “remote” locations has led to the most reliable communication.
Retrieving data ...