How do you mean? What did you press?
It is normal for this message to appear for 1-2 seconds while connecting. Or does it get stuck this way? You have to disconnect?
Calibrate button?
This happens when you reconnect a motor without restarting the Arduino. Disconnect your Arduino from USB and power, then reconnect.
Do you mean it stays that way? It sometimes happens for a second or two while connecting for me, but it never gets stuck that way. It should especially NOT happen when you see Connection was already open (since it already should know the version).
It’s not repeatable, so difficult to tell. Seems only at the first start of the day, but does stay more then a few seconds. The RX on the Meaga blinks, so a connection is there and the controller setting (from i) show all values, so the connection is there. I’ll just wait longer next time to find out.
OK, I have to ask what I suspect is a very newbie question…
Now that the software is running for me, I started to do the calibration. However, my sled wasn’t exactly centered so I got out of Calibration to jog the sled.
However, no matter what job button I press (X-, X+, Y-, Y+) the sled jumps slightly up vertically and stops. In the console, I get this alarm (similar alarm for any of the 4 options).
Any suggestions where I should start?
This is how Makerverse reports the “sled not keeping up with motors.” Usually for me this means a wire is loose. There are other occasional causes, like too much force on the motors – but these are much more rare. In general, it means that the PCB cannot guarantee that the motors have actually rotated the requested amount.
For me, this is an indicator that the Machine Setting “Height” has reset to less than 12 in. The error can usually be cleared by adjusting the height back to 48.
This isn’t a cable issue (I confirmed all are seated properly). I power cycled the Arduino/Shield and closed/opened the connection to it. After that, the job buttons did work properly and I was able to center my sled on the work area.
Then I went to do the calibration again, I got to the Edge Calibration tab, clicked Move to go to Upper Center and the sled just jumped a few mm, then stopped. At that point, everything is foobar-ed again. Now when I try to jog in any direction the sled goes straight up.
It seems some of the configuration settings are getting squashed. After fixing some of the obviously wrong settings (i.e. motor width was set to 16mm), I got control of the machine again and have been able to start the calibration process.
It does seem that there is something going on causing settings to get trashed, though.
4x4 workspace: calibration shown above +/- 10 mm with most within 2 mm. Calibrated with 1/8" 2 flute upcut bit. first cut looks ok except the last pass it did something unexpected and it was a gcode problem, so the nick on thr right was my fault, not a calibration issue. Painted, sanded and the gcode needs to be greatly simplified to clean it up, but it looks like what was intended.
Cut #2. Uploaded a design: like this:
Started the cut and got this:
I moved the machine to far left and pressed set home so the cut would be centered on the sheet. Perhaps I’m doing it wrong, but this is waaay out there.
took the same gcode, dropped it into webcontrol and it is cranking the second one now. I guess by having the drawing home in the lower left corner, setting home there like in webcontrol is a very bad thing to do. One must offset the workspace somehow. Guess I need to read that book about that spanish guy named Manual.
I can’t tell from your Makerverse screenshot what you WPos was. This is what determines where something is printed.
I’d recommend setting workspace dimensions. Then you can see exactly on the board where it will print. Sometimes the gCode has an origin in the lower left, sometimes in the center. In any case, the Work Pos (WPos) is the only thing you should change. That’s how you choose where the origin of the print will be aligned. And if you set the workspace area you can see the edges of the stock.
For example, here my WPos is centered (because WPos = MPos, it means my print is aligned at 0,0). And I have workspace dimensions (configured in settings) that show me the stock:
I need to figure out where this is coming from. It hasn’t happened to me yet. If you can spot any pattern as to when/what happens please let me know.
I’m going to work on better UI tomorrow for changing settings. I think part of the problem is that the Maslow will reject the change when certain things are happening (like sled moving). My best guess with the “wrong value” problem is something to do with imperial vs. metric (I usually test in metric, will test imperial tomorrow).
I could not find the calibration button to save my life.
I could not get it to clear, even with reset. The only time it wasn’t there was when I had the Rpi and Ardunio/shield setup unplugged form the motors and sitting on my desk.
Could not find it at all. Thought I collapsed and expanded every single box and menu I could find. Even when it was up and in front of me, it wasn’t taking input. Does it require the motor cables to be present in order to take input?
@zaneclaes - is the new MetalMaslow setting in Calibration designed for MetalMaslow’s new square sled or old round one? If the square one, I assume the sled needs to be leveled before measuring distances.
Did you look at my screenshot in my reply to you? It’s the only button in the Maslow panel, and is always visible on your screen. Here’s the screenshot again:
square – sorry, didn’t realize they hay a round one. I do find it handy to level ANY sled before measuring, personally. But it’s extremely easy and obvious with the square metal sled. Just try to align the entire edge with the edge of the stock. No need for an actual leveling device.
Yes, I saw the button. I didn’t see it when I had the boards inside and working and I also didn’t see it once I hooked them both back up to the motors. Next time I give makerverse a spin I’ll see if I can find it and make it take input but after spending a frustrating 2 or 3 minutes shuffling through menus looking for it, I gave up. Hopefully that’s good UX feedback, maybe not. As I said early on, I’m in the lowest rung of Rpi user and need the “for dummies” type instructions. Next run should go better but I’m back to webcontrol for now so I can make some cuts.
Oh, sorry, I misunderstood your most recent most to mean that you still hadn’t found it.
Yeah, the UX thing is always hard. I could have made it more obvious (blue, yellow, etc.)… but then again, the Calibration button is something you need at the beginning when setting up, but (hopefully) never again afterwards…
New update uploading now (build #205). This adds a lot of safety around applying settings. Whenever you edit settings, it will make sure to stop the machine, unlock, and wait for the settings to be applied. I hope this will help with some of the problems around settings not being changed correctly.
Though, as I said before, the fact that some settings are changing to “weird” values may be a different issue. So please do let me know if you see that keep happening, and if perhaps you’re using imperial measurements.
Minor bug report. RemoteAccess status seems wrong in the About area. This is being shown in the UI on my Mac while Makerverse is running on my Pi. ‘allowRemoteAccess’ is ‘true’ in .makerverse.
Good catch. I actually fixed that in the release that came out ~4h ago (post above yours).
I’m going to go mess with calibration more myself and see if I can recreate any more bugs.
