On 6/1/2015 11:28 AM, John Kasunich wrote: > > On Mon, Jun 1, 2015, at 11:06 AM, Ralph Stirling wrote: >> I've been puzzling for a long time how one would create sequential state >> machines in hal logic, and it finally dawned on me that you guys are doing >> that in things like pyvcp or axis. It would be nice if hal itself could >> have a >> good mechanism for defining states and state transition logic. Have I >> missed something? >> >> -- Ralph > "hal itself" is really just a framework for interconnecting components. It > is the components that do the work. We have simple components like > and gates and summers, medium components like software step > generators and software encoder counters, hardware drivers like parport > and Mesa, and we have very complex components like the LinuxCNC > motion controller and the Classicladder PLC. > > Classicladder can certainly do state machines. > > A component specifically designed to execute state machines would be > a nice addition. I think the biggest problem is probably coming up with a > way to specify the states and transitions, and passing that information to > the component. >
Oh yes. Ladder is the industrial standard for state machine logic in the US. There are lot of examples of state machine programming out there in Python etc. The trick is writing the software in a way that the state logic can be debugged. Dave --- This email has been checked for viruses by Avast antivirus software. http://www.avast.com ------------------------------------------------------------------------------ _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
