ELVIS 1 AND ELVIS II LABVIEW VIs COMPATIBILITY

I am currently working on a project that was previously using Labview (8.5.1) vis built for elvis I, we have now moved on to Elvis II and are experiencing problems that are believed to be steming from the differences in channel configurations. Could some one be as kind to avail channel configurations for both elvis I and Elvis II and what modifications we may need.

Hi,
First, I want to reference you to the support page for the NI ELVIS II and its help manual.
NI ELVIS II
http://sine.ni.com/psp/app/doc/p/id/psp-458/lang/en
NI ELVISmx Help
http://digital.ni.com/manuals.nsf/websearch/825085B4A34566818625745F006DF0F8
I want to verify what exactly is going on in your program when you upgraded to NI ELVIS II. Are there any errors you are seeing? Are you able to get it working in Measurement and Automation Explorer? Also, what drivers are you currently using?
Regards,
Jordan F
National Instruments

Similar Messages

Using HTTPS and SSH from LabVIEW VIs

I am currently using custom VIs, built over the TCP/IP LabVIEW VIs, to access to a distant machine with the TELNET protocol, and to access a HTTP server with the HTTP protocol.
In a near future, I will have to use more secure protocols such as SSH and HTTPS, that my VIs will no longer support.
Does the NI Internet toolkit support SSH and HTTPS?
And if it doesn't, what are the solutions?
Using PuTTY with a command line for SSH is suggested by NI and I have already tested this successfully.
Have someone other solutions and an idea for using HTTPS?
I'm currently using LV 6.1.

Hello,
You could find other solutions on this forum thread : http://forums.ni.com/ni/board/message?board.id=170&message.id=77865&requireLogin=False
Regards,
Isabelle
Ingénieur d'applications
National Instruments France

Measure current and voltage in Elvis and labview

Hi! We're setting up a control system setup for class where we need to monitor the current and voltage that we are supplying/drawing from the ELVIS hardware within a LABVIEW setup. So far, we can accurately display voltage input and outputs from the AI and DAO terminals respectively. However, we can't seem to find a direct way measure current draw. I believe that we are supposed to be able to get DMM readings from the AI5 channel, but either we're not doing it correctly, or we still need to place a known resistance across it (which we cannot do, due to variable loads). Any advise please?
Cheers,
Gerald

Are you using Elvis I or II? From your post, I will assume it is Elvis I but please correct me if this is not the case. Page 38 of the manual shows that ACH5 is used for capacitor or diode measurements for the DMM. To measure current, use the connectors on the front of the Elvis unit and then route the current HI/LO on the protoboard to either the oscilloscope or an analog input channel. You can use the DMM Soft Front Panel to monitor current as well.
Message Edited by h_baker on 07-09-2009 04:54 PM
Regards,
h_baker
National Instruments
Applications Engineer
Digital Multimeter Resources

Ni elvis oscilloscope vi in labview

Hello,
I'm using NI ELVIS and Labview to drive a remote labratory over the internet.
For this reason, I'm using the ELVIS source VI's running in labview, and not the elvis panel.
When using the VI source code for the oscilloscope, the time division function does not work properly.
When adjusting the time division, the waveform is not squeezed or stretched as it normally would.
The waveform stays the same, and the time division lines move! And if I decrease the time division below a certain value, the display itself shrinks.
What should I do about this problem?
You can veiw the distance VI's here:
http://elvis-test.cecn.sabo.mtu.edu/oscope_test.html
I did not change the source code in any way, except for moving the "Help" buttons out of the veiw of the user. (These are useless for the remote users.)

Hello,
When you installed NI-ELVIS library under LabVIEW 8.2, those
VIs were complied for that version of
LabVIEW. You can always open a VI in a
newer version of LabVIEW but you can not open a VI in an older version of
LabVIEW.
Do you have both LabVIEW 7.1 and 8.2 installed on your
computer at the same time? Have you installed
the NI-ELVIS VIs for LabVIEW 7.1?
You may have installed the NI-ELVIS for LabVIEW 8.2 and not
for LabVIEW 7.1. Those VIs are probably
complied with LabVIEW 8.2 and LabVIEW 7.1 is unable to understand how to open or
run those VIs.
What errors are you getting when you try to use Firefox? Both LabVIEW 7.1 & 8.2 should be able to
display remote front panels in Firefox. Here
is a great KnowledgeBase that describes why you might be getting some plugin
errors with Firefox.
Respectfully,
Rob F
Test Engineer
Condition Measurements
National Instruments

How to read and write data from Excel to TestStand without using LabVIEW VIs

Hi,
How can I read in columns of data from Excel into a TestStand array and write columns of data to Excel from TestStand without using LabVIEW VIs?
I don't think the Property Loader custom step type in TestStand will work because the data I would like to read in from Excel is in a column that is thousands of rows long and the data has to be in the proper format to use the Property Loader to load in an array from Excel.
Thanks for your help.

That example does not use LabVIEW and it does about 40% of what you need to do by calling Excel through ActiveX. If you don't know how to use Excel through ActiveX then you'll need to brush up on that.
http://www.microsoft.com/en-us/download/details.aspx?id=16250
http://support.microsoft.com/kb/141759
http://support.microsoft.com/kb/302084
CTA, CLA, MTFBWY

Which is better for usb camera between VISA and imaqdx in labview 2010?

i have done a program for usb camera to acquire images with imaqdx.
now i want to know which is better between VISA and imaqdx in labview 2010?
i didn't study visa before
thans for help.

VISA is primarily used to communicate with instruments via GPIB/TCP-IP/Serial/USB. In order to use easily VISA with an instrument over USB the instrument must adhere to the USBTMC spec. A camera is not likely to have this. Otherwise you have to use USB RAW, and that requires detailed knowledge of the data that is transmitted by the instrument. Manufacturers rarely give this information out. Normally they will provide a DLL to communicate with the instrument.
Thus, in your case, VISA is not going to be an appropriate API to use for a USB camera.
Out of curiosity, what prompted this question?

Find names of all open windows including other applications besides LabView VIs

Hi All, I have researched this subject, i.e., to find names of all open windows including other applications besides LabView VIs, but found no solution. Could someone suggest a solution to this? Thanks.

Hi,
Certainly! The Windows API Function Utilities (32-bit) for LabVIEW includes set of LabVIEW libraries (llb) with VIs that make calls to the Windows Application Programming Interface (API) for managing and controlling windows (minimize, maximize, move, resize, rename, close, and so on) including task list with names of windows application running. The Readme.doc contains information on running these VIs.
Attached below is a zipped file with a VI that list the names of all opened windows.
Tunde
Message Edited by Tunde A on 04-18-2007 02:28 PM
Attachments:
List Windows Application LV8.0.zip ‏55 KB

Labview VIs for HP 35670A

The link to the labview VIs for the HP 35670A is no longer valid and the search for the same returns nothing. Does anyone have the Labview VIs for that instrument?
The last post was back in 2004(see below)
The instrument driver for the HP 35670A is only
supported under LabVIEW 6 and 7. You should upgrade to the latest
version of LabVIEW in order to use the HP 35670A driver or any of the
newer drivers that we release in the future.
The instrument
driver for the HP 35670A can be found on our web site at
http://zone.ni.com/idnet97.nsf/9b2b33e1993d877786256436006ec498/61f1c707c2f10906862568ab005fb9ff?Ope...
Solved!
Go to Solution.

Why don't you go to the Instrument Driver Network? I don't know what kind of search you did but the driver is certainly still available and can be found by using the search option there.

Communicating USB using Labview VISA

I have a USB RAW device that I am trying to communicate with using labview VISA. I have had success with setting up the driver and I am able to get information from the device such as serial number, etc. When I try to use the VISA read and write commands, I have no success getting the information I want. The commands are simple: R SP<CR><LF> is a read set point command. The only thing I do get back for every command I try, is a 2 byte message "01 60"hex.
If you have any suggestions, I would appreciate it, thanks!
[email protected]

Hello Chris, I do not receive any errors and yes, I am including the termination characters in the string.
Here is what I get when I use a USB port monitor when I send out this string.
Thanks!!
[94] URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER (SUCCESS/0x00000000) 20101119150318.131 (+0)
Pipe handle: 0x87696D6C
Transfer flags: 0x00000002 (USBD_SHORT_TRANSFER_OUT, USBD_SHORT_TRANSFER_OK)
Transfer buffer MDL: 0x88C47208
Transfer buffer length: 6
Bytes transferred
0x0000: 52 20 53 50 0D 0A (R SP.. )
[94] URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER (SUCCESS/0x00000000) 20101119150318.147 (+16)
IRP status: 0x00000000 (STATUS_SUCCESS)
Pipe handle: 0x87696D6C
Transfer flags: 0x00000002 (USBD_SHORT_TRANSFER_OUT, USBD_SHORT_TRANSFER_OK)
Transfer buffer MDL: 0x88C47208

How To: Reference LabVIEW VIs in Memory from a Compiled Application?

Hello all! This is my first post on these boards despite the fact that I have been doing LabVIEW for almost 8 years...so go easy on me!
Basically my issue is this: I want to write a compiled application for my team to use to help us have a standardized tool to push VI help tip information. So I created a nice front panel, gave it memory storage via XML to remember info you might want to not have to type over and over again. I also gave it some formatting options, etc. Overall, a nice tool to speed up a repetitive task.
However, it runs great as a VI, but compiled does not work at all and I am sure many of you can see where this is going. I have cobbled together some snippets of code found on these boards to collect a list of references and names of all the VIs in memory that are not currently running. Then I use a ring control to parse which VI I want to target and then push the parsed and formatted help tip to that VI. But the reality is apparently that LabVIEW and a compiled application do not share the same memory allocation, because they are separate application instances.
Is there ANY way around this?
I tried one thing that seemed to make sense, but so far has resulted in the same thing. I tried to do a type def call by reference with an asynchronous call and a wait on asynchronous call function to return the reference list. However, even though this bit of code is still a VI and NOT part of the compiled code, it still somehow picks up the application instance of the owning app, and therefore does not see any of the open VIs in memory that LabVIEW controls.
Any help would be immense, as I am going nuts trying to figure this out!
Info: LabVIEW 2012.f3
I am also attaching a screen cap of the block diagram of the VI that collects the references.
Thanks in advance!
South West Applied Technologies
Senior LabVIEW Developer

Well you run into a security limitation of VI server here. Many methods and properties are not possible to be accessed through a remote application instance. Any Application instance that is opened with an address is considered a remote instance. Basically if you leave the address open in the Open Application, LabVIEW shortcuts to the internal instance. If you connect some address even if it is "localhost", LabVIEW goes through the TCP/IP socket for any and all methods and proeprties and the application instance is considered a remote instance.
Open your floating help window, and place your cursor above your property. Notice the text in there: Remote Access disallowed: Yes.
The reason for this is, that if this method was available over remote connections, anyone with access to your network could connect to that LabVIEW instance and basically discover any and every VI you have currently loaded and even download them to their own computer. And this can not be fixed. This security is not possible to circumvent other than hacking into LabVIEW itself.
I guess this kills your entire idea. An executable can't connect to another executable or the LabVIEW development environment other than through a remote connection! That is due to strict process isolation rules in all modern OSes. The only possible workaround I could think is to create VIs for all remote access protected methods and properties, copying them to every LabVIEW installation you want to access with your shell (and that likely would have to be done through the network as the according methods in the VI server interface are also remote access protected) and then call those VIs through VI server.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Calling labview VIs from python in Linux

Hello.
I've spent some time searching for this but I haven't found exactly what I was hoping for.
I'm involved in a project that we're starting now and it involves creating a complex software architecture in order to control a robot. This software will need to perform multiple tasks such as interfacing with hardware (which LabView is perfect for) as well as planning and high performance image processing (which LabView isn't as great for).
I was hoping to be able to use a scripting language like python to manage high level stuff (planning, behavior, etc) by calling "subroutines" in other languages such as C++ for the high performance stuff and LabView VIs for the hardware interfacing. I would also like this to run on Linux.
I've found a lot of suggestions on how to call Python scripts from within LabView but this is not what I want. I want exactly the opposite, invoke VIs from Python. I found some information on how to do this on Windows (http://zone.ni.com/devzone/cda/tut/p/id/5719) but this article seems to assume that Windows is being used.
Does anybody have an idea on how to do this?

Unfortunately that's not an option. This is an interdisciplinary school project involving students from engineering (mechanical, electrical and more), computer science and more fields. Some of these students have gotten used to using Labview and this is the main reason I'm trying to accomplish this. I want to have the higher level architecture done in a scripting language such as python which will enable us to create modules in various different environments such as C++ for tasks requiring high performance (image processing for example), Labview for tasks that the people used to using that and even something running on the GPU if there's use for that. Python would make it easy to glue all these components together while maintaining an environment that would make it very easy to configure the whole software system in different ways.
I'd also prefer that this all run on Linux.
The more I look for this the more hopeless I get I'll find anything which is very frustrating. It's a bit hard to believe that Labview doesn't have "python bindings" for running the VIs from within python :-(

Logging data in a file using Labview VIs vs. Mathscript functions.

Hello,
I'm working on a data logger at 200 Hz frequency. I wanted to log the data to a file after eace sample received. When I used (fopen,fprintf,....) on Mathscript, the Labview started to log the data at a slower rate. I then used the Labview file VIs and it is working fine up till now.
My questions are as follows:
1- Are the file functions in the Mathscript slower than the Labview VIs ?
2- Is saving the data to a file after each sample is received a good idea or is there a better idea ? I just don't want to keep the data in the memory and after all the data is logged, I flush them to a file ... because, it seems that the PC will run out of memory.
Thank you,
Walid

wfarid wrote:
Hello,
I'm working on a data logger at 200 Hz frequency. I wanted to log the data to a file after eace sample received. When I used (fopen,fprintf,....) on Mathscript, the Labview started to log the data at a slower rate. I then used the Labview file VIs and it is working fine up till now.
My questions are as follows:
1- Are the file functions in the Mathscript slower than the Labview VIs ?
Yes. That's because you're going through another layer of software. Why were you trying to use MathScript to log data to file in the first place? Are you a Matlab "aficionado"?
2- Is saving the data to a file after each sample is received a good idea or is there a better idea ? I just don't want to keep the data in the memory and after all the data is logged, I flush them to a file ... because, it seems that the PC will run out of memory.
It doesn't make sense to save data after each sample. File I/O is an expensive operation in terms of time, and you have the operating system to deal with, so while you may be able to keep up the rate for some time, eventually it will be thrown off. You can do as suggested which is to wait until you have a certain amount and then write that to file, or you can set up a producer-consumer or master-slave architecture. Let one process/loop collect the data and put into a buffer, like a queue, and the other process/loop can stream it to disk at a more reasonable rate. You just have to make sure the buffer is large enough so that if the file I/O gets hung up you won't reach the buffer's limit.

Where can I find example LabVIEW VIs for the NI-USRP?

There are several sources of example LabVIEW VIs for the NI USRP:
We have established a NI Community "NI USRP Example LabVIEW VIs" where you can find example VIs from us (NI) and the community.
The NI-USRP driver installs a variety of example VIs to the to the following folder on your PC:
<LabVIEW Installation path>\examples\instr\niUSRP
where you should replace <LabVIEW Installation path> with the root folder of your local LabVIEW installation. For instance, my Windows 7 32-bit PC here has LabVIEW 2011 installed and the examples can be found here: C:\Program Files\National Instruments\LabVIEW 2011\examples\instr\niUSRP
I've installed the NI-USRP driver, but I can't seem to find the new examples in the LabVIEW Example Finder. Where are the example LabVIEW VIs installed by the NI-USRP driver?
Although the NI-USRP driver does indeed install examples, the current NI-USRP 1.1 release does not update the LabVIEW Example Finder with entries for these examples. To find the examples, you can navigate the Windows Start Menu to the following location:
Start Menu\Programs\National Instruments\NI-USRP\Examples
This Start Menu entry includes several Shortcuts that point to folders that are the home to example VIs.
Sam Shearman

Hello,
It looks like Agilent/HP makes the 8990A, but I was not able to find a driver for it that we or Agilent has written for this device.
Since I am not familiar with the 8990A, I cannot recommend which drivers might be similar, but you are pointed in the right direction. Agilent themselves might know more about which models use similar command sets so that you can modify a driver easily.
Hope this helps.
Scott B.
Applications Engineer
National Instruments

How to use Modal Parameter Extraction Labview VIs

I can't install Modal Parameter Extraction Labview VIs
http://zone.ni.com/devzone/cda/epd/p/id/6121
The installer says "NI Labview System Identification Toolkit 4.0 or 2009 must be installed before you can install NI Modal
Parameters Identification 1.1"
under Labview 2010(+the
LabVIEW Advanced Signal Processing Toolkit and LabVIEW System
Identification Toolkit).
Should I delete Labview 2010 and reinstall 2009??
解決済！
解決策の投稿を見る。

Hi KCMTM,
My name is Yusuke Minami, Applications Engineer, NI Japan.
I'm so sorry, but the "Modal Parameter Extraction Labview VIs" is not supported by LabVIEW 2010.
Since it will unlikely be updated for 2010, we have to ask you to install LabVIEW 2009 with the LabVIEW Advanced Signal Processing Toolkit and LabVIEW System Identification Toolkit in order to use the package.
Although I cannot guarantee, but I'll send an update request to the R&D.
I deeply apologize for the inconvenience.
日本ナショナルインスツルメンツ株式会社　技術部　巳波裕介
Yusuke Minami, Applications Engineering, National Instruments Japan
技術サポートウェブページ:　http://www.ni.com/support/ja
お問い合わせフリーダイヤル:　0120-527196

Some errors when calling LabVIEW VIs Interactively from DIAdem

Hi! I'm having some trouble using the "Calling LabVIEW VIs Interactively from DIAdem" found on:
http://zone.ni.com/devzone/conceptd.nsf/webmain/1A98AB48E35D913086256E23004E6A22
Following the troubleshooting section didn't resolve the issue. I
recompiled and built the exe (DIAdemLabVIEW.exe) for version 7.1.1,
which I am developing on. But still I got the same error message, after
a waiting for about a minute, on a diadem popup window:
Error in <MenuAdd...ctDo.vbs (row:1, column: 1)
Error in <addmenuentry.vbs (row:14, column: 3)
ActiveX component can't create object.: 'DIAdemLabWIEV.Application'
Using the llb's and exe's that was included with the installer worked
flawless, with the exception that LV 7.1.1 vi's didn't appear on the
popup window(DIAdemLabWiev.vi). So I tried to recompile and build for
the 7.1.1, with this result.
I'd be very grateful for fixes or solutions for this problem!
Regards
Roger Isaksson

Brad, thanks for the reply! Below is my (correct?) modification of your script. Have I got it right?
Dim lvapp, vi, viPath, paramName(1), paramVal(1)
Set lvapp = CreateObject("LabVIEW.Application")
viPath = "C:\TEMP\Test.exe"
Set vi = lvapp.GetVIReference(viPath)
vi.FPWinOpen = True
paramName(0) = "In Name"
paramVal(0) = "In Value"
paramName(1) = "Ut Name"
Call vi.Call(paramName, paramVal)
Call lvapp.Quit()
MsgBox "Parameter1 Value = " & paramVal(1)
I am not sure about the format of the <paramName(0) = "In Name">.
The control name is "In" and is a I32, the name for the indicator is
"Ut" and has the same storage type as the control.
Running the script gives an error in line 4, that is the <Set vi =
lvapp.GetVIReference(viPath)>. I'll attach the exe and the error
message.
I have another question regarding the relatively large amount of RAM
that diadem uses for export from my labview application to diadem. More
than 10 times the size of the data is required for exporting to diadem.
Since our application use relatively large files, actually up to
several GB's, this soon becomes problematic. See the attached picture
of the memory usage after exporting a 10MB segment (contains 42
channels of measurement data). Your help in these matters would be
appreciated!
Regards
Roger Isaksson, Damill AB
Message Edited by Roger Isaksson on 09-09-2005 10:22 AM
Message Edited by Roger Isaksson on 09-09-2005 10:22 AM
Attachments:
VBError.JPG ‏181 KB
Test1.vi ‏9 KB

ELVIS 1 AND ELVIS II LABVIEW VIs COMPATIBILITY

Similar Messages

Maybe you are looking for