01-18-2017 03:15 AM
Hi,
I'm quit new to testStand.
I have both testStand & labview 2016.
when i debug a sequence in testStand and use step into on a labview code module,
labview doesn't lunch. the debugger just step over the module.
When I try to do the same with testStand 2013 (also installed on my pc),
it seems to work fine.
Is there some sort of comatapility issue or configuration new to testStand 2016?
Thanks for any help,
Barukh
Solved! Go to Solution.
01-18-2017 04:13 AM
Configure -> adapters...
Select labview->configure->check labivew development system
solved it for me
01-18-2017 04:14 AM
Barukh,
it sounds to me that the LV adapter of TestStand 2016 is configured to run VIs in the LV RTE (RunTime Engine). This is NOT the default configuration, so if that is the reason, someone had to change it.
You can change adapter configuration by selecting Configure >> Adapters. Make sure that the LabVIEW adapter uses the Development System.
Another option for this behavior is that the VIs are being distributed with the Block Diagram removed. That can be done using the LV Application Builder and create a source distribution. So if adapter configuration is not the source of the issue, please verify that you can open the VIs in LV and view the Block Diagrams.
PS: The word for starting things is launch. Lunch is what you eat at noon 🙂
01-18-2017 04:17 AM
Thanks, problem solved 🙂