New firmware 1.17 RC1
-
I have just released this at https://github.com/dc42/RepRapFirmware/tree/dev/Release/Duet-WiFi/Edge for the Duet WiFi and https://github.com/dc42/RepRapFirmware/tree/dev/Release/Duet-0.6-0.8.5/Edge for the wired Duet (as usual, follow the link to the version you want and then press Raw to download it). Here is a summary of new features since 1.16:
-
Implemented grid compensation. Use M557 to define a grid, G29 to probe the grid and save and activate the height map file, G29 S1 to load and activate a height map file, and G29 S2 or M561 to clear the height map. For compatibility with other firmwares, you can also use M374 to save the height map and M375 to load the height map. Grid compensation can be tapered using the M376 command.
-
M500, M501 and M502 now save parameters in SD card file /sys/config_override.g instead of in flash memory. The parameters saved and restored are the M307 auto tune results, the PID parameters (only if you used M301 to override the ones generated from the M307 model), Delta printer M665 and M666 settings, and the G31 trigger height, trigger value and X and Y offsets. The M501 auto save option has been removed.
-
Removed S and T parameters from M301 command, also M301 with negative P parameter no longer sets bang-bang mode. Use the M307 command instead.
-
Added P parameter to the G31 command to specify Z probe type. This allows you to view the parameters for the Z probe(s) and to set parameters for a particular Z probe type without selecting that type. G31 P or G31 P0 prints the parameters of the currently-selected Z probe.
-
Z probe offsets are now applied during G30 probing with specified XY coordinates, including during delta auto calibration. You may need to adjust your auto calibration points to allow for this.
-
Z probe recovery time can be configured using the M558 R parameter. The head will pause for this length of time after moving to over the probe point and before starting to probe.
-
G30 S-1 how prints the stopped height
-
Implemented M401 and M402
-
Removed maximum average printing acceleration parameter from M201 command
-
M571 command (set output on extrude) can now use any pin that supports PWM. Use the P parameter to specify the logical pin number. You can also specify the PWM frequency using the F parameter.
-
Added exception handlers and store a software reset code when an exception occurs. Previously an exception caused a watchdog reset.
-
Increased default maximum temperature excursion from 10C to 15C
-
M104 and M109 now default to tool 0 if no tool is specified or active instead of giving an error message
-
M109 activates the tool if it was not already active
-
M191 (set chamber temperature and wait) is now supported. However you may wish instead to use M141 followed by M116 later to wait for all temperatures.
-
M109, M109 and M191 commands support both R and S parameters as Marlin does. If you specify temperature using the S parameter, then the system will only wait until temperature is reached if the temperature is below target. If you use the R parameter instead, it will wait if cooling down too.
-
M143 now takes an H parameter to specify the heater whose temperature limit you are setting. If it is not provided then heater 1 is assumed.
-
You can now specify a Stenhart-Hart C coefficient in the M305 command, for better thermistor accuracy over a wide temperature range. If you do use a non-zero C coefficient then you will need to change the B (beta) parameter as well. The B parameter should be the reciprocal of the Steinhart-Hart B coefficient.
-
The thermistor disconnected detection now takes account of the thermistor parameters configured with M305. This should allow the Dyze thermistor to be used without getting so many 'thermistor disconnected' reports. You may need to use a small negative H parameter in your M305 command to make it reliable.
-
Multiple commands from different sources that do not interfere are executed concurrently. Previously, only a few status reporting commands could be executed concurrently with other commands.
-
Fixed bad JSON message during printing when there were no active extruders
-
Fixed reset reason text because on the Duet WiFi a watchdog reset can look like an external reset
-
Fixed bug: software reset codes were not stored or retrieve on the Duet WiFi
-
Fixed bug: M300 now causes a beep on PanelDue again (was broken in 1.16).
Important! See the upgrade notes at https://github.com/dc42/RepRapFirmware/blob/dev/WHATS_NEW before upgrading to this release.
The recommended web interface is still DWC 1.13. For the Duet WiFi, the recommended web server is still 1.03-ch.
Please report any new bugs in this thread (do not report old bugs here unless I have previously indicated that they will be fixed in 1.17). If no serious bugs are reported, I will release 1.17 a few days from now.
-
-
Hi David,
What do you mean by removed M201, acceleration cannot be set in configuration? Sorry I don't understand how it can be automatically done.
Thanks !
Hugues -
Yes, I too would like to know how I can set my accelerations if I can't use M201.
-
I said I removed the max average printing acceleration parameter in M201, not the standard M201 command parameters. I think very few people knew that extra parameter existed.
-
You're right, I never heard this parameter….
-
Me neither. I checked here before I posted and there is no mention of it http://reprap.org/wiki/G-code#M201:_Set_max_printing_acceleration.
Anyway, no worries (although if the sentence had read "Removed maximum average printing acceleration parameter from M201" rather than starting with "Removed M201….........." it would have had a less traumatic effect on my blood pressure)
-
Ok, I just changed the text to reduce confusion.
I plan to implement M202 as well in 1.18 to provide even more control over acceleration.
-
Thanks - blood pressure back to normal
-
Is there a difference between "G29 S1" and "M375"?
And while we're at it - is there a difference between using "M557" and "G29" or just using "G30 P…" for bed compensation? -
G29 S1 and M375 do the same.
M557/G29 and using G30 P commands in a bed.g file do different things. The bed.g file allows you to specify all the XY coordinates and also probe trigger height corrections, but you are limited to 5 points and there is no tapering. G29 allows many more probe points but because the coordinates are computed from the grid parameters, there are no trigger height corrections.
-
With the grid compensation tapering off feature, I presume if I am running 1.17 rc1 and have not specified an M376 command the compensation continues for the whole object? I only ask as I installed this firmware today and printed two 50mm tall cylinders. They have both come out slightly sloping i.e. x/y not perpendicular to Z. I am running a delta with a tooling plate bed, I've never seen any object sloping before. I cannot be certain the bed is absolutely perpendicular to the towers.
My console showed
22:23:42Done printing file
18:23:5718 points probed, mean error -0.01, deviation 0.07
Height map saved to file heightmap.csv
18:23:32G10 P0 S180
18:22:54Calibrated 7 factors using 10 points, deviation before 0.100 after 0.036
and my height map
RepRapFirmware height map file v1 generated at 2016-11-15 18:23, mean error -0.01, deviation 0.07
xmin,xmax,ymin,ymax,radius,spacing,xnum,ynum
-120.00,120.10,-120.00,120.10,140.00,60.00,5,5
0, 0.099, -0.030, -0.101, 0
0, -0.034, -0.035, -0.059, -0.194
0.014, -0.031, 0.030, 0.034, -0.103
0, 0.066, 0.074, 0.056, 0.095
0, 0, -0.028, 0.014, 0 -
Yes the compensation continues throughout the print by default. Can you post pictures, and also try the same print without using grid compensation?
Also, after a skewed print, please run M122 and see if any step errors were recorded.
Your bed map does appear to have a tilt towards the high X low Y corner, but only a fraction of a mm. However, it might be caused by effector tilt changing the Z probe trigger height rather than a real tilt.
-
Okay so tried a few f/w versions and grid compensation on and off, still skewed so it's not firmware. Will start a new thread see if anyone had any ideas. https://www.duet3d.com/forum/thread.php?pid=5895#p5895
