Labview 2010 8.1 Windows executables

Similar Questions

• Is it possible to build a project with Labview 2010 on a Windows XP system, which is useful for a system with windows 7 on it?

  Hello

  I intend to use Labview 2010 in no time.

  But before I go to use it I have a few questions.

  1. I know that it is possible to run Labview 2010 in an XP environment. But is it also possible, when running Labview 2010 on an XP system, to build a project for a version that is useful in a Windows 7 environment?
  2. Or should I run Labview 2010, when I want to build a project that is useful on a Windows 7 system, on a system with Windows 7?

  Please give me some information.

  I hope to hear from you soon.

  Kind regards

  Kenny

  the file (.exe) is also compatible with xp and seven, no need to change anything...

  Concerning

• LabVIEW 2010 executable runs under windows xp, but not in windows 7

  Hi all.  Here's the situation.  We have Labview 2010 professional development on a computer running Windows XP.  I designed all my programs with this PC.  We have another PC which has Windows 7 with no Labview.  I'm trying to make the executable files and put them on the Windows 7 PC.  I have been here three executable files and move the Windows 7 PC.  One of the executables work correctly, the other two interrupt immediately.

  Executables that stop have temperature limits and the program is apparently seen a low temperature and so stop the program.  Yet, these same executables work fine on the PC under Windows XP.  What seems to be the case, is that the program is expelled before allowing himself read the temperatures.  I use the modules of the series C 9213 and 9211 with 9188 Chassis.   My programs are showing 0 for temperatures.  Well, it's certainly in the low temp limit, so the program stops.  However, she should not do this.  I know there is little delay with the playback of all thermcouples in 9213 and 9211 modules, but this was not a problem with Windows XP.  Even if the program starts from scratch on the XP PC, temperatures immediately appear, or appear after a second or two.  Yes, I've rarely seen a temp 0 on the XP PC, but the program doesn't stop; Give it a second or two and the time appear.  Why is it that happens in Windows 7?

  An executable that works has no measure of temperature.  It uses only 9481 modules and run the solenoids at a rate of about 0.2 seconds.  This executable works fine on both computers.

  So what - this on the modules of temperature reading that is causing a problem in Windows 7?

  Other installation data :

  -The XP PC has the updates Labview 2010 is compatible with

  -The PC Win 7 not the latest updates of Labview 2010 there are has compatibility problems.  National Instruments has given me the compatible components, and they has several levels down by the most recent (for example MAX vs MAX 5.6 v14.0)

  
  

• 'LabVIEW 2010'.exe as a windows service running

  Hi all

  years, I wrote an application with LabVIEW 7.1 and transformed into a Windows NT Service according to this NOR-tutorial.

  Now, I have a similar use case and I wanted to do the same thing with an application built in LabVIEW 2010.

  Somehow, it does not work and I still get the error 62.

  I built a simple demo application once with LV7.1 and once with LV2010.

  I was able to use this service when they built with LV7.1 but not the version of LV2010 (client-side I always used LV2010). He has no problem with the connection to the server or using the port.

  I'd rather not rebuilt the app with LV7.1 because it is not really small. I consider that if there is no work around for this problem.

  Anyone any ideas?

  I really appreciate anyone's help

  See you soon,.

  Christian

  As well as information for those who execute it in the same problems:

  SC.exe toured BUT not as described in this tutorial. You must create a wrapper function as described on this Homepage. Services created with sc.exe need a BeginService() and an EndService() method otherwise it wont let you install.

  This image shows you how I did it. The CIN AnyService.dll of charges that loads server.dll.

  Kudos to Kuan Chen

  

  See you soon,.

  \c

• Running the latest Labview 2010 on new computers (Windows 7) but who have the older/more older material NI ELVIS

  We are running the latest Labview 2010 on new computers (Windows 7) but have more older/more old material NI ELVIS (NI ELVIS I?).

  LabVIEW works very well and the device drivers are installed.

  What NI ELVIS software move us?

  The latest version indicates that it is for ELVIS II and III hardware.

  Thank you

  Hi Tom,

  I'm sorry, I read your first post completely backward.  It's the pilot , you should try.  Sorry for the confusion!

  Kind regards

• You use HP 4156 instrument with Labview 2010 in Windows 7

  We recently bought Labview 2010 for Windows 7 and some software porting, we had on Labview 6.  These programs of control of two instruments: HP (Agilent) 4156A parameter Analyzer and the Keithley 7001 switch system.  When I looked for the drivers of instruments for these two systems, they were no longer available for Labview 2009 and associated NI-VISA 3.2 driver is not compatible with Windows 7.  You have any suggestions on how we can run Labview 2010 on Windows 7 with the ch (Agilent) 4156 A and Keithley 7001?

  A pilot in 2009 can be loaded in 2010 and this is the minimum VISA version, you can use. You need not even the driver of instruments most recent. Just run your existing code.

• The PSC-2000 is programmable with LabVIEW 2010 SP1 / Real Time 10.0.1?

  I have a PSC-2000 camera I want to use for a small project.  I see on the site OR that it is said»

• "Support for LabVIEW Real-time 8.5.1 and earlier" and "Support for Windows Vista and earlier versions.  It means that I can not use the latest version of LabVIEW (2010 SP1) with time real (version 10.0.1) running on a Windows 7 computer?  If not, what version of LabVIEW, real-time and operating system do I need?

When I tried to add a new target under LabVIEW 2010 SP1, the PSC-2000 was not among the choices.

As the support NOR documents indicate, you need LV version 8.5.1 or earlier to program the cFP-20xx devices family.  Version 8.5.1 of LabVIEW does not work under Win7.  You will need Windows Vista or something earlier like XP.

• LabVIEW 2010 help control Source code...

  I'm trying to set up Tortoise SVN to work with LabVIEW 2010.  I was able to get lvmerge and lvcompare to work by adding them to the list of programs within the turtle, but leave in LabVIEW there is a section to configure the source control I have a problem with.  Under "Configure Source code control" there is a drop down to the name of the Source control provider.  There is only one option: < none=""> .  I looked into it a bit online and found that LabVIEW running in Windows searches the registry database for a list of the sources of control.  I don't know exactly what he's looking for in the registry, but maybe I could make an entry in the registry to get LabVIEW see Tortoise SVN.  Anyone had this problem or any experience with this?

  To use the NCC options provided by LabVIEW you will need from a provider. For subversion, it is possible with the PushOK SVN SCC plugin.

  If you install you can checkin/checkout directly from the LabVIEW project environment.

  If you really like TortoiseSVN discover the Tortoise SVN integration made by JKI-software.

  Tone

  PS there is nothing special about 2010 in the integration of the CSC.

• Error 7 when opening the file auto-LabVIEW 2010

  I use Open/create/replace file in LabVIEW 2010 to open a text file.  It works fine until I have compile the code.  Then, I get error 7. I tried the paths that are similar to the following, but no doesn't work.

  c:\\file.txt

  c:\\file.txt

  c:\------\file.txt

  Thank you

  You must get the path to the .exe file.  Then remove the name of .vi and the .exe.  Then build the path from there to get your .txt file.  The way you have it, you treat the .exe to a folder rather than a file.  The text is no file not part of the .exe, you cannot create a path that includes the name of the .exe.

  Why my executable does not work when you use the constant path of the current VI?

• Is the combo box drop-down "Targets" in LabVIEW 2010?

  Guy of OR,.

  In LabVIEW 2010, I installed the touch screen module but 'Touch Panel corresponding project' does not appear in the list of "Targets" of the "Getting Started" initial LV window. The Add/Remove dialog box confirms that the module is installed... Is - can be changed?

  Thanks in advance

  I think that the Touch Panel project should be added to the drop target when you install the Touch Panel Module.  As this isn't the case, I think it's a bug.  Thanks for pointing out that, and I will file a request for corrective measures to get changed for the next editions of LabVIEW.

  Kind regards

  Elizabeth K.

  National Instruments | Sales engineer | www.NI.com/support

• LabVIEW 2010 crash when calling user32.dll

  Interesting LabVIEW 2010 'characteristic', I discovered this morning.

  Attached are two identical screws, a registered in 2010 and a registered in 2009.  These screws have been written specifically to demonstrate the bug, I came across this afternoon.  Each VI when it is run needs you to find a specific program (window) opened in Microsoft Windows and bring it to the foreground.  It is based on 'user32.dll' to perform this operation.  It also allows you to specify the calling convention for the function call.

  LV 2009, calling convention works without error.  However, in LV 2010 the calling convention of the function must be "stdcall (WINAPI)" and not the default value of 'C '.  If the calling convention is 'C' LabVIEW hangs and then closes without warning.

  If you happen to have LV 2009 and 2010 LV on your computer, I would like to hear if this phenomenon is duplicated so that I can identify if the bug is LV 2010 related or is more specific to my personal configuration.

  Thank you

  ~ David

  221113 Return

  COLD LAKE with the calling convention incorrect siliently crash LabVIEW can. LabVIEW 8.5 2009 could adjust the convention to call at run time if the user has selected the wrong option. In 2010, it is no longer a case. More information is located in the 59KB14WI knowledge base Workaround: Use the correct calling convention Reported Version: 2010 32-bit    Solved Version: N/A    Added the: 2010-07-23

  Release notes for 2010.

• Excel 2010 and labview 2010

  I think that this may have been covered, but if anyone noticed all the differences in the properties of the ActiveX or methods in labview when working with excellent 2007 versus excel 2010? I know at one point Microsoft had changed a few things excellent 97-2003 "and instead select 'value' in your method, you must now choose"value 2". Is the real wait even for excel 2010? I am currently using excel 2007 at work and 2000 at home, and when I opened my code at home, my call nodes 'have the wrong son' still all required entries are correct. Same code on excel 2007; lot of son and the code will be run. I'm just curious to know if anyone has tried to use labview 2010 and excel 2010 together and made a work? I'm opening 1 workbook and wrote to 4 different excel sheets using Windows XP, excel 2007 at work and have windows 7 and want to use excel 2010 home and prefers no problem or to all the least know what are potential problems. Sorry if this confusion. I think it's the best way I can explain that I have MY head wrapped around it yet.  I do not want to write the same code twice for different versions of excel. (write and test at home, then re - write at work)

  http://digital.NI.com/public.nsf/allkb/177D720A428CA72B862567EC00757F0C

  This is an example of what I'm talking about

  Myke,

  While I don't have excel 2010 available to try and see, Microsoft (and MSDN) has a huge amount of information about calls in all versions of Excel.

  Excel 2010 development resources: http://msdn.microsoft.com/en-us/library/ee658205 (office.14) .aspx

  Excel 2007 development resources: http://msdn.microsoft.com/en-us/library/bb979621(v=office.12).aspx

  I hope that helps you start, because I don't have access to excel 2010. Let me know if it works for you.

  Kind regards

  Kyle Mozdzyn

  Engineering applications

  National Instruments

• Files reading TDMS problem in Labview 2010, created in 2009, error-2503

  I did my measurements on my laptop with Labview 2009 installed.

  The file format has been TDMS v1.0

  I can read these files with the TDMS files viewer and I am able to do analysis on my laptop.

  On my desk I have Labview 2010.

  If I run the vi in Labview 2010 analysis, I get the following-2503 error: specified file does not have the PDM file format standards.

  What's wrong?

  I can open the file in Excel with the add-in.

  I've included a tdms file created on my laptop in Labview 2009

  For this problem, it's a bug in LabVIEW 2010 (not in previous versions of LabVIEW), sorry for the inconvenience. While the side R & D to fix this problem, we also a workaround solution, but perhaps a little more complicated:

  (1) Please use older version of LabVIEW (like 2009 or 8.6) for defragement file by using the node TDMS defragment, if it works fine, you can then open it défragmentée TDMS in LabVIEW 2010.

  (2) if the PDM defragment returns an error, then you can always find your defragmened files in the temp directory of Windows, but under a different filename (randomly generated), you can type "%Temp%" Run windows to open your temporary file.

• LabVIEW 2010 E4406 1XEVDO/CDMA2k pilot

  We recently bought labview 2010. I installed the drivers for Agilent E4406A VSA but it only installed the drivers for the GSM and WCDMA. Our product is running on CDMA2K (1xRTT) and EVDO-RA. How can I get labview 2010 drivers for it so that I can controll and acquire the data of my instrumnet. I was previously using Labview 8.6 and its drivers worked well and all of the code I have already came out on 8.6 drivers are great. The drivers that I downloaded from labview instrument driver 2010 search are Agilent PSA (W-CDMA) series and Agilent PSA (GSM). No other options for EVDO or CDMA2k appear. Help, please.

  Shad

  The dll can be anywhere on your system, perhaps in the system of windows or system32 directory

• Language setting bad compile App with labview 2010 SP1

  Hello

  I got this when I create an application with LabVIEW 2010 SP1

  My OS is a Windows XP English with a regional setting to English (Canada)

  Y at - it a fix for this problem, that some were.

  

  After a repair of my SP1 installing LabVIEW 2010 I had the correct behavior

  I think something was wrong in the installation of runtime LabVIEW 2010