Issues with motors..... Don't move

Dougal1957

@whosrdaddy Not only that but it is in the E1 position as well

peirof

ok,

thanks i check this.... but, none of 4 motors works (3 axis 1 extruder)

Dougal1957

but they won't move unless the printer is homed which can't happen unless the motors are connected to the correct places

peirof

@dougal1957 Doing test... i have chaged one axis motor, from his shocket to extruder shocket, for check if was a motor issue...

but no, no axis movement, no extruder movement

peirof

@dougal1957 i haved reconected the motors to this shockets in Duet, and home manual (move printer until endstops are engaged).... and NO moves

dc42

To check motors individually before you have homed them, them send G91 followed by e.g. G1 S2 X10 which should move the X motor 10mm in the positive direction. Replace X10 by X-10, Y10, Y-10 etc. to test the other direction and other motors.

Common reasons why motors won't move:

Motor current is set to zero. Send M906 without parameters and check that the reported motor currents are correct. Also send M913 and check all the currents are at 100%.
VIN is not present or the voltage is too low. Send M122 and check the reported VIN voltage. It needs to be at least 10V. If it is, try moving a motor (see earlier), and if the motor doesn't move run M122 again and check for under-voltage events in the report.
If it's a revision 1.04 Duet, the 7.5A fuse may have blown, for example because due to a short-circuited heater.

A common reason for VIN being too low is that the screws in the VIN terminal block are no longer tight., so VIN at the Duet drops when you try to move a motor or turn on a heater.

peirof

@dc42

I have do the test.... with next results

TEST A

 *PROCEDURE:*

  "To check motors individually before you have homed them, them send G91 followed by e.g. G1 S2 X10 which should move the X motor 10mm in the positive direction. Replace X10 by X-10, Y10, Y-10 etc. to test the other direction and other motors"

RESULTS:

 Dont move

TEST B

PROCEDURE:

Motor current is set to zero. Send M906 without parameters and check that the reported motor currents are correct. Also send M913 and check all the currents are at 100%.

RESULTS:

M906

Motor current (mA) - X:1200, Y:1200, Z:1200, E:800:800, idle factor 40%

M913

Motor current % of normal - X:100, Y:100, Z:100, E:100:100

TEST C

PROCEDURE:

VIN is not present or the voltage is too low. Send M122 and check the reported VIN voltage. It needs to be at least 10V. If it is, try moving a motor (see earlier), and if the motor doesn't move run M122 again and check for under-voltage events in the report

RESULT

Supply voltage: min 24.5, current 24.7, max 24.9, under voltage events: 0, over voltage events: 0, power good: yes

TEST D

PROCEDURE:

If it's a revision 1.04 Duet, the 7.5A fuse may have blown, for example because due to a short-circuited heater.

RESIULT

I have changed fuse, 7,5A. And the same.

All works, minus stepper motors

I have checked screws in Vin terminal.... are ok

peirof

For tests i have do....

All, minus motors, works....

peirof

If i conect a multimeter, to axis sockect, PIN X and Y (i dont know what pins)...... and command a move order to printer, that involves that axis, i have to see Voltage in multimeter? What range?1.0 A, aprox?

dc42

You can connect a multimeter set to a voltage range to pairs of stepper driver output pins, but be very careful not to short them together!

When you command a motor to move for the first time after powering up the Duet, does the axis become stiff and harder to turn by hand?

Please try commanding some motors to move, then send M122 once and post the report here.

peirof

@dc42

i send by console G91 and after G1 S2 X10.... and axis stiff, the same with Y and Z

after send a M122, the results

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.02(RTOS) running on Duet WiFi 1.02 or later
Board ID: 08DGM-956GU-DJMSN-6J1DJ-3S86S-K9RBH
Used output buffers: 1 of 20 (15 max)
=== RTOS ===
Static ram: 25524
Dynamic ram: 98632 of which 0 recycled
Exception stack ram used: 328
Never used ram: 6588
Tasks: NETWORK(ready,680) HEAT(blocked,1232) MAIN(running,3860) IDLE(ready,200)
Owned mutexes:
=== Platform ===
Last reset 00:07:29 ago, cause: power up
Last software reset at 2019-01-06 18:27, reason: User, spinning module GCodes, available RAM 6452 bytes (slot 2)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 36.4, current 38.5, max 38.8
Supply voltage: min 24.5, current 24.7, max 24.9, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: ok, SG min/max not available
Driver 1: ok, SG min/max not available
Driver 2: ok, SG min/max not available
Driver 3: ok, SG min/max not available
Driver 4: ok, SG min/max not available
Date/time: 2019-01-07 16:26:37
Cache data hit count 1683481520
Slowest loop: 2.26ms; fastest: 0.08ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0
=== Move ===
Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm: 239, MaxWait: 297717ms, Underruns: 0, 0
Scheduled moves: 3, completed moves: 3
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
=== 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
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 168.39ms; fastest: 0.08ms
Responder states: HTTP(0) 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.21
WiFi MAC address 5c:cf:7f:76:73:23
WiFi Vcc 3.29, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 15528
WiFi IP address 192.168.1.200
WiFi signal strength -44dBm, reconnections 0, sleep mode modem
Socket states: 0 0 0 0 0 0 0 0

peirof

What can i do?

dc42

Please post your config.g file.

sigxcpu

@peirof M119 ?

peirof

Hi,

Config.g

; Configuration file for Duet WiFi (firmware version 1.17)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool on Fri Aug 04 2017 00:02:04 GMT-0400 (Eastern Daylight Time)

; General preferences
M111 S0 ; Debugging off
G21 ; Work in millimetres
G90 ; Send absolute coordinates...
M83 ; ...but relative extruder moves
M555 P1 ; Set firmware compatibility to look like RepRapFirmare
M665 R157 L397.1073 B175 H500.3 ; Set delta radius, diagonal rod length, printable radius and homed height
M666 X0 Y0 Z0 ; Put your endstop adjustments here, or let auto calibration find them
M208 Z0 S1 ; Set minimum Z

; Endstops & Monitoring aa
M574 X2 Y2 Z2 S1 ; Define active high microswitches
M557 R110 S25 ; Define mesh grid
M911 S12.0:19.5:22.0 ; Auto-pause at 19.5V, then either stop at 12V or auto-resume at 22V

;DESACTIVAR EL PIN DEL HEATER7, EN EL SOCKET DE EXPANSION

;Zprobe Precision Piezo

; M558 P0
M558 P8 I1 R0.4 F500 X0 Y0 Z0; M558 P8 I1 R1 F300 X0 Y0 Z0 H2 / M558 P5 I1 R0.4 F300 H5 X0 Y0 Z0 T2400
G31 X0 Y0 Z-0.1 P400 ;(X, Y, Z offsets, debounce interval)

; Drives
M569 P0 S1 ; Drive 0 goes forwards
M569 P1 S1 ; Drive 1 goes forwards
M569 P2 S1 ; Drive 2 goes forwards
M569 P3 S0 ; Drive 3 goes reverse
M350 E16 I1 ; Configure microstepping with interpolation
M350 X32 Y32 Z32 I1 ; Configure microstepping with interpolation
M92 X160 Y160 Z160 E415 ; Set steps per mm
M566 X1200 Y1200 Z1200 E1200 ; Jerk Set maximum instantaneous speed changes (mm/min)
M203 X18000 Y18000 Z1800 E1200 ; Set maximum speeds (mm/min)
M201 X1000 Y1000 Z1000 E1000 ; Set accelerations (mm/s^2)
M906 X1200 Y1200 Z1200 E800 I40 ; Set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout

; Pressure in advance

M572 D0 S0.08 ; Setup for pressure in advance

; Heaters
M143 S285 ; Set maximum heater temperature to 285C
M301 H0 S1.00 P10 I0.1 D200 T0.4 W180 B30 ; Use PID on bed heater (may require further tuning

M305 P0 T100000 B4138 C0 R4700 ; Set thermistor + ADC parameters for heater 0
M305 P1 T100000 B4138 C0 R4700 ; Set thermistor + ADC parameters for heater 1

; Tools
M563 P0 S"Prometheus" D0 H1 F1 ;M563 P0 D0 H1 ; tool(P)0 Nombre(S) Motor de extrusion(D)0 Calentador(H)1 y Ventilador(F)1
G10 P0 X0 Y0 Z0 ; Set tool 0 axis offsets
G10 P0 R0 S0 ; Set initial tool 0 active and standby temperatures to 0C

; Network
M550 PTLM Duet 2 ; Set machine name
M587 S"TERRAZAExtender2.4GHz" P"a1b2c3d4" I192.168.1.200
M552 S1 ; Enable network
M586 P0 S1 ; Enable HTTP
M586 P1 S0 ; Disable FTP
M586 P2 S0 ; Disable Telnet

; Fans
M106 P0 H-1 ; GCODE FAN
M106 P1 H-1 ; GCODE FAN
M106 P2 S1 I0 F500 H1 T205 ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on a 70C

; Custom settings are not configured

; Miscellaneous
M501 ; Load saved parameters from non-volatile memory

M119

Endstops - X: not stopped, Y: not stopped, Z: not stopped, Z probe: not stopped

peirof

Hi,

An idea it's make a Soft reset... How would the procedure?

dc42

@peirof said in Issues with motors..... Don't move:

Hi,

An idea it's make a Soft reset... How would the procedure?

Sending M999 causes a software reset.

peirof

@dc42 Ok... Later try... Exist, in Duet, a Hard reset?

Dougal1957

@peirof said in Issues with motors..... Don't move:

M558 P8 I1 R0.4 F500 X0 Y0 Z0; M558 P8 I1 R1 F300 X0 Y0 Z0 H2 / M558 P5 I1 R0.4 F300 H5 X0 Y0 Z0 T2400

I could be way of the mark here but in this line
M558 P8 I1 R0.4 F500 X0 Y0 Z0; M558 P8 I1 R1 F300 X0 Y0 Z0 H2 / M558 P5 I1 R0.4 F300 H5 X0 Y0 Z0 T2400

is the semicolon directly after the Z0 ok or does it need a space in there?

Doug

peirof

@dougal1957

i am not sure, but think this is not the problem, the printer has been working with these config.g, months....