Some help regarding S3D
-
If you put the purge commands in the tpost.g file (or in a macro that is called by tpost.g) then they will get called on the initial tool selection as well, provided that the machine has been homed before the initial tool selection takes place.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
Yeah that's true, but i only want to purge the very first tool at print start. Not on every tool change, then that approach won't work will it?
-
@Exerqtor said in Some help regarding S3D:
Yeah that's true, but i only want to purge the very first tool at print start. Not on every tool change, then that approach won't work will it?
I'm missing the question sorry, maybe I'm too blinded by my own issues .. if you want to do something (purge in your case) only "at the print start", it has to go to startup script, as you did, but there's no "new_tool" in startup script as it's just starting ... maybe there is "tool_number" or something like that (would be cool if s3d would actually document all the available "Variables") ... I assume your problem is that you sometimes start print with T0 sometimes with T2, the easiest way would be to make 3 profiles in s3d "start-t0, start-t1 and start-t2" and then just use different startup script to initialize/prime appropriate extruder
...dunno if RRF knows what's selected tool so that you can instead of all the code in startup script in s3d just start some macro from s3d startup and do the code in the RRF
-
@smece
I already have one profile for each extruder, and one for all extruders. The profiles for single extruders ain't no problem since i just define the tool right after the purge heating is done.
But like you suspect, the problem comes if /when i want to do a multi extruder print. It's no "problem" pr. say if i allways use T0 for the initial tool. But some times that will involve and extra filament swap before startup just to acomidate, and it would be so much easier if the stupid slicer just had a [first_tool] placeholder that would work in start.
-
yeah I understood, but I suggested that you split the "multiple extruder" profile to 2, one that is "first is T0" and other that is "first is T1" so you select one or the other depending on what you have loaded where
put a question on s3d forum, they might answer, the problem is that whole company is single person (the developer, the "chris", the whole bunch of ppl on forum, the person doing all the censuring, approval of posts etc etc... all one man ... that's why they are slow to respond and slow to answer to proper queries), also shoot email to support@simplify3d.com he tends to answer that one quicker than the forum questions
-
Yeah i get that approach, but that's more like walking around the problem than solving it. Something i don't like by default.
On the other point i doubt Clayton Webster is the only man behind the rudder at S3D? In that case it's not strange everything takes forever.
-
@Exerqtor said in Some help regarding S3D:
Yeah i get that approach, but that's more like walking around the problem than solving it.
99% of issues with S3D are "solved" by workarounds, not by real solutions
On the other point i doubt Clayton Webster is the only man behind the rudder at S3D? In that case it's not strange everything takes forever.
look out at what's new added & fixed in past 3 years ... but it's story for some other time and some other place, nothing to bother duet3d folks with .. it's still a decent slicer
-
btw I assume you seen this one:
https://community.ultimaker.com/topic/11328-simplify3d-hidden-undocumented-placeholders-for-post-processing-scripts/ -
@smece
Teah i've seen it
I've started compiling a gdoc with everything i find that i plan to make as public and accessible as i can 
-
@exerqtor I know this is old, but S3D actually DOES have a [first_tool] that can be used in the starting script. Coincidentally, it's spelled exactly as you spelled it.
I found this discussion which seems to predate the variable implementation, and describe what it does.
-
Yeah i've ditched bloatware slicer long ago lol. That post in the S3D forum is also me
