Welcome to the SeeMeCNC Community

My Romax v2 won't home correctly. When I send G28, or press the button on the LCD, all three cheapskates go up the towers and the end-stop screws press the end-stop switches. But, when the screw hits the switch, the screws just keep slamming into the end-stops until I run over to shut the machine down manually.

When I send M119 while pressing the switches, I get: x_max:H y_max:H z_max:H. I've cleared the EEPROM and re-installed the firmware. I've adjusted the belt tension on all three carriages. And I've also checked the RAMBo board connections. I even bought new end-stops to see if that could be the problem.

I don't see what the issue could possibly be, and I'm wiling to try any suggestions.

One thing could be that the endstops are not wired to their corresponding stepper axes. By this I mean, the X endstop is on the Y endstop connector. You don't tell the history of this machine, if it is new and/or if you've done any rewiring on RAMBo, this is an easy mistake to make.

Run M119 and press just the X endstop switch. You should get x_max:H do this for each and validate that you are seeing the proper switches activated.

I checked the continuity of the wires, and they are all in the correct connectors and position on the RAMBo.
And as for the history of the machine, I have had it printing and working for about a year and a half. About a month ago my shelf hotend broke, and I decided, instead of trying to fix it, I would order the HE280, and the EZR, Ball Joint Arms, Injection Molded Carriages, etc. Last week I finished all of the wiring and assembly, and I've had problems ever since. The current problem is the inability to home my machine.
I've experimented with both the old and new firmware. With the old firmware, my machine would home in reverse, and with the new, I have this problem.
I ran M119 and did as you said, and got x_max:H, y_max:H and z_max:H when pressing the corresponding axes endstop switch.

Ok, if the electronics (and mechanical endstops) are indeed working properly as verified with M119, then the issue is firmware and/or configuration. Which "new" firmware are you using? Post the configuration.h file for us to take a look at.

Here the 2 configuration.h files that I have used

have you made any other changes lately?

I have found the answer to my problem in a another forum earlier today! Thank you all for your help

So tell the class!

g.

The solution was in the configuration.h. I changed these values:
#define INVERT_X_DIR 0
#define INVERT_Y_DIR 1
#define INVERT_Z_DIR 0