10-04-2013 05:06 PM
I'm implementing a series of Robot moves in a TestStand sequence. All the moves are working successfully in TestStand 2012, and the Denso Library VIs are called directly (LabVIEW 2012) as action steps in the sequence.
However, when I tried to add the DRL_Set_Get Current TOOL #.vi to the sequence, I get the following TestStand dialog,
The VI still shows up in TestStand and it appears I'm able to pass in the input variables (see attached screen cap). However, on execution I get the following TestStand Run-Time error at this step, "LabVIEW: robot session is a required parameter..."
It appears TestStand is supplying the robot session to a duplicate connector/control (based on the initial dialog) and it's the wrong one. There's a whole bunch of methods working in the TestStand implementation. It's just this VI giving me trouble, and it's an important one. I can probably create an envelope VI for this one step, and have TestStand interface with the envelope VI, but I'd like to keep the Library intact and have the root cause fixed.
Regards,
Iggy
Solved! Go to Solution.
10-07-2013 07:55 AM
Hello Iggy,
I work for DigiMetrix company (Former name is ImagingLab GmbH).
We have prepared a special build for you that has an updated version of this function. We've renamed the output terminal to "robot session*". Please download it and install with VI Package Manager.
We will publish this update soon in VIPM Network.
Should you have any questions or comments please contact us (support@digimetrix.com).
Kind Regards,
Nikita.
Software Engineer
Certified LabVIEW Developer
e-mail nikita.prorekhin@digimetrix.com
web www.digimetrix.com
10-07-2013 03:25 PM
10-07-2013 06:45 PM