gcode reference for Original Prusa i3 ?
Hi all,
I'm having a look in the gcode world to try to understand these prefix/postfix commands defined by default in Slic3r packaged with the Prusa software and to tweak them in some case. (especially when this initial line is overlapping with the object to print).
Is there any reference sheet of supported gcode command and limits specific to the Original Prusa i3 firmware ? I find a lot of them, but not sure which one are supposed to be implemented.
Many thanks in advance.
I'm like Jon Snow, I know nothing.
Re: gcode reference for Original Prusa i3 ?
Hi Christophe
Stock Marlin - commands here: http://reprap.org/wiki/G-code
There are a couple of differences, with filament change (M600) being properly implemented in this branch.
Peter
Please note: I do not have any affiliation with Prusa Research. Any advices given are offered in good faith. It is your responsibility to ensure that by following my advice you do not suffer or cause injury, damage…
Re: gcode reference for Original Prusa i3 ?
Thanks a lot Peter (again !).
Now I have a better understanding of the gcode used before and after a print.
After watching the wiki page, it seems that Marlin firmware is able to manage a filament sensor to pause the print when the filament spool is exhausted. Is there some working hack using this capability on the orginal Prusa i3 ?
I'm like Jon Snow, I know nothing.
Re: gcode reference for Original Prusa i3 ?
Christophe
The code for filament out is in the software and only requires activating.
I think it is called "Filament Runout" in the firmware, but there is a problem with it (and the Marlin partial implementation).
All GCode commands are buffered, so there are up to 16 (I believe) commands waiting in a buffer to be processed. Assume that you are in the process of a top layer when the filament runout switch activates. There would be 16 commands to be processed before the runout takes effect. Those 16 commands could use more filament than is available.
There is a possible work-around for this in that it may be possible to put the runout activation at the front of the buffer queue, but unfortunately this is very complex to program.
I think that at present, the general consensus if to not implement the runout feature at present.
Peter
Please note: I do not have any affiliation with Prusa Research. Any advices given are offered in good faith. It is your responsibility to ensure that by following my advice you do not suffer or cause injury, damage…
Re: gcode reference for Original Prusa i3 ?
Thanks for the explanation Peter.
I was specifically speaking of the M405/M406 commands ( http://reprap.org/wiki/G-code#M405:_Filament_Sensor_on ) , which seems more like a feature activation than a command to send interactivelly.
When I'll have some time I'll go in the source code to try to understand how it's implemented.
But maybe Josef could comment this one ?
I'm like Jon Snow, I know nothing.
Re: gcode reference for Original Prusa i3 ?
Hi Christophe
It's actually Michal who looks after the firmware and I have already had the discussion with him, hence my comments above...
The M405 and M406 commands turn on/off the sensor code while printing. This code (Filament Runout) needs to be enabled within the firmware:
//#define FILAMENT_RUNOUT_SUPPORT
Uncomment this line (remove the "//" to enable, but I am not sure it will work, as the FILAMENT_RUNOUT_SENSOR is not used elsewhere in the firmware. I presume that this is used to define the pin used for the sensor (there is nothing in Pins.h).
Peter
Please note: I do not have any affiliation with Prusa Research. Any advices given are offered in good faith. It is your responsibility to ensure that by following my advice you do not suffer or cause injury, damage…
Re: gcode reference for Original Prusa i3 ?
Hey guys,
I'm a complete noob and forgive me if this questions is complete nonsence! 😀
I'm running a mk2s with Octoprint and just added an endstop as a filament sensor. However, I do have some trouble adding a propper GCODE for pausing a resuming the print and was wondering if it would be possible to just copy and past what is in the mk3's firmware for the filament sensor.
What do you think?
André