MAX Test Panel into TestStand?

[Bladhart]

There are "Test Panel" in the MAX that allows us to read and write to channels.

I am wondering if there is an easy way to call that Test Panel up in TestStand in a step.

[Josh_W]

Bladhart,

There is a command line that you can use to programmatically launch a test panel.  You can call this command line using the call executable step type from TestStand.

nidmfpan.exe /devid:Dev1, where you can substitute Dev1 for the your correct device ID.

You can find more information in this KnowledgeBase: Launching Test Panels Without Running Measurement & Automation Explorer (MAX) in NI-DAQmx

[Omar_II]

MAX is calling an exe. You can do the same thing using the "Call Executable" step type.

I don't have CAN installed so I could not find the app "NI CAN Channel Test Panel".

Check the task manager the next time to see the exe that is running. Find it and configure a "Call Executable" step type

I attached an example that calls Switch_Soft_Front_Panel.exe

You could edit the TestStand tools menu to launch the CAN Channel Test Panel

Omar

[Bladhart]

I ran nidmfpan.exe in Run, and it says that it cannot find "nidmfpan.exe".  I went on to do a search in the entire computer for nidmfpan.exe, and nothing.

Then, I tried finding the Front_Panel.exe (or similar) as Omar has suggested, nothing as well.  I looked in the MAX folder, the NI CAN folder, and all the other device folders.

Any suggestions?

[Bladhart]

And... where do I find the device ID?

[Bladhart]

I think I fixed the first part of the problem.  I reinstalled the MAX drivers, and I now have nidmfpan.exe.

So, how do I find the device id?

[herosphro]

Bladhart,

Josh's suggestion for opening test panels will work for DAQmx devices, whose device numbers you can retreive from MAX.  Becuase you are using CAN devices, the test panels you are using are different and, as Omar said, we need to figure out what executable launches that test panel so we can use it our Call Exectuable step instead.

The best way to find out more about this would be to post this question on the CAN forum since this is a device/driver issue.  This way your question will get the attention of those who are more knowledgable about CAN.