Welcome to mirror list, hosted at ThFree Co, Russian Federation.

github.com/Duet3D/RepRapFirmware.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
path: root/Maths
AgeCommit message (Collapse)Author
2019-11-25VariousDavid Crocker
Bug fix: bed compensation should take account of XY offset of current tool Pulsed filament monitors: don't display current position, because it is meaningless; also don't include calibration data in M122 report, as for laser and magnetic filament monitors. Flush and/or invalidate cache around DMA operations that do not use non-cached memory Fix minimum radius calculation for Scara kinematics Removed Duet3_V03 configuration Replaced NumTotalFans by MaxFans
2019-07-14Bug fixesDavid Crocker
Fixed memory corruption bug Fixed delta trilateration when the rods are different lengths M118 messages to telnet now have newline appended Moved string compare nfunctions to RRFLibraries project Changed the form of paths to syscalls.o so that they don't depend on the file being present
2019-02-14Added support for magnetic filament monitor with V2 firmwareDavid Crocker
2019-02-03Version 2.03beta12.03beta1David Crocker
Refactored network responders to reduce RAM usage Added M122 P105 to print the sizes of some objects
2019-01-24Towards 2.03beta1David Crocker
Fixes to generalised Cartesian kinematics Support linear delta kinematics with up to 6 towers M106 Pn Sxx updates mapped fan speed if n is a mapped fan M408 S2 response now includes bed standby temperature Support G30 S-3 Added user-settable minimum radius to SCARA parameters 12864 bug fix: erase items that should no longer be visible
2018-08-03Added trilateration documentDavid Crocker
2017-08-01Updated a wxMaxima fileDavid Crocker
2017-07-11Version 1.19beta9David Crocker
New and changed features: - Experimental resume-after-power-failure support on Duet WiFi/Ethernet. See https://duet3d.com/wiki/Setting_up_to_resume_a_print_after_a_power_failure. - Partly implemented bed levelling using multiple independent Z motors (M671). See https://duet3d.com/wiki/Bed_levelling_using_multiple_independent_Z_motors. - If the G10 command is used to set the standby temperature of a tool that is on standby, the live temperature is adjusted accordingly - SCARA parameters configured using M669 now include X and Y bed origin offsets - Baby stepping is no longer cleared when you home the printer or probe the bed - The Y axis can now be mapped in a similar way to the X axis - When the WiFi module is in access point mode, M122 displays the number of connected clients (needs DuetWiFiServer 1.19beta9) - The M305 command now uses the S parameter to set the heater name instead of the H parameter - The meaning of the first M669 crosstalk parameter for a SCARA printer has changed. A zero value now means that the proximal motor does not affect the proximal-to-distal arm angle. - The CoreXY kinematics calculations have been changed to conform to the way they are defined in other firmwares and at CoreXY.com. See the important upgrade notes. The CoreXZ and CoreXYU kinematics have been changed similarly. - The maximum allowed target temperature for auto tuning now depends on the configured maximum temperature for that heater - The heater gain that provokes a warning when setting heater model parameters with M307 or after auto tuning now depends on the configured maximum temperature for that heater Bug fixes: - G2 and G3 arc movement commands didn't work when the X axis was mapped - On an IDEX machine there was unwanted movement of the new tool after a tool change occurred - Duet WiFiServer 1.19-beta9: fixed a bug that sometimes caused WiFi connection failures - On the Duet WiFi, if the own access point parameters were configurds but the list of remembered host access points was empty, the own access point name appeared in the remembered list displayed by M587 - On a SCARA mnachine, sending G92 X0 Y0 caused the Duet to return position data containing NaNs to Duet Web Control, which caused it to disconnect Upgrade notes: - **Important!** On a CoreXY machine, you need to either swap the X and Y motor connections, or set the Y axis factor to -1 in the M667 command. Similarly for CoreXZ and CoreXYU machines.