RepRapFirmware 3.0 is released!
-
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
-
@dc42 Must say this runs nicely, once I got over an error on my part, must learn to RTFI :-).
-
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.
-
@DaBit said in RepRapFirmware 3.0 is released!:
Difference with RRF2.05 is 0.12mm smaller.
I can confirm that for a Maestro.
-
Hello i just upgrade and after upgrade it's show that
![alt text]( image url)what i did wrong?
Matej
-
I haven't tested RRF 3.0 with DWC 1.22.6. I suggest you upgrade to DWC 2.0.4.
-
how i do that and what changes are with this DWC
-
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.
-
Is this DWC make change to config or any code or just for web interface
-
Upgrading DWC does not require configuration changes.
-
@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?!
-
@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? -
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
-
@matej1006
https://duet3d.dozuki.com/Wiki/RepRapFirmware_3_overview#Section_M305
https://duet3d.dozuki.com/Wiki/RepRapFirmware_3_overview#Section_M558
But you also have to edit some more places in config.g and in some files in sys folder. Maybe it's easy to do the base of conversion with the online configurator. -
@DIY-O-Sphere Thanks
-
Hi,
i think there is a small bug in the Machinesettings E0 display the wrong settings:btw. I miss this feature in dwc2!
-
Can I control my water temperature (PWM noctua Fan's) with out selected heater in code, just with one sensor which measuring water temp.?
-
@matej1006 said in RepRapFirmware 3.0 is released!:
Can I control my water temperature (PWM noctua Fan's) with out selected heater in code, just with one sensor which measuring water temp.?
Yes, set up a sensor for the water temperature (M308), then set the fan to run thermostatically based on that sensor. In RRF3 the H parameter in the M106 command is the sensor number, not a heater number.
-
@dc42
Like that:;Water temp M308 S5 P"e1temp" Y"thermistor" T100000 B4138 ;configure sensor 5 as thermistor on pin e1temp ; Fans M950 F0 C"!Fan0+exp.pb6" Q25000 ; fan 0 is a 4-wire PWM fan so invert it, use high PWM frequency, tacho connected to PB6 on expansion connector M106 H0 S1 T25
and can i control 3 fan with one PWM output and one tacho input?
-
@deckingman
Today I had to undo the change....