# Gcode interpreter

**URL:** <https://discourse.odriverobotics.com/t/gcode-interpreter/83>\
**Category:** General\
**Created:** [May 26, 2017, 4:29pm UTC](https://discourse.odriverobotics.com/t/gcode-interpreter/83 "2017-05-26T16:29:45Z")\
**Posts on this page:** 1\
**Showing post:** 32

<div class="post-metadata">

**Author:** ![madcowswe](https://discourse.odriverobotics.com/user_avatar/discourse.odriverobotics.com/madcowswe/32/1138_2.png) [@madcowswe](https://discourse.odriverobotics.com/u/madcowswe)\
**Post date:** [November 11, 2017, 11:14pm UTC](https://discourse.odriverobotics.com/t/gcode-interpreter/83/32 "2017-11-11T23:14:21Z")

</div>

Hi everyone, resurrecting this old thread to let you know that thanks to @Hello1024, we now have the G-Code parsing and motion planning features of GRBL stripped out and half-integrated into ODrive firmware here: [ODrive PR 47](https://github.com/madcowswe/ODrive/pull/47).  
Like it says in the PR, this hasn’t been tested on hardware, and is more of a proof of concept than a finished feature. Nevertheless, if someone want’s to work on finishing this off, you are more than welcome!  
Let me know, and I can coordinate.

---

_[View the full topic](https://discourse.odriverobotics.com/t/gcode-interpreter/83)._
