Labview 2010 no device found

I am upgrading a windows XP 32 bit lab to a Windows 7 64 bit Enterprise lab using Tektronix TDS1012C-EDU Scopes. When I launch LabView 2010 the software cannot find the scopes and display a message "No devices found". The scopes show up in device manage and in windows devices. I am have upgraded to the latest version of NI-Visa and installed all the critical updates for Labview 2010. The scopes are connected via a USB connection. I contacted Tektronix and they had me upgrade the bios in the scopes. Still nothing. Any help is welcome.

Do you have National Instruments Measurement and Automation Explorer installed (if you installed the NI drivers it should have been)? If yes, look to see if it can see the instruments, and if it does, see if the names or aliases are what is expected in your program. Of course, if the USB are being used as serial ports adapters then you may not see them. If they are, then quite possibly the settings or comm port associations have changed.
Putnam
Certified LabVIEW Developer
Senior Test Engineer
Currently using LV 6.1-LabVIEW 2012, RT8.5
LabVIEW Champion

Similar Messages

  • I do not have the daq assistant vi on my labview 2010 and have found no drivers for it what should i do

    I do not have the daq assistant vi on my labview 2010 and have found no drivers for it. I downloaded the service pack but  that did not have it either what should i do.

    Hi Youzhang He, 
    Did you install LabVIEW first on your PXIe 8102 before the drivers?  Most likely, you're missing LabVIEW support for your DAQmx drivers. Fortunately, this is an easy fix. What you should do is open Add/Remove Programs, select National Instruments Software, select Uninstall/Repair. In the window that pops up listing NI software, select NI-DAQmx 9.x and select Modify. In the window that appears, expand Application Development Support and select to install LabVIEW support.  From here complete the install process and restart your system.  LabVIEW support should be installed and DAQ Assistant should appear in your palette.
    Allie

  • NI TestStand 2010 Installer not found

    Hi,
    I am trying to deploy a TestStand system but it keeps saying
    Insert the CD or browse to the location where the following component is located:
    NI TestStand 2010 Installer.
    The last directory this component was found was:
    C:\Documents and Settings\smcmahon\Desktop
    I have inserted all four labVIEW 2010 CD's 1/3, 2/3, 3/3 and Devices and drivers. 
    I also tried downloading TestStand2010Patch276751 and TestStand4.0.1f1Patch236977 to see if these would fix the issue, whcih they did not.
    I suspect that I have downloaded an update to the desktop, unfortunately I recently erased all my downloads and cleared my desktop.
    Does anyone know what file I need to download?
    Thanks,
    Sean

    Hi Sean,
    Thanks for using the NI Forums!
    The reason you are seeing this error message is due to the TestStand engine not being cached on the PC. What I would recommend is to download TestStand 2010 evaluation ( https://lumen.ni.com/nicif/us/teststand3/content.xhtml ) if you do not have the installer discs or from ni.com/src if you are entitled to the files. The patch applications will only contain the patches rather than the full installers.
    When you try and build the installer, browse to the location of the downloaded TestStand installer.
    Please let me know how you get on!
    Ashish Naik
    Field Sales Engineer
    National Instruments UK

  • DAQmx support for LabVIEW 2010

    FYI to those downloading LabVIEW 2010 from NI web site:
    After Installing LabVIEW 2010 (download from web site), I noticed that there is no support for DAQmx (i.e.. VI libraries) in NI_DeviceDrivers-February2010 DVD (my latest copy).  Your have to download and install DAQmx 9.2 drivers (the first to include LabVIEW 2010 support).
    Additionally, If you were using Traditional NI-DAQ (Legacy) 7.4.4 VIs in a prior version of LabVIEW, you must do one of the following:
          1. Uninstall current Traditional NI-DAQ (Legacy) 7.4.4 installation and re-install after completing LabVIEW 2010 installation.
              Reason: Traditional NI-DAQ (Legacy) installs support only for the latest version of LabVIEW found on the system.
    Or
          2. Copy the the "<previous LabVIEW>\vi.lib\Daq" directory and all it contents to a new "<LabVIEW 2010\vi.lib\Daq directory.  This way you can use Traditional NI-DAQ in both versions of LabVIEW.

    I didn't have DVDs, I had to download.
    Yes it was a mess.  The device driver download took forever (NI can't help that).  The installation took beyond forever (what else can be done?). 
    I was disappointed that I had to do all of this backing up of legacy folders and restoring them after installing the device drivers.  Why does NI always have device drivers and toolkits install to the latest version of Labview only?  Why couldn't they leave the legacy stuff alone??  I still use LV2009 and wanted to try LV2010.  This involved a whole lot of trouble and time. 
    NI needs to provide a much easier way to upgrade, while still allowing previous versions to work without modification.  Most people who upgrade will not completely abandon the older versions.
    - tbob
    Inventor of the WORM Global

  • No Bluetooth Device found after BIOS Update

    Product Name and No.: HP dv6516tx
    Operating System: Windows XP
    Error Message: No Bluetooth device found
    Changes Made: Updated BIOS to most recent version F. 5A
    System Information:
    OS Name Microsoft Windows XP Professional
    Version 5.1.2600 Service Pack 3 Build 2600
    OS Manufacturer Microsoft Corporation
    System Name UDAYMITTAL-PC
    System Manufacturer Hewlett-Packard
    System Model HP Pavilion dv6500 Notebook PC
    System Type X86-based PC
    Processor x86 Family 6 Model 15 Stepping 13 GenuineIntel ~1496 Mhz
    BIOS Version/Date Hewlett-Packard F.5A, 3/22/2010
    SMBIOS Version 2.4
    Windows Directory C:\WINDOWS
    System Directory C:\WINDOWS\system32
    Boot Device \Device\HarddiskVolume1
    Locale United States
    Hardware Abstraction Layer Version = "5.1.2600.5687 (xpsp_sp3_qfe.080930-1426)"
    User Name UDAYMITTAL-PC\Uday Mittal
    Time Zone India Standard Time
    Total Physical Memory 4,096.00 MB
    Available Physical Memory 2.23 GB
    Total Virtual Memory 2.00 GB
    Available Virtual Memory 1.96 GB
    Page File Space 4.83 GB
    Page File C:\pagefile.sys
    Problem Description:
    Yesterday I updated my laptop's BIOS to F 5A - latest available on HP Website. Since then I have lost the bluetooth functionality, which was wroking just fine prior to the update. Now the system doesn't find a bluetooth device.
    What I have already done:
    1. Switched back to previous versions of BIOS (available on HP Website coz I didn't note the BIOS version before I updated it). - That didn't work.
    2. Reseated the wireless card - Didn't work.
    3. Manually checked the connection of bluetooth module to the motherboard - Connection was fine but it still didn't work.
    4. Uninstalled the bluetooth driver and reinstalled it (HP integrated module WIDCOM) - still didn't work
    5. Installed HP Wireless Agent - Didn't work
    6. Installed HP Integrated module driver along with HP Wireless Agent - Didn't work
    7. Installed Ubuntu to check if its recognizing the device - Even its not recognizing the device which it used to do earlier.
    8. Sadly there's no BIOS setting in Setup which I can change to correct the bluetooth behaviour (Phoenix BIOS with limited interface).
    After all the research, I am posting this because I am unable to find a sloution to this problem on my own. I request the members to please help.
    Uday

    I got the bluetooth working. Had to dismantle the laptop and found that a small switch was loose.

  • Application crashes in Windows 7 64bit made in Labview 2010 sp1 f2 with Fault module name%3A lvrt.dll%2C version 10.0.0.4033 and exception code c0000005

    I build an application exe and then its installer along with run time environment.
    The installers instals the application correctly but when I try to execute the application, I get an error that application has crashed and Windows must close it down or search for solutions online with this additional information for the crash. 
    Problem signature:
    Problem Event Name: APPCRASH
    Application Name: AGMS.exe
    Application Version: 1.3.0.0
    Application Timestamp: 4c24e8f5
    Fault Module Name: lvrt.dll
    Fault Module Version: 10.0.0.4033
    Fault Module Timestamp: 4c9273f4
    Exception Code: c0000005
    Exception Offset: 00005310
    OS Version: 6.1.7601.2.1.0.256.1
    Locale ID: 1033
    Additional Information 1: 0a9e
    Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
    Additional Information 3: 0a9e
    Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
    Read our privacy statement online:
    http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
    If the online privacy statement is not available, please read our privacy statement offline:
    C:\Windows\system32\en-US\erofflps.txt
    I am using labview 2010 sp1 32 bit on a 64-bit machine, with the following specs
    Operating System: Windows 7 Home Premium 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.130318-1533)
    Language: English (Regional Setting: English)
    System Manufacturer: Dell Inc.
    System Model: Dell System XPS L502X
    BIOS: Default System BIOS
    Processor: Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz (8 CPUs), ~2.0GHz
    Memory: 8192MB RAM
    Available OS Memory: 8106MB RAM
    Page File: 3457MB used, 12753MB available
    Windows Dir: C:\Windows
    DirectX Version: DirectX 11
    DX Setup Parameters: Not found
    User DPI Setting: Using System DPI
    System DPI Setting: 96 DPI (100 percent)
    DWM DPI Scaling: Disabled
    DxDiag Version: 6.01.7601.17514 32bit Unicode
    The exe /application runs fine on my PC but when I try to run it on another PC it crashes. The other PC has similar specs as given below
    Operating System: Windows 7 Ultimate 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.140303-2144)
    Language: English (Regional Setting: English)
    System Manufacturer: LENOVO
    System Model: HuronRiver Platform
    BIOS: Default System BIOS
    Processor: Intel(R) Core(TM) i3-2330M CPU @ 2.20GHz (4 CPUs), ~2.2GHz
    Memory: 4096MB RAM
    Available OS Memory: 4010MB RAM
    Page File: 1359MB used, 6658MB available
    Windows Dir: C:\Windows
    DirectX Version: DirectX 11
    DX Setup Parameters: Not found
    User DPI Setting: Using System DPI
    System DPI Setting: 96 DPI (100 percent)
    DWM DPI Scaling: Disabled
    DxDiag Version: 6.01.7601.17514 32bit Unicode
    I tried another machine, 64 bit of course, as I want to deploy my application on a 64bit PC, but still got the same problem.
    This other machine was from HP, iCore 3 (4 CPUs) 2.2GHz, 4GB RAM and running Windows Professional 64 bit.
    Now as I see it, it could be a Run-time environment mis-match error.
    For this I tried installing a 64 bit LVRTE from NI, but still no sucess.
    I checked DEP, for all 3 PCs and it was set to the following
    Turn on DEP for essential Windows programs and services only (first option).
    I am confused. I can not find a solution for this and it is really frustrating.

    But I am assuming that when I make the installer, the 32-bit Run Time Engine is appened with the installer, as show below
    Since from the picture you can see its including the support installers from '\Program Files (x86)\'
    The application runs queries to fetch data from database in SQL server 2008, and for that I am using a Microsoft SQL Native Client 2008 R2 64 bit ( this is the only version that installs on either PC, even the one on which I developed my LV Application).
    I am not using any driver, only toolkits for reports - and for that I un-checked the "Remove unused polymorphic VI instances" when making the executable, otherwise LV throws up an exception that share variable are not being included.
    Yes I did reboot every time after I ran the installation.
    Still getting the same error.

  • Report Generation toolkit for labview 2010

    H All.
    I'm looking to download the report generation toolkit for labview 2010. When I proceed to download the toolkit from the national instrumnets website, it says that i need to labview 2011 or later in order to install it.
    Is there a version of this report generation toollkit for labview 2010 and can someone provide a link maybe??.
    Thanks for reading.
    Solved!
    Go to Solution.

    Try this: [Link removed, NI software downloads can be found on ni.com/downloads, the LabVIEW 2010 Report Generation Toolkit is available to customers with Standard Service Program here: http://joule.ni.com/nidu/cds/view/p/id/3247/lang/en, other customers may contact NI directly]
    Beginner? Try LabVIEW Basics
    Sharing bits of code? Try Snippets or LAVA Code Capture Tool
    Have you tried Quick Drop?, Visit QD Community.

  • 3D graphs cause LabVIEW 2010 to hang

    I've been using LabVIEW  2010 for several weeks without any problems, but today I noticed that it doesn't work at all with anything related to the 3D picture control. Today was the first time that I tried doing anything with the 3D picture tool since installing LV 2010. Dropping any of the 3D Graphs on the front panel of a new VI causes LV2010 to hang. (By hang, I mean the VI window remains open but most UI things no longer work.  Right-clicking on the window does not show a context menu.  The main menu doesn't work.  The X button does not close the VI front panel window nor the diagram window. Control-Q does not cause LabVIEW to quit.  I have to kill the process in Task Manager.)  It is the same story with just a plaing 3D picture indicator.  Also, the solarsystem.vi example does not work either.  The problems start as soon as I open the solarsystem.vi.  After killing LV with Task Manager and relaunching LV10, I do not get the LV message about a previous crash.
    The problem I am talking about is for LabVIEW 2010 with the f2 patch running in Win7.  I am actually running it using VMware Fusion 3.1.3 on a 2009 Mac Pro running Lion.  The Mac drivers are all updated.  Since it is VMware Fusion machine, the video driver on the Windows side is part of the VMware Tools installation, which is up to date.
    After searching the forums, I've tried all the other potential solutions I could find:  1) repaired LV2010 using add/remove programs and 2) tried using the compatibilty mode settings to turn off Aero. 
    Interestingly, 3D graphs work fine on the Mac side for LV2010 for Mac.  
    Even more insterestingly, 3D graphs work fine on Win7 for LV 8.5, which I still have installed.  The fact that it works fine for LV 8.5 would seem to indicate that Lion did not introduce the problem and that the video driver is working fine.
    Solved!
    Go to Solution.

    Yep, it's the same virtual machine.  I set it up almost 2 years ago and it has been extremely stable.  Both LabVIEW 8.5 and 2010 have been perfectly happy on it.  It's a great way to do LabVIEW on Win7.  I didn't notice any changes at all to the VM when I upgraded from Snow Leopard to Lion.  I installed LabVIEW 2010 before upgrading to Lion, but I didn't have occasion to work with 3D controls before the upgrade to Lion so I don't know if it would have worked on Snow Leopard.  The Mac versions of both LabVIEW 8.5 and LabVIEW 2010 also work great on the both Snow Leopard and Lion.
    I happen to have an XP virtual machine too, but I haven't installed LabVIEW there.  Let me know if that would be a worthwhile test.
    You might check with Marc Page--unless he has already upgraded again I think he has a similar machine to mine.
    The video card is the original stock:
    NVIDIA GeForce GT 120:
    Chipset Model: NVIDIA GeForce GT 120
    Type: GPU
    Bus: PCIe
    Slot: Slot-1
    PCIe Lane Width: x16
    VRAM (Total): 512 MB
    Vendor: NVIDIA (0x10de)
    Device ID: 0x0640
    Revision ID: 0x00a1
    ROM Revision: 3386
    Displays:
    Cinema HD Display:
    Resolution: 2560 x 1600
    Pixel Depth: 32-Bit Color (ARGB8888)
    Main Display: Yes
    Mirror: Off
    Online: Yes
    Rotation: Supported
    Display Connector:
    Status: No Display Connected

  • Strange problem of calling library function node in labview 2010 and 2011

    one year ago,I develop a program to usb device data and it works well,in labview 8.6 or 2009(win xp).Recently, When I test
    the program in labview 2010 and labview 2011(win xp).,the program always crash immediately.I check the program and find main
    problem is in call library function node. In my program,I use labview 2009 library for the USBExpress driver for
    Silicon Labs USB MCU's from:https://decibel.ni.com/content/docs/DOC-9522,for example, 2 functions SI_OPEN and SI_READ
    can not work well.
    the header definition of SI_OPEN and SI_READ is:
    SI_STATUS WINAPI SI_Open(
    DWORD dwDevice,
    HANDLE* cyHandle
    SI_STATUS WINAPI SI_Read(
    HANDLE cyHandle,
    LPVOID lpBuffer,
    DWORD dwBytesToRead,
    LPDWORD lpdwBytesReturned,
    OVERLAPPED* o = NULL
    the SI_STATUS is equivalent to int type.
    orignally, for HANDLE * in SI_Open, the parameter type in call library function node is numeric, data format is unsigned 32 bit integer ,and pass pointer to value.
    for HANDLE in SI_Read, the parameter type in call library function node is numeric, data format is unsigned 32 bit integer ,and pass value.The program works well in labview 8.6&2009,however,crash in labview 2010 &2011.
    later,I debug the program, for HANDLE *, I choose parameter type in call library function node as adapt to type, data format is point to Handles.for HANDLE, I choose parameter type in call library function node as adapt to type, data format is Handles by Value.Crash not happend in labview 2010&2011,however,it cannot read any data from from USB device correctly as before.I can not find the reason.
    Dear friends,I need your help to answer the problem. Thank you.

    Based on the help page it looks like it should execute asynchronously.
    The thing in the description that leads me to believe they execute asynchronously is that you can configure the library to run as a multi-threaded operation.
    Please take a look here to see the difference between synchronous and asynchronous execution.
    Since the code even has the ability to be multi-threaded, you can consider it as running in parallel to your other code.
    Any data returned is passed to the thread that called that function.
    Cory K

  • No Device Found [Canon Vixia HF20]

    My HD camcorder does not show up when I try to connect to "Media". Yes, I am connected via USB but I continually get "No Device Found."

    I used "Device Manager" to look at the specific USB port and it showed "Mass Storage Device". I have yet to see it in Windows Explorer.
    This is what I did...
    I plugged a USB drive into the port to see which port in Device Manager I was working with. It showed up as a "Mass Storage Device" -- good. I removed the device, plugged in the camcorder to the same port and refreshed Device Manager. It could be that it did not refresh properly and still tagged the port with Mass Storage Device.
    I would try it again to verify but I have put the camera away as I am getting ready to go on a trip. I was hoping to download everything off the camera before I left but I'll just have to tackle this problem once I return.
    [Update ... April 26, 2010]
    My Canon Vixia HF20 comes with a software bundle from Pixela Corp. Supposedly, this software allows me to download movies from the camcorder to my computer. Well, it doesn't work on Windows 7. I downloaded and installed the latest "updater" from Pixela, which is supposed to fix the problem of interfacing with Windows 7. That didn't work either. So now I have this absolutely useless camcorder. Thanks Canon! You can be sure I'll never touch another one of your camcorders again!

  • LabVIEW 2010 in-placeness crash bug

    [cross-posted to LAVA]
    I found an odd LabVIEW 2010 bug that will cause a hard crash. The bug appears to be related to how LabVIEW operates on data in-place and some interaction between clusters, arrays, and the Aum Array Elements node. It's hard to describe verbally, so I'll just draw you a picture 
      LabVIEW 2010 CRASH.vi (16.56K) 

    No crash on my system: LV2010, W7 64-bit, Pentium E5200
    a.lia-user-name-link[href="/t5/user/viewprofilepage/user-id/88938"] {color: black;} a.lia-user-name-link[href="/t5/user/viewprofilepage/user-id/88938"]:after {content: '';} .jrd-sig {height: 80px; overflow: visible;} .jrd-sig-deploy {float:left; opacity:0.2;} .jrd-sig-img {float:right; opacity:0.2;} .jrd-sig-img:hover {opacity:0.8;} .jrd-sig-deploy:hover {opacity:0.8;}

  • Labview 2010 crashes XP while looking for webserver

    Hi,
    I am using a Windows 7 laptop with LV 2010 to compile my 32-bit executable.  I've copied it to my target Windows XP, SP3 computer and after running it for a short while it rebooted the computer automatically (I believe the reboot was caused by a BSOD).
    I've gone into the Windows Event Viewer and there is an event that says "Labview information:  Error: 404 "Not Found" for "national instruments/ni-rpc/interface/eadfc80d-1e6f-425b-8986-12ccef98f646/ncalrpc", file "c:/program files/national instruments/shared/ni webserver/www/national instruments/ni-rpc/interface/eadfc80d-1e6f-425b-8986-12ccef98f646/ncalrpc": Can't access URL     ."
    I'm attaching a jpg of the Event in case I typed it incorrectly.  There is another post that mentions this error but there is no resolution and the discussion went in a different direction:  http://forums.ni.com/t5/LabVIEW/LabVIEW-2010-unstable-on-Windows-7/m-p/1247366/highlight/true
    Neither my Win 7 development laptop or my target Win XP system have this www folder.
    Has anyone seen this before or know the cause?  Thanks.
    Steve
    Attachments:
    Event Viewer small.jpg ‏69 KB

    Altenbach,
    Thanks for the quick reply.
    Yes, the time stamp of this error coincides with the crash.  I guess I assumed that it caused the crash because I see about 20-25 instances of it in the Event Viewer.  Immediately before these errors appear there are two instances of the NI Configuration Manager with the Description saying "Opening configuration database".
    This only happened on time and I have not been able to reproduce it again.
    I'll need to explain to my customer why this Error has appeared so many times in the Event Viewer, and also how I can get it to not happen again.  Do you have any suggestions?  Once I isolate this error and prevent it from happening again then I can monitor the computer for future crashes.
    Thanks.
    Steve

  • LabVIEW 2010 unstable on Windows 7

    I am finding that LabVIEW 2010 is fairly unstable on Windows 7 Ultimate system.
    LV stopped working several times, LV tells me that it stopped working, looks for a solution and then shuts down. Like just a few minutes ago, shortly after system power up.
    Several times it just closes all of the Windows and terminates without any message or error displayed.  Didn't even say goodbye.
    I have even had one BSOD (which is hard to do on Win 7) almost immediately after an application was built and run. Didn't happen again when app was run again and built again.
    I have only observed these problems with LV. All other applications have been running fine over the last month without unusual errors or misbehaver.
    The system is only 1 month old. It is fairly clean with minimal software installed.
    I don't know how much data on these problems that NI is capturing automatically. I haven't seen my system request permission to send problem reports to NI.
    Has anyone else seen similar behavior with LV and Win 7 Ultimate?

    I too am extremely (that's a total understatement) displeased with the behavior of Labview 2010 under Windows 7.
    I get frequent crashes, some with recovery/log/.error message, some where Labview just exits. One minute I'm editing my code with 7 windows up; the next I'm staring at an empty desktop.
    I too have started saving my work every few seconds. It's a royal pain in the ass.
    I have turned in NUMEROUS bug reports, including samples of code that cause Labview to crash. MANY of them are related to typedefs. I just found another one and will be turning in that bug report within minutes. In this case I have a typedef (NOT strict) that contains only a combo listbox. If I right-click on the combo listbox, Labview silently exits and does no recovery or logging when started back up.
    I have lost SOOOOOO much time trying to create code while fighting numerous Labview 2010 issues. The most egregious (to me) is that I have a control (I *want* it to be a strict typdef) that when I drop it on the Labview block diagram, Labview crashes. Yes this has been reported. I had to change the control from 'strict typedef' to 'control' to use it. The result is that every time I have to modify it (it's a work in progress) I heve to go thru my code and change over 60 occurrences of that control. By hand. If it was a typedef, I would change it ONCE.
    I have a customer I'm developing Labview code for; I find it both personally and professionally embarassing to be missing deadlines for delivery, and blaming Labview instead of myself. But I have 3 pages of bug reports online with NI; each one cost me between an hour and 3-4 days of time. Many of them required me to redesign code I'd alrady written to avoid using constructs in Labview that simply don't work.
    I'm glad to know I'm not alone - but absolutely dismayed that the code base for Labview 2010 is so buggy under Windows 7; it may be buggy on every platform, but that's all I'm using.
    NI tech support has been helpful; but only to a point. They routinely generate correction requests based on my bug reports; not one has resulted in a patch from engineering to date.
    I've been a software engineer for over 35 years. This is probably the 2nd worst experience with an IDE that I've had. The first was with a Sun product that was supposed to generate user interfaces; it simply was crap. Labview is dismayingly similar. If I'd elected to write this application in C I'd not only be finished, but it would have taken 6 months less on the calendar. Some of that is due simply to the way you have to construct and enter code in Labview; but in my case, most is due to failures of Labview to work as documentd, or to failures in the Labview documentation to explain what Labview is really doing (yes, I've turned those in too).
    Here's an example of a Labview crash: open this VI and right-click on the listbox on the front panel. Make sure you do NOT have any other Labview code open at the time...!
    Gary Sloane
    SB/US Engineering Inc.
    Attachments:
    HL2_CAL_DISPLAY.ctl ‏5 KB

  • Using LabVIEW 7.1 and LabVIEW 2010 on the same PC (Windows XP)

    I have LabVIEW 7.1 on a Windows XP 32-bit PC and we plan to upgrade to LabVIEW 2010 soon. A lot of our software is using Traditional DAQ, DAQmx and DeviceNet. We need to use both versions of LabVIEW for some time on the same PC. Is this possible at all?
    I installed an evaluation 2010 version and now I don't have DAQ and DeviceNet in LabVIEW 7.1. Any suggestions will be very helpful.
    Thanks, Nick
    Solved!
    Go to Solution.

    For what it is worth, I tried having multiple versions of LabVIEW on the same PC.  If you are (very) careful, it is possible to do so, as long as you are only doing development work, i.e. you don't try and install LabVIEW drivers.  However, as I've discovered to my great sorrow (which involved installing and removing various versions of LabVIEW on the same machine probably 5-8 times, eventually leading to wiping the machine and installing WinXP all over again, then only one version of LabVIEW), if you want to actually run your code, particularly if it does anything with hardware, you need to stick to one version!
    There's another "gotcha" for those of us working with "older" versions (namely before 2009, though one can "trick" 8.6 if you're careful) -- Windows 7 doesn't "play well" with the older software!
    So my development machine runs Windows 7.  I have a VM of Windows XP in which I installed LabVIEW 7, which I use for my "legacy" work -- I use the Win 7 machine for LabVIEW 8.6, 2009, and 2010 development (and only development, see above).
    The machine that got "rebuilt", where I wanted to run LabVIEW code for various hardware and potentially various LabVIEW versions, I did a really nutty thing -- I created a quadruple-boot PC!  (It really is a triple-booter, as the Windows 7 system, which is the key step, is "hidden").  To make this work properly, I needed three hard drives in the machine (one for each OS -- I might have figured out how to put two XPs on a single drive, but since I already had the disks, one-OS-per-disk seemed easier).  I'm using Windows 7's Boot Loader to give me the startup choice of which system to use (the message says something like "System for Hardware A", "System for Hardware B", "Test System").  True, you need to do a Restart, but since you're going to be collecting data, it's not such a bad idea to start with a "fresh machine".
    [I did think about doing this with Virtual Machines, which would have been much simpler, but I didn't have "virtual drivers" for the hardware!  One piece was actually a USB device, but the other was a proprietary device that plugged into my PC ...]

  • Labview 2010 and internet toolkit 2012

    We at our company are using labview 2010 for creating quick test applications.
    I've recently created a program that uses features that are linked to the internet toolkit.
    When creating an installer and installing the application on another system it didn't work, i later found out that you need internet toolkit installed in order to use these features.
    In order to install the toolkit i have to install labview. Is it also possible to just have the runtime engine installed (2010 version) together with the interInternet toolkit 2012 in order to use these functions?

    Like mentioned before the internet toolkit does not have to be installed on the target PC. If VI where missing from the executable, it will not run at all and return an error stating it is missing VI's. What I think happens is that the toolkit VI's are in an error state but since you do not stop the loop on an error the loop will just continue to run and because of the error it is not doing anything. You can do a couple of things:
    1. Debug the executable. How that is done is described in the following KB:
    http://digital.ni.com/public.nsf/allkb/8DA679805915DE40862572D5007B2F70?OpenDocument
    When you are connected to the running executable you can use the normal debugging methods like probes to see what happens. Especially the error line would be good to monitor.
    2. Let the loop stop on an error. The executable will then show the error (if any) in the error cluster.
    3. Monitor the error line within the loop to see if there is an error occurring.
    Let me know what the outcome of one of these actions is.
    Regards,
    Rik Prins, CLD
    Applications Engineering Specialist Northern Europe, National Instruments
    Please tip your answer providers with kudos.
    Any attached Code is provided As Is. It has not been tested or validated as a product, for use in a deployed application or system,
    or for use in hazardous environments. You assume all risks for use of the Code and use of the Code is subject
    to the Sample Code License Terms which can be found at: http://ni.com/samplecodelicense

Maybe you are looking for