Bat-emc labview

Bonjour,
J'ai un programme (BAT-emc, un logiciel de génération de champ), qui est censé appeler une llb de labview et lui faire lancer les vi qu'elle contient.
Sur un ordinateur, l'opération se déroule comme prévue, mais sur un autre ordinateur (que je dois dorénavant utiliser ), cela ne fonctionne pas.
J'ai essayé de visualiser ce qui se passe avec "Process Monitor", mais j'avoue ne pas trop savoir comment interpréter tout ca. Labview semble bien essayer d'ouvrir la llb mais n'aboutit apparemment pas...
Je précise que j'ai la démo de labview sur les deux pc pour l'instant. Je mets aussi en PJ la capture prise par process monitor (c'est pas très lisible en .csv donc si quelqu'un a process monitor dites le moi, je l'enverrai en pml)
Un grand merci à ceux qui pourront m'aider...
Solved!
Go to Solution.
Attachments:
Logfile.CSV ‏523 KB

J'ai résolu mon problème: il fallait que je rajoute "*" dans la liste d'exportation des vi, afin d'autoriser l'exportation de tous les vi.
merci quand meme.

Similar Messages

How to show graph of emc analyzer on labview?

Hi guys,
I have posted the question a few days before, now I still cannot get totally correct waveform.
I use a Agilent E7405A emc analyzer, I would like to control the parameters (centre frequency, span etc.) I downloaded the driver and found the VIs that can change these parameters, but I really have trouble in showing the graph on the analyzer into the pc.
The plot y-trace VI seems not working right. Do you guys have samples on showing spectrum graph? I'm using labview 8.2 so some examples on the net I cannot open, that is annoying. I really need help, thx.

Hi
I feel so to....maybe you can create user groups and also then have different actions ..... but this is a high price to pay for the same. You may want to prefix your action reason with two character country code, and train your users accordingly, You can also then have a user exit based on which user needs to use which action.......that's if you want a very strict controll.....best regards

Include LabVIEW Run-Time Engine in C# Project Distribution

I have written a software package in Visual Studio using C# which calls a number of functions from a dll which I have built in LabVIEW. I am now trying to produce an installation program for my C# package but can't quite work out how to include the LabVIEW Run-Time Engine in this installation.
I am creating the installation program by defining a Visual Studio Deployment Project and I have added my LabVIEW dll to this. However, the dll requires the LabVIEW Run-Time Engine to also be installed on the target PC. I was hoping that there would be a set of files to implement the installation of the LabVIEW Run-Time Engine that I could include in my Visual Studio Deployment Project and do the installation of both my C# code and my LabVIEW dll (inc Engine) in one operation. Is this possible? Or do I need to produce a LabVIEW installation for my dll separately from the C# installation?
Info:
Development OS = Windows 2000
Target OS = Windows XP
C# Development Environment = Microsoft Visual Studio 2005 V8.0
LabVIEW Version = 8.5
Also, I am using the Order Analysis Toolkit and noticed that there seemed to be an 'Order Analysis Run-Time Engine' installed on my PC. Do I need this too?
Thanks for any help.
CAS

Hi CAS,
One way of automating the installation of the LabVIEW run-time engine is to use commands in a batch file (*.bat). These commands would be executed automatically at the same time as your distribution installer to install LVRT with your C# application. For more information on command line options, have a look at this KB. I don't have so much knowledge of C# distributions, though, so there may be a better way to approach this that someone else in the community could advise you on.
With regard to the order analysis toolkit, you will also need this runtime engine installed. A point to note, though, is that the toolkit requires a run-time licence to be deployed in this fashion. It is now part of the Sound and Vibration Measurement Suite and needs to be licenced accordingly.
I hope this helps!
Best regards,
Tom
Applications Engineering, NI UK

Installer Group: This is what it takes to do a network install of labview.

Here is the install.bat file we made to do this. Keep in mind, this just “appears” to install everything listed in it correctly as a clean install. Proton is our network drive.
@Echo Off
@Echo Starting Labview 8.2 Installation
\\Proton\LoginUpdates\LV-10-06\LV8.2\setup.exe \\Proton\LoginUpdates\LV-10-06\LV8.2\Bin\NoUser.txt /r:n /q /AcceptLicenses yes
@Echo Starting CVI 8.0.1 Installation
\\Proton\LoginUpdates\LV-10-06\CVI8.0.1\setup.exe \\Proton\LoginUpdates\LV-10-06\CVI8.0.1\support\NoUser.txt /r:n /q /AcceptLicenses yes
@Echo Starting Signal Express 1.1.1 Installation
\\Proton\LoginUpdates\LV-10-06\SignalExpress1.1.1\setup.exe \\Proton\LoginUpdates\LV-10-06\SignalExpress1.1.1\Bin\NoUser.txt /r:n /q
@Echo Starting Toolkit Installations
@Echo ---- Starting Advanced Signal Processing
\\Proton\LoginUpdates\LV-10-06\ToolKitSoftware\LabVIEW\Advanced Signal Processing\setup.exe" "\\Proton\LoginUpdates\LV-10-06\ToolKitSoftware\LabVIEW\Advanced Signal Processing\supportfiles\NoUser.txt" /q /r:n
@Echo ---- Starting Digital Filter Design
\\Proton\LoginUpdates\LV-10-06\ToolKitSoftware\LabVIEW\Digital Filter Design\setup.exe" "\\Proton\LoginUpdates\LV-10-06\ToolKitSoftware\LabVIEW\Digital Filter Design\supportfiles\NoUser.txt" /r:n /q
@Echo ---- Starting Database Connectivity
\\proton\LoginUpdates\LV-10-06\ToolKitSoftware\LabVIEW\Enterprise\Database Connectivity\Setup\lv_dbtools.msi" /passive /norestart
@Echo ---- Starting Internet kit
\\proton\LoginUpdates\LV-10-06\ToolKitSoftware\LabVIEW\Enterprise\Internet\InternetToolkit6.0.msi" /passive /norestart
Echo    **** Labview SPC Toolkit can not be installed silently ****
Echo    ****         You will need to install manually         ****
@Echo ---- Starting Express VI Development
\\proton\LoginUpdates\LV-10-06\ToolKitSoftware\LabVIEW\Express VI Development\ExpressVIDev\ExpressVIDev.msi" /passive /norestart
@Echo ---- Starting PID Control
\\proton\LoginUpdates\LV-10-06\ToolKitSoftware\LabVIEW\PID Control\setup\lv_pid_6.msi" /passive /norestart
@Echo ---- Starting Report Generator
\\proton\LoginUpdates\LV-10-06\ToolKitSoftware\LabVIEW\Report Generation\lvoffice\lvoffice.msi" /passive /norestart
@Echo ---- Starting State Diagram
\\Proton\LoginUpdates\LV-10-06\ToolKitSoftware\LabVIEW\State Diagram\StateDiagTK.msi" /passive /norestart
@Echo ---- Starting VI Analyzer
\\Proton\LoginUpdates\LV-10-06\ToolKitSoftware\LabVIEW\VI Analyzer\setup.exe" /q /r:n
Echo    **** CVI SPC Toolkit can not be installed silently ****
Echo    ****       You will need to install manually       ****
@Echo ---- Starting SQL Kit
\\Proton\LoginUpdates\LV-10-06\ToolKitSoftware\LabWindows CVI\Enterprise\SQL\Sql2.msi" /passive /norestart
@Echo ---- Starting PID for CVI
"\\Proton\LoginUpdates\LV-10-06\ToolKitSoftware\LabWindows CVI\PID Control\setup.exe" /q /r:n /AcceptLicenses yes
@Echo ---- Starting Signal Processing for CVI
"\\Proton\LoginUpdates\LV-10-06\ToolKitSoftware\LabWindows CVI\Signal Processing\Setup.exe" /passive /norestart
@Echo Toolkit Installations Completed... Please install manual components.
@Echo Starting NIDaq 8.3, NIMotion 7.4, NIVisa 4, etc... Installation
\\Proton\LoginUpdates\LV-10-06\DCD-Nov06-1\setup.exe \\Proton\LoginUpdates\LV-10-06\DCD-Nov06-1\spec.ini /r:n /q /AcceptLicenses yes
@Echo Installation Complete......
Now this took us weeks to make. Notice you have three different types of installers with different command line switches. there isn't even a set of NI standards. It took us a long, long time to put this together, trying an install and wiping the PC clean over and over and over until we finally came up with this...
So my question is, are you guys sure it was such a good idea not to use a standard MSI file? You really need the NI custom installer with non-group-policy-compatible msi's?
If you gave us real msi files this could have been much easier!
Message Edited by billings11 on 10-09-2007 02:17 PM
-Devin
I got 99 problems but 8.6 ain't one.

Hi Billings11,
To recap, here is Andrew's previous response:
You are correct in pointing out that NI's MSIs do not function as normal MSIs. We made the decision to create functionality which would extend MSI and allow us to create more robust installers. Our current installer framework acts as a supervisor over the installation. It has the ability to mark and match dependencies (more functionality than the MSI reference count) which are important when other NI products are being installed or if any product is uninstalled. The installer framework also provides a lookup service to all of the MSIs which can provide any installer with specific information about other NI products installed on the machine, paths to those products, etc. The framework gives the ability for groups within NI to create separate installation parts (MSIs) which can be brought together into one installer without recreating a single distribution MSI from scratch.
Extending functionality outside of normal MSIs also means that installation via a network group policy is no longer supported.
To support deploying through Active Directory, we would need to remove our installer framework instead and ship each piece of software as a single MSI. The features our framework provides would be eliminated, and much of the burden of tracking dependencies would be pushed onto the customer. Installation procedures would most likely become more complex, as each MSI would also be relatively blind to the current set of NI products on the machine.
To distribute the NI installers to many machines, our recommendation would be to place the installer on the network, use Active Directory to define the policy, and then distribute the software through Microsoft SMS (or a similar tool) by running the installer in silent mode. This involves creating a spec file, and then running 1 or more installers silently as part of a batch file. You had already brought up this point in a previous post:
"You might suggest running batch files as login scripts. But it takes longer for someone to create and test a batch file silent install than new installation in a real MSI file. You have to look up all the right switches to run the installation in silent mode with the right options - its a pain. Its really better in the long run to take the time to recreate NI's installation from scratch so you can have a real windows installer from that point forward."
I completely agree that the process for creating a batch file for the silent installation of NI products should be improved. We are working hard to create a process in which you can 1) create a spec file simply and quickly and 2) be able to run the installer easily in silent or basic mode. These improved features should reduce the issues your IT would have with NI software distribution through Microsoft SMS (or equivalent product).
Thanks again for your comments and have a great day!
Andrew W
Software R&D
National Instruments
Cheers,
David Goldberg
National Instruments
Software R&D

When bates numbering a .pdf in XI, how can I change the file name to include the bates number AND its name? I know under file output, there is an option for either/or. I want both. Thank you.

when bates numbering a .pdf in XI, how can I change the file name to include the bates number and the file name? I know under "file output: it's either/or. I need both. Thanks!

Long ago I wrote a little demo using the touch command. Check out the following thread:
http://forums.ni.com/ni/board/message?board.id=170&message.id=25128#M25128
LabVIEW Champion . Do more with less code and in less time .

Electrical/Software (LabVIEW) Design Engineer, Wiltshire, UK

Job Title: Electrical/Software (LabVIEW) Design Engineer
Job Type: Permanent
Location: Malmesbury, Wiltshire, UK
Job Purpose:
To provide design solutions for machine control, instrumentation and data acquisition using National Instruments LabVIEW. Support and maintain systems throughout Dyson Ltd.
Principal Accountabilities:
Design of software using National Instruments LabVIEW for control and data acquisition
Support existing National Instruments LabVIEW systems
Design, manufacture and installation of safety and machine control circuits
Design bespoke signal conditioning PCBs
Write specifications and manage sub-contract design and manufacture resource
Skills Knowledge & Experience:
Essential:
HND in Electrical/Electronic engineering with 5 years experience
Attendance at National Instruments LabVIEW Intermediate 1&2 with 5 years programming experience
Desirable:
Working knowledge of National Instruments hardware product range
PCB design (Mentor Graphics)
Experience of PLC programming
Formal training in CE directives on Machinery, Low Voltage and EMC.
Knowledge of BS7671 Electrical Installations (IEEE 17th Regs)
Behavioural:
The ability to communicate appropriate, concise and accurate information across the business (technical and non-technical) is essential for the successful applicant.
You will be a highly driven individual who strives for accuracy & quality in work delivered.
You will be able to solve problems in a logical way, pre-empt future problems and seizing opportunities without waiting to be told.
The proven ability to work as part of a team or un-supervised to an agreed goal or set of deliverables is imperative.
For more detail visit our website: www.careers.dyson.com
Contact: [email protected]

I AM WORKING IN LABVIEW FROM 6+ MONTHS WIHT PXI.
I AM VERY ENTHUSIATIC TO WORK IN LABVIEW
i am from INDIA
MY EMAIL ID IS [email protected]

Using Labview's System Exec.vi, is there any way to send multiple standard inputs to the same executeable console? Or is there a way using Labview to target the window for the executeable and send commands to it at will?

thanks

One suggestion is to write a batch (.bat) file that will call your executable. The batch file can contain all the standard inputs necessary to run the executable. Then, in LabVIEW, you can call the .bat file using the System Exec.vi.
As far as your second question, there is no slick way to do this LabVIEW. You would probably have to call Window API functions using the Call Library Function utility. There is a set of VI's that call some of the standard API functions but I don't think they have what you want.
http://zone.ni.com/devzone/devzoneweb.nsf/opendoc?openagent&74DDE683A1AFF6988625683A000C0D73&cat=034E59A8530E09DF862568900018707A
Chris_Mitchell
Product Development Engineer
Certified LabVIEW Architect

LabView equivalent to running batch files using the "shell" command (VisualBasic)

I'm converting a VisualBasic app to LabView and am having trouble figuring out how to run a batch file with LabView.
The VB code that I'm trying to replicate is:
'UNLOAD RTX DRIVERS
Dim ProcessId As Long
ProcessId = Shell(App.Path + "\UnloadReloadRTX.bat", vbNormalFocus)
Wait 400
I haven't found a LabView equivalent to the Shell command. Any suggestions will be appreciated.
thanks,
Todd

It seems as if this question pops up every week. Use the System Exec.vi found under Funtions - Communications palette. It is the equivalent of Shell.
- tbob
Inventor of the WORM Global

Labview Programmer Job Opening - Santa Clara, CA

Software
Engineer/LabView Programmer
OptiMedica
is looking for an experienced Software Engineer/LabVIEW Programmer to support
the development and production of its expanding line of innovative ophthalmic
instruments. Candidate must be familiar with LabView programming and Software
best practices, be familiar with medical device environment and its
regulations, and have the ability to quickly solve challenging problems. Candidate will function as a key software architect
for complex medical systems.
Strong skills and
experience with LabVIEW programming for FPGA, LabVIEW applications, and higher
level applications on Windows operating systems are required in order to develop
automated test, measurement, data acquisition, and control systems. Must be able to work with limited
guidance/supervision and be able to test, evaluate, document, qualify and
release designs for complex projects involving medical laser equipment in a
focused, highly collaborative multidisciplinary environment.
Skills/Experience
Requirements:
o
Highly
developed problem solving, communication and collaborative skills.
o
At
least five years experience developing automated test, measurement, data acquisition,
and control systems using LabVIEW. Experience
developing OEM products a plus.
o
At
least five years experience working with product development team to transfer new
products into production for commercial sale.
o
Key
participation in the test and integration of successfully shipped medical
products is strongly preferred.
o
Successful
track record delivering innovative software solutions to complex problems.
o    Familiar with
Electrical Safety, EMC/EMI Qualification Testing & Design Requirements for
Medical Equipment.
o
Fast
and eager at learning and applying new technology.
o
Familiarity
and experience with verification and validation phases for medical device
software.
o    Knowledge, experience
and understanding of software development standards.
o
Experience
with lasers, optics, motion control, and image processing.
o
Experience
with National Instruments hardware (especially FPGA); experience with a variety
of programmable instruments a plus.
o
Experience
using structured, specification driven, requirements-based approach to software
design and development.
o    Must be well
organized and enjoy working in a dynamic environment.
o    Facility with Qt, MATLAB and C++ beneficial.
Responsibilities:
o
Design,
develop, qualify, implement and release designs for FDA-approved medical laser
equipment using LabVIEW.
o
Support
R&D, Production, and Field Service of FDA-approved medical products in the form of
automated tests and control systems using LabVIEW.
o
Participate
in design review and hazard/risk analysis meetings.
o
Create
test procedures to verify the safe and proper software operation of FDA-approved
medical products.
o
Pursue
continuing education and certifications, including NI Certified LabVIEW
Developer and Architect.
o
Work
in a team environment with other engineers (of varied disciplines) as well as executives
and manufacturing personnel to sustain existing products and deliver new
products to market.
o
Apply
software principles and concepts to evaluate new designs for function and
performance. System integration of new
components and designs into high performance optical and opto-mechanical systems
and sub-systems.
o
Collect/
review data and communicate both status and recommendation on technical issues
by preparing technical reports and presentations.
o
Initiate,
execute & review product changes via OptiMedica’s ECO process.
o
Provide
continuous support for manufacturing and resolve complex manufacturing issues.
o
Develop
test methods, system test procedures and create test and qualification reports
for new product introduction.
o
Reports
to Director of Product Development.
Education Requirements:
o
Bachelor’s
degree in Computer Science, Electrical Engineering or equivalent strongly
preferred.
Site Location/Contact
Information:
o
Santa
Clara, California
Note:
Candidates must be legally authorized to work in the United States.
NOTE: This job description is not intended to be
all-inclusive. Employee may perform
other related duties as negotiated to meet the ongoing needs of the
organization.
Contact:
Debbie Goedicke - 650-585-6784
[email protected]

Labview Programmer

How to get sequence overall result in LabView ?

Hello,
Would anyone can help with this tiny problem ?
We have a batch (.bat) that launches a given list of TestStand sequences, which works as expected.
However, we would like to monitor the result of each sequence and display it to the operator.
Our idea is to get the sequence result in a VI, run at sequence end, and add it to a queue, that will be retrieved and displayed on a VI monitor, run separetly.
The only problem we have left is to be able to retrieve the sequence global result. Any idea or suggestion ?
Thanks
Raphael
Solved!
Go to Solution.

Thanks. The problem is not the monitor and how to pass the information to it.
We already have a test monitor (using queues) that is working as expected.
The test sequence is queuing information, mainly at steps end with step result, and the monitor is displaying information from that queue. The queue is resseted at each sequence start.
We would like to derivate that monitor to display only sequences (launched by a batch file) overall-global-final result of all the sequences ran. Using UImessage is maybe a better way, but we do not want to spend time re-writing another monitor.
The problem is how do we retrieve this overall-global-final sequence result in LabVIEW ?

How to run .exe file by labview?

Dear All,
I want to use Labview to run a .exe file, but I don't know how to do? who can tell you? Thanks!
Best regards,
Jimmy

Try the attached VI (LV v7.1.1). It uses the System Exec function:
(from the LV Help file):
"System Exec
Executes a system command. UNIX You can use wildcards, pipes, and shell meta-characters. Mac OS To use this VI on Mac OS, you must have the Macintosh Programmer's Workshop installed. Refer to the Apple Developer Connection Web site for information about downloading the MPW.
To launch an executable with options using the syntax filename.exe -option1 -option2, create a filename.bat file that calls the executable with the options syntax and use this VI to call the filename.bat file. "
Attachments:
Run Program.vi ‏30 KB

Change IP-number and Subnet-mask with LabView?

To upgrade the software on a CRio-System, the user needs to change some settings in the TCP/IP-configuration.
To simplify this task I think on a possiblity to do (and at the end redo) the changes in the TCP/IP-Configuration of the Windows PC.
What I need is:
- Change the IP-Adress (from "Obtain IP adress automatic" to IP xyz...)
- Change subnet-mask
- Redo this settings by saving an existing config or set to "Obtain IP adress automatic"
Who knows if and how it's possible to do that in LabVIEW?
Perhaps I have to call a script /.bat-file?
LabVIEW 6,7 and 8 available :-)

Sreedhar T wrote:
Hi, its a really interesting stuff to read. Did anyone try doing it ?
One thing that I wanted to know was: How long does it take to do this ? Since Im using a time critical application, can this entire operation happen in 100 milli seconds ?
Will be glad to hear from you.
Regards
Sreedhar
I have used this for a program that needs to have a host IP address for High sped cameras. I have it change the IP address to the required address and change it back when I am done. Here is a very simple Labview version of this code with out the switch back.
Tim
Johnson Controls
Holland Michigan
Attachments:
TCPIP Config Programically.vi ‏10 KB

Looking for LabView 6i GPIB-USB-A driver for Agilent E7401A

I am looking for LabView 6i GPIB-USA-A driver for Agilent E7401A EMC ANALYZER.

Hi,
There is a driver for this device available for downloading from the National Instruments Instrument Driver Network. Here is a link to the download page:
Multi-Environment Certified IVI Instrument Driver
Unfortunately, however, this driver is only available for 7.0 and 7.1. Unless someone else on this message board has created one for 6i, you will need to create your own.
The other option is to upgrade to LabVIEW 7.1, which I highly recommend. There are many improvements over LabVIEW 6, including Express VIs, Event Structures, and many others. You can see the new funtionality of LabVIEW 7.1 with a free online demo version at this link
Try LabVIEW 7.1 FREE Online
If you are interested in upgrading, you can call your National Instruments Technical Sales Representative at (888) 280-7645. Have a great day, and good luck with your driver search.
-John M

LabVIEW Core 1 and Core 2 training effectiveness

I'm scheduled to take LabVIEW core 1 and core 2 training in the second week of October. I would like to get an idea on how effective this training is, and how to approach it.
I work in a test and measurement lab and we use LabVIEW to automate our testing (RF, EMI/EMC). We currently have some labVIEW programs up but no one to maintain/upgrade or design new processes and I am planning to step into this role. Is it feasible to expect to jump right in after the training?
Thank you.

Jeff·Þ·Bohrer wrote:
Core I and Core II will teach you the fundamentals of what LabVIEW does. (And some very valuable skills)
It will not teach you how to architect a robust framework for test. That's something you will need to learn to step into a Lead Developer role.
It will not "Give" you a source code control repository. That's something your boss will need to provide to keep your work product safe.
It will not provide mastery of best methods and practices with a thourough knowledge of the intracacies of programming in LabVIEW for yor companies needs. BUT, you found the forums.....come back often! You'll learn more here by accident than you might imagine!
I found Core 1 and 2 to be very nice affirmations of what I have learned here!
I would highly recommend taking this tutorial in advance, so it won't be totally alien to you when you start the training. It's better to start out with some questions and some answers, than no questions or answers.
Post-training, I would recommend Bloomy's LabVIEW Style Book. You don't have to get the latest, greatest edition - most of the guidance there is timeless.
[edit]
LOL it would appear that I am responding the wrong post. I assume Jeff has advanced LabVIEW knowledge.
Bill
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.

Labview 8 crashes when saving a vi with a 'Bundle By Name' function

We have a working vi (Get_AN_Fast.vi), created with Labview 7.1.
Trying to open this vi with Labview 8 crashes Labview.
Problem seems to be related to a 'Bundle by Name' function, but it is not that simple as using this function by itself wirks fine.
Any ideas would be a help.
Attachments:
Labview_Upgrade_Crash.zip ‏117 KB

Sorry for the delay, I have been testing on other machines.
We can reproduce the error on other machines, with completly fresh installs of Labview 8.
The ActiveX Object we are connecting to is our own COM server, for interfacing to USB based data acquisition devices.
I have found that when our COM server is not installed on a computer, then the VI will open, but with errors related the the missing COM Server.
When the COM Server is installed, Labview 8 crashes when opening the vi.
I realise that our COM server might have bugs, but it worked fine with Labview 6 and 7, and it is Labview 8 that gives the error, not our COM Server (which is a stand-alone executable).
I have attached a zip file with our COM server, it just needs to be unzipped to a temporary file, and then run the 'register.bat' file to register the server.
It will not install any other files on your computer and, can just be deleted when you are finished.
Thanks
Charlie.
Attachments:
COM_Server.zip ‏659 KB
Labview_Upgrade_Crash.zip ‏117 KB

Bat-emc labview

Similar Messages

Maybe you are looking for