RepRapFirmware 3.0 is released!

dc42

@Hornetrider said in RepRapFirmware 3.0 is released!:

The symbols (double arrows) for Baby-Steps in the Print menu on Paneldue in combination with Duet3 and RRF3.0RC2 look different from RRF2.05 and are kind of missleading to me...

They used to show up and down arrows, but users complained about this because on machines that move the bed in Z, the arrows pointed in the opposite direction to the resulting bed movement. So now they show the gap between the nozzle and bed increasing or decreasing.

Danal

@dc42 said in RepRapFirmware 3.0 is released!:

they show the gap between the nozzle and bed increasing or decreasing

FWIW:

As someone who has both kinds of printers, those that move bed, and those that move nozzle, I could never figure out the old icons. The new "squeeze or separate" make it much more clear for all cases.

Hornetrider

Yeah, I got it.

Didn't think about it, regarding the Z axis as moving bed...

Thin I will get used to it as soon as I have updated my second printer to RRF3.0...

supernovae

Thanks for all your hard work @dc42! Love this update! Converted my HyperCube evo over and all is well (corexy)

kraegar

Just wanted to chime in that 3.0 is running on several RailCore's with both Duet 2's and Duet3's now with no reported troubles. Thanks for the great work @dc42 !

dc42

@kraegar, thanks for the feedback.

Do you have an application for conditional GCode on the RailCore?

kraegar

@dc42 We definitely do! Auto-leveling until below a set threshold is the obvious first one. But I've had quite a few others as well - I have a systems admin background, so being able to script within gcode has been something I've wanted for a long time. Very much looking forward to it!

kraegar

This is the "upgrade guide" I made for our users have been using to convert their RailCore's with a Duet2 to RRF3, if it's helpful to anyone else. It's taking our base RRF2.x config, and making it RRF3 compatible for new builds. There's a text document to describe the process for upgrading.

https://www.dropbox.com/sh/pg0ugu5qunokjc9/AAD8PkPqVGPp-yWV5Cug3_Usa?dl=0

stewwy

@dc42 Must say this runs nicely, once I got over an error on my part, must learn to RTFI :-).

DaBit

I did 15 hours of printing with RRF3 on the Duet. No failures due to RRF3. Random things I noticed:

I had to recalibrate the BLTouch triggerpoint to nozzle Z-offset. Difference with RRF2.05 is 0.12mm smaller.
Printing PusaSlicer generated brims at 60mm/s sounds a bit rougher than it did with 2.05. While printing the actual part I noticed no difference.
Some weirdness with 'pause print' and then not being able to cancel it in DWC. Might as well be an issue with running DWC on my (Android 7.1) phone; that usually takes a few reloads before DWC is displayed correctly anyway.

DIY-O-Sphere

@DaBit said in RepRapFirmware 3.0 is released!:

Difference with RRF2.05 is 0.12mm smaller.

I can confirm that for a Maestro.

matej1006

Hello i just upgrade and after upgrade it's show that
![alt text]( image url)

what i did wrong?

Matej

dc42

I haven't tested RRF 3.0 with DWC 1.22.6. I suggest you upgrade to DWC 2.0.4.

matej1006

how i do that and what changes are with this DWC

dc42

Move the SD card to a PC and unzip DuetWebControl-2.0.4-SD.zip into the /www folder.

You can find DWC release info at https://github.com/chrishamm/DuetWebControl/releases.

matej1006

Is this DWC make change to config or any code or just for web interface

dc42

Upgrading DWC does not require configuration changes.

A Former User

@DIY-O-Sphere said in RepRapFirmware 3.0 is released!:

@DaBit said in RepRapFirmware 3.0 is released!:

Difference with RRF2.05 is 0.12mm smaller.

I can confirm that for a Maestro.

Wow, this is weird?!

deckingman

@DaBit Ref the BL touch offset, does using a slower probing speed help? Or more specifically does probing speed affect the offset? Just wondering if there could be a latency issue between when the BL touch triggers and when the firmware reacts to that trigger. I don't use a BL touch myself so I could be way off the mark.
Edit. And is the probe connected to the main board or an expansion board?

matej1006

how i must convert this code :

;Water temp
M305 S"Water temperature" P103 X2 T10000 B3950

And that:

; Z-Probe
M574 Z1 S2 ; Set endstops controlled by probe
M558 P1 H5 F120 T3000 ; Set Z probe type to modulated and the dive height + speeds
G31 P467 X0 Y40 Z1.0 ; Set Z probe trigger value, offset and trigger height

how it's with auto bed compensation do i need there also to change anything