System/subsystem timing in Labview

[markedwards]

Hello,

I work in development of mechatronic systems, many of which have complex timing requirements for mechanisms that interact with each other.

I have been representing the timing diagrams in Microsoft Project or Excel to get a visualization of what mechs are moving when,for how long and in what order. This allows me to plan the overall system timing which I then code into State Charts to implement.

Is there a better way of representing this type of timing diagram or better being able to plan and run the sequences in LabView?

Many thanks,

Mark.  

[David_B]

It would be helpful to see some examples of how you are currently representing these transitions (a screen shot or attached example) as well as some background information about your use of the StateChart Module to program this application.  It may be that the best solution for you will be to simply start with an annotated StateChart rather than using excel at all if that is to be your first step in development. 

For those unfamiliar:  The StateChart Module is intended to provided that additional layer of abstraction and shorten development time by giving you a tool that both functions in the representation and design phase of the project as well as the actual coding and development.  Your StateChart becomes your program.

[markedwards]

Hi David,

Attached a MS Project snippit. Typically I create this for the timing specification and then come back to it when the design is realized to enter the actual timing. I use state charts to logically step through the sequences, adding delays in the transistions to implement the required timing. So there is a gap between my sequence in MS Project and my implemention in state charts. I thought there may be a way of representing the timing for management demonstration (MS Project is great for that) which can then be executed.

Are there any sequencer design patterns available for Labview?

Thanks.

[David_B]

Not that I'm aware of.  The most visual representation of this that I'm aware of is within our StateChart Module.

[Britoa]

That's quite a neat way to use project.  I never thought about that.  5 stars for giving a unitasking program a secondary skill.

[markedwards]

Exactly!

And that's my point. Laying out the timing in MS Project gives all the team a good idea of what goes on in the system and what the interactions are.

If I represent this information in State Charts all the detail is hidden in the states and it becomes hard to see where the bottlenecks and possible optimisations are.

I'll keep looking for a better way but until then I'll keep knocking out the MS Project representations.

Thanks.