<p>From the data you provided <strong>I would postulate that the problem is likely hardware: either with the the general assembly of the motherboard or with the stepper drivers</strong>.</p>

<p>The test you already performed excludes the stepper motors themselves as possible culprits.  Common sense suggests that if such a show-stopper bug was present in the original Anet firmware, thousands of users would report it.  </p>

<p>Stepper motors are usually controlled by two signals (two cables): <code>PULSE</code> and <code>DIR</code>.  The <code>PULSE</code> signal controls how many steps the motor needs to perform and the signal itself is normally a PWM or some other form of square wave.  The <code>DIR</code> signal controls which direction the motor is supposed to spin (clockwise or counter-clockwise), and the signal itself is just a "high/low" voltage.</p>

<p><a href="https://i.sstatic.net/z3dgW.gif" rel="nofollow noreferrer"><img src="https://i.sstatic.net/z3dgW.gif" alt="enter image description here"></a></p>

<p>Now, electronics is not exactly my cup of tea, but <strong>I would suggest what is happening is that the <code>DIR</code> signal of the broken output is stuck on either the high or low voltage</strong> (you can test this easily with a tester).</p>

<p>If I am right, <strong>the likely culprit is either a dry joint</strong> (so a joint that does not let electricity pass and keep the <code>DIR</code> signal in its low state), <strong>or a short</strong> (so a place where voltage at "high" level is allowed to get onto the cable carrying the <code>DIR</code> signal).  These kind of problems are typically related to poor soldering of the connectors, or to bridges between the pins of chips.  You can visually inspect your board for such problems.</p>

<p>Another possible culprit is obviously the driver for the stepper motor itself.</p>

CC BY-SA 3.0
2018-03-11T19:31:00.663Z
Thanks Mac.  I was able to trace down the issue to a cold solder joint on the Z-Motor1 board connector.  Resoldered and Z travel works properly.  Now to reassemble and get on with the rest of the troubleshooting.  Thank you.
Pyro-MO
CC BY-SA 3.0
2018-03-11T02:29:52.683Z
2018-03-12T07:24:30.067Z
2018-03-12T07:24:30.067Z
mac
<p>I just finished assembly of Anet A8 (Prusa i3 clone).  X any Y work fine, both Z motors move down just fine, when homed.</p>

<p>On Z-stop trigger, right Z moves up, left Z continues to try to move down.  When up command is given in Pronterface or RepetierHost, right Z moves up, left Z moves down.  Switching cable plugs moves the problem: the down only moves are always on Z-Motor1 output.</p>

<p>I have flashed the firmware with original Anet Omni firmware and problem persists.  <strong>How else can I test if the problem is hardware- or firmware- related?</strong></p>

<p>I am reluctant to change to different firmware entirely, as I have not yet found out what the problem is.</p>

CC BY-SA 4.0
2018-09-10T11:25:35.610Z
Have you found and fixed the problem? If so, has the answer below led you to the solution? Please vote to accept the answer so this question is not bumped up once in a while and can be removed from the unanswered question list. You may even add your own solution and accept that after 48 hours! If you have not been able to address the problem please update your question.
0scar
<z-axis><anet-a8><stepper><motor>
Anet A8 One Z output only moves down (even on up command)
Pyro-MO
# Anet A8 One Z output only moves down (even on up command)

(Asked by: username_0 on 2018-03-11)

I just finished assembly of Anet A8 (Prusa i3 clone). X any Y work fine, both Z motors move down just fine, when homed.

On Z-stop trigger, right Z moves up, left Z continues to try to move down. When up command is given in Pronterface or RepetierHost, right Z moves up, left Z moves down. Switching cable plugs moves the problem: the down only moves are always on Z-Motor1 output.

I have flashed the firmware with original Anet Omni firmware and problem persists. **How else can I test if the problem is hardware- or firmware- related?**

I am reluctant to change to different firmware entirely, as I have not yet found out what the problem is.

**Tags:** z-axis, anet-a8, stepper, motor
> **Comments:**
> **username_1**: Have you found and fixed the problem? If so, has the answer below led you to the solution? Please vote to accept the answer so this question is not bumped up once in a while and can be removed from the unanswered question list. You may even add your own solution and accept that after 48 hours! If you have not been able to address the problem please update your question.  

---

## 1 answers

### Answer by username_2 on 2018-03-11. Score: 2

From the data you provided **I would postulate that the problem is likely hardware: either with the the general assembly of the motherboard or with the stepper drivers**.

The test you already performed excludes the stepper motors themselves as possible culprits. Common sense suggests that if such a show-stopper bug was present in the original Anet firmware, thousands of users would report it.

Stepper motors are usually controlled by two signals (two cables): `PULSE` and `DIR`. The `PULSE` signal controls how many steps the motor needs to perform and the signal itself is normally a PWM or some other form of square wave. The `DIR` signal controls which direction the motor is supposed to spin (clockwise or counter-clockwise), and the signal itself is just a "high/low" voltage.

[![enter image description here](https://i.sstatic.net/z3dgW.gif)](https://i.sstatic.net/z3dgW.gif)

Now, electronics is not exactly my cup of tea, but **I would suggest what is happening is that the `DIR` signal of the broken output is stuck on either the high or low voltage** (you can test this easily with a tester).

If I am right, **the likely culprit is either a dry joint** (so a joint that does not let electricity pass and keep the `DIR` signal in its low state), **or a short** (so a place where voltage at "high" level is allowed to get onto the cable carrying the `DIR` signal). These kind of problems are typically related to poor soldering of the connectors, or to bridges between the pins of chips. You can visually inspect your board for such problems.

Another possible culprit is obviously the driver for the stepper motor itself.

> **Comments:**
> **username_0**: Thanks Mac.  I was able to trace down the issue to a cold solder joint on the Z-Motor1 board connector.  Resoldered and Z travel works properly.  Now to reassemble and get on with the rest of the troubleshooting.  Thank you.  

---

