Opal kelly builders and LabWindows/CVI

Similar Questions

• 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

• 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

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

• 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

• 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

• 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

• 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

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

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

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

• 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

• Why can I not use my labview controls created dll in labwindow CVI?

  I created a DLL in LabVIEW for run of LabWindows/CVI.  The DLL is started very well but I have no control on the GUI.  Why and how can I use this GUI controls?

  I found the solution on the following thread.

  http://forums.NI.com/NI/board/message?board.ID=180&message.ID=36951&query.ID=314335#M36951

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