Question about extruder motor settings



  • Hi,

    I am in the process of testing different types of extruders.

    For clarity I have grouped the appropriate settings together within the config.g file...

    ; --- for Nimble extruder on E0 ---
    M92 E2600 ; steps per mm
    M906 E500 ; motor current (mA)
    M201 E120 ; acceleration (mm/s^2)
    M203 E1200 ; max speed (mm/min)
    M566 E40 ; max instant speed change (jerk) (mm/min)

    ...which works fine when I am testing a machine that only has one extruder.

    My question is the any way to continue this format approach for a machine that has multiple different extruders.

    The documentation example for M92 shows M92 E420:500 which does not allow the format I would like to use.

    If not could the powers-that-be give some thought to allowing for this format - which probably has a potential group of users consisting of just me.

    Thanks.

    Frederick


  • administrators

    @fcwilt i am afraid that the array method of passing the information is pretty deeply embedded in both the firmware and in the way we use gcodes to pass information.

    Can you not compromise with:

    ; --- for Nimble extruder on E0: Titan on E1: Bontech on E2: etc ---
    M92 E2600:460:500	; steps per mm
    M906 E500:600:700	; motor current (mA)
    M201 E120:1200:1000	; acceleration (mm/s^2)
    M203 E1200:3000:3000	; max speed (mm/min)
    M566 E40:300:250	; max instant speed change (jerk) (mm/min)
    

    Or whatever. I know its not idea but I can't see I having such a major change to the way the gcode works.



  • @t3p3tony said in Question about extruder motor settings:

    @fcwilt i am afraid that the array method of passing the information is pretty deeply embedded in both the firmware and in the way we use gcodes to pass information.

    Can you not compromise with:

    Or whatever. I know its not idea but I can't see I having such a major change to the way the gcode works.

    I suspected as much which is why I made the remark about being needed by a group of one. 🙂

    I worked as a programmer for 35+ years and settled on simplified XML for configuration files. Too verbose for many applications but easy to expand without breaking anything. And of course nothing depends on position or order.

    Not complaining, love the Duet family and given the products on the market I would use nothing else.

    Thanks.

    Frederick


Log in to reply