# Push to extend bug?

**URL:** <https://forums.maslowcnc.com/t/push-to-extend-bug/20857>\
**Category:** Troubleshooting\
**Created:** [April 29, 2024, 1:17am UTC](https://forums.maslowcnc.com/t/push-to-extend-bug/20857 "2024-04-29T01:17:24Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![Scuba\_Shan](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/scuba_shan/32/22722_2.png) [@Scuba\_Shan](https://forums.maslowcnc.com/u/Scuba_Shan)\
**Post date:** [April 29, 2024, 1:17am UTC](https://forums.maslowcnc.com/t/push-to-extend-bug/20857/1 "2024-04-29T01:17:24Z")

</div>

After a successful day cutting 2 full sheets of parts yesterday I loaded up a new sheet this morning , attached the belts, and hit apply tension. Maslow pulled BL and TR so tight I thought it was going to snap. Errored with the usual exceed 4000ma current exceeded.

Powered off machine, retracted belts, and then went to extend.

TL and TR are both doing the thing where you can “push” the belt in and it’ll let you pull that distance out that I’ve documented before at [Extend all failing to release all belts](https://forums.maslowcnc.com/t/extend-all-failing-to-release-all-belts/20484)

Any ideas?

---

<div class="post-metadata">

**Author:** ![Carson\_Barry](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/carson_barry/32/23367_2.png) [@Carson\_Barry](https://forums.maslowcnc.com/u/Carson_Barry)\
**Post date:** [April 29, 2024, 1:43am UTC](https://forums.maslowcnc.com/t/push-to-extend-bug/20857/2 "2024-04-29T01:43:40Z")

</div>

If it doesn’t clear the issue with a restart, I’d try replacing your yaml/index and firmware with the most recent. Bar had mentioned that this could be related to the yaml file.

---

<div class="post-metadata">

**Author:** ![Scuba\_Shan](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/scuba_shan/32/22722_2.png) [@Scuba\_Shan](https://forums.maslowcnc.com/u/Scuba_Shan)\
**Post date:** [April 29, 2024, 1:58am UTC](https://forums.maslowcnc.com/t/push-to-extend-bug/20857/3 "2024-04-29T01:58:53Z")

</div>

Just did that with the same result. Usually that has fixed it in the past though.

It’s almost as if the motor is running or the encoder is reading backwards? So that as I push the belt in it powers that much out. Some sort of race condition?

I don’t think it could be hardware related as it’s sporadic in nature and I’ve had it cutting for just over 10 hours already.

---

<div class="post-metadata">

**Author:** ![Scuba\_Shan](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/scuba_shan/32/22722_2.png) [@Scuba\_Shan](https://forums.maslowcnc.com/u/Scuba_Shan)\
**Post date:** [April 29, 2024, 2:04am UTC](https://forums.maslowcnc.com/t/push-to-extend-bug/20857/4 "2024-04-29T02:04:24Z")

</div>

I swapped TL and BL encoder and motor ports on the controller , the problem stayed with TL so its got to be something to do with that encoder/motor?

---

<div class="post-metadata">

**Author:** ![bar](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/bar/32/10_2.png) [@bar](https://forums.maslowcnc.com/u/bar)\
**Post date:** [April 29, 2024, 3:28pm UTC](https://forums.maslowcnc.com/t/push-to-extend-bug/20857/5 "2024-04-29T15:28:49Z")

</div>

That is weird. Good sleuthing to track it down. I’m a little stumped.

Does pressing test report anything out of the ordinary?

---

<div class="post-metadata">

**Author:** ![clintloggins](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/clintloggins/32/56_2.png) [@clintloggins](https://forums.maslowcnc.com/u/clintloggins)\
**Post date:** [April 29, 2024, 6:10pm UTC](https://forums.maslowcnc.com/t/push-to-extend-bug/20857/6 "2024-04-29T18:10:20Z")

</div>

Im having the same issue botom left 🤔

 ![IMG_5746](https://canada1.discourse-cdn.com/flex031/uploads/maslowcnc/original/3X/3/8/381a109b152209fd159faf2eaff30c6cc493b7c9.png)

---

<div class="post-metadata">

**Author:** ![bar](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/bar/32/10_2.png) [@bar](https://forums.maslowcnc.com/u/bar)\
**Post date:** [April 29, 2024, 6:18pm UTC](https://forums.maslowcnc.com/t/push-to-extend-bug/20857/7 "2024-04-29T18:18:08Z")

</div>

Does anyone have a video of it happening? I’m still not 100% sure I can picture it right

---

<div class="post-metadata">

**Author:** ![clintloggins](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/clintloggins/32/56_2.png) [@clintloggins](https://forums.maslowcnc.com/u/clintloggins)\
**Post date:** [April 29, 2024, 6:34pm UTC](https://forums.maslowcnc.com/t/push-to-extend-bug/20857/8 "2024-04-29T18:34:47Z")

</div>

Gosh @bar I just unplugged for a minute this time, started over with retract then extend and working fine 🤷‍♂️

---

<div class="post-metadata">

**Author:** ![Scuba\_Shan](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/scuba_shan/32/22722_2.png) [@Scuba\_Shan](https://forums.maslowcnc.com/u/Scuba_Shan)\
**Post date:** [April 29, 2024, 7:52pm UTC](https://forums.maslowcnc.com/t/push-to-extend-bug/20857/9 "2024-04-29T19:52:28Z")

</div>

> [@Extend all failing to release all belts](https://forums.maslowcnc.com/t/extend-all-failing-to-release-all-belts/20484):
>
> UPS arrived this afternoon so I got to work building 'Luke" our m4. All went well , firmware updated to 0.66.3 and I was able to retract all belts after increasing /Maslow\_Retract\_Current\_Threshold to 1800. Now im trying to extend the belts and it’s not going so well. I cant pull on the belts without extreme force. I was able to do this to loosen a few mm but it wont extend any further. If I push the belt in , it unwinds a little which I can then pull out another few mm of belt but this doesnt…

---

<div class="post-metadata">

**Author:** ![bar](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/bar/32/10_2.png) [@bar](https://forums.maslowcnc.com/u/bar)\
**Post date:** [April 29, 2024, 8:01pm UTC](https://forums.maslowcnc.com/t/push-to-extend-bug/20857/10 "2024-04-29T20:01:07Z")

</div>

In that video is it extending on the push or on the pull?

If you push in and then extend slowly does it extend normally?

---

<div class="post-metadata">

**Author:** ![Scuba\_Shan](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/scuba_shan/32/22722_2.png) [@Scuba\_Shan](https://forums.maslowcnc.com/u/Scuba_Shan)\
**Post date:** [April 29, 2024, 8:03pm UTC](https://forums.maslowcnc.com/t/push-to-extend-bug/20857/11 "2024-04-29T20:03:30Z")

</div>

It extends on the push. You push it say 10mm , it’ll roll out 10mm more. then the next time you can push 20mm , and it’ll let out another 20mm. Eventually you can do this until all 4300mm are out (ive done this a few times) . Retract all works fine.

---

<div class="post-metadata">

**Author:** ![bar](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/bar/32/10_2.png) [@bar](https://forums.maslowcnc.com/u/bar)\
**Post date:** [April 29, 2024, 8:15pm UTC](https://forums.maslowcnc.com/t/push-to-extend-bug/20857/12 "2024-04-29T20:15:14Z")

</div>

> [@Scuba\_Shan](#):
>
> I swapped TL and BL encoder and motor ports on the controller , the problem stayed with TL so its got to be something to do with that encoder/motor?

I’m trying to picture this and I’m confusing myself. So the issue was happening on the top left arm…then when swapping the TL and BL encoder and motor ports the issue stayed with the same arm or stayed with the same port on the controller board?

---

<div class="post-metadata">

**Author:** ![Scuba\_Shan](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/scuba_shan/32/22722_2.png) [@Scuba\_Shan](https://forums.maslowcnc.com/u/Scuba_Shan)\
**Post date:** [April 29, 2024, 8:19pm UTC](https://forums.maslowcnc.com/t/push-to-extend-bug/20857/13 "2024-04-29T20:19:01Z")

</div>

Stayed with same arm

---

<div class="post-metadata">

**Author:** ![bar](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/bar/32/10_2.png) [@bar](https://forums.maslowcnc.com/u/bar)\
**Post date:** [April 29, 2024, 8:24pm UTC](https://forums.maslowcnc.com/t/push-to-extend-bug/20857/14 "2024-04-29T20:24:01Z")

</div>

That’s got to be an issue with the encoder then. If you unplug the cable on the encoder side and plug it back in does that change anything?

---

<div class="post-metadata">

**Author:** ![Scuba\_Shan](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/scuba_shan/32/22722_2.png) [@Scuba\_Shan](https://forums.maslowcnc.com/u/Scuba_Shan)\
**Post date:** [April 29, 2024, 8:28pm UTC](https://forums.maslowcnc.com/t/push-to-extend-bug/20857/15 "2024-04-29T20:28:02Z")

</div>

Nope. I have previously fixed it with some combination of firmware upgrade / replacing the config or just rebooting. Its an odd one…

---

<div class="post-metadata">

**Author:** ![bar](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/bar/32/10_2.png) [@bar](https://forums.maslowcnc.com/u/bar)\
**Post date:** [April 29, 2024, 8:29pm UTC](https://forums.maslowcnc.com/t/push-to-extend-bug/20857/16 "2024-04-29T20:29:47Z")

</div>

Super odd.

That the issue moves with the arm (great call on doing that test) points strongly to it being something with the encoder board, but having a firmware upgrade fix it points to it being a software thing.

---

<div class="post-metadata">

**Author:** ![Scuba\_Shan](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/scuba_shan/32/22722_2.png) [@Scuba\_Shan](https://forums.maslowcnc.com/u/Scuba_Shan)\
**Post date:** [April 29, 2024, 8:35pm UTC](https://forums.maslowcnc.com/t/push-to-extend-bug/20857/17 "2024-04-29T20:35:10Z")

</div>

Yup and it’s really odd that if it’s the encoder board how have I been able to cut ~10hrs without issue.

---

<div class="post-metadata">

**Author:** ![daveelt](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/daveelt/32/16840_2.png) [@daveelt](https://forums.maslowcnc.com/u/daveelt)\
**Post date:** [April 29, 2024, 8:39pm UTC](https://forums.maslowcnc.com/t/push-to-extend-bug/20857/18 "2024-04-29T20:39:45Z")

</div>

Just a thought, did you try swapping the Ethernet cables to see if it was a cable issue?

---

<div class="post-metadata">

**Author:** ![Scuba\_Shan](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/scuba_shan/32/22722_2.png) [@Scuba\_Shan](https://forums.maslowcnc.com/u/Scuba_Shan)\
**Post date:** [April 29, 2024, 8:41pm UTC](https://forums.maslowcnc.com/t/push-to-extend-bug/20857/19 "2024-04-29T20:41:25Z")

</div>

Will try that this morning!

---

<div class="post-metadata">

**Author:** ![bar](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/bar/32/10_2.png) [@bar](https://forums.maslowcnc.com/u/bar)\
**Post date:** [April 29, 2024, 8:45pm UTC](https://forums.maslowcnc.com/t/push-to-extend-bug/20857/20 "2024-04-29T20:45:00Z")

</div>

That’s why I was wondering if it was the wire. I was thinking maybe it came lose or something.

I don’t think that the encoder board failed, they’re good for a long long time usually and since a couple folks are seeing this I don’t think it’s a one off fluke.

I just took a look at the code and you should be seeing an encoder read failure message if the board is experiencing a bad connection to the encoder

[Next page](https://forums.maslowcnc.com/t/push-to-extend-bug/20857.md?page=2)
