Help, stepper motor/endstops problem
-
Do your axis actually show as homed in the DWC or on the PanelDue?
Can you post your homing files?
-
@Phaedrux Head position in DWI shows as n/a for all three axes, endstops showing no for triggered in machine properties, but do change to yes when i manually trip the switches.
Extruder shows as endstop triggered, but there isn't one installed. could this be causing a confllct?
homedelta.g
; called to home all towers on a delta printer
;
; generated by RepRapFirmware Configuration Tool v2 on Fri Apr 19 2019 22:05:21 GMT+0100 (British Summer Time)
G91 ; relative positioning;*** Slow homing has been configured. Change F180 to F1800 below when your configuration is working
G1 S1 X130 Y130 Z130 F180 ; move all towers to the high end stopping at the endstops (first pass)
G1 X-5 Y-5 Z-5 F1800 S2 ; go down a few mm
;*** Slow homing has been configured. Change F180 to F360 below when your configuration is working
G1 S1 X10 Y10 Z10 F180 ; move all towers up once more (second pass)
G1 Z-5 F6000 ; move down a few mm so that the nozzle can be centred
G90 ; absolute positioning
G1 X0 Y0 F6000 ; move X+Y to the centre -
One other point that may be relevant.
I am waiting for a better psu to come and am only putting a 5A supply onto the machine, but I've only ran one heater at a time, and 95%+ of my attempted axis movements have been with heaters off.
could there be insufficient power coming form the psu?
-
@dugee said in Help, stepper motor/endstops problem:
Extruder shows as endstop triggered, but there isn't one installed. could this be causing a confllct?
No that's normal.
Power should be enough to move the motors.
Can you try sending G92 X0 Y0 Z0 when the towers are at the top. This will set their position and set the axis as homed. You should then be able to move the motors.
Try sending a G1 X10 S2 to move the individual motor.
-
nothing, motors not responding at all.
The DWI thought the head had been homed, and the x, y and z head position changes in DWI when I use commands to move the head, but the physical head is not moving.
-
sorry, should have included:
10:37:30 PMG1 Y10 S2
Error: G0/G1: attempt to move individual motors of a delta machine to absolute positions -
You may need to send G91 first to put it in relative movement mode first.
-
Test the motors individually as described at https://duet3d.dozuki.com/Wiki/ConfiguringRepRapFirmwareDeltaPrinter#Section_Testing_the_motors_and_endstops_individually.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@dc42 Just tried that, no movement or response, the head position in the machine status box changes but there is no actual physical movement.
-
@dugee, please try moving the motors again (as described in that link), then run M122 once only and post the report here.
-
as requested
9:28:12 AMM122
=== Diagnostics ===
RepRapFirmware for Duet 2 Maestro version 2.02(RTOS) running on Duet Maestro 1.0
Board ID: 08DAM-9F9DA-MWNS8-6J1F6-3SS6Q-KP1UW
Used output buffers: 1 of 20 (13 max)
=== RTOS ===
Static ram: 19476
Dynamic ram: 92932 of which 0 recycled
Exception stack ram used: 152
Never used ram: 18512
Tasks: NETWORK(ready,672) HEAT(blocked,1356) MAIN(running,3940) IDLE(ready,204)
Owned mutexes:
=== Platform ===
Last reset 00:01:55 ago, cause: power up
Last software reset at 2019-04-21 22:35, reason: User, spinning module GCodes, available RAM 18440 bytes (slot 2)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0400f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 15.0MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 16.7, current 23.4, max 23.5
Supply voltage: min 0.0, current 12.3, max 12.4, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 1495
Driver 1: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 1495
Driver 2: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 1495
Driver 3: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 1494
Driver 4: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 1494
Driver 5: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 1494
Driver 6: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 1494
Date/time: 2019-04-23 09:28:09
Slowest loop: 1.45ms; fastest: 0.06ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0
=== Move ===
Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm: 240, 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
=== Heat ===
Bed heaters = 0, chamberHeaters = -1 -1
=== GCodes ===
Segments left: 0
Stack records: 1 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
lcd is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 5.00ms; fastest: 0.02ms
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
9:28:02 AMG1 S2 X-10
Error: G0/G1: attempt to move individual motors of a delta machine to absolute positions
9:27:49 AMG92 X0 Y0 Z0
9:27:29 AMMessage Log cleared! -
@dc42 just noticed I hadn't entered G91 first. Restarted the board and performed tests again. No movement on the motors still
0:42:48 AMM122
=== Diagnostics ===
RepRapFirmware for Duet 2 Maestro version 2.02(RTOS) running on Duet Maestro 1.0
Board ID: 08DAM-9F9DA-MWNS8-6J1F6-3SS6Q-KP1UW
Used output buffers: 3 of 20 (13 max)
=== RTOS ===
Static ram: 19476
Dynamic ram: 92932 of which 0 recycled
Exception stack ram used: 200
Never used ram: 18464
Tasks: NETWORK(ready,672) HEAT(blocked,1356) MAIN(running,3940) IDLE(ready,204)
Owned mutexes:
=== Platform ===
Last reset 00:01:13 ago, cause: software
Last software reset at 2019-04-23 10:41, reason: User, spinning module GCodes, available RAM 18464 bytes (slot 3)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x04427000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 15.0MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 30.8, current 31.1, max 31.3
Supply voltage: min 0.0, current 12.3, max 12.4, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 948
Driver 1: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 948
Driver 2: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 947
Driver 3: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 947
Driver 4: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 947
Driver 5: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 947
Driver 6: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 947
Date/time: 2019-04-23 10:42:48
Slowest loop: 1.46ms; fastest: 0.06ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0
=== Move ===
Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm: 239, MaxWait: 54757ms, 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, chamberHeaters = -1 -1
=== GCodes ===
Segments left: 0
Stack records: 1 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
lcd is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 5.01ms; fastest: 0.03ms
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
10:42:43 AMG1 S2 Z-10
10:42:38 AMG1 S2 Y-10
10:42:31 AMG1 S2 X-10
10:42:14 AMG91
10:41:57 AMMessage Log cleared! -
@dugee said in Help, stepper motor/endstops problem:
Supply voltage: min 0.0, current 12.3, max 12.4, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 948
Driver 1: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 948
Driver 2: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 947
Driver 3: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 947
Driver 4: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 947
Driver 5: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 947
Driver 6: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 947This indicates a problem with the UART communication to the TMC2224 drivers. Assuming you don't have anything connected to the stepper driver expansion connector, I suggest you ask for your Duet to be replaced under warranty.
-
ok thanks @dc42 I'll fill in the form now, as I purchased direct.
