Hi, I'm having trouble with the Ares printer;

Hi, I’m having trouble with the Ares printer; everytime I start a print when the G29 code is sent, the printer drives the motors up (in Z) so that the rails hit the top of the printer and continue to drive the motors. I’ve attached a snippet of the terminal output from the printer before I had to turn the printer off to stop it damaging itself:
Recv: T:227.6 E:0 W:2
Recv: T:228.0 E:0 W:1
Recv: T:227.6 E:0 W:0
Recv: ok
Send: N6 G2821
Recv: ok
Send: N7 G29
21
Recv: Bed x: 35.00 y: -70.00 z: 49.98
Recv: Bed x: 0.00 y: -70.00 z: 54.97
Recv: Bed x: -35.00 y: -70.00 z: 59.96
Recv: Bed x: -70.00 y: -35.00 z: 64.95
Recv: Bed x: -35.00 y: -35.00 z: 69.94
Recv: Bed x: 0.00 y: -35.00 z: 74.93
Recv: Bed x: 35.00 y: -35.00 z: 79.92
Recv: Bed x: 70.00 y: -35.00 z: 84.91
Recv: Bed x: 70.00 y: 0.00 z: 89.90
Recv: Bed x: 35.00 y: 0.00 z: 94.89
Recv: Bed x: 0.00 y: 0.00 z: 99.88
Recv: Bed x: -35.00 y: 0.00 z: 104.87
Recv: Bed x: -70.00 y: 0.00 z: 109.86
Recv: Bed x: -70.00 y: 35.00 z: 114.85
Recv: Bed x: -35.00 y: 35.00 z: 119.84
Recv: Bed x: 0.00 y: 35.00 z: 124.83
Recv: Bed x: 35.00 y: 35.00 z: 129.82
Recv: Bed x: 70.00 y: 35.00 z: 134.81
Recv: Bed x: 35.00 y: 70.00 z: 139.80
Recv: Bed x: 0.00 y: 70.00 z: 144.79
Recv: Bed x: -35.00 y: 70.00 z: 149.78
Recv: 40.32 60.24 55.24 50.26 60.28
Recv: 65.23 70.17 75.14 80.15 85.19
Recv: 110.13 105.08 100.03 95.10 90.17
Recv: 115.13 120.07 125.04 130.05 135.09
Recv: 140.11 150.06 145.06 140.08 160.07
Recv: ok
Send: N8 M10745
Recv: ok
Send: N9 G92 E0
78
Recv: ok
Send: N10 T011
Recv: echo:Active Extruder: 0
Recv: ok
Send: N11 M104 S225
80
Recv: ok
Send: N12 G92 E0116
Recv: ok
Send: N13 G1 X16.39 Y33.09 Z0.68 E0 F12000
117
Recv: ok
Send: N14 G1 X16.39 Y33.09 Z0.38 E0 F6000*66

Any idea’s what’s causing this/how it can be fixed?

I had that happening before but usually things just resolve after a G28 or a reboot. So today, I set out to reproduce it using OctoPi’s Terminal. I am able to at least under one condition: If the hotend is at home position (or close) when OctoPrint restarts (“System → Restart OctoPrint”), an immediate G29 without preceding G28 will cause the rods to hit upper stop. But if G28 is issued immediately after OctoPrint restart, there is no problem.

From your posted snippet, the output comes from a preprogrammed G-code file. Can you try to execute G-code from the Terminal and see if anything weird happens? There is a possibility that some files cause Ares to behave badly.

@whackyhack Thanks for taking a look at this. I spent many hours yesterday trying to figure out what was causing it. Trying out the commands directly through the terminal is a good idea and what I ended up doing. I eventually realised that the switch used for auto-leveling was slightly out of place and loosening the screws, adjusting the sensor and trying again seemed to resolve the issue. I’ve now been able to execute G29 without issue :smiley: