Firmware Capabilities Protocol
- 1 Idea
- 2 Protocol definition
- 3 Currently-defined capabilities
- 3.1 Cap:EEPROM
- 3.2 Cap:AUTOREPORT_TEMP
- 3.3 Cap:AUTOREPORT_SD_STATUS
- 3.4 Cap:PROGRESS
- 3.5 Cap:PRINT_JOB
- 3.6 Cap:BUILD_PERCENT
- 3.7 Cap:Z_PROBE
- 3.8 Cap:AUTOLEVEL
- 3.9 Cap:LEVELING_DATA
- 3.10 Cap:SOFTWARE_POWER
- 3.11 Cap:TOGGLE_LIGHTS
- 3.12 Cap:CASE_LIGHT_BRIGHTNESS
- 3.13 Cap:EMERGENCY_PARSER
- 3.14 Cap:SERIAL_XON_XOFF
- 3.15 Cap:VOLUMETRIC
- 3.16 Cap:THERMAL_PROTECTION
While it is nice if a firmware supports some special features, it would be even better if hosts would detect that these are available so they start using them. Especially with the wild growth of firmware forks and versions, no host can know which variant can handle what. So at least for Repetier-Firmware we introduce with version 1.0 a new simple protocol to tell hosts what features are available, so they can activate them.
To make it easy to detect, a standard M115 report gets now extended by one or more lines, each line telling what capability. These lines have the following format:
Cap:<NameOfCapability>:<0 or 1>
Notice: no spaces allowed, Name is upper case with underline to separate words. Lines MUST start with "Cap:" so it can be parsed very quickly by hosts.
The last value indicates if that capability is supported or not. The simple absence of a message is not enough since it would be possible, that the firmware simply does not report capabilities at all and host has to make assumptions like showing eeprom editor even with the risk that it is not available. Whereas a 0 value shows that a function is known, but the functionality is not implemented/active.
Knowing different developers will add other capabilities is no real problem as long as all names differ, so hosts can distinguish them by name. Hosts not understanding a name simply ignore them.
The firmware is compiled with EEPROM support.
The firmware can automatically report temperatures. This feature must be enabled by M155 S[interval] so older hosts won't get redundant reports from M105 and this feature.
The firmware will auto-report the SD Card status, using M27 S to enable and set the interval.
The firmware supports the progress protocol:
- M530 S<printing> L<layer> - Enables explicit printing mode (S1) or disables it (S0). L can set layer count.
- M531 filename - Set the filename being printed.
- M532 X<percent> L<curLayer> - Update current print state progress (X=0..100) and layer L.
This allows a host to enable a special information mode on LCD display, so users see progress in percent, model being printed, layer being printed, and total layer count. (Hosts can also use M117 to show time remaining on the LCD status line.)
This feature should only be enabled if a display is available to show it, otherwise the extra commands are useless.
The firmware supports the Print Job Timer commands M75 Start, M76 Pause, and M77 Stop.
The firmware supports setting the progress percentage with M73 P, required to show progress for host-based printing on the machine's display.
The firmware supports single point Z probing with G30.
The firmware supports auto-leveling with G29.
The firmware supports M420 V to report the stored leveling (mesh or matrix) data.
The firmware supports enabling/disabling power with M80 and M81.
The firmware supports turning the case lights on/off with M355 S1 and M355 S0. (May also support setting case light brightness with S values 2-255.)
The firmware supports setting the case light brightness with M355 S and values 2-255.
The firmware supports immediate execution of commands M108, M112, and M410. With this capability M108 can be used to break out of M0/M1, M109, and M190.
The firmware supports serial XON/XOFF handshaking.
The firmware supports Volumetric Extrusion with M200 T D.
The firmware has thermal protection enabled. Hosts can use this item to warn users of a potential fire hazard.