I’m putting together an MP3DP, and I got all of the parts here. I’m using a Mini Rambo and a Titan Aero, so I flashed the MP3DP511_MRambo firmware found at the bottom of the MP3DP page. The only change that I have made to the firmware is in the thermal settings: #define TEMP_SENSOR_0 5 //MPCNC
The problem that I am having, is that for some reason when I try to move 10 mm, it moves almost 20 mm (in all directions). This happens with the LCD and Repetier Host. This is what I have in the movement settings: #define DEFAULT_AXIS_STEPS_PER_UNIT { 200, 200, 788, 200 } //MPCNC
Do I have the right firmware? Is there any other reason that I could be getting such odd results? It also seems like when I try to extrude some of the filament using the LCD/Repetier, it moves VERY slowly, compared to my experience with the ROBO 3D. I’m not sure if it is supposed to do that though, or if it could be at all related?
Translate does not seem to be working well enough to help, Rissoual. The ramps firmware comes ready for drv8825. Any other board or driver will need adjustments.
I made the changes to my steps in the firmware to: #define DEFAULT_AXIS_STEPS_PER_UNIT { 100, 100, 400, 837 } //MPCNC
However, it made no difference. It is as if the original numbers are still in effect, and the actual distance travelled (in all directions) is still about double the distance that it should be. Any guess as to why that might be the case? The only place that I make changes is in the configuration.h file, correct?
Edit: I just checked on the LCD, and the original numbers are definitely still in there. I’ve updated my Arduino IDE, and I tried flashing from 2 different computers, but no luck. I can see lights on the Mini Rambo while it is uploading, and I can see on my computer that the uploading completes without any errors, but I can’t figure out why the numbers won’t change to the ones that I edit in the configuration.h file?
Thanks to everyone that has offered suggestions! It turns out that I had accidentally clicked on “store memory” on the LCD. This kept the incorrect default axis settings, even after flashing the firmware again. I had to “restore failsafe” to revert to the firmware with the updated axis settings, and now everything seems to be working as it should.
Moi j’ai une autre expérience avec le problème des pas. J’ai trouvé la solution de modifier les jumpers des driver, mais la carte de contrôle est (MKS GEN 1.4).