Multifunction DAQ

cancel
Showing results for 
Search instead for 
Did you mean: 

Convertion from NIdaqmx to NIdaqmx base creates problems with channel configurastion of tasks

Hi,

I have a running vi under Windows with NIdaqmx. I am using 3 devices (two 6008 and one 6501) to control photomultipliers that have LEDs and other TTL signals connected to each channel (as well as analog stuff but this is right now of secondary importance). These channels have to be operated separately. Under Windows in MAX I can configure each channel separately to give it one task and it works. Now that I have to switch to either a MAC or linux machine I have to change from NIdaqmx to NIdaqmx base. But in the configuration utility I could not find a way to configure each digital channel separately. What would be the easiest way to make the switch to another OS and still using each channel separately?

\Attached is the vi that works under windows (btw, after each start of the vi -- in windows --, I have to click first on arrays 2,4,6,8 to make it work, why is that? Wrong setting of the boolean array?)

Hope there is an easy solution.
Thanks
Thomas
0 Kudos
Message 1 of 4
(3,198 Views)
Thomas,

Looks like you are creating tasks in Measurement and Automation Explorer and using those in your VI.  Since you have switched to DAQmx Base, instead of creating tasks in Measurement and Automation Explorer, you could create channels in LabVIEW itself.  You can use a VI called DAQmx Base Create Channel and wire only one channel into the physical channel input of the create channel VI.  This is similar to the DAQmx create channel, which does the same think as creating tasks in Measurement and Automation Explorer.  This way you would not be including any tasks from MAX, just creating channels in LabVIEW.

Hope that helps.

Regards,


Raajit L
National Instruments
0 Kudos
Message 2 of 4
(3,154 Views)
Hi
thanks for the explanation and the links. Now I still cannot find a way to display after DAQmx base read a boolean out LED in one step, but have rather to compare the integer out with 255 or 0 to wire it to a boolen out LED. Is there a way to not use this comparison? OK its no big deal, I just wanted to reduce as many features as possible and in DAQmx I am given this option to choose from.
Thanks
Thomas
0 Kudos
Message 3 of 4
(3,131 Views)
Sorry to post again, I cannot edit my previous message anymore:
In addition I now have the problem that lsdaq correctly shows the device (USB 6501), lsusb also shows that it is properly recognized but in the vi no device is visible. I see the lsdaq message only if I am root, btu I am starting labview as root as well and still i cannot see the device in the scroll down menu (in fact it is greyed out). I read the forum articles about firmware update but I doubt it applies to my problem as i have seen the device before and there has always only be NIdaqmx base (as it is a linux only machine) on it.
Thomas
0 Kudos
Message 4 of 4
(3,128 Views)