Editing a Property loader locks up TS

I can add a property loader step to my sequence, but when I go to edit the loader, my TS session locks up. This is true for every installation that I have installed TS on. I must have missed something in the installation, but can't think of where I went wrong.
rjmiller

Share_Good
1. Does it happen every time you open the property loader step configuration dialog?.
2. Could you attach an example?
Property loader configuration dialog seemed to hang in TestStand 3.1 if your sequence contained very long arrays.
This issue was resolved with the service pack.
If you are seeing a similar behavior in TestStand 4.2 it is likely that is not the same issue found in TestStand 3.1.
Regards.

Similar Messages

  • Edit "Edit Property Loader..." cause an ActiveX Error

    Hello
    I have just make a fresh install of TS 3.1f1
    I have inserted a Property Loader step, and whenn I click on "Edit Property Loader..." button I get an ActiveX error:
    sCode = 0xffffbc66, Description: Unknow variable or property name 'SequenceFile'. Error accessing item 'SequenceFile'.
    Regards,
    Yannick Willener

    hi,
    Can you call the
    "\Examples\PropertyLoader\PropertyLoader.seq " and test this sequence? If you cann't run this sequence succsessfully may be you have to deinstall TS and install it again. If you run the sequence successfully than it seems that you have some problems with calling values through activeX. Check please the format of variables.
    Regards
    TN

  • High library cache load lock waits in AWR

    Hi All,
    Today i faced a significant performance problem related to shared pool. I made some observations, thought it would be a nice idea to share them with Oracle experts. Please feel free to add your observations/recommendations and correct me where i am wrong.
    Here are the excerpts from AWR report created for the problem timing. Database server is on 10.2.0.3 and running with 2*16 configuration. DB cache size is 4,000M and shared pool size is of 3008M.
    Snap Id Snap Time Sessions Cursors/Session
    Begin Snap: 9994 29-Jun-09 10:00:07 672 66.3
    End Snap: 10001 29-Jun-09 17:00:49 651 64.4
    Elapsed:   420.70 (mins)    
    DB Time:   4,045.34 (mins)   -- Very poor response time visible from difference between DB time and elapsed time.
    Load Profile
    Per Second Per Transaction
    Redo size: 248,954.70 23,511.82
    Logical reads: 116,107.04 10,965.40
    Block changes: 1,357.13 128.17
    Physical reads: 125.49 11.85
    Physical writes: 51.49 4.86
    User calls: 224.69 21.22
    Parses: 235.22 22.21
    Hard parses: 4.83 0.46
    Sorts: 102.94 9.72
    Logons: 1.12 0.11
    Executes: 821.11 77.55
    Transactions: 10.59   -- User calls and Parse count are almost same, means most of the calls are for parse. Most of the parses are soft. Per transaction 22 parses are very high figure.
    -- Not much disk I/O activity. Most of the reads are being satisfy from memory.
    Instance Efficiency
    Buffer Nowait %: 100.00 Redo NoWait %: 100.00
    Buffer Hit %: 99.92 In-memory Sort %: 100.00
    Library Hit %: 98.92 Soft Parse %: 97.95
    Execute to Parse %: 71.35 Latch Hit %: 99.98
    Parse CPU to Parse Elapsd %: 16.82 % Non-Parse CPU: 91.41 -- Low execute to parse ratio denotes CPU is significantly busy in parsing. Soft Parse% showing, most of the parse are soft parses. It means we should concentrate on soft parsing activity.
    -- Parse CPU to Parse Elapsed % is quite low, means some bottleneck is there related to parsing. It could be a side-effect of huge parsing pressure. Like CPU cycles are not available.
    Shared Pool Statistics
    Begin End
    Memory Usage %: 81.01 81.92
    % SQL with executions>1: 88.51 86.93
    % Memory for SQL w/exec>1: 86.16 86.76 -- Shared Pool memory seems ok (in 80% range)
    -- 88% of the SQLs are repeating ones. It's a good sign.
    Top 5 Timed Events
    Event Waits Time(s) Avg Wait(ms) % Total Call Time Wait Class
    library cache load lock 24,243 64,286 2,652 26.5 Concurrency
    db file sequential read 1,580,769 42,267 27 17.4 User I/O
    CPU time   33,039   13.6  
    latch: library cache 53,013 29,194 551 12.0 Concurrency
    db file scattered read 151,669 13,550 89 5.6 User I/O Problem-1: Contention on Library cache: May be due to under-sized shared pool, incorrect parameters, poor application design, But since we already observed that most of the parses are soft parses and shared pool usgae in 80%, seems problem related to holding cursors. open_cursors/session_cached_cursors are red flags.
    Problem-2: User I/O, may be due to poor SQLs, I/O sub-system, or poor physical design (wrong indexes are being used as DB file seq reads)
    Wait Class
    Wait Class Waits %Time -outs Total Wait Time (s) Avg wait (ms) Waits /txn
    Concurrency 170,577 44.58 109,020 639 0.64
    User I/O 2,001,978 0.00 59,662 30 7.49
    System I/O 564,771 0.00 8,069 14 2.11
    Application 145,106 1.25 6,352 44 0.54
    Commit 176,671 0.37 4,528 26 0.66
    Other 27,557 6.31 2,532 92 0.10
    Network 6,862,704 0.00 696 0 25.68
    Configuration 3,858 3.71 141 37 0.01
    Wait Events
    Event Waits %Time -outs Total Wait Time (s) Avg wait (ms) Waits /txn
    library cache load lock 24,243 83.95 64,286 2652 0.09
    db file sequential read 1,580,769 0.00 42,267 27 5.91
    latch: library cache 53,013 0.00 29,194 551 0.20
    db file scattered read 151,669 0.00 13,550 89 0.57
    latch: shared pool 25,403 0.00 12,969 511 0.10
    log file sync 176,671 0.37 4,528 26 0.66
    enq: TM - contention 1,455 90.93 3,975 2732 0.01 Instance Activity Stats
    opened cursors cumulative 5,290,760 209.60 19.80
    parse count (failures) 6,181 0.24 0.02
    parse count (hard) 121,841 4.83 0.46
    parse count (total) 5,937,336 235.22 22.21
    parse time cpu 283,787 11.24 1.06
    parse time elapsed 1,687,096 66.84 6.31 Latch Activity
    library cache 85,042,375 0.15 0.43 29194 304,831 7.16
    library cache load lock 257,089 0.00 1.20 0 69,065 0.00
    library cache lock 41,467,300 0.02 0.07 6 2,714 0.07
    library cache lock allocation 730,422 0.00 0.44 0 0  
    library cache pin 28,453,986 0.01 0.16 8 167 0.00
    library cache pin allocation 509,000 0.00 0.38 0 0 Init.ora parameters
    cursor_sharing= EXACT
    open_cursors= 3000
    session_cached_cursors= 0
    -- open_cursors value is too high. I have checked that maximum usage by a single session is 12%.
    -- session_cached_cursors are 0 causing soft parsing. 500/600 is good number to start with.
    cursor_sharing exact may cause hard parses. But here, hard parsing is comparatively small, we can ignore this.
    From v$librarycache
    NAMESPACE             GETS    GETHITS GETHITRATIO       PINS PINHITRATIO    RELOADS INVALIDATIONS
    SQL AREA            162827      25127  .154317159  748901435  .999153087     107941         81886-- high invalidation count due to DDL like activities.
    -- high reloads due to small library cache.
    -- hit ratio too small.
    -- Need to pin frequently executed objects into library cache.
    P.S. Same question asked on Oracle_L, but due to formatting reasons, pasing duplicate contents here.
    Regards,
    Neeraj Bhatia
    Edited by: Neeraj.Bhatia2 on Jul 13, 2009 6:51 AM                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

    Thanks Charles. I really appreciate your efforts to diagnose the issue.
    I agree with you performance issue is caused by soft parsing, which can be solved by holding cursors (session_cached_cursors). It may be due to oversized shared pool, which is causing delay in searching child cursors.
    My second thought is, there is large number of reloads, which can be due to under-sized shared pool, if invalidation activities are not going (CBO statistics collection, DDL etc), cursors are being flushed frequently.
    CPU utilization is continuously high (above 90%). Pasting additional information from same AWR report.
    Namespace                Get Requests       Pct Miss        Pin Requests         Pct Miss      Reloads        Invalidations
    BODY                       225,345               0.76            4,965,541            0.15           5,533           0
    CLUSTER                   1,278                  1.41            2,542                  1.73           26                0
    INDEX                       5,982                  9.31            13,922                7.35           258               0
    SQL AREA                  141,465              54.10           27,831,235         1.21           69,863          19,085 Latch Miss Sources
    Latch Name             Where                                         NoWait Misses                 Sleeps             Waiter Sleeps
    library cache lock       kgllkdl: child: no lock handle             0                                   8,250                   5,792 Time Model Statistics
    Statistic Name                                                                           Time (s)                               % of DB Time
    sql execute elapsed time                                                           206,979.31                                      85.27
    PL/SQL execution elapsed time                                                    94,651.78                                      39.00
    DB CPU                                                                                     33,039.29                                      13.61
    parse time elapsed                                                                      22,635.47                                       9.33
    inbound PL/SQL rpc elapsed time                                                  14,763.48                                       6.08
    hard parse elapsed time                                                               14,136.77                                       5.82
    connection management call elapsed time                                        1,625.07                                       0.67
    PL/SQL compilation elapsed time                                                        760.76                                       0.31
    repeated bind elapsed time                                                               664.81                                       0.27
    hard parse (sharing criteria) elapsed time                                             500.11                                       0.21
    Java execution elapsed time                                                              252.95                                       0.10
    failed parse elapsed time                                                                   167.23                                       0.07
    hard parse (bind mismatch) elapsed time                                             124.11                                       0.05
    sequence load elapsed time                                                                23.34                                        0.01
    DB time                                                                                   242,720.12  
    background elapsed time                                                             11,645.52  
    background cpu time                                                                      247.25 According to this DB CPU is 65% utilization (DB CPU + Background CPU / Total Available CPU seconds). While at the same time DB host was 95% utilized (confirmed from DBA_HIST_SYSMETRIC_SUMMARY).
    Operating System Statistics
    Statistic                                         Total
    BUSY_TIME                             3,586,030
    IDLE_TIME                              1,545,064
    IOWAIT_TIME                              22,237
    NICE_TIME                                           0
    SYS_TIME                                  197,661
    USER_TIME                              3,319,452
    LOAD                                                 11
    RSRC_MGR_CPU_WAIT_TIME                  0
    PHYSICAL_MEMORY_BYTES          867,180
    NUM_CPUS                                           2

  • 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

  • Best way for using Property Loader with Excel

    I am trying to architect a test system to run a variety of tests (DIO, AIO, PWM...etc) and I noticed that Property Loader can be quite handy. I am trying to find the best method to utilize NI TestStand Property Loader to load test properties from Excel into some sort of parameter database. The properties shall be loaded only once when the test sequence is opened. The parameters of the excel table will have a format like this:
    TestType TestCondition  ECUPin#   Limits.High    Limits.Low  Units  PWM_Frequency  CAN_TX   CAN_RX
    DI            ON                    1                                                                                      0x0102   0x0304
    AI            OFF                   2                0             0.1                V                                0x1324   0x0405
    The table will look much more complex than this one, but once I know how to do this I should be fine. Does anyone have suggestions for what I am trying to do ?
    Thanks,
    Ayman

    There are a couple methods of thought here:
    Property Loader-  You can use the tool to export and import properties.  The best way to do it is to export the properties that you want in the Excel file using the tool.  Then make copies of the file and change the values in there.  This will ensure that once the values come back into TestStand they will all go to the correct place.
    FileGlobals Method-  You can create a large container which has all the correct variables in it in your file globals or locals.  There is an object in the TS API called a PropertyObjectFile.  This file is a simple text file that contains the properties, sub properties and values of any property object in TS.  You can easily just pass the container into it.  The problem with this is that you then have to create a VI or some tool to edit the values in it.  You can go in there and manually change them but it's not as intuitive.
    Property Loader to FileGlobal Container-  This would basically be a hybrid of the two.  Pretty much what you described in your post.  Where the property loader only has to load the container in your FileGlobals.
    Which method is best? It all depends on your application.  If you ever need to dynamically export the properties then you can't use the Property Loader. 
    One thing to remember is that you should only Import/Export properties that need to be changed in the Excel file.  This will help reduce the number of properties. 
    Hope this helps,
    jigg
    CTA, CLA
    teststandhelp.com
    ~Will work for kudos and/or BBQ~

  • 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 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 loader error

    I have created a test for 50 measurements. This requires the property loader to read:
    1 off StationGlobals.CurrentTestName
    1 off StationGlobals.FailTarget
    1 off StationGlobals.PassTarget
    1 off Step.Comp
    1 off Step.Limits.High
    1 off Step.Limits.Low
    Array 0f [0] to [49] of:
    Step.Result.Measurement[*].Comp
    Step.Result.Measurement[*].Limits.High
    Step.Result.Measurement[*].Limits.Low
    To test this a single block program was written. The above was entered into the property loader step. All variables pointing to the reference files and the file start and stop label are set up by local variables. The limits file was manual altered and trial values entered.
    The program ran and loaded all limits successfully.
    I have a large program under development that I could not get this function to work in. I copied the property loader step and limits string from the working files into the larger program. I have checked the correct variables are being passed to the property loader for the limits source file name and the Data Start and End Markers. Everything looks fine but when I run the program I get an error message saying:
    Sequence File: 1065-32911_Block09_RDVS.seq
    Property loader step failed to import or export properties.
    153 property value(s) were found.
    3 property value(s) were imported from 6 row(s) of data
    I even tried copying the complete performance test across and the whole of the limits section for that performance test too. It still won’t work.
    Also, what does the error message
    3 property value(s) were imported from 6 row(s) of data
    actually mean anyway?
    I've attached a text file with the individual linits test text.
    Attachments:
    Multilim.txt ‏6 KB

    BrianM,
    It seems that the properties does not exist in your current context.
    'Rows of data' means the number of lines in your text file within the data markers.
    Is the error message you are providing complete?
    Did you copy the message from the Run-Time error dialog?.
    Make sure you have the same steps you had originally and that the steps contains tha same properties (measurements).
    In this case you should aways have a step called 'Test Multiple Numeric' containing 50 measurements.
    It is very importatnt that the step name is the same.
    It seems to me that the step is only being able to import the station globals.
    You can verify it by ignoring the error and checking the station globals values after the step executes.
    Hope it helps.
    If you have any question let me know.
    Antonio Lie.
    Message Edited by Antonio Lie (NI) on 04-12-2006 12:46 PM

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

  • Can the Property Loader load arrays of variable size?

    I need to run a series of tests on the same UUT, changing only one parameter at a time (for example, a frequency response test). The hardware developers would like to be able to change the values of parameters of the test at will, without making changes to the sequence. That's easy - just change the value of the parameter in the Properties file. The hard part is changing the number of iterations of the test, by ONLY adding or deleting the number of parameters from the text file. In other words, all I know during sequence editing is the types of parameters, not the values or how many. I want the test to loop as many times as there are sets of parameters in the text file.
    I would like to do this by loading the paramet
    ers as an array. But the Property Loader wants me to specify each variable while I am editing the sequence, including each individual member of the array (e.g. "Locals.Array[0].Value"). I want to do somthing like "Locals.Array[*].Value", where "*" means "all elements".
    Am I forced to write external code to load each parameter, or does TS have a native way to do this? Even better, has anybody done this already, and will you explain how? Thanks

    Hi,
    there's a couple of options here, and I've included what I think is the simplest below (using TestStand 2.0.1).
    It's not exactly elegant though. What I've done is to put in a step that finds out the number of steps to load (based on an earlier decision - in this case a message popup step). I read a number from the limits file, and use this in the looping options of the property loader step that's loading the values into the array. I've done it with a fixed size array target here, big enough to take any incoming data. (Otherwise, knowing how many items you're going to load from the limits file, you could start with an empty array and re-size it prior to loading).
    I've cheated slightly by using the pre-expression on the property loader step to specify where th
    e data is coming from and where it's going to in the sequence on each iteration of the loop based on the Runstate.Loopindex.
    Another option is to go straight into the property loader step, and keep loading properties until the Step.Result.NumPropertiesRead = 0 (remember we're only doing this one at a time)
    Another idea would be to load in a value, and check it isn't a "flag" value (i.e. you'd never use say 999 in your array, so set the last element in your limits file to this, and drop out of the loop when this happens.
    Further still, you've got the source code for the property loader step, so you could re-write it to make a custom step that loads an array until it fails all on its own (no looping in TestStand).
    Hope this gets you going
    S.
    // it takes almost no time to rate an answer
    Attachments:
    DynamicPropertyLoader.seq ‏32 KB

  • Loader locks images it has loaded

    Hi
    I am trying to create a simple flash that loads an image from my HardDrive. The following is my simple program:
    package {
    import flash.display.Sprite;
    import flash.events.*;
    import flash.display.Loader;
    import flash.net.URLRequest;
    import flash.display.Bitmap;
    public class Test extends Sprite {
      private var imgLoader:Loader;
      public function Test() {
       imgLoader= new Loader();
       imgLoader.contentLoaderInfo.addEventListener(Event.COMPLETE, onLoaderReady, false, 0, true);
       imgLoader.load(new URLRequest("test_image.png"));
       //imgLoader.close();
      private function onLoaderReady(e:Event) {
       //imgLoader.close();
       var b = Bitmap(e.target.content);
       b.x = 100;
       b.y = 100;
       addChild(b);
    however, I have noted that while this flash is opened, even though the loader has finished loading the image and the image is currently being displayed, I can not edit the image with any other program. (It will complain that the image is currently being used by another program.)
    I have found that if i use the close() function for the Loader, it will release the lock. however, if i try to close the loader in my event complete function (because i want to close the loader only after when the image has finished loading), it will complain with the following error:
    Error: Error #2029: This URLStream object does not have a stream opened.
    Does anyone knows how to release the lock the Loader has acquired after when the image has finished loading?
    thankyou very much in advance.

    i'm thinking of writing a small program so that the client (swf) will load an image. While the client is being opened, the server might want to modify the image.  after the image has been modified, it can notify the client that it has been modified and the client will refresh the image and get the latest image.
    Date: Thu, 12 Jan 2012 22:58:51 -0700
    From: [email protected]
    To: [email protected]
    Subject: Loader locks images it has loaded
        Re: Loader locks images it has loaded
        created by kglad in Action Script 3 - View the full discussion
    i don't think there's a work-around and i can't see any purpose.  why do you want to do that?
         Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page: http://forums.adobe.com/message/4137609#4137609
         To unsubscribe from this thread, please visit the message page at http://forums.adobe.com/message/4137609#4137609. In the Actions box on the right, click the Stop Email Notifications link.
         Start a new discussion in Action Script 3 by email or at Adobe Forums
      For more information about maintaining your forum email notifications please go to http://forums.adobe.com/message/2936746#2936746.

  • 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

  • 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

Maybe you are looking for