PNeville,/P
PI just tried to do an SCXI strain gauge project with
DAQmx and the most recent drivers and also had horrible
experiences. I don't think the addressing of SCXI modules
and channels is right. After my customer and NI didn't
have any luck at it, I had to make an emergency plane trip
The message box is excellent! I really needed it.
Thanks,
Prasun Mital
Well for Greg it is easy. He is one of the core LabVIEW developers and
although he doesn't know every detail from his head, he can go and look
in the sources, if he needs to.
For me it is just 12 years of working with LabVIEW and having read a lot
on Info-LabVIEW, as well as having done
I'm trying to do the same thing with a progress bar. The closest I have
come to increase/decrease control of the bar is to use a variable. Right
click on the variable name and select the desired indicator. Feed the
variable the data and the progress bar will follow. The indicator does
In the VI Properties (right click on the icon and select VI Properties
. .), on the Catagories dropdown list, select Window Appearance.
Choose Customize then un-check the option Allow run-time shortcut
menus.
That should do it for you.
Tim
See answer to identical post a
href=http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101RPAGEID=135HFORCEKWTID=99128:5HOID=5065000800FED2HExpertOnly=UCATEGORY_0=_49_%24_6_UCATEGORY_S=0;here/a
The reason I chose this way (other than not knowing another way) was
that I wanted to increase the value in the progress bar for 1 case
statement and decrease it for another. I have a while loop with a shift
register that is used to increment the progress bar in 1 case, and in
the other I
How come NI did not address this issue yet?! They got to have a
universal GetTypeofVariant thing somehwere there, I am pretty sure.
In plenty of cases, variants can only have a few types. It is pretty
easy to cast them to the various types to see which succeeds and which
fails.
In those
I can't save any VIs. When trying to save a VI, LabVIEW crashes and
gives the following error message:
Error #3:memory.cpp, line 996 LabVIEW version 6.1
This a new installation of LabVIEW 6.1 on a WIndows NT operating
system.
What has happened prior to the save? Error 3 indicates that
I want to disable the right-click of my mouse while my Labview app is
running. Anyone have a solution for this?
For each panel you want this done for, open VI Properties and change the
ring to Window Appearance. Hit customize and in the lower right is an
option for runtime shortcut menus.
What I mean to say is the use of time is inconsistant. Trying to put
time on the x-axis of a chart is terrifying. XY chart is pretty easy
and intuitive. Measurement Studio and VB is intuitive.
The realtime.vi is a help but what happens when your data is coming in
at irregular intervals.
At 11:04 PM -0400 5/7/04, David Hoadley wrote:
Has anyone had trouble with slow updates of tag data in LabVIEW DSC
v 6.1? Or better yet, have a resolution to the problem! We have a
control system that consists of an Allen-Bradley PLC SLC5/05
connected via Ethernet to our HMI PC.
I have a large vision based (IMAQ) application that I developed as an
executable for one of my customers using LV v6.1. The software uses the
serial port to communicate with a microscope stage and has a PCI1409 frame
grabber card. We are using Windows XP computers. The customer has a CD
with
Lewis,
What aboutinstalling LV7.0 without the new imaq images format? I think by default LV7.0 installation does not install the new image format. So may be LV7.0 with imaq 6.x might be a working conbination ?
PJMLewis Drake [EMAIL PROTECTED] wrote:
I have a large vision based (IMAQ) application
Hi Dennis
As in most of the LV-related things, also here I think you are right.
kind regards
Pawel
Hi Luca
Thank you for the answer. I understand. I my situation I would prefer
to have the latest version installed. I can live with some different
directories, but 90% will be overwritten with the new version. So do
you think I can overinstall the new version to the old one?
What about the
Greetings:
You will find that in Labview, the squeaky wheel gets the grease!
Until recently, EVENTS in Labview were treated as ugly children, now,
the entire architecture of Labview is event driven. This change was
brought about only because of vocal popular demand. I believe
Dear Carnivorus:
I would venture to say that perhaps there is not enough memory to
complete the operation! :) All snide aside, working with large
arrays takes some serious number crunching. You might try twiddling
your swap file size (on the Advanced properties tab of My
Good Afternoon all,
I've noticed that there has already been some dicussion about the improvement of
certain aspects of LabVIEW VISA usage with the release of LabVIEW 7.1. Has anyone any
feel for any impact in the response time, particularly in setting attributes (parity,
etc.), either
You will find that in Labview, the squeaky wheel gets the grease!
Until recently, EVENTS in Labview were treated as ugly children, now,
the entire architecture of Labview is event driven. This change was
brought about only because of vocal popular demand. I believe more
20 matches
Mail list logo
