Integrating an NI-USB 8451 driver and Labview Run-Time Files in an installation package of a .vi application

Hello,
I've built a .vi which uses the NI-USB 8451 device (please see http://sine.ni.com/nips/cds/view/p/lang/en/nid/202368), and I would like to create an installation package to be used on a costumer's PC, which has no Labview installed on or a driver for this device.
I would like to have this installation as a completely stand-alone setup, so that the user could take this file and run it, and have the driver to the 8451, the run-time files for the Labview application installed by themselves, and have the .exe file working on a completely "clean" PC.
How can I integrate it all in one package ?
Thanks,
Michael.

Nice hearing from you again, Ipshita
I do not call any dll's currently, but am using the driver of the USB device, NI-USB 845x, version 1.0.1
Now, I would very like to make the use of my application, by another user, with no Labview or this driver on his PC, as simple as possible.
I just thought that maybe I could create an .EXE file with some Labview created dll's, which this executable would use, and spare the need of the 845x Driver or Labview Run-Time library prior installation. I could be wrong.
What should I do ?
P.S.
Meanwhile, I've been playing with the Application Builder and tried to create an installation with the Driver and the Labview Run-Time.
It had started the compile, but stopped with the following pop-up window: "Locate the 'NI-845x Software 1.0.1' distribution. Labview needs to copy a component installed or updated by the distribution..."
(Attaching the pop-up window below)
What is it looking for and where can I find it ?
Thanks,
Michael.
Attachments:
Installation_pop-up.JPG ‏20 KB

Similar Messages

NI 5660 Driver DLL Errors when using Teststand 2010 and LabVIEW Run-Time Engine 2010

This problem seems similar to the post "Resource not found error in executable on development machine." but I didn't want to repost under that thread because I only happened upon it by chance and none of my searches brought me there... so I made a more descriptive Subject.
I am working on a system that uses a PXI Chassis with a NI 5600 Downconverter and a NI 5620 high speed digitizer, among other PXI Cards.
I inherited working code written in LabVIEW 2010, running with the LabVIEW Run-Time Engine 2010. The code was using a custom executive and my task was to rewrite the test using TestStand 2010. I reused the majority of the old code. The old code used NI-5660 to control the 5600 and 5620. When I run my sequence using the LV Development System and TestStand, it runs without any issues. When I change the adapter over to LabVIEW Run-Time Engine 2010, all of my NI5660 VIs become broken due to DLL issues. It warns that the nipxi5600u.dll was not initialized correctly. Many of the errors are associated with the NI Tuner and NI Scope. After this LabVIEW will crash randomly, and the seqeunce will not work in TestStand even when back with the LV Development Adapter. The only way to recover after this is to restart the computer - TestStand automatically reverts back to the development system, the VIs are no longer broken and the sequence works again.
I have all of my VIs associated with a project. After reading a little bit about DLLs and TestStand, I found all of the DLLs in the dependencies section of my project and added them to my TestStand workspace. I also used Dependency Walker to track down the problems with the nipxi5600u.dll, the 2 DLL files that it said were not found already existed in the same folder as the original DLL (C:\Windows\System32). I have also performed a Mass Compile to make sure everything was running in LV 2010. If I skip the steps involving the 5660, my entire sequence runs fine.
The previous code was running with the LabVIEW Run-Time Engine without any issues. Is there just a step I am missing? Has anyone seen anything like this before? I can send screenshots of errors to provide more detail if necessary.

I have tried some more things and still can't get it to work. I have added the VIs mentioned in the Notes On Creating Modulation Executables KB both to the TestStand workspace and the LabVIEW project holding all of my VIs. This did not change the results.
When I try to run my sequence, The first error I get is shown in Error 1445.bmp. This happens when I try to use the NI 5660 initialize.vi. If I click ignore, the next error I see is shown in Error -20551.bmp. When I try to open the VI to look at it, I get the 2 DLL errors shown in Error loading nipxi5600u.bmp and Error loading nidaq32.bmp. When I close TestStand, I get the error LabVIEW Fatal Error.bmp.
Attachments:
Error1445.JPG ‏164 KB
Error -20551.JPG ‏174 KB
Error loading nipxi5600u.JPG ‏9 KB

Error involving Report Generation Toolkit and Labview Run Time Engine

Developed an application using LabVIEW 6.1 and LabVIEW Report Generation Toolkit for Microsoft Office 1.0.1. From there, tried to build a shared application for use with the LabVIEW Run Time Engine. The Run Time version functions properly until "New Report.vi" is called and then an error is generated, code 7, calling out "Open VI Reference in New Report.vi" could not be found. When building the application, I did include the "NI Reports Support" in the advanced installer options. The machine used for original development and application build is running Windows XP Pro and Office XP. Any suggestions??

I am having the exact same problem but with LV 6.1 and M/S WORD 2000. It appears that the "New Report.vi" is trying to open "C:\APP.DIR\Word_Open.vi" and "C:\APP.Dir\Word_Open_Document.vi" by reference. The "OFFICE 2000.TXT" says that "_exclsub.llb and _wordsub.llb must be added as support files when building an application or a dynamic link library with the application builder." I added them as Support Files and I copied them to the "C:\TESTER\" where the TESTER.EXE is and I still get ERROR 7 in "NEW REPORT.VI" at VI OPEN REFERENCE.
Do I need to make a "C:\TESTER\DATA\" sub-dir and put the support files there?
I am building on MY COMPUTER on F: Drive on a network and transporting files to the real Tester.
I displayed my App.Property of APP.DI
R at start up and it is C:\TESTER\ ! How would my application know that "Word_Open.vi" and "Word_Open_Document.vi" are actually inside the _wordsub.llb?
Any ideas ?
Greg Klocek

Compact RIO and LabVIEW run time

Dear All,
Good Morning.
We are developing a new experimental setup which will have different components, such as mass spectrometer, pressure transducers, valves and thermocouples, RTDs. We are currently having LabVIEW 8.6 Run time. We would like to control different components and acquire data using CompactRIO. I am not clear if compact RIO works with 8.5 run time. In the developers guide NI, mention about the real-time LabVIEW.
Thank you very much for help,
Zach

You need the Real-Time Toolkit (and possibly the FPGA toolkit, depending on your needs) to work with the cRIO. The version of LabVIEW installed on the cRIO must match the version you're using for programming on the PC (so you can't have LabVIEW 8.5 on the cRIO and 8.6 on your computer). The LabVIEW Real-Time is not the same as the LabVIEW Run-Time engine. The Run-Time engine lets you run compiled applications on your computer. The Real-Time toolkit lets you program real-time targets such as the CompactRIO.

Can I partition a 1tb hard drive and also run time machine on that hard drive

I have a 1TB external hard drive which s currently running for Time machine only.
I was hoping to be able to partition the EHD so that 500GB would be for the Time Machine side and the other 500GB would be used as an ecternal storage [ a friend of mine has just lent me a 250gb hard drive with a load of tv series which i want to be able to copy].
Can anyone tell me if this is possible and if so how do i do it.
I know that Time Machine is running now but I don't mind starting all over again.

Yes it is possible, but it is generally not a good idea. That being said, if you decide to use the EHD for another purpose, partitioning it is the best solution. How big is your internal HD? It is recommended for a TM partition to be 2X as large as your internal drive, and it must be at least the size of your internal HD in order to be used.
In order to partition:
1) Connect the EHD
2) Open Disk Utility and select the drive
3) Click the "partition" tab and drag the original partition to its desired size.
4) Click "Apply" to create the secondary partition.
Resizing the TM partition will not erase it.

INI instrument driver and fatal run time errors

Hey everyone, I'm experimenting with the INI instrument driver and running into a fatal run time error. Here's what I know so far:
The runtime error only happens during the very first Ini_Putxxx
It only happens if the target INI file does not yet exist. After the file is created with a Ini_WriteToFile, then the program will proceed with all my Put functions without any errors.
Ideas?
Solved!
Go to Solution.

Are you sure about that? I just tried calling these functions in the Interactive Execution window without errors (the destination file wasn't there before the call and has been created without errors):
#include "inifile.h"
static int error = 0;
static IniText T = 0;
T = Ini_New (0);
Ini_PutString (T, "General", "Item 1", "Test string");
Ini_PutInt (T, "General", "Item 2", 123);
Ini_PutDouble (T, "General", "Item 3", Pi ());
error = Ini_WriteToFile (T, "C:\\test.ini");
Ini_Dispose (T);
Ini_PutXX functions do not make any disk access, they work entirely in memory; the only functions where the instrument accesses the disk are Ini_WriteToFile and Ini_ReadFromFile. Which error are you receiving? Can you post a sample code that exhibits the error?
Proud to use LW/CVI from 3.1 on.
My contributions to the Developer Zone Community
If I have helped you, why not giving me a kudos?

Include LabVIEW Run-Time Engine in C# Project Distribution

I have written a software package in Visual Studio using C# which calls a number of functions from a dll which I have built in LabVIEW. I am now trying to produce an installation program for my C# package but can't quite work out how to include the LabVIEW Run-Time Engine in this installation.
I am creating the installation program by defining a Visual Studio Deployment Project and I have added my LabVIEW dll to this. However, the dll requires the LabVIEW Run-Time Engine to also be installed on the target PC. I was hoping that there would be a set of files to implement the installation of the LabVIEW Run-Time Engine that I could include in my Visual Studio Deployment Project and do the installation of both my C# code and my LabVIEW dll (inc Engine) in one operation. Is this possible? Or do I need to produce a LabVIEW installation for my dll separately from the C# installation?
Info:
Development OS = Windows 2000
Target OS = Windows XP
C# Development Environment = Microsoft Visual Studio 2005 V8.0
LabVIEW Version = 8.5
Also, I am using the Order Analysis Toolkit and noticed that there seemed to be an 'Order Analysis Run-Time Engine' installed on my PC. Do I need this too?
Thanks for any help.
CAS

Hi CAS,
One way of automating the installation of the LabVIEW run-time engine is to use commands in a batch file (*.bat). These commands would be executed automatically at the same time as your distribution installer to install LVRT with your C# application. For more information on command line options, have a look at this KB. I don't have so much knowledge of C# distributions, though, so there may be a better way to approach this that someone else in the community could advise you on.
With regard to the order analysis toolkit, you will also need this runtime engine installed. A point to note, though, is that the toolkit requires a run-time licence to be deployed in this fashion. It is now part of the Sound and Vibration Measurement Suite and needs to be licenced accordingly.
I hope this helps!
Best regards,
Tom
Applications Engineering, NI UK

NI-LabVIEW run-time engine interop 2010 failed to install

Hi,
While installing Labview 2010 (32 bit) I got an error message:
NI-LabVIEW run-time engine interop 2010 installation has failed with the following error:
Error 1935. .... (see the .ppt for screenshot if interested)... HRESULT 0x8002802F
I googled HRESULT 0x8002802F and found a page that said that this error is usually b/c of a missing/corrupt entry in the registry: file %windir%\system32\mscoree.dll, and that "repairing the highest version of the .NET Framework on the system will correct any problems resulting from this error."
I have verified that mscoree.dll is not present, and I don't have the .NET Framework installed on my system. SO, I have the following questions:
1) do you concur with the advice given on the page referenced re: the reason for the error;
2) If so, should I install .NET Framework, and what do I then need to do in LabVIEW to tell it that the .dll is now present?
3) If your opinion is other, what do you advise?
Cheers
Attachments:
Labview Installation error.ppt ‏227 KB

Hi Luke,
After doing some research, there are two possible solutions.
1) According to a KB, it could be your antivirus. You may want to try to turn off any spyware blocking software such as Ad-Aware, Norton, etc and try the installation again.
2) Another customer had the same error, and they got it working by installing .NET 3.5 from Microsoft's website and then installing LabVIEW again.
Hope one of those options work for you!

How to include LabVIEW Run-Time in executable file ?

Hello folks,
I have an application that need the user to simply calling executable file without setting up LabVIEW run-time because my executable file will be posted in LAN and anyone can run it remotely. What should I do? Any help very appreciate...
Thanks so much

You have to have labVIEW run-time installed on your computer in order to run a LabVIEW programs (vi or exe). What you can do when you distribute an exe file is to create an installer which lets you install LabVIEW run-time and create a menu item (in Windows) in the Start>>Programs menus. Then you can distribute the whole package and after running the installer, LabVIEW run time as well as the exe is installed.
You can do this in the installer settings of the Application builder (when you create the .exe file). Go to the "Advanced" section. There you can add the LabVIEW run-time Engine to the installer.
One other possibility you can do if several people want to use the programm over Lan is to use the LabVIEW webserver. You can run a programm somewhere on the
network and other people can open the front panel in their Webbrowser. But maybe that's not exactly what you want. ??

How to download pictures fm i-photo to USB flash drive and/or to a cd

How can a person download pictures from i-photo to a USB flash drive
and/or to a cd with the purpose being to share the photos with another
group using a laptop computer to control and project images to a screen.
I can't find instructions anywhere in apple help. Please keep it simple.
Thanks.
LAS (Learning Apple Stuff)

Select the pics in the iPhoto Window and go File -> Export and export them to a Folder on the desktop. Then drag that folder to the USB drive / or burn it to CD with the Finder's Burn command.
Regards
TD

Booting from a USB Flash Drive and Optimizing Performance

I know that you can boot Leopard from a USB flash drive, and I have a 16GB flash drive I'm using as a bootup disk on this 2006 MacBook I have that has a broken hard drive (it was recalled, but the recall ended in 2010).
The problem is that it's very slow. I have about 8GB of free space on it, so it can't be the VRAM being too small. The USB speed just stinks. There must be ways to optimize the OS to run off of a slow drive by accessing data as infrequently as possible. What can I do to speed this up? Should I disable hard disk sleeping? Should I use some kind of Mac tuneup/optimization tool's feature?
I plan to get an internal hard drive for it, but I'm stuck with this for a while.

Not all USB2 Flash drives are equal, in fact I bought 2 16 GB USB drives for cheap, as along side of them were even the same brand 16 GB Flash Drives just a different model, for 5 times as much!
Me was thinking how bad could they be? Well, they could be 5 times worse than other USB2 flash drives... LOL on me!
They under extremely rare occasions will Read or Write at 5 MB/s, & very often 1 MB/s...
My Buffalo Flash drives do near USB2's top speed, see some diffs...
http://usbspeed.nirsoft.net/
Optimizing yours will give little benefit.
You could also do a USB2 RAID0 setup if you have enough ports.

Could I use two regular computer to achieve realtime communication using the Ethercat and Labview Real Time Module?

Could I use two regular computers (one acts master , another one acts as slave using the Ethercat Internet Card) to achieve realtime communication using the Ethercat and Labview Real Time Module? if it could, what hardware should I purchase from the NI ?
Thank you!

Hi Xiaolin,
NI doesn't offer Windows based Ethercat master or slave software. Only LabVIEW RT can run the Ethercat driver.
However, you could use a LabVIEW RT target as an Ethercat master and use the Ethercat Internet Card with a slave PC (note: I think this will work from the Beckhoff description of the card you are describing. The card should integrate like any other non-NI slave. However I haven't tested the setup and don't advise saying it will work until you have tried).
You can use any NI RT target with two ethernet ports as the Ethercat master. This could be a cRIO, PXI or RT Desktop.
Jesse Dennis
Design Engineer
Erdos Miller

I am running out of memory on my hard drive and need to delete files. How can I see all the files/applications on my hard drive so I can see what is taking up a lot of room?

I am running out of memory on my hard drive and need to delete files. How can I see all the files/applications on my hard drive so I can see what is taking up a lot of room?
Thanks!
David

Either of these should help.
http://grandperspectiv.sourceforge.net/
http://www.whatsizemac.com/
Or search 'disk size' in the App Store.
Be carefull with what you delete & have a backup BEFORE you start, you may also want to reboot to try to free any memory that may have been written to disk.

I recently had some 8mm film transferred to DVD. I am trying to edit the film clips using Premier Elements 4.0. Some of the film clips copy into the project but others don't. I tried copying the VOB filed onto my hard drive and then changing the file ext

I recently had some 8mm film transferred to DVD. I am trying to edit the film clips using Premier Elements 4.0. so I can reburn the films on a single BluRay disc. Some of the film clips copy into the project but others don't. I tried copying the VOB filed onto my hard drive and then changing the file extensions on the VOB files to MPEG but this was no help. Some of the VOB files contain numerous film clips but my software does not appear to be able to recognize them as such. I need to know if replacing my old Premier Elements with the new Version 13 would solve this problem or not. Any advice would be greatly appreciated!
Bob

Bob
What do you have now.....
What computer operating system do you have?
We can go into the finer points of source and your intentions, but for now it would appear that you are using SD 4:3 source media to get to a HD 16:9 result. Lots to discuss in this regard.
What was given to you on the DVD disc? DVD-VIDEO 4:3 or something else?
If DVD-VIDEO on DVD disc, you should expect to find on the disc a folder named VIDEO_TS. That is your target for your video files.
If you were given a DVD-VIDEO on DVD disc, then all you want from it are the video files, specifically
VTS_01_1.VOB, VTS_01_2.VOB, and so on through that series until possibly getting to
VTS_02_1.VOB, and so on. How many files you have beyond the VTS_01_1.VOB file will depend on the size of the DVD-VIDEO.
Does the above scenario apply to you?
The alternative might be someone giving a DVD disc (data disc) which contains just the VTS files mentioned which were copied from
the VIDEO_TS Folder. So, you do not get the whole VIDEO_TS Folder, just the essential video files. Does this scenario apply to you.
I see no need to replace your Premiere Elements 4 with a later version unless you have a huge project and need a later version that will be a 64 bit application running specifically on Windows 7, 8, or 8.1 64 bit computer.
Consider...Premiere Elements 4 and if you have DVD-VIDEO on DVD....
1. Place the DVD disc in the burner tray
2. Open Premiere Elements 4 and set the project preset for NTSC DV Standard (assuming you are working in a NTSC setup)
3. Go to
Get Media
"DVD, Digital Camera, Mobile Phone, Hard Drive Camcorder, Card Reader"
"Adobe Premiere Elements - Media Downloader" and its Advanced dialog.
Set the Source in the latter dialog for the drive which has your DVD disc inserted in its tray
You should see your VTS_01_1.VOB thumbnail in the "Adobe Premiere Elements - Media Downloader" Advanced dialog.
With this VOB selected, click on Get Media to get the file from there into the project.
Should work fine.
Complications may be involved if the people who processed your footage gave you something other what is described above.
Please review and consider, and then we can plan our project strategy accordingly.
Thank you.
ATR

LabVIEW Run Time Engine and ActiveX Automation Server

Hi,
I have a question related to LabVIEW Run Time Engine and ActiveX Automation Server:
We have a tool developed in LabVIEW and TestStand. End user interface is a LabVIEW GUI (it's an executable) which executes TestStand sequences. Some TestStand sequences call lower level LabVIEW VIs.
Everything works fine with LabVIEW installed, but I was wondering if I could run this tool on deployment machine with only LabVIEW run time engine installed. We are using LabVIEW 6.1 and with only the run time engine installed, I get the error message: "Unable to launch the 'LabVIEW.Application' ActiveX automation server ".
BTW, we are planning to upgrade the versions soon.
Is it possible to make things work only with the run time engine?
Thank you.

Thanks for the response, Brian.
I did upgrade to LabVIEW 8.0 and TestStand 3.5. Everything works fine on the development computer where LabVIEW and TestStand is installed. On the target computer in the lab, I installed LV RTE 8.0 and TestStand 3.5, and now when a VI is called in a sequence file, I get the following:
RunState.PreviousStep.Result.Error.Code -18002
RunState.PreviousStep.Result.Error.Msg "LabVIEW: The VI is not executable"
So, the executable opens and works fine (which means that the LV RTE is installed properly), but when a sequence calls a low level VI, it does not make it through.
comments/suggestions are appreciated. Thanks.

Integrating an NI-USB 8451 driver and Labview Run-Time Files in an installation package of a .vi application

Similar Messages

Maybe you are looking for