12-21-2012 10:43 AM
When running a TestStand sequence, I get the following error message:
The post-expression for the step 'Set Station Global Models' could not be evaluated.
Variable or property types do not match or are not compatible.
Error Code: -17321; Variable or property types do not match or are not compatible.
Although I do understand what the above is telling me, fixing the root cause is somewhat another thing.
I'll explain the scenario. The code is developped in TS4.1.0, although that should be irrelevant.
I inherited a TestStand project which calls LabVIEW modules. The original sequence works fine on the test pc (which is remotely located). The local and remote PC's share the same StationGlobals.ini.
Here is why it is strange.. I do get the error message on the local PC whether I use the old or the new code. I was assuming that using the same StationGlobals.ini would have fixed that, but it didn't. 😞
When I run the old code on the remote PC, I do not get that message, but I do get it with the new code. I don't recall modifying code that affected the StationGlobals. My goal is to fix it on both machines (at least the remote one).
This is the expression that it does not like:
StationGlobals.Models=Locals.Models,
However, that very same expression exists in the original code. The one thing that did change is the addition of a new model number in the Locals.Models.newNumber. I suspect that this contributes to the error. But why does it give me an error when I run the original sequence locally? Maybe I should try running it again..
In either case, any suggestions to overcome the error?
Thanks.
RayR
Solved! Go to Solution.
12-21-2012 11:29 AM - edited 12-21-2012 11:30 AM
Please ignore post.
I found the problem.. There was a mismatch with the number of models. Easy fix. It's all good.
For someone else who might tumble onto this thread for the same reason, here's an explanation.
I added a new model with its variants to the list of Locals.Models. In total, there were 16 additions to the list.
I also added these to the StationGlobals. Which meant that my StationGlobals no longer matched the one on the remote PC.
Where the error came in is that there was one missing model in the StationGlobals, so the size (number of models) did not match that of the Locals.
Slight oversight in the sea of models that are listed (I'm not even going to count them). Now fixed.
... and embarrassed ...
😞
I may as well give myself an "Accepted Solution".