Jump to content

Search the Community

Showing results for tags 'mccdaq'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • News
    • New Users Introduction
    • Announcements
  • Digilent Technical Forums
    • FPGA
    • Test and Measurement
    • Measurement Computing (MCC)
    • Add-on Boards
    • Digilent Microcontroller Boards
    • Non-Digilent Microcontrollers
    • LabVIEW
    • FRC
    • Other
  • General Discussion
    • Project Vault
    • Learn
    • Suggestions & Feedback
    • Buy, Sell, Trade
    • Sales Questions
    • Off Topic
    • Educators
    • Technical Based Off-Topic Discussions
    • Archived


  • Community Calendar

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 7 results

  1. My organization is eliminating computers running Windows 7 and moving to Windows 10. We are running QuickDAQ software, version on one of these Windows 7 PCs. I installed the same version on a Windows 10 computer but it is not able to open. I have tried running it in Windows 7 and Windows XP (SP3) compatibility mode, but it is still not able to launch. Does anyone have suggestions to get this version of QuickDAC running on Windows 10, or will we need to upgrade to a newer version of the software? Thank you for any advice you are able to provide. Regards, JK
  2. Hi, I need to use labview to program two USB1608gx. At the same time, two USB1608GX are needed to collect data together.Is it feasible to do so?   But there are no relevant examples in the MCC Knowledgebase.   Is there any important point I need focus on? How could I do it on labview? Thanks alot.
  3. I'm trying to use my PMD-1208LS personal measurement device in labview community 2022. Downloaded MCCDAQ.exe from measurement computers site. Running MCCDAQ.EXE and tried to load ULx driver. Get error "The wizzard was interupted before ULx for NI labview could be completely installed. Inscal32 works because can make top LED pulse twice. computer uses win 10 using labview community 2022 (free edition) Does anyone have ab idea. Thanks
  4. Hello, I have 2 MCC 172 DAQs and would like to synchronous scan now, but there are only examples with external triggers. So I modified existing example like attached code, and test without external trigger. But it seem DAQs have different start time (Figure 1). I used BNC distributor so blue and green graph on Figure 1 have same input. Additionally, blue graph is data from device #0 (Master). Is there any way to start DAQs simultaneously without external trigger or just code is wrong? Cheers, Lee multi_hat_synchronous_scan_test.py
  5. Hi, I am trying to access the downloads section of mccdaq.com (https://www.mccdaq.com/support/swdasylab.aspx?t=https://mcc.download.ni.com/downloads/DASYLab/DASYLab_2022_ENG.zip) and the form seems to be unresponsive on the second page. Does anyone have this issue? If there is a direct download link for the necessary drivers for a USB-TC please let me know, thanks!
  6. Hi, I would like to evaluate multiple accelerometers with the MCC 172. Some of them have an IEPE interface, others have three wire connection with supply voltage, signal and ground. If a disable the IEPE supply on the board, is there a point on the board, where I can tap into the analog supply voltage of the ADC (or other regulated voltage) to supply my sensor? I have no problem soldering a wire to a pin or passive component. Cheers, Matthias
  7. We use USB-TEMP and USB-TEMP-AI devices in production. They are configured in InstaCal, then we query temperatures and voltages, respectively, through our in-house Windows/Visual C++ software using the Universal Library API. Recently, we've run into issues where calls to the cbTin and cbVin functions don't return, causing their threads to lock up. Our code is basically as shown below: int nStatus = 0; nStatus = cbTin(nBoardID, nChannel, CELSIUS, &fTemperature, FILTER): // or: nStatus = cbVIn(nBoardID, nChannel, nADCRange, &fVoltage, 0); // nStatus = 0 if no errors if(nStatus != 0) { // Get error info from nStatus, display error msg... return -1; } return 0; Is there an issue with how we are using these API calls, and are there alternatives to these API functions that return immediately instead of blocking? Thanks!
  • Create New...