I'm trying to run a program written by someone else in LabVIEW. The program records voltage. However it won't open because it is missing subVIs.
Initially I thought that only one was missing and the rest weren't working becuase they were attached to it but after someone on this forum kindly found it for me the rest of the VIs still won't work so I think I need to download them again. However there are too many off them to get separately, also I tried googling them to no avail.
The subVIs are : Magnet Id, Hardware check, Plot Data and Print, Make Plot Lables, Plot it, Relabel It, Write File header, Record Analog Info, Fix Column Heading, Make Igor Label etc etc (this is not a complete list).
I feel that I should download a DAQ from The National Instruments Website but I am not sure which one. I am using 64 bit LabVIEW 2010 on Windows. Can someone please help me pick out the correct driver?
Thanks!
Just going from memory, those aren't NI VIs that I recognize, especially if the misspellings are in the original.
What hardware is this interfacing with?
You should still be able to open the main VI. It will not compile or run, since the subVIs are missing, but you should be able to open it and maybe get some clues about what it's doing.
The SubVIs all appear to be in the llb file so they should be available. I'm not sure how you can access the subVIs directly from the llb file so you may want to convert this to a project folder (this is the new way of creating libraries since version 8 I think). There are some pages on the NI website that may help, try Converting an LLB to a Project Library and then add this Project Library to your project.
From what I can see the VIs make use of the VISA drivers to communicate with the individual instruments so you should make sure you have this installed. You don't mention what version of LabVIEW 2010 you have but I think they should be provided even the Basic version, I know they are provided with the Professional Development System version.
Related
I have a file containing a LabView program and need to understand what it does. Of course it can not be executed without LabView. But is it possible to read a LabView program without Labview?
But is it possible to read a LabView program without Labview?
I presume you're asking, "Can I open a *.vi file and look at its source code (which is called the "Block Diagram"), without using LabVIEW?"
If that's your question then the answer is "No", not directly. Officially, you need LabVIEW to read, edit, and execute a *.vi file.
Third party support to view VIs without LabVIEW
You can get a third party to convert the VI for you:
If you know someone else who has LabVIEW, you can ask them to open the VI for you and save the Block Diagram as a picture file for you (preferable in the form of a Snippet).
There are unofficial 3rd-party tools (like the one in #mefistotelis's answer) which can convert VIs without LabVIEW.
Installing LabVIEW without purchasing
(NOTE: In April 2020, LabVIEW Community Edition was released. It is free for home use.)
If you are willing to download and install LabVIEW, you can open the VI file. This link lets you select the Community Edition for home use or the 7-day evaluation for commercial/academic use.
The parser I made can read VIs, and convert most of the content to XML (including Block Diagram, Front Panel and type definitions used for connectors):
https://github.com/mefistotelis/pylabview
It is open-source, and in no way related to NI.
The XML form you get isn't really easy to read, but with the data exported to XML, it should be possible to write a tool which parses it and displays as a diagram, or at least creates an SVG.
As #JKSH already stated the answer is "No".
If you think a Labview Viewer could be useful give a Kudo to this Labview Idea and try to convince National Instruments to provide one.
In the comments to the idea there's a link to a software, VIpreVIEW - Interactive VI preview, making a Flash-enabled HTML page for viewing the code (I've never tried it).
I have an Yes answer to this question. There is an option to export the block diagram as snippets as said by #JKSH.
I have created a POC - Export VI as images.vi here in github which can help you to export the VI you want to read as images. Then you can easily open the images in any image viewer and read that LabVIEW code. You need to feed it this POC with VI you want to export and image saving locations for the front Panel and the block diagram.
If the person who has given you the code has LabVIEW installed with his PC, s/he can export the code as images easily using this POC.
Ref: https://github.com/digiajay/ExportLabVIEWfilesAsImages/tree/master/POC
Thanks,
Ajay.
I purchased two Wacom stu-300 signature tabs. I had the ooption of buying the significant SDK/software, but I wanted to interact witht he pads myself. From research I see that I basically need access to wintab32.dll. I cant't find it anywhere? Can someone point me in the right direction?
I am looking to just capture a basic signature. No fancy graphics. Just cap signature. I have tried a few sample apps, but most of them complain about wintab being missing. Wacom seems to explicitly declare that the stu-300 is to be used as part of a compelte solution, and they don;t provide any driver or software for it. The signature pad is installed tho, and shows in devices. Does this tab work / fall into the caterogy of a "tablet" pc functionality?
I would really appreciate some help, maybe a sample app? I would prefer vb.net.
Thanks
It was last maintained by Wacom. The DLL is hidden inside their driver installs. I found it as part of the PenTablet driver version 5.2.5-5a, available at http://www.wacom.com/en/customercare/Drivers.aspx?model=Bamboo&os=
Rather than installing the entire driver, you can extract wintab32.dll from the self-extracting installer.
The stu-300 does not have wintab, Wacom has a set of SDK for the stu tablets, you can request it from https://ssl.wacom.eu/signature.wacom.eu/index.php?page_id=18
I’m new to Qt Quick. So, This might sound like a dumb question. But I’m struggling with this.
I want to develop a complete UI for my embedded system using Qt Quick. So, I need QML to run my system.
Now, which library to install on my target embedded linux system.
I ‘ve seen this page : http://qt-project.org/downloads but it shows the library with 228MB! which will float my system size abnormally. I expect my system to be around 50MB only! I think this comes with lot of things which I may not want.
I may use qml, for internet browsing purpose parts of webkit (webkit module for qtquick)
xml.
So, Can you please help me which to install? & how??
Thanks & Regards
inblueswithu
Check http://qt-project.org/doc/qt-4.8/qt-embedded-install.html for a initial documentation.
Please note, that this will install everything, meaning all Qt modules. You might be able to strip some of them away, also you might now need all image plugins. However, as a start this should work for you.
I need to build a fairly simple app but it needs to work on both PC and Mac.
It also needs to be redistributable on a disc or usb drive as a standalone desktop app.
Initially I thought AIR would be perfect for this (it ticks all the API requirements), but the difficulty is making it distributable, as the app would require the AIR runtime to be installed to run.
I came across Shu Player as an option as it seems to be able to package the AIR runtime with the app and do a (silent?) install.
However this seems to break the T&C from Adobe (as outlined here) so I'm not sure about the legality.
Another option could be Zinc but I haven't tested it so I'm not sure how well it'll fit the bill.
What would you recommend or suggest I check out?
Any suggestion much appreciated
EDIT:
There's a few more discussions on mono usage (though no real conclusion):
Here and Here
EDIT2:
Titanium could also fit the bill maybe, will check it out.
Any more comments from anyone?
EDIT3 (one year on): It's actually been almost a year since I posted that question but it seems some people still come across it every now and then, and even contribute an answer, even a year later.
Thought I'd update the question a bit. I did not get around to try the tcl/tk option at the end, time constraint and the uncertainty of the compatibility to different os versions led me to discard that as an option.
I did try Titanium for a bit but though the first impressions were ok, they really are pushing the mobile platform more than anything, and imho, the desktop implementation suffers a bit from that lack of attention. There are also some report of problems with some visual studio runtime on some OSs (can't remember the details now though).. So discarded that too.
I ended up going with XULRunner. The two major appeals were:
Firefox seems to work out of the box on most OS version, so I took it as good faith that a XULRunner app would likely be compatible with most system. Saved me a lot of testing and it turned out that it did run really well on all platforms, there hasn't been a single report of not being able to start the app
It's Javascript baby! Language learning curve was minimal. The main thing to work out is what the additional xpcom interfaces are and how to query them.
On the down side:
I thought troubleshooting errors was a sometimes difficult task, the venkman debugger is kinda clunky, ended up using the console more than anything.
The sqlite interface is a great asset for a desktop app but I often struggled to find relevant error infos when something didn't work - maybe i was doing it wrong.
It took a little while to work out how to package the app as a standalone app for both PC and Mac. The final approach was to have a "shell" mac app and a shell pc app and a couple of "compile" script that would copy the shells and add the custom source code onto it in the correct location.
One last potential issue for some, due to the nature of xulrunner apps, your source code will be deployed with the app, you can use obfuscation if you want but that's something to keep in mind if you want to protect your intellectual property
All in all, great platform for a cross-platform app. I'd highly recommend it.
Tcl/Tk has one of the best packaging solutions out there. You can easily wrap a cross-platform application (implemented in a fully working virtual filesystem) with a platform-specific binary to get a single file executable for just about any modern desktop system. Search google for the terms starkit, starpack and tclkit. Such wrapped binaries are tiny in comparison to many executables these days.
Many deride Tk as being "old" or "immature" but it's one of the oldest, most stable toolkits out there. It uses native widgets when such widgets exist.
One significant drawback of Tcl/Tk, however, is that it lacks any sort of printing support. If your application needs to print you'll have to be a bit creative. There are platform-specific solutions, and the ability to generate postscript documents, and libraries to create pdfs, but it takes a little extra effort.
Java is probably your best bet, although not all Windows PCs will necessarily have Java (most should). JavaFX is new enough you can't count on it - you'll probably find a lot of machines running Java 1.5 or (shudder) 1.4. I believe recent Mac OS still ships with 1.5 (latest version may have changed to 1.6).
Consider JavaFX
It would run everywhere with a modern JRE ..!
AIR could be an option, but only if you don't mind distributing two different files (the offline runtime installer and your app), and expecting the user to run one and then the other. You do have to submit an online form at Adobe's site saying you agree to distribute the offline installer as-is, rather than digging out individual DLLs or whatever, before they give you the installer.
Unfortunately there's currently no way to get both an AIR app and the runtime to install from one file though. I'm not sure what the deal with Shu is, or whether it's doing anything that isn't kosher.
i would recommended zink. it has all the functionalities you require for desktop. however, the las time i used it it was a bit glitchy.
i was hung up by trying to write a 6M file to the disk. thought it trough and changed the code to write 512K chunks at a time (3min work, fast).
probably it still has some little annoying glitches like making you think on root lvl but the ease of use and the features are just way too sweet to ignore.
The stage in the Flash CS4 Authoring Enviroment is a running SWF. That what makes thing like the 3D and Bone Tools to work in the IDE.
Is it possible to access that swf ? I suspect the immediate answer would be no because that would raise some security issues maybe and cause lots of developers to crash the IDE every 5 minutes :).
That said I don't expect this to be a straight forward process, but I guess there should be a way to access that.
Any thoughts ?
I can only tell you how components work on the stage, where we've attempted the type of access you talk about.
I suspect that at their core, the 3d and bone tools are implemented using component-like tech to display the "live" stage instance. In general this would involve a compiled instance of a live preview swf that is placed on the stage. It is misleading to think of the stage as a single player. Each component preview runs in its own sandbox that, as far as I can tell, has no means of communication with other component previews on the IDE stage. There is no common storage location.
Of course, if you were in charge of the preview swf (as with the case of a component), you could try LocalConnection to chat, but the previews you want to penetrate are closed. I suspect if you dig hard enough, you'd find the bone/3d preview hidden in the installation folders (perhaps in a swc.. ik.swc looks interesting) and might be able to hack about at it with a decompiler, but straight out the box, I'm not sure there's a solution to what you ask.