Microstepping Interpolation not working in 1.20.1RC2

  • Afternoon!

    I've been doing some tinkering with our CoreXY and made the choice to update to 1.20.1RC2

    After this change, it appears that I0/1 command in the M350 command has no impact. Setting the value to I1 leaves the printer "noisy" as if it was set to I0.

    I've tested this both bymanually jogging the machine as well as printing a part. I've also confirmed that the behavior is the same whether changing the config.g file or sending the command "M350 X16 Y16 Z16 E16:16 I1" from the G-code console.

    I'll start another thread, but I also now have a condition where the stall detection/sensorless endstops do not hold their values. It causes a second click of the homex/y/z button to no longer respond appropriately (the axis moved opposite of normal which is exciting).

    Software Information
    Firmware Name: RepRapFirmware for Duet WiFi
    Firmware Electronics: Duet WiFi 1.0
    Firmware Version: 1.20.1RC2 (2018-01-01)
    WiFi Server Version: 1.20+1
    Web Interface Version: 1.20
    Web Interface by Christian Hammacher
    Licensed under the terms of the GPL v3

    Below is my config.g:

    M111 S0
    M550 AMSS Airwolf
    M555 P2
    M552 S2
    M667 S1
    M569 P0 S1
    M569 P1 S1
    M569 P2 S0
    M569 P3 S1
    M569 P4 S1
    M915 P0:1:2 S5 R0
    M574 X1 Y1 Z2 S3
    M906 X1000 Y1000 Z800 E1000:1000
    M201 X3000 Y3000 Z200 E500
    M203 X15000 Y15000 Z500 E3600
    M566 X600 Y600 Z30 E200	
    M208 X344 Y230 Z244
    M208 S1 X-25 Y0 Z-0.5 
    M92 X100 Y100 Z400
    M92 E288:288
    M350 X16 Y16 Z16 E16:16 I1
    M558 P1 Z1
    G31 P500 Z2.4
    M305 P0 T100000 B3950 R4700 H0 L0
    M305 P1 T100000 B3988 R4700 H0 L0
    M305 P2 T100000 B3988 R4700 H0 L0
    M106 P2 T45 H1:2
    M572 D0 S0
    M572 D1 S0
    M572 D3 S0.1
    M572 D4 S0.1
    M563 P0 D0 H1 F3
    G10 P0 S0 R0 X0 Y0
    M563 P1 D1 H2 F3
    G10 P1 S0 R0 X22 Y0
    M143 H0 S150

  • administrators

    You probably need to move both axes slightly away from the endstops after homing them in order for a new stall to be recognised.

  • Tried that.

    Adding M915 P0:1 S5 R0 to the beginning of the homex/y/z.g file resolves the issue, but I'm still interested to know what changed.

    Any thoughts on Interpolation?

    I did notice that in the above config.g my M350 is below M92 commands. It was a mistake on my part ( the M92 commands are x16 steps) so in retrospect, I should have been getting huge moves, however that isn't happening. Putting the M350 command before or after those calls makes no difference whatsoever.

  • administrators

    The default microstepping is x16 so if your M350 command specifies x16 microstepping, it doesn't make any difference whether it is before or after M92.

    You can run M350 without parameters after changing interpolation to check that the on/off state is as you expect.

Log in to reply