Open vi reference conversion from Labview 6 to Labview 2014

Is there a way that someone can help me convert this VI written in Labview 6.1 so that I can work en EXE in Labview 2014.
I succed to open this vi from 6.1 to 2014 but it does not run. The open vi reference those not work in exe program. Someone know how I can replace that function...
Thanks!
Solved!
Go to Solution.
Attachments:
to convert 2104.zip ‏17 KB

Error 7 is File Not Found. So your dynamically called VI is not in your executable.
In the build spec for the executable in your project, there is a section for "Source Files". On of the options for the VIs is "Always Include".
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

Similar Messages

HELP: CONVERSION FROM ASCII TO LABVIEW

I am degitiging 4 chanels biomedical data by POWERLAB. I can save that
file into ASCII format or POWERLAB format. Recently I am using a
software to analyzed those data that need a file like labview format or
HP Vee FORMAT. I DO NOT KNOW THE TYPE OF THOSE FILE. How do I convert
that TEXT file into LABVIEW FILE? If any body is interested to help me,
I can send sample data file.
Thanks in advance.
Shamsuzzaman
Mayo Clinic
Rochester, MN
Sent via Deja.com http://www.deja.com/
Before you buy.

[email protected] wrote:
>
> I am degitiging 4 chanels biomedical data by POWERLAB. I can save that
> file into ASCII format or POWERLAB format. Recently I am using a
> software to analyzed those data that need a file like labview format or
> HP Vee FORMAT. I DO NOT KNOW THE TYPE OF THOSE FILE. How do I convert
> that TEXT file into LABVIEW FILE? If any body is interested to help me,
> I can send sample data file.
>
> Thanks in advance.
>
> Shamsuzzaman
> Mayo Clinic
> Rochester, MN
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.
Shamsuzzaman,
There is no standard LabVIEW format for your file. LabVIEW can read any
kind of file of known structure. Please explain more about your problem.
Basically you can read your text file into LabVIEW direct
ly. Most likely
POWERLAB stores data into tab-delimited format and you can read it
without any problems and hope there is no special format in it.
Send to me your file.
Sergey Krasnishov,
Automated Control Systems
National Instruments Alliance Member
Moscow, Russia
[email protected]

Widening Reference Conversion

5.1.4 Widening Reference Conversions
From any array type to type Cloneable.
From any array type to type java.io.Serializable
Why does the following code fail when trying to convert array as mentioned above?
     String[] arr1 = new String[] { "hello", "world" };
     SomeClass myCloneable = (SomeClass) (arr1);
class SomeClass implements Serializable, Cloneable {
Cannot cast from String[] to SomeClassMessage was edited by:
jp_in_chains

You can think of the inheritance tree like this:
          Serializable
Class       String[]When casting, you can only go up the tree, never down
it. Since Serializable is above String[], you could
cast String[] to Serializable, like this:
Serializable srsly =
(Serializable)someStringArray;
You can go both up and down, but going up one branch and then down the other will give a ClassCastException at runtime

LabVIEW 8.6.1 Project causes slow Open VI Reference

I have an odd problem with "Open VI Reference.vi".
Case 1.
Open LabVIEW project containing "Main.vi"
Open "Main.vi"
Run "Main.vi"
Execution of "Open VI Reference.vi" take about 2,000ms
Case 2.
Open "Main.vi" - No LabVIEW project open
Run "Main.vi"
Execution of "Open VI Reference.vi" take about 100ms
I converted the project to 8.5 and the problem goes away. I don't have any machines with 8.6.0 to test if this is an issue with 8.6.1 only.
Has anybody else seen something like this?
Solved!
Go to Solution.

Good catch on the type def. It turns out that this is also key to the problem. I cleaned up my example VIs, removed the Type Defs and OpenG VIs. When I ran the cleaned up VIs the problem went away. So, I added a simple type def back to my called VI and the problem was back.
You misunderstand the reason for including gmath into the project. This has nothing to do with the time to load the project from disk. The problem is slow execution of "Open VI Reference.vi" when opening VIs that contain TypeDefs that are in large projects. By including gmath I was able to create a large project without attaching extra VIs.
Open Reference Test - No Project: 11 ms
Open Reference Test - small Project: 105 ms
Open Reference Test - large Project: 753 ms
Code in Zip file is LV2009
Message Edited by Gleichman on 08-21-2009 06:36 PM
Attachments:
Open Ref Test - II.zip ‏62 KB

Open VI Reference to a LabVIEW executable.

Hello,
I haven't done this for a while and it's not working like expected. I'm trying to "Open VI Reference" from executable A.exe to B.exe. I'm trying to get a control value from B.exe in A.exe. Can someone send me an example?
Right now I'm at this stage: I have A.exe running as a LabVIEW executable. I'm trying to "Open VI Reference" to A.exe from LabVIEW development without success. Not sure what I'm doing wrong.
Don't hesitate to ask more info if you need some.
LabVIEW 2012, Windows 8.1.
Thanks,
Michel
Solved!
Go to Solution.

Bob_Schor wrote:
Once you have an Executable, does it matter that the underlying Development system is LabVIEW, rather than (say) Visual Studio, or Matlab? I suppose you could write an application that "knows" to, for example, listen to a TCP/IP port and interpret/execute commands, but that doesn't sound like the question being asked.
BS
LabVIEW-built executables still run as VI's in the RTE, though. Their identities have not been abstracted away into one single object or anything, and they still have name-based VI server access.
You can configure a build specification to include almost nothing, and require the VI files to be present in expected locations (i.e build specification's data or support directories). By default, all items in an executable application build specification are set to be put in the same location as their caller, which results in most things going into the .exe file, internally referenced in a directory-esque form like crossrulz mentioned, "MyExecutable.exe\MySubVI.vi".

Open file in excel from labview

I need a way to open an existing Excel file, that may or may not be open already. I am using the attached "Open Specific WorkBook.vi" from the examples. My LabVIEW program must be able to either open a specifc Excel workbook and worksheet even if it is already open. Is this even possible, or would it be better to close it (if open), the open it again?
Attachments:
Open Specific WorkBook.vi ‏37 KB

As you probably know, nothing "bad" happens when you open Excel if it's already open, it just doesn't come to the front of your LabVIIEW ap. To get it to the front, Minimize the Excel window then immediately Maximize it (or Normalize it) programmatically with a PN. I have tried many of the other methods (but not all of them) to no avail, this works for me. There may be a more elegant solution.
There are other known methods to bring an ap to the front, with callbacks etc, but they can be clunky, or require Userlib32, etc. Since this property node already exists in your ap, it's comes at little expense.
Of course, you may want to check that the ap was open before you do this, but even that is optional, at the expense of a little flashing on the screen.
Richard
Attachments:
windowState.gif ‏4 KB

Labview 8.2 close or crashes when opening up Test Exec. from labview 5.1

Why would Labview 8.2 close or crashes when opening up Test Exec. from 5.1? Labview 8.2 begins to load the Test Executive VI, then, stops and closes labview altogether. I remember getting it to load before but do not know what could be causing this? I am tasked with updating the old code from Labview 5.1 to Labview 8.2.1; actually Labview 8.5, since it is the latest.
Thanks, Mike

Dennis,
Thanks for the response. The odd thing is that I am able to open some of the subvi's. And I've opened the test executive before. Now, during the initial loading of the Test Executive, there are some drivers that are not executable by Labview 8.2.1 (i.e. ni-daq cards.... for MIO and DIO boards). Could that be it? I would expect the program to load but not run. I have gotten the program to load before, so I am confused by it not loading now. Thanks for the tip on Labview 8.5 as I was ultimately going to that version, too!
My ideal situation would be to load all drivers ( including Traditional Ni-daq and Ni-VXI 3.3.1, etc) and run this program using Labview 8.5 or 8.2.1 on an XP platform. This original program was created in Labview 5.1 and Windows NT. Any help and suggestions would be appreciated.
Thanks for your help,
Michael

How to open an excel file from labview?

I tried to use "open file" vi from File I/O -- Advanced file functions to open an excel file in LabVIEW. Why the excel file wouldn't open after I run the program?

In addition to ActiveX, you can also manipulate Excel data files using the Windows ADO interface - a technique that is more robust, faster and IMHO easier. Do a search on the forum as there have been several threads within the last week or so discussing this very thing.
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

Can a "object reference" type from TestStand be used for Labview VIs

I am creating a test sequence in Test Stand and I am looking to use a "object referrence" type stored in the globals of TestStand as an input to VIs that I will use later in TestStand. The object can be from .NET or ActiveX. I need to know if I can use a input that will support either type.

Hi Mcfrenzy36,
Object references can be used for LabVIEW. I have found an article that teaches how TestStand handles Activex object references. Here is the linkt o it:
http://zone.ni.com/devzone/cda/tut/p/id/2984
I hope that this helps.
Regards,
Perry S.
Applications Engineer
National Instruments

Open vi reference problems in labview 7 after building an application

I have a vi with an Open VI Reference vi in it.
This works fine. But when I build an application of it and run the vi it gives problems.
I get an Open VI Reference error. Why?

If you have strict typedefs for the dynamic loaded VIs you need to include the line "BldApp.RemovePolyVIsandTypedefs=False" into your LV ini file. See this discussion.
Waldemar
Waldemar
Using 7.1.1, 8.5.1, 8.6.1, 2009 on XP and RT
Don't forget to give Kudos to good answers and/or questions

Dynamically called VI becomes broken inside an executable. Error 1003 from "Open VI Reference".

Here's the problem. Dynamically called VI becomes broken inside an executable in debug executable mode Error 1003 is occuring from "Open VI Reference" Block. The computer has all of the necessary drivers, NI-VISA and NI-DAQmx. This executable is a new release of software that currently works on the PC in question. I can using NI-VISA Remote Server control the instruments from my PC using the executable. But when I put the executable on the PC I am getting this error. The only way I have been able to get this to work properly is to build the executable from the console I believe the project was created in, note that the project file has been moved to a network drive and it still works. All of the stations I have opened the project in show the VI that is being called is runnable. I've tried building the executable from the console I am deploying to and the same thing happens.
I am honestly at a loss for ideas why this is occuring. Is this something about the way LabView works internally that may be causing this problem?
I have trolled this forum for idea's and none have made sense to me.
Any input would be greatly appreciated.
-Nate

Two ideas:
Mass compile the project to ensure all linkages are ironed out
Include the dynamically launched VI's into the "Always Included" section of the build spec
Report back on if either of these actions solves your problem.
a.lia-user-name-link[href="/t5/user/viewprofilepage/user-id/88938"] {color: black;} a.lia-user-name-link[href="/t5/user/viewprofilepage/user-id/88938"]:after {content: '';} .jrd-sig {height: 80px; overflow: visible;} .jrd-sig-deploy {float:left; opacity:0.2;} .jrd-sig-img {float:right; opacity:0.2;} .jrd-sig-img:hover {opacity:0.8;} .jrd-sig-deploy:hover {opacity:0.8;}

How can I call a LabVIEW executable from within another LabVIEW executable?

I have a customer requirement for two LabVIEW executables. Based on their current setup, they need to run executable "A" or "B", both of which are under independent revision control. I have created a third "selection" executable that allows the operator to choose between one of the two, but I am receiving errors when I attempt to call a LabVIEW executable from within a LabVIEW executable using either the "System exec" VI or the "Run Application" VI. If I call a non-LabVIEW executable (such as Windows Explorer) everything works fine.

> I have a customer requirement for two LabVIEW executables. Based on
> their current setup, they need to run executable "A" or "B", both of
> which are under independent revision control. I have created a third
> "selection" executable that allows the operator to choose between one
> of the two, but I am receiving errors when I attempt to call a LabVIEW
> executable from within a LabVIEW executable using either the "System
> exec" VI or the "Run Application" VI. If I call a non-LabVIEW
> executable (such as Windows Explorer) everything works fine.
As with the other poster, I suspect a path problem. You might try the
path out in a shell window, and if it works, copy the complete absolute
path to LV to see if that works. LV is basically passing the comma
nd to
the OS and doesn't even know what is in it, so you should be able to get
it to work.
The other poster commented on subpanels, which is a good suggestion, but
without going to LV7, an EXE can have open more than one VI. You can
use the VI Server and the Run method to fire up another top-level VI.
The decision is whether you want both to be in unique processes.
Greg McKaskle

Reference Library for Converting Between LabVIEW and XML Data (GXML)

Please provide feedback, comments and questions on the Reference Library for Converting Between LabVIEW and XML Data (GXML) in this thread.
The latest version of the NI GXML Library is availble in VIPM on the NI LabVIEW Tools Network repository.

Francesco, Thank you for the feedback. With this component it was my intention to make a more "terse" version of the LabVIEW Flatten to XML VI that was also supported on RT and that gave the user more flexbility regarding the structure of the parsing type definition. I think you are right that the XML parser is not compliant to section 2.11 of the XML spec. The parser does specifically looking for a #D#A and this appears to be an oversight on my part. Please confirm for me, the specifcation is saying that the XML parser should be able to recognize three possibilities as an "end of line" character: #D#A, #D, or #A. Am I reading this right?There are more efficient (and in some cases much more efficient) ways of sharing data between LabVIEW and LabVIEW: some examples are flattened binary strings and the datalog binary format. XML is slower than these optons but the upside is that it is human readable. Furthermore XML is inherently hierarchical which is convenient for complex data structures like clusters of arrays of clusters, etc. If you don't care about human readability then you are correct XML doesn't make as much sense.I will return to the GXML source code and try to fix this in the near future but I would hope that instead of creating yet another custom VI from scratch that you could reuse what I have provided for you. I included enough documentation in the source code so that users could make some modificiations themselves. The target application for this reference library was LabVIEW to LabVIEW communication. As such I documented the schema on the dev zone document from a LabVIEW perspective. It includes all the supported datatypes and all the supported data structures (cluters, arrays, multidimensional arrays, clusters of multidimensional arrays, etc.) I do see some value in making a more conventional XML spec but the time investment required didn't really line up with my intended use case. Were there any other downsides to GXML that I have missed? Best Regards, Jeff TippsSystems Engineer - Sound and VibrationMessage Edited by Jeff T. on 04-21-2010 10:09 AM

Opening a java jar file through a labview program

Hello,
I need to open a java jar file in labview........this jar file is a GUI with multiple frames and has buttons on each frame help navigate through between frames....i just require the program to open it and close it based on some signals so then i won't have to do it manually

LabVIEW doesn't have any control over what happens in a system exec, as you give the control to the system. You can, however, check the process list through .NET commands and kill the process (You should be able to stop it through "taskkill /F /im java.exe"). Not the prettiest solution, but should work.
/Y
LabVIEW 8.2 - 2014
"Only dead fish swim downstream" - "My life for Kudos!" - "Dumb people repeat old mistakes - smart ones create new ones."
G# - Free award winning reference based OOP for LV

Dll function calls from VB6 to Labview do not work.

HI,
We are transferring our production test systems from VB6 to Labview, and we are using "CAN-AC2-PCI" cards. When call functions of dll "canacpci.dll", UUT does not response at all, and Labview program does not report any error either. Attached are the user manual and my labview codes.
I guess the DeviceNe_init.vi works because if run it twice, second runing will report error. To correct the error, the card has to be closed first..
I close the card first, then initialize it. After then send the data. But I can not see any communication by DeviceNet Analyzer when sending data.
All function parameters are copied from existing VB6 program. The VB6 program works fine.
Please help me out,
Thanks,
Xiang Zhan
Attachments:
DeviceNe_init.vi ‏36 KB
DeviceNet_SendDataXXXX.vi ‏18 KB
CAN-ACx-PCI.pdf ‏139 KB

Hi Turck,
I'm not familar with this device, and it is difficult to say in this case. I would recommend calling into National Instruments support or contacting the vendor of the device for additional assistance in this case. As this isn't one of NI's Industrial Communications devices, you could also post on the LabVIEW forums for additional assistance, as there are a lot more people looking at that board than this one.
Thanks!
Matt S.
Industrial Communications Product Support Engineer
National Instruments

Open vi reference conversion from Labview 6 to Labview 2014

Similar Messages

Maybe you are looking for