Property Loader and Multiple Numeric Limits

Question

I’m using a Multiple Numeric Limits Step with 50 measurements. From these 50 measurements I would like to create a limits file. The problem I have is that when I export the properties to a tab delimited file text file it becomes unreadable. I have attached a file with an example of what I mean.
Is there any way to format the limits file so that it is more readable?
Regards
Ray Farmer
Attachments:
example.txt ‏6 KB

Answer 1

Hi Ray and Scott,
 This thread is closest to my challenge, so I wanted to reply
instead of post a new thread.
I may have four or five different (multiple num lim) steps
with 10 – 25 measurements each. So there’s a lot of columns AND
Result.Measurement[3].Comp might be power limits for some steps, jitter for
another and OMA for yet another.
I may also have two to five
different custom steps that have 10 – 25 unique properties each.  This can stretch the top row colunn headings
of a properties file out to 75 – 100 columns.
What is a good or common approach to make property and
limits files more readable/editable by humans? I’ve tried a custom file editor
and a custom property loader, is one approach better, any other ideas? Should I
make steps with many properties or results into subsequences? Thanks
Sincerely,
Chris C.
more context:
I find
reading Ray’s example.txt file in excel better than notepad, but still
more cumbersome than I’d like. I also have the same problem with custom
step types that contain 10 – 25 properties to load at runtime, though this
is a little better because the NAME of the property is used in the column
headers. If I exported properties from a seq with four different steps
with 20 props each, the top property file row stretches out to 80 columns.
If I use Markers I think I can “stack” the column headers in excel and not
have such a wide file.
For
the limits I’m going to need to see the measurement name in the file,
Measurement[“Pave”].Comp instead of 
Measurement[3].Comp. I tried changing this in the limits file and
the Import tool but it wouldn’t work, is it possible?
I
built a limits and property file editor app (jpeg attached) for one
project to make editing easier and less error prone, and also maintain the
native TestStand file formats and property loader. The leftmost column
retains the order of the sequence.
I have
experimented with my own property loader, however it is not based on the
property loader code that comes with TestStand because I did it in
LabVIEW. This produces a file that looks like the attached jpeg and is readable in
Excel, a requirement (or was that a whine?) of my organization. (Can’t use
a database.) However it seems a little dangerous to recreate TestStand
components.
Attachments:
EditTSPropertyFileApp.jpg ‏150 KB