XYZ jog problem. no reverse!

Hi,

I have my board running now with the Reprap Host, and was using the commsdebug=true and the xyz tab to jog motors.

Set speed to 300 mm/minute max.

Jogging in the positive direction - all motors move.
Jogging in the negative direction - no movement.

Hooking up an oscope -

direction - inverts correctly (+5 for positive, GND for negative)
Steps - can see the pulse train on the positive BUT NO PULSES for the negative direction.

Watching the comms window -

I can see this for a 10mm step forward:
G1 X10.0

and backward(from 10mm position):
G1 X0.0

So the G-code looks correct, and is being sent to the motherboard.


Is there a configuration error somewhere in the firmware or the reprap host prefs? I assume it would be the frimware, since the gcode is sent out correctly?

Any help or insight would be appreciated.

Have you got your end stops connected and configured correctly? It wont move backwards if it thinks the end stop is triggered.

---

[www.hydraraptor.blogspot.com]

I have endstops configured and connected.

They are H21L0B, and the setting in configuration.h has them as inverted.

Based on your suggestion - I tried tripping them, and then running backward - same result - no pulses.

Tried disconnected as well - same result.

Thanks for the idea.

I had the same problem and the problem WAS the end stops. make double sure you checked this by changing the value in the "inverted" define.

though that seems unlikely to be the problem in your case.

so basically as far as you can tell

Host Software: OK (sending out correct G-code)
Sanguino/arduino: OK (dir pin inverts, and step pin is pulsed)
Stepper board: ?
Motor: ?

if my above summary is true, then:

I'd double check the connections to the stepper board, the stepper board itself if you soldered it, and the connection from the motor to the stepper board.

those are the only remaining points of possible failure as far as I can tell.

Edited 1 time(s). Last edit at 05/06/2010 06:07AM by Leav.

This questions comes up over and over again. It is ALWAYS the endstops. The firmware will not send steps if it thinks they are triggered.

---

[www.hydraraptor.blogspot.com]

I had a problem with just one endstop that turned out to be created by the Arduino board.

On the Arduino board itself an LED was connected to a pin that happended to be used as an endstop input and the endstop was not able to drive an LED, so insufficient signal was delivered to the microcontroller.

I simply swapped two connections, making sure that the pin with that LED connected to it was used as an output and my problem vanished.

t3kboi, any progress? (i'm curious )

Progress!

It was indeed the endstops - but not how I thought.

(OK - time to put on stupid hat)

I had connected the min endstops to the max pins - when I doublechecked pins, I just checked the same ones again. (i.e -- repeated my original error).

So......

When I actually connect them to the pins for the min stops - voila!

Sometimes I just cant see the forest for the trees.

Thanks to all for your suggestions.