All Activity

And this is the sort of thing that happens when I scramble late at night. The new "enable" box had a bug. This one doesn't have that particular bug. PauseAtLayer.zip

My good, old Ultimaker S5, which has been in use for almost 5 years, always on, suddenly died this night. It completed a print last night. This morning the screen was black, no light, totally dead. I checked the power button, the cable etc, but it's not something external to the printer. Since is not reacting at all to the power button, I guess a fuse has blown. Has anyone experienced the same? Any tips on what it could be? Marius

Well you can approach this from one of two directions (as literally as possible), I prefer the "scorched earth" approach myself. Go to %APPDATA% and rename the entire cura folder so it's forced to generate a completely new config from a blank slate. If you're using a custom printer definition, open Cura, then just quit it and put your definition in the %APPDATA%\cura\5.7 (definitions and variants if necessary, if you have a custom definition then you've already done this) folder it should have created so you can open it again and your printer will be in the list to add. Anyways, set up your printer. Get a model which won't slice (if you want one from the calibration shapes plugin, then go to the configuration folder you just moved out of the way and they're in plugins\CalibrationShapes\CalibrationShapes\models\) and see if it'll slice. If it doesn't, then either your custom printer definition is causing it or you have bigger problems. Then it's basically a matter of "close Cura, copy something from previous configuration folder into new one, open Cura, test". If it stops slicing after you copy something, you've found your culprit. Personally I'd test in this order: cura.cfg (overwrite the new one it made) If your printer setup differs from its definition (you've changed some of its settings in Cura) then the changes will be in a file in the definitions_changes folder, so that All the post-processing scripts (which should have nothing to do with it, but computer programs break in mysterious ways) Any custom/changed materials (just the whole materials folder), although if it's happening with a generic material it's probably not this All your quality settings profiles (they're in the quality_changes folder) and then test with those profiles Plugins. Ideally, one at a time. Yes, I know it can take a bit of time if you have a few (I have plenty). To cheat, you can do it about three at a time, just remember which three in case it breaks it you can uninstall those three and test individually. For ones you can find in the Marketplace, download them from there, if something is no longer listed there, copy it from the plugins folder in your old config folder. Then... that's about everything covered. If it works after that, you probably had a bum configuration file somewhere. And when I say you can approach it from the other direction: that's starting with what you have now and removing things individually until it works. But I prefer to do it from the ground up in case of things like aforementioned bum configuration file somewhere which you wouldn't get around to removing.

That's brill @GregValiant I'll check out the new version & thanks for your continued plugin work

Thanks! Ill give this a try

OK. What do I do next to diagnose this. I don't want to wall myself off from Cura updates.

No... it's obviously fine. heh.

Alas, you are correct. You could try it with a file with regular supports but open the gcode file in Cura so you can see what the preview looks like before you try and print it.

In theory, it's going by layer number in the Cura preview, which starts at 1, but in the gcode the layers start at 0, so I subtract one from the value you put in the settings (because what the Cura preview says is layer 250 is labelled layer 249 in the gcode, but it is in actuality the 250th layer). I can change it if you want. Whenever I do a script for someone I always want to have a happy customer.

When I've done my art prints from the SD card on my E3V3SE, M0 worked fine. The screen didn't update to say it was paused (blame Creality's crappy firmware - it won't even display messages sent with an M117) but just pushing the control knob resumed it. When I've done it using OctoPrint (from storage on the OctoPrint server), it automatically blocks the M0 command and just doesn't send any further instructions to the printer until you click the resume button in the web interface. Actually pretty inconvenient compared to just pushing the button on the printer. I've never tried running it through OctoPrint with the gcode on the SD card. Stop trying to complicate things. I was referring exclusively to printing through Cura, since the concept of USB printing as a whole cannot be deprecated and the printer does still support it then logically I must not have been referring to the system as a whole.

Okay, scratch that "can't remember why": it's "machine_nozzle_tip_outer_diameter" in the machine definition. Most files don't overwrite it so they just use the value from fdmprinter (the base definition almost all machines are based on) which is 1. If I override it in my machine definition to 0.0, then I can get my cube up to 219.9x219.9mm on my 220x220mm build plate:

I think there is a small disallowed area around the edge (look at the dark grey) by default but I can't remember why off the top of my head (I'm using a custom definition for my E3V3SE so I know there's no disallowed areas):

M25 works on some of the Creality machines. There is a glitch between the mainboard firmware and the LCD firmware that keeps commands that send messages to the LCD from working. Some printers required a string of "do nothing" commands in the "Gcode after Pause" box. The usual fix is to enter a string of M105 commands as M105,M105,M105,M105,M105. That insured that if the processor does a "read ahead" that it just sees temperature requests rather than any movement commands. Your M300 is the same sort of thing, just noisier. Since you are using a couple of my post processors, here is my replacement for "Pause at Height". Among other changes it has a checkbox to "disable" it without having to remove it from the list. There are also new Unload, Reload, and Purge settings. Let me know if there are any bugs. At some point I'll put in a pull request to include this in Cura, but it needs more people to play with it before that happens. PauseAtLayer.zip

Well that's pretty bizarre. When you installed your printer in Cura which definition did you use? When I open that project file it uses a standard Ender 3 with a bigger bed. Here is a project file with your model. The printer name is slightly different. If you get an option to allow Cura to install a new printer - do it. If you have done any customizing to your printer setup in Cura (StartUp Gcode, etc.) you don't want it to get over-written by this project file. GV Exhaust vent bottom modified.3mf

I removed 5.7.0 and all its data files including the ones under AppDate then installed 5.7.1 It still won't accept the file at 100%. If I try to scale down from 100% to 99% it won't work. But if I scale it down to 95% then scale it up one percent at a time I can get it to 99% but not 100%.

On that model I think setting it to "Sharpest Corner" and "Smart Hiding" looks pretty good. The seams get tucked into the notches. There will be some oddities like the I.D. where there isn't any corner for the seam.

Ha! I'm retired so I check the computer numerous times a day. I'm also not shy. It's odd that they are re-setting the "flow" for Extruder 1 but not Extruder 2. I recall that the firmware is different, but I don't recall exactly how it differs. The only Raise3D machine I fooled with was the E2 IDEX printer. If you happen to do a test print (calibration cube or something) then add the additional lines of code. For right now if it's printing well (other than the speed thing) leave it alone. For a test print - directly below the M221 T0 S100 I'd put: M221 T1 S100 M220 T0 S100 M220 T1 S100 Like I said, these are just safeties that are there to ensure that the printer starts with it's defaults, and not with some random manual setting that was made during a previous print. "Minimum Layer Time" is in the Cura "Cooling" settings. It's function is to slow a print down so each layer has time to harden before the nozzle comes back around.

Hi, One of my mates asked me to print a model on Printables. The model has seam notches to sort out seams. In PrusaSlicer the seams fall nicely into the notch. How can I achieve the same in Cura? Here is the printables model with a seam notch. Thanks in advance!

@Slashee_the_Cow I'm assuming I can't use generated supports, especially tree supports.

Thanks for the quick response. And just in general, I see your advice in like half the forum posts I read. I looked back at the start and end gcode I have been using and I only see M221 T0 S100, should I add a line above that reads, "M22 T0 S100" ? I'll investigate minimum layer time as well.

It's close ... I can work with that, but to be completely pedantic about it, setting the layer to 250 makes it stop wiping on 249. 🤔

I've never seen any problems with the way Cura puts the speeds in. I just did a slice with your numbers and 100 outer wall and 120 inner wall is what showed up in the gcode. Cura does take the "layer time" into consideration. If any layer is going to take less than "Minimum Layer Time" the speeds will be adjusted downward until "Minimum Speed" is hit. At that point Cura won't make any further downward adjustments. The speed modifier is M220 S and the S parameter is in percent. Make sure you have an M220 S100 and M221 S100 (flow rate) in your StartUp Gcode. If you happen to have tuned the flow and/or feedrate during a previous print those two lines will ensure that the printer sets itself back to default when a new print starts. I had to make this cube larger so it wouldn't bounce off the Minimum Layer Time.

Thanks GregValiant and everyone else involved. I was able to get this up and running on my Pro 2 Plus. The only setting I have that is behaving weirdly are some of the speeds. For instance, with settings of 100mm/s outer wall and 120 mm/s inner wall, I am instead getting what appears to be, 2 passes of 50 mm/s inner wall speed, followed by 100 mm/s outer wall. After that it actually does a single line of the infill at speed, and then drops into a slower pace. My best guess is that this is either some form of translation issue for how it reads some gcode commands, or some sort of more experimental setting that got turned on somewhere? When viewing the gcode in both Ideamaker and PrusaSlicer, it shows the speeds I put in, so presumably its something to do with the machine. It's not a hard limit though, it gets up to speed, but just in the wrong order. And I've printed at these speeds on this machine out of ideamaker. If anyone has some advice or experience getting all the settings to behave correctly it would be much appreciated.

I am using 5.7.0. I'll try 5.7.1 Thanks!

Every so often I've been using pause at height script on my S1 Pro. I found using M0 didn't work but the using this configuration works for me when either printing from SD or via my BeagleCam (Thanks Rick Impey) . FYI The Pause Layer of 99999 is just my way of disabling a pause when I'm not wanting to use it so that I don't have to delete & add the script again between uses. I've also read of a strange bug that sometimes happens where when the printer pauses it continues to display the pause button instead of the resume button. Although I haven't experienced it I understand the workaround is to select one of the fields on the home screen as though you were going to change the value but exit without changing anything & the resume button should now be displayed Missed a bit of config off the capture