Jump to content

amaningd

Members
  • Posts

    2
  • Joined

  • Last visited

amaningd's Achievements

Newbie

Newbie (1/4)

0

Reputation

  1. Thanks for your reply! The example C programs and reading temperatures/voltage through InstaCal both worked fine. To clarify, the issue we are having is intermittent. We did reproduce the issue occur again later today when trying to read temperature in our software. While leaving our software locked up and open in the background, we tried to open InstaCal, but it was stuck at the splash screen. During this time, the USB-TEMP and USB-TEMP-AI units' green LEDs were both on, so they both seemed to be properly connected. After we unplugged and reconnected both devices, our software became responsive again (albeit with an error message from the Universal Library and InstaCal was able to finish opening. Could a problem with USB communication cause the API calls to wait indefinitely instead of returning an error code immediately?
  2. 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...