CMS/Marlin
3
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

readme

Browse Source
This commit is contained in:
Bernhard 2012-06-02 13:44:38 +02:00
parent 6b14f95b3e
commit e792d62f47
1 changed files with 6 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
README.md
View File

@ -31,6 +31,7 @@ Features:
* Full endstop support * Full endstop support
* SD Card support * SD Card support
* SD Card folders (works in pronterface) * SD Card folders (works in pronterface)
* SD Card autostart support
* LCD support (ideally 20x4) * LCD support (ideally 20x4)
* LCD menu system for autonomous SD card printing, controlled by an click-encoder. * LCD menu system for autonomous SD card printing, controlled by an click-encoder.
* EEPROM storage of e.g. max-velocity, max-acceleration, and similar variables * EEPROM storage of e.g. max-velocity, max-acceleration, and similar variables
@ -100,6 +101,11 @@ If you have an SD card reader attached to your controller, also folders work now
You can write to file in a subfolder by specifying a similar text using small letters in the path. You can write to file in a subfolder by specifying a similar text using small letters in the path.
Also, backup copies of various operating systems are hidden, as well as files not ending with ".g". Also, backup copies of various operating systems are hidden, as well as files not ending with ".g".
*SD card folders:*
If you place a file auto<0-9>.g into the root of the sd card, it will be automatically executed if you boot the printer. The same file will be executed by selecting "Autostart" from the menu.
First *0 will be performed, than *1 and so on. That way, you can heat up or even print automatically without user interaction.
*Endstop trigger reporting:* *Endstop trigger reporting:*
If an endstop is hit while moving towards the endstop, the location at which the firmware thinks that the endstop was triggered is outputed on the serial port. If an endstop is hit while moving towards the endstop, the location at which the firmware thinks that the endstop was triggered is outputed on the serial port.