I just got an update for MC 2.0 this morning. Now at version 126.96.36.19916. Is there anywhere I can see the release notes? I assume this is a bugfix release, but what bugs?
Posts made by xeddog
MC 2.0 How to reset certain fields
I have been playing around with MC 2.0 (WHERE'S THE LINUX VERSION???), but I have been paying so much that I have screwed up a few of the settings. I would like to set SOME of them back to factory default, but not all of them. Is there a way to set individual settings back to default?
RE: How long to slice?
I did a little testing with different slicers today. All on the same machine, using settings as close to each other as I could get them, same models in same positions, nothing else running on the machine.
Cura 3.6 - 30 Seconds
IdeaMaker 188.8.131.523 - 20 seconds
Craftware 1.20 - 15 seconds
MatterControl 2.0 - 19 MINUTES
RE: mattercontrol update glitch
"Unfortunately", all is good now. The delete/re-install cleared up all of the operational problems I was having and now I am just wading through trying to find out how everything works. The unfortunate part is that I did not do any diagnosis at all so there is no information I can pass along. The only major issue I have now is NO LINUX VERSION 2. But I know it is being worked on.
How long to slice?
I have just started using MatterControl and like it, except for how long it takes to slice. I have used other slicers including Cura (many versions) Slic3r, Slic3rPE, IdeaMaker, and Craftware for a few. All of those slicers can slice a model, even a complicated model, in less than two minutes. MC on the other hand, takes tens of minutes. I currently have a slice going that has taken 20 minutes already and is only just half way done. It looks like there are several phases it goes through, but the really slow one is "Writing layers". Please tell me this isn't normal.
The machine is a desktop machine running Windows 10 Pro OS on an I7 processor with 16GB RAM. It's an older I7, maybe 3rd gen, but it handles the other slicers with ease, and Fusion 360 as well. With nothing else running on the machine, the task manager shows CPU utilization running 15-20%, memory usage relatively flat at around 30%, and Ethernet usage looks like a rather scraggly saw tooth bouncing between 0 and 50%.
RE: gcode coordinates outside of build area
Thanks, I'll see about going over to github and reporting this. It was, as you say, not a big deal since I realized later that I had sliced the model using a brim AND a skirt that was 5mm away from the print. I just removed the skirt and it is printing it's butt off as I type.
gcode coordinates outside of build area
I have a Monoprice Mini V1 that I have put several mods on. Right now it has a RAMPS 1.4 controller running Klipper, and I have a Z height increase so my build volume is now 120x120x160mm. These are the numbers used to define the printer to MC, and to Klipper as well.
Using MC 2.0, I loaded a model that took quite a bit of this space, but all fit within the 120x120 build plate with a little room to spare. I sliced it and exported the gcode file to Octoprint, and from Octoprint I started it printing. Very shortly after it started printing, I got an error from Klipper that said "... Reported error: Move out of range: 29.612 120.700 0.300 [60521.022]". Sure enough, this gcode command is in the file. "G1 X29.612 Y120.7 E10.23892"
This shows that when MC sliced the model, there is a Y coordinate of 120.700 which is outside the build area. This coordinate is the rearmost location of the skirt that MC added. I am assuming this is a bug since it seems to me like MC should not have allowed a coordinate outside the build area.
I'm still finding my way through the weeds when it comes to MC, so is there a place to report this, and a procedure?
RE: Layer view shows (or doesn't show) a lot of layers after slicing
I promise it is not because we are evil overlords.
RE: Changing Filament to different color during print
What firmware are you running on your printer? If Marlin, configure the advanced pause feature and then just use the M600 command. At the specified point, the printer will park the nozzle, retract a set amount of filament, and then wait. When you load the new filament you will be asked to continue and the extruder will purge the nozzle. When ready, resume will reposition the nozzle and it will start right where it left off.