Leaderboard

Name: UML2LV State Machin Compiler Submitter: Black Pearl Submitted: 30 Dec 2009 File Updated: 03 Jan 2011 Category: *Uncertified* LabVIEW Version: 7.1 License Type: BSD (Most common) This is a toolkit to convert a state diagram designed with the editor dia into a LabVIEW state machine. Warning: This uses Scripting: So be aware of dragons, black holes, rusty nails and other monsters. I've only tested it in LV 7.1., got a crash every 2 hours... Bugs and workarounds in newer LV versions welcomed. Crashes in 8.5. Found the CAR (# 4CJFKTCS)). Edit: Fixed in V 1.0.1 Basic Operation *************** Create an uml Chart in Dia (it is OpenSource too). Compile it into a LabVIEW state machine (this will generate an enum based state machine with .vi and States.ctl for the TypeDefed Enum). Code the States. Getting started *************** * You will need to have several OpenG packages installed. Dependencies: appcontrol, file, variantconfig. In order to install these, you need to get the VI package manager from: http://jkisoft.com/vipm/download/ * For users of LV 7.x you need to get the TRefTraverse.llb from NI: http://decibel.ni.co...t/docs/DOC-5091 From 8.0 onward they are located under vi.lib\utility Propably you need to fix the linking from the main vi * You will need to download Dia: http://live.gnome.org/Dia Customizing *********** * In the Folder LV Scripting you will find the template 'State Machine Prototype Template.vit'. You can modify this within limits to change the state machine that will be generated. * There is a lot of Documentation with the Code: Check out the documentation folder with the 'Tree VIs' and the uml diagrams (they are surprisingly also made with dia) * If you have questions, ideas or found a bug, please do not hesitate to contact me! You can do so via PM on LavaG or via my private email on the BD of the About.vi V 1.0.1: * Fixed a bug in error handling (Error Handler Close.vi) * Workaround for the 8.5 crash * Support for changed Name of CaseSelect * Started to add support for StarUML Happy New Year Click here to download this file

Another method is you can overlay a boolean array (flat square classic buttons work best) where the booleans are transparent except for the true state border colour. Then you just use the number to boolean array primitive to set one or more booleans "True" for the value or values you want to highlight in the main array. This will create a border around the value. But if you move it behind your array and make your array transparent, you can also make the boolean array "True" state bg coloured and it will look like you changed the background.

Here's another reason I don't visit IE very much: There are 1400+ ideas, and only 1 is "In Development". There are 20+ ideas with over 150 kudos. All marked "New". Most over a year old. So there doesn't seem to be a lot of point in submitting ideas or voting on them. Yes, I know 10 or so ideas were implimented in LV2010. But that left a whole lot of ideas with a whole lot of user support behind. In reality, I can't image the LV user base is really being ignored like this. Maybe the "Status" field needs to be updated more often? Or maybe there need to be more options than just "In Development" and "Being Ignored" "New"? Maybe "Under Consideration"? "Not in a Million Years"? Just more feedback, and updated more often, as to whether or not NI is actually paying attention to what gets posted in IE.

Roadmap (unsorted): * Extending the set of verification plugins * Loading/Parsing for StarUML/XMI * Creation of String based State Machines * Make it available for newer LV versions (see this scripting question) * Handling of orthogonal states * Converting Notes to Comments on BD * Converting Transition Events/Guards to whatever * Write an easy tutorial Felix