ulTIn does not return ERR_OPEN_CONNECTION for disconnected thermocouple channels on the USB-2408-2A0

[mccdaq]

ulTIn does not return ERR_OPEN_CONNECTION for disconnected thermocouple channels on the USB-2408-2A0

[MarkRivers]

I found that there is an option to enable open thermocouple detection. I added this to my code and now it detects open thermocouples on the USB-2408-2A0.

                // Need to set thermocouple open detection
                error = ulAISetConfig(daqDeviceHandle_, AI_CFG_CHAN_OTD_MODE, DevNum, OTD_ENABLED);

It seems strange that this appears to be the default on the E-TC, since I did not enable it explicitly in UL for Linux on that device.
It must also be the default for the USB-2408-2A0 on Windows, since I did not explicitly enable it with BIDETECOPENTC from cbw.h.

I am no longer having a problem, but I'd like to leave this issue open to allow a chance for the developers to respond to why this seems to be default on some devices and not others?

[sbazaz]

On E-TC, the device configurations are stored on EEPROM and UL for Linux reads and applies those settings when it loads. However, the USB-2408-2A0 configuration are not stored on the device and users are responsible for settings the default configurations explicitly when using the UL for Linux. On windows, InstaCal stores the configurations in the config file and every time the UL for windows loads, it applies those settings automatically. If you have further questions please reach out to MCC through their tech support form

[MarkRivers]

On windows, InstaCal stores the configurations in the config file and every time the UL for windows loads, it applies those settings automatically.

That is not true in my case, because I am not using InstaCal on Windows. I have called cbIgnoreInstaCal() at the beginning of my program, and I am using cbGetDaqDeviceInventory to find the device instead. So there must be some other explanation for the difference in behavior of UL for Linux and UL for Windows on this device.