MK4duo icon indicating copy to clipboard operation
MK4duo copied to clipboard

Home G28 not working for Minitronics 2.0

Open Diexon opened this issue 4 years ago • 1 comments

Hello MK team!

I hope you can hell me here.

Issue description

G28 command is not working. If I send it in the terminal the board answers ok and the axis current position but nothing moves.

The axis are moving normally with manual actuation via G code.

I tried to debug myself but #define PINS_DEBUGGING is not compiling due to not supported platform and #define DEBUG_FEATURE is not showing anything extra in the terminal.

Firmware version

4.3.8 (Unfortunately the only one compiling for Minitronics 2.0)

My setup

The printer is a Prusa i3 clone using Cartesian. I use mechanical endstops for X and Y and HAL sensor for Z. I tested them and they are working fine.

Heaters, thermistors, steppers and ventilaros al all operational. The only issue is that when homing nothing is moving.

I do not think my setup changes have anything to do with this. But just in case: #define MOTHERBOARD BOARD_MINITRONICS_V2 #define SERIAL_PORT_1 -1 #define DEFAULT_AXIS_STEPS_PER_UNIT {160, 160, 8000, 2263.54, 625, 625, 625} #define DEFAULT_MAX_ACCELERATION {1000, 1000, 50, 1000, 1000, 1000, 1000} #define DEFAULT_ACCELERATION 1000 #define DEFAULT_XJERK 5.0 #define DEFAULT_YJERK 5.0 #define X_DRIVER_TYPE DRV8825 #define Y_DRIVER_TYPE DRV8825 #define Z_DRIVER_TYPE DRV8825 #define X2_DRIVER_TYPE DRV8825 #define Y2_DRIVER_TYPE DRV8825 #define Z2_DRIVER_TYPE DRV8825 #define Z3_DRIVER_TYPE DRV8825 #define E0_DRIVER_TYPE DRV8825 #define E1_DRIVER_TYPE DRV8825 #define E2_DRIVER_TYPE DRV8825 #define E3_DRIVER_TYPE DRV8825 #define E4_DRIVER_TYPE DRV8825 #define E5_DRIVER_TYPE DRV8825 #define BEZIER_JERK_CONTROL

Diexon avatar Apr 26 '20 21:04 Diexon

After some deeper debugging I think I solved this one: The endstop pins are set for the Minitronics 2 to be MAX. My Prusa homes to min so this is solved by this delta:

diff --git a/MK4duo/src/boards/2706.h b/MK4duo/src/boards/2706.h index 28d4c898..a9880d6f 100644 --- a/MK4duo/src/boards/2706.h +++ b/MK4duo/src/boards/2706.h @@ -86,12 +86,12 @@ #define ORIG_SOL7_PIN NoPin

//###ENDSTOP -#define ORIG_X_MIN_PIN NoPin -#define ORIG_X_MAX_PIN 8 -#define ORIG_Y_MIN_PIN NoPin -#define ORIG_Y_MAX_PIN 9 -#define ORIG_Z_MIN_PIN NoPin -#define ORIG_Z_MAX_PIN 4 +#define ORIG_X_MIN_PIN 8 +#define ORIG_X_MAX_PIN NoPin +#define ORIG_Y_MIN_PIN 9 +#define ORIG_Y_MAX_PIN NoPin +#define ORIG_Z_MIN_PIN 4 +#define ORIG_Z_MAX_PIN NoPin

Is there any reason why Minitronics 2 origins are defined to MAX? If not maybe is a good change to push to the repo.

Cheers.

Diexon avatar Apr 27 '20 20:04 Diexon