Installing LabVIEW 8.2.1 with DAQmx 8.0 on Suse 10.3 for Linux.

Similar Questions

• Must install Labview App on cFP2200 with feature plug & play for measurement modules

  Hello

  I am trying to install a monitoring software on cFP2200 devices. This software uses anywhere from 1 to 8 modules of I-102. I want to be able to deploy my build to the fieldpoint without having to know in advance how many modules will be there.

  My plan to achieve this was to design my application to assume that all modules HAVE 102 were available to read to go, throw an error that I catch and delete if they weren't. It works perfectly in tests of interpreted code. I managed to disconnect the field point, 102 HAVE devices to different locations than before, and my software could find them and ignore the slots where were connected HAVE 102 s.

  A question is asked now when I try to deploy a compiled version of this app on the fieldpoint. When I do that, I get a "conflict resolution" popup that lists all of the I-102 s who are not connected at deployment time. I have to choose 'cancel the deployment' or 'Skip deployment' in these cases. So I am unable to find I-102 modules if I move them to one location other than when they were connected to install or put new ones in.

  We will put these modules at customer sites and we want the ability to develop so that it contains some 102 HAVE more or less as the customer systems expand and contract. Under the current situation, I have to re - install the software manually whenever they move a module that is not really an acceptable long term solution.

  Are there ideas about how to address the issue?

  Thank you

  Kelsey Golden

  I just realized that the "conflict resolution" window really means nothing. As long as I select 'Skip', I can always move the modules or new install! It makes me wonder what the conflict resolution is intended in the first place if he is not actually stop me using the modules later.

  For all those who want plug-and-play in the future, my solution essentially try to read all possible addresses and ignore those throwing errors basically seems to be the way to do this. Just ignore the stupid conflict resolution window. I of course hope that the fact that I can still install modules in locations where conflicts implicitly he wasn't their installation is not a defect that NEITHER patch later outside.

• SMU 8135 cannot ping pc when installing labview

  HJ. Help me

  my laptop do not install labview 2012 can ping with SMU 8135 but labview installed on my laptop cannot ping with SMU 8135. I don't understand

  Hi ffefef,

  Could you explain in more detail the question, you encounter?

  Thank you

• How to develop the final application exe file that will work on PC not installed labview

  Hello

  I developed a labview application (I request manufacturers/builders and professional license).

  I generate the final exe file by the tools of-> built Application exe of VI-> fact file

  But this the application exe file runs only on machines installed labview. His works do not on the other PC.

  For the execution of the other PC I have to do.

  Hello Ramji,

  As you said, EXE is created by you and its nning ruou fine on the PC where you created such as LabVIEW is present there.

  So for LV CE, please create an installer and Add Installer/additional software required by your EXE.

  Look at the link for reference.

  http://www.NI.com/white-paper/5406/en

  Kind regards

  Leila

  CLD

• How to install LabView Run-Time 2011 silently without removing daqMX?

  I'm trying to silently install LabView 2011 execution using the Agent HP Client Automation, formerly RADIA.  I tested successfully, however, the systems that installed daqMX have, I find that the silent installation program removes daqMX automatically.  Is there a command line argument or register defining who can defeat this behavior so that daqMX remains installed when the silent installation program is finished?  Thank you very much for your help!

  Hey EricJay,.

  I'm not very familiar with the Agent, HP Client Automation, but the silent installation should not automatically uninstall the DAQmx drivers. You can compare the process HP Client Automation Agent uses with a silent installation using command-line arguments, as described here. Another possibility could be any conflict check that the HP Client Automation Agent performs. As described here, we do not recommend installing DAQmx drivers until LabVIEW or LabVIEW runtime engine are installed to prevent contradictions or missing references. If HP Client Automation Agent is to detect these potential conflicts so we can uninstall the DAQmx drivers for conflict prevention. I hope this helps!

  -Ryan S.

• LabVIEW 8.0 works with IMAQ USB? If so, should which version I install?

  Hi, guys.

  LabVIEW 8.0 works with IMAQ USB? If so, should which version I install?

  Thank you very much!

  Have you seen this.

  Years for your questions, I guess it will be better for you if you stick to a single thread.

• problem with MAX after installing LABVIEW 10

  Hello everyone, I have a serious problem I installed labview 10 yesterday on 2 laptops, one of them works perfectly, however, the other gave me a two erros

  1.http://digital.ni.com/public.nsf/allkb/6CA56E2DDBCCA06086257591006141EE

  2. http://digital.ni.com/public.nsf/allkb/F24AA9FB6A3A0E9D86257539006141BE

  I tried the solutions above in the link, but it was all futile. can someone please suggest me what would be the problem? I had already LV8.0 on the laptop which is the cause of the problem. I tried to re - install the disk driver given

  for me by NEITHER, but no luck.

  When I started the laptop for the 1st time, there was a mistake in saying DOS command prompt: DATABASE ERROR and I cancelled the error!

  In addition, Labview works fine, its only MAX who has problems. is there a way I can only MAX to uninstall and reinstall? Please help me...

  Thank you

  Sorry CrackJack

  Try this one http://digital.ni.com/public.nsf/allkb/86256F0E001DA9FF86256FFD005B827C?OpenDocument    

• Update of LabVIEW, which updated 9.8 DAQmx. SMU-8101 to 9.4 DAQmx. Difficult how?

  I am trying to use MAX to navigate up to a DAQ SMU-6363 connected to my SMU - 8101 RT connected to my local network, but encounters an error: "error-88716 occurred at communication·entre·dispositifs·de·sante·personnels, or the possible reasons: the requested operation failed because a driver on the local and remote system versions are different."  Updated the driver for versions on both systems are the same.  "Remote system: 172.17.2.65, Incompatible driver: NI - DAQmx Device Driver 9.4.0f0.

  This problem occurred recently when I've updated LabVIEW on my development computer to the latest version (2013 f2), which updated DAQmx on my development for v9.8 machine.

  While I'm not quite there, I intend to analyze an audio signal using the SMU-6363.  I guess I'll need to have all the properly information in MAX before I have a hope of implementation in LabVIEW.

  I am now updating the drivers / firmware on the SMU help system full of communication between my development system and the SMU system and having problems.

  During an attempted 'Select all to install' for 'NOR-DAQmx 9.8.0"in the" Add/Remove software"on the SMU-8101 thanks MAX system, I get the error:

  ---------------------------

  Cannot continue following unresolved dependencies:

  Acquiring dynamic signals 9.8.0 requires linguistic support for LabVIEW RT 1.0.0.3
  Acquiring dynamic signals 9.8.0 requires Intel 8254 x Ethernet Driver 5.0
  Counter/Timer 9.8.0 requires linguistic support for LabVIEW RT 1.0.0.3
  Counter/Timer 9.8.0 requires Intel 8254 x Ethernet Driver 5.0
  NOR-DAQmx 9.8.0 requires linguistic support for LabVIEW RT 1.0.0.3
  NOR-DAQmx 9.8.0 requires Intel 8254 x Ethernet Driver 5.0
  Multifunction 9.8.0 requires linguistic support for LabVIEW RT 1.0.0.3
  9.8.0 multifunction data acquisition requires Intel 8254 x Ethernet Driver 5.0
  CompactDAQ 9.8.0 requires linguistic support for LabVIEW RT 1.0.0.3
  CompactDAQ 9.8.0 requires Intel 8254 x Ethernet Driver 5.0
  CompactDAQ 9.8.0 requires LabVIEW time real 12.0.0
  E/s digital industrial 9.8.0 requires linguistic support for LabVIEW RT 1.0.0.3
  E/s digital industrial 9.8.0 requires Intel 8254 x Ethernet Driver 5.0
  Analog output series 9.8.0 requires linguistic support for LabVIEW RT 1.0.0.3
  Analog output series 9.8.0 requires Intel 8254 x Ethernet Driver 5.0
  OR-653 x 9.8.0 requires linguistic support for LabVIEW RT 1.0.0.3
  OR-653 x 9.8.0 requires Intel 8254 x Ethernet Driver 5.0
  SC Express 9.8.0 requires linguistic support for LabVIEW RT 1.0.0.3
  SC Express 9.8.0 requires Intel 8254 x Ethernet Driver 5.0

  ---------------------------

  This dialog box does not offer an option to automatically try to download or to locate the missing packets.  Research online revealed no obvious statement upgrade for my particular case.

  I downloaded and installed v9.8 DAQmx as well as RealTime 2013 module on my development machine, and am trying to download the 4 GB device drivers.

  Is there a suggested method for the SMU-8101 software update / firmware must match that of my development machine that does not require me trying decrypt and download the packages manually?

  I've never worked with the SMU (or any remote system) with LabVIEW front and wait it would be an easy fix for someone more experienced in this.

  Owen

  AHA!

  OK, that explains it.  You actually have LabVIEW 2011 on target (SMU-8101) but you have LabVIEW 2013 on the host.  You have all the required software installed on the host computer, but there are conflicts between the required versions of the software on the controller itself compared to what you're trying to install now.  You have 3 ways to do this:

  (1) the cleaner to proceed is to keep track of all the software components that you have installed (version is not important) and then UNINSTALL all the controller software, and then REINSTALL your software (leaving MAX select the latest versions of everything).  This ensures that you'll get the latest components of software.

  (2) the 'simpler' wat to proceed is to pass by and "update" symbolizes all the components with an icon 'Bang' (yellow triangle with an exclamation point) to upgrade/reinstall the latest version found on the host - the icon of 'bang' software currently installed on the target, but more recent versions exist on the host computer.  Version does not update without user intervention, even if the other components require more recent versions.  This lump all your versions later, that's what want the latest version of DAQmx.

  (3) nuclear option - reformat your controller and reinstall all software.  This is not recommended, but this option always exists.

  -Danny

• 2009 with DAQmx Installer

  We distributed an integrated application that uses DAQmx 8.x and LabVIEW 8.6 for several years.  I'll call the application MyApp 2.8.  We are working on a new version that uses LV 2009 and DAQmx 9.x, which we will call 3.5 MyApp.  When build us and deploy a Setup program for MyApp 3.5, then try to use it on a computer that already has 2.8 installed MyApp, the installer complains about dependencies and said that the two DAQmx 8.x and MyApp 2.8 must be uninstalled first.  I spoke NOR cela briefly and told me that DAQmx 9 was a pretty radical overhaul that required this change.

  It's annoying and slow for us, but almost untenable for our customers.  First of all, MyApp MyApp 3.5 and 2.8 are compatible, and we prefer to leave MyApp 2.8 installed as a backup as people get used to 3.5.  If the customer needs:
  Uninstall MyApp 2.8

  Uninstall DAQmx 8.9

  Install MyApp 3.5 with DAQmx 9.0

  Reinstall 2.8 MyApp (as if they can still find the disc!)

  Far too many steps and complications.  In addition, it is not really necessary.  If the runtime for 2009 is already installed on the computer (for some reason any), you can simply copy the MyApp 3.5 on the computer and it will run with DAQmx 8.9.  But this only postpones the problem, because at some point the customer will upgrade once again, and we will have forgotten that they were installed with a workaround, and...

  The really frustrating part is setup for MyApp 3.5 refuses to install until MyApp 2.8 is uninstalled.   While we have proven that MyApp 2.8 will work very well with DAQmx 9.0.

  Is anyone else noticing this problem?  Has anyone found any better workaround?  Is the same problem when we jumped 2009 and returned with 2010 and the last DAQmx?

  Thank you

  DaveT

  DaveT,

  You're right - for this aspect of the problem - my proposed solution won't help. At the price of a larger Setup program, including the full version of DAQmx probably will give the upgrade experience you want. If the web download size is a concern, perhaps you could provide two builds of your product - with the acquisition of complete data (for those of you who have your old product) and with smaller data acquisition (for those who do a clean install)?

  In addition, certain registry keys to remove the dependency I guess hacking is sort of an option, but it probably isn't the type of solution you are looking for. (We are currently researching the addition of some extra features in the uninstall program OR allow without taking account of certain dependencies, but nothing is currently available).

  Kind regards

  -WesW

• Timing embedded with Daqmx on PCI-6132

  Hello

  My colleague and I are trying to make a program Labview which starts a timer when the first trigger (sensor) is struck and stop the timer when the second trigger (sensor) is reached in 2012. We currently have a program for her, but this program was not sufficiently precise. Also the current program is using the DAQ assistant, but we would like to replace with daqmx triggering. We have also tried to use the OnboardClock on the PCI-6132, but still could not do the work programme.

  Is there anyone who knows how to do this and could explain it?

  (In the attachment is the current program)

  Thanks in advance,

  Tommy van Geest

  Hello Tommy.

  You can share your current code?

• With a sampling of the data with DAQMX, error-200279 occurs when making 2d array dbl

  Hello

  I did a system of simple analog voltage with DAQMX data acquisition.

  It is made for reading of capacitance, where output capacitance value out of a circuit in the periodic voltage signal.

  What I want is to get data from four capacitors simultaneously through four channels, using samples n n (dbl 2d).

  The structure of my VI is almost similar with examples of continuous sampling of voltage in LabView, with the exception of a few other calculations in the loop.

  And for the synchronization of the trigger, I've corrected the edge of release with the external signal from the capacitance reading circuit.

  Version no. 1 has a channel for data input voltage. Version n ° 2 has four channels for the input data.

  While ver.1 can get accurate reading of four capacitors circuit data each (a single channel at a time),.

  ver.2 acquires four channels of data, with a single thin data channel, all the others were wrong.

  I saw a 200279 error occur in the DAQMX read part 2d dbl, so I tried increasing the buffers by changing the sampling frequency or the number of samples, but it wasn't everything.

  I rose for most of the forums with the 200279 error, but the solution would not work on mine.

  Anyone can find the problem? I will attach my screws it may include a bit of Korean language, but most of them are in English, shouldn't be too hard to recognize. Sorry for the inconvenience.

  Oh I forgot, my DAQ is NI USB-6259, and it works in Win XP sp3 and LabView 8.6.

  Thank you.

  Hello Azurenight,

  The 6259 is a DAQ card of the M Series Multiplexed, which means that it is not possible to sample each signal at the same instant, rather the channels are all sent through the ADC even and must be sampled in order. More information on this can be found here:

  LabVIEW Help: Multiplexing compared with simultaneous sampling

  http://zone.NI.com/reference/en-XX/help/370466W-01/mxcncpts/multisimulsamp/

  It may still be possible to get the data you need with the card you have - could you give more information about the maximum eligible period between samples on different channels?

  If you require * real * simultaneous sampling, you will probably need different hardware.

  Kind regards

• 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

• Strange delay on starting an exe with DAQmx

  I see a very strange delay when launching a program that loads a LabVIEW generated DLL that uses DAQmx. I also see the same thing on a LabVIEW EXE and maybe on a loading a LabVIEW VI that calls the DLL LabVIEW. The funniest, it is this delay only occurs when the sensors are connected. In this case, I use two 4462 s with approximately 50 feet of cable with a bit of connections between the two and accels IEPE. I don't see a delay when the sensors directly connected with a few feet of cable, or when the sensors are not connected to the cable.

  I will try to narrow the problem down to a particular card or a detector of tomorrow. The delay lasts 2 minutes and occurs before appears vi loading screen. At the launch of the program in C that loads the dll of LabVIEW on launch, basically I get no feedback, but the process appears in Task Manager. When you load a vi in LabVIEW to a project that calls the dll, I get a cursor busy until the loading screen screw rises. So the question is: what happens before that appears the VI loading screen?

  This is all before my code runs, so I don't see how any configuration software comes into play.

  Any thoughts?

  Chris

  
  

• Impossible to install labview 2012

  I try to install labview 2012 on my 64 bit Windows 7 system, but fails;

  Here are the symptoms:

  (1) I click setup.exe directly and it shows that:

  

  (2) if I run it with the administrator, it appears that:

  

  (3) I checked that I can execute another exe file...

  Thank you

  Hi Bestchun,

  It could be a damaged Setup file. Try to re - please download the installer of ni.com/downloads.

  I will follow this post, answer so if this does not work for you.

  N

• Install LabVIEW on Windows 7 X 64

  I try to install LabVIEW in NI Developer Suite third quarter 2009 on Windows 7 X 64 machine. The Setup program ends with an unexpected error. I can install LabWindows/CVI the same DVD on this machine.

  I resolved to myself. The solution is to run setup.exe on the installation disc is Windows Vista compatibility mode.