Homing fails on printerbot

nerdiator

I recently replaced my broken printerbot board with a Duet2Wifi. I'm a noob when it comes to the internal workings of this all but I think that I understand homing now. If I get it right, the goal is to move the printer to the starting point of the grid? I managed to configure my board in a way that it moves to the 0,0 mark. It moves in the correct direction but instead of stopping when the X stop and Y stop get triggered, the motors keep going and the homing fails. The LEDs on the board that indicate the X and Y stop do light off, so I think that I got it wired correctly?

dc42

Please post your config.g and homing files.

See https://duet3d.dozuki.com/Wiki/ConfiguringRepRapFirmwareCartesianPrinter#Section_Homing_files for a description of what these files should contain, and https://duet3d.dozuki.com/Wiki/Connecting_endstop_switches#Section_Test_endstop_switches for how to test that the endstop switches are being recognised.

nerdiator

Here is my config.g file: https://pastebin.com/CHfyAcJV

And these are my homing files: https://pastebin.com/MvB4A0rG

Phaedrux

Can you describe where on your printer the end stops are located? If you are looking at the printer from the front, the 0,0 position would be the front left corner. X- would be to the left, Y- would be towards the front.

Have you gone through the links provided above?

nerdiator

This is the position where all endpoints are being triggered:

This is the opposite position of the endpoints:

And I've been through your links, and I do see the endpoint status switching from yes to no in the machine settings when I move the bed and extruder

Phaedrux

If you send M119 in the gcode console with the endstop switches not pressed, what does it reply with? And if you manually depress the switches, what does it reply with?

nerdiator

M119 without endstops pressed:
Endstops - X: not stopped, Y: not stopped, Z: at min stop, Z probe: at min stop

M119 at endstop position:
Endstops - X: at min stop, Y: at max stop, Z: at min stop, Z probe: at min stop

Veti

your homing files require at least firmware version 2.03

which one are you running?

nerdiator

I'm running on 2.0.4

Phaedrux

So the Z endstop shows as activated even when it's not activated?

nerdiator

@Phaedrux I didn#t move the Z, it's probably just still activated because it's so low. I wanted to make X and Y work first

Phaedrux

Can you try modifying your homing files to remove the H2 from the second back off movements for X and Y?

ex: G1 H2 X5 F6000 ; go back a few mm

nerdiator

I tried that but it doesn't seem to help. I get an error saying "Insufficient axes homed"

Phaedrux

Mind you I only mean the moves that have X and Y movement. The move to lift Z at the start would stay the same.

If you're still getting that error message after only removing the H2 from the X and Y moves it would tell me that the X and Y axis are not actually getting homed on that first pass.

nerdiator

Yes that's what I did. Only for the X and Y moves, but they don't get properly homed

dc42

Something isn't right with your config. You indicated that the position where the X and Y homing switches get triggered is the corner of the bed marked with an X. That must be either X0 Y0 or X160 Y160. Assuming it is the bed that moves in Y and the print head that moves in X, as things stand your config says you have the X endstop at X0 and the Y endstop at Y160, which if those coordinates are where the X is, would give you mirrored prints.

nerdiator

@dc42 Oh I see. I just configured it until it moved to 0,0. But I probably made a mistake with the endstop location. But still, it should stop when the endpoint is triggered, right?

Veti

on moves that have the parameter H1.
if you really have a recent firmware.

are you sure that you did not swap x and y endstops?
what kind of endstops are they?

nerdiator

@Veti They are buttons that give a 3.3V current when pressed, 0V when not pressed.