That extra section you mention - how to use the events - may be need examples of other things you can do with events such as turn off the machine, reboot the machine, restart makerverse, etc.
I thought gcode stop was if you stopped it manually.
Is there a gcode line counter that indicates which gcode line the system is cutting? One of the webcontrol features that was useful was the line step command that allowed the user to move through the gcode and pick a starting point. We don’t have to have that, but if we had an indication of where the last cut line was, it would be easier to recover if something goes south.
I’m not 100% certain. I think that the stop event fires with Grbl/Maslow when the program completes, but not with Marlin, because the “play” button becomes active again with Grbl/Maslow when the program is done (but not with Marlin, it just hangs in the “playing” state at the end).
I’ll investigate more deeply soon.
Yes. The Gcode widget does this (sent/received):
You’re right, I really loved that feature too, but forgot about it because it didn’t work when I used WebControl on my phone. I’ll add this (“skip forward/backward or to a given line number”) to the Gcode widget and get it in for the public release
gcode finish event would trigger and then it would be followed by system ready, so a finish event probably isn’t needed if the system ready indication is the end/idle state after a completed gcode job.
Wouldn’t a system ready also fire on connect, etc.? Seems like you’d want to be able to have an event specifically when the program ends. You could send yourself a text message or something
The new versions of the RPi image now come with the remote GPIO pre-enabled, and the gpio.sh script pre-installed, so all you have to do is create the command The new versions of the image also come with the shopfloor tablet UI built in. You just add /tablet to the URL (see docs).
@Bob_Craig if you don’t want to re-install the image to get the shopfloor tablet UI, you should be able to run this from within the RPi:
Then manually edit your .makerverse file to add the following JSON to the third line of the file (coming right after the opening "watchDirectory" line):
Finally, restart Makerverse. You should then be able to use http://makerverse.local:8000/tablet. If you want the kiosk to automatically start with the tablet UI, see the docs.
@zaneclaes - Cool about the tablet addon - I’ll load it up!
Related to workspace limits, are they being enforced? I’ve gotten burned twice in a couple days with the Jog increment getting set to some large number (i.e. 100mm) and then forgetting it when I go to jog my z-axis slightly before moving the sled. In those cases, I’ve had to “reset” to stop the motor from banging on the end-stops. I thought, once I had the workspace limits set up, that the software would prevent exceeding the physical machine limits even if the command asks to do it.
Good point. I cut a good 100 mm beyond the right work space limit once and rather than stop it i helped it manually and it finished ok, but it should have stopped. I was wondering when it would error out and it never did.
Yes, I am on Mega. How would the firmware enforce Z-axis limits? Is it part of the configuration? Z-axis can so variable because of the various Z-axis improvements out there.
The maslow (mega) firmware only enforces x,y limits as @zaneclaes said… In order to do software limits on z-axis, I think you would need three settings added; minimum z, maximum z, and distance router bit extends from router collet.
we added user settings for z limits to the firmware in april in the mega. The Due has the soft limits, but they aren’t end stops, but based on a center-point and if it goes out of the limits, you have to disable the limits to bring it back to reset it.
@zaneclaes - I just loaded build 241 but the tablet UI is not working. I tried the URLs you shared above and also added “/tablet” to the URL of my open workspace. None of them will load.
In the last post, I mentioned you need to either (1) re-download and flash the Rasperry Pi image with the latest version (from scratch) or (2) follow the instructions to install the tablet UI. Did you do one of those two things?
Sorry, yeah, it’s a non-standard update process since I had to bundle a few new things into the Raspberry Pi image and make changes to the .makerverse file. Eventually I’ll build the “add-on” feature so this can be done within the app, but right now adding a widget is fairly cumbersome (which is why I re-built the RPi image with it pre-installed).
The Tablet UI does work after installing via the command-line. I agree with your past comments - there is a lot of opportunity for improvement in that experience.
I just noticed a UI bug in the work surface rendering. As my sled is cutting, the design moves around with the sled position instead of the design staying fixed and the sled position updating its location in the design. This is using #241.
The new versions of the image also come with the shopfloor tablet UI built in. You just add 