Motors dont move after G28X - driver short to ground

Lichty

Hey guys I think I have kind of a big problem.

I'm almost finished with my build of a COREXY Printer (BLV MGN CUBE) and wanted to slowly test the electronics.

As a first step I only connected X/Y endstops X/Y motors and wanted to do a small test run with those axis.

As soon as I started homing I got the Error "G28X driver 1 short to ground". Which first sounds pretty bad to me - after some reading in duet forums and so on I checked my motor wiring but those are wired correctly (as mentioned in BLV MGN GUIDE and motors are from BOM-list). So I dismounted my board from the back of my printer to make sure there cant be any short circuit.

I never had the Error again but Im not able to move my X and Y. I can click the endstops manually which is working fine and then use the web interface to control those. The coordiantes are changing as I click on for example "X +1 " but the printer does not move a micron.

Without motors connected and manually clicking the endstops I dont get any Error as well.

Can you guys please help me out - im really out of ideas...

Could it be that the board / driver was damaged before the first use?

Thanks!!

Diagnostics:

Driver 1: standstill, SG min/max 0/1023
Driver 2: standstill, SG min/max 0/7
Driver 3: standstill, SG min/max not available
Driver 4: standstill, SG min/max not available
Date/time: 2019-08-23 17:10:21
Slowest loop: 10.55ms; fastest: 0.07ms
=== Move ===
Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm 236, MaxWait: 2250569219ms, Underruns: 0, 0
Scheduled moves: 10, completed moves: 10
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, 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: 14.12ms; fastest: 0.01ms
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 4c:11:ae:02:e4:88
WiFi Vcc 3.30, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 17000
WiFi IP address 192.168.10.180
WiFi signal strength -44dBm, reconnections 0, sleep mode modem
Failed to request ESP stats
Socket states: 0 0 0 0 0 0 0 0
=== Filament sensors ===
Extruder 0 sensor: ok
=== Expansion ===

dc42

Please check that you have phased the stepper motors correctly. It is important that the two wires from one phase go to the 2 contacts at one end of the 4-pin connector, and the 2 wires from the other phase go to the 2 contacts at the other end. It doesn't matter which phase goes to which pair of contacts, or which way round each pair of phase wires is connected.
When you are sure of #1, test the motors individually as described at https://duet3d.dozuki.com/Wiki/ConfiguringRepRapFirmwareCoreXYPrinter#Section_Commissioning.

Lichty

Thank you for your fast response!
I checked the wiring here: https://d17kynu4zpq5hy.cloudfront.net/igi/duet3d/c4tc5QKFkWux5iWq.full

There it says the order for X and Y is: 2B-2A-1A-1B.
One pair is A one pair is B so I connect one pair in the middle of the pin and the other pair on the two outer pins - or am I'm doing something totally wrong here?

EDIT:

tested the double Z-axis which is working totally fine.
connecting another stepper motor gives the same result - nothing is happening

Is there any option that I can check the drivers for X and Y manually?