Should both of the Stop buttons (the red stop icon and the config>Stop) stop the Maslow from moving?
What is the purpose of the UI that is located under the first tab at the top left? Can that be used safely?
If the belts get tangled because I used the wrong UI is there a way to untangle them without taking the stack apart?
I noticed that there are a ton of javascript errors in the console while running the GCODE. Are these a known issue or does it indicate that I have something wrong with my firmware/config/ui?
Explanation:
While running a GCODE I realized I had not homed the Z axis correctly. Instead of cutting the wood the router was just cutting atmosphere. I hit the red stop icon in the UI and the Maslow did not stop.
Then, I hit config and hit that stop button. Maslow did not stop.
Then I went to the other UI* and the pause button there did in fact pause movement.
Then, I went back to the Maslow UI and told the Maslow to move to the home position. I would not move.
I was trying to avoid taking the belts off and setting it back up again since I have been doing that for several hours. When the Maslow UI Home button didn’t move the Maslow home I had the bright idea to use the other UI. I hit the home button there and the Maslow tried to moved way too fast and tangled up all the belts.
*Maybe it’s called the GRBL UI? Anyways, screenshot of the UI I am talking about:
The Red stop button on the front screen will stop the Maslow, but any commands in the buffer will execute first. You can then make adjustments and restart the job. The Stop under the Config menu, causes machine to error out, and you have to power down and completely reset the Maslow. I recommend you get a stop button similar to what is on most bench saws etc for an emergency stop.See The Not Shop — Maslow
Usually not unfortunately, you may be able to tease out a simple tangle, but looking at yours I think not. The problem is with the motor engaged you can’t revolve the spool.
Yes, BUT a software stop button is never that reliable especially when something goes wrong so I recommend having the hardware estop button in the not shop to have a for sure way to stop the machine for safety.
Great question! That is left over from FluidNC. Ideally it will be fully removed at some point, but it is still useful sometimes. It can mostly be used safely, but it isn’t very well tested so use with caution.
Yes! Using that aforementioned secret UI under the first tab you can manually send commands to the machine the terminal at the bottom $BRO and $BRI will override everything that the machine is doing and command the bottom right motor to go in or out (depending on the command) with full power. It’s a pretty hidden feature because you can 100% break things that way.
I think that those are probably safe to ignore, but they are something that we would love to get fixed!
I was able to manually extrude the motor out to untangle the belts. Then I performed two calibrations which never actually calibrated. The loss was too high. Then on the third calibration the belts tangled again and got stuck in the upper gear which shredded it.
Going to order a new set of belts and try again.
I think taking the whole thing apart and replacing the belts will be a good step to hopefully fix any potential build mistakes.
