Ultimaker 2 Go X or Y Axis Error on First Start Up

[LiquidCrimson 1]

Hi,

On first start up during the X/Y Homing calibration we receive an error "X or Y Axis Error on First Start Up"

New out of the box, on set up – ‘Homing’ the print head moves to the left, hits the limit switch and bounces back then errors – ‘X or Y switch broken’.

Tried to bend/straighten limit switch.  Installed Cura and updated firmware.

 

We clicking the limit switch with a pen manually the print head stops correctly.

The Print head also appears to not correctly align to the print bed (which you can see in the video)

Not sure what to do next... help appreciated, thanks.

Video of the ‘bounce’ can be viewed here...

 

Edited December 28, 2015 by Guest

[IRobertI 520]

Do you have access to a multimeter, or access to a person that has one? I would measure the switch and see if it's actually closing and opening when you push the lever or if it is permanently closed. The easiest way to access it would probably be to unscrew the switch from the printer.

Just make sure you are careful when you re-attach it, don't overtighten the screws as you risk stripping the threads ( which are formed by the screw when it is first inserted and therefore fairly weak).

If it passes that test I would flip the machine over, remove the cover over the electronics and check the connection to the board.

Edited December 28, 2015 by Guest

[tinkergnome 927]

During "Home head" the printhead should move simultaneously in the x and y direction.

It seems to me that the y-axis doesn't move at all. If you're lucky it's just a loose connector on the board.

[LiquidCrimson 1]

Thanks for the responses.

The Y Axis doesn't move at all, and therefore only the X axis limit switch gets triggered. I received the Ultimaker to go in this condition.

Is the basic recommendation to check it's connected on the board?

[tinkergnome 927]

Is the basic recommendation to check it's connected on the board?

 

Because this is a new printer, i recommend to contact the reseller first.

But basically: yes - perhaps a connection came loose during transport - or a cable was damaged....?