RepRapFirmware 3.0 is released!

c310

@deckingman said in RepRapFirmware 3.0 is released!:

M950 needs to be before M106

thanks! is works fine now. i have updated M950 documentation

DIY-O-Sphere

Successfully updated my Maestro from 2.05 to 3.0
I have done almost everything manual, but for reference also generated the files with RRF Config Tool.
For me that was the best way to get familiar with the new pin assignment.
@chrishamm: Apart from that it was not possible to select the right pin assignment for BL-Touch within RRF-CT.

With a customised 12864 display menu system and some macros I had to check around 70 files...
I would recommend Notepad++ as it provides a option to find multiple words.
It has only take some minutes to identify the relevant files.

As often, the time for converting itself depends on your own knowledge.
But in the end it was easy than expected.

Danal

Update via Pi, and all went well on DSF and 6HC main board. Had to manually issue a M997 B1 for expander. (This may be expected behavior at this point).

dc42

@Danal said in RepRapFirmware 3.0 is released!:

Had to manually issue a M997 B1 for expander. (This may be expected behavior at this point).

Yes it is.

Alexander Mundy

So what if any config changes would I need to make going from 3.0 Beta on a Duet2 WiFi? I already use S1 in M574.

Firmware Name: RepRapFirmware for Duet 2 WiFi/Ethernet
Firmware Electronics: Duet WiFi 1.02 or later
Firmware Version: 3.0beta5+4 (2019-06-22b1)
WiFi Server Version: 1.23
Web Interface Version: 1.22.6

G90                                         ; Send absolute coordinates...
M83                                         ; ...but relative extruder moves
M665 R226.747 L470.983 B200 H860.970 X-0.483 Y-0.268 Z0  ; Set delta radius, diagonal rod length, printable radius and homed height
M666 X0.18 Y-0.11 Z-0.07 A0.17 B-0.18       ; Put your endstop adjustments here, or let auto calibration find them
M579 X0.998 Y0.999

; Non Linear Advance
M592 D0 A0.001 B0.0004 L0.4                 ; PETG

; Network
M550 P"400"                                 ; Set machine name
M552 S1                                     ; Enable network

M586 P0 S1                                  ; Enable HTTP
M586 P1 S0                                  ; Disable FTP
M586 P2 S0                                  ; Disable Telnet

; Drives
M569 P0 S1                                  ; Physical drive 0 goes forwards
M569 P1 S1                                  ; Physical drive 1 goes forwards
M569 P2 S1                                  ; Physical drive 2 goes forwards
M569 P3 S1                                  ; Physical drive 3 goes forwards
M350 E16 I0                                 ; Configure microstepping without interpolation
M350 X16 Y16 Z16 I1                         ; Configure microstepping with interpolation
M92 X160 Y160 Z160 E1330                    ; Set steps per mm
M566 X600 Y600 Z600 E600                    ; Set maximum instantaneous speed changes (mm/min)
M203 X18000 Y18000 Z18000 E10000            ; Set maximum speeds (mm/min)
M201 X1500 Y1500 Z1500 E1500                ; Set accelerations (mm/s^2)
M906 X1200 Y1200 Z1200 E1200 I30            ; Set motor currents (mA) and motor idle factor in per cent
M84 S30                                     ; Set idle timeout

; Axis Limits
M208 Z-0.1 S1                               ; Set minimum Z

; Endstops
M574 X2 Y2 Z2 S1                            ; Set active high endstops

; Z-Probe
M558 P5 R0.5 H3 F100 T3000 I1 A5 S0.02      ; Set Z probe type to effector and the dive height + speeds
G31 P500 X0 Y0 Z-0.064                      ; Set Z probe trigger value, offset and trigger height
;M558 P1 R0.5 H2 F100 T3000 I1 A5 S0.02      ; Set Z probe type to effector and the dive height + speeds
;G31 P485 X0 Y0 Z-0.064                      ; Set Z probe trigger value, offset and trigger height
M557 R195 S20                               ; Define mesh grid

M950 H0 C"nil"
M950 H2 C"nil"
M950 F0 C"nil"

; Heaters
M950 H0 C"e1heat" Q10                       ; Remap bed heater to e1 heater and frequency to 10hz
M143 H0 S120                                ; Set Bed temperature limit to 120C
M305 P0 T100000 B3950 R4700                 ; Set Bed thermistor + ADC parameters
M307 H0 A318.5 C876.2 D4.2 B0               ; Bed PID
M143 H1 S280                                ; Set Hot End temperature limit to 280C
M305 P1 T100000 B4388 R4700                 ; Set Hot End thermistor + ADC parameters
M307 H1 A491.5 C268.4 D3.8 B0               ; Hot End PID


; Fans
M950 F0 C"bedheat" Q25500                   ; Map Part Fan to bed heater mosfet / freq 25.5Khz
M106 P0 S0 L125 X255 B0.2                   ; Part Fan starts off / Min 50% / Max 100% / 100% for 0.2 Sec when turned 
                                            ; on
M106 P1 T50 S255 H1                         ; Hot End Fan 100% when Hot End >= 50C
M106 P2 T50 S125 H1                  	    ; Extruder Stepper Fan 50% when Hot End >= 50C

; Tools
M563 P0 D0 H1                               ; Define tool 0
G10 P0 X0 Y0 Z0                             ; Set tool 0 axis offsets
G10 P0 R0 S0                                ; Set initial tool 0 active and standby temperatures to 0C
T0                    		            ; select first hot end

M80                                         ; PS_ON to activate relay for heaters

A Former User

@Alexander-Mundy said in RepRapFirmware 3.0 is released!:

So what if any config changes would I need to make going from 3.0 Beta on a Duet2 WiFi? I already use S1 in M574.

All releases link to the whats new log, which you're encouraged to read before upgrading as it will list all the relevant changes; big ones breaking configurations will be usually highlighted at the top of each version.
https://github.com/dc42/RepRapFirmware/blob/v3-dev/WHATS_NEW_RRF3.md

Alexander Mundy

Not before Beta 12, at least that I could find.

A Former User

@Alexander-Mundy said in RepRapFirmware 3.0 is released!:

Not before Beta 12, at least that I could find.

there is only beta 11 between, which has some notes in the release post
https://github.com/dc42/RepRapFirmware/releases/tag/3.0beta11

Alexander Mundy

Thank you. I lost track of 3 beta after I got it working for one of my printers that needed the remapping features because it worked and I didn't need more. But now that stable is out I figure time to upgrade because future release will be based from this one.

Shotfire

I've upgraded to 3.0
Duet Wifi 2,

Have everything working, at least I think, except for my Precision Piezo Z-Probe.
X and Y are homing correctly
Z probe is acting odd.

Old Code - that worked fine:
M558 P8 R0.4 H5 I1 F1200 T6000

New Code - Not Working
M558 P8 C"^zprobe.in" R0.04 H5 F1200 T6000

The Dashboard shows Z-Probe "1000" when I tap on it, it immediately goes to "0" then back to "1000"
If I remove the Invert Character "^" the dashboard right after connecting shows "1000".
When I tap on it, it will go to "0" and stays there for about 10 seconds and then goes back to "1000"

Any Ideas?

dc42

@Shotfire said in RepRapFirmware 3.0 is released!:

Old Code - that worked fine:
M558 P8 R0.4 H5 I1 F1200 T6000
New Code - Not Working
M558 P8 C"^zprobe.in" R0.04 H5 F1200 T6000
The Dashboard shows Z-Probe "1000" when I tap on it, it immediately goes to "0" then back to "1000"
If I remove the Invert Character "^" the dashboard right after connecting shows "1000".
When I tap on it, it will go to "0" and stays there for about 10 seconds and then goes back to "1000"
Any Ideas?

You used I1 in your old M558 command, therefore you need to use pin name "!zprobe.in" in the new command. If the probe needs a pullup resistor (as appears to be the case), you will need to use "^!zprobe.in".

Shotfire

@dc42 Thanks I will try that.

DaBit

Took the plunge and moved to RRF3.0. Sooner or later I will have to move anyway if I ever want to use conditional G-code, and it seems wiser to move before honing in the toolchange procedures.

Some weirdness. The X/Y endstop switches. These are normally open active low NPN proximity sensors. Configured in RRF2 like this:

; Endstops
M574 X1 Y2 S0                                   ; set active low and disabled endstops
M574 Z1 S2                                      ; set endstops controlled by probe

The RRF config tool generates this code:

; Endstops
M574 X1 S0 P"xstop"                                    ; configure active-low endstop for low end on X via pin xstop
M574 Y2 S0 P"ystop"                                    ; configure active-low endstop for high end on Y via pin ystop
M574 Z1 S2                                             ; configure Z-probe endstop for low end on Z

Which is not correct; according to the M574 documentation the S parameter should be 1 (microswitch-type endstop), and I suppose I need to do the inversion on the pins. Which seems to work:
(I also enabled the pullups)

; Endstops
M574 X1 S1 P"^!xstop"                                    ; configure active-low endstop for low end on X via pin xstop
M574 Y2 S1 P"^!ystop"                                    ; configure active-low endstop for high end on Y via pin ystop
M574 Z1 S2                                             ; configure Z-probe endstop for low end on Z

Next is Z homing. My RRF3 homez.g script, taken from the configurator and adjusted coordinates:

G91                ; relative positioning
G1 H2 Z5 F6000     ; lift Z relative to current position
G90                ; absolute positioning
G1 H2 X115 Y115 F6000 ; go to first probe point
G30                ; home Z by probing the bed

; Uncomment the following lines to lift Z after probing
G91               ; relative positioning
G1 H2 Z5 F100     ; lift Z relative to current position
G90               ; absolute positioning

The G1 H2 X115 Y115 fails, and actually moves to X115 Y0? I suppose it moves the CoreXY motors independently. Removing the H2 does not work; you cannot move axes that are not homed yet.

I hacked it with a pair of M564 commands:

G91                ; relative positioning
M564 S1 H0
G1 Z5 F6000     ; lift Z relative to current position
G90                ; absolute positioning
G1 X115 Y115 F6000 ; go to first probe point
G30                ; home Z by probing the bed

; Uncomment the following lines to lift Z after probing
G91               ; relative positioning
G1 H2 Z5 F100     ; lift Z relative to current position
G90               ; absolute positioning
M564 S1 H1

This works, but it is probably not how I am supposed to do that?

mihaitintea

I have a custom built delta printer with the latest Duet2Wifi board avec Duex5, running the latest RRF 2.x.

I use the latest Cura 4 for slicing.

If I do the RRF2 -> RRF3 upgrade for these boards (Duet2Wifi avec Duex5) , will the GCode generatedf by Cura 4 still work on my delta printer, or do I have to look for another slicing software ?

Danal

@mihaitintea said in RepRapFirmware 3.0 is released!:

I have a custom built delta printer with the latest Duet2Wifi board avec Duex5, running the latest RRF 2.x.

I use the latest Cura 4 for slicing.

If I do the RRF2 -> RRF3 upgrade for these boards (Duet2Wifi avec Duex5) , will the GCode generatedf by Cura 4 still work on my delta printer, or do I have to look for another slicing software ?

Should be no change to the slicer at all. There MIGHT be something in the start G-Code to adjust... but I really doubt it.

Do be aware that your config.g will require quite a bit of change. Look at all the guides for the Duet3.

dc42

@DaBit said in RepRapFirmware 3.0 is released!:

The RRF config tool generates this code:
; Endstops
M574 X1 S0 P"xstop"                                    ; configure active-low endstop for low end on X via pin xstop
M574 Y2 S0 P"ystop"                                    ; configure active-low endstop for high end on Y via pin ystop
M574 Z1 S2                                             ; configure Z-probe endstop for low end on Z
Which is not correct; according to the M574 documentation the S parameter should be 1 (microswitch-type endstop), and I suppose I need to do the inversion on the pins. Which seems to work:

You are correct. We'll get configtool fixed.

Next is Z homing. My RRF3 homez.g script, taken from the configurator and adjusted coordinates:
...
The G1 H2 X115 Y115 fails, and actually moves to X115 Y0? I suppose it moves the CoreXY motors independently. Removing the H2 does not work; you cannot move axes that are not homed yet.

The H2 should be removed. Surely X and Y have been homed by that point? It doesn't make sense to try to home Z using a Z probe if you can't set the XY coordinates.

DaBit

X and Y have been homed before Z.
I tested by accidentally removing the H2 at the first Z-lift too, my bad.

This works:

; homez.g
; called to home the Z axis

G91                ; relative positioning
G1 H2 Z5 F6000     ; lift Z relative to current position
G90                ; absolute positioning
G1 X115 Y115 F6000 ; go to first probe point
G30                ; home Z by probing the bed
G91                ; relative positioning
G1 Z5 F6000        ; lift Z relative to current position
G90                ; absolute positioning

Anyway, the RRF configurator is generating (imho) wrong code for this too; it produces a H2 for both the lift-Z and X/Y positioning moves.

RRF config tool generated homez.g:

; homez.g
; called to home the Z axis
;
; generated by RepRapFirmware Configuration Tool v2.1.4 on Sun Jan 05 2020 10:48:15 GMT+0100 (Midden-Europese standaardtijd)
G91                ; relative positioning
G1 H2 Z5 F6000     ; lift Z relative to current position
G90                ; absolute positioning
G1 H2 X19 Y1 F6000 ; go to first probe point
G30                ; home Z by probing the bed

; Uncomment the following lines to lift Z after probing
;G91               ; relative positioning
;G1 H2 Z5 F100     ; lift Z relative to current position
;G90               ; absolute positioning

Alexander Mundy

FYI for anyone else moving from early beta (before 11) I had to do the following:
Define heaters and associated temp sensors
Use M308 instead of M305
Activate the pullup resistors for endstops and z probe if needed since they are not active by default
I had remapped the bed heat and part cooling fans previously and had M950 H0 C"nil" and M950 H2 C"nil" but removed them since heaters are no longer automatically assigned.

wilriker

@tobias_munich said in RepRapFirmware 3.0 is released!:

Is the the paneldue running on the DUET3 with this release yet?
saw that IO_0 should be reserved for this.

Yes, it does. Connect it to IO_0 and it will work. If you are using Duet3 + SBC then everything related to job files and macros will not work on PanelDue because it cannot see those (maybe also contents of /sys, haven't checked that).

Hornetrider

Hi

I am not sure if this is off topic in this thread...sorry...

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...
Could there be an option to change them to something simpler like before?

I am having real fun using the Duet3 and RRF3.0. Damn good job!