Finally back to trying to get my Maslow working properly. Just trying to do a simple engrave with a v-bit. Sled movement is very jerky and Makerverse status is constantly switching back and forth between “Run” and “Idle”. Almost seems to be idle more then running. Makerverse is running on an Rpi4 8gb. Not sure how to start troubleshooting.
Is the sled top center?
I’m running on a 6x10 waste board with a 12’ top beam and am cutting about a foot above center
do the motors run smoothly when you do ‘check motors’?
can you post a video showing the problem?
It’s a M2 so I’m running Makerverse. Never come across “check motors”.
I’ll try to post a video later today.
On a side note, the engraving also seems to have gotten deeper from one side to the other. Workpiece was 24"x24" with 18" worth of 1" tall engraving across the center. 60° v-bit ,1/8" depth.
you may get better support posting on facebook where they do their support. We
will try to help but are limited.
I don’t have Facebook. Don’t really want to create one just for this but guess I will if I can’t find a solution.
I understand, I’ve thrown away products when I found their only support was via
facebook. hopefully some other user will be able to help.
Yeah, wish I woulda known about the other options before I purchased one from them.
I asked about the position because if the motor chips get hot, they will stall and then turn on when they cool so it ends up being very jerky movement. Mine would stall in the summer and run for a long time in the winter, so I put a fan on the controller to take the heat from the cooling fins on the chips and it made a huge difference. That would be one easy avenue to check. A box fan or whatever you have might work just fine. Are you in a shop with AC or out in 100+ in a garage these days?
Here’s videos showing the Makerverse screen and the Maslow movement. Screen is a bit blurry but you can still make it out.
It’s currently 68° in my shop and that video was shot about three minutes after starting the gcode. Machine had been in sleep mode all night before that.
looks like we need to see a log of the communications between the maslow and the
I’m assuming you mean the communication logs from the Maslow to the rpi. How can I pull that?
I don’t know with the makermade software.
As far as I know the Due board only works with Makerverse. Wondering if I might be better off picking up a new controller from East Bay and dumping the Makermade one. Any reason you know of why that wouldn’t work?
Not sure what kind of benefits the Due board offers anyway. I know it took away the ability to be able to connect a z-probe.
Do you see the same behavior with every gcode file? It looks to me like somehow it’s struggling to send each line of gcode so it does one line and then waits…etc…but I don’t know much about that board or Makerverse so I’m really shooting in the dark
A couple questions:
- have you run this particular carve before?
- where did you generate the gcode? did you use a maslow or grbl post processor?
- I’d be interested in the section of code you showed in the video. I’m wondering if I could run it on my machine (air move it).
- What were you buying for only $200 you mentioned in the video? (jk)
one thing that can cause movement to appear to be jerky is if your corners are
rounded with lots of tiny line segments. A CAM program aimed at metal cutting
can do this and end up with a curve that’s a smaller diameter than your bit
becomes hundreds of lines of gcode.
The maslow is not a fast processor (although the M2 is faster than others) and
has a limit of how fast it can process lines, so what looks like a pause can
actually be it processing hundreds of tiny movements that are too small to
Lee has a gcode cleaner that will detect and filter out movements that are too
small (configurable) among other things. But you can also check if the corners
are sharp or rounded in your CAD and check how many segments you use to
represent curves in your CAM