Duet ethernet running latest firmware motors not moving at all
-
Hi
I bought a new duet ethernet a few months ago to replace my BER duet wifi.
Only just got round to installing it.My problem is my duet doesn't seem to move any of the motors at all. I have upgraded to the latest firmware.
Board: Duet Ethernet 1.02 or later Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 2.04 (2019-11-01b1)
I have tried both using the offical configurator and an old config.g which AFAIK was working,
Everytime I try homing/ exruding, the web interface says winding A is disconnected then shortly winding B as well.However the connectors are seated properly and I tried the motor with the original prusa I3 mk2s board and they move.
Is there anyone who has a working configuration for a Prusa MK2S I can copy?
; Configuration file for Duet WiFi (firmware version 2.03) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v2.1.3 on Sun Dec 01 2019 00:35:50 GMT+0000 (Greenwich Mean Time) ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"Prusa I3" ; set printer name ; Network M552 P0.0.0.0 S1 ; enable network and acquire dynamic address via DHCP M586 P0 S1 ; enable HTTP M586 P1 S0 ; disable FTP M586 P2 S0 ; disable Telnet ; Drives M569 P0 S1 ; physical drive 0 goes forwards M569 P1 S1 ; physical drive 1 goes forwards M569 P2 S1 ; physical drive 2 goes forwards M569 P3 S1 ; physical drive 3 goes forwards M584 X0 Y1 Z2 E3 ; set drive mapping M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation M92 X80.00 Y80.00 Z4000.00 E420.00 ; set steps per mm M566 X900.00 Y900.00 Z12.00 E120.00 ; set maximum instantaneous speed changes (mm/min) 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) M906 X1200 Y1200 Z1200 E1200 I30 ; set motor currents (mA) and motor idle factor in per cent M84 S30 ; Set idle timeout ; Axis Limits M208 X0 Y0 Z0 S1 ; set axis minima M208 X250 Y210 Z210 S0 ; set axis maxima ; Endstops M574 X1 Y1 S1 ; set active high endstops M574 Z1 S2 ; set endstops controlled by probe ; Z-Probe M558 P1 H5 F120 T6000 ; set Z probe type to unmodulated and the dive height + speeds G31 P500 X230 Y9 Z2.5 ; set Z probe trigger value, offset and trigger height M557 X15:235 Y15:195 S20 ; define mesh grid ; Heaters M305 P0 T100000 B4138 R4700 ; set thermistor + ADC parameters for heater 0 M143 H0 S120 ; set temperature limit for heater 0 to 120C M305 P1 T100000 B4138 R4700 ; set thermistor + ADC parameters for heater 1 M143 H1 S280 ; set temperature limit for heater 1 to 280C ; Fans M106 P0 S0 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 ; Tools M563 P0 D0 H1 F0 ; 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 ; Custom settings are not defined
-
I don't see anything wrong with the config. What are you using for the plug connectors? It sounds like a bad crimp or something isn't making a good connection.
-
As far as I can tell they're definately pushed in as far as it will go and it definately used to work on the duet wifi before I let the magic smoke out of the processor I suspect. I wanted to keep the compatibility with the original prusa board you see.
It's still 0.1 inch compatible so I push it in.
-
When you send M122, what VIN voltage does it report?
-
12.1v apparently and no over voltage/ undervoltage events. Doesn't like me very much
-
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
-
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) 0that 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 axisI 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? -
@ageis said in Duet ethernet running latest firmware motors not moving at all:
Is there a way I turn off the temperature limit?
Yes there is. https://duet3d.dozuki.com/Wiki/Gcode#Section_M302_Allow_cold_extrudes
-
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.