RepRapFirmware 3.01-RC5 available

dc42

Download DuetMaestroIAP.bin from the 3.0 release and upload it to /sys on your Duet.

zorro_66

Worked perfectly thanks ...

bberger

Is there any documentation on how the object cancellation works?

I know that there isn't any interface for DWC (yet), but I might just patch that in if I get some spare time and an endpoint documentation.

droftarts

@bberger See https://duet3d.dozuki.com/Wiki/Gcode?revisionid=HEAD#Section_M486_Object_cancellation
and @dc42 's thread here: https://forum.duet3d.com/topic/15119/cancel-individual-objects-on-the-build-plate
No other documentation as yet. I believe that PrusaSlicer can generate appropriate tags, but haven't tested it yet.
@chrishamm was talking about adding it to DWC, but has other priorities at the moment, so I'm sure would be happy if someone else wanted to help out!

Ian

dc42

@droftarts said in RepRapFirmware 3.01-RC5 available:

@bberger See https://duet3d.dozuki.com/Wiki/Gcode?revisionid=HEAD#Section_M486_Object_cancellation
and @dc42 's thread here: https://forum.duet3d.com/topic/15119/cancel-individual-objects-on-the-build-plate
No other documentation as yet. I believe that PrusaSlicer can generate appropriate tags, but haven't tested it yet.
@chrishamm was talking about adding it to DWC, but has other priorities at the moment, so I'm sure would be happy if someone else wanted to help out!

To expand on this:

The "Label objects" option in PrusaSlicer will generate object labels in the GCode file that RRF 3.01-RC5 and -RC6 understand.
The list of known objects on the build plate and their XY limits is already included in the object model (send M409 K"job.build.objects" to retrieve it) so that future versions of DWC will be able to offer an interface to select an object to be cancelled.
Meanwhile, the M486 command can be used to cancel an object.

bberger

Thank you guys for your quick reply! Let's see if I can hack something together shortly.

The switch to Vue and Vuetify greatly helps in my case. Thank you for going down that road!

jbarros

@dc42
Mine being a v0.4 and from reading other threads about this issue does not have the extra filter capacitors.
2 UTP cables for fans and sensors, extruder heater AND extruder stepper cable all running at least 1m alongside each other might explain my issues.
Waiting for proper cables from China, I used a temporary shielded cable just for this sensor.

I'm happy to report the issue has not happened again

Pumlux

Bug or feature ?

Temperture is dopping during a long time consuming move / home all .

I'm running a Duet Wifi 1.01 board and ugraded some weeks ago to RRF3.
I noticed that the heater seems to be not heating if a time consuming move is made.

In detail :
I heat up the bed to 50 degrees and the extruder to 200 degrees and than I do homing all.
During the move to home all axes the heater seems to be not heating, the time for homing was aprox. 2 min 30 sec and the extruder temperature drops from 200 to ~140 degrees. (see screenshot below ) when all the moves for homing are completed the temperature is rasing again to targeted 200 degrees.
(I see this temperture drop on the long time z-axis movement, not sure about the x and y axis)

In addtition, If the duet is heating up to the target temperature e.g. from 20 degrees to 200 degrees, I can not do printhead moves until temperture is reached (not always, I don't know what makes the difference here) .

It looks like moves and heating can not be done in parallel, not sure if this behavior comes from the duet firmware or from the web firmware.

I just noticed it on RRF 3.01 RC4 and RC5.

Duet RRF3 Temperture heating.jpg

dc42

@Pumlux said in RepRapFirmware 3.01-RC5 available:

I noticed that the heater seems to be not heating if a time consuming move is made.
In detail :
I heat up the bed to 50 degrees and the extruder to 200 degrees and than I do homing all.
During the move to home all axes the heater seems to be not heating, the time for homing was aprox. 2 min 30 sec and the extruder temperature drops from 200 to ~140 degrees. (see screenshot below ) when all the moves for homing are completed the temperature is rasing again to targeted 200 degrees.
(I see this temperture drop on the long time z-axis movement, not sure about the x and y axis)

That will be because you have your M558 command set up to turn heaters off during bed probing (B1 parameter).

You could avoid it by probing twice. First send M558 B0 to enable heating during probing; then do a G30 command; then raise Z a little; then send M558 B1 to disable heaters during probing (assuming that you need to in order to get accurate results); then do another G30.

Pumlux

@DC42
David you are fast and you are right.
Thanks for your helpfull advice.

I had the M558 with B1 parameter (got is from setup example for BL-Touch) and wasn't aware of the impact of the B1 parameter.
Keeping the heater on as default is the better choice. Not sure if the homing will be that much more accurate with heaters switched off. Would need to check this.

With heaters off during homing I run into undertemperture issue with no extruding because of low temperture when the printhead was located very high over the bed. This is solved now.

dc42

@Pumlux said in RepRapFirmware 3.01-RC5 available:

With heaters off during homing I run into undertemperture issue with no extruding because of low temperture when the printhead was located very high over the bed. This is solved now.

You could have used command M116 after homing to avoid that; but I'm glad it's solved now.

Pumlux

I got the parameter B1 example from duet3d.dozuki. It might be a worth to change the B1 parameter to B0 in the toubleshooting doku for BL-Touch.

Modify your M558 and G31. The BLTouch behaviour is controlled by the M558 and G31 commands in config.g. Here is what an ideal set of commands should look like.  


M558 P9 F100 H5 R0.2 T6000 A5 B1 


This sets probe type 9 for BLTouch, 100mm/min probe speed, 5mm dive height, 0.2 second pause time before probe move, 100mm/s travel moves between probe points, probe up to 5 times , or until 2 consecutive probe results match, and disable heaters during a probe move to limit interference. G31 P25 X10 Y10 Z2 Sets the trigger sensitivity to 25, the X Y and Z values should be measured to match your setup.

Phaedrux

@Pumlux said in RepRapFirmware 3.01-RC5 available:

It might be a worth to change the B1 parameter to B0 in the toubleshooting doku for BL-Touch.

Well the problem with that is that turning the heaters off is a solution to other BLTouch problems, so it's not as simple as one way works for all cases.

As DC42 mentioned, the real solution would be to use M116 to wait for temps to return to the set point before proceeding.

It would also be a good idea to check to see if B0 or B1 works better for your setup.