SoliForum - 3D Printing Community — printer wont manually move

Re: printer wont manually move

2015-03-09T04:37:25Z

CrisRowlands wrote:

I had a problem similar to this yesterday whilst re-building my SD4.
It turns out the firmware doesn't like moving any of the axes (besides homing) when it can't detect the thermistor.
If you're getting temperature reset errors, it might be worth checking the thermistor wiring.

+1 - try this.
IMO totally bizarre behaviour, makes assembling and testing a printer in stages a bit tiresome haha

Re: printer wont manually move

2015-03-07T00:47:48Z

I had a problem similar to this yesterday whilst re-building my SD4.

It turns out the firmware doesn't like moving any of the axes (besides homing) when it can't detect the thermistor.
If you're getting temperature reset errors, it might be worth checking the thermistor wiring.

Re: printer wont manually move

2015-02-23T22:31:32Z

well. I flashed the board. now i can move the motors any way i want to. But I still get a m999 reset max heat problem although I change it to max heat 350 C. whats the deal here?

Re: printer wont manually move

2015-02-23T21:56:52Z

i have an sd4 (and I am very new at all this), but it wont move manually until after I click on the opposite direction I want it to go to 'activate' the motor (?) after homing all...
so to move X left from the home position, I have to hit the "move right" button first, then I can move it left
same thing for Y - to move forward from home, I have to hit the back button first, then I can move to where ever I want to.
Z will move manually without having to do this, however.
not really sure why this is, but it is....

Re: printer wont manually move

2015-02-23T21:28:53Z

Try homing the x and y axes and then try to move.

printer wont manually move

2015-02-23T19:36:02Z

finally got all of the binding issues worked out of the sd2. new rods and bearings and pulleys. now the printer will move when I hit the home button or run a job but will not move when I hit the manual buttons. kinda odd. anyone have a fix for this?

should I reflash the board would that help?