Problems in Operator Interface for LabVIEW

Hi Ray,
I am using LabVIEW 7.0 and TestStand 2.0 version. I am using the default operator interface for labVIEW provided in the TestStand and i am using custom step types in my sequence file.
This sequence calls a VI, which transmits strings that i specify from the serial port to the NI-7831 RIO Fpga Card for differnt baud rates. The same sequence is working fine when called from Sequence Editor but it is not working when it is called from Operator Interface for LAbVIEW. It justs either fails the test or skips them. Please tell me if there is any solution for it. I have attached the sequence file and the vi that i am calling from my sequence file.

Hi,
You forgot to attach your sequencefile and VI, but never mind.
I think the problem maybe that because you are using the default Operator Interface.
If it still the one in the NI folder, then you will have to re build the testexec.exe application using your LabVIEW 7.0 Application Builder. The default exe file has been built using LabVIEW 5.1.1
Before you start, copy the LV folder from OperatorInterfaces\NI\ to OperatorInterfaces\User.
Load the testexec.bld file in your Application Builder and rebuild testexec.exe.
Launch your new testexec.exe from the User\lV folder and retry your test sequencefile.
Hopefully that should cure your problem.
Regards
Ray Farmer
Regards
Ray Farmer

Similar Messages

Any 3D interfaces for Labview?

Is there any NI equivalent to Roboworks (Newtonium.com). This is software that can display a multi-joint 3D view of a robot, linked to Labview in real time.
While I found Roboworks appropriate for my needs, my company's policies don't agree with their sales process(online only). So, I am looking for an alternative.
I found ThreeDimSim, which supports COM programming, thus linkable to Labview. However, their sales site is not compatible to our company.
Any help is appreciated.

falkpl wrote:
Is there any plans to support openGL toolkits in LV7.0, I hav not made the switch to 7.1 from 7.0 since I have a major project nearing completion in 7.0 then I will switch. I had put some effort into developing a universal toolkit for openGL calls but got hung up on calling the drawing and events integration with windows. I could not get a valid device condext for a labview window. I wanted to render dirrectly to a labview window but this didnot seem to work. I was using OPENGL32.dll calls. I also would be interested to see a 3d toolkit similar to GLUT for labview.
-Paul
Basically, while the Picture Control in LabVIEW 7.0 seems to support the "draw OpenGL stream" opcode at least partly, the above mentioned Toolkit is made in such a way that it is not simply possible to resave it as a 7.0 version. So someone would probably have to recode the entire hierarchy in LabVIEW 7.0. Besides of the huge work this would mean, it is very likely that the OpenGL support in LabVIEW 7.0 was also not made public nor used outside of NI, because it was still experimental and had a number of bugs, problems, limitations, which might make above mentioned library more or less useless in LabVIEW 7.0 anyhow.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Problem with Outbound Interface for Party in Standard XI Content for SNC

Hi All,
I am configuring a standard XI Content for SNC, the ASN Processing (DIMP ERP Backend). The provided Integration scenario involves three swim lanes which corresponds to an ERP, SCM and an external system. The external system is as an application component that is designed for B2B communication, i.e. a service with party which is called Supplier.
The first action within the scenario is Create ASN in the Supplier swim lane and send a message to the action "Receive ASN and update inventory(in transit)" within the SCM system swim lane. I have created a sender party that corresponds to the Supplier swim lane and also a receiver party that corresponds to the SCM system. I used the Integration Scenario Configurator to assign services and also all the comm. channel. However, when i try to generate the logical routing objects and collaboration agreements, i get the error message that there was no outbound interface associated with the sender(the external system) defined for the first action. There is no option within the Integration Scenario Configurator on how to assign/define the outbound interface that I want to use for the sender.
I have no idea how to assign the outbound interface to the action for the Supplier swim lane in an Integration Scenario that is from an XI Content. Has anybody configured something similar or come across the same problem? Any info will be much appreciated.
Luqman

Hi,
This could be the problem of confilting namespace or combinations.
in receive action just check that right message interface is configured at Inbound side.
just check any place void ?
1)just check the name as case sensitive.
2)Just check is there interface belongs to right software component.
3)Just check mapping assigned to the right combination or not.
its better to cross check all the component are assigned to right place or not.
****if helpful then rewards points
Regards,
Sumit Gupta

ASIO interface for LabView

Hello NI Forums! Cheers
As everyone knows, everyone is looking for a solution to get along ASIO drivers into LabView. In another post about this same topic, Dr. Ben Sternberg, from University of Arizona, told us about an existent ASIO LabView VI that was developed in the Laboratory for Advanced Subsurface Imaging (Original post: http://forums.ni.com/t5/LabVIEW/Has-anyone-written-an-ASIO-sound-card-VI/td-p/405683), the GenMon.
I'm an acoustic engineering student and i'm on an undergraduate research about beamforming, and i need to use the ASIO driver to acquire data and then analyse.
But there's an issue, the ASIO driver no longer works with the recent versions of LabView (LabVIEW 2010 and newer), because the ASIO interface was built in LabView 6.x using the CIN (code interface node) technology. Now, we know that LabView no longer supports this function, and the function used to do the same thing is Call Library Function Node. That's why I'm creating another post: to discuss with you guys a solution for updating this ASIO interface. So we can create a collective solution.
Given that other people besides me is looking for this kind of software, we need you guys, please, help us.
I'm an beginner programmer and i really can't do this alone.
The ASIO interface can be downloaded here: https://drive.google.com/file/d/0Bz8qBRJgS7wvN1ZJc1dYbmV6SUU/view?usp=sharing
thx!

In addition to what natasftw already told you, you will want to have a pretty sound understanding about C programming even if you can get away without writing a wrapper DLL in C (but from what I remember about ASIO that chance is slim, the API was not designed with high level languages like LabVIEW or Visual Basic in mind but rather as a means for C programmers to interface to various high performance audio hardware).
The Call Library node allows you to call DLLs but it requires you to know what a C programmer would have to do when calling that function from a C program and sometimes even a little more about how a C compiler treats specific situations that the C programmer wouldn't really have to worry to much about.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Problems with mass compiling for LabVIEW 6.0.2

When mass compiling the LabVIEW folder after installing 6.0.2, I get a Log file telling me "Bad VI" for 8866 vi:s. Have looked specifically at two of them, and the broken arrows are fixed by pressing and clicking the broken arrow. Somehow I don't feel like doing this for 8866 vi:s.
What is wrong, and how do I fix it?
Attaching the Log.
//Martin
Attachments:
MassCompileLog ‏1263 KB

Yes, it definitely appears as though you need to reinstall NI-DAQ. You can receive this error when the VIs which are being mass compiled depend upon other VIs which are either not present or have been incorrectly updated. Make sure that you have installed NI-DAQ support for your new version of LabVIEW. This is separate from installed NI-DAQ by itself. You must install the LabVIEW support files also. You can get these off of NI's website.
Also, if you did a complete install of LabVIEW, you may have installed a newer version of NI-DAQ without realizing it. This could cause a problem if there are two versions of NI-DAQ on your computer. Make sure you only have one version.
J.R. Allen

Problem in Teststand Operator Interface

I am facing problems when i try to run my sequence file from TestStand Operator Interface for LabVIEW. It gives either all tests as failed or skipped but the same sequence file when i execute from TestStand Sequence Editor it gives me correct results. I am not able to figure out what is the problem?? Somebody worked with teststand operator interface please help me to solve the problem.
Regards
Subramania Bharathi.

Hi,
Which version of TestStand and LabVIEW are you using.
Are you using a Customised LabVIEW Operator Interface or are you using the default version?
If you can provide a example of your Test Sequence File to help identify your problem.
Regards
Ray Farmer
Regards
Ray Farmer

Can Not execute a TS Sequence File with VIs that are already being compile in my Custom TS Operator Interface

I have build a custom TS Operator Interface (Executable) with some custom VI(s)(GOOP VIs). I want to be able to call the same custom VI(s) from Teststand Sequences. When i try ti launch the sequence from my TS OI i got an error message, because LabVIEW Run Time find the same VI(s) from two different location : the OI and the sequence.
I would like to know, that is the best approach to resolve this problem.
For the moment i got two solutions :
(1) dynamically calling the VI(s) in the OI (executable)
(2)Changing the name of the VIs in the TS sequence.
I would like to know if it exist an another solution ?
thank you
derek

For the moment the VI�s that are shared between the sequencefile�s and the operator interface, are used as code module in the sequencefile�s (not as sub vi in the code module).
On the target system I will got my custom operator interface (which is build from the Testexec.llb + my goop VI�s). My goop VI�s are statically link to my operator interface.
(I will say that my executable are on the C drive : C:\Testexec.exe)
My sequencefile�s and the differents VI�s of each step is deploy with the TestStand deployment wizard. A library with all the vi�s call by the sequencefiles are group in SupportVIs.llb. (the sequencefiles and the VI�s library are on the C drive too)
For exemple I will say that I got a foo.vi (goop
method) which is build in the operator interface testexec.exe. The same foo.vi is call (as code module) by a step of one of my sequencefile�s.
When I try to launch the sequence with the operator interface, The LabVIEW Run Time inform me that he can�t load step "foo" of sequence �MainSequence� because he find 2 VI�s with the same name in 2 different location (C:\Testexec.exe\foo.vi) and (C:\SupportVIs.llb\foo.vi.
If you got a sample example, i will be glad to see it.
Thank you Ray for your help.
Derek

How can I get RTE information in operator interface (LV) from TS API?

Hi!
I have operator interface in Labview and use TS API to run tests.
I would like to eliminate RTE dialog and to show error messages directly in front panel control.
I have created callback for TS Application Manager BreakOnRTE event.
It works good and I can lock dialog apearance.
But if I try to get ErrorObject from event parameter (execution) is is empty (has no error information).
But this parameter is real execution which contains step with RTE.
When I allow the dialog appearance in this callback, it contains RTE information.
Where can I get error information from this callback or get it any another way?
Thanks in advance for any assistance.
Solved!
Go to Solution.

I have found the way to get RTE from callback BreakOnRunTimeError of ApplicationMgr.
This way is:
Execution->GetThread[0]->GetSequenceContext[0]->GetRuntimeErrorMessageEx().
It was not clear for me: all Error fields in step and Sequence are not filled yet on callback time.
Only the context method can return error message.
The question is closed.

Launch TS sequence with operator interface

create shortcut for launching a TS sequence with operator inteface.
Right now, with Windows98,
1. I doubleclick the test stand Labview Operator interface on the windows desktop.
2. Click on File menu
3. click /Select the sequence (at the bottom of File menu to launch the sequence in the Operator Interface.
How do I create a shortcut to do these three steps?
Double-click an icon on the desktop, launch the Operator interface and the sequence.

Hi,
I guess what you want to do is launch the OI and load a test sequence from the command line.
Unfortunately you cannot do this with the LabVIEW Operator Interface as labview apps does not except the command line parameters.
Regards
Ray Farmer
Regards
Ray Farmer

DCT for Labview fpga

Hi,
I have problems based on dct for labview fpga. I get the project example from this link https://decibel.ni.com/content/docs/DOC-8202. I run the project in labview and its run succesfully. After that, I try to use a different vhdl code for the CLIP (in labview) that I get from open cores (http://opencores.org/project,dct_idct). I rewrite the fpga.vi by inserting a new vhdl code in the CLIP. When I run the project, there are no errors. However, the compressed image is not display. I check the output values from the Read from FPGA block at the host.vi and it shows zero values at all time. I try to debug, but still don't get the solution. Anyone expert please help me. Thanks in advance.

Hey Troy,
Have a look at the attached front panel design that will be compatible in FPGA.
Hopefully it helps!!
Aashish M
Applications Engineer
National Instruments
http://www.ni.com/support/
Attachments:
FPGA_CALC.vi ‏22 KB

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!

Why I get an error when running a sequence using the LabVIEW operator interface ?

I have a simple TestStand sequence calling LabVIEW vis that is giving me an error when I run it with the .exe version of the LabVIEW operator interface and I set TestStand to run the vis using the 8.2.1 runtime engine instead of the development adapter. I made a change in the operator interface to open a vi programatically and get the value of a control, this vi is also used in the TestStand sequence I am trying to run. Could this be causing my problem ?
Thanks

Hello Verdulken,
I have a few additional questions:
Does your application function correctly when running the LabVIEW operator interface you have created as a VI in the LabVIEW development environment (i.e. does this problem only occur when the LabVIEW operator interface is run as an executable)?
What is the error that you are receiving?
Regarding the VI that you open programmatically, do you open it in a visible manner (i.e. use the Show front panel when called option from VI Properties)?If so, do you also close this VI after it finishes (i.e. use the Close if originally closed option from VI Properties)?
Does the error occur on the step that calls this very same VI again later in the sequence?
Does your application function correctly if you use the development adapter for all of your calls?
Thank you in advance for this information,
Matt G.
National Instruments
Applications Engineering

Why are my LabView Dialog Boxes no longer modal when using the Example LabVIEW Operator Interfaces?

Hello,
I have a step in my sequence that pops up a modal LabVIEW dialog box. My LabVIEW vi uses the TestStand - Start Modal Dialog.vi and TestStand - Stop Modal Dialog.vi as described in the example and it works as advertised when I'm using the TestStand Development environment however when I use the sample Operator Interfaces distributed with TestStand the Dialog boxes lose focus. I have the VI Properties->Window Appearance set to Dialog and have followed all of the instructions I could find for making a dialog modal. I've also reviewed all the documentation I could get my hands on including previous posts on this board and didn't see anything obvious.
Does anyone have any suggestions as to what I may be missing? Has anyone else experienced this problem and come up with the solution?
I am using LabVIEW 8.0 along with TestStand 3.5.
Thanks,
RG

Hi RG,
Running the example modal dialog in the teststand3.5 examples folder and using labVIEW8.0, I notice that when the Dialog is displayed its not active, but it is modal to the OI. Clicking on the Dialog panel makes it active. If you try to click on the OI panel behind, you can not. Is this what you are seeing?
I am using the Full labVIEW IO as supplied with TestStand and the example VI in the modal dialog folder is as supplied.
The LabVIEW Adapter is still configured to use the active labVIEW developement environment.
If I run the same example, only this time using LabVIEW7.1, the Dialog panel is active.
There is a patch to take it to labVIEW8.01, at this moment in time I am not sure what the update fixes.
There does seem to be a problem with TestStand3.5 (engine) and LabVIEW 8.0.
Regards
Ray Farmer
Regards
Ray Farmer

Adaptation of LIFA (LabVIEW Interface For Arduino) to other Arduino compatible boards

Hello evryone,
I am trying to use a ''Sakura board", which is an Arduino compatible board, having similar programming as Arduino. This board is manufactured by Renesas; more specifications on it can be found on the following link: http://sakuraboard.net/gr-sakura_en.html
What I would like to know, is if the firmware used for LIFA to interface Arduino with labview, or the ChipKit firmaware, can be used to this kind of Arduino compatible boards.
My aim, is to use the Sakura Board for acquiring signals from various pins(Be it digital or analog), and setting other pins (Digital) parralelly, using labVIEW, as this is done using LIFA, or LabVIEW interface for ChiKit!!
Thanks in advance for your support.

I haven't had any experience with the Sakura board, so can only go on the information on the website.
I've used the Arduino LabVIEW interface previously, and it basically uses serial communications between the PC and the Arduino. This serial interface is provided by the on-board USB-serial converter (an ATMega8u2 running custom firmware).
From what I can tell about the Sakura, it appears as a storage device when plugging into a PC, and doesn't seem to have a USB to serial converter. If this is the case, then the LIFA toolkit won't work. That said, my understanding of the Sakura board may be incorrect (for example I'm unsure what operation modes the slide switch changes between). If you can confirm it has a USB-serial port then LIFA may work. I guess the key thing is that the serial port is required.
You may be able to use a software serial port (http://arduino.cc/en/Reference/SoftwareSerial) on the Sakura to communicate with a PC, though that would require a PC with a serial port, or an external USB-serial converter. This approach would also require you to modify the LIFA arduino code (located in vi.lib\LabVIEW Interface for Arduino\Firmware\LIFA_Base) to reference the software serial port. It's probably a long shot that this will work, as the software serial library has been written for AVR chips, making use of their specific internal timers.

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

Problems in Operator Interface for LabVIEW

Similar Messages

Maybe you are looking for