Deploying to gh-pages from @ Klipper3d/klipper@d725dfd309 🚀
This commit is contained in:
@@ -1247,8 +1247,8 @@
|
||||
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="CANBUS_Troubleshooting.md" class="md-nav__link">
|
||||
None
|
||||
<a href="CANBUS_Troubleshooting.html" class="md-nav__link">
|
||||
CANBUS Troubleshooting
|
||||
</a>
|
||||
</li>
|
||||
|
||||
@@ -1433,7 +1433,9 @@
|
||||
</code></pre></div>
|
||||
|
||||
<p>In slic3r derivatives such as PrusaSlicer and SuperSlicer, the following would be used:</p>
|
||||
<p>START_PRINT EXTRUDER_TEMP=[first_layer_temperature] BED_TEMP=[first_layer_bed_temperature]</p>
|
||||
<div class="highlight"><pre><span></span><code>START_PRINT EXTRUDER_TEMP=[first_layer_temperature] BED_TEMP=[first_layer_bed_temperature]
|
||||
</code></pre></div>
|
||||
|
||||
<p>Also note that these slicers will insert their own heating codes when certain conditions are not met. In Cura, the existence of the <code>{material_bed_temperature_layer_0}</code> and <code>{material_print_temperature_layer_0}</code> variables is enough to mitigate this. In slic3r derivatives, you would use:</p>
|
||||
<div class="highlight"><pre><span></span><code>M140 S0
|
||||
M104 S0
|
||||
|
||||
Reference in New Issue
Block a user