LabVIEW LabVIEW 2013 2014

Similar Questions

• LabView 2013 or 2014 Web Application Server does not start.

  I have a request that I built in 2013 of LabView that uses the Web application server OR. The application worked until end November 2014 when the Web in LabView 2013 application server has stopped working. Specifically, 2 and 1) NI NI Application Server Web services) Web Server system both were running, but I was unable to access web pages that I created earlier, or I could access the Configuration Web page OR localhost:3582. In addition, the button "Configure Web Application Server" under "Options/Web Server" is gray. Makes me think that web services NOR did not start successfully upward. Complete a repair facility OR to the LabView 2013 install did not help either.

  Since the opening of a service ticket with NEITHER, I've now deleted and reinstalled the 2013 LabView and LabView 2014 each with the latest patches. But the problem persists.

  The ticket OR for that matter now rests with RnD, so I'm tender hand to the community OR to see if anyone sees something similar? Or has any ideas to try?

  Some additional notes:

  (1) contrary to LabView LabView 2013 2014 no web services NOR would begin, based on a new for 2014 dependence on the Authentication Service of NOR. In 2014 this service does not either.

  (2) when I uninstall 2014 and re-install 2013, chess happens again (as above).

  (3) my system runs Win 7 Pro x 64 with 8 GB of RAM.

  (4) I have McAfee virus scanner/firewall. I have disabled and even uninstalled without correcting the problems.

  At this point any ideas to try would be greatly appreciated, because I can't wipe my OS and start over.

  Thank you

  * Update *.

  I finally found a solution to this problem. The solution is the following:

  1. Delete the two files "C:\ProgramData\National Instruments\NIAuth"
     • commitmark.1
     • Registry.bin
  2. Restart the OS and re-launching of LabView.

  On the next reboot, LabView recreates these two files and the Web services OR Windows services start normally. Once NI WebService which works normally.

  I'm assuming that one or both of these files has become corrupted at some point, that has kept the WebServices OR start properly. But as none of the services OR created an error event Windows for that matter, I stayed to search for the solution. And since the installer NOR has not remove or repair any of these files, the question continues to no matter how many times I have re-installed LabView on my system.

• Please convert LabVIEW 2013 urgent please

  Please convert LabVIEW 2013 urgent please

  You can go there.

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

• 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

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

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

• LabVIEW 2013 64 bit does not support the 'toolboxes connection database?

  Hello

  I have download the labview 2013 64 bit & registed with success

  But encount a problem when I try to install "2013DCT"(database connectivity toolkits)

  Don't LV2013 64 bit does not support this toolkit?

  If Yes, where can I find the boxes to tools for 64-bit?

  You can install the version 32 bits in a relavent LV and copy the installation.
  /Y

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

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

• LabVIEW 2013 executable only works on the development machine?

  Hi all

  I created an executable to distribute my test software, but it only works on the development computer. With success, I gave my front executables with labview 2012 on the target computers by simply creating the .exe in the project and then Explorer in installing labview nessary drivers and run the engine of time without problems. Now, I created a new test with Labview 2013 program and I can not get my new test .exe application to run on the target computer. Has anyone seen this kind of problem before?  Any help will be appreciated.

  Thank you

  
  

• Can I use Labview 2013 on 64-bit and 32-bit PC interchangeably?

  Hello

  I am running Labview 2013 basic package on Windows 7/64 bit laptop, which is not stored permanently in the laboratory.  I need to buy a 32 bit desktop PC to run a non-Labview application, but it would be very convenient to use the new 32-bit machine to run Labview also, since it WILL BE at all times in the laboratory.  Then I wouldn't have to connect or disconnect the laptop computer in the laboratory every time I do the development of the system.

  Can I load my version of Labview 2013 on a desktop Windows 7/32-bit and write/run system live even as I do on my laptop Windows 7/64-bit?

  If the 32-bit and 64 - bit are interchangeable, so, I would get a higher end 32-bit system.  If they aren't, then I get the cheapest available 32-bit system and dedicated to the non-LabVIEW application.

  Thank you

  Dave

  LabVIEW edition will almost certainly be the screws you develop using 32-bit executables on Windows 32-bit and 64-bit systems.  What will certainly be different is the LabVIEW runtime system, so be careful when you build executable files.  Certain pieces of evidence that this is probably, it's developed under Windows XP (32-bit) code will run fine on Windows 7/64 (in development Mode).

  Note that I'm assuming that you installed LabVIEW 32-bit on your system Win7/64 (although there is a 64-bit version of LabVIEW, my understanding is that he could not be "ready for Prime Time").

• Edit event managed by this case in LabVIEW 2013 does not show the specifiers of the event, Event Sources and events on screen resolution 800 x 600

  Edit event managed by this case in LabVIEW 2013 shows not specifiers of the event, Event Sources and events on screen resolution 800 x 600.

  As far as I know, the list of supported resolutions is determined solely by the graphics card. It is possible that one used by the PC supports only 800 x 600 as maximum resolution, even if you plug an external monitor.

  Like Dennis suggested, the recommended option would probably be to develop on another PC and only deploy an executable for the industrial PC. That's what we do with our systems (although not because of this problem, but because it makes sense. There absolutely no need to have the IDE installed in most of our systems).

  Other options:

  1. See if you can get an update of the driver from the manufacturer to solve this problem.
  2. Plug a USB Monitor with its own driver.
  3. Try to hide the taskbar and make the smaller title bar in the hope that the bug manifests.
  4. Try remote access in the PC. I think that some remote access programs allow you to specify custom resolutions that are not affected by the original drivers. Remote Desktop seems to be a likely this option even if it has been awhile since I've used it.
  5. Check the BIOS. I saw at least one industrial PC where there was some settings in the BIOS to control the resolution, but I don't remember the details, and it was quite limited. I think that in this case, you can change the resolution, but then the image does not fill the entire screen.