I'm not sure if this will work for you or not, but this is what I
thought of when I read your post...
You can't look at 100 histogram simultaneously. You can probably only
fit 4 or 5 on a front panel (without using tab a control, and I
recomend NOT using the tab control), so I would try to work w
Use a Call By Reference node to pass the data directly to the dynamic
VI.
There is a great shipping exaple that illustrates how to use the call
by reference node. Launch the example finder >> go to the Search tab
>> type in call by reference >> click the Call By Refernce Nodes text
that apperas i
go to Paint (or your favorite drawing program) select and copy the
image (this puts the image onto the clipboard), go to labview and
paste the picture on the front panel.
You can also attach an image to a control (like a button) by right
clicking the fP object, selecting Advanced >> Customize, and
either build a Waveform (using the Build Waveform VIs) and supply the
initial time, and delta T. Or use the waveform Graph, and a bundle to
supply the array of data with a initial time, and the delta T.
LabVIEW ships with an example called Waveform Graph that illustrates
the various ways to trans
try to generate an HTML report first, and then print that. Some
printers are worse than other at printing (what looks like) a simple
object.
Otherwise, I would do some basic trouble shooting, like can you print
a simpler front panel image (say two numerics) to the printer. Next,
I would try to p
when putting arrays into a DB, you should define the column to be
"image data". (I'm sorry but I forgot the word that the DB people
use, it's not image data, but I think it is similar...). Since an
image is a 2D array, that data type works perfect for arrays of data.
It will let you insert the en
yeah,
have you tried the information available from the NI site? Just type:
+GOOP into the search field and you will get lots of information,
tutorials, etc.
here's the search results for the search mentioned above
(http://search.ni.com/query.html?col=alldocs&qs=-languagetype%3Anonenglish+-conte
CINs are a pain.
Whenever possible, use a Call Library Function (CLF) instead. Things
will go much smoother for you. If you have LV 7.0, there is a
shipping example called "Call DLL.vi" in the \examples\dll\data passing\Call Native Code.llb. This example is
an excellent resourse, and should add
If you are performing any sort of mathermatical analysis, then you
should upgrade your base version of LabVIEW to either full or
professional. The extra cost for the upgrade will be paid for as soon
as you call the Sinewaveform VI you mentioned. In addition to
function generation, you will get an
the LV team made this drop dead simple in LabVIEw 7.0 by intgrating
your VI and the command line. If you ahve LV 7.0, open the example
called "CommandLine.vi" to see how it works.
If you don't have LV 7, then I recommend that you look at the
evaluation version just for this feature. The eval is
do you have any more specifics on the issue? What version of LV, what
are you doing when the crash occurs (running a VI or editting), can
you reproduce it, etc. Also, is there anything else reported with the
crash, (error number, line number, module, .cpp file name, etc).
you should read in the file first. From the Read File VI, you now have
(for example) an orange wire representing an array of doubles. Now
take the new data you want to plot, and do a Build Array with the old
data (read from the file) and then wire the built arrays into a graph.
Somethings to keep
nice! Where can I get the LV 7.1 eval version?
13 matches
Mail list logo
