Many thanks.
I have tried it and yep spot on. it now does what I want it to do but found that it didn't wait for the temperature to stabilise before it printed.
so I added a M109 command with a {if new tool} entry infront of it and now it does what I want it to do. change tool using idle temps and wait for it to heat up. winner.
would I need to add retraction settings in there or will it go by the start script of the GCode file?
Many thanks.
I have tried it and yep spot on. it now does what I want it to do but found that it didn't wait for the temperature to stabilise before it printed.
so I added a M109 command with a {if new tool} entry infront of it and now it does what I want it to do. change tool using idle temps and wait for it to heat up. winner.
would I need to add retraction settings in there or will it go by the start script of the GCode file?
Not sure. I mean, I did msg Simplify3d almost a year ago about their um3 profile and they didn’t care/lissen and they answered with a ‘yeah ueah we know’. They use a weird way of solving the tool changing that isn’t effective because the tool retraction distances are applied when s3d goes from one process to the other (adding horrible long retractions). On my unfinished (the public one at least) profile I fixed that using the tool distance to 0 and making a fixed distance length inside the tool change scripts. This way you can define on your profile how much it will retract on tool change and you don’t have a double tool change retraction. Ofc not sure if they fixed this issue on 4.0 but afaik they didn’t because it’s part of the nature of the process system.
So, short answer. Settool change settings to zero and defined inside the tool change script by a fixed amount. This way it will work better and cleaner.
About the wait, yeah they also didn’t add that. They really needto step up the game and make a heat/cold like Cura does, and I thought (heard) that was gonna be 4.0, so hopefully they will add that on next releases (but who knows...).
Thanks for the info.
I think S3D got a bit too comfortable.
Cura made a massive leap forward and I think that in part thanks to you ????
I'm only using S3D cause I'm having an extrusion problem with the PVA. It's not consistent. There are breaks in the lines it puts down. It does eventually start to work as it suppose to but just not after the first layer. I think it might be a temp thing as I have cleaned out the nozzle so many times. It's getting boring. I just completed a 7hr print with S3D using PVA support and it looks great. So it leads me to think it's a profile issue with Cura.
I might set the PVA to default 220.
Again thank you and I will amend the script as suggested. ????
1
ArunC posted a topic in UltiMaker Cura,
.thumb.jpeg.0b7a05eafc09add17b8338efde5852e9.jpeg)
Dustin posted a topic in Firmware,
Recommended Posts
neotko 1,417
You need to remove the ;
That’s the ‘uncomment’
The one after the IF{}
Also um3 doesn’t know or thinks. S3D just do a poor heat/cold control, that’s one of the Cura features that make dual easier/faster. But um3 doesn’t actually think much about what’s happening on the print, but the slicer.
For example the material, um3 only checks the tag # compares to his internal list and send the info by wifi to cura so cura knows what material is there. But that’s all. UM3 doesn’t parse the gcode, set the heat/cold times or knows where the head shouldn’t go (like bed clips). All that job is done on the slicer.
Edited by GuestLink to post
Share on other sites