LabVIEW executable with my VirtualBench

Similar Questions

• Client server of executable activex LabVIEW project with excel vba

  Hi all

  I submitted a ticket to support nor on this problem, but my deadline for this project is very close, so I would like to ask the community to see if someone has encountered this problem before (I hope it's ok that I'm doing this!). I did a fair amount of forum-scouring, and I didn't know this even discussed problem.

  I built a labView project which is essentially in the material data and
  preforms various visualizations and transformations on the data. A bit of the
  Screws in this project are available by VBA Excel as a Server ActiveX with LabView and
  Excel as the customer - and it works! I recently discovered I would need to do a
  executable version of my project, so I'm now trying to figure out how to do the same thing
  with my executable file as the server instead of LabView. Here's a simplified version are
  My VBA code:

  Void Button1_Click()
  Dim lvapp As MyServer.Application
  Dim vi MyServer.VirtualInstrument

  Set lvapp = CreateObject ("MyServer.Application")
      
  VI the value is lvapp. GetVIReference ("Main.vi", "", True)
      
  Sheet1.cells (1, 1) = vi. GetControlValue ("Path")
      
  lvapp. Quit smoking
  End Sub

  I replaced LabView here with the name of my server. The code
  failure of the CreateObject method with the following error:

  Run-time error '13':
  Type mismatch

  Things, I'm pretty sure I'm doing it correctly:
  -L'application is configured as an ActiveX server in the build options
  -J' ran the VI once and close/re-open it just after each build before trying the
  worksheet
  -In excel, VBA method is configured to reference the type library of the server.
  -J' have LabView itself closed when I run the .exe

  Thank you

  Alex

  My versions and such:
  Software of NEITHER: LabVIEW version 2012
  OS: Windows 7

  It's interesting - I'll have to look into the issue. In the meantime, I found a solution.

  It's quite mysterious, but it seems that all I had to do was make sure you only the type library of the server executable has been referenced in VBA (no LabView or OLE type library) and declare the variable app as object, rather than MyServerName.Application. Honestly, I have no idea why this works, but it does. Also, I learned that you need to use the executable file paths, which are a little different than the paths of project files.

  Thank you

  Alex

• (My Labview executable built) has encountered a problem and needs to close.

  All,

  I built a labview executable that interacts with the GPIB and the Texas Instruments EV2300 via USB.

  The VI works beautifully on the development computer and I built the VI in an executable file and it works fine on the development computer.  So, I built a Setup program that installs running Labview 2010 on the target computer.  I ran the Setup program on a computer on the production line I know can run GPIB and the EV2300, but when I try to run the executable I get an error that says: ""(votre demande) has encountered an error and needs to close.""

  I can get labview executables that do not speak of GPIB or USB to run on the target computer, then it is not the execution environment.  And I VB6 applications that can run EV2300 and GPIB interfaces smoothly.

  I don't do anything weird with the paths to files in my program, only the creation of the railways using the VI canned to convert strings into paths.  Under the program, I've read some text files and write a.

  Is there anything that I need to know how to build an application with an installer?  I need to get up and running so the test program can work on a production line.

  
  

• Run LabVIEW executable in Windows 7

  Can I run an executable of Labview created with Labview 8.6(32-bit) in windows 7 or Vista. If this can be done then how? I tried to copy the lvrt.dll (runtime engine) in the system 32 folder, but it is not solved my problem. FYI, my Labview exe file also include the fuzzy logic toolkit.

  Hope someone will help me. Thank you.

  Lojius.

  Refer to http://search.ni.com/nisearch/app/main/p/bot/no/ap/tech/lang/en/pg/1/ps/30/sn/catnav: of, n12:, n13:r. /c0 >, motor run LabVIEW 8.6 only supports Vista.

  If you are using WIndows 7, you use LabVIEW 2009.

• Autonomous creation of labview executable problems

  Hello

  I have a problem creating an executable with my labview project and I can't seem to make it work. The presentation of the project looks like this.

  

  but when I'm building the executable file of the Application Builder, it does not run the LabVIEW VI. However, it does not use the functions (from what I can tell) the DLL or the ChrApi.lvlib, because it does not activate the tests that these libraries are responsible for dedicated... any advice would be appreciated.

  Check that the DLL calls in the vis.  If the ' name of the library or the path "contains a path, the Builder app will copy the DLL to the destination of the building and the executable will this copy.  If the "library name or path" contains only a name and not a path, then the DLL will be not be copied by the constructor of the app, and when the executable is run, it will ask the OS to find the DLL.

• Labview compared with Agilent Vee Pro

  Hallo! Could someone show me the key benefits of Labview compared with Agilent Vee?

  Thanks in advance!

  A lot of old debates. Start here, and then follow the links.

  What type of project do you need to face?

• External DMM communicates only with the LabVIEW executables

  Hello

  I currently have a system of power supplies connected with GPIB and an Agilent E34405A DMM connected via USB.  The system works fine when I use the complete Labview program, but when I make an executable and installler and put it on another machine, that I can not get the DMM communicate the work of supplies of power very well and done my other equipment.  Any thoughts?

  If your program LabVIEW use NI-VISA, you need to charge NI-VISA run-time on the target computer.

• Shared variable between 2 LabVIEW executables via the network

  Hello, I need to create a number of network shared variables by two (built with LabVIEW 8.6) executables running on two different computers on a local network. The library to invoke node returns an error when you use a different IP than localhost. even more, it is not clear to me what exactly I have to do (what executable deploys the library, on which targets, activate the link or not, so on...). Thanks for any help, if you have already managed to make this communication works properly...

  Thanks for the replies. I've found the last two documents, but the first one is the most interesting: if I can't put the sources of two applications in a single project, I will move to another solution (data as suggested by Mike sockets or TCP). The two original projects are larger, and their merger would lead to such a huge thing!

• Raspberry PI installed correctly on LabVIEW 2014 with LINX 3.0 (yellow warning)

  Hello everyone

  Well, I create this thread because I can't connect with my RPI with LabView2014, I'll put some different screenshots, as you can see I already install the LINX 3.0 on my computer.

  My computer sistem

  -10 64-bit Windows

  Products already installed

  -LabVIEW 2014 32-bit

  (this labVIEW I downloaded from the link of the PDF tutorial)

  LINX - 3.0

  -Control design and Simulation Module

  Module - MathScript RT

  NI - VISA

  VI - Pakage Manager

  -Also, I have my license activation

  I'm going to download some print screens in this same position

  Thank you

  Ruben Rhico

  Hey Patrick,

  Make sure that you have restarted LabVIEW since installing LINX.  If the problem persists, follow the instructions in sharpk in this thread.

  Let us know if that fixes the problem.

  Thank you!

  -Sam K

• LabVIEW interface with multiple blocks of Festo module

  I am trying to connect with a block of Festo, but I can't. Here are the details:

  I'm under Labview 2012 SP1 with IndComm-DeviceNet 2.2 pilot on a 64-bit Windows OS. I installed a PCI 8532 card NOR. I see the map to the MAX.

  The block of Festo is built with the following Modules: CPX_FB11 (communications module), 4 analog input Modules, 1 Digital module, 2 digital modules followed by 32 Festo valves. (Image below)

  

  Using DeviceNet PXIPCI Basics.lvproj I did the following:

  In the project, right-click on desktop > New > targets and devices > existing target or device, discover an existing target or device...

  Expand the node of DeviceNet Master Interface, DeviceNet1 chosen and added to the project.

  A click on the newly added DeviceNet/device target > New > targets and devices...

  Expanded the Festo Block "CPX_FB11" selected DeviceNet slave device and added to the project.

  Initially, I received an error card technique 'EDS file no assigned' I solved this by following the direction listed here.

  However, I'm unable to "see" anything other than the CPX_FB11 LabView. The tree view of the devices lists not analog, Digital e / s or valves. I can't operate the Valves and IOs digital or analog. When I run the entire project VI they then expire.

  Any help would be appreciated.

  Thank you

  Tennessee Paul

  Hi Jesse,.

  I'm not entirely sure what the specific problem was. I kept getting strange behavior. Errors in LabView and on my camera from Festo. The EDS files change. So, I did as any natural born THERE would be worker, I rebooted.

  Here are the steps I used to get this project going. In doing so, I found that to set up a DeviceNet device in LV2012SP1, no need to manually enter the data in file EDS. There is a tool to load files EDS. It dealt with issues I had in the previous Forum posts: here about loading files EDS in LabView and here regarding setting up a DeviceNet network.

  Environment: Windows 7, 64-bit processor. IndComm 2.2 pilot. LabVIEW 2012 SP1

  Starting with the example LabView project: "Devicenet PXIPCI Basic.lvproj.

  Add a DeviceNet master to a LabView project

  1. The project: right-click on my computer
  
  
  1. Select new
  
  
  2. Select the targets and the device (s)
  
  
  2. Select the option "discover existing devices.
  
  
  3. Select the discovered device.
  
  
  4. Click 'OK' (Note: in this case, my master is a card PCI of NOR-8532)

  Add a DeviceNet slave device to a LabView project

  1. Right-click on the master device newly added in the project tree
  
  
  1. Select new
  
  
  2. Select the targets and the device (s)
  
  
  2. Select 'discover existing devices.
  
  
  3. Select the discovered device.
  
  
  4. Click OK. (Note: in this case my slave is a block of Festo CPX-FB11.)

  Load an EDS file to the slave device

  1. Right-click on the slave device
  
  
  2. Select "Sheet"... »
  
  
  3. Click on add files...
  
  
  4. Navigate to the location of the EDS file.
  
  
  5. Select the file.
  
  
  6. Click OK.
  
  
  7. In the left pane, expand the data sheet newly added up to reach the node displays the version.
  
  
  8. Select the version.
  
  
  9. Click OK.

  Check the device and file EDS

  1. Right-click on the slave device
  
  
  1. Select utilities
  
  
  2. Select the Panel of Test online
  
  
• Select the option 'Device status' in the field of category on the left.


• On the right, select the slave device, you want to check.


• Click on "check the device".


• Read the errors/warnings or lack thereof.

In my case I had errors in my EDS file. Basically the slave device was not defined for the correct number of bytes of input/output in the EDS, i.e. a wrong configuration file. To fix this I had to change the EDS file.

Edit the file EDS

To change the EDS file, I used EZ-EDS , which is a freeware, devicenet specific EDS editor of ODVA.

I did my corrections and saved my file EDS. (After having saved my original, of course).

Remove the installed Labview EDS file

1. Navigate to the following location: C:\ProgramData\National Instruments\NI-IndComm for DeviceNet\Datasheet


2. Remove the sheet (Note: there is more that one datasheet added manually.) Additional EDS files come with the IndComm driver. Find the EDS file for the specific device that you want to replace and delete).

I restarted LabView.

I went through the steps above again and loaded my new EDS file.

I saved the project and came out of LabView.

I rebooted the computer and the slave device.

I restarted the project and launched a VI.

I was able to communicate with the device. That is something that I had not been able to do before. And, in doing so, I discovered how the device speak and why were not each module. (I have a standard for my block devices EDS file, as it appears that LabVIEW is not capable of a modular system that requires an EDS file for each module. I could be wrong on that last part though, as there may be a setting on my real device. But it is unecssary in my project. So I do not consider this further.) Because I was using a standard file of the EDS, only a single slave device showed, and so the data for each module are in the stream of bytes returned to the DeviceNet network. Addressing each module is a question of analysis the bits and the bytes appropriate.

Thank you

Tennessee Paul

• LabVIEW 2010 with CDAQ-9188 and NI9205

  Hello

  I use the NI CDAQ 9188 with the Analog Input Module NI 9205. The specification of the NI 9205 module shows that there

  16 channel differential channel, or simple 32 took end. I use the 'DAQ Assistance' in Labview to configure the

  Module OR 9205. But it only allows me to select 8 differential channels. After I put the 8 channel, then the

  Terminal configuration allows no differential inputs. It allows only to CSR or NRSE entered.

  I'm doing something wrong? I just bought the camera to use for 16-channel differential reading.

  Thank you

  Bobby

  Hello

  It worked.

  Thank you

  Bobby

• Make an executable with DAQmx

  I'm doing a .exe of a data recorder simple with the acquisition of input data.  I can do the .exe and it opens fine with the runtime, but the DAQmx features do not work.  I followed the instructions to build an installer, but I get an error about the hardware configuration.  The error measage is "some selected for this build installers do not exist on this computer.  He is looking for Labview platform DVD1 and National Instruments Device Drivers.  I don't have access to the installation DVD (we have a site license and can only download the software).  I downloaded device drivers and placed it locally on my computer.  I try to navigate/browes to it and point to the folder, but then I get the message "this site does not contain a valid installer."  I'm kinda stuck.   Any advice on what I should do?

  If you have a travel you have installation media. Period!  You know where it is

  By "Site License" I assume you mean a Volume license contract; but I will work in all cases

  1. Open License Manager OR to determine what type of license you have, and the serial number of your product.
     1. If it is a VLA VLA Admin Contact for the media. If you do not know the VLA administrator call OR they will look at it for you by its company name and serial number
     2. If it is a named user go to MyNI and register the product: then open a Support Ticket on your SSP active for new media. OR
     3. Other named user. Call your local OR field office and demand media-(ils savent où ils gardent pour juste ce genre de chose!)
     4. If it is a license find computerized which society media delivered too!  Still, the Customer Service with the serial number OR the call will cut through a lot of paperwork!
  2. Finally, under no circumstances, talk to your representative local field OR to discuss best practices for YOUR TEAM standing with and distributing keys and media.  You should not have to 'download only' products of NEITHER!  (His practice sometimes but not very durable!)

• Is the tool provided with the works of Labview 2009 with LabVIEW2010

  Hello

  I use currently LABVIEW 2010 want to know about toolkit provided with the dvd of LabVIEW 2009

  is compatible with the labVIEW 2010

  Thank you

  Check out this link.

  http://www.NI.com/support/LabVIEW/lvtool.htm

  If the required toolbox does not "(ou supérieur) ' after the requirement for 2009, or specifies LV2010 it is not compatible."

• Basis of LabVIEW Development with Compact RIO device software

  Hello.  Currently, I have the LabVIEW Base development software package and have been using it with DAQ Compact devices for the acquisition of basic data.  I would now like to start integrating controls in my system, changing to RIO Compact for deterministic real-time features.  My question is that I would be able to build applications for the Compact RIO system using only the basis of LabVIEW Development package without updating immediately?  Maybe some features are not available for me, but could at least get a good start like that?

  A CompactRIO embedded time real operating system (RTOS) called VxWorks you need to target the deployment of LabVIEW code to the device. Classic LabVIEW screws you will have been written so far are built to target general purpose operating systems (GPO) such as windows.

  To create screws that are deployable to STSOp, you will need the real-time Module that is not included in the basis of LabVIEW. As a result, to take advantage of the embedded FPGA, you'll need to install the LabVIEW FPGA Module as well.

  As long as you have the FPGA modules and in real time, it seems to me that you should be able to control these devices with LabVIEW Base. Without these software components you will not be able to create an instance of the device target your LabVIEW project.

• LabVIEW interface with micro contoller

  I'm new to labview. I need to know if the DAQ card is necessary to interface with micro controller? If no need then one can you explain how inter face microcontroller 89c 51 with Labview... If necessary, explain how interface?

  JEAN ASOKAN