Hello,
I'm finalizing the build of my CNC, which is based on the aluminum ox cnc, but my system has started acting up in a very bad way. The system uses a mach3 compatible motor driver board from china through ebay, and I'm using mach3 as my cnc software. I was routing my spoil board when all of a sudden the motors started jerking around and the planing blade was driven diagonally into the spoil board. I reset the board and computer, and frequently it immediately starts spazzing as soon as it was turned back on. Sometimes, the system doesn't spaz immediately, and the y and z axes work just fine. As soon as I begin moving the x axis, all 4 motors (three axes) begin spazzing out and driving in random directions. My initial thought is that the cheap chinese driver board has messed up. My second thought was maybe the parallel port on my PC (running windows XP) has died (I've heard that these die sometimes). Does anyone have any thoughts? Thanks.
For the record, I've probably run this system for at least 2 hours of programmed cut time before this incident occurred.
I'm finalizing the build of my CNC, which is based on the aluminum ox cnc, but my system has started acting up in a very bad way. The system uses a mach3 compatible motor driver board from china through ebay, and I'm using mach3 as my cnc software. I was routing my spoil board when all of a sudden the motors started jerking around and the planing blade was driven diagonally into the spoil board. I reset the board and computer, and frequently it immediately starts spazzing as soon as it was turned back on. Sometimes, the system doesn't spaz immediately, and the y and z axes work just fine. As soon as I begin moving the x axis, all 4 motors (three axes) begin spazzing out and driving in random directions. My initial thought is that the cheap chinese driver board has messed up. My second thought was maybe the parallel port on my PC (running windows XP) has died (I've heard that these die sometimes). Does anyone have any thoughts? Thanks.
For the record, I've probably run this system for at least 2 hours of programmed cut time before this incident occurred.