Cmal

QUOTE (CooLDuDe @ Apr 30 2009, 08:02 AM) CooLDuDe, I assume that you are using the Control Design and Simulation Module, and you are implementing a state space model in a Simulation Loop (If you aren't, please attach an example of what you are trying to do). The 'State-Space' Simulation block returns both the 'output' (y) and the 'state' (x). So you should be able to simply use the 'state x(k)' terminal. You mentioned that you want to obtain xdot. Note that this is the derivative of the states vector (x), so you would need to use a derivative block to get xdot. Chris M

Here are some of my thoughts on projects that I hope will help make a believer of you: One of the nice things about the project (in my opinion) is that all VIs are loaded into memory when a project is loaded. This helps ensure that there are no missing VIs, and it has saved me a lot of confusion more than a few times. The project integrates nicely with source code control. You can see which VIs are checked out, or which ones haven't been added to SCC from the project window. Once again, this has saved me the pain of accidentally creating VIs and forgetting to submit them the SCC. Auto-populating folders are not required. I personally use virtual folders instead. If you ever decide to use native LabVIEW classes (and you should), then the project is pretty much required. The same goes for XControls, Shared Variables, and many more LabVIEW features that don't come to mind right now. Chris M

QUOTE (crelf @ Mar 2 2009, 04:24 PM) If you have a chessboard object, and its private data includes objects of other classes, then you could simply wire the chessboard object to a datalog file. When you read from the datalog file, it will load all of the data that was saved, including the other classes included in chessboard. Datalog files work really well with classes. I may not have completely understood your question, so let me know if this is what you are looking for. Chris M

QUOTE (Antoine @ Jun 2 2008, 09:00 AM) I've been a fan of it for a while, and it's good to see someone else doing the problems with LabVIEW. Just out of curiosity, how have you been handling the questions that require (or encourage) using big integers? For example, try to find 1000! in LabVIEW. Chris M

QUOTE (Eugen Graf @ Apr 15 2008, 08:41 AM) Eugen, One important thing to note about LVOOP is that classes are passed by value, not by reference. So, if you branch a wire containing a LabVIEW class you will then have two separate objects of that class, and changing one will not affect the other. It helps to think of class objects as clusters with added functionality, so they obey dataflow just like anything else in LabVIEW. If you want to create classes that behave more like reference objects, a trick I've found useful is to create "Reference" classes that contain a single-element queue reference to each "Value" class. There's an example that shows how to do this in the Example Finder (browse to Fundamentals >> Object-Oriented >> ReferenceObject.lvproj). Here's a document that explains a lot more about how classes work in LabVIEW: http://zone.ni.com/devzone/cda/tut/p/id/3574 -Chris

Take a look at the latest version! http://www.break.com/index/more-video-of-l...obotic-dog.html Chris

QUOTE(JoeLabview @ Nov 29 2007, 11:52 AM) RayR, The ability to close an array of references was introduced in LabVIEW 8.5. To do this in earlier versions, you will need to use a For loop. Chris M

QUOTE(Eugen Graf @ Sep 6 2007, 10:32 AM) The "Message" event case is sending a True constant to stop the upper loop. Is there any reason you're stopping the upper loop on the Message event? Chris

QUOTE(Nullllll @ Jun 26 2007, 03:51 AM) Nullllll, I would recommend not using the Stop primitive in the case where the wrong password is selected. This is equivalent to pressing the Abort button, which should really never be used unless your program hangs unexpectedly. A better way to do things would be to simply let your program finish without going into any other cases. Chris M