CVI

Similar Questions

• The interface of the AVI with the PC using LabWindows/CVI

  Hi friends,

  I have a vector Network Analyzer Keysight Technologies / Agilent Technologies N5230A. I want to run with the LabWindows/CVI to measure channel 40 GHz. I want to interface the AVI with the PC using LabWindows/CVI. It is really essential for the measures, and I have no experience in doing these things. Would you please direct me to the best, easy as possible of this work? I'm really conscious of the fact that and thank you for your time and concern.

  Mohamed

  I have a vector Network Analyzer Keysight Technologies / Agilent Technologies N5230A. I want to run it with the LabWindows/CVI and measure channel 40 GHz. I want to interface the AVI with the PC using LabWindows/CVI. It is really essential to me, and I have no experience in doing these things. Would you please direct me to the track better, easy and correct these work? I'm really conscious of the fact that and thank you for your time and concern.

  Mohamed

• CVI executable causes an on update of Windows 10 anniversary 0xC0000005 Access Violation.

  Created executables always causes an Access Violation (0xc0000005 exception) to the closing period on Windows 10 RS1 (update of the anniversary).

  This problem occurs in LabWindows CVI 2015 and 2015 SP1.

  How to reproduce: simple program to create and compile with the (x 86) release profile by default.

  for example:

  #include "test.h".
  
  
  
  
  int ph;
  int __stdcall WinMain (HINSTANCE hInstance, HINSTANCE hPrevInstance,
  
  					   LPSTR lpszCmdLine, int nCmdShow)
  
  {
  
  	If (InitCVIRTE (hInstance, 0, 0) == 0)
  
  		Returns - 1;    / * memory * /.
  pH = LoadPanel (0, "test.uir", group of EXPERTS);
  
  	DisplayPanel (ph);
  
  	RunUserInterface();
  return 0;
  
  }
  int CVICALLBACK CallExit (int, int int event, control panel,
  
  						  void * callbackData, int eventData1, int eventData2)
  
  {
  
  	switch (event)
  
  	{
  
  		case EVENT_COMMIT:
  
  			QuitUserInterface (0);
  
  		break;
  
  	}
  
  	return 0;
  
  }

  The problem is visible on the control panel > reliability history > Error Reporting:

  

  Also the code of the executable file (exit code) is always 0xc0000005 instead of zero.

  To check out more easily code can be called the executable through file .bat:

  off @echo
  
  Test.exe
  
  echo ExitCode = %ERRORLEVEL%
  
  pause

  I have observed that if multiple instances of the same program are running, only block when the last instance is closed. It seems that the problem occurs at the time that the CVI runtime is released from the ram. (The latter is only a guess)

  Hello

  We did some research and saw that the failure is related to some police files in

  c:\Windows\SysWOW64\cvirte\fonts

  c:\Windows\System32\cvirte\fonts

  Could you try deleting these files and see if the heater is always performed. If this isn't the case, it would be a work around if you do not use these fonts.

  We continue the investigation to see the exact cause

• Real-time execution trace toolkit to optimize the Labwindows/CVI code

  Hello

  I am trying to optimize a code in real-time in LabWindows/CVI by minimizing the time of each section of the code is taking and find bottlenecks in the code. I check this time using the real-time execution trace toolkit.

  However, I just found it seems to be a constant error when you use the tool of real-time execution trace.

  When I put the traceviewer 'start' and 'stop' right after the other, I get around shift schedule 9us. It seems that the CPU will in some "idle" after the start of the trace mode, or maybe it's the time of communication or something.

  I'd appreciate it if someone could give me an idea of why this is happening. The time of real-time application window is very limited and I'm trying to minimize the time as much as possible. Even the United States 9 error is difficult to resell.

  I used the following code:

  TraceConfigure (1, 1, 0, 25000, NULL);
  
  TraceStart ();
  
  TraceStopAndSend (HOST_ADDRESS);

  and there is a photo in the toolkit of real-time execution trace.

  Thank you.

  Generally, you might be better off picking off the clock at the beginning and end of what you want to track. RTETT my introduce overhead that becomes difficult to quantify... Which is what you probably already see. The debug mode will also implement a ton of overhead. Then... Destemming of the clock in release mode will probably give you you the best estimate.

• Application stops working out - Windows 10, CVI 2013

  Hello

  I recently moved from Win 7 to 10 to win.  Now, all the applications I built under Win 7 or rebuilt under Win 10 "stops working" at the exit.  I found some posts that were similar and posted one, but got no response.  As another user has pointed out, I did a return 0; immediately following main() and I get the same error.

  My suspicion is Win 10 and cvirte.dll are not compatible.  But honestly, I don't know.  I saw a similar reference to this in 2015 CVI which has been reported by NOR as a bug.  I don't know if it has been fixed.

  All the solutions to this?

  Thank you

  Dave

  Is this the same problem as stated in this thread? And workaround suggested the fact he work? (deletion of fonts install files in folders of execution)

  If not, can you tell us what version of Win10 are you running?

• CVI 2015 & Windows SDK

  Installation of CVI 2015 on laptops Win7 enterprise.

  Work project recently installed, registered, launched, went to its construction, and ICB 2015 requires the installation of the Windows SDK 8.1.  Obtained after popup error message.

  

  I've traveled on ni.com/frinfo, entered the code and was immediately sent to the Microsoft SDK 8.1 page.  No information OR on what to do, how to install, how to bind the SDK of the CVI.  Tried to download the SDK 8.1, and he repeats to me that the file is corrupted.  I tried SDK 10.0, which says that it supports Win7, downloaded, installed, ICB does not recognize anything, wants 8.1 SDK.

  I'm dead in the water.  Help!

  Problem solved, sort of, by devious means, a way more harmful to complete the installation:

  Find and run the file from the DVD: D:\Distributions\CVI\Products\MSDTRedistributables_WindowsSDK_81\sdk\sdksetup.exe

  This creates successfully the folder C:\Program Files (x 86) \Windows Kits\.

  I have no idea why the installed does not automatically to my Windows 7 laptop.  I hope that NEITHER solves this problem by releasing CVI2015 SP1.

• With CVI to transfer files to cRIO 9066

  Hello

  I'm trying to copy files to a directory on a cRIO 9066.

  The method I use is to map a drive in Windows 7 and I want to copy the files with the CopyFile function in CVI.

  The reader is defined as \\ni-crio-9066-030c6bf1.local\files (I also tried http://ni-crio-9066-030c6bf1.local \files).

  With this method I can transfer files on this disc with the CopyFile function, but the transfer rate is extremely slow.

  For a 300 KB file, it will take about 25-30 years.

  During this time, my request is breaking, there is no more values in the controls or the UIRs until the copy is complete.

  I tried to disable 'Automatically detect settings' in Internet Explorer in tools > Internet options > LAN settings > connections as I've seen in a knowledge base (http://digital.ni.com/public.nsf/allkb/4EBE45E8A816B19386257B6C0071D025).

  The copy is much more rapid 1-1, 5 sec but I have a few failures of transfer. Windows told me that the transfer failed in a popup, the file in the cRIO is a file of 0ko (and CopyFile returns an error).

  In the knowledge base, they warn about the failures of transfer but I was hoping to get an error code in the CopyFile function.

  I also tried to run cmd.exe copy 'name of the source file' 'target file name' with LaunchExecutableEx but I got the same results.

  I'm in a dead end for now.

  Do you have any idea how I can transfer files between CVI and the cRIO?

  PS: I tried the WebDAV protocol in Labview and it seems fine with that (good transfer rate and no failure of transfer). But I did find this library in CVI.

  Thank you for your help.

  I'm sorry for my late reply.

  I managed to send files in the cRIO 9066 via FTP.

  I installed 'Legacy FTP Server' on the cRIO and I used the FTP API in CVI (proposed on the french forum and by the regulation).

  This solution works very well.

  I didn't want to use an external if possible API so I chose the FTP solution.

• PC (Win7 64 bit) freezes completely after some time due to the CVI 9.0.1 32-bit application: question in cvirte.dll

  I have a strange problem with my app CVI. After a while, no constant time (especially on a day or two), the PC freezes completely when running my application. Examine the system event logs, I see a lot of entries from the CVI, sometimes 8fois per second!

  Above all, it looks like the following:

  The description for event ID 0 in source CVI could not be found. Either the component that triggers this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

  If the event is on another computer, the display information had to be saved with the event.

  The following information has been included in the event:

  [14:18:42.389] [GetLWMessage] [FATAL] [.. \jsource\jn_msgs.c:672 assertion failure]: WRONG (error in the message handler: code #12689 unknown message received)

  Although the system event log is set to a size of 20 MB only and the fact that it is automatically overwrite (FIFO) itself, the PC won't be able to do in the face of this large amount of entries in line waiting.

  I searched the internet but found absolutely no clue. I searched then through my code using find in files and finally only found the following within the cvirte.dll sequence when you use "*." "*" as file extension filter:

  .. \jsource\jn_msgs.c ConvertMsgText error in the message Manager: unknown message code #% ld received GetLWMessage

  Why exactly what the system event log tells me. I wonder that there are some things Java in a related CVI runtime dll

  Know someone, any idea how I can fix this problem?

  I tried to run my application using WinXP SP3 compatibility mode, but this did not help.

  I'll try to refine the question. I will also try to recompile my application using CVI2015

  The application does not generally crushed. There are different configurations of my tool where he works a lot of days. So, I have to determine the exact circumstances. Also there is no memory leak, so does not unnecessarily increase consumption of RAM during execution.

  Any help much appreciated

  Thanks and greetings

  Hi Kyle,.

  Thanks for your response!

  In the meantime, I managed to solve the problem. Checked the date and version of the DLL runtime on the target PC, I found that they differ runtime DLLS that have been installed with my application using the distribution kit. After the reinstallation of the application, there was more no new error event log entries, so this solves the problem :-)

  Only, I wonder where these DLLs from...

  Thanks and greetings

  Manfred

• Performance of CVI 2013 SP2 with CVI 2015 - Windows XP problem

  I see that XP isn't an operating system in 2015 of the CVI.

  Most of our PC are Win7 now, but we have some legacy units which require XP due to a limitation of external controller processor.

  Is is possible to generate executables in 2015 CVI which will work correctly with the runtime of 2013?

  Alternatively, CVI SP2 from 2013 and 2015 CVI co-exist on the same PC development?

  I would not get stuck with CVI 2013 SP2 for the future just to maintain a few predictable XP-based PC.

  Hi Shr,

  I recommend reading through this community's message: https://decibel.ni.com/content/docs/DOC-23955

  Essentially, you can develop a code in CVI 2015 but set the executable to run on previous versions of the Run-Time Engine. Note that the older version of the RTE of Side-by-Side CVI is 2012. You can indeed install previous versions of the CVI on the same computer. The shared runtime will be set to the latest version. Other versions will be side-by-side. The code is not guaranteed to work with previous versions of the RTE so be sure to test the code locally before moving on to another computer.

• How to force the compilation released executable before running the distribution of LabWindows/CVI kit?

  I am new in 2015 of the CVI. I used CVI 7 and when I chose "Create the Kit of Distribution", when I was still in debug mode, Labwindows asked me to build the executable of setting before creating the Distribution Kit. This does not happen to CVI2015, and the Distribution Kit is created with the latest built executable version, although I made a few changes in my code! This is a problem since I work in debug mode and I usually forget to build the executable of liberation before calling the distribution kit, so I need CVI to do it automatically like CVI 7 did. I suppose that there is an option to do this, but I can't find. Can someone tell me please how to resolve this problem and force CVI to build the exe version before building the distribution kit? Thank you.

  Today, I've solved quite simply create a new distribution. The previous like unsing was automatically imported by CVI7 project. By creating a new distribution, now when I change something, CVI ask me if I want to build the release. So I did not understand the problem but I solved it by editing a new distribution kit.

• CVI 2013 SP1 crashes when opening file

  LabWindows 2013 SP1 has suddenly stopped working on my PC.  Any time I try to open a file, or by clicking Browse on the home page, by clicking the open file icon, or by selecting file - open or file - save as from the main menu, I get the message popup that says ' LabWindows/CVI 2013 has stopped working '.

  By clicking on "display characters invisible problem" shows this:

  Signature of the problem:
  Problem event name: BEX
  Application name: cvi.exe
  Application version: 13.0.1.201
  Application timestamp: 52d6eeab
  Fault Module name: CVI.dll
  Fault Module Version: 13.0.1.201
  Timestamp of Module error: 52d6eea1
  Exception offset: 00a4ecd0
  Exception code: c0000409
  The exception data : 00000000
  OS version: 6.1.7601.2.1.0.256.48
  Locale ID: 1033
  Information has additional 1: 417
  More information 2: 417afcd3ce602885d582521ac0f0405e
  3 more information: 39bb
  Additional information 4: 39bb24ea28d79f3c45538f96792cdc59

  These values are always the same.

  I am running Windows 7 Professional, SP 1.

  If you just did a normal installation of CVI 2015, it might still be interesting to try a force reinstall. It is possible that there is a corrupt file of CVI 2013 somewhere.

  Take the information to the same post here, it seems that this issue might be specific to your Windows configuration.

• Adding a new user with Labwindows/CVI

  Hello

  I really need help I'm strugggling to find a solution.

  I want to add a new user and view the list of users using CVI?

  When adding the user, I would like to add the name and the password as well.

  I don't want to use this TS_EngineDisplayNewUserDialog I want to be done with the user input from all this information that I receive information from Active Directory.

  Is this possible?

  Kind regards

  Shakeel

  HI RaviShrigiri

  Thanks for the reply.

  I found what I needed. http://forums.NI.com/T5/NI-TestStand/can-I-use-Active-Directory-to-validate-users/TD-p/3299366

  I added the creation of a new user and add to a group in the aforementioned project.

  Kind regards

  Shako

• Trying to shutter AWG out digitizer (CVI)

  I work with an arbitrary wave generator NI PXI-5421 and digitizer PXI-5211.

  With CVI, I let a waveform with the AWG output 500ms after the scanner is triggered.

  Is this possible?

  To set up triggers, I used the following two functions:

  • niFgen_ConfigureDigitalEdgeStartTrigger (AWGHandle, "PXI_Trig1", NIFGEN_VAL_RISING_EDGE);
  • niScope_ConfigureTriggerOutput (ScopeHandle, NISCOPE_VAL_START_TRIGGER_EVENT, NISCOPE_VAL_RTSI_1);

  However, I was not managed by entering the ARB to produce anything once the scope is triggered.

  I'm missing steps crucial or is - something that cannot be done in the way wherein I try?

  Thanks for your help.

  Hello

  I think I see the problem. It seems, it's that you configure your digitizer and fgen correctly if they were going to be run separately, except for one thing. In this section:

  Digitizer of config.

  ....

  Set up the output trig for digitizer to trigger AWG
  error | = niScope_ExportSignal (ScopeHandle, NISCOPE_VAL_START_TRIGGER, "", NISCOPE_VAL_RTSI_0);

  you export the start trigger, which is in fact sent immediately after you call the niScope_InitiateAcquisition() function. All this is done before you set up your AWG, so start trigger is already sent before calling the niScope_InitiateGeneration() to the working group. Also, I suppose that you want to trigger off the trigger of reference that you configure your call to the niScope_ConfigureTriggerEdge() function. I have attached a picture of the help file for this function.

  There are two things you need to do to solve this problem.

  1. you need to change this line: / / output trig to trigger AWG scanner configuration
  error | = niScope_ExportSignal (ScopeHandle, NISCOPE_VAL_START_TRIGGER, "", NISCOPE_VAL_RTSI_0);

  to export the reference trigger instead: / / output trig to trigger AWG scanner configuration
  error | = niScope_ExportSignal (ScopeHandle, NISCOPE_VAL_REF_TRIGGER, "", NISCOPE_VAL_RTSI_0);

  2. in addition, you must move the niScope_InitiateAcquisition() function to be called after the function niFgen_InitiateGeneration():

  "....

  Activate the AWG output
  error | = niFgen_ConfigureOutputEnabled (AWGHandle, '0', VI_TRUE);

  Output of arm
  error | = niFgen_InitiateGeneration (AWGHandle);

  Acquisition of digitizer Begin
  error | = niScope_InitiateAcquisition (ScopeHandle); "

  According to me, who must take care of it.

  Chris W

• How to convert the file with VI for LabView .lib to CVI?

  Hello

  I have the .lib file for my lock in the amplifier. The lib file is written for labView and already contains a visual interface (like ActiveX). The point is that I need this file for programming in CVI (8.5). How can I convert a LabView ICB .lib?

  Thank you.

  Denis.

  You said that you had a .lib file and in fact you have an llb file. There is a huge difference between an "i" (eye) and a 'l' (ell).

  There is a LabVIEW Instrument Driver Export Wizard but it's only for new pilots of project lifestyle and you need LabVIEW. There is no other way to convert a LabVIEW driver to a driver of the CVI. If the LabVIEW driver uses methods and properties of the ActiveX, you will need to write the same thing in CVI.

• create a CVI DLL to be called in LUA

  Hi all

  I am a user of LabVIEW and LabWindows again. Currently, I have to plan a project that needs to integrate the software into different languages.

  The situation is that I have a LabVIEW VI must be integrated into a GUI written in LUA. I'm now thinking is it possible first to convert LabVIEW vi or project first in CVI DLL and call him in LUA. Does anyone have an experince / advice on this? I found that it is possible to use LUA in LabVIEW with LuaView. What about the reverse?

  Any pointer will be highly appricated.

  See you soon,.

  Sparkle

  Hello

  I'm Ed National Instruments Applications Engineering. I was forwarded your query which I am happy to help you.

  In my view, that the following article should provide you with the necessary steps to develop a DLL into a LabVIEW project:

  http://digital.NI.com/public.nsf/allkb/A3804F88FCDB1E6286257CE00043C1A7

  After which, if LUA is capable of calling C DLL then you should then be able to use the DLL as you would to a C DLL. Of which some research described you may need a module of the stack overflow page that I've also linked below and also a module that is suggested to use on this page of stack overflow:

  1. http://stackoverflow.com/questions/2835716/how-do-i-call-functions-inside-c-dll-from-lua

  2. http://www.nongnu.org/cinvoke/lua.html

  Best regards

  Ed

• LabWindows CVI and debugging dll MSVC ++

  We use a written LabWindows/CVI DLLS in the code for Teststand module. This DLL calls a DLL written in MSVC ++.  Is it possible to use the debugger of Labwindows/CVI debug this DLL MSVC ++ (if this DLL MSVC ++ is built with 'good' options)?  Or is possible only using the environment of development MSVC ++?

  Hello mkossmann,

  The CVI compiler generates different types of than MSVC debugging information.

  The debugger CVI doen't understand the debugging information generated by MSVC, so you cannot debug the dll compiled in MSVC.

  Constantin