Hmmm. Left the machine powered up (with the e-stop depressed for safety) and came back to find the X axis unresponsive. The drive was still functional (leadscrew held firmly in position) and the controller was trying to drive it but nothing doing.
Connected up the comms software and it seemed to have defaulted to RS232 rather than the step/dir scheme it had been running. How the f*ck can it change that?? The comms lead wasn't even connect up.
Changed it back and all is good again. But when can I expect this to happen again?
For the record, here's the settings screen for both X and Y axes:
Not unduly impressed by this.....
Retrofitting 1983 Shizuoka AN-SB CNC milling machine, Bridgeport mill, Colchester Bantam lathe and 1982 Tree UP-1000 CNC lathe with modern controls - and other workshop stuff
Subscribe to:
Post Comments (Atom)
Improving homing accuracy on the Linuxcnc Bantam lathe?
Recently I've been messing with the CNC-converted Bantam lathe. This uses the Probe Basic Lathe GUI and I've been beta testing an ad...
-
Setting up the servo tuning(?) software: Having spent a couple of hours yesterday pratting about with the PID controllers for the X and Z ax...
-
Right, so having gone through the motions with the X axis (cross slide), I should now be able to set up the Z axis (longitudinal) encoder an...
-
WTF? This must the the definitive rabbit hole. I've been aiming to attempt a modification to the existing post processor that is provid...
No comments:
Post a Comment