Originally Posted by project5k  this is true, but i figure it this way. a properly written set of code, shouldnt cause crashes, and secondly you should have an estop button handy thats tied into your control software.
not to mention that this mill is acting as a sort of test bed for the router i'm building.. and it will be big, well, bigger than the mill anyway... so with what i've learned with this about speeds, and whatnot, when i get back to my router, i'll have that much more figured out. I'm also planning to use the same computer, and drivers, to run both my mill and the table router, at different times ofcourse, but i dont see the need to duplicate thoes components right now, i'll never need to use them both at the same time. |
"you should have an estop button handy thats tied into your control software" - Actually, that's very bad practice. The E-Stop should act as directly as possible on the motor drives themselves, and NOT be dependant on software. It's a good idea to *also* feed an E-stop signal to the software to notify it that the drives have been disabled, but you do not want to be dependant on software (which may have crashed and be the reason you NEED to E-stop) to be required to actually stop the machine.
Regards,
Ray L.