USB-TC - Error when trying to run

[Martin Rønnov Andersen]

Hi,

I've been using my USB-TC for quite some time now, but when I came in this morning to run a test, it come up with an error saying: "An unknown error has occurred. The specified channel is invalid.". It doesn't specifi which channel is invalid, so I've tried to run all channels individually but with no luck of solving this issue.

I'm running the latest version of DAQami

Has anyone had this issue before and if so, were you able to fix it?

 

Best regards,

Martin

 

[Fausto]

Hello @Martin Rønnov Andersen.

With DAQami closed, open MCC's InstaCal application.  Is your USB-TC detected in the application?  Which channels have thermocouples?  Are you able to read the temperature on the channels, in InstaCal?  What is your module's serial number and firmware listed in InstaCal?  Have you tested the module with a different USB port, USB cable and/or Windows PC?

Regards,

Fausto

[Martin Rønnov Andersen]

Hi @Fausto,

Thanks for the quick respond! To answer your questions:

• Is your USB-TC detected in InstaCal? Yes, the USB-TC pops up.
• Which channels have thermocouples? Out of the 8 channels, I'm using the first 4 (CH0, CH1, CH2, CH3).
• Are you able to read the temperature on the channels, in InstaCal? Please see the attached photo - as far as I know, this means that channel 0 and 1 are not ready, right?
• What is your module's serial number and firmware listed in InstaCal? The Serial No. is 20F3CBF and the Firmware version is 1.24.
• Have you tested the module with a different USB port, USB cable and/or Windows PC? Yes, I've tried different USB port, different USB cable and different PC - same issue.

Best regards,

Martin

Edited December 28, 2022 by Martin Rønnov Andersen

[Fausto]

Hello @Martin Rønnov Andersen.

Correct.  According to the Universal Library Help (https://www.mccdaq.com/pdfs/manuals/Mcculw_WebHelp/ULStart.htm):

Error temperature values:
-9999 is returned when a value is out of range or an open connection is detected.
-9000 is returned when the device is not ready. This usually occurs right after the device is powered up and calibration factors are being loaded.

I will reply to you via private message for the repair.

Regards,

Fausto