| Age | Commit message (Collapse) | Author |
|---|
|
|
|
M955 outputs the configuration only if requested
Minor refactoring in the Linux interface files
Bug fix: M918 didn't update the boards seq number
Bug fix: RRF could leave "starting" mode too early
|
|
|
|
M918 P0 deletes any existing display and no longer reports an error
When a display is deleted, set the CS and A0 pins back to inputs
|
|
|
|
|
|
|
|
|
|
|
|
* Adapted the latest version (2020-08-07) of v3.02-dev to include support
for a ST7565 minipanel display in the Duet 2 Maestro. An experimental
contrast parameter "C" (range 0-100) has been added to the M918 as well.
This builds on previous code where a ST7576 display was made to work on
a Duet 3 Mini board.
* Added final comments, TODO's and clarifications
* Added a default define to set the LCD_CS on the Maestro high permanently
on display init. LCD_CS functions as a gate pin for ST7567 displays on
the Maestro, and that doesn't have to happen with every chip select. In
this specific case, EXP_1 functions as the alternative LCD_CS, since the
original LCD_CS cannot provide an active low.
|
|
RAM
|
|
|
|
Also allow driver numbers of the form 0.# on boards that do not support
CAN expansion
|
|
Also moved pin definitions for interfacing to W5500 and ESP8266 into
this project from CoreNG
|
|
Loops are now working
Added noexcept specifiers to omst of the remaining C++ source files
|
|
|
|
Use new Wire library form CoreNG
Use a separate task to keep DueX endstop input status up to date
Task priority definitions moved from RRFLibraries project to ReprapFirmware.h
Added folder src/Hardware and moved some files into it
|
|
Fixed bugs in the 12864 menu system
Allow prints to be paused and cancelled while they are waiting for temperatures to be reached
|
|
|
|
Added legacy Duet RTOS configuration
Changed LF in HTTP responses to CRLF in legacy Duet webserver
Don't allocate memory for 12864 display until the display is configured using M918
Bug fix: when changing directory in files list on 12864 display, the display wasn't updated until the encoder was turned
|
|
Corrected processing of button actions
Corrected display of speed factor
Added support for right- and centre-aligned fields
|
|
Fixed items 79, 179 and 279 on 12864 display
Fixed 12864 display error timeout
Changed I2C calls to suit rewritten I2C driver
Use an interrupt to track changes to DueX5 endstop input status
Idle task is now included in task list
Filament consumed in tool change macros and filament loading is no longer included in filament usage count, for better print time estimation
:ookahead error check now allows for rounding error to avoid spurious reports
|
|
New and changed features:
- Send the mapped fan speed at the start of the fan speed list in the M408 response for PanelDue
- Support PanelDue emergency stop interrupt from UART driver
- Execute residual babystepping immediately
- Warning message are now generated if trying to move motors on internal drivers but VIN is too low or too high
- Increased minimum fullsteps for motor open detection from 4 to 20
- I2C addresses can be specified in hex format e.g. "0x71" or "x71"
- M584 can now use dummy (high) driver numbers to assign an axis or extruder to no driver
- M122 now tells you if the drivers are enabled, or disabled and waiting for the correct voltage
- Added special support for coast-to-end in RecalculateMove
- Brought RADDS build up to date and use RTOS
- Improved HTTP 'page not found' message
- M260 now lets you receive I2C data after sending data
Bug fixes:
- G30 H parameters didn't work if deployprobe.g or retractprobe.g file present
- M600 stopped the machine
- Watchdog initialisation timing was marginal
- Possible fix for issue with using 3 independent Z motors each with a separate endstop switch
- Use a I2C mutex instead of a critical section lock
- Use new I2C driver in CoreNG
- M557 P parameter was not working
- G30 S-2 tool offset was set in the wrong direction
- After G30 S-2, user coordinates were not updated to account for new tool offset
- M918 with a P parameter now resets the display
- Improved the mechanism used to determine which layer is being printed
- 12864 display buttons sometimes disappeared when moving between them
- 12864 display: last byte of images didn't display correctly
- 12864 display: in button commands, "#0" should be substituted, not "menu"
- Don't start executing a G30 S-2 command if no tool is selected
- Http responses now use \r\n as the line ending, not \n
|
|
New G/M code features since 2.02RC2:
G10 L2 and G10 L20 can now be used with no P parameter, meaning use the current coordinate system
G60 now saves the current tool as well as the current user coordinates
M116 now accepts an optional S parameter to specify the acceptable temperature difference
M205 is supported to set the jerk limits (in mm/sec) as an alternative to M566
M208 now accepts Xaa:bb Ycc:dd etc. as an alternative to separate M208 S0 and M208 s1 commands
M305 temperature sensor type 300-307 now supports a C parameter to select the input channel and a D parameter to select differential mode
M408 now accepts a P parameter. P0 (default) gives the previous behaviour. P1 S"filter" now returns those parts of the object model that match "filter".
M557 now supports a P parameter to set the number of X and Y points, as an alternative to using the S parameter to set the spacing
M558: zero or negative Z probe tolerance (S parameter) with A parameter > 1 now means always average all readings
M558 now accepts a C parameter to select the endstop number when the mode is 4. M558 P6 is translated to M558 P4 C4, and M558 P7 is translated to M558 P4 C2.
M600 is now supported
T R# (where # is a restore point number) is now supported
-
Other changed behaviour since 2.02RC2:
When storage module debug is enabled, failing to open a file is now a warning not an error because it is a normal accurrence when optional files are not present (e.g. tool change files, start.g, stop.g)
Increased number of restore points from 3 to 6
When the WiFi module is in client mode it tries to auto-reconnect continuously if the connection is lost
Implemented the object model framework and a few variables
Z leadscrew or manual be levelling adjustment results are now logged even if the process failed, if logging is enabled
Mesh probing results are now logged, if logging is enabled
Error and warning messages generated by incorrect GCode commands are now logged, if logging is enabled
-
Bug fixes since 2.02RC2:
The motor phase open circuit message is clearer, is now a warning instead of an error, and spurious instances of it should be reduced
M918 with no parameters now reports current settings (Duet 2 Maestro)
Further limited the amount of CPU time used to refresh the 12864 display
Fixed incorrect check for G2/G3 missing parameter
Fix CoreXYUV stall detection
Absolute babystepping was be restricted to 1mm change
After using G10 L2 or G10 L20 to change workplace coordinate offsets, the user positions of axes other than X and Y were not updated
M915 now recognises the E parameter
M915 output was truncated if no drives were specified
On the Duet 2 Maestro, if a BLTouch Z probe was used then the pin didn't always stay retracted after the probe was triggered
On the Duet 2 Maestro, if the SD card menu on the 12864 display was used then the network kept disconnecting
If G30 S-1 was sent with the Z probe type set to zero then reported trigger height was an undefined value
Fixed potential buffer overflow issues in 12864 menu code
-
Other changes:
Introduced class IPAddres and refactored most usage oif IP addresses
|
|
|
|
More improvements to 12864 display support
Implemented M144 S1
Merged in chrishamm's changes
|
|
Fixed bug that causes a rare hard fault if we ran out of buffers
Partially implemented 12864 menu system
|
|
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
|
|
|
|
Renamed IoPort{.cpp,.h} to avoid name clash with ASF
Fixes to 12864 display
Support beeper on 12864 display
Encoder parameters are now configurable (M918)
|
|
Refactored some string handling
Fixes for Duet 2M
|
|
Added multi-tap probing
Added M260/M281 I2C send and receive
Added absolute babystepping mode
Fix for pressure advance with non-uniform extrusoin rate
Disabled cache oin SAM4E
Fixed FTP "listen failed" bug
Fixed crash when trying to confoigure a filament monitor on a DueX
endstop input
Change endstops 5-9 pin allocation when no DueX board present
Show board revision as 1.02 if VSSA sense present
Ported DHCP fixes form lwip 2 to Duet 06/085 build
M304 bug fix
Bug fix to recent PrintMonitor change when getting "Generated by" string
|
