Missing VIs

I have been upgrading our lab computers and installing our Labview
programs executables that run in the lab and wanted to refine the
programs and update them to LV7 since they were done in 6. I have
opened the files in 7 and I am having errors appear because of missing
vis. I programmed these 3 years and haven't used Labview since so
needless to say I am very rusty. Can someone tell me if these are LV
vis or were they created by me? I don't think I have all of the data
backed up from when I created these so I may just have to run these and
be happy with that.
The files in question are AI Sample Channels.vi, multiple time delay
match.vi and created data string.vi. Does anyone recognise these as LV
vis? Is there any way to reverse engineer an .exe LV file?
I will keep looking for my backed up work...........
Thanks for any help.
Dave

AI Sample Channels.vi is a DAQ VI from the
"Traditional DAQ" drivers. When you installed LV 7, you likely just
installed the new DAQmx drivers so you no longer have the AI Sample Channels.vi available. You can either install the Traditional DAQ drivers
into LV 7 or (recommended) update your application to use the DAQmx
drivers if your DAQ boards are supported. (most are, only very old ones
are not).
The other two are likely something you built for this application. A
search in my LV 6.1 palette doesn't show either one. So they are either
built by you or from a tool kit I don't have, but I have most of them.
You might be able to get to these two VI's in the .exe by remaning the
.exe to a .llb and opening it with the library manager (look in the
Tools menu), but most likely they won't have block diagrams and so they
won't be able to be upgraded to LV 7 and you won't be ab;e to see the
diagram to rebuild it.
Good Luck
Ed
Ed Dickens - Certified LabVIEW Architect - DISTek Integration, Inc. - NI Certified Alliance Partner
Using the Abort button to stop your VI is like using a tree to stop your car. It works, but there may be consequences.

Similar Messages

Tektronix 3xx Driver: Missing VIs

After installing and starting the NI-Device-Driver-VI for Tektronix 3xx Devices, I get error messages due to missing VIs like "TKTDS Read.vi" or "TKTDS Start-Stop Acqui.vi". No dokumentation available with the driver. Working with LabVIEW 6.02.
Any idea?
C. Wennmacher

I downloaded the dktds3xx.zip file from NI's instrument driver download site. I unzipped the file and it created two llb's in two different folders. They were tktds3xx.llb and tktdsxxx.llb. The files you are missing are in the tktdsxxx.llb. To solve your problem you have a couple options.
1) When the VI prompts you for the location of the missing VIs just navigate to the llb and select the appropriate VI.
2) Better Way - Move both llb's into your instr.lib folder which is probably in your c:\Program Files\National Instruments\Labview 6 directory. The necessary VIs will automatically be found since this directory is automatically included in the VI search path.
Matt Kisler
Applications Engineer
National Instruments
http://www.ni.com/ask

Getting strange error while trying to search for missing VIs

So when I load the top-level VI, many of the subVIs have changed location, but they are all below the top level VI, and I have <topvi>/* set as my first search option so it should find them no problem. But during loadin I keep getting this error message:
I press okay for how many ever times I need to, then there are mannny errors. All the errors pertain to it not being able to find a "valid type def".
What is the deal with that error message, and why can't it find valid type defs, they are all there, they have moved but they are within the configured search paths.
Thanks for any help

I think I figured out whats going on here. The VIs actually weren't in directories below the topvi, so that explains why it couldn't find them. And the error message I think is becasue the next search path on the list after <topvi> and <topvi>\* is <foundvi> and <foundvi>\* but this found vi paths only get populated when you show LabVIEW where to look for a missing VI. Since, there was no opportunity to show LabVIEW where a missing VI was, the found vi paths were nonexistent. I believe that this is what caused the errror message. There should be some error checking implemented here within labview if no found vi paths exist.... Maybe this is already in future versions, still useing 8.5...

Loaded runtime but missing visa drivers?

I created an executeable on one pc and loaded it onto another with just the runtime engine installed. Now the serial visa's will not work so I am assuming I am missing some visa drivers. What would the best way to get these loaded, if in fact that is the issue? The PC is no longer in my possession so I would have to do this by sending files and have the operator manually load them.
I have another PC at the location that does have the drivers. Is there anyway to copy and paste the required folders or do I need to use an installer?
Thanks in advance.
LV 8.2.1
Solved!
Go to Solution.

CTBK,
You need to install the NI-VISA Runtime Engine on the target machine. Make sure to install the same version as the NI-VISA installed on your development machine.
P.S. Best way to handle this is to create an installer that installs the .exe, LV Runtime Engine, NI-VISA Runtime Engine and any other supporting software.
Message Edited by centerbolt on 03-03-2009 10:00 AM

Missing Visa driver?

The VISA runtime was not installed on my deployment. I have found the RT images directory on my development computer. How can I add it to the deployments or do I need to rebuild?
Thanks,
jvh

Just to clarify, are you attempting to build a VI using VISA into an executable and distribute it with an installer from the Application Builder? If so, have you added the NI-VISA Runtime as an additional installer?
Thanks!
- Greg J

TestStand Deplyment Error- Error: Unable to locate all subVIs from saved VIs because a subVI is missing

Hi,
I am a Systems and Software Engineer based in Vancouver. I developed an automated test system using LabVIEW 2013 and TestStand 2013 with custom operator interface.
I encountered 'missing VIs' problem which is kind of weird because I passed analyzing the sequence for both TestStand Sequence Editor and TestStand Deployment Utility >> Distrubuted Files Tab.
But when I tried building the installer and reaching the point 'Calling distribution VIs, it always throw an error saying 'An error occurred while trying to read the depencies of the VIs, possible because the VIs are not saved in the current version of LabVIEW. Do you want to save any modified now?'. I tried both cases (i.e. Yes and No) for this option but it did not solve the issue.
This is part of the original error message displayed in TestStand Deployment Utility:
While Processing VIs...
Error: Unable to locate all subVIs from saved VIs because a subVI is missing or the VI is not saved in the current version of LabVIEW.
The call chain to missing VIs:
1 - ATE_AccelerometerTest.vi
2 - CreateAndMergeErrors.vi (missing)
3 - LogControl_CheckForErrorSendUpdates.vi (missing) "
All missing VIs are coming from userlib.
Actions Done:
- Analyzed sequence file using TestStand Sequence Editor and TestStand Deployment Utility
- Verified 'Search Directories' include all necessary files/dependencies.
- Mass compile the directory of the missing VIs
- Added all needed files and folders in the workspace file.
The result is still the same based from the actions done.
The last debugging I did earlier is that I tried locating the sequence and steps of missing VIs as mentioned above (e.g. ATE_AccelerometerTest.vi)
and I found out that the step seems to be an empty action step. Would this be possible even if it already passed the analysis?
Other considerations include:
I am using LabVIEW 2013 sp1 and TestStand 2013. We tried building from three (3) computers and we only succeeded once to a freshly-installed comptuer.
Hope to hear from you soon.
With Best Regards,
Michael Panganiban
Systems and Software Engineer
www.synovus.ca
[email protected]

Hi All,
We were able to resolve the issue. First to note is that the release notes in TestStand 2013 is outdated and we confirmed from NI Engineer in Austin that TestStand 2013 works fine with LabVIEW 2013 SP1.
Secondly, we played around TestStand Deployment option that resolved the issue. Attached are the images.
We just enabled the 'Remove Unused VI Components'. It could be one of the libraries (lvlib) we included in the build but we haven't figured it out yet because we verified that all VIs are working. It could be also something else that I think very difficult to find based from the information. However, if anybody experienced the same issue, this could be helpful.
Again, we revert back in using TestStand 2013 and LabVIEW 2013 SP1.
I appreciate any comments and feedbacks. Otherwise, you can close this support request.
Thank you.
With Best Regards,
Michael Panganiban
Systems and Software Engineer

Missing Sub VI error when running Application.exe in development PC

Hi,
I have created an application(exe) on my computer, which is also where I have also designed the different blocks of code for this application.
All the blocks of code work just fine when made to run through Labview 2013 development software. After adding all the VI files associated with the project in the project explorer of a new project and configuring the build specifications, I was able to create the executable. But, when I try running this executable/application(.exe) file, I get the missing subVI message. I found that some of these missing sub VIs are the Instrument driver VIs which work absolutely fine when run through the LabVIEW development sofware.
How can I resolve this issue?
Attachment "Error Screenshot" shows the Missing sub VI message.
Attachment "Project & Error Screenshot" shows the Missing sub VI message along with the list of dependencies in the project, which shows the error being displayed eventhough the sub VI is present in the dependency list.
Any comments in this regard are highly appreciated.
Regards,
Vivek
Attachments:
Error Screenshot.jpg ‏257 KB
Project & Error Screenshot.jpg ‏360 KB

vivek.madhavan.13 wrote:
Thanks for your comment Jeff,
But what about the 'subBuildXYGraph.vi', 'Waveform Array To Dynamic.vi' and other such VI's in the attached error message that are not a part of the Rohde and Schwarz drivers but are included in the vi.lib folder? Ideally, labview must be able to find/trace atleast these VIs while performing the build procedure, right?
Vivek
If they are (Non dynamically called)-dependancies of always included dynamic calls, Yes, the build will include them.
I hate to say it but, Start with the rs dynamic vis and keep adding if that meerely helps reduce the list of the missing vis.
Jeff

Quanser DC Motor Control Trainer Missing Some VI's

Hi, my name is Ansel. I am working on a project to set up an NI ELVIS with the Quanser DC Motor Control Trainer board and create a few very simple experiments demonstrating basic mechatronic functions.
I've been unable to utilize the VI's that came with the Quanser DC Motor Control Trainer board. The disc that was included must have been faulty because not a single file (not even simple html files) would open. I contacted Quanser about this and was directed to a website (http://www.meqtronics.com/public/requests/QCI_TEMP/QNETCDv1.20forLabVIEW8_5/) from which I was able to download the content of the disc. The files I downloaded seem not to be broken, however when I attempt to run one of the VI's, such as "04-QNET_DCMCT_Speed_Control," all but four of the sub-VI's necessary are found. The four missing VI's are "Intergrator.VI," "Integrator (DBL).VI," "Transfer Function.VI," "and "Transfer Function (DBL).VI." I have all the necessary components installed, as far as I know, and a search of my computer's hard drive returns no results for any of these VI's. I am running the full version of LabVIEW 8.5.
I would appreciate advice from anyone concerning this issue, but I'd also like to know if the Quanser Trainer VI's are the best way to learn how to create my own very simple VI's. All of the documentation I have found on the internet has referenced the trainer VI's that were supplied, so without them I haven't made much progress. I am only interested in a very simple open-loop system for controlling motor velocity as well as a slightly more complex closed-loop system. Is it worthwhile to get the Quanser Trainer VI's working or could I build these experiments from scratch?
Thank you for your time.
Ansel
Message Edited by Ansel on 04-29-2008 04:50 PM

Ansel,
Just to clarify, the version of the NI-ELVIS software that you may have is not the reason for the missing VIs in the Quanser program you downloaded. The VIs in question are included as part of the LabVIEW PID Toolkit, which I'm assuming is not installed on your machine. However, these particular VIs (Integrator, Transfer Function, etc) are fairly out of date, and they are only included in the PID Toolkit to support legacy code. I'm not sure if you have access to the PID Toolkit (it is also included as part of the LabVIEW Real-Time Module), but I would not suggest purchasing it just to get this Quanser code working.
If you are going to be focusing on simple open-loop control of the Quanser DC Motor, you could start by looking at some of the basic DAQmx examples. Driving the motor at a certain velocity would just require supplying a constant voltage through a DAQ output. If you want to do more advanced closed-loop control, the LabVIEW Control Design & Simulation Module might be worth taking a look at. Take a look at the 3-hour Control Design & Simulation course here. It is written specifically with the Quanser DC Motor board in mind.
Chris M.

Missing Class VI

My class says a class member VI is missing. The error list says find the missing VIs on disk. There are large number of VIs in this class so I have no idea which one is missing. How do I find out? All that are visible have a valid path.
Thanks,
jvh
Message Edited by jvh75021 on 04-14-2010 03:30 PM

Hi JHV,
The error message should tell you which VI(s) are missing. Do you have a screenshot of the error message you could post so I can take a look at it?
Thanks!
Eli S.
National Instruments
Applications Engineer

Original files are missing after re-installation (Test-sequence context.ctl)

Hello,
after upgrading from LV2010 to LV2013 my VIa are missing these files for eample
Labview Test-Sequence Context.ctl
TestStand GetPropertyValue (String)
I also reinstalled Teststand.
How can i get the files back? I fdont know if they were a part of Labview or Teststand-installation.
Thanks for help
TM
Solved!
Go to Solution.

Hey TM,
It soundls like the missing VIs are part of TestStand.
"TestStand GetPropertyValue (String)" is something TestStand provides, "Labview Test-Sequence Context.ctl" is also a TestStand component if I remember correctly.
It is important that LabVIEW is installed first. After, you can run the installer of TestStand. It is important that support for LabVIEW is selected in the installer.
Regards, Stephan

Executable works even if I didn't include all the vis

Hi everybody,
I'm facing a weird behaviour building my executable from LabVIEW: I've just realised now I forgot to include some essential VIs in my executable (in the Build Specification properties - Source Files tab). Despite of that, launching the .exe (from my PC where LabVIEW developing environment is installed) I have no problem in getting it to work perfectly!
Possible explanation: in some way missing VIs get called from the executable????
Does someone have a better explanation?
Many Thanks.

Most often, you should always assume that LabVIEW is smart enough to do everything it possibly can automatically.
LabVIEW Champion . Do more with less code and in less time .

Quanser DC Motor Control Trainer missing VI's for labview 2009

Hi my name is phillip, a student developer working with labview 2009 and the Quanser DC Motor Control trainer with ELVIS II. I have failed to run the VI for speed control, it appears to be broken and says four sub-vi's are missing and they are "Intergrator.VI," "Integrator (DBL).VI," "Transfer Function.VI," "and "Transfer Function (DBL).VI.". I happen to have installed the control design and simulation toolkit but this has not solved the problem. Please help!!!!

Hi Phillk, I have the exact same problem with the missing VIs for the Quanser DC motor control with the NIELVIS also for Labview 2009.
Can you please tell me where I can find these VIs? Can you send them to me if it is possible?
I would really appreciate it,
I need the Transfer Function.vi, Transfer Function (DBL).vi and the integrators too.
Thank you,
Carlos M. Rodriguez
[email protected]

Missing SubVIs when generating exe

When I open my project file, Labview searches for a bunch of VIs and then opens. I have bee developing like this since I took over the code a couple of weeks ago. I am able to run the program with no problems. Now I want to generate an executable and/or installer with Labview 9 and it tells me that it is missing VIs. I have edited quite a few built in VIs and I am not sure what VIs the programmer before me has imported. All I know is that the program works and I have to install it on target machines. Why won't Labview 9 let me create an exe or installer? I never had problems with previous versions.
Please help.
Matt

Simpler Error Handler is in vi.lib\Utility\error.llb
Perhaps your .llb was corrupted in some way? Check that file path and see if the Simpler Error Handler.vi exists in that .llb.
Search and replace pattern.vi is under that same library as well.
The NI_report VI's are part of the report generation toolkit. Is that toolkit installed? Is it corrupted in some way?
I would suggest repairing your LabVIEW installation.
mattyk wrote:
I should mention that I edited quite a few of the report generation toolkit VIs that came with Labview so I could adjust the column width on a table for a printed report. I mention this because I see that it can't find some of those VIs and am wondering if there is a link. The errors occur on two separate machines. Hope this helps.
That is a big problem. You should never edit any of the VI's that LabVIEW provides. If you need to modify them, then you should make new copies of them with a different name. You probably either broke the libraries or somehow damaged the cross-linking between the subVI's.
Message Edited by Ravens Fan on 11-05-2009 11:34 AM

LV8 app doesn't find sub VIs on target machine

Hello
I had a running application, which I compiled and copied to a target PC.
Now I added some more features (subFile dlg, mergeErrors, Spline) and the built exe can't find the corresponding VIs when I copy the exe to the system it is supposed to run on.
The same VIs are used in a second app within the same project. No trouble - all VIs are found when I run that exe. I have checked all build params to be the same. When asked to locate the missing VIs, I point the RTE to the LV8/vi.lib/etc files. But it does not memorize the position - instead I have to run through the locating process again on new start.
What am I doing wrong - how can I teach LV to include the respective VIs in the app?
Thank you for your input.
Michael

Hi Michael,
Are the "new" VIs actually part of the hierarchy being compiled, or are they called dynamically? If they are called dynamically (or part of a VI that's called dynamically) they need to be explicitly included in list of "Source Files" for the compile. I only have 7.1 to look at now, it provides a "Add Dynamic VI" button - the concept is the same for 8.x.
Cheers!
"Inside every large program is a small program struggling to get out." (attributed to Tony Hoare)

2 missed broadband appointments

BT have missed 2 appointments to fix my broadband. They now say they will come in another 2 days. I work from home and a week without broadband has cost me a lot. I really need them to fix it today. Can anyone in BT reallocate an engineer to fix my broadband today? Does anyone know how I can speak to someone who manages the engineers in my local area? I can only speak with an outsourced call centre who can only book appointment slots and apparently have no means of escalation. Is this really a sensible way to look after your customers?
Solved!
Go to Solution.

My broadband was fixed today. It is interesting that the engineer told me that a Control Team based in the UK looks after communication between the outsourced call centre in India and the engineers. He said the Indian call centre can communicate with the Control Team and get updates on the whereabouts of engineers. This seems sensible but in my case the Indian call centre said that they had no way of communicating with the engineers (which it seems I was right not to believe).
The engineer was surprised that I had two missed visits with no communication. I suspect that the engineer bookings were never made because of a system or human error. I will never know.
Hopefully this may help someone else who has a similar problem.
Now onto getting my £10 compensation per missed visit ....

Missing VIs

Similar Messages

Maybe you are looking for