[BUG] Marlin 2.0 Homing Z won't work with SKR Pro

[budi67]

Hello all

I just finished install Marlin 2.0 on my SKR PRO, but i have a problem with homing.

I have a bltouch and i must set my Z_offset to -8
Bltouch ==> https://www.thingiverse.com/thing:2841443

But when it homing it stop at z0, i don't understant

A big thanks
Configuration.zip

[golfromeo-fr]

with the updates in the last 48 hours, the bltouch probing with my SKR PRO no longer works.
the bltouch now deploy/stow 3 times and no longer go down for probing
the probing fails

[golfromeo-fr]

is it related to
bigtreetech/BIGTREETECH-SKR-PRO-V1.1#31
?

[Chr157i4n]

with the updates in the last 48 hours, the bltouch probing with my SKR PRO no longer works.
the bltouch now deploy/stow 3 times and no longer go down for probing
the probing fails

This sound like the same issue i have.

[golfromeo-fr]

I figured out my problem: the connector on the bltouch was "half" disconnected on the "Z-" side (vibrations?) and the signal pin/+5V/Ground were still attached (probe still doing deploy/stow

so yes the pin physically changed!
=> problem solved

it looks like the Z probe pin has changed
the pin in pins_BIGTREE_SKR_PRO_V1.1.h has not changed it's PA2
#define Z_MIN_PROBE_PIN PA2
but maybe the definition of PA2 has changed for some obscure reason

---

I have tried the M43 S command like @ChristianGer did

I have tried
#define Z_MIN_PROBE_ENDSTOP_INVERTING false
and
#define Z_MIN_PROBE_ENDSTOP_INVERTING true
but the sequence only prints, ignoring the Z_MIN_PROBE_ENDSTOP_INVERTING value
Recv: . Z_MIN_PROBE_ENDSTOP_INVERTING: false

Z_MIN_PROBE_ENDSTOP_INVERTING, SERVO_DELAY are overrided in Conditionals_LCD.h

Send: M43 S
Recv: Servo probe test
Recv: . using index: 0, deploy angle: 10, stow angle: 90
Recv: . Probe Z_MIN_PROBE_PIN: 11
Recv: . Z_MIN_PROBE_ENDSTOP_INVERTING: false
Recv: . Check for BLTOUCH
Recv: . Deploy & stow 4 times
Recv: WARNING: INVERTING setting probably backwards.
Recv: ** Please trigger probe within 30 sec **
Communication timeout while idle, trying to trigger response from printer. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves.
Recv: FAIL: No trigger detected
Recv: ok

[budi67]

Hello

How do you active M43 ?
I have try to active #define PINS_DEBUGGING, but i have this error !!
Thanks

[golfromeo-fr]

I have try to active #define PINS_DEBUGGING, but i have this error !!

bigtreetech/BIGTREETECH-SKR-PRO-V1.1#31 (comment)

[Patag]

@budi67 See #14894

[budi67]

Thanks Patag.

I have download a new firmware from Marlin and all started again from 0.
All work fine.

But as the SKR Pro as no Eeprom, where save the Mesh ?

[Chr157i4n]

You can use SD-Card EEPROM Emulation to store the values in the SD-Card of the LCD:

#define BOARD_NAME "BIGTREE SKR Pro 1.1"

// Use one of these or SDCard-based Emulation will be used
//#define SRAM_EEPROM_EMULATION // Use BackSRAM-based EEPROM emulation
//#define FLASH_EEPROM_EMULATION // Use Flash-based EEPROM emulation

simply uncomment FLASH_EEPROM_EMULATION

(Marlin/src/pins/stm32/pins_BIGTREE_SKR_PRO_V1.1.h)

[budi67]

A big thanks for your answer Christianger, i will try this

[budi67]

I have uncomment FLASH_EEPROM_EMULATION

For save it's M500 ??
I have try and i get this :
Error:EEPROM disabled
[ERROR] Error:EEPROM disabled

In configuration.h this option is enable ==> #define EEPROM_CHITCHAT

[gloomyandy]

@budi67 Do you have EEPROM_SETTINGS enabled? That needs to be on toy have M500 etc work.

[budi67]

Thanks Gloomyandy, it's ok, work fine

[budi67]

Sorry but another question about start gcode in slicer

G28 after just M420 S1 ?

And where are stocked the infos of the mesh ?, after a M500 i have nothing on the Board sd an nothing on TFT sd

[budi67]

In pronterface when i make M500 after a G29
It say : echo:Settings Stored (762 bytes; crc 20618)
If i make M501 : echo:EEPROM version mismatch (EEPROM=? Marlin=V68)
echo:Hardcoded Default Settings Loaded
If i make M503, i don't have the mesh data

[boelle]

@budi67 problem solved?

[budi67]

yes, problem solved, sorry for not given assets news, lots of worries right now

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.