Because of the holidays, TI E2E™ design support forum responses will be delayed from Dec. 25 through Jan. 2. Thank you for your patience.

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.

ADS1246: ADCPro sometimes hangs when retrieving data, requires reboot

Part Number: ADS1246
Other Parts Discussed in Thread: ADCPRO, TUSB3410

We need to use something lightweight for some field measurements using the ADS1246EVM and associated MMB3. Currently trying to use a Surface Pro running Windows 10 Pro. The ADCPro version is 2.0.1 build 4. ADS1246EVM version 2.0.0.0. Running in scope mode with continuous sampling at 1000 sps and 2048 samples ADCPro will stop taking samples in less than a couple of minutes. Trace is frozen, continuous button is active but when selected grayed out with no samples being acquired. Any further actions, like trying to reload the EVM, results in a "Restarting VI" window and app not responsive.

Have to use the task manager to end the ADCPro task. When ADCPro is run again the ADS1246EVM is not found. Full power down by unplugging and re-plugging the USB connection has no effect.

When trying to restart the laptop hangs in the restart mode. Have to perform a hard start (hold power button down, etc.) to get back to the point where the EVM can be used again. If power down is selected also have to use a hard start.

Has anyone else seen this type of behavior?

  • Richard,


    I'm sorry you're having problems with the EVM. First, let me start by saying that these EVMs weren't designed for field measurements. They're designed to show the functionality of our devices so that customers can design their own systems to suit their needs. However, many have used the EVMs to take measurements for their own applications.

    ADCPro was developed back in the days of Windows XP so we don't have much experience with using it with newer versions of Windows (we don't have very many Windows 10 machines here yet). However, I know we've have gotten ADCPro to work on both Windows 8 and 10. Because of the signed driver requirements, the drivers have been the biggest sticking point. It looks like you've gotten past that problem. You've already been able to collect data from the EVM through ADCPro.

    As for ADCPro hanging, there are a couple of possibilities. If the USB connection is disrupted, then the software may lock up and won't recover. During this event, the port will unsuccessfully try to re-enumerate. Another possible problem is that there has been some sort of ESD event that disrupts the EVM/MMB3, causing it to reboot and then lock up. If you can, look at the MMB3 when ADCPro locks up. If the device is still streaming data, then it will say STREAM on the LCD display. If the device has rebooted, it will display the data being read.

    If there has been some sort of ESD event, you can check under the computer's device manager. I think that it would show up as an unknown TUSB3410 device under the COM ports. As I understand it, once a COM port is open, the port will stay open until there is a software command to close it. ADCPro will open the COM port with LabVIEW, and if the program locks up and fails to close, the only way to get out of it is to reboot.


    Joseph Wu
  • Richard,


    We're you able to get through the ADCPro problems? As I'd mentioned, I think there may be some issues with ESD/overvoltage events hanging the bus.

    If you were able to get ADCPro working to your satisfaction, I'll close this post. If not, come back and we can work on it again.


    Joseph Wu