NiDAQ to Lookout connection

[capsuleguy]

I am a little lost here.  First, I am a process engineer and not an EE so be kind.  Our normal DAQ guy has left the company and I am trying to pick up the pieces with very limited knowlege and documentation on this stuff. I have a fair understanding of Lookout and currently use it for a SLC/505 interface.  I have the feeling I am just missing something basic on this new project. 

I now have a new process to develop and plan to use a NI DAQCard 6062E card and SC-2345 connector block that I already have available.  I configured my sensor and can see it listed on the NI-DAQmx task list on MAX 4.0 and it seems to be working.  I can't seem to find a Lookout driver object that will see this data.  Should I be using the NIDAQOPC object?  If so, how do I configure it? I tried to do that but get a "OPC/OLE error: the OPC server is unavailable." message.  Also a OPC/OLE error OPC server not registered properly, (63) Invalid class..." error.  Do I have to set something else up outside of MAX?  Thanks for the help.  Any comments would be appreciated. A basic do A then B then C list would be great if it is not too much trouble.

[capsuleguy]

OK, I noticed the thread on the load cell issue and got some clues from his set up.  I am now using the OPC client and have setup global virtual channels in MAX.  I now seem to have what I need working on Lookout.  2 questions so I can learn from this. 

1) What is the difference between a global virtual channel and a task in MAX.  You seem to set them up the same.

2) When do you use the NIDAQOPC object instead of the OPCclient object in Lookout?

Thanks

[Khalid]

I don't know about #1, but "the OPCNIDAQ object is a shortcut for creating an OPCClient object for use with NI–DAQ."  The Server name is pre-defined in the case of NI-DAQOPC.  They're the same really.

-Khalid

[Bassett_Hound]

Capsuleguy,

To answer your question about the difference between Global Channels and Tasks, a Task consists of channel(s) with timing, triggering, and other properties whereas a Global Channel will consist of just the configuration for one specific channel.  For example the Voltage Range and input configuration could be configured in a global channel but the timing and triggering could not be.  Conceptually, a task represents a measurement or generation you want to perform.  Below is a link that will give you some further information on the differences.

http://digital.ni.com/public.nsf/websearch/BB06D0620FDD7ADB86256D2700557BFC?OpenDocument

Steven B.

[capsuleguy]

Thanks for all your help.  I think I understand and it seems to work!

[Bassett_Hound]

Glad we could help out.  Good luck with the rest of your application.

Steven B.