Jump to content

Search the Community

Showing results for tags 'usb-temp'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • 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

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 1 result

  1. 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...