X5SA DuetWifi - Common Problems and Fixes.

chriskimbr

Stock Motors are current plugged in as is, no rewiring.

Stops are rewired, stp and blck for ground on two ends.

Homing, going haywire, running into stop sensors and grinding.

Stephen6309

We'll need your config.g and homing files.

Usaually grinding against the endstops, means the firmware thinks the endstop is never triggered.

chriskimbr

when i do the tests and it prompts to press x endstop, it sees it.

But when i home, its ignores it.

DocTrucker

Assuming motors are wired as the duet expects...

Power off machine.
Manually move machine slowly to ensure limit switches are touched.
Move head to middle of x, y, z travel.
Power on machine.
Send gcode G92 X0 Y0 Z0.
Use the web control to nudge each axis in small movements to ensure it moves in the correct direction.
While in a position where no limit switches are triggered send M119 to endure the firmware agrees that no endstop is triggered.
Press and hold each endstop switch in turn and send M119 and ensure the limit switch is recognised on the firmware, and is correctly at the min or max travel.
Home each axis in turn ensuring the axis moves toward the switch.

DocTrucker

We'll need to see config and homing files if my previous post doesn't help.

chriskimbr

@doctrucker will try tonight and post results.

DocTrucker

To save other people searching this is the machine:

http://www.tronxy.com/web/index.php?topclassid=11&classid=17&id=77&lanstr=en&wap=1

330mm in x and z, 400 in z. Appears to be a core xy belt pattern.

DocTrucker

If you've not seen the following it's worth a read:

https://duet3d.dozuki.com/Wiki/Connecting_endstop_switches

chriskimbr

This post is deleted!

chriskimbr

This post is deleted!

chriskimbr

5_1550732071399_homex.g 4_1550732071399_homedelta.g 3_1550732071399_homeall.g 2_1550732071398_config.g 1_1550732071398_homez.g 0_1550732071398_homey.g

chriskimbr

@doctrucker Home X and Home Y seem to be working now.
However Home Z sends the Bed down(+) instead of up(-) towards the hot end.

DocTrucker

~~How did you get on following the list of checks I suggested? Where did it go wrong?~~

Edit: writing while you posted!

DocTrucker

Try running I0 on M558 in the config file?

DocTrucker

If you look on the web control it displays the reading from the probe. If it doesn't menyion the probe on the endstop status check there.

You wang to ensure it triggers at the right level manually before using it automatically.

If it is triggered when it shouldn't be and not triggered when it should be (according to dwc or firmware rather than light on probe) then the I on M558 is inverted.

DocTrucker

...but it will raise a little before diving as defined by the dive height.

"When using mesh bed compensation or running G30 commands with specified XY coordinates (for example from the bed.g file), the firmware moves the Z probe to this height above where it expects the bed to be before commencing probing."

https://duet3d.dozuki.com/Wiki/Gcode