Merge to 1.1f

1. Fix LED blink.
2. Use newer CoIDE.

doc/csv/build_option_codes_en_US.csv

@@ -6,11 +6,16 @@
 "P","Parking motion","Enabled"
 "Z","Homing force origin","Enabled"
 "H","Homing single axis commands","Enabled"
-"L","Two limit switches on axis","Enabled"
+"T","Two limit switches on axis","Enabled"
 "A","Allow feed rate overrides in probe cycles","Enabled"
+"D","Use spindle direction as enable pin","Enabled"
+"0","Spindle enable off when speed is zero","Enabled"
+"S","Software limit pin debouncing","Enabled"
+"R","Parking override control","Enabled"
 "*","Restore all EEPROM command","Disabled"
 "$","Restore EEPROM `$` settings command","Disabled"
 "#","Restore EEPROM parameter data command","Disabled"
 "I","Build info write user string command","Disabled"
 "E","Force sync upon EEPROM write","Disabled"
-"W","Force sync upon work coordinate offset change","Disabled"
+"W","Force sync upon work coordinate offset change","Disabled"
+"L","Homing initialization auto-lock","Disabled"

doc/csv/error_codes_en_US.csv

@@ -1,35 +1,36 @@
-"Error Code in v1.1+ ","Error Message in v1.0-"," Error Description"
-"1","Expected command letter","G-code words consist of a letter and a value. Letter was not found."
-"2","Bad number format","Missing the expected G-code word value or numeric value format is not valid."
-"3","Invalid statement","Grbl '$' system command was not recognized or supported."
-"4","Value < 0","Negative value received for an expected positive value."
-"5","Setting disabled","Homing cycle failure. Homing is not enabled via settings."
-"6","Value < 3 usec","Minimum step pulse time must be greater than 3usec."
-"7","EEPROM read fail. Using defaults","An EEPROM read failed. Auto-restoring affected EEPROM to default values."
-"8","Not idle","Grbl '$' command cannot be used unless Grbl is IDLE. Ensures smooth operation during a job."
-"9","G-code lock","G-code commands are locked out during alarm or jog state."
-"10","Homing not enabled","Soft limits cannot be enabled without homing also enabled."
-"11","Line overflow","Max characters per line exceeded. Received command line was not executed."
-"12","Step rate > 30kHz","Grbl '$' setting value cause the step rate to exceed the maximum supported."
-"13","Check Door","Safety door detected as opened and door state initiated."
-"14","Line length exceeded","Build info or startup line exceeded EEPROM line length limit. Line not stored."
-"15","Travel exceeded","Jog target exceeds machine travel. Jog command has been ignored."
-"16","Invalid jog command","Jog command has no '=' or contains prohibited g-code."
-"20","Unsupported command","Unsupported or invalid g-code command found in block."
-"21","Modal group violation","More than one g-code command from same modal group found in block."
-"22","Undefined feed rate","Feed rate has not yet been set or is undefined."
-"23","Invalid gcode ID:23","G-code command in block requires an integer value."
-"24","Invalid gcode ID:24","More than one g-code command that requires axis words found in block."
-"25","Invalid gcode ID:25","Repeated g-code word found in block."
-"26","Invalid gcode ID:26","No axis words found in block for g-code command or current modal state which requires them."
-"27","Invalid gcode ID:27","Line number value is invalid."
-"28","Invalid gcode ID:28","G-code command is missing a required value word."
-"29","Invalid gcode ID:29","G59.x work coordinate systems are not supported."
-"30","Invalid gcode ID:30","G53 only allowed with G0 and G1 motion modes."
-"31","Invalid gcode ID:31","Axis words found in block when no command or current modal state uses them."
-"32","Invalid gcode ID:32","G2 and G3 arcs require at least one in-plane axis word."
-"33","Invalid gcode ID:33","Motion command target is invalid."
-"34","Invalid gcode ID:34","Arc radius value is invalid."
-"35","Invalid gcode ID:35","G2 and G3 arcs require at least one in-plane offset word."
-"36","Invalid gcode ID:36","Unused value words found in block."
-"37","Invalid gcode ID:37","G43.1 dynamic tool length offset is not assigned to configured tool length axis."
+Error Code in v1.1+ ,Error Message in v1.0-, Error Description
+1,Expected command letter,G-code words consist of a letter and a value. Letter was not found.
+2,Bad number format,Missing the expected G-code word value or numeric value format is not valid.
+3,Invalid statement,Grbl '$' system command was not recognized or supported.
+4,Value < 0,Negative value received for an expected positive value.
+5,Setting disabled,Homing cycle failure. Homing is not enabled via settings.
+6,Value < 3 usec,Minimum step pulse time must be greater than 3usec.
+7,EEPROM read fail. Using defaults,An EEPROM read failed. Auto-restoring affected EEPROM to default values.
+8,Not idle,Grbl '$' command cannot be used unless Grbl is IDLE. Ensures smooth operation during a job.
+9,G-code lock,G-code commands are locked out during alarm or jog state.
+10,Homing not enabled,Soft limits cannot be enabled without homing also enabled.
+11,Line overflow,Max characters per line exceeded. Received command line was not executed.
+12,Step rate > 30kHz,Grbl '$' setting value cause the step rate to exceed the maximum supported.
+13,Check Door,Safety door detected as opened and door state initiated.
+14,Line length exceeded,Build info or startup line exceeded EEPROM line length limit. Line not stored.
+15,Travel exceeded,Jog target exceeds machine travel. Jog command has been ignored.
+16,Invalid jog command,Jog command has no '=' or contains prohibited g-code.
+20,Unsupported command,Unsupported or invalid g-code command found in block.
+21,Modal group violation,More than one g-code command from same modal group found in block.
+22,Undefined feed rate,Feed rate has not yet been set or is undefined.
+23,Invalid gcode ID:23,G-code command in block requires an integer value.
+24,Invalid gcode ID:24,More than one g-code command that requires axis words found in block.
+25,Invalid gcode ID:25,Repeated g-code word found in block.
+26,Invalid gcode ID:26,No axis words found in block for g-code command or current modal state which requires them.
+27,Invalid gcode ID:27,Line number value is invalid.
+28,Invalid gcode ID:28,G-code command is missing a required value word.
+29,Invalid gcode ID:29,G59.x work coordinate systems are not supported.
+30,Invalid gcode ID:30,G53 only allowed with G0 and G1 motion modes.
+31,Invalid gcode ID:31,Axis words found in block when no command or current modal state uses them.
+32,Invalid gcode ID:32,G2 and G3 arcs require at least one in-plane axis word.
+33,Invalid gcode ID:33,Motion command target is invalid.
+34,Invalid gcode ID:34,Arc radius value is invalid.
+35,Invalid gcode ID:35,G2 and G3 arcs require at least one in-plane offset word.
+36,Invalid gcode ID:36,Unused value words found in block.
+37,Invalid gcode ID:37,G43.1 dynamic tool length offset is not assigned to configured tool length axis.
+38,Invalid gcode ID:38,Tool number greater than max supported value.

doc/log/commit_log_v1.1.txt

@@ -1,3 +1,158 @@
+----------------
+Date: 2017-02-23
+Author: Sonny Jeon
+Subject: Restrict coincident target updates to M3 constant laser only.
+
+- Restrict M3 forced updates when there is a motion block with a
+coincident target. Force syncing of the spindle state can lead to some
+pauses during a job that has coincident targets. That’s not
+particularly desirable. This ensures M4 dynamic mode is not effected by
+this force-sync.
+
+
+----------------
+Date: 2017-02-23
+Author: Sonny Jeon
+Subject: Fixed issue with M3 laser state changes and coincident targets.
+
+[fix] When in M3 constant laser power mode, a change from G0 to G1
+would not set the laser on, if G1 was passed with a coincident target.
+Motion controller now checks for a coincident target situation and will
+force a spindle sync when detected.
+
+
+----------------
+Date: 2017-01-31
+Author: Sonny Jeon
+Subject: Additional build info in the $I printout.
+
+- [new] Added total available planner buffer blocks (15 shown, but
+there are 16. one is used by the ring buffer and to execute system
+motions) and serial RX buffer bytes. This information is useful for
+GUIs to setup and optimize their streaming protocols easily.
+
+[doc] Updated the interface document to reflect the change.
+
+
+----------------
+Date: 2017-01-29
+Author: Sonny Jeon
+Subject: Tidying up parking override control implementation
+
+[new] Added a default configuration for the parking override control
+upon a reset or power-up. By default, parking is enabled, but this may
+be disabled via a config.h option.
+
+[fix] Parking override control should be checking if the command word
+is passed, rather than the value.
+
+
+----------------
+Date: 2017-01-28
+Author: chamnit
+Subject: v1.1f. Parking override control. Spindle enable pin option.
+
+[ver] v1.1f update due to tweaks to interface from new parking override
+control.
+
+[new] Parking motion override control via new `M56 P0` and `M56 P1`
+command, which disables and enables the parking motion, respectively.
+Requires ENABLE_PARKING_OVERRIDE_CONTROL and PARKING_ENABLE enabled in
+config.h. Primarily for OEMs.
+
+[new] `M56` appears in the $G report when enabled.
+
+[new] Five new build info identification letters. Some were missing and
+a couple are new. Updated the CSV and documentation to reflect these
+new items.
+
+[new] Spindle enable pin configuration option to alter its behavior
+based on how certain lasers work. By default, Grbl treats the enable
+pin separately and leaves it on when S is 0. The new option turns the
+enable pin on and off with S>0 and S=0. This only is in effect when a
+user enables the USE_SPINDLE_DIR_AS_ENABLE_PIN option.
+
+[fix] M4 is now allowed to work when USE_SPINDLE_DIR_AS_ENABLE_PIN is
+enabled. Previously this was blocked and was problematic for laser
+folks using M4.
+
+[fix] Properly declared system variables as extern. Not sure how that
+went unnoticed or why it worked up until now but it has.
+
+[fix] EXTREMELY RARE. When AMASS is intentionally disabled and sent a
+motion command that is _one step_ in length, Grbl would not actuate the
+step due to numerical round-off. Applied a fix to prevent the round-off
+issue.
+
+[fix] Added a compile-time check for AMASS settings to make sure that
+the numerical round-off issue doesn’t effect it. This would only happen
+if someone set AMASS max levels to zero. It does not effect AMASS with
+its current defaults.
+
+[fix] Wrapped the mc_parking_motion() function in an ifdef for porting
+purposes.
+
+[fix] Fixed an issue when in inverse time mode and G0’s would require a
+F word. This was not correct.
+
+[fix] Added a note in the defaults.h file that MAX_TRAVEL values must
+be positive. Some users were setting this negative and it was causing
+issues.
+
+
+----------------
+Date: 2017-01-14
+Author: Sonny Jeon
+Subject: Tool number bug fix. Updated documentation.
+
+- [fix] Tool numbers were not being tracked and reported correctly. Now
+shows tool number values in $G when programmed.
+
+- [fix] Added a max tool number value check to the g-code parser.
+
+- [doc] Added a new error code for invalid tool number. Updated CSV and
+interface documents.
+
+- [doc] Added a implementation note for buffer state in status reports.
+Don’t rely on this data for streaming.
+
+
+----------------
+Date: 2017-01-03
+Author: Sonny Jeon
+Subject: Spindle enable pin with variable spindle option fix.
+
+- [fix] When USE_SPINDLE_DIR_AS_ENABLE_PIN is enabled in config.h, the
+enable pin was not being set when spindle speed is zero. This behavior
+should now be fixed.
+
+
+----------------
+Date: 2016-12-19
+Author: Sonny Jeon
+Subject: Fixed homing fail alarm handling. Re-integrated software debouncing.
+
+- [bug] Fixed a homing fail issue, where the alarm was not being set
+right, not cleared correctly. It would report the wrong code and enter
+an infinite alarm loop. This was due to how alarm codes were altered a
+while back. Now updated and fixed to show the right codes.
+
+- [feature] Re-installed optional software debouncing for hard limit
+switches. By request.
+
+
+----------------
+Date: 2016-12-18
+Author: Sonny Jeon
+Subject: Addressed optional PWM min value issue. Updated docs.
+
+- [fix] Spindle PWM minimum value had some typos. Fixed the macros to
+compile correctly. Only effects users that enable SPINDLE_MINIMUM_PWM.
+The name changed to SPINDLE_PWM_MIN_VALUE for consistency sake.
+
+- Updated the laser documentation.
+
+
 ----------------
 Date: 2016-12-12
 Author: Sonny Jeon

doc/markdown/change_summary.md

@@ -109,4 +109,6 @@ On a final note, these interface tweaks came about out of necessity, because mor
 - 	`$J=line` New jogging commands. This command behaves much like a normal G1 command, but there are some key differences. Jog commands don't alter the g-code parser state, meaning a GUI doesn't have to manage it anymore. Jog commands may be queued and cancelled at any time, where they are automatically flushed from the planner buffer without requiring a reset. See the jogging documentation on how they work and how they may be used to implement a low-latency joystick or rotary dial.
 
 - Laser mode `$` setting - When enabled, laser mode will move through consecutive G1, G2, and G3 motion commands that have different spindle speed values without stopping. A spindle speed of zero will disable the laser without stopping as well. However, when spindle states change, like M3 or M5, stops are still enforced.
-	- NOTE: Parking motions are automatically disabled when laser mode is enabled to prevent burning.
+	- NOTE: Parking motions are automatically disabled when laser mode is enabled to prevent burning.
+
+- `G56 P1` and `G56 P0` - When enabled in config.h with Grbl's parking motion, these commands enable and disable, respectively, the parking motion. Like all override control commands, these commands are modal and are part of the g-code stream.

doc/markdown/commands.md

@@ -64,7 +64,7 @@ This command prints all of the active gcode modes in Grbl's G-code parser. When
 
 These active modes determine how the next G-code block or command will be interpreted by Grbl's G-code parser. For those new to G-code and CNC machining, modes sets the parser into a particular state so you don't have to constantly tell the parser how to parse it. These modes are organized into sets called "modal groups" that cannot be logically active at the same time. For example, the units modal group sets whether your G-code program is interpreted in inches or in millimeters.
 
-A short list of the modal groups, supported by Grbl, is shown below, but more complete and detailed descriptions can be found at LinuxCNC's [website](http://www.linuxcnc.org/docs/2.4/html/gcode_overview.html#sec:Modal-Groups). The G-code commands in **bold** indicate the default modes upon powering-up Grbl or resetting it.
+A short list of the modal groups, supported by Grbl, is shown below, but more complete and detailed descriptions can be found at LinuxCNC's [website](http://www.linuxcnc.org/docs/2.4/html/gcode_overview.html#sec:Modal-Groups). The G-code commands in **bold** indicate the default modes upon powering-up Grbl or resetting it. The commands in _italics_ indicate a special Grbl-only command.
 
 | Modal Group Meaning	|  Member Words |
 |:----:|:----:|
@@ -80,6 +80,9 @@ A short list of the modal groups, supported by Grbl, is shown below, but more co
 |Program Mode | **M0**, M1, M2, M30|
 |Spindle State |M3, M4, **M5**|
 |Coolant State	| M7, M8, **M9** |
+|Override Control | _M56_ |
+
+Grbl supports a special _M56_ override control command, where this enables and disables Grbl's parking motion when a `P1` or a `P0` is passed with `M56`, respectively. This command is only available when both parking and this particular option is enabled.
 
 In addition to the G-code parser modes, Grbl will report the active `T` tool number, `S` spindle speed, and `F` feed rate, which all default to 0 upon a reset. For those that are curious, these don't quite fit into nice modal groups, but are just as important for determining the parser state.