AD7175-2 GPIO Input -- Logging digital inputs in AD717x Eval+ Software

Hi, 

I'm sorry I am confused with the question, are you trying to monitor the status of the GPIO pins and somehow wanted to display it in the waveform tab? 

Unfortunately, the EVAL+ software waveform tab only displayed the measurement across ADC inputs. It does not allow options to log the GPIO Data.

The GPIO data can be read from GPIO configuration register. If GPIO 0 input is enabled then the GPIO 0 will serve as an input and the GPIO Data will read its status. So in order to log this you need to keep reading the GPIO Con register, but like I have mentioned that EVAL+ software does not log this automatically. 

So if you want to log it using the EVAL+ somehow you can probably just use the AIN pins to connect the signal from the GPIO pins externally and select it as an additional input to your ADC. Please make sure that the Reference voltage is equal to AVDD as the GPIO voltage levels is based on AVDD supplies. 

Thanks,

Jellenie

Hi Jellenie,

Why no engineer give me one response for my questions about ADC, AD9083?

I have wait for nearly one week.

May you help me contact the relative expert?

Best Regards,

Nan

Hi Nan, 

Apologies for keeping you waiting. Can you share me the thread so I can follow up? 

Thanks,

Jellenie

Hi Jellenie,

Thanks for the information provided in your reply. 

I do recognize that signal bit digital signals can be externally connected to an analog inputs, but this slows down the sampling rate due to the MUX setting time when switching between channels.

Maybe I can try to explain my question a bit better to ensure that it does not lead to any confusion.

In the Eval+ Software, near the upper right corner there is “Sampling Mode” selection box.  My question is about the data written to the .csv file, when “Data Logging” is selected, not displaying it along with the waveforms. 

For the analog inputs, under the “Configuration” Tab, clicking on the “+” for the Crosspoint Multiplexer allows any combination of the four (4) analog inputs to be selected using the “Channel Enable” checkboxes.  This selection causes the selected channels to be added to the log file.

For the digital inputs, under the “Configuration” Tab, clicking on the “+” for the GPIO and MUX I/O Control, shows several checkboxes including “GPIO 0 Input Enable” and “GPIO 1 Input Enable”.  However, these selections do not cause the GPIO inputs to be added to the log file. 

Logging both analog and digital inputs is of interest to evaluate this family of ADCs during the proof-of-concept phase of a current and active product development.

If the functionality of logging GPIO Inputs is not presently possible, please consider it adding to a future revision of the Eval+ software, to help other customers.  We may need to consider the time required to write software for a better evaluation of these ADCs.

Thank You

Hi Nan, 

I have coordinated this to the HS Apps team. I would also recommend to just focus or post in one thread if it all happen to be the same project/issue. 

Thanks,

Jellenie

Hi, 

Regarding your question about the cross mux, yes when you enabled other channels then it will be included in the log because it is an ADC measurement results. Like I mentioned the data logging is somehow similar to the waveform tab. It only display measurement results across ADC inputs. And the purpose of cross mux + sequencer is to select which AIN pins or internal input will be converted/measured across the ADC input. 

The MUX I/O in the GPIOCON serve different purpose, it allows the GPIO output to control external mux so that the switching will be synchronize to the conversion. The GPIO's can be monitor by reading the GPIOCON register. We don't see this type of request of continuously logging the GPIO status, but we can take note of this for future revision. But like I mentioned the only workaround for now is to measure it using the external AIN pins. 

Thanks again for your feedback and let's see how we improve this software in the future. 

Regards,

Jellenie