Please convert LabVIEW 2013 urgent please

Similar Questions

• Please convert LabVIEW 13 10

  Can someone can convert LabVIEW 13 LV 10. These files come from the community

  Much thanks

  Here you are

• I don't see the icon of NOR-DAQmx in measurement window in Labview 2013 (student Edition)

  Hi all:

  I installed the driver NOR-DAQmx and Labview 2013 (Student Edition). I connected an acquisition of data NI USB-6008 and tested using NOR-DAQmx and that it works correctly.

  Now, I tried to make registration of data of this device using the software Labview installed but as I open a new project and go to the block diagram and show the measure menu I can't NEITHER-DAQmx icon in the window (Menu) measurement in Labview 2013 (student Edition).

  Any suggestion?

  I enclose two screenshots.

  Help, please.

  Thank you

  In what order did you install software?

  You must install LabVIEW first, followed by DeviceDrivers!

• Camera not found, error 1074360311 occurred at IMAQdx Open Camera.vi, USB cameras labview 2013 64 (bitts)

  I use USB cameras with labview 2013, and I can acquire images in the MAX and in the Acquisition of mink (express) settings, but when I run the VI, always appear the same error as shown in the Image below.

  -J' checked the correct versions of my software, IMAQ, IMAQdx, VDM 2013 IMAQ of e/s

  -J' I also make sure I had all the updated device drivers.

  -I'm using IMAQdx LKD schema and examples, getting the same error uu

  Help, please!

  Any suggestions would be very helpful.

  

  If it works in the pop up app Express VI and inside MAX (the two 32-bit applications), then I guess it will work in 32-bit LabVIEW. We wonder why it does not work in 64-bit LabVIEW, but these are the drivers of the device and other pieces of infrastructure/DirectShow Windows.

• cDAQ works correctly with Labview 2013?

  I have already upgraded to the LV805 for Labview 2013 in an existing system that has the cDaq-9172, NI9205, NI9263, and NI 9403.

  When executing NI MAX, it detects that cDAQ 9172 (chassis), but none of the cDAQ modules are detected.

  When I open my application, the paths of the cDAQ doesn't appear in entry options, so when it works, and the error message.

  I have SP1 2013 LV f2 and NEITHER-DAQmx 9.8

  This is a known issue, or I have a configuration problem?

  Help, please

  EDGAR_PLATRONICS wrote:

  Now, I have another problem.

  When I turn on my PC cDAQ does not start automatically.

  I have to go to services Windows and manually start OR Setup manager. Same startup is set to Automatic

  Once I run it, cDAQ works correctly.

  My company uses McAffe antivirus

  Concerning

  Edgar

  Mine also.  (McAffe)

  It turns out than if you change the startup type to "Automatic (delayed services start)" service OR McAffe plays more enjoyable.

  

• Runtime LabVIEW 2013

  I want to start a .exe file, written with LV 2013 SP1 on a windows 7 64-bit PC.  I downloaded and installed the Labview 2013 SP1 runtime.  When I try to run the .exe, a message box appears indicating that I need to install runtime Labview 2013!

  I tried to "Reinstall" to verify that it has been installed and I was unable to install the software becaue what is already installed.  I don't know where to go from here...  Help please!

  Are you sure THAT you have installed the 64-bit version of LabVIEW and created the .exe from that?  I ask because the vast majority of people use LabVIEW 32-bit even on Windows 64-bit OS.

  My theory is that you have 32-bit LabVIEW.  You have created an .exe with which would be also 32-bit.  Then download the 64-bit version of engine performance by mistake because you have the 64 bit version of Windows.  In this case your .exe 32 bits will complain of not installing a run-time engine.

• How to remove error 59, which occurred when using email using Smtp Client .VI in Labview 2013.

  Hi, I am trying to run email using Smtp Client .VI in examples of Labview 2013, but it gives error 59.le please can anyone suggest how to remove the error. The printscreen is attached below.

  My apologies, I just tried myself, the port number, you need is port 587 with TLS.

• Problems with the implementation of 32 or 64-bit DLLs in LabView 2013 13.0f2

  Dear Sirs and Madams,

  I try to order a motorized device (MGZ30-WORD thorlabs) with LabView 2013 (32 bit), product version 13.0f2 on a PC under Windows 7 64-bit. Unfortunately, there is no support of LabView for the WORD MGZ30, which means that there are no libraries or VIs for LabView.

  First of all, I want to describe the component or rather its functionality. It is connected to the PC via USB and managed by the v5.0.2153.1 Trinamic Virtual Serial Port Driver. If you wish, for example, adjust the position of the device, there is a small program (written in C++ by the seller). There are 2 different folders for 32 and 64-bit, each containing a .exe, .dll two (a ThemeControl.dll called, who apparently does not have the feature described in the h.file, I want to talk about later, and a ThorZStepper.dll called), a .lib (ThorZStepper.lib) file and an .xml file (ZStepeprSettings.xml, which contains the used COM Port and baud rate information). In addition, there is a folder that contains the driver and a folder called "SDK", that contains the subfolder with a .h file, samples and once more the files mentioned before.

  To use your device, you must modify the COM - ID in the .xml file and run the 64-bit .exe as administrator.

  First of all, I tried to use the VISA-USB-controls, which worked well with another device. However, he did not for the WORD MGZ30 as I did not have the possibility of obtaining the necessary chains of command although I used a sniffer port. Observed communication seems to be more complex than I expected and I was unable to extract the relevant information. To add, the device seems to communicate constantly with the PC even if it is inactive.

  The next idea, which came to my mind was to put in place the .dll files. Therefore, I used the import via Tools/Import/SharedLibrary function and the only h-file that I found in the file and the dll file which stood next the .exe in the folder of 64 bit. LabView created a file .lvlib and I got access to a few screws, which have also been described in the header file. The problem is that I can't run these screws because the .dll file is 64-bit while LabView is only 32-bit (at least, LabView suggests that this is the error.

  After that, I tried the same thing using the same header file (there is only one), but using the .dll file located in the folder of 32 bits. When I now try to run the files, execution of works, but I get an error message "call library function Node in ThorZStepper32.lvlib:Find Devices.vi. There are also a few screws, which do not generate this error, but will not work.

  My next test was to use the "call library function Node", as well as documentation in the .h file, but it didn't work. I don't know if I missed something or the 32-bit .dll file does not work on 64-bit operating system. Could you please help me to use the "call library function node" to investigate the weather that the 32-bit dll does not work properly?

  Please find the file h., (html.zip) documentation of the h.file and the VI, it must indicate the position, attached.

  Best wishes and thanks in advance!

  
  

• Help me convert LabVIEW 5.1 existing 8.5 worm code code...

  Hello

  Please help me to convert LabVIEW 5.1 existing 8.5 worm code code.

  Attached libraries of the LabVIEW to convert.

  Thank you

  Sery

  You can go there. If please read the results of massive compilation, because they may or may not be important for what you do.

• [LabVIEW 2013] Update Service NOR recommend to install the update for the 2012 LabVIEW runtime engine

  Update service NOR recommend to install the patch f5 for the 2012 LabVIEW runtime engine. However, I have LabVIEW 2013 currently running on this computer and never had installed LabVIEW 2012.

  Is this expected behavior and it is actually recommended to install this update?

  Hi mest,.

  Details of the full patch for f5 patch are available in this knowledge base article. As a general statement, we encourage everyone to install the patches as soon as they are available through the Update Service, especially if they are marked as Urgent (it is not marked urgent). In this particular case, it is unlikely that you'll turn to all the problems solved by the f5 2012 SP1 hotfix since you use LabVIEW 2013.

  The reason why you see the update in the update service is LabVIEW 2013 installs several versions of the runtime LabVIEW, so Update Service sees that you have on 2012 Run-Time Engine installed and invites you to patch.

  Kind regards

  Jeff Peacock

  Product Support Engineer | LabVIEW R & D | National Instruments

• Support of NOR-DNET for LabVIEW 2013

  We currently use OR DNET 1.6.6 with LabVIEW 2011. I installed LabVIEW 2013 now also on my computer and tried to synchronize all of the drivers with my installation of LabVIEW 2011.

  Well, it seems that NEITHER-DNET does not support LabVIEW 2013, at least officially. compatibility of Version of LabVIEW and NOR-DNET indicates that NEITHER-DNET 1.6.6 supports 2011 NOR-DNET 1.6.7 2012 LabVIEW and LabVIEW.

  The list NOR system driver November 2013 set OR DNET 1.6.7 defined pilot. When I try to install it, there is no support for LabVIEW 2013.

  My question is, if there is a plan to include support OR DNET for LabVIEW 2013 or later in the game to pilot?

  I copied the directories vi.lib\DeviceNet and vi.lib\nidnet of LabVIEW 2011-2013 and I can load my programs without any problems. I always did not build an executable and does not run on the test set-up, but projects can be loaded in LabVIEW 2013 without any screws of brocken. should I expect any problems running LabVIEW 2013 with the NOR-DNET to 1.6.6 and 1.6.7 driver?

  Nick

  There should not be problems but it is a former pilot, we will not be updated for the future version of labview.

• Software FPGA with LabVIEW 2013

  I have a system with a rotating computer "development" under Windows 7 and an NI PXI-1036 chassis with a PXI-8101 controller as well as a card FPGA PXI-7853R. Recently, I upgraded to LabVIEW 2011-2013 of LabVIEW. I kept LabVIEW 2011 installed just to make sure everything is still working on the new LabVIEW.

  Now, when I open my project in LabVIEW 2013 Project Explorer, my FPGA comes with a warning triangle yellow next to him (see attached photo). The warning says:

  "Software support for this target FPGA is not installed on the computer. You can view and copy elements into the project, but you can not compile any screw under the FPGA target, until you install support for the target. Refer to the documentation of specific material for more information on the proper drivers and for more information about the installation and configuration of the target FPGA ".

  Regarding the installed software, I have LabVIEW SP1 of 2013, 2013 of LabVIEW FPGA Module SP1, SP1 of Module 2013 LabVIEW Real-time, and Xilinx Compilation tools 14.4. On the chassis of the TARGET (with the PXI-8101 controller), I have attached a list of installed software.

  Interestingly, when I open the project in LabView 2011, no errors or warnings are present with the FPGA card. It is only under LabVIEW 2013 I see the warning. Did anyone see a glaring omission of software that could be the cause of LabVIEW raise this error? Thank you for your help.

  

  

  Best guess is that're missing you the driver for your FPGA device. Try to install the latest version of NOR-RIO (or at least the version supplied on your 2013 SP1 install disks). Have you installed device drivers at the time that you have installed SP1 2013 LabVIEW?

• LabVIEW 2013 close when I try to read the database table.

  LabVIEW 2013 close when I try to read the database table.
  I get the error message, Labview falls just crashes. I use Labview x 32 and connective Toolkit of connectivity of database on Windows 7 x 64. I connect to PostgreSQL with ODBC driver, the connection is stable.
  In my database, I have a lot of tables, I read all those without one.
  When I try to read table bad I get data then labview crash. When I restart Labview, I have no message on the error.
  Also I try to use LabSQL-1. 1a. But it has the same result.

  I found the solution.

  I think the problem was that I have very large table in my database.

  At the beginning I received data from table with next quiry:

  SELECT column1, column2 FROM 'table ';

  But when I write then:

  SELECT column1, (column2, ',') array_to_string FROM 'table ';

  all worked!

• convert from 2013 2012

  no idea how to convert from 2013 in 2012?

  Thank you very much

  In LV2013 file... Except for the previous Version.

  I don't know if this is available for all versions of LV (I Pro). You can also post your vi to the Commission on conversion of version

  http://forums.NI.com/T5/version-conversion/BD-p/VersionConversion

  Ben64

• Range of custom error codes and error rings/Labview 2013 SP1

  Hello

  for the error message personalized codes there are these assigned ranges:
  -8999-by-8000
  5000 to 9999
  500 000 to 599 999

  If I create an "error ring" in Labview 2013 SP1, then I am able to choose predefined error codes or I can put in some custom error codes. Curious as I was I chose 'Labview' in the menu drop down and looked up some error codes. I noticed that there are some affected error codes that are of the order of custom error codes (see attachment) of 538170 to 538193.

  Is this a bug or feature? What is the impact if I defined error codes customized with identical, already existing error codes?

  Kind regards

  Thomas

  Thomas,

  It seems you have installed ModBus library. As it is an additional package, picking "custom error codes" is not bad even if the library fits in LV...

  Norbert