LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

How to print a block diagram that is more than 1 page

Hi, I am documenting my program. My block diagram spans 6 to 7 pages horizontally and 4 pages vertically in an A4 sheet in the "VI documentation" utility(File -> Print -> selecting my vi

-> VI documentation ->Print Preview)

Is there a way to print it in one single chart(or bigger size paper).

Please Help...

 

Thank You,

DSK

0 Kudos
Message 1 of 5
(5,376 Views)

That probably means the your block diagram is too large.  Try reducing the size by encapsulating the code into subvis.

 

From the style guide:

 

The size of the block diagram window can affect how readable your
LabVIEW code is to others. Make the block diagram window no larger than
the screen size. In addition to the size of the block diagram window, it is
also important to ensure that the LabVIEW code displayed is not too large.
Code that is larger than the window is hard to read because it forces users
to scroll through the window. If the code is too large to fit on one screen,
make sure the user only has to scroll in one direction, horizontal or vertical,
to view the rest of the code.

 

http://www.ni.com/white-paper/4434/en 

>

"There is a God shaped vacuum in the heart of every man which cannot be filled by any created thing, but only by God, the Creator, made known through Jesus." - Blaise Pascal
0 Kudos
Message 2 of 5
(5,371 Views)

"That probably means the your block diagram is too large" is not a viable solution.  the basic problem is that NI (8.5) has yet to figure out what just about every other application on the planet uses and that is a ZOOM WINDOW feature.  Instead, they use their cumbersome navigation window.  One solution if to select print >> <VI name> >> "icon, desc, panel, and diagram" >> "HTML" >> "save"  then it will create a bunch of image files.  one of those image files will be the complete diagram.  the picture quality is not the greatest, but is sufficient.

0 Kudos
Message 3 of 5
(5,263 Views)

If you go further in the Print dialog screens, about the last thing you come to is an option to "Fit [FP or BD] to page." there, it will take up only 1 page. Unfortunately, with what you describe, it will be totally unreadable without a 14,400 dpi printer and a 5X loupe.

 

(To johncf) That is a big reason why the only really viable solution is to cut it into bite-size subVIs, then connect them to make the big picture.

 

(Back to Dsk001, now) The subVI route also makes things much easier to build and troubleshoot, because you can code them as standalones and confirm their functions without having to run the whole program (most of which, in your case, sounds like it would be irrelevant in testing one or two functions).

 

Cameron

 

To err is human, but to really foul it up requires a computer.
The optimist believes we are in the best of all possible worlds - the pessimist fears this is true.
Profanity is the one language all programmers know best.
An expert is someone who has made all the possible mistakes.

To learn something about LabVIEW at no extra cost, work the online LabVIEW tutorial(s):

LabVIEW Unit 1 - Getting Started</ a>
Learn to Use LabVIEW with MyDAQ</ a>
0 Kudos
Message 4 of 5
(5,253 Views)

@johncf wrote:

"That probably means the your block diagram is too large" is not a viable solution.  the basic problem is that NI (8.5) has yet to figure out what just about every other application on the planet uses and that is a ZOOM WINDOW feature.  Instead, they use their cumbersome navigation window.  One solution if to select print >> <VI name> >> "icon, desc, panel, and diagram" >> "HTML" >> "save"  then it will create a bunch of image files.  one of those image files will be the complete diagram.  the picture quality is not the greatest, but is sufficient.


God, I would love some sort of scaling window!  But you can still have a BD that is "too large."  If your code extends more than one screen in either direction, it will be pretty much unreadable at "fit to screen" mode.

 

But aside from aesthetics, breaking up your code into sub-VIs is always a good idea.  You wouldn't write C code with just a main, would you?

 

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 5 of 5
(5,245 Views)