Labview vi viewer

Dear All,
I have come back to this post after a year and a half and i don't have a LabVIEW on my machine right now.
The thing i am struggling with is that even though i do have some vi files from my previous work, i am not able to view them because of unavailability of LabVIEW.
Can anybody suggest me that which is the way i can view them, any labview vi viewer apart from LabVIEW itself?
And is it possible that i caan download a trial version of LabVIEW, if yes from which location on NI's site?
Looking for your prompt and positive reply.
Regards,
Nishant

This should do what you want
But
The LabVIEW Player is now obsolete. The LabVIEW
Player and the LabVIEW Player VI Creation Toolkit are no longer
available for download from the Drivers and Updates section of ni.com.
Message Edited by muks on 01-21-2010 04:26 PM

Similar Messages

Labview server view data remotely

Is there a way that I could set up LabVIEW as a server so I could view data when I'm not at the computer? Basically I have a program running, and it's constantly spitting out data to a .txt file, and I was wondering if there was any way that I could view the contents of that .txt file from another computer
Much thanks,
M.

You have a couple options:
1: You could write a VI to act as a server using the built-in TCP VIs such that a VI on the client PC could send requests for parts of that text file and the "server" could respond with that data. The TCP VIs are located in your functions palette at Data Communications > Protocols. Also take a look at the shipping TCP examples at Help > Example Finder... > Networking > TCP & UDP
2: If you need a way to display the data, then remote front panels may be the better route. You can write a VI such that the front panel can be viewed and controlled from a web browser on another machine. This way you could update the front panel with the requested data. This is not included in Base Development of LabVIEW but can be purchased separately.
Developing Remote Front Panel LabVIEW Applications
--Michelle
Instrument Control R&D
National Instruments
Instrument Control
Machine Vision

Can i use webserver other than that is provided by LabVIEW to view remote panels?

How to view remote panels using webserver (not inbuilt of labVIEW)? Is it possible to communicate with other webserver? if yes which VIs to be used?

What do you mean "use another web server"?
The remote panel publishing is an integral part of LV. I don't think it can just be detached.
You can write your own code which will grab the image of a front panel, send it to another VI and have that other VI capture the mouse clicks and send them back to the original VI which will then simulate them. You can also use something like VNC, PCAnywhere or XP's terminal services to remotely connect to the computer (or LabVNC to connect directly to a VI).
Why not use the built in web server?
Try to take over the world!

Labview viewer

I'm wondering if there is such a thing as a labview vi viewer utility? I am a software engineer in the role of software support to the factory. Labview teststand is used to run a variety of tests on our product. I don't need to develop tests, but I would like to know what exactly the tests are doing. It would be very nice if I could look at the vi's developed by our test engineers to see exactly what they are doing. But I don't need a full blown labview installation on my machine.

My idea would not be that great anyway, because we cannot see hidden cases etc. but I am wondering....
I was thinking along the lines of creating a built application that can display BD images of a selected VI in a picture indicator, but unforunately it does not seem to work once I make an application out of it.
According to the LabVIEW 8.0 help, the method "Block Diagram:Get Image Scaled Method" is supposed to work in a built application:
QUOTE: Available in Run-Time Engine and Real-Time Operating System:
Yes (Read/Write)
But all I get are blanks once the application is built.
(In pre-8.0 versions, the help correclty indicated that this method is not available in the runtime!)
So, which one is it:
I am not smart enough to use this and I am doing something wrong.
The LabVIEW 8.0 help is wrong (I am confused by the "read/write" anyway... what would writing this method possibly do???).
something else?
LabVIEW Champion . Do more with less code and in less time .
Attachments:
ShowDiagramLV8.vi ‏18 KB

Issues when using a Pixelink camera with LabView 9.0

In my lab, we have a program for video acquisition using LabView and the low level camera functions for Pixelink cameras. We run into some problems trying to run this program and other demo gui programs that came with the Pixelink SDK. In our data acquisition program, we have problems with our image coming out all scrambled. We use the low level functions to obtain a frame from the camera in the from of a vector. We then reshape the vector into an array and then send the array to a vi that turns it into an image. When we try to view this image using the standard Labview image viewer, the image comes out all scrambled if the zoom factor is not set to .5 on the image viewer. The full resolution of the image is supposed to be a 1024x1280 image which when we use the Capture OEM software for the camera provided by Pixelink we can see. The image that we can see through LabView when we have the correct zoom factor seems to be only the top left quarter of what the entire image is supposed to be. We also encounter strange problems when we attempt to use the demo programs for labview 8.6 that are provided with the SDK. When trying to run the simpleGUI.vi, for example, the program connects to the camera just fine. After you hit play to view an image, the problems start. The program will play the video for a few seconds until it just freezes up and quits responding. Labview must be exited and restarted in order for the camera to connect again. I am not sure if it makes a difference that we are running labview 9.0 on our computers or not. Any help you have on these issues would be of great help. Attached are pictures of the scrambled/unscrambled image and of the part of our block diagram for camera control.
Attachments:
Incorrectimage.jpg ‏126 KB
Errorexplanation.jpg ‏543 KB
correct image.jpg ‏22 KB

IMAQdx is the driver that National Instruments provides to interface Firewire, GigE and USB cameras (Directshow compliant USB). This is a licensed driver, so if you don't currently have it, then testing in MAX is not an option.
So if I understand correctly, you have the Pixelink software which works fine, but you have Pixelink VI's that are used in LabVIEW, but those do not work correctly? That to me seems like a driver issue, which I'm not sure how much I can help with since it is not our driver.
Do you know what dll's the Pixel link VIs are calling into? Are they Pixelink dlls? If so, I would suggest speaking with the manufacturer or perhaps on of our other users has worked with Pixelink before.
Sorry I can't be much more helpful.
Tejinder Gill
National Instruments
Applications Engineer
Visit ni.com/gettingstarted for step-by-step help in setting up your system.

Labview-Octave/GNUPlot Inegration

Hello, forum! I'm working on a little project to take images I've acquired using some LabVIEW code and automatically import them into GNU Octave (similar to MATLAB) and turn them into a 3D image "stack" an added bonus would bethe ability to return the stack to LabVIEW and view it in the front panel.
I know that it's possible to interact with Matlab using ActiveX, but as far as I understand it, that feature's missing from Octave, so what I've been working with so far is invoking Octave from the command line (using Sys Exec) end sending it commands directly. My code is attached; OctaveStacker.vi is the main. For some situations the interface works perfectly; for example in simple cases of affecting variables, arithmetic and so forth.
If you use the text in "script.m" instead of the output from the subVI and remove the semi-colons (verbose), you can see the results appearing as expected in the output box on the front panel. However, when the script gets to the "plot" command, which should cause Octave to open GNUPlot and plot x against y in a new figure window, nothing happens. Presumably the image commands in my other script would have similar problems. If I run my main VI using the two example pictures in the archive, however, I get no response at all except being dumped back at the working directory Windows shell in the output box. If anyone has any expertise in this area, I'd be much obliged for any help.
LabVIEW 2013, Windows 7
He who asks the question is a fool for five minutes; he who does not ask the question remains a fool forever.
Attachments:
Octave Code.zip ‏464 KB

Hi MattA1,
I've read through your VI and I'm currently downloading the Windows version of Octave so that I'll be able to play around with your code; however it may take some time to get up to speed because the String concatenation VIs are constructed in a way that references file locations on your computer.
For code modularity, it's great to make use of the Path based functions to reference to files stored in a local directory to the VI. By using the Current VI's Path VI in conjunction with the Strip Path and Build Path VIs, you'd be able to reference VIs files regardless of the computer you're connected to. This would be good for if you ever want to transport your VIs to other computers; it'd be especially useful in this debugging case!
Firstly, I believe that issues may be occuring because of the striking difference between "script.m" and "OctaveStacker.m"; mostly because OctaveStacker contains function calls which combine the functionality of the Windows Command Prompt and calculation functions, which may be causing some of the confusion. It'd be interesting to see how the .m file reacts when they're missing and called via LabVIEW.
However, for now, I just need to change this VI so that it'll match my computer. But I'd suggest that it may be worth trying removing the directory transitions and just using the folders locally and seeing whether this makes a difference. In terms of the String concatenation SubVIs you use such as the OctaveStackingScript VI, I recommend ensuring that the Strings you build are compatible in both of these instances when calling different kinds of Scripts.
Do I have a good idea of your problem? For now I'll keep working on trying to getting all of the references working on my computer. (Not to mention installing Octave!)
Regards,
Alex Thomas, University of Manchester School of EEE LabVIEW Ambassador (CLAD)

Comunication between opc server and a generic labview application

I'm developing a LabView application that hanldes data aquired with dedicated hardware. The system (PC+appl.+DAC) has to be iterfaced with remote PC that can see only an OPC server. Wich server have i install?
Does exist a similar application?

As far as I am aware, LabVIEW Base/FDS/PDS can only act as an OPC client i.e. they can receive information from other OPC servers. If you are reading information from an OPC server into LabVIEW, the easiest method is to use DataSocket as this considerably simplifies the communication process. Examples of using DataSocket within LabVIEW to view OPC data items are provided with LabVIEW.
In order for LabVIEW to act as an OPC server i.e. LabVIEW acquires the data, and the publishes this data such that other OPC-aware applications can access the data, you will need to use LabVIEW DSC (Datalogging & Supervisory Control).
LabVIEW DSC will allow you to generate a "tag" and assign this to the data that you acquire/process. This tag can then be seen by all OPC cl
ients (either local to your computer or across a network).
An alternative that you might want to consider would be to use DDE - this will all depend on the capabilities of the software you are working with. DDE capability is available in LabVIEW without DSC and will allow you to pass information between a DDE client/server. OPC has its origins with DDE so if this other piece of software that you refer to is a SCADA-type package, you may have some success here.
Jeremy

Selecting VI Server.Strictly Typed VIs in Class Browser crashes LabView

Hi!
My LabView 8.0 Pro on WinXP crashes in the following way:
0. Opening Blank VI.
1. Placing VI ref num on the front panel.
2. Going to "Select VI Server Class -> Strictly Typed VIs -> Browse..."
3. Loading any VI (say, "myVI").
4. Then going to menu: View -> Class Browser
5. Selecting Object Library: VI Server.
6. Selecting Class: Strictly Typed VIs - "myVI" icon.
Result: LabView crashes saying that there's error and application will be closed.
Besides there's a little question:
Did I get it right that if I change myVI connector layout or pins it's not refreshed in my
VI ref num and I have to load VI again (see step 2)?
Thanks in advance for any help.
Rashid.Message Edited by Rashid on 02-22-2006 11:17 AM

Hello,
I have reproduced this, but I think the menu navigation you indicated in step 2 has a mistake. I reproduce it with the following steps, and have filed a corrective action request to R&D on the matter:
0. Open a Blank VI.
1. Place a VI Refnum on the front panel.
2. Right-click on the VI Refnum and choose: Select VI Server Class -> Browse...
3. Select any VI (say MyVI.vi).
4. In LabVIEW click: View -> Class Browser
5. Select Object Library: VI Server.
6. Select Class: Strictly Typed VIs -> MyVI.vi connector pane icon.
Sorry for any inconvenience - the problem should be addressed in a future version of LabVIEW.
For your question, "Did I get it right that if I change myVI connector layout or pins it's not refreshed in my VI ref num and I have to load VI again (see step 2)?" - yes, I see the same behavior - you should save the VI and then select it again in the VI Refnum.
Best Regards,
JLS
Best,
JLS
Sixclear

How can I sanitize Labview code?

It's not classified, but it needs to be screened to get it out of the building I work in. Security is concerned about hidden information when you can't read something as ascii.
Solved!
Go to Solution.

PhillipBrooks wrote:
Probably not viable, but maybe you can you save your individual VIs as snippets?
They would be PNG files that could be scanned for what, I don't know.
They wouldn't need LabVIEW to 'view' the code.
I'd be curious if that would pass muster.
One of my thoughts would be if you were able to carry out pictures of your LabVIEW code. (Hardcopy since it seems that they are afraid of any electronic storage devices leaving the facility.) At least then you'd have enough information to recreate you VI's like you said.
A snippet would be appear to be a picture. But it is actually a vehicle for carrying out other information behind it. There is more info in that .png file than just a picture. It contains all the code to be able to recreate the VI. Well if a .png file on disk or USB key can do that, then what is stopping someone from figuring out how to hide sensitive secrets in the metadata of that .png file just like the LabVIEW code is buried in it?

Leap Motion + LabVIEW: Error

Hello Community,
I recently picked up a Leap Motion controller, and I would love to get it working with LabVIEW and do some cool stuff.
I went through the following intructions on how to setup and get started.
https://decibel.ni.com/content/groups/leap-motion-controller-toolkit-for-labview?view=documents
When I run Simple Controller.vi, I get the follow error (attached)
I am really not sure what is the issue here, if someone can let me know what is happening and possible suggestions?
Thanks,
Daniel
Attachments:
Capture.JPG ‏58 KB

I don't think any amount of help will allow you to do cool stuff with a Leap Motion
but you can try re-installing .NET 3.5. I'm not sure what the bad image might be, but it sounds like something is corrupt, either in .NET, or the Leap libraries. This is all pretty new right now, so there are bound to be issues. You should probably post in the community page for Leap Motion https://decibel.ni.com/content/groups/leap-motion-controller-toolkit-for-labview
Machine Vision, Robotics, Embedded Systems, Surveillance
www.movimed.com - Custom Imaging Solutions

Cant use DAQ from MAX in LABView

I am new to LABView and NI-DAQ and have some problems getting it going. I have LABView 6.1 and NI-DAQ 6.9.2 installed on a Windows XP operating system. The DAQ card is an AT-MIO-16E series,is installed and is visible in MAX under the "Devices and Interfaces" section. It tests fine in MAX using the channel test. However, I have no option in LABView to view the DAQ channel, and under the "Tools" menu there is no option to select anything regarding DAQ. Upon starting LABView, the "DAQ Solutions" is also greyed out and not selectable. I have uninstalled and re-installed the entire package a few times already! Can anyone please give me some advise to try and rectify this problem?

Hello,
if i got that right, you want to do a data acquisition with a LabView program.
Basicly there are examples coming with LabView to get started with DAQ programming. You find them under the menu:
"Help -> Find Examples"
In this example browser you can select:
"Hardware Input and Output -> DAQ -> Getting Started"
or other examples concerning hardware I/O
You can also give aliases to channels you want to read.
This is done in the Measurement and Automation explorer by creating virtual channels.
Here a link to how it is done:
Create a virtual channel
i hope this gives you a starting point
regards
Robert Halas
Na
tional Instruments

Getting access to ActiveX Enums

I posted an earlier question about being able to access the Excel VBA Help in LabVIEW to view the help for an Excel ActiveX Property or Methods node. One of my PCs (running Win XP) could access the help, another (running Windows 7) could not.
This is a related question that could be part of the same problem. More than a year ago, I wrote a VI that used the _Workbook SaveAs method to save an Excel file that I created with LabVIEW. To get it to save the file in the proper format, I wired an Enum whose value was "xlWorkbookNormal" to the "FileFormat" slot in the Method. [The enum in question takes on a range of values, from xlAddin,xlAddin8 to xlOpenDocumentSpreadsheet]. If I leave this unwired, I can still save the file, it "looks" OK when Excel opens it, but Excel complains that it is "not in an expected format", or something like that -- you can fix it by doing an explicit SaveAs and specifying the 97-2003 format.
My problem is I no longer remember how I got this enum. I presume that on my XP machine, I right-clicked something and the enum popped up. However, I'm now coding on my Windows 7 PC and can't figure out how to do this. [I got my new program to work by finding my older VI and simply copying the enum constant into my new routine].
So my (visual) basic question is, when expanding an ActiveX property or method in LabVIEW that takes a variant which corresponds to an Office enum, how do you get the right enum (let alone figure out which of its various instances to use)?

Hi Bob,
The only way I know to create the enum is to use the FileFormat property node. This property node returns the file format of an excel workbook and you can create an enum control from this output. I have attached a small example to illustrate this.
Thanks,
Paul B.
Motion Control R&D
Attachments:
Bob Example.vi ‏14 KB

Error #3, "memory.cpp", line 865(V6.0) 876(V6.0.2)

I used a VI one day with no problems, and the next I got this message - "Error #3, "memory.cpp", line 865" I did not even close the VI or modify it an anyway.
I was first running Labview V6.0 and tried upgrading to V6.0.2 but the error continued (now on line 876). I also tried recompiling and backup copies of the VI and SubVIs, which did not work either. A suggested fix is to delete "dir.mnu", which likewise did nothing.
To me it looks like the problem rests in the Labview "Copy" command, which I use to copy a file to another directory, because when I delete it it works fine again.
Any suggestions would be greatly appreciated!

Hello,
It seems that while copying your file, memory is filling up too quickly for LabVIEW to clean it up and it's crashing LabVIEW. View the memory usage in the Task Manager to confirm this.
LabVIEW Internal Errors (Failure in XXX.c / XXX.cpp at line YYY)
If the Copy function is not the cause of the error, about 95% of the time, the next step is to look for DLL nodes or CIN nodes. The likely culprit is that a string or array is being handed to the C code, which either overwrites memory, or leaves the array/string data structure to an inconsistent state leading LV to overwrite memory. Anyway, this is a very common cause.
If you eliminate that possib
ility, the remainder are usually some sort of corruption saved in the VI, but normally those will not even load.
To simplify it before submitting it to support, please try executing individual subVIs and see if the problem is limited to a particular VI or a smaller set of VIs.
Zvezdana S.

Advanced signal processing toolkit for Version 8.5

Hi all,
Please guys help me out. I am looking for the advanced signal processing toolkit for labview 8.5 (not an evaluation ) .
any help would be appreciated
Bill David

Dear Norbert_B.
Thanks a lot for your help . But I just cannot find a way to tell you this . I have just installed a newer version of labview ( LAB-VIEW 2009) because I got it from a friend and it has the Advance Signal Processing Toolkit . but have no idea where do i get the Digital Filter design toolkit as well as the biomedical toolkit that suits this version of software.
In another word I am just suffering with it . I have an application to build and it needs the digital filter toolkit and the biomedical toolkit . I know that's alot to request ..but I am trying to be honest with you .
your help was already appreciated.............m loosing my mind
Bill David
Bill David

OOP usage in UI

I'm an old hand at LabVIEW in general, and using Object Pascal, C++, etc (other object-oriented languages), but I'm trying to use LabVIEW objects and not having any luck.
I understand the trivial examples, about graphical shapes, and such, but I see no example making a real use of them.
Consider this:
I have a SCALER, which is a cluster of {A,B,C,D,E,FullScale, all numbers}. I'm thinking of making that a class, so I do that.
I have a CHANNEL, which has a NAME, an ACTIVE switch, and a SCALER.
If I put the SCALER.lvclass into the private data for CHANNEL, then I get a icon of a box. It's pretty and all, but not useful for a user interface.
If I put the SCALER.ctl into the private data for CHANNEL, then I get the cluster I want to see. But it's not an object. If I want to use the SCALER object methods on this data, the I have to create an object and set it to this value, don't I?
That's hardly a sensible approach.
I have a MODULE, which has a MODULE TYPE, some module-level stuff, and an array of CHANNELs.
Now, for reasons I don't understand, If I put a CHANNEL.ctl -OR- a CHANNEL.lvclass into the array in MODULE's private data, I get an array of the box icons. That's hardly useful for UI.
Are LabVIEW objects just not suitable for UI purposes like this?
Or is there something else I've missed?
Steve Bird
Culverson Software - Elegant software that is a pleasure to use.
Culverson.com
Blog for (mostly LabVIEW) programmers: Tips And Tricks

Hmmm... Where to start...
"...the initial reasons for xcontrols was to allow the programmer to create a visual representation of a class."
Really? I have never heard that --- and it certainly isn't in any of NI's description of XControls. XControls are for creating user interfaces, plain and simple. Of course using them as a way of providing class-specific interfaces, while I have never seen it done, is a neat idea.
"...LabVIEW so tightly couples UI elements to datatypes that we become blinded to the separation of the two."
What are you talking about? This doesn't make any sense on its face. A strip chart to the user is a graph with all kinds of controls and properties. To the code it is a scalar numeric indicator. Or you are saying that I should be able to wire anything up to a strip chart and let LV decide what I want? No thank you! We already have the dynamic data type and it causes problems enough.
"...it is pretty much impossible to actually implement MVC in LabVIEW."
Again, what in the world are you tralking about? MVC is a technique of understanding and defining the relationships between the various aspects of your application. A technique, by thte way, that is language independent. I first ran into the terminology in the discussion of website. Let me guess, you are one of those people that think LV wasn't object-oriented before LVOOP was introduced, right?
"Using purely LabVIEW your view is always coupled to procedural code."
Well, duh... The point of the View (the V part of MVC) is to "request information from the model that it uses to generate an output representation to the user". Now how is it to do that without procedural code? Without code how do you formulate or send a request? How do you process the response to that request? How do you generate an output representation?
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

Labview vi viewer

Similar Messages

Maybe you are looking for