Execution of Multisim with Labview

Similar Questions

• Deploy file. DLL for CompactRIO with LabView

  Hello

  I have compiled a DLL-file of SimulationX, and I want to deploy this file on a CompactRIO with LabView. How do I do that?

  Thanks in advance

  A correction, the x 900 cRIO and 908 x seem to use an x 86 CPU and execution Pharlap ETS. PharLap ETS allows you to run SOME Windows but by far not all DLLs, because it supports only a subset of the Windows API available on Windows 2000. So, if you have a controller of 908 x cRIO (900 x are very old and unlikely to be used these days) you MAY be able to deploy the DLLS on your cRIO system. To make sure that you check the DLL API not supported importation by the auditor of the DLL which can be downloaded for your version of LabVIEW specific here.

• Cannot bind to the shared object created with LabVIEW 2009

  I have problems referring to a shared library built from a LabVIEW VI under RHEL 5 with LabVIEW 2009.

  To illustrate the problem, I created a VI with a digital input and output that corresponds to a certain number. Then, I created a draft specification of build to create a shared library with a feature that makes use of this VI square. The shared object is created successfully (square.so).

  When I try to compile a test application written in C, that connects to this library, I get errors in the following link:

  cc  -I/usr/local/natinst/nidaqmxbase/include -I/usr/local/natinst/LabVIEW-2009/cintools build/square.so  test.c   -o test/usr/local/lib/liblvrtdark.so.9.0: undefined reference to `std::basic_istream >& std::basic_istream >::_M_extract(float&)@GLIBCXX_3.4.9'/usr/local/lib/liblvrtdark.so.9.0: undefined reference to `std::basic_istream >& std::basic_istream >::_M_extract(double&)@GLIBCXX_3.4.9'/usr/local/lib/liblvrtdark.so.9.0: undefined reference to `std::basic_istream >& std::basic_istream >::_M_extract(double&)@GLIBCXX_3.4.9'/usr/local/lib/liblvrtdark.so.9.0: undefined reference to `std::basic_ostream >& std::basic_ostream >::_M_insert(double)@GLIBCXX_3.4.9'/usr/local/lib/liblvrtdark.so.9.0: undefined reference to `std::basic_istream >& std::basic_istream >::_M_extract(float&)@GLIBCXX_3.4.9'/usr/local/lib/liblvrtdark.so.9.0: undefined reference to `std::basic_ostream >& std::basic_ostream >::_M_insert(double)@GLIBCXX_3.4.9'collect2: ld returned 1 exit statusmake: *** [test] Error 1
  

  Running ldd reveals that liblvrtdark.so.9.0 is used for the execution of labview.

  In order to investigate on what could be the cause of the problem, I have compiled the nidaqmx basic examples, and I don't have an error. Current running ldd as reveals that he uses liblvrtdark.so.8.2 for the view of laboratory, time of execution.

  My suspicion is that some components of labview are being compiled with gcc 3.4 while others are being compiled with gcc 4.1 (which is the default compiler in RHEL 5).

  Any ideas how I could fix the build errors?

  Thanks in advance for your suggestions.

  PS.

  I enclose a tar file with the source files and here are the details of the ldd:

  ldd build/square.so         linux-gate.so.1 =>  (0x008de000)        liblvrtdark.so.9.0 => /usr/local/lib/liblvrtdark.so.9.0 (0x00b9c000)        libc.so.6 => /lib/libc.so.6 (0x00110000)        libstdc++.so.6 => /usr/local/lib/LabVIEW-2009/patchlib/libstdc++.so.6 (0x009a7000)        libm.so.6 => /lib/libm.so.6 (0x00756000)        libdl.so.2 => /lib/libdl.so.2 (0x00256000)        libpthread.so.0 => /lib/libpthread.so.0 (0x0025a000)        /lib/ld-linux.so.2 (0x00b80000)        libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00272000)
  
  ldd /usr/local/natinst/nidaqmxbase/lib/libnidaqmxbase.so.3.3.0         linux-gate.so.1 =>  (0x00e50000)        libnidaqmxbaselv.so => /usr/local/lib/libnidaqmxbaselv.so (0x00248000)        libc.so.6 => /lib/libc.so.6 (0x00689000)        /lib/ld-linux.so.2 (0x00b80000)        liblvrtdark.so.8.2 => /usr/local/lib/liblvrtdark.so.8.2 (0x00e51000)        libdl.so.2 => /lib/libdl.so.2 (0x00813000)        libpthread.so.0 => /lib/libpthread.so.0 (0x001b0000)        libstdc++.so.5 => /usr/lib/libstdc++.so.5 (0x009c7000)        libm.so.6 => /lib/libm.so.6 (0x00b0a000)        libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x0050c000)
  

  Hi mimi,

  I'm happy to report that I managed to get the code to work. I have included some of the steps I experienced the problem in case it might help improve the documentation or future generations.

  In response to your question about the "error 1" reported by do, it's just an indication that detected a compiler error (it probably resembles the return code of the compiler).

  The errors ' undefined reference... @GLIBCXX_3.4.9 "have been narrowed down. The generated labview shared library, the square.so, links to /usr/local/lib/LabVIEW-2009/patchlib/libstdc++.so.6 which is a symlink to usr/local/lib/LabVIEW-2009/patchlib/libstdc++.so.6.0.9. I decided to compare this version of libstdc ++ that included with RHEL:

  strings /usr/local/lib/LabVIEW-2009/patchlib/libstdc++.so.6 | grep GLIBCXXGLIBCXX_3.4GLIBCXX_3.4.1GLIBCXX_3.4.2GLIBCXX_3.4.3GLIBCXX_3.4.4GLIBCXX_3.4.5GLIBCXX_3.4.6GLIBCXX_3.4.7GLIBCXX_3.4.8GLIBCXX_3.4.9GLIBCXX_FORCE_NEW
  

  strings /usr/lib/libstdc++.so.6 | grep GLIBCXXGLIBCXX_3.4GLIBCXX_3.4.1GLIBCXX_3.4.2GLIBCXX_3.4.3GLIBCXX_3.4.4GLIBCXX_3.4.5GLIBCXX_3.4.6GLIBCXX_3.4.7GLIBCXX_3.4.8GLIBCXX_FORCE_NEW
  

  So libstdc ++ RedHat does not include a string for GLIBCXX_3.4.9.

  With this in mind, I was able to get my test application to compile using the version of LabVIEW libstdc ++ using the following makefile:

  .PHONY: all cleanCPPFLAGS=-I/usr/local/natinst/nidaqmxbase/include -I/usr/local/natinst/LabVIEW-2009/cintoolsLDFLAGS=build/square.so \        /usr/local/lib/LabVIEW-2009/patchlib/libstdc++.so.6 \        -Wl,--rpath -Wl,/usr/local/lib/LabVIEW-2009/patchlib/
  
  all: test
  
  clean:        rm -f test *.o
  

  When you try to run the application, I got the following error:

  ./test: error while loading shared libraries: /usr/local/lib/liblvrtdark.so.9.0: cannot restore segment prot after reloc: Permission denied
  

  But apparently, it's because of SELinux prohibiting the use of libraries shared with moving text.
  This can be disabled by running /usr/sbin/setenforce 0 as root.

  The test application now works!

  See you soon,.

  RW

• Runtime Labview 8 coexisting with Labview 7

  Hello everyone!

  I have 2 questions about the coexistence of the different versions of Labview:

  First question: we have several machines with Labview 7 runtime engine, and where this Labiew version executables are running. Now, I was new software to develop using Labview 8, and I want to run them in the same devices. I guess for these new programs I install runtime Labview 8. Pourrait that affect running the old software? Because for us, the good performance of the oldest is crutial.

  Second question: in the other machine, installed 7is Labview. Also in this machine, we would launch an executable of Labview 8. We want to keep there Laview 7. So, if I install runtime Labview 8, could that affect Labview 7?

  Thank you!!

  Just install runtime LabVIEW 8. It does not come into conflict with the former engines of execution or the facilities of LabVIEW.

• VIMBA with Labview

  Hello

  is there anyone who have successfully used VIMBA SDK with Labview?

  You need to download version 1.3

  Use the LabVIEW import DLL

  Point to the VimbaC dll, not C++

  Put _WIN32 in the compiler directives.  This you will get part of the way.

• Compatible with labview thermostat

  Goodmorning,

  I'm looking for a thermostat (a device that can measure temperature and humidity) compatible with labview and if possible with a USB connector.

  You never heard / use such a device? I did some research but I can't find it.

  Thank you in advance.

  Thank you! I found another that looks better, but thank you! (Your temperature is smaller)

• NI 9148 with LabView module detection

  Hello

  I got the task of creating a deployable (compiled) software to a DAQ system with NI 9148 Ethernet RIO basket background and various modules. The user must have the ability to change the module type and the location of the different tests, so the application must detect (or the user specify) what modules are at what positions.

  I watched the blockset CRY, however this chassis is not supported and the lowest level blocks are protected. Is it possible to read the serial number of the modules connected to the 9148 OR position, type, and if all goes well?

  Thanks for any help!

  Hello Soonxaf,

  What are you helps as a controller-is this RT or Windows? Are you planning on the use of analysis of RIO or LabVIEW FPGA engine?

  If you plan use the analytical engine, so this should help you get started:

  Tutorial: Discovery, Configuration and programming access of the CompactRIO Scan Mode to IO with LabVIEW

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

  Kind regards

• Executable VI with Labview 2011

  Hello everyone, I'm doing an executable on LabVIEW 2011 SP1. I've never done before, but in my project, I go to tools-> Build Application (EXE) from VI... I check to make sure that all the Sub VI are in the Dependencies tab and I put the way I want the EXE to go, then I build it. Building compiles and I have good Run-Time Engine installed, but when I go to open the EXE file, I get a lot of mistakes because void VI could not be loaded. I checked these Sub VI that were not loaded and they are locked and password protected. Probably comes with LabVIEW, so they don't want to play us with anything. How can I get these included in the EXE and not return an error?

  Thank you.

  I deleted the Run-Time Engine and downloaded again, and I think it worked. Strange, but I accept it

• ACS550 control with LabVIEW

  Hello

  I recently implemented an ABB ACS550 player to control an air blower speed.  I was control the player through the interface on the disc itself.  However, I am now looking to control the device with LabVIEW.  I don't know where to start and I was wondering if someone could explain what I would need the equipment and the basic principles on how this control can be implemented.

  Thank you!

  -Alex

  After a few weeks to play with the entrance on the digital player, I now have a program that he order.  Thank you for your help.  If anyone needs help with digital controls, feel free to ask.

  Thank you

• temperature measurement with labview on four location using NTC thermistor

  
  

  Hello
  My project is the measure of the temperature of a thermistor on-site 4 difference.
  The measures must be 0 for 100 * C.

  details.
  

  • For the sensor, I must use only NTC thermistor.
  • I have to do an application with Labview.
  • the application must give me the right measure in real time, and it should save the sample in a database.
  • This measure is taken max 20 feet form the pc.
  
  I'm new with this.
  Can someone help me with sensor circuits.
  How can use DAQ with the thermistor.
  Can I use EMANT300 Low-Cost USB DAQ Module 24 bit?

  Please give an idea

• How to set the parameters of the AKD with LABVIEW driver?

  Hello

  I am looking for a simple example to set or read the AKD with Labview driver settings.

  The AKD has ethernet communication and control is analog - AKD-P00306-NBAN-0000

  I want to use Labview to read the paramerters even as Kollmorgen WorkBench

  Thanks for your help

  Thank your for your help

  I found a solution with the TELNET Protocol

• allow to create or write a PDM file with labview 2014

  Hello

  I need help. I'm new with LabView. I tried to create a PDM file, but it does not work. My code in the link below is really simple, but I don't know what the problem is. My code doesn't throw any errors so I don't know what to look for in the internet. Once my code is excuting, no file is created. I use LabView 2014 and my laptoop has windows 7 on it.  My question is, in all I need to do whenever I create a new VI of specific configurations that will be play/create/write a .tdms so that my code may work correctly because the writing in a .txt file works perfectly.

  Thank you and sorry for my English

  Hi bmtanguay,

  you want to run your VI on your cRIO9074?

  Where do you think your cRIO creates this file? A cRIO is a clean computer - and it has its own 'hard drive '. This is where your file is created: C partion on your cRIO!

  You cannot create a file on your Windows pc from a VI running on your cRIO!

• upgrade to labview 2013 problems now with labview 8.6

  Upgrade to Labview 2013 a few days ago and framework installation changed my MAX existing since version 5.1 to version 5.5 with CAN 2.7.5.

  Because all my previous software was written in version 8.6 and customer requirements, this can not be changed and if I need 'backward compatibility '.

  However check the supported versions in CAN it only seems to go back as far as Labview version 10.0?

  Worse still, when I try and load any program written in LabVIEW 8.6 8.6 I now get "cannot find file" for the DAQMX as

  DAQMX------Write.llb------DAQMX------Write.vi etc.

  Tried the navigation in the folder named "MAX."

  The questions are:

  What I have to remove and MAX and re - install the earler versions for compatibility with 8.6?

  If so this can be done without removing my 8.6 install/2013 installs?

  Yes, the new DAQmx versions are not compatible with LabVIEW 8.X.  You can just uninstall DAQmx and then install your previous version to restore your support 8.6, but you will have lost the support of DAQmx for 2013.

• How to install the version of nor-Sync 3.1 in the remote system (processor integrated PXI chassis) to recognize the PXI-6682 device to work with labview RT?

  How to install the version of nor-Sync 3.1 in the remote system (processor integrated PXI chassis) to recognize the PXI-6682 device to work with labview RT?

  Hung Nguyen

  Hung Nguyen,

  The installation of drivers for all targets in real-time remotely is more or less the same. First install the driver (in your case the NO-Sync) on your PC, then install it on your system remotely through MAX. For step-by-step instructions, see install the software on your NI CompactRIO controller.

  See you soon,.

• Watlow F4 controller with LabView

  Hi all

  I have a HX300 refrigerant in a closed circuit that uses a Watlow F4 controller. I want to control the F4 controller and monitor the conditions of it such as the rate of pressure and temperature using LabView. I heard about the pilot Modbus who helps make this communication possible and downloaded it. I use the version of LabView 8.6 and followed the steps needed to include it in Labview. I have very little experience with Labview and wonder how to start to write the code for this. Any help is very appreciated!

  Thank you

  Eric