Best I think we can get for the stop command. Not instant but pretty quick stopping. Please test and let me know of any problems encountered.
index.html.gz (133.9 KB)
firmware.bin (1.9 MB)
1 Like
This works well for me 
I’m ready to merge it, but I commented on the pull request to make sure that I’m merging the right one
This is the one:
Raise Z to safe height when stop is pressed
#846
Superseded:
#788 , #789 and #843, #844 can be closed
1 Like
Pause button now consistently pauses Maslow.
Fix pause button ignored during GCode command boundary transitions#850
Visual confirmation of Stop pressed
Visual feedback: Stop button turns orange on click, reverts on firmware acknowledgement#848
1 Like
Hi there! Anyone with similar issues to this GitHub issue: Excessive Belt Tension and Calibration Area Too Close to Anchors on Small Frame (Firmware 1.18–1.19)?
A few extra notes:
- The calibration lifts my sled slightly, this I also observe in 1.17 which I’m running now
- In version 1.18 - 1.19 when done calibrating; jogging the Maslow leads to a jumpy and uneven movement. I think this is also tension related.
The Maslowbot has made code suggestions and build a new firmware. This seemingly relieves the anchor issue but not the tension issue. I won’t pursue this further since I’m afraid that the mechanics/plastic parts in the Maslow will break.
All the best,
Lasse
Yes I also thought the orange looks a bit weird, but I didn’t want to make it too complicated, and at least you know it has registered.
1 Like
Send position data to new browser instances opened during GCode execution#858
This lets you take control of the Maslow after losing and re-establishing browser connection during GCode execution. It won’t display the GCode graphically, but you can see the movement and pause or stop the execution. This is in testing phase at the moment.
firmware.bin (1.9 MB)
index.html.gz (134.0 KB)
1 Like
Lasse wrote:
Hi there! Anyone with similar issues to this GitHub issue: Excessive Belt Tension and Calibration Area Too Close to Anchors on Small Frame (Firmware 1.18–1.19)?
A few extra notes:
- The calibration lifts my sled slightly, this I also observe in 1.17 which I’m running now
- In version 1.18 - 1.19 when done calibrating; jogging the Maslow leads to a jumpy and uneven movement. I think this is also tension related.
The Maslowbot has made code suggestions and build a new firmware. This seemingly relieves the anchor issue but not the tension issue. I won’t pursue this further since I’m afraid that the mechanics/plastic parts in the Maslow will break.
I’ve been offline the last few days and am a couple thousand emails behind at
the moment, did you see my post to github about my experience with small frames?
David Lang
@bar can you please put the latest firmware and index.html.gz files here for testing all changes together.
1 Like
I sure can! Here they are:
firmware.bin (1.9 MB)
index.html.gz (134.1 KB)
@bar Is there a timeout which lights the red led if power is on but no browser connected?
1 Like
There shouldn’t be, but I have also seen that behavior! My machine is usually in some sort of weird state because I’ve been testing something new so I thought that maybe it was something I triggered by unplugging an encoder and plugging it back in or something like that.
Sounds like a bug for sure to me!
Hay @dlang. Yes I saw your reply in the issue. I also responded, but I think you didn’t see it. In short here: My setup has been stable and working well in versions between approx 1.10 and 1.17. My anchors are all offset relatively to the height of the arms and also hasn’t been changed as of version 1.18. To me it seems something has changed causing more tension since version 1.18.
2 Likes
There is seemingly a bug on Maslow-Main that I haven’t run into before.
I was doing some testing today while cutting a sign and I had the machine sort of wander off twice. Both times it was moving quite slowly and both times the position readout on the UI was updating showing that it knew it was wandering off. Both times I was able to press stop and after stopping the machine behaved normally (no need to restart).
I went back to 1.19 and I didn’t seem to have the issue there so it seems like something new that we want to keep an eye on.
Yes, that’s part of what I am trying to chase down
1 Like
Excellent
It’s always good to know that I’m not the only one seeing something especially when I’m not quite sure how to reproduce it
Neither am I, but I suspect it has to do with short loss of communication with browser. Multiple short disconnection result in loss of position, power reset, retract etc so it’s hard to duplicate. i have seen it twice while testing.
1 Like
At least once for me it seemed to happen when I switched to another window to respond to something which would make sense
1 Like
Did you reload the GCode or just continue with what was in memory?
The fix for Error 66 broke the system. I have put in a change to reverse it and now don’t have the problem I experienced, No longer have the new browser window killing all connections and Maslow driving unpredictably.
1 Like