search

makerbase-mks / SGEN_L

MKS SGEN_L is a powerful 32-bit 3D printer control board with LPC1768. Support Marlin2.0, Smoothieware. Support MKS LCD12864B/MINI12864/LCD2004/12864 and MKS TFT Touch Screens. The motherboard integrates SPI / UART interface and works with MKS TMC2130/TMC2208 V2.0/TMC2209. It can be used after plugged in. No soldering or flying lead is required ...
https://es.aliexpress.com/item/33036918120.html?spm=a2g0o.store_home.slider_165457030.3
GNU General Public License v3.0
87 stars 61 forks source link

G28 fails to home z axis #48

Open doug-scott opened 3 years ago

doug-scott commented 3 years ago

I am running a MKS SGEN_L V1.0 with a BTT TFT35E3V3.0, MKS TMC2209 drivers in UART mode, and a 3DPROBE. Using Marlin 2.0.7.2 and current version of firmware in Touchscreen that was compiled a few days ago from the current release of source code from here.

When I run the G28 command it will home the X and Y axis, then move to mid point of bed and deploys probe. Then it just retracts and deploys the probe a couple of times without moving the bed at all. Once it does the multiple deploy/retract dance it shows an error

I have enabled DEBUG mode and here is the output from Pronterface:

Connecting... Printer is now online.

M111 S32 SENDING:M111 S32 echo:DEBUG:LEVELING g28 SENDING:G28 G28 X115.0000 Y145.0000 Z5.0000 Machine Type: Cartesian Probe: BLTOUCH Probe Offset X30.0000 Y0.0000 Z0.0000 (Right-Center & Same Z as Nozzle) Auto Bed Leveling: UBL (enabled) UBL Adjustment Z 0.000 current_position= X115.0000 Y145.0000 Z5.0000 : Leveling ON current_position= X115.0000 Y145.0000 Z5.0000 : ...Now OFF current_position= X115.0000 Y145.0000 Z5.0000 : sync_plan_position Raise Z (before homing) by 5.0000 do_blocking_move_to X115.0000 Y145.0000 Z5.0000 X115.0000 Y145.0000 Z5.0000 <<< do_blocking_move_to X115.0000 Y145.0000 Z5.0000 homeaxis(X) Home 1 Fast: do_homing_move X115.0000 Y145.0000 Z5.0000 ...(X, 2.0000, 50.00) <<< do_homing_move X115.0000 Y145.0000 Z5.0000 do_homing_move X115.0000 Y145.0000 Z5.0000 ...(X, -435.0000, [50.0000]) <<< do_homing_move X115.0000 Y145.0000 Z5.0000 Move Away: do_homing_move X115.0000 Y145.0000 Z5.0000 ...(X, 5.0000, [50.0000]) <<< do_homing_move X115.0000 Y145.0000 Z5.0000 Home 2 Slow: do_homing_move X115.0000 Y145.0000 Z5.0000 ...(X, -10.0000, 25.00) <<< do_homing_move X115.0000 Y145.0000 Z5.0000 set_axis_is_at_home(X) Axis X home_offset = 0.0000 position_shift = 0.0000 home_offset[X] = 0.0000 current_position= X0.0000 Y145.0000 Z5.0000 : <<< set_axis_is_at_home(X) current_position= X0.0000 Y145.0000 Z5.0000 : sync_plan_position current_position= X0.0000 Y145.0000 Z5.0000 : > AFTER set_axis_is_at_home <<< homeaxis(X) homeaxis(Y) Home 1 Fast: do_homing_move X0.0000 Y145.0000 Z5.0000 ...(Y, 2.0000, 50.00) <<< do_homing_move X0.0000 Y145.0000 Z5.0000 do_homing_move X0.0000 Y145.0000 Z5.0000 ...(Y, -435.0000, [50.0000]) <<< do_homing_move X0.0000 Y145.0000 Z5.0000 Move Away: do_homing_move X0.0000 Y145.0000 Z5.0000 ...(Y, 5.0000, [50.0000]) <<< do_homing_move X0.0000 Y145.0000 Z5.0000 Home 2 Slow: do_homing_move X0.0000 Y145.0000 Z5.0000 ...(Y, -10.0000, 25.00) <<< do_homing_move X0.0000 Y145.0000 Z5.0000 set_axis_is_at_home(Y) Axis Y home_offset = 0.0000 position_shift = 0.0000 home_offset[Y] = 0.0000 current_position= X0.0000 Y0.0000 Z5.0000 : <<< set_axis_is_at_home(Y) current_position= X0.0000 Y0.0000 Z5.0000 : sync_plan_position current_position= X0.0000 Y0.0000 Z5.0000 : > AFTER set_axis_is_at_home <<< homeaxis(Y) BLTouch Command :160 BLTouch Command :90 last_written_mode - 0 config mode - OD home_z_safely X0.0000 Y0.0000 Z5.0000 current_position= X0.0000 Y0.0000 Z5.0000 : sync_plan_position destination= X115.0000 Y145.0000 Z5.0000 : home_z_safely do_blocking_move_to X0.0000 Y0.0000 Z5.0000 X115.0000 Y145.0000 Z5.0000 <<< do_blocking_move_to X115.0000 Y145.0000 Z5.0000 homeaxis(Z) current_position= X115.0000 Y145.0000 Z5.0000 : Probe::set_deployed deploy: 1 Home 1 Fast: BLTouch DEPLOY requested BLTouch Command :10 BLTouch ALARM or TRIGGER after DEPLOY, recovering BLTouch Command :160 BLTouch Command :90 BLTouch Command :10 BLTouch Command :90 BLTouch Command :10 BLTouch Recovery Failed Error:!! STOP called because of BLTouch error - restart with M999 [ERROR] Error:!! STOP called because of BLTouch error - restart with M999

<<< home_z_safely X115.0000 Y145.0000 Z5.0000

do_blocking_move_to X115.0000 Y145.0000 Z5.0000 X115.0000 Y145.0000 Z5.0000 <<< do_blocking_move_to X115.0000 Y145.0000 Z5.0000 current_position= X115.0000 Y145.0000 Z5.0000 : sync_plan_position current_position= X115.0000 Y145.0000 Z5.0000 : Leveling OFF current_position= X115.0000 Y145.0000 Z5.0000 : ...Now ON current_position= X115.0000 Y145.0000 Z5.0000 : sync_plan_position <<< G28 X115.0000 Y145.0000 Z5.0000

To me it would be more helpful if the debug mode would also capture what is missing or expected that is causing the session to fail. This is one of those things that requires the user to know what is supposed to happen beyond "bed should move here but doesn't".

Configuration_files.zip

mks-viva commented 3 years ago

If Zaxis have not home, usually it is caused by the limit setting, you can try to modify it