X tower is going crazy

[Koops]

Hi guys,

My problems seem to be non-stop!

Switched the machine on today to try out the Slic3er as a enginer after experiencing bridging problems, the bed heated and so did the hot end, it moved down to print and stopped mid way only for the x tower to continue going and keep going once it hit the bottom, sending the extruder off the build plate.

turned off, restarted and now only the x tower is moving, trying to drive itself into the bed.

haven't done anything new! except switch the slicing engine.

thanks in advance!

[geneb]

Does it home properly? You might try re-setting your z-zero point as well.

I'd also check to make sure the stepper motor connectors are fully seated - but check with the power off! If you unplug a stepper with the power on, you'll kill the driver for that axis.

g.

[Koops]

Started a Print again after adjusting z-height, this time print went straight down into glass, and kept driving before I managed to turn off by switch.

Went to adjust z height again, and now its at like 800.00mm , how can this be? No idea what is going on!

[Koops]

It homes properly

[Koops]

All the axis are performing correctly, just ran the tower calibration without any problems.

[Koops]

it's just when I print strangely

[IMBoring25]

Is there a G92 command with a Z0 parameter on it in your start gcode? That would usually be unnecessary but not break anything on a machine that homes to a min endstop on Z, but that these machines are not.

[Koops]

Is there a G92 command with a Z0 parameter on it in your start gcode? That would usually be unnecessary but not break anything on a machine that homes to a min endstop on Z, but that these machines are not.

There doesn't seem to be

[Koops]

Right, Mattercontrol as slicer engine works fine, its only when I selected Slic3er as the enginer the x axis shoots across the leveling bed on at printing height

[IMBoring25]

That's a winning piece of information. Integration of Slic3r into MC has been buggy for deltas. Not sure if they ever have or ever will fix it, but the newer versions of Slic3r expect the bed dimensions to be expressed differently than MC supplies them, which leads the machine to try to print off the bed. You can download the standalone version of Slic3r, configure it appropriately, and load the resulting gcode files into MC or use one of the other slicers (or one of the other hosts).

[geneb]

Agreed. If you want to use Slic3r, download the stand-alone version and use that.

g.

[Koops]

Once again, than you all for the help, I'm moving to use Slic3r now in hope I can better control the bridging aspect