M201 firmware - supported GCODE command list

[neilcoggins]

Hi,

I've been discussing the M201 with the team that developed OctoPrint, because I can't get my M201 working with an OctoPi v1.2.9 installation. As pointed out in other posts, the firmware in M201 is still very young and has a number of issues.

What would be really helpful is a complete list of what GCODE commands (G*** and M***) are supported by each release of the firmware, so that software developers can actually begin to fix the issues, and increase support for the M201 printer on systems other than Repetier Host.

[Mark]

here is the command list, the others are still under developing:
G0
G1
G4
G20
G21
G28
G90
G91
G92
M17
M18
M20
M21
M23
M24
M25
M84
M104
M105
M106
M107
M109
M110
M114
M115
M117
M119
M140
M190
M220

[neilcoggins]

HI Mark,

Thanks for this list. I have observed unexpected behaviour whilst trying to use OctoPrint/OctoPi with the M201. After speaking with Gina (@foosel) and others, and reviewing the Marlin (v1.0.2-1), Repetier (0.9.28) and Smoothie (edge) firmware source code, it seems as though the behaviour for M110 is broken / non-standard...

If the M201 (running v1.0.4 firmware) receives a GCODE command N0 M110 N0*125 it rejects the command, because it isn't expecting the line number to be 0. However, all other firmwares that I can find the source code for expect the line number to be reset during the M110 command (as opposed to the outdated RepRap Wiki documentation which suggests it should change after the M110 command).

Can I suggest that the M201 firmware be adapted to not care about the line number for M110 commands (since it is being reset anyway)? This would improve the operability of the M201 with OctoPrint and probably other printing software packages.

Thanks.

Neil.

[Mark]

Yeah you're right, the line number can not be reset with this firmware. Will fix it in the next version, and do you have any other commands to add? I'll tell the software engineer and see if he can add it in the next version.

[neilcoggins]

Hi Mark,

Here's the list that should really be in there (ones in bold are important - the others are nice-to-have):

- M0
- M1
- M92
- M93
- M110
- M301 (this would simplify change of the hotend to use another thermistor, and makes swapping hotend possible)
- M360
- M400

So 2 essential M codes, and 6 nice-to-have ones.

[Mark]

have forward this to the software engineer, as they are a little busy these days, so can't forsure all of them will be supported, but will try our best.

[neilcoggins]

Mark,

Is there an NDA or something in place to allow 3rd party developers access to the GTM32 firmware source code?

Just asking, because I'm a C/C++ software developer (20 years experience), and have some skill writing software for set-top boxes, embedded systems, etc... I might be able to implement some of the functions myself on your behalf. Your software engineers could then perform a code review before incorporating it into firmware builds etc...

Just a thought...!

[Mark]

sorry but the firmware is not open sourced...

[stado65]

Hi,

Thanks Neil and Mark for this interesting discussion about G-Code commands to implement on M201.
Personally, I would add to the 'nice to have' G-Code commands :

• - M300 : Play a sound
  - All the codes related to the use of a Z-probe (G29-G30-G31-G32-M401-M402)

[Mark]

roger that! will forward them to the engineer later.