By the way if you go to FluidNC settings, Config Items, you can set your work area, which will limit how far the Maslow will travel. Set the limits (say 2200 and 1000) inside your usable work area and test it with small jogs until it gets to the edge and it will stop before it runs over the edge. You can also use this to set an offset, if you wanted to move the whole set up down 10mm to avoid the excessive belt tension at the top.
1 Like
Ian,
Yes, our parts are in inches. I didn’t catch that the Maslow interface swapped to the units of the code. When jogging before a job it has always been in mm, so I set it to 50 mm to move it off the piece that was just cut. Thank you for pointing that change out. I also played with jogging the sled around the cut area for a minute. It was neat how it would go right up to the edge and then stop.
Once I have gotten some support materials to add to the outside of the standard cut area, and have gotten more comfortable I will probably adjust my cut area down to use more of the board at the top accurately.
Thank you for the tips.
2 Likes
here is the current Maslow-Main it should show as v1.17-121-g68d0a747
firmware.bin (1.9 MB)
index.html.gz (132.3 KB)
2 Likes
Do we feel like we’re ready for a firmware release?
We’ve had a lot of great changes recently
I haven’t had any problems testing recently, so yes.
Can we put a reminder in the update notes that an unexpected power reset mid-cut or Maslow entering Alarm State ALWAYS requires a Retract, Extend, Apply Tension and the ‘Z’ parameters need to be confirmed/reset before continuing.
Point out the changes to defining Home positioning.
here’s a minor tweak to v1.18 that exposes the spoilboard thickness and workpiece thickness settings (spoilboard thickness in settings → config workpiece thickness on the main screen)
for workpiece thickness, set just changes the setting until a reboot, save as default saves it to the maslow.yaml file
firmware.bin (1.9 MB)
index.html.gz (133.2 KB)
This is PR #836
firmware-package-font-fix.zip (1.3 MB)
here is a version that fixes the fonts on the buttons to scale properly with screen size (on my 4k screen, the 12px font was unreadably small)
It was calculating a responsive size, but then overriding it.
This needs people to test it on a variety of screen sizes. but since it uses the same size font that was used on the ‘pick gcode’ pulldown, it should be good.
@bar please check the files in the v1.18 release tarball, I updated a machine today and it got 1.18 for the firmware, but 1.17-something for the index.html.gz file
1 Like
Hi! Anyone else not being able to reach the web interface on the Maslow after installing version 1.18? I can connect to the Maslow wifi, but I’m not being redirected to the interface via the browser as usually. I’m sure that I’ve done the installation correctly. Version 1.16 works fine for me. Linux/Ubuntu/Google Chrome.
Lasse wrote:
Hi! Anyone else not being able to reach the web interface on the Maslow after
installing version 1.18? I can connect to the Maslow wifi, but I’m not being
redirected to the interface via the browser as usually. I’m sure that I’ve
done the installation correctly. Version 1.16 works fine for me.
Linux/Ubuntu/Google Chrome.
try it by IP address rather than name http://192.168.0.1
also, check if your browser is changing http to https https will not work
David Lang
Today I updated to version 1.18 and it showed me an error I don’t understand. Then, when I applied tension, it showed the same error
more than 1200 times
, saturating my screen before finally indicating that the machine was ready. I successfully ran my cutting file, but I don’t understand what the error means. Can someone please explain what it means and how to fix it?
I get same error, checking for problem #837
Try these updates:
index.html.gz (133.8 KB)
firmware.bin (1.9 MB)
It’s only relevant when actually running a GCode file, so this suppress the error when it is irrelevant.
2 Likes
@dlang yes visiting the IP address directly did the trick. Stupid I did not try that out before posting 
This pull request stops Maslow straight away when Stop clicked, raises the Z axis to 2mm above Z home and goes to Idle.
Raise Z to safe height when stop is pressed #846
Supersedes #788 and #789
2 Likes
Woah! I love that. I won’t be able to test it until tomorrow, but that sounds amazing 
It’s not quite an instant stop, it has to finish the last command so it stays synced with each belt axis to the actual encoder position
1 Like
Ian Abbott wrote:
It’s not quite an instant stop, it has to finish the last command so it stays
synced with each belt axis to the actual encoder position
at this point, how does it differ from pause?
I have expected that pause would be a graceful stop, keep everything synced so
that you can restart, but stop is a more drastic thing for “something went
wrong, I need things to stop NOW” emergency type situations.
If you start cutting the wrong thing, pause, reset (reload gcode) start.
but if you have to hit stop you have to re-home because the priority is stopping
motion
or, it could be we need an e-stop that is what I have been thinking stop is.
David Lang
Pause stops cutting, belt tension stays, bit stays where it was, you can’t change anything. You then click play and it resumes cutting.
Stop now completes the last command (it used to keep going until it emptied the buffer of commands) then stops and lifts the bit out of the material. You then can reset whatever and start again. At one stage I thought I had it stopping straight away, but when it does that it loses sync of where its at and needs a complete reset. Belts retracted, extended etc. If your situation is that bad then you just kill power, which still means that the damage is unpredictable to the material, as Maslow may lurch as the tension comes off the belts.
1 Like