From 11:00 PM CDT Friday, May 10 – 02:30 PM CDT Saturday, May 11 (04:00 AM UTC – 07:30 PM UTC), ni.com will undergo system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

How to mass-compile types after Labview update?

Solved!
Go to solution

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

0 Kudos
Message 1 of 6
(2,452 Views)

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.

 

0 Kudos
Message 2 of 6
(2,439 Views)

Hello OnlyOne!

Have you maybe managed to solve your problem? Is it still actual?

Patryk Jankowski
NI CER Application Engineer | Certified LabVIEW Architect
Message 3 of 6
(2,398 Views)
Solution
Accepted by topic author OnlyOne

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

0 Kudos
Message 4 of 6
(2,394 Views)

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?

Patryk Jankowski
NI CER Application Engineer | Certified LabVIEW Architect
Message 5 of 6
(2,389 Views)

Sure

0 Kudos
Message 6 of 6
(2,374 Views)