Duet 2 wifi - problem
Hi, we got a motherboard from our client with didn't work E0 driver. Motor vibrates, instead of normal working. We checked a cable - is fine; we tested on a few motors - the same problem - only vibrates. Motor connected to E1 driver is ok. We suspect broken stepstick. Can you help us?
Do you get any error messages in the gcode console?
Can you send M122 after the motor has vibrated?
Do the pins of the motor connector look soldered correctly?
Here is M122 code.
=== Diagnostics ===<LF>RepRapFirmware for Duet 2 WiFi/Ethernet version 3.1.1 running on Duet WiFi 1.02 or later<LF>Board ID: 08DGM-917DA-G4MS8-6J1DA-3S86T-T8S7B<LF>Used output buffers: 1 of 24 (3 max)<LF>=== RTOS ===<LF>Static ram: 27980<LF>Dynamic ram: 93944 of which 44 recycled<LF>Exception stack ram used: 256<LF>Never used ram: 8848<LF>Tasks: NETWORK(ready,1252) HEAT(blocked,1288) MAIN(running,1912) IDLE(ready,80)<LF>Owned mutexes:<LF>=== Platform ===<LF>Last reset 00:11:49 ago, cause: power up<LF>Last software reset at 2020-11-16 22:08, reason: User, spinning module GCodes, available RAM 8696 bytes (slot 1)<LF>Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task MAIN<LF>Error status: 0<LF>MCU temperature: min 21.2, current 30.1, max 30.2<LF>Supply voltage: min 0.9, current 1.7, max 1.8, under voltage events: 0, over voltage events: 0, power good: no<LF>Driver 0: ok, SG min/max not available<LF>Driver 1: ok, SG min/max not available<LF>Driver 2: ok, SG min/max not available<LF>Driver 3: ok[Warning: Maximal number of bytes per line exceeded! Check the EOL (end-of-line) settings or increase the limit in the advanced terminal settings.]
Will it help?
The pins are properly soldered.
mendenmh last edited by
Supply voltage: min 0.9, current 1.7, max 1.8, under voltage events: 0, over voltage events: 0, power good: no<LF>
This report says there is something wrong with the power supply. It says you only have 1.7 volts, but I doubt the readback is right! I suspect that means other things on the board are fried, since it it unlikely to actually run on that voltage. If the readback is broken, something has probably been shorted that blew a bunch of stuff.
@mendenmh It likely just means that the Duet was only connected to USB power when the M122 command was sent. There would have been zero motor movement at all if VIN wasn't working.
@Hobby-Store It looks like you've only sent the M122 command when connected to USB, correct? I was hoping to get it after the driver had been used. It would also help to change the End of Line settings in your terminal software so we could see the entire report.
Is the board within warranty period?
mendenmh last edited by
@Phaedrux I hadn't considered the possibility that this was done only on USB power. That would explain wonky answers. Good point.
In that moment, we don’t have service 3D printer on shop to made more tests.
But mainboard have none traces of hardware crash. All parts are clean and have none burn marks, scratches or cracks.
When made resistance measurement on that TMC, we find that:
Z-step/z-dir = 16,58MOh
Y-step/y-dir = 16,46MOh
X-step/y-dir = 16,51MOh
E0-step/E0-dir = 14,20MOh
E1-step/E1-dir = 16,48MOh
All measures was made at background temp = 21*C
At higher temp, measures will be smaller, but still on E0 there will be <2MOh differences.
So, that one TMC on E0 have some issues, but there is no sign of damage, short circuit on pins or someone's hardware manipulation.
The board is under warranty.
bearer last edited by
Change your terminal settings to capture the full output of M122 after trying to move the E0 driver with Vin applied as was requested
I think this has some notes on the termina settings if using YAT https://duet3d.dozuki.com/Guide/1.)+Getting+Connected+to+your+Duet/7