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.

ADS1278EVM-PDK: ADS1278 EVM Labview code password

Part Number: ADS1278EVM-PDK
Other Parts Discussed in Thread: ADS1278, ADCPRO,

I am using your ADCPRO software for evaluating the ADS1278.
I would like to interface your EVM to my custom board with the ADS1278 on it
to do that, I need to modify the Labview code in the ADCPRO application
but the installed files are password protected
can you share the password to allow editing the ADCPRO code for my application

  • Hi Wilbur,

    The latest version of ADCPro shouldn't have any password protection in the source files and you can find the files for ADS1278 in the Plugins > EVM >  ADS1278 directory. If your version of ADCPro is password protected, you may want to try redownloading and installing the latest version!

    Best,

    Zak

  • No change. All the files in the adcpro_v2.zip folder are password protected.

  • Hi Wilbur,

    I don't think you  need access to the files in that zip folder as they are mostly redundant or archived versions of  the items in the main ADCPro directory. 

    That said, what are you aiming to accomplish with this? Typically when we see customers wanting to interface the EVM to their system they just directly connect to the ADC and don't use the MMB0. Honestly I think this will be a huge effort to adapt the code and GUI if you aren't using the same processor. Furthermore, I just want to warn you that these GUIs are not typically developed in-house so we will not be able to offer you any technical support along the way unless it is strictly with regards to the ADS1278 or the unmodified GUI operation (i.e. I can't give you any insight into how any of the GUI code actually works because I don't know).

    Best,

    Zak

  • Our product will have the ADC1278 imbedded in it so (due to limited resources) we want to take advantage of using your Labview code and the DSP on the EVM motherboard to interface with our system. The problem we run into is that your Labview code apparently looks for a EEPROM code that resides on the ADS1278 module and crashes without being able to find it when connected to our 1278 board. That zip folder contains the source code for the Labview program and we have a Labview expert. Our desire is to modify your code to fix the interface to communicate with our 1278 as well as some of the timing issues that cause frequent crashes in the code of the original design. The current ADCPRO has many of the test features we need to analyze our system performance (FFT, Histograms, data capture ).

  • Additional note : The ADS1278EVM-PDK does not allow for use of the SPI interface. We want to modify to use SPI. this would allow us to make a test interface to an ADS1278 board with the DSP used for datacapture and analysis

  • Hey Wilbur,

    Thanks for clarifying

    The EEPROM issue I can at least help with as this has started to impact many Windows 10 based systems. Here is a thread showing how to disable the EEPROM check: https://e2e.ti.com/support/data-converters-group/data-converters/f/data-converters-forum/533653/ads1278evm-pdk-wont-load-eeprom

    and another for giving yourself permission to save your change: https://e2e.ti.com/support/data-converters-group/data-converters/f/data-converters-forum/1029829/ads1278evm-pdk-adcpro-data-recorder-error-code

    I spoke with a colleague about the source code and he said the code for the ADS1278 module is included in the directory without requiring the ADCPro password. You can find it here: C:\Program Files (x86)\ADCPro\plugins\evm\ADS1278\source\ADS1278EVM LabVIEW source.zip

    Note, we also have another tool called the Analog Engineer's Calculator that includes a data analysis suite. You just need to be able to store your capture in a file the tool can load:

    If this seems useful, you can download it here: https://www.ti.com/tool/ANALOG-ENGINEER-CALC

    I hope  this helps!

    Best,

    Zak

  • This is a step in the right direction. My Labview guy says he can now open the files but there are some missing libraries or modules. They may be elsewhere in the installed directories so we need a couple days to list them all and search the directories. Thanks.