This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

ADS7142: Autonomous Mode GUI Operation

Part Number: ADS7142

Tool/software:

I have a customer who is using the ADS7142 2-Ch ADC and having some issues with the GUI interface in the Autonomous Mode. The customer's problem is lined up below:

"I selected it for an I2C based 2-Ch ADC with seemingly ease of integration.

However, I am having some difficulties with the GUI.

Our main use case would be the Autonomous Mode, in the Stop Burst mode (this way we can just go and read the sensor when we want and get the last 16 samples)...however, when I try that in the GUI, I get no data samples at all... My chart is just stuck at sample "1".

If I switch to I2C Command (Manual mode) I get my data charted nicely every 1/2 second (I am using a simple trim-pot resistor divider to create my waveform):

 

Is there some trick I am missing in the GUI to "start" the samples in Auto mode?

I see in the spec the following statement: 

but is the GUI supposed to do that? It almost seems as if the "START SEQUENCE" button is not working to start in Auto modes.

Please let me know if I am missing something. I see the cool waveforms in the user guide for the EVK, but the manual is lacking in more details on how to use the GUI effectively."

 

Thanks you in advance for your help.

Best,

Jason Maxwell

  • I'd like to add a few follow-on questions about the GUI:

    1) Does the register pane even do anything? I never see it update and the values I enter in the gui panel never seem to reflect on the register page, even with updating "as fast as possible"

    Here we can see values set for thresholds, but the register contents are always 0x00

    2) How do I get the alert functions in the GUI to work? They never do...

    Here we are clearly well above the PRE_ALERT_EVENT_COUNT (which is zero) and the ALERT never triggers:

    Thanks!

  • Hi Vinny and Jason,

    Allow me some time to get my hands on this hardware so that I may test it with the GUI. Thanks!

    Regards,
    Joel

  • Hi Vinny,

    I lost track of this conversation, so apologies for not getting back sooner. Wass your issue able to get resolved? Otherwise I will look into it.

    Regards,
    Joel

  • Hi Joel,

    Nope, still have the issue.

    Thanks!

  • Hi Vinny,

    After trying this on my board, I can verify that I am experiencing the exact same issues that you are running into. I am updating the thresholds in the GUI, but it does not send anything over the I2C bus, so doesn't change the registers. If they are set in the register page, it does update the flags in the registers, but has no effect in the GUI.

    Unfortunately, this seems to be an issue with the software that the GUI is running on, so there won't be an immediate fix for this. I will send an update in case we're able to get an update on this. I apologize for that.

    Regards,
    Joel

  • Thanks for confirming the behavior. I look forward to any info when you have it!

    In the meantime, I'll try an Aardvark device to talk to the IC and see if I can get it to work for us.

    Do you happen to have any python scripts for this device anywhere I can leverage?

    Even simple register read and conversion to voltage will help me from creating it all from scratch.

    Thanks

    Vinny

  • Hi Vinny,

    We don't have Python example code for this device at the moment unfortunately. This is something else we are currently working on developing and publishing, but the SPI devices will likely be the first ones to become available. 

    There are likely other I2C example codes for other devices, and this wouldn't be a bad place to start as this device isn't particularly exceptional in its interface. If you need some help understanding the interface, I am of course open to help. 

    Regards,
    Joel