<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel>
        <title>Extruder Trouble</title>
        <description> I&#039;ve got the Ramps 1.4, off of gadgets 3d. I&#039;m running the latest Marlin on it, and I&#039;ve got that all set up. The problem lies with KISSlicer, my slicing software, I suppose.  The temperature works, the commands work fine, everything&#039;s bright and shiny. Including the extruder, when it&#039;s manually controlled. The problem comes in actual prints. 

The three steppers for the Cartesian robot work just fine, and trace the path that it would take if it was printing. Without fail, however, the extuder&#039;s motor refuses to activate from the Gcode&#039;s command (although I can control it manually just fine, through the RAMPS). It&#039;s not Marlin, the Minimum extrusion temperature is well below the one at which it reaches during a print. I haven&#039;t a clue how to get it going, though, and I think the problem lies in the Gcode. 

The prefix-Gcode:

G28
M109 S155
M103
M227 P1600 S1600
M108 S600.0
M113 S1.0
M101</description>
        <link>https://reprap.org/forum/read.php?219,207732,207732#msg-207732</link>
        <lastBuildDate>Tue, 08 Sep 2026 23:59:14 -0400</lastBuildDate>
        <generator>Phorum 5.2.23</generator>
        <item>
            <guid>https://reprap.org/forum/read.php?219,207732,209086#msg-209086</guid>
            <title>Re: Extruder Trouble</title>
            <link>https://reprap.org/forum/read.php?219,207732,209086#msg-209086</link>
            <description><![CDATA[ You were right, I found the answer on the forums fifty seconds after I posted this. Had to switch it from BFB to 5D Absolute E. Got the motor running, at least, but the newest problem is that it's slow. It's only pulling one or two revolutions a minute, except when it's retracting filament. The BFB original Rapmen would retract and then re-extrude when it had to make a lengthy jump in the model, to prevent stringing, and in its current state, the printer only hits the specified speed during that process. Any ideas?]]></description>
            <dc:creator>Morpheus</dc:creator>
            <category>RAMPS Electronics</category>
            <pubDate>Thu, 16 May 2013 00:46:45 -0400</pubDate>
        </item>
        <item>
            <guid>https://reprap.org/forum/read.php?219,207732,207778#msg-207778</guid>
            <title>Re: Extruder Trouble</title>
            <link>https://reprap.org/forum/read.php?219,207732,207778#msg-207778</link>
            <description><![CDATA[ Is kisslicer set to use relative extruder values? I'm not an expert on it but I know there are 2 different ways to control an extruder. One is relative one is absolute vales, if your slicer is set to one and the firmware set to the other you will have problems,<br />
<br />
I know I haven't given a solution but I hope I've helped poi t you in the right direction.]]></description>
            <dc:creator>lazzymonk</dc:creator>
            <category>RAMPS Electronics</category>
            <pubDate>Sun, 12 May 2013 05:18:56 -0400</pubDate>
        </item>
        <item>
            <guid>https://reprap.org/forum/read.php?219,207732,207732#msg-207732</guid>
            <title>Extruder Trouble</title>
            <link>https://reprap.org/forum/read.php?219,207732,207732#msg-207732</link>
            <description><![CDATA[ I've got the Ramps 1.4, off of gadgets 3d. I'm running the latest Marlin on it, and I've got that all set up. The problem lies with KISSlicer, my slicing software, I suppose.  The temperature works, the commands work fine, everything's bright and shiny. Including the extruder, when it's manually controlled. The problem comes in actual prints. <br />
<br />
The three steppers for the Cartesian robot work just fine, and trace the path that it would take if it was printing. Without fail, however, the extuder's motor refuses to activate from the Gcode's command (although I can control it manually just fine, through the RAMPS). It's not Marlin, the Minimum extrusion temperature is well below the one at which it reaches during a print. I haven't a clue how to get it going, though, and I think the problem lies in the Gcode. <br />
<br />
The prefix-Gcode:<br />
<br />
G28<br />
M109 S155<br />
M103<br />
M227 P1600 S1600<br />
M108 S600.0<br />
M113 S1.0<br />
M101]]></description>
            <dc:creator>Morpheus</dc:creator>
            <category>RAMPS Electronics</category>
            <pubDate>Sun, 12 May 2013 01:04:27 -0400</pubDate>
        </item>
    </channel>
</rss>
