PaulG.

QUOTE (hooovahh @ Jan 13 2009, 12:50 PM)

Yeah I try doing http://letmegooglethatforyou.com/?q=site%3Awww.ni.com+make+executable+labview' target="_blank">this instead. This is the closest I can be to typing with sarcasm.

:thumbup:

We should come up with our own "Most Dangerous LabVIEW Programming Mistakes". I would add: Failing to properly close references, using stacked sequences, using globals, messing with a fellow team member's code without permission ...

Try over here on this thread.

Back in the day of a few size choices of CRT monitors there used to be a "standard" (I don't even remember what it was it was so long ago) but not any more. There are simply too many LCD's with different sizes and resolutions now days. If there is a standard it's "keep the block diagram on one screen".

QUOTE (crelf @ Dec 7 2008, 06:37 PM)

:!: This topic looks to be shaping up to be a possible hot-button topic. With that in mind, I wanted to remind everyone that if you find a post and/or thread inappropriate, our Forum Guidelines call for you to report it to the administrator or a moderator by clicking on the "! REPORT" button next to the post that you find questionable. Replying such directly in the thread is against our Forum Guidelines, and is grounds for temporary account suspension.

Done. Alpha is bad enough.

QUOTE (BobHamburger @ Dec 7 2008, 03:39 PM)

Two sage words of advice for you: State Machine.

Look it up. Learn it, live it, love it.

:thumbup:

State machines are the Holy Grail of programming, grasshopper ... in any programming language. :ninja:

GodSpeed, Norm. Kudos. Wish you nothing but the best.

5.1?! That's the version of LV that I first learned 10 years ago.

It has been my experience that NI will give you every older version of LV up to your licensed version for this very reason. Contact your local sales rep.

I've built applications that used up to 128 serial ports with no problem. But you will need a multiport serial device. But they are expensive. Take a look at the "serial concentrator" crelf mentioned then contact him. Good luck. :thumbup:

In my experience I have found that coming in 10 minutes early to get everything up and running works wonders.

Thanks for sharing. Very funny. And to think I get upset over password-protected VI's.

You will probably spend at least one man day (or more) perfecting your report. NI Report Generator SUCKS. :thumbdown:

QUOTE (BrokenArrow @ Nov 16 2008, 12:53 PM)

I really can't see what you can do with a Semaphore that you couldn't do with a local, global, or a Notifier. Does anyone here commonly use them?

I've learned to use User/Registered events in lieu of semaphores, locals, globals, notifiers, etc. Simple and elegant.

Lately I've been doing a some equipment safety check coding. As long as there are operators there will be operator errors - and in our case a possible loss of an expensive UUT and wasted time and data if the operator makes a mistake. I'm sure there are dozens of ways to do it, and my application isn't that complicated, but in this situation comparisons and one button dialog error messages ("Error: test position already in use.") where the test software will not continue until the error is corrected seems to be working very well.

QUOTE (crelf @ Oct 18 2008, 03:08 PM)

That said, password protecting the code that you distribute to protect your IP can be sensible (as long as you http://thinkinging.com/2007/08/19/password-protecting-vis-is-security-through-obscurity/' rel='nofollow' target="_blank">understand the risks and limitations of doing so).

Thanks mate. :thumbup:

QUOTE (km4hr @ Oct 17 2008, 10:22 AM)

IP security is not my goal. I'm building a LabVIEW application that will be used by students at the university where I work as undergraduate lab manager.

The students will take apart (ie break) any LabVIEW application I create if it's easy to do so. I just want to reduce the chaos by making it a little harder for students to modify my work.

jgcode,

Thanks for your support. I've used enough forums to realize that there will always be a few paulg's around. It's no big deal. The vast majority of LAVA posters are very generous with their knowledge.

thanks again,

km4hr

I screwed up. Big time. I won't apologize for what I said, but all of you could have done without my sarcasm and the ugly way I said it. I was tired and grumpy, but that is no excuse for the lack of respect I showed all of you, especially you, km4hr. For that I sincerely apologize for the way I said it and ask for yours and everyone else's forgiveness.

What I meant to say:

Password-locked LV code is real pet peeve of mine. Unless you intend to sell your source code as "intellectual property" passwords are almost always a very bad idea. The code you lock with a password invariably is the code someone else will inherit and maintain. Years ago I inherited a huge application where numerous, critical sub-VI's were password-protected. Just a few weeks ago I wanted to look at that code in my archives to help me with an issue I was dealing with at the time. Lo and behold I had forgotten the password. If you are concerned with someone messing around with your code you have far more serious issues in your working environment and a password would be nothing more than a Band-Aid. Regarding a thumb drive: everything I do I save to my thumb drive at the end of every single day. Its main purpose is to take my work home, but also, if someone changes my code I always have my version ready to replace it.

QUOTE (km4hr @ Oct 15 2008, 10:44 PM)

Aspiring labview programmer wants to know how to turn a completed VI into an application that can be run by others without leaving it wide open to modification. Is this possible? Is there an "execute-only" mode?

km4hr

ForCryinOutLoud! WTH are we doing here, guys? It's LabVIEW, not "labview". And if KM4HR wants to "protect" precious intellectual property ... ... just tell him/her to save their code onto their own personal thumbdrive.

What are we doing here?? And why do I keep coming here??

It's fun watching a master work. I don't get much of that.

And a pretty good sales pitch for Jing. That might be useful.

If you can no longer get in touch with the manufacturer for their recommendation the safe bet would be to get them re-certified. An ISO auditor can always ask: "How do you know the targets are still calibrated"? Can you re-certify them internally with another certified instrument?

QUOTE (neB @ Oct 10 2008, 07:11 AM)

[OT]

... Tim Burton is doing a version of "Alice In Wonderland". provided it isn't a musical, that sounds promising.

Ben

I would pay to see that. :thumbup:

QUOTE (mballa @ Sep 26 2008, 10:41 AM)

Here is the sequence I use to put my Main or dialog Front panels in place at runtime.

here is a demo vi to show how it works

Download File:post-584-1222440051.zip

Well done. I'll be using this a lot. :thumbup:

Are you including your called subVI in your build specifications, i.e. you have your startup vi but your called VI needs to be under the "always included".

QUOTE (jones @ Sep 24 2008, 04:49 PM)

I realize this is probably impossible, but I have inherited a LabVIEW EXE and I don't have the source code...is there any way to convert this back to LV code or even editable C code?

Thanks, Chip

No.

QUOTE (Michael_Aivaliotis @ Sep 23 2008, 02:09 AM)

Watch Michael Moore's new movie for free on blip.tv

http://slackeruprising.com/

You couldn't pay me to watch a Michael Moore film. :thumbdown:

Anything that allows us to make better looking front panels is a great idea. Working with control clusters is one of the least favorite parts of my job, simply because it is extremely difficult to get things sized and aligned properly. It has to be perfect. I have a lot of arrays of clusters and their sizes change during runtime. If everything isn't aligned and sized exactly right the FP looks like crap. And that is what the customer sees! I would think NI would realize this and work a little harder to give us the tools to make LV a little "sexier". Not all of our customers are engineers.