Property Loader and Step Names in TestStand 3.5

Hi All,
I enheritted a job from someone else who left the project unfinished.  There are roughly 100 or more steps all together.  The Property Loader is used to load limits and comparision type into Step.Comp, Step.High.Limit, and Step.Low.Limit from a text (.txt) file.  Step names that were created by the original developer has many charaters that I never thought to include. 
Examples are TN0500.x.zz_DMM: Meas AURID +/- via MRRM Switch, TN0400.x.zz_DMM: Meas AUR Power Path (+), TN0410.x.zz_DMM: Meas AUR Power Parallel 10 ohm, SCNR1: Close Relay for 1PPS +/-, TN0445.x.zz_DMM: Meas MRR Resistance w/ 1 Ohm, etc.
It has space, :, /, +, -, (), etc. as part of the name.  When the Property Load is executed, it appears to load the limits and comparision type from the correct file.  But it seems to load limits from from no where (not exist in the text file) for several steps later.  They are TestStand steps that are group together or in the same sub-sequence.  Also these are limits that are group together in between the same start and and end flags in the text file.
Does anyone know if any certain character such as :, /, ect. in the step name cause any strange behave for TestStand 3.5?
Thanks,
leek

I am eliminating all special characters from the step names, and use underscore (_) to replace space.  So the new step names are one contiguous string.  TesStand is configured to generate a database report file.  Special character may have side effect in the database.
The suspicion of special character comes in when the TestStand is executed, some steps read comparison type, high and low limits fine.  But some steps within the same group that read from the same Start and End flags in the text file appears to read the comparison type and limit values from no where.
Specifically, I have comparison type of "GELE"  20  0, "LT"  20  10, etc.  The failed steps show that it read "LT" 0.  These are resistance measurement.  So the tests failed.  There is no "LT"  0 any where in the limit file.  There are "LT", but not 0.
leek

Similar Messages

  • Property Loader and Multiple Numeric Limits

    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

    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

  • Load "Selected" in a Property Loader test step from file

    Hi,
    The Import/Export tool stores its selected properties in the file �PLPropertyLoader.ini�. Is it possible to use this file to specify which properties a �Property Loader Test Step� should load? How? Then the information about what to export and load dynamically later is stored in the same location and the risk possibilities is reduced to one place.
    Best regards,
    Morten Pedersen
    CIM Industrial Systems A/S
    Denmark

    Morten -
    By default, the Property Loader step type stores its selected property list in the step's property "Step.PropertyList". The Edit Property Loader dialog box has the "Property List Source" expression control that specifies this as its value.
    If you created a Station Globals array property of type "DatabasePropertyMapping", you could specify that the steps use this property. You might have to set to show hidden properties to find the "DatabasePropertyMapping" type in the insert menu. Note that when you do this when you edit the selected list in a step you are editing the selected list stored in the station global array property.
    Scott Richardson (NI)
    Scott Richardson
    National Instruments

  • Property Loader and then Save File

    I have an application where I'm programmatically building my sequence file from a spec document.  I generate a CSV that has all of my properties, and build a dummy sequence from template functions.  I can import the properties to this file using Import/Export, save the file, and then run the rest of my generator sequence, but I need to automate the whole process.
    I am able to use the property loader step from the sequence that I'm actually generating and the parameters are loaded without a problem.  I attempted to move this into my sequence that builds that sequence, and it didn't work.  I GetSequenceFileEX before loading to make sure it's open, perform the load, and then Save the sequence file and ReleaseSequenceFileEX, but it's not doing anything.  Is what I'm trying to do possible, and if so, what am I doing wrong?
    Thanks,
    Bryan

    Hi Bryan,
    First let me make sure I understand your situation.  It sounds like you've already built the sequence that can programmatically build a sequence of template functions then populate using a Property Loader step in the generated sequence.  You are hoping to remove that Property Loader from the generated sequence and instead have the generating sequence load the properties and embed them as defaults in the generated sequence.  This way you would avoid having to run the Property Load step every time you ran this sequence.  Is this correct?
    Assuming it is, I believe this exceeds the capabilities of the Property Loader functionality.  It isn't designed to "push" properties to another sequence.  Therefore your options are to either stick with the Property Loader step at the beginning of your generated sequence or implement the parsing and assigning of the CSV to manually populate the template steps.
    Please post back if I misunderstood you or you have additional questions.

  • Property Loader and Multiple Numeric Limit Test

    Hi!
    I'm trying to export the limits of all numeric limit tests im my sequence.
    I've no idea what i'm doing wrong, but i fail with exporting the limits of the multiple numeric limit tests. There are only the limits of the "normal" numeric limit tests in my export.
    Could someone please explain me how to export also the limits of the multiple numeric limit test?
    (TS 2013)

    when defining what to export, it is usually easiest/cleanest if you can explicitly define all multiple numeric step measurements as explicit indixes? For example if your MNL step has 2 measurements defined, you'd want to export 4 additional matches...
    Step.Result.Measurement[0].Limits.Low
    Step.Result.Measurement[0].Limits.High
    Step.Result.Measurement[1].Limits.Low
    Step.Result.Measurement[1].Limits.High
    ...and so on for more indexes....
    note how the pattern is different from the regular
    Step.Limits.*
    by default when you try to export using the '>' buttons for MNL steps, TestStand will usually try to help by generating an incomplete/invalid expression of:
    Step.Result.Measurement[?].Limits
    which it expects you as the user to fix before proceeding, however the '?' is often overlooked, because it's so small!
    some people prefer to simply export the entire Step.Result.Measurement.* to the file because they'd prefer not to define array indexes, but this will log the explicit XML for the container values, which may not be as easy for end users to work with... your mileage may vary. Good luck!
    -Elaine

  • I"m having trouble using Teststand's " property loader step

    ",I tried using the Demo sequence given with Teststand Ver 1.03(which I"m using) under drive:Teststand\Exersices\Database, it works fine (Test passes) but there is no data in the Local Variables, I know that i got the columens right I might have problems selecting the rows, I tried using the Local's Variable name or step name but it didn't help, I"ll appericiate any idea's

    Hello Kitty -
    I am curious about your problem, have you placed breakpoints in your sequence before and after your property loader Database step to see that the values aren't being loaded? If the step isn't loading properly there is usually some sort of error especially when you have your database of properties set up on the same pattern as the demo. Are you seeing Step.Comp and the Limit values change but not your Local variables? This would be an interesting detail to note. Also, as far as selecting rows the demo goes by "STEPNAME" due to the nature of how the table is set up, if yours follows the same pattern, selecting the same row would be best.
    If you are seeing the changes at Run-time but not when your sequence completes then this is expected behavior and the t
    ool that you may want to use is the "Import/Export Properties..." (Located in the tool menu) to give you more permanent alterations to your sequence. As always, refer to the user manual for a discussion on differences between 'Property Loader', 'Limit Loader', and 'Import/Export Properties...'
    Regards,
    Elaine R.
    National Instruments
    http://www.ni.com/ask

  • How to apply Property Loader to all sequences in the Sequence File?

    HI,
    I'm following the help instructions for the Property Loader and it states....
    Use Current Sequence File—Selects the file where the step is located.
    Sequence—Specifies the name of the sequence into which to import variables and properties. The specified sequence must exist in the specified sequence file. Select the <ALL SEQUENCES> tag from the drop-down list to instruct TestStand to import variables and properties for all of the sequences in the specified sequence file. You must specify a valid sequence name for the step to work properly.
    In my specific sequence file I added the Callbacks:  SequenceFileLoad, SequenceFileUnload, PreUUT. In addition to that, my MainSequence is calling 2 subsequences.
    I put the propertyLoader step (setting few values of the SequenceFileGlobals) in the setup section of the SequenceFileLoad, checked the 'Use Current Sequence File' and selected ALL SEQUENCES tag in the 'Sequence' option.  I verified that it does what I wanted.  Then, is it entered the PreUUT subsequnce, the values returned to the "original" values.
    Is that a bug?
    If not, how do I use the PropertyLoader in a sequenceFile that include several subsequences as well as Callback sequences.
    Thanks
    Rafi

    Ooops, sorry about that...
    I forgot to mention....it is TS 3.5.
    As per your questions-- yes they all in the same sequence file. 
         mySeqFile.seq
               SequenceFileLoad
               SdequnceFileUnload
               PreUUT
               Seq1
               Seq2
    AS I said....I put the property loader in the setup of the SequenceFileLoad,  I see that it works properly in that subsequence.  Then, after the SuequenceFileLoad is finished, I do Ctl+F5 for Test UUT's.  I put a breakpoint in the first step of the preUUT subsequence and check the context.  I notice that the variables in the FileGlobals to whom the property loader writes, have been changed back to the original values.
    I'll try to create a simple program to duplicate it but it may take me time as this test station is very busy.
    Thanks
    Rafi

  • Disable First Row in property loader

    Hi,
    TestStand 2.0.1f1
    I am trying to use the property loader with the option 'First Row of Data Specifies Step Property for Each Column' unchecked.
    I have followed the example text as outline in the User manual Ch8 page69.
    But it seems that the step name is always being checked. I have tried a number of varations but I can not get the property loader to ignore the Step Name.
    I have attached an example with a limit file. Any clues anyone.
    Regards
    Ray Farmer
    Regards
    Ray Farmer
    Attachments:
    Disable_the_First_Row.seq ‏26 KB
    Disable_first_row.txt ‏1 KB

    Ray,
    Using the Property Loader and Import/Export Properties Tool, you have to specify the Step Name. There is no way to ignore the Step Name.
    After reading over the help, I think the confusion may be over what the "First Row of Data Specifies Step Property for Each Column" option means. If you do not check that option (it is selected by default), then you can specify the order of the properties and data values that you will read in from the file. This may be of help because the Import/Export Properties tool does not allow you to modify the order of the properties that are exported.
    For example, if you use the Import/Export Properties tool to export Step.Limits.Comp, Step.Limits.High, and Step.Limits.Low properties to a text file, they will always be written to the file in that exact order (Step.Limits.Comp, Step.Limits.High, and Step.Limits.Low).
    Now if you use the Property Loader to read in that file that you just created, it will automatically map those properties to Step.Limits.Comp, Step.Limits.High, and Step.Limits.Low for a specific step name. If you need to switch the values received in the Property Loader step, you can deselect the checkbox for "First Row of Data Specifies Step Property for Each Column" and instead specify which properties should be associated with those columns from the file. For example, you could deselect the checkbox and then type in the text box:
    Comp, Limits.Low, Limits.High
    This would switch the Low and High data values, ignoring the column titles as written from the Import/Export Properties Tool. If you wanted to, you could even delete or modify the column titles in whatever manner you want to.
    Keep in mind that you still need to have an entry in your properties file for each step name in the sequence that has dynamically loaded values. TestStand will not load properties and apply them to generic steps; the step name is the key for the Property Loader tool.
    I hope this answers your question. If you need further clarification or if I missed a point, just let us know!
    Regards,
    Shannon R.
    Applications Engineer
    National Instruments

  • Significant digits from Property Loader

    Hello guys,
    I'd like to know if anyone already faced that issue, if I load a certain limit from property loader, for example Minimum "10.0", and the VI returns a measure of 9,999472894, the test should pass.
    Is there some easy way to detect the significant digits from the property loader, and automatically apply that rounding to the measured values? Actually it would become heavy to program it test by test.
    Perhaps in my .xls property fils I could put an integer for each limit that represents the number of significant digits...
    Any better idea?

    Correct, TestStand does not base the signficant digits of the comparison off of the significant digits of the given limits, instead it assumes you want a comparison done within the full precision of a double-precision floating point number.
    To fix existing limits, you could write a converter that converts limits like 10.0 to 9.999 since it is a mechanical process that could be done programmatically. Not sure why you would have to hard code limits to fix this problem. Is it not possible to change the limits in the property loader source to 9.999 or that is not an option? If that's not an option, another idea is that we ship the source code to the property loader, you could modify it to convert limits to their precision range values, for example, if a limit of 10.0 is loaded as a lower limit, it could automatically convert it to 9.999 before setting the limit value in the teststand step. That way you wouldn't have to change any sequence files, just the property loader itself.
    Not to say it wouldn't be useful to add a new feature to TestStand to match the precison of the comparison to the precision specified by the limit (or perhaps in a separate setting on the step), but that is not a common request. You could post such an idea to the idea exchange though and see what people think.
    -Doug

  • Rename Step.Name while editing the step

    Hi
    I have some SequenceFile librarys which i like to improve for more easy of use.
    Most of my librarys are using parameters to descripe what should be done.
    I have realized that often things have to done twice. 
    At first you select a SequenceCall StepType and give a name to it. Normally it descripes 
    what Sequence is doing. Then you have to set your parameters values. In a lot of
    cases Step.Name and Parameters where in relation. There are some possbilities to change the Step.Name 
    during runtime. But what about editime ?
    I assume i have to create my own StepType which is derived from Ni SequenceCall StypType. I think thats not the
    major problem. The main question is: Is it possible to rename it to my needs and force it to update in Sequence Editor
    Regards
    Juergen
    =s=i=g=n=a=t=u=r=e= Click on the Star and see what happens :-) =s=i=g=n=a=t=u=r=e=
    Solved!
    Go to Solution.

    Hi Doug
    good question. I agree that desciption would be the first choise for doing this. But for my task there is no need for the description field.
    For my stuff it is more important to have a link between Sequence and Report. And this is the Step.Name. If some thing went wrong.
    You are looking a the report. Remember the Step.Name and try to find in the Sequence. I am of the opinion the Step.Name descripes your
    Task,Requierement or what you think the system should do. On the other hand Step.Description is telling you what system is doing.
    At the moment i am in a project where i have created some sequence(files) librarys. In inside the sequences there is all what i have learned about
    Teststand. No beginner will understand whats going on there. So i have designed some sequences where you can define with parameters
    what the system should do. I have realized that my Paramters and Step.Name are in relation.
    At the moment you have to do things twice, Change parameters values and rename step in the same way.
    I like to this only once. And get rid of ts programming errors. How often i only changed only one. After system was running -> "Red"
    -> reading report -> Oh man what are doing !! -> enter the forgotten second value -> system running -> green!  
    Regards
    Juergen
    =s=i=g=n=a=t=u=r=e= Click on the Star and see what happens :-) =s=i=g=n=a=t=u=r=e=

  • How to access the Requirements property (& subproperties) of steps and sequences with the TestStand API

    The concept of associating teststand objects to unit requirements for traceability purposes was added to TS 3.5, and I need to find out how to access the array of strings used to store unit requirements in step objects, sequence objects and sequencefile objects. The teststand help file points out that the requirements list of a sequencefile object is accessible using the PropertyObjectFile interface, and also points out that Requirements is a property of the sequence and step classes. Furthermore it implicitly states that the requirements property has a Links subproperty which is an array of strings, but that is pretty much the extent of the documentation on this new feature so far. There seems to be no expression function available to get to those requirements either.
    I know that this feature was added to allow TestStand to interface with RG, and I am planning on using RG, but I would also like to do things with the requirements information within TestStand.
    Anyone? 

    Are you talking about the Requirements Gateway?  It is a separate product from NI that will do what you are looking for.  I haven't used it so I am not sure of the API chain to make it work.  Take a look and see if that is what you were thinking of.
    Hope that this helps,
    Bob Young
    Sorry, I just re-read your original post and see that you are looking to also use the Requirements Gateway, so you obviously know about it.  I don't know what the API changes were that made it work so I am not going to be much help.
    Sorry about posting before getting the correct information from the original.
    Bob Young
    Message Edited by Bob Y. on 08-24-2006 04:54 PM
    Bob Young - Test Engineer - Lapsed Certified LabVIEW Developer
    DISTek Integration, Inc. - NI Alliance Member
    mailto:[email protected]

  • How to Use Property Loader to Load All Step Limits of SubSequence

    I have a MainSequence which have 7 Sequence Call Steps,and these Steps all have several Numeric Limit Test(LabVIEW Adapter),Now I want Creat a property Loader Step in the Setup Table of MainSequence to load all the SubSequences' Steps Limits.But I do not know how to realize it?Who Can help me,Thank you!

    It wasn't your english I just misread the question. I found this link that might help answer your question.
    http://forums.ni.com/ni/board/message?board.id=330&message.id=13163&requireLogin=False
    Hope it helps.
    Using LabVIEW 2010SP1 and TestStand 4.5

  • Teststand property loader for multiple sequences

    Hi, I am using Teststand 3, and would like to be able to Export all sequences into one Excel spreadsheet, so that each tab references a single sequence. If anybody has already done this, or has a suggestion as to how to do it, I would be grateful. The end goal is to create a single excel file, that can be emailed around, without people losing track of all the different excel sequence files.

    ADL,
    Unfortunately, there is no way to do this with the property loader features of TestStand. The Import/Export Property tool does not distinguish between worksheets in a workbook and the Property Loader step type can only import properties. If you really need this functionality, one possibility is to use the ActiveX methods exposed by Excel to populate an Excel workbook.
    Regards,
    Matt P.
    Applications Engineer
    National Instruments

  • Using Property Loader with Renamed Steps

    If I have a test step in a loop where the step is renamed using RenamePreviousStep after each iteration, is there a simple way to use Property Loader to load test limits corresponding to the dynamically changing test name?
    The only way I have found to do this so far causes errors at runtime on the non-existent step names in the file which have to be ignored. Also it is not very slick to call PropertyLoader every time the loop iterates.
    Is there a more elegant way to load limits for steps which "don't yet exist"?

    How do you organise your limit file.
    Do you have a different Start/End Marker for each of your iterations
    so that you have the correctly named step(s) between the markers?
    You could try loading an array of limits into a local array(s) from
    your Limit File then index through the array as the datasource for your
    limits. Remember its a PropertyLoader, so its not limited to just
    limits. That way you only read it once and you are not tied to the Step
    name.
    I originally had all limits within a single Start-End marker pair. Having now given each limit set an individual Start-End marker and setting PropertiesListSource dynamically in the Loader Step in the loop, that works OK.  Perhaps not so elegant still as each iteration of the loop requires a Property Loader step instead of loading everything in one hit (I'm guessing there has to be some performance overhead in multiple property loader calls vs. a single load of all limits) but at least there are no errors on the loader step now I am only loading that test which exists after the loop rename.
    The alternative of loading data into arrays had ocurred to me and I may experiment with this if performance becomes an issue with the first approach.
    Thanks for your reply Ray, its much appreiated.

  • Can I set the "step run mode" -property with the property loader

    Is it possible to set the "step run mode"-property  by using the property loader to "Skip" , "Normal" or "Force PASS" ...in TestStand 3.0 ?

    I turned on Station Options>>Preferences>>Show Hidden Properties and then exported the Step.TS.Mode property to a limits file. I then added a PropertyLoader step and it functioned correctly. 
    Note that importing a hidden TS subproperty makes an edit to the sequence file, even if done at runtime. Thus if you later save the file, you might end up inadvertently saving the last imported values. This isn't necessarily a problem if the values in the file are always overwritten by a property loader step.
    (btw, I tested this in 4.0, but I'm hopeful it would also work in 3.0)

Maybe you are looking for