| Age | Commit message (Collapse) | Author |
|---|
|
New features:
- Stepper driver mode can now be set via D parameter in M569
- Stepper driver chopper control register can now be set via C parameter
in M569 - USE THIS ONLY IF YOIU KNOW WHAT YOU ARE DOING!
- When Z probe type 0 is selected and DWC/PanelDue have prompted for
manual jogging, axis movement before homing is allowed
Bug fixes:
- If a network password was set, DWC disconnected with a "Not
authorised" message after a large file was uploaded
- If MaxReps got too high then a watchdog reset occurred. MaxReps has
been replaced by a hiccup count.
- M122 reported some parts of network status twice on Duet 2 Ethernet
and Duet 2 Maestro
- If a PT1000 sensor was configured using M305 but a thermistor was
plugged in instead, the firmware reported semi-random high temperatures
instead of an error
- If a PT1000 sensor was configured using M305 and then M305 was used to
change it back to a thermistor, it remained configured as a PT1000
- The M105 response on a multi-tool system was not in the exact format
that Octoprint wanted
|
|
Bug fixes:
DWC sometimes disconnected after uploading a GCode file
Reverted the behaviour of G0 commands to the pre-2.0 behaviour when the
machine mode is FFF (i.e. the F parameter is recognised and the feed
rate is shared with the G1 feed rate)
If a G1 command with extrusion was followed by a G0 command, the
extrusion was repeated in the G0 command
When high microstepping was used, certain sequences of movement commands
could lock up the movement system
|
|
Use our own version of vsnprintf to save stack and avoid needing to stop
scheduler during calls to it
G0 now moves at maximum travel speed and ignores F parameters
Fixed problem with doing G20 after loading or probing a height map with
a significant Z offset
Added chrishamm's spindle and fan map changes
Added type 10 Z probe which uses Z motor stall detection
Don't need to home any more before simulating a file
Update user coordinates after G10 is used to change tool offsets
Don't require both X and Y or both I and J parameters to be specified in
G2/G3 commands
|
|
Increased Heat task stack to avoid crash when tuning a heater
Protected vsnprintf etc. from reentrancy
Use scheduler suspension instead of disabling interrupts for most
critical sections
|
|
Added malloc lock/unlock functions to avoid crash in sprintf etc.
Allow jerk values down to 0.1mm/sec
Add missing call to HttpResponder::CheckSessions()
Added mutex around the access to HttpResponder::gcodeReply
Warn if M500 used without M502 in config.g
M114 now sends user coordinates first
Condensed memory diagnostics a little
Embed OutputStack objects instead of creating them dynamically
|
|
Got rid of the global scratchString
Rationalised some String and StringRef functions
Bug fix: if a motor stall triggered a pause, the driver numbers were not
listed in the message
Fixed possible race conditions in TMC2660 driver,
|
|
Various changes to maske the filesystem thread safe
|
|
New features:
- New M569 T parameter options to specify step pulse width, step pulse
interval, direction setup and direction hold times
- M665 now sets the M208 limits (except Z min) to match the machine
limits, so that Duet Web Control reports the correct values
Bug fixes:
- M116 commands were sometimes executed out-of-order relative to
previous G10 commands if movement commands were in progress
- G10 L20 now computes the workplace coordinate origin correctly
- G53 is only active until the end of the current line of GCode
- The default coordinate system is the one selected by G54
- G54..G59 update the user coordinates immediately
- Fixed "Error: Pop(): stack underflow!" when a file or macro is
terminated due to an illegal move command
- A short delay is inserted when M558 is used to change the Z probe
type, to allow the averaging filters to accumulate the new data
- M291 messages which are non-blocking (i.e. mode < 2) are now
synchronised to queued moves, like M117 messages
Other changes:
- Duet Web Control and PanelDue now report the coordinates relative to
the origin of the current workplace
- Rewrote dhcp_rec function on Duet06/085 to avoid goto statements
(possible fix for startup problem when using DHCP)
|
|
New features:
- On CoreXZ machines we no longer require Z to be homed before bed
probing with G30
- M589 now checks that the password is either empty or 8 characters
minimum
- G10 L2 is supported as an alternative way to set tool offsets
- G10 L20 is supported as an alternative way to set workspace
coordinates
- Heater fault detection is suppressed when heaters are suspended during
bed probing
- DuetWiFiServer/bin uses a new SDK version, which seems to resolve some
issues
- On boards with a W5500 Ethernet interface, the Ethernet PHY is now
programmed to auto negotiate
- Added M564 H0 command to allow axis movement before homing on
Cartesian/CoreXY printers
- The filament length comment proposed to be generated by the next
version of Cura when using more than one filament is supported
Bug fixes:
- I parameter on M452, M453 and M573 didn't work
- If a homing file contained an illegal movement command then homing was
not cancelled
- Corrected Z probe input pin in RADDS build
- Possible fix to Duet 06/085 failure to start when using DHCP
|
|
Added nonlineear extrusion support (M592)
Show calibration parameters in M592 D# response
Bug fix: don't run stop.g, sleep.g or cancel.g at the end of simulating
a print or cancelling a simulation
|
|
Use separate conditionals for stall detect and smart drivers
functionality
Added PT1000 support
|
|
New features:
- Added Hangprinter kinematics. Auto calibration is not
expected to work yet.
- Added M122 P1 command for use in the Duet test
procedure
- Changed a path to a file in the linker command line to work
around an intermittent Eclipse bug
- DuetWiFi/Duet Ethernet: the
secondary hardware watchdog is now enabled and generates an interrupt,
so that if interrupts are enabled at the time then a crash dump can be
saved. If this fails then the primary watchdog will reset the processor
as before.
Bug fixes:
- Fixed issues caused by insufficient RAM (stack
running into heap) by freeing up additional RAM in the movement
structures
- Fixed occasional hang in USB ISR
- M201/203/208/566
commands now allow parameters for invisible axes to be set
- If a M584
command does not include the P parameter, the number of visible axes is
only set to the number of total axes if new axes are created in the
command
- Reverted to rounding down in step time calculations, because
the change to round to nearest may have contributed to issues seen by
some users of 1.20beta10
- Set correct priority for interrupt from the
UART used to receive debug info from the WiFi module
- When a filament
error occurred, the message displayed was one of the lines written to
resurrect.g instead of the type of filament error. Similarly if the
print was paused due to a motor stall.
|
