I have had my MPCNC build since ~2014. Built it with Ramps 1.4 and it ‘was’ working fine in Dual XY with dual end stops (so that it auto aligns when homed). But, I am adding a laser and so thought I would upgrade to Marlin 2.0.9 at first. (Was running Marlin 1.?? something). I had problem and saw there was Marlin 2.1.1 so I updated to that - Same Problem. X axis works in dual mode - both motors home and individually use their endstops. But, the Y axis - no… When I just move the Y axis, both motors run, as expected. BUT, when I home - Only 1 Y motor moves, And, only the Y1 End Stop works, when hit the motor stops (and back up by nn mm- as it should)
In the configuration.h I see that it is enabled for both X and Y for dual end stops and dual XY with the Y2 motor set to run inverse.
Anyone else get this working on a Ramps 1.4? What am I missing?
As I said, this was working in Dual mode for years, since the custom Marlin code was first put out, i installed it and it has worked fine since with the original 1. something version.
The reason i wanted to upgrade was the laser - with version 1.nn I could control the laser power manually sending a M3 Sn command. But, the laser software controls the laser power via G1 S commands, and Marlin added that feature with 2.0.6+
I know the hardware is wired right, so it has to be something in the configuration file(s).
The motors work when not homing? It sounds like there is a wiring issue that popped up somehow.
Can you connect a computer and send M119? That will tell you the state of the endstops and also let you make sure the endstop 1 is next to the motor 1, and 2/2. If you have them reversed, it does funny things.
Yea, I had done the M119 - all the end stops work. From the way I had it working in Marlin 1.nn I had to change the X X2 around and the Y Y2 so they align with the correct motors. And, yes, repeatedly if I just move the Y - both motors turn (for testing, I’ve taken off the belts) ONLY when I try to Home, then only the Y1 motor turns. Have you had this working on the Ramps version? To me, it seems like for homing, the software is not enabling the Dual stepper mode for the Y axis, but it is for the X
I don’t the latest has been used on ramps. You could try the previous 513D version.
But it seems weird that it would move, and then not home, unless there was a problem with the endstops. The logic for all of that is completely the same for different boards, and the rambo and skr pro have been tested.
If that is MArlin 2.0.9, I had tried that one first.
Another really odd thing is, when the end stops are hit, the motors are moved back a few mm. What is odd is that when I home the Y, Only the Y1 motor turns, and when the Y1 stop is hit, BOTH the Y1 and Y2 motors move back a few mm. The Y2 doesn’t move to Home, and that stop is not hit, but Both motors move back a few mm. When homing, it is just not sending the signals to the Y2 motor. It must be a bug in the actual code. I will try to find it in the CPP files, but, I don’t know what files that logic would be in. (I do programming, so I crazy enough to debug this if i have to).
I have a spare SKR2 board, but, I don’t see a version for that board. If one of the other SKR versions would work, I might try putting that in, but, then I’ll have to print a new case…
If the logic is all tested, then it should just need to configure for that board, and maybe the pin.h file, etc.
Resolved - Capital E for Embarrassing. It was the Y2 limit sw - plugged in wrong. There were other issues before that I resolved (like I had to switch the X1 and X2 limits switches around, and the Y1 and Y2, so they worked with the right motors. Then the mounting bracket I printed to attach the laser made the laser hit the side rail pipe before the limit sw was hit, so i had to redesign and print a new mount, etc. BEFORE all that took place I had run the M119 command and made sure all the limit sw were working… But, somehow when i fixed all the above, the Y2 limit sw plug got moved over, and was showing it was at home (I have LEDs on each limit sw so i can see when they are hit, but because the plug was in the wrong location. the software saw the sw at home, but the LED was not on. So, that confused me.
Got that issue solved. After seeing the motor move when the other motor hit limit, it made me think it had to be a limit sw issue. I will keep going on the Ramps, but, I’ve already started configuring for SKR2 board, so after I get the ramps working again, I’ll give the SKR2 a try. (I have a CoreXY printer, the TronXY Pro 400 that I had problems with their controller board and picked up 2 of the SKR2 boards and got that printer working with that board, so i should be able to get the MPCNC working with it as well.
close older topics to help with spambots, and faster new user questions.