Hi,
I have built my own 3d machine
Due to resonance at certain speeds i wanted to change from TB6600 drivers to DM542T drivers for the X/Y axes.
With the TB6600 drivers everything was working as expected (except for resonance at the specific speeds).
With the DM542T on the X axis (only have one DM542T driver at the moment), it works exactly as expected when the micro stepping is set to 800 (4).
When i say exactly as expected, i mean that the axis moves normally, and if i move, from the front panel, after homing, i can move it away from hp, back and forth, and when i return it to the hp, it will exactly (0.1mm) trigger the hp sensor. So home = hp sensor on, move 0.1mm = hp sensor off, whizz it around at various front panel dictated movements and return to hp which is activated when i move the last step of 0.1mm to 0 position.
But, when i change the micro stepping to 400 (2), it will work exactly as expected only if i do 1 click at a time, of the front panel encoder, to move it 1x 10mm, 1x 1mm, or 1 x 0.1mm. If i rotate the encoder so that it will move say 6 x 1mm in one movement, then it will miss steps. This problem happens both ways (ie "fast" movements left and right). Again with single rotary clicks it is good.
I have tried reducing the speed it moves from the front panel, reducing the accerleration, have tried min and max motor currents on the DM542T - all without success.
I am thinking that because it works reliably at 800 (micro step 4) it cannot be anything except a weird DM542T problem ???
This problem also happens from Pronterface, if i do not wait for the move to be completed after each click of the gui.
The Marlin bugifx 2.0 settings are for a TB6600, but the spec sheet says that it is 2.5uS min pulse for the DM542T, and it is working at micro step 4 ???
What have i missed ?
I have built my own 3d machine
Due to resonance at certain speeds i wanted to change from TB6600 drivers to DM542T drivers for the X/Y axes.
With the TB6600 drivers everything was working as expected (except for resonance at the specific speeds).
With the DM542T on the X axis (only have one DM542T driver at the moment), it works exactly as expected when the micro stepping is set to 800 (4).
When i say exactly as expected, i mean that the axis moves normally, and if i move, from the front panel, after homing, i can move it away from hp, back and forth, and when i return it to the hp, it will exactly (0.1mm) trigger the hp sensor. So home = hp sensor on, move 0.1mm = hp sensor off, whizz it around at various front panel dictated movements and return to hp which is activated when i move the last step of 0.1mm to 0 position.
But, when i change the micro stepping to 400 (2), it will work exactly as expected only if i do 1 click at a time, of the front panel encoder, to move it 1x 10mm, 1x 1mm, or 1 x 0.1mm. If i rotate the encoder so that it will move say 6 x 1mm in one movement, then it will miss steps. This problem happens both ways (ie "fast" movements left and right). Again with single rotary clicks it is good.
I have tried reducing the speed it moves from the front panel, reducing the accerleration, have tried min and max motor currents on the DM542T - all without success.
I am thinking that because it works reliably at 800 (micro step 4) it cannot be anything except a weird DM542T problem ???
This problem also happens from Pronterface, if i do not wait for the move to be completed after each click of the gui.
The Marlin bugifx 2.0 settings are for a TB6600, but the spec sheet says that it is 2.5uS min pulse for the DM542T, and it is working at micro step 4 ???
What have i missed ?