Software bundle 3.6.0-beta.1 now available
-
On behalf of the Duet3D team I am pleased to announce the release of firmware 3.6.0-beta.1. Users running Duets in standalone mode can download it from https://github.com/Duet3D/RepRapFirmware/releases/tag/3.6.0-beta.1. Users running with attached SBC can update from the unstable feed of the package server.
RRF release notes: https://github.com/Duet3D/RepRapFirmware/wiki/Changelog-RRF-3.x-Beta#reprapfirmware-360-beta1
DWC release notes: https://github.com/Duet3D/DuetWebControl/wiki/Changelog-DWC-3.x-Beta#version-360-beta1-changes-since-353
DSF release notes: https://github.com/Duet3D/DuetSoftwareFramework/wiki/Changelog-DSF-3.x-Beta#version-360-beta1-changes-since-353Compared to firmware 3.5.3 the major feature in this release is the new input shaping algorithm. Additionally, support for communication with devices supporting Modbus RTU is provided on Duet 3 boards.
If you encounter any issue with this release, please describe them in a new thread, including [3.6.0-beta.1] in the topic title.
-
Is the mini 5+ going to be included not seeing a file for it
-
@DangerMouse88 I just noticed that too, suspect he forgot to upload it
-
@Exerqtor correct. I've just added it.
-
@dc42 does the new input shaping algorithm also mean that something similar to the Klipper "minimum cruise ratio" (https://www.klipper3d.org/Kinematics.html#minimum-cruise-ratio ) is supported by RRF 3.6.0?
-
@NeoDue no we haven't implemented that yet, it's separate from input shaping.
-
@dc42 I'm not sure what's changed between the last alpha and the current beta but the Jubilee is once again dropping tools even with the M400's...
edit: on a side note it primarily appears to happen after I cancel a print and it parks the tool. At this point I'm reverting to the alpha 5 as it's been pretty solid.
-
I didn't have an M400 command after the tool park in my cancel.g file so that may be the culprit. I'll add it and retry but it won't be until tomorrow.
-
A few prints in and it seems as if adding the M400 to cancel.g addressed the issue. I guess I haven't been cancelling prints on the alpha.. Otherwise all seems to be working as expected.
-
@dc42 said in Software bundle 3.6.0-beta.1 now available:
@NeoDue no we haven't implemented that yet, it's separate from input shaping.
Thanks! Then I will wait until 3.6 is final.
-
Im tracking a possible bug (hard to determine if its hardware or firmware) relating to motor idle current.
Testing hardware is a E3D RotoCurrent working theory is when pause.g is pressed and the motors go into the lower power idle state. the Extruder motor also goes to a lower amperage mode, however when resuming or manually extruding the motor does wake up and stays at a low power mode.
Once I'm back from the trade show I am on (1 week left) I can swap extruders to check different types to see if the behaviour is consistent or just a behaviour of the Roto
-
@Notepad I have run into something similar to this, but I can't reproduce it yet... detailed my experience at the bottom of the earlier 3.6.0 alpha build thread.
-
@dc42 said in Software bundle 3.6.0-beta.1 now available:
[3.6.0-beta.1]
Did you get around to trying to reproduce Z axis clicking on linear delta with very slow, long-lasting moves? I'm still seeing this in the beta, albeit possibly somewhat reduced from the alpha.
-
Hey @dc42
I can't see anything in the release notes as to whether the new input shaping/3.6 release, has been released for the 1HCL boards or is it in development?
Sam
-
@samlogan87 yes it's implemented in 3.6beta1 on all expansion boards including 1HCL and M23CL motors.
-
@dc42 awesome thank you. Will update tonight and give it a try
-
Possible bug in 3.6.b1. Once a printer is Estop'ed the PanelDue sometimes doesn't reconnect and gets stuck in a connecting state. I have absolutely no idea how to gather data for this other than an observation + the behaviour is inconsistent.
This may be related to another issue I am diagnosing (I am not sure its a RRF issue or just a user setup issue so I didn't mention it before) where the PanelDue connected to a D36HC w/ SBC seems to have random slow response times. Pressing a button can take up to 2 seconds before the press is registered/actioned, some other times is instant like normal. This behaviour is not present in any of my D2 machines that do not include an SBC