Labview 8.5 .VIs

Hi,
I have some old .VI's that I want to continue developing.
They were created in Labview 8.5.
When loading the .VI's I get the messages that "deviceopen.VI", "DIOwriteportbyte.VI", "AIconfig.VI", etc cant be found.
I tried but cant find where I can download Labview 8.5. It would be easier for me to download 8.5 than to try to figure out how to upgrade 30 .VI's.
I currenty use Labview 2013.
Any suggestions?

Thank you for the suggestions.
As I use a 64 bit system, the traditional daq is not available to me.
As for rewriting the .VI's to daqmx, I am pretty new to this so I could if possible use some help or example suggestions.
I have attached three of the files that I need to rewrite as examples.
Attachments:
4718_digital_input.vi ‏11 KB
4718_digital_output.vi ‏14 KB
barometer.vi ‏25 KB

Similar Messages

Can LabVIEW Run-Time Engine 7.0 control LabVIEW 6.1 VIs?

I'm attempting to remotely control a LabVIEW 6.1 example VI through the browser plugin on another system. On that other system, can I use LabVIEW Run-Time Engine 7.0? Or do I need 6.1?

Never mind, I should have read the RTE 7.0 information first. I need LabVIEW Run-Time Engine 6.1 to run LabVIEW 6.1 VIs.

Labview Executable with VISA functions in Run Time Engine

Hi Everybody
I designed a gui to communicate using VISA GPIB. I created an executable for the gui. I also installed LabView Run Time Engine on the desired machine. I recieved couple of errors, for which I copied the files visa32.dll, NIVISV32.dll and serpdrv to the folder with the executable.
I recieved the following error, ' Initialization of NIVISV32.dll failed. The process interminating abnormally.'
Are there any drivers I should install in addition to the Run Time Engine? If so, where can I find these drivers?
Thank you
Jackie

I installed NI-VISA with similar version as my development installation, and LV runtime engine. Labview still crashed.
I noticed certain library functions in full labview that is not present in the NI-VISA + LV run time directory, such as _visa.llb etc.
Do I need to copy these additional library functions too? Will Run Time Engine read these library functions?

Labview opens all VIS in Run mode

LV2013 PDS is opening all VIs in Run Mode. This is a global problem, not specific to one or a specific number of VIs.
If I create a new VI, save it, close it and re-open it, it's in Run Mode, not Edit mode. Nothing is set to Run When Opened, nothing is set to be locked without a password.
It's only on this installation; if I take my code to another machine, there's no issue.
I have deleted the labview.INI file, but the behavior repeats itself.
Any ideas?

Jed_Davidow wrote:
SCC is not configured; I use perforce, but it's not configued to use it or to treat read-only as locked. I have also checked out all the filed ahead of time with P4, so LV never sees them locked. The folders themselves are not read-only.
Also, I have created VIs outside of my P4 folder, and I have the same trouble.
Example:
Launch LV: Create a blank VI (comes up in Edit mode).
Save to Desktop (not within P4 control) as test.VI
Close
Open test.VI ---> It's in Run Mode
I have never seen this happen before.
Neither have I
I'll assume a reboot was attempted and did not change anything. I would attempt a repair of LabVIEW from the control panel and another restart.
Jeff

Hi, can someone help me how can i connected my multimeter to my pc with rs232, because my computer can´t recognize the device, i mean the multimeter, is a multimeter keithley serie 2400, and i already downloaded all the drivers for labview even the VISA

hi, can someone help me how can i connected my multimeter to my pc with rs232, because my computer can´t recognize the device, i mean the multimeter, is a multimeter keithley serie 2400, and i already downloaded all the drivers for labview even the VISA

Marco,
Here are some suggestions:
1) Check the manual the Keithley manual to see how to configure the RS-232.
    On some models you need set Factory defaults to USER and turn on the RS-232.
    Also there may be a setting for SCPI which you want on (probably on by default).
2) On your PC - open Device Manager. See if a COM port exists and is functional.
     You must get this working before continuing.
      You can set the COM port parameters by right clicking and selecting Properties.
     (On some PCs the onboard ports can be disabled in the BIOS)
3) If step two was OK, open MAX (Measurement and Automation eXplorer).
    On the left side, click on Devices and Hardware.
    Click on Serial and Parallel.
    Go to the COM port you found in Device Manager.
    Open a VISA Test Panel.
    Now I don't have one I can look at right now, so this is general idea:
   Configure the COM port to match the Keithley settings (should be OK if step 2 worked)
   Go to the (I think) Input Output tab (you want to send a command)
   The command string input should already have a *IDN? entered, if not, type it in.
   Click on the Query button to send the command and check the response.
   If you get an ID string back (Company name, Model, FW Version ...) then it works.
   (Disregard an error saying it did not get enough charcters back.)
I hope this helps,
steve
Help the forum when you get help. Click the "Solution?" icon on the reply that answers your
question. Give "Kudos" to replies that help.

Examples for labview having sub vis

I am making some examples for labview adding to labview example directory (..\LabVIEW xxxx\examples\my own examples).
My examples contains some sub vis. As i copy example files and sub vis to (..\LabVIEW xxxx\examples\my own examples) then i see all files in example finder example files and sub vis. Is there any method that doesnot show sub vis in wxample finder. I will be very thank full to you NI. Sorry if i am duplicating post.
regards

I have a couple of thoughts about your questions:
1) When browsing by Directory, yes you will see subVIs. A common practice is to put all your subVIs in a separate folder labeled 'subVIs'. That way they don't look mixed among your examples.
2) Darren is correct that the bin3 file format is the same for all versions of LabVIEW, and that the bin3 file you created for LV 2010 will work in 2011. Notice he mentioned to put your bin3 file in [LabVIEW 20xx]\examples\exbins. This is important for LabVIEW 2011 and beyond. In LabVIEW 2010 and prior we would look anywhere in the examples folder for bin3 files. To speed up the launch time of the NI Example Finder, starting in LabVIEW 2011, you must put your bin3 file in the \examples\exbins, instr.lib, or user.lib folder. You can find this information if you click the Help button from within the Prepare Example VIs for NI Example Finder.

Mac Standalone LabVIEW App - Include Visa & LabvIEW Run-time

Hello All,
I've used LabVIEW for over a decade but only for Windows, just getting into LabVIEW for mac, so please pardon any ignorant questions.
I am developing a very simple project to be deployed stand-alone that needs LV Run-time and NI Visa. My project uses a simple USB-Serial device that I talk to using Visa. I used this link to package LabVIEW run-time with my app. I think I need to package NI Visa drivers as well. I am not sure how to do that. Anybody have any experience packaging drivers with stand alone apps for LabVIEW in mac? Thanks for your help.
Kudos always welcome for helpful posts
Solved!
Go to Solution.

Thanks, Silvia. This is a limitation and there are more and more developers on Mac OS. Can you provide answers for couple questions:
Any plans to include Installer App like how we have for Windows OS?
If [1] is not anytime soon, can NI provide a KB to deploy a stand-alone Mac app packaging drivers? I think this will be very valuable.
Kudos always welcome for helpful posts

Windows7 / LabVIEW 2010 project / vis access denied

Since I upgraded my OS to Windows 7 and my LabVIEW version to 2010 my project or the vis that I write cannot be opened by fellow administrators on the computer. Older projects and vis that were written in 8.6.1 are not experencing this problem. The computer support techs have checked out my settings in Windows and ensured me that I have everything shared properly. The other administrators can open any other type of file and make changes that demonstrate that Windows is not restricting their access and that they are administrators. Is there a setting in LabVIEW that would be restricting them?

Hi Joel
Thanks for the reply. I just checked the protections in the VI properties and it's set for unlocked (no password). I'll get the staff member I work for to log on and will try to write a VI under his account. We haven't tried other people on that computer. I will try that though. I just had the new OS installed and I installed LV2010 within the last 3 or 4 weeks. What seems weird to me is that he can run the VIs that I wrote in LabVIEW 8.6 before the computer rebuild. They open just fine in LV2010.
OK - I just found the problem and it is not LabVIEW's fault. I had a different person that was an administrator log onto the machine. He could run 90% of the VIs but could not open the project or a couple of the VIs. It would come up with a box saying that he did not have the permissions to open those files. A different computer support person came over and had seen this kind of problem before. To make it work for everyone, LabVIEW must be started by selecting to "run as administrator". You cannot start LabVIEW by double clicking on the project or vi or that will start the program in a normal mode. I guess Windows7 has bugs in the UAC (user access control) and even though a person is an administrator the OS will pick and choose where they can go and what they can do.THANK YOU Microsoft for making me so secure and unproductive.
Thank you for your time Joel. I hope this post might help others.
Joe Lundstrom

How to detect a lost TCPIP SOCKET using LabVIEW and NI VISA

I am using VISA functions in LabVIEW to remotely communicate with instruments over TCPIP SOCKET visa resources. In general this all works well by simply creating a resource name, passing it to VISA Open and then setting a couple of session attributes. Occasionally an instrument will be reset or power cycled and what I have noticed is that I need to call a VISA Close and then reopen the resource in order to get it to communicate again or close LabVIEW and run again. If you just use VISA Open without calling a VISA Close first you cannot communicate with the target. The problem is that I have no way of detecting this condition. I have tried always calling a VISA Close before VISA Open and this seems to work for this condition but it seems odd to always close a session before opening it. Why does VISA OPEN not work under this condition and is there any way to detect this situation?
Solved!
Go to Solution.

It works that way because that is how TCP works. A TCP connection is a dedicated connection between two endpoints. Unfortunately other than getting an error from a read or write operation there is no way to determine if the othe rside of teh connection is still there. You need to close the connection because otherwise VISA will continue to use th eold connection which is no longer valid. Closing it allows the system to cleanup the dead connection.
If you are communicating fairly infrequently you could simply open the connection, do you stuff and close it. The overhead for establishing the new connection is not that much. If you are using steady streams of data then you will need to watch for the errors and then reestablish the connection by closing the old one and opening a new connection as you have observed.
Mark Yedinak
"Does anyone know where the love of God goes when the waves turn the minutes to hours?"
Wreck of the Edmund Fitzgerald - Gordon Lightfoot

Do I need LabView to load VIs in TestStand ?

Hello,
I have TestStand 2012 installed on my machine and recently also installed LabView Runtime engine but do not have LabView Development license.
When I try to call a labView Project and its VIs, I get an error message unable to load Project. On another machine where I have labView installed, for the same paroject and VI, I do not get any error message.
Does it mean that I need to have LabView development license in order to call VIs. I always thought that run-time engine would be sufficient for such tasks where we are just calling VIs and not developing those on TestMachines.
Regards
Ricky

Hi,
thanks for suggestiong the possible solution.
actually, I could not get it working, unitll I installed LabView (test verion), then I changed adapter settings and then I opened the project in LabView. After opening, it loaded project in "MyComputer" and now I am able to see different VIs available in the project. I had to change paths everywhere in the project.
I am unable to understand, what "MyComputer" in LV means? I am able to browse VIs but not in my actual hard drive but a virtual my computer created by LabView. I wish to work without LabView but the prerequisite to open project in LV is hindering me to do it.
The Error I get is Unable to load project when I try opening a VI (without Project being loaded in LV "My Computer".
I do not know if something has to be changed by VI programmer or is it standard that virtual LV my computer must run on every maching?
Regards
Ricky

Labview USB with VISA on Mac OS X

Hi-
I have a 3rd party USB DAQ device that I'm trying to make work within labview 7.0. I've gone through the device tutorial on creating a driver with Windows2000. With Windows 2000 after using the VISA driver wizard the subvi "visa find resources" finds the DAQ device and I can talk to it
with a bulk transfer with VISA write.
With a Mac OS X (10.4), the system profiler sees the DAQ but I the VISA driver wizard won't allow me to check the usb button. The labview subvi "visa find resources" doesn't find the
DAQ. What equilivent steps do I need to do with OSX so that the find resources vi finds my DAQ?

Finally fixed the PermGen errors. I can run all day now without crashing. It turns out the eclipse.ini file is very tricky! You have to have carriage returns in the right places. Run the jmap -heap <pid> on the eclipse process id. It will tell you if your PermGen memory is actually setup how you thought it was supposed to be.
Here's my final eclipse.ini
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
892m
-vmargs
-XX:PermSize=128m
-XX:MaxPermSize=892m
-Dapple.awt.graphics.UseQuartz=true
-Xdock:icon=../Resources/Eclipse.icns
-XstartOnFirstThread
-Dosgi.requiredJavaVersion=1.5
-Xms40m
-Xmx892m

LabVIEW DIAdem Connectivity VIs Toolkit

Hallo zusammen!
Ich habe folgendes Problem:
Ein LabVIEW-Programm, welches vermutlich mit LabVIEW_2007 geschrieben wurde soll nun mit LabVIEW_2010 wieder in Betrieb genommen werden. Das einzige Problem besteht nun noch darin, LabVIEW wieder mit Diadem zu verknüpfen.
Ist das mit einem der Connectivity VIs Toolkits, die jedoch auch von 2007 zu sein scheinen möglich? Oder hat jemand eine andre Idee, wie ich die beiden wieder verknüpfen könnte.
Schon mal vielen Dank für eure Hilfe imVorraus!
Gruß, JohannesDD

Hallo Manuel!
Erst mal vielen Dank für deine Antwort.
Das VI von LV_07 hab ich schon probiert in LV_2010 zu öffnen. Dabei ist mir der Fehler ja überhaupt erst aufgefallen.
Ich vermute den Fehler im Bereich des DIAdem-Report-Wizard. Kann aber keine kompatible Version zu LV_2010 finden.
Leider ist das VI im Rahmen einer Diplomarbeit entwickelt worden, welche ich nun ausbauen soll.
Auf Grund des Urheberrechtes muss ich erst abklären, ob das VI hier gepostet werden darf.
Viele Grüße, Johannes

Here is a helpful blog on LabVIEW DAQmx Assistant VIs

http://www.dmcinfo.com/blog.aspx/articleType/ArticleView/articleId/256/categoryId/6/LabVIEW-DAQmx-As...

Hi Daniel,
the following knowledge base contains some information how to troubleshoot:
http://digital.ni.com/public.nsf/allkb/DC808866AF7D5C0986256FCE006E9BAB?OpenDocument
Maybe you didn't install the NI-VISA or NI-488.2 driver.
I wish you Merry Christmas and a Happy New Year.
With best regards
Ralf N.
Applications Engineering
Germany
PS:
If that wouldn't work for you, download the latest driver-CD from our website and install it. ( It may take a while. )
http://joule.ni.com/nidu/cds/view/p/id/1079/lang/de
I'd recommend to use an USB-harddisk for transferring the files.
Message Edited by ralfn on 12-23-2008 02:29 AM

Report generation VIs in Labview 6.1

Hello,
I am havinf problems with using Labview 6.1 VIs for report generations. The VIs provided by Labview are not executable! It seems as if they had internal errors, non fixed errors. Moreover, I am not able to open the diagram because it is password protected. Does someone know if there is any patch to fix this or the reason why these VIs don't work?
Thanks a lot!
Regards,
María

Hello Maria,
are you using the report Generation Toolkit for MS Office or the standard vis that LabVIEW provides for report generation?
If you use the Office toolkit, this may help:
http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/c8888a9a74e75c4786256cda00694a1e?OpenDocument
If not, this may also help:
http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/9acb175f6de483ae86256b2200776b8b?OpenDocument
In any case, WHAT I WOULD TRY FIRST is to do a Mass Compile of the folder where the report vis are located.
Here you can see what this does and how to perform it:
http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/654877e62a97b72986256c95006f9b24?OpenDocument
One last question...are you having trouble only
with executables or also during development?
Regards,
JorgeM.

LabVIEW built-in file I/O VIs have poor performance on network file I/O operation?

Hi,
I use LabVIEW built-in VIs to save a big 2-D array data into a ascii file (with the "write character to file" vi). When I write it on the local hard drive, it takes about 5 seconds to complete the task. But when I write the file on the network, it takes more than 5 minutes. A typical output file is 5MB big.
If I write the file on the hard drive, and use the built-in File MOVE vi, it takes about 30 seconds to complete the MOVE operation. But if I use Windows File Explorer to move the same file, it takes less than 1 second.
Both the PC and server are connected on a full-duplex 100BaseT network. I tried different file I/O operations (including MOVE, create new file and LIST)
with LabVIEW VIs and compared the speed with windows file explorer. It turned out LabVIEW VIs performance is always A LOT slower than Windows File Explorer. I tried the same test on many different PCs, with windows 98, NT, 2000, and the results are the same.
Is there anyway to improve the file IO performance or is there any other workaround on this issue, such as calling Windows File Explorer to perform the same task via ActiveX maybe?
Your imputs will be very much appreciated. Thanks!
Dan

Hi,
Do the ASCII files have a .txt extention? I've noticed the same behaviour
once, with .txt files. Renaming them (to e.g. .txq) fixed the problem.
I'm clueless why this happend. If you extentions are not .txt, I don't have
a clue...
What if you copy the file, and then delete the original?
Regards,
Wiebe.
"dikrn" wrote in message
news:506500000008000000EA7C0000-1042324653000@exchange.ni.com...
> Hi,
>
> I use LabVIEW built-in VIs to save a big 2-D array data into a ascii
> file (with the "write character to file" vi). When I write it on the
> local hard drive, it takes about 5 seconds to complete the task. But
> when I write the file on the network, it takes more than 5 minutes. A
> typical output file is 5MB big.
>
> If I write the file
on the hard drive, and use the built-in File MOVE
> vi, it takes about 30 seconds to complete the MOVE operation. But if I
> use Windows File Explorer to move the same file, it takes less than 1
> second.
>
> Both the PC and server are connected on a full-duplex 100BaseT
> network. I tried different file I/O operations (including MOVE,
> create new file and LIST) with LabVIEW VIs and compared the speed with
> windows file explorer. It turned out LabVIEW VIs performance is
> always A LOT slower than Windows File Explorer. I tried the same test
> on many different PCs, with windows 98, NT, 2000, and the results are
> the same.
>
> Is there anyway to improve the file IO performance or is there any
> other workaround on this issue, such as calling Windows File Explorer
> to perform the same task via ActiveX maybe?
>
> Your imputs will be very much appreciated. Thanks!
>
> Dan

Labview 8.5 .VIs

Similar Messages

Maybe you are looking for