01-20-2011 03:14 PM
@SteveChandler wrote:
Try reading a four hundred year old English text or understand someone from the Bayous of Louisiana. "Jeet?" *
Bayous of Louisiana jeet? You mean like "Laissez les bon temps roullez" (not sure about the spelling). Or how about"Zydeco".
Here is another one: When eating crawfish, newbies always get warned, "Don't eat the dead ones".
To make this Labview related, I too have used Labview to write applications outside of the Test and Measurement world. I used to use VB. But now its Labview hands down.
01-20-2011 03:19 PM
I too have used LV as if it is general purpose but ....
The big money is in getting real world meausrements to show up on a screen or a file or controlling something that a human could not keep up with or errors would be bad.
Ben
01-20-2011 04:59 PM
01-21-2011 07:31 AM
@billko wrote:
Sometimes you're unpleasantly surprised when automatic testing reveals out of tolerance conditions that you had missed before. ;)
I know off-topic but taht reminds me off a war story.
A customer had very large complex piece of equipment* sold all over the world that has a lot of comuter control and monitoring. everytime a change was made to the code (no not LV) every function had to be re-tested and verified. This amounted to two engineers sitting in front of the control panel for two days reading off punching in and checking every function.
They asked us to automate the checks so we hooked into the keyboard and watched the screen updates. The automated code did in 45 minutes what had previously taken two days AND while running the first full blown test we discovered that there was a bug in the code (not LV code) that would very quickly display bogus data then quickly over-write it. A human never saw the flaw. The LV code did.
Ben
* I am convince that piece of equipment has touched almost everyones life in one way or another.
01-21-2011 10:43 AM
@Ben wrote:
A human never saw the flaw.
If a bug happens in the forest and nobody notices, did it really matter? :o:D