Hard jitteing form stepper motor during heating.



  • I hsd recently bought a new DuetWifi. Installed it in my delta printer. the problem i currently face is that , while heating the heater of extruder i cant move the stepper motors properly, high jittering,vibrations and large noise are produced from the stepper motors. What will be the problem. Could someone please help me. Am pretty new to the duet. I had been using ramp 1.4 earlier.
    Am on the latest firmware.



  • Could you post the output from a M122 command?



  • Maybe inductance from the heater wiring into the stepper wiring? (disclaimer, this is wild guess, I don't actually know wtf I'm talking about)



  • Would also be nice to know which Motors or is it all of them?



  • 21:39:05M122
    === Diagnostics ===
    Used output buffers: 1 of 32 (4 max)
    === Platform ===
    Static ram used: 20320
    Dynamic ram used: 72808
    Recycled dynamic ram: 1080
    Stack ram used: 968 current, 3732 maximum
    Never used ram: 33132
    Last reset 00:00:54 ago, cause: software
    Last software reset code 0x0003, HFSR 0x00000000, CFSR 0x00000000, ICSR 0x00400000, BFAR 0xe000ed38, SP 0xffffffff
    Spinning module during software reset: GCodes, available RAM 33088 bytes (slot 4)
    Error status: 0
    Free file entries: 10
    SD card 0 detected, interface speed: 20.0MBytes/sec
    SD card longest block write time: 0.0ms
    MCU temperature: min 39.8, current 42.2, max 45.5
    Supply voltage: min 11.7, current 11.8, max 11.9, under voltage events: 0, over voltage events: 0
    Driver 0: stalled standstill
    Driver 1: standstill
    Driver 2: stalled standstill
    Driver 3: standstill
    Driver 4: standstill
    Date/time: 2017-04-09 21:39:04
    Slowest main loop (seconds): 0.003094; fastest: 0.000035
    === Move ===
    MaxReps: 0, StepErrors: 0, MaxWait: 0ms, Underruns: 0, 0
    Scheduled moves: 0, completed moves: 0
    Bed compensation in use: none
    Bed probe heights: 0.000 0.000 0.000 0.000 0.000
    Probe change coordinates:
    === Heat ===
    Bed heater = 0, chamber heater = -1
    Heater 1 is on, I-accum = 0.0
    === GCodes ===
    Segments left: 0
    Stack records: 2 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 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
    Code queue is empty.
    === Network ===
    WiFiServer is running
    SPI underruns 0, overruns 0
    === Webserver ===
    HTTP sessions: 1 of 8


  • administrators

    If it only occurs during heating then it may mean that the power supply voltage is dropping too much under load. The M122 diagnostic report will tell you what the power supply voltage is, and also whether there have been any under voltage events.


  • administrators

    Was that M122 report produced before or after you tried moving the motors while heating?



  • The problem is with all the motors.
    Will it be caused due to insufficient power?
    After an error stating heater is faulty ( temp not rising fast). The motors work perfectly.



  • @dc42:

    Was that M122 report produced before or after you tried moving the motors while heating?

    Sorry I couldn't take the M122 during the problem since am scared it would effect the duetwifi if left like that for longer.


  • administrators

    Can you turn on the heaters, then run M122 again?



  • @dc42:

    Can you turn on the heaters, then run M122 again?

    M122
    === Diagnostics ===
    Used output buffers: 1 of 32 (4 max)
    === Platform ===
    Static ram used: 20320
    Dynamic ram used: 72808
    Recycled dynamic ram: 1080
    Stack ram used: 968 current, 3776 maximum
    Never used ram: 33088
    Last reset 00:00:34 ago, cause: software
    Last software reset code 0x0003, HFSR 0x00000000, CFSR 0x00000000, ICSR 0x00400000, BFAR 0xe000ed38, SP 0xffffffff
    Spinning module during software reset: GCodes, available RAM 33132 bytes (slot 3)
    Error status: 0
    Free file entries: 10
    SD card 0 detected, interface speed: 20.0MBytes/sec
    SD card longest block write time: 0.0ms
    MCU temperature: min 41.5, current 44.4, max 47.3
    Supply voltage: min 9.6, current 9.6, max 11.9, 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-04-09 21:55:10
    Slowest main loop (seconds): 0.003092; fastest: 0.000035
    === Move ===
    MaxReps: 3, StepErrors: 0, MaxWait: 1247ms, Underruns: 0, 0
    Scheduled moves: 5, completed moves: 5
    Bed compensation in use: none
    Bed probe heights: 0.000 0.000 0.000 0.000 0.000
    Probe change coordinates:
    === Heat ===
    Bed heater = 0, chamber heater = -1
    Heater 1 is on, I-accum = 0.2
    === GCodes ===
    Segments left: 0
    Stack records: 2 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 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
    Code queue is empty.
    === Network ===
    WiFiServer is running
    SPI underruns 0, overruns 0
    === Webserver ===
    HTTP sessions: 1 of 8



  • M122
    === Diagnostics ===
    Used output buffers: 1 of 32 (9 max)
    === Platform ===
    Static ram used: 20320
    Dynamic ram used: 72808
    Recycled dynamic ram: 1080
    Stack ram used: 968 current, 3776 maximum
    Never used ram: 33088
    Last reset 00:02:45 ago, cause: software
    Last software reset code 0x0003, HFSR 0x00000000, CFSR 0x00000000, ICSR 0x00400000, BFAR 0xe000ed38, SP 0xffffffff
    Spinning module during software reset: GCodes, available RAM 33132 bytes (slot 3)
    Error status: 0
    Free file entries: 10
    SD card 0 detected, interface speed: 20.0MBytes/sec
    SD card longest block write time: 0.0ms
    MCU temperature: min 43.7, current 45.5, max 47.5
    Supply voltage: min 9.9, current 10.0, max 10.1, 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-04-09 21:57:21
    Slowest main loop (seconds): 0.004761; fastest: 0.000092
    === Move ===
    MaxReps: 0, StepErrors: 0, MaxWait: 0ms, Underruns: 0, 0
    Scheduled moves: 5, completed moves: 5
    Bed compensation in use: none
    Bed probe heights: 0.000 0.000 0.000 0.000 0.000
    Probe change coordinates:
    === Heat ===
    Bed heater = 0, chamber heater = -1
    Heater 1 is on, I-accum = 0.5
    === GCodes ===
    Segments left: 0
    Stack records: 2 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 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
    Code queue is empty.
    === Network ===
    WiFiServer is running
    SPI underruns 0, overruns 0
    === Webserver ===
    HTTP sessions: 1 of 8


  • administrators

    Thanks. It's a power problem, as shown by this line:

    Supply voltage: min 9.6, current 9.6, max 11.9, under voltage events: 0, over voltage events: 0

    If the supply voltage drops just 0.1V more than an under voltage event will be triggered and the stepper drivers will be turned off to protect them.

    So I think either your power supply isn't up to the job, or the wires from the PSU to the Duet are too thin, or you have a bad connection e.g. loose terminal block screw.



  • Thanks a lot sir. I will check into it and reply soon.



  • After I changed my wires everything worked perfectly.
    Thanks to everyone. :))


Log in to reply