-
Posts
6,196 -
Joined
-
Last visited
-
Days Won
104
Content Type
Profiles
Forums
Downloads
Gallery
Posts posted by Michael Aivaliotis
-
-
-
Yes. I already reported this in LV7.0. I guess it still exists in 7.1... :thumbdown:
See my post:
-
-
It sounds like you found a solution. Another way is to create the file in the c program and then have lv check for the presence of the file. When LV toggles the boolean then have lv delete the file. Repeat this process. This way you can have the c program verify that LV saw the file and toggled the boolean. As you say, NOT pretty but works. Why not get LV to do the DAQ card directly?
-
It looks like you're writing data to the chart plot name. Can you show us the diagram?
-
Try using a USB mouse if you can.
-
The error is comming from another VI that is trying to write to the same file you are trying to read. When you use the "read characters from file.vi" it sets the read-only flag on the file. This means while you are reading the file, all other vi's accessing the file will give an error.
-
PID control on a PC? Hmm. If it was more than 5 years ago I'd say sure, give it a go. However now with the availability of the LabVIEW RT software module and the RT targets, why go PC? The frequency is low enough to be run on a compact fieldpoint module. You will not get determinism on the windows platform. How critical is this control? What happens if you lose control? Do bad things happen? Do people get hurt?
-
-
It sounds like you should be using a UDP reference right? This is then a problem with the example code which must be reported to NI for a future fix.
-
Michael,
If I use the Install Creator app to create installer file. Is that a good idea??
Because when I use it created my app to installer file the *.EXE size is the smaller.
I have no idea about this software but the bottom line is, if it works, go for it!
-
I was on-site recently and was stumped by a few DAQmx issues. I qualify this by saying that i'm running LV7.0 with the DAQmx drivers that came with it. It's possible that these issues have been resolved in the most recent release.
The first problem is the tasks vs. channels. For some reason the task behaves quirky. In a continuous loop situation, when I used a task setup to monitor an input, I would not always get the latest voltage. Sometimes it appeared to display a previous cached value even though I verified that the voltage was changing on the input. I was also calling the same task name in a parallel loop (because i could). When I switched to using a straight global channel name, the problem went away.
The other issue is with the MAX configuration. I wish I had more time to debug this and provide a better solution but... The DAQmx tasks and channel names do not seem to be immeadiatly available when you boot your computer into another user account (under WinXP). My entire debugging was performed under an administrator account. Whenever I booted clean, the DAQ portion of my application would work properly. However, When I booted clean into an Operator account (no administrator access), the DAQ portion of my application would not function. It would not readback correctly. My debugging skills told me to go into MAX and verify the DAQmx tasks and channels. All is required is to expand the (+) icon on the tree to expose the tasks. Then if I go back into my application, it works! Why?
-
Is it possible that the files it is looking for are part of your LV installation? When you save all files to llb, do you include VI.LIB files?
-
I once posted that exact question on Info-LabVIEW and many thought I was crazy. Basically what you are asking for is a web browser built out of LabVIEW G code. Or... do you want NI to build yet another browser out of C code?
-
I assume you want to selectively monitor controls? For example, sometimes you look for a value change and sometimes you ignore it?
This is possible by using dynamic event registration. Without going into too much detail, this allows you to register a control and monitor events on it. When you do not want to monitor events then you would temporarily unregister the control.
I recommend that you investigate the LabVIEW event examples. There are several examples that show you how to do this. Go into your labview example finder in your help. If you have more questions after this then come back and I can help you out. I've used this extensively.
-
It's possible to reduce the size however there is a minimum overhead that must be there. This is a function of the Windows installer. The data.cab file is where all your installed files reside. This is where your *.llb is. The other stuff is required to support running the installer on specific windows platforms. For example, if you run it on Windows 95 or NT then the installer engine must be installed first before the actual install takes place. It's possible that the engine is already there however you don't always know that.
The LabVIEW install builder creates a safe installation so that everything works on any platform. This usually means excessive baggage you don't really need. If you want to manipulate the final size of the install and create a lean install folder then you must go to a third-party application like Installshield.
-
Could I wire a proberty node of the option field instead an enum?
I changed it - in the moment it looks like this - I forgot to add two more boolesch references because I have three options and the new is to show only two things (led...).
But the output of the led's make problems. I can't connect it direct with a tunnel.
Why not? Of course you can connect a control. You already have an enum on the front panel, no? Also, you can leave the property nodes outside or inside the case. Just wire the constants. You can aslo wire the boolean through. For cases that you do not use then you can specify a default case the does nothing.
-
-
-
Well, it is an animated GIF. You can create this with a graphics package that allows you to do this. The makers of Paintshop Pro have a program called Animation Shop. I think it is included as a bundle. It shows your animation as sequential frames. Like a roll of film.
-
I guess the question is, why did NI feel the need to change this behavior. It worked fine for so many years with the old way.
-
-
-
When you first installed XP it probably asked you to create an Administrator account. Can you use this login to get in?
Accessing Controls In SubVI Via Reference Cluster
in LabVIEW General
Posted
You have to use the bundle function on the diagram and wire each control reference control into the bundlw function. I think the problem occurs when you grab the controls and put them into the cluster. You must do this programmatically as I state.