Webcast: The Things I Wish I Would Have Known Before I Started Programming with NI-DAQmx

[Stuart_G]

I just wanted to respond to JoeLabVIEW's quote:

"HOT DANG YES!!!

I just posted a question about this..   here!!!

I mean really...  There has got to be a file somewhere which contains the "fake" data... Even if it's in binary.  How else do we fully test our code prior to having the actual card..  especially if that card is 1000 miles away       (not sure which smiley is appropriate) "

There is NOT a file somewhere which contains fake data.  All of the data is generated internally in the driver.  We have some code which directly generates data into the read buffer.  I will say I do get this request A LOT.  It is not that NI is ignoring it, but there are lots of issues we have to address.  Here are just a few

1.  JoeLabVIEW thinks is OK to just read in binary data.  That is fine for a savvy user such as yourself, but for a large percentage of customers this wouldn't be OK.  They just want DAQmx to be able to directly read their mp3,xml,xls, etc file and go from there.  Trust me, I get this request a lot!!!

2.  Where would you configure the "file to read". MAX, LV?  What about in CVI/MS, ANSI C (yes we do have customers that use ANSI C:) )? 

3.  How does the DAQmx "read" get this information.  Do we put a file read in all of our VIs now? Do we just have a standard file where we go look up whatever the customer puts there?

All of these can be solved, but it just isn't as easy a problem as one might think on the surface.  But...keep the suggestions coming...the more backing there is the harder it becomes to say NO 🙂

StuartG

[Ray.R]

Thanks Stuart,

LOL!!  Yes I can imagine you do get many requests.  Pushing the enveloppe is part of the fun, right?

I don't care about easy / pre-packaged solutions..  If we can have access, even indirectly, we can create our own solution.  😄 

In this case, I would read the info directly in LabView.  Of course, I could do the same in CVI (or ANSI-C).  A file is a file in any language 😄

If a "savvy" programmer can implement solution of his/her own, then why not give a clue at how / where this could be done.  I don't expect  shrink-wrapped solutions (all the time). LOL!!

When time permits, I'll have to visit the driver... 😉  for curiosity's sake..

Thanks!

RayR

[MogaRaghu]

I am glad there has already been a request for signal simulation for DAQMx virtual devices.

Going one step further it would be nice to get a manual interface option where all inputs are user controllable ( Configurable switches for DIs , knobs /sliders for AIs , LEDs for DO and meters for AO ) and automatically loaded based on the selected card's I/O count. 

Raghunathan

[MikeF_tmt]

Sorry guys, if my post is out of subject, but I strongly believe the driver should allow the system configuration access. What I mean are things like: which NI boards are installed, which drivers (and what versions) are installed, what are the board's features, etc. It could help a lot - but I failed to find any information on this.
How to know if there is DAQmx installed?
How to find out how many AI's has the board I am using?
etc....
and we are building systems, which can utilize various types of DAQs.
Thank you,
Mike

[MogaRaghu]

---

@Mikef_cetr wrote:

Sorry guys, if my post is out of subject, but I strongly believe the driver should allow the system configuration access. What I mean are things like: which NI boards are installed, which drivers (and what versions) are installed, what are the board's features, etc. It could help a lot - but I failed to find any information on this.
How to know if there is DAQmx installed?
How to find out how many AI's has the board I am using?
etc....
and we are building systems, which can utilize various types of DAQs.
Thank you,
Mike

---

If I am not mistaken all of the above information and more can be had from the NI Measurement and Automation Explorer ( NI MAX ).

Raghunathan.

[Stuart_G]

Couple of things

1.  Remember this post started off of "The things I wish I would have known before I started programming with DAQmx.".  Let's move some of the discussion to other posts/threads.  While it might be helpful for us, it isn't helping Jervin get anymore ideas for his webacst.

2.  I wanted to respond to MikeF's request.  There is this information you can query from the driver programatically.  I would suggest looking into the device and system property nodes.  They give a wealth of information.  You can also combine them with channel property nodes to get even more info.  Jervin....I think this might be a good topic for your webcast.

StuartG

Message Edited by Stuart G on 02-13-2008 08:13 AM

[MikeF_tmt]

Thank you Raghunathan, and - especially - Stuart for your answers. I managed to find the description of the properties mentioned and yes, there is a wealth of information available.
Now to address StuartG's item 1:
Like I mentioned originally I was sorry if I had posted to a wrong thread, even though I still believe that switching from Traditional driver to DAQmx requires clear understanding of how to identify  the hardware used. But it is more there.
As soon aswe are talking "switching", that ususally means one used the Traditional driver before and has to support multiple customers who do not have DAQmx installed.
As a result, it becomes fairly important (in order to be able to write generic software) to have a way to:
1. Before "touching" a device to figure whether the DAQmx is installed, and
2. To be able to run software even if it is not installed (meaning runtime driver binding I think).
I guess this is what a lot of people would like to know starting the transition and being in the situation like myself - when some of DAQs I am using are supported by both Traditional and DAQmx drivers, while some do not work with Traditional one.
Thank you again for insights and help,
Mike

[MikeF_tmt]

---

@stuart G wrote:

Couple of things

1.  Remember this post started off of "The things I wish I would have known before I started programming with DAQmx.".  Let's move some of the discussion to other posts/threads.  While it might be helpful for us, it isn't helping Jervin get anymore ideas for his webacst.

2.  I wanted to respond to MikeF's request.  There is this information you can query from the driver programatically.  I would suggest looking into the device and system property nodes.  They give a wealth of information.  You can also combine them with channel property nodes to get even more info.  Jervin....I think this might be a good topic for your webcast.

StuartG

Message Edited by Stuart G on 02-13-2008 08:13 AM

---

After I started playing with the properties StuartG gave me insight about, I figured they are still not fully descriptive. There is no way (or I missed ones) how to get the device-related parameters, like numberof physical AI/AO/DIO channels on board, AI/AO signal ranges available, # of bits used for ADC/DAC conversion (the latter is available but only related to a specific task, rather than on the device level). Guess it would be great if the driver could provide for complete information... to make the programming really generic

Again, thanks to everyone who helps
Mike

[Dennis_Knutson]

Look again at the DAQmx Device property. After you write the ActiveDev property, you can read all of the items you list. Right click and select Properties and you will see what is available.

edit: Just saw from another post of yours that you are not using LabVIEW so my hint will not work for you. The properties are there though, you just have to work harder with a text based language.

Message Edited by Dennis Knutson on 02-13-2008 09:43 PM

[MogaRaghu]

---

@Mikef_cetr wrote:

---

....... There is no way (or I missed ones) how to get the device-related parameters, like numberof physical AI/AO/DIO channels on board, AI/AO signal ranges available, # of bits used for ADC/DAC conversion (the latter is available but only related to a specific task, rather than on the device level). Guess it would be great if the driver could provide for complete information... to make the programming really generic

---

That entire list of above details are available as part of the product specfication summary and when you use the built in functions like DAQ-Assistant,  they are listed device wise for you to select and use.

I am sure you are wanting a particular functionality and maybe I am missing the point - but if this interaction can bring out that aspect, so much better for including it in future developments.

Thanks

Raghunathan