traditional xy in Makelangelo
2017-12-11 at 11:50 #14883AnonymousInactive
Hi, I want to install Makelangelo in a traditional xy mechanical structure.
I have seen that it is possible to configure this way by decomposing Polargraph.
The big problem I have is that the X axis carries two cloned motors and the Adafruit controller only serves two motors. Is it possible to clone the available output?
Thank you2017-12-11 at 12:45 #14885
The Makelangelo firmware supports several kinematic models and boards, including traditional xy gantry layout.
#define MACHINE_STYLE TRADITIONALXY // change it to this
#define MOTHERBOARD BOARD_RUMBA // change this to your controller type.
You might have to tweak some of these values for your machine.2017-12-11 at 12:47 #14886
I re-read your question…. the X gantry has one motor on both sides and the Y gantry has one motor. The AMS shield will not supply enough amps to drive three stepper motors – one of the L293 chips will melt.
Better to use a RAMPs or RUMBA board with a Y shaped cable for the two X motors, same as used on z axis of 3D printers like Prusa.2017-12-11 at 17:10 #14889AnonymousInactive
Dan, I do not have ramps and rumba, but if two adafruit and two arduino, is it possible to combine them?
thank you very much2017-12-11 at 17:32 #14892
Only with a lot of code rewriting.2017-12-12 at 09:32 #14900AnonymousInactive
Could it be with a Polarshield?
I have one
regards!2017-12-12 at 11:03 #14901
We don’t support the polarshield at the moment. More code writing.2017-12-18 at 13:20 #15008AnonymousInactive
I got ramps 1.4 shield. How to activate Makelangelo firmware for two x-axis motors
Thank you!2017-12-18 at 15:08 #15010
you should be able to change the configure.h file
#define BOARD_TYPE RAMPS
#define MACHINE_STYLE TRADITIONALXY
and in traditionalxy.h you may want to make further adjustments for speeds.
once the code is uploaded, run makelangelo app, connect to the robot, and do your configuration setup.
I have not personally tested the code for the makelangelo on a traditional gantry, so please report back. I’m here to help!2017-12-19 at 09:35 #15019AnonymousInactive
Thanks for your help, it’s great.
the configuration would be like this2017-12-19 at 09:48 #15020AnonymousInactive
Can you tell me where the drivers in ramps controller are?
Do I have to make any changes to clone the x axis?
Thank you!2017-12-19 at 12:23 #15025
eh, those links are 404.
the drivers on OUR ramps are a4988, 1/16th microstepping.2017-12-23 at 15:25 #15063AnonymousInactive2017-12-23 at 15:35 #15064
Makelangelo-firmware is not a library.
I don’t know why you are using #include
many times in your sketch.
I’m not sure what you’re trying to do.2017-12-23 at 16:07 #15065AnonymousInactive
Do you have firmware upload tutorial?2017-12-23 at 17:32 #15066AnonymousInactive
ok, I already got firmware running.
Now, what connection of ramps to clone Y axis?2017-12-23 at 17:56 #15067AnonymousInactive2017-12-24 at 02:27 #15069AnonymousInactive
Is it possible to clone Y axis to E1 of Ramps 1.4?
is the best … is it difficult?
Thank you!2017-12-24 at 11:12 #15072
some people use a Y shaped cable to drive two motors from one axis driver. be careful about current limit! each driver has max 1.5a without cooling, 2 with cooling.2019-05-16 at 15:37 #23328
Hello everyone, first of all my congratulations, this is an incredible project! a great job!!
I’m from Argentina and put together my version of Makelangelo with the polargraph type mechanical structure and it worked the first time, it worked perfectly.
Now I intend to make it walk with the traditional type structure x,y and the problems came … as I had to place a motor directly on the x axis another motor on the y axis (this has a gear reduction and pinion), the calculations for each of them are different.
How can I tell the firmware this difference?
What should I add and where?
Can you help me, please?? From already thank you very much2019-05-16 at 15:52 #23329
I’m excited someone tries the traditional XY mode. Please post pictures and keep us updated.
In robot_traditionalxy.cpp method IK() you will see
motorStepArray = lround(x / THREAD_PER_STEP);
motorStepArray = lround(y / THREAD_PER_STEP);
the THREAD_PER_STEP is really the difference between mm and steps-per-mm for each axis. For your solution you will want to change it a bit like this:
motorStepArray = lround(x / STEPS_PER_MM_X );
motorStepArray = lround(y / STEPS_PER_MM_Y );
and then define each new value based on your gear reduction, microstepping, and so on.2019-05-16 at 15:57 #23330
I made an update to the dev branch. the values are defined in robot_traditionalxy.h, adjust them there and everything should continue as normal.2019-05-17 at 04:50 #23334
thank you for your attention Dan, I will test the changes as soon as possible and when ready I will upload images. a big hug2019-05-20 at 18:39 #23361
Hello, I managed to get the first images, but I could not upload them, so I sent them by email … Sorry
It’s still a long time before it’s finished, it’s just the beginning.
Now I have a new problem, the engines get very hot when they are at rest, that is, when one motor moves, the other is magnetized and at that moment it gets very hot.
it would be possible from the firmware to tell each engine that when it does not receive movement commands it is in disable mode and when it receives orders to move it will be in enable mode ?? Thank you2019-05-21 at 04:35 #23362
Well … I try to show the images
- You must be logged in to reply to this topic.