Duet2 V1.04. Motor not energized but steps seen on oscilloscope
Could I please get a further suggestion for resolving my problem of no motor current on my Duet2?
When you home do the other two towers move and just the X not work?
Thank you T3P3Tony,
No. No movement on any motors.
I have put a motor into each of the motor connectors and none of them is energized.
My 24 volt power supply shows a draw of about 100mA, but none of the motors is energized.
I have checked the ENN pin of the TMC2660 chips, they are at ground. There is 24 volts at the appropriate pins of the TMC2660s, and 3.3 volts at their supply.
@vbiondo please post your homedelta.g
Also when are your endstops showing as being triggered when you look at the machine properties page of settings in Duet Web Control:
If you trigger them does the status change?
My X,Y, and Z endstops show as "No" ( not hit ) unless I short 1&3 of the endstop connector, then they show "Yes."
E0 is opposite, shows as "Yes" unless 1&3 are shorted.
Below is my homedelta.g file. Shouldn't my motors be energized regardless of homedelta?
; called to home all towers on a delta printer
; generated by RepRapFirmware Configuration Tool v2 on Wed May 22 2019 17:26:42 GMT-0700 (Pacific Daylight Time)
G91 ; relative positioning
;*** Slow homing has been configured. Change F180 to F1800 below when your configuration is working
G1 S1 X265 Y265 Z265 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 F2400 ; move down a few mm so that the nozzle can be centred
G90 ; absolute positioning
G1 X0 Y0 F2400 ; move X+Y to the centre
Veti last edited by
how exactly did you determine the phases of your motors?
deckingman last edited by
I don't know much about Delta's but @dc42 said above that the only moves allowed before homing are G1 with an S parameter and only if G91 relative is set. Yet the config file shows G90 (absolute).
@vbiondo that home delta looks ok to me. If it had been blank or something then maybe the motors would not be energised as they had not received a valid command to home. Although thinking about it you say you have seen the step pulses going to the driver so that does not make sense. I wonder if the ENN line is not switching for all the stepper drivers. See if pin 19 on the steppers is going low when movement is commanded.
@deckingman that's why the homedelta.g switches them to relative before homing them.
MoczikGabor last edited by
Does the extruder motor move?
If you can not heat up, use "M302 S1" to allow cold extrusion.
G1 E+100 F500
MoczikGabor last edited by
HW check ideas, since you have an oscilloscope:
Do any signal present on TMC's OA1 OA2 OB1 OB2 pins? (during move)
What can you measure between BRA/BRB and GND? 1. Measure resistance without power, 2. check on scope during move.
Between SRA/SRB and GND?
You verified that the TMC's get 24V and the STEP signals. This is where everything gets interesting... But does them get GND?
Please upgrade your firmware to version 2.02, which will provide better diagnostics.
Please verify that you have continuity from the Duet motor headers right through to your motors. With power off but motors connected, use your multimeter to measure the resistance between the two pins at one end of the X motor connector, by touching the probes on the motor connector spills on the underside of the Duet. It should read a few ohms, the resistance of one motor phase. Then check the resistance between the two pins at the other end of the X motor connector. Likewise you should get a few ohms resistance between. There should be on continuity between any pair of pins on the X motor connector that are not next to each other, or between the two middle pins.
I determined the phases of my motors using an ohmmeter to find the low resistance pairs.
Also, it corresponded to the motor manufacturer's spec sheet.
The ENN pin is always low.
No, the motor doesn't energize or move on either E0 or E1.
I used the commands you described, thank you:
G1 E+100 F500
The only explanation I can think of is that the SPI MOSI pin from the MCU isn't getting to the TMC2660 drivers, so they are not getting programmed. But it must have been working when the Duet was tested. Assuming it's a genuine Duet, I'm happy to approve a warranty replacement if you want to try another one.
I updated the firmware to 2.02, no change.
I purchased my Duet from Matter Hackers, so I believe it should be genuine.
Please direct me as to how to get a warranty replacement.
@vbiondo Matterhackers are one of our US resellers so it will be genuine. Contact their support and reference this thread. They should point you to a warranty return form to capture the details.
Thank you. I have an additional question.
Can I purchase tech support going forward?
I am using this card to develop a delta machine for a manufacturing application and it is worth it for me to pay to get more expedient answers when needed.
I have received the new Duet2 pcb rev 1.04B and still no motor energization when a motor is attached on any axis.
I have checked the motor on another system and it is fine.
The motor voltage supply is set at 20 volts.
I did not change the configuration that the card came with, it says "DuetTest" in the browser interface.
I am supplying 5 volts via the USB cable.
Here is the result of an M122 command:
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.02(RTOS) running on Duet WiFi 1.02 or later
Board ID: 08DGM-917DA-G4MS8-6JKD6-3S46T-9TTZA
Used output buffers: 1 of 20 (11 max)
=== RTOS ===
Static ram: 25524
Dynamic ram: 98908 of which 0 recycled
Exception stack ram used: 352
Never used ram: 6288
Tasks: NETWORK(ready,648) HEAT(blocked,872) MAIN(running,3776) IDLE(ready,200)
=== Platform ===
Last reset 00:15:38 ago, cause: software
Last software reset at 2019-05-30 16:21, reason: User, spinning module GCodes, available RAM 6336 bytes (slot 0)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
Error status: 0
Free file entries: 8
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 35.0, current 35.3, max 35.4
Supply voltage: min 20.3, current 20.4, max 20.4, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, 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-05-30 16:36:58
Cache data hit count 3482319139
Slowest loop: 1.11ms; 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: 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 -1 -1 -1, chamberHeaters = -1 -1
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Stack records: 1 allocated, 1 in use
Movement lock held by null
http is doing "M577 X S0 " in state(s) 0 0
telnet is idle in state(s) 0
file is idle in state(s) 0
serial is ready with "m122" 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: 202.68ms; 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 5
WiFi firmware version 1.22
WiFi MAC address 80:7d:3a:3f:f3:eb
WiFi Vcc 3.34, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 28992
WiFi IP address 192.168.1.84
WiFi signal strength -55dBm, reconnections 0, sleep mode modem
Socket states: 0 0 0 0 0 0 0 0
- WiFi -
I'm making some progress. When I uploaded my sys folder containing my configuration files using the uploader in the Duet web interface the folder ended up in the gcode folder.
I have now used an external SD card writer to move the sys folder to the root and am getting some motor current and can home the axes.