PaulG.
-
Posts
822 -
Joined
-
Last visited
-
Days Won
22
Content Type
Profiles
Forums
Downloads
Gallery
Posts posted by PaulG.
-
-
-
Edgar Alan Poe lives!
-
That made about as much sense as this entire thread. But I love the valediction: "All here. Bye". :laugh:
-
Relying on my cats to remotely control my home would be more reliable than Twitter.
-
QUOTE (MicrochipHo @ May 19 2008, 04:38 PM)
Ok, I have three indicators of arrays on the front panel. I know how to hide them on the front panel by right clicking them and pressing "hide indicator" but I would like to have the user be able to choose to hide them thru a boolean. Is there a way thru the property nodes?Yes. On the block diagram right-click the control>create>property node>visible. Write to that node.
-
-
My experience with my 17" laptop was the same as yours. My only difficulty moving down to the 15" laptop provided by my company was some eyestrain after long hours of coding. I found a good optometrist and he set me up with a fine-tuned pair of computer glasses. My 15" is fine now.
Second benefit of the smaller 15": it keeps your block diagrams at a reasonable size for someone else who might "inherit" your code. I don't know about you but I find block diagrams filling up 1680x1050 screen sizes really annoying.
-
-
Just downloaded it and have been playing with it for nearly an hour. SWEET. I've had a lot of fun with Celestia and Google Sky but I would have paid money for something like this. :thumbup:
-
I've never done anything like this in a LV/Windows environment, but did it all the time years ago with dedicated DEC (dating myself) mainframes and image processing equipment. Determinism in this application would simply being able to prove that when you wanted to acquire images you could do so at a specific time and at specific intervals. That part is easy. What would be more difficult would be doing this in a non-RT, Windows environment. I have done deterministic applications in Windows, but the hardware was set up for it. In the case of my DAQ board the board itself had "bus mastering" and I had a deep enough memory that when the trigger was activated the board acquired data and took over the bus. In between scans the memory downloaded (deterministic data) and the board got ready to scan again.
This same principle could be applied to image acquisition. When you trigger the camera to acquire images all you need to know is that the camera is acquiring the images exactly when you tell it to. Now how many images and at what rate I can't be much help since I'm not too familiar with the latest and greatest technology.
Keep us posted, tho. I would love to see what is out there nowadays and what you come up with. :thumbup:
I miss image processing. (sigh)
-
QUOTE (Gary Rubin @ May 15 2008, 10:48 AM)
My experience is that these are usually so poorly written (i.e. overuse of sequence structures) that we end up rewriting them amost from scratch anyway. The Labview SDK's that I've used are often only useful as examples to show the order in which dll functions should be called and how their inputs need to be formatted.My experience as well. That's why they are called "software development kits". Kind of like model kits we built as kids. You gotta do a lot of cutting and fitting and gluing.
-
QUOTE (Michael_Aivaliotis @ May 15 2008, 03:12 AM)
... "LabVIEW SDK", now I'm really laughing out loud!!! HAHA.LabVIEW SDK: ActiveX, dll's and/or C code drivers written by the manufacturer wrapped in LV Vi's. They usually include "example" programs demonstrating most of the functionality of the hardware along with full documentation*. They cost around $200 - $300. And laugh only after you try to do something like this by yourself without a "LabVIEW SKD".
*I consider myself blessed to get basic documentation from a peer working on the same frackin' project.
-
:laugh:
But seriously folks, to me a driver is a piece of code that allows me to use LabVIEW to interface relatively easily with a piece of hardware. A VI can indeed be called a "driver". Many companies sell LabVIEW SDK's with their equipment. They contain vi's that contain the dll's or the CIN's or whatever that allow you to communicate and control their hardware. That to me would be a "driver" VI. But more accurately I would call it an xyzdeviceInterface.vi. Not a driver. The actual dll or C code is the "driver". Or am I full of pixie dust?
-
-
Yes. Some joysticks are better than others. I've seen the same errors with a $50 Logitech "gaming" joystick but not with a $300 industrial grade joystick. Industrials have extra circuitry that generates a true "0" when in neutral along with added robustness and waterproofing. It all depends on what you need it to do. If you're just gaming the Logitech is probably fine. But if you're looking at ultrasonic transducer signals with fluids getting splashed all over the place you need to spend some money.
-
Another option is to create your vi documentation in Word and save as a web page (.htm file). Then link to it as the Help path under vi properties>documentation. The Detailed help link in the Context help window is a link to the document. Click on the link and the document will come up in your web browser. Since it is now a .htm file I don't think you will run into size restrictions. Also, while the vi is running, this document will come up in the browser when the operator presses the F1 key.
-
I usually save the work-from-home days for snow days. Nothing better than my sheepskin slippers, endless pots of coffee and my XM sans headphones while the lunatics are playing bumper-SUV's on the freeway.
-
-
From the guy's website:"... Big news. We have landed National Instruments as a sponsor ..."
That would exlain the LabVIEW hard hat.
Why didn't you just give him a National Instruments t-shirt? 
-
QUOTE (Michael_Aivaliotis @ Apr 30 2008, 05:03 PM)
Was that a Mac user he pulled onto the stage to dance with him?
This is typical internal stuff in many corporations. Pump up the employees!
I have been part of internal corporate cheerleading silliness myself (I was a "prop man" for a "play" ... our product was R2D2, my boss was "Hahns Olo" ... never mind) for a company I loved working for. Maybe I was a little too harsh.
-
-
He makes some good points, but life is balance, Michaelson. I love my work but sometimes the last thing I want to see waiting for me at home is a VI, and the first thing I want to see is that "mindless" episode of Lost I missed last night.
-
-
Considering recent events ...
Don't know if I should laugh myself silly ... or put a gun to my PC.
Right-click without mouse
in LAVA Lounge
Posted
Is there any way to duplicate a right-click of a mouse from the keyboard? In GotoMeeting right-click doesn't work. Really frustrating working remotely. It can be done on a Mac, but I can't seem to find it for Windows, let alone in LV.