<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel>
        <title>protocol for developing my own printer firmware?</title>
        <description> I am planning to use Kisslicer and octoprint to send gcode to my printer. but I am going to develop my own firmware for AVR Atmega 128 chip to drive step motors according to the movement vectors that OctoPrint passes to firmware through serial port.

I have looked for the the protocol to parse the commands that is sent by octoprint, but I couldn&#039;t find a documentation. I believe there is a common protocol so that firmware and driver software can communicate. 

If there is one, could you please share the link to that documentation? thanks.</description>
        <link>https://reprap.org/forum/read.php?2,503499,503499#msg-503499</link>
        <lastBuildDate>Tue, 15 Sep 2026 21:02:21 -0400</lastBuildDate>
        <generator>Phorum 5.2.23</generator>
        <item>
            <guid>https://reprap.org/forum/read.php?2,503499,506634#msg-506634</guid>
            <title>Re: protocol for developing my own printer firmware?</title>
            <link>https://reprap.org/forum/read.php?2,503499,506634#msg-506634</link>
            <description><![CDATA[ <blockquote class="bbcode"><div><small>Quote<br /></small><strong>totorovirus</strong><br />
I was just curious how those firmwares are developed.<br />
<br />
Thanks for your reply</div></blockquote>
<br />
You could take a look at [<a href="https://github.com/MarlinFirmware/Marlin" target="_blank"  rel="nofollow">github.com</a>]]]></description>
            <dc:creator>CptanPanic</dc:creator>
            <category>Developers</category>
            <pubDate>Fri, 08 May 2015 07:58:54 -0400</pubDate>
        </item>
        <item>
            <guid>https://reprap.org/forum/read.php?2,503499,505627#msg-505627</guid>
            <title>Re: protocol for developing my own printer firmware?</title>
            <link>https://reprap.org/forum/read.php?2,503499,505627#msg-505627</link>
            <description><![CDATA[ I was just curious how those firmwares are developed.<br />
<br />
Thanks for your reply]]></description>
            <dc:creator>totorovirus</dc:creator>
            <category>Developers</category>
            <pubDate>Tue, 05 May 2015 22:20:50 -0400</pubDate>
        </item>
        <item>
            <guid>https://reprap.org/forum/read.php?2,503499,503653#msg-503653</guid>
            <title>Re: protocol for developing my own printer firmware?</title>
            <link>https://reprap.org/forum/read.php?2,503499,503653#msg-503653</link>
            <description><![CDATA[ You mean <a href="http://reprap.org/wiki/Gcode" target="_blank"  rel="nofollow">this</a>?<br />
<br />
Why do you do your own Firmware and don't just modify one of the existing firmwares?]]></description>
            <dc:creator>JustAnotherOne</dc:creator>
            <category>Developers</category>
            <pubDate>Thu, 30 Apr 2015 11:28:51 -0400</pubDate>
        </item>
        <item>
            <guid>https://reprap.org/forum/read.php?2,503499,503499#msg-503499</guid>
            <title>protocol for developing my own printer firmware?</title>
            <link>https://reprap.org/forum/read.php?2,503499,503499#msg-503499</link>
            <description><![CDATA[ I am planning to use Kisslicer and octoprint to send gcode to my printer. but I am going to develop my own firmware for AVR Atmega 128 chip to drive step motors according to the movement vectors that OctoPrint passes to firmware through serial port.<br />
<br />
I have looked for the the protocol to parse the commands that is sent by octoprint, but I couldn't find a documentation. I believe there is a common protocol so that firmware and driver software can communicate. <br />
<br />
If there is one, could you please share the link to that documentation? thanks.]]></description>
            <dc:creator>totorovirus</dc:creator>
            <category>Developers</category>
            <pubDate>Thu, 30 Apr 2015 00:47:43 -0400</pubDate>
        </item>
    </channel>
</rss>
