# No bounds checking?

**URL:** <https://forums.maslowcnc.com/t/no-bounds-checking/25374>\
**Category:** Software\
**Created:** [December 29, 2025, 9:11pm UTC](https://forums.maslowcnc.com/t/no-bounds-checking/25374 "2025-12-29T21:11:24Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![2x4logic](https://avatars.discourse-cdn.com/v4/letter/2/dfb087/32.png) [@2x4logic](https://forums.maslowcnc.com/u/2x4logic)\
**Post date:** [December 29, 2025, 9:11pm UTC](https://forums.maslowcnc.com/t/no-bounds-checking/25374/1 "2025-12-29T21:11:24Z")

</div>

A warning and possible opportunity for firmware improvement…

There does not seem to be physical bounds checking with the Maslow firmware (v1.15), or at least not with the jog controls in the web interface.

After repeating calibration a number of times (and not just relying on when it pronounces it finished), it thinks the anchors are ~2302-2303 width and ~1152-1155 height (which is a few millimeters generous on the width and stingy on the height).

Calibration is 9x9 over a 1600x800 area. For this scenario, home position is set to the center-ish place calibration finishes up at.

Using the GUI jog controls, I then do six 100mm jogs down. That results in the Maslow attempting to go ~200mm beyond the calibration and ~50mm beyond the anchors. I then hit the Home button to _TRY_ to return it home.

Yes, the user should hopefully have the foresight to discern this could be trouble, but imagine accidentally hitting the jog controls too often or getting a G-code file that would fit the workpiece but the home position doesn’t suit the G-code file.

[![](https://img.youtube.com/vi/uFJXPrnmTVw/maxresdefault.jpg "Maslow 4.1 FW 1.15 out-of-bounds behavior") ](https://www.youtube.com/watch?v=uFJXPrnmTVw)

As you can see from the video, the belt cogs get loose at the end of the job, but then things really go awry when attempting to return home.

If the user then does a RETRACT ALL after this (DO NOT DO THIS!!!), it jams up the belt cogs and necessitates taking the Maslow apart to unjam it.

P.S.: another oddity I observed during this is that if one hits RETRACT ALL, then STOP during the retraction, then RELEASE TENSION, the RELEASE TENSION just starts retracting again… which is not likely what the user was expecting.

---

<div class="post-metadata">

**Author:** ![2x4logic](https://avatars.discourse-cdn.com/v4/letter/2/dfb087/32.png) [@2x4logic](https://forums.maslowcnc.com/u/2x4logic)\
**Post date:** [December 29, 2025, 9:13pm UTC](https://forums.maslowcnc.com/t/no-bounds-checking/25374/2 "2025-12-29T21:13:02Z")

</div>

a visual illustration of the jam (forum allows only one media link per post)…

 ![mIMG_20251229_131859341](https://canada1.discourse-cdn.com/flex031/uploads/maslowcnc/original/3X/b/f/bfc701854a7196889142883d965da100864ce793.jpeg)

---

<div class="post-metadata">

**Author:** ![2x4logic](https://avatars.discourse-cdn.com/v4/letter/2/dfb087/32.png) [@2x4logic](https://forums.maslowcnc.com/u/2x4logic)\
**Post date:** [December 29, 2025, 9:27pm UTC](https://forums.maslowcnc.com/t/no-bounds-checking/25374/3 "2025-12-29T21:27:41Z")

</div>

woohoo… I finally have permissions to post configuration files

[maslow-20251229c.yaml](https://forums.maslowcnc.com/uploads/short-url/digj4Y2UkPsxmmWmJj6oox3E6WN.yaml) (6.8 KB)

[Maslow-serial-20251229c1-calibration.log](https://forums.maslowcnc.com/uploads/short-url/aMlOyMSJNmUAZRiTGS2dlhWUhsh.log) (14.5 KB)

[Maslow-serial-20251229c2-outofbounds.log](https://forums.maslowcnc.com/uploads/short-url/rottOn5zIZY8Euu4RRhrXbxzT0P.log) (4.8 KB)

---

<div class="post-metadata">

**Author:** ![dlang](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/dlang/32/859_2.png) [@dlang](https://forums.maslowcnc.com/u/dlang)\
**Post date:** [December 29, 2025, 9:32pm UTC](https://forums.maslowcnc.com/t/no-bounds-checking/25374/4 "2025-12-29T21:32:54Z")

</div>

2x4logic wrote:

> A warning and possible opportunity for firmware improvement…
> 
> There does not seem to be physical bounds checking with the Maslow firmware (v1.15), or at least not with the jog controls in the web interface.

That is correct, v1.15 does not have a concept of where the borders of your  
workpiece are. I believe that Bar added that in 1.16, but if not, it’s something  
he is working on (I’ve seen a PR go by where it adds the concept of a workpiece  
area, and offsets, and then attempts to use them as limits)

> Using the GUI jog controls, I then do six 100mm jogs down. That results in  
> the Maslow attempting to go ~200mm beyond the calibration and ~50mm beyond

going beyond the calibration is not a problem, going beyond the anchors is a  
problem, but you run into grief long before that.

David Lang

---

<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:** [December 29, 2025, 9:36pm UTC](https://forums.maslowcnc.com/t/no-bounds-checking/25374/5 "2025-12-29T21:36:43Z")

</div>

@dlang is right, this is included in 1.16. I’m sorry that we didn’t add it fast enough to save you 😕
