07-21-2006 08:39 AM
You probably have several options, depending on the type of license deployed at your location. What version of LabVIEW do you have?
http://www.ni.com/license/licensing_options.htm
For example, "A named-user license is tied to an individual user who can install the software on up to 3 business computers at any given time, in addition to a single home computer. "
http://digital.ni.com/express.nsf/bycode/ex4fjs
04-30-2007 12:21 PM
This is a follow-up more than a year after the original message, just as an FYI to anyone else doing what I tried to do.
I'm a scientific technical writer (independent consultant) working on a project to document testing some time after the event. The environment is regulated (FDA), relating to medical devices.
Among the support items to be submitted along with the documentation is a LabVIEW .vi file, and as is often the case, I am required to document the file(s) being supplied.
In this case, the test materials and equipment have long since been dismantled or re-assigned and are no longer available. At the time, no-one thought to try to document the .vi other than as rather poor screenshots (familiarity with LabVIEW is moderate among the engineers, but familiarity with documentation requirements and the planning required is low, so no-one thought to try to produce even the HTML version of a report, as was suggested here. And just as an aside, persuading an engineer who is trying to get a job done ASAP that s/he should document in detail what they are doing is a HUGE no-no, as any technical writer will tell you :)).
I went in search of some kind of viewer in the hope that this would enable me to reproduce the contents of the .vi file, and found references here to the LabVIEW Player, now since defunct, which is a great shame. A viewer capable of re-creating (but not necessarily executing) the screen view of the original .vi - similar to the way that Adobe Reader lets someone without Adobe Acrobat view PDFs (and where there are many excellent alternatives to Adobe's Viewer, too) is a must-have, no two ways about it.
I have tried, with the help of an engineer who was not involved in the original testing, to load the .vi into LabVIEW and the results are, predictably, not very useful, since the equipment and materials are not available - lots of big question marks where LabVIEW can't find and/or connect to equipment.
I would suggest that even a .jpg image, embedded in the binary .vi, showing the working image that would have been seen when the .vi was originally created/saved, would be a very helpful addition for people like me. If access to such an image was possible using a simple viewer application, it would resolve documentation problems for those who would otherwise have to learn a lesson the hard way.
Best,
Peter
04-30-2007 01:26 PM
In this case, there is nothing you could do. The question marks are not missing hardware, but missing software. Specifically, missing functions.
LabVIEW VIs are already far from the most compact form of source code available and adding redundant data to them would only make them bigger. Also, a simple image is not enough to capture a VI, because a VI has some 3D data (structures which have multiple frames which occupy the same space).
Basically, you need to find and use the software modules missing when you open the VI and then the code will look fine when you open it in LV.
04-30-2007 02:34 PM
Interesting... Thanks for the feedback.
To the best of my knowledge, we have everything except the previously attached hardware - an exact copy of the folders and contents of the LabVIEW project as it was left on the PC in use at the time and untouched since then. If modules really are missing, that may cause even more problems. Oh, well. Not my problem...
Best,
Peter
04-30-2007 03:10 PM
04-30-2007 03:26 PM
To the best of my knowledge (limited, because I'm going by the assurances of others), the PC has not been changed in the interim, and the project folder is as it was at the time of testing, with all required modules contained in subfolders.
As far as I know, the only aspect that has changed is that the test equipment in use at the time, and the materials under test, are not present. Other projects have been installed on the same machine in the interim but no changes have been made to the project in question.
If in the future I find that is not the case, I'll post details (if possible) or at least post that changes were made after all.
I'm hampered by a lack of knowledge of LabVIEW. I had thought that we could have used LabVNC to view the .vi, but the restrictions on access to the PC (placed inside a restricted access lab within a restricted access building) almost certainly prevent us from installing any server app on the PC that would allow anyone outside the lab to access a .vi. Regulated environment rules, I guess.
I'll keep my options open if I can, but it looks as though we may have to submit documentation based on the poor screenshots and a description of the situation as we found it, in as much detail as we can verify. That happens all too often in regulated environments IME, sadly.
But thanks for your attempts to help - all assistance gratefully received, as always.
Best,
Peter
05-07-2007 04:40 AM
05-07-2007 10:49 AM
Or easier, enable context help (ctrl+h) and hover over the various missing subVIs. You'll get their name in the context help window. 🙂
wiebe@CARYA wrote:
If you dubble click a question mask vi (the missing vi), you get a pop up with it's name.
05-07-2007 11:40 AM
05-07-2007 01:10 PM
Alas, I only had a narrow window of access - restricted area in a regulated environment - and I doubt I'd be allowed to publish any details, anyway. The documentation had to go ahead without the information and is now out of my hands.
But I appreciate all attempts to help - and hopefully the engineers concerned will know what pitfalls to avoid next time...
Best,
Peter