odules must have expected prototype" error for individual code modules within a sequence. However, you're encountering a similar issue with sequence prototypes called within your main sequence, and "Update Sequences" isn't resolving it.
Here's a breakdown of the problem and how to address it:
Understanding the Problem
Code Modules vs. Sequence Prototypes:
Code modules are individual pieces of code (DLLs, VIs, etc.) that perform specific tasks.
Sequence prototypes are reusable sequences that you call from other sequences. They have their own inputs and outputs (parameters).
Prototype Mismatch:
When you modify the parameters (inputs/outputs) of a sequence prototype, the calling sequences need to be updated to reflect those changes. If they're not, you get the "Code modules must have expected prototype" error, but in this case, it refers to the sequence prototype's interface.
"Update Sequences" Limitation:
The "Update Sequences" tool in TestStand primarily focuses on updating code module references and some sequence call parameters, but it might not always automatically detect and update changes to sequence prototype interfaces, especially if the changes are complex.
Solutions
