Pin state reporting of all pins. Flash optimization.
- New pin state realtime reporting feature. Instead of `Lim:000` for limit state reports, the new feature shows `Pin:000|0|0000`, or something similar. The `|` delimited fields indicate xyz limits, probe, and control pin states, where 0 is always not triggered, and 1 is triggered. Invert masks ARE accounted for. Each field may be enabled or disabled via the `$10` status report setting. The probe and control pin flags are bits 5 and 6, respectively. - Remove the now deprecated `REPORT_CONTROL_PIN_STATE` option in config.h - The old limit pin reports `Lim:000` may be re-enabled by commenting out `REPORT_ALL_PIN_STATES` in config.h. - Incremented the version letter (v1.0c) to indicate the change in reporting style. - Replaced all bit_true_atomic and bit_false_atomic macros with function calls. This saved a couple hundred bytes of flash.
This commit is contained in:
@ -1,3 +1,39 @@
|
||||
----------------
|
||||
Date: 2015-09-30
|
||||
Author: Sonny Jeon
|
||||
Subject: Bug fixes.
|
||||
|
||||
- G38.x was not printing correctly in the $G g-code state reports. Now
|
||||
fixed.
|
||||
|
||||
- When investigating the above issue, it was noticed that G38.x
|
||||
wouldn’t show at all, but instead a G0 would be printed. This was
|
||||
unlike the v0.9j master build. It turned out volatile variables do not
|
||||
like to be defined inside a C struct. These are undefined on how to be
|
||||
handled. Once pulled out, all weird issues went away.
|
||||
|
||||
- Also changed two ‘sizeof()’ statements in the mc_probe() and
|
||||
probe_state_monitor() functions to be more robust later on.
|
||||
|
||||
- Updated the commit logs to individual files for each minor release.
|
||||
Forgot to update the generating script to account for this.
|
||||
|
||||
|
||||
----------------
|
||||
Date: 2015-09-30
|
||||
Author: Sonny Jeon
|
||||
Subject: Minor bug fixes.
|
||||
|
||||
- G38.x was not printing correctly in the $G g-code state reports. Now
|
||||
fixed.
|
||||
|
||||
- Potential bug regarding volatile variables inside a struct. It has
|
||||
never been a problem in v0.9, but ran into this during v1.0
|
||||
development. Just to be safe, the fixes are applied here.
|
||||
|
||||
- Updated pre-built firmwares with these two bug fixes.
|
||||
|
||||
|
||||
----------------
|
||||
Date: 2015-09-24
|
||||
Author: Sonny Jeon
|
||||
|
Reference in New Issue
Block a user