Basis of LabWindows/CVI 9.0 connecting winspool.drv

Similar Questions

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

• NOR tkds5000 LabWindows/CVI IVI driver not work for TDS5104, TDS5054B

  I'm trying to get the driver NI LabWindows/CVI IVI (tkds5000 version 1,212) working for the Tektronix TDS5054B scope.  When I execute the following functions, I have the warning 'Is not a valid value for the parameter or property' of 0xBFFA0010:

  IviScope_InitiateAcquisition

  IviScope_GetAttributeViInt32 for IVISCOPE_ATTR_TRIGGER_SCOPE and IVISCOPE_ATTR_ACQ_TYPE

  IviScope_ActualRecordLength

  This is not an exhaustive list of the functions that do not work, but just that I currently see.  There are several functions that work (see this joint SPY OR file).

  The strange thing is that everything works fine when I have an oscilloscope Tektronix TDS5104 connected (file SPY OR see attachment).  The code also works when I have an oscilloscope connected and selected through MAX TDS3054 driver tkds30xx IVI of NOR.

  Is it possible that the driver of version 1,212 tkds5000 does not support fully the TDS5054B?  I looked through the files tkds5000.c and tkds5000.h, but has not seen any dependencies on the model of the oscilloscope for these functions.  Any ideas?

  Thank you!

  Dave

  So, then I thought about it.  The tkds5000 driver AND works very well.  The problem is that the Tektronix TDS5054B scope do not "initialize" some of the attributes.  For example, I had a problem reading the value of the attribute of slope of relaxation because an invalid value was returned.  If I set the slope of the trigger, first of all, then read it, it works fine.

  Its strange because most of the attributes is set to the correct value corresponding to what is displayed on the oscilloscope screen and the Panel, but not ALL of them.  In addition, other Tektronix oscilloscopes did not require a writing before reading.

  Anyway, thanks a lot NathanT.  I appreciate your help.  You saved me a bunch of time to have to go back and add in a dedicated driver.

  -Dave

• Are there examples of DataSocket up-to-date for Labwindows/CVI

  I am in the process of taking data to return data from test equipment using WiFi.  I want to use DataSocket, but all the examples I found for Labwindows/CVI are using data functions API DataSocket.  Are there more recent examples available to show how to put in place a socket connection and transfer data?

  Hello

  You want to take a look at this example transfer a DataSocket of using ASCII text file and see if it helps?

• NI MAX entry for a pilot of LabWindows/CVI Instrument Non-NI/VISA

  Hi all

  Sorry in advance if this isn't the right forum.

  I created a class IIA and driver specific instruments in LabWindows/CVI for a video generator. The generator is a SCPI instrument based network. It does not automatically appear in MAX like other instruments NOR based.

  How or what I need to do for MAX to use the instrument? Is it as simple to add the logical name, the session pilot and advanced pilot joined MAX? I need to create a new instrument in the HW section, such that the pilot session has a device to point to? I played aroud with the section of the network instrument in MAX and nothing seemed to make sense to me.

  Any help would be greatly appreciated!

  Thank you

  Manesh

  Manesh,

  Maybe this Knowledge Base article will help you to help you get started. I think that you will need to add a new resource of VISA's TCP/IP able and Automation Explorer.

  How to set up an Instrument to communicate via TCP/IP able & Automation Explorer:

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

• LabWindows/CVI 8.5.1 for Windows 7

  I LabWindows/CVI version 8.5.1 running on XP that I use to develop with a target operating system from XP.  Now with Microsoft no longer provides XP, new sales for our product will go on Windows 7.  I guess I could use virtual XP environment in Win7, but I'd rather build my application as a native application for Win7.  I searched the forum and found some answers in fragmentary, and based on these points, here's my question:

  I want to use the version 8.5.1 of LabWindows/CVI to develop an application for Windows 7.  I see where install the runtime newest (2009 SP1) should be on the target (Win7) machine, and everything should be good; in other words, the application developed on XP with CVI 8.5.1 machine must run under Win7 with upgrade TEN 2009 SP1.  Is this correct?

  Are there problems with the update of the RTE on the development computer?

  Basically I'm asking if there is a problem do the following:

  PC 1: software development, XP, LabWindows/CVI 8.5.1, engine of execution of update for SP1 RTE2009, NOR-DAQmx 9.2.1 installed

  PC 2: computer application, Windows 7, SP1 Runtime Engine RTE2009, NOR-DAQmx 9.2.1

  Given this configuration, would be my application developed on PC1 work natively on PC2?

  One option would be:

  PC1: software development, Windows 7, LabWindows/CVI 8.5.1, engine of execution of update for SP1 RTE2009, NOR-DAQmx 9.2.1 installed

  PC2: no change

  Did anyone see any problems with any of these options?  (The big question is if CVI 8.5.1 would have had trouble with the RTE2009 SP1 for development).  Thank you!

  Hello

  You shouldn't have a problem of developing an application on a Windows XP computer to use on a Windows 7 computer. If you use the Windows SDK functions you may need to modify your code a little differences in BONE but other than that you should be ok as long as you take in the review on the connections. Have a great day!

  Best regards

  Adam G

• Using a DLL built with LabWindows/CVI

  Hello world

  I'm pretty new in the environment, LabWindows/CVI, until present excuses for any silly question. I have a real-time application running in a PXI, but I want to "complete" by adding new features, I have in the C Code generated from Dymola. I thought about creating a DLL of this code (using LabWindows) and then insert it in the .vi (the one I have running in the PXI) using the library function call so that I could have the new .vi running in PXI.

  Will it work?

  Thank you

  Hi all

  I S is true, you can find this knowledge base and really useful related links. This tutorial looks also interesting. However, take into account that the code runs on a real-time platform (such as the functions will work with the same priority as the appellant threadand, many other issues). Remember to FTP the file *.dll for PXI.

  Hope this helps,

• 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

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

• 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

• 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

• 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

• 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