Using an 1\8" bit in an adaptor. I really struggled. User error on the adaptor. Two test cuts garbage because my bit kept pushing up as the router went down.
Small lettering has some curved corners on the lower right. Otherwise it seems good.
My main issue really is the web interface. I can’t reconnect after an e-stop. So I kept hanging to switch between my phone and my laptop to connect.
And of course after any issue, it’s unhook, retract all, extend all… Ugh. That really is the worst. Not sure if this has a tilt sensor on the board and but a couple times I got too close to the edge and it tilted and e-stopped. Then the whole cycle again…
So right now I use makerverse or something like that to run the M2. Do you use a similar program? Would it work the same whether it’s wireless or wired?
So right now I use makerverse or something like that to run the M2. Do you
use a similar program? Would it work the same whether it¢s wireless or wired?
it will be very different. using a wifi network you are connecting to a web page
so all you need is a browser
if you connect via USB, you are connecting to a serial port, so you need
something like the universal gcode sender program to talk to the machine
David Lang
P.S. the maslow 4 does not have any wired ethernet, those rj-45 plugs are just
connections to the encoders, not ethernet
Basically you just open your computer and type maslow.local into the web browser. That will take you to a page which looks very similar to makerverse. No internet connection (or login) required, it will work with your computer connected directly to the machine.
The underlying technology is quite different from Makerverse, but in practice the user experience is almost exactly the same except there is no cord needed.
Until we get that heartbeat message out, this is pretty annoying to do though. In other programs the heartbeats quickly fill up the screen with heartbeat messages. If you end up releasing my latest ui changes, you can safely remove the heartbeat as the new ui starts using the fluidnc websocket pings instead which does not need anything in the serial messages to listen for.
Great! Note that I have not done a PR to fluidNC to stop the message yet though. Do you want a PR for just that? I do have one to add $MINFO out there I could add it to or create another…
I just merged it in. I’m sorry it took me so long, for some reason sometimes I’m not getting notified when pull requests are created to that repository so I didn’t notice until I went to make my own PR to it
sounds good, can we add a comment out of the heartbeat call in maslow.cpp (I didn’t have that in a pr yet). if its too late for this week, no worries, I’ll do a pr for it if it is.
Just released this week’s but I can merge that PR ASAP if you make one. I’ve got some things I want to do tomorrow which will probably result in an interstitial release so 0.74.1 will be out tomorrow I think
Hi Merlin - what hardware did you use for anchors in your concrete slab. Are they removeable?
I am planning similar install but use my shop floor for many things so need to remove the anchors when not in use. Most typical concrete anchors are one use only so I was thinking to epoxy a 3/8" connector nut into my slab and then to thread 3/6 bolt when using my maslow4.
I used “drop in” concrete anchors. You drill holes into the concrete . These sit flush or lower than the concrete floor. Then you can thread in bolts to hold the belts.
