Strange Stepper Behavior
-
1. Please check the voltage at the VIN terminal block. If you have a multimeter, use is to measure that voltage. Also you can run M122 and see what minimum, current and ,maximum supply voltages are recorded.
2. Please test the stepper drivers individually as described at https://duet3d.com/wiki/Configuring_RepRapFirmware_for_a_Delta_printer#Testing_the_motors_individually. It's probably best to do it as in your second video, using the same motor each time to eliminate possible issues with the motor and particularly the cable.
3. Note: When the motors are connected to the Duet, do not move the carriages rapidly by hand, because this can exceed the voltage rating of the stepper drivers.
-
1. Supply voltage: min 12.3, current 12.7, max 13.3, under voltage events: 0, over voltage events: 0
Checking with a multimeter yielded about 12.75v
2. Tested all the stepper drivers by putting printer in relative mode and sending move commands to individual steppers, appeared to work normally. Except my X input rotates counter clockwise while Y and Z input rotates clockwise
-
Did some additional troubleshooting as outlined in another video.
-
I suspect the X stepper driver is faulty, but please do the following additional tests:
1. Use G91 followed by G1 S2 to test carriage movement in both directions, i.e. try negative X, Y and Z values as well as positive ones.
2. After attempting homing, run M122 and check the minimum supply voltage reported and the number of under-voltage events.
-
1. Tested this, Y and Z move respective to what would be expected, X moves in the opposite direction while making the grinding noise.
2. Attempted homing ran M122 (Did this twice as the first time I noticed a wire had come uncrimped from my Y motor, which I fixed before recording the video, first time min was 11.7, I incorrectly quoted 11.4 in my video)
https://www.youtube.com/watch?v=PHsYdo6dCcw
[c] === Diagnostics ===
Used output buffers: 3 of 32 (6 max)
=== Platform ===
RepRapFirmware for Duet WiFi version 1.20 running on Duet WiFi 1.0
Board ID: 08DGM-95BNL-MGPSJ-6JTDJ-3SS6N-12XVZ
Static ram used: 15448
Dynamic ram used: 99168
Recycled dynamic ram: 72
Stack ram used: 1392 current, 4504 maximum
Never used ram: 11880
Last reset 00:03:31 ago, cause: power up
Last software reset at 2018-01-27 00:51, reason: User, spinning module GCodes, available RAM 11896 bytes (slot 1)
Software reset code 0x0003 HFSR 0x00000000, CFSR 0x00000000, ICSR 0x0441f000, BFAR 0xe000ed38, SP 0xffffffff
Error status: 0
Free file entries: 9
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms
MCU temperature: min 21.5, current 26.9, max 27.7
Supply voltage: min 12.4, current 12.8, max 13.3, under voltage events: 0, over voltage events: 0
Driver 0: ok, SG min/max 0/212
Driver 1: ok, SG min/max 9/249
Driver 2: standstill, SG min/max 15/227
Driver 3: standstill, SG min/max not available
Driver 4: standstill, SG min/max not available
Date/time: 2018-01-28 12:00:17
Cache data hit count 811346353
Slowest main loop (seconds): 0.014183; fastest: 0.000042
=== Move ===
MaxReps: 3, StepErrors: 0, FreeDm: 237, MinFreeDm 237, MaxWait: 17405932ms, Underruns: 0, 0
Scheduled moves: 7, completed moves: 6
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: 1 allocated, 1 in use
Movement lock held by http
http is idle in state(s) 1 4
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 state is running
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.20
WiFi MAC address 2c:3a:e8:0b:02:39
WiFi Vcc 3.39, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 15728
WiFi IP address 192.168.1.100
WiFi signal strength -58dBm, reconnections 0, sleep mode modem
HTTP sessions: 1 of 8
Socket states: 2 0 0 0 0 0 0 0
Responder states: HTTP(1) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) [/c] -
I was expecting your X carriage to move down whichever way you commanded it if the X driver was faulty, but it didn't. So please try swapping the X and Y motor connections over where they plug into the Duet, and putting this command in config.g immediately after your M569 commands to swap them back in firmware:
M584 X1 Y0 Z2 E3:4
Then see whether the problem is still with the X carriage or has moved to the Y carriage.
-
After following your instructions the problem has indeed moved to the Y carriage.
-
Thanks, that confirms a likely issue with the X driver. Please request a replacement Duet under warranty.
-
That's what I was afraid of, thank you for your assistance in troubleshooting dc42, do I need to go through your guys warranty form or should I contact Spool3d where I purchased it?
-
Contact Spool3d.
-
As an addendum, the issues I was having with my z axis during homing were due to the endstop. As the endstop I have was designed to work with 5v (I changed the 1k resistor down to 330) the IR LED wasn't quite as bright running off 3.3v. there was some plastic flashing on the plastic cover that was obstructing the IR receiver, cleaning up the flashing with a hobby knife has resolved the issues and I'm able to home with the new board with properly working drivers.
Thanks again for all your help DC42
