Keithley 6221 pilot - upgrade to labview 2009 to 2012

Similar Questions

• Problems with PCI-7811R after upgrade from LabVIEW

  Hello

  I have been using a PCI-7811R under LabVIEW 8.2 for quite awhile without difficulties. However, I just upgraded to LabVIEW 2009 and it seems to have stopped working.

  I tried to run old code (that worked before) and I get the attached error. I try and locate the PCI-7811R in MAX ver 4.7.7 and he's not here.

  Any suggestions?

  Gary

  
  

• Tap the Navigation Palette missing in LabVIEW 2009 Panel

  Hello

  I developed an application using LabVIEW 8.6 with the touch panel module and a TPC-2012 (Windows CE). I've now upgraded to LabVIEW 2009 and I'm trying to run my code in a TPC-2512 (XP Embedded), but the 'Touch Panel Navigation Palette' I used previously to be found in the new facility. In my view, there is a new range of "Navigation controls" in 2009, but I would like to avoid having to re - design my app with new controls.

  8.6 navigation controls are no longer supported in LabVIEW 2009 or have I missed something? The TPC is displayed in the Project Explorer and MAX, and I'm able to deploy and run applications on it. But the old vi navigation do not work and as I mentioned before, the palette is not even appear when you try to change the vi on the development computer.

  Any help would be appreciated.

  Thank you

  Hello

  The navigation screw touch panel are not displayed to the top, because you are currently using the TPC-2512. If you take a look in the Help file on the Navigation, it states: 'installed with: Touch Panel Module.» This topic can not match its corresponding palette in LabVIEW depending on your operating system, or the licensed products and the target. "I checked this with both LabVIEW 8.6 and LabVIEW 2009 targets. Due to the different architectures, you get a different set of palette (Windows CE vs XP Embedded).

  -Zach

• LabVIEW 2009 32 bit does not not on xp 64-bit

  Hi all

  I tried to upgrade to LabVIEW 2009 LabVIEW 8.6 on the XP machine 64-bit windows. After about a deletion of 2 hours of installation 8.6 and later of LV 2009 it turns out that the device drivers are not compatible with a 64-bit computer. At the launch of LabVIEW 2009 (32-bit), an error box is displayed indicating that it is corrupt or missing files and to fix this using the control panel etc. I tried this and still the same error occurs and LV refuses to start.

  All license files are correct and the components are enabled.

  Someone knows how to fix this? Or do I go back to 8.6 and cancel my subscription?

  Second, I use a firewire camera and was informed that neither IMAQ legacy are more supported and go to ni.com/ifo and enter legacy1394 to see how to download drivers for that etc. I find myself on a page that says no "authorized".

  Any help appreciated gratefully.

  Dear Leeser

  Since 2006, National Instruments has annually released a new version of LabVIEW each month of August in order to establish a more predictable release schedule. This allows users to better plan the new developments and improvements for future versions of LabVIEW. In addition, this year, NOR changed the name of the product to LabVIEW + year (for example, LabVIEW 2009) reflecting the year of the release and setting the stage for future annual editions of LabVIEW. Please see the following site for more information on this:

  http://www.NI.com/LabVIEW/product_lifecycle.htm

  What about Windows XP 64-bit it is not officially supported by hardware or software drivers. For a list of drivers who have been known to work, please see the link below:

  http://Joule.NI.com/nidu/CDs/fn/p/SN/N19: Windows.7809/lang/en

  Now with Windows Vista x 64 is a 32-bit compatibility of excellent "windows on windows" mode which allows our drivers work correctly. In regards to LabVIEW 2009, there is now a dedicated 64-bit version is recommended for use with 64-bit operating systems. Yet once Windows XP 64-bit is not officially supported.

  More details on the compatibility of Windows XP x 64 is located in the following article:

  http://digital.NI.com/public.nsf/allkb/C4EC0C87B6D70AA886256E61006568C8?OpenDocument

  I hope this helps to clarify some things.

  Kind regards

• Executable VI generating an error 222 on Keithley 2612 although his run correctly when starting labview 2009 directly

  Hi all

  I have a VI that works perfectly and I can control, a 2612 Keithley has for measurements of transistor.

  The VI run well when I realize it from the computer that has the Labview 2009 (XP OS) platform

  Equipment (IE Keithley 2612 A) is related to another computer that is not labview 2009.

  I installed the Run-time-engine 2009 (32-bit XP OS) on this computer.

  Then, I create an executable of my VI with the option 'build application.

  The executable VI starts normally on the computer, but when I run it, I get an error message from the Keithley 2612 (which wasn't the case when I ran the VI directly from the computer haing LabVIEW 2009 installed on it). The error message is 222 (ie the long parameter)

  I thought I did something wrong and I create an executable from an original VI of Keithley (IE without modification). I get the same error message.

  When I create an executable with the runtime engine 2009 included (because it is possible to do with LB 2009), I am geeting the same error message.

  So I need to check step after step, when the message arrives but

  Someone knows something about such a question?

  Thank you

  Hi all

  Just for those who might experience a similar problem.

  I found the solution after fighting all the possibilities.

  The source of the problem was (for some reason) that the country setting of the computer was wrong

  and decimals are written with one, instead of a point.

  As I correctly reset the country setting, stand-alone files work normally.

  Best regards

  Youki

• Xantrex HPD for LabVIEW 2009 pilot

  I saw there are other products OR with drivers for Xantrex HPD feeds.

  Someone at - it one that works for LabVIEW 2009 (or earlier)?

  Ok.  I have it.

  HyperTerminal has worked.

  He checked that port settings and command syntax is correct.

  ALL programs in LabVIEW examples do not have the function of VC to food.  When I hard coded the CR function after the order (also preprogrammed) it worked.  Xantrex (now Sorensen) manual do include SOME simple examples - you just know by experience (catch 22) how do.

  Also be noted that we need to send both a voltage and current definition commands because both are zero by default.  (If you send one, nothing SEEMS to happen because the other is 0).  That could also have been included in an example of beginning.

  THANKS for your help!

• convert elements using the DAQCard-6024E card to USB-6221using LabVIEW 2009

  I just got an old project, the VI has been primarily designed using the DAQCard-6024E map. Since we would be upgrading the equipment and the DAQCard-6024E serves not long. However, they want to keep the similar façade. I am trying to convert the drop-down menu that I can use with USB-6221 with Windows 7, but I don't know how. Can anyone help?

  Windows 7, NI USB-6221, LabVIEW 2009 sp1

  Hi smoothenigne007,

  After watching your upgrade.  All your writing VI should use the same task.  There is no need to close this task until the end of the program.  In addition, you can remove all the time because they do not allow the task close a loop.  I did a performance highlighted with your code and you can see that the first task was not allowed at the time wherever the data reached the second task.  When you try to create the second task, the error is generated.  Because you do not give me multiple writes to the same port there is no need to open and close the task each time.  Here is a link that will explain a little more about the DAQmx driver works.

  Getting Started With DAQ

  Kind regards

• Can I build an application with Labview 2009 for Windows 7?

  Hello

  I use Labview 2009 SP1 and the application builder 2009 SP1. If I install the app on win7 this message:

  Engine run LabVIEW depends on failure to upgrade (...) version 9.0.301, language {} code that is not in the distribution.

  Is it a problem with Windows 7, having two records of installation of 32 bit (C:\Program Files (x 86)) and 64 bit (C:\Program Files)?

  I had an application built on a XP machine and installed on a Windows 7 computer that was looking for the files in C:\Program Files when they were actually installed in C:\Program Files (x 86) - because it was 32-bit application.  After the installation I had to move the files to 1 place to another to make it work.

• Is there an Excel to TDM plugin for LabVIEW 2009

  I downloaded the Excel to TDM plugin and could not run. Dialog error usiReg said "this configuration file was created with a new version of the ICU and can not be used with the software you have installed." I installed LabVIEW 2009 SP1 and the .net version is 4.0. Y at - it another version of the 9

  the plugin I can use? Is there something else I can do, or am I just out of luck, until I update?

  Hello

  the functionality to open Excel files has been added to the ICU starting with version 1.8. However, the ICU in the manner described above upgrade you will register to use ExcelTDM and make it available through the _openWithRoot.vi in LabVIEW 2009. Simply install or DIAdem 2010 NI LabVIEW 2010 as a demo version.

  Please see also the comments from readers on the page of ExcelTDM use, a client has requested the use of using Excel in older versions of DIAdem:

  ExcelTDM use

  Greetings,

  Uwe

• Purchase / upgrade of LabVIEW with more Sound and Vibration

  Hi, supporters OR Forums,

  I'm new in LabVIEW but I'm working on a project that needs to use LabVIEW in these toolkits: DAQmx, PID and then Sound and Vibration Control.

  In order to experience on the vibrations, I need to use screws of Suite Sound and Vibration, which was not purchased in my Institute. We had the license for LabVIEW 2009 SP1. Unfortunately, I have a VI file written in LabVIEW 2010 my partner. According to the records of view VI, there is a lack of following screws:

  -SVFA Power Spectrum.vi
  -Application Directory.vi
  -SVT FFT .vi spectrum (Mag-Phase)
  -Frequency response (Mag Phase) .vi SVT
  -SVFA amplitude and Phase Real and Imaginary.vi
  -SVL get spectrum subset.vi
  -SVT UFFT58 write.vi
  -SVT UFFT58 write record 6 vi
  -SVT HFFT58 close file.vi

  I would like to confirm if these screws are supplied in the detroit and Viration Suite or / and other toolkits. If all of them can be found in the following Sound and Vibration, what I have to do is to buy the offer away from NOR, is it not? How much should I pay for this Suite.

  On the other hand, if we upgrade from LabVIEW 2011 (which is said to be able to deal with better timer - for the function of data acquisition), how much in total so also buy us more Sound and Vibration 2011.

  In comparison, which of the above two options is preferable in terms of price.

  For your information, I am working on my thesis at University in this means we would like to have a university degree.

  Plesea give me ideas on this subject. I'm sorry if my post is not fit to be posted here but I sent 2 emails to NI Germany (1 for the customer on the Web page Service NOR) and 1 in the Sales Department, but there is no response after more than 3 weeks.

  Thank you very much.

  Kind regards.

  Thinh Vo

  Hi thinhvo,

  All of these VI are included in the Suite Sound and Vibration, which means it's the only additional package that you would need to buy.  On the site OR in the States, the Sound and Vibration Measurement Suite USD $4119 costs.  Since I'm an applications engineer, I'm not in a position where I can advise you on the price, and I am sorry to say that it will be easier for you to contact your engineers in sales in Germany (I guess you are in Germany).  You may have better luck calling into lines of support rather than by e-mail.

  Thank you

  Lisa

• cRIO-9073 not appearing is not in devices and Labview 2009 targets

  In MAX, I show the following: a cRIO-9073 with NOR-RIO 3.0.0 installed. My system software has NEITHER-RIO 3.0. In LabView 2009, when I try and add the cRIO to my project in LabView 2009 in New-> targets and devices, I don't have a list in time real CompactRIO and my cRIO does not appear. I tried to add manually with its IP address, but it does not work either. I've updated the cRIO to LabView real-time 9.0 software.

  Is there other software that I need to update on the cRIO so that it is visible in LabView 2009? Do I need a new version of NOR-RIO?

  Thanks for any help.

  Todd

  I upgraded from NEITHER RIO NOR-RIO 3.2.1 3.0 and LabView 2009 seems happy.

  See you soon,.

  Todd

• LabView 2009 (64-bit) IMAQ GetScreenSize?

  Hello

  No one attempted to use of the vi in LabView 2009 64-bit GetScreenSize yet?

  Is not executable more? We have replacements?

  Thank you

  Hello

  IMAQ GetScreenSize is obsolete. Refer to KB: compatibility library when upgrading from old Versions of Module Vision Development.

  Instead of this function, you can use Display.Primary Workspace or Monitors Display.All property node.

  Andrey.

• Impossible to find the field read and write VI in labview 2009

  where is the field point to read and write VI in labview 2009

  According to the version of LV, BT pallets can be sensitive to the context. Try to create a project and add a fieldpoint target to the project.  Right-click on the target of FP in your project and select new > vi.  Now FP functions should appear

• Switch Executive stops working after LabVIEW 2009 installed.

  I just installed LabVIEW 2009 and now Switch Executive 3.0 does not work.

  NISE open session vi returns 0 instead of the valid session ID. It does now with LabVIEW 8.6.1 too.

  Everything looks OK in MAX.

  Any suggestions?

  Hi Pirkola,

  I'll try to replicate that.  I understand it is a returned 0 for a session ID.  Is there an error returned as well?

  Thank you!

  Chad Erickson

  Switch Product Support Engineer

  NOR - USA

• Failed to retrieve the DIAdem DataFinder research data, using data-finder toolkit LabVIEW 2009

  I am facing problem to retrieve the DIAdem Datafinder data.

  At first, I developed this project in LabVIEW 2010. But because of a problem that I met in LabVIEW 2010, I thougth to work on the project in LabVIEW 2009.

  Then, I reused the project that I created using LV 2010 using option economy for the previous version.

  When I tried to retrieve the data from the tiara using data finder toolkit. I got a 305505 warning. Please see the attached message of Warninig.

  But I have not seen this warning while I was working in LabVIEW 2010 and also, I was able to get the data from the tiara.

  Please suggest me a way to solve this problem.

  Hi Nanda,
  There is a bug when using the SDK use in combination with DataFinder Toolkit 2009.
  This bug is already fixed in LabVIEW 2010 and use SDK 2010. But as you said there is another question in LabVIEW 2010, forcing you to LV 2009.
  I suggest you use LabVIEW 2009 with use SDK 2009 and DataFinder Toolkit 2009 and instead to use the "Waveform.vi results" to read the search results, I would recommend to use the screw storage. I spread your example VI and it attached to this message. You will still see the dialog box to search for "lvStorage.dll" but it will automatically disappear and the VI works anyway because in this case LabVIEW will find the dll itself.
  My extended VI uses the '_openWithRoot.vi' to open a file with a different use than CT or PDM. This VI is also described in the following knowledge base article: http://zone.ni.com/devzone/cda/epd/p/id/4181
  With LabVIEW 2010 use support has been enhanced and fully integrated in the standard palette of storage screws. So in LabVIEW 2010, you can replace the "_openWithRoot.vi" with the 'Open Data Storage.vi' standard but with LabVIEW 2010, you can also use "Waveforms.vi results" to read the search results.

  I hope this helps.

  Kind regards
  Eva