The current version is here - pigcd - it has embedded JsonAPI so you can integrate it with web solutions easily.
The G-CODE interpreter for Raspberry Pi 3 (it works on older versions, but untested)
Recent experiments:
This is the CLI and library G-CODE interpreter that supports acceleration and deceleration, intelligent G-CODE execution for given machine and smooth movements without RT kernel. It accepts subset of G-CODE. Mainly
G0
G1
M3
M5
M17
M18
It also support:
- physical buttons
- execution pause and resume (with break on the given distance)
- configuration in json file
- experimental Bezier curve aproximation of path
- selection of impulse generation strategy
- stable impulses
You can execute the gcode using the following command (example)
gcd -c config_file.json -f program.gcd
You can turn off optimization of gcode by adding --raw
option. It will treat the gcode
without any additional processing, so impossible turns can be performed. In this
mode, only G1 and M codes are supported.
Quick start:
mkdir build
cd build
cmake ..
make -j 2 gcd
sudo ./gcd -c ../v4.json -f your_gcode_file.gcd
More info: doc/BUILD.md
You should install library for tests:
git clone https://github.com/catchorg/Catch2.git
cd Catch2
cmake -Bbuild -H. -DBUILD_TESTING=OFF
sudo cmake --build build/ --target install
The example connection schematic for stepstics. The configuration file is v3.json. Schematic is as follows:
STL style with custom types named with _t as the postfix
Most of units are in SI standard. The velocity and distance, when not marked differently, is presented in mm/s and mm.
M codes marks separate sections of gcode G codes are processed as a whole
This means that this kind of gcode program:
M3
M17
G1Z-1
G1X10
M5
G0Z10
G0X0
G0Z0
M18
will execute as following parts interpreted as separate executions of motor thread:
- M3
- M17
- G1Z-1, G1X10
- M5
- G0Z10, G0X0, G0Z0
- M18
AGPL
If you are interested in different (non-exclusive) license, please contact me (author).
(this section will be cleared)
You can send pull requests and issues. The credits will be yours and the version with merged changes will be on the same license (AGPL) forever. As a contributor you can ask me (pantadeusz) for a different license for the code. I will have the right to license the code with contribution differently for commercial purposes - for example - with custom features. Of course credits will be maintained. In this (hypothetical) case I will try to reach most active contributors to share some profit. Fortunately/unfortunately right now this is a one person show so the problem does not exist :)