Execute an applescript with labview 7.1

Is it possible to execute an applescript with labview? In my opinion an applescript isn´t a appleevent or? So i can´t execute the script. Is there a possibility to communicate with programms on the macintosh? I want to start a applescript with labview and want to read the information from the .txt file which the script writes also with labview. The reading from the .txt file is no problem but to start the script....I found a file which can do scripts. but something is strange with the file. It would be nice if someone could have a look to file and correct it or maybe have good tips for me.
Thanks a lot
volgi1
Attachments:
DoScript2001.vi ‏20 KB

Your VI is missing the CIN resource file. The error message says:
"This Code Interface Node has no code to execute. Right-click the node, select Load Code Resource from the shortcut menu, and select the object code file (.lsb)."
In LV7.1 there is an Apple event vi called AESend Do Script.vi at Functions >> Communications >> Apple Events. It sends a script to a scriptable application. I have not used Apple events much so I really cannot help you beyond this point.
Lynn

Similar Messages

Would a LabVIEW 8.5 Executable play nice with LabVIEW 7.1 Development on the Same System?

Our testing computer right now just has the user run the corresponding .vi file since we have LabVIEW 7.1 installed on the computer.
If I use 8.5 to compile this .vi to an executable, I realize that I must install the run-time support for 8.5. My question is what effect will installing the 8.5 run-time have on the ability to continue to run the other 7.1 VIs with LabVIEW 7.1.
Should I be concerned with losing MAX settings when installing the run-time support for 8.5? I want to be able to run 8.5 executables but also able to open up a 7.1 .vi file in LabVIEW 7.1 and run it that way also.
Thanks for your help! I have 8.5 on my system and the idea is to slowly replace the running of the .vi files with .exe files, I was just curious in case my .exe doesn't work I can still run the tests with .vi in the mean time.
Thanks for your help folks!

Just note one thing - installing the 8.5 RTE should have no effect on 7.1, but if your executable requires drivers (e.g. DAQmx) and you install a version which no longer supports 7.1, you will lose the ability to work with that driver in 7.1. I don't think NI has any drivers yet which are not supported in 7.1, but I believe there are some which are no longer supported in 7.0.
Try to take over the world!

Do executables built with Labview 8 Evaluation continue to run after evaluation expires?

Over the last couple weeks I've been tasked with evaluating the Labview environment and coming up with a recommendation as to whether I think our company could benefit from buying a license or two. In that time I've developed a couple standalone executable vi's that have proved useful for some of the environmental testing we're doing here in the lab. These executables will likely remain useful in further revisions of the product being developed, so naturally my question is:
Once my evaluation copy expires, will my executables continue to run?
I assume they will, but I thought it would be better to be safe and ask anyways.
There you go, simple question, hopefully simple answer.
Thanks!

Hey Alex,
You should be good to go with the exes you build with your eval version. We don't place any timing restrictions on built executables. For more information on eval limitations see What Limitations Does the LabVIEW Evaluation Version Have?
Thanks!!!!
Chris C
National Instruments
Chris Cilino
National Instruments
LabVIEW Product Marketing Manager
Certified LabVIEW Architect

Installing Test Executive 5.0 in LabVIEW 6.0.2

I'm trying to install Test Executive 5.0 in LabVIEW 6.0.2. However, I run into problems. When i Try to mass compile the test executive folder I get a lot of errors (see attached file), and I don't get the executive in the tools menu.
Could someone tell me what needs to be done?
Thanks,
/Martin
Attachments:
mass_compile_TestExec.txt ‏32 KB

I use Test Executive 5.1 with LabView 6.1 (after doing a mass compile) and have no problems.
It looks to me like Test Executive isn't installed correctly so some VIs are missing or in not the expected place. Try reinstalling Test Executive. Don't move any of its VIs after you install it.
You get a ### Bad VI message for a VI if any of its subVI's are missing. There's probably a lot of other reasons for Bad VI, but a bad install seems like the most likely reason. A install may be bad if it's incomplete or simply if you install it to a new location and the VIs that use it are still referencing the old location.
Test Stand is a much more powerful product (and I use it on other applications), but for an existing application with a limited budget, we upgraded LabView,
the PC and Windows, but we didn't replace Test Executive with Test Stand. Going to Test Stand, you not only have the cost of the Test Stand software, you also have the development cost of rewriting some code for Test Stand. Depending on your application and how much you customized Test Executive, the development cost may be significant.

Remote front panel with labview 8.6 executable

I am trying to create a remote front panel of my application, built in an executable using Labview 8.6. I want to run that application on a target machine (not the one used for developing the project) and view and control the front panel of the VI from a web browser on another computer.
I have followed these steps:
How can I use remote front panels with Labview Executables?
But when I finally open the web browser and navigate to the URL I obtain that the page cannot be found.
I have my Labview project created and I have built a web page using Web publishing tool. I have saved it in my Labview 8.6/www directory and added it to the project. I have built my executable including HTML file and copied all the obtained folders to the target PC.
Then, I have modified the .ini file like in the step 7, but when I arrive to the step 8 I don't know what to do. Which niwebserver.conf should I modify? The one localized at Labview 8.6 directory of the target machine? Or the one that is created in the directory where I have copied the executable when I run the executable?
In the DocumentRoot tag I have to replace the default Labview/www with the location of my HTML file. Should I use quotation marks or no?
Have you got any ideas of what is happening?
Thanks!

Ok, but when I create the executable, in the folder where the application.exe and .ini are there isn't a file called niwebserver.conf. When I run the application a file with this name appear in the directory (the one I include), but it hasn't the section Directives that apply to the default server as in the manual.
What I have done is to copy the niwebserver.conf file ubicated in the Labview 8.6 of the target machine in the same directory of the executable but it doesn´t work...
niwebserver.conf
ServerRoot "."
ErrorLog "./logs/error.log"
LogLevel 3
ServerName default
DocumentRoot "./../../www"
Listen 80
ThreadLimit 10
TypesConfig mime.types
DirectoryIndex index.html
LoadModulePath "./modules" "./LVModules" "./.."
LoadModule LVAuth lvauthmodule
LoadModule LVSnapshot lvsnapshotmodule
LoadModule LVRFP lvrfpmodule
LoadModule LvExec ws_runtime
LoadModule dir libdirModule
LoadModule copy libcopyModule
AddHandler LVAuthHandler
AddHandler LVSnapshotHandler .snap
AddHandler LVRFPHandler
AddHandler LvExec
AddHandler dirHandler
AddHandler copyHandler
CustomLog "./logs/access.log" "%h %l %u %t \"%r\" %>s %b"
KeepAlive on
KeepAliveTimeout 60
Timeout 60

Execute a VBAI code with Labview

Hello
I work with a CVS, and for that I create a VBAI code that I need to use with Labview, I already use the tool "migrate inspection to labview" and tryed this VI. I added the "inspect main" VI on my cvs target, but I did'nt do what I put on the VBAI code.
How can I do to execute exactly the VBAI steps in Labview.
Thank you for your help
Attachments:
Inspect Main.vi ‏103 KB

Here's a sample LV 2013 project with a CVS target and the build specs to get a startup app.
1. Right clikc on the CVS and select Properties. Change the IP Address to match your target's.
2. Right click on the "My Real-Time Application" under Build Specification for your target and select Build
3. Once the Build is done, right click again and select Deploy. This should automatically create a Configuration Files folder on the target with the correct files.
4. Right click again and select "Run as Startup" and this will ask you to reboot. Now the VI will start running when the target reboots.
If you need to debug, you can stop the startup app on the CVS by right clicking on the target and connecting. Then just open the Inspect Main.vi from the project when it's under your CVS target) and run it. The Configuration Files should already be downloaded to the target after following the above steps.
Hope this helps,
Brad
Attachments:
Sample Project.lvproj ‏36 KB

Open and close multisim contact with LabVIEW

Can I open and close multisim contact with labview and read the receptor estatus (p.e. lamp)?
Thanks.
Attachments:
Dibujo.JPG ‏13 KB

Hi Guddan,
I created a RFC having a query which is taking a long time to execute. So i want to close RFC connection with portals which is via java connector(JCO) before that query and open the connction again after that query.
I guess i will need to understand your requirement a little more in detail, as i understand you have an RFC which has a query within to fetch some data and is taking a long time to do so. In the meantime you don't want to keep the connection open?
My question would be, Is the role of this RFC to only execute the query and fetch the data or does it do something else?
If it does other things and these are independent of the query execution, then you can span a parallel call within the RFC to execute the query and in the meantime the RFC does the other things (or vice versa) hence reducing the overall time taken.
If the sole purpose of this RFC is to execute the query, then you will not be able(i mean to say there is no simple and direct way of doing this) to close the connection after the Query is started and re-establish the connection after its execution, for a simple reason that - how will you know if the query has completed it's execution, so that you can establish the connection back.
Alternate solutions, make this a two way asynchronous call, 1) You invoke the RFC asynchronously and close the connection, the RFC in turn will execute the query and transfer the data to JCO via another RFC call.
If this needs to be a synchronous call, then you will need to optimize the query to its best.
Regards,
Chen

Lost ActiveX connection with LabVIEW server

I have called LabVIEW in TestStand and tried to execute the test cases .
While executing I got the following error: ( Lost ActiveX connection with LabVIEW server.
The LabVIEW adapter will try to reconnect on the next execution attempt.-18001; An error occurred accessing the LabVIEW ActiveX automation server.).

Same error. Is anyone from NI going to bother commenting on this? It's been >8 months...

How can I call a LabVIEW executable from within another LabVIEW executable?

I have a customer requirement for two LabVIEW executables. Based on their current setup, they need to run executable "A" or "B", both of which are under independent revision control. I have created a third "selection" executable that allows the operator to choose between one of the two, but I am receiving errors when I attempt to call a LabVIEW executable from within a LabVIEW executable using either the "System exec" VI or the "Run Application" VI. If I call a non-LabVIEW executable (such as Windows Explorer) everything works fine.

> I have a customer requirement for two LabVIEW executables. Based on
> their current setup, they need to run executable "A" or "B", both of
> which are under independent revision control. I have created a third
> "selection" executable that allows the operator to choose between one
> of the two, but I am receiving errors when I attempt to call a LabVIEW
> executable from within a LabVIEW executable using either the "System
> exec" VI or the "Run Application" VI. If I call a non-LabVIEW
> executable (such as Windows Explorer) everything works fine.
As with the other poster, I suspect a path problem. You might try the
path out in a shell window, and if it works, copy the complete absolute
path to LV to see if that works. LV is basically passing the comma
nd to
the OS and doesn't even know what is in it, so you should be able to get
it to work.
The other poster commented on subpanels, which is a good suggestion, but
without going to LV7, an EXE can have open more than one VI. You can
use the VI Server and the Run method to fire up another top-level VI.
The decision is whether you want both to be in unique processes.
Greg McKaskle

Install labview 6.1 (or compatible) run-time engine with labview 2011

I have installed a trial period version of Labveiw 2011 in order to check for possible upgrade issues I may have if I decide to upgrade from labveiw 6.1. Well, needless to say there have been alot. That is as expected since I have not updated labview in many years. I am still not under any pressure to update; however, I would like to in order to get support and make sure I do not have any compatibility issues with new equipment purchases. I have been able to resolve most of my compatibility issues with simple code fixes and such. However, twice now I have run into an error when launching labview executeables compiled by two different equipment manufacturers. The equipment I am using is not even old...maybe a year or so. When I launch the labview executables to control this equipment on a PC that has the trial period labview 2011 installed, I get an error message stating something like " This requires a Labview 6.1 (or compatible) run time engine." I have tried to download and install the 6.1 labivew engine but I can't install this engine on a PC which has labview 2011 installed. Can someone explain how I am to run these executables under labview 2011. I can't imagine these executables were developed using 6.1 since this equipment is not even a year old now.
Solved!
Go to Solution.

Im not for sure I am on the same page with you here. Im not trying to develop any code myself. I have some labview executables that came with hardware we purchased in order to control it. We used to have labview 6.1 installed; so everything was working ok. But now that I have installed 2011, I get an error message when trying to run these executables. The error message states that this executable requires a labview 6.1 or compatible run-time engine. I have seen this error on both XP and Windows 7 machines. I did not develop the executable, it was developed by the hardware manufacturer. But since this hardware is only about 1 year old, I an assuming they used a newer version of Labview to develop this code. Certianly newer than 6.1.
So I guess my question is..is there a way for me to get this executable to work on a PC that has labview 2011 installed. I have tried to install a labview 6.1 run time engine but it will not install. Any other options?

Unload All Modules sometimes doesn't work with LabVIEW

TestStand's File >> Unload All Modules (and its RunState.Engine.UnloadAllModules() function) sometimes works and sometimes doesn't (with LabVIEW). When it doesn't, I have to quit LabVIEW to make TestStand unload LabVIEW VIs, otherwise I can't edit them.
Is there an "Unload All Modules" command that works all the time?

Hm, i assume that you have callbacks defined which do call those modules. Possible callbacks to look first are: SequenceFileLoad/Unload, FrontEndCallback.
Another possible reason is that there are components running in the LV RTE (runtime engine) calling into the VIs you try to debug/modify in the development environment.
Can you pinpoint the "lock" to specific sequences/modules? Do they lock only after specific sequences/modules have been executed?
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

Setting Search Directory with LabVIEW RTE

Hi,
I've LabVIEW 8.0.1 run time engine installed on target computer and would like to run LabVIEW executable on target computer. I also have required low level support VIs for developed VIs.
Question is: how do I set the search directory for low level VIs with LabVIEW run time engine installed on the system.
Suggestions/comments are appreciated. Thank you.

If your hierarchy is the same as was in the IDE, then there won't be a need to search for the VIs. If the VIs are not found where they are expected to be, then LV (including the RTE) starts to search for them first in the folder where the VI\application is and then in the folders in its list. To change the list, you need to place the viSearchPath key in your application's INI file. You can copy this key from the labview.ini file and then modify the paths listed in it.
Try to take over the world!

TCP/IP communication with LabVIEW Full?

Hi,
I would like to know if the TCP/IP VIs are included with the Base or Full version of LabVIEW?
I was looking at the different versions of LV and one of the features of the Pro version is 'Network Communication'.
I have done TCP/IP communication a while ago and I am quite sure it was with the Full version. I have the Pro version now but this is for a customer.
This brings another question: Is there a trick to be sure your code is going to work on a system with LV Base if you develop on a system with LV Pro?
Thanks!

I think that was a good answer to your first question. To answer your second question, if you are creating executables to be run on a computer with LabVIEW Base there will be no problem running the executable because LabVIEW Base has the run time engine. If you are sending VIs to another computer with LabVIEW Base they will not be able to access any VIs that are not included in there package. There is no simple way to tell that these VIs are not included except through the link in the previous post. In LabVIEW 8.6 many of the help documents state what LabVIEW package installs the VI. If all of the VIs state that they are installed with LabVIEW Base you will have no problems.
Vince M
Applications Engineer

Interacting with labview with my own developed scritpting language.

Hi all,
I am Divya.
My aim :
I need to develop a programing language to interact with Labview such that the script should call labview front panel, execute the given task and front panel shold give back the result to the script.
I want to achieve this by using my own developed programing language (Valid reasons are there why not to use already exixting scripts which I dont want to discuss here as it is not relevant).
My idea :
As developing a new scripting language is a big task I am planning to start with Python scripting. I am trying to interact with labview using python script for now.
My problem :
As I am fresher to this field I dont know the possible ways to interact with Labview using python scripting. (Except using Labpython). If there is any way to achieve this please guide me on this.
Thanks in advance

Hi Dennis_Knutson
I am doing the same as the original question I have asked. As I have mentioned in my question I am starting off with a small addition (or any basic mathematical operation) function using Python script.
And yes the basic idea is to call Labview from script not the vice versa. To achieve this I need to pass the parameters from the python script to Labview and output from Labview to Python. For this purpose I am developing a small VI which vil take Python commands and carry on furthur operations.
I can explain with an example.
I have a command in python as sum=x+y. I want to take this command and send 'x' to a numeric control, 'y' to another numeric control and 'sum' to a numeric indicator and at the same time back to script. In between numeric controls 'x' and 'y' I need to carry out '+' operation. Say if the command is sum=x-y I need to carry out '-' operation(Where identifying '+' or '-' or any other operation is the job of labview).
I have developed a VI which can take the command from python and give it to Labview as a string. I need to know how to bifurcate that string to numeric controls, operands etc.

Error -18004 with LabVIEW Adapter using LabVIEW Run Time Engine 7.1.1

Hi to all,
I am trying to use the LabVIEW Run Time Engine 7.1.1 instead of the Development System for executing VIs in TestStand with the LabVIEW adapter.
The Problem is that I get the following error, saying that my VIs cannot be executed:
-18004; An error occurred accessing the LabVIEW Run-Time Engine DLL.
All my VIs were masscompiled with LabVIEW 7.1.1
How do I manage this problem, in other words how do I get my VIs in TestStand to run with the LV Run Time Engine?
Thanks for you help,
- Caribe -
PS: I configured the adapter to use the LabVIEW Run Time Engine 7.1.1. When I check back in the dialog "LabVIEW Adapter Configuration" the selector went back to LV Runtime 7.1??? Thats weird dude!

Hi Caribe,
Did you find any solution to this weird behaviour? Even I am facing the same problem! If we set the adapter as LV 7.1.1 runtime engine, it changes back to LV 7.1 runtime engine.
I am also facing -18002 error after mass compiling LV 7.1 folder and my source code folder.
If you can share your solution, that would be of great help to me. If i couldnt find any solution, I have planned to revert back to LV 7.1 version.
Thank you,
Sasi

Execute an applescript with labview 7.1

Similar Messages

Maybe you are looking for