07-27-2018 03:46 AM - edited 07-27-2018 04:04 AM
Hello,
i have a testsystem where i updated labview 7.1 to 17 and teststand to current version.
I have a lot of custom step-types created with LV7.1 which currently create the attached error when executing.
If i open the steptype and click on the reload-button the vi-icon is shown and loadable.
The steptype shows then "modified" and is executable.
Question is now: How can this be done for all sequence automatically?
I already found the tip that this can be done with the "Sequence File Converter" but i dont understand what to do there?
Thanks for help
BR
Solved! Go to Solution.
07-27-2018 05:30 AM
Now i found out how to use the "Sequence File Converter" but after updating a file and applying the changes the types are still wrong.
08-07-2018 08:58 AM - edited 08-07-2018 08:58 AM
Hello OnlyOne!
Have you maybe managed to solve your problem? Is it still actual?
08-07-2018 09:16 AM
I manually updates the typedefinitions.
After this i used the teststand Tool -> "Update Vi Calls".
The thing was:
sequence_A.seq contained a custom type.
I manually changed the updated type in here.
Then i opened parallel sequence_B.seq which also contained this type.
The type gets automatically to the new version if sequence_A.seq updated BUT the already existing steps in the testplan still did not work.
I had to call additionally the "Update VI calls" the the steps work again.
very bad
08-07-2018 09:29 AM
I see. I wasn't aware that Sequence File Converter does not work on type definitions. As you found this way to Update VI calls from TestStand and eventually it solved the issue, may I mark your request as solved and add your solution to our knowledgebase?
08-09-2018 04:07 AM
Sure