DAQ

[SteveR_]

What do you mean view hardwara on MAX? If it helps, the computer registers that the USB is connected, as well as the USB connector although we can't view it in labview.

[Vincent90]

Measurement & Automation Explorer ... You should test your hardware communication launching it

[Daikataro]

Are you just connecting the raw thermocouple to an input port? Or are you using a buffer in between? NI DAQs can read raw thermocouples, but you need to specify it, and provide some data to DAQ or LabView before you can actually read a coherent value.

[SteveR_]

Yes the device is connected on MAX

[Vincent90]

Did you try to use Test Panels on it ? Any errors comming ? If none, share your VI.

[SteveR_]

We have no VI, we cant do one without the DAQ assistant. And we havent used test panels.

[RavensFan]

Are you saying that you DO see the DAQ assistant in LabVIEW when you don't have the hardware connected?

[NIquist]

---

@Stephen.robbins wrote:

We have no VI, we cant do one without the DAQ assistant. 

---

   Most of us wouldn't touch the Express VIs or DAQ Assistant and have been writing LabVIEW code long before there were any such things.  Using the actual DAQmx functions directly is a FAR more powerful way to control DAQ hardware.  If you want to try it the easy way with an example that ships with LabVIEW check out:  Help > Find Examples...  Hardware I/O > DAQmx > Analog Input  and then open Thermocouple - Continuous Input.vi.  

The Test Panels mentioned are another easy way to test out your DAQ hardware.  In NI-MAX there is a tab called Test Panels for each device listed in Devices and Interfaces (careful, it may be hidden on the top-right of the screen if there are too many tabs to view).  Open it up and you can set a few quick parameters and exercise your hardware I/O.

Of course none of that solves your initial problem.  Honestly, I have never seen anything like that before.  We still need more info.  Rather than describing your system just tell us the actual model numbers of ALL the hardware you're using.  Many NI empoyees monitor this board so maybe they've seen something like this and can chime in.  Perhaps it's some weird hardware that has limitations that are unusual.  We can't check it out unless you explicitly list what you'reworking with...