Conflict between local and global step types

[Angel Olivares]

I'm making some changfes in some previous programmed Step Types and I'm having conflicts. Is it posible to make global Step Types? I have some sequences that have another step type with the same name as the global and it appears the Type Conflict Dialog box. I'd like to use in all my sequences always global Step Types. Can I do this with TestStand 2.0.1?

[Ryan Ramcharan]

Hi Angel,

Yes. You can create a step type inside of the Type Palette. This will make the step type "global". However, in order to avoid type conflicts, when you create the step type in the Type Palette, you should set the Version number and uncheck the Modified check box. Then set the option that states "Use the defition that has the highest version number". Now when you insert a step of that type into your sequence file, save and close the sequence file, then modify the type in the Type Palette, simply increase the version of the step type and remove the modified check box. Now when you open the sequence file containing the type, TestStand will automatically replace the older verion of the type with the newer one.

Keep in mind that if either s
tep type (the one in the sequence file or the type palette) have the modified check box turned on, you will get a Type Conflict dialog.

If you do encounter a type conflict dialog, select to use the type with the higher version number, which should be the one inside of the Type Palette.

Hope this helps!

Bob

[Angel Olivares]

Hi Bob,
Until now we have always had in all our Step Types the version 0.0.0.0 and the option of the "Modified. When set, this check box indicates..." enable. Maybe that was my problem. I'll try to update the versions in order to avoid those problems in the future.
Thank you very much!

Angel

[Angel Olivares]

Hi again Bob,
I had two Step Types running perfectly in a sequence. Let's say Step Type A STA) and Step Type B (STB). I've make a modification on STA and if I insert this step in a sequence works perfectly. The problem comes when I try to use both in the same sequence. I cannot nor edit the "Edit Settings.." of both at the same time. The first that have benn tried to be edited works, but the second doesn't respond to the edit command. I've look through STB and it doesn't contain any reference to STA. I don't know which can be the problem of this conflict.

[Ryan Ramcharan]

Hi Angel,

I am not sure I understand what you are trying to do. Where do you create STA and STB. Then where do you try and edit them. Can you please explain what is the "Edit Settings..." option. Is this a custom Edit substep that both STA and STB are using? Please clarify.

Bob

[Angel Olivares]

Hi again,
For both Step Types A and B, I've inserted an "Edit SubStep" (inside Tab Substeps in the Step Type Properties). Those associated programs are written in LV. That means that when I insert one of my steps types in a sequence, if I click the right bottom, I have the possibility to make changes in this Edit VI and save those parameters in TestStand. I attach you the two Step Types that have the conflict, maybe you can see the problem. Have a nice weekend!

Angel

[Ryan Ramcharan]

Hi Angel,

I could not run your steps as some of the code was missing. However, I tried this with a very simple application (attached) and it worked fine. Keep in mind that once you call the Edit Substep, TestStand will wait until the VI is complete before allow you to choose another step's Edit routine. Therefore, it's a good idea to make these edit substeps modal to the TestStand application by calling the Start and End Modal Dialog VIs located on the TestStand palette. Let me know what you think.

Bob

[Angel Olivares]

Hi Bob,
Although you couldn't open all my files, just let you know that as you say I'm using the "Start Modal Dialog.vi" and the "End Dialog Modal.vi". It's everything very confusing, because the application doesn't work since I inserted a couple of subVIs that are capable to read and write values in an INI file, ???

[Ryan Ramcharan]

Hi Angel,

Could you send a small example, that reproduces this problem? Although I would love to solve this via the forum, I think at this point, a call to NI support may be much more efficient.

Sincerely,

Bob

[Angel Olivares]

Hi Bob,
I've just sent this problem to NI. Thank you very much for your help. I'll keep you inform when I find the solution. Thanks a lot.

Angel