exe of labview runing keithley instruments

Similar Questions

• How can pass data to a version of exe with LabVIEW?

  I have an application that allows to launch one or more instances of the same executable using "system Exec' VI, false option" wait until the end? My problem is I want to transmit a different value for each instance, to an input parameter. Something like that if you launch notpad.exe, followed by a file name. The executable file is a generation of LabVIEW application too.

  How can I do this?

  Best regards

  Passing parameters to the command line in a LabVIEW application is actually quite simple.

  There are 2 things you need to do:

  -Change the specification to build exe of LabVIEW to move all command line arguments to the application

  -Read the property App.Args that returns an array of strings for the parameters - the first parameter is always LabVIEW.exe.

  For an example:

  

  Here, I've read the arguments ignore the LabVIEW.exe and then read a path as the first argument and the check, it exists and there is also an option '-choose ' parameter that determines whether to show the user interface.

  Details are here: http://digital.ni.com/public.nsf/allkb/17C3AD70493CE0208625666A00763364

• How do I run the exe of labview with command line

  I would like to launch an exe of labview with a command line.

  I would like to get advice how to launch the exe of Labview with give values to the control settings?

  You can view the example where x, there are controls

  There is a more detailed guide here, I reference below:

  1. first of all, you can enable it in settings:

  1. open the properties for a version of the application specification

  2. navigate to the Advanced category

  3. check the pass all arguments on-demand command line

  To pass the arguments to command line to request and access in your code follow the same steps as for LabVIEW 7.x.

• .exe for labview driver

  I run an .exe driver for laser Doppler vibration. I want to use in lab mode

  or convert LabVIEW driver because the manufacturer donot have any lab display driver

  can someone please help how to do that

  Deutchland wrote:

  I have some commands to it. communication is via ehernet

  Make your own driver using VISA or TCP/IP functions.  You have just need to know what commands to send, and how the data will come back.  Once you make the connection and read the manual, it should be simple enough to make a decent driver library.

• exe of LabVIEW with HTML reports

  Hello

  I'm building an exe of a program using some simple screw to generate an HTML report (so I don't need to Report Generation Toolkit);

  When generating, I found a lot of screws included in 3 directories: NI_HTML, NI_Reports, NI_StandardReport... are all necessary?

  Is it possible to avoid this? Shoudn't the runtime include them?

  I'm using Labview 2009

  Thank you

  Sorry antea06,

  It's the right document.

• Is it possible to call a .exe (non-LabVIEW, such as Notepad) in a child windown on the front panel?

  I would like to launch a stand-alone .exe inside the front of my VI.  It is a piece of software by the provider of a sensor that I try to incorporate in my VI.  I was able to find how to call the .exe using the .NET constructor and invoke nodes.  However, the application opens in its own window.  Is there a way to run from a child window within the façade (ideally, within a tab on the front panel control)?

  I'm in LabVIEW 8.6.

  Thank you.

  smercurio_fc wrote:
  I don't think that it actually works. My understanding is limited about this feature, but since I read it only works with the pop-up windows and windows that are already children. The application's main window is not a child window.

  I've done it before.  I have attached a simple example using Notepad.  Make sure that the notebook is already open no open files.  Since the example is not the position of the child window, the position relative to the window will be the same, because it is off the desk.  So, make sure the upper left corner of the Notepad is close to the origin of the desktop computer.

• Using the Manager of synchronization for exe OI LabVIEW and TestStand

  We would like our operator LabVIEW executable Interface send data via a queue of TestStand to a sequence of logging.  The SyncManager API looks like a slick way to do this because it allows access to the synchronization objects other processes outside TestStand TS.  I created an experimental sequence of trying the concept.  The sequence creates a queue with a step of queue TestStand, up a point to another TS not queue, then uses calls to ActiveX in the SyncManager API to add another element to the queue of waiting.  That all works.

  When I added a LabVIEW VI to place another element through similar calls to ActiveX in the SyncManager API, the VI is not a valid reference to the queue and so it cannot place the element.

  I read on the forum that TS queue name must start with * in order to be accessed by separate processes on the same computer.  When I add a * on my queue name, queue TS operations continue to operate, but step that uses a call of ActiveX in the SyncManager API to get a reference to the queue returns one null ref so the next step of enqueue ActiveX returns an error.  In addition, the LabVIEW VI still does not receive a valid reference to the queue either.

  Ideas and suggestions welcome!  The sequence and LabVIEW VI are attached. Using LV and TS 2012, obtained similar results in 2013SP1.

  Thank you!
  Hans

  The queue API expects a PropertyObject not a string for the newElementPropObj parameter (not sure why LabVIEW similarly let you thread a string). To create a new PropertyObject, you can do something similar to the following:

  myProperty = engine. NewPropertyObject (PropValType_String, false, "", 0);

  myProperty.SetValString ("", 0, theActualString);

  Enqueue it.

  Close the ref to myProperty after you're done with it (i.e. after the queue it) in order to avoid leaking.

  -Doug

• Keithley UNFINISHED 420 'query' error Max scan for instruments

  Hello!

  We have a system for about 9 years. There is a PC with Windows XP and LabView 6.1. In the PC, there is a card GPIB PCI, and via the GPIB cable, 8 Keithley DVMs (including models like 2010, 2400, 2182) connected. A few days ago this old system began to malfunction. There are 4 screws are parallel on this old system - worked fine until now- but none of them are now able to communicate with the Keithley instruments.

  I got a virus check, also verified WinXP, checking the memory and so on (we had several BSOD also on the old PC). Because I couldn't trace the problem in the old system, I decided to check into the Keithleys with a new configuration.

  I have a new PC with a card GPIB + PCI and LabView 2010. I connected this new PC line above with the Keithley instruments GPIB. (old PC disconnected) When I open MAX and I navigate to the GPIB controller, and I scan for instruments, all DVMs Keithley started a signal sound and displays "error 420" on their screens. And I agree I get in MAX.

  So now I have to think that it is a hardware error? Since I have the same problem of communication the DVMs in this new configuration PC...?

  A defective digital Voltmeter can make unreliable GPIB communication? I have no idea where to go now...

  Moreover, in the case of the controller old PCs, I don't get any visible error, only the screw do not communicate (time error). I think I will also try to use the old system again, I will connect the new PC to GPIB channel and listen in the communication with the GPIB Analyzer functionality.

  Thanks for the tips!

  Basic troubleshooting: have you tried simply as an instrument both for the bus connecting? You can also check the cables.

• exe created with labview, 2012 will not be run using LVRTE2013

  I created an exe using Labview 2012.  I had the user to install the latest rte (lvrte2013).  The exe wouldn't and told the user to TENS of 2012.  Should users have the same rte for each exe?

  Yes.  But different rural enterprises can co-exist on the same PC.

• LabVIEW exe is secure

  Hi all

  Is it possible for someone to break the code in an exe of labVIEW? I wonder just about the integrity of my code when I send to the customer!

  Thank you

  dphan128 wrote:

  Hi all

  Is it possible for someone to break the code in an exe of labVIEW? I wonder just about the integrity of my code when I send to the customer!

  Thank you

  If you mean "is it easy for them to see my block diagram when I don't want to do", then the answer is difficult, if not impossible.

  If you give them the VI with a protected password block diagram, don't worry, they won't.

  There has been many discussions regarding the feasibility of crack the password, and due to a deliberately placed embedded wait function by NOR, it would be almost impossible to guess the password of brute force.

  If you simply gave them an executable built, their chances are even worse . To my knowledge, there is no way they could possibly get an executable for the block diagram.

• How to set programmatically a LabVIEW exe * Windows * priority?

  I have an executable of LabVIEW that makes data acquisition to 10 kHz on an ongoing basis and under certain conditions of dumps of these data to a CSV file that is viewable in Excel.  We noticed if the file becomes unusually large and someone tries to open this file so that DAQ'ing is always in course (but does not connect), Excel will monopolize the CPU long enough such that the exe of LabVIEW does not have enough time CPU to extract data from data acquisition until the data in its circular buffer gets replaced.  I could try to simply increase the size of the buffer DAQ, but really, the solution is to have this executable LabVIEW have "priority" over other executables non-LabVIEW (such as Excel.)    Looking at properties VI--> execution--> set the priority seems to only define the priority between other threads LabVIEW but says nothing about how a thread LabVIEW is prioritized to another non-LabVIEW exe.   I have confirmed this by setting the LabVIEW execution property to 'critical moment' and then in the Task Manager and windows reports still his priority as "normal".   How can I set the * Windows * priority of an executable of LabVIEW without having to do it manually via the Task Manager?

  Thank you

  Ninja Edit:

  I should mention that I am building the executable is nothing else than a "master GUI" which generates four LabVIEW modules in sub-panels using static VI refs and displays important data from these four modules persistent "dashboard".   Modules to do all the boring tasks such as DAQ'ing and display data in charts.  Because I am compiling my code in a single executable using the GUI 'master' as the boot VI, set the priority in properties of VI flow down to the modules I load in sub-panels or will only the priority of the Master GUI be changed?  On a related note, should I set four enforcement system 'Data acquisition' modules, then the master GUI to ' User Interface?

  You can try calling the next VI. It sets the priority for the current process and has worked for me in the past on XP.

• Automing instruments LabVIEW without using specific and coding drivers for each instrument?

  Hello

  I'm new to programming in labVIEW, but I had a few questions about its use in automation and remote controlling several instruments.

  It is an ideal software for automation of various instruments remote control/test. Assuming that I have several different companies spectrum analyzers, I understand that labVIEW drivers of instruments or special VI who would control these instruments. But if I wanted that all these spectrum analyzers to say, to display on another computer using the remote control, but I wanted to use the same program for effeciency, is it possible to do so universally for all instruments using labVIEW? Or do I have to adapt this program for each instrument to instrument drivers cause?

  If labVIEW can do that, is - anyone had good success for such scenarios in other programming languages?

  Thanks in advance for your help.

  Look for the Abstraction Layer material (that you can implement with LabVIEW, even if it's a slightly advanced topic).

  The idea of having a specific Test and be able to enforce it against different Instruments, decided at run time, is the kind of situation that LabVIEW and use of HALs was designed to facilitate.

  The concept is to 'Levels of Abstraction'.  When you create a test, you can design it for an abstract Framistan, since all the Framistans are supposed to be able to measure Vorbels in the range of 0 to 100, so you just plug a generator of Vorbel to generate Vorbels in a certain sequence of Test (linear, random, quickly, slowly, pulsatile, continuous, you decide), measure your Abstract Framistan records readings and compare with the results you expect write the results in a nice report.

  Of course, Framistat of OR uses Ethernet as the means of communication, while HP uses a serial port (depending on the model, series settings can change) and uses of the Intel one. DLL to communicate with the low-level API.  So you also need to develop, for each specific instrument, an "interface" between its API and the Framistan abstract (not everyone uses Vorbels as the input unit, for example).

  So the good news is that it can be done, the bad news is that one of the best ways of handling this type of question on the programming is to use OOP (OOP).  A number of languages (LabVIEW, C++, JAVA) support OOP, but LabVIEW might have the advantage when it comes to interact with the material.

  I you are looking for Hardware Abstraction Layer?  Add LabVIEW to the search query and you should find some nice presentations by Elijah Kerry...

  Bob Schor

• InStr.lib missing after installing LabVIEW

  Greetings,

  We have a q SMU-1062, which was profesional of LabVIEW and FPGA (2012 SP1) module installed. Due to some issues we had to uninstall both of them.

  I uninstalled someother drivers think that they would be installed with the installation of the new software. Now, Ive installed both programs of return and try to run a

  application tool (.exe in LabVIEW) but I get messages on the attached images. I can send more pictures if needed.

  I have experience relatively little in LabVIEW and do not know how to solve the problem. Any help, I appreatiate.

  Thanks in advance!

  Jorge Garza

  I would recommend to reinstall the driver.

  Use the most recent:

  NOR-DAQmx 14.5 - National Instruments

• Keithley 2400 tension question

  Hello, I use Labview 2010 to try to control a Keithley 2400 Sourcemeter by GPIB.  I use drivers labview the Keithley 24XX driver package that I downloaded from the 'instrument Drivers to find' in Labview.

  I am trying to use the device as a current source to power an electromagnet.  I have the system put in place and it will output current, but any height, I adjust the value of compliance, the output voltage of the sourcemeter will not exceed 2 volts.

  I am sure that this is not a limitation of the device because when I adjust the compliance and current manually the device has no difficulty.  For some reason when I have control the device with labview he just won't go more than 2 volts. Any help would be great.

  I have included my program here.  If someone needs screenshots to diagnose this problem, let me know.

  I think I got it.  I made a small change to "configure surge protection.   "I changed the string in the GPIB command of ' %. ; "SOUR: VOLTROT %g" to "%.; "SENSE: VoltROT %g" which changes the compliance of the range.

• Possible GPIB communication through interactive control of Visa, not with Labview

  Hello

  I have a communication problem with Labview with GPIB instruments (with functions of visa).

  I get:

  "Error 1073807298 occurred at the VISA opening

  Possible reasons:

  "VISA: (Hex 0xBFFF003E) failed to perform operation due to i/o error."

  However, it works with an interactive control visa and this is where I am confused!

  Here is my setup:

  -Labview 2011 assessment

  -VISA 5.1.2

  KUSB - 488B with the associated drivers (adapter USB to GPIB of Keithley)

  Because I can speak with my instruments in visaic, I guess the installation of drivers for the Keithley interface is ok.

  Trace IO NOR I see beeing of commands passed through Labview to VISA so that they "see" between them.

  I found a thread where someone had the same problem and its solution was downgrade to Labview 8.5.1, which is not possible for me.

  http://forums.NI.com/T5/instrument-control-GPIB-serial/Keithley-2700-driver-problems/TD-p/1474212/PA...

  You have an idea to solve this problem?

  Kind regards

  Baptist

  Here's a follow-up on this issue.

  I tried with Labview 32-bit on main machine: it works.

  The pleasure is that I have to use Labview 64-bit.

  So the ultimate solution is now to run a client and a server of visa on the machine: Labview 32 bit can directly access my resources GPIB, Labview 64-bit must go through the closure of the network.