I am unable to move axis XY with a belt on. With the belt off I can stop the motors with even slight finger pressure. Z works but again can stop with only slight finger pressure. XY carriage moves easily by hand when belts are not connected. NEMA 17 stepper 2.0A 83.6 oz. in , Rambo 1.4 , 24V ps. All steppers move in the correct directions Wired to (X,E0) Y,E1)
What drivers do you have and have you set the current limits on them?
:facepalm:… rambo. I can read…
Are you pulley set screws tight?
It is not the screws
Configuration_adv.h Max current all axis is 1000 ma which is half my rated 2A like I said I can stop rotation with my fingers
the holding current is scaled down to 800mA
are there jumpers that I should have placed? There are multiple current references pertaining to the steepers that needs to be changed if this is the problem which I assume is the case?
how do I edit the configuration_adv.h?
Don’t change the current until we figure out what’s wrong. The settings from Ryan’s firmware are much stronger than what you described.
Did you get the rambo from Ryan? Someone had an einsy rambo recently that was wired ABAB instead of AABB and that was causing a lot of problems.
I had installed the latest firmware with U8glib 1.19.1 with your help I split out the pairs to all steppers with a meter before connecting them one pair going to pins1&2 then the other to 3&4 according to the diagram on V1
Ah, this is also you: https://github.com/Allted/Marlin/archive/MPCNC_Rambo_T8_16T_LCD_DualEndstop.zip
I sometimes forget… Sorry.
The firmware you should be using is here: https://github.com/Allted/Marlin/archive/MPCNC_Rambo_T8_16T_LCD_DualEndstop.zip
It is not 1.19.1. It is tracking 2.0.x, and Ryan has all of our customizations and stuff in it, and he tests it.
You should be able to save the 1.19.1 version you’ve got, make a copy somewhere. Then unzip the one I just linked, and open the .ino file with arduino and flash it straight away.
No sorry I am using MPCNC_Raambo_T8_16T_LCD_DualEndstop
Can you run M503 from Repetier-Host and paste the results here? There is a lot of info in there that might be helpful.
|
16:16:55.480 : echo:Marlin 414D bugfix-2.0.x
|
|
|
Marlin 414D bugfix-2.0.x. So that’s good. That is definitely the dual endstop firmware from Ryan.
16:17:03.513 : Cap:EEPROM:0. This is not my preference, but it’s not going to hurt your motors, in fact, it eliminates a lot of potential problems.
I thought it would output the current values. They should be available with M907.
The firmware looks just fine. The pulley screws are good. That leaves maybe some wiring issue, but how would it affect all the motors? Maybe an issue with the test procedure?
I’m running out of ideas. Someone else is going to pop in here and have something for us, I hope.
Thanks
the M907 is in the configuration_Adv.h
these are the current, current settings (had to say it!) I have currently no Idea what to change
- @section stepper motor current
- Some boards have a means of setting the stepper motor current via firmware.
- The power on motor currents are set by:
- PWM_MOTOR_CURRENT - used by MINIRAMBO & ULTIMAIN_2
- known compatible chips: A4982
- DIGIPOT_MOTOR_CURRENT - used by BQ_ZUM_MEGA_3D, RAMBO & SCOOVO_X9H
- known compatible chips: AD5206
- DAC_MOTOR_CURRENT_DEFAULT - used by PRINTRBOARD_REVF & RIGIDBOARD_V2
- known compatible chips: MCP4728
- DIGIPOT_I2C_MOTOR_CURRENTS - used by 5DPRINT, AZTEEG_X3_PRO, AZTEEG_X5_MINI_WIFI, MIGHTYBOARD_REVE
- known compatible chips: MCP4451, MCP4018
- Motor currents can also be set by M907 - M910 and by the LCD.
- M907 - applies to all.
- M908 - BQ_ZUM_MEGA_3D, RAMBO, PRINTRBOARD_REVF, RIGIDBOARD_V2 & SCOOVO_X9H
- M909, M910 & LCD - only PRINTRBOARD_REVF & RIGIDBOARD_V2
*/
//#define PWM_MOTOR_CURRENT { 1300, 1300, 1250 } // Values in milliamps
#define DIGIPOT_MOTOR_CURRENT { 120, 120, 120, 120, 120 } // Values 0-255 (RAMBO 135 = ~0.75A, 185 = ~1A)
//#define DAC_MOTOR_CURRENT_DEFAULT { 70, 80, 90, 80 } // Default drive percent - X, Y, Z, E axis
// Use an I2C based DIGIPOT (e.g., Azteeg X3 Pro)
//#define DIGIPOT_I2C
#if ENABLED(DIGIPOT_I2C) && !defined(DIGIPOT_I2C_ADDRESS_A)
/**
- Common slave addresses:
- A (A shifted) B (B shifted) IC
- Smoothie 0x2C (0x58) 0x2D (0x5A) MCP4451
- AZTEEG_X3_PRO 0x2C (0x58) 0x2E (0x5C) MCP4451
- AZTEEG_X5_MINI 0x2C (0x58) 0x2E (0x5C) MCP4451
- AZTEEG_X5_MINI_WIFI 0x58 0x5C MCP4451
- MIGHTYBOARD_REVE 0x2F (0x5E) MCP4018
*/
#define DIGIPOT_I2C_ADDRESS_A 0x2C // unshifted slave address for first DIGIPOT
#define DIGIPOT_I2C_ADDRESS_B 0x2D // unshifted slave address for second DIGIPOT
#endif
//#define DIGIPOT_MCP4018 // Requires library from https://github.com/stawel/SlowSoftI2CMaster
#define DIGIPOT_I2C_NUM_CHANNELS 8 // 5DPRINT: 4 AZTEEG_X3_PRO: 8 MKS SBASE: 5
// Actual motor currents in Amps. The number of entries must match DIGIPOT_I2C_NUM_CHANNELS.
// These correspond to the physical drivers, so be mindful if the order is changed.
#define DIGIPOT_I2C_MOTOR_CURRENTS { 1.0, 1.0, 1.0, 1.0, 1.0, 1.0, 1.0, 1.0 } // AZTEEG_X3_PRO
That should be fine. There are many rambos out there with those same settings and people are using belts on most of them.
still not working!!
Try an older version of my firmware, on github under releases try 402
I loaded 402. Z works X and Y mostly just vibrate with the belt connected regardless of tension. Without the belt, they turn fine. Without the belt the carriage moves easily by hand there is not binding.