Eric H. Johnson wrote: > Alex, John, > > Ok, it is obvious now. The missing symbols were kinematicsType, > kinematicsInverse, and kinematicsForward, which all are defined on the > subsequent line when exported with halcmd save. Specifically: > loadrt trivkins > > Thus one can't do a halcmd save and then load the saved text with halcmd > source, without checking the ordering, although some basic ordering is > performed by the way it groups things into sections. >
Ah - you are dealing with a special case. Regular HAL modules don't have any dependencies on each other. You can load them in any order, then once all are loaded you connect the pins together with signals. The kinematics code isn't a regular HAL component - it doesn't connect with pins, instead it uses function calls. We made it look like a HAL component so it could be loaded and used like one without having to recompile when you change kinematics. But there is a dependency between motmod and kins and they need to be loaded in the right order. Regards, John Kasunich ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
