Code is compiled separately from LabVIEW 2010

Similar Questions

• 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

• NOR-DAQmx for LabView 2010 SP1

  I am looking for the installation of NOR-DAQmx for LabView 2010 64 bit SP1 package?

  Yes.  Do not change the destination directory.  The drivers will be add support for any version of LabVIEW, you installed from LabVIEW 2010.  This includes 32-bit and 64-bit versions.

• 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?

• Thread mode in LabVIEW 2010 bug?

  I had an application written in LabVIEW 2009 for a PSC-2220 who stopped working when it was converted in LabVIEW 2010, and I tracked down the problem to one thing: the software sets the mode of the Serial wire. Call this method simply disables all of the program. It works when you run from LabVIEW... but if you build an application to start it will not start. Remove the call to thread mode - and voila, the application runs as it should.

  -I can solve the problem easily by calling does not fashion wire method, but this isn't a solution due to the fact that I need to use the RS-422/485 port RS485 2-wire mode.

  I found a solution that I can live with... it does not explain what is wrong, but here's what I had to do to be able to run the init.vi serial port from outside vi.lib\Instr\ - which in turn allowed me to add the changes I need (set the thread mode) without having to edit a library function :

  I had to flatten, i.e.replace all of its report with their content... I could have tried the inline function, but did manually to be sure.

  This may indicate that something is wrong with the binding when the program is compiled with RT... but it happens without producing errors of conflict or anything either. A startup.exe is produced - but is not able to run.

• Extremely slow LabVIEW 2010 icon editor

  Working on a project of medium size in LabVIEW 2010.  Out of the blue icon editor is slowing down.  So slow that type in a character of text takes 20 seconds.  After closing, the editor he is about 3 to 5 second rule on everything that I do in LabVIEW.

  LabVIEW games restart things back to normal, until I open the icon editor.  No results of Subvi opening in this problem.  And this happens in any project or even if no project is open, and I'm trying to change the icon in a Subvi Untitled 1.

  Anyone else seen this behavior.  I really want to re - install LabVIEW 2010.

  Thank you

  I've not seen this behavior, and I really have no idea what could be the problem. As a solution, we can 'turn off' icon editor and force LabVIEW to use the old classic that is causing the problem to go, in my opinion. To do this, rename the following lv_icon.bak:

  [2010]\resource\plugins\lv_icon.vi LabVIEW

  This will completely ignore the code from the editor of icon and go directly to the editor of classic icons. You will lose a lot of the new functionality of the icon editor, but I'm guessing that this will make the downturn go away.

• 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

• I get the error indicating the niajel.dll missing for HSDIO in labVIEW 2010, can someone help how to solve this problem.

  I'm using LabVIEW 2010 and installed the drivers from device LV2010 and try to use the HSDIO functions, while setting the HSDIO function on the block diagram showing niajel.dll is missing, can someone help me fix this bug.

  I tried to uninstall and install not able to set several times.

  Hello. niajel.dll corresponds to the NOR-TClk, although NEITHER-HSDIO does not specifically use it. You use certain functions TClk?

  Also, what other PXI device driver are installed on the system? Could you give a report on the MAX system?

• How to sit interface with matlab 2010A and labview 2010

  I use tools of simulation interface 5.0 with matlab 2010A and labview 2010, I want to take my cue from matlab, labview but signal transfer, I am facing a problem. I want to know is there any compatibility issue in sit 5.0 or I do something wrong?
  photos of errors are attached.

  natasftw wrote:

  http://digital.NI.com/public.nsf/allkb/02F5FA55FC28BDE1862578A30071F975
  While it is for 2011, I doubt that they decided to remove 64-bit compatibility as they went forward as 64-bit has become more rather than less demand.  In this document,notes LabVIEW Simulation Interface Toolkit does not support 64 bit versions of MATLAB application software."

  The extent of the compatiblitly for 32 - bit, I'd take a peek at: http://digital.ni.com/public.nsf/allkb/D174674A91E5536286257428005C2426

  The OP's question was SIT support 64 - bit version of LabVIEW and 64-bit version of the MATLAB/Simulink itself, not the operating system software.

  Document in your second link is on a completely different topic to have API for LabVIEW and MATLAB/Simulink/RTW (well, mostly Simulink & RTW). Here is the relevant link for the 32-bit compatibility: http://digital.ni.com/public.nsf/allkb/049295038FF0EE2A86257A06006B2DAD is no SIT 64-bit.

  Other underlying issues is that Pharlap does not have a 64-bit version. Finally, simulations are better performed on some RTOS (embedded PXI) for a deterministic execution rather than PC operating systems.

  -BTC

• 9.30 NIDAQ drivers not install LabVIEW 2011 - example. Microsoft .com's in LabVIEW 2010 under vi.llb

  I just upgraded to LabVIEW 2011 without uninstalling LabVIEW 2010.  I downloaded the last set of drivers DAQmx 9.30.  I find that these drivers are installed in a DAQmx folder under the vi.llb of theLabVIEW 2010 and NOT in the vi.llb of LabVIEW 2011.  The DAQmx features do not appear on the menus and the existing instances are reported as 'cannot be compiled. How can I get the DAQmx functions to properly install LabVIEW 2011?

  You must DAQmx 9.4.

  9.4 DAQmx

• 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)

  
  

• HOWTO fix Labview 2010 delays

  My Labview 2010 causing huge delays ~ 30-40 years compiling and when using the restore function.

  It blocks the (useless) pc for its time.

  I tried several times now, but the work of development with this break is not possible.

  System: MS XP32, Athlon 64 3800 + with 2 GB of RAM is not recent, but clearly within the min. requirements: Pentium 4 and 1 GB

  The app is first written as LV 6.4/8.0 and use very less stuff express vi.

  HOWTO solve the problems of delay with LV coming 2010?

  1. do I need to rewrite my whole program express screws...

  2. can I disable certain features to reach LV 8.0 performance...

  3 do I need a faster cpu and more RAM...

  ((4 can I I restore this program to OR because of) a lack of compatibility and b) minimum requirements of evil

  BTW... can Labview be completely uninstalled at all...?

  Sorry to ask a little aggressive but this "program OR" cost me a couple of days now for nothing

  Tips in particular to Question 2 would be much appreciated...

  read it twice, I discovered a very interesting aspect now your answer Putnam... Thank you

  I think this indicates that the solution...

  sound in this line here...

  > Currently using LV 6.1 - LabVIEW 2009, RT8.5

  I'll go and reinstall 8.0 and available banks of LV and recommend seriously

  for all LV users do not update to LV 2010.

• LabVIEW 2010 local variable behavior

  HI -.

  I upgraded to LabVIEW 2010 of 2009SP1 and the attached sub that VI no longer works correctly.  It is a case of State machine structure that is called inside a loop.  I will put a Boolean variable true local, then on the next appeal when the case changes the variable has been reset to false. He has not done this in LV2009.

  Someone tell me immediately I have a race condition, but these local variables are not be written anywhere else, just in these separate cases.

  See the attached code, specifically, the local variable 'Activate' is to reset during the passage of the 'turn on' case for case "power."

  Anyone else seen elsewhere deliver, or can shed some light?

  I've corrected the VI by writing the value in each case, but this different behavior I wonder what are the other issues lurking in LV2010?

  Thank you

  This code looks more like a kind of a motor of Action that a state machine, but not quite.  It is called several times since a state machine, and he decides who will be the next State according to the entries.  Instead of using all local variables, I would use shift registers not initialized (Nothing cable on the left side).  They hold their value of one call to the other.  A case more will need to be added in this case.  An event of default without a name, which would set the initial values of all the shift registers.  Make the default case and does the same name.  It will be called first automatically because the shift register is not initialized, then the default value will be called.  Inside the default case, set all the shift fits to the desired values.  Next time the Subvi is called, these values will always be there.  As long as nothing is wired on the left side, everything is wired for the shift state register will be the next case called.

  See attached vi.  It's broken because I have this thread not to indicators.