crelf

Here's a photo of our superhero moderators/admins with the trophy:

Super excited to see everyone tonight!!

+1

I'm in!

noob: DO: Skim through the forum to see if your question has already been answered. Use the search function. You might find a great answer to your question, as well as a bunch of other cool things along the way. DON'T: abuse the PM feature. Only PM people you know personally. If you want to ask a general question, ask it in the forums: you'll get a much bigger cross section of experienced responses, and you won't upset people you PM. Experts: DO: Try remember what it was like when you were first starting out with a technology, Try not to rush to judge newbies, as today's newbies are tomorrow's champions. DON'T: Admonish a newbie on forums. That's not your job, and experts on crusades loose a lot of respect of their peers. If you think a newbie's post is inappropriate in any way, click "Report to Moderator", that's what they're there for.

I've always thought of us here, in the LAVA community, as members of a global independent without-physical-barriers user group. We don't all need to be in the same place to share knowledge, ideas and a little fun, and some of the most insightful and important knowledge I've gained in my career has come from me being a member in this user group right here. Wouldn't it be great for the user group, and all its members, to get a little more love for everything that you've all done here? That's why I'm asking you to take two minutes to head on over to the 5th Annual LUGnut Awards page and nominate LAVA. I'm not going to tell you to nominate us under any particular category, or if you should suggest an addition category to NI, but I'd really appreciate it if you could help all of, together, get a little more recognition for AFAIK an important user group that has arguably done more to shape the independent LabVIEW community that any other resource.

The LabVIEWWiki has a collection of these, compiled from a lot of different sources. Unfortunately, it's down right now, but you can browse from an archive: http://web.archive.org/web/20150531121321/http://labviewwiki.org/LabVIEW_configuration_file

I'd be wary of making a fully customer solution on your own. There are already good resources that can help you deploy and manage systems (and their components), so you can keep control of your test sequences, support files, drivers, etc, without having to design that stuff up front. Ultimately, this isn't a "test" challenge, it's an IT challenge, so I strongly suggest you engage with your company's IT department and ask how they would do it. FWIW: Microsoft System Center is my solution of choice - you can manage systems across multiple sites/domains/companies, group them as like-types, push software updates (sequences, drivers, OS patches, etc), and it gives you a traceable environment so you can audit what system has what, with history (important if you get a recall or a batch of parts coming back for warranty repair).

Looking for a LabVIEW or TestStand contractor for development work or consultancy? I'm available! I'm certified, have a ton of experience, and have very reasonable rates - check out my LinkedIn profile and ping me if you're interested!

Great intro presented by hooovahh at our local user group meeting today: https://decibel.ni.com/content/docs/DOC-46897 Brian Hoover XNodes Samsung.zip

I wasn't quite sure which category to post this in: I know guys like Jack and Jon have been looking into some of the visualization capabilities of other languages and how to extend the LabVIEW IDE with them - check out this cool dependency visualization tool Jon put together: http://www.labviewcraftsmen.com/blog/labview-class-dependency-viewer

So, how did you get on? Did you get what you were looking for?

Don't mark up NI hardware - NI doesn't like it when you do that. They prefer you to have a relationship with them (partner) where they can give you a discount and you sell the HW to the end-customer at lost outside.

With the load option as 0x48, that means your Sub.vi is going to have to be set for shared clone reentrant execution, so I'd say you'll get [3,6,9].

I mostly agree. I'm okay with it, if it's only but a step in the path to true reuse. Great stuff! I still use a VI from that llb on the odd occasion

In the context of the conversation we're having, "data mining" is completely valid, semantically speaking. This made me LOL. For more than one reason

I don't know about hooovahh, but that's not what I meant by mining. Well, not really anyway. Mining, to me, is half way between the "by reference" technique and the formally-released component. It's "hey, this is useful enough to modularize a little for this next project that I'm working on" without doing the formal redesign for ruse process. We have several stages that mined chunks go through before they get to the formally-released stage.

Oh, it was modular enough, it just wasn't aligned enough with our core businesses anymore (the screenshots I shared were of components, there was a top-level framework and UI experience that tied everything together). And a lot of the features had appeared in others' tools, so we left it where it was. LOL, yeah I was wondering who'd be the first to call that out. So yes, the project in this example was, indeed, 98% reuse. Only because I threw together a bunch on internal reuse library and OpenG VIs on an empty block diagram Nice work - I like this! Interesting you mention that: I've had people ask me in the past about what level of complexity and/or how many GOBs that they should be aiming for - which misses the point entirely. They're relative, and that's why I insisted in having the histograms in there - you're not looking for absolute values, you're looking for out-liers. And yes, some of these out-liers can be logically explained away. Broken VIs et al are quantitative attributes, complexity et al are qualitative. Right. Mined-from-previous-projects is one thing, formally-released-components is another. But yes, they're still both reuse. Open source, I doubt it. But... if someone were to release a framework (like ShaunR has), we could probably release a plug-in or two...

I was wading through an old SCC repo today, and stumbled upon some of our old tools - the ones that existed before VI Analyzer, execution trace toolkits, complexity metrics, Requirements Gateway, et al. Here's a few screenshots for those that have been in the LabVIEW world long enough to remember the VISTA offerings from V I Engineering, in the days of old - enjoy a trip down memory lane!

We're looking for a Business Development Manager. Think you've got the right stuff? Join the VI family! https://www.linkedin.com/jobs2/view/65604086?trk=vsrp_jobs_res_name&trkInfo=VSRPsearchId%3A4186423671438293337816%2CVSRPtargetId%3A65604086%2CVSRPcmpt%3Aprimary

We're looking for a Test Software and Integration Engineer. Think you've got the right stuff? Join the VI family! https://www.linkedin.com/jobs2/view/64695184?trk=vsrp_jobs_res_name&trkInfo=VSRPsearchId%3A4186423671438293337816%2CVSRPtargetId%3A64695184%2CVSRPcmpt%3Aprimary

Well that's kinda cool... http://www.banggood.com/DSO068-DIY-Oscilloscope-Kit-With-Digital-Storage-Frequency-Meter-ATmega64-AVR-Microcontrol-p-981017.html