Ramps Dual endstops not configured?

Software / Firmware
1

I’ve tried version 507 and 508 RAMPS_DUAL on my new LR2 with the same results. The steppers are attached per the dual endstop guide and picture here: https://www.v1engineering.com/wp-content/uploads/2017/11/Ramps.jpg

When jogging the machine, the X-direction only moves Y2 and the Y-direction moves the Y1. Z acts only on Z1. Was there still some configuration I need to do? I noticed there is not a SW version RAMPS_DUAL_LR but that doesn’t explain the Y axis not working together. All limits are closed.

2

I take it you have a RAMPS board? And a low rider? Can you share a photo of your wiring?

3

Thanks Jeff, This is a RAMPS 1.4 that was previously controlling an MPCNC that was too small to be fun to use. I built the LowRiderV2 to allow bigger projects and provide better access to the work space. As you may have suspected the E0 and E1 positions were swapped and there was a bad connection or two somewhere. After reviewing the instruction on how to connect I see the real issue being that there is no preconfigured LowRider firmware for RAMPS. Any tips for me modifying the code? It has been a while since i did an Arduino project.

4

I’m sure Jeff will be back around with some specifics since he has in-depth knowledge of the firmware, but here is a bit of info to get your started. The latest/official release point for MPCNBC firmware is here. Currently PlatformIO is recommended for compiling the Marlin firmware. You can find more information here. If you download from the official release point, you can also use the Arduino IDE to compile and upload the firmware. More information on compiling using the Arduino IDE here. Note that other versions of Marlin (outside of the official release point) may not compile using the Arduino IDE.

All your Marlin changes should be limited to the configuration.h and configuration_adv.h. If it were me, I’d run a difference tool on these two files between the Ramps MPCNC firmware and one of the LowRider versions for another board and see what pops up. My current difference tool is meld, though there are are a lot of difference tools on the net.

1 Like
5

That picture you reverenced is for the MPCNC, not the lowrider.

The Primo has 2 X motors, 2 Y motors, and 1 Z motor. The LR2 has 1 X motor, 2 Y motors, and 2 Z motors, so the wiring would need to be different. I actually question how you’ve got these things wired according to that diagram when the number of motors for X and Z is different. It seems to me that you might have the function of each of these motors different.

I haven’t looked at the LR2 specific firmware, but looking at the parts list for the LR2, I do not see microswitches listed. I don’t see provisions for endstops on the parts, but haven’t looked really close.

Keeping the machine level with Z endstops might work, however, since the machine does not have an absolute zero, unlike a 3D printer, this could be tricky. Maybe having optical endstops at an arbitrary height would work, provided that they didn’t get chips/dust in them, or were cleaned out prior to any attempt at homing. In any case, the firmware would need to be adjusted from the version for the MPCNC.

To use the dual endstop firmware (In order to get dual Y endstops on the LR2) I would wire the board as follows:

X goes to the X driver. Simple enough. The E0 driver for X2 would be left unused. I would probably just wire the X endstop in parallel to both X_Min and X_Max so that the firmware didn’t freak out when X2 doesn’t home.

Y1 goes to the Y driver, Y1 endstop to the Y_Min endstop connector.

Y2 goes to the E1 driver, Y2 endstop to the Y_Max endstop connector

Z1 and Z2 wired in series to the Z driver. Touch plate wired to the Z_Min endstop.

This won’t level the gantry for homing Z, but you will get the expected results when trying to home Z. It will square the Y axis to dual endstops.

I don’t think that the LR2 was designed for use with endstops, other than perhaps the Z touch plate.

Given what you’ve described for the movement, I would surmise that the X and Y (on the RAMPS) are connected to the 2 motors on the belts on each side plate. This would have the effect of X jogging one side, and Y jogging the other. Z1 is connected to Z, but Z2 is connected to something else. Not sure what, since you haven’t mentioned it connected to anything else, and you have not described X moving at all.

It would be worthwhile to use M119 from a terminal to query the endstop states, which might give you some more insight into what’s going on.

6

Dan and Robert are both right. Dan probably doesn’t know that we are trying to make dual endstop versions for the low rider. It is tricky because we don’t want the gantry to rest on microswitches, so we took the extra step and made it autosquare up with G28. But we want to be able to use the touchplate, so we also set up the probe down with G38.2.

The only trouble is, you have a pesky ramps instead of an skr or rambo.

If you want to get working RN, then follow Dan’s advice. If you want to use the new hotness, then meld the rambo and ramps versions of configuration and configuration_adv and make the rambo dual lr into a ramps dual lr. I think that should be very few changes. Just the board type, removing the current setting, and changing the steps per mm.

7

I appreciate the help guys. I did a merge with a Rambo version but i think my RAMPS is having a connection issue on the endstop pins. Going to operate without switches for now and research how to upgrade to a SKR board in the near future.

8

Easy enough to test the switches with M119, and worth doing

1 Like