However, as we mentioned before, TestStand already includes a lot of common, useful features having to do with automating a test, so make sure you know them! Leverage TestStandĪs LabVIEW developers, we are used to having to write most of the functionality we require for our application to work and this tends to carry over to our test sequence design. Failure to do this means that TestStand can (and eventually will!) get stuck, waiting for ever for the return value of a VI that will never finish executing, forcing the user to terminate TestStand’s execution to continue. If there’s no option but to use a loop, make sure that you know when that VI is going to stop, either by executing your FOR loops a clearly defined maximum amount of times or implementing timeout logic when using a WHILE loop. For most other cases, my recommendation is to not include any FOR or WHILE loops in your LabVIEW code.įigure 2 Simple VI's that perform a single task and execute only once are TestStand's idea of a perfect module
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |