11-07-2016 05:14 AM - edited 11-07-2016 05:15 AM
Hello everyone,
Anyone already experienced this attached bug ?
It is on one step type which calls (SubStep Menu) in post-step a LabVIEW VI.
The same VI and same step (just its name has changed) have been used in LabVIEW/TestStand 2014 without any issue. We got other similar steps which are runing fine in both 2014 and 2016 environement.
I cannot find a way de reproduce this bug and still not solved.
Any help will be apreciated.
BR,
Vincent
11-07-2016 08:54 AM
If you copy and past the step to a new sequence file does it still cause the issue?
11-07-2016 09:07 AM
Yes it still does. I'am stucked with this and really can't find a way to solve it 😞
11-07-2016 09:09 AM
Does it happen when you create a new step in a new sequence file and set it up exactly like that one?
11-07-2016 09:16 AM
I think i don't understand your question. My stepType is configured into "Type" Windows.
So everytime i use this step i get this error on the limits tab only.
The properties tab shows the right Type.
Vincent
11-07-2016 08:29 PM
can you send a sequence file with that type in it?
11-08-2016 02:36 AM
Generaly this error occurs because of a corrupt installation of TestStand development system. The error can be resolved by Repairing the software from Add/Remove programs in Control Panel.
If that does not work, uninstall TestStand and reinstall it.
Hope it will help you
Regards,
Maxime G. | Application Engineer
National Instruments France
11-08-2016 03:15 AM
Using TesStand 2013, 2014 and 2016 32 bits could corrupt all installation ?
I switch between TestStand versions with TestStand version Selector.
11-08-2016 09:05 AM
I have installed TestStand2016 on new PXI we received and we got the same "error".
Does it mean TestStand2016 installation is corrupted ?
StepStype CheckNumericValue attached
11-08-2016 09:12 AM
Why do i have a custum datatype from previous project on TestNI.seq ?!!!
How can i replace it by the one which already exists on other typepalette ?