What are your slicer settings? And what size nozzle are you using? I checked it again on my end and am not getting any slicing errors or gaps like that.
2 Likes
0.4 nozzle and 0.15 layer height. All standard. The wall is just too thin. This is the second time I’ve disassembled the whole thing so am just going to live with it for now.
2 Likes
@Ghinton Check your messages.
2 Likes
Any chance of a CAD file for the belt guard? I’m more of a “make it solid” kinda guy 
Plus, then I’m making parts instead of supports…
3 Likes
Absolutely, here is a .step file
Belt Guard.step (311.7 KB)
2 Likes
I don’t know if this is interesting for you or if it’s known problem, but my belts got jammed into the gears AFTER calibration, when i was trying to get a routerbit in it. i was raising z-axis and then all of a sudden things went crazy, belts were loosend and tightend in a quite random looking order. even single belts were loosen and tighten “randomly” so since i only have two hands, 2 belst got into the gears.
1 Like
Similar thing happened with me today, I retracted the belts, extended belts and mounted the maslow on the frame, then tensioned. When clicked on the Z access raise button, all the belts went loose then started to unspool completely. One got caught and suffered some damage, but not enough to stop it from working. I had set the Z access to rise 30 mm. I have also noticed a similar situation when calibration fails and any attempt to move the Z axis causes unspooling of 2 belts and pulling on opposing belts.
1 Like
was that 30mm or 30 inches? 30 inches would unspool a lot (we really need to
implement the soft limit for Z)
David Lang
1 Like
Which firmware version are you running? I know that some of the early versions had this issue, but it should be fixed
1 Like
30mm, it shouldn’t have unspooled much at all to compensate for the raising of the Z axis
2 Likes
Latest as of last week V 77
2 Likes
Was this with the belts extended but not hooked to the frame yet?
1 Like
Belts on frame, haven’t been game to mount a bit in yet, but have run the M4 with your Maslow file, and it appeared to work as expected. This was after that when the machine had been disconnected, and I had reconnected, retracted belts, extended belts, put on frame, tensioned then went to Z menu to raise the M4, and the machine just kept running out the belts. Bottom right belt was damaged about 400mm from the spool (which is not normally unwound, I have left the belts at full length).
I have ordered new belts from the store (just in case)
I then retracted all, BL did nor retract, extended all and pulled out BL only all the way, cycled power, retracted all again BL retracted. Extended all, remounted, set up camera to record and M4 now worked as is supposed to. Frustrating.
2 Likes
Hmm that’s unexpected.
When the zaxis moves it will attempt to tension the other belts too and if there is no opposing force for the motors to pull against they can unspool like that, but that usually only happens if the belts are not connected to the frame which tensions them
1 Like
Was running a simple file today, basically 2 triangles. Noticed that one of the belts unwound as the bit went into safety position before moving to the start position. Belt kept going to the point where it bound up and damaged an inch and half of belt.
Was able to loosen it all up and get it to pull in again. The damage is well inside the spool so never comes near the gears in normal operation, so should be able to operate if we can figure out why it unspools like that.
I am running the v0.78.1 firmware. Calibration completed successfully.
I see that others have seen this strange unspooling. I get that it needs to do some so as the bit rises the tension is kept constant, but this just kept coming out until it bound up. Had to pull the power to get it to stop.
2 Likes
There’s two ways that I can see that happening.
-
Its a bug and that motor went rogue for some reason
-
That belt needed to feed out some small amount of belt (say 1mm) but there wasn’t any tension to pull on it. Without tension to pull the belt out when the motor spins no belt extends so it keeps spinning.
Did that belt seem too slack at the time when it happened?
1 Like
There was tension on the belt before the bit went up and the sled started to move to the start position, so tension there again. I am going to try an older version of the firmware tonight to see if maybe it is a “new” bug in the latest version.
3 Likes
Just wanted to follow-up on this one in case anyone was waiting to see what I found. I ended up downgrading the firmware to v0.77 and was able to start cutting, but not for very long. I kept getting a failures due to resets due to GCODE. I generated the GCODE out of FreeCAD, so decided to invest in Easel Pro for a year and see what I could get.
I use FreeCAD to design the piece and Easel to prep it and generate GCODE. The good news, it works. I was able to cut a few pieces. The bad news, still get random errors about too much current on one of the motors or the occasional reset.
At the same time, I ordered a new belt so I can replace the one that got chewed up. Though the problem area is far enough from the end that most of working area of the Maslow is not affected, I am hearing strange sounds coming from the particular drive motor and belt.
More to learn, more to do, but again, wanted to update on what I found. Anyone know when the next firmware release will make its way out?
2 Likes
Fusion 360 can create the proper gcode for the maslow, the question there is
what machine you tell fusion that it is creating gcode for. There is a lot of
variation in what gcode machines can take. It should be that grbl will work
David Lang
2 Likes
FreeCAD does allow for grbl for generating the code. I probably have a parameter set incorrectly somewhere, but in the Easel has some other features that I was interested in using.
2 Likes