[Public Release Thread] Makerverse is a Universal Controller App for CNC & 3DP (and includes Maslow upgrades)

Thanks Zane! I have learned a great deal about Raspberry Pi since 1.1.2 came out! Silver linings and all that

1 Like

I’m happy to report that the new image is working perfectly.

1 Like

And I really like the shortcut in the menu that pulls up a tablet version of the web browser makerverse

2 Likes

Glad to hear it! When I eventually find time, I want to make the debugging process easier. Those commands are far too archaic and hard to interpret right now… I’m sure I could find a way to make a single “status command”

1 Like

I have followed the instructions for the MakerVerse install per this post. I have a Mega Arduino board and followed the link to the Maslow firmware for my board. The link is for v. 1.26. I uploaded this version to my board and get this message window when I open MakerVerse:

image

So I remembered bringing this up in the past because the 1.26 firmware release from this link did not apparently have the Holey included. This is a snippet from that reply:

" Anywho, there’s your answer @thbart – instead of downloading the zip from the “Releases” page, use the green “Code” button to download the zip on this page ."

I downloaded the zip from the green “Code” button mentioned in the previous reply, uploaded to the Arduino board, and still get the 51.28 error.

Please help!!

@thbart that is not an error message. Your screenshot is merely stating the required version, not telling you that there is a problem. What happens when you actually try to open the connection?

@thbart I made a 90 second video of clicking on the link, unzipping, downloading the firmware, uploading, and then verifying that the correct firmware is installed. Notice how I use the serial monitor at the end to verify the correct version (type B05 and press enter): https://youtu.be/lIXKg5rsNuY

Im planning on switching my Maslow from WebControl over to Makerverse this weekend. Is like to also try Makerverse with my Creality Ender 5 plus 3d printer. I haven’t changed the firmware or upgraded anything to it, its all stock. Will Makerverse work with it or do I need to change something?

2 Likes

In theory, it should just work… if you can find the right settings. For example, my Prusa runs Marlin at a specific baud rate (which I forget). You can usually find these specs on the manufacturer website… and I think I remember reading the Ender is also Marlin.

I’m also working on a big update to the community catalog. Right now you only see Maslows as pre-configured options (and have to manually configure other machines). My goal is to support any and all machines.

Which is to say: I’d like to get the Ender series into this catalog :slight_smile:

I should mention that big gCode files (like 50mb) tend to cause Makerverse UI to struggle. This can be annoying with 3DP, but it does not affect the print quality. I’m going to devote time to the 3DP experience soon. That said, I’ve been running big MMU prints on my prusa for pretty much the last 5 days nonstop, so it definitely works :wink:

I thought I had everything working so I started a simple project. I generated the object in Autocad, exported to DXF and opened it in CAMBAM. I generated the gcode, uploaded it to makerverse. The maslow pauses for the tool change and when I press play again the machine moves to the start point, lowers the bit and freezes. I assume CAMBAM is generating non compatible GCode. Below is the gcode:
( Made using CamBam - http://www.cambam.co.uk )
( tv holder 11/7/2020 3:00:25 PM )
( Post-pro: GRBL )
( T0 : 6.35 )
G21 G90 G40
G0 Z3.0
( T0 : 6.35 )
T0 M6
( Profile1 )
G17
M3 S1000
G0 X-381.0 Y-282.58
G0 Z1.0
G1 F300.0 Z-6.3
G1 F1200.0 X-285.75
G3X-282.58Y-279.4I0.0J3.18
G1 Y25.4
G2X-281.93I0.32J0.0
G3X-278.75Y22.23I3.18J0.0
G1 X278.75
G3X281.93Y25.4I0.0J3.18
G2X282.58I0.32J0.0
G1 Y-279.4
G3X285.75Y-282.58I3.18J0.0
G1 X381.0
G3X384.18Y-279.4I0.0J3.18
G1 Y102.0
G3X356.0Y130.18I-28.18J0.0
G1 X101.2
G2X79.37Y152.0I0.0J21.83
G1 Y177.8
G3X76.2Y180.98I-3.18J0.0
G1 X-76.2
G3X-79.38Y177.8I0.0J-3.18
G1 X-79.37 Y152.0
G2X-101.2Y130.18I-21.83J0.0
G1 X-356.0
G3X-384.18Y102.0I0.0J-28.18
G1 Y-279.4
G3X-381.0Y-282.58I3.18J0.0
G1 F300.0 Z-12.6
G1 F1200.0 X-285.75
G3X-282.58Y-279.4I0.0J3.18
G1 Y25.4
G2X-281.93I0.32J0.0
G3X-278.75Y22.23I3.18J0.0
G1 X278.75
G3X281.93Y25.4I0.0J3.18
G2X282.58I0.32J0.0
G1 Y-279.4
G3X285.75Y-282.58I3.18J0.0
G1 X381.0
G3X384.18Y-279.4I0.0J3.18
G1 Y102.0
G3X356.0Y130.18I-28.18J0.0
G1 X101.2
G2X79.37Y152.0I0.0J21.83
G1 Y177.8
G3X76.2Y180.98I-3.18J0.0
G1 X-76.2
G3X-79.38Y177.8I0.0J-3.18
G1 X-79.37 Y152.0
G2X-101.2Y130.18I-21.83J0.0
G1 X-356.0
G3X-384.18Y102.0I0.0J-28.18
G1 Y-279.4
G3X-381.0Y-282.58I3.18J0.0
G1 F300.0 Z-19.2
G1 F1200.0 X-285.75
G3X-282.58Y-279.4I0.0J3.18
G1 Y25.4
G2X-281.93I0.32J0.0
G3X-278.75Y22.23I3.18J0.0
G1 X278.75
G3X281.93Y25.4I0.0J3.18
G2X282.58I0.32J0.0
G1 Y-279.4
G3X285.75Y-282.58I3.18J0.0
G1 X381.0
G3X384.18Y-279.4I0.0J3.18
G1 Y102.0
G3X356.0Y130.18I-28.18J0.0
G1 X101.2
G2X79.37Y152.0I0.0J21.83
G1 Y177.8
G3X76.2Y180.98I-3.18J0.0
G1 X-76.2
G3X-79.38Y177.8I0.0J-3.18
G1 X-79.37 Y152.0
G2X-101.2Y130.18I-21.83J0.0
G1 X-356.0
G3X-384.18Y102.0I0.0J-28.18
G1 Y-279.4
G3X-381.0Y-282.58I3.18J0.0
G0 Z3.0
M5
M30

What do I need to do to cut this simple project.

Is there some reason you’re trying to use automatic spindle control? Have you wired your Maslow shield appropriately, using a motor of some kind to adjust the router’s spindle speed?

I’m not familiar with CanBam, but you’re using a Grbl post as well as options which are unlikely to work with your machine. I’d recommend following a Maslow specific tutorial, if possible. There are lots of good tutorials on this forum, FWIW.

edit in general, a Grbl post-processor is not a problem. Easel, for example, exports for Maslow just fine — so you don’t need a Maslow specific post-processor. However, my above recommendation to follow Maslow specific tutorials is based upon the assumption you’re not yet familiar with settings like “automatic spindle control” and therefore would benefit from a tutorial of this nature.

Is there any way to change the elapsed time to exclude time while paused? I’ve been pausing long cuts overnight, but the elaspsed time seems to toll specifically based on the original start time. The remaining time seems to use the elapsed time to determine how much time is left based on the amount of g-code inputs left and the average time for each g-code input that has already happened.

TimeRemaining = GcodeRemaining / (TimeElapsed / GcodeSent)

TimeElapsed = CurrentTime - StartTime

Can we change TimeElapsed to exclude PausedTime?
[ TimeElapsed = CurrentTime - StartTime - PausedTime ]

1 Like

Or is there a better way to pause and resume the next day other than hitting pause?

Thanks for the suggestion. I’ll work this in to the visualizer / gcode improvements I’m working on. It all needs some attention; there are other oddities with the gcode widget as well :slight_smile:

Zane thanks for the response.

1 Like

All - I ran into a problem today with a series of cuts. I got an Abort during cycle error when my g-code shifted to a new toolpath. I tried to troubleshoot by shifting to starting points of new toolpaths at several different locations in the g-code. All were there same type of operation - “2D Contour”.

I’m not sure what the root cause is. I’m using:

  • Maslow classic with Ridgid Router
  • Makerverse v1.1.2 #252
  • The G-code was generated by Fusion 360 with the maslow post processor.

Here is the g-code from the beginning of the new toolpath to when it errors. It errors at line 33812:

33082 (WHEN USING FUSION 360 FOR PERSONAL USE, THE FEEDRATE OF )
33083 (RAPID MOVES IS REDUCED TO MATCH THE FEEDRATE OF CUTTING )
33084 (MOVES, WHICH CAN INCREASE MACHINING TIME. UNRESTRICTED )
33085 (RAPID MOVES ARE AVAILABLE WITH A FUSION 360 SUBSCRIPTION. )
33806
33807 (DESKTOP CENTER CUT OUT MAIN)
33808 G0 Z4
33809 G0 X289.993 Y400.426
33810 G1 Z3.5 F800.
33811 G1 Z-2.5 F16.
33812 G1 X246.993 F800.

Any thoughts on whether this is a Fusion 360 issue? or a Makerverse issue?

Thanks in advance,

Scott

I do not have a direct answer for your main question, but I have a question for you that may or may not have bearing on the issue as well as a comment:

Q: Is there a special reason why your plunge rate is 16 mmpm vs 800 mmpm for your movements?

C: Generally folks are using the grbl post processor because it makes fewer segments (according to what I’ve read, not what I’ve tried - take that if it is worth anything to you).

@Orob my understanding (beginner’s understanding) is that it is a calculated value in Fusion 360 based on Spindle Speed and Feed per RPM.

But, that doesn’t mean that it’s correct…

Scott

Hi. New user here.

I have the M2(not the brand new version). This forum is amazing.

I would like to see more information about what Makerverse has implemented in its workings.

Maybe it’s on here, but I’ve read sooo many threads all the way through and there is mostly information and ideas dating back years, it seems.

I’m hoping to find a sort of collection of the newest ideology/best practices and what Makerverse includes from all those fantastic ideas/experiences/experiments over the years. I do assume that would be quite a bit of work to try to create if even possible at all.

Another thought I had about Makerverse… When I was calibrating upwards of 50 times with the edge and precision calibration, I found myself wondering what the previous measurement were. I want to look at how calibration was affecting the error over “time”. I want to look for the general pattern of accuracy shifts and tendencies (e.g. are the top 3 measurements consistently showing an arc or tilt or whatever, do they show tell tale signs of a certain mechanical set up being off etc.). What I imagine is either simply creating a log in Makerverse of previous calibration information or complexly creating a sort of graphical interface that shows what shape the calibration measurements make and how they change through iterations of calibration. Perhaps I’ve simply not found that function yet.

Thanks for all the hard work and collaboration.

1 Like

Makerverse has only been around almost one year, so there isn’t that much history on it. Quick Maslow history 101: Bar invents Maslow, writes firmware for mega and Groundcontrol software. Eastbay Source, Metal masllow and Makermade sell kits and Bar no longer supplies kits. Madgrizzle writes webcontrol software and Holey calibration gets implemented. Ldcull and son write firmware for Arduino Due controller. Makermade releases M2 using Due and makes it work with CNCjs instead of groundcontrol or webcontrol for grbl compatability. CNCjs gets upgraded to become Makerverse by zaneclaes (during covid) and adds support to run mega systems with the intent to replace groundcontrol and webcontrol so all maslow systems work on makerverse.

5 Likes