On 25 April 2012 15:44, Kenneth Lerman <[email protected]> wrote:
> A new HAL component could connect to N jog inputs (one for each axis). > In feed hold mode, the joggers would become active. The new component > would pass the jogs as offsets to the various axes and *memorize* the > jogs in the order that they occurred. It would need to know the accel, velocity and position limits for the axes too, and perform at least simple trajectory control. > Since memory is cheap, an arbitrary path could be memorized at > little cost. I don't think that recording the path is necessarily easy either. A decision would need to be made on whether to record timewise or distance-wise. In the former case you use memory indefinitely. In the latter case, how to choose resolution? I don't think kernel memory is all that cheap either, and the component would have to kmalloc the correct amount ahead of time. -- atp The idea that there is no such thing as objective truth is, quite simply, wrong. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
