crelf

When you say "read and log", I assume you don't mean you're reading from one database and logging the data to another, right?

We've had success reading that number of channels, but it often depends on the hardware. If you can get the data from the hardware in that time, then you're probably okay (the database writes aren't too timeconsuming).

Using your toolkit, you could write a VIE Hardware Explorer plugin pretty easily. We already have a plugin that supports NI DAQ hardware, maybe it makes sense to make another one that allows the use to add and configure channels (without allowing them to delete or modify existing ones).

VIE Hardware Explorer Overview.pdf

"An error occured loading VI 'Demo VI Using Globals.vi'. LabVIEW error code 6: Could not load bloack diagram." - LabVIEW 2010.

Wait, which controls are you talking about?

Please post any zazzle coupons you know of! I just found one that gives you $5 off t-shirts: SAYITTSHIRTS

Like previous years, we'll be having lucky-door prizes at the BBQ, so if you've got anything you'd like to offer up to be given away on the night please bring it with you. It doesn't have to be anything super awesome (previous prizes include anything from a Wii to Microsoft Zunes to signed copies of LabVIEW 2.0 user manuals, right down to stickers, pens and mousepads). When we draw your tiem(s) we'll give you a quick shout-out, and if it's a big prize we'll let you draw it.

See y'all in about a month!

I walked last year - the "Block Diagram Party" (groan) is on in the expo floor before the party, so grab yourself a beer there, then wander over (the sun's going down, so it's relatively cool by then).

Thanks so much for all the entries - we had some really good ones this year - well done to you all!

Congratulations to the winner of this year's competition: vugie - your design will adorn the LAVA 2011 T-Shirt!

New to the LAVAStore, the hottest item in this summer's* catalog has to be the fabulously-fetching LAVA 2011 T-Shirt!

Our very own vugie has expanded his portfolio with the height of this season's Geek Chic, with a t-shirts that's modern, yet stylish, and says "yes!" to me!

What's cooler than a hot LAVA flow? A hot LAVA *data*flow, fo course! Be instantly recognized as part of the LAVA community by sporting this stylish flow of nodes, complete with all of your favorites! Not only is this the hottest new design, it's significantly cheaper than last year's model, so now you have no excuse to turn up to the LAVA/OpenG BBQ as an individual (yes, we are all individuals!)

Retro is back in style. Enjoy this vintage-inspired ringer Tee. The shirt body is light-colored with contrasting neckline and sleeve bands. Made from 159g, pre-shrunk, 100% heavyweight cotton with a seamless collar and double-needle stitched neckline, bottom and sleeve hems. Made with 100 percent pre-washed cotton and provided in sizes from small up to extra extra large (we all love our Texan BBQ), this classic ringer t-shirt is a trendy old-school shirt for guys and gals. This one-of-kind tshirt is sewn with double stitching and is provided in whitered in addition to tons of other colors that will complement vugie's design. This t-shirt is be carefully made with a highly-developed printing process that makes long lasting designs that are superior in quality. All in all, this LAVA t-shirt displays an awesome cleverness which proves that it is a must-own tee for any time of year!

"Where can I get a dozen of these?!?!", I hear you scream? "Right here in the LAVAStore!!!!", I scream back.

* or winter's, depending on which hemiphere you're in.

Thanks to all those who subitted entries (and those who later withdrew them! ) - the competition is now closed, and judging has begun!

Building on Tom O's post, you can then update MAX programmatically to add virtual channels linked to the found card - using this method separates your setup code from your application.

Top job Jon - way to go!

Hmmm - I've never come up against this before... I wonder if you call the IEngine.ShutDown method then the IEngine.GetEngine method? It seems a little unintuative, but the latter is a method and not a property, so it might start the engine if one doesn't already exist?

Yep - the Austin Convention Center will have free wifi, and I've found it to be pretty decent in the past. It was a little shaky a few years ago (when the iPhone first became popular, go figure), but they've upgraded the system since.

Only 1 week to go before entries close - so get your designin' on people!

I agree - if I can build an exe with a version number <1, then I should be able to do the same with an installer.

I hate to say it, but if you don't get the dialog when you press ctrl+e, then you don't have any diagrams. It looks like the your ex-developer stripped them out. There are many motivations to do this, not all of them nefarious: it's sometimes a good idea when distributing code. Your least painful route might be to contact the develop to see if they have a backup with the diagrams in place.

Can you upload a vi here and we'll take a look at it to confirm?

Are you working locally? If so, this might help.

I do not share this opinion, but vox populi - vox Dei.

Nec audiendi qui solent dicere, Vox populi, vox Dei, quum tumultuositas vulgi semper insaniae proxima sit.

Done. You can use the report to moderator for anything you want mods to see.

For what? Why did you choose it? What has been your experince with it?

It's where we host the OpenG project. Never had any issues with it - we push it around a fair bit and it's always worked fine.

I've always used sourceforge.

A reminder that time's running out people - get your entries in!

We use the State Pattern as described by the Gang of Four. In this pattern we would never create a macro or queue of states, although we can and do create macros of triggers (could be commands) that we can invoke serially on the statemachine. Specifying a series of states would be antithtetical to the concept of a statemachine, I think.

One of the big problems I had with QSMs is that they don't really stay in any one 'state.' Even when there is no transition to another state the SM is exiting and re-entering the same state. Same thing, you say? Not when you start adding more strictly defined behaviors to your state machine.... When you look at a state diagram the arrows not only define the transitions the SM does make, but also defines the transitions the SM is allowed to make. The SM defines and restricts it's own behavior; it doesn't depend on an external entity to know details about what states are "valid" to call from its current state. If there's no arrow, the SM simply won't transition from one to the other regardless of the command it received, because it's an invalid command. Leaving that responsibility to the external entity is error prone.

For the benefit of Dannyt and others reading, "Queued State Machines" such as the JKI state machine are misnamed in that they are not actually state machines. True state machines are a different concept, and are what Paul_at_Lowell and Daklu are talking about. QSMs are more like queued command or queued operation machines, and thus the concept of a "macro" set of commands applies.

Excellent topic guys. I agree that using the term QSM is a misnomer, and we should use QMH (queued message handler) or the like instead.

Did you try this?