Ulrich
-
Posts
35 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Gallery
Posts posted by Ulrich
-
-
-
ZITAT(crelf @ Jun 12 2007, 03:02 PM)
Your colleague is ignorant: LabVIEW allows you to be as close, or as far away, from the hardware as you are comfortable with.You're absolutly right with Labview, but my colleague doesn't want to have it comfortable .
He prefers to program 30 minutes for a XY Graph rather then to have the same result in Labview after 2 minutes
(that's fun with him, we are joking every day)
have a nice weekend
Uli
-
Hi Lorenz,
thanks for hint. I turned it off. Let's see what will happen.
Have a nice day
Uli
-
Hi Lorenz,
thanks for your help!
Does it only occur on boot? no, during boot, while running and during shut down.
If you go to service control center (Start Menu->Control Panel->Administrative tools->services) and start/restart "National Instruments Variable Engine" does it crash then too? No, the service stops and starts again succesfully.
what libs (with variables and/or I\O Servers) do you currently have deployed. You can check with Variable Manager (Tools->Shared Variable->Variable Manager)?
I can see nothing in the variable manager, and we don't use shared variables.
What are the specs of the machines you are seeing the crash on (CPU speed, ram, how many CPUs, winxp?)
the spec of my office PC: CPU:1.8GHz, 1GByte RAM, 1 CPU, WIN2000
the second one is an office PC from my colleague (similar to my PC)
the third is an older Lab PC. All have WIN2000.
Many thanks and have a nice day
-
Hi all,
sometimes we get a mysterious error message (see attachment), which we don't understand.
But still everthing works fine, so the error doesn't really matter. Sometimes the error occurs when we start a PC,
sometimes when the PC is running and somethimes when the PC shuts down. This happend on three PCs. Two have the LV 8.2.1 PDS version and one have only the run time enginge 8.2. I already asked NI. They don't know the error.
Have a nice day
Uli
-
Hello all,
the installation was no problem.
See you
Uli
-
Hi,
my colleague always laughs at LabVIEW. He says that I'm just painting pictures similar to powerpoint foils. He prefers HP Basic where he is "close to the hardware".
I'm glad that LabVIEW is close to the hardware so if have time to program the important things
-
it must only be the PDS peopel who got the nifty carrying case....
Hi,
I have the PDS 8.2 Version with SSP, but I've got no nifty carrying case.
Just the common yellow-white cardboard box.
have a nice day
Ulrich
-
My colleguage and I got our LV 8.20 Versions End of August.
-
After a smooth migration from LabVIEW 7.0 to 8.2 I found out that 8.2's run time engine needs (local) admin rights to install, in contrast with 7.0rte.
In my company, with 100+ users of ready-built LV applications this means a huge overhead to deploy. I was forced to return and stick to LV 7.0 until this problem is solved by NI or otherwise.
Please advice.
Hi Pjotr,
we had the same problem. For LV 8.0 we COPY the whole Run time directory to the local hard disk and also copy the LV exe files in the same directory.
For our applications this works. I hope for you too.
Good luck
Ulrich
-
I have allways thought that you germans wanted it "nicht schnell, aber pl
-
One question I do have - how would I set current boolean states of LEDs based on what is in an array cell? I.e. how would I link an array cell to a boolean indicator?
Hi bwgames,
i hope i understood you and this vi can help you.
have a nice day
Ulrich
-
Hi bwgames,
welcome to lava!!!
"I want to be able to read the serial port and use the info to affect indicators whilst at the same time acting on any changes by the user to the FP."
e.g. you can run a sub VI dynamically for reading the serial port, while the main vi is acting on FP changes.
"(even though it gets horribly complex with ~40 buttons, each one wired to its own case statement - there must be a easier way?)"
You can put all buttons in one case. See the attachment.
hope it's helpful for you
Ulrich
-
Oh - and don't post the same thing twice in different places - it's annoying.
Hi c2r,
the gray background is a bug.
see also
have a nice day
Ulrich
-
the manufacturer was a local one in India , and hasn't given any drivers.
how to go about making one on my own?
Hi prasan,
I hope you have a manual of the positioner where you can find the commands for the remote control. And then use the Serial VIs you'll find unter "Instrument I/O"
good luck
Ulrich
-
EDIT: Any chance Ulrich that you could save the file you posted in version 7.0? I would like to see the other changes you made. Thanks.
Hi Philip,
here it is in LV7.0. I hope you can open it.
have a nice day
Ulrich
-
Hi Philip,
don't hesitate to ask. There are no stupid questions, just stupid answers.
I meant the same thing as ooth.
forgot one thing: Wire the case output directly to the sequence local. The foor loop output will automatically create an array.
(you also can disable the indexing if you don't need it)
Then wire this output to your sequence local and after you measured the voltages save both to an ASCII File.
I attached your main.vi where you can see it. I also made some other changes. I hope they are helpful for you.
your welcome
Ulrich
-
Hi,
here is simple question from a beginner:
How do I add/remove buttons on the same front panel in "real time". Let's say I have a main front panel running, then a condition is met and I would like to offer the user some options. How can I make these new options (buttons) appear on the same front panel (no new dialog).
Any help is much appreciated,
Juan
Hi Juan,
you can create a property node from the buttons with the property "visible" (true/false). This should help.
have a nice day
Ulrich
-
Do I have to create a local variable that points to my array for the input?
Hi Philip,
you can create a "sequence local" (right click on the sequence) and with this you can use the data in a following sequence.
have a nice weekend
Ulrich
Do I have to create a local variable that points to my array for the input?Hi Philip,
you can create a "sequence local" (right click on the sequence) and with this you can use the data in a following sequence.
have a nice weekend
Ulrich
I forgot one thing: Wire the case output directly to the sequence local. The foor loop output will automatically create an array.
(you also can disable the indexing if you don't need it)
see you
Ulrich
-
It would be extremely helpful to include an option to look for only writes or only reads, and that option would pick up on all locals, global references and property nodes at once for that control/indicator.
Hi,
this is great idea!
have a nice day
Ulrich
-
Glad to hear that you've got it working, but there's nothing obvious in your code that calls networked files - unless it's hiding in a hidden frame or a subVI. If you'd like us to look into the problem further, feel free to post your code here.
Hi Crelf,
there is no hidden frame and no subVI is running during the VI is waiting. I attached the main VI. The only thing is to update the front panel. But for this update we don't open any files (I know there are better ways to do this update). Maybe the error is somewhere in our WinXP network scripting?
Download File:post-3940-1154938783.vi
have a nice day
Uli
-
Hello crelf,
sorry for the late response but on friday I wasn't online anymore. You're right, there are many possible reasons for that. We use some dlls in Sub VIs (e.g. Hostname.dll to get the PC name). Communication and data acquiring goes over the GPIB Bus (with VISA). The code is very large (300 VIs). When we get the blue screen only the main VI was running. This is not more than a main menu, waiting which Sub VI the user is choosing. The block diagram of that is posted.
We are doing more tests to figure out the problem. Over the weekend the PC was logged on "local" and there was no blue screen. But normally we need to log on to our network domain.
Right at the moment it looks like the problem is home-made.
Many Thanks
Ulrich
Hi all,
we made a workaround. Log on local and map the network drives.
we don't know the problem, we didn't solved the problem but it works
have a nice day
Ulrich
-
Am I advanced? I don't know, but I'll answer anyway
Sometimes, if they're convenient.
I never prototyped anything with them, except once I played with the Signal Generator a bit. I have used them once or twice in production code. Sometimes they're a little nicer than attaching constants.
Big, unless they're taking too much room. They look nicer than the normal LabView icons.
I see Express VIs as a gimmick. I've never found them especially useful. They offer me very little beyond normal VIs.
Hi,
I don't use Express VIs. Till now I dind't see any advantage of using them (maybe I'm blind :-)
have a nice day
Ulrich
-
Hello!
On the diagram menu, you can find a sub-menu with a disk as icon. In this sub-menu, you can find different VIs than can export data to a text file (simple text file, Comma Separated Value...)
BY!
Hi,
if you have your data in an string array you can use the "Array to Spreadsheet String.vi" (you'll find this in the string menu)
If your data is only numbers you can use the read and write to a spreadsheet file VIs from the File I/O menu (with the disk icon)
Then you can easily import the text file into Excel if you need.
have a nice day
Ulrich
Time Date String convert to time stamp
in LabVIEW General
Posted
This is 8 years old, but still a very useful hint !!!
Many thanks!