RRF3 and 2 separate Z sensors



  • just a brain check ... if I want to use 2 different Z sensors I just do a new M558 before sensing and go as usual?

    I am testing the andromeda version of precision piezo on my ender5 with bltouch and if I'm satisfied with andromeda I'll drop the bltouch; but till I'm sure I'm happy with andromeda I would like to be able to use them both



  • can you explain what you want to do?

    do you want to have the option to switch or do you want them active at the same time?



  • @smece said in RRF3 and 2 separate Z sensors:

    if I want to use 2 different Z sensors I just do a new M558 before sensing and go as usual?

    Yes basically. As long as you can have both plugged in at the same time all you need to do on the configuration side is send the appropriate M558 and G31 configurations before calling the probe with G30.

    You could leave the BLTouch configured as it is and have the configuration for the andromeda in a separate macro.



  • dunno how would they work at the same time 😄 ... I would not mind that just not sure that's possible

    the idea is .. I do

    if I wanna test with bltouch:

    M558 K0 P9 C"^zprobe.in" H5 F120 T3000 A2
    M950 S0 C"exp.heater3"
    G31 K0 P100 X35 Y0 Z2.2 
    G29
    

    or if I wanna test with andromeda

    M558 K1 P5 C"zstop" H5 F120 T3000  ; maybe P8 here for piezo ?!
    G31 K1 P100 X0 Y0 Z0 
    G29
    

    or I need to use K0 on both? or I define in gcode.g both

    M558 K0 P9 C"^zprobe.in" H5 F120 T3000 A2
    M950 S0 C"exp.heater3"
    G31 K0 P100 X35 Y0 Z2.2 
    ;
    M558 K1 P5 C"zstop" H5 F120 T3000 
    G31 K1 P100 X0 Y0 Z0 
    

    but how then I tell G29 or G28 or G28Z to use K0 or K1 ?!



  • It will use the most recent command sent.



  • @Veti said in RRF3 and 2 separate Z sensors:

    can you explain what you want to do?

    I think I did 😄 I want to have andromeda and bltouch both connected in the same time until I'm happy that andromeda will work ok (as so far I know bltouch does) as I don't have the "cohones" to switch to andromeda alone for now 'cause I only have experience with piezo mounted on the extruder and never on the bed, and since this is new to me before I thoroghly test I don't want to remove my bltouch that I wanna use for control, for now. later on, if all goes as planned I'll remove bltouch and leave only andromeda but that config is clear

    so for now, I have them both attached and wanna chose which one I'm using... the confusing part is the K parameter in G31 and M558 but not having K parameter for G28, G29 ..



  • @Phaedrux said in RRF3 and 2 separate Z sensors:

    most recent

    what is the point of K0 and K1 then ?!



  • @smece said in RRF3 and 2 separate Z sensors:

    @Phaedrux said in RRF3 and 2 separate Z sensors:

    most recent

    what is the point of K0 and K1 then ?!

    I'm still learning RRF3 myself. Let me look into it.



  • I'm pretty sure if I use K0 both times it will work 🙂 but since there is K parameter maybe having both defined in gcode.g as K0 and K1 and then somehow telling RRF3 to use 0 or 1 😄 .. just like you can select "active tool" there's probbly a way (or will be a way) to select active z probe 😄



  • Yes that may be so, but the usage of the K parameter isn't exactly clear.

    It would seem that you may be able to use M558 K# to make that probe number active. So before you invoke the probe with G28/G29/G30 you could use M558 K# first to select the active probe. That's my guess anyway since it's not made explicit. I'll seek clarification.



  • I've received some clarification. The intention of the K parameter is as suspected, but there is currently no means to switch between configured probes.

    So at this time I would suggest ignoring the K parameter and simply using the method I described to configure the probe at time of use.



  • cool so K0 and always a full probe definition as initially assumed



  • time to figure out how all this "macro" thing works on RRF 🙂 so I don't have to copy/paste too much 😄



  • Macro is just a text file with line separated gcode commands. Executing the macro behaves the same as sending the commands via the console.

    Config.g and all the homing files are just macros.

    The Duet board has no inherent configuration. Without the SD card in the board to provide the config.g it has no personality configured.



  • @Phaedrux I guess so, I just haven't tried it (macro's) yet, so time to get on with that too 😄


Log in to reply