Running Continuum ND 6000 dye laser in LabView

Our lab recently received a Continuum ND 6000 dye laser and we would like to run it via LabView. However, it seems the software that the company gives out is DOS-based and the groups I have talked to all run the laser off of a computer that came with the laser (a computer that we do not have). I know you can talk to the laser using serial commands, and I was wondering if anyone out there had been able to communicate with it without using the DOS software or the aforementioned computer and could give me some insight in how to set this up in our system. Thanks, Carrie

Hi Carrie - I have been unable to get your code to work. I think the code is fine, but it is something about our setup that seems to be the problem. I can install a straight-through cable, and talk to the laser using the windows software. I can record these interactions with PORTMON, and see that it is transfering odd commands ("8V2.99", "8D777664", "8G", etc). I can turn off the software, and reissue the commands above in quotes, and I can hear the motors spinning (even if I don't know what the commands do). However, if I put a NULL MODEM cable in, at best I can get the port to echo commands back at me. Under no circumstances can I get any further response, and there is no sign of activity on the computer. I am stumped. Any ideas? One final observation - it appears in your code that you set the stop bits to 2, which differs from the manual (1 stop bit). Is this an error in the code, or a typo in the manual? Many thanks, RipRock PS: I don't know if this is verbotten on this board, but I could leave direct contact info if that would help.

Similar Messages

How to run downloaded drivers on Fresh Install of Labview 6.1 on a Mac G4 OS 9

I have just completed a fresh install of Labview 6.1 on an Macintosh G4 running OS9. I can run it and it seems to work just fine. I downloaded some drivers for an oscilloscope (HP 546XX) to run with an HP 54603b. When I installed, I went to open the 'Get Started.VI' I get a freeze and have to force quit out of labview. I am not sure how to resolve this. I am pretty sure that it is independent of the device, since I can open the vi's at least on another computer with no hardware attached. So I guess to boil my situation down. I have 2 questions:
-How do I get a fresh install on a mac G4 OS 9 to run downloaded drivers from the internet
-How do I ensure that I have the hardware configured on
a macintosh to run properly.
I really have little experience with macs so I am not really sure what my options are or what could be the problem so any assistance would be much appreciated.

Hmmm. I wonder if NI-VISA isn't installed correctly on this machine.
When LabVIEW loads a VI that uses a VISA name control on the front panel, it queries VISA for the installed devices. Sometimes this takes a few seconds, but maybe in your case, something has been corrupted and it's hanging.
To try to narrow this down, first run the separate program "VISAConfig". This should list your devices. If this works, this means it's pretty likely that VISA is installed correctly.
Next, run LabVIEW. On an empty front panel, select the "Controls->I/O->VISA Resource Name" and place it on the front panel. When you click on the arrow on this control, you should see a list of your devices. If this works, then that indicates that LabVIEW is successfully talking
to the VISA software.
If both of those succeeded, then we have to take a closer look at this particular instrument driver. Can you drop other VIs (say, Initialize or Close) without hanging?
If either of the first two steps fail, I'd suggest that you reinstall the VISA software. You may want to try the latest version of NI-VISA (from ni.com), but first confirm that it supports LabVIEW 6.1.
I hope this helps.
Brian

Error 15 at "Run VI" Invoke Node When Building a LabVIEW Executable

I am trying to run a vi by using the "run VI" method of the invoke node. The source code works perfect. However, I cannot run the vi when I use the executable version. Specifically, I get the Error code 15 at the "error out" output of the invoke node while using the executable version. Why is this occuring?
Thanks

Hello ameng,
This behavior is typically the result of trying to call VI that has had its front panel removed. The KnowledgeBase linked below has more information on this issue.
Error 1 or 15 Opening Dynamic VI from LabVIEW Application
Please let me know if you have any other questions about this issue.
Regards,
Matt F
Keep up to date on the latest PXI news at twitter.com/pxi

Exchange value from a running sequence teststand and an independent vi LabView.

I have a teststand sequence, which runs with a local variable.
I want to read this local variable in a independent vi.
Are you an Idea ?

Sebus,
I'm not sure what you mean by an "independent vi".
If you have a VI that TestStand calls, the post entitled In TestStand, how to pass data to LabVIEW will probably be very helpful. In addition, there are Getting Started guides that explain this concept and with TestStand 3.0, there is a whole manual called "Using TestStand with LabVIEW" that walks you through step by step how to use TestStand and LabVIEW together.
If you have a VI that executes your test, this VI would be considered an Operator Interface. For this situation, you can use the TestStand concept of UIMessages to pass data from your sequence to the operator interface. This is described in more detail in the TestStand help. UIMessages are a TestStand object that you can pass from your sequence to your operator interface. Since the engine actually executes the sequence, you do not have access to the internal sequence characteristics mid-execution. By using the UIMessages, you can have your sequence automatically send data, and then your Operator Interface will retrieve these messages.
The third scenario is where your VI is not connected to TestStand at all. In this case, if you truly have no connection to TestStand, this is not possible. However, if there is a common shared application then you can use that to pass data. For instance, you could use Datasocket (see DataSocket Overview
for a brief synopsis) and have TestStand pass the value of the local variable and have LabVIEW read from Datasocket. There is also an ActiveX server that TestStand has called the Synchronization server. This is used internally with the Synchronization step types. However, since it is based upon ActiveX you can use each of the methods and properties that are available; the functions just are not documented. You could use the queue synchronization type to pass data from TestStand to your independent LabVIEW VI.
If this does not answer your question, please let us know and clarify what you mean by an independent VI. Also, the versions of TestStand and LabVIEW would be helpful.
Regards,
Shannon R
Applications Engineer
National Instruments

I cannot run the matlab script node in the labview

Hi there,
My LabVIEW version is 8.5, and matlab version is R2008a.
I wrote a simple matlab code, like x= 1, y = x*2. Then I tried to put them into matlab script node in LabVIEW.
However, when I ran the program, I couldn't run and Labiew show some error.
Then I tried the method talked before on this forum. Please see the following link.
http://forums.ni.com/ni/board/message?board.id=MathScript&thread.id=571
I followed the instruction and open the "command prompt," type some commands then I could run the program, and simultaneously, the LabVIEW program open "Matlab command line window" and run my labview code. However, if I didn't use the command prompt, the "matlab command window" will not be opened by running the labview program. It would just show some error. And even if I turn on the matlab program in advance, I still couldn't run the labview program.
Is there any effecient way to deal with this problem without using "command prompt?" Because I try another PC with both matlab and labview installed on it, I "can" run my simple matlab script node on it, and it will open the matlab command line window automatically by running my code. Therefore, I thought there might be some software linking problems in the previous PC I used . Do you have any ideas?
Thanks in advacne.

Hi, and thanks for the post! I hope your well today.
This may help,
MATLAB® version 2006b (7.3) and version 2008a do work with LabVIEW
8.20. This problem can occur if a new version of the MATLAB® software
is installed along with a previous installation, which is then
uninstalled. The uninstallation of the older MATLAB® software results
in removing the ActiveX/COM components LabVIEW uses. This can cause the
MATLAB® script node in LabVIEW to stop working. There are three
solutions to this problem.
Uninstall the MATLAB® software and reinstall it. This should install the necessary ActiveX component.
Restore the MATLAB® automation server. Browse to the \bin directory (e.g. MATLAB\R2006b\bin) and type matlab -regserver ,
which will reset the registry settings and start the server. The server
can then be closed and the MATLAB® script node will work properly again
in LabVIEW. LabVIEW may need to be restarted if VIs are open that
contain MATLAB® script nodes.
Leave both versions of the MATLAB® software installed.
MATLAB® is a registered trademark of The MathWorks, Inc. Other
product and company names listed are trademarks and trade names of
their respective companies.
Did you have an older version of MATLAB before 2008a?
Kind Regards,
James.
Kind Regards
James Hillman
Applications Engineer 2008 to 2009 National Instruments UK & Ireland
Loughborough University UK - 2006 to 2011
Remember Kudos those who help!

Why i can not see the biomedical palette on the function palette when i run biomedical startup kit 8.5 on labview 8.6

Hi. I am trying to install biomedical tools on my labview 8.6. when i run the biomedical startup kit 8.5, it installs correctly, but when i go to see if the biomedical palette exsists on the function palette i dont see it.
can somebody help.

Howdy Boulos,
I looked into this issue a little and found that you have also emailed into support. I'm going to work with the engineer assigned to that request, but you can expect your primary source of information to come through email.
The quick answer to your question is that the Biomedical Startup Kit you downloaded is for LabVIEW 8.5, while you have LabVIEW 8.6 installed. I'm checking to see if there is a way to port the VIs over manually into the LabVIEW 8.6 palette, but I'm not confident this will work at this point.
We will let you know through email what we find out, but the official answer at this point is that the program you've installed is not supported under LabVIEW 8.6. Thanks, we'll keep you updated.
Sincerely,
Chris G in AE

Running Excel macro to format sheet from Labview?

Hey, thanks in advance.
I am trying to put together a VI that can run a macro in Excel. The macro I recorded simply formats some of the cells to be bold, sets the widths/heigths, merges some cells, adds some border, etc. I have been trying to piece together a bunch of examples from the discussion forum, from LV, etc. for doing this with ActiveX. I'm really starting to bang my head on the desk... all I need to do is make all the data my program sends to Excel pretty without having the operator (or supervisor) have to do this manually.
Does anyone have an example of a program that opens a file based on an extension you give it, runs a macro, then closes the file? Or other suggestions for doing this?
All the other examples I've looked at are different enough that I just can't make it work.
Thanks a million!

Well adam welcome to the world of active x. One trick I have learned with using it is when I want to do something in the program that uses macros (ie word, excel.) then what I do is create the macro and look at the code, then I will usually duplicate the code in labview using invoke and property nodes just because I do it that way does not mean it is the best way. I do it this way so I do not have to worry about someone deleting the macro. But running the macro is not trivial if you decide to go that route. Here are a bunch of vi's that will help you out.Message Edited by jhoskins on 04-27-2005 09:00 AM
Message Edited by jhoskins on 04-27-2005 09:00 AM
Joe.
"NOTHING IS EVER EASY"
Attachments:
Excel and word toolkit.zip ‏2013 KB

Labview run-time 8

Tengo instalado en mi computador con Windows XP Labview 6.1, y queria abrir unos VI's que baje de internet pero no podia pues necesitaban ser leidos por lo menos en un Labview 7... Por lo que instale el LabVIEW Run-Time Engine 8.0 for Windows 2000/XP. Baje dos archivos ejecutables desde la pagina de NI: "LVRunTimeEng.exe" (25 MB) y "LabVIEW_8.0_Runtime_Engine.exe" (89 MB). Segun la pagina debo instalar solo uno. Aca coloco el leame:
Description:
This document contains the LabVIEW 8.0 Run-Time Engine. This Run-Time Engine must be installed on any Windows system where you plan to run executables that you build with the LabVIEW Application Builder. Version 8.0 of the Run-Time Engine may only be used to run executables that were built with LabVIEW 8.0.
Additionally, the Run-Time Engine allows your browser to display VIs that are embedded in Web pages.
There are two downloads that are available. You only need to install one of them. LVRunTimeEng.exe is a smaller download intended when viewing Remote Front Panels in Web pages. It does not contain the full run-time engine, but will allow some executables to run. For full support for executables use the LabVIEW_8.0_Runtime_Engine.exe. This version will support all executables built with LabVIEW as well as allow viewing of Remote Front Panels in web browsers.
Installation Instructions
Run LVRunTimeEng.exe or LabVIEW_8.0_Runtime_Engine.exe to install the LabVIEW 8.0 Run-Time Engine.
If you were attempting to view a VI through a browser and you were directed to this site by your Web browser, the VI will display correctly after you install the Run-Time Engine.
See the PDF files for Japanese (JP), French (FR), German (DE) and Korean (KO) instructions.
Older versions of Run-Time Engine
To run applications built with an older version of LabVIEW you will need the corresponding run-time engine installed. You can have multiple run-time engines installed at the same time. See the All Versions list of Run-Time Engines to download an older run-time engine.
Quise instalar el de 89 MB, (fueron como 15 partes). Me pidio reiniciar pero al ver el menu Inicio o las carpetas donde se instalo, no vi nada del Labview Run-time engine. Y todavia cuando ejecuto un VI hecho con versiones nuevas, me sigue apareciendo el error en el Labview 6.1 que debo abrirlo en una version 7 o superior. Quiza pueda tener el error que debo instalar tambien el Labview Run-Time Engine 6 (creo que algo dice el ultimo parrafo del texto que copie en la pagina de NI)
Ojala me puedan ayudar, porque sigo sin abrir archivos de labview en mi version 6.1

It appears that you want to open a VI in LV 6.1, but that VI requires at least LV 7.x.
The runtime Engine of LV is only capable of running EXEs built with LV. If you want to open the Source code of a VI, installing LV 8 Runtime Engine won't be any beneficial.
These are your options:
1- Use a LV Development system ver. 7 or higher.
2- Find someone who has LV 7 and ask him to downconvert the VI to 6.1 by selecting "Save for Previous versions"
Adios
AlessioD

Unable to locate labview run time engine (lab view 8.5)

Hello I have a problem whit the labview 8.5 installer. I have created I project with included a .vi file (a simple panel wich control a serial port, with parameters (baud rate, stop bits, ...)), then I have created an application for this file (.exe) and then the installer (I have included the labview run time engine 8.5). When I run the setup.exe I have the following error message:
Unable to locate labview run time engine, the application require a labview run time engine 8.5 or compatible...
What I'm missing??
Thanks
Maurizio

are there one other reasons why it would not work. I have asimilar problem.
I intsalled version 8 of run time engine and acrtivated software. Now I am trying to run compiled application provided to me by third party.
When I click on application it says
Unable to locate LV run time engine
Test server requires a version 6.0 or compatible LV engine.
How do I know if the engine I installed and activated is running and is it supposed to be able to execute a program which is expectin rev 6 of the rund engine?

Why is VI not executable using Labview 7.1 Run-Time Engine?

Hi,
In our Teststand sequence, we have a Labview Action step which is returning an error: "The VI is not executable", along with the error code: -18002.
This error occurs on a Production PC using the L.V. 7.1 Run-Time Engine.
I'm aware of Mass Compiling to ensure all the VI's are the correct version, but this has not resolved the problem.
The software was installed on the production PC using a Teststand created installer, with the Labview Adapter set
correctly to the Run-Time Engine, i.e. not trying to open the Labview Developer Server to execute the step at run time.
Because it's the 1st Labview module to be executed, I added another similar step to run beforehand, i.e. the new simple
Labview code ran first. This executed correctly, but then the next step caused the error above.
The small number of associated sub-vi's are on the target PC, and have been mass compiled.
I've had -18002 errors before, but this is one I cannot cure.
All suggestions gratefully received.
Gary.

Hi Guys,
Regarding this -18002 error when using the Run Time Engine instead of the Development Environment, what is the VI within the step that is failing (in any of the cases you've mentioned) trying to do? Are they built around any toolkits?
In my experiments with a simple VI (with just a user dialogue) using the LabVIEW 7.1 RTE in both TestStand 3.1 and 3.5 this morning, I haven't found any issues
There is a possibility if any of the sub-VIs or toolkits you use contain a Merge Errors.vi, that the Run Time Engine picks up a copy of the VI built for previous versions of the RunTime Engine (due to the order in which the sub-VI directories are scanned), and it cannot convert it.
There are a few solutions for this, the easiest one looks to be to copy the error.llb\Merge Errors.vi for LabVIEW 7.1 into the same directory as the VI you're calling (so TestStand can pick it up easily).
Can you let me know if this solution helps at all? If not, would it be possible to post up any of the code or sequence you're having problems with?
Best wishes,
Mark
Applications Engineer
National Instruments

Trying to run Accutest 1000 manufactured by Physical Testing Equipment with Labview

We have an Accutest 1000 which is manufactured by Physical Testing Equipment and we would like to run the equipment and gather data thru Labview.
Does Labview support this type of activity? Is there a 3rd party that would contract to set-up this configuration?
Thanks

National Instruments doesn't officially support interacting with this board. Do you have more information about it? Can it communicate via serial? If so, you could try to use NI-VISA to communicate with the board.
Ravi A.
National Instruments | Applications Engineer

Are LabVIEW VISA functions supported by LabVIEW Run Time Engine?

I have an executable file that I created using LabVIEWS Application Builder. When I run the application on another computer that does not have LabVIEW installed, it crashes with a Windows message stateing the my application has generated erros and will be shut down by Windows. I have isolated the problem as having something to to with VISA Reasource Names.
Does anyone know if there has been any issues regarding the use of VISA function in LabVIEW Run Time Engine? The version of LabVIEW that I have is 6.0.2. The version of Run Time Engine is 6.0 .
Dan

Yes there are issues with the RTE 6.0 and VISA. Use the RTE 6.0.2
LabVIEW, C'est LabVIEW

How to change options in Run time menu while labView was running

Hello Good Afternoon,
I m Using LabView 8.5.How to change the options in Run time menu for any control while Labview was running
Thanks
Jai
Jayavel
Solved!
Go to Solution.

Hi Jai,
Try the below attached VI and let me know if u still need some explanation.
Rgds,
Venky
Attachments:
Run Time Menu.zip ‏6 KB

Acquiris card wont run under Labview 64bit

HI everyone,
I try to run a Agilent Acquiris card (U1082A) with Labview 64bit version under Windows7. The drivers are already installed and it works just fine with the Labview 32bit Version. Agilent supplys a 64bit driver and also Labview VI as seen in the following screenshot:
When I now insert just any of these VI's into Labview, it won't run. It says it doesn't find the function in the library:
I re installed the drivers now, just two different other system with Windows7 and it still won't work. Any suggestions on where the error may be?
Greetings from Wisconsin,
Arne Petersen

Arne,
Greetings from Texas! It looks like the function name in the library call is incorrect. Are you able to browse the functions included in the DLL to select the right one. The function itself looks like it may point to a 32-bit version (perhaps an oversight in the development of the code). Even if you can't see the included functions, I would still try to change the function name to _AcqrsD1_configVertical@64 instead of _AcqrsD1_configVertical@32.
In actuality, however, this is an issue with the function call to a DLL developed by Agilent, contained in a VI distributed by Agilent. They will probably be able to help you a bit more in this issue, if the above suggestions do not help.
Good Luck!
Drew T.
NIC AE Specialist

Running Datasocket in labview 2013 open labview runtime engine 7.0

Hello All,
I am trying to communicate with a COGNEX camera using Labview 2013. I am using Datasocket to read tags from cognex OPC server.
but when I open labview and run the code for the first time. An installer will automatically pop up trying to install labview runtime engine 7.0.
When i cancel the installation datasocket throws an error. Again if i run second time, datasocket works fine and communicate with cognex camera using OPC.
This problem comes everytime I open labview and run the datasocket. I cancel the installer. second time onwards when i run the code everything works fine.
This is actually annoying and i doubt how things will work when i make an executable.
Need help.
Is this due to datasocket version installed... how to resolve this.

Hi phil,
That is interesting that you were unable to find the offending key that the installation is having trouble with. Do you have Administrator privileges on your computer? You may even want to try to log in as the actual Administrator itself to make sure that you have access to all of the proper registry keys. Also, I was going to say that I do think you're right with Windows XP not having the Scanreg/fix function, but there are several free programs that you can download as registry checkers. You may want to try one of those to see if you can find the key and give it the proper permission.
As far as the other part of your question, the Run-Time Engines are very important for LabVIEW to be able to run, but the 7.1.1 Run-Time Engine should not be affecting a LabVIEW 8.2 installation as it will use the 8.2 Run-Time Engine. One thing that you can do is go into your Control Panel under Add or Remove Programs>>National Instruments Software and you can try and repair/modify your Run-Time Engine there. If you already have the 7.1.1 Run-Time Engine on your computer, this is where it will show up so you can make any changes you want. Also, if you go to www.ni.com and click on "Drivers and Updates" on the right, you will be able to find the Run-Time Engine there that you will need, but I would definitely try using a downloadable registry checker first before attempting to change any of the software that is currently on your computer. As stated in the Knowledgebase article, this is actually an error from Windows saying that the registry key does not have the proper permission settings, so I am reluctant to say that downloading the new Run-Time Engine from our website will help much. Please try some of these suggestions out and let me know how they work out for you. Thanks!
Regards
Noah R
Applications Engineering
National Instruments

Running Continuum ND 6000 dye laser in LabView

Similar Messages

Maybe you are looking for