Equivalent to Step.Limits.Low.NumericFormat in TestStand 3.1?

[SercoSteveB]

...and everything comes into focus.

Thanks Doug.  I appreciate your time spent on this.

[JonP]

Hey Steve, the picture of your solution seems to have gone missing, any chance of reposting it?

[SercoSteveB]

Hi Jon.  I have no idea where the images are .  I have reported the missing images to the NI Moderator.  Hopefully they will reappear at some point.

[JonP]

Thanks for the quick reply. Maybe you can answer another way: when I call GetPropertyObject on the step object, what do I pass into the lookupString? "Limits.Low", so that I have to also set "Limits.High" separately? The TestStand step settings seem to suggest that there is a single format that applies to both limits but that might just be a convenience)

[SercoSteveB]

Yep. Using the reference to the Step call AsPropertyObject and then use "Limits.Low" and "Limits.High". I have always done them separately, but that is based more on me finding a way that works and sticking with it rather than investigating further to see if there is a better way (setting them using a single call). I have attached an image from further up in this thread, that shows the sequence of calls in LabVIEW.

[SercoSteveB]

Attaching images is not working, Jon check out page 1 of this thread for the Set Step Limits.png image.

[JonP]

Well I may be daft but I don't see anything related to setting step limits in that link, though I did amuse myself looking through some of your posts!

Maybe it takes a while for NI to generate a new page?

[SercoSteveB]

The link at the bottom of my posts is to my blog, ignore that, it appears at the bottom of all my posts. 

Here is the image I was talking about, for some reason image attachement is now working.

[JonP]

Oh, sorry, you meant the picture on page 1 of *this* post, silly me. However that only shows me what I have already got working, it's the NumericFormat bit that I can't quite get how to do.

BTW your blog post "FOR Loop Count (N) Terminal" of 01-07-2016 has been answered incorrectly by everyone, I guess because the picture got lost and has been incorrectly reconstituted ... unless I really am daft!

[JonP]

I take it back about the blog post, I guess the 4th element of the array is empty, right? It's hard to see that on the pic.- LabVIEW shows a much more faded colour. Anyhow, sorry to go off track!