Using a batchfile with Teststand

Has anyone used a batch scripts with teststand and or know of any resources on writing batch scripts?
Brian

Hi Brian:
In order to do this in TestStand, you can use the Call Executable step.  If you right click anywhere in a sequence in the TestStand sequence editor, you can find the Call Executable step.  Here you can specify the path to your batch file.
Thank you
Nandini

Similar Messages

  • Problems in using Labview DLL with TestStand!

    Hi,
    I tried to put the VI's to create a TCP/IP Connection, read/write Data to it and close it inside a LabVIEW DLL and use these functions with TestStand.
    The problem is to get access to the ConnectionID generated as TCP Network Refnum in LabVIEW.
    I don't know how to specify the prototype entry for this Refnum in LabVIEW and how to read it with TestStand.
    Another try to pass an ActiveXReference of SequenceContext and use the SetValIDispatch method to set a local variable (Type: ActiveXReference) to the returned ConnectionID of the TCPOpen.VI wasn't successful too.
    It seems to me that the connectionID isn't a normal ActiveXReference.
    Regards,
    Sunny

    Hi Sunny -
    You should treat this parameter as a pointer to an int when calling the DLL from TestStand (or any language like C or C++). Note that you can't do anything with the value outside of LabVIEW since it only has meaning inside of LabVIEW. You can only pass it around for use in other VIs you call from TestStand.
    Hope this helps....
    Kyle G.
    National Instruments
    Kyle Gupton
    LabVIEW R&D
    National Instruments

  • Can I use C# forms with TestStand

    I am looking to use a rtf file to store data collected during a TestStand sequence test.  I have used C# class libraries in the past with TestStand, but I can only alter the Rich Text while using a Rich TextBox format and that can only be used in a windows form.  Is it possible to work with a windows form and not a library with TestStand?

    Hey mcfrenzy36,
    I found something in the TestStand help that I think can point you in the write direction http://zone.ni.com/reference/en-XX/help/370052J-01/tsapiref/infotopics/font_objects/
    Hope this helps
    BeauH
    Applications Engineer
    National Instruments

  • How to use Unicode characters with TestStand?

    I'm trying to implement the use of Greek characters such as mu and omega for units. I enabled multi-byte support in the station options and attempted to paste some characters in. I was able to paste the mu character (μ) and import it from Excel with PropertyLoader. However, I have not had any luck with omega (Ω). I found the HTML codes for these characters on a web page (http://www.hclrss.demon.co.uk/unicode/) so I could use those codes for HTML reports, but that won't work for database logging, nor does it display the characters correctly for the operator interface. The operator interface is not a major problem, but the database must have the correct characters for customer reports. Anyone know how to do this? D
    oes database logging support Unicode for stored procedure calls to Oracle?

    Hello Mark -
    At this time TestStand has no unicode support. The multi-byte support that we do offer is based on the Windows architecture that handles Asian language fonts. It really isn't meant to provide a bridge for unicode values in TestStand. Certainly, your Operator Interface environment will have its own support level for unicode, i.e. at this time neither LabWindows/CVI version 6.0 nor LabVIEW 6.1 officially support unicode characters. This is why you will see that the units defined in the TestStand enumerators are all text-based values.
    I have run a quick test here, probably similar to what you were doing on your end, and I am uncertain if you will get the database behavior you want from TestStand. The database logging steps and API all use basic char sty
    le strings to communicate to the driver. Even though you are reading in a good value from Excel, TestStand is interpreting the character as the nearest ASCII equivalent, i.e. "Ω" will be stored and sent to the database as "O". If you have a stored proceedure in Oracle that is calling on some TestStand variable or property string as an input, then it is doubtful you will get correct transmission of the values to the database. If your stored proceedure could call into a spreadsheet directly, you would probably have better luck.
    Regards,
    Elaine R.
    National Instruments
    http://www.ni.com/ask

  • What is the best way to organize LabVIEW VIs to be used with TestStand?

    I'm using LabVIEW 8.6 with TestStand 4.1.1 and I'm trying to organize the VIs to later deploy them to a production PC. So, I organized them into a LV project and built a LLB with the "Source Distribution Tool". (Destination type: LLB)
    Some VIs in the LLB use the "Call Library Function" (user32.dll) to simulate keyboard events. But, when any of these VIs is called from TS, LabVIEW is suddenly terminated. When these same VIs are not in the LLB and are called from TS they do not have any problem.
    Is the LLB the best way to organize VIs to be used with TestStand? If so, What could I be doing wrong?
    I appreciate your help.
    H.P.
    Mfg. Test Engineer
    Certified LabVIEW Associate Developer
    Attachments:
    LabVIEW Problem.JPG ‏28 KB

    Hi Ray,
    I really appreciate your intention to help, but I believe I solved the problem already. However I still have some questions.
    The problem was that when I built the LLB the configuration of the "Call Library Function" changed. When the LLB is built it is also created a Support Directory named "data" that contains some dependencies including a new copy of the user32.dll. The "Library name or path" field in the "Call Library Function" changed to be linked to a new Dependency Path. ( ...\data\user32.dll.)
    What I did was select "Specify path on diagram" and create a path-constant ("C:\WINDOWS\system32\user32.dll"), so the "Call Library Function" will be always linked to the original user32.dll.
    I still don't know why the "Call Library Function doesn't work with the user32.dll copy in the New Dependency Path. And I'm not sure if the LLB is the best way to organize VIs to be used with TestStand.
    Do you know why?
    Thank you,
    H.P.
    Mfg. Test Engineer
    Certified LabVIEW Associate Developer

  • Using Switch Excequtive with NI TestStand

    Hello
    I am beginner in NI teststand & NI switch excequtive.
    I have NI SCXI-1001 Chassis with NI SCXI-1130 switching slots.
    I need a quick help on how to use switching in NI TestStand. What  I am going to do is: generating a signal by a RIGOL Function Generator and switch this signal to excite some piezoelectric sensors and reading the response signals by a Tektronix oscilloscope.
    I have read these documents:
    NI TestStand 4.0 Quick Start Guide
    Getting Started with TestStand
    GETTING STARTED GUIDE NI Switch Executive
    and so on
    But still, I can not switch the signals with my hardware.
    Is there any Tutorial to help me in doing my work?
    Is there any VI code,  NI TestStand Sequence or Example which can help me?
    Please help me asap
    Thanks in advance,
    Mohammad

    Hi Mohammad,
    The following are a few documents that outline various ways (including with the Switch Executive) to incorporate switches into your TestStand sequence:
    http://zone.ni.com/reference/en-XX/help/370404G-01/nise/teststand/
    http://www.ni.com/white-paper/10092/en/
    Let us know if those are helpful and keep us updated on your progress!
    Regards,
    David R
    Applications Engineer
    National Instruments

  • Using LabVIEW OOP Objects with TestStand 2010

    I need to use labview classes in Teststand 2010. I am not able to pass reference between Labview and Teststand.

    Or leave it in Labview and use an action engine.
    http://forums.ni.com/t5/LabVIEW/Community-Nugget-4-08-2007-Action-Engines/m-p/503801?view=by_date_as...
    That's what I have done.
    Regards
    Ray Farmer

  • CPP DLL's use pass-by-reference integration with teststand

    I have the detail in the attached Outlook format file.
    Attachments:
    CPP DLL Integration with Teststand.docx ‏120 KB

    If you don't know what a method is, you're going to have a number of problems down the road... A method is a function. It's a member of a class. It sounds like you may need to go through some .NET tutorials to understand the terminology.
    Arrays in .NET are objects and are always passed by reference. That said, you would need to provide the details on the method's signature (i.e., the function prototype). Is the array a System.Array object or a regular old "int[]"? Is the method actually returning an array, or is it operating on the array in place. What is the return datatype of the method?
    Message Edited by smercurio_fc on 08-15-2008 02:26 PM

  • How to use stored procedures in TestStand

    I am trying to run a stored procedure but always get the error:
    Error executing substep 'Post'.
    The following SQL command failed: 'EXEC dbo.sp_test...'
    Native error code -2147217887 0x80040e21
    Microsoft OLE DB Provider for SQL Server:
    Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.

    NI_jc,
    > I am trying to run a stored procedure but always get the error:
    >
    > Error executing substep 'Post'.
    > The following SQL command failed: 'EXEC dbo.sp_test...'
    > Native error code -2147217887 0x80040e21
    > Microsoft OLE DB Provider for SQL Server:
    > Multiple-step OLE DB operation generated errors. Check each OLE DB
    > status value, if available. No work was done.
    In my dealings with TestStand and SQL, such errors are ~usually~ related to
    either security permissions or the parameters passed to the stored
    procedure.
    Can you successfully run the stored procedure from SQL Query Analyzer using
    the same username and password (and other connection info) that you use in
    the DataLink used in TestStand?
    If so, I would then look at the parameters you are passin
    g to the stored
    procedure. Verify you are passing the correct number and correct data types
    for each parameter the stored proc expects.
    If that all checks out, double check that you are using the correct
    connection handle, etc.
    Good luck,
    Bob

  • How to use CVI 2009 with CVI 2012 installed

    I have TestStand 2012 / CVI 2012 installed. 
    I need to also test using teststand 4.2.1 / CVI 2009.
    I installed teststand 4.2.1 / CVI 2009 and can activate teststand 4.2.1 but I cannot access CVI 2009. 
    Is there any way to have CVI2009/2012 both available on the same computer? 
    Is there a way to compile CVI 2012 to work with TestStand 4.2.1?

    Hi HMRJ,
    You can have multiple versions of CVI installed on the same computer. Can you explain in detail what you mean when you say that you cannot access CVI 2009? Do you mean that you can't open it or can't activate it?
    I am not sure I understand what you mean by compiling CVI 2012 to work with TestStand 4.2.1. You should be able to create a DLL from CVI 2012 and call this code module from TestStand. Are you receiving any errors when you try to do this?
    Regards,
    Anjelica W.
    National Instruments
    Applications Engineer

  • What are the advantages of using LabVIEW projects in TestStand, as apposed to just a path to a vi

    What are the advantages of using LabVIEW projects in TestStand, as apposed to just a path to a vi ?
    I am modifying an existing workspace for a new product, and it seems like more work to add the vi's into a LabVIEW project
    does it gain anything in the long run

    Hi Rusty,
    I wanted to quickly clarify on the integration between TestStand and LabVIEW Projects.
    As Jeff mentioned, some of the big benefits of using LabVIEW Projects is to organize code and to namespace them.
    For instance if you had a project called "Power Supply" that housed all your power supply code and had a VI in that called "Initialize", and another project called "Temperature Chamber" that also had a VI called "Initialize", both these VIs are namespaced by the project, so there is no longer confusion about which "Initialize" VI is being used.
    Now from a TestStand point of view, in prior version of TestStand, we lost some of this benefit because TestStand did not know about TestStand projects and called VIs simply as un-namespaced VIs. However, in TestStand 2010 (released last year, free eval available at ni.com/teststand), we added the ability to (optionally) call VIs within the context of their projects. This means that:
    VIs are now namespaced by their project, even when called from TestStand
    VIs can use project specific constructs like NI-DAQmx tasks and conditional compilation settings
    Note: When creating deployments, the VIs maintain their projects and namespacing, so this benefit holds true for deployments as well.
    Additionally, someone had mentioned looking into using lvlibs to namespace your VIs for deployment. Two comments:
    With TestStand 2010, this is no longer neccessary since the project itself namespaces the VIs
    You might also want to look into LabVIEW Packed Project Libraries, which combined several VIs into a single file. Think of it as a DLL specific to LabVIEW that is as easy to call as normal LabVIEW VIs. TestStand 2010 can call VIs that are exposed by PPLs. In addition, the deployment utility can automatically pack your VIs into PPLs for deployment.
    Hope this is helpful!
    Jervin Justin
    NI TestStand Product Manager

  • Who can help me using IVI powersupply in Teststand!

    Hi there,
    I'm newly in working with Teststand and IVI drivers and
    have a little simple question.
    I have a step to configure the powersupply.
    The logical name is "SamplePowerSupply", the operation
    is "configure". If I change to the "Validate IVI Configuration" form, uncheck the simulate checkbox
    and press the button "Init" I get the following errormessage:
    ....returned an error: -1073807343 ... Insufficient location information or the requested device or resource is not present in the system (-31619).
    But in MAX I see my powersupply and it seems to work correct.
    Thanks for any answer !!
    Mr.Pe

    Some IVI drivers are designed to work in simulation mode, that is, the virtual instrument can be defined in MAX but no physical instrument is necessary to use the "instrument". If you turn off the simulate checkbox on the validate dialog box, TestStand will create the instrument session without simulation and the driver will attempt to talk to a physical instrument. If no physical instrument definition is available or if the address defined for that virtual instrument is incorrect, the above error can occur.
    Scott Richardson (NI)
    Scott Richardson
    National Instruments

  • ActiveX Automation Reference getting corrupted when sharing with Teststand

    I am using ActiveX Automation to interact with a 3rd Party Software. I use LabVIEW Functional Global to store the activeX reference. I have some low-level APIs with the Automation Refnum In and Out and few high level APIs which use the reference from Functional Global. I am also using these APIs in Teststand. When I store the Automation Reference in the Teststand Local Variable and pass it to the low-level APIs, It was working fine. But when I pass the Reference from the Teststand Local Variable to the Functional Global and use it afterwards, the reference is getting corrupted and I am getting error.
    I have created a prototype of the situation using ActiveX call to Skype from LabVIEW. The attached file has 3 Teststand sequences explaining the situation. 
    Debug1.seq : Passes the reference from TS Local to LV Functional Global  : Generates error
    Debug2.seq : Uses the reference from TS Local alone : No error
    Debug3.seq : Uses the reference from LV Functional Global alone : No error
    Can anyone suggest why is the reference loses its validity or any solutions?

    Hello, Nandini,
    I am using the WinXP and I am calling the DLL provided by Pirouette for their chemometrics software. I just solved the error -2147467262, but the new error comes out is :
    Error code: -2147467259 Exception occured in IxAsObjs.CoSIMCAPredict.1, Language Server QueryInterface failed: No such interface supported.
    Here is a few word for the problem from priouette:
    " just a few more words that might help you understand the nature of the problem. your LabView client talks to AlgSuite.dll using IDispatch interfaces AlgSuite.dll communicates with the language server on an IUnknown interface.
    Your client knows nothing about the internal workings of AlgSuite.AlgSuite communicating with objects that do not have IDispatch interfaces should be irrelevant to your client."
    Since the VB demo works fine in my machine, so they though it is percular to labview. Any comments? I appreciate it.
    LvvL

  • IVI compliance package 2.2 with teststand 2.0

    Hy,
    I work with Teststand 2.0 and the IVI compliance package 2.2 and I do Fall time and Rise time measures on CAN low speed protocol with a remote scope Lecroy. If I do a data acquisition of one CAN frame (which contain several rise and fall front) and after, for example, I do a rise time measure on my previous data acquisition; I would like to know if the result of this rise time measure is the mean of all differents rise front or just the rise time measure of the rise front triggered.
    Thank you for you help,
    Xav

    Hi Xav,
    Alan from LeCroy Tech Support here...
    Which particular model are you using?  Most LeCroy scopes can accumulate measurements, both in terms of multiple measurements per sweep and over many sweeps. You can read back the overall mean value of everything accumulated since the last time "Clear Sweeps" was executed, or you can read back the last measured value. You can also read back the min, max and standard deviation of all measurements. The attached image shows a LeCroy WP7300A that is running our CAN analysis software... (Older scopes operate in a slightly different manner... )
    Let me know if you have any questions.
    Best Regards,
    Alan
    Alan Blankman, Technical Product Marketing Manager and LabVIEW Developer
    LeCroy Corporation
    800-553-2769 x 4412
    http://www.lecroy.com
    [email protected]
    Attachments:
    screenshot2.jpg ‏210 KB

  • Adapting LabView to work with TestStand

    I am currently trying to get TestStand 4.2 to work with VIs created in LabView 9.0.1.  I looked in the LabView adapter and the development system that I am using is chosen.  I am currently going through the booklet for using LabView with TestStand and it states that I must TestStand default value, but I can not find where this value exists. 
    Solved!
    Go to Solution.

    The folder of interest is below:
    C:\Documents and Settings\All Users\Documents\National Instruments\TestStand 4.2.1\AdapterSupport\LabVIEW
    I attached a picture of my folder contents.
    I believe you need to copy 'TestStand - Default Values 86.llb' to 'TestStand - Default Values 90.llb'.  Be sure after copying to make the LLB NOT read only before you mass compile.  It may not be 86 or whatever version is installed by default.
    I don't know where these VIs come into play but I have had to perform the copying when I was using Clusters in connector panes when I was calling LabVIEW VIs.  There are probably other reasons.
    Good luck,
    PH
    Attachments:
    AdapterSupport.PNG ‏15 KB

Maybe you are looking for