Large JPEG on Front Panel?

I have a JPEG of about 300 KB. When I drag it onto a front panel and save the VI, the VI is about 2.4MB. Is there a way to decrease the file space taken up by these JPEG's on a VI? Why such an increase?
Michael

miguelc a écrit:
I have a JPEG of about 300 KB. When I drag it onto a front panel and save the VI, the VI is about 2.4MB. Is there a way to decrease the file space taken up by these JPEG's on a VI? Why such an increase?
Michael
That's probably because LabVIEW stores the image as a bitmap. And your JPEG correspond probably to a very large image, heavily compressed. Try to resample the image at screen resolution and this will probably reduce stringly your memory foot print.
You should also know that screen update can be much slower when controls have to be updated over a background picture. A solution to reduce this problem (that you don't have yet...) is to divide the image in smaller chunks. That way LabVIEW is not obliged to redraw everything at each small screen change.
So while you are editing your image resolution, may be you should spend some additional time to cut it into smaller parts.
Message Edité par chilly charly le 11-17-2007 01:04 AM
Chilly Charly (aka CC)
E-List Master - Kudos glutton - Press the yellow button on the left...

Similar Messages

View Cluster Control/Indicator as Icon on Front Panel (sub VI's)

I make a lot of use of clusters to pass data into and out of sub vi's. I keep everything typedef'd and the clusters can often grow to be rather large on the front panel which makes navigating the front panel quite difficult. I usually have maybe 2 or 3 other controls and indicators that are not within the cluster.
Is it possible to view the cluster as an icon in a similar way to the block diagram?

Hello DNichols,
I recommend placing the cluster(s) in question partway off-screen, with the label displayed. If you really need to minimize the footprint of the cluster front panel object, set AutoSizing to "None" via the right-click menu and resize as needed, but keep in mind that the FP object is now more-or-less useless to future developers except for ease of clicking to link to the connector pane. Since you're type-defining everything, accessing or viewing the contents of the cluster might not matter much, though.
Redefining your architecture is probably not a priority right now, but you might also want to consider using classes in the future, as others have suggested.
Regards,
Tom L.

I built an application to store de front panel of vi in a JPEG image file, but native labels of controls and indicator are unclear after image capture, some one knows why? I have a working example you can test.

For some label colors like yellow or green, this defect is almost invisible, but for black color or any dark tone like brown or dark gray after file creation appears unclear labels.

In more details, JPEG uses lossy compression and is not really suitable for cartoon-like pictures with objects containing high-contrast sharp features such as lines and boxes (as found in front panels). This has to do with the truncation in the 2D cosine transforms which gives you weak ripples near sharp edges, not visible in typical photographs.
Of course you could set the quality to 100% (optional input) for no truncation with a trade-off of larger files, but it's pretty pointless. JPEG is only meant to be used for photographs.
PNG is a fantastic format (intended as a GIF replacement), uses lossless compression, and wins in all aspects over jpeg for your intended use. All modern applications can deal with them (e.g. you can insert them into word or powerpo
int) and any modern browser can display them. (see e.g. the PNG home site for more info).
LabVIEW Champion . Do more with less code and in less time .

How do I programmatically display jpeg files on the front panel

Hi,
I would like to be able to programmatically display various jpeg images on the front panel of a VI. I would mostly like to be able to display one image at a time and have the ability to programmatically change the image to different ones under program control. I found a picture indicator but not sure how to use if or if this is the best way. Thanks for any help.
Dave Adams

Yes, you can use a picture indicator.
The attached simple codelet shows how to display a jpeg image on it (Make sure the image indicator is big enough).
Let us know if you need help with the rest of the coding.
LabVIEW Champion . Do more with less code and in less time .
Attachments:
DrawJpeg.gif ‏2 KB

Larger Cursor on the Front Panel

Hello,
I wanted to know if anyone knows how to make the mouse cursor on the front panel larger. I looked at the Cursor VIs built into LabVIEW, but it seems none of them actually change the size of the cursor, but just the cursor image.
Thank you,
Russell
Engineering Team Leader
G Systems, www.gsystems.com
Certified LabVIEW Architect
Certified Professional Instructor

Thank you for your help. I am using Windows XP.
The link you sent does the same thing as the Create Cursor From File.vi that is part of the cursor VIs in LV, see the attached image. The VIs you mentioned were written in LV 5 and I think that was before they had the built in cursor VIs.
It looks like you can use the Create Cursor From File.vi to create a custom cursor, but I think the size is limited to 16 X 16 image. So it wouldn't make the cursor any larger. I think what I need to some way to scale the cursor itself not just change the image.
Any help you can give me would be great.
Thanks,
Russell
Engineering Team Leader
G Systems, www.gsystems.com
Certified LabVIEW Architect
Certified Professional Instructor
Attachments:
cursor.PNG ‏13 KB

How do I group a large logic circuit into a single icon that still allows for control of that VI's front panel?

I have a graphical representation of a P&ID made of LED lights that turns green or red depending on if that
process line is open or closed. The coorisponding block diagram is a rather large logic circuit that controls
these LED lights.
My problem is that I want to essentailly block that large piece of code into a "Sub VI" but I still want to use that
code to control THAT VI's front panal. This would allow me to, in the future, make an automated sequence that can
still use this light show without opening another VI's front panal.
If anyone has used Simulink this is the exact same thing as its grouping function...

Are you asking how to control the front panel of one VI from the front panel of one of its subVIs (or another VI)? Is so, check out VI server. VI server functions are found on the Application Control palette. For a short demo, right click on one of your controls and select Create»Reference. You will be switched to the block diagram and have a reference node attached to your cursor. Drop it. Now go to the Application Control palette and select and drop a Property Node. Connect the newly created reference to the Property Node top left terminal. Click the Property Node's Property area and scroll down to the Value property and select it. Right click on the Value and select Change to Write. Wire a value to this input and it will change the value of the control. You now have a method that allows you to change the value of a control from another VI.
Some caveats. This can be slow. It is synchronous, meaning that the function will not return until the front panel has been updated. If you want to do a lot of controls at once, use the VI property Defer Panel Updates to turn updates of the front panel off while you are writing to it. Don't forget to turn it back on. If you can use a terminal or local variable, do not use the Value property.
My apologies if I have misinterpreted your request. Let us know if you need more info.
This account is no longer active. Contact ShadesOfGray for current posts and information.

How to: display large error note in the front panel?

hi guys,
When "error out" has an error, I would like to display HUGE RED TEXT in the FRONT PANEL saying: "STOP, ERROR DETECTED!" )
How to do that?
Thanks for your help.
Solved!
Go to Solution.

Place an indicator on the panel. Set the text to HUGE and RED, and set its value to "STOP, ERROR DETECTED!". Make it not visible. When you get an error, use the "Visible" property node to display it.
To learn more about LabVIEW it is recommended that you go through the tutorial(s) and look over the material in the NI Developer Zone's Learning Center which provides links to other materials and other tutorials. You can also take the online courses for free.

Print front panel

I have been going through messages for a while but just can't seem to find exactly what I'm looking for. I need to print a waveform chart that has two plots that update at about 10Hz. Simple enough, right? Problem is that the report vi's have no way I can see to easily enlarge the image. I tried putting a larger chart in a sub vi that prints after executing but the chart only get part of the data when I run it. Then I tried the invoke get image method but can't find an indicator for the image data. Is there a way to print an enlarged waveform chart image? It would be even better if I can just print a front panel of a subvi with the same data on the waveform chart that appears on my top-level VI.
PaulG.
"I enjoy talking to you. Your mind appeals to me. It resembles my own mind except that you happen to be insane." -- George Orwell

What I have done in these situations is to have a graphs that is sized to printout the size that I want. I then update the graph from the program data, grab an image of the graph using the Get Image method, and save the image as a jpeg file. I can then either printhout this file or include it in a standard report.
OR you can use Draw Flattened Pixmap.vi to turn it into a form that will go into a picture indicator
OR you can create a VI with the graph on its front panel that is set to print itself when it finishes executing - or which you print programatically
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

Front Panel Mass Binding Project Variables Issue

Hello -
When attempting to bind controls to shared variables through the front panel mass binding option, there is an issue where you can not seem to bind a "project item" to the control. The method of binding I am using is to export a text list of control names, urls, mode, and function to a text editor utilizing the front panel binding mass configuration options. The text editor shows, in the fourth column, a "0" for no function, a "1" for network item, and a "2" for project item. when attempting to import the list back into the front panel binding mass configuration, all "2" indications become "1", as all items are treated as network. Thus one can not effectively bind to a project shared variable item.
The binding works fine manually by means of utilizing the properties selection of the control, but it is difficult to do this for 821 controls, as in my application.
My application is based on a OPC served group of 821 variables which are linked to controls and indicators through the shared variable representation for each item created in the multiple variable editor.
Does anyone have a work around for this issue, as it is a showstopper right now, ie, you can not effectively bind a large quantity of controls or indicators to project located shared variables as required.
The rationale behind utilizing project located variables instead of network located variables is to reduce the amount of calls to the OPC server which was causnig a large latency in the refresh of the 821 items. With the items defined as shared variables within the project, a single call is issued, which has tremendously sped up the refresh cycle for the list of variables.
Thank you in advance for your insight in this matter,
John DeCroos

Hello Brian A.,
In response to you comment --
"in 2006, and John did not follow up with any more information for Efosa"
-- a great deal of information was provided to NI (Efosa and many, many others, up to the product manager for the DCS module). I have never heard back on a fix for this bug for the identified version of LabVIEW. The reply by Efosa here was well after we had shipped our product -- (please see date + Efosa's apology) -- we had found our own solution as is identified in the original post.
My solution was, as is also indicated in my original post, to manually bind each variable. This was unbelievably time consuming, but was all I had.
The version of software I am now working on uses far less variables, manually bound to avoid the multiple binding issue we had in the past.
I have checked the mass binding function in LV 8.5.1, it works fine now. I guess it would have been nice to have had a reply that the bug had been resolved ---- would have helped me out a bit.
Thank you,
John DeCroos

Open and close front panel

Hi,
I wish to have a VI that works as a main menu from which you start new
VI's depending on your choice. When the new VI start I want the main
menu to hide it's front panel temporarily until it the second VI
returns.
Anyone has a solution to this?
/Nimrod
Sent via Deja.com http://www.deja.com/
Before you buy.

[email protected] wrote:
When the new VI start I want the main menu to hide it's front panel temporarily
until it the second VI returns.
If you are using LabVIEW 5.1, you can use the VI server attributes to hide
the VI by moving it off of the desktop. I will send you a sample in private
mail.
The attribute (property) you need to use is Front Panel Window -> Window
Bounds.
Set it to something that is larger than your window size, like 2000, 2000,
2200, 2200.
I hope that this helps,
Bob Young
Bob Young - Test Engineer - Lapsed Certified LabVIEW Developer
DISTek Integration, Inc. - NI Alliance Member
mailto:[email protected]

Have a program in which a sub vi front panel pops up when the main vi is loaded

I have a strange problem.
This problem only occures after building an application using LV 8.6 Professional version Application Builder, and I have installed it onto the target computer. It doesn't happen when running the development system.
When I load the program on the target computer, one of the subvi's front panels used in the application appears on top of the main vi's front panel.
This subvi should never appear on the front panel at any time during the program exicution.
It happens to be the Write to Spreadsheet.vi that is part of the standard vi library.
I have checked all calls to this subvi to verify that it has not be modified to make it load or appear when the main vi is loaded.
It is called at 4 different times during the program exicution but in no instance is it set to show the front panel.
Has anyone seen this and if so what was the fix?
Solved!
Go to Solution.

Does the exe file run on your development computer without the popup?
Can you post a VI that demonstrates this behavior?
You've probably already checked, but there are two places that need setting, the SubVI Node Setup, and the File Proeprties Execution tab. See attached jpegs.
Message Edited by Pablop on 09-02-2009 02:20 PM
~~~~~~~~~~~~~~~~~~~~
Paul Johnson
Renco Encoders, Inc
Goleta, CA
~~~~~~~~~~~~~~~~~~~~
Attachments:
SubVI Node Setup.jpg ‏13 KB
VI Properties Execution.jpg ‏32 KB

VI Front Panel in SubPanel reacts slowly

In LabView 2010F2, I have a VI that has several buttons and other controls on the Front Panel. When I run that VI standalone, it runs very quickly, uses less than 20% CPU, and is very responsive. ALl of the controls react very quickly. But when I put that same VI FP in a subpanel in a small VI, all of the controls in the VI in the subpanel are now running very slowly. There buttons are slow to react. There is almost a 1/2 second delay on the buttons. The CPU is stall down around 25% usage. The hosting VI does not do much and should not be responsible for this delay.
If the CPU is not very busy, what is the cause for the delay in the reaction of a Front Panel of a VI that is placed in a subpanel?
What can be done to significantly improve the response of a FP that is placed in a subpanel?

dbaechtel wrote:
Ben wrote:
How is you memory doing?
Do you have "show Kernal time' selected?
Ben
CPU Usage and Kernel Time do not pudge much during Save All or Clean Up Diagram of large diagram. CPU usage stays about 25%, Kernel time stays about 50-75% of Total CPU Usage.
I don't see any reason why LV would show "not responding" under these conditions unless there are some long LV processes that are being executed that include significant I/O delays that do not relinquish the CPU to do other things while executing these long LV processes. If LV was not blocked by I/O (disk) delays then I should see near 100% CPU usage. If LV was being delayed by memory swapping, the I should see less than 50% memory free,
I'll leave the discusion of Internals and Data Structure for another thread.
Spoiler (Highlight to read)
Both of my copies of that book are much more worn.
Both of my copies of that book are much more worn.
It is going to take some work to narrow down the possiblitlites since you have presented this situation as an interaction problem.
Generally speaking there is one hot button that comes to mind and that is the UI (User Inteface) thread where all GUI updates are handled as well as those things that do not play well if left to run in their own threads (property nodes for example).
SO I would like to suggest you start by trimming it down to something that work good and then start adding stuff back until you can detect the performance hit. At tath point step back and look for contention issues.
If I remebe correctly you can't post code images so asking you to post images of teh code that does not play nice together is a no-go.
You could also run the performance monitor.
THe Trace Execution tool kit should aslo help you get a the root of this situation.
Trying to help, wondering if if I can,
Ben
PS Regarding the bug thread. I depend on that thread to stay on top of potential bugs. I asked and Laura moved the off-topic posts to the proper thread. Please excuse my "anal-retentive" side.
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

Why doesn't LabView scale my objects properly in the front panel?

In LabView 6.02 (Windows 2000) I have experienced problems when using the "Scale all objects on panel as the window resizes" option under VI properties. Try the following example: Go to the front panel and draw two arrows (from Decorations), one vertical and one horizontal (make sure they are perfectly straight). Now, resize the window, using the bottom right corner several times. You will soon find that the two arrows become increasingly missaligned and are not perpendicular to each other anymore. The problem gets worse the more you play around with the window size and they will never return to their original state. Installing the 6.02 patch did not seem to help at all.

Dear Gustav,
First of all, some objects do not scale whatsoever in LabVIEW. These include refnum controls and text.
As far as the "scale all objects on the front panel as the window resizes" option goes, you have brought attention to an issue that I will announce to the R&D team. Currently, when you resize the screen, the objects on the front panel are resized at the same fraction of the original size, yet small rounding errors occur. As you move the window around, this small rounding error multiplies accordingly. Once you maximize the window, the small rounding error is translated into a large-scale degree change in the orientation of the (previously) perpendicular arrows.
What action are you trying to perform that caused this issue? If possible,
please post some screen shots of your front panel or give me explicit details as to your programmatic goal.
One thing that you may try in order to prevent this misalignment and orientation shift is to highlight the arrows. Then, click the "Reorder" button on the toolbar and select [lock]. This will lock the objects and prevent them from resizing while the rest of the screen resizes (see attached image).
Again, I'm sorry if the aforementioned phenomenon causes you any inconveniences, and I will be sure to announce this issue so that preventive changes are implemented in future LabVIEW revisions.
I hope this helps. Please let me know if you need any further assistance. Have a great day!
Kind Regards,
Joe Des Rosier
National Instruments
Attachments:
lock.JPG ‏33 KB

How can i print an excel spreadsheet file by clicking a button on the front panel

i have designed a vi that logs data into an excel spreadsheet. i want to take print out of the file when the user clicks a button on the front panel. what to do if there is very large amount of data.

Preet,
Printing the Excel sheet is just an ActiveX method call to print the worksheet. To add data to the worksheet, you already have the reference, just call a print method. As for handling large amounts of data, that is a vague question. The data will print how ever you placed it on the worksheet. If what you mean is that you don't want to print out 25 pages every time, the print method has options to only print specific pages or ranges. You may want to play around with a sample spreadsheet to learn the printing options. For help on the ActiveX functions, make sure you have the Visual Basic help installed for Excel.
Randy Hoskin
Applications Engineer
National Instruments
http://www.ni.com/ask

An alert messarge i don't underdant: insane object at BDHP + 83ACC in "VI name's":{graphics} (0x80):Front Panel Terminal (Term)

Hello!
I don't know why in just yesterday appear in one of my VI an alert message or error message when i want to close oer save the VI.
The message is like the following one:
Insane object at BDHP + 93ACC in "Vi name's": {graphics} (0x80}: Front Panel Terminal (Term)
I don't know why now it appears this message because i have no modify the Vi.
I want to ask you why it appears this message and the most important......how can i solve it?
Thank you very much
Larson

Hi!!! I copy and paste from an NI engineer post asking about what is the "insane object" problem:
This message means that an object in LabVIEW such as a wire or a loop tunnel does not pass an internal test known as a sanity check. If the errors are serious enough, LabVIEW exits because something has become very corrupted. Sanity checks occur before each save, to ensure that corrupted VIs are not written over good VIs. They also happen as part of the compile process. Thus, sanity checks happen frequently. Many insanities are actually fixed (made sane) after the dialog box appears and will not appear again, so the first thing you should do after receiving an insane object error is to try to make a backup copy of the VI, run it, and perform some additional editing to see if the problem was resolved automatically.
VI corruptions do not happen often. They can happen because of disk corruption, but this will often lead to a file that can no longer be loaded. Corruptions can also happen because the programmer did something that corrupts a LabVIEW data type, perhaps as the result of a call to external code. The following are examples of insane object errors:
Insane Object at BDHP+4D50 in 'sksks.vi': (graphics) (0x80):wire segment (WIRE)
Insane Object at BDHP+5CA0 in "CAPL3.vi": (graphics) (0x80):loop tunnel (DCO)
In the first example above, the error message itself gives information about which object is insane. BDHP means the offending object exists on the block diagram heap, as opposed to the FPHP for front panel heap. The +4D50 is the hex offset in the heap where the object is located. The "Wire Segment" text indicates that the object is a wire object. The "graphics" text indicates that the insanity is graphics-related, which means it is not serious and will most likely be repaired automatically.
The second message above is similar, but refers to a loop tunnel (i.e., the tunnel formed where a wire crosses the edge of a loop) rather than a wire.
Solution: If you receive an insane object message, it is best to delete and recreate the most recently created objects on either the front panel or block diagram, depending on whether the error message contains "FPHP" or "BDHP". Make use of the text in the error message in deciding which objects to rebuild. In the case of the second message above, it would be best to delete and recreate the most recently created loop tunnels.
Another workaround that works best if the VI is small is to select the entire diagram and copy it to a new VI. After saving the new VI, there is a good chance the insane object error will no longer appear. If the VI is too large to cut and paste to a new VI and another computer with an identical version of LabVIEW is available, you can copy the VI to disk (or to your network if that is available) and open it on the second machine. If the insane object errors do not appear, save the VI (on the second machine) and transfer it back to the original PC (by disk or by network). The new, uncorrupted version of the VI should now run without generating the insane object error.
Hope that helps you,
Jaime
Regards,
Jaime Cabrera
NI Applications Engineering Spain

Large JPEG on Front Panel?

Similar Messages

Maybe you are looking for