01-23-2013 04:10 PM
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
01-23-2013
04:33 PM
- last edited on
04-18-2025
09:29 AM
by
Content Cleaner
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
02-18-2014 07:20 AM - edited 02-18-2014 07:35 AM
"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.
02-18-2014 08:12 AM
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
02-18-2014 09:01 AM
@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?