my 6040 experience (yeah, and problems) so far

[EddyCurrent]

Using the red LED's on the drivers as diagnostics, what happens when everthing is connected apart from all the motors ? i.e. just unplug all the motrs, does the fault still happen ? DO NOT unplug them with power on, it will probably blow the drivers.

[jimbo_cnc]

The LEDs behave the same with no motors connected (there was just 1 connected in the video)

[EddyCurrent]

Did you try a different computer ? Is it currently a desktop or laptop ?

[jimbo_cnc]

new findings: forget what I thought before about the drivers all being equal.

When I disconnect the inputs and outputs from the non-used drivers (easy with plug in modules :) ) I find that I only get the malfunctions when using driver2, drivers 1 and 3 can't be made to fault by pressing the jogs on the other axes.

I will go run this simple test on the BOB X and Z outputs in a bit (if driver2 doesn't fault on the X or Z axis then the BOB is also involved in the problem).

[EddyCurrent]

Obvious but it's got to be said, make sure all the drivers have the same settings/links re. this manual (which I guess will be the right one ?) http://www.leadshine.com/UploadFile/Down/M542d.pdf
Also make sure any wiring is well clear of the Enable pins.

[JAZZCNC]

This looks very much like Keyboard trouble so Try another keyboard.!!

Also one thing to try is another parallel port cable. Did this one come with the machine or is it one you've sourced.? I've seen many weird things like this happen and it be the parallel port cable.

Do all the axis move ok with G-code commands.

Also where did you get Mach3 from did it come with the machine.? Wgat version number is it.? You'll find it in the help under about.!

[EddyCurrent]

Yes that's why I asked about another computer, also is the BOB powered by USB only or does it have a 12/24v supply ?

[jimbo_cnc]

dip switches are all the same (I adjusted them from 16micro steps to 8 yesterday).

Mach3 is latest version from Mach3 website.

Will try a different cable (I'd like to dismiss this, but my given one failure of deduction already I'm more open to testing).


I got the graunchy sound (which I thought was ballnut, but now think it is motor caused) also when using Gcode. I haven't cut anything yet so don't know about circles.

I just ran my tests using the X and Z outputs from the BOB (alone with no other connection) and got the same result, ie the fault only occurs when using driver2. different output from BOB also means different keyboard key and different pin on parallel port, so tends to rule those out as cause.

Defect appears to be in driver2 and maybe also BOB? I can't work out how pressing eg Y axis (with no driver connected) can cause problem on X axis, other than the BOB also being at fault.

I'm about to put the gantry back on and try driving X and Y using drivers 1 and 3. Which hopefully should work.

[jimbo_cnc]

I almost don't want to mention this, using driver1 (a supposed good one) I did an extended test for the graunchy sound, after about 5mins of up and down (still just the long axis, no gantry) it started to make a bit of a noise.

This leads me to think the ballnut is fine and the noise is related to the drive problem. Driver2 starts to breakdown(?) quickly, Driver1 breaks down after longer time. I don't know what I mean by break down, maybe a heat thing? (I'll put my hand on the heatsink next time).