TestStand adding a comma to Step Names

[EdDickens]

Has anyone ever seen TestStand mysteriously add a comma to end of step names while executing?

As you can see from the images, the step names in the actual sequence do not have commas at the end while in the executing display, one has been added on the first two steps. This is causing problems because the step parameters are pulled form variables based on the step name using an expression (Locals.TestLimits[Step.Name].Max_Value). With the comma added, it's can't find the correct varaible. Note the Report error below refering to the step name with the comma.

I had just changed all the steps over to custom step types. Everything was working when I had all the steps just as individual actions or tests in the sequence.

I've renamed the steps, deleted them and recreated them from scratch and still get the commas.

[Kimchi-Taco]

Hello, just to confirm, those step types are custom?  Also, what are the first three steps doing?  If you could attach your program so you could give others opportunity to troubleshoot or to see if they too are getting the same issue that would be great.

[EdDickens]

I've created a small test sequence that is doing the same thing. Everything should be in the attached zip file. No custom Step Types in this one. The VI's are just empty shells of the originals with the same UI items. 

I do get the same issue on a different machine. 

The steps are just numeric limit tests

[~jiggawax~]

The Get Step Names step in the setup is adding the comma.  What is your goal with that step?

Regards,

[~jiggawax~ · Accepted solution]

Maybe you meant just + "," instead of += ","?

[EdDickens]

Good catch Jigg.

Not sure how I missed it. Guess I need to get my eyes checked. 😉

Thanks