Core XZ homing issue - HELP

274 views
Skip to first unread message

David Bassetti

unread,
Apr 28, 2016, 8:26:41 AM4/28/16
to Smoothieware Support
Hi all,

I have a problem with the Core XZ on my Smoothieboard.

I used JNJ's  method for connecting the motors as per below..
https://github.com/Smoothieware/Smoothieware/blob/edge/ConfigSamples/Snippets/corexz.config

# arm_solution                                 corexz             # selects the corexz solution

# x_reduction                                  1.0              # standard CoreXZ has no reduction on x axis
# z_reduction                                  3.0              # standard CoreXZ has 3X reduction on z axis
# alpha_steps_per_mm                           55               [b]# xz motor 1[/b]
# beta_steps_per_mm                            55               [b]# xz motor 2[/b]
# gamma_steps_per_mm                           110              # y axis motor[/i]

It all moves fine EXCEPT when I home the Y axis ... this makes the Z move..
I think this is because your alpha and beta motors become the X and Z axis.. hence the smoothie does not recognise the true Y axis?

Is it easy ( or how can I do it ) to make the xz motors the actual XZ motors on the smoothie?

Or is there another solution for homing maybe?

Core XZ with Laser.jpg

wolfmanjm

unread,
Apr 28, 2016, 5:47:32 PM4/28/16
to Smoothieware Support
CoreXZ homing would need to be added to the Endstops.cpp file. Currently it only supports CoreXY.

David Bassetti

unread,
May 3, 2016, 10:51:41 AM5/3/16
to Smoothieware Support
Could anybody point me in the right direction ? I have no Idea about coding endstops.. but I can use PayPal ..!!
Is it a big thing to do?

Any help greatly appreciated :)
David

David Bassetti

unread,
May 10, 2016, 4:59:13 AM5/10/16
to Smoothieware Support
Core XZ Homing SOLUTION

Thanks to Andrew Leek ( and lots of whatsapp ) we did it..  !!!

https://github.com/andrewleek/Smoothieware/tree/fix/corexz-endstop

Seems the switches are much harder to "define or change"than the movement of the motors.

So all we did was make the right motor connect to the right driver.. and it homes perfectly :)

Arthur Wolf

unread,
May 10, 2016, 3:53:19 PM5/10/16
to Smoothieware Support
Great.

pull request maybe ?

--
You received this message because you are subscribed to the Google Groups "Smoothieware Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to smoothieware-sup...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--
Courage et bonne humeur.

wolfmanjm

unread,
May 10, 2016, 5:15:54 PM5/10/16
to Smoothieware Support
Yea I wouldn't bother with a PR, this may work but it duplicates a huge amount of code and is very flash unfriendly. I am glad it works for you, but I suspect it has such limited usefulness it is not worth the flash memory it uses for 99.9% of users.

I think with some careful analysis you could reduce the duplication significantly as the differences from corexy are minimal. I suspect a couple of lines need to be c\hanged to make corexy do corexz.


On Tuesday, May 10, 2016 at 12:53:19 PM UTC-7, Arthur Wolf wrote:
Great.

pull request maybe ?
On Tue, May 10, 2016 at 10:59 AM, David Bassetti <dbas...@gmail.com> wrote:
Core XZ Homing SOLUTION

Thanks to Andrew Leek ( and lots of whatsapp ) we did it..  !!!

https://github.com/andrewleek/Smoothieware/tree/fix/corexz-endstop

Seems the switches are much harder to "define or change"than the movement of the motors.

So all we did was make the right motor connect to the right driver.. and it homes perfectly :)

--
You received this message because you are subscribed to the Google Groups "Smoothieware Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to smoothieware-support+unsub...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
0 new messages