# Closed: \[Beta\] Makerverse (previously known as "CNCjs") Support for \*\*All Maslow Editions\*\* w/ Non-Destructive Edge Calibration

**URL:** <https://forums.maslowcnc.com/t/closed-beta-makerverse-previously-known-as-cncjs-support-for-all-maslow-editions-w-non-destructive-edge-calibration/14348>\
**Category:** Software\
**Created:** [August 19, 2020, 11:53pm UTC](https://forums.maslowcnc.com/t/closed-beta-makerverse-previously-known-as-cncjs-support-for-all-maslow-editions-w-non-destructive-edge-calibration/14348 "2020-08-19T23:53:25Z")\
**Posts on this page:** 20\
**Page:** 27

<div class="post-metadata">

**Author:** ![zaneclaes](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/zaneclaes/32/16801_2.png) [@zaneclaes](https://forums.maslowcnc.com/u/zaneclaes)\
**Post date:** [September 10, 2020, 7:22pm UTC](https://forums.maslowcnc.com/t/closed-beta-makerverse-previously-known-as-cncjs-support-for-all-maslow-editions-w-non-destructive-edge-calibration/14348/524 "2020-09-10T19:22:03Z")

</div>

Okay, I just did some X jogging. I can easily align the cotter pin in the center of the bar. I actually don’t think the orientation of the sprockets matters just yet.

Here’s my revised proposal:

1. Attach cotter pin and pull chains taut
2. Enter measurement for distBetweenMotors
3. Machine sets current chain lengths to distBetweenMotors/2
4. Jog in negative Y direction until the bit is just **above** the top of the stock.
5. Mark this spot on the **spoilboard**. It is your home / reset chains location.
6. Measure the distance from the mark to the top of the workspace.
7. The Maslow can now **compute**!!! the motorOffsetY – it’s just how much the sled moved during (4) plus. the offset from top of workspace in (6).
8. Finally, the chain lengths can be calculated. Assuming the original distBetweenMotors was correct, the motorOffsetY should be perfect. And since the chains are guaranteed to be the same length, the extended chain lengths should also be highly accurate.

---

<div class="post-metadata">

**Author:** ![madgrizzle](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/madgrizzle/32/1372_2.png) [@madgrizzle](https://forums.maslowcnc.com/u/madgrizzle)\
**Post date:** [September 10, 2020, 7:29pm UTC](https://forums.maslowcnc.com/t/closed-beta-makerverse-previously-known-as-cncjs-support-for-all-maslow-editions-w-non-destructive-edge-calibration/14348/525 "2020-09-10T19:29:53Z")

</div>

Where in there does the sled get attached?

---

<div class="post-metadata">

**Author:** ![zaneclaes](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/zaneclaes/32/16801_2.png) [@zaneclaes](https://forums.maslowcnc.com/u/zaneclaes)\
**Post date:** [September 10, 2020, 7:34pm UTC](https://forums.maslowcnc.com/t/closed-beta-makerverse-previously-known-as-cncjs-support-for-all-maslow-editions-w-non-destructive-edge-calibration/14348/526 "2020-09-10T19:34:22Z")

</div>

Sorry, any time while doing (4).

I also assume you’d start step (4) by homing. So by the time you get to (6), the Y coordinate shown by the Maslow is exactly the amount moved (negative).

---

<div class="post-metadata">

**Author:** ![Bob\_Craig](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/bob_craig/32/17242_2.png) [@Bob\_Craig](https://forums.maslowcnc.com/u/Bob_Craig)\
**Post date:** [September 10, 2020, 7:40pm UTC](https://forums.maslowcnc.com/t/closed-beta-makerverse-previously-known-as-cncjs-support-for-all-maslow-editions-w-non-destructive-edge-calibration/14348/527 "2020-09-10T19:40:11Z")

</div>

In reading through all the back and forth, I can’t help but be left with the impression that you are simply recreating the original Maslow calibration process. Steps 1-3 are just a variation of extending one chain from the L to R motor and pulling taut - that also gives you the motor spacing, correct? Then when you feed the chain from each motor you are finding the center point because you know both chains have been fed out the same distance.

I agree that the original setup process was tedious, mainly because the risk of chain wrap was high, but I’m not convinced this isn’t equally tedious.

---

<div class="post-metadata">

**Author:** ![zaneclaes](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/zaneclaes/32/16801_2.png) [@zaneclaes](https://forums.maslowcnc.com/u/zaneclaes)\
**Post date:** [September 10, 2020, 9:10pm UTC](https://forums.maslowcnc.com/t/closed-beta-makerverse-previously-known-as-cncjs-support-for-all-maslow-editions-w-non-destructive-edge-calibration/14348/528 "2020-09-10T21:10:17Z")

</div>

> [@Bob\_Craig](#):
>
> can’t help but be left with the impression that you are simply recreating the original Maslow calibration process.

Fair point, but I think we are getting close to something better.

> [@Bob\_Craig](#):
>
> Steps 1-3 are just a variation of extending one chain from the L to R motor and pulling taut - that also gives you the motor spacing, correct?

Yes, tho I’d say they’re much faster (you only end up extending 1/3 the distance) and less error-prone (no chain wrapping or snapping with the cotter pin in place).

I’m also wondering can do the following. It’s pretty easy to use the cotter pin to create a perfect triangle. I mean, maybe this isn’t the same as having the sled, but it feels pretty darn precise to me when I actually line it up and press down on it…

![image](https://canada1.discourse-cdn.com/flex031/uploads/maslowcnc/original/3X/4/0/4044f5997efc2c312a320a8ada911dfb9999479c.jpeg)

… so if I tell you to hit a specific point before attaching the sled, and then you measure the actual location of the sled, I can perform an initial validation. We know how long the chains **should be** at this point, given the cotter pin. If the actual sled location doesn’t line up, I can actually provide advice and prevent the user from trying to calibrate invalid measurements.

To recap, the steps are now just:

- Make cotter pin hit a given point (_with equal chain lengths; easy to do with sled off_)
- Attach sled
- Enter sled location measurement, as well as distBetweenMotors and motorOffsetY

If the sled’s location does not match expectations, it could do a single-point calibration process to adjust distBetweenMotors and motorOffsetY into nearby values which satisfy the expectations.

---

<div class="post-metadata">

**Author:** ![Orob](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/orob/32/16344_2.png) [@Orob](https://forums.maslowcnc.com/u/Orob)\
**Post date:** [September 10, 2020, 9:20pm UTC](https://forums.maslowcnc.com/t/closed-beta-makerverse-previously-known-as-cncjs-support-for-all-maslow-editions-w-non-destructive-edge-calibration/14348/529 "2020-09-10T21:20:35Z")

</div>

> [@zaneclaes](#):
>
> > [@Orob](#):
> >
> > The center I marked was not the center after calibrating
> 
> - How did you mark center before calibrating (pen & tape measure on stock?)
> - I assume you used “return to center” after calibrating and noted a difference in bit location?
> - Please moving the sled into the Edge Calibration top-middle & bottom-middle positions (just above and below center). Are these positions correct (exactly touching edge of stock)? Or do they experience the same skew as the center point?

1- marked center with pencil to make a plus in the middle with a 4’ drywall square ( work area is 4’, so easily done)  
2. used return to center after calibration  
3. used precision calibration with 1/8" bit to drill each location. Will do it again and get back to you.

with length of this thread, should we split it to calibration techniques /accuracy and UI feature / software issues?

---

<div class="post-metadata">

**Author:** ![Bob\_Craig](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/bob_craig/32/17242_2.png) [@Bob\_Craig](https://forums.maslowcnc.com/u/Bob_Craig)\
**Post date:** [September 10, 2020, 9:30pm UTC](https://forums.maslowcnc.com/t/closed-beta-makerverse-previously-known-as-cncjs-support-for-all-maslow-editions-w-non-destructive-edge-calibration/14348/530 "2020-09-10T21:30:38Z")

</div>

How does the user avoid the chains wrapping around the sprockets if they are feeding at the same time? I found I had to be at the motor making sure it didn’t come around and start wrapping until there was sufficient weight on the outfeed side. With both motors feeding chain at the same time, that would be impossible.

---

<div class="post-metadata">

**Author:** ![zaneclaes](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/zaneclaes/32/16801_2.png) [@zaneclaes](https://forums.maslowcnc.com/u/zaneclaes)\
**Post date:** [September 10, 2020, 9:41pm UTC](https://forums.maslowcnc.com/t/closed-beta-makerverse-previously-known-as-cncjs-support-for-all-maslow-editions-w-non-destructive-edge-calibration/14348/531 "2020-09-10T21:41:59Z")

</div>

Moving the discussion here: [Simplified Chain Length Measurements for Calibration](https://forums.maslowcnc.com/t/simplified-chain-length-measurements-for-calibration/14609)

Short answer: you never move the motors without the cotter pin in place. You throw the chains over the sprockets, stick the cotter pin in, and move them until they’re taut and the pin is centered. Then you can move in the -Y axis freely to align the pin with the target point.

---

<div class="post-metadata">

**Author:** ![Bob\_Craig](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/bob_craig/32/17242_2.png) [@Bob\_Craig](https://forums.maslowcnc.com/u/Bob_Craig)\
**Post date:** [September 10, 2020, 11:14pm UTC](https://forums.maslowcnc.com/t/closed-beta-makerverse-previously-known-as-cncjs-support-for-all-maslow-editions-w-non-destructive-edge-calibration/14348/532 "2020-09-10T23:14:23Z")

</div>

I just had time to re-run Precision Calibration. I measured and remeasured my work area and did find that what I thought was my center point was off a bit. I started the calibration from true 0,0 and will see if it consistently hits the mark going forward.

One nice to have - my machine is setup with Router On/Off control. The calibration never sends an M4 when starting but does send an M5 when done. It would be nice to have the M4 sent at the beginning so I don’t have to do it manually before starting calibration.

After calibrating, I’m between 0.5 and 1mm off on a 50mm square and 100mm circle. Not bad…

---

<div class="post-metadata">

**Author:** ![zaneclaes](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/zaneclaes/32/16801_2.png) [@zaneclaes](https://forums.maslowcnc.com/u/zaneclaes)\
**Post date:** [September 10, 2020, 11:33pm UTC](https://forums.maslowcnc.com/t/closed-beta-makerverse-previously-known-as-cncjs-support-for-all-maslow-editions-w-non-destructive-edge-calibration/14348/533 "2020-09-10T23:33:01Z")

</div>

> [@Bob\_Craig](#):
>
> After calibrating, I’m between 0.5 and 1mm off on a 50mm square and 100mm circle. Not bad…

Not bad at all! Definitely still check the corners though.

> [@Bob\_Craig](#):
>
> One nice to have - my machine is setup with Router On/Off control. The calibration never sends an M4 when starting but does send an M5 when done. It would be nice to have the M4 sent at the beginning so I don’t have to do it manually before starting calibration.

Yeah, I have this lumped with “probes” in my head. Though, I do have my RPi GPIO turning my router and shopvac on/off automatically (its described earlier in this thread).

I’m working on a new version that improves the visualizer a lot. There were some bugs with mpos vs. wpos. You can now see the bit, the limits of the material… the grid lines look cleaner, and so on.

 ![Screen Shot 2020-09-10 at 5.29.07 PM](https://canada1.discourse-cdn.com/flex031/uploads/maslowcnc/original/3X/4/b/4b9f434b0f95e7b4fc6a597bfb54192d422e502b.png)

---

<div class="post-metadata">

**Author:** ![Bob\_Craig](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/bob_craig/32/17242_2.png) [@Bob\_Craig](https://forums.maslowcnc.com/u/Bob_Craig)\
**Post date:** [September 11, 2020, 1:41am UTC](https://forums.maslowcnc.com/t/closed-beta-makerverse-previously-known-as-cncjs-support-for-all-maslow-editions-w-non-destructive-edge-calibration/14348/534 "2020-09-11T01:41:30Z")

</div>

If the Makerverse build is failing (like now) and I reboot my RPI, will it pull down the bad build? I just rebooted and Makerverse isn’t coming back up. I just checked the Github page and see that the build is failing. If the two things correlate I won’t bother investigating further.

---

<div class="post-metadata">

**Author:** ![zaneclaes](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/zaneclaes/32/16801_2.png) [@zaneclaes](https://forums.maslowcnc.com/u/zaneclaes)\
**Post date:** [September 11, 2020, 1:47am UTC](https://forums.maslowcnc.com/t/closed-beta-makerverse-previously-known-as-cncjs-support-for-all-maslow-editions-w-non-destructive-edge-calibration/14348/535 "2020-09-11T01:47:48Z")

</div>

In this case, it was only the Windows build which failed. And I did just pull successfully on my RPi.

I think the confusion comes from the fact it can take many minutes to pull and unpack the updates, during which time Makerverse says its “running” but it’s really running the update step…

---

<div class="post-metadata">

**Author:** ![Bob\_Craig](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/bob_craig/32/17242_2.png) [@Bob\_Craig](https://forums.maslowcnc.com/u/Bob_Craig)\
**Post date:** [September 11, 2020, 1:49am UTC](https://forums.maslowcnc.com/t/closed-beta-makerverse-previously-known-as-cncjs-support-for-all-maslow-editions-w-non-destructive-edge-calibration/14348/536 "2020-09-11T01:49:28Z")

</div>

Yep, I was a bit impatient. It finally came alive again running #211. It looks like I picked up your new workspace UI enhancements.

---

<div class="post-metadata">

**Author:** ![Bob\_Craig](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/bob_craig/32/17242_2.png) [@Bob\_Craig](https://forums.maslowcnc.com/u/Bob_Craig)\
**Post date:** [September 11, 2020, 4:31pm UTC](https://forums.maslowcnc.com/t/closed-beta-makerverse-previously-known-as-cncjs-support-for-all-maslow-editions-w-non-destructive-edge-calibration/14348/537 "2020-09-11T16:31:25Z")

</div>

When I upload Gcode to Makerverse, I press the “Play” button to start cutting. Sometimes, as I’m learning how Work position works in relation to Machine position, I find that the machine is going to do something I don’t want. I expected that I could press “Pause” or “Stop” to end what it is doing. However, neither of those buttons are enabled when the machine is running. The only way I’ve been able to stop the machine is to click “Reset” which stops it immediately but seems quite extreme.

Is this expected behavior or a bug in the button states for “Pause” and “Stop”?

![image](https://canada1.discourse-cdn.com/flex031/uploads/maslowcnc/original/3X/5/d/5d4f729783629188a6f2909691a832e6fe7532d0.png)

---

<div class="post-metadata">

**Author:** ![zaneclaes](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/zaneclaes/32/16801_2.png) [@zaneclaes](https://forums.maslowcnc.com/u/zaneclaes)\
**Post date:** [September 11, 2020, 4:37pm UTC](https://forums.maslowcnc.com/t/closed-beta-makerverse-previously-known-as-cncjs-support-for-all-maslow-editions-w-non-destructive-edge-calibration/14348/538 "2020-09-11T16:37:10Z")

</div>

> [@Bob\_Craig](#):
>
> However, neither of those buttons are enabled when the machine is running. The only way I’ve been able to stop the machine is to click “Reset” which stops it immediately but seems quite extreme.

I just figured this out myself, and did try to make some improvements (I thought these were in that #211 build you have). What you have circled are the “workflow” commands. They specifically control the GCode program. Not the machine, in general.

I think what you’re looking for is _formally_ called **Feedhold** (and subsequently **Cycle Start** ). These buttons used to be there all the time. Now, I made it so that when the machine is Running (e.g., moving) you should see this:

![Screen Shot 2020-09-11 at 10.35.39 AM](https://canada1.discourse-cdn.com/flex031/uploads/maslowcnc/original/3X/1/4/1441b4d205a77cd01340689e624a257aee5eb7e2.png)

Pressing the Feedhold halts the shuttling and shows this:

![Screen Shot 2020-09-11 at 10.35.50 AM](https://canada1.discourse-cdn.com/flex031/uploads/maslowcnc/original/3X/b/2/b20853a8a0091591880fbb037ec794d6095f9a7a.png)

WDYT?

I don’t like the fact that the **run** / **hold** badges are not buttons, but **feedhold** and **cycle start** are. I think this area generally needs polish…

---

<div class="post-metadata">

**Author:** ![Bob\_Craig](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/bob_craig/32/17242_2.png) [@Bob\_Craig](https://forums.maslowcnc.com/u/Bob_Craig)\
**Post date:** [September 11, 2020, 4:56pm UTC](https://forums.maslowcnc.com/t/closed-beta-makerverse-previously-known-as-cncjs-support-for-all-maslow-editions-w-non-destructive-edge-calibration/14348/539 "2020-09-11T16:56:00Z")

</div>

I would lean toward simpler terminology - Pause instead of Feedhold and Start/Resume instead of Cycle Start. And if those buttons are added, the Gcode button bar has to go away - they appear to the user to be the same function.

Honestly, I don’t really understand what the existing Play/Pause/Stop buttons are intended to do if they don’t control machine function. I think it will be a trap for most users and the possible benefit likely doesn’t rise to the level that it should take up primary screen real estate.

---

<div class="post-metadata">

**Author:** ![zaneclaes](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/zaneclaes/32/16801_2.png) [@zaneclaes](https://forums.maslowcnc.com/u/zaneclaes)\
**Post date:** [September 11, 2020, 5:03pm UTC](https://forums.maslowcnc.com/t/closed-beta-makerverse-previously-known-as-cncjs-support-for-all-maslow-editions-w-non-destructive-edge-calibration/14348/540 "2020-09-11T17:03:57Z")

</div>

You’re right. I’ve already started going down this code wormhole. Basically, I need to “normalize” the different states of different protocols (Grbl, Marlin, TingG, Smoothie, etc.) into a human-readable status badge. I’ll put the “formal” terms in tooltips, but abstract the whole thing behind a “normalized” version that applies to all machines.

---

<div class="post-metadata">

**Author:** ![zaneclaes](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/zaneclaes/32/16801_2.png) [@zaneclaes](https://forums.maslowcnc.com/u/zaneclaes)\
**Post date:** [September 11, 2020, 9:47pm UTC](https://forums.maslowcnc.com/t/closed-beta-makerverse-previously-known-as-cncjs-support-for-all-maslow-editions-w-non-destructive-edge-calibration/14348/541 "2020-09-11T21:47:38Z")

</div>

Tinkering with this, here’s where I’m at…

Pause while running gcode:

 ![Screen Shot 2020-09-11 at 3.44.01 PM](https://canada1.discourse-cdn.com/flex031/uploads/maslowcnc/original/3X/1/a/1ab238401262a3dcec066893f464567d9f6cfb37.png)

No GCode loaded (idle):

 ![Screen Shot 2020-09-11 at 3.45.03 PM](https://canada1.discourse-cdn.com/flex031/uploads/maslowcnc/original/3X/0/5/05824a56d625cf9898cf237675172a2634ddd4da.png)

No GCode loaded (shuttling):

 ![Screen Shot 2020-09-11 at 3.45.34 PM](https://canada1.discourse-cdn.com/flex031/uploads/maslowcnc/original/3X/6/3/6355e503734231e8230a2e2fb7cf2655a6a1c88b.png)

No Gcode, paused while shuttling:  
 ![Screen Shot 2020-09-11 at 3.46.06 PM](https://canada1.discourse-cdn.com/flex031/uploads/maslowcnc/original/3X/9/3/93f034710bc3f16d32590ddc87bf9c1a0a5bc6dc.png)

Freshly uploaded some gcode:

 ![Screen Shot 2020-09-11 at 3.47.22 PM](https://canada1.discourse-cdn.com/flex031/uploads/maslowcnc/original/3X/e/2/e2d83c0e447c5c83f5f65f1613e26cac016fd250.png)

Alarm State:

 ![Screen Shot 2020-09-11 at 3.48.52 PM](https://canada1.discourse-cdn.com/flex031/uploads/maslowcnc/original/3X/3/4/345042b1e4ad2eab12a95980e784e6df7e3d4c0d.png)

---

<div class="post-metadata">

**Author:** ![Bob\_Craig](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/bob_craig/32/17242_2.png) [@Bob\_Craig](https://forums.maslowcnc.com/u/Bob_Craig)\
**Post date:** [September 11, 2020, 10:13pm UTC](https://forums.maslowcnc.com/t/closed-beta-makerverse-previously-known-as-cncjs-support-for-all-maslow-editions-w-non-destructive-edge-calibration/14348/542 "2020-09-11T22:13:16Z")

</div>

Looks like a great improvement.

---

<div class="post-metadata">

**Author:** ![Orob](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/orob/32/16344_2.png) [@Orob](https://forums.maslowcnc.com/u/Orob)\
**Post date:** [September 12, 2020, 1:12pm UTC](https://forums.maslowcnc.com/t/closed-beta-makerverse-previously-known-as-cncjs-support-for-all-maslow-editions-w-non-destructive-edge-calibration/14348/543 "2020-09-12T13:12:15Z")

</div>

why does the settings dock no longer show all the values?

 ![image](https://canada1.discourse-cdn.com/flex031/uploads/maslowcnc/original/3X/0/f/0f8d4c2de13fbea82ad3b89f3f518d163e48af9d.png)  
clicking on it does nothing. I want to see the calibrated values. I screen shotted them and it says I’m within 1.8 mm now, but when I go to the calibration sheet, they are hidden, so I can’t save them just in case. How can I find them?

[Previous page](https://forums.maslowcnc.com/t/closed-beta-makerverse-previously-known-as-cncjs-support-for-all-maslow-editions-w-non-destructive-edge-calibration/14348.md?page=26)

[Next page](https://forums.maslowcnc.com/t/closed-beta-makerverse-previously-known-as-cncjs-support-for-all-maslow-editions-w-non-destructive-edge-calibration/14348.md?page=28)
