Open LabVIEW VI reference executable.

Similar Questions

• Cannot open labview 11 after installation

  I received the last mydaq at school. I have loaded all of the software and was able to use the mydaq, but does not open labview. I have an acer aspire v3-551-8664. There the A8 of AMD Quad core processor. I saw in another place that the AMD FX "bulldozer" has a problem with labview. Any ideas?

  So, I finally realized what I was missing that was the patch needed to go in two different folders. He has got to work! Thanks for your help and sorry for the confusion.

• Error opening of FPGA reference

  I use the 8.6 and all the latest versions of the software on a device cRIO. In my code RT I opens a reference to a FPGA file and when I do with this error to expire:

  error code:-63192
  in Kyle.vi CRIO-CRIO Kyle.vi host
  Activities FPGA:

  Open FPGA interface reference. in Kyle.vi CRIO-CRIO Kyle.vi host

  There seems to be no explanation of this error on the Web site of NOR, and I need help to find out why the error might be involved.

  OK, so I made a stupid mistake. The project I'm working on that uses 3 crios simultaineously. To simplify things, all cRIOs run the same screw on them and if necessary, they detect what crio they are on the fly.

  Well, because all crios use the same file I had only opened the structure of files on the crio first in the project. The error occurred because I do not have the FPGA files in parts of the second and third crios FPGA in the project. Either they were removed or never added when I created a new project (created a new project to resolve a previous error). Thus, when the reference the the bitfile was attempted to be opened on the second and third crios, there is no FPGA files in the build, so he would give this error.

  Quite embarrassing.

• error-61141 open FPGA VI reference

  Hello

  Plug-in a cRIO9074. I ran a scan EN Mode application, on the target that fontionnait. Then, in another project, I wanted to run a colorful mode FPGA application. The open FPGA VI reference then returns the error-61141 and indicates "Scan Interface is running". You must set the controller in FPGA Interface mode to unlock the FPGA". In the project window, I checked that the chassis was in mode FPGA. Moreover, when creating a new project RT, the discovery of the modules will fail with warning "FPGA is busy." The connection to the target is, however, possible, but takes several minutes. Information can be important: the first application in scan Mode established TCP communication with the host PC. Can this connection will hinder communication with the target?

  Thank you in advance pour your answer.

  Julien J.

  Hello

  I'm not sure what's going on. What I recommend is to completely reformat the controller and see if this can help you. I hope that you use the latest version of the NI-RIO driver.

• Just openning LabVIEW and causing 99% CPU usuage

  Hi people,

  I just opened LabVIEW 8.2.1 and later, he finishes its initialization, while on the start-up screen LabVIEW uses 99% of CPU.

  I tried to restart and repair the installation, but nothing helped. Someone has experienced this problem?

  Thanks in advance!

  One thing to try: start in safe mode. I think that LabVIEW should always run in safe mode, although no service will operate. I would be very interested to know if the CPU usage is still attached.

• Cannot open the secondary an executable after upgrade 2009

  I have a request that I had built in an executable in LV 8.6 open successfully several sub-panels using calls to the VI server. I use the App.Kind property to programmatically determine if the application runs in the system development or as an executable file. In both cases, I first use the Reference.vi Application open to get a reference to the instance of localhost, then I pass this reference to the Open Reference.vi VI, as well as the path of the VI. In the case of development system, I pass the absolute path to the VI to be opened in secondary school; in the executable file, I just pass the name of VI. Since each Secondary VI is included in the executable version (in the.) EXE file; always included), RTE has never had any problems finding files VI and by opening the sub-panels.

  However, after the LV2009, my executable update can't find the screw more. I checked they are all designated as "Still included" in the specification to build, and I rebuilt the executable several times, trying different possible paths (absolute and relative) to try to coax the RTE to find the necessary files. But everything I try it, still no luck. I'm still stuck with error 7 - file not found.

  Are there known issues with calls to the server LV2009 and VI in the executables? Does anyone have any ideas as to what could have changed that a running executable to screw would build between versions 8.6 and 2009? I would be very happy to help.

  Maybe this will help:

  7 error when launching my executable generated in LabVIEW 2009

  http://digital.NI.com/public.nsf/allkb/EEE8A5650DAC28558625762F0070A384

  Steve

• Suggestion: Allow users to attach a note to a tab open for future reference.

  I just wanted to make a quick suggestion: I work with about 25 tabs open, and sometimes need to add a quick note so that I can remember what I had to do with the info on the tab. It would be really handy if I was able to type a short note that was attached to the tab for future reference. Maybe a window that appears if I right click on the tab and select 'Add Note '. A pop appears up to where I can type a note and then disappears when I click "Save". I remember the note by right-clicking on the tab and selecting 'notes reveal. Maybe each tab which is a note could have a color bar in the upper part of the tab to indicate that a rating.
  Keep up the good work; Thank you!
  -Cary Snowden

  Maybe to open the Web Console (Firefox/tools > Web Developer) when this tab is open and add the comment here between the surrounding quotes: "This is a comment"

  • https://developer.Mozilla.org/Tools/Web_Console

  There could be several messages added, so you may need to scroll to the top if you do not see your comment.

• Open VI 476 reference error

  I was see this error, but I could not find any documentation on what it actually means. I get only error in my application intermittently so I don't have an easy way to resolve the issues to see what can be the cause of it. If someone could point me to documentation about this error, I would appreciate it.

  This error code is not yet defined. Are you sure that that's out of the open VI reference function? What are the values of the inputs to this function? Alternatively, it comes from some other VI which calls the function reference open VI?

• Version of LabVIEW for built executables?

  Is it possible to query a LabVIEW executable to determine the version of LabVIEW, it was coded in?  I need to tell my Department of production what Run-Time Engine to install to use some old EXEs of LabVIEW.

  Thank you!

  NIquist wrote:

  Is it possible to query a LabVIEW executable to determine the version of LabVIEW, it was coded in?  I need to tell my Department of production what Run-Time Engine to install to use some old EXEs of LabVIEW.

  You can just run the application on a computer that is not any LabVIEW software installed. You will get a dialog box that tells you what version you need.

• Open LabView VI to a LLB

  Hello

  Currently, I'm trying to connect my camera Andor Shamrock of newton and access the VI so that I can use in my LabVIEW program.
  The software readme directed me to the LLB directory, in which I found all VI applicable to the camera. However, when I try to open, a dialog box if poster direct me to find the files in the "shared library". The cancellation of this dialoge box allows the opening, however, VI block diagram see the? as well as whites where the icons of screws of the camera should be.

  Is there a way for me to access the screws in the LLB Manager list or I have to fix from a separate source?

  Thank you

  Justin

  Fortunately, after the conversation with the company, its seems to have been a fault of their own. After redownloading software, the VI became available. Thanks to everyone for their assistance; hope this is useful to others.

• Change LabVIEW code when executing

  Hello world! I'm quite new in LabVIEW and I have a question.

  If I change a code while it is running will there be problems? This code is a measure automation code, and I really don't want to screw up the measures.

  Thank you

  Edit 1: the code is in a shared hard disk. Assume that the code is running on a computer, and I change the code exactly the same from another computer, there will be problems?

  Diego

  diegocava wrote:

  I tried this experiment: a simple vi with a while loop and I threw it on my computer, I created on the shared drive. Then I used another computer and I opened the same vi (in this shared drive) and I have modified and saved the changes. After that I went to my computer and the code was still running without changes, as if I did nothing. Finally, I closed the vi and re-opened, find the changes made on the other computer.

  I think you answerd your own question in the present case.

  As I said the LabVIEW development system when running a VI. The VI is compiled at launch, so any changes made to the file VI will not affect the VI running in RAM.

  But what you do is 'dangerous', and you should not be remotely change the code that is running on another machine.

  Edit a copy, stop the running process and run your new code.

• LabVIEW 7.1 executable on win7 64-bit

  Hello world

  I am currently working on a project using LabView and a PIC 18F2550. I am not the initiator of the project, I simply to continue the work already done. I had a problem, when I connect my camera using the PHOTO on my new 64 bit PC, it seems that the .exe file do not recognize my device, but windows doesn't. The pilots are microchip, so I guess they must be good!

  I don't know where is the problem, plus it works on my old windows XP 32 bit perfectly. Maybe because it's labview 7.1? On a 64-bit operating system? If I upgrade to a newer version, it will be good? If you do not, thing, it's a problem of my program? The VID and PID seems good and it works on another computer...

  Thanks for your help!

  
  

• LabVIEW relative reference

  Hello

  My reference works in VI correctly, but when I buld exe, write the name of the exe on the way. Someone knows the solution?

  Thank you!

  Maybe this:

  http://digital.NI.com/public.nsf/allkb/FD7DE8BC8FFC256C862565F4006BE363

• Use LR5. Because of volume and the size of the photos, I use an external hard drive. When opening LR5 it references only the local hard disk. How can I change the refernce to read the external drive. Thank you

  Use LR5, due to volume and the size of the photos, I use an external hard drive. LR refers only the Local Drive C not outside. Where do I change this by LR read the external drive. Grateful for the help.

  Thank you

  LR is not a file Explorer. He knows only the disks that you imported photos of.

  If you have previously imported these photos, then later moved into the external hard drive, go to the library files and "update location" Panel on the files that you moved.

  If you have never imported these images on the external hard drive, perform an import by using the option 'Add' (not ' copy') to keep the images on the external hard drive during import.

• LabVIEW 8.6.1 project causes the slow open VI reference

  I have a strange problem with 'Open VI Reference.vi'.

  Case 1.

  • Open a project in LabVIEW that contains "Main.vi".
  • Open 'Main.vi '.
  • Run "Main.vi".
  • Execution of "Open VI Reference.vi" take about 2, 000ms

  Case 2.

  • Open "Main.vi" - open LabVIEW No. project
  • 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 have not all machines with 8.6.0 to test if there is a problem with 8.6.1 only.

  Has anyone else seen anything like this?