Feedback after one month using the maslow

Uncategorized
1

i would like to share my experience after my first weeks with the maslow.

i have done three proper sessions with it: first about 4 days, then 2 days, and now my third one. And finally i feel like i understand the beast

The beggining was frustrating, adjusting the frame, calibration, belts, tensions problems, Z issues, job stopping, trying to understand if the problem was the machine, the software, the G code or simply me.

But now my physical setup is solid, i understand much better how the machien behave, and i#m getting confident troubleshooting it.

I have also learned a few habits: check and tighten everything regulary, keep an eye on the belts, split complicated job into smaller ones when possible.

There is definitvely a learning curve, and still think software/error handling could be more begginer friendly. But once everything is dialled in, the maslow is a pretty impressive machine.

I started with a angle setup. My first big lesson: better work horizontally. second if you want try diagonalyou really need a LARGE frame. Mine is about 3960 x 2910mm. With a smaller geometry, things can become strange very quickly, especially near the edges, and i had situations where the machine wanted to lift away from the workpiece.

After a lot of testing i switched to horizontal setup. For me, this changed everything. I could maximize the usable dimension, and i also increased the belt extension limit in the settings.

I had some mechanical problems too. Some of the belt / motor retaining parts broke, both upper and lower ones. I still dont understand why. I had to 3d print replacements.

dust extraction is very important. Everything works much cleaner especially horizontally. I had to put a big fan to cool down my vacuum.

one thing that would be helpful is and ai agent that would help the users. i made one for my use that i feed with forum and website but if it was properly trained it would be amazing.

2 Likes
2

Fabien, this part made me laugh:

“trying to understand if the problem was the machine, the software, the G code or simply me.”
Welcome to the club. :grinning_face_with_smiling_eyes:
Some of us apparently prefer the advanced version, where we spend six days investigating firmware, kinematics, calibration, encoders, and every mathematical possibility imaginable—before finally putting a ruler next to the machine and discovering what a 30-second sanity check could have told us.
Your post actually describes something I think is important as Maslow continues developing.
You eventually “understood the beast.” You learned what to check, what different symptoms mean, when to look at belts, when to question the frame, when to question G-code, and when something simply doesn’t feel mechanically right.
That’s valuable knowledge. The next new user shouldn’t necessarily have to earn all of it the same painful way.
A few of us have been looking at this from the development side as well. Rather than adding more pages of troubleshooting instructions, I’m becoming increasingly interested in simple preflight and sanity diagnostics:
Find Anchors → Preflight → Ready / Warning → Cut
If Maslow already has enough information to recognize that something doesn’t look right, tell the user. If it doesn’t have enough information, tell them the simplest physical check that will separate the possibilities.
Sometimes that might literally amount to: “Move 300 mm and measure it with a ruler.”
Not particularly glamorous engineering, but neither is spending six days discovering you should have used the ruler. :grinning_face_with_smiling_eyes:
Your suggestion of an AI agent is interesting for exactly this reason. I think it becomes much more powerful if the machine itself can first provide good diagnostic evidence. Then the AI isn’t guessing from “my circle looks like an oval”—it’s helping interpret what Maslow actually observed.
So please keep posting the weird behavior, failures, fixes, and lessons learned.
For those of us experimenting with and contributing ideas toward future development, your frustrating first month is useful data. Every rabbit hole somebody documents is one we have an opportunity to keep the next Maslow user from falling into.

Charlie | MR2QUIK

3

I couldn’t agree more. I am working on updating our fork of FluidNC to the latest version in the hopes that it’s a little easier to work with, but if it’s not I think we might want to look at other options. Overall I think this is one of the biggest hurdles that we need to tackle.