Source Code for DAQmx Test Panel

[Mister_Rose]

In MAX, you can select a DAQmx device, and open a Test Panel.

Is the source code for this available anywhere? This program is almost what I need, and if I could get the source, make my mods and use that, it would save me from reinventing the wheel.

[kehander]

Have you looked at the DAQmx examples available through the Help menu?  They're pretty close - you just have to know a teensy bit more about what you need.

[Mister_Rose]

The DAQ examples are OK, but the test panel is more robust and full featured. It can easily switch between a low end 6008 and a more complex 6259 very easily. It would take me some time to code all that up with proper error checking, etc, using example code.

[F._Schubert]

I guess NI won't disclose this to you. Furthermore I think I've read somwhere (here on the forum), that it's written in CVI and not LV.

You'll need to do it on your own or supply MAX to your customers (you can use 'global channels' to use MAX for configuration and then make the remaining changes in your own software).

Felix

[kehander]

---

@mister Rose wrote:

It can easily switch between a low end 6008 and a more complex 6259 very easily.

---

It can?  Don't you have to reopen the test panel for each device? 

The analgous solution would be to create separate VIs from example code, each with the configuration options you need.

[Mister_Rose]

All I wanted to do was to be able to format the axis. I have a calibration routine that requires that the signal get as close to 5 V as possible. When you get to less than 10mV, you the numbers on the vertical axis go from 5.01 to 5. I'd like to be able to have it retain the three decimal spaces so I can see where I end up when I am less than 10mV away from a whole digit.

I guess I'll put in a feature reequest.

[Mister_Rose]

Re:

kehander

The analgous solution would be to create separate VIs from example code, each with the configuration options you need.

I'm trying to avoid having to code all that up. If I could just get the source and tweak the format string for the vertical axis, I'd be golden.

[JoePoerschke]

The source for the Test Panels would be such a fantastic asset.  I see an IEPE checkbox on my test panel, translating this to "AIExcitationSource.Internal, 0.02" was not in any way clear.  The test panel for my 9234 also has MeasurementType of Voltage, but the only funtion that uses IEPE is CreateAccelerometerChannel, which would indicate G's were being returned and not voltage.

[mcduff]

---

@JoePoerschke wrote:

The source for the Test Panels would be such a fantastic asset.  I see an IEPE checkbox on my test panel, translating this to "AIExcitationSource.Internal, 0.02" was not in any way clear.  The test panel for my 9234 also has MeasurementType of Voltage, but the only funtion that uses IEPE is CreateAccelerometerChannel, which would indicate G's were being returned and not voltage.

---

You can use the 9234 as a regular Analog Input channel which has the internal excitation. I do it all the time. Set up a task with Analog input then use a DAQ Channel Property node to set the excitation for EACH channel. You will need a For loop for this.

You can also use property nodes to see what excitation values are allowed.

mcduff

[rolfk]

That Test Panel is part of NI-MAX, almost certainly written in C++ (or maybe C#) and there is zero chance to get the actual source code for that and even if you did it wouldn't compile without about a few zillion other software components that are part of NI-MAX.

The DAQmx examples are pretty much the closest you can get to this. Depending on how many different hardware boards and sensor types you need to support, this could indeed get a bit of serious work, but why are you trying to get such a generic application in the first place? Start simple and easy and then start adding features for new sensor types as you go. DAQmx is a very generic application interface so that will not be the problem. Your main problem will be to get the user parameters to pass to the DAQmx functions verified as the user enters them in the control, to make certain controls available or not based on the functionality of the board or sensor and some cosmetic things like to adapt the graph axis labels to the actual measurement units of the analog channel.