Error selection LabWindows CVI Card Configuration

Similar Questions

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

• Cisco ACS SE "set ip" error: could not set up new NETWORK card configuration.

  Hello

  I get the error "error: could not set up new NETWORK card configuration." When I try to set the IP ACS SE.

  When I called into the device image and tried to do an initial installation, the IP to not hold after the restart and went back to the default value.

  I went by NetPro and apparently it is a common problem. One person it is solved re-imaging unit, but who has not worked for me.

  Someone there with a solid solution? I use NIC 1 FYI.

  EDD.

  Ed,

  Please make sure that if ACS is associated with active before setting Ethernet connection

  or change the IP address of your ACS system engineer.

  http://www.Cisco.com/en/us/docs/net_mgmt/cisco_secure_access_control_server_for_solution_engine/4.0/installation/guide/appliance/admap.html#wp1109621

  Kind regards

  ~ JG

• 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

• difference of initial value of string between the steps in the process and an external instance of LabWindows/CVI

  Hello

  I'm curious to know what I see using TestStand, LabWindows/2013 2013 with regard to initial in TestStand string values when you perform the steps in the process or an external instance of LabWindows/CVI.

  I have a step (CVI) string value that is used to check an array of characters stored in an EEPROM to test.  I pass on the Step.Result.String in the CVI by reference.  I then read the table charater of the EEPROM in the chain (Step.Result.String).  The string is then compared against the limit as specified in the test step breast.

  When I run this test step to perform the steps in the process selected in the popup Configuration of the adapter of LabWindows/CVI, it seems that the memory allocated for the string is filled with null characters.  Which is what I expected.

  When I run this test step to execute the steps in an external instance of LabWindows/CVI iselected of the Configuration of the adapter of LabWindows/CVI popup, it seems that the memory allocated for the string is filled with something else.  That is not what I expected.  For example what I see in the memory, it's the first characher is one byte NULL but the remaining bytes are some other values, as shown below:

  F0 00 AD BA 0D F0 AD BA 0D F0 AD BA 0D AD BA 0D AD BA 0D BA 0D AD F0 F0 F0
  F0 AD BA 0D F0 AD BA 0D F0 AD BA 0D F0 AD 0D AD BA 0D AD BA 0D F0 F0 F0 BA...

  In my code I make sure to write a null character in the following location table charater I just write in the chain so I have no problem with the test is working properly.  I have remove the writing from my code null character and was able to verity that the test passes when executing the steps in the process and fails during execution of the steps in an external instance of LabWindows/CVI.

  The returned string contains what I wrote for her, and then the rest of the string is filled with the values that are in the memory allocated for the string.

  Here's my Question: is this the expected behavior for the original string values in TestStand between both types of stage performances?

  Thank you

  Chris Young

  In general teststand not Initializes the unused portion of the string buffer, so it is expected that the values of the memory after character no endpoint will be different, or even to each call. If you happen to be get zeros after the null terminator which was probably due to random character (i.e. the memory allocated just arrived already having zeros in there) or perhaps a debug setting you use perhaps in the Visual C runtime (if you are debugging the process in visual studio or modify visual C runtime heap parameter). TestStand is not initializaing memory after the null terminator character in both cases (I checked the code).

  -Doug

• "Socket.h" is available for LabWindows/CVI

  I'm trying to use a third party API with LabWindows/CVI. I get a compilation error that says 'socketaddr_in' is undefined. On Unix/Linux systems, this parameter is defined in the include file "socket.h". I searched my system (Windows) for "socket.h". Nothing is found. I have to buy Visual Studio (or whatever we call it) just get socket.h (or whatever it is called on Windows)?

  I'm spoiled by having this kind of stuff available immediately free of charge on Linux.

  Querty99,

  When you installLabWindows/CVI you will have the option to install the Win32 API. For the header, you search the files make sure the Win32 API Interface a right-click and select install this feature for a local player (see the attached screenshot). If installed correctly, you should see your C:\Program NIUninstaller Instruments\\sdk\include WinSock2.h.

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

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

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

• Why the labwindows/cvi Installer runs whenever I try to start labview 7.1, after I installed N!-series?

  Why the labwindows/cvi Installer runs whenever I try to start labview 7.1, after I installed N!-series?  The installation program runs 3 times now and asks me to restart every time.  Then I reboot and it happens all over again when I try to start labview 7.1, unless I select Cancel 3 times in a row then labview starts.

  Thank you once again.  I am running.

  Barry-AIC

• 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

• 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

• Opal kelly builders and LabWindows/CVI

  Hello, all.

  I try to get a Council Opal Kelly XEM3005 running with LabWindows/CVI 8.5.

  I have been in touch with Tech Suppt of OK and overthrew the original questions of type 'bool '.  After (at the recommendation of OK) with "char" types, I can now include the headers without errors.

  There are, however, a new problem:

  When I call the constructor function, which should return a pointer to a type of "okFrontPanel_HANDLE", I get an error for a prototype missing for initialization.

  Dredged in the .c (pp) file I found the following:

  //----------------------------

  Hi tomii,.

  Looks like you posted another very similar thread on the compilation of mistakes with the DLL of your Opal Kelly here. I follow upward in this thread to help get traction with those questions.

• How to remove the additional window when I start LabWindows/CVI or will execute my program?

  For a short while (maybe a week or more), I get a small extra window behind my request. Also, when I start LabWindows/CVI, I get the same window. It is a small blank window with the same title as the application. Press close (X) closed the application too.

  I don't remember seeing this before and that he doesn't know what has changed on my PC. It also happens with old LabWindows (previously compiled) programs, it seems that something in Windows has changed.  I use Windows XP and LabWindows/CVI 9.0.0 (348).

  Thank you

  Rob

  Hi Rob,

  The window that you see is part of the CVI. It is the parent window for all windows of the CVI so much in the environment and execution. As a general rule, this window is hidden way off the screen so that you don't even know it's there. But some video cards have a parameter that requires all windows off the screen to move to the screen. Take a look in your video card settings to see if this setting exists on your pilot. If so, then disabling the setting will allow the window to hide off screen.