Made changed requested by Logan fori testing jigs in production.
- Fixed "auto0.g" autostart which was not working.
- Made it so M226 works on protected pins:
- There are no longer protected pins
- However, will only work on pins that are already inputs (like endstops)
The TAZ limits the heated bed current to 80% in order
to avoid exceeding the 15A limit on the Rambo. The
Mini needs no throttling because the bed is smaller.
The old Gladiola FW ran the bed at 100%, but since this
new branch was based on oliveoil, the conservative limit
was carried over to the Mini. This was causing temp overrun
errors on the Mini because the bed could not heat fast enough.
The PID tuning was re-run on the two-piece bed since it
had been tuned with the Mini bed running at 80% current.
Added "--config" option to build-lulzbot-firmware.sh to save out
values in "Configuration.h" and "Configuration_adv.h" for chosen
printer and toolhead. This is useful when submitting issues to
Marlin devs.
Fixed incorrect name of LULZBOT_PRINTCOUNTER
* Add MAX7219_DEBUG to Travis CI testing
* Tweak config and use standard pin naming for MAX7219_DEBUG
* MAX7219: Apply coding standards, use macros, etc.
* Make code work...
In former Marlin versions, all accelerations were controlled
by one parameter. Marlin 1.1.4 configures travel acceleration
and print acceleration independently. Adjusted print and travel
accelerations so they are equal in Marlin 1.1.4, just as they did
in prior firmwares. This improves smoothness of print head motion
on TAZ 5 using default profiles.
* Add Max7219 LED Matrix Debug Support
The Max7219 8x8 LED Matrix's are very helpful for debugging new code.
And for that matter, just trying to maximize printer settings without
causing stuttering.
The displays are very inexpensive (under $2.00 with shipping) and
provide a lot of help when trying to debug complicated code.
* Try to keep Makefile up to date.
When M405 is used it changes 'volumetric_multiplier[FILAMENT_SENSOR_EXTRUDER_NUM]' value. When M406 disables M405 it leaves the value unchanged.
This PR applies 'calculate_volumetric_multipliers' in M406 instead of resetting it to 1.0 because M200 may not be compatible with M405 hence I'm sure to restore anyway with correct value.
Marcio Teixeira