DLL crashes LabView 2013 Pro, but good to EXE

Similar Questions

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

  
  

• Installed AcrobatX Pro, but it crashes just after opening a document

  I just installed the trial version (I think) Acrobat X Pro.  I want to try out the features of edition of the Pro version before installing. I am not able to install Acrobat Pro DC because I'm on an old mac running on 10.7.5.

  So, I was successfully able to install Acrobat X Pro, but now whenever I open a document it hangs and quits the program after a few seconds. Can you help me?

  Hi Sarah,.

  Acrobat crashing on launch more likely seems to be a problem with the license.

  Try the following steps:

  Delete all the files in the following folders:

  C:\ProgramData\Adobe\SLStore

  C:\Program Files (x 86) \Common Files\Adobe\SLCache

  And delete all of the following except cache.db file

  C:\Program Files (x 86) \Common Files\Adobe\ Adobe PCD

  Product launch and activate with serial number again and check.

  Kind regards

  Rave

• Hello! I've got CS3 Design Standard - real records and certificate of software license. It was installed on my laptop that crashed and could not be uninstalled. I have now installed on my new MacBook Pro, but can't get it registered with the

  Hello! I've got CS3 Design Standard - real records and certificate of software license. It was installed on my laptop that crashed and could not be uninstalled. I have now installed it on my new MacBook Pro, but can't get it registered with the serial number. Is it because it has not been uninstalled on the previous laptop? What should I do now? THX!

  Maybe this can help someone else...  I had to simply properly uninstall CS3 and reinstall again after that.  I think what he sort!  I also remember having a similar problem with the Mac at work a couple of years back.  Not sure if it is the same for CS5/CS6.  Here is a link on how to properly uninstall CS3 on Windows XP, Windows Vista and Mac OS.  I'm on OS X 10.9.2 but it works beautifully.  Remove from Creative Suite 3 and CS3 products

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

• Load a complex DLLs in Labview

  Hi guys:

  I need to load a dll into labview, the prototype is:

  running long (const char a [],
  const double b,
  const int c,
  double d [5] [23],)
  Double e [4],
  );

  I put the prototype in labview is:

  Uint64_t function (const CStr has,

  const double b,

  const int32_t c,

  Array2DDouble * d,.

  Double * e);

  but the function does not work, I suppose that it maybe some concern to the parameter d, the attached file is the config box,.

  

  Someone tell me where is the problem?

  Thank you

  Good news. I have fix

• Call a C-built DLLS in LabVIEW

  Hello!

  I try to get knowledge on how to call DLLs in Labview.

  I found a very good example on this site:

  http://zone.NI.com/DevZone/CDA/EPD/p/ID/1513

  I downloaded and extracted the call_c_dll_in_lvnew.zipfile.

  When you try to open the sample file GenSortRandC.vi in the folder LabVIEW_code_and_DLL

  I get the following error message.

  "The procedure entry point not found RebootRTSystem in the library cvirte.dll dynamics."

  I searched on the Internet and some forums but so far without success.

  Could you please let me know if you have the same problem the example whith?

  I have the following configuration:

  -Labview 8.5.1 FDS (default installation)

  -Windows XP sp3

  Best regards

  Mattias

  Sweden

  Mattias salvation,

  I have no problem with this example. I can't run without error.

  It's maybe because I installed the CVI Run Time engine.

  Mike

• Python, call DLLs in LabVIEW: Fatal internal error when accessing output String Cluster

  Hello

  We have compiled a DLL in LabVIEW (TestError.dll) and tried to call it from Python.

  TestError.dll includes 2 functions:

  1 testErreur: cluster 1 entry string, 1 channel indicator

  2 TestError2: 1 channel input, 1 bunch of output string

  What we try to do in Python is actually something like this:

  1 provide values to controls in the functions of the DLL.

  2. call the DLL.

  3 get the values of the indicators.

  What we have seen are:

  1 read/write operations on normal data types (string, digital) indicators/controls are OK

  2. write operation on the Cluster string entry is OK

  3. read operation on the Cluster output string is not OK. The following error is still prompted for:

  «Unrecoverable internal error: 'MemoryManager.cpp', line 437.» LabVIEW version 8.6... »

  Also joined the TestError.prj and python code.

  Grateful if someone can help to explain why we get this error and how to overcome?

  Thank you

  howmean

  What we have seen are:

  1 read/write operations on normal data types (string, digital) indicators/controls are OK

  2. write operation on the Cluster string entry is OK

  3. read operation on the Cluster output string is not OK. The following error is still prompted for:

  «Unrecoverable internal error: 'MemoryManager.cpp', line 437.» LabVIEW version 8.6... »

  Also joined the TestError.prj and python code.

  It is very logical that it does not, and the bad news is, it cannot really be implemented reliable of a process not LabVIEW.

  LabVIEW channels (and tables) are very specific species. They are then called handles, which are pointers to a pointer to a block of memory. If you have a control or indicator on its own, the Prototype configuration allows you to configure this setting as a C. LabVIEW data pointer, when creating the DLL, create heels C for each exported function and place the code to do the translation between the past C pointer to and necessary LabVIEW data handle. For strings and arrays within the cluster, there is no configuration option and the DLL is expected to pass a structure with data handles native LabVIEW in there.

  You may say that creating handles data in your calling process enough to trick LabVIEW. For the input variables that actually CAN sometimes work (but is a delicate and dangerous generally to handle this). There is no way to make it work for output variables. LabVIEW will try to resize handle to fill data in that he wants to make. This resizing is done using internal memory manager of LabVIEW. This will work only if it had been allocated by EXACTLY the same instance of the memory manager. Otherwise, it refers to a different memory segment and catastophally fail. The only way to make this work perhaps, with luck, taking your heart and prayer to the gods, is to lvrt.dll to allocate a handle that you must pass to the DLL. Still find the good lvrt.dll, which will execute your DLL LabVIEW is a major challenge.

• Problem of memory, then I import a DLL on LabView 2010

  Hello

  I have a lot of problems with importing a file .dll on labview.

  The blocks of import to the third of fourth function and sometimes a textbox appear (as you can see in attachment).

  I tried with the import node, but it does not work (so maybe it's that I don't know how to use it really).

  I don't really know how to import the entire library, and I am really stuck.

  There is also the header and the dll as an attachment.

  Thanks for your interest.

  I didn't say it's impossible, but it is very likely well above your head. You probably have two options:

  (1) to abandon this material and get a part that has a good support for LabVIEW.

  (2) hire someone with a very good understanding about LabVIEW C interfacing and allow them to create a VI library and interface DLL for you.

  Good luck

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

• LabVIEW 2013: An error occurred trying to load the assembly

  Hey all,.

  I'm trying to load a dll .NET 4.5 in LabVIEW 2013.

  When I place one of the screws .NET and try to select the one I am after it says "an error occurred trying to load the assembly" and will not let me load it.

  I also tried to import the dll, but who also gave errors.

  It's defintely a 4.5 as the reflector .NET .NET dll gives me

  [assembly: ComVisible (false)] [assembly: TargetFramework(".)] NETFramework, Version = v4.5 ", FrameworkDisplayName =".NET Framework 4.5 ")] [Assembly: SecurityRules (SecurityRuleSet.Level1)] [assembly: SecurityPermission (SecurityAction.RequestMinimum, SkipVerification = true)] '"

  To try to work around the issue of the import, I added the following to my LabVIEW.exe.config file

  
  
   
     
   
  

  but it made no difference.

  Any suggestions? All the things I've read so far are for 2010.

  SOLVED!

  I installed a 64-bit version of LabVIEW and it works. HUZZAH!

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

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