incorrect Y axis origin

[cairn 5]

Not sure if this is an Ulti or an S3D question, but when I import a model (into S3D) and press center and arrange, the print will look good in the preview, but end up offset on the print-bed +4.5mm in the Y axis, and if it's too big, the print head will 'hit the wall' :(.

I guess I need to either change the machine firmware setup, or change the machine definition in S3D.

Any ideas?

Thanks,

Cairn

(edit: My machine: UM2 Ext )

Edited November 26, 2017 by Guest

[kmanstudios 740]

Which printer? If you put the printer in your profile or description in post, it makes it easier to diagnose what to do to help.

[cairn 5]

Which printer? If you put the printer in your profile or description in post, it makes it easier to diagnose what to do to help.

Ah Oops, edited above, thanks (UM2 Ext) ..

Edited November 26, 2017 by Guest

[tinkergnome 604]

Ah Oops, edited above, thanks (UM2 Ext) ..

How old is your firmware? The usable range for Y was 5 -230mm on firmware versions before 07/2016

This changed with this commit and again a few days later, that means - probably for all firmware versions included in Cura 2.1 and later.

[cairn 5]

How old is your firmware?

Haha no idea, how do I find out? (srsly)

Anyway, regardless of the firmware version, I need to know how to reconcile the y-zero in S3D with the y-zero in the UM2..

[kmanstudios 740]

How old is your firmware?

Haha no idea, how do I find out? (srsly)

Anyway, regardless of the firmware version, I need to know how to reconcile the y-zero in S3D with the y-zero in the UM2..

Follow the links young padawan......

[tinkergnome 604]

How old is your firmware?

Haha no idea, how do I find out? (srsly)

There should be an entry in the "Maintenance" menu (on the printer) - it shows a date and a version name.

[cairn 5]

There should be an entry in the "Maintenance" menu (on the printer) - it shows a date and a version name.

OK thanks, so I have version 15.02.1ex from Feb 2015..

[tinkergnome 604]

OK thanks, so I have version 15.02.1ex from Feb 2015..

Great - that means: you can update the firmware to the current version and your problem is solved.