Very slow printing Duet Wifi on Am8



  • Hi all.
    I wanted to reply on this topic:
    Re: (SOLVED) Duet Wifi slow printing
    .. but as it is very old, I might start a new one.

    Problem is as described in title:
    My AM8 prints fine quality but veeeeeery slow.
    A print that takes like 10h on my Prusa MK3 will take about 105 houres (!) on the AM8.

    I'm sure there must be a problem, something I missed but can't find it.

    As suggested in this other thread I altered the M201-settings, went from ecceleration-speed from 800 to 1200 ... but noticed no difference whatsoever.
    I'll try bump it some more but am afraid I'm lokking in the wrong direction.

    ANyone advice?

    My Config:

    ; Configuration file for Duet WiFi (firmware version 1.20 or newer)
    ; executed by the firmware on start-up
    ; generated by RepRapFirmware Configuration Tool on Thu Jun 21 2018 02:09:12 GMT+0200 (Midden-Europese zomertijd)

    ; adaptations by ldg - june,26 '18 - 21:30 a
    ; *************************************************

    ; General preferences
    G90 ; Send absolute coordinates...
    M83 ; ...but relative extruder moves

    ; Custom code by ldg, thx JohnV 🙂
    M564 S0 H0 ; allow motormovement outside boundaries
    G21 ; work in millimeters

    ; Network
    ; **************
    ; M550 PDuettest ; Set machine name
    M550 PDuetLDG ; Set machine name
    M552 S1 ; Enable network
    ;*** Access point is configured manually via M587
    M586 P0 S1 ; Enable HTTP
    M586 P1 S0 ; Disable FTP
    M586 P2 S0 ; Disable Telnet

    ; Drives
    ; **************
    ; DIRECTION
    ; M569 P0 S1 ; Drive 0 goes forwards
    M569 P0 S0 ; Drive 0 goes backwards
    ; M569 P1 S1 ; Drive 1 goes forwards
    M569 P1 S0 ; Drive 1 goes backwards
    M569 P2 S1 ; Drive 2 goes forwards
    ; M569 P3 S1 ; Drive 3 goes forwards
    M569 P3 S0 ; Drive 3 goes backwards

    ;STEPS
    M350 X16 Y16 Z16 E16 I1 ; Configure microstepping with interpolation
    ; M92 X80 Y80 Z4000 E420 ; Set steps per mm
    M92 X100 Y100 Z400 E101 ; Set steps per mm
    M566 X900 Y900 Z12 E120 ; Set maximum instantaneous speed changes (mm/min)
    ; M203 X6000 Y6000 Z180 E1200 ; Set maximum speeds (mm/min)
    M203 X6000 Y6000 Z360 E1200 ; Set maximum speeds (mm/min)
    ; M201 X500 Y20 Z250 E250 ; Set accelerations (mm/s^2)
    ; YET TOO SLOW M201 X800 Y800 Z15 E1000 ; Set accelerations (mm/s^2)
    M201 X1000 Y1000 Z200 E1000 ; Set accelerations (mm/s^2)
    M906 X800 Y800 Z800 E800 I30 ; Set motor currents (mA) and motor idle factor in per cent -OK-
    M84 S30 ; Set idle timeout

    ; Axis Limits
    ; ***************
    ; M208 X0 Y0 Z0 S1 ; Set axis minima
    ; M208 X220 Y220 Z240 S0 ; Set axis maxima
    M208 X-36 Y-5 Z0 S1 ; Set axis minima
    M208 X184 Y215 Z240 S0 ; Set axis maxima

    ; Endstops
    ; ***************
    ; M574 X1 Y2 Z1 S0 ; Set active low endstops
    M574 X1 Y1 Z1 S0 ; Set active low endstops

    ; Z-Probe
    ; ***************
    ; !! actually no probe yet ?!?
    M558 P1 H5 F120 T6000 ; Set Z probe type to unmodulated and the dive height + speeds
    G31 P500 X0 Y0 Z2.5 ; Set Z probe trigger value, offset and trigger height
    M557 X15:205 Y15:205 S20 ; Define mesh grid

    ; Heaters
    ; ***************
    ; ldg: No idea yet if these data are default and/or correct
    M305 P0 T100000 B4138 C0 R4700 ; Set thermistor + ADC parameters for heater 0
    M143 H0 S120 ; Set temperature limit for heater 0 to 120C
    M305 P1 T100000 B4138 C0 R4700 ; Set thermistor + ADC parameters for heater 1
    M143 H1 S280 ; Set temperature limit for heater 1 to 280C

    ; ADDED by ldg
    ; Configuring, finetuning heater-functions: detecting properties, PID-settings
    ;M307 H0 ;status Bed
    ;M307 H1 ;status Extruder-heater
    ;M303 H1 P0.6 S250 ;starts autotuning Extruder
    ;M500 ;saved data to memory/config
    ;M307 H1 ;report data: gain=A ConstantTemp=C DeadTime=D
    ;M307 H1 A337.7 C175.3 D8.3 ;line can be manually added to config but should be included in automatic added file config-override.g
    M307 H1 A337.7 C175.3 D8.3 B0

    ; Fans
    ; ***************
    M106 P0 S0.3 I0 F500 H-1 ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
    M106 P1 S1 I0 F500 H1 T45 ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on
    M106 P2 S1 I0 F500 H1 T45 ; Set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned on

    ; 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

    ; Automatic power saving
    ; ***************
    M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; Set voltage thresholds and actions to run on power loss

    ; Custom settings are not configured**



  • This is a movie, made while it was simply printing a brim:
    https://www.youtube.com/watch?v=z62fujeEcYY



  • @ludodg Nothing leaps out at me from your config.g (but I might have missed something). Looking at the video, it isn't acceleration that's the problem. Do normal moves through the web interface works at the correct speed? If so, then it has to something to do with the gcode file you are trying to print. What speed was it sliced at? Obvious question but what is the speed fact slider in DWC set to? Is there any sign of an M220 command anywhere? If you type M220 into DWC without any other parameters, what does it report?



  • Do you happen to be using mesh grid compensation? Your Z jerk is quite low (only 0.2mm/s) and that could be limiting the speed of XY moves as it has to slowly adjust the height of Z. Try increasing it to 60 (1mm/s) and see if it improves.

    Can you run an M122 and post the results?



  • @phaedrux Good catch (about the mesh compensation and slow Z speed).



  • Hello.
    Thx for looking into this with me.
    Mesh compensation? Again, some studying to do, I guess 🙂

    as requested:

    M122
    === Diagnostics ===
    Used output buffers: 3 of 32 (6 max)
    === Platform ===
    RepRapFirmware for Duet 2 WiFi/Ethernet version 1.21 running on Duet WiFi 1.02 or later
    Board ID: 08DGM-956GU-DJMSN-6J9F8-3S06S-KAQZG
    Static ram used: 16152
    Dynamic ram used: 100584
    Recycled dynamic ram: 2048
    Stack ram used: 1224 current, 6464 maximum
    Never used ram: 5824
    Last reset 01:18:40 ago, cause: reset button or watchdog
    Last software reset at 2018-07-28 00:05, reason: User, spinning module GCodes, available RAM 5672 bytes (slot 2)
    Software reset code 0x0003 HFSR 0x00000000, CFSR 0x00000000, ICSR 0x0041f000, BFAR 0xe000ed38, SP 0xffffffff
    Error status: 0
    Free file entries: 9
    SD card 0 detected, interface speed: 20.0MBytes/sec
    SD card longest block write time: 0.0ms
    MCU temperature: min 40.0, current 45.5, max 45.8
    Supply voltage: min 12.0, current 12.5, max 12.8, under voltage events: 0, over voltage events: 0
    Driver 0: ok, SG min/max 0/616
    Driver 1: ok, SG min/max 0/487
    Driver 2: standstill, SG min/max not available
    Driver 3: ok, SG min/max not available
    Driver 4: standstill, SG min/max not available
    Date/time: 1970-01-01 00:00:00
    Slowest main loop (seconds): 0.042753; fastest: 0.000046
    === Move ===
    MaxReps: 3, StepErrors: 0, LaErrors: 0, FreeDm: 174, MinFreeDm 150, MaxWait: 436051ms, Underruns: 0, 0
    Scheduled moves: 33946, completed moves: 33916
    Bed compensation in use: none
    Bed probe heights: 0.000 0.000 0.000 0.000 0.000
    === Heat ===
    Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
    Heater 0 is on, I-accum = 0.0
    Heater 1 is on, I-accum = 0.6
    === GCodes ===
    Segments left: 1
    Stack records: 1 allocated, 0 in use
    Movement lock held by null
    http is idle in state(s) 0
    telnet is idle in state(s) 0
    file is doing "G0 X89.372 Y114.372" in state(s) 0
    serial is idle in state(s) 0
    aux is idle in state(s) 0
    daemon is idle in state(s) 0
    queue is idle in state(s) 0
    autopause is idle in state(s) 0
    Code queue is empty.
    === Network ===
    Responder states: HTTP(1) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
    HTTP sessions: 1 of 8

    • WiFi -
      Network state is running
      WiFi module is connected to access point
      Failed messages: pending 0, notready 0, noresp 0
      WiFi firmware version 1.21RC4(08b3)
      WiFi MAC address 60:01:94:73:5b:e0
      WiFi Vcc 3.34, reset reason Turned on by main processor
      WiFi flash size 4194304, free heap 15976
      WiFi IP address 192.168.0.175
      WiFi signal strength -62dBm, reconnections 0, sleep mode modem
      Socket states: 2 0 0 0 0 0 0 0
      === Expansion ===


  • I guess I'm not running any grid compensation as I do not have a bed-level-sensor (yet)

    Might be something with my slicer ... (Slic3r Prusa Edition). The probleem seems less when slicing with cura... But that would very weird.



  • @phaedrux said in Very slow printing Duet Wifi on Am8:

    Z jerk is quite low (only 0.2mm/s)

    Can you explain to me where you read this value?
    Do you mean Acceleration? So "M201 Z200"? Changing this to a higher value?

    Or is it about M566?

    Thx!



  • @ludodg said in Very slow printing Duet Wifi on Am8:
    ................

    Might be something with my slicer ... (Slic3r Prusa Edition). The probleem seems less when slicing with cura... But that would very weird.

    Not really. There are all sorts of speed settings in each slicer and each one will only do what you tell it to. Did you check to see if moves via the web console are at the correct speed? If so, then the problem is likely to be the speeds that were used to slice the model. In Slic3r, look in the "Print Settings" tab, then under "Speed". What are the various speeds set too?



  • @ludodg said in Very slow printing Duet Wifi on Am8:

    @phaedrux said in Very slow printing Duet Wifi on Am8:

    Z jerk is quite low (only 0.2mm/s)

    Can you explain to me where you read this value?
    Do you mean Acceleration? So "M201 Z200"? Changing this to a higher value?

    Or is it about M566?

    Thx!

    He means instantaneous speed change. But as you aren't using any form of flatness compensation, the Z axis won't be moving so don't worry about - that's not the reason for your problem.



  • You could post a gcode file that has been sliced with Slic3r and we could see all of the settings slic3r has used since it saves a copy of all it's settings at the end of every file.



  • @deckingman
    Indeed, moving via de webconsole seems to function ok. Homing is happening at normal speed.

    Print Speed settings:
    I'll check those, ... but it now uses the standard settings that came with the latest firm- and software :s

    It has to be SlicerPE as the AM8 now prints Ok when using Cura for slicing.



  • @ludodg standard settings for which firmware and software?


Locked
 

Looks like your connection to Duet3D was lost, please wait while we try to reconnect.