RRF 3.0 & homedelta.g

jay_s_uk

Here is my homeall.g which works

G91                        ; relative positioning

G1 H1 X470 Y470 Z470 F1800 ; move all towers to the high end stopping at the endstops (first pass)
G1 X-5 Y-5 Z-5 F1800 H2    ; go down a few mm
G1 H1 X10 Y10 Z10 F360     ; move all towers up once more (second pass)
G90                        ; absolute positioning

ludisnet

Thanks @jay_s_uk ,

Here my test in RRF3 :

#########################
G91 ; use relative positioning
;******* Change F250 in the following line to F2500 when you are finished commissioning
;******* Change 320 in the following to a higher value if your Kossel has taller towers
G1 H1 X320 Y320 Z320 F2500 ; move all carriages up 320mm, stopping at the endstops
G1 X-3 Y-3 Z-3 F2500 H2 ; move all carriages down 3mm
G1 H1 X6 Y6 Z6 F250 ; move carriages slowly up 6mm, stopping at the endstops
G1 Z-5 F2000 ; down a few mm so that we can centre the head
G90 ; back to absolute positioning
G1 X0 Y0 F2000 ; centre the head and set a reasonable feed rate
#########################

the mechanics move down .... Three centimeters, and it stops.

Any ideas? a bad config.g configuration?

during the upgrade RRF2 to 3, I just modified config.g with :

del. M305
add. M308 & M950

...nothing changed in the mechanics config , right?

Thank you

jay_s_uk

You'll need to make endstop changes too.
My RRF3 config for my delta can be found at https://github.com/jaysuk/Anycubic-Predator-Duet/tree/SmartEffectorRRF3 for reference

ludisnet

...thanks,

Okay, now I've seen that my M574 is wrong... with :

M574 X2 Y2 Z2 S0

ludisnet

Solved :

; Endstops
M574 X2 S1 P"!xstop" ; configure active-high endstop for high end on X via pin xstop
M574 Y2 S1 P"!ystop" ; configure active-high endstop for high end on Y via pin ystop
M574 Z2 S1 P"!zstop" ; configure active-high endstop for high end on Z via pin zstop

Thanks @jay_s_uk

Ludis

droftarts

@ludisnet You can use the RRF configuration tool https://configtool.reprapfirmware.org/Start to generate an RRF3 compatible config.g, either to replace or to update your existing config.g. If you're stuck on one part, you don't have to do the whole config, just the relevant parts, and look at the generated config.g to get yours correct.

Ian

ludisnet

ok, thanks @droftarts ,

Do you know how import (existing) config.g , ....... and the configurator wants json?

Ludis

droftarts

@ludisnet Unfortunately you can't import a config.g into the configuration tool, only a json file. If you have created a configuration, at the end you get to choose if you want to download the json file of that configuration. Or download the configuration bundle, that includes the json file.

Ian

droftarts

I've raised an issue (more of a feature request) for a json configuration export from the firmware that is compatible with the RRF configuration tool. See https://github.com/chrishamm/configtool/issues/25

Ian

droftarts created this issue in chrishamm/configtool

open Export json from RRF to config tool #25

ludisnet

I did the configuration in the configurator, now I have a "clean" config.g, ...... everything is fine ...with RRF3.

thank you for your help!

Ludis