LabVIEW 2010 E4406 1XEVDO/CDMA2k pilot

Similar Questions

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

• Is there a Module NXT for LabVIEW 2010

  Is there a Module NXT for LabVIEW 2010?  If not, are there plans to bring a available and if so, when?

  Hello

  I found a link to a download for the module 2010 here.

  I hope this helps.

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

• programming LabVIEW 2010 how to scxi 1102 and 1503 cascade in scxi 1101 case

  How to scxi 1102 and 1503 cascading if 1101 scxi for labview 2010 programming

  

  just test ok
  
  LabVIEW 2010 latest

• 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

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

• Where the range of network flow in LabVIEW 2010?

  I know that this palette "exists" (since I can with the right button on a thread of endpoint and network flow Palette appear in the menu), but (so far), I have not found on the pallets of LabVIEW 2010 function.  Where is it hidden?

  BS

  Under the "Data Communication" on my machine.

• 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

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

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