Underruns ? shifting layers

  • Hello running the latest build on a corexy
    and change my motors to 0.9 motors
    now i some times get random shifting layers
    i know usually this is the printer not the software
    but i just want to ask what is "Underruns" ? can it be related to the shifting ?
    the motor is rated to 2A and i use ti have it att 80% now im trying 1.9A to see if it gets stronger

    "MaxReps: 6, StepErrors: 0, FreeDm: 240, MinFreeDm 120, MaxWait: 6888142ms, Underruns: 178, 0" ?

    === Diagnostics ===
    Used output buffers: 1 of 32 (10 max)
    === Platform ===
    RepRapFirmware for Duet WiFi version 1.19 running on Duet WiFi 1.0
    Board ID: 08DAM-999TL-MQ4S8-6J9F6-3SJ6J-T4B3W
    Static ram used: 21176
    Dynamic ram used: 96472
    Recycled dynamic ram: 1136
    Stack ram used: 4008 current, 9112 maximum
    Never used ram: 3176
    Last reset 07:33:35 ago, cause: software
    Last software reset reason: User, spinning module GCodes, available RAM 3224 bytes (slot 0)
    Software reset code 0x0003, HFSR 0x00000000, CFSR 0x00000000, ICSR 0x00400000, BFAR 0xe000ed38, SP 0xffffffff
    Error status: 0
    Free file entries: 10
    SD card 0 detected, interface speed: 20.0MBytes/sec
    SD card longest block write time: 235.4ms
    MCU temperature: min 30.0, current 35.9, max 37.5
    Supply voltage: min 20.9, current 23.4, max 24.5, under voltage events: 0, over voltage events: 0
    Driver 0: stalled standstill
    Driver 1: stalled standstill
    Driver 2: stalled standstill
    Driver 3: standstill
    Driver 4: standstill
    Date/time: 2017-08-22 23:55:48
    Slowest main loop (seconds): 0.236328; fastest: 0.000000
    === Move ===
    MaxReps: 6, StepErrors: 0, FreeDm: 240, MinFreeDm 120, MaxWait: 6888142ms, Underruns: 178, 0
    Scheduled moves: 8, completed moves: 8
    Bed compensation in use: 5 point
    Bed probe heights: -0.134 -0.638 0.238 0.637 -0.084
    === Heat ===
    Bed heater = 0, chamber heater = -1
    Heater 0 is on, I-accum = 0.3
    === GCodes ===
    Segments left: 0
    Stack records: 2 allocated, 0 in use
    Movement lock held by null
    http is ready with "M122" in state(s) 0
    telnet is idle in state(s) 0
    file is idle 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 state is running
    WiFi module is connected to access point
    WiFi firmware version 1.19
    WiFi MAC address a0:20:a6:18:39:47
    WiFi Vcc 3.12, reset reason Turned on by main processor
    WiFi flash size 4194304, free heap 38792
    WiFi IP address
    WiFi signal strength -59dBm
    HTTP sessions: 2 of 8
    Socket states: 0 0 0 0 0 0 0 0
    Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)


  • administrators

    An underrun occurs when data wasn't supplied fast enough to keep the printer running at maximum speed and it had to pause to wait for more data to be supplied. There are two typical causes. One is printing over USB from a PC. The other is the slicer producing sequences of lots of tiny segments. Simplify3D used to do this quite often. This has supposedly been fixed, however S3D still generates tiny segments sometimes.

    Underruns do not cause layer shifts.

  • ok thanks for a fast answer
    i use s3d

    i will try to lower my movement speed and see if that works better

Log in to reply