Using Labview and Labwindows CVI together in TestStand

[Matrix007]

I have a parametric test system for a module that is using Labview 8.5 & TestStand 4.0 to run automated test scripts. I have done the hardware (Analog & Digital I/O controls and measurements) test code in Labview.  The module we are testing has Analog & Digital I/O and a micro with CAN communication. I have a software engineer to help write the CAN communication part of the code. He wants to write the CAN code in LabWindows CVI 8.5. The CAN code will have parameters and data that I will need to compare to the values in my Labview code. (This data is aquired through the data acq PXI modules). I would have to aquire the CAN data and use TestStand to compare this to the Labview data.

Would it be difficult to use both of these systems (Labview & LabWindows CVI) together in a testand sequence?

Or would it be better to write all of the code in Labview.

[Dennis_Knutson]

You can use as many different programming languages as you want. Assuming that you are passing data from/to TestStand and the step module, the fact that one step is written in one language and the next step is written in another, is totally irrelevant. In case you haven't noticed, the built-in steps have been written with different languages, though LabVIEW is not one of them.

[Matrix007]

Thanks for your reply. The Labwindows CVI CAN code that was developed now works as a stand alone program. It can control and read CAN messages and data. Unfortunately I can't access the controls or read the data from the .exe file that Labwindows generated in TestStand. A .dll file was generated and the CVI.exe user interface functions show up in TestStand when I use this .dll as selected module. An error states that the parameter I select from the "functions" list doesn't have any parameter information.

Does Labwindows CVI code need to be written in a specific way so that TestStand can access it?

Can TestStand read the data from the CVI exe. file? (User Interface)

[Dennis_Knutson]

I would recomend reading the Using LabWindows/CVI with TestStand manual. It sounds as if the dll functions were not declared properly.

Using a LabWindows/CVI built exe would be no different than an exe built with LabVIEW or any other language. The exe would have to have an ActiveX interface or support command line parameters.