Clear report in report window of simple operator interface

Hello,
hello I want to clear the report-window of the simple operator interface at the beginning of each UUT test.
I want that there is nothing inside this window while testing a UUT. Only at the end of a test I want to show the actual report
How is this possible?
regards samuel

Report.Reset should replace the current report data with the data in the string you specify, which in your case should be blank.
Do you have a PreUUT Sequence in your Client Sequence File?
If not try adding the first step in the attached sequence below the Report.Reset step in your PreUUT sequence.  You may need to add the second step as well (below both new steps).  Not sure if the second step is required.  The first step tells the teststand engine that the report has changed, the second tells it to refresh all windows.
Regards
Steve
There are 10 types of people in the world that understand binary, those that do and those that don't.
Attachments:
UI Update.seq ‏18 KB

Similar Messages

  • Programatically Loading Several Sequences Using LV Simple Operator Interface

    I am playing around with the supplied LV(2009) Simple Operator Interface for running TestStand (4.2) and hoping that someone can point me in the right direction.  I know this may be too generic for a concise solution, but hopefully I can get some suggestions on the best approach for this. Here is a short description of what I am trying to accomplish. 
    I am testing 2 unique UUTs on a single test fixture that is controlled by a PCI-7831R DAQ.  Each UUT will have a unique serial number and report generated.  Therefore, I am using 2 unique sequence files created using TestStand.  Basically, I want to be able to read in a barcode on the test fixture and have the operator interface load the 2 unique sequence files based on information contained in the barcode.  The operator will then hit a button to start the sequence file executions.  I want the first sequence file to run and test the first UUT.  Once the first sequence file is finished, I want the second sequence file to load and run on the second UUT.
    I can use the simple operator interface to load both sequence files.  I then have to select the combo box to select which one I want to run.  This works fine, however, I am trying to automate this so that the operator doesn't have to open the files and continually use the combo box to select sequence files.
    Any ideas or suggestions would be greatly appreciated.

    I have figured out a solution (for my initial application at least) of programmatically loading the sequence files.  When the operator interface first starts, there is a prompt where the user will scan a barcode that is loaded on the front of the fixture.  For all of our product lines, we will have a unique format for the fixture barcode.  Included in this barcode is a product specific software ID number.  I create a folder with the same software ID number and store the sequence files there.  I then parse the barcode and open all *.seq files in that folder.  I have this working correctly now. 
    Once the sequence files are opened, the user must scan each UUT ID barcode before installing them on the fixture.  The intent is to have both UUTs installed on the fixture at the same time so they can be tested serially.  If, however, they do not scan one of the UUTs, it will not be tested.  Basically this is due to the fact that they may want to run only a single board.  Once all of the UUT barcode scanning has been completed, I have another button that will execute the sequence files using the 'Single Pass' execution entry point.  I agree that the 'Single Pass' and 'Test UUTs' points should be hidden from the user.  Once the execute test(s) button is pressed, it will check each UUT barcode to make sure that it is valid.  If both UUT's have valid barcodes, it will run the first UUT and then the second using the 2 sequence files that were previously loaded, otherwise, it will run only one or the other.  The UUT(s) will then be removed and the process starts over again from the UUT ID barcode scanning.  They will not have to scan the fixture barcode again since the correct sequence files have already been loaded.
    Currently I have the UUT/Sequence File associations hard-coded in the UI.  I will need to put my thinking cap on so that as we increase the product lines (several are already in the pipeline) we can use the same UI without any modifications.  Scalability is King!

  • Simple Operator Interface hungs up while executing a testsequence

    Hello,
    My operator interface hungs up sometimes while executing a testsequence.
    It hungs up every time after the PostUUT has passed
    The attached error description is available
    can anybody help me
    regards samuel
    Attachments:
    errors1.rtf ‏2566 KB

    Ray,
    I have created my own PreUUT.
    In this PreUUT I call the dll for the PopUp windows to enter serial numbers and to select specified UUTs etc...
    Yes I have tried to single step through the sequence but then the Problem doesn't occure. (I run it than in the Teststand developer environment) The problem only  occures when I use my modified Operator Interface on the second computer. (on my first computer it works without problems)
    My suspicion is that my modified simple operator interface makes the problem
    what can be the problem? what dlls does the simple operator interface use? Is it possible that on my second computer some standard teststand or Lab Windows CVI dlls are not up to date?
    regards samuel

  • LabVIEW Simple operator interface deployment

    Hi All,
    I try to deploy a TS 3.1 application with a LV 7.1 Simple OI. I successfully (no errors) built the OI executable and created an installer with default options. I also built the Deploy TestStand System and created an installer with default options, except I selected only User Interface->Simple->Labview (no development system). I installed them on the target machine without any problem. The problem appeared when I ran the OI; it reported "Error 97 occured at Unknown System Error in TestStand-Set TestStand Application Window.vi->Simple OI-Top-LevelVI.vi. Possible reasons: Labview: Null Refnum was passed in as input".
    I beleive this happened because the "Application Manager", "SequenceFileView Manager" and "ExecutionView Ma
    nager" ActiveX Controls, which were required by the OI, were not present on the target PC.
    Obviously, TestStand Deploy did not distribute them.
    Does anybody know how to distribute these ActiveX controls or have a successful experience of distributing the LabVIEW Interface?
    Thanks.

    PPascal,
    We've seen this error before, and it usually fixed by a simple reinstall. You could also possibly just run a repair on the TestStand engine within add/remove programs and this should also fix the problem. Please try this and post back if this does not fix the problem for some reason. Thanks and have a good one.
    Adam B.
    Applications Engineer
    National Instruments

  • Including Limits, Measurements in Simple Operator Interface UI

    Dear Experts,
    I am in the process of modifying OPerator Interface such at that it must also display Low Limit,High Limits,Measured Value, Units. I am sure that it is possible only through expressions. I want this Limit columns value to be updated during runtime i.e., it must display the same value as we use to enter using Edit limits for Numeric test, Measured value should be the value in Step.Result.Numeric or Step.Result.NumericArrya.
    I could just manage to create a parameters in each Sequence & Subsequence Parameters.Limits.Low, Parameters.Limits.High,,Parameters.Limits.Unit & just hard code the values in these. But for Parameters.Measurements i could get values in runtime using RunState.Sequence.Parameters.Measurement. I know this is not more efficient way. This might work only for Action, Numeric Limit.
    For reference i have attached Simple OI Top Level.vi(where i have made some modifications) all other supporting files you can find in TestExec.llb. I hope i have explained my problem. If anyone find any confusions in understanding please let me know.
    If someone tried this before please share your knowldege. Expecting your greatest support.
    regards,
    Bharat
    Attachments:
    Simple OI - Top-Level VI.vi ‏177 KB

    Hello Bharat,
    Adam is out of town right now. It looks like the error you are getting is occurring because you do not have the TestStand 3.0 UI controls installed for LabVIEW. You can check this by making sure that you have a TestStand subpalette in both your Control Palette and Function Palette. If you do not, you can go to "Start >> Settings >> Control Panel >> Add/Remove Program". Find the entry "National Instruments Software" and click "change". Find "TestStand 3.0" in the list of NI software installed on your computer. Click on "modify". This will launch the installer. Follow the steps and make sure to enable support for LabVIEW 7.0 (there is a step with a tree of features that you choose to install).
    I took the liberty of saving the latest VI that was posted to my computer. I opened it with LabVIEW 7.0. This was verified by going to the "About" LabVIEW Dialog box that displays the version. I was running on the TestStand 3.0 engine. Besides the fact that you can only have one engine active on a computer at a time, I added a message popup to my TestStand 3.0 Front End Callback so that it would display when an instance of the engine is created. I did save the VI again and am not attaching it to this post. It should certainly work with LabVIEW 7.0 and TestStand 3.0 if everything is installed correctly.
    Thank you for contacting National Instruments. Take care and good luck!
    Regards,
    Aaron B.
    National Instruments
    Attachments:
    Simple OI - Top-Level VI.vi ‏177 KB

  • Updating system time with simple operator interface

    Hello,
    I need to update system time on the simple OI but when I use "Get system time and date.vi". The indicator on the front panel doesn't get updated every second, there is delay of atleast 5 secs. I tried using parallel while Loop method as well but still the problem persist
    Any ideas guys?
    Regards
    Prav
    Solved!
    Go to Solution.

    See attached simple OI modified to display time and date. When I run It, the update on indicator is like this 16:21:04-->16:21:09 (delay of 5 secs).I tried in time out event as well but no sucesss.
    Attachments:
    example.vi ‏69 KB

  • Error Loading a VI of a sequence in operator interface (Error Code -18002)

    I am deploying a teststand sequence using LabVIEW adapter. After deploying, while running this sequence in operator interface in the deployment computer, I get an error saying that a particular step could not be loaded. This step calls a DIO initialization VI which basically uses DIO Port Config.vi from Traditional DAQ 7.4.4 version. Please see the attached image.
    Software Versions Used: Teststand 4.0.1f1, LabVIEW 8.5, Traditional DAQ 7.4.4, Simple OI shipped with Teststand, windows XP
    From couple of links from www.ni.com, I did following actions in my development computer:
    1. Compile All the VI in LV 8.5 using Mass Compile including Traditional DAQ LLBs, simple operator interface etc.
    2. Check if any VI or step is not broken.
    After getting the error, I tried opening the same sequence in sequence editor in deployment computer (I am also including sequence editor with the deployment utility), I checked DIO Initialization step. I see the warning in step indicating that the VI is either broken or one of its sub is not located. I tried using Reload VI Prototype, it asks for LVDAQ.dll which is also bundled in my deployment files. After specifying this dll, I can run this sequence without errors but after I exit from sequence editor, it does not save the changes and I get the same error in Operator interface as well in sequence editor after re launching. Also I dont want to reload VI prototype as I dont expect some to do this change after deploying the testsequence.
    Kindly help.
    Thanks in advance.
    Nirmal
    Attachments:
    Auto_Cal_18002 Error11.JPG ‏25 KB

    I found solution for this. While creating the workspace for my sequence and other files, I used to include all the files including the LabVIEW VIs. Doing this, DIO Config VI seemed getting confused while searching for LVDAQ.DLL in the deployment computer.
    I tried only including the test sequence and letting the teststand deployment utility select the VIs from the specified directory resolved this issue. I observed that in this case, all the sub vi and the support dlls gets placed in the support and data folder respectively. This resolved the issue.
    Regards,
    Nirmal

  • Sequence file path programmed in operator interface

    Hello,
    I do not want to load the sequence file with the button OPEN_FILE etc.. for example how it is done in th Simple Operator Interface. I want to programm the path and the sequence file name in the Operator Interface. How can I do this that the correct file will be loaded
    regards
    samuel

    I try to explain what you have to do without an example, because it is realy simple, and so we have no version dependency ;-)
    I used the "simple operator interface" installed with TestStand (..\National Instruments\TestStand 3.x\Operator\Interfaces\NI\Simple\LabVIEW\TestExec​.llb\Simple OI - Top-Level.vi). I added the method mentioned above in front of the Event-Structure (See attached picture)  and added a path-constant, to define which Sequence should be loaded automatically.
    Try this out. It works fine on my machine (LabVIEW 8.2.1, TestStand 3.5, but should be independent of Versions as long as you have TestStand 3 and LabVIEW 7 at least).
    Hope this helps!
    André
    Message Edited by Andre_Saller on 04-25-2007 11:34 AM
    Attachments:
    Autoload.jpg ‏167 KB

  • Windows 7 Client Operating Systems (Aggregate) reports not working

    Hello All,
    We are using Windows 7 Management pack in SCOM 2012.
    We tried running reports in Widnows 7 Client OS (Aggregate) MP.
    There is no data in the report. Do we need to enable any rules to collect data for these reports?
    We need Memory related reports in this MP.
    We have windows 7 agents and we can performance data in OPS console for those agents.
    Thanks!!

    Verify that you install windows 7 management pack from below link
    http://www.microsoft.com/en-us/download/details.aspx?id=15700
    You can also check below link to resolve your issue
    http://social.technet.microsoft.com/Forums/en-US/54efc509-cbb0-407c-b826-17694cd5f0bc/windows-7-client-operating-systems-aggregate-reports-not-showing-any-data?forum=operationsmanagerreporting
    Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"

  • Open "Navigate" enabled report in new window - OBI10g.

    Hello Experts,
    May be its novice user question, i have 2 reports, source and target reports. Both reports are connected using "Navigate" functionality.
    Issue is, i wan to open the target report in new window? is that possible?
    using GO URL: we have an option like target='_blank'. but in navigate.. what is the option?
    Thanks in advance....
    Regards,
    Kiran

    The Navigate feature can be modified to open targets in a new window by following the below steps:
    - Edit OracleBI\oc4j_bi\j2ee\home\applications\analytics\analytics\res\b_mozilla\viewhelper.js
    - Search for function NavigateInfo()
    - Find the line with code this.sWindowTarget = "_self";
    - Replace the line as this.sWindowTarget = "_blank";
    - Clear the browser cache and reload the page.
    The navigation targets will now open in a new window.

  • Error message when displaying a report in a windows form

    Hi,
    use Cr 2008.SP3 Fixpack 3.5,
    Visual Studio 2008 prof. editon version 9.0.30729.1 SP,
    :NET Framework 3.5 sp1
    vb.net 2008
    when displaying a report in a Windows form sometimes the following error message appears
    System.NullReferenceException: Object reference not set to an instance of an object
       bei CrystalDecisions.Windows.Forms.PageControl.OnMouseMove(MouseEventArgs e)
       bei System.Windows.Forms.Control.WmMouseMove(Message& m)
       bei System.Windows.Forms.Control.WndProc(Message& m)
       bei System.Windows.Forms.ScrollableControl.WndProc(Message& m)
       bei System.Windows.Forms.ContainerControl.WndProc(Message& m)
       bei System.Windows.Forms.UserControl.WndProc(Message& m)
       bei CrystalDecisions.Windows.Forms.PageControl.WndProc(Message& m)
       bei System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
       bei System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
       bei System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
    The rest of the error message is in german:
    ************** JIT-Debuggen **************
    Um das JIT-Debuggen (Just-In-Time) zu aktivieren, muss in der
    Konfigurationsdatei der Anwendung oder des Computers
    (machine.config) der jitDebugging-Wert im Abschnitt system.windows.forms festgelegt werden.
    Die Anwendung muss mit aktiviertem Debuggen kompiliert werden.
    Zum Beispiel:
    <configuration>
        <system.windows.forms jitDebugging="true" />
    </configuration>
    Wenn das JIT-Debuggen aktiviert ist, werden alle nicht behandelten
    Ausnahmen an den JIT-Debugger gesendet, der auf dem
    Computer registriert ist, und nicht in diesem Dialogfeld behandelt.
    Thank you
    Otto

    Can you define "sometimes" a bit more?
    Is it after a number of runs of a report?
    Is it on a particular report?
    Is it after you do certain operations on the report (paging, zooming, dill down, print, etc., etc.)?
    Can you duplicate the issue if you isolate the report to a new test app?
    Did you happen to notice if the issue existed prior to FP 3.5?
    Is this on your dev computer or a client computer?
    OS?
    Ludek
    Follow us on Twitter http://twitter.com/SAPCRNetSup
    Got Enhancement ideas? Try the [SAP Idea Place|https://ideas.sap.com/community/products_and_solutions/crystalreports]

  • Reports builder on Windows 7 (64bit)

    Hello,
    I hope someone can help me with this....... I have installed Oracle Forms an Reports (64) on Windows 7 (64bit) successfully, but when i try to start report builder it does not open and no error apeared. I try to run it in cmd and i get the following message : The Reports Builder is only supported on the Linux x86 and Windows x86 operating systems... So is it true that I can't run reports on 64bit Windows or am I doing somethin wrong? What can I do? Can I install Forms/Reports (x86) on my version of Windows and will it work?
    If someone has any idea please hepl me,
    thank you!!

    Today I installed FMW 11.1.1.3 and got the same error message when calling rwbuilder.bat. I had to remove the line "goto end" in the batch file to get Reports Builder running. I havn't tested the stability so far but at least I can run the builder. It is (as expected) the 32-bit software. If there are problems I would try to run it in compatibility mode.
    Regards Juergen

  • Report fetched by windows OS report "Performance by System"

    When we fetch the report from the reporting pane  in "Windows server operating server reporting" (Performance by System), sometimes the data shown in the column form comes in the yellow and red color (which shows warning and critical respectively).
    My question is the threshold for these performance rules are mentioned in those perfmon collection rule or the rules from which the alert gets generated.
    Appreciate your help.

    The threshold of these performance rules, click on the alert and display details then show threshold of this alerts.
    For more details, you can refer below link
    http://technet.microsoft.com/en-us/library/hh457556.aspx
    http://technet.microsoft.com/en-us/library/cc180267.aspx
    http://download.doubletake.com/_download/dt53/docs/RecoverNow/User%27s%20Guide/Content/SCOM.htm
    Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
    Mai Ali | My blog: Technical | Twitter:
    Mai Ali

  • Crystal Report Viewer and Windows 7 Enterprise

    Hi,
    We are using RDC methodology for launching the crystal reports in the web using ASP. 
    The web server operating server is Windows 2003, Crystal Reports XI Release 2 is installed in it. Activex Viewer is downloading fine in client machine having Windows XP OS (IE Version is 7) but for the same url ActiveXViewer.cab is not getting downloaded in Windows 7 Enterprise (IE Version is 8).  It throws the error u201CThe Crystal Report Viewer is unable to create its resource objects.u201D
    To download the cab file in Windows 7 machine it request for the following url
    1.     http://<web server name>/crystalreportviewers115/ActiveXControls/ActiveXViewer.cab
    2.     http://crl.verisign.com/pca3.crl
    3.     http://csc3-2004-crl.verisign.com/CSC3-2004.crl
    4.     http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cab
    URL 2,3,4 returns the http status as 502 (Bad gateway).  These url are not called from the Windows XP machine.
    The windows 7 client machine is not connected to the internet. I tried importing the crl files (by downloading from another machine).  But still we are getting the same error.
    How to over come this issue?
    Please Note :
    1. I am able to download the cab file when I tried to download only the cab file directly by specifying the cab url.
    2. If I am registering the ActiveXViewer.cab deliverables manually in the client machine report is launching fine, but we cannot do the same for the entire client machine having Windows 7 Enterprise Operating System.

    Hi Ludek Uher,
    Thank you very much for the information provided by you.  But still the same error (The Crystal Report Viewer is unable to create its resource objects) occurs after changing the IE8 Compatibility mode.
    Are there any other settings that can be tried for this issue?
    Thank You.

  • Reproducible error when loading many reports (Load report failed - Not enough memory for operation)

    Environment:
    Win 7 SP 1
    Visual Studio Pro 2012 Update 4
    Crystal Reports for Visual Studios Service Pack 10 (13.0.10.1385)
    Report created in Crystal Reports XI Release 2 (11.5.8.826)
    Targeting x86 .NET 4.0
    Scenario:
    We have a program that runs and creates a large number of reports before the process is ended. When running after many hours we'd get a Load report failed/Not enough memory of operation exception. I kept removing code and found i could reproduce just using the report.Load call. I simplified the report to a completely blank report to make sure it was nothing specific to a report I was loading. (Opened Crystal Reports XI Release 2, Save As, "Blank.rpt".). I then created, loaded, and disposed of this report in a loop. I was able to cause the same exception after 32,764 iterations on my machine. I also tried using .NET 3.5 same result. I added a counter to our main program and it also went through 32,764 report loads before the same exception was thrown. Main program uses 15 or so different reports with a variable number of subreports in each.
    Sample Code to illustrate the problem:
    I did this as a WinForms project since our main program is using winforms.
    References added:
    CrystalDecisions.CrystalReports.Engine
    CrystalDecisions.ReportSource
    CrystalDecisions.Shared
    CrystalDecisions.Windows.Forms
    using System;
    using System.Windows.Forms;
    using CrystalDecisions.CrystalReports.Engine;
    namespace CrystalTest
        public partial class Form1 : Form
            public Form1()
                InitializeComponent();
                int i = 0;
                try
                    while (true)
                        i++;
                        ReportDocument report = new ReportDocument();
                        report.Load("Blank.rpt");
                        report.Close();
                        report.Dispose();
                catch(Exception ex)
                    MessageBox.Show(i.ToString() + ex.Message);
    Exception:
    CrystalDecisions.Shared.CrystalReportsException: Load report failed. ---> System.Runtime.InteropServices.COMException (0x80041004):
    Not enough memory for operation.
       at CrystalDecisions.ReportAppServer.ClientDoc.ReportClientDocumentClass.Open(Object& DocumentPath, Int32 Options)
       at CrystalDecisions.ReportAppServer.ReportClientDocumentWrapper.Open(Object& DocumentPath, Int32 Options)
       at CrystalDecisions.ReportAppServer.ReportClientDocumentWrapper.EnsureDocumentIsOpened()
       --- End of inner exception stack trace ---
       at CrystalDecisions.ReportAppServer.ReportClientDocumentWrapper.EnsureDocumentIsOpened()
       at CrystalDecisions.CrystalReports.Engine.ReportDocument.Load(String filename, OpenReportMethod openMethod, Int16 parentJob)
       at CrystalDecisions.CrystalReports.Engine.ReportDocument.Load(String filename)
       at CrystalTest.Form1..ctor() in c:\Test Projects\CrystalTest\CrystalTest\Form1.cs:line 27

    int = Int32. No it's not the "counter" that's causing the problem. The max size of an int32 is far far larger than 32764.
    I am disposing and cleaning up the datasets in the main app. That is why I didn't include them in this test; they aren't relevant.
    I'm unsure why this test program is completely irrelevant. It throws the same exception, at the same count, as the main program. It does it in substantially less lines of code than our main program. I spent days running long tests to figure out exactly what I needed to make the problem appear so I could post a clean and precise post on these forums. I then created the test program to illustrate that.
    The "real" code as I said does stuff in sections and in a certain order.
    For each report I need to export based on rows in a table
    1. Creates a new Report Document
    2. Loads the report document with the report
    3. Creates a dataset of the data to display
    4. Calls SetDataSource
    5. Calls Report.ExportToDisk
    6. Disposes DataSets
    7. Closes/Disposes Reports
    To help isolate the problem I first took out the export to disk part (Step 5). The problem still occurred. I then took out everything related to our data. (Step 3, Step 4, Step 6). The problem still occurred. And yes I commented out this code in our main real program. This left me with:
    1. Creates a new Report Document
    2. Loads the report document with the report
    7. Closes/Disposes Reports
    At this point i had to prove it was not dependent on the report. This makes sure it's not a database connection, or pulling too much data into the report. The most efficient test for this is a blank report.
    So my order of operations becomes...
    1. Creates a new Report Document
    2. Loads the report document with a blank report
    7. Closes/Disposes Reports
    So you'll see this is exactly why I wrote this test the way that I did.
    I've had a run where it error on iteration 32761. My last runs have errored on 32764. I have had many runs over many weeks that all error with the same exception.
    There are no temp files left behind, With a test running you can see the temp files being added but they are immediately removed.

Maybe you are looking for