application in labwindows/CVI 6.0 error

Similar Questions

• LABWINDOWS CVI 2013 error: bad image in IValidateImage

  Hello

  travel form CVI 2012 to CVI 2013 I Get a sequence of the below errors in the application log.

  The errors seems to be generated whenever I have fly over the screen of the GUI of my application. After a sequence of these errors the application hang.

  Note that:

  -J' already installed the latest patch available for 2013 CVI

  -l' error was not present when compiling with CVI 2012

  -l' error is present also, when you distribute the application o windows XP

  Thank you

  Ezio Riva

  ERROR in widows application log

  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:

  [15:24:52.119] [IValidateImage] [FATAL] [.. \mgsource\image.c:9085 assertion failure]: FALSE (bad image in IValidateImage)

  Hi calou,.

  Do you agree with the workaround solutions provided by Daniel?

• uninstaller application, created with Labwindows CVI, work of doesn´t after the upgrade to version 2010

  Hello

  I worked with Labwindows CVI 2009 without problem, but after the upgrade to the 2010 version, I have the following problem:

  When I m going to run the unistaller, Panel configuration Windows or directly from the icon uninst.exe, it doesn´t work. The PC thought for a few seconds and does nothing, and it happens with all applications that I build with Labwindows CVi 2010.

  Thank you

  Asier

  Hello-

  You install these distributions on a non-English system?  If so, the first thing to try is the workaround solution listed on this known issue.

  The known problem lists only the Italian OSs because inconvenient BONE, but in fact, it can happen on of many different non - English OSs. I will update the text accordingly the next time I update the list of known issues.

  NickB

  National Instruments

• Always get errors trying to control power 7651 YOKOGAWA on Labwindows/CVI

  Hello

  I'm trying to set the voltage on YOKOGAWA 7651 feeding through labwindows/cvi. I've set up a digital slide on my UI with callback function "yoko7651dcvolts" and the name of the constant "YOKO7651DCVOLTS".

  I always get this error when I run my program:

  "FATAL RUN-TIME ERROR: "DcSource.c", line 53, col 65, thread id 0x00001F3C:   Invalid argument type: found 'pointer to double', expected 'pointer to int'."
  

  This error indicates the third argument to the GetCtrlVal function below. The lack of program/compiler pass the variable "yoko1volts" as a whole, but I want to (and should) be able to settle the tensions as floating numbers.

  Of more, even when I said "yoko1volts" as a whole, it stills does not work. All I get is zero, zero and zero... on the power meter whenever I press the digital slide.

  This is the section of the C code which is problemic:

  int CVICALLBACK yoko7651dcvolts (int panel, int control, int event,        void *callbackData, int eventData1, int eventData2){    double yoko1volts;    switch (event)    {        case EVENT_COMMIT:        GetCtrlVal (yoko76511Panel, YOKO7651_1_YOKO7651DCVOLTS, &yoko1volts); // to read the values entered on the numerical meter on the user interface
  
          yk7651_set_volts (yoko76511Panel, yoko1volts); // set the entered values as voltage on the instrument
  
          break;    }    return 0;}
  

  It's the h-file related:

  #define  YOKO7651_1                       4#define  YOKO7651_1_YOKO7651SWITCH        2       /* control type: binary, callback function: yoko7651switch */#define  YOKO7651_1_YOKO7651DCVOLTS       3       /* control type: scale, callback function: yoko7651dcvolts */
  
  
  

  Please help, how can I solve this problem?

  All pilots (including feeding YOKOGAWA 7651) are correctly installed and mounted. In fact, I can successfully turn the power supply on and off with the code below:

  int CVICALLBACK yoko7651switch (int panel, int control, int event,        void *callbackData, int eventData1, int eventData2){    int yoko7651switchstate;    switch (event)    {        case EVENT_COMMIT:        GetCtrlVal (yoko76511Panel, YOKO7651_1_YOKO7651SWITCH, &yoko7651switchstate);        SetCtrlVal (yoko76511Panel, YOKO7651_1_YOKO7651SWITCH, !yoko7651switchstate);        yk7651_output (yoko76511Panel, !yoko7651switchstate);            break;    }    return 0;}
  
  
  

  It is just setting the voltage on the power supply which is very problematic. Any help is appreciated... Thank you.

  I second opinion Al of a disconnection between the UIR and the variable that contains the handle to the Panel.

  As a side note, I noticed that the problematic line reads the value of the controll which callback is executed:

  #define  YOKO7651_1_YOKO7651DCVOLTS       3       /* control type: scale, callback function: yoko7651dcvolts */
  
  int CVICALLBACK yoko7651dcvolts (int panel, int control, int event,        void *callbackData, int eventData1, int eventData2){    double yoko1volts;    switch (event)    {        case EVENT_COMMIT:        GetCtrlVal (yoko76511Panel, YOKO7651_1_YOKO7651DCVOLTS, &yoko1volts); // to read the values entered on the numerical meter on the user interface
  
          yk7651_set_volts (yoko76511Panel, yoko1volts); // set the entered values as voltage on the instrument
  
          break;    }    return 0;}
  
  

  In a situation like this, I will try using GetCtrlVal (Panel, control, & yoko1volts); Instead, which should get rid of all the problems in the control panel manage / control ID.

  Despite this solution works, anyway I'd be deep into the problem like a bad Panel can lead to erratical behaviors in other parts of the program.

• Error selection LabWindows CVI Card Configuration

  I am trying to enter the Lab Windows CVI 2012 of TestStand 2012.  When I try to configure LabWindows CVI adapter to

  c:\Users\Public\Public Documents\National Instruments\TestStand 2012\Adapter Support\CVI\tscvirun.prj the window changes the path to

  c:\Users\Public\Documents\National Instruments\TestStand 2012\Adapter Support\CVI\tscvirun.prj and displays the message that it cannot find the file.  I use Windows 7 if that makes a difference.

  Hi herbertwatson,

  I have attached my tscviprj.ini. I have two TestStand 2010 and 2012 TestStand, installed on my machine but the ini is only in the 2010 directory. It is possible, he just needs to be an ini for TestStand work with all facilities CVI. Try to place it in the same directory as your tscvirun.prj for 2012.

  If this does not work, it may be useful CVI, TestStand and then reinstall.

  Kind regards

• passage of data container of teststand labwindows/cvi handle error

  Hello

  I'm moving a container of teststand parameter to labwindows/cvi using this UI API messages following this code created by Peter-r. example:

  https://decibel.NI.com/content/docs/doc-23332

  It is a great example to start with, but as I run using worldwide debbugging lying on the build options, I see that the handle of the containerData object is not released. If I add the CA_DiscardObjHandle (containerData) anywhere in the project, it gives me a FATAL_RUN_TIME_ERROR. This handle must be released? If I call a bunch of these user interface Messages, it will cause memory problems? My code runs right now, great, but I don't want to face a problem of memory later.

  Any help on this will be great!

  Thanks in advance.

  -Luis

  When you add throw it? Maybe you add it to the wrong place. You must add it just after the CA_FreeMemory() called as follows:

  CA_DiscardObjHandle (containerData);

  It should work.

  You can also try the following instead of the functions:

  CA_CreateObjHandleFromInterface (var, & IID_IUnknown, 1, LOCALE_NEUTRAL, 0, 0, & containerData);

  I think that you will still need to get rid of the objhandle when using this API.

  -Doug

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

• 6632A HP - tension - Labwindows CVI

  Hi all

  I'm trying to settle the tension of HP 6632 A with Labwindows CVI. The initialization succeeds (1) If no application ID and no reset command is sent and fails (2) if the two is sent (error occurred during the transfer of Bus) (see update below). Then when I try to set up/set the output by using the function below, I get an error BFFF0038 code - Bus error occurred during the transfer (1) or BFFF000E - invalid session handle (2).

  I checked tha MAX and match the GPIB address there with what is represented on the food. It also responds to the request to id it.  I use the driver of instruments provided by OR to talk to the device by the USB-GPIB converter of NOR.

  Am I missing a step here? I set up the device in a certain way before use?

  Thank you!

  Initialization (send request Id and reset the order)
  
      int error_int = hpe363xa_init ("GPIB::0 (', VI_ON, VI_ON, & g_instrumentHandle1);
  
      char chaine_erreur [100];
  
      FMT (chaine_erreur, "%x", error_int);
  
  MessagePopup ("Return Value Init", chaine_erreur);  <- error="" bfff0038="" bus="" error="" occurred="" during="">
  Config to activate the output
  
      error_int = hpe363xa_configOutput3632 (g_instrumentHandle1, VI_OFF);
  FMT (chaine_erreur, "%x", error_int);
  
      MessagePopup ('Return value Config', chaine_erreur);  <- error="" bfff000e="" invalid="" session="">
  Set the voltage to 12 V
  
      error_int = hpe363xa_outputSetOperate3632 (g_instrumentHandle1, VI_OFF, 12.0, 1.0, VI_ON);
  FMT (chaine_erreur, "%x", error_int);
  
      MessagePopup ('Return Value Set', chaine_erreur);  <- error="" bfff000e="" invalid="" session="">
  
  

  Device: HP 6632 has DC power supply by Labwindows CVI.

  Connection: NI GPIB-USB connection Cable

  Pilot: Labwindows Plug & Play

  Language: Labwindows 2013

  OS: Windows 7

  Edit1:

  I just realized that I'm not sends a request id and a reset command during initialization of the device. I've updated the code above. Unfortunately, I get an error code if I do and the devicehandle is not set! The game features following fail later.

  You also use the bad for a HP6632A instrument driver. The hpe363xa driver is for models E3631A, E3632A and E3634A.

  You must instead use the driver available to ... http://sine.ni.com/apps/utf8/niid_web_display.download_page?p_id_guid=E3B19B3E929C659CE034080020E748 .

• DLL for LabWindows/CVI 8.0 with the bool data type

  Hello

  I want to use a new SWIR camera in LabWindows/CVI 8.0 (Windows XP 32bits).

  The company delivered with the camera produced a 32-bit dll by using Microsoft Visual C++ 2010. The .dll and .lib and .h files include a working SDK/API (some functions with the bool data type)

  Compilation-online syntax error, variable Boolean is not a data type in LabWindows/CVI 8.0

  Generate the import of DLL-online syntax error library

  I tried to convert bool char (typedef unsigned char bool => no more syntax error but the functions does not work.)

  What can I do?

  Martin

  Hello again, Naumann!

  Microsoft Visual C++ 2010 represents Boolean using 1 byte, as stated by MSDN: https://msdn.microsoft.com/en-us/library/tf4dy80a(v=vs.100).aspx

  I guess that you import C++ functions using the syntax for extern "C". Otherwise, because of the C++ name mangling wouldn't you able to bind C++ library against your code CVI.

  You can also specify how you import C++ functions?

  In addition, because you have not described the problem as a corruption of heads or runtime error, I guess the C++ library function is called correctly the CVI. That said, I tend to believe that the problem is not really in the mechanism of interaction of C/C++, but in the C++ library. If you would start calling a dummy C++ function returning an integer from a simple CVI application that should work, because redefine bool in CVI 1 byte must ensure that settings are correctly transferred onto the stack.

  If you need to create a wrapper function of C++ that is not using bool and calls the C++ function, I expect to return the same result.

  Maybe you are missing a few prior initialization steps required? The provider of the camera also comes all example code?

  Best regards!

  -Johannes

• DirectInput with LabWindows/CVI

  Hello

  I'm trying to use DirectInput to obtain data on the position of a USB joystick in LabWindows/CVI. CVI 2013 comes with headers and libs for direct entry into its subfolder of the sdk and the DirectX SDK comes with a very simple example.

  However, already the first step in opening creating a directinput handle fails to compile - it is essentially copied verbatim from directInput documentation or the joystick sample provided with the DirectX SDK.

  #include
  #define DIRECTINPUT_VERSION 0x0800
  #include 'dinput.h.

  int main (int argc, char * argv [])
  {
  LPDIRECTINPUT8 di;
  HRESULT hr;

  HR = hr = DirectInput8Create (GetModuleHandle (NULL), DIRECTINPUT_VERSION, IID_IDirectInput8, (VOID *) & di, NULL);

  return 0;
  }

  60, 42 error: from 'const GUID' (aka "const struct _GUID") to the inconsistent type parameter ' const IID *' (aka ' const struct _GUID *')

  18, 1 in file included from c:\Users\tpaprotta\Documents\National Instruments\CVI\Command-line Application.c:18:

  "dinput.h" (2682,83) c:\program files (x 86) \national instruments\cvi2013\sdk\include\dinput.h:2682:83: Note: passing argument to the parameter "riidltf" here ".

  The same code compiles without problem under Visual Studio 2012.

  Therefore, it is / was a number of questions. Yes, the example in question is C++, so instead of the call

  DirectInput8Create (GetModuleHandle (NULL), DIRECTINPUT_VERSION, IID_IDirectInput8, (VOID *) & di, NULL);

  To call

  DirectInput8Create (GetModuleHandle (NULL), DIRECTINPUT_VERSION, & IID_IDirectInput8, (VOID *) & di, NULL);

  (IID_IDirectInput8 is defined differently depending on if C or C++ calls).

  However, if we make this change, the _IID_IDirectInput8 symbol is not found. The symbol is not in dinput8.lib (which is included with CVI), but rather in the dxguid.lib (which I couldn't find in the records of OR). It is distributed with the DirectX SDK - so I'm now a link against it. I'm curious, however, why NOT distribute dinput8.lib / dll and not other required libraries, which seem to be necessary to use.

• Executable built with CVI 8.1 error-5093, the analysis library is not found

  Upgraded to 8.1 Labwindows/CVI of Labwindows/CVI 7.0 development machines. An earlier application was built using the ICB 7.0 and installed on a test computer. The same code built with CVI 8.1 is any error during execution of the function stdev, 5093 error code has been generated. (From analysis.h: LibraryNotFoundAnlysErr =-5093, / / the analysis library was not found.) Tried to build a facility with 8.1 and installation on the test computer and application errors still executing the stdev function. Back to the same application, but built with CVI 7.0, it works fine. Am I missing something with the build in 8.1 options? Or is it something in the workspace or project? Please notify. Thanks in advance

  Hi Tommy,.

  In CVI 8.0, the implementation of the analysis library has changed a static library that is linked to your .exe in a DLL that must be loaded when running. If you rebuild your source code and you want to deploy to another machine where the CVI environment is not installed, then you must re-create an installer in CVI 8.1 distribution, so that he can pack the analysis as well as your program library.

  You can confirm whether the analysis library is installed by searching for C:\Program NIUninstaller Instruments\Shared\Analysis\nianlys.dll in your target machine (although it is not enough to simply copy this file manually).

  When you create an installer in the CVI, be sure that, in the tab drivers & components in the dialog box change Installer , support of analysis element under the Group of LabWindows/CVI Run-Time Engine is checked.

  Luis

• Where can I find NEITHER-HSDIO SMU 6556 LabWindows CVI examples?

  Greetings!

  I am looking for examples LabWindows CVI or a help file that shows the function or api calls to control the attributes of progrannable of the HSDIO SMU 6556/6555.

  Ken Grohman

  Hi Ken;

  "' You can find examples for the NOR-HSDIO in the example LabWindows CVI Finder by clicking on help > NOR example Finder and navigate to the material input and output" Modular Instruments ' NOR-HSDIO; "" "" or you can search in Start "all programs" National Instruments "NOR-HSDIO ' examples.

  http://zone.NI.com/reference/en-XX/help/370520J-01/HSDIO/using_ni_hsdio_in_labwindows_cvi/

  Just make sure that when you installed the driver, you have also installed the Application Development Enviroment Support for LabWindows CVI, otherwise the examples will not be there.

  Best regards;

  Pedro Muñoz

• Windows 7 Starter Edition and LabWindows/CVI

  Hello

  I have two questions/problems with an application written with CVI 9.0.1 and CVI 2009 respectively Windows Vista professional.

  First if I have a distribution of my software package (or a version of a sample distribution package) and you want to install it on a netbook with Windows 7 Starter Edition Setup displays the following error message:

  "This product does not support Windows Starter Edition."

  Is this just a restriction of the installation program, or CVI will never support the Starter Edition?

  We often sell these netbooks as well as our units of measurement as an input/output device. But I think that in a future close all netbooks will use Windows 7 instead of XP and above all the Starter Edition.

  So if it is not taken in charge this will help upgrade netbooks to Windows 7 Home Premium? I have already tested Windows 7 Professional and it works, but I do not want to install Professional on a netbook...

  My second question also the Starter Edition.

  I'm building a kit of distribution of working space example "interp.cws" (curve fit and Interpolation) with the runtime engine installed in the application directory. If I run the .msi instead of the setup.exe package then the software has been installed on the system.

  So I can run the software, and it seems to work. But if the software calls a function in the library of analysis advanced (for example, the Spline Interpolation) it does not work. With remote debugging I discovered that there was a nonlethal runtime error "the analysis DLL library is not found or could not be loaded" during the spline function calls.

  The same sample works fine with Windows 7 Professional.

  Is this also a restriction of the CVI, and will be the reason (or one of the reasons) did not support the Starter Edition?

  Or is there a workaround for these errors?

  Best regards

  M.S.

  National Instruments supports Windows 7 Starter; However, just as now, our facilities are defined to stop any Windows Starter Edition is detected.  This is because XP and Vista Starter Editions were marketed to emerging markets and had severe limitations of performance.

  You should make sure that your specific product supports Windows 7.  If this is the case you can follow the instructions in the knowledge base

• LabWindows CVI Full recommended OI does not start

  I made an installer of deployment Teststand-2013. On a target PC (Windows 7 64-bit) it works fine. But on another target PC starting the Labwindows/CVI Full IO recommended (attached screenshot) fails with an error-145 when trying to load testexec.uir. Both targets have Windows7 64-bit and Office 2010 installed. How will I know what ActiveX control is missing or damaged on the second PC?

  I found http://digital.ni.com/public.nsf/allkb/9894BE2B832B7FDE86256ECD00041172. But the Office is installed, and ActiveX Control Pad is obsolete and incompatible for Windows7 64 Bit and is no longer available from Ms.

  mkossmann,

  You can use the option "Hide the license dialog box" on the Installation Options tab. This will not prompt the user to activate TestStand until they try to open the software after installation. What is the desired behavior?

• Announcement: LabWindows/CVI 2015 beta program

  Hello world!

  I am pleased to inform that the beta program of LabWindows/CVI 2015 is now open for new applications for registration. As a member of the beta program, you'll be among the first to use the next version of LabWindows/CVI, giving you the opportunity to give feedback of NOR and test your existing projects against the latest features of LabWindows/CVI.

  If you are interested in participating in the program, we encourage you to the request to participate by visiting www.ni.com/beta and choosing to sign up for the beta of LabWindows/CVI 2015 in the menu dropdown. All previous beta users must re-register for the beta of LabWindows/CVI for we ensure that have up-to-date information.

  We look forward to hear from you!

  Best regards,

  Hi all!

  The beta version of LabWindows/CVI 2015 concluded.

  Thank you