WebControl/USB connecting,LEDs light up, but motors not turning

[sogus]

Hi,

I'm using a Duet Wifi (1.02 or later according to the M122 command. I can't recall which version exactly) running the latest DuetWifi, web server, and web control firmware.

When the board is connected to the main power supply or just USB power, the appropriate LED lights light up. In addition, I can connect to the printer via Pronterface and RepetierHost using the USB, and have no trouble connecting to the board using Web Control. However, whenever I send a movement command to any of the axes or send an extrusion command to either of the extruders, nothing happens. The coordinate value in the control panel changes by the inputted value (i.e. after sending "G1 X1", X0 Y0 Z0 becomes X1 Y0 Z0), but nothing happens to the printer.

The board looks fine, and I've tried using a different stepper motor on each motor port on the board to no avail. When I send a G-code command through Web Control I see no error messages in the "G-code Console" page of Web Control.

I've even tried erasing and re-updating the firmware on the board but this didn't help either.

I've been using the board for over a year, and this problem only came up a couple of days ago, when the printer had worked just fine the day before that. The printer finished the print and after that last print I didn't edit the config.g file or even change anything about the firmware, but the printer wouldn't respond the next day.

I'm thinking it may be a hardware issue, as I've done what I can to deal with firmware issues, and I'm less capable when it comes to dealing with hardware problems. Below is the message I get after sending the M122 command:

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.0(RTOS)RC2b running on Duet WiFi 1.02 or later
Board ID: 08DAM-9K9K2-NGNS0-7JTD0-3S86J-T53BK
Used output buffers: 3 of 20 (8 max)
=== RTOS ===
Static ram: 28412
Dynamic ram: 96372 of which 0 recycled
Exception stack ram used: 296
Never used ram: 5992
Task NETWORK ready, free stack 340
Task HEAT blocked, free stack 1256
Task MAIN running, free stack 3556
=== Platform ===
Last reset 00:09:57 ago, cause: reset button or watchdog
Last software reset at 2018-07-05 15:58, reason: User, spinning module GCodes, available RAM 6208 bytes (slot 1)
Software reset code 0x0003 HFSR 0x00000000, CFSR 0x00000000, ICSR 0x0441f000, BFAR 0xe000ed38, SP 0xffffffff
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms
MCU temperature: min 56.3, current 62.3, max 62.6
Supply voltage: min 1.9, current 24.6, max 24.8, under voltage events: 0, over voltage events: 0
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: 2018-07-06 10:32:24
Slowest main loop (seconds): 0.010635; fastest: 0.000057
=== 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 = -1 -1 -1 -1, 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
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
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.21
  WiFi MAC address 5c:cf:7f:37:88:09
  WiFi Vcc 3.38, reset reason Turned on by main processor
  WiFi flash size 4194304, free heap 14200
  WiFi IP address 192.168.1.140
  WiFi signal strength -59dBm, reconnections 0, sleep mode modem
  Socket states: 0 0 0 0 0 0 0 0
  === Expansion ===

[dc42]

It could be a power issue, judging from the minimum VIN voltage in the M122 report. In particular, check that the VIN terminal block screws are still tight.

[sogus]

Hi dc42, thanks for the prompt response.

I went and double checked the screws, and they were a bit loose. Unfortunately, while tightening them did increase the minimum voltage, it didn't change any of the issues with the motors.

The M122 report after the screws were tightened is as follows:

=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.0(RTOS)RC2b running on Duet WiFi 1.02 or later
Board ID: 08DAM-9K9K2-NGNS0-7JTD0-3S86J-T53BK
Used output buffers: 3 of 20 (9 max)
=== RTOS ===
Static ram: 28412
Dynamic ram: 96372 of which 0 recycled
Exception stack ram used: 312
Never used ram: 5976
Task NETWORK ready, free stack 436
Task HEAT blocked, free stack 1256
Task MAIN running, free stack 3556
=== Platform ===
Last reset 00:01:30 ago, cause: power up
Last software reset at 2018-07-05 15:58, reason: User, spinning module GCodes, available RAM 6208 bytes (slot 1)
Software reset code 0x0003 HFSR 0x00000000, CFSR 0x00000000, ICSR 0x0441f000, BFAR 0xe000ed38, SP 0xffffffff
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms
MCU temperature: min 39.6, current 56.9, max 57.3
Supply voltage: min 24.5, current 24.5, max 24.8, under voltage events: 0, over voltage events: 0
Driver 0: standstill, SG min/max not available
Driver 1: standstill, SG min/max not available
Driver 2: standstill, SG min/max 0/0
Driver 3: standstill, SG min/max not available
Driver 4: standstill, SG min/max not available
Date/time: 2018-07-06 11:41:52
Slowest main loop (seconds): 0.012016; fastest: 0.000065
=== Move ===
Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm 239, MaxWait: 1578624715ms, Underruns: 0, 0
Scheduled moves: 2, completed moves: 2
Bed compensation in use: none
Bed probe heights: 0.000 0.000 0.000 0.000 0.000
=== Heat ===
Bed heaters = -1 -1 -1 -1, 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
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
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.21
  WiFi MAC address 5c:cf:7f:37:88:09
  WiFi Vcc 3.38, reset reason Turned on by main processor
  WiFi flash size 4194304, free heap 12096
  WiFi IP address 192.168.1.140
  WiFi signal strength -57dBm, reconnections 0, sleep mode modem
  Socket states: 0 0 0 0 0 0 0 0
  === Expansion ===

[dc42]

@sogus, please send M906 without parameters to verify that the motor currents have been set. Also, after attempting movement, check the Console page of DWC or PanelDue for error messages, and run M122 again to check that the minimum VIN voltage is still good.

[sogus]

The motor currents are what they've been since I set up the printer.

The console page didn't show any errors when I moved, and the voltages didn't change after the movement commands were sent. Still not movement on any motor.

[dc42]

The only thing I can think of is that the ENN signal from the microcontroller to the stepper driver chips is stuck at a high level, or that somehow there is no VIN feed to the stepper drivers. But there is probably a much simpler explanation.

You can measure the ENN signal on the expansion connector. It should be +3.3V when no VIN power is present, falling to 0V when VIN power is present and the drivers have been initialized.

[sogus]

Hi, sorry for the delay in my response.

This photo is the ENN on the expansion connector when there's no VIN power:

And when VIN power is supplied, there's no change:

[dc42]

Thanks. That's not right. ENN should be at +3.3V if there is no VIN power applied, and fall to 0V shortly after VIN power is applied.

There is another thread at https://forum.duet3d.com/topic/6038/whats-wrong/16 from a user with possibly a similar problem, although he hasn't measured the ENN voltage yet.

[sogus]

At this point it seems like it's possible that some component on the board is in need of replacement.

Would it be possible to send the board in to be looked at and hopefully repaired?

[dc42]

Yes, please ask your supplier to exchange the Duet.