Upgrade drivers when upgrading to LabView v.8?

After upgrading from LabVIEW version 7.1 to version 8.0 the Keithley 40-SR01 switch sytem (controlled by a 7002 main frame) does not function correctly. So when upgrading from LabVIEW 7.1 to LabVIEW 8.0 do I need to upgrade the device driver also?

Hi tcsieng,
You are correct. Just go to
http://sine.ni.com/apps/we/niid_web_display.download_page?p_id_guid=E3B19B3E91CB659CE034080020E74861
and download the driver again. When you go to install the folder, just
place it in the LabVIEW 8 directory instead of the LabVIEW 7 directory.
You should then be able to access the functions to speak with the 7002
main frame with no problems.
Regards,
Matt S.
LabVIEW Integration Engineer with experience in LabVIEW Real-Time, LabVIEW FPGA, DAQ, Machine Vision, as well as C/C++. CLAD, working on CLD and CLA.

Similar Messages

Is there anything in particlar that I need other than the installation disk when upgrading from Labview 8 to 2010

I have a Labview program that ran fine when I had Labview 8 installed. I recently upgraded to Labview 2010 and now my program will not work. When I run the program, none of my instruments read out and after about 5 seconds, the whole Labview program closes with no error messages. Can someone please help? I am a new Labview user and I don't really know how to troubleshoot this problem.

If you have the installation disks that should be all you need. You will need a connection to the internet to register your product.
Tim
Johnson Controls
Holland Michigan

NI-DAQmx 8.8 does not work properly after upgrade to LabVIEW 8.6

Hi,
I just upgraded to LabView 8.6 from version 7.1 and found out that the NI-DAQmx 8.8 drivers do not install correctly, since there is not Measurement I/O tab in the Functions palette (see attached document). The curious thing is that I can see all my NI-DAQmx devices in the MAX, and they all test correctly, i.e., they are working correctly. The sales representative for my area recommended me to uninstall , and reinstall LV8.6 and then reinstall the NI-DAQmx 8.8 drivers, but it did not work. I still do not see the Measurement I/O functions and my application says that it "cannot compile" the NI-DAQmx vi's. Thanks in advance for your help.
Peter
PS. Someone reported a similar problem back in 2003, but the final solution was not posted. Thanks again.
Attachments:
LV8.6.doc ‏116 KB

Dear Mallori,
Thanks for your help. You are right, I uninstalled and reinstalled LabVIEW 8.6 (update from LabVIEW 7.1) and reinstalled DAQmx 8.8. I still continue to have some problem that seem (to me) beyond compatibility issues. Here are the answers to your questions:
1. Before you reinstalled DAQmx 8.8, did you
uninstall it? If not, then I believe that the installer would see the
driver already present and not actually make any changes.
REPLY: No, I did not uninstall DAQmx 8.8. What do you recommend? Should I uninstall BOTH LabVIEW 8.6 and DAQmx 8.8 and then reinstall everything again?
2. When you say that the VIs are not responsive,
could you describe this a bit better? Perhaps post one of the error
messages about compiling that you mentioned in your first post?
REPLY: I am having a lots of "This SubVI is not executable" error messages in many of the library VI's not even mine. See the attached file.
3. If you open the NI Example Finder (Help»Find
Examples) and the expand Hardware Input and Output»DAQmx»Analog
Measurements»Voltage, are you able to run one of the example programs
and see the correct values that you see in the Measurement and
Automation Explorer Test Panels?
REPLY: I tried to runa couple of the examples for continuous voltage acquisition (internal clock) and both open with errors (see attachement).
Thanks again for your help. I am looking forward to your recommendation.
Regards,
Peter
Attachments:
LV8.6-3.doc ‏43 KB

Since upgrading to LabVIEW 2013, every VI compiles every time I open it (including quick-drop).

Hi all. Since upgrading to LabVIEW 2013, every VI compiles every time I open it (including quick-drop). This really slows things down! Perhaps related, my system tells me I don't have permission/access to modify my LabVIEW ini. Has anyone seen similar, and/or any hints towards a solution?

Jeff-P wrote:
As a side note, LabVIEW.ini is a file that gets generated by LabVIEW when it is launched if the file does not exist. So if you are missing the 32-bit ini file, launch 32-bit LabVIEW and that file should be created.
I thought that the message: "Perhaps related, my system tells me I don't have permission/access to modify my LabVIEW ini" might indicate that the labview.ini file cannot even be created... strange...
LabVIEW Champion . Do more with less code and in less time .

Can not access serial port while upgrading from LabVIEW 6.1 to 7.0

Hi,
I built an application under LabVIEW 6.0.2. few years ago. This application uses LabVIEW serial features. When I upgraded to LabVIEW 6.1, my application was still working correctly.
Today, I upgraded to LabVIEW 7.0, mass compile all VIs and now my application can not communicate with my peripheral !!!
The program is sending the command to the peripheral. The peripheral answers but LabVIEW serial driver does not see any datas on buffer even if datas are available ... "Bytes At serial port.vi" always returns 0. I am sure that datas are available, using a COM port psy.
Does anyone has an idea?
I saw a lot of solutions in the forum, but I would like to know the best solution with minimum work, te
st, and so on ... on my program.
Regards,
Pascal.

Hi Pascal,
Which is your version of NI-VISA?
Please see the link bellow :
http://digital.ni.com/manuals.nsf/websearch/E8D86CD680B0753D86256D2C005D8EA0
The first test to be made is to test the communication with your serial port using MAX (Measurement and Automation Explorer) :
Open MAX, Go to "Devices and Interfaces", then "Ports", select COM1 (or ASRL1::INSTR). Right clic on it and select "Open VISA Session" the go the "Basic I/O" then Write data, execute, Read data, execute.
Be sure that the communication is OK. Be sure that you use the same Alias existing in MAX in your LabVIEW program.
Now, if all is OK, try to use Serial communication examples existing in LabVIEW Help>>Examples Finder. These examples use NI-VISA VIs.
If all above is OK and you
still have the same problem, try to follow these instructions :
"In order to use the old Serial Compatibility VIs in LabVIEW 7.x, you must copy the following files from a previous version of LabVIEW to the LabVIEW 7.x directory:
Replace the serial.llb in LabVIEW 7.x with the serial.llb from a previous version of LabVIEW. This file is found in C:\Program Files\National Instruments\LabVIEW\vi.lib\instr.
Replace the _sersup.llb file in LabVIEW 7.x with the _sersup.llb from a previous version of LabVIEW. In LabVIEW 6i and 6.1 this file is located in C:\Program Files\National Instruments\LabVIEW\vi.lib\platform. In LabVIEW 7.x (and 5.x) this file is found in C:\Program Files\National Instruments\LabVIEW\vi.lib\instr.
Copy the file serpdrv to the C:\Program Files\National Instruments\LabVIEW 7.x directory. This file is not installed with LabVIEW 7.x, so it only needs to be copied from a previous version of LabVIEW, not replaced."
I hope that my answer will help you.
Sa
naa T
National Instruments

System exception code 0xc0000005 after upgrading to LabVIEW 8.2

After upgrading to LabVIEW 8.2 from LabVIEW 8.0 I am continously getting a system reboot on my PXI (8187) when attempting to run my real time loops which worked fine with LabVIEW 8.0. The loops seem to start, and within less than a 30 seconds the system reboots. Upon reboot a message is displayed reboot due to system error. After running and getting this error again the system reboots into safe mode. Looking at the nirtlog file on the PXI, there is system crash log which list the exception code as 0xC0000005 and a listing of loaded dlls.
Does anyone have any idea what may be leading to this?
Thanks,
Kevin

The following is a simple example that produces the exception and reboots the PXI. This VI was originally created on a machine with LabVIEW version 8.0 and run on a PXI-8187 w/ RealTime version 8 and it ran without issue. I then took the VI to a machine running LabVIEW 8.2, I opened the VI, which compiled it to version 8.2, and ran it on another PXI-8187 w/ RealTime version 8.2 and I got a system exception and the PXI rebooted. If I run the two loops at the same priority level, it seems to run without issue. Also if I run with the loops at different priority levels and place a check in the Discard Missed Periods and in the Maintain Original Phase of the lower priority loop, it seems to run fine as well. However if I uncheck either the Discard Missed Periods or the Maintain Original Phase (as is set in the attached VI) the exception will occur. Any thoughts on what is going on, am I doing something wrong?
Thanks,
Kevin
Attachments:
TestLoop.vi ‏155 KB

Upgraded from LabVIEW 8 to 2013 and now VI asks to find the installation package for Run-Time Engine 7.0

I recently installed LabVIEW 2013 on a computer (running Windows XP 32-bit). The machine also has LabVIEW 8 installed, which is what I was using prior to upgrading. I opened a VI that was created in LV8 and then saved it and all its subVIs in LV2013. Now when I open the VI in LV2013 and try to run it, a window pops up asking me to find the "lvruntimeeng.msi" installation package for LabVIEW Run-Time Engine 7.0. If I cancel that dialog box and the subsequent message stating that the installion files were not found, the VI appears (at least from intial inspection) to run normally.
I closed LabVIEW, downloaded Run-Time Engine 7.0 from the NI website, and tried to install it, but I received a message saying that it is already installed (as I had suspected). How can I determine what part of the VI and/or its subVIs is trying to make use of Run-Time Engine 7.0? Alternatively, how can I get LabVIEW to instead use the Run-Time Engine 2013 that was installed when I upgraded to LabVIEW 2013?
Solved!
Go to Solution.

Bob_Schor wrote:
Are you running your VI from a Project? If so, you can look at Dependencies and get an idea what "dependent" VIs you might have. There may be "something old" in your LabVIEW 8 code that has been superceded in 2013, but still "hangs around" -- if you can identify it, you can probably replace it with its "more modern" equivalent.
If you do not have the VI in a Project, you can simply open LabVIEW, create a new blank project, and add your top level VI to it. If all of your relevant VIs are in a single folder, add the entire folder. Now look in Dependencies.
BS
Yes I am running the VI from within a LV Project. After some more searching in the NI Knowledgebase I was able to fix the problem by using the following procedure:
1. Use the Measurement and Automation Explorer to uninstall Run-Time Engine 7.0
2. Restart the PC
3. Open the project, close the project choosing to "save all"
4. Restart the PC
5. Re-install Run-Time Engine 7.0 using a file downloaded from ni.com
6. Restart the PC
7. Open the project, close the project choosing to "save all"
8. Open the project and run the VI. No more messages about LabVIEW trying to find Run-Time Engine 7.0.

How can I upgrade my LabVIEW 8.5 to the latest version LabVIEW 8.5.1?

Hi
I am currently using LabVIEW 8.5 Professional Development System and encountered an error when dealing with 4D Replace Array Subset. From the discussion forum, this bug has been reported before and logged under the CAR (Correction Action Request) number 4CFADPDX. The fix however is released in the LabVIEW 8.5.1 version.
Thus I'd like to know how I can upgrade my LabVIEW 8.5 version to LabVIEW 8.5.1 to resolve this error?
Appreciate all the help.
Thank you
Jega

If you're don't have a maintenance subscription, you can probably purchase an upgrade from what I can see from the links quoted above.
Try the upgrade advisor or contact your local service rep.
Message Edited by altenbach on 04-10-2009 08:29 AM
LabVIEW Champion . Do more with less code and in less time .

Problems with IMAQ Vision after upgrading from Labview 6i to Labview 6.1

Hi,
We just upgraded from Labview 6i to 6.1.To do this,we uninstalled the 6i version as was suggested by NI and then installed the 6.1 version.Later when we tried to run the old vi's written using Imaq vision, we ran into different problems.Has anyone experienced any similar problems with IMaq vision after upgrading?If so please help me solve this issue.
Thanx
deepak

What kind of problems?
I would strongly suggest that you uninstall IMAQ (all elements) and reinstall them. They register with Windows, probably docked to 6i, and also must be recompiled, which I believe is done in installation.
This is your best bet.
If you still have problems, contact NI and ni.com/ask and start a support inquiry.

Upgrade from LabView 5.0 to 5.0.1

I´m currently using LabView 5.0. I have some problems using GPIB and asynchronous access calls. These issues are solved in Version 5.0.1.
Now, how can I upgrade to Version 5.0.1? I seems that there is no way to download a corresponding patch from the NI website..?
Thanx.

Hello,
As I recall, the 5.0.1 update was not available as a web download because it was too large. I believe you must contact NI in order to get the 5.0.1 update CD sent to you, if it is still available.
Might I recommend upgrading to LabVIEW 7.0? I first started using LabVIEW with version 5.0.1 (back in January 99), and looking back, I feel like I was programming with an abacus, what with all the great new features introduced in LabVIEW since then (my favorite probably being the Event Structure). Of course, I am a bit biased, since I work for NI...
-D
Darren Nattinger, CLA
LabVIEW Artisan and Nugget Penman

Upgrading from LabVIEW 6.1 to 7.1, get a MS C++ Runtime Error

After upgrading from LabVIeW 6.1 to 7.1, I get a Microsoft Visual C++ Runtime Error
It states:
Runtime Error!
Program:...ogram Files\National Instruments\LabVIEW 7.1\LabVIEW.exe
abnormal program termination
I am using Windows NT, ver 4.0 SP 6.

I assume you get this error message everytime LabVIEW starts. This is not normal behavior. It is not even a common error. Have you tried reinstalling?

Problemm with the Goop Wizard while upgrading to LabVIEW 7.

I upgraded my LabVIEW from vers 6i to vers 7 and I've problemms with the Goop wizard, it doesn't appear in the Tools menu as it used. I supposse that I should upgrade the vers of my goop wizard too, but does anybody know if there is a goop wizard for LabVIEW7 and where could I doenload it from?

Hi,
If you use GOOP Wizard 1 (downloaded from NI), you have to reinstall it. Make sure you that the last LabVIEW version you start was LV7 (if you have multiple versions of LV installed). I don't know if GOOP Wizard 1 is supported in LabVIEW7 (Endevo does not support this tool anymore), it was developed in LV 5 I think.
GOOP Wizard 2.0 or 2.0.2
Make sure GOOPWiz2.llb is copied into the \project folder. Works on LabVIEW 6.0.2, 6.1 and 7.
GOOP Wizard 2.1
Run the setup.vi from the installation files of the toolkit. Works on LabVIEW 6.0.2, 6.1 and 7.
GOOP Inheritance Toolkit
Run the setup.vi from the installation files of the toolkit. works on LabVIEW 6.1 and LabVIEW 7
Regards,
Mattias Ericsson
Main developer of the GOOP Wiza
rd 2 and GOOP Inheritance Toolkit.

Upgrade Mathscript LabVIEW 2009

Hello
I have developped an application in LabVIEW 8.6 that
contains a large MathScript node. it's time to upgrade to LabVIEW 2009
and i am facing problems in that. I have the Mathscript RT Module
installed and activated on my computer.
I should emphasize that
the application works perfectly in 8.6. After the first execution in
2009 version, i got 2 run-time errors:
-90031 : "unknown output
variable". The variable is of string type. it's pointed in a red dot
(see picture). I have never seen that red dot before...
another
error in another node: -20104: input parameter have at least one NaN
element. What's a NaN element? this error occurs in a line that looks
like A=median(B) where B is a row vector.
also in this second
node, i have a lot of output variables pointed in red dots, the string
outputs and some of the double precision as well.
What
are the requirements to upgrade to LabVIEW 2009, as far as MathScript
is concerned? are there issues to be considered? major changes i should
be aware of?
Thank you very much
Sam
Solved!
Go to Solution.
Attachments:
error Mathscript.JPG ‏10 KB

Thanks Jattas
i am still confused about the coercion dots but since they don't necessarily indicate problems with the code, i'll keep the focus on something else to begin with. i beleive i should look for solutions for the whole upgrade. What i did not mention in the first post (because not sure if related to Mathscript) is the error messages i have on saving the VI before quitting, i also got those messages while loading the VI.
Attached are 3 messages that appeared (Please see pics). The result is obviously a borken arrow:VI failed to complie, Mathscript node failed to compile.
that would be a nice discussion with NI support but it's hard to explain these things on the phone. i am gathering every information that might be relevent for the migration.
thanks again
Attachments:
error1.JPG ‏12 KB
error2.JPG ‏13 KB
error3.JPG ‏12 KB

My hp pavilion dv6000 have a problems of sound drivers when i install a window seven (7)

my hp pavilion have a problems of sound drivers when i installed window seven.So i need supported so as to obtain a sound in my laptop

Hi:
Please read the helpful windows 7 upgrade guide for dv6000 models at the link below.
http://h30434.www3.hp.com/t5/Notebook-Operating-Systems-and-Software/Windows-7-Upgrade-Guide-for-dv6...

When I loaded labview 8.5 my pcmcia device stopped talking.

The system recognizes the device, but will not communicate with it. Somehow the port communications are now dead. I unsitalled LABView and the problem still persists. Prior to the installation the PCMCIA device always worked flawlessly and it contiues to function normally in other computers. This is a custom OEM device developed by my company. Any suggestions as to how i might regain communications?

When you installed LabVIEW 8.5, were any of the device drivers installed? If so, which drivers?
-Bob

Upgrade drivers when upgrading to LabView v.8?

Similar Messages

Maybe you are looking for