Originally Posted by
JayneV
I understand now. The motion controller takes care of all the critical timing and signals to the motors. It also optimises the gcode to create the actual real life path followed by the tool based on user settings for desired tolerance and speed. The computer is basically the user interface for the machine and keeps the buffer memory topped up for the motion controller to use. So as long as that buffer doesn’t become empty, the motion controller will happily continue to do its thing. This seems like a superior arrangement than one where the computer performs the role of motion controller as well. Does that all sound about right?
Peter, I read a little about path tolerance in the LinuxCNC manual. I’m sure the concept is the same across all controllers. I assume this is how machine limitations are handled when transferring from the ideal CAD/CAM world to the real world, like the acceleration limits of the machine. And different machines would have different solutions to the same problem?
Mactec54, is the UC100 the motion controller hardware used by Mach3 or is it a hardware interface to connect a computer to various brand motion controllers?
Thank you everyone for all of your help. It is all so very helpful to help me have a better understanding of CNC machine construction and their controlling electronics.
Jayne