LabWindows/CVI cannot compile a simple code

Hi all!

It's looks funny but LabWindows/CVI-9.1.0(427) cannot compile a simple C code

XML.h

void f();

XML.c

#include 'xml.h.

typedef struct
{
int bar;

} foo;

void f()
{
int Baz = 0;
If (!) Baz) baz = 1;
foop foo;
return;
}

It's not a bug, you make a statement block to a variable foop which is not allowed in the standard ANSI C89.

You can activate the C99 extensions with a pragma if you want this to work in CVI 9.1

Menchar

Tags: NI Software

Similar Questions

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

  • frmcmp cannot compile the modules containing SQL code that connected to the database

    Hello

    I checked several hundred messages of the forum on the net without finding a solution.

    I have a Linux server with 11.1 WebLogics (11 GR 1 material) and FormsRuntime installed.

    I am logged in as root.

    I put all the environment variables based on the values in default.env.

    In addition, I updated TERM and ORACLE_TERM vt220. And TNS_ADMIN to the location of the sqlnet.ora and tnsnames.ora.

    I compiled a simple .pll containing only the following code:

    IS test PROCEDURE

    an INTEGER: = 0;

    BEGIN

    a: = 1;

    END;

    command:

    frmcmp_batch module = TESTLIBPLAIN.pll userid=myuser/mypassword@mydb module_type = LIBRARY output_file = TESTLIBPLAIN.plx compile_all = Yes = Yes = No. batch connection

    result: successful compilation. generated .plx.

    now, I'm trying to compile an another .pll containing just the following code:

    IS test PROCEDURE

    an INTEGER: = 0;

    BEGIN

    Select 1 in the doubles.

    END;

    command:

    frmcmp_batch module = TESTLIBSQL.pll userid=myuser/mypassword@mydb module_type = LIBRARY output_file = TESTLIBSQL.plx compile_all = Yes = Yes = No. batch connection

    result: error:

    "

    11 forms (form of the compiler) Version 11.1.1.3.0 (Production)

    Copyright (c) 1982, 2010, Oracle and/or its affiliates.  All rights reserved.

    Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production

    With partitioning, OLAP and Data Mining options

    PL/SQL Version 11.1.0.7.0 (Production)

    Oracle V11.1.1.3.0 - Production procedure generator

    Oracle virtual graphics system Version 11.1.1.3.0 (Production)

    Oracle Multimedia Version 11.1.1.3.0 (Production)

    Oracle tools integration Version 11.1.1.2.0 (Production)

    Common tools Oracle area Version 11.1.1.3.0

    Oracle CORE Production 11.1.0.7.0

    Compile the library TESTLIB.

    Invalidate the body TEST procedure...

    Compilation of body TEST procedure...

    ERROR on line 5, column 1 0

    Ignored SQL statement

    Library TESTLIB closing...

    Errors on TEST:

    PL/SQL ERROR on line 5, column 1 0

    Ignored SQL statement

    Could not generate the library.

    FRM-30312: unable to compile the library.

    "

    the two libraries differ by having used SQl commands or not.

    I tried to compile some more complex .pll and .fmb containg the SQL code. I get similar error messages. The messages that I receive for each module are the same, I would get when compiling the module with FormBuilder 9i (Windows) without being connected to the database.

    So my first thought was, this frmcmp_batch is unable to connect to the database.

    BUT:

    From frmcmp_batch with an invalid user, password, or database name not existing (resp. not in tnsnames.ora), results in appropriate error messages (not found TNS, refusal to sign etc.).

    With myuser/mypassword@mydb I don' t get this kind of messages.

    sqlplus myuser/mypassword@mydb works.

    myuser can access all objects in the database mydb.

    mydb tnsping works.

    When I check v$ session on mydb while (!) frmcmp_batch is running, I see that it is in fact a db session, created from myuser: DB-User = myuser, terminal = myappsever, osuser = root, remote process = frmcmp_batch.  And State of the current session of the db is ACTIVE.

    As a result, frmcmp_batch fails with error messages that I expect that when there is no connection to the base, if it is connected!

    Any ideas what could be wrong with my setup?

    Help appreciated.

    Jean

    I found the solution. Seems, fmrcmp 11g can connect to, but compiles not on the 9i database. With the help of a Database 11 g resolves the problem :-)

  • 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

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

  • JNI and Labwindows/CVI linking problem

    I am trying to connect to the server in Java through LAbwindows CVI DataSocket.

    I am able to create a dll. Everything works fine with no error in compilation or execution, but when I run the DS_OpenEx cannot return a native class.

    If anyone can help me with the problem.

    Thank you

    Hello

    Could you better clarify the implementation that works properly and implementation that does not work properly?

    1 are you connected to the DataSocket with Java source code and you are trying to communicate through this source of Java through LabWindows/CVI?

    2 are. what environment you able to successfully create a DLL?

    3. can indicate you what environment survey code error and what this code?

    ADri - K

  • How implement not checking in LabWindows/CVI interchangeability?

    Hello

    I'm creating a driver of IVI - C using LabWindows/CVI 2012. I used IVI Instrument Driver Tool Wizard and he created most of the code to support inherent attributes and functions of the IVI.

    I do not plan to support the verification of interchangeability in option and according to the specifications of the IVI (IVI-version 2.1, 3.2 section 5.21):

    «If the IVI specific driver does not implement verification of the interchangeability, the specific driver returns the unsupported value error when the user attempts to set the attribute Interchange check true.»

    It would be a simple task if I could change the reminder of the writing of the Interchange attribute check. However, LabWindows/CVI does not any change of an inherent attribute. How can I make the driver returns the value not supported error when the user attempts to set the attribute Interchange check true?

    Any help is appreciated!

    Thank you.

    Hello buckhorn,.

    From your statement, I tried to 'Edit' the reminder of the writing of_ATTR_INTERCHANGE_CHECK attribute and seems it worked. Here is part of the codes.

    1. Create a ViBoolean write callback function:

    static ViStatus _VI_FUNC agx2k3k_InterchangeCheckWriteCallback(ViSession vi, ViSession io, ViConstString repCapName, ViAttr attributeId, ViBoolean value)
    {
        return IVI_ERROR_INVALID_VALUE;
    }
    

    2. Add the callback function to ATTR_INTERCHANGE_CHECK:

    checkErr (Ivi_SetAttrWriteCallbackViBoolean (vi, AGX2K3K_ATTR_INTERCHANGE_CHECK, agx2k3k_InterchangeCheckWriteCallback));
    

    I hope that it might help for your case.

    Thank you

    -Charles

  • problem with LabWindows CVI

    Hello I m trying to create a Setup program for an application created in a previous version of Labwindows CVI which one don't know locks I get just the file sources, I m working with the 2010 version, the problem is that the application is running in debug mode but when I run in release mode the application does not work only the icon in the taskbar is indicated but the GUI never appears, someone can help me with this

    Thanks for your help, the problem was not with the code and was not with the RT engine version, was a misconfiguration in the compilation release configuration, I myself do not add external sources dll´s and lib´s in the plug-ins option in the settings of the target

  • LabWindows CVI 2010 and GetProcessAddress()

    I use v10.0.1 Labwindows CVI 2010 after the upgrade to version 2010 CVI v10.0.0. After the upgrade, I have a compilation error of a statement that compiles fine in the previous version. The error is:

    «= Operands are types illegal "pointer to __stdcall int function (int, pointer to char, char pointer, pointer to char, int, pointer to char, pointer to char)' and"FARPROC".»

    What causes this error is the following statement in the code:

    my_FP = GetProcAddress (dll_handle, "DLL_FUNCT");

    and the definition of my_FP is:

    int __stdcall (* my_FP) (int x, y of char [], char [z], char * m, int g, char A [], char [] B);

    (the parameters and the function names have been changed for simplicity)

    As I said, this line compiles fine in the 10.0.0, version but not in 10.0.1. Y at - it a specific update to the compiler that will cause this error? What can be done to fix this?

    I thank very you much for your time and your help.

    You are right. This was caused by a change in the SDK Windows CVI headers that took place in the 2010 SP1 version. The change has been associated with bug fix #275934. Unfortunately, this bug fix introduced this unwanted side effect to require a cast for any function that returns a function (such as GetProcAddress) FARPROC poinrter. On reflection, this side effect is unacceptable and needs to be fixed in the next version. This is followed internally with bug ID #336341.

    I'm really sorry for this inconvenience. Until the problem is solved using the typedef & cast you have already implemented is a valid alternative.

    Another solution, if you're worried about other projects or other functions, where this error can also appear, is to edit CVI2010\sdk\include\windef.h and replace the following definitions of FARPROC (line 226 and 230, respectively):

    typedef INT_PTR (away from WINAPI * FARPROC) (void);

    typedef int (away from WINAPI * FARPROC) (void);

    with:

    typedef INT_PTR (away from WINAPI * FARPROC) ();

    typedef int (away from WINAPI * FARPROC) ();

    This will avoid the problem throughout a facility given to the CVI.

    Luis

    NEITHER

  • How to make a manager of UIMessage of PostStep of TestStand in LabWindows/CVI 8.1?

    How to make a manager of UIMessage of PostStep of TestStand in LabWindows/CVI 8.1?

    Hi all

    I have a problem of capture UIMessages motor TestStand for a DLL called from a sequence.
    A search on the forum gave rise to 2 posts on this topic or a similar problem, but with LV and unfortunately, they were not solved.

    TestStand Event 13 - UIMsg_StartInteractiveExecution is not captured by LV operator Interface

    Problems with ActiveX in LabVIEW 7 reminders

    In detail, I want to activate a DLL access the TestStand SequenceContext (variables) in phase of execution of the step.
    A pop-up Panel could then display variables such as the spy does, but more flexible user defined Panel window.

    He is currently working with a periodic timer that causes racing with TestStand conditions while monitoring the variables.
    It works 99%, but I want it to work 100%.

    I found the
     TS_ExecutionAddPostStepCustomUIMessage()
    to indicate to the engine, I want to be informed of one end of the stage with my private UIMessage.
    Next is to implement a callback with
     TS_EngineRegisterUIMessageCallback()
    to retrieve all UIMessages and filter my private.

    Sounds good - works for the capture of events, but TestStand locks and does not continue execution and not to carry out handling
    any operation of the user interface. I have tried 4 solutions (see code), no difference in the result.

    I must kill TestStand to get out of it.

    Attached you will find a stripped down a simple example to reproduce the problem.

    I'd appreciate any help.
    Thanks in advance.

    Kind regards
    Tom

    TestStand 3.5.0
    LabWindows/CVI 8.1.0

    Hello Nick,

    Thank you for your quick response!
    Yes, you are right. That works, I tried today, but...
    isn't this practice as I want it to be. The programmer of a sequence (not me) should take care of the good implementation of a reminder of PostStep to make it work, although he just wants to make a popup. It is not a real problem, but if you use a TestStand MessagePopup command, expected to implement another somewwhere command to make it work. Don't get me wrong, it's just that I don't think that it is a clean solution. And... at least, it is slower.
    I found a tutorial OR a LabView solution for this and two people were asking a LabWindows version. Of course, some are
    interested in this solution. These 2 functions, that I mentioned in my post should work somehow, otherwise they are fools.
    I would really like to know how.

    Thanks again anyway. I'll use your suggestion, if I don't get the problem solved at the root.

    Kind regards
    Tom

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

  • How is for NI LabWindows/CVI? How is it likely to be in the future?

    Hello

    How is changing in favour of NI LabWindows/CVI?  If it's good now, expect the same level to continue in the future?

    Thank you

    Gayle

    Hi Gayle,

    To answer your question re using LabVIEW OO with CVI, they are quite different technologies and really cannot be used in conjunction with each other. That said, if you put the code of the BCI in a DLL, you can call in the LabVIEW DLL using a node call library feature. If this is not clear things up for you, please let us know a little more on what you ask.

    As an observation, I am happy to learn that many of you have had good experiences with our support! Certainly, we do our best to provide excellent support and strive to help you succeed with your applications.

    Best regards

    John M

  • LabWindows CVI RS-232 is not fast enough

    Hello

    Is it possible to write a C program which takes RS-232 data buffers and prints it on the screen?

    I ask this question because I write a program in LabWindows CVI and the data is not correct. I used SimpleTerm Gold to see what data are supposed to look like, but CVI misses some. I believe it is not fast enough and therefore lack of data.

    A C program (do not use the functions or reminders CVI) would be possible and better?

    Is it possible to make the CVI to work faster? I changed the environmental policy of the previous "do not sleep". There are two ComRdTerm because we're not getting all the other packages.

    Rate 115200 baud, no parity, 8 data bits and 1 stop bit. Most of the data I receive are 313 bytes and the smallest is 17.

    Any help would be MUCH appreciated as I am completely puzzled.
    Thank you

    Code is below.

    OpenComConfig (com, "COM9", 115 200 Baud, 8, 1, 0, 1024, 1024); / /< opens="" serial="" ports="">
    SetComTime (com, 0); / /< sets="" serial="" port="" to="" never="" time="" out="">
    T0 = clock(); / /< calculate="" how="" fast="" comrdterm="" is="">
    bytes_read0 = ComRdTerm (com, & buffer0 [0], 314, 10); / / read com and store it in the buffer
    sprintf (p_check0,"%.4s" & buffer0 [0]);
    T0 = clock() - t0;
    Double time_taken0 = ((double) t0) / CLOCKS_PER_SEC; / / in seconds
    printf("%d\t%f\t%s\n",bytes_read0,time_taken0,&buffer0[0]);
    Memset (buffer0, 0, strlen (buffer0)); / / Clears the buffer

    T1 = clock();
    bytes_read1 = ComRdTerm (com, & buf1 [0], 314, 10);
    sprintf (p_check1,"%.4s" & buffer1 [0]);
    T1 = clock() - t1;
    Double time_taken1 = ((double) t1) / CLOCKS_PER_SEC;
    printf("%d\t%f\t%s\n",bytes_read1,time_taken1,&Buffer1[0]);
    Memset (buf1, 0, strlen (buffer1));

    Thanks for all the help guys. I finally found the solution. The program was running too slow because I kept opening and configure ports (not shown in the code) I simply kept open ports and it works fine.

    I appreciate all the comments and insight. Each of them will definitely help me still to develop with CVI.

    Kind regards
    Keegan.R

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

Maybe you are looking for