A way to view block diagram without LabVIEW installed?

[Yamaeda]

---

@Clint1000 wrote:

Not a solution but a comment..I had asked this years ago also.  Another issue is I look in Discussions Forum before I post a question.  Sometime people have posted code to try.  I don't have labview at my desk but in the Lab across campus and can't view it.  Its great when they post a snippet.  Added benefit of the snippet is it forces me to look thru the pallets to find the functions I need to recreate the vi.

---

Save the PNG and drag it into an empty VI and you'll get the code. 🙂

/Y

[Blokk]

Guys, did you read the OP's first post? I think not, otherwise you would not propose snippets and print outs. Read the first post again. 

[jcarmody]

Our Software Quality Assurance engineer has a basic license for LabVIEW and TestStand so he can view our stuff.  He can see any FPGA/RT pieces, just can't do anything with them.  It works for us.

[Relec]

---

@jcarmody wrote:

Our Software Quality Assurance engineer has a basic license for LabVIEW and TestStand so he can view our stuff.  He can see any FPGA/RT pieces, just can't do anything with them.  It works for us.

---

This seems like a viable solution, but isn't he going to get broken VI's if he tries to open Host.VI's that use FPGA or RT modules?  I'll try a trial version on a laptop and see if I get any issues opening the code. 

Thanks

Relec

[dmaripro]

NI should give serious consideration to releasing a viewer. In high security businesses like military and government contractors, atomic energy, public utilities, etc., USB ports are locked and often times, programmable systems are "air-gapped" to minimize security risks. They can't run security software because it interferes with the operation of real time applications. Users don't have the option to download example VI's and see how they work. 

I'm trying to do this right now and I have to go to IT, get an encrypted USB memory stick, download the file to it, make sure it's scanned, transfer it to the test system, and finally, I can see it.

It's not like NI is giving up any secrets or losing a major source of sales by simply letting us view VI's. I mean, we're going to put that information learned to work and, oh, maybe, BUY MORE NI systems because of it.

[rolfk]

But the real problem is that for a viewer to work you have to have available all Vis that are used which includes the whole vi.lib, user.lib and instr.lib and several other directories for RT and FPGA to work and then you end up installing pretty much the full professional version with any used modules and toolkits sans a few dlls and a reduced exe file!

Definitely not what anyone would expect when thinking about installing a viewer. Alternative would be to develop a module that can generate a svg or similar interactive movie format from a VI hierarchy. There have been community led attempts at that in the far past but all were abandoned. A proper NI created solution would likely be an effort of several man years of development and not something NI is likely to do as a free addin but as an additional addin most likely never would return the initial costs not to talk about maintenance and support so get abandonware very quickly as has happened with a LaBVIEW viewer version around LabVIEW 5 or so.

[Intaris]

I had an old version of a tool which modified the existing LV HTML documentation output to add hyperlinks everywhere. Made clicking on sub-VIs in the dependencies list possible. I found it useful, maybe I should dig it up even though I'll most likely be completely horrified by the code.....

[Bo-olean]

Maybe that's the universes way of saying your manager needs to start trusting you instead of micromanaging your code...

By the way, you can always make a snippet of your code, which is simple png, so should be viewable by your boss. And is not so much work for developer to create this.