Step.Prope​rtiesList in property loader step

what does the Step.PropertiesList property do in the property loader step. can it be used effectively to achieve some required operation.
Thanks 

Hi
This might be of some help....
http://forums.ni.com/ni/board/message?board.id=330​&message.id=3183&requireLogin=False
Vaibhav
.......^___________________^
....../ '---_BOT ____________ ]
...../_==O;;;;;;;;_______.:/

Similar Messages

  • 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

  • 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

  • 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.

  • 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

  • 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)

  • 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

  • Property Loader - How to set it up for all sequences?

    Hi,
    I made an attempt to use the property loader for the first time. (TS3.5).
    I set it up in the setup section of the SequenceFileLoad and specified few parameters of the FileGlobals.
    What happened was a proper operation for the SequenceFileLoad sequence, but as soon as the procedure stepped into the MainSequence, the values return to the original values.  I repeated the process with and without import to Run-time sequence only' and it behaved the same.
    Is there a way to set it up so ti will apply to all sequences within my sequence file and also to the external sequence files called from the main sequence.  In short to replace the parameters of the FileGlobals for the duration fo the test.
    Thanks
    Rafi

    Rafi,
    The behavior you are seeing with the SequenceFileLoad engine callback is expected.  The SequenceFileLoad callback occurs before the Sequence File is actually loaded.  In your case, you are setting the FileGlobals then loading the SequenceFile.  When the Sequence File is loaded by the engine, the FileGlobals are also loaded in with the file.  So the FileGlobals are reset to their default values.  If you want to set the FileGlobals from the property loader, put the Property Loader step in the Setup group of the MainSequence.  In this case, you are setting the values of the FileGlobals after the Sequence File is already loaded.
    FileGlobals only have a scope that covers a SequenceFile.  You will not
    be able to load FileGlobals that are accessible to sequences in
    external sequence files.  You have a few options for getting the data into the external sequences:
    (1)  Add parameter variables to the Parameters section of each external sequence.  When the sequence is then invoked, you can pass the data which will be used by the sequence.  This provides the proper data dependency between sequences and avoids confusion on when the data is being initialized.
    (2)  For each Sequence File or each Sequence, create a separate property file.  When each sequence is called, then use the Property Loader step to load in the data.
    (3)  Use StationGlobals instead of FileGlobals.  StationGlobals have a scope that covers all SequenceFiles on a test station.  However, this is not a recommended method, because the data is accessible to all sequences.  For large applications, it is easy to mistake points in the sequences where data is being initialized and used.  In these cases, you may expect the data to be a certain value that it isn't because another Sequence has already changed the data values.  That is why it is better to use smaller scoped data variables.
    Let me know if you have any further questions.
    Thanks,
    Tyler T

  • 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

  • Property loading an empty array

    I have an array that I want to initialize from text file using a property loader step.  I want the number of elements of the initialized array to be equal to the number of elements in  the array in the text file.  I tried to accomplish this by defining the TestStand array empty and importing all properties from the text file.  This resulted in an error message for each property in the array - here's a snippet of the error messages:
    Error evaluating expression:FileGlobals.Arinc629.Limits.Label[0].Address = (0xE90)
    Property does not exist.
    The text file I'm loading the properties from is attached.  The properties are loaded successfully if I define the TestStand array with a size bigger or equal to the number of elements in the text file.  But I want to have the text file to dictate how many elements are in the TestStand array.  Is there a good way to do that?
    Thanks,
    Hans
    Message Edited by hans17 on 11-05-2008 06:28 PM

    Hans,
    What version of TestStand are you using?
    Starting with TestStand 3.1 you can import/export arrays and containers as XML strings.
    If
    you want to be able to set the array bounds in the text file all you
    have to do is to modify the LBound and HBound attributes in the
    corresponding XML Prop tag and add the Value tags corresponding to the
    elements you want to add.
    For example.
    Let's assume I have an numeric array local variable named MyArray (Locals.MyArray).
    The first thing I would do is to use the Import/Export Properties tool to generate my text file.
    1. Make sure that the Locals.MyArray variable is not empty (In my case Lower Bound =0 and Upper Bound= 9)
    2.  Go to Tools>>Import/Export Properties
    3. Go to the Source/Destination tab and  specify your text file location
    4.  Go to the properties tab and add Locals.MyArray to the selected properties list
    5. Click the Export  button
    6. Open your text file and verify it looks as follows:
    <Step Name>
    <Locals>    Variable Value
    MyArray   
    <Prop Name='MyArray' Type='Array' LBound='[0]' HBound='[9]'
    ElementType='Number'><Value ID='[0]'>0</Value><Value
    ID='[1]'>0</Value><Value
    ID='[2]'>0</Value><Value
    ID='[3]'>0</Value><Value
    ID='[4]'>0</Value><Value
    ID='[5]'>0</Value><Value
    ID='[6]'>0</Value><Value
    ID='[7]'>0</Value><Value
    ID='[8]'>0</Value><Value
    ID='[9]'>0</Value></Prop>
    <FileGlobals>    Variable Value
    <StationGlobals>    Variable Value
    7. In my case I only exported the Locals.MyArray variable
    8. Notice that the Value of the Locals.MyArray variable is a XML string that contains a Value tag for each element in the array.
    9. 
    If I want to change the number of elements in the array next time I
    import the text file, I only have tp modify the LBound and HBound
    attributes and add or remove the value tags for the array elements.
    10.
    Let's say that I want my array to have only one element, then I need to
    set the value of HBound to 0 and get rid of the Value tags
    corresponding to the rest of the elements.
     <Step Name>
    <Locals>    Variable Value
    MyArray  
     <Prop Name='MyArray' Type='Array' LBound='[0]' HBound='[0]'
    ElementType='Number'><Value
    ID='[0]'>0</Value></Prop>
    <FileGlobals>    Variable Value
    <StationGlobals>    Variable Value
    11.  Modify your text file and use the Import/Export Properties tool or the property loader step to import the text file
    12 . Verify that the array bounds are modified
    You could use this technique to initialize an empty array using the property loader.
    Hope it helps.
     Regards.

  • How to use the property-loader?

    Hello,
    i´m using TS 3.5 and LV 8.0. Now i also want to use the built-in property-loader from Teststand.
    Is there somewhere a documentation for "beginners" how to use this property-loader? At the end i want to read parameters from an ascii-file which updates my input-parameters of the steps in the current-sequence.
    I know how to read and change parameters from teststand in labview via active-x, but i have no idea how to use this propertyloader-thing.
    Is there an easy help file somewhere in the net ( I havent found one yet)?
    Thanks for your help.

    Meanwhile i can use the propertyloader for Limits and Variables which are in a container of the teststep. What not worked was:
    1.) setting the properties of a "Messagebox". For example the property "Button1Label". Why is this not working?
    2.) The second thing what is not clear: Do i need for each sequence an own property-loader? I tested it with a sequence with one subsequence. Does the subsequence needs its own property-loader?
    Currently the import-csv-file looks like this:
    Start Marker,,,
    <Step Name>,Limits.Low,Limits.High,Cont.Voltage
    TestStep_1,1,2,4
    TestStep_2,8,16,32
    End Marker,,,
    When Teststep_1 and Teststep_2 are both in mainsequence then it works. When i copy Teststep_2 in a subsequence then i get an error (-18).
    Any ideas about my two questions?
    Thanks

  • Error while importing a big array with thr property loader

    Hello,
    the following problems occure: when I want to import a *.txt file with a array of more than arround 3300 members with the property loader, the following error meassage occures:
    property loader step failed to import or export properties
    x property values were found
    x-1 property values were imported from y rows
    Error code: -18, user defined error code.
    how can I solve this problem?
    I think sizes of arrays are limited somewhere in the source code of the property loader. is it possible to increase this size? And how?
    regards samuel

    Could you attach an example of your .txt file and your sequence?

  • 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

  • Property loader / property saver

    Property loader works really well, but I have a question ...
    Where is the ability to 'Property save?'. I see the menu item, import/export properties.
    Is there an equivalent test stand statement that allows me to save properties from a sequence while it is executing?

    checkers18,
    I am attaching a simple example that uses TestStand database step types to update the values in the database.
    The attachment contains an Access database (testdb.mdb). The table where the calibration values are stores is LIMITS.
    I created 3 calibration values to impor (export).
    FileGlobals.CalibrationVal1.
    FileGlobals.CalibrationVal2.
    FileGlobals.CalibrationVal3.
    The sequence imports the calibration values from the database using a property loader step.
    In order to pretend the values changed I ask the user to enter the new values manually one by one.
    I store the temporary new values in local variables using a post expression.
    Finally I update the values in the database using a DataOperation step.
    Hope it helps.
    Let me know if you have any problem.
    I used TS 3.5 and Microsoft Access 2003 to create the database.
    Antonio Lie
    Message Edited by Antonio Lie (NI) on 10-03-2006 09:51 AM
    Attachments:
    Example1.zip ‏19 KB

  • Using Property Loader in a sub-sequence with multiple invocations

    I'm using the Property Loader to load a different set of limits for each invocation of a sub-sequence. In my example, I have a sequence to do tests all the tests on a given RF band. But I want the ability to specify different test limits for each band.
    It wasn't hard to come up with an expression based on Parameters.Band to specify different Start and End data markers in the Property Loader step. So far so good.
    I don't necessarily want to override the same limits in every band. For one band, I might be happy with a default limit from the sequence file itself. Trouble is, if I don't specify a limit in the limit-file for a given band, then the limit loaded by the previous invocation of the sub-sequ
    ence is still in effect. This was a surprising behaviour. There's a huge opportunity for errors to creep in here, because the limit files may be edited by "lusers", and it's hard to explain this pitfall.
    Is there an easy way to make the limits reset to the sequence-file defaults before I call the Property Loader? Or alternatively, to make the loaded limits affect only the present invocation of the subsequence (the same way loading Locals only affects the present invocation?)
    BTW, I'm not actually using the official TestStand Property Loader, which I find too unwieldy. We wrote our own Property Loader. But the problem is common to both. Changes to RunState.Sequence.Main... persist across invocations of the sequence.
    - Ron

    Here I go, answering my own question again. For the benefit of anyone else who ever runs up against this...
    The trick is in the Sequence Properties dialog. Turn off "Optimize Non-Reentrant Calls to This Sequence". The little comment there makes it pretty clear that this is what's needed. I tried it, and it works.
    - Ron

Maybe you are looking for