Retraction, De-string, Jump, and Trigger Settings
Posted: 17 Sep 2015, 15:27
Thanks for your efforts to produce a quality KISSlicer manual, Davide! It is very much needed and useful.
Could you please provide a better explanation for the Min jump and Trigger settings in your explanation of the Materials Tab (after fig. 32)? I do not think your explanation of these settings is entirely correct and it omits some important details.
You have:
▪ Min jump (mm): the maximum movement that can be performed without oozing. Longer jumps will
start the wipe process.
▪ Trigger (mm): the maximum movement that can be performed after wipe (if enabled). Longer jumps
will start the wipe AND destring (suck) process.
Kisslicer's mouse-over "hover" tips aren't much better so, some time ago, I inquired about these settings on the old forum. Sadly the link below is currently broken, but this was Jonathan's reply here:
http://kisslicer.com/forum/index.php?to ... 49#msg2549
“So, here is the order of operations. For any given travel, KISSlicer will…
1. request a wipe/destring if the travel crosses (or comes really close to) the surface of the object
2. cancel the request for wipe/destring if the jump Trigger (say you want all travels over 10mm to do a wipe/destring, even if it isn’t close to the surface of the object)”
Here is how I interpret Jonathan's explanation:
1. Unless cancelled (per the Min. Jump setting rule, defined in #2 below), KISSlicer performs a wipe/destring operation whenever the travel (jump) path crosses or comes very close to the surface of the object.
2. The wipe/destring setting is cancelled whenever the length of the jump is less than the Min. Jump setting. (Obviously the behavior with a Min. Jump setting of 0 is no jumps will be cancelled.)
3. The Trigger setting is used to "force" a wipe/destring, apart from the above surface crossing-based scheduling and cancellation rules. Any travel (jump) that is longer than the Trigger setting, even if it does not cross or approach the object's surface, results in a wipe/destring operation.
Hopefully Jonathan will, once again, jump in here, if I am misinterpreting his previous explanation.
Could you please provide a better explanation for the Min jump and Trigger settings in your explanation of the Materials Tab (after fig. 32)? I do not think your explanation of these settings is entirely correct and it omits some important details.
You have:
▪ Min jump (mm): the maximum movement that can be performed without oozing. Longer jumps will
start the wipe process.
▪ Trigger (mm): the maximum movement that can be performed after wipe (if enabled). Longer jumps
will start the wipe AND destring (suck) process.
Kisslicer's mouse-over "hover" tips aren't much better so, some time ago, I inquired about these settings on the old forum. Sadly the link below is currently broken, but this was Jonathan's reply here:
http://kisslicer.com/forum/index.php?to ... 49#msg2549
“So, here is the order of operations. For any given travel, KISSlicer will…
1. request a wipe/destring if the travel crosses (or comes really close to) the surface of the object
2. cancel the request for wipe/destring if the jump Trigger (say you want all travels over 10mm to do a wipe/destring, even if it isn’t close to the surface of the object)”
Here is how I interpret Jonathan's explanation:
1. Unless cancelled (per the Min. Jump setting rule, defined in #2 below), KISSlicer performs a wipe/destring operation whenever the travel (jump) path crosses or comes very close to the surface of the object.
2. The wipe/destring setting is cancelled whenever the length of the jump is less than the Min. Jump setting. (Obviously the behavior with a Min. Jump setting of 0 is no jumps will be cancelled.)
3. The Trigger setting is used to "force" a wipe/destring, apart from the above surface crossing-based scheduling and cancellation rules. Any travel (jump) that is longer than the Trigger setting, even if it does not cross or approach the object's surface, results in a wipe/destring operation.
Hopefully Jonathan will, once again, jump in here, if I am misinterpreting his previous explanation.