Hello.

I upgraded to firmware 2.05 about 2 weeks ago or so. After doing so, nothing happens when I try to move a motor. At first there were some errors about phases, but now nothing at all. The wiring did not change at all, and I'm sure I have the phases correct. After sending a move command, nothing errors out, and the system message at the top will say "Busy" for a moment, then it will report the axis position as moved that amount. I.E. I press x+10 after boot up, and x position reads 10, but no move. If I try to manually turn the motor after making the move, it spins freely.

Now, the odd part: All heaters, fans, and thermistors are still functioning 100% correctly. Even the ir sensor and endstop leds will still go red and report that it is triggered. I have checked all fuses, however my Duet Wifi 2 is an older model when they were soldered on. 5v and 3.3v rails all show as working properly under my multi-meter.

So I went back to the 2.02RC6 that was on it originally before all this. I unplugged all drives, plugged in only 1 to drive 2 which is set at X in my firmware, powered the duet back on, and tried to run it. Still nada.
M122 Reports the following:

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.02RC6(RTOS) running on Duet WiFi 1.0 or 1.01
Board ID: 08DAM-999TL-MQ4S8-6JTD0-3SJ6L-14BMW
Used output buffers: 3 of 20 (9 max)
=== RTOS ===
Static ram: 25524
Dynamic ram: 98508 of which 0 recycled
Exception stack ram used: 392
Never used ram: 6648
Tasks: NETWORK(ready,648) HEAT(blocked,848) MAIN(running,3804) IDLE(ready,200)
Owned mutexes:
=== Platform ===
Last reset 00:05:16 ago, cause: power up
Last software reset at 2019-12-12 01:30, reason: User, spinning module GCodes, available RAM 6648 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 35.9, current 39.9, max 40.1
Supply voltage: min 12.3, current 12.4, max 12.5, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, SG min/max 0/0
Driver 1: standstill, SG min/max 0/0
Driver 2: standstill, SG min/max 0/1023
Driver 3: standstill, SG min/max not available
Driver 4: standstill, SG min/max not available
Date/time: 2020-01-03 23:17:10
Cache data hit count 1166347818
Slowest loop: 3.96ms; fastest: 0.07ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0
=== Move ===
Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm: 239, MaxWait: 159273ms, Underruns: 0, 0
Scheduled moves: 21, completed moves: 21
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, 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: 15.79ms; fastest: 0.00ms
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.23
  WiFi MAC address xxxxxxxxxxxxxxx
  WiFi Vcc 3.38, reset reason Turned on by main processor
  WiFi flash size 4194304, free heap 25936
  WiFi IP address 192.168.254.75
  WiFi signal strength -41dBm, reconnections 0, sleep mode modem
  Socket states: 0 0 0 0 0 0 0 0

I tried a breakout and a bare ramps board from the expansion header and the same, so decided to scope it. No signals are going out for en, step or dir from any pin on the board.

Since I have tried upgrading on to 3.0. No go still. I know it's way out of warranty as I bought it in 2017, however this board only had about 50 - 60 hours of total print time (Was on my Mono Maker Select v2). Anything else I can try, or test to see if it is a single driver being bad? I have used the multi-meter and verified no voltage is coming from any pin when I tell a motor to move using the test pads on the board.

I do have access to a 4 channel Rigol scope at home, and a nice Keysight one at work if I need to scope anything.

Worked like a charm, thanks. Also turning off the fans during warmup helped a lot. >.> Forgot to disable them during heating.

I am attempting to get my heated bed to tune for printing ABS. It's a stock Maker Select V.2. With a Rambo Mini, I was able to get it to 110* C easily. I can get it tuned to 90*, albeit hit and miss. About half of the time it will fail. If trying to go above, I get a bad curve error. I have swapped between a Meanwell 12v 500w supply, the stock supply, and a Corsair AX750 and Antec Earth Power 600 watt atx supplies, so I don't think it's a power issue or a bed issue. Here's my error:

3:13:48 PM
Warning: Auto tune of heater 0 failed due to bad curve fit (G=67.4, tc=239.3, td=-1.2)
3:10:08 PM
Auto tune phase 3, peak temperature was 100.0
3:10:01 PM
Auto tune phase 2, heater off
2:59:21 PM
Auto tune phase 1, heater on
2:59:15 PM
M303 H0 P1.0 S100
Auto tuning heater 0 using target temperature 100.0°C and PWM 1.00 - do not leave printer unattended

Any suggestions?

Yep. Stupid me didn't check inside my quick connect wire setup for my hotend change out. The sense pin was about 100mm too short. Thanks for the help!

I am trying to get my sensor calibrated to my new setup. It works fine on another build I have with an older Duet board and BuildTak base, even now, so I know it is functioning correctly. On my new build, I have a matte aluminum print bed with pei over it. I first sanded the pei, but the problem was still the same, so I took it all off, cleaned the build plate with denatured alcohol, then painted the bottom of a new pei sheet with black oven paint before reapplying. The problem is still there.

The sensor triggers from Y200 down to about Y110, but from Y0 - Y110, nothing, even right next to the IR sensor. It just has a constant reading of ~265 around the front half of the bed. Not sure what else to try. I moved the older board to the newer machine, and it's the same, so I know it's not the wiring or the electronics themselves. Is there something else I could check that would cause this? Anything in software able to cause it only to detect 1/2 of the y axis of the bed? Cause I did just copy the base files for the new machine over to the old board to test. Also, I am just using M558 P1 and G31 P500 Z1.0 in the console for now, so I don't have it in the config files until I get this worked out. Thanks!

I'm in the process of converting out my 2020 aex Core XY system to a Cartesian system with IDEX. (Though I am torn between a modified prusa x-axis for a z-axis bed, Makerbot, and E3d BigBox movement mechanics >.> ) I am going to be using a central mount with the belts attached and the DC42 IR Probe for my X-Axis. This central mount will have 2 of the above mentioned electromagnets. Basically I wanna be able to park the left extruder and pick up the right one via g-code changes to turn on and off the left or right magnet.

I used relays for my prusa clone to do this same thing. For the Duet WiFi, I was thinking about using the extra heater outputs on the expansion header for it. I am going to be using the last two fan outputs on it for the part cooling fan for each extruder. Am I correct in that I can just simply hook the magnets up to say the heater 2 and 3 connections with a diode in parallel and be fine? Then just add in the gcode to turn on or off that heater each time I need to change the extruder out?

I took the advice of a local friend that has this board and tried to SSH into the SD card to look at the firmware. I was getting some errors when trying to open the files. So I decided to just pull it out and look at it on my pc using an SD card reader. It immediately popped up a file structure error and told me to format the SD card. It failed in the attempt. So, I decided to go to the github (dc42, your repository of files here is awesome!). I grabbed the Sys-CoreXY build, popped it on a fresh SD card, and ran through the configurator for detailed options. Works like a charm now.

I don't know if my original firmware update failed due to a power/net issue, or it was just a dud SD card destined to fail, but all is awesome now. I want to thank you guys for your help and advice. The M122 code tipped me off a bit on it, thanks for pointing me there for the voltages yesterday dc42. Here was the readout I was concerned with:

SD card 0 detected, interface speed: 11.7MBytes/sec
SD card longest block write time: 582.4ms

My friend told me that is should be interfacing at around 20 MB/s and writing under 50ms for most of the up-time.

@elmoret:

I did receive those emails regarding the heatbreaks, and replied about 2 hours later. Looking more closely, it seems like my reply didn't get to you because of the email address entered in the contact form (which differs from subsequent emails):

http://i.imgur.com/uf3Xr6c.png

I'm happy to waive the shipping on a second order if you'd like, since it was just a communications problem.

I checked my server this afternoon and it appears I was losing lots of packets last week in the upstream. When I placed that second order today, it took 5 times for me to get the credit card to accept. No need to refund anything, this was entirely on my side. Besides, I added that PT100 board, so shipping was free. No need to rush it though. The other company is re-cutting my extrusions at no cost as this was their error. Fabrication of the extrusions is going to be at a week time frame though due to the dimensions, so I'm in no hurry. Thank you again for your wonderful service.

@dc42:

1. Are you certain that you have identified the phases of the motors connections correctly? See https://duet3d.com/wiki/Connecting_stepper_motors#Using_the_internal_drivers.

They are 6 wire variety, but they came with the phases already split out on a connector at 2B 2A 1A 1B. I tested the resistances last night to ensure the phases were correct, and even went so far as to test the motor with an LED. I know, ghetto, but was afraid maybe my scope and meter were failing me. When connecting them to a sanguinololu, Duet 0.6, or a UltiController v2.1 board, the motors all performed flawlessly.

@dc42:

2. Make sure that you are not trying to move them too fast or with acceleration that is too high, especially if you have increased microstepping, or you are running the motors well below their rated current.

I tried lowering the accelerations and movement rates to 1/4th of what they are. I've had microstepping at 1/16 the entire time until I get everything ironed out. I bumped the rated current all the way up to 95% max, still the same problem. If I only have 1 motor hooked up on the X output and I send a +10 on X, it jitters, but will move about 10 - 15 down the rail, stop, then go back around the same amount, but not exactly the same each time. If I send a +10 on Y, it jitters and will move slightly. Z and both E's it remains motionless as it should.

@dc42:

3. Make sure the power supply voltage is not too low or is dropping when you drive the motors. If the voltage drops below approx. 9.5V then the drivers will be shut down until the voltage reaches 10V again. You can see whether this has happened by sending M122 and looking to see if any under-voltage events have been recorded. Check that the VIN terminal block screws are tight.

Checked this purposefully at work today just to make sure. I am using an Corsair AX760 that has a single 12v rail at 756w. I know overkill, but this power supply was having to power a 12v 300x300 heater in another build. My kossel machine that I tested it on is a Mean Well NES-350-12 12V 350W DC power supply. At work, a few of my colleagues helped me test it using several other 4/6/8 wire nemas we had laying around. I used a Keysight Technologies 6652A variable power supply to ensure smooth power during this. I scoped it again with an Agilent MSO9254A, a bit better than than one I used at home. There is on average 43% of the amperage that is supposed to go out the X output going out the Y output.

I did think to check the traces while I was there. I didn't use the x-ray, but just a standard scope and ensured there were not solder or trace breaks across the X and Y outputs, and made sure that they weren't connected in anyway so I'd say it is on a software level. I will take time to dig through all the firmware and flash it all with the most up to date from github on Monday.

I've actually plugged in and unplugged motors so many times one of the plastic connectors on the board is now broken, but the pins are fine. It was just the tall support piece that the connector locks into. I am going to take a break from troubleshooting it over the weekend. I'll check back though if there are any other suggestions, and report back after I have re-flashed it Monday.

@dc42:

Regarding the endstops, the endstop LEDs on the Duet light when the switches are closed. Therefore when you use normally-closed switches (which is recommended), the lights are on when the switch is connected but not triggered, and of when it is triggered. This is described at https://duet3d.com/wiki/Connecting_endstop_switches.

Thanks! I didn't see this in one spot on doing the endstops, but found it in another on the wiki after you mentioned this. I swapped them out for normally-closed switches and the LEDs all went out.

@elmoret:

Tim here, from Filastruder. I've looked through emails and the only one I'm seeing is the one sent at 1AM EST today, about 7 hours ago. I've replied to that one, concerning the Duet's stepper outputs. The Duet is tested before shipment and it seems very unusual that all stepper drivers are faulty, so there may be some troubleshooting needed. Rocking back and forth like you describe often means a miswired stepper.

Regarding the LCD - I looked at your order and you only ordered the LCD, you did not order the PanelDue.

What other issues ("tons of issues") where you having?

I am following this diagram:

https://duet3d.com/wiki/Duet_WiFi_wiring_diagrams

I have worked with steppers professionally for many years. I am taking it in to work today though to have a colleague of mine see if it is just me and my equipment here. Always a possibility.

On the LCD, I was sure I'd ordered the one with the Ormerod Board. But then again, I was sure I'd ordered 3 E3D V6 Heatsinks only, but after the order was placed, I saw they weren't on the order. I emailed 2 times on that, then again about that LCD when I first received the package using the email from my order, but hadn't received word back. After the previous poster had mentioned how good you are on replies, I thought it may have been a bad email address or even that laptop I was using to complete the contact form with so did it on another pc with another email. I've even tried to sign up to the website so I can actually log in, but when I click log in, it tells me "Invalid login credentials." I signed up with the original order, then again when I was trying to find order info after I saw the E3D heatsinks weren't on the receipt. Just checked the receipt again and it shows LCD only. Gah. Well, I'll be ordering that Ormerod later today.

I sent about 4 or 5 more times through that contact page on the website to find troubleshooting stuff on the Wifi board since I got it in the mail 24 hours ago. I was trying to find wiring diagrams, etc. Previous Duet boards I ordered came with a little pamphlet in them showing the wiring schematic, pin layout, etc, but this one came in with nothing. So after a lot of searching, I found this site through github where I always get my Duet firmware.

The original email used to sign up order was xxabyss23xx@yahoo.com. Maybe it's mostly been issues on my internet end, and I am sorry for that. I had 3 other orders that came in bad with it, one of which I ordered 3 E3D Titans from Amazon for $178, and got 3 cheap MK8 brass kits in its stead, and all of my extrusions for this build from SMW3D came in at the wrong lengths, and 2 rods from another company came in bent, so I've been quite frustrated this week. Really sorry if that's came out in my post. Of every build I've attempted from scratch, this has been the worst!

On the board itself, here are the problems still persisting:

1: When I run an M119, it reports that only Zprobe and extruder endstops hit, but the lights are on for x, y, and z. I can manually push in an endstop switch, and the light goes off then. I've changed out the code for them being active high/low to no avail. It has stopped reporting as triggered on the M119 command finally though since I have left it set to M574 X1 Y1 Z1 S1.

2: If I tell it to move say X +10 or -10, X and Y motors will jitter back and forth for a bit then stop, but no smooth motion. Same for Y. Z will move, but it is very jerky. When only hooking a single motor up: The X jitters back and forth no move, moving it to Y, jitters but no move. On Z it will move about 3 turns of the shaft, stop, move 2 or 3 more and stop, etc until it completes the movement amount. Scoping it revealed current to be passing into Y and X concurrently when sending a move command to only one, not sure why there. It's reading at 400mA at each driver when the config is set to 800mA per channel. Might be firmware, I did update to the newest on everything as soon as I got the board. For the Z, it is showing intermittent spikes of current, which appeared normal to me, but then I decided to check the output for both coils, and one coil was getting 1/2 the power of the other coil. E1 and E2 send out nothing when sending extrude commands. The heater will heat up and reports roughly the right temperature without even tuning it yet.

3: The wifi has lost connection many times and is sitting next to my router. My phone and laptop cannot connect to it. I click connect on it's server page, it goes yellow and says "Connecting…" but just stays there. It will still connect fine on my server machine though. This all worked fine before I updated the firmware. My current firmware looks like this:

irmware Name: RepRapFirmware for Duet WiFi
Firmware Electronics: Duet WiFi 1.0
Firmware Version: 1.17e (2017-02-10)
WiFi Server Version: 1.03 (ch fork)
Web Interface Version: 1.14a
Web Interface by Christian Hammacher
Licensed under the terms of the GPL v2

I just decided to try something else this morning. I connected a cheap external pololu shield and all 3 motor drivers on it worked flawlessly when setup. I now have it moving around fine on x, y, and z running from that board using the expansion header and using M584 X5 Y6 Z7 and the M569 to set the active and pulse width. While at work today, I will try to also reinstall firmware on it using their servers in case it was a bad download. In the meantime, any suggestions would be appreciated. I have a full slew of test equipment available here and at work (I teach Space Systems Engineering at a local University),

As a side note, I looked through the GitHub to answer my first question. Luckily I have an ARM Microcontroller, the ATSAM3S2BA-AU, so I should be able to do it. Just gotta dig up all the capacitors and such.

But yeah, on the motor issue, didn't think of it in my last post, but I even tried a motor on every driver with no endstops hooked up (Yes I did turn off the power before swapping it out).