Duet ethernet running latest firmware motors not moving at all



  • 12.1v apparently and no over voltage/ undervoltage events. Doesn't like me very much 😒

    I'm fairly certain the psu isn'n't the problem because I just tried a known good 500w atx psu.

    Warning: motor phase A may be disconnected reported by driver(s) 0
    Warning: motor phase B may be disconnected reported by driver(s) 0
    02/12/2019, 17:21:52 	M122
    === Diagnostics ===
    RepRapFirmware for Duet 2 WiFi/Ethernet version 2.04 running on Duet Ethernet 1.02 or later
    Board ID: 08DGM-917DA-G4MS4-6J9D0-3S86J-K9Y7A
    Used output buffers: 3 of 24 (13 max)
    === RTOS ===
    Static ram: 25680
    Dynamic ram: 92372 of which 0 recycled
    Exception stack ram used: 388
    Never used ram: 12632
    Tasks: NETWORK(ready,676) HEAT(blocked,1232) MAIN(running,3808) IDLE(ready,200)
    Owned mutexes:
    === Platform ===
    Last reset 00:02:18 ago, cause: power up
    Last software reset at 2019-12-01 21:56, reason: User, spinning module GCodes, available RAM 12752 bytes (slot 0)
    Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
    Error status: 0
    Free file entries: 9
    SD card 0 detected, interface speed: 20.0MBytes/sec
    SD card longest block write time: 0.0ms, max retries 0
    MCU temperature: min 22.6, current 22.9, max 23.2
    Supply voltage: min 12.1, current 12.1, max 12.2, under voltage events: 0, over voltage events: 0, power good: yes
    Driver 0: open-load-A open-load-B, SG min/max not available
    Driver 1: standstill, SG min/max not available
    Driver 2: standstill, SG min/max not available
    Driver 3: standstill, SG min/max not available
    Driver 4: standstill, SG min/max not available
    Date/time: 2019-12-02 17:21:51
    Cache data hit count 340424367
    Slowest loop: 1.09ms; fastest: 0.07ms
    I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
    === Move ===
    Hiccups: 0, FreeDm: 159, MinFreeDm: 159, MaxWait: 0ms
    Bed compensation in use: none, comp offset 0.000
    === DDARing ===
    Scheduled moves: 9, completed moves: 8, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
    === Heat ===
    Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
    === GCodes ===
    Segments left: 0
    Stack records: 1 allocated, 1 in use
    Movement lock held by http
    http is idle in state(s) 1 8
    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 ===
    Slowest loop: 2.72ms; fastest: 0.05ms
    Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
    HTTP sessions: 1 of 8
    Interface state 5, link 100Mbps full duplex
    

  • administrators

    It could mean that your stepper motors are low current high resistance types that need more than 12V to achieve the current you have set (1.2A). What is the specification of the stepper motors you are using? Or, if you don't have the motor specifications, the resistance of each phase?



  • 6.6 ohms and 6.5ohms 1.8 degrees motor

    I dont have the specs because they're came with the prusa MK2 printer.

    The 1.2A is just a random number. It was oringinally 800mA when it was running on the duet wifi.
    this didn't work on the duet ethernet so I increased it to 1.2A.

    However I am confused it definately was working with the duet wifi because that's how I printed a base mount plate for the duet wifi. It was also working on the original board which is 12v.



  • @ageis said in Duet ethernet running latest firmware motors not moving at all:

    Warning: motor phase A may be disconnected reported by driver(s) 0
    Warning: motor phase B may be disconnected reported by driver(s) 0

    that means both phases are not connected to the stepper drivers.

    do you get this on all of the drivers?



  • I still suspect a bad connection at the plug.



  • @Veti
    I do when I home all axis

    I did try another motor from a different printer and it still didn't move



  • @ageis said in Duet ethernet running latest firmware motors not moving at all:

    I do when I home all axis

    even on the extruder driver?



  • @Veti
    I didn't try.
    I don't have any filament loaded. Is there a way I turn off the temperature limit?





  • yes even on the extruder

    Warning: motor phase A may be disconnected reported by driver(s) 3
    Warning: motor phase B may be disconnected reported by driver(s) 3
    

    Is it that likely all of the drivers are dead?

    Is there a common component that controls all the drivers?



  • JUst tried remapping x axis to e1 motor driver for the hell of it and I get the same error.

    So I get this warning for all 4 stepper drivers



  • It is incredibly unlikely that all the drivers are alive enough to respond to SPI commands that report disconnected coils, and dead at the coil driver.

    It is time to cut those connectors off and properly crimp on the connectors supplied with the Duet.



  • So I have desoldered one of the connectors off the original board then soldered a fly lead to it.
    The connector on the end I plug into the board is the standard white jst ones you get on motor/ lipo from china.

    I connected it to my bench supply with 24v running through it. IT still the same.
    I was able to use my multimeter to prove there is a continuous loop from the driver to motor and back again on both windings.

    So I can't see why it's not working



  • Have you checked the 7.5A fuse? It's the one closest to the Z stepper. Remove, visually inspect or use a meter to check continuity, and reseat if okay. This provides protection for the steppers and heaters, so check if those aren't working either.

    Ian



  • yes the fuse fine.. The very first thing I checked.



  • @ageis said in Duet ethernet running latest firmware motors not moving at all:

    G31 P500 X230 Y9 Z2.5 ; set Z probe trigger value, offset and trigger height

    your x offset is bigger than the probing area. it cant be 23cm away. i dont know what this would do.

    M92 X80.00 Y80.00 Z4000.00 E420.00 ; set steps per mm

    your z steps seem way off. it should be 400.

    please check if there is continuity between the trinamic chip output and the pins.
    https://www.trinamic.com/fileadmin/assets/Products/ICs_Documents/TMC2660_datasheet.pdf
    using OA1, OA2 and OB1, OB2 pins.

    also are you sure its a genuine board and not a chinese clone? if its a chinese clone they could have used bad chips.



  • Thats what I mean't by tested from the driver to motor and back again. Definately genuine from ooznest



  • @ageis said in Duet ethernet running latest firmware motors not moving at all:

    M203 X360000.00 Y360000.00 Z10800.00 E72000.00 ; set maximum speeds (mm/min)
    M201 X500.00 Y20.00 Z250.00 E250.00 ; set accelerations (mm/s^2)

    also your y acceleration is way to low and your max speed way to high


  • administrators

    @Veti said in Duet ethernet running latest firmware motors not moving at all:

    @ageis said in Duet ethernet running latest firmware motors not moving at all:

    M203 X360000.00 Y360000.00 Z10800.00 E72000.00 ; set maximum speeds (mm/min)
    M201 X500.00 Y20.00 Z250.00 E250.00 ; set accelerations (mm/s^2)

    also your y acceleration is way to low and your max speed way to high

    Low acceleration is OK, but the unreasonably high speeds in M203 could be the problem. Try reducing them from 360000 to 6000.


Log in to reply