Hmmm...
It looks to me like you should be able to as if you'll look under XY
Graph Properties-Plots, each plot has a drop-down list of items
specifying the Y-Scale and X-Scale that the current plot is using.
The only problem is, each list only contains a single item - either
the current X-Scale
Howdy all,
There was a similar earlier post asking about wait accuracy over small
periods:
tmh,
No, I'm pretty sure you understand perfectly, as that's exactly what I
wanted to do. I knew that if you had two loops on a block diagram,
they would execute in parallel, but I assumed that if you had a loop
and a SubVI on a block diagram, that whichever one started executing
first would
and I guess I should come up with a new expression other than
frustratingly lacking at times, since I used that one already...
Yup, I've reworked my VIs and it works exactly as I wanted. I feel
pretty dumb... my new golden rule: keep it simple stupid.
thanks again
Hi Alex,
Sorry, but I can't open that VI either.
I had exactly the same problem yesterday involving three very
important VIs to a large project at work. The project has a vision
component that I was testing yesterday. We're short on hardware, so I
was given a crappy IMAQ framegrabber card that
From what I understand, using local variables is frowned upon unless
they are ABSOLUTELY necessary. In my mind, there is no debate and I
would take the shift register. Here are my reasons.
1. I believe that each local variable you have on your block diagram
takes up the same amount of space as
Howdy all,
Here's my situation:
- I have some task that needs to be executed in parallel to the
currently running VI. In fact, this task needs to executed in
parallel to a number of VIs,
so I've decided to build a sub-vi to handle this task.
- This task involves performing some processes every
Sander,
I'm 100% sure I could help you... if I knew what you were trying to
do. The more I read your description, the less I understand, and
since I don't really know what you're trying to do, I can't do much
with your code.
It seems to me like your real problem is your ability to partition the
the wait down
into several sections to reduce the time between sending the command
and receiving it, but this would amount to polling a variable and I
don't want to do that.
In any case, sincere thanks for your suggestion.
Victrick
H...
A few more details might be a little more helpful... If you could
write a scaled down version of your program that demonstrates the
problem, that would be helpful for anyone trying to solve your
problem.
I wish I could help you as I'm also doing some stuff with the HTTP
server, but I'm
Howdy all,
I've got a program that is complete, and offers some basic service.
Advanced users will have the option of additional functionality. When
users decide to use this program, they decide what capabilities they
want - whether it provides just the base functionality, or if it has
the
Andr=E9 and James,
Thanks for your help. Right now, I'm using the
SHGetSpecialFolderLocation and SHGetPathFromIDList functions of
the shell32.dll to get the windows system directory.
The event handling is divided amongst multiple loops for the sake of
encapsulating the related code - in the actual program, there are lots
of controls on each tab and lots of events to handle. Lumping all the
events together in a single event structure makes the code less
readable then I would
14 matches
Mail list logo
